From owner-mobile-ip@sunroof.eng.sun.com  Sun Sep  2 12:29:29 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12026
	for <mobileip-archive@odin.ietf.org>; Sun, 2 Sep 2001 12:29:29 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id KAA02402;
	Sun, 2 Sep 2001 10:29:13 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA11476;
	Sun, 2 Sep 2001 09:29:06 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f82GS240014833
	for <mobile-ip-dist@sunroof.eng.sun.com>; Sun, 2 Sep 2001 09:28:02 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0/Submit) id f82GS1nS014832
	for mobile-ip-dist; Sun, 2 Sep 2001 09:28:01 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f82GRw40014825
	for <mobile-ip@sunroof.eng.sun.com>; Sun, 2 Sep 2001 09:27:58 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA27330
	for <mobile-ip@sunroof.eng.sun.com>; Sun, 2 Sep 2001 09:28:10 -0700 (PDT)
Received: from laposte.enst-bretagne.fr (laposte.enst-bretagne.fr [192.108.115.3])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id JAA11315
	for <mobile-ip@sunroof.eng.sun.com>; Sun, 2 Sep 2001 09:28:08 -0700 (PDT)
Received: from rsm.rennes.enst-bretagne.fr (rsm.rennes.enst-bretagne.fr [192.44.77.1])
	by laposte.enst-bretagne.fr (8.11.6/8.11.6) with ESMTP id f82GS6t31703
	for <mobile-ip@sunroof.eng.sun.com>; Sun, 2 Sep 2001 18:28:06 +0200
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr [193.52.74.194])
	by rsm.rennes.enst-bretagne.fr (8.8.8/8.8.8) with ESMTP id SAA09723
	for <mobile-ip@sunroof.eng.sun.com>; Sun, 2 Sep 2001 18:28:06 +0200 (MET DST)
Received: from givry.rennes.enst-bretagne.fr (localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.11.3/8.11.3) with ESMTP id f82GS6l02900
	for <mobile-ip@sunroof.eng.sun.com>; Sun, 2 Sep 2001 18:28:06 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200109021628.f82GS6l02900@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Mobile IPv6 draft revision 
In-reply-to: Your message of Wed, 22 Aug 2001 12:06:26 PDT.
             <3B8402B2.A4935BF7@iprg.nokia.com> 
Date: Sun, 02 Sep 2001 18:28:06 +0200
X-Virus-Scanned: by amavisd-milter (http://www.amavis.org/) at enst-bretagne.fr
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
 In your previous mail you wrote:

   some comments....
   
   <description of the "previous proposal">

=> the previous proposal works, so I'd like to keep it in the document,
but is a DAD probe against the Home Agent own address, so I'd like the
previous proposal gets a MAY (in place of the current MUST) and alternate
solutions (as I proposed in a previous mail) are developped, if possible
an alternate solution which works in all cases (mine works only for
mobile hosts).
I believe we agree to rollback to the "previous proposal" (as the
current proposal is obviously wrong)? So the discussion will be about
the level of requirement and to find/choose alternate proposals.

Regards

Francis.Dupont@enst-bretagne.fr


From owner-mobile-ip@sunroof.eng.sun.com  Sun Sep  2 21:48:37 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA16936
	for <mobileip-archive@odin.ietf.org>; Sun, 2 Sep 2001 21:48:36 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id TAA07259;
	Sun, 2 Sep 2001 19:48:25 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id SAA07198;
	Sun, 2 Sep 2001 18:48:21 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f831kh40015122
	for <mobile-ip-dist@sunroof.eng.sun.com>; Sun, 2 Sep 2001 18:46:43 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0/Submit) id f831khfO015121
	for mobile-ip-dist; Sun, 2 Sep 2001 18:46:43 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f831kd40015114
	for <mobile-ip@sunroof.eng.sun.com>; Sun, 2 Sep 2001 18:46:39 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id SAA12353
	for <mobile-ip@sunroof.eng.sun.com>; Sun, 2 Sep 2001 18:46:51 -0700 (PDT)
Received: from mail1.ics.ntts.co.jp (mail1.ics.ntts.co.jp [202.32.24.45])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id TAA06685
	for <mobile-ip@sunroof.eng.sun.com>; Sun, 2 Sep 2001 19:46:46 -0600 (MDT)
Received: from mail26.silk.ntts.co.jp by mail1.ics.ntts.co.jp (8.9.3/3.7W-NTTSOFT-SUR2.0)
	id KAA07392; Mon, 3 Sep 2001 10:46:44 +0900 (JST)
Received: from daemon.inl.ntts.co.jp by mail26.silk.ntts.co.jp (8.11.4/3.7W-silk-4.4)
	id f831khs14625; Mon, 3 Sep 2001 10:46:43 +0900 (JST)
Received: (qmail 63479 invoked by alias); 3 Sep 2001 10:46:43 +0900
Received: (qmail 63464 invoked from network); 3 Sep 2001 10:46:43 +0900
Received: from tunayosi.inl.ntts.co.jp (HELO localhost)
  by daemon.inl.ntts.co.jp with SMTP; 3 Sep 2001 10:46:43 +0900
Date: Mon, 03 Sep 2001 10:46:42 +0900 (JST)
Message-Id: <20010903.104642.884096194.takamiya@po.ntts.co.jp>
To: mobile-ip@sunroof.eng.sun.com
Cc: takamiya@po.ntts.co.jp
From: Noriaki Takamiya <takamiya@po.ntts.co.jp>
X-Mailer: Mew version 2.0 on XEmacs 21.4.1 (Copyleft)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hello,

  This is Takamiya. 

  I'm using MIPL implementation on USAGI IPv6 platform.

  In MIPL mailing list, I encountered the following problem:

  When a Home Agent sends Router Advertisement Message and changes
  Home Agent Flag(H) from on to off, should other Home Agent remove
  this router from the Home Agent List?

  I thought that the Home Agent changed Router Advertisement Message
  change Home Agent Flag from on to off, the other Home Agent should
  remove this router entry. But It seems that this behavior is not
  documented(draft 14) explicitly.

  I'm newbie about this mailing list, so I will apologize some
  mistakes.

  Regards,

--
Noriaki Takamiya


From owner-mobile-ip@sunroof.eng.sun.com  Mon Sep  3 04:04:17 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA05666
	for <mobileip-archive@odin.ietf.org>; Mon, 3 Sep 2001 04:04:16 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id CAA01845;
	Mon, 3 Sep 2001 02:05:04 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id BAA14882;
	Mon, 3 Sep 2001 01:05:00 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f8382x40015434
	for <mobile-ip-dist@sunroof.eng.sun.com>; Mon, 3 Sep 2001 01:02:59 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0/Submit) id f8382v3E015433
	for mobile-ip-dist; Mon, 3 Sep 2001 01:02:57 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f8382k40015425
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 3 Sep 2001 01:02:46 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id BAA07275
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 3 Sep 2001 01:02:58 -0700 (PDT)
Received: from telecom.samsung.co.kr ([165.213.221.4])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id CAA20967
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 3 Sep 2001 02:03:27 -0600 (MDT)
Received: from cychong (a22416 [165.213.224.16])
	by telecom.samsung.co.kr (8.9.3/8.9.3) with SMTP id RAA29530
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 3 Sep 2001 17:05:39 +0900 (KST)
Message-ID: <001601c1344f$aba71880$10e0d5a5@cychong>
From: "Chae-yong Chong" <cychong@telecom.samsung.co.kr>
To: <mobile-ip@sunroof.eng.sun.com>
References: <20010807120327.8097.qmail@web3504.mail.yahoo.com>
Subject: [mobile-ip] Question about the prefix length field of Router Advertisement
Date: Mon, 3 Sep 2001 17:08:50 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by sunroof.eng.sun.com id f8382l40015426
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 8bit

Hi.

I got an question about the "prefix length" field of Router Advertisemt in Moblie IPv6.
According to the RFC2462:

5.5.3 Router Advertisement Processing

       If the sum of the prefix length and interface identifier length
       does not equal 128 bits, the Prefix Information option MUST be
       ignored.  An implementation MAY wish to log a system management
       error in this case. It is the responsibility of the system
       administrator to insure that the lengths of prefixes contained in
       Router Advertisements are consistent with the length of interface
       identifiers for that link type. Note that interface identifiers
       will typically be 64-bits long and based on EUI-64 identifiers as
       described in [ADDR-ARCH].

I understand that the Router should advertise 64bits long network prefix to enable
a host to form the globally unique address by combining this netowk prefix and
host's interface identifer(whch is typically 64bits long)

In Mobile IPv6 said the Modified Prefix information which include the Router's global 
address is required for this following reasons.

    -  To allow a home agent (a router) to learn the address of all
       other home agents on the link for which it is providing home
       agent service, for use in building its Home Agents List as
       part of the dynamic home agent address discovery mechanism
       (Sections 9.8 and 10.8).

    -  To allow a mobile node to send a Binding Update to a router on
       the link on which its previous care-of address is located, for
       purposes of establishing forwarding from this previous care-of
       address to its new care-of address (Section 10.10).

From these two statement, I get a question.
If Router is located in /48 network and acts as an HA. If a mobile node
moved to this network and send a Router solicitation. The Mobile Node
needs a COA. For MN to form the COA by stateless address autoconfiguration, 
it should got a Router Advertisement which include 64 bits long network prefix.
But, the Router is located in the /48 network. 
In this case how does MN form a COA?

Sincerely
Chae-yong





From owner-mobile-ip@sunroof.eng.sun.com  Mon Sep  3 09:17:05 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA09219
	for <mobileip-archive@odin.ietf.org>; Mon, 3 Sep 2001 09:17:04 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id HAA15141;
	Mon, 3 Sep 2001 07:17:55 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id GAA07638;
	Mon, 3 Sep 2001 06:17:50 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f83DGL40015869
	for <mobile-ip-dist@sunroof.eng.sun.com>; Mon, 3 Sep 2001 06:16:21 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0/Submit) id f83DGLNK015868
	for mobile-ip-dist; Mon, 3 Sep 2001 06:16:21 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f83DGH40015861
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 3 Sep 2001 06:16:17 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id GAA14098
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 3 Sep 2001 06:15:44 -0700 (PDT)
Received: from ftpbox.mot.com (ftpbox.mot.com [129.188.136.101])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id HAA13984
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 3 Sep 2001 07:15:40 -0600 (MDT)
Received: [from pobox.mot.com (pobox.mot.com [129.188.137.100]) by ftpbox.mot.com (ftpbox 2.1) with ESMTP id GAA27281 for <mobile-ip@sunroof.eng.sun.com>; Mon, 3 Sep 2001 06:15:43 -0700 (MST)]
Received: [from m-il06-r1.mot.com (m-il06-r1.mot.com [129.188.137.193]) by pobox.mot.com (MOT-pobox 2.0) with ESMTP id GAA12734 for <mobile-ip@sunroof.eng.sun.com>; Mon, 3 Sep 2001 06:15:43 -0700 (MST)]
Received: from thorgal.crm.mot.com by m-il06-r1.mot.com with ESMTP; Mon, 3 Sep 2001 06:15:42 -0700
Received: from test9.crm.mot.com.crm.mot.com (test9.crm.mot.com [140.101.173.239])
	by thorgal.crm.mot.com (Postfix) with ESMTP
	id 5D3192ECAC; Mon,  3 Sep 2001 15:14:01 +0200 (CEST)
To: hesham.soliman@era.ericsson.se, claude.castellucia@@inria.fr,
        karim.el-malki@era.ericsson.se, ludovic.bellier@inria.fr
Cc: mobile-ip@sunroof.eng.sun.com
Subject: [mobile-ip] Question on HMIPv6 Dynamic MAP Discovery
From: Alexandru Petrescu <petrescu@crm.mot.com>
Date: 03 Sep 2001 15:15:39 +0200
Message-Id: <m3heukza84.fsf@test9.crm.mot.com>
Lines: 21
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.0.103
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Hi,

This has probably been raised in the past, sorry for duplicating
questions.  If so, thank you for pointing me to a thread discussing
it.

Page 11, middle of the one paragraph before last reads:

     "Upon reception of a router advertisement with the MAP option and
      given that a router is configured to re-send this option on
      certain interfaces, the router MUST copy the option and re-send
      it after incrementing the Distance field by one."

I understand that a router between AR and MAP is supposed to "re-send"
(forward) RA's from one interface to another?  Or is it supposed to
forward only the MAP Option?  Is there an implementation allowing to
configure a router to behave that way?

Thank you,

Alex



From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep  4 05:19:25 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA06425
	for <mobileip-archive@odin.ietf.org>; Tue, 4 Sep 2001 05:19:25 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id CAA13776;
	Tue, 4 Sep 2001 02:20:31 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id CAA16275;
	Tue, 4 Sep 2001 02:20:16 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f849J740016924
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 4 Sep 2001 02:19:07 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0/Submit) id f849J7D8016923
	for mobile-ip-dist; Tue, 4 Sep 2001 02:19:07 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f849J440016916
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 02:19:04 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id CAA16076
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 02:19:17 -0700 (PDT)
Received: from albatross-ext.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id CAA22502
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 02:19:16 -0700 (PDT)
Received: from era-t.ericsson.se (koff.ericsson.se [147.214.173.137])
	by albatross.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id f849JDK10134;
	Tue, 4 Sep 2001 11:19:13 +0200 (MEST)
Received: from era.ericsson.se by era-t.ericsson.se (SMI-8.6/LME-DOM-2.2.5(ERA/T))
	id LAA23148; Tue, 4 Sep 2001 11:19:12 +0200
Message-ID: <3B949C14.8B2BE09A@era.ericsson.se>
Date: Tue, 04 Sep 2001 11:17:08 +0200
From: Mattias Pettersson <mattias.pettersson@era.ericsson.se>
Organization: Ericsson Research
X-Mailer: Mozilla 4.77 [en] (Win95; U)
X-Accept-Language: en
MIME-Version: 1.0
To: mobile-ip@sunroof.eng.sun.com
CC: hesham.soliman@era.ericsson.se, claude.castellucia@inria.fr,
        ludovic.bellier@inria.fr, karim.el-malki@era.ericsson.se
Subject: Re: [mobile-ip] Question on HMIPv6 Dynamic MAP Discovery
References: <m3heukza84.fsf@test9.crm.mot.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit


Alexandru Petrescu wrote:
> 
> Hi,
> 
> This has probably been raised in the past, sorry for duplicating
> questions.  If so, thank you for pointing me to a thread discussing
> it.
> 
> Page 11, middle of the one paragraph before last reads:
> 
>      "Upon reception of a router advertisement with the MAP option and
>       given that a router is configured to re-send this option on
>       certain interfaces, the router MUST copy the option and re-send
>       it after incrementing the Distance field by one."
> 
> I understand that a router between AR and MAP is supposed to "re-send"
> (forward) RA's from one interface to another?  Or is it supposed to
> forward only the MAP Option? 

Only the MAP option, as far as I understand.

> Is there an implementation allowing to
> configure a router to behave that way?

KAME's rtadvd transmits RAs, but also monitors what other routers are
sending.

/Mattias

PS. My mailer was quite confused by your claude.castellucia@@inria.fr
(double @!!!).


From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep  4 07:07:18 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA07717
	for <mobileip-archive@odin.ietf.org>; Tue, 4 Sep 2001 07:07:17 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id EAA10700;
	Tue, 4 Sep 2001 04:08:24 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id EAA25992;
	Tue, 4 Sep 2001 04:08:18 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f84B7E40017065
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 4 Sep 2001 04:07:14 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0/Submit) id f84B7D3G017064
	for mobile-ip-dist; Tue, 4 Sep 2001 04:07:13 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f84B7A40017057
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 04:07:10 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id EAA25906
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 04:07:21 -0700 (PDT)
Received: from motgate.mot.com (motgate.mot.com [129.188.136.100])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id FAA12320
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 05:07:54 -0600 (MDT)
Received: [from mothost.mot.com (mothost.mot.com [129.188.137.101]) by motgate.mot.com (motgate 2.1) with ESMTP id EAA19545 for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 04:07:19 -0700 (MST)]
Received: [from m-il06-r2.mot.com (m-il06-r2.mot.com [129.188.137.24]) by mothost.mot.com (MOT-mothost 2.0) with ESMTP id EAA04291 for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 04:07:19 -0700 (MST)]
Received: from thorgal.crm.mot.com by m-il06-r2.mot.com with ESMTP; Tue, 4 Sep 2001 04:07:18 -0700
Received: from test9.crm.mot.com.crm.mot.com (test9.crm.mot.com [140.101.173.239])
	by thorgal.crm.mot.com (Postfix) with ESMTP
	id A1BDC2ECAC; Tue,  4 Sep 2001 13:05:32 +0200 (CEST)
To: mobile-ip@sunroof.eng.sun.com
Cc: hesham.soliman@era.ericsson.se, claude.castellucia@inria.fr,
        ludovic.bellier@inria.fr, karim.el-malki@era.ericsson.se
Subject: Re: [mobile-ip] Question on HMIPv6 Dynamic MAP Discovery
References: <m3heukza84.fsf@test9.crm.mot.com>
	<3B949C14.8B2BE09A@era.ericsson.se>
From: Alexandru Petrescu <petrescu@crm.mot.com>
Date: 04 Sep 2001 13:07:14 +0200
In-Reply-To: <3B949C14.8B2BE09A@era.ericsson.se>
Message-Id: <m3vgizi599.fsf@test9.crm.mot.com>
Lines: 22
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.0.103
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Mattias Pettersson <mattias.pettersson@era.ericsson.se> writes:
> > Is there an implementation allowing to
> > configure a router to behave that way?
> 
> KAME's rtadvd transmits RAs, but also monitors what other routers are
> sending.

Indeed, I guess routers should monitor what other routers are sending
on the same link in order to ensure they advertise same things.  But I
don't know if routers should re-transmit on other links what they
receive via RA's on one link.  I don't know, I'm wondering.

> 
> /Mattias
> 
> PS. My mailer was quite confused by your claude.castellucia@@inria.fr
> (double @!!!).

Sorry for typo! it was against spammers :-) Our sendmail didn't even
complain, dumb sendmail.

Alex



From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep  4 07:08:40 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA07837
	for <mobileip-archive@odin.ietf.org>; Tue, 4 Sep 2001 07:08:39 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id EAA11181;
	Tue, 4 Sep 2001 04:09:47 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id EAA26110;
	Tue, 4 Sep 2001 04:09:42 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f84B8k40017090
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 4 Sep 2001 04:08:46 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0/Submit) id f84B8kos017089
	for mobile-ip-dist; Tue, 4 Sep 2001 04:08:46 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f84B8b40017074;
	Tue, 4 Sep 2001 04:08:37 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id EAA26516;
	Tue, 4 Sep 2001 04:08:48 -0700 (PDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id EAA24271;
	Tue, 4 Sep 2001 04:08:47 -0700 (PDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA07733;
	Tue, 4 Sep 2001 07:07:22 -0400 (EDT)
Message-Id: <200109041107.HAA07733@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
CC: ngtrans@sunroof.eng.sun.com, ipngwg@sunroof.eng.sun.com,
        mobile-ip@sunroof.eng.sun.com
From: Internet-Drafts@ietf.org
Subject: [mobile-ip] I-D ACTION:draft-engelstad-ngtrans-6to4-v4v6-mobility-00.txt
Date: Tue, 04 Sep 2001 07:07:21 -0400
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.


	Title		: IPv4 over 6to4 and 6to4 mobility
	Author(s)	: P. Engelstad
	Filename	: draft-engelstad-ngtrans-6to4-v4v6-mobility-00.txt
	Pages		: 9
	Date		: 14-Aug-01
	
This draft outlines how a 6to4-enabled host can be provided with
transparent IPv4 and IPv6 connectivity and mobility no matter if the
host is located in a 6to4 network or is roaming an IPv4-only network.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-engelstad-ngtrans-6to4-v4v6-mobility-00.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-engelstad-ngtrans-6to4-v4v6-mobility-00.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-engelstad-ngtrans-6to4-v4v6-mobility-00.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:	<20010904070810.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-engelstad-ngtrans-6to4-v4v6-mobility-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-engelstad-ngtrans-6to4-v4v6-mobility-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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

--OtherAccess--

--NextPart--




From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep  4 07:19:45 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA08364
	for <mobileip-archive@odin.ietf.org>; Tue, 4 Sep 2001 07:19:44 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id EAA14296;
	Tue, 4 Sep 2001 04:20:48 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id EAA27320;
	Tue, 4 Sep 2001 04:20:40 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f84BJG40017199
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 4 Sep 2001 04:19:16 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0/Submit) id f84BJFvT017198
	for mobile-ip-dist; Tue, 4 Sep 2001 04:19:15 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f84BJ740017183;
	Tue, 4 Sep 2001 04:19:07 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id EAA27241;
	Tue, 4 Sep 2001 04:19:18 -0700 (PDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id EAA23525;
	Tue, 4 Sep 2001 04:19:16 -0700 (PDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA08268;
	Tue, 4 Sep 2001 07:17:50 -0400 (EDT)
Message-Id: <200109041117.HAA08268@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
CC: ngtrans@sunroof.eng.sun.com, ipng@sunroof.eng.sun.com,
        mobile-ip@sunroof.eng.sun.com
From: Internet-Drafts@ietf.org
Subject: [mobile-ip] I-D ACTION:draft-engelstad-ngtrans-mobility-requirements-00.txt
Date: Tue, 04 Sep 2001 07:17:50 -0400
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.


	Title		: Requirements to mobility while transitioning from IPv4 to IPv6
	Author(s)	: P. Engelstad
	Filename	: draft-engelstad-ngtrans-mobility-requirements-00.txt
	Pages		: 7
	Date		: 14-Aug-01
	
This document explores how layer-3 mobility can be provided to mobile
nodes that are subjects to and affected by the transition mechanisms
specified by the NGTRANS Working Group. It points out that the
combination of mobility and transition mechanisms might lead to
problems that will require a solution, and suggests requirements that
a solution should meet.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-engelstad-ngtrans-mobility-requirements-00.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-engelstad-ngtrans-mobility-requirements-00.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-engelstad-ngtrans-mobility-requirements-00.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:	<20010904071727.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-engelstad-ngtrans-mobility-requirements-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-engelstad-ngtrans-mobility-requirements-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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

--OtherAccess--

--NextPart--




From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep  4 07:20:09 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA08415
	for <mobileip-archive@odin.ietf.org>; Tue, 4 Sep 2001 07:20:08 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id EAA14444;
	Tue, 4 Sep 2001 04:21:15 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id EAA27365;
	Tue, 4 Sep 2001 04:21:05 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f84BJo40017225
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 4 Sep 2001 04:19:50 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0/Submit) id f84BJnax017224
	for mobile-ip-dist; Tue, 4 Sep 2001 04:19:49 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f84BJb40017209;
	Tue, 4 Sep 2001 04:19:37 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id EAA18544;
	Tue, 4 Sep 2001 04:19:48 -0700 (PDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id FAA16751;
	Tue, 4 Sep 2001 05:20:20 -0600 (MDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA08298;
	Tue, 4 Sep 2001 07:18:21 -0400 (EDT)
Message-Id: <200109041118.HAA08298@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
CC: ngtrans@sunroof.eng.sun.com, ipng@sunroof.eng.sun.com,
        mobile-ip@sunroof.eng.sun.com
From: Internet-Drafts@ietf.org
Subject: [mobile-ip] I-D ACTION:draft-engelstad-ngtrans-6to4-v4v6-mobility-00.txt
Date: Tue, 04 Sep 2001 07:18:21 -0400
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.


	Title		: IPv4 over 6to4 and 6to4 mobility
	Author(s)	: P. Engelstad
	Filename	: draft-engelstad-ngtrans-6to4-v4v6-mobility-00.txt
	Pages		: 9
	Date		: 14-Aug-01
	
This draft outlines how a 6to4-enabled host can be provided with
transparent IPv4 and IPv6 connectivity and mobility no matter if the
host is located in a 6to4 network or is roaming an IPv4-only network.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-engelstad-ngtrans-6to4-v4v6-mobility-00.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-engelstad-ngtrans-6to4-v4v6-mobility-00.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-engelstad-ngtrans-6to4-v4v6-mobility-00.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:	<20010904070810.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-engelstad-ngtrans-6to4-v4v6-mobility-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-engelstad-ngtrans-6to4-v4v6-mobility-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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

--OtherAccess--

--NextPart--




From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep  4 07:40:26 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA09262
	for <mobileip-archive@odin.ietf.org>; Tue, 4 Sep 2001 07:40:26 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id EAA19855;
	Tue, 4 Sep 2001 04:41:29 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id EAA20689;
	Tue, 4 Sep 2001 04:41:22 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f84Be240017426
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 4 Sep 2001 04:40:02 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0/Submit) id f84Be2xA017425
	for mobile-ip-dist; Tue, 4 Sep 2001 04:40:02 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f84Bdw40017418
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 04:39:58 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id EAA20564
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 04:40:10 -0700 (PDT)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id EAA00159
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 04:40:08 -0700 (PDT)
Received: from era-t.ericsson.se (koff.ericsson.se [147.214.173.137])
	by penguin.wise.edt.ericsson.se (8.11.0/8.10.1/WIREfire-1.3) with SMTP id f84Be0v06173;
	Tue, 4 Sep 2001 13:40:01 +0200 (MEST)
Received: from era.ericsson.se by era-t.ericsson.se (SMI-8.6/LME-DOM-2.2.5(ERA/T))
	id NAA26671; Tue, 4 Sep 2001 13:40:00 +0200
Message-ID: <3B94BD13.189D52CC@era.ericsson.se>
Date: Tue, 04 Sep 2001 13:37:55 +0200
From: Mattias Pettersson <mattias.pettersson@era.ericsson.se>
Organization: Ericsson Research
X-Mailer: Mozilla 4.77 [en] (Win95; U)
X-Accept-Language: en
MIME-Version: 1.0
To: mobile-ip@sunroof.eng.sun.com
CC: hesham.soliman@era.ericsson.se, claude.castellucia@inria.fr,
        ludovic.bellier@inria.fr, karim.el-malki@era.ericsson.se
Subject: Re: [mobile-ip] Question on HMIPv6 Dynamic MAP Discovery
References: <m3heukza84.fsf@test9.crm.mot.com>
		<3B949C14.8B2BE09A@era.ericsson.se> <m3vgizi599.fsf@test9.crm.mot.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit


Alexandru Petrescu wrote:
> 
> Mattias Pettersson <mattias.pettersson@era.ericsson.se> writes:
> > > Is there an implementation allowing to
> > > configure a router to behave that way?
> >
> > KAME's rtadvd transmits RAs, but also monitors what other routers are
> > sending.
> 
> Indeed, I guess routers should monitor what other routers are sending
> on the same link in order to ensure they advertise same things.  But I
> don't know if routers should re-transmit on other links what they
> receive via RA's on one link.  I don't know, I'm wondering.

Fundamental question, indeed. I see it as a larger-than-link-scoped RA.
This would be the same as with router renumbering, wouldn't it?

/Mattias


From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep  4 10:05:14 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16669
	for <mobileip-archive@odin.ietf.org>; Tue, 4 Sep 2001 10:05:13 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id IAA27818;
	Tue, 4 Sep 2001 08:06:02 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id HAA17216;
	Tue, 4 Sep 2001 07:05:57 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f84E4840017538
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 4 Sep 2001 07:04:08 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0/Submit) id f84E48FP017537
	for mobile-ip-dist; Tue, 4 Sep 2001 07:04:08 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f84E4440017530
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 07:04:04 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id HAA07952
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 07:04:16 -0700 (PDT)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id IAA26407
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 08:04:10 -0600 (MDT)
Received: from esealnt406.al.sw.ericsson.se (ESEALNT406.al.sw.ericsson.se [153.88.251.29])
	by penguin.wise.edt.ericsson.se (8.11.0/8.10.1/WIREfire-1.3) with SMTP id f84E4Dv28810
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 16:04:13 +0200 (MEST)
Received: FROM esealnt400.al.sw.ericsson.se BY esealnt406.al.sw.ericsson.se ; Tue Sep 04 16:04:10 2001 +0200
Received: by esealnt400 with Internet Mail Service (5.5.2653.19)
	id <NBWWDB3D>; Tue, 4 Sep 2001 16:04:02 +0200
Message-ID: <034BEFD03799D411A59F00508BDF754603008C68@esealnt448.al.sw.ericsson.se>
From: "Hesham Soliman  (ERA)" <Hesham.Soliman@era.ericsson.se>
To: "Mattias Pettersson (ERA)" <Mattias.Pettersson@era.ericsson.se>,
        mobile-ip@sunroof.eng.sun.com
Cc: "Hesham Soliman  (ERA)" <Hesham.Soliman@era.ericsson.se>,
        claude.castellucia@inria.fr, ludovic.bellier@inria.fr,
        "Karim El-Malki (ERA)" <Karim.El-Malki@era.ericsson.se>
Subject: RE: [mobile-ip] Question on HMIPv6 Dynamic MAP Discovery
Date: Tue, 4 Sep 2001 16:03:59 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

> > 
> > Mattias Pettersson <mattias.pettersson@era.ericsson.se> writes:
> > > > Is there an implementation allowing to
> > > > configure a router to behave that way?
> > >
> > > KAME's rtadvd transmits RAs, but also monitors what other routers are
> > > sending.
> > 
> > Indeed, I guess routers should monitor what other routers are sending
> > on the same link in order to ensure they advertise same things.  But I
> > don't know if routers should re-transmit on other links what they
> > receive via RA's on one link.  I don't know, I'm wondering.
> 
> Fundamental question, indeed. I see it as a larger-than-link-scoped RA.
> This would be the same as with router renumbering, wouldn't it?
> 
	=> Yes I think it is a very similar concept. In addition, the draft says that
	the advertisement SHOULD be secured to guarantee that no malicious
	nodes will provide false information. 
	The router renumbering mechanism can also be used as per the draft. 

	BTW, since we're discussing the MAP discovery, I'd like to point out 
	that the 8n alignment in the draft is not correct (for the MAP option)
	we will fix that in the next revision, but I'd rather wait for more substantial 
	issues before we submit the next revision. 

	Hesham


From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep  4 11:32:02 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19421
	for <mobileip-archive@odin.ietf.org>; Tue, 4 Sep 2001 11:32:02 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA21476;
	Tue, 4 Sep 2001 08:32:54 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id IAA03305;
	Tue, 4 Sep 2001 08:32:32 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f84FVU40017641
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 4 Sep 2001 08:31:30 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0/Submit) id f84FVUjk017640
	for mobile-ip-dist; Tue, 4 Sep 2001 08:31:30 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f84FVQ40017633
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 08:31:26 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id IAA07101
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 08:31:27 -0700 (PDT)
Received: from megisto-sql1.megisto.com ([63.113.114.132])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id JAA09487
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 09:31:21 -0600 (MDT)
Received: by megisto-sql1.megisto.com with Internet Mail Service (5.5.2650.21)
	id <RAY8HSL2>; Tue, 4 Sep 2001 11:30:08 -0400
Message-ID: <CD8355C7E19ED411BD5F00508BB0D19D698003@megisto-sql1.megisto.com>
From: Phil Roberts <PRoberts@MEGISTO.com>
To: "'mobile-ip@sunroof.eng.sun.com'" <mobile-ip@sunroof.eng.sun.com>
Subject: RE: [mobile-ip] FW: draft-ietf-mobileip-mier-07.txt
Date: Tue, 4 Sep 2001 11:30:07 -0400 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

I've received zero feedback on this.  Let me try another tack.

I propose we integrate this document into 2002bis.  It would allow
us to have a normative reference for all future documents using
extensions, 2002bis will be the primary standards document going forward,
and is in the process of being revised now.

Is the WG okay with this?  Please post comments to the list.

Thanks,
Phil


> -----Original Message-----
> From: Phil Roberts [mailto:PRoberts@MEGISTO.com]
> Sent: Thursday, August 23, 2001 4:34 PM
> To: 'mobile-ip@sunroof.eng.sun.com'
> Subject: [mobile-ip] FW: draft-ietf-mobileip-mier-07.txt
> 
> 
> Hi folks,
> 
>     we've received this feedback from the IESG on the MIER draft.
> Please provide comments, especially on the first set of options.
> 
> Phil
> 
> 
> --------------------
> General comment. This ID seems to be of rather limited usefulness as a
> standalone RFC. Is it really needed? This document seems to update RFC
> 2002, but is informational. This can be remedied by:
> 
>   - making this standards track (seems overkill, since it doesn't
>     actually define an option, and hence, doesn't define anything
>     anyone needs to implement, from what I can tell)
>   - merge it in with 2002bis (which is being revised right now anyway)
>   - merge this document with GNAI, since the GNAI document is a
>     specific case where use of MIER might make sense. 
>   - take out the MUST/SHOULDs and make it clear that this document is
>     only proposing an approach to encoding options, and that future
>     options writers should consider the issues raised when designing
>     their options. NOte: if this approach is used, other documents
>     (e.g., draft-ietf-mobileip-gnaie-04.txt) shouldn't have normative
>     references to this document. At present, gnai appears to do just
>     that.
> 
> For example:
> 
> > MIER describes a new extension 
> >     structure to Mobile IP to make the extensions far more 
> >     extensible.     
> 
> Could be rewritten as:
> 
>      MIER describes a way of encoding extensions that make it possible
>      to conserve MIP options in some cases. Authors of future options
>      should consider the issues raised in this document when designing
>      new options.
> 
> There are several other places in the document where the langauge
> could be toned down and made more neutral.
>      
> >     It is in the interest of the Mobile IP WG to conserve the 
> >     usage of the type field since we see many drafts proposing 
> >     new extensions for Mobile IP. Therefore there is a real 
> 
> There is an alternate approach, one that seems to be working in
> practice, and has other benefits. Don't allow IANA to assign options
> until there is significant support for an option, i.e, via something
> like "IETF consensus" [RFC 2434].  This approach also has the
> advantage that it discourages the use of many options anyway, a
> generaly desirable feature.  Usage of many options tends to negatively
> impact interoperability.
> 
> Finally, looking at the IANA pages, it does not appear that options
> are being used at a significant rate and that exhaustion of the space
> is serious issue at present.
> 
> 
> > 1.0 Introduction
> > 
> >     The type field in the Mobile IP extension structure can support
> >     upto 255 (skippable and not skippable) uniquely identifiable
> >     extensions. With new developments/additions to Mobile IP
> >     there is a strong possibility that the available space will 
> >     run out.
> 
> What  evidence is there that this is true at present?
> 
> >     Mobile IP Extensions Rationalization (MIER) describes a 
> >     new extension structure to solve this problem. MIER strategy
> >     is to initially aggregate certain types of extensions (e.g,
> >     NAI) and sub types to identify the precise extension (example
> >     MN/User NAI, HA NAI etc). This will greatly reduce the usage
> >     of the type field. 
> 
> Last sentence seems a bit too strong. Better to say "This may reduce
> the usage of the type field in some cases".
> 
> > 2.2 New Mobile IP Extension format
> > 
> >     This draft proposes the following  two structures for Mobile IP
> >     extensions to be carried in the Mobile IP control messages.
> >     Since the new extension structures will cause an efficient
> >     usage of the extension type space, it is strongly recommended
> >     that all the new proposals for the Mobile IP WG that have new 
> >     extensions SHOULD follow this format. 
> 
> SHOULD wording seems a bit strong. Encoding options in this way makes
> sense in *some* cases, but it is not clear (to me) that it does so in
> even the majority of cases. It would be sufficient to say option
> writers should consider whether the structure defined here makes sense
> when a new option is defined. Saying they SHOULD follow it is too
> strong.
> 
> > 2.2.1 Long Extension Format
> 
> In the absence of a specific proposed need for a long option, I don't
> see the value in defining it. Moreover, will MIP *ever* define any
> more non-skippable options? Seems like doing so would be bad for
> interoperating with the installed base (which won't understand any
> newly defined options) . If that is the case, why define now? One can
> always define a long format later should it be deemed necessary.
> 
> > 2.2.2 Short Extension Format
> 
> This format makes sense for some types of options (GNAI would seem to
> be one). It does not make sense for others. For example, of the
> existing MIP options, how many would it actually make sense to encode
> in this fashion?
> 
> >     Sub-Type  is a unique number given to each member in the
> >               aggregated type.  Sub-Type values between of 
> 200 through
> >               255 are reserved for future use and standardization.
> 
> The semantics of this field are dependent on the actual option; it
> make no sense to say anything about reserving values in the general
> case. It *might* make sense to say something like that in the case of
> a specific option, but that would be the job of that specific option.
> 
> If this document is to be published as a standalone document:
> 
> Needs security considerations section.
> 
> Would be good to have an IANA considerations section; I would expect
> it to say "There are no IANA Actions in this document", but that sort
> of depends on resolution of the first point.
> 


From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep  4 11:38:15 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19596
	for <mobileip-archive@odin.ietf.org>; Tue, 4 Sep 2001 11:38:14 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id JAA16691;
	Tue, 4 Sep 2001 09:39:13 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id IAA04692;
	Tue, 4 Sep 2001 08:39:09 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f84FcH40017678
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 4 Sep 2001 08:38:17 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0/Submit) id f84FcHBK017677
	for mobile-ip-dist; Tue, 4 Sep 2001 08:38:17 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f84FcD40017670
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 08:38:13 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id IAA08308
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 08:38:21 -0700 (PDT)
Received: from sj-msg-core-3.cisco.com (sj-msg-core-3.cisco.com [171.70.157.152])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id JAA16828
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 09:38:53 -0600 (MDT)
Received: from mira-sjc5-7.cisco.com (mira-sjc5-7.cisco.com [171.71.163.27])
	by sj-msg-core-3.cisco.com (8.11.3/8.9.1) with ESMTP id f84Fa9n09013;
	Tue, 4 Sep 2001 08:36:14 -0700 (PDT)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-7.cisco.com (Mirapoint)
	with ESMTP id ABD01902;
	Tue, 4 Sep 2001 08:38:03 -0700 (PDT)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id IAA23974; Tue, 4 Sep 2001 08:38:03 -0700 (PDT)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15252.62811.108950.296379@thomasm-u1.cisco.com>
Date: Tue, 4 Sep 2001 08:38:03 -0700 (PDT)
To: mobile-ip@sunroof.eng.sun.com
Cc: "Mattias Pettersson (ERA)" <Mattias.Pettersson@era.ericsson.se>,
        "Hesham Soliman  (ERA)" <Hesham.Soliman@era.ericsson.se>,
        claude.castellucia@inria.fr, ludovic.bellier@inria.fr,
        "Karim El-Malki (ERA)" <Karim.El-Malki@era.ericsson.se>
Subject: RE: [mobile-ip] Question on HMIPv6 Dynamic MAP Discovery
In-Reply-To: <034BEFD03799D411A59F00508BDF754603008C68@esealnt448.al.sw.ericsson.se>
References: <034BEFD03799D411A59F00508BDF754603008C68@esealnt448.al.sw.ericsson.se>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hesham Soliman  (ERA) writes:
 > > > 
 > > > Mattias Pettersson <mattias.pettersson@era.ericsson.se> writes:
 > > > > > Is there an implementation allowing to
 > > > > > configure a router to behave that way?
 > > > >
 > > > > KAME's rtadvd transmits RAs, but also monitors what other routers are
 > > > > sending.
 > > > 
 > > > Indeed, I guess routers should monitor what other routers are sending
 > > > on the same link in order to ensure they advertise same things.  But I
 > > > don't know if routers should re-transmit on other links what they
 > > > receive via RA's on one link.  I don't know, I'm wondering.
 > > 
 > > Fundamental question, indeed. I see it as a larger-than-link-scoped RA.
 > > This would be the same as with router renumbering, wouldn't it?
 > > 
 > 	=> Yes I think it is a very similar concept. In addition, the draft says that
 > 	the advertisement SHOULD be secured to guarantee that no malicious
 > 	nodes will provide false information. 
 > 	The router renumbering mechanism can also be used as per the draft. 

     How do you do that?

	    Mike


From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep  4 13:07:37 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21644
	for <mobileip-archive@odin.ietf.org>; Tue, 4 Sep 2001 13:07:37 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA13263;
	Tue, 4 Sep 2001 10:08:33 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id KAA28380;
	Tue, 4 Sep 2001 10:08:25 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f84H7K40017769
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 4 Sep 2001 10:07:20 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0/Submit) id f84H7KFU017768
	for mobile-ip-dist; Tue, 4 Sep 2001 10:07:20 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from heliopolis.eng.sun.com (bigbang.Eng.Sun.COM [152.70.8.30])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f84H7H40017761
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 10:07:17 -0700 (PDT)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.eng.sun.com (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id KAA06104
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 10:07:29 -0700 (PDT)
Message-Id: <200109041707.KAA06104@heliopolis.eng.sun.com>
Date: Tue, 4 Sep 2001 10:07:29 -0700 (PDT)
From: James Kempf <James.Kempf@Sun.COM>
Subject: RE: [mobile-ip] FW: draft-ietf-mobileip-mier-07.txt
To: mobile-ip@sunroof.eng.sun.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: TFiwxm4tbknx9fLED9xbZw==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

I agree with this.

		jak
		
>From: Phil Roberts <PRoberts@MEGISTO.com>
>To: "'mobile-ip@sunroof.eng.sun.com'" <mobile-ip@sunroof.eng.sun.com>
>Subject: RE: [mobile-ip] FW: draft-ietf-mobileip-mier-07.txt
>Date: Tue, 4 Sep 2001 11:30:07 -0400 
>
>I've received zero feedback on this.  Let me try another tack.
>
>I propose we integrate this document into 2002bis.  It would allow
>us to have a normative reference for all future documents using
>extensions, 2002bis will be the primary standards document going forward,
>and is in the process of being revised now.
>
>Is the WG okay with this?  Please post comments to the list.
>
>Thanks,
>Phil
>
>
>> -----Original Message-----
>> From: Phil Roberts [mailto:PRoberts@MEGISTO.com]
>> Sent: Thursday, August 23, 2001 4:34 PM
>> To: 'mobile-ip@sunroof.eng.sun.com'
>> Subject: [mobile-ip] FW: draft-ietf-mobileip-mier-07.txt
>> 
>> 
>> Hi folks,
>> 
>>     we've received this feedback from the IESG on the MIER draft.
>> Please provide comments, especially on the first set of options.
>> 
>> Phil
>> 
>> 
>> --------------------
>> General comment. This ID seems to be of rather limited usefulness as a
>> standalone RFC. Is it really needed? This document seems to update RFC
>> 2002, but is informational. This can be remedied by:
>> 
>>   - making this standards track (seems overkill, since it doesn't
>>     actually define an option, and hence, doesn't define anything
>>     anyone needs to implement, from what I can tell)
>>   - merge it in with 2002bis (which is being revised right now anyway)
>>   - merge this document with GNAI, since the GNAI document is a
>>     specific case where use of MIER might make sense. 
>>   - take out the MUST/SHOULDs and make it clear that this document is
>>     only proposing an approach to encoding options, and that future
>>     options writers should consider the issues raised when designing
>>     their options. NOte: if this approach is used, other documents
>>     (e.g., draft-ietf-mobileip-gnaie-04.txt) shouldn't have normative
>>     references to this document. At present, gnai appears to do just
>>     that.
>> 
>> For example:
>> 
>> > MIER describes a new extension 
>> >     structure to Mobile IP to make the extensions far more 
>> >     extensible.     
>> 
>> Could be rewritten as:
>> 
>>      MIER describes a way of encoding extensions that make it possible
>>      to conserve MIP options in some cases. Authors of future options
>>      should consider the issues raised in this document when designing
>>      new options.
>> 
>> There are several other places in the document where the langauge
>> could be toned down and made more neutral.
>>      
>> >     It is in the interest of the Mobile IP WG to conserve the 
>> >     usage of the type field since we see many drafts proposing 
>> >     new extensions for Mobile IP. Therefore there is a real 
>> 
>> There is an alternate approach, one that seems to be working in
>> practice, and has other benefits. Don't allow IANA to assign options
>> until there is significant support for an option, i.e, via something
>> like "IETF consensus" [RFC 2434].  This approach also has the
>> advantage that it discourages the use of many options anyway, a
>> generaly desirable feature.  Usage of many options tends to negatively
>> impact interoperability.
>> 
>> Finally, looking at the IANA pages, it does not appear that options
>> are being used at a significant rate and that exhaustion of the space
>> is serious issue at present.
>> 
>> 
>> > 1.0 Introduction
>> > 
>> >     The type field in the Mobile IP extension structure can support
>> >     upto 255 (skippable and not skippable) uniquely identifiable
>> >     extensions. With new developments/additions to Mobile IP
>> >     there is a strong possibility that the available space will 
>> >     run out.
>> 
>> What  evidence is there that this is true at present?
>> 
>> >     Mobile IP Extensions Rationalization (MIER) describes a 
>> >     new extension structure to solve this problem. MIER strategy
>> >     is to initially aggregate certain types of extensions (e.g,
>> >     NAI) and sub types to identify the precise extension (example
>> >     MN/User NAI, HA NAI etc). This will greatly reduce the usage
>> >     of the type field. 
>> 
>> Last sentence seems a bit too strong. Better to say "This may reduce
>> the usage of the type field in some cases".
>> 
>> > 2.2 New Mobile IP Extension format
>> > 
>> >     This draft proposes the following  two structures for Mobile IP
>> >     extensions to be carried in the Mobile IP control messages.
>> >     Since the new extension structures will cause an efficient
>> >     usage of the extension type space, it is strongly recommended
>> >     that all the new proposals for the Mobile IP WG that have new 
>> >     extensions SHOULD follow this format. 
>> 
>> SHOULD wording seems a bit strong. Encoding options in this way makes
>> sense in *some* cases, but it is not clear (to me) that it does so in
>> even the majority of cases. It would be sufficient to say option
>> writers should consider whether the structure defined here makes sense
>> when a new option is defined. Saying they SHOULD follow it is too
>> strong.
>> 
>> > 2.2.1 Long Extension Format
>> 
>> In the absence of a specific proposed need for a long option, I don't
>> see the value in defining it. Moreover, will MIP *ever* define any
>> more non-skippable options? Seems like doing so would be bad for
>> interoperating with the installed base (which won't understand any
>> newly defined options) . If that is the case, why define now? One can
>> always define a long format later should it be deemed necessary.
>> 
>> > 2.2.2 Short Extension Format
>> 
>> This format makes sense for some types of options (GNAI would seem to
>> be one). It does not make sense for others. For example, of the
>> existing MIP options, how many would it actually make sense to encode
>> in this fashion?
>> 
>> >     Sub-Type  is a unique number given to each member in the
>> >               aggregated type.  Sub-Type values between of 
>> 200 through
>> >               255 are reserved for future use and standardization.
>> 
>> The semantics of this field are dependent on the actual option; it
>> make no sense to say anything about reserving values in the general
>> case. It *might* make sense to say something like that in the case of
>> a specific option, but that would be the job of that specific option.
>> 
>> If this document is to be published as a standalone document:
>> 
>> Needs security considerations section.
>> 
>> Would be good to have an IANA considerations section; I would expect
>> it to say "There are no IANA Actions in this document", but that sort
>> of depends on resolution of the first point.
>> 



From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep  4 15:20:15 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25071
	for <mobileip-archive@odin.ietf.org>; Tue, 4 Sep 2001 15:20:14 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id NAA25712;
	Tue, 4 Sep 2001 13:20:43 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id MAA09724;
	Tue, 4 Sep 2001 12:20:39 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f84JJV40018254
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 4 Sep 2001 12:19:31 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0/Submit) id f84JJVhB018253
	for mobile-ip-dist; Tue, 4 Sep 2001 12:19:31 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from heliopolis.eng.sun.com (bigbang.Eng.Sun.COM [152.70.8.30])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f84JJS40018246
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 12:19:28 -0700 (PDT)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.eng.sun.com (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id MAA12637
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 12:19:40 -0700 (PDT)
Message-Id: <200109041919.MAA12637@heliopolis.eng.sun.com>
Date: Tue, 4 Sep 2001 12:19:39 -0700 (PDT)
From: James Kempf <James.Kempf@Sun.COM>
Subject: RE: [mobile-ip] Low Latency Issue: Where to Run the Reverse Tunne l?
To: mobile-ip@sunroof.eng.sun.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: gJ6+l0PUHjNl3DCiD3Lefw==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Ok, well, it seems like this issue hasn't stirred alot of comment. In
the interest of pushing the draft forward, I'd like to make the following
proposal. I think this will address Ajoy's comment about tunneling
compressed packets or PPP to the old FA, and also the comment in the
original issue summary about how to accommodate route optimization.

The proposal involves modifying the flag bits to indicate whether
the reverse tunnel should be terminated at the old FA or at the HA,
and whether route optimization is in effect.

Currently, we have 4 flag bits concerned with tunneling: M for minimal 
encapsulation supported, G for GRE encapsulation supported, T for reverse tunnel 
supported. These flag bits occur in both the Handoff Request and Handoff Reply.

I'd like to propose that we modify the tunneling flags as follows:

M - MN requested minimal encapsulation, use it in any tunnel with FA or HA
G - MN requested GRE encapsulation, use it in any tunnel with FA or HA
    (must be accompanied  by the GRE Key Extension if GRE security in 
     effect)
H -  MN requested reverse tunnel to HA, perform reverse tunnel regardless
     of egress filtering status on new subnet (the MN may be using 
     a private home address, for example). 
O - old FA is performing optimizations on MNs traffic (compression, 
    PPP, etc.), tunnel through the old FA regardless of egress filtering
     status on new subnet.
R - Route optimization is in effect and the MN is using CoA as the source
    address. MN's old CoA included in the message instead of the MN's 
    home address. The O bit MUST also be set.
    
The reverse tunnel termination point would be decided by the following
algorithm:

  If the H flag is set, the new FA MUST reverse tunnel to the HA regardless of
  the egress filtering status on the new subnet. This is because the
  MN requested reverse tunneling.
  
  If the O flag is set, the old FA is performing optimizations, such
  as compression, and therefore the new FA MUST reverse tunnel to
  the old FA regardless of the egress filtering status because the
  old FA must perform processing before the packets can be sent. This
  flag MUST also be set if the R flag is on, indicating that the 
  MN is performing route optimization.
  
  If neither the H nor the O flag are set, then the new FA can reverse tunnel
  to the HA, reverse tunnel to the old FA, or it can simply route packets
  directly onto its subnet if egress filtering is not on.
  
Note that if the new FA does NOT want to perform reverse tunneling but
the MN did not request reverse tunneling, the H flag MUST NOT be set.
The new FA indicates its unwillingness to reverse tunnel by 
a tunnel lifetime of zero in the Handoff Request or Handoff Reply, this 
indication applies to forward tunneling also.

If the R flag is set, the old FA sends the MN's old Care of Address
in place of the MN's Home Address, since the source address on
outgoing packets will be the MN's old Care of Address. The MN's 
HA address is also sent.

Comments?

			jak


  
  
  



From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep  4 15:31:16 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25289
	for <mobileip-archive@odin.ietf.org>; Tue, 4 Sep 2001 15:31:15 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA28447;
	Tue, 4 Sep 2001 12:32:20 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id MAA12993;
	Tue, 4 Sep 2001 12:32:14 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f84JTp40018321
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 4 Sep 2001 12:29:51 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0/Submit) id f84JTpUH018320
	for mobile-ip-dist; Tue, 4 Sep 2001 12:29:51 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f84JTm40018313
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 12:29:48 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id MAA12270
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 12:29:59 -0700 (PDT)
Received: from motgate.mot.com (motgate.mot.com [129.188.136.100])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id MAA12401
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 12:29:58 -0700 (PDT)
Received: [from pobox4.mot.com (pobox4.mot.com [10.64.251.243]) by motgate.mot.com (motgate 2.1) with ESMTP id MAA01593 for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 12:29:56 -0700 (MST)]
Received: [from il27exb01.cig.mot.com (il27exb01.cig.mot.com [136.182.15.100]) by pobox4.mot.com (MOT-pobox4 2.0) with ESMTP id MAA14433 for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 12:29:56 -0700 (MST)]
Received: by il27exb01.cig.mot.com with Internet Mail Service (5.5.2654.52)
	id <SCC2K5KH>; Tue, 4 Sep 2001 14:29:56 -0500
Message-ID: <A5B4C9A2AD89D411AB3E009027B0DA1E3B20CE@IL27EXM09.cig.mot.com>
From: Singh Ajoy-ASINGH1 <ASINGH1@motorola.com>
To: "'mobile-ip@sunroof.eng.sun.com'" <mobile-ip@sunroof.eng.sun.com>
Subject: RE: [mobile-ip] Low Latency Issue: Where to Run the Reverse Tunne
	 l?
Date: Tue, 4 Sep 2001 14:29:51 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2654.52)
Content-Type: text/plain
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Looks good to me. 
regards,
ajoy 

-----Original Message-----
From: James Kempf [mailto:James.Kempf@sun.com]
Sent: Tuesday, September 04, 2001 2:20 PM
To: mobile-ip@sunroof.eng.sun.com
Subject: RE: [mobile-ip] Low Latency Issue: Where to Run the Reverse
Tunne l?


Ok, well, it seems like this issue hasn't stirred alot of comment. In
the interest of pushing the draft forward, I'd like to make the following
proposal. I think this will address Ajoy's comment about tunneling
compressed packets or PPP to the old FA, and also the comment in the
original issue summary about how to accommodate route optimization.

The proposal involves modifying the flag bits to indicate whether
the reverse tunnel should be terminated at the old FA or at the HA,
and whether route optimization is in effect.

Currently, we have 4 flag bits concerned with tunneling: M for minimal 
encapsulation supported, G for GRE encapsulation supported, T for reverse tunnel 
supported. These flag bits occur in both the Handoff Request and Handoff Reply.

I'd like to propose that we modify the tunneling flags as follows:

M - MN requested minimal encapsulation, use it in any tunnel with FA or HA
G - MN requested GRE encapsulation, use it in any tunnel with FA or HA
    (must be accompanied  by the GRE Key Extension if GRE security in 
     effect)
H -  MN requested reverse tunnel to HA, perform reverse tunnel regardless
     of egress filtering status on new subnet (the MN may be using 
     a private home address, for example). 
O - old FA is performing optimizations on MNs traffic (compression, 
    PPP, etc.), tunnel through the old FA regardless of egress filtering
     status on new subnet.
R - Route optimization is in effect and the MN is using CoA as the source
    address. MN's old CoA included in the message instead of the MN's 
    home address. The O bit MUST also be set.
    
The reverse tunnel termination point would be decided by the following
algorithm:

  If the H flag is set, the new FA MUST reverse tunnel to the HA regardless of
  the egress filtering status on the new subnet. This is because the
  MN requested reverse tunneling.
  
  If the O flag is set, the old FA is performing optimizations, such
  as compression, and therefore the new FA MUST reverse tunnel to
  the old FA regardless of the egress filtering status because the
  old FA must perform processing before the packets can be sent. This
  flag MUST also be set if the R flag is on, indicating that the 
  MN is performing route optimization.
  
  If neither the H nor the O flag are set, then the new FA can reverse tunnel
  to the HA, reverse tunnel to the old FA, or it can simply route packets
  directly onto its subnet if egress filtering is not on.
  
Note that if the new FA does NOT want to perform reverse tunneling but
the MN did not request reverse tunneling, the H flag MUST NOT be set.
The new FA indicates its unwillingness to reverse tunnel by 
a tunnel lifetime of zero in the Handoff Request or Handoff Reply, this 
indication applies to forward tunneling also.

If the R flag is set, the old FA sends the MN's old Care of Address
in place of the MN's Home Address, since the source address on
outgoing packets will be the MN's old Care of Address. The MN's 
HA address is also sent.

Comments?

			jak


  
  
  


From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep  4 15:56:37 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26056
	for <mobileip-archive@odin.ietf.org>; Tue, 4 Sep 2001 15:56:36 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA10224;
	Tue, 4 Sep 2001 12:57:27 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id MAA20067;
	Tue, 4 Sep 2001 12:56:09 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f84Jrl40018395
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 4 Sep 2001 12:53:47 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0/Submit) id f84Jrlgx018394
	for mobile-ip-dist; Tue, 4 Sep 2001 12:53:47 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f84Jrh40018387
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 12:53:43 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id MAA11448
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 12:53:54 -0700 (PDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id NAA21490
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 13:53:49 -0600 (MDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id MAA28628
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 12:53:53 -0700 (PDT)
X-Delivered-For: <mobile-ip@sunroof.eng.sun.com>
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f84Jrqu01868
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 12:53:52 -0700
X-mProtect:  Tue, 4 Sep 2001 12:53:52 -0700 Nokia Silicon Valley Messaging Protection
Received: from Icharliep-1.iprg.nokia.com (205.226.22.18, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpdHvYL70; Tue, 04 Sep 2001 12:53:50 PDT
Message-ID: <3B9530C6.9C6AFBF2@iprg.nokia.com>
Date: Tue, 04 Sep 2001 12:51:34 -0700
From: Charlie Perkins <charliep@iprg.nokia.com>
Organization: Nokia
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Mobile IP Working Group Mailing List <mobile-ip@sunroof.eng.sun.com>
Subject: [mobile-ip] Coexistence with other uses for routing header
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hello folks,

In response to a question about how Mobile IPv6 uses routing
headers vs. other uses, I propose inserted the following paragraph
into the revised text, as the last paragraph of section 8.9.

Comments or additional clarifying text will be appreciated.

I put this as a SHOULD, because of the uncertainty about future
definitions of routing headers.

Regards,
Charlie P.

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

It is possible that a correspondent node, having no knowledge of
the mobile node's care-of address, would still (for reasons unspecified
here but not necessarily related to mobility) attempt use a routing
header to deliver a packet to the mobile node's home address.
If the correspondent node accepts a Binding Update
and creates a Binding Cache entry for the mobile node, then
in that case, the correspondent node SHOULD put the mobile
node's care-of address as the last intermediate node address
of the routing header, following all other intermediate node
addresses that would have already been in the routing header
before the creation of the Binding Cache entry for the care-of
address.


From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep  4 17:25:37 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA28454
	for <mobileip-archive@odin.ietf.org>; Tue, 4 Sep 2001 17:25:37 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id PAA04538;
	Tue, 4 Sep 2001 15:26:29 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id OAA23980;
	Tue, 4 Sep 2001 14:26:25 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f84LPI40018622
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 4 Sep 2001 14:25:18 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0/Submit) id f84LPIkc018621
	for mobile-ip-dist; Tue, 4 Sep 2001 14:25:18 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f84LPE40018614
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 14:25:14 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id OAA17368
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 14:25:26 -0700 (PDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id PAA27736
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 15:25:58 -0600 (MDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id OAA05725;
	Tue, 4 Sep 2001 14:25:24 -0700 (PDT)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f84LPNX03057;
	Tue, 4 Sep 2001 14:25:23 -0700
X-mProtect:  Tue, 4 Sep 2001 14:25:23 -0700 Nokia Silicon Valley Messaging Protection
Received: from Icharliep-1.iprg.nokia.com (205.226.22.18, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpdRHwReW; Tue, 04 Sep 2001 14:25:20 PDT
Message-ID: <3B954578.999A4016@iprg.nokia.com>
Date: Tue, 04 Sep 2001 14:19:52 -0700
From: Charlie Perkins <charliep@iprg.nokia.com>
Organization: Nokia
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Lars Henrik Petander <lpetande@tml.hut.fi>
CC: Venkata Jagana <jagana@us.ibm.com>,
        Mobile IP Working Group Mailing List <mobile-ip@sunroof.eng.sun.com>
Subject: [mobile-ip] Re: 
References: <200109042044.NAA11378@charliep.iprg.nokia.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hello Lars,

Charles Perkins wrote:

> Date: Thu, 2 Aug 2001 21:10:51 +0300 (EET DST)
> From: Lars Henrik Petander <lpetande@tml.hut.fi>

> When implementing DHAAD, we noticed that the resending policy for the
> DHAAD request is not specified in draft 14. However, it probably should be
> specified, since the initial request or reply can easily get lost if MN
> moves.

O.K.  Here is my proposed text:


     If, after a mobile node transmits a Home Agent Address
     Discovery Request message to the Home Agents Anycast address,
     it does not receive a corresponding Home Agent Address
     Discovery Reply message within INITIAL_DHAAD_TIMEOUT
     seconds, the mobile node MAY retransmit the same
     Request message to the same anycast address.  This
     retransmission MAY be repeated up to a maximum
     of DHAAD_RETRIES attempts.  Each retransmission MUST
     be delayed by twice the time interval of the previous
     retransmission.

> Regarding the processing of the home address option section 8.1 says:
>    "... However, any actual modifications
>    to the Source Address field in the packet's IPv6 header MUST not
>    be performed until after all processing of other options contained
>    in the same Destination Options extension header is completed."
>
> Normally destination options are handled independently of each other in
> the order they are in the packet, which allows a clean design for
> destination option processing. Unfortuantely draft section 8.1 breaks this
> and requires the handler to go back to the home address option after
> processing all other destination options in the header. I wonder, whether
> this behaviour is really worth the complications it causes.

I agree that the specification needs to be changed.  Here is some
proposed text, which basically puts two sentences together.  The
second sentence specifies the required effect, and the new combined
sentence states that the required effect must be made to happen, but
doesn't say just how to make it happen.

     However, any actual modifications to the Source Address field in the
     packet's IPv6 header MUST be carried out in such a fashion that
     further processing of such a packet after all IPv6 options processing
     (e.g., at the transport layer)
     does not need to know that the original Source Address was a
     care-of address, or that the Home Address option was used in the packet.

Comments or suggestions for improvement will be appreciated.

Regards,
Charlie P.




From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep  4 17:56:27 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29086
	for <mobileip-archive@odin.ietf.org>; Tue, 4 Sep 2001 17:56:26 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id PAA26865;
	Tue, 4 Sep 2001 15:57:33 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id OAA19619;
	Tue, 4 Sep 2001 14:57:28 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f84LuC40018736
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 4 Sep 2001 14:56:12 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0/Submit) id f84LuBdb018735
	for mobile-ip-dist; Tue, 4 Sep 2001 14:56:11 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from jurassic.eng.sun.com (jurassic [129.146.81.36] (may be forged))
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f84Lu840018728
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 14:56:08 -0700 (PDT)
Received: from istanbul (istanbul.Eng.Sun.COM [129.146.86.247])
	by jurassic.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with SMTP id f84LiU9d242322
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 14:45:08 -0700 (PDT)
Message-Id: <200109042145.f84LiU9d242322@jurassic.eng.sun.com>
Date: Tue, 4 Sep 2001 14:44:52 -0700 (PDT)
From: Alper Yegin <Alper.Yegin@eng.sun.com>
Subject: Re: [mobile-ip] Coexistence with other uses for routing header
To: mobile-ip@sunroof.eng.sun.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: /Ygsc07RskaD8muh8phzaA==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4_37 SunOS 5.8.1 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Hi Charlie,

I think it is a good idea to put some effort to see/get route optimization work 
in the existence of routing headers.

> Hello folks,
> 
> In response to a question about how Mobile IPv6 uses routing
> headers vs. other uses, I propose inserted the following paragraph
> into the revised text, as the last paragraph of section 8.9.
> 
> Comments or additional clarifying text will be appreciated.
> 
> I put this as a SHOULD, because of the uncertainty about future
> definitions of routing headers.
> 
> Regards,
> Charlie P.
> 
> ===========================================================================
> 
> It is possible that a correspondent node, having no knowledge of
> the mobile node's care-of address, would still (for reasons unspecified
> here but not necessarily related to mobility) attempt use a routing
> header to deliver a packet to the mobile node's home address.
> If the correspondent node accepts a Binding Update
> and creates a Binding Cache entry for the mobile node, then
> in that case, the correspondent node SHOULD put the mobile
> node's care-of address as the last intermediate node address
> of the routing header, following all other intermediate node
> addresses that would have already been in the routing header
> before the creation of the Binding Cache entry for the care-of
> address.

If we are going to make route optimization work with other uses of routing 
headers, why not make it work even when Home Address of a mobile node is not 
only the final destination of a packet, but also maybe an intermediate hop?

This correspondent node knows that the only way to reach to Home_Address is to 
send the packet through Care_of_Address. Whether Home_Address is the final 
destination of a packet with routing header, or an intermediate hop, replacing 
"Home_Address" with "Care_of_Address + Home_Address" would ensure this packet 
goes to/through "mobile node".

We should also clarify in the paragraph that this formula applies only to 
Routing Header Type 0. 

Regards,

alper



From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep  4 18:00:53 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29180
	for <mobileip-archive@odin.ietf.org>; Tue, 4 Sep 2001 18:00:52 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id PAA11303;
	Tue, 4 Sep 2001 15:02:02 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id PAA20964;
	Tue, 4 Sep 2001 15:01:52 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f84M0i40018771
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 4 Sep 2001 15:00:44 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0/Submit) id f84M0i26018770
	for mobile-ip-dist; Tue, 4 Sep 2001 15:00:44 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f84M0e40018763
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 15:00:40 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id PAA04805
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 15:00:53 -0700 (PDT)
Received: from albatross-ext.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id QAA29374
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 16:00:47 -0600 (MDT)
Received: from esealnt462.al.sw.ericsson.se (ESEALNT462.al.sw.ericsson.se [153.88.251.62])
	by albatross.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id f84M0oK19843
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 00:00:50 +0200 (MEST)
Received: FROM esealnt400.al.sw.ericsson.se BY esealnt462.al.sw.ericsson.se ; Wed Sep 05 00:00:49 2001 +0200
Received: by esealnt400 with Internet Mail Service (5.5.2653.19)
	id <NBWWDKJH>; Wed, 5 Sep 2001 00:00:48 +0200
Message-ID: <034BEFD03799D411A59F00508BDF754603008C69@esealnt448.al.sw.ericsson.se>
From: "Hesham Soliman  (ERA)" <Hesham.Soliman@era.ericsson.se>
To: "'Michael Thomas'" <mat@cisco.com>, mobile-ip@sunroof.eng.sun.com
Cc: "Mattias Pettersson (ERA)" <Mattias.Pettersson@era.ericsson.se>,
        "Hesham Soliman  (ERA)" <Hesham.Soliman@era.ericsson.se>,
        claude.castellucia@inria.fr, ludovic.bellier@inria.fr,
        "Karim El-Malki (ERA)" <Karim.El-Malki@era.ericsson.se>
Subject: RE: [mobile-ip] Question on HMIPv6 Dynamic MAP Discovery
Date: Wed, 5 Sep 2001 00:00:39 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

>  > > > Mattias Pettersson <mattias.pettersson@era.ericsson.se> writes:
>  > > > > > Is there an implementation allowing to
>  > > > > > configure a router to behave that way?
>  > > > >
>  > > > > KAME's rtadvd transmits RAs, but also monitors what other routers are
>  > > > > sending.
>  > > > 
>  > > > Indeed, I guess routers should monitor what other routers are sending
>  > > > on the same link in order to ensure they advertise same things.  But I
>  > > > don't know if routers should re-transmit on other links what they
>  > > > receive via RA's on one link.  I don't know, I'm wondering.
>  > > 
>  > > Fundamental question, indeed. I see it as a larger-than-link-scoped RA.
>  > > This would be the same as with router renumbering, wouldn't it?
>  > > 
>  > 	=> Yes I think it is a very similar concept. In addition, the draft says that
>  > 	the advertisement SHOULD be secured to guarantee that no malicious
>  > 	nodes will provide false information. 
>  > 	The router renumbering mechanism can also be used as per the draft. 
> 
>      How do you do that?
> 
	=> Do you mean how you use router renumbering ?
	This is explained in the draft. There are extensions defined to the 
	router renumbering mechanisms. 

	Hesham


From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep  4 18:07:04 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29353
	for <mobileip-archive@odin.ietf.org>; Tue, 4 Sep 2001 18:07:03 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id PAA14035;
	Tue, 4 Sep 2001 15:07:53 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id PAA22840;
	Tue, 4 Sep 2001 15:07:37 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f84M6N40018817
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 4 Sep 2001 15:06:23 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0/Submit) id f84M6Nw8018816
	for mobile-ip-dist; Tue, 4 Sep 2001 15:06:23 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f84M6J40018809
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 15:06:19 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id PAA06742
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 15:06:32 -0700 (PDT)
Received: from albatross-ext.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id PAA04168
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 15:06:30 -0700 (PDT)
Received: from esealnt462.al.sw.ericsson.se (ESEALNT462.al.sw.ericsson.se [153.88.251.62])
	by albatross.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id f84M6TK20212
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 00:06:29 +0200 (MEST)
Received: FROM esealnt742.al.sw.ericsson.se BY esealnt462.al.sw.ericsson.se ; Wed Sep 05 00:06:28 2001 +0200
Received: by esealnt742.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <NBWNRZPW>; Tue, 4 Sep 2001 23:59:38 +0200
Message-ID: <034BEFD03799D411A59F00508BDF754603008C6B@esealnt448.al.sw.ericsson.se>
From: "Hesham Soliman  (ERA)" <Hesham.Soliman@era.ericsson.se>
To: "'mobile-ip@sunroof.eng.sun.com'" <mobile-ip@sunroof.eng.sun.com>
Subject: RE: [mobile-ip] Coexistence with other uses for routing header
Date: Wed, 5 Sep 2001 00:06:21 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
	Hi Charlie, 

> In response to a question about how Mobile IPv6 uses routing
> headers vs. other uses, I propose inserted the following paragraph
> into the revised text, as the last paragraph of section 8.9.
> 
> Comments or additional clarifying text will be appreciated.
> 
> I put this as a SHOULD, because of the uncertainty about future
> definitions of routing headers.
> 
> Regards,
> Charlie P.
> 
> ===========================================================================
> 
> It is possible that a correspondent node, having no knowledge of
> the mobile node's care-of address, would still (for reasons unspecified
> here but not necessarily related to mobility) attempt use a routing
> header to deliver a packet to the mobile node's home address.
> If the correspondent node accepts a Binding Update
> and creates a Binding Cache entry for the mobile node, then
> in that case, the correspondent node SHOULD put the mobile
> node's care-of address as the last intermediate node address
> of the routing header, following all other intermediate node
> addresses that would have already been in the routing header
> before the creation of the Binding Cache entry for the care-of
> address.
> 
	=> Wouldn't the home address be the last segment in the 
	routing header ? 

	Hesham


From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep  4 18:09:46 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29426
	for <mobileip-archive@odin.ietf.org>; Tue, 4 Sep 2001 18:09:45 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id QAA06916;
	Tue, 4 Sep 2001 16:10:52 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id PAA24145;
	Tue, 4 Sep 2001 15:10:47 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f84M9T40018858
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 4 Sep 2001 15:09:29 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0/Submit) id f84M9S4M018857
	for mobile-ip-dist; Tue, 4 Sep 2001 15:09:28 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f84M9P40018850
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 15:09:25 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id PAA23820
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 15:09:38 -0700 (PDT)
Received: from sj-msg-core-2.cisco.com (sj-msg-core-2.cisco.com [171.69.24.11])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id QAA05923
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 16:09:33 -0600 (MDT)
Received: from mira-sjc5-7.cisco.com (mira-sjc5-7.cisco.com [171.71.163.27])
	by sj-msg-core-2.cisco.com (8.11.3/8.9.1) with ESMTP id f84M9vv07207
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 15:09:57 -0700 (PDT)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-7.cisco.com (Mirapoint)
	with ESMTP id ABE10831;
	Tue, 4 Sep 2001 15:09:34 -0700 (PDT)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id PAA24004; Tue, 4 Sep 2001 15:09:34 -0700 (PDT)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15253.20766.506149.760736@thomasm-u1.cisco.com>
Date: Tue, 4 Sep 2001 15:09:34 -0700 (PDT)
To: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Coexistence with other uses for routing header
In-Reply-To: <200109042145.f84LiU9d242322@jurassic.eng.sun.com>
References: <200109042145.f84LiU9d242322@jurassic.eng.sun.com>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Alper Yegin writes:
 > If we are going to make route optimization work with other uses of routing 
 > headers, why not make it work even when Home Address of a mobile node is not 
 > only the final destination of a packet, but also maybe an intermediate hop?

   Are you talking about the case where a mobile host is behind
   a mobile router? If so, how would CN know what order to put
   the routing headers in given two BU's?


	       Mike


From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep  4 18:11:12 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29473
	for <mobileip-archive@odin.ietf.org>; Tue, 4 Sep 2001 18:11:11 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id PAA16706;
	Tue, 4 Sep 2001 15:12:13 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id PAA24703;
	Tue, 4 Sep 2001 15:12:03 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f84MAv40018887
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 4 Sep 2001 15:10:57 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0/Submit) id f84MAvDP018886
	for mobile-ip-dist; Tue, 4 Sep 2001 15:10:57 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f84MAq40018879
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 15:10:52 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id PAA01609
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 15:11:05 -0700 (PDT)
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id QAA07013
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 16:11:00 -0600 (MDT)
Received: from mira-sjc5-7.cisco.com (mira-sjc5-7.cisco.com [171.71.163.27])
	by sj-msg-core-1.cisco.com (8.11.3/8.9.1) with ESMTP id f84MAx805683;
	Tue, 4 Sep 2001 15:10:59 -0700 (PDT)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-7.cisco.com (Mirapoint)
	with ESMTP id ABE10877;
	Tue, 4 Sep 2001 15:10:58 -0700 (PDT)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id PAA24007; Tue, 4 Sep 2001 15:10:58 -0700 (PDT)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15253.20849.847013.537485@thomasm-u1.cisco.com>
Date: Tue, 4 Sep 2001 15:10:57 -0700 (PDT)
To: "Hesham Soliman  (ERA)" <Hesham.Soliman@era.ericsson.se>
Cc: "'Michael Thomas'" <mat@cisco.com>, mobile-ip@sunroof.eng.sun.com,
        "Mattias Pettersson (ERA)" <Mattias.Pettersson@era.ericsson.se>,
        claude.castellucia@inria.fr, ludovic.bellier@inria.fr,
        "Karim El-Malki (ERA)" <Karim.El-Malki@era.ericsson.se>
Subject: RE: [mobile-ip] Question on HMIPv6 Dynamic MAP Discovery
In-Reply-To: <034BEFD03799D411A59F00508BDF754603008C69@esealnt448.al.sw.ericsson.se>
References: <034BEFD03799D411A59F00508BDF754603008C69@esealnt448.al.sw.ericsson.se>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hesham Soliman  (ERA) writes:
 > >  > 	=> Yes I think it is a very similar concept. In addition, the draft says that
 > >  > 	the advertisement SHOULD be secured to guarantee that no malicious
 > >  > 	nodes will provide false information. 
 > >  > 	The router renumbering mechanism can also be used as per the draft. 
 > > 
 > >      How do you do that?
 > > 
 > 	=> Do you mean how you use router renumbering ?
 > 	This is explained in the draft. There are extensions defined to the 
 > 	router renumbering mechanisms. 

   No, I meant the part about "secured to guarantee..."

	 Mike


From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep  4 18:29:14 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29873
	for <mobileip-archive@odin.ietf.org>; Tue, 4 Sep 2001 18:29:13 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id PAA24696;
	Tue, 4 Sep 2001 15:30:21 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id PAA14224;
	Tue, 4 Sep 2001 15:30:07 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f84MSr40018997
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 4 Sep 2001 15:28:53 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0/Submit) id f84MSqj5018996
	for mobile-ip-dist; Tue, 4 Sep 2001 15:28:52 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f84MSn40018989
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 15:28:49 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id PAA13896
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 15:29:00 -0700 (PDT)
Received: from albatross-ext.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id QAA26606
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 16:29:27 -0600 (MDT)
Received: from esealnt461 (esealnt461.al.sw.ericsson.se [153.88.251.61])
	by albatross.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id f84MSqK22617
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 00:28:52 +0200 (MEST)
Received: FROM esealnt400.al.sw.ericsson.se BY esealnt461 ; Wed Sep 05 00:28:51 2001 +0200
Received: by esealnt400 with Internet Mail Service (5.5.2653.19)
	id <NBWWDKPM>; Wed, 5 Sep 2001 00:28:44 +0200
Message-ID: <034BEFD03799D411A59F00508BDF754603008C6D@esealnt448.al.sw.ericsson.se>
From: "Hesham Soliman  (ERA)" <Hesham.Soliman@era.ericsson.se>
To: "'Michael Thomas'" <mat@cisco.com>
Cc: mobile-ip@sunroof.eng.sun.com,
        "Mattias Pettersson (ERA)"
	 <Mattias.Pettersson@era.ericsson.se>,
        claude.castellucia@inria.fr, ludovic.bellier@inria.fr,
        "Karim El-Malki (ERA)"
	 <Karim.El-Malki@era.ericsson.se>
Subject: RE: [mobile-ip] Question on HMIPv6 Dynamic MAP Discovery
Date: Wed, 5 Sep 2001 00:28:43 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>


>  > >  > 	=> Yes I think it is a very similar concept. In addition, the draft says that
>  > >  > 	the advertisement SHOULD be secured to guarantee that no malicious
>  > >  > 	nodes will provide false information. 
>  > >  > 	The router renumbering mechanism can also be used as per the draft. 
>  > > 
>  > >      How do you do that?
>  > > 
>  > 	=> Do you mean how you use router renumbering ?
>  > 	This is explained in the draft. There are extensions defined to the 
>  > 	router renumbering mechanisms. 
> 
>    No, I meant the part about "secured to guarantee..."
> 
	=> You can use IPsec to secure ND messages between routers. 
	The keys can be manually configured in the routers. The link local 
	addresses are manually configured on the routers. 
	Other key distribution mechanisms are not part of the draft and are outside 
	our scope. Do you thing something is missing ?

	Hesham




From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep  4 21:40:00 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02863
	for <mobileip-archive@odin.ietf.org>; Tue, 4 Sep 2001 21:40:00 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id TAA29854;
	Tue, 4 Sep 2001 19:41:05 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id SAA01819;
	Tue, 4 Sep 2001 18:41:00 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f851da40019225
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 4 Sep 2001 18:39:36 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0/Submit) id f851darU019224
	for mobile-ip-dist; Tue, 4 Sep 2001 18:39:36 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from jurassic.eng.sun.com (jurassic [129.146.85.105] (may be forged))
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f851dX40019217
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 18:39:33 -0700 (PDT)
Received: from istanbul.Eng.Sun.COM (istanbul.Eng.Sun.COM [129.146.86.247])
	by jurassic.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with SMTP id f851dk9d293439
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 18:39:46 -0700 (PDT)
Message-Id: <200109050139.f851dk9d293439@jurassic.eng.sun.com>
Date: Tue, 4 Sep 2001 18:39:48 -0700 (PDT)
From: Alper Yegin <Alper.Yegin@eng.sun.com>
Subject: Re: [mobile-ip] Coexistence with other uses for routing header
To: mobile-ip@sunroof.eng.sun.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: oecE09AH6tokx8ki4CVLNg==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4_37 SunOS 5.8.1 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Hi Mike,

> Alper Yegin writes:
>  > If we are going to make route optimization work with other uses of routing 
>  > headers, why not make it work even when Home Address of a mobile node is 
not 
>  > only the final destination of a packet, but also maybe an intermediate hop?
> 
>    Are you talking about the case where a mobile host is behind
>    a mobile router? If so, how would CN know what order to put
>    the routing headers in given two BU's?

I wasn't really thinking about that. It's just that CN is sending a packet that 
has to go through a MN (which is away from home and CN knows its CoA).

alper



From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep  4 21:44:56 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02936
	for <mobileip-archive@odin.ietf.org>; Tue, 4 Sep 2001 21:44:55 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id SAA23720;
	Tue, 4 Sep 2001 18:46:04 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id SAA02789;
	Tue, 4 Sep 2001 18:45:09 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f851iF40019269
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 4 Sep 2001 18:44:15 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0/Submit) id f851iF0v019268
	for mobile-ip-dist; Tue, 4 Sep 2001 18:44:15 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f851iB40019261
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 18:44:11 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id SAA02663
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 18:44:23 -0700 (PDT)
Received: from sj-msg-core-3.cisco.com (sj-msg-core-3.cisco.com [171.70.157.152])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id SAA10302
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 18:44:22 -0700 (PDT)
Received: from mira-sjc5-7.cisco.com (mira-sjc5-7.cisco.com [171.71.163.27])
	by sj-msg-core-3.cisco.com (8.11.3/8.9.1) with ESMTP id f851gQD07503
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 18:42:26 -0700 (PDT)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-7.cisco.com (Mirapoint)
	with ESMTP id ABH02258;
	Tue, 4 Sep 2001 18:44:20 -0700 (PDT)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id SAA24031; Tue, 4 Sep 2001 18:44:20 -0700 (PDT)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15253.33652.300206.53054@thomasm-u1.cisco.com>
Date: Tue, 4 Sep 2001 18:44:20 -0700 (PDT)
To: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Coexistence with other uses for routing header
In-Reply-To: <200109050139.f851dk9d293439@jurassic.eng.sun.com>
References: <200109050139.f851dk9d293439@jurassic.eng.sun.com>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Alper Yegin writes:
 > Hi Mike,
 > 
 > > Alper Yegin writes:
 > >  > If we are going to make route optimization work with other uses of routing 
 > >  > headers, why not make it work even when Home Address of a mobile node is 
 > not 
 > >  > only the final destination of a packet, but also maybe an intermediate hop?
 > > 
 > >    Are you talking about the case where a mobile host is behind
 > >    a mobile router? If so, how would CN know what order to put
 > >    the routing headers in given two BU's?
 > 
 > I wasn't really thinking about that. It's just that CN is sending a packet that 
 > has to go through a MN (which is away from home and CN knows its CoA).

   I guess I'm being really dense here, but...
   something that allows a packet to traverse a
   mobile node node is a router, no?

	       Mike


From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep  4 23:25:05 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA04767
	for <mobileip-archive@odin.ietf.org>; Tue, 4 Sep 2001 23:25:05 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id UAA10578;
	Tue, 4 Sep 2001 20:26:10 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id UAA16988;
	Tue, 4 Sep 2001 20:26:04 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f853P540019367
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 4 Sep 2001 20:25:05 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0/Submit) id f853P5rC019366
	for mobile-ip-dist; Tue, 4 Sep 2001 20:25:05 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f853P240019359
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 20:25:02 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id UAA05108
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 20:25:13 -0700 (PDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id UAA06022
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 20:25:13 -0700 (PDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id UAA27588;
	Tue, 4 Sep 2001 20:25:13 -0700 (PDT)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f853PCb19545;
	Tue, 4 Sep 2001 20:25:12 -0700
X-mProtect:  Tue, 4 Sep 2001 20:25:12 -0700 Nokia Silicon Valley Messaging Protection
Received: from Icharliep-1.iprg.nokia.com (205.226.22.18, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpdlDJ8Ti; Tue, 04 Sep 2001 20:25:10 PDT
Message-ID: <3B95967C.7C06BA51@iprg.nokia.com>
Date: Tue, 04 Sep 2001 20:05:32 -0700
From: Charlie Perkins <charliep@iprg.nokia.com>
Organization: Nokia
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Krishna Kumar <kumarkr@us.ibm.com>
CC: Mobile IP Working Group Mailing List <mobile-ip@sunroof.eng.sun.com>
Subject: [mobile-ip] Re: 
References: <200109042146.OAA11445@charliep.iprg.nokia.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit


Hello Krishna,

> From: "Krishna Kumar" <kumarkr@us.ibm.com>
> Date: Mon, 20 Aug 2001 11:06:32 -0700

> Section 9.2 of the draft says that when the MN requests the HA to no
> longer serve as it's HA (returns home) :
>
> "In addition, the home agent MUST stop intercepting packets on the
> mobile node's home link addressed to the mobile node (Section 9.3)."...
>
> I feel this step should also apply for the HA when the binding cache
> entry expires.

I agree that it should.

> I would like to suggest that the draft be modified to say that when an
> entry in the binding cache expires, the home agent MUST stop
> intercepting packets on the mobile node's home link addressed to
> the mobile node.

I will put some language to this effect into the next revision.

Regards,
Charlie P.





From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep  5 05:59:00 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA22298
	for <mobileip-archive@odin.ietf.org>; Wed, 5 Sep 2001 05:59:00 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id DAA29624;
	Wed, 5 Sep 2001 03:59:53 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id CAA11249;
	Wed, 5 Sep 2001 02:59:48 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f859wh40019773
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 5 Sep 2001 02:58:43 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0/Submit) id f859whuc019772
	for mobile-ip-dist; Wed, 5 Sep 2001 02:58:43 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f859wd40019765
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 02:58:39 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id CAA20560
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 02:58:52 -0700 (PDT)
Received: from laposte.enst-bretagne.fr (laposte.enst-bretagne.fr [192.108.115.3])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id CAA24365
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 02:58:51 -0700 (PDT)
Received: from rsm.rennes.enst-bretagne.fr (rsm.rennes.enst-bretagne.fr [192.44.77.1])
	by laposte.enst-bretagne.fr (8.11.6/8.11.6) with ESMTP id f859wps23301
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 11:58:51 +0200
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr [193.52.74.194])
	by rsm.rennes.enst-bretagne.fr (8.8.8/8.8.8) with ESMTP id LAA01500
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 11:58:49 +0200 (MET DST)
Received: from givry.rennes.enst-bretagne.fr (localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.11.3/8.11.3) with ESMTP id f859wnl14479
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 11:58:49 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200109050958.f859wnl14479@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Coexistence with other uses for routing header 
In-reply-to: Your message of Tue, 04 Sep 2001 14:44:52 PDT.
             <200109042145.f84LiU9d242322@jurassic.eng.sun.com> 
Date: Wed, 05 Sep 2001 11:58:49 +0200
X-Virus-Scanned: by amavisd-milter (http://www.amavis.org/) at enst-bretagne.fr
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
 In your previous mail you wrote:

   If we are going to make route optimization work with other uses of
   routing headers, why not make it work even when Home Address of a
   mobile node is not only the final destination of a packet, but also
   maybe an intermediate hop?
   
=> this seems a bit complex/difficult to implement. I believe
this should not get more than a MAY.

Regards

Francis.Dupont@enst-bretagne.fr

PS: I've sent a private comment about reversing of merged routing header:
this proposal SHOULD NOT be applied when the routing header will be
reversed, i.e. for authenticated connections.


From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep  5 12:16:22 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA09724
	for <mobileip-archive@odin.ietf.org>; Wed, 5 Sep 2001 12:16:19 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id KAA12067;
	Wed, 5 Sep 2001 10:17:11 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA11554;
	Wed, 5 Sep 2001 09:17:02 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f85GFw40020385
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 5 Sep 2001 09:15:58 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0/Submit) id f85GFwBJ020383
	for mobile-ip-dist; Wed, 5 Sep 2001 09:15:58 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from eastmail1.East.Sun.COM (eastmail1.East.Sun.COM [129.148.1.240])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f85GFt40020370
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 09:15:55 -0700 (PDT)
Received: from onion.east.sun.com (onion.East.Sun.COM [129.148.174.110])
	by eastmail1.East.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id MAA24773
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 12:16:06 -0400 (EDT)
Received: (from glass@localhost)
	by onion.east.sun.com (8.9.3+Sun/8.9.3) id MAA24301
	for mobile-ip@sunroof.eng.sun.com; Wed, 5 Sep 2001 12:16:36 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f84IGF40018025
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 11:16:15 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id LAA11711
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 11:15:55 -0700 (PDT)
Received: from ihemail2.firewall.lucent.com (ihemail2.lucent.com [192.11.222.163])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id LAA06324
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 11:15:54 -0700 (PDT)
Received: from marconi.ih.lucent.com (h135-1-120-108.lucent.com [135.1.120.108])
	by ihemail2.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id f84IFrR26307
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 14:15:53 -0400 (EDT)
Received: from nwsgpa.ih.lucent.com by marconi.ih.lucent.com (8.8.8+Sun/EMS-1.5 sol2)
	id NAA25513; Tue, 4 Sep 2001 13:15:51 -0500 (CDT)
Received: by nwsgpa.ih.lucent.com (8.8.8+Sun/EMS-1.5 client sol2)
	id NAA24946; Tue, 4 Sep 2001 13:15:45 -0500 (CDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15253.6737.475499.411227@nwsgpa.ih.lucent.com>
Date: Tue, 4 Sep 2001 13:15:45 -0500
From: Pete McCann <mccap@lucent.com>
To: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Low Latency Issue: Where to Run the Reverse Tunnel?
In-Reply-To: <200108302105.OAA28947@heliopolis.eng.sun.com>
References: <200108302105.OAA28947@heliopolis.eng.sun.com>
X-Mailer: VM 6.90 under 21.1 (patch 13) "Crater Lake" XEmacs Lucid
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hi, James,

I agree with your opinion that the reverse tunnel should go to the old
FA.  As stated below in your initial summary, the new FA and HA are
unlikely to share a security association, and without help from the
mobile node (in the form of a registration request going through AAA)
they are unlikely to get one easily.

On the other hand, the old and new FA should already have an
appropriate pair-wise agreement in place because they are supporting
fast handoff based on link layer triggers.  The two FAs need to have a
pre-arranged security association and some degree of trust that the L2
triggers received by one of the FAs will be honored by the other.
This pre-arranged agreement should be leveraged for the reverse tunnel
as well.

Also, handling the ping-pong case, as well as handoff-to-third, should
be much easier if those effects are confined to the FAs until the MN
re-registers itself with the HA.

I also agree with Ajoy's comments about leaving open the possibility
that we will tunnel already header-compressed packets between the two
FAs, rather than just IP packets.

-Pete

James Kempf writes:
 > Here's my opinion about one particular aspect of this issue:
 > 
 > >...
 > >
 > >In favor of the old FA: ...
 > > In addition,
 > >tunneling them to the HA will require a preregistration transaction
 > >between the HA and the new FA, otherwise the HA is in danger of
 > >dropping the packets because the new FA is not yet known. This
 > >transaction will add to the latency of handover, in particular, because
 > >the topological distance between the new FA and the HA is likely to
 > >be longer than the distance between the old and new FAs.
 > >
 > >In favor of the HA: ...
 > > The additional
 > >amount of latency added by the preregistration should not be extreme,
 > >and the FA can buffer outgoing packets until the registration reply
 > >is received, or opportunistically send them to the HA in anticipation of
 > >a successful preregistration.
 > >
 > 
 > The RTT on the preregistration request/reply could cause
 > a significant increase in latency on the handover (like, say, 60 ms if
 > I am in California and my HA is in New Jersey, or 160 ms if I am
 > in Minneapolis and my HA is in Germany), to say nothing of the packet 
 > getting dropped because it is sent UDP. The indicated
 > mitigating measures are relatively unattractive. Optimistically sending
 > the packets runs the risk of the HA dropping them if the preregistration
 > packet never got there, buffering them runs the risk of propagating
 > the latency and causing user perceptible artifacts in the real time stream.
 > One solution would be to deploy regional registration. This would
 > reduce the latency somewhat, but not eliminate it completely. In addition,
 > regional registration is currently not widely deployed and its prospects
 > are uncertain, whereas the need for low latency handoff is very acute
 > and the prospects for immediate deployment are fairly good.



From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep  5 12:21:04 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA09962
	for <mobileip-archive@odin.ietf.org>; Wed, 5 Sep 2001 12:21:03 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id JAA12424;
	Wed, 5 Sep 2001 09:19:51 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA11922;
	Wed, 5 Sep 2001 09:18:31 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f85GHY40020409
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 5 Sep 2001 09:17:34 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0/Submit) id f85GHYdw020408
	for mobile-ip-dist; Wed, 5 Sep 2001 09:17:34 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from eastmail2.East.Sun.COM (eastmail2.East.Sun.COM [129.148.1.241])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f85GHV40020401
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 09:17:32 -0700 (PDT)
Received: from onion.east.sun.com (onion.East.Sun.COM [129.148.174.110])
	by eastmail2.East.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id MAA29864
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 12:17:42 -0400 (EDT)
Received: (from glass@localhost)
	by onion.east.sun.com (8.9.3+Sun/8.9.3) id MAA24337
	for mobile-ip@sunroof.eng.sun.com; Wed, 5 Sep 2001 12:18:13 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f84ILk40018074
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 11:21:46 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id LAA22315
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 11:21:57 -0700 (PDT)
Received: from ihemail2.firewall.lucent.com (ihemail2.lucent.com [192.11.222.163])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA25440
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 12:22:31 -0600 (MDT)
Received: from marconi.ih.lucent.com (h135-1-120-108.lucent.com [135.1.120.108])
	by ihemail2.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id f84ILtR29269
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 4 Sep 2001 14:21:55 -0400 (EDT)
Received: from nwsgpa.ih.lucent.com by marconi.ih.lucent.com (8.8.8+Sun/EMS-1.5 sol2)
	id NAA28316; Tue, 4 Sep 2001 13:21:54 -0500 (CDT)
Received: by nwsgpa.ih.lucent.com (8.8.8+Sun/EMS-1.5 client sol2)
	id NAA08717; Tue, 4 Sep 2001 13:21:48 -0500 (CDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15253.7100.600250.507018@nwsgpa.ih.lucent.com>
Date: Tue, 4 Sep 2001 13:21:48 -0500
From: Pete McCann <mccap@lucent.com>
To: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Low Latency Issue: Should HTT be MUST, SHOULD, or MAY?
In-Reply-To: <3B8F9431.BA27E510@attglobal.net>
References: <200108301725.KAA18100@heliopolis.eng.sun.com>
	<3B8F9431.BA27E510@attglobal.net>
X-Mailer: VM 6.90 under 21.1 (patch 13) "Crater Lake" XEmacs Lucid
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

In my opinion, HTT should be a natural consequence of the low-latency
mechanism.  That is, it should naturally be a part of the way that
neighboring FAs "compose" in that they support tunneling to/from a
neighbor FA (and to/from a previous FA); a local registration may or
may not be initiated at any time, in a manner orthogonal to the edge
tunnels.  I guess this means HTT is a MUST but it should fall out as a
natural consequence of the way BETH is specified.

-Pete


Sebastian Thalanany writes:
 > Hello James,
 > 
 >                             Perhaps the following paragraph, indicating
 > the context in which HTT is
 > applied, may support the use of "MUST".
 > 
 >                             "In case the link layer triggers, which are
 > required by the post-registration scheme,
 > to support the movement of the wireless end of the BET, are available,
 > then the HTT scheme
 > MUST be applied to avoid a context transfer from the aFA to the nFA for
 > delay-sensitive information."
 > 
 > Regards,
 >      Sebastian
 > 
 > James Kempf wrote:
 > 
 > > At IETF 51 in London, it was agreed to add the Handoff To Third (HTT)
 > > to the POST-REGISTRATION part of the MIPv4 low latency handoff design.
 > > The HTT allows a MN that is already receiving traffic via a tunnel
 > > from an anchor FA to move to a new FA without receiving a new CoA.
 > > It is necessary because the current design provides no support for
 > > the case where a MN is moving so rapidly that it does not complete
 > > L3 handover by the time it moves to a new FA.
 > >
 > > The authors of the draft have discussed this, and are not in agreement
 > > about what level to incorporate HTT. In particular, should HTT be
 > > MUST, SHOULD, or MAY?
 > >
 > > In favor of MAY: We should keep the protocol as simple as possible.
 > > This message is only required in certain restricted circumstances
 > > that will not occur for every radio link protocol, and therefore
 > > it should not be required unless the radio link protocol supports
 > > rapid movement to a new FA.
 > >
 > > In favor of MUST: In addition to fixing the abovementioned bug,
 > > HTT also provides a new capability that is not available in
 > > RFC 2002 nor with PRE-REGISTRATION, namely the ability of the MN
 > > to choose when it should obtain a CoA based upon its traffic.
 > > If the MN is receiving real time traffic, it may choose to
 > > forgo L3 handoff until the real time stream is done, thereby
 > > avoiding the radio link traffic involved in MIP signalling. This
 > > is similar to the BETH proposal for IPv6, which the WG agreed
 > > to incorporate into the FMIPv6 draft.
 > >
 > > The authors need working group guidance on this issue.
 > >
 > >                 jak
 > 


From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep  5 12:28:24 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10158
	for <mobileip-archive@odin.ietf.org>; Wed, 5 Sep 2001 12:28:24 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id JAA17361;
	Wed, 5 Sep 2001 09:28:16 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA13643;
	Wed, 5 Sep 2001 09:25:25 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f85GOL40020530
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 5 Sep 2001 09:24:21 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0/Submit) id f85GOKk1020529
	for mobile-ip-dist; Wed, 5 Sep 2001 09:24:20 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from eastmail1.East.Sun.COM (eastmail1.East.Sun.COM [129.148.1.240])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f85GOI40020522
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 09:24:18 -0700 (PDT)
Received: from onion.east.sun.com (onion.East.Sun.COM [129.148.174.110])
	by eastmail1.East.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id MAA26073
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 12:24:29 -0400 (EDT)
Received: (from glass@localhost)
	by onion.east.sun.com (8.9.3+Sun/8.9.3) id MAA24459
	for mobile-ip@sunroof.eng.sun.com; Wed, 5 Sep 2001 12:24:59 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f85ED740020053
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 07:13:07 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id HAA14049
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 07:13:17 -0700 (PDT)
Received: from netmail2.alcatel.com (netmail2.alcatel.com [128.251.168.51])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA01656
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 08:13:50 -0600 (MDT)
Received: from auds953.usa.alcatel.com (auds953.usa.alcatel.com [143.209.238.6])
	by netmail2.alcatel.com (8.9.1/8.9.1) with ESMTP id JAA05409
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 09:13:16 -0500 (CDT)
Received: from alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.10.2/8.10.2) with ESMTP id f85EDFx11637
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 09:13:15 -0500 (CDT)
Message-ID: <3B9623D7.624CF75A@alcatel.com>
Date: Wed, 05 Sep 2001 09:08:43 -0400
From: Behcet Sarikaya <behcet.sarikaya@alcatel.com>
X-Mailer: Mozilla 4.76 [en]C-CCK-MCD BDPjm-Sony3  (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Coexistence with other uses for routing header
References: <034BEFD03799D411A59F00508BDF754603008C6B@esealnt448.al.sw.ericsson.se>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hesham,

"Hesham Soliman (ERA)" wrote:

> > In response to a question about how Mobile IPv6 uses routing
> following all other intermediate node
> > addresses that would have already been in the routing header
> > before the creation of the Binding Cache entry for the care-of
> > address.
> >
>         => Wouldn't the home address be the last segment in the
>         routing header ?
>
>         Hesham

Yes, in route optimized IPv6 datagrams the destination address is the CoA and the
home address is placed in the routing header.
My 0.002 euros.

--
Behcet



From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep  5 12:45:49 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10491
	for <mobileip-archive@odin.ietf.org>; Wed, 5 Sep 2001 12:45:46 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id KAA09344;
	Wed, 5 Sep 2001 10:46:41 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA21112;
	Wed, 5 Sep 2001 09:46:37 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f85GjB40020678
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 5 Sep 2001 09:45:11 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0/Submit) id f85GjBbA020677
	for mobile-ip-dist; Wed, 5 Sep 2001 09:45:11 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from eastmail1.East.Sun.COM (eastmail1.East.Sun.COM [129.148.1.240])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f85Gj540020670
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 09:45:09 -0700 (PDT)
Received: from onion.east.sun.com (onion.East.Sun.COM [129.148.174.110])
	by eastmail1.East.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id MAA00080
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 12:45:16 -0400 (EDT)
Received: (from glass@localhost)
	by onion.east.sun.com (8.9.3+Sun/8.9.3) id MAA24823
	for mobile-ip@sunroof.eng.sun.com; Wed, 5 Sep 2001 12:45:46 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f835TG40015315
	for <mobile-ip@sunroof.eng.sun.com>; Sun, 2 Sep 2001 22:29:16 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id WAA02015
	for <mobile-ip@sunroof.eng.sun.com>; Sun, 2 Sep 2001 22:29:28 -0700 (PDT)
Received: from mail1.ics.ntts.co.jp (mail1.ics.ntts.co.jp [202.32.24.45])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id WAA20845
	for <mobile-ip@sunroof.eng.sun.com>; Sun, 2 Sep 2001 22:29:22 -0700 (PDT)
Received: from mail26.silk.ntts.co.jp by mail1.ics.ntts.co.jp (8.9.3/3.7W-NTTSOFT-SUR2.0)
	id OAA10779; Mon, 3 Sep 2001 14:29:21 +0900 (JST)
Received: from daemon.inl.ntts.co.jp by mail26.silk.ntts.co.jp (8.11.4/3.7W-silk-4.4)
	id f835TKb12432; Mon, 3 Sep 2001 14:29:20 +0900 (JST)
Received: (qmail 69334 invoked by alias); 3 Sep 2001 14:29:20 +0900
Received: (qmail 69326 invoked from network); 3 Sep 2001 14:29:20 +0900
Received: from tunayosi.inl.ntts.co.jp (HELO localhost)
  by daemon.inl.ntts.co.jp with SMTP; 3 Sep 2001 14:29:20 +0900
Date: Mon, 03 Sep 2001 14:29:19 +0900 (JST)
Message-Id: <20010903.142919.115990780.takamiya@po.ntts.co.jp>
To: mobile-ip@sunroof.eng.sun.com
From: takamiya@po.ntts.co.jp, Noriaki Takamiya <takamiya@po.ntts.co.jp>
Subject: [mobile-ip] About Home Agent Flag in Router Advertisement Message
X-Mailer: Mew version 2.0 on XEmacs 21.4.1 (Copyleft)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hello,

  This is Takamiya. 

  I'm using MIPL implementation on USAGI IPv6 platform.

  In MIPL mailing list, I encountered the following problem:

  When a Home Agent sends Router Advertisement Message and changes
  Home Agent Flag(H) from on to off, should other Home Agent remove
  this router from the Home Agent List?

  I thought that the Home Agent changed Router Advertisement Message
  change Home Agent Flag from on to off, the other Home Agent should
  remove this router entry. But It seems that this behavior is not
  documented(draft 14) explicitly.

  I'm newbie about this mailing list, so I will apologize some
  mistakes.

  Regards,

--
Noriaki Takamiya


From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep  5 12:51:43 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10760
	for <mobileip-archive@odin.ietf.org>; Wed, 5 Sep 2001 12:51:43 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id JAA01112;
	Wed, 5 Sep 2001 09:52:45 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA23367;
	Wed, 5 Sep 2001 09:52:37 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f85Gpf40020871
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 5 Sep 2001 09:51:41 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0/Submit) id f85GpfIj020870
	for mobile-ip-dist; Wed, 5 Sep 2001 09:51:41 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from heliopolis.eng.sun.com (redcoast.Eng.Sun.COM [152.70.28.21])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f85Gpb40020863
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 09:51:37 -0700 (PDT)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.eng.sun.com (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id JAA21795
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 09:51:50 -0700 (PDT)
Message-Id: <200109051651.JAA21795@heliopolis.eng.sun.com>
Date: Wed, 5 Sep 2001 09:51:49 -0700 (PDT)
From: James Kempf <James.Kempf@Sun.COM>
Subject: Re: [mobile-ip] Low Latency Issue: Should HTT be MUST, SHOULD, or MAY?
To: mobile-ip@sunroof.eng.sun.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: iNr057WeEuxkyqaWWQ74uw==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

I'd like to make a proposal which I think will address Pete's and Sebastian's
concerns. 

First off, there is an issue with regard to whether the mobile node should
perform movement detection or not. When a mobile node,
capable of delaying L3 handoff until real time traffic slows, moves into a 
domain where BETH is supported and registers with an FA, how will it
know not to issue a ProxyRtSol (if mobile initiated low latency
handoff is happening) or to issue a RtSol (if RFC2002bis handoff is
happening)? If network initiated handoff is happening, how will
the mobile node know not to perform a registration when it receives
the Link Up L2 trigger on the new FA?

I'd like to suggest that we add a bit to the Agent Advertisement:

  S - Mobile node can suppress movement detection and handoff at L3 if
      desired. FAs will make sure the mobile node's packets are properly
      routed until a registration for a new care of address is made.
      
This will inform a BETH-capable mobile node that it can calibrate
L3 handoff to its movement pattern and real time traffic volume.

Secondly, I'd like to suggest that we make HTT a MUST, in order
to simplify interoperability. As Pete pointed out, HTT is fundamental
to providing the high performance benefits of BETH, in addition to supporting
quick movement between FAs before the care of address is established. 
If it is not a MUST, problems could arise in deployment.

As a simple example of what could happen if HTT is a MAY or SHOULD,
suppose a small wireless ISP decides that they don't want to support
high performance real time services, so they buy a brand of FA that
does not support HTT. 3 years later they have grown big enough and
that their customers are beginning to request high performance
real time service. Now, they are in the position of having to go
through and replace all their FAs with another brand. If HTT was
a MUST, they could just turn on the bit in the Agent Advertisement
and configure for proper tunneling. 

With regard to the implementation complexity issue, we are currently
working on an implementation of low latency, and so far it really
does not look like a problem.

Comments?

		jak




From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep  5 13:10:41 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11306
	for <mobileip-archive@odin.ietf.org>; Wed, 5 Sep 2001 13:10:41 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA11597;
	Wed, 5 Sep 2001 10:11:43 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id KAA29296;
	Wed, 5 Sep 2001 10:11:24 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f85H9r40020989
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 5 Sep 2001 10:09:53 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0/Submit) id f85H9rHS020988
	for mobile-ip-dist; Wed, 5 Sep 2001 10:09:53 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f85H9n40020981
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 10:09:50 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id KAA03041
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 10:10:01 -0700 (PDT)
Received: from auemail2.firewall.lucent.com (auemail2.lucent.com [192.11.223.163])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA16762
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 11:10:35 -0600 (MDT)
Received: from hoserve.ho.lucent.com (h135-17-35-10.lucent.com [135.17.35.10])
	by auemail2.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with SMTP id f85H9xJ05783
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 13:09:59 -0400 (EDT)
Received: from qc84.ho.lucent.com by hoserve.ho.lucent.com (SMI-8.6/EMS-1.5 sol2)
	id NAA08168; Wed, 5 Sep 2001 13:13:54 -0400
Received: from qc84 by qc84.ho.lucent.com (8.8.8+Sun/EMS-1.4.1 client sol2)
	id NAA24230; Wed, 5 Sep 2001 13:17:30 -0400 (EDT)
Message-Id: <200109051717.NAA24230@qc84.ho.lucent.com>
Date: Wed, 5 Sep 2001 13:17:30 -0400 (EDT)
From: chuah <chuah@hoserve.ho.lucent.com>
Subject: Re: [mobile-ip] Low Latency Issue: Should HTT be MUST, SHOULD, or MAY?
To: mobile-ip@sunroof.eng.sun.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: 2fOBembSB0n8zGIuJtZIoA==
X-Mailer: dtmail 1.2.1 CDE Version 1.2.1 SunOS 5.6 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

James,
sorry, I didn't read multiple emails.  what is HTT?

Mooi Choo



From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep  5 13:12:04 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11393
	for <mobileip-archive@odin.ietf.org>; Wed, 5 Sep 2001 13:12:02 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id LAA03978;
	Wed, 5 Sep 2001 11:12:58 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id KAA29694;
	Wed, 5 Sep 2001 10:12:53 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f85HBl40021009
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 5 Sep 2001 10:11:47 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0/Submit) id f85HBkNw021008
	for mobile-ip-dist; Wed, 5 Sep 2001 10:11:46 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from heliopolis.eng.sun.com (heliopolis.Eng.Sun.COM [152.70.1.39])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f85HBh40020998
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 10:11:43 -0700 (PDT)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.eng.sun.com (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id KAA22744
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 10:11:55 -0700 (PDT)
Message-Id: <200109051711.KAA22744@heliopolis.eng.sun.com>
Date: Wed, 5 Sep 2001 10:11:54 -0700 (PDT)
From: James Kempf <James.Kempf@Sun.COM>
Subject: Re: [mobile-ip] Low Latency Issue: Where to Run the Reverse Tunnel?
To: mobile-ip@sunroof.eng.sun.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: kvcDIJQomANrkiJaP7sXmQ==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Hi Pete,

>
>I agree with your opinion that the reverse tunnel should go to the old
>FA.  As stated below in your initial summary, the new FA and HA are
>unlikely to share a security association, and without help from the
>mobile node (in the form of a registration request going through AAA)
>they are unlikely to get one easily.
>
>On the other hand, the old and new FA should already have an
>appropriate pair-wise agreement in place because they are supporting
>fast handoff based on link layer triggers.  The two FAs need to have a
>pre-arranged security association and some degree of trust that the L2
>triggers received by one of the FAs will be honored by the other.
>This pre-arranged agreement should be leveraged for the reverse tunnel
>as well.
>

The only issue I can see with this is that routing may be suboptimal
when the mobile node requests a reverse tunnel from the anchor FA.

RFC 2344 has been folded into RFC2002bis, so there is now a flag
in the Registration Request that allows the mobile node to request
a reverse tunnel from the FA to the HA. RFC 2344 recommends a
Foreign to Home Authentication extension as the best way  to
protect against attacks. If such a security association is not in
place, it also suggests an elegant little
hack, requiring the mobile node to set the TTL to 255 on its
Registration Requests, to disallow a node more than one hop
away from posing as the mobile node (of course, this will not
stop  an attack from a node on the same subnet). 

Naturally, if a tunnel is extended from the new FA to the HA, the same security 
requirements apply, except that there will be no communication with
the mobile node.

With regard to the proposal I sent out yesterday, do you see any issue
with allowing the old FA to indicate whether the mobile node
has requested a tunnel to the HA, and having the new FA do the tunnel,
provided the proper security association is available?

One issue I can see is that the new FA may not be in a position to
do so if the proper security association is not in place. So
maybe rather than making the H flag a MUST, it could be made a SHOULD.
This would allow the new FA to optimize routing if the proper
security association was in place, if not, the new FA could run the
tunnel back to the old FA, which could take care of the reverse
tunnel.


		jak



From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep  5 14:35:03 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15581
	for <mobileip-archive@odin.ietf.org>; Wed, 5 Sep 2001 14:34:56 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id MAA13494;
	Wed, 5 Sep 2001 12:35:54 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id LAA23319;
	Wed, 5 Sep 2001 11:35:49 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f85IYi40021315
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 5 Sep 2001 11:34:44 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0/Submit) id f85IYiAT021314
	for mobile-ip-dist; Wed, 5 Sep 2001 11:34:44 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from jurassic.eng.sun.com (jurassic [129.146.84.31] (may be forged))
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f85IYe40021307
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 11:34:40 -0700 (PDT)
Received: from istanbul.Eng.Sun.COM (istanbul.Eng.Sun.COM [129.146.86.247])
	by jurassic.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with SMTP id f85IYn9d410758
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 11:34:51 -0700 (PDT)
Message-Id: <200109051834.f85IYn9d410758@jurassic.eng.sun.com>
Date: Wed, 5 Sep 2001 11:34:53 -0700 (PDT)
From: Alper Yegin <Alper.Yegin@eng.sun.com>
Subject: Re: [mobile-ip] Coexistence with other uses for routing header
To: mobile-ip@sunroof.eng.sun.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: C0Ve+3tbmDqHH9CnzaG3Mw==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4_37 SunOS 5.8.1 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

>  > >  > If we are going to make route optimization work with other uses of 
routing 
>  > >  > headers, why not make it work even when Home Address of a mobile node 
is 
>  > not 
>  > >  > only the final destination of a packet, but also maybe an intermediate 
hop?
>  > > 
>  > >    Are you talking about the case where a mobile host is behind
>  > >    a mobile router? If so, how would CN know what order to put
>  > >    the routing headers in given two BU's?
>  > 
>  > I wasn't really thinking about that. It's just that CN is sending a packet 
that 
>  > has to go through a MN (which is away from home and CN knows its CoA).
> 
>    I guess I'm being really dense here, but...
>    something that allows a packet to traverse a
>    mobile node node is a router, no?


Mobile node doesn't have to be a "router", it just needs to "forward" the packet 
though. It's just like when it forwards the packet to itself when the 
destination of a packet is CoA and the next hop is Home_Address.

I can't think of any application that needs this right now, but I think the 
practice was to allow future protocols using routing header work with route 
optimization.

alper


alper



From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep  5 14:56:46 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17658
	for <mobileip-archive@odin.ietf.org>; Wed, 5 Sep 2001 14:56:43 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id MAA00713;
	Wed, 5 Sep 2001 12:57:35 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id LAA00082;
	Wed, 5 Sep 2001 11:57:33 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f85IuW40021390
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 5 Sep 2001 11:56:32 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0/Submit) id f85IuWCw021389
	for mobile-ip-dist; Wed, 5 Sep 2001 11:56:32 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from eastmail2.East.Sun.COM (eastmail2.East.Sun.COM [129.148.1.241])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f85IuU40021382
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 11:56:30 -0700 (PDT)
Received: from onion.east.sun.com (onion.East.Sun.COM [129.148.174.110])
	by eastmail2.East.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id OAA06665
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 14:56:40 -0400 (EDT)
Received: (from glass@localhost)
	by onion.east.sun.com (8.9.3+Sun/8.9.3) id OAA26997
	for mobile-ip@sunroof.eng.sun.com; Wed, 5 Sep 2001 14:57:10 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f85Idc40021348
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 11:39:38 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id LAA21311
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 11:39:49 -0700 (PDT)
Received: from e1.ny.us.ibm.com (e1.ny.us.ibm.com [32.97.182.101])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id LAA05141
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 11:39:47 -0700 (PDT)
Received: from northrelay02.pok.ibm.com (northrelay02.pok.ibm.com [9.117.200.22])
	by e1.ny.us.ibm.com (8.9.3/8.9.3) with ESMTP id OAA326848
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 14:37:23 -0400
Received: from d01ml233.pok.ibm.com (d01ml233.pok.ibm.com [9.117.200.63])
	by northrelay02.pok.ibm.com (8.11.1m3/NCO v4.97.1) with ESMTP id f85IVQj26384
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 14:31:26 -0400
Importance: Normal
Subject: [mobile-ip] MobiHoc 2001 - Call For Participation
To: sigmob@acm.org
X-Mailer: Lotus Notes Release 5.0.3 (Intl) 21 March 2000
Message-ID: <OF17DE8117.8EBE22CF-ON85256ABE.0063AC1C@pok.ibm.com>
From: "Young-bae Ko" <youngko@us.ibm.com>
Date: Wed, 5 Sep 2001 14:39:22 -0400
X-MIMETrack: Serialize by Router on D01ML233/01/M/IBM(Release 5.0.8 |June 18, 2001) at
 09/05/2001 02:39:27 PM
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

                     Call for Participation

                          MobiHoc 2001
                          ============

            The 2001 ACM International Symposium on
              Mobile Ad Hoc Networking & Computing

         October 4-5, 2001,Long Beach, California, USA

                 http://www.cs.ucla.edu/mobihoc/

                   Sponsored by ACM SIGMOBILE

MobiHoc 2001, sponsored by ACM SIGMOBILE, will serve as an international
forum for addressing cutting-edge issues related to mobile ad hoc
networking and computing. Following the success of MobiHoc 2000 in Boston,
MobiHoc 2001 has been expanded to a 2-day symposium, to provide more
opportunities for participation by the ad hoc networking and computing
community.

We invite you to join us for MobiHoc 2001, at the Hyatt Regency hotel,
on the waters' edge in Long Beach, California, USA, October 4-5, 2001.

--------------------------------------------------------------------------

REGISTRATION AND HOTEL INFORMATION

For information on registration and hotel reservations, please refer to
the MobiHoc 2001 web site at
                               "http://www.cs.ucla.edu/mobihoc/".

*** Important Dates:
                     Early Registration Deadline:     September 13, 2001
                     Special Hotel Rate Cut-off Date: September 12, 2001

--------------------------------------------------------------------------

TRAVEL SUPPORT

Travel support is expected to be available for some attendees.
Please watch the MobiHoc 2001 web site for additional information.

--------------------------------------------------------------------------

TECHNICAL SESSIONS

This year, a large number of technical papers was received, resulting in
a highly selective technical program. The program will include research
paper sessions on routing and transport protocols, link and physical layer
issues, sensor networks, energy management, security issues, testbeds and
applications, Bluetooth, and analysis techniques. It will also include
a number of exciting poster presentations.

*** October 4, Thursday

8:45 - 9:45 Keynote Speech "Wireless Networks: Where is the Beef?"
            by Professor Anthony Ephremides (University of Maryland)

10:15 - 11:30 Session 1: Routing (Chair - Martha Steenstrup)

           "Implicit Source Routing for On-Demand Ad Hoc Network Routing"
            by Yih-Chun Hu (CMU) and David B. Johnson (Rice University)

           "Neighborhood Aware Source Routing"
            by Marcelo Spohn and J.J. Garcia-Luna-Aceves (USUC)

           "Making Link-State Routing Scale for Ad Hoc Networking"
            by Cesar A. Santivanez (BBN), Ram Ramanathan (BBN), and
            Ioannis Stavrakakis (University of Athens)

11:30 - 12:15 Invited Talk
           "Mobile Ad Hoc Networking with Directional Antennas
            for Future Combat Systems", by James A. Freebersyser (DARPA)

1:30 - 2:45 Session 2: Routing and Transport (Chair - Charles Perkins)

           "Adaptive Demand-Driven Multicast Routing in Multi-Hop Wireless
            Ad Hoc Networks", by Jorjeta G. Jetcheva (CMU) and
            David B. Johnson (Rice University)

           "Geometric Spanner for Routing in Mobile Networks"
            by Jie Gao, Leonidas J. Buibas (Stanford University),
            John Hershberger (Mentor Graphics), Li Zhang (Compaq Systems
            Research), An Zhu (Stanford University)

           "A Comparison of TCP Performance over Three Routing Protocols
            for Mobile Ad Hoc Networks", by Thomas D. Dyer and
            Rajendra V. Boppana (University of Texas, San Antonio)

3:15 - 5:00 Session 3: Link and Physical Layer Issues
            (Chair - David B. Johnson)

           "SEEDEX: A MAC Protocol for Ad Hoc Networks"
            by R. Rozovsky and P.R. Kumar (University of Illinois)

           "Medium Access and Radio Resource Management for Ad Hoc Networks
            based on UTRA TDD", by M. Lott, R. Halfmann, E. Schulz
            (Siemens AG), and M. Radimirsch (University of Hannover)

           "Effects of Wireless Physical Layer Modeling in Ad Hoc Networks"
            by Mineo Takai, Jay Martin, and Rajive Bagrodia (UCLA)

           "On the Performance of Ad Hoc Networks with Beamforming
            Antennas" by Ram Ramanathan (BBN Technologies)

5:15 - 6:00 Outrageous Opinions Session
            (Chair - Zygmunt Haas, Cornell University)


*** October 5, Friday

8:00 - 9:30 Poster Session
            (Chair - Joe Macker, Naval Research Lab)

9:45 - 11:30 Session 4: Sensor Networks and Energy Management
            (Chair - Andrew Campbell)

           "Localized Algorithms in Wireless Ad-Hoc Networks:
            Location Discovery and Sensor Exposure", by S. Meguerdichian,
            S. Slijepcevic, V. Karayan, and M. Potkonjak (UCLA)

           "Effects of Power Conservation, Wireless Coverage and
            Cooperation on Data Dissemination among Mobile Devices",
            by M. Papadopouli and H. Schulzrinne (Columbia University)

           "Maximum Flow-Life Curve for a Wireless Ad Hoc Network"
            T.X. Brown, H.N. Gabow, and Qi Zhang (University of Colorado)

           "Birthday Protocols for Low Energy Deployment and Flexible
            Neighbor Discovery in Ad Hoc Wireless Networks",
            M.J. McGlynn and S. A. Borbash (Lab. for Telecomm. Sciences)

1:15 - 3:00 Session 5: Security, Testbeds and Applications
            (Chair - Elizabeth Royer)

           "The Quest for Security in Mobile Ad Hoc Networks"
            by Jean-Pierre Hubaux, Levente Buttyan, and Srdan Capkun
            (Swiss Federal Institute of Technology)

           "Secure Pebblenets"
            by Stefano Basagni, Kris Herrin (University of Texas, Dallas),
            Danilo Bruschi, Emilia Rosti (Universita Degli Studi di Milano)

           "Testbed on a Desktop: Strategies and Techniques to Support
            Multi-hop MANET Routing Protocol Development", by James T. Kaba
            and Douglas R. Raichle (Sarnoff Corporation)

           "Time Synchronization in Ad Hoc Networks"
            by Kay Romer (ETH Zurich)

3:30 - 4:45 Session 6: Bluetooth (Chair - Jason Redi)

           "Performance of a New Bluetooth Scatternet Formation Protocol"
            by Ching Law, Amar K. Mehta, and Kai-Yeung Siu (MIT)

           "A Pseudo Random Coordinated Scheduling Algorithm for Bluetooth
            Scatternets", by Andras Racz, Gyorgy Miklos, Ferenc Kubinszky,
            and Andras Valko (Ericsson Research)

           "JUMP Mode - A Dynamic Window-based Scheduling Framework for
            Bluetooth Scatternets", Niklas Johansson, Fredrik Alriksson,
            and Ulf Jonsson (Ericsson Research)

5:00 - 6:15 Session 7: Analysis Techniques (Chair - Ram Ramanathan)

           "A Probabilistic Analysis for the Range Assignment Problem in
            Ad Hoc Networks", by Paolo Santi (Area della Ricerca del CNR),
            Douglas M. Blough and Feodor Vainstein (Georgia Tech)

           "On Max-min Fairness and Scheduling in Wireless Ad-Hoc Networks:
            Analytical Framework and Implementation", by Xiao Long Huang
            and Brahim Bensaou (Hong Kong University of Science and Tech.)

           "Scenario-Based Stability Analysis of the Distributed
            Mobility-Adaptive Clustering (DMAC) Algorithm",
            C. Bettstetter, R. Krausser (Technische Universitat Muncheon)

-----------------------------------------------------------------------------



OUTRAGEOUS OPINIONS SESSION

Short abstracts (at most 50 words) are solicited for this special session.
An outrageous prize will be awarded to the winner of the most shocking
presentation. Please email your submission to the session chair,
Zygmunt Haas (haas@ece.cornell.edu).

-----------------------------------------------------------------------------



ORGANIZING COMMITTEE

* General Chair:
       Nitin H. Vaidya (University of Illinois at Urbana-Champaign)

* Technical Program Co-Chairs:
       M. Scott Corson (Flarion Technologies)
       Samir R. Das (University of Cincinnati)

* European Liaison:
       Jean-Pierre Hubaux (Swiss Federal Inst. of Tech.)

* Local Arrangements Chair:
       Srikanth Krishnamurthy (UC-Riverside)

* Finance Co-Chairs:
       Stefano Basagni (UT-Dallas)
       Violet R. Syrotiuk (UT-Dallas)

* Publicity Co-Chairs:
       Young-Bae Ko (IBM T.J. Watson Research)
       Songwu Lu (UC-Los Angeles)

* Publication Chair:
       Sung-Ju Lee (Hewlett-Packard Labs)

* Registration Chair:
       John Heidemann (ISI-USC)
       Katia Obraczka (UC-Santa Cruz)

* Outrageous Session Chair:
       Zygmunt Haas (Cornell University)

* Steering Committee:
       Andrew Campbell (Columbia University)
       J.J. Garcia-Luna-Aceves (UC-Santa Cruz)
       Mario Gerla (UC-Los Angeles)
       Joseph P. Macker (NRL)
       Charles E. Perkins (Nokia Research)
       Ram Ramanathan (BBN Tech.)
       Martha Steenstrup (Stow Research)
       C-K. Toh (Georgia Tech.)
       Nitin H. Vaidya (University of Illinois)

* Technical Program Committee:
       Dennis Baker (NRL)
       Pravin Bhagwat (ReefEdge, Inc.)
       Andrew Campbell (Columbia University)
       Anthony Ephremides (University of Maryland)
       J.J. Garcia-Luna-Aceves (UC-Santa Cruz)
       Ramesh Govindan (USC/ISI)
       Phillippe Jacquet (INRIA)
       David B. Johnson (Rice University)
       Tony Larsson (Ericsson Research)
       Joe Macker (NRL)
       David Maltz (AON Networks)
       Gyorgy Miklos (Ericsson Research)
       Richard Ogier (SRI)
       Vincent Park (Flarion Technologies)
       Charles E. Perkins (Nokia Research)
       Amir Qayyum (INRIA)
       Ram Ramanathan (BBN Tech.)
       Andras Racz (Ericsson Research)
       Jason Redi (BBN Tech.)
       Elizabeth Royer (UC-Santa Barbara)
       Martha Steenstrup (Stow Research)
       Leandros Tassiulas (University of Maryland)
       Fred Templin (SRI)

------------------------------------------------------------

SUPPORTED BY

       TRW and NSF
------------------------------------------------------------





From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep  5 15:23:13 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18988
	for <mobileip-archive@odin.ietf.org>; Wed, 5 Sep 2001 15:23:13 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA18349;
	Wed, 5 Sep 2001 12:24:16 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id MAA07691;
	Wed, 5 Sep 2001 12:23:44 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f85JMB40021487
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 5 Sep 2001 12:22:11 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0/Submit) id f85JMBDW021486
	for mobile-ip-dist; Wed, 5 Sep 2001 12:22:11 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f85JM740021479
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 12:22:07 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id MAA04283
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 12:22:18 -0700 (PDT)
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA01251
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 13:22:51 -0600 (MDT)
Received: from mira-sjc5-7.cisco.com (mira-sjc5-7.cisco.com [171.71.163.27])
	by sj-msg-core-1.cisco.com (8.11.3/8.9.1) with ESMTP id f85JMJ811475
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 12:22:19 -0700 (PDT)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-7.cisco.com (Mirapoint)
	with ESMTP id ABI03139;
	Wed, 5 Sep 2001 12:22:13 -0700 (PDT)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id MAA24332; Wed, 5 Sep 2001 12:22:13 -0700 (PDT)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15254.31589.380641.473319@thomasm-u1.cisco.com>
Date: Wed, 5 Sep 2001 12:22:13 -0700 (PDT)
To: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Coexistence with other uses for routing header
In-Reply-To: <200109051834.f85IYn9d410758@jurassic.eng.sun.com>
References: <200109051834.f85IYn9d410758@jurassic.eng.sun.com>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Alper Yegin writes:
 > Mobile node doesn't have to be a "router", it just needs to "forward" the packet 
 > though. It's just like when it forwards the packet to itself when the 
 > destination of a packet is CoA and the next hop is Home_Address.
 > 
 > I can't think of any application that needs this right now, but I think the 
 > practice was to allow future protocols using routing header work with route 
 > optimization.

   We're probably off in the definitional weeds here,
   but I'd think that something that moves packets
   toward their destination instead of toward
   themselves is acting like a router, regardless
   of what caused them to do so. Practically
   speaking, I'd sure like some knob -- like the
   router on/off switch -- which controls whether
   my node acts as a forwarder regardless of how
   something is trying to get me to forward.

		Mike


From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep  5 15:31:13 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19482
	for <mobileip-archive@odin.ietf.org>; Wed, 5 Sep 2001 15:31:08 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id NAA28312;
	Wed, 5 Sep 2001 13:32:01 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id MAA10159;
	Wed, 5 Sep 2001 12:31:57 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f85JUl40021537
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 5 Sep 2001 12:30:48 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0/Submit) id f85JUlST021536
	for mobile-ip-dist; Wed, 5 Sep 2001 12:30:47 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f85JUh40021529
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 12:30:43 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id MAA09720
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 12:30:54 -0700 (PDT)
Received: from auemail1.firewall.lucent.com (auemail1.lucent.com [192.11.223.161])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA06070
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 13:31:28 -0600 (MDT)
Received: from marconi.ih.lucent.com (h135-1-120-108.lucent.com [135.1.120.108])
	by auemail1.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id f85JUpc14266
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 15:30:51 -0400 (EDT)
Received: from nwsgpa.ih.lucent.com by marconi.ih.lucent.com (8.8.8+Sun/EMS-1.5 sol2)
	id OAA23926; Wed, 5 Sep 2001 14:30:51 -0500 (CDT)
Received: by nwsgpa.ih.lucent.com (8.8.8+Sun/EMS-1.5 client sol2)
	id OAA14048; Wed, 5 Sep 2001 14:30:44 -0500 (CDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15254.32099.974219.450451@nwsgpa.ih.lucent.com>
Date: Wed, 5 Sep 2001 14:30:43 -0500
From: Pete McCann <mccap@lucent.com>
To: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Low Latency Issue: Where to Run the Reverse Tunnel?
In-Reply-To: <200109051711.KAA22744@heliopolis.eng.sun.com>
References: <200109051711.KAA22744@heliopolis.eng.sun.com>
X-Mailer: VM 6.90 under 21.1 (patch 13) "Crater Lake" XEmacs Lucid
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hi, James,

James Kempf writes:
 > Hi Pete,
 > 
 > >
 > >I agree with your opinion that the reverse tunnel should go to the old
 > >FA.
 >
 > The only issue I can see with this is that routing may be suboptimal
 > when the mobile node requests a reverse tunnel from the anchor FA.

Maybe it is suboptimal, but at least it will work.  In my book this
is more-optimal than not working. :)

 > RFC 2344 has been folded into RFC2002bis, so there is now a flag
 > in the Registration Request that allows the mobile node to request
 > a reverse tunnel from the FA to the HA. RFC 2344 recommends a
 > Foreign to Home Authentication extension as the best way  to
 > protect against attacks. If such a security association is not in
 > place, it also suggests an elegant little
 > hack, requiring the mobile node to set the TTL to 255 on its
 > Registration Requests, to disallow a node more than one hop
 > away from posing as the mobile node (of course, this will not
 > stop  an attack from a node on the same subnet). 
 >
 > Naturally, if a tunnel is extended from the new FA to the HA, the same security 
 > requirements apply, except that there will be no communication with
 > the mobile node.

As I understand it, these security mechanisms protect the registration
traffic but not the data traffic.  It is possible for a malicious node
to inject traffic into the reverse tunnel if the L2 is not protected.
However, this is a problem with any Mobile IP scenario where the
visited link is accessible to untrusted nodes.  The low-latency draft
relies on trust between the neighboring FAs, but does not introduce
any new vulnerabilities as far as I am aware.  If you can inject
packets on the L2 from new FA, you could probably do it from old FA as
well.

 > With regard to the proposal I sent out yesterday, do you see any issue
 > with allowing the old FA to indicate whether the mobile node
 > has requested a tunnel to the HA, and having the new FA do the tunnel,
 > provided the proper security association is available?

I have a couple of issues with the proposal you sent out - I will
respond to it in a separate message.

 > One issue I can see is that the new FA may not be in a position to
 > do so if the proper security association is not in place. So
 > maybe rather than making the H flag a MUST, it could be made a SHOULD.
 > This would allow the new FA to optimize routing if the proper
 > security association was in place, if not, the new FA could run the
 > tunnel back to the old FA, which could take care of the reverse
 > tunnel.

Remember, it might not just be a Mobile IP security association
protecting control traffic, there might also be an IPSec security
association protecting data traffic.  It takes several round-trips to
set up one of those.  In this case tunneling data back to old FA, and
leveraging the security that is already in place there, is the fastest
(least interruption) way to get the MN's packets to their destination.

-Pete



From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep  5 15:37:35 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19841
	for <mobileip-archive@odin.ietf.org>; Wed, 5 Sep 2001 15:37:34 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA25045;
	Wed, 5 Sep 2001 12:38:41 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id MAA11650;
	Wed, 5 Sep 2001 12:38:32 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f85JZE40021577
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 5 Sep 2001 12:35:14 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0/Submit) id f85JZERq021576
	for mobile-ip-dist; Wed, 5 Sep 2001 12:35:14 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from heliopolis.eng.sun.com (bigbang.Eng.Sun.COM [152.70.8.30])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f85JZB40021569
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 12:35:11 -0700 (PDT)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.eng.sun.com (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id MAA00211
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 12:35:23 -0700 (PDT)
Message-Id: <200109051935.MAA00211@heliopolis.eng.sun.com>
Date: Wed, 5 Sep 2001 12:35:22 -0700 (PDT)
From: James Kempf <James.Kempf@Sun.COM>
Subject: Re: [mobile-ip] Low Latency Issue: Where to Run the Reverse Tunnel?
To: mobile-ip@sunroof.eng.sun.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: 58L4fYYHYSplmVZnUI+5ZA==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Pete,

Good points. I'm going to try to finish up the BETH section of the
low latency draft this week so Karim can get it integrated and we
can move the draft along.

Looking forward to your response.

		jak
		
>Date: Wed, 5 Sep 2001 14:30:43 -0500
>From: Pete McCann <mccap@lucent.com>
>To: mobile-ip@sunroof.eng.sun.com
>Subject: Re: [mobile-ip] Low Latency Issue: Where to Run the Reverse Tunnel?
>
>Hi, James,
>
>James Kempf writes:
> > Hi Pete,
> > 
> > >
> > >I agree with your opinion that the reverse tunnel should go to the old
> > >FA.
> >
> > The only issue I can see with this is that routing may be suboptimal
> > when the mobile node requests a reverse tunnel from the anchor FA.
>
>Maybe it is suboptimal, but at least it will work.  In my book this
>is more-optimal than not working. :)
>
> > RFC 2344 has been folded into RFC2002bis, so there is now a flag
> > in the Registration Request that allows the mobile node to request
> > a reverse tunnel from the FA to the HA. RFC 2344 recommends a
> > Foreign to Home Authentication extension as the best way  to
> > protect against attacks. If such a security association is not in
> > place, it also suggests an elegant little
> > hack, requiring the mobile node to set the TTL to 255 on its
> > Registration Requests, to disallow a node more than one hop
> > away from posing as the mobile node (of course, this will not
> > stop  an attack from a node on the same subnet). 
> >
> > Naturally, if a tunnel is extended from the new FA to the HA, the same 
security 
> > requirements apply, except that there will be no communication with
> > the mobile node.
>
>As I understand it, these security mechanisms protect the registration
>traffic but not the data traffic.  It is possible for a malicious node
>to inject traffic into the reverse tunnel if the L2 is not protected.
>However, this is a problem with any Mobile IP scenario where the
>visited link is accessible to untrusted nodes.  The low-latency draft
>relies on trust between the neighboring FAs, but does not introduce
>any new vulnerabilities as far as I am aware.  If you can inject
>packets on the L2 from new FA, you could probably do it from old FA as
>well.
>
> > With regard to the proposal I sent out yesterday, do you see any issue
> > with allowing the old FA to indicate whether the mobile node
> > has requested a tunnel to the HA, and having the new FA do the tunnel,
> > provided the proper security association is available?
>
>I have a couple of issues with the proposal you sent out - I will
>respond to it in a separate message.
>
> > One issue I can see is that the new FA may not be in a position to
> > do so if the proper security association is not in place. So
> > maybe rather than making the H flag a MUST, it could be made a SHOULD.
> > This would allow the new FA to optimize routing if the proper
> > security association was in place, if not, the new FA could run the
> > tunnel back to the old FA, which could take care of the reverse
> > tunnel.
>
>Remember, it might not just be a Mobile IP security association
>protecting control traffic, there might also be an IPSec security
>association protecting data traffic.  It takes several round-trips to
>set up one of those.  In this case tunneling data back to old FA, and
>leveraging the security that is already in place there, is the fastest
>(least interruption) way to get the MN's packets to their destination.
>
>-Pete
>



From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep  5 15:51:30 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20400
	for <mobileip-archive@odin.ietf.org>; Wed, 5 Sep 2001 15:51:29 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA00894;
	Wed, 5 Sep 2001 12:52:31 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id MAA15988;
	Wed, 5 Sep 2001 12:52:13 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f85Jo340021640
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 5 Sep 2001 12:50:03 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0/Submit) id f85Jo3FW021639
	for mobile-ip-dist; Wed, 5 Sep 2001 12:50:03 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f85Jnx40021632
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 12:49:59 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id MAA17114
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 12:50:10 -0700 (PDT)
Received: from auemail1.firewall.lucent.com (auemail1.lucent.com [192.11.223.161])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id NAA11145
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 13:50:07 -0600 (MDT)
Received: from marconi.ih.lucent.com (h135-1-120-108.lucent.com [135.1.120.108])
	by auemail1.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id f85Jo9c21526
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 15:50:09 -0400 (EDT)
Received: from nwsgpa.ih.lucent.com by marconi.ih.lucent.com (8.8.8+Sun/EMS-1.5 sol2)
	id OAA05453; Wed, 5 Sep 2001 14:50:08 -0500 (CDT)
Received: by nwsgpa.ih.lucent.com (8.8.8+Sun/EMS-1.5 client sol2)
	id OAA28787; Wed, 5 Sep 2001 14:50:01 -0500 (CDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15254.33256.136099.329418@nwsgpa.ih.lucent.com>
Date: Wed, 5 Sep 2001 14:50:00 -0500
From: Pete McCann <mccap@lucent.com>
To: mobile-ip@sunroof.eng.sun.com
Subject: RE: [mobile-ip] Low Latency Issue: Where to Run the Reverse Tunnel?
In-Reply-To: <200109041919.MAA12637@heliopolis.eng.sun.com>
References: <200109041919.MAA12637@heliopolis.eng.sun.com>
X-Mailer: VM 6.90 under 21.1 (patch 13) "Crater Lake" XEmacs Lucid
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hi, James,

A couple of comments on your proposal below.  Basically, I think it is
possible to do something a lot simpler - see my comments at the end.

James Kempf writes:
 > Ok, well, it seems like this issue hasn't stirred alot of comment. In
 > the interest of pushing the draft forward, I'd like to make the following
 > proposal. I think this will address Ajoy's comment about tunneling
 > compressed packets or PPP to the old FA, and also the comment in the
 > original issue summary about how to accommodate route optimization.
 > 
 > The proposal involves modifying the flag bits to indicate whether
 > the reverse tunnel should be terminated at the old FA or at the HA,
 > and whether route optimization is in effect.
 > 
 > Currently, we have 4 flag bits concerned with tunneling: M for minimal 
 > encapsulation supported, G for GRE encapsulation supported, T for reverse tunnel 
 > supported. These flag bits occur in both the Handoff Request and Handoff Reply.
 > 
 > I'd like to propose that we modify the tunneling flags as follows:
 > 
 > M - MN requested minimal encapsulation, use it in any tunnel with FA or HA

Note that the tunneling type between the FAs is really orthogonal to
the tunneling type requested by the mobile node.  See below under your
proposed 'O' flag.

 > G - MN requested GRE encapsulation, use it in any tunnel with FA or HA
 >     (must be accompanied  by the GRE Key Extension if GRE security in 
 >      effect)

This might be a misconception, and I think it was present in your
original summary: GRE Key != security.  The GRE Key field is for an
additional layer of demultiplexing.  That is all.  It is called a
"key" in the sense of an index, not in a cryptographic sense.

 > H -  MN requested reverse tunnel to HA, perform reverse tunnel regardless
 >      of egress filtering status on new subnet (the MN may be using 
 >      a private home address, for example). 
 > O - old FA is performing optimizations on MNs traffic (compression, 
 >     PPP, etc.), tunnel through the old FA regardless of egress filtering
 >      status on new subnet.

Note that to support this, we MUST have GRE tunneling between the two
FAs, and the GRE Protocol Type could be used to signal that we will be
sending already-compressed packets.  The Protocol Type is part of the
GRE Extension:

ftp://ftp.isi.edu/internet-drafts/draft-calhoun-mobileip-gre-ext-00.txt

 > R - Route optimization is in effect and the MN is using CoA as the source
 >     address. MN's old CoA included in the message instead of the MN's 
 >     home address. The O bit MUST also be set.

I don't understand the concern with route optimization.  As I recall
(the draft is expired and currently unavailable), R-O is run either
between MNs and CNs, or MNs and previous FAs.  In either case, it is a
signaling and security matter between the MN and those other nodes.
Packets are then tunneled to the MN's care-of address directly from
CNs or previous FAs, and the care-of address can be either co-located
or FA-located.  Why would the old FA know or even care whether the MN
is performing route optimization with CNs?  Why would it affect the
endpoint of the reverse tunneled traffic?  It seems like R-O only
affects the path taken by forward direction traffic.

 > The reverse tunnel termination point would be decided by the following
 > algorithm:
 > 
 >   If the H flag is set, the new FA MUST reverse tunnel to the HA regardless of
 >   the egress filtering status on the new subnet. This is because the
 >   MN requested reverse tunneling.
 >   
 >   If the O flag is set, the old FA is performing optimizations, such
 >   as compression, and therefore the new FA MUST reverse tunnel to
 >   the old FA regardless of the egress filtering status because the
 >   old FA must perform processing before the packets can be sent. This
 >   flag MUST also be set if the R flag is on, indicating that the 
 >   MN is performing route optimization.
 >   
 >   If neither the H nor the O flag are set, then the new FA can reverse tunnel
 >   to the HA, reverse tunnel to the old FA, or it can simply route packets
 >   directly onto its subnet if egress filtering is not on.
 >   
 > Note that if the new FA does NOT want to perform reverse tunneling but
 > the MN did not request reverse tunneling, the H flag MUST NOT be set.
 > The new FA indicates its unwillingness to reverse tunnel by 
 > a tunnel lifetime of zero in the Handoff Request or Handoff Reply, this 
 > indication applies to forward tunneling also.
 > 
 > If the R flag is set, the old FA sends the MN's old Care of Address
 > in place of the MN's Home Address, since the source address on
 > outgoing packets will be the MN's old Care of Address. The MN's 
 > HA address is also sent.
 > 
 > Comments?

This seems quite complicated.  I would rather just use the 'T' bit
that we already have in the Handoff Request/Reply to signal the desire
by either side to reverse-tunnel packets to the old FA.  If
either of them set this bit, then reverse tunnel to the old FA is
enabled.  Either side could set the bit for whatever reason seemed
aprpropriate.

Now, there is an orthogonal question, which is, when we are NOT
performing reverse tunneling to old FA, we may or may not need to
reverse tunnel to the HA.  This could be one flag from the old FA to
the new FA (in either Request or Reply, depending on the trigger type)
indicating that the FA is currently supporting a reverse tunnel to the
HA, and that there is currently no security on this tunnel, and the
new FA SHOULD choose to do so as well.

I think the addition of one new flag such as this, rather than
redefining all the flags and adding 2 new flags, will cover the cases
we want to cover adequately, and conveys exactly the information we
want conveyed.  In other words, the flags in the Handoff messages
apply to the tunnels established with those messages, not to other
tunnels that may appear as side effects of the handoff.

In summary: I think your R and O bits could be combined into the
current T bit.  I would agree with adding an H bit as a form of advice
from the old FA to the new FA, but it may only be set when the T bit
is not set.

-Pete




From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep  5 15:52:35 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20454
	for <mobileip-archive@odin.ietf.org>; Wed, 5 Sep 2001 15:52:34 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id NAA13829;
	Wed, 5 Sep 2001 13:53:34 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id MAA16379;
	Wed, 5 Sep 2001 12:53:23 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f85JqE40021660
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 5 Sep 2001 12:52:14 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0/Submit) id f85JqDw9021659
	for mobile-ip-dist; Wed, 5 Sep 2001 12:52:13 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f85Jq940021652
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 12:52:09 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id MAA12705;
	Wed, 5 Sep 2001 12:52:20 -0700 (PDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id MAA11963;
	Wed, 5 Sep 2001 12:52:20 -0700 (PDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id MAA16606;
	Wed, 5 Sep 2001 12:52:19 -0700 (PDT)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f85JqIe10931;
	Wed, 5 Sep 2001 12:52:18 -0700
X-mProtect:  Wed, 5 Sep 2001 12:52:18 -0700 Nokia Silicon Valley Messaging Protection
Received: from charliep.iprg.nokia.com (205.226.2.89, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpdNLeVBX; Wed, 05 Sep 2001 12:52:16 PDT
Message-ID: <3B968269.9C4897CE@iprg.nokia.com>
Date: Wed, 05 Sep 2001 12:52:09 -0700
From: "Charles E. Perkins" <charliep@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Alper Yegin <Alper.Yegin@eng.sun.com>
CC: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Coexistence with other uses for routing header
References: <200109051834.f85IYn9d410758@jurassic.eng.sun.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hello folks,

For the purposes of what to put into the revised specification,
I think the main result of the recent discussion would be that
the mobile node's home address does not have to be the last stop
along the source route indicated in a routing header.  This part
of the revision should not be the deciding factor in any
specification about mobile routers or further route optimization,
and so I have reformulated the paragraph as follows:

     It is possible that a correspondent node, having no knowledge of the
     mobile node's care-of address, would still (for reasons unspecified
     here but not necessarily related to mobility) attempt to deliver a 
     packet, either to or by way of the mobile node's home address,
     by using a routing header.  If the correspondent node subsequently
     accepts a Binding Update and creates a Binding Cache entry for the
     mobile node, then afterwards, the routing header used by the
     corresponding node which includes the mobile node's home address
     SHOULD also include the mobile node's care-of address.
     The correspondent node SHOULD put the mobile node's care-of address
     as the intermediate node address immediately preceding the
     mobile node's home address.  When the care-of address is the
     first intermediate node address, this implies that the care-of
     address is to be placed in the Destination Address of the IPv6
     headerd, and the mobile node's home address is the first entry
     in the type 0 routing header.  Otherwise, the correspondent 
     node MUST place the mobile node's home address immediately 
     after the care-of address entry of the routing header, following
     all other intermediate node addresses that would have
     already been in the routing header before the creation
     of the Binding Cache entry for the care-of address.

I hope this is better.

Regards,
Charlie P.


From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep  5 15:58:12 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20628
	for <mobileip-archive@odin.ietf.org>; Wed, 5 Sep 2001 15:58:11 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id NAA18036;
	Wed, 5 Sep 2001 13:59:13 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id MAA18012;
	Wed, 5 Sep 2001 12:59:08 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f85Jw040021740
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 5 Sep 2001 12:58:00 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0/Submit) id f85Jw0dG021739
	for mobile-ip-dist; Wed, 5 Sep 2001 12:58:00 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f85Jvu40021732
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 12:57:56 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id MAA17853
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 12:58:07 -0700 (PDT)
Received: from mgw-dax1.ext.nokia.com (mgw-dax1.ext.nokia.com [63.78.179.216])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA22423
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 13:58:42 -0600 (MDT)
Received: from davir03nok.americas.nokia.com (davir03nok.americas.nokia.com [172.18.242.86])
	by mgw-dax1.ext.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f85Jw5o08827
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 14:58:05 -0500 (CDT)
Received: from daebh002.NOE.Nokia.com (unverified) by davir03nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T55cf48f615ac12f256126@davir03nok.americas.nokia.com> for <mobile-ip@sunroof.eng.sun.com>;
 Wed, 5 Sep 2001 14:58:05 -0500
Received: from daebe007.NOE.Nokia.com ([172.18.242.211]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.2966);
	 Wed, 5 Sep 2001 14:58:05 -0500
content-class: urn:content-classes:message
Subject: [mobile-ip] RFC2002bis and MIER
Date: Wed, 5 Sep 2001 14:57:19 -0500
Message-ID: <697DAA22C5004B4596E033803A7CEF441E85C3@daebe007.NOE.Nokia.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0
Thread-Topic: RFC2002bis and MIER
Thread-Index: AcE2Q6WEKVdWhqIqEdWwsAAAhj/HZA==
From: "Patil Basavaraj (NET/Dallas)" <Basavaraj.Patil@nokia.com>
To: "'Mobile IP'" <mobile-ip@sunroof.eng.sun.com>
X-OriginalArrivalTime: 05 Sep 2001 19:58:05.0176 (UTC) FILETIME=[138D5F80:01C13645]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by sunroof.eng.sun.com id f85Jvu40021733
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 8bit

Hello,

We would like to incorporate the format for extensions specified in
MIER into the RFC2002bis I-D and eliminate the MIER draft as a 
WG document. Comments/Opinions?

Phil had sent a note to the list earlier with detailed feedback from the
IESG which failed to elicit any response from WG members.

Regards,
-Basavaraj


From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep  5 16:18:52 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21234
	for <mobileip-archive@odin.ietf.org>; Wed, 5 Sep 2001 16:18:51 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id OAA04465;
	Wed, 5 Sep 2001 14:19:53 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id NAA23917;
	Wed, 5 Sep 2001 13:19:45 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f85KIa40021835
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 5 Sep 2001 13:18:36 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0/Submit) id f85KIaQ0021832
	for mobile-ip-dist; Wed, 5 Sep 2001 13:18:36 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from heliopolis.eng.sun.com (redcoast.Eng.Sun.COM [152.70.28.21])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f85KIW40021825
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 13:18:32 -0700 (PDT)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.eng.sun.com (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id NAA02268
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 13:18:44 -0700 (PDT)
Message-Id: <200109052018.NAA02268@heliopolis.eng.sun.com>
Date: Wed, 5 Sep 2001 13:18:43 -0700 (PDT)
From: James Kempf <James.Kempf@Sun.COM>
Subject: Re: [mobile-ip] RFC2002bis and MIER
To: mobile-ip@sunroof.eng.sun.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: EfumznFAkNJGBSIrmraz7Q==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

>
>We would like to incorporate the format for extensions specified in
>MIER into the RFC2002bis I-D and eliminate the MIER draft as a 
>WG document. Comments/Opinions?
>
>Phil had sent a note to the list earlier with detailed feedback from the
>IESG which failed to elicit any response from WG members.
>

Actually, I responded and said that I favored the proposal.

		jak



From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep  5 16:18:54 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21245
	for <mobileip-archive@odin.ietf.org>; Wed, 5 Sep 2001 16:18:54 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id OAA04282;
	Wed, 5 Sep 2001 14:19:42 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id NAA23886;
	Wed, 5 Sep 2001 13:19:32 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f85KHx40021820
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 5 Sep 2001 13:17:59 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0/Submit) id f85KHx8Q021819
	for mobile-ip-dist; Wed, 5 Sep 2001 13:17:59 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from heliopolis.eng.sun.com (redhook.Eng.Sun.COM [152.70.24.37])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f85KHt40021812
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 13:17:55 -0700 (PDT)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.eng.sun.com (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id NAA02247
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 13:18:07 -0700 (PDT)
Message-Id: <200109052018.NAA02247@heliopolis.eng.sun.com>
Date: Wed, 5 Sep 2001 13:18:06 -0700 (PDT)
From: James Kempf <James.Kempf@Sun.COM>
Subject: RE: [mobile-ip] Low Latency Issue: Where to Run the Reverse Tunnel?
To: mobile-ip@sunroof.eng.sun.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: Tq+4/dCxzO7adlRogb4ggw==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Hi Pete,

In general, I like your proposal, as it is alot simpler, but there
are a few points I think we still need to clear up.


>Note that the tunneling type between the FAs is really orthogonal to
>the tunneling type requested by the mobile node.  See below under your
>proposed 'O' flag.
>

OK.

> > G - MN requested GRE encapsulation, use it in any tunnel with FA or HA
> >     (must be accompanied  by the GRE Key Extension if GRE security in 
> >      effect)
>
>This might be a misconception, and I think it was present in your
>original summary: GRE Key != security.  The GRE Key field is for an
>additional layer of demultiplexing.  That is all.  It is called a
>"key" in the sense of an index, not in a cryptographic sense.
>

OK, sorry. I misread the GRE draft. Should go back and check it again.

> > O - old FA is performing optimizations on MNs traffic (compression, 
> >     PPP, etc.), tunnel through the old FA regardless of egress filtering
> >      status on new subnet.
>
>Note that to support this, we MUST have GRE tunneling between the two
>FAs, and the GRE Protocol Type could be used to signal that we will be
>sending already-compressed packets.  The Protocol Type is part of the
>GRE Extension:
>
>ftp://ftp.isi.edu/internet-drafts/draft-calhoun-mobileip-gre-ext-00.txt
>

I will check out the reference. 

> > R - Route optimization is in effect and the MN is using CoA as the source
> >     address. MN's old CoA included in the message instead of the MN's 
> >     home address. The O bit MUST also be set.
>
>I don't understand the concern with route optimization.  As I recall
>(the draft is expired and currently unavailable), R-O is run either
>between MNs and CNs, or MNs and previous FAs.  In either case, it is a
>signaling and security matter between the MN and those other nodes.
>Packets are then tunneled to the MN's care-of address directly from
>CNs or previous FAs, and the care-of address can be either co-located
>or FA-located.  Why would the old FA know or even care whether the MN
>is performing route optimization with CNs?  Why would it affect the
>endpoint of the reverse tunneled traffic?  It seems like R-O only
>affects the path taken by forward direction traffic.
>

My concern was that packets originating at the MN will be
sent with the source address set to the care of address and
not the home address, as would be the case if no route optimization
were in effect. The current version of HRqst/HRply has the old
FA sending the mobile node's home address and the HA address
in the HRqst/HRply. If the new FA uses the source address to
decide whether to send the packets down the reverse tunnel,
it will not have the right source address with route optimization.
As you point out, there is an issue with the old FA discovering
that route optimization is in effect, and since the draft has expired,
it is not possible at this time to check whether that is covered.

I think this case can be handled by having the new FA use the
mobile node's L2 address to decide whether to send the packets
down the reverse tunnel to the old FA. This won't change regardless
of whether route optimization is used or not, and the new FA
will have that either from the L2 trigger or as a result of
the HRqst(s).

>This seems quite complicated.  I would rather just use the 'T' bit
>that we already have in the Handoff Request/Reply to signal the desire
>by either side to reverse-tunnel packets to the old FA.  If
>either of them set this bit, then reverse tunnel to the old FA is
>enabled.  Either side could set the bit for whatever reason seemed
>aprpropriate.
>

I'm certainly in favor of simplification. In addition, I think
we need to note what you mentioned above that the G bit MUST
be set if the old FA is doing optimizations (compression, PPP, etc.),
and the GRE Protocol Type needs to be set appropriately, as an
additional extension.

>Now, there is an orthogonal question, which is, when we are NOT
>performing reverse tunneling to old FA, we may or may not need to
>reverse tunnel to the HA.  This could be one flag from the old FA to
>the new FA (in either Request or Reply, depending on the trigger type)
>indicating that the FA is currently supporting a reverse tunnel to the
>HA, and that there is currently no security on this tunnel, and the
>new FA SHOULD choose to do so as well.
>

I think saying there is no security is a bit strong, there
could be security, it could be prearranged via context transfer
or even some configuration step. I think it would be more precise
to say that the new FA is not expected to set up a security 
association in real time during the handover, but that it SHOULD,
at its discretion, choose to support a reverse tunnel as well.

>I think the addition of one new flag such as this, rather than
>redefining all the flags and adding 2 new flags, will cover the cases
>we want to cover adequately, and conveys exactly the information we
>want conveyed.  In other words, the flags in the Handoff messages
>apply to the tunnels established with those messages, not to other
>tunnels that may appear as side effects of the handoff.
>
>In summary: I think your R and O bits could be combined into the
>current T bit.  I would agree with adding an H bit as a form of advice
>from the old FA to the new FA, but it may only be set when the T bit
>is not set.
>

Agreed. Unless there are any other comments, I will write up the
BETH part of low latency with this. 

		jak



From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep  5 16:21:10 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21338
	for <mobileip-archive@odin.ietf.org>; Wed, 5 Sep 2001 16:21:09 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id OAA06543;
	Wed, 5 Sep 2001 14:22:07 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id NAA24431;
	Wed, 5 Sep 2001 13:21:55 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f85KKO40021871
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 5 Sep 2001 13:20:24 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0/Submit) id f85KKOct021870
	for mobile-ip-dist; Wed, 5 Sep 2001 13:20:24 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f85KKJ40021863
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 13:20:19 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id NAA21298;
	Wed, 5 Sep 2001 13:20:30 -0700 (PDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id OAA05107;
	Wed, 5 Sep 2001 14:20:27 -0600 (MDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id NAA18966;
	Wed, 5 Sep 2001 13:20:28 -0700 (PDT)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f85KKSS29244;
	Wed, 5 Sep 2001 13:20:28 -0700
X-mProtect:  Wed, 5 Sep 2001 13:20:28 -0700 Nokia Silicon Valley Messaging Protection
Received: from charliep.iprg.nokia.com (205.226.2.89, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpdM6qD4P; Wed, 05 Sep 2001 13:20:20 PDT
Message-ID: <3B968905.F296AA68@iprg.nokia.com>
Date: Wed, 05 Sep 2001 13:20:21 -0700
From: "Charles E. Perkins" <charliep@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Alper Yegin <Alper.Yegin@eng.sun.com>
CC: Mobile IP Working Group <mobile-ip@sunroof.eng.sun.com>
Subject: [mobile-ip] Re: from Connectathon 2001
References: <200109051958.MAA12653@charliep.iprg.nokia.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hello Alper,

Sorry these points didn't make it into revision ...-14, and thanks
to your reminder for inclusion into revision ...-15.

> Date: Fri, 6 Apr 2001 18:12:30 -0700 (PDT)
> From: Alper Yegin <Alper.Yegin@eng.sun.com>

> For the second year Connectathon covered testing both Mobile IPv4 and Mobile
> IPv6 protocols. During the event, Mobile IP participants got together to
> discuss specification related issues. We came up with a number of them,
> which was outlined in the Connectathon presentation given by Carl Williams
> and myself at IETF 50.
> 
> Here's a recapture of Mobile IPv6 spec issues, for those who weren't at the
> IETF meeting (in case they have comments), and for the Mobile IPv6 draft authors
> to incorporate these into the next revision of the draft.


> [1] Movement detection (section 10.4)
> 
>    ... Instead,
>    a mobile node SHOULD consider receipt of any IPv6 packets from its
>    current default router as an indication that it is still reachable
>    from the router.  Both packets from the router's IP address and
>    (IPv6) packets from its link-layer address (e.g., those forwarded but
>    not originated by the router) SHOULD be considered.
> 
> Draft suggests that receiving packets from a node with same link-layer
> address and IP address as current default router means that mobile node
> is still attached to the same link.
> 
> BUT, different interfaces of the same router can have the same MAC address,
> therefore same link-local address but advertise different prefixes. In this
> case, mobile node would fail to detect movement if it only looks at the
> source MAC and IP address of packets.
> 
> Therefore draft should not suggest a match on source MAC address and IP
> address is sufficient.

What if we mandate that the routing prefixes must also be considered?


> [2] Sending binding acknowledgement for failed binding updates (section 5.2)
> 
>    Rather, the care-of address used by this node in
>    sending the packet containing the Binding Acknowledgement MUST be
>    copied from the care-of address received in the rejected Binding
>    Update; ...
> 
> Draft says receiving node MUST send a binding acknowledgement for failed
> binding updates. It also says the care-of address MUST be copied from the
> failed binding update.
> 
> BUT in the case care-of address is an invalid address such as multicast
> or unspecified address, such an address should not be used as the care-of
> address in binding acknowledgement.

Correct!


> Draft can be updated to say:
> - If we have received this binding update as a home agent, we MUST not send
>   a binding acknowledgement
> - If we have received this binding update as a correspondent node, we MUST
>   send the binding acknowledgement to home address (or not send at all?)

I assume that you meant in the case where the care-of address is
a prohibited destination.  Should we also exclude link-local
care-of addresses?


> [3] Home agent address discovery request message (section 5.6)
> 
> Home Agent Address Discovery Request Message includes the Home Address
> field. This information is used by the receiving home agent to return
> the list of home agents matching the prefix of the mobile node.
> 
> This request packet is sent to "Mobile IPv6 Home-Agents" anycast address for
> its own home subnet prefix.
> 
> The receiving home agent can figure out the prefix of the mobile node just
> by looking at the destination address of the request packet. Therefore Home
> Address field in the request message is not needed in the draft.

This is O.K. with me -- at least I don't see anything wrong with
it off the top of my head without re-reading all the relevant parts
of the specification.


> [4] ICMPs can delete binding cache (section 8.8)
> 
>    If the correspondent node
>    receives persistent ICMP Destination Unreachable messages after
>    sending packets to a mobile node based on an entry in its Binding
>    Cache, the correspondent node SHOULD delete this Binding Cache
>    entry.
> 
> The only way binding cache entries can be deleted is through binding updates
> and persistent ICMP unreachables. The former is required to be authenticated,
> but not the latter. The draft should have a proper warning about this, as
> unauthenticated ICMP messages can be used for DoS attacks.

I agree that this should be indicated in the draft.  Probably the right
place for it is within the Security Considerations section.


> [5] Deregistering a care-of address (section 8.5)
> 
> The draft says that binding acknowledgement MUST be sent using a routing
> header in the same way as any other packet sent to a mobile node using a
> care-of address.
> 
> BUT, what should be the care-of address used in the case this was a
> deregistration? Draft should specify that it MUST be the care-of address
> used in the triggering binding update. (similarly, draft already specifies
> that for failed binding updates case).

O.K.  Will do.

Regards,
Charlie P.


From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep  5 16:29:21 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21490
	for <mobileip-archive@odin.ietf.org>; Wed, 5 Sep 2001 16:29:20 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id OAA12749;
	Wed, 5 Sep 2001 14:30:26 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id NAA27201;
	Wed, 5 Sep 2001 13:30:19 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f85KSl40021954
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 5 Sep 2001 13:28:47 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0/Submit) id f85KSlRh021953
	for mobile-ip-dist; Wed, 5 Sep 2001 13:28:47 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f85KSh40021946
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 13:28:43 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id NAA27487
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 13:28:55 -0700 (PDT)
Received: from mgw-dax1.ext.nokia.com (mgw-dax1.ext.nokia.com [63.78.179.216])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id NAA29708
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 13:28:54 -0700 (PDT)
Received: from davir04nok.americas.nokia.com (davir04nok.americas.nokia.com [172.18.242.87])
	by mgw-dax1.ext.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f85KSso11231
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 15:28:54 -0500 (CDT)
Received: from daebh002.NOE.Nokia.com (unverified) by davir04nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T55cf652c28ac12f257079@davir04nok.americas.nokia.com> for <mobile-ip@sunroof.eng.sun.com>;
 Wed, 5 Sep 2001 15:28:54 -0500
Received: from daebe007.NOE.Nokia.com ([172.18.242.211]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.2966);
	 Wed, 5 Sep 2001 15:28:53 -0500
content-class: urn:content-classes:message
Subject: RE: [mobile-ip] RFC2002bis and MIER
Date: Wed, 5 Sep 2001 15:21:35 -0500
Message-ID: <697DAA22C5004B4596E033803A7CEF441E85CE@daebe007.NOE.Nokia.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0
Thread-Topic: [mobile-ip] RFC2002bis and MIER
Thread-Index: AcE2SCEwu+Hjh6I6EdWBSQBQi2X+DwAADnHw
From: "Patil Basavaraj (NET/Dallas)" <Basavaraj.Patil@nokia.com>
To: <mobile-ip@sunroof.eng.sun.com>
X-OriginalArrivalTime: 05 Sep 2001 20:28:53.0954 (UTC) FILETIME=[61828220:01C13649]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by sunroof.eng.sun.com id f85KSi40021947
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 8bit

Thanks James, but you were the only person that responded :)

I think that this WG has at least a few more interested members.

> >
> >We would like to incorporate the format for extensions specified in
> >MIER into the RFC2002bis I-D and eliminate the MIER draft as a 
> >WG document. Comments/Opinions?
> >
> >Phil had sent a note to the list earlier with detailed 
> feedback from the
> >IESG which failed to elicit any response from WG members.
> >
> 
> Actually, I responded and said that I favored the proposal.
> 
> 		jak
> 


From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep  5 17:50:46 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAB23180
	for <mobileip-archive@odin.ietf.org>; Wed, 5 Sep 2001 17:50:46 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id PAA17246;
	Wed, 5 Sep 2001 15:51:46 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id OAA21483;
	Wed, 5 Sep 2001 14:51:40 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f85LoY40022131
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 5 Sep 2001 14:50:34 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0/Submit) id f85LoYPv022130
	for mobile-ip-dist; Wed, 5 Sep 2001 14:50:34 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from jurassic.eng.sun.com (jurassic [129.146.86.31] (may be forged))
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f85LoV40022123
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 14:50:31 -0700 (PDT)
Received: from istanbul.Eng.Sun.COM (istanbul.Eng.Sun.COM [129.146.86.247])
	by jurassic.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with SMTP id f85Loh9d445394
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 14:50:43 -0700 (PDT)
Message-Id: <200109052150.f85Loh9d445394@jurassic.eng.sun.com>
Date: Wed, 5 Sep 2001 14:50:45 -0700 (PDT)
From: Alper Yegin <Alper.Yegin@eng.sun.com>
Subject: Re: [mobile-ip] Coexistence with other uses for routing header
To: mobile-ip@sunroof.eng.sun.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: Y2qGBpBI0JmedasBsnNhZA==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4_37 SunOS 5.8.1 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

> Alper Yegin writes:
>  > Mobile node doesn't have to be a "router", it just needs to "forward" the 
packet 
>  > though. It's just like when it forwards the packet to itself when the 
>  > destination of a packet is CoA and the next hop is Home_Address.
>  > 
>  > I can't think of any application that needs this right now, but I think the 
>  > practice was to allow future protocols using routing header work with route 
>  > optimization.
> 
>    We're probably off in the definitional weeds here,

I think so :)

>    but I'd think that something that moves packets
>    toward their destination instead of toward
>    themselves is acting like a router, regardless
>    of what caused them to do so. Practically
>    speaking, I'd sure like some knob -- like the
>    router on/off switch -- which controls whether
>    my node acts as a forwarder regardless of how
>    something is trying to get me to forward.

For example Solaris has a "ip_forwarding" knob. Only when it is turned on, the 
box starts forwarding packets. It doesn't necessarily have to be running any 
"routing protocol" at this point (RIP, etc.). It can do forwarding using minimal 
routing table that contains on-link routes and default route.


alper



From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep  5 17:53:15 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23214
	for <mobileip-archive@odin.ietf.org>; Wed, 5 Sep 2001 17:53:15 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id PAA19257;
	Wed, 5 Sep 2001 15:54:20 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id OAA22369;
	Wed, 5 Sep 2001 14:54:12 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f85LrJ40022174
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 5 Sep 2001 14:53:19 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0/Submit) id f85LrJTn022173
	for mobile-ip-dist; Wed, 5 Sep 2001 14:53:19 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from jurassic.eng.sun.com (jurassic [129.146.87.31] (may be forged))
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f85LrF40022166
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 14:53:15 -0700 (PDT)
Received: from istanbul.Eng.Sun.COM (istanbul.Eng.Sun.COM [129.146.86.247])
	by jurassic.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with SMTP id f85LrS9d446007
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 14:53:28 -0700 (PDT)
Message-Id: <200109052153.f85LrS9d446007@jurassic.eng.sun.com>
Date: Wed, 5 Sep 2001 14:53:29 -0700 (PDT)
From: Alper Yegin <Alper.Yegin@eng.sun.com>
Subject: Re: [mobile-ip] Coexistence with other uses for routing header
To: mobile-ip@sunroof.eng.sun.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: llOUr93PfhetRQySq5bjwA==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4_37 SunOS 5.8.1 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

> Hello folks,
> 
> For the purposes of what to put into the revised specification,
> I think the main result of the recent discussion would be that
> the mobile node's home address does not have to be the last stop
> along the source route indicated in a routing header.  This part
> of the revision should not be the deciding factor in any
> specification about mobile routers or further route optimization,
> and so I have reformulated the paragraph as follows:
> 
>      It is possible that a correspondent node, having no knowledge of the
>      mobile node's care-of address, would still (for reasons unspecified
>      here but not necessarily related to mobility) attempt to deliver a 
>      packet, either to or by way of the mobile node's home address,
>      by using a routing header.  If the correspondent node subsequently
>      accepts a Binding Update and creates a Binding Cache entry for the
>      mobile node, then afterwards, the routing header used by the
>      corresponding node which includes the mobile node's home address
>      SHOULD also include the mobile node's care-of address.
>      The correspondent node SHOULD put the mobile node's care-of address
>      as the intermediate node address immediately preceding the
>      mobile node's home address.  When the care-of address is the
>      first intermediate node address, this implies that the care-of
>      address is to be placed in the Destination Address of the IPv6
>      headerd, and the mobile node's home address is the first entry
>      in the type 0 routing header.  Otherwise, the correspondent 
>      node MUST place the mobile node's home address immediately 
>      after the care-of address entry of the routing header, following
>      all other intermediate node addresses that would have
>      already been in the routing header before the creation
>      of the Binding Cache entry for the care-of address.
> 
> I hope this is better.

Yes, this looks good.

alper



From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep  5 17:57:36 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23270
	for <mobileip-archive@odin.ietf.org>; Wed, 5 Sep 2001 17:57:35 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id PAA22493;
	Wed, 5 Sep 2001 15:58:45 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id OAA23650;
	Wed, 5 Sep 2001 14:58:42 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f85Lvk40022224
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 5 Sep 2001 14:57:46 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0/Submit) id f85LvjVq022223
	for mobile-ip-dist; Wed, 5 Sep 2001 14:57:45 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f85Lvf40022216
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 14:57:41 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id OAA20488
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 14:57:54 -0700 (PDT)
Received: from motgate3.mot.com (motgate3.mot.com [144.189.100.103])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id PAA24742
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 15:58:27 -0600 (MDT)
Received: [from mothost.mot.com (mothost.mot.com [129.188.137.101]) by motgate3.mot.com (motgate3 2.1) with ESMTP id OAA14097 for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 14:49:52 -0700 (MST)]
Received: [from il27exb01.cig.mot.com (il27exb01.cig.mot.com [136.182.15.100]) by mothost.mot.com (MOT-mothost 2.0) with ESMTP id OAA16316 for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 14:57:52 -0700 (MST)]
Received: by il27exb01.cig.mot.com with Internet Mail Service (5.5.2654.52)
	id <SCC2L785>; Wed, 5 Sep 2001 16:57:52 -0500
Message-ID: <35DBB8B7AC89D4118E98009027B1009B017A9FC6@IL27EXM10.cig.mot.com>
From: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>
To: "'mobile-ip@sunroof.eng.sun.com'" <mobile-ip@sunroof.eng.sun.com>
Subject: [mobile-ip] question on BET tear down
Date: Wed, 5 Sep 2001 16:57:51 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2654.52)
Content-Type: text/plain
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

James and other authors of BETH,

I have a couple of  questions regarding BET tear down:

In section 3.2 it says:

" Once the BET between oCoA and nCoA is in place, it is torn down by 
   one of the following events: ...."

what does a  tunnel between oCoA and nCoA mean here? Do you mean the 
BET between oAR and nAR?

The second event in that same section is

" 2) The MN begins the process of obtaining an nCoA through nAR. 
        This may include either stateless or stateful address 
        configuration. In this case, nAR sends a HRqst(r) with the MN's 
        home address, oCoA, and the R bit set, and the Lifetime field 
        set to zero, indicating that tunneling service is no longer 
        required. The nAR and aAR may elect to postpone terminating 
        tunneling service for some period of time to allow propogation 
        of the MN's nCoA to the HA and CNs. 
 "

My question is, what would the lifetime be set to, if the nAR and aAR
elect to postpone terminating tunneling service?


Thanks,
Madjid


    


From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep  5 17:59:23 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23305
	for <mobileip-archive@odin.ietf.org>; Wed, 5 Sep 2001 17:59:23 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id PAA01489;
	Wed, 5 Sep 2001 15:00:11 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id OAA24252;
	Wed, 5 Sep 2001 14:59:58 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f85Lx440022244
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 5 Sep 2001 14:59:04 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0/Submit) id f85Lx3VZ022243
	for mobile-ip-dist; Wed, 5 Sep 2001 14:59:03 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from jurassic.eng.sun.com (jurassic [129.146.87.31] (may be forged))
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f85Lwx40022236
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 14:58:59 -0700 (PDT)
Received: from istanbul.Eng.Sun.COM (istanbul.Eng.Sun.COM [129.146.86.247])
	by jurassic.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with SMTP id f85LxC9d447038
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 14:59:12 -0700 (PDT)
Message-Id: <200109052159.f85LxC9d447038@jurassic.eng.sun.com>
Date: Wed, 5 Sep 2001 14:59:14 -0700 (PDT)
From: Alper Yegin <Alper.Yegin@eng.sun.com>
Subject: Re: [mobile-ip] Re: from Connectathon 2001
To: mobile-ip@sunroof.eng.sun.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: L0b7o3Du/eZXNWpf8wHb6Q==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4_37 SunOS 5.8.1 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Hi Charlie,


> > [1] Movement detection (section 10.4)
> > 
> >    ... Instead,
> >    a mobile node SHOULD consider receipt of any IPv6 packets from its
> >    current default router as an indication that it is still reachable
> >    from the router.  Both packets from the router's IP address and
> >    (IPv6) packets from its link-layer address (e.g., those forwarded but
> >    not originated by the router) SHOULD be considered.
> > 
> > Draft suggests that receiving packets from a node with same link-layer
> > address and IP address as current default router means that mobile node
> > is still attached to the same link.
> > 
> > BUT, different interfaces of the same router can have the same MAC address,
> > therefore same link-local address but advertise different prefixes. In this
> > case, mobile node would fail to detect movement if it only looks at the
> > source MAC and IP address of packets.
> > 
> > Therefore draft should not suggest a match on source MAC address and IP
> > address is sufficient.
> 
> What if we mandate that the routing prefixes must also be considered?

Yes, that should do.

> 
> 
> > [2] Sending binding acknowledgement for failed binding updates (section 5.2)
> > 
> >    Rather, the care-of address used by this node in
> >    sending the packet containing the Binding Acknowledgement MUST be
> >    copied from the care-of address received in the rejected Binding
> >    Update; ...
> > 
> > Draft says receiving node MUST send a binding acknowledgement for failed
> > binding updates. It also says the care-of address MUST be copied from the
> > failed binding update.
> > 
> > BUT in the case care-of address is an invalid address such as multicast
> > or unspecified address, such an address should not be used as the care-of
> > address in binding acknowledgement.
> 
> Correct!
> 
> 
> > Draft can be updated to say:
> > - If we have received this binding update as a home agent, we MUST not send
> >   a binding acknowledgement
> > - If we have received this binding update as a correspondent node, we MUST
> >   send the binding acknowledgement to home address (or not send at all?)
> 
> I assume that you meant in the case where the care-of address is
> a prohibited destination. 

Yes.

> Should we also exclude link-local
> care-of addresses?
> 

I can't think of why a MN would use a link-local CoA, but I can't see a problem 
with this either. Unless somebody see a problem, I'd think link-local is fine.


> 
> > [3] Home agent address discovery request message (section 5.6)
> > 
> > Home Agent Address Discovery Request Message includes the Home Address
> > field. This information is used by the receiving home agent to return
> > the list of home agents matching the prefix of the mobile node.
> > 
> > This request packet is sent to "Mobile IPv6 Home-Agents" anycast address for
> > its own home subnet prefix.
> > 
> > The receiving home agent can figure out the prefix of the mobile node just
> > by looking at the destination address of the request packet. Therefore Home
> > Address field in the request message is not needed in the draft.
> 
> This is O.K. with me -- at least I don't see anything wrong with
> it off the top of my head without re-reading all the relevant parts
> of the specification.
> 
> 
> > [4] ICMPs can delete binding cache (section 8.8)
> > 
> >    If the correspondent node
> >    receives persistent ICMP Destination Unreachable messages after
> >    sending packets to a mobile node based on an entry in its Binding
> >    Cache, the correspondent node SHOULD delete this Binding Cache
> >    entry.
> > 
> > The only way binding cache entries can be deleted is through binding updates
> > and persistent ICMP unreachables. The former is required to be 
authenticated,
> > but not the latter. The draft should have a proper warning about this, as
> > unauthenticated ICMP messages can be used for DoS attacks.
> 
> I agree that this should be indicated in the draft.  Probably the right
> place for it is within the Security Considerations section.

Yes.

> 
> 
> > [5] Deregistering a care-of address (section 8.5)
> > 
> > The draft says that binding acknowledgement MUST be sent using a routing
> > header in the same way as any other packet sent to a mobile node using a
> > care-of address.
> > 
> > BUT, what should be the care-of address used in the case this was a
> > deregistration? Draft should specify that it MUST be the care-of address
> > used in the triggering binding update. (similarly, draft already specifies
> > that for failed binding updates case).
> 
> O.K.  Will do.
> 
> Regards,
> Charlie P.

Thanks Charlie!

alper



From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep  5 18:02:46 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA23391
	for <mobileip-archive@odin.ietf.org>; Wed, 5 Sep 2001 18:02:45 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id QAA27209;
	Wed, 5 Sep 2001 16:03:54 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id PAA25595;
	Wed, 5 Sep 2001 15:03:50 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f85M2j40022324
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 5 Sep 2001 15:02:45 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0/Submit) id f85M2jCu022323
	for mobile-ip-dist; Wed, 5 Sep 2001 15:02:45 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f85M2e40022316
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 15:02:40 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id PAA22264
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 15:02:52 -0700 (PDT)
Received: from ftpbox.mot.com (ftpbox.mot.com [129.188.136.101])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id QAA26970
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 16:03:26 -0600 (MDT)
Received: [from pobox2.mot.com (pobox2.mot.com [136.182.15.8]) by ftpbox.mot.com (ftpbox 2.1) with ESMTP id PAA04214 for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 15:02:51 -0700 (MST)]
Received: [from il27exm07.cig.mot.com (IL27EXM07.cig.mot.com [136.182.15.116]) by pobox2.mot.com (MOT-pobox2 2.0) with ESMTP id PAA20515 for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 15:02:51 -0700 (MST)]
Received: by IL27EXM07.cig.mot.com with Internet Mail Service (5.5.2654.52)
	id <RPK6LJ4F>; Wed, 5 Sep 2001 17:02:51 -0500
Message-ID: <35DBB8B7AC89D4118E98009027B1009B017A9FC7@IL27EXM10.cig.mot.com>
From: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>
To: "'mobile-ip@sunroof.eng.sun.com'" <mobile-ip@sunroof.eng.sun.com>
Cc: charliep@iprg.nokia.com
Subject: RE: [mobile-ip] RFC2002bis
Date: Wed, 5 Sep 2001 17:02:48 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2654.52)
Content-Type: text/plain
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

There might be a procedure about the bis version that I don't understand.
Can Charlie or the chairs answer this question?

Can an outside SDO refer to a bis RFC? i.e. does it have same
standard status as the non-bis RFC?
I was under impression that the RFC2002bis has ID status,
maybe I am way off in the woods???

Thanks in advance,
Madjid

-----Original Message-----
From: Marcello Lioy [mailto:lioy@qualcomm.com]
Sent: Sunday, August 12, 2001 11:39 AM
To: mobile-ip@sunroof.eng.sun.com
Cc: charliep@iprg.nokia.com; nish@qualcomm.com; jeffd@qualcomm.com;
susiea@qualcomm.com
Subject: Re: [mobile-ip] RFC2002bis


At 02:00 8/11/2001, you wrote:
>Hello folks,
>
>A new version of RFC2002bis has been prepared.  According
>to the most recent guidance given by the IESG, a change in
>the mandated authentication algorithm has been strongly
>suggested.  Unfortunately, this will have the effect of
>causing almost all previous implementations of Mobile IP
>for IPv4 to become incompatible with the new specification.
>
>The working group chairs recently asked the working group,
>by way of the mailing list, whether this incompatible
>change would be acceptable.  The discussion was quite
>limited, somewhat to my surprise.  This has been taken
>as evidence that going with HMAC_MD5 is more-or-less
>O.K.  Thus, it has been decided to go ahead with the
>change.  On the other hand, it is conceivable that not
>all interested parties have been notified of the possible
>change, or have had time to reply.  If there are dissenters
>to this change, now would be the time to express that
>opinion.

This could be an issue.  TIA/EIA IS-835 (the packet data standard for 
CDMA2000) is going to be deployed in North America this fall.  It specifies 
the user of RFC 2002.  There are two major areas of incompatibilty in RFC 
2002bis:
1) the inclusion of the SPI in the auth calculation
2) HMAC_MD5 if that is decided on.

Both of these things break 2002 - which means that the mobiles and 
infrastructure that are 835 compliant will be obsoleted when RFC 2002 is 
obsoleted.

I think that both of these fixes are good (the SPI was a bug that slipped 
through in 2002, and HMAC sounds like it is less vulnerable than vanila 
MD5) but they could cause issues in these planned network deployments.
-----------------------------------
Marcello (Wandering through France)


From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep  5 18:13:11 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA23538
	for <mobileip-archive@odin.ietf.org>; Wed, 5 Sep 2001 18:13:10 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id QAA05071;
	Wed, 5 Sep 2001 16:14:14 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id PAA28497;
	Wed, 5 Sep 2001 15:14:11 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f85MD840022401
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 5 Sep 2001 15:13:08 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0/Submit) id f85MD8CW022400
	for mobile-ip-dist; Wed, 5 Sep 2001 15:13:08 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from heliopolis.eng.sun.com (heliopolis.Eng.Sun.COM [152.70.1.39])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f85MD440022393
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 15:13:04 -0700 (PDT)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.eng.sun.com (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id PAA07781
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 15:13:17 -0700 (PDT)
Message-Id: <200109052213.PAA07781@heliopolis.eng.sun.com>
Date: Wed, 5 Sep 2001 15:13:16 -0700 (PDT)
From: James Kempf <James.Kempf@Sun.COM>
Subject: Re: [mobile-ip] question on BET tear down
To: mobile-ip@sunroof.eng.sun.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: Z997NcsGLmYI3ADiDgUa1A==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Hi Madjid,

The latest version of the BETH draft clarifies this, I have not yet
posted it because I have been busy with the low latency MIPv4 BETH version,
but I will try to get it out by the end of the week.

Responses below.


>In section 3.2 it says:
>
>" Once the BET between oCoA and nCoA is in place, it is torn down by 
>   one of the following events: ...."
>
>what does a  tunnel between oCoA and nCoA mean here? Do you mean the 
>BET between oAR and nAR?
>

Yes, this is a typo.

>The second event in that same section is
>
>" 2) The MN begins the process of obtaining an nCoA through nAR. 
>        This may include either stateless or stateful address 
>        configuration. In this case, nAR sends a HRqst(r) with the MN's 
>        home address, oCoA, and the R bit set, and the Lifetime field 
>        set to zero, indicating that tunneling service is no longer 
>        required. The nAR and aAR may elect to postpone terminating 
>        tunneling service for some period of time to allow propogation 
>        of the MN's nCoA to the HA and CNs. 
> "
>
>My question is, what would the lifetime be set to, if the nAR and aAR
>elect to postpone terminating tunneling service?
>

The nAR needs to renew the tunnel lifetime before it expires, or, if
a request to renew is denied, it must immediately inform the MN that
the MN must obtain a new CoA by sending it a Router Advertisement. 
The nAR needs to send the renewel request sufficiently prior to the
expiration that, if the anchor AR denies the request, the MN has a high 
probability of completing L3 handover before the tunnel times out. This will 
depend on the particular networking configuration, and the MN's traffic (RTT to 
HA and any CNs for BU, etc.), of course, but configuration can estimate a
worst case time.

The new draft has more details about how the tunnel gets torn down
when the MN starts to establish a new CoA. Basically, there are three
ways: the MN has a security association with oAR and sends a BU
after it has the new CoA (same as in existing FMIPv4 draft), the new AR notices 
that the MN is sending traffic with the new CoA as its source address
after the MN has just gone through the process of getting a new CoA (Neighbor
Advertisement and DAD (stateless), or DHCP (stateful)), or some other means, 
like the new AR is snooping the Destination Options to find the BAcks. In the 
first case, the old AR cancels the tunnel, in the second two, the
new AR cancels the tunnel.

		jak 



From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep  5 19:08:35 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA24303
	for <mobileip-archive@odin.ietf.org>; Wed, 5 Sep 2001 19:08:34 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id RAA13031;
	Wed, 5 Sep 2001 17:09:38 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id QAA11424;
	Wed, 5 Sep 2001 16:09:25 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f85N8440022499
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 5 Sep 2001 16:08:04 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0/Submit) id f85N84do022498
	for mobile-ip-dist; Wed, 5 Sep 2001 16:08:04 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f85N7x40022491
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 16:08:00 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id QAA11163
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 16:08:09 -0700 (PDT)
Received: from ihemail2.firewall.lucent.com (ihemail2.lucent.com [192.11.222.163])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id RAA11896
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 17:08:07 -0600 (MDT)
Received: from marconi.ih.lucent.com (h135-1-120-108.lucent.com [135.1.120.108])
	by ihemail2.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id f85N88G26281
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 19:08:08 -0400 (EDT)
Received: from nwsgpa.ih.lucent.com by marconi.ih.lucent.com (8.8.8+Sun/EMS-1.5 sol2)
	id SAA10995; Wed, 5 Sep 2001 18:08:07 -0500 (CDT)
Received: by nwsgpa.ih.lucent.com (8.8.8+Sun/EMS-1.5 client sol2)
	id SAA08297; Wed, 5 Sep 2001 18:08:00 -0500 (CDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15254.45136.421805.855746@nwsgpa.ih.lucent.com>
Date: Wed, 5 Sep 2001 18:08:00 -0500
From: Pete McCann <mccap@lucent.com>
To: mobile-ip@sunroof.eng.sun.com
Subject: RE: [mobile-ip] Low Latency Issue: Where to Run the Reverse Tunnel?
In-Reply-To: <200109052018.NAA02247@heliopolis.eng.sun.com>
References: <200109052018.NAA02247@heliopolis.eng.sun.com>
X-Mailer: VM 6.90 under 21.1 (patch 13) "Crater Lake" XEmacs Lucid
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hi, James,

A few comments/questions:

James Kempf writes:
 > > > R - Route optimization is in effect and the MN is using CoA as the source
 > > >     address. MN's old CoA included in the message instead of the MN's 
 > > >     home address. The O bit MUST also be set.
 > >
 > >I don't understand the concern with route optimization.  As I recall
 > >(the draft is expired and currently unavailable), R-O is run either
 > >between MNs and CNs, or MNs and previous FAs.  In either case, it is a
 > >signaling and security matter between the MN and those other nodes.
 > >Packets are then tunneled to the MN's care-of address directly from
 > >CNs or previous FAs, and the care-of address can be either co-located
 > >or FA-located.  Why would the old FA know or even care whether the MN
 > >is performing route optimization with CNs?  Why would it affect the
 > >endpoint of the reverse tunneled traffic?  It seems like R-O only
 > >affects the path taken by forward direction traffic.
 > >
 > 
 > My concern was that packets originating at the MN will be
 > sent with the source address set to the care of address and
 > not the home address, as would be the case if no route optimization
 > were in effect. 

Ok, I'm lost.  I managed to find an old (-07) version of the route
optimization draft, and I quickly searched through the new Reverse
Tunneling RFC.  I couldn't find where this requirement is stated.  My
current understanding of Route Optimization is that it only affects
the forward direction traffic.

RFC 3024 states:

   Route optimization [4] introduces forward tunnels initiated at a
   correspondent host.  Since a mobile node may not know if the
   correspondent host can decapsulate packets, reverse tunnels in that
   context are not discussed here.

Does the new -11 version of R-O contain some text about reverse
tunnels?  It's too bad I can't look at it.  I think you are saying
that, even if the MN is using an FA-located COA, it would "borrow"
this address for the purpose of sending packets to CNs with which it
had arranged for route optimization, while implementing reverse
tunneling.  Essentially these "reverse tunnels" would go back to CNs,
but as we can't expect the FA to do source routing per-CN, the MN must
take care of it.  However, I'm just making up protocol now - could
someone tell me whether -11 R-O deals with this?  Better yet, could
someone put a copy up somewhere that I can read?

 > The current version of HRqst/HRply has the old
 > FA sending the mobile node's home address and the HA address
 > in the HRqst/HRply. If the new FA uses the source address to
 > decide whether to send the packets down the reverse tunnel,
 > it will not have the right source address with route optimization.
 > As you point out, there is an issue with the old FA discovering
 > that route optimization is in effect, and since the draft has expired,
 > it is not possible at this time to check whether that is covered.

 > I think this case can be handled by having the new FA use the
 > mobile node's L2 address to decide whether to send the packets
 > down the reverse tunnel to the old FA. This won't change regardless
 > of whether route optimization is used or not, and the new FA
 > will have that either from the L2 trigger or as a result of
 > the HRqst(s).

Absolutely, I think this is the right approach.  When reverse
tunneling to the old FA is enabled, the new FA should take ANY packet
from the MN (that is not a registration request intended for itself)
to the old FA.  It should be insensitive to the source address used on
such a packet.  Note that if we are tunneling already-compressed
packets, the new FA would have a hard time discovering the IP address
of a given packet stream anyway because it did not participate in the
header compression context initialization.

 > >Now, there is an orthogonal question, which is, when we are NOT
 > >performing reverse tunneling to old FA, we may or may not need to
 > >reverse tunnel to the HA.  This could be one flag from the old FA to
 > >the new FA (in either Request or Reply, depending on the trigger type)
 > >indicating that the FA is currently supporting a reverse tunnel to the
 > >HA, and that there is currently no security on this tunnel, and the
 > >new FA SHOULD choose to do so as well.
 > >
 > 
 > I think saying there is no security is a bit strong, there
 > could be security, it could be prearranged via context transfer
 > or even some configuration step. I think it would be more precise
 > to say that the new FA is not expected to set up a security 
 > association in real time during the handover, but that it SHOULD,
 > at its discretion, choose to support a reverse tunnel as well.

Pre-arranged I could buy (although it would require some other MN from
that HA to have visited previously), but I hope we don't end up
transferring security associations.  SAs, especially IPSec SAs, are
indexed by IP address and I think it would be a bad idea to allow an
HA to start using an SA for a different communication endpoint just
because it started getting packets on it.

 > >In summary: I think your R and O bits could be combined into the
 > >current T bit.  I would agree with adding an H bit as a form of advice
 > >from the old FA to the new FA, but it may only be set when the T bit
 > >is not set.
 > >
 > 
 > Agreed. Unless there are any other comments, I will write up the
 > BETH part of low latency with this. 

OK.  Does anyone have a copy of route optimization -11 that we could
use to resolve some of the questions above?

-Pete



From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep  5 19:11:34 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA24615
	for <mobileip-archive@odin.ietf.org>; Wed, 5 Sep 2001 19:11:34 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id RAA15114;
	Wed, 5 Sep 2001 17:12:42 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id QAA12204;
	Wed, 5 Sep 2001 16:12:37 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f85NBU40022535
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 5 Sep 2001 16:11:30 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0/Submit) id f85NBT1t022534
	for mobile-ip-dist; Wed, 5 Sep 2001 16:11:29 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f85NBP40022527
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 16:11:25 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id QAA11860
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 16:11:36 -0700 (PDT)
Received: from motgate.mot.com (motgate.mot.com [129.188.136.100])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id RAA14396
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 17:11:34 -0600 (MDT)
Received: [from pobox.mot.com (pobox.mot.com [129.188.137.100]) by motgate.mot.com (motgate 2.1) with ESMTP id QAA29834 for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 16:11:35 -0700 (MST)]
Received: [from il27exm07.cig.mot.com (IL27EXM07.cig.mot.com [136.182.15.116]) by pobox.mot.com (MOT-pobox 2.0) with ESMTP id QAA03243 for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 16:11:35 -0700 (MST)]
Received: by IL27EXM07.cig.mot.com with Internet Mail Service (5.5.2654.52)
	id <RPK6LLF1>; Wed, 5 Sep 2001 18:11:35 -0500
Message-ID: <35DBB8B7AC89D4118E98009027B1009B017A9FCD@IL27EXM10.cig.mot.com>
From: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>
To: "'mobile-ip@sunroof.eng.sun.com'" <mobile-ip@sunroof.eng.sun.com>
Subject: RE: [mobile-ip] question on BET tear down
Date: Wed, 5 Sep 2001 18:11:32 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2654.52)
Content-Type: text/plain
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Thanks for your reply. I think I got my answer, my conclusion
would be: if you want to keep the tunnel up for a while then
you would not send lifetime=0 in the HRqst as it can be interpreted
from the draft, the way it is written.

Also I am getting the impression that MN might like to get
its traffic tunneled to it through BET, even after nCoA acquisition.
Hence at the end the nAR would have to send another HRqst and this
time with lifetime=0 to tear the tunnel down, correct?

Regards,
Madjid

-----Original Message-----
From: James Kempf [mailto:James.Kempf@Sun.COM]
Sent: Wednesday, September 05, 2001 5:13 PM
To: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] question on BET tear down


Hi Madjid,

The latest version of the BETH draft clarifies this, I have not yet
posted it because I have been busy with the low latency MIPv4 BETH version,
but I will try to get it out by the end of the week.

Responses below.


>In section 3.2 it says:
>
>" Once the BET between oCoA and nCoA is in place, it is torn down by 
>   one of the following events: ...."
>
>what does a  tunnel between oCoA and nCoA mean here? Do you mean the 
>BET between oAR and nAR?
>

Yes, this is a typo.

>The second event in that same section is
>
>" 2) The MN begins the process of obtaining an nCoA through nAR. 
>        This may include either stateless or stateful address 
>        configuration. In this case, nAR sends a HRqst(r) with the MN's 
>        home address, oCoA, and the R bit set, and the Lifetime field 
>        set to zero, indicating that tunneling service is no longer 
>        required. The nAR and aAR may elect to postpone terminating 
>        tunneling service for some period of time to allow propogation 
>        of the MN's nCoA to the HA and CNs. 
> "
>
>My question is, what would the lifetime be set to, if the nAR and aAR
>elect to postpone terminating tunneling service?
>

The nAR needs to renew the tunnel lifetime before it expires, or, if
a request to renew is denied, it must immediately inform the MN that
the MN must obtain a new CoA by sending it a Router Advertisement. 
The nAR needs to send the renewel request sufficiently prior to the
expiration that, if the anchor AR denies the request, the MN has a high 
probability of completing L3 handover before the tunnel times out. This will

depend on the particular networking configuration, and the MN's traffic (RTT
to 
HA and any CNs for BU, etc.), of course, but configuration can estimate a
worst case time.

The new draft has more details about how the tunnel gets torn down
when the MN starts to establish a new CoA. Basically, there are three
ways: the MN has a security association with oAR and sends a BU
after it has the new CoA (same as in existing FMIPv4 draft), the new AR
notices 
that the MN is sending traffic with the new CoA as its source address
after the MN has just gone through the process of getting a new CoA
(Neighbor
Advertisement and DAD (stateless), or DHCP (stateful)), or some other means,

like the new AR is snooping the Destination Options to find the BAcks. In
the 
first case, the old AR cancels the tunnel, in the second two, the
new AR cancels the tunnel.

		jak 


From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep  5 19:54:54 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA25124
	for <mobileip-archive@odin.ietf.org>; Wed, 5 Sep 2001 19:54:53 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id QAA17129;
	Wed, 5 Sep 2001 16:55:53 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id QAA22352;
	Wed, 5 Sep 2001 16:55:47 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f85Nsi40022674
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 5 Sep 2001 16:54:44 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0/Submit) id f85NsiJQ022670
	for mobile-ip-dist; Wed, 5 Sep 2001 16:54:44 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.12.0.Gamma0+Sun/8.12.0.Gamma0) with ESMTP id f85Nsd40022659
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 16:54:39 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id QAA25164
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 16:54:50 -0700 (PDT)
Received: from motgate2.mot.com (motgate2.mot.com [136.182.1.10])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id QAA27513
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 16:54:50 -0700 (PDT)
Received: [from pobox2.mot.com (pobox2.mot.com [136.182.15.8]) by motgate2.mot.com (motgate2 2.1) with ESMTP id QAA24153 for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 16:54:49 -0700 (MST)]
Received: [from il27exb01.cig.mot.com (il27exb01.cig.mot.com [136.182.15.100]) by pobox2.mot.com (MOT-pobox2 2.0) with ESMTP id QAA19916 for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 16:54:49 -0700 (MST)]
Received: by il27exb01.cig.mot.com with Internet Mail Service (5.5.2654.52)
	id <SCC2L04Y>; Wed, 5 Sep 2001 18:54:49 -0500
Message-ID: <35DBB8B7AC89D4118E98009027B1009B017A9FCE@IL27EXM10.cig.mot.com>
From: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>
To: "'mobile-ip@sunroof.eng.sun.com'" <mobile-ip@sunroof.eng.sun.com>
Subject: RE: [mobile-ip] Low Latency Issue: Where to Run the Reverse Tunne
	l?
Date: Wed, 5 Sep 2001 18:54:48 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2654.52)
Content-Type: text/plain
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Hi,

looks like this draft is not accessible:

ftp://ftp.isi.edu/internet-drafts/draft-calhoun-mobileip-gre-ext-00.txt

 01 is on the ftp site but it has expired last week.
Do you have a copy?

thanks,
Madjid


From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep  5 21:10:20 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA25948
	for <mobileip-archive@odin.ietf.org>; Wed, 5 Sep 2001 21:10:19 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id TAA17133;
	Wed, 5 Sep 2001 19:11:18 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id SAA06991;
	Wed, 5 Sep 2001 18:11:09 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f8619lIQ022929
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 5 Sep 2001 18:09:47 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1/Submit) id f8619laF022928
	for mobile-ip-dist; Wed, 5 Sep 2001 18:09:47 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f8619hIQ022921
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 18:09:44 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id SAA06614
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 18:09:55 -0700 (PDT)
Received: from mail1.ics.ntts.co.jp (mail1.ics.ntts.co.jp [202.32.24.45])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id SAA09722
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 18:09:54 -0700 (PDT)
Received: from mail26.silk.ntts.co.jp by mail1.ics.ntts.co.jp (8.9.3/3.7W-NTTSOFT-SUR2.0)
	id KAA12743; Thu, 6 Sep 2001 10:09:50 +0900 (JST)
Received: from daemon.inl.ntts.co.jp by mail26.silk.ntts.co.jp (8.11.4/3.7W-silk-4.4)
	id f8619nd18346; Thu, 6 Sep 2001 10:09:49 +0900 (JST)
Received: (qmail 16043 invoked by alias); 6 Sep 2001 10:09:49 +0900
Received: (qmail 16027 invoked from network); 6 Sep 2001 10:09:49 +0900
Received: from tunayosi.inl.ntts.co.jp (HELO localhost)
  by daemon.inl.ntts.co.jp with SMTP; 6 Sep 2001 10:09:49 +0900
Date: Thu, 06 Sep 2001 10:09:49 +0900 (JST)
Message-Id: <20010906.100949.424336656.takamiya@po.ntts.co.jp>
To: mobile-ip@sunroof.eng.sun.com
Cc: takamiya@po.ntts.co.jp
Subject: [mobile-ip] About Home Agent Flag in Router Advertisement Message
From: Noriaki Takamiya <takamiya@po.ntts.co.jp>
X-Mailer: Mew version 2.0 on XEmacs 21.4.1 (Copyleft)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hello,

# Sorry for resending.

  This is Takamiya. 

  I'm using MIPL implementation on USAGI IPv6 platform.

  In MIPL mailing list, I encountered the following problem:

  When a Home Agent sends Router Advertisement Message and changes
  Home Agent Flag(H) from on to off, should other Home Agent remove
  this router from the Home Agent List?

  I thought that the Home Agent changed Router Advertisement Message
  change Home Agent Flag from on to off, the other Home Agent should
  remove this router entry. But It seems that this behavior is not
  documented(draft 14) explicitly.

  I'm newbie about this mailing list, so I will apologize some
  mistakes.

  Regards,

--
Noriaki Takamiya


From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep  6 03:30:11 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA16949
	for <mobileip-archive@odin.ietf.org>; Thu, 6 Sep 2001 03:30:11 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id BAA11002;
	Thu, 6 Sep 2001 01:31:16 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id AAA01664;
	Thu, 6 Sep 2001 00:31:12 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f867U9IQ023427
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 6 Sep 2001 00:30:09 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1/Submit) id f867U9UR023426
	for mobile-ip-dist; Thu, 6 Sep 2001 00:30:09 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f867U5IQ023419
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 00:30:05 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id AAA01569
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 00:30:16 -0700 (PDT)
Received: from motgate4.mot.com (motgate4.mot.com [144.189.100.102])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id BAA10531
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 01:30:14 -0600 (MDT)
Received: [from pobox4.mot.com (pobox4.mot.com [10.64.251.243]) by motgate4.mot.com (motgate4 2.1) with ESMTP id AAA28549 for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 00:30:15 -0700 (MST)]
Received: [from m-il06-r1.mot.com (m-il06-r1.mot.com [129.188.137.193]) by pobox4.mot.com (MOT-pobox4 2.0) with ESMTP id AAA14702 for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 00:30:15 -0700 (MST)]
Received: from thorgal.crm.mot.com by m-il06-r1.mot.com with ESMTP; Thu, 6 Sep 2001 00:30:14 -0700
Received: from test9.crm.mot.com.crm.mot.com (test9.crm.mot.com [140.101.173.239])
	by thorgal.crm.mot.com (Postfix) with ESMTP
	id 7FF7E2ECAC; Thu,  6 Sep 2001 09:28:22 +0200 (CEST)
To: mobile-ip@sunroof.eng.sun.com
Cc: "Mattias Pettersson (ERA)" <Mattias.Pettersson@era.ericsson.se>,
        "Hesham Soliman (ERA)" <Hesham.Soliman@era.ericsson.se>,
        claude.castellucia@inria.fr, ludovic.bellier@inria.fr,
        "Karim El-Malki (ERA)" <Karim.El-Malki@era.ericsson.se>
Subject: Re: [mobile-ip] Question on HMIPv6 Dynamic MAP Discovery
References: <034BEFD03799D411A59F00508BDF754603008C68@esealnt448.al.sw.ericsson.se>
From: Alexandru Petrescu <petrescu@crm.mot.com>
Date: 06 Sep 2001 00:43:27 +0200
In-Reply-To: <034BEFD03799D411A59F00508BDF754603008C68@esealnt448.al.sw.ericsson.se>
Message-Id: <m3vgixw968.fsf@test9.crm.mot.com>
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.0.103
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Lines: 28
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

"Hesham Soliman  (ERA)" <Hesham.Soliman@era.ericsson.se> writes:
> > Fundamental question, indeed. I see it as a larger-than-link-scoped RA.
> > This would be the same as with router renumbering, wouldn't it?
> > 
> 	=> Yes I think it is a very similar concept. In addition, the draft says that
> 	the advertisement SHOULD be secured to guarantee that no malicious
> 	nodes will provide false information. 
> 	The router renumbering mechanism can also be used as per the
> 	draft. 

Yes, draft specifies a router renumbering technique.  I think I have a
remark to that too, sorry for being to verbose.

In my opinnion, if the PROPAGATE OpCode is exclusive with existing
codes (you can only have one of ADD, CHANGE, SET-GLOBAL, PROPAGATE)
and the MAP-Option is not in the match-prefix then the draft should
probably specify new means to delete MAP-options from an advertising
interface.(RR means to do that is to put 0 in use-prefix of a CHANGE).

> 	BTW, since we're discussing the MAP discovery, I'd like to
> 	point out that the 8n alignment in the draft is not correct
> 	(for the MAP option) we will fix that in the next revision,
> 	but I'd rather wait for more substantial issues before we
> 	submit the next revision.

Also, there's a type error in the RR rfc no.

Alex



From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep  6 04:29:17 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA17556
	for <mobileip-archive@odin.ietf.org>; Thu, 6 Sep 2001 04:29:17 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id BAA04547;
	Thu, 6 Sep 2001 01:30:27 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id BAA21708;
	Thu, 6 Sep 2001 01:30:10 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f868SaIQ023574
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 6 Sep 2001 01:28:36 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1/Submit) id f868SZpJ023573
	for mobile-ip-dist; Thu, 6 Sep 2001 01:28:35 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f868SWIQ023566
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 01:28:32 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id BAA23728
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 01:28:44 -0700 (PDT)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id BAA13748
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 01:28:43 -0700 (PDT)
Received: from era-t.ericsson.se (koff.ericsson.se [147.214.173.137])
	by penguin.wise.edt.ericsson.se (8.11.0/8.10.1/WIREfire-1.3) with SMTP id f868Sgv27448
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 10:28:42 +0200 (MEST)
Received: from era.ericsson.se by era-t.ericsson.se (SMI-8.6/LME-DOM-2.2.5(ERA/T))
	id KAA02741; Thu, 6 Sep 2001 10:28:39 +0200
Message-ID: <3B973332.94DA19A5@era.ericsson.se>
Date: Thu, 06 Sep 2001 10:26:26 +0200
From: Mattias Pettersson <mattias.pettersson@era.ericsson.se>
Organization: Ericsson Research
X-Mailer: Mozilla 4.77 [en] (Win95; U)
X-Accept-Language: en
MIME-Version: 1.0
To: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] About Home Agent Flag in Router Advertisement Message
References: <20010906.100949.424336656.takamiya@po.ntts.co.jp>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit


Noriaki Takamiya wrote:

>   When a Home Agent sends Router Advertisement Message and changes
>   Home Agent Flag(H) from on to off, should other Home Agent remove
>   this router from the Home Agent List?

At least the entry for this home agent should not be updated. Each home
agent has a lifetime, taken from the Home Agent Information Option, or
if that is missing, taken from the router lifetime field in the RA.

But it sounds reasonable to remove the entry, since the H flag
explicitly is cleared.

> 
>   I thought that the Home Agent changed Router Advertisement Message
>   change Home Agent Flag from on to off, the other Home Agent should
>   remove this router entry. But It seems that this behavior is not
>   documented(draft 14) explicitly.

/Mattias


From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep  6 07:28:37 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA20838
	for <mobileip-archive@odin.ietf.org>; Thu, 6 Sep 2001 07:28:37 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id EAA26498;
	Thu, 6 Sep 2001 04:29:43 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id EAA07231;
	Thu, 6 Sep 2001 04:29:30 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f86BSCIQ023800
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 6 Sep 2001 04:28:12 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1/Submit) id f86BSCEc023799
	for mobile-ip-dist; Thu, 6 Sep 2001 04:28:12 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f86BS8IQ023792
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 04:28:08 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id EAA21760
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 04:28:21 -0700 (PDT)
Received: from albatross-ext.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id FAA04209
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 05:28:18 -0600 (MDT)
Received: from esealnt462.al.sw.ericsson.se (ESEALNT462.al.sw.ericsson.se [153.88.251.62])
	by albatross.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id f86BSJK10168
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 13:28:19 +0200 (MEST)
Received: FROM esealnt742.al.sw.ericsson.se BY esealnt462.al.sw.ericsson.se ; Thu Sep 06 13:28:12 2001 +0200
Received: by esealnt742.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <NBWNT5N9>; Thu, 6 Sep 2001 13:21:27 +0200
Message-ID: <034BEFD03799D411A59F00508BDF754603008C74@esealnt448.al.sw.ericsson.se>
From: "Hesham Soliman  (ERA)" <Hesham.Soliman@era.ericsson.se>
To: "'mobile-ip@sunroof.eng.sun.com'" <mobile-ip@sunroof.eng.sun.com>
Subject: RE: [mobile-ip] Low Latency Issue: Should HTT be MUST, SHOULD, or
	 MAY?
Date: Thu, 6 Sep 2001 13:28:09 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>


> First off, there is an issue with regard to whether the mobile node should
> perform movement detection or not. When a mobile node,
> capable of delaying L3 handoff until real time traffic slows, moves into a 
> domain where BETH is supported and registers with an FA, how will it
> know not to issue a ProxyRtSol (if mobile initiated low latency
> handoff is happening) 
> 
	=> Because MN initiated handovers will happen in different scenarios
	where BETH can not be used (like WLAN). 

> or to issue a RtSol (if RFC2002bis handoff is
> happening)? If network initiated handoff is happening, how will
> the mobile node know not to perform a registration when it receives
> the Link Up L2 trigger on the new FA?
> 
> I'd like to suggest that we add a bit to the Agent Advertisement:
> 
>   S - Mobile node can suppress movement detection and handoff at L3 if
>       desired. FAs will make sure the mobile node's packets are properly
>       routed until a registration for a new care of address is made.
> 
	=> I thought that the whole point was to run vanilla MIP in the MN ?
	Why do we want to inform the MN about BETH or any handover
	mechanism that does not involve the MN ? The MN is automatically
	not doing movemement detection because it doesn't receive
	any indication that it did move. If the MN solicits then you have to
	reply. Let's not change the entire architecture when there is no 
	clear gain. As you said in London BETH is not applicable to all access
	technologies (in fact it is designed with a particular system in mind
	based on the assumptions in the draft), so people designing hosts 
	for the specifc systems will design them with the handover mechanism 
	in mind. 

	So to conclude I don't see any benefit in doing this. Let's 
	minimise the changes now to get this draft out. 

	Hesham

>       
> 


From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep  6 07:56:29 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA21891
	for <mobileip-archive@odin.ietf.org>; Thu, 6 Sep 2001 07:56:28 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id FAA15451;
	Thu, 6 Sep 2001 05:57:32 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id EAA23681;
	Thu, 6 Sep 2001 04:57:26 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f86BuLIQ023866
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 6 Sep 2001 04:56:21 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1/Submit) id f86BuLNZ023865
	for mobile-ip-dist; Thu, 6 Sep 2001 04:56:21 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f86BuHIQ023858
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 04:56:18 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id EAA11520
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 04:56:31 -0700 (PDT)
Received: from mgw-dax2.ext.nokia.com (mgw-dax2.ext.nokia.com [63.78.179.217])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id FAA02930
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 05:57:05 -0600 (MDT)
Received: from davir02nok.americas.nokia.com (davir02nok.americas.nokia.com [172.18.242.85])
	by mgw-dax2.ext.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f86BuTD09252
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 06:56:29 -0500 (CDT)
Received: from daebh002.NOE.Nokia.com (unverified) by davir02nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T55d2b66391ac12f255079@davir02nok.americas.nokia.com>;
 Thu, 6 Sep 2001 06:56:28 -0500
Received: from daebe007.NOE.Nokia.com ([172.18.242.211]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.2966);
	 Thu, 6 Sep 2001 06:56:28 -0500
content-class: urn:content-classes:message
Subject: RE: [mobile-ip] RFC2002bis
Date: Thu, 6 Sep 2001 06:56:28 -0500
Message-ID: <697DAA22C5004B4596E033803A7CEF44096807@daebe007.NOE.Nokia.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Thread-Topic: [mobile-ip] RFC2002bis
X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0
Thread-Index: AcE2Vv1+dO8gRqJHEdWpVgBQi2kYTQAc34TQ
From: "Patil Basavaraj (NET/Dallas)" <Basavaraj.Patil@nokia.com>
To: <mobile-ip@sunroof.eng.sun.com>
Cc: "Perkins Charles (IPRG/MtView)" <Charles.Perkins@nokia.com>,
        <Madjid.Nakhjiri@motorola.com>
X-OriginalArrivalTime: 06 Sep 2001 11:56:28.0539 (UTC) FILETIME=[F63A3CB0:01C136CA]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by sunroof.eng.sun.com id f86BuIIQ023859
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 8bit

rfc2002bis is an I-D and NOT an RFC yet. Outside SDOs can
choose whether they want to reference an I-D, which is essentially
work in progress and has the possibility of change occuring or wait
for it to become a PS with a new RFC number. 
I think you are still on the greens in your understanding of the
status of the 2002bis I-D.

> -----Original Message-----
> From: ext Nakhjiri Madjid-MNAKHJI1 
> 
> There might be a procedure about the bis version that I don't 
> understand.
> Can Charlie or the chairs answer this question?
> 
> Can an outside SDO refer to a bis RFC? i.e. does it have same
> standard status as the non-bis RFC?
> I was under impression that the RFC2002bis has ID status,
> maybe I am way off in the woods???
> 
> Thanks in advance,
> Madjid
> 
> -----Original Message-----
> From: Marcello Lioy [mailto:lioy@qualcomm.com]
> 
> 
> At 02:00 8/11/2001, you wrote:
> >Hello folks,
> >
> >A new version of RFC2002bis has been prepared.  According
> >to the most recent guidance given by the IESG, a change in
> >the mandated authentication algorithm has been strongly
> >suggested.  Unfortunately, this will have the effect of
> >causing almost all previous implementations of Mobile IP
> >for IPv4 to become incompatible with the new specification.
> >
> >The working group chairs recently asked the working group,
> >by way of the mailing list, whether this incompatible
> >change would be acceptable.  The discussion was quite
> >limited, somewhat to my surprise.  This has been taken
> >as evidence that going with HMAC_MD5 is more-or-less
> >O.K.  Thus, it has been decided to go ahead with the
> >change.  On the other hand, it is conceivable that not
> >all interested parties have been notified of the possible
> >change, or have had time to reply.  If there are dissenters
> >to this change, now would be the time to express that
> >opinion.
> 
> This could be an issue.  TIA/EIA IS-835 (the packet data standard for 
> CDMA2000) is going to be deployed in North America this fall. 
>  It specifies 
> the user of RFC 2002.  There are two major areas of 
> incompatibilty in RFC 
> 2002bis:
> 1) the inclusion of the SPI in the auth calculation
> 2) HMAC_MD5 if that is decided on.
> 
> Both of these things break 2002 - which means that the mobiles and 
> infrastructure that are 835 compliant will be obsoleted when 
> RFC 2002 is 
> obsoleted.
> 
> I think that both of these fixes are good (the SPI was a bug 
> that slipped 
> through in 2002, and HMAC sounds like it is less vulnerable 
> than vanila 
> MD5) but they could cause issues in these planned network deployments.
> -----------------------------------
> Marcello (Wandering through France)
> 


From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep  6 08:15:56 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA22694
	for <mobileip-archive@odin.ietf.org>; Thu, 6 Sep 2001 08:15:55 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id GAA24349;
	Thu, 6 Sep 2001 06:17:02 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id FAA25801;
	Thu, 6 Sep 2001 05:16:59 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f86CFvIQ023923
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 6 Sep 2001 05:15:58 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1/Submit) id f86CFvw0023922
	for mobile-ip-dist; Thu, 6 Sep 2001 05:15:57 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f86CFrIQ023915
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 05:15:54 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id FAA10560
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 05:16:07 -0700 (PDT)
Received: from motgate2.mot.com (motgate2.mot.com [136.182.1.10])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id GAA09886
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 06:16:41 -0600 (MDT)
Received: [from mothost.mot.com (mothost.mot.com [129.188.137.101]) by motgate2.mot.com (motgate2 2.1) with ESMTP id FAA21681 for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 05:16:05 -0700 (MST)]
Received: [from m-il06-r2.mot.com (m-il06-r2.mot.com [129.188.137.24]) by mothost.mot.com (MOT-mothost 2.0) with ESMTP id FAA12512 for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 05:16:05 -0700 (MST)]
Received: from thorgal.crm.mot.com by m-il06-r2.mot.com with ESMTP for mobile-ip@sunroof.eng.sun.com; Thu, 6 Sep 2001 05:15:48 -0700
Received: from test9.crm.mot.com.crm.mot.com (test9.crm.mot.com [140.101.173.239])
	by thorgal.crm.mot.com (Postfix) with ESMTP id 8E5222ECAC
	for <mobile-ip@sunroof.eng.sun.com>; Thu,  6 Sep 2001 14:13:02 +0200 (CEST)
To: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Low Latency Issue: Where to Run the Reverse Tunne l?
References: <35DBB8B7AC89D4118E98009027B1009B017A9FCE@IL27EXM10.cig.mot.com>
From: Alexandru Petrescu <petrescu@crm.mot.com>
Date: 06 Sep 2001 14:13:10 +0200
In-Reply-To: <35DBB8B7AC89D4118E98009027B1009B017A9FCE@IL27EXM10.cig.mot.com>
Message-Id: <m3pu94wm95.fsf@test9.crm.mot.com>
Lines: 490
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.0.103
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com> writes:
> Hi,
> 
> looks like this draft is not accessible:
> 
> ftp://ftp.isi.edu/internet-drafts/draft-calhoun-mobileip-gre-ext-00.txt
> 
>  01 is on the ftp site but it has expired last week.
> Do you have a copy?
> 
> thanks,
> Madjid

We keep older versions of I-D's.

Alex


INTERNET DRAFT                                            Pat R. Calhoun
Category: Standards Track                         Sun Microsystems, Inc.
Title: draft-calhoun-mobileip-gre-ext-00.txt                  Tom Hiller
Date: September 2000                                     Peter J. McCann
                                                     Lucent Technologies
                                                             Yingchun Xu
                                                        3Com Corporation



                             GRE Extensions



Status of this Memo

   This document is an individual contribution for consideration by the
   Mobile IP Working Group of the Internet Engineering Task Force.
   Comments should be submitted to the mobile-
   ip@standards.nortelnetworks.com mailing list.

   Distribution of this memo is unlimited.

   This document is an Internet-Draft and is in full conformance with
   all provisions of Section 10 of RFC2026.  Internet-Drafts are working
   documents of the Internet Engineering Task Force (IETF), its areas,
   and its working groups.  Note that other groups may also distribute
   working documents as Internet-Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at:

      http://www.ietf.org/ietf/1id-abstracts.txt

   The list of Internet-Draft Shadow Directories can be accessed at:

      http://www.ietf.org/shadow.html.

   Copyright   (C) The Internet Society 2000.  All Rights Reserved.


Abstract

   The GRE specification contains a Key field, which MAY contain a value



Calhoun et al.           expires February 2001                  [Page 1]





INTERNET DRAFT                                            September 2000


   that is used to identify a particular GRE "flow". This specification
   defines a new Mobile IP extensions that is used to exchange the value
   to be used in the GRE Key field.

   This specification also introduces a new extension, called the GRE
   Type extension, which is used during registration to signal the GRE
   type that will be used for the Mobile Node's session. This extension
   is deemed important in order to allow the Mobility Agents to setup
   the necessary protocol interfaces prior to receiving the mobile's
   traffic.


Table of Contents

      1.0  Introduction
            1.1  Requirements language
            1.2  Fast handoffs
      2.0  GRE Key extension
      3.0  GRE Type extension
      4.0  Error Values
      5.0  GRE Encapsulation
      6.0  IANA Considerations
      7.0  Security Considerations
      8.0  References
      9.0  Acknowledgements
      10.0  Authors' Addresses
      11.0  Full Copyright Statement
























Calhoun et al.           expires February 2001                  [Page 2]





INTERNET DRAFT                                            September 2000


1.0  Introduction

   The GRE specification contains a Key field, which MAY contain a value
   that is used to identify a particular GRE "flow". This specification
   defines a new Mobile IP extensions that is used to exchange the value
   to be used in the GRE Key field.

   This specification also introduces a new extension, called the GRE
   Type extension, which is used during registration to signal the GRE
   type that will be used for the Mobile Node's session. This extension
   is deemed important in order to allow the Mobility Agents to setup
   the necessary protocol interfaces prior to receiving the mobile's
   traffic.


1.1  Requirements language

   In this document, the key words "MAY", "MUST, "MUST NOT", "optional",
   "recommended", "SHOULD", and "SHOULD NOT", are to be interpreted as
   described in [2].


2.0  GRE Key extension

   The GRE Key extension MAY be included in Registration Requests [1],
   and Regional Registration Requests [3] whose 'G' bit is enabled. The
   GRE Key extension is used to inform the recipient of the Mobile IP
   request of the value to be used in GRE's Key field.

       0                   1                   2                   3
       0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |     Type      |   Length      |           Reserved            |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                        Key Identifier                         |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

      Type

         TBD (non-skippable) [1]

      Length

         6

      Reserved

         This field MUST be set to zero (0).



Calhoun et al.           expires February 2001                  [Page 3]





INTERNET DRAFT                                            September 2000


      Key Identifier

         This is a four octet value assigned in the Registration or
         Regional Registration Request, and inserted in every GRE frame
         (see Section 5).


3.0  GRE Type extension

   The GRE Type extension MAY be included in Registration Requests [1],
   and Regional Registration Requests [3] whose 'G' bit is enabled. The
   GRE Type extension is used to signal to the peer the type of traffic
   that will be sent from the Mobile Node encapsulated in GRE. Note that
   only one GRE Type extension MAY be present in a request.

   If the GRE Type is not supported by the receiver of the Registration
   or Regional Registration Request, it MUST return the appropriate
   Reply with the Code field set to PROTO_NOT_SUPPORTED (see Section 4).

   If the GRE Type extension was present in the Request, all traffic for
   the Mobile Node MUST be of the type specified in this extension.

       0                   1                   2                   3
       0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |     Type      |   Length      |           GRE Type            |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

      Type

         TBD (skippable) [1]

      Length

         6

      GRE Type

         The GRE protocol type, as defined in [4].


4.0  Error Values

   The following table contains the name of Code [1] to be returned in a
   Registration and Regional Registration Replies, the value for the
   Code, and the section in which the error is first mentioned in this
   specification.




Calhoun et al.           expires February 2001                  [Page 4]





INTERNET DRAFT                                            September 2000


      Error Name               Value   Section of Document
      ----------------------   -----   -------------------
      PROTO_NOT_SUPPORTED       TBD    3.0


5.0  GRE Encapsulation

   When the Registration or Regional Registration Request has the 'G'
   bit enabled, contains the GRE Key extension, all GRE [4] encapsulated
   packets for the Mobile Node MUST include the value found in the
   extension within the GRE Key field [5]. The receiver of the GRE frame
   will use the Key field to identify the particular Mobility Binding.


6.0  IANA Considerations

   The GRE Key extension defined in Section 2 and the GRE Type extension
   are Mobile IP registration extension as defined in RFC 2002 [1] and
   extended in RFC 2356 [6]. IANA should assign a value of 131 for this
   purpose.

   The Code values defined in Section 4 are error codes as defined in
   RFC 2002 [1] and extended in RFC 2344 [7] and RFC 2356 [6].


7.0  Security Considerations

   This specification does not introduce any new security
   considerations, beyond those described in [1].


8.0  References


   [1]  C. Perkins, Editor. "IP Mobility Support". RFC 2002. October
        1996.

   [2]  S. Bradner. "Key words for use in RFCs to Indicate Requirement
        Levels". BCP 14. RFC 2119. March 1997.

   [3]  E. Gustafsson, A. Jonsson, C. Perkins. "Mobile IP Regional
        Registration", draft-ietf-mobileip-reg-tunnel-02.txt (work in
        progress), March 2000.

   [4]  Farinacci, D., Li, T., Hanks, S., Meyer, D. and Traina, P.,
        "Generic Routing Encapsulation (GRE)," RFC 2784, March 2000.

   [5]  Gopal Dommety. "Key and Sequence Number Extensions to GRE".



Calhoun et al.           expires February 2001                  [Page 5]





INTERNET DRAFT                                            September 2000


        draft-dommety-gre-ext-04.txt, June 2000. (work in progress)

   [6]  Montenegro, G. and V. Gupta, "Sun's SKIP Firewall Traversal for
        Mobile IP", RFC 2356, June 1998.

   [7]  G. Montenegro.  Reverse Tunneling for Mobile IP.  Request for
        Comments (Proposed Standard) 2344, Internet Engineering Task
        Force, May 1998.


9.0  Acknowledgements

   The authors would like to thank the authors of draft-ietf-mobileip-
   3Gwireless-ext-04.txt, given that some text from that Internet Draft
   was copied into this specification.


10.0  Authors' Addresses

   Questions about this memo can be directed to:

      Pat R. Calhoun
      Network and Security Research Center, Sun Labs
      Sun Microsystems, Inc.
      15 Network Circle
      Menlo Park, California, 94025
      USA

       Phone:  +1 650 786 7733
         Fax:  +1 650 786 6445
      E-mail:  pcalhoun@eng.sun.com

      Gopal Dommety
      Cisco Systems
      170 West Tasman Drive
      San Jose, CA 95134

       Phone: +1 408 525 1404
      E-mail: gdommety@cisco.com












Calhoun et al.           expires February 2001                  [Page 6]





INTERNET DRAFT                                            September 2000


      Tom Hiller
      Lucent Technologies
      Rm 2F-218
      263 Shuman Blvd
      Naperville, IL  60566-7050
      USA

       Phone: +1 630 979 7673
         Fax: +1 630 979 7673
      E-Mail: tom.hiller@lucent.com

      Peter J. McCann
      Lucent Technologies
      Rm 2Z-305
      263 Shuman Blvd
      Naperville, IL  60566-7050
      USA

       Phone: +1 630 713 9359
         Fax: +1 630 713 4982
      E-Mail: mccap@lucent.com


      Yingchun Xu
      3Com Corporation
      1800 West Central Road
      Mount Prospect,
      USA 60056

       Phone: +1 847 342 6814
      E-mail: Yingchun_Xu@3com.com


11.0  Full Copyright Statement

   Copyright (C) The Internet Society (2000).  All Rights Reserved.

   This document and translations of it may be copied and furnished to
   others, and derivative works that comment on or otherwise explain it
   or assist in its implementation may be prepared, copied, published
   and distributed, in whole or in part, without restriction of any
   kind, provided that the above copyright notice and this paragraph are
   included on all such copies and derivative works. However, this docu-
   ment itself may not be modified in any way, such as by removing the
   copyright notice or references to the Internet Society or other
   Internet organizations, except as needed for the purpose of develop-
   ing Internet standards in which case the procedures for copyrights
   defined in the Internet Standards process must be followed, or as



Calhoun et al.           expires February 2001                  [Page 7]





INTERNET DRAFT                                            September 2000


   required to translate it into languages other than  English. The lim-
   ited permissions granted above are perpetual and will not be revoked
   by the Internet Society or its successors or assigns. This document
   and the information contained herein is provided on an "AS IS" basis
   and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DIS-
   CLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED
   TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT
   INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR
   FITNESS FOR A PARTICULAR PURPOSE."










































Calhoun et al.           expires February 2001                  [Page 8]



From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep  6 08:22:14 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA22980
	for <mobileip-archive@odin.ietf.org>; Thu, 6 Sep 2001 08:22:13 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id GAA28167;
	Thu, 6 Sep 2001 06:23:08 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id FAA26632;
	Thu, 6 Sep 2001 05:23:05 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f86CMEIQ023982
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 6 Sep 2001 05:22:14 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1/Submit) id f86CMES6023981
	for mobile-ip-dist; Thu, 6 Sep 2001 05:22:14 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f86CMAIQ023974
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 05:22:10 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id FAA11044
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 05:22:24 -0700 (PDT)
Received: from motgate2.mot.com (motgate2.mot.com [136.182.1.10])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id GAA12016
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 06:22:57 -0600 (MDT)
Received: [from pobox2.mot.com (pobox2.mot.com [136.182.15.8]) by motgate2.mot.com (motgate2 2.1) with ESMTP id FAA24696 for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 05:22:22 -0700 (MST)]
Received: [from m-il06-r2.mot.com (m-il06-r2.mot.com [129.188.137.24]) by pobox2.mot.com (MOT-pobox2 2.0) with ESMTP id FAA17231 for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 05:22:22 -0700 (MST)]
Received: from thorgal.crm.mot.com by m-il06-r2.mot.com with ESMTP for mobile-ip@sunroof.eng.sun.com; Thu, 6 Sep 2001 05:22:19 -0700
Received: from test9.crm.mot.com.crm.mot.com (test9.crm.mot.com [140.101.173.239])
	by thorgal.crm.mot.com (Postfix) with ESMTP id 4D0FD2ECAC
	for <mobile-ip@sunroof.eng.sun.com>; Thu,  6 Sep 2001 14:20:28 +0200 (CEST)
To: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Low Latency Issue: Where to Run the Reverse Tunne l?
References: <35DBB8B7AC89D4118E98009027B1009B017A9FCE@IL27EXM10.cig.mot.com>
	<m3pu94wm95.fsf@test9.crm.mot.com>
From: Alexandru Petrescu <petrescu@crm.mot.com>
Date: 06 Sep 2001 14:20:36 +0200
In-Reply-To: <m3pu94wm95.fsf@test9.crm.mot.com>
Message-Id: <m3y9nsv7cb.fsf@test9.crm.mot.com>
Lines: 499
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.0.103
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Sorry, this was intended to Madjid only.  I can't seem to learn how to
check headers before sending.  We do keep older versions but it's in
internal network.

Alex

Alexandru Petrescu <petrescu@crm.mot.com> writes:

> Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com> writes:
> > Hi,
> > 
> > looks like this draft is not accessible:
> > 
> > ftp://ftp.isi.edu/internet-drafts/draft-calhoun-mobileip-gre-ext-00.txt
> > 
> >  01 is on the ftp site but it has expired last week.
> > Do you have a copy?
> > 
> > thanks,
> > Madjid
> 
> We keep older versions of I-D's.
> 
> Alex
> 
> 
> INTERNET DRAFT                                            Pat R. Calhoun
> Category: Standards Track                         Sun Microsystems, Inc.
> Title: draft-calhoun-mobileip-gre-ext-00.txt                  Tom Hiller
> Date: September 2000                                     Peter J. McCann
>                                                      Lucent Technologies
>                                                              Yingchun Xu
>                                                         3Com Corporation
> 
> 
> 
>                              GRE Extensions
> 
> 
> 
> Status of this Memo
> 
>    This document is an individual contribution for consideration by the
>    Mobile IP Working Group of the Internet Engineering Task Force.
>    Comments should be submitted to the mobile-
>    ip@standards.nortelnetworks.com mailing list.
> 
>    Distribution of this memo is unlimited.
> 
>    This document is an Internet-Draft and is in full conformance with
>    all provisions of Section 10 of RFC2026.  Internet-Drafts are working
>    documents of the Internet Engineering Task Force (IETF), its areas,
>    and its working groups.  Note that other groups may also distribute
>    working documents as Internet-Drafts.
> 
>    Internet-Drafts are draft documents valid for a maximum of six months
>    and may be updated, replaced, or obsoleted by other documents at any
>    time.  It is inappropriate to use Internet-Drafts as reference
>    material or to cite them other than as "work in progress."
> 
>    The list of current Internet-Drafts can be accessed at:
> 
>       http://www.ietf.org/ietf/1id-abstracts.txt
> 
>    The list of Internet-Draft Shadow Directories can be accessed at:
> 
>       http://www.ietf.org/shadow.html.
> 
>    Copyright   (C) The Internet Society 2000.  All Rights Reserved.
> 
> 
> Abstract
> 
>    The GRE specification contains a Key field, which MAY contain a value
> 
> 
> 
> Calhoun et al.           expires February 2001                  [Page 1]
> 
> 
> 
> 
> 
> INTERNET DRAFT                                            September 2000
> 
> 
>    that is used to identify a particular GRE "flow". This specification
>    defines a new Mobile IP extensions that is used to exchange the value
>    to be used in the GRE Key field.
> 
>    This specification also introduces a new extension, called the GRE
>    Type extension, which is used during registration to signal the GRE
>    type that will be used for the Mobile Node's session. This extension
>    is deemed important in order to allow the Mobility Agents to setup
>    the necessary protocol interfaces prior to receiving the mobile's
>    traffic.
> 
> 
> Table of Contents
> 
>       1.0  Introduction
>             1.1  Requirements language
>             1.2  Fast handoffs
>       2.0  GRE Key extension
>       3.0  GRE Type extension
>       4.0  Error Values
>       5.0  GRE Encapsulation
>       6.0  IANA Considerations
>       7.0  Security Considerations
>       8.0  References
>       9.0  Acknowledgements
>       10.0  Authors' Addresses
>       11.0  Full Copyright Statement
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Calhoun et al.           expires February 2001                  [Page 2]
> 
> 
> 
> 
> 
> INTERNET DRAFT                                            September 2000
> 
> 
> 1.0  Introduction
> 
>    The GRE specification contains a Key field, which MAY contain a value
>    that is used to identify a particular GRE "flow". This specification
>    defines a new Mobile IP extensions that is used to exchange the value
>    to be used in the GRE Key field.
> 
>    This specification also introduces a new extension, called the GRE
>    Type extension, which is used during registration to signal the GRE
>    type that will be used for the Mobile Node's session. This extension
>    is deemed important in order to allow the Mobility Agents to setup
>    the necessary protocol interfaces prior to receiving the mobile's
>    traffic.
> 
> 
> 1.1  Requirements language
> 
>    In this document, the key words "MAY", "MUST, "MUST NOT", "optional",
>    "recommended", "SHOULD", and "SHOULD NOT", are to be interpreted as
>    described in [2].
> 
> 
> 2.0  GRE Key extension
> 
>    The GRE Key extension MAY be included in Registration Requests [1],
>    and Regional Registration Requests [3] whose 'G' bit is enabled. The
>    GRE Key extension is used to inform the recipient of the Mobile IP
>    request of the value to be used in GRE's Key field.
> 
>        0                   1                   2                   3
>        0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>       |     Type      |   Length      |           Reserved            |
>       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>       |                        Key Identifier                         |
>       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> 
>       Type
> 
>          TBD (non-skippable) [1]
> 
>       Length
> 
>          6
> 
>       Reserved
> 
>          This field MUST be set to zero (0).
> 
> 
> 
> Calhoun et al.           expires February 2001                  [Page 3]
> 
> 
> 
> 
> 
> INTERNET DRAFT                                            September 2000
> 
> 
>       Key Identifier
> 
>          This is a four octet value assigned in the Registration or
>          Regional Registration Request, and inserted in every GRE frame
>          (see Section 5).
> 
> 
> 3.0  GRE Type extension
> 
>    The GRE Type extension MAY be included in Registration Requests [1],
>    and Regional Registration Requests [3] whose 'G' bit is enabled. The
>    GRE Type extension is used to signal to the peer the type of traffic
>    that will be sent from the Mobile Node encapsulated in GRE. Note that
>    only one GRE Type extension MAY be present in a request.
> 
>    If the GRE Type is not supported by the receiver of the Registration
>    or Regional Registration Request, it MUST return the appropriate
>    Reply with the Code field set to PROTO_NOT_SUPPORTED (see Section 4).
> 
>    If the GRE Type extension was present in the Request, all traffic for
>    the Mobile Node MUST be of the type specified in this extension.
> 
>        0                   1                   2                   3
>        0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>       |     Type      |   Length      |           GRE Type            |
>       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> 
>       Type
> 
>          TBD (skippable) [1]
> 
>       Length
> 
>          6
> 
>       GRE Type
> 
>          The GRE protocol type, as defined in [4].
> 
> 
> 4.0  Error Values
> 
>    The following table contains the name of Code [1] to be returned in a
>    Registration and Regional Registration Replies, the value for the
>    Code, and the section in which the error is first mentioned in this
>    specification.
> 
> 
> 
> 
> Calhoun et al.           expires February 2001                  [Page 4]
> 
> 
> 
> 
> 
> INTERNET DRAFT                                            September 2000
> 
> 
>       Error Name               Value   Section of Document
>       ----------------------   -----   -------------------
>       PROTO_NOT_SUPPORTED       TBD    3.0
> 
> 
> 5.0  GRE Encapsulation
> 
>    When the Registration or Regional Registration Request has the 'G'
>    bit enabled, contains the GRE Key extension, all GRE [4] encapsulated
>    packets for the Mobile Node MUST include the value found in the
>    extension within the GRE Key field [5]. The receiver of the GRE frame
>    will use the Key field to identify the particular Mobility Binding.
> 
> 
> 6.0  IANA Considerations
> 
>    The GRE Key extension defined in Section 2 and the GRE Type extension
>    are Mobile IP registration extension as defined in RFC 2002 [1] and
>    extended in RFC 2356 [6]. IANA should assign a value of 131 for this
>    purpose.
> 
>    The Code values defined in Section 4 are error codes as defined in
>    RFC 2002 [1] and extended in RFC 2344 [7] and RFC 2356 [6].
> 
> 
> 7.0  Security Considerations
> 
>    This specification does not introduce any new security
>    considerations, beyond those described in [1].
> 
> 
> 8.0  References
> 
> 
>    [1]  C. Perkins, Editor. "IP Mobility Support". RFC 2002. October
>         1996.
> 
>    [2]  S. Bradner. "Key words for use in RFCs to Indicate Requirement
>         Levels". BCP 14. RFC 2119. March 1997.
> 
>    [3]  E. Gustafsson, A. Jonsson, C. Perkins. "Mobile IP Regional
>         Registration", draft-ietf-mobileip-reg-tunnel-02.txt (work in
>         progress), March 2000.
> 
>    [4]  Farinacci, D., Li, T., Hanks, S., Meyer, D. and Traina, P.,
>         "Generic Routing Encapsulation (GRE)," RFC 2784, March 2000.
> 
>    [5]  Gopal Dommety. "Key and Sequence Number Extensions to GRE".
> 
> 
> 
> Calhoun et al.           expires February 2001                  [Page 5]
> 
> 
> 
> 
> 
> INTERNET DRAFT                                            September 2000
> 
> 
>         draft-dommety-gre-ext-04.txt, June 2000. (work in progress)
> 
>    [6]  Montenegro, G. and V. Gupta, "Sun's SKIP Firewall Traversal for
>         Mobile IP", RFC 2356, June 1998.
> 
>    [7]  G. Montenegro.  Reverse Tunneling for Mobile IP.  Request for
>         Comments (Proposed Standard) 2344, Internet Engineering Task
>         Force, May 1998.
> 
> 
> 9.0  Acknowledgements
> 
>    The authors would like to thank the authors of draft-ietf-mobileip-
>    3Gwireless-ext-04.txt, given that some text from that Internet Draft
>    was copied into this specification.
> 
> 
> 10.0  Authors' Addresses
> 
>    Questions about this memo can be directed to:
> 
>       Pat R. Calhoun
>       Network and Security Research Center, Sun Labs
>       Sun Microsystems, Inc.
>       15 Network Circle
>       Menlo Park, California, 94025
>       USA
> 
>        Phone:  +1 650 786 7733
>          Fax:  +1 650 786 6445
>       E-mail:  pcalhoun@eng.sun.com
> 
>       Gopal Dommety
>       Cisco Systems
>       170 West Tasman Drive
>       San Jose, CA 95134
> 
>        Phone: +1 408 525 1404
>       E-mail: gdommety@cisco.com
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Calhoun et al.           expires February 2001                  [Page 6]
> 
> 
> 
> 
> 
> INTERNET DRAFT                                            September 2000
> 
> 
>       Tom Hiller
>       Lucent Technologies
>       Rm 2F-218
>       263 Shuman Blvd
>       Naperville, IL  60566-7050
>       USA
> 
>        Phone: +1 630 979 7673
>          Fax: +1 630 979 7673
>       E-Mail: tom.hiller@lucent.com
> 
>       Peter J. McCann
>       Lucent Technologies
>       Rm 2Z-305
>       263 Shuman Blvd
>       Naperville, IL  60566-7050
>       USA
> 
>        Phone: +1 630 713 9359
>          Fax: +1 630 713 4982
>       E-Mail: mccap@lucent.com
> 
> 
>       Yingchun Xu
>       3Com Corporation
>       1800 West Central Road
>       Mount Prospect,
>       USA 60056
> 
>        Phone: +1 847 342 6814
>       E-mail: Yingchun_Xu@3com.com
> 
> 
> 11.0  Full Copyright Statement
> 
>    Copyright (C) The Internet Society (2000).  All Rights Reserved.
> 
>    This document and translations of it may be copied and furnished to
>    others, and derivative works that comment on or otherwise explain it
>    or assist in its implementation may be prepared, copied, published
>    and distributed, in whole or in part, without restriction of any
>    kind, provided that the above copyright notice and this paragraph are
>    included on all such copies and derivative works. However, this docu-
>    ment itself may not be modified in any way, such as by removing the
>    copyright notice or references to the Internet Society or other
>    Internet organizations, except as needed for the purpose of develop-
>    ing Internet standards in which case the procedures for copyrights
>    defined in the Internet Standards process must be followed, or as
> 
> 
> 
> Calhoun et al.           expires February 2001                  [Page 7]
> 
> 
> 
> 
> 
> INTERNET DRAFT                                            September 2000
> 
> 
>    required to translate it into languages other than  English. The lim-
>    ited permissions granted above are perpetual and will not be revoked
>    by the Internet Society or its successors or assigns. This document
>    and the information contained herein is provided on an "AS IS" basis
>    and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DIS-
>    CLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED
>    TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT
>    INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR
>    FITNESS FOR A PARTICULAR PURPOSE."
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Calhoun et al.           expires February 2001                  [Page 8]



From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep  6 09:50:50 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA27216
	for <mobileip-archive@odin.ietf.org>; Thu, 6 Sep 2001 09:50:50 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id GAA10144;
	Thu, 6 Sep 2001 06:51:53 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id GAA22668;
	Thu, 6 Sep 2001 06:51:45 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f86DntIQ024102
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 6 Sep 2001 06:49:55 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1/Submit) id f86Dnsia024101
	for mobile-ip-dist; Thu, 6 Sep 2001 06:49:54 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f86DnpIQ024094
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 06:49:51 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id GAA21407
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 06:50:05 -0700 (PDT)
Received: from mgw-dax1.ext.nokia.com (mgw-dax1.ext.nokia.com [63.78.179.216])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id HAA20257
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 07:50:03 -0600 (MDT)
Received: from davir04nok.americas.nokia.com (davir04nok.americas.nokia.com [172.18.242.87])
	by mgw-dax1.ext.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f86Dnxm28798
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 08:50:04 -0500 (CDT)
Received: from daebh001.NOE.Nokia.com (unverified) by davir04nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T55d31e51c2ac12f257079@davir04nok.americas.nokia.com> for <mobile-ip@sunroof.eng.sun.com>;
 Thu, 6 Sep 2001 08:49:59 -0500
Received: from daebe007.NOE.Nokia.com ([172.18.242.211]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.2966);
	 Thu, 6 Sep 2001 08:49:59 -0500
content-class: urn:content-classes:message
Subject: RE: [mobile-ip] Low Latency Issue: Should HTT be MUST, SHOULD, or MAY?
Date: Thu, 6 Sep 2001 08:49:59 -0500
Message-ID: <697DAA22C5004B4596E033803A7CEF441E85DB@daebe007.NOE.Nokia.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0
Thread-Topic: [mobile-ip] Low Latency Issue: Should HTT be MUST, SHOULD, or MAY?
Thread-Index: AcE2zFCzQb+4I6K8EdWpVgBQi2kYTQADpp/A
From: "Patil Basavaraj (NET/Dallas)" <Basavaraj.Patil@nokia.com>
To: <mobile-ip@sunroof.eng.sun.com>
X-OriginalArrivalTime: 06 Sep 2001 13:49:59.0528 (UTC) FILETIME=[D1E4AE80:01C136DA]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by sunroof.eng.sun.com id f86DnpIQ024095
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 8bit

>> or to issue a RtSol (if RFC2002bis handoff is
>> happening)? If network initiated handoff is happening, how will
>> the mobile node know not to perform a registration when it receives
>> the Link Up L2 trigger on the new FA?
>> 
>> I'd like to suggest that we add a bit to the Agent Advertisement:
>> 
>>   S - Mobile node can suppress movement detection and handoff at L3
if
>>       desired. FAs will make sure the mobile node's packets are
properly
>>       routed until a registration for a new care of address is made.
>> 
>	=> I thought that the whole point was to run vanilla MIP in the
MN ?
>	Why do we want to inform the MN about BETH or any handover
>	mechanism that does not involve the MN ?

James, I thought one of the advantages of BETH was that since it is a
network initiated (and Network only) handoff protocol, the MN is not
involved in the handoff process. So I agree with Hesham that the MN
does not need indications of what is occuring in the network.

>
>	Hesham
>

-Basavaraj



From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep  6 10:45:15 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA29141
	for <mobileip-archive@odin.ietf.org>; Thu, 6 Sep 2001 10:45:14 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id HAA04586;
	Thu, 6 Sep 2001 07:46:23 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id HAA09818;
	Thu, 6 Sep 2001 07:46:11 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f86EilIQ024270
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 6 Sep 2001 07:44:47 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1/Submit) id f86EilQG024269
	for mobile-ip-dist; Thu, 6 Sep 2001 07:44:47 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f86EihIQ024262
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 07:44:43 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id HAA01542
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 07:44:56 -0700 (PDT)
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by patan.sun.com (8.9.3+Sun/8.9.3) with SMTP id IAA03245
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 08:44:53 -0600 (MDT)
Received: (qmail 14365 invoked by uid 500); 6 Sep 2001 14:32:02 -0000
Date: Thu, 6 Sep 2001 07:32:02 -0700
From: Pat Calhoun <pcalhoun@diameter.org>
To: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] FW: draft-ietf-mobileip-mier-07.txt
Message-ID: <20010906073202.B14344@charizard.diameter.org>
References: <CD8355C7E19ED411BD5F00508BB0D19D698003@megisto-sql1.megisto.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <CD8355C7E19ED411BD5F00508BB0D19D698003@megisto-sql1.megisto.com>; from PRoberts@MEGISTO.com on Tue, Sep 04, 2001 at 11:30:07AM -0400
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

yes, I'm ok with that.

PatC
On Tue, Sep 04, 2001 at 11:30:07AM -0400, Phil Roberts wrote:
> I've received zero feedback on this.  Let me try another tack.
> 
> I propose we integrate this document into 2002bis.  It would allow
> us to have a normative reference for all future documents using
> extensions, 2002bis will be the primary standards document going forward,
> and is in the process of being revised now.
> 
> Is the WG okay with this?  Please post comments to the list.
> 
> Thanks,
> Phil
> 
> 
> > -----Original Message-----
> > From: Phil Roberts [mailto:PRoberts@MEGISTO.com]
> > Sent: Thursday, August 23, 2001 4:34 PM
> > To: 'mobile-ip@sunroof.eng.sun.com'
> > Subject: [mobile-ip] FW: draft-ietf-mobileip-mier-07.txt
> > 
> > 
> > Hi folks,
> > 
> >     we've received this feedback from the IESG on the MIER draft.
> > Please provide comments, especially on the first set of options.
> > 
> > Phil
> > 
> > 
> > --------------------
> > General comment. This ID seems to be of rather limited usefulness as a
> > standalone RFC. Is it really needed? This document seems to update RFC
> > 2002, but is informational. This can be remedied by:
> > 
> >   - making this standards track (seems overkill, since it doesn't
> >     actually define an option, and hence, doesn't define anything
> >     anyone needs to implement, from what I can tell)
> >   - merge it in with 2002bis (which is being revised right now anyway)
> >   - merge this document with GNAI, since the GNAI document is a
> >     specific case where use of MIER might make sense. 
> >   - take out the MUST/SHOULDs and make it clear that this document is
> >     only proposing an approach to encoding options, and that future
> >     options writers should consider the issues raised when designing
> >     their options. NOte: if this approach is used, other documents
> >     (e.g., draft-ietf-mobileip-gnaie-04.txt) shouldn't have normative
> >     references to this document. At present, gnai appears to do just
> >     that.
> > 
> > For example:
> > 
> > > MIER describes a new extension 
> > >     structure to Mobile IP to make the extensions far more 
> > >     extensible.     
> > 
> > Could be rewritten as:
> > 
> >      MIER describes a way of encoding extensions that make it possible
> >      to conserve MIP options in some cases. Authors of future options
> >      should consider the issues raised in this document when designing
> >      new options.
> > 
> > There are several other places in the document where the langauge
> > could be toned down and made more neutral.
> >      
> > >     It is in the interest of the Mobile IP WG to conserve the 
> > >     usage of the type field since we see many drafts proposing 
> > >     new extensions for Mobile IP. Therefore there is a real 
> > 
> > There is an alternate approach, one that seems to be working in
> > practice, and has other benefits. Don't allow IANA to assign options
> > until there is significant support for an option, i.e, via something
> > like "IETF consensus" [RFC 2434].  This approach also has the
> > advantage that it discourages the use of many options anyway, a
> > generaly desirable feature.  Usage of many options tends to negatively
> > impact interoperability.
> > 
> > Finally, looking at the IANA pages, it does not appear that options
> > are being used at a significant rate and that exhaustion of the space
> > is serious issue at present.
> > 
> > 
> > > 1.0 Introduction
> > > 
> > >     The type field in the Mobile IP extension structure can support
> > >     upto 255 (skippable and not skippable) uniquely identifiable
> > >     extensions. With new developments/additions to Mobile IP
> > >     there is a strong possibility that the available space will 
> > >     run out.
> > 
> > What  evidence is there that this is true at present?
> > 
> > >     Mobile IP Extensions Rationalization (MIER) describes a 
> > >     new extension structure to solve this problem. MIER strategy
> > >     is to initially aggregate certain types of extensions (e.g,
> > >     NAI) and sub types to identify the precise extension (example
> > >     MN/User NAI, HA NAI etc). This will greatly reduce the usage
> > >     of the type field. 
> > 
> > Last sentence seems a bit too strong. Better to say "This may reduce
> > the usage of the type field in some cases".
> > 
> > > 2.2 New Mobile IP Extension format
> > > 
> > >     This draft proposes the following  two structures for Mobile IP
> > >     extensions to be carried in the Mobile IP control messages.
> > >     Since the new extension structures will cause an efficient
> > >     usage of the extension type space, it is strongly recommended
> > >     that all the new proposals for the Mobile IP WG that have new 
> > >     extensions SHOULD follow this format. 
> > 
> > SHOULD wording seems a bit strong. Encoding options in this way makes
> > sense in *some* cases, but it is not clear (to me) that it does so in
> > even the majority of cases. It would be sufficient to say option
> > writers should consider whether the structure defined here makes sense
> > when a new option is defined. Saying they SHOULD follow it is too
> > strong.
> > 
> > > 2.2.1 Long Extension Format
> > 
> > In the absence of a specific proposed need for a long option, I don't
> > see the value in defining it. Moreover, will MIP *ever* define any
> > more non-skippable options? Seems like doing so would be bad for
> > interoperating with the installed base (which won't understand any
> > newly defined options) . If that is the case, why define now? One can
> > always define a long format later should it be deemed necessary.
> > 
> > > 2.2.2 Short Extension Format
> > 
> > This format makes sense for some types of options (GNAI would seem to
> > be one). It does not make sense for others. For example, of the
> > existing MIP options, how many would it actually make sense to encode
> > in this fashion?
> > 
> > >     Sub-Type  is a unique number given to each member in the
> > >               aggregated type.  Sub-Type values between of 
> > 200 through
> > >               255 are reserved for future use and standardization.
> > 
> > The semantics of this field are dependent on the actual option; it
> > make no sense to say anything about reserving values in the general
> > case. It *might* make sense to say something like that in the case of
> > a specific option, but that would be the job of that specific option.
> > 
> > If this document is to be published as a standalone document:
> > 
> > Needs security considerations section.
> > 
> > Would be good to have an IANA considerations section; I would expect
> > it to say "There are no IANA Actions in this document", but that sort
> > of depends on resolution of the first point.
> > 


From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep  6 11:16:13 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00141
	for <mobileip-archive@odin.ietf.org>; Thu, 6 Sep 2001 11:16:12 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA19659;
	Thu, 6 Sep 2001 08:17:15 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id IAA08245;
	Thu, 6 Sep 2001 08:17:07 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f86FG0IQ024337
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 6 Sep 2001 08:16:00 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1/Submit) id f86FG0sm024336
	for mobile-ip-dist; Thu, 6 Sep 2001 08:16:00 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from eastmail2.East.Sun.COM (eastmail2.East.Sun.COM [129.148.1.241])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f86FFvIQ024329
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 08:15:58 -0700 (PDT)
Received: from onion.east.sun.com (onion.East.Sun.COM [129.148.174.110])
	by eastmail2.East.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id LAA02256
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 11:16:11 -0400 (EDT)
Received: (from glass@localhost)
	by onion.east.sun.com (8.9.3+Sun/8.9.3) id LAA19158
	for mobile-ip@sunroof.eng.sun.com; Thu, 6 Sep 2001 11:16:40 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f866jSIQ023360
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 23:45:28 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id XAA12766
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 23:45:39 -0700 (PDT)
Received: from muminmamman.lifix.fi ([195.238.204.197])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id XAA16797
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 5 Sep 2001 23:45:37 -0700 (PDT)
Received: from ban by muminmamman.lifix.fi with local (Exim 3.12 #1 (Debian))
	id 15esuu-0004Ni-00
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 06 Sep 2001 09:45:36 +0300
Date: Thu, 6 Sep 2001 09:45:36 +0300
From: Bjorn Andersson <bjorn@lifix.fi>
To: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] RFC2002bis and MIER
Message-ID: <20010906094536.A16579@lifix.fi>
Mail-Followup-To: Bjorn Andersson <bjorn@lifix.fi>,
	mobile-ip@sunroof.eng.sun.com
References: <200109052018.NAA02268@heliopolis.eng.sun.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <200109052018.NAA02268@heliopolis.eng.sun.com>
User-Agent: Mutt/1.3.20i
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 8bit

On Wed, Sep 05 2001, at 13:18:43 -0700, James Kempf wrote:
> >We would like to incorporate the format for extensions specified in
> >MIER into the RFC2002bis I-D and eliminate the MIER draft as a 
> >WG document. Comments/Opinions?
> >
> >Phil had sent a note to the list earlier with detailed feedback from the
> >IESG which failed to elicit any response from WG members.
> 
> Actually, I responded and said that I favored the proposal.

If all you want is an acceptance statement, then yes, I also
favor the proposal. 

I think there are few responses because no one objects the
proposal. I interpret the silence as a general acceptance.

  Björn

-- 
Björn Andersson <bjorn@lifix.fi>                       +358 50 341 2556
Lifix Systems Oy <http://www.lifix.fi/>                 PGP id 5AFC144B
Yliopistonkatu 5, 3rd floor; FIN-00100 Helsinki


From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep  6 12:07:18 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01324
	for <mobileip-archive@odin.ietf.org>; Thu, 6 Sep 2001 12:07:18 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id JAA16248;
	Thu, 6 Sep 2001 09:08:24 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA19461;
	Thu, 6 Sep 2001 09:08:11 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f86G6fIQ024432
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 6 Sep 2001 09:06:41 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1/Submit) id f86G6fVg024431
	for mobile-ip-dist; Thu, 6 Sep 2001 09:06:41 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from heliopolis.eng.sun.com (redcoast.Eng.Sun.COM [152.70.28.21])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f86G6cIQ024424
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 09:06:38 -0700 (PDT)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.eng.sun.com (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id JAA10725
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 09:06:53 -0700 (PDT)
Message-Id: <200109061606.JAA10725@heliopolis.eng.sun.com>
Date: Thu, 6 Sep 2001 09:06:52 -0700 (PDT)
From: James Kempf <James.Kempf@Sun.COM>
Subject: RE: [mobile-ip] question on BET tear down
To: mobile-ip@sunroof.eng.sun.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: y8i3iFq8f2ODfnaaRvNrxw==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

>Thanks for your reply. I think I got my answer, my conclusion
>would be: if you want to keep the tunnel up for a while then
>you would not send lifetime=0 in the HRqst as it can be interpreted
>from the draft, the way it is written.
>

Correct.

>Also I am getting the impression that MN might like to get
>its traffic tunneled to it through BET, even after nCoA acquisition.
>Hence at the end the nAR would have to send another HRqst and this
>time with lifetime=0 to tear the tunnel down, correct?
>

When L3 handover is complete (== new CoA aquisition is complete) including
BU/BAck transactions with HA, CNs, and possibly old AR, then either
the old or new AR can initiate tunnel tear down. Prior to that,
tearing down the tunnel runs the risk of stranding any in-flight
packets. The new AR should renew the tunnel when it is about to expire,
even if the MN is in the process of aquiring a new CoA. Only when 
the old or new AR have proof that the MN has a new CoA should
they tear down the tunnel. Such proof was mentioned in the previous
email and is described in the forthcoming draft.

		jak 



From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep  6 12:16:48 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01560
	for <mobileip-archive@odin.ietf.org>; Thu, 6 Sep 2001 12:16:47 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id KAA25645;
	Thu, 6 Sep 2001 10:17:38 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA21850;
	Thu, 6 Sep 2001 09:17:30 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f86GGQIQ024512
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 6 Sep 2001 09:16:26 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1/Submit) id f86GGQsB024511
	for mobile-ip-dist; Thu, 6 Sep 2001 09:16:26 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f86GGMIQ024504
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 09:16:23 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA21516
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 09:16:36 -0700 (PDT)
Received: from albatross-ext.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA16497
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 10:17:09 -0600 (MDT)
Received: from esealnt462.al.sw.ericsson.se (ESEALNT462.al.sw.ericsson.se [153.88.251.62])
	by albatross.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id f86GGXK17513
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 18:16:33 +0200 (MEST)
Received: FROM esealnt742.al.sw.ericsson.se BY esealnt462.al.sw.ericsson.se ; Thu Sep 06 18:16:32 2001 +0200
Received: by esealnt742.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <NBWN4JFC>; Thu, 6 Sep 2001 18:09:40 +0200
Message-ID: <034BEFD03799D411A59F00508BDF754603008C7B@esealnt448.al.sw.ericsson.se>
From: "Hesham Soliman  (ERA)" <Hesham.Soliman@era.ericsson.se>
To: "'mobile-ip@sunroof.eng.sun.com'" <mobile-ip@sunroof.eng.sun.com>
Subject: RE: [mobile-ip] question on BET tear down
Date: Thu, 6 Sep 2001 18:16:24 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

> >Also I am getting the impression that MN might like to get
> >its traffic tunneled to it through BET, even after nCoA acquisition.
> >Hence at the end the nAR would have to send another HRqst and this
> >time with lifetime=0 to tear the tunnel down, correct?
> >
> 
> When L3 handover is complete (== new CoA aquisition is complete) including
> BU/BAck transactions with HA, CNs, and possibly old AR, then either
> the old or new AR can initiate tunnel tear down. Prior to that,
> tearing down the tunnel runs the risk of stranding any in-flight
> packets. The new AR should renew the tunnel when it is about to expire,
> even if the MN is in the process of aquiring a new CoA. Only when 
> the old or new AR have proof that the MN has a new CoA should
> they tear down the tunnel. Such proof was mentioned in the previous
> email and is described in the forthcoming draft.
> 
	=> So for the nAR to know that the above has happened, 
	does it monitor te MN's traffic to see whether BAcks from 
	the HA and CN have been received ?

	Hesham


From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep  6 12:35:21 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02024
	for <mobileip-archive@odin.ietf.org>; Thu, 6 Sep 2001 12:35:20 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id JAA01308;
	Thu, 6 Sep 2001 09:36:26 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA27124;
	Thu, 6 Sep 2001 09:36:11 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f86GYbIQ024579
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 6 Sep 2001 09:34:37 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1/Submit) id f86GYaRx024578
	for mobile-ip-dist; Thu, 6 Sep 2001 09:34:36 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f86GYXIQ024571
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 09:34:33 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA11219;
	Thu, 6 Sep 2001 09:34:47 -0700 (PDT)
Received: from laposte.enst-bretagne.fr (laposte.enst-bretagne.fr [192.108.115.3])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id JAA14014;
	Thu, 6 Sep 2001 09:34:46 -0700 (PDT)
Received: from rsm.rennes.enst-bretagne.fr (rsm.rennes.enst-bretagne.fr [192.44.77.1])
	by laposte.enst-bretagne.fr (8.11.6/8.11.6) with ESMTP id f86GYes11946;
	Thu, 6 Sep 2001 18:34:40 +0200
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr [193.52.74.194])
	by rsm.rennes.enst-bretagne.fr (8.8.8/8.8.8) with ESMTP id SAA20667;
	Thu, 6 Sep 2001 18:34:41 +0200 (MET DST)
Received: from givry.rennes.enst-bretagne.fr (localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.11.3/8.11.3) with ESMTP id f86GYel20584;
	Thu, 6 Sep 2001 18:34:40 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200109061634.f86GYel20584@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: mobile-ip@sunroof.eng.sun.com
cc: Alper Yegin <Alper.Yegin@eng.sun.com>
Subject: Re: [mobile-ip] Coexistence with other uses for routing header 
In-reply-to: Your message of Wed, 05 Sep 2001 12:52:09 PDT.
             <3B968269.9C4897CE@iprg.nokia.com> 
Date: Thu, 06 Sep 2001 18:34:40 +0200
X-Virus-Scanned: by amavisd-milter (http://www.amavis.org/) at enst-bretagne.fr
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
 In your previous mail you wrote:

   For the purposes of what to put into the revised specification,
   I think the main result of the recent discussion would be that
   the mobile node's home address does not have to be the last stop
   along the source route indicated in a routing header.  This part
   of the revision should not be the deciding factor in any
   specification about mobile routers or further route optimization,
   and so I have reformulated the paragraph as follows:
   
        It is possible that a correspondent node, having no knowledge of the
        mobile node's care-of address, would still (for reasons unspecified
        here but not necessarily related to mobility) attempt to deliver a 
        packet, either to or by way of the mobile node's home address,
        by using a routing header.  If the correspondent node subsequently
        accepts a Binding Update and creates a Binding Cache entry for the
        mobile node, then afterwards, the routing header used by the
        corresponding node which includes the mobile node's home address
        SHOULD also include the mobile node's care-of address.
        The correspondent node SHOULD put the mobile node's care-of address
        as the intermediate node address immediately preceding the
        mobile node's home address.  When the care-of address is the
        first intermediate node address, this implies that the care-of
        address is to be placed in the Destination Address of the IPv6
        headerd, and the mobile node's home address is the first entry
        in the type 0 routing header.  Otherwise, the correspondent 
        node MUST place the mobile node's home address immediately 
        after the care-of address entry of the routing header, following
        all other intermediate node addresses that would have
        already been in the routing header before the creation
        of the Binding Cache entry for the care-of address.
   
   I hope this is better.
   
=> yes but you should add something about the possible reversing
of this by the receiver. This issue is easy to solve if it is MN
but difficult if it is not. Has someone a simple proposal?

Thanks

Francis.Dupont@enst-bretagne.fr

PS: reference is RFC 2460 section 8.4


From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep  6 12:48:13 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02311
	for <mobileip-archive@odin.ietf.org>; Thu, 6 Sep 2001 12:48:12 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id JAA08244;
	Thu, 6 Sep 2001 09:49:22 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA01229;
	Thu, 6 Sep 2001 09:49:06 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f86GlaIQ024654
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 6 Sep 2001 09:47:36 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1/Submit) id f86Glag8024653
	for mobile-ip-dist; Thu, 6 Sep 2001 09:47:36 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from heliopolis.eng.sun.com (bigbang.Eng.Sun.COM [152.70.8.30])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f86GlWIQ024646
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 09:47:32 -0700 (PDT)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.eng.sun.com (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id JAA12591
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 09:47:48 -0700 (PDT)
Message-Id: <200109061647.JAA12591@heliopolis.eng.sun.com>
Date: Thu, 6 Sep 2001 09:47:47 -0700 (PDT)
From: James Kempf <James.Kempf@Sun.COM>
Subject: RE: [mobile-ip] question on BET tear down
To: mobile-ip@sunroof.eng.sun.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: CP40y7uQ3+pK24SP0AOb+g==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Hesham,

>> >Also I am getting the impression that MN might like to get
>> >its traffic tunneled to it through BET, even after nCoA acquisition.
>> >Hence at the end the nAR would have to send another HRqst and this
>> >time with lifetime=0 to tear the tunnel down, correct?
>> >
>> 
>> When L3 handover is complete (== new CoA aquisition is complete) including
>> BU/BAck transactions with HA, CNs, and possibly old AR, then either
>> the old or new AR can initiate tunnel tear down. Prior to that,
>> tearing down the tunnel runs the risk of stranding any in-flight
>> packets. The new AR should renew the tunnel when it is about to expire,
>> even if the MN is in the process of aquiring a new CoA. Only when 
>> the old or new AR have proof that the MN has a new CoA should
>> they tear down the tunnel. Such proof was mentioned in the previous
>> email and is described in the forthcoming draft.
>> 
>	=> So for the nAR to know that the above has happened, 
>	does it monitor te MN's traffic to see whether BAcks from 
>	the HA and CN have been received ?
>
>	Hesham


As I mentioned in my reply to Madjid yestereday, it doesn't have to.
The oAR can initiate the tunnel tear down if the MN has a
security association (and it *must* in order to send a BU) as
in standard FMIPv6, or the nAR can simply notice that the MN is
sending packets with the nCoA as the source address, so the
tunnel is no longer needed. The nAR can monitor the traffic
to match BU/BAck if it chooses, but it is not necessary.


		jak



From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep  6 13:05:57 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02816
	for <mobileip-archive@odin.ietf.org>; Thu, 6 Sep 2001 13:05:56 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA17561;
	Thu, 6 Sep 2001 10:07:04 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id KAA16004;
	Thu, 6 Sep 2001 10:06:54 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f86H5XIQ024706
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 6 Sep 2001 10:05:33 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1/Submit) id f86H5WLA024705
	for mobile-ip-dist; Thu, 6 Sep 2001 10:05:32 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f86H5TIQ024698
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 10:05:29 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id KAA05814
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 10:05:43 -0700 (PDT)
Received: from albatross-ext.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id KAA29063
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 10:05:43 -0700 (PDT)
Received: from esealnt461 (esealnt461.al.sw.ericsson.se [153.88.251.61])
	by albatross.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id f86H5gK00120
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 19:05:42 +0200 (MEST)
Received: FROM esealnt742.al.sw.ericsson.se BY esealnt461 ; Thu Sep 06 19:05:35 2001 +0200
Received: by esealnt742.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <NBWN4KAW>; Thu, 6 Sep 2001 18:58:49 +0200
Message-ID: <034BEFD03799D411A59F00508BDF754603008C7F@esealnt448.al.sw.ericsson.se>
From: "Hesham Soliman  (ERA)" <Hesham.Soliman@era.ericsson.se>
To: "'mobile-ip@sunroof.eng.sun.com'" <mobile-ip@sunroof.eng.sun.com>
Subject: RE: [mobile-ip] question on BET tear down
Date: Thu, 6 Sep 2001 19:05:27 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

> >> 
> >> When L3 handover is complete (== new CoA aquisition is complete) including
> >> BU/BAck transactions with HA, CNs, and possibly old AR, then either
> >> the old or new AR can initiate tunnel tear down. Prior to that,
> >> tearing down the tunnel runs the risk of stranding any in-flight
> >> packets. The new AR should renew the tunnel when it is about to expire,
> >> even if the MN is in the process of aquiring a new CoA. Only when 
> >> the old or new AR have proof that the MN has a new CoA should
> >> they tear down the tunnel. Such proof was mentioned in the previous
> >> email and is described in the forthcoming draft.
> >> 
> >	=> So for the nAR to know that the above has happened, 
> >	does it monitor te MN's traffic to see whether BAcks from 
> >	the HA and CN have been received ?
> >
> >	Hesham
> 
> 
> As I mentioned in my reply to Madjid yestereday, it doesn't have to.
> The oAR can initiate the tunnel tear down if the MN has a
> security association (and it *must* in order to send a BU) as
> in standard FMIPv6, 
> 
	=> I understand this part. 

> or the nAR can simply notice that the MN is
> sending packets with the nCoA as the source address, so the
> tunnel is no longer needed. The nAR can monitor the traffic
> to match BU/BAck if it chooses, but it is not necessary.
> 
	=> But you were explaining that you have it as an option
	so perhaps it needs to be shown how this can happen. 
	I can't see monitoring traffic for BU/BA as being an option really, 
	routers just won't do that. Even if they do, you may not 
	get a BA from CNs. So I'm not sure that having 
	it as an option is useful because it is not a realistic one. 

	Looking for the source address is not accurate either because
	using a new CoA doesn't tell you that the routing is 
	optimised or symmetric. 

	Hesham





From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep  6 13:08:56 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02898
	for <mobileip-archive@odin.ietf.org>; Thu, 6 Sep 2001 13:08:56 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id LAA12862;
	Thu, 6 Sep 2001 11:09:54 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id KAA16785;
	Thu, 6 Sep 2001 10:09:47 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f86H8ZIQ024738
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 6 Sep 2001 10:08:35 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1/Submit) id f86H8ZO5024737
	for mobile-ip-dist; Thu, 6 Sep 2001 10:08:35 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from heliopolis.eng.sun.com (redhook.Eng.Sun.COM [152.70.24.37])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f86H8WIQ024727
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 10:08:32 -0700 (PDT)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.eng.sun.com (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id KAA13653
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 10:08:47 -0700 (PDT)
Message-Id: <200109061708.KAA13653@heliopolis.eng.sun.com>
Date: Thu, 6 Sep 2001 10:08:46 -0700 (PDT)
From: James Kempf <James.Kempf@Sun.COM>
Subject: RE: [mobile-ip] Low Latency Issue: Where to Run the Reverse Tunnel?
To: mobile-ip@sunroof.eng.sun.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: 1jkyaxBytL83bUF3L8qTag==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Hi Pete,


> > My concern was that packets originating at the MN will be
> > sent with the source address set to the care of address and
> > not the home address, as would be the case if no route optimization
> > were in effect. 
>
>Ok, I'm lost.  I managed to find an old (-07) version of the route
>optimization draft, and I quickly searched through the new Reverse
>Tunneling RFC.  I couldn't find where this requirement is stated.  My
>current understanding of Route Optimization is that it only affects
>the forward direction traffic.
>

Right, but the MN will still put its CoA in as the source address
on outgoing packets, I think.

>RFC 3024 states:
>
>   Route optimization [4] introduces forward tunnels initiated at a
>   correspondent host.  Since a mobile node may not know if the
>   correspondent host can decapsulate packets, reverse tunnels in that
>   context are not discussed here.
>
>Does the new -11 version of R-O contain some text about reverse
>tunnels?  It's too bad I can't look at it.  I think you are saying
>that, even if the MN is using an FA-located COA, it would "borrow"
>this address for the purpose of sending packets to CNs with which it
>had arranged for route optimization, while implementing reverse
>tunneling.  Essentially these "reverse tunnels" would go back to CNs,
>but as we can't expect the FA to do source routing per-CN, the MN must
>take care of it.  However, I'm just making up protocol now - could
>someone tell me whether -11 R-O deals with this?  Better yet, could
>someone put a copy up somewhere that I can read?
>

I wasn't proposing that the reverse tunnel go back to  the CN, only
that the new FA be able to use the MN CoA to index to the reverse tunnel
to the old FA, since the packet coming from the MN will have the
CoA and not the home address as the source address. But, as mentioned,
this is unnecessary if the old FA uses the L2 address to
identify which packet should go through the tunnel to the old FA.

But you do bring up an interesting point about how to deal with the
case where the reverse tunnel needs to run to the CN. As far as
low latency is concerned, I think we can basically punt since
the route optimization draft doesn't propose to solve the
fundamental problem.

> > I think saying there is no security is a bit strong, there
> > could be security, it could be prearranged via context transfer
> > or even some configuration step. I think it would be more precise
> > to say that the new FA is not expected to set up a security 
> > association in real time during the handover, but that it SHOULD,
> > at its discretion, choose to support a reverse tunnel as well.
>
>Pre-arranged I could buy (although it would require some other MN from
>that HA to have visited previously), but I hope we don't end up
>transferring security associations.  SAs, especially IPSec SAs, are
>indexed by IP address and I think it would be a bad idea to allow an
>HA to start using an SA for a different communication endpoint just
>because it started getting packets on it.
>

OK.

>OK.  Does anyone have a copy of route optimization -11 that we could
>use to resolve some of the questions above?
>

I'll see if I can find one, but I think that I've got enough to go
on now to rework the POST-REG/BETH  section of the low latency draft.
Thanx.

		jak



From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep  6 13:49:22 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04106
	for <mobileip-archive@odin.ietf.org>; Thu, 6 Sep 2001 13:49:22 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA09271;
	Thu, 6 Sep 2001 10:50:10 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id KAA19106;
	Thu, 6 Sep 2001 10:49:50 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f86HmGIQ024870
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 6 Sep 2001 10:48:16 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1/Submit) id f86HmGIx024869
	for mobile-ip-dist; Thu, 6 Sep 2001 10:48:16 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f86HmCIQ024862
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 10:48:12 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id KAA18451
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 10:48:27 -0700 (PDT)
Received: from femail48.sdc1.sfba.home.com (femail48.sdc1.sfba.home.com [24.254.60.42])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id KAA00506
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 10:48:26 -0700 (PDT)
Received: from ieee.org ([65.6.9.134]) by femail48.sdc1.sfba.home.com
          (InterMail vM.4.01.03.20 201-229-121-120-20010223) with ESMTP
          id <20010906174825.XRCQ26637.femail48.sdc1.sfba.home.com@ieee.org>
          for <mobile-ip@sunroof.eng.sun.com>;
          Thu, 6 Sep 2001 10:48:25 -0700
Message-ID: <3B97B6C0.2023F90@ieee.org>
Date: Thu, 06 Sep 2001 12:47:44 -0500
From: Peter Lei <peter.lei@ieee.org>
X-Mailer: Mozilla 4.78 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Low Latency Issue: Where to Run the Reverse Tunnel?
References: <200109061708.KAA13653@heliopolis.eng.sun.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hi James,

James Kempf wrote:
> 
> Hi Pete,
> 
> > > My concern was that packets originating at the MN will be
> > > sent with the source address set to the care of address and
> > > not the home address, as would be the case if no route optimization
> > > were in effect.
> >
> >Ok, I'm lost.  I managed to find an old (-07) version of the route
> >optimization draft, and I quickly searched through the new Reverse
> >Tunneling RFC.  I couldn't find where this requirement is stated.  My
> >current understanding of Route Optimization is that it only affects
> >the forward direction traffic.
> >
> 
> Right, but the MN will still put its CoA in as the source address
> on outgoing packets, I think.

I think the only time the MN would do this is if it is doing local
decapsulation (ie. colocated COA).  Otherwise, I think the RFC's state
that the MN use its home address as the source address (for both direct
and encasulating delivery styles).  If you could point to some text
that states otherwise, then I've got some code to fix...

--peter

 
> >RFC 3024 states:
> >
> >   Route optimization [4] introduces forward tunnels initiated at a
> >   correspondent host.  Since a mobile node may not know if the
> >   correspondent host can decapsulate packets, reverse tunnels in that
> >   context are not discussed here.
> >
> >Does the new -11 version of R-O contain some text about reverse
> >tunnels?  It's too bad I can't look at it.  I think you are saying
> >that, even if the MN is using an FA-located COA, it would "borrow"
> >this address for the purpose of sending packets to CNs with which it
> >had arranged for route optimization, while implementing reverse
> >tunneling.  Essentially these "reverse tunnels" would go back to CNs,
> >but as we can't expect the FA to do source routing per-CN, the MN must
> >take care of it.  However, I'm just making up protocol now - could
> >someone tell me whether -11 R-O deals with this?  Better yet, could
> >someone put a copy up somewhere that I can read?
> >
> 
> I wasn't proposing that the reverse tunnel go back to  the CN, only
> that the new FA be able to use the MN CoA to index to the reverse tunnel
> to the old FA, since the packet coming from the MN will have the
> CoA and not the home address as the source address. But, as mentioned,
> this is unnecessary if the old FA uses the L2 address to
> identify which packet should go through the tunnel to the old FA.
> 
> But you do bring up an interesting point about how to deal with the
> case where the reverse tunnel needs to run to the CN. As far as
> low latency is concerned, I think we can basically punt since
> the route optimization draft doesn't propose to solve the
> fundamental problem.
> 
> > > I think saying there is no security is a bit strong, there
> > > could be security, it could be prearranged via context transfer
> > > or even some configuration step. I think it would be more precise
> > > to say that the new FA is not expected to set up a security
> > > association in real time during the handover, but that it SHOULD,
> > > at its discretion, choose to support a reverse tunnel as well.
> >
> >Pre-arranged I could buy (although it would require some other MN from
> >that HA to have visited previously), but I hope we don't end up
> >transferring security associations.  SAs, especially IPSec SAs, are
> >indexed by IP address and I think it would be a bad idea to allow an
> >HA to start using an SA for a different communication endpoint just
> >because it started getting packets on it.
> >
> 
> OK.
> 
> >OK.  Does anyone have a copy of route optimization -11 that we could
> >use to resolve some of the questions above?
> >
> 
> I'll see if I can find one, but I think that I've got enough to go
> on now to rework the POST-REG/BETH  section of the low latency draft.
> Thanx.
> 
>                 jak



From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep  6 13:51:51 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04172
	for <mobileip-archive@odin.ietf.org>; Thu, 6 Sep 2001 13:51:50 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA10788;
	Thu, 6 Sep 2001 10:53:00 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id KAA19950;
	Thu, 6 Sep 2001 10:52:51 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f86HpkIQ024906
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 6 Sep 2001 10:51:46 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1/Submit) id f86HpjID024905
	for mobile-ip-dist; Thu, 6 Sep 2001 10:51:45 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from heliopolis.eng.sun.com (redhook.Eng.Sun.COM [152.70.24.37])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f86HpgIQ024898
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 10:51:42 -0700 (PDT)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.eng.sun.com (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id KAA16164
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 10:51:58 -0700 (PDT)
Message-Id: <200109061751.KAA16164@heliopolis.eng.sun.com>
Date: Thu, 6 Sep 2001 10:51:57 -0700 (PDT)
From: James Kempf <James.Kempf@Sun.COM>
Subject: RE: [mobile-ip] question on BET tear down
To: mobile-ip@sunroof.eng.sun.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: Ictp7LCQoSxt9sxWUlnwYw==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Hesham,

>	=> But you were explaining that you have it as an option
>	so perhaps it needs to be shown how this can happen. 
>	I can't see monitoring traffic for BU/BA as being an option really, 
>	routers just won't do that. Even if they do, you may not 

Why? If the traffic is encrypted, it would naturally be a problem, but
if its not, then it's a possibility. This is not meant to be a 
prescription but a way that the AR can optimize tunnel management,
more of a hint. Ultimately, the tunnel will time out anyway, these
techniques are to help optimize managment.

>	get a BA from CNs. So I'm not sure that having 
>	it as an option is useful because it is not a realistic one. 
>

According to Section 8.5 draft-ietf-mobileip-ipv6-13.txt (the latest draft I
have), the CN MUST send a BA to the MN if it receives a BU. So the only
reason that a MN would not receive a BAck is that it was dropped in transit.
Section 10.10 says that a MN SHOULD retransmit the BU until a BAck
is received. The draft does not state what the MN should do if 
it does not receive a BAck by MAX_BINDACK_TIMEOUT, perhaps it should.
But, should this occur, it would be no different than in standard
MIPv6, and would constitute a routing update failure. In BETH/FMIPv6,
the situation is better than in standard MIPv6 because the MN is
getting packets through the forward tunnel under its old CoA, so
if a routing update failure occurs, the MN can simply forgo 
sending the BU to the oAR, or the nAR can forgo tearing down
the tunnel when it sees packets going out under the MN's old
CoA.

>	Looking for the source address is not accurate either because
>	using a new CoA doesn't tell you that the routing is 
>	optimised or symmetric. 
>

I'm not sure I understand. This is a problem in standard MIP and
FMIPv6 as well. The forward tunnel is only needed as long as packets
are coming into the oAR with destination address the old CoA. The reverse tunnel
is only needed as long as packets are coming from the MN
with the old CoA as the source address. When that is no longer happening
the tunnel can be dropped. We could specify a timeout for how long
an AR should wait after seeing the last packet with the old CoA, but
it seems that this may depend on the network configuration and so
should be left up to the network administator. Am I missing something?

		jak



From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep  6 13:53:33 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04231
	for <mobileip-archive@odin.ietf.org>; Thu, 6 Sep 2001 13:53:32 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA11776;
	Thu, 6 Sep 2001 10:54:36 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id KAA20429;
	Thu, 6 Sep 2001 10:54:09 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f86Hr1IQ024942
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 6 Sep 2001 10:53:01 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1/Submit) id f86Hr1pE024941
	for mobile-ip-dist; Thu, 6 Sep 2001 10:53:01 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from heliopolis.eng.sun.com (redcoast.Eng.Sun.COM [152.70.28.21])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f86HqwIQ024934
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 10:52:58 -0700 (PDT)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.eng.sun.com (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id KAA16271
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 10:53:13 -0700 (PDT)
Message-Id: <200109061753.KAA16271@heliopolis.eng.sun.com>
Date: Thu, 6 Sep 2001 10:53:12 -0700 (PDT)
From: James Kempf <James.Kempf@Sun.COM>
Subject: Re: [mobile-ip] Low Latency Issue: Where to Run the Reverse Tunnel?
To: mobile-ip@sunroof.eng.sun.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: Ik8pDycEyp0SpltYZ18owg==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Ok, thanx Peter. I guess there is no problem with just sending the
home address and HA address in the RO case as well.

		jak

>Date: Thu, 06 Sep 2001 12:47:44 -0500
>From: Peter Lei <peter.lei@ieee.org>
>To: mobile-ip@sunroof.eng.sun.com
>Subject: Re: [mobile-ip] Low Latency Issue: Where to Run the Reverse Tunnel?
>
>Hi James,
>
>James Kempf wrote:
>> 
>> Hi Pete,
>> 
>> > > My concern was that packets originating at the MN will be
>> > > sent with the source address set to the care of address and
>> > > not the home address, as would be the case if no route optimization
>> > > were in effect.
>> >
>> >Ok, I'm lost.  I managed to find an old (-07) version of the route
>> >optimization draft, and I quickly searched through the new Reverse
>> >Tunneling RFC.  I couldn't find where this requirement is stated.  My
>> >current understanding of Route Optimization is that it only affects
>> >the forward direction traffic.
>> >
>> 
>> Right, but the MN will still put its CoA in as the source address
>> on outgoing packets, I think.
>
>I think the only time the MN would do this is if it is doing local
>decapsulation (ie. colocated COA).  Otherwise, I think the RFC's state
>that the MN use its home address as the source address (for both direct
>and encasulating delivery styles).  If you could point to some text
>that states otherwise, then I've got some code to fix...
>
>--peter
>
> 
>> >RFC 3024 states:
>> >
>> >   Route optimization [4] introduces forward tunnels initiated at a
>> >   correspondent host.  Since a mobile node may not know if the
>> >   correspondent host can decapsulate packets, reverse tunnels in that
>> >   context are not discussed here.
>> >
>> >Does the new -11 version of R-O contain some text about reverse
>> >tunnels?  It's too bad I can't look at it.  I think you are saying
>> >that, even if the MN is using an FA-located COA, it would "borrow"
>> >this address for the purpose of sending packets to CNs with which it
>> >had arranged for route optimization, while implementing reverse
>> >tunneling.  Essentially these "reverse tunnels" would go back to CNs,
>> >but as we can't expect the FA to do source routing per-CN, the MN must
>> >take care of it.  However, I'm just making up protocol now - could
>> >someone tell me whether -11 R-O deals with this?  Better yet, could
>> >someone put a copy up somewhere that I can read?
>> >
>> 
>> I wasn't proposing that the reverse tunnel go back to  the CN, only
>> that the new FA be able to use the MN CoA to index to the reverse tunnel
>> to the old FA, since the packet coming from the MN will have the
>> CoA and not the home address as the source address. But, as mentioned,
>> this is unnecessary if the old FA uses the L2 address to
>> identify which packet should go through the tunnel to the old FA.
>> 
>> But you do bring up an interesting point about how to deal with the
>> case where the reverse tunnel needs to run to the CN. As far as
>> low latency is concerned, I think we can basically punt since
>> the route optimization draft doesn't propose to solve the
>> fundamental problem.
>> 
>> > > I think saying there is no security is a bit strong, there
>> > > could be security, it could be prearranged via context transfer
>> > > or even some configuration step. I think it would be more precise
>> > > to say that the new FA is not expected to set up a security
>> > > association in real time during the handover, but that it SHOULD,
>> > > at its discretion, choose to support a reverse tunnel as well.
>> >
>> >Pre-arranged I could buy (although it would require some other MN from
>> >that HA to have visited previously), but I hope we don't end up
>> >transferring security associations.  SAs, especially IPSec SAs, are
>> >indexed by IP address and I think it would be a bad idea to allow an
>> >HA to start using an SA for a different communication endpoint just
>> >because it started getting packets on it.
>> >
>> 
>> OK.
>> 
>> >OK.  Does anyone have a copy of route optimization -11 that we could
>> >use to resolve some of the questions above?
>> >
>> 
>> I'll see if I can find one, but I think that I've got enough to go
>> on now to rework the POST-REG/BETH  section of the low latency draft.
>> Thanx.
>> 
>>                 jak
>



From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep  6 14:07:43 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04590
	for <mobileip-archive@odin.ietf.org>; Thu, 6 Sep 2001 14:07:42 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id MAA04345;
	Thu, 6 Sep 2001 12:08:44 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id LAA25550;
	Thu, 6 Sep 2001 11:08:30 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f86I6tIQ025065
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 6 Sep 2001 11:06:55 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1/Submit) id f86I6sgg025064
	for mobile-ip-dist; Thu, 6 Sep 2001 11:06:54 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f86I6oIQ025057
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 11:06:51 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id LAA24549
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 11:07:05 -0700 (PDT)
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id LAA11106
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 11:07:04 -0700 (PDT)
Received: from mira-sjc5-7.cisco.com (mira-sjc5-7.cisco.com [171.71.163.27])
	by sj-msg-core-1.cisco.com (8.11.3/8.9.1) with ESMTP id f86I74x02423
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 11:07:04 -0700 (PDT)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-7.cisco.com (Mirapoint)
	with ESMTP id ABI25701;
	Thu, 6 Sep 2001 11:06:46 -0700 (PDT)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id LAA24645; Thu, 6 Sep 2001 11:06:46 -0700 (PDT)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15255.47925.943702.696167@thomasm-u1.cisco.com>
Date: Thu, 6 Sep 2001 11:06:45 -0700 (PDT)
To: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Coexistence with other uses for routing header
In-Reply-To: <200109052150.f85Loh9d445394@jurassic.eng.sun.com>
References: <200109052150.f85Loh9d445394@jurassic.eng.sun.com>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Alper Yegin writes:
 > >    but I'd think that something that moves packets
 > >    toward their destination instead of toward
 > >    themselves is acting like a router, regardless
 > >    of what caused them to do so. Practically
 > >    speaking, I'd sure like some knob -- like the
 > >    router on/off switch -- which controls whether
 > >    my node acts as a forwarder regardless of how
 > >    something is trying to get me to forward.
 > 
 > For example Solaris has a "ip_forwarding" knob. Only when it is turned on, the 
 > box starts forwarding packets. It doesn't necessarily have to be running any 
 > "routing protocol" at this point (RIP, etc.). It can do forwarding using minimal 
 > routing table that contains on-link routes and default route.

Ah, yes, I didn't mean to imply that there was
anything actively populating its forwarding
tables. Colloquially, "router" means "forwarder"
IMO which may contain be nothing more than static
routes. Routing headers are in essence
self-describing single use routing updates :-)

So what were we talking about?

	Mike


From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep  6 15:42:36 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06875
	for <mobileip-archive@odin.ietf.org>; Thu, 6 Sep 2001 15:42:35 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA03784;
	Thu, 6 Sep 2001 12:43:45 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id MAA28957;
	Thu, 6 Sep 2001 12:43:35 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f86Jf7IQ025237
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 6 Sep 2001 12:41:07 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1/Submit) id f86Jf7nn025236
	for mobile-ip-dist; Thu, 6 Sep 2001 12:41:07 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from eastmail1.East.Sun.COM (eastmail1.East.Sun.COM [129.148.1.240])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f86Jf4IQ025229
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 12:41:04 -0700 (PDT)
Received: from onion.east.sun.com (onion.East.Sun.COM [129.148.174.110])
	by eastmail1.East.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id PAA21797
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 15:41:18 -0400 (EDT)
Received: (from glass@localhost)
	by onion.east.sun.com (8.9.3+Sun/8.9.3) id PAA23567
	for mobile-ip@sunroof.eng.sun.com; Thu, 6 Sep 2001 15:41:47 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f86HFJIQ024785
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 10:15:19 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id KAA08488
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 10:15:34 -0700 (PDT)
From: mobilecf@ece.gatech.edu
Received: from mail.ee.gatech.edu (mail.ee.gatech.edu [130.207.225.105])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id LAA17782
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 11:15:30 -0600 (MDT)
Received: from ece.gatech.edu (seiya.ece.gatech.edu [130.207.225.101])
	by mail.ee.gatech.edu (8.12.0.Beta19/8.11.3) with SMTP id f86HFVav027972
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 13:15:32 -0400 (EDT)
Received: from 130.207.230.13
        (SquirrelMail authenticated user mobilecf)
        by secure2.ece.gatech.edu with HTTP;
        Thu, 6 Sep 2001 13:15:32 -0400 (EDT)
Message-ID: <62068.130.207.230.13.999796532.squirrel@secure2.ece.gatech.edu>
Date: Thu, 6 Sep 2001 13:15:32 -0400 (EDT)
Subject: [mobile-ip] IEEE Ad Hoc Wireless Symposium Technical Program
To: <mobile-ip@sunroof.eng.sun.com>
X-Mailer: SquirrelMail (version 1.1.2)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
 
Content-Transfer-Encoding: 8bit

======================================================
IEEE Symposium on Ad Hoc Mobile Wireless Networks

    in conjunction with IEEE GLOBECOM 2001
            San Antonio, Texas, USA

           IEEE Communications Society

                 November 25-29
======================================================
Symposium Registration
  http://www.globecom2001.com/src/Register.shtml

Hotels/Acommodation
  http://www.globecom2001.com/src/Hotels.shtml

Symposium Web Page
  http://www.globecom2001.com/src/S_SAWN2001.shtml
------------------------------------------------------

TECHNICAL PROGRAM

SAW01 Special Session & Opening Address
Monday, November 26, 2001 9:00 am

Opening Address by Symposium Chairman

Invited Distinguished Speakers

  Professor Victor O. K. Li, University of Hong Kong
  Theme: A Reflection of Past Innovative Research in 
         Ad Hoc Networks
  Title: Transmission Range Control in Multihop Packet 
         Radio Networks

  Professor Nick Bambos, Stanford University
  Theme: Power Control for Wireless
  Title: Power Control and Management Issues in Next 
         Generation Wireless Devices and Networks

--------------------------------------------------------
Technical Sessions

---------------------------------
SAW02 Ad Hoc Routing
Monday, November 26, 2001 2:00 pm
---------------------------------
306 SAW02 - 1 LORA: Robust and Simple Routing Algorithms for Wireless
Mobile Ad Hoc Networks
Gunnar Carlsson, Mathematics Department, Stanford University, USA
Mung Chiang, Electrical Engineering Department, Stanford University, USA

564 SAW02 - 2 On Supporting Link Asymmetry in Mobile Ad Hoc Networks
Dongkyun Kim, School of Computer Science and Engineering, Seoul National
University, Seou, Korea
Yanghee Choi, School of Computer Science and Engineering, Seoul National
University, Seou, Korea

46 SAW02 - 3 Disjoint Routes for On Demand Routing Protocols in Ad Hoc
Networks
Evangelos Papapetrou, Aristotle University of Thessaloniki, Greece
Fotini-Niovi Pavlidou, AUTh, Greece

1018 SAW02 - 4 Anticipated Route Maintenance (ARM) in Location-Aided
Mobile Ad Hoc Networks
Brian VanVoorst, Honeywell Labs, USA
Seungjin Park, Michigan Technological University, USA

1150 SAW02 - 5 Self Organized Routing in Wide Area Mobile Ad-Hoc Networks
Jean-Yves LeBoudec, Swiss Federal Institute of Techology, Lausanne,
Switzerland
Ljubica Blazevic, Swiss Federal Institute of Techology, Lausanne,
Switzerland
Silvia Giordano, Swiss Federal Institute of Techology, Lausanne,
Switzerland

----------------------------------
SAW03 Power-Aware Protocols
Tuesday, November 27, 2001 9:00 am
----------------------------------
912 SAW03 - 1 Power Control Routing for Multi Hop Wireless Ad-hoc Network
Akira Matsumoto, Information Network Laboratory, Kansai University, Japan
Hiromi Okada, Information Network Laboratory, Kansai University, Japan
Kentaro Tsudaka, Information Network Laboratory, Kansai University, Japan
Masanobu Kawahara, Information Network Laboratory, Kansai University,
Japan

1111 SAW03 - 2 Performance of a very Low Power Wireless Protocol
Hwa Chang, Tufts University, USA
Joshua L. Jabs, US Air Force, USA
Robert Tingley, Draper Lab, USA

1276 SAW03 - 3 Power-Aware Fair Infrastructure Formation for Wireless
Mobile Ad Hoc Communications
Ahmed M. Safwat, Queen's University, Canada
Hossam S. Hassanein, Queen's University, Canada
Hussein T. Mouftah, Queen's University, Canada

1475 SAW03 - 4 A Location-aided Power-aware Routing Protocol in Mobile Ad
Hoc Networks
Baochun Li, University of Toronto, Canada
Yuan Xue, University of Illinois at Urbana-Champaign, USA

1519 SAW03 - 5 Location Aided Broadcast in Wireless Ad hoc Networks
Min-Te Sun, Department of Computer and Information Science, The Ohio
State University, USA
Ten-Hwang Lai, Department of Computer and Information Science, The Ohio
State University, USA
Wuchi Feng, Department of Computer and Information Science, The Ohio
State University, USA

----------------------------------
SAW04 TCP & Bluetooth
Tuesday, November 27, 2001 2:00 pm
----------------------------------
292 SAW04 - 1 Revealing TCP Incompatibility Problem in 802.11-based
Wireless Multi-hop Networks
Shugong Xu, Dept. EE, City College, USA
Tarek Saadawi, Dept. EE, City College, USA

878 SAW04 - 2 ENIC - An Improved Reliable Transport Scheme for Mobile Ad
Hoc Networks
Dong Sun, STEVENS INSTITUTE OF TECHNOLOGY, USA
Hong Man, STEVENS INSTITUTE OF TECHNOLOGY, USA

813 SAW04 - 3 Interference Aware Bluetooth Packet Scheduling
Issam Elbakkouri, NIST, USA
Nada Golmie, NIST, USA
Nicolas Chevrollier, NIST, USA

883 SAW04 - 4 A Bluetooth Scatternet Formation Algorithm
Ching Law, M.I.T., USA
Kai-Yeung Siu, M.I.T., USA

124 SAW04 - 5 Piconet Interference Modeling and Performance Evaluation of
Bluetooth MAC Protocol
Carlos de Morais Cordeiro, UFPE - Universidade Federal de Pernambuco,
Brazil
Dharma P. Agrawal, Center for Distributed and Mobile Computing,
University of Cincinnati, USA
Djamel Fawzi Hadj Sadok, UFPE - Universidade Federal de Pernambuco,
Brazil

----------------------------------
SAW05 MAC for Ad Hoc
Wednesday, November 28, 20 9:00 am
----------------------------------

076 SAW05 - 1 Performance Analysis of Multihop Packet CDMA Cellular
Networks
Ali Nabi Zadeh, George Mason University, USA
Bijan Jabbari, George Mason University, USA
Bijan Jabbari, George Mason University, USA

1097 SAW05 - 2 Adaptive Acquisition Collision Avoidance Multiple Access
for Multihop Ad Hoc Wireless Networks
Akira Fukuda, Dept. of Electrical Engineering, Shizuoka Univ., Japan
Jian-dong Li, Information Science Institute and National Key Lab. of ISN,
Xidian Univ., China
Kai Liu, National Key Lab. of ISN and Information Science Institute,
Xidian Univ., China

1257 SAW05 - 3 Traffic Sensitive MAC Algorithms in Multi-hop Radio
Networks
Oscar Manuel Somarriba Jarqu, National University of Engineering (UNI),
Nicaragua

471 SAW05 - 4 Space-Time Division Multiple Access (STDMA) and
Coordinated, Power-Aware MACA for Mobile Ad-hoc Networks
Konstantinos Gus Amouris, Renaissance Wireless, USA

457 SAW05 - 5 An Adaptive MAC Protocol for Wireless Ad Hoc Community
Network (WACNet) Using Electronically Steerable Passive Array Radiator
Antenna
Kazuo Hasuike, ATR Adaptive Communications Research Laboratory, Japan
Koichi Gyoda, ATR Adaptive Communications Research Laboratory, Japan
Shingo Horisawa, ATR Adaptive Communications Research Laboratory, Japan
Somprakash Bandyopadhyay, ATR Adaptive Communications Research
Laboratory, Japan

----------------------------------
SAW06 QoS Issues
Wednesday, November 28, 20 2:00 pm
----------------------------------
827 SAW06 - 1 Supporting QoS Routing in Mobile Ad Hoc Networks using
Probabilistic Locality and Load Balancing
Ehab Elmallah, Department of Computing Science, U. of Alberta, Canada
Hosam AboElFotoh, Department of Math. and Computing Science, Kuwait
Hossam Hassanein, Department of Computing and Information Science,
Queen's University, Canada

1159 SAW06 - 2 Impact of Interferences on Bandwidth Reservation for Ad
Hoc Networks: a First Theoretical Study
Bertet Karell, L3I/Universit de La Rochelle, France
Guerin lassous Isabelle, INRIA/ENS Lyon, France
Viennot Laurent, INRIA Rocquencourt, France

420 SAW06 - 3 Resource Allocation for QoS Provisioning in Wireless Ad Hoc
Networks
Daniel ONeill, Stanford University, USA
David Jonathan Julian, Stanford University, USA
Mung Chiang, Stanford University, USA
Steven Boyd, Stanford University, USA

530 SAW06 - 4 A Low Power Protocol to Broadcast Real-time Data Traffic in
a Clustered Ad Hoc Network
Juan Carlos Cano, Universidad Politecnica de Valencia, Spain
Pietro Manzoni, Universidad Politecnica de Valencia, Spain

831 SAW06 - 5 Phase Transition Phenomena in Wireless Ad-Hoc Networks
Bhaskar Krishnamachari, School of Electrical and Computer Engineering,
Cornell University, USA
Ramon Bejar, Department of Computer Science, Cornell University, USA
Stephen B. Wicker, School of Electrical and Computer Engineering, Cornell
University, USA 

----------------------------------
SAW07 Systems, Protocols, Services
Wednesday, November 28, 20 2:00 pm
----------------------------------
416 SAW07 - 1 Ad Hoc Positioning System (APS)
Badri Nath, Rutgers University, USA
Dragos Niculescu, Rutgers University, USA

575 SAW07 - 2 Optimal Threshold Energy Level of Energy Efficient MAC for
Energy-limited Ad-hoc Networks
Dong-Ho Cho, Korea Advanced Institute of Science and Technology (KAIST),
Korea
Kyu-Tae Jin, Korea Advanced Institute of Science and Technology (KAIST),
Korea

1376 SAW07 - 3 Weighted Hierarchical Backoff Algorithm for Wireless
Ad-hoc Networks
Timucin Ozugur, Alcatel Research and Innovation Center, USA

1432 SAW07 - 4 Low Power Distributed MAC for Ad Hoc Sensor Radio Networks
Chunlong Guo, Berkeley Wireless Research Center, USA
Jan Rabaey, Berkeley Wireless Research Center, USA
Lizhi Charlie Zhong, Berkeley Wireless Research Center, USA

1008 SAW07 - 5 A Fully Distributed Mediator Based Service Location
Protocol in Ad Hoc Networks
Fleury Eric, LORIA INRIA, France
Koubaa Hend, LORIA INRIA, France

----------------------------------------------------------------------------





From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep  6 15:51:33 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07000
	for <mobileip-archive@odin.ietf.org>; Thu, 6 Sep 2001 15:51:33 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id NAA22958;
	Thu, 6 Sep 2001 13:52:33 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id MAA01117;
	Thu, 6 Sep 2001 12:52:23 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f86JoXIQ025301
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 6 Sep 2001 12:50:33 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1/Submit) id f86JoXQP025300
	for mobile-ip-dist; Thu, 6 Sep 2001 12:50:33 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f86JoTIQ025293
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 12:50:29 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id MAA00678
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 12:50:43 -0700 (PDT)
Received: from motgate.mot.com (motgate.mot.com [129.188.136.100])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA13458
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 13:51:18 -0600 (MDT)
Received: [from pobox4.mot.com (pobox4.mot.com [10.64.251.243]) by motgate.mot.com (motgate 2.1) with ESMTP id MAA13591 for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 12:50:41 -0700 (MST)]
Received: [from il27exm07.cig.mot.com (IL27EXM07.cig.mot.com [136.182.15.116]) by pobox4.mot.com (MOT-pobox4 2.0) with ESMTP id MAA23652 for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 12:50:41 -0700 (MST)]
Received: by IL27EXM07.cig.mot.com with Internet Mail Service (5.5.2654.52)
	id <RPK6L0AD>; Thu, 6 Sep 2001 14:50:40 -0500
Message-ID: <35DBB8B7AC89D4118E98009027B1009B017A9FD5@IL27EXM10.cig.mot.com>
From: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>
To: "'mobile-ip@sunroof.eng.sun.com'" <mobile-ip@sunroof.eng.sun.com>
Subject: RE: [mobile-ip] question on BET tear down
Date: Thu, 6 Sep 2001 14:50:40 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2654.52)
Content-Type: text/plain
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

James,

Thanks for the reply, please see below.

-----Original Message-----
From: James Kempf [mailto:James.Kempf@Sun.COM]
Sent: Thursday, September 06, 2001 11:48 AM
To: mobile-ip@sunroof.eng.sun.com
Subject: RE: [mobile-ip] question on BET tear down


Hesham,

>> >Also I am getting the impression that MN might like to get
>> >its traffic tunneled to it through BET, even after nCoA acquisition.
>> >Hence at the end the nAR would have to send another HRqst and this
>> >time with lifetime=0 to tear the tunnel down, correct?
>> >
>> 
>> When L3 handover is complete (== new CoA aquisition is complete)
including
>> BU/BAck transactions with HA, CNs, and possibly old AR, then either
>> the old or new AR can initiate tunnel tear down. Prior to that,
>> tearing down the tunnel runs the risk of stranding any in-flight
>> packets. The new AR should renew the tunnel when it is about to expire,
>> even if the MN is in the process of aquiring a new CoA. Only when 
>> the old or new AR have proof that the MN has a new CoA should
>> they tear down the tunnel. Such proof was mentioned in the previous
>> email and is described in the forthcoming draft.
>> 
>	=> So for the nAR to know that the above has happened, 
>	does it monitor te MN's traffic to see whether BAcks from 
>	the HA and CN have been received ?
>
>	Hesham


As I mentioned in my reply to Madjid yestereday, it doesn't have to.
The oAR can initiate the tunnel tear down if the MN has a
security association (and it *must* in order to send a BU) as
in standard FMIPv6, or the nAR can simply notice that the MN is
sending packets with the nCoA as the source address, so the
tunnel is no longer needed. The nAR can monitor the traffic
to match BU/BAck if it chooses, but it is not necessary.


		jak


Madjid> Ok, the problem is the following scenario:

the MN has acquired nCoA, but the tunnel is
not torn down, since we want to make sure everybody knows about this nCoA,
in the mean time, traffic might still be going through the tunnel (before it
is torn down), which means the header compression states are also changing.
This means as long as the traffic is flowing through the tunnel, I cannot 
transfer the header compression context from oldAR to newAR.

So I am trying to find out exactly when the traffic stops:
I guess this is when the tunnel is torn down. But when does tear down
 happen:

1-oldAR receives a BU from MN and sends a tunnel tear down to nAR.
2-nAR somehow finds out MN is using its newCoA, by monitoring
MN's traffic.
Does the  MN suddenly starts using its newCoA, without notifying nAR?

I thought in FMIP, the MN sends an NA and gets some ack back from nAR.
Shouldn't that be used as a sure tunnel tear down trigger?

Am I making any sense?

Madjid


From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep  6 15:53:16 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07070
	for <mobileip-archive@odin.ietf.org>; Thu, 6 Sep 2001 15:53:15 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id NAA23961;
	Thu, 6 Sep 2001 13:54:13 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id MAA01434;
	Thu, 6 Sep 2001 12:54:07 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f86JqkIQ025324
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 6 Sep 2001 12:52:46 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1/Submit) id f86Jqkjw025323
	for mobile-ip-dist; Thu, 6 Sep 2001 12:52:46 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f86JqfIQ025313
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 12:52:41 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id MAA01178
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 12:52:39 -0700 (PDT)
Received: from motgate.mot.com (motgate.mot.com [129.188.136.100])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id MAA19693
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 12:52:38 -0700 (PDT)
Received: [from pobox4.mot.com (pobox4.mot.com [10.64.251.243]) by motgate.mot.com (motgate 2.1) with ESMTP id MAA15147 for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 12:52:38 -0700 (MST)]
Received: [from il75exm04.cig.mot.com ([136.182.110.113]) by pobox4.mot.com (MOT-pobox4 2.0) with ESMTP id MAA24681 for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 12:52:37 -0700 (MST)]
Received: by IL75EXM04 with Internet Mail Service (5.5.2654.52)
	id <QPL7YK21>; Thu, 6 Sep 2001 14:52:37 -0500
Message-ID: <35DBB8B7AC89D4118E98009027B1009B017A9FD6@IL27EXM10.cig.mot.com>
From: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>
To: "'mobile-ip@sunroof.eng.sun.com'" <mobile-ip@sunroof.eng.sun.com>
Subject: RE: [mobile-ip] Low Latency Issue: Where to Run the Reverse Tunne
	 l?
Date: Thu, 6 Sep 2001 14:52:35 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2654.52)
Content-Type: text/plain
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Thanks Alex.

Madjid

-----Original Message-----
From: Alexandru Petrescu [mailto:petrescu@crm.mot.com]
Sent: Thursday, September 06, 2001 7:13 AM
To: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Low Latency Issue: Where to Run the Reverse
Tunne l?


Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com> writes:
> Hi,
> 
> looks like this draft is not accessible:
> 
> ftp://ftp.isi.edu/internet-drafts/draft-calhoun-mobileip-gre-ext-00.txt
> 
>  01 is on the ftp site but it has expired last week.
> Do you have a copy?
> 
> thanks,
> Madjid

We keep older versions of I-D's.

Alex


INTERNET DRAFT                                            Pat R. Calhoun
Category: Standards Track                         Sun Microsystems, Inc.
Title: draft-calhoun-mobileip-gre-ext-00.txt                  Tom Hiller
Date: September 2000                                     Peter J. McCann
                                                     Lucent Technologies
                                                             Yingchun Xu
                                                        3Com Corporation



                             GRE Extensions



Status of this Memo

   This document is an individual contribution for consideration by the
   Mobile IP Working Group of the Internet Engineering Task Force.
   Comments should be submitted to the mobile-
   ip@standards.nortelnetworks.com mailing list.

   Distribution of this memo is unlimited.

   This document is an Internet-Draft and is in full conformance with
   all provisions of Section 10 of RFC2026.  Internet-Drafts are working
   documents of the Internet Engineering Task Force (IETF), its areas,
   and its working groups.  Note that other groups may also distribute
   working documents as Internet-Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at:

      http://www.ietf.org/ietf/1id-abstracts.txt

   The list of Internet-Draft Shadow Directories can be accessed at:

      http://www.ietf.org/shadow.html.

   Copyright   (C) The Internet Society 2000.  All Rights Reserved.


Abstract

   The GRE specification contains a Key field, which MAY contain a value



Calhoun et al.           expires February 2001                  [Page 1]





INTERNET DRAFT                                            September 2000


   that is used to identify a particular GRE "flow". This specification
   defines a new Mobile IP extensions that is used to exchange the value
   to be used in the GRE Key field.

   This specification also introduces a new extension, called the GRE
   Type extension, which is used during registration to signal the GRE
   type that will be used for the Mobile Node's session. This extension
   is deemed important in order to allow the Mobility Agents to setup
   the necessary protocol interfaces prior to receiving the mobile's
   traffic.


Table of Contents

      1.0  Introduction
            1.1  Requirements language
            1.2  Fast handoffs
      2.0  GRE Key extension
      3.0  GRE Type extension
      4.0  Error Values
      5.0  GRE Encapsulation
      6.0  IANA Considerations
      7.0  Security Considerations
      8.0  References
      9.0  Acknowledgements
      10.0  Authors' Addresses
      11.0  Full Copyright Statement
























Calhoun et al.           expires February 2001                  [Page 2]





INTERNET DRAFT                                            September 2000


1.0  Introduction

   The GRE specification contains a Key field, which MAY contain a value
   that is used to identify a particular GRE "flow". This specification
   defines a new Mobile IP extensions that is used to exchange the value
   to be used in the GRE Key field.

   This specification also introduces a new extension, called the GRE
   Type extension, which is used during registration to signal the GRE
   type that will be used for the Mobile Node's session. This extension
   is deemed important in order to allow the Mobility Agents to setup
   the necessary protocol interfaces prior to receiving the mobile's
   traffic.


1.1  Requirements language

   In this document, the key words "MAY", "MUST, "MUST NOT", "optional",
   "recommended", "SHOULD", and "SHOULD NOT", are to be interpreted as
   described in [2].


2.0  GRE Key extension

   The GRE Key extension MAY be included in Registration Requests [1],
   and Regional Registration Requests [3] whose 'G' bit is enabled. The
   GRE Key extension is used to inform the recipient of the Mobile IP
   request of the value to be used in GRE's Key field.

       0                   1                   2                   3
       0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |     Type      |   Length      |           Reserved            |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                        Key Identifier                         |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

      Type

         TBD (non-skippable) [1]

      Length

         6

      Reserved

         This field MUST be set to zero (0).



Calhoun et al.           expires February 2001                  [Page 3]





INTERNET DRAFT                                            September 2000


      Key Identifier

         This is a four octet value assigned in the Registration or
         Regional Registration Request, and inserted in every GRE frame
         (see Section 5).


3.0  GRE Type extension

   The GRE Type extension MAY be included in Registration Requests [1],
   and Regional Registration Requests [3] whose 'G' bit is enabled. The
   GRE Type extension is used to signal to the peer the type of traffic
   that will be sent from the Mobile Node encapsulated in GRE. Note that
   only one GRE Type extension MAY be present in a request.

   If the GRE Type is not supported by the receiver of the Registration
   or Regional Registration Request, it MUST return the appropriate
   Reply with the Code field set to PROTO_NOT_SUPPORTED (see Section 4).

   If the GRE Type extension was present in the Request, all traffic for
   the Mobile Node MUST be of the type specified in this extension.

       0                   1                   2                   3
       0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |     Type      |   Length      |           GRE Type            |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

      Type

         TBD (skippable) [1]

      Length

         6

      GRE Type

         The GRE protocol type, as defined in [4].


4.0  Error Values

   The following table contains the name of Code [1] to be returned in a
   Registration and Regional Registration Replies, the value for the
   Code, and the section in which the error is first mentioned in this
   specification.




Calhoun et al.           expires February 2001                  [Page 4]





INTERNET DRAFT                                            September 2000


      Error Name               Value   Section of Document
      ----------------------   -----   -------------------
      PROTO_NOT_SUPPORTED       TBD    3.0


5.0  GRE Encapsulation

   When the Registration or Regional Registration Request has the 'G'
   bit enabled, contains the GRE Key extension, all GRE [4] encapsulated
   packets for the Mobile Node MUST include the value found in the
   extension within the GRE Key field [5]. The receiver of the GRE frame
   will use the Key field to identify the particular Mobility Binding.


6.0  IANA Considerations

   The GRE Key extension defined in Section 2 and the GRE Type extension
   are Mobile IP registration extension as defined in RFC 2002 [1] and
   extended in RFC 2356 [6]. IANA should assign a value of 131 for this
   purpose.

   The Code values defined in Section 4 are error codes as defined in
   RFC 2002 [1] and extended in RFC 2344 [7] and RFC 2356 [6].


7.0  Security Considerations

   This specification does not introduce any new security
   considerations, beyond those described in [1].


8.0  References


   [1]  C. Perkins, Editor. "IP Mobility Support". RFC 2002. October
        1996.

   [2]  S. Bradner. "Key words for use in RFCs to Indicate Requirement
        Levels". BCP 14. RFC 2119. March 1997.

   [3]  E. Gustafsson, A. Jonsson, C. Perkins. "Mobile IP Regional
        Registration", draft-ietf-mobileip-reg-tunnel-02.txt (work in
        progress), March 2000.

   [4]  Farinacci, D., Li, T., Hanks, S., Meyer, D. and Traina, P.,
        "Generic Routing Encapsulation (GRE)," RFC 2784, March 2000.

   [5]  Gopal Dommety. "Key and Sequence Number Extensions to GRE".



Calhoun et al.           expires February 2001                  [Page 5]





INTERNET DRAFT                                            September 2000


        draft-dommety-gre-ext-04.txt, June 2000. (work in progress)

   [6]  Montenegro, G. and V. Gupta, "Sun's SKIP Firewall Traversal for
        Mobile IP", RFC 2356, June 1998.

   [7]  G. Montenegro.  Reverse Tunneling for Mobile IP.  Request for
        Comments (Proposed Standard) 2344, Internet Engineering Task
        Force, May 1998.


9.0  Acknowledgements

   The authors would like to thank the authors of draft-ietf-mobileip-
   3Gwireless-ext-04.txt, given that some text from that Internet Draft
   was copied into this specification.


10.0  Authors' Addresses

   Questions about this memo can be directed to:

      Pat R. Calhoun
      Network and Security Research Center, Sun Labs
      Sun Microsystems, Inc.
      15 Network Circle
      Menlo Park, California, 94025
      USA

       Phone:  +1 650 786 7733
         Fax:  +1 650 786 6445
      E-mail:  pcalhoun@eng.sun.com

      Gopal Dommety
      Cisco Systems
      170 West Tasman Drive
      San Jose, CA 95134

       Phone: +1 408 525 1404
      E-mail: gdommety@cisco.com












Calhoun et al.           expires February 2001                  [Page 6]





INTERNET DRAFT                                            September 2000


      Tom Hiller
      Lucent Technologies
      Rm 2F-218
      263 Shuman Blvd
      Naperville, IL  60566-7050
      USA

       Phone: +1 630 979 7673
         Fax: +1 630 979 7673
      E-Mail: tom.hiller@lucent.com

      Peter J. McCann
      Lucent Technologies
      Rm 2Z-305
      263 Shuman Blvd
      Naperville, IL  60566-7050
      USA

       Phone: +1 630 713 9359
         Fax: +1 630 713 4982
      E-Mail: mccap@lucent.com


      Yingchun Xu
      3Com Corporation
      1800 West Central Road
      Mount Prospect,
      USA 60056

       Phone: +1 847 342 6814
      E-mail: Yingchun_Xu@3com.com


11.0  Full Copyright Statement

   Copyright (C) The Internet Society (2000).  All Rights Reserved.

   This document and translations of it may be copied and furnished to
   others, and derivative works that comment on or otherwise explain it
   or assist in its implementation may be prepared, copied, published
   and distributed, in whole or in part, without restriction of any
   kind, provided that the above copyright notice and this paragraph are
   included on all such copies and derivative works. However, this docu-
   ment itself may not be modified in any way, such as by removing the
   copyright notice or references to the Internet Society or other
   Internet organizations, except as needed for the purpose of develop-
   ing Internet standards in which case the procedures for copyrights
   defined in the Internet Standards process must be followed, or as



Calhoun et al.           expires February 2001                  [Page 7]





INTERNET DRAFT                                            September 2000


   required to translate it into languages other than  English. The lim-
   ited permissions granted above are perpetual and will not be revoked
   by the Internet Society or its successors or assigns. This document
   and the information contained herein is provided on an "AS IS" basis
   and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DIS-
   CLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED
   TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT
   INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR
   FITNESS FOR A PARTICULAR PURPOSE."










































Calhoun et al.           expires February 2001                  [Page 8]


From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep  6 15:55:06 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07093
	for <mobileip-archive@odin.ietf.org>; Thu, 6 Sep 2001 15:55:06 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA09690;
	Thu, 6 Sep 2001 12:56:11 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id MAA01858;
	Thu, 6 Sep 2001 12:56:00 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f86JrlIQ025350
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 6 Sep 2001 12:53:47 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1/Submit) id f86JrlW8025349
	for mobile-ip-dist; Thu, 6 Sep 2001 12:53:47 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f86JrhIQ025339
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 12:53:43 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id MAA26330
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 12:53:57 -0700 (PDT)
Received: from albatross-ext.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA14919
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 13:54:32 -0600 (MDT)
Received: from esealnt462.al.sw.ericsson.se (ESEALNT462.al.sw.ericsson.se [153.88.251.62])
	by albatross.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id f86JrsK24859
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 21:53:54 +0200 (MEST)
Received: FROM esealnt742.al.sw.ericsson.se BY esealnt462.al.sw.ericsson.se ; Thu Sep 06 21:53:53 2001 +0200
Received: by esealnt742.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <NBWN4LYC>; Thu, 6 Sep 2001 21:47:01 +0200
Message-ID: <034BEFD03799D411A59F00508BDF754603008C80@esealnt448.al.sw.ericsson.se>
From: "Hesham Soliman  (ERA)" <Hesham.Soliman@era.ericsson.se>
To: "'mobile-ip@sunroof.eng.sun.com'" <mobile-ip@sunroof.eng.sun.com>
Subject: RE: [mobile-ip] Low Latency Issue: Where to Run the Reverse Tunne
	l?
Date: Thu, 6 Sep 2001 21:53:45 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

[ I haven't expressed my opinion on this to the rest of the 
authors so I'll just say it on the list]

James, 

	I'm just as confused as Pete, your use of "CoA" in the case
	where an FA is used seems really strange to me. 
	Are you saying the MN has a colocated CoA ? 
	If so what is the FA (or low latency draft's) role here ?

	Hesham



> > > My concern was that packets originating at the MN will be
> > > sent with the source address set to the care of address and
> > > not the home address, as would be the case if no route optimization
> > > were in effect. 
> >
> >Ok, I'm lost.  I managed to find an old (-07) version of the route
> >optimization draft, and I quickly searched through the new Reverse
> >Tunneling RFC.  I couldn't find where this requirement is stated.  My
> >current understanding of Route Optimization is that it only affects
> >the forward direction traffic.
> >
> 
> Right, but the MN will still put its CoA in as the source address
> on outgoing packets, I think.
> 
> >RFC 3024 states:
> >
> >   Route optimization [4] introduces forward tunnels initiated at a
> >   correspondent host.  Since a mobile node may not know if the
> >   correspondent host can decapsulate packets, reverse tunnels in that
> >   context are not discussed here.
> >
> >Does the new -11 version of R-O contain some text about reverse
> >tunnels?  It's too bad I can't look at it.  I think you are saying
> >that, even if the MN is using an FA-located COA, it would "borrow"
> >this address for the purpose of sending packets to CNs with which it
> >had arranged for route optimization, while implementing reverse
> >tunneling.  Essentially these "reverse tunnels" would go back to CNs,
> >but as we can't expect the FA to do source routing per-CN, the MN must
> >take care of it.  However, I'm just making up protocol now - could
> >someone tell me whether -11 R-O deals with this?  Better yet, could
> >someone put a copy up somewhere that I can read?
> >
> 
> I wasn't proposing that the reverse tunnel go back to  the CN, only
> that the new FA be able to use the MN CoA to index to the reverse tunnel
> to the old FA, since the packet coming from the MN will have the
> CoA and not the home address as the source address. But, as mentioned,
> this is unnecessary if the old FA uses the L2 address to
> identify which packet should go through the tunnel to the old FA.
> 
> But you do bring up an interesting point about how to deal with the
> case where the reverse tunnel needs to run to the CN. As far as
> low latency is concerned, I think we can basically punt since
> the route optimization draft doesn't propose to solve the
> fundamental problem.
> 
> > > I think saying there is no security is a bit strong, there
> > > could be security, it could be prearranged via context transfer
> > > or even some configuration step. I think it would be more precise
> > > to say that the new FA is not expected to set up a security 
> > > association in real time during the handover, but that it SHOULD,
> > > at its discretion, choose to support a reverse tunnel as well.
> >
> >Pre-arranged I could buy (although it would require some other MN from
> >that HA to have visited previously), but I hope we don't end up
> >transferring security associations.  SAs, especially IPSec SAs, are
> >indexed by IP address and I think it would be a bad idea to allow an
> >HA to start using an SA for a different communication endpoint just
> >because it started getting packets on it.
> >
> 
> OK.
> 
> >OK.  Does anyone have a copy of route optimization -11 that we could
> >use to resolve some of the questions above?
> >
> 
> I'll see if I can find one, but I think that I've got enough to go
> on now to rework the POST-REG/BETH  section of the low latency draft.
> Thanx.
> 
> 		jak


From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep  6 16:03:19 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA07352
	for <mobileip-archive@odin.ietf.org>; Thu, 6 Sep 2001 16:03:18 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA13043;
	Thu, 6 Sep 2001 13:04:31 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id NAA03621;
	Thu, 6 Sep 2001 13:04:11 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f86K2ZIQ025438
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 6 Sep 2001 13:02:35 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1/Submit) id f86K2YHG025437
	for mobile-ip-dist; Thu, 6 Sep 2001 13:02:34 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f86K2VIQ025430
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 13:02:31 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id NAA26136
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 13:02:45 -0700 (PDT)
Received: from albatross-ext.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id NAA23649
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 13:02:44 -0700 (PDT)
Received: from esealnt462.al.sw.ericsson.se (ESEALNT462.al.sw.ericsson.se [153.88.251.62])
	by albatross.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id f86K2hK25764
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 22:02:43 +0200 (MEST)
Received: FROM esealnt400.al.sw.ericsson.se BY esealnt462.al.sw.ericsson.se ; Thu Sep 06 22:02:42 2001 +0200
Received: by esealnt400 with Internet Mail Service (5.5.2653.19)
	id <NBWWF7T3>; Thu, 6 Sep 2001 22:02:35 +0200
Message-ID: <034BEFD03799D411A59F00508BDF754603008C81@esealnt448.al.sw.ericsson.se>
From: "Hesham Soliman  (ERA)" <Hesham.Soliman@era.ericsson.se>
To: "'mobile-ip@sunroof.eng.sun.com'" <mobile-ip@sunroof.eng.sun.com>
Subject: RE: [mobile-ip] question on BET tear down
Date: Thu, 6 Sep 2001 22:02:34 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

> >	=> But you were explaining that you have it as an option
> >	so perhaps it needs to be shown how this can happen. 
> >	I can't see monitoring traffic for BU/BA as being an option really, 
> >	routers just won't do that. Even if they do, you may not 
> 
> Why? If the traffic is encrypted, it would naturally be a problem, but
> if its not, then it's a possibility. This is not meant to be a 
> prescription but a way that the AR can optimize tunnel management,
> more of a hint. Ultimately, the tunnel will time out anyway, these
> techniques are to help optimize managment.
> 
	=> I didn't say it's impossible, I said that router jsimply won't 
	do it. It's an unnecessary and unrealistic thing to expect. 
	It adds delays per packet for no reason.

> >	get a BA from CNs. So I'm not sure that having 
> >	it as an option is useful because it is not a realistic one. 
> >
> 
> According to Section 8.5 draft-ietf-mobileip-ipv6-13.txt (the latest draft I
> have), the CN MUST send a BA to the MN if it receives a BU. So the only
> reason that a MN would not receive a BAck is that it was dropped in transit.
> 
	=> Section 8.5:

	   "When any node receives a packet containing a Binding Update option
	   in which the Acknowledge (A) bit is set, it MUST return a Binding
	   Acknowledgement option acknowledging receipt of the Binding Update."

	You've ignored the "A flag set" part.

> >	Looking for the source address is not accurate either because
> >	using a new CoA doesn't tell you that the routing is 
> >	optimised or symmetric. 
> >
> 
> I'm not sure I understand. This is a problem in standard MIP and
> FMIPv6 as well. The forward tunnel is only needed as long as packets
> are coming into the oAR with destination address the old CoA. The reverse tunnel
> is only needed as long as packets are coming from the MN
> with the old CoA as the source address. When that is no longer happening
> the tunnel can be dropped. 
> 
	=> Only in one direction, because packets may stillbe forwarded 
	from the old AR. 

	Hesham


> We could specify a timeout for how long
> an AR should wait after seeing the last packet with the old CoA, but
> it seems that this may depend on the network configuration and so
> should be left up to the network administator. Am I missing something?
> 
> 		jak


From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep  6 16:04:50 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA07473
	for <mobileip-archive@odin.ietf.org>; Thu, 6 Sep 2001 16:04:49 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA13736;
	Thu, 6 Sep 2001 13:05:57 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id NAA03946;
	Thu, 6 Sep 2001 13:05:44 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f86K4NIQ025464
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 6 Sep 2001 13:04:23 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1/Submit) id f86K4NgB025463
	for mobile-ip-dist; Thu, 6 Sep 2001 13:04:23 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from heliopolis.eng.sun.com (heliopolis.Eng.Sun.COM [152.70.1.39])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f86K4JIQ025456
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 13:04:19 -0700 (PDT)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.eng.sun.com (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id NAA23816
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 13:04:34 -0700 (PDT)
Message-Id: <200109062004.NAA23816@heliopolis.eng.sun.com>
Date: Thu, 6 Sep 2001 13:04:33 -0700 (PDT)
From: James Kempf <James.Kempf@Sun.COM>
Subject: RE: [mobile-ip] Low Latency Issue: Where to Run the Reverse Tunne l?
To: mobile-ip@sunroof.eng.sun.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: jgBSCghBtq6tAa0l5jtCbA==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Hesham,

As Peter pointed out, this is not an issue since the MN uses its 
home address as the source address regardless of whether route
optimization is in effect, unless the CoA is colocated.

		jak
		
>From: "Hesham Soliman  (ERA)" <Hesham.Soliman@era.ericsson.se>
>To: "'mobile-ip@sunroof.eng.sun.com'" <mobile-ip@sunroof.eng.sun.com>
>Subject: RE: [mobile-ip] Low Latency Issue: Where to Run the Reverse Tunne l?
>Date: Thu, 6 Sep 2001 21:53:45 +0200 
>
>[ I haven't expressed my opinion on this to the rest of the 
>authors so I'll just say it on the list]
>
>James, 
>
>	I'm just as confused as Pete, your use of "CoA" in the case
>	where an FA is used seems really strange to me. 
>	Are you saying the MN has a colocated CoA ? 
>	If so what is the FA (or low latency draft's) role here ?
>
>	Hesham
>
>
>
>> > > My concern was that packets originating at the MN will be
>> > > sent with the source address set to the care of address and
>> > > not the home address, as would be the case if no route optimization
>> > > were in effect. 
>> >
>> >Ok, I'm lost.  I managed to find an old (-07) version of the route
>> >optimization draft, and I quickly searched through the new Reverse
>> >Tunneling RFC.  I couldn't find where this requirement is stated.  My
>> >current understanding of Route Optimization is that it only affects
>> >the forward direction traffic.
>> >
>> 
>> Right, but the MN will still put its CoA in as the source address
>> on outgoing packets, I think.
>> 
>> >RFC 3024 states:
>> >
>> >   Route optimization [4] introduces forward tunnels initiated at a
>> >   correspondent host.  Since a mobile node may not know if the
>> >   correspondent host can decapsulate packets, reverse tunnels in that
>> >   context are not discussed here.
>> >
>> >Does the new -11 version of R-O contain some text about reverse
>> >tunnels?  It's too bad I can't look at it.  I think you are saying
>> >that, even if the MN is using an FA-located COA, it would "borrow"
>> >this address for the purpose of sending packets to CNs with which it
>> >had arranged for route optimization, while implementing reverse
>> >tunneling.  Essentially these "reverse tunnels" would go back to CNs,
>> >but as we can't expect the FA to do source routing per-CN, the MN must
>> >take care of it.  However, I'm just making up protocol now - could
>> >someone tell me whether -11 R-O deals with this?  Better yet, could
>> >someone put a copy up somewhere that I can read?
>> >
>> 
>> I wasn't proposing that the reverse tunnel go back to  the CN, only
>> that the new FA be able to use the MN CoA to index to the reverse tunnel
>> to the old FA, since the packet coming from the MN will have the
>> CoA and not the home address as the source address. But, as mentioned,
>> this is unnecessary if the old FA uses the L2 address to
>> identify which packet should go through the tunnel to the old FA.
>> 
>> But you do bring up an interesting point about how to deal with the
>> case where the reverse tunnel needs to run to the CN. As far as
>> low latency is concerned, I think we can basically punt since
>> the route optimization draft doesn't propose to solve the
>> fundamental problem.
>> 
>> > > I think saying there is no security is a bit strong, there
>> > > could be security, it could be prearranged via context transfer
>> > > or even some configuration step. I think it would be more precise
>> > > to say that the new FA is not expected to set up a security 
>> > > association in real time during the handover, but that it SHOULD,
>> > > at its discretion, choose to support a reverse tunnel as well.
>> >
>> >Pre-arranged I could buy (although it would require some other MN from
>> >that HA to have visited previously), but I hope we don't end up
>> >transferring security associations.  SAs, especially IPSec SAs, are
>> >indexed by IP address and I think it would be a bad idea to allow an
>> >HA to start using an SA for a different communication endpoint just
>> >because it started getting packets on it.
>> >
>> 
>> OK.
>> 
>> >OK.  Does anyone have a copy of route optimization -11 that we could
>> >use to resolve some of the questions above?
>> >
>> 
>> I'll see if I can find one, but I think that I've got enough to go
>> on now to rework the POST-REG/BETH  section of the low latency draft.
>> Thanx.
>> 
>> 		jak



From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep  6 16:09:52 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA07636
	for <mobileip-archive@odin.ietf.org>; Thu, 6 Sep 2001 16:09:52 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA16286;
	Thu, 6 Sep 2001 13:11:03 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id NAA04963;
	Thu, 6 Sep 2001 13:10:55 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f86K9oIQ025520
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 6 Sep 2001 13:09:50 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1/Submit) id f86K9n3s025519
	for mobile-ip-dist; Thu, 6 Sep 2001 13:09:49 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from heliopolis.eng.sun.com (bigbang.Eng.Sun.COM [152.70.8.30])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f86K9kIQ025512
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 13:09:46 -0700 (PDT)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.eng.sun.com (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id NAA24128
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 13:10:01 -0700 (PDT)
Message-Id: <200109062010.NAA24128@heliopolis.eng.sun.com>
Date: Thu, 6 Sep 2001 13:10:00 -0700 (PDT)
From: James Kempf <James.Kempf@Sun.COM>
Subject: RE: [mobile-ip] Low Latency Issue: Should HTT be MUST, SHOULD, or MAY?
To: mobile-ip@sunroof.eng.sun.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: kULhdsPRTr5D8A5L2CaSeA==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Raj/All,

OK, then how about the following for what the MN should do:

	If a MN receives an Link Up trigger in which the FA L2
	address does not match the L2 address of its current FA
	and the MN is capable of deferring L3 handover based
	on traffic and movement patterns, the MN SHOULD use
	this capability to optimize the timing of L3 handover
	so as not to impact ongoing traffic. If the MN is incapable
	of deferring L3 handover, the MN MUST issue a SolRtAdv to
	the new FA to begin the process of L3 handover. 

		jak

>content-class: urn:content-classes:message
>Subject: RE: [mobile-ip] Low Latency Issue: Should HTT be MUST, SHOULD, or MAY?
>Date: Thu, 6 Sep 2001 08:49:59 -0500
>X-MS-Has-Attach: 
>X-MS-TNEF-Correlator: 
>X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0
>Thread-Topic: [mobile-ip] Low Latency Issue: Should HTT be MUST, SHOULD, or 
MAY?
>Thread-Index: AcE2zFCzQb+4I6K8EdWpVgBQi2kYTQADpp/A
>From: "Patil Basavaraj (NET/Dallas)" <Basavaraj.Patil@nokia.com>
>To: <mobile-ip@sunroof.eng.sun.com>
>X-OriginalArrivalTime: 06 Sep 2001 13:49:59.0528 (UTC) 
FILETIME=[D1E4AE80:01C136DA]
>X-MIME-Autoconverted: from quoted-printable to 8bit by sunroof.eng.sun.com id 
f86DnpIQ024095
>
>>> or to issue a RtSol (if RFC2002bis handoff is
>>> happening)? If network initiated handoff is happening, how will
>>> the mobile node know not to perform a registration when it receives
>>> the Link Up L2 trigger on the new FA?
>>> 
>>> I'd like to suggest that we add a bit to the Agent Advertisement:
>>> 
>>>   S - Mobile node can suppress movement detection and handoff at L3
>if
>>>       desired. FAs will make sure the mobile node's packets are
>properly
>>>       routed until a registration for a new care of address is made.
>>> 
>>	=> I thought that the whole point was to run vanilla MIP in the
>MN ?
>>	Why do we want to inform the MN about BETH or any handover
>>	mechanism that does not involve the MN ?
>
>James, I thought one of the advantages of BETH was that since it is a
>network initiated (and Network only) handoff protocol, the MN is not
>involved in the handoff process. So I agree with Hesham that the MN
>does not need indications of what is occuring in the network.
>
>>
>>	Hesham
>>
>
>-Basavaraj
>



From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep  6 16:25:28 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA07845
	for <mobileip-archive@odin.ietf.org>; Thu, 6 Sep 2001 16:25:23 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA23756;
	Thu, 6 Sep 2001 13:26:36 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id NAA14619;
	Thu, 6 Sep 2001 13:26:29 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f86KP2IQ025571
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 6 Sep 2001 13:25:03 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1/Submit) id f86KP2tT025570
	for mobile-ip-dist; Thu, 6 Sep 2001 13:25:02 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from heliopolis.eng.sun.com (bigbang.Eng.Sun.COM [152.70.8.30])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f86KOxIQ025563
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 13:24:59 -0700 (PDT)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.eng.sun.com (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id NAA24927
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 13:25:14 -0700 (PDT)
Message-Id: <200109062025.NAA24927@heliopolis.eng.sun.com>
Date: Thu, 6 Sep 2001 13:25:13 -0700 (PDT)
From: James Kempf <James.Kempf@Sun.COM>
Subject: RE: [mobile-ip] question on BET tear down
To: mobile-ip@sunroof.eng.sun.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: G+kf1V0LNpgZc2fjfxICkw==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Madjid,

>the MN has acquired nCoA, but the tunnel is
>not torn down, since we want to make sure everybody knows about this nCoA,
>in the mean time, traffic might still be going through the tunnel (before it
>is torn down), which means the header compression states are also changing.
>This means as long as the traffic is flowing through the tunnel, I cannot 
>transfer the header compression context from oldAR to newAR.
>
>So I am trying to find out exactly when the traffic stops:
>I guess this is when the tunnel is torn down. But when does tear down
> happen:
>
>1-oldAR receives a BU from MN and sends a tunnel tear down to nAR.

Yes, that is one possibility.

>2-nAR somehow finds out MN is using its newCoA, by monitoring
>MN's traffic.
>Does the  MN suddenly starts using its newCoA, without notifying nAR?
>

Currently, there is nothing in the protocol, nor in FMIPv6, for
the MN to notify newAR when the process of L3 handover, including
routing updates to HA and CNs, completes. If the MN sends a BU to the oldAR,
the newAR gets informed when it gets the HRqst(r) to terminate the
tunnel.

>I thought in FMIP, the MN sends an NA and gets some ack back from nAR.
>Shouldn't that be used as a sure tunnel tear down trigger?
>

MN does send a NA but I believe that happens before sending the BUs and receipt 
of the BAcks from the HA and CNs. If the new AR terminates the tunnel
prior to the MN getting the BAcks, in-flight packets could be lost.

I suppose we could put in a BU to the new AR, but, again, there is
the issue of a security association. Presumably,the new AR
gets it via a context transfer from the old AR, but I don't think
BETH/FMIPv6 can assume this.

Actually, I'm not sure there's an issue here. If the MN has a real
time session going, it can use BETH to delay handover until the
session has stopped. At that point, the header compression state
becomes moot anyway. If it doesn't have a real time session going,
then it can perform L3 handover via the standard FMIPv6 algorithm,
or on the new router, and the compression state can either be
transferred or not. If not, it won't make much difference because
it will get reestablished within 3-4 packets on the new router anyway,
and there is no time critical human waiting for the result.

Am I missing anything here?

		jak



From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep  6 17:01:23 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA09000
	for <mobileip-archive@odin.ietf.org>; Thu, 6 Sep 2001 17:01:23 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id PAA13537;
	Thu, 6 Sep 2001 15:02:32 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id OAA24313;
	Thu, 6 Sep 2001 14:02:28 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f86L1HIQ025664
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 6 Sep 2001 14:01:17 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1/Submit) id f86L1Hxx025663
	for mobile-ip-dist; Thu, 6 Sep 2001 14:01:17 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from heliopolis.eng.sun.com (redhook.Eng.Sun.COM [152.70.24.37])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f86L1DIQ025656
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 14:01:13 -0700 (PDT)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.eng.sun.com (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id OAA26347
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 14:01:29 -0700 (PDT)
Message-Id: <200109062101.OAA26347@heliopolis.eng.sun.com>
Date: Thu, 6 Sep 2001 14:01:28 -0700 (PDT)
From: James Kempf <James.Kempf@Sun.COM>
Subject: RE: [mobile-ip] question on BET tear down
To: mobile-ip@sunroof.eng.sun.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: dxdCJcrK0MtJFUksqXsjWA==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Hesham,

>> Why? If the traffic is encrypted, it would naturally be a problem, but
>> if its not, then it's a possibility. This is not meant to be a 
>> prescription but a way that the AR can optimize tunnel management,
>> more of a hint. Ultimately, the tunnel will time out anyway, these
>> techniques are to help optimize managment.
>> 
>	=> I didn't say it's impossible, I said that router jsimply won't 
>	do it. It's an unnecessary and unrealistic thing to expect. 
>	It adds delays per packet for no reason.
>
>> >	get a BA from CNs. So I'm not sure that having 
>> >	it as an option is useful because it is not a realistic one. 
>> >
>> 

OK.

>> >	Looking for the source address is not accurate either because
>> >	using a new CoA doesn't tell you that the routing is 
>> >	optimised or symmetric. 
>> >
>> 
>> I'm not sure I understand. This is a problem in standard MIP and
>> FMIPv6 as well. The forward tunnel is only needed as long as packets
>> are coming into the oAR with destination address the old CoA. The reverse 
tunnel
>> is only needed as long as packets are coming from the MN
>> with the old CoA as the source address. When that is no longer happening
>> the tunnel can be dropped. 
>> 
>	=> Only in one direction, because packets may stillbe forwarded 
>	from the old AR. 
>

If the nAR notices that packets are no longer being sent from the MN
with the old CoA, it can send a HRqst(r) with lifetime 0 to the old AR.
The old AR can return an HRqst(r) with lifetime nonzero to indicate
that it would like to prolong the forward tunnel, if there are 
still packets coming from CNs with the MN's old CoA. 

Anyway, the definitive indication is for the MN to send a BU to the
old AR, as per FMIPv6, when the BU/BAcks are in, and for old AR
to send the HRqst(r) to new AR with lifetime zero. This technique
is only for when there is no security association between the
MN and the old AR.

		jak



From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep  6 17:17:05 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA09229
	for <mobileip-archive@odin.ietf.org>; Thu, 6 Sep 2001 17:17:04 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id PAA25194;
	Thu, 6 Sep 2001 15:18:12 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id OAA28339;
	Thu, 6 Sep 2001 14:18:08 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f86LGwIQ025720
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 6 Sep 2001 14:16:58 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1/Submit) id f86LGvhw025719
	for mobile-ip-dist; Thu, 6 Sep 2001 14:16:57 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f86LGsIQ025712
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 14:16:54 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id OAA17497
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 14:17:09 -0700 (PDT)
Received: from albatross-ext.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id PAA24626
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 15:17:43 -0600 (MDT)
Received: from esealnt461 (esealnt461.al.sw.ericsson.se [153.88.251.61])
	by albatross.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id f86LH6K04064
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 23:17:06 +0200 (MEST)
Received: FROM esealnt742.al.sw.ericsson.se BY esealnt461 ; Thu Sep 06 23:16:58 2001 +0200
Received: by esealnt742.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <NBWN4MPF>; Thu, 6 Sep 2001 23:10:13 +0200
Message-ID: <034BEFD03799D411A59F00508BDF754603008C82@esealnt448.al.sw.ericsson.se>
From: "Hesham Soliman  (ERA)" <Hesham.Soliman@era.ericsson.se>
To: "'mobile-ip@sunroof.eng.sun.com'" <mobile-ip@sunroof.eng.sun.com>
Subject: RE: [mobile-ip] question on BET tear down
Date: Thu, 6 Sep 2001 23:16:55 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

> >> 
> >	=> Only in one direction, because packets may stillbe forwarded 
> >	from the old AR. 
> >
> 
> If the nAR notices that packets are no longer being sent from the MN
> with the old CoA, it can send a HRqst(r) with lifetime 0 to the old AR.
> The old AR can return an HRqst(r) with lifetime nonzero to indicate
> that it would like to prolong the forward tunnel, if there are 
> still packets coming from CNs with the MN's old CoA. 
> 
	=> hmm, starting to look a bit messy though.

> Anyway, the definitive indication is for the MN to send a BU to the
> old AR, as per FMIPv6, when the BU/BAcks are in, and for old AR
> to send the HRqst(r) to new AR with lifetime zero. This technique
> is only for when there is no security association between the
> MN and the old AR.
> 
	=> I'm not sure that relying on the BU to the oAR is a good
	idea. In some cases there can be one BU sent if the HA is close
	(local) or a MAP...etc.
	I don't have an answer though as to how the tunnel should be torn.

	Hesham


From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep  6 17:24:53 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA09373
	for <mobileip-archive@odin.ietf.org>; Thu, 6 Sep 2001 17:24:53 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id OAA20339;
	Thu, 6 Sep 2001 14:26:03 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id OAA00670;
	Thu, 6 Sep 2001 14:25:50 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f86LOoIQ025770
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 6 Sep 2001 14:24:50 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1/Submit) id f86LOnVB025769
	for mobile-ip-dist; Thu, 6 Sep 2001 14:24:49 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from heliopolis.eng.sun.com (redcoast.Eng.Sun.COM [152.70.28.21])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f86LOkIQ025762
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 14:24:46 -0700 (PDT)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.eng.sun.com (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id OAA28619
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 14:25:02 -0700 (PDT)
Message-Id: <200109062125.OAA28619@heliopolis.eng.sun.com>
Date: Thu, 6 Sep 2001 14:25:01 -0700 (PDT)
From: James Kempf <James.Kempf@Sun.COM>
Subject: RE: [mobile-ip] question on BET tear down
To: mobile-ip@sunroof.eng.sun.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: LNLWLkeTbJbxwoctp76RtA==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

>> >> 
>> >	=> Only in one direction, because packets may stillbe forwarded 
>> >	from the old AR. 
>> >
>> 
>> If the nAR notices that packets are no longer being sent from the MN
>> with the old CoA, it can send a HRqst(r) with lifetime 0 to the old AR.
>> The old AR can return an HRqst(r) with lifetime nonzero to indicate
>> that it would like to prolong the forward tunnel, if there are 
>> still packets coming from CNs with the MN's old CoA. 
>> 
>	=> hmm, starting to look a bit messy though.
>

But doable. :-)

>> Anyway, the definitive indication is for the MN to send a BU to the
>> old AR, as per FMIPv6, when the BU/BAcks are in, and for old AR
>> to send the HRqst(r) to new AR with lifetime zero. This technique
>> is only for when there is no security association between the
>> MN and the old AR.
>> 
>	=> I'm not sure that relying on the BU to the oAR is a good
>	idea. In some cases there can be one BU sent if the HA is close
>	(local) or a MAP...etc.
>	I don't have an answer though as to how the tunnel should be torn.
>

What solution did the original FMIPv6 design team envision for this? 
The original design also had a forward tunnel to the new AR, though not the 
reverse tunnel, possibly for bicasting. I thought that the original
idea was to send the BU to the old AR  after the MN had completed
everyting for new CoA establishment. 

We could write the spec to discourage using a tunnel lifetime of
0xffff, which is good till cancelled, unless the ARs have some
means of definitively telling that the MN has completed L3 handover,
such as the BU or maybe the HRqst(r)/HRply(r) exchange. That way,
the tunnel will time out eventually if not renewed.

		jak 



From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep  6 18:30:26 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA10391
	for <mobileip-archive@odin.ietf.org>; Thu, 6 Sep 2001 18:30:26 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id QAA18263;
	Thu, 6 Sep 2001 16:31:30 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id PAA12781;
	Thu, 6 Sep 2001 15:31:18 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f86MT8IQ025862
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 6 Sep 2001 15:29:08 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1/Submit) id f86MT8uv025861
	for mobile-ip-dist; Thu, 6 Sep 2001 15:29:08 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f86MT4IQ025854
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 15:29:04 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id PAA05790
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 15:29:13 -0700 (PDT)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id QAA16521
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 16:29:00 -0600 (MDT)
Received: from esealnt409.al.sw.ericsson.se (ESEALNT409.al.sw.ericsson.se [153.88.251.32])
	by penguin.wise.edt.ericsson.se (8.11.0/8.10.1/WIREfire-1.3) with SMTP id f86MT1v04702
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 7 Sep 2001 00:29:02 +0200 (MEST)
Received: FROM esealnt742.al.sw.ericsson.se BY esealnt409.al.sw.ericsson.se ; Fri Sep 07 00:28:55 2001 +0200
Received: by esealnt742.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <NBWN4NBT>; Fri, 7 Sep 2001 00:22:09 +0200
Message-ID: <034BEFD03799D411A59F00508BDF754603008C83@esealnt448.al.sw.ericsson.se>
From: "Hesham Soliman  (ERA)" <Hesham.Soliman@era.ericsson.se>
To: "'mobile-ip@sunroof.eng.sun.com'" <mobile-ip@sunroof.eng.sun.com>
Subject: RE: [mobile-ip] question on BET tear down
Date: Fri, 7 Sep 2001 00:28:53 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

> >> >	=> Only in one direction, because packets may stillbe forwarded 
> >> >	from the old AR. 
> >> >
> >> 
> >> If the nAR notices that packets are no longer being sent from the MN
> >> with the old CoA, it can send a HRqst(r) with lifetime 0 to the old AR.
> >> The old AR can return an HRqst(r) with lifetime nonzero to indicate
> >> that it would like to prolong the forward tunnel, if there are 
> >> still packets coming from CNs with the MN's old CoA. 
> >> 
> >	=> hmm, starting to look a bit messy though.
> >
> 
> But doable. :-)
> 
	=> Yes, and I can make it to Mars one day :)
	No seriously, this is like a NAT handling UDP connections, the same 
	problems apply, except in this case we want a much higher 
	certainty about the timers. 

> >> Anyway, the definitive indication is for the MN to send a BU to the
> >> old AR, as per FMIPv6, when the BU/BAcks are in, and for old AR
> >> to send the HRqst(r) to new AR with lifetime zero. This technique
> >> is only for when there is no security association between the
> >> MN and the old AR.
> >> 
> >	=> I'm not sure that relying on the BU to the oAR is a good
> >	idea. In some cases there can be one BU sent if the HA is close
> >	(local) or a MAP...etc.
> >	I don't have an answer though as to how the tunnel should be torn.
> >
> 
> What solution did the original FMIPv6 design team envision for this? 
> The original design also had a forward tunnel to the new AR, though not the 
> reverse tunnel, possibly for bicasting. I thought that the original
> idea was to send the BU to the old AR  after the MN had completed
> everyting for new CoA establishment. 
> 
	=> The original design had a tunnel to the nAR but only as an
	error case if the address was not useable. The possibility 
	of that happening is minimal. However, if it did happen the 
	problem would have been the same. I didn't get any 
	concrete answers back then either but because it was 
	an error case it wasn't urgent. Bicasting was not an issue 
	for this case, the tunnel end point would have been the MN. 

	For bicasting we were focused on the BU based bicasting.

> We could write the spec to discourage using a tunnel lifetime of
> 0xffff, which is good till cancelled, unless the ARs have some
> means of definitively telling that the MN has completed L3 handover,
> 
	=> "some means" above is the problem. 

> such as the BU or maybe the HRqst(r)/HRply(r) exchange. That way,
> the tunnel will time out eventually if not renewed.
> 
	=> it's a tradeoff between keeping unnecessary state and making 
	sure no packets are dropped. I suspect the exact numbers will depend
	on the system calculations but the draft should highlight the 
	issues and put some guidelines with a safety factor. 

	Hesham


From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep  6 18:37:54 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA10501
	for <mobileip-archive@odin.ietf.org>; Thu, 6 Sep 2001 18:37:54 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id PAA20703;
	Thu, 6 Sep 2001 15:39:08 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id PAA05982;
	Thu, 6 Sep 2001 15:38:56 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f86MavIQ025944
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 6 Sep 2001 15:36:57 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1/Submit) id f86MavxV025943
	for mobile-ip-dist; Thu, 6 Sep 2001 15:36:57 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from heliopolis.eng.sun.com (bigbang.Eng.Sun.COM [152.70.8.30])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f86MarIQ025936
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 15:36:53 -0700 (PDT)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.eng.sun.com (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id PAA01980
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 15:37:01 -0700 (PDT)
Message-Id: <200109062237.PAA01980@heliopolis.eng.sun.com>
Date: Thu, 6 Sep 2001 15:37:00 -0700 (PDT)
From: James Kempf <James.Kempf@Sun.COM>
Subject: RE: [mobile-ip] question on BET tear down
To: mobile-ip@sunroof.eng.sun.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: sAJOHqpbP8HyWLEw+3mYGA==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Hesham,

>	=> it's a tradeoff between keeping unnecessary state and making 
>	sure no packets are dropped. I suspect the exact numbers will depend
>	on the system calculations but the draft should highlight the 
>	issues and put some guidelines with a safety factor. 
>

OK, I'll write the spec with this in mind. Thanx for the input.

		jak



From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep  6 18:39:49 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA10547
	for <mobileip-archive@odin.ietf.org>; Thu, 6 Sep 2001 18:39:48 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id PAA21476;
	Thu, 6 Sep 2001 15:41:02 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id PAA06581;
	Thu, 6 Sep 2001 15:40:50 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f86MdTIQ025977
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 6 Sep 2001 15:39:29 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1/Submit) id f86MdTc0025976
	for mobile-ip-dist; Thu, 6 Sep 2001 15:39:29 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f86MdPIQ025969
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 15:39:25 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id PAA14426
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 15:39:28 -0700 (PDT)
Received: from zrc2s03g.us.nortel.com (zrc2s03g.nortelnetworks.com [47.103.122.66])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id PAA18332
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 15:39:28 -0700 (PDT)
Received: from smtprch2.nortel.com (erchg0k.us.nortel.com [47.113.64.104])
	by zrc2s03g.us.nortel.com (8.9.3+Sun/8.9.1) with ESMTP id RAA04489
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 17:39:22 -0500 (CDT)
Received: from zrchb200.us.nortel.com by smtprch2.nortel.com;
          Thu, 6 Sep 2001 17:32:35 -0500
Received: by zrchb200.us.nortel.com with Internet Mail Service (5.5.2653.19) 
          id <SK3L2H38>; Thu, 6 Sep 2001 17:38:51 -0500
Message-ID: <52F74DDA50B5D211AF800000F808252108C068A2@zrchb212.us.nortel.com>
From: "Kuntal Chowdhury" <chowdury@nortelnetworks.com>
To: mobile-ip@sunroof.eng.sun.com
Subject: RE: [mobile-ip] RFC2002bis
Date: Thu, 6 Sep 2001 17:38:51 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01C13724.B3BB9550"
X-Orig: <chowdury@americasm01.nt.com>
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

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

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

Hi all,
3GPP2 cannot use any reference to RFC 2002bis before it reaches RFC status.
Moreover cdma2000 packet data standards i.e. IS-835, IS-835-A refer to RFC
2002. Even the IS-835-B which is scheduled to be released sometime late this
year, will use RFC 2002 reference. All the cdma2000 deployments in the near
future will be based on MIP as defined in RFC 2002. Now, obsoleting RFC 2002
with an incompatible version would basically make cdma2000 networks
incompatible with all other MIP implementations. This seems like a huge
problem for 3G wireless carriers who plan to deploy MIP.

Regards,
Kuntal


-----Original Message-----
From: Patil Basavaraj (NET/Dallas) [mailto:Basavaraj.Patil@nokia.com]
Sent: Thursday, September 06, 2001 6:56 AM
To: mobile-ip
Cc: Perkins Charles (IPRG/MtView); Madjid.Nakhjiri
Subject: RE: [mobile-ip] RFC2002bis


rfc2002bis is an I-D and NOT an RFC yet. Outside SDOs can
choose whether they want to reference an I-D, which is essentially
work in progress and has the possibility of change occuring or wait
for it to become a PS with a new RFC number. 
I think you are still on the greens in your understanding of the
status of the 2002bis I-D.

> -----Original Message-----
> From: ext Nakhjiri Madjid-MNAKHJI1 
> 
> There might be a procedure about the bis version that I don't 
> understand.
> Can Charlie or the chairs answer this question?
> 
> Can an outside SDO refer to a bis RFC? i.e. does it have same
> standard status as the non-bis RFC?
> I was under impression that the RFC2002bis has ID status,
> maybe I am way off in the woods???
> 
> Thanks in advance,
> Madjid
> 
> -----Original Message-----
> From: Marcello Lioy [mailto:lioy@qualcomm.com]
> 
> 
> At 02:00 8/11/2001, you wrote:
> >Hello folks,
> >
> >A new version of RFC2002bis has been prepared.  According
> >to the most recent guidance given by the IESG, a change in
> >the mandated authentication algorithm has been strongly
> >suggested.  Unfortunately, this will have the effect of
> >causing almost all previous implementations of Mobile IP
> >for IPv4 to become incompatible with the new specification.
> >
> >The working group chairs recently asked the working group,
> >by way of the mailing list, whether this incompatible
> >change would be acceptable.  The discussion was quite
> >limited, somewhat to my surprise.  This has been taken
> >as evidence that going with HMAC_MD5 is more-or-less
> >O.K.  Thus, it has been decided to go ahead with the
> >change.  On the other hand, it is conceivable that not
> >all interested parties have been notified of the possible
> >change, or have had time to reply.  If there are dissenters
> >to this change, now would be the time to express that
> >opinion.
> 
> This could be an issue.  TIA/EIA IS-835 (the packet data standard for 
> CDMA2000) is going to be deployed in North America this fall. 
>  It specifies 
> the user of RFC 2002.  There are two major areas of 
> incompatibilty in RFC 
> 2002bis:
> 1) the inclusion of the SPI in the auth calculation
> 2) HMAC_MD5 if that is decided on.
> 
> Both of these things break 2002 - which means that the mobiles and 
> infrastructure that are 835 compliant will be obsoleted when 
> RFC 2002 is 
> obsoleted.
> 
> I think that both of these fixes are good (the SPI was a bug 
> that slipped 
> through in 2002, and HMAC sounds like it is less vulnerable 
> than vanila 
> MD5) but they could cause issues in these planned network deployments.
> -----------------------------------
> Marcello (Wandering through France)
> 

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.89">
<TITLE>RE: [mobile-ip] RFC2002bis</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Hi all,</FONT>
<BR><FONT SIZE=3D2>3GPP2 cannot use any reference to RFC 2002bis before =
it reaches RFC status. Moreover cdma2000 packet data standards i.e. =
IS-835, IS-835-A refer to RFC 2002. Even the IS-835-B which is =
scheduled to be released sometime late this year, will use RFC 2002 =
reference. All the cdma2000 deployments in the near future will be =
based on MIP as defined in RFC 2002. Now, obsoleting RFC 2002 with an =
incompatible version would basically make cdma2000 networks =
incompatible with all other MIP implementations. This seems like a huge =
problem for 3G wireless carriers who plan to deploy MIP.</FONT></P>

<P><FONT SIZE=3D2>Regards,</FONT>
<BR><FONT SIZE=3D2>Kuntal</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Patil Basavaraj (NET/Dallas) [<A =
HREF=3D"mailto:Basavaraj.Patil@nokia.com">mailto:Basavaraj.Patil@nokia.c=
om</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Thursday, September 06, 2001 6:56 AM</FONT>
<BR><FONT SIZE=3D2>To: mobile-ip</FONT>
<BR><FONT SIZE=3D2>Cc: Perkins Charles (IPRG/MtView); =
Madjid.Nakhjiri</FONT>
<BR><FONT SIZE=3D2>Subject: RE: [mobile-ip] RFC2002bis</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>rfc2002bis is an I-D and NOT an RFC yet. Outside SDOs =
can</FONT>
<BR><FONT SIZE=3D2>choose whether they want to reference an I-D, which =
is essentially</FONT>
<BR><FONT SIZE=3D2>work in progress and has the possibility of change =
occuring or wait</FONT>
<BR><FONT SIZE=3D2>for it to become a PS with a new RFC number. </FONT>
<BR><FONT SIZE=3D2>I think you are still on the greens in your =
understanding of the</FONT>
<BR><FONT SIZE=3D2>status of the 2002bis I-D.</FONT>
</P>

<P><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: ext Nakhjiri Madjid-MNAKHJI1 </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; There might be a procedure about the bis =
version that I don't </FONT>
<BR><FONT SIZE=3D2>&gt; understand.</FONT>
<BR><FONT SIZE=3D2>&gt; Can Charlie or the chairs answer this =
question?</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Can an outside SDO refer to a bis RFC? i.e. =
does it have same</FONT>
<BR><FONT SIZE=3D2>&gt; standard status as the non-bis RFC?</FONT>
<BR><FONT SIZE=3D2>&gt; I was under impression that the RFC2002bis has =
ID status,</FONT>
<BR><FONT SIZE=3D2>&gt; maybe I am way off in the woods???</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Thanks in advance,</FONT>
<BR><FONT SIZE=3D2>&gt; Madjid</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Marcello Lioy [<A =
HREF=3D"mailto:lioy@qualcomm.com">mailto:lioy@qualcomm.com</A>]</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; At 02:00 8/11/2001, you wrote:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;Hello folks,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;A new version of RFC2002bis has been =
prepared.&nbsp; According</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;to the most recent guidance given by the =
IESG, a change in</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;the mandated authentication algorithm has =
been strongly</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;suggested.&nbsp; Unfortunately, this will =
have the effect of</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;causing almost all previous implementations =
of Mobile IP</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;for IPv4 to become incompatible with the =
new specification.</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;The working group chairs recently asked the =
working group,</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;by way of the mailing list, whether this =
incompatible</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;change would be acceptable.&nbsp; The =
discussion was quite</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;limited, somewhat to my surprise.&nbsp; =
This has been taken</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;as evidence that going with HMAC_MD5 is =
more-or-less</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;O.K.&nbsp; Thus, it has been decided to go =
ahead with the</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;change.&nbsp; On the other hand, it is =
conceivable that not</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;all interested parties have been notified =
of the possible</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;change, or have had time to reply.&nbsp; If =
there are dissenters</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;to this change, now would be the time to =
express that</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;opinion.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; This could be an issue.&nbsp; TIA/EIA IS-835 =
(the packet data standard for </FONT>
<BR><FONT SIZE=3D2>&gt; CDMA2000) is going to be deployed in North =
America this fall. </FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp; It specifies </FONT>
<BR><FONT SIZE=3D2>&gt; the user of RFC 2002.&nbsp; There are two major =
areas of </FONT>
<BR><FONT SIZE=3D2>&gt; incompatibilty in RFC </FONT>
<BR><FONT SIZE=3D2>&gt; 2002bis:</FONT>
<BR><FONT SIZE=3D2>&gt; 1) the inclusion of the SPI in the auth =
calculation</FONT>
<BR><FONT SIZE=3D2>&gt; 2) HMAC_MD5 if that is decided on.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Both of these things break 2002 - which means =
that the mobiles and </FONT>
<BR><FONT SIZE=3D2>&gt; infrastructure that are 835 compliant will be =
obsoleted when </FONT>
<BR><FONT SIZE=3D2>&gt; RFC 2002 is </FONT>
<BR><FONT SIZE=3D2>&gt; obsoleted.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; I think that both of these fixes are good (the =
SPI was a bug </FONT>
<BR><FONT SIZE=3D2>&gt; that slipped </FONT>
<BR><FONT SIZE=3D2>&gt; through in 2002, and HMAC sounds like it is =
less vulnerable </FONT>
<BR><FONT SIZE=3D2>&gt; than vanila </FONT>
<BR><FONT SIZE=3D2>&gt; MD5) but they could cause issues in these =
planned network deployments.</FONT>
<BR><FONT SIZE=3D2>&gt; -----------------------------------</FONT>
<BR><FONT SIZE=3D2>&gt; Marcello (Wandering through France)</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C13724.B3BB9550--


From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep  6 19:21:01 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA11676
	for <mobileip-archive@odin.ietf.org>; Thu, 6 Sep 2001 19:21:00 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id RAA20505;
	Thu, 6 Sep 2001 17:22:10 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id QAA15991;
	Thu, 6 Sep 2001 16:22:00 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f86NKTIQ026176
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 6 Sep 2001 16:20:29 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1/Submit) id f86NKTJM026175
	for mobile-ip-dist; Thu, 6 Sep 2001 16:20:29 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from jurassic.eng.sun.com (jurassic [129.146.87.130] (may be forged))
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f86NKPIQ026168
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 16:20:25 -0700 (PDT)
Received: from istanbul.Eng.Sun.COM (istanbul.Eng.Sun.COM [129.146.86.247])
	by jurassic.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with SMTP id f86NKd41663727;
	Thu, 6 Sep 2001 16:20:39 -0700 (PDT)
Message-Id: <200109062320.f86NKd41663727@jurassic.eng.sun.com>
Date: Thu, 6 Sep 2001 16:20:39 -0700 (PDT)
From: Alper Yegin <Alper.Yegin@eng.sun.com>
Subject: Re: [mobile-ip] Coexistence with other uses for routing header 
To: mobile-ip@sunroof.eng.sun.com, Francis.Dupont@enst-bretagne.fr
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: K+d6Vvr1ANTbvh17vApBqg==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4_37 SunOS 5.8.1 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

>  In your previous mail you wrote:
> 
>    For the purposes of what to put into the revised specification,
>    I think the main result of the recent discussion would be that
>    the mobile node's home address does not have to be the last stop
>    along the source route indicated in a routing header.  This part
>    of the revision should not be the deciding factor in any
>    specification about mobile routers or further route optimization,
>    and so I have reformulated the paragraph as follows:
>    
>         It is possible that a correspondent node, having no knowledge of the
>         mobile node's care-of address, would still (for reasons unspecified
>         here but not necessarily related to mobility) attempt to deliver a 
>         packet, either to or by way of the mobile node's home address,
>         by using a routing header.  If the correspondent node subsequently
>         accepts a Binding Update and creates a Binding Cache entry for the
>         mobile node, then afterwards, the routing header used by the
>         corresponding node which includes the mobile node's home address
>         SHOULD also include the mobile node's care-of address.
>         The correspondent node SHOULD put the mobile node's care-of address
>         as the intermediate node address immediately preceding the
>         mobile node's home address.  When the care-of address is the
>         first intermediate node address, this implies that the care-of
>         address is to be placed in the Destination Address of the IPv6
>         headerd, and the mobile node's home address is the first entry
>         in the type 0 routing header.  Otherwise, the correspondent 
>         node MUST place the mobile node's home address immediately 
>         after the care-of address entry of the routing header, following
>         all other intermediate node addresses that would have
>         already been in the routing header before the creation
>         of the Binding Cache entry for the care-of address.
>    
>    I hope this is better.
>    
> => yes but you should add something about the possible reversing
> of this by the receiver. This issue is easy to solve if it is MN
> but difficult if it is not. Has someone a simple proposal?

Francis,

I don't have a proposal, but just an observation: this just effects the reverse 
traffic not being route optimized (which is the case if this above method is not 
used anyways). And yes, mobile node can be smart about dealing with reversing 
routing headers...

alper



From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep  6 20:18:46 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA12691
	for <mobileip-archive@odin.ietf.org>; Thu, 6 Sep 2001 20:18:45 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id SAA21256;
	Thu, 6 Sep 2001 18:19:55 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id RAA03986;
	Thu, 6 Sep 2001 17:19:47 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f870IVIQ026271
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 6 Sep 2001 17:18:31 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1/Submit) id f870IVXS026270
	for mobile-ip-dist; Thu, 6 Sep 2001 17:18:31 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f870IRIQ026263
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 17:18:27 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id RAA27989
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 17:18:36 -0700 (PDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id RAA01921
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 6 Sep 2001 17:18:35 -0700 (PDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id RAA06070;
	Thu, 6 Sep 2001 17:18:35 -0700 (PDT)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f870IYV32498;
	Thu, 6 Sep 2001 17:18:34 -0700
X-mProtect:  Thu, 6 Sep 2001 17:18:34 -0700 Nokia Silicon Valley Messaging Protection
Received: from Icharliep-1.iprg.nokia.com (205.226.22.18, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpdDQZ3L0; Thu, 06 Sep 2001 17:18:31 PDT
Message-ID: <3B981267.DCEEE8F4@iprg.nokia.com>
Date: Thu, 06 Sep 2001 17:18:47 -0700
From: Charlie Perkins <charliep@iprg.nokia.com>
Organization: Nokia
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: chowdury@nortelnetworks.com, Madjid.Nakhjiri@motorola.com
CC: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] RFC2002bis
References: <52F74DDA50B5D211AF800000F808252108C068A2@zrchb212.us.nortel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hello,

As far as I can tell, RFC2002bis was completed until this recent
request to merge in MIER, and that is not hard to do.  In fact,
I'm already just about finished with a draft revision containing
MIER, the text of which wouldn't surprise anyone who cared.

If you wanna build RFC2002bis systems, I would say to go ahead
and build them.  There aren't any outstanding issues that would
endanger its progress at this point.

Regards,
Charlie P.


Kuntal Chowdhury wrote:

>
>
> Hi all,
> 3GPP2 cannot use any reference to RFC 2002bis before it reaches RFC
> status. Moreover cdma2000 packet data standards i.e. IS-835, IS-835-A
> refer to RFC 2002. Even the IS-835-B which is scheduled to be released
> sometime late this year, will use RFC 2002 reference. All the cdma2000
> deployments in the near future will be based on MIP as defined in RFC
> 2002. Now, obsoleting RFC 2002 with an incompatible version would
> basically make cdma2000 networks incompatible with all other MIP
> implementations. This seems like a huge problem for 3G wireless
> carriers who plan to deploy MIP.
>
> Regards,
> Kuntal
>
> -----Original Message-----
> From: Patil Basavaraj (NET/Dallas) [mailto:Basavaraj.Patil@nokia.com]
> Sent: Thursday, September 06, 2001 6:56 AM
> To: mobile-ip
> Cc: Perkins Charles (IPRG/MtView); Madjid.Nakhjiri
> Subject: RE: [mobile-ip] RFC2002bis
>
> rfc2002bis is an I-D and NOT an RFC yet. Outside SDOs can
> choose whether they want to reference an I-D, which is essentially
> work in progress and has the possibility of change occuring or wait
> for it to become a PS with a new RFC number.
> I think you are still on the greens in your understanding of the
> status of the 2002bis I-D.
>
> > -----Original Message-----
> > From: ext Nakhjiri Madjid-MNAKHJI1
> >
> > There might be a procedure about the bis version that I don't
> > understand.
> > Can Charlie or the chairs answer this question?
> >
> > Can an outside SDO refer to a bis RFC? i.e. does it have same
> > standard status as the non-bis RFC?
> > I was under impression that the RFC2002bis has ID status,
> > maybe I am way off in the woods???
> >
> > Thanks in advance,
> > Madjid
> >
> > -----Original Message-----
> > From: Marcello Lioy [mailto:lioy@qualcomm.com]
> >
> >
> > At 02:00 8/11/2001, you wrote:
> > >Hello folks,
> > >
> > >A new version of RFC2002bis has been prepared.  According
> > >to the most recent guidance given by the IESG, a change in
> > >the mandated authentication algorithm has been strongly
> > >suggested.  Unfortunately, this will have the effect of
> > >causing almost all previous implementations of Mobile IP
> > >for IPv4 to become incompatible with the new specification.
> > >
> > >The working group chairs recently asked the working group,
> > >by way of the mailing list, whether this incompatible
> > >change would be acceptable.  The discussion was quite
> > >limited, somewhat to my surprise.  This has been taken
> > >as evidence that going with HMAC_MD5 is more-or-less
> > >O.K.  Thus, it has been decided to go ahead with the
> > >change.  On the other hand, it is conceivable that not
> > >all interested parties have been notified of the possible
> > >change, or have had time to reply.  If there are dissenters
> > >to this change, now would be the time to express that
> > >opinion.
> >
> > This could be an issue.  TIA/EIA IS-835 (the packet data standard
> for
> > CDMA2000) is going to be deployed in North America this fall.
> >  It specifies
> > the user of RFC 2002.  There are two major areas of
> > incompatibilty in RFC
> > 2002bis:
> > 1) the inclusion of the SPI in the auth calculation
> > 2) HMAC_MD5 if that is decided on.
> >
> > Both of these things break 2002 - which means that the mobiles and
> > infrastructure that are 835 compliant will be obsoleted when
> > RFC 2002 is
> > obsoleted.
> >
> > I think that both of these fixes are good (the SPI was a bug
> > that slipped
> > through in 2002, and HMAC sounds like it is less vulnerable
> > than vanila
> > MD5) but they could cause issues in these planned network
> deployments.
> > -----------------------------------
> > Marcello (Wandering through France)
> >



From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep  7 04:16:00 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA04076
	for <mobileip-archive@lists.ietf.org>; Fri, 7 Sep 2001 04:16:00 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id BAA28722;
	Fri, 7 Sep 2001 01:17:08 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id BAA21366;
	Fri, 7 Sep 2001 01:16:54 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f878F5IQ026936
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 7 Sep 2001 01:15:05 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1/Submit) id f878F5SP026935
	for mobile-ip-dist; Fri, 7 Sep 2001 01:15:05 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from bebop.France.Sun.COM (bebop.France.Sun.COM [129.157.174.15])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f878F0IQ026928
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 7 Sep 2001 01:15:01 -0700 (PDT)
Received: from lillen (lillen [129.157.212.23])
	by bebop.France.Sun.COM (8.10.2+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id f878F9N27661;
	Fri, 7 Sep 2001 10:15:09 +0200 (MET DST)
Date: Fri, 7 Sep 2001 10:11:22 +0200 (CEST)
From: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Subject: Re: [mobile-ip] Mobile Routers support without optimization
To: Mattias Pettersson <mattias.pettersson@era.ericsson.se>
Cc: Erik Nordmark <Erik.Nordmark@eng.sun.com>, mobile-ip@sunroof.eng.sun.com
Message-ID: <Roam.SIMC.2.0.6.999850282.20800.nordmark@bebop.france>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

[Catching up on old mail ...]

> Regarding your first proposal to have MR adjacent to all routers on the
> home link when it is home, and then make it reachable behind the HA when
> not at home: how fast can routing protocols reflect this change? If the
> other routers are not updated quickly when the MR moves away, they will
> keep sending packets to MR's link-local address (according to routing
> protocol). The HA has sent proxy NA for MR's link-local address, and the
> packets will end up at the HA, which will tunnel them to the MR. This
> way will work.

Apart from the fact that the MIPv6 spec says that the link local
packets will not be forwarded over the tunnel.

On the convergece time, I think most IGPs can be tuned to detect routers
coming and going in a second or less.

But I suspect that it causes unnecessary churn to have the MR be adjancent
to a set of routers while at home and a different set of
routers while away from home (the different set being just the HAs).
So it is presumably simpler to have the MR always be only adjancent to
two or more (for redundancy) HAs on its home link and use BUs to
merely update the CoA associated with the tunnels between the HAs and the MR.

Effectively this is what you get if you declare the the MR's home link
is a virtual link.


> Either, synchronize the BUs with the routing protocol updates, or use a
> tunnel to the HA, also when the MR is at home.

I agree on the latter.

> > > Maybe Mobile IPv6 should be changed to tunnel *all* packets.
> > 
> > But that means that the MN will see e.g. all mulicast ND packets which might
> > not be that good use of bandwidth. From an architectural perspective this
> > would make the HA an L2 bridge instead of a L3 router.
> > If there are different links the thing that connects them is a router
> > and link-locals don't cross between links.
> > 
> 
> Ok.
> 
> Or maybe ND packets can be filtered out.

Don't mess with the transparency of the network please ...
Filtering packets based on the content of the packets is acceptable
to implement security policies and the like, but we shouldn't have to
hard-code this in order to make the network work.

   Erik



From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep  7 05:29:38 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA04871
	for <mobileip-archive@odin.ietf.org>; Fri, 7 Sep 2001 05:29:37 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id DAA06363;
	Fri, 7 Sep 2001 03:30:45 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id CAA07550;
	Fri, 7 Sep 2001 02:30:42 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f879TYIQ027042
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 7 Sep 2001 02:29:34 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1/Submit) id f879TX9D027041
	for mobile-ip-dist; Fri, 7 Sep 2001 02:29:33 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f879TUIQ027034
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 7 Sep 2001 02:29:30 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id CAA04182
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 7 Sep 2001 02:29:45 -0700 (PDT)
Received: from iproxy1.ericsson.dk (iproxy1.ericsson.dk [130.228.248.98])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id CAA16856
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 7 Sep 2001 02:29:44 -0700 (PDT)
Received: from unixmail.ted.dk.eu.ericsson.se (knud.ted.dk.eu.ericsson.se [192.66.4.246])
	by iproxy1.ericsson.dk (8.10.1/8.10.1) with ESMTP id f879Tgc03192;
	Fri, 7 Sep 2001 11:29:42 +0200 (MET DST)
Received: from ted.ericsson.dk (petg.ted.dk.eu.ericsson.se [192.66.4.85])
	by unixmail.ted.dk.eu.ericsson.se (8.10.1/8.10.1/TEDmain-1.0) with ESMTP id f879TaL19444;
	Fri, 7 Sep 2001 11:29:37 +0200 (MEST)
Message-ID: <3B989380.F7266A42@ted.ericsson.dk>
Date: Fri, 07 Sep 2001 11:29:36 +0200
From: "Peter Grimstrup (TED)" <peter.grimstrup@ted.ericsson.dk>
Organization: Ericsson Telebit A/S
X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.14-5.0 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: charliep@iprg.nokia.com, mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Coexistence with other uses for routing header
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Charlie wrote:
>    It is possible that a correspondent node, having no knowledge of the
>    mobile node's care-of address, would still (for reasons unspecified
>    here but not necessarily related to mobility) attempt to deliver a 
>    packet, either to or by way of the mobile node's home address,
>    by using a routing header.  If the correspondent node subsequently
>    accepts a Binding Update and creates a Binding Cache entry for the
>    mobile node, then afterwards, the routing header used by the
>    corresponding node which includes the mobile node's home address
>    SHOULD also include the mobile node's care-of address.
>    The correspondent node SHOULD put the mobile node's care-of address
>    as the intermediate node address immediately preceding the
>    mobile node's home address.  When the care-of address is the
>    first intermediate node address, this implies that the care-of
>    address is to be placed in the Destination Address of the IPv6
>    headerd, and the mobile node's home address is the first entry
>    in the type 0 routing header.  Otherwise, the correspondent 
>    node MUST place the mobile node's home address immediately 
>    after the care-of address entry of the routing header, following
>    all other intermediate node addresses that would have
>    already been in the routing header before the creation
>    of the Binding Cache entry for the care-of address.

I don't understand the last part, i.e. "... following all other ..." 

Suggest replacing with
    ...
    in the type 0 routing header.  Otherwise, the correspondent 
    node MUST insert the mobile node's care-of address immediately 
    before the home address entry in the routing header.

An example:

Packets like these are sent:

IPv6 Hdr:      source
               intermediate-dest-1
RH(3 entries): intermediate-dest-2
               intermediate-dest-3
               destination

Then a BU(intermediate-dest3=HoA-3, CoA-3) is accepted and the next packets
should be:

IPv6 Hdr:      source
               intermediate-dest-1
RH(4 entries): intermediate-dest-2
               CoA-3
               intermediate-dest-3
               destination

Further I suggest changing section "8.9 Sending Packets to a Mobile Node"
in a way that the next example will be described/allowed:

IPv6 Hdr:      source
               intermediate-dest-1
RH(4 entries): intermediate-dest-2
               CoA
               MN-HoA

Peter


From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep  7 06:52:08 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA05931
	for <mobileip-archive@lists.ietf.org>; Fri, 7 Sep 2001 06:52:08 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id DAA09274;
	Fri, 7 Sep 2001 03:53:16 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id DAA13849;
	Fri, 7 Sep 2001 03:53:07 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f87Aq2IQ027136
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 7 Sep 2001 03:52:02 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1/Submit) id f87Aq2Vf027135
	for mobile-ip-dist; Fri, 7 Sep 2001 03:52:02 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f87ApvIQ027128
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 7 Sep 2001 03:51:57 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id DAA11566
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 7 Sep 2001 03:52:10 -0700 (PDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id EAA21193
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 7 Sep 2001 04:52:44 -0600 (MDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA05876;
	Fri, 7 Sep 2001 06:50:41 -0400 (EDT)
Message-Id: <200109071050.GAA05876@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: mobile-ip@sunroof.eng.sun.com
From: Internet-Drafts@ietf.org
Subject: [mobile-ip] I-D ACTION:draft-ietf-mobileip-optim-11.txt
Date: Fri, 07 Sep 2001 06:50:41 -0400
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

--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		: Route Optimization in Mobile IP
	Author(s)	: C. Perkins, D. Johnson
	Filename	: draft-ietf-mobileip-optim-11.txt
	Pages		: 25
	Date		: 06-Sep-01
	
Using the base Mobile IP protocol, all datagrams destined to a mobile
node are routed through that mobile node's home agent, which then
tunnels each datagram to the mobile node's current location.  This
document defines Route Optimization messages and extensions to the
base protocol to optimize datagram routing to a mobile node.  Using
these protocol extensions, correspondent nodes may cache the binding
of a mobile node, and then tunnel their datagrams for the mobile node
directly to the care-of address, bypassing the mobile node's home
agent.  Extensions are also provided to allow datagrams in flight
when a mobile node moves, and datagrams sent based on an out-of-date
cached binding, to be forwarded directly to the mobile node's new
binding.

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

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-optim-11.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-optim-11.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:	<20010906145300.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-mobileip-optim-11.txt

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

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

--OtherAccess--

--NextPart--




From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep  7 10:13:14 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14821
	for <mobileip-archive@odin.ietf.org>; Fri, 7 Sep 2001 10:13:13 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id HAA04425;
	Fri, 7 Sep 2001 07:14:24 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id HAA24069;
	Fri, 7 Sep 2001 07:14:11 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f87ECJIQ027369
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 7 Sep 2001 07:12:19 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1/Submit) id f87ECJpf027368
	for mobile-ip-dist; Fri, 7 Sep 2001 07:12:19 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from bebop.France.Sun.COM (bebop.France.Sun.COM [129.157.174.15])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f87ECEIQ027361
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 7 Sep 2001 07:12:15 -0700 (PDT)
Received: from lillen (lillen [129.157.212.23])
	by bebop.France.Sun.COM (8.10.2+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id f87ECON15129;
	Fri, 7 Sep 2001 16:12:24 +0200 (MET DST)
Date: Fri, 7 Sep 2001 16:08:36 +0200 (CEST)
From: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Subject: RE: [mobile-ip] IPsec, IKE, MIPv6 and concensus 
To: jarno.rajahalme@nokia.com
Cc: mobile-ip@sunroof.eng.sun.com
In-Reply-To: "Your message with ID" <009CA59D1752DD448E07F8EB2F911757197FE3@esebe004.NOE.Nokia.com>
Message-ID: <Roam.SIMC.2.0.6.999871716.7667.nordmark@bebop.france>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

> I wote:
> > Agreed from the perspective of IPsec.
> > (There are still PMTU, ROHC? issues etc with piggybacking.)
> > 
> 
> These issues burden the sender choosing to piggyback, not the innocent
> receiver.

Any ROHC issues (assuming they are not already solved)
would appear on any link using ROHC whether the link
is close to the sender or close to the receiver.

   Erik



From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep  7 10:26:14 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15323
	for <mobileip-archive@odin.ietf.org>; Fri, 7 Sep 2001 10:26:13 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id HAA09145;
	Fri, 7 Sep 2001 07:27:21 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id HAA26684;
	Fri, 7 Sep 2001 07:27:07 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f87EPYIQ027410
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 7 Sep 2001 07:25:34 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1/Submit) id f87EPYq3027409
	for mobile-ip-dist; Fri, 7 Sep 2001 07:25:34 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from bebop.France.Sun.COM (bebop.France.Sun.COM [129.157.174.15])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f87EPTIQ027402
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 7 Sep 2001 07:25:30 -0700 (PDT)
Received: from lillen (lillen [129.157.212.23])
	by bebop.France.Sun.COM (8.10.2+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id f87EPdN15941;
	Fri, 7 Sep 2001 16:25:39 +0200 (MET DST)
Date: Fri, 7 Sep 2001 16:21:52 +0200 (CEST)
From: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Subject: Re: [mobile-ip] PMTU, ROHC and piggybacking (was IPsec, IKE, MIPv6 and concensus)
To: Vijay Devarapalli <vijayd@iprg.nokia.com>
Cc: mobile-ip@sunroof.eng.sun.com
In-Reply-To: "Your message with ID" <3B853C5E.191C4C6A@iprg.nokia.com>
Message-ID: <Roam.SIMC.2.0.6.999872512.32574.nordmark@bebop.france>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

[Can we fix the reply-to stuff for this mailing list? I'd like
to be able to tell which emails are replies to stuff I wrote without
looking for "Erik Nordmark wrote:" in the body of the email.]

> hi,
> 
> Erik Nordmark wrote:
> 
> > Agreed from the perspective of IPsec.
> > (There are still PMTU, ROHC? issues etc with piggybacking.)
> 
> whats are the PMTU issues? you check the data packet. if you 
> can add the BU option to the packet without exceeding the
> PMTU, you piggyback. otherwise you dont. you send the BU
> as a separate packet. only the sender has to do this check.

I don't understand whether or not including a BU in a TCP SYN
exchange will/should have any effect on the MSS vs. PMTU 
calculation. Those more up to date on TCP can presumably help.

But in any case, the PMTU stuff adds complexity to the specification.

> its not an issue for ROHC either, we have an implementation 
> here. when ROHC comes across a packet bigger than what it 
> is supposed to be, it skips compressing this particular 
> packet. and this packet is received in the clear. we do 
> exactly this. we have run tests with a simple RTP 
> application. the typical packet in the data stream 
> (that is being compressed in our experiment) is 
> (IPv6 header + home address option + UDP header + 
> RTP header + payload). if a packet received by the 
> compression engine is bigger  than this, we skip 
> compression on this packet. i dont know whats the big 
> deal. it works. somebody please correct me if i am 
> wrong.

Does such an implementation gain any performance benefit by using piggybacking?
 If you assume that an RTP packet gets compressed to N bytes (including
the RTP header) plus RTP payload even when the previous RTP packet
packet did not go through compression you get something like this:

Number of bytes over wire for one RTP packet plus on BU.

No piggybacking:

Packet 1:
	IPv6
	BU

Packet 2:
	IPv6+UDP+RTP+payload compressed to N+payload

sum: 
	IPv6+BU+N+payload

Piggybacking:

Single packet = sum:
	IPv6+BU+UDP+RTP+payload

Difference:
	UDP+RTP-N

Thus you gain by not doing piggybacking.

In order to gain in the piggtbacking+ROHC case the ROHC compressor
must identify that the piggybacked packet is part of the RTP context
in question and compress everything but the BU.

  Erik



From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep  7 10:33:06 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15631
	for <mobileip-archive@odin.ietf.org>; Fri, 7 Sep 2001 10:33:04 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id IAA19341;
	Fri, 7 Sep 2001 08:34:05 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id HAA07594;
	Fri, 7 Sep 2001 07:33:49 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f87EWpIQ027450
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 7 Sep 2001 07:32:51 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1/Submit) id f87EWpEU027449
	for mobile-ip-dist; Fri, 7 Sep 2001 07:32:51 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from bebop.France.Sun.COM (bebop.France.Sun.COM [129.157.174.15])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f87EWlIQ027442
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 7 Sep 2001 07:32:47 -0700 (PDT)
Received: from lillen (lillen [129.157.212.23])
	by bebop.France.Sun.COM (8.10.2+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id f87EWtN16270;
	Fri, 7 Sep 2001 16:32:55 +0200 (MET DST)
Date: Fri, 7 Sep 2001 16:29:08 +0200 (CEST)
From: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Subject: Re: [mobile-ip] processing of the home address option
To: "Charles E. Perkins" <charliep@iprg.nokia.com>
Cc: Henrik.Petander@hut.fi, mobile-ip@sunroof.eng.sun.com
In-Reply-To: "Your message with ID" <3B8D01B5.D3F70A48@iprg.nokia.com>
Message-ID: <Roam.SIMC.2.0.6.999872948.6131.nordmark@bebop.france>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

> The intention was to make sure that processing the home address
> option would cause the mobile node's home address to be delivered
> to the higher level protocols at the correspondent node, while still
> allowing the care-of address to be visible at the IP layer.  The
> restriction about when the processing occurs should probably be
> removed, because it does not matter how an implementation ensures
> the correct property of the home address option (as long as it does
> ensure it).  Currently, the care-of address doesn't serve any
> purpose past this point, and would not have to be maintained by
> the implementation after processing at the network layer.

Well, in order to be able to satisfy the spirit of section 13.2
an implementation should be able to carry the the source (CoA) address
to the transports and applications.

For instance, if TCP detects that it is subject to a SYN attack and wants
to log the source of those packets it would be desired to log both
the CoA and the home address, since the CoA would indicate the topologically
correct source address when ingress filtering is in use.

   Erik



From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep  7 10:43:28 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15998
	for <mobileip-archive@odin.ietf.org>; Fri, 7 Sep 2001 10:43:28 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id HAA16512;
	Fri, 7 Sep 2001 07:44:38 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id HAA09686;
	Fri, 7 Sep 2001 07:44:25 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f87EhFIQ027517
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 7 Sep 2001 07:43:15 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1/Submit) id f87EhFQD027516
	for mobile-ip-dist; Fri, 7 Sep 2001 07:43:15 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f87EhCIQ027509
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 7 Sep 2001 07:43:12 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id HAA08822;
	Fri, 7 Sep 2001 07:43:24 -0700 (PDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA27954;
	Fri, 7 Sep 2001 08:43:59 -0600 (MDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id HAA09449;
	Fri, 7 Sep 2001 07:42:50 -0700 (PDT)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f87Egnk19741;
	Fri, 7 Sep 2001 07:42:49 -0700
X-mProtect:  Fri, 7 Sep 2001 07:42:49 -0700 Nokia Silicon Valley Messaging Protection
Received: from charliep.iprg.nokia.com (205.226.2.89, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpd0cSPGL; Fri, 07 Sep 2001 07:42:47 PDT
Message-ID: <3B98DCE8.279DE5C4@iprg.nokia.com>
Date: Fri, 07 Sep 2001 07:42:48 -0700
From: "Charles E. Perkins" <charliep@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Erik Nordmark <Erik.Nordmark@eng.sun.com>
CC: mobile-ip@sunroof.eng.sun.com, Henrik.Petander@hut.fi
Subject: Re: [mobile-ip] processing of the home address option
References: <Roam.SIMC.2.0.6.999872948.6131.nordmark@bebop.france>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Erik Nordmark wrote:

> Well, in order to be able to satisfy the spirit of section 13.2
> an implementation should be able to carry the the source (CoA) address
> to the transports and applications.
> 
> For instance, if TCP detects that it is subject to a SYN attack and wants
> to log the source of those packets it would be desired to log both
> the CoA and the home address, since the CoA would indicate the topologically
> correct source address when ingress filtering is in use.

Agreed.  Is this something you think ought to be written up in
the specification?  I'd lean towards not including it unless
you think it's important (and, might I ask, supply text?).

Regards,
Charlie P.


From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep  7 11:42:26 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17554
	for <mobileip-archive@odin.ietf.org>; Fri, 7 Sep 2001 11:42:25 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA13246;
	Fri, 7 Sep 2001 08:43:27 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id IAA17203;
	Fri, 7 Sep 2001 08:42:47 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f87FfQIQ027696
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 7 Sep 2001 08:41:26 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1/Submit) id f87FfQ4I027695
	for mobile-ip-dist; Fri, 7 Sep 2001 08:41:26 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f87FfNIQ027688
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 7 Sep 2001 08:41:23 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id IAA18906
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 7 Sep 2001 08:41:35 -0700 (PDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id JAA28799
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 7 Sep 2001 09:42:11 -0600 (MDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id IAA12560;
	Fri, 7 Sep 2001 08:41:34 -0700 (PDT)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f87FfXV21853;
	Fri, 7 Sep 2001 08:41:33 -0700
X-mProtect:  Fri, 7 Sep 2001 08:41:33 -0700 Nokia Silicon Valley Messaging Protection
Received: from charliep.iprg.nokia.com (205.226.2.89, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpd6rvTpa; Fri, 07 Sep 2001 08:41:31 PDT
Message-ID: <3B98EAAC.F3C7D746@iprg.nokia.com>
Date: Fri, 07 Sep 2001 08:41:32 -0700
From: "Charles E. Perkins" <charliep@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: "Peter Grimstrup (TED)" <peter.grimstrup@ted.ericsson.dk>
CC: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Coexistence with other uses for routing header
References: <3B989380.F7266A42@ted.ericsson.dk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

"Peter Grimstrup (TED)" wrote:

                 ..........

>>    in the type 0 routing header.  Otherwise, the correspondent
>>    node MUST place the mobile node's home address immediately
>>    after the care-of address entry of the routing header, following
>>    all other intermediate node addresses that would have
>>    already been in the routing header before the creation
>>    of the Binding Cache entry for the care-of address.
> 
> I don't understand the last part, i.e. "... following all other ..."
> 
> Suggest replacing with
>     ...
>     in the type 0 routing header.  Otherwise, the correspondent
>     node MUST insert the mobile node's care-of address immediately
>     before the home address entry in the routing header.

Yes, this is better.  I'll use your simpler formulation.


> Further I suggest changing section "8.9 Sending Packets to a Mobile Node"
> in a way that the next example will be described/allowed:
> 
> IPv6 Hdr:      source
>                intermediate-dest-1
> RH(4 entries): intermediate-dest-2
>                CoA
>                MN-HoA

No problem; can you suggest some text?

Regards,
Charlie P.


From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep  7 13:11:09 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20877
	for <mobileip-archive@odin.ietf.org>; Fri, 7 Sep 2001 13:11:07 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id LAA10842;
	Fri, 7 Sep 2001 11:12:04 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id KAA11369;
	Fri, 7 Sep 2001 10:11:59 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f87HAoIQ027859
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 7 Sep 2001 10:10:50 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1/Submit) id f87HAouM027858
	for mobile-ip-dist; Fri, 7 Sep 2001 10:10:50 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f87HAkIQ027851
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 7 Sep 2001 10:10:46 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id KAA12435
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 7 Sep 2001 10:10:59 -0700 (PDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id KAA08279
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 7 Sep 2001 10:10:58 -0700 (PDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id KAA18875;
	Fri, 7 Sep 2001 10:10:58 -0700 (PDT)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f87HAvN30544;
	Fri, 7 Sep 2001 10:10:57 -0700
X-mProtect:  Fri, 7 Sep 2001 10:10:57 -0700 Nokia Silicon Valley Messaging Protection
Received: from charliep.iprg.nokia.com (205.226.2.89, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpd7HGv0L; Fri, 07 Sep 2001 10:10:55 PDT
Message-ID: <3B98FFA0.DAC0B9F1@iprg.nokia.com>
Date: Fri, 07 Sep 2001 10:10:56 -0700
From: "Charles E. Perkins" <charliep@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: "Peter Grimstrup (TED)" <peter.grimstrup@ted.ericsson.dk>
CC: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Mobile IPv6 draft revision
References: <3B84DDAD.918FE9B3@ted.ericsson.dk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hello Peter,

I'm resolving old issues one by one...

"Peter Grimstrup (TED)" wrote:
> 
> >From draft-14:
> 
> 8.5. Sending Binding Acknowledgements
> 
>                    and the packet MUST be sent using a Routing header
>                                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>    in the same way as any other packet sent to a mobile node using a
>    care-of address (even if the binding was rejected), as described in
>    Section 8.9.
> 
> 8.9. Sending Packets to a Mobile Node
> 
>    Before sending any packet, the sending node SHOULD examine its
>    Binding Cache for an entry for the destination address to which the
>    packet is being sent.  If the sending node has a Binding Cache entry
>    for this address, the sending node SHOULD use a Routing header
> 
> I find the 2 sections in conflict. Further sec. 5.2 also says
> "The packet is sent using a routing header"

I agree that the wording is inconsistent.  I think that the original
idea was to to accomplish two results:
1. mandate use of the care-of address in Binding Acknowledgements
2. strongly recommend, but not absolutely mandate, the use of the
   care-of address by typical correspondent nodes whenever they have
   a valid Binding Cache entry with the mobile node's care-of address.

I'm not sure about all the reasons for result (2).  We could just
go ahead and mandate use of the care-of address, but I'm not so
confident that is the correct plan.  As it is, I will revise the
wording in sections 8.9 and 5.2 to eliminate, for instance, the
clause "in the same way as any other packet sent to a mobile node".
I think that will fix the immediate problem.


> Comments to De-registration (not touching the questions raised by
> Francis Dupont recently).
> 
> The deregistration may be sent from
>  a) the Home Address (any Lifetime)
>  b) the latest Care Of Address (Lifetime = 0)
>  c) another address (Lifetime = 0)
> 
> First the Binding Cache Entry (BCE) is deleted (see sec. 8.4 and 9.2)
> then the Binding Acknowledgement (BA) is sent.
> 
> As mentioned above, the BA must be sent with a routing header, but
> we have no BCE anymore.

Check.  I see the problem!

> In case a) the BA should be sent to the Home Address (in this case a
> routing header is not really needed, doesn't harm much either).
> In case b) and c) the BA could reasonably be sent back to the source
> address of the deregistration, which in case b) is the BCE just deleted.

Here I am not so sure.  Since the mobile node is considered to be
addressable at its home address, I think it should receive packets
that are addressed to its home address.  Use of the care-of address
is akin to multi-homing, and I don't think that should be considered
as a solution to this problem.

The problem is that:
- On the one hand, a Binding Update with a positive lifetime, and the
  'A' bit set, needs to have the Binding Cache updated before a Binding
  Acknowledgement sent by way of the _new_ care-of address.

- On the other hand, a Binding Update with a zero lifetime, and the
  'A' bit set, needs to have a Binding Acknowledgement send by way
  of a care-of address that arguably can no longer be used.

I think this is a basic inconsistency in the use of the Binding
Update, and I thought of a fairly trivial-to-implement solution:

   + Disallow Binding Updates with zero lifetimes in cases (b) and (c).

If the Binding Update, intended for deregistration, had a
lifetime of 1 second, then that would be enough time to use
the existing Binding Cache entry for delivering the Binding
Acknowledgement to the still non-local mobile node.

If you agree that this is a good solution, then the next step is
to figure out how to write the specification.  Help is always
appreciated!

Regards,
Charlie P.


From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep  7 15:40:14 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25880
	for <mobileip-archive@odin.ietf.org>; Fri, 7 Sep 2001 15:40:13 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id NAA04192;
	Fri, 7 Sep 2001 13:41:08 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id MAA20089;
	Fri, 7 Sep 2001 12:41:02 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f87Jd1IQ028199
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 7 Sep 2001 12:39:01 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1/Submit) id f87Jd1TJ028198
	for mobile-ip-dist; Fri, 7 Sep 2001 12:39:01 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f87JcvIQ028191
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 7 Sep 2001 12:38:57 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id MAA19713
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 7 Sep 2001 12:39:10 -0700 (PDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id MAA22099
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 7 Sep 2001 12:39:09 -0700 (PDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id MAA29987;
	Fri, 7 Sep 2001 12:39:03 -0700 (PDT)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f87Jd2032213;
	Fri, 7 Sep 2001 12:39:02 -0700
X-mProtect:  Fri, 7 Sep 2001 12:39:02 -0700 Nokia Silicon Valley Messaging Protection
Received: from charliep.iprg.nokia.com (205.226.2.89, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpdohpTLG; Fri, 07 Sep 2001 12:39:00 PDT
Message-ID: <3B992254.679EA9BA@iprg.nokia.com>
Date: Fri, 07 Sep 2001 12:39:00 -0700
From: "Charles E. Perkins" <charliep@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Mobile IP Working Group <mobile-ip@sunroof.eng.sun.com>
CC: "Basavaraj Patil (NTC/Dallas)" <Basavaraj.Patil@nokia.com>,
        Phil Roberts <PRoberts@MEGISTO.com>
Subject: [mobile-ip] [Fwd: Re: Proposed addition to RFC2002bis]
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hello folks,

In case it is finally decided to insert MIER into RFC2002bis,
I have prepared the following rough text.  It was taken directly
from MIER version 7, and I did a little wordsmithing to make it
fit.  If there are no objections, the final result is likely
to be very similar to what is shown below.

Comments will be appreciated!

Regards,
Charlie P.

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


material for existing section 1.8.
	"Message Format and Protocol Extensibility"

    The type field in the Mobile IP extension structure can support
    upto 255 (skippable and not skippable) uniquely identifiable
    extensions.  Unless additional structure is utilized for the
    extension types, the proliferation of new developments/additions
    to Mobile IP might require so many new extensions that the available
    space for extension types might run out.

    Two new extension structures are proposed to solve this problem.
    Certain types of extensions can be aggregated, using subtypes to
    identify the precise extension, for example as has been done
    with the Generalized Key Distribution extensions~\cite{genkey}.
    This will greatly reduce the rate of allocation for news
    values of the type field. 

    Since the new extension structures will cause an efficient
    usage of the extension type space, it is recommended
    that new Mobile IP extensions follow one of the two new
    extension formats whenever there may be the possibility to
    group related extensions together. 


1.8.1 Long Extension Format

   This format is applicable for non-skippable extensions which carry 
   information more than 256 bytes. It should be applicable to any future
   standardization which consider non-skippable extensions which accommodate 
   up to 64 KBytes of data. 

      0                   1                   2                   3
     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |     Type      |  Sub-Type     |           Length              |
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |                           Data      .....    
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 


     The proposed general structure of the Long Extension consists
     of the following fields:

     
    Type   is the type which describe a collection of extensions which
           has a common data type (see A.1, A.3).

    Sub-Type  is a unique number given to each member in the
              aggregated type.  Sub-Type values between of 200 through
              255 are reserved for future use and standardization.

    Length indicates the length (in bytes) of the data field within
           this Extension. It does NOT include the Type, Length
           and Sub-Type bytes.


    Data   is the data associated with this extension. This data MAY
           be represented in many ways (see A.1, A.3)

        
    Two bytes for the length field is suggested to enable providing a
    sufficiently large space for the extension data (maximum 64Kbytes). 
    
1.8.2 Short Extension Format

    This format is backward compatible with the skippable extensions
    as it is defined in [Perkins96]. Also, it applicable for extensions
    which doe not require more than 256 bytes of data.

      0                   1                   2                   3
     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    |     Type      |   Length      |    Sub-Type   |    Data ....
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

     The proposed general structure of the Short Extension consists
     of the following fields:

     
    Type   is the type which describe a collection of extensions which
           has a common data type (see  A.2).

    Sub-Type  is a unique number given to each member in the
              aggregated type.  Sub-Type values between of 200 through
              255 are reserved for future use and standardization.

    Length 8-bit unsigned integer. Length of the extension, in octets,
           excluding the extension Type and the extension Length fields.
           This field MUST be set to 1 plus the total length of the 
           data field.


    Data   is the data associated with this extension. This data MAY
           be represented in many ways (see  A.2)


From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep  7 18:06:59 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29900
	for <mobileip-archive@lists.ietf.org>; Fri, 7 Sep 2001 18:06:58 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id QAA09440;
	Fri, 7 Sep 2001 16:07:34 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id PAA25722;
	Fri, 7 Sep 2001 15:07:28 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f87M6LIQ028412
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 7 Sep 2001 15:06:21 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1/Submit) id f87M6LlO028411
	for mobile-ip-dist; Fri, 7 Sep 2001 15:06:21 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from heliopolis.eng.sun.com (heliopolis.Eng.Sun.COM [152.70.1.39])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f87M6IIQ028404
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 7 Sep 2001 15:06:18 -0700 (PDT)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.eng.sun.com (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id PAA17773
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 7 Sep 2001 15:06:33 -0700 (PDT)
Message-Id: <200109072206.PAA17773@heliopolis.eng.sun.com>
Date: Fri, 7 Sep 2001 15:06:32 -0700 (PDT)
From: James Kempf <James.Kempf@Sun.COM>
Subject: [mobile-ip] New BETH Draft
To: mobile-ip@sunroof.eng.sun.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: F8RxhRodQu7XDpC5lpY99A==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Hi folks,

Just posted the 02 BETH draft to the IETF drafts directory. Many thanx
to those who contributed to the discussion of tunnel termination
over the last couple days, I've attempted to capture the conversation
in the section on tunnel termination. Also, I think I've incorporated all the 
comments that came up at the London meeting and prior to it as well,
and tryed to integrate BETH into the FMIPv6 framework more tightly.
Please let me know if I've missed anything. 

I also removed alot of the explanatory material, and the appendicies
discussing theoretical performance of FMIPv6 and smoothing, and
sanitized any references to individual smoothing techniques within
the body of the protocol description. The result should be ready
to incorporate into FMIPv6.

As agreed upon in London, unless there are any further changes needed,
I'd like to move forward with Gopal on incorporating the draft
into the body of draft-ietf-mobileip-fast-mipv6-02.txt.

		jak



From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep  7 19:49:33 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01614
	for <mobileip-archive@odin.ietf.org>; Fri, 7 Sep 2001 19:49:32 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id QAA12278;
	Fri, 7 Sep 2001 16:50:41 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id QAA17554;
	Fri, 7 Sep 2001 16:50:29 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f87NnOIQ028552
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 7 Sep 2001 16:49:24 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1/Submit) id f87NnO0P028551
	for mobile-ip-dist; Fri, 7 Sep 2001 16:49:24 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f87NnKIQ028544
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 7 Sep 2001 16:49:20 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id QAA17995
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 7 Sep 2001 16:49:33 -0700 (PDT)
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id RAA18672
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 7 Sep 2001 17:50:08 -0600 (MDT)
Received: from mira-sjc5-7.cisco.com (mira-sjc5-7.cisco.com [171.71.163.27])
	by sj-msg-core-1.cisco.com (8.11.3/8.9.1) with ESMTP id f87Nnax08080
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 7 Sep 2001 16:49:36 -0700 (PDT)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-7.cisco.com (Mirapoint)
	with ESMTP id ABK00325;
	Fri, 7 Sep 2001 16:49:29 -0700 (PDT)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id QAA25043; Fri, 7 Sep 2001 16:49:29 -0700 (PDT)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15257.23817.574057.41814@thomasm-u1.cisco.com>
Date: Fri, 7 Sep 2001 16:49:29 -0700 (PDT)
To: mobile-ip@sunroof.eng.sun.com
Subject: [mobile-ip] I-D ACTION:draft-ietf-mobileip-optim-11.txt
In-Reply-To: <200109071050.GAA05876@ietf.org>
References: <200109071050.GAA05876@ietf.org>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

So, like, doesn't this suffer from the exact same
set of issues as mipv6 for binding update
security? Is the intention to have a common
solution for both? I assume this can't progress
until the CN security scaling problem is solved
similar to mipv6.

	   Mike

Internet-Drafts@ietf.org writes:
 > 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		: Route Optimization in Mobile IP
 > 	Author(s)	: C. Perkins, D. Johnson
 > 	Filename	: draft-ietf-mobileip-optim-11.txt
 > 	Pages		: 25
 > 	Date		: 06-Sep-01
 > 	
 > Using the base Mobile IP protocol, all datagrams destined to a mobile
 > node are routed through that mobile node's home agent, which then
 > tunnels each datagram to the mobile node's current location.  This
 > document defines Route Optimization messages and extensions to the
 > base protocol to optimize datagram routing to a mobile node.  Using
 > these protocol extensions, correspondent nodes may cache the binding
 > of a mobile node, and then tunnel their datagrams for the mobile node
 > directly to the care-of address, bypassing the mobile node's home
 > agent.  Extensions are also provided to allow datagrams in flight
 > when a mobile node moves, and datagrams sent based on an out-of-date
 > cached binding, to be forwarded directly to the mobile node's new
 > binding.
 > 
 > A URL for this Internet-Draft is:
 > http://www.ietf.org/internet-drafts/draft-ietf-mobileip-optim-11.txt
 > 
 > To remove yourself from the IETF Announcement list, send a message to 
 > ietf-announce-request with the word unsubscribe in the body of the message.
 > 
 > 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-optim-11.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-optim-11.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.
 > Content-Type: text/plain
 > Content-ID:	<20010906145300.I-D@ietf.org>
 > 
 > ENCODING mime
 > FILE /internet-drafts/draft-ietf-mobileip-optim-11.txt
 > Content-Type: text/plain
 > Content-ID:	<20010906145300.I-D@ietf.org>


From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep  7 21:31:04 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA03285
	for <mobileip-archive@lists.ietf.org>; Fri, 7 Sep 2001 21:31:03 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id TAA05581;
	Fri, 7 Sep 2001 19:32:06 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id SAA04650;
	Fri, 7 Sep 2001 18:31:49 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f881UPIQ028648
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 7 Sep 2001 18:30:25 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1/Submit) id f881UPpV028647
	for mobile-ip-dist; Fri, 7 Sep 2001 18:30:25 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.12.0.Gamma1+Sun/8.12.0.Gamma1) with ESMTP id f881ULIQ028640
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 7 Sep 2001 18:30:21 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id SAA01848
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 7 Sep 2001 18:30:36 -0700 (PDT)
Received: from roll.mentat.com ([192.88.122.129])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id SAA28539
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 7 Sep 2001 18:30:35 -0700 (PDT)
Received: from leo.mentat.com (leo [192.88.122.132])
	by roll.mentat.com (8.9.1b+Sun/8.9.1) with ESMTP id SAA28286
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 7 Sep 2001 18:31:17 -0700 (PDT)
Received: (from marc@localhost)
	by leo.mentat.com (8.9.1b+Sun/8.9.1) id SAA05370
	for mobile-ip@sunroof.eng.sun.com; Fri, 7 Sep 2001 18:31:16 -0700 (PDT)
Date: Fri, 7 Sep 2001 18:31:16 -0700 (PDT)
From: Marc Hasson <marc@mentat.com>
Message-Id: <200109080131.SAA05370@leo.mentat.com>
To: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Mobile IPv6 draft revision
X-Sun-Charset: US-ASCII
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Hi Charlie,

 > > The deregistration may be sent from
 > >  a) the Home Address (any Lifetime)
 > >  b) the latest Care Of Address (Lifetime = 0)
 > >  c) another address (Lifetime = 0)
 > > 

...

 > I think this is a basic inconsistency in the use of the Binding
 > Update, and I thought of a fairly trivial-to-implement solution:
 > 
 >    + Disallow Binding Updates with zero lifetimes in cases (b) and (c).
 > 
 > If the Binding Update, intended for deregistration, had a
 > lifetime of 1 second, then that would be enough time to use
 > the existing Binding Cache entry for delivering the Binding
 > Acknowledgement to the still non-local mobile node.

I think there are more implications here beyond sending off the
immediate BA.  Perhaps some more clarifications can be added.  What if
the BA is lost on its way to the MN?  The MN doesn't know the HA
actually received its deregistration BU so its going to have to
retransmit its BU.  Likely to be at more than a 1 second interval?
Meanwhile the HA has already deregistered and destroyed the binding.
On subsequent BUs is the HA supposed to *know* that a 1 second
lifetime is not enough to be useful so don't go through the true
registration stuff (DAD/ND, etc.) but just send a BA back to the MN to
"acknowledge" the deregistration that actually "lives" 1 more second?

Whats wrong with keeping the special deregistration lifetime of 0 on
the non-Home Address BUs?  (I won't ask why a zero is not mandatory on
the returned-to-home ones too so one path in the BU processing code may
be quickly selected.)  Just have the HA interpret the zero as the MN
asking "please confirm via a BA using this BU's info that I'm no longer
registered with you"?  This also sidesteps the issue of the lost BA and
getting back "success" vs. "not HA for this MN" errors on the
retransmission.  Both would be consistent success instead of implying
some kind of operational error for merely a lost packet.  The BCE lives
long enough, or exists temporarily/updated from this BU, just to get
the BA reply into some transmission queue before disappearing due to
the BU's zero lifetime.  Seems to me this takes care of the issue of
the MN retransmitting for a lost deregistration BU or BA without having
the HA go through any kind of registration "dance", having been misled
by a non-zero lifetime or burdened with more rules about lifetime
values.

What am I missing?  Another way to look at this is to simply state that
for deregistration the BA is constructed from the BSA-secured
deregistration BU's info (error #139 is one exception to "BSA-secured"
but for that and other errors the BA is built the same way).  Its *not*
exactly like sending "any other packet" as stated in 8.5/8.9 using a
BCE.  The earlier change you suggested, not quoted in this note, will
clean that up.  For deregistration BUs it may help to state a routing
header is included in the BA, built using the BU's info, only if the
deregistration BU was of non-local origin.  The BCE itself can, in
fact, be deleted before sending the BA for all deregistration cases.
                        
                         
   -- Marc --




From owner-mobile-ip@sunroof.eng.sun.com  Mon Sep 10 04:33:33 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA07308
	for <mobileip-archive@lists.ietf.org>; Mon, 10 Sep 2001 04:33:33 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id CAA27711;
	Mon, 10 Sep 2001 02:31:52 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id BAA22445;
	Mon, 10 Sep 2001 01:31:36 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8A8U949001032
	for <mobile-ip-dist@sunroof.eng.sun.com>; Mon, 10 Sep 2001 01:30:09 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8A8U9O0001031
	for mobile-ip-dist; Mon, 10 Sep 2001 01:30:09 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8A8U549001024
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 10 Sep 2001 01:30:05 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id BAA22284
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 10 Sep 2001 01:30:15 -0700 (PDT)
Received: from cwcsun41.cwc.nus.edu.sg (cwcsun41.cwc.nus.edu.sg [137.132.163.102])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id CAB25316
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 10 Sep 2001 02:28:01 -0600 (MDT)
Received: from there ([172.16.3.147])
	by cwcsun41.cwc.nus.edu.sg (8.9.3/8.9.3) with SMTP id QAA15662;
	Mon, 10 Sep 2001 16:26:39 +0800 (SGT)
Message-Id: <200109100826.QAA15662@cwcsun41.cwc.nus.edu.sg>
Content-Type: text/plain;
  charset="iso-8859-1"
From: Parijat <parijat@cwc.nus.edu.sg>
Organization: CWC
To: mobile-ip@sunroof.eng.sun.com,
        "Charles E. Perkins" <charliep@iprg.nokia.com>,
        "Peter Grimstrup (TED)" <peter.grimstrup@ted.ericsson.dk>
Subject: Re: [mobile-ip] Mobile IPv6 draft revision
Date: Mon, 10 Sep 2001 16:31:59 -0400
X-Mailer: KMail [version 1.3]
Cc: mobile-ip@sunroof.eng.sun.com
References: <3B84DDAD.918FE9B3@ted.ericsson.dk> <3B98FFA0.DAC0B9F1@iprg.nokia.com>
In-Reply-To: <3B98FFA0.DAC0B9F1@iprg.nokia.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 8bit

On Friday 07 September 2001 13:10, Charles E. Perkins wrote:
>
> I think this is a basic inconsistency in the use of the Binding
> Update, and I thought of a fairly trivial-to-implement solution:
>
>    + Disallow Binding Updates with zero lifetimes in cases (b) and (c).
>
> If the Binding Update, intended for deregistration, had a
> lifetime of 1 second, then that would be enough time to use
> the existing Binding Cache entry for delivering the Binding
> Acknowledgement to the still non-local mobile node.

That does not answer the basic question that a BA might be addressed to a CoA 
which is no longer valid.

I would suggest that cache deletion requests come in with zero lifetimes, 
(perhaps even in case (a)?), and the acknowledgements to _deletion_ requests 
be sent to the home address of the mobile node.

Of course, I am assuming that there is some need to keep a conceptual, 
specific difference between binding cache deletion requests and binding 
updates which merely have a very short lifetime.  It seems to be a neat thing 
to have a separate binding deletion message rather than one which is a 
degenerate case of a normal BU (okay, okay, zero lifetime BUs _are_ 
degenerate cases of normal BUs, but you know what I mean).


-- 
Parijat Mishra
R & D Engineer,
Centre for Wireless Communications, NUS
Tel: (65)8709353


From owner-mobile-ip@sunroof.eng.sun.com  Mon Sep 10 10:19:55 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16192
	for <mobileip-archive@lists.ietf.org>; Mon, 10 Sep 2001 10:19:54 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id HAA20729;
	Mon, 10 Sep 2001 07:20:53 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id HAA25855;
	Mon, 10 Sep 2001 07:20:33 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8AEHX49001390
	for <mobile-ip-dist@sunroof.eng.sun.com>; Mon, 10 Sep 2001 07:17:33 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8AEHWhC001389
	for mobile-ip-dist; Mon, 10 Sep 2001 07:17:32 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8AEHT49001382
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 10 Sep 2001 07:17:29 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id HAA25585
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 10 Sep 2001 07:17:41 -0700 (PDT)
Received: from iproxy1.ericsson.dk (iproxy1.ericsson.dk [130.228.248.98])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id IAA14104
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 10 Sep 2001 08:17:37 -0600 (MDT)
Received: from unixmail.ted.dk.eu.ericsson.se (knud.ted.dk.eu.ericsson.se [192.66.4.246])
	by iproxy1.ericsson.dk (8.10.1/8.10.1) with ESMTP id f8AEHdc08021
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 10 Sep 2001 16:17:39 +0200 (MET DST)
Received: from ted.ericsson.dk (petg.ted.dk.eu.ericsson.se [192.66.4.85])
	by unixmail.ted.dk.eu.ericsson.se (8.10.1/8.10.1/TEDmain-1.0) with ESMTP id f8AEHXL21265;
	Mon, 10 Sep 2001 16:17:33 +0200 (MEST)
Message-ID: <3B9CCB7D.83E2734C@ted.ericsson.dk>
Date: Mon, 10 Sep 2001 16:17:33 +0200
From: "Peter Grimstrup (TED)" <peter.grimstrup@ted.ericsson.dk>
Organization: Ericsson Telebit A/S
X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.14-5.0 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Mobile IPv6 draft revision
References: <200109080131.SAA05370@leo.mentat.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hi Marc and Charlie,

Agree with Marcs comments and suggestions.

Peter


Marc Hasson wrote:
> 
> Hi Charlie,
> 
>  > > The deregistration may be sent from
>  > >  a) the Home Address (any Lifetime)
>  > >  b) the latest Care Of Address (Lifetime = 0)
>  > >  c) another address (Lifetime = 0)
>  > >
> 
> ...
> 
>  > I think this is a basic inconsistency in the use of the Binding
>  > Update, and I thought of a fairly trivial-to-implement solution:
>  >
>  >    + Disallow Binding Updates with zero lifetimes in cases (b) and (c).
>  >
>  > If the Binding Update, intended for deregistration, had a
>  > lifetime of 1 second, then that would be enough time to use
>  > the existing Binding Cache entry for delivering the Binding
>  > Acknowledgement to the still non-local mobile node.
> 
> I think there are more implications here beyond sending off the
> immediate BA.  Perhaps some more clarifications can be added.  What if
> the BA is lost on its way to the MN?  The MN doesn't know the HA
> actually received its deregistration BU so its going to have to
> retransmit its BU.  Likely to be at more than a 1 second interval?
> Meanwhile the HA has already deregistered and destroyed the binding.
> On subsequent BUs is the HA supposed to *know* that a 1 second
> lifetime is not enough to be useful so don't go through the true
> registration stuff (DAD/ND, etc.) but just send a BA back to the MN to
> "acknowledge" the deregistration that actually "lives" 1 more second?
> 
> Whats wrong with keeping the special deregistration lifetime of 0 on
> the non-Home Address BUs?  (I won't ask why a zero is not mandatory on
> the returned-to-home ones too so one path in the BU processing code may
> be quickly selected.)  Just have the HA interpret the zero as the MN
> asking "please confirm via a BA using this BU's info that I'm no longer
> registered with you"?  This also sidesteps the issue of the lost BA and
> getting back "success" vs. "not HA for this MN" errors on the
> retransmission.  Both would be consistent success instead of implying
> some kind of operational error for merely a lost packet.  The BCE lives
> long enough, or exists temporarily/updated from this BU, just to get
> the BA reply into some transmission queue before disappearing due to
> the BU's zero lifetime.  Seems to me this takes care of the issue of
> the MN retransmitting for a lost deregistration BU or BA without having
> the HA go through any kind of registration "dance", having been misled
> by a non-zero lifetime or burdened with more rules about lifetime
> values.
> 
> What am I missing?  Another way to look at this is to simply state that
> for deregistration the BA is constructed from the BSA-secured
> deregistration BU's info (error #139 is one exception to "BSA-secured"
> but for that and other errors the BA is built the same way).  Its *not*
> exactly like sending "any other packet" as stated in 8.5/8.9 using a
> BCE.  The earlier change you suggested, not quoted in this note, will
> clean that up.  For deregistration BUs it may help to state a routing
> header is included in the BA, built using the BU's info, only if the
> deregistration BU was of non-local origin.  The BCE itself can, in
> fact, be deleted before sending the BA for all deregistration cases.
> 
> 
>    -- Marc --


From owner-mobile-ip@sunroof.eng.sun.com  Mon Sep 10 10:39:38 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16766
	for <mobileip-archive@odin.ietf.org>; Mon, 10 Sep 2001 10:39:38 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id IAA01300;
	Mon, 10 Sep 2001 08:40:35 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id HAA28753;
	Mon, 10 Sep 2001 07:40:15 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8AEaj49001444
	for <mobile-ip-dist@sunroof.eng.sun.com>; Mon, 10 Sep 2001 07:36:45 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8AEaiIf001443
	for mobile-ip-dist; Mon, 10 Sep 2001 07:36:44 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8AEaf49001436
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 10 Sep 2001 07:36:41 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id HAA23520
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 10 Sep 2001 07:36:54 -0700 (PDT)
Received: from iproxy1.ericsson.dk (iproxy1.ericsson.dk [130.228.248.98])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id HAA29610
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 10 Sep 2001 07:36:53 -0700 (PDT)
Received: from unixmail.ted.dk.eu.ericsson.se (knud.ted.dk.eu.ericsson.se [192.66.4.246])
	by iproxy1.ericsson.dk (8.10.1/8.10.1) with ESMTP id f8AEapc10642
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 10 Sep 2001 16:36:51 +0200 (MET DST)
Received: from ted.ericsson.dk (petg.ted.dk.eu.ericsson.se [192.66.4.85])
	by unixmail.ted.dk.eu.ericsson.se (8.10.1/8.10.1/TEDmain-1.0) with ESMTP id f8AEagL21803;
	Mon, 10 Sep 2001 16:36:42 +0200 (MEST)
Message-ID: <3B9CCFFA.B6FBB249@ted.ericsson.dk>
Date: Mon, 10 Sep 2001 16:36:42 +0200
From: "Peter Grimstrup (TED)" <peter.grimstrup@ted.ericsson.dk>
Organization: Ericsson Telebit A/S
X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.14-5.0 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Mobile IPv6 draft revision
References: <3B84DDAD.918FE9B3@ted.ericsson.dk> <3B98FFA0.DAC0B9F1@iprg.nokia.com> <200109100826.QAA15662@cwcsun41.cwc.nus.edu.sg>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Comments inline

Peter

Parijat wrote:
> 
> That does not answer the basic question that a BA might be addressed to a CoA
> which is no longer valid.
> 

Well, if a MN send the deregistration from a Care-of Address it does
not want to use (any more) asking for an acknowledgement, it should
reasonably stay there for some minimum of time. Leaving before the BA
is received is OK though, the MN may wish to retransmit the deregistration
from its new location - but with the interpretation from Marc Hassons mail
(7 sep, 18:31) that will be OK as well.

> I would suggest that cache deletion requests come in with zero lifetimes,
> (perhaps even in case (a)?), and the acknowledgements to _deletion_ requests
> be sent to the home address of the mobile node.

But maybe the MN just wants to stay away in privacy for some time for some
reason - that happens, I guess. I think Marc's proposal will work.

> 
> Of course, I am assuming that there is some need to keep a conceptual,
> specific difference between binding cache deletion requests and binding
> updates which merely have a very short lifetime.  It seems to be a neat thing
> to have a separate binding deletion message rather than one which is a
> degenerate case of a normal BU (okay, okay, zero lifetime BUs _are_
> degenerate cases of normal BUs, but you know what I mean).
> 
Actually a nice idea, but...
> --
> Parijat Mishra
> R & D Engineer,
> Centre for Wireless Communications, NUS
> Tel: (65)8709353


From owner-mobile-ip@sunroof.eng.sun.com  Mon Sep 10 11:22:36 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18170
	for <mobileip-archive@odin.ietf.org>; Mon, 10 Sep 2001 11:22:35 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id JAA09556;
	Mon, 10 Sep 2001 09:23:38 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id IAA09923;
	Mon, 10 Sep 2001 08:23:33 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8AFLo49001617
	for <mobile-ip-dist@sunroof.eng.sun.com>; Mon, 10 Sep 2001 08:21:50 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8AFLotX001616
	for mobile-ip-dist; Mon, 10 Sep 2001 08:21:50 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8AFLk49001609
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 10 Sep 2001 08:21:47 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id IAA09549
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 10 Sep 2001 08:22:01 -0700 (PDT)
Received: from e1.ny.us.ibm.com (e1.ny.us.ibm.com [32.97.182.101])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id IAA26410
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 10 Sep 2001 08:21:59 -0700 (PDT)
Received: from northrelay02.pok.ibm.com (northrelay02.pok.ibm.com [9.117.200.22])
	by e1.ny.us.ibm.com (8.9.3/8.9.3) with ESMTP id LAA279940
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 10 Sep 2001 11:19:37 -0400
Received: from d01ml233.pok.ibm.com (d01ml233.pok.ibm.com [9.117.200.63])
	by northrelay02.pok.ibm.com (8.11.1m3/NCO v4.97.1) with ESMTP id f8AFDhd107850
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 10 Sep 2001 11:13:43 -0400
Importance: Normal
Subject: [mobile-ip] MobiHoc 2001 early registration due this Thursday (September 13)
To: mobile-ip@sunroof.eng.sun.com
X-Mailer: Lotus Notes Release 5.0.3 (Intl) 21 March 2000
Message-ID: <OF679AEE97.F68F09CE-ON85256AC3.004AEFE3@pok.ibm.com>
From: "Young-bae Ko" <youngko@us.ibm.com>
Date: Mon, 10 Sep 2001 11:21:47 -0400
X-MIMETrack: Serialize by Router on D01ML233/01/M/IBM(Release 5.0.8 |June 18, 2001) at
 09/10/2001 11:21:50 AM
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

                     Call for Participation

                          MobiHoc 2001
                          ============

            The 2001 ACM International Symposium on
              Mobile Ad Hoc Networking & Computing

         October 4-5, 2001,Long Beach, California, USA

                 http://www.cs.ucla.edu/mobihoc/
                 ------------------------------

                   Sponsored by ACM SIGMOBILE

MobiHoc 2001, sponsored by ACM SIGMOBILE, will serve as an international
forum for addressing cutting-edge issues related to mobile ad hoc
networking and computing. Following the success of MobiHoc 2000 in Boston,
MobiHoc 2001 has been expanded to a 2-day symposium, to provide more
opportunities for participation by the ad hoc networking and computing
community.

We invite you to join us for MobiHoc 2001, at the Hyatt Regency hotel,
on the waters' edge in Long Beach, California, USA, October 4-5, 2001.

--------------------------------------------------------------------------

REGISTRATION AND HOTEL INFORMATION

For information on registration and hotel reservations, please refer to
the MobiHoc 2001 web site at
                               "http://www.cs.ucla.edu/mobihoc/".

*** Important Dates:
                     Early Registration Deadline:     September 13, 2001
                     Special Hotel Rate Cut-off Date: September 12, 2001

--------------------------------------------------------------------------

TRAVEL SUPPORT

Travel support is expected to be available for some attendees.
Please watch the MobiHoc 2001 web site for additional information.

--------------------------------------------------------------------------

TECHNICAL SESSIONS

This year, a large number of technical papers was received, resulting in
a highly selective technical program. The program will include research
paper sessions on routing and transport protocols, link and physical layer
issues, sensor networks, energy management, security issues, testbeds and
applications, Bluetooth, and analysis techniques. It will also include
a number of exciting poster presentations.

*** October 4, Thursday

8:45 - 9:45 Keynote Speech "Wireless Networks: Where is the Beef?"
            by Professor Anthony Ephremides (University of Maryland)

10:15 - 11:30 Session 1: Routing (Chair - Martha Steenstrup)

           "Implicit Source Routing for On-Demand Ad Hoc Network Routing"
            by Yih-Chun Hu (CMU) and David B. Johnson (Rice University)

           "Neighborhood Aware Source Routing"
            by Marcelo Spohn and J.J. Garcia-Luna-Aceves (USUC)

           "Making Link-State Routing Scale for Ad Hoc Networking"
            by Cesar A. Santivanez (BBN), Ram Ramanathan (BBN), and
            Ioannis Stavrakakis (University of Athens)

11:30 - 12:15 Invited Talk
           "Mobile Ad Hoc Networking with Directional Antennas
            for Future Combat Systems", by James A. Freebersyser (DARPA)

1:30 - 2:45 Session 2: Routing and Transport (Chair - Charles Perkins)

           "Adaptive Demand-Driven Multicast Routing in Multi-Hop Wireless
            Ad Hoc Networks", by Jorjeta G. Jetcheva (CMU) and
            David B. Johnson (Rice University)

           "Geometric Spanner for Routing in Mobile Networks"
            by Jie Gao, Leonidas J. Guibas (Stanford University),
            John Hershberger (Mentor Graphics), Li Zhang (Compaq Systems
            Research), An Zhu (Stanford University)

           "A Comparison of TCP Performance over Three Routing Protocols
            for Mobile Ad Hoc Networks", by Thomas D. Dyer and
            Rajendra V. Boppana (University of Texas, San Antonio)

3:15 - 5:00 Session 3: Link and Physical Layer Issues
            (Chair - David B. Johnson)

           "SEEDEX: A MAC Protocol for Ad Hoc Networks"
            by R. Rozovsky and P.R. Kumar (University of Illinois)

           "Medium Access and Radio Resource Management for Ad Hoc Networks
            based on UTRA TDD", by M. Lott, R. Halfmann, E. Schulz
            (Siemens AG), and M. Radimirsch (University of Hannover)

           "Effects of Wireless Physical Layer Modeling in Ad Hoc Networks"
            by Mineo Takai, Jay Martin, and Rajive Bagrodia (UCLA)

           "On the Performance of Ad Hoc Networks with Beamforming
            Antennas" by Ram Ramanathan (BBN Technologies)

5:15 - 6:00 Outrageous Opinions Session
            (Chair - Zygmunt Haas, Cornell University)


*** October 5, Friday

8:00 - 9:30 Poster Session
            (Chair - Joe Macker, Naval Research Lab)

9:45 - 11:30 Session 4: Sensor Networks and Energy Management
            (Chair - Andrew Campbell)

           "Localized Algorithms in Wireless Ad-Hoc Networks:
            Location Discovery and Sensor Exposure", by S. Meguerdichian,
            S. Slijepcevic, V. Karayan, and M. Potkonjak (UCLA)

           "Effects of Power Conservation, Wireless Coverage and
            Cooperation on Data Dissemination among Mobile Devices",
            by M. Papadopouli and H. Schulzrinne (Columbia University)

           "Maximum Flow-Life Curve for a Wireless Ad Hoc Network"
            T.X. Brown, H.N. Gabow, and Qi Zhang (University of Colorado)

           "Birthday Protocols for Low Energy Deployment and Flexible
            Neighbor Discovery in Ad Hoc Wireless Networks",
            M.J. McGlynn and S. A. Borbash (Lab. for Telecomm. Sciences)

1:15 - 3:00 Session 5: Security, Testbeds and Applications
            (Chair - Elizabeth Royer)

           "The Quest for Security in Mobile Ad Hoc Networks"
            by Jean-Pierre Hubaux, Levente Buttyan, and Srdan Capkun
            (Swiss Federal Institute of Technology)

           "Secure Pebblenets"
            by Stefano Basagni, Kris Herrin (University of Texas, Dallas),
            Danilo Bruschi, Emilia Rosti (Universita Degli Studi di Milano)

           "Testbed on a Desktop: Strategies and Techniques to Support
            Multi-hop MANET Routing Protocol Development", by James T. Kaba
            and Douglas R. Raichle (Sarnoff Corporation)

           "Time Synchronization in Ad Hoc Networks"
            by Kay Romer (ETH Zurich)

3:30 - 4:45 Session 6: Bluetooth (Chair - Jason Redi)

           "Performance of a New Bluetooth Scatternet Formation Protocol"
            by Ching Law, Amar K. Mehta, and Kai-Yeung Siu (MIT)

           "A Pseudo Random Coordinated Scheduling Algorithm for Bluetooth
            Scatternets", by Andras Racz, Gyorgy Miklos, Ferenc Kubinszky,
            and Andras Valko (Ericsson Research)

           "JUMP Mode - A Dynamic Window-based Scheduling Framework for
            Bluetooth Scatternets", Niklas Johansson, Fredrik Alriksson,
            and Ulf Jonsson (Ericsson Research)

5:00 - 6:15 Session 7: Analysis Techniques (Chair - Ram Ramanathan)

           "A Probabilistic Analysis for the Range Assignment Problem in
            Ad Hoc Networks", by Paolo Santi (Area della Ricerca del CNR),
            Douglas M. Blough and Feodor Vainstein (Georgia Tech)

           "On Max-min Fairness and Scheduling in Wireless Ad-Hoc Networks:
            Analytical Framework and Implementation", by Xiao Long Huang
            and Brahim Bensaou (Hong Kong University of Science and Tech.)

           "Scenario-Based Stability Analysis of the Distributed
            Mobility-Adaptive Clustering (DMAC) Algorithm",
            C. Bettstetter, R. Krausser (Technische Universitat Muncheon)

-----------------------------------------------------------------------------



OUTRAGEOUS OPINIONS SESSION

Short abstracts (at most 50 words) are solicited for this special session.
An outrageous prize will be awarded to the winner of the most shocking
presentation. Please email your submission to the session chair,
Zygmunt Haas (haas@ece.cornell.edu).

-----------------------------------------------------------------------------


SUPPORTED BY

       TRW and NSF

-----------------------------------------------------------------------------






From owner-mobile-ip@sunroof.eng.sun.com  Mon Sep 10 11:46:35 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19150
	for <mobileip-archive@odin.ietf.org>; Mon, 10 Sep 2001 11:46:34 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA05576;
	Mon, 10 Sep 2001 08:47:38 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id IAA15021;
	Mon, 10 Sep 2001 08:46:28 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8AFie49001682
	for <mobile-ip-dist@sunroof.eng.sun.com>; Mon, 10 Sep 2001 08:44:40 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8AFiers001681
	for mobile-ip-dist; Mon, 10 Sep 2001 08:44:40 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from eastmail2.East.Sun.COM (eastmail2.East.Sun.COM [129.148.1.241])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8AFib49001674
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 10 Sep 2001 08:44:38 -0700 (PDT)
Received: from onion.east.sun.com (onion.East.Sun.COM [129.148.174.110])
	by eastmail2.East.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id LAA08410
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 10 Sep 2001 11:44:51 -0400 (EDT)
Received: (from glass@localhost)
	by onion.east.sun.com (8.9.3+Sun/8.9.3) id LAA25691
	for mobile-ip@sunroof.eng.sun.com; Mon, 10 Sep 2001 11:45:22 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8ACnJ49001290
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 10 Sep 2001 05:49:19 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id FAA24585
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 10 Sep 2001 05:49:34 -0700 (PDT)
Received: from gorilla.mchh.siemens.de (gorilla.mchh.siemens.de [194.138.158.18])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id FAA00914
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 10 Sep 2001 05:49:33 -0700 (PDT)
Received: from blues.mchh.siemens.de (mail2.mchh.siemens.de [194.138.158.227])
	by gorilla.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id OAA09679
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 10 Sep 2001 14:49:01 +0200 (MET DST)
Received: from mchh246e.demchh201e.icn.siemens.de ([139.21.200.56])
	by blues.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id OAA22197
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 10 Sep 2001 14:48:45 +0200 (MET DST)
Received: by MCHH246E with Internet Mail Service (5.5.2653.19)
	id <SMDGX6M7>; Mon, 10 Sep 2001 14:48:02 +0200
Message-ID: <D73559B38D51D4119CB800508B9527B5CE485E@MCHH266E>
From: Gerlich Notker <Notker.Gerlich@icn.siemens.de>
To: "'mobile-ip@sunroof.eng.sun.com'" <mobile-ip@sunroof.eng.sun.com>
Subject: [mobile-ip] MIPv6 BA is response to BU with life time 0
Date: Mon, 10 Sep 2001 14:47:55 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Hi all,

when experimenting with different HA implementations we came upon the problem where to send the BA to in response to a BU with life time zero:
- to the source address of the BU ?
  The CoA may be no longer valid which has been the reason for sendindg the BU.
- the home address ?

We saw both possibilities implemented in different HA implementations.
Should a clarification be added to the draft?

Notker
-------------------------------------------------------------------------------------
Dr. Notker Gerlich                         Siemens AG
                                                     Phone: +49-(0)-89-722-61557
Radio Network Concepts              Fax    : +49-(0)-89-722-55995
ICM N MR ST 10                           mailto:notker.gerlich@icn.siemens.de
-------------------------------------------------------------------------------------
Important Note: This e-mail  may contain trade secrets or privileged, 
undisclosed or otherwise confidential information. If you have received 
this e-mail in error, you are hereby notified that any review, copying or 
distribution of it is strictly prohibited. Please inform us immediately and
 destroy the original transmittal. Thank you for your cooperation.
-------------------------------------------------------------------------------------




From owner-mobile-ip@sunroof.eng.sun.com  Mon Sep 10 11:48:31 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19209
	for <mobileip-archive@odin.ietf.org>; Mon, 10 Sep 2001 11:48:30 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id JAA02078;
	Mon, 10 Sep 2001 09:49:23 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id IAA15687;
	Mon, 10 Sep 2001 08:49:19 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8AFmN49001720
	for <mobile-ip-dist@sunroof.eng.sun.com>; Mon, 10 Sep 2001 08:48:23 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8AFmMYQ001719
	for mobile-ip-dist; Mon, 10 Sep 2001 08:48:22 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from eastmail1.East.Sun.COM (eastmail1.East.Sun.COM [129.148.1.240])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8AFmK49001712
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 10 Sep 2001 08:48:20 -0700 (PDT)
Received: from onion.east.sun.com (onion.East.Sun.COM [129.148.174.110])
	by eastmail1.East.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id LAA03560
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 10 Sep 2001 11:48:34 -0400 (EDT)
Received: (from glass@localhost)
	by onion.east.sun.com (8.9.3+Sun/8.9.3) id LAA25770
	for mobile-ip@sunroof.eng.sun.com; Mon, 10 Sep 2001 11:49:04 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8ADVg49001326
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 10 Sep 2001 06:31:42 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id GAA19367
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 10 Sep 2001 06:31:56 -0700 (PDT)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id GAA18249
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 10 Sep 2001 06:31:55 -0700 (PDT)
Received: from esealnt406.al.sw.ericsson.se (ESEALNT406.al.sw.ericsson.se [153.88.251.29])
	by penguin.wise.edt.ericsson.se (8.11.0/8.10.1/WIREfire-1.3) with SMTP id f8ADVsv27312
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 10 Sep 2001 15:31:54 +0200 (MEST)
Received: FROM esealnt746.al.sw.ericsson.se BY esealnt406.al.sw.ericsson.se ; Mon Sep 10 15:31:52 2001 +0200
Received: by ESEALNT746.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <NB0M2STX>; Mon, 10 Sep 2001 15:31:44 +0200
Message-ID: <F7709E7648BAD41181E60008C716A22901059018@edkchnt102.lmd.ericsson.se>
From: "Peter Grimstrup (TED)" <Peter.Grimstrup@lmd.ericsson.se>
To: "'Charles E. Perkins'" <charliep@iprg.nokia.com>
Cc: mobile-ip@sunroof.eng.sun.com
Subject: RE: [mobile-ip] Coexistence with other uses for routing header
Date: Mon, 10 Sep 2001 15:33:34 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Hi Charlie,

Some pieces of text for your consideration:

Peter

Charles E. Perkins wrote:
> 
> > Further I suggest changing section "8.9 Sending Packets to 
> a Mobile Node"
> > in a way that the next example will be described/allowed:
> > 
> > IPv6 Hdr:      source
> >                intermediate-dest-1
> > RH(4 entries): intermediate-dest-2
> >                CoA
> >                MN-HoA
> 
> No problem; can you suggest some text?

I think I prefer adding a small paragraph - the original contains the
mostly used instance:

8.9. Sending Packets to a Mobile Node

   ...
   entry.  For example, assuming use of a Type 0 Routing header [6], if
   no other use of a Routing header is involved in the routing of this
   packet, the mobile node sets the fields in the packet's IPv6 header
   and Routing header as follows:

    -  The Destination Address in the packet's IPv6 header is set to
       the mobile node's care-of address copied from the Binding Cache
       entry.

    -  The Routing header is initialized to contain a single route
       segment, with an Address of the mobile node's home address (the
       original destination address to which the packet was being sent).

   If a Type 0 Routing Header [6] is used (for some other reason than
   mobility), the Home Address of the Mobile Node will be the last entry
   immediately preceded by the Care-of Address of the Mobile Node.

   Following the definition of a Type 0 Routing header [6], this packet
   ...


For the sake of completeness, I suggest a (new) section:

(8.10. Combining Binding Cache Entries and a Type 0 Routing Header)

   If a node for some reason not specified in section 8.9 is using a
   Type 0 Routing Header, the list of addresses found in the routing
   header including the first address found in the IPv6 header SHOULD be
   matched against the content of the Binding Cache. If match(es) are
   found, the appropriate Care-of Address SHOULD be inserted immediately
   before the matching address, thus expanding the Routing Header as
   needed.


Shouldn't section "10.3. Receiving Packets While Away from Home"
have a new subsection (before last subsection) something like:

   If the home address is not the last segment of the routing header,
   i.e. this node is just an intermediate on the path to the final
   destination, the usual processing of the routing header SHOULD be
   executed, which will result in the packet being forwarded to the next
   (intermediate) destination.


From owner-mobile-ip@sunroof.eng.sun.com  Mon Sep 10 12:39:54 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21721
	for <mobileip-archive@odin.ietf.org>; Mon, 10 Sep 2001 12:39:53 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id JAA04455;
	Mon, 10 Sep 2001 09:40:50 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA03668;
	Mon, 10 Sep 2001 09:13:46 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8AGBh49001871
	for <mobile-ip-dist@sunroof.eng.sun.com>; Mon, 10 Sep 2001 09:11:43 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8AGBgcD001870
	for mobile-ip-dist; Mon, 10 Sep 2001 09:11:42 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from eastmail1.East.Sun.COM (eastmail1.East.Sun.COM [129.148.1.240])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8AGBe49001863
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 10 Sep 2001 09:11:40 -0700 (PDT)
Received: from onion.east.sun.com (onion.East.Sun.COM [129.148.174.110])
	by eastmail1.East.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id MAA09212
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 10 Sep 2001 12:11:53 -0400 (EDT)
Received: (from glass@localhost)
	by onion.east.sun.com (8.9.3+Sun/8.9.3) id MAA26163
	for mobile-ip@sunroof.eng.sun.com; Mon, 10 Sep 2001 12:12:24 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8AFU949001654
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 10 Sep 2001 08:30:09 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id IAA10000
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 10 Sep 2001 08:30:22 -0700 (PDT)
Received: from Eng.Auburn.EDU (dns.eng.auburn.edu [131.204.10.13])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id IAA13010
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 10 Sep 2001 08:30:16 -0700 (PDT)
Received: from hornet.eng.auburn.edu (IDENT:17991@hornet.eng.auburn.edu [131.204.11.14])
	by Eng.Auburn.EDU (8.9.3/8.9.3) with ESMTP id KAA21667;
	Mon, 10 Sep 2001 10:29:52 -0500 (CDT)
Received: from localhost (gibboda@localhost) by hornet.eng.auburn.edu (8.9.3+Sun/8.6.4) with ESMTP id KAA00327; Mon, 10 Sep 2001 10:29:48 -0500 (CDT)
X-Authentication-Warning: hornet.eng.auburn.edu: gibboda owned process doing -bs
Date: Mon, 10 Sep 2001 10:29:48 -0500 (CDT)
From: Dona A Gibbons <gibboda@eng.auburn.edu>
To: mobile-ip@sunroof.eng.sun.com, Phil Roberts <proberts@megisto.com>,
        Basavaraj Patil <basavaraj.patil@nokia.com>,
        Rob Coltun <rcoltun@redback.com>, Abha Ahuja <ahuja@wibh.net>
Subject: [mobile-ip] MOBILE IP TECHNOLOGY
Message-ID: <Pine.SOL.4.10.10109101017400.226-100000@hornet.eng.auburn.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

I am a student working on trying to understand what Mobile IP is.  I found
a lot of technical data, but this information does not really answer the
question I have about Mobile IP Technology.  I am not concern with the
technical side right not just trying to get a picture of Mobile IP.
Listed below is the questions I am seeking to answer and where to find
these answers.

What is Mobile IP?
Where did Mobile IP evolved from?
What is drive the need for Mobile IP?
What are the advantages and disadvantages of Mobile IP?
What progress has been made?
What challenges Mobile IP has to overcome?
Who is working on or behind Mobile IP?
What is the future of Mobile IP?
What applications will be using Mobile IP or developing Mobile IP?

My goal is to understand Mobile IP Technology and to give a Technology
Presentation for a class.  I am not concern about the technical side just
yet which may be use at later date.  Just looking for the Technology side
and understand the Technology.

Thank you for your time and help.
Have a great day.

Sincerely,

Mr. Dona A.C. Gibbons
HomePage - http://www.eng.auburn.edu/~gibboda
Music Playground Project - http://www.auburn.edu/~gibboda



From owner-mobile-ip@sunroof.eng.sun.com  Mon Sep 10 15:33:30 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28308
	for <mobileip-archive@odin.ietf.org>; Mon, 10 Sep 2001 15:33:29 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id NAA19884;
	Mon, 10 Sep 2001 13:34:30 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id MAA13155;
	Mon, 10 Sep 2001 12:34:24 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8AJW249002189
	for <mobile-ip-dist@sunroof.eng.sun.com>; Mon, 10 Sep 2001 12:32:02 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8AJW26u002188
	for mobile-ip-dist; Mon, 10 Sep 2001 12:32:02 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8AJVx49002181
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 10 Sep 2001 12:31:59 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id MAA11127
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 10 Sep 2001 12:32:13 -0700 (PDT)
Received: from idcpa4.pa.interdigital.com ([12.32.197.142])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id NAA18255
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 10 Sep 2001 13:32:08 -0600 (MDT)
Received: by idcpa4.pa.interdigital.com with Internet Mail Service (5.5.2653.19)
	id <RN09VXVC>; Mon, 10 Sep 2001 15:31:15 -0400
Message-ID: <A1170612471BD21185B90008C7FA0A0D01F1FA3A@idcpa4.pa.interdigital.com>
From: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
To: "'mobile-ip@sunroof.eng.sun.com'" <mobile-ip@sunroof.eng.sun.com>
Subject: RE: [mobile-ip] Commercial deployment o Mobile IP
Date: Mon, 10 Sep 2001 15:31:09 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>


Hi,

	I was wondering if there were anyone deploying Mobile Internet
protocols commercially or as an experimental system. I am interested in
hardware/software platforms for Mobile Internet. I am interested in the
protocols developed by this WG, Mobile IPv4 and IPv6, and also in
prepriotory solutions. 

I would be interested in some off-line discussions with people in this area.
Thnaks.

-Sharif.


From owner-mobile-ip@sunroof.eng.sun.com  Mon Sep 10 15:40:54 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28572
	for <mobileip-archive@odin.ietf.org>; Mon, 10 Sep 2001 15:40:54 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id NAA25313;
	Mon, 10 Sep 2001 13:41:59 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id MAA15302;
	Mon, 10 Sep 2001 12:41:57 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8AJf049002253
	for <mobile-ip-dist@sunroof.eng.sun.com>; Mon, 10 Sep 2001 12:41:01 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8AJf0na002252
	for mobile-ip-dist; Mon, 10 Sep 2001 12:41:00 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from jurassic.eng.sun.com (jurassic [129.146.89.50] (may be forged))
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8AJev49002245
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 10 Sep 2001 12:40:57 -0700 (PDT)
Received: from istanbul.Eng.Sun.COM (istanbul.Eng.Sun.COM [129.146.86.247])
	by jurassic.eng.sun.com (8.12.0+Sun/8.12.0) with SMTP id f8AJfB9n228598
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 10 Sep 2001 12:41:11 -0700 (PDT)
Message-Id: <200109101941.f8AJfB9n228598@jurassic.eng.sun.com>
Date: Mon, 10 Sep 2001 12:41:09 -0700 (PDT)
From: Alper Yegin <Alper.Yegin@eng.sun.com>
Subject: Re: [mobile-ip] Mobile IPv6 draft revision
To: mobile-ip@sunroof.eng.sun.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: FAwdHq7AF0hsxvUUwE8DFw==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4_37 SunOS 5.8.1 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

This issue was included in the Conenctathon 2001 list:

 [5] Deregistering a care-of address (section 8.5)
 
 The draft says that binding acknowledgement MUST be sent using a routing
 header in the same way as any other packet sent to a mobile node using a
 care-of address.
 
 BUT, what should be the care-of address used in the case this was a
 deregistration? Draft should specify that it MUST be the care-of address
 used in the triggering binding update. (similarly, draft already specifies
 that for failed binding updates case).

MN should put wherever it wants to receive the BAck as the CoA in this 
de-registration BU.

alper



> X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to 
owner-mobile-ip@sunroof.eng.sun.com using -f
> X-Accept-Language: en
> MIME-Version: 1.0
> To: mobile-ip@sunroof.eng.sun.com
> Subject: Re: [mobile-ip] Mobile IPv6 draft revision
> Content-Transfer-Encoding: 7bit
> List-Archive: <http://playground.sun.com/mobile-ip/>
> List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
> List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
> List-Unsubscribe: 
<mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
> 
> Comments inline
> 
> Peter
> 
> Parijat wrote:
> > 
> > That does not answer the basic question that a BA might be addressed to a 
CoA
> > which is no longer valid.
> > 
> 
> Well, if a MN send the deregistration from a Care-of Address it does
> not want to use (any more) asking for an acknowledgement, it should
> reasonably stay there for some minimum of time. Leaving before the BA
> is received is OK though, the MN may wish to retransmit the deregistration
> from its new location - but with the interpretation from Marc Hassons mail
> (7 sep, 18:31) that will be OK as well.
> 
> > I would suggest that cache deletion requests come in with zero lifetimes,
> > (perhaps even in case (a)?), and the acknowledgements to _deletion_ requests
> > be sent to the home address of the mobile node.
> 
> But maybe the MN just wants to stay away in privacy for some time for some
> reason - that happens, I guess. I think Marc's proposal will work.
> 
> > 
> > Of course, I am assuming that there is some need to keep a conceptual,
> > specific difference between binding cache deletion requests and binding
> > updates which merely have a very short lifetime.  It seems to be a neat 
thing
> > to have a separate binding deletion message rather than one which is a
> > degenerate case of a normal BU (okay, okay, zero lifetime BUs _are_
> > degenerate cases of normal BUs, but you know what I mean).
> > 
> Actually a nice idea, but...
> > --
> > Parijat Mishra
> > R & D Engineer,
> > Centre for Wireless Communications, NUS
> > Tel: (65)8709353

alper



From owner-mobile-ip@sunroof.eng.sun.com  Mon Sep 10 15:41:46 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28646
	for <mobileip-archive@odin.ietf.org>; Mon, 10 Sep 2001 15:41:46 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id NAA26141;
	Mon, 10 Sep 2001 13:42:54 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id MAA15529;
	Mon, 10 Sep 2001 12:42:52 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8AJfk49002270
	for <mobile-ip-dist@sunroof.eng.sun.com>; Mon, 10 Sep 2001 12:41:46 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8AJfkHl002269
	for mobile-ip-dist; Mon, 10 Sep 2001 12:41:46 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from jurassic.eng.sun.com (jurassic [129.146.89.50] (may be forged))
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8AJfg49002262
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 10 Sep 2001 12:41:42 -0700 (PDT)
Received: from istanbul.Eng.Sun.COM (istanbul.Eng.Sun.COM [129.146.86.247])
	by jurassic.eng.sun.com (8.12.0+Sun/8.12.0) with SMTP id f8AJfv9n228663
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 10 Sep 2001 12:41:57 -0700 (PDT)
Message-Id: <200109101941.f8AJfv9n228663@jurassic.eng.sun.com>
Date: Mon, 10 Sep 2001 12:41:55 -0700 (PDT)
From: Alper Yegin <Alper.Yegin@eng.sun.com>
Subject: Re: [mobile-ip] MIPv6 BA is response to BU with life time 0
To: mobile-ip@sunroof.eng.sun.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: v0oHvOSiBSzBBzdGdyvLwQ==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4_37 SunOS 5.8.1 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Please see the thread "[mobile-ip] Mobile IPv6 draft revision".  This is the 
latest discussion on that thread.

alper


> X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to 
owner-mobile-ip@sunroof.eng.sun.com using -f
> To: "'mobile-ip@sunroof.eng.sun.com'" <mobile-ip@sunroof.eng.sun.com>
> Subject: [mobile-ip] MIPv6 BA is response to BU with life time 0
> MIME-Version: 1.0
> List-Archive: <http://playground.sun.com/mobile-ip/>
> List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
> List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
> List-Unsubscribe: 
<mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
> 
> Hi all,
> 
> when experimenting with different HA implementations we came upon the problem 
where to send the BA to in response to a BU with life time zero:
> - to the source address of the BU ?
>   The CoA may be no longer valid which has been the reason for sendindg the 
BU.
> - the home address ?
> 
> We saw both possibilities implemented in different HA implementations.
> Should a clarification be added to the draft?
> 
> Notker
> 
--------------------------------------------------------------------------------
-----
> Dr. Notker Gerlich                         Siemens AG
>                                                      Phone: 
+49-(0)-89-722-61557
> Radio Network Concepts              Fax    : +49-(0)-89-722-55995
> ICM N MR ST 10                           mailto:notker.gerlich@icn.siemens.de
> 
--------------------------------------------------------------------------------
-----
> Important Note: This e-mail  may contain trade secrets or privileged, 
> undisclosed or otherwise confidential information. If you have received 
> this e-mail in error, you are hereby notified that any review, copying or 
> distribution of it is strictly prohibited. Please inform us immediately and
>  destroy the original transmittal. Thank you for your cooperation.
> 
--------------------------------------------------------------------------------
-----
> 

alper



From owner-mobile-ip@sunroof.eng.sun.com  Mon Sep 10 16:07:05 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA29525
	for <mobileip-archive@odin.ietf.org>; Mon, 10 Sep 2001 16:07:05 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id OAA15233;
	Mon, 10 Sep 2001 14:08:01 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id NAA19085;
	Mon, 10 Sep 2001 13:07:58 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8AK4S49002376
	for <mobile-ip-dist@sunroof.eng.sun.com>; Mon, 10 Sep 2001 13:04:28 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8AK4S7B002375
	for mobile-ip-dist; Mon, 10 Sep 2001 13:04:28 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8AK4O49002368
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 10 Sep 2001 13:04:25 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id NAA18573
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 10 Sep 2001 13:04:39 -0700 (PDT)
Received: from hoemail2.firewall.lucent.com (hoemail2.lucent.com [192.11.226.163])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id OAA20977
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 10 Sep 2001 14:05:17 -0600 (MDT)
Received: from il0015exch001h.wins.lucent.com (h135-1-23-83.lucent.com [135.1.23.83])
	by hoemail2.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id f8AK4aC28578
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 10 Sep 2001 16:04:36 -0400 (EDT)
Received: by IL0015EXCH001H with Internet Mail Service (5.5.2650.21)
	id <SK1XGNA6>; Mon, 10 Sep 2001 15:04:36 -0500
Message-ID: <DFEDFA513370D31192020090279CCF1806749701@il0015exch008u.ih.lucent.com>
From: "Dolan, Michael F (Mike)" <mfdolan@lucent.com>
To: mobile-ip@sunroof.eng.sun.com
Subject: RE: [mobile-ip] Commercial deployment o Mobile IP
Date: Mon, 10 Sep 2001 15:04:31 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

I believe that the Nextel wireless system in the U.S. is based on Mobile
IPv4.

Mike Dolan


-----Original Message-----
From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
Sent: Monday, September 10, 2001 2:31 PM
To: 'mobile-ip@sunroof.eng.sun.com'
Subject: RE: [mobile-ip] Commercial deployment o Mobile IP



Hi,

	I was wondering if there were anyone deploying Mobile Internet
protocols commercially or as an experimental system. I am interested in
hardware/software platforms for Mobile Internet. I am interested in the
protocols developed by this WG, Mobile IPv4 and IPv6, and also in
prepriotory solutions. 

I would be interested in some off-line discussions with people in this area.
Thnaks.

-Sharif.


From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep 11 05:06:37 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA00957
	for <mobileip-archive@odin.ietf.org>; Tue, 11 Sep 2001 05:06:36 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id CAA05200;
	Tue, 11 Sep 2001 02:06:25 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id CAA11310;
	Tue, 11 Sep 2001 02:06:14 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8B94F49003186
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 11 Sep 2001 02:04:15 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8B94Fqm003185
	for mobile-ip-dist; Tue, 11 Sep 2001 02:04:15 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8B94B49003178
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 11 Sep 2001 02:04:11 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id CAA23751
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 11 Sep 2001 02:04:27 -0700 (PDT)
Received: from mx0.gmx.net (mx0.gmx.net [213.165.64.100])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with SMTP id CAA23668
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 11 Sep 2001 02:04:26 -0700 (PDT)
Received: (qmail 27932 invoked by uid 0); 11 Sep 2001 09:04:25 -0000
Date: Tue, 11 Sep 2001 11:04:25 +0200 (MEST)
From: cn yap <cnyap@gmx.net>
To: Sharif.Shahrier@InterDigital.com
Cc: mobile-ip@sunroof.eng.sun.com
MIME-Version: 1.0
Subject: RE: [mobile-ip] Commercial deployment o Mobile IP
X-Authenticated-Sender: #0011436637@gmx.net
X-Authenticated-IP: [212.218.174.122]
Message-ID: <3540.1000199065@www18.gmx.net>
X-Mailer: WWW-Mail 1.5 (Global Message Exchange)
X-Flags: 0001
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hi,

There is about 6 companies developing mobile IP.
There are also about 6 companies developing 
proprietary solutions, that is not compatible with
mobile IP. :)

Still the biggest killer is GRX

There are some other methods to resolve mobility issues
depend how you see it.
Cheers
Chern Nam Yap



>Hi,

>	I was wondering if there were anyone deploying Mobile Internet
>protocols commercially or as an experimental system. I am interested in
>hardware/software platforms for Mobile Internet. I am interested in the
>protocols developed by this WG, Mobile IPv4 and IPv6, and also in
>prepriotory solutions. 

>I would be interested in some off-line discussions with people in this
>area.
>Thnaks.

-Sharif.

-- 
Sent through GMX FreeMail - http://www.gmx.net



From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep 11 06:55:50 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA02598
	for <mobileip-archive@odin.ietf.org>; Tue, 11 Sep 2001 06:55:50 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id DAA04888;
	Tue, 11 Sep 2001 03:55:24 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id DAA19886;
	Tue, 11 Sep 2001 03:55:17 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8BArR49003378
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 11 Sep 2001 03:53:27 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8BArR45003377
	for mobile-ip-dist; Tue, 11 Sep 2001 03:53:27 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8BArN49003370
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 11 Sep 2001 03:53:23 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id DAA02780
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 11 Sep 2001 03:53:41 -0700 (PDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id EAA29241
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 11 Sep 2001 04:53:36 -0600 (MDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA02524;
	Tue, 11 Sep 2001 06:53:38 -0400 (EDT)
Message-Id: <200109111053.GAA02524@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
CC: mobile-ip@sunroof.eng.sun.com
From: Internet-Drafts@ietf.org
Subject: [mobile-ip] I-D ACTION:draft-kempf-beth-ipv6-02.txt
Date: Tue, 11 Sep 2001 06:53:37 -0400
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.


	Title		: Bidirectional Edge Tunnel Handover for IPv6
	Author(s)	: J. Kempf et al.
	Filename	: draft-kempf-beth-ipv6-02.txt
	Pages		: 27
	Date		: 10-Sep-01
	
This document discusses an extension to the Fast Mobile IPv6 
handover protocol described in draft-ietf-mobileip-fastmipv6-01.txt 
that reduces the amount of L3 latency in Mobile IPv6 handover to 
zero.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-kempf-beth-ipv6-02.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-kempf-beth-ipv6-02.txt".

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


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

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-kempf-beth-ipv6-02.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-kempf-beth-ipv6-02.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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

--OtherAccess--

--NextPart--




From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep 11 16:53:33 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA18668
	for <mobileip-archive@odin.ietf.org>; Tue, 11 Sep 2001 16:53:33 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id OAA26684;
	Tue, 11 Sep 2001 14:53:00 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id NAA27815;
	Tue, 11 Sep 2001 13:52:41 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8BKoq49004015
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 11 Sep 2001 13:50:52 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8BKoqLX004014
	for mobile-ip-dist; Tue, 11 Sep 2001 13:50:52 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8BKoi49004007
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 11 Sep 2001 13:50:44 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id NAA11562
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 11 Sep 2001 13:51:02 -0700 (PDT)
Received: from mail.gmx.net (mail.gmx.net [213.165.64.20])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with SMTP id NAA09043
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 11 Sep 2001 13:51:01 -0700 (PDT)
Received: (qmail 11809 invoked by uid 0); 11 Sep 2001 20:51:00 -0000
Received: from pd9522a7c.dip.t-dialin.net (HELO borg) (217.82.42.124)
  by mail.gmx.net (mp002-rz3) with SMTP; 11 Sep 2001 20:51:00 -0000
Message-ID: <000801c13b04$972cfb20$a664fea9@borg>
From: "cnyap" <cnyap@gmx.net>
To: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
Cc: <mobile-ip@sunroof.eng.sun.com>
References: <A1170612471BD21185B90008C7FA0A0D01F1FA3F@idcpa4.pa.interdigital.com>
Subject: Re: [mobile-ip] Commercial deployment o Mobile IP
Date: Tue, 11 Sep 2001 22:59:02 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hi Sharif

The companies are:
Cisco, IPunpluggd, NetSeal, BirdStep, Nextel, Sprint.

Some Information for GRX.
http://www.gsmworld.com/technology/gprs_grx_prov.html
3GPP Document.
http://www.3gpp.org/ftp/tsg_sa/WG3_Security/2000_meetings/TSGS3_15bis_Munich
/Docs/PDF/S3z000005.pdf

Cheers
Chern Nam Yap


----- Original Message -----
From: "Shahrier, Sharif M." <Sharif.Shahrier@InterDigital.com>
To: "'cn yap'" <cnyap@gmx.net>
Sent: Tuesday, September 11, 2001 5:44 PM
Subject: RE: [mobile-ip] Commercial deployment o Mobile IP


> Hi Chern,
>
> Do you have the names and web sites of these companies?
>
> Also, I am interested in finding out more about GRX. Do you have the
> 3GPP document number?
>
> -Sharif.
>
> -----Original Message-----
> From: cn yap [mailto:cnyap@gmx.net]
> Sent: Tuesday, September 11, 2001 5:04 AM
> To: Sharif.Shahrier@InterDigital.com
> Cc: mobile-ip@sunroof.eng.sun.com
> Subject: RE: [mobile-ip] Commercial deployment o Mobile IP
>
>
> Hi,
>
> There is about 6 companies developing mobile IP.
> There are also about 6 companies developing
> proprietary solutions, that is not compatible with
> mobile IP. :)
>
> Still the biggest killer is GRX
>
> There are some other methods to resolve mobility issues
> depend how you see it.
> Cheers
> Chern Nam Yap
>
>
>
> >Hi,
>
> > I was wondering if there were anyone deploying Mobile Internet
> >protocols commercially or as an experimental system. I am interested in
> >hardware/software platforms for Mobile Internet. I am interested in the
> >protocols developed by this WG, Mobile IPv4 and IPv6, and also in
> >prepriotory solutions.
>
> >I would be interested in some off-line discussions with people in this
> >area.
> >Thnaks.
>
> -Sharif.
>
> --
> Sent through GMX FreeMail - http://www.gmx.net
>



From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep 12 06:56:04 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA16884
	for <mobileip-archive@odin.ietf.org>; Wed, 12 Sep 2001 06:56:03 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id DAA25305;
	Wed, 12 Sep 2001 03:55:42 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id DAA08834;
	Wed, 12 Sep 2001 03:55:32 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8CAs749004744
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 12 Sep 2001 03:54:07 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8CAs77M004743
	for mobile-ip-dist; Wed, 12 Sep 2001 03:54:07 -0700 (PDT)
Date: Wed, 12 Sep 2001 03:54:07 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8CAs449004736
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 12 Sep 2001 03:54:04 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id DAA04291
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 12 Sep 2001 03:54:23 -0700 (PDT)
Received: from telesoft.indts.com ([164.164.71.52])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id EAA00186
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 12 Sep 2001 04:54:14 -0600 (MDT)
Received: from indts_fs.indts.com (indts_fs [201.64.64.29])
	by telesoft.indts.com (8.8.7/8.8.7) with ESMTP id QAA03808
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 12 Sep 2001 16:53:21 +0530
Received: by INDTS_FS with Internet Mail Service (5.5.2650.21)
	id <QSWBNJYT>; Wed, 12 Sep 2001 16:38:04 +0530
Message-ID: <F73B646FCC01D5118F530002B32C33724C6F53@INDTS_FS>
From: Amit Shakya <amits@indts.com>
To: "'mobile-ip@sunroof.eng.sun.com'" <mobile-ip@sunroof.eng.sun.com>
Subject: [mobile-ip] Date: Wed, 12 Sep 2001 16:37:57 +0530
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Hi,
I have a doubt regrading the processing of packets received from HA by FA.
If the FA receives the PDU's before the Registration Reply is received, what
policy should the FA follow for those packets ? Since the communication is
over UDP, this scenario is possible, so what could be the right approach for
handling this ?
Regards
Amit


From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep 12 07:11:04 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA17157
	for <mobileip-archive@odin.ietf.org>; Wed, 12 Sep 2001 07:11:04 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id EAA29738;
	Wed, 12 Sep 2001 04:10:40 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id EAA10311;
	Wed, 12 Sep 2001 04:10:30 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8CB9549004793
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 12 Sep 2001 04:09:05 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8CB94aE004792
	for mobile-ip-dist; Wed, 12 Sep 2001 04:09:04 -0700 (PDT)
Date: Wed, 12 Sep 2001 04:09:04 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8CB9149004785
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 12 Sep 2001 04:09:01 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id EAA22565
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 12 Sep 2001 04:09:21 -0700 (PDT)
Received: from telesoft.indts.com ([164.164.71.52])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id FAA06795
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 12 Sep 2001 05:09:04 -0600 (MDT)
Received: from indts_fs.indts.com (indts_fs [201.64.64.29])
	by telesoft.indts.com (8.8.7/8.8.7) with ESMTP id RAA09335
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 12 Sep 2001 17:08:11 +0530
Received: by INDTS_FS with Internet Mail Service (5.5.2650.21)
	id <QSWBNJ5L>; Wed, 12 Sep 2001 16:52:54 +0530
Message-ID: <F73B646FCC01D5118F530002B32C33724C6F54@INDTS_FS>
From: Amit Shakya <amits@indts.com>
To: "'mobile-ip@sunroof.eng.sun.com'" <mobile-ip@sunroof.eng.sun.com>
Subject: [mobile-ip] Date: Wed, 12 Sep 2001 16:52:44 +0530
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Hi 
This is in continuation to the previous mail i.e
----
Hi,
I have a doubt regrading the processing of packets received from HA by FA.
If the FA receives the PDU's before the Registration Reply is received, what
policy should the FA follow for those packets ? Since the communication is
over UDP, this scenario is possible, so what could be the right approach for
handling this ?

-----

Now since the PDU's are received by FA that means the Registration is
successful, so can the FA start forwarding the PDU's without actually
waiting for the Registration Reply?

Regards
Amit


From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep 12 09:01:48 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20590
	for <mobileip-archive@odin.ietf.org>; Wed, 12 Sep 2001 09:01:47 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id GAA29017;
	Wed, 12 Sep 2001 06:01:09 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id GAA02716;
	Wed, 12 Sep 2001 06:01:00 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8CCxh49004900
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 12 Sep 2001 05:59:43 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8CCxh86004899
	for mobile-ip-dist; Wed, 12 Sep 2001 05:59:43 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8CCxd49004892
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 12 Sep 2001 05:59:39 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id FAA19839
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 12 Sep 2001 06:00:00 -0700 (PDT)
Received: from atlsnmx1.nextel.com (nat-167-20.nextel.com [168.73.245.70])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id GAA26743
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 12 Sep 2001 06:59:55 -0600 (MDT)
Received: from atlntgw02.nextel.com (atlntgw02.nextel.com [10.8.79.186])
	by atlsnmx1.nextel.com (8.8.8+Sun/8.8.6) with ESMTP id IAA04365
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 12 Sep 2001 08:59:58 -0400 (EDT)
Received: by atlntgw02.nextel.com with Internet Mail Service (5.5.2650.21)
	id <RZQT6ZGA>; Wed, 12 Sep 2001 09:00:08 -0400
Message-ID: <D456C897C3DBD311816F0008C716D05107BBC0A7@NHQNTEX02.nextel.com>
From: "Bui, Hung" <Hung.Bui@Nextel.com>
To: "'mobile-ip@sunroof.eng.sun.com'" <mobile-ip@sunroof.eng.sun.com>
Subject: RE: [mobile-ip] Commercial deployment o Mobile IP
Date: Wed, 12 Sep 2001 09:02:03 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Dear Sharif,

I am working for Nextel Communications, Inc.  I joined Nextel last month.

Today, Nextel is actually deploying Mobile IP.  We have over 2 millions
mobile IP node subscribers.

Please let me know should you have any questions on commercial mobile IP
system.  As I am new here, I may not have all the answers for you.

Regards,
Hung

______________________________________
Hung Bui
Sr. Manager
Technology Development
NEXTEL Communications, Inc.
? desk: 703-433 8111
? mobile: 703-932 9895
? email: hung.bui@nextel.com
? text messaging: 7039329895@messaging.nextel.com
______________________________________

-----Original Message-----
From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
Sent: Monday, September 10, 2001 3:31 PM
To: 'mobile-ip@sunroof.eng.sun.com'
Subject: RE: [mobile-ip] Commercial deployment o Mobile IP


Hi,

        I was wondering if there were anyone deploying Mobile Internet
protocols commercially or as an experimental system. I am interested in
hardware/software platforms for Mobile Internet. I am interested in the
protocols developed by this WG, Mobile IPv4 and IPv6, and also in
prepriotory solutions.

I would be interested in some off-line discussions with people in this area.
Thnaks.

-Sharif.


From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep 12 19:31:49 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05427
	for <mobileip-archive@odin.ietf.org>; Wed, 12 Sep 2001 19:31:48 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id RAA06715;
	Wed, 12 Sep 2001 17:31:26 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id QAA12621;
	Wed, 12 Sep 2001 16:31:11 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8CNTU49005374
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 12 Sep 2001 16:29:30 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8CNTUOt005373
	for mobile-ip-dist; Wed, 12 Sep 2001 16:29:30 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8CNTQ49005366
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 12 Sep 2001 16:29:26 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id QAA28064
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 12 Sep 2001 16:29:47 -0700 (PDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id QAA26254
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 12 Sep 2001 16:29:46 -0700 (PDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id QAA24567
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 12 Sep 2001 16:29:46 -0700 (PDT)
X-Delivered-For: <mobile-ip@sunroof.eng.sun.com>
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f8CNTjg24575
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 12 Sep 2001 16:29:45 -0700
X-mProtect:  Wed, 12 Sep 2001 16:29:45 -0700 Nokia Silicon Valley Messaging Protection
Received: from rajeev.iprg.nokia.com (205.226.2.90, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpd9J40pd; Wed, 12 Sep 2001 16:29:44 PDT
Message-ID: <3B9FEFE7.28CC7C2E@iprg.nokia.com>
Date: Wed, 12 Sep 2001 16:29:43 -0700
From: Rajeev Koodli <rajeev@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] New BETH Draft
References: <200109072206.PAA17773@heliopolis.eng.sun.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hello James,


> As agreed upon in London, unless there are any further changes needed,
> I'd like to move forward with Gopal on incorporating the draft
> into the body of draft-ietf-mobileip-fast-mipv6-02.txt.
>

I have some concerns with this. As I understand, please correct me if I am
wrong, BETH
relies on link-layer triggers to establish the bi-directional tunnel. The
link-layer triggers are

- not standarized. Who will do the standardization ?
- not implemented (I guess since there is no standard). Any comments ?

Given this dependence, having BETH as a part of FMIPv6 raises the following
issues

- how can we implement FMIPv6 with BETH ?
- how can we test inter-operability ?

So, I feel that FMIPv6 should contain enough specification that can become a
standard without depending on link-layer trigger standardization to succeed. We
are keen on moving FMIPv6 along, and would welcome new ideas that would improve
the protocol. However, items that would require standardization of their own
should perhaps be part of a separate document, and (still) be recognized in the
FMIPv6 specification.

Comments ?


Regards,

-Rajeev




>
>                 jak



From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep 12 22:31:07 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA09473
	for <mobileip-archive@lists.ietf.org>; Wed, 12 Sep 2001 22:31:06 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id TAA23565;
	Wed, 12 Sep 2001 19:30:40 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id TAA16815;
	Wed, 12 Sep 2001 19:29:13 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8D2S549005524
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 12 Sep 2001 19:28:05 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8D2S5G1005523
	for mobile-ip-dist; Wed, 12 Sep 2001 19:28:05 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8D2S149005516
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 12 Sep 2001 19:28:01 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id TAA12899
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 12 Sep 2001 19:28:23 -0700 (PDT)
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with SMTP id UAA28709
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 12 Sep 2001 20:29:05 -0600 (MDT)
Received: (qmail 29599 invoked by uid 500); 13 Sep 2001 02:14:59 -0000
Date: Wed, 12 Sep 2001 19:14:59 -0700
From: Pat Calhoun <pcalhoun@diameter.org>
To: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] New BETH Draft
Message-ID: <20010912191459.A29588@charizard.diameter.org>
References: <200109072206.PAA17773@heliopolis.eng.sun.com> <3B9FEFE7.28CC7C2E@iprg.nokia.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <3B9FEFE7.28CC7C2E@iprg.nokia.com>; from rajeev@iprg.nokia.com on Wed, Sep 12, 2001 at 04:29:43PM -0700
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

> I have some concerns with this. As I understand, please correct me if I am
> wrong, BETH
> relies on link-layer triggers to establish the bi-directional tunnel. The
> link-layer triggers are
> 
> - not standarized. Who will do the standardization ?
> - not implemented (I guess since there is no standard). Any comments ?
> 
> Given this dependence, having BETH as a part of FMIPv6 raises the following
> issues
> 
> - how can we implement FMIPv6 with BETH ?
> - how can we test inter-operability ?

Triggers, the link layer and the MIP implementation exist on a single platform.
Therefore, this is implementation specific, and obviously cannot cause any
interoperability issues.

Perhaps I've missed something here,

PatC


From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep 13 04:48:07 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA29321
	for <mobileip-archive@odin.ietf.org>; Thu, 13 Sep 2001 04:48:07 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id CAA01015;
	Thu, 13 Sep 2001 02:45:43 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id BAA00307;
	Thu, 13 Sep 2001 01:45:33 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8D8i249005919
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 13 Sep 2001 01:44:02 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8D8i1HQ005918
	for mobile-ip-dist; Thu, 13 Sep 2001 01:44:01 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8D8hw49005911
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 13 Sep 2001 01:43:58 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id BAA00040
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 13 Sep 2001 01:44:19 -0700 (PDT)
Received: from albatross-ext.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id CAA00133
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 13 Sep 2001 02:44:14 -0600 (MDT)
Received: from esealnt461 (esealnt461.al.sw.ericsson.se [153.88.251.61])
	by albatross.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id f8D8iHK03018
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 13 Sep 2001 10:44:17 +0200 (MEST)
Received: FROM esealnt742.al.sw.ericsson.se BY esealnt461 ; Thu Sep 13 10:44:16 2001 +0200
Received: by esealnt742.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <NBWN5VQ6>; Thu, 13 Sep 2001 10:37:17 +0200
Message-ID: <034BEFD03799D411A59F00508BDF754603008CB3@esealnt448.al.sw.ericsson.se>
From: "Hesham Soliman  (ERA)" <Hesham.Soliman@era.ericsson.se>
To: "'mobile-ip@sunroof.eng.sun.com'" <mobile-ip@sunroof.eng.sun.com>
Subject: RE: [mobile-ip] New BETH Draft
Date: Thu, 13 Sep 2001 10:44:06 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Rajeev, 

Is there any scenario in FMIPv4 or FMIPv6 that does not
rely on triggers? I don't think BETH is unique here. 

Hesham


> > As agreed upon in London, unless there are any further changes needed,
> > I'd like to move forward with Gopal on incorporating the draft
> > into the body of draft-ietf-mobileip-fast-mipv6-02.txt.
> >
> 
> I have some concerns with this. As I understand, please correct me if I am
> wrong, BETH
> relies on link-layer triggers to establish the bi-directional tunnel. The
> link-layer triggers are
> 
> - not standarized. Who will do the standardization ?
> - not implemented (I guess since there is no standard). Any comments ?
> 
> Given this dependence, having BETH as a part of FMIPv6 raises the following
> issues
> 
> - how can we implement FMIPv6 with BETH ?
> - how can we test inter-operability ?
> 
> So, I feel that FMIPv6 should contain enough specification that can become a
> standard without depending on link-layer trigger standardization to succeed. We
> are keen on moving FMIPv6 along, and would welcome new ideas that would improve
> the protocol. However, items that would require standardization of their own
> should perhaps be part of a separate document, and (still) be recognized in the
> FMIPv6 specification.
> 
> Comments ?
> 
> 
> Regards,
> 
> -Rajeev
> 
> 
> 
> 
> >
> >                 jak


From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep 13 09:43:41 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA03439
	for <mobileip-archive@odin.ietf.org>; Thu, 13 Sep 2001 09:43:40 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id HAA04913;
	Thu, 13 Sep 2001 07:42:54 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id GAA05804;
	Thu, 13 Sep 2001 06:42:44 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8DDfP49006238
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 13 Sep 2001 06:41:25 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8DDfPEJ006237
	for mobile-ip-dist; Thu, 13 Sep 2001 06:41:25 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8DDfL49006230
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 13 Sep 2001 06:41:22 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id GAA29000
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 13 Sep 2001 06:41:42 -0700 (PDT)
Received: from adept.qualcomm.com (adept.qualcomm.com [129.46.64.129])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id GAA18613
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 13 Sep 2001 06:41:33 -0700 (PDT)
Received: from jwillkie2.qualcomm.com (vpnap-g1-012017.qualcomm.com [10.13.12.17])
	by adept.qualcomm.com (8.11.3/8.11.3/1.0) with ESMTP id f8DDfVq11003;
	Thu, 13 Sep 2001 06:41:32 -0700 (PDT)
Message-Id: <4.3.1.0.20010913063528.020b72a0@mail1.qualcomm.com>
X-Sender: jwillkie@mail1.qualcomm.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Thu, 13 Sep 2001 06:39:21 -0700
To: mobile-ip@sunroof.eng.sun.com,
        "'mobile-ip@sunroof.eng.sun.com'" <mobile-ip@sunroof.eng.sun.com>
From: Jim Willkie <jwillkie@qualcomm.com>
Subject: RE: [mobile-ip] Commercial deployment o Mobile IP
In-Reply-To: <D456C897C3DBD311816F0008C716D05107BBC0A7@NHQNTEX02.nextel.
 com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

At 09:02 AM 9/12/2001 -0400, Bui, Hung wrote:
>Dear Sharif,
>
>I am working for Nextel Communications, Inc.  I joined Nextel last month.
>
>Today, Nextel is actually deploying Mobile IP.  We have over 2 millions
>mobile IP node subscribers.
>
>Please let me know should you have any questions on commercial mobile IP
>system.  As I am new here, I may not have all the answers for you.

Mr. Hung:
A couple of brief questions regarding the Nextel MobileIP deployment:

1) Is this a packet data deployment? Is it VOIP?

2) I presume this deployment is for a wireless service. Is this correct?

3) Are static IP address assignment used? How about dynamic IP address 
assignments? Do you folks do both?

4) Is this service available in San Diego, Calif?

Thank you, Jim Willkie



From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep 13 12:32:33 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08055
	for <mobileip-archive@odin.ietf.org>; Thu, 13 Sep 2001 12:32:32 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id JAA01157;
	Thu, 13 Sep 2001 09:31:29 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA02347;
	Thu, 13 Sep 2001 09:29:08 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8DGRJ49006781
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 13 Sep 2001 09:27:20 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8DGRJrB006780
	for mobile-ip-dist; Thu, 13 Sep 2001 09:27:19 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from heliopolis.eng.sun.com (redcoast.Eng.Sun.COM [152.70.28.21])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8DGRE49006773
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 13 Sep 2001 09:27:14 -0700 (PDT)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.eng.sun.com (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id JAA00876
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 13 Sep 2001 09:27:35 -0700 (PDT)
Message-Id: <200109131627.JAA00876@heliopolis.eng.sun.com>
Date: Thu, 13 Sep 2001 09:27:34 -0700 (PDT)
From: James Kempf <James.Kempf@Sun.COM>
Subject: Re: [mobile-ip] New BETH Draft
To: mobile-ip@sunroof.eng.sun.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: Se8llfLueAZSyONN8964oQ==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Hi Rajeev,

Responses in line.

>
>
>> As agreed upon in London, unless there are any further changes needed,
>> I'd like to move forward with Gopal on incorporating the draft
>> into the body of draft-ietf-mobileip-fast-mipv6-02.txt.
>>
>
>I have some concerns with this. As I understand, please correct me if I am
>wrong, BETH
>relies on link-layer triggers to establish the bi-directional tunnel. The
>link-layer triggers are
>
>- not standarized. Who will do the standardization ?
>- not implemented (I guess since there is no standard). Any comments ?
>

As you know, there is a draft ongoing that is working toward defining
abstract triggers.  These naturally need to be implemented for specific
link layers, but the whole point of making them abstract is to 
remove the fast handoff specification from dependence on a specific
link layer. Naturally, it is up to specific groups that control
link layer specifications to work toward standardizing the triggers
for their link layers. As Pat pointed out in his response, a system vendor
may choose to implement the triggers as events on a particular platform
instead, in which case, there would be no interoperability implications.

>Given this dependence, having BETH as a part of FMIPv6 raises the following
>issues
>
>- how can we implement FMIPv6 with BETH ?
>- how can we test inter-operability ?
>
>So, I feel that FMIPv6 should contain enough specification that can become a
>standard without depending on link-layer trigger standardization to succeed. We
>are keen on moving FMIPv6 along, and would welcome new ideas that would improve
>the protocol. However, items that would require standardization of their own
>should perhaps be part of a separate document, and (still) be recognized in the
>FMIPv6 specification.
>

As Hesham has pointed out, the current FMIPv6 spec has an implicit dependence
on link layer triggers. How would an AR know to send a PrxyRtAdv or an
MN to send a SolPrxyRtAdv without some kind of information from the
link layer that a handover was pending? The BETH spec has made these
dependencies explicit, and has used the abstract trigger formulation to
make them independent of a particular link layer. In the low latency
MIPv4 spec, this approach was taken from the beginning. From an engineering
standpoint, IMHO making the need for triggers explicit and outlining
how they might work seems more likely to result in successful implementations.
It does not mean that every link layer must support all the triggers,
nor that every link layer must support BETH. It is possible that some
link layers won't have the proper kinds of triggers, in fact, some
may not even be able to support the base FMIPv6 spec for that reason.
If the need for triggers is called out in the spec, an implementor
can make a quicker decision about whether or not their link layer
and system platform supports the right ones, and, if not, work with
the right standardization bodies and their system vendor to assure
that the link layer triggers are available.

So, I guess I don't see a real problem. There seemed to be strong
concensus in London for including BETH in the base spec at this
point, I think we should move forward with it.

		jak



From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep 13 22:21:46 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA22818
	for <mobileip-archive@lists.ietf.org>; Thu, 13 Sep 2001 22:21:46 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id UAA10952;
	Thu, 13 Sep 2001 20:20:54 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id TAA16325;
	Thu, 13 Sep 2001 19:20:46 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8E2JU7B000427
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 13 Sep 2001 19:19:30 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8E2JUuJ000426
	for mobile-ip-dist; Thu, 13 Sep 2001 19:19:30 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8E2Fe7D000391
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 13 Sep 2001 19:19:26 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id PAA16694
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 13 Sep 2001 15:39:27 -0700 (PDT)
Received: from hoemail2.firewall.lucent.com (hoemail2.lucent.com [192.11.226.163])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id PAA23341
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 13 Sep 2001 15:39:26 -0700 (PDT)
Received: from marconi.ih.lucent.com (h135-1-120-108.lucent.com [135.1.120.108])
	by hoemail2.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id f8DMdP728650;
	Thu, 13 Sep 2001 18:39:25 -0400 (EDT)
Received: from nwsgpa.ih.lucent.com by marconi.ih.lucent.com (8.8.8+Sun/EMS-1.5 sol2)
	id RAA22851; Thu, 13 Sep 2001 17:39:24 -0500 (CDT)
Received: by nwsgpa.ih.lucent.com (8.8.8+Sun/EMS-1.5 client sol2)
	id RAA26610; Thu, 13 Sep 2001 17:39:15 -0500 (CDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15265.13715.831364.830180@nwsgpa.ih.lucent.com>
Date: Thu, 13 Sep 2001 17:39:15 -0500
From: Pete McCann <mccap@lucent.com>
To: mobile-ip@sunroof.eng.sun.com
Cc: pcalhoun@diameter.org, tom.hiller@lucent.com
Subject: [mobile-ip] IPv6 over Mobile IPv4
X-Mailer: VM 6.90 under 21.1 (patch 13) "Crater Lake" XEmacs Lucid
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hi,

We (Pat Calhoun, Tom Hiller, and myself) recently wrote a draft
describing a method for running IPv6 traffic while using Mobile IPv4
signaling for mobility management and security.  We submitted it today
to internet-drafts; you can find an advance copy at:

http://www.diameter.org/draft-mccann-mobileip-ipv6mipv4-00.txt

Basically, this could serve as an interim solution while we wait for
all of the Mobile IPv6 security work to converge.  It would allow us
to use the existing Mobile IPv4 security model, including AAA, for
securing registration requests, while providing IPv6 service to
dual-stack mobile nodes.  It may also help ease the overall transition
to IPv6 because it only requires IPv6 support in the MN, FA, HA, and
home network, while the network between the FA and HA could be a
legacy IPv4 cloud.

The draft itself is fairly straightforward; we would appreciate
comments on the list and would like to see if there is interest in
making this a working group item.

-Pete


From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep 13 22:24:29 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA22960
	for <mobileip-archive@lists.ietf.org>; Thu, 13 Sep 2001 22:24:28 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id TAA24218;
	Thu, 13 Sep 2001 19:23:50 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id TAA16765;
	Thu, 13 Sep 2001 19:23:43 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8E2MC7B000492
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 13 Sep 2001 19:22:12 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8E2MCPQ000491
	for mobile-ip-dist; Thu, 13 Sep 2001 19:22:12 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from heliopolis.eng.sun.com (redhook.Eng.Sun.COM [152.70.24.37])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8E2M87B000478
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 13 Sep 2001 19:22:08 -0700 (PDT)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.eng.sun.com (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id QAA20832;
	Thu, 13 Sep 2001 16:22:42 -0700 (PDT)
Message-Id: <200109132322.QAA20832@heliopolis.eng.sun.com>
Date: Thu, 13 Sep 2001 16:22:41 -0700 (PDT)
From: James Kempf <James.Kempf@Sun.COM>
Subject: Re: [mobile-ip] New BETH Draft
To: mobile-ip@sunroof.eng.sun.com, rajeev@iprg.nokia.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: cHmqj+aqoQU7SxNI1TIfaw==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Hi Rajeev,


>thanks for your comments. I guess was not clear enough in separating the 
concerns
>regarding link-layer triggers. I suppose you can identify two kinds. First, in
>response to an existing L2 event, one could generate a trigger internally to 
effect
>a L3 action. For instance, an implementation may generate Proxy Router 
Solicitation
>in response to scanning and detecting a new AP that the MN wishes to connect 
to.
>This is internal to a host, such as a MN, and I guess this is what Pat was
>referring to. Second, a new Layer 2 trigger (message ?) between two different
>entities (such as a MN and an AR) could also be defined. But, this would 
perhaps
>require standardization. This latter form of a trigger is perhaps needed to
>indicate, e.g.,  that a MN has moved away from an AR. [In shared media, are 
there
>link triggers available to indicate termination of link connectivity ?  Also, 
in
>dedicated links, an AP may know that a MN has terminated link connectivity, but 
a
>new trigger is still needed between the AP and the AR (in the general) case to
>indicate to the AR of the MN's movement]
>
>So, my concern is regarding those kinds that require standardization. Would it 
be
>possible to clearly identify those triggers that are implementation-specific 
and
>those that require standardization ? If BETH has only implementation-specific
>triggers, that would be fine.  However, it has to be clearly identified and 
stated.
>It must also identify what triggers need standardization of their own, if any.
>
>Hope this is clearer.
>

I think this depends on the particular radio protocol and how it
is implemented. In CDMA protocols, the MIP AR will probably
see the trigger as a platform specific API event, since the APs
are basically hidden by the RAN protocol. In 802.11 systems where
the AR and AP are in the same box, this will likely be true as
well. These kinds of systems are not very common today for 802.11.

So the main issue is when there are bridging APs and a wired subnet
between the AP and AR which is not opaque at L3 like a CDMA RAN is.
This is the common deployment situation with 802.11 today,
maybe Bluetooth as well? In that case, some standardization of a protocol 
between the AP and AR to allow the AP to transfer trigger information 
to the AR would be appropriate.

One possibility is to look at extensions to the IEEE IAPP (InterAccess
Point Protocol) for 802.11 (I think it is designated 802.11/f). 
Bernard Aboba recently published a draft that does something similar
for context transfer of RADIUS context (draft-aboba-802-context-01.txt).
Bernard used  an extensiblity feature of 802.11, perhaps we could do
the same. If not, we should start talking with IEEE about what we need.
The standard is not yet finished, last I heard, so there is time.

		jak



From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep 13 22:24:36 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA22979
	for <mobileip-archive@lists.ietf.org>; Thu, 13 Sep 2001 22:24:35 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id UAA12583;
	Thu, 13 Sep 2001 20:23:56 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id TAA16852;
	Thu, 13 Sep 2001 19:23:54 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8E2MM7B000498
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 13 Sep 2001 19:22:22 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8E2MMcp000497
	for mobile-ip-dist; Thu, 13 Sep 2001 19:22:22 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from heliopolis.eng.sun.com (redhook.Eng.Sun.COM [152.70.24.37])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8E2M87D000478
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 13 Sep 2001 19:22:08 -0700 (PDT)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.eng.sun.com (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id NAA13206;
	Thu, 13 Sep 2001 13:23:44 -0700 (PDT)
Message-Id: <200109132023.NAA13206@heliopolis.eng.sun.com>
Date: Thu, 13 Sep 2001 13:23:43 -0700 (PDT)
From: James Kempf <James.Kempf@Sun.COM>
Subject: RE: [mobile-ip] New BETH Draft
To: mobile-ip@sunroof.eng.sun.com, Basavaraj.Patil@nokia.com
Cc: James.Kempf@Sun.COM
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: Ut1lk+z1hBAWssR42WlDJA==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Hi Raj,


>During the design team discussions we recognized the need for L2
>triggers and the importance of those which makes fast handoffs
>possible. However we agreed to keep working on the L3 details and
>take an abstract view of the L2 dependencies and triggers. We
>expected that this work would be taken up at some time in the
>future either in the MIP WG or elsewhere. 
>I think what Rajeev is questioning is the validity of the solution from
>an implementation perspective. To truly make the fast handoff solution
>interoperable we need to define a set of triggers (to<->from) the lower
>layers. I think the manyfolks draft is a good start in this direction. 
>The abstractness of L2s on the fast handoff solution cannot be ignored
>for too long. We can stick our heads in the sand and pretend that it 
>does not cause any impacts to the L3 solution. But when you start 
>dealing with implementing the spec you are bound to run into these
>issues.
>

Agree!

We're working on some  "proof of concept" for L2 triggers and 
low latency MIPv4, and ultimately I'd like to extend the work
to FMIPv6. Hopefully that will flush out some issues. But there is definitely 
the need to work with some real L2 protocols and see  what can
be done about supporting the kind of triggers needed for
high performance MIP handover.

		jak
		
>However I see no reason for not including BETH in the current FMIPv6
>draft. I think the BETH solution should be added as another way of 
>accomplishing fast handoffs. But the spec is incomplete without there
>existing ways and means to interact with the lower layers. 
>I think the sooner we tackle this problem, the faster we can get some
>real implementations that can interoperate.
>



From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep 13 22:42:05 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA24602
	for <mobileip-archive@lists.ietf.org>; Thu, 13 Sep 2001 22:42:04 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id UAA21868;
	Thu, 13 Sep 2001 20:41:25 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id TAA19463;
	Thu, 13 Sep 2001 19:41:24 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8E2eE7B000755
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 13 Sep 2001 19:40:14 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8E2eEqk000754
	for mobile-ip-dist; Thu, 13 Sep 2001 19:40:14 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from jurassic.eng.sun.com (jurassic [129.146.88.130] (may be forged))
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8E2e77F000735
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 13 Sep 2001 19:40:08 -0700 (PDT)
Received: from istanbul.Eng.Sun.COM (istanbul.Eng.Sun.COM [129.146.86.247])
	by jurassic.eng.sun.com (8.12.0+Sun/8.12.0) with SMTP id f8DN32Vj449314
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 13 Sep 2001 16:03:03 -0700 (PDT)
Message-Id: <200109132303.f8DN32Vj449314@jurassic.eng.sun.com>
Date: Thu, 13 Sep 2001 16:02:56 -0700 (PDT)
From: Alper Yegin <Alper.Yegin@eng.sun.com>
Subject: RE: [mobile-ip] New BETH Draft
To: mobile-ip@sunroof.eng.sun.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: GGbQH3W/dvqieMFz4Kcqfw==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4_37 SunOS 5.8.1 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

> Rajeev, 
> 
> Is there any scenario in FMIPv4 or FMIPv6 that does not
> rely on triggers? I don't think BETH is unique here. 
> 
> Hesham


Hesham,

We should still distinguish among different triggers though. For example FMIPv6 
can operate even if the only triggers available are on the Mobile Node. On some 
links, such as WLAN, some of the AR side triggers might not exist, e.g. LINK 
DOWN. And this effects the availability of BETH to those networks.

FMIPv6's reliance on the L2 triggers is less than that of BETH.

But of course, as James said, one should use BETH only if they have support for 
these triggers.. If they don't, they can't. That simple.

alper

> 
> 
> > > As agreed upon in London, unless there are any further changes needed,
> > > I'd like to move forward with Gopal on incorporating the draft
> > > into the body of draft-ietf-mobileip-fast-mipv6-02.txt.
> > >
> > 
> > I have some concerns with this. As I understand, please correct me if I am
> > wrong, BETH
> > relies on link-layer triggers to establish the bi-directional tunnel. The
> > link-layer triggers are
> > 
> > - not standarized. Who will do the standardization ?
> > - not implemented (I guess since there is no standard). Any comments ?
> > 
> > Given this dependence, having BETH as a part of FMIPv6 raises the following
> > issues
> > 
> > - how can we implement FMIPv6 with BETH ?
> > - how can we test inter-operability ?
> > 
> > So, I feel that FMIPv6 should contain enough specification that can become a
> > standard without depending on link-layer trigger standardization to succeed. 
We
> > are keen on moving FMIPv6 along, and would welcome new ideas that would 
improve
> > the protocol. However, items that would require standardization of their own
> > should perhaps be part of a separate document, and (still) be recognized in 
the
> > FMIPv6 specification.
> > 
> > Comments ?
> > 
> > 
> > Regards,
> > 
> > -Rajeev
> > 
> > 
> > 
> > 
> > >
> > >                 jak

alper



From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep 13 22:42:34 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA24638
	for <mobileip-archive@lists.ietf.org>; Thu, 13 Sep 2001 22:42:34 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id TAA28012;
	Thu, 13 Sep 2001 19:41:54 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id TAA19514;
	Thu, 13 Sep 2001 19:41:35 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8E2eD7B000752
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 13 Sep 2001 19:40:13 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8E2eDGR000751
	for mobile-ip-dist; Thu, 13 Sep 2001 19:40:13 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from jurassic.eng.sun.com (jurassic [129.146.88.130] (may be forged))
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8E2e77B000735
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 13 Sep 2001 19:40:07 -0700 (PDT)
Received: from istanbul.Eng.Sun.COM (istanbul.Eng.Sun.COM [129.146.86.247])
	by jurassic.eng.sun.com (8.12.0+Sun/8.12.0) with SMTP id f8DNkQVj462291
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 13 Sep 2001 16:46:26 -0700 (PDT)
Message-Id: <200109132346.f8DNkQVj462291@jurassic.eng.sun.com>
Date: Thu, 13 Sep 2001 16:46:19 -0700 (PDT)
From: Alper Yegin <Alper.Yegin@eng.sun.com>
Subject: Re: [mobile-ip] New BETH Draft
To: mobile-ip@sunroof.eng.sun.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: HAH4+oyU5nN0/TW3bmCtJg==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4_37 SunOS 5.8.1 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Hi Jim,

Right before the last IETF we had discussed how handoff would work when nAR 
doesn't support the BETH protocol.

I think you have added section 2.5.3 Failure of BET Handover to address this 
issue, right?

I have a question on how this works:

	If the candidate cannot support BETH, then the current AR
	should initiate FMIPv6 handover if the candidate supports it, or, if
	the candidate AR does not support FMIPv6, simply allow the MN to do
	movement detection according to the original Johnson and Perkins
	algorithm.
	
If the nAR doesn't support neither BETH nor FMIPv6, then how is MN supposed to 
detect this and proceed with a stock handoff? 

I think it would be useful to have a section that describes MN behavior, 
especially under these different cases.

Cheers,

alper



From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep 13 23:01:08 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA25254
	for <mobileip-archive@lists.ietf.org>; Thu, 13 Sep 2001 23:01:07 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id UAA01856;
	Thu, 13 Sep 2001 20:00:32 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id UAA21714;
	Thu, 13 Sep 2001 20:00:24 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8E2wc7T000952
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 13 Sep 2001 19:58:42 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8E2Ose4000555
	for mobile-ip-dist; Thu, 13 Sep 2001 19:24:54 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8E2L47H000454
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 13 Sep 2001 19:24:50 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id LAA19390
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 13 Sep 2001 11:42:03 -0700 (PDT)
Received: from mgw-dax2.ext.nokia.com (mgw-dax2.ext.nokia.com [63.78.179.217])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id LAA28327
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 13 Sep 2001 11:42:03 -0700 (PDT)
Received: from davir02nok.americas.nokia.com (davir02nok.americas.nokia.com [172.18.242.85])
	by mgw-dax2.ext.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f8DIg8C29228
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 13 Sep 2001 13:42:08 -0500 (CDT)
Received: from daebh002.NOE.Nokia.com (unverified) by davir02nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T55f8363768ac12f255079@davir02nok.americas.nokia.com>;
 Thu, 13 Sep 2001 13:42:02 -0500
Received: from daebe007.NOE.Nokia.com ([172.18.242.211]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.2966);
	 Thu, 13 Sep 2001 13:42:04 -0500
content-class: urn:content-classes:message
Subject: RE: [mobile-ip] New BETH Draft
Date: Thu, 13 Sep 2001 13:42:02 -0500
Message-ID: <697DAA22C5004B4596E033803A7CEF441E8679@daebe007.NOE.Nokia.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Thread-Topic: [mobile-ip] New BETH Draft
X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0
Thread-Index: AcE8cWBm3vqGWahgEdWJUwAIx6TWpQAEScHw
From: "Patil Basavaraj (NET/Dallas)" <Basavaraj.Patil@nokia.com>
To: <mobile-ip@sunroof.eng.sun.com>
Cc: "'James kempf'" <James.Kempf@Sun.COM>
X-OriginalArrivalTime: 13 Sep 2001 18:42:04.0922 (UTC) FILETIME=[C8BBD5A0:01C13C83]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by sunroof.eng.sun.com id f8E2Op7B000547
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 8bit

Hi James,

During the design team discussions we recognized the need for L2
triggers and the importance of those which makes fast handoffs
possible. However we agreed to keep working on the L3 details and
take an abstract view of the L2 dependencies and triggers. We
expected that this work would be taken up at some time in the
future either in the MIP WG or elsewhere. 
I think what Rajeev is questioning is the validity of the solution from
an implementation perspective. To truly make the fast handoff solution
interoperable we need to define a set of triggers (to<->from) the lower
layers. I think the manyfolks draft is a good start in this direction. 
The abstractness of L2s on the fast handoff solution cannot be ignored
for too long. We can stick our heads in the sand and pretend that it 
does not cause any impacts to the L3 solution. But when you start 
dealing with implementing the spec you are bound to run into these
issues.

However I see no reason for not including BETH in the current FMIPv6
draft. I think the BETH solution should be added as another way of 
accomplishing fast handoffs. But the spec is incomplete without there
existing ways and means to interact with the lower layers. 
I think the sooner we tackle this problem, the faster we can get some
real implementations that can interoperate.

-Basavaraj



> Hi Rajeev,
> 
> Responses in line.
> 
> >
> >
> >> As agreed upon in London, unless there are any further 
> changes needed,
> >> I'd like to move forward with Gopal on incorporating the draft
> >> into the body of draft-ietf-mobileip-fast-mipv6-02.txt.
> >>
> >
> >I have some concerns with this. As I understand, please 
> correct me if I am
> >wrong, BETH
> >relies on link-layer triggers to establish the 
> bi-directional tunnel. The
> >link-layer triggers are
> >
> >- not standarized. Who will do the standardization ?
> >- not implemented (I guess since there is no standard). Any 
> comments ?
> >
> 
> As you know, there is a draft ongoing that is working toward defining
> abstract triggers.  These naturally need to be implemented 
> for specific
> link layers, but the whole point of making them abstract is to 
> remove the fast handoff specification from dependence on a specific
> link layer. Naturally, it is up to specific groups that control
> link layer specifications to work toward standardizing the triggers
> for their link layers. As Pat pointed out in his response, a 
> system vendor
> may choose to implement the triggers as events on a 
> particular platform
> instead, in which case, there would be no interoperability 
> implications.
> 
> >Given this dependence, having BETH as a part of FMIPv6 
> raises the following
> >issues
> >
> >- how can we implement FMIPv6 with BETH ?
> >- how can we test inter-operability ?
> >
> >So, I feel that FMIPv6 should contain enough specification 
> that can become a
> >standard without depending on link-layer trigger 
> standardization to succeed. We
> >are keen on moving FMIPv6 along, and would welcome new ideas 
> that would improve
> >the protocol. However, items that would require 
> standardization of their own
> >should perhaps be part of a separate document, and (still) 
> be recognized in the
> >FMIPv6 specification.
> >
> 
> As Hesham has pointed out, the current FMIPv6 spec has an 
> implicit dependence
> on link layer triggers. How would an AR know to send a PrxyRtAdv or an
> MN to send a SolPrxyRtAdv without some kind of information from the
> link layer that a handover was pending? The BETH spec has made these
> dependencies explicit, and has used the abstract trigger 
> formulation to
> make them independent of a particular link layer. In the low latency
> MIPv4 spec, this approach was taken from the beginning. From 
> an engineering
> standpoint, IMHO making the need for triggers explicit and outlining
> how they might work seems more likely to result in successful 
> implementations.
> It does not mean that every link layer must support all the triggers,
> nor that every link layer must support BETH. It is possible that some
> link layers won't have the proper kinds of triggers, in fact, some
> may not even be able to support the base FMIPv6 spec for that reason.
> If the need for triggers is called out in the spec, an implementor
> can make a quicker decision about whether or not their link layer
> and system platform supports the right ones, and, if not, work with
> the right standardization bodies and their system vendor to assure
> that the link layer triggers are available.
> 
> So, I guess I don't see a real problem. There seemed to be strong
> concensus in London for including BETH in the base spec at this
> point, I think we should move forward with it.
> 
> 		jak
> 


From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep 13 23:01:25 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA25266
	for <mobileip-archive@lists.ietf.org>; Thu, 13 Sep 2001 23:01:20 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id VAA00777;
	Thu, 13 Sep 2001 21:00:40 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id UAA21743;
	Thu, 13 Sep 2001 20:00:35 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8E2wc7R000952
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 13 Sep 2001 19:58:42 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8E2RvMt000592
	for mobile-ip-dist; Thu, 13 Sep 2001 19:27:57 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8E2Rr7B000576
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 13 Sep 2001 19:27:53 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id LAA04995
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 13 Sep 2001 11:06:01 -0700 (PDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id MAA16413
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 13 Sep 2001 12:05:56 -0600 (MDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id LAA13684
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 13 Sep 2001 11:05:59 -0700 (PDT)
X-Delivered-For: <mobile-ip@sunroof.eng.sun.com>
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f8DI5wS25098
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 13 Sep 2001 11:05:58 -0700
X-mProtect:  Thu, 13 Sep 2001 11:05:58 -0700 Nokia Silicon Valley Messaging Protection
Received: from rajeev.iprg.nokia.com (205.226.2.90, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpdxzZhih; Thu, 13 Sep 2001 11:05:56 PDT
Message-ID: <3BA0F585.D01FBA08@iprg.nokia.com>
Date: Thu, 13 Sep 2001 11:05:57 -0700
From: Rajeev Koodli <rajeev@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] New BETH Draft
References: <200109131627.JAA00876@heliopolis.eng.sun.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hello James,

thanks for your comments. I guess was not clear enough in separating the concerns
regarding link-layer triggers. I suppose you can identify two kinds. First, in
response to an existing L2 event, one could generate a trigger internally to effect
a L3 action. For instance, an implementation may generate Proxy Router Solicitation
in response to scanning and detecting a new AP that the MN wishes to connect to.
This is internal to a host, such as a MN, and I guess this is what Pat was
referring to. Second, a new Layer 2 trigger (message ?) between two different
entities (such as a MN and an AR) could also be defined. But, this would perhaps
require standardization. This latter form of a trigger is perhaps needed to
indicate, e.g.,  that a MN has moved away from an AR. [In shared media, are there
link triggers available to indicate termination of link connectivity ?  Also, in
dedicated links, an AP may know that a MN has terminated link connectivity, but a
new trigger is still needed between the AP and the AR (in the general) case to
indicate to the AR of the MN's movement]

So, my concern is regarding those kinds that require standardization. Would it be
possible to clearly identify those triggers that are implementation-specific and
those that require standardization ? If BETH has only implementation-specific
triggers, that would be fine.  However, it has to be clearly identified and stated.
It must also identify what triggers need standardization of their own, if any.

Hope this is clearer.

Regards,

-Rajeev


James Kempf wrote:

> Hi Rajeev,
>
> Responses in line.
>
> >
> >
> >> As agreed upon in London, unless there are any further changes needed,
> >> I'd like to move forward with Gopal on incorporating the draft
> >> into the body of draft-ietf-mobileip-fast-mipv6-02.txt.
> >>
> >
> >I have some concerns with this. As I understand, please correct me if I am
> >wrong, BETH
> >relies on link-layer triggers to establish the bi-directional tunnel. The
> >link-layer triggers are
> >
> >- not standarized. Who will do the standardization ?
> >- not implemented (I guess since there is no standard). Any comments ?
> >
>
> As you know, there is a draft ongoing that is working toward defining
> abstract triggers.  These naturally need to be implemented for specific
> link layers, but the whole point of making them abstract is to
> remove the fast handoff specification from dependence on a specific
> link layer. Naturally, it is up to specific groups that control
> link layer specifications to work toward standardizing the triggers
> for their link layers. As Pat pointed out in his response, a system vendor
> may choose to implement the triggers as events on a particular platform
> instead, in which case, there would be no interoperability implications.
>
> >Given this dependence, having BETH as a part of FMIPv6 raises the following
> >issues
> >
> >- how can we implement FMIPv6 with BETH ?
> >- how can we test inter-operability ?
> >
> >So, I feel that FMIPv6 should contain enough specification that can become a
> >standard without depending on link-layer trigger standardization to succeed. We
> >are keen on moving FMIPv6 along, and would welcome new ideas that would improve
> >the protocol. However, items that would require standardization of their own
> >should perhaps be part of a separate document, and (still) be recognized in the
> >FMIPv6 specification.
> >
>
> As Hesham has pointed out, the current FMIPv6 spec has an implicit dependence
> on link layer triggers. How would an AR know to send a PrxyRtAdv or an
> MN to send a SolPrxyRtAdv without some kind of information from the
> link layer that a handover was pending? The BETH spec has made these
> dependencies explicit, and has used the abstract trigger formulation to
> make them independent of a particular link layer. In the low latency
> MIPv4 spec, this approach was taken from the beginning. From an engineering
> standpoint, IMHO making the need for triggers explicit and outlining
> how they might work seems more likely to result in successful implementations.
> It does not mean that every link layer must support all the triggers,
> nor that every link layer must support BETH. It is possible that some
> link layers won't have the proper kinds of triggers, in fact, some
> may not even be able to support the base FMIPv6 spec for that reason.
> If the need for triggers is called out in the spec, an implementor
> can make a quicker decision about whether or not their link layer
> and system platform supports the right ones, and, if not, work with
> the right standardization bodies and their system vendor to assure
> that the link layer triggers are available.
>
> So, I guess I don't see a real problem. There seemed to be strong
> concensus in London for including BETH in the base spec at this
> point, I think we should move forward with it.
>
>                 jak



From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep 13 23:01:40 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA25293
	for <mobileip-archive@lists.ietf.org>; Thu, 13 Sep 2001 23:01:39 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id VAA01051;
	Thu, 13 Sep 2001 21:00:59 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id UAA21809;
	Thu, 13 Sep 2001 20:00:57 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8E2wc7L000952
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 13 Sep 2001 19:58:40 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8E2Umef000620
	for mobile-ip-dist; Thu, 13 Sep 2001 19:30:48 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8E2Uj7B000613
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 13 Sep 2001 19:30:45 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id PAA20316
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 13 Sep 2001 15:53:10 -0700 (PDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id QAA09857
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 13 Sep 2001 16:53:05 -0600 (MDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id PAA05032
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 13 Sep 2001 15:53:08 -0700 (PDT)
X-Delivered-For: <mobile-ip@sunroof.eng.sun.com>
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f8DMr8r28483
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 13 Sep 2001 15:53:08 -0700
X-mProtect:  Thu, 13 Sep 2001 15:53:08 -0700 Nokia Silicon Valley Messaging Protection
Received: from rajeev.iprg.nokia.com (205.226.2.90, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpdUBUy6e; Thu, 13 Sep 2001 15:53:02 PDT
Message-ID: <3BA138CE.658E5B6D@iprg.nokia.com>
Date: Thu, 13 Sep 2001 15:53:02 -0700
From: Rajeev Koodli <rajeev@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: mobile-ip@sunroof.eng.sun.com
Subject: [mobile-ip] [Fwd: Warning: could not send message for past 4 hours]
Content-Type: multipart/mixed;
 boundary="------------53198F62C53F665663C04B9C"
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

This is a multi-part message in MIME format.
--------------53198F62C53F665663C04B9C
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit



--------------53198F62C53F665663C04B9C
Content-Type: message/rfc822
Content-Disposition: inline

Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id PAA02679
	for <rajeev@iprg.nokia.com>; Thu, 13 Sep 2001 15:16:17 -0700 (PDT)
X-Delivered-For: <rajeev@iprg.nokia.com>
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f8DMGGc31158
	for <rajeev@iprg.nokia.com>; Thu, 13 Sep 2001 15:16:16 -0700
X-mProtect:  Thu, 13 Sep 2001 15:16:16 -0700 Nokia Silicon Valley Messaging Protection
Received: from mailrelay.iprg.nokia.com (205.226.0.201)
	by darkstar.iprg.nokia.com(P1.5 smtpdNyeQ3T; Thu, 13 Sep 2001 15:16:12 PDT
Received: (from root@localhost)
	by mailrelay.iprg.nokia.com (8.11.0/8.11.0-WTS) id f8DNQTH21817
	for <rajeev@iprg.nokia.com>; Thu, 13 Sep 2001 15:26:29 -0800
Received: from patan.Sun.COM (192.18.98.43)
	by -={Mailrelay}=-(WTS.12.69) smtpdnqrktK; Thu, 13 Sep 2001 15:26:28 AKDT
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id QAA10396
	for <rajeev@iprg.nokia.com>; Thu, 13 Sep 2001 16:16:06 -0600 (MDT)
Received: from localhost (localhost)
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with internal id OAD16548;
	Thu, 13 Sep 2001 15:16:11 -0700 (PDT)
Date: Thu, 13 Sep 2001 15:16:11 -0700 (PDT)
From: Mail Delivery Subsystem <MAILER-DAEMON@engmail2.Eng.Sun.COM>
Message-Id: <200109132216.OAD16548@engmail2.Eng.Sun.COM>
To: <rajeev@iprg.nokia.com>
MIME-Version: 1.0
Content-Type: multipart/report; report-type=delivery-status;
	boundary="OAD16548.1000419371/engmail2.Eng.Sun.COM"
Subject: Warning: could not send message for past 4 hours
Auto-Submitted: auto-generated (warning-timeout)
X-Mozilla-Status2: 00000000

This is a MIME-encapsulated message

--OAD16548.1000419371/engmail2.Eng.Sun.COM

    **********************************************
    **      THIS IS A WARNING MESSAGE ONLY      **
    **  YOU DO NOT NEED TO RESEND YOUR MESSAGE  **
    **********************************************

The original message was received at Thu, 13 Sep 2001 11:06:01 -0700 (PDT)
from patan.Central.Sun.COM [129.147.5.43]

   ----- The following addresses had transient non-fatal errors -----
<mobile-ip@sunroof.eng.sun.com>

   ----- Transcript of session follows -----
<mobile-ip@sunroof.eng.sun.com>... Deferred: Connection refused by sunroof.eng.sun.com.
Warning: message still undelivered after 4 hours
Will keep trying until message is 3 days old

--OAD16548.1000419371/engmail2.Eng.Sun.COM
Content-Type: message/delivery-status

Reporting-MTA: dns; engmail2.Eng.Sun.COM
Arrival-Date: Thu, 13 Sep 2001 11:06:01 -0700 (PDT)

Final-Recipient: RFC822; mobile-ip@sunroof.eng.sun.com
Action: delayed
Status: 4.4.1
Remote-MTA: DNS; sunroof.eng.sun.com
Last-Attempt-Date: Thu, 13 Sep 2001 15:16:09 -0700 (PDT)
Will-Retry-Until: Sun, 16 Sep 2001 11:06:01 -0700 (PDT)

--OAD16548.1000419371/engmail2.Eng.Sun.COM
Content-Type: message/rfc822

Return-Path: <rajeev@iprg.nokia.com>
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id LAA04995
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 13 Sep 2001 11:06:01 -0700 (PDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id MAA16413
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 13 Sep 2001 12:05:56 -0600 (MDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id LAA13684
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 13 Sep 2001 11:05:59 -0700 (PDT)
X-Delivered-For: <mobile-ip@sunroof.eng.sun.com>
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f8DI5wS25098
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 13 Sep 2001 11:05:58 -0700
X-mProtect:  Thu, 13 Sep 2001 11:05:58 -0700 Nokia Silicon Valley Messaging Protection
Received: from rajeev.iprg.nokia.com (205.226.2.90, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpdxzZhih; Thu, 13 Sep 2001 11:05:56 PDT
Sender: rajeev@iprg.nokia.com
Message-ID: <3BA0F585.D01FBA08@iprg.nokia.com>
Date: Thu, 13 Sep 2001 11:05:57 -0700
From: Rajeev Koodli <rajeev@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] New BETH Draft
References: <200109131627.JAA00876@heliopolis.eng.sun.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


Hello James,

thanks for your comments. I guess was not clear enough in separating the concerns
regarding link-layer triggers. I suppose you can identify two kinds. First, in
response to an existing L2 event, one could generate a trigger internally to effect
a L3 action. For instance, an implementation may generate Proxy Router Solicitation
in response to scanning and detecting a new AP that the MN wishes to connect to.
This is internal to a host, such as a MN, and I guess this is what Pat was
referring to. Second, a new Layer 2 trigger (message ?) between two different
entities (such as a MN and an AR) could also be defined. But, this would perhaps
require standardization. This latter form of a trigger is perhaps needed to
indicate, e.g.,  that a MN has moved away from an AR. [In shared media, are there
link triggers available to indicate termination of link connectivity ?  Also, in
dedicated links, an AP may know that a MN has terminated link connectivity, but a
new trigger is still needed between the AP and the AR (in the general) case to
indicate to the AR of the MN's movement]

So, my concern is regarding those kinds that require standardization. Would it be
possible to clearly identify those triggers that are implementation-specific and
those that require standardization ? If BETH has only implementation-specific
triggers, that would be fine.  However, it has to be clearly identified and stated.
It must also identify what triggers need standardization of their own, if any.

Hope this is clearer.

Regards,

-Rajeev


James Kempf wrote:

> Hi Rajeev,
>
> Responses in line.
>
> >
> >
> >> As agreed upon in London, unless there are any further changes needed,
> >> I'd like to move forward with Gopal on incorporating the draft
> >> into the body of draft-ietf-mobileip-fast-mipv6-02.txt.
> >>
> >
> >I have some concerns with this. As I understand, please correct me if I am
> >wrong, BETH
> >relies on link-layer triggers to establish the bi-directional tunnel. The
> >link-layer triggers are
> >
> >- not standarized. Who will do the standardization ?
> >- not implemented (I guess since there is no standard). Any comments ?
> >
>
> As you know, there is a draft ongoing that is working toward defining
> abstract triggers.  These naturally need to be implemented for specific
> link layers, but the whole point of making them abstract is to
> remove the fast handoff specification from dependence on a specific
> link layer. Naturally, it is up to specific groups that control
> link layer specifications to work toward standardizing the triggers
> for their link layers. As Pat pointed out in his response, a system vendor
> may choose to implement the triggers as events on a particular platform
> instead, in which case, there would be no interoperability implications.
>
> >Given this dependence, having BETH as a part of FMIPv6 raises the following
> >issues
> >
> >- how can we implement FMIPv6 with BETH ?
> >- how can we test inter-operability ?
> >
> >So, I feel that FMIPv6 should contain enough specification that can become a
> >standard without depending on link-layer trigger standardization to succeed. We
> >are keen on moving FMIPv6 along, and would welcome new ideas that would improve
> >the protocol. However, items that would require standardization of their own
> >should perhaps be part of a separate document, and (still) be recognized in the
> >FMIPv6 specification.
> >
>
> As Hesham has pointed out, the current FMIPv6 spec has an implicit dependence
> on link layer triggers. How would an AR know to send a PrxyRtAdv or an
> MN to send a SolPrxyRtAdv without some kind of information from the
> link layer that a handover was pending? The BETH spec has made these
> dependencies explicit, and has used the abstract trigger formulation to
> make them independent of a particular link layer. In the low latency
> MIPv4 spec, this approach was taken from the beginning. From an engineering
> standpoint, IMHO making the need for triggers explicit and outlining
> how they might work seems more likely to result in successful implementations.
> It does not mean that every link layer must support all the triggers,
> nor that every link layer must support BETH. It is possible that some
> link layers won't have the proper kinds of triggers, in fact, some
> may not even be able to support the base FMIPv6 spec for that reason.
> If the need for triggers is called out in the spec, an implementor
> can make a quicker decision about whether or not their link layer
> and system platform supports the right ones, and, if not, work with
> the right standardization bodies and their system vendor to assure
> that the link layer triggers are available.
>
> So, I guess I don't see a real problem. There seemed to be strong
> concensus in London for including BETH in the base spec at this
> point, I think we should move forward with it.
>
>                 jak


--OAD16548.1000419371/engmail2.Eng.Sun.COM--


--------------53198F62C53F665663C04B9C--



From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep 13 23:06:09 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA25432
	for <mobileip-archive@lists.ietf.org>; Thu, 13 Sep 2001 23:06:09 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id VAA03574;
	Thu, 13 Sep 2001 21:05:30 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id UAA22597;
	Thu, 13 Sep 2001 20:05:30 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8E34W7B001134
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 13 Sep 2001 20:04:32 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8E34WTd001133
	for mobile-ip-dist; Thu, 13 Sep 2001 20:04:32 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8E34S7B001126
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 13 Sep 2001 20:04:28 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id QAA29874
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 13 Sep 2001 16:36:19 -0700 (PDT)
Received: from ipop6 (ipop6.tm.net.my [202.188.0.250])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id QAA17146
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 13 Sep 2001 16:36:18 -0700 (PDT)
Received: from jun (isdn-brf-87-200.tm.net.my [202.188.87.200])
 by ipop6.tm.net.my (iPlanet Messaging Server 5.1 (built May  7 2001))
 with SMTP id <0GJM00J5JK8B0E@ipop6.tm.net.my> for
 mobile-ip@sunroof.eng.sun.com; Fri, 14 Sep 2001 07:36:12 +0800 (SGT)
Date: Fri, 14 Sep 2001 07:39:07 +0800
From: Rob Cayzer <cayzer@ieee.org>
Subject: RE: [mobile-ip] Commercial deployment o Mobile IP
In-reply-to: <D456C897C3DBD311816F0008C716D05107BBC0A7@NHQNTEX02.nextel.com>
To: mobile-ip@sunroof.eng.sun.com
Message-id: <NEBBJGGKGCJHCCJHBMILKENNCAAA.cayzer@ieee.org>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7BIT

Hi Hung,

I am interested to know what your use case is.

cheers,
Rob Cayzer

-----Original Message-----
From: owner-mobile-ip@sunroof.eng.sun.com
[mailto:owner-mobile-ip@sunroof.eng.sun.com]On Behalf Of Bui, Hung
Sent: 12 September 2001 21:02
To: 'mobile-ip@sunroof.eng.sun.com'
Subject: RE: [mobile-ip] Commercial deployment o Mobile IP


Dear Sharif,

I am working for Nextel Communications, Inc.  I joined Nextel last month.

Today, Nextel is actually deploying Mobile IP.  We have over 2 millions
mobile IP node subscribers.

Please let me know should you have any questions on commercial mobile IP
system.  As I am new here, I may not have all the answers for you.

Regards,
Hung

______________________________________
Hung Bui
Sr. Manager
Technology Development
NEXTEL Communications, Inc.
? desk: 703-433 8111
? mobile: 703-932 9895
? email: hung.bui@nextel.com
? text messaging: 7039329895@messaging.nextel.com
______________________________________

-----Original Message-----
From: Shahrier, Sharif M. [mailto:Sharif.Shahrier@InterDigital.com]
Sent: Monday, September 10, 2001 3:31 PM
To: 'mobile-ip@sunroof.eng.sun.com'
Subject: RE: [mobile-ip] Commercial deployment o Mobile IP


Hi,

        I was wondering if there were anyone deploying Mobile Internet
protocols commercially or as an experimental system. I am interested in
hardware/software platforms for Mobile Internet. I am interested in the
protocols developed by this WG, Mobile IPv4 and IPv6, and also in
prepriotory solutions.

I would be interested in some off-line discussions with people in this area.
Thnaks.

-Sharif.



From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep 14 10:10:52 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18293
	for <mobileip-archive@lists.ietf.org>; Fri, 14 Sep 2001 10:10:51 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id IAA17122;
	Fri, 14 Sep 2001 08:09:52 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id HAA11246;
	Fri, 14 Sep 2001 07:09:46 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8EE8F7B001923
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 14 Sep 2001 07:08:15 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8EE8FBZ001922
	for mobile-ip-dist; Fri, 14 Sep 2001 07:08:15 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8EE8B7B001915
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 14 Sep 2001 07:08:11 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id HAA10999
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 14 Sep 2001 07:08:31 -0700 (PDT)
Received: from albatross-ext.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id HAA08014
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 14 Sep 2001 07:08:29 -0700 (PDT)
Received: from esealnt462.al.sw.ericsson.se (ESEALNT462.al.sw.ericsson.se [153.88.251.62])
	by albatross.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id f8EE8NK13304
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 14 Sep 2001 16:08:28 +0200 (MEST)
Received: FROM esealnt742.al.sw.ericsson.se BY esealnt462.al.sw.ericsson.se ; Fri Sep 14 16:08:22 2001 +0200
Received: by esealnt742.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <NBWN7V0K>; Fri, 14 Sep 2001 16:01:22 +0200
Message-ID: <034BEFD03799D411A59F00508BDF754603008CC5@esealnt448.al.sw.ericsson.se>
From: "Hesham Soliman  (ERA)" <Hesham.Soliman@era.ericsson.se>
To: "'mobile-ip@sunroof.eng.sun.com'" <mobile-ip@sunroof.eng.sun.com>
Subject: RE: [mobile-ip] New BETH Draft
Date: Fri, 14 Sep 2001 16:08:11 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
	Alper, 

> We should still distinguish among different triggers though. For example FMIPv6 
> can operate even if the only triggers available are on the Mobile Node. On some 
> links, such as WLAN, some of the AR side triggers might not exist, e.g. LINK 
> DOWN. And this effects the availability of BETH to those networks.
> 
	=> Of course, the triggers are in the MN or the AR depending on the 
	type of radio that you have. But they are all triggers based on L2
	events. So I guess we're saying the same thing. FMIPv4/6 relies 
	on these triggers for all scenarios. Network initiation or MN initiation
	is independant.

> FMIPv6's reliance on the L2 triggers is less than that of BETH.
> 
	=> It is actually a third scenario in FMIPv6, the reliance on 
	triggers is identical to the case where the AR sends Pr_rtradv
	I don't see why you say that. The difference here is that the MN
	doesn't know, which is something we can debate, but anyhow
	this is not the issue on this thread. 

> But of course, as James said, one should use BETH only if they have support for 
> these triggers.. If they don't, they can't. That simple.
> 
	=> Exactly, but it's the same scenario for the case where the 
	AR sends an unsolicited Pr_rtr_adv. I don't see the difference.

	Hesham


> > 
> > 
> > > > As agreed upon in London, unless there are any further changes needed,
> > > > I'd like to move forward with Gopal on incorporating the draft
> > > > into the body of draft-ietf-mobileip-fast-mipv6-02.txt.
> > > >
> > > 
> > > I have some concerns with this. As I understand, please correct me if I am
> > > wrong, BETH
> > > relies on link-layer triggers to establish the bi-directional tunnel. The
> > > link-layer triggers are
> > > 
> > > - not standarized. Who will do the standardization ?
> > > - not implemented (I guess since there is no standard). Any comments ?
> > > 
> > > Given this dependence, having BETH as a part of FMIPv6 raises the following
> > > issues
> > > 
> > > - how can we implement FMIPv6 with BETH ?
> > > - how can we test inter-operability ?
> > > 
> > > So, I feel that FMIPv6 should contain enough specification that can become a
> > > standard without depending on link-layer trigger standardization to succeed. 
> We
> > > are keen on moving FMIPv6 along, and would welcome new ideas that would 
> improve
> > > the protocol. However, items that would require standardization of their own
> > > should perhaps be part of a separate document, and (still) be recognized in 
> the
> > > FMIPv6 specification.
> > > 
> > > Comments ?
> > > 
> > > 
> > > Regards,
> > > 
> > > -Rajeev
> > > 
> > > 
> > > 
> > > 
> > > >
> > > >                 jak
> 
> alper


From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep 14 13:03:07 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21982
	for <mobileip-archive@odin.ietf.org>; Fri, 14 Sep 2001 13:03:06 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA02638;
	Fri, 14 Sep 2001 10:00:44 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA06413;
	Fri, 14 Sep 2001 09:20:49 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8EGJ67B002190
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 14 Sep 2001 09:19:06 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8EGJ6xd002189
	for mobile-ip-dist; Fri, 14 Sep 2001 09:19:06 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from heliopolis.eng.sun.com (redhook.Eng.Sun.COM [152.70.24.37])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8EGJ37B002182
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 14 Sep 2001 09:19:03 -0700 (PDT)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.eng.sun.com (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id JAA10309
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 14 Sep 2001 09:19:25 -0700 (PDT)
Message-Id: <200109141619.JAA10309@heliopolis.eng.sun.com>
Date: Fri, 14 Sep 2001 09:19:23 -0700 (PDT)
From: James Kempf <James.Kempf@Sun.COM>
Subject: Re: [mobile-ip] New BETH Draft
To: mobile-ip@sunroof.eng.sun.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: V7tMX3JFHl2Qs6iVgu5+VQ==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Hi Alper,


>Right before the last IETF we had discussed how handoff would work when nAR 
>doesn't support the BETH protocol.
>
>I think you have added section 2.5.3 Failure of BET Handover to address this 
>issue, right?
>

Yes, that's correct. 

>I have a question on how this works:
>
>	If the candidate cannot support BETH, then the current AR
>	should initiate FMIPv6 handover if the candidate supports it, or, if
>	the candidate AR does not support FMIPv6, simply allow the MN to do
>	movement detection according to the original Johnson and Perkins
>	algorithm.
>	
>If the nAR doesn't support neither BETH nor FMIPv6, then how is MN supposed to 
>detect this and proceed with a stock handoff? 
>

Good question, but this isn't specifically an issue with BETH. What
happens if the current AR supports stock FMIPv6 and the new AR
doesn't? This issue isn't covered in the FMIPv6 draft.

>I think it would be useful to have a section that describes MN behavior, 
>especially under these different cases.
>

Agree.

In the case of BETH, if nAR doesn't support BETH, then it will use
the standard Johnson and Perkins algorithm, by which nAR will advertise
a RtAdv when the MN is already on the new L2 and the MN will respond 
when the RtAdv is received. Note that performance here may not be particularly 
fast if the RtAdv is periodically sent. If the nAR uses an L2 trigger rather 
than a timer to send the RtAdv, it can catch the MN as soon as L2 handover is 
complete. If the MN receives an L2 trigger, of course, it may choose to wait 
until the nAR sends the RtAdv rather than soliciting if it has a real time 
stream, because it doesn't know, a priori, that the nAR doesn't support
BETH. The stream may then get disrupted if the MN doesn't receive
the RtAdv quickly enough.

In the case of FMIPv6, pretty much the same thing will happen, except
if the MN gets an L2 trigger, it will start the process of L3 handover
when it gets the L2 trigger rather than waiting. If the MN doesn't
get an L2 trigger, and the nAR does timer-based route advertisement,
the same kind of disruptions in the real time stream will occur.

These cases assume that the oAR does nothing to inform the MN prior
to the handover that a handover is coming up. 

Performance would probably benefit by allowing the oAR to signal the MN
when it is still on the oAR that a handover to a nonFMIPv6/nonBETH
capable node is pending. This would allow a MN that is using either
algorithm to revert to the standard Johnson and Perkins algorithm
for movement detection, according to its ability to receive
an L2 trigger. If the MN receives an L2 trigger, it can send
a SolRtAdv as soon as it is on the nAR, if not, it must wait
until the RtAdv is sent from the nAR. 

A good place to add support for this would be the PrxyRtAdv. The 
PrxyRtAdv currently has three codes, we could add one like:

	2 - Handover to nonFMIPv6/nonBETH capable AR pending
	
This would be sent when the oAR has knowledge of the capabilities
of the nAR, to allow MNs to optimize handover as much as possible.

Of course, if nAR doesn't have such knowledge, it could send
a 128 (New attachment point unknown), indicating the MN is basically
on its own.

		jak



From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep 14 13:59:04 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23360
	for <mobileip-archive@odin.ietf.org>; Fri, 14 Sep 2001 13:59:03 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id LAA06854;
	Fri, 14 Sep 2001 11:58:12 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id KAA02377;
	Fri, 14 Sep 2001 10:58:01 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8EHuH7B002298
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 14 Sep 2001 10:56:17 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8EHuHqN002297
	for mobile-ip-dist; Fri, 14 Sep 2001 10:56:17 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8EHuD7B002290
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 14 Sep 2001 10:56:13 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id KAA01913
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 14 Sep 2001 10:56:33 -0700 (PDT)
Received: from mgw-dax2.ext.nokia.com (mgw-dax2.ext.nokia.com [63.78.179.217])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA13134
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 14 Sep 2001 11:57:16 -0600 (MDT)
Received: from davir02nok.americas.nokia.com (davir02nok.americas.nokia.com [172.18.242.85])
	by mgw-dax2.ext.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f8EHubC13248
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 14 Sep 2001 12:56:37 -0500 (CDT)
Received: from daebh002.NOE.Nokia.com (unverified) by davir02nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T55fd32e4bcac12f255079@davir02nok.americas.nokia.com>;
 Fri, 14 Sep 2001 12:56:31 -0500
Received: from daebe007.NOE.Nokia.com ([172.18.242.211]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.2966);
	 Fri, 14 Sep 2001 12:56:30 -0500
content-class: urn:content-classes:message
Subject: RE: [mobile-ip] New BETH Draft
Date: Fri, 14 Sep 2001 12:56:30 -0500
Message-ID: <697DAA22C5004B4596E033803A7CEF441E8683@daebe007.NOE.Nokia.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Thread-Topic: [mobile-ip] New BETH Draft
X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0
Thread-Index: AcE9OWoxSXln/KkqEdWrxAAIx6S5QwADQyNg
From: "Patil Basavaraj (NET/Dallas)" <Basavaraj.Patil@nokia.com>
To: <mobile-ip@sunroof.eng.sun.com>
Cc: "'James kempf'" <James.Kempf@Sun.COM>
X-OriginalArrivalTime: 14 Sep 2001 17:56:30.0745 (UTC) FILETIME=[95734890:01C13D46]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by sunroof.eng.sun.com id f8EHuE7B002291
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 8bit


>In the case of BETH, if nAR doesn't support BETH, then it will use
>the standard Johnson and Perkins algorithm, by which nAR will advertise
>a RtAdv when the MN is already on the new L2 and the MN will respond 
>when the RtAdv is received. Note that performance here may not be
>particularly fast if the RtAdv is periodically sent. 

The MN need not wait for the RtAdv. It can solicit it. So you can
improve performance to some extent that way.

>If the nAR uses an L2 trigger rather 
>than a timer to send the RtAdv, it can catch the MN as soon as L2
handover is 
>complete. If the MN receives an L2 trigger, of course, it may choose to
wait 
>until the nAR sends the RtAdv rather than soliciting if it has a real
time 
>stream, because it doesn't know, a priori, that the nAR doesn't support
>BETH. The stream may then get disrupted if the MN doesn't receive
>the RtAdv quickly enough.

According to BETH the MN will not know if a handover is occuring in
the network at any time. So it would be too much to ask the MN to NOT
react to an L2 trigger by sending a RtAdv solict right away. The MN
has no idea if the ARs support BETH at any given time.

>In the case of FMIPv6, pretty much the same thing will happen, except
>if the MN gets an L2 trigger, it will start the process of L3 handover
>when it gets the L2 trigger rather than waiting. If the MN doesn't
>get an L2 trigger, and the nAR does timer-based route advertisement,
>the same kind of disruptions in the real time stream will occur.

The fallback of the FMIPv6 scheme in case of trigger failures etc. is
the standard Johnson/Perkins algorithm. There is not much you can
really do. And trying to synchronize your L2 and L3 handoffs via
triggers etc. is not exactly the easiest thing done.

>These cases assume that the oAR does nothing to inform the MN prior
>to the handover that a handover is coming up. 
>Performance would probably benefit by allowing the oAR to signal the MN
>when it is still on the oAR that a handover to a nonFMIPv6/nonBETH
>capable node is pending. 

Most cases the L2 HO will have already occured and the oAR will have
no means of telling the MN anything. 
If the MN sends a PrRtrSolicit to the oAR (assuming a Mob. Initiated
HO via some trigger in the MN) and the oAR has no knowledge
about the capabilities of the new AP/AR that the MN is indicating in
the PrRtrSolict, the oAR may not even be able to respond to the
solicit before the MN completes the L2 HO. 

>This would allow a MN that is using either
>algorithm to revert to the standard Johnson and Perkins algorithm
>for movement detection, according to its ability to receive
>an L2 trigger. If the MN receives an L2 trigger, it can send
>a SolRtAdv as soon as it is on the nAR, if not, it must wait
>until the RtAdv is sent from the nAR. 

The L2 movement detection (or change of AP) and it's use via triggers
to cause a RtrSolicit is something that the MN should do anyway to
proactively determine movement detection and the AR that it is
connected to. This is something that can be done with the MIPv6 spec
as is without having to do anything with FMIPv6. 

>A good place to add support for this would be the PrxyRtAdv. The 
>PrxyRtAdv currently has three codes, we could add one like:
>
>	2 - Handover to nonFMIPv6/nonBETH capable AR pending
>

If the MN is going to HO to an AP/AR that is not in the HO domain of
the oAR, it probably has no idea of the MNs intent to HO and is
incapable of sending the PrRtrAdv. It has to be Mobile initiated. 
Can you elaborate on a viable scenario where this message would be
required?
	
>This would be sent when the oAR has knowledge of the capabilities
>of the nAR, to allow MNs to optimize handover as much as possible.

The oAR can know the capabilities of the nAR only if the MN tells it via
the PrRtSolicit. Unless your triggers and timing are synchronized the
MN could be gone. However the spec may be able to use a NAK to the
PrRtSolicit to say no HOs are possible to the AR specified in the
PrRtrSolict. But I guess that's what you are suggesting.

>Of course, if nAR doesn't have such knowledge, it could send
>a 128 (New attachment point unknown), indicating the MN is basically
>on its own.

Exactly. Just keep it simple. I think we are saying the same thing to
some extent in this thread.

The point is how closely are you or can you synchronize your L2/L3 HOs
via triggers. It may be better to keep the solution relatively simple
and rely on the fallback algorithm.

>
>		jak
>
-Basavaraj


From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep 14 14:36:59 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24268
	for <mobileip-archive@odin.ietf.org>; Fri, 14 Sep 2001 14:36:58 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA17531;
	Fri, 14 Sep 2001 11:35:14 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id LAA08508;
	Fri, 14 Sep 2001 11:28:04 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8EIQk7B002361
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 14 Sep 2001 11:26:46 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8EIQkSB002360
	for mobile-ip-dist; Fri, 14 Sep 2001 11:26:46 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from jurassic.eng.sun.com (jurassic [129.146.88.130] (may be forged))
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8EIQg7B002353
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 14 Sep 2001 11:26:42 -0700 (PDT)
Received: from istanbul.Eng.Sun.COM (istanbul.Eng.Sun.COM [129.146.86.247])
	by jurassic.eng.sun.com (8.12.0+Sun/8.12.0) with SMTP id f8EIR3Vj594316
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 14 Sep 2001 11:27:03 -0700 (PDT)
Message-Id: <200109141827.f8EIR3Vj594316@jurassic.eng.sun.com>
Date: Fri, 14 Sep 2001 11:26:56 -0700 (PDT)
From: Alper Yegin <Alper.Yegin@eng.sun.com>
Subject: RE: [mobile-ip] New BETH Draft
To: mobile-ip@sunroof.eng.sun.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: zVJqFKotu3xXY1zXAs0TcQ==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4_37 SunOS 5.8.1 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Hesham,

I was comparing FMIPv6 and under what minimal L2 signals it can work, vs BETH 
and its L2 signal requirements. But thinking BETH as one of the cases under 
FMIPv6 umbrella, I agree with your points.

alper


> X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to 
owner-mobile-ip@sunroof.eng.sun.com using -f
> To: "'mobile-ip@sunroof.eng.sun.com'" <mobile-ip@sunroof.eng.sun.com>
> Subject: RE: [mobile-ip] New BETH Draft
> MIME-Version: 1.0
> List-Archive: <http://playground.sun.com/mobile-ip/>
> List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
> List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
> List-Unsubscribe: 
<mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe> Alper, 
> 
> > We should still distinguish among different triggers though. For example 
FMIPv6 
> > can operate even if the only triggers available are on the Mobile Node. On 
some 
> > links, such as WLAN, some of the AR side triggers might not exist, e.g. LINK 
> > DOWN. And this effects the availability of BETH to those networks.
> > 
> 	=> Of course, the triggers are in the MN or the AR depending on the 
> 	type of radio that you have. But they are all triggers based on L2
> 	events. So I guess we're saying the same thing. FMIPv4/6 relies 
> 	on these triggers for all scenarios. Network initiation or MN initiation
> 	is independant.
> 
> > FMIPv6's reliance on the L2 triggers is less than that of BETH.
> > 
> 	=> It is actually a third scenario in FMIPv6, the reliance on 
> 	triggers is identical to the case where the AR sends Pr_rtradv
> 	I don't see why you say that. The difference here is that the MN
> 	doesn't know, which is something we can debate, but anyhow
> 	this is not the issue on this thread. 
> 
> > But of course, as James said, one should use BETH only if they have support 
for 
> > these triggers.. If they don't, they can't. That simple.
> > 
> 	=> Exactly, but it's the same scenario for the case where the 
> 	AR sends an unsolicited Pr_rtr_adv. I don't see the difference.
> 
> 	Hesham
> 
> 
> > > 
> > > 
> > > > > As agreed upon in London, unless there are any further changes needed,
> > > > > I'd like to move forward with Gopal on incorporating the draft
> > > > > into the body of draft-ietf-mobileip-fast-mipv6-02.txt.
> > > > >
> > > > 
> > > > I have some concerns with this. As I understand, please correct me if I 
am
> > > > wrong, BETH
> > > > relies on link-layer triggers to establish the bi-directional tunnel. 
The
> > > > link-layer triggers are
> > > > 
> > > > - not standarized. Who will do the standardization ?
> > > > - not implemented (I guess since there is no standard). Any comments ?
> > > > 
> > > > Given this dependence, having BETH as a part of FMIPv6 raises the 
following
> > > > issues
> > > > 
> > > > - how can we implement FMIPv6 with BETH ?
> > > > - how can we test inter-operability ?
> > > > 
> > > > So, I feel that FMIPv6 should contain enough specification that can 
become a
> > > > standard without depending on link-layer trigger standardization to 
succeed. 
> > We
> > > > are keen on moving FMIPv6 along, and would welcome new ideas that would 
> > improve
> > > > the protocol. However, items that would require standardization of their 
own
> > > > should perhaps be part of a separate document, and (still) be recognized 
in 
> > the
> > > > FMIPv6 specification.
> > > > 
> > > > Comments ?
> > > > 
> > > > 
> > > > Regards,
> > > > 
> > > > -Rajeev
> > > > 
> > > > 
> > > > 
> > > > 
> > > > >
> > > > >                 jak
> > 
> > alper

alper



From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep 14 15:10:32 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24846
	for <mobileip-archive@odin.ietf.org>; Fri, 14 Sep 2001 15:10:31 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id NAA08055;
	Fri, 14 Sep 2001 13:09:40 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id MAA09411;
	Fri, 14 Sep 2001 12:09:34 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8EJ8I7B002525
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 14 Sep 2001 12:08:18 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8EJ8IYp002524
	for mobile-ip-dist; Fri, 14 Sep 2001 12:08:18 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from heliopolis.eng.sun.com (redcoast.Eng.Sun.COM [152.70.28.21])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8EJ8F7B002517
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 14 Sep 2001 12:08:15 -0700 (PDT)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.eng.sun.com (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id MAA16946;
	Fri, 14 Sep 2001 12:08:36 -0700 (PDT)
Message-Id: <200109141908.MAA16946@heliopolis.eng.sun.com>
Date: Fri, 14 Sep 2001 12:08:35 -0700 (PDT)
From: James Kempf <James.Kempf@sun.com>
Subject: RE: [mobile-ip] New BETH Draft
To: mobile-ip@sunroof.eng.sun.com, Basavaraj.Patil@nokia.com
Cc: James.Kempf@sun.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: emchiMNLz5IGA4M68pmD2w==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Hi Raj,

I guess my original  email wasn't very clear, sorry. Responses below.

>
>>In the case of BETH, if nAR doesn't support BETH, then it will use
>>the standard Johnson and Perkins algorithm, by which nAR will advertise
>>a RtAdv when the MN is already on the new L2 and the MN will respond 
>>when the RtAdv is received. Note that performance here may not be
>>particularly fast if the RtAdv is periodically sent. 
>
>The MN need not wait for the RtAdv. It can solicit it. So you can
>improve performance to some extent that way.
>

Agree. The issue here is that, if the MN doesn't know that it is
being handed off to an AR that can't do FMIPv6 and can't do 
BETH, it may try to optimize by doing BETH, and then it won't
solicit. That prompted the suggestion to inform the MN prior
to movement, via the standard FMIPv6 PrxyRtAdv, that it was
about to move into a nonFMIPv6, nonBETH coverage area, if that
fact is known  in advance of the handover.

>>If the nAR uses an L2 trigger rather 
>>than a timer to send the RtAdv, it can catch the MN as soon as L2
>handover is 
>>complete. If the MN receives an L2 trigger, of course, it may choose to
>wait 
>>until the nAR sends the RtAdv rather than soliciting if it has a real
>time 
>>stream, because it doesn't know, a priori, that the nAR doesn't support
>>BETH. The stream may then get disrupted if the MN doesn't receive
>>the RtAdv quickly enough.
>
>According to BETH the MN will not know if a handover is occuring in
>the network at any time. So it would be too much to ask the MN to NOT
>react to an L2 trigger by sending a RtAdv solict right away. The MN
>has no idea if the ARs support BETH at any given time.
>

Even if the MN is using BETH, at some point, it must solicit a RtAdv
or PrxyRtAdv and initiate L3 handover, so that it can get a new
CoA. If the MN gets an L2 trigger prior to or after handover, it
can use that to gate when to begin L3 handover, just as in FMIPv6
and standard MIPv6. If the MN does not get an L2 trigger, it will
simply solicit whenever its real time stream is done.

>>In the case of FMIPv6, pretty much the same thing will happen, except
>>if the MN gets an L2 trigger, it will start the process of L3 handover
>>when it gets the L2 trigger rather than waiting. If the MN doesn't
>>get an L2 trigger, and the nAR does timer-based route advertisement,
>>the same kind of disruptions in the real time stream will occur.
>
>The fallback of the FMIPv6 scheme in case of trigger failures etc. is
>the standard Johnson/Perkins algorithm. There is not much you can
>really do. 

Agree in general, but I think you can warn the MN if the old AR knows what's
coming.

>And trying to synchronize your L2 and L3 handoffs via
>triggers etc. is not exactly the easiest thing done.
>

Well, the goal of the triggers is to provide timely and accurate
L2 sequencing information from L2 to L3, so as to optimize L3 handover.
If they don't achieve that, then they are of no use.

>>These cases assume that the oAR does nothing to inform the MN prior
>>to the handover that a handover is coming up. 
>>Performance would probably benefit by allowing the oAR to signal the MN
>>when it is still on the oAR that a handover to a nonFMIPv6/nonBETH
>>capable node is pending. 
>
>Most cases the L2 HO will have already occured and the oAR will have
>no means of telling the MN anything. 

The oAR may know that a handover is coming, and it may even know
where, or, as you say, it may not. If it knows, it could potentially
send a PrxyRtAdv to the MN. Also, the MN may know that the handover
is coming.

>If the MN sends a PrRtrSolicit to the oAR (assuming a Mob. Initiated
>HO via some trigger in the MN) and the oAR has no knowledge
>about the capabilities of the new AP/AR that the MN is indicating in
>the PrRtrSolict, the oAR may not even be able to respond to the
>solicit before the MN completes the L2 HO. 
>

Agree. This is the worst case.

>>This would allow a MN that is using either
>>algorithm to revert to the standard Johnson and Perkins algorithm
>>for movement detection, according to its ability to receive
>>an L2 trigger. If the MN receives an L2 trigger, it can send
>>a SolRtAdv as soon as it is on the nAR, if not, it must wait
>>until the RtAdv is sent from the nAR. 
>
>The L2 movement detection (or change of AP) and it's use via triggers
>to cause a RtrSolicit is something that the MN should do anyway to
>proactively determine movement detection and the AR that it is
>connected to. This is something that can be done with the MIPv6 spec
>as is without having to do anything with FMIPv6. 
>

If the MN is doing BETH, then it will be supressing solicitation of
RtAdv in order to conserve radio bandwidth, so it would have
to wait for the nAR to send a RtAdv instead of soliciting. Maybe
not all that bad, but if the oAR knows where the MN is going,
it could tell the MN ahead of time to solicit.

>>A good place to add support for this would be the PrxyRtAdv. The 
>>PrxyRtAdv currently has three codes, we could add one like:
>>
>>	2 - Handover to nonFMIPv6/nonBETH capable AR pending
>>
>
>If the MN is going to HO to an AP/AR that is not in the HO domain of
>the oAR, it probably has no idea of the MNs intent to HO and is
>incapable of sending the PrRtrAdv. It has to be Mobile initiated. 
>Can you elaborate on a viable scenario where this message would be
>required?
>

Please see draft-ietf-seamoby-CARdiscovery-issues-00.txt. Seamoby
is working on a protocol to allow ARs to advertise their capabilities.
One such might be whether or not they support FMIPv6 and BETH. 
	
>>This would be sent when the oAR has knowledge of the capabilities
>>of the nAR, to allow MNs to optimize handover as much as possible.
>
>The oAR can know the capabilities of the nAR only if the MN tells it via
>the PrRtSolicit. Unless your triggers and timing are synchronized the
>MN could be gone. However the spec may be able to use a NAK to the
>PrRtSolicit to say no HOs are possible to the AR specified in the
>PrRtrSolict. But I guess that's what you are suggesting.
>

The CAR discovery draft outlines two possible ways an AR can discover
the capabilites, one that involves exchanging information over the
wired backbone and one that involves exchanging information via the MN.
The oAR can discover the capabilities of the nAR without the MN's 
involvement and inform the MN prior to handover.

>>Of course, if nAR doesn't have such knowledge, it could send
>>a 128 (New attachment point unknown), indicating the MN is basically
>>on its own.
>
>Exactly. Just keep it simple. I think we are saying the same thing to
>some extent in this thread.
>

Agree. The only point I'm trying to make is that, as with the entire
rest of FMIPv6, if the oAR has information about the capabilities of the AR 
where the MN is going, it is possible to optimize handover. It need not
depend on CAR discovery, the information could be statically configured,
but that is an example.

>The point is how closely are you or can you synchronize your L2/L3 HOs
>via triggers. It may be better to keep the solution relatively simple
>and rely on the fallback algorithm.

Not entirely sure what your point is here, since the L2 triggers are
just presenting sequencing information and parameters to L3, which
then uses them for optimizing handover. Of course, if the L2 information
is not there, it is not possible to do the optimization. This
is like any other optimization problem. Or am I missing something?

		jak



From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep 14 15:49:10 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25376
	for <mobileip-archive@odin.ietf.org>; Fri, 14 Sep 2001 15:49:09 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id NAA05129;
	Fri, 14 Sep 2001 13:48:15 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id MAA18382;
	Fri, 14 Sep 2001 12:47:53 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8EJjr7B002604
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 14 Sep 2001 12:45:53 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8EJjrAv002603
	for mobile-ip-dist; Fri, 14 Sep 2001 12:45:53 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8EJjn7B002596
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 14 Sep 2001 12:45:49 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id MAA29318
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 14 Sep 2001 12:46:05 -0700 (PDT)
Received: from fluorine.mcis.singnet.com.sg (fluorine.singnet.com.sg [165.21.74.72])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id NAA03507
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 14 Sep 2001 13:45:59 -0600 (MDT)
Received: from mail pickup service by fluorine.mcis.singnet.com.sg with Microsoft SMTPSVC;
	 Sat, 15 Sep 2001 03:45:02 +0800
Received: from mx11.singnet.com.sg ([165.21.74.121]) by fluorine.mcis.singnet.com.sg  with Microsoft SMTPSVC(5.5.1877.687.68);
	 Sat, 15 Sep 2001 02:32:19 +0800
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by mx11.singnet.com.sg (8.11.5/8.11.5) with ESMTP id f8EIWCM26483
	for <haushian@singnet.com.sg>; Sat, 15 Sep 2001 02:32:13 +0800
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA14266;
	Fri, 14 Sep 2001 11:28:34 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id LAA08604;
	Fri, 14 Sep 2001 11:28:29 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8EIQk7B002361
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 14 Sep 2001 11:26:46 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8EIQkSB002360
	for mobile-ip-dist; Fri, 14 Sep 2001 11:26:46 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from jurassic.eng.sun.com (jurassic [129.146.88.130] (may be forged))
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8EIQg7B002353
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 14 Sep 2001 11:26:42 -0700 (PDT)
Received: from istanbul.Eng.Sun.COM (istanbul.Eng.Sun.COM [129.146.86.247])
	by jurassic.eng.sun.com (8.12.0+Sun/8.12.0) with SMTP id f8EIR3Vj594316
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 14 Sep 2001 11:27:03 -0700 (PDT)
Message-Id: <200109141827.f8EIR3Vj594316@jurassic.eng.sun.com>
Date: Fri, 14 Sep 2001 11:26:56 -0700 (PDT)
From: Alper Yegin <Alper.Yegin@eng.sun.com>
Subject: RE: [mobile-ip] New BETH Draft
To: mobile-ip@sunroof.eng.sun.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: zVJqFKotu3xXY1zXAs0TcQ==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4_37 SunOS 5.8.1 sun4u sparc 
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Hesham,

I was comparing FMIPv6 and under what minimal L2 signals it can work, vs BETH 
and its L2 signal requirements. But thinking BETH as one of the cases under 
FMIPv6 umbrella, I agree with your points.

alper


> X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to 
owner-mobile-ip@sunroof.eng.sun.com using -f
> To: "'mobile-ip@sunroof.eng.sun.com'" <mobile-ip@sunroof.eng.sun.com>
> Subject: RE: [mobile-ip] New BETH Draft
> MIME-Version: 1.0
> List-Archive: <http://playground.sun.com/mobile-ip/>
> List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
> List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
> List-Unsubscribe: 
<mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe> Alper, 
> 
> > We should still distinguish among different triggers though. For example 
FMIPv6 
> > can operate even if the only triggers available are on the Mobile Node. On 
some 
> > links, such as WLAN, some of the AR side triggers might not exist, e.g. LINK 
> > DOWN. And this effects the availability of BETH to those networks.
> > 
> 	=> Of course, the triggers are in the MN or the AR depending on the 
> 	type of radio that you have. But they are all triggers based on L2
> 	events. So I guess we're saying the same thing. FMIPv4/6 relies 
> 	on these triggers for all scenarios. Network initiation or MN initiation
> 	is independant.
> 
> > FMIPv6's reliance on the L2 triggers is less than that of BETH.
> > 
> 	=> It is actually a third scenario in FMIPv6, the reliance on 
> 	triggers is identical to the case where the AR sends Pr_rtradv
> 	I don't see why you say that. The difference here is that the MN
> 	doesn't know, which is something we can debate, but anyhow
> 	this is not the issue on this thread. 
> 
> > But of course, as James said, one should use BETH only if they have support 
for 
> > these triggers.. If they don't, they can't. That simple.
> > 
> 	=> Exactly, but it's the same scenario for the case where the 
> 	AR sends an unsolicited Pr_rtr_adv. I don't see the difference.
> 
> 	Hesham
> 
> 
> > > 
> > > 
> > > > > As agreed upon in London, unless there are any further changes needed,
> > > > > I'd like to move forward with Gopal on incorporating the draft
> > > > > into the body of draft-ietf-mobileip-fast-mipv6-02.txt.
> > > > >
> > > > 
> > > > I have some concerns with this. As I understand, please correct me if I 
am
> > > > wrong, BETH
> > > > relies on link-layer triggers to establish the bi-directional tunnel. 
The
> > > > link-layer triggers are
> > > > 
> > > > - not standarized. Who will do the standardization ?
> > > > - not implemented (I guess since there is no standard). Any comments ?
> > > > 
> > > > Given this dependence, having BETH as a part of FMIPv6 raises the 
following
> > > > issues
> > > > 
> > > > - how can we implement FMIPv6 with BETH ?
> > > > - how can we test inter-operability ?
> > > > 
> > > > So, I feel that FMIPv6 should contain enough specification that can 
become a
> > > > standard without depending on link-layer trigger standardization to 
succeed. 
> > We
> > > > are keen on moving FMIPv6 along, and would welcome new ideas that would 
> > improve
> > > > the protocol. However, items that would require standardization of their 
own
> > > > should perhaps be part of a separate document, and (still) be recognized 
in 
> > the
> > > > FMIPv6 specification.
> > > > 
> > > > Comments ?
> > > > 
> > > > 
> > > > Regards,
> > > > 
> > > > -Rajeev
> > > > 
> > > > 
> > > > 
> > > > 
> > > > >
> > > > >                 jak
> > 
> > alper

alper


From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep 14 16:09:56 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25765
	for <mobileip-archive@odin.ietf.org>; Fri, 14 Sep 2001 16:09:56 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id OAA19465;
	Fri, 14 Sep 2001 14:09:04 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id NAA02352;
	Fri, 14 Sep 2001 13:09:03 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8EK7e7B002971
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 14 Sep 2001 13:07:40 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8EK7eYX002970
	for mobile-ip-dist; Fri, 14 Sep 2001 13:07:40 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8EK7a7B002963
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 14 Sep 2001 13:07:36 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id NAA02056
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 14 Sep 2001 13:07:58 -0700 (PDT)
Received: from tellurium.mcis.singnet.com.sg (tellurium.singnet.com.sg [165.21.74.71])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id OAA18396
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 14 Sep 2001 14:07:52 -0600 (MDT)
Received: from mail pickup service by tellurium.mcis.singnet.com.sg with Microsoft SMTPSVC;
	 Sat, 15 Sep 2001 04:05:28 +0800
Received: from mx18.singnet.com.sg ([165.21.74.118]) by tellurium.mcis.singnet.com.sg  with Microsoft SMTPSVC(5.5.1877.687.68);
	 Sat, 15 Sep 2001 00:32:34 +0800
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by mx18.singnet.com.sg (8.11.5/8.11.5) with ESMTP id f8EGMaC30408
	for <haushian@singnet.com.sg>; Sat, 15 Sep 2001 00:23:00 +0800
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id KAA11028;
	Fri, 14 Sep 2001 10:21:39 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA06583;
	Fri, 14 Sep 2001 09:21:37 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8EGJ67B002190
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 14 Sep 2001 09:19:06 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8EGJ6xd002189
	for mobile-ip-dist; Fri, 14 Sep 2001 09:19:06 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from heliopolis.eng.sun.com (redhook.Eng.Sun.COM [152.70.24.37])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8EGJ37B002182
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 14 Sep 2001 09:19:03 -0700 (PDT)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.eng.sun.com (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id JAA10309
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 14 Sep 2001 09:19:25 -0700 (PDT)
Message-Id: <200109141619.JAA10309@heliopolis.eng.sun.com>
Date: Fri, 14 Sep 2001 09:19:23 -0700 (PDT)
From: James Kempf <James.Kempf@Sun.COM>
Subject: Re: [mobile-ip] New BETH Draft
To: mobile-ip@sunroof.eng.sun.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: V7tMX3JFHl2Qs6iVgu5+VQ==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Hi Alper,


>Right before the last IETF we had discussed how handoff would work when nAR 
>doesn't support the BETH protocol.
>
>I think you have added section 2.5.3 Failure of BET Handover to address this 
>issue, right?
>

Yes, that's correct. 

>I have a question on how this works:
>
>	If the candidate cannot support BETH, then the current AR
>	should initiate FMIPv6 handover if the candidate supports it, or, if
>	the candidate AR does not support FMIPv6, simply allow the MN to do
>	movement detection according to the original Johnson and Perkins
>	algorithm.
>	
>If the nAR doesn't support neither BETH nor FMIPv6, then how is MN supposed to 
>detect this and proceed with a stock handoff? 
>

Good question, but this isn't specifically an issue with BETH. What
happens if the current AR supports stock FMIPv6 and the new AR
doesn't? This issue isn't covered in the FMIPv6 draft.

>I think it would be useful to have a section that describes MN behavior, 
>especially under these different cases.
>

Agree.

In the case of BETH, if nAR doesn't support BETH, then it will use
the standard Johnson and Perkins algorithm, by which nAR will advertise
a RtAdv when the MN is already on the new L2 and the MN will respond 
when the RtAdv is received. Note that performance here may not be particularly 
fast if the RtAdv is periodically sent. If the nAR uses an L2 trigger rather 
than a timer to send the RtAdv, it can catch the MN as soon as L2 handover is 
complete. If the MN receives an L2 trigger, of course, it may choose to wait 
until the nAR sends the RtAdv rather than soliciting if it has a real time 
stream, because it doesn't know, a priori, that the nAR doesn't support
BETH. The stream may then get disrupted if the MN doesn't receive
the RtAdv quickly enough.

In the case of FMIPv6, pretty much the same thing will happen, except
if the MN gets an L2 trigger, it will start the process of L3 handover
when it gets the L2 trigger rather than waiting. If the MN doesn't
get an L2 trigger, and the nAR does timer-based route advertisement,
the same kind of disruptions in the real time stream will occur.

These cases assume that the oAR does nothing to inform the MN prior
to the handover that a handover is coming up. 

Performance would probably benefit by allowing the oAR to signal the MN
when it is still on the oAR that a handover to a nonFMIPv6/nonBETH
capable node is pending. This would allow a MN that is using either
algorithm to revert to the standard Johnson and Perkins algorithm
for movement detection, according to its ability to receive
an L2 trigger. If the MN receives an L2 trigger, it can send
a SolRtAdv as soon as it is on the nAR, if not, it must wait
until the RtAdv is sent from the nAR. 

A good place to add support for this would be the PrxyRtAdv. The 
PrxyRtAdv currently has three codes, we could add one like:

	2 - Handover to nonFMIPv6/nonBETH capable AR pending
	
This would be sent when the oAR has knowledge of the capabilities
of the nAR, to allow MNs to optimize handover as much as possible.

Of course, if nAR doesn't have such knowledge, it could send
a 128 (New attachment point unknown), indicating the MN is basically
on its own.

		jak


From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep 14 17:33:29 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26868
	for <mobileip-archive@odin.ietf.org>; Fri, 14 Sep 2001 17:33:28 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id OAA00109;
	Fri, 14 Sep 2001 14:32:36 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id OAA11758;
	Fri, 14 Sep 2001 14:32:30 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8ELUp7B003439
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 14 Sep 2001 14:30:51 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8ELUpdR003438
	for mobile-ip-dist; Fri, 14 Sep 2001 14:30:51 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from jurassic.eng.sun.com (jurassic [129.146.89.50] (may be forged))
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8ELUm7B003431
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 14 Sep 2001 14:30:48 -0700 (PDT)
Received: from istanbul.Eng.Sun.COM (istanbul.Eng.Sun.COM [129.146.86.247])
	by jurassic.eng.sun.com (8.12.0+Sun/8.12.0) with SMTP id f8ELV8Vj631688;
	Fri, 14 Sep 2001 14:31:08 -0700 (PDT)
Message-Id: <200109142131.f8ELV8Vj631688@jurassic.eng.sun.com>
Date: Fri, 14 Sep 2001 14:31:01 -0700 (PDT)
From: Alper Yegin <Alper.Yegin@eng.sun.com>
Subject: Re: [mobile-ip] New BETH Draft
To: mobile-ip@sunroof.eng.sun.com
Cc: gdommety@cisco.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: dsNTWque0HNQLI2DGWQLAA==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4_37 SunOS 5.8.1 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Hi Jim,

> Hi Alper,
> 
> 
> >Right before the last IETF we had discussed how handoff would work when nAR 
> >doesn't support the BETH protocol.
> >
> >I think you have added section 2.5.3 Failure of BET Handover to address this 
> >issue, right?
> >
> 
> Yes, that's correct. 
> 
> >I have a question on how this works:
> >
> >	If the candidate cannot support BETH, then the current AR
> >	should initiate FMIPv6 handover if the candidate supports it, or, if
> >	the candidate AR does not support FMIPv6, simply allow the MN to do
> >	movement detection according to the original Johnson and Perkins
> >	algorithm.
> >	
> >If the nAR doesn't support neither BETH nor FMIPv6, then how is MN supposed 
to 
> >detect this and proceed with a stock handoff? 
> >
> 
> Good question, but this isn't specifically an issue with BETH. What
> happens if the current AR supports stock FMIPv6 and the new AR
> doesn't? This issue isn't covered in the FMIPv6 draft.

PrRtAdv can indicate this. I am not sure if we have clarified this in the draft 
(therefore CC'ing the editor). Two-way communication between MN and the ARs help 
here. So, I don't see an issue for FMIPv6 here.


> 
> >I think it would be useful to have a section that describes MN behavior, 
> >especially under these different cases.
> >
> 
> Agree.
> 
> In the case of BETH, if nAR doesn't support BETH, then it will use
> the standard Johnson and Perkins algorithm, by which nAR will advertise
> a RtAdv when the MN is already on the new L2 and the MN will respond 
> when the RtAdv is received. 

But it's not standard that AR will send an RA as soon as a MN attaches. And this 
can't be accomplished by a requirement by BETH, because at least this AR is not 
supporting BETH.

I don't think you can rely on nAR sending RA or not sending to figure out BETH 
support on ARs.

Also, for any new message between the MN and the AR, I think you are diverging 
from your goal of zero latency, which relies on no-L3 traffic.

Note that FMIPv6 can get away without any L3 signalling on the new link. As both 
MN and nAR know each other's L2 identity, L2 attachment signal is enough get 
traffic going.


> Note that performance here may not be particularly 
> fast if the RtAdv is periodically sent. If the nAR uses an L2 trigger rather 
> than a timer to send the RtAdv, it can catch the MN as soon as L2 handover is 
> complete. If the MN receives an L2 trigger, of course, it may choose to wait 
> until the nAR sends the RtAdv rather than soliciting if it has a real time 
> stream, because it doesn't know, a priori, that the nAR doesn't support
> BETH. The stream may then get disrupted if the MN doesn't receive
> the RtAdv quickly enough.


> 
> In the case of FMIPv6, pretty much the same thing will happen, except
> if the MN gets an L2 trigger, it will start the process of L3 handover
> when it gets the L2 trigger rather than waiting. If the MN doesn't
> get an L2 trigger, and the nAR does timer-based route advertisement,
> the same kind of disruptions in the real time stream will occur.

Actually I'm comparing FMIPv6 and BETH based on the same set of L2 triggers that 
BETH requires. BETH requires triggers on nAR to indicate arrival of MN. And in 
this case, FMIPv6 doesn't need any L3 signaling. (again, this wasn't clear in 
the FMIPv6 draft...note to the editor)

> 
> These cases assume that the oAR does nothing to inform the MN prior
> to the handover that a handover is coming up. 
> 
> Performance would probably benefit by allowing the oAR to signal the MN
> when it is still on the oAR that a handover to a nonFMIPv6/nonBETH
> capable node is pending. This would allow a MN that is using either
> algorithm to revert to the standard Johnson and Perkins algorithm
> for movement detection, according to its ability to receive

But again this L3 message on old (current) link will defeat the purpose of BETH, 
right? 

> an L2 trigger. If the MN receives an L2 trigger, it can send
> a SolRtAdv as soon as it is on the nAR, if not, it must wait
> until the RtAdv is sent from the nAR. 
> 
> A good place to add support for this would be the PrxyRtAdv. The 
> PrxyRtAdv currently has three codes, we could add one like:
> 
> 	2 - Handover to nonFMIPv6/nonBETH capable AR pending
> 	
> This would be sent when the oAR has knowledge of the capabilities
> of the nAR, to allow MNs to optimize handover as much as possible.
> 
> Of course, if nAR doesn't have such knowledge, it could send
> a 128 (New attachment point unknown), indicating the MN is basically
> on its own.
> 
> 		jak


Jim, my understanding is that the value of BETH comes from lack of L3 signalling 
on the air. You had a table in the version 1 that showed the latencies involved. 
I think the problem of BETH being partially deployed (not all routers are 
expected to deploy any particular method) yet handoffs should be still as fast 
can be fixed by using L3 messages. And I think this defeats the purpose.

What do you think?

alper



From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep 14 17:51:46 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA27018
	for <mobileip-archive@odin.ietf.org>; Fri, 14 Sep 2001 17:51:46 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id PAA02731;
	Fri, 14 Sep 2001 15:51:00 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id OAA16761;
	Fri, 14 Sep 2001 14:50:58 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8ELnU7B003507
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 14 Sep 2001 14:49:30 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8ELnU2V003506
	for mobile-ip-dist; Fri, 14 Sep 2001 14:49:30 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8ELnQ7B003499
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 14 Sep 2001 14:49:26 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id OAA29153
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 14 Sep 2001 14:49:46 -0700 (PDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id PAA01810
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 14 Sep 2001 15:49:41 -0600 (MDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id OAA12786
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 14 Sep 2001 14:49:45 -0700 (PDT)
X-Delivered-For: <mobile-ip@sunroof.eng.sun.com>
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f8ELniN18905
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 14 Sep 2001 14:49:44 -0700
X-mProtect:  Fri, 14 Sep 2001 14:49:44 -0700 Nokia Silicon Valley Messaging Protection
Received: from vijayd.iprg.nokia.com (205.226.2.94, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpdMt5UtI; Fri, 14 Sep 2001 14:49:35 PDT
Message-ID: <3BA27B6F.4DEDF2C9@iprg.nokia.com>
Date: Fri, 14 Sep 2001 14:49:35 -0700
From: Vijay Devarapalli <vijayd@iprg.nokia.com>
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] question on BET tear down
References: <200109062125.OAA28619@heliopolis.eng.sun.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

James Kempf wrote:
> 

> What solution did the original FMIPv6 design team envision for this?
> The original design also had a forward tunnel to the new AR, though not the

a binding cache entry created at the oldAR when a FBU was sent by
the MN to the oldAR. the FBU has a definite lifetime.

> reverse tunnel, possibly for bicasting. I thought that the original
> idea was to send the BU to the old AR  after the MN had completed
> everyting for new CoA establishment.

sending a BU to the oldAR after moving to the newAR is done only
in standard MIPv6. this is not needed in case of Fast MIPv6. this
is because FBU does this. the lifetime value in FBU can be large
enough to take care of all inflight packets between the CN and
the oldAR.

Vijay

> 
> We could write the spec to discourage using a tunnel lifetime of
> 0xffff, which is good till cancelled, unless the ARs have some
> means of definitively telling that the MN has completed L3 handover,
> such as the BU or maybe the HRqst(r)/HRply(r) exchange. That way,
> the tunnel will time out eventually if not renewed.
> 
>                 jak


From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep 14 18:10:44 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27211
	for <mobileip-archive@odin.ietf.org>; Fri, 14 Sep 2001 18:10:39 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id PAA13765;
	Fri, 14 Sep 2001 15:09:30 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id PAA21575;
	Fri, 14 Sep 2001 15:08:53 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8EM7X7B003598
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 14 Sep 2001 15:07:33 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8EM7XTI003597
	for mobile-ip-dist; Fri, 14 Sep 2001 15:07:33 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8EM7T7B003590
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 14 Sep 2001 15:07:29 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id PAA01170
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 14 Sep 2001 15:07:49 -0700 (PDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id PAA06740;
	Fri, 14 Sep 2001 15:07:49 -0700 (PDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id PAA13779;
	Fri, 14 Sep 2001 15:07:49 -0700 (PDT)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f8EM7m210189;
	Fri, 14 Sep 2001 15:07:48 -0700
X-mProtect:  Fri, 14 Sep 2001 15:07:48 -0700 Nokia Silicon Valley Messaging Protection
Received: from rajeev.iprg.nokia.com (205.226.2.90, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpdoVSoTw; Fri, 14 Sep 2001 15:07:35 PDT
Message-ID: <3BA27FA7.DA69BF6E@iprg.nokia.com>
Date: Fri, 14 Sep 2001 15:07:35 -0700
From: Rajeev Koodli <rajeev@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: mobile-ip@sunroof.eng.sun.com
CC: "'James kempf'" <James.Kempf@Sun.COM>
Subject: Re: [mobile-ip] New BETH Draft
References: <697DAA22C5004B4596E033803A7CEF441E8683@daebe007.NOE.Nokia.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hello folks,


"Patil Basavaraj (NET/Dallas)" wrote:

>
> >If the nAR uses an L2 trigger rather
> >than a timer to send the RtAdv, it can catch the MN as soon as L2
> handover is
> >complete. If the MN receives an L2 trigger, of course, it may choose to
> wait
> >until the nAR sends the RtAdv rather than soliciting if it has a real
> time
> >stream, because it doesn't know, a priori, that the nAR doesn't support
> >BETH. The stream may then get disrupted if the MN doesn't receive
> >the RtAdv quickly enough.
>
> According to BETH the MN will not know if a handover is occuring in
> the network at any time. So it would be too much to ask the MN to NOT
> react to an L2 trigger by sending a RtAdv solict right away. The MN
> has no idea if the ARs support BETH at any given time.
>

I agree with Raj that it would be easier for the MN to send a RtSol rather
than for the AR to catch the MN. A MN can detect a new link being made
available and react to it by sending the RtSol. An AR, which could be
connected via an AP, may not be able to get a trigger from the AP without
support from a variety of link types connecting the AP with the AR.  I
think this is an issue to be addressed when relying on link-layer triggers.
When we speak of a trigger between the MN and AR, it is really two
triggers: between MN and AP and AP and AR. Practical deployments, at least
today, realize the AP-AR link by a variety of means. It is non-trivial to
come up with a trigger for each of the possible link types connecting AP
and AR. Or, may be not. I am open to hear arguments. When an AP and AR are
"integrated", perhaps this issue is less relevant.

I also have a question: what would be the response of a MN which is within
a BETH session when it gets a link-layer trigger ? Would it be required not
to send a RtSol ?

Regards,

-Rajeev


>



From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep 14 19:49:54 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA28166
	for <mobileip-archive@odin.ietf.org>; Fri, 14 Sep 2001 19:49:53 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id RAA11362;
	Fri, 14 Sep 2001 17:48:58 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id QAA27232;
	Fri, 14 Sep 2001 16:48:55 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8ENlZ7B003787
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 14 Sep 2001 16:47:35 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8ENlZdq003786
	for mobile-ip-dist; Fri, 14 Sep 2001 16:47:35 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from heliopolis.eng.sun.com (bigbang.Eng.Sun.COM [152.70.8.30])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8ENlV7B003779
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 14 Sep 2001 16:47:31 -0700 (PDT)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.eng.sun.com (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id QAA25353;
	Fri, 14 Sep 2001 16:47:54 -0700 (PDT)
Message-Id: <200109142347.QAA25353@heliopolis.eng.sun.com>
Date: Fri, 14 Sep 2001 16:47:52 -0700 (PDT)
From: James Kempf <James.Kempf@Sun.COM>
Subject: Re: [mobile-ip] New BETH Draft
To: mobile-ip@sunroof.eng.sun.com
Cc: gdommety@cisco.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: KGpMIgLEif1tWKK1cWU6kQ==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Hi Alper,

I've embedded responses below, but before I go to them, let's make
sure we are talking about the same thing. What we are talking about
is the following;

1) The MN is doing BETH supported by the network.

2) It comes to an AR that must hand it over to a new AR without support
for either FMIPv6 or BETH.

3) The current AR does not know that the next AR doesn't support
FMIPv6 nor BETH, so it cannot send a PrxyRtAdv to the MN, which
would trigger the MN to stop doing BETH and solicit a RtAdv on
the new AR.

4) As a consequence, the MN gets onto the new AR and must wait
until a RtAdv shows up from it.

Right? If so, IMHO, as I mentioned in the draft, this is likely to
be a corner case and the result of misconfiguration or lack
of use of CAR discovery, and so not very common. But it should
be covered.

Now, on to your comments.

>> 
>> In the case of BETH, if nAR doesn't support BETH, then it will use
>> the standard Johnson and Perkins algorithm, by which nAR will advertise
>> a RtAdv when the MN is already on the new L2 and the MN will respond 
>> when the RtAdv is received. 
>
>But it's not standard that AR will send an RA as soon as a MN attaches. And 
this 
>can't be accomplished by a requirement by BETH, because at least this AR is not 
>supporting BETH.
>
>I don't think you can rely on nAR sending RA or not sending to figure out BETH 
>support on ARs.
>

MIPv6 isn't RFC yet. If we need to, we can ask Charlie to stick some words in it
about the AR optimizing RtAdv similar to the words about the MN optimizing
movement detection on pg. 80, and we probably should, not just for
FMIPv6.

>Also, for any new message between the MN and the AR, I think you are diverging 
>from your goal of zero latency, which relies on no-L3 traffic.
>

See discussion above. This is a corner case. When it happens, it
means the MN must terminate BET handover and start doing
standard MIPv6 handover (i.e. it cannot even do FMIPv6 handover).

>Note that FMIPv6 can get away without any L3 signalling on the new link. As 
both 
>MN and nAR know each other's L2 identity, L2 attachment signal is enough get 
>traffic going.
>

OK.

>Actually I'm comparing FMIPv6 and BETH based on the same set of L2 triggers 
that 
>BETH requires. BETH requires triggers on nAR to indicate arrival of MN. And in 
>this case, FMIPv6 doesn't need any L3 signaling. (again, this wasn't clear in 
>the FMIPv6 draft...note to the editor)
>

The role of L2 triggers in FMIPv6 does need some clarification.


>But again this L3 message on old (current) link will defeat the purpose of 
BETH, 
>right? 
>

Right, but there's no choice. The next AR can't do BETH anyway.

>
>Jim, my understanding is that the value of BETH comes from lack of L3 
signalling 
>on the air. You had a table in the version 1 that showed the latencies 
involved. 
>I think the problem of BETH being partially deployed (not all routers are 
>expected to deploy any particular method) yet handoffs should be still as fast 
>can be fixed by using L3 messages. And I think this defeats the purpose.
>
>What do you think?
>


As I mentioned above, we are talking about a particular corner case
when the MN runs off of the BETH coverage area. All bets are off
about performance. If the MN can't do BETH and it can't do stock
FMIPv6, it gets the same performance as standard MIPv6 handover.

		jak



From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep 14 20:01:22 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA28266
	for <mobileip-archive@odin.ietf.org>; Fri, 14 Sep 2001 20:01:22 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id SAA16319;
	Fri, 14 Sep 2001 18:00:33 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id RAA00241;
	Fri, 14 Sep 2001 17:00:32 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8ENx37B003864
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 14 Sep 2001 16:59:03 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8ENx3bm003863
	for mobile-ip-dist; Fri, 14 Sep 2001 16:59:03 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from heliopolis.eng.sun.com (redhook.Eng.Sun.COM [152.70.24.37])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8ENwx7B003856
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 14 Sep 2001 16:58:59 -0700 (PDT)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.eng.sun.com (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id QAA25619;
	Fri, 14 Sep 2001 16:59:22 -0700 (PDT)
Message-Id: <200109142359.QAA25619@heliopolis.eng.sun.com>
Date: Fri, 14 Sep 2001 16:59:20 -0700 (PDT)
From: James Kempf <James.Kempf@sun.com>
Subject: Re: [mobile-ip] New BETH Draft
To: mobile-ip@sunroof.eng.sun.com, rajeev@iprg.nokia.com
Cc: James.Kempf@sun.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: S9vmKKB8YE2O8O8NOMrHGw==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Hi Rajeev,

Again, as I mentioned in my email to Alper, the case we are discussing
here is one in which the MN runs off the end of the BETH coverage
area. The MN's current AR either knows that the new AR does not
support FMIPv6 or BETH, or it does not know what the new AR supports.
The latter case, IMHO, is a misconfiguration and should be corrected.


>> According to BETH the MN will not know if a handover is occuring in
>> the network at any time. So it would be too much to ask the MN to NOT
>> react to an L2 trigger by sending a RtAdv solict right away. The MN
>> has no idea if the ARs support BETH at any given time.
>>
>
>I agree with Raj that it would be easier for the MN to send a RtSol rather
>than for the AR to catch the MN.

If the MN is doing BETH and it moves to a router where there is no
BETH, the MN may be delaying L3 handover and so it will wait for
the RtADv. If the old AR can tell it beforehand that it will move
to a new AR without BETH, the MN can begin FMIPv6 handover (if
the new AR supports FMIPv6) or it can know to stop doing BETH
and do RtSol on the new router.

> A MN can detect a new link being made
>available and react to it by sending the RtSol. An AR, which could be
>connected via an AP, may not be able to get a trigger from the AP without
>support from a variety of link types connecting the AP with the AR.  I
>think this is an issue to be addressed when relying on link-layer triggers.
>When we speak of a trigger between the MN and AR, it is really two
>triggers: between MN and AP and AP and AR. 

That is for a particular implementation which happens to be common
right now for a particular radio protocol. It is by no means the
common to all radio protocols, and even in the protocol for
which it is currently common, it is likely to change.

>Practical deployments, at least
>today, realize the AP-AR link by a variety of means. It is non-trivial to
>come up with a trigger for each of the possible link types connecting AP
>and AR. Or, may be not. I am open to hear arguments. When an AP and AR are
>"integrated", perhaps this issue is less relevant.
>

Agree, though I think it might be more straightforward than you think
to come up with triggers. I think they are already there in CDMA,
for example. 

>I also have a question: what would be the response of a MN which is within
>a BETH session when it gets a link-layer trigger ? Would it be required not
>to send a RtSol ?
>

The MN would only be required to send a RtSol if it had been informed
ahead of time on the old AR that it was moving out of a BETH
coverage area. This is why I proposed adding a code to the PrxyRtAdv,
so that the old AR could do this. Otherwise, the optimization
of BETH provided by lack of any L3 MIP signalling would be invalidated.

		jak



From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep 14 20:35:39 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA28587
	for <mobileip-archive@odin.ietf.org>; Fri, 14 Sep 2001 20:35:39 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id SAA29589;
	Fri, 14 Sep 2001 18:34:52 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id RAA25235;
	Fri, 14 Sep 2001 17:34:52 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8F0XT7B003982
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 14 Sep 2001 17:33:29 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8F0XTmt003981
	for mobile-ip-dist; Fri, 14 Sep 2001 17:33:29 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8F0XO7B003974
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 14 Sep 2001 17:33:24 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id RAA04447
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 14 Sep 2001 17:33:46 -0700 (PDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id RAA28176;
	Fri, 14 Sep 2001 17:33:45 -0700 (PDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id RAA24547;
	Fri, 14 Sep 2001 17:33:44 -0700 (PDT)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f8F0Xis29189;
	Fri, 14 Sep 2001 17:33:44 -0700
X-mProtect:  Fri, 14 Sep 2001 17:33:44 -0700 Nokia Silicon Valley Messaging Protection
Received: from rajeev.iprg.nokia.com (205.226.2.90, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpdYK1ijh; Fri, 14 Sep 2001 17:33:42 PDT
Message-ID: <3BA2A1E7.5904F35D@iprg.nokia.com>
Date: Fri, 14 Sep 2001 17:33:43 -0700
From: Rajeev Koodli <rajeev@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: James Kempf <James.Kempf@sun.com>
CC: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] New BETH Draft
References: <200109142359.QAA25619@heliopolis.eng.sun.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hello James,

I am seeking some clarifications below (at the end) regarding when a MN sends
RtSol and what does it do with RtAdv on the new AR. Your responses are
appreciated. I also have some comments below.

Regards,

-Rajeev


James Kempf wrote:

>
> If the MN is doing BETH and it moves to a router where there is no
> BETH, the MN may be delaying L3 handover and so it will wait for
> the RtADv. If the old AR can tell it beforehand that it will move
> to a new AR without BETH, the MN can begin FMIPv6 handover (if
> the new AR supports FMIPv6) or it can know to stop doing BETH
> and do RtSol on the new router.

I guess my point was there is no reason for the MN to wait for RtAdv in any
case. For instance, the Linux IPv6 MN that we have has the hook to send out a
RtSol as soon as an interface becomes enabled (i.e., when the MN undergoes
AP handover). One could call this type of a hook an L2 trigger and that is
implementation-specific.


>
>
> > A MN can detect a new link being made
> >available and react to it by sending the RtSol. An AR, which could be
> >connected via an AP, may not be able to get a trigger from the AP without
> >support from a variety of link types connecting the AP with the AR.  I
> >think this is an issue to be addressed when relying on link-layer triggers.
> >When we speak of a trigger between the MN and AR, it is really two
> >triggers: between MN and AP and AP and AR.
>
> That is for a particular implementation which happens to be common
> right now for a particular radio protocol. It is by no means the
> common to all radio protocols, and even in the protocol for
> which it is currently common, it is likely to change.
>

Well, the other scenario you are referring to is not common either, right ? In
fact, I would argue that having an integrated AR-AP device would be a special
case for which we have limited experience currently. Today, both WLAN and
cellular have this model: there is a separate link between the AP and an AR.
I would guess that such a model would continue to exist.


>
> >Practical deployments, at least
> >today, realize the AP-AR link by a variety of means. It is non-trivial to
> >come up with a trigger for each of the possible link types connecting AP
> >and AR. Or, may be not. I am open to hear arguments. When an AP and AR are
> >"integrated", perhaps this issue is less relevant.
> >
>
> Agree, though I think it might be more straightforward than you think
> to come up with triggers. I think they are already there in CDMA,
> for example.
>

Ok. Would it be possible to clearly specify what a link-layer trigger
constitues (e.g., it could actually span more than one link type) and some
examples ?


>
> >I also have a question: what would be the response of a MN which is within
> >a BETH session when it gets a link-layer trigger ? Would it be required not
> >to send a RtSol ?
> >
>
> The MN would only be required to send a RtSol if it had been informed
> ahead of time on the old AR that it was moving out of a BETH
> coverage area. This is why I proposed adding a code to the PrxyRtAdv,
> so that the old AR could do this. Otherwise, the optimization
> of BETH provided by lack of any L3 MIP signalling would be invalidated.

So, it is requirement for the MN *not* to send a RtSol if it was moving into a
BETH router then ? For this to happen, the MN must be informed a priori by old
AR that the MN is moving into a BETH router as you point out. That means
sending ProxyRtAdv with appripriate code is a necessity for BETH ? If yes, this
is not a corner case anymore.

Also, what happens if the MN receives an unsolicited RtAdv on the new AR when
it is in a BETH session ?

Regards,

-Rajeev


>
>
>                 jak



From owner-mobile-ip@sunroof.eng.sun.com  Sat Sep 15 11:48:57 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21115
	for <mobileip-archive@lists.ietf.org>; Sat, 15 Sep 2001 11:48:57 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA22184;
	Sat, 15 Sep 2001 08:48:31 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id IAA16942;
	Sat, 15 Sep 2001 08:48:17 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8FFkn7B004972
	for <mobile-ip-dist@sunroof.eng.sun.com>; Sat, 15 Sep 2001 08:46:49 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8FFknpt004971
	for mobile-ip-dist; Sat, 15 Sep 2001 08:46:49 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8FFkj7B004964
	for <mobile-ip@sunroof.eng.sun.com>; Sat, 15 Sep 2001 08:46:46 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id IAA21097
	for <mobile-ip@sunroof.eng.sun.com>; Sat, 15 Sep 2001 08:47:07 -0700 (PDT)
Received: from motgate3.mot.com (motgate3.mot.com [144.189.100.103])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id IAA25929
	for <mobile-ip@sunroof.eng.sun.com>; Sat, 15 Sep 2001 08:47:06 -0700 (PDT)
Received: [from pobox4.mot.com (pobox4.mot.com [10.64.251.243]) by motgate3.mot.com (motgate3 2.1) with ESMTP id IAA21803 for <mobile-ip@sunroof.eng.sun.com>; Sat, 15 Sep 2001 08:38:54 -0700 (MST)]
Received: [from il27exb01.cig.mot.com (il27exb01.cig.mot.com [136.182.15.100]) by pobox4.mot.com (MOT-pobox4 2.0) with ESMTP id IAA29585 for <mobile-ip@sunroof.eng.sun.com>; Sat, 15 Sep 2001 08:47:05 -0700 (MST)]
Received: by il27exb01.cig.mot.com with Internet Mail Service (5.5.2654.52)
	id <SCC2SP9M>; Sat, 15 Sep 2001 10:47:05 -0500
Message-ID: <A5B4C9A2AD89D411AB3E009027B0DA1E3B2110@IL27EXM09.cig.mot.com>
From: Singh Ajoy-ASINGH1 <ASINGH1@motorola.com>
To: "'mobile-ip@sunroof.eng.sun.com'" <mobile-ip@sunroof.eng.sun.com>,
        James Kempf <James.Kempf@sun.com>
Subject: RE: [mobile-ip] New BETH Draft
Date: Sat, 15 Sep 2001 10:47:04 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2654.52)
Content-Type: text/plain
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Hello Rajeev/James/Alper:
Sorry for jumping in the middle.
Please find my inline response.
regards,
ajoy 

-----Original Message-----
From: Rajeev Koodli [mailto:rajeev@iprg.nokia.com]
Sent: Friday, September 14, 2001 7:34 PM
To: James Kempf
Cc: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] New BETH Draft


Hello James,

I am seeking some clarifications below (at the end) regarding when a MN sends
RtSol and what does it do with RtAdv on the new AR. Your responses are
appreciated. I also have some comments below.

Regards,

-Rajeev


James Kempf wrote:

>
> If the MN is doing BETH and it moves to a router where there is no
> BETH, the MN may be delaying L3 handover and so it will wait for
> the RtADv. If the old AR can tell it beforehand that it will move
> to a new AR without BETH, the MN can begin FMIPv6 handover (if
> the new AR supports FMIPv6) or it can know to stop doing BETH
> and do RtSol on the new router.

I guess my point was there is no reason for the MN to wait for RtAdv in any
case. For instance, the Linux IPv6 MN that we have has the hook to send out a
RtSol as soon as an interface becomes enabled (i.e., when the MN undergoes
AP handover). One could call this type of a hook an L2 trigger and that is
implementation-specific.

ajoy-> I do not think the example of Linux Mobile/IP is appropriate here.
I do not think if Linux does some way, we should write the spec according to 
that. Here we are talking about enabling Voice over IP for wireless user,
which will require different treatment from the way Mobile/IP was 
implemented for purely non-real time data traffic. 

>
>
> > A MN can detect a new link being made
> >available and react to it by sending the RtSol. An AR, which could be
> >connected via an AP, may not be able to get a trigger from the AP without
> >support from a variety of link types connecting the AP with the AR.  I
> >think this is an issue to be addressed when relying on link-layer triggers.
> >When we speak of a trigger between the MN and AR, it is really two
> >triggers: between MN and AP and AP and AR.
>
> That is for a particular implementation which happens to be common
> right now for a particular radio protocol. It is by no means the
> common to all radio protocols, and even in the protocol for
> which it is currently common, it is likely to change.
>

Well, the other scenario you are referring to is not common either, right ? In
fact, I would argue that having an integrated AR-AP device would be a special
case for which we have limited experience currently. Today, both WLAN and
cellular have this model: there is a separate link between the AP and an AR.
I would guess that such a model would continue to exist.

-> I do not think getting link layer trigger at AR is difficult in case of 
existing cellular network. In fact such work is in progress in 
3GPP2. I am positive this can be done in 3GPP,
provided 3GPP decides to use Mobile/IP. 

>
> >Practical deployments, at least
> >today, realize the AP-AR link by a variety of means. It is non-trivial to
> >come up with a trigger for each of the possible link types connecting AP
> >and AR. Or, may be not. I am open to hear arguments. When an AP and AR are
> >"integrated", perhaps this issue is less relevant.
> >
>
> Agree, though I think it might be more straightforward than you think
> to come up with triggers. I think they are already there in CDMA,
> for example.
>

Ok. Would it be possible to clearly specify what a link-layer trigger
constitues (e.g., it could actually span more than one link type) and some
examples ?


>
> >I also have a question: what would be the response of a MN which is within
> >a BETH session when it gets a link-layer trigger ? Would it be required not
> >to send a RtSol ?
> >
>
> The MN would only be required to send a RtSol if it had been informed
> ahead of time on the old AR that it was moving out of a BETH
> coverage area. This is why I proposed adding a code to the PrxyRtAdv,
> so that the old AR could do this. Otherwise, the optimization
> of BETH provided by lack of any L3 MIP signalling would be invalidated.

So, it is requirement for the MN *not* to send a RtSol if it was moving into a
BETH router then ? For this to happen, the MN must be informed a priori by old
AR that the MN is moving into a BETH router as you point out. That means
sending ProxyRtAdv with appripriate code is a necessity for BETH ? If yes, this
is not a corner case anymore.

-> I think this is a corner case. Could you please provide any realistic example where 
MN can move from BETH capable AR to nonBETH capable AR in same technology ? I am having hard time
to imagine any scenario where we need seamless handover from one AR to other without
any prior agreement between neighboring ARS. Please note that this argument can be
made for any access protocol. For example, please find a few:

What happens when MN moves from AR which supports PPP to the 
AR which does not support PPP ? What happens if PPP unaware MN
tries to connect to non-PPP aware AR ? ....

Regards,

-Rajeev


>
>
>                 jak


From owner-mobile-ip@sunroof.eng.sun.com  Sun Sep 16 18:52:23 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15984
	for <mobileip-archive@lists.ietf.org>; Sun, 16 Sep 2001 18:52:23 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id PAA09103;
	Sun, 16 Sep 2001 15:52:05 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id PAA07565;
	Sun, 16 Sep 2001 15:51:45 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8GMoW7B005830
	for <mobile-ip-dist@sunroof.eng.sun.com>; Sun, 16 Sep 2001 15:50:32 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8GMoWH2005829
	for mobile-ip-dist; Sun, 16 Sep 2001 15:50:32 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8GMoT7B005822
	for <mobile-ip@sunroof.eng.sun.com>; Sun, 16 Sep 2001 15:50:29 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id PAA13898
	for <mobile-ip@sunroof.eng.sun.com>; Sun, 16 Sep 2001 15:50:50 -0700 (PDT)
Received: from fe030.worldonline.dk (fe030.worldonline.dk [212.54.64.197])
	by patan.sun.com (8.9.3+Sun/8.9.3) with SMTP id QAA08306
	for <mobile-ip@sunroof.eng.sun.com>; Sun, 16 Sep 2001 16:50:42 -0600 (MDT)
Received: (qmail 3576 invoked by uid 0); 16 Sep 2001 22:50:47 -0000
Received: from 23.ppp3-5.worldonline.dk (HELO ejlev.dk) (213.237.81.23)
  by fe030.worldonline.dk with SMTP; 16 Sep 2001 22:50:47 -0000
Message-ID: <3BA52C3E.4EB1BDAA@ejlev.dk>
Date: Mon, 17 Sep 2001 00:48:31 +0200
From: Anders Ejlev <anders@ejlev.dk>
X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: mobile-ip <mobile-ip@sunroof.eng.sun.com>
Subject: [mobile-ip] How to get of the mailing list ?? 
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hi
please help me  - how do I get of this mailing list ?

Thanks in advance

Regards
Anders



From owner-mobile-ip@sunroof.eng.sun.com  Mon Sep 17 08:48:48 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA11190
	for <mobileip-archive@odin.ietf.org>; Mon, 17 Sep 2001 08:48:48 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id FAA04167;
	Mon, 17 Sep 2001 05:47:43 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id FAA10756;
	Mon, 17 Sep 2001 05:47:32 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8HCkH7B006560
	for <mobile-ip-dist@sunroof.eng.sun.com>; Mon, 17 Sep 2001 05:46:17 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8HCkHfR006559
	for mobile-ip-dist; Mon, 17 Sep 2001 05:46:17 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8HCkD7B006552
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 17 Sep 2001 05:46:13 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id FAA10930
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 17 Sep 2001 05:46:32 -0700 (PDT)
Received: from mail.zrz.tu-berlin.de (mail.zrz.TU-Berlin.DE [130.149.4.15])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id FAA28924
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 17 Sep 2001 05:46:31 -0700 (PDT)
Received: from ftsu07.ee.tu-berlin.de ([130.149.49.87] helo=ftmail.ee.tu-berlin.de)
	  by mail.zrz.tu-berlin.de with smtp (exim-3.33)
	  for <mobile-ip@sunroof.eng.sun.com>
	  id 15ixnB-0003MR-00; Mon, 17 Sep 2001 14:46:29 +0200
Received: from ee.tu-berlin.de (sinope.ee.TU-Berlin.DE [130.149.49.127])
	by ftmail.ee.tu-berlin.de (8.11.3/8.11.3) with ESMTP id f8HCkTH13742
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 17 Sep 2001 14:46:29 +0200
Message-ID: <3BA5F0A5.689AD3DD@ee.tu-berlin.de>
Date: Mon, 17 Sep 2001 14:46:29 +0200
From: Xiaoming Fu <fu@ee.tu-berlin.de>
Organization: Telecommunication Networks Group, TU-Berlin
X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.14 i686)
X-Accept-Language: en-US, de, zh-CN
MIME-Version: 1.0
To: "mobile-ip@sunroof.eng.sun.com" <mobile-ip@sunroof.eng.sun.com>
Subject: [mobile-ip] comments on HMIPv6 draft
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hi,

I just wonder some bits in HMIPv6 draft (04):

  - Why needs two bits ("R" and "M") instead of one to classify 
    Basic Mode and Extended Mode? (Consequently the "P" and "T")
    Is there any other mode beyond Basic Mode and Extended Mode?
  - "I" bit still depends on some other configuration, right? 
    If so is it necessary to keep this bit?

Also I would favor if a section on possible "conceptual data 
structures" added/updated over MIPv6 could be provided.

Thanks in advance.

Xiaoming


From owner-mobile-ip@sunroof.eng.sun.com  Mon Sep 17 10:58:53 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13518
	for <mobileip-archive@odin.ietf.org>; Mon, 17 Sep 2001 10:58:52 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id HAA29240;
	Mon, 17 Sep 2001 07:55:21 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id HAA04741;
	Mon, 17 Sep 2001 07:54:28 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8HErJ7B006726
	for <mobile-ip-dist@sunroof.eng.sun.com>; Mon, 17 Sep 2001 07:53:19 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8HErI8i006724
	for mobile-ip-dist; Mon, 17 Sep 2001 07:53:18 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8HErD7B006710
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 17 Sep 2001 07:53:14 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id HAA10128
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 17 Sep 2001 07:53:30 -0700 (PDT)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id HAA01378
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 17 Sep 2001 07:53:29 -0700 (PDT)
Received: from esealnt409.al.sw.ericsson.se (ESEALNT409.al.sw.ericsson.se [153.88.251.32])
	by penguin.wise.edt.ericsson.se (8.11.0/8.10.1/WIREfire-1.3) with SMTP id f8HErSv16608
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 17 Sep 2001 16:53:28 +0200 (MEST)
Received: FROM esealnt400.al.sw.ericsson.se BY esealnt409.al.sw.ericsson.se ; Mon Sep 17 16:53:27 2001 +0200
Received: by esealnt400 with Internet Mail Service (5.5.2653.19)
	id <NBWWQJZG>; Mon, 17 Sep 2001 16:53:19 +0200
Message-ID: <034BEFD03799D411A59F00508BDF754603008CCB@esealnt448.al.sw.ericsson.se>
From: "Hesham Soliman  (ERA)" <Hesham.Soliman@era.ericsson.se>
To: "'mobile-ip@sunroof.eng.sun.com'" <mobile-ip@sunroof.eng.sun.com>
Subject: RE: [mobile-ip] comments on HMIPv6 draft
Date: Mon, 17 Sep 2001 16:53:11 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
	Hi Xiaoming, 

> I just wonder some bits in HMIPv6 draft (04):
> 
>   - Why needs two bits ("R" and "M") instead of one to classify 
>     Basic Mode and Extended Mode?
> 
	=> No good answer really ! It seemed safer at the time to explicitly
	leave on flag per mode. 

>  (Consequently the "P" and "T")
>     Is there any other mode beyond Basic Mode and Extended Mode?
> 
	=> You need 2 here because one says that the network is mandatnig 
	that the user uses RCoA as a source address. So if another 
	one is used the routers ingress filtering will drop the packets. 
	Anothe flag is needed to allow the user to use RCoA if they wish (MAY).


> Also I would favor if a section on possible "conceptual data 
> structures" added/updated over MIPv6 could be provided.
> 
	=> OK, will add that to the TODO list. 

	Thanks, 
	Hesham




From owner-mobile-ip@sunroof.eng.sun.com  Mon Sep 17 16:42:57 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21390
	for <mobileip-archive@odin.ietf.org>; Mon, 17 Sep 2001 16:42:56 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA08016;
	Mon, 17 Sep 2001 13:40:15 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id NAA08507;
	Mon, 17 Sep 2001 13:37:31 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8HKZk7B007606
	for <mobile-ip-dist@sunroof.eng.sun.com>; Mon, 17 Sep 2001 13:35:46 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8HKZkmL007605
	for mobile-ip-dist; Mon, 17 Sep 2001 13:35:46 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from heliopolis.eng.sun.com (redhook.Eng.Sun.COM [152.70.24.37])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8HKZg7B007598
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 17 Sep 2001 13:35:42 -0700 (PDT)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.eng.sun.com (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id NAA14001;
	Mon, 17 Sep 2001 13:36:00 -0700 (PDT)
Message-Id: <200109172036.NAA14001@heliopolis.eng.sun.com>
Date: Mon, 17 Sep 2001 13:36:00 -0700 (PDT)
From: James Kempf <James.Kempf@sun.com>
Subject: Re: [mobile-ip] New BETH Draft
To: James.Kempf@sun.com, rajeev@iprg.nokia.com
Cc: mobile-ip@sunroof.eng.sun.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: nHZdcMIpcqQLH/wo1cE07g==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Hi Rajeev,

>
>I am seeking some clarifications below (at the end) regarding when a MN sends
>RtSol and what does it do with RtAdv on the new AR. Your responses are
>appreciated. I also have some comments below.
>

OK, I'll see what I can do.


>> If the MN is doing BETH and it moves to a router where there is no
>> BETH, the MN may be delaying L3 handover and so it will wait for
>> the RtADv. If the old AR can tell it beforehand that it will move
>> to a new AR without BETH, the MN can begin FMIPv6 handover (if
>> the new AR supports FMIPv6) or it can know to stop doing BETH
>> and do RtSol on the new router.
>
>I guess my point was there is no reason for the MN to wait for RtAdv in any
>case. For instance, the Linux IPv6 MN that we have has the hook to send out a
>RtSol as soon as an interface becomes enabled (i.e., when the MN undergoes
>AP handover). One could call this type of a hook an L2 trigger and that is
>implementation-specific.
>

Right, and normally that would be the case. But the scenario is that
the MN is doing BETH, and in BETH the RtSol is suppressed since
the network is handling the handover. If network handover fails,
due to the MN running off the end of a BETH coverage area, then
unless there is a signal that the MN is running off the end, it
will just wait until the RtAdv occurs, because it doesn't know
to solicit.


>
>Well, the other scenario you are referring to is not common either, right ? In
>fact, I would argue that having an integrated AR-AP device would be a special
>case for which we have limited experience currently. Today, both WLAN and
>cellular have this model: there is a separate link between the AP and an AR.
>I would guess that such a model would continue to exist.
>
>

But from the cellular viewpoint, the MN doesn't see the AP. It's the
stratified stack: the RAN protocol (even if it's all IP!) is hidden from
the MN's stack. So most cellular systems will appear as if the AP
and AR are integrated.

I think the only real AP/AR deployments that matter are WLAN: 802.11
primarily. Not sure about HiperLan or Bluetooth. 


>>
>
>Ok. Would it be possible to clearly specify what a link-layer trigger
>constitues (e.g., it could actually span more than one link type) and some
>examples ?
>

There are some hypothetical examples in draft-manyfolks-l2-mobilereq-00.txt.
Perhaps we need to get a few from the CDMA world as more concrete examples?


>So, it is requirement for the MN *not* to send a RtSol if it was moving into a
>BETH router then ? For this to happen, the MN must be informed a priori by old
>AR that the MN is moving into a BETH router as you point out.  

Yes, that's correct. The whole *point* of BETH is to eliminate the
radio MIP signalling for L3 handover until either: a) the MN is prepared
to pay the cost (i.e. it slows down, there is no real time traffic, etc.),
or: b) The network can no longer support the tunnel. The latter
includes the case of the MN running off the edge of the BETH coverage
area.

>That means
>sending ProxyRtAdv with appripriate code is a necessity for BETH ?

It is a further optimization that I think would be helpful. If the
PrxyRtAdv with code is not sent, then the MN will simply wait
on the new AR until an unsolicited RtAdv shows up and then do
L3 handover (see below). The PrxyRtAdv optimizes this by allowing
the MN to proactively perform L3 handover rather than waiting.


>If yes, this
>is not a corner case anymore.
>

What I meant was that the MN running off the edge of the coverage
area and standard FMIPv6 is not implemented at the new AR.  I think
that most ARs will at least support FMIPv6. If the new AR does,
the old AR can simply send the PrxyRtAdv to the MN, and the MN will perform
a standard FMIPv6 handover (even if it was doing BETH in the
BETH coverage area).

>Also, what happens if the MN receives an unsolicited RtAdv on the new AR when
>it is in a BETH session ?
>

Then it *must* begin the process of L3 handover, to establish a new 
CoA at the new AR. An unsolicited RtAdv is an indication from the
AR that it is no longer prepared to maintain the bidirectional edge
tunnel, and so the MN must establish a new CoA.

Does that make sense?

		jak




From owner-mobile-ip@sunroof.eng.sun.com  Mon Sep 17 17:10:52 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21925
	for <mobileip-archive@odin.ietf.org>; Mon, 17 Sep 2001 17:10:51 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id PAA23857;
	Mon, 17 Sep 2001 15:09:51 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id OAA18199;
	Mon, 17 Sep 2001 14:09:49 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8HL8K7B007889
	for <mobile-ip-dist@sunroof.eng.sun.com>; Mon, 17 Sep 2001 14:08:20 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8HL8KeK007888
	for mobile-ip-dist; Mon, 17 Sep 2001 14:08:20 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from jurassic.eng.sun.com (jurassic [129.146.83.36] (may be forged))
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8HL8G7B007881
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 17 Sep 2001 14:08:17 -0700 (PDT)
Received: from istanbul.Eng.Sun.COM (istanbul.Eng.Sun.COM [129.146.86.247])
	by jurassic.eng.sun.com (8.12.0+Sun/8.12.0) with SMTP id f8HL8aVj996322
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 17 Sep 2001 14:08:36 -0700 (PDT)
Message-Id: <200109172108.f8HL8aVj996322@jurassic.eng.sun.com>
Date: Mon, 17 Sep 2001 14:08:27 -0700 (PDT)
From: Alper Yegin <Alper.Yegin@eng.sun.com>
Subject: RE: [mobile-ip] New BETH Draft
To: mobile-ip@sunroof.eng.sun.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: eGJF6PLDeHzr39csVBeE3w==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4_37 SunOS 5.8.1 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Ajoy,

Just a quick response to your point below...


> So, it is requirement for the MN *not* to send a RtSol if it was moving into a
> BETH router then ? For this to happen, the MN must be informed a priori by old
> AR that the MN is moving into a BETH router as you point out. That means
> sending ProxyRtAdv with appripriate code is a necessity for BETH ? If yes, 
this
> is not a corner case anymore.
> 
AJOY -> I think this is a corner case. Could you please provide any realistic 
example where 
> MN can move from BETH capable AR to nonBETH capable AR in same technology ?

Two same-technology wireless networks, which are physically adjacent to each 
other, doesn't have to necessarily deploy same mobility protocols. (speaking of 
IPv6) minimum requirement is to deploy an IPv6 access routers, and everything 
should work. Additionally, any combination of FMIPv6/BETH protocols can be 
deployed on each. 


> I am having hard time
> to imagine any scenario where we need seamless handover from one AR to other 
without
> any prior agreement between neighboring ARS. 

Yes, for *ultimate* performance, deploying the same mobility technology on both 
sides (oAR and nAR) is a must. BUT, if any of the protocols, such as BETH as 
defined in draft v02, makes the performance of handoff to non-BETH networks 
slower than before, then this is a problem we should solve. The ideal is not to 
degrade such performance.

> Please note that this argument can be
> made for any access protocol. For example, please find a few:

A MN which supports base-MIPv6/FMIPv6/BETH should be able to hop around ARs that 
support any of these protocols. And ideally the performance shouldn't be no 
worse than pure base-MIPv6 protocol's.


> 
> What happens when MN moves from AR which supports PPP to the 
> AR which does not support PPP ? What happens if PPP unaware MN
> tries to connect to non-PPP aware AR ? ....


alper



From owner-mobile-ip@sunroof.eng.sun.com  Mon Sep 17 17:28:24 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22088
	for <mobileip-archive@odin.ietf.org>; Mon, 17 Sep 2001 17:28:19 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id OAA02073;
	Mon, 17 Sep 2001 14:27:13 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id OAA18763;
	Mon, 17 Sep 2001 14:25:39 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8HLOQ7B007960
	for <mobile-ip-dist@sunroof.eng.sun.com>; Mon, 17 Sep 2001 14:24:26 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8HLOQ6n007959
	for mobile-ip-dist; Mon, 17 Sep 2001 14:24:26 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from jurassic.eng.sun.com (jurassic [129.146.83.130] (may be forged))
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8HLOM7B007952
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 17 Sep 2001 14:24:22 -0700 (PDT)
Received: from istanbul.Eng.Sun.COM (istanbul.Eng.Sun.COM [129.146.86.247])
	by jurassic.eng.sun.com (8.12.0+Sun/8.12.0) with SMTP id f8HLOdVj999311;
	Mon, 17 Sep 2001 14:24:40 -0700 (PDT)
Message-Id: <200109172124.f8HLOdVj999311@jurassic.eng.sun.com>
Date: Mon, 17 Sep 2001 14:24:30 -0700 (PDT)
From: Alper Yegin <Alper.Yegin@eng.sun.com>
Subject: Re: [mobile-ip] New BETH Draft
To: mobile-ip@sunroof.eng.sun.com
Cc: gdommety@cisco.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: zNPATqOxiw8jc53QXaga7g==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4_37 SunOS 5.8.1 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Hi James,

> 1) The MN is doing BETH supported by the network.
> 
> 2) It comes to an AR that must hand it over to a new AR without support
> for either FMIPv6 or BETH.
> 
> 3) The current AR does not know that the next AR doesn't support
> FMIPv6 nor BETH, so it cannot send a PrxyRtAdv to the MN, which
> would trigger the MN to stop doing BETH and solicit a RtAdv on
> the new AR.
> 
> 4) As a consequence, the MN gets onto the new AR and must wait
> until a RtAdv shows up from it.
> 
> Right? If so, IMHO, as I mentioned in the draft, this is likely to
> be a corner case and the result of misconfiguration or lack
> of use of CAR discovery, and so not very common. But it should
> be covered.

Reading this, I understand you are proposing adding a PrRtAdv to the protocol. 
This should be sent prior to MN detaching from old link. And it can indicate 
whether the Mn is going to handoff to a BETH supporting AR or not. Right? If so, 
this should help.

But this is not in the draft yet, right? Also, would you send this message all 
the time, regadless of whether nAR is BETH capable or not. I'd recommend so.

So, now answering your above question: yes, I agree this is a misconfig given 
that now we have such a message to inform MN.


> 
> Now, on to your comments.
> 
> >> 
> >> In the case of BETH, if nAR doesn't support BETH, then it will use
> >> the standard Johnson and Perkins algorithm, by which nAR will advertise
> >> a RtAdv when the MN is already on the new L2 and the MN will respond 
> >> when the RtAdv is received. 
> >
> >But it's not standard that AR will send an RA as soon as a MN attaches. And 
> this 
> >can't be accomplished by a requirement by BETH, because at least this AR is 
not 
> >supporting BETH.
> >
> >I don't think you can rely on nAR sending RA or not sending to figure out 
BETH 
> >support on ARs.
> >
> 
> MIPv6 isn't RFC yet. If we need to, we can ask Charlie to stick some words in 
it
> about the AR optimizing RtAdv similar to the words about the MN optimizing
> movement detection on pg. 80, and we probably should, not just for
> FMIPv6.

Yes, we can think about that too. But unless I misunderstood, we are already 
accomplishing this by sending a PrRtAdv. MN already knows by the time it 
attaches to new link.

> 
> >Also, for any new message between the MN and the AR, I think you are 
diverging 
> >from your goal of zero latency, which relies on no-L3 traffic.
> >
> 
> See discussion above. This is a corner case. When it happens, it
> means the MN must terminate BET handover and start doing
> standard MIPv6 handover (i.e. it cannot even do FMIPv6 handover).


If you add PrRtAdv, then you are adding latency.

> 
> >Note that FMIPv6 can get away without any L3 signalling on the new link. As 
> both 
> >MN and nAR know each other's L2 identity, L2 attachment signal is enough get 
> >traffic going.
> >
> 
> OK.
> 
> >Actually I'm comparing FMIPv6 and BETH based on the same set of L2 triggers 
> that 
> >BETH requires. BETH requires triggers on nAR to indicate arrival of MN. And 
in 
> >this case, FMIPv6 doesn't need any L3 signaling. (again, this wasn't clear in 
> >the FMIPv6 draft...note to the editor)
> >
> 
> The role of L2 triggers in FMIPv6 does need some clarification.
> 
> 
> >But again this L3 message on old (current) link will defeat the purpose of 
> BETH, 
> >right? 
> >
> 
> Right, but there's no choice. The next AR can't do BETH anyway.

Same question as above: are we going to always send a PrRtAdv to MN, or not?

> 
> >
> >Jim, my understanding is that the value of BETH comes from lack of L3 
> signalling 
> >on the air. You had a table in the version 1 that showed the latencies 
> involved. 
> >I think the problem of BETH being partially deployed (not all routers are 
> >expected to deploy any particular method) yet handoffs should be still as 
fast 
> >can be fixed by using L3 messages. And I think this defeats the purpose.
> >
> >What do you think?
> >
> 
> 
> As I mentioned above, we are talking about a particular corner case
> when the MN runs off of the BETH coverage area. All bets are off
> about performance. If the MN can't do BETH and it can't do stock
> FMIPv6, it gets the same performance as standard MIPv6 handover.

If MN thinks BETH is going on and if this is not the case, since MN would hold 
on to sending RS (BETH says so, right?), the performance would be worse than 
base-MIPv6. Because, if MN had known, then it could send an RS and expedite the 
process.

A solution, if I understand right, is to send a PrRtAdv from oAR to MN. But now 
this introduces L3 latency. Then I think we should take a look at the 
performance gains over FMIPv6 again.

I think we should also look at other cases: BETH-enabled MN doing handoff from 
one non-BETH-AR to another non-BETH-AR. BETH-enabled MN entering back into a 
BETH domain..

And on another case is: what if MN is not BETH-enabled? How does BETH-enabled 
ARs treat them..

I think these are missing in the draft.

> 
> 		jak

alper



From owner-mobile-ip@sunroof.eng.sun.com  Mon Sep 17 18:24:44 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA22969
	for <mobileip-archive@odin.ietf.org>; Mon, 17 Sep 2001 18:24:39 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id PAA29340;
	Mon, 17 Sep 2001 15:23:47 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id PAA03889;
	Mon, 17 Sep 2001 15:22:12 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8HMKr7B008308
	for <mobile-ip-dist@sunroof.eng.sun.com>; Mon, 17 Sep 2001 15:20:53 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8HMKrtl008307
	for mobile-ip-dist; Mon, 17 Sep 2001 15:20:53 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from heliopolis.eng.sun.com (redhook.Eng.Sun.COM [152.70.24.37])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8HMKn7B008300
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 17 Sep 2001 15:20:49 -0700 (PDT)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.eng.sun.com (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id PAA18103;
	Mon, 17 Sep 2001 15:21:07 -0700 (PDT)
Message-Id: <200109172221.PAA18103@heliopolis.eng.sun.com>
Date: Mon, 17 Sep 2001 15:21:06 -0700 (PDT)
From: James Kempf <James.Kempf@Sun.COM>
Subject: Re: [mobile-ip] New BETH Draft
To: mobile-ip@sunroof.eng.sun.com
Cc: gdommety@cisco.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: Amqh60GpxEMYqd04qFtPpw==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Hi Alper,

>
>> 1) The MN is doing BETH supported by the network.
>> 
>> 2) It comes to an AR that must hand it over to a new AR without support
>> for either FMIPv6 or BETH.
>> 
>> 3) The current AR does not know that the next AR doesn't support
>> FMIPv6 nor BETH, so it cannot send a PrxyRtAdv to the MN, which
>> would trigger the MN to stop doing BETH and solicit a RtAdv on
>> the new AR.
>> 
>> 4) As a consequence, the MN gets onto the new AR and must wait
>> until a RtAdv shows up from it.
>> 
>> Right? If so, IMHO, as I mentioned in the draft, this is likely to
>> be a corner case and the result of misconfiguration or lack
>> of use of CAR discovery, and so not very common. But it should
>> be covered.
>
>Reading this, I understand you are proposing adding a PrRtAdv to the protocol. 
>This should be sent prior to MN detaching from old link. And it can indicate 
>whether the Mn is going to handoff to a BETH supporting AR or not. Right? If 
so, 
>this should help.
>

What I am proposing is that if the old AR knows that the new AR does
not support FMIPv6, it sends a PrxyRtAdv with a new code indicating
that. This benefits *both* a BETH capable MN and one that is doing
standard FMIPv6. If the new AR does support FMIPv6, of course, it sends a 
PrxyRtAdv with one of the existing codes. If the new AR doesn't
know what the new AR supports, it sends a PrxyRtAdv with code 255.
And finally, if the new AR doesn't even know that a handover is
coming nor where, we are out of luck and the MN must wait til
it gets to the new AR to discover that fact, regardless of whether
FMIPv6 or BETH is used.


>But this is not in the draft yet, right? Also, would you send this message all 
>the time, regadless of whether nAR is BETH capable or not. I'd recommend so.
>

No it is not in the draft, but I will fold it in when I incorporate the BETH 
draft into the FMIPv6 draft. The message only gets sent if the new AR
is not BETH capable, otherwise, it compromises the optimization of
radio link traffic.

>So, now answering your above question: yes, I agree this is a misconfig given 
>that now we have such a message to inform MN.
>

OK.

>> >I don't think you can rely on nAR sending RA or not sending to figure out 
>BETH 
>> >support on ARs.
>> >
>> 
>> MIPv6 isn't RFC yet. If we need to, we can ask Charlie to stick some words in 
>it
>> about the AR optimizing RtAdv similar to the words about the MN optimizing
>> movement detection on pg. 80, and we probably should, not just for
>> FMIPv6.
>
>Yes, we can think about that too. But unless I misunderstood, we are already 
>accomplishing this by sending a PrRtAdv. MN already knows by the time it 
>attaches to new link.
>

But consider exactly the same case where the MN is doing FMIPv6 instead of BETH,
new AR is not capable of doing FMIPv6, and the MN gets no trigger
information indicating when handover has occured but the AR does.
Even if the MN gets the PrxyRtAdv, it may come with code 255 or the
new code, indicating the new AR is unknown or that it does standard MIPv6 
handover.  The MN must then wait until it receives the unsolicited RtAdv before 
it can begin L3 handover. If the new AR sends the unsolicited RtAdv immediately 
upon L2 handover, the MN will start L3 handover more quickly. 

>> 
>> >Also, for any new message between the MN and the AR, I think you are 
>diverging 
>> >from your goal of zero latency, which relies on no-L3 traffic.
>> >
>> 
>> See discussion above. This is a corner case. When it happens, it
>> means the MN must terminate BET handover and start doing
>> standard MIPv6 handover (i.e. it cannot even do FMIPv6 handover).
>
>
>If you add PrRtAdv, then you are adding latency.
>

Right, but this is *only* when you run off the edge of a BETH coverage
area. At that point, you have very little choice, and taking the
hit of a known amount of radio traffic delay in place of an unknown amount
if the MN gets to the new AR and must wait for the RtAdv is probably
a good bet.


>> Right, but there's no choice. The next AR can't do BETH anyway.
>
>Same question as above: are we going to always send a PrRtAdv to MN, or not?
>

The answer is no. Only when the MN runs off the edge of the BETH
coverage area.


>If MN thinks BETH is going on and if this is not the case, since MN would hold 
>on to sending RS (BETH says so, right?), the performance would be worse than 
>base-MIPv6. Because, if MN had known, then it could send an RS and expedite the 
>process.
>
>A solution, if I understand right, is to send a PrRtAdv from oAR to MN. But now 
>this introduces L3 latency. Then I think we should take a look at the 
>performance gains over FMIPv6 again.
>

I agree. If the old AR knows the new one doesn't support BETH or FMIPv6,
it should tell the MN via the PrxyRtAdv. If the new AR supports BETH,
the old AR should send nothing.

>I think we should also look at other cases: BETH-enabled MN doing handoff from 
>one non-BETH-AR to another non-BETH-AR. 

If the MN gets a PrxyRtAdv, then it knows not to use BETH. 

>BETH-enabled MN entering back into a 
>BETH domain..
>

If the MN does not receive a PrxyRtAdv from the network and it
detects an L2 trigger for handover, then it knows the network
is handling the handover. Provided, of course, the MN knows
that the network supports FMIPv6/BETH.

But you bring up another, wider issue: how does an MN know that the
AR is capable of doing FMIPv6 or BETH in the first place? For example,
suppose the MN wants to do mobile initiated FMIPv6 handover. Does it
just send off the SolPrxyRtAdv without any indication whatsoever that
the AR can perform FMIPv6, or does the MN receive some indication
beforehand that the AR is FMIPv6 capable? Similarly for BETH.

>And on another case is: what if MN is not BETH-enabled? How does BETH-enabled 
>ARs treat them..
>

Like FMIPv6. FMIPv6 is the fallback case, if that isn't available, then
standard MIPv6.

>I think these are missing in the draft.
>

I need to look through it. Perhaps I need to add a section or paragraph
about fall back positions, and something is probably needed in the
FMIPv6 base draft as well.

		jak



From owner-mobile-ip@sunroof.eng.sun.com  Mon Sep 17 19:17:19 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA24554
	for <mobileip-archive@odin.ietf.org>; Mon, 17 Sep 2001 19:17:18 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id QAA21589;
	Mon, 17 Sep 2001 16:16:22 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id QAA23701;
	Mon, 17 Sep 2001 16:16:12 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8HNEV7B008784
	for <mobile-ip-dist@sunroof.eng.sun.com>; Mon, 17 Sep 2001 16:14:31 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8HNEVlf008783
	for mobile-ip-dist; Mon, 17 Sep 2001 16:14:31 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8HNEO7B008766
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 17 Sep 2001 16:14:24 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id QAA23327
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 17 Sep 2001 16:14:43 -0700 (PDT)
From: Internet-Drafts@ietf.org
Received: from guinness (mx.last.plus.net [212.159.3.230])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id RAA24310
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 17 Sep 2001 17:14:34 -0600 (MDT)
Received: from [212.159.14.227] (helo=warrior-outbound.services.quay.plus.net)
	by guinness with smtp (Exim 3.16 #2)
	id 15j7OZ-0002KS-00
	for mobile-ip@sunroof.eng.sun.com; Tue, 18 Sep 2001 00:01:43 +0100
Received: (qmail 29298 invoked from network); 17 Sep 2001 23:13:58 -0000
Received: from unknown (HELO NEXUS.replicants.org.uk) (212.56.122.201)
  by warrior with SMTP; 17 Sep 2001 23:13:58 -0000
Received: from mail pickup service by NEXUS.replicants.org.uk with Microsoft SMTPSVC;
	 Tue, 18 Sep 2001 00:13:49 +0100
X-From_: ietf-123-owner@loki.ietf.org Tue Jun 26 16:02:05 2001
Received: from [132.151.1.177] (helo=loki.ietf.org)	by imailg2.svr.pol.co.uk with esmtp (Exim 3.13 #0)	id 15EuLt-00079u-00; Tue, 26 Jun 2001 16:02:05 +0100
Received: (from adm@localhost)	by loki.ietf.org (8.9.1b+Sun/8.9.1) id JAA19873	for ietf-123-outbound.10@ietf.org; Tue, 26 Jun 2001 09:55:02 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28])	by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id HAA18631	for <all-ietf@loki.ietf.org>; Tue, 26 Jun 2001 07:02:57 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA27339;	Tue, 26 Jun 2001 07:02:56 -0400 (EDT)
Message-Id: <200106261102.HAA27339@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
CC: mobile-ip@sunroof.eng.sun.com
Subject: [mobile-ip] I-D ACTION:draft-subbarao-mobileip-redundancy-00.txt
Date: Tue, 26 Jun 2001 07:02:55 -0400
X-OriginalArrivalTime: 17 Sep 2001 23:13:49.0579 (UTC) FILETIME=[68B80DB0:01C13FCE]
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.


	Title		: Home Agent Redundancy in Mobile IP
	Author(s)	: K. Leung, M. Subbarao
	Filename	: draft-subbarao-mobileip-redundancy-00.txt
	Pages		: 
	Date		: 11-Jun-01
	
In Mobile IP, a Home Agent (HA) creates a mobility binding table
that tracks the association of a Mobile Node's (MN) home address with
its current Care-of Address (CoA).  If the HA fails, the mobility
binding table will be lost and all MNs registered with the HA will
lose connectivity.  In this draft, we propose a Mobile IP Home Agent
Redundancy framework mechanism that provides the essential robust
redundancy needed at the HA.  The mechanism described herein can also
be used to provide the redundancy needed at any 'regional/local' HAs.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-subbarao-mobileip-redundancy-00.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-subbarao-mobileip-redundancy-00.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-subbarao-mobileip-redundancy-00.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:	<20010625110710.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-subbarao-mobileip-redundancy-00.txt

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

--OtherAccess--
--NextPart--


From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep 18 02:24:38 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA12907
	for <mobileip-archive@odin.ietf.org>; Tue, 18 Sep 2001 02:24:37 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id XAA24656;
	Mon, 17 Sep 2001 23:23:41 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id XAA16333;
	Mon, 17 Sep 2001 23:23:32 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8I6MM7B009599
	for <mobile-ip-dist@sunroof.eng.sun.com>; Mon, 17 Sep 2001 23:22:22 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8I6MMJx009598
	for mobile-ip-dist; Mon, 17 Sep 2001 23:22:22 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8I6MI7B009591
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 17 Sep 2001 23:22:18 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id XAA13216
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 17 Sep 2001 23:22:37 -0700 (PDT)
Received: from wombat.cs.rmit.edu.au (wombat.cs.rmit.edu.au [131.170.24.41])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id XAA01774
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 17 Sep 2001 23:22:35 -0700 (PDT)
Received: from yallara.cs.rmit.edu.au (ryanlea@yallara.cs.rmit.edu.au [131.170.24.42])
	by wombat.cs.rmit.edu.au (8.9.3/8.9.3/cshub) with ESMTP id QAA15901
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 18 Sep 2001 16:22:34 +1000 (EST)
Received: (from ryanlea@localhost)
	by yallara.cs.rmit.edu.au (8.9.3/8.9.3/csnode) id QAA20274
	for mobile-ip@sunroof.eng.sun.com; Tue, 18 Sep 2001 16:22:33 +1000 (EST)
Message-Id: <200109180622.QAA20274@yallara.cs.rmit.edu.au>
Subject: [mobile-ip] Hitachi's implementation
To: mobile-ip@sunroof.eng.sun.com
Date: Tue, 18 Sep 2001 16:22:33 +1000 (EST)
From: "Ryan Anthony Lea" <ryanlea@cs.rmit.edu.au>
X-Mailer: ELM [version 2.5 PL3]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hi,

just wondering if anyone knows where the Hitachi implementation of mipv6
for the Kame stack can be found?

Thank s in advance

Ryan


From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep 18 02:34:35 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA13633
	for <mobileip-archive@odin.ietf.org>; Tue, 18 Sep 2001 02:34:34 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id XAA26633;
	Mon, 17 Sep 2001 23:33:45 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id XAA25118;
	Mon, 17 Sep 2001 23:33:37 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8I6WL7B009677
	for <mobile-ip-dist@sunroof.eng.sun.com>; Mon, 17 Sep 2001 23:32:21 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8I6WLpN009676
	for mobile-ip-dist; Mon, 17 Sep 2001 23:32:21 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8I6WH7B009669
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 17 Sep 2001 23:32:17 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id XAA14253
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 17 Sep 2001 23:32:36 -0700 (PDT)
Received: from cwcsun41.cwc.nus.edu.sg (cwcsun41.cwc.nus.edu.sg [137.132.163.102])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id XAA13038
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 17 Sep 2001 23:32:30 -0700 (PDT)
Received: from sooguan ([172.16.3.160])
	by cwcsun41.cwc.nus.edu.sg (8.9.3/8.9.3) with SMTP id OAA27348
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 18 Sep 2001 14:31:14 +0800 (SGT)
Message-ID: <011501c1400c$48367c00$a00310ac@cwc.nus.edu.sg>
From: "Eng Soo Guan" <engsg@cwc.nus.edu.sg>
To: <mobile-ip@sunroof.eng.sun.com>
References: <200109180622.QAA20274@yallara.cs.rmit.edu.au>
Subject: Re: [mobile-ip] Hitachi's implementation
Date: Tue, 18 Sep 2001 14:36:42 +0800
Organization: CWC
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Dear Ryan,

This is the first time I heard of a MIPv6 implementation from Hitachi. May I
know where did you get the information?

Warmest regards.

ESG
Eng Soo Guan
R&D Engineer (Software Lab)
Centre for Wireless Communications, NUS
http://www.cwc.nus.edu.sg
Tel (65) 8709330
****************************************************
----- Original Message -----
From: Ryan Anthony Lea
To: mobile-ip@sunroof.eng.sun.com
Sent: Tuesday, September 18, 2001 2:22 PM
Subject: [mobile-ip] Hitachi's implementation


Hi,

just wondering if anyone knows where the Hitachi implementation of mipv6
for the Kame stack can be found?

Thank s in advance

Ryan



From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep 18 03:49:43 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA16176
	for <mobileip-archive@odin.ietf.org>; Tue, 18 Sep 2001 03:49:42 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id AAA19011;
	Tue, 18 Sep 2001 00:48:49 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id AAA24649;
	Tue, 18 Sep 2001 00:48:32 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8I7kI7B009780
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 18 Sep 2001 00:46:18 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8I7kIZi009779
	for mobile-ip-dist; Tue, 18 Sep 2001 00:46:18 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8I7kE7B009772
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 18 Sep 2001 00:46:15 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id AAA02462
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 18 Sep 2001 00:46:32 -0700 (PDT)
From: Wei.Zhuang@sae.siemens.com.sg
Received: from goliath.siemens.de ([194.138.37.131])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id AAA03246
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 18 Sep 2001 00:45:26 -0700 (PDT)
Received: from mail3.siemens.de (mail3.siemens.de [139.25.208.14])
	by goliath.siemens.de (8.11.6/8.11.6) with ESMTP id f8I7jPl14319
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 18 Sep 2001 09:45:25 +0200 (MET DST)
Received: from mail.siemens.com.sg (mail.siemens.com.sg [194.138.237.71])
	by mail3.siemens.de (8.11.6/8.11.6) with ESMTP id f8I7jNi5922322
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 18 Sep 2001 09:45:24 +0200 (MEST)
Received: from sgpk001a.sae.siemens.com.sg (sgpk001a.siemens.com.sg [140.231.107.1])
	by mail.siemens.com.sg (8.11.4/8.11.4) with ESMTP id f8I7jLY11345
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 18 Sep 2001 15:45:21 +0800 (SGT)
Received: by sgpk001a.siemens.com.sg with Internet Mail Service (5.5.2650.21)
	id <T1JJZK66>; Tue, 18 Sep 2001 15:46:42 +0800
Message-ID: <608F404BBCAAD3119F930800062838CBD7F874@SGPK200A>
To: mobile-ip@sunroof.eng.sun.com
Subject: RE: [mobile-ip] Hitachi's implementation
Date: Tue, 18 Sep 2001 15:47:46 +0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C14016.0CBDDE34"
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

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

------_=_NextPart_001_01C14016.0CBDDE34
Content-Type: text/plain;
	charset="iso-8859-1"

www.kame.net

-----Original Message-----
From: Eng Soo Guan [mailto:engsg@cwc.nus.edu.sg]
Sent: Tuesday, September 18, 2001 2:37 PM
To: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Hitachi's implementation


Dear Ryan,

This is the first time I heard of a MIPv6 implementation from Hitachi. May I
know where did you get the information?

Warmest regards.

ESG
Eng Soo Guan
R&D Engineer (Software Lab)
Centre for Wireless Communications, NUS
http://www.cwc.nus.edu.sg
Tel (65) 8709330
****************************************************
----- Original Message -----
From: Ryan Anthony Lea
To: mobile-ip@sunroof.eng.sun.com
Sent: Tuesday, September 18, 2001 2:22 PM
Subject: [mobile-ip] Hitachi's implementation


Hi,

just wondering if anyone knows where the Hitachi implementation of mipv6
for the Kame stack can be found?

Thank s in advance

Ryan

------_=_NextPart_001_01C14016.0CBDDE34
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2650.12">
<TITLE>RE: [mobile-ip] Hitachi's implementation</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=2>www.kame.net</FONT>
</P>

<P><FONT SIZE=2>-----Original Message-----</FONT>
<BR><FONT SIZE=2>From: Eng Soo Guan [<A HREF="mailto:engsg@cwc.nus.edu.sg">mailto:engsg@cwc.nus.edu.sg</A>]</FONT>
<BR><FONT SIZE=2>Sent: Tuesday, September 18, 2001 2:37 PM</FONT>
<BR><FONT SIZE=2>To: mobile-ip@sunroof.eng.sun.com</FONT>
<BR><FONT SIZE=2>Subject: Re: [mobile-ip] Hitachi's implementation</FONT>
</P>
<BR>

<P><FONT SIZE=2>Dear Ryan,</FONT>
</P>

<P><FONT SIZE=2>This is the first time I heard of a MIPv6 implementation from Hitachi. May I</FONT>
<BR><FONT SIZE=2>know where did you get the information?</FONT>
</P>

<P><FONT SIZE=2>Warmest regards.</FONT>
</P>

<P><FONT SIZE=2>ESG</FONT>
<BR><FONT SIZE=2>Eng Soo Guan</FONT>
<BR><FONT SIZE=2>R&amp;D Engineer (Software Lab)</FONT>
<BR><FONT SIZE=2>Centre for Wireless Communications, NUS</FONT>
<BR><FONT SIZE=2><A HREF="http://www.cwc.nus.edu.sg" TARGET="_blank">http://www.cwc.nus.edu.sg</A></FONT>
<BR><FONT SIZE=2>Tel (65) 8709330</FONT>
<BR><FONT SIZE=2>****************************************************</FONT>
<BR><FONT SIZE=2>----- Original Message -----</FONT>
<BR><FONT SIZE=2>From: Ryan Anthony Lea</FONT>
<BR><FONT SIZE=2>To: mobile-ip@sunroof.eng.sun.com</FONT>
<BR><FONT SIZE=2>Sent: Tuesday, September 18, 2001 2:22 PM</FONT>
<BR><FONT SIZE=2>Subject: [mobile-ip] Hitachi's implementation</FONT>
</P>
<BR>

<P><FONT SIZE=2>Hi,</FONT>
</P>

<P><FONT SIZE=2>just wondering if anyone knows where the Hitachi implementation of mipv6</FONT>
<BR><FONT SIZE=2>for the Kame stack can be found?</FONT>
</P>

<P><FONT SIZE=2>Thank s in advance</FONT>
</P>

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

</BODY>
</HTML>
------_=_NextPart_001_01C14016.0CBDDE34--


From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep 18 04:02:18 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA16306
	for <mobileip-archive@odin.ietf.org>; Tue, 18 Sep 2001 04:02:18 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id CAA13124;
	Tue, 18 Sep 2001 02:01:18 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id BAA26090;
	Tue, 18 Sep 2001 01:01:17 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8I7xQ7B009896
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 18 Sep 2001 00:59:26 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8I7xQ3b009895
	for mobile-ip-dist; Tue, 18 Sep 2001 00:59:26 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8I7xN7B009888
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 18 Sep 2001 00:59:23 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id AAA03836
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 18 Sep 2001 00:59:42 -0700 (PDT)
Received: from motgate4.mot.com (motgate4.mot.com [144.189.100.102])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id AAA09440
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 18 Sep 2001 00:59:41 -0700 (PDT)
Received: [from pobox3.mot.com (pobox3.mot.com [10.64.251.242]) by motgate4.mot.com (motgate4 2.1) with ESMTP id AAA10144 for <mobile-ip@sunroof.eng.sun.com>; Tue, 18 Sep 2001 00:59:41 -0700 (MST)]
Received: [from m-il06-r3.mot.com (m-il06-r3.mot.com [129.188.137.194]) by pobox3.mot.com (MOT-pobox3 2.0) with ESMTP id AAA02071 for <mobile-ip@sunroof.eng.sun.com>; Tue, 18 Sep 2001 00:51:10 -0700 (MST)]
Received: from thorgal.crm.mot.com by m-il06-r3.mot.com with ESMTP for mobile-ip@sunroof.eng.sun.com; Tue, 18 Sep 2001 00:59:29 -0700
Received: from test9.crm.mot.com.crm.mot.com (test9.crm.mot.com [140.101.173.239])
	by thorgal.crm.mot.com (Postfix) with ESMTP id 5C5C22ED1D
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 18 Sep 2001 09:56:59 +0200 (CEST)
To: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Hitachi's implementation
References: <200109180622.QAA20274@yallara.cs.rmit.edu.au>
	<011501c1400c$48367c00$a00310ac@cwc.nus.edu.sg>
From: Alexandru Petrescu <petrescu@crm.mot.com>
Date: 18 Sep 2001 09:59:29 +0200
In-Reply-To: <011501c1400c$48367c00$a00310ac@cwc.nus.edu.sg>
Message-Id: <m3wv2xhqu6.fsf@test9.crm.mot.com>
Lines: 10
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.0.103
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

"Eng Soo Guan" <engsg@cwc.nus.edu.sg> writes:
> This is the first time I heard of a MIPv6 implementation from Hitachi. May I
> know where did you get the information?

I think Hitachi does have an IPv6 stack for various Windows platforms.
Search toolnet6.

I don't know about Mobile IPv6.

Alex



From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep 18 13:37:04 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27220
	for <mobileip-archive@odin.ietf.org>; Tue, 18 Sep 2001 13:37:04 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id LAA06704;
	Tue, 18 Sep 2001 11:35:54 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id KAA23690;
	Tue, 18 Sep 2001 10:35:51 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8IHYh7B010933
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 18 Sep 2001 10:34:43 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8IHYhkj010932
	for mobile-ip-dist; Tue, 18 Sep 2001 10:34:43 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8IHYd7B010925
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 18 Sep 2001 10:34:39 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id KAA26776
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 18 Sep 2001 10:34:40 -0700 (PDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id KAA04556
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 18 Sep 2001 10:34:40 -0700 (PDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id KAA09348;
	Tue, 18 Sep 2001 10:34:36 -0700 (PDT)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f8IHYZ025510;
	Tue, 18 Sep 2001 10:34:35 -0700
X-mProtect:  Tue, 18 Sep 2001 10:34:35 -0700 Nokia Silicon Valley Messaging Protection
Received: from charliep.iprg.nokia.com (205.226.2.89, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpdBn8QuD; Tue, 18 Sep 2001 10:34:33 PDT
Message-ID: <3BA785A9.6BE2244B@iprg.nokia.com>
Date: Tue, 18 Sep 2001 10:34:33 -0700
From: "Charles E. Perkins" <charliep@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: mobile-ip@sunroof.eng.sun.com
CC: "Basavaraj Patil (NTC/Dallas)" <Basavaraj.Patil@nokia.com>,
        Thomas Narten <narten@raleigh.ibm.com>
Subject: Re: [mobile-ip] FW: draft-ietf-mobileip-mier-07.txt
References: <CD8355C7E19ED411BD5F00508BB0D19D697F18@megisto-sql1.megisto.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hello folks,

Here are some responses to the comments below about MIER, encountered
along the way towards integrating MIER into RFC2002bis.

The revised document (draft-ietf-mobileip-rfc2002-bis-08.txt)
is available at:
	http://people.nokia.net/charliep/txt/mobileip/mobileip.txt

> --------------------
> General comment. This ID seems to be of rather limited usefulness as a
> standalone RFC. Is it really needed? This document seems to update RFC
> 2002, but is informational. This can be remedied by:
> 
>   - making this standards track (seems overkill, since it doesn't
>     actually define an option, and hence, doesn't define anything
>     anyone needs to implement, from what I can tell)
>   - merge it in with 2002bis (which is being revised right now anyway)
>   - merge this document with GNAI, since the GNAI document is a
>     specific case where use of MIER might make sense.
>   - take out the MUST/SHOULDs and make it clear that this document is
>     only proposing an approach to encoding options, and that future
>     options writers should consider the issues raised when designing
>     their options. NOte: if this approach is used, other documents
>     (e.g., draft-ietf-mobileip-gnaie-04.txt) shouldn't have normative
>     references to this document. At present, gnai appears to do just
>     that.

Since I was asked to integrate MIER into RFC2002bis, I reckon
that the second alternative was selected.

> For example:
> 
>> MIER describes a new extension
>>     structure to Mobile IP to make the extensions far more
>>     extensible.
> 
> Could be rewritten as:
> 
>      MIER describes a way of encoding extensions that make it possible
>      to conserve MIP options in some cases. Authors of future options
>      should consider the issues raised in this document when designing
>      new options.
> 
> There are several other places in the document where the langauge
> could be toned down and made more neutral.

Here is the related paragraph in the new section 1.8:

   Unless additional structure is utilized for the extension types,
   new developments or additions to Mobile IP might require so many
   new extensions that the available space for extension types might
   run out.  Two new extension structures are proposed to solve this
   problem.  Certain types of extensions can be aggregated, using
   subtypes to identify the precise extension, for example as has been
   done with the Generic Authentication Keys extensions [35].  In many
   cases, this may reduce the rate of allocation for new values of the
   type field.

>>     It is in the interest of the Mobile IP WG to conserve the
>>     usage of the type field since we see many drafts proposing
>>     new extensions for Mobile IP. Therefore there is a real
> 
> There is an alternate approach, one that seems to be working in
> practice, and has other benefits. Don't allow IANA to assign options
> until there is significant support for an option, i.e, via something
> like "IETF consensus" [RFC 2434].  This approach also has the
> advantage that it discourages the use of many options anyway, a
> generaly desirable feature.  Usage of many options tends to negatively
> impact interoperability.
> 
> Finally, looking at the IANA pages, it does not appear that options
> are being used at a significant rate and that exhaustion of the space
> is serious issue at present.

Even though there are millions of Mobile IPv4 implementations out
there, the general feeling in the working group (and outside the
working group, I believe) is that Mobile IP is still in its infancy.
Of course if Mobile IPv6 fills the Internet need for seamless
mobility, then Mobile IPv4 may not grow as much as it would if
IPv4 maintains dominance.  Anyway, there is a realistic and
reasonable chance that Mobile IPv4 could grow quite a bit more.

Furthermore, since MIER passed working group Last Call, the
inference could be taken that the people involved with creating
new extensions decided that it was better to specify a useful
type/subtype template sooner rather than later.

Lastly, I should mention that I'm not exactly the right person
to be supplying these answers.  I didn't write MIER, and I didn't
participate much in the discussion after the first few months
where we talked about flags.  Even so, in the interest of getting
some progress for RFC2002bis (which now has to include MIER),
I try to provide my best understanding of the technical
reasoning for creating MIER.  Someone else with more involvement
might easily be able to correct any misstatements I might have
made.

>> 1.0 Introduction
>>
>>     The type field in the Mobile IP extension structure can support
>>     upto 255 (skippable and not skippable) uniquely identifiable
>>     extensions. With new developments/additions to Mobile IP
>>     there is a strong possibility that the available space will
>>     run out.
> 
> What evidence is there that this is true at present?

I think MIER was created in response to a perceived future
shortage, not in response to any existing current problem.

>>     Mobile IP Extensions Rationalization (MIER) describes a
>>     new extension structure to solve this problem. MIER strategy
>>     is to initially aggregate certain types of extensions (e.g,
>>     NAI) and sub types to identify the precise extension (example
>>     MN/User NAI, HA NAI etc). This will greatly reduce the usage
>>     of the type field.
> 
> Last sentence seems a bit too strong. Better to say "This may reduce
> the usage of the type field in some cases".

I hope the abovementioned paragraph from the new section 1.8
is O.K. for this.

>> 2.2 New Mobile IP Extension format
>>
>>     This draft proposes the following  two structures for Mobile IP
>>     extensions to be carried in the Mobile IP control messages.
>>     Since the new extension structures will cause an efficient
>>     usage of the extension type space, it is strongly recommended
>>     that all the new proposals for the Mobile IP WG that have new
>>     extensions SHOULD follow this format.
> 
> SHOULD wording seems a bit strong. Encoding options in this way makes
> sense in *some* cases, but it is not clear (to me) that it does so in
> even the majority of cases. It would be sufficient to say option
> writers should consider whether the structure defined here makes sense
> when a new option is defined. Saying they SHOULD follow it is too
> strong.

Fixed, I think.

>> 2.2.1 Long Extension Format
> 
> In the absence of a specific proposed need for a long option, I don't
> see the value in defining it. Moreover, will MIP *ever* define any
> more non-skippable options? Seems like doing so would be bad for
> interoperating with the installed base (which won't understand any
> newly defined options) . If that is the case, why define now? One can
> always define a long format later should it be deemed necessary.

There are already proposals for long options that could
reasonable be expected to use a MIER-ified extension layout.
For instance, the Registration Keys draft could do so.

>> 2.2.2 Short Extension Format
> 
> This format makes sense for some types of options (GNAI would seem to
> be one). It does not make sense for others. For example, of the
> existing MIP options, how many would it actually make sense to encode
> in this fashion?
> 
>>     Sub-Type  is a unique number given to each member in the
>>               aggregated type.  Sub-Type values between of 200 through
>>               255 are reserved for future use and standardization.
> 
> The semantics of this field are dependent on the actual option; it
> make no sense to say anything about reserving values in the general
> case. It *might* make sense to say something like that in the case of
> a specific option, but that would be the job of that specific option.

O.K.  Unless there is an objection, I will remove this sentence
about reserving values.  I agree it's better to leave this for
each specfic option.


Regards,
Charlie P.


From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep 18 19:07:11 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA04644
	for <mobileip-archive@odin.ietf.org>; Tue, 18 Sep 2001 19:07:10 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id RAA23126;
	Tue, 18 Sep 2001 17:05:56 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id QAA20959;
	Tue, 18 Sep 2001 16:04:42 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8IN3p7B011475
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 18 Sep 2001 16:03:51 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8IN3p4o011474
	for mobile-ip-dist; Tue, 18 Sep 2001 16:03:51 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8IN3l7B011467
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 18 Sep 2001 16:03:47 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id QAA25239
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 18 Sep 2001 16:03:49 -0700 (PDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id QAA13225;
	Tue, 18 Sep 2001 16:03:43 -0700 (PDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id QAA03571;
	Tue, 18 Sep 2001 16:03:43 -0700 (PDT)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f8IN3gZ28791;
	Tue, 18 Sep 2001 16:03:42 -0700
X-mProtect:  Tue, 18 Sep 2001 16:03:42 -0700 Nokia Silicon Valley Messaging Protection
Received: from rajeev.iprg.nokia.com (205.226.2.90, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpdvlWxxG; Tue, 18 Sep 2001 16:03:41 PDT
Message-ID: <3BA7D2CD.89447E43@iprg.nokia.com>
Date: Tue, 18 Sep 2001 16:03:41 -0700
From: Rajeev Koodli <rajeev@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: James Kempf <James.Kempf@sun.com>
CC: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] New BETH Draft
References: <200109172036.NAA14001@heliopolis.eng.sun.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hello James,

thanks for the reply. I would like to summarize this discussion.

1. the MN need not be aware that the ARs support BETH. When this is the case, the
MN waits for an RtAdv on a non-BETH router.

2. the MN may be made aware that the AR it is handing over to is a non-BETH
router. This could be done via an extension to PrRtAdv.

3. On a BETH AR, unsolicited Router Advertisements must be disabled, at least
until the BETH session is over.

I don't see how a MN can continue sending packets using it's old CoA if it does
not know that the new AR is a BETH AR. I mean it could send packets with old CoA,
but they are prone to be discarded due to ingress filtering by the new AR. In
other words, it *needs* to be informed about the BETH-ability of the new AR, one
way or the other.

In any case,  I see the following requirements.

R1. Due to 1), the MN is required not to send RtSol when it establishes a new
link.
R2. Due to 2), a L3 message over the air interface is needed.
R3. Due to 3), unsolicited router advertisements cannot be multicast to all-nodes
multicast address. They need to be sent only at the termination of a BETH session
to each MN.

To me R1 is undesirable. You would need this requirement in all the MNs.
R2 of course means bits spent over the air interface; however, this seems
inevitable.
I don't see issues with R3 other than defining new method to deliver RtAdvs.

Is this accurate ? If yes, could you add it to the current BETH proposal ?


Regards,

-Rajeev


James Kempf wrote:

> Hi Rajeev,
>
> >
> >I am seeking some clarifications below (at the end) regarding when a MN sends
> >RtSol and what does it do with RtAdv on the new AR. Your responses are
> >appreciated. I also have some comments below.
> >
>
> OK, I'll see what I can do.
>
> >> If the MN is doing BETH and it moves to a router where there is no
> >> BETH, the MN may be delaying L3 handover and so it will wait for
> >> the RtADv. If the old AR can tell it beforehand that it will move
> >> to a new AR without BETH, the MN can begin FMIPv6 handover (if
> >> the new AR supports FMIPv6) or it can know to stop doing BETH
> >> and do RtSol on the new router.
> >
> >I guess my point was there is no reason for the MN to wait for RtAdv in any
> >case. For instance, the Linux IPv6 MN that we have has the hook to send out a
> >RtSol as soon as an interface becomes enabled (i.e., when the MN undergoes
> >AP handover). One could call this type of a hook an L2 trigger and that is
> >implementation-specific.
> >
>
> Right, and normally that would be the case. But the scenario is that
> the MN is doing BETH, and in BETH the RtSol is suppressed since
> the network is handling the handover. If network handover fails,
> due to the MN running off the end of a BETH coverage area, then
> unless there is a signal that the MN is running off the end, it
> will just wait until the RtAdv occurs, because it doesn't know
> to solicit.
>
> >
> >Well, the other scenario you are referring to is not common either, right ? In
> >fact, I would argue that having an integrated AR-AP device would be a special
> >case for which we have limited experience currently. Today, both WLAN and
> >cellular have this model: there is a separate link between the AP and an AR.
> >I would guess that such a model would continue to exist.
> >
> >
>
> But from the cellular viewpoint, the MN doesn't see the AP. It's the
> stratified stack: the RAN protocol (even if it's all IP!) is hidden from
> the MN's stack. So most cellular systems will appear as if the AP
> and AR are integrated.
>
> I think the only real AP/AR deployments that matter are WLAN: 802.11
> primarily. Not sure about HiperLan or Bluetooth.
>
> >>
> >
> >Ok. Would it be possible to clearly specify what a link-layer trigger
> >constitues (e.g., it could actually span more than one link type) and some
> >examples ?
> >
>
> There are some hypothetical examples in draft-manyfolks-l2-mobilereq-00.txt.
> Perhaps we need to get a few from the CDMA world as more concrete examples?
>
> >So, it is requirement for the MN *not* to send a RtSol if it was moving into a
> >BETH router then ? For this to happen, the MN must be informed a priori by old
> >AR that the MN is moving into a BETH router as you point out.
>
> Yes, that's correct. The whole *point* of BETH is to eliminate the
> radio MIP signalling for L3 handover until either: a) the MN is prepared
> to pay the cost (i.e. it slows down, there is no real time traffic, etc.),
> or: b) The network can no longer support the tunnel. The latter
> includes the case of the MN running off the edge of the BETH coverage
> area.
>
> >That means
> >sending ProxyRtAdv with appripriate code is a necessity for BETH ?
>
> It is a further optimization that I think would be helpful. If the
> PrxyRtAdv with code is not sent, then the MN will simply wait
> on the new AR until an unsolicited RtAdv shows up and then do
> L3 handover (see below). The PrxyRtAdv optimizes this by allowing
> the MN to proactively perform L3 handover rather than waiting.
>
> >If yes, this
> >is not a corner case anymore.
> >
>
> What I meant was that the MN running off the edge of the coverage
> area and standard FMIPv6 is not implemented at the new AR.  I think
> that most ARs will at least support FMIPv6. If the new AR does,
> the old AR can simply send the PrxyRtAdv to the MN, and the MN will perform
> a standard FMIPv6 handover (even if it was doing BETH in the
> BETH coverage area).
>
> >Also, what happens if the MN receives an unsolicited RtAdv on the new AR when
> >it is in a BETH session ?
> >
>
> Then it *must* begin the process of L3 handover, to establish a new
> CoA at the new AR. An unsolicited RtAdv is an indication from the
> AR that it is no longer prepared to maintain the bidirectional edge
> tunnel, and so the MN must establish a new CoA.
>
> Does that make sense?
>
>                 jak



From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep 18 19:19:07 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA04852
	for <mobileip-archive@odin.ietf.org>; Tue, 18 Sep 2001 19:19:06 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id RAA01068;
	Tue, 18 Sep 2001 17:18:09 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id QAA24144;
	Tue, 18 Sep 2001 16:18:06 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8INHD7B011547
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 18 Sep 2001 16:17:13 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8INHDsU011546
	for mobile-ip-dist; Tue, 18 Sep 2001 16:17:13 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from heliopolis.eng.sun.com (bigbang.Eng.Sun.COM [152.70.8.30])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8INH97B011539
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 18 Sep 2001 16:17:10 -0700 (PDT)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.eng.sun.com (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id QAA24480;
	Tue, 18 Sep 2001 16:17:10 -0700 (PDT)
Message-Id: <200109182317.QAA24480@heliopolis.eng.sun.com>
Date: Tue, 18 Sep 2001 16:17:10 -0700 (PDT)
From: James Kempf <James.Kempf@sun.com>
Subject: Re: [mobile-ip] New BETH Draft
To: James.Kempf@sun.com, rajeev@iprg.nokia.com
Cc: mobile-ip@sunroof.eng.sun.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: E4tsv/ES2libQ+ODNJfr9w==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Hi Rajeev,

Comments embedded.

>thanks for the reply. I would like to summarize this discussion.
>
>1. the MN need not be aware that the ARs support BETH. When this is the case, the
>MN waits for an RtAdv on a non-BETH router.
>

Within a BETH coverage area, yes. Outside of a BETH coverage area, it depends
on whether the MN has been informed that it is leaving the area or not.

>2. the MN may be made aware that the AR it is handing over to is a non-BETH
>router. This could be done via an extension to PrRtAdv.
>

Yes, necessary if the MN is to perform FMIPv6 handover, or, lacking FMIPv6
capability in the new AR, standard MIPv6 handover.

>3. On a BETH AR, unsolicited Router Advertisements must be disabled, at least
>until the BETH session is over.
>

If you mean sending of unsolicited RtAdv from the AR, yes.

>I don't see how a MN can continue sending packets using it's old CoA if it does
>not know that the new AR is a BETH AR. I mean it could send packets with old CoA,
>but they are prone to be discarded due to ingress filtering by the new AR. In
>other words, it *needs* to be informed about the BETH-ability of the new AR, one
>way or the other.
>

Yes, if the AR has no Neighbor Cache entry for the MN, they would likely be
discarded. Like I've been trying to emphasize and like the new draft says,
the MN showing up at an AR where it doesn't know what kind of service
is available is a misconfiguration that may result in suboptimal service.

>In any case,  I see the following requirements.
>
>R1. Due to 1), the MN is required not to send RtSol when it establishes a new
>link.

If you are talking about within the BETH coverage area, yes.

>R2. Due to 2), a L3 message over the air interface is needed.

If you are talking about notifying the MN when it leaves the BETH coverage
area, then yes.

>R3. Due to 3), unsolicited router advertisements cannot be multicast to all-nodes
>multicast address. They need to be sent only at the termination of a BETH session
>to each MN.
>

Right. The draft says this for FMIPv6 handover in both the case where the
MN terminates the BETH session and where the AR terminates the session. It
currently does not state this for standard MIP handover, because there
is currently no way in FMIPv6 to indicate that the MN should use standard
MIP handover.

>To me R1 is undesirable. You would need this requirement in all the MNs.

Only if the MN supports BETH. That will depend on the availability of
L2 triggers and therefore of the radio protocol. If the radio interface
does not support the requirements for BETH, obviously, the MN can't support it.

>R2 of course means bits spent over the air interface; however, this seems
>inevitable.

It is only inevitable when the MN leaves the BETH coverage area. If it is within
a coverage area, there is no reason for it, the network can take care of
the handover.

>I don't see issues with R3 other than defining new method to deliver RtAdvs.
>
>Is this accurate ? If yes, could you add it to the current BETH proposal ?
>
>

I will be happy to add a new code to PrxyRtAdv allowing the AR to inform
the MN when it leaves the BETH coverage area and is moving to a coverage
area where FMIPv6 service is unavailable. I believe the draft already
allows the AR to inform the MN when it is leaving a BETH coverage
area and FMIPv6 service is available. This is standard FMIPv6 handover.

		jak




From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep 18 19:22:08 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA04898
	for <mobileip-archive@odin.ietf.org>; Tue, 18 Sep 2001 19:22:08 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id QAA25395;
	Tue, 18 Sep 2001 16:20:56 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id QAA24473;
	Tue, 18 Sep 2001 16:19:09 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8INIJ7B011564
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 18 Sep 2001 16:18:19 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8INIJ61011563
	for mobile-ip-dist; Tue, 18 Sep 2001 16:18:19 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8INIF7B011556
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 18 Sep 2001 16:18:15 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id QAA28555
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 18 Sep 2001 16:18:17 -0700 (PDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id RAA23649
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 18 Sep 2001 17:19:05 -0600 (MDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id QAA05070;
	Tue, 18 Sep 2001 16:18:15 -0700 (PDT)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f8INIEn20727;
	Tue, 18 Sep 2001 16:18:14 -0700
X-mProtect:  Tue, 18 Sep 2001 16:18:14 -0700 Nokia Silicon Valley Messaging Protection
Received: from rajeev.iprg.nokia.com (205.226.2.90, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpdiDsxFQ; Tue, 18 Sep 2001 16:18:12 PDT
Message-ID: <3BA7D634.ACEDA9BC@iprg.nokia.com>
Date: Tue, 18 Sep 2001 16:18:12 -0700
From: Rajeev Koodli <rajeev@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: mobile-ip@sunroof.eng.sun.com
CC: James Kempf <James.Kempf@Sun.COM>
Subject: Re: [mobile-ip] New BETH Draft
References: <A5B4C9A2AD89D411AB3E009027B0DA1E3B2110@IL27EXM09.cig.mot.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hello Ajoy,

Singh Ajoy-ASINGH1 wrote:

> Hello Rajeev/James/Alper:
> Sorry for jumping in the middle.
> Please find my inline response.
> regards,
> ajoy
>
> -----Original Message-----
> From: Rajeev Koodli [mailto:rajeev@iprg.nokia.com]
> Sent: Friday, September 14, 2001 7:34 PM
> To: James Kempf
> Cc: mobile-ip@sunroof.eng.sun.com
> Subject: Re: [mobile-ip] New BETH Draft
>
> Hello James,
>
> I am seeking some clarifications below (at the end) regarding when a MN sends
> RtSol and what does it do with RtAdv on the new AR. Your responses are
> appreciated. I also have some comments below.
>
> Regards,
>
> -Rajeev
>
> James Kempf wrote:
>
> >
> > If the MN is doing BETH and it moves to a router where there is no
> > BETH, the MN may be delaying L3 handover and so it will wait for
> > the RtADv. If the old AR can tell it beforehand that it will move
> > to a new AR without BETH, the MN can begin FMIPv6 handover (if
> > the new AR supports FMIPv6) or it can know to stop doing BETH
> > and do RtSol on the new router.
>
> I guess my point was there is no reason for the MN to wait for RtAdv in any
> case. For instance, the Linux IPv6 MN that we have has the hook to send out a
> RtSol as soon as an interface becomes enabled (i.e., when the MN undergoes
> AP handover). One could call this type of a hook an L2 trigger and that is
> implementation-specific.
>
> ajoy-> I do not think the example of Linux Mobile/IP is appropriate here.
> I do not think if Linux does some way, we should write the spec according to
> that. Here we are talking about enabling Voice over IP for wireless user,
> which will require different treatment from the way Mobile/IP was
> implemented for purely non-real time data traffic.
>

Well, going by your own argument, writing a spec based on your favorite application is also not
appropriate, I guess.. The point of bringing up the example above was a *link-layer* trigger could
be implemented, potentially in any civilized OS, to solicit router advertisements.


>
> > That is for a particular implementation which happens to be common
> > right now for a particular radio protocol. It is by no means the
> > common to all radio protocols, and even in the protocol for
> > which it is currently common, it is likely to change.
> >
>
> Well, the other scenario you are referring to is not common either, right ? In
> fact, I would argue that having an integrated AR-AP device would be a special
> case for which we have limited experience currently. Today, both WLAN and
> cellular have this model: there is a separate link between the AP and an AR.
> I would guess that such a model would continue to exist.
>
> -> I do not think getting link layer trigger at AR is difficult in case of
> existing cellular network. In fact such work is in progress in
> 3GPP2. I am positive this can be done in 3GPP,
> provided 3GPP decides to use Mobile/IP.
>

Ok. What do you have to say about the link between the AP and the AR ? What link type is used there
? If I choose to use ethernet, I have to figure out how to send a trigger to the AR in response to
the trigger from the MN, right ?


>
> >
> > The MN would only be required to send a RtSol if it had been informed
> > ahead of time on the old AR that it was moving out of a BETH
> > coverage area. This is why I proposed adding a code to the PrxyRtAdv,
> > so that the old AR could do this. Otherwise, the optimization
> > of BETH provided by lack of any L3 MIP signalling would be invalidated.
>
> So, it is requirement for the MN *not* to send a RtSol if it was moving into a
> BETH router then ? For this to happen, the MN must be informed a priori by old
> AR that the MN is moving into a BETH router as you point out. That means
> sending ProxyRtAdv with appripriate code is a necessity for BETH ? If yes, this
> is not a corner case anymore.
>
> -> I think this is a corner case. Could you please provide any realistic example where
> MN can move from BETH capable AR to nonBETH capable AR in same technology ? I am having hard time
> to imagine any scenario where we need seamless handover from one AR to other without
> any prior agreement between neighboring ARS. Please note that this argument can be
> made for any access protocol. For example, please find a few:
>

The point here is that the MN needs to know what type of an AR it is moving into. Even if you have
the same technology on the two routers, does that constitute a binding requirement that the target
AR is also a BETH AR ? What if it belongs to a different operator ? Furthermore, after being
informed about the target AR, the MN has to abstain from sending out Router Solicitations as soon as
the new link is established. This is a requirement on the MNs to implement.

I don't have any problem with optimizations. Their implications, however, have to be clearly defined
and made known.

Regards,

-Rajeev


>
> What happens when MN moves from AR which supports PPP to the
> AR which does not support PPP ? What happens if PPP unaware MN
> tries to connect to non-PPP aware AR ? ....
>
> Regards,
>
> -Rajeev
>
> >
> >
> >                 jak



From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep 18 19:26:18 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA04954
	for <mobileip-archive@odin.ietf.org>; Tue, 18 Sep 2001 19:26:17 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id RAA05381;
	Tue, 18 Sep 2001 17:25:21 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id QAA25810;
	Tue, 18 Sep 2001 16:25:24 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8INOd7B011632
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 18 Sep 2001 16:24:39 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8INOdYd011631
	for mobile-ip-dist; Tue, 18 Sep 2001 16:24:39 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from jurassic.eng.sun.com (jurassic [129.146.86.31] (may be forged))
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8INOa7B011624
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 18 Sep 2001 16:24:36 -0700 (PDT)
Received: from istanbul.Eng.Sun.COM (istanbul.Eng.Sun.COM [129.146.86.247])
	by jurassic.eng.sun.com (8.12.0+Sun/8.12.0) with SMTP id f8INObVj337983;
	Tue, 18 Sep 2001 16:24:38 -0700 (PDT)
Message-Id: <200109182324.f8INObVj337983@jurassic.eng.sun.com>
Date: Tue, 18 Sep 2001 16:24:27 -0700 (PDT)
From: Alper Yegin <Alper.Yegin@eng.sun.com>
Subject: Re: [mobile-ip] New BETH Draft
To: mobile-ip@sunroof.eng.sun.com
Cc: gdommety@cisco.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: 5afrF+vlR75zlkKIoRVUxg==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4_37 SunOS 5.8.1 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Hi James,

> >> 1) The MN is doing BETH supported by the network.
> >> 
> >> 2) It comes to an AR that must hand it over to a new AR without support
> >> for either FMIPv6 or BETH.
> >> 
> >> 3) The current AR does not know that the next AR doesn't support
> >> FMIPv6 nor BETH, so it cannot send a PrxyRtAdv to the MN, which
> >> would trigger the MN to stop doing BETH and solicit a RtAdv on
> >> the new AR.
> >> 
> >> 4) As a consequence, the MN gets onto the new AR and must wait
> >> until a RtAdv shows up from it.
> >> 
> >> Right? If so, IMHO, as I mentioned in the draft, this is likely to
> >> be a corner case and the result of misconfiguration or lack
> >> of use of CAR discovery, and so not very common. But it should
> >> be covered.
> >
> >Reading this, I understand you are proposing adding a PrRtAdv to the 
protocol. 
> >This should be sent prior to MN detaching from old link. And it can indicate 
> >whether the Mn is going to handoff to a BETH supporting AR or not. Right? If 
> so, 
> >this should help.
> >
> 
> What I am proposing is that if the old AR knows that the new AR does
> not support FMIPv6, it sends a PrxyRtAdv with a new code indicating
> that. This benefits *both* a BETH capable MN and one that is doing
> standard FMIPv6. If the new AR does support FMIPv6, of course, it sends a 

I think this already exists for FMIPv6. Checking the draft, code 128 of PrRtAdv 
can be used for this case as well.


> PrxyRtAdv with one of the existing codes. If the new AR doesn't
> know what the new AR supports, it sends a PrxyRtAdv with code 255.
> And finally, if the new AR doesn't even know that a handover is
> coming nor where, we are out of luck and the MN must wait til
> it gets to the new AR to discover that fact, regardless of whether
> FMIPv6 or BETH is used.
> 
> 
> >But this is not in the draft yet, right? Also, would you send this message 
all 
> >the time, regadless of whether nAR is BETH capable or not. I'd recommend so.
> >
> 
> No it is not in the draft, but I will fold it in when I incorporate the BETH 
> draft into the FMIPv6 draft. The message only gets sent if the new AR
> is not BETH capable, otherwise, it compromises the optimization of
> radio link traffic.
> 
> >So, now answering your above question: yes, I agree this is a misconfig given 
> >that now we have such a message to inform MN.
> >
> 
> OK.
> 
> >> >I don't think you can rely on nAR sending RA or not sending to figure out 
> >BETH 
> >> >support on ARs.
> >> >
> >> 
> >> MIPv6 isn't RFC yet. If we need to, we can ask Charlie to stick some words 
in 
> >it
> >> about the AR optimizing RtAdv similar to the words about the MN optimizing
> >> movement detection on pg. 80, and we probably should, not just for
> >> FMIPv6.
> >
> >Yes, we can think about that too. But unless I misunderstood, we are already 
> >accomplishing this by sending a PrRtAdv. MN already knows by the time it 
> >attaches to new link.
> >
> 
> But consider exactly the same case where the MN is doing FMIPv6 instead of 
BETH,
> new AR is not capable of doing FMIPv6, and the MN gets no trigger
> information indicating when handover has occured but the AR does.
> Even if the MN gets the PrxyRtAdv, it may come with code 255 or the
> new code, indicating the new AR is unknown or that it does standard MIPv6 
> handover.  The MN must then wait until it receives the unsolicited RtAdv 
before 
> it can begin L3 handover. If the new AR sends the unsolicited RtAdv 
immediately 
> upon L2 handover, the MN will start L3 handover more quickly. 

With FMIPv6, if MN knows the new AR is not going to help with handoff, then MN 
can send a RS as soon as it attaches to that link. I think this is the fastest 
thing that MN can do under this circumstance. (are there any L2s that doesn't 
provide an "attached" indication to mobile side?)

> 
> >> 
> >> >Also, for any new message between the MN and the AR, I think you are 
> >diverging 
> >> >from your goal of zero latency, which relies on no-L3 traffic.
> >> >
> >> 
> >> See discussion above. This is a corner case. When it happens, it
> >> means the MN must terminate BET handover and start doing
> >> standard MIPv6 handover (i.e. it cannot even do FMIPv6 handover).
> >
> >
> >If you add PrRtAdv, then you are adding latency.
> >
> 
> Right, but this is *only* when you run off the edge of a BETH coverage
> area. At that point, you have very little choice, and taking the
> hit of a known amount of radio traffic delay in place of an unknown amount
> if the MN gets to the new AR and must wait for the RtAdv is probably
> a good bet.


OK, I see. This PrRtAdv is only sent when MN is leaving the BETH domain.

But then I guess you'd need another message to inform MN when it is entering a 
BETH domain. So that it doesn't attempt FMIPv6 or MIPv6, and leave the handoff 
to ARs.


> 
> 
> >> Right, but there's no choice. The next AR can't do BETH anyway.
> >
> >Same question as above: are we going to always send a PrRtAdv to MN, or not?
> >
> 
> The answer is no. Only when the MN runs off the edge of the BETH
> coverage area.

I'd have preferred "receipt of a message" as the indication of whether next AR 
support BETH or not. Not receiving a message means it does. This message might 
be lost due to some other reason. ..  Now MN is waiting for its traffic, and ARs 
are doing nothing.

> 
> 
> >If MN thinks BETH is going on and if this is not the case, since MN would 
hold 
> >on to sending RS (BETH says so, right?), the performance would be worse than 
> >base-MIPv6. Because, if MN had known, then it could send an RS and expedite 
the 
> >process.
> >
> >A solution, if I understand right, is to send a PrRtAdv from oAR to MN. But 
now 
> >this introduces L3 latency. Then I think we should take a look at the 
> >performance gains over FMIPv6 again.
> >
> 
> I agree. If the old AR knows the new one doesn't support BETH or FMIPv6,
> it should tell the MN via the PrxyRtAdv. If the new AR supports BETH,
> the old AR should send nothing.
> 
> >I think we should also look at other cases: BETH-enabled MN doing handoff 
from 
> >one non-BETH-AR to another non-BETH-AR. 
> 
> If the MN gets a PrxyRtAdv, then it knows not to use BETH. 

But these non-BETH-enabled ARs don't have to send PrRtAdv. They can be simple 
IPv6 routers. I think MN should keep a state. As soon as it receives a PrRtAdv 
from a BETH-enabled AR, it should declare it's leaving BETH-domain. But then, at 
some point, it should also be able to detect moving into a BETH-domain. Maybe 
another message for that?

> 
> >BETH-enabled MN entering back into a 
> >BETH domain..
> >
> 
> If the MN does not receive a PrxyRtAdv from the network and it
> detects an L2 trigger for handover, then it knows the network
> is handling the handover. Provided, of course, the MN knows
> that the network supports FMIPv6/BETH.

But MN doesn't know that. It just attached to a new AR. I think this AR should 
send a message to MN indicating MN is entering a BETH domain.

> 
> But you bring up another, wider issue: how does an MN know that the
> AR is capable of doing FMIPv6 or BETH in the first place? For example,
> suppose the MN wants to do mobile initiated FMIPv6 handover. Does it
> just send off the SolPrxyRtAdv without any indication whatsoever that
> the AR can perform FMIPv6, or does the MN receive some indication
> beforehand that the AR is FMIPv6 capable? Similarly for BETH.

With FMIPv6, the response to PrRtSol indicates the support it can get from the 
AR. If AR doesn't recognize this solicitaiton, MN gets no response. Therefore no 
FMIPv6.

> 
> >And on another case is: what if MN is not BETH-enabled? How does BETH-enabled 
> >ARs treat them..
> >
> 
> Like FMIPv6. FMIPv6 is the fallback case, if that isn't available, then
> standard MIPv6.


yes, but how does AR know that MN doesn't support BETH? There's no two-way 
exchange of information between two. 

> 
> >I think these are missing in the draft.
> >
> 
> I need to look through it. Perhaps I need to add a section or paragraph
> about fall back positions, and something is probably needed in the
> FMIPv6 base draft as well.
> 
> 		jak

alper



From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep 18 19:45:45 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05131
	for <mobileip-archive@odin.ietf.org>; Tue, 18 Sep 2001 19:45:44 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id RAA16398;
	Tue, 18 Sep 2001 17:44:48 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id QAA00383;
	Tue, 18 Sep 2001 16:44:51 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8INht7B011701
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 18 Sep 2001 16:43:55 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8INhtug011700
	for mobile-ip-dist; Tue, 18 Sep 2001 16:43:55 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8INhp7B011693
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 18 Sep 2001 16:43:51 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id QAA00828
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 18 Sep 2001 16:43:53 -0700 (PDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id RAA15781;
	Tue, 18 Sep 2001 17:43:44 -0600 (MDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id QAA06646;
	Tue, 18 Sep 2001 16:43:52 -0700 (PDT)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f8INhpH28223;
	Tue, 18 Sep 2001 16:43:51 -0700
X-mProtect:  Tue, 18 Sep 2001 16:43:51 -0700 Nokia Silicon Valley Messaging Protection
Received: from rajeev.iprg.nokia.com (205.226.2.90, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpdBeVDtH; Tue, 18 Sep 2001 16:43:49 PDT
Message-ID: <3BA7DC36.D910CF3@iprg.nokia.com>
Date: Tue, 18 Sep 2001 16:43:50 -0700
From: Rajeev Koodli <rajeev@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: James Kempf <James.Kempf@sun.com>
CC: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] New BETH Draft
References: <200109182317.QAA24480@heliopolis.eng.sun.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hello again James,

it appears that we are in sync. However, I would like to see clear descriptions of

- what are the requirements for a BETH MN
- what are the requirements for a BETH AR

in the draft, especially if it needs to be part of the FMIPv6 draft. As I understand,
BETH is a very specific optimization with underlying assumptions and associated
requirements. They need to be *clearly* specified, perhaps in an individual section.
If such a thing already exists, please excuse this note.

Regards,

-Rajeev



James Kempf wrote:

> Hi Rajeev,
>
> Comments embedded.
>
> >thanks for the reply. I would like to summarize this discussion.
> >
> >1. the MN need not be aware that the ARs support BETH. When this is the case, the
> >MN waits for an RtAdv on a non-BETH router.
> >
>
> Within a BETH coverage area, yes. Outside of a BETH coverage area, it depends
> on whether the MN has been informed that it is leaving the area or not.
>
> >2. the MN may be made aware that the AR it is handing over to is a non-BETH
> >router. This could be done via an extension to PrRtAdv.
> >
>
> Yes, necessary if the MN is to perform FMIPv6 handover, or, lacking FMIPv6
> capability in the new AR, standard MIPv6 handover.
>
> >3. On a BETH AR, unsolicited Router Advertisements must be disabled, at least
> >until the BETH session is over.
> >
>
> If you mean sending of unsolicited RtAdv from the AR, yes.
>
> >I don't see how a MN can continue sending packets using it's old CoA if it does
> >not know that the new AR is a BETH AR. I mean it could send packets with old CoA,
> >but they are prone to be discarded due to ingress filtering by the new AR. In
> >other words, it *needs* to be informed about the BETH-ability of the new AR, one
> >way or the other.
> >
>
> Yes, if the AR has no Neighbor Cache entry for the MN, they would likely be
> discarded. Like I've been trying to emphasize and like the new draft says,
> the MN showing up at an AR where it doesn't know what kind of service
> is available is a misconfiguration that may result in suboptimal service.
>
> >In any case,  I see the following requirements.
> >
> >R1. Due to 1), the MN is required not to send RtSol when it establishes a new
> >link.
>
> If you are talking about within the BETH coverage area, yes.
>
> >R2. Due to 2), a L3 message over the air interface is needed.
>
> If you are talking about notifying the MN when it leaves the BETH coverage
> area, then yes.
>
> >R3. Due to 3), unsolicited router advertisements cannot be multicast to all-nodes
> >multicast address. They need to be sent only at the termination of a BETH session
> >to each MN.
> >
>
> Right. The draft says this for FMIPv6 handover in both the case where the
> MN terminates the BETH session and where the AR terminates the session. It
> currently does not state this for standard MIP handover, because there
> is currently no way in FMIPv6 to indicate that the MN should use standard
> MIP handover.
>
> >To me R1 is undesirable. You would need this requirement in all the MNs.
>
> Only if the MN supports BETH. That will depend on the availability of
> L2 triggers and therefore of the radio protocol. If the radio interface
> does not support the requirements for BETH, obviously, the MN can't support it.
>
> >R2 of course means bits spent over the air interface; however, this seems
> >inevitable.
>
> It is only inevitable when the MN leaves the BETH coverage area. If it is within
> a coverage area, there is no reason for it, the network can take care of
> the handover.
>
> >I don't see issues with R3 other than defining new method to deliver RtAdvs.
> >
> >Is this accurate ? If yes, could you add it to the current BETH proposal ?
> >
> >
>
> I will be happy to add a new code to PrxyRtAdv allowing the AR to inform
> the MN when it leaves the BETH coverage area and is moving to a coverage
> area where FMIPv6 service is unavailable. I believe the draft already
> allows the AR to inform the MN when it is leaving a BETH coverage
> area and FMIPv6 service is available. This is standard FMIPv6 handover.
>
>                 jak



From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep 19 07:08:29 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA28940
	for <mobileip-archive@odin.ietf.org>; Wed, 19 Sep 2001 07:08:28 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id EAA01803;
	Wed, 19 Sep 2001 04:07:01 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id EAA19174;
	Wed, 19 Sep 2001 04:06:53 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8JB667B012692
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 19 Sep 2001 04:06:06 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8JB65xD012691
	for mobile-ip-dist; Wed, 19 Sep 2001 04:06:05 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8JB617B012684
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 19 Sep 2001 04:06:01 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id EAA15218
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 19 Sep 2001 04:06:02 -0700 (PDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id FAA28191
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 19 Sep 2001 05:05:51 -0600 (MDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA28827;
	Wed, 19 Sep 2001 07:06:40 -0400 (EDT)
Message-Id: <200109191106.HAA28827@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: mobile-ip@sunroof.eng.sun.com
From: Internet-Drafts@ietf.org
Subject: [mobile-ip] I-D ACTION:draft-ietf-mobileip-rfc2002-bis-08.txt
Date: Wed, 19 Sep 2001 07:06:40 -0400
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

--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		: IP Mobility Support for IPv4, revised
	Author(s)	: C. Perkins
	Filename	: draft-ietf-mobileip-rfc2002-bis-08.txt
	Pages		: 96
	Date		: 18-Sep-01
	
This document specifies protocol enhancements that allow transparent
routing of IP datagrams to mobile nodes in the Internet.  Each
mobile node is always identified by its home address, regardless of
its current point of attachment to the Internet.  While situated
away from its home, a mobile node is also associated with a
care-of address, which provides information about its current
point of attachment to the Internet.  The protocol provides for
registering the care-of address with a home agent.  The home agent
sends datagrams destined for the mobile node through a tunnel to
the care-of address.  After arriving at the end of the tunnel, each
datagram is then delivered to the mobile node.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mobileip-rfc2002-bis-08.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-rfc2002-bis-08.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-rfc2002-bis-08.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:	<20010918152124.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-mobileip-rfc2002-bis-08.txt

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

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

--OtherAccess--

--NextPart--




From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep 19 09:39:59 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02173
	for <mobileip-archive@lists.ietf.org>; Wed, 19 Sep 2001 09:39:58 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id GAA17121;
	Wed, 19 Sep 2001 06:38:36 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id GAA06471;
	Wed, 19 Sep 2001 06:37:57 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8JDXp7B012839
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 19 Sep 2001 06:33:51 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8JDXpVZ012838
	for mobile-ip-dist; Wed, 19 Sep 2001 06:33:51 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8JDXm7B012831
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 19 Sep 2001 06:33:48 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id GAA05758
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 19 Sep 2001 06:33:50 -0700 (PDT)
Received: from mail1.kth.se (mail1.kth.se [130.237.32.62])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id HAA21620
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 19 Sep 2001 07:34:38 -0600 (MDT)
Received: from kth.se (yorick.admin.kth.se [130.237.32.55])
	by mail1.kth.se (8.11.5/8.11.5) with SMTP id f8JDXlR26387;
	Wed, 19 Sep 2001 15:33:47 +0200 (MEST)
Message-ID: <39022001931913334732@kth.se>
X-EM-Version: 5, 0, 0, 13
X-EM-Registration: #0000530610E41400EC10
X-Originating-IP: 130.237.50.86
From: "Babak Ayani" <babakay@kth.se>
To: mobile-ip@sunroof.eng.sun.com
Subject: [mobile-ip] How many MNs connected to a HA?
Date: Wed, 19 Sep 2001 15:33:47 +0200
MIME-Version: 1.0
Content-type: text/plain; charset=ISO-8859-1
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Hi
Sorry if this question sounds stupid but I haven't been able to find any
information about this.
I'm doing my Ms thesis about handoffs in Mobile IP and I'm trying to
calculate an approximate handoff time 
when having a buffer at the HA. In order to be able to do this, I need to
know approximately how many MNs that usually are connected to 
one HA (is it 5, 10, 50, 100 or more?).
Is it possible that only one MN is connected to a HA?
Thanks for your help in advance.

Babak



From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep 19 12:42:43 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA06086
	for <mobileip-archive@odin.ietf.org>; Wed, 19 Sep 2001 12:42:43 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id JAA20056;
	Wed, 19 Sep 2001 09:41:45 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA21686;
	Wed, 19 Sep 2001 09:41:18 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8JGe47B012986
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 19 Sep 2001 09:40:04 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8JGe4Dg012985
	for mobile-ip-dist; Wed, 19 Sep 2001 09:40:04 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from eastmail2.East.Sun.COM (eastmail2.East.Sun.COM [129.148.1.241])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8JGe27B012978
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 19 Sep 2001 09:40:02 -0700 (PDT)
Received: from onion.east.sun.com (onion.East.Sun.COM [129.148.174.110])
	by eastmail2.East.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id MAA25411
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 19 Sep 2001 12:40:03 -0400 (EDT)
Received: (from glass@localhost)
	by onion.east.sun.com (8.9.3+Sun/8.9.3) id MAA20041
	for mobile-ip@sunroof.eng.sun.com; Wed, 19 Sep 2001 12:40:34 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8J55K7B012203;
	Tue, 18 Sep 2001 22:05:20 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id WAA14446;
	Tue, 18 Sep 2001 22:05:21 -0700 (PDT)
Received: from lochinvar.ece.neu.edu (mail2.ece.neu.edu [129.10.60.82])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id WAA20622;
	Tue, 18 Sep 2001 22:05:21 -0700 (PDT)
Received: from runner.ece.neu.edu (runner.ece.neu.edu [129.10.60.136])
	by lochinvar.ece.neu.edu (8.9.3/8.9.3) with ESMTP id BAA10675;
	Wed, 19 Sep 2001 01:07:22 -0400 (EDT)
Received: from localhost by runner.ece.neu.edu (8.9.3/8.9.3) with ESMTP id BAA04292;
	Wed, 19 Sep 2001 01:05:05 -0400 (EDT)
X-Authentication-Warning: runner.ece.neu.edu: mcdonald owned process doing -bs
Date: Wed, 19 Sep 2001 01:05:05 -0400 (EDT)
From: "A. Bruce McDonald" <mcdonald@ECE.NEU.EDU>
X-Sender: mcdonald@runner
To: CNDS 2002 CFP <mcdonald@ECE.NEU.EDU>
Subject: [mobile-ip] CNDS 2002 (FINAL CALL FOR PAPERS) 
Message-ID: <Pine.GSO.4.21.0109190104010.4285-100000@runner>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

                         FINAL CALL FOR PAPERS

			       CNDS'2002

		    Submission Deadline: Sept 21, 2001
 		 (submissions accepted via ftp or email)		
	
   	        (Check web site for any last minute changes)
		
          
-----------------------------------------------------------------------
	Please Accept Our Sincere Apologies Should you Receive 

                      Multiple Copies of this CFP
-----------------------------------------------------------------------

    
  The Society for Modeling and Simulation International (SCS) presents:

             COMMUNICATION NETWORKS AND DISTRIBUTED SYSTEMS
                   MODELING AND SIMULATION CONFERENCE
                                  2002

   Part of the 2002 SCS Western Multiconference on Computer Simulation


                          January 27-31, 2002

                Four Points Sheraton Hotel, Riverwalk North
                           San Antonio, Texas


                   Keynote Address by Dr. Erol Gelenbe
       Professor of Computer Science and of Electrical Engineering, 
                    Director of the School of EECS and
Associate Dean of Engineering at the University of Central Florida in Orlando.

       Please Visit the Conference Web Site for Additional Information

	          http://www.ece.neu.edu/conf/CNDS/2002/

-----------------------------------------------------------------------

Original, high-quality technical papers, addressing significant
aspects of the design, modeling, or performance analysis of communication
networks and distributed systems are solicited for review, possible
presentation and subsequent publication in the conference proceedings. 
Papers that include well-conceived or innovative simulation modeling
techniques with strong results and analysis are especially sought.

Papers are solicited from not limited to the following topics:

	* Performance Modeling and Analysis 	
	* Mobile and Nomadic Computing 
	* Distributed and Wireless Multimedia Systems  
	* QoS Support for Wireless Ad Hoc Network Applications
	* Routing and Mobility Management in Wireless Networks
	* Power Control in Wireless Computer Systems
	* Distributed and Intelligent Sensor Networks
	* Wearable Computer Systems		
	* Resource Allocation in High Speed Networks
	* Switch and Processor Architectures for High Speed Routers
	* Advances in Computer Architecture and Memory Systems
        * Network and Parallel Computing
	* Storage Area Networks		
	* Content Based Image Retrieval Systems
	* Real-Time and Mobile Web-Based Computing
	* Reliable Multicast Routing and Group Communications  
	* Network and Application Security and Availability                
	* Web Caching and Switching 
        * Scalable and Reliable Distributed Servers
        * Load Balancing in Distributed Systems 


IMPORTANT DATES:

September 21, 2001		Paper Submission Deadline.
October   31, 2001		(Approx) Acceptance Notification.
November  21, 2001		Camera Ready Paper (Hard) Deadline.

KEYNOTE ADDRESS:

In addition to the regular technical sessions we are very pleased to 
announce that Prof. Erol Gelenbe will present the keynote address at 
CNDS 2002. Prof. Gelenbe's research interests cover intelligent
network protocols, computer performance analysis, artificial neural
networks and image processing. His recent applied work has included 
adaptive routing in the OSI protocol stack, search algorithms in
information environments, enhanced reality, and video compression. 
Please see the web site for additional information.

INSTRUCTIONS FOR AUTHORS:

**NOTICE: Due to problems experienced by many international authors in the
anonymous ftp process, authors may email their manuscripts directly to
the Program Chair: mcdonald@ece.neu.edu

Authors are requested to submit manuscripts electronically to the Program
Chair by 11:00 pm (Eastern Time) of the due date via Anonymous ftp  
directly: ftp.ece.neu.edu:/pub/conf/CNDS/2002/Submissions. Papers can
also be uploaded using the Web Site: www.ece.neu.edu/conf/CNDS/2002/.
Email is an acceptable (alternative) mechanism for submission of your
manuscripts.  Mail to: mcdonald@ece.neu.edu (Subject: CNDS Submission).

     ***The preferred electronic format is PDF***

Papers must be in English and submitted files must be in Postscript or PDF
format with all figures and tables included. Files names must be unique
and reflect the name of the primary author, his or her primary
affiliation, the version number of the file and an extension indicating
the file type. Multiple versions may be uploaded; however, only the most
recent will be reviewed. Filenames are not readable once the file transfer
has been completed. Confirmations will be sent to the contact author when
the file has been retrieved and successfully viewed or printed. Only
original unpublished material will be considered for publication.

This year's International TPC is outstanding. Its members represent a
broad spectrum of interrelated interests and technical expertise relevent
to CNDS including performance analysis, simulation, communications
networks, both wired and wireless, mobile computing, computer 
architecture, distributed systems and more. The TPC consists of newcomers
and veterans of CNDS from Universities and Research Labs around the
world. Each member is committed to ensure that all submissions are fully
refereed for accuracy, technical content, and relevance, and to make this
year's conference an exciting International forum for the presentation of
high quality work and the exchange of ideas. Papers should be limited to
20 double-spaced pages (camera-ready versions are limited to 6
single-spaced pages). Authors must include a single page which includes
all the authors' names, titles and affiliations, a paper abstract, list of
top three relevant topics and contact person information (complete
address, email, phone, and fax). Accepted papers will appear in the
Conference's Proceedings to be published by the Society for Computer
Simulation. Instructions for submitting camera ready papers will be sent
to authors following paper acceptance. An award will be presented to the
best paper presented at WMC'02. Authors of top papers will also be
encouraged to submit a follow-on paper to the International Journal in
Computer Simulation. Authors must obtain employer, client, or government
releases prior to submittal of the final manuscript.

Please do not hesitate to contact the Program Chair, Prof. McDonald via
email (mcdonald@ece.neu.edu), or telephone ((617) 373-3028) with any
questions concerning the paper submission and review process, or questions
regarding the relevance of a paper to the conference. 


   General Chair                       Program Chair 

Dr. Taieb F. Znati                 Prof. A. Bruce McDonald
Senior Program Director            Dept. of Electrical and Computer Eng.
National Science Foundation        417 Dana Research Center
ANIR and  			   Northeastern University
Computer Science Department        360 Huntington Avenue
University of Pittsburgh           Boston, MA 15221
Pittsburgh, PA 15260               U.S.A.
U.S.A.      

Phone:  +1(412)624-8417            Phone:  +1(617)328-3028
FAX:    +1(412)624-8854            FAX:    +1(617)328-8970
E_Mail: znati@cs.pitt.edu          E_Mail: mcdonald@ece.neu.edu

Please visit the conference Web Site for up-to-date information and to see
a list of the distinguished  members of the International Technical
Program Commmittee: 

	    http://www.ece.neu.edu/conf/CNDS/2002/

	      
--------------------------------------------------------
A. Bruce McDonald	f:617.373.8970
Assistant Prof.		v:617.373.3028
ECE Dept., 417 Dana     mcdonald@ece.neu.edu
360 Huntington Ave.     www.ece.neu.edu/faculty/mcdonald	
Northeastern University
Boston, MA 02115        
--------------------------------------------------------
















From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep 19 13:45:35 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07150
	for <mobileip-archive@odin.ietf.org>; Wed, 19 Sep 2001 13:45:35 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA24638;
	Wed, 19 Sep 2001 10:44:39 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id KAA00816;
	Wed, 19 Sep 2001 10:44:29 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8JHhU7B013142
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 19 Sep 2001 10:43:30 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8JHhUAf013141
	for mobile-ip-dist; Wed, 19 Sep 2001 10:43:30 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from heliopolis.eng.sun.com (redhook.Eng.Sun.COM [152.70.24.37])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8JHhR7B013134
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 19 Sep 2001 10:43:27 -0700 (PDT)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.eng.sun.com (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id KAA16728;
	Wed, 19 Sep 2001 10:43:27 -0700 (PDT)
Message-Id: <200109191743.KAA16728@heliopolis.eng.sun.com>
Date: Wed, 19 Sep 2001 10:43:27 -0700 (PDT)
From: James Kempf <James.Kempf@Sun.COM>
Subject: Re: [mobile-ip] New BETH Draft
To: mobile-ip@sunroof.eng.sun.com
Cc: gdommety@cisco.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: sVcEC95mqcsQHfpH2ugYwg==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Hi Alper,

>
>> 
>> What I am proposing is that if the old AR knows that the new AR does
>> not support FMIPv6, it sends a PrxyRtAdv with a new code indicating
>> that. This benefits *both* a BETH capable MN and one that is doing
>> standard FMIPv6. If the new AR does support FMIPv6, of course, it sends a 
>
>I think this already exists for FMIPv6. Checking the draft, code 128 of PrRtAdv 
>can be used for this case as well.
>

I had something different in mind, namely refining the notification
from "Access Point Not Known" to "Access Point Known, but Does Not
Support FMIPv6". If the MN gets an L2 trigger, it could send
a SolRtAdv right away, as described in draft-ietf-mobileip-ipv6-14.txt
pg. 80. If the MN doesn't know what the Access Point is, it needs
to wait for the RtAdv. If knows the AP, it can solicit the RtAdv. This could
result in faster CoA establishment (though, of course, not nearly
as fast as FMIPv6).

		jak




From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep 19 13:54:50 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07330
	for <mobileip-archive@odin.ietf.org>; Wed, 19 Sep 2001 13:54:49 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA29645;
	Wed, 19 Sep 2001 10:53:51 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id KAA03556;
	Wed, 19 Sep 2001 10:53:44 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8JHr07B013246
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 19 Sep 2001 10:53:00 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8JHr0ul013245
	for mobile-ip-dist; Wed, 19 Sep 2001 10:53:00 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from heliopolis.eng.sun.com (redcoast.Eng.Sun.COM [152.70.28.21])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8JHqv7B013238
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 19 Sep 2001 10:52:57 -0700 (PDT)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.eng.sun.com (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id KAA17119;
	Wed, 19 Sep 2001 10:52:57 -0700 (PDT)
Message-Id: <200109191752.KAA17119@heliopolis.eng.sun.com>
Date: Wed, 19 Sep 2001 10:52:57 -0700 (PDT)
From: James Kempf <James.Kempf@Sun.COM>
Subject: Re: [mobile-ip] New BETH Draft
To: James.Kempf@Sun.COM, mobile-ip@sunroof.eng.sun.com
Cc: mobile-ip@sunroof.eng.sun.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: WpsOjpB26T6mGNjqiZQv1A==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Hi Rajeev,

>
>it appears that we are in sync. However, I would like to see clear descriptions 
of
>
>- what are the requirements for a BETH MN
>- what are the requirements for a BETH AR
>
>in the draft, especially if it needs to be part of the FMIPv6 draft. As I 
understand,
>BETH is a very specific optimization with underlying assumptions and associated
>requirements. They need to be *clearly* specified, perhaps in an individual 
section.
>If such a thing already exists, please excuse this note.


Agree. I will make sure that they are spelled out in the merged draft.

BTW, what do you think about letting the AR tell the MN whether
it is entering a BETH coverage area? This would allow the MN to
start performing BETH optimization, just as informing it when
it is leaving the coverage area allows it to stop performing
the optimization? If the MN wasn't capable of performing the
optimization, it would simply continue to do FMIPv6 handover.

		jak



From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep 19 14:39:30 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08138
	for <mobileip-archive@lists.ietf.org>; Wed, 19 Sep 2001 14:39:29 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id MAA09307;
	Wed, 19 Sep 2001 12:38:20 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id LAA24240;
	Wed, 19 Sep 2001 11:38:20 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8JIbA7B013333
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 19 Sep 2001 11:37:10 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8JIbA53013332
	for mobile-ip-dist; Wed, 19 Sep 2001 11:37:10 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8JIb67B013325
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 19 Sep 2001 11:37:06 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id LAA23914
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 19 Sep 2001 11:37:07 -0700 (PDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id LAA06829;
	Wed, 19 Sep 2001 11:37:05 -0700 (PDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id LAA26324;
	Wed, 19 Sep 2001 11:37:05 -0700 (PDT)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f8JIb4l08809;
	Wed, 19 Sep 2001 11:37:04 -0700
X-mProtect:  Wed, 19 Sep 2001 11:37:04 -0700 Nokia Silicon Valley Messaging Protection
Received: from rajeev.iprg.nokia.com (205.226.2.90, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpdWFH5lh; Wed, 19 Sep 2001 11:37:02 PDT
Message-ID: <3BA8E5CF.AEA3E428@iprg.nokia.com>
Date: Wed, 19 Sep 2001 11:37:03 -0700
From: Rajeev Koodli <rajeev@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: mobile-ip@sunroof.eng.sun.com
CC: James.Kempf@Sun.COM
Subject: Re: [mobile-ip] New BETH Draft
References: <200109191752.KAA17119@heliopolis.eng.sun.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

James,


> BTW, what do you think about letting the AR tell the MN whether
> it is entering a BETH coverage area? This would allow the MN to
> start performing BETH optimization, just as informing it when
> it is leaving the coverage area allows it to stop performing
> the optimization? If the MN wasn't capable of performing the
> optimization, it would simply continue to do FMIPv6 handover.
>

This could be useful. I guess the AR would advertise that it supports BETH, perhaps
through solicited RtAdvs.

Regards,

-Rajeev


>
>                 jak



From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep 19 14:41:20 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08259
	for <mobileip-archive@lists.ietf.org>; Wed, 19 Sep 2001 14:41:20 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id MAA11148;
	Wed, 19 Sep 2001 12:40:20 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id LAA24961;
	Wed, 19 Sep 2001 11:40:23 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8JIdY7B013356
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 19 Sep 2001 11:39:34 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8JIdXfx013355
	for mobile-ip-dist; Wed, 19 Sep 2001 11:39:33 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from heliopolis.eng.sun.com (redcoast.Eng.Sun.COM [152.70.28.21])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8JIdU7B013348
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 19 Sep 2001 11:39:30 -0700 (PDT)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.eng.sun.com (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id LAA19060;
	Wed, 19 Sep 2001 11:39:31 -0700 (PDT)
Message-Id: <200109191839.LAA19060@heliopolis.eng.sun.com>
Date: Wed, 19 Sep 2001 11:39:30 -0700 (PDT)
From: James Kempf <James.Kempf@sun.com>
Subject: Re: [mobile-ip] New BETH Draft
To: mobile-ip@sunroof.eng.sun.com, rajeev@iprg.nokia.com
Cc: James.Kempf@sun.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: Dqbfu7GXlbMufxWMtJce7w==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

>> BTW, what do you think about letting the AR tell the MN whether
>> it is entering a BETH coverage area? This would allow the MN to
>> start performing BETH optimization, just as informing it when
>> it is leaving the coverage area allows it to stop performing
>> the optimization? If the MN wasn't capable of performing the
>> optimization, it would simply continue to do FMIPv6 handover.
>>
>
>This could be useful. I guess the AR would advertise that it supports BETH, 
perhaps
>through solicited RtAdvs.
>

Yes, that is what I had thought. 

		jak



From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep 19 16:24:08 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10296
	for <mobileip-archive@odin.ietf.org>; Wed, 19 Sep 2001 16:24:07 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA12898;
	Wed, 19 Sep 2001 13:22:49 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id NAA18537;
	Wed, 19 Sep 2001 13:22:34 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8JKKe7B013575
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 19 Sep 2001 13:20:40 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8JKKeil013574
	for mobile-ip-dist; Wed, 19 Sep 2001 13:20:40 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8JKKa7B013567
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 19 Sep 2001 13:20:36 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id NAA17824
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 19 Sep 2001 13:20:38 -0700 (PDT)
Received: from mgw-dax1.ext.nokia.com (mgw-dax1.ext.nokia.com [63.78.179.216])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id NAA14884
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 19 Sep 2001 13:20:37 -0700 (PDT)
Received: from davir01nok.americas.nokia.com (davir01nok.americas.nokia.com [172.18.242.84])
	by mgw-dax1.ext.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f8JKKd310231
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 19 Sep 2001 15:20:39 -0500 (CDT)
Received: from daebh002.NOE.Nokia.com (unverified) by davir01nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T5617769e10ac12f2540ff@davir01nok.americas.nokia.com>;
 Wed, 19 Sep 2001 15:20:37 -0500
Received: from daebe007.NOE.Nokia.com ([172.18.242.211]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.2966);
	 Wed, 19 Sep 2001 15:20:36 -0500
content-class: urn:content-classes:message
Subject: Re: [mobile-ip] New BETH Draft
Date: Wed, 19 Sep 2001 15:20:40 -0500
Message-ID: <697DAA22C5004B4596E033803A7CEF441E86D3@daebe007.NOE.Nokia.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Thread-Topic: Re: [mobile-ip] New BETH Draft
Thread-Index: AcFBSIoKZ09p8q0QEdWw3gAAhj/HZA==
x-mimeole: Produced By Microsoft Exchange V6.0.4712.0
From: "Patil Basavaraj (NET/Dallas)" <Basavaraj.Patil@nokia.com>
To: "'James kempf'" <James.Kempf@Sun.COM>
Cc: "'Mobile IP'" <mobile-ip@sunroof.eng.sun.com>
X-OriginalArrivalTime: 19 Sep 2001 20:20:36.0694 (UTC) FILETIME=[8AE72760:01C14148]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by sunroof.eng.sun.com id f8JKKa7B013568
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 8bit

James,

Here's a scenario on HOs that I would like to get your opinion on what
happens w.r.t BETH:

BETH is a network initiated HO and as such the MN is kept in the dark
about the change in AR. Once a HO decision has been made the oAR
creates a Bi-directional tunnel between the oAR and the nAR. The MN is
not consulted at all. 
There may be scenarios where the MN may be capable of handing off to
another network (via another i/f). The oAR that the MN is currently
attached to is not aware of this network/AR as it may not be in its
configuration or neighbor list. There may be a possibility that the
network may be in the process of performing a BET HO while the MN may
initiate a Mobile originated HO. While this may be considered to be a
race condition or a special case, the fast HO I-D should specify the
precedence that would exist in such cases. In this case I would think
that the BET HO would be abandoned and the Mobile originated HO
request would take prerogative.

Comments,

-Basavaraj



From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep 19 16:34:51 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10542
	for <mobileip-archive@lists.ietf.org>; Wed, 19 Sep 2001 16:34:50 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id OAA13828;
	Wed, 19 Sep 2001 14:33:36 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id NAA21175;
	Wed, 19 Sep 2001 13:33:35 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8JKWU7B013639
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 19 Sep 2001 13:32:30 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8JKWUnq013638
	for mobile-ip-dist; Wed, 19 Sep 2001 13:32:30 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8JKWQ7B013631
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 19 Sep 2001 13:32:26 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id NAA24281
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 19 Sep 2001 13:32:27 -0700 (PDT)
Received: from mgw-dax1.ext.nokia.com (mgw-dax1.ext.nokia.com [63.78.179.216])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id NAA06472
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 19 Sep 2001 13:32:26 -0700 (PDT)
Received: from davir03nok.americas.nokia.com (davir03nok.americas.nokia.com [172.18.242.86])
	by mgw-dax1.ext.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f8JKWR311498
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 19 Sep 2001 15:32:27 -0500 (CDT)
Received: from daebh002.NOE.Nokia.com (unverified) by davir03nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T5617816d21ac12f256126@davir03nok.americas.nokia.com>;
 Wed, 19 Sep 2001 15:32:25 -0500
Received: from daebe007.NOE.Nokia.com ([172.18.242.211]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.2966);
	 Wed, 19 Sep 2001 15:32:25 -0500
content-class: urn:content-classes:message
Subject: RE: [mobile-ip] New BETH Draft
Date: Wed, 19 Sep 2001 15:32:28 -0500
Message-ID: <697DAA22C5004B4596E033803A7CEF441E86D4@daebe007.NOE.Nokia.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Thread-Topic: [mobile-ip] New BETH Draft
Thread-Index: AcFBOoECrFWYca0sEdWxLgAIx6TWeAAD5fxw
x-mimeole: Produced By Microsoft Exchange V6.0.4712.0
From: "Patil Basavaraj (NET/Dallas)" <Basavaraj.Patil@nokia.com>
To: <mobile-ip@sunroof.eng.sun.com>
Cc: <James.Kempf@Sun.COM>, <rajeev@iprg.nokia.com>
X-OriginalArrivalTime: 19 Sep 2001 20:32:25.0225 (UTC) FILETIME=[31386790:01C1414A]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by sunroof.eng.sun.com id f8JKWQ7B013632
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 8bit

>James,
>
>> BTW, what do you think about letting the AR tell the MN whether
>> it is entering a BETH coverage area? This would allow the MN to
>> start performing BETH optimization, just as informing it when
>> it is leaving the coverage area allows it to stop performing
>> the optimization? If the MN wasn't capable of performing the
>> optimization, it would simply continue to do FMIPv6 handover.
>>
>
>This could be useful. I guess the AR would advertise that it supports
>BETH, perhaps through solicited RtAdvs.
>

Any reason why solicited RtrAdvts and not the reguar rtradvts?

Would you advertise that the network you are in supports Fast HO  (as
per FMIPv6) or only indicate that the network supports BETH? The MN
may not really know if a BETH HO was initiated or was succesful. So
even if you indicated via the rtr-advt that it was in a BETH capable
domain, you may still want to allow the MN to go ahead with a
RtrSolicit if it gets L2 triggers about changes in AP. Maybe there
needs to be a way of damping the RtrSolicit (in the network) if a BETH
HO has already been done succesfully or is in the process? I just do
not think you should change the MNs behavior of reacting to L2
triggers (movement detection) just because it is in a BETH capable
domain. 

>Regards,
>
>-Rajeev
>
>>
>>                 jak

-Basavaraj



From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep 19 16:45:58 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10697
	for <mobileip-archive@lists.ietf.org>; Wed, 19 Sep 2001 16:45:57 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id OAA22968;
	Wed, 19 Sep 2001 14:44:52 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id NAA24755;
	Wed, 19 Sep 2001 13:44:52 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8JKhc7B013715
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 19 Sep 2001 13:43:38 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8JKhc6I013714
	for mobile-ip-dist; Wed, 19 Sep 2001 13:43:38 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from eastmail2.East.Sun.COM (eastmail2.East.Sun.COM [129.148.1.241])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8JKhV7B013707
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 19 Sep 2001 13:43:32 -0700 (PDT)
Received: from onion.east.sun.com (onion.East.Sun.COM [129.148.174.110])
	by eastmail2.East.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id QAA20357
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 19 Sep 2001 16:43:33 -0400 (EDT)
Received: (from glass@localhost)
	by onion.east.sun.com (8.9.3+Sun/8.9.3) id QAA24761
	for mobile-ip@sunroof.eng.sun.com; Wed, 19 Sep 2001 16:44:03 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8JJqC7B013511
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 19 Sep 2001 12:52:12 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id MAA07956
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 19 Sep 2001 12:52:14 -0700 (PDT)
Received: from netmail.alcatel.com (netmail.alcatel.com [128.251.168.50])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id MAA00260
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 19 Sep 2001 12:52:10 -0700 (PDT)
Received: from auds951.usa.alcatel.com (auds951.usa.alcatel.com [143.209.238.80])
	by netmail.alcatel.com (8.9.1/8.9.1) with ESMTP id OAA00796
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 19 Sep 2001 14:52:09 -0500 (CDT)
Received: from alcatel.com (localhost [127.0.0.1])
	by auds951.usa.alcatel.com (8.10.2/8.10.2) with ESMTP id f8JJq9e00681
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 19 Sep 2001 14:52:09 -0500 (CDT)
Message-ID: <3BA911F0.4C53C77E@alcatel.com>
Date: Wed, 19 Sep 2001 14:45:20 -0700
From: Xiaofeng Xu <xiaofeng.xu@alcatel.com>
X-Mailer: Mozilla 4.75 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] How many MNs connected to a HA?
References: <39022001931913334732@kth.se>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

I would say that in the range of  500 (enterprise network) ~500,000 (carrier
network).

Babak Ayani wrote:

> Hi
> Sorry if this question sounds stupid but I haven't been able to find any
> information about this.
> I'm doing my Ms thesis about handoffs in Mobile IP and I'm trying to
> calculate an approximate handoff time
> when having a buffer at the HA. In order to be able to do this, I need to
> know approximately how many MNs that usually are connected to
> one HA (is it 5, 10, 50, 100 or more?).
> Is it possible that only one MN is connected to a HA?
> Thanks for your help in advance.
>
> Babak



From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep 19 18:31:12 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA11913
	for <mobileip-archive@lists.ietf.org>; Wed, 19 Sep 2001 18:31:11 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id QAA13773;
	Wed, 19 Sep 2001 16:30:13 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id PAA07696;
	Wed, 19 Sep 2001 15:30:13 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8JMTE7B013926
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 19 Sep 2001 15:29:14 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8JMTDth013925
	for mobile-ip-dist; Wed, 19 Sep 2001 15:29:13 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from heliopolis.eng.sun.com (redcoast.Eng.Sun.COM [152.70.28.21])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8JMTA7B013918
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 19 Sep 2001 15:29:10 -0700 (PDT)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.eng.sun.com (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id PAA29794;
	Wed, 19 Sep 2001 15:29:10 -0700 (PDT)
Message-Id: <200109192229.PAA29794@heliopolis.eng.sun.com>
Date: Wed, 19 Sep 2001 15:29:10 -0700 (PDT)
From: James Kempf <James.Kempf@sun.com>
Subject: Re: [mobile-ip] New BETH Draft
To: James.Kempf@sun.com, Basavaraj.Patil@nokia.com
Cc: mobile-ip@sunroof.eng.sun.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: 5zMCDYsXRnfUgWGluYpjCA==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Hi Raj,

>
>Here's a scenario on HOs that I would like to get your opinion on what
>happens w.r.t BETH:
>
>BETH is a network initiated HO and as such the MN is kept in the dark
>about the change in AR. Once a HO decision has been made the oAR
>creates a Bi-directional tunnel between the oAR and the nAR. The MN is
>not consulted at all. 
>There may be scenarios where the MN may be capable of handing off to
>another network (via another i/f). The oAR that the MN is currently
>attached to is not aware of this network/AR as it may not be in its
>configuration or neighbor list. There may be a possibility that the
>network may be in the process of performing a BET HO while the MN may
>initiate a Mobile originated HO. While this may be considered to be a
>race condition or a special case, the fast HO I-D should specify the
>precedence that would exist in such cases. In this case I would think
>that the BET HO would be abandoned and the Mobile originated HO
>request would take prerogative.
>

I agree.

Specifically, when the MN decides to hand over to another interface,
it issues a SolPrxyRtAdv to the AR that is handling the active interface,
requesting handover to the AR handling the new interface. Upon
receipt of the SolPrxyRtAdv, the current AR proceeds to do
an FMIPv6 handoff to the new AR, issuing a standard FMIPv6 HI/HACK, and
sending the PrxyRtAdv to the MN. Upon receipt of the PrxyRtAdv, the
MN proceeds to configure its IP stack so that the home address is
on the new interface, then it does F-BU and F-NA, just like standard
FMIPv6, but now on the new interface. 

This procedure is exactly the same as for an FMIPv6 handover. The difference
w.r.t. BETH is that the old AR terminates the bidirectional tunnel
upon receipt of the F-BU. In additon, the procedure for a MN doing BETH would
be exactly the same should it handover to an AR that was not
BETH capable on the same interface, except in that case, the current AR would 
signal the MN to do FMIPv6 handover by sending it a PrxyRtAdv, rather
than having the MN signal it by doing the SolPrxyRtAdv.

I don't believe this case is mentioned in the spec,  but I can
add it.

		jak



From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep 19 19:00:39 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA12171
	for <mobileip-archive@lists.ietf.org>; Wed, 19 Sep 2001 19:00:38 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id QAA03689;
	Wed, 19 Sep 2001 16:59:39 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id PAA13975;
	Wed, 19 Sep 2001 15:59:43 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8JMwl7B014009
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 19 Sep 2001 15:58:47 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8JMwlKc014008
	for mobile-ip-dist; Wed, 19 Sep 2001 15:58:47 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8JMwh7B014001
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 19 Sep 2001 15:58:43 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id PAA00065
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 19 Sep 2001 15:58:44 -0700 (PDT)
Received: from mgw-dax1.ext.nokia.com (mgw-dax1.ext.nokia.com [63.78.179.216])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id QAA09958
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 19 Sep 2001 16:59:32 -0600 (MDT)
Received: from davir03nok.americas.nokia.com (davir03nok.americas.nokia.com [172.18.242.86])
	by mgw-dax1.ext.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f8JMwj324975
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 19 Sep 2001 17:58:45 -0500 (CDT)
Received: from daebh001.NOE.Nokia.com (unverified) by davir03nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T5618075ccbac12f256126@davir03nok.americas.nokia.com>;
 Wed, 19 Sep 2001 17:58:43 -0500
Received: from daebe007.NOE.Nokia.com ([172.18.242.211]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.2966);
	 Wed, 19 Sep 2001 17:58:42 -0500
content-class: urn:content-classes:message
Subject: RE: [mobile-ip] New BETH Draft
Date: Wed, 19 Sep 2001 17:58:42 -0500
Message-ID: <697DAA22C5004B4596E033803A7CEF441E86DD@daebe007.NOE.Nokia.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Thread-Topic: [mobile-ip] New BETH Draft
Thread-Index: AcFBWoMQWr1pg61MEdWBSwBQi2X+DwABA54w
x-mimeole: Produced By Microsoft Exchange V6.0.4712.0
From: "Patil Basavaraj (NET/Dallas)" <Basavaraj.Patil@nokia.com>
To: "'James Kempf'" <James.Kempf@sun.com>
Cc: <mobile-ip@sunroof.eng.sun.com>
X-OriginalArrivalTime: 19 Sep 2001 22:58:42.0658 (UTC) FILETIME=[A0FA6420:01C1415E]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by sunroof.eng.sun.com id f8JMwi7B014002
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 8bit

James,

>
>Hi Raj,
>
>>
>>Here's a scenario on HOs that I would like to get your opinion on what
>>happens w.r.t BETH:
>>
>>BETH is a network initiated HO and as such the MN is kept in the dark
>>about the change in AR. Once a HO decision has been made the oAR
>>creates a Bi-directional tunnel between the oAR and the nAR. The MN is
>>not consulted at all. 
>>There may be scenarios where the MN may be capable of handing off to
>>another network (via another i/f). The oAR that the MN is currently
>>attached to is not aware of this network/AR as it may not be in its
>>configuration or neighbor list. There may be a possibility that the
>>network may be in the process of performing a BET HO while the MN may
>>initiate a Mobile originated HO. While this may be considered to be a
>>race condition or a special case, the fast HO I-D should specify the
>>precedence that would exist in such cases. In this case I would think
>>that the BET HO would be abandoned and the Mobile originated HO
>>request would take prerogative.
>>
>
>I agree.
>
>Specifically, when the MN decides to hand over to another interface,
>it issues a SolPrxyRtAdv to the AR that is handling the active
interface,
>requesting handover to the AR handling the new interface. Upon
>receipt of the SolPrxyRtAdv, the current AR proceeds to do
>an FMIPv6 handoff to the new AR, issuing a standard FMIPv6 HI/HACK, and
>sending the PrxyRtAdv to the MN. Upon receipt of the PrxyRtAdv, the
>MN proceeds to configure its IP stack so that the home address is
>on the new interface, then it does F-BU and F-NA, just like standard
>FMIPv6, but now on the new interface. 
>
>This procedure is exactly the same as for an FMIPv6 handover. The
difference
>w.r.t. BETH is that the old AR terminates the bidirectional tunnel
>upon receipt of the F-BU. In additon, the procedure for a MN doing BETH
would
>be exactly the same should it handover to an AR that was not
>BETH capable on the same interface, except in that case, the current AR
would 
>signal the MN to do FMIPv6 handover by sending it a PrxyRtAdv, rather
>than having the MN signal it by doing the SolPrxyRtAdv.
>
>I don't believe this case is mentioned in the spec,  but I can
>add it.

Thanks. That would be good. Just for clarification (in BETH) , I guess
the time at which you start forwarding packets to the MN via the
tunnel to the new AR is at the time when you get an L2 indication that
the MN is no longer connected to the AP. I may have to reread the BETH
spec to ensure that is the case.

>		jak
>

-Basavaraj



From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep 19 19:05:44 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA12301
	for <mobileip-archive@lists.ietf.org>; Wed, 19 Sep 2001 19:05:44 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id RAA07043;
	Wed, 19 Sep 2001 17:04:45 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id QAA15423;
	Wed, 19 Sep 2001 16:04:47 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8JN467B014086
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 19 Sep 2001 16:04:06 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8JN46Sf014085
	for mobile-ip-dist; Wed, 19 Sep 2001 16:04:06 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8JN427B014078
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 19 Sep 2001 16:04:02 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id QAA27614
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 19 Sep 2001 16:04:03 -0700 (PDT)
Received: from telecom.samsung.co.kr ([165.213.221.4])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id QAA22020
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 19 Sep 2001 16:04:01 -0700 (PDT)
Received: from cychong (a22416 [165.213.224.16])
	by telecom.samsung.co.kr (8.11.6/8.11.6) with SMTP id f8JN3qP24316
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 20 Sep 2001 08:03:53 +0900 (KST)
Message-ID: <000801c14160$3ee27960$10e0d5a5@cychong>
From: "Chae-yong Chong" <cychong@metro.telecom.samsung.co.kr>
To: <mobile-ip@sunroof.eng.sun.com>
References: <39022001931913334732@kth.se>
Subject: Re: [mobile-ip] How many MNs connected to a HA?
Date: Thu, 20 Sep 2001 08:10:16 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by sunroof.eng.sun.com id f8JN427B014079
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 8bit

Of course, it depends on the capacitiy of HA :-)
How about look up the product sheet of HA(CISCO, 3com ...)

Chae-yong

----- Original Message ----- 
From: "Babak Ayani" <babakay@kth.se>
To: <mobile-ip@sunroof.eng.sun.com>
Sent: Wednesday, September 19, 2001 10:33 PM
Subject: [mobile-ip] How many MNs connected to a HA?


> Hi
> Sorry if this question sounds stupid but I haven't been able to find any
> information about this.
> I'm doing my Ms thesis about handoffs in Mobile IP and I'm trying to
> calculate an approximate handoff time 
> when having a buffer at the HA. In order to be able to do this, I need to
> know approximately how many MNs that usually are connected to 
> one HA (is it 5, 10, 50, 100 or more?).
> Is it possible that only one MN is connected to a HA?
> Thanks for your help in advance.
> 
> Babak
> 
> 


From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep 19 19:15:17 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA12423
	for <mobileip-archive@lists.ietf.org>; Wed, 19 Sep 2001 19:15:15 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id RAA13400;
	Wed, 19 Sep 2001 17:14:11 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id QAA29694;
	Wed, 19 Sep 2001 16:14:13 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8JNDK7B014156
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 19 Sep 2001 16:13:20 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8JNDKwk014155
	for mobile-ip-dist; Wed, 19 Sep 2001 16:13:20 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from heliopolis.eng.sun.com (heliopolis.Eng.Sun.COM [152.70.1.39])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8JNDH7B014148
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 19 Sep 2001 16:13:17 -0700 (PDT)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.eng.sun.com (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id QAA02467;
	Wed, 19 Sep 2001 16:13:18 -0700 (PDT)
Message-Id: <200109192313.QAA02467@heliopolis.eng.sun.com>
Date: Wed, 19 Sep 2001 16:13:18 -0700 (PDT)
From: James Kempf <James.Kempf@Sun.COM>
Subject: RE: [mobile-ip] New BETH Draft
To: mobile-ip@sunroof.eng.sun.com, Basavaraj.Patil@nokia.com
Cc: James.Kempf@Sun.COM, rajeev@iprg.nokia.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: p8TVASeq5v+9tWjZEjqoGA==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Hi Raj,


>Any reason why solicited RtrAdvts and not the reguar rtradvts?
>

Good point.

There's a bootstrapping issue here w.r.t. FMIPv6
in general. Suppose an MN is capable of doing mobile initiated
FMIPv6 handover, it comes up in a network, gets a RtAdv for its initial
AR. How does it know that it can issue a SolPrxyRtAdv when it
gets a trigger saying it is about to be handed over? Should it
just issue one, and, if the current AR doesn't respond, assume that
it can't do FMIPv6 handover in this coverage area? Obviously, if the handover is 
network initiated, the MN will receive a PrxyRtAdv and then it knows it can do 
an FMIPv6 handover if it is capable. If not, it will simply
ignore the PrxyRtAdv. Similarly, if the MN moves out of an FMIPv6
coverage area and back again, how does it know when it can restart
doing FMIPv6 handover?

A similar consideration holds for BETH. The MN may come up in a 
network that is BETH capable, it needs to know it can suppress
MIPv6 handover signalling if it's traffic pattern suggests to.
The MN may be handed over into a coverage area lacking BETH
support, then handed over again to a coverage area in which
BETH is supported. 

>Would you advertise that the network you are in supports Fast HO  (as
>per FMIPv6) or only indicate that the network supports BETH? The MN
>may not really know if a BETH HO was initiated or was succesful. So
>even if you indicated via the rtr-advt that it was in a BETH capable
>domain, you may still want to allow the MN to go ahead with a
>RtrSolicit if it gets L2 triggers about changes in AP. Maybe there
>needs to be a way of damping the RtrSolicit (in the network) if a BETH
>HO has already been done succesfully or is in the process? I just do
>not think you should change the MNs behavior of reacting to L2
>triggers (movement detection) just because it is in a BETH capable
>domain. 
>

I think we need to advertise both BETH and FMIPv6. The MN has to know what the
capabilities are. I think there are basically two cases:

1) The MN comes up in the network and aquires an initial AR via SolRtAdv
or an unsolicited RtAdv from the AR. Or the MN moves into
a coverage area where FMIPv6 is not supported and it starts doing
standard MIPv6 handover, then it moves into an FMIPv6/BETH coverage
area again.

2) The MN is in an FMIPv6/BETH coverage area and the current AR
knows that it is about to be handed over into a coverage area
where the ARs support more or fewer handover possibilities, so
the current AR can signal the MN via the PrxyRtAdv.

I think 1) can be handled by indicating the handover capabilities
in the RtAdv, and 2) can be handled by indicating them in the PrxyRtAdv.

		jak



From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep 19 19:16:00 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA12445
	for <mobileip-archive@lists.ietf.org>; Wed, 19 Sep 2001 19:16:00 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id RAA14043;
	Wed, 19 Sep 2001 17:15:00 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id QAA29959;
	Wed, 19 Sep 2001 16:15:01 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8JNEF7B014173
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 19 Sep 2001 16:14:15 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8JNEEa5014172
	for mobile-ip-dist; Wed, 19 Sep 2001 16:14:14 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from heliopolis.eng.sun.com (bigbang.Eng.Sun.COM [152.70.8.30])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8JNEA7B014165
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 19 Sep 2001 16:14:10 -0700 (PDT)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.eng.sun.com (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id QAA02519;
	Wed, 19 Sep 2001 16:14:11 -0700 (PDT)
Message-Id: <200109192314.QAA02519@heliopolis.eng.sun.com>
Date: Wed, 19 Sep 2001 16:14:11 -0700 (PDT)
From: James Kempf <James.Kempf@sun.com>
Subject: RE: [mobile-ip] New BETH Draft
To: James.Kempf@sun.com, Basavaraj.Patil@nokia.com
Cc: mobile-ip@sunroof.eng.sun.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: A7OEfO53avEKAMvLmIzWXQ==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Hi Raj,


>Thanks. That would be good. Just for clarification (in BETH) , I guess
>the time at which you start forwarding packets to the MN via the
>tunnel to the new AR is at the time when you get an L2 indication that
>the MN is no longer connected to the AP. I may have to reread the BETH
>spec to ensure that is the case.
>

Yes, that's the case. Please let me know if it is unclear.

		jak



From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep 19 21:04:47 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA13236
	for <mobileip-archive@lists.ietf.org>; Wed, 19 Sep 2001 21:04:47 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id TAA11852;
	Wed, 19 Sep 2001 19:03:51 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id SAA28709;
	Wed, 19 Sep 2001 18:03:51 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8K12N7B014528
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 19 Sep 2001 18:02:23 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8K12Na8014527
	for mobile-ip-dist; Wed, 19 Sep 2001 18:02:23 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8K12G7B014512;
	Wed, 19 Sep 2001 18:02:16 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id SAA28376;
	Wed, 19 Sep 2001 18:02:18 -0700 (PDT)
From: paalee@telenorisv.com
Received: from fep2.mta.online.no (lionmta2.online.no [148.122.208.25])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id SAA09892;
	Wed, 19 Sep 2001 18:02:17 -0700 (PDT)
Received: from [10.122.209.34] by fep2.mta.online.no
          (InterMail vM.4.01.03.23 201-229-121-123-20010418) with ESMTP
          id <20010920010215.TEWE392.fep2.mta.online.no@[10.122.209.34]>;
          Thu, 20 Sep 2001 03:02:15 +0200
To: G.Tsirtsis@flarion.com, gtsirt@hotmail.com, sltsao@itri.org.tw
CC: ipng@sunroof.eng.sun.com, ngtrans@sunroof.eng.sun.com,
        mobile-ip@sunroof.eng.sun.com
Subject: Fwd: [mobile-ip] IPv6 over Mobile IPv4
Date: Thu, 20 Sep 2001 3:02:43 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Message-Id: <20010920010215.TEWE392.fep2.mta.online.no@[10.122.209.34]>
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

(Sorry if you have received a duplicate of this message - I had some problems with my e-mail.)

George and Charles,

FYI, the Internet Draft 
http://search.ietf.org/internet-drafts/draft-mccann-mobileip-ipv6mipv4-00.txt 
was recently submitted and announced on the Mobile IP mailing list. 

While we are waiting for the security-issues of MIPv6 to be resolved, I find the proposed solution promising. It provides a mechanism for IPv6 mobility that also incorporates AAA functionality. In the long run, the proposed idea can be relevant for IPv4 to IPv6 transition.

Their mechanism might be useful to your "Dual Stack Moving" efforts. It is definitely related to my own Dual Stack Mobile IP draft, which I plan to rewrite, simplify and adapt to their proposal.

Earlier, we have talked about a framework for dual stack mobility. Perhaps their draft could be a good starting point for that discussion? 

-- Paal

---------------------------------------------------------------------



>From: Pete McCann <mccap@lucent.com>
>Reply-To: mobile-ip@sunroof.eng.sun.com
>To: mobile-ip@sunroof.eng.sun.com
>CC: pcalhoun@diameter.org, tom.hiller@lucent.com
>Subject: [mobile-ip] IPv6 over Mobile IPv4
>Date: Thu, 13 Sep 2001 17:39:15 -0500
>
>Hi,
>
>We (Pat Calhoun, Tom Hiller, and myself) recently wrote a draft
>describing a method for running IPv6 traffic while using Mobile IPv4
>signaling for mobility management and security. We submitted it today
>to internet-drafts; you can find an advance copy at:
>
>http://www.diameter.org/draft-mccann-mobileip-ipv6mipv4-00.txt
>
>Basically, this could serve as an interim solution while we wait for
>all of the Mobile IPv6 security work to converge. It would allow us
>to use the existing Mobile IPv4 security model, including AAA, for
>securing registration requests, while providing IPv6 service to
>dual-stack mobile nodes. It may also help ease the overall transition
>to IPv6 because it only requires IPv6 support in the MN, FA, HA, and
>home network, while the network between the FA and HA could be a
>legacy IPv4 cloud.
>
>The draft itself is fairly straightforward; we would appreciate
>comments on the list and would like to see if there is interest in
>making this a working group item.
>
>-Pete




From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep 20 10:03:23 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10667
	for <mobileip-archive@odin.ietf.org>; Thu, 20 Sep 2001 10:03:23 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id IAA10202;
	Thu, 20 Sep 2001 08:02:27 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id HAA19372;
	Thu, 20 Sep 2001 07:02:28 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8KE1S7B015426
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 20 Sep 2001 07:01:28 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8KE1RF5015425
	for mobile-ip-dist; Thu, 20 Sep 2001 07:01:27 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8KE1N7B015418
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 20 Sep 2001 07:01:23 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id HAA28655
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 20 Sep 2001 07:01:21 -0700 (PDT)
Received: from muminmamman.lifix.fi ([195.238.204.197])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id IAA09404
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 20 Sep 2001 08:01:09 -0600 (MDT)
Received: from ban by muminmamman.lifix.fi with local (Exim 3.12 #1 (Debian))
	id 15k4OF-0006X9-00
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 20 Sep 2001 17:01:19 +0300
Date: Thu, 20 Sep 2001 17:01:19 +0300
From: Bjorn Andersson <bjorn@lifix.fi>
To: mobile-ip@sunroof.eng.sun.com
Subject: [mobile-ip] Mobile-Home Auth. Ext. requirement in RFC2002bis
Message-ID: <20010920170119.A24154@lifix.fi>
Mail-Followup-To: Bjorn Andersson <bjorn@lifix.fi>,
	mobile-ip@sunroof.eng.sun.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.20i
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Section 3.5.2, "Mobile-Home Authentication Extension", in
draft-ietf-mobileip-rfc2002-bis-08.txt states that "exactly one
authorization-enabling extension MUST be present in all Registration
Requests".

However, in various AAA scenarios as discussed in other RFCs and IDs,
this requirement cannot be fulfilled since the MN might only have
an SA with AAA infrastructure, and not (yet) with the Home Agent.
I suggest that the above section should be clarified, and require
that the MH auth ext only has to be present if no other home
network authentication extension is present (such as the MN-AAA
authentication extension).

Regards,
Bjorn Andersson

-- 
Bjorn Andersson <bjorn@lifix.fi>                       +358 50 341 2556
Lifix Systems Oy <http://www.lifix.fi/>                 PGP id 5AFC144B
Yliopistonkatu 5, 3rd floor; FIN-00100 Helsinki


From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep 20 10:48:52 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12270
	for <mobileip-archive@odin.ietf.org>; Thu, 20 Sep 2001 10:48:51 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id HAA02695;
	Thu, 20 Sep 2001 07:48:04 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id HAA18194;
	Thu, 20 Sep 2001 07:47:51 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8KEkx7B015579
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 20 Sep 2001 07:46:59 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8KEkxjD015578
	for mobile-ip-dist; Thu, 20 Sep 2001 07:46:59 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8KEku7B015571
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 20 Sep 2001 07:46:56 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id HAA01437
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 20 Sep 2001 07:46:57 -0700 (PDT)
Received: from motgate4.mot.com (motgate4.mot.com [144.189.100.102])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id HAA23169
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 20 Sep 2001 07:46:56 -0700 (PDT)
Received: [from pobox.mot.com (pobox.mot.com [129.188.137.100]) by motgate4.mot.com (motgate4 2.1) with ESMTP id HAA13368 for <mobile-ip@sunroof.eng.sun.com>; Thu, 20 Sep 2001 07:46:55 -0700 (MST)]
Received: [from il27exm07.cig.mot.com (IL27EXM07.cig.mot.com [136.182.15.116]) by pobox.mot.com (MOT-pobox 2.0) with ESMTP id HAA05641 for <mobile-ip@sunroof.eng.sun.com>; Thu, 20 Sep 2001 07:46:55 -0700 (MST)]
Received: by IL27EXM07.cig.mot.com with Internet Mail Service (5.5.2654.52)
	id <RPK64AXY>; Thu, 20 Sep 2001 09:46:55 -0500
Message-ID: <A5B4C9A2AD89D411AB3E009027B0DA1E3B2118@IL27EXM09.cig.mot.com>
From: Singh Ajoy-ASINGH1 <ASINGH1@motorola.com>
To: "'mobile-ip@sunroof.eng.sun.com'" <mobile-ip@sunroof.eng.sun.com>
Subject: RE: [mobile-ip] New BETH Draft
Date: Thu, 20 Sep 2001 09:46:54 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2654.52)
Content-Type: text/plain
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Hello Rajeev:
Thanx for reply. Please find my inline reply/clarfication.
regards,
ajoy 

-----Original Message-----
From: Rajeev Koodli [mailto:rajeev@iprg.nokia.com]
Sent: Tuesday, September 18, 2001 6:18 PM
To: mobile-ip@sunroof.eng.sun.com
Cc: James Kempf
Subject: Re: [mobile-ip] New BETH Draft


Hello Ajoy,

Singh Ajoy-ASINGH1 wrote:

> Hello Rajeev/James/Alper:
> Sorry for jumping in the middle.
> Please find my inline response.
> regards,
> ajoy
>
> -----Original Message-----
> From: Rajeev Koodli [mailto:rajeev@iprg.nokia.com]
> Sent: Friday, September 14, 2001 7:34 PM
> To: James Kempf
> Cc: mobile-ip@sunroof.eng.sun.com
> Subject: Re: [mobile-ip] New BETH Draft
>
> Hello James,
>
> I am seeking some clarifications below (at the end) regarding when a MN
sends
> RtSol and what does it do with RtAdv on the new AR. Your responses are
> appreciated. I also have some comments below.
>
> Regards,
>
> -Rajeev
>
> James Kempf wrote:
>
> >
> > If the MN is doing BETH and it moves to a router where there is no
> > BETH, the MN may be delaying L3 handover and so it will wait for
> > the RtADv. If the old AR can tell it beforehand that it will move
> > to a new AR without BETH, the MN can begin FMIPv6 handover (if
> > the new AR supports FMIPv6) or it can know to stop doing BETH
> > and do RtSol on the new router.
>
> I guess my point was there is no reason for the MN to wait for RtAdv in
any
> case. For instance, the Linux IPv6 MN that we have has the hook to send
out a
> RtSol as soon as an interface becomes enabled (i.e., when the MN undergoes
> AP handover). One could call this type of a hook an L2 trigger and that is
> implementation-specific.
>
> ajoy-> I do not think the example of Linux Mobile/IP is appropriate here.
> I do not think if Linux does some way, we should write the spec according
to
> that. Here we are talking about enabling Voice over IP for wireless user,
> which will require different treatment from the way Mobile/IP was
> implemented for purely non-real time data traffic.
>

Well, going by your own argument, writing a spec based on your favorite
application is also not
appropriate, I guess.. The point of bringing up the example above was a
*link-layer* trigger could
be implemented, potentially in any civilized OS, to solicit router
advertisements.

ajoy-> Rajeev, we are not writing the spec based upon our favorite
application. We are trying 
to write spec which should also be implementatble in bandwidth constraint 
network. Currently there are more wireless networks which are limited by RF
bandwidth
than otherwise.  

>
> > That is for a particular implementation which happens to be common
> > right now for a particular radio protocol. It is by no means the
> > common to all radio protocols, and even in the protocol for
> > which it is currently common, it is likely to change.
> >
>
> Well, the other scenario you are referring to is not common either, right
? In
> fact, I would argue that having an integrated AR-AP device would be a
special
> case for which we have limited experience currently. Today, both WLAN and
> cellular have this model: there is a separate link between the AP and an
AR.
> I would guess that such a model would continue to exist.
>
> -> I do not think getting link layer trigger at AR is difficult in case of
> existing cellular network. In fact such work is in progress in
> 3GPP2. I am positive this can be done in 3GPP,
> provided 3GPP decides to use Mobile/IP.
>

Ok. What do you have to say about the link between the AP and the AR ? What
link type is used there
? If I choose to use Ethernet, I have to figure out how to send a trigger to
the AR in response to
the trigger from the MN, right ?

ajoy: The Ethernet may be used as transport, but AP and AR uses some
tunneling mechanism. The tunnel
setup/teardown can be used a trigger at the AR. 

>
> >
> > The MN would only be required to send a RtSol if it had been informed
> > ahead of time on the old AR that it was moving out of a BETH
> > coverage area. This is why I proposed adding a code to the PrxyRtAdv,
> > so that the old AR could do this. Otherwise, the optimization
> > of BETH provided by lack of any L3 MIP signaling would be invalidated.
>
> So, it is requirement for the MN *not* to send a RtSol if it was moving
into a
> BETH router then ? For this to happen, the MN must be informed a priori by
old
> AR that the MN is moving into a BETH router as you point out. That means
> sending ProxyRtAdv with appropriate code is a necessity for BETH ? If yes,
this
> is not a corner case anymore.
>
> -> I think this is a corner case. Could you please provide any realistic
example where
> MN can move from BETH capable AR to nonBETH capable AR in same technology
? I am having hard time
> to imagine any scenario where we need seamless handover from one AR to
other without
> any prior agreement between neighboring ARS. Please note that this
argument can be
> made for any access protocol. For example, please find a few:
>

The point here is that the MN needs to know what type of an AR it is moving
into. Even if you have
the same technology on the two routers, does that constitute a binding
requirement that the target
AR is also a BETH AR ? What if it belongs to a different operator ?
Furthermore, after being
informed about the target AR, the MN has to abstain from sending out Router
Solicitations as soon as
the new link is established. This is a requirement on the MNs to implement.

ajoy: I agree. Sometime it is possible to have different mobility protocols
deployed in
same technology. 

My point if some technology decides to deploy BETH, it is likely that they
are doing that 
to save over the air L3 message during handover. 
I don't have any problem with optimizations. Their implications, however,
have to be clearly defined
and made known.

ajoy: OK. Hopefully, your concerns are already addressed by James's proposed
change to BETH. 

Regards,

-Rajeev


>
> What happens when MN moves from AR which supports PPP to the
> AR which does not support PPP ? What happens if PPP unaware MN
> tries to connect to non-PPP aware AR ? ....
>
> Regards,
>
> -Rajeev
>
> >
> >
> >                 jak


From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep 20 12:47:05 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15477
	for <mobileip-archive@odin.ietf.org>; Thu, 20 Sep 2001 12:47:05 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id KAA08777;
	Thu, 20 Sep 2001 10:46:08 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA10905;
	Thu, 20 Sep 2001 09:46:04 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8KGij7B015847
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 20 Sep 2001 09:44:45 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8KGijAZ015846
	for mobile-ip-dist; Thu, 20 Sep 2001 09:44:45 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from eastmail2.East.Sun.COM (eastmail2.East.Sun.COM [129.148.1.241])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8KGih7B015839
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 20 Sep 2001 09:44:43 -0700 (PDT)
Received: from onion.east.sun.com (onion.East.Sun.COM [129.148.174.110])
	by eastmail2.East.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id MAA13343
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 20 Sep 2001 12:44:34 -0400 (EDT)
Received: (from glass@localhost)
	by onion.east.sun.com (8.9.3+Sun/8.9.3) id MAA17895
	for mobile-ip@sunroof.eng.sun.com; Thu, 20 Sep 2001 12:45:03 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8K0Y77B014371;
	Wed, 19 Sep 2001 17:34:07 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id RAA17435;
	Wed, 19 Sep 2001 17:34:10 -0700 (PDT)
From: tisv@telenorisv.com
Received: from fep2.mta.online.no (lionmta2.online.no [148.122.208.25])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id RAA00467;
	Wed, 19 Sep 2001 17:34:08 -0700 (PDT)
Received: from [10.122.209.35] by fep2.mta.online.no
          (InterMail vM.4.01.03.23 201-229-121-123-20010418) with ESMTP
          id <20010920003405.TDRB392.fep2.mta.online.no@[10.122.209.35]>;
          Thu, 20 Sep 2001 02:34:05 +0200
To: G.Tsirtsis@flarion.com, gtsirt@hotmail.com, sltsao@itri.org.tw
CC: ipngwg@sunroof.eng.sun.com, ngtrans@sunroof.eng.sun.com,
        mobile-ip@sunroof.eng.sun.com
Subject: Fwd: [mobile-ip] IPv6 over Mobile IPv4
Date: Thu, 20 Sep 2001 2:34:30 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Message-Id: <20010920003405.TDRB392.fep2.mta.online.no@[10.122.209.35]>
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

George and Charles,

FYI, the Internet Draft  &#8220; http://search.ietf.org/internet-drafts/draft-mccann-mobileip-ipv6mipv4-00.txt &#8221; was recently submitted and announced on the Mobile IP mailing list. 

While we are waiting for the security-issues of MIPv6 to be resolved, I find the proposed solution promising.  It provides a mechanism for IPv6 mobility that also incorporates AAA functionality.  In the long run, the proposed idea can be relevant for IPv4 to IPv6 transition.

Their mechanism might be useful to your  "Dual Stack Moving" efforts. It is definitely related to my own Dual Stack Mobile IP draft, which I plan to rewrite, simplify and adapt to their proposal.

Earlier, we have talked about a framework for dual stack mobility. Perhaps their draft could be a good starting point for that discussion? 

-- Paal

---------------------------------------------------------------------



>From: Pete McCann <mccap@lucent.com>
>Reply-To: mobile-ip@sunroof.eng.sun.com
>To: mobile-ip@sunroof.eng.sun.com
>CC: pcalhoun@diameter.org, tom.hiller@lucent.com
>Subject: [mobile-ip] IPv6 over Mobile IPv4
>Date: Thu, 13 Sep 2001 17:39:15 -0500
>
>Hi,
>
>We (Pat Calhoun, Tom Hiller, and myself) recently wrote a draft
>describing a method for running IPv6 traffic while using Mobile IPv4
>signaling for mobility management and security.  We submitted it today
>to internet-drafts; you can find an advance copy at:
>
>http://www.diameter.org/draft-mccann-mobileip-ipv6mipv4-00.txt
>
>Basically, this could serve as an interim solution while we wait for
>all of the Mobile IPv6 security work to converge.  It would allow us
>to use the existing Mobile IPv4 security model, including AAA, for
>securing registration requests, while providing IPv6 service to
>dual-stack mobile nodes.  It may also help ease the overall transition
>to IPv6 because it only requires IPv6 support in the MN, FA, HA, and
>home network, while the network between the FA and HA could be a
>legacy IPv4 cloud.
>
>The draft itself is fairly straightforward; we would appreciate
>comments on the list and would like to see if there is interest in
>making this a working group item.
>
>-Pete




From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep 20 12:49:48 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15543
	for <mobileip-archive@odin.ietf.org>; Thu, 20 Sep 2001 12:49:48 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id KAA11663;
	Thu, 20 Sep 2001 10:48:55 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA11802;
	Thu, 20 Sep 2001 09:48:57 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8KGmA7B015904
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 20 Sep 2001 09:48:10 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8KGm9NU015903
	for mobile-ip-dist; Thu, 20 Sep 2001 09:48:09 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8KGm67B015893
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 20 Sep 2001 09:48:06 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA23429
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 20 Sep 2001 09:48:07 -0700 (PDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA20338
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 20 Sep 2001 10:48:57 -0600 (MDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id JAA03019;
	Thu, 20 Sep 2001 09:48:05 -0700 (PDT)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f8KGm4g22150;
	Thu, 20 Sep 2001 09:48:04 -0700
X-mProtect:  Thu, 20 Sep 2001 09:48:04 -0700 Nokia Silicon Valley Messaging Protection
Received: from charliep.iprg.nokia.com (205.226.2.89, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpdXXNIKi; Thu, 20 Sep 2001 09:47:48 PDT
Message-ID: <3BAA1DAA.8CBAB4CD@iprg.nokia.com>
Date: Thu, 20 Sep 2001 09:47:38 -0700
From: "Charles E. Perkins" <charliep@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Brian Haley USG <haley@zk3.dec.com>
CC: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Mobile IPv6 draft revision
References: <200108281851.AA09446@dogbert.zk3.dec.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hello Brian,

After some delay, I am again trying to get the draft revision finished...



Brian Haley USG wrote:

> Hi Charlie,
> 
> Here are some comments I have on draft -14.
> 
> Section 6.4 (HA info option)
> 
>  The last paragraph starts:
> 
>   "If both the Home Agent Preference and Home Agent Lifetime are set
>    to their default values specified above..."
> 
>  but a default value for Home Agent Lifetime is never discussed.
>  Maybe it should be the same as the Router Lifetime value that
>  would be sent in an RA?

That sounds just right.  I've included a sentence to that
effect in the description for the Home Agent Lifetime field.

> Section 6.5 (Router advert changes)
> 
>  Why has the MinRtrADvInterval shrunk to 0.05 seconds from 0.5 seconds?

This is intended to enable faster handovers when movement detection
depends on receiving router advertisements.  It is not by any means
_required_ for advertisements to come out that often; similarly,
it is not by any means _required_ for movement detection to depend
on receiving advertisements.

> Section 8.2 (Recieving BUs)
> 
>  This still has the old wording in bullet #4 that:
> 
>   "The Sequence Number field in the Binding Update option is greater
>    than the Sequence Number received in the previous Binding Update
>    for this home address, if any. ..."
> 
>   "Any Binding Update not satisfying all of these tests MUST be
>    silently ignored..."
> 
>  Section 5.2 has the correct wording that should be put here:
> 
>   "If the mobile node sends a sequence number which is not greater than
>    the sequence number from the last successful Binding Update, then the
>    home agent MUST send back a Binding Acknowledgement with status code
>    141, and the last accepted sequence number in the Sequence Number
>    field of the Binding Acknowledgement."

This is trickier.  As I understand it, the specfication needs to be
as follows:

- If the sequence number is wrong, a Binding Acknowledgement is sent.
- Other violations of the bulleted conditions cause the packet to
  be silently ignored.

Acting on this understanding, I have included the suggested paragraph,
somewhat reworded, after the bulleted list of conditions.  I have
also reworded the text about silently discarding the packet for
other violations.


> Section 8.5 (Sending BAs)
> 
>  The second paragraph mentions IPsec:
> 
>   "The packet in which the Binding Acknowledgement is returned MUST meet
>    the specific IPsec requirements for Binding Acknowledgements..."
> 
>  it should maybe say "security".

Now, it says "authentication".


> Thanks,
> 
> -Brian

Thanks for your comments!

Regards,
Charlie P.


From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep 20 13:35:02 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16987
	for <mobileip-archive@odin.ietf.org>; Thu, 20 Sep 2001 13:35:02 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id LAA21936;
	Thu, 20 Sep 2001 11:34:10 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id KAA00832;
	Thu, 20 Sep 2001 10:34:15 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8KHPm7B016009
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 20 Sep 2001 10:25:48 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8KHPmak016008
	for mobile-ip-dist; Thu, 20 Sep 2001 10:25:48 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from eastmail1.East.Sun.COM (eastmail1.East.Sun.COM [129.148.1.240])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8KHPk7B016001
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 20 Sep 2001 10:25:46 -0700 (PDT)
Received: from onion.east.sun.com (onion.East.Sun.COM [129.148.174.110])
	by eastmail1.East.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id NAA04161
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 20 Sep 2001 13:25:48 -0400 (EDT)
Received: (from glass@localhost)
	by onion.east.sun.com (8.9.3+Sun/8.9.3) id NAA18692
	for mobile-ip@sunroof.eng.sun.com; Thu, 20 Sep 2001 13:26:19 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8KGUD7B015813
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 20 Sep 2001 09:30:13 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA24151
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 20 Sep 2001 09:30:15 -0700 (PDT)
Received: from netmail.alcatel.com (netmail.alcatel.com [128.251.168.50])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA09705
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 20 Sep 2001 10:31:05 -0600 (MDT)
Received: from auds953.usa.alcatel.com (auds953.usa.alcatel.com [143.209.238.6])
	by netmail.alcatel.com (8.9.1/8.9.1) with ESMTP id LAA12590
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 20 Sep 2001 11:30:12 -0500 (CDT)
Received: from alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.10.2/8.10.2) with ESMTP id f8KGUCx25592
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 20 Sep 2001 11:30:12 -0500 (CDT)
Message-ID: <3BAA0A5D.2D376204@alcatel.com>
Date: Thu, 20 Sep 2001 11:25:17 -0400
From: Behcet Sarikaya <behcet.sarikaya@alcatel.com>
X-Mailer: Mozilla 4.76 [en]C-CCK-MCD BDPjm-Sony3  (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Minutes of London Meeting
References: <697DAA22C5004B4596E033803A7CEF441E86DD@daebe007.NOE.Nokia.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hi Raj,
  I extracted the following from the minutes you distributed earlier. Are
there answers to these questions now? Or they are still up in the air?



- What destination address to use in the F-BU? It was confirmed by
  group that global IP address should be used instead of local address
  as suggested by current specifications
- Creating binding cache entry on previous access router (after
  receiving Hack and after sending F-Back to the old link). It was
  concluded that this is implementation specific and doesn't really have
  any protocol impact.
- What source address to use when sending F-BU from newer AR?
- Issues may be related to sending of F-NA (including only one IP
  address suffices). The group provided comments that it is essential to
  know both Hack and F-Back.
- When to change default router? There are two options proposed: after
  receiving proxy PA (may be not) or after actually attaching to the new
  link (the new AR).

"Patil Basavaraj (NET/Dallas)" wrote:

Thanks in advance.

--
Behcet



From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep 20 13:36:40 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17055
	for <mobileip-archive@odin.ietf.org>; Thu, 20 Sep 2001 13:36:40 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id LAA23408;
	Thu, 20 Sep 2001 11:35:48 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id KAA01432;
	Thu, 20 Sep 2001 10:35:53 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8KHRe7B016042
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 20 Sep 2001 10:27:40 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8KHRed7016040
	for mobile-ip-dist; Thu, 20 Sep 2001 10:27:40 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from eastmail2.East.Sun.COM (eastmail2.East.Sun.COM [129.148.1.241])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8KHRb7B016027
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 20 Sep 2001 10:27:37 -0700 (PDT)
Received: from onion.east.sun.com (onion.East.Sun.COM [129.148.174.110])
	by eastmail2.East.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id NAA25426
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 20 Sep 2001 13:27:38 -0400 (EDT)
Received: (from glass@localhost)
	by onion.east.sun.com (8.9.3+Sun/8.9.3) id NAA18747
	for mobile-ip@sunroof.eng.sun.com; Thu, 20 Sep 2001 13:28:09 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8KGjt7B015858
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 20 Sep 2001 09:45:55 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA10863
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 20 Sep 2001 09:45:57 -0700 (PDT)
Received: from netmail.alcatel.com (netmail.alcatel.com [128.251.168.50])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id KAA08310
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 20 Sep 2001 10:45:46 -0600 (MDT)
Received: from auds952.usa.alcatel.com (auds952.usa.alcatel.com [143.209.238.7])
	by netmail.alcatel.com (8.9.1/8.9.1) with ESMTP id LAA15714
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 20 Sep 2001 11:45:56 -0500 (CDT)
Received: from alcatel.com (localhost [127.0.0.1])
	by auds952.usa.alcatel.com (8.10.2/8.10.2) with ESMTP id f8KGjtP12564
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 20 Sep 2001 11:45:55 -0500 (CDT)
Message-ID: <3BAA0E0C.24766D24@alcatel.com>
Date: Thu, 20 Sep 2001 11:41:01 -0400
From: Behcet Sarikaya <behcet.sarikaya@alcatel.com>
X-Mailer: Mozilla 4.76 [en]C-CCK-MCD BDPjm-Sony3  (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] comments on HMIPv6 draft
References: <034BEFD03799D411A59F00508BDF754603008CCB@esealnt448.al.sw.ericsson.se>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hi Hesham,
  In
draft-mobileip-hmipv6-04.txt in Fig. A.2 MAP sends HI to nAR. This interaction is
marked 1a which seems to suggest that MAP knows that HO got initiated before
anybody else. How could this be possible considering the fact that MAP is probably
the farthest away node in the configuration?

"Hesham Soliman (ERA)" wrote:

> > I just wonder some bits in HMIPv6 draft (04):
> >
> >   - Why needs two bits ("R" and "M") instead of one to classify
> >     Basic Mode and Extended Mode?
> >
>         => No good answer really ! It seemed safer at the time to explicitly
>         leave on flag per mode.
>
> >  (Consequently the "P" and "T")
> >     Is there any other mode beyond Basic Mode and Extended Mode?
> >
>         => You need 2 here because one says that the network is mandatnig
>         that the user uses RCoA as a source address. So if another
>         one is used the routers ingress filtering will drop the packets.
>         Anothe flag is needed to allow the user to use RCoA if they wish (MAY).
>
> > Also I would favor if a section on possible "conceptual data
> > structures" added/updated over MIPv6 could be provided.
> >
>         => OK, will add that to the TODO list.
>
>         Thanks,
>         Hesham

Regards,

--
Behcet



From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep 20 14:39:02 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA18800
	for <mobileip-archive@odin.ietf.org>; Thu, 20 Sep 2001 14:39:01 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA09352;
	Thu, 20 Sep 2001 11:38:04 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id LAA25232;
	Thu, 20 Sep 2001 11:37:39 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8KITG7B016253
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 20 Sep 2001 11:29:16 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8KITGTY016252
	for mobile-ip-dist; Thu, 20 Sep 2001 11:29:16 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8KITC7B016245
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 20 Sep 2001 11:29:12 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id LAA22304
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 20 Sep 2001 11:29:13 -0700 (PDT)
Received: from mgw-dax1.ext.nokia.com (mgw-dax1.ext.nokia.com [63.78.179.216])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id LAA23821
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 20 Sep 2001 11:29:12 -0700 (PDT)
Received: from davir01nok.americas.nokia.com (davir01nok.americas.nokia.com [172.18.242.84])
	by mgw-dax1.ext.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f8KITD319678
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 20 Sep 2001 13:29:14 -0500 (CDT)
Received: from daebh002.NOE.Nokia.com (unverified) by davir01nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T561c36f721ac12f2540ff@davir01nok.americas.nokia.com>;
 Thu, 20 Sep 2001 13:29:11 -0500
Received: from daebe007.NOE.Nokia.com ([172.18.242.211]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.2966);
	 Thu, 20 Sep 2001 13:29:11 -0500
content-class: urn:content-classes:message
Subject: RE: [mobile-ip] Minutes of London Meeting
Date: Thu, 20 Sep 2001 13:29:10 -0500
Message-ID: <697DAA22C5004B4596E033803A7CEF441E86F4@daebe007.NOE.Nokia.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Thread-Topic: [mobile-ip] Minutes of London Meeting
Thread-Index: AcFB+4sfiLeR7K3sEdWrxAAIx6S5QwABj+Ow
x-mimeole: Produced By Microsoft Exchange V6.0.4712.0
From: "Patil Basavaraj (NET/Dallas)" <Basavaraj.Patil@nokia.com>
To: <mobile-ip@sunroof.eng.sun.com>
Cc: <behcet.sarikaya@alcatel.com>, "'Gopal Dommety'" <gdommety@cisco.com>
X-OriginalArrivalTime: 20 Sep 2001 18:29:11.0511 (UTC) FILETIME=[24A2EE70:01C14202]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by sunroof.eng.sun.com id f8KITC7B016246
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 8bit

Behcet,

The next revision of FMIPv6 will possibly address and clarify
these issues. I do agree that it is important to clearly specify
the mechanics to get some degree of interoperability between
implementatoins. I am hoping that Gopal Dommety (editor of
FMIPv6) will have noted your concerns and addresses them in
a new revision that should be out soon.

-Basavaraj

> 
> Hi Raj,
>   I extracted the following from the minutes you distributed 
> earlier. Are
> there answers to these questions now? Or they are still up in the air?
> 
> 
> 
> - What destination address to use in the F-BU? It was confirmed by
>   group that global IP address should be used instead of local address
>   as suggested by current specifications
> - Creating binding cache entry on previous access router (after
>   receiving Hack and after sending F-Back to the old link). It was
>   concluded that this is implementation specific and doesn't 
> really have
>   any protocol impact.
> - What source address to use when sending F-BU from newer AR?
> - Issues may be related to sending of F-NA (including only one IP
>   address suffices). The group provided comments that it is 
> essential to
>   know both Hack and F-Back.
> - When to change default router? There are two options proposed: after
>   receiving proxy PA (may be not) or after actually attaching 
> to the new
>   link (the new AR).
> 
> "Patil Basavaraj (NET/Dallas)" wrote:
> 
> Thanks in advance.
> 
> --
> Behcet
> 


From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep 20 15:26:26 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19633
	for <mobileip-archive@odin.ietf.org>; Thu, 20 Sep 2001 15:26:25 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA02143;
	Thu, 20 Sep 2001 12:25:44 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id MAA13852;
	Thu, 20 Sep 2001 12:25:37 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8KJGs7B016349
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 20 Sep 2001 12:16:55 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8KJGs8S016348
	for mobile-ip-dist; Thu, 20 Sep 2001 12:16:54 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8KJGo7B016341
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 20 Sep 2001 12:16:50 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id MAA23948
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 20 Sep 2001 12:16:46 -0700 (PDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id NAA18461
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 20 Sep 2001 13:16:35 -0600 (MDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id MAA14937;
	Thu, 20 Sep 2001 12:16:45 -0700 (PDT)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f8KJGiA32427;
	Thu, 20 Sep 2001 12:16:44 -0700
X-mProtect:  Thu, 20 Sep 2001 12:16:44 -0700 Nokia Silicon Valley Messaging Protection
Received: from charliep.iprg.nokia.com (205.226.2.89, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpdo0dK2k; Thu, 20 Sep 2001 12:16:43 PDT
Message-ID: <3BAA409C.F73674F1@iprg.nokia.com>
Date: Thu, 20 Sep 2001 12:16:44 -0700
From: "Charles E. Perkins" <charliep@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: karen.e.nielsen@lmd.ericsson.se, karen.e.nielsen@ted.ericsson.dk
CC: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] -14 Authentication Data computation
References: <F7709E7648BAD41181E60008C716A229F56750@edkchnt102.lmd.ericsson.se>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hello Karen,

"Karen E Nielsen (TED)" wrote:
> 
> Comment/question to the computation of the Authentication Data covering
> a Binding Update and a Binding Acknowledgement in draft -14.
> 
> According to section 4.4 in draft-14 the Authentication Data covering
> a Binding Updata MUST be computed over a bit string containing the
> following IP addresses:
>	Destination IP Address of the IPv6 header
>	Care-of Address, in the Source IP Address of the IPv6 header
>	Home Address, from the Home Address destination option
>	+ some more data
> 
> And the Authentication Data covering a Binding Acknowledgement MUST be
> computed over a bit string containing the following IP addresses :
>	Destination IP Address of the IPv6 header
>	Source IP Address of the IPv6 header
>	+ some more data
> 
> First of all I suppose that what is meant is the destination addresses
> of the IPv6 header as it appears at the receiver end (in line with the
> computation of authentication data in IP SEC)  !?   Since both the BU
> (in case the CN is mobile) and the BUAck might be send using a routing
> header this will be important to specify, I think.

I agree!


> Secondly, in the case where the CN is itself a mobile node, the source
> address of the IP header of the BuAck will be a CoA of the CN,
> which really has nothing to do with the acknowledgement of a BU sent
> to the CN - wouldn't the appropriate address to cover here be the Home
> address of the CN -  either appearing in the source address of the IP
> header or in the Home Address option ?

Again, I agree!  Thank you for pointing out these problems.

Here is the new text for section 4.4:

=======================================================================
4.4. Authentication Requirements for Binding Update and Acknowledgement

   Any packet that includes a Binding Update or Binding Acknowledgement
   option has to contain some Authentication Data to guard against
   malicious Binding Updates or Acknowledgements.  The way that
   the Authentication Data is computed has to provide sender
   authentication, data integrity protection, and replay protection.
   This section specifies requirements for which data is to be protected
   when the Authentication Data Sub-Option is used to supply the
   necessary authentication data for the Binding Update or Binding
   Acknowledgement.  Every IPv6 node which supports transmission or
   reception of these destination options MUST support the computation
   of the Authentication Data Sub-Option according to the rules in
   this section.  The Authentication Data Sub-Option MUST be the last
   Sub-Option contained within any destination option in which the
   Authentication Data Sub-Option occurs.

   The Authentication Data covering a Binding Update or MUST be computed
   over a bitstring containing the following fields of the IPv6 header
   and destination options, in order:

    -  The IPv6 address of the destination of the packet, as seen by the
       recipient
    -  Care-of Address, in the Source IP Address of the IPv6 header
    -  The Home Address of the mobile node, from the Home Address
       destination option
    -  Option Type of the Binding Update destination option
    -  Option Length of the Binding Update destination option
    -  All flags of the Binding Update destination option
    -  Reserved Field of the Binding Update destination option
    -  Sequence Number Field of the Binding Update
    -  Lifetime of the Binding Update destination option
    -  The entire data from all Binding Update Sub-Options (except the
       Authentication Data suboption), if any others exist
    -  The Type (i.e., the 8-bit value 0x04) and the Length of the
       Authentication Data Sub-Option
    -  Security Parameters Index (SPI) of the Authentication Data
       Sub-Option

   When a Routing Header is used to deliver the Binding Update to
   the receiving node, the address to be used for the Destination IP
   Address part of the computation will initially be located as the last
   component of the Routing Header.  Otherwise, the address to be used
   will be the Destination IP Address in the IPv6 header of the outgoing
   packet.

   When the Authentication Data Sub-Option is used with a Binding
   Acknowledgement, the Authentication Data MUST be computed over a
   bitstring containing the following data, in order:

    -  The IPv6 address of the destination of the packet, as seen by the
       recipient
    -  The Home Address of the sender
    -  Option Type of the Binding Acknowledgement destination option
    -  Option Length of the Binding Acknowledgement
    -  Status of the Binding Acknowledgement
    -  Sequence Number field of the Binding Acknowledgement
    -  Lifetime field of the Binding Acknowledgement destination option
    -  Refresh field of the Binding Acknowledgement destination option
    -  The entire data from all Binding Acknowledgement Sub-Options
       (except the Authentication Data suboption), if any others exist
    -  The Type (i.e., the 8-bit value 0x04) and the Length of the
       Authentication Data Sub-Option
    -  Security Parameters Index (SPI) of the Authentication Data
       Sub-Option

   When a Home Address destination option is used to deliver the Binding
   Acknowledgement to the receiving node, the Home Address of the sender
   will be located in that destination option.  Otherwise, the Home
   Address of the sender will be located in the Source IP Address field
   of the IPv6 header.

   If a Security Association applied to the packet for other reasons
   requires use of ESP [12], for example to encrypt the transport layer
   data carried in the packet, this use of ESP is not sufficient to
   satisfy the authentication requirements of Mobile IPv6.

   Authentication Data assuring the integrity of Binding Updates and
   Binding Acknowledgement MAY, in some cases, instead be supplied by
   other authentication mechanisms outside the scope of this document
   (e.g., IPsec [13]).  When alternative mechanisms are used, the same
   data as indicated above MUST be included as part of the input data
   stream for the authentication algorithm; however (according to the
   requirements of the alternative authentication algorithm) the order
   of the data elements in the input data stream MAY be changed from the
   order specfied within this section for use with the Authentication
   Data Sub-Option (see section 5.5).

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

Note: the exact wording and placement of this text is likely to
change if I find further problems.  Maybe it should be two subsections
instead of one.  Maybe there should be two Authentication Data
Sub-Options instead of one.

Comments?


> /Karen

Regards,
Charlie P.


From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep 20 15:36:21 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19850
	for <mobileip-archive@odin.ietf.org>; Thu, 20 Sep 2001 15:36:20 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA06280;
	Thu, 20 Sep 2001 12:35:38 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id MAA16580;
	Thu, 20 Sep 2001 12:35:19 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8KJPm7B016367
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 20 Sep 2001 12:25:48 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8KJPlTa016366
	for mobile-ip-dist; Thu, 20 Sep 2001 12:25:47 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8KJPh7B016359
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 20 Sep 2001 12:25:43 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id MAA25900
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 20 Sep 2001 12:25:44 -0700 (PDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA17371
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 20 Sep 2001 13:26:35 -0600 (MDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id MAA15697;
	Thu, 20 Sep 2001 12:25:43 -0700 (PDT)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f8KJPgw14306;
	Thu, 20 Sep 2001 12:25:42 -0700
X-mProtect:  Thu, 20 Sep 2001 12:25:42 -0700 Nokia Silicon Valley Messaging Protection
Received: from charliep.iprg.nokia.com (205.226.2.89, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpdQ91gKk; Thu, 20 Sep 2001 12:25:40 PDT
Message-ID: <3BAA42B5.12CB0D8F@iprg.nokia.com>
Date: Thu, 20 Sep 2001 12:25:41 -0700
From: "Charles E. Perkins" <charliep@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Noriaki Takamiya <takamiya@po.ntts.co.jp>
CC: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] About Home Agent Flag in Router Advertisement Message
References: <20010906.100949.424336656.takamiya@po.ntts.co.jp>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hello Takamiya,

Noriaki Takamiya wrote:

>   When a Home Agent sends Router Advertisement Message and changes
>   Home Agent Flag(H) from on to off, should other Home Agent remove
>   this router from the Home Agent List?

That seems like a very reasonable requirement.  Unfortunately,
it means checking for removal upon reception of every Router
Advertisement.  However, I do not think that is much more
work than already has to be done.

>   I thought that the Home Agent changed Router Advertisement Message
>   change Home Agent Flag from on to off, the other Home Agent should
>   remove this router entry. But It seems that this behavior is not
>   documented(draft 14) explicitly.

I will make it explicit.

>   I'm newbie about this mailing list, so I will apologize some
>   mistakes.

No apologies needed, and thanks for your observation!

> Noriaki Takamiya

Regards,
Charlie P.


From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep 20 15:48:16 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21742
	for <mobileip-archive@odin.ietf.org>; Thu, 20 Sep 2001 15:48:16 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA11332;
	Thu, 20 Sep 2001 12:47:34 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id MAA19370;
	Thu, 20 Sep 2001 12:47:24 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8KJbs7B016485
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 20 Sep 2001 12:37:54 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8KJbskr016484
	for mobile-ip-dist; Thu, 20 Sep 2001 12:37:54 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from jurassic.eng.sun.com (jurassic [129.146.86.38] (may be forged))
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8KJbp7B016477
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 20 Sep 2001 12:37:51 -0700 (PDT)
Received: from istanbul.Eng.Sun.COM (istanbul.Eng.Sun.COM [129.146.86.247])
	by jurassic.eng.sun.com (8.12.0+Sun/8.12.0) with SMTP id f8KJbpVj694328;
	Thu, 20 Sep 2001 12:37:52 -0700 (PDT)
Message-Id: <200109201937.f8KJbpVj694328@jurassic.eng.sun.com>
Date: Thu, 20 Sep 2001 12:37:41 -0700 (PDT)
From: Alper Yegin <Alper.Yegin@eng.sun.com>
Subject: Re: [mobile-ip] New BETH Draft
To: mobile-ip@sunroof.eng.sun.com
Cc: gdommety@cisco.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: F6sxzEWcY21ZOhuBIkvtyQ==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4_37 SunOS 5.8.1 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Jim,

> >> What I am proposing is that if the old AR knows that the new AR does
> >> not support FMIPv6, it sends a PrxyRtAdv with a new code indicating
> >> that. This benefits *both* a BETH capable MN and one that is doing
> >> standard FMIPv6. If the new AR does support FMIPv6, of course, it sends a 
> >
> >I think this already exists for FMIPv6. Checking the draft, code 128 of 
PrRtAdv 
> >can be used for this case as well.
> >
> 
> I had something different in mind, namely refining the notification
> from "Access Point Not Known" to "Access Point Known, but Does Not
> Support FMIPv6". If the MN gets an L2 trigger, it could send
> a SolRtAdv right away, as described in draft-ietf-mobileip-ipv6-14.txt
> pg. 80. If the MN doesn't know what the Access Point is, it needs
> to wait for the RtAdv. If knows the AP, it can solicit the RtAdv. This could
> result in faster CoA establishment (though, of course, not nearly
> as fast as FMIPv6).


OK, having more explicit messages makes sense.

From other e-mails, I see you are positive on using a message to inform MN that 
it's entering a BETH domain. This helps too.

One more question remaining from my last message: what if MN doesn't support 
BETH?

With the current protocol specification, ARs don't know this, since there's no 
message sent from MN to AR. Maybe we should have one?

If ARs run BETH assuming MN supports it, this might cause problems with non-BETH 
mobiles:

- MN cannot correctly detect movement, because receiving its packet will imply 
it hasn't moved.
- I'd recommend ARs send an unsolicited unicast RA as soon as they detect a 
device attached. This saves bandwidth and latency, compared to MN soliciting or 
waiting for AR to send periodically. So, using a L2 technology that supports the 
trigger, my mobile node was going to wait for an unsolicited RA. But AR with 
BETH support wouldn't do that. So this causes some additional latency.

I think if both MN and ARs are fully aware of each other's capabilities before 
they take any actions, that'd be a more robust solution that can be extended and 
can fully interoperate with other scenarios.


alper




From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep 20 16:41:21 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22620
	for <mobileip-archive@odin.ietf.org>; Thu, 20 Sep 2001 16:41:21 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA07169;
	Thu, 20 Sep 2001 13:40:12 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id NAA00863;
	Thu, 20 Sep 2001 13:33:53 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8KKPK7B016589
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 20 Sep 2001 13:25:21 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8KKPKNu016588
	for mobile-ip-dist; Thu, 20 Sep 2001 13:25:20 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from heliopolis.eng.sun.com (bigbang.Eng.Sun.COM [152.70.8.30])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8KKPH7B016581
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 20 Sep 2001 13:25:17 -0700 (PDT)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.eng.sun.com (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id NAA16137;
	Thu, 20 Sep 2001 13:25:19 -0700 (PDT)
Message-Id: <200109202025.NAA16137@heliopolis.eng.sun.com>
Date: Thu, 20 Sep 2001 13:25:18 -0700 (PDT)
From: James Kempf <James.Kempf@Sun.COM>
Subject: Re: [mobile-ip] New BETH Draft
To: mobile-ip@sunroof.eng.sun.com
Cc: gdommety@cisco.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: z2egdxdgNtJTiJLGc5LsOQ==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Hi Alper,


>One more question remaining from my last message: what if MN doesn't support 
>BETH?
>
>With the current protocol specification, ARs don't know this, since there's no 
>message sent from MN to AR. Maybe we should have one?
>
>If ARs run BETH assuming MN supports it, this might cause problems with 
non-BETH 
>mobiles:
>

Yes, I think that there probably ought to be some way to indicate
this. And also for FMIPv6. Otherwise, the AR might think the
MN can do FMIPv6 handover and send it the PrxyRtAdv. The MN
will ignore it, of course, but perhaps better to not send it
at all.

So it seems like we should have a code in SolRtAdv and SolPrxyRtAdv
for indicating whether the MN supports FMIPv6 or BETH as well. 


		jak



From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep 20 18:18:06 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24955
	for <mobileip-archive@odin.ietf.org>; Thu, 20 Sep 2001 18:18:06 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id QAA09063;
	Thu, 20 Sep 2001 16:17:15 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id PAA21452;
	Thu, 20 Sep 2001 15:17:19 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8KMGO7B016885
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 20 Sep 2001 15:16:24 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8KMGONm016884
	for mobile-ip-dist; Thu, 20 Sep 2001 15:16:24 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8KMGI7B016877
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 20 Sep 2001 15:16:19 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id PAA16327
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 20 Sep 2001 15:16:18 -0700 (PDT)
Received: from netmail.alcatel.com (netmail.alcatel.com [128.251.168.50])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id QAA08957
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 20 Sep 2001 16:17:09 -0600 (MDT)
Received: from auds953.usa.alcatel.com (auds953.usa.alcatel.com [143.209.238.6])
	by netmail.alcatel.com (8.9.1/8.9.1) with ESMTP id RAA16524
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 20 Sep 2001 17:16:17 -0500 (CDT)
Received: from alcatel.com (localhost [127.0.0.1])
	by auds953.usa.alcatel.com (8.10.2/8.10.2) with ESMTP id f8KMGHx02512
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 20 Sep 2001 17:16:17 -0500 (CDT)
Message-ID: <3BAA6BC8.50E2041C@alcatel.com>
Date: Thu, 20 Sep 2001 17:20:56 -0500
From: Behcet Sarikaya <behcet.sarikaya@alcatel.com>
Organization: Alcatel USA
X-Mailer: Mozilla 4.75 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Minutes of London Meeting
References: <697DAA22C5004B4596E033803A7CEF441E86F4@daebe007.NOE.Nokia.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Raj,
  Maybe Rajeev can provide his answers? MN is at nAR right after receiving
PrRtrAdv. What are src and dst address values of F-BU and F-Back?
Sorry if this had already been discussed before.

"Patil Basavaraj (NET/Dallas)" wrote:

> Behcet,
>
> The next revision of FMIPv6 will possibly address and clarify
> these issues. I do agree that it is important to clearly specify
> the mechanics to get some degree of interoperability between
> implementatoins. I am hoping that Gopal Dommety (editor of
> FMIPv6) will have noted your concerns and addresses them in
> a new revision that should be out soon.
>
> -Basavaraj
>

Regards,
--
Behcet



From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep 20 18:26:20 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA25073
	for <mobileip-archive@odin.ietf.org>; Thu, 20 Sep 2001 18:26:19 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id PAA24815;
	Thu, 20 Sep 2001 15:25:38 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id PAA23255;
	Thu, 20 Sep 2001 15:25:32 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8KMOi7B016941
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 20 Sep 2001 15:24:44 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8KMOhPX016940
	for mobile-ip-dist; Thu, 20 Sep 2001 15:24:43 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from heliopolis.eng.sun.com (heliopolis.Eng.Sun.COM [152.70.1.39])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8KMOe7B016933
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 20 Sep 2001 15:24:40 -0700 (PDT)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.eng.sun.com (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id PAA25122
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 20 Sep 2001 15:24:41 -0700 (PDT)
Message-Id: <200109202224.PAA25122@heliopolis.eng.sun.com>
Date: Thu, 20 Sep 2001 15:24:40 -0700 (PDT)
From: James Kempf <James.Kempf@Sun.COM>
Subject: Re: [mobile-ip] Minutes of London Meeting
To: mobile-ip@sunroof.eng.sun.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: QZjR8eAaYiZllb9jKMSW4Q==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Behcet,

>  Maybe Rajeev can provide his answers? MN is at nAR right after receiving
>PrRtrAdv. What are src and dst address values of F-BU and F-Back?
>Sorry if this had already been discussed before.
>

I guess I'm not really sure this will always be true. Ideally, MN will
be at oAR when it gets PrxyRtAdv, but if the handover happens more
quickly that anticipated (maybe the MN speeds up from 30 mph to
60 mph), it could get to nAR sooner. 

		jak



From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep 20 20:34:21 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA27201
	for <mobileip-archive@odin.ietf.org>; Thu, 20 Sep 2001 20:34:20 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id RAA08300;
	Thu, 20 Sep 2001 17:33:35 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id RAA16692;
	Thu, 20 Sep 2001 17:33:27 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8L0WV7B017207
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 20 Sep 2001 17:32:31 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8L0WVrW017206
	for mobile-ip-dist; Thu, 20 Sep 2001 17:32:31 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8L0WS7B017199
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 20 Sep 2001 17:32:28 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id RAA08517
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 20 Sep 2001 17:32:30 -0700 (PDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id RAA10343
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 20 Sep 2001 17:32:29 -0700 (PDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id RAA07475;
	Thu, 20 Sep 2001 17:32:22 -0700 (PDT)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f8L0WMd02919;
	Thu, 20 Sep 2001 17:32:22 -0700
X-mProtect:  Thu, 20 Sep 2001 17:32:22 -0700 Nokia Silicon Valley Messaging Protection
Received: from vijayd.iprg.nokia.com (205.226.2.94, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpd7m3NHZ; Thu, 20 Sep 2001 17:32:20 PDT
Message-ID: <3BAA8A94.B9D19A77@iprg.nokia.com>
Date: Thu, 20 Sep 2001 17:32:20 -0700
From: Vijay Devarapalli <vijayd@iprg.nokia.com>
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: mobile-ip@sunroof.eng.sun.com
CC: gdommety@cisco.com
Subject: Re: [mobile-ip] New BETH Draft
References: <200109202025.NAA16137@heliopolis.eng.sun.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

James Kempf wrote:
> 
> Hi Alper,
> 
> >One more question remaining from my last message: what if MN doesn't support
> >BETH?
> >
> >With the current protocol specification, ARs don't know this, since there's no
> >message sent from MN to AR. Maybe we should have one?
> >
> >If ARs run BETH assuming MN supports it, this might cause problems with
> non-BETH
> >mobiles:
> >
> 
> Yes, I think that there probably ought to be some way to indicate
> this. And also for FMIPv6. Otherwise, the AR might think the
> MN can do FMIPv6 handover and send it the PrxyRtAdv. The MN
> will ignore it, of course, but perhaps better to not send it
> at all.
> 
> So it seems like we should have a code in SolRtAdv and SolPrxyRtAdv
> for indicating whether the MN supports FMIPv6 or BETH as well.

you dont need such a thing for FMIPv6. if the MN does not respond 
to the PrxyRtAdv, nothing happens. the oldAR does not start
forwarding packets to the newAR. the MN moves over to the newAR, 
sends a router solicitation and gets a router advertisement.

vijay

> 
>                 jak


From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep 20 20:48:15 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA27320
	for <mobileip-archive@odin.ietf.org>; Thu, 20 Sep 2001 20:48:15 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id RAA11740;
	Thu, 20 Sep 2001 17:47:33 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id RAA19143;
	Thu, 20 Sep 2001 17:47:28 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8L0kX7B017275
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 20 Sep 2001 17:46:33 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8L0kXCi017274
	for mobile-ip-dist; Thu, 20 Sep 2001 17:46:33 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8L0kS7B017267
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 20 Sep 2001 17:46:30 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id RAA22744
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 20 Sep 2001 17:46:30 -0700 (PDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id RAA17321
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 20 Sep 2001 17:46:29 -0700 (PDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id RAA08226
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 20 Sep 2001 17:46:28 -0700 (PDT)
X-Delivered-For: <mobile-ip@sunroof.eng.sun.com>
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f8L0kSb27275
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 20 Sep 2001 17:46:28 -0700
X-mProtect:  Thu, 20 Sep 2001 17:46:28 -0700 Nokia Silicon Valley Messaging Protection
Received: from rajeev.iprg.nokia.com (205.226.2.90, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpdIhwrrj; Thu, 20 Sep 2001 17:44:53 PDT
Message-ID: <3BAA8D85.4780C796@iprg.nokia.com>
Date: Thu, 20 Sep 2001 17:44:53 -0700
From: Rajeev Koodli <rajeev@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Minutes of London Meeting
References: <697DAA22C5004B4596E033803A7CEF441E86F4@daebe007.NOE.Nokia.com> <3BAA6BC8.50E2041C@alcatel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hello Bechet,


Behcet Sarikaya wrote:

> Raj,
>   Maybe Rajeev can provide his answers? MN is at nAR right after receiving
> PrRtrAdv. What are src and dst address values of F-BU and F-Back?
> Sorry if this had already been discussed before.
>

If the MN determines that it is on the newAR before sending the F-BU, it must
first formulate an address on the newAR. In order for this to happen, it must
notice some sort of link switching (from oldAR to newAR). Subsequently, it
can form a newCoA (without waiting for RtAdv) since it has already seen a
PrRtAdv. It must however, ensure that its newCoA is valid before sending any
packets. For this, I think, it may use F-NA and determine what global
IP address is to be used. After that, it can send a BU to the oldAR. This
BU is more like Previous Router Notification, rather than F-BU. This BU is
still needed to enable the forwarding of packets from oldAR to the MN.

Regarding the other questions you had brought up earlier, see my replies
below.


- What source address to use when sending F-BU from newer AR?

As I mentioned above, whatever the newAR allows.

- Issues may be related to sending of F-NA (including only one IP
  address suffices). The group provided comments that it is essential to
  know both Hack and F-Back.

This statement is not clear to me. Both HI and F-NA include old-CoA. I don't
know why you need to include both addresses in F-NA..

- When to change default router? There are two options proposed: after
  receiving proxy PA (may be not) or after actually attaching to the new
  link (the new AR).

MN should not change its default router prior to changing its link (to the
new router).

Regards,

-Rajeev


>
> "Patil Basavaraj (NET/Dallas)" wrote:
>
> > Behcet,
> >
> > The next revision of FMIPv6 will possibly address and clarify
> > these issues. I do agree that it is important to clearly specify
> > the mechanics to get some degree of interoperability between
> > implementatoins. I am hoping that Gopal Dommety (editor of
> > FMIPv6) will have noted your concerns and addresses them in
> > a new revision that should be out soon.
> >
> > -Basavaraj
> >
>
> Regards,
> --
> Behcet



From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep 20 21:53:55 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA28880
	for <mobileip-archive@odin.ietf.org>; Thu, 20 Sep 2001 21:53:55 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id SAA28840;
	Thu, 20 Sep 2001 18:53:12 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id SAA20715;
	Thu, 20 Sep 2001 18:52:35 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8L1oo7B017520
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 20 Sep 2001 18:50:50 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8L1onWo017519
	for mobile-ip-dist; Thu, 20 Sep 2001 18:50:49 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8L1ok7B017512
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 20 Sep 2001 18:50:46 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id SAA02388
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 20 Sep 2001 18:50:47 -0700 (PDT)
Received: from e34.bld.us.ibm.com (e34.co.us.ibm.com [32.97.110.132])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id SAA19440
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 20 Sep 2001 18:50:46 -0700 (PDT)
Received: from westrelay02.boulder.ibm.com (westrelay02.boulder.ibm.com [9.99.140.23])
	by e34.bld.us.ibm.com (8.9.3/8.9.3) with ESMTP id VAA58260;
	Thu, 20 Sep 2001 21:48:23 -0400
Received: from d03nm103.boulder.ibm.com (d03nm103.boulder.ibm.com [9.99.140.95])
	by westrelay02.boulder.ibm.com (8.11.1m3/NCO v4.98) with ESMTP id f8L1nQN230218;
	Thu, 20 Sep 2001 19:49:26 -0600
From: "Venkata Jagana" <jagana@us.ibm.com>
Importance: Normal
Subject: [mobile-ip] Comments on Mobile IPv6 draft 14
To: mobile-ip@sunroof.eng.sun.com
Cc: charliep@iprg.nokia.com
X-Mailer: Lotus Notes Release 5.0.3 (Intl) 21 March 2000
Message-ID: <OFE80E90FA.29105FB0-ON88256ACD.00722C12@boulder.ibm.com>
Date: Thu, 20 Sep 2001 18:49:22 -0700
X-MIMETrack: Serialize by Router on D03NM103/03/M/IBM(Release 5.0.8 |June 18, 2001) at
 09/20/2001 07:49:26 PM
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>


Hello Charlie,

I have the following comments on MIP6 draft 14. Not really sure,
whether these similar issues have come up in earlier discussions or not
but I am unable to find any references in the archive. I am also
one of the contributors to MIP6 implementation in Linux
(i.e. MIPL/HUT project) and came across some of these issues during
an implementation. Thanks in advance for your responses and sorry for
the long mail.

1. There are conflicting descriptions about MN retransmitting BU's to HA
   in Sec 10.7 and Sec 10.8 if it doesn't receive matching BA's. Pasting
   the corresponding text here for quick reference.

   From Sec 10.7:
   " ...the mobile node SHOULD retransmit this Binding Update to its home
agent
   until it receives a matching Binding Acknowledgement.  Once reaching a
   retransmission timeout period of MAX_BINDACK_TIMEOUT, the mobile
   node SHOULD continue to periodically retransmit ..."

   It is quite possible that there may not be any matching BA from the HA
for
   the period of MAX_BINDACK_TIMEOUT (as noted in Sec 10.7) and in which
case
   rather than defaulting to periodic retransmissions, the MN could try the
   registration process of this binding with the remaining list of
   Home Agents for MN before switching to periodic retransmissions.

   In fact, sec 10.8, dynamic home agent address discovery (DHAAD), talks
about
   the exact similar thing of trying the home registration with the
remaining
   list of home agents.

   From Sec 10.8:
   " For example,if necessary, the mobile node MAY attempt its home
registration
   with each of these home agents,...... ...... In trying
   each of the returned home agent addresses, the mobile node SHOULD try
   each in the order listed in the Home Agent Addresses field in the
   received Home Agent Address Discovery Reply message."

   Even excluding the example piece in sec 10.8, I believe the MN should
   really try sending BU's with its remaining list of Home Agents (if any)
   after it initially failed with its first HA for a MAX_BINDACK_TIMEOUT
period.

   This needs to be clarified in the draft document.

2. This comment is also related to again Sec 10.7 "sending binding updates
   to the home agent":

   "...... the mobile node SHOULD continue to periodically retransmit
   the Binding Update at this rate until acknowledged (or until it begins
   attempting to register a different primary care-of address)."

   The above underlined statement is confusing to me because I can come up
   with two different interpretations of "different primary CoA is selected
   either from its pool of CoA's obtained in the same FN or when it has
   moved to a new FN." Of course, the first interpretation doesn't seem to
   make any sense but it quite possible to select different CoA as the
primary
   for some vague reason and use that in the BU.

   Please clarify if it really means that the selection of different
primary CoA
   is to be made after moving to a different FN or in the same FN. But, If
the
   selection of primary CoA is made within the same FN, then the spec
should
   clarify about the retransmission under Retransmission of binding update
(sec 10.11).

3. This comment is also related to again Sec 10.7 "sending binding updates
   to the home agent":

   "In the unlikely event that the mobile node's home address is
autoconfigured
    ......the home agent will reply to the mobile node's subsequent Binding
    Update with a Binding Acknowledgement showing Status 138, Duplicate
Address
    Detection failed".

   However, the draft doesn't clarify on what MN should do next in such a
scenario.
   I believe that, at least, even if this home address registration fails,
then MN
   can/should continue with additional registrations of its remaining home
addresses
   if there are any. Of course, these multiple registrations can however be
performed
   in parallel rather than doing them in sequence. In the case of a single
home address
   registration, if BA comes with status 138, then what else MN should do?
Is that the
   decision left to the implementation or would the draft clarify
something?

   Usually, I believe such a scenario wouldn't occur and I agree that it is
never
   guaranteed and hence MN possibly may pick up a different home address
and then
   continue rather than having to leave MN up in the air.

4. The above comment (3) brings up another interesting point related to
BU's sent to
   CNs.

   Consider the following scenario: If a MN sends BU to CN at any time ( as
defined in
   sec. 10.9 "A mobile node MAY send a Binding Update to any correspondent
node at
   any time to allow the correspondent node ...") after picking up new
CoA(s) but
   before the completion of Home Address registration of this same COA
(used in BU to CN),
   then won't this be a problem.

   Hence, a MN may not a send a BU to CN at any time but only after the
primary COA
   registration succeeds to make sure the home address is valid and
otherwise, this
   address will be a conflict with another node on its home network. Of
course, the procedure
   for not allowing this home address to be picked up by another network is
outside the
   scope of this document and I am sure this is a hole in the ND protocol
unless I am
   missing something here.

5. The draft doesn't talk about what would MN do if MN returns back to its
   previously visited network.

   Sec 10.20 discusses about MN returning home - I may be wrong but my
   understanding of this section is that MN is returning to its Original
   Home (OH) but not the previous FN it just visited earlier and returning
back
   to it like in example of MN moving from A -> B -> C -> B network and
   in which case, MN should deregister its earlier CoA with HA at B (FH -
Foreign Home,
   btw, pardon for my new terminology)as described in Sec 10.20 but in
addition,
   the draft should also clarify that MN should register this primary CoA
with its original HA.

   In overall, I believe the section 10.20 is fully applicable to the
scenario
   just I described but additional clarifications needed to be added.


I may be wrong in some of my interpretations but please let me know if
that's the case.

Thanks,
Venkat

----------------------------------------------------------------
Venkata R Jagana
IBM Linux Technology Centre, Beaverton
jagana@us.ibm.com
Tel: (503) 578 3430 T/L 775-3430
----------------------------------------------------------------




From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep 21 11:31:15 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28601
	for <mobileip-archive@odin.ietf.org>; Fri, 21 Sep 2001 11:31:15 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id JAA28082;
	Fri, 21 Sep 2001 09:30:21 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id IAA19342;
	Fri, 21 Sep 2001 08:30:16 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8LFSu7B018296
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 21 Sep 2001 08:28:56 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8LFStmc018295
	for mobile-ip-dist; Fri, 21 Sep 2001 08:28:55 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from heliopolis.eng.sun.com (redhook.Eng.Sun.COM [152.70.24.37])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8LFSq7B018288
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 21 Sep 2001 08:28:52 -0700 (PDT)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.eng.sun.com (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id IAA28687;
	Fri, 21 Sep 2001 08:28:51 -0700 (PDT)
Message-Id: <200109211528.IAA28687@heliopolis.eng.sun.com>
Date: Fri, 21 Sep 2001 08:28:50 -0700 (PDT)
From: James Kempf <James.Kempf@Sun.COM>
Subject: Re: [mobile-ip] New BETH Draft
To: mobile-ip@sunroof.eng.sun.com
Cc: gdommety@cisco.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: mYqM8nIEQDLGFiy5/M1Eag==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

>you dont need such a thing for FMIPv6. if the MN does not respond 
>to the PrxyRtAdv, nothing happens. the oldAR does not start
>forwarding packets to the newAR. the MN moves over to the newAR, 
>sends a router solicitation and gets a router advertisement.
>


Sure. It's only one message but somehow it seems cleaner to not
send it if you don't have to. 

		jak



From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep 21 12:23:56 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA00154
	for <mobileip-archive@odin.ietf.org>; Fri, 21 Sep 2001 12:23:55 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id JAA13260;
	Fri, 21 Sep 2001 09:22:43 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA22651;
	Fri, 21 Sep 2001 09:18:42 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8LGHh7B018497
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 21 Sep 2001 09:17:43 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8LGHhb5018496
	for mobile-ip-dist; Fri, 21 Sep 2001 09:17:43 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8LGHd7B018489
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 21 Sep 2001 09:17:39 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA22366
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 21 Sep 2001 09:17:38 -0700 (PDT)
Received: from mgw-dax1.ext.nokia.com (mgw-dax1.ext.nokia.com [63.78.179.216])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA12876
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 21 Sep 2001 10:18:27 -0600 (MDT)
Received: from davir03nok.americas.nokia.com (davir03nok.americas.nokia.com [172.18.242.86])
	by mgw-dax1.ext.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f8LGHc305033
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 21 Sep 2001 11:17:38 -0500 (CDT)
Received: from daebh001.NOE.Nokia.com (unverified) by davir03nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T5620e4d5daac12f256126@davir03nok.americas.nokia.com> for <mobile-ip@sunroof.eng.sun.com>;
 Fri, 21 Sep 2001 11:17:35 -0500
Received: from daebe007.NOE.Nokia.com ([172.18.242.211]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.2966);
	 Fri, 21 Sep 2001 11:17:34 -0500
content-class: urn:content-classes:message
Subject: [mobile-ip] WG last call - draft-ietf-mobileip-rfc2002-bis-08.txt
Date: Fri, 21 Sep 2001 11:17:34 -0500
Message-ID: <697DAA22C5004B4596E033803A7CEF441E870C@daebe007.NOE.Nokia.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Thread-Topic: WG last call - draft-ietf-mobileip-rfc2002-bis-08.txt
x-mimeole: Produced By Microsoft Exchange V6.0.4712.0
Thread-Index: AcFCuOlF+RU2gK6SEdWw4ERFU1R3dw==
From: "Patil Basavaraj (NET/Dallas)" <Basavaraj.Patil@nokia.com>
To: "'Mobile IP'" <mobile-ip@sunroof.eng.sun.com>
X-OriginalArrivalTime: 21 Sep 2001 16:17:34.0450 (UTC) FILETIME=[EC08CD20:01C142B8]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by sunroof.eng.sun.com id f8LGHe7B018490
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 8bit

Hello,

Revision 8 of rfc2002bis has been submitted. The new revision
incorporates
the MIER extensions into this document. MIER as a separate WG I-D will
be deprecated since the concept has been included in the base MIPv4
spec.

We would like to solicit comments and feedback on the new revision of
the
I-D with emphasis on the MIER sections. The deadline for receiving
comments
on this I-D is 09/28/01 after which time we will submit it to the IESG
for approval.

So if you have concerns/comments/ssues (NOT HMAC MD5), please raise them
now.

Regards,
-Basavaraj

http://www.ietf.org/internet-drafts/draft-ietf-mobileip-rfc2002-bis-08.t
xt


From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep 21 13:33:28 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02521
	for <mobileip-archive@odin.ietf.org>; Fri, 21 Sep 2001 13:33:27 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA10952;
	Fri, 21 Sep 2001 10:18:47 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id KAA26444;
	Fri, 21 Sep 2001 10:18:09 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8LHHH7B018615
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 21 Sep 2001 10:17:17 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8LHHHXC018614
	for mobile-ip-dist; Fri, 21 Sep 2001 10:17:17 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8LHHD7B018607
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 21 Sep 2001 10:17:13 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id KAA16924
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 21 Sep 2001 10:17:12 -0700 (PDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id KAA18678
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 21 Sep 2001 10:17:11 -0700 (PDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id KAA18744;
	Fri, 21 Sep 2001 10:17:06 -0700 (PDT)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f8LHH5e03388;
	Fri, 21 Sep 2001 10:17:05 -0700
X-mProtect:  Fri, 21 Sep 2001 10:17:05 -0700 Nokia Silicon Valley Messaging Protection
Received: from charliep.iprg.nokia.com (205.226.2.89, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpdfgEBKI; Fri, 21 Sep 2001 10:17:03 PDT
Message-ID: <3BAB760F.D19AE102@iprg.nokia.com>
Date: Fri, 21 Sep 2001 10:17:03 -0700
From: "Charles E. Perkins" <charliep@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Bjorn Andersson <bjorn@lifix.fi>
CC: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Mobile-Home Auth. Ext. requirement in RFC2002bis
References: <20010920170119.A24154@lifix.fi>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hello Bjorn,

The intention in the draft is to do exactly what you want.
The MN-AAA Authentication Extension is presumably (by policy)
an acceptable candidate for an "authorization-enabling extension".

Regards,
Charlie P.


Bjorn Andersson wrote:
> 
> Section 3.5.2, "Mobile-Home Authentication Extension", in
> draft-ietf-mobileip-rfc2002-bis-08.txt states that "exactly one
> authorization-enabling extension MUST be present in all Registration
> Requests".
> 
> However, in various AAA scenarios as discussed in other RFCs and IDs,
> this requirement cannot be fulfilled since the MN might only have
> an SA with AAA infrastructure, and not (yet) with the Home Agent.
> I suggest that the above section should be clarified, and require
> that the MH auth ext only has to be present if no other home
> network authentication extension is present (such as the MN-AAA
> authentication extension).
> 
> Regards,
> Bjorn Andersson
> 
> --
> Bjorn Andersson <bjorn@lifix.fi>                       +358 50 341 2556
> Lifix Systems Oy <http://www.lifix.fi/>                 PGP id 5AFC144B
> Yliopistonkatu 5, 3rd floor; FIN-00100 Helsinki


From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep 21 13:38:26 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02666
	for <mobileip-archive@odin.ietf.org>; Fri, 21 Sep 2001 13:38:24 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA18227;
	Fri, 21 Sep 2001 10:32:46 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id KAA27890;
	Fri, 21 Sep 2001 10:23:42 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8LHN37B018668
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 21 Sep 2001 10:23:03 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8LHN3jZ018667
	for mobile-ip-dist; Fri, 21 Sep 2001 10:23:03 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8LHMw7B018660
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 21 Sep 2001 10:22:59 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id KAA27755
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 21 Sep 2001 10:22:58 -0700 (PDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id KAA21898
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 21 Sep 2001 10:22:53 -0700 (PDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id KAA19128;
	Fri, 21 Sep 2001 10:22:44 -0700 (PDT)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f8LHMhT14220;
	Fri, 21 Sep 2001 10:22:43 -0700
X-mProtect:  Fri, 21 Sep 2001 10:22:43 -0700 Nokia Silicon Valley Messaging Protection
Received: from vijayd.iprg.nokia.com (205.226.2.94, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpdrHprgw; Fri, 21 Sep 2001 10:22:41 PDT
Message-ID: <3BAB7762.1036960F@iprg.nokia.com>
Date: Fri, 21 Sep 2001 10:22:42 -0700
From: Vijay Devarapalli <vijayd@iprg.nokia.com>
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: mobile-ip@sunroof.eng.sun.com
CC: gdommety@cisco.com
Subject: Re: [mobile-ip] New BETH Draft
References: <200109211528.IAA28687@heliopolis.eng.sun.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

James Kempf wrote:
> 
> >you dont need such a thing for FMIPv6. if the MN does not respond
> >to the PrxyRtAdv, nothing happens. the oldAR does not start
> >forwarding packets to the newAR. the MN moves over to the newAR,
> >sends a router solicitation and gets a router advertisement.
> >
> 
> Sure. It's only one message but somehow it seems cleaner to not
> send it if you don't have to.
> 

somehow??? would you care to explain?

it beats having an extra bit in the router solicitation or in the
proxy router solicitation. and the network does not have to store
state which says this mobile node knows FMIPv6.

vijay



>                 jak


From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep 21 14:29:03 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA03989
	for <mobileip-archive@odin.ietf.org>; Fri, 21 Sep 2001 14:29:03 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id MAA05679;
	Fri, 21 Sep 2001 12:28:10 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id LAA26857;
	Fri, 21 Sep 2001 11:28:08 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8LIR67B018809
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 21 Sep 2001 11:27:07 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8LIR6Pf018808
	for mobile-ip-dist; Fri, 21 Sep 2001 11:27:06 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8LIR27B018801
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 21 Sep 2001 11:27:02 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id LAA13807;
	Fri, 21 Sep 2001 11:26:59 -0700 (PDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA02761;
	Fri, 21 Sep 2001 12:27:51 -0600 (MDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id LAA24396;
	Fri, 21 Sep 2001 11:26:58 -0700 (PDT)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f8LIQrB18105;
	Fri, 21 Sep 2001 11:26:53 -0700
X-mProtect:  Fri, 21 Sep 2001 11:26:53 -0700 Nokia Silicon Valley Messaging Protection
Received: from charliep.iprg.nokia.com (205.226.2.89, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpdLNkchU; Fri, 21 Sep 2001 11:26:51 PDT
Message-ID: <3BAB866C.39DA6B4A@iprg.nokia.com>
Date: Fri, 21 Sep 2001 11:26:52 -0700
From: "Charles E. Perkins" <charliep@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Alper Yegin <Alper.Yegin@eng.sun.com>, Marc Hasson <marc@mentat.com>,
        "Peter Grimstrup (TED)" <peter.grimstrup@ted.ericsson.dk>,
        Parijat <parijat@cwc.nus.edu.sg>
CC: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Mobile IPv6 draft revision
References: <200109101941.f8AJfB9n228598@jurassic.eng.sun.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hello folks,

<...still catching up!...>

Here is an attempt to summarize the discussion and formulate a solution
for the problems with deregistration vs. Binding Cache entries, when
attempting to deliver a Binding Acknowledgement resulting from an
authenticated deregistration (a Binding Update with zero lifetime).

- My quickie solution about disallowing zero-lifetime Binding Updates is
  unlikely to work, so should not be used.

- A zero-lifetime Binding Update is to be treated slightly differently
  than Binding Updates with nonzero lifetimes, insofar as the Binding
  Acknowledgement should not be handled by the usual rules for Binding
  Cache entries.  This is because the Binding Cache entry is likely to
  be already invalidated.  Marc's point about retransmission makes this
  point elegantly.

- The rule for handling zero-lifetime Binding Update is to be based
  on Marc's formulation:

             Just have the HA interpret the zero as the MN
     asking "please confirm via a BA using this BU's info
     that I'm no longer registered with you"? 

- The Care-of Address to be deregistered is located in the
  Alternate Care-of Address Sub-Option if that is present.
  Otherwise, it is located in the Source IP Address field of the
  IPv6 header of the packet containing the Binding Update.
  This is the same as has already been specified up until now.

- The Binding Acknowledgement is to be sent to the Mobile Node
  at the address in the Source IP address field of the Binding Update.
  If this is not the same as the Mobile Node's home address, then
  the Binding Acknowledgement is to be delivered using a Routing
  Header to the delivery address, _as if_ there were a Binding
  Cache entry associating the mobile node's specified delivery
  address with its home address.  This is the main point of
  difference with previous specification, and allows the mobile
  node to reliably turn off delivery of packets to its care-of
  addresses without having to be on the home network.


Please let me know if this makes good sense.

Regards,
Charlie P.


Alper Yegin wrote:
> 
> This issue was included in the Conenctathon 2001 list:
> 
>  [5] Deregistering a care-of address (section 8.5)
> 
>  The draft says that binding acknowledgement MUST be sent using a routing
>  header in the same way as any other packet sent to a mobile node using a
>  care-of address.
> 
>  BUT, what should be the care-of address used in the case this was a
>  deregistration? Draft should specify that it MUST be the care-of address
>  used in the triggering binding update. (similarly, draft already specifies
>  that for failed binding updates case).
> 
> MN should put wherever it wants to receive the BAck as the CoA in this
> de-registration BU.
> 
> alper
> 
> > X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to
> owner-mobile-ip@sunroof.eng.sun.com using -f
> > X-Accept-Language: en
> > MIME-Version: 1.0
> > To: mobile-ip@sunroof.eng.sun.com
> > Subject: Re: [mobile-ip] Mobile IPv6 draft revision
> > Content-Transfer-Encoding: 7bit
> > List-Archive: <http://playground.sun.com/mobile-ip/>
> > List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
> > List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
> > List-Unsubscribe:
> <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
> >
> > Comments inline
> >
> > Peter
> >
> > Parijat wrote:
> > >
> > > That does not answer the basic question that a BA might be addressed to a
> CoA
> > > which is no longer valid.
> > >
> >
> > Well, if a MN send the deregistration from a Care-of Address it does
> > not want to use (any more) asking for an acknowledgement, it should
> > reasonably stay there for some minimum of time. Leaving before the BA
> > is received is OK though, the MN may wish to retransmit the deregistration
> > from its new location - but with the interpretation from Marc Hassons mail
> > (7 sep, 18:31) that will be OK as well.
> >
> > > I would suggest that cache deletion requests come in with zero lifetimes,
> > > (perhaps even in case (a)?), and the acknowledgements to _deletion_ requests
> > > be sent to the home address of the mobile node.
> >
> > But maybe the MN just wants to stay away in privacy for some time for some
> > reason - that happens, I guess. I think Marc's proposal will work.
> >
> > >
> > > Of course, I am assuming that there is some need to keep a conceptual,
> > > specific difference between binding cache deletion requests and binding
> > > updates which merely have a very short lifetime.  It seems to be a neat
> thing
> > > to have a separate binding deletion message rather than one which is a
> > > degenerate case of a normal BU (okay, okay, zero lifetime BUs _are_
> > > degenerate cases of normal BUs, but you know what I mean).
> > >
> > Actually a nice idea, but...
> > > --
> > > Parijat Mishra
> > > R & D Engineer,
> > > Centre for Wireless Communications, NUS
> > > Tel: (65)8709353
> 
> alper


From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep 21 14:31:41 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04160
	for <mobileip-archive@odin.ietf.org>; Fri, 21 Sep 2001 14:31:41 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id MAA08118;
	Fri, 21 Sep 2001 12:30:49 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id LAA27716;
	Fri, 21 Sep 2001 11:30:39 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8LITT7B018829
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 21 Sep 2001 11:29:29 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8LITSg1018828
	for mobile-ip-dist; Fri, 21 Sep 2001 11:29:28 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from heliopolis.eng.sun.com (heliopolis.Eng.Sun.COM [152.70.1.39])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8LITP7B018821
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 21 Sep 2001 11:29:25 -0700 (PDT)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.eng.sun.com (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id LAA07445;
	Fri, 21 Sep 2001 11:29:23 -0700 (PDT)
Message-Id: <200109211829.LAA07445@heliopolis.eng.sun.com>
Date: Fri, 21 Sep 2001 11:29:22 -0700 (PDT)
From: James Kempf <James.Kempf@Sun.COM>
Subject: Re: [mobile-ip] New BETH Draft
To: mobile-ip@sunroof.eng.sun.com
Cc: gdommety@cisco.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: h1NHN6gIgiwRAQTf/UfhgA==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

>> >you dont need such a thing for FMIPv6. if the MN does not respond
>> >to the PrxyRtAdv, nothing happens. the oldAR does not start
>> >forwarding packets to the newAR. the MN moves over to the newAR,
>> >sends a router solicitation and gets a router advertisement.
>> >
>> 
>> Sure. It's only one message but somehow it seems cleaner to not
>> send it if you don't have to.
>> 
>
>somehow??? would you care to explain?
>
>it beats having an extra bit in the router solicitation or in the
>proxy router solicitation. and the network does not have to store
>state which says this mobile node knows FMIPv6.
>

You need to have a code for BETH for the router to tell the MN
that it is entering a BETH coverage area, and similarly
when it leaves. Why not do the same thing for FMIPv6?

		jak



From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep 21 15:12:36 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04851
	for <mobileip-archive@odin.ietf.org>; Fri, 21 Sep 2001 15:12:36 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id NAA10920;
	Fri, 21 Sep 2001 13:11:43 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id MAA07537;
	Fri, 21 Sep 2001 12:11:45 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8LJAk7B018969
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 21 Sep 2001 12:10:46 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8LJAknP018968
	for mobile-ip-dist; Fri, 21 Sep 2001 12:10:46 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8LJAg7B018961
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 21 Sep 2001 12:10:42 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id MAA00442
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 21 Sep 2001 12:10:40 -0700 (PDT)
Received: from sj-msg-core-3.cisco.com (sj-msg-core-3.cisco.com [171.70.157.152])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id NAA10019
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 21 Sep 2001 13:10:29 -0600 (MDT)
Received: from mira-sjcm-3.cisco.com (mira-sjcm-3.cisco.com [171.69.24.15])
	by sj-msg-core-3.cisco.com (8.11.3/8.9.1) with ESMTP id f8LJ7Zg09935;
	Fri, 21 Sep 2001 12:07:57 -0700 (PDT)
Received: from GDOMMETY-W2K2.cisco.com (dhcp-171-70-57-100.cisco.com [171.70.57.100])
	by mira-sjcm-3.cisco.com (Mirapoint)
	with ESMTP id AAX05262;
	Fri, 21 Sep 2001 12:09:34 -0700 (PDT)
Message-Id: <4.3.2.7.2.20010921120723.01f5d608@mira-sjcm-3.cisco.com>
X-Sender: gdommety@mira-sjcm-3.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 21 Sep 2001 12:12:48 -0700
To: mobile-ip@sunroof.eng.sun.com, mobile-ip@sunroof.eng.sun.com
From: Gopal Dommety <gdommety@cisco.com>
Subject: Re: [mobile-ip] IPv6 over Mobile IPv4
Cc: pcalhoun@diameter.org, tom.hiller@lucent.com
In-Reply-To: <15265.13715.831364.830180@nwsgpa.ih.lucent.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Pete, Pat, and Tom,

Good idea..... In the past, the LMA draft 
(draft-dommety-mobileip-lma-ipv6-02.txt) talked about doing similar thing.
  Following is an excerpt from the draft:


B)  Inter-network mechanism between  IPv6 and  IPv4: LMAs  provide the
option of  establishing either an  IPv6 tunnel or IPv4  tunnel between
the HA and LMA, depending  on the network.  This enables the operation
of Mobile IPv6 over the existing Internet, which is predominently IPv4
and will most likely evolve gradually to IPv6.

This was one of the three main motivations for LMA draft.

Thanks
Gopal


At 05:39 PM 9/13/2001 -0500, Pete McCann wrote:
>Hi,
>
>We (Pat Calhoun, Tom Hiller, and myself) recently wrote a draft
>describing a method for running IPv6 traffic while using Mobile IPv4
>signaling for mobility management and security.  We submitted it today
>to internet-drafts; you can find an advance copy at:
>
>http://www.diameter.org/draft-mccann-mobileip-ipv6mipv4-00.txt
>
>Basically, this could serve as an interim solution while we wait for
>all of the Mobile IPv6 security work to converge.  It would allow us
>to use the existing Mobile IPv4 security model, including AAA, for
>securing registration requests, while providing IPv6 service to
>dual-stack mobile nodes.  It may also help ease the overall transition
>to IPv6 because it only requires IPv6 support in the MN, FA, HA, and
>home network, while the network between the FA and HA could be a
>legacy IPv4 cloud.
>
>The draft itself is fairly straightforward; we would appreciate
>comments on the list and would like to see if there is interest in
>making this a working group item.
>
>-Pete



From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep 21 15:33:09 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA05141
	for <mobileip-archive@odin.ietf.org>; Fri, 21 Sep 2001 15:33:08 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA13857;
	Fri, 21 Sep 2001 12:32:10 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id MAA29388;
	Fri, 21 Sep 2001 12:31:46 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8LJTU7B019062
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 21 Sep 2001 12:29:30 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8LJTUf0019061
	for mobile-ip-dist; Fri, 21 Sep 2001 12:29:30 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8LJTP7B019054
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 21 Sep 2001 12:29:27 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id MAA11347
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 21 Sep 2001 12:29:24 -0700 (PDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id MAA29942
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 21 Sep 2001 12:29:24 -0700 (PDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id MAA29697
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 21 Sep 2001 12:29:24 -0700 (PDT)
X-Delivered-For: <mobile-ip@sunroof.eng.sun.com>
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f8LJTNP27561
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 21 Sep 2001 12:29:23 -0700
X-mProtect:  Fri, 21 Sep 2001 12:29:23 -0700 Nokia Silicon Valley Messaging Protection
Received: from charliep.iprg.nokia.com (205.226.2.89, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpdiEf3cW; Fri, 21 Sep 2001 12:29:21 PDT
Message-ID: <3BAB9511.26D0C24B@iprg.nokia.com>
Date: Fri, 21 Sep 2001 12:29:21 -0700
From: "Charles E. Perkins" <charliep@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: mobile-ip@sunroof.eng.sun.com
Subject: [mobile-ip] Text for how to deliver Binding Acknowledgements after deregistration
References: <200109101941.f8AJfB9n228598@jurassic.eng.sun.com> <3BAB866C.39DA6B4A@iprg.nokia.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hello folks,

Here's the new text in Section 8.5 which I have drawn up to fulfill the
requirements suggested by the previous discussion.  Even though the
reasoning was complicated, I think the actual result is pretty simple.

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

   The packet in which the Binding Acknowledgement is returned
   MUST meet the specific authentication requirements for Binding
   Acknowledgements, defined in Section 4.4.  Furthermore, if the packet
   is to be sent to the mobile node at any address other than the mobile
   node's home address, it MUST be sent using a Routing header (even if
   the binding was rejected).  The intermediate IP address, to which 
   the packet will be delivered immediately before the home address, is
   determined as follows: 
   
    -  Whenever the Binding Update is accepted with a nonzero lifetime,
       the routing header will be constructed using the care-of address
       as described in Section 8.9. 
   
    -  Otherwise, the routing header will be constructed using the 
       Source IP Address of the packet containing the Binding Update.

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

Suggestions for improved text are always appreciated.  My current plan is
to have the section related to Home Agent handling of deregistration to
just refer to this part of section 8.5, and to delete the (wrong) part
of section 5.2 which had mentioned use of the Routing Header.

Regards,
Charlie P.




"Charles E. Perkins" wrote:
> 
> Hello folks,
> 
> <...still catching up!...>
> 
> Here is an attempt to summarize the discussion and formulate a solution
> for the problems with deregistration vs. Binding Cache entries, when
> attempting to deliver a Binding Acknowledgement resulting from an
> authenticated deregistration (a Binding Update with zero lifetime).
> 
> - My quickie solution about disallowing zero-lifetime Binding Updates is
>   unlikely to work, so should not be used.
> 
> - A zero-lifetime Binding Update is to be treated slightly differently
>   than Binding Updates with nonzero lifetimes, insofar as the Binding
>   Acknowledgement should not be handled by the usual rules for Binding
>   Cache entries.  This is because the Binding Cache entry is likely to
>   be already invalidated.  Marc's point about retransmission makes this
>   point elegantly.
> 
> - The rule for handling zero-lifetime Binding Update is to be based
>   on Marc's formulation:
> 
>              Just have the HA interpret the zero as the MN
>      asking "please confirm via a BA using this BU's info
>      that I'm no longer registered with you"?
> 
> - The Care-of Address to be deregistered is located in the
>   Alternate Care-of Address Sub-Option if that is present.
>   Otherwise, it is located in the Source IP Address field of the
>   IPv6 header of the packet containing the Binding Update.
>   This is the same as has already been specified up until now.
> 
> - The Binding Acknowledgement is to be sent to the Mobile Node
>   at the address in the Source IP address field of the Binding Update.
>   If this is not the same as the Mobile Node's home address, then
>   the Binding Acknowledgement is to be delivered using a Routing
>   Header to the delivery address, _as if_ there were a Binding
>   Cache entry associating the mobile node's specified delivery
>   address with its home address.  This is the main point of
>   difference with previous specification, and allows the mobile
>   node to reliably turn off delivery of packets to its care-of
>   addresses without having to be on the home network.
> 
> Please let me know if this makes good sense.
> 
> Regards,
> Charlie P.
> 
> Alper Yegin wrote:
> >
> > This issue was included in the Conenctathon 2001 list:
> >
> >  [5] Deregistering a care-of address (section 8.5)
> >
> >  The draft says that binding acknowledgement MUST be sent using a routing
> >  header in the same way as any other packet sent to a mobile node using a
> >  care-of address.
> >
> >  BUT, what should be the care-of address used in the case this was a
> >  deregistration? Draft should specify that it MUST be the care-of address
> >  used in the triggering binding update. (similarly, draft already specifies
> >  that for failed binding updates case).
> >
> > MN should put wherever it wants to receive the BAck as the CoA in this
> > de-registration BU.
> >
> > alper
> >
> > > X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to
> > owner-mobile-ip@sunroof.eng.sun.com using -f
> > > X-Accept-Language: en
> > > MIME-Version: 1.0
> > > To: mobile-ip@sunroof.eng.sun.com
> > > Subject: Re: [mobile-ip] Mobile IPv6 draft revision
> > > Content-Transfer-Encoding: 7bit
> > > List-Archive: <http://playground.sun.com/mobile-ip/>
> > > List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
> > > List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
> > > List-Unsubscribe:
> > <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
> > >
> > > Comments inline
> > >
> > > Peter
> > >
> > > Parijat wrote:
> > > >
> > > > That does not answer the basic question that a BA might be addressed to a
> > CoA
> > > > which is no longer valid.
> > > >
> > >
> > > Well, if a MN send the deregistration from a Care-of Address it does
> > > not want to use (any more) asking for an acknowledgement, it should
> > > reasonably stay there for some minimum of time. Leaving before the BA
> > > is received is OK though, the MN may wish to retransmit the deregistration
> > > from its new location - but with the interpretation from Marc Hassons mail
> > > (7 sep, 18:31) that will be OK as well.
> > >
> > > > I would suggest that cache deletion requests come in with zero lifetimes,
> > > > (perhaps even in case (a)?), and the acknowledgements to _deletion_ requests
> > > > be sent to the home address of the mobile node.
> > >
> > > But maybe the MN just wants to stay away in privacy for some time for some
> > > reason - that happens, I guess. I think Marc's proposal will work.
> > >
> > > >
> > > > Of course, I am assuming that there is some need to keep a conceptual,
> > > > specific difference between binding cache deletion requests and binding
> > > > updates which merely have a very short lifetime.  It seems to be a neat
> > thing
> > > > to have a separate binding deletion message rather than one which is a
> > > > degenerate case of a normal BU (okay, okay, zero lifetime BUs _are_
> > > > degenerate cases of normal BUs, but you know what I mean).
> > > >
> > > Actually a nice idea, but...
> > > > --
> > > > Parijat Mishra
> > > > R & D Engineer,
> > > > Centre for Wireless Communications, NUS
> > > > Tel: (65)8709353
> >
> > alper


From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep 21 16:55:24 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA06489
	for <mobileip-archive@odin.ietf.org>; Fri, 21 Sep 2001 16:55:24 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA16976;
	Fri, 21 Sep 2001 13:54:37 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id NAA00972;
	Fri, 21 Sep 2001 13:54:24 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8LKrM7B019178
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 21 Sep 2001 13:53:22 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8LKrLPZ019177
	for mobile-ip-dist; Fri, 21 Sep 2001 13:53:21 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8LKrG7B019170
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 21 Sep 2001 13:53:18 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id NAA24257;
	Fri, 21 Sep 2001 13:53:16 -0700 (PDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id OAA24499;
	Fri, 21 Sep 2001 14:53:04 -0600 (MDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id NAA05515;
	Fri, 21 Sep 2001 13:53:15 -0700 (PDT)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f8LKrEK25520;
	Fri, 21 Sep 2001 13:53:14 -0700
X-mProtect:  Fri, 21 Sep 2001 13:53:14 -0700 Nokia Silicon Valley Messaging Protection
Received: from charliep.iprg.nokia.com (205.226.2.89, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpdvRaT9T; Fri, 21 Sep 2001 13:53:12 PDT
Message-ID: <3BABA8B8.2D75B331@iprg.nokia.com>
Date: Fri, 21 Sep 2001 13:53:12 -0700
From: "Charles E. Perkins" <charliep@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Alper Yegin <Alper.Yegin@eng.sun.com>
CC: mobile-ip@sunroof.eng.sun.com
Subject: [mobile-ip] Re: Connectathon input for Mobile IPv6 draft revision
References: <200108240031.f7O0VZS8652749@jurassic.eng.sun.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hello Alper,

Alper Yegin wrote:
> 
> I assume the "Connectathon 2001 feedback on the Mobile IPv6 draft" will
> also be incorporated into this upcoming version. Right? I attached the
> original e-mail that details the issues which were both presented at IETF
> 50 and sent on the mailing list before. 

Thanks, Alper.  As noted, I am finally trying to catch up on this...

>From your earlier note (slightly reformatted to fit my screen better):

> Here's a recapture of Mobile IPv6 spec issues, for those who weren't at
> the IETF meeting (in case they have comments), and for the Mobile IPv6
> draft authors to incorporate these into the next revision of the draft. 


> [1] Movement detection (section 10.4)
> 
>                                                     ... Instead,
>    a mobile node SHOULD consider receipt of any IPv6 packets from its
>    current default router as an indication that it is still reachable
>    from the router.  Both packets from the router's IP address and
>    (IPv6) packets from its link-layer address (e.g., those forwarded but
>    not originated by the router) SHOULD be considered.
> 
> Draft suggests that receiving packets from a node with same link-layer
> address and IP address as current default router means that mobile node
> is still attached to the same link.
> 
> BUT, different interfaces of the same router can have the same MAC
> address, therefore same link-local address but advertise different
> prefixes. In this case, mobile node would fail to detect movement if
> it only looks at the source MAC and IP address of packets.
> 
> Therefore draft should not suggest a match on source MAC address and
> IP address is sufficient.

Here, the important thing seems to be that the mobile node is
still reachable from the router.  Other problems would presumably
be resolved by way of Neighbor Discovery (not Mobile IPv6), and
so should not be specified again within Mobile IPv6.  Here is the
current relevant text:

    Instead, when a mobile node receives any IPv6 packets from its
    current default router at all, irrespective of the source IPv6
    address, it SHOULD use that as an indication that 
    it is still reachable from the router.

Is this O.K.?


> [2] Sending binding acknowledgement for failed binding updates (section 5.2)
> 
>    Rather, the care-of address used by this node in
>    sending the packet containing the Binding Acknowledgement MUST be
>    copied from the care-of address received in the rejected Binding
>    Update; ...
> 
> Draft says receiving node MUST send a binding acknowledgement for
> failed binding updates. It also says the care-of address MUST be
> copied from the failed binding update.
> 
> BUT in the case care-of address is an invalid address such as multicast
> or unspecified address, such an address should not be used as the
> care-of address in binding acknowledgement.
> 
> Draft can be updated to say:
> - If we have received this binding update as a home agent, we MUST not
>   send a binding acknowledgement
> - If we have received this binding update as a correspondent node, we MUST
>   send the binding acknowledgement to home address (or not send at all?)

This requires further revision to the last text I sent out about
deregistering care-of addresses:

    -  Otherwise, if the Source IP Address of the packet containing
       the Binding Update, is legal for inclusion in a Routing Header,
       the routing header will be constructed using that IP address.
       Note that multicast addresses, link-local addresses, and the
       unspecified address, MUST NOT be used within a Routing Header for
       the Binding Acknowledgement.

    -  Otherwise, if the Binding Update has a zero lifetime but the
       Source IP address is not allowable for use within the Routing
       Header, the Binding Acknowledgment MUST be sent to the mobile
       node's home address

I also inserted the following prohibition within section 5.1:

    In any case, the care-of address MUST NOT be any IPv6 address
    which is prohibited for use within a Routing Header; thus
    multicast addresses, the unspecified address, loop-back address,
    and link-local addresses are excluded.  Binding Updates indicating
    any such excluded care-of address MUST be silently discarded.



> [3] Home agent address discovery request message (section 5.6)
> 
> Home Agent Address Discovery Request Message includes the Home Address
> field.  This information is used by the receiving home agent to return
> the list of home agents matching the prefix of the mobile node.
> 
> This request packet is sent to "Mobile IPv6 Home-Agents" anycast address
> for its own home subnet prefix.
> 
> The receiving home agent can figure out the prefix of the mobile node
> just by looking at the destination address of the request packet.
> Therefore Home Address field in the request message is not needed in
> the draft. 

I didn't see any discussion about this.  And, as best I can tell,
you are correct in your assertion, because a home agent couldn't
respond to the "Mobile IPv6 Home-Agents" anycast address without
knowing the routing prefix for that anycast address.  So, I've
deleted that field.  This also removes the need to say anything
about what happens if the mobile node doesn't have a home address.

Once the Home Address field is gone, the alignment requirement
for ICMPv6 messages is is (I think) different, so I reduced the
Reserved field to only 16 bits.

Furthermore, I don't see any reason to restrict the inclusion
of a Home Address option.  Such a thing might be handy if, in
the future, we can devise a security association with an anycast
group.  Besides that, it might be the case that home agent
discovery is initiated when the mobile node has a perfectly
valid care-of address for one of its other home addresses,
so some of the other wording in the relevant section has been
changed.

Lastly, if it is decided that this ICMPv6 message can also be
used by the mobile node to request a home address, that can
be done by using a bit from the Reserved field, but I reckon
that is something we can defer for a long time.


> [4] ICMPs can delete binding cache (section 8.8)
> 
>                                          If the correspondent node
>    receives persistent ICMP Destination Unreachable messages after
>    sending packets to a mobile node based on an entry in its Binding
>    Cache, the correspondent node SHOULD delete this Binding Cache
>    entry.
> 
> The only way binding cache entries can be deleted is through binding
> updates and persistent ICMP unreachables. The former is required to be
> authenticated, but not the latter. The draft should have a proper
> warning about this, as unauthenticated ICMP messages can be used
> for DoS attacks.

O.K.  I have borrowed your wording as part of a statement to this effect
in the Security Considerations:

    The only way binding cache entries can be deleted is through Binding  
    Updates and persistent ICMP unreachables messages.  The former are
    required to be authenticated, but not the latter.  Therefore,
    unauthenticated ICMP messages can unfortunately be used 
    for DoS attacks.   However, the security exposure is limited,
    since the effect would be only to cause packets for the mobile
    node to be sent by way of the mobile node's home network.


> [5] Deregistering a care-of address (section 8.5)
> 
> The draft says that binding acknowledgement MUST be sent using a
> routing header in the same way as any other packet sent to a mobile
> node using a care-of address.
> 
> BUT, what should be the care-of address used in the case this was a
> deregistration? Draft should specify that it MUST be the care-of
> address used in the triggering binding update. (similarly, draft
> already specifies that for failed binding updates case).

According to recent discussion, I hope this problem has been fixed.



Regards,
Charlie P.


From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep 21 18:18:32 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07567
	for <mobileip-archive@odin.ietf.org>; Fri, 21 Sep 2001 18:18:32 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id PAA20367;
	Fri, 21 Sep 2001 15:17:47 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id PAA01329;
	Fri, 21 Sep 2001 15:17:32 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8LMG77B019329
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 21 Sep 2001 15:16:08 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8LMG7mO019328
	for mobile-ip-dist; Fri, 21 Sep 2001 15:16:07 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from jurassic.eng.sun.com (jurassic [129.146.86.38] (may be forged))
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8LMG07B019319
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 21 Sep 2001 15:16:00 -0700 (PDT)
Received: from istanbul.Eng.Sun.COM (istanbul.Eng.Sun.COM [129.146.86.247])
	by jurassic.eng.sun.com (8.12.0+Sun/8.12.0) with SMTP id f8LMFwVj938098;
	Fri, 21 Sep 2001 15:15:58 -0700 (PDT)
Message-Id: <200109212215.f8LMFwVj938098@jurassic.eng.sun.com>
Date: Fri, 21 Sep 2001 15:15:45 -0700 (PDT)
From: Alper Yegin <Alper.Yegin@eng.sun.com>
Subject: Re: [mobile-ip] Mobile IPv6 draft revision
To: marc@mentat.com, peter.grimstrup@ted.ericsson.dk, parijat@cwc.nus.edu.sg,
        mobile-ip@sunroof.eng.sun.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: SAF6i+KACTIp53tt+Whwcg==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4_37 SunOS 5.8.1 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Charlie,

This looks good. One point tough:

> - The Binding Acknowledgement is to be sent to the Mobile Node
>   at the address in the Source IP address field of the Binding Update.

This packet should be sent to care-of address, right? Not necessarily the source 
address of the incoming BU. Care-of address would be different than the source 
address of BU if there's a alternate care-of address option.


>   If this is not the same as the Mobile Node's home address, then
>   the Binding Acknowledgement is to be delivered using a Routing
>   Header to the delivery address, _as if_ there were a Binding
>   Cache entry associating the mobile node's specified delivery
>   address with its home address.  This is the main point of
>   difference with previous specification, and allows the mobile
>   node to reliably turn off delivery of packets to its care-of
>   addresses without having to be on the home network.


Thanks Charlie!

alper



From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep 21 18:34:36 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07794
	for <mobileip-archive@odin.ietf.org>; Fri, 21 Sep 2001 18:34:35 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id QAA07004;
	Fri, 21 Sep 2001 16:33:43 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id PAA05163;
	Fri, 21 Sep 2001 15:33:45 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8LMWM7B019473
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 21 Sep 2001 15:32:22 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8LMWMxx019472
	for mobile-ip-dist; Fri, 21 Sep 2001 15:32:22 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from jurassic.eng.sun.com (jurassic [129.146.86.38] (may be forged))
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8LMWI7B019465
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 21 Sep 2001 15:32:19 -0700 (PDT)
Received: from istanbul.Eng.Sun.COM (istanbul.Eng.Sun.COM [129.146.86.247])
	by jurassic.eng.sun.com (8.12.0+Sun/8.12.0) with SMTP id f8LMWHVj944318
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 21 Sep 2001 15:32:17 -0700 (PDT)
Message-Id: <200109212232.f8LMWHVj944318@jurassic.eng.sun.com>
Date: Fri, 21 Sep 2001 15:32:04 -0700 (PDT)
From: Alper Yegin <Alper.Yegin@eng.sun.com>
Subject: Re: [mobile-ip] Re: Connectathon input for Mobile IPv6 draft revision
To: mobile-ip@sunroof.eng.sun.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: eI6erN4e9mRnRjkRpH/C4Q==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4_37 SunOS 5.8.1 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Hi Charlie,


> > [1] Movement detection (section 10.4)
> > 
> >                                                     ... Instead,
> >    a mobile node SHOULD consider receipt of any IPv6 packets from its
> >    current default router as an indication that it is still reachable
> >    from the router.  Both packets from the router's IP address and
> >    (IPv6) packets from its link-layer address (e.g., those forwarded but
> >    not originated by the router) SHOULD be considered.
> > 
> > Draft suggests that receiving packets from a node with same link-layer
> > address and IP address as current default router means that mobile node
> > is still attached to the same link.
> > 
> > BUT, different interfaces of the same router can have the same MAC
> > address, therefore same link-local address but advertise different
> > prefixes. In this case, mobile node would fail to detect movement if
> > it only looks at the source MAC and IP address of packets.
> > 
> > Therefore draft should not suggest a match on source MAC address and
> > IP address is sufficient.
> 
> Here, the important thing seems to be that the mobile node is
> still reachable from the router.  Other problems would presumably

Actually it is not reachable. MN is just attached to another link on the AR. The 
packets coming from the AR can have the same MAC address (a legal choice and a 
feature on some platforms) and the same source IP address (link local address 
derived from the same MAC address). But MN is not "reachable", because it's 
using a prefix from another link, not the current link.


> be resolved by way of Neighbor Discovery (not Mobile IPv6), and
> so should not be specified again within Mobile IPv6.  Here is the
> current relevant text:
> 
>     Instead, when a mobile node receives any IPv6 packets from its
>     current default router at all, irrespective of the source IPv6
>     address, it SHOULD use that as an indication that 
>     it is still reachable from the router.

That doesn't work, as I explained above. Only if the same prefix is advertised 
on this link, then MN can conclude it's reachable.

So, I suggest we remove the text in the draft that suggests checking source IP 
address and MAC address is sufficient.


> 
> Is this O.K.?
> 
> 
> > [2] Sending binding acknowledgement for failed binding updates (section 5.2)
> > 
> >    Rather, the care-of address used by this node in
> >    sending the packet containing the Binding Acknowledgement MUST be
> >    copied from the care-of address received in the rejected Binding
> >    Update; ...
> > 
> > Draft says receiving node MUST send a binding acknowledgement for
> > failed binding updates. It also says the care-of address MUST be
> > copied from the failed binding update.
> > 
> > BUT in the case care-of address is an invalid address such as multicast
> > or unspecified address, such an address should not be used as the
> > care-of address in binding acknowledgement.
> > 
> > Draft can be updated to say:
> > - If we have received this binding update as a home agent, we MUST not
> >   send a binding acknowledgement
> > - If we have received this binding update as a correspondent node, we MUST
> >   send the binding acknowledgement to home address (or not send at all?)
> 
> This requires further revision to the last text I sent out about
> deregistering care-of addresses:
> 
>     -  Otherwise, if the Source IP Address of the packet containing
>        the Binding Update, is legal for inclusion in a Routing Header,
>        the routing header will be constructed using that IP address.
>        Note that multicast addresses, link-local addresses, and the
>        unspecified address, MUST NOT be used within a Routing Header for
>        the Binding Acknowledgement.
> 
>     -  Otherwise, if the Binding Update has a zero lifetime but the
>        Source IP address is not allowable for use within the Routing
>        Header, the Binding Acknowledgment MUST be sent to the mobile
>        node's home address
> 
> I also inserted the following prohibition within section 5.1:
> 
>     In any case, the care-of address MUST NOT be any IPv6 address
>     which is prohibited for use within a Routing Header; thus
>     multicast addresses, the unspecified address, loop-back address,
>     and link-local addresses are excluded.  Binding Updates indicating
>     any such excluded care-of address MUST be silently discarded.
> 

Looks good to me.

> 
> 
> > [3] Home agent address discovery request message (section 5.6)
> > 
> > Home Agent Address Discovery Request Message includes the Home Address
> > field.  This information is used by the receiving home agent to return
> > the list of home agents matching the prefix of the mobile node.
> > 
> > This request packet is sent to "Mobile IPv6 Home-Agents" anycast address
> > for its own home subnet prefix.
> > 
> > The receiving home agent can figure out the prefix of the mobile node
> > just by looking at the destination address of the request packet.
> > Therefore Home Address field in the request message is not needed in
> > the draft. 
> 
> I didn't see any discussion about this.  And, as best I can tell,
> you are correct in your assertion, because a home agent couldn't
> respond to the "Mobile IPv6 Home-Agents" anycast address without
> knowing the routing prefix for that anycast address.  So, I've
> deleted that field.  This also removes the need to say anything
> about what happens if the mobile node doesn't have a home address.
> 
> Once the Home Address field is gone, the alignment requirement
> for ICMPv6 messages is is (I think) different, so I reduced the
> Reserved field to only 16 bits.
> 
> Furthermore, I don't see any reason to restrict the inclusion
> of a Home Address option.  Such a thing might be handy if, in
> the future, we can devise a security association with an anycast
> group.  Besides that, it might be the case that home agent
> discovery is initiated when the mobile node has a perfectly
> valid care-of address for one of its other home addresses,
> so some of the other wording in the relevant section has been
> changed.
> 
> Lastly, if it is decided that this ICMPv6 message can also be
> used by the mobile node to request a home address, that can
> be done by using a bit from the Reserved field, but I reckon
> that is something we can defer for a long time.
> 


Sounds good.

> 
> > [4] ICMPs can delete binding cache (section 8.8)
> > 
> >                                          If the correspondent node
> >    receives persistent ICMP Destination Unreachable messages after
> >    sending packets to a mobile node based on an entry in its Binding
> >    Cache, the correspondent node SHOULD delete this Binding Cache
> >    entry.
> > 
> > The only way binding cache entries can be deleted is through binding
> > updates and persistent ICMP unreachables. The former is required to be
> > authenticated, but not the latter. The draft should have a proper
> > warning about this, as unauthenticated ICMP messages can be used
> > for DoS attacks.
> 
> O.K.  I have borrowed your wording as part of a statement to this effect
> in the Security Considerations:
> 
>     The only way binding cache entries can be deleted is through Binding  
>     Updates and persistent ICMP unreachables messages.  The former are
>     required to be authenticated, but not the latter.  Therefore,
>     unauthenticated ICMP messages can unfortunately be used 
>     for DoS attacks.   However, the security exposure is limited,
>     since the effect would be only to cause packets for the mobile
>     node to be sent by way of the mobile node's home network.
> 


Looks good.

> 
> > [5] Deregistering a care-of address (section 8.5)
> > 
> > The draft says that binding acknowledgement MUST be sent using a
> > routing header in the same way as any other packet sent to a mobile
> > node using a care-of address.
> > 
> > BUT, what should be the care-of address used in the case this was a
> > deregistration? Draft should specify that it MUST be the care-of
> > address used in the triggering binding update. (similarly, draft
> > already specifies that for failed binding updates case).
> 
> According to recent discussion, I hope this problem has been fixed.
> 

Yes, except the care-of address vs. source address issue I pointed out.


> Regards,
> Charlie P.

Thanks Charlie.

alper



From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep 21 19:31:42 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08213
	for <mobileip-archive@odin.ietf.org>; Fri, 21 Sep 2001 19:31:42 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id QAA13578;
	Fri, 21 Sep 2001 16:30:51 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id QAA02115;
	Fri, 21 Sep 2001 16:30:40 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8LNTU7B019595
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 21 Sep 2001 16:29:30 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8LNTU5m019594
	for mobile-ip-dist; Fri, 21 Sep 2001 16:29:30 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8LNTP7B019587
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 21 Sep 2001 16:29:27 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id QAA07489
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 21 Sep 2001 16:29:24 -0700 (PDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id QAA08396
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 21 Sep 2001 16:29:24 -0700 (PDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id QAA16348;
	Fri, 21 Sep 2001 16:29:17 -0700 (PDT)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f8LNTGL12201;
	Fri, 21 Sep 2001 16:29:16 -0700
X-mProtect:  Fri, 21 Sep 2001 16:29:16 -0700 Nokia Silicon Valley Messaging Protection
Received: from vijayd.iprg.nokia.com (205.226.2.94, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpdeCfXI5; Fri, 21 Sep 2001 16:29:14 PDT
Message-ID: <3BABCD4B.FAE7450@iprg.nokia.com>
Date: Fri, 21 Sep 2001 16:29:15 -0700
From: Vijay Devarapalli <vijayd@iprg.nokia.com>
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: mobile-ip@sunroof.eng.sun.com
CC: gdommety@cisco.com
Subject: Re: [mobile-ip] New BETH Draft
References: <200109211829.LAA07445@heliopolis.eng.sun.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

James Kempf wrote:

> 
> You need to have a code for BETH for the router to tell the MN
> that it is entering a BETH coverage area, and similarly
> when it leaves. Why not do the same thing for FMIPv6?


BETH needs it because the Mobile node is not involved when the
OldAR descides to start forwarding packets to the NewAR. In
FMIPv6, OldAR does not do this until it gets an indication
from the MN. Therefore FMIPv6 does not need it....

vijay

> 
>                 jak


From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep 21 19:32:12 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08238
	for <mobileip-archive@odin.ietf.org>; Fri, 21 Sep 2001 19:32:11 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id RAA11204;
	Fri, 21 Sep 2001 17:31:17 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id QAA02301;
	Fri, 21 Sep 2001 16:31:21 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8LNUT7B019612
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 21 Sep 2001 16:30:29 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8LNUTOu019611
	for mobile-ip-dist; Fri, 21 Sep 2001 16:30:29 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8LNUP7B019604
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 21 Sep 2001 16:30:25 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id QAA24925;
	Fri, 21 Sep 2001 16:30:24 -0700 (PDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id QAA08693;
	Fri, 21 Sep 2001 16:30:24 -0700 (PDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id QAA16420;
	Fri, 21 Sep 2001 16:30:23 -0700 (PDT)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f8LNUNp14397;
	Fri, 21 Sep 2001 16:30:23 -0700
X-mProtect:  Fri, 21 Sep 2001 16:30:23 -0700 Nokia Silicon Valley Messaging Protection
Received: from Icharliep-1.iprg.nokia.com (205.226.22.18, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpdmAn1fO; Fri, 21 Sep 2001 16:30:21 PDT
Message-ID: <3BABCD92.AC211520@iprg.nokia.com>
Date: Fri, 21 Sep 2001 16:30:26 -0700
From: Charlie Perkins <charliep@iprg.nokia.com>
Organization: Nokia
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Alper Yegin <Alper.Yegin@eng.sun.com>
CC: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Mobile IPv6 draft revision
References: <200109212215.f8LMFwVj938098@jurassic.eng.sun.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hello Alper,

> > - The Binding Acknowledgement is to be sent to the Mobile Node
> >   at the address in the Source IP address field of the Binding Update.
>
> This packet should be sent to care-of address, right? Not necessarily the source
> address of the incoming BU. Care-of address would be different than the source
> address of BU if there's a alternate care-of address option.

I thought the purpose of using the alternate care-of address
was to deregister a care-of address at which the mobile node
no longer had connectivity.  If this is true, then it makes more
sense to use the source address of the packet containing the
Binding Update, I think.

> alper

Regards,
Charlie P.





From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep 21 19:37:00 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08279
	for <mobileip-archive@odin.ietf.org>; Fri, 21 Sep 2001 19:37:00 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id RAA13640;
	Fri, 21 Sep 2001 17:36:06 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id QAA03622;
	Fri, 21 Sep 2001 16:36:11 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8LNZR7B019725
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 21 Sep 2001 16:35:27 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8LNZRO1019724
	for mobile-ip-dist; Fri, 21 Sep 2001 16:35:27 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from heliopolis.eng.sun.com (redhook.Eng.Sun.COM [152.70.24.37])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8LNZN7B019717
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 21 Sep 2001 16:35:23 -0700 (PDT)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.eng.sun.com (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id QAA23836;
	Fri, 21 Sep 2001 16:35:22 -0700 (PDT)
Message-Id: <200109212335.QAA23836@heliopolis.eng.sun.com>
Date: Fri, 21 Sep 2001 16:35:21 -0700 (PDT)
From: James Kempf <James.Kempf@Sun.COM>
Subject: [mobile-ip] Optimizing Movement Detection on the AR
To: charliep@iprg.nokia.com
Cc: mobile-ip@sunroof.eng.sun.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: O8PJCRNQfm1rd6jAE5GTIw==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Hi Charlie,

In the discussion of handover optimization for IPv6, the following point
came up. 

In standard MIPv6 handover, draft-ietf-mobile-ipv6-14.txt has a 
section on movement detection that encourages the MN to perform
optimization if it can (Section 10, first few paragraphs), i.e. to
solicit a Router Advert if it has evidence that it is on a new link. However,
Section 6.5 only allows the AR to increase the frequency of multicast
Router Adverts, not to use any link information to explicitly
signal the MN. 

Would it be possible to add some text to Section 6.5 that allows
the AR to unicast a Router Advert to the MN if the AR detects that the MN
has arrived on its link? Alternatively, if unicast isn't acceptable,
the AR could be encouraged to multicast when it detected a new MN
on the link, rather than wait for the next period.

This is needed to allow a graceful transition from a coverage area
where FMIPv6 is supported to one where it isn't, in the case where
the network but not the mobile node gets some kind of notification
that the new link is up.

		jak



From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep 21 19:45:54 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08374
	for <mobileip-archive@odin.ietf.org>; Fri, 21 Sep 2001 19:45:53 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id RAA17974;
	Fri, 21 Sep 2001 17:45:00 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id QAA05122;
	Fri, 21 Sep 2001 16:45:04 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8LNiD7B019794
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 21 Sep 2001 16:44:13 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8LNiC5m019793
	for mobile-ip-dist; Fri, 21 Sep 2001 16:44:12 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from heliopolis.eng.sun.com (redcoast.Eng.Sun.COM [152.70.28.21])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8LNi87B019786
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 21 Sep 2001 16:44:09 -0700 (PDT)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.eng.sun.com (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id QAA24211;
	Fri, 21 Sep 2001 16:44:08 -0700 (PDT)
Message-Id: <200109212344.QAA24211@heliopolis.eng.sun.com>
Date: Fri, 21 Sep 2001 16:44:07 -0700 (PDT)
From: James Kempf <James.Kempf@Sun.COM>
Subject: Re: [mobile-ip] New BETH Draft
To: mobile-ip@sunroof.eng.sun.com
Cc: gdommety@cisco.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: 0GTG3y8w82sf5EFFglo/jQ==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Vijay,


>> 
>> You need to have a code for BETH for the router to tell the MN
>> that it is entering a BETH coverage area, and similarly
>> when it leaves. Why not do the same thing for FMIPv6?
>
>
>BETH needs it because the Mobile node is not involved when the
>OldAR descides to start forwarding packets to the NewAR. In
>FMIPv6, OldAR does not do this until it gets an indication
>from the MN. Therefore FMIPv6 does not need it....
>

The issue here is not when both the MN and the AR support FMIPv6,
it is when the MN doesn't but the AR does. If the AR doesn't know
that, then it could send a PrRtAdv which would be
ignored by the MN. Since not all radio spectrum is free, it 
seems appropriate to take reasonable measures to reduce the
amount of unneeded signalling over the air. I sometimes feel
like I am harping on this theme too much, but I believe the point bears
re-emphasizing: for some radio protocols, spectrum is very expensive.
I think it is entirely reonable to add such a code, since the
AR and the MN need to tell each other what their handover
capabilities are for BETH anyway. Adding an additional code
during the initial Router Advert Solicitation/Router Advert exchange
doesn't seem like such a big deal, if it saves an unneeded message
during every handover.

		jak



From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep 21 19:54:51 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08435
	for <mobileip-archive@odin.ietf.org>; Fri, 21 Sep 2001 19:54:51 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id RAA22603;
	Fri, 21 Sep 2001 17:53:58 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id QAA07243;
	Fri, 21 Sep 2001 16:54:03 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8LNrQ7B019874
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 21 Sep 2001 16:53:26 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8LNrQEe019873
	for mobile-ip-dist; Fri, 21 Sep 2001 16:53:26 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8LNrM7B019866
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 21 Sep 2001 16:53:23 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id QAA12015;
	Fri, 21 Sep 2001 16:53:22 -0700 (PDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id QAA15919;
	Fri, 21 Sep 2001 16:53:21 -0700 (PDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id QAA17917;
	Fri, 21 Sep 2001 16:53:21 -0700 (PDT)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f8LNrKi23198;
	Fri, 21 Sep 2001 16:53:20 -0700
X-mProtect:  Fri, 21 Sep 2001 16:53:20 -0700 Nokia Silicon Valley Messaging Protection
Received: from Icharliep-1.iprg.nokia.com (205.226.22.18, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpdA9zE4V; Fri, 21 Sep 2001 16:53:18 PDT
Message-ID: <3BABD2ED.3ED6D615@iprg.nokia.com>
Date: Fri, 21 Sep 2001 16:53:17 -0700
From: Charlie Perkins <charliep@iprg.nokia.com>
Organization: Nokia
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Alper Yegin <Alper.Yegin@eng.sun.com>
CC: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Re: Connectathon input for Mobile IPv6 draft revision
References: <200109212232.f8LMWHVj944318@jurassic.eng.sun.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hello again Alper,

Alper Yegin wrote:

> > > BUT, different interfaces of the same router can have the same MAC
> > > address, therefore same link-local address but advertise different
> > > prefixes. In this case, mobile node would fail to detect movement if
> > > it only looks at the source MAC and IP address of packets.
> > >
> > > Therefore draft should not suggest a match on source MAC address and
> > > IP address is sufficient.
> >
> > Here, the important thing seems to be that the mobile node is
> > still reachable from the router.  Other problems would presumably
>
> Actually it is not reachable. MN is just attached to another link on the AR. The
> packets coming from the AR can have the same MAC address (a legal choice and a
> feature on some platforms) and the same source IP address (link local address
> derived from the same MAC address). But MN is not "reachable", because it's
> using a prefix from another link, not the current link.

Maybe it would be enough to say that the mobile node should use the
lack of continued advertisement of a particular prefix as evidence that
it is no longer connected to the interface which had advertised that
prefix.

> > be resolved by way of Neighbor Discovery (not Mobile IPv6), and
> > so should not be specified again within Mobile IPv6.  Here is the
> > current relevant text:
> >
> >     Instead, when a mobile node receives any IPv6 packets from its
> >     current default router at all, irrespective of the source IPv6
> >     address, it SHOULD use that as an indication that
> >     it is still reachable from the router.
>
> That doesn't work, as I explained above. Only if the same prefix is advertised
> on this link, then MN can conclude it's reachable.
>
> So, I suggest we remove the text in the draft that suggests checking source IP
> address and MAC address is sufficient.

Can you be more specific about which text you would like to see removed?

Regards,
Charlie P.




From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep 21 23:32:45 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA12590
	for <mobileip-archive@odin.ietf.org>; Fri, 21 Sep 2001 23:32:44 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id VAA29083;
	Fri, 21 Sep 2001 21:31:52 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id UAA11219;
	Fri, 21 Sep 2001 20:31:54 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8M3Uv7B020170
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 21 Sep 2001 20:30:57 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8M3Uu0L020169
	for mobile-ip-dist; Fri, 21 Sep 2001 20:30:56 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8M3Uq7B020162
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 21 Sep 2001 20:30:53 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id UAA19466
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 21 Sep 2001 20:30:51 -0700 (PDT)
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by patan.sun.com (8.9.3+Sun/8.9.3) with SMTP id VAA28762
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 21 Sep 2001 21:30:40 -0600 (MDT)
Received: (qmail 950 invoked by uid 500); 22 Sep 2001 03:17:06 -0000
Date: Fri, 21 Sep 2001 20:17:05 -0700
From: Pat Calhoun <pcalhoun@diameter.org>
To: Gopal Dommety <gdommety@cisco.com>
Cc: mobile-ip@sunroof.eng.sun.com, pcalhoun@diameter.org,
        tom.hiller@lucent.com
Subject: Re: [mobile-ip] IPv6 over Mobile IPv4
Message-ID: <20010921201705.A940@charizard.diameter.org>
References: <15265.13715.831364.830180@nwsgpa.ih.lucent.com> <4.3.2.7.2.20010921120723.01f5d608@mira-sjcm-3.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <4.3.2.7.2.20010921120723.01f5d608@mira-sjcm-3.cisco.com>; from gdommety@cisco.com on Fri, Sep 21, 2001 at 12:12:48PM -0700
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

On Fri, Sep 21, 2001 at 12:12:48PM -0700, Gopal Dommety wrote:
> 
> Pete, Pat, and Tom,
> 
> Good idea..... In the past, the LMA draft 
> (draft-dommety-mobileip-lma-ipv6-02.txt) talked about doing similar thing.
>   Following is an excerpt from the draft:
> 
> 
> B)  Inter-network mechanism between  IPv6 and  IPv4: LMAs  provide the
> option of  establishing either an  IPv6 tunnel or IPv4  tunnel between
> the HA and LMA, depending  on the network.  This enables the operation
> of Mobile IPv6 over the existing Internet, which is predominently IPv4
> and will most likely evolve gradually to IPv6.
> 
> This was one of the three main motivations for LMA draft.


Interesting. I don't remember seeing supporting protocol details, so 
obviously missed this feature of LMA.

PatC


From owner-mobile-ip@sunroof.eng.sun.com  Mon Sep 24 09:52:39 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA09523
	for <mobileip-archive@lists.ietf.org>; Mon, 24 Sep 2001 09:52:38 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id DAA19211;
	Mon, 24 Sep 2001 03:22:36 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id DAA29331;
	Mon, 24 Sep 2001 03:22:29 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8OALg7B023091
	for <mobile-ip-dist@sunroof.eng.sun.com>; Mon, 24 Sep 2001 03:21:42 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8OALgih023090
	for mobile-ip-dist; Mon, 24 Sep 2001 03:21:42 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8OALd7B023083
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 24 Sep 2001 03:21:39 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id DAA29246
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 24 Sep 2001 03:21:39 -0700 (PDT)
Received: from laposte.enst-bretagne.fr (laposte.enst-bretagne.fr [192.108.115.3])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id DAA13684
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 24 Sep 2001 03:21:38 -0700 (PDT)
Received: from rsm.rennes.enst-bretagne.fr (rsm.rennes.enst-bretagne.fr [192.44.77.1])
	by laposte.enst-bretagne.fr (8.11.6/8.11.6) with ESMTP id f8OALTv22090;
	Mon, 24 Sep 2001 12:21:29 +0200
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr [193.52.74.194])
	by rsm.rennes.enst-bretagne.fr (8.8.8/8.8.8) with ESMTP id MAA03807;
	Mon, 24 Sep 2001 12:21:29 +0200 (MET DST)
Received: from givry.rennes.enst-bretagne.fr (localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.11.3/8.11.3) with ESMTP id f8OALTl18087;
	Mon, 24 Sep 2001 12:21:29 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200109241021.f8OALTl18087@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: "Peter Grimstrup (TED)" <peter.grimstrup@ted.ericsson.dk>
cc: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Mobile IPv6 draft revision 
In-reply-to: Your message of Mon, 24 Sep 2001 10:59:04 +0200.
             <3BAEF5D8.C0EDD571@ted.ericsson.dk> 
Date: Mon, 24 Sep 2001 12:21:29 +0200
X-Virus-Scanned: by amavisd-milter (http://www.amavis.org/) at enst-bretagne.fr
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
 In your previous mail you wrote:

   >    When deregistering, the HoA is the (unique) key and the only use
   >    of the CoA is to be used as destination of the BA. If an alt-CoA
   >    is in the deregistering BU, the only reason must be that the
   
   If I understand you correct, I recognize that "only reason" was not
   a good wording. You have described another good reason below.
   
=> you've understood be correctly.

   >    mobile node for some reason want the BA to be sent there.
   > 
   > => the CoA is implicitly the source address of the BU where there is
   > no alt-CoA, so if you'd like to use an alternate source address for the
   > BU the alt-CoA feature provides exactly what you need. For instance
   > if you have registered only a global HoA, the deregistration packet
   > can be: source=link-local address on the home link, destination=HA
   > own address, HA=HoA, alt-CoA=HoA. This works very well without
   > any interference with neighbor discovery.
   
   In this case, the destination of the BA could still be the alt-CoA=HoA?
   
=> yes, the destination of the BA should be the HoA.

   Interference with ND is needed at least before sending a BA on the 
   home network, I guess.
   
=> yes but this will happen *after* the deregistration so without trouble.
This works so well that I'll complain if someone suggests to remove the
alt-CoA feature.

Regards

Francis.Dupont@enst-bretagne.fr


From owner-mobile-ip@sunroof.eng.sun.com  Mon Sep 24 09:55:12 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA09851
	for <mobileip-archive@odin.ietf.org>; Mon, 24 Sep 2001 09:55:11 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id CAA22211;
	Mon, 24 Sep 2001 02:35:26 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id BAA06527;
	Mon, 24 Sep 2001 01:35:29 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8O8YG7B022717
	for <mobile-ip-dist@sunroof.eng.sun.com>; Mon, 24 Sep 2001 01:34:16 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8O8YG3s022716
	for mobile-ip-dist; Mon, 24 Sep 2001 01:34:16 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8O8YC7B022709
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 24 Sep 2001 01:34:12 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id BAA21265
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 24 Sep 2001 01:34:16 -0700 (PDT)
Received: from laposte.enst-bretagne.fr (laposte.enst-bretagne.fr [192.108.115.3])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id BAA22848
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 24 Sep 2001 01:34:15 -0700 (PDT)
Received: from rsm.rennes.enst-bretagne.fr (rsm.rennes.enst-bretagne.fr [192.44.77.1])
	by laposte.enst-bretagne.fr (8.11.6/8.11.6) with ESMTP id f8O8YDB02757
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 24 Sep 2001 10:34:13 +0200
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr [193.52.74.194])
	by rsm.rennes.enst-bretagne.fr (8.8.8/8.8.8) with ESMTP id KAA02155
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 24 Sep 2001 10:34:13 +0200 (MET DST)
Received: from givry.rennes.enst-bretagne.fr (localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.11.3/8.11.3) with ESMTP id f8O8YDl17634
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 24 Sep 2001 10:34:13 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200109240834.f8O8YDl17634@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Mobile IPv6 draft revision 
In-reply-to: Your message of Mon, 24 Sep 2001 10:16:31 +0200.
             <3BAEEBDF.8A8C34E4@ted.ericsson.dk> 
Date: Mon, 24 Sep 2001 10:34:13 +0200
X-Virus-Scanned: by amavisd-milter (http://www.amavis.org/) at enst-bretagne.fr
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
 In your previous mail you wrote:

   When deregistering, the HoA is the (unique) key and the only use 
   of the CoA is to be used as destination of the BA. If an alt-CoA 
   is in the deregistering BU, the only reason must be that the 
   mobile node for some reason want the BA to be sent there.
   
=> the CoA is implicitly the source address of the BU where there is
no alt-CoA, so if you'd like to use an alternate source address for the
BU the alt-CoA feature provides exactly what you need. For instance
if you have registered only a global HoA, the deregistration packet
can be: source=link-local address on the home link, destination=HA
own address, HA=HoA, alt-CoA=HoA. This works very well without
any interference with neighbor discovery.

Regards

Francis.Dupont@enst-bretagne.fr


From owner-mobile-ip@sunroof.eng.sun.com  Mon Sep 24 09:55:12 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA09858
	for <mobileip-archive@odin.ietf.org>; Mon, 24 Sep 2001 09:55:12 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id CAA14106;
	Mon, 24 Sep 2001 02:17:34 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id BAA05007;
	Mon, 24 Sep 2001 01:17:38 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8O8Ge7B022636
	for <mobile-ip-dist@sunroof.eng.sun.com>; Mon, 24 Sep 2001 01:16:40 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8O8GdUW022635
	for mobile-ip-dist; Mon, 24 Sep 2001 01:16:39 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8O8Ga7B022628
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 24 Sep 2001 01:16:36 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id BAA19283;
	Mon, 24 Sep 2001 01:16:39 -0700 (PDT)
Received: from iproxy1.ericsson.dk (iproxy1.ericsson.dk [130.228.248.98])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id BAA27644;
	Mon, 24 Sep 2001 01:16:38 -0700 (PDT)
Received: from unixmail.ted.dk.eu.ericsson.se (knud.ted.dk.eu.ericsson.se [192.66.4.246])
	by iproxy1.ericsson.dk (8.10.1/8.10.1) with ESMTP id f8O8Gbc01282;
	Mon, 24 Sep 2001 10:16:37 +0200 (MET DST)
Received: from ted.ericsson.dk (petg.ted.dk.eu.ericsson.se [192.66.4.85])
	by unixmail.ted.dk.eu.ericsson.se (8.10.1/8.10.1/TEDmain-1.0) with ESMTP id f8O8GVL08305;
	Mon, 24 Sep 2001 10:16:31 +0200 (MEST)
Message-ID: <3BAEEBDF.8A8C34E4@ted.ericsson.dk>
Date: Mon, 24 Sep 2001 10:16:31 +0200
From: "Peter Grimstrup (TED)" <peter.grimstrup@ted.ericsson.dk>
Organization: Ericsson Telebit A/S
X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.14-5.0 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: charliep.@iprg.nokia.com, alper.yegin@eng.sun.com
CC: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Mobile IPv6 draft revision
References: <200109212215.f8LMFwVj938098@jurassic.eng.sun.com> <3BABCD92.AC211520@iprg.nokia.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Comments below.

Charlie Perkins wrote:
> 
> Hello Alper,
> 
> > > - The Binding Acknowledgement is to be sent to the Mobile Node
> > >   at the address in the Source IP address field of the Binding Update.
> >
> > This packet should be sent to care-of address, right? Not necessarily the source
> > address of the incoming BU. Care-of address would be different than the source
> > address of BU if there's a alternate care-of address option.
> 
> I thought the purpose of using the alternate care-of address
> was to deregister a care-of address at which the mobile node
> no longer had connectivity.  If this is true, then it makes more
> sense to use the source address of the packet containing the
> Binding Update, I think.
> 
> > alper
> 
> Regards,
> Charlie P.

When registering, I think a number of reasons to use an alt-CoA 
could be listed. The (alt-)CoA will be put in the binding cash 
with the HoA as (unique) key.

When deregistering, the HoA is the (unique) key and the only use 
of the CoA is to be used as destination of the BA. If an alt-CoA 
is in the deregistering BU, the only reason must be that the 
mobile node for some reason want the BA to be sent there.

Peter


From owner-mobile-ip@sunroof.eng.sun.com  Mon Sep 24 09:55:13 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA09867
	for <mobileip-archive@odin.ietf.org>; Mon, 24 Sep 2001 09:55:13 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id CAA23572;
	Mon, 24 Sep 2001 02:38:09 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id BAA06878;
	Mon, 24 Sep 2001 01:38:13 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8O8bQ7B022773
	for <mobile-ip-dist@sunroof.eng.sun.com>; Mon, 24 Sep 2001 01:37:26 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8O8bQLZ022772
	for mobile-ip-dist; Mon, 24 Sep 2001 01:37:26 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8O8bN7B022765
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 24 Sep 2001 01:37:23 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id BAA11970
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 24 Sep 2001 01:37:27 -0700 (PDT)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id BAA23780
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 24 Sep 2001 01:37:26 -0700 (PDT)
Received: from esealnt406.al.sw.ericsson.se (ESEALNT406.al.sw.ericsson.se [153.88.251.29])
	by penguin.wise.edt.ericsson.se (8.11.0/8.10.1/WIREfire-1.3) with SMTP id f8O8bPv01189
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 24 Sep 2001 10:37:25 +0200 (MEST)
Received: FROM esealnt746.al.sw.ericsson.se BY esealnt406.al.sw.ericsson.se ; Mon Sep 24 10:37:21 2001 +0200
Received: by ESEALNT746.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <THN5DT5Y>; Mon, 24 Sep 2001 10:37:13 +0200
Message-ID: <F7709E7648BAD41181E60008C716A229F567CE@edkchnt102.lmd.ericsson.se>
From: "Karen E Nielsen (TED)" <Karen.E.Nielsen@lmd.ericsson.se>
To: "'Charles E. Perkins'" <charliep@iprg.nokia.com>
Cc: mobile-ip@sunroof.eng.sun.com
Subject: RE: [mobile-ip] -14 Authentication Data computation
Date: Mon, 24 Sep 2001 10:40:04 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Hi Charlie,

I gather from what's below that you're now aiming at putting
the authentication data into a destination sub-option - that seems reasonable
(I guess that it allows for more elegant interworking with other authentication 
mechs (e.g., IP SEC AH)).

Other Comments (for what they are worth) are inside.

Regards,
Karen

> -----Original Message-----
> From: Charles E. Perkins [mailto:charliep@iprg.nokia.com]
> Sent: 20. september 2001 21:17
> To: karen.e.nielsen@lmd.ericsson.se; karen.e.nielsen@ted.ericsson.dk
> Cc: mobile-ip@sunroof.eng.sun.com
> Subject: Re: [mobile-ip] -14 Authentication Data computation
> 
> 
> 
> Hello Karen,
> 
> "Karen E Nielsen (TED)" wrote:
> > 
> > Comment/question to the computation of the Authentication 
> Data covering
> > a Binding Update and a Binding Acknowledgement in draft -14.
> > 
> > According to section 4.4 in draft-14 the Authentication 
> Data covering
> > a Binding Updata MUST be computed over a bit string containing the
> > following IP addresses:
> >	Destination IP Address of the IPv6 header
> >	Care-of Address, in the Source IP Address of the IPv6 header
> >	Home Address, from the Home Address destination option
> >	+ some more data
> > 
> > And the Authentication Data covering a Binding 
> Acknowledgement MUST be
> > computed over a bit string containing the following IP addresses :
> >	Destination IP Address of the IPv6 header
> >	Source IP Address of the IPv6 header
> >	+ some more data
> > 
> > First of all I suppose that what is meant is the 
> destination addresses
> > of the IPv6 header as it appears at the receiver end (in 
> line with the
> > computation of authentication data in IP SEC)  !?   Since 
> both the BU
> > (in case the CN is mobile) and the BUAck might be send 
> using a routing
> > header this will be important to specify, I think.
> 
> I agree!
> 
> 
> > Secondly, in the case where the CN is itself a mobile node, 
> the source
> > address of the IP header of the BuAck will be a CoA of the CN,
> > which really has nothing to do with the acknowledgement of a BU sent
> > to the CN - wouldn't the appropriate address to cover here 
> be the Home
> > address of the CN -  either appearing in the source address 
> of the IP
> > header or in the Home Address option ?
> 
> Again, I agree!  Thank you for pointing out these problems.
> 
> Here is the new text for section 4.4:
> 
> ==============================================================
> =========
> 4.4. Authentication Requirements for Binding Update and 
> Acknowledgement
> 
>    Any packet that includes a Binding Update or Binding 
> Acknowledgement
>    option has to contain some Authentication Data to guard against
>    malicious Binding Updates or Acknowledgements.  The way that
>    the Authentication Data is computed has to provide sender
>    authentication, data integrity protection, and replay protection.
>    This section specifies requirements for which data is to 
> be protected
>    when the Authentication Data Sub-Option is used to supply the
>    necessary authentication data for the Binding Update or Binding
>    Acknowledgement.  Every IPv6 node which supports transmission or
>    reception of these destination options MUST support the computation
>    of the Authentication Data Sub-Option according to the rules in
>    this section.  The Authentication Data Sub-Option MUST be the last
>    Sub-Option contained within any destination option in which the
>    Authentication Data Sub-Option occurs.
> 
>    The Authentication Data covering a Binding Update or MUST 
> be computed
>    over a bitstring containing the following fields of the IPv6 header
>    and destination options, in order:
> 
>     -  The IPv6 address of the destination of the packet, as 
> seen by the
>        recipient
>     -  Care-of Address, in the Source IP Address of the IPv6 header
>     -  The Home Address of the mobile node, from the Home Address
>        destination option

I think, one shouldn't specify where the CoA and Home Address can be found. I find 
it slightly confusing since the (at least conceptual) location of these addresses might have 
been interchanged due to prior IP SEC processing of the packet in case some SA applies to the packet as a hole.

>     -  Option Type of the Binding Update destination option
>     -  Option Length of the Binding Update destination option
>     -  All flags of the Binding Update destination option
>     -  Reserved Field of the Binding Update destination option
>     -  Sequence Number Field of the Binding Update
>     -  Lifetime of the Binding Update destination option
>     -  The entire data from all Binding Update Sub-Options (except the
>        Authentication Data suboption), if any others exist
>     -  The Type (i.e., the 8-bit value 0x04) and the Length of the
>        Authentication Data Sub-Option
>     -  Security Parameters Index (SPI) of the Authentication Data
>        Sub-Option
> 
>    When a Routing Header is used to deliver the Binding Update to
>    the receiving node, the address to be used for the Destination IP
>    Address part of the computation will initially be located 
> as the last
>    component of the Routing Header.  Otherwise, the address to be used
>    will be the Destination IP Address in the IPv6 header of 
> the outgoing
>    packet.
> 
>    When the Authentication Data Sub-Option is used with a Binding
>    Acknowledgement, the Authentication Data MUST be computed over a
>    bitstring containing the following data, in order:
> 
>     -  The IPv6 address of the destination of the packet, as 
> seen by the
>        recipient
>     -  The Home Address of the sender
>     -  Option Type of the Binding Acknowledgement destination option
>     -  Option Length of the Binding Acknowledgement
>     -  Status of the Binding Acknowledgement
>     -  Sequence Number field of the Binding Acknowledgement
>     -  Lifetime field of the Binding Acknowledgement 
> destination option
>     -  Refresh field of the Binding Acknowledgement destination option
>     -  The entire data from all Binding Acknowledgement Sub-Options
>        (except the Authentication Data suboption), if any others exist
>     -  The Type (i.e., the 8-bit value 0x04) and the Length of the
>        Authentication Data Sub-Option
>     -  Security Parameters Index (SPI) of the Authentication Data
>        Sub-Option
> 
>    When a Home Address destination option is used to deliver 
> the Binding
>    Acknowledgement to the receiving node, the Home Address of 
> the sender
>    will be located in that destination option.  Otherwise, the Home
>    Address of the sender will be located in the Source IP 
> Address field
>    of the IPv6 header.
> 
>    If a Security Association applied to the packet for other reasons
>    requires use of ESP [12], for example to encrypt the 
> transport layer
>    data carried in the packet, this use of ESP is not sufficient to
>    satisfy the authentication requirements of Mobile IPv6.
> 
I do not see why it is important to specify that ESP cannot be used.
The specification below which clearly states that any alternative authentication
mechs MUST cover the data specified above should be sufficient.

>    Authentication Data assuring the integrity of Binding Updates and
>    Binding Acknowledgement MAY, in some cases, instead be supplied by
>    other authentication mechanisms outside the scope of this document
>    (e.g., IPsec [13]).  When alternative mechanisms are used, the same
>    data as indicated above MUST be included as part of the input data
>    stream for the authentication algorithm; however (according to the
>    requirements of the alternative authentication algorithm) the order
>    of the data elements in the input data stream MAY be 
> changed from the
>    order specfied within this section for use with the Authentication
>    Data Sub-Option (see section 5.5).
> 
> ==============================================================
> =========
> 
> Note: the exact wording and placement of this text is likely to
> change if I find further problems.  Maybe it should be two subsections
> instead of one.  Maybe there should be two Authentication Data
> Sub-Options instead of one.
> 
> Comments?
> 
> 
> > /Karen
> 
> Regards,
> Charlie P.
> 


From owner-mobile-ip@sunroof.eng.sun.com  Mon Sep 24 09:57:25 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10229
	for <mobileip-archive@lists.ietf.org>; Mon, 24 Sep 2001 09:57:24 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id CAA23967;
	Mon, 24 Sep 2001 02:00:42 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id CAA09206;
	Mon, 24 Sep 2001 02:00:20 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8O8xN7B022948
	for <mobile-ip-dist@sunroof.eng.sun.com>; Mon, 24 Sep 2001 01:59:23 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8O8xNmo022947
	for mobile-ip-dist; Mon, 24 Sep 2001 01:59:23 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8O8xJ7B022940
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 24 Sep 2001 01:59:19 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id BAA28467
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 24 Sep 2001 01:59:21 -0700 (PDT)
Received: from iproxy1.ericsson.dk (iproxy1.ericsson.dk [130.228.248.98])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id BAA14516
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 24 Sep 2001 01:59:20 -0700 (PDT)
Received: from unixmail.ted.dk.eu.ericsson.se (knud.ted.dk.eu.ericsson.se [192.66.4.246])
	by iproxy1.ericsson.dk (8.10.1/8.10.1) with ESMTP id f8O8xAc06830;
	Mon, 24 Sep 2001 10:59:10 +0200 (MET DST)
Received: from ted.ericsson.dk (petg.ted.dk.eu.ericsson.se [192.66.4.85])
	by unixmail.ted.dk.eu.ericsson.se (8.10.1/8.10.1/TEDmain-1.0) with ESMTP id f8O8x5L09243;
	Mon, 24 Sep 2001 10:59:05 +0200 (MEST)
Message-ID: <3BAEF5D8.C0EDD571@ted.ericsson.dk>
Date: Mon, 24 Sep 2001 10:59:04 +0200
From: "Peter Grimstrup (TED)" <peter.grimstrup@ted.ericsson.dk>
Organization: Ericsson Telebit A/S
X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.14-5.0 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: mobile-ip@sunroof.eng.sun.com, Francis.Dupont@enst-bretagne.fr
Subject: Re: [mobile-ip] Mobile IPv6 draft revision
References: <200109240834.f8O8YDl17634@givry.rennes.enst-bretagne.fr>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hi Francis

Comments inline.

Regards
Peter
--
Francis Dupont wrote:
> 
>    When deregistering, the HoA is the (unique) key and the only use
>    of the CoA is to be used as destination of the BA. If an alt-CoA
>    is in the deregistering BU, the only reason must be that the

If I understand you correct, I recognize that "only reason" was not
a good wording. You have described another good reason below.

>    mobile node for some reason want the BA to be sent there.
> 
> => the CoA is implicitly the source address of the BU where there is
> no alt-CoA, so if you'd like to use an alternate source address for the
> BU the alt-CoA feature provides exactly what you need. For instance
> if you have registered only a global HoA, the deregistration packet
> can be: source=link-local address on the home link, destination=HA
> own address, HA=HoA, alt-CoA=HoA. This works very well without
> any interference with neighbor discovery.

In this case, the destination of the BA could still be the alt-CoA=HoA?

Interference with ND is needed at least before sending a BA on the 
home network, I guess.

> 
> Regards
> 
> Francis.Dupont@enst-bretagne.fr

-- 
Peter Grimstrup          Systems Developer
Ericsson Telebit A/S     tel: +45 89 38 52 75
Skanderborgvej 232       fax: +45 89 38 51 01
DK 8260 Viby J, Denmark  e-mail: peter.grimstrup@ted.ericsson.dk


From owner-mobile-ip@sunroof.eng.sun.com  Mon Sep 24 10:04:05 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10937
	for <mobileip-archive@lists.ietf.org>; Mon, 24 Sep 2001 10:04:05 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id AAA26832;
	Mon, 24 Sep 2001 00:21:23 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id AAA05686;
	Mon, 24 Sep 2001 00:21:18 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8O7KV7B022417
	for <mobile-ip-dist@sunroof.eng.sun.com>; Mon, 24 Sep 2001 00:20:31 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8O7KUMD022416
	for mobile-ip-dist; Mon, 24 Sep 2001 00:20:30 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8O7KR7B022409
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 24 Sep 2001 00:20:27 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id AAA05657
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 24 Sep 2001 00:20:30 -0700 (PDT)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id AAA02563
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 24 Sep 2001 00:20:29 -0700 (PDT)
Received: from esealnt406.al.sw.ericsson.se (ESEALNT406.al.sw.ericsson.se [153.88.251.29])
	by penguin.wise.edt.ericsson.se (8.11.0/8.10.1/WIREfire-1.3) with SMTP id f8O7KSv21479
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 24 Sep 2001 09:20:28 +0200 (MEST)
Received: FROM esealnt400.al.sw.ericsson.se BY esealnt406.al.sw.ericsson.se ; Mon Sep 24 09:20:27 2001 +0200
Received: by esealnt400 with Internet Mail Service (5.5.2653.19)
	id <THZ65JL2>; Mon, 24 Sep 2001 09:20:27 +0200
Message-ID: <034BEFD03799D411A59F00508BDF754603008CE0@esealnt448.al.sw.ericsson.se>
From: "Hesham Soliman  (ERA)" <Hesham.Soliman@era.ericsson.se>
To: "'mobile-ip@sunroof.eng.sun.com'" <mobile-ip@sunroof.eng.sun.com>,
        Alper Yegin <Alper.Yegin@eng.sun.com>
Subject: RE: [mobile-ip] Mobile IPv6 draft revision
Date: Mon, 24 Sep 2001 09:20:16 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Hello Charlie, 

> > > - The Binding Acknowledgement is to be sent to the Mobile Node
> > >   at the address in the Source IP address field of the Binding Update.
> >
> > This packet should be sent to care-of address, right? Not necessarily the source
> > address of the incoming BU. Care-of address would be different than the source
> > address of BU if there's a alternate care-of address option.
> 
> I thought the purpose of using the alternate care-of address
> was to deregister a care-of address at which the mobile node
> no longer had connectivity.  If this is true, then it makes more
> sense to use the source address of the packet containing the
> Binding Update, I think.
> 
	=> I beleive that the purpose of using the alt-CoA suboption is 
	to allow the MN to send a BU from one CoA but request that
	packets are sent to another. The particular situation where this
	is applicable will vary. One reason is the example you mention 
	above but there are others. HMIPv6 uses it in a different way. 
	So I just wanted to make sure that we don't decide on a certain
	usage of the alt-CoA based on the example above only. 

	Regs,
	Hesham



From owner-mobile-ip@sunroof.eng.sun.com  Mon Sep 24 10:07:10 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA11228
	for <mobileip-archive@lists.ietf.org>; Mon, 24 Sep 2001 10:07:09 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id XAA21472;
	Sun, 23 Sep 2001 23:56:48 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id XAA03722;
	Sun, 23 Sep 2001 23:56:33 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8O6tk7B022316
	for <mobile-ip-dist@sunroof.eng.sun.com>; Sun, 23 Sep 2001 23:55:46 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8O6tj8I022315
	for mobile-ip-dist; Sun, 23 Sep 2001 23:55:45 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8O6tg7B022308
	for <mobile-ip@sunroof.eng.sun.com>; Sun, 23 Sep 2001 23:55:42 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id XAA18744
	for <mobile-ip@sunroof.eng.sun.com>; Sun, 23 Sep 2001 23:55:45 -0700 (PDT)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id XAA00261
	for <mobile-ip@sunroof.eng.sun.com>; Sun, 23 Sep 2001 23:55:44 -0700 (PDT)
Received: from esealnt406.al.sw.ericsson.se (ESEALNT406.al.sw.ericsson.se [153.88.251.29])
	by penguin.wise.edt.ericsson.se (8.11.0/8.10.1/WIREfire-1.3) with SMTP id f8O6tgv01754
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 24 Sep 2001 08:55:43 +0200 (MEST)
Received: FROM esealnt742.al.sw.ericsson.se BY esealnt406.al.sw.ericsson.se ; Mon Sep 24 08:55:42 2001 +0200
Received: by esealnt742.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <TH2J611M>; Mon, 24 Sep 2001 08:48:33 +0200
Message-ID: <034BEFD03799D411A59F00508BDF754603008CDF@esealnt448.al.sw.ericsson.se>
From: "Hesham Soliman  (ERA)" <Hesham.Soliman@era.ericsson.se>
To: "'mobile-ip@sunroof.eng.sun.com'" <mobile-ip@sunroof.eng.sun.com>
Subject: RE: [mobile-ip] New BETH Draft
Date: Mon, 24 Sep 2001 08:55:32 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

James, 

I don't think we should advertise anything about FMIPv6
to the MN, or BETH for that matter. 
The whole mechanism works transparently andif one 
side is unaware of it then it will naturally fall through. 
If the MN sends Pr_rtr_sol an gets no reply then the 
Fast Handover will fail. If the AR sends Pr_adv and the 
MN doesn't understand it the handover will fail anyway. 

Also for MIPv6 if the MN sends a BU to oAR and it is not
capable then the BU will be dropped.

In BETH, there is no involvment from the MN anyway so 
no need to advertise. 

I understood BETH was designed for certain cases in which 
BW is expensive and getting some parallelism between the 
traffic and signalling was not possible. The last thing you 
need is yet another rtr_adv option which will not be necessary.

Hesham


> -----Original Message-----
> From:	James Kempf [SMTP:James.Kempf@Sun.COM]
> Sent:	Thursday, 20 September 2001 1:13
> To:	mobile-ip@sunroof.eng.sun.com; Basavaraj.Patil@nokia.com
> Cc:	James.Kempf@Sun.COM; rajeev@iprg.nokia.com
> Subject:	RE: [mobile-ip] New BETH Draft
> 
> Hi Raj,
> 
> 
> >Any reason why solicited RtrAdvts and not the reguar rtradvts?
> >
> 
> Good point.
> 
> There's a bootstrapping issue here w.r.t. FMIPv6
> in general. Suppose an MN is capable of doing mobile initiated
> FMIPv6 handover, it comes up in a network, gets a RtAdv for its initial
> AR. How does it know that it can issue a SolPrxyRtAdv when it
> gets a trigger saying it is about to be handed over? Should it
> just issue one, and, if the current AR doesn't respond, assume that
> it can't do FMIPv6 handover in this coverage area? Obviously, if the handover is 
> network initiated, the MN will receive a PrxyRtAdv and then it knows it can do 
> an FMIPv6 handover if it is capable. If not, it will simply
> ignore the PrxyRtAdv. Similarly, if the MN moves out of an FMIPv6
> coverage area and back again, how does it know when it can restart
> doing FMIPv6 handover?
> 
> A similar consideration holds for BETH. The MN may come up in a 
> network that is BETH capable, it needs to know it can suppress
> MIPv6 handover signalling if it's traffic pattern suggests to.
> The MN may be handed over into a coverage area lacking BETH
> support, then handed over again to a coverage area in which
> BETH is supported. 
> 
> >Would you advertise that the network you are in supports Fast HO  (as
> >per FMIPv6) or only indicate that the network supports BETH? The MN
> >may not really know if a BETH HO was initiated or was succesful. So
> >even if you indicated via the rtr-advt that it was in a BETH capable
> >domain, you may still want to allow the MN to go ahead with a
> >RtrSolicit if it gets L2 triggers about changes in AP. Maybe there
> >needs to be a way of damping the RtrSolicit (in the network) if a BETH
> >HO has already been done succesfully or is in the process? I just do
> >not think you should change the MNs behavior of reacting to L2
> >triggers (movement detection) just because it is in a BETH capable
> >domain. 
> >
> 
> I think we need to advertise both BETH and FMIPv6. The MN has to know what the
> capabilities are. I think there are basically two cases:
> 
> 1) The MN comes up in the network and aquires an initial AR via SolRtAdv
> or an unsolicited RtAdv from the AR. Or the MN moves into
> a coverage area where FMIPv6 is not supported and it starts doing
> standard MIPv6 handover, then it moves into an FMIPv6/BETH coverage
> area again.
> 
> 2) The MN is in an FMIPv6/BETH coverage area and the current AR
> knows that it is about to be handed over into a coverage area
> where the ARs support more or fewer handover possibilities, so
> the current AR can signal the MN via the PrxyRtAdv.
> 
> I think 1) can be handled by indicating the handover capabilities
> in the RtAdv, and 2) can be handled by indicating them in the PrxyRtAdv.
> 
> 		jak


From owner-mobile-ip@sunroof.eng.sun.com  Mon Sep 24 10:18:27 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12340
	for <mobileip-archive@odin.ietf.org>; Mon, 24 Sep 2001 10:18:27 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id BAA03698;
	Mon, 24 Sep 2001 01:55:09 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id AAA08248;
	Mon, 24 Sep 2001 00:55:11 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8O7sF7B022524
	for <mobile-ip-dist@sunroof.eng.sun.com>; Mon, 24 Sep 2001 00:54:15 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8O7sFKd022523
	for mobile-ip-dist; Mon, 24 Sep 2001 00:54:15 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8O7sB7B022516
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 24 Sep 2001 00:54:11 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id AAA22868
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 24 Sep 2001 00:54:15 -0700 (PDT)
Received: from albatross-ext.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id BAA05619
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 24 Sep 2001 01:55:07 -0600 (MDT)
Received: from esealnt461 (esealnt461.al.sw.ericsson.se [153.88.251.61])
	by albatross.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id f8O7sCK11113
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 24 Sep 2001 09:54:12 +0200 (MEST)
Received: FROM esealnt400.al.sw.ericsson.se BY esealnt461 ; Mon Sep 24 09:54:11 2001 +0200
Received: by esealnt400 with Internet Mail Service (5.5.2653.19)
	id <THZ65LYY>; Mon, 24 Sep 2001 09:54:12 +0200
Message-ID: <034BEFD03799D411A59F00508BDF754603008CE3@esealnt448.al.sw.ericsson.se>
From: "Hesham Soliman  (ERA)" <Hesham.Soliman@era.ericsson.se>
To: "'mobile-ip@sunroof.eng.sun.com'" <mobile-ip@sunroof.eng.sun.com>
Subject: RE: [mobile-ip] comments on HMIPv6 draft
Date: Mon, 24 Sep 2001 09:54:01 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
	Hi Behcet, 

>   In
> draft-mobileip-hmipv6-04.txt in Fig. A.2 MAP sends HI to nAR. This interaction is
> marked 1a which seems to suggest that MAP knows that HO got initiated before
> anybody else. How could this be possible considering the fact that MAP is probably
> the farthest away node in the configuration?
> 
	=> The HI message is triggered by the BU received from the 
	MN. So oAR sends Pr_rtr_adv to the MN, MN sends a BU
	to the MAP which triggers the HI. 
	Of course if every node in the domain is using HMIPv6 then 
	you don't need the HI message at all because the address 
	dupication can be done locally (if you have one MAP). 
	Personally I prefer removing HI completely but there are
	more important issues to be solved in the FMIPv6 draft.

	Cheers, 
	Hesham


> "Hesham Soliman (ERA)" wrote:
> 
> > > I just wonder some bits in HMIPv6 draft (04):
> > >
> > >   - Why needs two bits ("R" and "M") instead of one to classify
> > >     Basic Mode and Extended Mode?
> > >
> >         => No good answer really ! It seemed safer at the time to explicitly
> >         leave on flag per mode.
> >
> > >  (Consequently the "P" and "T")
> > >     Is there any other mode beyond Basic Mode and Extended Mode?
> > >
> >         => You need 2 here because one says that the network is mandatnig
> >         that the user uses RCoA as a source address. So if another
> >         one is used the routers ingress filtering will drop the packets.
> >         Anothe flag is needed to allow the user to use RCoA if they wish (MAY).
> >
> > > Also I would favor if a section on possible "conceptual data
> > > structures" added/updated over MIPv6 could be provided.
> > >
> >         => OK, will add that to the TODO list.
> >
> >         Thanks,
> >         Hesham
> 
> Regards,
> 
> --
> Behcet


From owner-mobile-ip@sunroof.eng.sun.com  Mon Sep 24 10:51:08 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15412
	for <mobileip-archive@odin.ietf.org>; Mon, 24 Sep 2001 10:51:08 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id IAA27589;
	Mon, 24 Sep 2001 08:48:03 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id HAA22455;
	Mon, 24 Sep 2001 07:48:07 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8OElC7B023261
	for <mobile-ip-dist@sunroof.eng.sun.com>; Mon, 24 Sep 2001 07:47:12 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8OElCvH023260
	for mobile-ip-dist; Mon, 24 Sep 2001 07:47:12 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8OEl87B023253
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 24 Sep 2001 07:47:08 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id HAA28209
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 24 Sep 2001 07:47:10 -0700 (PDT)
Received: from extmail01m.raleigh.ibm.com (extmail01.raleigh.ibm.com [204.146.167.242])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id IAA26575
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 24 Sep 2001 08:46:58 -0600 (MDT)
Received: from rtpmail02.raleigh.ibm.com (rtpmail02.raleigh.ibm.com [192.168.1.108])
	by extmail01m.raleigh.ibm.com (8.9.0/8.9.0/RTP-FW-1.3) with ESMTP id KAA20870;
	Mon, 24 Sep 2001 10:47:08 -0400
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.37.60.3])
	by rtpmail02.raleigh.ibm.com (8.8.5/8.8.5/RTP-ral-1.2) with ESMTP id KAA29432;
	Mon, 24 Sep 2001 10:47:07 -0400
Received: from rotala.raleigh.ibm.com (narten@localhost) by rotala.raleigh.ibm.com (8.9.3/8.7/RTP-ral-1.0) with ESMTP id JAA06620; Mon, 24 Sep 2001 09:50:03 -0400
Message-Id: <200109241350.JAA06620@rotala.raleigh.ibm.com>
To: mobile-ip@sunroof.eng.sun.com
cc: charliep@iprg.nokia.com
Subject: Re: [mobile-ip] Optimizing Movement Detection on the AR 
In-Reply-To: Message of "Fri, 21 Sep 2001 16:35:21 PDT." <200109212335.QAA23836@heliopolis.eng.sun.com> 
Date: Mon, 24 Sep 2001 09:50:02 -0400
From: Thomas Narten <narten@raleigh.ibm.com>
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

> Would it be possible to add some text to Section 6.5 that allows
> the AR to unicast a Router Advert to the MN if the AR detects that the MN
> has arrived on its link?

Does the current text disallow this? I.e, are you asking for text that
encourages implementations to  do this, or just making sure that it
isn't disallowed?

Also, rather than asking someone else to provide text, how about
providing it yourself. :-) That tends to lead to the desired result
more quickly, and allows folks to better understand just what it is
you want to add to the spec.

Thomas


From owner-mobile-ip@sunroof.eng.sun.com  Mon Sep 24 11:04:47 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16865
	for <mobileip-archive@odin.ietf.org>; Mon, 24 Sep 2001 11:04:47 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id JAA12076;
	Mon, 24 Sep 2001 09:04:33 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id IAA19672;
	Mon, 24 Sep 2001 08:01:04 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8OF097B023345
	for <mobile-ip-dist@sunroof.eng.sun.com>; Mon, 24 Sep 2001 08:00:09 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8OF09Ct023344
	for mobile-ip-dist; Mon, 24 Sep 2001 08:00:09 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8OF047B023337
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 24 Sep 2001 08:00:05 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id IAA03897
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 24 Sep 2001 08:00:06 -0700 (PDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id IAA02476
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 24 Sep 2001 08:00:05 -0700 (PDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16340;
	Mon, 24 Sep 2001 10:59:54 -0400 (EDT)
Message-Id: <200109241459.KAA16340@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
CC: mobile-ip@sunroof.eng.sun.com
From: Internet-Drafts@ietf.org
Subject: [mobile-ip] I-D ACTION:draft-kempf-cdma-appl-02.txt
Date: Mon, 24 Sep 2001 10:59:53 -0400
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.


	Title		: IP Mobility and the CDMA Radio Access Network: 
                          Applicability Statement for Soft Handoff
	Author(s)	: J. Kempf, P. McCann, P. Roberts
	Filename	: draft-kempf-cdma-appl-02.txt
	Pages		: 12
	Date		: 21-Sep-01
	
Recently, there have been a variety of proposals submitted to the
Mobile IP Working Group and to other IETF working groups for IP
mobility solutions that seek to enhance or replace mobile IP. These
proposals, often characterized as micromobility or fast handoff, are
addressed primarily at the perceived need of multimedia sessions such
as video or voice over IP for faster handoff between radio base
stations, and are primarily directed at real time multimedia traffic
in 3rd generation cellular access networks. In this paper, we discuss
the design of CDMA radio access networks (RANs) and the applicability
of IP mobility to soft handoff in a CDMA RAN. We attempt to show that
given current IP routing algorithms and the constraints on a CDMA
RAN, IP mobility solutions have little, if any, role to play in
handoff within the RAN. In contrast, an IP mobility solution is
likely to play a big role in fast handoff between RANs, also called
hard handoff. While future developments in IP networking may change
this situation, IP mobility in CDMA networks currently seems to apply
only when the mobile node roams between disconnected RANs rather than
between base stations within a RAN or between connected RANs.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-kempf-cdma-appl-02.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-kempf-cdma-appl-02.txt".

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


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

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-kempf-cdma-appl-02.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-kempf-cdma-appl-02.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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

--OtherAccess--

--NextPart--




From owner-mobile-ip@sunroof.eng.sun.com  Mon Sep 24 11:21:11 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18455
	for <mobileip-archive@odin.ietf.org>; Mon, 24 Sep 2001 11:21:10 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id JAA25904;
	Mon, 24 Sep 2001 09:20:58 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id IAA25100;
	Mon, 24 Sep 2001 08:21:00 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8OFJt7B023442
	for <mobile-ip-dist@sunroof.eng.sun.com>; Mon, 24 Sep 2001 08:19:55 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8OFJsGt023441
	for mobile-ip-dist; Mon, 24 Sep 2001 08:19:54 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from eastmail1.East.Sun.COM (eastmail1.East.Sun.COM [129.148.1.240])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8OFJq7B023434
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 24 Sep 2001 08:19:52 -0700 (PDT)
Received: from onion.east.sun.com (onion.East.Sun.COM [129.148.174.110])
	by eastmail1.East.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id LAA03822
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 24 Sep 2001 11:19:53 -0400 (EDT)
Received: (from glass@localhost)
	by onion.east.sun.com (8.9.3+Sun/8.9.3) id LAA09765
	for mobile-ip@sunroof.eng.sun.com; Mon, 24 Sep 2001 11:20:24 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8NG107B021752
	for <mobile-ip@sunroof.eng.sun.com>; Sun, 23 Sep 2001 09:01:01 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA05793
	for <mobile-ip@sunroof.eng.sun.com>; Sun, 23 Sep 2001 09:01:03 -0700 (PDT)
Received: from auemail1.firewall.lucent.com (auemail1.lucent.com [192.11.223.161])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id JAA10367
	for <mobile-ip@sunroof.eng.sun.com>; Sun, 23 Sep 2001 09:01:03 -0700 (PDT)
Received: from ih2mail.ih.lucent.com (h135-1-241-39.lucent.com [135.1.241.39])
	by auemail1.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id f8NG0PR12005;
	Sun, 23 Sep 2001 12:00:25 -0400 (EDT)
Received: from lucent.com by ih2mail.ih.lucent.com (8.8.8+Sun/EMS-1.5 sol2)
	id LAA02617; Sun, 23 Sep 2001 11:00:22 -0500 (CDT)
Message-ID: <3BAE0713.EA26DB3E@lucent.com>
Date: Sun, 23 Sep 2001 11:00:19 -0500
From: Tom Hiller <tomhiller@lucent.com>
Organization: Lucent Technologies
X-Mailer: Mozilla 4.76 [en]C-CCK-MCD EMS-1.5  (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Gopal Dommety <gdommety@cisco.com>
CC: mobile-ip@sunroof.eng.sun.com, pcalhoun@diameter.org
Subject: Re: [mobile-ip] IPv6 over Mobile IPv4
References: <4.3.2.7.2.20010921120723.01f5d608@mira-sjcm-3.cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Gopal,

Thanks for your note on the tunneling similarities between LMA and our draft.
The motivation of our draft is as an interim solution while MIPv6 converges. A
major difference between the LMA draft and what we've proposed is that LMA
assumes MIPv6 and we do not. 

thanks,
Tom


PS I was having email problems - this email may be redundant


Gopal Dommety wrote:
> 
> Pete, Pat, and Tom,
> 
> Good idea..... In the past, the LMA draft
> (draft-dommety-mobileip-lma-ipv6-02.txt) talked about doing similar thing.
>   Following is an excerpt from the draft:
> 
> B)  Inter-network mechanism between  IPv6 and  IPv4: LMAs  provide the
> option of  establishing either an  IPv6 tunnel or IPv4  tunnel between
> the HA and LMA, depending  on the network.  This enables the operation
> of Mobile IPv6 over the existing Internet, which is predominently IPv4
> and will most likely evolve gradually to IPv6.
> 
> This was one of the three main motivations for LMA draft.
> 
> Thanks
> Gopal
> 
> At 05:39 PM 9/13/2001 -0500, Pete McCann wrote:
> >Hi,
> >
> >We (Pat Calhoun, Tom Hiller, and myself) recently wrote a draft
> >describing a method for running IPv6 traffic while using Mobile IPv4
> >signaling for mobility management and security.  We submitted it today
> >to internet-drafts; you can find an advance copy at:
> >
> >http://www.diameter.org/draft-mccann-mobileip-ipv6mipv4-00.txt
> >
> >Basically, this could serve as an interim solution while we wait for
> >all of the Mobile IPv6 security work to converge.  It would allow us
> >to use the existing Mobile IPv4 security model, including AAA, for
> >securing registration requests, while providing IPv6 service to
> >dual-stack mobile nodes.  It may also help ease the overall transition
> >to IPv6 because it only requires IPv6 support in the MN, FA, HA, and
> >home network, while the network between the FA and HA could be a
> >legacy IPv4 cloud.
> >
> >The draft itself is fairly straightforward; we would appreciate
> >comments on the list and would like to see if there is interest in
> >making this a working group item.
> >
> >-Pete


From owner-mobile-ip@sunroof.eng.sun.com  Mon Sep 24 12:26:58 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21982
	for <mobileip-archive@odin.ietf.org>; Mon, 24 Sep 2001 12:26:58 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id JAA10540;
	Mon, 24 Sep 2001 09:23:59 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA12721;
	Mon, 24 Sep 2001 09:23:51 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8OGMv7B023610
	for <mobile-ip-dist@sunroof.eng.sun.com>; Mon, 24 Sep 2001 09:22:57 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8OGMvin023609
	for mobile-ip-dist; Mon, 24 Sep 2001 09:22:57 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from heliopolis.eng.sun.com (redhook.Eng.Sun.COM [152.70.24.37])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8OGMr7B023602
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 24 Sep 2001 09:22:53 -0700 (PDT)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.eng.sun.com (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id JAA18976
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 24 Sep 2001 09:22:56 -0700 (PDT)
Message-Id: <200109241622.JAA18976@heliopolis.eng.sun.com>
Date: Mon, 24 Sep 2001 09:22:55 -0700 (PDT)
From: James Kempf <James.Kempf@Sun.COM>
Subject: Re: [mobile-ip] Optimizing Movement Detection on the AR 
To: mobile-ip@sunroof.eng.sun.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: y8gOQ8seqzD/7N3f1/2/jA==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Hi Thomas,

>> Would it be possible to add some text to Section 6.5 that allows
>> the AR to unicast a Router Advert to the MN if the AR detects that the MN
>> has arrived on its link?
>
>Does the current text disallow this? I.e, are you asking for text that
>encourages implementations to  do this, or just making sure that it
>isn't disallowed?
>

The current text doesn't say anything about allowing the router to using 
additional information for optimzations. The concern expressed was that
because it is explicitly not in the spec, it would be viewed
as not acceptable. This contrasts with Section 10, where mobile node
movement detection is discussed, in which the spec says:

	A mobile node MAY use any combination of mechanisms available
	to it to detect when it has moved from one link to another.
	
and later:

	Mobile nodes SHOULD use Router Discovery to discover new routers
	and on-link subnet prefixes; a mobile node MAY send Router
	Solicitation messages, or MAY wait for unsolicited (periodic)
	multicast Router Advertisement messages, as specified for
	Router Discovery [17]. 

Section 10 only encourages access routers to decrease the period
of Router Advertisment transmission, but says nothing about explicitly
tying the transmission of a Router Advertisement to the apperance
of a mobile node.

>Also, rather than asking someone else to provide text, how about
>providing it yourself. :-) That tends to lead to the desired result
>more quickly, and allows folks to better understand just what it is
>you want to add to the spec.
>

OK, how about this;

	An access router MAY use any combination of mechanisms to
	detect when a mobile node has established a link with the
	subnet serviced by the router and to inform the mobile node
	via a Router Advertisement of the mobile node's new
	point of attachment. An access router MAY unicast
	a Router Advertisement to a mobile node if it discovers
	that one has established a link, or it MAY multicast a
	Router Advertisement in response to link establishment
	rather than periodically. The intent is to speed up informing
	the mobile node of its new attachment point, to reduce the
	overall delay in establishing a new care of address.
	
One issue here is what IP address to use as the destination address for unicast. 
I suppose it could be the old care of address, but the standard MIPv6 algorithm 
provides no way for the access router to discover that, and outlining such a way 
definitely shouldn't be included in the spec, since the standard algorithm is 
intended to be simple and general. If the access router knows the mobile
node's link address, it can always deliver the packet if there is a link
level connection, but the mobile node's IP stack might not accept
it unless it has the right destination address. Perhaps it should just be left 
open, or perhaps the phrase about unicast should be taken out and the paragraph 
restricted to multicast?

		jak



From owner-mobile-ip@sunroof.eng.sun.com  Mon Sep 24 12:39:04 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22545
	for <mobileip-archive@odin.ietf.org>; Mon, 24 Sep 2001 12:39:03 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id KAA05589;
	Mon, 24 Sep 2001 10:38:52 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA25644;
	Mon, 24 Sep 2001 09:38:50 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8OGbY7B023680
	for <mobile-ip-dist@sunroof.eng.sun.com>; Mon, 24 Sep 2001 09:37:35 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8OGbYGQ023679
	for mobile-ip-dist; Mon, 24 Sep 2001 09:37:34 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8OGbV7B023672
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 24 Sep 2001 09:37:31 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA22558
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 24 Sep 2001 09:37:33 -0700 (PDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA29775
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 24 Sep 2001 10:38:26 -0600 (MDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id JAA11431;
	Mon, 24 Sep 2001 09:37:31 -0700 (PDT)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f8OGbU615650;
	Mon, 24 Sep 2001 09:37:30 -0700
X-mProtect:  Mon, 24 Sep 2001 09:37:30 -0700 Nokia Silicon Valley Messaging Protection
Received: from charliep.iprg.nokia.com (205.226.2.89, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpd8LdC0z; Mon, 24 Sep 2001 09:37:25 PDT
Message-ID: <3BAF6145.EBE4B110@iprg.nokia.com>
Date: Mon, 24 Sep 2001 09:37:25 -0700
From: "Charles E. Perkins" <charliep@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: "Hesham Soliman (EPA)" <Hesham.Soliman@ERICSSON.COM.AU>
CC: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Mobile IPv6 draft revision
References: <034BEFD03799D411A59F00508BDF754603008CE0@esealnt448.al.sw.ericsson.se>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

"Hesham Soliman (ERA)" wrote:

>> I thought the purpose of using the alternate care-of address
>> was to deregister a care-of address at which the mobile node
>> no longer had connectivity.  If this is true, then it makes more
>> sense to use the source address of the packet containing the
>> Binding Update, I think.
>
>         => I beleive that the purpose of using the alt-CoA suboption is
>         to allow the MN to send a BU from one CoA but request that
>         packets are sent to another. The particular situation where this
>         is applicable will vary. One reason is the example you mention
>         above but there are others. HMIPv6 uses it in a different way.
>         So I just wanted to make sure that we don't decide on a certain
>         usage of the alt-CoA based on the example above only.

In my paragraph, I "SHOULD" have been more explicit that my statement
was made in the context of the deregistration discussion.  There are
other uses when the Binding Update is not deregistering a care-of address.
I hope you'll let me know if anything goes wrong.

Regards,
Charlie P.


From owner-mobile-ip@sunroof.eng.sun.com  Mon Sep 24 12:39:46 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22592
	for <mobileip-archive@odin.ietf.org>; Mon, 24 Sep 2001 12:39:45 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id KAA06229;
	Mon, 24 Sep 2001 10:39:34 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA25967;
	Mon, 24 Sep 2001 09:39:37 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8OGcb7B023697
	for <mobile-ip-dist@sunroof.eng.sun.com>; Mon, 24 Sep 2001 09:38:37 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8OGcaov023696
	for mobile-ip-dist; Mon, 24 Sep 2001 09:38:36 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8OGcW7B023689
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 24 Sep 2001 09:38:32 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA22770
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 24 Sep 2001 09:38:34 -0700 (PDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id JAA21037
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 24 Sep 2001 09:38:34 -0700 (PDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id JAA11487;
	Mon, 24 Sep 2001 09:38:33 -0700 (PDT)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f8OGcXC17192;
	Mon, 24 Sep 2001 09:38:33 -0700
X-mProtect:  Mon, 24 Sep 2001 09:38:33 -0700 Nokia Silicon Valley Messaging Protection
Received: from charliep.iprg.nokia.com (205.226.2.89, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpd7w3Jdf; Mon, 24 Sep 2001 09:38:30 PDT
Message-ID: <3BAF6187.FDC8D8A4@iprg.nokia.com>
Date: Mon, 24 Sep 2001 09:38:31 -0700
From: "Charles E. Perkins" <charliep@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: "Peter Grimstrup (TED)" <peter.grimstrup@ted.ericsson.dk>
CC: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Mobile IPv6 draft revision
References: <200109212215.f8LMFwVj938098@jurassic.eng.sun.com> <3BABCD92.AC211520@iprg.nokia.com> <3BAEEBDF.8A8C34E4@ted.ericsson.dk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

"Peter Grimstrup (TED)" wrote:

> When registering, I think a number of reasons to use an alt-CoA
> could be listed. The (alt-)CoA will be put in the binding cash
> with the HoA as (unique) key.

Right.

> When deregistering, the HoA is the (unique) key and the only use
> of the CoA is to be used as destination of the BA. If an alt-CoA
> is in the deregistering BU, the only reason must be that the
> mobile node for some reason want the BA to be sent there.

It seems to me that the following natural interpretation
works well:

- The Source IP address is where the packet came from --
  and thus where the Binding Acknowledgement should go.
- The Alternate care-of address is the care-of address
  that should be deregistered.  This conforms to the
  specification for that Sub-Option.

But this is different than your interpretation.

Regards,
Charlie P.


From owner-mobile-ip@sunroof.eng.sun.com  Mon Sep 24 12:56:51 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23620
	for <mobileip-archive@odin.ietf.org>; Mon, 24 Sep 2001 12:56:51 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id KAA21875;
	Mon, 24 Sep 2001 10:56:44 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA00100;
	Mon, 24 Sep 2001 09:56:46 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8OGta7B023855
	for <mobile-ip-dist@sunroof.eng.sun.com>; Mon, 24 Sep 2001 09:55:36 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8OGta1o023854
	for mobile-ip-dist; Mon, 24 Sep 2001 09:55:36 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8OGtW7B023847
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 24 Sep 2001 09:55:33 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA22744
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 24 Sep 2001 09:55:35 -0700 (PDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id KAA20567
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 24 Sep 2001 10:55:23 -0600 (MDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id JAA12673;
	Mon, 24 Sep 2001 09:55:34 -0700 (PDT)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f8OGtWZ19848;
	Mon, 24 Sep 2001 09:55:32 -0700
X-mProtect:  Mon, 24 Sep 2001 09:55:32 -0700 Nokia Silicon Valley Messaging Protection
Received: from charliep.iprg.nokia.com (205.226.2.89, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpdkX3gxg; Mon, 24 Sep 2001 09:55:30 PDT
Message-ID: <3BAF6584.FEC045D@iprg.nokia.com>
Date: Mon, 24 Sep 2001 09:55:32 -0700
From: "Charles E. Perkins" <charliep@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Francis Dupont <Francis.Dupont@inria.fr>
CC: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Mobile IPv6 draft revision
References: <200109240834.f8O8YDl17634@givry.rennes.enst-bretagne.fr>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hello Francis,

Francis Dupont wrote:
> 
>    When deregistering, the HoA is the (unique) key and the only use
>    of the CoA is to be used as destination of the BA. If an alt-CoA
>    is in the deregistering BU, the only reason must be that the
>    mobile node for some reason want the BA to be sent there.
> 
> => the CoA is implicitly the source address of the BU where there is
> no alt-CoA, so if you'd like to use an alternate source address for the
> BU the alt-CoA feature provides exactly what you need.

O.K., but I like the more the explicit and natural statement that
the source of the Binding Update is in the Source IP address field
of the IPv6 header.  We've gone to a lot of trouble to make exactly
that statement true (e.g., create the Home Address destination option).

>                                                     For instance
> if you have registered only a global HoA, the deregistration packet
> can be: source=link-local address on the home link, destination=HA
> own address, HA=HoA, alt-CoA=HoA. This works very well without
> any interference with neighbor discovery.

Right!  But, in a later note, you said:

> => yes, the destination of the BA should be the HoA.

I didn't see your reasoning here.  I gather that you would
rather the Binding Acknowledgement _not_ be sent to the
Source IP address of the Binding Update, so I am worried.

Regards,
Charlie P.


From owner-mobile-ip@sunroof.eng.sun.com  Mon Sep 24 13:04:47 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23959
	for <mobileip-archive@odin.ietf.org>; Mon, 24 Sep 2001 13:04:47 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA03593;
	Mon, 24 Sep 2001 10:04:51 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id KAA02225;
	Mon, 24 Sep 2001 10:04:45 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8OH3t7B023928
	for <mobile-ip-dist@sunroof.eng.sun.com>; Mon, 24 Sep 2001 10:03:55 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8OH3tUY023927
	for mobile-ip-dist; Mon, 24 Sep 2001 10:03:55 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from heliopolis.eng.sun.com (redhook.Eng.Sun.COM [152.70.24.37])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8OH3p7B023917
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 24 Sep 2001 10:03:51 -0700 (PDT)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.eng.sun.com (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id KAA21140
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 24 Sep 2001 10:03:54 -0700 (PDT)
Message-Id: <200109241703.KAA21140@heliopolis.eng.sun.com>
Date: Mon, 24 Sep 2001 10:03:53 -0700 (PDT)
From: James Kempf <James.Kempf@Sun.COM>
Subject: RE: [mobile-ip] New BETH Draft
To: mobile-ip@sunroof.eng.sun.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: mA5cylWsiuu+PTbVLCnbeg==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Hi Hesham,


>I don't think we should advertise anything about FMIPv6
>to the MN, or BETH for that matter. 
>The whole mechanism works transparently andif one 
>side is unaware of it then it will naturally fall through. 
>If the MN sends Pr_rtr_sol an gets no reply then the 
>Fast Handover will fail. If the AR sends Pr_adv and the 
>MN doesn't understand it the handover will fail anyway. 
>

I understand your concern, but consider the following situation.
A MN capable of doing BETH is currently traversing an area
in which there is no FMIPv6 coverage (and consequently no BETH).
The MN enters an area in which BETH coverage is available.

While the MN is in the no-coverage area, it will be using the
standard MIPv6 algorithm for handover (soliciting for RtAdv
or waiting until the AR sends them). How does it know
to transition to not soliciting and allowing the network
to perform the handover?

There are other examples for similar transitions.

>Also for MIPv6 if the MN sends a BU to oAR and it is not
>capable then the BU will be dropped.
>

I don't follow.

>In BETH, there is no involvment from the MN anyway so 
>no need to advertise. 
>

Sure, but the MN must know when to suppress sending SolRtPr
if the AR can handle the handover via BETH.

>I understood BETH was designed for certain cases in which 
>BW is expensive and getting some parallelism between the 
>traffic and signalling was not possible. The last thing you 
>need is yet another rtr_adv option which will not be necessary.
>

It isn't that expensive, just an additional 4 bytes. The RtAdv
is only sent to the MN once, when it enters the coverage area.
After that, the MN either uses FMIPv6 handover or BETH, if
these are supported. With the text I proposed be added to
Section 6.5 of the MIPv6 spec, the AR can limit advertising
the RtAdv to only when an MN appears rather than doing it periodically,
if the AR has that information available.

The other issue here w.r.t. FMIPv6 is that if the MN doesn't know
that the network isn't capable of doing FMIPv6, it could send out
a RtSolPr on every handover, only to have these ignored by the
AR. Similarly, if the AR doesn't know that the MN isn't capable
of doing FMIPv6, then the AR could send out a PrRtAdv on every
handover, only to have them ignored. Thus, by sending out an
additional 8 bytes (4 in the SolRtAdv and 4 in the RtAdv) when the MN 
enters the coverage area, you can save sizeof(PrRtAdv) bytes 
or sizeof(SolRtAdv) for every MN on every handover.

		jak



From owner-mobile-ip@sunroof.eng.sun.com  Mon Sep 24 13:14:51 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24384
	for <mobileip-archive@odin.ietf.org>; Mon, 24 Sep 2001 13:14:51 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA07683;
	Mon, 24 Sep 2001 10:12:07 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id KAA04347;
	Mon, 24 Sep 2001 10:11:39 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8OHAM7B023987
	for <mobile-ip-dist@sunroof.eng.sun.com>; Mon, 24 Sep 2001 10:10:22 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8OHALiY023986
	for mobile-ip-dist; Mon, 24 Sep 2001 10:10:21 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8OHAI7B023979
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 24 Sep 2001 10:10:18 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id KAA22734
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 24 Sep 2001 10:10:17 -0700 (PDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id KAA06782
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 24 Sep 2001 10:10:16 -0700 (PDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id KAA14206;
	Mon, 24 Sep 2001 10:10:16 -0700 (PDT)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f8OHAFX19214;
	Mon, 24 Sep 2001 10:10:15 -0700
X-mProtect:  Mon, 24 Sep 2001 10:10:15 -0700 Nokia Silicon Valley Messaging Protection
Received: from charliep.iprg.nokia.com (205.226.2.89, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpdEo5nQX; Mon, 24 Sep 2001 10:10:13 PDT
Message-ID: <3BAF68F5.644E0A68@iprg.nokia.com>
Date: Mon, 24 Sep 2001 10:10:13 -0700
From: "Charles E. Perkins" <charliep@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
CC: Mobile IP Working Group <mobile-ip@sunroof.eng.sun.com>
Subject: Re: [mobile-ip] Coexistence with other uses for routing header
References: <200109051737.f85HbXl16720@givry.rennes.enst-bretagne.fr>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hello Francis,

Francis Dupont wrote:
> 
>  In your previous mail you wrote:
> 
>    > PS: you have a similar issue when the source route is reversed,
>    > the last (becomes the first) intermediate hop (i.e. the care-of address)
>    > SHOULD be removed. If it is not, the first hop is the sender node
>    > and if policy is to disable forwarding of source routed packet on hosts
>    > (cf. a current thread in the IPv6 WG mailing list) one is in trouble.
> 
>    But the routing header does NOT require source route reversal,
>    as best I understand it.
> 
> => RFC 2460 uses the word "permitted" but in fact reversing is done
> if and only if there is a (valid) AH.
> 
>    If this isn't clear, then I think it
>    should be made clear in the Mobile IPv6 text.
> 
> => I agree, this must be made clear in the Mobile IPv6 text.

I checked, and I think the handling for Routing Headers is pretty
clear in the text.  The mobile node doesn't put its care-of address
in a routing header for the correspondent node, and the correspondent
node checks its Binding Cache before putting in the care-of address
into a Routing Header.  These cases are not in the danger zone of
reversing "unauthorized" Routing Headers.

Regards,
Charlie P.


From owner-mobile-ip@sunroof.eng.sun.com  Mon Sep 24 13:37:39 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25512
	for <mobileip-archive@odin.ietf.org>; Mon, 24 Sep 2001 13:37:34 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id LAA27904;
	Mon, 24 Sep 2001 11:37:27 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id KAA08818;
	Mon, 24 Sep 2001 10:37:32 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8OHad7B024094
	for <mobile-ip-dist@sunroof.eng.sun.com>; Mon, 24 Sep 2001 10:36:39 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8OHadK4024093
	for mobile-ip-dist; Mon, 24 Sep 2001 10:36:39 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8OHaZ7B024086
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 24 Sep 2001 10:36:35 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id KAA29688
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 24 Sep 2001 10:36:36 -0700 (PDT)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id LAA27008
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 24 Sep 2001 11:36:24 -0600 (MDT)
Received: from esealnt406.al.sw.ericsson.se (ESEALNT406.al.sw.ericsson.se [153.88.251.29])
	by penguin.wise.edt.ericsson.se (8.11.0/8.10.1/WIREfire-1.3) with SMTP id f8OHaYv17676
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 24 Sep 2001 19:36:34 +0200 (MEST)
Received: FROM esealnt400.al.sw.ericsson.se BY esealnt406.al.sw.ericsson.se ; Mon Sep 24 19:36:05 2001 +0200
Received: by esealnt400 with Internet Mail Service (5.5.2653.19)
	id <THZ66MKX>; Mon, 24 Sep 2001 19:36:04 +0200
Message-ID: <034BEFD03799D411A59F00508BDF754603008CE8@esealnt448.al.sw.ericsson.se>
From: "Hesham Soliman  (ERA)" <Hesham.Soliman@era.ericsson.se>
To: "'mobile-ip@sunroof.eng.sun.com'" <mobile-ip@sunroof.eng.sun.com>
Subject: RE: [mobile-ip] New BETH Draft
Date: Mon, 24 Sep 2001 19:36:03 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

	Hi James, 

> >I don't think we should advertise anything about FMIPv6
> >to the MN, or BETH for that matter. 
> >The whole mechanism works transparently andif one 
> >side is unaware of it then it will naturally fall through. 
> >If the MN sends Pr_rtr_sol an gets no reply then the 
> >Fast Handover will fail. If the AR sends Pr_adv and the 
> >MN doesn't understand it the handover will fail anyway. 
> >
> 
> I understand your concern, but consider the following situation.
> A MN capable of doing BETH is currently traversing an area
> in which there is no FMIPv6 coverage (and consequently no BETH).
> The MN enters an area in which BETH coverage is available.
> 
> While the MN is in the no-coverage area, it will be using the
> standard MIPv6 algorithm for handover (soliciting for RtAdv
> or waiting until the AR sends them). How does it know
> to transition to not soliciting and allowing the network
> to perform the handover?
> 
	=> Why should it know or suppress rtr_sol ? My understanding 
	has been that the entire point of BETH was that some 
	link layers have certain timing restrictions and are not 
	flexible enough to allow for MIP to be integrated in their
	radio. But now it seems like you're adding something 
	else: suppresing rtr_sol. I don't think we need to do that. 

	We MUST distinguish between implementation issues
	and protocol issues. If I'm designing an IPv6 stack to 
	work in system foo, where foo has certain limitations 
	then I'll consider that in my design of the stack. BETH 
	has a narrow scope of use and is not designed to work
	in all cases so let's keep it that way. 

	Seriously let's not make things so unbeleivably complex that
	they become useless in practice. 


> >Also for MIPv6 if the MN sends a BU to oAR and it is not
> >capable then the BU will be dropped.
> >
> 
> I don't follow.
> 
	=> The aim was to say that you can't guarantee that every router
	will support all functions required. MIPv6 does not require 
	routers to add an option in the RA stating whether it will 
	accept BUs or not. The protocol is robust enough to handle
	that.

> >In BETH, there is no involvment from the MN anyway so 
> >no need to advertise. 
> >
> 
> Sure, but the MN must know when to suppress sending SolRtPr
> if the AR can handle the handover via BETH.
> 
	=> New requirement and is not relevant to mobility management. 
	We should not solve all problems within MIP. If the MN solicits
	and gets a new RA, normal MIPv6 will take place. 

> >I understood BETH was designed for certain cases in which 
> >BW is expensive and getting some parallelism between the 
> >traffic and signalling was not possible. The last thing you 
> >need is yet another rtr_adv option which will not be necessary.
> >
> 
> It isn't that expensive, just an additional 4 bytes. The RtAdv
> is only sent to the MN once, when it enters the coverage area.
> 
	=> These are statements based on some architecture that you're
	thinking about. RAs in general can be sent as often as the 
	network administrator wants them to be. 4 bytes plus many other
	bytes will lead to fragmentation over slow links and unnecessary
	delays. I don't know why we need it, the protocol will still
	work very well.
	Anyway, I don't think you can have a 4 byte-long option in the RA. 
	I always get confused with the alignment requirements but I
	beleive it's 8n for RAs.


> The other issue here w.r.t. FMIPv6 is that if the MN doesn't know
> that the network isn't capable of doing FMIPv6, it could send out
> a RtSolPr on every handover, only to have these ignored by the
> AR. Similarly, if the AR doesn't know that the MN isn't capable
> of doing FMIPv6, then the AR could send out a PrRtAdv on every
> handover, only to have them ignored. Thus, by sending out an> 
> additional 8 bytes (4 in the SolRtAdv and 4 in the RtAdv) when the MN > 
> enters the coverage area, you can save sizeof(PrRtAdv) bytes 
> or sizeof(SolRtAdv) for every MN on every handover.
> 
	=> The same analogy applies when a MN performs standard
	MIPv6 and send a BU (to anyone apart fron the HA) it may be accepted
	or dropped. So why is this any different ?? 

	Hesham


From owner-mobile-ip@sunroof.eng.sun.com  Mon Sep 24 16:20:23 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA29856
	for <mobileip-archive@odin.ietf.org>; Mon, 24 Sep 2001 16:20:22 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA11191;
	Mon, 24 Sep 2001 13:20:16 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id NAA17457;
	Mon, 24 Sep 2001 13:20:07 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8OKJ27B024263
	for <mobile-ip-dist@sunroof.eng.sun.com>; Mon, 24 Sep 2001 13:19:02 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8OKJ2tF024262
	for mobile-ip-dist; Mon, 24 Sep 2001 13:19:02 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8OKIw7B024255
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 24 Sep 2001 13:18:58 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id NAA19263
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 24 Sep 2001 13:19:01 -0700 (PDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id NAA22617
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 24 Sep 2001 13:19:00 -0700 (PDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id NAA29860;
	Mon, 24 Sep 2001 13:19:00 -0700 (PDT)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f8OKIxY19694;
	Mon, 24 Sep 2001 13:18:59 -0700
X-mProtect:  Mon, 24 Sep 2001 13:18:59 -0700 Nokia Silicon Valley Messaging Protection
Received: from charliep.iprg.nokia.com (205.226.2.89, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpdj4VbZG; Mon, 24 Sep 2001 13:18:58 PDT
Message-ID: <3BAF9531.DFF4C73@iprg.nokia.com>
Date: Mon, 24 Sep 2001 13:18:57 -0700
From: "Charles E. Perkins" <charliep@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Venkata Jagana <jagana@us.ibm.com>
CC: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Comments on Mobile IPv6 draft 14
References: <OFE80E90FA.29105FB0-ON88256ACD.00722C12@boulder.ibm.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hello Venkata,

Sorry for the delay in answering your questions.

Venkata Jagana wrote:

> 1. There are conflicting descriptions about MN retransmitting BU's to HA
>    in Sec 10.7 and Sec 10.8 if it doesn't receive matching BA's. Pasting
>    the corresponding text here for quick reference.
> 
>    From Sec 10.7:
>    " ...the mobile node SHOULD retransmit this Binding Update to its
>    home agent until it receives a matching Binding Acknowledgement.
>    Once reaching a retransmission timeout period of MAX_BINDACK_TIMEOUT,
>    the mobile node SHOULD continue to periodically retransmit ..."
                        .........
>    Even excluding the example piece in sec 10.8, I believe the MN should
>    really try sending BU's with its remaining list of Home Agents (if any)
>    after it initially failed with its first HA for a MAX_BINDACK_TIMEOUT
>    period.
> 
>    This needs to be clarified in the draft document.

Agreed.  Here is my text which tries to capture your argument:

           .....                        Once reaching a retransmission
   timeout period of MAX_BINDACK_TIMEOUT, the mobile node SHOULD restart
   the process of delivering the Binding Update, but trying instead the
   next Home Agent from its Home Agent list (see section 10.8).  If 
   there is only one home agent in the Home Agent list, the mobile node
   instead SHOULD continue to periodically retransmit the Binding Update
   at this rate until acknowledged (or until it begins attempting to 
   register a different primary care-of address).  See section 10.11 for
   information about retransmitting Binding Updates.


> 2. This comment is also related to again Sec 10.7 "sending binding updates
>    to the home agent":
> 
>    "...... the mobile node SHOULD continue to periodically retransmit
>    the Binding Update at this rate until acknowledged (or until it begins
>    attempting to register a different primary care-of address)."
> 
>    The above underlined statement is confusing to me because I can come up
>    with two different interpretations of "different primary CoA is selected
>    either from its pool of CoA's obtained in the same FN or when it has
>    moved to a new FN." Of course, the first interpretation doesn't seem to
>    make any sense but it quite possible to select different CoA as the
>    primary for some vague reason and use that in the BU.
> 
>    Please clarify if it really means that the selection of different
>    primary CoA is to be made after moving to a different FN or in the
>    same FN. But, If the selection of primary CoA is made within the
>    same FN, then the spec should clarify about the retransmission under
>    Retransmission of binding update (sec 10.11).

I don't know whether it is wise to make this restriction.  I can
imagine arguments for both sides.  And anyway, the point should
be that the mobile node tries a new Home Agent, not a new care-of
address. (!)  The mechanisms by which a mobile node acquires a new
care-of address are more related to either layer-2 triggers, or
reception of new Advertisements.  Neither of those events is
crucially relevant to the issue here, it seems to me.

> 3. This comment is also related to again Sec 10.7 "sending binding updates
>    to the home agent":
> 
>    "In the unlikely event that the mobile node's home address is
>     autoconfigured ......the home agent will reply to the mobile node's
>     subsequent Binding Update with a Binding Acknowledgement showing
>     Status 138, Duplicate Address Detection failed".
> 
>    However, the draft doesn't clarify on what MN should do next in such a
>    scenario. I believe that, at least, even if this home address
>    registration fails, then MN can/should continue with additional
>    registrations of its remaining home addresses if there are any.
>    Of course, these multiple registrations can however be performed
>    in parallel rather than doing them in sequence. In the case of a single
>    home address registration, if BA comes with status 138, then what
>    else MN should do? Is that the decision left to the implementation
>    or would the draft clarify something?
> 
>    Usually, I believe such a scenario wouldn't occur and I agree that it is
>    never guaranteed and hence MN possibly may pick up a different home
>    address and then continue rather than having to leave MN up in the air.

First, it's important to make sure the mobile node stops using the
same home address in this case.  But I think it's reasonable to
follow your suggestion here.  I've put in the following text:

      ....  In this case, the mobile node MUST NOT attempt to re-use
   the same home address.  It SHOULD continue to register care-of
   addresses for its other home addresses, if any.  The mobile node MAY
   also attempt to acquire a new home address to replace the one for
   which Status 138 was received, for instance by using the techniques
   described in appendix B.
 

> 4. The above comment (3) brings up another interesting point related to
>    BU's sent to CNs.
> 
>    Consider the following scenario: If a MN sends BU to CN at any time (as
>    defined in sec. 10.9 "A mobile node MAY send a Binding Update to any
>    correspondent node at any time to allow the correspondent node ...")
>    after picking up new CoA(s) but before the completion of Home Address
>    registration of this same COA (used in BU to CN), then won't this
>    be a problem.
> 
>    Hence, a MN may not a send a BU to CN at any time but only after the
>    primary COA registration succeeds to make sure the home address is
>    valid and otherwise, this address will be a conflict with another
>    node on its home network. Of course, the procedure for not allowing
>    this home address to be picked up by another network is outside the
>    scope of this document and I am sure this is a hole in the ND protocol
>    unless I am missing something here.

If the mobile node is assured that its home address is valid, then
it should be allowed to send Binding Updates to correspondent nodes
at any time.  After the mobile node sets the 'D' bit in a home
registration, and the home agent accepts, the mobile node can have
this assurance.  I have put in some text to make this clear.
For instance, in the description of the `D' bit in section 9.1:

                         .......              When the home agent sends
       a successful Binding Acknowledgement to the mobile node, in 
       response to a Binding Update with the `D' bit set, the home agent
       assures to the mobile node that its home address will continue to
       be valid at least as long as the mobile node transmits Binding  
       Updates with new care-of addresses for that home address.    

And in section 10.9:

   When the mobile node is assured that its home address is valid,  
   it MAY send a Binding Update to any correspondent node at any
   time to allow the correspondent node to cache the mobile node's
   current care-of address (subject to the rate limiting defined in  
   Section 10.12).  See for example the home agent's use the 'D' bit  
   of Binding Updates (in section 9.1) for how the mobile node can be 
   assured that its home address is still valid.


> 5. The draft doesn't talk about what would MN do if MN returns back to its
>    previously visited network.
> 
>    Sec 10.20 discusses about MN returning home - I may be wrong but my
>    understanding of this section is that MN is returning to its Original
>    Home (OH) but not the previous FN it just visited earlier and returning
>    back to it like in example of MN moving from A -> B -> C -> B network
>    and in which case, MN should deregister its earlier CoA with HA at B
>    (FH - Foreign Home, btw, pardon for my new terminology) as described
>    in Sec 10.20 but in addition, the draft should also clarify that MN
>    should register this primary CoA with its original HA.

I didn't understand the problem here.  What does "HA" mean in the last
sentence?  I don't think there is a problem, unless the mobile node
is changing its home agent or home address somehow.  Basically, the
home agent just has a single care-of address for the mobile node,
and the care-of address is supposed to correspond exactly to the
current FN.  There would not be a need for the mobile node to
deregister previous care-of addresses at its home agent.

> Venkat

Regards,
Charlie P.


From owner-mobile-ip@sunroof.eng.sun.com  Mon Sep 24 17:11:14 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01164
	for <mobileip-archive@odin.ietf.org>; Mon, 24 Sep 2001 17:11:14 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id OAA04845;
	Mon, 24 Sep 2001 14:09:29 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id OAA21251;
	Mon, 24 Sep 2001 14:09:21 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8OL867B024378
	for <mobile-ip-dist@sunroof.eng.sun.com>; Mon, 24 Sep 2001 14:08:06 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8OL86CN024377
	for mobile-ip-dist; Mon, 24 Sep 2001 14:08:06 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8OL827B024370
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 24 Sep 2001 14:08:02 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id OAA02057
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 24 Sep 2001 14:08:05 -0700 (PDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id PAA21762
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 24 Sep 2001 15:08:58 -0600 (MDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id OAA03582;
	Mon, 24 Sep 2001 14:07:58 -0700 (PDT)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f8OL7v417370;
	Mon, 24 Sep 2001 14:07:57 -0700
X-mProtect:  Mon, 24 Sep 2001 14:07:57 -0700 Nokia Silicon Valley Messaging Protection
Received: from charliep.iprg.nokia.com (205.226.2.89, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpdEVPDAx; Mon, 24 Sep 2001 14:07:53 PDT
Message-ID: <3BAFA0A9.A1520959@iprg.nokia.com>
Date: Mon, 24 Sep 2001 14:07:53 -0700
From: "Charles E. Perkins" <charliep@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Mobile IP Working Group <mobile-ip@sunroof.eng.sun.com>
CC: "Basavaraj Patil (NTC/Dallas)" <Basavaraj.Patil@nokia.com>,
        Phil Roberts <PRoberts@megisto.com>
Subject: [mobile-ip] Draft 15
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hello folks,

I have done a rough edit on revision 15 of Mobile IPv6.
It needs some proofreading.  There may still be some problems
left over because of eliminating the Mobile Router capability,
and the "Prefix Length" field of the Binding Update.  Also,
I am still puzzling over the e-mail about how a mobile node
should get the link-layer address of the home agent when it
returns home.

Here is the current draft:
	http://people.nokia.net/charlep/txt/mobilev6/mobilev6.txt



Here is a list of changes:

    -  Removed the Mobile Router Prefix Length Sub-Option
   
    -  Removed the Prefix Length field from the Binding Update.
   
    -  Reworded the specification so that the Home Agent now has to
       perform Duplicate Address Detection for the mobile node's address
       on all the prefixes for which the router is performing home agent
       service.
   
    -  Removed the section about Mobile Routers
   
    -  Added the Authentication Data Sub-option; reorganized the section
       about computing authentication data.
    
    -  Specified that the Home Agent lifetime is by default the same as
       the Router lifetime, in a Router Advertisement.
    
    -  Specified that Binding Updates with zero lifetime and the 'A' bit
       set should cause a Binding Acknowledgement to be sent back to the
       Source IP address of the Binding Update.

    -  Qualified the allowable times when a mobile node can send a
       Binding Update to a correspondent node

    -  Added text allowing the correspondent node to extend an existing
       Routing Header by also including the care-of address as the entry
       of a routing header to be visited immediately before the home
       address.  In this way, for instance, the mobile node can be an
       intermediate node of a path along the way to some other node.
   
    -  Removed the Home Address field from the Home Agent Address
       Discovery Request Message.
    
    -  Noted that ICMP Unreachable forms a potential mechanism by which
       a malicious node can cause a correspondent node to delete a valid
       entry from its Binding Cache.

    -  Specified that, when a router stops offering home agent services
       by turning off the 'H' flag, the mobile node has to delete the
       corresponding entry from its Home Agent list. 



I'll wait a bit longer before sending it, depending on current
mailing list discussion and any other comments that may be
contributed.  Surely there will be some other changes that have
to be made anyway, but it is possible to imagine that they will
be small ones.


Regards,
Charlie P.


From owner-mobile-ip@sunroof.eng.sun.com  Mon Sep 24 17:55:05 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02101
	for <mobileip-archive@odin.ietf.org>; Mon, 24 Sep 2001 17:55:04 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id OAA23768;
	Mon, 24 Sep 2001 14:55:07 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id OAA13722;
	Mon, 24 Sep 2001 14:54:57 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8OLrY7B024516
	for <mobile-ip-dist@sunroof.eng.sun.com>; Mon, 24 Sep 2001 14:53:34 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8OLrYSD024515
	for mobile-ip-dist; Mon, 24 Sep 2001 14:53:34 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8OLrU7B024508
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 24 Sep 2001 14:53:30 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id OAA09355
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 24 Sep 2001 14:53:31 -0700 (PDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id PAA18987
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 24 Sep 2001 15:53:20 -0600 (MDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id OAA07184;
	Mon, 24 Sep 2001 14:53:30 -0700 (PDT)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f8OLrSl22350;
	Mon, 24 Sep 2001 14:53:28 -0700
X-mProtect:  Mon, 24 Sep 2001 14:53:28 -0700 Nokia Silicon Valley Messaging Protection
Received: from charliep.iprg.nokia.com (205.226.2.89, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpdjyNJOI; Mon, 24 Sep 2001 14:53:25 PDT
Message-ID: <3BAFAB56.FB543C9F@iprg.nokia.com>
Date: Mon, 24 Sep 2001 14:53:26 -0700
From: "Charles E. Perkins" <charliep@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: karen.e.nielsen@lmd.ericsson.se
CC: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] -14 Authentication Data computation
References: <F7709E7648BAD41181E60008C716A229F567CE@edkchnt102.lmd.ericsson.se>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hello Karen,

> I gather from what's below that you're now aiming at putting
> the authentication data into a destination sub-option - that seems reasonable
> (I guess that it allows for more elegant interworking with other authentication
> mechs (e.g., IP SEC AH)).

Yes, thanks, I have indeed put the authentication data into a sub-option
as part of the revisions for draft ...-15


>>    The Authentication Data covering a Binding Update or MUST
>> be computed
>>    over a bitstring containing the following fields of the IPv6 header
>>    and destination options, in order:
>>
>>     -  The IPv6 address of the destination of the packet, as seen by the
>>        recipient
>>     -  Care-of Address, in the Source IP Address of the IPv6 header
>>     -  The Home Address of the mobile node, from the Home Address
>>        destination option

> I think, one shouldn't specify where the CoA and Home Address can be found.
> I find it slightly confusing since the (at least conceptual) location of these
> addresses might have been interchanged due to prior IP SEC processing of the
> packet in case some SA applies to the packet as a hole.

O.K.  I will try to figure out how to make this change.  In particular,
something needs to be said when the care-of address is in the
Alternate Care-of Address Sub-Option.


>>    If a Security Association applied to the packet for other reasons
>>    requires use of ESP [12], for example to encrypt the transport layer
>>    data carried in the packet, this use of ESP is not sufficient to
>>    satisfy the authentication requirements of Mobile IPv6.
>
> I do not see why it is important to specify that ESP cannot be used.
> The specification below which clearly states that any alternative authentication
> mechs MUST cover the data specified above should be sufficient.

The original intention was to say that ESP couldn't be used *in transport mode*.
I don't think there is any prohibition against using ESP in tunnel mode.
Does this alleviate your concern?


Regards,
Charlie P.


From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep 25 02:28:06 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA22187
	for <mobileip-archive@odin.ietf.org>; Tue, 25 Sep 2001 02:28:06 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id XAA03345;
	Mon, 24 Sep 2001 23:28:04 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id XAA02312;
	Mon, 24 Sep 2001 23:27:54 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8P6Qa7B025194
	for <mobile-ip-dist@sunroof.eng.sun.com>; Mon, 24 Sep 2001 23:26:36 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8P6Qaxv025193
	for mobile-ip-dist; Mon, 24 Sep 2001 23:26:36 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8P6QW7B025186
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 24 Sep 2001 23:26:32 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id XAA02141
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 24 Sep 2001 23:26:35 -0700 (PDT)
Received: from albatross-ext.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id XAA17977
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 24 Sep 2001 23:26:34 -0700 (PDT)
Received: from esealnt462.al.sw.ericsson.se (ESEALNT462.al.sw.ericsson.se [153.88.251.62])
	by albatross.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id f8P6QXK15599
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 08:26:33 +0200 (MEST)
Received: FROM esealnt400.al.sw.ericsson.se BY esealnt462.al.sw.ericsson.se ; Tue Sep 25 08:26:32 2001 +0200
Received: by esealnt400 with Internet Mail Service (5.5.2653.19)
	id <THZ6645K>; Tue, 25 Sep 2001 08:26:31 +0200
Message-ID: <034BEFD03799D411A59F00508BDF754603008CF5@esealnt448.al.sw.ericsson.se>
From: "Hesham Soliman  (ERA)" <Hesham.Soliman@era.ericsson.se>
To: "'mobile-ip@sunroof.eng.sun.com'" <mobile-ip@sunroof.eng.sun.com>
Cc: "Basavaraj Patil (NTC/Dallas)" <Basavaraj.Patil@nokia.com>,
        Phil Roberts <PRoberts@megisto.com>
Subject: RE: [mobile-ip] Draft 15
Date: Tue, 25 Sep 2001 08:26:22 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Hello Charlie,

We seemed to have concensus earlier (if I dare say so) that IPsec 
was to stay in the draft. But draft-14 removed IPsec, I didn't see it in
the list of changes. The draft seems to assume that the authentication
data suboption is mandated and IPsec is a MAY. I'm not sure that this 
reflects the concensus on the list, but I might have missed something. 
Comments ?
 
BTW your name is misspelt in the link. 

Regards,
Hesham


> -----Original Message-----
> From:	Charles E. Perkins [SMTP:charliep@iprg.nokia.com]
> Sent:	Tuesday, 25 September 2001 7:08
> To:	Mobile IP Working Group
> Cc:	Basavaraj Patil (NTC/Dallas); Phil Roberts
> Subject:	[mobile-ip] Draft 15
> 
> Hello folks,
> 
> I have done a rough edit on revision 15 of Mobile IPv6.
> It needs some proofreading.  There may still be some problems
> left over because of eliminating the Mobile Router capability,
> and the "Prefix Length" field of the Binding Update.  Also,
> I am still puzzling over the e-mail about how a mobile node
> should get the link-layer address of the home agent when it
> returns home.
> 
> Here is the current draft:
> 	http://people.nokia.net/charlep/txt/mobilev6/mobilev6.txt
> 
> 
> 
> Here is a list of changes:
> 
>     -  Removed the Mobile Router Prefix Length Sub-Option
>    
>     -  Removed the Prefix Length field from the Binding Update.
>    
>     -  Reworded the specification so that the Home Agent now has to
>        perform Duplicate Address Detection for the mobile node's address
>        on all the prefixes for which the router is performing home agent
>        service.
>    
>     -  Removed the section about Mobile Routers
>    
>     -  Added the Authentication Data Sub-option; reorganized the section
>        about computing authentication data.
>     
>     -  Specified that the Home Agent lifetime is by default the same as
>        the Router lifetime, in a Router Advertisement.
>     
>     -  Specified that Binding Updates with zero lifetime and the 'A' bit
>        set should cause a Binding Acknowledgement to be sent back to the
>        Source IP address of the Binding Update.
> 
>     -  Qualified the allowable times when a mobile node can send a
>        Binding Update to a correspondent node
> 
>     -  Added text allowing the correspondent node to extend an existing
>        Routing Header by also including the care-of address as the entry
>        of a routing header to be visited immediately before the home
>        address.  In this way, for instance, the mobile node can be an
>        intermediate node of a path along the way to some other node.
>    
>     -  Removed the Home Address field from the Home Agent Address
>        Discovery Request Message.
>     
>     -  Noted that ICMP Unreachable forms a potential mechanism by which
>        a malicious node can cause a correspondent node to delete a valid
>        entry from its Binding Cache.
> 
>     -  Specified that, when a router stops offering home agent services
>        by turning off the 'H' flag, the mobile node has to delete the
>        corresponding entry from its Home Agent list. 
> 
> 
> 
> I'll wait a bit longer before sending it, depending on current
> mailing list discussion and any other comments that may be
> contributed.  Surely there will be some other changes that have
> to be made anyway, but it is possible to imagine that they will
> be small ones.
> 
> 
> Regards,
> Charlie P.


From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep 25 02:30:26 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA22372
	for <mobileip-archive@odin.ietf.org>; Tue, 25 Sep 2001 02:30:26 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id AAA14927;
	Tue, 25 Sep 2001 00:30:14 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id XAA02869;
	Mon, 24 Sep 2001 23:30:17 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8P6TP7B025261
	for <mobile-ip-dist@sunroof.eng.sun.com>; Mon, 24 Sep 2001 23:29:25 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8P6TOpG025260
	for mobile-ip-dist; Mon, 24 Sep 2001 23:29:24 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8P6TK7B025250
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 24 Sep 2001 23:29:20 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id XAA27056
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 24 Sep 2001 23:29:23 -0700 (PDT)
Received: from e31.bld.us.ibm.com (e31.co.us.ibm.com [32.97.110.129])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id XAA25918
	for <mobile-ip@sunroof.eng.sun.com>; Mon, 24 Sep 2001 23:29:22 -0700 (PDT)
Received: from westrelay02.boulder.ibm.com (westrelay02.boulder.ibm.com [9.99.140.23])
	by e31.bld.us.ibm.com (8.9.3/8.9.3) with ESMTP id CAA53592;
	Tue, 25 Sep 2001 02:27:02 -0400
Received: from d03nm036.boulder.ibm.com (d03nm036.boulder.ibm.com [9.99.140.36])
	by westrelay02.boulder.ibm.com (8.11.1m3/NCO v4.97.1) with ESMTP id f8P6TLE79176;
	Tue, 25 Sep 2001 00:29:21 -0600
From: "Venkata Jagana" <jagana@us.ibm.com>
Importance: Normal
Subject: Re: [mobile-ip] Comments on Mobile IPv6 draft 14
To: "Charles E. Perkins" <charliep@iprg.nokia.com>
Cc: mobile-ip@sunroof.eng.sun.com
X-Mailer: Lotus Notes Release 5.0.5  September 22, 2000
Message-ID: <OF293DB735.F2C87DCD-ON88256AD2.001D7F39@boulder.ibm.com>
Date: Mon, 24 Sep 2001 23:29:15 -0700
X-MIMETrack: Serialize by Router on D03NM036/03/M/IBM(Release 5.0.8 |June 18, 2001) at
 09/25/2001 12:29:21 AM
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>


Hello Charlie,

Thanks very much for your responses.

The modified text for items 1, 3 and 4 looks quite good to me.
Item 2 doesn't seem to cause any problem now (see my response below).
See my response below to item 5 with some reasoning why it is still
an issue.

>> 1. There are conflicting descriptions about MN retransmitting BU's to HA
>>    in Sec 10.7 and Sec 10.8 if it doesn't receive matching BA's. Pasting
>>    the corresponding text here for quick reference.
>>
>>    From Sec 10.7:
>>    " ...the mobile node SHOULD retransmit this Binding Update to its
>>    home agent until it receives a matching Binding Acknowledgement.
>>    Once reaching a retransmission timeout period of MAX_BINDACK_TIMEOUT,
>>    the mobile node SHOULD continue to periodically retransmit ..."
                        .........
>>    Even excluding the example piece in sec 10.8, I believe the MN should
>>    really try sending BU's with its remaining list of Home Agents (if
any)
>>    after it initially failed with its first HA for a MAX_BINDACK_TIMEOUT
>>    period.
>>
>>    This needs to be clarified in the draft document.

>Agreed.  Here is my text which tries to capture your argument:

>           .....                        Once reaching a retransmission
>   timeout period of MAX_BINDACK_TIMEOUT, the mobile node SHOULD restart
>   the process of delivering the Binding Update, but trying instead the
>   next Home Agent from its Home Agent list (see section 10.8).  If
>   there is only one home agent in the Home Agent list, the mobile node
>   instead SHOULD continue to periodically retransmit the Binding Update
>   at this rate until acknowledged (or until it begins attempting to
>   register a different primary care-of address).  See section 10.11 for
>   information about retransmitting Binding Updates.

   Looks good.

>> 2. This comment is also related to again Sec 10.7 "sending binding
updates
>>    to the home agent":
>>
>>    "...... the mobile node SHOULD continue to periodically retransmit
>>    the Binding Update at this rate until acknowledged (or until it
begins
>>    attempting to register a different primary care-of address)."
>>
>>    The above underlined statement is confusing to me because I can come
up
>>    with two different interpretations of "different primary CoA is
selected
>>    either from its pool of CoA's obtained in the same FN or when it has
>>    moved to a new FN." Of course, the first interpretation doesn't seem
to
>>    make any sense but it quite possible to select different CoA as the
>>    primary for some vague reason and use that in the BU.
>>
>>    Please clarify if it really means that the selection of different
>>    primary CoA is to be made after moving to a different FN or in the
>>    same FN. But, If the selection of primary CoA is made within the
>>    same FN, then the spec should clarify about the retransmission under
>>    Retransmission of binding update (sec 10.11).

> I don't know whether it is wise to make this restriction.  I can
> imagine arguments for both sides.  And anyway, the point should
> be that the mobile node tries a new Home Agent, not a new care-of
> address. (!)  The mechanisms by which a mobile node acquires a new
> care-of address are more related to either layer-2 triggers, or
> reception of new Advertisements.  Neither of those events is
> crucially relevant to the issue here, it seems to me.

   I agree that the issue here is not related to how MN acquires the CoA's
   in the foreign networks but how it makes use of its pool of CoA's in
   registering with the home agent.

   OK, this issue may not make sense anymore because of comment [1] above
   which dictates that MN should restart the BU process with the new home
   agent from its list if doesn't get an BA within MAX_BINDACK_TIMEOUT
   period.

>> 3. This comment is also related to again Sec 10.7 "sending binding
updates
>>    to the home agent":
>>
>>    "In the unlikely event that the mobile node's home address is
>>     autoconfigured ......the home agent will reply to the mobile node's
>>     subsequent Binding Update with a Binding Acknowledgement showing
>>     Status 138, Duplicate Address Detection failed".
>>
>>    However, the draft doesn't clarify on what MN should do next in such
a
>>    scenario. I believe that, at least, even if this home address
>>    registration fails, then MN can/should continue with additional
>>    registrations of its remaining home addresses if there are any.
>>    Of course, these multiple registrations can however be performed
>>    in parallel rather than doing them in sequence. In the case of a
single
>>    home address registration, if BA comes with status 138, then what
>>    else MN should do? Is that the decision left to the implementation
>>    or would the draft clarify something?
>>
>>    Usually, I believe such a scenario wouldn't occur and I agree that it
is
>>    never guaranteed and hence MN possibly may pick up a different home
>>    address and then continue rather than having to leave MN up in the
air.

> First, it's important to make sure the mobile node stops using the
> same home address in this case.  But I think it's reasonable to
> follow your suggestion here.  I've put in the following text:

>      ....  In this case, the mobile node MUST NOT attempt to re-use
>   the same home address.  It SHOULD continue to register care-of
>   addresses for its other home addresses, if any.  The mobile node MAY
>   also attempt to acquire a new home address to replace the one for
>   which Status 138 was received, for instance by using the techniques
>   described in appendix B.

  Looks good.

>> 4. The above comment (3) brings up another interesting point related to
>>    BU's sent to CNs.
>>
>>    Consider the following scenario: If a MN sends BU to CN at any time
(as
>>    defined in sec. 10.9 "A mobile node MAY send a Binding Update to any
>>    correspondent node at any time to allow the correspondent node ...")
>>    after picking up new CoA(s) but before the completion of Home Address
>>    registration of this same COA (used in BU to CN), then won't this
>>    be a problem.
>>
>>    Hence, a MN may not a send a BU to CN at any time but only after the
>>    primary COA registration succeeds to make sure the home address is
>>    valid and otherwise, this address will be a conflict with another
>>    node on its home network. Of course, the procedure for not allowing
>>    this home address to be picked up by another network is outside the
>>    scope of this document and I am sure this is a hole in the ND
protocol
>>    unless I am missing something here.

> If the mobile node is assured that its home address is valid, then
> it should be allowed to send Binding Updates to correspondent nodes
> at any time.  After the mobile node sets the 'D' bit in a home
> registration, and the home agent accepts, the mobile node can have
> this assurance.  I have put in some text to make this clear.
> For instance, in the description of the `D' bit in section 9.1:

>                         .......              When the home agent sends
>       a successful Binding Acknowledgement to the mobile node, in
>       response to a Binding Update with the `D' bit set, the home agent
>       assures to the mobile node that its home address will continue to
>       be valid at least as long as the mobile node transmits Binding
>       Updates with new care-of addresses for that home address.

> And in section 10.9:

>   When the mobile node is assured that its home address is valid,
>   it MAY send a Binding Update to any correspondent node at any
>   time to allow the correspondent node to cache the mobile node's
>   current care-of address (subject to the rate limiting defined in
>   Section 10.12).  See for example the home agent's use the 'D' bit
>   of Binding Updates (in section 9.1) for how the mobile node can be
>   assured that its home address is still valid.

   The text looks quite OK to me.

>> 5. The draft doesn't talk about what would MN do if MN returns back to
its
>>    previously visited network.
>>
>>    Sec 10.20 discusses about MN returning home - I may be wrong but my
>>    understanding of this section is that MN is returning to its Original
>>    Home (OH) but not the previous FN it just visited earlier and
returning
>>    back to it like in example of MN moving from A -> B -> C -> B network
>>    and in which case, MN should deregister its earlier CoA with HA at B
>>    (FH - Foreign Home, btw, pardon for my new terminology) as described
>>    in Sec 10.20 but in addition, the draft should also clarify that MN
>>    should register this primary CoA with its original HA.

> I didn't understand the problem here.  What does "HA" mean in the last
> sentence?  I don't think there is a problem, unless the mobile node
> is changing its home agent or home address somehow.  Basically, the
> home agent just has a single care-of address for the mobile node,
> and the care-of address is supposed to correspond exactly to the
> current FN.  There would not be a need for the mobile node to
> deregister previous care-of addresses at its home agent.

  Let us consider a scenario where MN moves from its home network 'A' to
  foreign network 'B' and then to foreign network 'C'.

  After moving from network 'A' to network 'B', MN should have registered
  (i.e. BU sent)its primary CoA picked up at 'B' with the home agent at
'A'.
  Now, the HA at 'A' has a binding cache entry marked home registration.

  Next, the MN moves from 'B' to 'C', then, MN would send BU to the HA
  at 'A' to request the change in cache entry with the new CoA just
obtained
  at 'C' and also to a home agent at 'B' to register its new CoA obtained
at
  'C' network. The registration with home agent at 'B' is required so that
  packets addressed to its old CoA at B will now be tunnelled to its new
  CoA at 'C'. Effectively, the MN now has one home agent at 'A', which I
  called 'Original Home - OH' (because that's where its home was) and
another
  home agent at 'B' which I called 'Foreign Home - FH' at 'B'.

  Let us say that, after sometime, the MN came back from 'C' to 'B'
  during its movement path and which means that MN can start reusing its
  old COA at but before start using it there, it needs to deregister its
CoA
  at B with HA at 'B'; then sending a BU to its OH at 'A' with this CoA
  at 'B'. Then, it will have to send a BU to HA at 'C' with the CoA at 'B'
  to start tunnelling packets destined fro MN. In this case, the 'FH' is
  effectively now moved 'B' to 'C'. In this case, it had to perform 3
steps:
  deregistration with 'B', registration with HA ('OH') at 'A' with CoA at
'B'
  and registration with  HA ('FH') at 'C' with COA at 'B'.

  Hope I made this clear without making it too complicated. So, my point
  is that the draft didn't consider a scenario like this and hence never
  talked about deregistration with home agent on the foreign networks the
  MN visited. The draft only discussed about the MN going back to its home,
  i,.e always 'A' in this case, and its deregistration procedures. In
reality,
  I am sure this scenario( and there are others) I described here is very
  well applicable and I strongly believe that this needs to be addressed,
  Am I missing something here? Hope not.

Thanks,
Venkat

----------------------------------------------------------------
Venkata R Jagana
IBM Linux Technology Center, Beaverton
jagana@us.ibm.com
Tel: (503) 578 3430 T/L 775-3430



From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep 25 03:17:56 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA24839
	for <mobileip-archive@odin.ietf.org>; Tue, 25 Sep 2001 03:17:56 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id AAA15675;
	Tue, 25 Sep 2001 00:17:53 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id AAA02653;
	Tue, 25 Sep 2001 00:17:48 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8P7FD7B025422
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 25 Sep 2001 00:15:13 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8P7FDxH025421
	for mobile-ip-dist; Tue, 25 Sep 2001 00:15:13 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8P7F97B025414
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 00:15:09 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id AAA20904
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 00:15:12 -0700 (PDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id BAA13113
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 01:16:07 -0600 (MDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id AAA03484;
	Tue, 25 Sep 2001 00:15:10 -0700 (PDT)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f8P7FAv18679;
	Tue, 25 Sep 2001 00:15:10 -0700
X-mProtect:  Tue, 25 Sep 2001 00:15:10 -0700 Nokia Silicon Valley Messaging Protection
Received: from Icharliep-1.iprg.nokia.com (205.226.22.18, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpdmKjuuW; Tue, 25 Sep 2001 00:15:07 PDT
Message-ID: <3BB02E31.EC3F8D70@iprg.nokia.com>
Date: Tue, 25 Sep 2001 00:11:45 -0700
From: Charlie Perkins <charliep@iprg.nokia.com>
Organization: Nokia
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Hesham Soliman (ERA)" <Hesham.Soliman@era.ericsson.se>
CC: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Draft 15
References: <034BEFD03799D411A59F00508BDF754603008CF5@esealnt448.al.sw.ericsson.se>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hello Hesham,

As best I can figure it out, one can use IPsec for authentication
if you can get the selectors to select the right security association,
but some (or most) implementations aren't selective enough
to be assured of always picking out the right security association
depending on which destination options (or future ones) may
be in use.

So, I have made an authentication data sub-option that MUST be
supported.  IPsec MAY be used instead, and if so I don't think
that there is any additional specification within the Mobile IPv6
document that is needed for this.  If IPsec is used, then the
Authentication Data Sub-Option does not have to be present.

I hope this is good enough to satisfy the current needs, as well
as the previous discussion about how we could not count on
using IPsec in its current form.  I hope you like the new Sub-Option,
and if you have suggestions about how to make better wording
for allowing IPsec I'd be interested in that, too.

Regards,
Charlie P.


"Hesham Soliman (ERA)" wrote:

> Hello Charlie,
>
> We seemed to have concensus earlier (if I dare say so) that IPsec
> was to stay in the draft. But draft-14 removed IPsec, I didn't see it in
> the list of changes. The draft seems to assume that the authentication
> data suboption is mandated and IPsec is a MAY. I'm not sure that this
> reflects the concensus on the list, but I might have missed something.
> Comments ?
>
> BTW your name is misspelt in the link.
>
> Regards,
> Hesham
>
> > -----Original Message-----
> > From: Charles E. Perkins [SMTP:charliep@iprg.nokia.com]
> > Sent: Tuesday, 25 September 2001 7:08
> > To:   Mobile IP Working Group
> > Cc:   Basavaraj Patil (NTC/Dallas); Phil Roberts
> > Subject:      [mobile-ip] Draft 15
> >
> > Hello folks,
> >
> > I have done a rough edit on revision 15 of Mobile IPv6.
> > It needs some proofreading.  There may still be some problems
> > left over because of eliminating the Mobile Router capability,
> > and the "Prefix Length" field of the Binding Update.  Also,
> > I am still puzzling over the e-mail about how a mobile node
> > should get the link-layer address of the home agent when it
> > returns home.
> >
> > Here is the current draft:
> >       http://people.nokia.net/charlep/txt/mobilev6/mobilev6.txt
> >
> >
> >
> > Here is a list of changes:
> >
> >     -  Removed the Mobile Router Prefix Length Sub-Option
> >
> >     -  Removed the Prefix Length field from the Binding Update.
> >
> >     -  Reworded the specification so that the Home Agent now has to
> >        perform Duplicate Address Detection for the mobile node's address
> >        on all the prefixes for which the router is performing home agent
> >        service.
> >
> >     -  Removed the section about Mobile Routers
> >
> >     -  Added the Authentication Data Sub-option; reorganized the section
> >        about computing authentication data.
> >
> >     -  Specified that the Home Agent lifetime is by default the same as
> >        the Router lifetime, in a Router Advertisement.
> >
> >     -  Specified that Binding Updates with zero lifetime and the 'A' bit
> >        set should cause a Binding Acknowledgement to be sent back to the
> >        Source IP address of the Binding Update.
> >
> >     -  Qualified the allowable times when a mobile node can send a
> >        Binding Update to a correspondent node
> >
> >     -  Added text allowing the correspondent node to extend an existing
> >        Routing Header by also including the care-of address as the entry
> >        of a routing header to be visited immediately before the home
> >        address.  In this way, for instance, the mobile node can be an
> >        intermediate node of a path along the way to some other node.
> >
> >     -  Removed the Home Address field from the Home Agent Address
> >        Discovery Request Message.
> >
> >     -  Noted that ICMP Unreachable forms a potential mechanism by which
> >        a malicious node can cause a correspondent node to delete a valid
> >        entry from its Binding Cache.
> >
> >     -  Specified that, when a router stops offering home agent services
> >        by turning off the 'H' flag, the mobile node has to delete the
> >        corresponding entry from its Home Agent list.
> >
> >
> >
> > I'll wait a bit longer before sending it, depending on current
> > mailing list discussion and any other comments that may be
> > contributed.  Surely there will be some other changes that have
> > to be made anyway, but it is possible to imagine that they will
> > be small ones.
> >
> >
> > Regards,
> > Charlie P.



From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep 25 03:20:41 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA24876
	for <mobileip-archive@odin.ietf.org>; Tue, 25 Sep 2001 03:20:40 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id AAA16454;
	Tue, 25 Sep 2001 00:20:40 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id AAA03077;
	Tue, 25 Sep 2001 00:20:36 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8P7Jw7B025471
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 25 Sep 2001 00:19:58 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8P7JvEd025470
	for mobile-ip-dist; Tue, 25 Sep 2001 00:19:57 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8P7Jr7B025463
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 00:19:53 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id AAA07804
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 00:19:56 -0700 (PDT)
Received: from albatross-ext.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id BAA07147
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 01:19:44 -0600 (MDT)
Received: from esealnt462.al.sw.ericsson.se (ESEALNT462.al.sw.ericsson.se [153.88.251.62])
	by albatross.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id f8P7JsK23477
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 09:19:54 +0200 (MEST)
Received: FROM esealnt746.al.sw.ericsson.se BY esealnt462.al.sw.ericsson.se ; Tue Sep 25 09:19:53 2001 +0200
Received: by ESEALNT746.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <THN5DZZD>; Tue, 25 Sep 2001 09:19:53 +0200
Message-ID: <F7709E7648BAD41181E60008C716A2290105902E@edkchnt102.lmd.ericsson.se>
From: "Peter Grimstrup (TED)" <Peter.Grimstrup@lmd.ericsson.se>
To: "'mobile-ip@sunroof.eng.sun.com'" <mobile-ip@sunroof.eng.sun.com>
Cc: "'charliep@iprg.nokia.com'" <charliep@iprg.nokia.com>
Subject: RE: [mobile-ip] Draft 15
Date: Tue, 25 Sep 2001 09:22:43 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Hi Charlie,

Your revision seems to be fine, a question and a comment though:

Did I miss the conclusion on the piggyback discussion, or is 
this still an item?

Peter
----------------------------------------------------------------
> Here is a list of changes:
> 
>     -  Specified that Binding Updates with zero lifetime and 
>        the 'A' bit set should cause a Binding Acknowledgement
>        to be sent back to the Source IP address of the Binding
>        Update.

I still think "Source IP address" should be 
  exists(alt-CoA) ? alt-CoA : Source IP address

> 
> I'll wait a bit longer before sending it, depending on current
> mailing list discussion and any other comments that may be
> contributed.  Surely there will be some other changes that have
> to be made anyway, but it is possible to imagine that they will
> be small ones.
> 
> 
> Regards,
> Charlie P.


From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep 25 03:22:41 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA24913
	for <mobileip-archive@odin.ietf.org>; Tue, 25 Sep 2001 03:22:40 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id AAA17228;
	Tue, 25 Sep 2001 00:22:39 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id AAA03266;
	Tue, 25 Sep 2001 00:22:34 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8P7Lt7B025514
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 25 Sep 2001 00:21:55 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8P7Lsdg025512
	for mobile-ip-dist; Tue, 25 Sep 2001 00:21:54 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8P7Lp7B025504
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 00:21:51 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id AAA07950
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 00:21:54 -0700 (PDT)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id BAA15185
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 01:22:49 -0600 (MDT)
Received: from esealnt409.al.sw.ericsson.se (ESEALNT409.al.sw.ericsson.se [153.88.251.32])
	by penguin.wise.edt.ericsson.se (8.11.0/8.10.1/WIREfire-1.3) with SMTP id f8P7Lpv09098
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 09:21:51 +0200 (MEST)
Received: FROM esealnt742.al.sw.ericsson.se BY esealnt409.al.sw.ericsson.se ; Tue Sep 25 09:21:51 2001 +0200
Received: by esealnt742.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <TH2J749H>; Tue, 25 Sep 2001 09:14:41 +0200
Message-ID: <034BEFD03799D411A59F00508BDF754603008CF6@esealnt448.al.sw.ericsson.se>
From: "Hesham Soliman  (ERA)" <Hesham.Soliman@era.ericsson.se>
To: "'Charlie Perkins'" <charliep@iprg.nokia.com>
Cc: mobile-ip@sunroof.eng.sun.com
Subject: RE: [mobile-ip] Draft 15
Date: Tue, 25 Sep 2001 09:21:39 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

> As best I can figure it out, one can use IPsec for authentication
> if you can get the selectors to select the right security association,
> but some (or most) implementations aren't selective enough
> to be assured of always picking out the right security association
> depending on which destination options (or future ones) may
> be in use.
> 
> So, I have made an authentication data sub-option that MUST be
> supported.  IPsec MAY be used instead, and if so I don't think
> that there is any additional specification within the Mobile IPv6
> document that is needed for this.  If IPsec is used, then the
> Authentication Data Sub-Option does not have to be present.
> 
	=> The issue is exactly what you mentioned in the first paragraph. 
	MIPv6 needs to solve the granularity problem since it is a MIPv6
	specific problem. So as discussed earlier we could create
	a new nxt Header value for the BU option, or write some 
	text about how to increases the selectors granularity in the 
	MN and the CN. Either way piggybacking will be very difficult if 
	possible at all. 
	So unfortunately we can't leave it the way it is because if we 
	say that IPsec MAY be supported then it has to be shown
	how it can be supported. 

	I believe that the concensus was that the first option (new
	nxt hdr) should be used.

> I hope this is good enough to satisfy the current needs, as well
> as the previous discussion about how we could not count on
> using IPsec in its current form.  I hope you like the new Sub-Option,
> and if you have suggestions about how to make better wording
> for allowing IPsec I'd be interested in that, too.
> 
	=> I could help with sending you some text if you like, provided
	we do agree with the assumptions above.

	Regards,
	Hesham


From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep 25 04:01:43 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA25353
	for <mobileip-archive@odin.ietf.org>; Tue, 25 Sep 2001 04:01:42 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id BAA28047;
	Tue, 25 Sep 2001 01:01:41 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id BAA24714;
	Tue, 25 Sep 2001 01:01:35 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8P80A7B025637
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 25 Sep 2001 01:00:10 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8P80A5M025636
	for mobile-ip-dist; Tue, 25 Sep 2001 01:00:10 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8P8067B025629
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 01:00:06 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id BAA11435
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 01:00:09 -0700 (PDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id BAA15022
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 01:00:09 -0700 (PDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id BAA04807;
	Tue, 25 Sep 2001 01:00:09 -0700 (PDT)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f8P809519955;
	Tue, 25 Sep 2001 01:00:09 -0700
X-mProtect:  Tue, 25 Sep 2001 01:00:09 -0700 Nokia Silicon Valley Messaging Protection
Received: from Icharliep-1.iprg.nokia.com (205.226.22.18, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpd9gA2W0; Tue, 25 Sep 2001 01:00:06 PDT
Message-ID: <3BB03866.1B247D18@iprg.nokia.com>
Date: Tue, 25 Sep 2001 00:55:18 -0700
From: Charlie Perkins <charliep@iprg.nokia.com>
Organization: Nokia
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Hesham Soliman (ERA)" <Hesham.Soliman@era.ericsson.se>
CC: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Draft 15
References: <034BEFD03799D411A59F00508BDF754603008CF6@esealnt448.al.sw.ericsson.se>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hello Hesham,

I'd rather have it that IPsec _may_ be supported if in the
future someone can figure out how to specify it.  In the
meantime, we can go forward with a spec that works,
without losing features and without having to do things
that may in the future be found inadequate within the IPsec
working group.  I really do think that the message we have
received more than once, is that we need to have a way to
do authentication without necessarily relying on IPsec.
This doesn't mean that IPsec can not be used.  I would
hope that the specification for using it would be in a
separate document, and that it would not delay the progress
of Mobile IPv6.

I'd have to go back and study a number of old messages
to figure out whether getting a new next header for
Binding Update was the consensus position.  I do recall
reading a lot of different opinions on the subject, ranging
from encapsulation, to putting all the Mobile IPv6 options
in the same header as suboptions, and probably a lot of
others that I can't remember right now.  I thought that
making the Sub-Option was the most middle-of-the
road course.

Regards,
Charlie P.



"Hesham Soliman (ERA)" wrote:

> > As best I can figure it out, one can use IPsec for authentication
> > if you can get the selectors to select the right security association,
> > but some (or most) implementations aren't selective enough
> > to be assured of always picking out the right security association
> > depending on which destination options (or future ones) may
> > be in use.
> >
> > So, I have made an authentication data sub-option that MUST be
> > supported.  IPsec MAY be used instead, and if so I don't think
> > that there is any additional specification within the Mobile IPv6
> > document that is needed for this.  If IPsec is used, then the
> > Authentication Data Sub-Option does not have to be present.
> >
>         => The issue is exactly what you mentioned in the first paragraph.
>         MIPv6 needs to solve the granularity problem since it is a MIPv6
>         specific problem. So as discussed earlier we could create
>         a new nxt Header value for the BU option, or write some
>         text about how to increases the selectors granularity in the
>         MN and the CN. Either way piggybacking will be very difficult if
>         possible at all.
>         So unfortunately we can't leave it the way it is because if we
>         say that IPsec MAY be supported then it has to be shown
>         how it can be supported.
>
>         I believe that the concensus was that the first option (new
>         nxt hdr) should be used.
>
> > I hope this is good enough to satisfy the current needs, as well
> > as the previous discussion about how we could not count on
> > using IPsec in its current form.  I hope you like the new Sub-Option,
> > and if you have suggestions about how to make better wording
> > for allowing IPsec I'd be interested in that, too.
> >
>         => I could help with sending you some text if you like, provided
>         we do agree with the assumptions above.
>
>         Regards,
>         Hesham



From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep 25 04:06:37 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA25388
	for <mobileip-archive@odin.ietf.org>; Tue, 25 Sep 2001 04:06:37 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id CAA00478;
	Tue, 25 Sep 2001 02:06:24 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id BAA25295;
	Tue, 25 Sep 2001 01:06:21 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8P84r7B025713
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 25 Sep 2001 01:04:53 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8P84rMh025712
	for mobile-ip-dist; Tue, 25 Sep 2001 01:04:53 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8P84n7B025705
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 01:04:49 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id BAA12017
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 01:04:52 -0700 (PDT)
Received: from laposte.enst-bretagne.fr (laposte.enst-bretagne.fr [192.108.115.3])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id CAA29287
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 02:04:40 -0600 (MDT)
Received: from rsm.rennes.enst-bretagne.fr (rsm.rennes.enst-bretagne.fr [192.44.77.1])
	by laposte.enst-bretagne.fr (8.11.6/8.11.6) with ESMTP id f8P84k924536;
	Tue, 25 Sep 2001 10:04:46 +0200
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr [193.52.74.194])
	by rsm.rennes.enst-bretagne.fr (8.8.8/8.8.8) with ESMTP id KAA15463;
	Tue, 25 Sep 2001 10:04:46 +0200 (MET DST)
Received: from givry.rennes.enst-bretagne.fr (localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.11.3/8.11.3) with ESMTP id f8P84kl22271;
	Tue, 25 Sep 2001 10:04:46 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200109250804.f8P84kl22271@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: "Charles E. Perkins" <charliep@iprg.nokia.com>
cc: Mobile IP Working Group <mobile-ip@sunroof.eng.sun.com>
Subject: Re: [mobile-ip] Coexistence with other uses for routing header 
In-reply-to: Your message of Mon, 24 Sep 2001 10:10:13 PDT.
             <3BAF68F5.644E0A68@iprg.nokia.com> 
Date: Tue, 25 Sep 2001 10:04:46 +0200
X-Virus-Scanned: by amavisd-milter (http://www.amavis.org/) at enst-bretagne.fr
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
 In your previous mail you wrote:

   >  In your previous mail you wrote:
   > 
   >    > PS: you have a similar issue when the source route is reversed,
   >    > the last (becomes the first) intermediate hop (i.e. the care-of address)
   >    > SHOULD be removed. If it is not, the first hop is the sender node
   >    > and if policy is to disable forwarding of source routed packet on hosts
   >    > (cf. a current thread in the IPv6 WG mailing list) one is in trouble.
   > 
   >    But the routing header does NOT require source route reversal,
   >    as best I understand it.
   > 
   > => RFC 2460 uses the word "permitted" but in fact reversing is done
   > if and only if there is a (valid) AH.
   > 
   >    If this isn't clear, then I think it
   >    should be made clear in the Mobile IPv6 text.
   > 
   > => I agree, this must be made clear in the Mobile IPv6 text.
   
   I checked, and I think the handling for Routing Headers is pretty
   clear in the text.  The mobile node doesn't put its care-of address
   in a routing header for the correspondent node, and the correspondent
   node checks its Binding Cache before putting in the care-of address
   into a Routing Header.  These cases are not in the danger zone of
   reversing "unauthorized" Routing Headers.
   
=> the issue is not in reversing "unauthorized" RHs, the issue is in
reversing "authorized" RHs from the correspondent node and keeping
the care-of address in them (the CoA is the last intermediate in
received RHs and in careless reversing the CoA becomes the first one).
 "Authorized" RHs are managed through reversing using the property than
reverse o reverse = Id, if the mobility adds something in the RH, the
other end SHOULD removes it. BTW your proposed text should avoid
spurious multiple additions of the CoA in RHs by the correspondent
if the mobile node doesn't apply my idea.

Thanks

Francis.Dupont@enst-bretagne.fr

PS: this is very easy to implement and changes are only in
the mobile node code.


From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep 25 04:28:41 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA25584
	for <mobileip-archive@odin.ietf.org>; Tue, 25 Sep 2001 04:28:40 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id BAA06862;
	Tue, 25 Sep 2001 01:28:40 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id BAA27685;
	Tue, 25 Sep 2001 01:28:32 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8P8RV7B025800
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 25 Sep 2001 01:27:31 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8P8RV8D025799
	for mobile-ip-dist; Tue, 25 Sep 2001 01:27:31 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8P8RR7B025792
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 01:27:27 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id BAA27624
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 01:27:26 -0700 (PDT)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id BAA07365
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 01:27:25 -0700 (PDT)
Received: from esealnt409.al.sw.ericsson.se (ESEALNT409.al.sw.ericsson.se [153.88.251.32])
	by penguin.wise.edt.ericsson.se (8.11.0/8.10.1/WIREfire-1.3) with SMTP id f8P8ROv07852
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 10:27:24 +0200 (MEST)
Received: FROM esealnt400.al.sw.ericsson.se BY esealnt409.al.sw.ericsson.se ; Tue Sep 25 10:27:23 2001 +0200
Received: by esealnt400 with Internet Mail Service (5.5.2653.19)
	id <THZ668DZ>; Tue, 25 Sep 2001 10:27:23 +0200
Message-ID: <034BEFD03799D411A59F00508BDF754603008CFE@esealnt448.al.sw.ericsson.se>
From: "Hesham Soliman  (ERA)" <Hesham.Soliman@era.ericsson.se>
To: "'Charlie Perkins'" <charliep@iprg.nokia.com>,
        "Hesham Soliman  (ERA)"
	 <Hesham.Soliman@era.ericsson.se>
Cc: mobile-ip@sunroof.eng.sun.com
Subject: RE: [mobile-ip] Draft 15
Date: Tue, 25 Sep 2001 10:27:02 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

	Hello Charlie, 

> I'd rather have it that IPsec _may_ be supported 
> 
	=. But the way the draft s written it can _not_ be supported. 
	If we have it in a separate draft we will end up
	with major interoperability problems.
	Since IPsec is mandated anyway for IPv6 hosts it 
	makes sense for us to use IPsec.

> if in the
> future someone can figure out how to specify it.  In the
> meantime, we can go forward with a spec that works,
> without losing features and without having to do things
> that may in the future be found inadequate within the IPsec
> working group.  
> 
	=> We seemed to have worked it out on the mailing list 
	over several weeks. I think it will work, I haven't seen
	any objection to having IPsec. Quite the contrary. 
	The discussion as on whether piggybacking should go or stay.

> I really do think that the message we have
> received more than once, is that we need to have a way to
> do authentication without necessarily relying on IPsec.
> 
	=> OK so that's where we have different understandings. 
	The message I understood was that we can not rely on IKE
	as the only key exchange mechanism. I don't recall disallowing
	IPsec at all. The problems were highlighted by the ADs 
	but they are definitely fixable without too much trouble.

	Regards,
	Hesham


> "Hesham Soliman (ERA)" wrote:
> 
> > > As best I can figure it out, one can use IPsec for authentication
> > > if you can get the selectors to select the right security association,
> > > but some (or most) implementations aren't selective enough
> > > to be assured of always picking out the right security association
> > > depending on which destination options (or future ones) may
> > > be in use.
> > >
> > > So, I have made an authentication data sub-option that MUST be
> > > supported.  IPsec MAY be used instead, and if so I don't think
> > > that there is any additional specification within the Mobile IPv6
> > > document that is needed for this.  If IPsec is used, then the
> > > Authentication Data Sub-Option does not have to be present.
> > >
> >         => The issue is exactly what you mentioned in the first paragraph.
> >         MIPv6 needs to solve the granularity problem since it is a MIPv6
> >         specific problem. So as discussed earlier we could create
> >         a new nxt Header value for the BU option, or write some
> >         text about how to increases the selectors granularity in the
> >         MN and the CN. Either way piggybacking will be very difficult if
> >         possible at all.
> >         So unfortunately we can't leave it the way it is because if we
> >         say that IPsec MAY be supported then it has to be shown
> >         how it can be supported.
> >
> >         I believe that the concensus was that the first option (new
> >         nxt hdr) should be used.
> >
> > > I hope this is good enough to satisfy the current needs, as well
> > > as the previous discussion about how we could not count on
> > > using IPsec in its current form.  I hope you like the new Sub-Option,
> > > and if you have suggestions about how to make better wording
> > > for allowing IPsec I'd be interested in that, too.
> > >
> >         => I could help with sending you some text if you like, provided
> >         we do agree with the assumptions above.
> >
> >         Regards,
> >         Hesham


From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep 25 04:35:57 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA25658
	for <mobileip-archive@odin.ietf.org>; Tue, 25 Sep 2001 04:35:57 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id CAA16285;
	Tue, 25 Sep 2001 02:35:46 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id BAA15361;
	Tue, 25 Sep 2001 01:35:50 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8P8Ye7B025864
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 25 Sep 2001 01:34:40 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8P8Yegf025863
	for mobile-ip-dist; Tue, 25 Sep 2001 01:34:40 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8P8Ya7B025856
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 01:34:36 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id BAA10532
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 01:34:39 -0700 (PDT)
Received: from albatross-ext.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id CAA14041
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 02:35:33 -0600 (MDT)
Received: from esealnt461 (esealnt461.al.sw.ericsson.se [153.88.251.61])
	by albatross.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id f8P8YbK01263
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 10:34:37 +0200 (MEST)
Received: FROM esealnt746.al.sw.ericsson.se BY esealnt461 ; Tue Sep 25 10:34:36 2001 +0200
Received: by ESEALNT746.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <THN5D54G>; Tue, 25 Sep 2001 10:34:36 +0200
Message-ID: <F7709E7648BAD41181E60008C716A2290105902F@edkchnt102.lmd.ericsson.se>
From: "Peter Grimstrup (TED)" <Peter.Grimstrup@lmd.ericsson.se>
To: "'Charles E. Perkins'" <charliep@iprg.nokia.com>
Cc: mobile-ip@sunroof.eng.sun.com
Subject: RE: [mobile-ip] Mobile IPv6 draft revision
Date: Tue, 25 Sep 2001 10:37:28 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Hi Charlie,

Sorry, but this discussion has been split up into a number of 
threads, thus I'm probably commenting in odd threads at odd 
times.

Peter
----------------------------------------------------------------
> 
> It seems to me that the following natural interpretation
> works well:
> 
> - The Source IP address is where the packet came from --
>   and thus where the Binding Acknowledgement should go.
> - The Alternate care-of address is the care-of address
>   that should be deregistered.  This conforms to the
>   specification for that Sub-Option.
> 
> But this is different than your interpretation.

I agree, your interpretation seems natural.
I guess my view is very much practical. When deregistrating, I do not
use the CoA *at all* to find the record in the Binding cache to be
deleted. The HoA is the key. Therefore the only (practical) use of an
alt-CoA in the deregistering is to direct the BA. 

> 
> Regards,
> Charlie P.
> 


From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep 25 04:46:00 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA25751
	for <mobileip-archive@odin.ietf.org>; Tue, 25 Sep 2001 04:45:59 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id CAA21688;
	Tue, 25 Sep 2001 02:45:49 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id BAA16070;
	Tue, 25 Sep 2001 01:45:52 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8P8ij7B025926
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 25 Sep 2001 01:44:45 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8P8ijV9025925
	for mobile-ip-dist; Tue, 25 Sep 2001 01:44:45 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8P8if7B025918
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 01:44:41 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id BAA15981
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 01:44:43 -0700 (PDT)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id BAA00781
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 01:44:42 -0700 (PDT)
Received: from esealnt409.al.sw.ericsson.se (ESEALNT409.al.sw.ericsson.se [153.88.251.32])
	by penguin.wise.edt.ericsson.se (8.11.0/8.10.1/WIREfire-1.3) with SMTP id f8P8ifv23219
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 10:44:41 +0200 (MEST)
Received: FROM esealnt742.al.sw.ericsson.se BY esealnt409.al.sw.ericsson.se ; Tue Sep 25 10:44:33 2001 +0200
Received: by esealnt742.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <TH2J75Y9>; Tue, 25 Sep 2001 10:37:23 +0200
Message-ID: <034BEFD03799D411A59F00508BDF754603008D00@esealnt448.al.sw.ericsson.se>
From: "Hesham Soliman  (ERA)" <Hesham.Soliman@era.ericsson.se>
To: "'mobile-ip@sunroof.eng.sun.com'" <mobile-ip@sunroof.eng.sun.com>,
        "Charles E. Perkins" <charliep@iprg.nokia.com>
Subject: RE: [mobile-ip] Comments on Mobile IPv6 draft 14
Date: Tue, 25 Sep 2001 10:44:23 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

> >>    back to it like in example of MN moving from A -> B -> C -> B network
> >>    and in which case, MN should deregister its earlier CoA with HA at B
> >>    (FH - Foreign Home, btw, pardon for my new terminology) as described
> >>    in Sec 10.20 but in addition, the draft should also clarify that MN
> >>    should register this primary CoA with its original HA.
> 
> > I didn't understand the problem here.  What does "HA" mean in the last
> > sentence?  I don't think there is a problem, unless the mobile node
> > is changing its home agent or home address somehow.  Basically, the
> > home agent just has a single care-of address for the mobile node,
> > and the care-of address is supposed to correspond exactly to the
> > current FN.  There would not be a need for the mobile node to
> > deregister previous care-of addresses at its home agent.
> 
>   Let us consider a scenario where MN moves from its home network 'A' to
>   foreign network 'B' and then to foreign network 'C'.
> 
>   After moving from network 'A' to network 'B', MN should have registered
>   (i.e. BU sent)its primary CoA picked up at 'B' with the home agent at
> 'A'.
>   Now, the HA at 'A' has a binding cache entry marked home registration.
> 
>   Next, the MN moves from 'B' to 'C', then, MN would send BU to the HA
>   at 'A' to request the change in cache entry with the new CoA just
> obtained
>   at 'C' and also to a home agent at 'B' to register its new CoA obtained
> at
>   'C' network. The registration with home agent at 'B' is required so that
>   packets addressed to its old CoA at B will now be tunnelled to its new
>   CoA at 'C'. Effectively, the MN now has one home agent at 'A', which I
>   called 'Original Home - OH' (because that's where its home was) and
> another
>   home agent at 'B' which I called 'Foreign Home - FH' at 'B'.
> 
>   Let us say that, after sometime, the MN came back from 'C' to 'B'
>   during its movement path and which means that MN can start reusing its
>   old COA at but before start using it there, it needs to deregister its
> CoA
>   at B with HA at 'B'; then sending a BU to its OH at 'A' with this CoA
>   at 'B'. Then, it will have to send a BU to HA at 'C' with the CoA at 'B'
>   to start tunnelling packets destined fro MN. In this case, the 'FH' is
>   effectively now moved 'B' to 'C'. In this case, it had to perform 3
> steps:
>   deregistration with 'B', registration with HA ('OH') at 'A' with CoA at
> 'B'
>   and registration with  HA ('FH') at 'C' with COA at 'B'.
> 
>   Hope I made this clear without making it too complicated. So, my point
>   is that the draft didn't consider a scenario like this and hence never
>   talked about deregistration with home agent on the foreign networks the
>   MN visited. 
> 
	=> I beleive that this is due to th fact that neither the data structures
	(Binding cache or BUL) nor the BUs distinguish between a "foreign HA" or a 
	"real HA". So the section on deregistering when connecting to the 
	Home network still applies to your scenario. 


	Hesham


From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep 25 05:00:53 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA25877
	for <mobileip-archive@odin.ietf.org>; Tue, 25 Sep 2001 05:00:52 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id DAA00103;
	Tue, 25 Sep 2001 03:00:37 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id CAA17410;
	Tue, 25 Sep 2001 02:00:40 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8P8xQ7B026074
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 25 Sep 2001 01:59:26 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8P8xPts026073
	for mobile-ip-dist; Tue, 25 Sep 2001 01:59:25 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8P8xM7B026066
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 01:59:22 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id BAA17234
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 01:59:24 -0700 (PDT)
Received: from laposte.enst-bretagne.fr (laposte.enst-bretagne.fr [192.108.115.3])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id CAA29294
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 02:59:11 -0600 (MDT)
Received: from rsm.rennes.enst-bretagne.fr (rsm.rennes.enst-bretagne.fr [192.44.77.1])
	by laposte.enst-bretagne.fr (8.11.6/8.11.6) with ESMTP id f8P8xH900871
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 10:59:17 +0200
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr [193.52.74.194])
	by rsm.rennes.enst-bretagne.fr (8.8.8/8.8.8) with ESMTP id KAA16262
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 10:59:18 +0200 (MET DST)
Received: from givry.rennes.enst-bretagne.fr (localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.11.3/8.11.3) with ESMTP id f8P8xHl22557
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 10:59:17 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200109250859.f8P8xHl22557@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Re: Connectathon input for Mobile IPv6 draft revision 
In-reply-to: Your message of Fri, 21 Sep 2001 13:53:12 PDT.
             <3BABA8B8.2D75B331@iprg.nokia.com> 
Date: Tue, 25 Sep 2001 10:59:17 +0200
X-Virus-Scanned: by amavisd-milter (http://www.amavis.org/) at enst-bretagne.fr
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
 In your previous mail you wrote:

   This requires further revision to the last text I sent out about
   deregistering care-of addresses:
   
       -  Otherwise, if the Source IP Address of the packet containing
          the Binding Update, is legal for inclusion in a Routing Header,
          the routing header will be constructed using that IP address.
          Note that multicast addresses, link-local addresses, and the
          unspecified address, MUST NOT be used within a Routing Header for
          the Binding Acknowledgement.
   
=> argh! Link-local addresses are legal in some cases, what is
forbidden is zone mismatch and/or ambiguity (i.e. the source, the
current destination and the next destination must be in the same zone,
in case of link-local in the same link).

   I also inserted the following prohibition within section 5.1:
   
       In any case, the care-of address MUST NOT be any IPv6 address
       which is prohibited for use within a Routing Header; thus
       multicast addresses, the unspecified address, loop-back address,
       and link-local addresses are excluded.  Binding Updates indicating
       any such excluded care-of address MUST be silently discarded.
   
=> same remark but I agree a link-local address must be prohibited
(i.e. the argument is wrong in its form but right in deep).
   
Regards

Francis.Dupont@enst-bretagne.fr

PS: I believe that Itojun would like to add IPv4 mapped addresses
in the list of forbidden address kinds.


From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep 25 05:57:02 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA26300
	for <mobileip-archive@odin.ietf.org>; Tue, 25 Sep 2001 05:57:01 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id CAA05347;
	Tue, 25 Sep 2001 02:57:01 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id CAA05833;
	Tue, 25 Sep 2001 02:56:50 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8P9tv7B026176
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 25 Sep 2001 02:55:58 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8P9tvxl026175
	for mobile-ip-dist; Tue, 25 Sep 2001 02:55:57 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from bebop.France.Sun.COM (bebop.France.Sun.COM [129.157.174.15])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8P9tr7B026168
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 02:55:53 -0700 (PDT)
Received: from lillen (lillen [129.157.212.23])
	by bebop.France.Sun.COM (8.10.2+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id f8P9tpg06659;
	Tue, 25 Sep 2001 11:55:52 +0200 (MET DST)
Date: Tue, 25 Sep 2001 11:51:25 +0200 (CEST)
From: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Subject: Re: [mobile-ip] Draft 15
To: charliep@iprg.nokia.com
Cc: "Hesham Soliman (ERA)" <Hesham.Soliman@era.ericsson.se>,
        mobile-ip@sunroof.eng.sun.com
In-Reply-To: "Your message with ID" <3BB03866.1B247D18@iprg.nokia.com>
Message-ID: <Roam.SIMC.2.0.6.1001411485.3654.nordmark@bebop.france>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

> I'd rather have it that IPsec _may_ be supported if in the
> future someone can figure out how to specify it.  In the
> meantime, we can go forward with a spec that works,
> without losing features and without having to do things
> that may in the future be found inadequate within the IPsec
> working group.  I really do think that the message we have
> received more than once, is that we need to have a way to
> do authentication without necessarily relying on IPsec.
> This doesn't mean that IPsec can not be used.  I would
> hope that the specification for using it would be in a
> separate document, and that it would not delay the progress
> of Mobile IPv6.

The use of the term "IPsec" might be inexact.
There is clearly a requirement to do authentication without relying on a PKI
and I think that this translates into being able to do authentication
without relying on IKE. (While IKE in theory doesn't assume certificates or
pre-shared secrets I suspect implementations do assume this.)
But it doesn't necessarily follow that authentication can not rely on
using AH and/or ESP. So what did "IPsec" mean above :-)

> I'd have to go back and study a number of old messages
> to figure out whether getting a new next header for
> Binding Update was the consensus position.  I do recall
> reading a lot of different opinions on the subject, ranging
> from encapsulation, to putting all the Mobile IPv6 options
> in the same header as suboptions, and probably a lot of
> others that I can't remember right now.  I thought that
> making the Sub-Option was the most middle-of-the
> road course.

I think there are two areas where the WG needs to make rough consensus
decisions: key management and packet authentication

For key management there needs to be a method that doesn't require a PKI
but I've also seen emails I've interpreted as a desire to use a PKI when
it is available. Thus it seems like there needs to be at least
two mechanisms here: IKE plus one that works without a PKI.
With more than one mechanism to choose there must also be a mechanism
for a MN to choose which one to use that is secure enough so that the MN
can't be tricked into using a less secure method when the more secure
one is indeed available.

For packet authentication there are also choices.
But if the desire to use a PKI when it is available is in fact WG rough 
consensus (something which the chairs get to guage), then
it seems like it would be a requirement to make MIPv6 work with the
constraints of AH/ESP and the IPsec architecture.
(Using IKE to create security associations for something other than
AH and ESP seems like it would require additional standards work in the
form of a DOI as I understand it.)
Once this work is done, it isn't obvious to me whether or not it makes
sense to also use AH/ESP for BUs when the key management is done without IKE.
It might be that AH/ESP is the simpler one. Or it might be that using
the sub-option when IKE isn't used is the best path.

But too me it seems a bit too early to have this last part
of the discussion - I don't feel I understand the tradeoffs yet and 
I haven't seen any discussion how a MN can choose between the PKI/IKE
key management and the alternate one before sending a BU. Do folks
have any ideas in that area?

  Erik



From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep 25 06:07:49 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA26397
	for <mobileip-archive@odin.ietf.org>; Tue, 25 Sep 2001 06:07:48 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id EAA08355;
	Tue, 25 Sep 2001 04:07:34 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id DAA07089;
	Tue, 25 Sep 2001 03:07:34 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8PA6Y7B026233
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 25 Sep 2001 03:06:34 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8PA6Yd2026232
	for mobile-ip-dist; Tue, 25 Sep 2001 03:06:34 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8PA6U7B026225
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 03:06:30 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id DAA23866
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 03:06:31 -0700 (PDT)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id DAA14112
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 03:06:29 -0700 (PDT)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by penguin.wise.edt.ericsson.se (8.11.0/8.10.1/WIREfire-1.3) with ESMTP id f8PA6Ov29229;
	Tue, 25 Sep 2001 12:06:25 +0200 (MEST)
Received: from lmf.ericsson.se (lmf4ws450.lmf.ericsson.se [131.160.38.50])
	by fogerty.lmf.ericsson.se (8.11.3/8.11.3) with ESMTP id f8PA6Ob04589;
	Tue, 25 Sep 2001 13:06:24 +0300 (EET DST)
Message-ID: <3BB05720.295D288C@lmf.ericsson.se>
Date: Tue, 25 Sep 2001 13:06:24 +0300
From: Jari Arkko <Jari.Arkko@lmf.ericsson.se>
Organization: Oy L M Ericsson Ab
X-Mailer: Mozilla 4.77 [en] (X11; U; SunOS 5.6 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: mobile-ip@sunroof.eng.sun.com
CC: "'Charlie Perkins'" <charliep@iprg.nokia.com>,
        "Hesham Soliman (ERA)" <Hesham.Soliman@era.ericsson.se>
Subject: Re: [mobile-ip] Draft 15
References: <034BEFD03799D411A59F00508BDF754603008CFE@esealnt448.al.sw.ericsson.se>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hesham (and Charlie) wrote:

>> I really do think that the message we have
>> received more than once, is that we need to have a way to
>> do authentication without necessarily relying on IPsec.
>> 
>  => OK so that's where we have different understandings. 
>     The message I understood was that we can not rely on IKE
>     as the only key exchange mechanism. I don't recall disallowing
>     IPsec at all. The problems were highlighted by the ADs 
>     but they are definitely fixable without too much trouble.

There is very clear consensus that we can't use IKE, i.e.
the key management part. There wasn't a very good consensus
on what to do with the actual packet protection, to use -14
or AH: a very long discussion was held in the mailing list,
discussing various issues such as options vs. new next header
numbers, piggybacking pros and cons, etc.

I would like to note that the latter issue is a bit more fine-
grained that "ipsec on" or "ipsec off". For instance, we do have
the option of (1) using standard ipsec as-is (possibly giving
up something else in the process such as piggybacking), (2)
enhancing ipsec (I'm not very fond of this alternative), (3)
using just -14 and bake and forgetting PKI-based schemes
for any environment, and (4) running both -14 for BUs and
ipsec/ike for all traffic on certain areas...

Anyway, I'm presently writing an Internet Draft that tries
to summarize the packet protection discussion and describe
the alternatives we have, their pros and cons, and effects
to e.g. piggybacking. I'm nearing completion in this work
and should be able to publish it Real Soon Now.

Jari


From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep 25 06:17:19 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA26495
	for <mobileip-archive@odin.ietf.org>; Tue, 25 Sep 2001 06:17:18 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id EAA13090;
	Tue, 25 Sep 2001 04:16:50 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id DAA08401;
	Tue, 25 Sep 2001 03:16:51 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8PAFq7B026301
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 25 Sep 2001 03:15:52 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8PAFqWE026300
	for mobile-ip-dist; Tue, 25 Sep 2001 03:15:52 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from bebop.France.Sun.COM (bebop.France.Sun.COM [129.157.174.15])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8PAFk7B026293
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 03:15:47 -0700 (PDT)
Received: from lillen (lillen [129.157.212.23])
	by bebop.France.Sun.COM (8.10.2+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id f8PAFhg10075;
	Tue, 25 Sep 2001 12:15:43 +0200 (MET DST)
Date: Tue, 25 Sep 2001 12:11:17 +0200 (CEST)
From: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Subject: Re: [mobile-ip] Draft 15
To: Jari.Arkko@lmf.ericsson.se
Cc: mobile-ip@sunroof.eng.sun.com,
        "'Charlie Perkins'" <charliep@iprg.nokia.com>,
        "Hesham Soliman (ERA)" <Hesham.Soliman@era.ericsson.se>
In-Reply-To: "Your message with ID" <3BB05720.295D288C@lmf.ericsson.se>
Message-ID: <Roam.SIMC.2.0.6.1001412677.3892.nordmark@bebop.france>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

> Anyway, I'm presently writing an Internet Draft that tries
> to summarize the packet protection discussion and describe
> the alternatives we have, their pros and cons, and effects
> to e.g. piggybacking. I'm nearing completion in this work
> and should be able to publish it Real Soon Now.

Jari,

Does this draft also go into issues when there is more than one
choice (e.g. IKE vs. BAKE to pick examples) and how the MN can pick on the fly?
Or are you just looking at the packet protection issue?

  Erik



From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep 25 06:57:34 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA26891
	for <mobileip-archive@odin.ietf.org>; Tue, 25 Sep 2001 06:57:33 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id DAA21129;
	Tue, 25 Sep 2001 03:56:16 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id DAA13202;
	Tue, 25 Sep 2001 03:56:11 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8PAtP7B026372
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 25 Sep 2001 03:55:25 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8PAtP49026371
	for mobile-ip-dist; Tue, 25 Sep 2001 03:55:25 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8PAtL7B026364
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 03:55:21 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id DAA27590;
	Tue, 25 Sep 2001 03:55:22 -0700 (PDT)
Received: from albatross-ext.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id EAA00226;
	Tue, 25 Sep 2001 04:55:09 -0600 (MDT)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by albatross.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with ESMTP id f8PAtHK23510;
	Tue, 25 Sep 2001 12:55:17 +0200 (MEST)
Received: from lmf.ericsson.se (lmf4ws450.lmf.ericsson.se [131.160.38.50])
	by fogerty.lmf.ericsson.se (8.11.3/8.11.3) with ESMTP id f8PAtGb06009;
	Tue, 25 Sep 2001 13:55:16 +0300 (EET DST)
Message-ID: <3BB06294.B2BC892@lmf.ericsson.se>
Date: Tue, 25 Sep 2001 13:55:16 +0300
From: Jari Arkko <Jari.Arkko@lmf.ericsson.se>
Organization: Oy L M Ericsson Ab
X-Mailer: Mozilla 4.77 [en] (X11; U; SunOS 5.6 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: Erik.Nordmark@eng.sun.com
CC: mobile-ip@sunroof.eng.sun.com, charliep@iprg.nokia.com,
        "Hesham Soliman (ERA)" <Hesham.Soliman@era.ericsson.se>
Subject: [mobile-ip] Choosing betwen PKI and "weak" global authentication
References: <Roam.SIMC.2.0.6.1001411485.3654.nordmark@bebop.france>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

(I'm changing the subject line to match what we discuss.)

>But too me it seems a bit too early to have this last part
>of the discussion - I don't feel I understand the tradeoffs yet and 
>I haven't seen any discussion how a MN can choose between the PKI/IKE
>key management and the alternate one before sending a BU. Do folks
>have any ideas in that area?

There are multiple ways of doing this, depending on what the
underlying BU packet protection scheme really is. In any case,
it is likely that the PKI/VPN policy mechanisms are relied upon in
making the decision you mention above.

For instance, let's assume we decide to use solely the BU suboption
for the authentication of BUs, and key this through BAKE. Then,
we might apply *in addition* PKI/IKE/IPsec on a particular organization
to allow for strong authentication of *all* traffic, including
the BUs. The IPsec policies would be set up, for instance, to
require IPsec for all traffic between all nodes. Or to require
IPsec for all traffic within the organization's own address space,
and nothing to the outside.

Another alternative would be to extend things like BAKE to
allow also for PKI authentication. This would require extending
them also to have some sort of policy mechanisms to decide
when to do this or not. (And the protocols might have to be
extended with the various authentication schemes people for
some reason want to use in their organizations, see what the
IPSRA group is doing as an example.)

A third alternative would be to use AH for protecting the
BUs, and allow the policy rules to dictate when to use IKE
and when e.g. BAKE. 

In any of these schemes, choosing dynamically between "weak"
and traditional authentication is tricky. It is easy to require
implementations to support both, and to configure one or the
other globally on. It is possible to configure both mechanisms
on at the same time, but given that the selection has to be
done without cryptographic authentication we need to rely to
the correctness of the IP addresses to an extent. Of course,
this may be the tradeoff the user wanted as he configured to
allow same traffic to be protected in different ways towards
different addresses. But the security implications should
be documented, so that users don't mistakenly trust the
functionality too much.

>Does this draft also go into issues when there is more than one
>choice (e.g. IKE vs. BAKE to pick examples) and how the MN can
>pick on the fly?

Yes. Though the security implications of the picking propably
deserve some discussion, and I haven't thought out all the
issues through yet.

Jari


From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep 25 10:24:38 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04705
	for <mobileip-archive@odin.ietf.org>; Tue, 25 Sep 2001 10:24:37 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id HAA05128;
	Tue, 25 Sep 2001 07:24:31 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id HAA04100;
	Tue, 25 Sep 2001 07:24:23 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8PENN7B026528
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 25 Sep 2001 07:23:23 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8PENN5p026527
	for mobile-ip-dist; Tue, 25 Sep 2001 07:23:23 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from bebop.France.Sun.COM (bebop.France.Sun.COM [129.157.174.15])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8PENE7B026520
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 07:23:15 -0700 (PDT)
Received: from lillen (lillen [129.157.212.23])
	by bebop.France.Sun.COM (8.10.2+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id f8PENEg04456
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 16:23:14 +0200 (MET DST)
Date: Tue, 25 Sep 2001 16:18:47 +0200 (CEST)
From: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Subject: [mobile-ip] Concerns/comments for aaa-keys and gen-key
To: mobile-ip@sunroof.eng.sun.com
In-Reply-To: "Your message with ID" <Roam.SIMC.2.0.6.1001422737.21505.nordmark@bebop.france>
Message-ID: <Roam.SIMC.2.0.6.1001427527.14101.nordmark@bebop.france>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

I've read draft-ietf-mobileip-aaa-key-08.txt and 
draft-ietf-mobileip-gen-key-01.txt and I have some significant comments and
concerns. Most of these comments is about aaa-key - the gen-key document
seems to be mostly a set of option formats without much behavioral protocol
specifications.

Some of these echo and perhaps extend the comments that Thomas generated
and that where forwarded to the mobile-ip mailing list on Aug 30.

High level comments (details below):
1. The scope of the problem and proposed solution isn't very clear.
2. The protocols outlined in the documents are very underspecified.
3. It is unclear what level of careful security review the documents
   have seen.
4. Between the lines there appear to be some architectural assumptions 
   e.g. that AAAh and HA have some high degree of mutual trust, which seem
   to imply that the solution might not be a good fit when the AAAh and
   HA are operated by different entities.


Scope/Applicability
-------------------

While the abstract talks solely of using this to create security associations
between MN-HA and MN-FA there appear to be other documents that appear to
use the same protocol mechanisms such as draft-le-aaa-lsa-tsk-00.txt.
While that draft doesn't specify packet formats it is using similar
techniques to those described in the aaa-keys draft. Currently there
is no way to tell whether the aaa-keys packet formats are intended to
be useful beyond the MN-HA and MN-FA security associations.

Thus what is needed is something indicating the applicability of aaa-keys.
Without knowing the applicability it is not possible to determine what
needs to be supported in terms of algorithms and key sizes, as
well as the constraints on how to negotiate what algorithm and key length
to use for a given SA.

Underspecification
------------------

As Thomas specified in depth there specification doesn't actual
contain message flows showing the interaction between MN, FA, HA, and the
AAA entities. 
(Who sends what to whom when? When processing occurs when a message is
received.)
Without this it is hard if not impossible to do a security analysis of
the specification.

The spec is completely silent on the need for re-keying and the
mechanism used to accomplish this.

The spec doesn't talk about algorithm negotiation?
I would assume that there needs to be at least one mandatory to implement 
algorithm to ensure that there is interoperability.

Does the protocol assume that the AAA exchanges provide confidentiality
or is it sufficient if the AAA exchanges provide integrity of the information
carried in the AAA protocol?


Security review
---------------

The security considerations section point out that there is
an assumption about the strength of the security for AAA being at least
as strong as the attempted security strength for the created security 
associations. Yet there doesn't seem to be a way for the protocol
to extract this information from AAA, in particular when there are
AAA proxies in the path. (If such information exists in a AAA draft
please provide a pointer.)

The document has a section on key derivation.
This section assumes that 64 bit randomness is sufficient, but this
depends on what current and future algorithms will be used (which is
related to the applicability of the protocol).

In general I think key derivation is a tricky thing. For some algorithms
the key derivation process must avoid weak keys. Yet the proposed mechanism
doesn't have a mechanism to do this.

The document talks about using the NAI to identify the user, which
might have privacy implications. While the NAI must have a stable domain
component (the part after the @ sign) in order to route to the right home
AAA server, but that doesn't inherently require that the component
before the @ sign be a fixed string like a user name.
Has there been any privacy review of this?
Are there any thoughts or proposals around using temporary IDs instead
of user names before the @ sign?


Architectural Assumptions
------------------------

Between the lines there appear to be some architectural assumptions 
e.g. that AAAh and HA have some high degree of mutual trust, which seem
to imply that the solution might not be a good fit when the AAAh and
HA are operated by different entities.

This assumption does not exist in RFC 2977 as far as I can tell.
Unless it is implicit in the term "home domain" (which is not defined
in RFC 2977) - that that term is supposed to be to both the location 
of the home AAA service and the location of the home routing service 
(i.e. the home agent).

It would seem unwise to have hard-code the requirement that the AAA home
and the IP address home is the same; folks have suggested scenarios
where the AAA home could be e.g. Visa and the routing home is
a home agent in the house (or elsewhere). Of course there
might also be scenarios when the are provided by the same administration e.g
when the same ISP/operator provides AAA and routing home.
So I think it makes sense to support both.

In the case when the AAAh and HA are different administrations then
I suspect that one needs to be able to have a different chain of trust -
with the MN-HA having the initial trust. But when they are the same 
administration it makes sense to have MN-AAAH be the initial trust that
is used to build the other trust relationships.

Thus I think this architectural issues will have an impact on the 
specification once the specification provides more detail.

----



From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep 25 10:55:51 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05635
	for <mobileip-archive@lists.ietf.org>; Tue, 25 Sep 2001 10:55:51 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id IAA10553;
	Tue, 25 Sep 2001 08:55:35 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id HAA10351;
	Tue, 25 Sep 2001 07:55:36 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8PEsZ7B026597
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 25 Sep 2001 07:54:35 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8PEsZMb026596
	for mobile-ip-dist; Tue, 25 Sep 2001 07:54:35 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8PEsV7B026589
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 07:54:31 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id HAA28828
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 07:54:32 -0700 (PDT)
Received: from laposte.enst-bretagne.fr (laposte.enst-bretagne.fr [192.108.115.3])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id HAA12772
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 07:54:30 -0700 (PDT)
Received: from rsm.rennes.enst-bretagne.fr (rsm.rennes.enst-bretagne.fr [192.44.77.1])
	by laposte.enst-bretagne.fr (8.11.6/8.11.6) with ESMTP id f8PEsF928280
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 16:54:15 +0200
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr [193.52.74.194])
	by rsm.rennes.enst-bretagne.fr (8.8.8/8.8.8) with ESMTP id QAA21703
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 16:54:16 +0200 (MET DST)
Received: from givry.rennes.enst-bretagne.fr (localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.11.3/8.11.3) with ESMTP id f8PEsFl23521
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 16:54:15 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200109251454.f8PEsFl23521@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Draft 15 
In-reply-to: Your message of Mon, 24 Sep 2001 14:07:53 PDT.
             <3BAFA0A9.A1520959@iprg.nokia.com> 
Date: Tue, 25 Sep 2001 16:54:15 +0200
X-Virus-Scanned: by amavisd-milter (http://www.amavis.org/) at enst-bretagne.fr
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
 In your previous mail you wrote:

   Here is the current draft:
   	http://people.nokia.net/charlep/txt/mobilev6/mobilev6.txt

=> charlep -> charliep   
   
   Here is a list of changes:
   
       -  Removed the Prefix Length field from the Binding Update.
      
=> I like the Prefix-Length==0 option and I am very displeased this
is no more possible. As there are many dangling references to the
Prefix Length I suggest to give this back!

I have another concern about movement detection (10.4, 10.6) which
makes the hidden and incorrect assumption that there is only one
candidate default router. No, mobile is not wireless only and
wireless is not cellular only.

Regards

Francis.Dupont@enst-bretagne.fr


From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep 25 11:13:48 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06126
	for <mobileip-archive@odin.ietf.org>; Tue, 25 Sep 2001 11:13:47 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA29242;
	Tue, 25 Sep 2001 08:13:48 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id IAA22076;
	Tue, 25 Sep 2001 08:13:34 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8PFCf7B026701
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 25 Sep 2001 08:12:41 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8PFCeA2026700
	for mobile-ip-dist; Tue, 25 Sep 2001 08:12:40 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8PFCb7B026693
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 08:12:37 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id IAA14617
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 08:12:38 -0700 (PDT)
Received: from laposte.enst-bretagne.fr (laposte.enst-bretagne.fr [192.108.115.3])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id IAA22824
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 08:12:37 -0700 (PDT)
Received: from rsm.rennes.enst-bretagne.fr (rsm.rennes.enst-bretagne.fr [192.44.77.1])
	by laposte.enst-bretagne.fr (8.11.6/8.11.6) with ESMTP id f8PFCX930840
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 17:12:33 +0200
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr [193.52.74.194])
	by rsm.rennes.enst-bretagne.fr (8.8.8/8.8.8) with ESMTP id RAA21920
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 17:12:33 +0200 (MET DST)
Received: from givry.rennes.enst-bretagne.fr (localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.11.3/8.11.3) with ESMTP id f8PFCXl23708
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 17:12:33 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200109251512.f8PFCXl23708@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Draft 15 
In-reply-to: Your message of Tue, 25 Sep 2001 09:21:39 +0200.
             <034BEFD03799D411A59F00508BDF754603008CF6@esealnt448.al.sw.ericsson.se> 
Date: Tue, 25 Sep 2001 17:12:33 +0200
X-Virus-Scanned: by amavisd-milter (http://www.amavis.org/) at enst-bretagne.fr
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

I support Hersham's position:
 - drop piggybacking
 - document a way to use IPsec
 - the simplest fix to the selector problem is a new next header value
   (or a well known UDP port if the previous solution is not available)

Thanks

Francis.Dupont@enst-bretagne.fr

PS: the random correspondent case is only one part of the whole picture,
MN-HA stuff is at least as important.


From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep 25 11:39:48 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06797
	for <mobileip-archive@lists.ietf.org>; Tue, 25 Sep 2001 11:39:48 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id JAA18805;
	Tue, 25 Sep 2001 09:39:37 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id IAA29229;
	Tue, 25 Sep 2001 08:39:42 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8PFcn7B026770
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 25 Sep 2001 08:38:49 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8PFcn2b026769
	for mobile-ip-dist; Tue, 25 Sep 2001 08:38:49 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8PFcj7B026762
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 08:38:45 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id IAA29024
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 08:38:47 -0700 (PDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id JAA19897
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 09:39:40 -0600 (MDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id IAA22198
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 08:38:45 -0700 (PDT)
X-Delivered-For: <mobile-ip@sunroof.eng.sun.com>
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f8PFciu05273
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 08:38:44 -0700
X-mProtect:  Tue, 25 Sep 2001 08:38:44 -0700 Nokia Silicon Valley Messaging Protection
Received: from charliep.iprg.nokia.com (205.226.2.89, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpdlUw6CE; Tue, 25 Sep 2001 08:38:20 PDT
Message-ID: <3BB0A4EC.C7E993F@iprg.nokia.com>
Date: Tue, 25 Sep 2001 08:38:20 -0700
From: "Charles E. Perkins" <charliep@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Draft 15
References: <200109251512.f8PFCXl23708@givry.rennes.enst-bretagne.fr>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hello Francis,

Francis Dupont wrote:
> 
> I support Hersham's position:
>  - drop piggybacking

I think this is far premature.  It has the potential to be a very
important improvement, and once gone it would be difficult to restore.

Sending Binding Updates along with data packets has many advantages:
- reduces number of media acquistions
- in the most natural implementations, reduces the total number
  of Binding Updates sent
- reduces number of bytes sent.

The crucial thing is to prevent Binding Updates from being sent
unnecessarily.  Any implementation which sends Binding Updates at
every change in point of connection to the Internet (or, even worse,
on every movement detection) is potentially doing a lot of
unnecessary signalling.  In contrast, an implementation that sends
Binding Updates in the first data packet going out after detecting
a change in the mobile node's point of attachment, is going to have
a lot less overheat.

This is a very important point.  Avoiding unnecessary signaling
should be one of our prime goals, considering that Mobile IPv6
is likely to be used over bandwidth-constrained media.

>  - document a way to use IPsec

That can be done separately, and it would be nice to avoid the
dangers of somehow running afoul of the sort of technical difficulties
that have brought us to this point.  I'm speaking as someone who was
(it seemed to me) the lone defender of using IPsec AH, during the
discussions at the end of last year.  I was told that doing this
could take a long time, which I thought was strange since we have
already had IPsec AH working in our prototype for a long time.
We can do things a lot faster by saying just exactly what we need,
and leaving it for later, or for others, to get agreement from
IPsec folks about how to use their protocol.

>  - the simplest fix to the selector problem is a new next header value
>    (or a well known UDP port if the previous solution is not available)

I don't have any problem with getting a new next header unless that
will somehow introduce (yet!) another delay factor.


Regards,
Charlie P.


From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep 25 11:58:18 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07444
	for <mobileip-archive@lists.ietf.org>; Tue, 25 Sep 2001 11:58:17 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id JAA05103;
	Tue, 25 Sep 2001 09:58:05 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id IAA24315;
	Tue, 25 Sep 2001 08:58:08 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8PFvD7B026896
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 25 Sep 2001 08:57:13 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8PFvDiQ026895
	for mobile-ip-dist; Tue, 25 Sep 2001 08:57:13 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from heliopolis.eng.sun.com (redcoast.Eng.Sun.COM [152.70.28.21])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8PFv97B026888
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 08:57:09 -0700 (PDT)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.eng.sun.com (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id IAA07103;
	Tue, 25 Sep 2001 08:57:12 -0700 (PDT)
Message-Id: <200109251557.IAA07103@heliopolis.eng.sun.com>
Date: Tue, 25 Sep 2001 08:57:11 -0700 (PDT)
From: James Kempf <James.Kempf@Sun.COM>
Subject: Re: [mobile-ip] Draft 15
To: mobile-ip@sunroof.eng.sun.com
Cc: charliep@iprg.nokia.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: rQKkroV4frLgH/SRsRoW+w==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Hi Charlie,

I had a suggestion for addition as the last paragraph in Section 6.5.
Section 6.5 discusses loosening the restriction on RA from 3 seconds
to between 0.5 and 1.5 second, in order to facilitate movement detection.
The text I'd be interested in seeing added is the following:

	In addition to increasing the frequency of advertisment,
	an access router MAY use any combination of mechanisms to
	detect when a mobile node has established a new link with the
	subnet serviced by the router and to inform the mobile node
	via a Router Advertisement of the mobile node's new
	point of attachment. An access router MAY unicast
	a Router Advertisement to a mobile node if it discovers
	that one has established a link, or it MAY multicast a
	Router Advertisement in response to link establishment
	rather than periodically. The intent is to speed up informing
	the mobile node of its new attachment point, to reduce the
	overall delay in establishing a new care of address.

The idea behind this text is to allow the access router the same
freedom to optimize as the mobile node is granted in the first
few paragraphs of Section 10, while still keeping the same simplicity,
generality, and interoperability of the standard MIPv6 movement detection 
algorithm.

Does this sound OK?

		jak

>X-mProtect: Mon, 24 Sep 2001 14:07:57 -0700 Nokia Silicon Valley Messaging 
Protection
>Date: Mon, 24 Sep 2001 14:07:53 -0700
>From: "Charles E. Perkins" <charliep@iprg.nokia.com>
>To: Mobile IP Working Group <mobile-ip@sunroof.eng.sun.com>
>CC: "Basavaraj Patil (NTC/Dallas)" <Basavaraj.Patil@nokia.com>, Phil Roberts 
<PRoberts@MEGISTO.com>
>Subject: [mobile-ip] Draft 15
>
>Hello folks,
>
>I have done a rough edit on revision 15 of Mobile IPv6.
>It needs some proofreading.  There may still be some problems
>left over because of eliminating the Mobile Router capability,
>and the "Prefix Length" field of the Binding Update.  Also,
>I am still puzzling over the e-mail about how a mobile node
>should get the link-layer address of the home agent when it
>returns home.
>
>Here is the current draft:
>	http://people.nokia.net/charlep/txt/mobilev6/mobilev6.txt
>
>
>
>Here is a list of changes:
>
>    -  Removed the Mobile Router Prefix Length Sub-Option
>   
>    -  Removed the Prefix Length field from the Binding Update.
>   
>    -  Reworded the specification so that the Home Agent now has to
>       perform Duplicate Address Detection for the mobile node's address
>       on all the prefixes for which the router is performing home agent
>       service.
>   
>    -  Removed the section about Mobile Routers
>   
>    -  Added the Authentication Data Sub-option; reorganized the section
>       about computing authentication data.
>    
>    -  Specified that the Home Agent lifetime is by default the same as
>       the Router lifetime, in a Router Advertisement.
>    
>    -  Specified that Binding Updates with zero lifetime and the 'A' bit
>       set should cause a Binding Acknowledgement to be sent back to the
>       Source IP address of the Binding Update.
>
>    -  Qualified the allowable times when a mobile node can send a
>       Binding Update to a correspondent node
>
>    -  Added text allowing the correspondent node to extend an existing
>       Routing Header by also including the care-of address as the entry
>       of a routing header to be visited immediately before the home
>       address.  In this way, for instance, the mobile node can be an
>       intermediate node of a path along the way to some other node.
>   
>    -  Removed the Home Address field from the Home Agent Address
>       Discovery Request Message.
>    
>    -  Noted that ICMP Unreachable forms a potential mechanism by which
>       a malicious node can cause a correspondent node to delete a valid
>       entry from its Binding Cache.
>
>    -  Specified that, when a router stops offering home agent services
>       by turning off the 'H' flag, the mobile node has to delete the
>       corresponding entry from its Home Agent list. 
>
>
>
>I'll wait a bit longer before sending it, depending on current
>mailing list discussion and any other comments that may be
>contributed.  Surely there will be some other changes that have
>to be made anyway, but it is possible to imagine that they will
>be small ones.
>
>
>Regards,
>Charlie P.



From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep 25 12:13:26 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07897
	for <mobileip-archive@lists.ietf.org>; Tue, 25 Sep 2001 12:13:25 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id KAA19540;
	Tue, 25 Sep 2001 10:13:09 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA27875;
	Tue, 25 Sep 2001 09:13:10 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8PGC87B026967
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 25 Sep 2001 09:12:08 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8PGC7sj026966
	for mobile-ip-dist; Tue, 25 Sep 2001 09:12:07 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8PGC17B026956
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 09:12:01 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA08383
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 09:12:03 -0700 (PDT)
Received: from fep01-app.kolumbus.fi (fep01-0.kolumbus.fi [193.229.0.41])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA08805
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 10:12:58 -0600 (MDT)
Received: from jariws1 ([62.248.238.238]) by fep01-app.kolumbus.fi
          (InterMail vM.5.01.03.08 201-253-122-118-108-20010628) with SMTP
          id <20010925161200.NLED11276.fep01-app.kolumbus.fi@jariws1>
          for <mobile-ip@sunroof.eng.sun.com>;
          Tue, 25 Sep 2001 19:12:00 +0300
Message-ID: <00ad01c145dc$d3ac7160$8a1b6e0a@arenanet.fi>
From: "Jari Arkko" <jari.arkko@kolumbus.fi>
To: <mobile-ip@sunroof.eng.sun.com>
References: <200109251512.f8PFCXl23708@givry.rennes.enst-bretagne.fr> <3BB0A4EC.C7E993F@iprg.nokia.com>
Subject: [mobile-ip] Re: AH vs. BU suboption and piggybacking
Date: Tue, 25 Sep 2001 19:12:08 +0300
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

(Changing subject line again...)

Charlie wrote:

> I think this is far premature.  It has the potential to be a very
> important improvement, and once gone it would be difficult to restore.

I agree that we need to understand the implications of keeping/removing
piggybacking.

> The crucial thing is to prevent Binding Updates from being sent
> unnecessarily.  Any implementation which sends Binding Updates at
> every change in point of connection to the Internet (or, even worse,
> on every movement detection) is potentially doing a lot of
> unnecessary signalling.  In contrast, an implementation that sends
> Binding Updates in the first data packet going out after detecting
> a change in the mobile node's point of attachment, is going to have
> a lot less overheat.

This optimization is indeed a crucial one. But perhaps it is not
tied to the concept of piggybacking itself but rather its about
the trigger that makes a MIP implementation send a BU? Even
an implementation that sends separate BUs and payload data
could achieve the above behavior, if the BU was sent at the
time we first see some traffic.

The effects of piggybacking are more related to complexity, and
the bandwidth consumed for the signaling. On a LAN, the bandwidth
doesn't matter but on a cellular link you do care. The trouble is that
there are many complicating factors on these links that make it less
easy to understand the bandwidth implications. 

On first look at the ROHC header compression, for instance,
it appears that an additional option within the Dest Opts
header (remember that it will always be present as it carries
the HA option on all packets) can be sent as a diff, while a
separate packet with a different protocol number will cause
a complete new header to be transmitted.

On the other hand, a very specific QoS channel may have been
reserved for e.g. a voice call stream and it is simply impossible
to squeze in additional bytes without forcing the packet to go
through best effort channels, delaying the packet long enough
to make it effectively useless when it arrives. Ok, maybe your
IPv6 mobile phone could use some intelligence to avoid this,
but the server at the other end wouldn't have a clue that it should
be avoiding piggybacked signals on the stream coming towards
the phone.

Jari





From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep 25 12:13:54 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07925
	for <mobileip-archive@odin.ietf.org>; Tue, 25 Sep 2001 12:13:53 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id JAA00759;
	Tue, 25 Sep 2001 09:13:43 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA27903;
	Tue, 25 Sep 2001 09:13:22 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8PGC57B026964
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 25 Sep 2001 09:12:05 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8PGC59x026963
	for mobile-ip-dist; Tue, 25 Sep 2001 09:12:05 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8PGC07B026949
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 09:12:00 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA27645
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 09:12:02 -0700 (PDT)
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id JAA19148
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 09:12:02 -0700 (PDT)
Received: from mira-sjc5-7.cisco.com (mira-sjc5-7.cisco.com [171.71.163.27])
	by sj-msg-core-1.cisco.com (8.11.3/8.9.1) with ESMTP id f8PGC2509441
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 09:12:02 -0700 (PDT)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-7.cisco.com (Mirapoint)
	with ESMTP id AAI19514;
	Tue, 25 Sep 2001 09:12:01 -0700 (PDT)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id JAA00775; Tue, 25 Sep 2001 09:12:01 -0700 (PDT)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15280.44241.284529.749005@thomasm-u1.cisco.com>
Date: Tue, 25 Sep 2001 09:12:01 -0700 (PDT)
To: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Draft 15
In-Reply-To: <3BB0A4EC.C7E993F@iprg.nokia.com>
References: <200109251512.f8PFCXl23708@givry.rennes.enst-bretagne.fr>
	<3BB0A4EC.C7E993F@iprg.nokia.com>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Charles E. Perkins writes:
 > The crucial thing is to prevent Binding Updates from being sent
 > unnecessarily.  Any implementation which sends Binding Updates at
 > every change in point of connection to the Internet (or, even worse,
 > on every movement detection) is potentially doing a lot of
 > unnecessary signalling.  In contrast, an implementation that sends
 > Binding Updates in the first data packet going out after detecting
 > a change in the mobile node's point of attachment, is going to have
 > a lot less overheat.

   I see no reason why an implementation cannot
   have the exact same behavior you suggest (which
   I think is correct) but instead of sending one
   packet, it sends two. With layer two header
   compression and blocking both the overhead and
   latency can be minimized where that's a concern.

 > >  - document a way to use IPsec
 > 
 > That can be done separately, and it would be nice to avoid the
 > dangers of somehow running afoul of the sort of technical difficulties
 > that have brought us to this point.

   I too am in agreement with Francis that this should both
   be a baseline requirement for MIPv6 given the threats
   against the HA/MN and that we should be able to use
   IPsec with no issues if we follow the set of rules
   outlined.
   
	Mike


From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep 25 12:32:03 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08516
	for <mobileip-archive@odin.ietf.org>; Tue, 25 Sep 2001 12:32:02 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id KAA06189;
	Tue, 25 Sep 2001 10:31:52 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA03093;
	Tue, 25 Sep 2001 09:31:53 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8PGUX7B027086
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 25 Sep 2001 09:30:33 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8PGUXtE027085
	for mobile-ip-dist; Tue, 25 Sep 2001 09:30:33 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8PGUT7B027078
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 09:30:29 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA11155
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 09:30:31 -0700 (PDT)
Received: from albatross-ext.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id KAA04725
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 10:30:19 -0600 (MDT)
Received: from esealnt462.al.sw.ericsson.se (ESEALNT462.al.sw.ericsson.se [153.88.251.62])
	by albatross.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id f8PGUTK25754
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 18:30:29 +0200 (MEST)
Received: FROM esealnt742.al.sw.ericsson.se BY esealnt462.al.sw.ericsson.se ; Tue Sep 25 18:30:20 2001 +0200
Received: by esealnt742.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <TH2J8VL0>; Tue, 25 Sep 2001 18:23:10 +0200
Message-ID: <034BEFD03799D411A59F00508BDF754603008D02@esealnt448.al.sw.ericsson.se>
From: "Hesham Soliman  (ERA)" <Hesham.Soliman@era.ericsson.se>
To: "'mobile-ip@sunroof.eng.sun.com'" <mobile-ip@sunroof.eng.sun.com>
Subject: RE: [mobile-ip] Draft 15
Date: Tue, 25 Sep 2001 18:30:11 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

	Hello Charlie, 


> I don't have any problem with getting a new next header unless that
> will somehow introduce (yet!) another delay factor.
> 
	=> I think it's _very_important for us to recognise what the 
	_real_ cause of the delay is. The real cause in terms of security
	was relying on IKE (which needs PKI) as the only key exchange
	mechanism. We've already discussed the use of IPsec for 
	weeks before and after London. 
	I haven't seen any comment suggesting the removal of IPsec, 
	the discussion was whether piggybacking should stay or go. 
	There are several ways of handling the IPsec problem
	I attempted to list some options in the thread titled
	"IPsec, IKE, MIPv6 and concensus" the first message
	was sent on 17th August, you can trace the thread from
	there. 
	Also Jari mentioned that he's documenting these discussoins
	in a draft coming out soon. 

	Hesham




From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep 25 12:33:39 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08600
	for <mobileip-archive@odin.ietf.org>; Tue, 25 Sep 2001 12:33:38 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id JAA11270;
	Tue, 25 Sep 2001 09:33:36 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA03500;
	Tue, 25 Sep 2001 09:33:20 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8PGWS7B027108
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 25 Sep 2001 09:32:28 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8PGWScv027107
	for mobile-ip-dist; Tue, 25 Sep 2001 09:32:28 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8PGWO7B027100
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 09:32:24 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA23435
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 09:32:26 -0700 (PDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA21253
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 10:33:20 -0600 (MDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id JAA25335;
	Tue, 25 Sep 2001 09:32:24 -0700 (PDT)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f8PGWNZ20042;
	Tue, 25 Sep 2001 09:32:23 -0700
X-mProtect:  Tue, 25 Sep 2001 09:32:23 -0700 Nokia Silicon Valley Messaging Protection
Received: from charliep.iprg.nokia.com (205.226.2.89, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpdFCB7GK; Tue, 25 Sep 2001 09:32:10 PDT
Message-ID: <3BB0B182.F600D4F3@iprg.nokia.com>
Date: Tue, 25 Sep 2001 09:32:02 -0700
From: "Charles E. Perkins" <charliep@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@kolumbus.fi>
CC: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Re: AH vs. BU suboption and piggybacking
References: <200109251512.f8PFCXl23708@givry.rennes.enst-bretagne.fr> <3BB0A4EC.C7E993F@iprg.nokia.com> <00ad01c145dc$d3ac7160$8a1b6e0a@arenanet.fi>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hello Jari,

Jari Arkko wrote:

>> The crucial thing is to prevent Binding Updates from being sent
>> unnecessarily.  Any implementation which sends Binding Updates at
>> every change in point of connection to the Internet (or, even worse,
>> on every movement detection) is potentially doing a lot of
>> unnecessary signalling.  In contrast, an implementation that sends
>> Binding Updates in the first data packet going out after detecting
>> a change in the mobile node's point of attachment, is going to have
>> a lot less overheat.

(I meant overhead :-)

> This optimization is indeed a crucial one. But perhaps it is not
> tied to the concept of piggybacking itself but rather its about
> the trigger that makes a MIP implementation send a BU? Even
> an implementation that sends separate BUs and payload data
> could achieve the above behavior, if the BU was sent at the
> time we first see some traffic.

This is generally true, except that it would be better to have
the Binding Update applied to the data which needed to be sent
at the same time.  If the Binding Update arrives first, all is
well and good, at the expense of delaying the data for another
slot or medium acquisition time.  If the Binding Update arrives
later, then smooth data delivery will be the casualty.

> The effects of piggybacking are more related to complexity, and
> the bandwidth consumed for the signaling. On a LAN, the bandwidth
> doesn't matter but on a cellular link you do care. The trouble is that
> there are many complicating factors on these links that make it less
> easy to understand the bandwidth implications.

True enough -- and, we have to build a Mobile IPv6 that can work
well with all of them.

> On first look at the ROHC header compression, for instance,
> it appears that an additional option within the Dest Opts
> header (remember that it will always be present as it carries
> the HA option on all packets) can be sent as a diff, while a
> separate packet with a different protocol number will cause
> a complete new header to be transmitted.

Good point.

> On the other hand, a very specific QoS channel may have been
> reserved for e.g. a voice call stream and it is simply impossible
> to squeze in additional bytes without forcing the packet to go
> through best effort channels, delaying the packet long enough
> to make it effectively useless when it arrives. Ok, maybe your
> IPv6 mobile phone could use some intelligence to avoid this,
> but the server at the other end wouldn't have a clue that it should
> be avoiding piggybacked signals on the stream coming towards
> the phone.

I would expect this to be part of the QoS negotiation.  Furthermore,
it depends on very special properties of the voice encoding and
channel utilization.  Thus, we need to make it so that such applications
are supported well, and still so that other applications with different
constraints are equally well supported.

Thus, I again suggest that we really need to allow Binding Updates
and data to live in the same IPv6 packet.  Making data streams fit
into reserved channels of exactly prescribed bandwidth is a very
interesting problem; I am sure we can make a solution to that
problem which handles Binding Updates correctly -- likely as part
of a separable ("non-piggybacked") signaling algorithm.  This should
not penalize the other applications that do not have the same
constraint.

Regards,
Charlie P.


From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep 25 12:58:04 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA09419
	for <mobileip-archive@odin.ietf.org>; Tue, 25 Sep 2001 12:58:03 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id KAA00022;
	Tue, 25 Sep 2001 10:57:47 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA09819;
	Tue, 25 Sep 2001 09:57:47 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8PGul7B027274
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 25 Sep 2001 09:56:47 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8PGulFD027273
	for mobile-ip-dist; Tue, 25 Sep 2001 09:56:47 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8PGuh7B027266
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 09:56:43 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA09463;
	Tue, 25 Sep 2001 09:56:45 -0700 (PDT)
Received: from sj-msg-core-2.cisco.com (sj-msg-core-2.cisco.com [171.69.24.11])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id JAA14890;
	Tue, 25 Sep 2001 09:56:45 -0700 (PDT)
Received: from mira-sjc5-7.cisco.com (mira-sjc5-7.cisco.com [171.71.163.27])
	by sj-msg-core-2.cisco.com (8.11.3/8.9.1) with ESMTP id f8PGukd24246;
	Tue, 25 Sep 2001 09:56:46 -0700 (PDT)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-7.cisco.com (Mirapoint)
	with ESMTP id AAI20803;
	Tue, 25 Sep 2001 09:56:43 -0700 (PDT)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id JAA00778; Tue, 25 Sep 2001 09:56:43 -0700 (PDT)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15280.46923.497792.293898@thomasm-u1.cisco.com>
Date: Tue, 25 Sep 2001 09:56:43 -0700 (PDT)
To: mobile-ip@sunroof.eng.sun.com
Cc: Erik.Nordmark@eng.sun.com, charliep@iprg.nokia.com,
        "Hesham Soliman (ERA)" <Hesham.Soliman@era.ericsson.se>
Subject: [mobile-ip] No keying for "weak" global authentication
In-Reply-To: <3BB06294.B2BC892@lmf.ericsson.se>
References: <Roam.SIMC.2.0.6.1001411485.3654.nordmark@bebop.france>
	<3BB06294.B2BC892@lmf.ericsson.se>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Jari Arkko writes:
 > Another alternative would be to extend things like BAKE to
 > allow also for PKI authentication. This would require extending
 > them also to have some sort of policy mechanisms to decide
 > when to do this or not. (And the protocols might have to be
 > extended with the various authentication schemes people for
 > some reason want to use in their organizations, see what the
 > IPSRA group is doing as an example.)

   In fact, I believe that the basic mechanism for
   weak authentication SHOULD NOT include keying at
   all. The reason is that the actual security property
   being enforced by all of these proposals is the return
   routability test, *not* the keying. The keying is an
   optimization for subsequent updates so that it does
   not need to perform the full return routability test
   each time.

   In interest of getting this spec done soon, I urge
   the working group to keep the weak test as simple
   as possible which means that it must not include
   any provisions for keying and/or proxying binding
   updates return routability tests on things like
   the home agent. The second you start adding
   lots of crypto, people's eyes glaze over and
   there is a real threat that route optimization
   will be ignored if its security module is
   considered too onerous. Considering that the
   crypto is an optmization, that would be a real
   shame.

   This may seem strange coming from somebody
   who's written a draft which proposes a solution
   with the base test along with the two
   optimizations, but I've also had time to
   reflect on what is necessary and what is 
   optional. I still think that both of the 
   optimiztions would be useful additions to
   MIPv6 (along with MR support as well), but 
   at this point I think it would be far more
   prudent to pursue those optimizations as a 
   separate WG item so that we can finish the
   current MIPv6 draft as soon as possible.

	    Mike


From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep 25 13:11:45 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09669
	for <mobileip-archive@odin.ietf.org>; Tue, 25 Sep 2001 13:11:45 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id LAA13147;
	Tue, 25 Sep 2001 11:11:32 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id KAA13972;
	Tue, 25 Sep 2001 10:11:33 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8PHAU7B027395
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 25 Sep 2001 10:10:30 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8PHATGN027394
	for mobile-ip-dist; Tue, 25 Sep 2001 10:10:29 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8PHAQ7B027387
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 10:10:26 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id KAA13790
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 10:10:28 -0700 (PDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id LAA12026
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 11:10:17 -0600 (MDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id KAA27899
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 10:10:27 -0700 (PDT)
X-Delivered-For: <mobile-ip@sunroof.eng.sun.com>
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f8PHARI23071
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 10:10:27 -0700
X-mProtect:  Tue, 25 Sep 2001 10:10:27 -0700 Nokia Silicon Valley Messaging Protection
Received: from vijayd.iprg.nokia.com (205.226.2.94, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpdw6EqIz; Tue, 25 Sep 2001 10:10:25 PDT
Message-ID: <3BB0BA81.E04F0959@iprg.nokia.com>
Date: Tue, 25 Sep 2001 10:10:25 -0700
From: Vijay Devarapalli <vijayd@iprg.nokia.com>
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Draft 15
References: <034BEFD03799D411A59F00508BDF754603008D02@esealnt448.al.sw.ericsson.se>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

"Hesham Soliman (ERA)" wrote:
> 
>         Hello Charlie,
> 
> > I don't have any problem with getting a new next header unless that
> > will somehow introduce (yet!) another delay factor.
> >
>         => I think it's _very_important for us to recognise what the
>         _real_ cause of the delay is. The real cause in terms of security
>         was relying on IKE (which needs PKI) as the only key exchange
>         mechanism. We've already discussed the use of IPsec for
>         weeks before and after London.
>         I haven't seen any comment suggesting the removal of IPsec,
>         the discussion was whether piggybacking should stay or go.
>         There are several ways of handling the IPsec problem
>         I attempted to list some options in the thread titled
>         "IPsec, IKE, MIPv6 and concensus" the first message
>         was sent on 17th August, you can trace the thread from
>         there.
>         Also Jari mentioned that he's documenting these discussoins
>         in a draft coming out soon.

getting a new next header will cause a delay. this should be pursued
separately and should not be in the MIPv6 spec.

Vijay

> 
>         Hesham


From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep 25 13:31:25 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10165
	for <mobileip-archive@odin.ietf.org>; Tue, 25 Sep 2001 13:31:24 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA14140;
	Tue, 25 Sep 2001 10:31:04 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id KAA18531;
	Tue, 25 Sep 2001 10:28:06 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8PHR47B027492
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 25 Sep 2001 10:27:04 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8PHR4Su027491
	for mobile-ip-dist; Tue, 25 Sep 2001 10:27:04 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8PHR17B027484
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 10:27:01 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id KAA18192
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 10:27:03 -0700 (PDT)
Received: from laposte.enst-bretagne.fr (laposte.enst-bretagne.fr [192.108.115.3])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id KAA08720
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 10:27:02 -0700 (PDT)
Received: from rsm.rennes.enst-bretagne.fr (rsm.rennes.enst-bretagne.fr [192.44.77.1])
	by laposte.enst-bretagne.fr (8.11.6/8.11.6) with ESMTP id f8PHR0923235
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 19:27:00 +0200
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr [193.52.74.194])
	by rsm.rennes.enst-bretagne.fr (8.8.8/8.8.8) with ESMTP id TAA23421
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 19:27:00 +0200 (MET DST)
Received: from givry.rennes.enst-bretagne.fr (localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.11.3/8.11.3) with ESMTP id f8PHR0l24678
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 19:27:00 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200109251727.f8PHR0l24678@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Draft 15 
In-reply-to: Your message of Tue, 25 Sep 2001 08:38:20 PDT.
             <3BB0A4EC.C7E993F@iprg.nokia.com> 
Date: Tue, 25 Sep 2001 19:27:00 +0200
X-Virus-Scanned: by amavisd-milter (http://www.amavis.org/) at enst-bretagne.fr
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
 In your previous mail you wrote:

   > I support Hersham's position:
   >  - drop piggybacking
   
   I think this is far premature.  It has the potential to be a very
   important improvement

=> IMHO for the moment it was only a burden.

   and once gone it would be difficult to restore.

=> from my point of view this is not a bad point (:-)!
   
   Sending Binding Updates along with data packets has many advantages:
   - reduces number of media acquistions

=> ?

   - in the most natural implementations, reduces the total number
     of Binding Updates sent

=> I believe the argument is delayed BUs, isn't it? This relies on
a specific traffic pattern, for instance no request-like traffic from
correspondents.

   - reduces number of bytes sent.
   
=> you have to prove this when MTU discovery and ROHC compression
is broken.

   The crucial thing is to prevent Binding Updates from being sent
   unnecessarily.  Any implementation which sends Binding Updates at
   every change in point of connection to the Internet (or, even worse,
   on every movement detection) is potentially doing a lot of
   unnecessary signalling.

=> see my answer to the last point.

   In contrast, an implementation that sends
   Binding Updates in the first data packet going out after detecting
   a change in the mobile node's point of attachment, is going to have
   a lot less overheat.
   
=> until one of its poor correspondents sends a packet to its previous
location which is no more valid...

   This is a very important point.  Avoiding unnecessary signaling
   should be one of our prime goals, considering that Mobile IPv6
   is likely to be used over bandwidth-constrained media.
   
=> if you need to optimise this particular case perhaps the best solution
is to avoid routing optimization (the extra travel of packets, if any,
will be on a very fast backbone) and to rely on ROHC in order to remove
the cost of encapsulation from the HA to the MN. So the signaling will
occur on with HAs (something we can't delay or avoid).

   >  - document a way to use IPsec
   
   That can be done separately

=> Hersham explained (far better than I can) why this should not be done
separately.

   I'm speaking as someone who was (it seemed to me) the lone defender
   of using IPsec AH, during the discussions at the end of last year.

=> I had the same impression, to be in the IPsec AH camp was an ordeal...

   I was told that doing this could take a long time, which I thought was
   strange since we have already had IPsec AH working in our prototype
   for a long time.

=> your implementation was known to work only because there was a second
one (:-).

   We can do things a lot faster by saying just exactly what we need,
   and leaving it for later, or for others, to get agreement from
   IPsec folks about how to use their protocol.
   
=> hum, the issue is the argument shall be the same from IPsec folk
(i.e. what we shall have to change in Mobile IPv6 in order to fit
with IPsec)... IPsec folk are ready to help us, don't say "wait, we
finish this, after you'll say what we should have done".

Thanks

Francis.Dupont@enst-bretagne.fr


From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep 25 13:47:08 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10492
	for <mobileip-archive@odin.ietf.org>; Tue, 25 Sep 2001 13:47:07 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id LAA15273;
	Tue, 25 Sep 2001 11:46:55 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id KAA02541;
	Tue, 25 Sep 2001 10:47:00 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8PHk57B027622
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 25 Sep 2001 10:46:05 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8PHk4vA027621
	for mobile-ip-dist; Tue, 25 Sep 2001 10:46:04 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8PHk17B027614
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 10:46:01 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id KAA22785
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 10:46:02 -0700 (PDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id LAA14153
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 11:45:50 -0600 (MDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id KAA00756
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 10:46:00 -0700 (PDT)
X-Delivered-For: <mobile-ip@sunroof.eng.sun.com>
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f8PHk0D28592
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 10:46:00 -0700
X-mProtect:  Tue, 25 Sep 2001 10:46:00 -0700 Nokia Silicon Valley Messaging Protection
Received: from vijayd.iprg.nokia.com (205.226.2.94, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpdKuBMwH; Tue, 25 Sep 2001 10:45:57 PDT
Message-ID: <3BB0C2D5.540E1781@iprg.nokia.com>
Date: Tue, 25 Sep 2001 10:45:57 -0700
From: Vijay Devarapalli <vijayd@iprg.nokia.com>
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Draft 15
References: <200109251727.f8PHR0l24678@givry.rennes.enst-bretagne.fr>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Francis Dupont wrote:

>    Sending Binding Updates along with data packets has many advantages:
>    - reduces number of media acquistions
> 
> => ?
> 
>    - in the most natural implementations, reduces the total number
>      of Binding Updates sent
> 
> => I believe the argument is delayed BUs, isn't it? This relies on
> a specific traffic pattern, for instance no request-like traffic from
> correspondents.
> 
>    - reduces number of bytes sent.
> 
> => you have to prove this when MTU discovery and ROHC compression
> is broken.

strongly disagree!! neither would be broken.

>    >  - document a way to use IPsec
> 
>    That can be done separately
> 
> => Hersham explained (far better than I can) why this should not be done
> separately.

i prefer a separate draft which explains how AH can be used with 
MIPv6. and the requirements like (new next header, disable piggybacking)
for AH to work can be present in that draft. and it can advance at its 
own pace.

vijay


From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep 25 13:51:56 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10599
	for <mobileip-archive@odin.ietf.org>; Tue, 25 Sep 2001 13:51:56 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id LAA19683;
	Tue, 25 Sep 2001 11:51:45 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id KAA04167;
	Tue, 25 Sep 2001 10:51:49 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8PHp97B027713
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 25 Sep 2001 10:51:10 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8PHp9i0027712
	for mobile-ip-dist; Tue, 25 Sep 2001 10:51:09 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from heliopolis.eng.sun.com (heliopolis.Eng.Sun.COM [152.70.1.39])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8PHp67B027705
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 10:51:06 -0700 (PDT)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.eng.sun.com (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id KAA12378
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 10:51:07 -0700 (PDT)
Message-Id: <200109251751.KAA12378@heliopolis.eng.sun.com>
Date: Tue, 25 Sep 2001 10:51:06 -0700 (PDT)
From: James Kempf <James.Kempf@Sun.COM>
Subject: RE: [mobile-ip] New BETH Draft
To: mobile-ip@sunroof.eng.sun.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: J5pmxsTfmzPPKAlU5y5oGA==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Hesham,

>> While the MN is in the no-coverage area, it will be using the
>> standard MIPv6 algorithm for handover (soliciting for RtAdv
>> or waiting until the AR sends them). How does it know
>> to transition to not soliciting and allowing the network
>> to perform the handover?
>> 
>	=> Why should it know or suppress rtr_sol ? My understanding 
>	has been that the entire point of BETH was that some 
>	link layers have certain timing restrictions and are not 
>	flexible enough to allow for MIP to be integrated in their
>	radio. But now it seems like you're adding something 
>	else: suppresing rtr_sol. I don't think we need to do that. 
>

Hmm, well, let me try again. I think we both agree that one way a MN gets a 
RtAdv in standard MIPv6 is to send a SolRtAdv and that the MN could do this 
solicitation based on an L2 trigger, right?

Suppose the MN is moving in a coverage area in which the access
routers use the standard MIPv6 algorithm. In this coverage area,
the MN responds to the L2 trigger by sending SolRtAdv, receiving
a RtAdv in response. So you have these messages going out over
the air from the MN in response to its L2 handover.

Now, suppose the MN moves to a coverage area in which BETH is available.
Up until this point, the MN has been doing the SolRtAdv. How does
it know to stop doing the SolRtAdv and simply wait for the AR
to set up the tunnels? Can you give me a simple
explanation of how this would work without some kind of 
exchange between the MN and AR to let the MN know that things
have changed and it can now receive optimized service?

>	We MUST distinguish between implementation issues
>	and protocol issues. If I'm designing an IPv6 stack to 
>	work in system foo, where foo has certain limitations 
>	then I'll consider that in my design of the stack. BETH 
>	has a narrow scope of use and is not designed to work
>	in all cases so let's keep it that way. 
>

I think it is an interoperability issue. You want to allow a BETH-capable
MN to operate optimally in an nonBETH network, and to transition. Also,
we are not just talking about BETH here. The same issues arise with
transitioning between an FMIPv6 and a standard MIPv6 (SMIPv6?) coverage area

>	Seriously let's not make things so unbeleivably complex that
>	they become useless in practice. 
>

I agree 100%. And if you can explain to me how to interoperably manage the
following transitions:

	FMIPv6 coverage <-> Standard MIPv6 coverage
	BETH coverage <-> Standard MIPv6 coverage
	
without adding having the MN and AR know what the other is capable of,
I'll be happy. Rajeev and I discussed this extensively on the list,
and having the MN and AR exchange this information seemed like the
right way to go, but I am certainly open to better suggestions if
you have one.

>
>> >Also for MIPv6 if the MN sends a BU to oAR and it is not
>> >capable then the BU will be dropped.
>> >
>> 
>> I don't follow.
>> 
>	=> The aim was to say that you can't guarantee that every router
>	will support all functions required. MIPv6 does not require 
>	routers to add an option in the RA stating whether it will 
>	accept BUs or not. The protocol is robust enough to handle
>	that.
>

Well, I consider this a bug in the MIPv6 spec. It must be possible
to suppress unnecessary on the air signalling when radio spectrum
is expensive. Service providers are not going to deploy MIPv6 if
they have to put up with gratuitous use of expensive spectrum, or
they are going to insist that vendors do something to allow
supressing it that may result in non-interoperable implementations. 
I haven't studied this issue closely enough to
make a recommendation about how to avoid it, however.

>> >In BETH, there is no involvment from the MN anyway so 
>> >no need to advertise. 
>> >
>> 

That's the whole point of what I'm trying to say. How is the
the MN told when to stop being involved in a transition situation?

>> Sure, but the MN must know when to suppress sending SolRtPr
>> if the AR can handle the handover via BETH.
>> 
>	=> New requirement and is not relevant to mobility management. 
>	We should not solve all problems within MIP. If the MN solicits
>	and gets a new RA, normal MIPv6 will take place. 
>

Right, but if it doesn't have to solicit, or if it should use
a RtSolPr instead, then what? How does it know to use FMIPv6
or BETH instead of SMIPv6?

>	=> These are statements based on some architecture that you're
>	thinking about. RAs in general can be sent as often as the 
>	network administrator wants them to be. 4 bytes plus many other
>	bytes will lead to fragmentation over slow links and unnecessary
>	delays. I don't know why we need it, the protocol will still
>	work very well.
>	Anyway, I don't think you can have a 4 byte-long option in the RA. 
>	I always get confused with the alignment requirements but I
>	beleive it's 8n for RAs.
>

OK, without actually going through the numbers, I can see your argument
that the additional 8 bytes may outweigh the savings on the 
handover if the AR is advertising very frequently.

Another possibility is to use the ICMP code field. According to RFC
2463, the code is used to create "another level of granularity". 
Neither the RA or the SolRA specify any codes for RA and SolAR, 
so there would be no conflict if a code were used.
Alternatively, the bit field could be used. Both the RA and SolRA
have empty bit fields. SolRA has 4 bytes of Reserved, RA has
5 bits.

>	=> The same analogy applies when a MN performs standard
>	MIPv6 and send a BU (to anyone apart fron the HA) it may be accepted
>	or dropped. So why is this any different ?? 
>

Like I said, that's a bug IMHO.

		jak



From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep 25 14:15:48 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11106
	for <mobileip-archive@odin.ietf.org>; Tue, 25 Sep 2001 14:15:47 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA09590;
	Tue, 25 Sep 2001 11:15:06 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id LAA07088;
	Tue, 25 Sep 2001 11:00:56 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8PHxt7B027786
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 25 Sep 2001 10:59:56 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8PHxtLU027785
	for mobile-ip-dist; Tue, 25 Sep 2001 10:59:55 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8PHxq7B027778
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 10:59:52 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id KAA08521
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 10:59:53 -0700 (PDT)
Received: from megisto-sql1.megisto.com ([63.113.114.132])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id KAA15816
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 10:59:53 -0700 (PDT)
Received: by megisto-sql1.megisto.com with Internet Mail Service (5.5.2650.21)
	id <TFN8SR0W>; Tue, 25 Sep 2001 13:57:52 -0400
Message-ID: <CD8355C7E19ED411BD5F00508BB0D19D69811F@megisto-sql1.megisto.com>
From: Phil Roberts <PRoberts@megisto.com>
To: "'mobile-ip@sunroof.eng.sun.com'" <mobile-ip@sunroof.eng.sun.com>
Subject: [mobile-ip] security and MIPv6
Date: Tue, 25 Sep 2001 13:57:52 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Hi folks,

   it's still premature at this point to be discussing what MUST and MAY be
supported in the
way of securing binding updates for route optimization.  Here are the
upcoming steps re: getting
the security story together for mobile-ip:


- The security requirements and threat analysis has been revised and
is about to be published as a working group document, and we will
immediately
issue a last call for comments.
- Gabriel has agreed to begin a document assessing proposed approaches
against the above requirements and threat analysis with a view to assessing
which approaches meet the requirements and where there are gaps.
- Jari Arkko has agreed to produce a summary document outlining the issues
involved in determining how best to protect binding updates, ranging from
a mobile IP specific implementation to various approaches using IPSEC
including issues with current implementations.

Until these documents have been discussed by the working group everyone
should understand
the security aspects of Mobile IP v6 are very much subject to change.

Phil


From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep 25 14:17:37 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11138
	for <mobileip-archive@odin.ietf.org>; Tue, 25 Sep 2001 14:17:37 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id MAA12831;
	Tue, 25 Sep 2001 12:17:21 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id LAA13513;
	Tue, 25 Sep 2001 11:17:25 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8PIGP7B027857
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 25 Sep 2001 11:16:25 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8PIGPua027856
	for mobile-ip-dist; Tue, 25 Sep 2001 11:16:25 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8PIGK7B027845
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 11:16:21 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id LAA13550
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 11:16:09 -0700 (PDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id LAA06618
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 11:16:08 -0700 (PDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id LAA03440
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 11:16:07 -0700 (PDT)
X-Delivered-For: <mobile-ip@sunroof.eng.sun.com>
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f8PIG6e29632
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 11:16:06 -0700
X-mProtect:  Tue, 25 Sep 2001 11:16:06 -0700 Nokia Silicon Valley Messaging Protection
Received: from charliep.iprg.nokia.com (205.226.2.89, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpdj1f0vi; Tue, 25 Sep 2001 11:16:04 PDT
Message-ID: <3BB0C9E5.1BD30A84@iprg.nokia.com>
Date: Tue, 25 Sep 2001 11:16:05 -0700
From: "Charles E. Perkins" <charliep@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Coexistence with other uses for routing header
References: <200109250804.f8P84kl22271@givry.rennes.enst-bretagne.fr>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Francis Dupont wrote:

>    I checked, and I think the handling for Routing Headers is pretty
>    clear in the text.  The mobile node doesn't put its care-of address
>    in a routing header for the correspondent node, and the correspondent
>    node checks its Binding Cache before putting in the care-of address
>    into a Routing Header.  These cases are not in the danger zone of
>    reversing "unauthorized" Routing Headers.
> 
> => the issue is not in reversing "unauthorized" RHs, the issue is in
> reversing "authorized" RHs from the correspondent node and keeping
> the care-of address in them (the CoA is the last intermediate in
> received RHs and in careless reversing the CoA becomes the first one).
>  "Authorized" RHs are managed through reversing using the property than
> reverse o reverse = Id, if the mobility adds something in the RH, the
> other end SHOULD removes it. BTW your proposed text should avoid
> spurious multiple additions of the CoA in RHs by the correspondent
> if the mobile node doesn't apply my idea.

O.K.  Now I see the point, and remember that this point has been
raised in the past.  The mobile node should use natural route
table selection when sending packets to the correspondent node,
not route reversal of a source route from the correspondent node.
But there is already text in the draft that says what you want,
in section 10.3:

   In addition, the general procedures defined by IPv6 for Routing
   headers suggest that a received Routing header MAY be automatically 
   "reversed" to construct a Routing header for use in any response
   packets sent by upper-layer protocols, if the received packet is
   authenticated [6].  If this is done for upper-layer protocol response
   packets sent by a mobile node while away from home, the mobile
   node SHOULD NOT include its own care-of address, which appears in  
   the Routing header of the received packet, in the reversed route
   for the response packet.            ...........

Is there more to do?

Regards,
Charlie P.


From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep 25 14:21:05 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11276
	for <mobileip-archive@odin.ietf.org>; Tue, 25 Sep 2001 14:21:05 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id MAA16487;
	Tue, 25 Sep 2001 12:20:54 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id LAA15258;
	Tue, 25 Sep 2001 11:20:58 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8PIKB7B027932
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 25 Sep 2001 11:20:12 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8PIKB8G027931
	for mobile-ip-dist; Tue, 25 Sep 2001 11:20:11 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from bebop.France.Sun.COM (bebop.France.Sun.COM [129.157.174.15])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8PIK77B027924
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 11:20:07 -0700 (PDT)
Received: from lillen (vpn133-11.EBay.Sun.COM [129.150.133.11])
	by bebop.France.Sun.COM (8.10.2+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id f8PIJPg26537;
	Tue, 25 Sep 2001 20:19:26 +0200 (MET DST)
Date: Tue, 25 Sep 2001 20:14:49 +0200 (CEST)
From: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Subject: Re: [mobile-ip] No keying for "weak" global authentication
To: mat@cisco.com
Cc: mobile-ip@sunroof.eng.sun.com, Erik.Nordmark@eng.sun.com,
        charliep@iprg.nokia.com,
        "Hesham Soliman (ERA)" <Hesham.Soliman@era.ericsson.se>
In-Reply-To: "Your message with ID" <15280.46923.497792.293898@thomasm-u1.cisco.com>
Message-ID: <Roam.SIMC.2.0.6.1001441689.27166.nordmark@bebop.france>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

> 
>    In fact, I believe that the basic mechanism for
>    weak authentication SHOULD NOT include keying at
>    all. The reason is that the actual security property
>    being enforced by all of these proposals is the return
>    routability test, *not* the keying. The keying is an
>    optimization for subsequent updates so that it does
>    not need to perform the full return routability test
>    each time.

While I don't have a problem with this per-see I wonder how many flavours
will end up with. Potentially will have:
 - just return routability for each BU being sent - no crypto
 - return routability for first BU plus establish some keys so that
   subsequent BUs don't need the 3-way handshake required for
   return routability
 - IKE in the case when there is a PKI
 - Perhaps SUCV if not now but at a future date

From a total complexity perspective it would be good to figure out
how many flavours we need.

   Erik



From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep 25 14:39:12 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11674
	for <mobileip-archive@odin.ietf.org>; Tue, 25 Sep 2001 14:39:11 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id MAA03036;
	Tue, 25 Sep 2001 12:39:00 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id LAA29797;
	Tue, 25 Sep 2001 11:39:02 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8PIbq7B028029
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 25 Sep 2001 11:37:52 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8PIbqQ0028028
	for mobile-ip-dist; Tue, 25 Sep 2001 11:37:52 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8PIbm7B028021
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 11:37:48 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id LAA20669;
	Tue, 25 Sep 2001 11:37:49 -0700 (PDT)
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA01372;
	Tue, 25 Sep 2001 12:38:44 -0600 (MDT)
Received: from mira-sjc5-7.cisco.com (mira-sjc5-7.cisco.com [171.71.163.27])
	by sj-msg-core-1.cisco.com (8.11.6/8.9.1) with ESMTP id f8PIblG20712;
	Tue, 25 Sep 2001 11:37:47 -0700 (PDT)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-7.cisco.com (Mirapoint)
	with ESMTP id AAJ00758;
	Tue, 25 Sep 2001 11:37:44 -0700 (PDT)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id LAA00808; Tue, 25 Sep 2001 11:37:43 -0700 (PDT)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15280.52983.402820.137567@thomasm-u1.cisco.com>
Date: Tue, 25 Sep 2001 11:37:43 -0700 (PDT)
To: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Cc: mat@cisco.com, mobile-ip@sunroof.eng.sun.com, charliep@iprg.nokia.com,
        "Hesham Soliman (ERA)" <Hesham.Soliman@era.ericsson.se>
Subject: Re: [mobile-ip] No keying for "weak" global authentication
In-Reply-To: <Roam.SIMC.2.0.6.1001441689.27166.nordmark@bebop.france>
References: <15280.46923.497792.293898@thomasm-u1.cisco.com>
	<Roam.SIMC.2.0.6.1001441689.27166.nordmark@bebop.france>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Erik Nordmark writes:
 > 
 > > 
 > >    In fact, I believe that the basic mechanism for
 > >    weak authentication SHOULD NOT include keying at
 > >    all. The reason is that the actual security property
 > >    being enforced by all of these proposals is the return
 > >    routability test, *not* the keying. The keying is an
 > >    optimization for subsequent updates so that it does
 > >    not need to perform the full return routability test
 > >    each time.
 > 
 > While I don't have a problem with this per-see I wonder how many flavours
 > will end up with. Potentially will have:
 >  - just return routability for each BU being sent - no crypto
 >  - return routability for first BU plus establish some keys so that
 >    subsequent BUs don't need the 3-way handshake required for
 >    return routability
 >  - IKE in the case when there is a PKI
 >  - Perhaps SUCV if not now but at a future date

IMO, there should be two pieces in the MIPv6 draft:

1) A mechanism to use IPsec to protect BU's. Francis
   layed out the necessary changes required to make
   that possible. There is no need to mention IKE at
   all here because keying is orthogonal to IPsec,
   and its implications are well known to anybody
   who has any experience VPN's.

2) A basic return routability test for use between
   CN and MN. This can be extremely simple requiring
   no more than several paragraphs to explain, and
   a couple of new ICMP messages.

Any other optimizations should be deferred.
Indeed, it would probably be a good idea to get
some implementation/deployment experience to find
out whether further optmizations are even
warrented.

		Mike


From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep 25 15:25:14 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12688
	for <mobileip-archive@odin.ietf.org>; Tue, 25 Sep 2001 15:25:14 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA18035;
	Tue, 25 Sep 2001 12:25:10 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id MAA10141;
	Tue, 25 Sep 2001 12:25:00 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8PJNr7B028164
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 25 Sep 2001 12:23:53 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8PJNrkS028163
	for mobile-ip-dist; Tue, 25 Sep 2001 12:23:53 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8PJNo7B028156
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 12:23:50 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id MAA11996
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 12:23:52 -0700 (PDT)
Received: from e31.bld.us.ibm.com (e31.co.us.ibm.com [32.97.110.129])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA24922
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 13:24:46 -0600 (MDT)
Received: from westrelay01.boulder.ibm.com (westrelay01.boulder.ibm.com [9.99.140.22])
	by e31.bld.us.ibm.com (8.9.3/8.9.3) with ESMTP id PAA119436
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 15:21:29 -0400
Received: from d03nm103.boulder.ibm.com (d03nm103.boulder.ibm.com [9.99.140.95])
	by westrelay01.boulder.ibm.com (8.11.1m3/NCO v4.97.1) with ESMTP id f8PJNmJ110832
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 13:23:48 -0600
From: "Venkata Jagana" <jagana@us.ibm.com>
Importance: Normal
Subject: Re: [mobile-ip] Draft 15
To: mobile-ip@sunroof.eng.sun.com
X-Mailer: Lotus Notes Release 5.0.3 (Intl) 21 March 2000
Message-ID: <OF3C7A3DF8.3DFACA22-ON88256AD2.00677AE7@boulder.ibm.com>
Date: Tue, 25 Sep 2001 12:23:34 -0700
X-MIMETrack: Serialize by Router on D03NM103/03/M/IBM(Release 5.0.8 |June 18, 2001) at
 09/25/2001 01:23:48 PM
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>




   >> I support Hersham's position:
   >>  - drop piggybacking

   > I think this is far premature.  It has the potential to be a very
   > important improvement


   > Sending Binding Updates along with data packets has many advantages:
   > - reduces number of media acquistions

   > => ?

   > - in the most natural implementations, reduces the total number
   >  of Binding Updates sent

   > => I believe the argument is delayed BUs, isn't it? This relies on
   > a specific traffic pattern, for instance no request-like traffic from
   > correspondents.


      I agree that it is a good idea to delay the BU's for an outgoing
     packet case. Why send Bu's unnecessarily if there is no incoming
     tunnelled packets to or no outgoing packets from MN, so it is a good
     idea to delay them. What would CN do by having this BU early if it
     has nothing to send (in a specific scenario) to MN and needed only
     when it receives something from MN.

     I can see both arguments here: a) delay case b) piggybacking.
     I strongly believe delaying is important to avoid unnecessary
     overhead very early on, piggybacking is important to reduce the
      packet overhead.

      This discussion is already captured in draft in sec 10.9 (...For
     example,since the Binding Update is a destination option and can be
     included in any packet sent by a mobile node, the mobile node MAY
     delay sending a new Binding Update to any correspondent...) and it
     looks OK to me.



 Thanks,
 Venkat

 ----------------------------------------------------------------
 Venkata R Jagana
 IBM Linux Technology Centre, Beaverton
 jagana@us.ibm.com
 Tel: (503) 578 3430 T/L 775-3430




From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep 25 15:51:26 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13324
	for <mobileip-archive@odin.ietf.org>; Tue, 25 Sep 2001 15:51:26 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA01117;
	Tue, 25 Sep 2001 12:51:17 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id MAA16229;
	Tue, 25 Sep 2001 12:51:07 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8PJnq7B028256
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 25 Sep 2001 12:49:52 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8PJnq5H028255
	for mobile-ip-dist; Tue, 25 Sep 2001 12:49:52 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8PJnm7B028248
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 12:49:48 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id MAA15947;
	Tue, 25 Sep 2001 12:49:50 -0700 (PDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA07198;
	Tue, 25 Sep 2001 13:50:40 -0600 (MDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id MAA11124;
	Tue, 25 Sep 2001 12:49:35 -0700 (PDT)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f8PJnZY11234;
	Tue, 25 Sep 2001 12:49:35 -0700
X-mProtect:  Tue, 25 Sep 2001 12:49:35 -0700 Nokia Silicon Valley Messaging Protection
Received: from charliep.iprg.nokia.com (205.226.2.89, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpdQrGxol; Tue, 25 Sep 2001 12:49:34 PDT
Message-ID: <3BB0DFCE.73AA315A@iprg.nokia.com>
Date: Tue, 25 Sep 2001 12:49:34 -0700
From: "Charles E. Perkins" <charliep@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: James Kempf <kempf@eng.sun.com>
CC: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Draft 15
References: <200109251557.IAA07103@heliopolis.eng.sun.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hello Jim,

James Kempf wrote:
> 
> Hi Charlie,
> 
> I had a suggestion for addition as the last paragraph in Section 6.5.
> Section 6.5 discusses loosening the restriction on RA from 3 seconds
> to between 0.5 and 1.5 second, in order to facilitate movement detection.

The lower limit is 0.05 seconds (I hope!).

> The text I'd be interested in seeing added is the following:
> 
>         In addition to increasing the frequency of advertisment,
>         an access router MAY use any combination of mechanisms to
>         detect when a mobile node has established a new link with the
>         subnet serviced by the router and to inform the mobile node
>         via a Router Advertisement of the mobile node's new
>         point of attachment.

I have several comments on this.  First, I'm not so much adverse
to making clear that routers can employ varous mechanisms to
do motion detection.  But I am quite reluctant to go down the
path of specifying every conceivable circumstance.  I do not
subscribe to the theory that we have to say that a protocol
entity can only use protocol messages in exactly some set of
circumstances.  Instead, it is important to stick to what comes
out over the physical medium. From this, I would say that we
need to say that Router Advertisements can be sent by the router
at arbitrary times (but not to exceed the fastest rate) and with
periodicity in conformance to the values it advertises.

>                               An access router MAY unicast
>         a Router Advertisement to a mobile node if it discovers
>         that one has established a link,

If this isn't already obvious from the previous parts of
the specfication, then we should make it so.  For instance,
section 6.5 already says:

   Thus, to provide good support for mobile nodes, Mobile IPv6 relaxes
   this limit such that routers MAY send unsolicited multicast Router 
   Advertisements more frequently.

Your sentence would logically come after this one, if more needs
to be said.

>                                           or it MAY multicast a
>         Router Advertisement in response to link establishment
>         rather than periodically.

Here, wouldn't it be important to limit the use of multicast?
Unicast would be better.  If the mobile node's IP address is
unavailable, then maybe the multicast IP packet would be sent
to the mobile node's specific layer-2 address.  Do you think
it's important to have this multicast feature?

>                                    The intent is to speed up informing
>         the mobile node of its new attachment point, to reduce the
>         overall delay in establishing a new care of address.

Again, I'd rather avoid trying to specify intentions, if possible.

> The idea behind this text is to allow the access router the same
> freedom to optimize as the mobile node is granted in the first
> few paragraphs of Section 10, while still keeping the same simplicity,
> generality, and interoperability of the standard MIPv6 movement detection
> algorithm.

I agree that we should allow access routers to do whatever they can
do to increase the performance of Mobile IPv6.


Regards,
Charlie P.


From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep 25 16:08:39 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13723
	for <mobileip-archive@odin.ietf.org>; Tue, 25 Sep 2001 16:08:38 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id OAA20085;
	Tue, 25 Sep 2001 14:08:23 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id NAA20634;
	Tue, 25 Sep 2001 13:08:25 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8PK737B028357
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 25 Sep 2001 13:07:03 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8PK737C028356
	for mobile-ip-dist; Tue, 25 Sep 2001 13:07:03 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8PK6x7B028349
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 13:06:59 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id NAA12356
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 13:07:01 -0700 (PDT)
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id NAA04719
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 13:07:01 -0700 (PDT)
Received: from mira-sjc5-7.cisco.com (mira-sjc5-7.cisco.com [171.71.163.27])
	by sj-msg-core-1.cisco.com (8.11.6/8.9.1) with ESMTP id f8PK72G25910
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 13:07:02 -0700 (PDT)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-7.cisco.com (Mirapoint)
	with ESMTP id AAJ03518;
	Tue, 25 Sep 2001 13:07:00 -0700 (PDT)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id NAA00853; Tue, 25 Sep 2001 13:07:00 -0700 (PDT)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15280.58339.881234.535333@thomasm-u1.cisco.com>
Date: Tue, 25 Sep 2001 13:06:59 -0700 (PDT)
To: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Draft 15
In-Reply-To: <3BB0C2D5.540E1781@iprg.nokia.com>
References: <200109251727.f8PHR0l24678@givry.rennes.enst-bretagne.fr>
	<3BB0C2D5.540E1781@iprg.nokia.com>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Vijay Devarapalli writes:
 > i prefer a separate draft which explains how AH can be used with 
 > MIPv6. and the requirements like (new next header, disable piggybacking)
 > for AH to work can be present in that draft. and it can advance at its 
 > own pace.

  The problem is that that does not provide adequate
  security for the HA/MN security association. We
  need a strong authentication mode for this SA.

	 Mike


From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep 25 16:39:43 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14415
	for <mobileip-archive@odin.ietf.org>; Tue, 25 Sep 2001 16:39:42 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA25788;
	Tue, 25 Sep 2001 13:39:34 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id NAA20649;
	Tue, 25 Sep 2001 13:39:21 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8PKcQ7B028462
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 25 Sep 2001 13:38:26 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8PKcQlD028461
	for mobile-ip-dist; Tue, 25 Sep 2001 13:38:26 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8PKcM7B028454
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 13:38:22 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id NAA20412
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 13:38:25 -0700 (PDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id NAA20610
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 13:38:24 -0700 (PDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id NAA14543
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 13:38:24 -0700 (PDT)
X-Delivered-For: <mobile-ip@sunroof.eng.sun.com>
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f8PKcNf18882
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 13:38:23 -0700
X-mProtect:  Tue, 25 Sep 2001 13:38:23 -0700 Nokia Silicon Valley Messaging Protection
Received: from vijayd.iprg.nokia.com (205.226.2.94, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpdTJ91R1; Tue, 25 Sep 2001 13:38:21 PDT
Message-ID: <3BB0EB3E.82137092@iprg.nokia.com>
Date: Tue, 25 Sep 2001 13:38:22 -0700
From: Vijay Devarapalli <vijayd@iprg.nokia.com>
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Draft 15
References: <200109251727.f8PHR0l24678@givry.rennes.enst-bretagne.fr>
		<3BB0C2D5.540E1781@iprg.nokia.com> <15280.58339.881234.535333@thomasm-u1.cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Michael Thomas wrote:
> 
> Vijay Devarapalli writes:
>  > i prefer a separate draft which explains how AH can be used with
>  > MIPv6. and the requirements like (new next header, disable piggybacking)
>  > for AH to work can be present in that draft. and it can advance at its
>  > own pace.
> 
>   The problem is that that does not provide adequate
>   security for the HA/MN security association. We
>   need a strong authentication mode for this SA.
> 

I consider authentication data suboption with keys provided by 
BAKE/IKE/AAA/whatever as strong authentication too.

Vijay

>          Mike


From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep 25 16:41:53 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14480
	for <mobileip-archive@odin.ietf.org>; Tue, 25 Sep 2001 16:41:53 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA27089;
	Tue, 25 Sep 2001 13:41:49 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id NAA21300;
	Tue, 25 Sep 2001 13:41:27 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8PKeg7B028506
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 25 Sep 2001 13:40:42 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8PKegRD028505
	for mobile-ip-dist; Tue, 25 Sep 2001 13:40:42 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8PKec7B028496
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 13:40:38 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id NAA20967
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 13:40:41 -0700 (PDT)
Received: from sj-msg-core-4.cisco.com (sj-msg-core-4.cisco.com [171.71.163.10])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id OAA17529
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 14:40:29 -0600 (MDT)
Received: from mira-sjc5-7.cisco.com (mira-sjc5-7.cisco.com [171.71.163.27])
	by sj-msg-core-4.cisco.com (8.11.3/8.9.1) with ESMTP id f8PKeq325318;
	Tue, 25 Sep 2001 13:40:52 -0700 (PDT)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-7.cisco.com (Mirapoint)
	with ESMTP id AAJ04498;
	Tue, 25 Sep 2001 13:40:38 -0700 (PDT)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id NAA00859; Tue, 25 Sep 2001 13:40:38 -0700 (PDT)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15280.60358.24767.908578@thomasm-u1.cisco.com>
Date: Tue, 25 Sep 2001 13:40:38 -0700 (PDT)
To: mobile-ip@sunroof.eng.sun.com
Cc: charliep@iprg.nokia.com,
        "Hesham Soliman (ERA)" <Hesham.Soliman@era.ericsson.se>
Subject: Re: [mobile-ip] Draft 15
In-Reply-To: <Roam.SIMC.2.0.6.1001411485.3654.nordmark@bebop.france>
References: <3BB03866.1B247D18@iprg.nokia.com>
	<Roam.SIMC.2.0.6.1001411485.3654.nordmark@bebop.france>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Erik Nordmark writes:
 > For key management there needs to be a method that doesn't require a PKI
 > but I've also seen emails I've interpreted as a desire to use a PKI when
 > it is available. Thus it seems like there needs to be at least
 > two mechanisms here: IKE plus one that works without a PKI.
 > With more than one mechanism to choose there must also be a mechanism
 > for a MN to choose which one to use that is secure enough so that the MN
 > can't be tricked into using a less secure method when the more secure
 > one is indeed available.

   If you have access to the outbound IPsec processing,
   this should be fairly straightforward, I'd think:
   you check to see if BU packet would cause an ESP
   or AH header to be added, and if not then you use
   the weaker variety. I believe that this also addresses
   the authorization issue since you could set up different
   security policy database entries which reflect the
   different policies you might want to apply to BU's
   vs. other data (if any).

	     Mike


From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep 25 18:02:55 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16480
	for <mobileip-archive@odin.ietf.org>; Tue, 25 Sep 2001 18:02:55 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id PAA06732;
	Tue, 25 Sep 2001 15:02:43 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id PAA12458;
	Tue, 25 Sep 2001 15:02:36 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8PM1g7B028712
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 25 Sep 2001 15:01:42 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8PM1goU028711
	for mobile-ip-dist; Tue, 25 Sep 2001 15:01:42 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8PM1c7B028704
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 15:01:39 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id PAA21777
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 15:01:40 -0700 (PDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id QAA21857
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 16:01:28 -0600 (MDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id PAA20495
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 15:01:38 -0700 (PDT)
X-Delivered-For: <mobile-ip@sunroof.eng.sun.com>
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f8PM1c900607
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 15:01:38 -0700
X-mProtect:  Tue, 25 Sep 2001 15:01:38 -0700 Nokia Silicon Valley Messaging Protection
Received: from vijayd.iprg.nokia.com (205.226.2.94, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpdihQ9CH; Tue, 25 Sep 2001 15:01:37 PDT
Message-ID: <3BB0FEC1.CADD31B6@iprg.nokia.com>
Date: Tue, 25 Sep 2001 15:01:37 -0700
From: Vijay Devarapalli <vijayd@iprg.nokia.com>
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Draft 15
References: <200109251727.f8PHR0l24678@givry.rennes.enst-bretagne.fr>
			<3BB0C2D5.540E1781@iprg.nokia.com> <15280.58339.881234.535333@thomasm-u1.cisco.com> <3BB0EB3E.82137092@iprg.nokia.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Vijay Devarapalli wrote:
> 
> Michael Thomas wrote:
> >
> > Vijay Devarapalli writes:
> >  > i prefer a separate draft which explains how AH can be used with
> >  > MIPv6. and the requirements like (new next header, disable piggybacking)
> >  > for AH to work can be present in that draft. and it can advance at its
> >  > own pace.
> >
> >   The problem is that that does not provide adequate
> >   security for the HA/MN security association. We
> >   need a strong authentication mode for this SA.
> >
> 
> I consider authentication data suboption with keys provided by
> BAKE/IKE/AAA/whatever as strong authentication too.
> 

sorry. BAKE wasnt supposed to be there. everything else

vijay

> 
> >          Mike


From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep 25 18:20:49 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16823
	for <mobileip-archive@odin.ietf.org>; Tue, 25 Sep 2001 18:20:49 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id QAA05979;
	Tue, 25 Sep 2001 16:19:57 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id PAA16489;
	Tue, 25 Sep 2001 15:19:58 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8PMJ47B028874
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 25 Sep 2001 15:19:04 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8PMJ481028873
	for mobile-ip-dist; Tue, 25 Sep 2001 15:19:04 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from jurassic.eng.sun.com (jurassic [129.146.84.31] (may be forged))
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8PMJ17B028866
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 15:19:01 -0700 (PDT)
Received: from istanbul.Eng.Sun.COM (istanbul.Eng.Sun.COM [129.146.86.247])
	by jurassic.eng.sun.com (8.12.0+Sun/8.12.0) with SMTP id f8PMJ2Vj656355;
	Tue, 25 Sep 2001 15:19:02 -0700 (PDT)
Message-Id: <200109252219.f8PMJ2Vj656355@jurassic.eng.sun.com>
Date: Tue, 25 Sep 2001 15:18:46 -0700 (PDT)
From: Alper Yegin <Alper.Yegin@eng.sun.com>
Subject: Re: [mobile-ip] Mobile IPv6 draft revision
To: charliep@iprg.nokia.com
Cc: mobile-ip@sunroof.eng.sun.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: gCRenk8MEzCyvLa/irM4rw==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4_37 SunOS 5.8.1 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

> Hello Alper,
> 
> > > - The Binding Acknowledgement is to be sent to the Mobile Node
> > >   at the address in the Source IP address field of the Binding Update.
> >
> > This packet should be sent to care-of address, right? Not necessarily the 
source
> > address of the incoming BU. Care-of address would be different than the 
source
> > address of BU if there's a alternate care-of address option.
> 
> I thought the purpose of using the alternate care-of address
> was to deregister a care-of address at which the mobile node
> no longer had connectivity.  If this is true, then it makes more
> sense to use the source address of the packet containing the
> Binding Update, I think.


Hi Charlie,

We don't need to use CoA as a selector to figure out which binding this 
deregistration should remove, because there's only one for each Home Address.

CoA is determined by the Alt-CoA suboption if it exists, if not, than the source 
address of the BU packet. and this is where the outgoing traffic should be sent 
by the CN. I think we should follow the same model, and let the BAck be sent to 
the Care-of address (copied from Alt-CoA or the source address of the BU). This 
is what we already do for failed BUs.


Cheers,

alper



From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep 25 18:23:07 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16871
	for <mobileip-archive@odin.ietf.org>; Tue, 25 Sep 2001 18:23:07 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id QAA07760;
	Tue, 25 Sep 2001 16:22:16 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id PAA16951;
	Tue, 25 Sep 2001 15:22:18 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8PMLa7B028927
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 25 Sep 2001 15:21:36 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8PMLa1N028926
	for mobile-ip-dist; Tue, 25 Sep 2001 15:21:36 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8PMLW7B028916
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 15:21:32 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id PAA25293
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 15:21:34 -0700 (PDT)
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id QAA23177
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 16:22:28 -0600 (MDT)
Received: from mira-sjc5-7.cisco.com (mira-sjc5-7.cisco.com [171.71.163.27])
	by sj-msg-core-1.cisco.com (8.11.6/8.9.1) with ESMTP id f8PMLXG19572
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 15:21:33 -0700 (PDT)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-7.cisco.com (Mirapoint)
	with ESMTP id AAJ07819;
	Tue, 25 Sep 2001 15:21:28 -0700 (PDT)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id PAA00902; Tue, 25 Sep 2001 15:21:27 -0700 (PDT)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15281.871.307372.886069@thomasm-u1.cisco.com>
Date: Tue, 25 Sep 2001 15:21:27 -0700 (PDT)
To: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Draft 15
In-Reply-To: <3BB0EB3E.82137092@iprg.nokia.com>
References: <200109251727.f8PHR0l24678@givry.rennes.enst-bretagne.fr>
	<3BB0C2D5.540E1781@iprg.nokia.com>
	<15280.58339.881234.535333@thomasm-u1.cisco.com>
	<3BB0EB3E.82137092@iprg.nokia.com>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Vijay Devarapalli writes:
 > Michael Thomas wrote:
 > > 
 > > Vijay Devarapalli writes:
 > >  > i prefer a separate draft which explains how AH can be used with
 > >  > MIPv6. and the requirements like (new next header, disable piggybacking)
 > >  > for AH to work can be present in that draft. and it can advance at its
 > >  > own pace.
 > > 
 > >   The problem is that that does not provide adequate
 > >   security for the HA/MN security association. We
 > >   need a strong authentication mode for this SA.
 > > 
 > 
 > I consider authentication data suboption with keys provided by 
 > BAKE/IKE/AAA/whatever as strong authentication too.

   You can delete IKE from this list too since IKE
   does not have the ability to key the proposed 
   authentication suboption. Considering the brutal
   feedback from the AD's on the AAA keying draft, 
   including it is if nothing else premature.
   
		Mike


From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep 25 18:39:58 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA17154
	for <mobileip-archive@odin.ietf.org>; Tue, 25 Sep 2001 18:39:57 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id QAA20201;
	Tue, 25 Sep 2001 16:38:59 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id PAA13094;
	Tue, 25 Sep 2001 15:38:59 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8PMbt7B029035
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 25 Sep 2001 15:37:55 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8PMbtDM029034
	for mobile-ip-dist; Tue, 25 Sep 2001 15:37:55 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from jurassic.eng.sun.com (jurassic [129.146.84.31] (may be forged))
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8PMbq7B029027
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 15:37:52 -0700 (PDT)
Received: from istanbul.Eng.Sun.COM (istanbul.Eng.Sun.COM [129.146.86.247])
	by jurassic.eng.sun.com (8.12.0+Sun/8.12.0) with SMTP id f8PMbrVj660118
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 15:37:54 -0700 (PDT)
Message-Id: <200109252237.f8PMbrVj660118@jurassic.eng.sun.com>
Date: Tue, 25 Sep 2001 15:37:37 -0700 (PDT)
From: Alper Yegin <Alper.Yegin@eng.sun.com>
Subject: Re: [mobile-ip] Re: Connectathon input for Mobile IPv6 draft revision
To: mobile-ip@sunroof.eng.sun.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: JbvG0xUdGE2U+7S/vBIszA==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4_37 SunOS 5.8.1 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Hi Charlie,

> > > > BUT, different interfaces of the same router can have the same MAC
> > > > address, therefore same link-local address but advertise different
> > > > prefixes. In this case, mobile node would fail to detect movement if
> > > > it only looks at the source MAC and IP address of packets.
> > > >
> > > > Therefore draft should not suggest a match on source MAC address and
> > > > IP address is sufficient.
> > >
> > > Here, the important thing seems to be that the mobile node is
> > > still reachable from the router.  Other problems would presumably
> >
> > Actually it is not reachable. MN is just attached to another link on the AR. 
The
> > packets coming from the AR can have the same MAC address (a legal choice and 
a
> > feature on some platforms) and the same source IP address (link local 
address
> > derived from the same MAC address). But MN is not "reachable", because it's
> > using a prefix from another link, not the current link.
> 
> Maybe it would be enough to say that the mobile node should use the
> lack of continued advertisement of a particular prefix as evidence that
> it is no longer connected to the interface which had advertised that
> prefix.

Actually this is different. The text I'm recommending to have removed is talking 
about positive indications of being still connected. The above text is 
describing how to detect being no longer connected. So, I don't this this can be 
a substitute. But instead, I think (at least) removal of the relevant statements 
is what's needed.


> 
> > > be resolved by way of Neighbor Discovery (not Mobile IPv6), and
> > > so should not be specified again within Mobile IPv6.  Here is the
> > > current relevant text:
> > >
> > >     Instead, when a mobile node receives any IPv6 packets from its
> > >     current default router at all, irrespective of the source IPv6
> > >     address, it SHOULD use that as an indication that
> > >     it is still reachable from the router.
> >
> > That doesn't work, as I explained above. Only if the same prefix is 
advertised
> > on this link, then MN can conclude it's reachable.
> >
> > So, I suggest we remove the text in the draft that suggests checking source 
IP
> > address and MAC address is sufficient.
> 
> Can you be more specific about which text you would like to see removed?

The section number was in my original e-mail. It's in section 10.4 Movement 
Detection:

   Instead, when a mobile node receives any IPv6 packets from its current 
   default router at all, irrespective of the source IPv6 address, it SHOULD use
   that as an indication that it is still reachable from the router.


And also in this section, there's some other reference to this paragraph for 
"receiving packets sent by the router". In the previous revision, there was also 
mention of matching on source IP address and the MAC address of packets.

So, receiving a router advertisement with the right prefix is a clear indication 
of still being reachable, but not just receiving a packet from the default 
router (default router defined by its (possibly link local) IP address and MAC 
address).

Cheers,

alper



From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep 25 18:49:21 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA17308
	for <mobileip-archive@odin.ietf.org>; Tue, 25 Sep 2001 18:49:20 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id PAA28140;
	Tue, 25 Sep 2001 15:48:32 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id PAA14685;
	Tue, 25 Sep 2001 15:46:22 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8PMjG7B029100
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 25 Sep 2001 15:45:16 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8PMjGlp029099
	for mobile-ip-dist; Tue, 25 Sep 2001 15:45:16 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from heliopolis.eng.sun.com (redhook.Eng.Sun.COM [152.70.24.37])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8PMjC7B029092
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 15:45:12 -0700 (PDT)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.eng.sun.com (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id PAA26823;
	Tue, 25 Sep 2001 15:45:14 -0700 (PDT)
Message-Id: <200109252245.PAA26823@heliopolis.eng.sun.com>
Date: Tue, 25 Sep 2001 15:45:12 -0700 (PDT)
From: James Kempf <James.Kempf@Sun.COM>
Subject: Re: [mobile-ip] Draft 15
To: James.Kempf@Sun.COM, charliep@iprg.nokia.com
Cc: mobile-ip@sunroof.eng.sun.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: +FNvNqQ6zgBf3dPU7HMBKg==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Hi Charlie,
Hi Charlie,

Thanx for the reply.

>The lower limit is 0.05 seconds (I hope!).
>

Right, sorry.

>> The text I'd be interested in seeing added is the following:
>> 
>>         In addition to increasing the frequency of advertisment,
>>         an access router MAY use any combination of mechanisms to
>>         detect when a mobile node has established a new link with the
>>         subnet serviced by the router and to inform the mobile node
>>         via a Router Advertisement of the mobile node's new
>>         point of attachment.
>
>I have several comments on this.  First, I'm not so much adverse
>to making clear that routers can employ varous mechanisms to
>do motion detection.  But I am quite reluctant to go down the
>path of specifying every conceivable circumstance.  I do not
>subscribe to the theory that we have to say that a protocol
>entity can only use protocol messages in exactly some set of
>circumstances.  Instead, it is important to stick to what comes
>out over the physical medium. From this, I would say that we
>need to say that Router Advertisements can be sent by the router
>at arbitrary times (but not to exceed the fastest rate) and with
>periodicity in conformance to the values it advertises.
>

I agree.

>>                               An access router MAY unicast
>>         a Router Advertisement to a mobile node if it discovers
>>         that one has established a link,
>
>If this isn't already obvious from the previous parts of
>the specfication, then we should make it so.  For instance,
>section 6.5 already says:
>
>   Thus, to provide good support for mobile nodes, Mobile IPv6 relaxes
>   this limit such that routers MAY send unsolicited multicast Router 
>   Advertisements more frequently.
>

I think it would be good to make it explicit. As I mentioned, it
was not obvious to some during the recent discussion of fast
handoff.

>Your sentence would logically come after this one, if more needs
>to be said.
>
>>                                           or it MAY multicast a
>>         Router Advertisement in response to link establishment
>>         rather than periodically.
>
>Here, wouldn't it be important to limit the use of multicast?
>Unicast would be better.  If the mobile node's IP address is
>unavailable, then maybe the multicast IP packet would be sent
>to the mobile node's specific layer-2 address.  Do you think
>it's important to have this multicast feature?
>

I think the unicast feature is superior, and, as you say, the
router can send it to the layer-2 address.

>>                                    The intent is to speed up informing
>>         the mobile node of its new attachment point, to reduce the
>>         overall delay in establishing a new care of address.
>
>Again, I'd rather avoid trying to specify intentions, if possible.
>

OK.

>> The idea behind this text is to allow the access router the same
>> freedom to optimize as the mobile node is granted in the first
>> few paragraphs of Section 10, while still keeping the same simplicity,
>> generality, and interoperability of the standard MIPv6 movement detection
>> algorithm.
>
>I agree that we should allow access routers to do whatever they can
>do to increase the performance of Mobile IPv6.
>

Great, thanx. I think the changes you've outlined above would do more
to make sure people don't misinterpret the specification as disallowing
optimization.

		jak



From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep 25 20:14:45 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA19050
	for <mobileip-archive@odin.ietf.org>; Tue, 25 Sep 2001 20:14:44 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id RAA28725;
	Tue, 25 Sep 2001 17:14:06 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id RAA12403;
	Tue, 25 Sep 2001 17:13:53 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8Q0Cp7B029281
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 25 Sep 2001 17:12:51 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8Q0Cpre029280
	for mobile-ip-dist; Tue, 25 Sep 2001 17:12:51 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8Q0Cl7B029271
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 17:12:47 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id RAA12233
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 17:12:50 -0700 (PDT)
Received: from albatross-ext.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id RAA01604
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 17:12:49 -0700 (PDT)
Received: from esealnt462.al.sw.ericsson.se (ESEALNT462.al.sw.ericsson.se [153.88.251.62])
	by albatross.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id f8Q0CmK27597
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 02:12:48 +0200 (MEST)
Received: FROM esealnt400.al.sw.ericsson.se BY esealnt462.al.sw.ericsson.se ; Wed Sep 26 02:12:47 2001 +0200
Received: by esealnt400 with Internet Mail Service (5.5.2653.19)
	id <THZ679ZV>; Wed, 26 Sep 2001 02:12:47 +0200
Message-ID: <034BEFD03799D411A59F00508BDF754603008D04@esealnt448.al.sw.ericsson.se>
From: "Hesham Soliman  (ERA)" <Hesham.Soliman@era.ericsson.se>
To: "'mobile-ip@sunroof.eng.sun.com'" <mobile-ip@sunroof.eng.sun.com>
Subject: RE: [mobile-ip] Draft 15
Date: Wed, 26 Sep 2001 02:12:38 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
	\> 

> > > I don't have any problem with getting a new next header unless that
> > > will somehow introduce (yet!) another delay factor.
> > >
> >         => I think it's _very_important for us to recognise what the
> >         _real_ cause of the delay is. The real cause in terms of security
> >         was relying on IKE (which needs PKI) as the only key exchange
> >         mechanism. We've already discussed the use of IPsec for
> >         weeks before and after London.
> >         I haven't seen any comment suggesting the removal of IPsec,
> >         the discussion was whether piggybacking should stay or go.
> >         There are several ways of handling the IPsec problem
> >         I attempted to list some options in the thread titled
> >         "IPsec, IKE, MIPv6 and concensus" the first message
> >         was sent on 17th August, you can trace the thread from
> >         there.
> >         Also Jari mentioned that he's documenting these discussoins
> >         in a draft coming out soon.
> 
> getting a new next header will cause a delay. this should be pursued
> separately and should not be in the MIPv6 spec.
> 
	=> Really ?! Why ? we don't even have a key exchange mechanism 
	and you think the new nxt header value will be the cause of delay ?

	Hesham


From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep 25 20:32:33 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA19297
	for <mobileip-archive@odin.ietf.org>; Tue, 25 Sep 2001 20:32:32 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id RAA03919;
	Tue, 25 Sep 2001 17:31:53 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id RAA16686;
	Tue, 25 Sep 2001 17:31:40 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8Q0Uh7B029379
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 25 Sep 2001 17:30:43 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8Q0UhTR029378
	for mobile-ip-dist; Tue, 25 Sep 2001 17:30:43 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from jurassic.eng.sun.com (jurassic [129.146.83.36] (may be forged))
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8Q0Ud7B029371
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 17:30:40 -0700 (PDT)
Received: from istanbul.Eng.Sun.COM (istanbul.Eng.Sun.COM [129.146.86.247])
	by jurassic.eng.sun.com (8.12.0+Sun/8.12.0) with SMTP id f8Q0UgVj682099
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 17:30:43 -0700 (PDT)
Message-Id: <200109260030.f8Q0UgVj682099@jurassic.eng.sun.com>
Date: Tue, 25 Sep 2001 17:30:28 -0700 (PDT)
From: Alper Yegin <Alper.Yegin@eng.sun.com>
Subject: Re: [mobile-ip] Optimizing Movement Detection on the AR 
To: mobile-ip@sunroof.eng.sun.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: rBBhNrSeXgAGyb5Eor9Jsw==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4_37 SunOS 5.8.1 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

> >> Would it be possible to add some text to Section 6.5 that allows
> >> the AR to unicast a Router Advert to the MN if the AR detects that the MN
> >> has arrived on its link?
> >
> >Does the current text disallow this? I.e, are you asking for text that
> >encourages implementations to  do this, or just making sure that it
> >isn't disallowed?
> >
> 
> The current text doesn't say anything about allowing the router to using 
> additional information for optimzations. The concern expressed was that
> because it is explicitly not in the spec, it would be viewed
> as not acceptable. This contrasts with Section 10, where mobile node
> movement detection is discussed, in which the spec says:
> 
> 	A mobile node MAY use any combination of mechanisms available
> 	to it to detect when it has moved from one link to another.
> 	
> and later:
> 
> 	Mobile nodes SHOULD use Router Discovery to discover new routers
> 	and on-link subnet prefixes; a mobile node MAY send Router
> 	Solicitation messages, or MAY wait for unsolicited (periodic)
> 	multicast Router Advertisement messages, as specified for
> 	Router Discovery [17]. 
> 
> Section 10 only encourages access routers to decrease the period
> of Router Advertisment transmission, but says nothing about explicitly
> tying the transmission of a Router Advertisement to the apperance
> of a mobile node.
> 
> >Also, rather than asking someone else to provide text, how about
> >providing it yourself. :-) That tends to lead to the desired result
> >more quickly, and allows folks to better understand just what it is
> >you want to add to the spec.
> >
> 
> OK, how about this;
> 
> 	An access router MAY use any combination of mechanisms to
> 	detect when a mobile node has established a link with the
> 	subnet serviced by the router and to inform the mobile node
> 	via a Router Advertisement of the mobile node's new
> 	point of attachment. An access router MAY unicast
> 	a Router Advertisement to a mobile node if it discovers
> 	that one has established a link, or it MAY multicast a
> 	Router Advertisement in response to link establishment
> 	rather than periodically. The intent is to speed up informing
> 	the mobile node of its new attachment point, to reduce the
> 	overall delay in establishing a new care of address.
> 	
> One issue here is what IP address to use as the destination address for 
unicast. 
> I suppose it could be the old care of address, but the standard MIPv6 
algorithm 
> provides no way for the access router to discover that, and outlining such a 
way 
> definitely shouldn't be included in the spec, since the standard algorithm is 
> intended to be simple and general. If the access router knows the mobile
> node's link address, it can always deliver the packet if there is a link
> level connection, but the mobile node's IP stack might not accept
> it unless it has the right destination address. Perhaps it should just be left 
> open, or perhaps the phrase about unicast should be taken out and the 
paragraph 
> restricted to multicast?

I think draft should recommend "unicast" stronger than "multicast" for this RAs. 
Sending a multicast RA for each time a device attaches to a link is very costly 
for the network. It might even be worth not optimizing RS/RA in this way, and 
let MN send a RS.

So, IMHO, access routers "SHOULD unicast", if this is not possible "MAY 
multicast" router advertisements.

When unicasted, I think the destination IP address of the RA can be unspecified. 
This seems to be a valid source address for RS, therefore a valid destination 
address for (at least solicited) RAs.

Reading Jim's text above, maybe what he has in mind is to unicast RA at L2 with 
a multicast L3 destination? But I think unspecified destination address is 
cleaner.


alper



From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep 25 20:43:35 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA19438
	for <mobileip-archive@odin.ietf.org>; Tue, 25 Sep 2001 20:43:34 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id RAA07728;
	Tue, 25 Sep 2001 17:43:06 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id RAA18852;
	Tue, 25 Sep 2001 17:42:58 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8Q0g37B029480
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 25 Sep 2001 17:42:03 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8Q0g27N029479
	for mobile-ip-dist; Tue, 25 Sep 2001 17:42:02 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8Q0fx7B029472
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 17:41:59 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id RAA18599
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 17:42:02 -0700 (PDT)
Received: from albatross-ext.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id RAA06175
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 17:42:01 -0700 (PDT)
Received: from esealnt462.al.sw.ericsson.se (ESEALNT462.al.sw.ericsson.se [153.88.251.62])
	by albatross.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id f8Q0g0K29836
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 02:42:00 +0200 (MEST)
Received: FROM esealnt742.al.sw.ericsson.se BY esealnt462.al.sw.ericsson.se ; Wed Sep 26 02:41:59 2001 +0200
Received: by esealnt742.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <TH2J862Z>; Wed, 26 Sep 2001 02:34:49 +0200
Message-ID: <034BEFD03799D411A59F00508BDF754603008D05@esealnt448.al.sw.ericsson.se>
From: "Hesham Soliman  (ERA)" <Hesham.Soliman@era.ericsson.se>
To: "'mobile-ip@sunroof.eng.sun.com'" <mobile-ip@sunroof.eng.sun.com>
Subject: RE: [mobile-ip] New BETH Draft
Date: Wed, 26 Sep 2001 02:41:50 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

> >> While the MN is in the no-coverage area, it will be using the
> >> standard MIPv6 algorithm for handover (soliciting for RtAdv
> >> or waiting until the AR sends them). How does it know
> >> to transition to not soliciting and allowing the network
> >> to perform the handover?
> >> 
> >	=> Why should it know or suppress rtr_sol ? My understanding 
> >	has been that the entire point of BETH was that some 
> >	link layers have certain timing restrictions and are not 
> >	flexible enough to allow for MIP to be integrated in their
> >	radio. But now it seems like you're adding something 
> >	else: suppresing rtr_sol. I don't think we need to do that. 
> >
> 
> Hmm, well, let me try again. I think we both agree that one way a MN gets a 
> RtAdv in standard MIPv6 is to send a SolRtAdv and that the MN could do this 
> solicitation based on an L2 trigger, right?
> 
> Suppose the MN is moving in a coverage area in which the access
> routers use the standard MIPv6 algorithm. In this coverage area,
> the MN responds to the L2 trigger by sending SolRtAdv, receiving
> a RtAdv in response. So you have these messages going out over
> the air from the MN in response to its L2 handover.
> 
	=> OK.

> Now, suppose the MN moves to a coverage area in which BETH is available.
> Up until this point, the MN has been doing the SolRtAdv. How does
> it know to stop doing the SolRtAdv and simply wait for the AR
> to set up the tunnels? 
> 
	=> Why should it know ?

> Can you give me a simple
> explanation of how this would work without some kind of 
> exchange between the MN and AR to let the MN know that things
> have changed and it can now receive optimized service?
> 
	=> Actually I can't :) and I shouldn't. What is the outcome
	that you're trying to avoid ? If the MN solicits it gets an
	RA, if it finds out that it moved it will do standard MIPv6
	and overwrite BETH. What's the problem ?

	BTW BETH does not give optimised service, the packets
	are still going through oAR. Depending on the topology this 
	may not be optimal, e2e BUs are the most optimal.

> >	We MUST distinguish between implementation issues
> >	and protocol issues. If I'm designing an IPv6 stack to 
> >	work in system foo, where foo has certain limitations 
> >	then I'll consider that in my design of the stack. BETH 
> >	has a narrow scope of use and is not designed to work
> >	in all cases so let's keep it that way. 
> >
> 
> I think it is an interoperability issue. You want to allow a BETH-capable
> MN 
> 
	=> There is no such thing as a BETH-capable MN. BETH relies
	on the fact that the MN is incapable ! 

> to operate optimally in an nonBETH network, and to transition. Also,
> we are not just talking about BETH here. The same issues arise with
> transitioning between an FMIPv6 and a standard MIPv6 (SMIPv6?) coverage area
> 
	=> Interoperability problems are problems that arise when two entities
	participating in a protocol have different understandings of the protocol
	parameters which results in communication failure. This is not at
	all the case here. No communication will fail.

> >	Seriously let's not make things so unbeleivably complex that
> >	they become useless in practice. 
> >
> 
> I agree 100%. And if you can explain to me how to interoperably manage the
> following transitions:
> 
> 	FMIPv6 coverage <-> Standard MIPv6 coverage
> 
	=> The MN always uses standard MIPv6 unless something
	se happens. If a Pr_rtr_adv is received then it goes into FMIPv6
	mode. Otherwise it's standard MIPv6.

> 	BETH coverage <-> Standard MIPv6 coverage
> 
	=> Even easier than the above, the MN ALWAYS operates
	in MIPv6 mode. BETH will still work until the MN receives 
	a rtr adv. Whether that is solicited or not is not important.
> 	
> without adding having the MN and AR know what the other is capable of,> 
> I'll be happy. Rajeev and I discussed this extensively on the list,
> and having the MN and AR exchange this information seemed like the
> right way to go, but I am certainly open to better suggestions if
> you have one.
> 
	=> How about the above ?

> >
> >> >Also for MIPv6 if the MN sends a BU to oAR and it is not
> >> >capable then the BU will be dropped.
> >> >
> >> 
> >> I don't follow.
> >> 
> >	=> The aim was to say that you can't guarantee that every router
> >	will support all functions required. MIPv6 does not require 
> >	routers to add an option in the RA stating whether it will 
> >	accept BUs or not. The protocol is robust enough to handle
> >	that.
> Well, I consider this a bug in the MIPv6 spec. It must be possible
> to suppress unnecessary on the air signalling when radio spectrum
> is expensive. Service providers are not going to deploy MIPv6 if
> they have to put up with gratuitous use of expensive spectrum, or
> they are going to insist that vendors do something to allow
> supressing it that may result in non-interoperable implementations. 
> I haven't studied this issue closely enough to
> make a recommendation about how to avoid it, however.
> 
	=> First of all this is a ND protocol. Second, as I tried to explain, 
	if you're optimising your implementation for a certain radio
	interface then please do it in your implementation. The protocol
	provides the general framework, optimisations like these
	are implementation dependant as long as  they don't break the 
	protocol. 
	We already have these issues in UMTS and are dealing with 
	it in the right places (configuration of routers and implementations 
	of routers and hosts).

> >> >In BETH, there is no involvment from the MN anyway so 
> >> >no need to advertise. 
> >> >
> >> 
> 
> That's the whole point of what I'm trying to say. How is the
> the MN told when to stop being involved in a transition situation?
> 
	=> The MN can be involved after he handover not before. I thought
	that's the whole point behind BETH.

> >> Sure, but the MN must know when to suppress sending SolRtPr
> >> if the AR can handle the handover via BETH.
> >> 
> >	=> New requirement and is not relevant to mobility management. 
> >	We should not solve all problems within MIP. If the MN solicits
> >	and gets a new RA, normal MIPv6 will take place. 
> >
> 
> Right, but if it doesn't have to solicit, or if it should use
> a RtSolPr instead, then what? How does it know to use FMIPv6
> or BETH instead of SMIPv6?
> 
	=>You only use Pr_rtr_sol if you are soliciting BEFORE you 
	move. This is based on your L2 trigger that tells you you're
	about to move. Otherwise you use normal rtr solicitations.
	remember Pr_rtr_sol are TRIGGERED by L2 triggers.

	Hesham


From owner-mobile-ip@sunroof.eng.sun.com  Tue Sep 25 21:10:41 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA19914
	for <mobileip-archive@odin.ietf.org>; Tue, 25 Sep 2001 21:10:40 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id SAA14964;
	Tue, 25 Sep 2001 18:10:08 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id SAA23411;
	Tue, 25 Sep 2001 18:10:02 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8Q19E7B029595
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 25 Sep 2001 18:09:14 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8Q19ELG029594
	for mobile-ip-dist; Tue, 25 Sep 2001 18:09:14 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8Q19A7B029587
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 18:09:10 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id SAA16805
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 18:09:11 -0700 (PDT)
Received: from e31.bld.us.ibm.com (e31.co.us.ibm.com [32.97.110.129])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id SAA14933
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 18:09:11 -0700 (PDT)
Received: from westrelay02.boulder.ibm.com (westrelay02.boulder.ibm.com [9.99.140.23])
	by e31.bld.us.ibm.com (8.9.3/8.9.3) with ESMTP id VAA98506;
	Tue, 25 Sep 2001 21:06:45 -0400
Received: from d03nm103.boulder.ibm.com (d03nm103.boulder.ibm.com [9.99.140.95])
	by westrelay02.boulder.ibm.com (8.11.1m3/NCO v4.97.1) with ESMTP id f8Q194V231220;
	Tue, 25 Sep 2001 19:09:04 -0600
From: "Venkata Jagana" <jagana@us.ibm.com>
Importance: Normal
Subject: RE: [mobile-ip] Comments on Mobile IPv6 draft 14
To: mobile-ip@sunroof.eng.sun.com
Cc: Hesham.Soliman@era.ericsoon.se, charliep@iprg.nokia.com
X-Mailer: Lotus Notes Release 5.0.3 (Intl) 21 March 2000
Message-ID: <OFD16776EE.D3130AC8-ON88256AD2.0082B46F@boulder.ibm.com>
Date: Tue, 25 Sep 2001 18:08:58 -0700
X-MIMETrack: Serialize by Router on D03NM103/03/M/IBM(Release 5.0.8 |June 18, 2001) at
 09/25/2001 07:09:04 PM
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>




>   Let us consider a scenario where MN moves from its home network 'A' to
>   foreign network 'B' and then to foreign network 'C'.
>
>   After moving from network 'A' to network 'B', MN should have registered
>   (i.e. BU sent)its primary CoA picked up at 'B' with the home agent at
> 'A'.
>   Now, the HA at 'A' has a binding cache entry marked home registration.
>
>   Next, the MN moves from 'B' to 'C', then, MN would send BU to the HA
>   at 'A' to request the change in cache entry with the new CoA just
> obtained
>   at 'C' and also to a home agent at 'B' to register its new CoA obtained
> at
>   'C' network. The registration with home agent at 'B' is required so
that
>   packets addressed to its old CoA at B will now be tunnelled to its new
>   CoA at 'C'. Effectively, the MN now has one home agent at 'A', which I
>   called 'Original Home - OH' (because that's where its home was) and
> another
>   home agent at 'B' which I called 'Foreign Home - FH' at 'B'.
>
>   Let us say that, after sometime, the MN came back from 'C' to 'B'
>   during its movement path and which means that MN can start reusing its
>   old COA at but before start using it there, it needs to deregister its
> CoA
>   at B with HA at 'B'; then sending a BU to its OH at 'A' with this CoA
>   at 'B'. Then, it will have to send a BU to HA at 'C' with the CoA at
'B'
>   to start tunnelling packets destined fro MN. In this case, the 'FH' is
>   effectively now moved 'B' to 'C'. In this case, it had to perform 3
> steps:
>   deregistration with 'B', registration with HA ('OH') at 'A' with CoA at
> 'B'
>   and registration with  HA ('FH') at 'C' with COA at 'B'.
>
>   Hope I made this clear without making it too complicated. So, my point
>   is that the draft didn't consider a scenario like this and hence never
>   talked about deregistration with home agent on the foreign networks the
>   MN visited.
>
           => I beleive that this is due to th fact that neither the data
structures
           => (Binding cache or BUL) nor the BUs distinguish between a
"foreign HA" or a
           => "real HA". So the section on deregistering when connecting to
the
           => Home network still applies to your scenario.

     Deregistering section, 9.4, applies to Home agent operation
     and it describes about what HA should do when deregistration
     (i.e. BU received) happens but what I am talking about is MN
     operation, sec 10.20 (MN returning home) and not HA. This scenario
     involves not just deregistration only but much more, sorry,
     I haven't made that very clear in my last mail.

     In a scenario, I have described here, MN should do the following
     things at a minimum:
          - deregister with home agent at 'B'
          - Binding update to home agent at 'A' to refresh its
            bcache entry with the CoA at 'B' now
          - registration with foreign home agent at 'C' to start
            tunnelling packets to CoA at 'B'

     At any time, a MN may have a single original/real Home Agent
     and single or multiple foreign Home Agents. At a given instance,
     the number of foreign home agents a MN may have, will depend upon
     how fast the MN is moving across the networks but it doesn't need to
     keep track of all those foreign home agents except for the last one.
     In a case where MN moves too quickly from one network to another,
     then it would have established registrations with each of those
     foreign home agents at the networks it visited earlier in order to
     have the packets tunnelled to its current CoA from the previous
     old CoA's.

     Section 10.20 simply talks about MN returning home (its original
     or real home) but it doesn't 'explicitly' talk about a MN moving
     back to a old network it just visited earlier and what MN
     should do (probably, I would consider this as a special case) and it
     is not covered at all in this section unless it is interpreted that
     it is left to the implementation, but I don't think that's a
     good idea to leave it that way.

Thanks,
Venkat

----------------------------------------------------------------
Venkata R Jagana
IBM Linux Technology Centre, Beaverton
jagana@us.ibm.com
Tel: (503) 578 3430 T/L 775-3430




From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep 26 00:41:41 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA24578
	for <mobileip-archive@odin.ietf.org>; Wed, 26 Sep 2001 00:41:40 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id VAA00464;
	Tue, 25 Sep 2001 21:41:04 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id VAA26840;
	Tue, 25 Sep 2001 21:40:51 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8Q4e27B029805
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 25 Sep 2001 21:40:02 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8Q4e1An029804
	for mobile-ip-dist; Tue, 25 Sep 2001 21:40:01 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8Q4dw7B029797
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 21:39:58 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id VAA26792
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 21:40:01 -0700 (PDT)
Received: from mgw-dax2.ext.nokia.com (mgw-dax2.ext.nokia.com [63.78.179.217])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id VAA14125
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 21:40:01 -0700 (PDT)
Received: from davir02nok.americas.nokia.com (davir02nok.americas.nokia.com [172.18.242.85])
	by mgw-dax2.ext.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f8Q4eEC14785
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 23:40:15 -0500 (CDT)
Received: from daebh001.NOE.Nokia.com (unverified) by davir02nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T563825f9d5ac12f255079@davir02nok.americas.nokia.com>;
 Tue, 25 Sep 2001 23:40:00 -0500
Received: from daebe007.NOE.Nokia.com ([172.18.242.211]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.2966);
	 Tue, 25 Sep 2001 23:40:00 -0500
content-class: urn:content-classes:message
Subject: RE: [mobile-ip] New BETH Draft
Date: Tue, 25 Sep 2001 23:40:06 -0500
Message-ID: <697DAA22C5004B4596E033803A7CEF441E873E@daebe007.NOE.Nokia.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Thread-Topic: [mobile-ip] New BETH Draft
X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0
Thread-Index: AcFF6sZ9dbLMarHdEdWBSwBQi2X+DwAWavXQ
From: "Patil Basavaraj (NET/Dallas)" <Basavaraj.Patil@nokia.com>
To: <mobile-ip@sunroof.eng.sun.com>
Cc: "'James kempf'" <James.Kempf@Sun.COM>
X-OriginalArrivalTime: 26 Sep 2001 04:40:00.0211 (UTC) FILETIME=[4D078230:01C14645]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by sunroof.eng.sun.com id f8Q4dw7B029798
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 8bit

James,

Following this thread, I tend to agree with Hesham. I do not believe
it is required to advertise capabilities of FMIPv6 or BETH to the MN
via router advertisements. As has been discussed at length in this
thread the MN will know if the network supports fast HO when it
sends a ProxyRtrSolicit and receives an Advt as a response. And
similarly the network knows that an MN is capable of fast HO when
it receives the F-BU as a response to a ProxyRtrAdvt. So what do
you do when the network performs HOs via BETH? I think you should
allow the MN to still send a ProxyRtrSolct as a result of some L2
trigger on the MN but either ignore the message if the network is doing
a HO using BETH or send a NAK to the MN as a response to the
ProxyRtrSlct. I agree that this causes some additional signaling but
it keeps implementations simple (relatively) and also avoids having to
build new extensions or flags into router advts any more than we already
have.

-Basavaraj



From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep 26 00:43:53 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA24631
	for <mobileip-archive@lists.ietf.org>; Wed, 26 Sep 2001 00:43:52 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id WAA12245;
	Tue, 25 Sep 2001 22:42:47 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id VAA27155;
	Tue, 25 Sep 2001 21:42:50 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8Q4gB7B029846
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 25 Sep 2001 21:42:11 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8Q4gAGf029845
	for mobile-ip-dist; Tue, 25 Sep 2001 21:42:10 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8Q4g67B029835
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 21:42:07 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id VAA27066;
	Tue, 25 Sep 2001 21:42:10 -0700 (PDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id VAA14549;
	Tue, 25 Sep 2001 21:42:09 -0700 (PDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id VAA10785;
	Tue, 25 Sep 2001 21:41:39 -0700 (PDT)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f8Q4fc125111;
	Tue, 25 Sep 2001 21:41:38 -0700
X-mProtect:  Tue, 25 Sep 2001 21:41:38 -0700 Nokia Silicon Valley Messaging Protection
Received: from charliep.iprg.nokia.com (205.226.2.89, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpdLVt4yC; Tue, 25 Sep 2001 21:41:36 PDT
Message-ID: <3BB15C81.DE5655DA@iprg.nokia.com>
Date: Tue, 25 Sep 2001 21:41:37 -0700
From: "Charles E. Perkins" <charliep@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Erik Nordmark <Erik.Nordmark@eng.sun.com>
CC: mobile-ip@sunroof.eng.sun.com, Pat Calhoun <pcalhoun@diameter.org>
Subject: Re: [mobile-ip] Concerns/comments for aaa-keys and gen-key
References: <Roam.SIMC.2.0.6.1001427527.14101.nordmark@bebop.france>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hello Erik,

Your comments seem to go right to the heart of what it means for
a working group to create protocol specifications.  Thus, I will
try to make some very general comments.  However, it has to be
other members of the working group that really will have to take
up the argument.  There have been people working with these
documents to produce interoperable implementations that do what
the engineers want to have done.  Their experience is reflected
in these documents.  That is what the IETF is about, it seems to
me.  But now the documents, even though they reflect the combined
wisdom of engineering some useful and interoperable implementations,
are apparently going to be vetoed.

My involvement with these documents is to try to capture codify
the practice of various groups developing authorization
infrastructure components for Mobile IP and AAA.  I'll happily do
whatever the working group and IESG decide, but I am in no position
to lead the effort towards making the decision.  I can only try to
make sure that the two documents in question fit well (enough) with
RFC 2002(bis) and the other documents (e.g., MN-NAI and the FA
challenge) that we have already finished.

Some more comments inline:

Erik Nordmark wrote:
> 
> I've read draft-ietf-mobileip-aaa-key-08.txt and
> draft-ietf-mobileip-gen-key-01.txt and I have some significant comments and
> concerns. Most of these comments is about aaa-key - the gen-key document
> seems to be mostly a set of option formats without much behavioral protocol
> specifications.

Yes, that was exactly the idea, and was considered to be the approach
indicated by MIER, which was also approved as a working group item,
and more recently integrated into RFC2002bis.

> Some of these echo and perhaps extend the comments that Thomas generated
> and that where forwarded to the mobile-ip mailing list on Aug 30.

Unfortunately, I didn't manage to respond to those comments yet, given
other time pressures.

> High level comments (details below):
> 1. The scope of the problem and proposed solution isn't very clear.

The scope of the problem is to create a way for AAA to authorize network
access and set up the security associations needed for the mobile node
to work with a home agent.  It is supposed to look very much like what
is done today with RADIUS, except for improvements due to DIAMETER.
Building on existing experience seems to help a lot with getting
interoperability.

> 2. The protocols outlined in the documents are very underspecified.

The documents specify extensions for Mobile IP to be used with
a DIAMETER/AAA infrastructure.  The detailed specifications for
the message flows are expected to be in Mobile IP and AAA protocol
documents.

> 3. It is unclear what level of careful security review the documents
>    have seen.

The people doing the work would probably state that they're a heck
of lot more secure than RADIUS, but I probably ought to avoid trying
to put any words in their mouths.

> 4. Between the lines there appear to be some architectural assumptions
>    e.g. that AAAh and HA have some high degree of mutual trust, which seem
>    to imply that the solution might not be a good fit when the AAAh and
>    HA are operated by different entities.

All protocols have particular spheres of applicability.  I think that
most, but not all, people want to have the high degree of trust that
you infer.  However, I also think that the drafts have been written to
allow authorization by a third party.  Again, I am not conversant with
specific implementations that exhibity this behavior, and my only role
has been to try to incorporate the relevant comments that have been
given to me over the last couple of years for this document.



> Scope/Applicability
> -------------------
> 
> While the abstract talks solely of using this to create security associations
> between MN-HA and MN-FA there appear to be other documents that appear to
> use the same protocol mechanisms such as draft-le-aaa-lsa-tsk-00.txt.

That draft was written after the drafts under discussion.  I'm not
sure what your point is here.  There are similarities, which is
understandable because the motivations from the authors of the 
document you cite are very similar to the motivations of the people
who suggested the ways for distributing keys according to the aaa-keys
draft -- again, as best I understand the motivations of the people
involved.

> While that draft doesn't specify packet formats it is using similar
> techniques to those described in the aaa-keys draft. Currently there
> is no way to tell whether the aaa-keys packet formats are intended to
> be useful beyond the MN-HA and MN-FA security associations.

Are you asking whether the generalized key definitions are general
enough?  The specific subtypes in the aaa-keys are supposed to be
pretty specific, so I don't know whether anyone would want them to
be useful beyond what is there in the draft.

> Thus what is needed is something indicating the applicability of aaa-keys.
> Without knowing the applicability it is not possible to determine what
> needs to be supported in terms of algorithms and key sizes, as
> well as the constraints on how to negotiate what algorithm and key length
> to use for a given SA.

As far as I know, everyone believes this will be determined by
policy at AAAH.  It "should" be legitimate for a vendor to create
a proprietary key distribution protocol and utilize that between
mobile node and AAAH.  Thus, in such a scenario, your suggestion
amounts to a request to determine whether proprietary information
is sufficient for the purposes intended by the vendors.

> Underspecification
> ------------------
> 
> As Thomas specified in depth there specification doesn't actual
> contain message flows showing the interaction between MN, FA, HA, and the
> AAA entities.

The message flows are expected to be determined by Mobile IP and
by AAA.

> (Who sends what to whom when? When processing occurs when a message is
> received.)
> Without this it is hard if not impossible to do a security analysis of
> the specification.
> 
> The spec is completely silent on the need for re-keying and the
> mechanism used to accomplish this.

But this would depend on the specific algorithm that was in use.

> The spec doesn't talk about algorithm negotiation?
> I would assume that there needs to be at least one mandatory to implement
> algorithm to ensure that there is interoperability.

Maybe it's a proprietary algorithm?  Again, others may be
better positioned to answer this.

> Does the protocol assume that the AAA exchanges provide confidentiality
> or is it sufficient if the AAA exchanges provide integrity of the information
> carried in the AAA protocol?

I've never heard anyone ask this question before, and I think it would
indicate that everyone assumes that the key is never passed in the clear.

> Security review
> ---------------

            ............... stuff I don't know about   ..........

> The document talks about using the NAI to identify the user, which
> might have privacy implications. While the NAI must have a stable domain
> component (the part after the @ sign) in order to route to the right home
> AAA server, but that doesn't inherently require that the component
> before the @ sign be a fixed string like a user name.
> Has there been any privacy review of this?
> Are there any thoughts or proposals around using temporary IDs instead
> of user names before the @ sign?

I would have expected that the way a node uses the NAI to identify
itself was more a matter for AAAH policy and operator contractual
negotiations.  It would not necessarily have any effect on the
format of the Mobile IP extensions, nor even the DIAMETER extensions,
and almost surely not much effect on the generalized extensions.

> Architectural Assumptions
> ------------------------
> 
> Between the lines there appear to be some architectural assumptions
> e.g. that AAAh and HA have some high degree of mutual trust, which seem
> to imply that the solution might not be a good fit when the AAAh and
> HA are operated by different entities.

This was already discussed above, right?

> It would seem unwise to have hard-code the requirement that the AAA home
> and the IP address home is the same; folks have suggested scenarios
> where the AAA home could be e.g. Visa and the routing home is
> a home agent in the house (or elsewhere). Of course there
> might also be scenarios when the are provided by the same administration e.g
> when the same ISP/operator provides AAA and routing home.
> So I think it makes sense to support both.

I also think it makes sense to support both.  I thought that
the working group review of the document had caused this to be
true, and I am not yet very clear on how the NAI considerations
would work against this.  For instance, company XYZ may somehow
have an agreement with company QWE to allow Mobile IP as long as
the mobile node can pay with a credit card.  But, again, I am
not conversant with the details of any prototype exhibiting that.

> In the case when the AAAh and HA are different administrations then
> I suspect that one needs to be able to have a different chain of trust -
> with the MN-HA having the initial trust. But when they are the same
> administration it makes sense to have MN-AAAH be the initial trust that
> is used to build the other trust relationships.
> 
> Thus I think this architectural issues will have an impact on the
> specification once the specification provides more detail.

O.K.  I hope someone will provide the necessary text.

Regards,
Charlie P.


From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep 26 01:32:35 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA26374
	for <mobileip-archive@odin.ietf.org>; Wed, 26 Sep 2001 01:32:34 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id WAA11360;
	Tue, 25 Sep 2001 22:31:54 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id WAA03427;
	Tue, 25 Sep 2001 22:31:46 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8Q5UQ7B000080
	for <mobile-ip-dist@sunroof.eng.sun.com>; Tue, 25 Sep 2001 22:30:26 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8Q5UQSF000079
	for mobile-ip-dist; Tue, 25 Sep 2001 22:30:26 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8Q5UM7B000072
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 22:30:22 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id WAA01844
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 22:30:24 -0700 (PDT)
Received: from telecom.samsung.co.kr ([165.213.221.4])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id WAA26591
	for <mobile-ip@sunroof.eng.sun.com>; Tue, 25 Sep 2001 22:30:22 -0700 (PDT)
Received: from cychong (a22421 [165.213.224.21])
	by telecom.samsung.co.kr (8.11.6/8.11.6) with SMTP id f8Q5UEb02159
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 14:30:15 +0900 (KST)
Message-ID: <000e01c1464d$47f6d770$15e0d5a5@cychong>
From: "Chae-yong Chong" <cychong@metro.telecom.samsung.co.kr>
To: <mobile-ip@sunroof.eng.sun.com>
References: <3BAFA0A9.A1520959@iprg.nokia.com>
Subject: Re: [mobile-ip] Draft 15
Date: Wed, 26 Sep 2001 14:37:06 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by sunroof.eng.sun.com id f8Q5UN7B000073
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 8bit

I am sorry, but i cannot get a revised copy of this draft.
The site is not accessible. 
Where can I get a copy?

Chae-yong


----- Original Message ----- 
From: "Charles E. Perkins" <charliep@iprg.nokia.com>
To: "Mobile IP Working Group" <mobile-ip@sunroof.eng.sun.com>
Cc: "Basavaraj Patil (NTC/Dallas)" <Basavaraj.Patil@nokia.com>; "Phil Roberts" <PRoberts@MEGISTO.com>
Sent: Tuesday, September 25, 2001 6:07 AM
Subject: [mobile-ip] Draft 15


> Hello folks,
> 
> I have done a rough edit on revision 15 of Mobile IPv6.
> It needs some proofreading.  There may still be some problems
> left over because of eliminating the Mobile Router capability,
> and the "Prefix Length" field of the Binding Update.  Also,
> I am still puzzling over the e-mail about how a mobile node
> should get the link-layer address of the home agent when it
> returns home.
> 
> Here is the current draft:
> http://people.nokia.net/charlep/txt/mobilev6/mobilev6.txt
> 
> 
> 
> Here is a list of changes:
> 
>     -  Removed the Mobile Router Prefix Length Sub-Option
>    
>     -  Removed the Prefix Length field from the Binding Update.
>    
>     -  Reworded the specification so that the Home Agent now has to
>        perform Duplicate Address Detection for the mobile node's address
>        on all the prefixes for which the router is performing home agent
>        service.
>    
>     -  Removed the section about Mobile Routers
>    
>     -  Added the Authentication Data Sub-option; reorganized the section
>        about computing authentication data.
>     
>     -  Specified that the Home Agent lifetime is by default the same as
>        the Router lifetime, in a Router Advertisement.
>     
>     -  Specified that Binding Updates with zero lifetime and the 'A' bit
>        set should cause a Binding Acknowledgement to be sent back to the
>        Source IP address of the Binding Update.
> 
>     -  Qualified the allowable times when a mobile node can send a
>        Binding Update to a correspondent node
> 
>     -  Added text allowing the correspondent node to extend an existing
>        Routing Header by also including the care-of address as the entry
>        of a routing header to be visited immediately before the home
>        address.  In this way, for instance, the mobile node can be an
>        intermediate node of a path along the way to some other node.
>    
>     -  Removed the Home Address field from the Home Agent Address
>        Discovery Request Message.
>     
>     -  Noted that ICMP Unreachable forms a potential mechanism by which
>        a malicious node can cause a correspondent node to delete a valid
>        entry from its Binding Cache.
> 
>     -  Specified that, when a router stops offering home agent services
>        by turning off the 'H' flag, the mobile node has to delete the
>        corresponding entry from its Home Agent list. 
> 
> 
> 
> I'll wait a bit longer before sending it, depending on current
> mailing list discussion and any other comments that may be
> contributed.  Surely there will be some other changes that have
> to be made anyway, but it is possible to imagine that they will
> be small ones.
> 
> 
> Regards,
> Charlie P.
> 
> 


From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep 26 04:08:43 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA10558
	for <mobileip-archive@odin.ietf.org>; Wed, 26 Sep 2001 04:08:42 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id BAA18554;
	Wed, 26 Sep 2001 01:07:53 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id BAA01129;
	Wed, 26 Sep 2001 01:07:38 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8Q86c7B000350
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 26 Sep 2001 01:06:38 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8Q86bOL000348
	for mobile-ip-dist; Wed, 26 Sep 2001 01:06:37 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8Q86Y7B000341
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 01:06:34 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id BAA06814;
	Wed, 26 Sep 2001 01:06:37 -0700 (PDT)
Received: from mailgw.ipunplugged.com (217.134.88.213.host.tele1europe.se [213.88.134.217])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id CAA08607;
	Wed, 26 Sep 2001 02:06:24 -0600 (MDT)
Received: from fredrikj (hotel-14.local.ipunplugged.com [192.168.8.14])
	by mailgw.ipunplugged.com (8.9.3/8.9.3) with SMTP id KAA28744;
	Wed, 26 Sep 2001 10:07:06 +0200
From: "Fredrik Johansson" <fredrik.johansson@ipunplugged.com>
To: <Erik.Nordmark@eng.sun.com>, <mobile-ip@sunroof.eng.sun.com>,
        "Charlie Perkins" <charliep@IPRG.nokia.com>
Cc: "Pat Calhoun" <pcalhoun@diameter.org>
Subject: RE: [mobile-ip] Concerns/comments for aaa-keys and gen-key
Date: Wed, 26 Sep 2001 10:07:35 +0200
Message-ID: <MJEMJBGGCLLDLFFAHLJKAEHFDGAA.fredrik.johansson@ipunplugged.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
In-Reply-To: <3BB15C81.DE5655DA@iprg.nokia.com>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hi Erik,

Please see additions to Charlies comments inline

/Fredrik
>
>
>Hello Erik,
>
>Your comments seem to go right to the heart of what it means for
>a working group to create protocol specifications.  Thus, I will
>try to make some very general comments.  However, it has to be
>other members of the working group that really will have to take
>up the argument.  There have been people working with these
>documents to produce interoperable implementations that do what
>the engineers want to have done.  Their experience is reflected
>in these documents.  That is what the IETF is about, it seems to
>me.  But now the documents, even though they reflect the combined
>wisdom of engineering some useful and interoperable implementations,
>are apparently going to be vetoed.
>
>My involvement with these documents is to try to capture codify
>the practice of various groups developing authorization
>infrastructure components for Mobile IP and AAA.  I'll happily do
>whatever the working group and IESG decide, but I am in no position
>to lead the effort towards making the decision.  I can only try to
>make sure that the two documents in question fit well (enough) with
>RFC 2002(bis) and the other documents (e.g., MN-NAI and the FA
>challenge) that we have already finished.
>
>Some more comments inline:
>
>Erik Nordmark wrote:
>>
>> I've read draft-ietf-mobileip-aaa-key-08.txt and
>> draft-ietf-mobileip-gen-key-01.txt and I have some significant
>comments and
>> concerns. Most of these comments is about aaa-key - the gen-key document
>> seems to be mostly a set of option formats without much
>behavioral protocol
>> specifications.
>
>Yes, that was exactly the idea, and was considered to be the approach
>indicated by MIER, which was also approved as a working group item,
>and more recently integrated into RFC2002bis.
>
>> Some of these echo and perhaps extend the comments that Thomas generated
>> and that where forwarded to the mobile-ip mailing list on Aug 30.
>
>Unfortunately, I didn't manage to respond to those comments yet, given
>other time pressures.
>
>> High level comments (details below):
>> 1. The scope of the problem and proposed solution isn't very clear.
>
>The scope of the problem is to create a way for AAA to authorize network
>access and set up the security associations needed for the mobile node
>to work with a home agent.  It is supposed to look very much like what
>is done today with RADIUS, except for improvements due to DIAMETER.
>Building on existing experience seems to help a lot with getting
>interoperability.
>
>> 2. The protocols outlined in the documents are very underspecified.
>
>The documents specify extensions for Mobile IP to be used with
>a DIAMETER/AAA infrastructure.  The detailed specifications for
>the message flows are expected to be in Mobile IP and AAA protocol
>documents.

As Charlie points out, the specification of message flows are in
draft-ietf-diameter-mobileip-07.txt. The gen-key and aaa-key drafts
merely specify the format of the specific message.

>
>> 3. It is unclear what level of careful security review the documents
>>    have seen.
>
>The people doing the work would probably state that they're a heck
>of lot more secure than RADIUS, but I probably ought to avoid trying
>to put any words in their mouths.
>
>> 4. Between the lines there appear to be some architectural assumptions
>>    e.g. that AAAh and HA have some high degree of mutual trust,
>which seem
>>    to imply that the solution might not be a good fit when the AAAh and
>>    HA are operated by different entities.
>

The assumption is that a AAA server (let it be AAAh or AAAf) have a high
degree of mutual trust with the HA. And that AAA servers of different
domains have a mutual trust (Service Level Agreement). If the HA is located
in a foreign network, the AAAh will distribute the keys to the AAAf which
will distribute them to the allocated HA in the foreign network.

>All protocols have particular spheres of applicability.  I think that
>most, but not all, people want to have the high degree of trust that
>you infer.  However, I also think that the drafts have been written to
>allow authorization by a third party.  Again, I am not conversant with
>specific implementations that exhibity this behavior, and my only role
>has been to try to incorporate the relevant comments that have been
>given to me over the last couple of years for this document.
>
>
>
>> Scope/Applicability
>> -------------------
>>
>> While the abstract talks solely of using this to create security
>associations
>> between MN-HA and MN-FA there appear to be other documents that appear to
>> use the same protocol mechanisms such as draft-le-aaa-lsa-tsk-00.txt.
>
>That draft was written after the drafts under discussion.  I'm not
>sure what your point is here.  There are similarities, which is
>understandable because the motivations from the authors of the
>document you cite are very similar to the motivations of the people
>who suggested the ways for distributing keys according to the aaa-keys
>draft -- again, as best I understand the motivations of the people
>involved.
>
>> While that draft doesn't specify packet formats it is using similar
>> techniques to those described in the aaa-keys draft. Currently there
>> is no way to tell whether the aaa-keys packet formats are intended to
>> be useful beyond the MN-HA and MN-FA security associations.
>
>Are you asking whether the generalized key definitions are general
>enough?  The specific subtypes in the aaa-keys are supposed to be
>pretty specific, so I don't know whether anyone would want them to
>be useful beyond what is there in the draft.
>
>> Thus what is needed is something indicating the applicability of
>aaa-keys.
>> Without knowing the applicability it is not possible to determine what
>> needs to be supported in terms of algorithms and key sizes, as
>> well as the constraints on how to negotiate what algorithm and key length
>> to use for a given SA.
>

It's up to the policy of the AAAh to determine the necessary level of the
keys to distribute.

>As far as I know, everyone believes this will be determined by
>policy at AAAH.  It "should" be legitimate for a vendor to create
>a proprietary key distribution protocol and utilize that between
>mobile node and AAAH.  Thus, in such a scenario, your suggestion
>amounts to a request to determine whether proprietary information
>is sufficient for the purposes intended by the vendors.
>
>> Underspecification
>> ------------------
>>
>> As Thomas specified in depth there specification doesn't actual
>> contain message flows showing the interaction between MN, FA, HA, and the
>> AAA entities.
>
>The message flows are expected to be determined by Mobile IP and
>by AAA.
>
>> (Who sends what to whom when? When processing occurs when a message is
>> received.)
>> Without this it is hard if not impossible to do a security analysis of
>> the specification.

Who sends what to whom and when is all specified in
draft-ietf-diameter-mobileip-07.txt


>>
>> The spec is completely silent on the need for re-keying and the
>> mechanism used to accomplish this.
>

The keys have a given lifetime, it's also specified in the mobile ip
and diameter drafts how to distribute new keys when the keys expire.


>But this would depend on the specific algorithm that was in use.
>
>> The spec doesn't talk about algorithm negotiation?
>> I would assume that there needs to be at least one mandatory to implement
>> algorithm to ensure that there is interoperability.
>

Since the mobile node and AAAh is in the same administrative domain it can
be
any algorithm that is supported by both nodes. However, HMAC-MD5 is
mandatory to
support in rfc2002-bis and in Diameter so there's one algorithm that always
will be supported.

>Maybe it's a proprietary algorithm?  Again, others may be
>better positioned to answer this.
>
>> Does the protocol assume that the AAA exchanges provide confidentiality
>> or is it sufficient if the AAA exchanges provide integrity of
>the information
>> carried in the AAA protocol?
>

The keys for the mobile node is distributed via key material so there is
really no need for confidentiality, the keys distributed to the FA and HA
is carried in the AAA protocol which requires either TLS or IPsec.

>I've never heard anyone ask this question before, and I think it would
>indicate that everyone assumes that the key is never passed in the clear.
>
>> Security review
>> ---------------
>
>            ............... stuff I don't know about   ..........
>
>> The document talks about using the NAI to identify the user, which
>> might have privacy implications. While the NAI must have a stable domain
>> component (the part after the @ sign) in order to route to the right home
>> AAA server, but that doesn't inherently require that the component
>> before the @ sign be a fixed string like a user name.
>> Has there been any privacy review of this?
>> Are there any thoughts or proposals around using temporary IDs instead
>> of user names before the @ sign?
>

I would not expect that this is a problem of the aaa-key or gen-key draft,
since they only handle transportation of keying data. The actual
registration
and identification of the user is handled by rfc 2002 and Diameter, thus
that's
where the problem lies (if there is a problem). The key drafts can use any
identifier used by mobile ip and diameter.

>I would have expected that the way a node uses the NAI to identify
>itself was more a matter for AAAH policy and operator contractual
>negotiations.  It would not necessarily have any effect on the
>format of the Mobile IP extensions, nor even the DIAMETER extensions,
>and almost surely not much effect on the generalized extensions.
>
>> Architectural Assumptions
>> ------------------------
>>
>> Between the lines there appear to be some architectural assumptions
>> e.g. that AAAh and HA have some high degree of mutual trust, which seem
>> to imply that the solution might not be a good fit when the AAAh and
>> HA are operated by different entities.
>
>This was already discussed above, right?
>
>> It would seem unwise to have hard-code the requirement that the AAA home
>> and the IP address home is the same; folks have suggested scenarios
>> where the AAA home could be e.g. Visa and the routing home is
>> a home agent in the house (or elsewhere). Of course there
>> might also be scenarios when the are provided by the same
>administration e.g
>> when the same ISP/operator provides AAA and routing home.
>> So I think it makes sense to support both.
>
>I also think it makes sense to support both.  I thought that
>the working group review of the document had caused this to be
>true, and I am not yet very clear on how the NAI considerations
>would work against this.  For instance, company XYZ may somehow
>have an agreement with company QWE to allow Mobile IP as long as
>the mobile node can pay with a credit card.  But, again, I am
>not conversant with the details of any prototype exhibiting that.
>
>> In the case when the AAAh and HA are different administrations then
>> I suspect that one needs to be able to have a different chain of trust -
>> with the MN-HA having the initial trust. But when they are the same
>> administration it makes sense to have MN-AAAH be the initial trust that
>> is used to build the other trust relationships.
>>
>> Thus I think this architectural issues will have an impact on the
>> specification once the specification provides more detail.
>

I'm not sure that I understand what you mean here, if the AAAh and HA are in
different administrative domains, I would suspect that the initial trust
should
be between the MN-AAAh since it's only the AAAh that can determine if it's
willing
to pay for the user using the requested service. The HA is merely requesting
to
get paid for services provided.

>O.K.  I hope someone will provide the necessary text.
>
>Regards,
>Charlie P.



From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep 26 04:35:36 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA10757
	for <mobileip-archive@odin.ietf.org>; Wed, 26 Sep 2001 04:35:35 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id BAA27544;
	Wed, 26 Sep 2001 01:35:04 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id BAA23290;
	Wed, 26 Sep 2001 01:34:56 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8Q8Xn7B000431
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 26 Sep 2001 01:33:49 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8Q8XnYC000430
	for mobile-ip-dist; Wed, 26 Sep 2001 01:33:49 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8Q8Xk7B000423
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 01:33:46 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id BAA10119
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 01:33:49 -0700 (PDT)
Received: from laposte.enst-bretagne.fr (laposte.enst-bretagne.fr [192.108.115.3])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id BAA29459
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 01:33:48 -0700 (PDT)
Received: from rsm.rennes.enst-bretagne.fr (rsm.rennes.enst-bretagne.fr [192.44.77.1])
	by laposte.enst-bretagne.fr (8.11.6/8.11.6) with ESMTP id f8Q8Xk917185
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 10:33:46 +0200
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr [193.52.74.194])
	by rsm.rennes.enst-bretagne.fr (8.8.8/8.8.8) with ESMTP id KAA29336
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 10:33:46 +0200 (MET DST)
Received: from givry.rennes.enst-bretagne.fr (localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.11.3/8.11.3) with ESMTP id f8Q8Xjl27046
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 10:33:45 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200109260833.f8Q8Xjl27046@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Draft 15 
In-reply-to: Your message of Tue, 25 Sep 2001 10:10:25 PDT.
             <3BB0BA81.E04F0959@iprg.nokia.com> 
Date: Wed, 26 Sep 2001 10:33:45 +0200
X-Virus-Scanned: by amavisd-milter (http://www.amavis.org/) at enst-bretagne.fr
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
 In your previous mail you wrote:

   getting a new next header will cause a delay. this should be pursued
   separately and should not be in the MIPv6 spec.
   
=> Vijay, we should not do that because the final result will be
two incompatible versions of MIPv6. If we really have a deadline
problem I propose to use UDP port 434 for BU, BA and BR (BRs don't
need security but they are used in a context where BSAs should be
already available so this doesn't matter).
 Of course this will work for IPsec but not with piggybacking so
we have to solve the piggybacking issue first. I propose to relaunch
the multiple payload by packet idea because it is generalization
of piggybacking, so if piggybacking is good this will be even better.
Last draft seems to be draft-kre-ipv6-payload-01.txt. A side effect
of this proposal is to remove the piggybacking issue from the
discussion.

Regards

Francis.Dupont@enst-bretagne.fr

PS: references: UDP port 434: RFC 2002 1.9
draft-kre-ipv6-payload-01.txt: I have it, if someone has a public
ftp/http server with a very good connectivity (akamai :-) I'll send
it to him in order to make it available.


From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep 26 04:40:35 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA10842
	for <mobileip-archive@lists.ietf.org>; Wed, 26 Sep 2001 04:40:35 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id CAA27465;
	Wed, 26 Sep 2001 02:39:40 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id BAA23823;
	Wed, 26 Sep 2001 01:39:40 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8Q8cv7B000499
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 26 Sep 2001 01:38:57 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8Q8cvPD000498
	for mobile-ip-dist; Wed, 26 Sep 2001 01:38:57 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8Q8cr7B000491
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 01:38:53 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id BAA19023
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 01:38:56 -0700 (PDT)
Received: from iproxy1.ericsson.dk (iproxy1.ericsson.dk [130.228.248.98])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id BAA01424
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 01:38:55 -0700 (PDT)
Received: from unixmail.ted.dk.eu.ericsson.se (knud.ted.dk.eu.ericsson.se [192.66.4.246])
	by iproxy1.ericsson.dk (8.10.1/8.10.1) with ESMTP id f8Q8csc21488;
	Wed, 26 Sep 2001 10:38:54 +0200 (MET DST)
Received: from ted.ericsson.dk (petg.ted.dk.eu.ericsson.se [192.66.4.85])
	by unixmail.ted.dk.eu.ericsson.se (8.10.1/8.10.1/TEDmain-1.0) with ESMTP id f8Q8cmL15383;
	Wed, 26 Sep 2001 10:38:48 +0200 (MEST)
Message-ID: <3BB19418.3E94CA94@ted.ericsson.dk>
Date: Wed, 26 Sep 2001 10:38:48 +0200
From: "Peter Grimstrup (TED)" <peter.grimstrup@ted.ericsson.dk>
Organization: Ericsson Telebit A/S
X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.14-5.0 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: jagana@us.ibm.com
CC: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Comments on Mobile IPv6 draft 14
References: <OFD16776EE.D3130AC8-ON88256AD2.0082B46F@boulder.ibm.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hi Venkata,

If you for a moment view the MN as being CoA at 'B' (the first) visiting
network 'C' and then returning home to network 'B', the draft describes 
the procedure.
It might be a good idea though to add a bit in the draft explaining this.

However, I should like give another scenario almost similar to yours:
The MN returns to network 'B' but gets another (second) CoA at 'B'. In
this case, the "first CoA at 'B'" does not return home, and the 
deregistration at home agent at 'B' shouldn't be done.

Extending this scenario seems messy, but one should remember, that most
probably, the lifetime of "forwarding from a Previous Care-of Address"
is short.

Peter
--
Venkata Jagana wrote:
> 
> ...
>      Deregistering section, 9.4, applies to Home agent operation
>      and it describes about what HA should do when deregistration
>      (i.e. BU received) happens but what I am talking about is MN
>      operation, sec 10.20 (MN returning home) and not HA. This scenario
>      involves not just deregistration only but much more, sorry,
>      I haven't made that very clear in my last mail.
> 
>      In a scenario, I have described here, MN should do the following
>      things at a minimum:
>           - deregister with home agent at 'B'
>           - Binding update to home agent at 'A' to refresh its
>             bcache entry with the CoA at 'B' now
>           - registration with foreign home agent at 'C' to start
>             tunnelling packets to CoA at 'B'
> 
>      At any time, a MN may have a single original/real Home Agent
>      and single or multiple foreign Home Agents. At a given instance,
>      the number of foreign home agents a MN may have, will depend upon
>      how fast the MN is moving across the networks but it doesn't need to
>      keep track of all those foreign home agents except for the last one.
>      In a case where MN moves too quickly from one network to another,
>      then it would have established registrations with each of those
>      foreign home agents at the networks it visited earlier in order to
>      have the packets tunnelled to its current CoA from the previous
>      old CoA's.
> 
>      Section 10.20 simply talks about MN returning home (its original
>      or real home) but it doesn't 'explicitly' talk about a MN moving
>      back to a old network it just visited earlier and what MN
>      should do (probably, I would consider this as a special case) and it
>      is not covered at all in this section unless it is interpreted that
>      it is left to the implementation, but I don't think that's a
>      good idea to leave it that way.
> 
> Thanks,
> Venkat


From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep 26 05:01:41 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA10956
	for <mobileip-archive@odin.ietf.org>; Wed, 26 Sep 2001 05:01:40 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id CAA05993;
	Wed, 26 Sep 2001 02:01:02 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id CAA25517;
	Wed, 26 Sep 2001 02:00:10 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8Q8x17B000601
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 26 Sep 2001 01:59:01 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8Q8x0cf000600
	for mobile-ip-dist; Wed, 26 Sep 2001 01:59:00 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8Q8wv7B000593
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 01:58:57 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id BAA12558;
	Wed, 26 Sep 2001 01:58:59 -0700 (PDT)
Received: from laposte.enst-bretagne.fr (laposte.enst-bretagne.fr [192.108.115.3])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id BAA08520;
	Wed, 26 Sep 2001 01:58:57 -0700 (PDT)
Received: from rsm.rennes.enst-bretagne.fr (rsm.rennes.enst-bretagne.fr [192.44.77.1])
	by laposte.enst-bretagne.fr (8.11.6/8.11.6) with ESMTP id f8Q8wr922256;
	Wed, 26 Sep 2001 10:58:53 +0200
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr [193.52.74.194])
	by rsm.rennes.enst-bretagne.fr (8.8.8/8.8.8) with ESMTP id KAA29669;
	Wed, 26 Sep 2001 10:58:52 +0200 (MET DST)
Received: from givry.rennes.enst-bretagne.fr (localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.11.3/8.11.3) with ESMTP id f8Q8wpl27271;
	Wed, 26 Sep 2001 10:58:51 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200109260858.f8Q8wpl27271@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: mobile-ip@sunroof.eng.sun.com
cc: mat@cisco.com, Erik.Nordmark@eng.sun.com, charliep@iprg.nokia.com,
        "Hesham Soliman (ERA)" <Hesham.Soliman@era.ericsson.se>
Subject: Re: [mobile-ip] No keying for "weak" global authentication 
In-reply-to: Your message of Tue, 25 Sep 2001 20:14:49 +0200.
             <Roam.SIMC.2.0.6.1001441689.27166.nordmark@bebop.france> 
Date: Wed, 26 Sep 2001 10:58:51 +0200
X-Virus-Scanned: by amavisd-milter (http://www.amavis.org/) at enst-bretagne.fr
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
 In your previous mail you wrote:

   While I don't have a problem with this per-see I wonder how many flavours
   will end up with. Potentially will have:
    - just return routability for each BU being sent - no crypto
    - return routability for first BU plus establish some keys so that
      subsequent BUs don't need the 3-way handshake required for
      return routability
    - IKE in the case when there is a PKI

=> and any (partial) replacements for IKE (KINK, AAA, ...) when
   it is available

    - Perhaps SUCV if not now but at a future date
   
   >From a total complexity perspective it would be good to figure out
   how many flavours we need.
   
=> at least two for IPsec based and not IPsec based (this is why
I'd like to get IPsec support hooks in the Mobile IPv6 document,
with those and the authentication sub-option the complexity should
be movable outside the Mobile IPv6 document).

Regards

Francis.Dupont@enst-bretagne.fr


From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep 26 05:21:33 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA11119
	for <mobileip-archive@lists.ietf.org>; Wed, 26 Sep 2001 05:21:33 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id DAA19636;
	Wed, 26 Sep 2001 03:20:43 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id CAA27605;
	Wed, 26 Sep 2001 02:20:43 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8Q9JR7B000686
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 26 Sep 2001 02:19:28 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8Q9JRVY000685
	for mobile-ip-dist; Wed, 26 Sep 2001 02:19:27 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from bebop.France.Sun.COM (bebop.France.Sun.COM [129.157.174.15])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8Q9JN7B000678
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 02:19:23 -0700 (PDT)
Received: from lillen (lillen [129.157.212.23])
	by bebop.France.Sun.COM (8.10.2+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id f8Q9JJg14351;
	Wed, 26 Sep 2001 11:19:19 +0200 (MET DST)
Date: Wed, 26 Sep 2001 11:14:50 +0200 (CEST)
From: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Subject: RE: [mobile-ip] Concerns/comments for aaa-keys and gen-key
To: Fredrik Johansson <fredrik.johansson@ipunplugged.com>
Cc: Erik.Nordmark@eng.sun.com, mobile-ip@sunroof.eng.sun.com,
        Charlie Perkins <charliep@IPRG.nokia.com>,
        Pat Calhoun <pcalhoun@diameter.org>
In-Reply-To: "Your message with ID" <MJEMJBGGCLLDLFFAHLJKAEHFDGAA.fredrik.johansson@ipunplugged.com>
Message-ID: <Roam.SIMC.2.0.6.1001495690.1688.nordmark@bebop.france>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

> As Charlie points out, the specification of message flows are in
> draft-ietf-diameter-mobileip-07.txt. The gen-key and aaa-key drafts
> merely specify the format of the specific message.

Thanks for the pointer - I hope this sheads some light.
[Seems like having this pointer in the mobileip drafts would be asking
to much. I should have read all of draft-ietf-mobileip* and draft-ietf-aaa-* 
before asking :-)]

A quick look leads me to believe that aaa-key is still very underspecified
when it comes to how the MN extensions are sent and processed in the MN
packets - diameter-mobileip talks about how/when the diameter messages
are sent and how they are processed on receipt, but nothing about what
the MN does.

> The assumption is that a AAA server (let it be AAAh or AAAf) have a high
> degree of mutual trust with the HA. And that AAA servers of different
> domains have a mutual trust (Service Level Agreement). If the HA is located
> in a foreign network, the AAAh will distribute the keys to the AAAf which
> will distribute them to the allocated HA in the foreign network.

I understand they need the appropriate level of trust in order implement
the AAA functionality. But my concern stems from the fact that the AAA
infrastructure is viewed as a way to distribute keying material to be shared
between MN and HA and that this keying material seems to be intended to
be used for more than protecting the AAA exchanges.
So while the MN/HA trusts the AAA infrastructure for those functions
it doesn't follow that they should be trusted with arbitrary keying material.

> >> Without knowing the applicability it is not possible to determine what
> >> needs to be supported in terms of algorithms and key sizes, as
> >> well as the constraints on how to negotiate what algorithm and key length
> >> to use for a given SA.
> >
> 
> It's up to the policy of the AAAh to determine the necessary level of the
> keys to distribute.

I do think we need an applicability to understand e.g. whether only 64 bits
of randomness is sufficient, what is required in terms of re-keying, etc.

> The keys have a given lifetime, it's also specified in the mobile ip
> and diameter drafts how to distribute new keys when the keys expire.

Which mobileip draft?
It seems like the MN might need to be able to determine when a key
is about to expire and initiate a re-key, but aaa-keys is utterly silent
on anything about re-keying.

> Since the mobile node and AAAh is in the same administrative domain it can
> be
> any algorithm that is supported by both nodes. However, HMAC-MD5 is
> mandatory to
> support in rfc2002-bis and in Diameter so there's one algorithm that always
> will be supported.

So it seems like aaa-keys should list this one as MUST implement.

> The keys for the mobile node is distributed via key material so there is
> really no need for confidentiality, the keys distributed to the FA and HA
> is carried in the AAA protocol which requires either TLS or IPsec.

I'm told that inventing a new key exchange/agreement protocol is non-trivial.
What the drafts are describing sure looks like a new protocol in this
area. 
If this is the case I expect there to somehow be a critical mass of
experts in this area that will review this protocol, because
I don't think its in our collective interest to create another WEP
debacle.

Alternative, if there are existing proven mechanisms to distribute keys
that fit into this it would seem to be prudent to reuse that.
(The diameter-e2e-sec draft is proposing to reuse CMS for diameter for
instance.)

   Erik




From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep 26 06:04:55 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA11786
	for <mobileip-archive@odin.ietf.org>; Wed, 26 Sep 2001 06:04:55 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id DAA27892;
	Wed, 26 Sep 2001 03:03:45 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id DAA17495;
	Wed, 26 Sep 2001 03:02:24 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8QA1Y7B000772
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 26 Sep 2001 03:01:34 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8QA1YA7000771
	for mobile-ip-dist; Wed, 26 Sep 2001 03:01:34 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8QA1U7B000764
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 03:01:30 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id DAA25439;
	Wed, 26 Sep 2001 03:01:30 -0700 (PDT)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id EAA22533;
	Wed, 26 Sep 2001 04:02:25 -0600 (MDT)
Received: from fogerty.lmf.ericsson.se (fogerty.lmf.ericsson.se [131.160.11.6])
	by penguin.wise.edt.ericsson.se (8.11.0/8.10.1/WIREfire-1.3) with ESMTP id f8QA1Mv01170;
	Wed, 26 Sep 2001 12:01:22 +0200 (MEST)
Received: from lmf.ericsson.se (lmf4ws450.lmf.ericsson.se [131.160.38.50])
	by fogerty.lmf.ericsson.se (8.11.3/8.11.3) with ESMTP id f8QA1Lb06675;
	Wed, 26 Sep 2001 13:01:21 +0300 (EET DST)
Message-ID: <3BB1A771.AC4918D5@lmf.ericsson.se>
Date: Wed, 26 Sep 2001 13:01:21 +0300
From: Jari Arkko <Jari.Arkko@lmf.ericsson.se>
Organization: Oy L M Ericsson Ab
X-Mailer: Mozilla 4.77 [en] (X11; U; SunOS 5.6 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: Erik Nordmark <Erik.Nordmark@eng.sun.com>, mat@cisco.com
CC: mobile-ip@sunroof.eng.sun.com, charliep@iprg.nokia.com,
        "Hesham Soliman (ERA)" <Hesham.Soliman@epa.ericsson.se>
Subject: Re: [mobile-ip] No keying for "weak" global authentication
References: <15280.46923.497792.293898@thomasm-u1.cisco.com>
		<Roam.SIMC.2.0.6.1001441689.27166.nordmark@bebop.france> <15280.52983.402820.137567@thomasm-u1.cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

> While I don't have a problem with this per-see I wonder how many flavours
> will end up with. Potentially will have:
>  - just return routability for each BU being sent - no crypto
>  - return routability for first BU plus establish some keys so that
>    subsequent BUs don't need the 3-way handshake required for
>    return routability
>  - IKE in the case when there is a PKI
>  - Perhaps SUCV if not now but at a future date

One observation I'd like to make here is that we
have basically entered a very new area, in terms
of existing research etc there isn't much old work.
The whole problem of "weak" authentication wasn't 
even known some time ago, and the the smart ways
of handling the problem (like SUCV etc) have surfaced
quite recently.

Therefore, it would seem prudent to prepare for
the possibility that research will come up with
more results in the area, given some time. 

Engineering-wise, this means that we should try
to decouple the weak key management protocols
from the rest of the system, allowing us to
add new ones later. This decoupling might mean
that any protocols designed for e.g. the
return routability should be extensible to
allow for SUCV etc at a future date, or that
we simply have different protocols that all
can key the same BU protection mechanism.

It may also mean that we should on purpose
try to *not* include everything we can in
the initial spec, fearing the danger that
we go too close to the leading edge and make
a mistake...

Jari


From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep 26 06:31:56 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA12032
	for <mobileip-archive@lists.ietf.org>; Wed, 26 Sep 2001 06:31:55 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id EAA29741;
	Wed, 26 Sep 2001 04:31:07 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id DAA13838;
	Wed, 26 Sep 2001 03:31:06 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8QAUC7B000891
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 26 Sep 2001 03:30:12 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8QAUB4f000890
	for mobile-ip-dist; Wed, 26 Sep 2001 03:30:11 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from bebop.France.Sun.COM (bebop.France.Sun.COM [129.157.174.15])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8QAU77B000883
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 03:30:07 -0700 (PDT)
Received: from lillen (lillen [129.157.212.23])
	by bebop.France.Sun.COM (8.10.2+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id f8QAU1v21439;
	Wed, 26 Sep 2001 12:30:02 +0200 (MET DST)
Date: Wed, 26 Sep 2001 12:25:33 +0200 (CEST)
From: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Subject: Re: [mobile-ip] Concerns/comments for aaa-keys and gen-key
To: "Charles E. Perkins" <charliep@iprg.nokia.com>
Cc: Erik Nordmark <Erik.Nordmark@eng.sun.com>, mobile-ip@sunroof.eng.sun.com,
        Pat Calhoun <pcalhoun@diameter.org>
In-Reply-To: "Your message with ID" <3BB15C81.DE5655DA@iprg.nokia.com>
Message-ID: <Roam.SIMC.2.0.6.1001499933.19612.nordmark@bebop.france>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

> Your comments seem to go right to the heart of what it means for
> a working group to create protocol specifications.

Charlie,

I think the purpose is stated at a high-level in RFC 2026 which talks
about ...
   The goals of the Internet Standards Process are:
   o  technical excellence;
   o  prior implementation and testing;
   o  clear, concise, and easily understood documentation;
   o  openness and fairness;  and
   o  timeliness.

   [...]

   A Proposed Standard specification is generally stable, has resolved
   known design choices, is believed to be well-understood, has received
   significant community review, and appears to enjoy enough community
   interest to be considered valuable.  

One stringest test for verifying the "clear and well-understod" is to
expect that interoperable implementations result from merely reading
the specification without the ability to ask questions of other
implementors or authors.
If such indepedent implementations achieve full interoperability at the first
try we have a pretty good indication that the specs are clear.

But of course we can't mandate that folks provide such implementation efforts
-  in fact most of the implementators have been involved in the standardization
effort in the WG. Thus we rely on members of the community to read the
specifications and try to find issues that would be unclear to a prospective
implementor.

Do you have a different view of how we get interoperable implementations?

> But now the documents, even though they reflect the combined
> wisdom of engineering some useful and interoperable implementations,
> are apparently going to be vetoed.

Whatever gave up that impression?

We need the specs to be clear.

> The documents specify extensions for Mobile IP to be used with
> a DIAMETER/AAA infrastructure.  The detailed specifications for
> the message flows are expected to be in Mobile IP and AAA protocol
> documents.

In separate documents? When will those documents be available for review?
(Thanks to Fredrik I know the answer to my question.)

Which documents should an implementor building just an MN read?
Must such an implementator read the diameter specs or should be
be sufficient to read the mobile-ip specifications?
(My preference would be to have specifications that are structured
so that the the mobile-ip specs are self contained but with additional,
non-required background reading in other documents.)


> All protocols have particular spheres of applicability.
[and later]
> As far as I know, everyone believes this will be determined by
> policy at AAAH.  It "should" be legitimate for a vendor to create
> a proprietary key distribution protocol and utilize that between
> mobile node and AAAH.  Thus, in such a scenario, your suggestion
> amounts to a request to determine whether proprietary information
> is sufficient for the purposes intended by the vendors.

Do you view that a vendor that takes these extensions and build
a proprietary protocol should be able to say that their protocol
conforms to an RFC?

> > The spec doesn't talk about algorithm negotiation?
> > I would assume that there needs to be at least one mandatory to implement
> > algorithm to ensure that there is interoperability.
> 
> Maybe it's a proprietary algorithm?  Again, others may be
> better positioned to answer this.

You seem to be missing my point.
How do you expect to get secure interoperability if you allow vendor X to
only implement algorithm A and vendor Y only implement algorithm B?
What is worse that in your view of the standards work, it would be fine
for both vendors to claim "We fully conform to the RFC" yet there is no
hope of interoperability.
I thought the IETF was about interoperability first and foremost.
What am I missing?

> I would have expected that the way a node uses the NAI to identify
> itself was more a matter for AAAH policy and operator contractual
> negotiations.  It would not necessarily have any effect on the
> format of the Mobile IP extensions, nor even the DIAMETER extensions,
> and almost surely not much effect on the generalized extensions.

I think you are probably correct in that the semantics on the local part of
the NAI doesn't affect the packet formats. But I think it has
a profound effect on everything else including
 - the question whether it is important to solve this privacy issue,
 - mechanisms needed in the AAA system if the local part is transient IDs
   instead of user names.
 - a mechanism by which the AAA system and the MN can agree or securely
   exchange which the sequence temporary IDs will be used.

Thus if the IETF thinks it is important to solve this problem (and that is
really my question) then it is obvious to me that some protocol specifications
are needed in order for this to result in interoperable implementations.

> > Architectural Assumptions
> > ------------------------
> > 
> > Between the lines there appear to be some architectural assumptions
> > e.g. that AAAh and HA have some high degree of mutual trust, which seem
> > to imply that the solution might not be a good fit when the AAAh and
> > HA are operated by different entities.
> 
> This was already discussed above, right?

Yes, you started commenting on my table of contents for the email at the top.

> I also think it makes sense to support both.  I thought that
> the working group review of the document had caused this to be
> true, and I am not yet very clear on how the NAI considerations
> would work against this.  For instance, company XYZ may somehow
> have an agreement with company QWE to allow Mobile IP as long as
> the mobile node can pay with a credit card.  But, again, I am
> not conversant with the details of any prototype exhibiting that.

Good. So all we need is the clear specification of how this works.
I'll see if diameter-mobileip sheds any light on this part.

   Erik



From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep 26 07:08:01 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA12677
	for <mobileip-archive@odin.ietf.org>; Wed, 26 Sep 2001 07:08:00 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id EAA20283;
	Wed, 26 Sep 2001 04:07:27 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id EAA17770;
	Wed, 26 Sep 2001 04:07:09 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8QB6H7B000992
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 26 Sep 2001 04:06:17 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8QB6HMv000991
	for mobile-ip-dist; Wed, 26 Sep 2001 04:06:17 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8QB6C7B000984
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 04:06:13 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id EAA06573
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 04:06:14 -0700 (PDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id FAA22930
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 05:07:08 -0600 (MDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA12487;
	Wed, 26 Sep 2001 07:06:10 -0400 (EDT)
Message-Id: <200109261106.HAA12487@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: mobile-ip@sunroof.eng.sun.com
From: Internet-Drafts@ietf.org
Subject: [mobile-ip] I-D ACTION:draft-ietf-mobileip-reg-tunnel-05.txt
Date: Wed, 26 Sep 2001 07:06:10 -0400
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

--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 Registration
	Author(s)	: E. Gustafsson, a. Jonsson, C. Perkins
	Filename	: draft-ietf-mobileip-reg-tunnel-05.txt
	Pages		: 36
	Date		: 25-Sep-01
	
Using 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 new kind of 'regional' registration, i.e., registration local to
the visited domain.  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.

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

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-05.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-05.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:	<20010925111105.I-D@ietf.org>

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

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

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

--OtherAccess--

--NextPart--




From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep 26 08:59:36 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16671
	for <mobileip-archive@odin.ietf.org>; Wed, 26 Sep 2001 08:59:35 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id FAA23959;
	Wed, 26 Sep 2001 05:58:47 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id FAA16617;
	Wed, 26 Sep 2001 05:58:18 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8QCv87B001133
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 26 Sep 2001 05:57:08 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8QCv8mc001132
	for mobile-ip-dist; Wed, 26 Sep 2001 05:57:08 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8QCv47B001125
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 05:57:04 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id FAA11005
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 05:57:06 -0700 (PDT)
Received: from motgate3.mot.com (motgate3.mot.com [144.189.100.103])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id GAA16044
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 06:56:55 -0600 (MDT)
Received: [from mothost.mot.com (mothost.mot.com [129.188.137.101]) by motgate3.mot.com (motgate3 2.1) with ESMTP id FAA12048 for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 05:48:45 -0700 (MST)]
Received: [from m-il06-r4.mot.com (m-il06-r4.mot.com [129.188.137.196]) by mothost.mot.com (MOT-mothost 2.0) with ESMTP id FAA04870 for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 05:57:05 -0700 (MST)]
Received: from thorgal.crm.mot.com by m-il06-r4.mot.com with ESMTP; Wed, 26 Sep 2001 07:57:04 -0500
Received: from test9.crm.mot.com.crm.mot.com (test9.crm.mot.com [140.101.173.239])
	by thorgal.crm.mot.com (Postfix) with ESMTP
	id 790D92ED28; Wed, 26 Sep 2001 14:53:51 +0200 (CEST)
To: "Fredrik Johansson" <fredrik.johansson@ipunplugged.com>
Cc: <Erik.Nordmark@eng.sun.com>, mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Concerns/comments for aaa-keys and gen-key
References: <MJEMJBGGCLLDLFFAHLJKAEHFDGAA.fredrik.johansson@ipunplugged.com>
From: Alexandru Petrescu <petrescu@crm.mot.com>
Date: 26 Sep 2001 14:56:59 +0200
In-Reply-To: <MJEMJBGGCLLDLFFAHLJKAEHFDGAA.fredrik.johansson@ipunplugged.com>
Message-Id: <m3u1xq2jqc.fsf@test9.crm.mot.com>
Lines: 29
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.0.103
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Hi Frederik,

Since this has been brought up, I have a few questions that I wanted
to ask a while back.  See inline, thanks.

Erik:
> >> 4. Between the lines there appear to be some architectural
> >> assumptions e.g. that AAAh and HA have some high degree of mutual
> >> trust, which seem to imply that the solution might not be a good
> >> fit when the AAAh and HA are operated by different entities.

Frederik:
> The assumption is that a AAA server (let it be AAAh or AAAf) have a high
> degree of mutual trust with the HA. And that AAA servers of different
> domains have a mutual trust (Service Level Agreement).

It looks to me that an (AAAH, HA) must have SLA's with every AAAF's in
whose domains that HA's MN could possibly roam.  Doesn't this boil
down to a scaleability issue similar to Mobile IPv6 (in which MN must
have trust relationships with any possible CN)?

I can understand trust between AAAH and HA, but I suppose that trust
relationship between AAAH and AAAF's, or between HA's and AAAF's, are
difficult.  If I'm missing something, sorry, please enlighten me.

If one can assume trust between an HA and any AAAF then why not using
same method between MN and CN?

Alex



From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep 26 09:56:29 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19297
	for <mobileip-archive@lists.ietf.org>; Wed, 26 Sep 2001 09:56:29 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id HAA29106;
	Wed, 26 Sep 2001 07:55:26 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id GAA10461;
	Wed, 26 Sep 2001 06:55:24 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8QDsO7B001324
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 26 Sep 2001 06:54:24 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8QDsOje001323
	for mobile-ip-dist; Wed, 26 Sep 2001 06:54:24 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from bebop.France.Sun.COM (bebop.France.Sun.COM [129.157.174.15])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8QDsJ7B001316
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 06:54:20 -0700 (PDT)
Received: from lillen (vpn133-11.EBay.Sun.COM [129.150.133.11])
	by bebop.France.Sun.COM (8.10.2+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id f8QDsHv08995
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 15:54:17 +0200 (MET DST)
Date: Wed, 26 Sep 2001 15:49:45 +0200 (CEST)
From: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Subject: Re: [mobile-ip] Draft 15
To: mobile-ip@sunroof.eng.sun.com
In-Reply-To: "Your message with ID" <3BB0A4EC.C7E993F@iprg.nokia.com>
Message-ID: <Roam.SIMC.2.0.6.1001512185.18385.nordmark@bebop.france>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

> I think this is far premature.  It has the potential to be a very
> important improvement, and once gone it would be difficult to restore.
> 
> Sending Binding Updates along with data packets has many advantages:
> - reduces number of media acquistions
> - in the most natural implementations, reduces the total number
>   of Binding Updates sent
> - reduces number of bytes sent.

Since there exists implementations of MIPv6 I wonder 1) how many of them
have implementing piggybacking and 2) of those have any looked at
the effect of turning piggy-backing on and off.

Is there any data?

> The crucial thing is to prevent Binding Updates from being sent
> unnecessarily.  Any implementation which sends Binding Updates at
> every change in point of connection to the Internet (or, even worse,
> on every movement detection) is potentially doing a lot of
> unnecessary signalling.  In contrast, an implementation that sends
> Binding Updates in the first data packet going out after detecting
> a change in the mobile node's point of attachment, is going to have
> a lot less overheat.

It clearly doesn't work to always delay the BU until data needs to be sent
to the CN. The BU needs to be sent before the CN tries to send data
to the MN - if the CN sends to the old CoA the packet might be dropped
(depending whether the MN was successful in updating a previous default router
and to what extent you want to have a residual dependency on the availability
of the previous visited link).

Predicting when a CN is going to next try to send to the MN is hard and
requires being able to predict the behavior of the transport protocol
as well as the applications running.

I wonder what working strategies folks have tried in implementations.

   Erik




From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep 26 10:08:40 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19572
	for <mobileip-archive@odin.ietf.org>; Wed, 26 Sep 2001 10:08:39 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id HAA24532;
	Wed, 26 Sep 2001 07:06:48 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id HAA11996;
	Wed, 26 Sep 2001 07:04:29 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8QE3h7B001387
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 26 Sep 2001 07:03:43 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8QE3hfH001386
	for mobile-ip-dist; Wed, 26 Sep 2001 07:03:43 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from bebop.France.Sun.COM (bebop.France.Sun.COM [129.157.174.15])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8QE3c7B001379
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 07:03:39 -0700 (PDT)
Received: from lillen (vpn133-11.EBay.Sun.COM [129.150.133.11])
	by bebop.France.Sun.COM (8.10.2+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id f8QE3Qv09848;
	Wed, 26 Sep 2001 16:03:26 +0200 (MET DST)
Date: Wed, 26 Sep 2001 15:58:55 +0200 (CEST)
From: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Subject: Re: [mobile-ip] Re: AH vs. BU suboption and piggybacking
To: charliep@iprg.nokia.com
Cc: Jari Arkko <jari.arkko@kolumbus.fi>, mobile-ip@sunroof.eng.sun.com
In-Reply-To: "Your message with ID" <3BB0B182.F600D4F3@iprg.nokia.com>
Message-ID: <Roam.SIMC.2.0.6.1001512735.32211.nordmark@bebop.france>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

> Thus, I again suggest that we really need to allow Binding Updates
> and data to live in the same IPv6 packet.  Making data streams fit
> into reserved channels of exactly prescribed bandwidth is a very
> interesting problem; I am sure we can make a solution to that
> problem which handles Binding Updates correctly -- likely as part
> of a separable ("non-piggybacked") signaling algorithm.  This should
> not penalize the other applications that do not have the same
> constraint.

I think it is fair to say that as the piggybacking is currently defined
MIPv6 doesn't fit well with the IPsec architecture.

At least some folks see a need to be able use ESP and/or AH with
MIPv6, so isn't it time to face reality?

A few weeks back I had suggested a different way to doing piggybacking -
a generic IPv6 feature to allow to IP payloads in one packet.
The semantics of this should be defined as the same as two separate packets
i.e. a receiver could process this by cloning the IPv6 header and
creating the two different packets, which it can process independently
(including processing as it relates to IPsec).

If the WG has consensus to be able to use AH/ESP as well as consensus
to support piggybacking above the link layer, then it would make sense
to seriously explore things in the direction I expected.

My 2 cents,
   Erik



From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep 26 10:13:50 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19739
	for <mobileip-archive@lists.ietf.org>; Wed, 26 Sep 2001 10:13:50 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id IAA15985;
	Wed, 26 Sep 2001 08:13:04 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id HAA13357;
	Wed, 26 Sep 2001 07:13:01 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8QEBT7B001445
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 26 Sep 2001 07:11:29 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8QEBTCv001444
	for mobile-ip-dist; Wed, 26 Sep 2001 07:11:29 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from bebop.France.Sun.COM (bebop.France.Sun.COM [129.157.174.15])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8QEBK7B001437
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 07:11:25 -0700 (PDT)
Received: from lillen (vpn133-11.EBay.Sun.COM [129.150.133.11])
	by bebop.France.Sun.COM (8.10.2+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id f8QEAov10618;
	Wed, 26 Sep 2001 16:10:50 +0200 (MET DST)
Date: Wed, 26 Sep 2001 16:06:15 +0200 (CEST)
From: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Subject: Re: [mobile-ip] Draft 15
To: Vijay Devarapalli <vijayd@iprg.nokia.com>
Cc: mobile-ip@sunroof.eng.sun.com
In-Reply-To: "Your message with ID" <3BB0BA81.E04F0959@iprg.nokia.com>
Message-ID: <Roam.SIMC.2.0.6.1001513175.16627.nordmark@bebop.france>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

> getting a new next header will cause a delay. this should be pursued
> separately and should not be in the MIPv6 spec.

Vijay,

Are you concerned with the delay caused by allocating the next header value
or the delay associated with implementations being modified?

The former delay is zero.
It is addressed by putting text like this in the IANA considerations section
in the spec
	This document requests that the IANA assign an IPv6 next header value
	(which come from the same space as IPv4 protocol numbers)
	for the Binding Update extension header in section X.

Then the IANA will allocate the number before the RFC is published as
proposed standard per the IANA instructions in RFC 2780.

  Erik



From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep 26 10:29:54 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20013
	for <mobileip-archive@odin.ietf.org>; Wed, 26 Sep 2001 10:29:53 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id HAA00618;
	Wed, 26 Sep 2001 07:18:12 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id HAA13344;
	Wed, 26 Sep 2001 07:12:56 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8QEBj7B001455
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 26 Sep 2001 07:11:46 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8QEBj34001454
	for mobile-ip-dist; Wed, 26 Sep 2001 07:11:45 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8QEBg7B001447
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 07:11:42 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id HAA21904
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 07:11:39 -0700 (PDT)
Received: from laposte.enst-bretagne.fr (laposte.enst-bretagne.fr [192.108.115.3])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id IAA14505
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 08:11:27 -0600 (MDT)
Received: from rsm.rennes.enst-bretagne.fr (rsm.rennes.enst-bretagne.fr [192.44.77.1])
	by laposte.enst-bretagne.fr (8.11.6/8.11.6) with ESMTP id f8QEBa914279
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 16:11:36 +0200
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr [193.52.74.194])
	by rsm.rennes.enst-bretagne.fr (8.8.8/8.8.8) with ESMTP id QAA04545
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 16:11:36 +0200 (MET DST)
Received: from givry.rennes.enst-bretagne.fr (localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.11.3/8.11.3) with ESMTP id f8QEBal29153
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 16:11:36 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200109261411.f8QEBal29153@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Draft 15 
In-reply-to: Your message of Wed, 26 Sep 2001 15:49:45 +0200.
             <Roam.SIMC.2.0.6.1001512185.18385.nordmark@bebop.france> 
Date: Wed, 26 Sep 2001 16:11:36 +0200
X-Virus-Scanned: by amavisd-milter (http://www.amavis.org/) at enst-bretagne.fr
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
 In your previous mail you wrote:

   Since there exists implementations of MIPv6 I wonder

=> I can answer for my (old) implementation

   1) how many of them have implementing piggybacking

=> only the receiving (mandatory) side

   2) of those have any looked at the effect of turning piggy-backing
   on and off.
   
=> no answer: the knob to put it on was never there.

   Is there any data?
   
=> at least one crash in a conformance test (unused code written
with regret :-). I've already explained in previous mails what
I think about piggybacking (BTW there is a warning against it in
the entrance of your previous building at Palo-Alto :-).

   ...
   I wonder what working strategies folks have tried in implementations.
   
=> as noted before delaying BUs can be done with or without piggybacking.
I can't see a reason to forbid or enforce delaying: the current MAY
is fine. (PS: I didn't implement it)

Thanks

Francis.Dupont@enst-bretagne.fr


From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep 26 11:33:27 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21263
	for <mobileip-archive@lists.ietf.org>; Wed, 26 Sep 2001 11:33:27 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id JAA27740;
	Wed, 26 Sep 2001 09:32:38 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id IAA29405;
	Wed, 26 Sep 2001 08:31:37 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8QFUW7B001742
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 26 Sep 2001 08:30:32 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8QFUW50001741
	for mobile-ip-dist; Wed, 26 Sep 2001 08:30:32 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8QFUS7B001734
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 08:30:28 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id IAA26225;
	Wed, 26 Sep 2001 08:30:30 -0700 (PDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id JAA25535;
	Wed, 26 Sep 2001 09:30:18 -0600 (MDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id IAA05518;
	Wed, 26 Sep 2001 08:29:58 -0700 (PDT)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f8QFTwj13998;
	Wed, 26 Sep 2001 08:29:58 -0700
X-mProtect:  Wed, 26 Sep 2001 08:29:58 -0700 Nokia Silicon Valley Messaging Protection
Received: from charliep.iprg.nokia.com (205.226.2.89, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpd0dqS1M; Wed, 26 Sep 2001 08:29:56 PDT
Message-ID: <3BB1F475.A0BF4DD1@iprg.nokia.com>
Date: Wed, 26 Sep 2001 08:29:57 -0700
From: "Charles E. Perkins" <charliep@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Erik Nordmark <Erik.Nordmark@eng.sun.com>
CC: mobile-ip@sunroof.eng.sun.com, Pat Calhoun <pcalhoun@diameter.org>
Subject: Re: [mobile-ip] Concerns/comments for aaa-keys and gen-key
References: <Roam.SIMC.2.0.6.1001499933.19612.nordmark@bebop.france>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hello Erik,

Erik Nordmark wrote:

>> But now the documents, even though they reflect the combined
>> wisdom of engineering some useful and interoperable implementations,
>> are apparently going to be vetoed.
> 
> Whatever gave up that impression?

I'm glad that no such impression was intended.  Thanks!


> We need the specs to be clear.
> 
> > The documents specify extensions for Mobile IP to be used with
> > a DIAMETER/AAA infrastructure.  The detailed specifications for
> > the message flows are expected to be in Mobile IP and AAA protocol
> > documents.
> 
> In separate documents? When will those documents be available for review?
> (Thanks to Fredrik I know the answer to my question.)
> 
> Which documents should an implementor building just an MN read?
> Must such an implementator read the diameter specs or should be
> be sufficient to read the mobile-ip specifications?
> (My preference would be to have specifications that are structured
> so that the the mobile-ip specs are self contained but with additional,
> non-required background reading in other documents.)

Whenever specifications are written that involve two (or more) other
base specifications, I thought it should be reasonable to expect that
implementers would read those base specifications.  I think that
applies in the case of these documents.  The specific processing
that is required for handling the extensions in the aaa-keys draft
should be in there, but it wouldn't be appropriate to say exactly
how to use DIAMETER I don't think.  In fact, these documents were
written before DIAMETER was selected (even before the working group
was formed, I think).  So an attempt was made to allow the Mobile IP
extensions work with _any_ AAA protocol that met the requirements
outlined in the Mobile IP requirements statements for AAA.

>> All protocols have particular spheres of applicability.
> [and later]
>> As far as I know, everyone believes this will be determined by
>> policy at AAAH.  It "should" be legitimate for a vendor to create
>> a proprietary key distribution protocol and utilize that between
>> mobile node and AAAH.  Thus, in such a scenario, your suggestion
>> amounts to a request to determine whether proprietary information
>> is sufficient for the purposes intended by the vendors.
> 
> Do you view that a vendor that takes these extensions and build
> a proprietary protocol should be able to say that their protocol
> conforms to an RFC?

Here, I think you meant,  "a proprietary security protocol".
If so, the answer is "yes".

Even so, I reckon it would be fine to mandate a particular security
algorithm, but I didn't build the prototypes, and I don't know which
algorithm people would choose for the default.  Is there something
besides IKE that we can mandate here?  Otherwise, I would worry that
placing the requirement would amount to an indefinite delay while
someone creates a new default choice -- which would then itself have
to undergo months of review and would probably be more complicated
than the whole rest of the AAA-keys document, maybe by an order
of magnitude.

>> Maybe it's a proprietary algorithm?  Again, others may be
>> better positioned to answer this.
> 
> You seem to be missing my point.
> How do you expect to get secure interoperability if you allow vendor X to
> only implement algorithm A and vendor Y only implement algorithm B?
> What is worse that in your view of the standards work, it would be fine
> for both vendors to claim "We fully conform to the RFC" yet there is no
> hope of interoperability.
> I thought the IETF was about interoperability first and foremost.
> What am I missing?

I didn't say you were missing anything, and I'm pretty sure I did
not miss your point.

However, I would emphasize the difference between building
protocols, vs. building systems.  A system has many parts,
and even using interoperable protocols can usually be built
so that there isn't any interoperation.  To take a trivial
example, two systems can implement IP and TCP and UDP and
yet not interoperate because of mismatch at the application
level.  I don't remember any requirement that TCP specify a
guaranteed interoperable application running at a well-known port.
IP itself doesn't require any interoperable transport protocol,
and yet without such a thing, two systems cannot interoperate.
Even so, we all think of IP as being a nice, small. interoperable
network protocol.

Here, the extensions are the interoperable containers for
key distribution data which (I think!) was expected to be
specified in other documents.

>> I would have expected that the way a node uses the NAI to identify
>> itself was more a matter for AAAH policy and operator contractual
>> negotiations.  It would not necessarily have any effect on the
>> format of the Mobile IP extensions, nor even the DIAMETER extensions,
>> and almost surely not much effect on the generalized extensions.
> 
> I think you are probably correct in that the semantics on the local part of
> the NAI doesn't affect the packet formats. But I think it has
> a profound effect on everything else including
>  - the question whether it is important to solve this privacy issue,
>  - mechanisms needed in the AAA system if the local part is transient IDs
>    instead of user names.
>  - a mechanism by which the AAA system and the MN can agree or securely
>    exchange which the sequence temporary IDs will be used.

No doubt about these points.  And yet, we cannot solve every
such problem in these supposedly simple extension documents.

> Thus if the IETF thinks it is important to solve this problem (and that is
> really my question) then it is obvious to me that some protocol specifications
> are needed in order for this to result in interoperable implementations.

This is exactly right.  The quesion is, whether "some protocol specifications"
will occur in the two documents in question, or in other documents.

And, one other point (out of order from your message):

>> Your comments seem to go right to the heart of what it means for
>> a working group to create protocol specifications.

> I think the purpose is stated at a high-level in RFC 2026 which talks
> about ...
>    The goals of the Internet Standards Process are:
>    o  technical excellence;
>    o  prior implementation and testing;
>    o  clear, concise, and easily understood documentation;
>    o  openness and fairness;  and
>    o  timeliness.
> 
>    [...]

> One stringest test for verifying the "clear and well-understod" is to
> expect that interoperable implementations result from merely reading
> the specification without the ability to ask questions of other
> implementors or authors.
> If such indepedent implementations achieve full interoperability at the first
> try we have a pretty good indication that the specs are clear.
> 
> But of course we can't mandate that folks provide such implementation efforts
> -  in fact most of the implementators have been involved in the standardization
> effort in the WG. Thus we rely on members of the community to read the
> specifications and try to find issues that would be unclear to a prospective
> implementor.
> 
> Do you have a different view of how we get interoperable implementations?

No, this is exactly right from my understanding.



Regards,
Charlie P.


From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep 26 12:06:23 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21952
	for <mobileip-archive@lists.ietf.org>; Wed, 26 Sep 2001 12:06:23 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id KAA28399;
	Wed, 26 Sep 2001 10:04:43 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA07179;
	Wed, 26 Sep 2001 09:03:32 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8QG2n7B001885
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 26 Sep 2001 09:02:49 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8QG2mNh001884
	for mobile-ip-dist; Wed, 26 Sep 2001 09:02:48 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8QG2j7B001877
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 09:02:45 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA06960;
	Wed, 26 Sep 2001 09:02:46 -0700 (PDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id JAA10031;
	Wed, 26 Sep 2001 09:02:46 -0700 (PDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id JAA07600;
	Wed, 26 Sep 2001 09:02:46 -0700 (PDT)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f8QG2kN00874;
	Wed, 26 Sep 2001 09:02:46 -0700
X-mProtect:  Wed, 26 Sep 2001 09:02:46 -0700 Nokia Silicon Valley Messaging Protection
Received: from charliep.iprg.nokia.com (205.226.2.89, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpdsEZeeu; Wed, 26 Sep 2001 09:02:44 PDT
Message-ID: <3BB1FC21.517BA23D@iprg.nokia.com>
Date: Wed, 26 Sep 2001 09:02:41 -0700
From: "Charles E. Perkins" <charliep@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Erik Nordmark <Erik.Nordmark@eng.sun.com>
CC: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Draft 15
References: <Roam.SIMC.2.0.6.1001513175.16627.nordmark@bebop.france>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hello Erik,

Erik Nordmark wrote:

> Vijay,
> 
> Are you concerned with the delay caused by allocating the next header value
> or the delay associated with implementations being modified?
> 
> The former delay is zero.
> It is addressed by putting text like this in the IANA considerations section
> in the spec
>         This document requests that the IANA assign an IPv6 next header value
>         (which come from the same space as IPv4 protocol numbers)
>         for the Binding Update extension header in section X.
> 
> Then the IANA will allocate the number before the RFC is published as
> proposed standard per the IANA instructions in RFC 2780.

Does this come up for discussion within the IPv6 working group
before IANA approves it?  If so, what do you think would be the
consensus view of that working group?

Regards,
Charlie P.


From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep 26 12:09:15 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22113
	for <mobileip-archive@lists.ietf.org>; Wed, 26 Sep 2001 12:09:14 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id KAA02912;
	Wed, 26 Sep 2001 10:08:29 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA08660;
	Wed, 26 Sep 2001 09:08:29 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8QG7a7B001951
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 26 Sep 2001 09:07:36 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8QG7aST001950
	for mobile-ip-dist; Wed, 26 Sep 2001 09:07:36 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8QG7W7B001943
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 09:07:32 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA08343
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 09:07:34 -0700 (PDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id KAA01720
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 10:07:23 -0600 (MDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id JAA07912;
	Wed, 26 Sep 2001 09:07:32 -0700 (PDT)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f8QG7We10473;
	Wed, 26 Sep 2001 09:07:32 -0700
X-mProtect:  Wed, 26 Sep 2001 09:07:32 -0700 Nokia Silicon Valley Messaging Protection
Received: from charliep.iprg.nokia.com (205.226.2.89, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpdlyTzsa; Wed, 26 Sep 2001 09:07:30 PDT
Message-ID: <3BB1FD42.248E33EC@iprg.nokia.com>
Date: Wed, 26 Sep 2001 09:07:30 -0700
From: "Charles E. Perkins" <charliep@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Francis Dupont <Francis.Dupont@inria.fr>
CC: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Draft 15
References: <200109251454.f8PEsFl23521@givry.rennes.enst-bretagne.fr>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hello Francis,

Francis Dupont wrote:
> 
>    Here is the current draft:
>         http://people.nokia.net/charlep/txt/mobilev6/mobilev6.txt

Yes, I regret the error.  Actually, 'i' is almost bad on my keyboard :-(.

	http://people.nokia.net/charliep/txt/mobilev6/mobilev6.txt

>        -  Removed the Prefix Length field from the Binding Update.
> 
> => I like the Prefix-Length==0 option and I am very displeased this
> is no more possible. As there are many dangling references to the
> Prefix Length I suggest to give this back!


> I have another concern about movement detection (10.4, 10.6) which
> makes the hidden and incorrect assumption that there is only one
> candidate default router. No, mobile is not wireless only and
> wireless is not cellular only.

Of course I agree with you that such an assumption would be wrong,
and that mobile != wireless.  But I didn't see where the assumption
was actually made.

Regards,
Charlie P.


From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep 26 12:19:49 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22453
	for <mobileip-archive@lists.ietf.org>; Wed, 26 Sep 2001 12:19:48 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id KAA15219;
	Wed, 26 Sep 2001 10:19:01 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA07014;
	Wed, 26 Sep 2001 09:18:57 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8QGHr7B002035
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 26 Sep 2001 09:17:53 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8QGHrOH002034
	for mobile-ip-dist; Wed, 26 Sep 2001 09:17:53 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from heliopolis.eng.sun.com (redhook.Eng.Sun.COM [152.70.24.37])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8QGHo7B002027
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 09:17:50 -0700 (PDT)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.eng.sun.com (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id JAA28595;
	Wed, 26 Sep 2001 09:16:34 -0700 (PDT)
Message-Id: <200109261616.JAA28595@heliopolis.eng.sun.com>
Date: Wed, 26 Sep 2001 09:16:33 -0700 (PDT)
From: James Kempf <James.Kempf@Sun.COM>
Subject: Re: [mobile-ip] No keying for "weak" global authentication
To: Erik.Nordmark@eng.sun.com, mat@cisco.com, mobile-ip@sunroof.eng.sun.com
Cc: mobile-ip@sunroof.eng.sun.com, charliep@iprg.nokia.com,
        Hesham.Soliman@epa.ericsson.se
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: MdejeuR1LX/uvR4G74wkSg==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Jari,

Your recommendation below strikes me as one of the most sensible I've
heard in this entire debate. I have not been following this thread
intensively, but it seems to me like it should be possible to
come up with a standard that leaves room for newer key management
protocols that are more flexible, while also allowing known,
perhaps suboptimal protocols to serve in the interim. This opinion may
be naively optimistic, and it certainly not informed by a thorough
study of the problem, but I think it could be a tactic to get MIPv6
out of its current holding pattern, as long as the IESG agrees, of course.

		jak

>Date: Wed, 26 Sep 2001 13:01:21 +0300
>From: Jari Arkko <Jari.Arkko@lmf.ericsson.se>
>To: Erik Nordmark <Erik.Nordmark@eng.sun.com>, mat@cisco.com
>CC: mobile-ip@sunroof.eng.sun.com, charliep@iprg.nokia.com, "Hesham Soliman 
(ERA)" <Hesham.Soliman@epa.ericsson.se>
>Subject: Re: [mobile-ip] No keying for "weak" global authentication
>
>> While I don't have a problem with this per-see I wonder how many flavours
>> will end up with. Potentially will have:
>>  - just return routability for each BU being sent - no crypto
>>  - return routability for first BU plus establish some keys so that
>>    subsequent BUs don't need the 3-way handshake required for
>>    return routability
>>  - IKE in the case when there is a PKI
>>  - Perhaps SUCV if not now but at a future date
>
>One observation I'd like to make here is that we
>have basically entered a very new area, in terms
>of existing research etc there isn't much old work.
>The whole problem of "weak" authentication wasn't 
>even known some time ago, and the the smart ways
>of handling the problem (like SUCV etc) have surfaced
>quite recently.
>
>Therefore, it would seem prudent to prepare for
>the possibility that research will come up with
>more results in the area, given some time. 
>
>Engineering-wise, this means that we should try
>to decouple the weak key management protocols
>from the rest of the system, allowing us to
>add new ones later. This decoupling might mean
>that any protocols designed for e.g. the
>return routability should be extensible to
>allow for SUCV etc at a future date, or that
>we simply have different protocols that all
>can key the same BU protection mechanism.
>
>It may also mean that we should on purpose
>try to *not* include everything we can in
>the initial spec, fearing the danger that
>we go too close to the leading edge and make
>a mistake...
>
>Jari



From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep 26 12:23:58 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22556
	for <mobileip-archive@odin.ietf.org>; Wed, 26 Sep 2001 12:23:57 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id JAA03884;
	Wed, 26 Sep 2001 09:21:39 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id IAA05645;
	Wed, 26 Sep 2001 08:57:41 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8QFuq7B001827
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 26 Sep 2001 08:56:52 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8QFupNa001826
	for mobile-ip-dist; Wed, 26 Sep 2001 08:56:51 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from heliopolis.eng.sun.com (bigbang.Eng.Sun.COM [152.70.8.30])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8QFum7B001819
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 08:56:48 -0700 (PDT)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.eng.sun.com (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id IAA27704
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 08:56:50 -0700 (PDT)
Message-Id: <200109261556.IAA27704@heliopolis.eng.sun.com>
Date: Wed, 26 Sep 2001 08:56:49 -0700 (PDT)
From: James Kempf <James.Kempf@Sun.COM>
Subject: Re: [mobile-ip] Optimizing Movement Detection on the AR 
To: mobile-ip@sunroof.eng.sun.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: uN6/0hAYQge6Sr8IUGbW3Q==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Alper,


>Reading Jim's text above, maybe what he has in mind is to unicast RA at L2 with 
>a multicast L3 destination? But I think unspecified destination address is 
>cleaner.
>

I agree that a unicast is better. The spec should just mention unicast.

		jak



From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep 26 13:19:36 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23963
	for <mobileip-archive@lists.ietf.org>; Wed, 26 Sep 2001 13:19:36 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA01997;
	Wed, 26 Sep 2001 10:18:45 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id KAA11095;
	Wed, 26 Sep 2001 10:17:22 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8QHFM7B002262
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 26 Sep 2001 10:15:22 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8QHFMvq002261
	for mobile-ip-dist; Wed, 26 Sep 2001 10:15:22 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8QHFI7B002254
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 10:15:18 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id KAA22667;
	Wed, 26 Sep 2001 10:15:20 -0700 (PDT)
Received: from sj-msg-core-2.cisco.com (sj-msg-core-2.cisco.com [171.69.24.11])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA05283;
	Wed, 26 Sep 2001 11:16:06 -0600 (MDT)
Received: from mira-sjc5-7.cisco.com (mira-sjc5-7.cisco.com [171.71.163.27])
	by sj-msg-core-2.cisco.com (8.11.3/8.9.1) with ESMTP id f8QHEDv09330;
	Wed, 26 Sep 2001 10:14:13 -0700 (PDT)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-7.cisco.com (Mirapoint)
	with ESMTP id AAJ23117;
	Wed, 26 Sep 2001 10:14:10 -0700 (PDT)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id KAA01367; Wed, 26 Sep 2001 10:14:10 -0700 (PDT)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15282.3298.522332.579900@thomasm-u1.cisco.com>
Date: Wed, 26 Sep 2001 10:14:10 -0700 (PDT)
To: mobile-ip@sunroof.eng.sun.com
Cc: Fredrik Johansson <fredrik.johansson@ipunplugged.com>,
        Erik.Nordmark@eng.sun.com, Charlie Perkins <charliep@IPRG.nokia.com>,
        Pat Calhoun <pcalhoun@diameter.org>
Subject: RE: [mobile-ip] Concerns/comments for aaa-keys and gen-key
In-Reply-To: <Roam.SIMC.2.0.6.1001495690.1688.nordmark@bebop.france>
References: <MJEMJBGGCLLDLFFAHLJKAEHFDGAA.fredrik.johansson@ipunplugged.com>
	<Roam.SIMC.2.0.6.1001495690.1688.nordmark@bebop.france>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Erik Nordmark writes:
 > I understand they need the appropriate level of trust in order implement
 > the AAA functionality. But my concern stems from the fact that the AAA
 > infrastructure is viewed as a way to distribute keying material to be shared
 > between MN and HA and that this keying material seems to be intended to
 > be used for more than protecting the AAA exchanges.
 > So while the MN/HA trusts the AAA infrastructure for those functions
 > it doesn't follow that they should be trusted with arbitrary keying material.

   Right. This has been what my discomfort with these
   drafts have been related too. Currently, AAA (RADIUS) 
   is a one way authentication proxy mechanism. DIAMETER
   brings mutual authentication to the table, but I think
   it's quite a leap of faith to say that AAA should then 
   become a key distribution protocol as well. Key distribution
   protocols are hard, and it is not clear to me that MIP is
   a very good venue to be pursuing them. At the very least,
   keying MN/HA SA's begs the question of why you should
   stop there. Why should AAA not be able to key other 
   protocols as well? How many specialized AAA key distribution
   protocols will there be? Will there be a sufficient amount
   of review by clueful security people to make certain that
   stupid mistakes are not made? Has anybody considered that
   there may be significant wheel-reinvention going on here
   (cf Kerberos).

   My feeling is that if this is done at all, it should
   be done in a new working group and most definitely
   under the security AD's watch.

	     Mike


From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep 26 13:45:18 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24639
	for <mobileip-archive@lists.ietf.org>; Wed, 26 Sep 2001 13:45:17 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA14733;
	Wed, 26 Sep 2001 10:44:16 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id KAA16452;
	Wed, 26 Sep 2001 10:34:00 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8QHWm7B002364
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 26 Sep 2001 10:32:48 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8QHWl9O002363
	for mobile-ip-dist; Wed, 26 Sep 2001 10:32:47 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8QHWi7B002356
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 10:32:44 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id KAA15937
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 10:32:44 -0700 (PDT)
Received: from laposte.enst-bretagne.fr (laposte.enst-bretagne.fr [192.108.115.3])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id KAA03227
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 10:32:43 -0700 (PDT)
Received: from rsm.rennes.enst-bretagne.fr (rsm.rennes.enst-bretagne.fr [192.44.77.1])
	by laposte.enst-bretagne.fr (8.11.6/8.11.6) with ESMTP id f8QHWc917982;
	Wed, 26 Sep 2001 19:32:38 +0200
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr [193.52.74.194])
	by rsm.rennes.enst-bretagne.fr (8.8.8/8.8.8) with ESMTP id TAA07601;
	Wed, 26 Sep 2001 19:32:39 +0200 (MET DST)
Received: from givry.rennes.enst-bretagne.fr (localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.11.3/8.11.3) with ESMTP id f8QHWcl29930;
	Wed, 26 Sep 2001 19:32:38 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200109261732.f8QHWcl29930@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: "Charles E. Perkins" <charliep@iprg.nokia.com>
Cc: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Draft 15 
In-reply-to: Your message of Wed, 26 Sep 2001 09:07:30 PDT.
             <3BB1FD42.248E33EC@iprg.nokia.com> 
Date: Wed, 26 Sep 2001 19:32:38 +0200
X-Virus-Scanned: by amavisd-milter (http://www.amavis.org/) at enst-bretagne.fr
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
 In your previous mail you wrote:

   > I have another concern about movement detection (10.4, 10.6) which
   > makes the hidden and incorrect assumption that there is only one
   > candidate default router. No, mobile is not wireless only and
   > wireless is not cellular only.
   
   Of course I agree with you that such an assumption would be wrong,
   and that mobile != wireless.  But I didn't see where the assumption
   was actually made.
   
=> almost everywhere in 10.4 after the introduction:
For instance:
   "so that it can switch to a new default router and
    to a new primary care-of address": the "and" suggests
   that the loss of "the" default router implies a movement.
   "it is likewise important for the mobile node to detect
    when it becomes unreachable for packets sent from its
    default router": this makes the assumption that packets
   can't come from another (default) router.
   etc...
More than one half of statements in 10.4 are false for a host with
multi-path routing (i.e. which can use many default routers at the
same time) connected to a link with a large number of routers.
My concern is the default router tracking method to detect movement
switched from an example to the only method... Illustration is
*not* recommendation.

Regards

Francis.Dupont@enst-bretagne.fr


From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep 26 13:49:41 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24892
	for <mobileip-archive@lists.ietf.org>; Wed, 26 Sep 2001 13:49:40 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA17078;
	Wed, 26 Sep 2001 10:48:56 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id KAA20378;
	Wed, 26 Sep 2001 10:45:44 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8QHiS7B002425
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 26 Sep 2001 10:44:28 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8QHiSRR002424
	for mobile-ip-dist; Wed, 26 Sep 2001 10:44:28 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from heliopolis.eng.sun.com (heliopolis.Eng.Sun.COM [152.70.1.39])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8QHiP7B002417
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 10:44:25 -0700 (PDT)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.eng.sun.com (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id KAA02870;
	Wed, 26 Sep 2001 10:44:26 -0700 (PDT)
Message-Id: <200109261744.KAA02870@heliopolis.eng.sun.com>
Date: Wed, 26 Sep 2001 10:44:25 -0700 (PDT)
From: James Kempf <James.Kempf@sun.com>
Subject: RE: [mobile-ip] New BETH Draft
To: mobile-ip@sunroof.eng.sun.com, Basavaraj.Patil@nokia.com
Cc: James.Kempf@sun.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: dsY5PzZci4AksSLvklMtuw==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Hi Raj,

Thanx for the comments. Responses below.


>Following this thread, I tend to agree with Hesham. I do not believe
>it is required to advertise capabilities of FMIPv6 or BETH to the MN
>via router advertisements. As has been discussed at length in this
>thread the MN will know if the network supports fast HO when it
>sends a ProxyRtrSolicit and receives an Advt as a response. And
>similarly the network knows that an MN is capable of fast HO when
>it receives the F-BU as a response to a ProxyRtrAdvt.

The issue here is the case where an FMIPv6 MN has transitioned
into an area where FMIPv6 is not available and only SMIPv6 is.
The MN will continue to send out ProxyRtrSolicits, or, will
do so at least once, presuming it gets clueful when the AR
doesn't reply and stops trying. I suppose one gratuitous
over the air message is OK. However, I would like to include
the following text in the FMIPv6 spec in large, glowing, neon
orange letters (:-)):

	If the MN does not receive a response to a ProxyRtrAdv,
	it MUST discontinue performing FMIPv6 handover,
	assume that the AR does not support FMIPv6, and
	revert to the standard MIPv6 handover algorithm.
	Similarly, if the AR does not receive a F-BU in
	response to a ProxyRtAdv, it MUST discontinue
	performing FMIPv6 handover, assume that the MN
	does not support FMIPv6, and revert to the standard
	MIPv6 handover algorithm
	

It is *absolutely essential* that the spec be very clear about
this, so that implementations do not end up wasting expensive
radio network bandwidth by sending out gratuitous radio
traffic. It is by no means certain that implementors will do
the right thing given the current spec. I've seen cases where
even when the protocol spec explicitly specified measures to conserve
network bandwidth, implementations violated the spec in ways
that resulted in wasted bandwidth. Fortunately (or perhaps
unfortunately, since we have to put up with it on our network) it
was for a wired network protocol. Radio spectrum is too
expensive to waste.

Do you agree to this change? 

> So what do
>you do when the network performs HOs via BETH? I think you should
>allow the MN to still send a ProxyRtrSolct as a result of some L2
>trigger on the MN but either ignore the message if the network is doing
>a HO using BETH or send a NAK to the MN as a response to the
>ProxyRtrSlct. I agree that this causes some additional signaling but
>it keeps implementations simple (relatively) and also avoids having to
>build new extensions or flags into router advts any more than we already
>have.
>

We have had this conversation before, and I simply do not think it
is necessary to have the ProxyRtSolct every time the MN hands over.
For the price of a single notification when the MN enters a BETH
coverage area, you get performance that is strictly limited by
L2 handover. If you would rather not have the notification come
via a RtAdv, that is fine. The ProxyRtAdv will work just as well.
With a code in the PrxyRtAdv telling the MN
that it has entered the BETH coverage area, the MN can be notified to suppress
any over the air signaling. After that, the MN's handover is handled
by BETH. When the MN is about to transition out of a BETH coverage
area, it gets a ProxyRtAdv indicating that it should revert to
FMIPv6 or SMIPv6 handover. The ProxyRtAdv and SolProxyRtAdv already
have room for such a code, and it is used to notify the MN about
certain cases w.r.t. to the handover, this is just another one.

Do you see any issues with this?

		jak



From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep 26 14:49:06 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26082
	for <mobileip-archive@lists.ietf.org>; Wed, 26 Sep 2001 14:49:05 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id MAB13573;
	Wed, 26 Sep 2001 12:48:14 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id LAA21289;
	Wed, 26 Sep 2001 11:48:09 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8QIkw7B002861
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 26 Sep 2001 11:46:58 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8QIkv5L002860
	for mobile-ip-dist; Wed, 26 Sep 2001 11:46:57 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8QIks7B002853
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 11:46:54 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id LAA00913
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 11:46:56 -0700 (PDT)
Received: from sj-msg-core-4.cisco.com (sj-msg-core-4.cisco.com [171.71.163.10])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id LAA15476
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 11:46:55 -0700 (PDT)
Received: from mira-sjc5-7.cisco.com (mira-sjc5-7.cisco.com [171.71.163.27])
	by sj-msg-core-4.cisco.com (8.11.3/8.9.1) with ESMTP id f8QIl7d15337
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 11:47:07 -0700 (PDT)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-7.cisco.com (Mirapoint)
	with ESMTP id AAJ26570;
	Wed, 26 Sep 2001 11:46:48 -0700 (PDT)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id LAA01392; Wed, 26 Sep 2001 11:46:47 -0700 (PDT)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15282.8855.493145.16450@thomasm-u1.cisco.com>
Date: Wed, 26 Sep 2001 11:46:47 -0700 (PDT)
To: mobile-ip@sunroof.eng.sun.com
Subject: [mobile-ip] more on gen-keys
In-Reply-To: <15282.3298.522332.579900@thomasm-u1.cisco.com>
References: <MJEMJBGGCLLDLFFAHLJKAEHFDGAA.fredrik.johansson@ipunplugged.com>
	<Roam.SIMC.2.0.6.1001495690.1688.nordmark@bebop.france>
	<15282.3298.522332.579900@thomasm-u1.cisco.com>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

First, I should say that I think that this draft
is the right overall approach, so don't take this
as an indictment.

1) It's not entirely clear to me how general the
   gen-keys draft actual is. According to its
   introduction, it should be possible to use many
   different types of authentication schemes to
   key up the SA. While I'm not saying that it
   isn't possible, it would be nice to see some 
   flows of at least two schemes as an existance
   proof. Preferably, it would sketch out how it
   would be possible to do so using a cert based
   public key scheme (PKCS XX), Kerberos, and
   the AAA proposal. This would go a long way to
   making what is supposed to be a framework more
   understandable.

2) It seems to me that this draft should probably
   define some minimum requirements on whatever
   the payloads are, ie, must provide replay
   protection, mutual authentication, etc.

3) Eric might have already mentioned this, but
   it's not clear to me what the security 
   relationship between MN and HA, HA and FA,
   along with FA to FA. For example, when a mobile
   node moves, can the HA/FA's before it derive
   the secret between MN and it's current
   FA? If so, is that acceptible? How does a MN
   prevent a FA to pass things to another FA 
   that it doesn't want to be a participant? Are
   there any sceanrios where the MN could be 
   compromised without its knowledge?

4) It's not very clear to me why there needs to
   be specific message types for each
   combination of HA, FA, MN. Why isn't it sufficient
   to just have a single suboption and allow the
   context to determine who's talking to whom?
   Have missed something?   
    

	Mike


From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep 26 15:04:07 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26483
	for <mobileip-archive@lists.ietf.org>; Wed, 26 Sep 2001 15:04:06 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id NAA27417;
	Wed, 26 Sep 2001 13:03:03 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id MAA25136;
	Wed, 26 Sep 2001 12:02:59 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8QJ207B002934
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 26 Sep 2001 12:02:00 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8QJ20Vs002933
	for mobile-ip-dist; Wed, 26 Sep 2001 12:02:00 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8QJ1u7B002926
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 12:01:56 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id MAA14123;
	Wed, 26 Sep 2001 12:01:57 -0700 (PDT)
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA16501;
	Wed, 26 Sep 2001 13:02:54 -0600 (MDT)
Received: from mira-sjc5-7.cisco.com (mira-sjc5-7.cisco.com [171.71.163.27])
	by sj-msg-core-1.cisco.com (8.11.6/8.9.1) with ESMTP id f8QJ1vG13707;
	Wed, 26 Sep 2001 12:01:57 -0700 (PDT)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-7.cisco.com (Mirapoint)
	with ESMTP id AAJ27143;
	Wed, 26 Sep 2001 12:01:54 -0700 (PDT)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id MAA01400; Wed, 26 Sep 2001 12:01:54 -0700 (PDT)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15282.9762.49677.55899@thomasm-u1.cisco.com>
Date: Wed, 26 Sep 2001 12:01:54 -0700 (PDT)
To: mobile-ip@sunroof.eng.sun.com
Cc: Erik Nordmark <Erik.Nordmark@eng.sun.com>, mat@cisco.com,
        charliep@iprg.nokia.com,
        "Hesham Soliman (ERA)" <Hesham.Soliman@epa.ericsson.se>
Subject: Re: [mobile-ip] No keying for "weak" global authentication
In-Reply-To: <3BB1A771.AC4918D5@lmf.ericsson.se>
References: <15280.46923.497792.293898@thomasm-u1.cisco.com>
	<Roam.SIMC.2.0.6.1001441689.27166.nordmark@bebop.france>
	<15280.52983.402820.137567@thomasm-u1.cisco.com>
	<3BB1A771.AC4918D5@lmf.ericsson.se>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Jari Arkko writes:
 > One observation I'd like to make here is that we
 > have basically entered a very new area, in terms
 > of existing research etc there isn't much old work.
 > The whole problem of "weak" authentication wasn't 
 > even known some time ago, and the the smart ways
 > of handling the problem (like SUCV etc) have surfaced
 > quite recently.

   Oh, I wouldn't say that it's _that_ new. I know
   that a certain rilly big router company who
   shall go unnamed has had to make patches to its
   TCP code to make certain that the ISS is random
   to provide protection against guessing barge in
   attacks...

   At it's base, that is what all of these
   proposals are providing when you strip all the
   rest of the bells and whistles... Which is why
   I think it would be prudent to do exactly that
   in the MIPv6 draft itself.

 > Therefore, it would seem prudent to prepare for
 > the possibility that research will come up with
 > more results in the area, given some time. 

   Right. That's pretty much the point of the
   mail I sent out with this subject: strip what
   needs to be done with weak authentication down
   to it essentials for the mipv6 draft, and add 
   any enhancements later in another draft. 
   Generating a shared secret is not one of those
   essentials.

		Mike


From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep 26 18:46:44 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA00571
	for <mobileip-archive@odin.ietf.org>; Wed, 26 Sep 2001 18:46:43 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id PAA14346;
	Wed, 26 Sep 2001 15:46:06 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id PAA10191;
	Wed, 26 Sep 2001 15:45:40 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8QMiO7B003383
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 26 Sep 2001 15:44:24 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8QMiODP003382
	for mobile-ip-dist; Wed, 26 Sep 2001 15:44:24 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from heliopolis.eng.sun.com (bigbang.Eng.Sun.COM [152.70.8.30])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8QMiK7B003375
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 15:44:20 -0700 (PDT)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by heliopolis.eng.sun.com (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id PAA18189
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 15:44:23 -0700 (PDT)
Message-Id: <200109262244.PAA18189@heliopolis.eng.sun.com>
Date: Wed, 26 Sep 2001 15:44:22 -0700 (PDT)
From: James Kempf <James.Kempf@Sun.COM>
Subject: [mobile-ip] MIPv6 Handover Coverage Area Transition Issues
To: mobile-ip@sunroof.eng.sun.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: pHzVjzRIz+/hFafS0JvGvg==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc 
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

All,

Last week, Rajeev Kooldi and I had a very productive discussion in which
I thought we had pretty much nailed down the technical interoperability issues 
involved in transitioning between areas in which the ARs support different
MIPv6 handover algorithms. This week, the basic issue of handover coverage
area transition has been raised yet again.

The major issue that seems to have arisen this week is including some
notification of the handover algorithm supported in the standard MIPv6
Router Advertisement and Solicitation for Router Advertisement. The
issue was that this is unnecessary and wastes network bandwidth. 

Below, I've attached a description of how a transition could work without
having any modification to the Router Advertisement or Solicitation
for Router Advertisement. All notification of transition would occur
through FMIPv6 signaling. There is only one "bad case:" a network-initiated
handover from an FMIPv6 AR to a BETH AR. The network must first
establish whether the MN is a standard MIPv6 node or is FMIPv6/BETH
capable before it can perform BETH, otherwise, it may conclude that
the MN can't do BETH and a potential for optimization will be lost. 

I am interested in hearing some feedback on this, but I would like it
to be constructive and focused at improving the transition protocol
so that it is simpler, while still maintaining the promising optimization
potential of the various algorithms. Baiting, flaming, and other such tactics
will result in my hitting the "Delete" button, as they should for
every participant in every IETF list. I am interested in achieving
closure on this so that we can move forward with the spec.

Thanx.

		jak
		
-------------------------------------------------------------------------------
This is a proposal about how to handle transitions between coverage
areas providing different optimized handover support with a minimum
of notification to the MN. Transitions from/to each kind of coverage
area are considered. The proposal is based on using the FMIPv6
expanded usage of the message code field, which already is used for notifying 
the MN of particular kinds of handover.

Note: SMIPv6 stands for "Standard MIPv6" handover.

1) BETH -> SMIPv6

AR sends MN a PrRtAdv with code SMIPV6-HANDOVER.

MN uses SMIPv6 movement detection. MN solicits a RtAdv if it can
determine when it is on the new AR, otherwise waits for the unsolicited
RtAdv.

2) SMIPv6 -> BETH

The handover from the last SMIPv6 AR to the first BETH/FMIPv6 AR
is done using the SMIPv6 movement detection.

Handover to the next BETH router is done according to 5).

3) SMIPv6 -> FMIPv6

Same as 2).

4) FMIPv6 -> SMIPv6

Same as 1).

5) FMIPv6 -> BETH

Two cases: network initiated and mobile initiated.

    a) Network Initiated:
	AR sends PrRtAdv to MN with code BETH-HANDOVER.
	   
           i) If MN is BETH capable, it supresses all 
	      handover related radio traffic until it
	      needs a new CoA. ARs take care of handover.

	   ii) If MN is not BETH capable, it sends an
	       F-BU and the network continues to do
	       FMIPv6 handover.

	   iii) Concern: The MN would have to do at
		least *one* FMIPv6 handover before
		the AR could distinguish between
		a BETH capable MN and one that
		was not capable of doing FMIPv6
		at all, because there is no signaling
		back from the MN for the AR to distinguish
		between:

		  - A MN that is BETH capable and is
		    supressing handover related signaling
		    because it knows the network will
		    handle it.

		  - A completely nonFMIPv6 MN that is
		    incapable of responding to FMIPv6 messaging.

		We could solve this problem by having the
		MN issue a PrRtSol for the old AR when it
		came up in the network and include the code BETH-HANDOVER,
		and have AR respond with a PrRtAdv with its own
		address. This would avoid having to put this
		information into the RtAdv. 

    b) Mobile Initiated:
	MN sends SolPrRtAdv to old AR with code BETH-HANDOVER.

	i) If new AR is BETH capable, old AR replies with 
	   PrRtAdv having code BETH-HANDOVER. MN supresses
	   handover related signaling until it needs a new CoA.

	ii) If new AR is not BETH capable, old AR replies
	    with PrRtAdv having code FMIPv6-HANDOVER. MN
	    continues FMIPv6 handover.

6) BETH->FMIPv6

Essentially, this works the same as in 5), except the code is
FMIPv6-HANDOVER. 

Network-initiated:

	The old AR issues a PrRtAdv for the new AR with code
	FMIPv6-HANDOVER.

	The MN begins doing FMIPv6 handover, i.e. issues an F-BU
	when on the new AR, etc.

Mobile-initiated:

	The MN issues a SolPrRtAdv for the new AR with code
	FMIPv6-HANDOVER.

	The old AR replies with PrRtAdv with code FMIPv6-HANDOVER.

	Thereafter, the MN/AR does FMIPv6 handover.


7) nonFMIPv6 capable 

If an FMIPv6 AR sends a PrRtAdv to an MN that has not established
that it is BETH capable and it receives no F-BU, the network
MUST suppress sending further FMIPv6 signaling over the air
and allow the MN to do SMIPv6 handover.

If an FMIPv6 MN sends a SolPrRtAdv to an AR and it gets no
PrRtAdv in response, it MUST suppress sending further FMIPv6
signaling over the air and do SMIPv6 handover.
	



From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep 26 21:10:57 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA01871
	for <mobileip-archive@odin.ietf.org>; Wed, 26 Sep 2001 21:10:56 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id SAA03003;
	Wed, 26 Sep 2001 18:10:03 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id SAA13375;
	Wed, 26 Sep 2001 18:09:47 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8R18I7B003673
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 26 Sep 2001 18:08:18 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8R18IwA003672
	for mobile-ip-dist; Wed, 26 Sep 2001 18:08:18 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8R18E7B003665
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 18:08:14 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id SAA29488
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 18:08:15 -0700 (PDT)
Received: from mgw-dax1.ext.nokia.com (mgw-dax1.ext.nokia.com [63.78.179.216])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id TAA18339
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 19:09:08 -0600 (MDT)
Received: from davir03nok.americas.nokia.com (davir03nok.americas.nokia.com [172.18.242.86])
	by mgw-dax1.ext.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f8R18A315972
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 20:08:11 -0500 (CDT)
Received: from daebh001.NOE.Nokia.com (unverified) by davir03nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T563c8a62e1ac12f256126@davir03nok.americas.nokia.com>;
 Wed, 26 Sep 2001 20:08:09 -0500
Received: from daebe005.NOE.Nokia.com ([172.18.242.203]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.2966);
	 Wed, 26 Sep 2001 20:08:09 -0500
content-class: urn:content-classes:message
Subject: RE: [mobile-ip] Concerns/comments for aaa-keys and gen-key
Date: Wed, 26 Sep 2001 20:08:09 -0500
Message-ID: <82ECD4351A4A9547957C606034A3CB8D0B0212@daebe005.NOE.Nokia.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Thread-Topic: [mobile-ip] Concerns/comments for aaa-keys and gen-key
X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0
Thread-Index: AcFGi8S0WLKKmrJ9EdWxLwAIx6TWeAAYrjxQ
From: "Faccin Stefano (NRC/Dallas)" <stefano.faccin@nokia.com>
To: <petrescu@crm.mot.com>, <mobile-ip@sunroof.eng.sun.com>
Cc: <Erik.Nordmark@eng.sun.com>
X-OriginalArrivalTime: 27 Sep 2001 01:08:09.0674 (UTC) FILETIME=[DF5F3AA0:01C146F0]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by sunroof.eng.sun.com id f8R18F7B003666
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 8bit

Hello Alex,

please find some comments/answers below.

Stefano

> -----Original Message-----
> From: ext Alexandru Petrescu [mailto:petrescu@crm.mot.com]
> Sent: Wednesday, September 26, 2001 7:57 AM
> To: Fredrik Johansson
> Cc: Erik.Nordmark@eng.sun.com; mobile-ip@sunroof.eng.sun.com
> Subject: Re: [mobile-ip] Concerns/comments for aaa-keys and gen-key
> 
> 
> Hi Frederik,
> 
> Since this has been brought up, I have a few questions that I wanted
> to ask a while back.  See inline, thanks.
> 
> Erik:
> > >> 4. Between the lines there appear to be some architectural
> > >> assumptions e.g. that AAAh and HA have some high degree of mutual
> > >> trust, which seem to imply that the solution might not be a good
> > >> fit when the AAAh and HA are operated by different entities.
> 
> Frederik:
> > The assumption is that a AAA server (let it be AAAh or 
> AAAf) have a high
> > degree of mutual trust with the HA. And that AAA servers of 
> different
> > domains have a mutual trust (Service Level Agreement).
> 
> It looks to me that an (AAAH, HA) must have SLA's with every AAAF's in
> whose domains that HA's MN could possibly roam.  Doesn't this boil
> down to a scaleability issue similar to Mobile IPv6 (in which MN must
> have trust relationships with any possible CN)?

In the current drafts there is no assumption regarding a trusted
relation between AAAF and the HA in the home domain of the MN. The
drafts allow for dynamic allocation of a HA in a foreign domain, thus
the security relation assumed in the draft is between AAAFs and HAs
belonging to the same domain.

In the drafts it is assumed that AAAH and AAAF have a trusted relation
in the sense that it is possible to safely exchange information between
AAAH and AAAF. How this is achieved is another matter. A simple way to
do it would be to have an SA between AAAF and AAAH, but as you say this
can lead to scalability issues. However, the concept of "security
gateway" can be used, where entity in the foreign/home domain share a
local SAf/SAh with security gateways, and security gateways belonging to
visited and home domain share another SA (e.g. established as result of
roaming agreements or through other mechanisms). In such way, AAAF can
send messages protecting them with SAf, the security gateways transmits
it to the home domain using SA, and the gateway in the home network uses
SAh to protect the message to AAAH. In this way scalability can be
achieved, as already demonstrated in other large scale commercial
networks using similar concepts.  

Finally, the issue is quite different from the security issue with
Mobile IPv6. In Mobile IPv6 it wouldn't be very "clean" to use security
gateways, since we would break the end-to-end nature of Binding Updates.
Int he AAA case we just want to make sure that messages exchanged, e.g,
between AAAF and AAAH are protected (mainly integrity protection and
data authentication), but there isn't really an end-to-end issue.

> 
> I can understand trust between AAAH and HA, but I suppose that trust
> relationship between AAAH and AAAF's, or between HA's and AAAF's, are
> difficult.  If I'm missing something, sorry, please enlighten me.
> 
> If one can assume trust between an HA and any AAAF then why not using
> same method between MN and CN?
> 
> Alex
> 


From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep 26 21:44:28 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA03195
	for <mobileip-archive@odin.ietf.org>; Wed, 26 Sep 2001 21:44:27 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id TAA04398;
	Wed, 26 Sep 2001 19:43:20 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id SAA04356;
	Wed, 26 Sep 2001 18:43:13 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8R1de7B003907
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 26 Sep 2001 18:39:40 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8R1de2W003906
	for mobile-ip-dist; Wed, 26 Sep 2001 18:39:40 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8R1da7B003899
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 18:39:36 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id SAA26716
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 18:39:38 -0700 (PDT)
Received: from newish7.ericsson.com.au ([203.61.155.116])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id TAA02264
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 19:40:31 -0600 (MDT)
Received: from brsf10.epa.ericsson.se (igw2.ericsson.com.au [203.61.155.10])
	by newish7.ericsson.com.au (8.9.3+Sun/8.9.3) with ESMTP id LAA25495
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 11:37:53 +1000 (EST)
Received: from eaubrnt019.epa.ericsson.se (eaubrnt019.epa.ericsson.se [146.11.9.165])
	by brsf10.epa.ericsson.se (8.9.3+Sun/8.9.3) with ESMTP id LAA28376
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 11:38:59 +1000 (EST)
Received: by eaubrnt019.epa.ericsson.se with Internet Mail Service (5.5.2653.19)
	id <TSJKLGFT>; Thu, 27 Sep 2001 11:38:58 +1000
Message-ID: <4B6BC00CD15FD2119E5F0008C7A419A51308ECA9@eaubrnt018.epa.ericsson.se>
From: "Hesham Soliman (EPA)" <Hesham.Soliman@ericsson.com.au>
To: "'mobile-ip@sunroof.eng.sun.com'" <mobile-ip@sunroof.eng.sun.com>
Subject: [mobile-ip] mail
Date: Thu, 27 Sep 2001 11:38:57 +1000
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C146F5.2CAD20C0"
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

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

------_=_NextPart_001_01C146F5.2CAD20C0
Content-Type: text/plain

Sorry for the bouncing mails for those of you who might have answered
one of my mails. This email address should work now. 
If you sent me something in the last 24 hours I probably haven't
got it.

Cheers,
Hesham

------_=_NextPart_001_01C146F5.2CAD20C0
Content-Type: text/html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=US-ASCII">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2654.19">
<TITLE>mail</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=2 FACE="Arial">Sorry for the bouncing mails for those of you who might have answered</FONT>
<BR><FONT SIZE=2 FACE="Arial">one of my mails. This email address should work now. </FONT>
<BR><FONT SIZE=2 FACE="Arial">If you sent me something in the last 24 hours I probably haven't</FONT>
<BR><FONT SIZE=2 FACE="Arial">got it.</FONT>
</P>

<P><FONT SIZE=2 FACE="Arial">Cheers,</FONT>
<BR><FONT SIZE=2 FACE="Arial">Hesham</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C146F5.2CAD20C0--


From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep 26 22:12:50 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA03436
	for <mobileip-archive@odin.ietf.org>; Wed, 26 Sep 2001 22:12:49 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id TAA17493;
	Wed, 26 Sep 2001 19:11:58 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id TAA06391;
	Wed, 26 Sep 2001 19:11:51 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8R2Aa7B003991
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 26 Sep 2001 19:10:36 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8R2Aavi003990
	for mobile-ip-dist; Wed, 26 Sep 2001 19:10:36 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8R2AW7B003983
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 19:10:32 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id TAA08462
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 19:10:34 -0700 (PDT)
Received: from WIN-INET-01.wingroup.windeploy.ntdev.microsoft.com ([131.107.3.118])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id TAA22776
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 19:10:33 -0700 (PDT)
Received: from win-hub-01.wingroup.windeploy.ntdev.microsoft.com ([157.54.5.229]) by WIN-INET-01.wingroup.windeploy.ntdev.microsoft.com with Microsoft SMTPSVC(5.0.2195.3651);
	 Wed, 26 Sep 2001 19:05:04 -0700
Received: from 157.54.5.226 by win-hub-01.wingroup.windeploy.ntdev.microsoft.com (InterScan E-Mail VirusWall NT); Wed, 26 Sep 2001 19:05:04 -0700
Received: from win-msg-01.wingroup.windeploy.ntdev.microsoft.com ([157.54.0.52]) by win-hub-01.wingroup.windeploy.ntdev.microsoft.com with Microsoft SMTPSVC(5.0.2195.3651);
	 Wed, 26 Sep 2001 19:05:04 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.0.5716.0
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Subject: [mobile-ip] Joining to SSM sources that are IPv6 mobile nodes
Date: Wed, 26 Sep 2001 19:05:04 -0700
Message-ID: <2E33960095B58E40A4D3345AB9F65EC102DB7D6A@win-msg-01.wingroup.windeploy.ntdev.microsoft.com>
Thread-Topic: Joining to SSM sources that are IPv6 mobile nodes
thread-index: AcFG+L0zdxWOSEFrQS2r4c4TfpMGsQ==
From: "Dave Thaler" <dthaler@windows.microsoft.com>
To: <mobile-ip@sunroof.eng.sun.com>, <magma@innovationslab.net>,
        <ssm-interest@external.cisco.com>
X-OriginalArrivalTime: 27 Sep 2001 02:05:04.0686 (UTC) FILETIME=[D2E0B4E0:01C146F8]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by sunroof.eng.sun.com id f8R2AX7B003984
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 8bit

Sorry for the cross-post, but this issue really does concern 
interactions between drafts in three different WGs:
MobileIP: draft-ietf-mobileip-ipv6-14.txt, section 10.19
MAGMA: draft-vida-mld-v2-01.txt
SSM: draft-ietf-ssm-overview-01.txt
(Please trim the recipients when responding, if appropriate.)

Starting from the Mobile IPv6 spec:
> A mobile node that wishes to send packets to a multicast group
> also has two options:  (1) send directly on the foreign link being
> visited; or (2) send via a tunnel to its home agent.  Because
> multicast routing in general depends upon the Source Address used in
> the IPv6 header of the multicast packet, a mobile node that tunnels a
> multicast packet to its home agent MUST use its home address as the
> IPv6 Source Address of the inner multicast packet.

The issue is how to continue getting data to receivers after a mobile
node moves.
Method (2) works fine for SSM, but has the obvious inefficiency.
Method (1) does not work as is for SSM.

I'll assume the sender has advertised (HA,G) in whatever method (e.g. a
web page) he uses to announce the session, just like the session would
advertise HA in any method used to get unicast clients to connect to
him.  (The sender could just as well use (COA,G) but the same issues
arise if it subsequently moves, from my understanding.)

In the SSM model, when receivers join (HA,G) via MLDv2, join state is
constructed along the path to HA (i.e. hitting the home agent).  Any
data sent directly on the foreign link being visited will go nowhere,
since there is no join state there.

A bad answer would be "do nothing, we don't care if sourcing SSM is
broken".

A simple answer would be "an SSM source MUST use option (2), i.e.
tunnel packets to the home agent".  In this case, either option (1)
would never be used for any multicast traffic, or else the host would
have to know whether a receiver might want to use an include-mode list
with MLDv2 and tunnel to the home agent if so.  Personally, I don't
like this answer, but if this is what the consensus turns out to be,
then it should be documented in the Mobile IPv6 spec (no effect on the
SSM or MAGMA WGs), and apis to inform the mobile node stack that it
MUST tunnel to the home agent may be required.

Another answer, which would require adding rules to both the Mobile
IPv6 and MLDv2 specs (and probably mentioning it in the SSM overview
doc), would be to make method (1) work for SSM sources.  A potential
solution here is twofold: 

1) If an MLDv2 host is sending an include-mode report for a source X,
and a binding cache entry exists for X with a care-of-address COA, then
put both X and COA in the membership report.  (This means that if you
can somehow get a Binding Update to all the group members, then they'll
be able to receive packets sourced from COA, since routers will
construct join state back to the foreign link.)  It needs to join to
both addresses so that if the node moves again, it won't be stuck
waiting for data from the old COA.

2) A mobile node sourcing traffic when away from home needs to get a
Binding Update to all the group members.  I believe this can be done by
tunneling a packet via the home agent (and hence must have a source
address of its home address) which contains a Binding Update with
an Alternate Care-of Address of its current COA.  This would need to be
done periodically, so that new receivers get it.

Comments?  Am I missing anything?

-Dave Thaler



From owner-mobile-ip@sunroof.eng.sun.com  Wed Sep 26 22:18:08 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA03522
	for <mobileip-archive@odin.ietf.org>; Wed, 26 Sep 2001 22:18:08 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id UAA19797;
	Wed, 26 Sep 2001 20:17:08 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id TAA07113;
	Wed, 26 Sep 2001 19:17:10 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8R2GV7B004050
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 26 Sep 2001 19:16:31 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8R2GVk4004049
	for mobile-ip-dist; Wed, 26 Sep 2001 19:16:31 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8R2GR7B004042
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 19:16:27 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id TAA06932
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 19:16:14 -0700 (PDT)
Received: from e34.bld.us.ibm.com (e34.co.us.ibm.com [32.97.110.132])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id TAA24453
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 19:16:14 -0700 (PDT)
Received: from westrelay02.boulder.ibm.com (westrelay02.boulder.ibm.com [9.99.140.23])
	by e34.bld.us.ibm.com (8.9.3/8.9.3) with ESMTP id WAA118800
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 22:13:53 -0400
Received: from d03nm103.boulder.ibm.com (d03nm103.boulder.ibm.com [9.99.140.95])
	by westrelay02.boulder.ibm.com (8.11.1m3/NCO v4.97.1) with ESMTP id f8R2Evj119624
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 20:14:57 -0600
From: "Venkata Jagana" <jagana@us.ibm.com>
Importance: Normal
Subject: Re: [mobile-ip] Comments on Mobile IPv6 draft 14
To: mobile-ip@sunroof.eng.sun.com
X-Mailer: Lotus Notes Release 5.0.3 (Intl) 21 March 2000
Message-ID: <OF2DC197EB.BA73FEDD-ON88256AD4.000A8F28@boulder.ibm.com>
Date: Wed, 26 Sep 2001 19:14:55 -0700
X-MIMETrack: Serialize by Router on D03NM103/03/M/IBM(Release 5.0.8 |June 18, 2001) at
 09/26/2001 08:14:57 PM
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>


Hello Peter,


> It might be a good idea though to add a bit in the draft explaining this.

     I think so.

> However, I should like give another scenario almost similar to yours:
> The MN returns to network 'B' but gets another (second) CoA at 'B'. In
> this case, the "first CoA at 'B'" does not return home, and the
> deregistration at home agent at 'B' shouldn't be done.

     You may 'not' like to get another CoA if your MN already knew that
     it currently has a home registration with that 'B' network. And
     otherwise, the packets destined for old CoA at 'B' will be tunnelled
     to network 'C' and from there, again it will be tunnelled back
     to this new CoA at 'B' which I believe is messy. In fact, you can
     avoid this cris-cros situation by simple deregistering at 'B'
     and grab the old CoA at 'B'. I can imagine a scenario where a MN,
     at the boundaries moving too fast from one network to another even
     considering that fact that the lifetime of 'forwarding from previous
     CoA' is short, may experience this type of problem and this
     solution can simply avoid that problem.

> Extending this scenario seems messy, but one should remember, that most
> probably, the lifetime of "forwarding from a Previous Care-of Address"
> is short.

> Peter

Thanks,

Venkat
--
Venkata Jagana wrote:
>
> ...
>      Deregistering section, 9.4, applies to Home agent operation
>      and it describes about what HA should do when deregistration
>      (i.e. BU received) happens but what I am talking about is MN
>      operation, sec 10.20 (MN returning home) and not HA. This scenario
>      involves not just deregistration only but much more, sorry,
>      I haven't made that very clear in my last mail.
>
>      In a scenario, I have described here, MN should do the following
>      things at a minimum:
>           - deregister with home agent at 'B'
>           - Binding update to home agent at 'A' to refresh its
>             bcache entry with the CoA at 'B' now
>           - registration with foreign home agent at 'C' to start
>             tunnelling packets to CoA at 'B'
>
>      At any time, a MN may have a single original/real Home Agent
>      and single or multiple foreign Home Agents. At a given instance,
>      the number of foreign home agents a MN may have, will depend upon
>      how fast the MN is moving across the networks but it doesn't need to
>      keep track of all those foreign home agents except for the last one.
>      In a case where MN moves too quickly from one network to another,
>      then it would have established registrations with each of those
>      foreign home agents at the networks it visited earlier in order to
>      have the packets tunnelled to its current CoA from the previous
>      old CoA's.
>
>      Section 10.20 simply talks about MN returning home (its original
>      or real home) but it doesn't 'explicitly' talk about a MN moving
>      back to a old network it just visited earlier and what MN
>      should do (probably, I would consider this as a special case) and it
>      is not covered at all in this section unless it is interpreted that
>      it is left to the implementation, but I don't think that's a
>      good idea to leave it that way.

Thanks,
Venkat

----------------------------------------------------------------
Venkata R Jagana
IBM Linux Technology Centre, Beaverton
jagana@us.ibm.com
Tel: (503) 578 3430 T/L 775-3430






From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep 27 02:41:49 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA20809
	for <mobileip-archive@odin.ietf.org>; Thu, 27 Sep 2001 02:41:48 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id XAA04070;
	Wed, 26 Sep 2001 23:40:46 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id XAA01841;
	Wed, 26 Sep 2001 23:40:39 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8R6do7B004848
	for <mobile-ip-dist@sunroof.eng.sun.com>; Wed, 26 Sep 2001 23:39:50 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8R6doYM004847
	for mobile-ip-dist; Wed, 26 Sep 2001 23:39:50 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8R6dl7B004840
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 23:39:47 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id XAA26377
	for <mobile-ip@sunroof.eng.sun.com>; Wed, 26 Sep 2001 23:39:49 -0700 (PDT)
Received: from telesoft.indts.com ([164.164.71.52])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id AAA11079
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 00:40:41 -0600 (MDT)
Received: from indts_fs.indts.com (indts_fs [201.64.64.29])
	by telesoft.indts.com (8.8.7/8.8.7) with ESMTP id MAA17082
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 12:35:29 +0530
Received: by INDTS_FS with Internet Mail Service (5.5.2650.21)
	id <TCHS9AQL>; Thu, 27 Sep 2001 12:24:14 +0530
Message-ID: <F73B646FCC01D5118F530002B32C33724C6FE2@INDTS_FS>
From: Amit Shakya <amits@indts.com>
To: "'mobile-ip@sunroof.eng.sun.com'" <mobile-ip@sunroof.eng.sun.com>
Subject: [mobile-ip] DOUBT!!
Date: Thu, 27 Sep 2001 12:24:10 +0530
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

hi
I have a doubt regarding the implementation of FA. If a Router has only one
network interface and it advertises that as a care of address via Agent
Advertisement then it will start receiving both normal packets for routing
as well as packets to be decapsulated. Now my question is how will the
Router know whether the packet it is receiving has to be decapsulated and
then forwarded or forward directly ? Is my understanding of FA correct with
regards to this question or am i missing something?
Regards
Amit


From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep 27 03:57:20 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA23511
	for <mobileip-archive@lists.ietf.org>; Thu, 27 Sep 2001 03:57:19 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id AAA22974;
	Thu, 27 Sep 2001 00:56:25 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id AAA09364;
	Thu, 27 Sep 2001 00:56:11 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8R7tE7B005327
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 27 Sep 2001 00:55:14 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8R7tEjw005326
	for mobile-ip-dist; Thu, 27 Sep 2001 00:55:14 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from bebop.France.Sun.COM (bebop.France.Sun.COM [129.157.174.15])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8R7t47B005319
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 00:55:04 -0700 (PDT)
Received: from lillen (lillen [129.157.212.23])
	by bebop.France.Sun.COM (8.10.2+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id f8R7t1v21728;
	Thu, 27 Sep 2001 09:55:01 +0200 (MET DST)
Date: Thu, 27 Sep 2001 09:50:30 +0200 (CEST)
From: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Subject: Re: [mobile-ip] Concerns/comments for aaa-keys and gen-key
To: "Charles E. Perkins" <charliep@iprg.nokia.com>
Cc: Erik Nordmark <Erik.Nordmark@eng.sun.com>, mobile-ip@sunroof.eng.sun.com,
        Pat Calhoun <pcalhoun@diameter.org>
In-Reply-To: "Your message with ID" <3BB1F475.A0BF4DD1@iprg.nokia.com>
Message-ID: <Roam.SIMC.2.0.6.1001577030.19672.nordmark@bebop.france>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Charlie,

> > Do you view that a vendor that takes these extensions and build
> > a proprietary protocol should be able to say that their protocol
> > conforms to an RFC?
> 
> Here, I think you meant,  "a proprietary security protocol".
> If so, the answer is "yes".

No, I actually meant "protocol".

The question I'm trying to ask was the same as the one about vendor X and Y;
whether you think it is ok that two vendors can correctly implement
a given set of RFCs and conform to them, and there is no chance for them to
interoperate since they've chosen different optional subsets of the protocols.

And you didn't seem to answer that question (see below using TCP FIN/RST
as an example).

> Even so, I reckon it would be fine to mandate a particular security
> algorithm, but I didn't build the prototypes, and I don't know which
> algorithm people would choose for the default.  Is there something
> besides IKE that we can mandate here?  Otherwise, I would worry that
> placing the requirement would amount to an indefinite delay while
> someone creates a new default choice -- which would then itself have
> to undergo months of review and would probably be more complicated
> than the whole rest of the AAA-keys document, maybe by an order
> of magnitude.

I'm a bit lost - the comment was about security algorithms (like HMAC-MD5) -
what does IKE or any other key exchange/agreement protocol have to do
with this?

> However, I would emphasize the difference between building
> protocols, vs. building systems.  A system has many parts,
> and even using interoperable protocols can usually be built
> so that there isn't any interoperation.  To take a trivial
> example, two systems can implement IP and TCP and UDP and
> yet not interoperate because of mismatch at the application
> level.  I don't remember any requirement that TCP specify a
> guaranteed interoperable application running at a well-known port.
> IP itself doesn't require any interoperable transport protocol,
> and yet without such a thing, two systems cannot interoperate.
> Even so, we all think of IP as being a nice, small. interoperable
> network protocol.

But those systems that implement UDP, TCP, and IP can in fact,
provided they satisfy the MUST/MUST NOTs in the specs,
interoperate at those layers. Sure, they might not share any applications
which will effect the utility of the system for sure. But that isn't the
point - the point is whether a given RFC specifying a given protocol
is structured so that two implementations of that RFC can interoperate
using the specified protocol ignoring the systems level issues when making the
determination.

But the way I interpret your reluctance to mandating an algorithm for
aaa-keys seems similar in advocating the TCP RST and TCP FIN packets should be
optional resulting in one implementation only being capable of
sending RST (and not FIN) and another implementation only being capable
of processing FIN (and not RST). The way I interpret what you say is that
this would be a system level issue and it is perfectly fine to have a spec
that says MAY or the sending as well as receiving of FIN and RST.
Did I understand your point correctly?

Cheers, 
   Erik

 



From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep 27 04:00:51 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA23571
	for <mobileip-archive@lists.ietf.org>; Thu, 27 Sep 2001 04:00:50 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id CAA05764;
	Thu, 27 Sep 2001 02:00:09 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id BAA09776;
	Thu, 27 Sep 2001 01:00:12 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8R7xI7B005395
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 27 Sep 2001 00:59:18 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8R7xIK6005394
	for mobile-ip-dist; Thu, 27 Sep 2001 00:59:18 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from bebop.France.Sun.COM (bebop.France.Sun.COM [129.157.174.15])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8R7xE7B005387
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 00:59:14 -0700 (PDT)
Received: from lillen (lillen [129.157.212.23])
	by bebop.France.Sun.COM (8.10.2+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id f8R7xCv22294;
	Thu, 27 Sep 2001 09:59:12 +0200 (MET DST)
Date: Thu, 27 Sep 2001 09:54:41 +0200 (CEST)
From: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Subject: Re: [mobile-ip] Draft 15
To: "Charles E. Perkins" <charliep@iprg.nokia.com>
Cc: Erik Nordmark <Erik.Nordmark@eng.sun.com>, mobile-ip@sunroof.eng.sun.com
In-Reply-To: "Your message with ID" <3BB1FC21.517BA23D@iprg.nokia.com>
Message-ID: <Roam.SIMC.2.0.6.1001577281.16150.nordmark@bebop.france>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

> Does this come up for discussion within the IPv6 working group
> before IANA approves it?  If so, what do you think would be the
> consensus view of that working group?

There would at a minimum be an IETF wide last call
at which point anybody can voice their opinion.
I have no ability to guess what opions would be shared.

What is the real question?

  Erik



From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep 27 06:15:26 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA24777
	for <mobileip-archive@lists.ietf.org>; Thu, 27 Sep 2001 06:15:25 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id EAA13987;
	Thu, 27 Sep 2001 04:14:23 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id DAA22614;
	Thu, 27 Sep 2001 03:14:24 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8RADc7B006744
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 27 Sep 2001 03:13:38 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8RADc0u006743
	for mobile-ip-dist; Thu, 27 Sep 2001 03:13:38 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8RADY7B006736
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 03:13:34 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id DAA22437
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 03:13:35 -0700 (PDT)
Received: from mailer3.bham.ac.uk (mailer3.bham.ac.uk [147.188.128.54])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id DAA23982
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 03:13:34 -0700 (PDT)
Received: from bham.ac.uk ([147.188.128.127])
	by mailer3.bham.ac.uk with esmtp (Exim 3.16 #2)
	id 15mYAf-0006QQ-00
	for mobile-ip@sunroof.eng.sun.com; Thu, 27 Sep 2001 11:13:33 +0100
Received: from eee-fs7.bham.ac.uk ([147.188.145.131] helo=bham-eee-fs7.bham.ac.uk)
	by bham.ac.uk with esmtp (Exim 3.16 #3)
	id 15mYAy-0006nW-00
	for mobile-ip@sunroof.eng.sun.com; Thu, 27 Sep 2001 11:13:52 +0100
Received: by eee-fs7.bham.ac.uk with Internet Mail Service (5.5.2653.19)
	id <SLZCP2CN>; Thu, 27 Sep 2001 11:12:31 +0100
Message-ID: <B036F14C7A7FD511827000805FFEA8AD06F04F@eee-fs7.bham.ac.uk>
From: "Vanijprahba H." <vanijprh@eee-fs7.bham.ac.uk>
To: "'mobile-ip@sunroof.eng.sun.com'" <mobile-ip@sunroof.eng.sun.com>
Subject: RE: [mobile-ip] DOUBT!!
Date: Thu, 27 Sep 2001 11:12:28 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

hi Amit,

   I think the router checks the destination network prefix first.  If it is
for its own network then it will decapsulate.  If not, then it will just
forward the next router.  Please double check this as I am very new to this
as well.

Hugh

-----Original Message-----
From: Amit Shakya [mailto:amits@indts.com]
Sent: 27 September 2001 07:54
To: 'mobile-ip@sunroof.eng.sun.com'
Subject: [mobile-ip] DOUBT!!


hi
I have a doubt regarding the implementation of FA. If a Router has only one
network interface and it advertises that as a care of address via Agent
Advertisement then it will start receiving both normal packets for routing
as well as packets to be decapsulated. Now my question is how will the
Router know whether the packet it is receiving has to be decapsulated and
then forwarded or forward directly ? Is my understanding of FA correct with
regards to this question or am i missing something?
Regards
Amit


From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep 27 06:26:16 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA25000
	for <mobileip-archive@lists.ietf.org>; Thu, 27 Sep 2001 06:26:15 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id DAA07291;
	Thu, 27 Sep 2001 03:25:11 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id DAA23563;
	Thu, 27 Sep 2001 03:24:57 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8RANj7B006956
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 27 Sep 2001 03:23:45 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8RANiQH006955
	for mobile-ip-dist; Thu, 27 Sep 2001 03:23:44 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8RANf7B006948
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 03:23:41 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id DAA06821
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 03:23:42 -0700 (PDT)
Received: from laposte.enst-bretagne.fr (laposte.enst-bretagne.fr [192.108.115.3])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id DAA04825
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 03:23:36 -0700 (PDT)
Received: from rsm.rennes.enst-bretagne.fr (rsm.rennes.enst-bretagne.fr [192.44.77.1])
	by laposte.enst-bretagne.fr (8.11.6/8.11.6) with ESMTP id f8RANW905330;
	Thu, 27 Sep 2001 12:23:32 +0200
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr [193.52.74.194])
	by rsm.rennes.enst-bretagne.fr (8.8.8/8.8.8) with ESMTP id MAA15365;
	Thu, 27 Sep 2001 12:23:32 +0200 (MET DST)
Received: from givry.rennes.enst-bretagne.fr (localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.11.3/8.11.3) with ESMTP id f8RANVl32696;
	Thu, 27 Sep 2001 12:23:31 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200109271023.f8RANVl32696@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: mobile-ip@sunroof.eng.sun.com
cc: magma@innovationslab.net, ssm-interest@external.cisco.com
Subject: Re: [mobile-ip] Joining to SSM sources that are IPv6 mobile nodes 
In-reply-to: Your message of Wed, 26 Sep 2001 19:05:04 PDT.
             <2E33960095B58E40A4D3345AB9F65EC102DB7D6A@win-msg-01.wingroup.windeploy.ntdev.microsoft.com> 
Date: Thu, 27 Sep 2001 12:23:31 +0200
X-Virus-Scanned: by amavisd-milter (http://www.amavis.org/) at enst-bretagne.fr
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
 In your previous mail you wrote:

   The issue is how to continue getting data to receivers after a mobile
   node moves.
   Method (2) works fine for SSM, but has the obvious inefficiency.
   Method (1) does not work as is for SSM.
   
=> IMHO only the method 2 (i.e. to use a bidirectional tunnel between
the MN and the HA, and of course the home address as the source) is
reasonnable. But I wait for folks who have worked with (traditional)
multicast for mobile nodes.

Regards

Francis.Dupont@enst-bretagne.fr

PS: method 2 is not always inefficient, but this is always simple
(apply KISS principle? :-)


From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep 27 07:01:43 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA25771
	for <mobileip-archive@lists.ietf.org>; Thu, 27 Sep 2001 07:01:42 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id EAA17399;
	Thu, 27 Sep 2001 04:01:05 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id EAA11238;
	Thu, 27 Sep 2001 04:00:53 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8RAxj7B007463
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 27 Sep 2001 03:59:45 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8RAxiqa007462
	for mobile-ip-dist; Thu, 27 Sep 2001 03:59:44 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8RAxd7B007442
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 03:59:39 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id DAA26916
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 03:59:40 -0700 (PDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id DAA07510
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 03:59:39 -0700 (PDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA25562;
	Thu, 27 Sep 2001 06:59:36 -0400 (EDT)
Message-Id: <200109271059.GAA25562@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: mobile-ip@sunroof.eng.sun.com
From: Internet-Drafts@ietf.org
Subject: [mobile-ip] I-D ACTION:draft-ietf-mobileip-mipv6-scrty-reqts-00.txt
Date: Thu, 27 Sep 2001 06:59:36 -0400
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

--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		: Threat Models introduced by Mobile IPv6 and 
                          Requirements for Security in Mobile IPv6                     
	Author(s)	: P. Nikander et al.
	Filename	: draft-ietf-mobileip-mipv6-scrty-reqts-00.txt
	Pages		: 28
	Date		: 26-Sep-01
	
The IESG returned the MIP v6 draft to the working group due to
concerns about the security and scalability of binding updates (BUs)
sent to correspondent nodes and the associated IPSEC processing that
is specified in the draft. Since that time discussions have continued
to attempt to define what is really needed to make binding updates
secure while taking into consideration the aspect of scalability as
well as the fact that IPSec may not be the most suitable security
mechanism for securing BUs between MNs and CNs.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mobileip-mipv6-scrty-reqts-00.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-mipv6-scrty-reqts-00.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-mipv6-scrty-reqts-00.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:	<20010926120544.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-mobileip-mipv6-scrty-reqts-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-mobileip-mipv6-scrty-reqts-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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

--OtherAccess--

--NextPart--




From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep 27 07:03:00 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA25806
	for <mobileip-archive@lists.ietf.org>; Thu, 27 Sep 2001 07:03:00 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id EAA17404;
	Thu, 27 Sep 2001 04:01:05 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id EAA11241;
	Thu, 27 Sep 2001 04:00:54 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8RB007B007473
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 27 Sep 2001 04:00:00 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8RB005c007472
	for mobile-ip-dist; Thu, 27 Sep 2001 04:00:00 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8RAxt7B007465
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 03:59:55 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id DAA26406
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 03:59:56 -0700 (PDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id FAA03525
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 05:00:54 -0600 (MDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA25595;
	Thu, 27 Sep 2001 06:59:52 -0400 (EDT)
Message-Id: <200109271059.GAA25595@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
CC: mobile-ip@sunroof.eng.sun.com
From: Internet-Drafts@ietf.org
Subject: [mobile-ip] I-D ACTION:draft-mccann-mobileip-ipv6mipv4-01.txt
Date: Thu, 27 Sep 2001 06:59:51 -0400
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.


	Title		: IPv6 over Mobile IPv4
	Author(s)	: E. Gustafsson, P. Engelstad, T. Hiller, P. McCann
	Filename	: draft-mccann-mobileip-ipv6mipv4-01.txt
	Pages		: 10
	Date		: 26-Sep-01
	
This document specifies a Mobile IPv4 extension that may be used by
dual stack mobile nodes to obtain IPv6 service with the use of a
Mobile IPv4 registration. This extension allows for immediate
deployment of IPv6 on dual stack mobile devices, without the need
for a full IPv6 infrastructure. It is believed that providing IPv6
services to mobile devices in the short term will spur the growth of
IPv6 networks.
This extension makes use of the existing Mobile IPv4 security model,
including the interface to the AAA infrastructure, but does not
provide the route optimization capabilities included in the Mobile
IPv6 protocol. Further, this specification requires that the mobile
node and mobility agents have dual IPv4 and IPv6 stacks.

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

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-mccann-mobileip-ipv6mipv4-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-mccann-mobileip-ipv6mipv4-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:	<20010926120603.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-mccann-mobileip-ipv6mipv4-01.txt

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

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

--OtherAccess--

--NextPart--




From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep 27 08:49:02 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA28980
	for <mobileip-archive@odin.ietf.org>; Thu, 27 Sep 2001 08:49:02 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id GAA02669;
	Thu, 27 Sep 2001 06:47:42 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id FAA29289;
	Thu, 27 Sep 2001 05:47:41 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8RCkj7B009477
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 27 Sep 2001 05:46:45 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8RCkjgp009476
	for mobile-ip-dist; Thu, 27 Sep 2001 05:46:45 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from bebop.France.Sun.COM (bebop.France.Sun.COM [129.157.174.15])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8RCkf7B009469
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 05:46:41 -0700 (PDT)
Received: from lillen (lillen [129.157.212.23])
	by bebop.France.Sun.COM (8.10.2+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id f8RCkdv22045;
	Thu, 27 Sep 2001 14:46:39 +0200 (MET DST)
Date: Thu, 27 Sep 2001 14:42:07 +0200 (CEST)
From: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Subject: Re: [mobile-ip] Draft 15
To: mat@cisco.com
Cc: mobile-ip@sunroof.eng.sun.com, charliep@iprg.nokia.com,
        "Hesham Soliman (ERA)" <Hesham.Soliman@era.ericsson.se>
In-Reply-To: "Your message with ID" <15280.60358.24767.908578@thomasm-u1.cisco.com>
Message-ID: <Roam.SIMC.2.0.6.1001594527.24786.nordmark@bebop.france>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Michael Thomas wrote:
>    If you have access to the outbound IPsec processing,
>    this should be fairly straightforward, I'd think:
>    you check to see if BU packet would cause an ESP
>    or AH header to be added, and if not then you use
>    the weaker variety. I believe that this also addresses
>    the authorization issue since you could set up different
>    security policy database entries which reflect the
>    different policies you might want to apply to BU's
>    vs. other data (if any).

That approach solves the problem when there already is
an IPsec SA established, which is an important case (it handles
MN-HA communication secured by IPsec).

But what about the general case?
MN has a certificate from the (private) foo CA, and a given CN also
has a certificate from the same CA. In this case they could use
IKE to establish an IPsec CA and use that for the BU (as well as potentially
other packets).

I think I've already seen your answer to the above question - that it
is controlled by the IPsec policy.
This would mean that for machines that are in the same (private) key
infrastructure they would need to have policy entries, e.g. based on
IP address prefixes, to indicate when they would kick IKE to create
a SA.
I was hoping that there be a less management intensive manner to make
this happen.

  Erik



From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep 27 09:51:58 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA00751
	for <mobileip-archive@lists.ietf.org>; Thu, 27 Sep 2001 09:51:57 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id GAA13791;
	Thu, 27 Sep 2001 06:51:14 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id GAA29613;
	Thu, 27 Sep 2001 06:51:01 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8RDne7B010902
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 27 Sep 2001 06:49:40 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8RDne77010901
	for mobile-ip-dist; Thu, 27 Sep 2001 06:49:40 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from bebop.France.Sun.COM (bebop.France.Sun.COM [129.157.174.15])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8RDnZ7B010894
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 06:49:36 -0700 (PDT)
Received: from lillen (lillen [129.157.212.23])
	by bebop.France.Sun.COM (8.10.2+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id f8RDnXv00231;
	Thu, 27 Sep 2001 15:49:33 +0200 (MET DST)
Date: Thu, 27 Sep 2001 15:45:01 +0200 (CEST)
From: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Subject: Re: [mobile-ip] Draft 15 
To: Francis.Dupont@enst-bretagne.fr
Cc: mobile-ip@sunroof.eng.sun.com
In-Reply-To: "Your message with ID" <200109260833.f8Q8Xjl27046@givry.rennes.enst-bretagne.fr>
Message-ID: <Roam.SIMC.2.0.6.1001598301.15805.nordmark@bebop.france>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

>  Of course this will work for IPsec but not with piggybacking so
> we have to solve the piggybacking issue first. I propose to relaunch
> the multiple payload by packet idea because it is generalization
> of piggybacking, so if piggybacking is good this will be even better.
> Last draft seems to be draft-kre-ipv6-payload-01.txt. A side effect
> of this proposal is to remove the piggybacking issue from the
> discussion.

It would make sense to check with kre whether he is interested in
pursuing the draft or handing it over to somebody else - at least it
can serve as a starting point.

For instance, it isn't clear whether we need/want the generality of
N payloads per packet or if 2 is sufficient.
The security considerations need work even though kre had work when he
wrote the draft. For instance, understanding the impact on firewalls
that would like to inspect the packets for port numbers.

  Erik



From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep 27 10:06:28 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01160
	for <mobileip-archive@lists.ietf.org>; Thu, 27 Sep 2001 10:06:28 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id HAA19843;
	Thu, 27 Sep 2001 07:05:33 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id HAA01525;
	Thu, 27 Sep 2001 07:05:16 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8RE3M7B011085
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 27 Sep 2001 07:03:22 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8RE3MTv011083
	for mobile-ip-dist; Thu, 27 Sep 2001 07:03:22 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8RE3H7B011067
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 07:03:17 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id HAA16805
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 07:03:18 -0700 (PDT)
Received: from motgate3.mot.com (motgate3.mot.com [144.189.100.103])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA00109
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 08:04:11 -0600 (MDT)
Received: [from pobox.mot.com (pobox.mot.com [129.188.137.100]) by motgate3.mot.com (motgate3 2.1) with ESMTP id GAA04121 for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 06:54:51 -0700 (MST)]
Received: [from m-il06-r4.mot.com (m-il06-r4.mot.com [129.188.137.196]) by pobox.mot.com (MOT-pobox 2.0) with ESMTP id HAA01989 for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 07:03:12 -0700 (MST)]
Received: from thorgal.crm.mot.com by m-il06-r4.mot.com with ESMTP; Thu, 27 Sep 2001 09:03:12 -0500
Received: from test9.crm.mot.com.crm.mot.com (test9.crm.mot.com [140.101.173.239])
	by thorgal.crm.mot.com (Postfix) with ESMTP
	id 548612ED24; Thu, 27 Sep 2001 15:59:56 +0200 (CEST)
To: "Faccin Stefano (NRC/Dallas)" <stefano.faccin@nokia.com>
Cc: <mobile-ip@sunroof.eng.sun.com>
Subject: Re: [mobile-ip] Concerns/comments for aaa-keys and gen-key
References: <82ECD4351A4A9547957C606034A3CB8D0B0212@daebe005.NOE.Nokia.com>
From: Alexandru Petrescu <petrescu@crm.mot.com>
Date: 27 Sep 2001 16:03:09 +0200
In-Reply-To: <82ECD4351A4A9547957C606034A3CB8D0B0212@daebe005.NOE.Nokia.com>
Message-Id: <m3ofnw689u.fsf@test9.crm.mot.com>
Lines: 31
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.0.103
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Stefano, thank you for your reply.  

"Faccin Stefano (NRC/Dallas)" <stefano.faccin@nokia.com> writes:
> However, the concept of "security gateway" can be used, where entity
> in the foreign/home domain share a local SAf/SAh with security
> gateways, and security gateways belonging to visited and home domain
> share another SA (e.g. established as result of roaming agreements
> or through other mechanisms).

Where can I find more about this "security gateway" concept?  Is it a
recent IETF IPsec thing?  Or does it stem from the earlier firewall
research originated by Steve Bellovin?

So all security gateways of all domains have SA's among them.  You
mention "roaming agreements".  You previously mentioned SLA's.  You
reduce the AAAF-AAAH trust problem to SecGate-SecGate trust problem.
I suppose the problem is still there.

> In such way, AAAF can send messages protecting them with SAf, the
> security gateways transmits it to the home domain using SA, and the
> gateway in the home network uses SAh to protect the message to
> AAAH. In this way scalability can be achieved, as already
> demonstrated in other large scale commercial networks using similar
> concepts.

For my better understanding: examples of those successful comercial
networks, please?  Were they using IETF protocols?

Thank you,

Alex



From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep 27 10:13:10 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01333
	for <mobileip-archive@odin.ietf.org>; Thu, 27 Sep 2001 10:13:09 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id HAA23007;
	Thu, 27 Sep 2001 07:12:34 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id HAA02626;
	Thu, 27 Sep 2001 07:12:17 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8REBX7B011334
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 27 Sep 2001 07:11:33 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8REBXbr011333
	for mobile-ip-dist; Thu, 27 Sep 2001 07:11:33 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8REBU7B011326
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 07:11:30 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id HAA20809;
	Thu, 27 Sep 2001 07:11:30 -0700 (PDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id HAA10746;
	Thu, 27 Sep 2001 07:11:30 -0700 (PDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id HAA15952;
	Thu, 27 Sep 2001 07:11:30 -0700 (PDT)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f8REBTZ07628;
	Thu, 27 Sep 2001 07:11:29 -0700
X-mProtect:  Thu, 27 Sep 2001 07:11:29 -0700 Nokia Silicon Valley Messaging Protection
Received: from Icharliep-1.iprg.nokia.com (205.226.22.18, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpdtcUeCX; Thu, 27 Sep 2001 07:11:27 PDT
Message-ID: <3BB33378.7F97B410@iprg.nokia.com>
Date: Thu, 27 Sep 2001 07:11:04 -0700
From: Charlie Perkins <charliep@iprg.nokia.com>
Organization: Nokia
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Erik Nordmark <Erik.Nordmark@eng.sun.com>
CC: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Draft 15
References: <Roam.SIMC.2.0.6.1001577281.16150.nordmark@bebop.france>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hello Erik,

That was my question, thanks for answering!

There's a lot of sentiment favoring getting a new
number for Binding Update, and your answer seems
to indicate that it would be unlikely to present much
of a problem.  That means we ought to do that as
part of draft ...-15.

Regards,
Charlie P.

Erik Nordmark wrote:

> > Does this come up for discussion within the IPv6 working group
> > before IANA approves it?  If so, what do you think would be the
> > consensus view of that working group?
>
> There would at a minimum be an IETF wide last call
> at which point anybody can voice their opinion.
> I have no ability to guess what opions would be shared.
>
> What is the real question?
>
>   Erik



From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep 27 10:15:52 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01415
	for <mobileip-archive@odin.ietf.org>; Thu, 27 Sep 2001 10:15:51 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id HAA24109;
	Thu, 27 Sep 2001 07:14:57 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id HAA03127;
	Thu, 27 Sep 2001 07:14:20 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8REDY7B011381
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 27 Sep 2001 07:13:34 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8REDYWg011380
	for mobile-ip-dist; Thu, 27 Sep 2001 07:13:34 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8REDU7B011373
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 07:13:30 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id HAA02887;
	Thu, 27 Sep 2001 07:13:30 -0700 (PDT)
Received: from mailgw.ipunplugged.com (217.134.88.213.host.tele1europe.se [213.88.134.217])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id HAA23671;
	Thu, 27 Sep 2001 07:13:28 -0700 (PDT)
Received: from fredrikj (hotel-14.local.ipunplugged.com [192.168.8.14])
	by mailgw.ipunplugged.com (8.9.3/8.9.3) with SMTP id QAA11477;
	Thu, 27 Sep 2001 16:13:57 +0200
From: "Fredrik Johansson" <fredrik.johansson@ipunplugged.com>
To: "Erik Nordmark" <Erik.Nordmark@eng.sun.com>
Cc: <mobile-ip@sunroof.eng.sun.com>,
        "Charlie Perkins" <charliep@IPRG.nokia.com>,
        "Pat Calhoun" <pcalhoun@diameter.org>
Subject: RE: [mobile-ip] Concerns/comments for aaa-keys and gen-key
Date: Thu, 27 Sep 2001 16:14:28 +0200
Message-ID: <MJEMJBGGCLLDLFFAHLJKKEJGDGAA.fredrik.johansson@ipunplugged.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
In-Reply-To: <Roam.SIMC.2.0.6.1001495690.1688.nordmark@bebop.france>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

>
>> As Charlie points out, the specification of message flows are in
>> draft-ietf-diameter-mobileip-07.txt. The gen-key and aaa-key drafts
>> merely specify the format of the specific message.
>
>Thanks for the pointer - I hope this sheads some light.
>[Seems like having this pointer in the mobileip drafts would be asking
>to much. I should have read all of draft-ietf-mobileip* and
>draft-ietf-aaa-*
>before asking :-)]

:-),

>
>A quick look leads me to believe that aaa-key is still very underspecified
>when it comes to how the MN extensions are sent and processed in the MN
>packets - diameter-mobileip talks about how/when the diameter messages
>are sent and how they are processed on receipt, but nothing about what
>the MN does.
>
>> The assumption is that a AAA server (let it be AAAh or AAAf) have a high
>> degree of mutual trust with the HA. And that AAA servers of different
>> domains have a mutual trust (Service Level Agreement). If the HA
>is located
>> in a foreign network, the AAAh will distribute the keys to the AAAf which
>> will distribute them to the allocated HA in the foreign network.
>
>I understand they need the appropriate level of trust in order implement
>the AAA functionality. But my concern stems from the fact that the AAA
>infrastructure is viewed as a way to distribute keying material to
>be shared
>between MN and HA and that this keying material seems to be intended to
>be used for more than protecting the AAA exchanges.

yes, the key material is intended to protect the MIP signaling, having the
keys/key-material distributed via AAA is just a way to create a more
scalable
solution. The use of the distributed keys is exactly the same as in regular
MIP where the keys are pre-configured.

>So while the MN/HA trusts the AAA infrastructure for those functions
>it doesn't follow that they should be trusted with arbitrary
>keying material.
>
>> >> Without knowing the applicability it is not possible to determine what
>> >> needs to be supported in terms of algorithms and key sizes, as
>> >> well as the constraints on how to negotiate what algorithm
>and key length
>> >> to use for a given SA.
>> >
>>
>> It's up to the policy of the AAAh to determine the necessary level of the
>> keys to distribute.
>
>I do think we need an applicability to understand e.g. whether only 64 bits
>of randomness is sufficient, what is required in terms of re-keying, etc.
>
>> The keys have a given lifetime, it's also specified in the mobile ip
>> and diameter drafts how to distribute new keys when the keys expire.
>
>Which mobileip draft?

draft-ietf-aaa-diameter-mobileip-08.txt (when it becomes available, -07 is
not
updated to reflect the changes to use key material in aaa-key). The AAAh
sets
an Authorization lifetime for the session it authorizes and the same is used
on the keys that are distributed.
The HA will set the registration lifetime so that the authorization lifetime
is a multiple of the registration lifetime. This way the mobile node will
not
update the keys at every periodic tunnel update, but only once in a while.
The mobile node can request new keys when the authorization lifetime is
about
to expire, or the FA can determine to send the registratio request via the
AAA and request that new keys be distributed, i.e. both the network and the
mobilen node can determine when to re-create keys.

>It seems like the MN might need to be able to determine when a key
>is about to expire and initiate a re-key, but aaa-keys is utterly silent
>on anything about re-keying.

ok, there might be some more explanations needed in aaa-key. However,
the thought is that it is not only up to the mn to determine when new
keys are to be created, it can also be up to the network to distribute
new keys when appropriate. But I agree that this need to be explained.

>
>> Since the mobile node and AAAh is in the same administrative
>domain it can
>> be
>> any algorithm that is supported by both nodes. However, HMAC-MD5 is
>> mandatory to
>> support in rfc2002-bis and in Diameter so there's one algorithm
>that always
>> will be supported.
>
>So it seems like aaa-keys should list this one as MUST implement.

I've no problem with this. why not take HMAC-MD5 since it's already
mandatory in rfc2002-bis

>
>> The keys for the mobile node is distributed via key material so there is
>> really no need for confidentiality, the keys distributed to the FA and HA
>> is carried in the AAA protocol which requires either TLS or IPsec.
>
>I'm told that inventing a new key exchange/agreement protocol is
>non-trivial.
>What the drafts are describing sure looks like a new protocol in this
>area.
>If this is the case I expect there to somehow be a critical mass of
>experts in this area that will review this protocol, because
>I don't think its in our collective interest to create another WEP
>debacle.

It's not like the different nodes are negotiating what keys to use, the
different MIP entities gets the keys to use via AAA. The keys destined
for the HA and FA are transported in Diameter which have end-to-end
security, and the keys to the MN is not realy a key but key material,
thus no one can re-create the key unless they know the shared secret
between the mn and the AAAh. So there is not such a big difference from
someone manually configuring the different nodes with keys sent via snail
mail
or agreed on over some other media.

But I might be over simplifying the problem here.

/Fredrik

>
>Alternative, if there are existing proven mechanisms to distribute keys
>that fit into this it would seem to be prudent to reuse that.
>(The diameter-e2e-sec draft is proposing to reuse CMS for diameter for
>instance.)
>
>   Erik
>



From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep 27 10:22:05 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01545
	for <mobileip-archive@odin.ietf.org>; Thu, 27 Sep 2001 10:22:04 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id IAA09867;
	Thu, 27 Sep 2001 08:21:11 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id HAA04124;
	Thu, 27 Sep 2001 07:21:05 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8REJr7B011789
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 27 Sep 2001 07:19:53 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8REJqOG011788
	for mobile-ip-dist; Thu, 27 Sep 2001 07:19:52 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from bebop.France.Sun.COM (bebop.France.Sun.COM [129.157.174.15])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8REJk7B011767
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 07:19:47 -0700 (PDT)
Received: from lillen (lillen [129.157.212.23])
	by bebop.France.Sun.COM (8.10.2+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id f8REJfv04883;
	Thu, 27 Sep 2001 16:19:41 +0200 (MET DST)
Date: Thu, 27 Sep 2001 16:15:10 +0200 (CEST)
From: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Subject: RE: [mobile-ip] Concerns/comments for aaa-keys and gen-key
To: Fredrik Johansson <fredrik.johansson@ipunplugged.com>
Cc: Erik Nordmark <Erik.Nordmark@eng.sun.com>, mobile-ip@sunroof.eng.sun.com,
        Charlie Perkins <charliep@IPRG.nokia.com>,
        Pat Calhoun <pcalhoun@diameter.org>
In-Reply-To: "Your message with ID" <MJEMJBGGCLLDLFFAHLJKKEJGDGAA.fredrik.johansson@ipunplugged.com>
Message-ID: <Roam.SIMC.2.0.6.1001600110.20729.nordmark@bebop.france>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

> It's not like the different nodes are negotiating what keys to use, the
> different MIP entities gets the keys to use via AAA. The keys destined
> for the HA and FA are transported in Diameter which have end-to-end
> security, and the keys to the MN is not realy a key but key material,
> thus no one can re-create the key unless they know the shared secret
> between the mn and the AAAh. So there is not such a big difference from
> someone manually configuring the different nodes with keys sent via snail
> mail
> or agreed on over some other media.

It is the assertion that key material being different than keys
that makes the alarm bells start ringing - I think such an assertion needs
to be analysed by folks that are subject matter experts in the protocols
and algorithms used to carry the material as well as constructing
keys from the material.

This approach is quite different that the proposed 
draft-ietf-aaa-diameter-e2e-sec which re-uses an existing mechanism
(CMS) and relies on certificates (by distributing the certificate chains
itself). At least that doesn't seem to invent new stuff that makes my alarm
bells go off.

  Erik



From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep 27 10:47:37 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02831
	for <mobileip-archive@odin.ietf.org>; Thu, 27 Sep 2001 10:47:36 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id HAA08698;
	Thu, 27 Sep 2001 07:46:53 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id HAA23383;
	Thu, 27 Sep 2001 07:46:46 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8REjj7B012262
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 27 Sep 2001 07:45:45 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8REjjXE012261
	for mobile-ip-dist; Thu, 27 Sep 2001 07:45:45 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8REjf7B012247
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 07:45:41 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id HAA23135;
	Thu, 27 Sep 2001 07:45:42 -0700 (PDT)
Received: from laposte.enst-bretagne.fr (laposte.enst-bretagne.fr [192.108.115.3])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id HAA09613;
	Thu, 27 Sep 2001 07:45:41 -0700 (PDT)
Received: from rsm.rennes.enst-bretagne.fr (rsm.rennes.enst-bretagne.fr [192.44.77.1])
	by laposte.enst-bretagne.fr (8.11.6/8.11.6) with ESMTP id f8REjc908194;
	Thu, 27 Sep 2001 16:45:38 +0200
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr [193.52.74.194])
	by rsm.rennes.enst-bretagne.fr (8.8.8/8.8.8) with ESMTP id QAA20243;
	Thu, 27 Sep 2001 16:45:38 +0200 (MET DST)
Received: from givry.rennes.enst-bretagne.fr (localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.11.3/8.11.3) with ESMTP id f8REjcl33856;
	Thu, 27 Sep 2001 16:45:38 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200109271445.f8REjcl33856@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Erik Nordmark <Erik.Nordmark@eng.sun.com>
cc: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Draft 15 
In-reply-to: Your message of Thu, 27 Sep 2001 15:45:01 +0200.
             <Roam.SIMC.2.0.6.1001598301.15805.nordmark@bebop.france> 
Date: Thu, 27 Sep 2001 16:45:38 +0200
X-Virus-Scanned: by amavisd-milter (http://www.amavis.org/) at enst-bretagne.fr
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
 In your previous mail you wrote:

   >  Of course this will work for IPsec but not with piggybacking so
   > we have to solve the piggybacking issue first. I propose to relaunch
   > the multiple payload by packet idea because it is generalization
   > of piggybacking, so if piggybacking is good this will be even better.
   > Last draft seems to be draft-kre-ipv6-payload-01.txt. A side effect
   > of this proposal is to remove the piggybacking issue from the
   > discussion.
   
   It would make sense to check with kre whether he is interested in
   pursuing the draft or handing it over to somebody else - at least it
   can serve as a starting point.
   
=> My intention was to use it as a starting point. I can't see
someting else to do with a draft which expired many years ago.

   For instance, it isn't clear whether we need/want the generality of
   N payloads per packet or if 2 is sufficient.

=> with recursion and no-next-header both are equivalent
(so 2 is sufficient and simpler).

   The security considerations need work even though kre had work when he
   wrote the draft. For instance, understanding the impact on firewalls
   that would like to inspect the packets for port numbers.
   
=> I expect the main problem will be the same than for piggybacking
(ambiguity for IPsec selectors, path MTU discovery, ROHC compressor
confusion, etc). But I agree that the possibility to have two (or more)
transport headers will open new perspectives...

Regards

Francis.Dupont@enst-bretagne.fr

PS: the draft should be available soon on some servers.
   


From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep 27 10:53:31 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02995
	for <mobileip-archive@odin.ietf.org>; Thu, 27 Sep 2001 10:53:30 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id HAA11325;
	Thu, 27 Sep 2001 07:52:42 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id HAA24663;
	Thu, 27 Sep 2001 07:52:35 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8REpw7B012734
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 27 Sep 2001 07:51:58 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8REpwiM012733
	for mobile-ip-dist; Thu, 27 Sep 2001 07:51:58 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8REpr7B012726
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 07:51:53 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id HAA11496
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 07:51:54 -0700 (PDT)
Received: from muminmamman.lifix.fi ([195.238.204.197])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id IAA05427
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 08:51:42 -0600 (MDT)
Received: from ban by muminmamman.lifix.fi with local (Exim 3.12 #1 (Debian))
	id 15mcUP-0007gE-00
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 17:50:13 +0300
Date: Thu, 27 Sep 2001 17:50:13 +0300
From: Bjorn Andersson <bjorn@lifix.fi>
To: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] DOUBT!!
Message-ID: <20010927175013.B22182@lifix.fi>
Mail-Followup-To: Bjorn Andersson <bjorn@lifix.fi>,
	mobile-ip@sunroof.eng.sun.com
References: <F73B646FCC01D5118F530002B32C33724C6FE2@INDTS_FS>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <F73B646FCC01D5118F530002B32C33724C6FE2@INDTS_FS>
User-Agent: Mutt/1.3.20i
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

On Thu, Sep 27 2001, at 12:24:10 +0530, Amit Shakya wrote:
> I have a doubt regarding the implementation of FA. If a Router has only one
> network interface and it advertises that as a care of address via Agent
> Advertisement then it will start receiving both normal packets for routing
> as well as packets to be decapsulated. Now my question is how will the
> Router know whether the packet it is receiving has to be decapsulated and
> then forwarded or forward directly ? Is my understanding of FA correct with
> regards to this question or am i missing something?

If the FA sets the Code field in the advertisement to 16, then
the agent does not route common traffic. See the "Agent
Advertisement section" in the specs:

ICMP Fields

   Code     The Code field of the agent advertisement is
            interpreted as follows:

             0 The mobility agent handles common traffic -- that
               is, it acts as a router for IP datagrams not
               necessarily related to mobile nodes.
            16 The mobility agent does not route common traffic.
               However, all foreign agents MUST (minimally)
               forward to a default router any datagrams received
               from a registered mobile node (Section 4.2.2).


Hope that answers your question.

Regards,
Bjorn


-- 
Bjorn Andersson <bjorn@lifix.fi>                       +358 50 341 2556
Lifix Systems Oy <http://www.lifix.fi/>                 PGP id 5AFC144B
Yliopistonkatu 5, 3rd floor; FIN-00100 Helsinki


From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep 27 11:18:52 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03496
	for <mobileip-archive@odin.ietf.org>; Thu, 27 Sep 2001 11:18:52 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA25569;
	Thu, 27 Sep 2001 08:17:55 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id IAA00016;
	Thu, 27 Sep 2001 08:17:36 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8RFGh7B013247
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 27 Sep 2001 08:16:43 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8RFGhhE013246
	for mobile-ip-dist; Thu, 27 Sep 2001 08:16:43 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8RFGd7B013239
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 08:16:39 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id IAA29818
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 08:16:41 -0700 (PDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id IAA18586
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 08:16:40 -0700 (PDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id IAA20042;
	Thu, 27 Sep 2001 08:16:39 -0700 (PDT)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f8RFGdH25787;
	Thu, 27 Sep 2001 08:16:39 -0700
X-mProtect:  Thu, 27 Sep 2001 08:16:39 -0700 Nokia Silicon Valley Messaging Protection
Received: from charliep.iprg.nokia.com (205.226.2.89, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpdPisUds; Thu, 27 Sep 2001 08:16:38 PDT
Message-ID: <3BB342D6.E268637E@iprg.nokia.com>
Date: Thu, 27 Sep 2001 08:16:38 -0700
From: "Charles E. Perkins" <charliep@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Francis Dupont <Francis.Dupont@inria.fr>
CC: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Draft 15
References: <200109271445.f8REjcl33856@givry.rennes.enst-bretagne.fr>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hello Francis,

While I agree that both the multi-payload scheme and inserting
Binding Updates into packets with data payloads share the
advantages of reducing the number of packets sent, I think
the similarities stop there.

In particular, it is likely that the multi-payload scheme
would require buffering and delay for previous data packets,
inserting Binding Updates into packets with data payloads
involves checking for recent movement at the time one consults
the route table.  This is quite a bit easier to implement,
and involves no delay.  The receiving end is also quite a
bit easier.

Thus, I think that for the purposes of the present discussion
there should not be any linkage between these two features.

Having said that, however, I do agree that it would be good
idea to enable the delivery of multiple payloads in a single
IPv6 packet, for those applications that can stand the delay.
For major applications of interest to our own research group
here at Nokia, over the next years, I think this delay would
not be tolerable.

Regards,
Charlie P.




Francis Dupont wrote:
> 
>    >  Of course this will work for IPsec but not with piggybacking so
>    > we have to solve the piggybacking issue first. I propose to relaunch
>    > the multiple payload by packet idea because it is generalization
>    > of piggybacking, so if piggybacking is good this will be even better.
>    > Last draft seems to be draft-kre-ipv6-payload-01.txt. A side effect
>    > of this proposal is to remove the piggybacking issue from the
>    > discussion.
> 
>    It would make sense to check with kre whether he is interested in
>    pursuing the draft or handing it over to somebody else - at least it
>    can serve as a starting point.
> 
> => My intention was to use it as a starting point. I can't see
> someting else to do with a draft which expired many years ago.
> 
>    For instance, it isn't clear whether we need/want the generality of
>    N payloads per packet or if 2 is sufficient.
> 
> => with recursion and no-next-header both are equivalent
> (so 2 is sufficient and simpler).
> 
>    The security considerations need work even though kre had work when he
>    wrote the draft. For instance, understanding the impact on firewalls
>    that would like to inspect the packets for port numbers.
> 
> => I expect the main problem will be the same than for piggybacking
> (ambiguity for IPsec selectors, path MTU discovery, ROHC compressor
> confusion, etc). But I agree that the possibility to have two (or more)
> transport headers will open new perspectives...
> 
> Regards
> 
> Francis.Dupont@enst-bretagne.fr
> 
> PS: the draft should be available soon on some servers.
>


From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep 27 12:09:19 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA05088
	for <mobileip-archive@odin.ietf.org>; Thu, 27 Sep 2001 12:09:18 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id KAA15238;
	Thu, 27 Sep 2001 10:08:18 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA14083;
	Thu, 27 Sep 2001 09:08:14 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8RG7N7B015205
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 27 Sep 2001 09:07:23 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8RG7Noh015204
	for mobile-ip-dist; Thu, 27 Sep 2001 09:07:23 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8RG7J7B015197
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 09:07:19 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA04343;
	Thu, 27 Sep 2001 09:07:21 -0700 (PDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id JAA26810;
	Thu, 27 Sep 2001 09:07:21 -0700 (PDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id JAA22475;
	Thu, 27 Sep 2001 09:06:50 -0700 (PDT)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f8RG6om28685;
	Thu, 27 Sep 2001 09:06:50 -0700
X-mProtect:  Thu, 27 Sep 2001 09:06:50 -0700 Nokia Silicon Valley Messaging Protection
Received: from charliep.iprg.nokia.com (205.226.2.89, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpdO5NXwg; Thu, 27 Sep 2001 09:06:48 PDT
Message-ID: <3BB34E99.DFDF4C69@iprg.nokia.com>
Date: Thu, 27 Sep 2001 09:06:49 -0700
From: "Charles E. Perkins" <charliep@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Erik Nordmark <Erik.Nordmark@eng.sun.com>
CC: mobile-ip@sunroof.eng.sun.com, Pat Calhoun <pcalhoun@diameter.org>
Subject: Re: [mobile-ip] Concerns/comments for aaa-keys and gen-key
References: <Roam.SIMC.2.0.6.1001577030.19672.nordmark@bebop.france>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hello Erik,

Comments inline...

Erik Nordmark wrote:

             ..........

> The question I'm trying to ask was the same as the one about vendor X and Y;
> whether you think it is ok that two vendors can correctly implement
> a given set of RFCs and conform to them, and there is no chance for them to
> interoperate since they've chosen different optional subsets of the protocols.

From your note below, it seems that we don't have any major difference
of opinion about what needs to be done here.  But even so, I would like
to clarify that the example in my previous note did not involve selection
of different optional subsets from the aaa-keys extensions.  In the case
I described, it was more like whether or not AAAH and mobile node share
a compatible security association from which they can produce derived keys.

> And you didn't seem to answer that question (see below using TCP FIN/RST
> as an example).

Well, I thought I did.  I think that if two vendors implement the same
aaa-keys protocol, and the nodes are configured with compatible security
associations for this purpose, then interoperability would result.
Since these are Mobile IP extensions, it is already guaranteed that the
mobile node is going to implement a well-known message digestification
algorithm -- in RFC2002bis, HMAC-MD5.  Thus, while I'm happy to put whatever
is needed into the document (e.g., explicitly mandate use of HMAC_MD5 as
the algorithm which is used to derive the key), I also believe that this
process of key derivation is quite a bit different than the kind of
message flow involved in your TCP FIN/RST example.


>> Even so, I reckon it would be fine to mandate a particular security
>> algorithm, but I didn't build the prototypes, and I don't know which
>> algorithm people would choose for the default.  Is there something
>> besides IKE that we can mandate here?  Otherwise, I would worry that
>> placing the requirement would amount to an indefinite delay while
>> someone creates a new default choice -- which would then itself have
>> to undergo months of review and would probably be more complicated
>> than the whole rest of the AAA-keys document, maybe by an order
>> of magnitude.
> 
> I'm a bit lost - the comment was about security algorithms (like HMAC-MD5) -
> what does IKE or any other key exchange/agreement protocol have to do
> with this?

Now that I see that your comment was about security algorithms like HMAC-MD5,
I can see why my paragraph would be completely irrelevant to your concern.
On the other hand, I think that IKE does qualify as a security algorithm,
so that the terminology can get confusing, which just indicates a strong
need for providing as much context as possible during our discussions.
Furthermore, your comment came after some discussion in my paragraph that
concerned key distribution protocols.  In other words, we seem to have
been talking pretty much right past each other on this point, since
I didn't realize at the outset you were focusing on the choice of
digistification/encoding algorithm.

           ........  points already covered   ...........
 
> But the way I interpret your reluctance to mandating an algorithm for
> aaa-keys seems similar in advocating the TCP RST and TCP FIN packets should be
> optional resulting in one implementation only being capable of
> sending RST (and not FIN) and another implementation only being capable
> of processing FIN (and not RST). The way I interpret what you say is that
> this would be a system level issue and it is perfectly fine to have a spec
> that says MAY or the sending as well as receiving of FIN and RST.
> Did I understand your point correctly?

In the first place, I am not reluctant to mandate an algorithm -- in fact,
my role is to put in there what others tell me to put in there, since I
was not present at the interoperability tests.  Even more abstractly, as
you have clarified your request, I have no problem at all with putting
in a mandate for, say, HMAC-MD5.  So, for example, I could rewrite
section 4 to use HMAC-MD5, delete references to MD5 in prefix+suffix
mode, and state that the algorithm in section was mandatory to implement,
and that other algorithms MAY be used.  Would that resolve this issue?

To clarify my point further, I would not agree with the interpretation
you suggest FIN and RST.  These are messages that are sent and received,
and they are supposed to initiate actions according to the presumed
state of the communications partner.

The aaa-keys draft does not specify such distinct message components,
but rather containers for material to be managed according to the
security association shared by the parties.

Unfortunately, I have to defer further discussion of these drafts to
the people who are actually doing the work.  I hope that with this
message our positions can be seen as very close, and that someone will
supply the necessary text for me whenever it is agreed about whether
HMAC-MD5 will be mandated.  I'll try to be very responsive in producing
the next draft.


Regards,
Charlie P.


From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep 27 12:28:53 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA05757
	for <mobileip-archive@odin.ietf.org>; Thu, 27 Sep 2001 12:28:51 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id KAA04289;
	Thu, 27 Sep 2001 10:28:03 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA18902;
	Thu, 27 Sep 2001 09:28:07 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8RGRC7B015802
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 27 Sep 2001 09:27:12 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8RGRChe015801
	for mobile-ip-dist; Thu, 27 Sep 2001 09:27:12 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from bebop.France.Sun.COM (bebop.France.Sun.COM [129.157.174.15])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8RGR87B015794
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 09:27:08 -0700 (PDT)
Received: from lillen (lillen [129.157.212.23])
	by bebop.France.Sun.COM (8.10.2+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id f8RGR4v22971;
	Thu, 27 Sep 2001 18:27:04 +0200 (MET DST)
Date: Thu, 27 Sep 2001 18:22:33 +0200 (CEST)
From: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Subject: Re: [mobile-ip] Concerns/comments for aaa-keys and gen-key
To: "Charles E. Perkins" <charliep@iprg.nokia.com>
Cc: Erik Nordmark <Erik.Nordmark@eng.sun.com>, mobile-ip@sunroof.eng.sun.com,
        Pat Calhoun <pcalhoun@diameter.org>
In-Reply-To: "Your message with ID" <3BB34E99.DFDF4C69@iprg.nokia.com>
Message-ID: <Roam.SIMC.2.0.6.1001607753.16697.nordmark@bebop.france>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

> From your note below, it seems that we don't have any major difference
> of opinion about what needs to be done here. 

Great.

> But even so, I would like
> to clarify that the example in my previous note did not involve selection
> of different optional subsets from the aaa-keys extensions.  In the case
> I described, it was more like whether or not AAAH and mobile node share
> a compatible security association from which they can produce derived keys.

You're saying "security association" - but I think this is about
the "algorithm", right?

I do think it is similar in the sense that if e.g HMAC-MD5 and HMAC-SHA1
are the defined algorithms and both are optional you can end
up with a case where one vendor implements only HMAC-MD5 and another vendor
implements only HMAC-SHA1 then no matter how hard the customer tries those
boxes can't interoperate using the specified protocol.

> > And you didn't seem to answer that question (see below using TCP FIN/RST
> > as an example).
> 
> Well, I thought I did.  I think that if two vendors implement the same
> aaa-keys protocol, and the nodes are configured with compatible security
> associations for this purpose, then interoperability would result.
> Since these are Mobile IP extensions, it is already guaranteed that the
> mobile node is going to implement a well-known message digestification
> algorithm -- in RFC2002bis, HMAC-MD5.  Thus, while I'm happy to put whatever
> is needed into the document (e.g., explicitly mandate use of HMAC_MD5 as
> the algorithm which is used to derive the key), I also believe that this
> process of key derivation is quite a bit different than the kind of
> message flow involved in your TCP FIN/RST example.

Requiring one algorithm as MUST be implemented would be the first step.
Assuming HMAC-MD5 provides adequate security I don't see a problem mandating
that one.

But if there are other (current and future) algorithms that are used
it seems like there needs to be a way for the communicating parties to
determine which algorithm to use.
For instance, if 5 years from now HMAC-MD5 is not considered to be secure
enough, when both parties implement the NEW-BETTER-ALG they should be able
to discover that and use it instead of HMAC-MD5.

In MIPv4 HA-MN authentication this is determined when the relationship
between those two boxes is configured (i.e. at "subscription" time).
Do you envision the same here?
Doesn't the AAA server also need to support the same algorithm or do
they "merely" provide a secure communication channel between the HA and MN?

Hmm - perhaps the confusion between the terms "algorithm" and "security 
association" stems from the fact that here (as well as in RFC 2002)
the security associations between MN and HA are pre-configured
i.e. there is no notion of a master key and re-keying creating different
SAs over time. (IKE with pre-shared secrets ends up creating a new SA
when re-keying so that while the new SA is put in place the old SA can
be used for packets in transit.)

I wonder if anybody has been thinking about periodic re-keying in
the RFC 2002 context - it sure seems usefulin general.
I need to read what the AAA docs say about re-keyeing.

> Now that I see that your comment was about security algorithms like HMAC-MD5,
> I can see why my paragraph would be completely irrelevant to your concern.
> On the other hand, I think that IKE does qualify as a security algorithm, so
> that the terminology can get confusing, which just indicates a strong need
> for providing as much context as possible during our discussions.
> Furthermore, your comment came after some discussion in my paragraph that
> concerned key distribution protocols.  In other words, we seem to have been
> talking pretty much right past each other on this point, since I didn't
> realize at the outset you were focusing on the choice of
> digistification/encoding algorithm.

Yep - we've had some terminology problems.
I think adding some definitions to aaa-keys would help here (I think Thomas
was asking for this as well).

   Erik



From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep 27 12:43:56 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA06373
	for <mobileip-archive@odin.ietf.org>; Thu, 27 Sep 2001 12:43:56 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id KAA19488;
	Thu, 27 Sep 2001 10:42:46 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA23066;
	Thu, 27 Sep 2001 09:42:50 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8RGg07B016407
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 27 Sep 2001 09:42:00 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8RGfxW0016406
	for mobile-ip-dist; Thu, 27 Sep 2001 09:41:59 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8RGfu7B016399
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 09:41:56 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA19944
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 09:41:58 -0700 (PDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id JAA10202
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 09:41:57 -0700 (PDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id JAA25209
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 09:41:55 -0700 (PDT)
X-Delivered-For: <mobile-ip@sunroof.eng.sun.com>
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f8RGfts25568
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 09:41:55 -0700
X-mProtect:  Thu, 27 Sep 2001 09:41:55 -0700 Nokia Silicon Valley Messaging Protection
Received: from vijayd.iprg.nokia.com (205.226.2.94, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpdqc5V3c; Thu, 27 Sep 2001 09:41:53 PDT
Message-ID: <3BB356D0.DECDA55@iprg.nokia.com>
Date: Thu, 27 Sep 2001 09:41:52 -0700
From: Vijay Devarapalli <vijayd@iprg.nokia.com>
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Draft 15
References: <200109271445.f8REjcl33856@givry.rennes.enst-bretagne.fr>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Francis Dupont wrote:
> 

> Francis.Dupont@enst-bretagne.fr
> 
> PS: the draft should be available soon on some servers.
> 

heres the URL

http://people.nokia.net/~vijayd/draft-kre-ipv6-payload-01.txt

vijay


From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep 27 12:51:52 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA06664
	for <mobileip-archive@odin.ietf.org>; Thu, 27 Sep 2001 12:51:52 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id KAA26678;
	Thu, 27 Sep 2001 10:51:02 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA25027;
	Thu, 27 Sep 2001 09:51:04 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8RGo97B016865
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 27 Sep 2001 09:50:09 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8RGo9JG016864
	for mobile-ip-dist; Thu, 27 Sep 2001 09:50:09 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8RGo47B016847
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 09:50:04 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA24780
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 09:50:07 -0700 (PDT)
Received: from laposte.enst-bretagne.fr (laposte.enst-bretagne.fr [192.108.115.3])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA14055
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 10:51:03 -0600 (MDT)
Received: from rsm.rennes.enst-bretagne.fr (rsm.rennes.enst-bretagne.fr [192.44.77.1])
	by laposte.enst-bretagne.fr (8.11.6/8.11.6) with ESMTP id f8RGnu931559;
	Thu, 27 Sep 2001 18:49:56 +0200
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr [193.52.74.194])
	by rsm.rennes.enst-bretagne.fr (8.8.8/8.8.8) with ESMTP id SAA22327;
	Thu, 27 Sep 2001 18:49:56 +0200 (MET DST)
Received: from givry.rennes.enst-bretagne.fr (localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.11.3/8.11.3) with ESMTP id f8RGnul34381;
	Thu, 27 Sep 2001 18:49:56 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200109271649.f8RGnul34381@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: "Charles E. Perkins" <charliep@iprg.nokia.com>
cc: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Draft 15 
In-reply-to: Your message of Thu, 27 Sep 2001 08:16:38 PDT.
             <3BB342D6.E268637E@iprg.nokia.com> 
Date: Thu, 27 Sep 2001 18:49:56 +0200
X-Virus-Scanned: by amavisd-milter (http://www.amavis.org/) at enst-bretagne.fr
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
 In your previous mail you wrote:

   In particular, it is likely that the multi-payload scheme
   would require buffering and delay for previous data packets,

=> this is not true if collapsed packets are taken from the
sending queue (*). I believe a similar mechanism (super-framing?)
is done on very fast links where media acquisition is expensive.

   inserting Binding Updates into packets with data payloads
   involves checking for recent movement at the time one consults
   the route table.  This is quite a bit easier to implement,
   and involves no delay.  The receiving end is also quite a
   bit easier.
   
=> I agree but your argument is only for not smart enough
implementations of multi-payload (not of BU piggybacking).

   Thus, I think that for the purposes of the present discussion
   there should not be any linkage between these two features.
   
=> is your opinion based mainly on the delay argument?

Thanks

Francis.Dupont@enst-bretagne.fr

PS: the counter-argument is by Laurent Toutain (I suggested
that to wait to get enough payloads before to send a large
packet is not the best idea of the year).


From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep 27 13:33:21 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08178
	for <mobileip-archive@odin.ietf.org>; Thu, 27 Sep 2001 13:33:21 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id LAA03816;
	Thu, 27 Sep 2001 11:32:33 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id KAA06999;
	Thu, 27 Sep 2001 10:32:34 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8RHVh7B018390
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 27 Sep 2001 10:31:43 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8RHVg2M018389
	for mobile-ip-dist; Thu, 27 Sep 2001 10:31:42 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8RHVd7B018382
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 10:31:39 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id KAA06740
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 10:31:42 -0700 (PDT)
Received: from sj-msg-core-2.cisco.com (sj-msg-core-2.cisco.com [171.69.24.11])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA09108
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 11:32:38 -0600 (MDT)
Received: from mira-sjc5-7.cisco.com (mira-sjc5-7.cisco.com [171.71.163.27])
	by sj-msg-core-2.cisco.com (8.11.3/8.9.1) with ESMTP id f8RHVev11097;
	Thu, 27 Sep 2001 10:31:40 -0700 (PDT)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-7.cisco.com (Mirapoint)
	with ESMTP id AAP21383;
	Thu, 27 Sep 2001 10:31:20 -0700 (PDT)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id KAA01890; Thu, 27 Sep 2001 10:31:19 -0700 (PDT)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15283.25191.704021.172583@thomasm-u1.cisco.com>
Date: Thu, 27 Sep 2001 10:31:19 -0700 (PDT)
To: mobile-ip@sunroof.eng.sun.com
Cc: mat@cisco.com, charliep@iprg.nokia.com,
        "Hesham Soliman (ERA)" <Hesham.Soliman@era.ericsson.se>
Subject: Re: [mobile-ip] Draft 15
In-Reply-To: <Roam.SIMC.2.0.6.1001594527.24786.nordmark@bebop.france>
References: <15280.60358.24767.908578@thomasm-u1.cisco.com>
	<Roam.SIMC.2.0.6.1001594527.24786.nordmark@bebop.france>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Erik Nordmark writes:
 > That approach solves the problem when there already is
 > an IPsec SA established, which is an important case (it handles
 > MN-HA communication secured by IPsec).
 > 
 > But what about the general case?
 > MN has a certificate from the (private) foo CA, and a given CN also
 > has a certificate from the same CA. In this case they could use
 > IKE to establish an IPsec CA and use that for the BU (as well as potentially
 > other packets).
 > 
 > I think I've already seen your answer to the above question - that it
 > is controlled by the IPsec policy.

   Correct.

 > This would mean that for machines that are in the same (private) key
 > infrastructure they would need to have policy entries, e.g. based on
 > IP address prefixes, to indicate when they would kick IKE to create
 > a SA.
 > I was hoping that there be a less management intensive manner to make
 > this happen.

   This is a general IPsec issue. If you have some better
   ideas about how to automagically install IPsec 
   policy, I'm sure lots of folks would be interested :-)

	   Mike


From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep 27 13:44:34 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08964
	for <mobileip-archive@odin.ietf.org>; Thu, 27 Sep 2001 13:44:34 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA19174;
	Thu, 27 Sep 2001 10:43:57 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id KAA10326;
	Thu, 27 Sep 2001 10:43:26 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8RHgX7B019057
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 27 Sep 2001 10:42:33 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8RHgXTG019056
	for mobile-ip-dist; Thu, 27 Sep 2001 10:42:33 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from eastmail1.East.Sun.COM (eastmail1.East.Sun.COM [129.148.1.240])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8RHgV7B019049
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 10:42:31 -0700 (PDT)
Received: from onion.east.sun.com (onion.East.Sun.COM [129.148.174.110])
	by eastmail1.East.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id NAA04103
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 13:42:31 -0400 (EDT)
Received: (from glass@localhost)
	by onion.east.sun.com (8.9.3+Sun/8.9.3) id NAA06546
	for mobile-ip@sunroof.eng.sun.com; Thu, 27 Sep 2001 13:43:02 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8R7Tx7B005154
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 00:29:59 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id AAA22102
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 00:30:00 -0700 (PDT)
Received: from mailserv.intranet.gr (mailserv.intranet.GR [146.124.14.106])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id BAA24487
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 01:11:44 -0600 (MDT)
Received: from patreas.patra.intranet.gr (patreas.intranet.GR [146.124.171.10])
	by mailserv.intranet.gr (8.11.3/8.11.1) with ESMTP id f8R78gm21082;
	Thu, 27 Sep 2001 10:08:42 +0300 (EET DST)
Received: from patdpd19.intranet.gr (patdpd19 [146.124.171.45])
	by patreas.patra.intranet.gr (8.9.3+Sun/8.9.0) with SMTP id KAA07827;
	Thu, 27 Sep 2001 10:27:52 +0300 (EET DST)
Content-Type: text/plain;
  charset="iso-8859-1"
From: Dionisios Gatzounas <dgat@intracom.gr>
Organization: INTRACOM S.A.
To: Amit Shakya <amits@indts.com>
Subject: Re: [mobile-ip] DOUBT!!
Date: Thu, 27 Sep 2001 10:08:19 +0000
X-Mailer: KMail [version 1.2]
References: <F73B646FCC01D5118F530002B32C33724C6FE2@INDTS_FS>
In-Reply-To: <F73B646FCC01D5118F530002B32C33724C6FE2@INDTS_FS>
Cc: mobile-ip@sunroof.eng.sun.com
MIME-Version: 1.0
Message-Id: <01092710081900.00760@patdpd19.intranet.gr>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by sunroof.eng.sun.com id f8R7U07B005155
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 8bit

Hello Amit,

On Thursday 27 September 2001 06:54, you wrote:
> hi
> I have a doubt regarding the implementation of FA. If a Router has only one
> network interface and it advertises that as a care of address via Agent
> Advertisement then it will start receiving both normal packets for routing
> as well as packets to be decapsulated. Now my question is how will the
> Router know whether the packet it is receiving has to be decapsulated and
> then forwarded or forward directly ? Is my understanding of FA correct with
> regards to this question or am i missing something?
> Regards
> Amit


source ---> encapsulator --------> decapsulator ---> destination
The Router (decapsulator) will check the Protocol Type field in the IP 
header. If this is 4 (IP in IP encapsulation) then the Router will 
decapsulate the packet and forward it to the destination.
Is this the problem or you meant something else?

Regards,
Dionisios.
-- 
------------------------------------------
Dionisios D. Gatzounas           	          
Development Programmes Department 	     
INTRACOM S.A.                       	          
254 Panepistimiou Str., Patras 26443, GREECE              	          
tel: +30 61 465168
fax: +30 61 465070
e-mail: dgat@intracom.gr
------------------------------------------


From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep 27 13:46:39 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09055
	for <mobileip-archive@odin.ietf.org>; Thu, 27 Sep 2001 13:46:39 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id LAA16550;
	Thu, 27 Sep 2001 11:45:57 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id KAA11315;
	Thu, 27 Sep 2001 10:45:59 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8RHjG7B019130
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 27 Sep 2001 10:45:16 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8RHjGCS019128
	for mobile-ip-dist; Thu, 27 Sep 2001 10:45:16 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from eastmail1.East.Sun.COM (eastmail1.East.Sun.COM [129.148.1.240])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8RHjD7B019119
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 10:45:14 -0700 (PDT)
Received: from onion.east.sun.com (onion.East.Sun.COM [129.148.174.110])
	by eastmail1.East.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id NAA05504
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 13:45:13 -0400 (EDT)
Received: (from glass@localhost)
	by onion.east.sun.com (8.9.3+Sun/8.9.3) id NAA06602
	for mobile-ip@sunroof.eng.sun.com; Thu, 27 Sep 2001 13:45:44 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8RDQt7B010332
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 06:26:55 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id GAA11749
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 06:26:57 -0700 (PDT)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id GAA02219
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 06:26:56 -0700 (PDT)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (8.11.0/8.11.0) with ESMTP id f8RDQOp24595
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 09:26:24 -0400 (EDT)
Received: from zcard00m.ca.nortel.com by zcars04f.ca.nortel.com;
          Thu, 27 Sep 2001 09:26:25 -0400
Received: from zbl6c000.corpeast.baynetworks.com ([132.245.205.50]) 
          by zcard00m.ca.nortel.com 
          with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) 
          id TK5W4P1W; Thu, 27 Sep 2001 09:26:20 -0400
Received: from americasm06.nt.com (deathvalley.us.nortel.com [47.141.98.23]) 
          by zbl6c000.corpeast.baynetworks.com 
          with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) 
          id RS87S1QF; Thu, 27 Sep 2001 09:26:19 -0400
Message-ID: <3BB32904.B2B0926D@americasm06.nt.com>
Date: Thu, 27 Sep 2001 09:26:28 -0400
X-Sybari-Space: 00000000 00000000 00000000
From: "Brian Haberman" <haberman@nortelnetworks.com>
X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Dave Thaler <dthaler@windows.microsoft.com>
CC: mobile-ip <mobile-ip@sunroof.eng.sun.com>,
        magma <magma@innovationslab.net>,
        ssm-interest <ssm-interest@external.cisco.com>
Subject: [mobile-ip] Re: Joining to SSM sources that are IPv6 mobile nodes
References: <2E33960095B58E40A4D3345AB9F65EC102DB7D6A@win-msg-01.wingroup.windeploy.ntdev.microsoft.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Orig: <haberman@americasm06.nt.com>
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Dave,
     I prefer method 2.  Trying to get BUs to all group members
in order to make SSM work seems overly complicated.  Let the
group members think the MN is always at home sourcing the
multicast data.

Brian

Dave Thaler wrote:
> 
> Sorry for the cross-post, but this issue really does concern
> interactions between drafts in three different WGs:
> MobileIP: draft-ietf-mobileip-ipv6-14.txt, section 10.19
> MAGMA: draft-vida-mld-v2-01.txt
> SSM: draft-ietf-ssm-overview-01.txt
> (Please trim the recipients when responding, if appropriate.)
> 
> Starting from the Mobile IPv6 spec:
> > A mobile node that wishes to send packets to a multicast group
> > also has two options:  (1) send directly on the foreign link being
> > visited; or (2) send via a tunnel to its home agent.  Because
> > multicast routing in general depends upon the Source Address used in
> > the IPv6 header of the multicast packet, a mobile node that tunnels a
> > multicast packet to its home agent MUST use its home address as the
> > IPv6 Source Address of the inner multicast packet.
> 
> The issue is how to continue getting data to receivers after a mobile
> node moves.
> Method (2) works fine for SSM, but has the obvious inefficiency.
> Method (1) does not work as is for SSM.
> 
> I'll assume the sender has advertised (HA,G) in whatever method (e.g. a
> web page) he uses to announce the session, just like the session would
> advertise HA in any method used to get unicast clients to connect to
> him.  (The sender could just as well use (COA,G) but the same issues
> arise if it subsequently moves, from my understanding.)
> 
> In the SSM model, when receivers join (HA,G) via MLDv2, join state is
> constructed along the path to HA (i.e. hitting the home agent).  Any
> data sent directly on the foreign link being visited will go nowhere,
> since there is no join state there.
> 
> A bad answer would be "do nothing, we don't care if sourcing SSM is
> broken".
> 
> A simple answer would be "an SSM source MUST use option (2), i.e.
> tunnel packets to the home agent".  In this case, either option (1)
> would never be used for any multicast traffic, or else the host would
> have to know whether a receiver might want to use an include-mode list
> with MLDv2 and tunnel to the home agent if so.  Personally, I don't
> like this answer, but if this is what the consensus turns out to be,
> then it should be documented in the Mobile IPv6 spec (no effect on the
> SSM or MAGMA WGs), and apis to inform the mobile node stack that it
> MUST tunnel to the home agent may be required.
> 
> Another answer, which would require adding rules to both the Mobile
> IPv6 and MLDv2 specs (and probably mentioning it in the SSM overview
> doc), would be to make method (1) work for SSM sources.  A potential
> solution here is twofold:
> 
> 1) If an MLDv2 host is sending an include-mode report for a source X,
> and a binding cache entry exists for X with a care-of-address COA, then
> put both X and COA in the membership report.  (This means that if you
> can somehow get a Binding Update to all the group members, then they'll
> be able to receive packets sourced from COA, since routers will
> construct join state back to the foreign link.)  It needs to join to
> both addresses so that if the node moves again, it won't be stuck
> waiting for data from the old COA.
> 
> 2) A mobile node sourcing traffic when away from home needs to get a
> Binding Update to all the group members.  I believe this can be done by
> tunneling a packet via the home agent (and hence must have a source
> address of its home address) which contains a Binding Update with
> an Alternate Care-of Address of its current COA.  This would need to be
> done periodically, so that new receivers get it.
> 
> Comments?  Am I missing anything?
> 
> -Dave Thaler


From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep 27 14:29:42 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10360
	for <mobileip-archive@odin.ietf.org>; Thu, 27 Sep 2001 14:29:42 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA14029;
	Thu, 27 Sep 2001 11:29:05 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id LAA12278;
	Thu, 27 Sep 2001 11:28:51 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8RIRl7B020606
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 27 Sep 2001 11:27:47 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8RIRlJB020605
	for mobile-ip-dist; Thu, 27 Sep 2001 11:27:47 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8RIRh7B020598
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 11:27:43 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id LAA11986
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 11:27:44 -0700 (PDT)
Received: from fep01-app.kolumbus.fi (fep01-0.kolumbus.fi [193.229.0.41])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id LAA27803
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 11:27:43 -0700 (PDT)
Received: from jariws1 ([62.248.238.242]) by fep01-app.kolumbus.fi
          (InterMail vM.5.01.03.08 201-253-122-118-108-20010628) with SMTP
          id <20010927182742.UKD11276.fep01-app.kolumbus.fi@jariws1>;
          Thu, 27 Sep 2001 21:27:42 +0300
Message-ID: <011001c14782$1a216000$8a1b6e0a@arenanet.fi>
From: "Jari Arkko" <jari.arkko@kolumbus.fi>
To: <charliep@iprg.nokia.com>
Cc: <mobile-ip@sunroof.eng.sun.com>
References: <200109271445.f8REjcl33856@givry.rennes.enst-bretagne.fr> <3BB342D6.E268637E@iprg.nokia.com>
Subject: [mobile-ip] Re: multi-payload schemes
Date: Thu, 27 Sep 2001 21:27:44 +0300
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hi Charlie,

> In particular, it is likely that the multi-payload scheme
> would require buffering and delay for previous data packets,
> inserting Binding Updates into packets with data payloads
> involves checking for recent movement at the time one consults
> the route table.  This is quite a bit easier to implement,
> and involves no delay.  The receiving end is also quite a
> bit easier.

I suppose the above depends on how the 'merge' operation
is viewed. If it is seen as a general purpose packet merger
looking at outgoing packets, then it would need to see two
packets before doing a merge, implying buffer. However, this
may not be necessary. You might also implement the receiver
side in a general manner, but have a specific trigger on the
sending side when to do a merge. For instance, when your
implementation now would construct a piggybacked BU, it
appears that it should be able to construct a merged packet
in the similar manner and without a delay. 

However, one concern I have with the general solution is
that I'm not quite sure how it would be deployed in a world
where not all (obviously!) nodes support this. How would an
MN know the receiver supports this? Through a trial-and-ICMP?
Or try once and if you get an ack, then use towards that host
also in the future?

Jari





From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep 27 14:31:11 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10431
	for <mobileip-archive@odin.ietf.org>; Thu, 27 Sep 2001 14:31:10 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA14724;
	Thu, 27 Sep 2001 11:30:18 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id LAA12632;
	Thu, 27 Sep 2001 11:29:50 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8RISg7B020623
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 27 Sep 2001 11:28:42 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8RISfkW020622
	for mobile-ip-dist; Thu, 27 Sep 2001 11:28:41 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from eastmail1.East.Sun.COM (eastmail1.East.Sun.COM [129.148.1.240])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8RISc7B020615
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 11:28:39 -0700 (PDT)
Received: from onion.east.sun.com (onion.East.Sun.COM [129.148.174.110])
	by eastmail1.East.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id OAA24744
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 14:28:39 -0400 (EDT)
Received: (from glass@localhost)
	by onion.east.sun.com (8.9.3+Sun/8.9.3) id OAA09256
	for mobile-ip@sunroof.eng.sun.com; Thu, 27 Sep 2001 14:29:10 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8RGml7B016658
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 09:48:47 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA21697
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 09:48:49 -0700 (PDT)
Received: from isis.lip6.fr (isis.lip6.fr [132.227.60.2])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id KAA24493
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 10:48:33 -0600 (MDT)
Received: from tibre.lip6.fr (tibre.lip6.fr [132.227.74.2])
          by isis.lip6.fr (8.12.0.Beta19/jtpda-5.3.2+victor) with ESMTP id f8RG8MeZ000709
          ; Thu, 27 Sep 2001 18:08:23 +0200
X-pt: isis.lip6.fr
Received: from lip6.fr (otos.lip6.fr [132.227.61.47])
	by tibre.lip6.fr (8.11.3/8.11.3) with ESMTP id f8RG8AW29331;
	Thu, 27 Sep 2001 18:08:10 +0200 (CEST)
Message-ID: <3BB34EF5.14CD184F@lip6.fr>
Date: Thu, 27 Sep 2001 18:08:21 +0200
From: Rolland Vida <Rolland.Vida@lip6.fr>
Organization: Laboratoire Lip6
X-Mailer: Mozilla 4.75 [fr] (WinNT; U)
X-Accept-Language: fr
MIME-Version: 1.0
To: Dave Thaler <dthaler@windows.microsoft.com>
CC: mobile-ip@sunroof.eng.sun.com, magma@innovationslab.net,
        ssm-interest@external.cisco.com
Subject: [mobile-ip] Re: [Magma] Joining to SSM sources that are IPv6 mobile nodes
References: <2E33960095B58E40A4D3345AB9F65EC102DB7D6A@win-msg-01.wingroup.windeploy.ntdev.microsoft.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Dave et al.,

Solution 2 is obviously the simplest one. However, solution 1 might prove
to be not as bad as it looks like. Brian said "Let the
group members think the MN is always at home sourcing the multicast data."
In fact, you could use your proposed solution 1 without the receivers being
aware of the MN's address change. The MN should advertise its new CoA to
the edge routers, and not to the receivers. Edge routers then will send a
PIM-SSM join message to the CoA, and a second SSM tree is built. This will
be done transparently for the receivers.
There's of course the problem that even if data will arrive on the new CoA
SSM tree, receivers will drop the packets as the source address is not OK
for them. A possible solution for that is to do NAT in the edge routers,
and change back the source address to the home address, before forwarding
the data to their receivers. I agree however that this solution is a lot
more complicated than a simple tunneling.

> Either option (1) would never be used for any multicast traffic, or else
> the host would
> have to know whether a receiver might want to use an include-mode list
> with MLDv2 and tunnel to the home agent if so.

You can make the difference between an SSM and an SM connection by the
group's address. There's a specific SSM address range, and it is supposed
that you do not do PIM-SM  in the SSM range.

More generally, I think that the problem has a lot in common with the
problem of reliability in an SSM environment. Imagine that you have an SSM
source, and a potential repair server somewhere downstream. If data gets
lost, only the source can send repair data. If you want to use the repair
server, you should probably create a second SSM tree, rooted at the repair
server. In addition, repair servers could move, or in fact could be
activated or deactivated in certain conditions. There are some papers on
this issue by people from UMASS. The point is that you will have to
constantly join and leave different SSM repair trees, like the different
CoA trees. Somehow similar, isn't it?

Ok, I'm a bit far from the strating point. But it's an interesting issue I
think

Regards,
Rolland Vida.





From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep 27 14:31:14 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10443
	for <mobileip-archive@odin.ietf.org>; Thu, 27 Sep 2001 14:31:13 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA14708;
	Thu, 27 Sep 2001 11:30:17 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id LAA12730;
	Thu, 27 Sep 2001 11:29:56 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8RISn7B020633
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 27 Sep 2001 11:28:49 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8RISm28020632
	for mobile-ip-dist; Thu, 27 Sep 2001 11:28:48 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from eastmail1.East.Sun.COM (eastmail1.East.Sun.COM [129.148.1.240])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8RISj7B020625
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 11:28:46 -0700 (PDT)
Received: from onion.east.sun.com (onion.East.Sun.COM [129.148.174.110])
	by eastmail1.East.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id OAA24819
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 14:28:46 -0400 (EDT)
Received: (from glass@localhost)
	by onion.east.sun.com (8.9.3+Sun/8.9.3) id OAA09260
	for mobile-ip@sunroof.eng.sun.com; Thu, 27 Sep 2001 14:29:17 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8RGuV7B017098
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 09:56:31 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA16892
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 09:56:33 -0700 (PDT)
Received: from mx.webfountain.com (mx.digitalfountain.com [209.219.233.39])
	by patan.sun.com (8.9.3+Sun/8.9.3) with SMTP id KAA01716
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 10:56:21 -0600 (MDT)
Received: (qmail 31646 invoked from network); 27 Sep 2001 16:56:30 -0000
Received: from mail.intranet (10.1.1.37)
  by mx.digitalfountain.com with SMTP; 27 Sep 2001 16:56:30 -0000
Received: from mikedell (pptp-10-1-129-55.intranet [10.1.129.55])
	by mail.intranet (8.9.3/8.9.3) with SMTP id JAA06909;
	Thu, 27 Sep 2001 09:56:04 -0700
X-Authentication-Warning: mail.intranet: Host pptp-10-1-129-55.intranet [10.1.129.55] claimed to be mikedell
From: "Michael Luby" <luby@digitalfountain.com>
To: "Dave Thaler" <dthaler@windows.microsoft.com>
Cc: <mobile-ip@sunroof.eng.sun.com>, <ssm-interest@external.cisco.com>,
        <magma@innovationslab.net>
Subject: [mobile-ip] RE: Joining to SSM sources that are IPv6 mobile nodes
Date: Thu, 27 Sep 2001 09:56:25 -0700
Message-ID: <NEBBIAPCNKEDCLPNFBNCOEGOCHAA.luby@digitalfountain.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Importance: Normal
In-Reply-To: <2E33960095B58E40A4D3345AB9F65EC102DB7D6A@win-msg-01.wingroup.windeploy.ntdev.microsoft.com>
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Dave,

I think that neither of these options is necessarily the right answer all
the time, as this seems to me to be more of an application service issue
rather than a networking service issue.

For example, an application could implement the solution to 1 that you
propose below at the application level in pretty much the same manner
(without additional explicit network support).  The idea would be for the
roaming source to always send its current address to its permanent home
address (at the application level), and then the home server would always
send out the current address of the source through an application level SSM
announcement channel.  In this solution, the roaming source would send its
data multicast packets using its local source address.

As another example, at the application level, solution 2 could also be used,
where the roaming source always tunnels its multicast packets back to its
permanent home address, and then these are sent out using SSM from the home
address.

There are other ways of doing this as well, but I believe that they should
be done at the application level specific to each application, and not at
the network services level.  I like the philosophy of building a simple but
robust common denominator network service (like SSM), rather than trying to
build too much of the complexity into this level (like MSDP) that could be
done more efficiently and simply at the application level (because one
doesn't have to provide a general implementation at the application level,
only a much simpler implementation particular to the application).  The
problem with doing this at the network level is that it will either be too
general (and thus hard to implement and scale) or else too restrictive.

Mike

-----Original Message-----
From: Dave Thaler [mailto:dthaler@windows.microsoft.com]
Sent: Wednesday, September 26, 2001 7:05 PM
To: mobile-ip@sunroof.eng.sun.com; magma@innovationslab.net;
ssm-interest@external.cisco.com
Subject: Joining to SSM sources that are IPv6 mobile nodes


Sorry for the cross-post, but this issue really does concern
interactions between drafts in three different WGs:
MobileIP: draft-ietf-mobileip-ipv6-14.txt, section 10.19
MAGMA: draft-vida-mld-v2-01.txt
SSM: draft-ietf-ssm-overview-01.txt
(Please trim the recipients when responding, if appropriate.)

Starting from the Mobile IPv6 spec:
> A mobile node that wishes to send packets to a multicast group
> also has two options:  (1) send directly on the foreign link being
> visited; or (2) send via a tunnel to its home agent.  Because
> multicast routing in general depends upon the Source Address used in
> the IPv6 header of the multicast packet, a mobile node that tunnels a
> multicast packet to its home agent MUST use its home address as the
> IPv6 Source Address of the inner multicast packet.

The issue is how to continue getting data to receivers after a mobile
node moves.
Method (2) works fine for SSM, but has the obvious inefficiency.
Method (1) does not work as is for SSM.

I'll assume the sender has advertised (HA,G) in whatever method (e.g. a
web page) he uses to announce the session, just like the session would
advertise HA in any method used to get unicast clients to connect to
him.  (The sender could just as well use (COA,G) but the same issues
arise if it subsequently moves, from my understanding.)

In the SSM model, when receivers join (HA,G) via MLDv2, join state is
constructed along the path to HA (i.e. hitting the home agent).  Any
data sent directly on the foreign link being visited will go nowhere,
since there is no join state there.

A bad answer would be "do nothing, we don't care if sourcing SSM is
broken".

A simple answer would be "an SSM source MUST use option (2), i.e.
tunnel packets to the home agent".  In this case, either option (1)
would never be used for any multicast traffic, or else the host would
have to know whether a receiver might want to use an include-mode list
with MLDv2 and tunnel to the home agent if so.  Personally, I don't
like this answer, but if this is what the consensus turns out to be,
then it should be documented in the Mobile IPv6 spec (no effect on the
SSM or MAGMA WGs), and apis to inform the mobile node stack that it
MUST tunnel to the home agent may be required.

Another answer, which would require adding rules to both the Mobile
IPv6 and MLDv2 specs (and probably mentioning it in the SSM overview
doc), would be to make method (1) work for SSM sources.  A potential
solution here is twofold:

1) If an MLDv2 host is sending an include-mode report for a source X,
and a binding cache entry exists for X with a care-of-address COA, then
put both X and COA in the membership report.  (This means that if you
can somehow get a Binding Update to all the group members, then they'll
be able to receive packets sourced from COA, since routers will
construct join state back to the foreign link.)  It needs to join to
both addresses so that if the node moves again, it won't be stuck
waiting for data from the old COA.

2) A mobile node sourcing traffic when away from home needs to get a
Binding Update to all the group members.  I believe this can be done by
tunneling a packet via the home agent (and hence must have a source
address of its home address) which contains a Binding Update with
an Alternate Care-of Address of its current COA.  This would need to be
done periodically, so that new receivers get it.

Comments?  Am I missing anything?

-Dave Thaler




From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep 27 15:28:25 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11461
	for <mobileip-archive@odin.ietf.org>; Thu, 27 Sep 2001 15:28:24 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id MAA11493;
	Thu, 27 Sep 2001 12:27:47 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id MAA20719;
	Thu, 27 Sep 2001 12:27:34 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8RJQG7B021059
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 27 Sep 2001 12:26:16 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8RJQGku021058
	for mobile-ip-dist; Thu, 27 Sep 2001 12:26:16 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8RJQC7B021051
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 12:26:12 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id MAA20284
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 12:26:13 -0700 (PDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id NAA18873
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 13:27:11 -0600 (MDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id MAA08205;
	Thu, 27 Sep 2001 12:26:12 -0700 (PDT)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f8RJQBb26096;
	Thu, 27 Sep 2001 12:26:11 -0700
X-mProtect:  Thu, 27 Sep 2001 12:26:11 -0700 Nokia Silicon Valley Messaging Protection
Received: from Icharliep-1.iprg.nokia.com (205.226.22.18, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpdeiVLUf; Thu, 27 Sep 2001 12:26:09 PDT
Message-ID: <3BB37D5F.BC45505B@iprg.nokia.com>
Date: Thu, 27 Sep 2001 12:26:23 -0700
From: Charlie Perkins <charliep@iprg.nokia.com>
Organization: Nokia
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@kolumbus.fi>
CC: mobile-ip@sunroof.eng.sun.com
Subject: [mobile-ip] Re: multi-payload schemes
References: <200109271445.f8REjcl33856@givry.rennes.enst-bretagne.fr> <3BB342D6.E268637E@iprg.nokia.com> <011001c14782$1a216000$8a1b6e0a@arenanet.fi>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hello Jari,

> > In particular, it is likely that the multi-payload scheme
> > would require buffering and delay for previous data packets,
> > inserting Binding Updates into packets with data payloads
> > involves checking for recent movement at the time one consults
> > the route table.  This is quite a bit easier to implement,
> > and involves no delay.  The receiving end is also quite a
> > bit easier.

I see that I didn't type this correctly.  'inserting Binding Update'
should be the start of a new sentence.  As it is, I reckon that
it would be easy to misinterpret what I meant.

Regards,
Charlie P.



From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep 27 16:30:00 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12751
	for <mobileip-archive@odin.ietf.org>; Thu, 27 Sep 2001 16:29:59 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id OAA07605;
	Thu, 27 Sep 2001 14:29:08 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id NAA17552;
	Thu, 27 Sep 2001 13:29:10 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8RKS07B021333
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 27 Sep 2001 13:28:00 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8RKRxK6021332
	for mobile-ip-dist; Thu, 27 Sep 2001 13:27:59 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from eastmail1.East.Sun.COM (eastmail1.East.Sun.COM [129.148.1.240])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8RKRv7B021325
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 13:27:57 -0700 (PDT)
Received: from onion.east.sun.com (onion.East.Sun.COM [129.148.174.110])
	by eastmail1.East.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id QAA16344
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 16:27:59 -0400 (EDT)
Received: (from glass@localhost)
	by onion.east.sun.com (8.9.3+Sun/8.9.3) id QAA11594
	for mobile-ip@sunroof.eng.sun.com; Thu, 27 Sep 2001 16:28:29 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8RGuV7B017098
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 09:56:31 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA16892
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 09:56:33 -0700 (PDT)
Received: from mx.webfountain.com (mx.digitalfountain.com [209.219.233.39])
	by patan.sun.com (8.9.3+Sun/8.9.3) with SMTP id KAA01716
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 10:56:21 -0600 (MDT)
Received: (qmail 31646 invoked from network); 27 Sep 2001 16:56:30 -0000
Received: from mail.intranet (10.1.1.37)
  by mx.digitalfountain.com with SMTP; 27 Sep 2001 16:56:30 -0000
Received: from mikedell (pptp-10-1-129-55.intranet [10.1.129.55])
	by mail.intranet (8.9.3/8.9.3) with SMTP id JAA06909;
	Thu, 27 Sep 2001 09:56:04 -0700
X-Authentication-Warning: mail.intranet: Host pptp-10-1-129-55.intranet [10.1.129.55] claimed to be mikedell
From: "Michael Luby" <luby@digitalfountain.com>
To: "Dave Thaler" <dthaler@windows.microsoft.com>
Cc: <mobile-ip@sunroof.eng.sun.com>, <ssm-interest@external.cisco.com>,
        <magma@innovationslab.net>
Subject: [mobile-ip] RE: Joining to SSM sources that are IPv6 mobile nodes
Date: Thu, 27 Sep 2001 09:56:25 -0700
Message-ID: <NEBBIAPCNKEDCLPNFBNCOEGOCHAA.luby@digitalfountain.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Importance: Normal
In-Reply-To: <2E33960095B58E40A4D3345AB9F65EC102DB7D6A@win-msg-01.wingroup.windeploy.ntdev.microsoft.com>
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Dave,

I think that neither of these options is necessarily the right answer all
the time, as this seems to me to be more of an application service issue
rather than a networking service issue.

For example, an application could implement the solution to 1 that you
propose below at the application level in pretty much the same manner
(without additional explicit network support).  The idea would be for the
roaming source to always send its current address to its permanent home
address (at the application level), and then the home server would always
send out the current address of the source through an application level SSM
announcement channel.  In this solution, the roaming source would send its
data multicast packets using its local source address.

As another example, at the application level, solution 2 could also be used,
where the roaming source always tunnels its multicast packets back to its
permanent home address, and then these are sent out using SSM from the home
address.

There are other ways of doing this as well, but I believe that they should
be done at the application level specific to each application, and not at
the network services level.  I like the philosophy of building a simple but
robust common denominator network service (like SSM), rather than trying to
build too much of the complexity into this level (like MSDP) that could be
done more efficiently and simply at the application level (because one
doesn't have to provide a general implementation at the application level,
only a much simpler implementation particular to the application).  The
problem with doing this at the network level is that it will either be too
general (and thus hard to implement and scale) or else too restrictive.

Mike

-----Original Message-----
From: Dave Thaler [mailto:dthaler@windows.microsoft.com]
Sent: Wednesday, September 26, 2001 7:05 PM
To: mobile-ip@sunroof.eng.sun.com; magma@innovationslab.net;
ssm-interest@external.cisco.com
Subject: Joining to SSM sources that are IPv6 mobile nodes


Sorry for the cross-post, but this issue really does concern
interactions between drafts in three different WGs:
MobileIP: draft-ietf-mobileip-ipv6-14.txt, section 10.19
MAGMA: draft-vida-mld-v2-01.txt
SSM: draft-ietf-ssm-overview-01.txt
(Please trim the recipients when responding, if appropriate.)

Starting from the Mobile IPv6 spec:
> A mobile node that wishes to send packets to a multicast group
> also has two options:  (1) send directly on the foreign link being
> visited; or (2) send via a tunnel to its home agent.  Because
> multicast routing in general depends upon the Source Address used in
> the IPv6 header of the multicast packet, a mobile node that tunnels a
> multicast packet to its home agent MUST use its home address as the
> IPv6 Source Address of the inner multicast packet.

The issue is how to continue getting data to receivers after a mobile
node moves.
Method (2) works fine for SSM, but has the obvious inefficiency.
Method (1) does not work as is for SSM.

I'll assume the sender has advertised (HA,G) in whatever method (e.g. a
web page) he uses to announce the session, just like the session would
advertise HA in any method used to get unicast clients to connect to
him.  (The sender could just as well use (COA,G) but the same issues
arise if it subsequently moves, from my understanding.)

In the SSM model, when receivers join (HA,G) via MLDv2, join state is
constructed along the path to HA (i.e. hitting the home agent).  Any
data sent directly on the foreign link being visited will go nowhere,
since there is no join state there.

A bad answer would be "do nothing, we don't care if sourcing SSM is
broken".

A simple answer would be "an SSM source MUST use option (2), i.e.
tunnel packets to the home agent".  In this case, either option (1)
would never be used for any multicast traffic, or else the host would
have to know whether a receiver might want to use an include-mode list
with MLDv2 and tunnel to the home agent if so.  Personally, I don't
like this answer, but if this is what the consensus turns out to be,
then it should be documented in the Mobile IPv6 spec (no effect on the
SSM or MAGMA WGs), and apis to inform the mobile node stack that it
MUST tunnel to the home agent may be required.

Another answer, which would require adding rules to both the Mobile
IPv6 and MLDv2 specs (and probably mentioning it in the SSM overview
doc), would be to make method (1) work for SSM sources.  A potential
solution here is twofold:

1) If an MLDv2 host is sending an include-mode report for a source X,
and a binding cache entry exists for X with a care-of-address COA, then
put both X and COA in the membership report.  (This means that if you
can somehow get a Binding Update to all the group members, then they'll
be able to receive packets sourced from COA, since routers will
construct join state back to the foreign link.)  It needs to join to
both addresses so that if the node moves again, it won't be stuck
waiting for data from the old COA.

2) A mobile node sourcing traffic when away from home needs to get a
Binding Update to all the group members.  I believe this can be done by
tunneling a packet via the home agent (and hence must have a source
address of its home address) which contains a Binding Update with
an Alternate Care-of Address of its current COA.  This would need to be
done periodically, so that new receivers get it.

Comments?  Am I missing anything?

-Dave Thaler




From owner-mobile-ip@sunroof.eng.sun.com  Thu Sep 27 21:02:57 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA16704
	for <mobileip-archive@odin.ietf.org>; Thu, 27 Sep 2001 21:02:57 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id SAA01072;
	Thu, 27 Sep 2001 18:02:13 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id SAA26087;
	Thu, 27 Sep 2001 18:01:58 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8S1147B023309
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 27 Sep 2001 18:01:04 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8S114BW023308
	for mobile-ip-dist; Thu, 27 Sep 2001 18:01:04 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8S1117B023301
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 18:01:01 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id SAA22252
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 18:01:04 -0700 (PDT)
From: Christopher.Carroll@VerizonWireless.com
Received: from mail.verizonwireless.com (mail2.verizonwireless.com [199.74.158.61])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id SAA28554
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 18:01:03 -0700 (PDT)
Received: from mail.verizonwireless.com 
	by mail.verizonwireless.com (414/1100) with ESMTP id f8S10xf23266
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 21:01:01 -0400 (EDT)
Received: by hqbedigwy2.corp.bam.com with Internet Mail Service (5.5.2653.19)
	id <TV06GVRR>; Thu, 27 Sep 2001 11:21:53 -0400
Message-ID: <43E8CCEAF148D211854C00805FA72E5808318FC6@rhqnneex1.corp.bam.com>
To: mobile-ip@sunroof.eng.sun.com
Subject: RE: [mobile-ip] Concerns/comments for aaa-keys and gen-key
Date: Thu, 27 Sep 2001 11:21:51 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Hi Erik,

I have the following comments regarding your concerns with the current
aaa-keys procedure:

1) Keying material is used between the MN and FA (or MN and HA) because a
Key Agreement Protocol is used as opposed to simply encrypting and
distributing the MN-HA or MN-FA key.  The reason for using a key agreement
protocol is that the MN-FA link and/or MN-HA link may be over-the-air which
is inherently more vulnerable to eavesdropping and cryptanalysis.  Please
review the attached comments, originally sent to Charlie Perkins and Pat
Calhoun, regarding the vulnerabilities associated with their original
proposal to simply encrypt the MN-HA and/or MN-FA key for transmission to
the MN.

Key Agreement Protocols are well understood and have been used for many
years in GSM and North American cellular/PCS networks to enable secure
session key generation (in a symmetric/secret key system).

Note: It is assumed that AAA links to other MIP entities (AAA, HA and FA)
will be protected.

2)  With regard the AAA-to-AAA, AAA-to-HA and AAA-to-FA links, 3G Wireless
providers intend to protect these links using one of several techniques: 1)
IPsec, 2) Linked encryption boxes, or 3) private commication links.
Distribution of AAA keys is NOT OUR ONLY CONCERN on these links.  We intend
to encrypt all data between the AAA and HA/FA for subscriber privacy reasons
and other security concerns.  Assuming we intend to protect these links
using techniques outside the scope of MIP, it is inefficient from our
perspective to utilize a more elaborate key distribution scheme between the
AAA and other network infrastructure components (which are controlled by the
service providers).  In other words, we'll already have an SA established
between these entities and don't need to deal with bootstrapping even
another SA!

I do recognize that other implementations of MIPv4 will require more
inherent security compliance (architecturally built-in SA establishment
schemes) because most users/system operators will not have the security
expertise/resources of large service providers.  I recommend that a separate
procedure/protocol be developed to satisfy this requirement without delaying
the implementation of the existing scheme.

thanks,

chris

>Hi Pat,
>
>Thanks for taking to time out to talk about security issues.  Verizon
>Wireless has reviewed your AAA Registration Keys for Mobile IP draft and we
>are concerned about how the MN-FA and MN-HA key are encrypted.  Feel free
to
>distribute these comments to any interested party.
>
>The scheme employs a fixed encryption pad (or mask) which may expose the
>MN-FA and MN-HA key to an attacker.  We assume that the mask is fixed
>because it is generated using the following formula:
>
>mask = MD5 (AAA-key || node-address || AAA-key)
>
>If the AAA-key is the shared secret between the MN and Home AAA server, it
>will likely not change for the life of the MN user's subscription because
it
>is expensive for the Mobile IP provider to distribute the AAA-key (we
define
>it as the MN-AAAh key) to the MN.  Also, if the "node-address" is the MN's
>NAI, the mask will remain constant for the life to the subscription.  In
GSM
>and TIA cellular networks, the root key (shared secret between the Mobile
>Station and Authentication Center) is never changed, i.e., MS retains the
>same root key for years (note: other session security keys are continously
>generated from the root to ensure security).  Note: your draft proposes
>using the MN's home IP address as the "node-address", however, based on the
>last TSG-P meeting, I believe you were planning on changing it to the MN's
>NAI.
>
>Fixed Mask Problems:
>
>1)  If the encryption mask remains fixed, any FA that interacts with a
>particular MN will have the ability to recover the encryption mask for both
>MN-FA and MN-HA key distribution.  This may not be significant for Verizon
>Wireless initially because all the FAs will be controled by us.  But
>eventually we may allow our subscribers to interact with Mobile IP networks
>controlled by other companies, the government, or individuals.  Anyone with
>access to these FAs with be able to recover the fixed encryption mask and
>subsequently recover the MN-FA and/or MN-HA key by eavesdropping on the
>MN-to-FA air interface.  The attack works as follows:
>
>The FA normally sends the MN-FA key update in an Unsolicited MN-FA key From
>AAA Subtype message (included in the Registration Reply).  The MN-FA is
>encoded as follows:
>
>Encoded MN-FA key = MN-FA key XOR Fixed Encryption Mask
>
>Fixed Encryption Mask = MD5 (MN-AAAh key || MN NAI || MN-AAAh key)
>
>The FA also recieves the MN-FA key via its AAA server.
>
>The FA recovers the Fixed Encryption Mask using the following:
>
>Fixed Encryption Mask = MN-FA key XOR (MN-FA key XOR Fixed Encryption Mask)
>
>By eavesdropping on any future MN-FA or MN-HA key updates on the air
>interface, an attacker with access to any FA that interacts with the MN
will
>have the ability to recover either key.
>
>Imagine the scenarion in which Verizon Wireless allows the FBI to set up
its
>own Mobile IP network that interacts with our service.  Whenever a Verizon
>Wireless subscriber accesses thier network, they save the Fixed Mask
>associated with that subscriber.  The same thing could happen on a
>University campus in which hackers are actually running the Mobile IP
>network.  An individual, out of the goodness in his heart, could offer free
>service to subscribers while they happen to be within the vacinity of his
>network (while stealing MN-FA/MN-HA masks).
>
>Finally, the MN-FA key may be more important than intended for Mobile IP
>alone.  The MN-FA key, as a shared secret between the MN and FA, can enable
>other security services such as Radio Access Layer Encryption and Message
>Authentication.
>
>2)  Because the mask is fixed, an eavesdropper on the air interface is able
>to track changes made to the MN-FA or MN-HA key whenever the keys are
>updated.  Consider the following:
>
>Encoded MN-FA key #1 = MN-FA key #1 XOR Fixed Encryption Mask
>
>Encoded MN-FA key #2 = MN-FA key #2 XOR Fixed Encryption Mask
>
>Delta MN-FA key = Encoded MN-FA key #1 XOR Encoded MN-FA key #2
>
>As long as the MN-FA key is a cryptographically strong secret key (randomly
>or pseudo-randomly generated), you have the situation in which the MN-FA
key
>is acting as a One-time Pad for the fixed Mask!  I don't believe this was
>your original intent.
>
>Because MD5 is a one-way function, I don't believe that an attacker can
>actually recovery the MN-FA (or MN-HA) key.  However, you are leaking
>information about the key.  A real cryptographer (not me) might be able to
>exploit this.
>
>We propose the following enhancements to draft-ietf-mobileip-aaa-key-04.txt
>to eliminate this vulnerability:
>
>Instead of distributing an encrypted key, we recommend that the procedure
>utilize a key agreement scheme.  The procedure works as follows when
>generating the MN-HA key:
>
>1.  The AAA server determines the "node-address" of the MN with
node-address
>= NAI.
>
>2.  The AAA server generates RAND (64 bits recommended).  RAND should be
>randomly or pseudo-randomly generated based on RFC 1750.
>
>3.  The AAA server computes the following:  MN-HA key = MD5 (MN-AAAh key ||
>MN NAI || HA IP address || RAND).
>
>4.  The AAA server inserts the RAND (instead of the encoded MN-HA key) into
>the Key extension in the "RAND" field (which replaces the MN-HA Encoded Key
>data field).  Note: the AAA server must independently delivery the MN-HA
key
>to the HA.
>
>5.  The MN computes the following:  MN-HA key = MD5 (MN-AAAh key || MN NAI
>|| HA IP address || RAND).
>
>The procedure for MN-FA key generation is:
>
>1.  The AAA server determines the "node-address" of the MN with
node-address
>= NAI.
>
>2.  The AAA server generates RAND (64 bits recommended).
>
>3.  The AAA server computes the following:  MN-fA key = MD5 (MN-AAAh key ||
>MN NAI || FA IP address || RAND).
>
>4.  The AAA server inserts the RAND (instead of the encoded MN-FA key) into
>the Key extension in the "RAND" field (which replaces the MN-FA Encoded Key
>data field).  Note: the AAA server must independently delivery the MN-FA
key
>to the FA.
>
>5.  The MN computes the following:  MN-FA key = MD5 (MN-AAAh key || MN NAI
>|| FA IP address || RAND).
>
>We do not alter the structure of the Unsolicited Key extension.  We only
>replace the Encoded key with RAND.  While RAND is only 64-bits (or even
only
>32-bits), the MN and Home AAA server still generate a 128-bit key.  Thus,
we
>reduce air interface overhead while increasing security at the same time.
>
>Security Considerations:
>
>Under our proposal, the MN-HA and MN-FA key are derived from the root
>MN-AAAh key.  If the keys are derived based on a cryptographically secure
>one-way function (e.g. MD5 or SHA-1), compromise of the MN-HA or MN-FA key
>will not compromise the root MN-AAAh key.  If the root MN-AAAh key is
>compromised, the current MN-HA or MN-FA key will be compromised only if the
>attacker observed the RAND transmitted during the Update.  However, this is
>also true for the existing scheme, because the MN-AAAh key is used to
>encrypt the MN-FA or MN-HA key during the Update.
>
>Key agreement is not a new or unproven key distribution method.  It has
been
>used successfully used for years by GSM and TIA for cellular telephone
>security.



From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep 28 00:03:48 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA20643
	for <mobileip-archive@lists.ietf.org>; Fri, 28 Sep 2001 00:03:47 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id VAA08186;
	Thu, 27 Sep 2001 21:03:07 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id VAA13291;
	Thu, 27 Sep 2001 21:02:57 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8S41V7B023733
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 27 Sep 2001 21:01:31 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8S41Vmg023732
	for mobile-ip-dist; Thu, 27 Sep 2001 21:01:31 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8S41R7B023725
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 21:01:27 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id VAA06775
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 21:01:30 -0700 (PDT)
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by venus.sun.com (8.9.3+Sun/8.9.3) with SMTP id VAA28765
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 21:01:29 -0700 (PDT)
Received: (qmail 1846 invoked by uid 500); 28 Sep 2001 03:47:24 -0000
Date: Thu, 27 Sep 2001 20:47:24 -0700
From: Pat Calhoun <pcalhoun@diameter.org>
To: "Charles E. Perkins" <charliep@IPRG.nokia.com>
Cc: Erik Nordmark <Erik.Nordmark@eng.sun.com>, mobile-ip@sunroof.eng.sun.com,
        Pat Calhoun <pcalhoun@diameter.org>
Subject: Re: [mobile-ip] Concerns/comments for aaa-keys and gen-key
Message-ID: <20010927204724.A1723@charizard.diameter.org>
References: <Roam.SIMC.2.0.6.1001427527.14101.nordmark@bebop.france> <3BB15C81.DE5655DA@iprg.nokia.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <3BB15C81.DE5655DA@iprg.nokia.com>; from charliep@IPRG.nokia.com on Tue, Sep 25, 2001 at 09:41:37PM -0700
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Sorry for the latency... seem to be a tad busy these days :(

> > High level comments (details below):
> > 1. The scope of the problem and proposed solution isn't very clear.
> 
> The scope of the problem is to create a way for AAA to authorize network
> access and set up the security associations needed for the mobile node
> to work with a home agent.  It is supposed to look very much like what
> is done today with RADIUS, except for improvements due to DIAMETER.
> Building on existing experience seems to help a lot with getting
> interoperability.

In order to cut down on the spec size, we decided not to copy all the
verbose text from the Diameter Mobile IP application. However, all of the
information you are requesting can be found there.

> > 3. It is unclear what level of careful security review the documents
> >    have seen.
> 
> The people doing the work would probably state that they're a heck
> of lot more secure than RADIUS, but I probably ought to avoid trying
> to put any words in their mouths.
> 

The latest revisions of the draft made use of key material, which was
suggested by 3GPP2's AHAG chair (their security folks). Since no keys
are sent in the clear, there is no possibility of key compromise (other
than plain text and brute force attacks - which one can always do).

> > 4. Between the lines there appear to be some architectural assumptions
> >    e.g. that AAAh and HA have some high degree of mutual trust, which seem
> >    to imply that the solution might not be a good fit when the AAAh and
> >    HA are operated by different entities.
> 
Again, all of this can be found in the Diameter Mobile IP application.

> > While the abstract talks solely of using this to create security associations
> > between MN-HA and MN-FA there appear to be other documents that appear to
> > use the same protocol mechanisms such as draft-le-aaa-lsa-tsk-00.txt.

ok... and?

> > Thus what is needed is something indicating the applicability of aaa-keys.
> > Without knowing the applicability it is not possible to determine what
> > needs to be supported in terms of algorithms and key sizes, as
> > well as the constraints on how to negotiate what algorithm and key length
> > to use for a given SA.

Mobile IP is a request/response protocol. Unfortunately, it doesn't lend itself
well to negotiations. So, the AAAH (owned by the administrator) will have to
select the algorithm and key length. If the transforms provided are not
sufficient (e.g. hmac-md5), then some guidance would be appreciated.

> > Underspecification
> > ------------------
> > 
> > As Thomas specified in depth there specification doesn't actual
> > contain message flows showing the interaction between MN, FA, HA, and the
> > AAA entities.

right. again, we decided against redoing all of the work in the Diameter
Mobile IP application. Folks MUST read the other spec anyways to build a
system, so we didn't feel it was all that necessary to redo in this spec.

> 
> > (Who sends what to whom when? When processing occurs when a message is
> > received.)
> > Without this it is hard if not impossible to do a security analysis of
> > the specification.
> > 
> > The spec is completely silent on the need for re-keying and the
> > mechanism used to accomplish this.

it states what the key lifetime is. Once a key is expired, one rekeys.
perhaps additional language is needed in that area.

> > The spec doesn't talk about algorithm negotiation?
> > I would assume that there needs to be at least one mandatory to implement
> > algorithm to ensure that there is interoperability.

check. hmac-md5 should be a must (boy.. that didn't sound right)

> > Does the protocol assume that the AAA exchanges provide confidentiality
> > or is it sufficient if the AAA exchanges provide integrity of the information
> > carried in the AAA protocol?

It doesn't matter if AAA doesn't provide confidentiality since the actual keys
aren't passed. Just the key material.

> > The document talks about using the NAI to identify the user, which
> > might have privacy implications. While the NAI must have a stable domain
> > component (the part after the @ sign) in order to route to the right home
> > AAA server, but that doesn't inherently require that the component
> > before the @ sign be a fixed string like a user name.
> > Has there been any privacy review of this?
> > Are there any thoughts or proposals around using temporary IDs instead
> > of user names before the @ sign?

These very schemes are used universally for dial-up, and the whole AAA
protocol is modeled around this. If this is a genuine concern, it applies
to more than just Mobile IP.

> > Architectural Assumptions
> > ------------------------
> > 
> > Between the lines there appear to be some architectural assumptions
> > e.g. that AAAh and HA have some high degree of mutual trust, which seem
> > to imply that the solution might not be a good fit when the AAAh and
> > HA are operated by different entities.

All of these assumptions are clearly defined in the Diameter Mobile IP 
application.

> > It would seem unwise to have hard-code the requirement that the AAA home
> > and the IP address home is the same; folks have suggested scenarios
> > where the AAA home could be e.g. Visa and the routing home is
> > a home agent in the house (or elsewhere). Of course there
> > might also be scenarios when the are provided by the same administration e.g
> > when the same ISP/operator provides AAA and routing home.
> > So I think it makes sense to support both.

It supports both.

PatC


From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep 28 00:10:11 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA20706
	for <mobileip-archive@odin.ietf.org>; Fri, 28 Sep 2001 00:10:11 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id VAA09272;
	Thu, 27 Sep 2001 21:09:31 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id VAA14422;
	Thu, 27 Sep 2001 21:09:26 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8S48f7B023830
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 27 Sep 2001 21:08:41 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8S48f27023829
	for mobile-ip-dist; Thu, 27 Sep 2001 21:08:41 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8S48c7B023822
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 21:08:38 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id VAA07737
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 21:08:40 -0700 (PDT)
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by patan.sun.com (8.9.3+Sun/8.9.3) with SMTP id WAA28290
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 22:08:29 -0600 (MDT)
Received: (qmail 1870 invoked by uid 500); 28 Sep 2001 03:54:36 -0000
Date: Thu, 27 Sep 2001 20:54:36 -0700
From: Pat Calhoun <pcalhoun@diameter.org>
To: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Cc: Fredrik Johansson <fredrik.johansson@ipunplugged.com>,
        mobile-ip@sunroof.eng.sun.com,
        Charlie Perkins <charliep@IPRG.nokia.com>,
        Pat Calhoun <pcalhoun@diameter.org>
Subject: Re: [mobile-ip] Concerns/comments for aaa-keys and gen-key
Message-ID: <20010927205436.B1723@charizard.diameter.org>
References: <MJEMJBGGCLLDLFFAHLJKAEHFDGAA.fredrik.johansson@ipunplugged.com> <Roam.SIMC.2.0.6.1001495690.1688.nordmark@bebop.france>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <Roam.SIMC.2.0.6.1001495690.1688.nordmark@bebop.france>; from Erik.Nordmark@eng.sun.com on Wed, Sep 26, 2001 at 11:14:50AM +0200
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

> Thanks for the pointer - I hope this sheads some light.
> [Seems like having this pointer in the mobileip drafts would be asking
> to much. I should have read all of draft-ietf-mobileip* and draft-ietf-aaa-* 
> before asking :-)]


Charlie and I removed these based on a comment on another one of our
drafts that had such a reference. Perhaps now that AAA has selected its
protocol, we can now include the reference.

> A quick look leads me to believe that aaa-key is still very underspecified
> when it comes to how the MN extensions are sent and processed in the MN
> packets - diameter-mobileip talks about how/when the diameter messages
> are sent and how they are processed on receipt, but nothing about what
> the MN does.

ok... perhaps more is needed here.

> > It's up to the policy of the AAAh to determine the necessary level of the
> > keys to distribute.
> 
> I do think we need an applicability to understand e.g. whether only 64 bits
> of randomness is sufficient, what is required in terms of re-keying, etc.

ok

> 
> Which mobileip draft?
> It seems like the MN might need to be able to determine when a key
> is about to expire and initiate a re-key, but aaa-keys is utterly silent
> on anything about re-keying.

It is in the Diameter Mobile IP draft, but it should also be in this draft.

> 
> > Since the mobile node and AAAh is in the same administrative domain it can
> > be
> > any algorithm that is supported by both nodes. However, HMAC-MD5 is
> > mandatory to
> > support in rfc2002-bis and in Diameter so there's one algorithm that always
> > will be supported.
> 
> So it seems like aaa-keys should list this one as MUST implement.

yes

> I'm told that inventing a new key exchange/agreement protocol is non-trivial.

right, that this is not a key exchange/agreement protocol. It has been
through a security review, but not an IETF one :(

> What the drafts are describing sure looks like a new protocol in this
> area. 
> If this is the case I expect there to somehow be a critical mass of
> experts in this area that will review this protocol, because
> I don't think its in our collective interest to create another WEP
> debacle.

Although these are two completely different domains, I agree that a 
security review is needed....


> Alternative, if there are existing proven mechanisms to distribute keys
> that fit into this it would seem to be prudent to reuse that.
> (The diameter-e2e-sec draft is proposing to reuse CMS for diameter for
> instance.)

but cms/mobile ip seems unnecessarily cumbersome, and would now require
a multiple request/reply exchange.

PatC


From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep 28 00:11:40 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA20746
	for <mobileip-archive@lists.ietf.org>; Fri, 28 Sep 2001 00:11:40 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id WAA29683;
	Thu, 27 Sep 2001 22:10:52 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id VAA14824;
	Thu, 27 Sep 2001 21:10:48 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8S49s7B023866
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 27 Sep 2001 21:09:54 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8S49so2023865
	for mobile-ip-dist; Thu, 27 Sep 2001 21:09:54 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8S49n7B023855
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 21:09:49 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id VAA07876
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 21:09:52 -0700 (PDT)
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by patan.sun.com (8.9.3+Sun/8.9.3) with SMTP id WAA28869
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 22:09:40 -0600 (MDT)
Received: (qmail 1888 invoked by uid 500); 28 Sep 2001 03:55:47 -0000
Date: Thu, 27 Sep 2001 20:55:47 -0700
From: Pat Calhoun <pcalhoun@diameter.org>
To: Michael Thomas <mat@cisco.com>
Cc: mobile-ip@sunroof.eng.sun.com,
        Fredrik Johansson <fredrik.johansson@ipunplugged.com>,
        Erik.Nordmark@eng.sun.com, Charlie Perkins <charliep@IPRG.nokia.com>,
        Pat Calhoun <pcalhoun@diameter.org>
Subject: Re: [mobile-ip] Concerns/comments for aaa-keys and gen-key
Message-ID: <20010927205547.C1723@charizard.diameter.org>
References: <MJEMJBGGCLLDLFFAHLJKAEHFDGAA.fredrik.johansson@ipunplugged.com> <Roam.SIMC.2.0.6.1001495690.1688.nordmark@bebop.france> <15282.3298.522332.579900@thomasm-u1.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <15282.3298.522332.579900@thomasm-u1.cisco.com>; from mat@cisco.com on Wed, Sep 26, 2001 at 10:14:10AM -0700
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

>    Right. This has been what my discomfort with these
>    drafts have been related too. Currently, AAA (RADIUS) 
>    is a one way authentication proxy mechanism. DIAMETER
>    brings mutual authentication to the table, but I think
>    it's quite a leap of faith to say that AAA should then 
>    become a key distribution protocol as well. Key distribution
>    protocols are hard, and it is not clear to me that MIP is
>    a very good venue to be pursuing them. At the very least,
>    keying MN/HA SA's begs the question of why you should
>    stop there. Why should AAA not be able to key other 
>    protocols as well? How many specialized AAA key distribution
>    protocols will there be? Will there be a sufficient amount
>    of review by clueful security people to make certain that
>    stupid mistakes are not made? Has anybody considered that
>    there may be significant wheel-reinvention going on here
>    (cf Kerberos).
> 
>    My feeling is that if this is done at all, it should
>    be done in a new working group and most definitely
>    under the security AD's watch.

Let me see... scrap the work, and start over with new folks... 

very constructive. 

How about we review the work, and then comment.

sigh.

PatC


From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep 28 00:14:48 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA20788
	for <mobileip-archive@lists.ietf.org>; Fri, 28 Sep 2001 00:14:47 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id WAA01284;
	Thu, 27 Sep 2001 22:14:03 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id VAA15540;
	Thu, 27 Sep 2001 21:14:04 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8S4D87B024013
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 27 Sep 2001 21:13:08 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8S4D89n024012
	for mobile-ip-dist; Thu, 27 Sep 2001 21:13:08 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8S4D57B024005
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 21:13:05 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id VAA15432
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 21:13:07 -0700 (PDT)
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with SMTP id VAA25678
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 21:13:07 -0700 (PDT)
Received: (qmail 1923 invoked by uid 500); 28 Sep 2001 03:59:03 -0000
Date: Thu, 27 Sep 2001 20:59:03 -0700
From: Pat Calhoun <pcalhoun@diameter.org>
To: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Cc: Fredrik Johansson <fredrik.johansson@ipunplugged.com>,
        mobile-ip@sunroof.eng.sun.com,
        Charlie Perkins <charliep@IPRG.nokia.com>,
        Pat Calhoun <pcalhoun@diameter.org>
Subject: Re: [mobile-ip] Concerns/comments for aaa-keys and gen-key
Message-ID: <20010927205903.D1723@charizard.diameter.org>
References: <MJEMJBGGCLLDLFFAHLJKKEJGDGAA.fredrik.johansson@ipunplugged.com> <Roam.SIMC.2.0.6.1001600110.20729.nordmark@bebop.france>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <Roam.SIMC.2.0.6.1001600110.20729.nordmark@bebop.france>; from Erik.Nordmark@eng.sun.com on Thu, Sep 27, 2001 at 04:15:10PM +0200
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

> It is the assertion that key material being different than keys
> that makes the alarm bells start ringing - I think such an assertion needs
> to be analysed by folks that are subject matter experts in the protocols
> and algorithms used to carry the material as well as constructing
> keys from the material.

In fact, sending key material is MUCH MORE secure than keys... not sure
why bells are ringing... maybe someone's at your front door

:)

> This approach is quite different that the proposed 
> draft-ietf-aaa-diameter-e2e-sec which re-uses an existing mechanism
> (CMS) and relies on certificates (by distributing the certificate chains
> itself). At least that doesn't seem to invent new stuff that makes my alarm
> bells go off.

but cms is not appropriate here. the mobile node doesn't participate
in the AAA transactions.

PatC


From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep 28 00:16:44 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA20815
	for <mobileip-archive@lists.ietf.org>; Fri, 28 Sep 2001 00:16:44 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id WAA02166;
	Thu, 27 Sep 2001 22:16:04 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id VAA16001;
	Thu, 27 Sep 2001 21:16:05 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8S4Eq7B024051
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 27 Sep 2001 21:14:52 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8S4EqCu024050
	for mobile-ip-dist; Thu, 27 Sep 2001 21:14:52 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8S4Em7B024043
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 21:14:48 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id VAA15653
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 21:14:51 -0700 (PDT)
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by patan.sun.com (8.9.3+Sun/8.9.3) with SMTP id WAA01572
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 22:14:39 -0600 (MDT)
Received: (qmail 1943 invoked by uid 500); 28 Sep 2001 04:00:46 -0000
Date: Thu, 27 Sep 2001 21:00:46 -0700
From: Pat Calhoun <pcalhoun@diameter.org>
To: mobile-ip@sunroof.eng.sun.com
Cc: Fredrik Johansson <fredrik.johansson@ipunplugged.com>,
        Erik.Nordmark@eng.sun.com
Subject: Re: [mobile-ip] Concerns/comments for aaa-keys and gen-key
Message-ID: <20010927210046.E1723@charizard.diameter.org>
References: <MJEMJBGGCLLDLFFAHLJKAEHFDGAA.fredrik.johansson@ipunplugged.com> <m3u1xq2jqc.fsf@test9.crm.mot.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <m3u1xq2jqc.fsf@test9.crm.mot.com>; from petrescu@crm.mot.com on Wed, Sep 26, 2001 at 02:56:59PM +0200
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

> It looks to me that an (AAAH, HA) must have SLA's with every AAAF's in
> whose domains that HA's MN could possibly roam.  Doesn't this boil
> down to a scaleability issue similar to Mobile IPv6 (in which MN must
> have trust relationships with any possible CN)?

nope. That's why folks like GRIC (www.gric.com) and IPass (www.ipass.com)
exist, which is to reduce B2B roaming relationships.

> I can understand trust between AAAH and HA, but I suppose that trust
> relationship between AAAH and AAAF's, or between HA's and AAAF's, are
> difficult.  If I'm missing something, sorry, please enlighten me.

sure, a top level AAAF can be used to reduce the number of relationships,
or a broker can be used.

PatC


From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep 28 00:22:25 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA20873
	for <mobileip-archive@odin.ietf.org>; Fri, 28 Sep 2001 00:22:24 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id VAA11919;
	Thu, 27 Sep 2001 21:21:47 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id VAA16904;
	Thu, 27 Sep 2001 21:21:40 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8S4Kr7B024227
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 27 Sep 2001 21:20:53 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8S4KrP9024226
	for mobile-ip-dist; Thu, 27 Sep 2001 21:20:53 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8S4Kn7B024219
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 21:20:50 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id VAA09533
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 21:20:52 -0700 (PDT)
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by patan.sun.com (8.9.3+Sun/8.9.3) with SMTP id WAA03820
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 22:20:40 -0600 (MDT)
Received: (qmail 1978 invoked by uid 500); 28 Sep 2001 04:06:47 -0000
Date: Thu, 27 Sep 2001 21:06:47 -0700
From: Pat Calhoun <pcalhoun@diameter.org>
To: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Cc: "Charles E. Perkins" <charliep@iprg.nokia.com>,
        mobile-ip@sunroof.eng.sun.com, Pat Calhoun <pcalhoun@diameter.org>
Subject: Re: [mobile-ip] Concerns/comments for aaa-keys and gen-key
Message-ID: <20010927210647.F1723@charizard.diameter.org>
References: <3BB1F475.A0BF4DD1@iprg.nokia.com> <Roam.SIMC.2.0.6.1001577030.19672.nordmark@bebop.france>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <Roam.SIMC.2.0.6.1001577030.19672.nordmark@bebop.france>; from Erik.Nordmark@eng.sun.com on Thu, Sep 27, 2001 at 09:50:30AM +0200
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

While on this interoperability talk, I'd like to note that we have 4 
independently developed implementations that successfully interoperated
on many occasions.

PatC
On Thu, Sep 27, 2001 at 09:50:30AM +0200, Erik Nordmark wrote:
> 
> Charlie,
> 
> > > Do you view that a vendor that takes these extensions and build
> > > a proprietary protocol should be able to say that their protocol
> > > conforms to an RFC?
> > 
> > Here, I think you meant,  "a proprietary security protocol".
> > If so, the answer is "yes".
> 
> No, I actually meant "protocol".
> 
> The question I'm trying to ask was the same as the one about vendor X and Y;
> whether you think it is ok that two vendors can correctly implement
> a given set of RFCs and conform to them, and there is no chance for them to
> interoperate since they've chosen different optional subsets of the protocols.
> 
> And you didn't seem to answer that question (see below using TCP FIN/RST
> as an example).
> 
> > Even so, I reckon it would be fine to mandate a particular security
> > algorithm, but I didn't build the prototypes, and I don't know which
> > algorithm people would choose for the default.  Is there something
> > besides IKE that we can mandate here?  Otherwise, I would worry that
> > placing the requirement would amount to an indefinite delay while
> > someone creates a new default choice -- which would then itself have
> > to undergo months of review and would probably be more complicated
> > than the whole rest of the AAA-keys document, maybe by an order
> > of magnitude.
> 
> I'm a bit lost - the comment was about security algorithms (like HMAC-MD5) -
> what does IKE or any other key exchange/agreement protocol have to do
> with this?
> 
> > However, I would emphasize the difference between building
> > protocols, vs. building systems.  A system has many parts,
> > and even using interoperable protocols can usually be built
> > so that there isn't any interoperation.  To take a trivial
> > example, two systems can implement IP and TCP and UDP and
> > yet not interoperate because of mismatch at the application
> > level.  I don't remember any requirement that TCP specify a
> > guaranteed interoperable application running at a well-known port.
> > IP itself doesn't require any interoperable transport protocol,
> > and yet without such a thing, two systems cannot interoperate.
> > Even so, we all think of IP as being a nice, small. interoperable
> > network protocol.
> 
> But those systems that implement UDP, TCP, and IP can in fact,
> provided they satisfy the MUST/MUST NOTs in the specs,
> interoperate at those layers. Sure, they might not share any applications
> which will effect the utility of the system for sure. But that isn't the
> point - the point is whether a given RFC specifying a given protocol
> is structured so that two implementations of that RFC can interoperate
> using the specified protocol ignoring the systems level issues when making the
> determination.
> 
> But the way I interpret your reluctance to mandating an algorithm for
> aaa-keys seems similar in advocating the TCP RST and TCP FIN packets should be
> optional resulting in one implementation only being capable of
> sending RST (and not FIN) and another implementation only being capable
> of processing FIN (and not RST). The way I interpret what you say is that
> this would be a system level issue and it is perfectly fine to have a spec
> that says MAY or the sending as well as receiving of FIN and RST.
> Did I understand your point correctly?
> 
> Cheers, 
>    Erik
> 
>  
> 


From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep 28 00:27:18 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA21001
	for <mobileip-archive@lists.ietf.org>; Fri, 28 Sep 2001 00:27:17 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id WAA06212;
	Thu, 27 Sep 2001 22:26:37 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id VAA17548;
	Thu, 27 Sep 2001 21:26:39 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8S4Pg7B024310
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 27 Sep 2001 21:25:42 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8S4PgVY024309
	for mobile-ip-dist; Thu, 27 Sep 2001 21:25:42 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8S4Pc7B024302
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 21:25:38 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id VAA10019
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 21:25:41 -0700 (PDT)
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with SMTP id WAA09373
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 22:26:38 -0600 (MDT)
Received: (qmail 1999 invoked by uid 500); 28 Sep 2001 04:11:35 -0000
Date: Thu, 27 Sep 2001 21:11:35 -0700
From: Pat Calhoun <pcalhoun@diameter.org>
To: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Cc: "Charles E. Perkins" <charliep@iprg.nokia.com>,
        mobile-ip@sunroof.eng.sun.com, Pat Calhoun <pcalhoun@diameter.org>
Subject: Re: [mobile-ip] Concerns/comments for aaa-keys and gen-key
Message-ID: <20010927211135.G1723@charizard.diameter.org>
References: <3BB34E99.DFDF4C69@iprg.nokia.com> <Roam.SIMC.2.0.6.1001607753.16697.nordmark@bebop.france>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <Roam.SIMC.2.0.6.1001607753.16697.nordmark@bebop.france>; from Erik.Nordmark@eng.sun.com on Thu, Sep 27, 2001 at 06:22:33PM +0200
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

> But if there are other (current and future) algorithms that are used
> it seems like there needs to be a way for the communicating parties to
> determine which algorithm to use.
> For instance, if 5 years from now HMAC-MD5 is not considered to be secure
> enough, when both parties implement the NEW-BETTER-ALG they should be able
> to discover that and use it instead of HMAC-MD5.

If that's the case, then a new multi round trip mobile ip protocol is
needed, since the protocol doesn't allow for negotiation.

> I wonder if anybody has been thinking about periodic re-keying in
> the RFC 2002 context - it sure seems usefulin general.
> I need to read what the AAA docs say about re-keyeing.

it states that once the lifetime has expired, keys are useless and rekey
is mandatory.

> Yep - we've had some terminology problems.
> I think adding some definitions to aaa-keys would help here (I think Thomas
> was asking for this as well).

I agree.

PatC


From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep 28 00:32:01 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA21083
	for <mobileip-archive@odin.ietf.org>; Fri, 28 Sep 2001 00:32:00 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id VAA13744;
	Thu, 27 Sep 2001 21:31:22 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id VAA18344;
	Thu, 27 Sep 2001 21:31:15 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8S4UV7B024417
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 27 Sep 2001 21:30:31 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8S4UU4I024416
	for mobile-ip-dist; Thu, 27 Sep 2001 21:30:30 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8S4UR7B024409
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 21:30:27 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id VAA21003
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 21:30:30 -0700 (PDT)
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with SMTP id VAA00856
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 21:30:29 -0700 (PDT)
Received: (qmail 2027 invoked by uid 500); 28 Sep 2001 04:16:26 -0000
Date: Thu, 27 Sep 2001 21:16:26 -0700
From: Pat Calhoun <pcalhoun@diameter.org>
To: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Concerns/comments for aaa-keys and gen-key
Message-ID: <20010927211626.H1723@charizard.diameter.org>
References: <43E8CCEAF148D211854C00805FA72E5808318FC6@rhqnneex1.corp.bam.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <43E8CCEAF148D211854C00805FA72E5808318FC6@rhqnneex1.corp.bam.com>; from Christopher.Carroll@VerizonWireless.com on Thu, Sep 27, 2001 at 11:21:51AM -0400
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Christopher,

Thank you very much for your response. I hope it helps Erik understand
that a security review has been done.

PatC

On Thu, Sep 27, 2001 at 11:21:51AM -0400, Christopher.Carroll@VerizonWireless.com wrote:
> Hi Erik,
> 
> I have the following comments regarding your concerns with the current
> aaa-keys procedure:
> 
> 1) Keying material is used between the MN and FA (or MN and HA) because a
> Key Agreement Protocol is used as opposed to simply encrypting and
> distributing the MN-HA or MN-FA key.  The reason for using a key agreement
> protocol is that the MN-FA link and/or MN-HA link may be over-the-air which
> is inherently more vulnerable to eavesdropping and cryptanalysis.  Please
> review the attached comments, originally sent to Charlie Perkins and Pat
> Calhoun, regarding the vulnerabilities associated with their original
> proposal to simply encrypt the MN-HA and/or MN-FA key for transmission to
> the MN.
> 
> Key Agreement Protocols are well understood and have been used for many
> years in GSM and North American cellular/PCS networks to enable secure
> session key generation (in a symmetric/secret key system).
> 
> Note: It is assumed that AAA links to other MIP entities (AAA, HA and FA)
> will be protected.
> 
> 2)  With regard the AAA-to-AAA, AAA-to-HA and AAA-to-FA links, 3G Wireless
> providers intend to protect these links using one of several techniques: 1)
> IPsec, 2) Linked encryption boxes, or 3) private commication links.
> Distribution of AAA keys is NOT OUR ONLY CONCERN on these links.  We intend
> to encrypt all data between the AAA and HA/FA for subscriber privacy reasons
> and other security concerns.  Assuming we intend to protect these links
> using techniques outside the scope of MIP, it is inefficient from our
> perspective to utilize a more elaborate key distribution scheme between the
> AAA and other network infrastructure components (which are controlled by the
> service providers).  In other words, we'll already have an SA established
> between these entities and don't need to deal with bootstrapping even
> another SA!
> 
> I do recognize that other implementations of MIPv4 will require more
> inherent security compliance (architecturally built-in SA establishment
> schemes) because most users/system operators will not have the security
> expertise/resources of large service providers.  I recommend that a separate
> procedure/protocol be developed to satisfy this requirement without delaying
> the implementation of the existing scheme.
> 
> thanks,
> 
> chris
> 
> >Hi Pat,
> >
> >Thanks for taking to time out to talk about security issues.  Verizon
> >Wireless has reviewed your AAA Registration Keys for Mobile IP draft and we
> >are concerned about how the MN-FA and MN-HA key are encrypted.  Feel free
> to
> >distribute these comments to any interested party.
> >
> >The scheme employs a fixed encryption pad (or mask) which may expose the
> >MN-FA and MN-HA key to an attacker.  We assume that the mask is fixed
> >because it is generated using the following formula:
> >
> >mask = MD5 (AAA-key || node-address || AAA-key)
> >
> >If the AAA-key is the shared secret between the MN and Home AAA server, it
> >will likely not change for the life of the MN user's subscription because
> it
> >is expensive for the Mobile IP provider to distribute the AAA-key (we
> define
> >it as the MN-AAAh key) to the MN.  Also, if the "node-address" is the MN's
> >NAI, the mask will remain constant for the life to the subscription.  In
> GSM
> >and TIA cellular networks, the root key (shared secret between the Mobile
> >Station and Authentication Center) is never changed, i.e., MS retains the
> >same root key for years (note: other session security keys are continously
> >generated from the root to ensure security).  Note: your draft proposes
> >using the MN's home IP address as the "node-address", however, based on the
> >last TSG-P meeting, I believe you were planning on changing it to the MN's
> >NAI.
> >
> >Fixed Mask Problems:
> >
> >1)  If the encryption mask remains fixed, any FA that interacts with a
> >particular MN will have the ability to recover the encryption mask for both
> >MN-FA and MN-HA key distribution.  This may not be significant for Verizon
> >Wireless initially because all the FAs will be controled by us.  But
> >eventually we may allow our subscribers to interact with Mobile IP networks
> >controlled by other companies, the government, or individuals.  Anyone with
> >access to these FAs with be able to recover the fixed encryption mask and
> >subsequently recover the MN-FA and/or MN-HA key by eavesdropping on the
> >MN-to-FA air interface.  The attack works as follows:
> >
> >The FA normally sends the MN-FA key update in an Unsolicited MN-FA key From
> >AAA Subtype message (included in the Registration Reply).  The MN-FA is
> >encoded as follows:
> >
> >Encoded MN-FA key = MN-FA key XOR Fixed Encryption Mask
> >
> >Fixed Encryption Mask = MD5 (MN-AAAh key || MN NAI || MN-AAAh key)
> >
> >The FA also recieves the MN-FA key via its AAA server.
> >
> >The FA recovers the Fixed Encryption Mask using the following:
> >
> >Fixed Encryption Mask = MN-FA key XOR (MN-FA key XOR Fixed Encryption Mask)
> >
> >By eavesdropping on any future MN-FA or MN-HA key updates on the air
> >interface, an attacker with access to any FA that interacts with the MN
> will
> >have the ability to recover either key.
> >
> >Imagine the scenarion in which Verizon Wireless allows the FBI to set up
> its
> >own Mobile IP network that interacts with our service.  Whenever a Verizon
> >Wireless subscriber accesses thier network, they save the Fixed Mask
> >associated with that subscriber.  The same thing could happen on a
> >University campus in which hackers are actually running the Mobile IP
> >network.  An individual, out of the goodness in his heart, could offer free
> >service to subscribers while they happen to be within the vacinity of his
> >network (while stealing MN-FA/MN-HA masks).
> >
> >Finally, the MN-FA key may be more important than intended for Mobile IP
> >alone.  The MN-FA key, as a shared secret between the MN and FA, can enable
> >other security services such as Radio Access Layer Encryption and Message
> >Authentication.
> >
> >2)  Because the mask is fixed, an eavesdropper on the air interface is able
> >to track changes made to the MN-FA or MN-HA key whenever the keys are
> >updated.  Consider the following:
> >
> >Encoded MN-FA key #1 = MN-FA key #1 XOR Fixed Encryption Mask
> >
> >Encoded MN-FA key #2 = MN-FA key #2 XOR Fixed Encryption Mask
> >
> >Delta MN-FA key = Encoded MN-FA key #1 XOR Encoded MN-FA key #2
> >
> >As long as the MN-FA key is a cryptographically strong secret key (randomly
> >or pseudo-randomly generated), you have the situation in which the MN-FA
> key
> >is acting as a One-time Pad for the fixed Mask!  I don't believe this was
> >your original intent.
> >
> >Because MD5 is a one-way function, I don't believe that an attacker can
> >actually recovery the MN-FA (or MN-HA) key.  However, you are leaking
> >information about the key.  A real cryptographer (not me) might be able to
> >exploit this.
> >
> >We propose the following enhancements to draft-ietf-mobileip-aaa-key-04.txt
> >to eliminate this vulnerability:
> >
> >Instead of distributing an encrypted key, we recommend that the procedure
> >utilize a key agreement scheme.  The procedure works as follows when
> >generating the MN-HA key:
> >
> >1.  The AAA server determines the "node-address" of the MN with
> node-address
> >= NAI.
> >
> >2.  The AAA server generates RAND (64 bits recommended).  RAND should be
> >randomly or pseudo-randomly generated based on RFC 1750.
> >
> >3.  The AAA server computes the following:  MN-HA key = MD5 (MN-AAAh key ||
> >MN NAI || HA IP address || RAND).
> >
> >4.  The AAA server inserts the RAND (instead of the encoded MN-HA key) into
> >the Key extension in the "RAND" field (which replaces the MN-HA Encoded Key
> >data field).  Note: the AAA server must independently delivery the MN-HA
> key
> >to the HA.
> >
> >5.  The MN computes the following:  MN-HA key = MD5 (MN-AAAh key || MN NAI
> >|| HA IP address || RAND).
> >
> >The procedure for MN-FA key generation is:
> >
> >1.  The AAA server determines the "node-address" of the MN with
> node-address
> >= NAI.
> >
> >2.  The AAA server generates RAND (64 bits recommended).
> >
> >3.  The AAA server computes the following:  MN-fA key = MD5 (MN-AAAh key ||
> >MN NAI || FA IP address || RAND).
> >
> >4.  The AAA server inserts the RAND (instead of the encoded MN-FA key) into
> >the Key extension in the "RAND" field (which replaces the MN-FA Encoded Key
> >data field).  Note: the AAA server must independently delivery the MN-FA
> key
> >to the FA.
> >
> >5.  The MN computes the following:  MN-FA key = MD5 (MN-AAAh key || MN NAI
> >|| FA IP address || RAND).
> >
> >We do not alter the structure of the Unsolicited Key extension.  We only
> >replace the Encoded key with RAND.  While RAND is only 64-bits (or even
> only
> >32-bits), the MN and Home AAA server still generate a 128-bit key.  Thus,
> we
> >reduce air interface overhead while increasing security at the same time.
> >
> >Security Considerations:
> >
> >Under our proposal, the MN-HA and MN-FA key are derived from the root
> >MN-AAAh key.  If the keys are derived based on a cryptographically secure
> >one-way function (e.g. MD5 or SHA-1), compromise of the MN-HA or MN-FA key
> >will not compromise the root MN-AAAh key.  If the root MN-AAAh key is
> >compromised, the current MN-HA or MN-FA key will be compromised only if the
> >attacker observed the RAND transmitted during the Update.  However, this is
> >also true for the existing scheme, because the MN-AAAh key is used to
> >encrypt the MN-FA or MN-HA key during the Update.
> >
> >Key agreement is not a new or unproven key distribution method.  It has
> been
> >used successfully used for years by GSM and TIA for cellular telephone
> >security.
> 


From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep 28 01:09:33 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA21576
	for <mobileip-archive@lists.ietf.org>; Fri, 28 Sep 2001 01:09:33 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id XAA22810;
	Thu, 27 Sep 2001 23:08:52 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id WAA22383;
	Thu, 27 Sep 2001 22:08:54 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8S5847B024543
	for <mobile-ip-dist@sunroof.eng.sun.com>; Thu, 27 Sep 2001 22:08:04 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8S5839P024542
	for mobile-ip-dist; Thu, 27 Sep 2001 22:08:03 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8S5807B024535
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 22:08:00 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id WAA25050
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 22:08:02 -0700 (PDT)
Received: from telesoft.indts.com ([164.164.71.52])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id WAA12357
	for <mobile-ip@sunroof.eng.sun.com>; Thu, 27 Sep 2001 22:07:58 -0700 (PDT)
Received: from indts_fs.indts.com (indts_fs [201.64.64.29])
	by telesoft.indts.com (8.8.7/8.8.7) with ESMTP id LAA21780
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 11:03:56 +0530
Received: by INDTS_FS with Internet Mail Service (5.5.2650.21)
	id <TCHS9CKY>; Fri, 28 Sep 2001 10:52:38 +0530
Message-ID: <F73B646FCC01D5118F530002B32C33724C6FEB@INDTS_FS>
From: Amit Shakya <amits@indts.com>
To: "'mobile-ip@sunroof.eng.sun.com'" <mobile-ip@sunroof.eng.sun.com>
Subject: RE: [mobile-ip] DOUBT!!
Date: Fri, 28 Sep 2001 10:52:32 +0530
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

hi Dionisios,
Thanx a lot for the reply. Yes, that was what i wanted to know. 
Regards
Amit

-----Original Message-----
From: Dionisios Gatzounas [mailto:dgat@intracom.gr]
Sent: Thursday, September 27, 2001 3:38 PM
To: Amit Shakya
Cc: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] DOUBT!!


Hello Amit,

On Thursday 27 September 2001 06:54, you wrote:
> hi
> I have a doubt regarding the implementation of FA. If a Router has only
one
> network interface and it advertises that as a care of address via Agent
> Advertisement then it will start receiving both normal packets for routing
> as well as packets to be decapsulated. Now my question is how will the
> Router know whether the packet it is receiving has to be decapsulated and
> then forwarded or forward directly ? Is my understanding of FA correct
with
> regards to this question or am i missing something?
> Regards
> Amit


source ---> encapsulator --------> decapsulator ---> destination
The Router (decapsulator) will check the Protocol Type field in the IP 
header. If this is 4 (IP in IP encapsulation) then the Router will 
decapsulate the packet and forward it to the destination.
Is this the problem or you meant something else?

Regards,
Dionisios.
-- 
------------------------------------------
Dionisios D. Gatzounas           	          
Development Programmes Department 	     
INTRACOM S.A.                       	          
254 Panepistimiou Str., Patras 26443, GREECE              	          
tel: +30 61 465168
fax: +30 61 465070
e-mail: dgat@intracom.gr
------------------------------------------


From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep 28 04:09:21 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA07484
	for <mobileip-archive@odin.ietf.org>; Fri, 28 Sep 2001 04:09:21 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id BAA03221;
	Fri, 28 Sep 2001 01:08:31 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id BAA12682;
	Fri, 28 Sep 2001 01:08:08 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8S86c7B024825
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 28 Sep 2001 01:06:38 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8S86bgk024824
	for mobile-ip-dist; Fri, 28 Sep 2001 01:06:37 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8S86U7B024817
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 01:06:31 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id BAA09972;
	Fri, 28 Sep 2001 01:06:26 -0700 (PDT)
Received: from mailgw.ipunplugged.com (217.134.88.213.host.tele1europe.se [213.88.134.217])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id BAA12405;
	Fri, 28 Sep 2001 01:06:25 -0700 (PDT)
Received: from fredrikj (hotel-14.local.ipunplugged.com [192.168.8.14])
	by mailgw.ipunplugged.com (8.9.3/8.9.3) with SMTP id KAA06645;
	Fri, 28 Sep 2001 10:06:22 +0200
From: "Fredrik Johansson" <fredrik.johansson@ipunplugged.com>
To: <mobile-ip@sunroof.eng.sun.com>,
        "Erik Nordmark" <Erik.Nordmark@eng.sun.com>
Cc: "Charles E. Perkins" <charliep@iprg.nokia.com>,
        "Pat Calhoun" <pcalhoun@diameter.org>
Subject: RE: [mobile-ip] Concerns/comments for aaa-keys and gen-key
Date: Fri, 28 Sep 2001 10:06:53 +0200
Message-ID: <MJEMJBGGCLLDLFFAHLJKEECADHAA.fredrik.johansson@ipunplugged.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
In-Reply-To: <20010927211135.G1723@charizard.diameter.org>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

>
>> But if there are other (current and future) algorithms that are used
>> it seems like there needs to be a way for the communicating parties to
>> determine which algorithm to use.
>> For instance, if 5 years from now HMAC-MD5 is not considered to be secure
>> enough, when both parties implement the NEW-BETTER-ALG they
>should be able
>> to discover that and use it instead of HMAC-MD5.

There is a way for the communicating parties to determine which algorithm
to use.

>
>If that's the case, then a new multi round trip mobile ip protocol is
>needed, since the protocol doesn't allow for negotiation.

It's true that the protocol doesn't allow for negotiation, but there is
nothing that prevents you from pointing out the NEW-BETTER-ALG when your
AAAh and MN both implement them. The AAAh is the one that tells the MN what
algorithm to use to derive the key from the key-material and what algorithm
to use with the derived key when talking to the HA/FA, i.e. it's up to the
policy of the AAAh to set the right level of security.

/Fredrik

>
>> I wonder if anybody has been thinking about periodic re-keying in
>> the RFC 2002 context - it sure seems usefulin general.
>> I need to read what the AAA docs say about re-keyeing.
>
>it states that once the lifetime has expired, keys are useless and rekey
>is mandatory.
>
>> Yep - we've had some terminology problems.
>> I think adding some definitions to aaa-keys would help here (I
>think Thomas
>> was asking for this as well).
>
>I agree.
>
>PatC



From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep 28 04:34:32 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA07704
	for <mobileip-archive@odin.ietf.org>; Fri, 28 Sep 2001 04:34:31 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id CAA25541;
	Fri, 28 Sep 2001 02:33:34 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id BAA07384;
	Fri, 28 Sep 2001 01:33:37 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8S8Wf7B024945
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 28 Sep 2001 01:32:41 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8S8Wf3e024944
	for mobile-ip-dist; Fri, 28 Sep 2001 01:32:41 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8S8Wb7B024937
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 01:32:37 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id BAA07106
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 01:32:40 -0700 (PDT)
Received: from muminmamman.lifix.fi ([195.238.204.197])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id BAA22066
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 01:32:38 -0700 (PDT)
Received: from ban by muminmamman.lifix.fi with local (Exim 3.12 #1 (Debian))
	id 15mt4X-00045A-00
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 11:32:37 +0300
Date: Fri, 28 Sep 2001 11:32:37 +0300
From: Bjorn Andersson <bjorn@lifix.fi>
To: mobile-ip@sunroof.eng.sun.com
Subject: [mobile-ip] Minor typo in draft-ietf-mobileip-rfc2002-bis-08.txt
Message-ID: <20010928113237.A15512@lifix.fi>
Mail-Followup-To: Bjorn Andersson <bjorn@lifix.fi>,
	mobile-ip@sunroof.eng.sun.com
References: <200109191106.HAA28827@ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200109191106.HAA28827@ietf.org>
User-Agent: Mutt/1.3.20i
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

There is minor typo in draft-ietf-mobileip-rfc2002-bis-08.txt.

Section 6.4, "Code Values for Mobile IP Registration Reply Messages", defines
the following error code ranges:

         0-8        Success Codes
         9-63       No allocation guidelines currently exist
         64-128     Error Codes from the Foreign Agent
         128-192    Error Codes from the Home Agent
         193-255    No allocation guidelines currently exist

The error code range for the Foreign Agent should of course be
64-127.

  Bjorn

-- 
Bjorn Andersson <bjorn@lifix.fi>                       +358 50 341 2556
Lifix Systems Oy <http://www.lifix.fi/>                 PGP id 5AFC144B
Yliopistonkatu 5, 3rd floor; FIN-00100 Helsinki


From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep 28 04:35:02 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA07716
	for <mobileip-archive@odin.ietf.org>; Fri, 28 Sep 2001 04:35:02 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id BAA11214;
	Fri, 28 Sep 2001 01:34:22 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id BAA07499;
	Fri, 28 Sep 2001 01:34:10 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8S8XN7B024964
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 28 Sep 2001 01:33:23 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8S8XNVJ024963
	for mobile-ip-dist; Fri, 28 Sep 2001 01:33:23 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from bebop.France.Sun.COM (bebop.France.Sun.COM [129.157.174.15])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8S8XI7B024956
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 01:33:19 -0700 (PDT)
Received: from lillen (lillen [129.157.212.23])
	by bebop.France.Sun.COM (8.10.2+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id f8S8XEv18099;
	Fri, 28 Sep 2001 10:33:15 +0200 (MET DST)
Date: Fri, 28 Sep 2001 10:28:42 +0200 (CEST)
From: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Subject: Re: [mobile-ip] Concerns/comments for aaa-keys and gen-key
To: Pat Calhoun <pcalhoun@diameter.org>
Cc: "Charles E. Perkins" <charliep@IPRG.nokia.com>,
        Erik Nordmark <Erik.Nordmark@eng.sun.com>,
        mobile-ip@sunroof.eng.sun.com
In-Reply-To: "Your message with ID" <20010927204724.A1723@charizard.diameter.org>
Message-ID: <Roam.SIMC.2.0.6.1001665722.1526.nordmark@bebop.france>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

> Mobile IP is a request/response protocol. Unfortunately, it doesn't lend
> itself well to negotiations. So, the AAAH (owned by the administrator) will
> have to select the algorithm and key length. If the transforms provided are
> not sufficient (e.g. hmac-md5), then some guidance would be appreciated.

Huh?
Negotiation doesn't require multiple exchanges. It is sufficient
for the sender to list which algorithms it supports (e.g. in priority
order) and the responder to pick the first one it supports in the list.

> right. again, we decided against redoing all of the work in the Diameter
> Mobile IP application. Folks MUST read the other spec anyways to build a
> system, so we didn't feel it was all that necessary to redo in this spec.

OK. This means that the aaa-diameter-mobileip spec should be listed
as a normative reference in aaa-keys.
And it has the effect that aaa-keys can't move to PS until its normative
references move. I don't know if that is what you want...

An alternative would be to make aaa-keys standalone in describing what mobileip
nodes (MN, FA, HA) need to do without actually getting into the details of
what AAA protocol is used and the encoding in that protocol. An example of how
this could look in aaa-keys:

	Section x.y: FA receiving Registration Requests

	When a FA receives a registration request from a MN, in addition to
	the message validation specified in rfc2002, the FA must verify
	 - ...
	 - ...

	Then the FA takes the information contain in (or in the x and y fields)
	in the registration request and passes them to AAA.

	If the AAA system grants access, the result is that a AAA message
	containing x, y, and z is passed to the HA.
	If the AAA system denies the request, the result is ...

	Section ...: HA receiving logical registrations from AAA

	When a MN registers the result is that the FA causes x, y, z
	to appear at the HA from the AAA. The exact encoding of this information
	depends on which AAA protocol is used.

	The HA, if addition to the verification steps specified in rfc2002,
	must verify:
	 - ...
	 - ...

I hope you get the idea.
I think taking this pass allows implementors to build
a complete MN without needing to read any AAA documents (i.e. no normative
reference) even though such documents can provide background information.
I also allows implementors to build FA and HA functionality assuming
that there is a place to plug in a AAA protocol that passes the needed
information (with the appropriate security provisions).
So I my mind this would get rid of a bunch of diameter documents 
as being normative references.

It is of course up to the WG to decide which path they want to take.

> > > The document talks about using the NAI to identify the user, which
> > > might have privacy implications. While the NAI must have a stable domain
> > > component (the part after the @ sign) in order to route to the right home
> > > AAA server, but that doesn't inherently require that the component
> > > before the @ sign be a fixed string like a user name.
> > > Has there been any privacy review of this?
> > > Are there any thoughts or proposals around using temporary IDs instead
> > > of user names before the @ sign?
> 
> These very schemes are used universally for dial-up, and the whole AAA
> protocol is modeled around this. If this is a genuine concern, it applies
> to more than just Mobile IP.

I agree it applies to more than mobile IP. Where should we have this
discussion?

  Erik



From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep 28 04:45:02 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA07792
	for <mobileip-archive@odin.ietf.org>; Fri, 28 Sep 2001 04:45:01 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id BAA14242;
	Fri, 28 Sep 2001 01:44:34 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id BAA08710;
	Fri, 28 Sep 2001 01:44:26 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8S8hb7B025103
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 28 Sep 2001 01:43:37 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8S8hacw025102
	for mobile-ip-dist; Fri, 28 Sep 2001 01:43:36 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from bebop.France.Sun.COM (bebop.France.Sun.COM [129.157.174.15])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8S8hW7B025095
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 01:43:32 -0700 (PDT)
Received: from lillen (lillen [129.157.212.23])
	by bebop.France.Sun.COM (8.10.2+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id f8S8hRv19152;
	Fri, 28 Sep 2001 10:43:27 +0200 (MET DST)
Date: Fri, 28 Sep 2001 10:38:54 +0200 (CEST)
From: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Subject: Re: [mobile-ip] Concerns/comments for aaa-keys and gen-key
To: Pat Calhoun <pcalhoun@diameter.org>
Cc: Erik Nordmark <Erik.Nordmark@eng.sun.com>,
        Fredrik Johansson <fredrik.johansson@ipunplugged.com>,
        mobile-ip@sunroof.eng.sun.com,
        Charlie Perkins <charliep@IPRG.nokia.com>
In-Reply-To: "Your message with ID" <20010927205903.D1723@charizard.diameter.org>
Message-ID: <Roam.SIMC.2.0.6.1001666334.30071.nordmark@bebop.france>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

> > It is the assertion that key material being different than keys
> > that makes the alarm bells start ringing - I think such an assertion needs
> > to be analysed by folks that are subject matter experts in the protocols
> > and algorithms used to carry the material as well as constructing
> > keys from the material.
> 
> In fact, sending key material is MUCH MORE secure than keys... not sure
> why bells are ringing... maybe someone's at your front door

I guess it is a difference in approach.
I think that constructing new security protocols (as opposed to
protocols which encapsulate and use existing security) is a darn hard
problem and I do not see how I can judge such protocols. Thus I will
defer to experts in this area.

So while carrying keying material instead of the actual keys might 
appear at first sight, I assume the security of the system actually
depends on the algorithms used to 1) protect they keying material
in transit and 2) the algorithms used to construct
keys from the keying material.

So the bells will stop ringing when either some IETF security experts 
tell me not to worry, or if the problem can be solved using an existing
security protocol.

> > This approach is quite different that the proposed 
> > draft-ietf-aaa-diameter-e2e-sec which re-uses an existing mechanism
> > (CMS) and relies on certificates (by distributing the certificate chains
> > itself). At least that doesn't seem to invent new stuff that makes my alarm
> > bells go off.
> 
> but cms is not appropriate here. the mobile node doesn't participate
> in the AAA transactions.

I didn't actually suggest using cms - I gave an example where a new security
protocol isn't invented but instead an existing wheel^H^H^H^H^Hsecurity
protocol is used.
Which existing security protocols might apply is beyond my expertise.

And just because cms is used by AAA doesn't imply that it can't be used
by other protocols (like email, mobile-ip, etc :-)

  Erik



From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep 28 04:47:44 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA07837
	for <mobileip-archive@odin.ietf.org>; Fri, 28 Sep 2001 04:47:43 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id CAA03241;
	Fri, 28 Sep 2001 02:47:00 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id BAA09045;
	Fri, 28 Sep 2001 01:47:05 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8S8kS7B025165
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 28 Sep 2001 01:46:28 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8S8kRSh025164
	for mobile-ip-dist; Fri, 28 Sep 2001 01:46:27 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from bebop.France.Sun.COM (bebop.France.Sun.COM [129.157.174.15])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8S8kN7B025157
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 01:46:24 -0700 (PDT)
Received: from lillen (lillen [129.157.212.23])
	by bebop.France.Sun.COM (8.10.2+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id f8S8kIv19449;
	Fri, 28 Sep 2001 10:46:18 +0200 (MET DST)
Date: Fri, 28 Sep 2001 10:41:46 +0200 (CEST)
From: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Subject: Re: [mobile-ip] Concerns/comments for aaa-keys and gen-key
To: Pat Calhoun <pcalhoun@diameter.org>
Cc: Erik Nordmark <Erik.Nordmark@eng.sun.com>,
        "Charles E. Perkins" <charliep@iprg.nokia.com>,
        mobile-ip@sunroof.eng.sun.com
In-Reply-To: "Your message with ID" <20010927210647.F1723@charizard.diameter.org>
Message-ID: <Roam.SIMC.2.0.6.1001666506.1719.nordmark@bebop.france>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

> While on this interoperability talk, I'd like to note that we have 4 
> independently developed implementations that successfully interoperated
> on many occasions.

Good, but that doesn't necessarily mean that the specs are clear.

I suspect that all those implementations were done by folks that participate
in the IETF - they might even have asked the authors for clarification.

The goal is to have specifications so that a newcommer actually can implement
the protocol from the spec without asking anybody any questions.

   Erik



From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep 28 05:20:00 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA08084
	for <mobileip-archive@odin.ietf.org>; Fri, 28 Sep 2001 05:19:59 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id CAA24951;
	Fri, 28 Sep 2001 02:19:20 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id CAA08696;
	Fri, 28 Sep 2001 02:19:06 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8S9Hl7B025342
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 28 Sep 2001 02:17:47 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8S9HlBE025341
	for mobile-ip-dist; Fri, 28 Sep 2001 02:17:47 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8S9Hh7B025333
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 02:17:43 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id CAA19588
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 02:17:45 -0700 (PDT)
Received: from mail.gmx.net (mail.gmx.net [213.165.64.20])
	by venus.sun.com (8.9.3+Sun/8.9.3) with SMTP id CAA08907
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 02:17:44 -0700 (PDT)
Received: (qmail 15250 invoked by uid 0); 28 Sep 2001 09:17:43 -0000
Received: from porta.predictive.de (HELO borg) (212.218.174.122)
  by mail.gmx.net (mp004-rz3) with SMTP; 28 Sep 2001 09:17:43 -0000
Message-ID: <00a801c147ff$ab95d340$550016ac@borg>
From: "cnyap" <cnyap@gmx.net>
To: <mobile-ip@sunroof.eng.sun.com>
References: <4D45BA2A58A7D3119E050008C7E69E29F7946B@trimail2.tri.sbc.com>
Subject: Re:  [mobile-ip] Heterogeneous Handover - where do i look
Date: Fri, 28 Sep 2001 11:26:33 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hi Doradla

I suppose some IP mobility companies are working on it now.
It is feasible as I have seen it running already although it only works with
RFC2002.

Cheers
Chern Nam




----- Original Message -----
From: "Doradla, Anil" <doradla@tri.sbc.com>
To: <mobile-ip@sunroof.eng.sun.com>
Sent: Friday, August 10, 2001 6:28 PM
Subject: [mobile-ip] Heterogeneous Handover - where do i look


> Coming back to the question of handover across heterogeneous wireless
> networks.  Can anyone advise me as to where i should look at?
> We are seeing a desire for handover between 802.11 and GPRS networks.  Is
> there any group looking at the feasibility of this ?
>
> Thanks in advance
>
> Anil Doradla
> SBC- Technology Resources, Inc.
> Austin, TX-78727
>
>
> -----Original Message-----
> From: James Kempf [mailto:James.Kempf@sun.com]
> Sent: Friday, August 10, 2001 3:57 AM
> To: mobile-ip@sunroof.eng.sun.com; mobile-ip@sunroof.eng.sun.com
> Cc: Peter.Dahl
> Subject: RE: [mobile-ip] Heterogeneous Handover - How Would it Work?
>
>
> Glenn,
>
> I think Raj is right on here, sorry. There are enough technical issues
> involved in getting MIP to be deployable that the MIP group really
> needs to focus on. An example is this NAT question.
>
> If there are any operational issues involved in handover between operators
> that
> need resolution, they should probably be handled in a separate working
> group, like ROAMOPS. An example of such an issue might be advertising
> access routers between operators using something like the Seamoby
> CAR discovery protocol, which is just now getting off the ground.
>
> jak
> >Raj,
> >
> >That's like saying that BGP doesn't deal with the routing policy related
to
> >business relationships between the owners of autonomous systems. You are
> >shoe-holing the group into only dealing with an enterprise - not the
> >Internet.
> >
> >-----Original Message-----
> >From: Basavaraj.Patil@nokia.com [mailto:Basavaraj.Patil@nokia.com]
> >Sent: Thursday, August 09, 2001 10:55 AM
> >To: mobile-ip
> >Cc: Peter.Dahl
> >Subject: RE: [mobile-ip] Heterogeneous Handover - How Would it Work?
> >
> >
> >Clearly, you are mixing roaming with seamless mobility across
> >heterogeneous
> >access types. The Mobile IP WG does not deal with aspects related to
> >roaming
> >agreements between operators or administrative domains. That is NOT what
> >this WG is about.
> >
> >-Basavaraj
> >
> >> -----Original Message-----
> >> From: ext Dahl, Peter [mailto:Peter.Dahl@VerizonWireless.com]
> >> Sent: Wednesday, August 08, 2001 1:53 PM
> >> To: 'mobile-ip@sunroof.eng.sun.com'
> >> Subject: RE: [mobile-ip] Heterogeneous Handover - How Would it Work?
> >>
> >>
> >> ...not forgetting cdma2000.  I am not aware of any work in
> >> 3GPP2 or IEEE,
> >> perhaps 3GPP ?
> >>
> >> Pete
> >>
> >> -----Original Message-----
> >> From: Brad Casemore [mailto:bcasemore@home.com]
> >> Sent: Wednesday, August 08, 2001 11:29 AM
> >> To: mobile-ip@sunroof.eng.sun.com
> >> Subject: RE: [mobile-ip] Heterogeneous Handover - How Would it Work?
> >>
> >>
> >> If that is the case, then WECA's WISPr is dedicated to
> >> 802.11b roaming,
> >> while the ETSI has assigned a group to address GPRS roaming.
> >> Is there a
> >> group anywhere that is looking into the technical issues
> >> associated with
> >> heterogeneous network roaming (such as between, theoretically, 802.11b
> >> WLANs and GPRS)?
> >>
> >> Brad
> >>
> >> > -----Original Message-----
> >> > From: owner-mobile-ip@sunroof.eng.sun.com [mailto:owner-mobile-
> >> > ip@sunroof.eng.sun.com] On Behalf Of James Kempf
> >> > Sent: Wednesday, August 08, 2001 2:19 AM
> >> > To: mobile-ip@sunroof.eng.sun.com; mobile-ip@sunroof.eng.sun.com
> >> > Subject: Re: [mobile-ip] Heterogeneous Handover - How Would it Work?
> >> >
> >> > Pat,
> >> >
> >> > I think they already have such a standard and I believe it
> >> only works
> >> > with GPRS.
> >> >
> >> > jak
> >> >
> >> > >Also, I believe that ETSI is working on a standard called GRX for
> >> GSM<-
> >> > >802.11
> >> > >roaming.
> >> > >
> >> > >PatC
> >> > >On Tue, Aug 07, 2001 at 09:32:58AM -0700, Dahl, Peter wrote:
> >> > >> FYI, the Wireless ISPs (WISPs) are already talking about such
> >> roaming
> >> > >> issues.
> >> > >>
> >> > >> There appear to be 2 emerging forums for these discussions, one
> >> under
> >> > the
> >> > >> auspices of WECA (http://www.weca.net) known as the WISPr group
> >> ('r'
> >> > being
> >> > >> for roaming), the other a yet to be finalized 'WISP Forum' the
> >> prime
> >> > mover
> >> > >> for which is a company in Luxembourg (www.excilan.com).
> >> > >>
> >> > >> Regards
> >> > >>
> >> > >> -----Original Message-----
> >> > >> From: James Kempf [mailto:James.Kempf@Sun.COM]
> >> > >> Sent: Tuesday, August 07, 2001 8:58 AM
> >> > >> To: mobile-ip@sunroof.eng.sun.com; mobile-ip@sunroof.eng.sun.com
> >> > >> Subject: Re: [mobile-ip] Heterogeneous Handover - How Would it
> >> Work?
> >> > >>
> >> > >>
> >> > >> >On the other hand, the home address must belong to some
> >> ISP/operator.
> >> > >> >That ISP must provide a home agent and an ip address, and a CoA
> >> when
> >> > the
> >> > >> >MN is connected to other than the home subnet. Other
> >> ISPs that are
> >> > used
> >> > >> >are only access providers, and would give the MN its
> >> CoA. This of
> >> > course
> >> > >> >would cause political problems. Who are the ISPs that
> >> are willing
> >> to
> >> > be
> >> > >> >access providers only, and who will be providing home agent and
> >> home
> >> > >> >address as well?
> >> > >> >
> >> > >>
> >> > >> This is an issue. What happens if you have one access provider on
> >> > >> one interface, say the wCDMA interface, and another on
> >> another, say
> >> > 802.11?
> >> > >> There are now in the US a growing number of 802.11 access
> >> providers,
> >> > >> and I can imagine someone with a laptop having a wCDMA modem and
> >> > >> an 802.11 card.
> >> > >>
> >> > >> Maybe something like the "roaming consortia" that have sprung up
> >> > >> around ISP access might evolve, but the protocol
> >> design/engineering
> >> > >> issue is whether there is any additional work (such as the NAI in
> >> > >> the roaming consortia example) needed to enable sharing of a home
> >> > >> address among interfaces for which different ISPs are
> >> responsible.
> >> > >>
> >> > >> Something like SUCV, that would allow an ISP to cryptographically
> >> > identify
> >> > >> to what other ISP an address belonged, might be useful in this
> >> context.
> >> > >>
> >> > >> jak
> >>
>



From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep 28 05:48:17 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA08296
	for <mobileip-archive@odin.ietf.org>; Fri, 28 Sep 2001 05:48:16 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id DAA03645;
	Fri, 28 Sep 2001 03:47:21 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id CAA11037;
	Fri, 28 Sep 2001 02:47:22 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8S9k47B025449
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 28 Sep 2001 02:46:05 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8S9k4CO025448
	for mobile-ip-dist; Fri, 28 Sep 2001 02:46:04 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8S9k17B025441
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 02:46:01 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id CAA22347
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 02:46:03 -0700 (PDT)
Received: from its-mu-earth.its.rmit.edu.au (its-mu-earth.its.rmit.edu.au [131.170.2.10])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id CAA17559
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 02:46:02 -0700 (PDT)
Received: from ems.rmit.edu.au (ems.rmit.edu.au [131.170.10.112])
	by its-mu-earth.its.rmit.edu.au (8.10.1/8.10.1/ANTI-SPAM/ANTI-RELAY/EARTH) with SMTP id f8S9jxq16692
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 19:45:59 +1000 (EST)
Received: from INET1-Message_Server by ems.rmit.edu.au
	with Novell_GroupWise; Fri, 28 Sep 2001 19:46:00 +1100
Message-Id: <sbb4d378.019@ems.rmit.edu.au>
X-Mailer: Novell GroupWise Internet Agent 5.5.5.1
Date: Fri, 28 Sep 2001 19:45:57 +1100
From: "Robin Chellappa" <e44244@ems.rmit.edu.au>
To: <cnyap@gmx.net>, <mobile-ip@sunroof.eng.sun.com>
Subject: Re:  [mobile-ip] Heterogeneous Handover - where do i look
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by sunroof.eng.sun.com id f8S9k17B025442
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 8bit

Hi Anil,
That's a field that iam interested in as well as i am in the earl stage of a Ph.d.
Would be interested in co-operation.

Cheers!
Robin.


--------------------------------------------------------
Robin Chellappa
WINET Researcher 
RMIT University
Melbourne  VIC 3001
Australia.
Ph: + 61 3 9925 9578
Fax : + 61 3 9925 5340
Email: e44244@ems.rmit.edu.au
--------------------------------------------------------

>>> cnyap@gmx.net 09/28/01 08:26pm >>>
Hi Doradla

I suppose some IP mobility companies are working on it now.
It is feasible as I have seen it running already although it only works with
RFC2002.

Cheers
Chern Nam




----- Original Message -----
From: "Doradla, Anil" <doradla@tri.sbc.com>
To: <mobile-ip@sunroof.eng.sun.com>
Sent: Friday, August 10, 2001 6:28 PM
Subject: [mobile-ip] Heterogeneous Handover - where do i look


> Coming back to the question of handover across heterogeneous wireless
> networks.  Can anyone advise me as to where i should look at?
> We are seeing a desire for handover between 802.11 and GPRS networks.  Is
> there any group looking at the feasibility of this ?
>
> Thanks in advance
>
> Anil Doradla
> SBC- Technology Resources, Inc.
> Austin, TX-78727
>
>
> -----Original Message-----
> From: James Kempf [mailto:James.Kempf@sun.com] 
> Sent: Friday, August 10, 2001 3:57 AM
> To: mobile-ip@sunroof.eng.sun.com; mobile-ip@sunroof.eng.sun.com 
> Cc: Peter.Dahl
> Subject: RE: [mobile-ip] Heterogeneous Handover - How Would it Work?
>
>
> Glenn,
>
> I think Raj is right on here, sorry. There are enough technical issues
> involved in getting MIP to be deployable that the MIP group really
> needs to focus on. An example is this NAT question.
>
> If there are any operational issues involved in handover between operators
> that
> need resolution, they should probably be handled in a separate working
> group, like ROAMOPS. An example of such an issue might be advertising
> access routers between operators using something like the Seamoby
> CAR discovery protocol, which is just now getting off the ground.
>
> jak
> >Raj,
> >
> >That's like saying that BGP doesn't deal with the routing policy related
to
> >business relationships between the owners of autonomous systems. You are
> >shoe-holing the group into only dealing with an enterprise - not the
> >Internet.
> >
> >-----Original Message-----
> >From: Basavaraj.Patil@nokia.com [mailto:Basavaraj.Patil@nokia.com] 
> >Sent: Thursday, August 09, 2001 10:55 AM
> >To: mobile-ip
> >Cc: Peter.Dahl
> >Subject: RE: [mobile-ip] Heterogeneous Handover - How Would it Work?
> >
> >
> >Clearly, you are mixing roaming with seamless mobility across
> >heterogeneous
> >access types. The Mobile IP WG does not deal with aspects related to
> >roaming
> >agreements between operators or administrative domains. That is NOT what
> >this WG is about.
> >
> >-Basavaraj
> >
> >> -----Original Message-----
> >> From: ext Dahl, Peter [mailto:Peter.Dahl@VerizonWireless.com] 
> >> Sent: Wednesday, August 08, 2001 1:53 PM
> >> To: 'mobile-ip@sunroof.eng.sun.com' 
> >> Subject: RE: [mobile-ip] Heterogeneous Handover - How Would it Work?
> >>
> >>
> >> ...not forgetting cdma2000.  I am not aware of any work in
> >> 3GPP2 or IEEE,
> >> perhaps 3GPP ?
> >>
> >> Pete
> >>
> >> -----Original Message-----
> >> From: Brad Casemore [mailto:bcasemore@home.com] 
> >> Sent: Wednesday, August 08, 2001 11:29 AM
> >> To: mobile-ip@sunroof.eng.sun.com 
> >> Subject: RE: [mobile-ip] Heterogeneous Handover - How Would it Work?
> >>
> >>
> >> If that is the case, then WECA's WISPr is dedicated to
> >> 802.11b roaming,
> >> while the ETSI has assigned a group to address GPRS roaming.
> >> Is there a
> >> group anywhere that is looking into the technical issues
> >> associated with
> >> heterogeneous network roaming (such as between, theoretically, 802.11b
> >> WLANs and GPRS)?
> >>
> >> Brad
> >>
> >> > -----Original Message-----
> >> > From: owner-mobile-ip@sunroof.eng.sun.com [mailto:owner-mobile-
> >> > ip@sunroof.eng.sun.com] On Behalf Of James Kempf
> >> > Sent: Wednesday, August 08, 2001 2:19 AM
> >> > To: mobile-ip@sunroof.eng.sun.com; mobile-ip@sunroof.eng.sun.com 
> >> > Subject: Re: [mobile-ip] Heterogeneous Handover - How Would it Work?
> >> >
> >> > Pat,
> >> >
> >> > I think they already have such a standard and I believe it
> >> only works
> >> > with GPRS.
> >> >
> >> > jak
> >> >
> >> > >Also, I believe that ETSI is working on a standard called GRX for
> >> GSM<-
> >> > >802.11
> >> > >roaming.
> >> > >
> >> > >PatC
> >> > >On Tue, Aug 07, 2001 at 09:32:58AM -0700, Dahl, Peter wrote:
> >> > >> FYI, the Wireless ISPs (WISPs) are already talking about such
> >> roaming
> >> > >> issues.
> >> > >>
> >> > >> There appear to be 2 emerging forums for these discussions, one
> >> under
> >> > the
> >> > >> auspices of WECA (http://www.weca.net) known as the WISPr group
> >> ('r'
> >> > being
> >> > >> for roaming), the other a yet to be finalized 'WISP Forum' the
> >> prime
> >> > mover
> >> > >> for which is a company in Luxembourg (www.excilan.com).
> >> > >>
> >> > >> Regards
> >> > >>
> >> > >> -----Original Message-----
> >> > >> From: James Kempf [mailto:James.Kempf@Sun.COM] 
> >> > >> Sent: Tuesday, August 07, 2001 8:58 AM
> >> > >> To: mobile-ip@sunroof.eng.sun.com; mobile-ip@sunroof.eng.sun.com 
> >> > >> Subject: Re: [mobile-ip] Heterogeneous Handover - How Would it
> >> Work?
> >> > >>
> >> > >>
> >> > >> >On the other hand, the home address must belong to some
> >> ISP/operator.
> >> > >> >That ISP must provide a home agent and an ip address, and a CoA
> >> when
> >> > the
> >> > >> >MN is connected to other than the home subnet. Other
> >> ISPs that are
> >> > used
> >> > >> >are only access providers, and would give the MN its
> >> CoA. This of
> >> > course
> >> > >> >would cause political problems. Who are the ISPs that
> >> are willing
> >> to
> >> > be
> >> > >> >access providers only, and who will be providing home agent and
> >> home
> >> > >> >address as well?
> >> > >> >
> >> > >>
> >> > >> This is an issue. What happens if you have one access provider on
> >> > >> one interface, say the wCDMA interface, and another on
> >> another, say
> >> > 802.11?
> >> > >> There are now in the US a growing number of 802.11 access
> >> providers,
> >> > >> and I can imagine someone with a laptop having a wCDMA modem and
> >> > >> an 802.11 card.
> >> > >>
> >> > >> Maybe something like the "roaming consortia" that have sprung up
> >> > >> around ISP access might evolve, but the protocol
> >> design/engineering
> >> > >> issue is whether there is any additional work (such as the NAI in
> >> > >> the roaming consortia example) needed to enable sharing of a home
> >> > >> address among interfaces for which different ISPs are
> >> responsible.
> >> > >>
> >> > >> Something like SUCV, that would allow an ISP to cryptographically
> >> > identify
> >> > >> to what other ISP an address belonged, might be useful in this
> >> context.
> >> > >>
> >> > >> jak
> >>
>



From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep 28 11:01:28 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17090
	for <mobileip-archive@odin.ietf.org>; Fri, 28 Sep 2001 11:01:27 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA24512;
	Fri, 28 Sep 2001 08:00:56 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id IAA14775;
	Fri, 28 Sep 2001 08:00:19 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8SEx57B025764
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 28 Sep 2001 07:59:05 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8SEx502025763
	for mobile-ip-dist; Fri, 28 Sep 2001 07:59:05 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8SEx17B025756
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 07:59:01 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id HAA01275
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 07:59:03 -0700 (PDT)
Received: from mgw-dax1.ext.nokia.com (mgw-dax1.ext.nokia.com [63.78.179.216])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id HAA28655
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 07:59:03 -0700 (PDT)
Received: from davir01nok.americas.nokia.com (davir01nok.americas.nokia.com [172.18.242.84])
	by mgw-dax1.ext.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f8SEx3326530
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 09:59:03 -0500 (CDT)
Received: from daebh002.NOE.Nokia.com (unverified) by davir01nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T5644a9702cac12f2540ff@davir01nok.americas.nokia.com>;
 Fri, 28 Sep 2001 09:59:02 -0500
Received: from daebe007.NOE.Nokia.com ([172.18.242.211]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.2966);
	 Fri, 28 Sep 2001 09:59:02 -0500
content-class: urn:content-classes:message
Subject: RE: [mobile-ip] New BETH Draft
Date: Fri, 28 Sep 2001 09:59:09 -0500
Message-ID: <697DAA22C5004B4596E033803A7CEF441E876D@daebe007.NOE.Nokia.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Thread-Topic: [mobile-ip] New BETH Draft
X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0
Thread-Index: AcFGsuwBLA4di7KlEdWBTABQi2X+DwBeqoGA
From: "Patil Basavaraj (NET/Dallas)" <Basavaraj.Patil@nokia.com>
To: "'James Kempf'" <James.Kempf@sun.com>, <mobile-ip@sunroof.eng.sun.com>
X-OriginalArrivalTime: 28 Sep 2001 14:59:02.0033 (UTC) FILETIME=[1C1B4810:01C1482E]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by sunroof.eng.sun.com id f8SEx17B025757
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 8bit

James,
Comments inline (prefixed BP>)

>Hi Raj,
>
>Thanx for the comments. Responses below.
>
>
>>Following this thread, I tend to agree with Hesham. I do not believe
>>it is required to advertise capabilities of FMIPv6 or BETH to the MN
>>via router advertisements. As has been discussed at length in this
>>thread the MN will know if the network supports fast HO when it
>>sends a ProxyRtrSolicit and receives an Advt as a response. And
>>similarly the network knows that an MN is capable of fast HO when
>>it receives the F-BU as a response to a ProxyRtrAdvt.
>
>The issue here is the case where an FMIPv6 MN has transitioned
>into an area where FMIPv6 is not available and only SMIPv6 is.
>The MN will continue to send out ProxyRtrSolicits, or, will
>do so at least once, presuming it gets clueful when the AR
>doesn't reply and stops trying. I suppose one gratuitous
>over the air message is OK. However, I would like to include
>the following text in the FMIPv6 spec in large, glowing, neon
>orange letters (:-)):
>
>	If the MN does not receive a response to a ProxyRtrAdv,
>	it MUST discontinue performing FMIPv6 handover,
>	assume that the AR does not support FMIPv6, and
>	revert to the standard MIPv6 handover algorithm.
>	Similarly, if the AR does not receive a F-BU in
>	response to a ProxyRtAdv, it MUST discontinue
>	performing FMIPv6 handover, assume that the MN
>	does not support FMIPv6, and revert to the standard
>	MIPv6 handover algorithm
>	
>

BP> The above text does provide some guidelines for implementations to
deal with no respones to ProxyRtr[Slct/Advt].  You may want to add that:
"A MN and an AR realize capabilities for fast handoff support only via
the
ProxyRtr[Advt/Slct] messages". 

>It is *absolutely essential* that the spec be very clear about
>this, so that implementations do not end up wasting expensive
>radio network bandwidth by sending out gratuitous radio
>traffic. It is by no means certain that implementors will do
>the right thing given the current spec. 

BP> You cannot prevent someone from building poor implementations :(
irrespective of how well the spec is written.

>I've seen cases where
>even when the protocol spec explicitly specified measures to conserve
>network bandwidth, implementations violated the spec in ways
>that resulted in wasted bandwidth. Fortunately (or perhaps
>unfortunately, since we have to put up with it on our network) it
>was for a wired network protocol. Radio spectrum is too
>expensive to waste.

BP> But you have to take into consideration spectrums that do not cost
and
are not exactly bandwidth limited as well. Optimizing the messaging
for networks where spectrum is at a premium is a good goal, but should
be used as ONE of the design criteria. 

>
>Do you agree to this change? 
>

BP> I agree. 

>> So what do
>>you do when the network performs HOs via BETH? I think you should
>>allow the MN to still send a ProxyRtrSolct as a result of some L2
>>trigger on the MN but either ignore the message if the network is
doing
>>a HO using BETH or send a NAK to the MN as a response to the
>>ProxyRtrSlct. I agree that this causes some additional signaling but
>>it keeps implementations simple (relatively) and also avoids having to
>>build new extensions or flags into router advts any more than we
already
>>have.
>>
>
>We have had this conversation before, and I simply do not think it
>is necessary to have the ProxyRtSolct every time the MN hands over.
>For the price of a single notification when the MN enters a BETH
>coverage area, you get performance that is strictly limited by
>L2 handover. If you would rather not have the notification come
>via a RtAdv, that is fine. The ProxyRtAdv will work just as well.
>With a code in the PrxyRtAdv telling the MN
>that it has entered the BETH coverage area, the MN can be notified to
suppress
>any over the air signaling. After that, the MN's handover is handled
>by BETH. When the MN is about to transition out of a BETH coverage
>area, it gets a ProxyRtAdv indicating that it should revert to
>FMIPv6 or SMIPv6 handover. The ProxyRtAdv and SolProxyRtAdv already
>have room for such a code, and it is used to notify the MN about
>certain cases w.r.t. to the handover, this is just another one.
>
>Do you see any issues with this?
>

BP> I think I can live with that :) Hope to see the new revision of the
I-D soon.

>		jak

-Basavaraj


From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep 28 11:12:22 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17278
	for <mobileip-archive@odin.ietf.org>; Fri, 28 Sep 2001 11:12:22 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA29808;
	Fri, 28 Sep 2001 08:11:32 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id IAA16880;
	Fri, 28 Sep 2001 08:10:30 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8SF9D7B025858
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 28 Sep 2001 08:09:13 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8SF9DCF025857
	for mobile-ip-dist; Fri, 28 Sep 2001 08:09:13 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from bebop.France.Sun.COM (bebop.France.Sun.COM [129.157.174.15])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8SF987B025850
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 08:09:09 -0700 (PDT)
Received: from lillen (vpn133-11.EBay.Sun.COM [129.150.133.11])
	by bebop.France.Sun.COM (8.10.2+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id f8SF94v04043;
	Fri, 28 Sep 2001 17:09:05 +0200 (MET DST)
Date: Fri, 28 Sep 2001 16:46:18 +0200 (CEST)
From: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Subject: RE: [mobile-ip] Concerns/comments for aaa-keys and gen-key
To: Christopher.Carroll@VerizonWireless.com
Cc: mobile-ip@sunroof.eng.sun.com
Message-ID: <Roam.SIMC.2.0.6.1001688378.10875.nordmark@bebop.france>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Christopher,

> I have the following comments regarding your concerns with the current
> aaa-keys procedure:
> 
> 1) Keying material is used between the MN and FA (or MN and HA) because a
> Key Agreement Protocol is used as opposed to simply encrypting and
> distributing the MN-HA or MN-FA key.  The reason for using a key agreement
> protocol is that the MN-FA link and/or MN-HA link may be over-the-air which
> is inherently more vulnerable to eavesdropping and cryptanalysis.  Please
> review the attached comments, originally sent to Charlie Perkins and Pat
> Calhoun, regarding the vulnerabilities associated with their original
> proposal to simply encrypt the MN-HA and/or MN-FA key for transmission to
> the MN.

I understand the requirement; I just wonder whether the suggested
protocols actually satisfy the security requirements.

> Key Agreement Protocols are well understood and have been used for many
> years in GSM and North American cellular/PCS networks to enable secure
> session key generation (in a symmetric/secret key system).

Has the security of those protocols been analysed in the open
literature? Do you have pointers to such analysis papers?

> Note: It is assumed that AAA links to other MIP entities (AAA, HA and FA)
> will be protected.

One of my questions was whether there was an assumption about encryption
being used to prevent evesdropping on these links, or if it is viewed
sufficient from the key agreement protocols if this communication 
is provided with integrity protection? Replay prevention or not?
(The term "protected" is a bit unspecific.)

> 2)  With regard the AAA-to-AAA, AAA-to-HA and AAA-to-FA links, 3G Wireless
> providers intend to protect these links using one of several techniques: 1)
> IPsec, 2) Linked encryption boxes, or 3) private commication links.
> Distribution of AAA keys is NOT OUR ONLY CONCERN on these links.  We intend
> to encrypt all data between the AAA and HA/FA for subscriber privacy reasons
> and other security concerns.  Assuming we intend to protect these links
> using techniques outside the scope of MIP, it is inefficient from our
> perspective to utilize a more elaborate key distribution scheme between the
> AAA and other network infrastructure components (which are controlled by the
> service providers).  In other words, we'll already have an SA established
> between these entities and don't need to deal with bootstrapping even
> another SA!
> 
> I do recognize that other implementations of MIPv4 will require more
> inherent security compliance (architecturally built-in SA establishment
> schemes) because most users/system operators will not have the security
> expertise/resources of large service providers.  I recommend that a separate
> procedure/protocol be developed to satisfy this requirement without delaying
> the implementation of the existing scheme.

There are subtly but importantly different interpretatiosn of what
you say above. Let me restate and see if you agree with either one of these:
 We know that the IETF protocols and mechanisms for securing the communication
 between FA, AAA*, and HA will not satisfy the security requirements for
 3G wireless use. But don't worry because we will use other security protocols
 to make sure we get adequate protection.
 We do need the aaa-key and related IETF documents to move forward in the 
 IETF so that we can get adequate protection for the communication 
 involving the MN.

or

 For other reasons we will be using non-IETF standard mechanisms for securing
 the communication between FA, AAA*, and HA thus we do not care
 (and perhaps also "have not analysed") the security that the internet drafts 
 propose to add for the communication between FA, AAA*, and HA.
 We do need the aaa-key and related IETF documents to move forward in the 
 IETF so that we can get adequate protection for the communication 
 involving the MN.

Does either of the above get close to being a restatement of what you said
in the paragraphs above?

  Erik



From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep 28 11:21:09 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17396
	for <mobileip-archive@odin.ietf.org>; Fri, 28 Sep 2001 11:21:08 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id JAA15390;
	Fri, 28 Sep 2001 09:20:23 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id IAA18517;
	Fri, 28 Sep 2001 08:20:18 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8SFJF7B025935
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 28 Sep 2001 08:19:15 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8SFJFs1025934
	for mobile-ip-dist; Fri, 28 Sep 2001 08:19:15 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8SFJB7B025927
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 08:19:11 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id IAA25565
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 08:19:13 -0700 (PDT)
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with SMTP id JAA26630
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 09:20:11 -0600 (MDT)
Received: (qmail 3911 invoked by uid 500); 28 Sep 2001 15:05:05 -0000
Date: Fri, 28 Sep 2001 08:05:05 -0700
From: Pat Calhoun <pcalhoun@diameter.org>
To: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Cc: Pat Calhoun <pcalhoun@diameter.org>,
        "Charles E. Perkins" <charliep@IPRG.nokia.com>,
        mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Concerns/comments for aaa-keys and gen-key
Message-ID: <20010928080505.D3848@charizard.diameter.org>
References: <20010927204724.A1723@charizard.diameter.org> <Roam.SIMC.2.0.6.1001665722.1526.nordmark@bebop.france>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <Roam.SIMC.2.0.6.1001665722.1526.nordmark@bebop.france>; from Erik.Nordmark@eng.sun.com on Fri, Sep 28, 2001 at 10:28:42AM +0200
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

On Fri, Sep 28, 2001 at 10:28:42AM +0200, Erik Nordmark wrote:
> > Mobile IP is a request/response protocol. Unfortunately, it doesn't lend
> > itself well to negotiations. So, the AAAH (owned by the administrator) will
> > have to select the algorithm and key length. If the transforms provided are
> > not sufficient (e.g. hmac-md5), then some guidance would be appreciated.
> 
> Huh?
> Negotiation doesn't require multiple exchanges. It is sufficient
> for the sender to list which algorithms it supports (e.g. in priority
> order) and the responder to pick the first one it supports in the list.

then that's not really negotiation, but rather listing the supported algorithms.
If the AAAH didn't like the list, it cannot get into a bidding war with the 
client. That's what I consider negotiation.

sorry I misunderstood.

> 
> > right. again, we decided against redoing all of the work in the Diameter
> > Mobile IP application. Folks MUST read the other spec anyways to build a
> > system, so we didn't feel it was all that necessary to redo in this spec.
> 
> OK. This means that the aaa-diameter-mobileip spec should be listed
> as a normative reference in aaa-keys.
> And it has the effect that aaa-keys can't move to PS until its normative
> references move. I don't know if that is what you want...

not sure there is any way around this one... I'm comfortable with it.

> An alternative would be to make aaa-keys standalone in describing what mobileip
> nodes (MN, FA, HA) need to do without actually getting into the details of
> what AAA protocol is used and the encoding in that protocol. An example of how
> this could look in aaa-keys:
> 
> 	Section x.y: FA receiving Registration Requests
> 
> 	When a FA receives a registration request from a MN, in addition to
> 	the message validation specified in rfc2002, the FA must verify
> 	 - ...
> 	 - ...
> 
> 	Then the FA takes the information contain in (or in the x and y fields)
> 	in the registration request and passes them to AAA.
> 
> 	If the AAA system grants access, the result is that a AAA message
> 	containing x, y, and z is passed to the HA.
> 	If the AAA system denies the request, the result is ...
> 
> 	Section ...: HA receiving logical registrations from AAA
> 
> 	When a MN registers the result is that the FA causes x, y, z
> 	to appear at the HA from the AAA. The exact encoding of this information
> 	depends on which AAA protocol is used.
> 
> 	The HA, if addition to the verification steps specified in rfc2002,
> 	must verify:
> 	 - ...
> 	 - ...
> 
> I hope you get the idea.

yes, but personally prefer the former (don't know what the rest of the WG think).

> I think taking this pass allows implementors to build
> a complete MN without needing to read any AAA documents (i.e. no normative
> reference) even though such documents can provide background information.
> I also allows implementors to build FA and HA functionality assuming
> that there is a place to plug in a AAA protocol that passes the needed
> information (with the appropriate security provisions).
> So I my mind this would get rid of a bunch of diameter documents 
> as being normative references.
> 
> It is of course up to the WG to decide which path they want to take.

right

> 
> > > > The document talks about using the NAI to identify the user, which
> > > > might have privacy implications. While the NAI must have a stable domain
> > > > component (the part after the @ sign) in order to route to the right home
> > > > AAA server, but that doesn't inherently require that the component
> > > > before the @ sign be a fixed string like a user name.
> > > > Has there been any privacy review of this?
> > > > Are there any thoughts or proposals around using temporary IDs instead
> > > > of user names before the @ sign?
> > 
> > These very schemes are used universally for dial-up, and the whole AAA
> > protocol is modeled around this. If this is a genuine concern, it applies
> > to more than just Mobile IP.
> 
> I agree it applies to more than mobile IP. Where should we have this
> discussion?

We've had these in roamops 5 years ago. We could revive that WG if need be.

PatC


From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep 28 11:29:37 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17575
	for <mobileip-archive@odin.ietf.org>; Fri, 28 Sep 2001 11:29:37 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA09419;
	Fri, 28 Sep 2001 08:28:53 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id IAA19175;
	Fri, 28 Sep 2001 08:23:24 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8SFMK7B025995
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 28 Sep 2001 08:22:20 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8SFMKFD025994
	for mobile-ip-dist; Fri, 28 Sep 2001 08:22:20 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8SFMG7B025986
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 08:22:16 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id IAA05561;
	Fri, 28 Sep 2001 08:22:18 -0700 (PDT)
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id JAA28183;
	Fri, 28 Sep 2001 09:23:14 -0600 (MDT)
Received: from mira-sjc5-7.cisco.com (mira-sjc5-7.cisco.com [171.71.163.27])
	by sj-msg-core-1.cisco.com (8.11.6/8.9.1) with ESMTP id f8SFMDG26703;
	Fri, 28 Sep 2001 08:22:13 -0700 (PDT)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-7.cisco.com (Mirapoint)
	with ESMTP id AAU05147;
	Fri, 28 Sep 2001 08:22:12 -0700 (PDT)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id IAA02402; Fri, 28 Sep 2001 08:22:12 -0700 (PDT)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15284.38307.873861.584422@thomasm-u1.cisco.com>
Date: Fri, 28 Sep 2001 08:22:11 -0700 (PDT)
To: mobile-ip@sunroof.eng.sun.com
Cc: Michael Thomas <mat@cisco.com>,
        Fredrik Johansson <fredrik.johansson@ipunplugged.com>,
        Erik.Nordmark@eng.sun.com, Charlie Perkins <charliep@IPRG.nokia.com>,
        Pat Calhoun <pcalhoun@diameter.org>
Subject: Re: [mobile-ip] Concerns/comments for aaa-keys and gen-key
In-Reply-To: <20010927205547.C1723@charizard.diameter.org>
References: <MJEMJBGGCLLDLFFAHLJKAEHFDGAA.fredrik.johansson@ipunplugged.com>
	<Roam.SIMC.2.0.6.1001495690.1688.nordmark@bebop.france>
	<15282.3298.522332.579900@thomasm-u1.cisco.com>
	<20010927205547.C1723@charizard.diameter.org>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Pat Calhoun writes:
 > > Why should AAA not be able to key other 
 > >    protocols as well? How many specialized AAA key distribution
 > >    protocols will there be? Will there be a sufficient amount
 > >    of review by clueful security people to make certain that
 > >    stupid mistakes are not made? Has anybody considered that
 > >    there may be significant wheel-reinvention going on here
 > >    (cf Kerberos).
 > > 
 > >    My feeling is that if this is done at all, it should
 > >    be done in a new working group and most definitely
 > >    under the security AD's watch.
 > 
 > Let me see... scrap the work, and start over with new folks... 
 > 
 > very constructive. 

   Nobody's said anything about starting over. I notice
   that you don't address my main concern of why *key
   distribution* is being pursued in MIP. It's not even
   in the AAA charter, let alone the MIP charter.

 > How about we review the work, and then comment.

   Fine. This working group has taken a drubbing
   on the security front for something that was 
   clearly in its charter: securing binding updates.
   This was largely not its fault, and just goes to
   prove the obvious: security is hard. It is 
   incomprehensible to me that this working group
   should attempt to take on the task of AAA based 
   key distribution. If that is a useful concept
   at all, it clearly has further applicability 
   than just keying a few specialized security 
   associations in a one-off, poorly reviewed
   manner.

   FWIW, I might even support a properly chartered
   effort, especially if were simpler/lighter
   weight than the other two suspects.

		Mike



From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep 28 11:30:21 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17594
	for <mobileip-archive@odin.ietf.org>; Fri, 28 Sep 2001 11:30:20 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA09423;
	Fri, 28 Sep 2001 08:28:53 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id IAA19176;
	Fri, 28 Sep 2001 08:23:24 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8SFMP7B026007
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 28 Sep 2001 08:22:25 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8SFMOTD026006
	for mobile-ip-dist; Fri, 28 Sep 2001 08:22:24 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8SFMJ7B025993
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 08:22:19 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id IAA05569
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 08:22:21 -0700 (PDT)
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by venus.sun.com (8.9.3+Sun/8.9.3) with SMTP id IAA23814
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 08:22:21 -0700 (PDT)
Received: (qmail 3932 invoked by uid 500); 28 Sep 2001 15:08:15 -0000
Date: Fri, 28 Sep 2001 08:08:15 -0700
From: Pat Calhoun <pcalhoun@diameter.org>
To: Erik Nordmark <Erik.Nordmark@eng.sun.com>
Cc: Pat Calhoun <pcalhoun@diameter.org>,
        Fredrik Johansson <fredrik.johansson@ipunplugged.com>,
        mobile-ip@sunroof.eng.sun.com,
        Charlie Perkins <charliep@IPRG.nokia.com>
Subject: Re: [mobile-ip] Concerns/comments for aaa-keys and gen-key
Message-ID: <20010928080815.E3848@charizard.diameter.org>
References: <20010927205903.D1723@charizard.diameter.org> <Roam.SIMC.2.0.6.1001666334.30071.nordmark@bebop.france>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <Roam.SIMC.2.0.6.1001666334.30071.nordmark@bebop.france>; from Erik.Nordmark@eng.sun.com on Fri, Sep 28, 2001 at 10:38:54AM +0200
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

> So while carrying keying material instead of the actual keys might 
> appear at first sight, I assume the security of the system actually
> depends on the algorithms used to 1) protect they keying material
> in transit and 2) the algorithms used to construct
> keys from the keying material.

The keying material doesn't need to be protected. Both end points have a 
known secret key, and an algorithm. The actual key used is derived from the keying
material.

yes, the algorithms used to construct the key must be cryptographically strong.

> So the bells will stop ringing when either some IETF security experts 
> tell me not to worry, or if the problem can be solved using an existing
> security protocol.

Can we get a security review, please?

> I didn't actually suggest using cms - I gave an example where a new security
> protocol isn't invented but instead an existing wheel^H^H^H^H^Hsecurity
> protocol is used.
> Which existing security protocols might apply is beyond my expertise.
> 
> And just because cms is used by AAA doesn't imply that it can't be used
> by other protocols (like email, mobile-ip, etc :-)

but one size fits all doesn't always exist. btw, we aren't inventing anything
new here. As others stated on this thread, the mechanism described is widely used
in cellular systems today.

PatC


From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep 28 11:33:38 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17659
	for <mobileip-archive@odin.ietf.org>; Fri, 28 Sep 2001 11:33:37 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA11758;
	Fri, 28 Sep 2001 08:32:50 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id IAA22094;
	Fri, 28 Sep 2001 08:31:51 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8SFUM7B026214
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 28 Sep 2001 08:30:22 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8SFUMJN026213
	for mobile-ip-dist; Fri, 28 Sep 2001 08:30:22 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8SFUI7B026206
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 08:30:18 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id IAA21552
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 08:30:21 -0700 (PDT)
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by patan.sun.com (8.9.3+Sun/8.9.3) with SMTP id JAA25046
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 09:30:09 -0600 (MDT)
Received: (qmail 3978 invoked by uid 500); 28 Sep 2001 15:16:14 -0000
Date: Fri, 28 Sep 2001 08:16:14 -0700
From: Pat Calhoun <pcalhoun@diameter.org>
To: Michael Thomas <mat@cisco.com>
Cc: mobile-ip@sunroof.eng.sun.com,
        Fredrik Johansson <fredrik.johansson@ipunplugged.com>,
        Erik.Nordmark@eng.sun.com, Charlie Perkins <charliep@IPRG.nokia.com>,
        Pat Calhoun <pcalhoun@diameter.org>
Subject: Re: [mobile-ip] Concerns/comments for aaa-keys and gen-key
Message-ID: <20010928081614.F3848@charizard.diameter.org>
References: <MJEMJBGGCLLDLFFAHLJKAEHFDGAA.fredrik.johansson@ipunplugged.com> <Roam.SIMC.2.0.6.1001495690.1688.nordmark@bebop.france> <15282.3298.522332.579900@thomasm-u1.cisco.com> <20010927205547.C1723@charizard.diameter.org> <15284.38307.873861.584422@thomasm-u1.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <15284.38307.873861.584422@thomasm-u1.cisco.com>; from mat@cisco.com on Fri, Sep 28, 2001 at 08:22:11AM -0700
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

>  > Let me see... scrap the work, and start over with new folks... 
>  > 
>  > very constructive. 
> 
>    Nobody's said anything about starting over. I notice
>    that you don't address my main concern of why *key
>    distribution* is being pursued in MIP. It's not even
>    in the AAA charter, let alone the MIP charter.

ok... perhaps I misunderstood, but it sure sounded that way to
me. As some folks (including the IESG) have repeatedly mentioned,
don't expect the security area to secure every other WG's protocols.
That will not happen. They will, however, lend a hand in security
reviews.

I believe that's what we are asking for here. Creating a whole new
WG to look at this problem will delay the work, and waste engineering
resources. We don't need hundreds of folks to look at it (but if they have
time, they are certainly welcomed to do so in the MIP WG), just a review
to get the document out to RFC-dom.

btw, creating keys based on key material is not reinventing the wheel.

We just need a security review.

> 
>  > How about we review the work, and then comment.
> 
>    Fine. This working group has taken a drubbing
>    on the security front for something that was 
>    clearly in its charter: securing binding updates.

apples != oranges. I was never involved in the binding 
updates... have for a long time stated this doesn't scale.

Please don't bundle me in that work.

>    This was largely not its fault, and just goes to
>    prove the obvious: security is hard. It is 
>    incomprehensible to me that this working group
>    should attempt to take on the task of AAA based 
>    key distribution. If that is a useful concept
>    at all, it clearly has further applicability 
>    than just keying a few specialized security 
>    associations in a one-off, poorly reviewed
>    manner.

hmmmm.... the draft was recently modified due to comments
following a security review... so poorly reviewed is 
perhaps not the correct term here. Not reviewed by folks
you'd prefer may be more adequate.

PatC


From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep 28 11:54:08 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18166
	for <mobileip-archive@odin.ietf.org>; Fri, 28 Sep 2001 11:54:07 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id JAA18325;
	Fri, 28 Sep 2001 09:53:19 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id IAA28622;
	Fri, 28 Sep 2001 08:53:19 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8SFq57B026353
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 28 Sep 2001 08:52:05 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8SFq5lB026352
	for mobile-ip-dist; Fri, 28 Sep 2001 08:52:05 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8SFq27B026345
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 08:52:02 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id IAA02676
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 08:52:04 -0700 (PDT)
Received: from tholian.securitydynamics.com (mail.rsasecurity.com [204.167.112.129])
	by patan.sun.com (8.9.3+Sun/8.9.3) with SMTP id JAA16856
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 09:51:53 -0600 (MDT)
Received: from sdtihq24.securitydynamics.com by tholian.securitydynamics.com
          via smtpd (for [192.18.98.43]) with SMTP; 28 Sep 2001 15:49:01 UT
Received: from ebola.securitydynamics.com (ebola.securid.com [192.168.7.4])
	by sdtihq24.securid.com (Pro-8.9.3/Pro-8.9.3) with ESMTP id LAA10527
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 11:51:59 -0400 (EDT)
Received: from spirit.dynas.se (localhost [127.0.0.1])
	by ebola.securitydynamics.com (8.9.3+Sun/8.9.1) with SMTP id LAA16666
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 11:51:57 -0400 (EDT)
Received: (qmail 6540 invoked from network); 28 Sep 2001 15:51:56 -0000
Received: from sjosefsson-pc.d.dynas.se (172.16.13.115)
  by spirit.dynas.se with SMTP; 28 Sep 2001 15:51:56 -0000
To: mobile-ip@sunroof.eng.sun.com
Subject: [mobile-ip] Strawman generic authentication framework for Mobile IP
From: Simon Josefsson <sjosefsson@dynas.se>
Date: Fri, 28 Sep 2001 17:52:13 +0200
Message-ID: <m3u1xngvo2.fsf@sjosefsson-pc.d.dynas.se>
Lines: 142
User-Agent: Gnus/5.090004 (Oort Gnus v0.04) Emacs/21.0.106
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

(Resent because of mailing list subscription address problems.)

The discussion in the "Concerns/comments for aaa-keys and gen-key"
thread mentioned a multi round trip Mobile IP protocol, for
negotiation authentication algorithm/parameters.  This is more or less
what I've been thinking about for the past few days.  This would allow
for non-AAA/Diameter solutions within Mobile IP which I believe there
are applications for.

I'm including my outline of how this should work below... any comments
most welcome, in particular on how this would affect Mobile IP
implementations since I am no expert on Mobile IP.

Thanks,
Simon Josefsson
RSA Security

Strawman generic authentication framework for Mobile IP
-------------------------------------------------------

The purpose of this note is to explore how existing authentication
methods can be used directly in Mobile IP.  For example, how TLS, EAP,
SASL or CHAP could be used directly in Mobile IP.

The goal is to be able to provide user (or device) authentication of
the Mobile Node to a Foreign Agent or Home Agent within the Mobile IP
protocl
     packets, one for the Home Agent, one for the Foreign Agent and
     one for the Mobile Node.

     However, the way in which the Authenticator packets are exchange
     is not changed.  Only a generic packet format is defined, but a
     generic interaction description is not included.  This "generic
     interaction description" should include how the authentication
     mechanism can signal "continue", "abort" and "ol (the Registration Request and Registration Response packets),
and optionally establish keying material for IP encryption.

A side effect of this is that Mobile IP is enhanced with a security
framework that is able to negotiate the algorithm to use, instead of
the current situation where Mobile Nodes, Foreign Agents and Home
Agents need to be setup with this information in advance (or somehow
use Diameter for this).

We begin by identifying some problems:
--------------------------------------

   * Mobile IP does not obviously describe how authentication
     mechanisms that need more than a simple two round packet exchange
     can be used in Mobile IP. (RFC 2002 and Son-of-RFC2002.)  This is
     the main problem we address.

   * The Mobile IP Challenge/Response Extensions (RFC 3012) seems to
     be an attempt to make the authentication in Mobile IP more
     generic.  This is accomplished by using the same packet format
     for authentication of any entity, instead of using speciasuccess" to the
     other entity.  Only "abort" and "success" is possible now, using
     the base RFC 2002 spec.

     The Generalized Key Distribution Extension is similar, it only
     describes a generic packet format without discussing a generic
     way in which the packets can be used.

Outline of suggested specification:
-----------------------------------

A specification may introduce new Mobile IP error codes that should be
used as indicators that the other entity that additional authenticator
packets needs to be exchanges before it can complete.  Examples:

   Registration denied by the foreign agent:

...
       89 Foreign Agent needs more authentication data before it can proceed

   Registration denied by the home agent:

...
      142 Home Agent needs more authentication data before it can proceed.

The individual authenticator mechanisms could be allocated in the
0-255 SPI IANA space as defined in RFC 3012, examples:


SPI Values for the Mobile IP Reserved SPIs:

	0 Reserved                                            [RFC3012]
        1 Reserved                                            [RFC3012]
        2 CHAP                                                [RFC3012]
	3 TLS
	4 EAP
	5 PKI
	...

(Where 5 could be ideas similar to what is in
draft-jacobs-mobileip-pki-auth-03.txt.)

Example:
--------

This is an example of how TLS can be used to authenticate a user to a
Mobileenticator:
					TLS Server Finished, ...}

Open Issues:
------------

One needs to investigate the need for a CHALLENGE extension such as
the one used in RFC 3012 to prevent replay-attacks of the registration
requests, or at least a identification scheme to make it possible to
separate between multiple authentication attempts.

It is not clear to me how sending multiple registration requests would
affect Mobile IP implem IP infrastructure.  Note that the TLS_SPI of 4 and Continuation
Error Code of 137 are just examples, they are not official in any way.

        Mobile Node                            Home Agent

{Mobile IP Registration Request:
Mobile-Home Auth Extension:
SPI=4 (TLS_SPI), Authenticator:
TLS Client Hello, ...}

                                        {Mobile IP Registration Reply:
                                        Code=137 (Continue Authentication)
					Mobile-Home Auth Extension:
					SPI=4 (TLS_SPI), Authenticator:
					TLS Server Hello, ...}

{Mobile IP Registration Request:
Mobile-Home Auth Extension:
SPI=4 (TLS_SPI), Authenticator:
TLS Client Key Exchange, ...}
                                    .
                                    .
                                    .

                                        {Mobile IP Registration Reply:
                                        Code=0 (Registration Accepted)
					Mobile-Home Auth Extension:
					SPI=4 (TLS_SPI), Authentations, especially how the Foreign Agent
would react.  Maybe the approach above interacts badly with the design
of Mobile IP.



From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep 28 12:15:56 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAB18720
	for <mobileip-archive@odin.ietf.org>; Fri, 28 Sep 2001 12:15:56 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id JAA03384;
	Fri, 28 Sep 2001 09:14:22 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA04586;
	Fri, 28 Sep 2001 09:10:25 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8SG9H7B026523
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 28 Sep 2001 09:09:18 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8SG9HKR026522
	for mobile-ip-dist; Fri, 28 Sep 2001 09:09:17 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8SG9D7B026515
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 09:09:14 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA07093
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 09:09:16 -0700 (PDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA24210
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 10:10:04 -0600 (MDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id JAA00263;
	Fri, 28 Sep 2001 09:08:38 -0700 (PDT)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f8SG8cI09655;
	Fri, 28 Sep 2001 09:08:38 -0700
X-mProtect:  Fri, 28 Sep 2001 09:08:38 -0700 Nokia Silicon Valley Messaging Protection
Received: from charliep.iprg.nokia.com (205.226.2.89, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpdz8Js8a; Fri, 28 Sep 2001 09:08:36 PDT
Message-ID: <3BB4A085.CCBEF66F@iprg.nokia.com>
Date: Fri, 28 Sep 2001 09:08:37 -0700
From: "Charles E. Perkins" <charliep@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Pat Calhoun <pcalhoun@diameter.org>
CC: mobile-ip@sunroof.eng.sun.com
Subject: [mobile-ip] Scalability of Binding Updates
References: <MJEMJBGGCLLDLFFAHLJKAEHFDGAA.fredrik.johansson@ipunplugged.com> <Roam.SIMC.2.0.6.1001495690.1688.nordmark@bebop.france> <15282.3298.522332.579900@thomasm-u1.cisco.com> <20010927205547.C1723@charizard.diameter.org> <15284.38307.873861.584422@t
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hello Pat,

Pat Calhoun wrote:

> apples != oranges. I was never involved in the binding
> updates... have for a long time stated this doesn't scale.

It seems to me that there is more than one aspect of scalability
that is important here.  In order to have scalable routing, we
need to have Binding Updates.  More recently the task has been
given to us to develop scalable key exchange techniques.

When that's accomplished, I reckon we will see that mobility
management is more scalable, not less scalable, in all the
aspects of interest.

Regards,
Charlie P.


From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep 28 12:21:09 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18806
	for <mobileip-archive@odin.ietf.org>; Fri, 28 Sep 2001 12:21:08 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id JAA06282;
	Fri, 28 Sep 2001 09:19:33 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA06224;
	Fri, 28 Sep 2001 09:13:53 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8SGD57B026570
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 28 Sep 2001 09:13:05 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8SGD57s026569
	for mobile-ip-dist; Fri, 28 Sep 2001 09:13:05 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8SGD17B026559
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 09:13:01 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id JAA17518
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 09:13:03 -0700 (PDT)
Received: from tholian.securitydynamics.com (mail.rsasecurity.com [204.167.112.129])
	by venus.sun.com (8.9.3+Sun/8.9.3) with SMTP id JAA27684
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 09:13:02 -0700 (PDT)
Received: from sdtihq24.securitydynamics.com by tholian.securitydynamics.com
          via smtpd (for [192.9.25.5]) with SMTP; 28 Sep 2001 16:10:00 UT
Received: from ebola.securitydynamics.com (ebola.securid.com [192.168.7.4])
	by sdtihq24.securid.com (Pro-8.9.3/Pro-8.9.3) with ESMTP id MAA18840
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 12:13:01 -0400 (EDT)
Received: from spirit.dynas.se (localhost [127.0.0.1])
	by ebola.securitydynamics.com (8.9.3+Sun/8.9.1) with SMTP id MAA20014
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 12:13:00 -0400 (EDT)
Received: (qmail 7669 invoked from network); 28 Sep 2001 16:12:59 -0000
Received: from sjosefsson-pc.d.dynas.se (172.16.13.115)
  by spirit.dynas.se with SMTP; 28 Sep 2001 16:12:59 -0000
To: mobile-ip@sunroof.eng.sun.com
Subject: [mobile-ip] Re: Strawman generic authentication framework for Mobile IP
References: <m3u1xngvo2.fsf@sjosefsson-pc.d.dynas.se>
From: Simon Josefsson <sjosefsson@dynas.se>
Date: Fri, 28 Sep 2001 18:13:15 +0200
In-Reply-To: <m3u1xngvo2.fsf@sjosefsson-pc.d.dynas.se> (Simon Josefsson's
 message of "Fri, 28 Sep 2001 15:52:13 GMT")
Message-ID: <m3d74bguoz.fsf@sjosefsson-pc.d.dynas.se>
Lines: 133
User-Agent: Gnus/5.090004 (Oort Gnus v0.04) Emacs/21.0.106
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Simon Josefsson <sjosefsson@dynas.se> writes:

> (Resent because of mailing list subscription address problems.)

The post got completely garbled as well... I'm trying again below.

Regards Simon, RSA Security

Strawman generic authentication framework for Mobile IP
-------------------------------------------------------

The purpose of this note is to explore how existing authentication
methods can be used directly in Mobile IP.  For example, how TLS, EAP,
SASL or CHAP could be used directly in Mobile IP.

The goal is to be able to provide user (or device) authentication of
the Mobile Node to a Foreign Agent or Home Agent within the Mobile IP
protocol (the Registration Request and Registration Response packets),
and optionally establish keying material for IP encryption.

A side effect of this is that Mobile IP is enhanced with a security
framework that is able to negotiate the algorithm to use, instead of
the current situation where Mobile Nodes, Foreign Agents and Home
Agents need to be setup with this information in advance (or somehow
use Diameter for this).

We begin by identifying some problems:
--------------------------------------

   * Mobile IP does not obviously describe how authentication
     mechanisms that need more than a simple two round packet exchange
     can be used in Mobile IP. (RFC 2002 and Son-of-RFC2002.)  This is
     the main problem we address.

   * The Mobile IP Challenge/Response Extensions (RFC 3012) seems to
     be an attempt to make the authentication in Mobile IP more
     generic.  This is accomplished by using the same packet format
     for authentication of any entity, instead of using special
     packets, one for the Home Agent, one for the Foreign Agent and
     one for the Mobile Node.

     However, the way in which the Authenticator packets are exchange
     is not changed.  Only a generic packet format is defined, but a
     generic interaction description is not included.  This "generic
     interaction description" should include how the authentication
     mechanism can signal "continue", "abort" and "success" to the
     other entity.  Only "abort" and "success" is possible now, using
     the base RFC 2002 spec.

     The Generalized Key Distribution Extension is similar, it only
     describes a generic packet format without discussing a generic
     way in which the packets can be used.

Outline of suggested specification:
-----------------------------------

A specification may introduce new Mobile IP error codes that should be
used as indicators that the other entity that additional authenticator
packets needs to be exchanges before it can complete.  Examples:

   Registration denied by the foreign agent:

...
       89 Foreign Agent needs more authentication data before it can proceed

   Registration denied by the home agent:

...
      142 Home Agent needs more authentication data before it can proceed.

The individual authenticator mechanisms could be allocated in the
0-255 SPI IANA space as defined in RFC 3012, examples:


SPI Values for the Mobile IP Reserved SPIs:

	0 Reserved                                            [RFC3012]
        1 Reserved                                            [RFC3012]
        2 CHAP                                                [RFC3012]
	3 TLS
	4 EAP
	5 PKI
	...

(Where 5 could be ideas similar to what is in
draft-jacobs-mobileip-pki-auth-03.txt.)

Example:
--------

This is an example of how TLS can be used to authenticate a user to a
Mobile IP infrastructure.  Note that the TLS_SPI of 4 and Continuation
Error Code of 137 are just examples, they are not official in any way.

        Mobile Node                            Home Agent

{Mobile IP Registration Request:
Mobile-Home Auth Extension:
SPI=4 (TLS_SPI), Authenticator:
TLS Client Hello, ...}

                                        {Mobile IP Registration Reply:
                                        Code=137 (Continue Authentication)
					Mobile-Home Auth Extension:
					SPI=4 (TLS_SPI), Authenticator:
					TLS Server Hello, ...}

{Mobile IP Registration Request:
Mobile-Home Auth Extension:
SPI=4 (TLS_SPI), Authenticator:
TLS Client Key Exchange, ...}
                                    .
                                    .
                                    .

                                        {Mobile IP Registration Reply:
                                        Code=0 (Registration Accepted)
					Mobile-Home Auth Extension:
					SPI=4 (TLS_SPI), Authenticator:
					TLS Server Finished, ...}

Open Issues:
------------

One needs to investigate the need for a CHALLENGE extension such as
the one used in RFC 3012 to prevent replay-attacks of the registration
requests, or at least a identification scheme to make it possible to
separate between multiple authentication attempts.

It is not clear to me how sending multiple registration requests would
affect Mobile IP implementations, especially how the Foreign Agent
would react.  Maybe the approach above interacts badly with the design
of Mobile IP.



From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep 28 13:24:44 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20250
	for <mobileip-archive@odin.ietf.org>; Fri, 28 Sep 2001 13:24:43 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA12605;
	Fri, 28 Sep 2001 10:23:46 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id KAA26524;
	Fri, 28 Sep 2001 10:20:02 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8SHIk7B026877
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 28 Sep 2001 10:18:46 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8SHIk0A026876
	for mobile-ip-dist; Fri, 28 Sep 2001 10:18:46 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from eastmail1.East.Sun.COM (eastmail1.East.Sun.COM [129.148.1.240])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8SHIi7B026869
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 10:18:44 -0700 (PDT)
Received: from onion.east.sun.com (onion.East.Sun.COM [129.148.174.110])
	by eastmail1.East.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id NAA04267
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 13:18:46 -0400 (EDT)
Received: (from glass@localhost)
	by onion.east.sun.com (8.9.3+Sun/8.9.3) id NAA06007
	for mobile-ip@sunroof.eng.sun.com; Fri, 28 Sep 2001 13:19:16 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8S8lG7B025178
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 01:47:16 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id BAA09078
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 01:47:18 -0700 (PDT)
Received: from tholian.securitydynamics.com (mail.rsasecurity.com [204.167.112.129])
	by venus.sun.com (8.9.3+Sun/8.9.3) with SMTP id BAA27792
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 01:47:16 -0700 (PDT)
Received: from sdtihq24.securid.com by tholian.securitydynamics.com
          via smtpd (for [192.9.25.5]) with SMTP; 28 Sep 2001 08:44:15 UT
Received: from ebola.securitydynamics.com (ebola.securid.com [192.168.7.4])
	by sdtihq24.securid.com (Pro-8.9.3/Pro-8.9.3) with ESMTP id EAA10967
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 04:47:16 -0400 (EDT)
Received: from spirit.dynas.se (localhost [127.0.0.1])
	by ebola.securitydynamics.com (8.9.3+Sun/8.9.1) with SMTP id EAA07271
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 04:47:14 -0400 (EDT)
Received: (qmail 29596 invoked from network); 28 Sep 2001 08:47:13 -0000
Received: from sjosefsson-pc.d.dynas.se (172.16.13.115)
  by spirit.dynas.se with SMTP; 28 Sep 2001 08:47:13 -0000
To: mobile-ip@sunroof.eng.sun.com
Subject: [mobile-ip] Strawman generic authentication framework for Mobile IP
From: Simon Josefsson <sjosefsson@rsasecurity.com>
Date: Fri, 28 Sep 2001 10:47:28 +0200
Message-ID: <m3k7yjpuqn.fsf@sjosefsson-pc.d.dynas.se>
Lines: 139
User-Agent: Gnus/5.090004 (Oort Gnus v0.04) Emacs/21.0.106
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

The discussion in the "Concerns/comments for aaa-keys and gen-key"
thread mentioned a multi round trip Mobile IP protocol, for
negotiation authentication algorithm/parameters.  This is more or less
what I've been thinking about for the past few days.  This would allow
for non-AAA/Diameter solutions within Mobile IP which I believe there
are applications for.

I'm including my outline of how this should work below... any comments
most welcome, in particular on how this would affect Mobile IP
implementations since I am no expert on Mobile IP.

Thanks,
Simon

Strawman generic authentication framework for Mobile IP
-------------------------------------------------------

The purpose of this note is to explore how existing authentication
methods can be used directly in Mobile IP.  For example, how TLS, EAP,
SASL or CHAP could be used directly in Mobile IP.

The goal is to be able to provide user (or device) authentication of
the Mobile Node to a Foreign Agent or Home Agent within the Mobile IP
protocol (the Registration Request and Registration Response packets),
and optionally establish keying material for IP encryption.

A side effect of this is that Mobile IP is enhanced with a security
framework that is able to negotiate the algorithm to use, instead of
the current situation where Mobile Nodes, Foreign Agents and Home
Agents need to be setup with this information in advance (or somehow
use Diameter for this).

We begin by identifying some problems:
--------------------------------------

   * Mobile IP does not obviously describe how authentication
     mechanisms that need more than a simple two round packet exchange
     can be used in Mobile IP. (RFC 2002 and Son-of-RFC2002.)  This is
     the main problem we address.

   * The Mobile IP Challenge/Response Extensions (RFC 3012) seems to
     be an attempt to make the authentication in Mobile IP more
     generic.  This is accomplished by using the same packet format
     for authentication of any entity, instead of using special
     packets, one for the Home Agent, one for the Foreign Agent and
     one for the Mobile Node.

     However, the way in which the Authenticator packets are exchange
     is not changed.  Only a generic packet format is defined, but a
     generic interaction description is not included.  This "generic
     interaction description" should include how the authentication
     mechanism can signal "continue", "abort" and "success" to the
     other entity.  Only "abort" and "success" is possible now, using
     the base RFC 2002 spec.

     The Generalized Key Distribution Extension is similar, it only
     describes a generic packet format without discussing a generic
     way in which the packets can be used.

Outline of suggested specification:
-----------------------------------

A specification may introduce new Mobile IP error codes that should be
used as indicators that the other entity that additional authenticator
packets needs to be exchanges before it can complete.  Examples:

   Registration denied by the foreign agent:

...
       89 Foreign Agent needs more authentication data before it can proceed

   Registration denied by the home agent:

...
      142 Home Agent needs more authentication data before it can proceed.

The individual authenticator mechanisms could be allocated in the
0-255 SPI IANA space as defined in RFC 3012, examples:


SPI Values for the Mobile IP Reserved SPIs:

	0 Reserved                                            [RFC3012]
        1 Reserved                                            [RFC3012]
        2 CHAP                                                [RFC3012]
	3 TLS
	4 EAP
	5 PKI
	...

(Where 5 could be ideas similar to what is in
draft-jacobs-mobileip-pki-auth-03.txt.)

Example:
--------

This is an example of how TLS can be used to authenticate a user to a
Mobile IP infrastructure.  Note that the TLS_SPI of 4 and Continuation
Error Code of 137 are just examples, they are not official in any way.

        Mobile Node                            Home Agent

{Mobile IP Registration Request:
Mobile-Home Auth Extension:
SPI=4 (TLS_SPI), Authenticator:
TLS Client Hello, ...}

                                        {Mobile IP Registration Reply:
                                        Code=137 (Continue Authentication)
					Mobile-Home Auth Extension:
					SPI=4 (TLS_SPI), Authenticator:
					TLS Server Hello, ...}

{Mobile IP Registration Request:
Mobile-Home Auth Extension:
SPI=4 (TLS_SPI), Authenticator:
TLS Client Key Exchange, ...}
                                    .
                                    .
                                    .

                                        {Mobile IP Registration Reply:
                                        Code=0 (Registration Accepted)
					Mobile-Home Auth Extension:
					SPI=4 (TLS_SPI), Authenticator:
					TLS Server Finished, ...}

Open Issues:
------------

One needs to investigate the need for a CHALLENGE extension such as
the one used in RFC 3012 to prevent replay-attacks of the registration
requests, or at least a identification scheme to make it possible to
separate between multiple authentication attempts.

It is not clear to me how sending multiple registration requests would
affect Mobile IP implementations, especially how the Foreign Agent
would react.  Maybe the approach above interacts badly with the design
of Mobile IP.



From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep 28 13:30:46 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20421
	for <mobileip-archive@odin.ietf.org>; Fri, 28 Sep 2001 13:30:46 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA15919;
	Fri, 28 Sep 2001 10:29:47 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id KAA29326;
	Fri, 28 Sep 2001 10:29:19 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8SHSN7B027141
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 28 Sep 2001 10:28:23 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8SHSMaI027140
	for mobile-ip-dist; Fri, 28 Sep 2001 10:28:22 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8SHSJ7B027133
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 10:28:19 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id KAA27982
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 10:28:22 -0700 (PDT)
Received: from zrc2s03g.us.nortel.com (h66s122a103n47.user.nortelnetworks.com [47.103.122.66])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA09348
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 11:29:12 -0600 (MDT)
Received: from smtprch1.nortel.com (erchg0j.us.nortel.com [47.113.64.103])
	by zrc2s03g.us.nortel.com (8.9.3+Sun/8.9.1) with ESMTP id MAA15146
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 12:27:56 -0500 (CDT)
Received: from zrchb200.us.nortel.com by smtprch1.nortel.com;
          Fri, 28 Sep 2001 12:27:53 -0500
Received: by zrchb200.us.nortel.com with Internet Mail Service (5.5.2653.19) 
          id <SK3LSJXD>; Fri, 28 Sep 2001 12:27:37 -0500
Message-ID: <933FADF5E673D411B8A30002A5608A0E2E43CE@zrc2c012.us.nortel.com>
From: "Glenn Morrow" <gmorrow@nortelnetworks.com>
To: mobile-ip@sunroof.eng.sun.com
Subject: [mobile-ip] Security Requirements Draft
Date: Fri, 28 Sep 2001 12:27:37 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01C14842.DDF44860"
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

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

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

Hello,

In draft,

http://www.ietf.org/internet-drafts/draft-ietf-mobileip-mipv6-scrty-reqts-00
.txt,

there are a list of assumptions detailed in section 1.1. Paraphrased they
are:

1> MN and HA have pre-arranged SA.
2> No pre-arranged SA between MN and CA.

I would like to float another proposed assumption and get feedback on this.

3> That there is some sort of SA (perhaps dynamically created at initial
access) between the ARs and the MN in the visited subnet.


Comments, please.

Glenn

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.89">
<TITLE>Security Requirements Draft</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Hello,</FONT>
</P>

<P><FONT SIZE=3D2>In draft,</FONT>
</P>

<P><FONT SIZE=3D2><A =
HREF=3D"http://www.ietf.org/internet-drafts/draft-ietf-mobileip-mipv6-sc=
rty-reqts-00.txt" =
TARGET=3D"_blank">http://www.ietf.org/internet-drafts/draft-ietf-mobilei=
p-mipv6-scrty-reqts-00.txt</A>,</FONT>
</P>

<P><FONT SIZE=3D2>there are a list of assumptions detailed in section =
1.1. Paraphrased they are:</FONT>
</P>

<P><FONT SIZE=3D2>1&gt; MN and HA have pre-arranged SA.</FONT>
<BR><FONT SIZE=3D2>2&gt; No pre-arranged SA between MN and CA.</FONT>
</P>

<P><FONT SIZE=3D2>I would like to float another proposed assumption and =
get feedback on this.</FONT>
</P>

<P><FONT SIZE=3D2>3&gt; That there is some sort of SA (perhaps =
dynamically created at initial access) between the ARs and the MN in =
the visited subnet.</FONT></P>
<BR>

<P><FONT SIZE=3D2>Comments, please.</FONT>
</P>

<P><FONT SIZE=3D2>Glenn</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C14842.DDF44860--


From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep 28 13:36:53 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20585
	for <mobileip-archive@odin.ietf.org>; Fri, 28 Sep 2001 13:36:53 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id LAA19275;
	Fri, 28 Sep 2001 11:35:49 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id KAA01109;
	Fri, 28 Sep 2001 10:35:42 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8SHYp7B027238
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 28 Sep 2001 10:34:51 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8SHYp7m027237
	for mobile-ip-dist; Fri, 28 Sep 2001 10:34:51 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8SHYm7B027230
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 10:34:48 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id KAA09334
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 10:34:49 -0700 (PDT)
Received: from extmail02m.raleigh.ibm.com (extmail02.raleigh.ibm.com [204.146.167.243])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id LAA18286
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 11:34:38 -0600 (MDT)
Received: from rtpmail01.raleigh.ibm.com (rtpmail01.raleigh.ibm.com [192.168.1.107])
	by extmail02m.raleigh.ibm.com (8.9.0/8.9.0/RTP-FW-1.3) with ESMTP id NAA34706
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 13:33:19 -0400
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.37.60.3])
	by rtpmail01.raleigh.ibm.com (8.8.5/8.8.5/RTP-ral-1.2) with ESMTP id NAA11614
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 13:34:47 -0400
Received: from rotala.raleigh.ibm.com (narten@localhost) by rotala.raleigh.ibm.com (8.9.3/8.7/RTP-ral-1.0) with ESMTP id NAA25234 for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 13:32:23 -0400
Message-Id: <200109281732.NAA25234@rotala.raleigh.ibm.com>
To: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Concerns/comments for aaa-keys and gen-key 
In-Reply-To: Message of "Thu, 27 Sep 2001 21:06:47 PDT." <20010927210647.F1723@charizard.diameter.org> 
Date: Fri, 28 Sep 2001 13:32:22 -0400
From: Thomas Narten <narten@raleigh.ibm.com>
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Since the following point has been stated twice now...

Pat Calhoun <pcalhoun@diameter.org> writes:

> While on this interoperability talk, I'd like to note that we have 4 
> independently developed implementations that successfully interoperated
> on many occasions.

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

> up the argument.  There have been people working with these
> documents to produce interoperable implementations that do what
> the engineers want to have done.  Their experience is reflected
> in these documents.

The single most important purpose of the IETF is to produce Standards
from which interoperable implementations can be built. Note that this
*very* different than having a document that N implementations claim
to conform to. Let me repeat, the goal is to get *documents* that are
clear and from which implementations can be build. That means, the
specs *need* to stand up on their own.

It is common for implementations and draft writing to go on in
parallel (and this is generally good!), but one negative side effect
is that sometimes issues get discussed in e-mail only, and don't get
clearly written up in the specs themselves. But implementors don't
notice, because they've got their implementations working based on
e-mail, hallway conversations, and bakeoffs.

I would think that a WG would find it very valuable to have a detailed
review from someone outside of the WG (i.e., from somone not familar
with the detailed history of what has gone on on the mailing
list). Such a review then really evaluates the spec on its own. I.e.,
much like when a new implementor, one who knows little about MIP
because MIP is a new project for them, starts by reading the RFC for
the first time.

Unfortunately, we do have a long history of documents that in
hindsight were riddled with ambiguities. If only the original language
had been clearer.

Thomas


From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep 28 14:01:55 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21315
	for <mobileip-archive@odin.ietf.org>; Fri, 28 Sep 2001 14:01:54 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id MAA11344;
	Fri, 28 Sep 2001 12:01:06 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id LAA07500;
	Fri, 28 Sep 2001 11:01:06 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8SHxx7B027410
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 28 Sep 2001 10:59:59 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8SHxx87027409
	for mobile-ip-dist; Fri, 28 Sep 2001 10:59:59 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8SHxt7B027402
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 10:59:55 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id KAA06202
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 10:59:56 -0700 (PDT)
Received: from WIN-INET-01.wingroup.windeploy.ntdev.microsoft.com ([131.107.3.118])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id KAA06805
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 10:59:56 -0700 (PDT)
Received: from win-hub-01.wingroup.windeploy.ntdev.microsoft.com ([157.54.5.229]) by WIN-INET-01.wingroup.windeploy.ntdev.microsoft.com with Microsoft SMTPSVC(5.0.2195.3651);
	 Fri, 28 Sep 2001 10:53:03 -0700
Received: from 157.54.5.226 by win-hub-01.wingroup.windeploy.ntdev.microsoft.com (InterScan E-Mail VirusWall NT); Fri, 28 Sep 2001 10:53:03 -0700
Received: from win-msg-01.wingroup.windeploy.ntdev.microsoft.com ([157.54.0.52]) by win-hub-01.wingroup.windeploy.ntdev.microsoft.com with Microsoft SMTPSVC(5.0.2195.3651);
	 Fri, 28 Sep 2001 10:53:03 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.0.5716.0
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Subject: [mobile-ip] RE: Joining to SSM sources that are IPv6 mobile nodes
Date: Fri, 28 Sep 2001 10:53:00 -0700
Message-ID: <2E33960095B58E40A4D3345AB9F65EC102DB7D75@win-msg-01.wingroup.windeploy.ntdev.microsoft.com>
Thread-Topic: Joining to SSM sources that are IPv6 mobile nodes
thread-index: AcFHdEJyDC+htTC/STSdH+XWQl2H3AAz08gg
From: "Dave Thaler" <dthaler@windows.microsoft.com>
To: "Rolland Vida" <Rolland.Vida@lip6.fr>, <mobile-ip@sunroof.eng.sun.com>
Cc: <magma@innovationslab.net>, <ssm-interest@external.cisco.com>
X-OriginalArrivalTime: 28 Sep 2001 17:53:03.0329 (UTC) FILETIME=[6B9A9D10:01C14846]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by sunroof.eng.sun.com id f8SHxu7B027403
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 8bit

Rolland Vida (Rolland.Vida@lip6.fr) writes:
[...]
> > Either option (1) would never be used for any multicast traffic, or
else
> > the host would
> > have to know whether a receiver might want to use an include-mode
list
> > with MLDv2 and tunnel to the home agent if so.
> 
> You can make the difference between an SSM and an SM connection by the
> group's address. There's a specific SSM address range, and it is
supposed
> that you do not do PIM-SM  in the SSM range.

It's not that simple.  Moving on to quote draft-ietf-ssm-overview-01.txt
section 1:
> Source-Filtered Multicast (SFM) : This is a variant of the multicast
> service model defined in RFC 1112. A source transmits IP datagrams to
> a host group address in the range of 224.0.0.0 to 239.255.255.255.
[for now ignore the fact that the above sentence needs to be reworded
to apply to IPv6 as well... hint to SSM WG...]
> However, each "upper layer protocol module" can now request data sent
> to a host group G by only a specific set of sources, or can request
> data sent to host group G from all BUT a specific set of sources.
> Such support for source filtering is provided by version 3 of the
> Internet Group Management Protocol (or IGMPv3) [IGMPv3] for IPv4, and
> version 2 of the Multicast Listener Discovery (or MLD) protocol for
> IPv6 [MLDv2]. 

The point here is that the problem is not limited to the SSM
address range for IPv6.  It really applies to include-mode joins
for any IPv6 multicast address.  Today the multicast model does not
require sources to know whether receivers might do this.  As a result,
without changing the model, you cannot use the address range to make any
decision here.

Based on the four people who have responded so far (Dupont, Haberman,
Luby, and Vida) it sounds like the consensus will be to always tunnel 
via the home agent if you need network-layer mobility.  If this
consensus holds, then I think the Mobile IPv6 spec should say that any
time the app sends multicast using the home address, the stack
SHOULD/MUST tunnel it via the home agent, and also say that the Home
Address Option SHOULD NOT/MUST NOT be used in multicast packets.  The
application can certainly choose whether to source from the Home Address
(in which case receivers will continue to get data if it moves), or from
the Care Of Address (where mobility must be handled by the application
as Mike Luby suggested).  There would then be no additional impact on
APIs, or the MAGMA or SSM WGs.

-Dave



From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep 28 15:01:29 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22481
	for <mobileip-archive@lists.ietf.org>; Fri, 28 Sep 2001 15:01:26 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id NAA00849;
	Fri, 28 Sep 2001 13:00:37 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id MAA21427;
	Fri, 28 Sep 2001 12:00:35 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8SIxA7B027611
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 28 Sep 2001 11:59:10 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8SIxAsw027610
	for mobile-ip-dist; Fri, 28 Sep 2001 11:59:10 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8SIx77B027603
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 11:59:07 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id LAA21980
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 11:59:09 -0700 (PDT)
Received: from ftpbox.mot.com (ftpbox.mot.com [129.188.136.101])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id LAA28643
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 11:59:08 -0700 (PDT)
Received: [from pobox2.mot.com (pobox2.mot.com [136.182.15.8]) by ftpbox.mot.com (ftpbox 2.1) with ESMTP id LAA19234 for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 11:59:08 -0700 (MST)]
Received: [from m-il06-r2.mot.com (m-il06-r2.mot.com [129.188.137.24]) by pobox2.mot.com (MOT-pobox2 2.0) with ESMTP id LAA12396 for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 11:59:08 -0700 (MST)]
Received: from thorgal.crm.mot.com by m-il06-r2.mot.com with ESMTP for mobile-ip@sunroof.eng.sun.com; Fri, 28 Sep 2001 11:58:59 -0700
Received: from test9.crm.mot.com.crm.mot.com (test9.crm.mot.com [140.101.173.239])
	by thorgal.crm.mot.com (Postfix) with ESMTP id 5AC882ED24
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 20:55:46 +0200 (CEST)
To: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Security Requirements Draft
References: <933FADF5E673D411B8A30002A5608A0E2E43CE@zrc2c012.us.nortel.com>
From: Alexandru Petrescu <petrescu@crm.mot.com>
Date: 28 Sep 2001 20:59:03 +0200
In-Reply-To: <933FADF5E673D411B8A30002A5608A0E2E43CE@zrc2c012.us.nortel.com>
Message-Id: <m3ite316rs.fsf@test9.crm.mot.com>
Lines: 17
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.0.103
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

"Glenn Morrow" <gmorrow@nortelnetworks.com> writes:
> I would like to float another proposed assumption and get feedback
> on this.
>
> 3> That there is some sort of SA (perhaps dynamically created at
> initial access) between the ARs and the MN in the visited subnet.

Probably establishing an AR-MN SA is very much like establishing CN-MN
SA.  Hard to do, so it's probably difficult to assume it already
exists.

Requirement G.1 imposes establishing an SA between AR (acting as HA)
and MN.

Just my oppinion,

Alex



From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep 28 17:55:34 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA25662
	for <mobileip-archive@odin.ietf.org>; Fri, 28 Sep 2001 17:55:33 -0400 (EDT)
Received: from engmail1.Eng.Sun.COM ([129.146.1.13])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id OAA16771;
	Fri, 28 Sep 2001 14:54:50 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id OAA06346;
	Fri, 28 Sep 2001 14:54:38 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8SLra7B027868
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 28 Sep 2001 14:53:36 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8SLrZH0027867
	for mobile-ip-dist; Fri, 28 Sep 2001 14:53:35 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8SLrW7B027860
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 14:53:32 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id OAA05041
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 14:53:33 -0700 (PDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id OAA11140
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 14:53:33 -0700 (PDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id OAA29897;
	Fri, 28 Sep 2001 14:53:33 -0700 (PDT)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f8SLrWO27608;
	Fri, 28 Sep 2001 14:53:32 -0700
X-mProtect:  Fri, 28 Sep 2001 14:53:32 -0700 Nokia Silicon Valley Messaging Protection
Received: from Icharliep-1.iprg.nokia.com (205.226.22.18, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpdg4WT0j; Fri, 28 Sep 2001 14:53:30 PDT
Message-ID: <3BB4F163.74444F54@iprg.nokia.com>
Date: Fri, 28 Sep 2001 14:53:39 -0700
From: Charlie Perkins <charliep@iprg.nokia.com>
Organization: Nokia
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Thomas Narten <narten@raleigh.ibm.com>
CC: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Concerns/comments for aaa-keys and gen-key
References: <200109281732.NAA25234@rotala.raleigh.ibm.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Hello Thomas,

I ought to say something about this, since my initial foray
into the discussion was based on my understanding that
we were being asked to develop some new key distribution
protocol between AAA and mobile node.  If you read
my initial (probably too long) e-mail in this context, it
probably makes a lot more sense (at least I hope!).
When it became clear that the actual request was much
narrower in scope, then the problem has become very
much smaller.  I've already outlined what I thought would
be a way to satisfy the smaller request which I think is
what was originally requested (e.g., explicitly state that
the mandated RFC2002bis digestification algorithm must
be implemented).  In fact, if the proposal is put that
way, it's practically a no-brainer.  I guess I wasn't expecting
it to be so easy.


Regarding your statements:

> The single most important purpose of the IETF is to produce Standards
> from which interoperable implementations can be built. Note that this
> *very* different than having a document that N implementations claim
> to conform to. Let me repeat, the goal is to get *documents* that are
> clear and from which implementations can be build. That means, the
> specs *need* to stand up on their own.

Wholeheartedly agree.

> It is common for implementations and draft writing to go on in
> parallel (and this is generally good!), but one negative side effect
> is that sometimes issues get discussed in e-mail only, and don't get
> clearly written up in the specs themselves. But implementors don't
> notice, because they've got their implementations working based on
> e-mail, hallway conversations, and bakeoffs.

Agreed, with the proviso (with which I am sure you will agree)
that implementation experience is the hugely positive factor and
that the implicit assumptions you allude to are what need to be
brought out and examined (and perhaps on occasion challenged).

> I would think that a WG would find it very valuable to have a detailed
> review from someone outside of the WG (i.e., from somone not familar
> with the detailed history of what has gone on on the mailing
> list). Such a review then really evaluates the spec on its own. I.e.,
> much like when a new implementor, one who knows little about MIP
> because MIP is a new project for them, starts by reading the RFC for
> the first time.

I definitely agree with this, as long as the new implementor can be
presumed to tackle the implementation tasks roughly "in order".

Regards,
Charlie P.




From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep 28 18:19:57 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA26244
	for <mobileip-archive@odin.ietf.org>; Fri, 28 Sep 2001 18:19:56 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id PAA27012;
	Fri, 28 Sep 2001 15:19:25 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id PAA18667;
	Fri, 28 Sep 2001 15:19:13 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8SMIJ7B027970
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 28 Sep 2001 15:18:19 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8SMIJAr027969
	for mobile-ip-dist; Fri, 28 Sep 2001 15:18:19 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8SMIF7B027962
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 15:18:15 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id PAA13524
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 15:18:17 -0700 (PDT)
Received: from mgw-dax2.ext.nokia.com (mgw-dax2.ext.nokia.com [63.78.179.217])
	by venus.sun.com (8.9.3+Sun/8.9.3) with ESMTP id PAA00153
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 15:18:17 -0700 (PDT)
Received: from davir02nok.americas.nokia.com (davir02nok.americas.nokia.com [172.18.242.85])
	by mgw-dax2.ext.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f8SMIWC00833
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 17:18:32 -0500 (CDT)
Received: from daebh001.NOE.Nokia.com (unverified) by davir02nok.americas.nokia.com
 (Content Technologies SMTPRS 4.2.5) with ESMTP id <T56463b909eac12f255079@davir02nok.americas.nokia.com> for <mobile-ip@sunroof.eng.sun.com>;
 Fri, 28 Sep 2001 17:18:16 -0500
Received: from daebe007.NOE.Nokia.com ([172.18.242.211]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.2966);
	 Fri, 28 Sep 2001 17:18:16 -0500
content-class: urn:content-classes:message
Subject: RE: [mobile-ip] Security Requirements Draft
Date: Fri, 28 Sep 2001 17:18:23 -0500
Message-ID: <697DAA22C5004B4596E033803A7CEF441E8776@daebe007.NOE.Nokia.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C1486B.7C99D418"
Thread-Topic: [mobile-ip] Security Requirements Draft
X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0
Thread-Index: AcFIQzX1kuZ7ErQyEdWxLwAIx6TWeAAKDh/w
From: "Patil Basavaraj (NET/Dallas)" <Basavaraj.Patil@nokia.com>
To: <mobile-ip@sunroof.eng.sun.com>
X-OriginalArrivalTime: 28 Sep 2001 22:18:16.0020 (UTC) FILETIME=[784E9140:01C1486B]
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C1486B.7C99D418
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


Glenn,
=20
>
>Hello,=20
>
>In draft,=20
>=20
>draft-ietf-mobileip-mipv6-scrty-reqts-00.txt
>there are a list of assumptions detailed in section 1.1. Paraphrased
>they are: =20
>
>1> MN and HA have pre-arranged SA.=20
>2> No pre-arranged SA between MN and CA.=20
>
>I would like to float another proposed assumption and get feedback on
this.=20
>
>3> That there is some sort of SA (perhaps dynamically created at
>initial access) between the ARs and the MN in the visited subnet.=20
>
>
=20
I guess the reason for having such an SA with an AR and the MN is for
the AR to take on the role of a Home Agent when the MN moves and sends
a BU to the AR on the previous link. There needs to be an SA between
the MN and this AR since the BU needs to be authenticated. However I
do not believe we should assume that this is somehow setup. There
needs to be a mechanism for setting up this SA. It could be
accomplished via the same mechanism that would be used for setting up
a dynamic SA between the MN and the CN. So I would prefer not to make
an assumption about the existence of such an SA.
=20
>
>Comments, please.=20
>
>Glenn=20
=20
-Basavaraj
=20
>
>


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<TITLE>Security Requirements Draft</TITLE>

<META content=3D"MSHTML 5.50.4134.600" name=3DGENERATOR></HEAD>
<BODY><FONT face=3DArial color=3D#0000ff size=3D2>
<DIV><BR>Glenn,</DIV>
<DIV>&nbsp;</DIV>
<DIV>&gt;<BR>&gt;Hello, <BR>&gt;<BR>&gt;In draft, <BR>&gt;=20
<BR>&gt;draft-ietf-mobileip-mipv6-scrty-reqts-00.txt<BR>&gt;there are a =
list of=20
assumptions detailed in section 1.1. Paraphrased<BR>&gt;they are:&nbsp;=20
<BR>&gt;<BR>&gt;1&gt; MN and HA have pre-arranged SA. <BR>&gt;2&gt; No=20
pre-arranged SA between MN and CA. <BR>&gt;<BR>&gt;I would like to float =
another=20
proposed assumption and get feedback on this. <BR>&gt;<BR>&gt;3&gt; That =
there=20
is some sort of SA (perhaps dynamically created at<BR>&gt;initial =
access)=20
between the ARs and the MN in the visited subnet. <BR>&gt;<BR>&gt;</DIV>
<DIV>&nbsp;</DIV>
<DIV>I guess the reason for having such an SA with an AR and the MN is=20
for<BR>the AR to take on the role of a Home Agent when the MN moves and=20
sends<BR>a BU to the AR on the previous link. There needs to be an SA=20
between<BR>the MN and this AR since the BU needs to be authenticated. =
However=20
I<BR>do not believe we should assume that this is somehow setup. =
There<BR>needs=20
to be a mechanism for setting up this SA. It could be<BR>accomplished =
via the=20
same mechanism that would be used for setting up<BR>a dynamic SA between =
the MN=20
and the CN. So I would prefer not to make<BR>an assumption about the =
existence=20
of such an SA.</DIV>
<DIV>&nbsp;</DIV>
<DIV>&gt;<BR>&gt;Comments, please. <BR>&gt;<BR>&gt;Glenn </DIV>
<DIV>&nbsp;</DIV>
<DIV>-Basavaraj</DIV>
<DIV>&nbsp;</DIV>
<DIV>&gt;<BR>&gt;<BR></FONT></DIV></BODY></HTML>

------_=_NextPart_001_01C1486B.7C99D418--


From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep 28 18:26:02 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA26429
	for <mobileip-archive@lists.ietf.org>; Fri, 28 Sep 2001 18:26:02 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id QAA28878;
	Fri, 28 Sep 2001 16:25:23 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id PAA19948;
	Fri, 28 Sep 2001 15:25:26 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8SMOi7B028066
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 28 Sep 2001 15:24:44 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8SMOir7028065
	for mobile-ip-dist; Fri, 28 Sep 2001 15:24:44 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8SMOf7B028058
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 15:24:41 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id PAA19837;
	Fri, 28 Sep 2001 15:24:43 -0700 (PDT)
Received: from sj-msg-core-3.cisco.com (sj-msg-core-3.cisco.com [171.70.157.152])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id QAA01553;
	Fri, 28 Sep 2001 16:25:41 -0600 (MDT)
Received: from mira-sjc5-7.cisco.com (mira-sjc5-7.cisco.com [171.71.163.27])
	by sj-msg-core-3.cisco.com (8.11.3/8.9.1) with ESMTP id f8SMMa711019;
	Fri, 28 Sep 2001 15:22:38 -0700 (PDT)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-7.cisco.com (Mirapoint)
	with ESMTP id AAV11745;
	Fri, 28 Sep 2001 15:24:36 -0700 (PDT)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id PAA02487; Fri, 28 Sep 2001 15:24:36 -0700 (PDT)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15284.63652.615358.830329@thomasm-u1.cisco.com>
Date: Fri, 28 Sep 2001 15:24:36 -0700 (PDT)
To: mobile-ip@sunroof.eng.sun.com
Cc: "Charles E. Perkins" <charliep@IPRG.nokia.com>,
        Erik Nordmark <Erik.Nordmark@eng.sun.com>,
        Pat Calhoun <pcalhoun@diameter.org>
Subject: Re: [mobile-ip] Concerns/comments for aaa-keys and gen-key
In-Reply-To: <20010927204724.A1723@charizard.diameter.org>
References: <Roam.SIMC.2.0.6.1001427527.14101.nordmark@bebop.france>
	<3BB15C81.DE5655DA@iprg.nokia.com>
	<20010927204724.A1723@charizard.diameter.org>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Pat Calhoun writes:
 > Mobile IP is a request/response protocol. Unfortunately, it doesn't lend itself
 > well to negotiations. So, the AAAH (owned by the administrator) will have to
 > select the algorithm and key length. If the transforms provided are not
 > sufficient (e.g. hmac-md5), then some guidance would be  appreciated.

   Beyond Eric's clarification, I have a question:
   You clearly must derive new keys from the MN/AAA
   secret which if I remember correctly comes from
   the AAA, encrypted in the MN/AAA key. What prevents
   key reuse, especially for rekeying? Is there a way
   to get the AAA to supply fresh key material on demand?
   If so, is the performance penalty going to be acceptible?
   If not, is the expectation that one or both of the
   ends of the SA supply entropy? If it's only one side,
   what happens if their random number generator is not
   very good, like oh say open("/dev/null")?

   The reason I ask is because key derivation is a pretty
   big preoccupation with crypto types. Generally speaking,
   the safest thing is to have all parties contribute to
   the entropy, though having a trustworthy source of entropy
   like a KDC may be adequate assuming that you don't
   reuse its entropy without adding fresh entropy.

		     Mike


From owner-mobile-ip@sunroof.eng.sun.com  Fri Sep 28 19:03:35 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27071
	for <mobileip-archive@odin.ietf.org>; Fri, 28 Sep 2001 19:03:34 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id QAA13691;
	Fri, 28 Sep 2001 16:02:58 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id QAA29476;
	Fri, 28 Sep 2001 16:02:44 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8SN1l7B028235
	for <mobile-ip-dist@sunroof.eng.sun.com>; Fri, 28 Sep 2001 16:01:47 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0/Submit) id f8SN1k3E028234
	for mobile-ip-dist; Fri, 28 Sep 2001 16:01:46 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail1.Eng.Sun.COM (engmail1 [129.146.1.13])
	by sunroof.eng.sun.com (8.12.0+Sun/8.12.0) with ESMTP id f8SN1h7B028227
	for <mobile-ip@sunroof.eng.sun.com>; Fri, 28 Sep 2001 16:01:43 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail1.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id QAA21459;
	Fri, 28 Sep 2001 16:01:45 -0700 (PDT)
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id QAA05155;
	Fri, 28 Sep 2001 16:01:45 -0700 (PDT)
Received: from mira-sjc5-7.cisco.com (mira-sjc5-7.cisco.com [171.71.163.27])
	by sj-msg-core-1.cisco.com (8.11.6/8.9.1) with ESMTP id f8SN1kG13235;
	Fri, 28 Sep 2001 16:01:46 -0700 (PDT)
Received: from thomasm-u1.cisco.com (thomasm-u1.cisco.com [128.107.140.53])
	by mira-sjc5-7.cisco.com (Mirapoint)
	with ESMTP id AAV12767;
	Fri, 28 Sep 2001 16:01:43 -0700 (PDT)
Received: (thomasm@localhost) by thomasm-u1.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) id QAA02490; Fri, 28 Sep 2001 16:01:43 -0700 (PDT)
From: Michael Thomas <mat@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15285.342.564369.518062@thomasm-u1.cisco.com>
Date: Fri, 28 Sep 2001 16:01:42 -0700 (PDT)
To: mobile-ip@sunroof.eng.sun.com
Cc: Michael Thomas <mat@cisco.com>,
        Fredrik Johansson <fredrik.johansson@ipunplugged.com>,
        Erik.Nordmark@eng.sun.com, Charlie Perkins <charliep@IPRG.nokia.com>,
        Pat Calhoun <pcalhoun@diameter.org>
Subject: Re: [mobile-ip] Concerns/comments for aaa-keys and gen-key
In-Reply-To: <20010928081614.F3848@charizard.diameter.org>
References: <MJEMJBGGCLLDLFFAHLJKAEHFDGAA.fredrik.johansson@ipunplugged.com>
	<Roam.SIMC.2.0.6.1001495690.1688.nordmark@bebop.france>
	<15282.3298.522332.579900@thomasm-u1.cisco.com>
	<20010927205547.C1723@charizard.diameter.org>
	<15284.38307.873861.584422@thomasm-u1.cisco.com>
	<20010928081614.F3848@charizard.diameter.org>
X-Mailer: VM 6.72 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
X-Face: &,heK/V66p?[2!i|tVn,9lN0TUvEv7:9FzXREj/AuzN4m<D]vnFJ>u!4x[/Z4t{V}~L]+Sk
 @RFNnJEg~WZ/(8<`5a),-7ukALWa^&?&D2R0CSG3kO5~#6JxLF\d,g">$%B!0w{W)qIhmwhye104zd
 bUcI'1!
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>
Content-Transfer-Encoding: 7bit

Pat Calhoun writes:
 > >    Nobody's said anything about starting over. I notice
 > >    that you don't address my main concern of why *key
 > >    distribution* is being pursued in MIP. It's not even
 > >    in the AAA charter, let alone the MIP charter.
 > 
 > ok... perhaps I misunderstood, but it sure sounded that way to
 > me. As some folks (including the IESG) have repeatedly mentioned,
 > don't expect the security area to secure every other WG's protocols.
 > That will not happen. They will, however, lend a hand in security
 > reviews.

   This is not the same creature though; I certainly
   don't want the security area to become an IETF
   sweat shop. However I think it's pretty reasonable
   to say that key distribution protocols are hard 
   enough creatures that it requires a great deal of
   awareness from the right people to ask the right
   questions. Like, for example:

   1) my entropy question I ask in a previous piece of mail
   2) What is the key scheduling policy? On the client? On the server?
   3) How are cross realm relationships maintained?
   4) What are the security implications of cross realm distribution?
   5) How is revocation handled?
   6) What about name canonicalization?
   7) Are there hidden assumptions with other protocols
      which could cause trouble?

   etc, etc.

   A lot of these things are pretty subtle, and not
   always immediately obvious unless you've been 
   through the wars enough times. I know that I've
   had a few eye opening revelations before that are
   pretty obvious in hindsight.
     
 > I believe that's what we are asking for here. Creating a whole new
 > WG to look at this problem will delay the work, and waste engineering
 > resources.

   I'm not convinced about that. The WEP debacle
   should make everybody a little more cautious
   about rushing things through.
 
 > We just need a security review.

   And this I'm pretty dubious about. Getting a
   "security review" is no panacea. It takes time
   and energy to understand the system as a whole
   to find where protocol weaknesses are, and I'm
   pretty skeptical that these security reviewers
   actually have the time to really sit down and
   do that. It's *far* better to design something
   where those security reviewers are throwing rocks
   along the way instead of trying to make sense of
   a complicated system in a two week last call
   period.

 > >    Fine. This working group has taken a drubbing
 > >    on the security front for something that was 
 > >    clearly in its charter: securing binding updates.
 > 
 > apples != oranges. I was never involved in the binding 
 > updates... have for a long time stated this doesn't scale.
 > 
 > Please don't bundle me in that work.

   I'm not. I'm just trying to point out that lack
   of security people watching along the way has
   already lead to one meltdown. What this is attempting
   is even more ambitious, IMO.


	   Mike


From owner-mobile-ip@sunroof.eng.sun.com  Sun Sep 30 10:50:47 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA24145
	for <mobileip-archive@lists.ietf.org>; Sun, 30 Sep 2001 10:50:46 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id HAA09001;
	Sun, 30 Sep 2001 07:50:03 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id HAA08620;
	Sun, 30 Sep 2001 07:49:50 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.1+Sun/8.12.1) with ESMTP id f8UEmwML000283
	for <mobile-ip-dist@sunroof.eng.sun.com>; Sun, 30 Sep 2001 07:48:58 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.1+Sun/8.12.1/Submit) id f8UEmvZs000281
	for mobile-ip-dist; Sun, 30 Sep 2001 07:48:57 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.12.1+Sun/8.12.1) with ESMTP id f8UEmsML000273
	for <mobile-ip@sunroof.eng.sun.com>; Sun, 30 Sep 2001 07:48:54 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id HAA08520
	for <mobile-ip@sunroof.eng.sun.com>; Sun, 30 Sep 2001 07:48:56 -0700 (PDT)
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by patan.sun.com (8.9.3+Sun/8.9.3) with SMTP id IAA19565
	for <mobile-ip@sunroof.eng.sun.com>; Sun, 30 Sep 2001 08:48:44 -0600 (MDT)
Received: (qmail 16154 invoked by uid 500); 30 Sep 2001 14:34:41 -0000
Date: Sun, 30 Sep 2001 07:34:41 -0700
From: Pat Calhoun <pcalhoun@diameter.org>
To: mobile-ip@sunroof.eng.sun.com
Subject: Re: [mobile-ip] Concerns/comments for aaa-keys and gen-key
Message-ID: <20010930073441.A16146@charizard.diameter.org>
References: <20010927210647.F1723@charizard.diameter.org> <200109281732.NAA25234@rotala.raleigh.ibm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <200109281732.NAA25234@rotala.raleigh.ibm.com>; from narten@raleigh.ibm.com on Fri, Sep 28, 2001 at 01:32:22PM -0400
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

> The single most important purpose of the IETF is to produce Standards
> from which interoperable implementations can be built. Note that this
> *very* different than having a document that N implementations claim
> to conform to. Let me repeat, the goal is to get *documents* that are
> clear and from which implementations can be build. That means, the
> specs *need* to stand up on their own.
> 
> It is common for implementations and draft writing to go on in
> parallel (and this is generally good!), but one negative side effect
> is that sometimes issues get discussed in e-mail only, and don't get
> clearly written up in the specs themselves. But implementors don't
> notice, because they've got their implementations working based on
> e-mail, hallway conversations, and bakeoffs.
> 
> I would think that a WG would find it very valuable to have a detailed
> review from someone outside of the WG (i.e., from somone not familar
> with the detailed history of what has gone on on the mailing
> list). Such a review then really evaluates the spec on its own. I.e.,
> much like when a new implementor, one who knows little about MIP
> because MIP is a new project for them, starts by reading the RFC for
> the first time.
> 
> Unfortunately, we do have a long history of documents that in
> hindsight were riddled with ambiguities. If only the original language
> had been clearer.

check. I was simply providing the info as a data point.

PatC


From owner-mobile-ip@sunroof.eng.sun.com  Sun Sep 30 10:55:12 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA24218
	for <mobileip-archive@lists.ietf.org>; Sun, 30 Sep 2001 10:55:11 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id IAA20676;
	Sun, 30 Sep 2001 08:54:25 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id HAA09368;
	Sun, 30 Sep 2001 07:54:18 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.1+Sun/8.12.1) with ESMTP id f8UErXML000352
	for <mobile-ip-dist@sunroof.eng.sun.com>; Sun, 30 Sep 2001 07:53:33 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.1+Sun/8.12.1/Submit) id f8UErXOa000351
	for mobile-ip-dist; Sun, 30 Sep 2001 07:53:33 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.1+Sun/8.12.1) with ESMTP id f8UErUML000343
	for <mobile-ip@sunroof.eng.sun.com>; Sun, 30 Sep 2001 07:53:30 -0700 (PDT)
Received: from venus.sun.com (venus.EBay.Sun.COM [129.150.69.5])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id HAA26852
	for <mobile-ip@sunroof.eng.sun.com>; Sun, 30 Sep 2001 07:53:32 -0700 (PDT)
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by venus.sun.com (8.9.3+Sun/8.9.3) with SMTP id HAA15520
	for <mobile-ip@sunroof.eng.sun.com>; Sun, 30 Sep 2001 07:53:31 -0700 (PDT)
Received: (qmail 16184 invoked by uid 500); 30 Sep 2001 14:39:19 -0000
Date: Sun, 30 Sep 2001 07:39:19 -0700
From: Pat Calhoun <pcalhoun@diameter.org>
To: Michael Thomas <mat@cisco.com>
Cc: mobile-ip@sunroof.eng.sun.com,
        "Charles E. Perkins" <charliep@IPRG.nokia.com>,
        Erik Nordmark <Erik.Nordmark@eng.sun.com>,
        Pat Calhoun <pcalhoun@diameter.org>
Subject: Re: [mobile-ip] Concerns/comments for aaa-keys and gen-key
Message-ID: <20010930073919.B16146@charizard.diameter.org>
References: <Roam.SIMC.2.0.6.1001427527.14101.nordmark@bebop.france> <3BB15C81.DE5655DA@iprg.nokia.com> <20010927204724.A1723@charizard.diameter.org> <15284.63652.615358.830329@thomasm-u1.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <15284.63652.615358.830329@thomasm-u1.cisco.com>; from mat@cisco.com on Fri, Sep 28, 2001 at 03:24:36PM -0700
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

>    Beyond Eric's clarification, I have a question:
>    You clearly must derive new keys from the MN/AAA
>    secret which if I remember correctly comes from
>    the AAA, encrypted in the MN/AAA key. What prevents
>    key reuse, especially for rekeying?

no key is ever sent encrypted or otherwise. All that is sent is keying
material, which the mobile uses to create the actual key. The key creation
process does require the long term MN/AAA key.

> Is there a way
>    to get the AAA to supply fresh key material on demand?
>    If so, is the performance penalty going to be acceptible?
>    If not, is the expectation that one or both of the
>    ends of the SA supply entropy? If it's only one side,
>    what happens if their random number generator is not
>    very good, like oh say open("/dev/null")?

Unfortunately, MIP doesn't have the ability for an unsolicited MIP message
to be sent to the mobile. So, using today's protocol, the answer is no.

PatC


From owner-mobile-ip@sunroof.eng.sun.com  Sun Sep 30 10:58:03 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA24263
	for <mobileip-archive@lists.ietf.org>; Sun, 30 Sep 2001 10:58:02 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id HAA09772;
	Sun, 30 Sep 2001 07:57:25 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id HAA09780;
	Sun, 30 Sep 2001 07:57:18 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.1+Sun/8.12.1) with ESMTP id f8UEuYML000411
	for <mobile-ip-dist@sunroof.eng.sun.com>; Sun, 30 Sep 2001 07:56:34 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.1+Sun/8.12.1/Submit) id f8UEuXE4000410
	for mobile-ip-dist; Sun, 30 Sep 2001 07:56:33 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.12.1+Sun/8.12.1) with ESMTP id f8UEuUML000403
	for <mobile-ip@sunroof.eng.sun.com>; Sun, 30 Sep 2001 07:56:30 -0700 (PDT)
Received: from patan.sun.com (patan.Central.Sun.COM [129.147.5.43])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id HAA09668
	for <mobile-ip@sunroof.eng.sun.com>; Sun, 30 Sep 2001 07:56:32 -0700 (PDT)
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by patan.sun.com (8.9.3+Sun/8.9.3) with SMTP id IAA21089
	for <mobile-ip@sunroof.eng.sun.com>; Sun, 30 Sep 2001 08:56:20 -0600 (MDT)
Received: (qmail 16205 invoked by uid 500); 30 Sep 2001 14:42:19 -0000
Date: Sun, 30 Sep 2001 07:42:19 -0700
From: Pat Calhoun <pcalhoun@diameter.org>
To: Michael Thomas <mat@cisco.com>
Cc: mobile-ip@sunroof.eng.sun.com,
        Fredrik Johansson <fredrik.johansson@ipunplugged.com>,
        Erik.Nordmark@eng.sun.com, Charlie Perkins <charliep@IPRG.nokia.com>,
        Pat Calhoun <pcalhoun@diameter.org>
Subject: Re: [mobile-ip] Concerns/comments for aaa-keys and gen-key
Message-ID: <20010930074219.C16146@charizard.diameter.org>
References: <MJEMJBGGCLLDLFFAHLJKAEHFDGAA.fredrik.johansson@ipunplugged.com> <Roam.SIMC.2.0.6.1001495690.1688.nordmark@bebop.france> <15282.3298.522332.579900@thomasm-u1.cisco.com> <20010927205547.C1723@charizard.diameter.org> <15284.38307.873861.584422@thomasm-u1.cisco.com> <20010928081614.F3848@charizard.diameter.org> <15285.342.564369.518062@thomasm-u1.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <15285.342.564369.518062@thomasm-u1.cisco.com>; from mat@cisco.com on Fri, Sep 28, 2001 at 04:01:42PM -0700
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

>  > ok... perhaps I misunderstood, but it sure sounded that way to
>  > me. As some folks (including the IESG) have repeatedly mentioned,
>  > don't expect the security area to secure every other WG's protocols.
>  > That will not happen. They will, however, lend a hand in security
>  > reviews.
> 
>    This is not the same creature though; I certainly
>    don't want the security area to become an IETF
>    sweat shop. However I think it's pretty reasonable
>    to say that key distribution protocols are hard 
>    enough creatures that it requires a great deal of
>    awareness from the right people to ask the right
>    questions. Like, for example:
> 
>    1) my entropy question I ask in a previous piece of mail
>    2) What is the key scheduling policy? On the client? On the server?
>    3) How are cross realm relationships maintained?
>    4) What are the security implications of cross realm distribution?
>    5) How is revocation handled?
>    6) What about name canonicalization?
>    7) Are there hidden assumptions with other protocols
>       which could cause trouble?
> 

I hear your concern. All of the above, with the exception of one, is
handled in the Diameter MIP application. Unfortunately, it is spread out
throughout the spec. Perhaps a recap in the security considerations would
be a good idea.

PatC


From owner-mobile-ip@sunroof.eng.sun.com  Sun Sep 30 11:05:41 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24366
	for <mobileip-archive@lists.ietf.org>; Sun, 30 Sep 2001 11:05:41 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id JAA22791;
	Sun, 30 Sep 2001 09:04:33 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id IAA10866;
	Sun, 30 Sep 2001 08:04:35 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.1+Sun/8.12.1) with ESMTP id f8UF3hML000524
	for <mobile-ip-dist@sunroof.eng.sun.com>; Sun, 30 Sep 2001 08:03:43 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.1+Sun/8.12.1/Submit) id f8UF3hvE000523
	for mobile-ip-dist; Sun, 30 Sep 2001 08:03:43 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail4.Eng.Sun.COM (engmail4 [129.144.134.6])
	by sunroof.eng.sun.com (8.12.1+Sun/8.12.1) with ESMTP id f8UF3dML000516
	for <mobile-ip@sunroof.eng.sun.com>; Sun, 30 Sep 2001 08:03:39 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id IAA10743
	for <mobile-ip@sunroof.eng.sun.com>; Sun, 30 Sep 2001 08:03:42 -0700 (PDT)
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with SMTP id IAA19258
	for <mobile-ip@sunroof.eng.sun.com>; Sun, 30 Sep 2001 08:03:41 -0700 (PDT)
Received: (qmail 16276 invoked by uid 500); 30 Sep 2001 14:49:30 -0000
Date: Sun, 30 Sep 2001 07:49:30 -0700
From: Pat Calhoun <pcalhoun@diameter.org>
To: "Charles E. Perkins" <charliep@IPRG.nokia.com>
Cc: Pat Calhoun <pcalhoun@diameter.org>, mobile-ip@sunroof.eng.sun.com
Subject: [mobile-ip] Re: Scalability of Binding Updates
Message-ID: <20010930074929.G16146@charizard.diameter.org>
References: <MJEMJBGGCLLDLFFAHLJKAEHFDGAA.fredrik.johansson@ipunplugged.com> <Roam.SIMC.2.0.6.1001495690.1688.nordmark@bebop.france> <15282.3298.522332.579900@thomasm-u1.cisco.com> <20010927205547.C1723@charizard.diameter.org> <15284.38307.873861.584422@t <3BB4A085.CCBEF66F@iprg.nokia.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <3BB4A085.CCBEF66F@iprg.nokia.com>; from charliep@IPRG.nokia.com on Fri, Sep 28, 2001 at 09:08:37AM -0700
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

On Fri, Sep 28, 2001 at 09:08:37AM -0700, Charles E. Perkins wrote:
> 
> Hello Pat,
> 
> Pat Calhoun wrote:
> 
> > apples != oranges. I was never involved in the binding
> > updates... have for a long time stated this doesn't scale.
> 
> It seems to me that there is more than one aspect of scalability
> that is important here.  In order to have scalable routing, we
> need to have Binding Updates.  More recently the task has been
> given to us to develop scalable key exchange techniques.
> 
> When that's accomplished, I reckon we will see that mobility
> management is more scalable, not less scalable, in all the
> aspects of interest.

you know what I meant. We talked about PKI scaling at Sun, and how its
reliance in binding updates didn't make me comfortable. I wasn't trying
to address the current work in progress, which I haven't spend one ms
looking at.

I'm sure that the new solution will be much better, and will address
my concerns. I just didn't want to take Mike's BS that I was the one
involved in this one to try to show how AAA keys is bad.

PatC


From owner-mobile-ip@sunroof.eng.sun.com  Sun Sep 30 11:17:08 2001
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24525
	for <mobileip-archive@lists.ietf.org>; Sun, 30 Sep 2001 11:17:07 -0400 (EDT)
Received: from engmail4.Eng.Sun.COM ([129.144.134.6])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA10952;
	Sun, 30 Sep 2001 08:07:50 -0700 (PDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail4.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id IAA11170;
	Sun, 30 Sep 2001 08:07:44 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.1+Sun/8.12.1) with ESMTP id f8UF71ML000592
	for <mobile-ip-dist@sunroof.eng.sun.com>; Sun, 30 Sep 2001 08:07:01 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.1+Sun/8.12.1/Submit) id f8UF70Jn000591
	for mobile-ip-dist; Sun, 30 Sep 2001 08:07:00 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from engmail3.Eng.Sun.COM (engmail3 [129.144.170.5])
	by sunroof.eng.sun.com (8.12.1+Sun/8.12.1) with ESMTP id f8UF6vML000584
	for <mobile-ip@sunroof.eng.sun.com>; Sun, 30 Sep 2001 08:06:57 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Central.Sun.COM [129.147.5.31])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id IAA04090
	for <mobile-ip@sunroof.eng.sun.com>; Sun, 30 Sep 2001 08:06:59 -0700 (PDT)
Received: from charizard.diameter.org (c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with SMTP id JAA15535
	for <mobile-ip@sunroof.eng.sun.com>; Sun, 30 Sep 2001 09:07:59 -0600 (MDT)
Received: (qmail 16305 invoked by uid 500); 30 Sep 2001 14:52:46 -0000
Date: Sun, 30 Sep 2001 07:52:46 -0700
From: Pat Calhoun <pcalhoun@diameter.org>
To: Pat Calhoun <pcalhoun@diameter.org>
Cc: "Charles E. Perkins" <charliep@IPRG.nokia.com>,
        mobile-ip@sunroof.eng.sun.com
Subject: [mobile-ip] Foot in mouth (was Re: Scalability of Binding Updates)
Message-ID: <20010930075246.H16146@charizard.diameter.org>
References: <MJEMJBGGCLLDLFFAHLJKAEHFDGAA.fredrik.johansson@ipunplugged.com> <Roam.SIMC.2.0.6.1001495690.1688.nordmark@bebop.france> <15282.3298.522332.579900@thomasm-u1.cisco.com> <20010927205547.C1723@charizard.diameter.org> <15284.38307.873861.584422@t <3BB4A085.CCBEF66F@iprg.nokia.com> <20010930074929.G16146@charizard.diameter.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20010930074929.G16146@charizard.diameter.org>; from pcalhoun@diameter.org on Sun, Sep 30, 2001 at 07:49:30AM -0700
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

well, seems like I did it again. I thought this was a private e-mail from
Charles, and my reply all kicked me in the * again :(

It wasn't meant for global distribution, and hope no one takes offense to
what I said. 

sigh... better get coffee and wake up a little before continuing :(

PatC

On Sun, Sep 30, 2001 at 07:49:30AM -0700, Pat Calhoun wrote:
> On Fri, Sep 28, 2001 at 09:08:37AM -0700, Charles E. Perkins wrote:
> > 
> > Hello Pat,
> > 
> > Pat Calhoun wrote:
> > 
> > > apples != oranges. I was never involved in the binding
> > > updates... have for a long time stated this doesn't scale.
> > 
> > It seems to me that there is more than one aspect of scalability
> > that is important here.  In order to have scalable routing, we
> > need to have Binding Updates.  More recently the task has been
> > given to us to develop scalable key exchange techniques.
> > 
> > When that's accomplished, I reckon we will see that mobility
> > management is more scalable, not less scalable, in all the
> > aspects of interest.
> 
> you know what I meant. We talked about PKI scaling at Sun, and how its
> reliance in binding updates didn't make me comfortable. I wasn't trying
> to address the current work in progress, which I haven't spend one ms
> looking at.
> 
> I'm sure that the new solution will be much better, and will address
> my concerns. I just didn't want to take Mike's BS that I was the one
> involved in this one to try to show how AAA keys is bad.
> 
> PatC


From owner-mobile-ip@sunroof.eng.sun.com  Sun Sep 30 20:51:44 2001
Received: from patan.sun.com (patan.Sun.COM [192.18.98.43])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA00435
	for <mobileip-archive@lists.ietf.org>; Sun, 30 Sep 2001 20:51:44 -0400 (EDT)
Received: from engmail3.Eng.Sun.COM ([129.144.170.5])
	by patan.sun.com (8.9.3+Sun/8.9.3) with ESMTP id SAA24320;
	Sun, 30 Sep 2001 18:50:40 -0600 (MDT)
Received: from sunroof.eng.sun.com (sunroof.Eng.Sun.COM [129.146.168.88])
	by engmail3.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id RAA03249;
	Sun, 30 Sep 2001 17:50:40 -0700 (PDT)
Received: from sunroof.eng.sun.com (localhost [127.0.0.1])
	by sunroof.eng.sun.com (8.12.1+Sun/8.12.1) with ESMTP id f910nVML001158
	for <mobile-ip-dist@sunroof.eng.sun.com>; Sun, 30 Sep 2001 17:49:31 -0700 (PDT)
Received: (from majordomo@localhost)
	by sunroof.eng.sun.com (8.12.1+Sun/8.12.1/Submit) id f910nV4j001157
	for mobile-ip-dist; Sun, 30 Sep 2001 17:49:31 -0700 (PDT)
X-Authentication-Warning: sunroof.eng.sun.com: majordomo set sender to owner-mobile-ip@sunroof.eng.sun.com using -f
Received: from eastmail2.East.Sun.COM (eastmail2.East.Sun.COM [129.148.1.241])
	by sunroof.eng.sun.com (8.12.1+Sun/8.12.1) with ESMTP id f910nTML001150
	for <mobile-ip@sunroof.eng.sun.com>; Sun, 30 Sep 2001 17:49:29 -0700 (PDT)
Received: from onion.east.sun.com (onion.East.Sun.COM [129.148.174.110])
	by eastmail2.East.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id UAA21734
	for <mobile-ip@sunroof.eng.sun.com>; Sun, 30 Sep 2001 20:49:32 -0400 (EDT)
Received: (from glass@localhost)
	by onion.east.sun.com (8.9.3+Sun/8.9.3) id UAA11133
	for mobile-ip@sunroof.eng.sun.com; Sun, 30 Sep 2001 20:50:02 -0400 (EDT)
Received: from engmail2.Eng.Sun.COM (engmail2 [129.146.1.25])
	by sunroof.eng.sun.com (8.12.1+Sun/8.12.1) with ESMTP id f8UCnVML000168
	for <mobile-ip@sunroof.eng.sun.com>; Sun, 30 Sep 2001 05:49:31 -0700 (PDT)
Received: from saturn.sun.com (saturn.EBay.Sun.COM [129.150.69.2])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id FAA18394
	for <mobile-ip@sunroof.eng.sun.com>; Sun, 30 Sep 2001 05:49:34 -0700 (PDT)
Received: from netcore.fi (netcore.fi [193.94.160.1])
	by saturn.sun.com (8.9.3+Sun/8.9.3) with ESMTP id FAA02020
	for <mobile-ip@sunroof.eng.sun.com>; Sun, 30 Sep 2001 05:49:33 -0700 (PDT)
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id f8UCnVG27905
	for <mobile-ip@sunroof.eng.sun.com>; Sun, 30 Sep 2001 15:49:31 +0300
Date: Sun, 30 Sep 2001 15:49:31 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: <mobile-ip@sunroof.eng.sun.com>
Subject: [mobile-ip] MIPv6 SecReqs: HA Option processing, HA Dyn Discovery
Message-ID: <Pine.LNX.4.33.0109301519340.27777-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-mobile-ip@sunroof.eng.sun.com
Precedence: bulk
Reply-To: mobile-ip@sunroof.eng.sun.com
List-Archive: <http://playground.sun.com/mobile-ip/>
List-Owner: <mailto:owner-mobile-ip@sunroof.eng.sun.com>
List-Subscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=subscribe>
List-Unsubscribe: <mailto:mobile-ip-request@sunroof.eng.sun.com?body=unsubscribe>

Hello all,

(please keep Cc:, not on the list)

About draft-ietf-mobileip-mipv6-scrty-reqts-00.txt ...

First a gripe about Mobile IPv6...

It appears to me that MIPv6 has gotten awfully "fat" with all of these
options, and may not be globally, securely workable in the end.  Would it
be better to consider simpler scenarios at first, e.g.

 1) MN's would send BU's to CN's first-hop routers (e.g. subnet-router
anycast address); this might scale better especially if IPv6 end-nodes are
supposed to be simple.

Does anyone really believe that a washing machine, connected to an
Intranet using IPv6, MUST be able to process e.g. Home Address Destination
option, or SHOULD be able to process Binding Updates?, or

 2) Reinstate FA's (e.g. by default all IPv6 routers that implement MIPv6)
in the picture, or

 3) Never mind route optimization, always tunnel back to HA


Now to the security requirements draft...

I have may have missed something, but it appears to me that two scenarios
discussed in more detail:

 1) usage of Home Address Option.  Its use need not be authenticated.
Anyone can put it in.  This makes _one-way_ (nice enough for UDP and ICMP)
IP spoofing less than trivial.

One possible fix (needs more analysis):

Home Address option would be processed only if either of these apply:
 - the packet, including Home Address option, is authenticated, or
 - in CN, there exists a Binding between the CoA and Home Address in the
packet (and the Binding was created securely)

caveat here is, of course, that when establishing TCP sessions with CN, if
you can't use Home Address option, the connection is very likely to break
if MN moves...

... but nonetheless, I consider the security to be far more important than
unbroken mobility ...

As can probably be read from above, I consider adding too much required
complexity to _every_ IPv6 node a very bad thing.

 2) the assumption may be flawed in a scenario:

   1  The mobile node and the HA have setup a pre-established security
      association before the mobile node begins to roam and connects to
      the network from a location that is not its home.

This wouldn't appear to work with e.g. 'Dynamic Home Agent Address
Discovery' (10.8), that is, e.g. when the trusted HA dies and MN is away
from home and it needs to find the new HA.  The assumption is valid only
after a HA-MN relationship has been formed.

btw,

   [Ref2]    draft-nikander-ipng-address-ownership-00.txt - Work in
             progress

-01 is the latest in IETF repositories, and even that has been replaced
with the "removed" message.  I don't think it's appropriate to refer to
a draft like this :-)

-- 
Pekka Savola                 "Tell me of difficulties surmounted,
Netcore Oy                   not those you stumble over and fall"
Systems. Networks. Security.  -- Robert Jordan: A Crown of Swords



