From mip6-bounces@ietf.org Mon May 01 05:30:39 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FaUjn-0000Hw-0U; Mon, 01 May 2006 05:30:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FaUjl-0000Hb-DW
	for mip6@ietf.org; Mon, 01 May 2006 05:30:37 -0400
Received: from nproxy.gmail.com ([64.233.182.188])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FaUjk-0001UX-4i
	for mip6@ietf.org; Mon, 01 May 2006 05:30:37 -0400
Received: by nproxy.gmail.com with SMTP id l36so1797158nfa
	for <mip6@ietf.org>; Mon, 01 May 2006 02:30:35 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=Ub+eSHfiZU0oHpHrSeEVp7p+IIk4jFXhmNlP3NqhlWCgqZEf173PUZWbWwuuwGdcVh9SQJ3X/mIC9v1YpFkYyw0/JKmtH6HSxlpVBJf/XSE4wLYuTgptWiCkflXf0Rz56m32jWFh2P/x8DIFPG+l5m1E9UGMtH5AzBIiw6JNzcE=
Received: by 10.49.18.8 with SMTP id v8mr1341940nfi;
	Mon, 01 May 2006 02:30:35 -0700 (PDT)
Received: by 10.49.40.20 with HTTP; Mon, 1 May 2006 02:30:35 -0700 (PDT)
Message-ID: <eaa74a7e0605010230k23762364oc28e2c6e06d184f3@mail.gmail.com>
Date: Mon, 1 May 2006 11:30:35 +0200
From: "Gerardo Giaretta" <gerardo.giaretta@gmail.com>
To: "Alexandru Petrescu" <alexandru.petrescu@motorola.com>
Subject: Re: DHCP options (was Re: [Mip6] Questions on
	draft-ietf-mip6-bootstrapping-integrated-dhc-00.txt)
In-Reply-To: <44525CB5.9030002@motorola.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <445242EE.9050008@motorola.com> <44524E69.6000806@azairenet.com>
	<44525CB5.9030002@motorola.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Alexandru Petrescu <alexandru.petrescu@motorola.com> wrote:

> It's still uncommon to see a document titled "MIPv6 bootsrapping" in the
> MIP6 WG only with DHCP messages modified, no MIP6 messaging, no MIP6
> data structure, no keyword "binding" present, no CoA and only one
> occurence of "home address" (the one to be boot-strapped).  Maybe the
> title should be "DHCPv6-based MIPv6 bootstrapping for integrated scenario=
"?
>

Current title is already DHCPv6-based since it is "MIP6-bootstrapping
via DHCPv6 for the Integrated Scenario". I don't see any big
difference in what you are proposing.

--Gerardo

> Alex
>
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
>

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Mon May 01 05:38:57 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FaUrl-0001L6-62; Mon, 01 May 2006 05:38:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FaUrj-0001Kf-Vt
	for mip6@ietf.org; Mon, 01 May 2006 05:38:51 -0400
Received: from nproxy.gmail.com ([64.233.182.186])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FaUri-0002i4-Ly
	for mip6@ietf.org; Mon, 01 May 2006 05:38:51 -0400
Received: by nproxy.gmail.com with SMTP id l36so1797860nfa
	for <mip6@ietf.org>; Mon, 01 May 2006 02:38:49 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=q2f3C0Iofhak0mNe1+opgZ5bXcLYoBm1yV3S59sMK7e21SphxGiih93HiaiDQMRJ3CwWL3Ln3Yfzr8VvTlLqmVDE4Ms35TkE4T3DB8vp7l63Ng7yQZrkCvd+z9FGZ9SZUzSCiPB8ea3z2ZYI2vH5M6+uqc0yyMWM8RtKDswCEMg=
Received: by 10.49.38.13 with SMTP id q13mr113915nfj;
	Mon, 01 May 2006 02:38:49 -0700 (PDT)
Received: by 10.49.40.20 with HTTP; Mon, 1 May 2006 02:38:49 -0700 (PDT)
Message-ID: <eaa74a7e0605010238s36eef57fm23b8fba6b3d9eaac@mail.gmail.com>
Date: Mon, 1 May 2006 11:38:49 +0200
From: "Gerardo Giaretta" <gerardo.giaretta@gmail.com>
To: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
Subject: Re: [Mip6] How to store DNS records about HAs,
	(draft-ietf-mip6-bootstrapping-split-02.txt)?
In-Reply-To: <8A16DAD84432534FBFC19FD92B50512F05B97A15@ames.starentnetworks.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <8A16DAD84432534FBFC19FD92B50512F05B97A15@ames.starentnetworks.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Cc: mip6@ietf.org,
	COMBES Jean-Michel RD-MAPS-ISS <jeanmichel.combes@francetelecom.com>,
	Alexandru Petrescu <alexandru.petrescu@motorola.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi Alex and Kuntal,

one comment below...

> > If operator considers storing 3 fqdns in each phone as not minimal,
> what
> > protocol would operator use to store each location's HA address in the
> > DNS?  And how would MN know to query the DNS for a specific location
> HA
> > when all it has is just one fqdn?
> >
> [KC>] Normally, allocation of the most optimum home agent based on the
> MN's point of attachment is done in the network. I think your question
> is a valid one, i.e. how does the operator do that using DNS. May be
> some clarification is required on this (if not there already).
>

Currently this is not possible using the solution defined for split
scenario. In this draft, only HA discovery is possible and this is not
possible to achieve a "location-based" HA assignment. Note that this
is also a consequence of split scenario definition: there is no link
between the location of the MN (i.e. ASP) and the MSP.

IMO, this limitation is well covered in the draft, also discussing
load balancing. But, please any suggestion on how to improve the
document is welcome.

I think HA assignment is much more useful in integrated scenario; this
is why the DT chose DHCP in that scenario.

--Gerardo
> > Alex
>
>
>
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
>

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Mon May 01 12:17:03 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fab4r-0005yh-7i; Mon, 01 May 2006 12:16:49 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fab4p-0005yb-9G
	for mip6@ietf.org; Mon, 01 May 2006 12:16:47 -0400
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fab4n-0001KA-SH
	for mip6@ietf.org; Mon, 01 May 2006 12:16:47 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by laposte.rennes.enst-bretagne.fr (8.13.4/8.13.4/2004.10.03) with
	ESMTP id k41GGdCx013079; Mon, 1 May 2006 18:16:39 +0200
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[192.44.77.29])
	by laposte.rennes.enst-bretagne.fr (8.13.4/8.13.4/2004.09.01) with
	ESMTP id k41GGcWl013074; Mon, 1 May 2006 18:16:38 +0200
Received: from givry.rennes.enst-bretagne.fr
	(localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.13.1/8.13.1) with ESMTP id
	k41GGaM6026628; Mon, 1 May 2006 18:16:37 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200605011616.k41GGaM6026628@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@point6.net>
To: "Soliman, Hesham" <hsoliman@qualcomm.com>
Subject: Re: [Mip6] WG Last call: draft-ietf-mip6-ikev2-ipsec-06.txt 
In-reply-to: Your message of Sun, 30 Apr 2006 11:12:13 PDT.
	<1487A357FD2ED544B8AD29E528FF9DF00255622A@NAEX06.na.qualcomm.com> 
Date: Mon, 01 May 2006 18:16:36 +0200
X-Virus-Scanned: amavisd-new at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: Gopal Dommety <gdommety@cisco.com>, mip6@ietf.org, jari.arkko@ericsson.com,
	Basavaraj Patil <basavaraj.patil@nokia.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:
   
   => Ok. So at least there is one agreement here, that is, for the 
   "MIPv6 application" transport mode makes sense since the communication
   is between MN and HA.

=> yes, transport mode is this case is the best solution, this is why
it has been *the* solution before the tunnel all mode proposal.

   Also, there is no double tunneling since there is 
   only one header in this case and the HAO.

=> note that the HAO can be considered as a degenerated tunnel.

   There would be unnecessary
   tunnelling IMO in tunnel mode for the BU or MPD.
   
=> the tunnel all mode is just full tunnel in place of degenerated tunnel,
something less bad than double tunnel...
   
Regards   
   
Francis.Dupont@point6.net

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Mon May 01 13:10:10 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FabuP-0007Z1-1u; Mon, 01 May 2006 13:10:05 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FabuN-0007Xs-KG
	for mip6@ietf.org; Mon, 01 May 2006 13:10:03 -0400
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FabuN-0003Sk-6e
	for mip6@ietf.org; Mon, 01 May 2006 13:10:03 -0400
Received: from c1-vpn2.isi.edu (c1-vpn2.isi.edu [128.9.176.28])
	by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id k41H9DQ27662
	for <mip6@ietf.org>; Mon, 1 May 2006 10:09:13 -0700 (PDT)
From: Wei Ye <weiye@ISI.EDU>
To: mip6@ietf.org
Content-Type: text/plain; charset=UTF-8
Date: Mon, 01 May 2006 10:09:10 -0700
Message-Id: <1146503350.3398.27.camel@localhost.localdomain>
Mime-Version: 1.0
X-Mailer: Evolution 2.2.3 (2.2.3-2.fc4) 
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: weiye@isi.edu
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by boreas.isi.edu id
	k41H9DQ27662
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 29dc808194f5fb921c09d0040806d6eb
Subject: [Mip6] CFP: ACM Workshop on Underwater Networks (WUWNet 2006)
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Our Apologies if you have received multiple copies of the CFP.

Volkan Rodoplu and Wei Ye
WUWNet 2006 Publicity Co-Chairs


-----------------------------------------------------
      The First ACM International Workshop on
         UnderWater Networks (WUWNet 2006)
           http://wuwnet.engr.uconn.edu/

        In conjunction with ACM MobiCom 2006
                 September 29, 2006
           Los Angeles, California, USA
            Sponsored by ACM SIGMOBILE
-----------------------------------------------------


Overview & Scope =20
****************

The oceans cover 71% of the earth's surface and represent=20
one of the least explored frontiers, yet the oceans are=20
integral to climate regulation, nutrient production, oil=20
retrieval and transportation. As such, there is significant=20
interest in monitoring aquatic environments for scientific,=20
environmental, commercial, safety, and military reasons.=20
While there is a need for highly precise, real-time, fine=20
grained spatio-temporal sampling of the ocean environment,=20
current methods such as remote telemetry and sequential=20
local sensing cannot satisfy current needs, let alone=20
future needs. The notion of an underwater network is=20
relatively new due to the lack of maturity of underwater=20
acoustic communication. However, networks are necessary=20
in order to achieve the monitoring goals noted above. The=20
physical challenges of acoustic underwater communication=20
require us to completely re-think how a network should be=20
designed and deployed in this environment. Challenges to=20
be overcome by underwater acoustic modem and network=20
designers include: severely limited range-dependent bandwidth=20
and attenuation, extensive time-varying multipath propagation,=20
and low speed of sound propagation in water resulting in long=20
propagation delays. Moreover, a unique feature of underwater=20
networks is that the environment is constantly mobile, naturally=20
causing the node passive mobility. All the above distinct=20
features of underwater networks yield new challenges for every=20
level of the network protocol suite.

The goal of the proposed workshop is to bring together=20
researchers and practioners in areas relevant to underwater=20
networks. Thus, many layers of the "stack" from the physical=20
layer to the application layer will be represented. The objective=20
is to serve as a forum for presenting state of the art research,=20
exchanging ideas and experiences, and facilitating interaction=20
and collaboration.=20

The workshop will span one day, including presentations of technical=20
papers, tutorial/survey papers, a panel session and a poster/demo=20
session. Submissions for regular technical papers and poster/demo=20
extended abstracts should describe original research, not published=20
or currently under review for other workshops, conferences, or
journals.  =20

Topics of interest include, but are not limited to:

-	Network architecture design=20
-	Efficient acoustic communications
-	Cooperative underwater communications
-	Medium access control
-	Routing and forwarding
-	Reliable data transfer
-	Security and robustness
-	Power management
-	Data storage and management=20
-	Localization and synchronization
-	Data fusion, dissemination, tracking
-	Network modeling and simulations
-	Capacity analysis
-	New techniques for aquatic applications
-	New applications for underwater networks


Submission Guidelines
*********************

All paper submissions will be handled electronically. Papers must=20
be in PDF format, no longer than 8 pages for regular papers (10=20
pages for tutorial/survey papers and 4 pages for poster/demo papers),=20
and must follow ACM single-space, double-column format, 10 pt.=20
Submitted papers will be judged based on their quality and novelty=20
through a rigorous review process. Over-length papers will be=20
automatically rejected. Detailed instructions for paper submission
are posted on the workshop website.


Important Dates
***************

Submission deadline: June 30, 2006
Acceptance notification: July 28, 2006
Camera-ready version: August 11, 2006
Workshop date: September 29, 2006


Organizing Committee
********************
=20
General Co-chairs:=20

Jun-Hong Cui (University of Connecticut)=20
Urbashi Mitra (University of Southern California)

Technical Program Co-chairs:

Kevin Fall (Intel Research, Berkeley)
Milica Stojanovic (MIT/WHOI)

Publicity Co-chairs:

Volkan Rodoplu (University of California, Santa Barbara)
Wei Ye (USC/ISI)

Treasurer:

Shengli Zhou (University of Connecticut)

Publications Chair:

Xiuzhen Cheng (George Washington University)


Technical Program Committee
***************************

Ian Akyildiz (Georgia Institute of Technology)=20
Lee Freitag (Woods Hole Oceanographic Institution)
Mario Gerla (University of California, Los Angeles)
Jo=C3=A3o Pedro Gomes (Instituto Superior T=C3=A9cnico, Portugal)
John Heidemann (USC/ISI)
Ronald A. Iltis (University of California, Santa Barbara)
Jim Kurose (University of Massachusetts, Amherst)
Mehul Motani (National University of Singapore)
Joseph A. Rice (Naval Postgraduate School)
Daniela Rus (Massachusetts Institute of Technology)
Mani Srivastava (University of California, Los Angeles)
Yongguang Zhang (Microsoft Research Asia, China)
Michele Zorzi (Universita'di Ferrara, Italy)=20



_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Mon May 01 14:20:08 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Faczk-0004V4-Cj; Mon, 01 May 2006 14:19:40 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Faczj-0004Uz-9J
	for mip6@ietf.org; Mon, 01 May 2006 14:19:39 -0400
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Faczf-0005wV-TR
	for mip6@ietf.org; Mon, 01 May 2006 14:19:39 -0400
Received: from magus.qualcomm.com (magus.qualcomm.com [129.46.61.148])
	by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k41IJWxH009006
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Mon, 1 May 2006 11:19:32 -0700
Received: from NAEXBR04.na.qualcomm.com (naexbr04.qualcomm.com [10.46.141.42])
	by magus.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k41IJQlT022181; Mon, 1 May 2006 11:19:31 -0700 (PDT)
Received: from NAEX06.na.qualcomm.com ([129.46.135.161]) by
	NAEXBR04.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 1 May 2006 11:19:13 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] WG Last call: draft-ietf-mip6-ikev2-ipsec-06.txt 
Date: Mon, 1 May 2006 11:19:12 -0700
Message-ID: <1487A357FD2ED544B8AD29E528FF9DF0025566AC@NAEX06.na.qualcomm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] WG Last call: draft-ietf-mip6-ikev2-ipsec-06.txt 
Thread-Index: AcZtOrFBfcYrHpLVQTeZh9GUL5+VgAAEOtIA
From: "Soliman, Hesham" <hsoliman@qualcomm.com>
To: <Francis.Dupont@point6.net>
X-OriginalArrivalTime: 01 May 2006 18:19:14.0128 (UTC)
	FILETIME=[C0348500:01C66D4B]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: Gopal Dommety <gdommety@cisco.com>, mip6@ietf.org, jari.arkko@ericsson.com,
	Basavaraj Patil <basavaraj.patil@nokia.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

=20
 >    Also, there is no double tunneling since there is=20
 >    only one header in this case and the HAO.
 >=20
 > =3D> note that the HAO can be considered as a degenerated tunnel.

=3D> Sure.

 >=20
 >    There would be unnecessary
 >    tunnelling IMO in tunnel mode for the BU or MPD.
 >   =20
 > =3D> the tunnel all mode is just full tunnel in place of=20
 > degenerated tunnel,
 > something less bad than double tunnel...

=3D> But we don't have a double tunnel today. So no need
for the "less bad" either.=20

Hesham

 >   =20
 > Regards  =20
 >   =20
 > Francis.Dupont@point6.net
 >=20

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Mon May 01 17:58:17 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FagP3-0004Gc-AS; Mon, 01 May 2006 17:58:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FagP2-0004GV-80
	for mip6@ietf.org; Mon, 01 May 2006 17:58:00 -0400
Received: from mail1.azairenet.com ([66.92.223.4] helo=bart.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FagP1-0007Q2-Lw
	for mip6@ietf.org; Mon, 01 May 2006 17:58:00 -0400
Received: from [10.1.201.19] ([10.1.201.19]) by bart.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Mon, 1 May 2006 14:57:57 -0700
Message-ID: <44568464.1090807@azairenet.com>
Date: Mon, 01 May 2006 14:57:56 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.2 (Windows/20060308)
MIME-Version: 1.0
To: Gerardo Giaretta <gerardo.giaretta@gmail.com>,  hartmans-ietf@mit.edu
Subject: Re: [Mip6] FW: DISCUSS and COMMENT: draft-ietf-mip6-bootstrap-ps
References: <eaa74a7e0604301330y4bc37bcamd953a713cf50c95a@mail.gmail.com>
In-Reply-To: <eaa74a7e0604301330y4bc37bcamd953a713cf50c95a@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-OriginalArrivalTime: 01 May 2006 21:57:57.0069 (UTC)
	FILETIME=[4E1667D0:01C66D6A]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b2809b6f39decc6de467dcf252f42af1
Cc: mip6@ietf.org, Basavaraj Patil <Basavaraj.Patil@nokia.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Gerardo Giaretta wrote:
> Hi Sam,
> 
> thanks for the comments and sorry for very late answers.
> 
> Concerning the EAP issue, I think that both solutions that are under
> definition in the WG does not follow the directions you mentioned.
> After your and others' comments (also during ICOS BOF and HOAKEY BOF)
> the WG has been producing solutions where network access
> authentication and mobility service authentication are considered
> fully separated. It seems to me that this problem statement does not
> suggest this kind of solutions. Please let me know if you think some
> clarifying text needs to be added to this problem statement.
> 
> Concerning rfc4285, the WG is currently not working on a solutions for
> bootstrapping rfc4285 SAs. I'm OK with removing all references to
> rfc4285. Is this your suggestion?

couple of contexts where RFC 4285 is mentioned are
okay. RFC 4285 is mentioned as a mechanism for
securing the BU. thats is fine. we could say it
exists, but this problem statement does not address
4285 bootstrapping. completely ignoring it would
be a bad idea.

Vijay

> 
>> Comment:
>> The claim in section 5.2.1 that use of certificates would require
>> deploying a PKI is false.  I do agree that certificates do not align
>> well with AAA. I'd recommend rewording as "Certificates are not easily
>> supported by traditional AAA infrastructures."
>>
> 
> Done.
> 
> --Gerardo
> 
>> -----Original Message-----
>> From: Basavaraj Patil [mailto:basavaraj.patil@nokia.com]
>> Sent: mercoledì 1 marzo 2006 22.16
>> To: mip6@ietf.org
>> Subject: [Mip6] FW: DISCUSS and COMMENT: draft-ietf-mip6-bootstrap-ps
>>
>>
>> FYI,
>>
>> ------ Forwarded Message
>> > From: ext Sam Hartman <hartmans-ietf@mit.edu>
>> > Date: Wed, 01 Mar 2006 16:03:22 -0500
>> > To: <iesg@ietf.org>
>> > Cc: <basavaraj.patil@nokia.com>, <gdommety@cisco.com>
>> > Subject: DISCUSS and COMMENT: draft-ietf-mip6-bootstrap-ps
>> >
>> > Discuss:
>> > First, thanks for a good job on a well written problem
>> statement.  My
>> > concerns here are concernes about the document but can be
>> interpreted
>> > as early warnings about the direction the WG seems to be taking.
>> > Addressing the concerns against the document can probably
>> be done very
>> > simply, but it is important to discuss the working group's direction
>> > now to make sure that you will not end up with a discuss challenging
>> > something fundamental about your solution when it comes to the IESG.
>> >
>> > In section 7.2 you discuss using the authentication to both set up
>> > network access and mobility access.  I don't think this is
>> compatible
>> > with how the EAP working group and security area invision EAP being
>> > used. For example the key management framework requires
>> that all keys
>> > based on the EMSK be generated at the beginning of the
>> exchange. We've
>> > explicitly resisted several attempts to use EAP keying information
>> > used to set up network access to later generate keys for other
>> > purposes.  Both mobility and network access are at least valid EAP
>> > applications.  I recommend that you note that the question
>> of whether
>> > this authentication can be reused is open in your document.  I
>> > recommend that you get together with Russ Housley, Jari,
>> myself and the EAP
>> > community and decide whether this use is OK before designing a
>> > solution that assumes you will be able to do this.
>> >
>> > I'm assuming that this problem statement is for a standards track
>> > solution.  As such, I don't think considering RFC 4285 is
>> appropriate.
>> > In particular I don't think it makes sense for us to base standards
>> > trackrequirements on a protocol we were unwilling to
>> standardize.  It
>> > feels too much like using the informational RFC series as a
>> mechanism
>> > for doing ongoing standards work without meeting our
>> requirements for
>> > review.  If the working group believes that something like
>> RFC 4285 is
>> > needed, then the working group should commit to doing the necessary
>> > work to make a standard in this space: write a service model for
>> > Mobile IP security and then write both the authentication
>> protocol and
>> > the IPsec security solution as architectural blocks that fit that
>> > model.  If the working group does not want to do this work, then RFC
>> > 4285-like solutions need not influence requirements here.
>> >
>> > Comment:
>> > The claim in section 5.2.1 that use of certificates would require
>> > deploying a PKI is false.  I do agree that certificates do not align
>> > well with AAA. I'd recommend rewording as "Certificates are
>> not easily
>> > supported by traditional AAA infrastructures."
>> >
>>
>> ------ End of Forwarded Message
>>
>>
>> _______________________________________________
>> Mip6 mailing list
>> Mip6@ietf.org
>> https://www1.ietf.org/mailman/listinfo/mip6
>>
> 
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6


_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Tue May 02 04:17:37 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Faq4b-0004Eu-0t; Tue, 02 May 2006 04:17:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Faq4Z-0004EE-3A
	for mip6@ietf.org; Tue, 02 May 2006 04:17:31 -0400
Received: from nproxy.gmail.com ([64.233.182.191])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Faq4X-0005vH-QJ
	for mip6@ietf.org; Tue, 02 May 2006 04:17:31 -0400
Received: by nproxy.gmail.com with SMTP id l36so1953009nfa
	for <mip6@ietf.org>; Tue, 02 May 2006 01:17:28 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=hcg54fab1zM5eaTda2BtKJF4xc9Pvyf8GJuZb8ZFkn990HOT4hwPzTREeGGR5P9EkyM08RtzO8kT6eTpn7YMZJtQON5eV+punv22478Ix4jaUQdHglq5JBDP5Z/qwPGmcN6Y/PDoZ6AZCpqAEl3qzAG/TdLrPkOzy12gKWwaeUA=
Received: by 10.48.214.2 with SMTP id m2mr298236nfg;
	Tue, 02 May 2006 01:17:28 -0700 (PDT)
Received: by 10.49.40.20 with HTTP; Tue, 2 May 2006 01:17:28 -0700 (PDT)
Message-ID: <eaa74a7e0605020117n31ff475bie7dc2541dd8e197@mail.gmail.com>
Date: Tue, 2 May 2006 10:17:28 +0200
From: "Gerardo Giaretta" <gerardo.giaretta@gmail.com>
To: "Sam Hartman" <hartmans-ietf@mit.edu>
Subject: Re: [Mip6] FW: DISCUSS and COMMENT: draft-ietf-mip6-bootstrap-ps
In-Reply-To: <tslpsixe68p.fsf@cz.mit.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <eaa74a7e0604301330y4bc37bcamd953a713cf50c95a@mail.gmail.com>
	<44568464.1090807@azairenet.com> <tslpsixe68p.fsf@cz.mit.edu>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Cc: mip6@ietf.org, Basavaraj Patil <Basavaraj.Patil@nokia.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi Sam,

sorry for that. It's my fault.

Find the email below.

--Gerardo

On 5/2/06, Sam Hartman <hartmans-ietf@mit.edu> wrote:
> Hi.  I don't seem to have the original mail to which this is a reply.
>
>

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

Hi Sam,

thanks for the comments and sorry for very late answers.

Concerning the EAP issue, I think that both solutions that are under
definition in the WG does not follow the directions you mentioned.
After your and others' comments (also during ICOS BOF and HOAKEY BOF)
the WG has been producing solutions where network access
authentication and mobility service authentication are considered
fully separated. It seems to me that this problem statement does not
suggest this kind of solutions. Please let me know if you think some
clarifying text needs to be added to this problem statement.

Concerning rfc4285, the WG is currently not working on a solutions for
bootstrapping rfc4285 SAs. I'm OK with removing all references to
rfc4285. Is this your suggestion?

> Comment:
> The claim in section 5.2.1 that use of certificates would require
> deploying a PKI is false.  I do agree that certificates do not align
> well with AAA. I'd recommend rewording as "Certificates are not easily
> supported by traditional AAA infrastructures."
>

Done.

--Gerardo

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Tue May 02 08:01:56 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FatZX-0002x8-2v; Tue, 02 May 2006 08:01:43 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FatZU-0002rf-Gv
	for mip6@ietf.org; Tue, 02 May 2006 08:01:40 -0400
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FatZU-0007iP-9E
	for mip6@ietf.org; Tue, 02 May 2006 08:01:40 -0400
Received: from az33exr03.mot.com ([10.64.251.233])
	by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id k42CIWb7013078;
	Tue, 2 May 2006 05:18:32 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by az33exr03.mot.com (8.13.1/8.13.0) with ESMTP id k42CIV4s029926;
	Tue, 2 May 2006 07:18:32 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id 5B29A865980; Tue,  2 May 2006 14:01:33 +0200 (CEST)
Message-ID: <44574A1D.2060603@motorola.com>
Date: Tue, 02 May 2006 14:01:33 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: Gerardo Giaretta <gerardo.giaretta@gmail.com>
Subject: Re: [Mip6] How to store DNS records about HAs,
	(draft-ietf-mip6-bootstrapping-split-02.txt)?
References: <8A16DAD84432534FBFC19FD92B50512F05B97A15@ames.starentnetworks.com>
	<eaa74a7e0605010238s36eef57fm23b8fba6b3d9eaac@mail.gmail.com>
In-Reply-To: <eaa74a7e0605010238s36eef57fm23b8fba6b3d9eaac@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAQAAAAQ=
X-White-List-Member: TRUE
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Cc: mip6@ietf.org,
	COMBES Jean-Michel RD-MAPS-ISS <jeanmichel.combes@francetelecom.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Gerardo Giaretta wrote:
> Hi Alex and Kuntal,
> 
> one comment below...
> 
>>> If operator considers storing 3 fqdns in each phone as not 
>>> minimal,
>> what
>>> protocol would operator use to store each location's HA address 
>>> in the DNS?  And how would MN know to query the DNS for a 
>>> specific location
>> HA
>>> when all it has is just one fqdn?
>>> 
>> [KC>] Normally, allocation of the most optimum home agent based on 
>> the MN's point of attachment is done in the network. I think your 
>> question is a valid one, i.e. how does the operator do that using 
>> DNS. May be some clarification is required on this (if not there 
>> already).
>> 
> 
> Currently this is not possible using the solution defined for split 
> scenario. In this draft, only HA discovery is possible and this is 
> not possible to achieve a "location-based" HA assignment. Note that 
> this is also a consequence of split scenario definition: there is no 
> link between the location of the MN (i.e. ASP) and the MSP.
> 
> IMO, this limitation is well covered in the draft, also discussing 
> load balancing. But, please any suggestion on how to improve the 
> document is welcome.

Yes.

Improving a document is a useful.  It's also good to keep the document
short and tractable.

For split, (1) specify that HA updates the DNS with its own address,
maybe via DHCP, with a new type of SRV record or (2) eliminate the claim
of SRV helping with load balancing.  The latter seems to me to be least
work.

For integrated, clarify what is the pre-configured information before
bootstrapping (NAI apparently).  Clarify that a domain name encompasses
several subnets each comprising its own set of HAs.  Clarify how using
only one NAI key for searching addresses this search (a search should
retrieve only one subnet's set of HAs, not entire domain's).  This seems
much work to me.

Does this make sense?

Alex
PS: I don't think there's a clearcut  difference between "HA discovery"
and "HA assignment".  DHAAD is mainly discovery but its effect is that
MN gets its HA address, thus it is assigned the HA address.

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Tue May 02 08:02:48 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fataa-0004DZ-Fw; Tue, 02 May 2006 08:02:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FataY-000492-Mk
	for mip6@ietf.org; Tue, 02 May 2006 08:02:46 -0400
Received: from motgate7.mot.com ([129.188.136.7])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FataX-0007mA-Fu
	for mip6@ietf.org; Tue, 02 May 2006 08:02:46 -0400
Received: from az33exr02.mot.com ([10.64.251.232])
	by motgate7.mot.com (8.12.11/Motgate7) with ESMTP id k42CYi4f007391;
	Tue, 2 May 2006 05:34:45 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by az33exr02.mot.com (8.13.1/8.13.0) with ESMTP id k42CGLsY022478;
	Tue, 2 May 2006 07:16:21 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id 0EE2D865980; Tue,  2 May 2006 14:02:41 +0200 (CEST)
Message-ID: <44574A60.9080803@motorola.com>
Date: Tue, 02 May 2006 14:02:40 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: Gerardo Giaretta <gerardo.giaretta@gmail.com>
Subject: Re: DHCP options (was Re: [Mip6] Questions on
	draft-ietf-mip6-bootstrapping-integrated-dhc-00.txt)
References: <445242EE.9050008@motorola.com> <44524E69.6000806@azairenet.com>	
	<44525CB5.9030002@motorola.com>
	<eaa74a7e0605010230k23762364oc28e2c6e06d184f3@mail.gmail.com>
In-Reply-To: <eaa74a7e0605010230k23762364oc28e2c6e06d184f3@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAQAAAAQ=
X-White-List-Member: TRUE
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Gerardo Giaretta wrote:
> Alexandru Petrescu <alexandru.petrescu@motorola.com> wrote:
> 
>> It's still uncommon to see a document titled "MIPv6 bootsrapping" 
>> in the MIP6 WG only with DHCP messages modified, no MIP6 messaging,
>>  no MIP6 data structure, no keyword "binding" present, no CoA and 
>> only one occurence of "home address" (the one to be boot-strapped).
>>  Maybe the title should be "DHCPv6-based MIPv6 bootstrapping for 
>> integrated scenario"?
>> 
> 
> Current title is already DHCPv6-based since it is "MIP6-bootstrapping
>  via DHCPv6 for the Integrated Scenario". I don't see any big 
> difference in what you are proposing.

Ok.  We could argue endlessly about a title, but you seem to agree that
the draft is mainly about DHCP, me too.

Alex


_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Tue May 02 08:26:45 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fatxg-0001XD-4m; Tue, 02 May 2006 08:26:40 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fatxf-0001X8-5z
	for mip6@ietf.org; Tue, 02 May 2006 08:26:39 -0400
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fatxe-0000ad-Ti
	for mip6@ietf.org; Tue, 02 May 2006 08:26:39 -0400
Received: from il06exr03.mot.com (il06exr03.mot.com [129.188.137.133])
	by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id k42ChN8h018753;
	Tue, 2 May 2006 05:43:23 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by il06exr03.mot.com (8.13.1/8.13.0) with ESMTP id k42Ci5BP027903;
	Tue, 2 May 2006 07:44:06 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id 79BCE865980; Tue,  2 May 2006 14:26:24 +0200 (CEST)
Message-ID: <44574FF0.1080700@motorola.com>
Date: Tue, 02 May 2006 14:26:24 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: Henrik Levkowetz <henrik@levkowetz.com>
References: <1487A357FD2ED544B8AD29E528FF9DF0024F2419@NAEX06.na.qualcomm.com>
	<44513C22.9090706@motorola.com>
	<E0CD2CF1-BA63-427D-8151-BB4DB0DF3A78@sfc.wide.ad.jp>
	<445244F0.4010905@motorola.com> <44524D69.6080709@levkowetz.com>
	<44525415.3050103@motorola.com>
	<445262C7.6050603@levkowetz.com> <44526F9E.70709@motorola.com>
	<44529BC4.3040609@levkowetz.com> <4452A40F.9080409@motorola.com>
	<44533034.7070106@levkowetz.com>
In-Reply-To: <44533034.7070106@levkowetz.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAQAAAAQ=
X-White-List-Member: TRUE
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Cc: "Zhang, Qiang \[NTK\]" <Qiang.Zhang@sprint.com>,
	Ryuji Wakikawa <ryuji@sfc.wide.ad.jp>, "Soliman,
	Hesham" <hsoliman@qualcomm.com>, mip6@ietf.org
Subject: [Mip6] Re: NAT,
	heartbeats and app interruptions (was: When behind NAT...)
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi Henrik, thanks for the reply.  If there's interest I'll try to split
the discussion into simplest topics.

Henrik Levkowetz wrote:
>> Do you think a DS-MIPv6 section about "Assumptions on NAT for NAT 
>> Traversal for DS-MIPv6" would be appropriate?  Know that I'm not 
>> trying to have my name in the draft.  Anybody can write it.  Should
>>  at least contain "This draft assumes that the NAT leaves open the
>>  DS-MIPv6 port number [TBD]".
> 
> No.  That's not even a NAT functionality you're talking about, it's a
>  firewall functionality.

I think you're right.  That port left open is firewall functionality in
common thinking.

But then how about a section with assumptions more precisely on NAT, not
firewalling.  For example:

"The NAT functionality assumed by this document is the following.  A NAT
  box translates IPv4 private address space into one (or more) IPv4
  public addresses.  NAT receives a packet from MN addressed to its HA,
  hashes it into a unique id, saves state keyed by this id, changes
  the source address into its IP public address and finally forwards to
  HA.  Then NAT receives a response packet from HA, hashes it into the
  same unique id, searches its set of states to find out the private IP
  address of MN, substitutes the dst address with the private address,
  and forwards to MN."

Do we have the same high-level understanding of NAT working this way?

If yes, then there are NATs who when they receive a UDP packet from MN
will change the src port number too (not only the src IP address).  Do
we agree on the existence of such NATs?

If yes, then there are NATs who will keep the mentioned state active for
about 5 minutes.  After the 5 minutes they will change again the src
port number and will save a different state (even if heartbeating every
1s).  Do we agree? (the reason why NAT forces to change this src port
number may be because there are only 65535 available and active users
are more than that).

If yes, there may be a UDPv6 application on HA streaming packets to MN.
  This app only sends UDPv6 packets to MN for one hour, during which time
MN does not send any UDPv6 app messaging to HA.  Do we agree that (in
absence of tunnel heartbeat) the packet stream from HA to MN will be
interrupted after 5 minutes, until MN sends a packet to HA?

If yes, and if we add tunnel maintenance in the picture, do we agree
that that UDPv6 streaming application may be stopped at worst until next
heartbeat is sent by MN (the 120seconds figure was mentioned)?

Alex

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Tue May 02 08:48:46 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FauIz-0000K4-2s; Tue, 02 May 2006 08:48:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FauIy-0000Jz-0A
	for mip6@ietf.org; Tue, 02 May 2006 08:48:40 -0400
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FauIw-0001y6-Nq
	for mip6@ietf.org; Tue, 02 May 2006 08:48:39 -0400
Received: from il06exr02.mot.com (il06exr02.mot.com [129.188.137.132])
	by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id k42D5Zdi024294;
	Tue, 2 May 2006 06:05:35 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by il06exr02.mot.com (8.13.1/8.13.0) with ESMTP id k42D3Ucx021598;
	Tue, 2 May 2006 08:03:30 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id 35E67865980; Tue,  2 May 2006 14:48:37 +0200 (CEST)
Message-ID: <44575524.6050200@motorola.com>
Date: Tue, 02 May 2006 14:48:36 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: Henrik Levkowetz <henrik@levkowetz.com>
References: <1487A357FD2ED544B8AD29E528FF9DF0024F2419@NAEX06.na.qualcomm.com>
	<44513C22.9090706@motorola.com>
	<E0CD2CF1-BA63-427D-8151-BB4DB0DF3A78@sfc.wide.ad.jp>
	<445244F0.4010905@motorola.com> <44524D69.6080709@levkowetz.com>
	<44525415.3050103@motorola.com>
	<445262C7.6050603@levkowetz.com> <44526F9E.70709@motorola.com>
	<44529BC4.3040609@levkowetz.com> <4452A40F.9080409@motorola.com>
	<44533034.7070106@levkowetz.com>
In-Reply-To: <44533034.7070106@levkowetz.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAQAAAAQ=
X-White-List-Member: TRUE
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: "Zhang, Qiang \[NTK\]" <Qiang.Zhang@sprint.com>,
	Ryuji Wakikawa <ryuji@sfc.wide.ad.jp>, "Soliman,
	Hesham" <hsoliman@qualcomm.com>, mip6@ietf.org
Subject: [Mip6] Re: sometimes keepalives won't keep NAT state up
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Henrik Levkowetz wrote:
> Hi,
> 
> on 2006-04-29 01:23 Alexandru Petrescu said the following:

> "The keepalive is every second RA and ping from both directions" is
> very far from what's described in 3519.

Well, 3519 says it should be a UDP-encapsulated icmp echo request,
right?  So that's what I was doing.  Ping encapsulated in the UDP
tunnel.  Using RA is indeed not specified.  I've tried RA in UDPv4
because I thought that NAT forces tunnel change because NAT would
consider ICMP as tunnel keepalive, and assumed NAT knows nothing about
IPv6/ICMPv6.  So in my tests while the 1s ping runs there are also 1s
RAs from [GW], hoping state would not change, but it does.

Also, 3519 says that MN should send keepalive if there's no ongoing udp
app packets for K seconds.  But this comes down to the same problem when
NAT changes state even if keepalive running.  Unless that K seconds is
in the order of milliseconds, the app streaming from [GW] to MN may
suffer interruptions.  No?

Do you think one can choose an appropriate K such that the NAT will keep
state unchanged (don't change src port number)?

Alex

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Tue May 02 09:28:26 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FauvH-0008VL-26; Tue, 02 May 2006 09:28:15 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FauvG-0008VG-NS
	for mip6@ietf.org; Tue, 02 May 2006 09:28:14 -0400
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FauvG-0003ij-B5
	for mip6@ietf.org; Tue, 02 May 2006 09:28:14 -0400
Received: from il06exr04.mot.com (il06exr04.mot.com [129.188.137.134])
	by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id k42Dj2rP005368;
	Tue, 2 May 2006 06:45:02 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by il06exr04.mot.com (8.13.1/8.13.0) with ESMTP id k42DgFnF022165;
	Tue, 2 May 2006 08:42:16 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id C3D28865980; Tue,  2 May 2006 15:28:03 +0200 (CEST)
Message-ID: <44575E63.2090805@motorola.com>
Date: Tue, 02 May 2006 15:28:03 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: Henrik Levkowetz <henrik@levkowetz.com>
References: <1487A357FD2ED544B8AD29E528FF9DF0024F2419@NAEX06.na.qualcomm.com>
	<44513C22.9090706@motorola.com>
	<E0CD2CF1-BA63-427D-8151-BB4DB0DF3A78@sfc.wide.ad.jp>
	<445244F0.4010905@motorola.com> <44524D69.6080709@levkowetz.com>
	<44525415.3050103@motorola.com>
	<445262C7.6050603@levkowetz.com> <44526F9E.70709@motorola.com>
	<44529BC4.3040609@levkowetz.com> <4452A40F.9080409@motorola.com>
	<44533034.7070106@levkowetz.com>
In-Reply-To: <44533034.7070106@levkowetz.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAQAAAAQ=
X-White-List-Member: TRUE
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8fbbaa16f9fd29df280814cb95ae2290
Cc: "Zhang, Qiang \[NTK\]" <Qiang.Zhang@sprint.com>,
	Ryuji Wakikawa <ryuji@sfc.wide.ad.jp>, "Soliman,
	Hesham" <hsoliman@qualcomm.com>, mip6@ietf.org
Subject: [Mip6] Re: When behind NAT MN should have a real IPv6 CoA not
 mapped (was: Again on port number for DS-MIPv6)
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Henrik Levkowetz wrote:

> When the MN acquires an IPv4 address in an IPv4-only network and uses
>  that as a MIPv6 CoA, there is **no** IPv6 CoA involved anywhere.

Ok, if there is an RA on the UDP tunnel and MN has an EUI-64 and
auto-configures an address, is it abnormal to call it an IPv6 CoA?

If HA uses the IPv6 address MN uses on its UDP tunnel interface as a
MIPv6 CoA, I think the terminology is right.

I suggest we call the MN's IPv6 v4-mapped private IPv4 address a
"DS-MIPv6 IPv4 CoA".  I.e. a definition section entry saying "DS-MIPv6
CoA can be: an IPv6 CoA, an IPv4-mapped IPv6 address, etc".

>>>> The fact that DS-MIPv6 requires MN to support IPv4 Home 
>>>> Addresses, but does not permit MN to have a real IPv6 CoA when 
>>>> behind NAT is none of my faults either.
>>> No, but understanding the basics of the mechanism is, I believe, 
>>> your responsibiltiy.
>> Henrik, the WG can't impose some users what the WG thinks the user
>>  needs.  If an IPv6 user on some IPv6 MN is behind a NAT needs an 
>> IPv6 address to run his/her IPv6 application, the WG can't tell 
>> him/her "no no, use an v4-mapped CoA, it's better".
> 
> An application on a MN running MIPv6 sees the MN's IPv6 home address,
>  (HoA) and shouldn't care whether MIPv6 uses an IPv4 CoA to transport
>  the app's IPv6 traffic to the HA.

That is right, with DS-MIPv6 as drafted.

> It now seems to me (and I'm saying this because it's just what it 
> here seems like, no other reason) that you're saying 'CoA' when you 
> are referring to the address the applications see.  But that is the 
> MN's HoA, nothing else.

I see, there may have been some confusion on my part.  Let me try to
clarify.

The v6 address MN configures on its UDP tunnel interface may be a Home
Address when the MN is connected behind NAT most of the time.  In this
case, if the MN temporarily (i.e. less time) attaches to an IPv6 access
network it will configure a CoA on its true not virtual UDP interface.

If on the other hand, if the MN is mostly connected to WiFi on an IPv6
access network it will use that as a MIPv6 Home Address, and the one on
the UDP tunnel interface as a CoA.

Thirdly, if the MN is always connected to v4 access (never on v6
access), the IPv6 address on one UDP tunnel is the HoA and the other
tunnel is the CoA.

Thinking out all possible access possibilities, the IPv6 address on the
UDP tunnel interface can either be HoA or CoA, no restriction.

>>>> Ok, but can MIPv6 MN (3775, 3776) still support an IPv6 Care-of
>>>>  Address for this Mobile Node when MN behind NAT, over the UDP 
>>>> "tunnel" interface?
>>> Oh, I'm sure we could arrange for that, but there is no reason 
>>> to, I believe.
>> Why not?  Having a real IPv6 address on the MN is a godsend for 
>> pure IPv6 applications and pure IPv6 DNS.  I won't ask you why you 
>> think there's no reason because I don't want to troll.
> 
> Because the apps use the IPv6 HoA provided by MIPv6!

Completely agree, I was wrong to write "apps".

But I think RR and 3776 (not the apps) may be very tighly bound to IPv6
being a 128-bit IPv6 address (not a v4-mapped which is inherently
link-local).

>>>> How does HA know to whom to send traffic it intercepts for MN's
>>>>  HoA when the CoA is NAT's public address and there's no port 
>>>> number saved?
>>> The statement that there's no port number used is incorrect.
>> Currently the port numbers aren't in the binding cache.
> 
> I don't care where you put them in your implementation.  They have to
>  be known and remembered.

I partly agree.  NAT, and the way DS-MIPv6 stores and checks
private/public addresses and the port numbers has potential security
issues, depending how IKE is being used.  Maybe we'll look at that later.

> ???  If the MN is in an IPv4 only network, that seems a bit weird. 
> Are you proposing that we set up a 6to4 tunnel so we can get a MIPv6
>  address which we can use as a CoA?

No, not on the 6to4 tunnel, but on the UDP tunnel.  I don't see any
difference anyways.  My implementation has it on the UDP tunnel and I
can put it on the 6to4 IPv6-in-IPv4 tunnel too (except that the 6to4
Gateways I use don't send RAs on these tunnels).

> That approach has been discussed, but has much higher overhead than 
> the current proposal. See 
> http://tools.ietf.org/html/draft-larsson-v6ops-mip-scenarios-01

Ok, if you think it is useful we can discuss that draft's results
separately.  Overhead of having an IPv6 CoA on the UDP tunnel interface
is 0 (on v6-in-v4 too).  Contrary to what that draft states, there's no
need of 6to4 on the entire home network, but only on a unique Gateway,
but separated from the HA.

>>>> And finally, what do you guys have against MN having a real 
>>>> IPv6 CoA when behind NAT?  What would that break?  Wouldn't 
>>>> software reusability be good?  3775, 3776 and bootstrapping 
>>>> work work unmodified.
>>> If you want that functionality, define an extension for it.  I 
>>> don't see any reason to fake an IPv6 CoA when the active CoA is 
>>> IPv4.
>> It's not a "fake IPv6" CoA.  It's a real IPv6 address.  It's 
>> publicly routable on the entire IPv6 Internet.  It's distributed to
>>  it from the real IPv6 prefix advertised to it by the HA (that I 
>> currently call GW).
> 
> Seems to me you're talking about the HoA, then.  The whole purpose of
>  the current draft is to provide an IPv6 HoA by means of MIPv6. But 
> if you insist on calling the HA by the name of 'GW', and calling the
>  HoA by the name of 'CoA'

Right.  The IPv6 address configured on the UDP tunnel interface could be
either a HoA (if MN mostly on same NATed access) or a CoA otherwise.
That IPv6 address can play any role, HoA or CoA.

About HA and GW: I think it is useful to separate the HA doing MIP6 from
the GW doing NAT traversal and other v6-v4 translation.  For several
reasons, but we can discuss separately.

Alex


_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Tue May 02 10:40:23 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Faw2l-00058r-W8; Tue, 02 May 2006 10:40:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Faw2k-00058m-Dm
	for mip6@ietf.org; Tue, 02 May 2006 10:40:02 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Faw2b-0006bk-BU
	for mip6@ietf.org; Tue, 02 May 2006 10:40:02 -0400
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	262014F0001; Tue,  2 May 2006 16:39:39 +0200 (CEST)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.170]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 2 May 2006 16:39:39 +0200
Received: from [147.214.237.61] ([147.214.237.61]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 2 May 2006 16:39:38 +0200
Message-ID: <44576F2A.9010703@levkowetz.com>
Date: Tue, 02 May 2006 16:39:38 +0200
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Thunderbird 1.5 (Macintosh/20051201)
MIME-Version: 1.0
To: Alexandru Petrescu <alexandru.petrescu@motorola.com>
References: <1487A357FD2ED544B8AD29E528FF9DF0024F2419@NAEX06.na.qualcomm.com>
	<44513C22.9090706@motorola.com>
	<E0CD2CF1-BA63-427D-8151-BB4DB0DF3A78@sfc.wide.ad.jp>
	<445244F0.4010905@motorola.com> <44524D69.6080709@levkowetz.com>
	<44525415.3050103@motorola.com>
	<445262C7.6050603@levkowetz.com> <44526F9E.70709@motorola.com>
	<44529BC4.3040609@levkowetz.com> <4452A40F.9080409@motorola.com>
	<44533034.7070106@levkowetz.com> <44575E63.2090805@motorola.com>
In-Reply-To: <44575E63.2090805@motorola.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 02 May 2006 14:39:38.0570 (UTC)
	FILETIME=[3D5FAAA0:01C66DF6]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 156eddb66af16eef49a76ae923b15b92
Cc: "Zhang, Qiang \[NTK\]" <Qiang.Zhang@sprint.com>,
	Ryuji Wakikawa <ryuji@sfc.wide.ad.jp>, "Soliman,
	Hesham" <hsoliman@qualcomm.com>, mip6@ietf.org
Subject: [Mip6] Re: When behind NAT MN should have a real IPv6 CoA not mapped
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi Alexandru,

This is my last message to you.  See the comments inside.  This is too
much of a drain on my time, to no benefit I can see.


On 2006-05-02 15:28 Alexandru Petrescu said the following:
> Henrik Levkowetz wrote:
> 
>> When the MN acquires an IPv4 address in an IPv4-only network and uses
>>  that as a MIPv6 CoA, there is **no** IPv6 CoA involved anywhere.
> 
> Ok, if there is an RA on the UDP tunnel and MN has an EUI-64 and
> auto-configures an address, is it abnormal to call it an IPv6 CoA?

Yes.

> If HA uses the IPv6 address MN uses on its UDP tunnel interface as a
> MIPv6 CoA, I think the terminology is right.

No.

> I suggest we call the MN's IPv6 v4-mapped private IPv4 address a
> "DS-MIPv6 IPv4 CoA".  I.e. a definition section entry saying "DS-MIPv6
> CoA can be: an IPv6 CoA, an IPv4-mapped IPv6 address, etc".

The concept of a MIP CoA is very clear and simple.  Don't enforce
your own past complications in understanding on others, please.

>>>>> The fact that DS-MIPv6 requires MN to support IPv4 Home 
>>>>> Addresses, but does not permit MN to have a real IPv6 CoA when 
>>>>> behind NAT is none of my faults either.
>>>> No, but understanding the basics of the mechanism is, I believe, 
>>>> your responsibiltiy.
>>> Henrik, the WG can't impose some users what the WG thinks the user
>>>  needs.  If an IPv6 user on some IPv6 MN is behind a NAT needs an 
>>> IPv6 address to run his/her IPv6 application, the WG can't tell 
>>> him/her "no no, use an v4-mapped CoA, it's better".
>> An application on a MN running MIPv6 sees the MN's IPv6 home address,
>>  (HoA) and shouldn't care whether MIPv6 uses an IPv4 CoA to transport
>>  the app's IPv6 traffic to the HA.
> 
> That is right, with DS-MIPv6 as drafted.
> 
>> It now seems to me (and I'm saying this because it's just what it 
>> here seems like, no other reason) that you're saying 'CoA' when you 
>> are referring to the address the applications see.  But that is the 
>> MN's HoA, nothing else.
> 
> I see, there may have been some confusion on my part.  Let me try to
> clarify.
> 
> The v6 address MN configures on its UDP tunnel interface may be a Home
> Address when the MN is connected behind NAT most of the time.  In this
> case, if the MN temporarily (i.e. less time) attaches to an IPv6 access
> network it will configure a CoA on its true not virtual UDP interface.
> 
> If on the other hand, if the MN is mostly connected to WiFi on an IPv6
> access network it will use that as a MIPv6 Home Address, and the one on
> the UDP tunnel interface as a CoA.

No.  Now you're calling a potential IPv6 CoA by the name 'MIPv6 Home Address'.
That's also incorrect.

> Thirdly, if the MN is always connected to v4 access (never on v6
> access), the IPv6 address on one UDP tunnel is the HoA and the other
> tunnel is the CoA.

No, this still seems confused to me.  MIP provides the HoA to the applications,
and does this by using a locally assigned/configured CoA (or multiple CoAs).

> Thinking out all possible access possibilities, the IPv6 address on the
> UDP tunnel interface can either be HoA or CoA, no restriction.

If you're talking about the MIP tunnel, the answer is: Nope, not at all.
It is the HoA, which isn't the CoA.

>>>>> Ok, but can MIPv6 MN (3775, 3776) still support an IPv6 Care-of
>>>>>  Address for this Mobile Node when MN behind NAT, over the UDP 
>>>>> "tunnel" interface?
>>>> Oh, I'm sure we could arrange for that, but there is no reason 
>>>> to, I believe.
>>> Why not?  Having a real IPv6 address on the MN is a godsend for 
>>> pure IPv6 applications and pure IPv6 DNS.  I won't ask you why you 
>>> think there's no reason because I don't want to troll.
>> Because the apps use the IPv6 HoA provided by MIPv6!
> 
> Completely agree, I was wrong to write "apps".
> 
> But I think RR and 3776 (not the apps) may be very tighly bound to IPv6
> being a 128-bit IPv6 address (not a v4-mapped which is inherently
> link-local).

The v4traversal draft does not aim at providing route optimization
when using an IPv4 CoA, so although what you say seems correct, it's
not relevant.

>>>>> How does HA know to whom to send traffic it intercepts for MN's
>>>>>  HoA when the CoA is NAT's public address and there's no port 
>>>>> number saved?
>>>> The statement that there's no port number used is incorrect.
>>> Currently the port numbers aren't in the binding cache.
>> I don't care where you put them in your implementation.  They have to
>>  be known and remembered.
> 
> I partly agree.  NAT, and the way DS-MIPv6 stores and checks
> private/public addresses and the port numbers has potential security
> issues, depending how IKE is being used.  Maybe we'll look at that later.

I don't think you have more security issues that those clearly described
in the security considerations of 3519.

>> ???  If the MN is in an IPv4 only network, that seems a bit weird. 
>> Are you proposing that we set up a 6to4 tunnel so we can get a MIPv6
>>  address which we can use as a CoA?
> 
> No, not on the 6to4 tunnel, but on the UDP tunnel.  I don't see any
> difference anyways.  My implementation has it on the UDP tunnel and I
> can put it on the 6to4 IPv6-in-IPv4 tunnel too (except that the 6to4
> Gateways I use don't send RAs on these tunnels).
> 
>> That approach has been discussed, but has much higher overhead than 
>> the current proposal. See 
>> http://tools.ietf.org/html/draft-larsson-v6ops-mip-scenarios-01
> 
> Ok, if you think it is useful we can discuss that draft's results
> separately.

No, I'm not about to dive into that.  That's another rathole as far
as the current draft is concerned.

>  Overhead of having an IPv6 CoA on the UDP tunnel interface
> is 0 (on v6-in-v4 too).  Contrary to what that draft states, there's no
> need of 6to4 on the entire home network, but only on a unique Gateway,
> but separated from the HA.
> 
>>>>> And finally, what do you guys have against MN having a real 
>>>>> IPv6 CoA when behind NAT?  What would that break?  Wouldn't 
>>>>> software reusability be good?  3775, 3776 and bootstrapping 
>>>>> work work unmodified.
>>>> If you want that functionality, define an extension for it.  I 
>>>> don't see any reason to fake an IPv6 CoA when the active CoA is 
>>>> IPv4.
>>> It's not a "fake IPv6" CoA.  It's a real IPv6 address.  It's 
>>> publicly routable on the entire IPv6 Internet.  It's distributed to
>>>  it from the real IPv6 prefix advertised to it by the HA (that I 
>>> currently call GW).
>> Seems to me you're talking about the HoA, then.  The whole purpose of
>>  the current draft is to provide an IPv6 HoA by means of MIPv6. But 
>> if you insist on calling the HA by the name of 'GW', and calling the
>>  HoA by the name of 'CoA'
> 
> Right.  The IPv6 address configured on the UDP tunnel interface could be
> either a HoA (if MN mostly on same NATed access) or a CoA otherwise.

Nope, the IPv6 address provided by MIP on the MIP 'tunnel interface'
is never called the CoA.

> That IPv6 address can play any role, HoA or CoA.

No.  It is the HoA.

> About HA and GW: I think it is useful to separate the HA doing MIP6 from
> the GW doing NAT traversal and other v6-v4 translation.  For several
> reasons, but we can discuss separately.

No.  See the beginning of the message.


	Henrik

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Tue May 02 11:57:49 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FaxFy-0003Gw-Gx; Tue, 02 May 2006 11:57:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FaxFx-0003CO-G0
	for mip6@ietf.org; Tue, 02 May 2006 11:57:45 -0400
Received: from nproxy.gmail.com ([64.233.182.186])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FaxFx-0001oy-6P
	for mip6@ietf.org; Tue, 02 May 2006 11:57:45 -0400
Received: by nproxy.gmail.com with SMTP id l36so2025283nfa
	for <mip6@ietf.org>; Tue, 02 May 2006 08:57:44 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=VQhdnxABWwSRMuv+JGBKbvm//Ea7XBk7139bSoyey8jYncKK/HdB5PR4bivw5aztASrd/7ZK2WNtIPStuml2EnXxFp/H+5Wi9ViZZlGQ/F+9gbH6N06ZIMNFq0bbWN/1ObjbP81qJJrwdGOFwN35FJo1dtz4vHOFW7TRtQYJIf8=
Received: by 10.48.241.16 with SMTP id o16mr640282nfh;
	Tue, 02 May 2006 08:57:44 -0700 (PDT)
Received: by 10.49.40.20 with HTTP; Tue, 2 May 2006 08:57:44 -0700 (PDT)
Message-ID: <eaa74a7e0605020857s27f685b6l8948ab3a63a5b325@mail.gmail.com>
Date: Tue, 2 May 2006 17:57:44 +0200
From: "Gerardo Giaretta" <gerardo.giaretta@gmail.com>
To: "Sam Hartman" <hartmans-ietf@mit.edu>
Subject: Re: [Mip6] FW: DISCUSS and COMMENT: draft-ietf-mip6-bootstrap-ps
In-Reply-To: <tslu088d43x.fsf@cz.mit.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <eaa74a7e0604301330y4bc37bcamd953a713cf50c95a@mail.gmail.com>
	<44568464.1090807@azairenet.com> <tslpsixe68p.fsf@cz.mit.edu>
	<eaa74a7e0605020117n31ff475bie7dc2541dd8e197@mail.gmail.com>
	<tslu088d43x.fsf@cz.mit.edu>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
Cc: mip6@ietf.org, Basavaraj Patil <Basavaraj.Patil@nokia.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

On 5/2/06, Sam Hartman <hartmans-ietf@mit.edu> wrote:
> >>>>> "Gerardo" =3D=3D Gerardo Giaretta <gerardo.giaretta@gmail.com> writ=
es:
>
>
>     Gerardo> Hi Sam,
>
>     Gerardo> thanks for the comments and sorry for very late answers.
>
>     Gerardo> Concerning the EAP issue, I think that both solutions
>     Gerardo> that are under definition in the WG does not follow the
>     Gerardo> directions you mentioned.  After your and others'
>     Gerardo> comments (also during ICOS BOF and HOAKEY BOF) the WG has
>     Gerardo> been producing solutions where network access
>     Gerardo> authentication and mobility service authentication are
>     Gerardo> considered fully separated. It seems to me that this
>     Gerardo> problem statement does not suggest this kind of
>     Gerardo> solutions. Please let me know if you think some
>     Gerardo> clarifying text needs to be added to this problem
>     Gerardo> statement.
>
> Take a look at the last phrase in the following paragraph of 7.2:
>
>     In this scenario, the ASA and MSA are the same entity.  The MN has
>        security credentials for access to the network and these credentia=
ls
>           can be used to bootstrap MIPv6.  This bootstrapping can be done
>              during the same phase as access authentication/authorization=
 or at a
>                 later time (probably based on some state created during a=
ccess
>                    authentication/authorization).
>
> It sounds like the two are bound.
>

I would delete the last sentence. I would like to keep the following:

>     In this scenario, the ASA and MSA are the same entity.  The MN has
>        security credentials for access to the network and these credentia=
ls
>           can be used to bootstrap MIPv6.

since it is a clear deployment scenario. Sounds good?

>     Gerardo> Concerning rfc4285, the WG is currently not working on a
>     Gerardo> solutions for bootstrapping rfc4285 SAs. I'm OK with
>     Gerardo> removing all references to rfc4285. Is this your
>     Gerardo> suggestion?
>
> I'd certainly be happiest with that.
>
> I do think that  the mention of RFC 4285  in the following bullet should =
be removed:
>
>        *  IPsec SA between MN and HA, IKE pre-shared secret between MN
>            and HA, or shared secret/security association for
>                 authentication protocol [RFC4285]
>
> I don't have a problem with the reference to 4285 in section 1.
>

I'm OK with that. What do others think?

--Gerardo

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Tue May 02 12:04:23 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FaxMJ-0002Il-IJ; Tue, 02 May 2006 12:04:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FaxMI-0002Gb-Bn
	for mip6@ietf.org; Tue, 02 May 2006 12:04:18 -0400
Received: from nproxy.gmail.com ([64.233.182.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FaxMI-0001yn-2b
	for mip6@ietf.org; Tue, 02 May 2006 12:04:18 -0400
Received: by nproxy.gmail.com with SMTP id l36so2026826nfa
	for <mip6@ietf.org>; Tue, 02 May 2006 09:04:17 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=VZNs0Y76SvUFp5bK94lUGQ3U4XJUj75PTPWA1GEp0zNaIWt5DZAvTKd2hWMF8sROU6Zz6eJ59L3c8PFNfoBZrqM5W/sPrMcwtG971ycxNmEbY/eqqudY/wIgkhfRziajSelLWtjPkEmLozSf1yzMZDm91sS2MgkjlHOE0YlfFys=
Received: by 10.48.164.3 with SMTP id m3mr658311nfe;
	Tue, 02 May 2006 09:04:17 -0700 (PDT)
Received: by 10.49.40.20 with HTTP; Tue, 2 May 2006 09:04:17 -0700 (PDT)
Message-ID: <eaa74a7e0605020904j2019296am329ea1988d5fb0a5@mail.gmail.com>
Date: Tue, 2 May 2006 18:04:17 +0200
From: "Gerardo Giaretta" <gerardo.giaretta@gmail.com>
To: "Alexandru Petrescu" <alexandru.petrescu@motorola.com>
Subject: Re: [Mip6] How to store DNS records about HAs,
	(draft-ietf-mip6-bootstrapping-split-02.txt)?
In-Reply-To: <44574A1D.2060603@motorola.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <8A16DAD84432534FBFC19FD92B50512F05B97A15@ames.starentnetworks.com>
	<eaa74a7e0605010238s36eef57fm23b8fba6b3d9eaac@mail.gmail.com>
	<44574A1D.2060603@motorola.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
Cc: mip6@ietf.org,
	COMBES Jean-Michel RD-MAPS-ISS <jeanmichel.combes@francetelecom.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi Alex,

I will reply for the split document, letting Kuntal the details of the
integrated.
> > IMO, this limitation is well covered in the draft, also discussing
> > load balancing. But, please any suggestion on how to improve the
> > document is welcome.
>
> Yes.
>
> Improving a document is a useful.  It's also good to keep the document
> short and tractable.
>
> For split, (1) specify that HA updates the DNS with its own address,
> maybe via DHCP, with a new type of SRV record or (2) eliminate the claim
> of SRV helping with load balancing.  The latter seems to me to be least
> work.
>

We have already stated that a fine-grained load balancing is not
possible using DNS. We have this paragraph in section 5.1:

        This document does not provide a specific mechanism to load
balance different
        Mobile Nodes among Home Agents. It is possible for an MSP to
achieve coarse-
        grained load balancing by dynamically updating the SRV RR
priorities to reflect
        the current load on the MSP's collection of Home Agents.
Mobile Nodes then use
        the priority mechanism to preferentially select the least
loaded HA. The
        effectiveness of this technique depends on how much of a load
it will place on
        the DNS servers, particularly if dynamic DNS is used for
frequent updates.

Isn'it enough?

> For integrated, clarify what is the pre-configured information before
> bootstrapping (NAI apparently).  Clarify that a domain name encompasses
> several subnets each comprising its own set of HAs.  Clarify how using
> only one NAI key for searching addresses this search (a search should
> retrieve only one subnet's set of HAs, not entire domain's).  This seems
> much work to me.
>
> Does this make sense?
>
> Alex
> PS: I don't think there's a clearcut  difference between "HA discovery"
> and "HA assignment".  DHAAD is mainly discovery but its effect is that
> MN gets its HA address, thus it is assigned the HA address.
>

I think there is a big difference from an operator perspective; the HA
assignment implies that an operator may assign a specific HA to a
specific MN.

This is not possible with HA discovery (e.g. based on DNS).
This is possible using the solution provided in the integrated draft.

--Gerardo

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Tue May 02 12:35:04 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Faxpw-0004LT-5L; Tue, 02 May 2006 12:34:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Faxpu-0004LI-MI
	for mip6@ietf.org; Tue, 02 May 2006 12:34:54 -0400
Received: from p-mail1.rd.francetelecom.com ([195.101.245.15])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Faxpu-0003Fh-BW
	for mip6@ietf.org; Tue, 02 May 2006 12:34:54 -0400
Received: from ftrdmel3.rd.francetelecom.fr ([10.193.117.155]) by
	ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 2 May 2006 18:34:53 +0200
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Subject: RE: [Mip6] How to store DNS records about HAs,
	(draft-ietf-mip6-bootstrapping-split-02.txt)?
Date: Tue, 2 May 2006 18:34:40 +0200
Message-ID: <D2AA6DF1AEE4404F8D983B68BAC97CD202E2B9BD@ftrdmel3.rd.francetelecom.fr>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] How to store DNS records about HAs,
	(draft-ietf-mip6-bootstrapping-split-02.txt)?
Thread-Index: AcZt4CuA9GUaMmfiRmyV+pq2oGoHlwAJW6eQ
From: "COMBES Jean-Michel RD-MAPS-ISS" <jeanmichel.combes@francetelecom.com>
To: "Alexandru Petrescu" <alexandru.petrescu@motorola.com>,
	"Gerardo Giaretta" <gerardo.giaretta@gmail.com>
X-OriginalArrivalTime: 02 May 2006 16:34:53.0347 (UTC)
	FILETIME=[56E6E730:01C66E06]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

=20

> -----Original Message-----
> From: Alexandru Petrescu [mailto:alexandru.petrescu@motorola.com]=20
> Sent: Tuesday, May 02, 2006 2:02 PM
> To: Gerardo Giaretta
> Cc: Chowdhury, Kuntal; mip6@ietf.org; COMBES Jean-Michel RD-MAPS-ISS
> Subject: Re: [Mip6] How to store DNS records about HAs,=20
> (draft-ietf-mip6-bootstrapping-split-02.txt)?
>=20
>

[snip]
=20
> Alex
> PS: I don't think there's a clearcut  difference between "HA=20
> discovery"
> and "HA assignment".  DHAAD is mainly discovery but its=20
> effect is that MN gets its HA address, thus it is assigned=20
> the HA address.
>=20

Alex,

When you book a room in a hotel, who does decide finally on the number
of your room? This is the hotel, regarding what type of room you want
and the ones that are available. This is assignment :)

Best regards.

JMC.

France Telecom - R&D Division - MAPS/NSS  =20
Jean-Michel COMBES, Internet/Intranet Security
E-Mail: jeanmichel.combes@francetelecom.com
Phone: +33 (0)1 45 29 45 94
Fax: +33 (0)1 45 29 65 19
Mobile: +33 (0)6 07 29 30 16=20

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Tue May 02 12:43:41 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FaxyL-0004Ug-Nq; Tue, 02 May 2006 12:43:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FaxyK-0004Ub-GA
	for mip6@ietf.org; Tue, 02 May 2006 12:43:36 -0400
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FaxyD-0003VX-BX
	for mip6@ietf.org; Tue, 02 May 2006 12:43:36 -0400
Received: from il06exr02.mot.com (il06exr02.mot.com [129.188.137.132])
	by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id k42Gxs7N003386;
	Tue, 2 May 2006 09:59:54 -0700 (MST)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by il06exr02.mot.com (8.13.1/8.13.0) with ESMTP id k42Gvmm0023276;
	Tue, 2 May 2006 11:57:48 -0500 (CDT)
Message-ID: <44578C0D.1030804@motorola.com>
Date: Tue, 02 May 2006 18:42:53 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: Gerardo Giaretta <gerardo.giaretta@gmail.com>
Subject: Re: [Mip6] How to store DNS records about HAs,
	(draft-ietf-mip6-bootstrapping-split-02.txt)?
References: <8A16DAD84432534FBFC19FD92B50512F05B97A15@ames.starentnetworks.com>	
	<eaa74a7e0605010238s36eef57fm23b8fba6b3d9eaac@mail.gmail.com>	
	<44574A1D.2060603@motorola.com>
	<eaa74a7e0605020904j2019296am329ea1988d5fb0a5@mail.gmail.com>
In-Reply-To: <eaa74a7e0605020904j2019296am329ea1988d5fb0a5@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAQAAAAQ=
X-White-List-Member: TRUE
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976
Cc: mip6@ietf.org,
	COMBES Jean-Michel RD-MAPS-ISS <jeanmichel.combes@francetelecom.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Gerardo Giaretta wrote:
> Hi Alex,
> 
> I will reply for the split document, letting Kuntal the details of 
> the integrated.
>>> IMO, this limitation is well covered in the draft, also 
>>> discussing load balancing. But, please any suggestion on how to 
>>> improve the document is welcome.
>> 
>> Yes.
>> 
>> Improving a document is a useful.  It's also good to keep the 
>> document short and tractable.
>> 
>> For split, (1) specify that HA updates the DNS with its own 
>> address, maybe via DHCP, with a new type of SRV record or (2) 
>> eliminate the claim of SRV helping with load balancing.  The latter
>>  seems to me to be least work.
>> 
> 
> We have already stated that a fine-grained load balancing is not 
> possible using DNS. We have this paragraph in section 5.1:
> 
> This document does not provide a specific mechanism to load balance 
> different Mobile Nodes among Home Agents. It is possible for an MSP 
> to achieve coarse- grained load balancing by dynamically updating the
>  SRV RR priorities to reflect the current load on the MSP's 
> collection of Home Agents. Mobile Nodes then use the priority 
> mechanism to preferentially select the least loaded HA. The 
> effectiveness of this technique depends on how much of a load it will
>  place on the DNS servers, particularly if dynamic DNS is used for 
> frequent updates.
> 
> Isn'it enough?

Looks ok, if I assume that "fine-grained" load balancing is the one
achieved with DHAAD and "coarse-grained" load balancing is the one
assigning HA from different subnets.

Maybe one should add that when assigning a HA from subnet different than
the previous (with coarse-grained load balancing) the MN HoA will
change and previous communications are not guaranteed to be continued.

>> For integrated, clarify what is the pre-configured information 
>> before bootstrapping (NAI apparently).  Clarify that a domain name
>>  encompasses several subnets each comprising its own set of HAs. 
>> Clarify how using only one NAI key for searching addresses this 
>> search (a search should retrieve only one subnet's set of HAs, not
>>  entire domain's).  This seems much work to me.
>> 
>> Does this make sense?
>> 
>> Alex PS: I don't think there's a clearcut  difference between "HA 
>> discovery" and "HA assignment".  DHAAD is mainly discovery but its
>>  effect is that MN gets its HA address, thus it is assigned the HA
>>  address.
>> 
> 
> I think there is a big difference from an operator perspective; the 
> HA assignment implies that an operator may assign a specific HA to a 
> specific MN.

I agree that it may be advantageous for an operator to use a central
server assigning HA to MN centrally.

> This is not possible with HA discovery (e.g. based on DNS). This is 
> possible using the solution provided in the integrated draft.

Ok.

I think I look too much at MIP6 as a set of HAs running on every subnet,
while you seem to look at it as a central server independent of the
existing subnets, which assigns HAs to MN.

For example, with integrated scenario bootstrapping one could
accommodate a central server of a cell phone operator dynamically
assigning HA to its phone terminals.  But couldn't accommodate one's
laptop in an enterprise network, which is usually deep in that
Enterprise's subnet topology.

Alex

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Tue May 02 12:48:48 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fay3I-0000lp-6v; Tue, 02 May 2006 12:48:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fay3G-0000lk-U8
	for mip6@ietf.org; Tue, 02 May 2006 12:48:42 -0400
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fay3A-0003iD-RP
	for mip6@ietf.org; Tue, 02 May 2006 12:48:42 -0400
Received: from il06exr01.mot.com (il06exr01.mot.com [129.188.137.131])
	by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id k42H5NnQ004682;
	Tue, 2 May 2006 10:05:23 -0700 (MST)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by il06exr01.mot.com (8.13.5/8.13.0) with ESMTP id k42H5bvX017453;
	Tue, 2 May 2006 12:05:38 -0500 (CDT)
Message-ID: <44578D57.7030402@motorola.com>
Date: Tue, 02 May 2006 18:48:23 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: COMBES Jean-Michel RD-MAPS-ISS <jeanmichel.combes@francetelecom.com>
Subject: Re: [Mip6] How to store DNS records about HAs,
	(draft-ietf-mip6-bootstrapping-split-02.txt)?
References: <D2AA6DF1AEE4404F8D983B68BAC97CD202E2B9BD@ftrdmel3.rd.francetelecom.fr>
In-Reply-To: <D2AA6DF1AEE4404F8D983B68BAC97CD202E2B9BD@ftrdmel3.rd.francetelecom.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAQAAAAQ=
X-White-List-Member: TRUE
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

COMBES Jean-Michel RD-MAPS-ISS wrote:
>> Alex PS: I don't think there's a clearcut  difference between "HA 
>> discovery" and "HA assignment".  DHAAD is mainly discovery but its
>>  effect is that MN gets its HA address, thus it is assigned the HA
>> address.
>> 
> 
> Alex,
> 
> When you book a room in a hotel, who does decide finally on the
> number of your room? This is the hotel, regarding what type of room
> you want and the ones that are available. This is assignment :)

YEs, and this assignment does not guarantee forwarding of all my mail
arriving at my house in my home country to the room assigned by that
hotel.  (For that, I'll have to tell La Poste (USMail) my real house
address and the room number at that hotel).

I suppose I'm correct to understand that HA assignment will not offer
session continuity from the previously assigned HA/HoA.

Alex

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Tue May 02 12:51:42 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fay6A-0002l4-3c; Tue, 02 May 2006 12:51:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fay69-0002kn-2W
	for mip6@ietf.org; Tue, 02 May 2006 12:51:41 -0400
Received: from nproxy.gmail.com ([64.233.182.190])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fay67-0003uF-Pr
	for mip6@ietf.org; Tue, 02 May 2006 12:51:41 -0400
Received: by nproxy.gmail.com with SMTP id l36so2036348nfa
	for <mip6@ietf.org>; Tue, 02 May 2006 09:51:39 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=CZt+RBrH0FHVfph+jTnx3E5SYanj0SmSk5Z9mZdm33qqzfRfODMganuNAFa4MgKd0HvuPj6HsTc71BAYea5VyZ+dxd2sSWN4kT71YaTKlAK3tBSbci1Ym6uX+ysQi6/aytKwkEQkK9pJFIJsGOVvoAT7lXmo2ps0YYow6THBmbA=
Received: by 10.49.95.8 with SMTP id x8mr688776nfl;
	Tue, 02 May 2006 09:51:39 -0700 (PDT)
Received: by 10.49.40.20 with HTTP; Tue, 2 May 2006 09:51:38 -0700 (PDT)
Message-ID: <eaa74a7e0605020951g79bddb93q27f34809a2589a52@mail.gmail.com>
Date: Tue, 2 May 2006 18:51:38 +0200
From: "Gerardo Giaretta" <gerardo.giaretta@gmail.com>
To: "Alexandru Petrescu" <alexandru.petrescu@motorola.com>
Subject: Re: [Mip6] How to store DNS records about HAs,
	(draft-ietf-mip6-bootstrapping-split-02.txt)?
In-Reply-To: <44578D57.7030402@motorola.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <D2AA6DF1AEE4404F8D983B68BAC97CD202E2B9BD@ftrdmel3.rd.francetelecom.fr>
	<44578D57.7030402@motorola.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Cc: mip6@ietf.org,
	COMBES Jean-Michel RD-MAPS-ISS <jeanmichel.combes@francetelecom.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

On 5/2/06, Alexandru Petrescu <alexandru.petrescu@motorola.com> wrote:
> COMBES Jean-Michel RD-MAPS-ISS wrote:
> >> Alex PS: I don't think there's a clearcut  difference between "HA
> >> discovery" and "HA assignment".  DHAAD is mainly discovery but its
> >>  effect is that MN gets its HA address, thus it is assigned the HA
> >> address.
> >>
> >
> > Alex,
> >
> > When you book a room in a hotel, who does decide finally on the
> > number of your room? This is the hotel, regarding what type of room
> > you want and the ones that are available. This is assignment :)
>
> YEs, and this assignment does not guarantee forwarding of all my mail
> arriving at my house in my home country to the room assigned by that
> hotel.  (For that, I'll have to tell La Poste (USMail) my real house
> address and the room number at that hotel).
>
> I suppose I'm correct to understand that HA assignment will not offer
> session continuity from the previously assigned HA/HoA.
>

This is not a goal for the bootstrapping work.

--Gerardo

> Alex
>

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Tue May 02 13:00:18 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FayDq-0008JU-2T; Tue, 02 May 2006 12:59:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FayDo-0008JP-Km
	for mip6@ietf.org; Tue, 02 May 2006 12:59:36 -0400
Received: from p-mail2.rd.francetelecom.com ([195.101.245.16])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FayDo-0004Bn-9N
	for mip6@ietf.org; Tue, 02 May 2006 12:59:36 -0400
Received: from ftrdmel3.rd.francetelecom.fr ([10.193.117.155]) by
	ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 2 May 2006 18:59:33 +0200
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Subject: RE: [Mip6] How to store DNS records about HAs,
	(draft-ietf-mip6-bootstrapping-split-02.txt)?
Date: Tue, 2 May 2006 18:59:30 +0200
Message-ID: <D2AA6DF1AEE4404F8D983B68BAC97CD202E2B9BE@ftrdmel3.rd.francetelecom.fr>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] How to store DNS records about HAs,
	(draft-ietf-mip6-bootstrapping-split-02.txt)?
Thread-Index: AcZuCD7gHLZB+kcQS+mAGPn7ekJIbQAAHq8g
From: "COMBES Jean-Michel RD-MAPS-ISS" <jeanmichel.combes@francetelecom.com>
To: "Alexandru Petrescu" <alexandru.petrescu@motorola.com>
X-OriginalArrivalTime: 02 May 2006 16:59:33.0408 (UTC)
	FILETIME=[C9164A00:01C66E09]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org



=20

> -----Original Message-----
> From: Alexandru Petrescu [mailto:alexandru.petrescu@motorola.com]=20
> Sent: Tuesday, May 02, 2006 6:48 PM
> To: COMBES Jean-Michel RD-MAPS-ISS
> Cc: Gerardo Giaretta; Chowdhury, Kuntal; mip6@ietf.org
> Subject: Re: [Mip6] How to store DNS records about HAs,=20
> (draft-ietf-mip6-bootstrapping-split-02.txt)?
>=20
> COMBES Jean-Michel RD-MAPS-ISS wrote:
> >> Alex PS: I don't think there's a clearcut  difference between "HA=20
> >> discovery" and "HA assignment".  DHAAD is mainly discovery=20
> but its =20
> >> effect is that MN gets its HA address, thus it is assigned the HA=20
> >> address.
> >>=20
> >=20
> > Alex,
> >=20
> > When you book a room in a hotel, who does decide finally on=20
> the number=20
> > of your room? This is the hotel, regarding what type of=20
> room you want=20
> > and the ones that are available. This is assignment :)
>=20
> YEs, and this assignment does not guarantee forwarding of all=20
> my mail arriving at my house in my home country to the room=20
> assigned by that hotel.  (For that, I'll have to tell La=20
> Poste (USMail) my real house address and the room number at=20
> that hotel).
>=20
> I suppose I'm correct to understand that HA assignment will=20
> not offer session continuity from the previously assigned HA/HoA.

In my point of view, this is another issue (which may have solutions
like HAHA or CxT maybe) which out of scope the bootstrapping issue (ie.
we can assume the MN has no active session when it bootstrapps because
in fact it is not yet a MN and so has not previous HA :)

>=20
> Alex
>=20

Best regards.

JMC.

France Telecom - R&D Division - MAPS/NSS  =20
Jean-Michel COMBES, Internet/Intranet Security
E-Mail: jeanmichel.combes@francetelecom.com
Phone: +33 (0)1 45 29 45 94
Fax: +33 (0)1 45 29 65 19
Mobile: +33 (0)6 07 29 30 16=20

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Tue May 02 13:00:40 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FayEq-0008Q3-Gs; Tue, 02 May 2006 13:00:40 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FayEp-0008Py-NG
	for mip6@ietf.org; Tue, 02 May 2006 13:00:39 -0400
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FayEb-0004Dw-10
	for mip6@ietf.org; Tue, 02 May 2006 13:00:39 -0400
Received: from il06exr02.mot.com (il06exr02.mot.com [129.188.137.132])
	by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id k42HH7ah007427;
	Tue, 2 May 2006 10:17:12 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by il06exr02.mot.com (8.13.1/8.13.0) with ESMTP id k42HF2wh002387;
	Tue, 2 May 2006 12:15:02 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id 8F4EC865980; Tue,  2 May 2006 19:00:02 +0200 (CEST)
Message-ID: <44579012.2020406@motorola.com>
Date: Tue, 02 May 2006 19:00:02 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: Gerardo Giaretta <gerardo.giaretta@gmail.com>
Subject: Re: [Mip6] How to store DNS records about HAs,
	(draft-ietf-mip6-bootstrapping-split-02.txt)?
References: <D2AA6DF1AEE4404F8D983B68BAC97CD202E2B9BD@ftrdmel3.rd.francetelecom.fr>	
	<44578D57.7030402@motorola.com>
	<eaa74a7e0605020951g79bddb93q27f34809a2589a52@mail.gmail.com>
In-Reply-To: <eaa74a7e0605020951g79bddb93q27f34809a2589a52@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAQAAAAQ=
X-White-List-Member: TRUE
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Cc: mip6@ietf.org,
	COMBES Jean-Michel RD-MAPS-ISS <jeanmichel.combes@francetelecom.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Gerardo Giaretta wrote:
> On 5/2/06, Alexandru Petrescu <alexandru.petrescu@motorola.com> 
> wrote:
>> COMBES Jean-Michel RD-MAPS-ISS wrote:
>>>> Alex PS: I don't think there's a clearcut  difference between 
>>>> "HA discovery" and "HA assignment".  DHAAD is mainly discovery 
>>>> but its effect is that MN gets its HA address, thus it is 
>>>> assigned the HA address.
>>>> 
>>> 
>>> Alex,
>>> 
>>> When you book a room in a hotel, who does decide finally on the 
>>> number of your room? This is the hotel, regarding what type of 
>>> room you want and the ones that are available. This is assignment
>>>  :)
>> 
>> YEs, and this assignment does not guarantee forwarding of all my 
>> mail arriving at my house in my home country to the room assigned 
>> by that hotel.  (For that, I'll have to tell La Poste (USMail) my 
>> real house address and the room number at that hotel).
>> 
>> I suppose I'm correct to understand that HA assignment will not 
>> offer session continuity from the previously assigned HA/HoA.
>> 
> 
> This is not a goal for the bootstrapping work.

I think bootstrapping that forces MN to change its HoA is not adequate
to the MIP6 goal of session continuity and reachability at a permanent
home address, over the world-wide Internet.

And if we assume that MN does not need session continuity then it is
sufficient for MN to just use DHCPv6 in the visited network, get a new
address each time.

I may be wrong though.

Alex

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Tue May 02 13:20:10 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FayXd-0008NW-Pl; Tue, 02 May 2006 13:20:05 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FayXc-0008NQ-CU
	for mip6@ietf.org; Tue, 02 May 2006 13:20:04 -0400
Received: from mail1.azairenet.com ([66.92.223.4] helo=bart.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FayXb-00053w-35
	for mip6@ietf.org; Tue, 02 May 2006 13:20:04 -0400
Received: from [10.1.201.19] ([10.1.201.19]) by bart.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Tue, 2 May 2006 10:20:01 -0700
Message-ID: <445794C1.3080909@azairenet.com>
Date: Tue, 02 May 2006 10:20:01 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.2 (Windows/20060308)
MIME-Version: 1.0
To: Alexandru Petrescu <alexandru.petrescu@motorola.com>
Subject: Re: [Mip6] How to store DNS records about HAs,
	(draft-ietf-mip6-bootstrapping-split-02.txt)?
References: <D2AA6DF1AEE4404F8D983B68BAC97CD202E2B9BD@ftrdmel3.rd.francetelecom.fr>
	<44578D57.7030402@motorola.com>
In-Reply-To: <44578D57.7030402@motorola.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 02 May 2006 17:20:01.0528 (UTC)
	FILETIME=[A51A8780:01C66E0C]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Cc: mip6@ietf.org,
	COMBES Jean-Michel RD-MAPS-ISS <jeanmichel.combes@francetelecom.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Alexandru Petrescu wrote:
> COMBES Jean-Michel RD-MAPS-ISS wrote:
>>> Alex PS: I don't think there's a clearcut  difference between "HA 
>>> discovery" and "HA assignment".  DHAAD is mainly discovery but its
>>>  effect is that MN gets its HA address, thus it is assigned the HA
>>> address.
>>>
>>
>> Alex,
>>
>> When you book a room in a hotel, who does decide finally on the
>> number of your room? This is the hotel, regarding what type of room
>> you want and the ones that are available. This is assignment :)
> 
> YEs, and this assignment does not guarantee forwarding of all my mail
> arriving at my house in my home country to the room assigned by that
> hotel.  (For that, I'll have to tell La Poste (USMail) my real house
> address and the room number at that hotel).
> 
> I suppose I'm correct to understand that HA assignment will not offer
> session continuity from the previously assigned HA/HoA.

yes. MIP6 bootstrapping enables scenarios where the
IPv6 HoA is no longer the identity of the mobile
node. there is a separate identity and every time
the mobile node bootstraps it could get a new HoA
and HA.

Vijay

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Tue May 02 13:22:26 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FayZu-0000Mr-Sj; Tue, 02 May 2006 13:22:26 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FayZt-0000Mm-Db
	for mip6@ietf.org; Tue, 02 May 2006 13:22:25 -0400
Received: from mail1.azairenet.com ([66.92.223.4] helo=bart.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FayZr-0005GD-VE
	for mip6@ietf.org; Tue, 02 May 2006 13:22:25 -0400
Received: from [10.1.201.19] ([10.1.201.19]) by bart.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Tue, 2 May 2006 10:22:22 -0700
Message-ID: <4457954E.4080709@azairenet.com>
Date: Tue, 02 May 2006 10:22:22 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.2 (Windows/20060308)
MIME-Version: 1.0
To: Alexandru Petrescu <alexandru.petrescu@motorola.com>
Subject: Re: [Mip6] How to store DNS records about HAs,
	(draft-ietf-mip6-bootstrapping-split-02.txt)?
References: <8A16DAD84432534FBFC19FD92B50512F05B97A15@ames.starentnetworks.com>	<eaa74a7e0605010238s36eef57fm23b8fba6b3d9eaac@mail.gmail.com>
	<44574A1D.2060603@motorola.com>
In-Reply-To: <44574A1D.2060603@motorola.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 02 May 2006 17:22:22.0247 (UTC)
	FILETIME=[F8FA8B70:01C66E0C]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Cc: mip6@ietf.org,
	COMBES Jean-Michel RD-MAPS-ISS <jeanmichel.combes@francetelecom.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Alexandru Petrescu wrote:
> For split, (1) specify that HA updates the DNS with its own address,
> maybe via DHCP, with a new type of SRV record or 

I dont think this should be specified in the
split bootstrapping document. this is out of
scope for this document.

regarding your proposal, the HA does not use
DHCP to get it owns address. so it can't use
DHCP to update its DNS entries.

Vijay

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Tue May 02 13:22:36 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Faya4-0000Pz-Fe; Tue, 02 May 2006 13:22:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Faya3-0000Pp-S9
	for mip6@ietf.org; Tue, 02 May 2006 13:22:35 -0400
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FayZy-0005GG-TW
	for mip6@ietf.org; Tue, 02 May 2006 13:22:35 -0400
Received: from az33exr02.mot.com ([10.64.251.232])
	by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id k42HcdO8012527;
	Tue, 2 May 2006 10:38:39 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by az33exr02.mot.com (8.13.1/8.13.0) with ESMTP id k42HZIrC016049;
	Tue, 2 May 2006 12:35:18 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id 48068865980; Tue,  2 May 2006 19:21:39 +0200 (CEST)
Message-ID: <44579522.5010806@motorola.com>
Date: Tue, 02 May 2006 19:21:38 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: COMBES Jean-Michel RD-MAPS-ISS <jeanmichel.combes@francetelecom.com>
Subject: Re: [Mip6] How to store DNS records about HAs,
	(draft-ietf-mip6-bootstrapping-split-02.txt)?
References: <D2AA6DF1AEE4404F8D983B68BAC97CD202E2B9BE@ftrdmel3.rd.francetelecom.fr>
In-Reply-To: <D2AA6DF1AEE4404F8D983B68BAC97CD202E2B9BE@ftrdmel3.rd.francetelecom.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAQAAAAQ=
X-White-List-Member: TRUE
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

COMBES Jean-Michel RD-MAPS-ISS wrote:
> 
> 
> 
>> -----Original Message----- From: Alexandru Petrescu
>> [mailto:alexandru.petrescu@motorola.com] Sent: Tuesday, May 02,
>> 2006 6:48 PM To: COMBES Jean-Michel RD-MAPS-ISS Cc: Gerardo
>> Giaretta; Chowdhury, Kuntal; mip6@ietf.org Subject: Re: [Mip6] How
>> to store DNS records about HAs, 
>> (draft-ietf-mip6-bootstrapping-split-02.txt)?
>> 
>> COMBES Jean-Michel RD-MAPS-ISS wrote:
>>>> Alex PS: I don't think there's a clearcut  difference between
>>>> "HA discovery" and "HA assignment".  DHAAD is mainly discovery
>>>> 
>> but its
>>>> effect is that MN gets its HA address, thus it is assigned the
>>>> HA address.
>>>> 
>>> Alex,
>>> 
>>> When you book a room in a hotel, who does decide finally on
>> the number
>>> of your room? This is the hotel, regarding what type of
>> room you want
>>> and the ones that are available. This is assignment :)
>> YEs, and this assignment does not guarantee forwarding of all my
>> mail arriving at my house in my home country to the room assigned
>> by that hotel.  (For that, I'll have to tell La Poste (USMail) my
>> real house address and the room number at that hotel).
>> 
>> I suppose I'm correct to understand that HA assignment will not
>> offer session continuity from the previously assigned HA/HoA.
> 
> In my point of view, this is another issue (which may have solutions 
> like HAHA or CxT maybe)

I think Context Transfer as is (RFC 4067) wouldn't work here.  It is
experimental.  The other issue is that CxT works between two routers
nearby, and there are no route updates between them.  Bootstrapping a HA
  (from different subnet) to MN necessarily implies route or path updates
between the two HAs, such that the same HoA is now reachable from CN, at
the new HA.

HAHA (global HAHA) has been actively discussed recently in the NEMO WG.
  It is not yet clear (to me at least) how it will evolve.  Its current
status is that it is a personal proposal.

shim6 is yet another possibility to have two HAs in different subnets
serve same HoA.  It is not yet specified as such, but one could imagine
how to use it.

netlmm in the home network would work too.  But if we consider netlmm in
the home network we could as well consider it in the foreign network.
In which case MIP6 is not involved.

But the need for bootstrapping itself seems to be immediate, not later.

> we can assume the MN has no active session when it bootstrapps
> because in fact it is not yet a MN and so has not previous HA :)

Yes, I agree with you.

That is the role of pre-configured information.  For bootstrapping with
session continuity to work one would need a pre-configured information
that ensures that whenever the MN bootstraps it obtains same HoA and a
HA from same subnet.

I think I can not assume every time I reboot my phone I perform a
bootstrap assigning me a different HoA.  Or maybe I want to do such
bootstrap only when the phone is brand new.

Alex


_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Tue May 02 13:44:32 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FayvG-0004ZW-Ig; Tue, 02 May 2006 13:44:30 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FayvE-0004ZR-Q2
	for mip6@ietf.org; Tue, 02 May 2006 13:44:28 -0400
Received: from p-mail2.rd.francetelecom.com ([195.101.245.16])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FayvE-0006st-B9
	for mip6@ietf.org; Tue, 02 May 2006 13:44:28 -0400
Received: from ftrdmel3.rd.francetelecom.fr ([10.193.117.155]) by
	ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 2 May 2006 19:44:24 +0200
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Subject: RE: [Mip6] How to store DNS records about HAs,
	(draft-ietf-mip6-bootstrapping-split-02.txt)?
Date: Tue, 2 May 2006 19:44:22 +0200
Message-ID: <D2AA6DF1AEE4404F8D983B68BAC97CD202E2B9BF@ftrdmel3.rd.francetelecom.fr>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] How to store DNS records about HAs,
	(draft-ietf-mip6-bootstrapping-split-02.txt)?
Thread-Index: AcZuDOdN2z4YOmYyRsiLUEUHuNAiIgAASM5w
From: "COMBES Jean-Michel RD-MAPS-ISS" <jeanmichel.combes@francetelecom.com>
To: "Alexandru Petrescu" <alexandru.petrescu@motorola.com>
X-OriginalArrivalTime: 02 May 2006 17:44:24.0537 (UTC)
	FILETIME=[0D1FFC90:01C66E10]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6640e3bbe8a4d70c4469bcdcbbf0921d
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org



> -----Original Message-----
> From: Alexandru Petrescu [mailto:alexandru.petrescu@motorola.com]=20
> Sent: Tuesday, May 02, 2006 7:22 PM
> To: COMBES Jean-Michel RD-MAPS-ISS
> Cc: Gerardo Giaretta; Chowdhury, Kuntal; mip6@ietf.org
> Subject: Re: [Mip6] How to store DNS records about HAs,=20
> (draft-ietf-mip6-bootstrapping-split-02.txt)?
>=20
> COMBES Jean-Michel RD-MAPS-ISS wrote:
> >=20
> >=20
> >=20
> >> -----Original Message----- From: Alexandru Petrescu=20
> >> [mailto:alexandru.petrescu@motorola.com] Sent: Tuesday, May 02,
> >> 2006 6:48 PM To: COMBES Jean-Michel RD-MAPS-ISS Cc:=20
> Gerardo Giaretta;=20
> >> Chowdhury, Kuntal; mip6@ietf.org Subject: Re: [Mip6] How=20
> to store DNS=20
> >> records about HAs, (draft-ietf-mip6-bootstrapping-split-02.txt)?
> >>=20
> >> COMBES Jean-Michel RD-MAPS-ISS wrote:
> >>>> Alex PS: I don't think there's a clearcut  difference=20
> between "HA=20
> >>>> discovery" and "HA assignment".  DHAAD is mainly discovery
> >>>>=20
> >> but its
> >>>> effect is that MN gets its HA address, thus it is=20
> assigned the HA=20
> >>>> address.
> >>>>=20
> >>> Alex,
> >>>=20
> >>> When you book a room in a hotel, who does decide finally on
> >> the number
> >>> of your room? This is the hotel, regarding what type of
> >> room you want
> >>> and the ones that are available. This is assignment :)
> >> YEs, and this assignment does not guarantee forwarding of=20
> all my mail=20
> >> arriving at my house in my home country to the room=20
> assigned by that=20
> >> hotel.  (For that, I'll have to tell La Poste (USMail) my=20
> real house=20
> >> address and the room number at that hotel).
> >>=20
> >> I suppose I'm correct to understand that HA assignment=20
> will not offer=20
> >> session continuity from the previously assigned HA/HoA.
> >=20
> > In my point of view, this is another issue (which may have=20
> solutions=20
> > like HAHA or CxT maybe)
>=20
> I think Context Transfer as is (RFC 4067) wouldn't work here.=20
>  It is experimental.  The other issue is that CxT works=20
> between two routers nearby, and there are no route updates=20
> between them.  Bootstrapping a HA
>   (from different subnet) to MN necessarily implies route or=20
> path updates between the two HAs, such that the same HoA is=20
> now reachable from CN, at the new HA.
>=20
> HAHA (global HAHA) has been actively discussed recently in=20
> the NEMO WG.
>   It is not yet clear (to me at least) how it will evolve. =20
> Its current status is that it is a personal proposal.
>=20
> shim6 is yet another possibility to have two HAs in different=20
> subnets serve same HoA.  It is not yet specified as such, but=20
> one could imagine how to use it.
>=20
> netlmm in the home network would work too.  But if we=20
> consider netlmm in the home network we could as well consider=20
> it in the foreign network.
> In which case MIP6 is not involved.
>=20
> But the need for bootstrapping itself seems to be immediate,=20
> not later.
>=20
> > we can assume the MN has no active session when it=20
> bootstrapps because=20
> > in fact it is not yet a MN and so has not previous HA :)
>=20
> Yes, I agree with you.
>=20
> That is the role of pre-configured information.  For=20
> bootstrapping with session continuity to work one would need=20
> a pre-configured information that ensures that whenever the=20
> MN bootstraps it obtains same HoA and a HA from same subnet.
>=20
> I think I can not assume every time I reboot my phone I=20
> perform a bootstrap assigning me a different HoA.  Or maybe I=20
> want to do such bootstrap only when the phone is brand new.
>=20

That depends the MSP's policy. But, BTW, in your two examples,
impossible to have session continuity ;)

Another point (from draft-ietf-mip6-bootstrap-ps-04):

"1.2 What is Bootstrapping?
   Bootstrapping is defined as obtaining enough information at the
   mobile node so that the mobile node can successfully register with an
   appropriate home agent.  Specifically, this means obtaining the home
   agent address and home address, and for the mobile node and home
   agent to authenticate and mutually construct security credentials for
   Mobile IPv6.
   Typically, bootstrapping happens when a mobile node does not have all
   the information it needs to setup the Mobile IPv6 service.  This
   includes, but is not limited to, the mobile node (MN) not having any
   information when it boots up for the first time (out of the box), it
   does not retain any information during reboots, etc.
   Also, in certain scenarios, after the MN bootstraps for the first
   time (out of the box), subsequent bootstrapping is implementation-
   dependent.  For instance, the MN may bootstrap every time it boots,
   bootstrap everytime on prefix change, bootstrap periodically to
   anchor to an optimal (distance, load etc) HA, etc."

IMO, your session continuity issue is more linked to the HA reliability.


> Alex
>=20
>=20


Best regards.

JMC.

France Telecom - R&D Division - MAPS/NSS  =20
Jean-Michel COMBES, Internet/Intranet Security
E-Mail: jeanmichel.combes@francetelecom.com
Phone: +33 (0)1 45 29 45 94
Fax: +33 (0)1 45 29 65 19
Mobile: +33 (0)6 07 29 30 16=20

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Tue May 02 14:05:16 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FazFF-0007zu-Lk; Tue, 02 May 2006 14:05:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FazFE-0007zo-Fu
	for mip6@ietf.org; Tue, 02 May 2006 14:05:08 -0400
Received: from [129.188.136.9] (helo=ftpbox.mot.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FazFD-0007hF-6p
	for mip6@ietf.org; Tue, 02 May 2006 14:05:08 -0400
Received: from az33exr01.mot.com (az33exr01.mot.com [10.64.251.231])
	by ftpbox.mot.com (8.12.11/Motgate7) with ESMTP id k42IAIZK028413;
	Tue, 2 May 2006 13:10:23 -0500 (CDT)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by az33exr01.mot.com (8.13.1/8.13.0) with ESMTP id k42IR60x008235;
	Tue, 2 May 2006 13:27:07 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id 188B5865980; Tue,  2 May 2006 20:04:26 +0200 (CEST)
Message-ID: <44579F29.6090401@motorola.com>
Date: Tue, 02 May 2006 20:04:25 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: Vijay Devarapalli <vijay.devarapalli@AzaireNet.com>
Subject: Re: [Mip6] How to store DNS records about HAs,
	(draft-ietf-mip6-bootstrapping-split-02.txt)?
References: <D2AA6DF1AEE4404F8D983B68BAC97CD202E2B9BD@ftrdmel3.rd.francetelecom.fr>
	<44578D57.7030402@motorola.com> <445794C1.3080909@azairenet.com>
In-Reply-To: <445794C1.3080909@azairenet.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAQAAAAQ=
X-White-List-Member: TRUE
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Cc: mip6@ietf.org,
	COMBES Jean-Michel RD-MAPS-ISS <jeanmichel.combes@francetelecom.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Vijay Devarapalli wrote:
> Alexandru Petrescu wrote:
>> COMBES Jean-Michel RD-MAPS-ISS wrote:
>>>> Alex PS: I don't think there's a clearcut  difference between 
>>>> "HA discovery" and "HA assignment".  DHAAD is mainly discovery 
>>>> but its effect is that MN gets its HA address, thus it is 
>>>> assigned the HA address.
>>>> 
>>> 
>>> Alex,
>>> 
>>> When you book a room in a hotel, who does decide finally on the 
>>> number of your room? This is the hotel, regarding what type of 
>>> room you want and the ones that are available. This is assignment
>>>  :)
>> 
>> YEs, and this assignment does not guarantee forwarding of all my 
>> mail arriving at my house in my home country to the room assigned 
>> by that hotel.  (For that, I'll have to tell La Poste (USMail) my 
>> real house address and the room number at that hotel).
>> 
>> I suppose I'm correct to understand that HA assignment will not 
>> offer session continuity from the previously assigned HA/HoA.
> 
> yes. MIP6 bootstrapping enables scenarios where the IPv6 HoA is no 
> longer the identity of the mobile node. there is a separate identity 
> and every time the mobile node bootstraps it could get a new HoA and 
> HA.

But applications use IPv6 addresses, not other separate identities.  If
I have an app that uses an id which is not the IPv6 address (i.e. a
skype id) then just use DHCPv6 not MIP6, no?

Alex

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Tue May 02 14:16:39 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FazQL-0001zf-Ah; Tue, 02 May 2006 14:16:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FazQK-0001za-LB
	for mip6@ietf.org; Tue, 02 May 2006 14:16:36 -0400
Received: from mail1.azairenet.com ([66.92.223.4] helo=bart.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FazQJ-0007tP-Ac
	for mip6@ietf.org; Tue, 02 May 2006 14:16:36 -0400
Received: from [10.1.201.19] ([10.1.201.19]) by bart.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Tue, 2 May 2006 11:16:30 -0700
Message-ID: <4457A1FE.2020405@azairenet.com>
Date: Tue, 02 May 2006 11:16:30 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.2 (Windows/20060308)
MIME-Version: 1.0
To: Alexandru Petrescu <alexandru.petrescu@motorola.com>
Subject: Re: [Mip6] How to store DNS records about HAs,
	(draft-ietf-mip6-bootstrapping-split-02.txt)?
References: <D2AA6DF1AEE4404F8D983B68BAC97CD202E2B9BD@ftrdmel3.rd.francetelecom.fr>
	<44578D57.7030402@motorola.com> <445794C1.3080909@azairenet.com>
	<44579F29.6090401@motorola.com>
In-Reply-To: <44579F29.6090401@motorola.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 02 May 2006 18:16:30.0973 (UTC)
	FILETIME=[895ECAD0:01C66E14]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: mip6@ietf.org,
	COMBES Jean-Michel RD-MAPS-ISS <jeanmichel.combes@francetelecom.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Alexandru Petrescu wrote:

>>> YEs, and this assignment does not guarantee forwarding of all my mail 
>>> arriving at my house in my home country to the room assigned by that 
>>> hotel.  (For that, I'll have to tell La Poste (USMail) my real house 
>>> address and the room number at that hotel).
>>>
>>> I suppose I'm correct to understand that HA assignment will not offer 
>>> session continuity from the previously assigned HA/HoA.
>>
>> yes. MIP6 bootstrapping enables scenarios where the IPv6 HoA is no 
>> longer the identity of the mobile node. there is a separate identity 
>> and every time the mobile node bootstraps it could get a new HoA and HA.
> 
> But applications use IPv6 addresses, not other separate identities.  If
> I have an app that uses an id which is not the IPv6 address (i.e. a
> skype id) then just use DHCPv6 not MIP6, no?

you can do that. but if you move and your IP
address changes changes while the skype session is
on, the session might break.

Alex, there are a fourth step described in the
bootstrapping documents. Dynamic DNS update for the
MN. by using that mechanism, the MN can ensure its
current HoA is always in the DNS entry. so even if
the HoA changes everytime the MN bootstraps, the MN
can at least ensure CNs get the right HoA when they
do a DNS lookup for the MN.

Vijay

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Tue May 02 14:18:28 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FazS8-0003Bc-FL; Tue, 02 May 2006 14:18:28 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FazS6-0003BX-GD
	for mip6@ietf.org; Tue, 02 May 2006 14:18:26 -0400
Received: from motgate7.mot.com ([129.188.136.7])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FazRY-0007v4-OH
	for mip6@ietf.org; Tue, 02 May 2006 14:18:26 -0400
Received: from az33exr03.mot.com ([10.64.251.233])
	by motgate7.mot.com (8.12.11/Motgate7) with ESMTP id k42InKsU014072;
	Tue, 2 May 2006 11:49:20 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by az33exr03.mot.com (8.13.1/8.13.0) with ESMTP id k42IYF2K021531;
	Tue, 2 May 2006 13:34:16 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id C116D865980; Tue,  2 May 2006 20:17:16 +0200 (CEST)
Message-ID: <4457A22C.9050102@motorola.com>
Date: Tue, 02 May 2006 20:17:16 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: COMBES Jean-Michel RD-MAPS-ISS <jeanmichel.combes@francetelecom.com>
Subject: Re: [Mip6] How to store DNS records about HAs,
	(draft-ietf-mip6-bootstrapping-split-02.txt)?
References: <D2AA6DF1AEE4404F8D983B68BAC97CD202E2B9BF@ftrdmel3.rd.francetelecom.fr>
In-Reply-To: <D2AA6DF1AEE4404F8D983B68BAC97CD202E2B9BF@ftrdmel3.rd.francetelecom.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAQAAAAQ=
X-White-List-Member: TRUE
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 932cba6e0228cc603da43d861a7e09d8
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

COMBES Jean-Michel RD-MAPS-ISS wrote:
> 
>> -----Original Message----- From: Alexandru Petrescu 
>> [mailto:alexandru.petrescu@motorola.com] Sent: Tuesday, May 02, 
>> 2006 7:22 PM To: COMBES Jean-Michel RD-MAPS-ISS Cc: Gerardo 
>> Giaretta; Chowdhury, Kuntal; mip6@ietf.org Subject: Re: [Mip6] How 
>> to store DNS records about HAs, 
>> (draft-ietf-mip6-bootstrapping-split-02.txt)?
>> 
>> COMBES Jean-Michel RD-MAPS-ISS wrote:
>>> 
>>> 
>>>> -----Original Message----- From: Alexandru Petrescu 
>>>> [mailto:alexandru.petrescu@motorola.com] Sent: Tuesday, May 02,
>>>>  2006 6:48 PM To: COMBES Jean-Michel RD-MAPS-ISS Cc:
>> Gerardo Giaretta;
>>>> Chowdhury, Kuntal; mip6@ietf.org Subject: Re: [Mip6] How
>> to store DNS
>>>> records about HAs, 
>>>> (draft-ietf-mip6-bootstrapping-split-02.txt)?
>>>> 
>>>> COMBES Jean-Michel RD-MAPS-ISS wrote:
>>>>>> Alex PS: I don't think there's a clearcut  difference
>> between "HA
>>>>>> discovery" and "HA assignment".  DHAAD is mainly discovery
>>>>>> 
>>>> but its
>>>>>> effect is that MN gets its HA address, thus it is
>> assigned the HA
>>>>>> address.
>>>>>> 
>>>>> Alex,
>>>>> 
>>>>> When you book a room in a hotel, who does decide finally on
>>>> the number
>>>>> of your room? This is the hotel, regarding what type of
>>>> room you want
>>>>> and the ones that are available. This is assignment :)
>>>> YEs, and this assignment does not guarantee forwarding of
>> all my mail
>>>> arriving at my house in my home country to the room
>> assigned by that
>>>> hotel.  (For that, I'll have to tell La Poste (USMail) my
>> real house
>>>> address and the room number at that hotel).
>>>> 
>>>> I suppose I'm correct to understand that HA assignment
>> will not offer
>>>> session continuity from the previously assigned HA/HoA.
>>> In my point of view, this is another issue (which may have
>> solutions
>>> like HAHA or CxT maybe)
>> I think Context Transfer as is (RFC 4067) wouldn't work here. It is
>>  experimental.  The other issue is that CxT works between two 
>> routers nearby, and there are no route updates between them. 
>> Bootstrapping a HA (from different subnet) to MN necessarily 
>> implies route or path updates between the two HAs, such that the 
>> same HoA is now reachable from CN, at the new HA.
>> 
>> HAHA (global HAHA) has been actively discussed recently in the NEMO
>>  WG. It is not yet clear (to me at least) how it will evolve. Its 
>> current status is that it is a personal proposal.
>> 
>> shim6 is yet another possibility to have two HAs in different 
>> subnets serve same HoA.  It is not yet specified as such, but one 
>> could imagine how to use it.
>> 
>> netlmm in the home network would work too.  But if we consider 
>> netlmm in the home network we could as well consider it in the 
>> foreign network. In which case MIP6 is not involved.
>> 
>> But the need for bootstrapping itself seems to be immediate, not 
>> later.
>> 
>>> we can assume the MN has no active session when it
>> bootstrapps because
>>> in fact it is not yet a MN and so has not previous HA :)
>> Yes, I agree with you.
>> 
>> That is the role of pre-configured information.  For bootstrapping 
>> with session continuity to work one would need a pre-configured 
>> information that ensures that whenever the MN bootstraps it obtains
>>  same HoA and a HA from same subnet.
>> 
>> I think I can not assume every time I reboot my phone I perform a 
>> bootstrap assigning me a different HoA.  Or maybe I want to do such
>>  bootstrap only when the phone is brand new.
>> 
> 
> That depends the MSP's policy. But, BTW, in your two examples, 
> impossible to have session continuity ;)

Well, if any of the protocols mentioned is matured and used, then there
may be.  But one can't assume that so early.

> Another point (from draft-ietf-mip6-bootstrap-ps-04):

I agree, the draft takes bootstrapping as an operation that happens
relatively rarely.

> "1.2 What is Bootstrapping? Bootstrapping is defined as obtaining 
> enough information at the mobile node so that the mobile node can 
> successfully register with an appropriate home agent.  Specifically, 
> this means obtaining the home agent address and home address, and for
> the mobile node and home agent to authenticate and mutually construct
> security credentials for Mobile IPv6. Typically, bootstrapping
> happens when a mobile node does not have all the information it needs
> to setup the Mobile IPv6 service.  This includes, but is not limited
> to, the mobile node (MN) not having any information when it boots up
> for the first time (out of the box), it does not retain any
> information during reboots, etc.

Any device booting up has some user information based on which to rely.
  BOOTP and DHCP use the MAC addresses.  GSM phones use some IMEI or
other data in the SIM card.  Sometimes NAI is used and based on it one
would obtain same IP address at house from ISP.

> Also, in certain scenarios, after the MN bootstraps for the first 
> time (out of the box), subsequent bootstrapping is implementation- 
> dependent.  For instance, the MN may bootstrap every time it boots, 
> bootstrap everytime on prefix change, bootstrap periodically to 
> anchor to an optimal (distance, load etc) HA, etc."

I think this is a wide qualification.  I'd suggest only keep a minimal
scenario for bootstrapping, maybe only when out-of-the-box only.

When home prefix changes there's MPD.

Optimal anchor and distance are not really defined or known supporting
protocol.

Most certainly not do a change-HoA bootstrapping everytime it powers up,
it's too often, I think.

> IMO, your session continuity issue is more linked to the HA 
> reliability.

I don't think so, just session continuity as offered by plain MIP6.

Alex


_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Tue May 02 14:20:52 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FazUS-0005Nk-47; Tue, 02 May 2006 14:20:52 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FazUR-0005Nf-6w
	for mip6@ietf.org; Tue, 02 May 2006 14:20:51 -0400
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FazUP-0007yE-Ui
	for mip6@ietf.org; Tue, 02 May 2006 14:20:51 -0400
Received: from il06exr04.mot.com (il06exr04.mot.com [129.188.137.134])
	by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id k42IbWtI026770;
	Tue, 2 May 2006 11:37:32 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by il06exr04.mot.com (8.13.1/8.13.0) with ESMTP id k42IYkR1009568;
	Tue, 2 May 2006 13:34:46 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id 53BE3865980; Tue,  2 May 2006 20:20:33 +0200 (CEST)
Message-ID: <4457A2F0.6030309@motorola.com>
Date: Tue, 02 May 2006 20:20:32 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: Vijay Devarapalli <vijay.devarapalli@AzaireNet.com>
Subject: Re: [Mip6] How to store DNS records about HAs,
	(draft-ietf-mip6-bootstrapping-split-02.txt)?
References: <8A16DAD84432534FBFC19FD92B50512F05B97A15@ames.starentnetworks.com>	<eaa74a7e0605010238s36eef57fm23b8fba6b3d9eaac@mail.gmail.com>
	<44574A1D.2060603@motorola.com> <4457954E.4080709@azairenet.com>
In-Reply-To: <4457954E.4080709@azairenet.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAQAAAAQ=
X-White-List-Member: TRUE
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: mip6@ietf.org,
	COMBES Jean-Michel RD-MAPS-ISS <jeanmichel.combes@francetelecom.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Vijay Devarapalli wrote:
> Alexandru Petrescu wrote:
>> For split, (1) specify that HA updates the DNS with its own 
>> address, maybe via DHCP, with a new type of SRV record or
> 
> I dont think this should be specified in the split bootstrapping 
> document. this is out of scope for this document.
> 
> regarding your proposal, the HA does not use DHCP to get it owns 
> address. so it can't use DHCP to update its DNS entries.

I think you're right, but then how?

I think that if we agree that the "cold" bootstrapping should happen
only once, when out-of-the-box,  offering new HA/HoA data then
subsequent power-ups and related bootstrapping should offer same subnet
HA/HoA.  This can be achieved only if the DNS retrieves same data based 
on same key (maybe the fqdn).

But if we think that "cold" bootstrapping with a change in HoA happens 
any time the phone powers up then yes, no need to relate the HA 
subnet/HoA to the key MN uses for bootstrapping.

Alex


_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Tue May 02 15:00:51 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fb077-0005nF-JC; Tue, 02 May 2006 15:00:49 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fb075-0005nA-Fr
	for mip6@ietf.org; Tue, 02 May 2006 15:00:47 -0400
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fb06q-0001S0-U3
	for mip6@ietf.org; Tue, 02 May 2006 15:00:47 -0400
Received: from az33exr01.mot.com ([10.64.251.231])
	by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id k42JGfqT006135;
	Tue, 2 May 2006 12:16:45 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by az33exr01.mot.com (8.13.1/8.13.0) with ESMTP id k42JML7d016138;
	Tue, 2 May 2006 14:22:22 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id A3D4F865980; Tue,  2 May 2006 20:59:40 +0200 (CEST)
Message-ID: <4457AC1C.2010407@motorola.com>
Date: Tue, 02 May 2006 20:59:40 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: Vijay Devarapalli <vijay.devarapalli@AzaireNet.com>
Subject: Re: [Mip6] How to store DNS records about HAs,
	(draft-ietf-mip6-bootstrapping-split-02.txt)?
References: <D2AA6DF1AEE4404F8D983B68BAC97CD202E2B9BD@ftrdmel3.rd.francetelecom.fr>
	<44578D57.7030402@motorola.com> <445794C1.3080909@azairenet.com>
	<44579F29.6090401@motorola.com> <4457A1FE.2020405@azairenet.com>
In-Reply-To: <4457A1FE.2020405@azairenet.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAQAAAAQ=
X-White-List-Member: TRUE
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Cc: mip6@ietf.org,
	COMBES Jean-Michel RD-MAPS-ISS <jeanmichel.combes@francetelecom.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Vijay Devarapalli wrote:
> Alexandru Petrescu wrote:
> 
>>>> YEs, and this assignment does not guarantee forwarding of all 
>>>> my mail arriving at my house in my home country to the room 
>>>> assigned by that hotel.  (For that, I'll have to tell La Poste
>>>>  (USMail) my real house address and the room number at that 
>>>> hotel).
>>>> 
>>>> I suppose I'm correct to understand that HA assignment will not
>>>>  offer session continuity from the previously assigned HA/HoA.
>>> 
>>> yes. MIP6 bootstrapping enables scenarios where the IPv6 HoA is 
>>> no longer the identity of the mobile node. there is a separate 
>>> identity and every time the mobile node bootstraps it could get a
>>>  new HoA and HA.
>> 
>> But applications use IPv6 addresses, not other separate identities.
>>  If I have an app that uses an id which is not the IPv6 address 
>> (i.e. a skype id) then just use DHCPv6 not MIP6, no?
> 
> you can do that. but if you move and your IP address changes changes
>  while the skype session is on, the session might break.

Right, if the laptop's IP address changes (with DHCP, no MIP) its
ongoing sessions will break, I think it's the case with skype.  But when
acquiring a new address the laptop will be again reachable at same skype id.

> Alex, there are a fourth step described in the bootstrapping 
> documents. Dynamic DNS update for the MN. by using that mechanism, 
> the MN can ensure its current HoA is always in the DNS entry. so even
>  if the HoA changes everytime the MN bootstraps, the MN can at least
>  ensure CNs get the right HoA when they do a DNS lookup for the MN.

For DNS update to offer session continuity at a permanent fqdn, it's
assumed that apps will DNS resolve their peer's fqdn every time an
ongoing session breaks.  I think this behaviour is unusual.  At least we
can't plan to re-program all apps to do so.

What DNS update in the home network offers is reachability at a
permanent fqdn (just as skype offers permanent skype id, with DHCP); but
DNS update too might involve breaking the session continuity at same IP
address, no?

Alex

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Wed May 03 10:58:22 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FbInr-00033a-Rf; Wed, 03 May 2006 10:58:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FbInq-00033V-Oq
	for mip6@ietf.org; Wed, 03 May 2006 10:58:10 -0400
Received: from p-mail2.rd.francetelecom.com ([195.101.245.16])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FbInn-0003wo-AH
	for mip6@ietf.org; Wed, 03 May 2006 10:58:10 -0400
Received: from FTRDMEL2.rd.francetelecom.fr ([10.193.117.153]) by
	ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 3 May 2006 16:58:06 +0200
Content-class: urn:content-classes:message
MIME-Version: 1.0
x-mimeole: Produced By Microsoft Exchange V6.5
Date: Wed, 3 May 2006 16:58:04 +0200
Message-ID: <BBBE5BAA3B351C488C415EA662EA8840033329EE@FTRDMEL2.rd.francetelecom.fr>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: New Draft: Problem Statement for Global IP Mobility
Thread-Index: AcZuwxmLmAwnd9FxR/KxHLFi5tkw9w==
From: "NJEDJOU Eric RD-RESA-REN" <eric.njedjou@francetelecom.com>
To: <mip6@ietf.org>
X-OriginalArrivalTime: 03 May 2006 14:58:06.0005 (UTC)
	FILETIME=[FBDE9650:01C66EC1]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 21bf7a2f1643ae0bf20c1e010766eb78
Subject: [Mip6] New Draft: Problem Statement for Global IP Mobility
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0619799780=="
Errors-To: mip6-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0619799780==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C66EC1.FB1386DD"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C66EC1.FB1386DD
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi all,

There was an Ad-Hoc BOF on the right mobility management architecture
for the Internet initiated by James Kempf during the Dallas Meeting.
Global IP Mobility Management was discussed and a rough consensus was
made to develop the discussions to make the problem better understood.
Couple IAB members were present.

draft-njedjou-netlmm-globalmm-ps-00.txt was presented and received
several comments. Following the Ad-Hoc, a new version has just been
released, with a new title.=20

Name: draft-njedjou-globalmm-ps-01.txt
Title: Problem Statement for Global IP Mobility
Authors: Eric Njedjou, Julien Riera, France Telecom

Abstract:
This document discusses the problem of global IP mobility management in
a context where some mobile operators and service providers are looking
for adequate solutions to the inter-system IP mobility problem. The
document addresses the specific issue of moving between IP access
domains that use different mobility management protocols and mechanisms.
Indeed this type of movement would be an important subset of global IP
mobility scenarios.

Version 01 is available at the following link:
http://perso.rd.francetelecom.fr/njedjou/draft-njedjou-globalmm-ps-00.tx
t

Major changes from 00 include:

*	Re-defining global IP mobility=20
*	Adressing both single and multiple operators mobility scenarios
(with both terminal and network centric schemes)
*	Adressing other comments received during the ad-hoc=20
*	Developing issues with existing global IP mobility solutions

Please provide comments


Best Regards
Eric Njedjou

------_=_NextPart_001_01C66EC1.FB1386DD
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7638.1">
<TITLE>New Draft: Problem Statement for Global IP Mobility</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><FONT SIZE=3D2 FACE=3D"Arial">Hi all,</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">There was an Ad-Hoc BOF on the right =
mobility management architecture for the Internet initiated by James =
Kempf during the Dallas Meeting. Global IP Mobility Management was =
discussed and a rough consensus was made to develop the discussions to =
make the problem better understood. Couple IAB members were =
present.</FONT></P>

<P><SPAN LANG=3D"nl"><FONT SIZE=3D2 =
FACE=3D"Arial">draft-njedjou-netlmm-globalmm-ps-00.txt was presented and =
received several comments. Following the Ad-Hoc, a new version has just =
been released, with a new title. </FONT></SPAN></P>

<P><SPAN LANG=3D"nl"><B><FONT SIZE=3D2 FACE=3D"Arial">Name:</FONT></B> =
<FONT SIZE=3D2 =
FACE=3D"Arial">draft-njedjou-globalmm-ps-01.txt</FONT></SPAN>

<BR><B><SPAN LANG=3D"en-us"><FONT SIZE=3D2 =
FACE=3D"Arial">Title:</FONT></SPAN></B><SPAN LANG=3D"en-us"><FONT =
SIZE=3D2 FACE=3D"Arial"> Problem Statement for Global IP =
Mobility</FONT></SPAN>

<BR><SPAN LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Arial">Authors:</FONT></B><FONT SIZE=3D2 FACE=3D"Arial"> Eric =
Njedjou, Julien Riera, France Telecom</FONT></SPAN>
</P>

<P><SPAN LANG=3D"en-us"><B><FONT SIZE=3D2 =
FACE=3D"Arial">Abstract:</FONT></B></SPAN>

<BR><SPAN LANG=3D"en-us"><FONT SIZE=3D2 FACE=3D"Arial">This document =
discusses the problem of global IP mobility management in a context =
where some mobile operators and service providers are looking for =
adequate solutions to the inter-system IP mobility problem. The document =
addresses the specific issue of moving between IP access domains that =
use different mobility management protocols and mechanisms. Indeed this =
type of movement would be an important subset of global IP mobility =
scenarios.</FONT></SPAN><SPAN LANG=3D"fr"></SPAN></P>

<P><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">Version 01 is =
available at the following link:</FONT></SPAN>

<BR><SPAN LANG=3D"fr"></SPAN><A =
HREF=3D"http://perso.rd.francetelecom.fr/njedjou/draft-njedjou-globalmm-p=
s-00.txt"><SPAN LANG=3D"fr"><U><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">http://perso.rd.francetelecom.fr/njedjou/draft-njedjou-glo=
balmm-ps-00.txt</FONT></U></SPAN></A><SPAN LANG=3D"fr"></SPAN>
</P>

<P><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">Major changes from 00 =
include:</FONT></SPAN>
</P>

<UL>
<LI><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">Re-defining global =
IP mobility </FONT></SPAN></LI>

<LI><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">Adressing both =
single and multiple operators mobility scenarios (with both terminal and =
network centric schemes)</FONT></SPAN></LI>

<LI><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">Adressing other =
comments received during the ad-hoc </FONT></SPAN></LI>

<LI><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">Developing issues =
with existing global IP mobility solutions</FONT></SPAN></LI>
<BR>
</UL>
<P><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">Please provide =
comments</FONT></SPAN>
</P>
<BR>

<P><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">Best =
Regards</FONT></SPAN>

<BR><SPAN LANG=3D"fr"><FONT SIZE=3D2 FACE=3D"Arial">Eric =
Njedjou</FONT></SPAN>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C66EC1.FB1386DD--


--===============0619799780==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6

--===============0619799780==--




From mip6-bounces@ietf.org Wed May 03 14:14:52 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FbLrw-0001yn-6A; Wed, 03 May 2006 14:14:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FbLrv-0001yf-Fc
	for mip6@ietf.org; Wed, 03 May 2006 14:14:35 -0400
Received: from hostree9f.alcatel.com ([143.209.238.159]
	helo=audl952.usa.alcatel.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FbLrs-0003cb-RI
	for mip6@ietf.org; Wed, 03 May 2006 14:14:35 -0400
Received: from usdaln07347 (usdaln07347.usa.alcatel.com [143.209.105.69])
	by audl952.usa.alcatel.com (ALCANET) with ESMTP id k43IEQWx006933;
	Wed, 3 May 2006 13:14:26 -0500
From: "Tim Ozugur" <tim.ozugur@alcatel.com>
To: <mip6@ietf.org>
Date: Wed, 3 May 2006 13:14:25 -0500
Message-ID: <00ac01c66edd$695d5570$4569d18f@ad3.ad.alcatel.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1807
Thread-index: AcZu3RZf2J7ICLthSTyN8QWpYrkJBwAAEI0Q
X-Scanned-By: MIMEDefang 2.51 on 143.209.238.34
X-Spam-Score: 0.1 (/)
X-Scan-Signature: a1dc446dc7ac353b90b60743d0e479e3
Cc: tpc@bwan.org
Subject: [Mip6] Call For Papers: BWAN 2006
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0064552599=="
Errors-To: mip6-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0064552599==
Content-Type: multipart/related;
	boundary="----=_NextPart_000_00AD_01C66EB3.80874D70"

This is a multi-part message in MIME format.

------=_NextPart_000_00AD_01C66EB3.80874D70
Content-Type: multipart/alternative;
	boundary="----=_NextPart_001_00AE_01C66EB3.80874D70"


------=_NextPart_001_00AE_01C66EB3.80874D70
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit

(Apologies if you are receiving this message more than once)

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

CALL FOR PAPERS

INTERNATIONAL WORKSHOP ON BROADBAND WIRELESS

ACCESS FOR UBIQUITOUS NETWORKING (BWAN 2006)

20 September 2006 - Alghero, Sardinia, Italy 

(www.bwan.org)

Technically sponsored by IEEE (approval pending) 

 

IMPORTANT DATES:

Submission of Summaries: 15 May 2006

 

SPECIAL STUDENT REGISTRATION RATE: 

Early registration rate for students: USD 270 (cut-off date: one month prior
to the workshop)

The late registration rate for students: USD 320

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

Scope and Interests 

Today Broadband Wireless access (mobile/nomadic) is emerging to offer
outstanding opportunities. In this new world of communicating devices, the
evolution towards ubiquitous networking is promising new paradigm with the
aim of providing communication capability all the time, everywhere,
transparently and invisibly to the user, using devices embedded in the
surrounding physical environment. The implementation of such a paradigm
requires innovation in wireless network technologies and devices,
development of infrastructures, enablers supporting enhanced features for
ubiquitous capability. 
The workshop is intended to present features based on new architectures
supporting mobility and/or nomadic features for wireless access (IEEE
802.yx, Mesh,...), the sharing of the network access, bandwidth sharing on
radio access, network enablers all favoring the new perspective of
ubiquitous and ambient networking. Within the framework of BWAN 2006, the
next generation of network access will be investigated. 
Topics of interest to this workshop include (but are not limited to)
performance studies and solutions (algorithms, protocols, architectures)
that tend to improve experience of users of services and applications with
context awareness. 


Workshop topics 

  <http://www.bwan.org/immagini/punto_elenco.gif>   New Architectures and
technologies for broadband wireless access (xDSL/FTTx,etc) with mobility
features 

  <http://www.bwan.org/immagini/punto_elenco.gif>   3G and beyond 

  <http://www.bwan.org/immagini/punto_elenco.gif>   Ambient Networking 

  <http://www.bwan.org/immagini/punto_elenco.gif>   AAA (Authentication,
Authorization, Accounting) 

  <http://www.bwan.org/immagini/punto_elenco.gif>   QoS efficient and
scalable routing 

  <http://www.bwan.org/immagini/punto_elenco.gif>   Transport mechanism for
supporting various high speed traffics

  <http://www.bwan.org/immagini/punto_elenco.gif>   End to end security and
privacy issues for ubiquitous Network access

  <http://www.bwan.org/immagini/punto_elenco.gif>   xDSL/FTTx+WiFi modem
with mobility enhancement 

  <http://www.bwan.org/immagini/punto_elenco.gif>   Radio extension such as
802.xy (WiFi, WiMax, etc) P2P network 

  <http://www.bwan.org/immagini/punto_elenco.gif>   Standard and regulations

  <http://www.bwan.org/immagini/punto_elenco.gif>   Low cost and low power
integrated Modulation

  <http://www.bwan.org/immagini/punto_elenco.gif>   Network cost performance
and Business Models

  <http://www.bwan.org/immagini/punto_elenco.gif>   RFID tags,
sensors,actuators, etc

  <http://www.bwan.org/immagini/punto_elenco.gif>   Interference mitigation
for multiple access

  <http://www.bwan.org/immagini/punto_elenco.gif>   IPv6 impact

  <http://www.bwan.org/immagini/punto_elenco.gif>   Cognitive radio


Submission Dates 

  <http://www.bwan.org/immagini/punto_elenco.gif>   Submission of summaries:
15 May 2006

  <http://www.bwan.org/immagini/punto_elenco.gif>   Notification of
Acceptance: 15 June 2006 


  <http://www.bwan.org/immagini/punto_elenco.gif>   Submission Camera Ready
Papers: 10 July 2006 


Publication 

The submissions to be presented at the workshop will be selected, based on
their originality, technical merit and topical relevance of their contents.
All accepted papers will be published in the conference proceedings that
will be available at the workshop.


------=_NextPart_001_00AE_01C66EB3.80874D70
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2800.1528" name=3DGENERATOR></HEAD>
<BODY>
<DIV></DIV>
<DIV><FONT face=3DArial><FONT face=3DVerdana><FONT color=3D#003366><B>
<P><FONT size=3D2>(Apologies if you are receiving this message more than =

once)</FONT></P>
<P><FONT =
size=3D2>--------------------------------------------------</FONT></P>
<P><FONT size=3D2>CALL FOR PAPERS</FONT></P>
<P><FONT size=3D2>INTERNATIONAL WORKSHOP ON BROADBAND =
WIRELESS</FONT></P>
<P><FONT size=3D2>ACCESS FOR UBIQUITOUS NETWORKING (BWAN =
2006)</FONT></P>
<P><FONT size=3D2></FONT></P>
<P><FONT size=3D2>20 September 2006 - Alghero, Sardinia, Italy =
</FONT></P>
<P><FONT size=3D2>(</FONT><A href=3D"www.bwan.org"><U><FONT =
color=3D#0000ff><FONT=20
size=3D2>www.bwan.org</FONT></U></FONT></A><FONT size=3D2>)</FONT></P>
<P><FONT size=3D2>Technically sponsored by IEEE (approval pending) =
</FONT></P>
<P><FONT size=3D2></FONT>&nbsp;</P>
<P><FONT size=3D2>IMPORTANT DATES:</FONT></P>
<P><FONT size=3D2>Submission of Summaries: 15 May 2006</FONT></P>
<P><FONT face=3DArial size=3D2><SPAN=20
class=3D348430518-03052006></SPAN></FONT>&nbsp;</P>
<P><FONT face=3DArial size=3D2><SPAN class=3D348430518-03052006>SPECIAL =
STUDENT=20
REGISTRATION RATE: </SPAN></FONT></P>
<P><FONT face=3DArial><FONT size=3D2><SPAN =
class=3D348430518-03052006>E</SPAN>arly=20
registration rate for students: USD 270<SPAN class=3D348430518-03052006> =
(cut-off=20
date:&nbsp;one month prior to the workshop)</SPAN></FONT></FONT></P>
<P><FONT face=3DArial><FONT size=3D2><SPAN=20
class=3D348430518-03052006></SPAN></FONT></FONT><FONT face=3DArial =
size=3D2>The late=20
registration rate for students: USD 320</FONT></P>
<P><FONT=20
size=3D2>---------------------------------------------------</FONT></P></=
B></FONT></FONT>
<P align=3Djustify><FONT size=3D2><FONT face=3DVerdana><FONT =
color=3D#003366><B>Scope=20
and Interests</B> </FONT><BR><BR>Today Broadband Wireless access=20
(mobile/nomadic) is emerging to offer outstanding opportunities. In this =
new=20
world of communicating devices, the evolution towards ubiquitous =
networking is=20
promising new paradigm with the aim of providing communication =
capability all=20
the time, everywhere, transparently and invisibly to the user, using =
devices=20
embedded in the surrounding physical environment. The implementation of =
such a=20
paradigm requires innovation in wireless network technologies and =
devices,=20
development of infrastructures, enablers supporting enhanced features =
for=20
ubiquitous capability. <BR>The workshop is intended to present features =
based on=20
new architectures supporting mobility and/or nomadic features for =
wireless=20
access (IEEE 802.yx, Mesh,...), the sharing of the network access, =
bandwidth=20
sharing on radio access, network enablers all favoring the new =
perspective of=20
ubiquitous and ambient networking. Within the framework of BWAN 2006, =
the next=20
generation of network access will be investigated. <BR>Topics of =
interest to=20
this workshop include (but are not limited to) performance studies and =
solutions=20
(algorithms, protocols, architectures) that tend to improve experience =
of users=20
of services and applications with context awareness. <BR><BR><BR><FONT=20
color=3D#003366><B>Workshop topics</B> </FONT><BR><BR><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp; New=20
Architectures and technologies for broadband wireless access =
(xDSL/FTTx,etc)=20
with mobility features </FONT></FONT></P>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp; 3G=20
and beyond </FONT></P>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp;=20
Ambient Networking </FONT></P>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp; AAA=20
(Authentication, Authorization, Accounting) </FONT></P>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp; QoS=20
efficient and sca<SPAN class=3D348430518-03052006>la</SPAN>ble routing =
</FONT></P>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp;=20
Transport mechanism for supporting various high speed =
traffics</FONT></P>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp; End=20
to end security and privacy issues for ubiquitous Network =
access</FONT></P>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp;=20
xDSL/FTTx+WiFi modem with mobility enhancement </FONT></P>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp;=20
Radio extension such as 802.xy (WiFi, WiMax, etc) P2P network =
</FONT></P>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp;=20
Standard and regulations</FONT></P>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp; Low=20
cost and low power integrated Modulation</FONT></P>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp;=20
Network cost performance and Business Models</FONT></P>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp;=20
RFID tags, sensors,actuators, etc</FONT></P>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp;=20
Interference mitigation for multiple access</FONT></P>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp;=20
IPv6 impact</FONT></P>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp;=20
Cognitive radio</FONT></P><BR>
<P align=3Djustify><FONT color=3D#003366><FONT size=3D2><FONT=20
face=3DVerdana><B>Submission Dates</B> </FONT></FONT></FONT></P>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp;=20
Submission of summaries: 15 May 2006</FONT></P>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp;=20
Notification of Acceptance: 15 June 2006 </FONT>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D11 =
border=3D0>&nbsp;=20
Submission Camera Ready Papers: 10 July 2006 </FONT></P><BR>
<P align=3Djustify><FONT size=3D2><FONT face=3DVerdana><FONT=20
color=3D#003366><B>Publication</B> </FONT><BR><BR>The submissions to be =
presented=20
at the workshop will be selected, based on their originality, technical =
merit=20
and topical relevance of their contents. All accepted papers will be =
published=20
in the conference proceedings that will be available at the=20
workshop.</FONT></FONT></P></FONT></DIV></BODY></HTML>

------=_NextPart_001_00AE_01C66EB3.80874D70--

------=_NextPart_000_00AD_01C66EB3.80874D70
Content-Type: image/gif;
	name="punto_elenco.gif"
Content-Transfer-Encoding: base64
Content-Location: http://www.bwan.org/immagini/punto_elenco.gif

R0lGODlhDAAMAHcAACH/C01TT0ZGSUNFOS4wDQAAAAFzUkdCAK7OHOkAIf8LTVNPRkZJQ0U5LjAY
AAAADG1zT1BNU09GRklDRTkuMAgRTF2IACH/C01TT0ZGSUNFOS4wGAAAAAxjbVBQSkNtcDA3MTIC
AAABDAfaGwAh+QQBAAAAACwAAAAADAAMAIPAwMDMmTPMmQDMZgDMMwCZZgCZMwCZAAABAgMBAgMB
AgMBAgMBAgMBAgMBAgMBAgMDKQi63P4wPjMGuYYwUjkRA1MYVDUETKZa4UKqlOYSRoG1Ss1izGH4
L0MCADs=

------=_NextPart_000_00AD_01C66EB3.80874D70--



--===============0064552599==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6

--===============0064552599==--





From mip6-bounces@ietf.org Fri May 05 02:36:40 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FbtvQ-0000SP-J5; Fri, 05 May 2006 02:36:28 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FbtvP-0000OO-Ax
	for mip6@ietf.org; Fri, 05 May 2006 02:36:27 -0400
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FbtvO-0003O4-U2
	for mip6@ietf.org; Fri, 05 May 2006 02:36:27 -0400
Received: from c1-vpn7.isi.edu (c1-vpn7.isi.edu [128.9.176.37])
	by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id k456ZGN24597
	for <mip6@ietf.org>; Thu, 4 May 2006 23:35:16 -0700 (PDT)
From: Wei Ye <weiye@ISI.EDU>
To: mip6@ietf.org
Content-Type: text/plain
Date: Thu, 04 May 2006 23:35:13 -0700
Message-Id: <1146810913.3374.32.camel@localhost.localdomain>
Mime-Version: 1.0
X-Mailer: Evolution 2.2.3 (2.2.3-2.fc4) 
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: weiye@isi.edu
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4
Subject: [Mip6] ACM SenSys'06 call for posters and demos
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Our Apologies if you have received multiple copies.

Wei Ye and Cormac J. Sreenan
SenSys'06 Publicity Co-Chairs
------------

ACM SenSys 2006: Call for Posters and Demos

The 4th ACM Conference on Embedded Networked Sensor Systems
Sponsored by ACM SIGCOMM, SIGMOBILE, SIGARCH, SIGOPS, SIGMETRICS and  
SIGBED; with support from NSF.
Boulder, Colorado, USA
November 1-3, 2006
http://sensys.acm.org/2006/

CALL FOR POSTERS

The poster session will provide a forum for researchers to showcase  
their work and obtain feedback on ongoing research from knowledgeable  
conference attendees. Areas of interest are the same as those listed  
in the technical call for papers. While the poster need not describe  
completed work, it should report on research for which at least  
preliminary results are available. We especially encourage  
submissions by students (that is, for which a student is the first  
author on the poster).

POSTER SUBMISSION INSTRUCTIONS

Poster proposals must be submitted as a single PDF file with no more  
than 3 pages. The first two pages should contain an abstract  
describing the research content of the poster, along with title,  
authors, institutional affiliations and contact information. The  
third page should contain a thumbnail draft of the poster's contents.  
Please submit your poster proposal as a PDF e-mail attachment to

sensys06-poster-chairs@isi.edu

with the subject line reading "Sensys Poster Submission" before the  
deadline. Any questions for the Poster Co-chairs Henry Tirri (Nokia),  
Robert Szewczyk (Moteiv) may also be directed to this address.

IMPORTANT DATES

Three-page poster proposal: 11:59pm (EST), July 24, 2006
Notification of acceptance: August 7, 2006
Camera-ready abstract: August 22, 2006
Conference dates: November 1-3, 2006

BASIC INFORMATION ABOUT POSTERS

Two-page poster abstracts will appear in the conference proceedings.
Authors of accepted poster proposals will have a chance to present
the poster to interested attendees during a special poster session at
SenSys. Well-crafted posters will tell the story well by themselves,
but authors of posters are expected to be available to describe and
discuss the work in the poster during the session.

The poster dimensions are 30" by 40", with poster contents mounted on
rectangular poster board that we will provide. You may choose a
layout consisting of individual sheets of paper, or a monolithic
large piece of poster paper (which can be printed at document
companies).

Henry Tirri, Nokia
Robert Szewczyk, Moteiv
SenSys 2006 Poster Chairs

CALL FOR DEMOS

Demonstrations showing innovative research and applications are  
solicited. SenSys'06 is very interested in demonstrations of technology,
platforms, and applications of wireless sensor networks. Two-page
abstracts of accepted demos will be published in the SenSys conference
proceedings. Submissions from both industries and universities are
encouraged. Large-scale, outdoor demos can also be accommodated at the
conference facility. For the first time, SenSys 2006 will present a best
demo award.

DEMO SUBMISSION INSTRUCTIONS

Please send a two-page description of your demo to 

sensys06-demo-chairs@isi.edu

in PDF format by the dates listed below. An additional one page appendix
can be included in the initial submission but will be removed in
published proceedings. Be as specific as possible in describing what you
will show.

IMPORTANT DATES

Two-page demo descriptions: 11:59pm (EST), July 24, 2006
Notification of acceptance: August 7, 2006
Camera-ready abstract: August 22, 2006
Conference dates: November 1-3, 2006

Chieh-Yih Wan, Intel Labs
Jie Liu, Microsoft Research
SenSys 2006 Demo Chairs



_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Tue May 09 05:39:32 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FdOfp-0005Sn-H9; Tue, 09 May 2006 05:38:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FdOfp-0005Si-1M
	for mip6@ietf.org; Tue, 09 May 2006 05:38:33 -0400
Received: from smtp16.clb.oleane.net ([213.56.31.159])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FdOfm-0005rH-KK
	for mip6@ietf.org; Tue, 09 May 2006 05:38:33 -0400
Received: from Pavillonquatre ([194.3.133.88]) 
	by smtp16.clb.oleane.net with ESMTP id k499cPR1024998
	for <mip6@ietf.org>; Tue, 9 May 2006 11:38:25 +0200
Message-Id: <200605090938.k499cPR1024998@smtp16.clb.oleane.net>
From: "Chantal Ladouce" <chantal.ladouce@upperside.fr>
To: <mip6@ietf.org>
Date: Tue, 9 May 2006 11:37:07 +0200
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
Thread-Index: AcZzTCL+fGGiRKvHS2ia44f1QpxU3A==
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 225414c974e0d6437992164e91287a51
Subject: [Mip6] Wireless/WiFi Convergence Conference 2006 - Paris - France
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1088524965=="
Errors-To: mip6-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1088524965==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_027A_01C6735C.E90AC360"

This is a multi-part message in MIME format.

------=_NextPart_000_027A_01C6735C.E90AC360
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

UMA how? IMS when?

Don't miss the 2006 Wireless/WiFi Convergence Conference to be held next
week in Paris (on May 16 to May 19). Distinguished experts and key players
in the convergence field will address technical issues. 

Registration is still open.

Get all details at:

 

 
<http://www.upperside.fr/wirelessconvergence2006/wwconvergence2006intro.htm>
http://www.upperside.fr/wirelessconvergence2006/wwconvergence2006intro.htm

 

 


------=_NextPart_000_027A_01C6735C.E90AC360
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"place" downloadurl=3D"http://www.5iantlavalamp.com/"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"City" =
downloadurl=3D"http://www.5iamas-microsoft-com:office:smarttags"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
	{font-family:"\@MS Mincho";
	panose-1:0 0 0 0 0 0 0 0 0 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
@page Section1
	{size:595.3pt 841.9pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DFR link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><em><b><i><font size=3D1 face=3DArial><span =
lang=3DEN-GB
style=3D'font-size:9.0pt;font-family:Arial;font-weight:bold'>UMA how? =
IMS when?</span></font></i></b></em><font
size=3D1 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:9.0pt;font-family:Arial'><o:p></o:p></span></font></p>=


<p class=3DMsoNormal><font size=3D1 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
9.0pt;font-family:Arial'>Don't miss the <strong><b><font =
face=3DArial><span
style=3D'font-family:Arial'>2006 Wireless/WiFi Convergence Conference =
</span></font></b></strong>to
be held next week in <st1:place w:st=3D"on"><st1:City =
w:st=3D"on">Paris</st1:City></st1:place>
(on May 16 to May 19<strong><b><font face=3DArial><span =
style=3D'font-family:Arial'>)</span></font></b></strong>.
Distinguished experts and key players in the convergence field will =
address
technical issues. <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
9.0pt;font-family:Arial'>Registration is still =
open.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
9.0pt;font-family:Arial'>Get all details =
at:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
9.0pt;font-family:Arial'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 face=3DArial><span =
style=3D'font-size:9.0pt;
font-family:Arial'><a
href=3D"http://www.upperside.fr/wirelessconvergence2006/wwconvergence2006=
intro.htm"
title=3D"http://www.upperside.fr/wirelessconvergence2006/wwconvergence200=
6intro.htm"><span
lang=3DEN-GB>http://www.upperside.fr/wirelessconvergence2006/wwconvergenc=
e2006intro.htm</span></a></span></font><font
size=3D1 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:9.0pt;font-family:Arial'><o:p></o:p></span></font></p>=


<p class=3DMsoNormal><font size=3D1 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
9.0pt;font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
9.0pt;font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

------=_NextPart_000_027A_01C6735C.E90AC360--



--===============1088524965==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6

--===============1088524965==--





From mip6-bounces@ietf.org Tue May 09 14:45:12 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FdXBo-0008Kv-Ru; Tue, 09 May 2006 14:44:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FdXBn-0008Jb-8i
	for mip6@ietf.org; Tue, 09 May 2006 14:44:07 -0400
Received: from mail1.azairenet.com ([66.92.223.4] helo=bart.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FdXBl-00075Z-Vl
	for mip6@ietf.org; Tue, 09 May 2006 14:44:07 -0400
Received: from [10.1.201.13] ([10.1.201.13]) by bart.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Tue, 9 May 2006 11:44:04 -0700
Message-ID: <4460E2F4.1070209@azairenet.com>
Date: Tue, 09 May 2006 11:44:04 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.2 (Windows/20060308)
MIME-Version: 1.0
To: mip6@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 09 May 2006 18:44:04.0088 (UTC)
	FILETIME=[8B985F80:01C67398]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Subject: [Mip6] INTERNAL_IP6_SUBNET attribute
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

hello all,

currently, draft-ietf-mip6-ikev2-ipsec-06 says

>    The
>    mobile node MAY also include the INTERNAL_IP6_SUBNET attribute if it
>    wants to obtain information about the IPv6 prefixes on the home link.

and draft-eronen-ipsec-ikev2-clarifications-09.txt
(which is with the IESG right now) says

>    It is less clear what the attributes mean in CFG_REQUESTs, and
>    whether other lengths than zero make sense in this situation (but for
>    INTERNAL_IP6_SUBNET, zero length is not allowed at all!).  Currently
>    this document recommends that implementations should not include
>    INTERNAL_IP4_SUBNET or INTERNAL_IP6_SUBNET attributes in
>    CFG_REQUESTs.

draft-eronen also has more text clarifying the use of
INTERNAL_IP6_SUBNET attribute. I don't think we can use
it to obtain the home prefix. so I propose removing the
text about using the INTERNAL_IP6_SUBNET from
draft-ietf-mip6-ikev2-ipsec-06.

to obtain the home prefix, there are two options.

1. use the MIP6_HOME_PREFIX attribute during IKEv2
negotiation. this attribute is defined in
draft-ietf-mip6-bootstrapping-split-02.txt

2. run Mobile Prefix Discovery with the home agent later.

Vijay

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Tue May 09 16:31:27 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FdYrR-0003Ci-I3; Tue, 09 May 2006 16:31:13 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FdYrP-0003CT-Jw
	for mip6@ietf.org; Tue, 09 May 2006 16:31:11 -0400
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FdYrO-0004Ny-73
	for mip6@ietf.org; Tue, 09 May 2006 16:31:11 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by laposte.rennes.enst-bretagne.fr (8.13.4/8.13.4/2004.10.03) with
	ESMTP id k49KV3Rs005764; Tue, 9 May 2006 22:31:03 +0200
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[192.44.77.29])
	by laposte.rennes.enst-bretagne.fr (8.13.4/8.13.4/2004.09.01) with
	ESMTP id k49KV2x4005760; Tue, 9 May 2006 22:31:02 +0200
Received: from givry.rennes.enst-bretagne.fr
	(localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.13.1/8.13.1) with ESMTP id
	k49KV28f069167; Tue, 9 May 2006 22:31:02 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200605092031.k49KV28f069167@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@point6.net>
To: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
Subject: Re: [Mip6] INTERNAL_IP6_SUBNET attribute 
In-reply-to: Your message of Tue, 09 May 2006 11:44:04 PDT.
	<4460E2F4.1070209@azairenet.com> 
Date: Tue, 09 May 2006 22:31:02 +0200
X-Virus-Scanned: amavisd-new at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   1. use the MIP6_HOME_PREFIX attribute during IKEv2
   ...
   2. run Mobile Prefix Discovery with the home agent later.
   
=> I agree the whole thing is not clear and should be handled by
the bootstrapping documents... So we have two choices:
 - simply remove the INTERNAL_IP6_SUBNET statement
 - replace it by a reference to a bootstrapping document.
I am in favor of the first option because I'd like to avoid to introduce
a reference to an I-D but perhaps I am a bit too conservative here.

Thanks

Francis.Dupont@point6.net

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Tue May 09 18:14:07 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FdaS6-0006Mo-KK; Tue, 09 May 2006 18:13:10 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FdaS5-0006Me-93
	for mip6@ietf.org; Tue, 09 May 2006 18:13:09 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FdZ7f-0005RY-RL
	for mip6@ietf.org; Tue, 09 May 2006 16:47:59 -0400
Received: from mail1.azairenet.com ([66.92.223.4] helo=bart.corp.azairenet.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1FdYu7-0003jl-Tr
	for mip6@ietf.org; Tue, 09 May 2006 16:34:01 -0400
Received: from [10.1.201.13] ([10.1.201.13]) by bart.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Tue, 9 May 2006 13:33:57 -0700
Message-ID: <4460FCB6.8060707@azairenet.com>
Date: Tue, 09 May 2006 13:33:58 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.2 (Windows/20060308)
MIME-Version: 1.0
To: Francis Dupont <Francis.Dupont@point6.net>
Subject: Re: [Mip6] INTERNAL_IP6_SUBNET attribute
References: <200605092031.k49KV28f069167@givry.rennes.enst-bretagne.fr>
In-Reply-To: <200605092031.k49KV28f069167@givry.rennes.enst-bretagne.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 09 May 2006 20:33:57.0894 (UTC)
	FILETIME=[E5CF5260:01C673A7]
X-Spam-Score: -1.5 (-)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Francis Dupont wrote:
>  In your previous mail you wrote:
> 
>    1. use the MIP6_HOME_PREFIX attribute during IKEv2
>    ...
>    2. run Mobile Prefix Discovery with the home agent later.
>    
> => I agree the whole thing is not clear and should be handled by
> the bootstrapping documents... So we have two choices:
>  - simply remove the INTERNAL_IP6_SUBNET statement
>  - replace it by a reference to a bootstrapping document.
> I am in favor of the first option

me too.

Vijay

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Wed May 10 16:01:55 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FdusS-0002Ji-Ke; Wed, 10 May 2006 16:01:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FdusR-0002Ey-Mj
	for mip6@ietf.org; Wed, 10 May 2006 16:01:43 -0400
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FdusQ-0006nI-5j
	for mip6@ietf.org; Wed, 10 May 2006 16:01:43 -0400
Received: from p130.piuha.net (localhost [127.0.0.1])
	by p130.piuha.net (Postfix) with ESMTP id 716E6898DA;
	Wed, 10 May 2006 23:01:41 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id 22F48898D9;
	Wed, 10 May 2006 23:01:41 +0300 (EEST)
Message-ID: <446246E3.6070107@kolumbus.fi>
Date: Wed, 10 May 2006 23:02:43 +0300
From: Jari Arkko <jari.arkko@kolumbus.fi>
User-Agent: Mozilla Thunderbird 1.0.8 (X11/20060502)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Gerardo Giaretta <gerardo.giaretta@gmail.com>
Subject: Re: [Mip6] FW: COMMENT: draft-ietf-mip6-bootstrap-ps
References: <eaa74a7e0604301331m65c11d8ax7eae32a2023577a5@mail.gmail.com>
In-Reply-To: <eaa74a7e0604301331m65c11d8ax7eae32a2023577a5@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Virus-Scanned: ClamAV using ClamSMTP
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43
Cc: mip6@ietf.org, Basavaraj Patil <Basavaraj.Patil@nokia.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Gerardo Giaretta wrote:

> Sorry for late comments on this. All editorial changes proposed have
> been fixed in the new version (will be available very soon). Below the
> answers to some detailed comments:
>
> - s3, 1st bullet: If boostrapping creates an IKE pre-shared secret, isn=
't
> that enough to be able to create the SA between HA and MN?  Do you need
> both? Or does it depend on whether RFC4285 is being used or not?
>
> IKE pre-shared key is enough if IPsec is used between MN and HA. If
> rfc4285 is used, some dedicated keys may be needed. This is still not
> covered by current RFCs and I-Ds and let open in this document.

Note: as a part of the other thread you are removing the 4285
reference, which removes the issue, I think.

> - s5.2.1: Is the phrase 'traditional AAA infrastructure' sufficiently
> well-understood?  I think it may need a few hints as what is traditiona=
l
> will change over time!
>
> I would rephrase as the following:
> " Where an AAA scheme based on RADIUS or Diameter protocols is used,
> the home agent is not able to leverage authentication and
> authorization information established between the mobile node, the
> foreign AAA server, and the home AAA server."

Ok.

> - s5.2.2: I would have thought this section belong with 5.1 (addressing=
)
> rather then 5.2 (security infrastructure).
>
> Right, moved to 5.1

Looks good to me.

--Jari

> Thx,
> --Gerardo
>
>> -----Original Message-----
>> From: Basavaraj Patil [mailto:basavaraj.patil@nokia.com]
>> Sent: mercoled=EC 1 marzo 2006 14.56
>> To: mip6@ietf.org
>> Subject: [Mip6] FW: COMMENT: draft-ietf-mip6-bootstrap-ps
>>
>>
>> Gen-ART review:
>>
>> ------ Forwarded Message
>> > From: ext Brian Carpenter <brc@zurich.ibm.com>
>> > Date: Wed, 01 Mar 2006 05:48:24 -0500
>> > To: <iesg@ietf.org>
>> > Cc: <basavaraj.patil@nokia.com>, <gdommety@cisco.com>
>> > Subject: COMMENT: draft-ietf-mip6-bootstrap-ps
>> >
>> > Comment:
>> > From Gen-ART review by Elwyn Davies:
>> >
>> > ..There are a small number of very minor issues and
>> questions plus a fair
>> > number of editorial nits...
>> >
>> > The detailed review with these points is posted at
>> >
>> http://www.alvestrand.no/ietf/gen/reviews/draft-ietf-mip6-boot
>
> strap-ps-04-davi
>
>> > es.txt
>> >
>>
>> ------ End of Forwarded Message
>>
>>
>> _______________________________________________
>> Mip6 mailing list
>> Mip6@ietf.org
>> https://www1.ietf.org/mailman/listinfo/mip6
>>
>
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
>


_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Wed May 10 16:02:00 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FdusD-0002CY-9d; Wed, 10 May 2006 16:01:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FdusC-0002CN-0p
	for mip6@ietf.org; Wed, 10 May 2006 16:01:28 -0400
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FdusB-0006mJ-7q
	for mip6@ietf.org; Wed, 10 May 2006 16:01:27 -0400
Received: from p130.piuha.net (localhost [127.0.0.1])
	by p130.piuha.net (Postfix) with ESMTP id DF7DA898DA;
	Wed, 10 May 2006 23:01:25 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id 8E973898D9;
	Wed, 10 May 2006 23:01:25 +0300 (EEST)
Message-ID: <446246D3.3010800@kolumbus.fi>
Date: Wed, 10 May 2006 23:02:27 +0300
From: Jari Arkko <jari.arkko@kolumbus.fi>
User-Agent: Mozilla Thunderbird 1.0.8 (X11/20060502)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Gerardo Giaretta <gerardo.giaretta@gmail.com>
Subject: Re: [Mip6] FW: DISCUSS and COMMENT: draft-ietf-mip6-bootstrap-ps
References: <eaa74a7e0604301330y4bc37bcamd953a713cf50c95a@mail.gmail.com>	<44568464.1090807@azairenet.com>
	<tslpsixe68p.fsf@cz.mit.edu>	<eaa74a7e0605020117n31ff475bie7dc2541dd8e197@mail.gmail.com>	<tslu088d43x.fsf@cz.mit.edu>
	<eaa74a7e0605020857s27f685b6l8948ab3a63a5b325@mail.gmail.com>
In-Reply-To: <eaa74a7e0605020857s27f685b6l8948ab3a63a5b325@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248
Cc: mip6@ietf.org, Sam Hartman <hartmans-ietf@mit.edu>,
	Basavaraj Patil <Basavaraj.Patil@nokia.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Gerardo Giaretta wrote:

> On 5/2/06, Sam Hartman <hartmans-ietf@mit.edu> wrote:
>
>> >>>>> "Gerardo" == Gerardo Giaretta <gerardo.giaretta@gmail.com> writes:
>>
>>
>>     Gerardo> Hi Sam,
>>
>>     Gerardo> thanks for the comments and sorry for very late answers.
>>
>>     Gerardo> Concerning the EAP issue, I think that both solutions
>>     Gerardo> that are under definition in the WG does not follow the
>>     Gerardo> directions you mentioned.  After your and others'
>>     Gerardo> comments (also during ICOS BOF and HOAKEY BOF) the WG has
>>     Gerardo> been producing solutions where network access
>>     Gerardo> authentication and mobility service authentication are
>>     Gerardo> considered fully separated. It seems to me that this
>>     Gerardo> problem statement does not suggest this kind of
>>     Gerardo> solutions. Please let me know if you think some
>>     Gerardo> clarifying text needs to be added to this problem
>>     Gerardo> statement.
>>
>> Take a look at the last phrase in the following paragraph of 7.2:
>>
>>     In this scenario, the ASA and MSA are the same entity.  The MN has
>>        security credentials for access to the network and these
>> credentials
>>           can be used to bootstrap MIPv6.  This bootstrapping can be
>> done
>>              during the same phase as access
>> authentication/authorization or at a
>>                 later time (probably based on some state created
>> during access
>>                    authentication/authorization).
>>
>> It sounds like the two are bound.
>>
>
> I would delete the last sentence. I would like to keep the following:

Ok.

>
>>     In this scenario, the ASA and MSA are the same entity.  The MN has
>>        security credentials for access to the network and these
>> credentials
>>           can be used to bootstrap MIPv6.
>
>
> since it is a clear deployment scenario. Sounds good?

Ok. Maybe "... can also be used ... ".

>
>>     Gerardo> Concerning rfc4285, the WG is currently not working on a
>>     Gerardo> solutions for bootstrapping rfc4285 SAs. I'm OK with
>>     Gerardo> removing all references to rfc4285. Is this your
>>     Gerardo> suggestion?
>>
>> I'd certainly be happiest with that.
>>
>> I do think that  the mention of RFC 4285  in the following bullet
>> should be removed:
>>
>>        *  IPsec SA between MN and HA, IKE pre-shared secret between MN
>>            and HA, or shared secret/security association for
>>                 authentication protocol [RFC4285]
>>
>> I don't have a problem with the reference to 4285 in section 1.
>>
>
> I'm OK with that. What do others think?

Ok for me.

--Jari



_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Mon May 15 10:17:20 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FfdsF-0001Gp-Ap; Mon, 15 May 2006 10:16:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FfXS1-0006qB-Sz
	for mip6@ietf.org; Mon, 15 May 2006 03:25:09 -0400
Received: from mailb.microsoft.com ([131.107.1.8] helo=mail3.microsoft.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FfXRx-0002KU-Jr
	for mip6@ietf.org; Mon, 15 May 2006 03:25:09 -0400
Received: from mailout6.microsoft.com ([157.54.69.150]) by mail3.microsoft.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 15 May 2006 00:25:04 -0700
Received: from RED-MSG-40.redmond.corp.microsoft.com ([157.54.61.19]) by
	mailout6.microsoft.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 15 May 2006 00:25:04 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 15 May 2006 00:25:04 -0700
Message-ID: <33C26512D973DF4DB227D5C3E9E7F5C5F18C2D@RED-MSG-40.redmond.corp.microsoft.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Reminder: May 15th is the MobiSys 2006 Early Registration
	Deadline
Thread-Index: AcZ38K8hB+Yx2AppQoucI6WK6v9M9Q==
From: "Alec Wolman" <alecw@microsoft.com>
To: <mip6@ietf.org>
X-OriginalArrivalTime: 15 May 2006 07:25:04.0812 (UTC)
	FILETIME=[AF92AEC0:01C677F0]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
X-Mailman-Approved-At: Mon, 15 May 2006 10:16:37 -0400
Subject: [Mip6] Reminder: May 15th is the MobiSys 2006 Early Registration
	Deadline
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org


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

Call for participation

MobiSys 2006 - The Fourth International Conference on Mobile Systems,
Applications, and Services

Uppsala, Sweden, June 19-22, 2006.

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

See the MobiSys website -
http://www.sigmobile.org/mobisys/2006/index.html for details on the
program and registration information.

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Tue May 16 18:07:58 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fg7h8-0002XO-TE; Tue, 16 May 2006 18:07:10 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fg7h5-0002WE-On; Tue, 16 May 2006 18:07:07 -0400
Received: from nit.isi.edu ([128.9.160.116])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Fg7h4-00024h-D3; Tue, 16 May 2006 18:07:07 -0400
Received: from nit.isi.edu (loopback [127.0.0.1])
	by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id k4GM75OB004288; 
	Tue, 16 May 2006 15:07:05 -0700
Received: (from apache@localhost)
	by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id k4GM759h004287;
	Tue, 16 May 2006 15:07:05 -0700
Date: Tue, 16 May 2006 15:07:05 -0700
Message-Id: <200605162207.k4GM759h004287@nit.isi.edu>
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
X-Spam-Score: -14.8 (--------------)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36
Cc: mip6@ietf.org, rfc-editor@rfc-editor.org
Subject: [Mip6] RFC 4487 on Mobile IPv6 and Firewalls: Problem Statement
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org


A new Request for Comments is now available in online RFC libraries.

        
        RFC 4487

        Title:      Mobile IPv6 and Firewalls: Problem 
                    Statement 
        Author:     F. Le, S. Faccin,
                    B. Patil, H. Tschofenig
        Status:     Informational
        Date:       May 2006
        Mailbox:    franckle@cmu.edu, 
                    sfaccinstd@gmail.com, 
                    Basavaraj.Patil@nokia.com,  
                    Hannes.Tschofenig@siemens.com
        Pages:      16
        Characters: 32022
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mip6-firewalls-04.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4487.txt

This document captures the issues that may arise in the deployment of
IPv6 networks when they support Mobile IPv6 and firewalls.  The
issues are not only applicable to firewalls protecting enterprise
networks, but are also applicable in 3G mobile networks such as
General Packet Radio Service / Universal Mobile Telecommunications
System (GPRS/UMTS) and CDMA2000 networks.

The goal of this document is to highlight the issues with firewalls
and Mobile IPv6 and act as an enabler for further discussion.  Issues
identified here can be solved by developing appropriate solutions.  This 
memo provides information for the Internet community.

This document is a product of the Mobility for IPv6
Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community. 
It does not specify an Internet standard of any kind. Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...



_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Tue May 16 20:19:43 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fg9ka-00027m-IV; Tue, 16 May 2006 20:18:52 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fg9kZ-00027c-Rj
	for mip6@ietf.org; Tue, 16 May 2006 20:18:51 -0400
Received: from mgw-ext14.nokia.com ([131.228.20.173])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fg9kZ-0001zJ-D4
	for mip6@ietf.org; Tue, 16 May 2006 20:18:51 -0400
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
	by mgw-ext14.nokia.com (Switch-3.1.8/Switch-3.1.7) with ESMTP id
	k4H0Ioqn006077 for <mip6@ietf.org>; Wed, 17 May 2006 03:18:50 +0300
Received: from daebh101.NOE.Nokia.com ([10.241.35.111]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 17 May 2006 03:18:12 +0300
Received: from sdebe101.NOE.Nokia.com ([172.19.222.105]) by
	daebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 16 May 2006 19:18:11 -0500
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 16 May 2006 17:18:08 -0700
Message-ID: <84CA64E50179964E8EF67403019ABB940204D5C2@sdebe101.NOE.Nokia.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: RFC4487 issues
Thread-Index: AcZ5R1+/gRfw5gJRTd6OZ/jMgvEkaA==
From: <Gabor.Bajko@nokia.com>
To: <mip6@ietf.org>
X-OriginalArrivalTime: 17 May 2006 00:18:11.0018 (UTC)
	FILETIME=[616362A0:01C67947]
X-Spam-Score: 0.2 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Subject: [Mip6] RFC4487 issues
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0383306257=="
Errors-To: mip6-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0383306257==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C67947.60679C5A"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C67947.60679C5A
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Folks,

We have written up a draft which addresses one of the RFC4487 identified
problems
http://www.ietf.org/internet-drafts/draft-bajko-mip6-rrtfw-00.txt

The draft proposes an extension to the MIPv6 RRT to make it possible to
perform an RRT even in the case when CN is behind firewall. Thus, RO
could be used even in those cases.

Comments are welcome.

Gabor


------_=_NextPart_001_01C67947.60679C5A
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7650.21">
<TITLE>RFC4487 issues</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

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

<P><FONT SIZE=3D2 FACE=3D"Arial">We have written up a draft which =
addresses one of the RFC4487 identified problems </FONT><A =
HREF=3D"http://www.ietf.org/internet-drafts/draft-bajko-mip6-rrtfw-00.txt=
"><U><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Arial">http://www.ietf.org/internet-drafts/draft-bajko-mip6-rrtfw=
-00.txt</FONT></U></A></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">The draft proposes an extension to the =
MIPv6 RRT to make it possible to perform an RRT even in the case when CN =
is behind firewall. Thus, RO could be used even in those =
cases.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Comments are welcome.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Gabor</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C67947.60679C5A--


--===============0383306257==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6

--===============0383306257==--




From mip6-bounces@ietf.org Thu May 18 10:28:31 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FgjSl-00088A-1s; Thu, 18 May 2006 10:26:51 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FgjSk-000885-3f
	for mip6@ietf.org; Thu, 18 May 2006 10:26:50 -0400
Received: from zrtps0kp.nortel.com ([47.140.192.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FgjSj-0004yJ-Qj
	for mip6@ietf.org; Thu, 18 May 2006 10:26:50 -0400
Received: from zrc2hxm2.corp.nortel.com (zrc2hxm2.corp.nortel.com
	[47.103.123.73])
	by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	k4IEQjR06315; Thu, 18 May 2006 10:26:45 -0400 (EDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 18 May 2006 09:26:44 -0500
Message-ID: <6FC4416DDE56C44DA0AEE67BC7CA43710E7FD7AE@zrc2hxm2.corp.nortel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: MIPv6: Using the last Accepted Sequence Number in BA
Thread-Index: AcZ6hxXS0AZCoNWpSGqLC1sx6fPZrw==
From: "Ahmad Muhanna" <amuhanna@nortel.com>
To: <mip6@ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Cc: Gopal Dommety <gdommety@cisco.com>,
	"Charles E. Perkins" <charliep@iprg.nokia.com>,
	jari.arkko@ericsson.com, dbj@cs.rice.edu,
	Basavaraj Patil <basavaraj.patil@nokia.com>,
	Mohamed Khalil <mkhalil@nortel.com>
Subject: [Mip6] MIPv6: Using the last Accepted Sequence Number in BA
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2069695176=="
Errors-To: mip6-bounces@ietf.org

This is a multi-part message in MIME format.

--===============2069695176==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C67A87.16C2EEFD"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C67A87.16C2EEFD
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable


Hi all,

In response to a Binding Update which contains an out of range sequence
number, as per sections 9.5.1 and 11.7.1, the CN or HA is allowed to
send a Binding Acknowledgement with a status of 135 after inserting the
last accepted sequence number received in the last valid Binding Update
in the sequence number field (Different from the sequence number
received in the outstanding BU)

According to MN processing of the Binding Acknowledgement as specified
under section 11.7.3., the MN will silently discard the received BA
rather than picking the last accepted sequence number and then generate
a new sequence number.=20

I think the intention was to allow the HA or CN to communicate back to
the MN the last accepted sequence number, however, we are breaking the
protocol by using this mechanism.

Could you please comment on this and let me know if I am on the right
track.
Thanks.

Regards,
Ahmad


------_=_NextPart_001_01C67A87.16C2EEFD
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7233.28">
<TITLE>MIPv6: Using the last Accepted Sequence Number in BA</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->
<BR>

<P><FONT SIZE=3D2 FACE=3D"Courier New">Hi all,</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">In response to a Binding Update =
which contains an out of range sequence number, as per sections 9.5.1 =
and 11.7.1, the CN or HA is allowed to send a Binding Acknowledgement =
with a status of 135 after inserting the last accepted sequence number =
received in the last valid Binding Update in the sequence number field =
(Different from the sequence number received in the outstanding =
BU)</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">According to MN processing of the =
Binding Acknowledgement as specified under section 11.7.3., the MN will =
silently discard the received BA rather than picking the last accepted =
sequence number and then generate a new sequence number. </FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">I think the intention was to =
allow the HA or CN to communicate back to the MN the last accepted =
sequence number, however, we are breaking the protocol by using this =
mechanism.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">Could you please comment on this =
and let me know if I am on the right track.</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Courier New">Thanks.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">Regards,</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Courier New">Ahmad</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C67A87.16C2EEFD--


--===============2069695176==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6

--===============2069695176==--




From mip6-bounces@ietf.org Thu May 18 17:15:25 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fgpor-0007uq-4I; Thu, 18 May 2006 17:14:05 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fgpoq-0007uf-AZ
	for mip6@ietf.org; Thu, 18 May 2006 17:14:04 -0400
Received: from mail1.azairenet.com ([66.92.223.4] helo=bart.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fgpop-0006zg-1B
	for mip6@ietf.org; Thu, 18 May 2006 17:14:04 -0400
Received: from [10.1.201.8] ([10.1.201.8]) by bart.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Thu, 18 May 2006 14:14:00 -0700
Message-ID: <446CE398.2060804@azairenet.com>
Date: Thu, 18 May 2006 14:14:00 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.2 (Windows/20060308)
MIME-Version: 1.0
To: Ahmad Muhanna <amuhanna@nortel.com>
Subject: Re: [Mip6] MIPv6: Using the last Accepted Sequence Number in BA
References: <6FC4416DDE56C44DA0AEE67BC7CA43710E7FD7AE@zrc2hxm2.corp.nortel.com>
In-Reply-To: <6FC4416DDE56C44DA0AEE67BC7CA43710E7FD7AE@zrc2hxm2.corp.nortel.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 18 May 2006 21:14:00.0445 (UTC)
	FILETIME=[FB8F42D0:01C67ABF]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Cc: Gopal Dommety <gdommety@cisco.com>,
	"Charles E. Perkins" <charliep@iprg.nokia.com>,
	jari.arkko@ericsson.com, dbj@cs.rice.edu,
	Basavaraj Patil <basavaraj.patil@nokia.com>, mip6@ietf.org,
	Mohamed Khalil <mkhalil@nortel.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Ahmad Muhanna wrote:
> 
> Hi all,
> 
> In response to a Binding Update which contains an out of range sequence 
> number, as per sections 9.5.1 and 11.7.1, the CN or HA is allowed to 
> send a Binding Acknowledgement with a status of 135 after inserting the 
> last accepted sequence number received in the last valid Binding Update 
> in the sequence number field (Different from the sequence number 
> received in the outstanding BU)
> 
> According to MN processing of the Binding Acknowledgement as specified 
> under section 11.7.3., the MN will silently discard the received BA 
> rather than picking the last accepted sequence number and then generate 
> a new sequence number.
> 
> I think the intention was to allow the HA or CN to communicate back to 
> the MN the last accepted sequence number, however, we are breaking the 
> protocol by using this mechanism.
> 
> Could you please comment on this and let me know if I am on the right 
> track.

when the mobile node receives a binding ack with
status 135, it should pick a sequence number
greater than what was returned in the binding ack
and re-try with another binding update. it should
not ignore the sequence number field in the
binding ack.

the text in section 11.7.3 needs to be fixed when
RFC 3775 is revised.

thanks for catching this.

Vijay

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Thu May 18 17:38:17 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FgqBD-0000Yf-Kh; Thu, 18 May 2006 17:37:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FgqBC-0000YY-Dj
	for mip6@ietf.org; Thu, 18 May 2006 17:37:10 -0400
Received: from mail1.azairenet.com ([66.92.223.4] helo=bart.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FgqBB-00006b-VV
	for mip6@ietf.org; Thu, 18 May 2006 17:37:10 -0400
Received: from [10.1.201.8] ([10.1.201.8]) by bart.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Thu, 18 May 2006 14:37:06 -0700
Message-ID: <446CE902.5040908@azairenet.com>
Date: Thu, 18 May 2006 14:37:06 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.2 (Windows/20060308)
MIME-Version: 1.0
To: Mohamed Khalil <mkhalil@nortel.com>
Subject: Re: [Mip6] MIPv6: Using the last Accepted Sequence Number in BA
References: <62B9B0847CC47543B6B3B5E26BD268E60B5F62AF@zrc2hxm2.corp.nortel.com>
In-Reply-To: <62B9B0847CC47543B6B3B5E26BD268E60B5F62AF@zrc2hxm2.corp.nortel.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 18 May 2006 21:37:06.0630 (UTC)
	FILETIME=[35CA4E60:01C67AC3]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d
Cc: Gopal Dommety <gdommety@cisco.com>,
	"Charles E. Perkins" <charliep@iprg.nokia.com>,
	jari.arkko@ericsson.com, dbj@cs.rice.edu,
	Basavaraj Patil <basavaraj.patil@nokia.com>, mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Mohamed Khalil wrote:
> Hi Vijay,
> 
> A cleaner solution is to put the sequence number as it is in the BA, and
> introduce a new option which have the proposed sequence number to be
> used. 

perhaps.

> trial and error approach is not the right way to resolve the
> issue.

the status 135 combined with the sequence number in the
binding ack *tells* the mobile node what sequence number
it used last. this works.

this was added to address the case where the mobile node
reboots suddenly and forgets about its binding cache
entries at the HA or the CN when it comes up again.

Vijay

> 
> -----Original Message-----
> From: Vijay Devarapalli [mailto:vijay.devarapalli@AzaireNet.com] 
> Sent: Thursday, May 18, 2006 4:14 PM
> To: Muhanna, Ahmad [RICH2:2Q30:EXCH]
> Cc: mip6@ietf.org; Gopal Dommety; Charles E. Perkins;
> jari.arkko@ericsson.com; dbj@cs.rice.edu; Basavaraj Patil; Khalil,
> Mohamed [RICH2:2S20:EXCH]
> Subject: Re: [Mip6] MIPv6: Using the last Accepted Sequence Number in BA
> 
> 
> Ahmad Muhanna wrote:
>> Hi all,
>>
>> In response to a Binding Update which contains an out of range 
>> sequence
>> number, as per sections 9.5.1 and 11.7.1, the CN or HA is allowed to 
>> send a Binding Acknowledgement with a status of 135 after inserting
> the 
>> last accepted sequence number received in the last valid Binding
> Update 
>> in the sequence number field (Different from the sequence number 
>> received in the outstanding BU)
>>
>> According to MN processing of the Binding Acknowledgement as specified
>> under section 11.7.3., the MN will silently discard the received BA 
>> rather than picking the last accepted sequence number and then
> generate 
>> a new sequence number.
>>
>> I think the intention was to allow the HA or CN to communicate back to
>> the MN the last accepted sequence number, however, we are breaking the
> 
>> protocol by using this mechanism.
>>
>> Could you please comment on this and let me know if I am on the right
>> track.
> 
> when the mobile node receives a binding ack with
> status 135, it should pick a sequence number
> greater than what was returned in the binding ack
> and re-try with another binding update. it should
> not ignore the sequence number field in the
> binding ack.
> 
> the text in section 11.7.3 needs to be fixed when
> RFC 3775 is revised.
> 
> thanks for catching this.
> 
> Vijay
> 


_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Fri May 19 04:24:56 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fh0GY-0000dS-FI; Fri, 19 May 2006 04:23:22 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fh0GX-0000dN-Oi
	for mip6@ietf.org; Fri, 19 May 2006 04:23:21 -0400
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fh0GX-0004Wj-G4
	for mip6@ietf.org; Fri, 19 May 2006 04:23:21 -0400
Received: from p130.piuha.net (localhost [127.0.0.1])
	by p130.piuha.net (Postfix) with ESMTP id 18389898ED;
	Fri, 19 May 2006 11:23:16 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id C3663898EB;
	Fri, 19 May 2006 11:23:15 +0300 (EEST)
Message-ID: <446D80AB.60205@kolumbus.fi>
Date: Fri, 19 May 2006 11:24:11 +0300
From: Jari Arkko <jari.arkko@kolumbus.fi>
User-Agent: Mozilla Thunderbird 1.0.8 (X11/20060502)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Vijay Devarapalli <vijay.devarapalli@azairenet.com>, 
	Mohamed Khalil <mkhalil@nortel.com>
Subject: Re: [Mip6] MIPv6: Using the last Accepted Sequence Number in BA
References: <62B9B0847CC47543B6B3B5E26BD268E60B5F62AF@zrc2hxm2.corp.nortel.com>
	<446CE902.5040908@azairenet.com>
In-Reply-To: <446CE902.5040908@azairenet.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org


Section 11.7.3 does not list the case that involves Status code
135, but it was certainly the intention that the mobile node would
deal with this in the way that Vijay explained.

This is indeed something that should be clarified in a revision.
I do not think we should change the protocol where a
clarification suffices.

--jari


_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Fri May 19 11:06:36 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fh6YG-0004t9-Sj; Fri, 19 May 2006 11:06:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fh6YF-0004t4-27
	for mip6@ietf.org; Fri, 19 May 2006 11:06:03 -0400
Received: from zcars04f.nortel.com ([47.129.242.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fh6YE-0006oa-OS
	for mip6@ietf.org; Fri, 19 May 2006 11:06:03 -0400
Received: from zrc2hxm2.corp.nortel.com (zrc2hxm2.corp.nortel.com
	[47.103.123.73])
	by zcars04f.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	k4JF5m004733; Fri, 19 May 2006 11:05:48 -0400 (EDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] MIPv6: Using the last Accepted Sequence Number in BA
Date: Fri, 19 May 2006 10:05:35 -0500
Message-ID: <6FC4416DDE56C44DA0AEE67BC7CA43710E862E1F@zrc2hxm2.corp.nortel.com>
In-Reply-To: <446CE398.2060804@azairenet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] MIPv6: Using the last Accepted Sequence Number in BA
Thread-Index: AcZ6v/+0SfVIUnhbRRW1R8Pp2en1EgAAvmYw
From: "Ahmad Muhanna" <amuhanna@nortel.com>
To: "Vijay Devarapalli" <vijay.devarapalli@AzaireNet.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86
Cc: Gopal Dommety <gdommety@cisco.com>,
	"Charles E. Perkins" <charliep@iprg.nokia.com>,
	jari.arkko@ericsson.com, dbj@cs.rice.edu,
	Basavaraj Patil <basavaraj.patil@nokia.com>, mip6@ietf.org,
	Mohamed Khalil <mkhalil@nortel.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Thanks Vijay for the comments.
Please see comments inline.

Regards,
Ahmad


>=20
>=20
> Ahmad Muhanna wrote:
> >=20
> > Hi all,
> >=20
> > In response to a Binding Update which contains an out of range
> > sequence
> > number, as per sections 9.5.1 and 11.7.1, the CN or HA is=20
> allowed to
> > send a Binding Acknowledgement with a status of 135 after
> inserting the
> > last accepted sequence number received in the last valid
> Binding Update
> > in the sequence number field (Different from the sequence number
> > received in the outstanding BU)
> >=20
> > According to MN processing of the Binding Acknowledgement
> as specified
> > under section 11.7.3., the MN will silently discard the received BA
> > rather than picking the last accepted sequence number and=20
> then generate
> > a new sequence number.
> >=20
> > I think the intention was to allow the HA or CN to
> communicate back to
> > the MN the last accepted sequence number, however, we are
> breaking the
> > protocol by using this mechanism.
> >=20
> > Could you please comment on this and let me know if I am on
> the right
> > track.
>=20
> when the mobile node receives a binding ack with
> status 135, it should pick a sequence number
> greater than what was returned in the binding ack
> and re-try with another binding update. it should
> not ignore the sequence number field in the
> binding ack.

[Ahmad]
I see this issue has two folds which we need to address.

1. The solution, as per RFC3775, in communicating the last accepted
sequence number violates the basic principle of replay protection
mechanism using sequence number. In other word, when we allow the Mobile
Node to accept the BA based on the status (135) ONLY, we are asking the
MN to ignore replay protection mechanism all together.=20

2. The more serious problem is a security issue. In the case of the HA
where there is manual IPsec, any man in the middle can replay an old BA
with a status of 135 and makes the Mobile Node to think that the
sequence number in BA is the last accepted sequence number.

Here is an example:

1. MN accidentally reboots and loose track of the last accepted sequence
number e.g. (1000).
2. MN sends a BU with seq. number =3D 1
3. HA sends a BA with status 135 and sequence number =3D 1000.
4. Man in the middle capture BA from step 3 and save.
5. MN receives BA (from step 3) and process successfully according to
current RFC3775.
6. MN sends a BU with seq. # of 1000 to the HA.
7. MN receives a successful BA with seq. # 1000.
8. After some time, MN sends another BU with seq. # =3D 1001, for =
example.
9. Man in the middle replay BA captured in step 4.
10. MN receives BA (step 9) and process successfully.

In my opinion, this a successful replay attack.


Thanks,
Ahmad


>=20
> the text in section 11.7.3 needs to be fixed when
> RFC 3775 is revised.
>=20
> thanks for catching this.
>=20
> Vijay
>=20
>=20

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Fri May 19 11:54:35 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fh7Ip-00083k-5S; Fri, 19 May 2006 11:54:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fh7In-00083f-SK
	for mip6@ietf.org; Fri, 19 May 2006 11:54:09 -0400
Received: from zrtps0kp.nortel.com ([47.140.192.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fh7In-0000Sy-HD
	for mip6@ietf.org; Fri, 19 May 2006 11:54:09 -0400
Received: from zrc2hxm2.corp.nortel.com (zrc2hxm2.corp.nortel.com
	[47.103.123.73])
	by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	k4JFs4s05661; Fri, 19 May 2006 11:54:04 -0400 (EDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] MIPv6: Using the last Accepted Sequence Number in BA
Date: Fri, 19 May 2006 10:54:03 -0500
Message-ID: <6FC4416DDE56C44DA0AEE67BC7CA43710E862F12@zrc2hxm2.corp.nortel.com>
In-Reply-To: <62B9B0847CC47543B6B3B5E26BD268E60B5F62B6@zrc2hxm2.corp.nortel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] MIPv6: Using the last Accepted Sequence Number in BA
Thread-Index: AcZ6v/+0SfVIUnhbRRW1R8Pp2en1EgAAvmYwACVt7hAAAFaYgAAAeulg
From: "Ahmad Muhanna" <amuhanna@nortel.com>
To: "Mohamed Khalil" <mkhalil@nortel.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86
Cc: Gopal Dommety <gdommety@cisco.com>,
	"Charles E. Perkins" <charliep@iprg.nokia.com>,
	jari.arkko@ericsson.com, dbj@cs.rice.edu,
	Basavaraj Patil <basavaraj.patil@nokia.com>, mip6@ietf.org,
	Vijay Devarapalli <vijay.devarapalli@AzaireNet.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

All,

One very minor correction to both scenarios,

In step 6, sequence number should have been 1001 and in step 8 sequence
number should have been 1002.

Regards,
Ahmad


> -----Original Message-----
> From: Khalil, Mohamed [RICH2:2S20:EXCH]=20
> Sent: Friday, May 19, 2006 10:47 AM
> To: Muhanna, Ahmad [RICH2:2Q30:EXCH]
> Cc: Muhanna, Ahmad [RICH2:2Q30:EXCH]; 'mip6@ietf.org'; 'Gopal=20
> Dommety'; 'Charles E. Perkins'; 'jari.arkko@ericsson.com';=20
> 'dbj@cs.rice.edu'; 'Basavaraj Patil'; 'Vijay Devarapalli'
> Subject: RE: [Mip6] MIPv6: Using the last Accepted Sequence=20
> Number in BA
>=20
>=20
>=20
> Ahmad,
>=20
> Thank you for making it clear that we need a clean solution.=20
> Let us repeat this scenario Ahamd's brought up with the clean solution
>=20
> 1. MN accidentally reboots and loose track of the last=20
> accepted sequence number e.g. (1000). 2. MN sends a BU with=20
> seq. number =3D 1=20
> 3. HA sends a BA with status 135 and sequence number =3D 1,=20
> with a new proposed SQ option =3D 1000. 4. Man in the middle=20
> capture BA from step 3 and save. 5. MN receives BA (from step=20
> 3) and process successfully according to the new proposal 6.=20
> MN sends a BU with seq. # of 1000 to the HA. 7. MN receives a=20
> successful BA with seq. # 1000. 8. After some time, MN sends=20
> another BU with seq. # =3D 1001, for example. 9. Man in the=20
> middle replay BA captured in step 4.=20
> 10. MN receives BA (step 9) and reject it because SQ#=20
> mismatch (replay protection). 11. MN receives BA with seq=20
> =3D1001 and process it successfully
>=20
> no replay attack with the new proposal
>=20
>=20
> [Ahmad wrote]
>=20
> I see this issue has two folds which we need to address.
>=20
> 1. The solution, as per RFC3775, in communicating the last=20
> accepted sequence number violates the basic principle of=20
> replay protection mechanism using sequence number. In other=20
> word, when we allow the Mobile Node to accept the BA based on=20
> the status (135) ONLY, we are asking the MN to ignore replay=20
> protection mechanism all together.=20
>=20
> 2. The more serious problem is a security issue. In the case=20
> of the HA where there is manual IPsec, any man in the middle=20
> can replay an old BA with a status of 135 and makes the=20
> Mobile Node to think that the sequence number in BA is the=20
> last accepted sequence number.
>=20
> Here is an example:
>=20
> 1. MN accidentally reboots and loose track of the last=20
> accepted sequence number e.g. (1000). 2. MN sends a BU with=20
> seq. number =3D 1=20
> 3. HA sends a BA with status 135 and sequence number =3D 1000.
> 4. Man in the middle capture BA from step 3 and save.
> 5. MN receives BA (from step 3) and process successfully=20
> according to current RFC3775. 6. MN sends a BU with seq. # of=20
> 1000 to the HA. 7. MN receives a successful BA with seq. #=20
> 1000. 8. After some time, MN sends another BU with seq. # =3D=20
> 1001, for example. 9. Man in the middle replay BA captured in step 4.=20
> 10. MN receives BA (step 9) and process successfully.
>=20
> In my opinion, this a successful replay attack.
>=20
>=20
> Thanks,
> Ahmad
>=20
>=20
> >=20
> > the text in section 11.7.3 needs to be fixed when
> > RFC 3775 is revised.
> >=20
> > thanks for catching this.
> >=20
> > Vijay
> >=20
> >=20
>=20
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
>=20
>=20

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Fri May 19 15:25:41 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FhAad-0007Cl-Tl; Fri, 19 May 2006 15:24:47 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FhAac-0007Cg-Mf
	for mip6@ietf.org; Fri, 19 May 2006 15:24:46 -0400
Received: from mail1.azairenet.com ([66.92.223.4] helo=bart.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FhAaa-0005XI-At
	for mip6@ietf.org; Fri, 19 May 2006 15:24:46 -0400
Received: from [192.168.27.202] ([10.3.40.117]) by bart.corp.azairenet.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 19 May 2006 12:24:41 -0700
Message-ID: <446E1B79.6030200@azairenet.com>
Date: Fri, 19 May 2006 12:24:41 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.2 (Windows/20060308)
MIME-Version: 1.0
To: Mohamed Khalil <mkhalil@nortel.com>
Subject: Re: [Mip6] MIPv6: Using the last Accepted Sequence Number in BA
References: <62B9B0847CC47543B6B3B5E26BD268E60B5F62B1@zrc2hxm2.corp.nortel.com>
In-Reply-To: <62B9B0847CC47543B6B3B5E26BD268E60B5F62B1@zrc2hxm2.corp.nortel.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 19 May 2006 19:24:41.0482 (UTC)
	FILETIME=[E086AEA0:01C67B79]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f66b12316365a3fe519e75911daf28a8
Cc: Gopal Dommety <gdommety@cisco.com>,
	"Charles E. Perkins" <charliep@iprg.nokia.com>,
	jari.arkko@ericsson.com, dbj@cs.rice.edu,
	Basavaraj Patil <basavaraj.patil@nokia.com>, mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Mohamed Khalil wrote:
> Vijay,
> 
> 
> the status 135 combined with the sequence number in the
> binding ack *tells* the mobile node what sequence number
> it used last. this works.
> 
> MK>> The proposed solution goes in line and consistent with what MIPv6
> standard mentioned that the sequence number should be copied into the
> BA. The current solution for 135 makes an exception for the sequence
> number rule which is not needed. I still believe going with a clean
> solution is better.

going forward I think we might be embedding more
information in a failed binding ack. IMO, we should
remove the text about ignore all binding acks with
status > 128.

Vijay



> 
> 
> this was added to address the case where the mobile node reboots
> suddenly and forgets about its binding cache entries at the HA or the CN
> when it comes up again.
> 
> MK>> I can understand that, thx.
> 
> Vijay
> 
>> -----Original Message-----
>> From: Vijay Devarapalli [mailto:vijay.devarapalli@AzaireNet.com]
>> Sent: Thursday, May 18, 2006 4:14 PM
>> To: Muhanna, Ahmad [RICH2:2Q30:EXCH]
>> Cc: mip6@ietf.org; Gopal Dommety; Charles E. Perkins;
>> jari.arkko@ericsson.com; dbj@cs.rice.edu; Basavaraj Patil; Khalil,
>> Mohamed [RICH2:2S20:EXCH]
>> Subject: Re: [Mip6] MIPv6: Using the last Accepted Sequence Number in
> BA
>>
>> Ahmad Muhanna wrote:
>>> Hi all,
>>>
>>> In response to a Binding Update which contains an out of range
>>> sequence
>>> number, as per sections 9.5.1 and 11.7.1, the CN or HA is allowed to 
>>> send a Binding Acknowledgement with a status of 135 after inserting
>> the
>>> last accepted sequence number received in the last valid Binding
>> Update
>>> in the sequence number field (Different from the sequence number
>>> received in the outstanding BU)
>>>
>>> According to MN processing of the Binding Acknowledgement as 
>>> specified under section 11.7.3., the MN will silently discard the 
>>> received BA rather than picking the last accepted sequence number and
> 
>>> then
>> generate
>>> a new sequence number.
>>>
>>> I think the intention was to allow the HA or CN to communicate back 
>>> to the MN the last accepted sequence number, however, we are breaking
> 
>>> the
>>> protocol by using this mechanism.
>>>
>>> Could you please comment on this and let me know if I am on the right
> 
>>> track.
>> when the mobile node receives a binding ack with
>> status 135, it should pick a sequence number
>> greater than what was returned in the binding ack
>> and re-try with another binding update. it should
>> not ignore the sequence number field in the
>> binding ack.
>>
>> the text in section 11.7.3 needs to be fixed when
>> RFC 3775 is revised.
>>
>> thanks for catching this.
>>
>> Vijay
>>
> 
> 


_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Fri May 19 15:39:03 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FhAoE-0001Fq-Lh; Fri, 19 May 2006 15:38:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FhAoD-0001Fl-A9
	for mip6@ietf.org; Fri, 19 May 2006 15:38:49 -0400
Received: from mail1.azairenet.com ([66.92.223.4] helo=bart.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FhAoC-0006rD-Ls
	for mip6@ietf.org; Fri, 19 May 2006 15:38:49 -0400
Received: from [192.168.27.202] ([10.3.40.117]) by bart.corp.azairenet.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 19 May 2006 12:38:44 -0700
Message-ID: <446E1EC4.8080404@azairenet.com>
Date: Fri, 19 May 2006 12:38:44 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.2 (Windows/20060308)
MIME-Version: 1.0
To: Ahmad Muhanna <amuhanna@nortel.com>
Subject: Re: [Mip6] MIPv6: Using the last Accepted Sequence Number in BA
References: <6FC4416DDE56C44DA0AEE67BC7CA43710E862E1F@zrc2hxm2.corp.nortel.com>
In-Reply-To: <6FC4416DDE56C44DA0AEE67BC7CA43710E862E1F@zrc2hxm2.corp.nortel.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 19 May 2006 19:38:44.0690 (UTC)
	FILETIME=[D71E0320:01C67B7B]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac
Cc: Gopal Dommety <gdommety@cisco.com>,
	"Charles E. Perkins" <charliep@iprg.nokia.com>,
	jari.arkko@ericsson.com, dbj@cs.rice.edu,
	Basavaraj Patil <basavaraj.patil@nokia.com>, mip6@ietf.org,
	Mohamed Khalil <mkhalil@nortel.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Ahmad Muhanna wrote:
> 1. The solution, as per RFC3775, in communicating the last accepted
> sequence number violates the basic principle of replay protection
> mechanism using sequence number. In other word, when we allow the Mobile
> Node to accept the BA based on the status (135) ONLY, we are asking the
> MN to ignore replay protection mechanism all together. 

the mobile node does not actually accept the BA.
when the status is 135, it checks only the
sequence number field to figure out which sequence
number it should be using.

> 2. The more serious problem is a security issue. In the case of the HA
> where there is manual IPsec, any man in the middle can replay an old BA

note this wont happen if dynamic keying is used.

> with a status of 135 and makes the Mobile Node to think that the
> sequence number in BA is the last accepted sequence number.

if ESP with non-null encryption is used, the
binding ack is encrypted. the attacker cannot
obviously figure out that this is a binding ack
with status '135'. the attacker won't be able to
trap this particular binding ack and replay it.

if you use the authentication option protocol,
then the status field is visible. an attacker
would be able to spot the binding ack with status
135 and replay it.

> Here is an example:
> 
> 1. MN accidentally reboots and loose track of the last accepted sequence
> number e.g. (1000).
> 2. MN sends a BU with seq. number = 1
> 3. HA sends a BA with status 135 and sequence number = 1000.
> 4. Man in the middle capture BA from step 3 and save.
> 5. MN receives BA (from step 3) and process successfully according to
> current RFC3775.
> 6. MN sends a BU with seq. # of 1001 to the HA.
> 7. MN receives a successful BA with seq. # 1001.
> 8. After some time, MN sends another BU with seq. # = 1002, for example.
> 9. Man in the middle replay BA captured in step 4.
> 10. MN receives BA (step 9) and process successfully.
> 
> In my opinion, this a successful replay attack.

(I have modified the text in steps 6,7 and 8 with
the right sequence numbers)

nope. if the binding update list on the MN says
it has received a binding ack with status 1001
with "success" status (in step 7), it would drop
the binding ack in step 10. only when the sequence
number in the binding update list is less than the
sequence number in the BA with status 135, does
the MN start using a sequence number greater than
the one returned in the BA with status 135.

Vijay

> 
> 
> Thanks,
> Ahmad
> 
> 
>> the text in section 11.7.3 needs to be fixed when
>> RFC 3775 is revised.
>>
>> thanks for catching this.
>>
>> Vijay
>>
>>


_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Fri May 19 18:15:42 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FhDFc-0006IP-G2; Fri, 19 May 2006 18:15:16 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FhDFa-0006CF-W0
	for mip6@ietf.org; Fri, 19 May 2006 18:15:14 -0400
Received: from mail1.azairenet.com ([66.92.223.4] helo=bart.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FhDFZ-0002Nv-JS
	for mip6@ietf.org; Fri, 19 May 2006 18:15:14 -0400
Received: from [192.168.27.202] ([10.3.40.117]) by bart.corp.azairenet.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 19 May 2006 15:15:10 -0700
Message-ID: <446E436E.1080801@azairenet.com>
Date: Fri, 19 May 2006 15:15:10 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.2 (Windows/20060308)
MIME-Version: 1.0
To: Mohamed Khalil <mkhalil@nortel.com>
Subject: Re: [Mip6] MIPv6: Using the last Accepted Sequence Number in BA
References: <62B9B0847CC47543B6B3B5E26BD268E60B5F62B7@zrc2hxm2.corp.nortel.com>
In-Reply-To: <62B9B0847CC47543B6B3B5E26BD268E60B5F62B7@zrc2hxm2.corp.nortel.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 19 May 2006 22:15:10.0382 (UTC)
	FILETIME=[B16CF4E0:01C67B91]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 67c1ea29f88502ef6a32ccec927970f0
Cc: Gopal Dommety <gdommety@cisco.com>,
	"Charles E. Perkins" <charliep@iprg.nokia.com>,
	jari.arkko@ericsson.com, dbj@cs.rice.edu,
	Basavaraj Patil <basavaraj.patil@nokia.com>, mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Mohamed Khalil wrote:
> Vijay,
> 
> The protocol should be robust enough and accommodate all cases. There is
> no guarantee that the BU will be sent encrypted. also there is no
> guarantee that we will be using dynamic IPSec.

I took all these into account when I replied. it will work
even with the authentication option protocol. let me know
if I missed something.

The proposed solution
> doesn't require encryption for the payload to protect against replay
> attacks in case of IPSec manual configuration, and auto authentication.
> It is clean and simple solution which goes in line with the standard
> protocol.

sure. but I am trying to see if the existing spec (with one
clarification in section 11.7.3) would be sufficient.

Vijay

> -----Original Message-----
> From: Vijay Devarapalli [mailto:vijay.devarapalli@AzaireNet.com] 
> Sent: Friday, May 19, 2006 2:39 PM
> To: Muhanna, Ahmad [RICH2:2Q30:EXCH]
> Cc: mip6@ietf.org; Gopal Dommety; Charles E. Perkins;
> jari.arkko@ericsson.com; dbj@cs.rice.edu; Basavaraj Patil; Khalil,
> Mohamed [RICH2:2S20:EXCH]
> Subject: Re: [Mip6] MIPv6: Using the last Accepted Sequence Number in BA
> 
> 
> Ahmad Muhanna wrote:
>> 1. The solution, as per RFC3775, in communicating the last accepted 
>> sequence number violates the basic principle of replay protection 
>> mechanism using sequence number. In other word, when we allow the 
>> Mobile Node to accept the BA based on the status (135) ONLY, we are 
>> asking the MN to ignore replay protection mechanism all together.
> 
> the mobile node does not actually accept the BA.
> when the status is 135, it checks only the
> sequence number field to figure out which sequence
> number it should be using.
> 
>> 2. The more serious problem is a security issue. In the case of the HA
> 
>> where there is manual IPsec, any man in the middle can replay an old 
>> BA
> 
> note this wont happen if dynamic keying is used.
> 
>> with a status of 135 and makes the Mobile Node to think that the 
>> sequence number in BA is the last accepted sequence number.
> 
> if ESP with non-null encryption is used, the
> binding ack is encrypted. the attacker cannot
> obviously figure out that this is a binding ack
> with status '135'. the attacker won't be able to
> trap this particular binding ack and replay it.
> 
> 
> MK>> what about if it is not encrypted??
> 
> 
> if you use the authentication option protocol,
> then the status field is visible. an attacker
> would be able to spot the binding ack with status
> 135 and replay it.
> 
>> Here is an example:
>>
>> 1. MN accidentally reboots and loose track of the last accepted 
>> sequence number e.g. (1000). 2. MN sends a BU with seq. number = 1
>> 3. HA sends a BA with status 135 and sequence number = 1000.
>> 4. Man in the middle capture BA from step 3 and save.
>> 5. MN receives BA (from step 3) and process successfully according to
>> current RFC3775.
>> 6. MN sends a BU with seq. # of 1001 to the HA.
>> 7. MN receives a successful BA with seq. # 1001.
>> 8. After some time, MN sends another BU with seq. # = 1002, for
> example.
>> 9. Man in the middle replay BA captured in step 4.
>> 10. MN receives BA (step 9) and process successfully.
>>
> MK>> if MN sends 8 and receive 10 before the BA (seq=1002) is received
> it will process it.
> 
>> In my opinion, this a successful replay attack.
> 
> (I have modified the text in steps 6,7 and 8 with
> the right sequence numbers)
> 
> nope. if the binding update list on the MN says
> it has received a binding ack with status 1001
> with "success" status (in step 7), it would drop
> the binding ack in step 10. only when the sequence
> number in the binding update list is less than the
> sequence number in the BA with status 135, does
> the MN start using a sequence number greater than
> the one returned in the BA with status 135.
> 
> Vijay
> 
>>
>> Thanks,
>> Ahmad
>>
>>
>>> the text in section 11.7.3 needs to be fixed when
>>> RFC 3775 is revised.
>>>
>>> thanks for catching this.
>>>
>>> Vijay
>>>
>>>
> 
> 


_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Sat May 20 09:10:47 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FhRDM-0007Mt-RY; Sat, 20 May 2006 09:09:52 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FhRDL-0007Mj-LW
	for mip6@ietf.org; Sat, 20 May 2006 09:09:51 -0400
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FhRDK-0007hy-9S
	for mip6@ietf.org; Sat, 20 May 2006 09:09:51 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by laposte.rennes.enst-bretagne.fr (8.13.4/8.13.4/2004.10.03) with
	ESMTP id k4KD9DVI021361; Sat, 20 May 2006 15:09:13 +0200
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[192.44.77.29])
	by laposte.rennes.enst-bretagne.fr (8.13.4/8.13.4/2004.09.01) with
	ESMTP id k4KD9B2Q021354; Sat, 20 May 2006 15:09:11 +0200
Received: from givry.rennes.enst-bretagne.fr
	(localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.13.1/8.13.1) with ESMTP id
	k4KD98cV047483; Sat, 20 May 2006 15:09:08 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200605201309.k4KD98cV047483@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@point6.net>
To: "Ahmad Muhanna" <amuhanna@nortel.com>
Subject: Re: [Mip6] MIPv6: Using the last Accepted Sequence Number in BA 
In-reply-to: Your message of Fri, 19 May 2006 10:05:35 CDT.
	<6FC4416DDE56C44DA0AEE67BC7CA43710E862E1F@zrc2hxm2.corp.nortel.com> 
Date: Sat, 20 May 2006 15:09:08 +0200
X-Virus-Scanned: amavisd-new at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Cc: Gopal Dommety <gdommety@cisco.com>,
	"Charles E. Perkins" <charliep@iprg.nokia.com>,
	jari.arkko@ericsson.com, dbj@cs.rice.edu,
	Basavaraj Patil <basavaraj.patil@nokia.com>, mip6@ietf.org,
	Mohamed Khalil <mkhalil@nortel.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   2. The more serious problem is a security issue. In the case of the HA
   where there is manual IPsec,

=> with manual IPsec you are open to many replay attacks, so you simply
should never use manual IPsec...

Regards
   
Francis.Dupont@point6.net

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Mon May 22 09:42:38 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FiAg2-0007ZS-NV; Mon, 22 May 2006 09:42:30 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FiAg1-0007ZH-AS
	for mip6@ietf.org; Mon, 22 May 2006 09:42:29 -0400
Received: from zcars04e.nortel.com ([47.129.242.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FiAfz-0000vh-Ur
	for mip6@ietf.org; Mon, 22 May 2006 09:42:29 -0400
Received: from zrc2hxm2.corp.nortel.com (zrc2hxm2.corp.nortel.com
	[47.103.123.73])
	by zcars04e.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id
	k4MDamQ28633; Mon, 22 May 2006 09:36:48 -0400 (EDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] MIPv6: Using the last Accepted Sequence Number in BA
Date: Mon, 22 May 2006 08:41:50 -0500
Message-ID: <6FC4416DDE56C44DA0AEE67BC7CA43710E8D971F@zrc2hxm2.corp.nortel.com>
In-Reply-To: <446E1EC4.8080404@azairenet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] MIPv6: Using the last Accepted Sequence Number in BA
Thread-Index: AcZ7e98qSrS9FP/cROyIdps31GnpcwCKA1Og
From: "Ahmad Muhanna" <amuhanna@nortel.com>
To: "Vijay Devarapalli" <vijay.devarapalli@AzaireNet.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2857c5c041d6c02d7181d602c22822c8
Cc: Gopal Dommety <gdommety@cisco.com>,
	"Charles E. Perkins" <charliep@iprg.nokia.com>,
	jari.arkko@ericsson.com, dbj@cs.rice.edu,
	Basavaraj Patil <basavaraj.patil@nokia.com>, mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi Vijay,
Comments inline.

Regards,
Ahmad

>=20
> Ahmad Muhanna wrote:
> > 1. The solution, as per RFC3775, in communicating the last accepted=20
> > sequence number violates the basic principle of replay protection=20
> > mechanism using sequence number. In other word, when we allow the=20
> > Mobile Node to accept the BA based on the status (135) ONLY, we are=20
> > asking the MN to ignore replay protection mechanism all together.
>=20
> the mobile node does not actually accept the BA.
> when the status is 135, it checks only the
> sequence number field to figure out which sequence
> number it should be using.

[Ahmad]
May be we are saying the same thing in different ways. IMO, when a
mobile Node does not accept a BA, it silently discards the message. If
the MN processes the BA and acts based on the information received in
that BA, it means MN accepted the BA. I am not trying here to argue the
issue but just for clarification.
>=20
> > 2. The more serious problem is a security issue. In the=20
> case of the HA=20
> > where there is manual IPsec, any man in the middle can=20
> replay an old=20
> > BA
>=20
> note this wont happen if dynamic keying is used.

[Ahmad]
But manual IPsec is supported as per RFC3775 and we need to have a
protocol that works for all possibilities.
>=20
> > with a status of 135 and makes the Mobile Node to think that the=20
> > sequence number in BA is the last accepted sequence number.
>=20
> if ESP with non-null encryption is used, the
> binding ack is encrypted. the attacker cannot
> obviously figure out that this is a binding ack
> with status '135'. the attacker won't be able to
> trap this particular binding ack and replay it.

[Ahmad]
Agreed.
>=20
> if you use the authentication option protocol,
> then the status field is visible. an attacker
> would be able to spot the binding ack with status
> 135 and replay it.

{Ahmad]
That's why we need a fundamental solution.

Again, IMO, what is proposed in RFC3775 is a clear violation of the
replay protection mechanism that the RFC itself proposing. I do not
think that is a good idea. We have to maintain the replay protection in
all scenarios including error scenarios and this case is no different
than any other.

>=20
> > Here is an example:
> >=20
> > 1. MN accidentally reboots and loose track of the last accepted=20
> > sequence number e.g. (1000). 2. MN sends a BU with seq. number =3D 1
> > 3. HA sends a BA with status 135 and sequence number =3D 1000.
> > 4. Man in the middle capture BA from step 3 and save.
> > 5. MN receives BA (from step 3) and process successfully=20
> according to
> > current RFC3775.
> > 6. MN sends a BU with seq. # of 1001 to the HA.
> > 7. MN receives a successful BA with seq. # 1001.
> > 8. After some time, MN sends another BU with seq. # =3D 1002,=20
> for example.
> > 9. Man in the middle replay BA captured in step 4.
> > 10. MN receives BA (step 9) and process successfully.
> >=20
> > In my opinion, this a successful replay attack.
>=20
> (I have modified the text in steps 6,7 and 8 with
> the right sequence numbers)
>=20
> nope. if the binding update list on the MN says
> it has received a binding ack with status 1001
> with "success" status (in step 7), it would drop
> the binding ack in step 10. only when the sequence
> number in the binding update list is less than the
> sequence number in the BA with status 135, does
> the MN start using a sequence number greater than
> the one returned in the BA with status 135.
>=20
> Vijay
>=20
> >=20
> >=20
> > Thanks,
> > Ahmad
> >=20
> >=20
> >> the text in section 11.7.3 needs to be fixed when
> >> RFC 3775 is revised.
> >>
> >> thanks for catching this.
> >>
> >> Vijay
> >>
> >>
>=20
>=20
>=20

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Mon May 22 10:18:43 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FiBF2-0003pk-Bp; Mon, 22 May 2006 10:18:40 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FiBF0-0003pf-R8
	for mip6@ietf.org; Mon, 22 May 2006 10:18:38 -0400
Received: from zcars04f.nortel.com ([47.129.242.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FiBEz-0002en-Iw
	for mip6@ietf.org; Mon, 22 May 2006 10:18:38 -0400
Received: from zrc2hxm2.corp.nortel.com (zrc2hxm2.corp.nortel.com
	[47.103.123.73])
	by zcars04f.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	k4MEGsp11721; Mon, 22 May 2006 10:16:54 -0400 (EDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] MIPv6: Using the last Accepted Sequence Number in BA 
Date: Mon, 22 May 2006 09:16:54 -0500
Message-ID: <62B9B0847CC47543B6B3B5E26BD268E60B5F62BA@zrc2hxm2.corp.nortel.com>
In-Reply-To: <200605201309.k4KD98cV047483@givry.rennes.enst-bretagne.fr>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] MIPv6: Using the last Accepted Sequence Number in BA 
Thread-Index: AcZ8DrS5QZFp8RRMTUiaPtHJaaVmJgBmy4Vg
From: "Mohamed Khalil" <mkhalil@nortel.com>
To: <Francis.Dupont@point6.net>, "Ahmad Muhanna" <amuhanna@nortel.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc: Gopal Dommety <gdommety@cisco.com>,
	"Charles E. Perkins" <charliep@iprg.nokia.com>,
	jari.arkko@ericsson.com, dbj@cs.rice.edu,
	Basavaraj Patil <basavaraj.patil@nokia.com>, mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

The proposed idea will make the manual IPSec more secure. I don't know
what is the problem to fix this issue in the current standard???? We
can't tell people not to use manual IPSec if it is part from the
security configuration of MIP6

-----Original Message-----
From: Francis.Dupont@point6.net [mailto:Francis.Dupont@point6.net]=20
Sent: Saturday, May 20, 2006 8:09 AM
To: Muhanna, Ahmad [RICH2:2Q30:EXCH]
Cc: Vijay Devarapalli; Gopal Dommety; Charles E. Perkins;
jari.arkko@ericsson.com; dbj@cs.rice.edu; Basavaraj Patil;
mip6@ietf.org; Khalil, Mohamed [RICH2:2S20:EXCH]
Subject: Re: [Mip6] MIPv6: Using the last Accepted Sequence Number in BA



 In your previous mail you wrote:

   2. The more serious problem is a security issue. In the case of the
HA
   where there is manual IPsec,

=3D> with manual IPsec you are open to many replay attacks, so you =
simply
should never use manual IPsec...

Regards
  =20
Francis.Dupont@point6.net


_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Mon May 22 10:43:19 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FiBc5-0002Nj-Bt; Mon, 22 May 2006 10:42:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FiBc4-0002MA-KW
	for mip6@ietf.org; Mon, 22 May 2006 10:42:28 -0400
Received: from mail.um.es ([155.54.212.109])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FiBc3-0003pN-0E
	for mip6@ietf.org; Mon, 22 May 2006 10:42:28 -0400
Received: from localhost (localhost [127.0.0.1])
	by mail.um.es (Postfix) with ESMTP id 5E3CC1FABF1;
	Mon, 22 May 2006 16:42:26 +0200 (CEST)
Received: from mail.um.es ([127.0.0.1])
	by localhost (xenon1 [127.0.0.1]) (amavisd-new, port 10024) with LMTP
	id 02782-01-53; Mon, 22 May 2006 16:42:26 +0200 (CEST)
Received: from [155.54.205.190] (unknown [155.54.205.190])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mail.um.es (Postfix) with ESMTP id 0E0EF1FAC48;
	Mon, 22 May 2006 16:42:23 +0200 (CEST)
Message-ID: <4471CDCF.7000801@dif.um.es>
Date: Mon, 22 May 2006 16:42:23 +0200
From: "Pedro M. Ruiz" <pedrom@dif.um.es>
User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: mip6@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at telemat.um.es
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2086112c730e13d5955355df27e3074b
Subject: [Mip6] CFP LOCAN 2006: 2nd Int'l Workshop on Localized
 Communications and Topology Control for Ad Hoc Networks
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org


Our apologies for duplicate postings.

---------------------------------------------------------------------------
                 CALL FOR PAPERS - LOCAN 2006
       2nd International Workshop on Localized Communication
             and Topology Protocols for Ad hoc Networks

         in conjunction with MASS-2006 (www.ieee-mass.org)
              Vancouver, Canada, October 9 - 12, 2006

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

SUBJECT AND SCOPE
-----------------
This workshop covers comprehensively the algorithmic issues in the hot
area of ad hoc and sensor networking. The design of data communication
techniques in multi-hop ad hoc networks has challenges at all layers
of communication. This workshop concentrates on the network layer
problems like data communication (routing, QoS-routing, geocasting,
multicasting, broadcasting, etc.)  and topology control (neighbor
discovery, power adjustment, neighbor elimination, etc.).

Additionally, sensor networks are currently recognized as one of the
priority research areas by NSF. The area of sensor networking is
gaining momentum within the research community. This workshop will
address ongoing research on this field, including problems such as:
physical properties, sensor training, security through intelligent
node cooperation, medium access, sensor area coverage with random and
deterministic placement, object location, sensor position
determination, energy efficient broadcasting and activity scheduling,
routing, connectivity, data dissemination and gathering, sensor
centric quality of routing, temporal message ordering, path exposure,
tree reconfiguration, topology construction, and transport layer.

The main paradigm shift is to apply localized (or greedy) schemes as
opposed to existing protocols requiring global information. Localized
algorithms are distributed algorithms where simple local node
behaviour achieves a desired global objective. Localized protocols
provide scalable solutions, that is, solutions for wireless networks
with an arbitrary number of nodes, which is the main goal of this
plan. Sensor and rooftop/mesh networks, for instance, have hundreds or
thousands of nodes.

The main objective of the workshop is to present state of the art
research results on data communication and topology control in rapidly
growing area of ad hoc and sensor networks, with emphasizes on
localized techniques.

Topics of interest include, but are not limited to:
* Medium access control
* Analytical, mobility and validation models for ad hoc networks
* Hybrid networks and wireless Internet
* Security in ad hoc networks
* Data management issues, query processing, and data delivery
* Routing, broadcasting and multicasting in ad hoc networks
* Energy-efficient protocols for ad hoc networks
* Quality of service in medium access control and routing
* Topology construction and maintenance in ad hoc networks
* Neighborhood discovery and mobility management

IMPORTANT DATES
---------------
Manuscript Submission: June 19, 2006
Acceptance Notification: July 19, 2006
Final Manuscript Due: August 10, 2006

PAPER SUBMISSION
----------------
Papers must not exceed 10 single-spaced and two-column pages using at
least 10 point size type on 8.5 x 11 inches pages. See style files,
author guidelines and instructions at the conference website. Accepted
papers will be published by IEEE Computer Society Press, as
proceedings of the MASS2006 workshops. Please submit papers via email
to both program co-chairs (pedrom@dif.um.es, fei.dai@ndsu.edu).

GENERAL CO-CHAIRS
-----------------
David Simplot-Ryl, University of Lille, France
Ivan Stojmenovic, University of Ottawa, Canada

PROGRAM CO-CHAIRS
-----------------
Pedro M. Ruiz, University of Murcia, Spain
Fei Dai, North Dakota State University, USA


Program Committee
-----------------
Michel Barbeau, Carleton University, Ottawa, Canada
Raffaele Bruno, IIT-CNR, Italy
Ian Chakeres, Boing Inc., USA
Misha Dohler, France Telecom R&D, France
Stefan Dulman, University of Twente, Netherlands
Jie Gao, State University of New York, USA
J. J. Garcia-Luna-Aceves, Univ. of California, Santa Cruz, USA
Silvia Giordano, University of Applied Science, SUPSI, Switzerland
Antonio F. Gomez-Skarmeta, University of Murcia, Spain
Isabelle Guerin Lassous, INRIA Rhone Alpes, France
Mattias Handy, Univ. Rostock, Germany
Thomas Kunz, Carleton University, Canada
Miguel A. Labrador, Univ. South Florida, USA
Pietro Manzoni, Univ. Politecnica de Valencia, Spain
Luis Orozco, Univ. Castilla La Mancha, Spain
S. S. Ravi, State University of New York at Albany, USA
Isabelle Simplot-Ryl, University of Lille, France


ADDITIONAL INFORMATION
----------------------
Additional information about the workshop will be continuously
updated at the LOCAN 2006 website.

               http://ants.dif.um.es/locan2006/

-- 
---------------------------------------------------------------------
Pedro M. Ruiz, Ph.D.                    E-mail: pedrom@dif.um.es
Fac. Informatica, Univ. of Murcia       Phone:  +34968364335
Campus de Espinardo s/n                 Fax:    +34968364151
E-30100, Espinardo, Murcia              www: ants.dif.um.es/~pedrom/
SPAIN
---------------------------------------------------------------------


_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Mon May 22 13:12:30 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FiDwD-0008F6-RY; Mon, 22 May 2006 13:11:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FiDwC-0008Ep-IH
	for mip6@ietf.org; Mon, 22 May 2006 13:11:24 -0400
Received: from mail1.azairenet.com ([66.92.223.4] helo=bart.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FiDwB-0001wX-95
	for mip6@ietf.org; Mon, 22 May 2006 13:11:24 -0400
Received: from [10.1.201.5] ([10.1.201.5]) by bart.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Mon, 22 May 2006 10:11:19 -0700
Message-ID: <4471F0B3.4090602@azairenet.com>
Date: Mon, 22 May 2006 10:11:15 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.2 (Windows/20060308)
MIME-Version: 1.0
To: Ahmad Muhanna <amuhanna@nortel.com>
Subject: Re: [Mip6] MIPv6: Using the last Accepted Sequence Number in BA
References: <6FC4416DDE56C44DA0AEE67BC7CA43710E8D971F@zrc2hxm2.corp.nortel.com>
In-Reply-To: <6FC4416DDE56C44DA0AEE67BC7CA43710E8D971F@zrc2hxm2.corp.nortel.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 22 May 2006 17:11:19.0776 (UTC)
	FILETIME=[BE607E00:01C67DC2]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: Gopal Dommety <gdommety@cisco.com>,
	"Charles E. Perkins" <charliep@iprg.nokia.com>,
	jari.arkko@ericsson.com, dbj@cs.rice.edu,
	Basavaraj Patil <basavaraj.patil@nokia.com>, mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Ahmad Muhanna wrote:

> Agreed.
>> if you use the authentication option protocol,
>> then the status field is visible. an attacker
>> would be able to spot the binding ack with status
>> 135 and replay it.
> 
> {Ahmad]
> That's why we need a fundamental solution.

see below. I think you missed part of my email.
there is no problem even with the authentication
option protocol.

>> nope. if the binding update list on the MN says
>> it has received a binding ack with status 1001
>> with "success" status (in step 7), it would drop
>> the binding ack in step 10. only when the sequence
>> number in the binding update list is less than the
>> sequence number in the BA with status 135, does
>> the MN start using a sequence number greater than
>> the one returned in the BA with status 135.

Vijay

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Mon May 22 13:38:25 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FiEM8-0001Oq-3c; Mon, 22 May 2006 13:38:12 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FiEM6-0001O8-Ma
	for mip6@ietf.org; Mon, 22 May 2006 13:38:10 -0400
Received: from zrtps0kp.nortel.com ([47.140.192.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FiEM5-00037R-Cd
	for mip6@ietf.org; Mon, 22 May 2006 13:38:10 -0400
Received: from zrc2hxm2.corp.nortel.com (zrc2hxm2.corp.nortel.com
	[47.103.123.73])
	by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	k4MHbvR28112; Mon, 22 May 2006 13:37:57 -0400 (EDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] MIPv6: Using the last Accepted Sequence Number in BA
Date: Mon, 22 May 2006 12:37:56 -0500
Message-ID: <62B9B0847CC47543B6B3B5E26BD268E60B5F62BE@zrc2hxm2.corp.nortel.com>
In-Reply-To: <4471F0B3.4090602@azairenet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] MIPv6: Using the last Accepted Sequence Number in BA
Thread-Index: AcZ9wsMphLm4+yGHSYaLsKuXj/d7sAAAyQnA
From: "Mohamed Khalil" <mkhalil@nortel.com>
To: "Vijay Devarapalli" <vijay.devarapalli@AzaireNet.com>,
	"Ahmad Muhanna" <amuhanna@nortel.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Cc: Gopal Dommety <gdommety@cisco.com>,
	"Charles E. Perkins" <charliep@iprg.nokia.com>,
	jari.arkko@ericsson.com, dbj@cs.rice.edu,
	Basavaraj Patil <basavaraj.patil@nokia.com>, mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

The major issue is with IPSec manual confg which is considered as basic
security configuration mode for MIP6. As mentioned before that this
issue is easily can be solved.

-----Original Message-----
From: Vijay Devarapalli [mailto:vijay.devarapalli@AzaireNet.com]=20
Sent: Monday, May 22, 2006 12:11 PM
To: Muhanna, Ahmad [RICH2:2Q30:EXCH]
Cc: mip6@ietf.org; Gopal Dommety; Charles E. Perkins;
jari.arkko@ericsson.com; dbj@cs.rice.edu; Basavaraj Patil; Khalil,
Mohamed [RICH2:2S20:EXCH]
Subject: Re: [Mip6] MIPv6: Using the last Accepted Sequence Number in BA


Ahmad Muhanna wrote:

> Agreed.
>> if you use the authentication option protocol,
>> then the status field is visible. an attacker
>> would be able to spot the binding ack with status
>> 135 and replay it.
>=20
> {Ahmad]
> That's why we need a fundamental solution.

see below. I think you missed part of my email.
there is no problem even with the authentication
option protocol.

>> nope. if the binding update list on the MN says
>> it has received a binding ack with status 1001
>> with "success" status (in step 7), it would drop
>> the binding ack in step 10. only when the sequence
>> number in the binding update list is less than the
>> sequence number in the BA with status 135, does
>> the MN start using a sequence number greater than
>> the one returned in the BA with status 135.

Vijay


_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Mon May 22 13:42:06 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FiEPm-0001rE-9m; Mon, 22 May 2006 13:41:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FiEPl-0001r9-35
	for mip6@ietf.org; Mon, 22 May 2006 13:41:57 -0400
Received: from mail1.azairenet.com ([66.92.223.4] helo=bart.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FiEPj-0003Mx-Lx
	for mip6@ietf.org; Mon, 22 May 2006 13:41:57 -0400
Received: from [10.1.201.0] ([10.1.201.0]) by bart.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Mon, 22 May 2006 10:41:53 -0700
Message-ID: <44723DE8.6080605@azairenet.com>
Date: Mon, 22 May 2006 15:40:40 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Debian Thunderbird 1.0.2 (X11/20060423)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Mohamed Khalil <mkhalil@nortel.com>
Subject: Re: [Mip6] MIPv6: Using the last Accepted Sequence Number in BA
References: <62B9B0847CC47543B6B3B5E26BD268E60B5F62BE@zrc2hxm2.corp.nortel.com>
In-Reply-To: <62B9B0847CC47543B6B3B5E26BD268E60B5F62BE@zrc2hxm2.corp.nortel.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 22 May 2006 17:41:53.0237 (UTC)
	FILETIME=[03347050:01C67DC7]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
Cc: Gopal Dommety <gdommety@cisco.com>,
	"Charles E. Perkins" <charliep@iprg.nokia.com>,
	jari.arkko@ericsson.com, dbj@cs.rice.edu,
	Basavaraj Patil <basavaraj.patil@nokia.com>, mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Mohamed Khalil wrote:
> The major issue is with IPSec manual confg which is considered as basic
> security configuration mode for MIP6. As mentioned before that this
> issue is easily can be solved.

there is no problem with the use of manual IPsec too.

if the binding update list on the MN says it has received
a binding ack with status 1001 with "success" status (in
step 7), it would drop the binding ack in step 10. only
when the sequence number in the binding update list is
less than the sequence number in the BA with status 135,
does the MN start using a sequence number greater than the
one returned in the BA with status 135. otherwise it sticks
to the current sequence number it is using since it is
greater than what is suggested in the binding ack.

Vijay

> 
> -----Original Message-----
> From: Vijay Devarapalli [mailto:vijay.devarapalli@AzaireNet.com] 
> Sent: Monday, May 22, 2006 12:11 PM
> To: Muhanna, Ahmad [RICH2:2Q30:EXCH]
> Cc: mip6@ietf.org; Gopal Dommety; Charles E. Perkins;
> jari.arkko@ericsson.com; dbj@cs.rice.edu; Basavaraj Patil; Khalil,
> Mohamed [RICH2:2S20:EXCH]
> Subject: Re: [Mip6] MIPv6: Using the last Accepted Sequence Number in BA
> 
> 
> Ahmad Muhanna wrote:
> 
> 
>>Agreed.
>>
>>>if you use the authentication option protocol,
>>>then the status field is visible. an attacker
>>>would be able to spot the binding ack with status
>>>135 and replay it.
>>
>>{Ahmad]
>>That's why we need a fundamental solution.
> 
> 
> see below. I think you missed part of my email.
> there is no problem even with the authentication
> option protocol.
> 
> 
>>>nope. if the binding update list on the MN says
>>>it has received a binding ack with status 1001
>>>with "success" status (in step 7), it would drop
>>>the binding ack in step 10. only when the sequence
>>>number in the binding update list is less than the
>>>sequence number in the BA with status 135, does
>>>the MN start using a sequence number greater than
>>>the one returned in the BA with status 135.
> 
> 
> Vijay
> 


_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Mon May 22 15:05:35 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FiFiS-0004ku-98; Mon, 22 May 2006 15:05:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FiFiR-0004kZ-Gx
	for mip6@ietf.org; Mon, 22 May 2006 15:05:19 -0400
Received: from hostree9f.alcatel.com ([143.209.238.159]
	helo=audl952.usa.alcatel.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FiFiP-0007QL-SN
	for mip6@ietf.org; Mon, 22 May 2006 15:05:19 -0400
Received: from usdaln07347 (usdaln07347.usa.alcatel.com [143.209.105.69])
	by audl952.usa.alcatel.com (ALCANET) with ESMTP id k4MJ55qb009185;
	Mon, 22 May 2006 14:05:05 -0500
From: "Tim Ozugur" <tim.ozugur@alcatel.com>
To: <mip6@ietf.org>
Date: Mon, 22 May 2006 14:05:05 -0500
Message-ID: <008101c67dd2$a2ef8c50$4569d18f@ad3.ad.alcatel.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1807
Thread-index: AcZu3RZf2J7ICLthSTyN8QWpYrkJBwO9IIBAAAA9e9A=
X-Scanned-By: MIMEDefang 2.51 on 143.209.238.34
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b058151374d77ee76edaac850f7449fb
Cc: tpc@bwan.org
Subject: [Mip6] Call For Papers: BWAN 2006 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0931119976=="
Errors-To: mip6-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0931119976==
Content-Type: multipart/related;
	boundary="----=_NextPart_000_0082_01C67DA8.BA198450"

This is a multi-part message in MIME format.

------=_NextPart_000_0082_01C67DA8.BA198450
Content-Type: multipart/alternative;
	boundary="----=_NextPart_001_0083_01C67DA8.BA198450"


------=_NextPart_001_0083_01C67DA8.BA198450
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

 
 (Apologies if you are receiving this message more than once) 
 (Submission deadline is extended to 15 June 2006)

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

CALL FOR PAPERS

INTERNATIONAL WORKSHOP ON BROADBAND WIRELESS

ACCESS FOR UBIQUITOUS NETWORKING (BWAN 2006)

20 September 2006 - Alghero, Sardinia, Italy 

(www.bwan.org)

Technically sponsored by IEEE (approval pending) 

 

IMPORTANT DATES:

Submission of Summaries: 15 June 2006

 

SPECIAL STUDENT REGISTRATION RATE: 

Early registration rate for students: USD 270 (cut-off date: one month prior
to the workshop)

The late registration rate for students: USD 320

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

Scope and Interests 

Today Broadband Wireless access (mobile/nomadic) is emerging to offer
outstanding opportunities. In this new world of communicating devices, the
evolution towards ubiquitous networking is promising new paradigm with the
aim of providing communication capability all the time, everywhere,
transparently and invisibly to the user, using devices embedded in the
surrounding physical environment. The implementation of such a paradigm
requires innovation in wireless network technologies and devices,
development of infrastructures, enablers supporting enhanced features for
ubiquitous capability. 
The workshop is intended to present features based on new architectures
supporting mobility and/or nomadic features for wireless access (IEEE
802.yx, Mesh,...), the sharing of the network access, bandwidth sharing on
radio access, network enablers all favoring the new perspective of
ubiquitous and ambient networking. Within the framework of BWAN 2006, the
next generation of network access will be investigated. 
Topics of interest to this workshop include (but are not limited to)
performance studies and solutions (algorithms, protocols, architectures)
that tend to improve experience of users of services and applications with
context awareness. 


Workshop topics 

  <http://www.bwan.org/immagini/punto_elenco.gif>   New Architectures and
technologies for broadband wireless access (xDSL/FTTx,etc) with mobility
features 

  <http://www.bwan.org/immagini/punto_elenco.gif>   3G and beyond 

  <http://www.bwan.org/immagini/punto_elenco.gif>   Ambient Networking 

  <http://www.bwan.org/immagini/punto_elenco.gif>   AAA (Authentication,
Authorization, Accounting) 

  <http://www.bwan.org/immagini/punto_elenco.gif>   QoS efficient and
scalable routing 

  <http://www.bwan.org/immagini/punto_elenco.gif>   Transport mechanism for
supporting various high speed traffics

  <http://www.bwan.org/immagini/punto_elenco.gif>   End to end security and
privacy issues for ubiquitous Network access

  <http://www.bwan.org/immagini/punto_elenco.gif>   xDSL/FTTx+WiFi modem
with mobility enhancement 

  <http://www.bwan.org/immagini/punto_elenco.gif>   Radio extension such as
802.xy (WiFi, WiMax, etc) P2P network 

  <http://www.bwan.org/immagini/punto_elenco.gif>   Standard and regulations

  <http://www.bwan.org/immagini/punto_elenco.gif>   Low cost and low power
integrated Modulation

  <http://www.bwan.org/immagini/punto_elenco.gif>   Network cost performance
and Business Models

  <http://www.bwan.org/immagini/punto_elenco.gif>   RFID tags,
sensors,actuators, etc

  <http://www.bwan.org/immagini/punto_elenco.gif>   Interference mitigation
for multiple access

  <http://www.bwan.org/immagini/punto_elenco.gif>   IPv6 impact

  <http://www.bwan.org/immagini/punto_elenco.gif>   Cognitive radio


Submission Dates 

  <http://www.bwan.org/immagini/punto_elenco.gif>   Submission of summaries:
15 June 2006

  <http://www.bwan.org/immagini/punto_elenco.gif>   Notification of
Acceptance: 15 July  2006 


  <http://www.bwan.org/immagini/punto_elenco.gif>   Submission Camera Ready
Papers: 10 August 2006 


Publication 

The submissions to be presented at the workshop will be selected, based on
their originality, technical merit and topical relevance of their contents.
All accepted papers will be published in the conference proceedings that
will be available at the workshop.


------=_NextPart_001_0083_01C67DA8.BA198450
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2800.1528" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial><FONT =
face=3DVerdana><FONT=20
color=3D#003366><FONT size=3D2><SPAN class=3D487385718-22052006><FONT =
face=3DArial=20
color=3D#0000ff></FONT></SPAN></FONT></FONT></FONT></FONT>&nbsp;</DIV>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><FONT=20
face=3DArial><FONT face=3DVerdana><FONT color=3D#003366><FONT =
size=3D2><SPAN=20
class=3D487385718-22052006>&nbsp;</SPAN><STRONG>(Apologies if you are =
receiving=20
this message more than once)</STRONG><SPAN =
class=3D487385718-22052006><FONT=20
face=3DArial =
color=3D#0000ff>&nbsp;</FONT></SPAN></FONT></FONT></FONT></FONT></DIV>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><FONT=20
face=3DArial><FONT face=3DVerdana><FONT color=3D#003366><FONT =
size=3D2><SPAN=20
class=3D487385718-22052006><STRONG>&nbsp;(Submission deadline is =
extended to 15=20
June 2006)</STRONG></SPAN></FONT></DIV>
<DIV>
<P><FONT=20
size=3D2><STRONG>--------------------------------------------------</STRO=
NG></FONT></P>
<P><FONT size=3D2><STRONG>CALL FOR PAPERS</STRONG></FONT></P>
<P><FONT size=3D2><STRONG>INTERNATIONAL WORKSHOP ON BROADBAND=20
WIRELESS</STRONG></FONT></P>
<P><FONT size=3D2><STRONG>ACCESS FOR UBIQUITOUS NETWORKING (BWAN=20
2006)</STRONG></FONT></P>
<P><FONT size=3D2></FONT></P>
<P><FONT size=3D2><STRONG>20 September 2006 - Alghero, Sardinia, Italy=20
</STRONG></FONT></P>
<P><FONT size=3D2><STRONG>(</STRONG></FONT><A =
href=3D"www.bwan.org"><U><FONT=20
color=3D#0000ff><FONT=20
size=3D2><STRONG>www.bwan.org</STRONG></FONT></U></FONT></A><FONT=20
size=3D2><STRONG>)</STRONG></FONT></P>
<P><FONT size=3D2><STRONG>Technically sponsored by IEEE (approval =
pending)=20
</STRONG></FONT></P>
<P><FONT size=3D2></FONT>&nbsp;</P>
<P><FONT size=3D2><STRONG>IMPORTANT DATES:</STRONG></FONT></P>
<P><FONT size=3D2><STRONG>Submission of Summaries: 15</STRONG><SPAN=20
class=3D487385718-22052006><FONT face=3DArial =
color=3D#0000ff><STRONG><FONT=20
face=3DVerdana =
color=3D#003366>&nbsp;</FONT></STRONG></FONT></SPAN><STRONG><SPAN=20
class=3D487385718-22052006><FONT face=3DArial color=3D#0000ff><FONT =
face=3DVerdana=20
color=3D#003366>June</FONT></FONT></SPAN> 2006</STRONG></FONT></P>
<P><FONT face=3DArial size=3D2><SPAN=20
class=3D348430518-03052006></SPAN></FONT>&nbsp;</P>
<P><FONT face=3DArial size=3D2><SPAN =
class=3D348430518-03052006><STRONG>SPECIAL=20
STUDENT REGISTRATION RATE: </STRONG></SPAN></FONT></P>
<P><FONT face=3DArial><FONT size=3D2><STRONG><SPAN=20
class=3D348430518-03052006>E</SPAN>arly registration rate for students: =
USD=20
270<SPAN class=3D348430518-03052006> (cut-off date:&nbsp;one month prior =
to the=20
workshop)</SPAN></STRONG></FONT></FONT></P>
<P><FONT face=3DArial><FONT size=3D2><SPAN=20
class=3D348430518-03052006></SPAN></FONT></FONT><FONT face=3DArial=20
size=3D2><STRONG>The late registration rate for students: USD=20
320</STRONG></FONT></P>
<P><FONT=20
size=3D2><STRONG>---------------------------------------------------</STR=
ONG></FONT></P></FONT></FONT>
<P align=3Djustify><FONT size=3D2><FONT face=3DVerdana><FONT =
color=3D#003366><B>Scope=20
and Interests</B> </FONT><BR><BR>Today Broadband Wireless access=20
(mobile/nomadic) is emerging to offer outstanding opportunities. In this =
new=20
world of communicating devices, the evolution towards ubiquitous =
networking is=20
promising new paradigm with the aim of providing communication =
capability all=20
the time, everywhere, transparently and invisibly to the user, using =
devices=20
embedded in the surrounding physical environment. The implementation of =
such a=20
paradigm requires innovation in wireless network technologies and =
devices,=20
development of infrastructures, enablers supporting enhanced features =
for=20
ubiquitous capability. <BR>The workshop is intended to present features =
based on=20
new architectures supporting mobility and/or nomadic features for =
wireless=20
access (IEEE 802.yx, Mesh,...), the sharing of the network access, =
bandwidth=20
sharing on radio access, network enablers all favoring the new =
perspective of=20
ubiquitous and ambient networking. Within the framework of BWAN 2006, =
the next=20
generation of network access will be investigated. <BR>Topics of =
interest to=20
this workshop include (but are not limited to) performance studies and =
solutions=20
(algorithms, protocols, architectures) that tend to improve experience =
of users=20
of services and applications with context awareness. <BR><BR><BR><FONT=20
color=3D#003366><B>Workshop topics</B> </FONT><BR><BR><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp; New=20
Architectures and technologies for broadband wireless access =
(xDSL/FTTx,etc)=20
with mobility features </FONT></FONT></P>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp; 3G=20
and beyond </FONT></P>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp;=20
Ambient Networking </FONT></P>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp; AAA=20
(Authentication, Authorization, Accounting) </FONT></P>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp; QoS=20
efficient and sca<SPAN class=3D348430518-03052006>la</SPAN>ble routing =
</FONT></P>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp;=20
Transport mechanism for supporting various high speed =
traffics</FONT></P>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp; End=20
to end security and privacy issues for ubiquitous Network =
access</FONT></P>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp;=20
xDSL/FTTx+WiFi modem with mobility enhancement </FONT></P>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp;=20
Radio extension such as 802.xy (WiFi, WiMax, etc) P2P network =
</FONT></P>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp;=20
Standard and regulations</FONT></P>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp; Low=20
cost and low power integrated Modulation</FONT></P>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp;=20
Network cost performance and Business Models</FONT></P>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp;=20
RFID tags, sensors,actuators, etc</FONT></P>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp;=20
Interference mitigation for multiple access</FONT></P>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp;=20
IPv6 impact</FONT></P>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp;=20
Cognitive radio</FONT></P><BR>
<P align=3Djustify><FONT color=3D#003366><FONT size=3D2><FONT=20
face=3DVerdana><B>Submission Dates</B> </FONT></FONT></FONT></P>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp;=20
Submission of summaries: 15&nbsp;<SPAN=20
class=3D487385718-22052006>June&nbsp;</SPAN>2006</FONT></P>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp;=20
Notification of Acceptance: 15 Ju<SPAN =
class=3D487385718-22052006>ly&nbsp;</SPAN>=20
2006 </FONT>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D11 =
border=3D0>&nbsp;=20
Submission Camera Ready Papers: 10&nbsp;<SPAN=20
class=3D487385718-22052006>August</SPAN> 2006 </FONT></P><BR>
<P align=3Djustify><FONT size=3D2><FONT face=3DVerdana><FONT=20
color=3D#003366><B>Publication</B> </FONT><BR><BR>The submissions to be =
presented=20
at the workshop will be selected, based on their originality, technical =
merit=20
and topical relevance of their contents. All accepted papers will be =
published=20
in the conference proceedings that will be available at the=20
workshop.</FONT></FONT></P></FONT></DIV></BODY></HTML>

------=_NextPart_001_0083_01C67DA8.BA198450--

------=_NextPart_000_0082_01C67DA8.BA198450
Content-Type: image/gif;
	name="punto_elenco.gif"
Content-Transfer-Encoding: base64
Content-Location: http://www.bwan.org/immagini/punto_elenco.gif

R0lGODlhDAAMAHcAACH/C01TT0ZGSUNFOS4wDQAAAAFzUkdCAK7OHOkAIf8LTVNPRkZJQ0U5LjAY
AAAADG1zT1BNU09GRklDRTkuMAgRTF2IACH/C01TT0ZGSUNFOS4wGAAAAAxjbVBQSkNtcDA3MTIC
AAABDAfaGwAh+QQBAAAAACwAAAAADAAMAIPAwMDMmTPMmQDMZgDMMwCZZgCZMwCZAAABAgMBAgMB
AgMBAgMBAgMBAgMBAgMBAgMDKQi63P4wPjMGuYYwUjkRA1MYVDUETKZa4UKqlOYSRoG1Ss1izGH4
L0MCADs=

------=_NextPart_000_0082_01C67DA8.BA198450--



--===============0931119976==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6

--===============0931119976==--





From mip6-bounces@ietf.org Mon May 22 16:06:09 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FiGex-0005Pt-Ew; Mon, 22 May 2006 16:05:47 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FiGew-0005P5-9o
	for mip6@ietf.org; Mon, 22 May 2006 16:05:46 -0400
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FiGet-00026U-Dq
	for mip6@ietf.org; Mon, 22 May 2006 16:05:46 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by laposte.rennes.enst-bretagne.fr (8.13.4/8.13.4/2004.10.03) with
	ESMTP id k4MK5NEK026777; Mon, 22 May 2006 22:05:23 +0200
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[192.44.77.29])
	by laposte.rennes.enst-bretagne.fr (8.13.4/8.13.4/2004.09.01) with
	ESMTP id k4MK5HqW026769; Mon, 22 May 2006 22:05:17 +0200
Received: from givry.rennes.enst-bretagne.fr
	(localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.13.1/8.13.1) with ESMTP id
	k4MK5FWT059496; Mon, 22 May 2006 22:05:15 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200605222005.k4MK5FWT059496@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@point6.net>
To: "Mohamed Khalil" <mkhalil@nortel.com>
Subject: Re: [Mip6] MIPv6: Using the last Accepted Sequence Number in BA 
In-reply-to: Your message of Mon, 22 May 2006 09:16:54 CDT.
	<62B9B0847CC47543B6B3B5E26BD268E60B5F62BA@zrc2hxm2.corp.nortel.com> 
Date: Mon, 22 May 2006 22:05:15 +0200
X-Virus-Scanned: amavisd-new at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Cc: Gopal Dommety <gdommety@cisco.com>,
	"Charles E. Perkins" <charliep@iprg.nokia.com>,
	jari.arkko@ericsson.com, dbj@cs.rice.edu,
	Basavaraj Patil <basavaraj.patil@nokia.com>, mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   The proposed idea will make the manual IPSec more secure.

=> no, it is already instrincically insecure and it will remain
insecure (ie, it is not enough to fix one of the many ways to
play with the lack of anti-replay).

   I don't know
   what is the problem to fix this issue in the current standard????

=> add a SHOULD NOT against manual keying.

   We can't tell people not to use manual IPSec

=> not only we can but we should!

   Regards
      
Francis.Dupont@point6.net

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Mon May 22 16:22:04 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FiGuT-0003mY-IO; Mon, 22 May 2006 16:21:49 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FiGuR-0003mI-Vn
	for mip6@ietf.org; Mon, 22 May 2006 16:21:47 -0400
Received: from zrtps0kn.nortel.com ([47.140.192.55])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FiGuP-0002pN-MW
	for mip6@ietf.org; Mon, 22 May 2006 16:21:47 -0400
Received: from zrc2hxm2.corp.nortel.com (zrc2hxm2.corp.nortel.com
	[47.103.123.73])
	by zrtps0kn.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	k4MKLdt16120; Mon, 22 May 2006 16:21:39 -0400 (EDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] MIPv6: Using the last Accepted Sequence Number in BA
Date: Mon, 22 May 2006 15:21:39 -0500
Message-ID: <62B9B0847CC47543B6B3B5E26BD268E60B5F62BF@zrc2hxm2.corp.nortel.com>
In-Reply-To: <44723DE8.6080605@azairenet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] MIPv6: Using the last Accepted Sequence Number in BA
Thread-Index: AcZ9xwlkkZ444yGoQDq9F+JKxxuGxAAFX7+A
From: "Mohamed Khalil" <mkhalil@nortel.com>
To: "Vijay Devarapalli" <vijay.devarapalli@AzaireNet.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Cc: Gopal Dommety <gdommety@cisco.com>,
	"Charles E. Perkins" <charliep@iprg.nokia.com>,
	jari.arkko@ericsson.com, dbj@cs.rice.edu,
	Basavaraj Patil <basavaraj.patil@nokia.com>, mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org



when the sequence number in the binding update list is
less than the sequence number in the BA with status 135,
does the MN start using a sequence number greater than the
one returned in the BA with status 135.=20
MK>> replay attack can happen at anytime. the condition you mentioned
could happen in a reply attack too.

otherwise it sticks
to the current sequence number it is using since it is
greater than what is suggested in the binding ack.

Vijay

>=20
> -----Original Message-----
> From: Vijay Devarapalli [mailto:vijay.devarapalli@AzaireNet.com]
> Sent: Monday, May 22, 2006 12:11 PM
> To: Muhanna, Ahmad [RICH2:2Q30:EXCH]
> Cc: mip6@ietf.org; Gopal Dommety; Charles E. Perkins;
> jari.arkko@ericsson.com; dbj@cs.rice.edu; Basavaraj Patil; Khalil,
> Mohamed [RICH2:2S20:EXCH]
> Subject: Re: [Mip6] MIPv6: Using the last Accepted Sequence Number in
BA
>=20
>=20
> Ahmad Muhanna wrote:
>=20
>=20
>>Agreed.
>>
>>>if you use the authentication option protocol,
>>>then the status field is visible. an attacker
>>>would be able to spot the binding ack with status
>>>135 and replay it.
>>
>>{Ahmad]
>>That's why we need a fundamental solution.
>=20
>=20
> see below. I think you missed part of my email.
> there is no problem even with the authentication
> option protocol.
>=20
>=20
>>>nope. if the binding update list on the MN says
>>>it has received a binding ack with status 1001
>>>with "success" status (in step 7), it would drop
>>>the binding ack in step 10. only when the sequence
>>>number in the binding update list is less than the
>>>sequence number in the BA with status 135, does
>>>the MN start using a sequence number greater than
>>>the one returned in the BA with status 135.
>=20
>=20
> Vijay
>=20



_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Mon May 22 16:34:05 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FiH67-0001Ir-V4; Mon, 22 May 2006 16:33:51 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FiH66-0001Ih-Dk
	for mip6@ietf.org; Mon, 22 May 2006 16:33:50 -0400
Received: from zcars04f.nortel.com ([47.129.242.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FiH65-0003UF-4m
	for mip6@ietf.org; Mon, 22 May 2006 16:33:50 -0400
Received: from zrc2hxm2.corp.nortel.com (zrc2hxm2.corp.nortel.com
	[47.103.123.73])
	by zcars04f.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	k4MKXep13114; Mon, 22 May 2006 16:33:41 -0400 (EDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] MIPv6: Using the last Accepted Sequence Number in BA 
Date: Mon, 22 May 2006 15:33:39 -0500
Message-ID: <62B9B0847CC47543B6B3B5E26BD268E60B5F62C0@zrc2hxm2.corp.nortel.com>
In-Reply-To: <200605222005.k4MK5FWT059496@givry.rennes.enst-bretagne.fr>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] MIPv6: Using the last Accepted Sequence Number in BA 
Thread-Index: AcZ92yQEKXT+PoU7RECbz9MfJA1z0gAA0YZQ
From: "Mohamed Khalil" <mkhalil@nortel.com>
To: <Francis.Dupont@point6.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
Cc: Gopal Dommety <gdommety@cisco.com>,
	"Charles E. Perkins" <charliep@iprg.nokia.com>,
	jari.arkko@ericsson.com, dbj@cs.rice.edu,
	Basavaraj Patil <basavaraj.patil@nokia.com>, mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org




=3D> add a SHOULD NOT against manual keying.

   I believe it will be more practical to remove this option from the
spec, since the replay protection for this option is not useful. this
will remove the overhead of implementing, testing etc this option and it
will save implementers money, time and effort.

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



From mip6-bounces@ietf.org Wed May 24 10:07:19 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fiu0S-0006XT-7u; Wed, 24 May 2006 10:06:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fiu0Q-0006X4-Td
	for mip6@ietf.org; Wed, 24 May 2006 10:06:34 -0400
Received: from smtp9.clb.oleane.net ([213.56.31.31])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fiu0K-0000TA-FP
	for mip6@ietf.org; Wed, 24 May 2006 10:06:34 -0400
Received: from Pavillonquatre ([194.3.133.88]) 
	by smtp9.clb.oleane.net with ESMTP id k4OE6Gc4003867
	for <mip6@ietf.org>; Wed, 24 May 2006 16:06:18 +0200
Message-Id: <200605241406.k4OE6Gc4003867@smtp9.clb.oleane.net>
From: "Chantal Ladouce" <chantal.ladouce@upperside.fr>
To: <mip6@ietf.org>
Date: Wed, 24 May 2006 16:06:16 +0200
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
Thread-Index: AcZ/OziT0ofB/Fh9RUOmbiib1Vk5rQ==
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 21bf7a2f1643ae0bf20c1e010766eb78
Subject: [Mip6] WiMAX Summit 2007 - Call for proposals
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1251034607=="
Errors-To: mip6-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1251034607==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_02FC_01C67F4B.FC936270"

This is a multi-part message in MIME format.

------=_NextPart_000_02FC_01C67F4B.FC936270
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

The fourth edition of the WiMAX Summit will stand in Paris next February 27
to March 02, 2007.

A  <http://www.upperside.fr/wimax2007/wimax2007cfp.htm> call for proposals
has been launched and will close on July 15. Members of the scientific
committee will examine the proposals submitted. 

 

All details at:

 <http://www.upperside.fr/wimax2007/wimax2007intro.htm>
http://www.upperside.fr/wimax2007/wimax2007intro.htm

 


------=_NextPart_000_02FC_01C67F4B.FC936270
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"City"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"place"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
	{font-family:"\@MS Mincho";
	panose-1:0 0 0 0 0 0 0 0 0 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
@page Section1
	{size:595.3pt 841.9pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DFR link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D1 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
9.0pt;font-family:Arial'>The fourth edition of the <b><u><span
style=3D'font-weight:bold'>WiMAX Summit</span></u></b> will stand in =
<st1:place
w:st=3D"on"><st1:City w:st=3D"on">Paris</st1:City></st1:place> next =
February 27 to
March 02, 2007.</span></font><font size=3D1><span lang=3DEN-GB =
style=3D'font-size:
9.0pt'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
9.0pt;font-family:Arial'>A </span></font><font size=3D1><span =
style=3D'font-size:
9.0pt'><a href=3D"http://www.upperside.fr/wimax2007/wimax2007cfp.htm"
title=3D"http://www.upperside.fr/wimax2007/wimax2007cfp.htm"><font =
color=3Dblack
face=3DArial =
title=3D"http://www.upperside.fr/wimax2007/wimax2007cfp.htm"><span
lang=3DEN-GB style=3D'font-family:Arial;color:black'>call for =
proposals</span></font></a></span></font><font
size=3D1 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:9.0pt;font-family:Arial'>
has been launched and will close on July 15. Members of the scientific
committee will examine the proposals submitted. </span></font><font =
size=3D1><span
lang=3DEN-GB style=3D'font-size:9.0pt'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 face=3D"Times New Roman"><span =
lang=3DEN-GB
style=3D'font-size:9.0pt'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
9.0pt;font-family:Arial'>All details at:</span></font><font =
size=3D1><span
lang=3DEN-GB style=3D'font-size:9.0pt'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 face=3DArial><span =
style=3D'font-size:9.0pt;
font-family:Arial'><a
href=3D"http://www.upperside.fr/wimax2007/wimax2007intro.htm"
title=3D"http://www.upperside.fr/wimax2007/wimax2007intro.htm"><span =
lang=3DEN-GB>http://www.upperside.fr/wimax2007/wimax2007intro.htm</span><=
/a></span></font><font
size=3D1><span lang=3DEN-GB =
style=3D'font-size:9.0pt'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
9.0pt;font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

------=_NextPart_000_02FC_01C67F4B.FC936270--



--===============1251034607==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6

--===============1251034607==--





From mip6-bounces@ietf.org Tue May 30 18:51:07 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FlD2K-0001U8-6S; Tue, 30 May 2006 18:50:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FlD2I-0001TI-Md; Tue, 30 May 2006 18:50:02 -0400
Received: from oak.neustar.com ([209.173.53.70])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FlD2I-0006Ea-AG; Tue, 30 May 2006 18:50:02 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10])
	by oak.neustar.com (8.12.8/8.12.8) with ESMTP id k4UMo1WR031989
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Tue, 30 May 2006 22:50:02 GMT
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1FlD2H-0000mr-BA; Tue, 30 May 2006 18:50:01 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1FlD2H-0000mr-BA@stiedprstage1.ietf.org>
Date: Tue, 30 May 2006 18:50:01 -0400
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be
Cc: mip6@ietf.org
Subject: [Mip6] I-D ACTION:draft-ietf-mip6-bootstrap-ps-05.txt 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Mobility for IPv6 Working Group of the IETF.

	Title		: Problem Statement for bootstrapping Mobile IPv6
	Author(s)	: G. Giaretta, A. Patel
	Filename	: draft-ietf-mip6-bootstrap-ps-05.txt
	Pages		: 29
	Date		: 2006-5-30
	
A mobile node needs at least the following information: a home
address, home agent address and a security association with home
agent to register with the home agent.  The process of obtaining this
information is called bootstrapping.  This document discuss the
issues involved with how the mobile node can be bootstrapped for
Mobile IPv6 and various potential deployment scenarios for mobile
node bootstrapping.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mip6-bootstrap-ps-05.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


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-mip6-bootstrap-ps-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-mip6-bootstrap-ps-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: <2006-5-30162438.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-mip6-bootstrap-ps-05.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-mip6-bootstrap-ps-05.txt"; site="ftp.ietf.org";
	access-type="anon-ftp"; directory="internet-drafts"

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


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6

--NextPart--





From mip6-bounces@ietf.org Wed May 31 03:56:05 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FlLXS-000561-Jn; Wed, 31 May 2006 03:54:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FlLXQ-00055M-VY
	for mip6@ietf.org; Wed, 31 May 2006 03:54:44 -0400
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FlLXM-0007uV-FX
	for mip6@ietf.org; Wed, 31 May 2006 03:54:44 -0400
Received: from c1-vpn5.isi.edu (c1-vpn5.isi.edu [128.9.176.35])
	by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id k4V7s3R26996
	for <mip6@ietf.org>; Wed, 31 May 2006 00:54:03 -0700 (PDT)
From: Wei Ye <weiye@ISI.EDU>
To: mip6@ietf.org
Content-Type: text/plain; charset=UTF-8
Date: Wed, 31 May 2006 00:54:03 -0700
Message-Id: <1149062043.3651.21.camel@localhost.localdomain>
Mime-Version: 1.0
X-Mailer: Evolution 2.2.3 (2.2.3-2.fc4) 
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: weiye@isi.edu
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by boreas.isi.edu id
	k4V7s3R26996
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0cff8c3ec906d056784362c06f5f88c1
Subject: [Mip6] CFP: Workshops at ACM Sensys 2006
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Our Apologies if you have received multiple copies of the CFP.

Wei Ye and Cormac J. Sreenan
SenSys'06 Publicity Co-Chairs
------------


CFP: Workshops at ACM Sensys 2006

ACM Sensys 2006 is sponsored by ACM SIGCOMM, SIGMOBILE, SIGARCH, SIGOPS,
SIGMETRICS and SIGBED; with support from NSF.
http://sensys.acm.org/2006/
=20
--------------------------

Workshop on Distributed Smart Cameras (DSC-06)

http://www.iti.tugraz.at/dsc06

Boulder, Colorado, USA
October 31, 2006

Scope:
Distributed smart cameras combine two concepts: physically =20
distributed cameras and distributed computing.  Distributed smart =20
cameras are examples of high-performance multimedia sensor networks. =20
This area brings together researchers in image processing, sensor =20
networks, and embedded system architecture.

Several groups are now working on distributed smart cameras, but =20
generally pursuing them in different research communities.  This =20
meeting would be the first event to bring together all the research =20
groups working on this problem.  We solicit papers addressing =20
theoretical and practical aspects of distributed smart cameras.  We =20
particularly encourage submissions describing applications, case =20
studies or deployments.

Topics of interest include, but are not limited to:

- Distributed embedded systems for video
- Smart camera architectures
- Collaborative embedded vision
- Networking for distributed smart cameras
- Multi-sensor systems and sensor fusion
- Middleware for distributed smart cameras
- Applications of smart cameras in areas such as surveillance, =20
  tracking and smart rooms

Submission Instructions:

We invite authors to submit papers no longer than 5 pages in PDF to =20
dsc06@iti.tugraz.at. Accepted papers will made available to workshop =20
participants. Demo presentations are welcome. If you plan to present =20
a demo of distributed smart cameras contact the workshop co-chairs.

Important Dates:

- Paper submission: July 31, 2006
- Notification of acceptance: Sep 15, 2006
- CR paper submission: Sep. 30, 2006
- Workshop: Oct. 31, 2006

Program co-chairs:
B. Rinner, TU Graz
W. Wolf, Princeton U.

Program committee:
F. Berry, Univ. Clermont-Ferrand
S. Bhattacharyya, U. Maryland
M. Bove, MIT Media Lab
J. Ferryman, Reading Univ.
C. Guestrin, CMU
R. Kleihorst, Philips Research
X. Koutsoukos, Vanderbilt U.
C. Regazzoni, Univ. Genova
M. Srivastava, UCLA
W. Strasser, Univ. T=C3=BCbingen


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

First Workshop on World-Sensor-Web (WSW'2006)

Mobile Device Centric Sensory Networks and Applications

http://www.sensorplanet.org/wsw2006/

Boulder, Colorado, USA
October 31, 200

SCOPE

The global use of mobile phones on a scale never seen before enables =20
the development of new types of application scenarios. Furthermore, a =20
mobile device centric approach to large-scale sensory networks =20
provides a challenging platform for research purposes. Additionally, =20
connecting sensory networks to the Internet creates endless =20
opportunities for applications and services, new emerging models of =20
operation.

The workshop aims to address these aspects, beside traditional =20
sensory network topics such as power management, communication =20
issues, topology management, distributed architectures, peer-to-peer =20
scenarios, etc. Demonstrations and initial ideas are welcome as well.

Original, short or position papers (max 5 page), presenting results =20
on both theoretical and practical aspects of large-scale mobile =20
device centric sensor networks are expected. We are particularly =20
interested in prototype descriptions, reports from on-going trials =20
and demonstrations, real-life deployments. Live or videod demos are =20
encouraged.

Topics of interest include but are not limited to:

- device centric sensory networks
- communication strategies and topology control
- location and mobility management
- power management, energy-efficient design
- data gathering, transport, storage, retrieval, mining and =20
  dissemination
- data analysis and visualisation
- modelling and simulation software tools
- experimental systems and demonstrations
- real-life deployments, middleware implementations
- beyond location sensing
- intelligent sensors, body sensors and their utilisation
- phone as a gateway
- end-user aspects, UI issues, use cases
- sensory networks and the Web

WORKSHOP CO-ORGANIZERS

Henry Tirri, Nokia Research Center, Helsinki, Finland
Barbara Heikkinen, Nokia Research Center, Helsinki, Finland
Boda P=C3=A9ter, Nokia Research Center, Helsinki, Finland

TECHNICAL PROGRAM COMMITTEE

Joe Paradiso, MIT Media Laboratory, Cambridge, MA, USA
Deborah Estrin, UCLA, Los Angeles, CA, USA
Gaetano Borriello, University of Washington, Seattle, WA, USA
Philippe Bonnet, University of Copenhagen, Copenhagen, Denmark
Sam Madden, MIT CSAIL, Cambridge, USA
Jukka Salminen, Nokia research Center, Helsinki, Finland

IMPORTANT DATES

Papers due:                   September 1, 2006
Notification of acceptance    September 30, 2006
Camera-ready papers due       October 10, 2006

SUBMISSION INSTRUCTIONS

WSW'2006 invites submissions for position papers or short papers on =20
prototype descriptions, early research results, reports from on-going =20
demonstrations, etc. Demonstrations, live or videod, are mostly =20
encouraged.

All papers should meet the following formatting rules:

1. Papers should be submitted in PDF format.
2. The maximum length is five pages. The paper size format is US=20
   letter, including all text, figures, references, appendices, etc.
3. Two column formatting
4. One-inch margins on all sides
5. Minimum 10-point font size (smaller fonts are acceptable for =20
   footnotes, references, and figure captions).

Questions, inquiries

Please mail to peter dot boda at nokia dot com with subject WSW2006.=20



_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6



