From mip4-bounces@ietf.org Fri Dec 01 03:05:17 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gq3ON-0001a7-GL; Fri, 01 Dec 2006 03:05:07 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gq3ON-0001a2-1I
	for mip4@ietf.org; Fri, 01 Dec 2006 03:05:07 -0500
Received: from consign.cs.umd.edu ([128.8.128.61])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gq3OK-0004lN-My
	for mip4@ietf.org; Fri, 01 Dec 2006 03:05:07 -0500
Received: from delegate.pc.cs.umd.edu (exchange.cs.umd.edu [128.8.130.248])
	by consign.cs.umd.edu (8.13.1/8.12.5) with ESMTP id kB1852mD018514
	for <mip4@ietf.org>; Fri, 1 Dec 2006 03:05:02 -0500
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Fri, 1 Dec 2006 03:04:57 -0500
Message-ID: <5B211F0A44261848B86EC460096A555A1BACCC@delegate.pc.cs.umd.edu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [NetCri07] Submission deadline extension
Thread-Index: AccVH2Qy2uAqG9VNRtCFNvFmHDfK1w==
From: "Elsharnouby, Tamer" <sharno@cs.umd.edu>
To: <mip4@ietf.org>
X-CSD-MailScanner-Information: Please email staff@cs.umd.edu for more
	information
X-CSD-MailScanner: Found to be clean
X-CSD-MailScanner-SpamCheck: not spam, SpamAssassin (cached, score=-1.44,
	required 5, ALL_TRUSTED -1.44)
X-CSD-MailScanner-From: sharno@cs.umd.edu
X-Spam-Status: No
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7da5a831c477fb6ef97f379a05fb683c
Subject: [Mip4] [NetCri07] Submission deadline extension
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

***        Our Apologies if you received this multiple              ***

Paper submission deadline extended to December 7th.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

                                Call for Papers
                                   NetCri 07

                         The First International Workshop on
                Research Challenges in Next Generation  Networks for
                   First Responders and Critical Infrastructures

                       http://www.cs.umd.edu/~sharno/NetCri07 =
<http://www.cs.umd.edu/~sharno/NetCri07>=20

                            In Conjunction with

              IEEE IPCCC 2007, New Orleans, Louisiana, April 11-13
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

As advances in pervasive computing, wireless communication and sensor
networks continue, more opportunities are open to first responders and
critical infrastructures to benefit from these technologies. Providing
first responders with the best possible technology, infrastructure and
services help save the lives of the general public and the  first
responders as well. One of the main challenges to the operations of =
first
responders and critical infrastructures is to deploy a communication
network that is dependable, secure, and rapidly deployable. In order to
operate effectively, the deployed network supports services such as
location determination, audio and video communication, and in site and
remote sensing. Another key feature for first responders and critical
infrastructures networks is to support interactions among multiple
heterogeneous networks.
    =20
This workshop provides a forum for researchers, industry, and government
agencies to discuss the challenges facing the design, deployment and
operational issues for next generation network support for first =
responders
and critical infrastructure. The workshop will identify and define
fundamental concepts and techniques, resolve conflicts between different
approaches in the area, and provide a common ground for an advanced
research and development agenda. Topics
of interest include, but are not limited to:
  - Smart environments (buildings, roads, vehicles, etc.)
  - Fast roaming  in heterogonous network environment
  - Localization and time synchronization
  - Rapidly deployable and self configuring services and networks
  - Security, dependability, privacy, and performance trade-offs
  - QoS in heterogeneous wireless networks
  - Sensor and actuator networks for information gathering and real-time
control
  - Network and system support for augmented reality and visual =
analytics
  - Simulation studies of first responders and critical infrastructures'
networks
  - Novel and adaptive communication protocols to support first =
responders
and critical infrastructure' operation
  - Resource management and allocation
  - Power control management
  - Admission, load and flow control
  - Performance analysis and experimentation of heterogeneous wireless
networks
  - Security techniques and methods for heterogeneous wireless networks
  - Interoperability among WLANs, Cellular, WSN and wired networks
  - Metrics and measurements on heterogeneous networks
  - Mobility models and traffic patterns in disaster areas
  - Cross-layer design
  - Testbeds


Paper Submission

Papers should describe original, previously unpublished work, not
currently under review by another conference, workshop, or journal. =
Authors
are invited to submit a maximum of 6 pages papers including the =
abstract,
figures and references. Papers should include the title, author(s),
authors' affiliation and an abstract.  The formatting should be =
according
to IEEE rules. Papers should be submitted in a PDF format using the EDAS
submission system.

Accepted papers will be accessible through the IEEE digital library and
are included in the conference proceedings.



Important Dates

   Submission deadline:         December 7, 2006   (Extended Deadline)
   Notification of acceptance:  January 5, 2007
   Camera ready version:        January 26, 2007


Workshop Organizing Committee

   Program Co-Chairs
        Mohamed Eltoweissy,   Virginia Tech, USA
        Moustafa Youssef,     University of Maryland, USA

   Publicity Co-Chairs
        Tamer Elsharnouby,    Microsoft Corporation, USA
        James Joshi,          University of Pittsburg, USA

   Technical Program Committee
        Arup Acharya,         IBM, USA
        Ashok Agrawala,       University of Maryland, USA
        Jonathan Agre,        Fujitsu Lab, USA
        Mustaque Ahamad,      Georgia Tech, USA
        Nils Aschenbruck,     University of Bonn, Germany
        Farag Azzedine,       King Fahd University, Saudi Arabia
        Doreen Cheng,         Samsung Research, USA
        Nagwa Elmakky,        Alexandria University, Egypt
        Mohamed Gouda,        University of Texas, USA
        Elena Guara,          Coventry University, UK
        Wendi Heinzelman,     University of Rochester, USA
        James Joshi,          University of Pittsburgh, USA
        P. Krishnan,          Avaya Labs, USA
        Scott Midkiff,        Virginia Tech, USA
        Tamer Nadeem,         Siemens Research, USA
        Farid Nait-Abdesselam,LIFL, France
        Dragos Niculescu,     NEC Labs, USA
        Stephan Olariu,       Old Dominion University, USA
        Krishna Sivalingam,   University of Maryland at BC, USA
        Stephen D. Wolthusen, University of London, USA
        Mohamed Younis,       University of Maryland at BC, USA
        Adel Youssef,         Google, USA


-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Mon Dec 04 15:28:07 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GrKPv-0001yZ-8L; Mon, 04 Dec 2006 15:27:59 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GrKPt-0001uz-Q1
	for mip4@ietf.org; Mon, 04 Dec 2006 15:27:57 -0500
Received: from web36210.mail.mud.yahoo.com ([209.191.68.236])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1GrKPm-0008VL-GS
	for mip4@ietf.org; Mon, 04 Dec 2006 15:27:57 -0500
Received: (qmail 92891 invoked by uid 60001); 4 Dec 2006 20:27:48 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=X-YMail-OSG:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID;
	b=T+4YDBw2leto7Ryxwc+69LC7U7bEAlKh08M66cKhA6iDJsRB/GOv9SYBzzw8Cvqw/QR2ZrY10uTmqRco2o4S4OVgc4zaZvPZtmNY3NeTkdhVWVzMEByHECqIB9UGSpusa+XyMJUuqFXu4Bi074YD27S0A3Wr8l4lu4t4THeYou4=;
X-YMail-OSG: KTNMuEkVM1kdn.PSvLsEelxcgOC982VuNZInDxmq
Received: from [62.231.205.110] by web36210.mail.mud.yahoo.com via HTTP;
	Mon, 04 Dec 2006 12:27:48 PST
Date: Mon, 4 Dec 2006 12:27:48 -0800 (PST)
From: sara mowag <saramowag@yahoo.com>
To: mip4@ietf.org
MIME-Version: 1.0
Message-ID: <714571.92774.qm@web36210.mail.mud.yahoo.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Subject: [Mip4] route optimization in mobile ip
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1711411088=="
Errors-To: mip4-bounces@ietf.org

--===============1711411088==
Content-Type: multipart/alternative; boundary="0-2041056652-1165264068=:92774"
Content-Transfer-Encoding: 8bit

--0-2041056652-1165264068=:92774
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Hellow every body
   
  I'm trying to do a simulation for route optimization in mobile ip using ns-2 simulator.i want to evaluate the delay and delay variation with and without route optimization in mobile ip.
   
   I need the (otcl & c++) program code as base for my work because i cant do it from the scratch. I have the flowchart for this program but i cant translate it in (otcl&c++).
   
  Please help me .
   
  Thanx
   
  Sara

 
---------------------------------
Everyone is raving about the all-new Yahoo! Mail beta.
--0-2041056652-1165264068=:92774
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

<div>Hellow every body</div>  <div>&nbsp;</div>  <div>I'm trying to do a simulation for route optimization in mobile ip using ns-2 simulator.i want to evaluate the delay and delay variation with and without route optimization in mobile ip.</div>  <div>&nbsp;</div>  <div>&nbsp;I need the (otcl &amp; c++) program code as base for my work because i cant do it from the scratch. I have the flowchart for this program but i cant translate it in (otcl&amp;c++).</div>  <div>&nbsp;</div>  <div>Please help me .</div>  <div>&nbsp;</div>  <div>Thanx</div>  <div>&nbsp;</div>  <div>Sara</div><p>&#32;


<hr size=1>Everyone is raving about <a href="http://us.rd.yahoo.com/evt=42297/*http://advision.webevents.yahoo.com/mailbeta">the all-new Yahoo! Mail beta.</a>
--0-2041056652-1165264068=:92774--


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

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

--===============1711411088==--




From mip4-bounces@ietf.org Tue Dec 05 16:57:00 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GriHU-0007HQ-DL; Tue, 05 Dec 2006 16:56:52 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GrhRM-0003sJ-1U; Tue, 05 Dec 2006 16:03:00 -0500
Received: from is1.enterasys.com ([63.160.138.52])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1GrhR8-00058q-PF; Tue, 05 Dec 2006 16:02:59 -0500
Received: from MABOSEVS2.ets.enterasys.com ([134.141.77.30]) by 
	nhrocefe2.ets.enterasys.com with Microsoft SMTPSVC(6.0.3790.1830);
	Tue, 5 Dec 2006 16:02:41 -0500
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: Tue, 5 Dec 2006 16:02:41 -0500
Message-ID: <3CFB564E055A594B82C4FE89D21565605A49F4@MABOSEVS2.ets.enterasys.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Consideration of draft-lior-radius-attribute-type-extension-01
	in RADEXT WG
Thread-Index: AccYsLOR0FxEg7QgQhip5ojm8f5C0Q==
From: "Nelson, David" <dnelson@enterasys.com>
To: <radiusext@ops.ietf.org>,
	<dime@ietf.org>
X-OriginalArrivalTime: 05 Dec 2006 21:02:41.0415 (UTC) 
	FILETIME=[B3DB4170:01C718B0]
X-imss-version: 2.044
X-imss-result: Passed
X-imss-approveListMatch: *@enterasys.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
X-Mailman-Approved-At: Tue, 05 Dec 2006 16:56:50 -0500
Cc: mip6@ietf.org, mipshop@ietf.org, mip4@ietf.org
Subject: [Mip4] Consideration of
	draft-lior-radius-attribute-type-extension-01 in RADEXT WG
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

The RADEXT WG has a charter deliverable for an extended form of RADIUS
attribute.  The apparent consensus in the WG is to solve a very simple
set of problems in this space, including the pending exhaustion of the
standard RADIUS attribute IDs, a consistent mechanism for application
layer fragmentation and reassembly for Diameter interoperability, and a
consistent mechanism for grouping of attributes for data structuring,
also for Diameter interoperability.

Given the list of proposed work in RADEXT and other IETF WGs with RADIUS
extensions work on their charters, it is conceivable that we might
exhaust the existing IANA RADIUS registry for Attribute Types fairly
soon.  Therefore, this work is considered to be of some urgency.

The structure of the extended attribute format currently under
consideration may require changes in various RADIUS extensions drafts in
RADEXT and other working groups.   This assumes that at least some of
these documents will ultimately use the RADIUS extended attribute
allocations.

The RADEXT WG Chairs are requesting that the RADEXT WG and all other
affected WGs please review the following document:

http://www.ietf.org/internet-drafts/draft-lior-radius-attribute-type-ext
ension-01.txt

Please comment as to whether this document is ready for adoption as a
RADEXT WG work item, and provide comments as to suggested changes or
improvements.  Please use the RADEXT Issue Tracker format template,
found at

http://www.drizzle.com/~aboba/RADEXT/

and submit your comments to the RADEXT WG mailing list with the keyword
"New Issue" in the subject header.

radiusext@ops.ietf.org

Please respond by December 22, 2006.  Once all the resultant open issues
have been resolved, the RADEXT WG Chairs expect that a WGLC will be
issued on the revised draft soon thereafter, early in 2007.

Thank you, in advance, for your timely review, especially during this
busy holiday season.

Regards,
=20
Dave Nelson
Bernard Aboba

Co-Chairs, RADEXT WG


-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Tue Dec 05 17:15:54 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GriZq-0007bI-IN; Tue, 05 Dec 2006 17:15:50 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GriZp-0007bB-GL
	for mip4@ietf.org; Tue, 05 Dec 2006 17:15:49 -0500
Received: from av7-1-sn3.vrr.skanova.net ([81.228.9.181])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GriZn-00062E-0L
	for mip4@ietf.org; Tue, 05 Dec 2006 17:15:49 -0500
Received: by av7-1-sn3.vrr.skanova.net (Postfix, from userid 502)
	id 60FDA37F21; Tue,  5 Dec 2006 23:15:27 +0100 (CET)
Received: from smtp3-1-sn3.vrr.skanova.net (smtp3-1-sn3.vrr.skanova.net
	[81.228.9.101]) by av7-1-sn3.vrr.skanova.net (Postfix) with ESMTP
	id 3F80137E86; Tue,  5 Dec 2006 23:15:27 +0100 (CET)
Received: from shiraz.levkowetz.com (81-232-110-214-no16.tbcn.telia.com
	[81.232.110.214])
	by smtp3-1-sn3.vrr.skanova.net (Postfix) with ESMTP id 1538037E43;
	Tue,  5 Dec 2006 23:15:44 +0100 (CET)
Received: from localhost ([127.0.0.1])
	by shiraz.levkowetz.com with esmtp (Exim 4.63)
	(envelope-from <henrik@levkowetz.com>)
	id 1GriZb-0001YJ-7n; Tue, 05 Dec 2006 23:15:35 +0100
Message-ID: <4575EF85.50604@levkowetz.com>
Date: Tue, 05 Dec 2006 23:15:33 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Thunderbird 1.5.0.8 (Macintosh/20061025)
MIME-Version: 1.0
To: Mobile IPv4 Mailing List <mip4@ietf.org>
X-Enigmail-Version: 0.94.1.2
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: mip4@ietf.org, dnelson@enterasys.com,
	mip4-chairs@tools.ietf.org, henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on shiraz.levkowetz.com);
	SAEximRunCond expanded to false
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 6cca30437e2d04f45110f2ff8dc1b1d5
Cc: mip4-chairs@tools.ietf.org, "Nelson, David" <dnelson@enterasys.com>
Subject: [Mip4] RADEXT chair information and request
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0837495087=="
Errors-To: mip4-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============0837495087==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig1157EF1BBFDA9B2A30243FCC"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig1157EF1BBFDA9B2A30243FCC
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi,

  Here's a message forwarded on behalf of David Nelson (radext):

-------- Original Message --------

The RADEXT WG has a charter deliverable for an extended form of RADIUS
attribute.  The apparent consensus in the WG is to solve a very simple
set of problems in this space, including the pending exhaustion of the
standard RADIUS attribute IDs, a consistent mechanism for application
layer fragmentation and reassembly for Diameter interoperability, and a
consistent mechanism for grouping of attributes for data structuring,
also for Diameter interoperability.

Given the list of proposed work in RADEXT and other IETF WGs with RADIUS
extensions work on their charters, it is conceivable that we might
exhaust the existing IANA RADIUS registry for Attribute Types fairly
soon.  Therefore, this work is considered to be of some urgency.

The structure of the extended attribute format currently under
consideration may require changes in various RADIUS extensions drafts in
RADEXT and other working groups.   This assumes that at least some of
these documents will ultimately use the RADIUS extended attribute
allocations.

The RADEXT WG Chairs are requesting that the RADEXT WG and all other
affected WGs please review the following document:

http://www.ietf.org/internet-drafts/draft-lior-radius-attribute-type-exte=
nsion-01.txt

Please comment as to whether this document is ready for adoption as a
RADEXT WG work item, and provide comments as to suggested changes or
improvements.  Please use the RADEXT Issue Tracker format template,
found at

http://www.drizzle.com/~aboba/RADEXT/

and submit your comments to the RADEXT WG mailing list with the keyword
"New Issue" in the subject header.

radiusext@ops.ietf.org

Please respond by December 22, 2006.  Once all the resultant open issues
have been resolved, the RADEXT WG Chairs expect that a WGLC will be
issued on the revised draft soon thereafter, early in 2007.

Thank you, in advance, for your timely review, especially during this
busy holiday season.

Regards,
=20
Dave Nelson
Bernard Aboba

Co-Chairs, RADEXT WG




--------------enig1157EF1BBFDA9B2A30243FCC
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iD8DBQFFde+GeVhrtTJkXCMRAr9zAJ9qR4v/51BSDw0qvl2gabpnRsOMxACgyshk
zkKlqjpxShiR84YcRrp/lLw=
=OeWe
-----END PGP SIGNATURE-----

--------------enig1157EF1BBFDA9B2A30243FCC--


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

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

--===============0837495087==--




From mip4-bounces@ietf.org Wed Dec 06 18:03:10 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gs5n8-0000DL-CQ; Wed, 06 Dec 2006 18:03:06 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gs3zz-0004Qg-0q
	for mip4@ietf.org; Wed, 06 Dec 2006 16:08:15 -0500
Received: from ns1.siteground5.com ([67.15.157.13] helo=serv01.siteground5.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gs3zs-0007DC-FK
	for mip4@ietf.org; Wed, 06 Dec 2006 16:08:15 -0500
Received: from boostwor by serv01.siteground5.com with local (Exim 4.52)
	id 1Gs3zP-0007dQ-Hc
	for mip4@ietf.org; Wed, 06 Dec 2006 15:07:39 -0600
To: mip4@ietf.org
Date: Wed, 6 Dec 2006 15:07:39 -0600
From: contact@ntms2007.org
Message-ID: <15c29676ac7a5095207dcc39615d627a@www.boostwork.com>
X-Priority: 3
X-Mailer: PHPMailer [version 1.73]
X-Mailer: PHPlist v2.10.2
X-MessageID: 41
X-ListMember: mip4@ietf.org
Precedence: bulk
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset="iso-8859-1"
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - serv01.siteground5.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [32094 501] / [47 12]
X-AntiAbuse: Sender Address Domain - serv01.siteground5.com
X-Source: /usr/bin/php
X-Source-Args: /usr/bin/php index.php 
X-Source-Dir: boostwork.com:/public_html/phpemaillist/admin
X-Spam-Score: 1.0 (+)
X-Scan-Signature: 43317e64100dd4d87214c51822b582d1
X-Mailman-Approved-At: Wed, 06 Dec 2006 18:03:05 -0500
Subject: [Mip4] [NTMS'2007 TELECOM PARIS] : EXTENDED DEADLINE
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Dear all,

We apologize for multiple copies of this email

1th International Conference on New Technologies, Mobility and
Security (NTMS 2007)
 Technically co-sponsored by IFIP and IEEE France Computer Section
 April 30 to May 3, 2007 - TELECOM PARIS, FRANCE
 http://www.ntms2007.org <http://www.ntms2007.org/>

IMPORTANT DATES
------------------------------
Draft papers should be submitted by January 25, 2007 
Authors will receive the acceptance notification by February 20, 2007

Final papers for presentation should be sent before March 15, 2007 
Tutorial Workshop (Instructor) Submission due : November 5, 2006 
Deadline Notification of Tutorial & Workshop Acceptance : December
30, 2006 

ABOUT NTMS'2007
--------------------------------

NTMS'2007 aims at fostering advances in the areas of New
Technologies, Wireless Networks, Mobile Computing, Ad hoc and Ambient
Networks, QoS, Network Security and E-commerce, to mention a few, and
provides a dynamic forum for researchers, students and professionals
to present their state-of-the-art research and development in these
interesting areas. 
The event will be combined with tutorial sessions and workshops.
Tutorials will precede the main program, aiming at the dissemination
of mature knowledge and technology advances in the field. Two or more
Workshops will immediately follow the main conference, offering the
opportunity for a more focused exchange of ideas and presentation of
on-going research relevant to selected topics. During NTMS'2007, demo
areas will also be available to R&D labs and consortia to demonstrate
their prototype implementations, or other prominent results.

TOPICS OF INTEREST
-------------------------------
The organising and technical committees of the conference are seeking
original contributions in the areas of, but not limited to:

Analysis and design of network architectures and algorithms 
Network management and traffic engineering 
Network, transport, and application-layer protocols 
Resource management, quality of service, signalling & scheduling 
Routing, switching, and addressing 
Network fault-tolerance & reliability, debugging & troubleshooting 
Network security, vulnerability, authentication and access control 
Intrusion Detection, Prediction, and Countermeasures 
Smart Device, Identity, Privacy and Trust 
Privacy, contract agreements, and payment systems 
Public key infrastructure implementation 
Mobile code security & Security management 
E-business and E-commerce security 
Peer-to-peer, overlay, and content distribution networks 
Optical networks and switching 
Wireless Mesh Networks & Metropolitan Area Networks (WiMAX, 802.16e) 
3G & Wireless Personal Area Networks (Wimedia, UWB, Bluetooth, ...) 
Wireless Local Area Networks (Wi-Fi, ...) & Wireless Local Loop 
Ad hoc, Sensor Networks and Embedded Systems, Ambient Networks 
Mobility management and Handover 
Medium Access Control & Scheduling Techniques for Wireless Systems 
Cross-layer network design and optimization 
Pervasive, Ubiquitous and Mobile Computing 
Agents and Middleware, Agent Computing and Agent Applications 
Grid and cluster computing & Context aware computing 
Adaptation software development 
Next generation systems & Service-oriented techniques 
Component based software engineering &Software verification &
analysis 
Web Commerce & Services, Data models, Web searching & querying 
XML, Query Processing & Optimization, Storage Structures & Indexing 
Web Mining & Web Semantic 

SUBMISSION GUIDELINES
--------------------------------------
Authors are invited to submit complete and original papers. All
submitted papers will be refereed for quality, correctness,
originality and relevance. Authors of accepted papers will be
required to produce final
versions of their papers in IEEE camera ready format (double column)
according to IEEE Computer Society Press style guidelines Preferred
maximum paper length is 5 printed pages (10-point font) including
figures, graphics and tables. However, papers for review of up to 8
pages in length will also be accepted, although accepted papers
exceeding 5 pages will be charged an overlength fee of $100 for the
6th page.
NTMS'2007 is using the EDAS Conference Management System
(http://edas.info <http://edas.info/>) to manage paper submissions
process. 

The proposal for tutorial should include the title and clear
explanation of the content of the proposed tutorial. Please include
in the proposal (1) Organizer Name, (2) Name of proposed instructor,
(3) Title of tutorial and detailed outline, (4) Qualifications of
proposed instructor, (5) Full contact information: mailing address,
telephone & fax number, and email address.

CONFERENCE COMMITTEES
-----------------------------------------
----- CONFERENCE PROGRAM CO-CHAIRS
Houda Labiod - General Chair (ENST Paris) - France
Bassel Souleiman (ENST Bretagne) - France
Bilal Chebaro (Lebanese University) - Lebanon

----- TECHNICAL PROGRAM CO-CHAIRS
Houda Labiod - General Chair (ENST Paris) - France
Stamatios Kartalopoulos, (University of Oklahoma), USA
Pascal Lorenz (Universit&eacute; de Haute Alsace), France

----- TECHNICAL PROGRAM COMMITTEE
Akmal Abdelfatah (American University of Sharjah), UAE 
Mohamed Achemlal (France Telecom R&D Caen), France 
Khaldoun Al Agha (University Paris-Sud), France 
Kablan Barbar (Lebanese University), Lebanon 
Carlo Blundo (Di Salerno University), Italy
Raouf Boutaba (University of Waterloo), Canada 
Azzedine Boukerche (University of ottawa), Canada 
Rajkumar Buyya (University of Melbourne), Australia 
Jacques Demerjian (ESRGroups), France 
Mahmoud Doughan (Lebanese University), Lebanon 
Bertrand du Castel (Axalto), USA 
Khaled Fouad Elsayed (Cairo University), Egypt 
Stephan Flake (ORGA Systems), Germany 
Steve Furnell (University of Plymouth), United Kingdom 
Giulio Galante (Istituto Superiore Mario Boella), Italy 
Wassim Haddad (Ericsson Research), Canada 
James Hughes (Sun Microsystems), USA 
Bilel Jamoussi (Nortel - Northern Telecom), Canada 
Joe Khalife (Lebanese American University), Lebanon 
Yvon Kermarrec (ENST Bretagne), France 
Bo-Kyung Lee (Korea Polytechnic University), Korea 
Seng Loke (La Trobe University), Australia 
Maryline Maknavicius (INT Evry),France 
Imad Mougharbel (Lebanese University), Lebanon 
Chafik Moukbel (Balamand University), Lebanon 
Hasnaa Moustafa (France Telecom R&D Paris), France
Elie Najm (ENST Paris), France 
Ahmad Nasri (American University of Beirut), Lebanon 
Jose Marcos Nogueira (Federal Univ. of Minas Gerais) , Brasil 
Alessandro Nordio (Polytechnico di Torino), Italy 
Pierre Paradinas (CNAM), France 
Guy Pujolle (Paris 6 Univeristy),France 
Francis Rousseaux (Universit&eacute; de Reims), France 
Pedro Ruiz (University of Murcia), Espagne 
Kassem Saleh (American University of Sharjah), UAE 
Yahya Sanadidi (University of California), USA 
Brunilde Sans&ograve; (&Eacute;cole Polytechnique de
Montr&eacute;al), Canada 
Christian Schindelhauer (University of Paderborn), Germany 
David Simplot-Ryl (Universit&eacute; de Lille 1, LIFL & INRIA),
France 
Otto Spaniol (RWTH Aachen University), Germany 
Steve Uhlig (Universit&eacute; catholique de Louvain), Belgium 
Pascal Urien (ENST Paris), France 
Sung-Ming Yen (National Central University), Taiwan 
Cui Yong (Tsinghua University), China 
Bin Zhu (Microsoft Research Asia),China 

----- Steering Board
Prof. Houda Labiod (ENST Paris), France 
Prof. Algirdas Pakstas (London Metropolitan University), England 
Prof. Stamatios Kartalopoulos (University of Oklahoma), USA 
Dr. Mohamad Badra (CNRS France), France 
Dr. Jacques Demerjian (ESRGroups), France 
Mr. Samer El Sawda (ENST Paris), France 
Dr. Ibrahim Hajjeh (Acti Group), France 
Dr. Ouahiba Fouial (ESRGroups), France 

----- WORKSHOPS & TUTORIALS CHAIR
Michel Riguidel (ENST Paris) - France
Mohamad Badra (CNRS France) - France

CONTACT:
--------------
Associate Prof. Labiod Houda
INFRES Department - ENST Paris 
46, rue barrault 75634 
Paris Cedex 13 - France 
E-mail :labiod@enst.fr






--
Powered by PHPlist, www.phplist.com --



-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Thu Dec 07 03:37:51 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GsEl5-000065-Hx; Thu, 07 Dec 2006 03:37:36 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GsEl4-00005A-CO
	for mip4@ietf.org; Thu, 07 Dec 2006 03:37:34 -0500
Received: from airmail.airvananet.com ([12.6.244.34]
	helo=airmail.wirelessworld.airvananet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GsEl2-0000Q8-Vj
	for mip4@ietf.org; Thu, 07 Dec 2006 03:37:34 -0500
Received: from nilgiri.india.wirelessworld.airvananet.com ([192.168.51.3]) by
	airmail.wirelessworld.airvananet.com with Microsoft
	SMTPSVC(6.0.3790.1830); Thu, 7 Dec 2006 03:36:18 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 7 Dec 2006 14:06:13 +0530
Message-ID: <653F3CF58193744C9DE59C217C072B58A06A8D@nilgiri.india.wirelessworld.airvananet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: MIP NAT Traversal Question
Thread-Index: AccZ2sEIQsc+cqZNRKGSQK2PKKMbYg==
From: "Arunkumar Sivaraman" <asivaraman@airvana.com>
To: <mip4@ietf.org>
X-OriginalArrivalTime: 07 Dec 2006 08:36:18.0700 (UTC)
	FILETIME=[C41ABCC0:01C719DA]
X-Spam-Score: 0.2 (/)
X-Scan-Signature: e3ebaaff3b3539efaf29ef65eea2aded
Subject: [Mip4] MIP NAT Traversal Question
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1778553532=="
Errors-To: mip4-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1778553532==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C719DA.C15F8171"

This is a multi-part message in MIME format.

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

Hello,

=20

I have a question regarding MIP NAT traversal as per rfc 3519.

=20

The rfc states in para 5, sec 4.6:

=20

If the home agent assents to UDP tunnelling, it MUST use the source
address of the registration request as the effective care-of address,
rather than the care-of address given in the registration request,
except in the case where the 'R' flag is set in the UDP Tunnel Request
Extension.

=20

The question I have is, what address does the HA put as the CoA in the
registration reply, when it assents to UDP tunneling. Is it the source
address(NAT router addr) of the registration request packet or the CoA
as sent by the FA?=20

=20

regards,

=20

Arunkumar Sivaraman,

Airvana India Pvt. Ltd.,

Ph: +91-80-41348788.

=20

"I once wanted to become an atheist,=20
but I gave up - they have no holidays."

=20


------_=_NextPart_001_01C719DA.C15F8171
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=3DContent-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"PersonName" downloadurl=3D"http://www.microsoft.com"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
h2
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.4in;
	margin-bottom:.0001pt;
	text-indent:-.4in;
	mso-list:l1 level2 lfo3;
	font-size:14.0pt;
	font-family:"Times New Roman";
	font-style:italic;}
h3
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	text-indent:-.5in;
	mso-list:l1 level3 lfo3;
	font-size:14.0pt;
	font-family:"Times New Roman";
	font-weight:normal;}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
pre
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:129905530;
	mso-list-template-ids:-1785709538;}
@list l0:level1
	{mso-level-text:%1;
	mso-level-tab-stop:30.6pt;
	mso-level-number-position:left;
	margin-left:30.6pt;
	text-indent:-.3in;
	font-variant:normal !important;
	mso-hide:none;
	text-transform:none;
	position:relative;
	top:0pt;
	mso-text-raise:0pt;
	letter-spacing:0pt;
	mso-font-kerning:0pt;
	text-effect:none;
	text-shadow:none;
	text-effect:none;
	text-effect:none;
	font-emphasize:none;
	mso-ansi-font-weight:normal;
	mso-bidi-font-weight:normal;
	text-decoration:none;
	text-underline:none;
	text-decoration:none;
	text-line-through:none;
	vertical-align:baseline;}
@list l0:level2
	{mso-level-text:"%1\.%2";
	mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	margin-left:.4in;
	text-indent:-.4in;
	font-variant:normal !important;
	mso-hide:none;
	text-transform:none;
	position:relative;
	top:0pt;
	mso-text-raise:0pt;
	letter-spacing:0pt;
	mso-font-kerning:0pt;
	text-effect:none;
	text-shadow:none;
	text-effect:none;
	text-effect:none;
	font-emphasize:none;
	mso-ansi-font-weight:normal;
	mso-bidi-font-weight:normal;
	text-decoration:none;
	text-underline:none;
	text-decoration:none;
	text-line-through:none;
	vertical-align:baseline;}
@list l0:level3
	{mso-level-text:"%1\.%2\.%3";
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	margin-left:.5in;
	text-indent:-.5in;
	mso-ansi-font-style:normal;}
@list l0:level4
	{mso-level-text:"%1\.%2\.%3\.%4";
	mso-level-tab-stop:.6in;
	mso-level-number-position:left;
	margin-left:.6in;
	text-indent:-.6in;}
@list l0:level5
	{mso-level-text:"%1\.%2\.%3\.%4\.%5";
	mso-level-tab-stop:.7in;
	mso-level-number-position:left;
	margin-left:.7in;
	text-indent:-.7in;}
@list l0:level6
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6";
	mso-level-tab-stop:.8in;
	mso-level-number-position:left;
	margin-left:.8in;
	text-indent:-.8in;}
@list l0:level7
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7";
	mso-level-tab-stop:.9in;
	mso-level-number-position:left;
	margin-left:.9in;
	text-indent:-.9in;}
@list l0:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	margin-left:1.0in;
	text-indent:-1.0in;}
@list l0:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:1.1in;
	mso-level-number-position:left;
	margin-left:1.1in;
	text-indent:-1.1in;}
@list l1
	{mso-list-id:1917133475;
	mso-list-template-ids:-722674806;}
@list l1:level1
	{mso-level-text:%1;
	mso-level-tab-stop:30.6pt;
	mso-level-number-position:left;
	margin-left:30.6pt;
	text-indent:-.3in;
	font-variant:normal !important;
	mso-hide:none;
	text-transform:none;
	position:relative;
	top:0pt;
	mso-text-raise:0pt;
	letter-spacing:0pt;
	mso-font-kerning:0pt;
	text-effect:none;
	text-shadow:none;
	text-effect:none;
	text-effect:none;
	font-emphasize:none;
	mso-ansi-font-weight:normal;
	mso-bidi-font-weight:normal;
	text-decoration:none;
	text-underline:none;
	text-decoration:none;
	text-line-through:none;
	vertical-align:baseline;}
@list l1:level2
	{mso-level-style-link:"Heading 2";
	mso-level-text:"%1\.%2";
	mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	margin-left:.4in;
	text-indent:-.4in;
	font-variant:normal !important;
	mso-hide:none;
	text-transform:none;
	position:relative;
	top:0pt;
	mso-text-raise:0pt;
	letter-spacing:0pt;
	mso-font-kerning:0pt;
	text-effect:none;
	text-shadow:none;
	text-effect:none;
	text-effect:none;
	font-emphasize:none;
	mso-ansi-font-weight:normal;
	mso-bidi-font-weight:normal;
	text-decoration:none;
	text-underline:none;
	text-decoration:none;
	text-line-through:none;
	vertical-align:baseline;}
@list l1:level3
	{mso-level-style-link:"Heading 3";
	mso-level-text:"%1\.%2\.%3";
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	margin-left:.5in;
	text-indent:-.5in;
	mso-ansi-font-style:normal;}
@list l1:level4
	{mso-level-text:"%1\.%2\.%3\.%4";
	mso-level-tab-stop:.6in;
	mso-level-number-position:left;
	margin-left:.6in;
	text-indent:-.6in;}
@list l1:level5
	{mso-level-text:"%1\.%2\.%3\.%4\.%5";
	mso-level-tab-stop:.7in;
	mso-level-number-position:left;
	margin-left:.7in;
	text-indent:-.7in;}
@list l1:level6
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6";
	mso-level-tab-stop:.8in;
	mso-level-number-position:left;
	margin-left:.8in;
	text-indent:-.8in;}
@list l1:level7
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7";
	mso-level-tab-stop:.9in;
	mso-level-number-position:left;
	margin-left:.9in;
	text-indent:-.9in;}
@list l1:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	margin-left:1.0in;
	text-indent:-1.0in;}
@list l1:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:1.1in;
	mso-level-number-position:left;
	margin-left:1.1in;
	text-indent:-1.1in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Hello,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>I have a question regarding MIP NAT traversal as per =
rfc
3519.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>The rfc states in </span></font><font size=3D2
face=3D"Courier New"><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>para
5, sec 4.6:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
font-family:"Courier New"'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><i><font size=3D2
face=3D"Courier New"><span =
style=3D'font-size:10.0pt;font-family:"Courier New";
font-style:italic'>If the home agent assents to UDP tunnelling, it MUST =
use the
source address of the registration request as the effective care-of =
address,
rather than the care-of address given in the registration request, =
except in
the case where the 'R' flag is set in the UDP Tunnel Request =
Extension.<o:p></o:p></span></font></i></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>The question I have is, what address does the HA put =
as the
CoA in the registration reply, when it assents to UDP tunneling. Is it =
the source
address(NAT router addr) of the registration request packet or the CoA =
as sent
by the FA? <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>regards,</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><st1:PersonName w:st=3D"on"><font size=3D2 =
face=3DArial><span
 style=3D'font-size:10.0pt;font-family:Arial'>Arunkumar =
Sivaraman</span></font></st1:PersonName><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>,</span></font><o:p></o:p></=
p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Airvana India Pvt. Ltd.,</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Ph: +91-80-41348788.</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

<pre><em><i><font size=3D2 color=3Dgreen face=3D"Courier New"><span =
style=3D'font-size:
10.0pt;font-family:"Courier New";color:green'>&quot;I once wanted to =
become an atheist, =
</span></font></i></em><o:p></o:p></pre><pre><em><i><font
size=3D2 color=3Dgreen face=3D"Courier New"><span =
style=3D'font-size:10.0pt;font-family:
"Courier New";color:green'>but I gave up - they have no =
holidays.&quot;</span></font></i></em><o:p></o:p></pre>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

------_=_NextPart_001_01C719DA.C15F8171--


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

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

--===============1778553532==--




From mip4-bounces@ietf.org Thu Dec 07 05:51:16 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GsGqH-0001zg-RQ; Thu, 07 Dec 2006 05:51:05 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GsGqG-0001zZ-7I
	for mip4@ietf.org; Thu, 07 Dec 2006 05:51:04 -0500
Received: from av9-1-sn3.vrr.skanova.net ([81.228.9.185])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GsGpr-0001Pl-1O
	for mip4@ietf.org; Thu, 07 Dec 2006 05:51:04 -0500
Received: by av9-1-sn3.vrr.skanova.net (Postfix, from userid 502)
	id 38E3A380BC; Thu,  7 Dec 2006 11:50:38 +0100 (CET)
Received: from smtp3-2-sn3.vrr.skanova.net (smtp3-2-sn3.vrr.skanova.net
	[81.228.9.102]) by av9-1-sn3.vrr.skanova.net (Postfix) with ESMTP
	id 1574837EF4; Thu,  7 Dec 2006 11:50:38 +0100 (CET)
Received: from shiraz.levkowetz.com (81-232-110-214-no16.tbcn.telia.com
	[81.232.110.214])
	by smtp3-2-sn3.vrr.skanova.net (Postfix) with ESMTP id DF72337E83;
	Thu,  7 Dec 2006 11:50:37 +0100 (CET)
Received: from localhost ([127.0.0.1])
	by shiraz.levkowetz.com with esmtp (Exim 4.63)
	(envelope-from <henrik@levkowetz.com>)
	id 1GsGpo-0002aR-Cw; Thu, 07 Dec 2006 11:50:36 +0100
Message-ID: <4577F1F4.5030706@levkowetz.com>
Date: Thu, 07 Dec 2006 11:50:28 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Thunderbird 1.5.0.8 (Macintosh/20061025)
MIME-Version: 1.0
To: Arunkumar Sivaraman <asivaraman@airvana.com>
Subject: Re: [Mip4] MIP NAT Traversal Question
References: <653F3CF58193744C9DE59C217C072B58A06A8D@nilgiri.india.wirelessworld.airvananet.com>
In-Reply-To: <653F3CF58193744C9DE59C217C072B58A06A8D@nilgiri.india.wirelessworld.airvananet.com>
X-Enigmail-Version: 0.94.1.2
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: asivaraman@airvana.com, mip4@ietf.org,
	henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on shiraz.levkowetz.com);
	SAEximRunCond expanded to false
X-Spam-Score: 0.1 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Cc: mip4@ietf.org
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1410087772=="
Errors-To: mip4-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============1410087772==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig093CBB907625C77F71C4CBCB"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig093CBB907625C77F71C4CBCB
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi,

on 2006-12-07 09:36 Arunkumar Sivaraman said the following:
> Hello,
>=20
> I have a question regarding MIP NAT traversal as per rfc 3519.
>=20
> The rfc states in para 5, sec 4.6:
>=20
> If the home agent assents to UDP tunnelling, it MUST use the source
> address of the registration request as the effective care-of address,
> rather than the care-of address given in the registration request,
> except in the case where the 'R' flag is set in the UDP Tunnel Request
> Extension.
>=20
> The question I have is, what address does the HA put as the CoA in the
> registration reply, when it assents to UDP tunneling. Is it the source
> address(NAT router addr) of the registration request packet or the CoA
> as sent by the FA?

If you are you asking to which IP address the HA sends the registration
reply packet, the answer is given by Section 3.4 of RFC 3344:
http://tools.ietf.org/html/rfc3344#section-3.4


	Henrik



--------------enig093CBB907625C77F71C4CBCB
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iD8DBQFFd/H7eVhrtTJkXCMRAmm8AJ9Gr7RkE7G3+hSOpoTqI1v8wgltoQCffAu5
w+5WCkAX1yXpxbo8UHQEZo4=
=H2Jv
-----END PGP SIGNATURE-----

--------------enig093CBB907625C77F71C4CBCB--


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

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

--===============1410087772==--




From mip4-bounces@ietf.org Thu Dec 07 07:20:24 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GsIEi-0003JY-M1; Thu, 07 Dec 2006 07:20:24 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GsIEh-0003IT-4D
	for mip4@ietf.org; Thu, 07 Dec 2006 07:20:23 -0500
Received: from airmail.airvananet.com ([12.6.244.34]
	helo=airmail.wirelessworld.airvananet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GsIEf-0007Z1-SO
	for mip4@ietf.org; Thu, 07 Dec 2006 07:20:23 -0500
Received: from nilgiri.india.wirelessworld.airvananet.com ([192.168.51.3]) by
	airmail.wirelessworld.airvananet.com with Microsoft
	SMTPSVC(6.0.3790.1830); Thu, 7 Dec 2006 07:19:07 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
Subject: RE: [Mip4] MIP NAT Traversal Question
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 7 Dec 2006 17:50:15 +0530
Message-ID: <653F3CF58193744C9DE59C217C072B58A06B52@nilgiri.india.wirelessworld.airvananet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip4] MIP NAT Traversal Question
Thread-Index: AccZ7V/8ilH6IGSbQVu8l/I0bIjIAAADFY9w
From: "Arunkumar Sivaraman" <asivaraman@airvana.com>
To: "Henrik Levkowetz" <henrik@levkowetz.com>
X-OriginalArrivalTime: 07 Dec 2006 12:19:07.0545 (UTC)
	FILETIME=[E48E9890:01C719F9]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Cc: mip4@ietf.org
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

My question in a MIP NAT scenario, what is the Care of Address(CoA) that
the HA puts in a reg. req reply once it detects MN/FA is behind a NAT.
Is it the private address of the FA as sent in the reg. req. or is it
the source address (NAT's address, possibly) that the HA see's in the
received reg. req. packet?

regards,
=20
Arunkumar Sivaraman,
Airvana India Pvt. Ltd.,
Ph: +91-80-41348788.
=20
"I once wanted to become an atheist,=20
but I gave up - they have no holidays."

-----Original Message-----
From: Henrik Levkowetz [mailto:henrik@levkowetz.com]=20
Sent: Thursday, December 07, 2006 4:20 PM
To: Arunkumar Sivaraman
Cc: mip4@ietf.org
Subject: Re: [Mip4] MIP NAT Traversal Question

Hi,

on 2006-12-07 09:36 Arunkumar Sivaraman said the following:
> Hello,
>=20
> I have a question regarding MIP NAT traversal as per rfc 3519.
>=20
> The rfc states in para 5, sec 4.6:
>=20
> If the home agent assents to UDP tunnelling, it MUST use the source
> address of the registration request as the effective care-of address,
> rather than the care-of address given in the registration request,
> except in the case where the 'R' flag is set in the UDP Tunnel Request
> Extension.
>=20
> The question I have is, what address does the HA put as the CoA in the
> registration reply, when it assents to UDP tunneling. Is it the source
> address(NAT router addr) of the registration request packet or the CoA
> as sent by the FA?

If you are you asking to which IP address the HA sends the registration
reply packet, the answer is given by Section 3.4 of RFC 3344:
http://tools.ietf.org/html/rfc3344#section-3.4


	Henrik



-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Thu Dec 07 11:01:12 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GsLgK-0007Zd-Qf; Thu, 07 Dec 2006 11:01:08 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GsLgJ-0007ZP-GX
	for mip4@ietf.org; Thu, 07 Dec 2006 11:01:07 -0500
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1GsLg4-0003vN-5Y
	for mip4@ietf.org; Thu, 07 Dec 2006 11:01:07 -0500
Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.120])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 4D8255A8; 
	Thu,  7 Dec 2006 17:00:49 +0100 (CET)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.177]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 7 Dec 2006 17:00:27 +0100
Received: from [147.214.237.61] ([147.214.237.61]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 7 Dec 2006 16:59:19 +0100
Message-ID: <45783A56.8040505@levkowetz.com>
Date: Thu, 07 Dec 2006 16:59:18 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Thunderbird 1.5.0.8 (Macintosh/20061025)
MIME-Version: 1.0
To: Arunkumar Sivaraman <asivaraman@airvana.com>
Subject: Re: [Mip4] MIP NAT Traversal Question
References: <653F3CF58193744C9DE59C217C072B58A06B52@nilgiri.india.wirelessworld.airvananet.com>
In-Reply-To: <653F3CF58193744C9DE59C217C072B58A06B52@nilgiri.india.wirelessworld.airvananet.com>
X-Enigmail-Version: 0.94.1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 07 Dec 2006 15:59:19.0275 (UTC)
	FILETIME=[A75C9BB0:01C71A18]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
Cc: mip4@ietf.org
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Hi,

On 2006-12-07 13:20 Arunkumar Sivaraman said the following:
> My question in a MIP NAT scenario, what is the Care of Address(CoA) that
> the HA puts in a reg. req reply once it detects MN/FA is behind a NAT.
> Is it the private address of the FA as sent in the reg. req. or is it
> the source address (NAT's address, possibly) that the HA see's in the
> received reg. req. packet?

If my answer wasn't sufficient for you, you'll have to specify *where*
in the registration reply you are talking about putting the CoA.  In
the response IP header?  In the MIP message header?  In some MIP extension?


	Henrik



> regards,
>  
> Arunkumar Sivaraman,
> Airvana India Pvt. Ltd.,
> Ph: +91-80-41348788.
>  
> "I once wanted to become an atheist, 
> but I gave up - they have no holidays."
> 
> -----Original Message-----
> From: Henrik Levkowetz [mailto:henrik@levkowetz.com] 
> Sent: Thursday, December 07, 2006 4:20 PM
> To: Arunkumar Sivaraman
> Cc: mip4@ietf.org
> Subject: Re: [Mip4] MIP NAT Traversal Question
> 
> Hi,
> 
> on 2006-12-07 09:36 Arunkumar Sivaraman said the following:
>> Hello,
>>
>> I have a question regarding MIP NAT traversal as per rfc 3519.
>>
>> The rfc states in para 5, sec 4.6:
>>
>> If the home agent assents to UDP tunnelling, it MUST use the source
>> address of the registration request as the effective care-of address,
>> rather than the care-of address given in the registration request,
>> except in the case where the 'R' flag is set in the UDP Tunnel Request
>> Extension.
>>
>> The question I have is, what address does the HA put as the CoA in the
>> registration reply, when it assents to UDP tunneling. Is it the source
>> address(NAT router addr) of the registration request packet or the CoA
>> as sent by the FA?
> 
> If you are you asking to which IP address the HA sends the registration
> reply packet, the answer is given by Section 3.4 of RFC 3344:
> http://tools.ietf.org/html/rfc3344#section-3.4
> 
> 
> 	Henrik
> 
> 
> 


-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Thu Dec 07 21:12:22 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GsVDa-0008In-KB; Thu, 07 Dec 2006 21:12:06 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GsVDZ-0008Ih-Sa
	for mip4@ietf.org; Thu, 07 Dec 2006 21:12:05 -0500
Received: from av8-2-sn3.vrr.skanova.net ([81.228.9.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GsVDY-0002oc-EU
	for mip4@ietf.org; Thu, 07 Dec 2006 21:12:05 -0500
Received: by av8-2-sn3.vrr.skanova.net (Postfix, from userid 502)
	id A079C38048; Fri,  8 Dec 2006 03:12:01 +0100 (CET)
Received: from smtp3-1-sn3.vrr.skanova.net (smtp3-1-sn3.vrr.skanova.net
	[81.228.9.101]) by av8-2-sn3.vrr.skanova.net (Postfix) with ESMTP
	id 54E8337E96; Fri,  8 Dec 2006 03:12:01 +0100 (CET)
Received: from shiraz.levkowetz.com (81-232-110-214-no16.tbcn.telia.com
	[81.232.110.214])
	by smtp3-1-sn3.vrr.skanova.net (Postfix) with ESMTP id 0ACF737E49;
	Fri,  8 Dec 2006 03:12:01 +0100 (CET)
Received: from localhost ([127.0.0.1])
	by shiraz.levkowetz.com with esmtp (Exim 4.63)
	(envelope-from <henrik@levkowetz.com>)
	id 1GsVDT-0004BG-B3; Fri, 08 Dec 2006 03:11:59 +0100
Message-ID: <4578C9E0.7080801@levkowetz.com>
Date: Fri, 08 Dec 2006 03:11:44 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Thunderbird 1.5.0.8 (Macintosh/20061025)
MIME-Version: 1.0
To: Arunkumar Sivaraman <asivaraman@airvana.com>
Subject: Re: [Mip4] MIP NAT Traversal Question
References: <653F3CF58193744C9DE59C217C072B58A06B52@nilgiri.india.wirelessworld.airvananet.com>
	<45783A56.8040505@levkowetz.com>
	<653F3CF58193744C9DE59C217C072B5883BA7E@nilgiri.india.wirelessworld.airvananet.com>
	<45785CE4.70502@levkowetz.com>
	<653F3CF58193744C9DE59C217C072B5883BA80@nilgiri.india.wirelessworld.airvananet.com>
In-Reply-To: <653F3CF58193744C9DE59C217C072B5883BA80@nilgiri.india.wirelessworld.airvananet.com>
X-Enigmail-Version: 0.94.1.2
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: asivaraman@airvana.com, mip4@ietf.org,
	henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on shiraz.levkowetz.com);
	SAEximRunCond expanded to false
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be
Cc: Mobile IPv4 Mailing List <mip4@ietf.org>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1091950848=="
Errors-To: mip4-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============1091950848==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig856503F2148EDC5424939A47"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig856503F2148EDC5424939A47
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi Arun,

on 2006-12-08 02:51 Arunkumar Sivaraman said the following:
=2E..
>=20
> on 2006-12-07 18:59 Arunkumar Sivaraman said the following:
>> Let me probably restate my question.
>>=20
>> If during initial reg. req. the HA has assented for UDP tunneling and
>> for that particular session reg. revoc. has been negotiated, then
>> when the actual reg. revocation has to be sent to the FA, does the HA
>> put the foreign domain address in the reg. revoc. pkt as the private
>> address of the FA or does it still put the public ip address of the
>> NAT router, behind which the FA resides.
>>=20
>> RFC 3543 states foregin domain address to be foreign's agent IP
>> address.
>=20
> Ah.  Now this actually becomes interesting, and not something already
> obviously covered in From mip4-bounces@ietf.org Thu Dec 07 21:12:22 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GsVDa-0008In-KB; Thu, 07 Dec 2006 21:12:06 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GsVDZ-0008Ih-Sa
	for mip4@ietf.org; Thu, 07 Dec 2006 21:12:05 -0500
Received: from av8-2-sn3.vrr.skanova.net ([81.228.9.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GsVDY-0002oc-EU
	for mip4@ietf.org; Thu, 07 Dec 2006 21:12:05 -0500
Received: by av8-2-sn3.vrr.skanova.net (Postfix, from userid 502)
	id A079C38048; Fri,  8 Dec 2006 03:12:01 +0100 (CET)
Received: from smtp3-1-sn3.vrr.skanova.net (smtp3-1-sn3.vrr.skanova.net
	[81.228.9.101]) by av8-2-sn3.vrr.skanova.net (Postfix) with ESMTP
	id 54E8337E96; Fri,  8 Dec 2006 03:12:01 +0100 (CET)
Received: from shiraz.levkowetz.com (81-232-110-214-no16.tbcn.telia.com
	[81.232.110.214])
	by smtp3-1-sn3.vrr.skanova.net (Postfix) with ESMTP id 0ACF737E49;
	Fri,  8 Dec 2006 03:12:01 +0100 (CET)
Received: from localhost ([127.0.0.1])
	by shiraz.levkowetz.com with esmtp (Exim 4.63)
	(envelope-from <henrik@levkowetz.com>)
	id 1GsVDT-0004BG-B3; Fri, 08 Dec 2006 03:11:59 +0100
Message-ID: <4578C9E0.7080801@levkowetz.com>
Date: Fri, 08 Dec 2006 03:11:44 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Thunderbird 1.5.0.8 (Macintosh/20061025)
MIME-Version: 1.0
To: Arunkumar Sivaraman <asivaraman@airvana.com>
Subject: Re: [Mip4] MIP NAT Traversal Question
References: <653F3CF58193744C9DE59C217C072B58A06B52@nilgiri.india.wirelessworld.airvananet.com>
	<45783A56.8040505@levkowetz.com>
	<653F3CF58193744C9DE59C217C072B5883BA7E@nilgiri.india.wirelessworld.airvananet.com>
	<45785CE4.70502@levkowetz.com>
	<653F3CF58193744C9DE59C217C072B5883BA80@nilgiri.india.wirelessworld.airvananet.com>
In-Reply-To: <653F3CF58193744C9DE59C217C072B5883BA80@nilgiri.india.wirelessworld.airvananet.com>
X-Enigmail-Version: 0.94.1.2
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: asivaraman@airvana.com, mip4@ietf.org,
	henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on shiraz.levkowetz.com);
	SAEximRunCond expanded to false
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be
Cc: Mobile IPv4 Mailing List <mip4@ietf.org>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1091950848=="
Errors-To: mip4-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============1091950848==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig856503F2148EDC5424939A47"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig856503F2148EDC5424939A47
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi Arun,

on 2006-12-08 02:51 Arunkumar Sivaraman said the following:
=2E..
>=20
> on 2006-12-07 18:59 Arunkumar Sivaraman said the following:
>> Let me probably restate my question.
>>=20
>> If during initial reg. req. the HA has assented for UDP tunneling and
>> for that particular session reg. revoc. has been negotiated, then
>> when the actual reg. revocation has to be sent to the FA, does the HA
>> put the foreign domain address in the reg. revoc. pkt as the private
>> address of the FA or does it still put the public ip address of the
>> NAT router, behind which the FA resides.
>>=20
>> RFC 3543 states foregin domain address to be foreign's agent IP
>> address.
>=20
> Ah.  Now this actually becomes interesting, and not something already
> obviously covered in existing documents.
>=20
>=20
> My thought would be that the destination IP address has to be the
> effective CoA (in order for the registration revocation message to
> reach the FA at all), but the Foreign Domain Address must be the
> CoA indicated by the FA in as CoA in the Registration Request message,
> so that the FA can retrieve the proper context for the revocation.
>=20
> [Arun]: This was my understanding too though the RFC doesn't
> explicitly mention it. So, what this means is that even though as per
> RFC 3519, the HA will use the source address of the reg. req. packet
> as the 'effective' CoA, for all HA-initiated MIP signalling

No!

We've *only* covered the Foreign Domain Address of the registration
revocation message here, nothing else.  If there are other cases not
covered in 3519, we need to inspect them individually to understand
the effects.

> messages
> like the registration revocation, the HA will still continue to use
> the original CoA - aka the private address of the FA.

I'm sure you mean this right, but what you're saying lacks the
necessary distinctions.

What we can say is that in the IP header, the HA follows Section 3.4
of RFC 3344, which is equivalent with using the effective CoA, while
for the Foreign Domain Address of a Registration Revocation, it uses
the CoA received in the Registration Request message from the FA,
which you call the original CoA.

> [Arun]: Can we add a text to RFC 3519 to explicitly state the use of
> CoA for HA-initiated mip signalling messages in NAT scenarios?

If we do a bis version of RFC 3519, it might make sense to add
text about the Foreign Domain Address of the Registration Revocation
message, but we can't add any general text about this without
understanding the effects.

> Do you mind if I send this reply to the MIP4 list too?
> [Arun]: I forgot to copy the group in my last mail. Pls do so.=20

Done.


	Henrik


--------------enig856503F2148EDC5424939A47
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iD8DBQFFeMnoeVhrtTJkXCMRAnQuAJ0TnKpVWDckPeczRDNZflCP0zNtWwCg5hMv
HTVWWLmFtPTGySCnMyX/nsY=
=dKP5
-----END PGP SIGNATURE-----

--------------enig856503F2148EDC5424939A47--


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

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

--===============1091950848==--


From mip4-bounces@ietf.org Thu Dec 07 21:12:22 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GsVDf-0008LV-SS; Thu, 07 Dec 2006 21:12:11 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GsVDf-0008LQ-8t
	for mip4@ietf.org; Thu, 07 Dec 2006 21:12:11 -0500
Received: from av8-2-sn3.vrr.skanova.net ([81.228.9.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GsVDd-0002qN-SQ
	for mip4@ietf.org; Thu, 07 Dec 2006 21:12:11 -0500
Received: by av8-2-sn3.vrr.skanova.net (Postfix, from userid 502)
	id 7E8C638002; Fri,  8 Dec 2006 03:12:09 +0100 (CET)
Received: from smtp3-1-sn3.vrr.skanova.net (smtp3-1-sn3.vrr.skanova.net
	[81.228.9.101]) by av8-2-sn3.vrr.skanova.net (Postfix) with ESMTP
	id 5A7CC37E96; Fri,  8 Dec 2006 03:12:09 +0100 (CET)
Received: from shiraz.levkowetz.com (81-232-110-214-no16.tbcn.telia.com
	[81.232.110.214])
	by smtp3-1-sn3.vrr.skanova.net (Postfix) with ESMTP id 4A07737E49;
	Fri,  8 Dec 2006 03:12:09 +0100 (CET)
Received: from localhost ([127.0.0.1])
	by shiraz.levkowetz.com with esmtp (Exim 4.63)
	(envelope-from <henrik@levkowetz.com>)
	id 1GsVDb-0004Fr-TB; Fri, 08 Dec 2006 03:12:09 +0100
Message-ID: <4578C9F7.30705@levkowetz.com>
Date: Fri, 08 Dec 2006 03:12:07 +0100
From: Henrik Levkowetz <henrik@levkowetz.cexisting documents.
>=20
>=20
> My thought would be that the destination IP address has to be the
> effective CoA (in order for the registration revocation message to
> reach the FA at all), but the Foreign Domain Address must be the
> CoA indicated by the FA in as CoA in the Registration Request message,
> so that the FA can retrieve the proper context for the revocation.
>=20
> [Arun]: This was my understanding too though the RFC doesn't
> explicitly mention it. So, what this means is that even though as per
> RFC 3519, the HA will use the source address of the reg. req. packet
> as the 'effective' CoA, for all HA-initiated MIP signalling

No!

We've *only* covered the Foreign Domain Address of the registration
revocation message here, nothing else.  If there are other cases not
covered in 3519, we need to inspect them individually to understand
the effects.

> messages
> like the registration revocation, the HA will still continue to use
> the original CoA - aka the private address of the FA.

I'm sure you mean this right, but what you're saying lacks the
necessary distinctions.

What we can say is that in the IP header, the HA follows Section 3.4
of RFC 3344, which is equivalent with using the effective CoA, while
for the Foreign Domain Address of a Registration Revocation, it uses
the CoA received in the Registration Request message from the FA,
which you call the original CoA.

> [Arun]: Can we add a text to RFC 3519 to explicitly state the use of
> CoA for HA-initiated mip signalling messages in NAT scenarios?

If we do a bis version of RFC 3519, it might make sense to add
text about the Foreign Domain Address of the Registration Revocation
message, but we can't add any general text about this without
understanding the effects.

> Do you mind if I send this reply to the MIP4 list too?
> [Arun]: I forgot to copy the group in my last mail. Pls do so.=20

Done.


	Henrik


--------------enig856503F2148EDC5424939A47
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iD8DBQFFeMnoeVhrtTJkXCMRAnQuAJ0TnKpVWDckPeczRDNZflCP0zNtWwCg5hMv
HTVWWLmFtPTGySCnMyX/nsY=
=dKP5
-----END PGP SIGNATURE-----

--------------enig856503F2148EDC5424939A47--


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

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

--===============1091950848==--


From mip4-bounces@ietf.org Thu Dec 07 21:12:22 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GsVDf-0008LV-SS; Thu, 07 Dec 2006 21:12:11 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GsVDf-0008LQ-8t
	for mip4@ietf.org; Thu, 07 Dec 2006 21:12:11 -0500
Received: from av8-2-sn3.vrr.skanova.net ([81.228.9.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GsVDd-0002qN-SQ
	for mip4@ietf.org; Thu, 07 Dec 2006 21:12:11 -0500
Received: by av8-2-sn3.vrr.skanova.net (Postfix, from userid 502)
	id 7E8C638002; Fri,  8 Dec 2006 03:12:09 +0100 (CET)
Received: from smtp3-1-sn3.vrr.skanova.net (smtp3-1-sn3.vrr.skanova.net
	[81.228.9.101]) by av8-2-sn3.vrr.skanova.net (Postfix) with ESMTP
	id 5A7CC37E96; Fri,  8 Dec 2006 03:12:09 +0100 (CET)
Received: from shiraz.levkowetz.com (81-232-110-214-no16.tbcn.telia.com
	[81.232.110.214])
	by smtp3-1-sn3.vrr.skanova.net (Postfix) with ESMTP id 4A07737E49;
	Fri,  8 Dec 2006 03:12:09 +0100 (CET)
Received: from localhost ([127.0.0.1])
	by shiraz.levkowetz.com with esmtp (Exim 4.63)
	(envelope-from <henrik@levkowetz.com>)
	id 1GsVDb-0004Fr-TB; Fri, 08 Dec 2006 03:12:09 +0100
Message-ID: <4578C9F7.30705@levkowetz.com>
Date: Fri, 08 Dec 2006 03:12:07 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Thunderbird 1.5.0.8 (Macintosh/20061025)
MIME-Version: 1.0
To: Arunkumar Sivaraman <asivaraman@airvana.com>
Subject: Re: [Mip4] MIP NAT Traversal Question
References: <653F3CF58193744C9DE59C217C072B58A06B52@nilgiri.india.wirelessworld.airvananet.com>
	<45783A56.8040505@levkowetz.com>
	<653F3CF58193744C9DE59C217C072B5883BA7E@nilgiri.india.wirelessworld.airvananet.com>
In-Reply-To: <653F3CF58193744C9DE59C217C072B5883BA7E@nilgiri.india.wirelessworld.airvananet.com>
X-Enigmail-Version: 0.94.1.2
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: asivaraman@airvana.com, mip4@ietf.org,
	henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on shiraz.levkowetz.com);
	SAEximRunCond expanded to false
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Cc: Mobile IPv4 Mailing List <mip4@ietf.org>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0520654893=="
Errors-To: mip4-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============0520654893==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig41E6494B40F909B6018CB9DE"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig41E6494B40F909B6018CB9DE
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi Arun,

on 2006-12-07 18:59 Arunkumar Sivaraman said the following:
> Let me probably restate my question.
>=20
> If during initial reg. req. the HA has assented for UDP tunneling and
> for that particular session reg. revoc. has been negotiated, then
> when the actual reg. revocation has to be sent to the FA, does the HA
> put the foreign domain address in the reg. revoc. pkt as the private
> address of the FA or does it still put the public ip address of the
> NAT router, behind which the FA resides.
>=20
> RFC 3543 states foregin domain address to be foreign's agent IP
> address.

Ah.  Now this actually becomes interesting, and not something already
obviously covered in existing documents.

My thought would be that the destination IP address has to be the
effective CoA (in order for the registration revocation message to
reach the FA at all), but the Foreign Domain Address must be the
CoA indicated by the FA in as CoA in the Registration Request message,
so that the FA can retrieve the proper context for the revocation.

Do you mind if I send this reply to the MIP4 list too?

	Henrik



--------------enig41E6494B40F909B6018CB9DE
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iD8DBQFFeMn3eVhrtTJkXCMRAhLNAJ9s0dRkmnvXq1kESKXtql7pfjD/LwCbBkA8
MNoBaGLYQu3+Z+j6uZIGD8A=
=0jLf
-----END PGP SIGNATURE-----

--------------enig41E6494B40F909B6018CB9DE--


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

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

--===============0520654893==--






om>
User-Agent: Thunderbird 1.5.0.8 (Macintosh/20061025)
MIME-Version: 1.0
To: Arunkumar Sivaraman <asivaraman@airvana.com>
Subject: Re: [Mip4] MIP NAT Traversal Question
References: <653F3CF58193744C9DE59C217C072B58A06B52@nilgiri.india.wirelessworld.airvananet.com>
	<45783A56.8040505@levkowetz.com>
	<653F3CF58193744C9DE59C217C072B5883BA7E@nilgiri.india.wirelessworld.airvananet.com>
In-Reply-To: <653F3CF58193744C9DE59C217C072B5883BA7E@nilgiri.india.wirelessworld.airvananet.com>
X-Enigmail-Version: 0.94.1.2
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: asivaraman@airvana.com, mip4@ietf.org,
	henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on shiraz.levkowetz.com);
	SAEximRunCond expanded to false
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Cc: Mobile IPv4 Mailing List <mip4@ietf.org>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0520654893=="
Errors-To: mip4-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============0520654893==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig41E6494B40F909B6018CB9DE"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig41E6494B40F909B6018CB9DE
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi Arun,

on 2006-12-07 18:59 Arunkumar Sivaraman said the following:
> Let me probably restate my question.
>=20
> If during initial reg. req. the HA has assented for UDP tunneling and
> for that particular session reg. revoc. has been negotiated, then
> when the actual reg. revocation has to be sent to the FA, does the HA
> put the foreign domain address in the reg. revoc. pkt as the private
> address of the FA or does it still put the public ip address of the
> NAT router, behind which the FA resides.
>=20
> RFC 3543 states foregin domain address to be foreign's agent IP
> address.

Ah.  Now this actually becomes interesting, and not something already
obviously covered in existing documents.

My thought would be that the destination IP address has to be the
effective CoA (in order for the registration revocation message to
reach the FA at all), but the Foreign Domain Address must be the
CoA indicated by the FA in as CoA in the Registration Request message,
so that the FA can retrieve the proper context for the revocation.

Do you mind if I send this reply to the MIP4 list too?

	Henrik



--------------enig41E6494B40F909B6018CB9DE
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iD8DBQFFeMn3eVhrtTJkXCMRAhLNAJ9s0dRkmnvXq1kESKXtql7pfjD/LwCbBkA8
MNoBaGLYQu3+Z+j6uZIGD8A=
=0jLf
-----END PGP SIGNATURE-----

--------------enig41E6494B40F909B6018CB9DE--


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

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

--===============0520654893==--






From mip4-bounces@ietf.org Fri Dec 08 18:08:20 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GsopA-0006Z3-Nq; Fri, 08 Dec 2006 18:08:12 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gshr2-0007tY-Mh
	for mip4@ietf.org; Fri, 08 Dec 2006 10:41:40 -0500
Received: from grid.lrg.ufsc.br ([150.162.63.19])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GshqQ-00076Y-Ev
	for mip4@ietf.org; Fri, 08 Dec 2006 10:41:06 -0500
Received: from localhost.grid.lrg.ufsc.br (localhost [127.0.0.1])
	by grid.lrg.ufsc.br (Postfix) with ESMTP id CF35412A233;
	Fri,  8 Dec 2006 11:26:57 -0200 (BRST)
X-Original-To: mycolleagues@grid.lrg.ufsc.br
Delivered-To: mycolleagues@grid.lrg.ufsc.br
Received: from smtp.tssg.org (tssg.wit.ie [193.1.185.11])
	by grid.lrg.ufsc.br (Postfix) with ESMTP id 17530128B6C
	for <mycolleagues@grid.lrg.ufsc.br>;
	Fri,  8 Dec 2006 10:30:04 -0200 (BRST)
Received: from [10.37.2.102] (unknown [10.37.2.102])
	by smtp.tssg.org (Postfix) with ESMTP id EC2C963CEC;
	Fri,  8 Dec 2006 13:21:57 +0000 (GMT)
Message-ID: <457966E9.6040909@tssg.org>
Date: Fri, 08 Dec 2006 13:21:45 +0000
From: Tom Pfeifer <tpfeifer@tssg.org>
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US;
	rv:1.8.0.8) Gecko/20061030 SeaMonkey/1.0.6
MIME-Version: 1.0
To: mycolleagues@grid.lrg.ufsc.br
X-Mailman-Approved-At: Fri, 08 Dec 2006 10:50:17 -0200
X-BeenThere: mycolleagues@grid.lrg.ufsc.br
X-Mailman-Version: 2.1.8
Precedence: list
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 36b1f8810cb91289d885dc8ab4fc8172
X-Mailman-Approved-At: Fri, 08 Dec 2006 18:08:11 -0500
Cc: 
Subject: [Mip4] [mycolleagues] CfP: MUCS2007: Management of Ubiquitous
	Communications and Services
X-BeenThere: mip4@ietf.org
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Call for Papers
+--------------------------------------------------------------------------+
                         4th International Workshop on
           Management of Ubiquitous Communications and Services
                                 www.MUCS2007.org

as part of the 10th IFIP/IEEE Symposium of Integrated Management, IM 2007
                                 www.im2007.org
                                Munich, Germany

                         Submission: January 24th 2007
                            Workshop: May 25th 2007
+--------------------------------------------------------------------------+

Scope of the MUCS Workshop

Ubiquitous and Pervasive Communications, as evidenced in pervasive
computing and smart space applications present significant management
challenges for successful delivery of highly adaptive services across
heterogeneous networks, middleware, applications and devices.

Today's management systems are unable to cope with the complexity,
heterogeneity and automation required by the pervasive computing vision. New
paradigms, models and technology need to be developed to allow computer
systems manage themselves in accordance with high-level guidance from human=
s.
This workshop seeks to explore the theoretic, technological and
organisational challenges in managing ubiquitous communications and
application services.

The workshop provides a single-track scientific programme containing a blend
of keynote presentations from leaders in the research of communications and
services management systems, peer-reviewed papers and a small selection of
invited presentations. The goal of the workshop is to investigate the state
of the art in managing ubiquitous communications and services from a broad
perspective.

Submissions are invited for original, and previously unpublished research
in all aspects of management techniques in ubiquitous communications.


Topics

* Management of Smart Spaces and Applications (Smart Home/Office etc)
* Context Aware Management and Configuration
* Policy Based Management
* Communication & Systems Management
* Wireless and Fixed Network Integrated Management
* Adaptive Service and Network Management
* Security, Privacy, and Trust Management in Ubiquitous Communications
* Management and Control of Mobile Ad-hoc and Wireless Sensor Networks
* Content Oriented Network & Service Management
* Distributed Management & Collaborative Governance
* Context Identification, Retrieval, Prediction and Management
* Service and Network Management for Optimised Personalisation
* Managing Collaborative Ubicomp Applications
* Provisioning and Maintenance of Quality of Service in Ubicomp environments
* Knowledge Representation Techniques and Ontologies
   for Distributed Management Services
* User Interaction with Managing UbiComp Systems
* Bio-inspired management approach


Paper Submission

Paper submissions must present original, unpublished research or experience=
s.
Late-breaking advances and work-in-progress reports from ongoing research
are also encouraged to be submitted to MUCS 2007. Authors are requested to
submit either long papers or short papers (work-in-progress reports),
strictly in 10 point following IEEE conference style:
* Long papers (up to 10 single-spaced two-column pages, including figures,
                tables, references and annexes)
* Short papers describing work-in-progress (up to 4 pages, including
                figures, tables, references and annexes)

Submissions exceeding the above mentioned paper size will not be reviewed
and returned to the authors. Please see the workshop website for detailed
instructions on http://www.mucs2007.org/

Papers are to be submitted via the EDAS conference management system:
http://www.edas.info/newPaper.php?c=3D5092&submit=3D0&


Proceedings

The proceedings of MUCS 2007 will be published in the Multicon Lecture Notes
with ISBN and the IEEE Explorer (confirmation pending).


Important Deadlines

* Submission: January 24th 2007
* Notification: March 26th 2007
* Camera ready: April 9th 2007
* Workshop: May 25th 2007


Committee

Chair:           Tom Pfeifer  (WIT, Ireland)
Programme Committee Chairs:
                  John Strassner (Motorola Labs, USA)
                  Simon Dobson (University College Dublin, Ireland)
Steering Committee:
                  Sven van der Meer (TSSG, Ireland)
                  Vincent Wade (Trinity College Dublin, Ireland)
                  Dirk Pesch (Cork Institute of Technology, Ireland)
Publication Chair:
                  Brendan Jennings (WIT, Ireland)

Technical Programme Committee:

Nazim Agoulmine, Universit=E9 d'Evry-Val d'Essonne, France
Mark Burgess, Oslo University College, Norway
Owen Conlan, Trinity College Dublin, Ireland
Lorcan Coyle, University College Dublin, Ireland
Kieran Delaney, Tyndall Institute, Ireland
Dominique Gaiti, Universit=E9 de Technologies de Troyes, France
Hani Hagras, University of Essex, UK
Markus Huebscher, Imperial College London, UK
Jadwiga Indulska, University of Queensland, Australia
Martin Klepal, Cork Institute of Technology, Ireland
David Lewis, Trinity College Dublin, Ireland
Kevin Curran, University of Ulster, UK
M=EDche=E1l =D3 Foghl=FA, Waterford Institute of Technology, Ireland
Fergus O'Reilly, Cork Institute of Technology, Ireland
Declan O'Sullivan, Trinity College Dublin, Ireland
Kay Uwe R=F6mer, ETH Zurich, Switzerland
Albrecht Schmidt, Ludwig-Maximilians-Universit=E4t M=FCnchen, Germany
Joan Serrat, Universitat Polit=E8cnica de Catalunya, Spain
Roy Sterritt, University of Ulster, UK
Michael Smirnov, Fraunhofer FOKUS, Germany
Yacine Ghamri-Doudane, Institut d'Informatique d'Entreprise, France
+--------------------------------------------------------------------------+
_______________________________________________
mycolleagues mailing list
mycolleagues@grid.lrg.ufsc.br
http://grid.lrg.ufsc.br/mailman/listinfo/mycolleagues

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Mon Dec 11 10:25:29 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gtn1x-0002uq-9x; Mon, 11 Dec 2006 10:25:25 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gtn1w-0002q3-0t
	for mip4@ietf.org; Mon, 11 Dec 2006 10:25:24 -0500
Received: from mail119.messagelabs.com ([216.82.241.179])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1Gtn1u-0005jj-PU
	for mip4@ietf.org; Mon, 11 Dec 2006 10:25:24 -0500
X-VirusChecked: Checked
X-Env-Sender: pete.mccann@motorola.com
X-Msg-Ref: server-14.tower-119.messagelabs.com!1165850721!16810588!1
X-StarScan-Version: 5.5.10.7; banners=-,-,-
X-Originating-IP: [129.188.136.8]
Received: (qmail 2975 invoked from network); 11 Dec 2006 15:25:21 -0000
Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8)
	by server-14.tower-119.messagelabs.com with SMTP;
	11 Dec 2006 15:25:21 -0000
Received: from az33exr02.mot.com ([10.64.251.232])
	by motgate8.mot.com (8.12.11/Motorola) with ESMTP id kBBFPHns010709
	for <mip4@ietf.org>; Mon, 11 Dec 2006 08:25:21 -0700 (MST)
Received: from de01exm67.ds.mot.com (de01exm67.am.mot.com [10.176.8.18])
	by az33exr02.mot.com (8.13.1/8.13.0) with ESMTP id kBBFPESP027357
	for <mip4@ietf.org>; Mon, 11 Dec 2006 09:25:16 -0600 (CST)
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
Subject: RE: [Mip4] WGLC: draft-ietf-mip4-mobike-connectivity-01.txt
Date: Mon, 11 Dec 2006 10:23:03 -0500
Message-ID: <BE4B07D4197BF34EB3B753DD34EBCD13012D8974@de01exm67.ds.mot.com>
In-Reply-To: <BE4B07D4197BF34EB3B753DD34EBCD130125E6C2@de01exm67.ds.mot.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip4] WGLC: draft-ietf-mip4-mobike-connectivity-01.txt
Thread-Index: AccTCmsX+3AuBSnxSX+BjwQKcbmG8QKLaY/Q
From: "McCann Peter-A001034" <pete.mccann@motorola.com>
To: <mip4@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Reminder: this WGLC ends tomorrow at midnight.  So far we
have gotten minimal feedback.  More support will be required
to advance this to the IESG.

-Pete

McCann Peter-A001034 wrote:
> This message announces a (second) WG last call on:
>=20
>    "Secure Connectivity and Mobility using Mobile IPv4 and MOBIKE"
>    draft-ietf-mip4-mobike-connectivity-01.txt
>=20
> The last call will conclude at 24:00 UTC on Tuesday, 12 December 2006.
>=20
> "Secure Connectivity and Mobility using Mobile IPv4 and MOBIKE"
> describes
> a solution using Mobile IPv4 and mobility extensions to IKEv2 (MOBIKE)
> to
> provide secure connectivity and mobility.
>=20
> A URL for this internet draft is:
>=20
>
http://www.ietf.org/internet-drafts/draft-ietf-mip4-mobike-connectivity-
> 01.txt
>=20
>=20
> Please respond to this WG last call:
>=20
>=20
> * If you have no comments on the draft, and support its advancement,
>   simply respond with a line containing something like
>=20
>=20
>    "I support the advancement of this document to the IESG with a
>     request for publication as proposed standard."
>=20
>=20
>   If you have comments, please use a line similar to the one above,
>   and supplement this with your comments.
>=20
>=20
>=20
> * If you *don't* support its advancement, respond with a line
>   containing something like the following, supplemented by your
> comments -=20
>=20
>=20
>    "I don't support the advancement of this document to the IESG with
>     a request for publication as proposed standard, for the following
>     reasons:"
>    ...
>=20
>=20
>=20
>=20
>     Pete & Henrik


-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Mon Dec 11 10:32:48 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gtn96-0006iw-0q; Mon, 11 Dec 2006 10:32:48 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GtPht-0000Ui-JJ
	for mip4@ietf.org; Sun, 10 Dec 2006 09:31:09 -0500
Received: from grid.lrg.ufsc.br ([150.162.63.19])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GtPhG-0007sN-FR
	for mip4@ietf.org; Sun, 10 Dec 2006 09:30:33 -0500
Received: from localhost.grid.lrg.ufsc.br (localhost [127.0.0.1])
	by grid.lrg.ufsc.br (Postfix) with ESMTP id 7F59E12A569;
	Sun, 10 Dec 2006 11:36:53 -0200 (BRST)
X-Original-To: mycolleagues@grid.lrg.ufsc.br
Delivered-To: mycolleagues@grid.lrg.ufsc.br
Received: from cingular.com (extmail09.cingular.com [170.35.225.24])
	by grid.lrg.ufsc.br (Postfix) with ESMTP id 9E4421282C1
	for <mycolleagues@grid.lrg.ufsc.br>;
	Mon,  4 Dec 2006 22:25:07 -0200 (BRST)
Received: from ([10.148.14.29])
	by extmail09.cingular.com with ESMTP  id KP-VYGZ6.91277492;
	Mon, 04 Dec 2006 20:16:18 -0500
Received: from BD01XSMTP001.US.Cingular.Net ([135.214.27.36]) by
	TD02XSMTP007.US.Cingular.Net with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 4 Dec 2006 19:16:18 -0600
Received: from BD01MSXMB021.US.Cingular.Net ([10.9.6.237]) by
	BD01XSMTP001.US.Cingular.Net with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 4 Dec 2006 17:16:13 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 4 Dec 2006 17:16:13 -0800
Message-ID: <F84134D60178C848888036FD4B66992001DA686F@BD01MSXMB021.US.Cingular.Net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: CFP: 4th MOBILITY CONFERENCE 2007
Thread-Index: AccYCu6mVxuDyyhhSEClDAyO1fymJg==
To: <mycolleagues@grid.lrg.ufsc.br>
X-OriginalArrivalTime: 05 Dec 2006 01:16:13.0536 (UTC)
	FILETIME=[F492F600:01C7180A]
From: "Bari, Farooq" <farooq.bari@cingular.com>
X-Mailman-Approved-At: Sun, 10 Dec 2006 09:21:07 -0200
X-BeenThere: mycolleagues@grid.lrg.ufsc.br
X-Mailman-Version: 2.1.8
Precedence: list
Content-Type: multipart/mixed; boundary="===============1202936712=="
X-Spam-Score: 1.8 (+)
X-Scan-Signature: c07eeb7900970a16fe4056cc74ae9ce2
X-Mailman-Approved-At: Mon, 11 Dec 2006 10:32:46 -0500
Cc: 
Subject: [Mip4] [mycolleagues] CFP: 4th MOBILITY CONFERENCE 2007
X-BeenThere: mip4@ietf.org
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1202936712==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7180A.F46C7FBC"

This is a multi-part message in MIME format.

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

Call for Papers
4th MOBILITY CONFERENCE 2007
An International Conference on Mobile Technology, Applications and
Systems=20
12-14 September 2007 Singapore
=20
Organized by:
The Singapore Chapter Association of Computer Machinery (ACM) SIG Mobile
& Mixed Reality Lab National University of Singapore
=20
In Co-operation with: ACM SIG MOBILE
=20
www.mobilityconference.org <http://www.mobilityconference.org/>=20
=20
=20
Mobility Conference & Exhibition is a three (3) day event comprising of
keynote speeches by both leading researchers and industrial experts,
focused symposiums, technical oral presentations and updates by
industrial presenters. This event provides a platform to introduce new
mobile technologies that would shape the next generation of mobile
systems & technology platforms. We hope to be able to achieve the
following goals:
=20
1. Promotes understanding and interaction among players in the
value-chain necessary for the delivery of total mobility solutions.
2. Facilitates discussions, encourage the formulation and adoption of
standards and "open" interfaces to enable rapid development, testing and
deployment of mobility solutions.
3. Encourages exchange and sharing of knowledge and ideas to boost
growth in the mobility industry.
=20
Our Keynote Sessions
There will be renowned keynote speakers each day, providing strategic
updates in the mobile industry. Topics will cover issues of
technologies/standards, applications and different mobile devices.
=20
Oral Technical Presentations
The technical tracks provide high-level research information about the
next generation systems, latest operating systems, software development
platforms, networking technologies and mobile device capabilities.
=20
Industrial Presentations
These are technology-specific "how-to" sessions for developers and
system integrators. The industrial tracks cover areas including Palm OS,
Windows, Java and Symbian application development environments, network
integration to a mobile (GPRS and 802.11 wireless LAN) environment, and
working with specific mobile-device platforms.
=20
Technical Paper Submission
=20
Authors are to submit their full papers by the 2 April 2007 complying to
the ACM Digital Library standards. Each paper should not exceed more
than 8 pages inclusive of diagrams and graphs. Participants please
register electronically via the conference website:
=20
www.mobilityconference.org
=20
Paper Submission Deadline:       30 April 2007
Notification of Acceptance:      04 June 2007
Early Bird Deadline:             09 July 2007
=20
This conference accepts full papers immediately. All paper submissions
are peer reviewed by the technical programme committee. Accepted work
must be presented by one of the authors. The full conference papers will
be published and indexed in ACM Digital Library and EI. Authors are now
invited to submit their full papers in the topics listed below:
=20
1.         Mobile Computing
2.         Mobile Applications
3.         Mobile Internet; m-Business: m-office, m-commerce, m-payment,
m-banking
4.         Mobile System Platforms, Mobile OS, User Interface and Mobile
Devices
5.         Wireless and Mobile Networks: Wireless Personal Area
Networking; Wireless Home LAN; Wi-Fi; WLAN
6.         3G/4G/UMTS/IMT2000
7.         UWB/Bluetooth
8.         Mobile Security: Access; Data; Device security
9.         Location Based Services
10.        Resource Management
11.        Mobile Agents
12.        Wireless Communications Technology
13.        Mobile System Performance
14.        Standards and Interoperability
15.        Mobility Management
16.        HCI and Multi-modal Interaction with Mobile Devices
17.        Machine-to-Machine Communications
18.        Mobile Gaming
19.        Ubiquitous Computing for Mobile Entertainment
20.        Human Factors for Mobile Collaboration and Interaction
=20
Journal Publication
The top papers will be selected for publication in the official journal:
International Journal of Ad Hoc and Ubiquitous Computing. The selection
of the papers for the journal will be made by the technical review
committee and shall be subjected to the final approval of the journal
editorial boards acceptance.
=20
Industrial Presentation
All industry submissions will NOT be peer reviewed.  Accepted submission
would not be published in the conference proceedings nor indexed.
Participant will only need to submit a short write up of no more than
500 words. Please state clearly the title of the presentation. Attached
a short resume of the presenter along with the submission. Submissions
deadline for Mobility Conference 2007 is 2 April 2007. Submissions
should be sent via email to Ivan Boo, Mobility Conference Manager at
this email address: ivan@inmeet.com.sg
=20
MOBILITY CONFERENCE MANAGER
C/O Integrated Meetings Specialist Pte Ltd Block 998, Toa Payoh North
#07-18 Singapore 318993=20
Tel: (65) 6356 4727
Fax: (65) 6356 7471
Email: mobility@inmeet.com.sg

=20


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
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"country-region"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"place"/>
<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"PlaceType"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"PlaceName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Courier;
	panose-1:2 7 4 9 2 2 5 2 4 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
h4
	{margin-top:12.0pt;
	margin-right:0in;
	margin-bottom:3.0pt;
	margin-left:0in;
	page-break-after:avoid;
	font-size:12.0pt;
	font-family:"Times New Roman";}
h6
	{margin-top:12.0pt;
	margin-right:0in;
	margin-bottom:3.0pt;
	margin-left:0in;
	font-size:11.0pt;
	font-family:"Times New Roman";
	font-weight:normal;
	font-style:italic;}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
pre
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:Courier;
	color:black;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:black;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1><pre><font size=3D2 color=3Dblack =
face=3DCourier><span
style=3D'font-size:10.0pt'>Call for =
Papers<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3DCourier><span =
style=3D'font-size:10.0pt'>4th MOBILITY CONFERENCE =
2007<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3DCourier><span =
style=3D'font-size:10.0pt'>An International Conference on <st1:place
w:st=3D"on">Mobile</st1:place> Technology, Applications and Systems =
<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3DCourier><span =
style=3D'font-size:10.0pt'>12-14 September 2007 <st1:country-region
w:st=3D"on"><st1:place =
w:st=3D"on">Singapore</st1:place></st1:country-region><o:p></o:p></span><=
/font></pre><pre><font
size=3D2 color=3Dblack face=3DCourier><span style=3D'font-size:10.0pt'> =
<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3DCourier><span =
style=3D'font-size:10.0pt'>Organized =
by:<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3DCourier><span =
style=3D'font-size:10.0pt'>The <st1:country-region
w:st=3D"on">Singapore</st1:country-region> Chapter Association of =
Computer Machinery (ACM) SIG <st1:City
w:st=3D"on">Mobile</st1:City> &amp; Mixed <st1:PlaceName =
w:st=3D"on">Reality</st1:PlaceName> <st1:PlaceName
w:st=3D"on">Lab</st1:PlaceName> <st1:PlaceName =
w:st=3D"on">National</st1:PlaceName> <st1:PlaceType
w:st=3D"on">University</st1:PlaceType> of <st1:country-region =
w:st=3D"on"><st1:place
 =
w:st=3D"on">Singapore</st1:place></st1:country-region><o:p></o:p></span><=
/font></pre><pre><font
size=3D2 color=3Dblack face=3DCourier><span style=3D'font-size:10.0pt'> =
<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3DCourier><span =
style=3D'font-size:10.0pt'>In Co-operation with: ACM SIG <st1:City
w:st=3D"on"><st1:place =
w:st=3D"on">MOBILE</st1:place></st1:City><o:p></o:p></span></font></pre><=
pre><font
size=3D2 color=3Dblack face=3DCourier><span style=3D'font-size:10.0pt'> =
<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3DCourier><span =
style=3D'font-size:10.0pt'><a
href=3D"http://www.mobilityconference.org/">www.mobilityconference.org</a=
><o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3DCourier><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 color=3Dblack face=3DCourier><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 color=3Dblack face=3DCourier><span =
style=3D'font-size:10.0pt'>Mobility Conference &amp; Exhibition is a =
three (3) day event comprising of keynote speeches by both leading =
researchers and industrial experts, focused symposiums, technical oral =
presentations and updates by industrial presenters. This event provides =
a platform to introduce new mobile technologies that would shape the =
next generation of mobile systems &amp; technology platforms. We hope to =
be able to achieve the following =
goals:<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3DCourier><span style=3D'font-size:10.0pt'> =
<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3DCourier><span =
style=3D'font-size:10.0pt'>1. Promotes understanding and interaction =
among players in the value-chain necessary for the delivery of total =
mobility solutions.<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3DCourier><span =
style=3D'font-size:10.0pt'>2. Facilitates discussions, encourage the =
formulation and adoption of standards and &quot;open&quot; interfaces to =
enable rapid development, testing and deployment of mobility =
solutions.<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3DCourier><span =
style=3D'font-size:10.0pt'>3. Encourages exchange and sharing of =
knowledge and ideas to boost growth in the mobility =
industry.<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3DCourier><span style=3D'font-size:10.0pt'> =
<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3DCourier><span =
style=3D'font-size:10.0pt'>Our Keynote =
Sessions<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3DCourier><span =
style=3D'font-size:10.0pt'>There will be renowned keynote speakers each =
day, providing strategic updates in the mobile industry. Topics will =
cover issues of technologies/standards, applications and different =
mobile devices.<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3DCourier><span style=3D'font-size:10.0pt'> =
<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3DCourier><span =
style=3D'font-size:10.0pt'>Oral Technical =
Presentations<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3DCourier><span =
style=3D'font-size:10.0pt'>The technical tracks provide high-level =
research information about the next generation systems, latest operating =
systems, software development platforms, networking technologies and =
mobile device capabilities.<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3DCourier><span style=3D'font-size:10.0pt'> =
<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3DCourier><span =
style=3D'font-size:10.0pt'>Industrial =
Presentations<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3DCourier><span =
style=3D'font-size:10.0pt'>These are technology-specific =
&quot;how-to&quot; sessions for developers and system integrators. The =
industrial tracks cover areas including Palm OS, Windows, Java and =
Symbian application development environments, network integration to a =
mobile (GPRS and 802.11 wireless LAN) environment, and working with =
specific mobile-device =
platforms.<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3DCourier><span style=3D'font-size:10.0pt'> =
<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3DCourier><span =
style=3D'font-size:10.0pt'>Technical Paper =
Submission<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3DCourier><span style=3D'font-size:10.0pt'> =
<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3DCourier><span =
style=3D'font-size:10.0pt'>Authors are to submit their full papers by =
the 2 April 2007 complying to the ACM Digital Library standards. Each =
paper should not exceed more than 8 pages inclusive of diagrams and =
graphs. Participants please register electronically via the conference =
website:<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3DCourier><span style=3D'font-size:10.0pt'> =
<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3DCourier><span =
style=3D'font-size:10.0pt'>www.mobilityconference.org<o:p></o:p></span></=
font></pre><pre><font
size=3D2 color=3Dblack face=3DCourier><span style=3D'font-size:10.0pt'> =
<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3DCourier><span =
style=3D'font-size:10.0pt'>Paper Submission =
Deadline:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 30 April =
2007<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3DCourier><span =
style=3D'font-size:10.0pt'>Notification of =
Acceptance:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 04 June =
2007<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3DCourier><span =
style=3D'font-size:10.0pt'>Early Bird =
Deadline:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp; 09 July 2007<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3DCourier><span style=3D'font-size:10.0pt'> =
<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3DCourier><span =
style=3D'font-size:10.0pt'>This conference accepts full papers =
immediately. All paper submissions are peer reviewed by the technical =
programme committee. Accepted work must be presented by one of the =
authors. The full conference papers will be published and indexed in ACM =
Digital Library and EI. Authors are now invited to submit their full =
papers in the topics listed =
below:<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3DCourier><span style=3D'font-size:10.0pt'> =
<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3DCourier><span =
style=3D'font-size:10.0pt'>1.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp; Mobile Computing<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3DCourier><span =
style=3D'font-size:10.0pt'>2.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp; Mobile Applications<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3DCourier><span =
style=3D'font-size:10.0pt'>3.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp; Mobile Internet; m-Business: m-office, m-commerce, m-payment, =
m-banking<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3DCourier><span =
style=3D'font-size:10.0pt'>4.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp; Mobile System Platforms, Mobile OS, User Interface and <st1:place
w:st=3D"on">Mobile</st1:place> =
Devices<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3DCourier><span =
style=3D'font-size:10.0pt'>5.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp; Wireless and <st1:City
w:st=3D"on"><st1:place w:st=3D"on">Mobile</st1:place></st1:City> =
Networks: Wireless Personal Area Networking; Wireless Home LAN; Wi-Fi; =
WLAN<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3DCourier><span =
style=3D'font-size:10.0pt'>6.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp; 3G/4G/UMTS/IMT2000<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3DCourier><span =
style=3D'font-size:10.0pt'>7.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp; UWB/Bluetooth<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3DCourier><span =
style=3D'font-size:10.0pt'>8.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp; Mobile Security: Access; Data; Device =
security<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3DCourier><span =
style=3D'font-size:10.0pt'>9.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp; Location Based Services<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3DCourier><span =
style=3D'font-size:10.0pt'>10.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Resource Management<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3DCourier><span =
style=3D'font-size:10.0pt'>11.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Mobile Agents<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3DCourier><span =
style=3D'font-size:10.0pt'>12.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Wireless Communications =
Technology<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3DCourier><span =
style=3D'font-size:10.0pt'>13.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Mobile System Performance<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3DCourier><span =
style=3D'font-size:10.0pt'>14.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Standards and Interoperability<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3DCourier><span =
style=3D'font-size:10.0pt'>15.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Mobility Management<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3DCourier><span =
style=3D'font-size:10.0pt'>16.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
HCI and Multi-modal Interaction with <st1:place
w:st=3D"on">Mobile</st1:place> =
Devices<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3DCourier><span =
style=3D'font-size:10.0pt'>17.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Machine-to-Machine =
Communications<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3DCourier><span =
style=3D'font-size:10.0pt'>18.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Mobile Gaming<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3DCourier><span =
style=3D'font-size:10.0pt'>19.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Ubiquitous Computing for <st1:place
w:st=3D"on">Mobile</st1:place> =
Entertainment<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3DCourier><span =
style=3D'font-size:10.0pt'>20.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Human Factors for <st1:place
w:st=3D"on">Mobile</st1:place> Collaboration and =
Interaction<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3DCourier><span style=3D'font-size:10.0pt'> =
<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3DCourier><span =
style=3D'font-size:10.0pt'>Journal =
Publication<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3DCourier><span =
style=3D'font-size:10.0pt'>The top papers will be selected for =
publication in the official journal: International Journal of Ad Hoc and =
Ubiquitous Computing. The selection of the papers for the journal will =
be made by the technical review committee and shall be subjected to the =
final approval of the journal editorial boards =
acceptance.<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3DCourier><span style=3D'font-size:10.0pt'> =
<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3DCourier><span =
style=3D'font-size:10.0pt'>Industrial =
Presentation<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3DCourier><span =
style=3D'font-size:10.0pt'>All industry submissions will NOT be peer =
reviewed.&nbsp; Accepted submission would not be published in the =
conference proceedings nor indexed. Participant will only need to submit =
a short write up of no more than 500 words. Please state clearly the =
title of the presentation. Attached a short resume of the presenter =
along with the submission. Submissions deadline for Mobility Conference =
2007 is 2 April 2007. Submissions should be sent via email to Ivan Boo, =
Mobility Conference Manager at this email address: <a
href=3D"mailto:ivan@inmeet.com.sg">ivan@inmeet.com.sg</a><o:p></o:p></spa=
n></font></pre><pre><font
size=3D2 color=3Dblack face=3DCourier><span style=3D'font-size:10.0pt'> =
<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3DCourier><span =
style=3D'font-size:10.0pt'>MOBILITY CONFERENCE =
MANAGER<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3DCourier><span =
style=3D'font-size:10.0pt'>C/O Integrated Meetings Specialist Pte Ltd =
Block 998, Toa Payoh North #07-18 <st1:place
w:st=3D"on"><st1:country-region =
w:st=3D"on">Singapore</st1:country-region></st1:place> 318993 =
<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3DCourier><span =
style=3D'font-size:10.0pt'>Tel: (65) 6356 =
4727<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3DCourier><span =
style=3D'font-size:10.0pt'>Fax: (65) 6356 =
7471<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3DCourier><span =
style=3D'font-size:10.0pt'>Email: <a
href=3D"mailto:mobility@inmeet.com.sg">mobility@inmeet.com.sg</a><o:p></o=
:p></span></font></pre>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:black'><o:p>&nbsp;</o:p></span></font></p>=


</div>

</body>

</html>

------_=_NextPart_001_01C7180A.F46C7FBC--

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

_______________________________________________
mycolleagues mailing list
mycolleagues@grid.lrg.ufsc.br
http://grid.lrg.ufsc.br/mailman/listinfo/mycolleagues

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

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

--===============1202936712==--




From mip4-bounces@ietf.org Mon Dec 11 10:32:48 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gtn96-0006jj-8p; Mon, 11 Dec 2006 10:32:48 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gtkx4-0001eQ-1p
	for mip4@ietf.org; Mon, 11 Dec 2006 08:12:14 -0500
Received: from hero.nocdirect.com ([69.73.180.187])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gtkx1-00077p-Ku
	for mip4@ietf.org; Mon, 11 Dec 2006 08:12:14 -0500
Received: from icstconf by hero.nocdirect.com with local (Exim 4.52)
	id 1Gtkws-0006fe-Cq
	for mip4@ietf.org; Mon, 11 Dec 2006 08:12:02 -0500
To: mip4@ietf.org
From: info@icstconferences.org
X-Mailer: PHP/
Message-Id: <E1Gtkws-0006fe-Cq@hero.nocdirect.com>
Date: Mon, 11 Dec 2006 08:12:02 -0500
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - hero.nocdirect.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [32117 619] / [47 12]
X-AntiAbuse: Sender Address Domain - hero.nocdirect.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 995b2e24d23b953c94bac5288c432399
X-Mailman-Approved-At: Mon, 11 Dec 2006 10:32:46 -0500
Subject: [Mip4] CFP-WICON2007: The Third Annual International Wireless
	Internet Conference
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: info@icstconferences.org
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org


We apologize in advance if you receive multiple copies of this CFP.

**********************************************************************
                        ***** WICON 2007 *****
                                                           
      The Third Annual International Wireless Internet Conference        
                                                                    
                          October 22-24, 2007                           
                          Austin, Texas, USA             
                                                                    
                         http://www.wicon.org                 
                                                                    
**********************************************************************

Wireless  Internet  is  quickly  becoming  a  reality  thanks to  fast 
evolution of  various  wireless  access  technologies.  Convergence of 
heterogeneous wireless networks,  enabled by interworking and wireless 
mesh  networking technologies,  further brings  wireless Internet into 
various  application  scenarios.  On  the  other  hand,  new  wireless 
Internet architectures,  services,  and solutions are still desired in 
order to achieve the ultimate goal of wireless Internet access anytime 
anywhere.

The Wireless Internet Conference  (WICON)  will continue to  provide a 
premier international forum  to discuss novel research results related 
to the emerging Wireless Internet.  The focus of WICON 2007 will be on 
advanced  wireless  access   technologies,   wireless  mesh  networks, 
interworking  of  heterogeneous  networks,  next  generation  wireless 
Internet, and industrial practice methodology.  Given the existence of 
many other conferences  on mobile ad hoc networks and sensor networks, 
papers  that are  oriented  to these  networks  are discouraged unless 
they directly focus on the conference  theme of the Wireless Internet.

WICON 2007 is  soliciting both academic research and industry practice 
papers.  Industry practice papers  must have  at least one author from 
industry   and   should  describe  interesting  technical  aspects  of 
industrial  applications,  prototypes,   experiences,  and  standards; 
performance and design details are encouraged,  whereas papers focused 
on marketing or product information  will not  be accepted.  Topics of 
interest include, but are not limited to, the following:

Wireless access technologies:
=============================
* Wireless LANs, WiMedia, WiMAX, Bluetooth
* 3G and 4G cellular networks

Wireless multi-hop mesh networks:
=================================
* New mesh network architecture
* WiFi, UWB, Bluetooth wireless mesh networks
* Scalable MAC and routing protocols
* Multi-radio and multi-channel mesh networks
* QoS, security, and mobility management

Convergence of various wireless technologies:
=============================================
* Roaming, Interworking, and UMA
* Cognitive radios and programmable radios for wireless Internet
* Adaptive transport layer protocols

Testbed and measurements:
=========================
* Protocol design, implementation, and testbed setup of wireless 
  Internet
* Measurement of wireless Internet and performance analysis

Next generation wireless Internet:
==================================
* Novel wireless Internet architecture
* New services and applications
* New algorithms for scalable, reliable, and high speed wireless 
  Internet


SUBMISSION INSTRUCTIONS:
======================== 

Papers will be submitted by electronic submission through COCUS system: 
http://cocus.create-net.it.  The page limit is 10 pages  in IEEE double 
column format with fonts not smaller than 10 points.


IMPORTANT DATES:
================

Submission deadline        :                May 30, 2007
Notification of acceptance :               July 22, 2007
Camera-ready version       :           September 1, 2007


Selected papers  will be published  on a special issue  of  ACM Mobile 
Networks and Applications (MONET).


WORKSHOPS:
=========== 

Proposals  for  workshops  should be  submitted to  the Workshop Chair 
directly at yry@cs.yale.edu.  Evaluation of workshop proposals will be 
based on the expertise  and experience of the instructors,  and on the 
relevance of the subject matter.


PANELS:
=======

Proposals  for panel discussions  that  focus on  the  next generation 
wireless Internet  are encouraged.  Potential panel organizers  should 
submit a panel proposal to the Panel Chair directly at 
sujata.banerjee@hp.com.


Posters/Demos:
============== 

The conference  will  include  a poster/demo  session  that highlights 
experiments   and    testbeds   that    demonstrate   the   successful 
implementation of recent  or  on-going  research work.  Please contact 
Poster/Demo Chair directly at shakkott@ece.utexas.edu


Organization Committee:
=======================

 General Co-Chairs:
 ------------------
 Lili Qiu                          University of Texas-Austin, USA
 Andras Valko                      Ericsson Research, Hungary

 Technical Program Co-Chairs:
 ----------------------------
 Xudong Wang                       Kiyon, Inc, USA
 Karoly Farkas                     ETH Zurich, Switzerland

 Steering Committee Chair:
 -------------------------
 Imrich Chlamtac                   Create-Net, Italy

 Panel Chair:
 ------------
 Sujata Banerjee                   HP Labs, USA

 Publicity Chair:
 ----------------
 Linda Xie                         UNC-Charlotte, USA

 Workshop Chair:
 ---------------
 Richard Yang                      Yale University

 Local Arrangement Chair:
 ------------------------
 Sriram Vishwanath                 University of Texas-Austin, USA

 Publication Chair:
 ------------------
 Xin Liu                           University of California-Davis, USA

 Poster/Demo Chair:
 ------------------
 Sanjay Shakkottai                 University of Texas-Austin, USA

 Conference Chair:
 -----------------
 Kitti H. Kovacs                   ICST

For more information about the conference, see http://www.wicon.org/



--------------------------------------------------
You are reading ICST conference newsletter. To report any kind of abuse, please contact admin at icst.org.
To unsubscribe, please visit the following page: http://icstconferences.org/cmc/unsubscribe.php?p=sioqydapnz and enter your email address.

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Mon Dec 11 14:08:23 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GtqVf-0003fl-Le; Mon, 11 Dec 2006 14:08:19 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GtqVd-0003cT-Ts
	for mip4@ietf.org; Mon, 11 Dec 2006 14:08:17 -0500
Received: from mail2.azairenet.com ([66.92.223.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GtqVc-0004Xn-3D
	for mip4@ietf.org; Mon, 11 Dec 2006 14:08:17 -0500
Received: from [127.0.0.1] ([66.92.223.6]) by mail2.azairenet.com over TLS
	secured channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 11 Dec 2006 11:08:04 -0800
Message-ID: <457DAC9A.1040501@azairenet.com>
Date: Mon, 11 Dec 2006 11:08:10 -0800
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: Jouni Korhonen <jouni.korhonen@teliasonera.com>
Subject: Re: [Mip4] WGLC: draft-ietf-mip4-mobike-connectivity-01.txt
References: <BE4B07D4197BF34EB3B753DD34EBCD130125E6C2@de01exm67.ds.mot.com>
	<456CA2B2.9010708@azairenet.com> <456D6775.4050905@teliasonera.com>
In-Reply-To: <456D6775.4050905@teliasonera.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 11 Dec 2006 19:08:04.0374 (UTC)
	FILETIME=[AF4C9360:01C71D57]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Cc: mip4@ietf.org, McCann Peter-A001034 <pete.mccann@motorola.com>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Jouni Korhonen wrote:
> Hi Vijay,
> 
> I think it was me who asked for this appendix. I'm happy to have it 
> there now. I'm not sure whether it makes any additional value to mention 
> in appendix A that the operator trusted network could also be 
> implemented as the home link from MNs. For certain wireless technologies 
> this would give a nice optimization.

We can add the following sentence at the end of the
appendix.

    When the mobile node is attached to the trusted access network, it
    can either by attached to a foreign link in the trusted network or to
    the home link directly.  This document does not impose any
    restrictions.

Vijay


> Apart from the above "I support the advancement of this document to the 
> IESG with a request for publication as proposed standard."
> 
> Cheers,
>     Jouni
> 
> Vijay Devarapalli kirjoitti:
>> just wanted to point out that the only major change
>> since the last WG last call was to add a new section
>> in the Appendix to show how the solution can be
>> applied to a mobile operator network.
>>
>> Vijay
>>
>> McCann Peter-A001034 wrote:
>>> This message announces a (second) WG last call on:
>>>
>>>    "Secure Connectivity and Mobility using Mobile IPv4 and MOBIKE"
>>>    draft-ietf-mip4-mobike-connectivity-01.txt
>>>
>>> The last call will conclude at 24:00 UTC on Tuesday, 12 December 2006.
>>>
>>> "Secure Connectivity and Mobility using Mobile IPv4 and MOBIKE"
>>> describes a solution using Mobile IPv4 and mobility extensions to 
>>> IKEv2 (MOBIKE)
>>> to provide secure connectivity and mobility.
>>>
>>> A URL for this internet draft is:
>>>
>>> http://www.ietf.org/internet-drafts/draft-ietf-mip4-mobike-connectivity-
>>> 01.txt
>>>
>>>
>>> Please respond to this WG last call:
>>>
>>>
>>> * If you have no comments on the draft, and support its advancement,
>>>   simply respond with a line containing something like
>>>
>>>
>>>    "I support the advancement of this document to the IESG with a
>>>     request for publication as proposed standard."
>>>
>>>
>>>   If you have comments, please use a line similar to the one above, and
>>>   supplement this with your comments.
>>>
>>>
>>>
>>> * If you *don't* support its advancement, respond with a line containing
>>>   something like the following, supplemented by your comments -
>>>
>>>
>>>    "I don't support the advancement of this document to the IESG with
>>>     a request for publication as proposed standard, for the following
>>>     reasons:"
>>>    ...
>>>
>>>
>>>
>>>
>>>     Pete & Henrik
>>>
>>
>>


-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Mon Dec 11 20:27:40 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GtwQi-0002no-TF; Mon, 11 Dec 2006 20:27:36 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GtwQh-0002nj-UQ
	for mip4@ietf.org; Mon, 11 Dec 2006 20:27:35 -0500
Received: from smtp.nokia.com ([131.228.20.172] helo=mgw-ext13.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GtwQd-0008Q5-As
	for mip4@ietf.org; Mon, 11 Dec 2006 20:27:35 -0500
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143])
	by mgw-ext13.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	kBC1QoqD029017; Tue, 12 Dec 2006 03:27:06 +0200
Received: from daebh101.NOE.Nokia.com ([10.241.35.111]) by
	esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 12 Dec 2006 03:26:07 +0200
Received: from daebe103.NOE.Nokia.com ([10.241.35.24]) by
	daebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 11 Dec 2006 19:26:04 -0600
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
Subject: RE: [Mip4] WGLC: draft-ietf-mip4-mobike-connectivity-01.txt
Date: Mon, 11 Dec 2006 19:26:03 -0600
Message-ID: <3C33B44F3E969F4D8DE8D578078410C855798E@daebe103.NOE.Nokia.com>
In-Reply-To: <BE4B07D4197BF34EB3B753DD34EBCD13012D8974@de01exm67.ds.mot.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip4] WGLC: draft-ietf-mip4-mobike-connectivity-01.txt
Thread-Index: AccTCmsX+3AuBSnxSX+BjwQKcbmG8QKLaY/QABUQqaA=
From: <rajeev.koodli@nokia.com>
To: <pete.mccann@motorola.com>, <mip4@ietf.org>
X-OriginalArrivalTime: 12 Dec 2006 01:26:04.0462 (UTC)
	FILETIME=[7DAF5CE0:01C71D8C]
X-Nokia-AV: Clean
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 31247fb3be228bb596db9127becad0bc
Cc: 
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org


Hi Pete,

  I support progressing this document to the IESG with a
  request for publication as proposed standard.


-Rajeev


>-----Original Message-----
>From: ext McCann Peter-A001034 [mailto:pete.mccann@motorola.com]=20
>Sent: Monday, December 11, 2006 7:23 AM
>To: mip4@ietf.org
>Subject: RE: [Mip4] WGLC: draft-ietf-mip4-mobike-connectivity-01.txt
>
>Reminder: this WGLC ends tomorrow at midnight.  So far we have=20
>gotten minimal feedback.  More support will be required to=20
>advance this to the IESG.
>
>-Pete
>
>McCann Peter-A001034 wrote:
>> This message announces a (second) WG last call on:
>>=20
>>    "Secure Connectivity and Mobility using Mobile IPv4 and MOBIKE"
>>    draft-ietf-mip4-mobike-connectivity-01.txt
>>=20
>> The last call will conclude at 24:00 UTC on Tuesday, 12=20
>December 2006.
>>=20
>> "Secure Connectivity and Mobility using Mobile IPv4 and MOBIKE"
>> describes
>> a solution using Mobile IPv4 and mobility extensions to=20
>IKEv2 (MOBIKE)=20
>> to provide secure connectivity and mobility.
>>=20
>> A URL for this internet draft is:
>>=20
>>
>http://www.ietf.org/internet-drafts/draft-ietf-mip4-mobike-conn
>ectivity-
>> 01.txt
>>=20
>>=20
>> Please respond to this WG last call:
>>=20
>>=20
>> * If you have no comments on the draft, and support its advancement,
>>   simply respond with a line containing something like
>>=20
>>=20
>>    "I support the advancement of this document to the IESG with a
>>     request for publication as proposed standard."
>>=20
>>=20
>>   If you have comments, please use a line similar to the one above,
>>   and supplement this with your comments.
>>=20
>>=20
>>=20
>> * If you *don't* support its advancement, respond with a line
>>   containing something like the following, supplemented by your=20
>> comments -
>>=20
>>=20
>>    "I don't support the advancement of this document to the IESG with
>>     a request for publication as proposed standard, for the following
>>     reasons:"
>>    ...
>>=20
>>=20
>>=20
>>=20
>>     Pete & Henrik
>
>
>--
>Mip4 mailing list: Mip4@ietf.org
>    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
>     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
>Supplemental site: http://www.mip4.org/
>

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Mon Dec 11 22:19:04 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GtyAT-0001v7-UI; Mon, 11 Dec 2006 22:18:57 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GtyAT-0001tK-8g
	for mip4@ietf.org; Mon, 11 Dec 2006 22:18:57 -0500
Received: from mail2.azairenet.com ([66.92.223.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GtyAS-0005XY-I8
	for mip4@ietf.org; Mon, 11 Dec 2006 22:18:57 -0500
Received: from [127.0.0.1] ([66.92.223.6]) by mail2.azairenet.com over TLS
	secured channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 11 Dec 2006 19:18:44 -0800
Message-ID: <457E1F9E.3000109@azairenet.com>
Date: Mon, 11 Dec 2006 19:18:54 -0800
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: Henrik Levkowetz <henrik@levkowetz.com>
Subject: Re: [Mip4] Charter Update Proposal
References: <45647C27.4040208@levkowetz.com>
In-Reply-To: <45647C27.4040208@levkowetz.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 12 Dec 2006 03:18:44.0903 (UTC)
	FILETIME=[3B38CB70:01C71D9C]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 71f780ffdd80c541d3e75aa5f2710d3d
Cc: mip4-chairs@tools.ietf.org, mip4-ads@tools.ietf.org,
	Mobile IPv4 Mailing List <mip4@ietf.org>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Henrik Levkowetz wrote:
> Hi,
> 
> 
> Both the list and the WG meeting during IETF-67 indicated support for
> adding moving network support and a notification mechanism to the
> charter, so below is a proposal for a charter update.  (The resulting
> charter, if the updates are accepted, are provided as an attachment.)
> 
> We propose to add the following two items to the list of work to
> be done:
> 
>   11. MIPv4 Moving Network Support

Can we call this "MIPv4 Mobile Network Support" or "MIPv4 Network 
Mobility Support"? I don't like the term "Moving Network". :)

Vijay

> 
>   The Network Mobility (nemo) working group deals with the problem of
>   mobility of a whole network, such as might exist inside a vehicle,
>   train, or airplane.  The nemo working group has developed draft
>   specifications for both IPv6 and IPv4 mobile networks.  However, it has
>   been recognized that the IPv4 version of the protocol can be viewed as
>   an extension of the basic Mobile IPv4 protocol, and there is good reason
>   to do this extension in the mip4 working group.  The working group will
>   take on the MIPv4 network mobility internet draft and progress it along
>   the standards track.  In addition, the working group will take up
>   extensions to the basic MIPv4 moving network support in the areas of
>   dynamic prefix assignment and foreign agent support.
> 
> 
>   12. Asynchronous Notification Mechanism
> 
>   In some situations, there is a need for Mobile IPv4 entities, such as
>   the home agent, foreign agent and mobile node to send and receive
>   asynchronous notification events during a mobility session.  The base
>   Mobile IP Specification [RFC3344] does not have a provision for this. A
>   new MIPv4 message pair which would support asynchronous notifications,
>   and a notification model describing how to use these messages has been
>   proposed.  The working group will take on the existing MIPv4
>   notification message draft as a starting point, review and update it as
>   needed, and progress it as a standards track document.  In addition, the
>   working group will also consider defining specific usages of the
>   notification message based on the examples in the current document. 
> 
> We also propose to add the following milestones:
> 
>    Sep 2007	Base MIPv4 Mobile Network Support (Draft Std.) to IESG
>    Nov 2007	MIPv4 Mobile Network Support for FAs (Draft Std.) to IESG
>    Nov 2007	MIPv4 Mobile Network Support Dynamic Address Assignment (Draft Std.) to IESG
> 
> 
> If you have comments or suggestions relating to the suggested update, please
> send them to the list.
> 
> 
> Best Regards,
> 
> 	Henrik and Pete
> 
> 
> 
> 
> ------------------------------------------------------------------------
> 
> Mobility for IPv4 (mip4)
> ------------------------
> 
>  Charter
>  Last Modified: 2006-07-25
> 
>  Current Status: Active Working Group
> 
>  Chair(s):
>      Henrik Levkowetz  <henrik@levkowetz.com>
>      Pete McCann  <mccap@petoni.org>
> 
>  Internet Area Director(s):
>      Jari Arkko  <jari.arkko@piuha.net>
>      Mark Townsley  <townsley@cisco.com>
> 
>  Internet Area Advisor:
>      Jari Arkko  <jari.arkko@piuha.net>
> 
>  Mailing Lists: 
>      General Discussion:mip4@ietf.org
>      To Subscribe:      mip4-request@ietf.org
>          In Body:       subscribe
>      Archive:           http://www.ietf.org/mail-archive/web/mip4/index.html
> 
> Description of Working Group:
> 
> IP mobility support for IPv4 nodes (hosts and routers) is specified in
> RFC3344. RFC 3344 mobility allows a node to continue using its
> "permanent" home address as it moves around the Internet. The Mobile
> IP protocols support transparency above the IP layer, including
> maintenance of active TCP connections and UDP port bindings.  Besides
> the basic Mobile IPv4 (MIPv4) protocols, several other drafts deal
> with concerns such as optimization, security, extensions, AAA support,
> and deployment issues.
> 
> MIPv4 is currently being deployed on a wide basis (e.g., in cdma2000
> networks). The scope of the deployment is on a fairly large scale and
> accordingly, the MIP4 WG will focus on deployment issues and on
> addressing known deficiencies and shortcomings in the protocol that
> have come up as a result of deployment experience. Specifically, the
> working group will complete the work items to facilitate interactions
> with AAA environments, interactions with enterprise environments when
> MIPv4 is used therein, and updating existing protocol specifications
> in accordance with deployment needs and advancing those protocols that
> are on the standards track.
> 
> Work expected to be done by the MIP4 WG as proposed by this charter is
> as follows:
> 
> 1. MIPv4 has been a proposed standard for several years. It has been
> adopted by other standard development organizations and has been
> deployed commercially. One of the next steps for the WG is to advance
> the protocol to draft standard status. As part of advancing base
> Mobile IP specs to DS, the MIPv4 NAI RFC (2794) will be revised to
> reflect implementation experience.
> 
> 2. Work items that are pending from the previous Mobile IP WG, which
> will be completed by the MIP4 WG, are:
> 
> - completion of the MIB for the revised base Mobile IP specification
> (2006bis)
> 
> - regional registration draft.
> 
> 3. The MIP4 WG will also complete the work on MIPv4 interactions in
> VPN scenarios. This work will involve identifying the requirements and
> a solution development for MIPv4 operation in the presence of IPsec
> VPNs.
> 
> 4. Additionally, a proposal has been made for how MOBIKE could work
> together with MIPv4. This proposal does not describe any new protocol,
> but formulates a best current practice for deploying MOBIKE together
> with MIPv4. The working group will adopt and complete this document.
> 
> 5. Some issues have been raised with respect to RFC3519. These will be
> identified and addressed as appropriate, through errata, revision of
> RFC 3519, and/or supplemental documents as needed.
> 
> 6. It has been proposed that the FMIP protocol, which has been
> standardised for MIPv6 in the MIPSHOP working group, should also be
> published as an experimental protocol for MIPv4. A draft for this
> exists. The working group will take up and carry this work forward to
> publication
> 
> 7. An extension to carry generic strings in the Registration Reply
> message has been proposed. The purpose is to supply supplemental
> human-readable information intended to the MN user. The working group
> will complete the specification and applicability statement of such an
> extension.
> 
> 8. RADIUS attributes for MIP4. A set of RADIUS attributes has been
> proposed for MIPv4.
> 
> The working group will first produce a requirements specification,
> describing how the work differs from the requirements in RFC 2977 and
> the functionality provided by RFC 4004 (the MIPv4 Diameter App). The
> reason why this first step is required is that RFC 3127 shows that
> full RFC 2977 functionality can't be provided by even a considerably
> extended RADIUS, so we need to match the requirements to what can be
> done within RADIUS.
> 
> Provided the requirements work finds approval with ADs and RADEXT WG,
> the workgroup will complete the specification of MIPv4 RADIUS
> attributes, solicit feedback from the RADEXT WG, adjust, and submit
> this for publication. Note that the work may require extensions to the
> RADIUS attribute space which will be handled outside the MIP4 WG.
> 
> 9. MIPv4 Extension for Configuration Options.
> 
> Several drafts have proposed extensions to help improve configuration
> of MIPv4 clients. The latest proposal is for a general configuration
> option extension which could carry information such as e.g., DNS
> address and DHCP server address. The working group will take on and
> complete one proposal for a configuration option extension.
> 
> 10. Dual-stack Support
> 
> There have been several proposals for how to enable an IPv6 connection
> over a network that supports Mobile IPv4. A protocol enhancement to
> MIPv4 would allow for IPv6 support in a region where Mobile IPv4 has
> already been implemented and deployed. This would allow a dual stack
> mobile node to maintain IPv6 connectivity when using MIPv4. The
> solution would therefore be applicable only to networks that are
> not deploying Mobile IPv6.
> 
> The working group will take on and complete one proposal for IPv6 over
> Mobile IPv4. This work is restricted to a small protocol extension
> similar to current Mobile IPv4 functionality. Support for advanced
> Mobile IPv6 functionality is strictly outside the scope.
> 
> A problem statement covering both Mobile IPv4 and IPv6 dual-stack
> issues is expected to come out of MIP6 WG, and will not be developed
> in MIP4 WG.
> 
> 
> 11. MIPv4 Moving Network Support
>  
> The Network Mobility (nemo) working group deals with the problem of
> mobility of a whole network, such as might exist inside a vehicle,
> train, or airplane.  The nemo working group has developed draft
> specifications for both IPv6 and IPv4 mobile networks.  However, it has
> been recognized that the IPv4 version of the protocol can be viewed as
> an extension of the basic Mobile IPv4 protocol, and there is good reason
> to do this extension in the mip4 working group.  The working group will
> take on the MIPv4 network mobility internet draft and progress it along
> the standards track.  In addition, the working group will take up
> extensions to the basic MIPv4 moving network support in the areas of
> dynamic prefix assignment and foreign agent support.
> 
> 
> 12. Asynchronous Notification Mechanism
> 
> In some situations, there is a need for Mobile IPv4 entities, such as
> the home agent, foreign agent and mobile node to send and receive
> asynchronous notification events during a mobility session.  The base
> Mobile IP Specification [RFC3344] does not have a provision for this. A
> new MIPv4 message pair which would support asynchronous notifications,
> and a notification model describing how to use these messages has been
> proposed.  The working group will take on the existing MIPv4
> notification message draft as a starting point, review and update it as
> needed, and progress it as a standards track document.  In addition, the
> working group will also consider defining specific usages of the
> notification message based on the examples in the current document. 
> 
> 
> Goals and Milestones:
> 
>    Done         AAA Keys for MIPv4 to IESG 
>    Done         MIPv4 VPN interaction problem statement to IESG 
>    Done         Low latency handover to experimental 
>    Done         Experimental MIPv4 message and extensions draft to IESG 
>    Done         Dynamic Home Agent assignment protocol solution to IESG 
>    Done         Revised MIPv4 Challenge/Response (3012bis) to IESG 
>    Done         Regional registration document to IESG 
>    Jan 2007     MIPv4 Mobike interaction (BCP) to the IESG 
>    Feb 2007     MIPv4 Extension for Config. Options (Proposed Std.) to the IESG 
>    Dec 2006     MIPv4 VPN interaction (BCP) to the IESG 
>    May 2007     RADIUS Extensions for MIPv4 to the RADEXT WG for comment 
>    Jan 2007     Revised MIPv4 specification to IESG for Draft Std. 
>    Dec 2006     Generic Strings for MIPv4 (Proposed Std.) to the IESG 
>    Mar 2007     MIPv4 RADIUS Extensions Requirements to the IESG 
>    Dec 2006     FMIPv4 (Experimental) to the IESG 
>    Sep 2007     RADIUS Extensions for MIPv4 (Proposed Std.) to the IESG 
>    Nov 2007     Revised rfc2794bis (NAI extension) (Draft Std.) to the IESG 
>    Aug 2007     Revised MIB for MIPv4 (Proposed Std.) to IESG 
>    Apr 2007     Dual-stack MIPv4 (Draft Std.) to IESG 
>    Jul 2007	Notification Mechanism (Draft Std.) to IESG
>    Sep 2007	Base MIPv4 Mobile Network Support (Draft Std.) to IESG
>    Nov 2007	MIPv4 Mobile Network Support for FAs (Draft Std.) to IESG
>    Nov 2007	MIPv4 Mobile Network Support Dynamic Address Assignment (Draft Std.) to IESG
> 
> 


-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Mon Dec 11 22:21:55 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GtyDH-0003Gd-Br; Mon, 11 Dec 2006 22:21:51 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GtyDF-0003GT-IM
	for mip4@ietf.org; Mon, 11 Dec 2006 22:21:49 -0500
Received: from mail2.azairenet.com ([66.92.223.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GtyDE-0005xe-06
	for mip4@ietf.org; Mon, 11 Dec 2006 22:21:49 -0500
Received: from [127.0.0.1] ([66.92.223.6]) by mail2.azairenet.com over TLS
	secured channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 11 Dec 2006 19:21:36 -0800
Message-ID: <457E204A.5060609@azairenet.com>
Date: Mon, 11 Dec 2006 19:21:46 -0800
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: mip4@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 12 Dec 2006 03:21:36.0636 (UTC)
	FILETIME=[A1952BC0:01C71D9C]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 88b11fc64c1bfdb4425294ef5374ca07
Cc: "Kent Leung \(kleung\)" <kleung@cisco.com>,
	Alexandru Petrescu <alexandru.petrescu@motorola.com>
Subject: [Mip4] Comments on draft-ietf-nemo-v4-base-01.txt
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Hello,

Here are some comments on draft-ietf-nemo-v4-base-01.txt

Some high level comments

- The terms "subnet", "prefix" and "mobile network" are
used interchangeably in many places. Needs to be fixed
throughout in the document.
- Support for mobile networks using the FA CoA mode is
not explained clearly.
- Running a dynamic routing protocol between the mobile
router and the home agent probably does not work when
FA-CoA mode is used.

> 	  IPv4 Network Mobility (NEMO) Basic Support Protocol

Lets just call it "IPv4 Network Mobility (NEMO) Protocol".
The Basic Support was used for NEMOv6 since there was a
plan to work on route optimization for NEMOv6 and this
was called Extended Support. Its not the same with MIPv4
and IPv4 NEMO.

>    This document describes the support of Mobile Networks, as defined in
>    Mobile IPv4, by the Mobile Router and Home Agent.  

This statement is confusing. What does "as defined in
Mobile IPv4" mean? Perhaps rephrase to

    This document describes a protocol for supporting Mobile Networks
    between a Mobile Router and a Home Agent by extending the Mobile
    IPv4 protocol.

>    This document describes protocol extensions to Mobile IPv4
>    ([RFC3344]) to enable support for Mobile Networks.  A Mobile Network
>    is defined as a network segment or subnet that can change its point
>    of attachment to the routing infrastructure.  Such movement is
>    performed by a Mobile Router, which is the mobility entity that
>    provides connectivity and reachability as well as session continuity
>    for all the nodes in the Mobile Network.  The Mobile Router typically
>    serves as the default gateway for the devices on the Mobile Network.

s/devices/hosts/

>    Mobility for the Mobile Network is supported by the Mobile Router
>    registering the point of attachment to its Home Agent.  This
>    signaling sets up the tunnel between the two entities.  The Mobile
>    Networks (either implicitly configured on the Home Agent or
>    explicitly identified by the Mobile Router) are advertised by the
>    Home Agent for route propagation.  Traffic to and from nodes in the
>    Mobile Network are tunneled by the Home Agent to the Mobile Router,
>    and vice versa.  Though packets from the Mobile Network can be
>    forwarded directly without tunneling when reverse tunneling is not
>    enabled, 

Not just "not enabled" but also "not used".

> reachability is still subject to ingress filtering
>    conditions for the path in this case.

What reachability? I guess you want to say packets can
be dropped if ingress filtering is turned on.

>    This document specifies an additional tunnel between Mobile Router's
>    Home Address and the Home Agent.  This tunnel is encapsulated within
>    the normal tunnel between the Care-of Address (CoA) and Home Agent.
>    In Foreign Agent CoA mode, the tunnel between the Mobile Router and
>    Home Agent is needed to allow the Foreign Agent to direct the
>    decapsulated packet to the proper visiting Mobile Router.  

Lets take an example.

IPv4 hdr (src=HA, dst=FA-CoA)
IPv4 hdr (src=HA, dst=HoA)
IPv4 hdr (src=CN, dst=MNN)
Payload

I borrowed the MNN terminology for NEMOv6 to indicate a
host that is attached to the mobile network. The above
packet format is always used for FA CoA mode, correct?

> However,
>    in Collocated CoA mode, the additional tunnel is not essential and
>    can be eliminated because the Mobile Router is the recipient of the
>    encapsulated packets for the Mobile Network.

This would give us

IPv4 hdr (src=HA, dst=CoA)
IPv4 hdr (src=CN, dst=MNN)
Payload

This gives us a unique case of the packet overhead being
the same for the co-located CoA mode and the FA CoA mode. :)

>    A similar protocol has been documented in [RFC3963] for supporting
>    IPv6 moving networks with Mobile IPv6 extensions.

s/moving networks/mobile networks/

>    Although Mobile IPv4 stated that Mobile Network can be supported by
>    the Mobile Router and Home Agent using static configuration or
>    running a routing protocol, there is no solution for explicit
>    registration of the Mobile Networks served by the Mobile Router.  

Perhaps elaborate to say that there is no mechanism for
the home agent to know that the mobile router is
authorized to send routing updates for a particular
mobile network prefix? Is this the intention of the above
sentence?

> 4.2.  Mobile Network Acknowledgement Extension
> 
>    The Registration Reply contains zero, one or several Mobile Network
>    Acknowledgement extensions in addition to any other extensions
>    defined by or in the context of ([RFC3344]).  For Implicit Mode,
>    the Mobile Network Acknowledgement informs the Mobile Router the
>    prefixes served by the Home Agent.  

You mean owned by the Mobile Router? The Home Agent only
sets up forwarding for the mobile network prefix. Is this
what you mean by "served by the Home Agent"?

>    In accordance with this specification, a Mobile Router may operate in
>    one of the following two modes: explicit and implicit.  In explicit
>    mode, the Mobile Router includes Mobile Network Prefix information in
>    all Registration Requests (as Mobile Network Request extensions),
>    while in implicit mode it does not include this information in any
>    Registration Request.  In this latter case, the Home Agent obtains
>    the Mobile Network Prefixes by other means than Mobile IP.

Perhaps give one example, like configuration on the home
agent.

>    A Mobile Router can obtain a Collocated or Foreign Agent Care-of-
>    Address while operating in explicit or implicit modes.

Whether the mobile router is using the explicit or implicit
mode it has no impact on FA or colocated CoA mode, right?
Anyway re-phrase the above sentence to

    A Mobile Router MAY use either Co-located or Foreign Agent
    Care-of Address while operating in explicit or implicit mode.

>    1.  Check that the subnet information is valid

s/subnet/Mobile Network Prefix/

We have used mobile network prefix or just mobile network so
far.

>    2.  Ensure such subnet is authorized to be on the Mobile Router

Same as above.

> 6.2.1.  Registration Table
> 
>    The registration table in the Home Agent, in accordance with
>    ([RFC3344]), contains binding information for every mobile node
>    registered with it.  

Mention that the Registration Table is already defined in
RFC 3344.

>    If all checks are successful, the Home Agent either creates a new
>    entry(ies) for the Mobile Router or updates an existing binding
>    entry(ies) for it 

Isn't there only one entry per Mobile Router? Are you
considering multiple home addresses per mobile router?
Anyway a registration request can only modify one
binding cache entry at a time. It cannot modify more
than one, right?

> 6.4.  Advertising Mobile Network Reachability
> 
>    If the mobile network prefixes served by the Home Agent are
>    aggregated with the home network prefix and if the Home Agent is the
>    default router on the home network, the Home Agent does not have to
>    do anything different than normal.  

s/do anything different than normal/advertise the mobile network prefixes.

 > The routes for the mobile network
>    prefix are automatically aggregated into the home network prefix.  

Mention that it is assumed that the mobile network
prefixes are automatically aggregated under the home
network prefix.

If
>    the Mobile Router updates the mobile network prefix routes via a
>    dynamic routing protocol, the Home Agent SHOULD propagate the routes
>    on the appropriate networks.

This is the first mention of running a dynamic routing
protocol between the MR and the HA. Perhaps it should
be described briefly somewhere earlier on how to run
a dynamic routing protocol between the mobile router
and the HA.

Vijay

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Tue Dec 12 05:47:52 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gu5Ao-0005Dh-1A; Tue, 12 Dec 2006 05:47:46 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gu5Am-0005Bx-6B
	for mip4@ietf.org; Tue, 12 Dec 2006 05:47:44 -0500
Received: from av9-2-sn3.vrr.skanova.net ([81.228.9.186])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gu5Ak-0008El-OH
	for mip4@ietf.org; Tue, 12 Dec 2006 05:47:44 -0500
Received: by av9-2-sn3.vrr.skanova.net (Postfix, from userid 502)
	id 1409837FDC; Tue, 12 Dec 2006 11:47:38 +0100 (CET)
Received: from smtp3-1-sn3.vrr.skanova.net (smtp3-1-sn3.vrr.skanova.net
	[81.228.9.101]) by av9-2-sn3.vrr.skanova.net (Postfix) with ESMTP
	id E3CDA37EB1; Tue, 12 Dec 2006 11:47:37 +0100 (CET)
Received: from shiraz.levkowetz.com (81-232-110-214-no16.tbcn.telia.com
	[81.232.110.214])
	by smtp3-1-sn3.vrr.skanova.net (Postfix) with ESMTP id BDF1437E6E;
	Tue, 12 Dec 2006 11:47:37 +0100 (CET)
Received: from localhost ([127.0.0.1])
	by shiraz.levkowetz.com with esmtp (Exim 4.63)
	(envelope-from <henrik@levkowetz.com>)
	id 1Gu5AY-0005Nm-OK; Tue, 12 Dec 2006 11:47:30 +0100
Message-ID: <457E88BE.6090107@levkowetz.com>
Date: Tue, 12 Dec 2006 11:47:26 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Thunderbird 1.5.0.8 (Macintosh/20061025)
MIME-Version: 1.0
To: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
Subject: Re: [Mip4] Charter Update Proposal
References: <45647C27.4040208@levkowetz.com> <457E1F9E.3000109@azairenet.com>
In-Reply-To: <457E1F9E.3000109@azairenet.com>
X-Enigmail-Version: 0.94.1.2
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: vijay.devarapalli@azairenet.com, mip4-ads@tools.ietf.org,
	mip4@ietf.org, mip4-chairs@tools.ietf.org,
	henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on shiraz.levkowetz.com);
	SAEximRunCond expanded to false
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Cc: mip4-chairs@tools.ietf.org, mip4-ads@tools.ietf.org,
	Mobile IPv4 Mailing List <mip4@ietf.org>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0317702301=="
Errors-To: mip4-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============0317702301==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig5B352FA9E8DA7398EE597603"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig5B352FA9E8DA7398EE597603
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi Vijay,

on 2006-12-12 04:18 Vijay Devarapalli said the following:
> Henrik Levkowetz wrote:
>> Hi,
>>=20
>>=20
>> Both the list and the WG meeting during IETF-67 indicated support for
>> adding moving network support and a notification mechanism to the
>> charter, so below is a proposal for a charter update.  (The resulting
>> charter, if the updates are accepted, are provided as an attachment.)
>>=20
>> We propose to add the following two items to the list of work to
>> be done:
>>=20
>>   11. MIPv4 Moving Network Support
>=20
> Can we call this "MIPv4 Mobile Network Support" or "MIPv4 Network=20
> Mobility Support"? I don't like the term "Moving Network". :)

So exactly what distinguishes "Network Mobility" from "Network-based
Mobility"? =20

I proposed "Moving Network" because it is clearly not what NetLMM is
working on.  It may not be elegant, it may not be conventional, but
it is (I think) pretty clear what we're talking about... :-)


	Henrik




--------------enig5B352FA9E8DA7398EE597603
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iD8DBQFFfoi/eVhrtTJkXCMRAg31AJwMR9dZ6TyuJqHj6Finypl2iNHRZACgnXKO
vwyG+56ZMyGzE/TGmr/8o9w=
=EBvG
-----END PGP SIGNATURE-----

--------------enig5B352FA9E8DA7398EE597603--


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

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

--===============0317702301==--




From mip4-bounces@ietf.org Tue Dec 12 06:32:11 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gu5rU-0007H4-Dd; Tue, 12 Dec 2006 06:31:52 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gu5rS-0007DT-Qm
	for mip4@ietf.org; Tue, 12 Dec 2006 06:31:50 -0500
Received: from floor.dave.sonera.fi ([131.177.130.22])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gu5rR-00018N-52
	for mip4@ietf.org; Tue, 12 Dec 2006 06:31:50 -0500
Received: from floor.dave.sonera.fi (localhost [127.0.0.1]) by
	floor.dave.sonera.fi (Sendmail) with ESMTP id kBCBVaN8013988
	for <mip4@ietf.org>; Tue, 12 Dec 2006 13:31:37 +0200 (EET)
Received: from [131.177.107.29] (ws329.secureuser.sonera.fi [131.177.107.29])
	by floor.dave.sonera.fi (Sendmail) with ESMTP id kBCBVKAc013983;
	Tue, 12 Dec 2006 13:31:25 +0200 (EET)
Message-ID: <457E930A.4060101@teliasonera.com>
Date: Tue, 12 Dec 2006 13:31:22 +0200
From: Jouni Korhonen <jouni.korhonen@teliasonera.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: Vijay Devarapalli <vijay.devarapalli@AzaireNet.com>
Subject: Re: [Mip4] WGLC: draft-ietf-mip4-mobike-connectivity-01.txt
References: <BE4B07D4197BF34EB3B753DD34EBCD130125E6C2@de01exm67.ds.mot.com>
	<456CA2B2.9010708@azairenet.com> <456D6775.4050905@teliasonera.com>
	<457DAC9A.1040501@azairenet.com>
In-Reply-To: <457DAC9A.1040501@azairenet.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1a1bf7677bfe77d8af1ebe0e91045c5b
Cc: mip4@ietf.org, McCann Peter-A001034 <pete.mccann@motorola.com>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Hi Vijay,

Vijay Devarapalli kirjoitti:
> Jouni Korhonen wrote:
>> Hi Vijay,
>>
>> I think it was me who asked for this appendix. I'm happy to have it 
>> there now. I'm not sure whether it makes any additional value to 
>> mention in appendix A that the operator trusted network could also be 
>> implemented as the home link from MNs. For certain wireless 
>> technologies this would give a nice optimization.
> 
> We can add the following sentence at the end of the
> appendix.
> 
>    When the mobile node is attached to the trusted access network, it
>    can either by attached to a foreign link in the trusted network or to
>    the home link directly.  This document does not impose any
>    restrictions.

This is OK. Thanks.

> 
> Vijay
> 
> 
>> Apart from the above "I support the advancement of this document to 
>> the IESG with a request for publication as proposed standard."

So repeating myself ;)

"I support the advancement of this document to the IESG with a request 
for publication as proposed standard."


>>
>> Cheers,
>>     Jouni
>>
>> Vijay Devarapalli kirjoitti:
>>> just wanted to point out that the only major change
>>> since the last WG last call was to add a new section
>>> in the Appendix to show how the solution can be
>>> applied to a mobile operator network.
>>>
>>> Vijay
>>>
>>> McCann Peter-A001034 wrote:
>>>> This message announces a (second) WG last call on:
>>>>
>>>>    "Secure Connectivity and Mobility using Mobile IPv4 and MOBIKE"
>>>>    draft-ietf-mip4-mobike-connectivity-01.txt
>>>>
>>>> The last call will conclude at 24:00 UTC on Tuesday, 12 December 2006.
>>>>
>>>> "Secure Connectivity and Mobility using Mobile IPv4 and MOBIKE"
>>>> describes a solution using Mobile IPv4 and mobility extensions to 
>>>> IKEv2 (MOBIKE)
>>>> to provide secure connectivity and mobility.
>>>>
>>>> A URL for this internet draft is:
>>>>
>>>> http://www.ietf.org/internet-drafts/draft-ietf-mip4-mobike-connectivity- 
>>>>
>>>> 01.txt
>>>>
>>>>
>>>> Please respond to this WG last call:
>>>>
>>>>
>>>> * If you have no comments on the draft, and support its advancement,
>>>>   simply respond with a line containing something like
>>>>
>>>>
>>>>    "I support the advancement of this document to the IESG with a
>>>>     request for publication as proposed standard."
>>>>
>>>>
>>>>   If you have comments, please use a line similar to the one above, and
>>>>   supplement this with your comments.
>>>>
>>>>
>>>>
>>>> * If you *don't* support its advancement, respond with a line 
>>>> containing
>>>>   something like the following, supplemented by your comments -
>>>>
>>>>
>>>>    "I don't support the advancement of this document to the IESG with
>>>>     a request for publication as proposed standard, for the following
>>>>     reasons:"
>>>>    ...
>>>>
>>>>
>>>>
>>>>
>>>>     Pete & Henrik
>>>>
>>>
>>>
> 
> 

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Tue Dec 12 07:44:46 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gu6zq-0003Kp-7m; Tue, 12 Dec 2006 07:44:34 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gu6zo-0003KX-VS
	for mip4@ietf.org; Tue, 12 Dec 2006 07:44:32 -0500
Received: from mail119.messagelabs.com ([216.82.241.179])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1Gu6zm-0000EN-L1
	for mip4@ietf.org; Tue, 12 Dec 2006 07:44:32 -0500
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@motorola.com
X-Msg-Ref: server-8.tower-119.messagelabs.com!1165927153!12679459!1
X-StarScan-Version: 5.5.10.7; banners=-,-,-
X-Originating-IP: [129.188.136.8]
Received: (qmail 7165 invoked from network); 12 Dec 2006 12:39:13 -0000
Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8)
	by server-8.tower-119.messagelabs.com with SMTP;
	12 Dec 2006 12:39:13 -0000
Received: from il06exr01.mot.com (il06exr01.mot.com [129.188.137.131])
	by motgate8.mot.com (8.12.11/Motorola) with ESMTP id kBCCdCwB010907;
	Tue, 12 Dec 2006 05:39:12 -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 kBCCdA8J028689;
	Tue, 12 Dec 2006 06:39:11 -0600 (CST)
Message-ID: <457EA2ED.1030603@motorola.com>
Date: Tue, 12 Dec 2006 13:39:09 +0100
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: Vijay Devarapalli <vijay.devarapalli@AzaireNet.com>
References: <457E204A.5060609@azairenet.com>
In-Reply-To: <457E204A.5060609@azairenet.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1676547e4f33b5e63227e9c02bd359e3
Cc: "Kent Leung \(kleung\)" <kleung@cisco.com>, mip4@ietf.org
Subject: [Mip4] Re: mobile moving networks (was: Comments on
	draft-ietf-nemo-v4-base-01.txt)
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Vijay thanks for the comments, will address soon.  Let me thread one
terminology topic separately.

Vijay Devarapalli suggests to substitute:
> s/moving networks/mobile networks/

I think 'moving networks' is more illustrative of NEMO than 'mobile
networks' which could mean too fixed networks supporting mobility.  I.e.
  it is common in telecom industry to call a 3GPP network a 'mobile
network' which is not moving actually.  A 'moving network' doesn't have
that ambiguity.

On another hand both the mobility terminology rfc3753 and the
draft-ietf-nemo-terminology suggest 'mobile network' instead.

I'm personally inclined to go with 'moving network', per the reason
above.  A s/x/y isn't hard to do either.  Let's see.

Alex

> 
>> Although Mobile IPv4 stated that Mobile Network can be supported by
>>  the Mobile Router and Home Agent using static configuration or 
>> running a routing protocol, there is no solution for explicit 
>> registration of the Mobile Networks served by the Mobile Router.
> 
> Perhaps elaborate to say that there is no mechanism for the home
> agent to know that the mobile router is authorized to send routing
> updates for a particular mobile network prefix? Is this the intention
> of the above sentence?
> 
>> 4.2.  Mobile Network Acknowledgement Extension
>> 
>> The Registration Reply contains zero, one or several Mobile Network
>>  Acknowledgement extensions in addition to any other extensions 
>> defined by or in the context of ([RFC3344]).  For Implicit Mode, 
>> the Mobile Network Acknowledgement informs the Mobile Router the 
>> prefixes served by the Home Agent.
> 
> You mean owned by the Mobile Router? The Home Agent only sets up
> forwarding for the mobile network prefix. Is this what you mean by
> "served by the Home Agent"?
> 
>> In accordance with this specification, a Mobile Router may operate
>> in one of the following two modes: explicit and implicit.  In
>> explicit mode, the Mobile Router includes Mobile Network Prefix
>> information in all Registration Requests (as Mobile Network Request
>> extensions), while in implicit mode it does not include this
>> information in any Registration Request.  In this latter case, the
>> Home Agent obtains the Mobile Network Prefixes by other means than
>> Mobile IP.
> 
> Perhaps give one example, like configuration on the home agent.
> 
>> A Mobile Router can obtain a Collocated or Foreign Agent Care-of- 
>> Address while operating in explicit or implicit modes.
> 
> Whether the mobile router is using the explicit or implicit mode it
> has no impact on FA or colocated CoA mode, right? Anyway re-phrase
> the above sentence to
> 
> A Mobile Router MAY use either Co-located or Foreign Agent Care-of
> Address while operating in explicit or implicit mode.
> 
>> 1.  Check that the subnet information is valid
> 
> s/subnet/Mobile Network Prefix/
> 
> We have used mobile network prefix or just mobile network so far.
> 
>> 2.  Ensure such subnet is authorized to be on the Mobile Router
> 
> Same as above.
> 
>> 6.2.1.  Registration Table
>> 
>> The registration table in the Home Agent, in accordance with 
>> ([RFC3344]), contains binding information for every mobile node 
>> registered with it.
> 
> Mention that the Registration Table is already defined in RFC 3344.
> 
>> If all checks are successful, the Home Agent either creates a new 
>> entry(ies) for the Mobile Router or updates an existing binding 
>> entry(ies) for it
> 
> Isn't there only one entry per Mobile Router? Are you considering
> multiple home addresses per mobile router? Anyway a registration
> request can only modify one binding cache entry at a time. It cannot
> modify more than one, right?
> 
>> 6.4.  Advertising Mobile Network Reachability
>> 
>> If the mobile network prefixes served by the Home Agent are 
>> aggregated with the home network prefix and if the Home Agent is
>> the default router on the home network, the Home Agent does not
>> have to do anything different than normal.
> 
> s/do anything different than normal/advertise the mobile network
> prefixes.
> 
>> The routes for the mobile network prefix are automatically
>> aggregated into the home network prefix.
> 
> Mention that it is assumed that the mobile network prefixes are
> automatically aggregated under the home network prefix.
> 
> If
>> the Mobile Router updates the mobile network prefix routes via a 
>> dynamic routing protocol, the Home Agent SHOULD propagate the
>> routes on the appropriate networks.
> 
> This is the first mention of running a dynamic routing protocol
> between the MR and the HA. Perhaps it should be described briefly
> somewhere earlier on how to run a dynamic routing protocol between
> the mobile router and the HA.
> 
> Vijay
> 


-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Tue Dec 12 10:02:13 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gu98r-0003Cv-B2; Tue, 12 Dec 2006 10:02:01 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gu98q-0003Cq-PM
	for mip4@ietf.org; Tue, 12 Dec 2006 10:02:00 -0500
Received: from michael.checkpoint.com ([194.29.32.68])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gu98o-0007xQ-7M
	for mip4@ietf.org; Tue, 12 Dec 2006 10:02:00 -0500
Received: from ysheffer.ad.checkpoint.com (localhost [127.0.0.1])
	by michael.checkpoint.com (8.12.10+Sun/8.12.10) with ESMTP id
	kBCF1j67020969; Tue, 12 Dec 2006 17:01:46 +0200 (IST)
Message-Id: <200612121501.kBCF1j67020969@michael.checkpoint.com>
Date: Tue, 12 Dec 2006 17:01:46 +0200
From: Yaron Sheffer <yaronf@checkpoint.com>
Subject: RE: [Mip4] WGLC: draft-ietf-mip4-mobike-connectivity-01.txt
To: McCann Peter-A001034 <pete.mccann@motorola.com>, mip4@ietf.org
In-reply-to: <BE4B07D4197BF34EB3B753DD34EBCD13012D8974@de01exm67.ds.mot.com>
MIME-Version: 1.0
X-Mailer: Sun Outlook Connector 7.1.228.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: QUOTED-PRINTABLE
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6cca30437e2d04f45110f2ff8dc1b1d5
Cc: 
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Dear WG participants,

I support the advancement of this document, as my comments to version -00 h=
ave been addressed.

One nit: the paragraph saying "Mobility extensions for IKEv2 are being stan=
dardized" should say "have been standardized" - MOBIKE is an RFC.

Thanks,
=09Yaron

> -----Original Message-----
> From: McCann Peter-A001034 [mailto:pete.mccann@motorola.com]
> Sent: Monday, December 11, 2006 17:23
> To: mip4@ietf.org
> Subject: RE: [Mip4] WGLC: draft-ietf-mip4-mobike-connectivity-01.txt
>=20
> Reminder: this WGLC ends tomorrow at midnight.  So far we
> have gotten minimal feedback.  More support will be required
> to advance this to the IESG.
>=20
> -Pete
>=20
> McCann Peter-A001034 wrote:
> > This message announces a (second) WG last call on:
> >
> >    "Secure Connectivity and Mobility using Mobile IPv4 and MOBIKE"
> >    draft-ietf-mip4-mobike-connectivity-01.txt
> >
> > The last call will conclude at 24:00 UTC on Tuesday, 12 December 2006.
> >
> > "Secure Connectivity and Mobility using Mobile IPv4 and MOBIKE"
> > describes
> > a solution using Mobile IPv4 and mobility extensions to IKEv2 (MOBIKE)
> > to
> > provide secure connectivity and mobility.
> >
> > A URL for this internet draft is:
> >
> >
> http://www.ietf.org/internet-drafts/draft-ietf-mip4-mobike-connectivity-
> > 01.txt
> >
> >
> > Please respond to this WG last call:
> >
> >
> > * If you have no comments on the draft, and support its advancement,
> >   simply respond with a line containing something like
> >
> >
> >    "I support the advancement of this document to the IESG with a
> >     request for publication as proposed standard."
> >
> >
> >   If you have comments, please use a line similar to the one above,
> >   and supplement this with your comments.
> >
> >
> >
> > * If you *don't* support its advancement, respond with a line
> >   containing something like the following, supplemented by your
> > comments -
> >
> >
> >    "I don't support the advancement of this document to the IESG with
> >     a request for publication as proposed standard, for the following
> >     reasons:"
> >    ...
> >
> >
> >
> >
> >     Pete & Henrik
>=20
>=20



-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Tue Dec 12 11:45:11 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GuAkd-0003DF-Pp; Tue, 12 Dec 2006 11:45:07 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GuAkc-0003D6-SO
	for mip4@ietf.org; Tue, 12 Dec 2006 11:45:06 -0500
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GuAkW-0002bq-9x
	for mip4@ietf.org; Tue, 12 Dec 2006 11:45:06 -0500
Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 0FE3410FB
	for <mip4@ietf.org>; Tue, 12 Dec 2006 17:44:45 +0100 (CET)
Received: from esealmw106.eemea.ericsson.se ([153.88.200.69]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 12 Dec 2006 17:44:44 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 12 Dec 2006 17:44:43 +0100
Message-ID: <857CEC890B0AEE4F9A48DB972AC4457A1F26ED@esealmw106.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Question about "MN returning home"
Thread-Index: AcceDNMUMwH4C9M1QZucIoyNuvsjYQ==
From: "David Przybylak \(LN/EAB\)" <david.przybylak@ericsson.com>
To: <mip4@ietf.org>
X-OriginalArrivalTime: 12 Dec 2006 16:44:44.0849 (UTC)
	FILETIME=[D3FEF210:01C71E0C]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
Subject: [Mip4] Question about "MN returning home"
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1620515901=="
Errors-To: mip4-bounces@ietf.org


This is a multi-part message in MIME format.

--===============1620515901==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C71E0C.D3A57442"


This is a multi-part message in MIME format.

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

Hello,

My name is David Przybylak, I'm quite new to the mailing list.

There's one thing that is still not very clear to me in the case of "MN
returning home" in RFC 3344, I hope someone can make this clear to me!

Let's assume a MIP client (a MN) registered away from its home network
and got a home address dynamically assigned to it by its HA.
When this MN is then returning home, can we assume (if the MN is RFC
3344 compliant) that it will use its home address once at home after it
has deregistered? I mean, will its interface physically have its home
address as its IP address, or can the MN use another IP address there?

Best regards

David Przybylak


------_=_NextPart_001_01C71E0C.D3A57442
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.28">
<TITLE>Question about &quot;MN returning home&quot;</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

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

<P><FONT SIZE=3D2 FACE=3D"Courier New">My name is David Przybylak, I'm =
quite new to the mailing list.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">There's one thing that is still =
not very clear to me in the case of &quot;MN returning home&quot; in RFC =
3344, I hope someone can make this clear to me!</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">Let's assume a MIP client (a MN) =
registered away from its home network and got a home address dynamically =
assigned to it by its HA.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">When this MN is then returning =
home, can we assume (if the MN is RFC 3344 compliant) that it will use =
its home address once at home after it has deregistered? I mean, will =
its interface physically have its home address as its IP address, or can =
the MN use another IP address there?</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">Best regards</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">David Przybylak</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C71E0C.D3A57442--


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

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

--===============1620515901==--




From mip4-bounces@ietf.org Tue Dec 12 12:26:05 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GuBOH-0004uD-0E; Tue, 12 Dec 2006 12:26:05 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GuBOG-0004tv-GG
	for mip4@ietf.org; Tue, 12 Dec 2006 12:26:04 -0500
Received: from 213.80.52.78.dataphone.se ([213.80.52.78]
	helo=mailgw.local.ipunplugged.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GuBOE-0001kn-HB
	for mip4@ietf.org; Tue, 12 Dec 2006 12:26:04 -0500
Received: from [127.0.0.1] (echo.local.ipunplugged.com [192.168.4.74])
	by mailgw.local.ipunplugged.com (8.12.8/8.12.3) with ESMTP id
	kBCHPgOg002980; Tue, 12 Dec 2006 18:25:47 +0100
Message-ID: <457EE614.1050501@ipunplugged.com>
Date: Tue, 12 Dec 2006 18:25:40 +0100
From: Hans Sjostrand <hans@ipunplugged.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: "David Przybylak (LN/EAB)" <david.przybylak@ericsson.com>
Subject: Re: [Mip4] Question about "MN returning home"
References: <857CEC890B0AEE4F9A48DB972AC4457A1F26ED@esealmw106.eemea.ericsson.se>
In-Reply-To: <857CEC890B0AEE4F9A48DB972AC4457A1F26ED@esealmw106.eemea.ericsson.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: clamd / ClamAV version 0.75.1, clamav-milter version 0.75c
	on mailgw.local.ipunplugged.com
X-Virus-Status: Clean
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Cc: mip4@ietf.org
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Hi David,

It's in the definition of the term Home Address in RFC3344, section 
"1.6. Terminology"

      Home Address
            An IP address that is assigned for an extended period of
            time to a mobile node.  It remains unchanged regardless of
            where the node is attached to the Internet.

Else it's kind of pointless to have mobile ip. All sessions with other 
CN's would brake at every handover from or to the home network if the 
home address didn't remain unchanged.

However, you do not find the answer to _how_ this is done in RFC3344. 
This is left for the vendors to implement in any way they choose. Some 
vendors have implemented this and some have simply chosen not to do it 
and hence not support the case of coming home combined with dynamic home 
address assignment. This list is not the place to advertise which 
vendors that have done what.

Best regards
/// Hasse

David Przybylak (LN/EAB) wrote:
>
> Hello,
>
> My name is David Przybylak, I'm quite new to the mailing list.
>
> There's one thing that is still not very clear to me in the case of 
> "MN returning home" in RFC 3344, I hope someone can make this clear to me!
>
> Let's assume a MIP client (a MN) registered away from its home network 
> and got a home address dynamically assigned to it by its HA.
>
> When this MN is then returning home, can we assume (if the MN is RFC 
> 3344 compliant) that it will use its home address once at home after 
> it has deregistered? I mean, will its interface physically have its 
> home address as its IP address, or can the MN use another IP address 
> there?
>
> Best regards
>
> David Przybylak
>



-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Tue Dec 12 13:31:30 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GuCPa-0006JH-N8; Tue, 12 Dec 2006 13:31:30 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GuCPZ-0006If-Pl
	for mip4@ietf.org; Tue, 12 Dec 2006 13:31:29 -0500
Received: from mail2.azairenet.com ([66.92.223.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GuCPY-0000cL-E4
	for mip4@ietf.org; Tue, 12 Dec 2006 13:31:29 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip4] WGLC: draft-ietf-mip4-mobike-connectivity-01.txt
Date: Tue, 12 Dec 2006 10:31:26 -0800
Message-ID: <D4AE20519DDD544A98B3AE9235C8A4C2525DFC@moe.corp.azairenet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip4] WGLC: draft-ietf-mip4-mobike-connectivity-01.txt
Thread-Index: Accd/sgKu4+K+Un/TReTuVMLd284nAAHKpcg
From: "Vijay Devarapalli" <Vijay.Devarapalli@AzaireNet.com>
To: "Yaron Sheffer" <yaronf@checkpoint.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 057ebe9b96adec30a7efb2aeda4c26a4
Cc: mip4@ietf.org, McCann Peter-A001034 <pete.mccann@motorola.com>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Hi Yaron,=20

> One nit: the paragraph saying "Mobility extensions for IKEv2=20
> are being standardized" should say "have been standardized" -=20
> MOBIKE is an RFC.

Actually I am going to remove the entire paragraph.
That paragraph used to refer to an appendix that
described mobility extensions to IKEv1. We removed
the appendix but did not delete the paragraph.

Also added the following text to the Introduction
section.

   IPsec VPN gateways that use IKEv1 [14] are not addressed in this
   document.

Vijay

>=20
> Thanks,
> 	Yaron
>=20
> > -----Original Message-----
> > From: McCann Peter-A001034 [mailto:pete.mccann@motorola.com]
> > Sent: Monday, December 11, 2006 17:23
> > To: mip4@ietf.org
> > Subject: RE: [Mip4] WGLC: draft-ietf-mip4-mobike-connectivity-01.txt
> >=20
> > Reminder: this WGLC ends tomorrow at midnight.  So far we
> > have gotten minimal feedback.  More support will be required
> > to advance this to the IESG.
> >=20
> > -Pete
> >=20
> > McCann Peter-A001034 wrote:
> > > This message announces a (second) WG last call on:
> > >
> > >    "Secure Connectivity and Mobility using Mobile IPv4 and MOBIKE"
> > >    draft-ietf-mip4-mobike-connectivity-01.txt
> > >
> > > The last call will conclude at 24:00 UTC on Tuesday, 12=20
> December 2006.
> > >
> > > "Secure Connectivity and Mobility using Mobile IPv4 and MOBIKE"
> > > describes
> > > a solution using Mobile IPv4 and mobility extensions to=20
> IKEv2 (MOBIKE)
> > > to
> > > provide secure connectivity and mobility.
> > >
> > > A URL for this internet draft is:
> > >
> > >
> >=20
> http://www.ietf.org/internet-drafts/draft-ietf-mip4-mobike-con
nectivity-
> > > 01.txt
> > >
> > >
> > > Please respond to this WG last call:
> > >
> > >
> > > * If you have no comments on the draft, and support its=20
> advancement,
> > >   simply respond with a line containing something like
> > >
> > >
> > >    "I support the advancement of this document to the IESG with a
> > >     request for publication as proposed standard."
> > >
> > >
> > >   If you have comments, please use a line similar to the=20
> one above,
> > >   and supplement this with your comments.
> > >
> > >
> > >
> > > * If you *don't* support its advancement, respond with a line
> > >   containing something like the following, supplemented by your
> > > comments -
> > >
> > >
> > >    "I don't support the advancement of this document to=20
> the IESG with
> > >     a request for publication as proposed standard, for=20
> the following
> > >     reasons:"
> > >    ...
> > >
> > >
> > >
> > >
> > >     Pete & Henrik
> >=20
> >=20
>=20
>=20
>=20
> --=20
> Mip4 mailing list: Mip4@ietf.org
>     Web interface: https://www1.ietf.org/mailman/listinfo/mip4
>      Charter page: http://www.ietf.org/html.charters/mip4-charter.html
> Supplemental site: http://www.mip4.org/
>=20

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Tue Dec 12 13:46:01 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GuCdd-0003TR-5I; Tue, 12 Dec 2006 13:46:01 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GuCdc-0003TM-70
	for mip4@ietf.org; Tue, 12 Dec 2006 13:46:00 -0500
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GuCdU-0002zv-L4
	for mip4@ietf.org; Tue, 12 Dec 2006 13:46:00 -0500
Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.120])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id E045B23; 
	Tue, 12 Dec 2006 19:45:47 +0100 (CET)
Received: from esealmw106.eemea.ericsson.se ([153.88.200.69]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 12 Dec 2006 19:45:47 +0100
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
Subject: RE: [Mip4] Question about "MN returning home"
Date: Tue, 12 Dec 2006 19:45:46 +0100
Message-ID: <857CEC890B0AEE4F9A48DB972AC4457A1F275D@esealmw106.eemea.ericsson.se>
In-Reply-To: <457EE614.1050501@ipunplugged.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip4] Question about "MN returning home"
Thread-Index: AcceEpJtxJf8+IfaQF+rdOOt8CubwgACvYmQ
From: "David Przybylak \(LN/EAB\)" <david.przybylak@ericsson.com>
To: "Hans Sjostrand" <hans@ipunplugged.com>
X-OriginalArrivalTime: 12 Dec 2006 18:45:47.0069 (UTC)
	FILETIME=[BC9DC6D0:01C71E1D]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
Cc: mip4@ietf.org
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Thank you for your answer Hasse!

That's just how I thought it should be.
I was however surprised to find some MIP clients which didn't work that
way so I was wondering how to handle them. But now at least I know what
the standard "RFC 3344 compliant" behaviour of a MIP client is.

BR

/David
=20

> -----Original Message-----
> From: Hans Sjostrand [mailto:hans@ipunplugged.com]=20
> Sent: den 12 december 2006 18:26
> To: David Przybylak (LN/EAB)
> Cc: mip4@ietf.org
> Subject: Re: [Mip4] Question about "MN returning home"
>=20
> Hi David,
>=20
> It's in the definition of the term Home Address in RFC3344,=20
> section "1.6. Terminology"
>=20
>       Home Address
>             An IP address that is assigned for an extended period of
>             time to a mobile node.  It remains unchanged regardless of
>             where the node is attached to the Internet.
>=20
> Else it's kind of pointless to have mobile ip. All sessions=20
> with other CN's would brake at every handover from or to the=20
> home network if the home address didn't remain unchanged.
>=20
> However, you do not find the answer to _how_ this is done in RFC3344.=20
> This is left for the vendors to implement in any way they=20
> choose. Some vendors have implemented this and some have=20
> simply chosen not to do it and hence not support the case of=20
> coming home combined with dynamic home address assignment.=20
> This list is not the place to advertise which vendors that=20
> have done what.
>=20
> Best regards
> /// Hasse
>=20
> David Przybylak (LN/EAB) wrote:
> >
> > Hello,
> >
> > My name is David Przybylak, I'm quite new to the mailing list.
> >
> > There's one thing that is still not very clear to me in the case of=20
> > "MN returning home" in RFC 3344, I hope someone can make=20
> this clear to me!
> >
> > Let's assume a MIP client (a MN) registered away from its=20
> home network=20
> > and got a home address dynamically assigned to it by its HA.
> >
> > When this MN is then returning home, can we assume (if the MN is RFC
> > 3344 compliant) that it will use its home address once at=20
> home after=20
> > it has deregistered? I mean, will its interface physically have its=20
> > home address as its IP address, or can the MN use another=20
> IP address=20
> > there?
> >
> > Best regards
> >
> > David Przybylak

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Wed Dec 13 02:34:13 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GuOcm-0007zd-PZ; Wed, 13 Dec 2006 02:33:56 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GuOcl-0007zS-2S
	for mip4@ietf.org; Wed, 13 Dec 2006 02:33:55 -0500
Received: from ithilien.qualcomm.com ([129.46.51.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GuOcj-0006Hz-Jw
	for mip4@ietf.org; Wed, 13 Dec 2006 02:33:55 -0500
Received: from neophyte.qualcomm.com (neophyte.qualcomm.com [129.46.61.149])
	by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	kBD7XqoU006253
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL)
	for <mip4@ietf.org>; Tue, 12 Dec 2006 23:33:52 -0800
Received: from sanexcas01.na.qualcomm.com (sanexcas01.qualcomm.com
	[172.30.36.175])
	by neophyte.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	kBD7Xpis009255 for <mip4@ietf.org>; Tue, 12 Dec 2006 23:33:51 -0800
Received: from NAEX13.na.qualcomm.com ([129.46.51.248]) by
	sanexcas01.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 12 Dec 2006 23:33:51 -0800
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: Tue, 12 Dec 2006 23:33:50 -0800
Message-ID: <C24CB51D5AA800449982D9BCB903251335E82F@NAEX13.na.qualcomm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: WGLC Comments: draft-ietf-mip4-mobike-connectivity-01.txt
Thread-Index: AcceiQiXSGBYpMQ7TJixCXQllMRnyw==
From: "Narayanan, Vidya" <vidyan@qualcomm.com>
To: "Mobile IPv4 Mailing List" <mip4@ietf.org>
X-OriginalArrivalTime: 13 Dec 2006 07:33:51.0309 (UTC)
	FILETIME=[08F6BFD0:01C71E89]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Subject: [Mip4] WGLC Comments: draft-ietf-mip4-mobike-connectivity-01.txt
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Overall, I support advancing this draft. But, I think it requires some
clarifications. =20

1. The draft states:=20

"The Mobile IP tunnel uses reverse tunneling through the
   home agent [8]."

>From this, it is not clear if reverse tunneling is mandated or not. This
should be clarified. When using the HoA for communication, reverse
tunneling probably needs to be mandated when accessing via a VPN -
otherwise, the VPN GW is going to drop the packets. If the VPN is set up
to bypass such packets as well, it will work, if the HoA is a routable
address and if there is no ingress filtering on the local network. But,
I'm not sure we need to allow such a scenario. Alternately, the MN may
use its VPN TIA for communication.=20

2. For crossing security boundaries, the document states:=20

"   If the mobile node has an existing VPN tunnel to its VPN gateway, it
   MUST send a MOBIKE message at the same time as the registration
   request to the i-HA whenever the IP address changes.  If the mobile
   node receives a response from the VPN gateway, but not from the i-HA,
   it assumes it is outside the enterprise network.  If it receives a
   response from the i-HA, then it assumes it is inside the enterprise
   network."

I don't understand this. I don't think it is trivial to bypass the VPN
to send a MIP RRQ, when the tunnel outer address is changing and a
MOBIKE exchange has been initiated. This would involve dynamically
changing the bypass rules for the VPN - in fact, it's not clear to me
how such a rule might even work. Obviously, UDP port 434 messages cannot
always be allowed to bypass IPsec. "Bypass UDP port 434 traffic when a
link change just occurred" doesn't quite work. If the MN is using a
CCoA, "bypass UDP port 434 traffic when IP source =3D local address" =
might
work, but, it won't work when the MN is using an FA CoA. Also, if the MN
discovered an FA on the local network, how does it know whether or not
to use it? It needs to not use it if that subnet is part of an untrusted
network. I understand that the motivation is to allow an operation with
lower latency, but, I am confused as to how this works.=20

In fact, I think it is simplest to state that the detection of trusted
networks is done by out-of-band mechanisms and that if there is a VPN
tunnel, that is always used. If we attempt to solve it as in the draft,
we need a lot more clarity on the following:=20

- What bypass rules are to be used for IPsec? I don't think hand-waving
this is good.=20
- Is the MN allowed to use an FA upon a subnet change? Is this the same
behavior whether the MN is moving from an untrusted or trusted network?=20
- If the MN used an FA, but discovers it is on an untrusted network, it
needs to then obtain a local address to set up a VPN.=20

3. Some VPNs support bypass mode/split tunneling when the host is
attached via an untrusted network - such traffic will not have any
mobility support as well. This is not too different from a MIP MN using
it's CoA for local communication - however, since this document ties the
VPN to MIP, I think it is good to note this - especially to avoid any
implementation issues (ambiguities with respect to what packets go
through MIP processing prior to IPsec processing and what don't). Any
attempt to route packets meant to bypass the VPN through the MIP stack
will result in dropped packets.=20

4. The document doesn't touch on simultaneous bindings and I think it
should. Some enterprises treat the internal wireless access networks
similar to untrusted networks (thereby requiring a VPN over it) and it
is quite common to have simultaneous wired and wireless connectivity.
One of those may be routed through a VPN, while the other may be routed
directly. Is the MN allowed to register both interfaces with the HA?
Unfortunately, the only form of simultaneous bindings supported by
RFC3344 is bicasting, which is not-so-desirable here, since, there may
be long periods of time when wired and wireless interfaces are
simultaneously active. So, perhaps the right thing to do is to recommend
against simultaneous bindings, but, I'm not sure.=20

5. Is a scenario where an MN may connect via a cellular network in scope
for the document? If so, there are a couple of cases to consider here.
The cellular network may be offering MIP separately. This is not an
issue when the MIP client for the cellular network is in the cellular
modem. But, when the MIP client in the host attempts to handle that
mobility as well, there might be a problem. This leads to a
MIP-IPsec-MIP layering, which I'm not sure we want to get into :) May be
we need to say that it is out of scope, but I'd like to hear other views
on this.=20

Vidya

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Wed Dec 13 06:41:39 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GuSUS-0001KL-FP; Wed, 13 Dec 2006 06:41:36 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GuSUR-0001KD-9i
	for mip4@ietf.org; Wed, 13 Dec 2006 06:41:35 -0500
Received: from wr-out-0506.google.com ([64.233.184.238])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GuSUQ-0004tH-4J
	for mip4@ietf.org; Wed, 13 Dec 2006 06:41:35 -0500
Received: by wr-out-0506.google.com with SMTP id i7so50510wra
	for <mip4@ietf.org>; Wed, 13 Dec 2006 03:41:33 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
	b=r9Sw1LxuYf/HYRspS9oGfARgrKLpOB47YBbfabcd5ECuLg59cwDXV5+yfqkT7xCEZ0e0NubN1JrwLRQfww7aPO3zHZ/t7hS8PCEqP5gqVJs6JzEv2gJuK9i8csozDRJ6fvumIPLRi6E9RVKyP7p+t9BJxwvyrH7OcikS0r2cqck=
Received: by 10.78.57.11 with SMTP id f11mr523632hua.1166010092716;
	Wed, 13 Dec 2006 03:41:32 -0800 (PST)
Received: by 10.78.146.14 with HTTP; Wed, 13 Dec 2006 03:41:32 -0800 (PST)
Message-ID: <496af9a70612130341x2c08b898ua78c76e6c974452f@mail.gmail.com>
Date: Wed, 13 Dec 2006 17:11:32 +0530
From: "Pradap K V" <on18thapril.pradap@gmail.com>
To: mip4@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6d62ab47271805379d7172ee693a45db
Subject: [Mip4] Conformance Test Document of MIPV4
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Hi all
Is there a   "Conformance test scenarios" draft  for MIPV4 , if so can
you provide me the reference or link .
Thanks and regards
pradap

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Wed Dec 13 06:52:12 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GuSei-0006s0-Cp; Wed, 13 Dec 2006 06:52:12 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GuSeh-0006rv-B0
	for mip4@ietf.org; Wed, 13 Dec 2006 06:52:11 -0500
Received: from mx0.starentnetworks.com ([12.38.223.203])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GuSeg-0007bN-2k
	for mip4@ietf.org; Wed, 13 Dec 2006 06:52:11 -0500
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mx0.starentnetworks.com (Postfix) with ESMTP id BAF1F1E0273
	for <mip4@ietf.org>; Wed, 13 Dec 2006 06:52:06 -0500 (EST)
Received: from mx0.starentnetworks.com ([127.0.0.1])
	by localhost (mx0.starentnetworks.com [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id 07030-11 for <mip4@ietf.org>;
	Wed, 13 Dec 2006 06:52:02 -0500 (EST)
Received: from exchtewks1.starentnetworks.com (exchtewks1.starentnetworks.com
	[12.33.233.52]) by mx0.starentnetworks.com (Postfix) with ESMTP
	for <mip4@ietf.org>; Wed, 13 Dec 2006 06:52:02 -0500 (EST)
Received: from EXCHINDIA2.starentnetworks.com ([10.4.2.4]) by
	exchtewks1.starentnetworks.com with Microsoft
	SMTPSVC(6.0.3790.1830); Wed, 13 Dec 2006 06:52:01 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.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: [Mip4] Conformance Test Document of MIPV4
Date: Wed, 13 Dec 2006 17:21:58 +0530
Message-ID: <CF406A890CCCA14E9543EAFBE3A2C2D101474911@exchindia2.starentnetworks.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip4] Conformance Test Document of MIPV4
Thread-Index: Acceq/0VsAH3/+mKTYKETVmDaZkfPAAAQ8tQ
From: "Phaneendra, S" <sphaneendra@starentnetworks.com>
To: "Pradap K V" <on18thapril.pradap@gmail.com>, <mip4@ietf.org>
X-OriginalArrivalTime: 13 Dec 2006 11:52:01.0986 (UTC)
	FILETIME=[1A207A20:01C71EAD]
X-Virus-Scanned: amavisd-new 2.2.1 (20041222) at mx0.starentnetworks.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Cc: 
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

That's a very good Qstn..
If you find the link..Plz send it to me as well.=20

-----Original Message-----
From: Pradap K V [mailto:on18thapril.pradap@gmail.com]=20
Sent: Wednesday, December 13, 2006 5:12 PM
To: mip4@ietf.org
Subject: [Mip4] Conformance Test Document of MIPV4

Hi all
Is there a   "Conformance test scenarios" draft  for MIPV4 , if so can
you provide me the reference or link .
Thanks and regards
pradap

--
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Wed Dec 13 10:36:30 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GuW9e-0000S0-5s; Wed, 13 Dec 2006 10:36:22 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GtuRA-00005r-Bp
	for mip4@ietf.org; Mon, 11 Dec 2006 18:19:56 -0500
Received: from ulysses.noc.ntua.gr ([147.102.222.230])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GtuR5-0006fn-OA
	for mip4@ietf.org; Mon, 11 Dec 2006 18:19:56 -0500
Received: from ektor.telecom.ece.ntua.gr (ektor.telecom.ece.ntua.gr
	[147.102.7.1])
	by ulysses.noc.ntua.gr (8.13.8/8.13.8) with ESMTP id kBBNI3xe094760;
	Tue, 12 Dec 2006 01:18:35 +0200 (EET)
	(envelope-from pimrc07-bounces@telecom.ntua.gr)
Received: from localhost (localhost.telecom.ece.ntua.gr [127.0.0.1])
	by ektor.telecom.ece.ntua.gr (Postfix) with ESMTP id 433DE8A345;
	Tue, 12 Dec 2006 01:18:34 +0200 (EET)
X-Virus-Scanned: ClamAV version 0.88.6,
	clamav-milter version 0.88.6 on ulysses.noc.ntua.gr
X-Virus-Scanned: Clam AntiVirus on ektor.telecom.ece.ntua.gr
Received: from ektor.telecom.ece.ntua.gr ([127.0.0.1])
	by localhost (ektor.telecom.ece.ntua.gr [127.0.0.1]) (amavisd-new,
	port 10024)
	with ESMTP id fTSK7nKgCYxr; Tue, 12 Dec 2006 01:18:33 +0200 (EET)
Received: from ektor.telecom.ece.ntua.gr (localhost.telecom.ece.ntua.gr
	[127.0.0.1])
	by ektor.telecom.ece.ntua.gr (Postfix) with ESMTP id 2ABE98A28D;
	Tue, 12 Dec 2006 01:15:56 +0200 (EET)
X-Original-To: pimrc07@telecom.ntua.gr
Delivered-To: pimrc07@telecom.ntua.gr
Received: from localhost (localhost.telecom.ece.ntua.gr [127.0.0.1])
	by ektor.telecom.ece.ntua.gr (Postfix) with ESMTP id 469D08A26B
	for <pimrc07@telecom.ntua.gr>; Tue, 12 Dec 2006 01:11:47 +0200 (EET)
X-Virus-Scanned: Clam AntiVirus on ektor.telecom.ece.ntua.gr
Received: from ektor.telecom.ece.ntua.gr ([127.0.0.1])
	by localhost (ektor.telecom.ece.ntua.gr [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id PrZisa3iX3Lo for <pimrc07@telecom.ntua.gr>;
	Tue, 12 Dec 2006 01:11:43 +0200 (EET)
Received: from harry (ppp042-044.dsl.hol.gr [89.210.42.44])
	by ektor.telecom.ece.ntua.gr (Postfix) with ESMTP id 1BCD78A270
	for <pimrc07@telecom.ntua.gr>; Tue, 12 Dec 2006 01:11:43 +0200 (EET)
Message-ID: <008b01c71d79$b8c4ebf0$1ab2a8c0@telecom.ntua.gr>
To: <pimrc07@telecom.ntua.gr>
Date: Tue, 12 Dec 2006 01:11:42 +0200
Organization: NTUA
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2869
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
X-Mailman-Approved-At: Tue, 12 Dec 2006 01:15:21 +0200
From: PIMRC 2007 <pimrc07@telecom.ntua.gr>
X-BeenThere: pimrc07@telecom.ntua.gr
X-Mailman-Version: 2.1.8
Precedence: list
List-Archive: <http://www.telecom.ntua.gr/pipermail/pimrc07>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Virus-Status: Clean
X-Spam-Score: 0.5 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
X-Mailman-Approved-At: Wed, 13 Dec 2006 10:36:21 -0500
Cc: 
Subject: [Mip4] [pimrc07] CFP: IEEE PIMRC 2007, Athens, Greece
X-BeenThere: mip4@ietf.org
Reply-To: pimrc07@telecom.ntua.gr
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

[Apologies if you receive multiple copies of this CFP]


========================================================
                               Call For Papers

                                IEEE PIMRC 2007
18th IEEE International Symposium on Personal, Indoor and Mobile Radio
Communications, September, 3-6, 2007, Athens, Greece
                        http://www.pimrc2007.org
========================================================


Conference Main Theme: Wireless Entropy

Overview

PIMRC 2007 provides a global forum for presenting the most recent
advances, the future technical challenges and business opportunities that
comprise the contemporary landscape in wireless communications. The
organizers endeavour to attract contributions covering not only
conventional areas of wireless communications (e.g., physical layer), but
also emerging areas with high potential for essential scientific and
societal impact such as wireless sensors for biomedical applications and
non-trivial pervasive computing services. The latter areas are expected to
facilitate the development of a broad vision of innovative future
applications in wireless communications. The high quality IEEE endorsed
technical programme, will also include tutorials, workshops, exhibitions,
panel discussions and keynote presentations from leading experts coming
from the academic community, industry, as well as regulatory and 
standardisation
bodies.

PIMRC 2007 will be held in Athens, Greece, September 3-6, 2007 i.e. one
week following the peak of Greece's beautiful summer season.


Call for Papers

Authors are invited to submit high-quality papers describing original and
previously unpublished contributions in a wide range of topics in wireless
communications. These topics are clustered into the following three major
categories:

1) Physical Layer and MAC
2) Mobile and Wireless Networks
3) Applications, Services and Business Models

Papers should be in English, strictly not exceeding 5 double-column pages
(3,000 words), in Adobe PDF format (which is the only accepted format for
PIMRC 2007). Authors should use the relevant IEEE template, ensuring an
IEEE Xplore compatible PDF-format.

To access the full list of topics, submission guidelines, as well as venue
and travel information please visit: www.pimrc2007.org

Important Dates

Full papers due:  March 3rd, 2007
Acceptance notice:   May 31st, 2007
Final manuscript due:  June 16th, 2007
Conference dates: September 3-6, 2007

_______________________________________________
pimrc07 mailing list
pimrc07@telecom.ntua.gr
http://www.telecom.ntua.gr/mailman/listinfo/pimrc07

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Wed Dec 13 11:40:43 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GuX9v-0000YV-Ay; Wed, 13 Dec 2006 11:40:43 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GuX9t-0000Xp-Kz
	for mip4@ietf.org; Wed, 13 Dec 2006 11:40:41 -0500
Received: from av10-2-sn2.hy.skanova.net ([81.228.8.182])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GuX9s-0007oP-2C
	for mip4@ietf.org; Wed, 13 Dec 2006 11:40:41 -0500
Received: by av10-2-sn2.hy.skanova.net (Postfix, from userid 502)
	id 367A23A0A3; Wed, 13 Dec 2006 17:40:39 +0100 (CET)
Received: from smtp4-1-sn2.hy.skanova.net (smtp4-1-sn2.hy.skanova.net
	[81.228.8.92]) by av10-2-sn2.hy.skanova.net (Postfix) with ESMTP
	id 0C9FF3A0A2; Wed, 13 Dec 2006 17:40:38 +0100 (CET)
Received: from shiraz.levkowetz.com (81-232-110-214-no16.tbcn.telia.com
	[81.232.110.214])
	by smtp4-1-sn2.hy.skanova.net (Postfix) with ESMTP id 2587237E46;
	Wed, 13 Dec 2006 17:40:37 +0100 (CET)
Received: from localhost ([127.0.0.1])
	by shiraz.levkowetz.com with esmtp (Exim 4.63)
	(envelope-from <henrik@levkowetz.com>)
	id 1GuX9p-00032I-Nj; Wed, 13 Dec 2006 17:40:37 +0100
Message-ID: <45802D03.6020404@levkowetz.com>
Date: Wed, 13 Dec 2006 17:40:35 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Thunderbird 1.5.0.8 (Macintosh/20061025)
MIME-Version: 1.0
To: "Narayanan, Vidya" <vidyan@qualcomm.com>
Subject: Re: [Mip4] WGLC Comments: draft-ietf-mip4-mobike-connectivity-01.txt
References: <C24CB51D5AA800449982D9BCB903251335E82F@NAEX13.na.qualcomm.com>
In-Reply-To: <C24CB51D5AA800449982D9BCB903251335E82F@NAEX13.na.qualcomm.com>
X-Enigmail-Version: 0.94.1.2
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: vidyan@qualcomm.com, mip4@ietf.org,
	henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on shiraz.levkowetz.com);
	SAEximRunCond expanded to false
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 1449ead51a2ff026dcb23465f5379250
Cc: Mobile IPv4 Mailing List <mip4@ietf.org>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0042346302=="
Errors-To: mip4-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============0042346302==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enigF9C4FA35ACC886E279333E82"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigF9C4FA35ACC886E279333E82
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable



on 2006-12-13 08:33 Narayanan, Vidya said the following:
> Overall, I support advancing this draft. But, I think it requires some
> clarifications. =20
>=20
> 1. The draft states:=20
>=20
> "The Mobile IP tunnel uses reverse tunneling through the
>    home agent [8]."
>=20
>>From this, it is not clear if reverse tunneling is mandated or not. Thi=
s
> should be clarified.

This is part of a solution overview, and as such is perfectly clear to me=

- it simply says that the solution uses reverse tunnelling through the
home agent.  Nothing to clarify.

> When using the HoA for communication, reverse
> tunneling probably needs to be mandated when accessing via a VPN -
> otherwise, the VPN GW is going to drop the packets. If the VPN is set u=
p
> to bypass such packets as well, it will work, if the HoA is a routable
> address and if there is no ingress filtering on the local network. But,=

> I'm not sure we need to allow such a scenario. Alternately, the MN may
> use its VPN TIA for communication.=20
>=20
> 2. For crossing security boundaries, the document states:=20
>=20
> "   If the mobile node has an existing VPN tunnel to its VPN gateway, i=
t
>    MUST send a MOBIKE message at the same time as the registration
>    request to the i-HA whenever the IP address changes.  If the mobile
>    node receives a response from the VPN gateway, but not from the i-HA=
,
>    it assumes it is outside the enterprise network.  If it receives a
>    response from the i-HA, then it assumes it is inside the enterprise
>    network."
>=20
> I don't understand this.

Seems clear enough to me.

> I don't think it is trivial to bypass the VPN
> to send a MIP RRQ, when the tunnel outer address is changing and a
> MOBIKE exchange has been initiated. This would involve dynamically
> changing the bypass rules for the VPN - in fact, it's not clear to me
> how such a rule might even work. Obviously, UDP port 434 messages canno=
t
> always be allowed to bypass IPsec. "Bypass UDP port 434 traffic when a
> link change just occurred" doesn't quite work. If the MN is using a
> CCoA, "bypass UDP port 434 traffic when IP source =3D local address" mi=
ght
> work, but, it won't work when the MN is using an FA CoA. Also, if the M=
N
> discovered an FA on the local network, how does it know whether or not
> to use it? It needs to not use it if that subnet is part of an untruste=
d
> network. I understand that the motivation is to allow an operation with=

> lower latency, but, I am confused as to how this works.=20

It seems to me that a rule to permit traffic to a specific host address
and port is trivial to implement.  What's so hard about that?

> In fact, I think it is simplest to state that the detection of trusted
> networks is done by out-of-band mechanisms and that if there is a VPN
> tunnel, that is always used. If we attempt to solve it as in the draft,=

> we need a lot more clarity on the following:=20

How to do the inside-outside detection isn't trivial, on the other hand,
so there is clear value in defining it.  Declaring it undefined doesn't
help.

> - What bypass rules are to be used for IPsec? I don't think hand-waving=

> this is good.
> - Is the MN allowed to use an FA upon a subnet change? Is this the same=

> behavior whether the MN is moving from an untrusted or trusted network?=
=20
> - If the MN used an FA, but discovers it is on an untrusted network, it=

> needs to then obtain a local address to set up a VPN.=20

Since the text you're criticizing already states clearly that a local
address has been acquired, this is not particularly relevant.  Sending
a RRQ to the i-HA using the acquired local address constitutes a simple
and feasible test of inside/outsideness, and that's what's desired here.

> 3. Some VPNs support bypass mode/split tunneling when the host is
> attached via an untrusted network - such traffic will not have any
> mobility support as well. This is not too different from a MIP MN using=

> it's CoA for local communication - however, since this document ties th=
e
> VPN to MIP, I think it is good to note this - especially to avoid any
> implementation issues (ambiguities with respect to what packets go
> through MIP processing prior to IPsec processing and what don't). Any
> attempt to route packets meant to bypass the VPN through the MIP stack
> will result in dropped packets.=20

A note about this seems reasonable.

> 4. The document doesn't touch on simultaneous bindings and I think it
> should. Some enterprises treat the internal wireless access networks
> similar to untrusted networks (thereby requiring a VPN over it) and it
> is quite common to have simultaneous wired and wireless connectivity.
> One of those may be routed through a VPN, while the other may be routed=

> directly. Is the MN allowed to register both interfaces with the HA?
> Unfortunately, the only form of simultaneous bindings supported by
> RFC3344 is bicasting, which is not-so-desirable here, since, there may
> be long periods of time when wired and wireless interfaces are
> simultaneously active. So, perhaps the right thing to do is to recommen=
d
> against simultaneous bindings, but, I'm not sure.=20

I guess a note about this could be added, too.

> 5. Is a scenario where an MN may connect via a cellular network in scop=
e
> for the document? If so, there are a couple of cases to consider here.
> The cellular network may be offering MIP separately. This is not an
> issue when the MIP client for the cellular network is in the cellular
> modem. But, when the MIP client in the host attempts to handle that
> mobility as well, there might be a problem. This leads to a
> MIP-IPsec-MIP layering, which I'm not sure we want to get into :) May b=
e
> we need to say that it is out of scope, but I'd like to hear other view=
s
> on this.=20

I don't see the problem.  If a MIP client in the cellular modem provides
what is (to it) a stable inner IP address, it does so completely
transparently to the IPsec and inner nested MIP tunnel, resulting in
less IP address changes for the IPsec.  So?  This is essentially an
application of RFC 4093 and should be unproblematic.



	Henrik


--------------enigF9C4FA35ACC886E279333E82
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iD8DBQFFgC0EeVhrtTJkXCMRAmdOAJ9n1UiBoplur5dLag1mSAhROueKQgCg0C7A
IFJYko7aXomrxtCDQQ9Mxf8=
=ltlM
-----END PGP SIGNATURE-----

--------------enigF9C4FA35ACC886E279333E82--


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

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

--===============0042346302==--




From mip4-bounces@ietf.org Wed Dec 13 12:29:39 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GuXv9-0005Ym-0D; Wed, 13 Dec 2006 12:29:31 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GuXv8-0005YF-EL
	for mip4@ietf.org; Wed, 13 Dec 2006 12:29:30 -0500
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GuXv4-0008QS-P8
	for mip4@ietf.org; Wed, 13 Dec 2006 12:29:30 -0500
Received: from crowley.qualcomm.com (crowley.qualcomm.com [129.46.61.151])
	by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	kBDHTPWf027212
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Wed, 13 Dec 2006 09:29:25 -0800
Received: from SANEXCAS02.na.qualcomm.com (sanexcas02.qualcomm.com
	[172.30.36.176])
	by crowley.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	kBDHTK1m025921; Wed, 13 Dec 2006 09:29:24 -0800 (PST)
Received: from NAEX13.na.qualcomm.com ([129.46.51.248]) by
	SANEXCAS02.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 13 Dec 2006 09:29:17 -0800
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
Subject: RE: [Mip4] WGLC Comments: draft-ietf-mip4-mobike-connectivity-01.txt
Date: Wed, 13 Dec 2006 09:29:16 -0800
Message-ID: <C24CB51D5AA800449982D9BCB903251335E865@NAEX13.na.qualcomm.com>
In-Reply-To: <45802D03.6020404@levkowetz.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip4] WGLC Comments: draft-ietf-mip4-mobike-connectivity-01.txt
Thread-Index: Acce1uE6/GnktGDcTWWG2oYRt+gUogAA92Qg
From: "Narayanan, Vidya" <vidyan@qualcomm.com>
To: "Henrik Levkowetz" <henrik@levkowetz.com>
X-OriginalArrivalTime: 13 Dec 2006 17:29:17.0993 (UTC)
	FILETIME=[37BA1990:01C71EDC]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0e9ebc0cbd700a87c0637ad0e2c91610
Cc: Mobile IPv4 Mailing List <mip4@ietf.org>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

=20

> -----Original Message-----
> From: Henrik Levkowetz [mailto:henrik@levkowetz.com]=20
> Sent: Wednesday, December 13, 2006 8:41 AM
> To: Narayanan, Vidya
> Cc: Mobile IPv4 Mailing List
> Subject: Re: [Mip4] WGLC Comments:=20
> draft-ietf-mip4-mobike-connectivity-01.txt
>=20
>=20
>=20
> on 2006-12-13 08:33 Narayanan, Vidya said the following:
> > Overall, I support advancing this draft. But, I think it=20
> requires some=20
> > clarifications.
> >=20
> > 1. The draft states:=20
> >=20
> > "The Mobile IP tunnel uses reverse tunneling through the
> >    home agent [8]."
> >=20
> >>From this, it is not clear if reverse tunneling is mandated or not.=20
> >>This
> > should be clarified.
>=20
> This is part of a solution overview, and as such is perfectly=20
> clear to me
> - it simply says that the solution uses reverse tunnelling=20
> through the home agent.  Nothing to clarify.
>=20

I'm not saying that it needs to be clarified in the overview, but there
is no clarification on it elsewhere either. If the MN is allowed normal
RFC3344 behavior (where reverse tunneling is optional), nothing needs to
be said. But, as I state below, when a VPN is used, I think reverse
tunneling should be mandatory. Or at least, it should be noted that if
reverse tunneling is not used, packets will be dropped by the VPN GW.

> > When using the HoA for communication, reverse tunneling=20
> probably needs=20
> > to be mandated when accessing via a VPN - otherwise, the VPN GW is=20
> > going to drop the packets. If the VPN is set up to bypass=20
> such packets=20
> > as well, it will work, if the HoA is a routable address and=20
> if there=20
> > is no ingress filtering on the local network. But, I'm not sure we=20
> > need to allow such a scenario. Alternately, the MN may use=20
> its VPN TIA=20
> > for communication.
> >=20
> > 2. For crossing security boundaries, the document states:=20
> >=20
> > "   If the mobile node has an existing VPN tunnel to its=20
> VPN gateway, it
> >    MUST send a MOBIKE message at the same time as the registration
> >    request to the i-HA whenever the IP address changes.  If=20
> the mobile
> >    node receives a response from the VPN gateway, but not=20
> from the i-HA,
> >    it assumes it is outside the enterprise network.  If it=20
> receives a
> >    response from the i-HA, then it assumes it is inside the=20
> enterprise
> >    network."
> >=20
> > I don't understand this.
>=20
> Seems clear enough to me.
>=20
> > I don't think it is trivial to bypass the VPN to send a MIP=20
> RRQ, when=20
> > the tunnel outer address is changing and a MOBIKE exchange has been=20
> > initiated. This would involve dynamically changing the bypass rules=20
> > for the VPN - in fact, it's not clear to me how such a rule=20
> might even=20
> > work. Obviously, UDP port 434 messages cannot always be allowed to=20
> > bypass IPsec. "Bypass UDP port 434 traffic when a link change just=20
> > occurred" doesn't quite work. If the MN is using a CCoA,=20
> "bypass UDP=20
> > port 434 traffic when IP source =3D local address" might=20
> work, but, it=20
> > won't work when the MN is using an FA CoA. Also, if the MN=20
> discovered=20
> > an FA on the local network, how does it know whether or not=20
> to use it?=20
> > It needs to not use it if that subnet is part of an=20
> untrusted network.=20
> > I understand that the motivation is to allow an operation=20
> with lower=20
> > latency, but, I am confused as to how this works.
>=20
> It seems to me that a rule to permit traffic to a specific=20
> host address and port is trivial to implement.  What's so=20
> hard about that?
>=20

UDP port 434 traffic to HA cannot always be bypassed and that's the
problem. We want to selectively bypass it only when a subnet change just
occurred - I don't see how there is a good way to do that. At other
times, you want to send MIP RRQs through the VPN tunnel (to register the
TIA as the CoA, for instance).=20

> > In fact, I think it is simplest to state that the detection=20
> of trusted=20
> > networks is done by out-of-band mechanisms and that if=20
> there is a VPN=20
> > tunnel, that is always used. If we attempt to solve it as in the=20
> > draft, we need a lot more clarity on the following:
>=20
> How to do the inside-outside detection isn't trivial, on the=20
> other hand, so there is clear value in defining it. =20
> Declaring it undefined doesn't help.
>=20
> > - What bypass rules are to be used for IPsec? I don't think=20
> > hand-waving this is good.
> > - Is the MN allowed to use an FA upon a subnet change? Is this the=20
> > same behavior whether the MN is moving from an untrusted or=20
> trusted network?
> > - If the MN used an FA, but discovers it is on an untrusted=20
> network,=20
> > it needs to then obtain a local address to set up a VPN.
>=20
> Since the text you're criticizing already states clearly that=20
> a local address has been acquired, this is not particularly=20
> relevant. =20

That is the point - it says "a local address has been acquired" without
stating implications of "what if there was an FA the MN found". Given
that FAs in trusted networks are allowed by the solution, that behavior
needs to be clarified.=20

> Sending a RRQ to the i-HA using the acquired local=20
> address constitutes a simple and feasible test of=20
> inside/outsideness, and that's what's desired here.
>=20
<snip>

>=20
> > 5. Is a scenario where an MN may connect via a cellular network in=20
> > scope for the document? If so, there are a couple of cases=20
> to consider here.
> > The cellular network may be offering MIP separately. This is not an=20
> > issue when the MIP client for the cellular network is in=20
> the cellular=20
> > modem. But, when the MIP client in the host attempts to handle that=20
> > mobility as well, there might be a problem. This leads to a=20
> > MIP-IPsec-MIP layering, which I'm not sure we want to get=20
> into :) May=20
> > be we need to say that it is out of scope, but I'd like to=20
> hear other=20
> > views on this.
>=20
> I don't see the problem.  If a MIP client in the cellular=20
> modem provides what is (to it) a stable inner IP address, it=20
> does so completely transparently to the IPsec and inner=20
> nested MIP tunnel, resulting in less IP address changes for=20
> the IPsec.  So?  This is essentially an application of RFC=20
> 4093 and should be unproblematic.
>=20

I already said that if the MIP client is in the modem, it is not an
issue. It is an issue when the MIP client in the host is expected to
handle MIP for cellular access too - I don't think this model is
deployed today, but, as cellular networks adopt various access
technologies (WLAN, WiMAX, etc.), this model has to change, if mobility
across the interfaces is needed. In that case, it does become an issue.=20

Regards,
Vidya

>=20
>=20
> 	Henrik
>=20
>=20

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Wed Dec 13 13:33:28 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GuYv2-0006ML-H4; Wed, 13 Dec 2006 13:33:28 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GuYv0-0006JL-7D
	for mip4@ietf.org; Wed, 13 Dec 2006 13:33:26 -0500
Received: from av6-1-sn3.vrr.skanova.net ([81.228.9.179])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GuYgS-0001u5-Ld
	for mip4@ietf.org; Wed, 13 Dec 2006 13:18:26 -0500
Received: by av6-1-sn3.vrr.skanova.net (Postfix, from userid 502)
	id CCA333819D; Wed, 13 Dec 2006 19:18:21 +0100 (CET)
Received: from smtp3-2-sn3.vrr.skanova.net (smtp3-2-sn3.vrr.skanova.net
	[81.228.9.102]) by av6-1-sn3.vrr.skanova.net (Postfix) with ESMTP
	id A66733815B; Wed, 13 Dec 2006 19:18:21 +0100 (CET)
Received: from shiraz.levkowetz.com (81-232-110-214-no16.tbcn.telia.com
	[81.232.110.214])
	by smtp3-2-sn3.vrr.skanova.net (Postfix) with ESMTP id C527837E4E;
	Wed, 13 Dec 2006 19:18:20 +0100 (CET)
Received: from localhost ([127.0.0.1])
	by shiraz.levkowetz.com with esmtp (Exim 4.63)
	(envelope-from <henrik@levkowetz.com>)
	id 1GuYgO-00038B-9Q; Wed, 13 Dec 2006 19:18:20 +0100
Message-ID: <458043E9.4000304@levkowetz.com>
Date: Wed, 13 Dec 2006 19:18:17 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Thunderbird 1.5.0.8 (Macintosh/20061025)
MIME-Version: 1.0
To: "Narayanan, Vidya" <vidyan@qualcomm.com>
Subject: Re: [Mip4] WGLC Comments: draft-ietf-mip4-mobike-connectivity-01.txt
References: <C24CB51D5AA800449982D9BCB903251335E865@NAEX13.na.qualcomm.com>
In-Reply-To: <C24CB51D5AA800449982D9BCB903251335E865@NAEX13.na.qualcomm.com>
X-Enigmail-Version: 0.94.1.2
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: vidyan@qualcomm.com, mip4@ietf.org,
	henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on shiraz.levkowetz.com);
	SAEximRunCond expanded to false
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 42e3ed3f10a1d8bef690f09da16f507a
Cc: Mobile IPv4 Mailing List <mip4@ietf.org>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1637266033=="
Errors-To: mip4-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============1637266033==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enigC3977E877A7581E526604C8B"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigC3977E877A7581E526604C8B
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable


on 2006-12-13 18:29 Narayanan, Vidya said the following:
=2E..
>>=20
>> on 2006-12-13 08:33 Narayanan, Vidya said the following:
>> > Overall, I support advancing this draft. But, I think it=20
>> requires some=20
>> > clarifications.
>> >=20
>> > 1. The draft states:=20
>> >=20
>> > "The Mobile IP tunnel uses reverse tunneling through the
>> >    home agent [8]."
>> >=20
>> >>From this, it is not clear if reverse tunneling is mandated or not. =

>> >>This
>> > should be clarified.
>>=20
>> This is part of a solution overview, and as such is perfectly=20
>> clear to me
>> - it simply says that the solution uses reverse tunnelling=20
>> through the home agent.  Nothing to clarify.
>>=20
>=20
> I'm not saying that it needs to be clarified in the overview, but there=

> is no clarification on it elsewhere either. If the MN is allowed normal=

> RFC3344 behavior (where reverse tunneling is optional), nothing needs t=
o
> be said. But, as I state below, when a VPN is used, I think reverse
> tunneling should be mandatory. Or at least, it should be noted that if
> reverse tunneling is not used, packets will be dropped by the VPN GW.

Ok, that makes sense.

[snip]
>>=20
>> It seems to me that a rule to permit traffic to a specific=20
>> host address and port is trivial to implement.  What's so=20
>> hard about that?
>>=20
>=20
> UDP port 434 traffic to HA cannot always be bypassed and that's the
> problem. We want to selectively bypass it only when a subnet change jus=
t
> occurred - I don't see how there is a good way to do that. At other
> times, you want to send MIP RRQs through the VPN tunnel (to register th=
e
> TIA as the CoA, for instance).=20

There's no need to create time-dependent or conditional rules here.
Any port 434 from TIA to HA goes through the tunnel.  Any port 434
to HA from other addresses doesn't.

[snip]=20
>=20
> That is the point - it says "a local address has been acquired" without=

> stating implications of "what if there was an FA the MN found". Given
> that FAs in trusted networks are allowed by the solution, that behavior=

> needs to be clarified.=20

The inside-outside detection mechanism is described in more detail
in http://tools.ietf.org/html/draft-ietf-mip4-vpn-problem-solution,
if I remember correctly.  If so, a reference to it might help.  If
the text can be read as if you could send the detection registration
to an FA instead of the HA, it should be clarified, although I have
a hard time reading it that way.

>> Sending a RRQ to the i-HA using the acquired local=20
>> address constitutes a simple and feasible test of=20
>> inside/outsideness, and that's what's desired here.
>>=20
> <snip>
>=20
>>=20
>> > 5. Is a scenario where an MN may connect via a cellular network in=20
>> > scope for the document? If so, there are a couple of cases=20
>> to consider here.
>> > The cellular network may be offering MIP separately. This is not an =

>> > issue when the MIP client for the cellular network is in=20
>> the cellular=20
>> > modem. But, when the MIP client in the host attempts to handle that =

>> > mobility as well, there might be a problem. This leads to a=20
>> > MIP-IPsec-MIP layering, which I'm not sure we want to get=20
>> into :) May=20
>> > be we need to say that it is out of scope, but I'd like to=20
>> hear other=20
>> > views on this.
>>=20
>> I don't see the problem.  If a MIP client in the cellular=20
>> modem provides what is (to it) a stable inner IP address, it=20
>> does so completely transparently to the IPsec and inner=20
>> nested MIP tunnel, resulting in less IP address changes for=20
>> the IPsec.  So?  This is essentially an application of RFC=20
>> 4093 and should be unproblematic.
>>=20
>=20
> I already said that if the MIP client is in the modem, it is not an
> issue. It is an issue when the MIP client in the host is expected to
> handle MIP for cellular access too - I don't think this model is
> deployed today, but, as cellular networks adopt various access
> technologies (WLAN, WiMAX, etc.), this model has to change, if mobility=

> across the interfaces is needed. In that case, it does become an issue.=


But then this draft still isn't relevant -- you're still back in the=20
RFC 4093 scenario, and the solution of draft-ietf-mip4-vpn-problem-soluti=
on
applies, no?


	Henrik








--------------enigC3977E877A7581E526604C8B
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iD8DBQFFgEPpeVhrtTJkXCMRAip6AKC/ZbXt6iYaPStVWO+m5vEyxXGyOgCg4xpI
KKauowwDSevRzmNlIjfF2Tw=
=w9dD
-----END PGP SIGNATURE-----

--------------enigC3977E877A7581E526604C8B--


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

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

--===============1637266033==--




From mip4-bounces@ietf.org Wed Dec 13 14:30:34 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GuZoD-0002p4-Nu; Wed, 13 Dec 2006 14:30:29 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GuZoC-0002ot-VS
	for mip4@ietf.org; Wed, 13 Dec 2006 14:30:28 -0500
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GuZoA-0000EF-D1
	for mip4@ietf.org; Wed, 13 Dec 2006 14:30:28 -0500
Received: from crowley.qualcomm.com (crowley.qualcomm.com [129.46.61.151])
	by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	kBDJUOqV009212
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Wed, 13 Dec 2006 11:30:25 -0800
Received: from sanexcas01.na.qualcomm.com (sanexcas01.qualcomm.com
	[172.30.36.175])
	by crowley.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	kBDJUJXx015044; Wed, 13 Dec 2006 11:30:23 -0800 (PST)
Received: from NAEX13.na.qualcomm.com ([129.46.51.248]) by
	sanexcas01.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 13 Dec 2006 11:30:16 -0800
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
Subject: RE: [Mip4] WGLC Comments: draft-ietf-mip4-mobike-connectivity-01.txt
Date: Wed, 13 Dec 2006 11:30:16 -0800
Message-ID: <C24CB51D5AA800449982D9BCB903251335E896@NAEX13.na.qualcomm.com>
In-Reply-To: <458043E9.4000304@levkowetz.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip4] WGLC Comments: draft-ietf-mip4-mobike-connectivity-01.txt
Thread-Index: Acce4xgKEWW8evgsTTS7XHHGEkMC+gAA8dMw
From: "Narayanan, Vidya" <vidyan@qualcomm.com>
To: "Henrik Levkowetz" <henrik@levkowetz.com>
X-OriginalArrivalTime: 13 Dec 2006 19:30:16.0848 (UTC)
	FILETIME=[1E577900:01C71EED]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3a4bc66230659131057bb68ed51598f8
Cc: Mobile IPv4 Mailing List <mip4@ietf.org>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

> >>=20
> >=20
> > UDP port 434 traffic to HA cannot always be bypassed and that's the=20
> > problem. We want to selectively bypass it only when a subnet change=20
> > just occurred - I don't see how there is a good way to do that. At=20
> > other times, you want to send MIP RRQs through the VPN tunnel (to=20
> > register the TIA as the CoA, for instance).
>=20
> There's no need to create time-dependent or conditional rules here.
> Any port 434 from TIA to HA goes through the tunnel.  Any=20
> port 434 to HA from other addresses doesn't.
>=20

I don't believe RFC4301 allows this sort of SPD rules set up. The IP
address cannot be a variable in the SPD. Here, the local address of the
MN is changing every time. So, this involves dynamically updating the
SPD value to create a bypass rule for the acquired address and then
sending the RRQ - however, MNs almost never have admin access to create
such SPD rules and I think it would create a security vulnerability to
enable something like this in software.=20

> [snip]=20
> >=20
> > That is the point - it says "a local address has been acquired"=20
> > without stating implications of "what if there was an FA the MN=20
> > found". Given that FAs in trusted networks are allowed by the=20
> > solution, that behavior needs to be clarified.
>=20
> The inside-outside detection mechanism is described in more=20
> detail in=20
> http://tools.ietf.org/html/draft-ietf-mip4-vpn-problem-solution,
> if I remember correctly.  If so, a reference to it might=20
> help.  If the text can be read as if you could send the=20
> detection registration to an FA instead of the HA, it should=20
> be clarified, although I have a hard time reading it that way.
>=20

Perhaps, we are talking about different things here. My question is
basically this - when the MN changed subnets, it doesn't know if that is
a trusted or untrusted subnet; if it sees an FA on that subnet, should
it use that FA, assuming it is a trusted subnet first or should it
ignore that and acquire an address to use as CCoA? If the subnet ends up
being trusted, it could be using that FA without a problem. If not, that
address has to be the VPN tunnel outer address.=20

If an MN is configured to always use an FA CoA mode within the trusted
network and CCoA mode only when the VPN TIA is used as the CoA, it poses
a problem.=20

> >> Sending a RRQ to the i-HA using the acquired local address=20
> >> constitutes a simple and feasible test of inside/outsideness, and=20
> >> that's what's desired here.
> >>=20
> > <snip>
> >=20
> >>=20
> >> > 5. Is a scenario where an MN may connect via a cellular=20
> network in=20
> >> > scope for the document? If so, there are a couple of cases
> >> to consider here.
> >> > The cellular network may be offering MIP separately.=20
> This is not an=20
> >> > issue when the MIP client for the cellular network is in
> >> the cellular
> >> > modem. But, when the MIP client in the host attempts to=20
> handle that=20
> >> > mobility as well, there might be a problem. This leads to a=20
> >> > MIP-IPsec-MIP layering, which I'm not sure we want to get
> >> into :) May
> >> > be we need to say that it is out of scope, but I'd like to
> >> hear other
> >> > views on this.
> >>=20
> >> I don't see the problem.  If a MIP client in the cellular modem=20
> >> provides what is (to it) a stable inner IP address, it does so=20
> >> completely transparently to the IPsec and inner nested MIP tunnel,=20
> >> resulting in less IP address changes for the IPsec.  So?  This is=20
> >> essentially an application of RFC
> >> 4093 and should be unproblematic.
> >>=20
> >=20
> > I already said that if the MIP client is in the modem, it is not an=20
> > issue. It is an issue when the MIP client in the host is=20
> expected to=20
> > handle MIP for cellular access too - I don't think this model is=20
> > deployed today, but, as cellular networks adopt various access=20
> > technologies (WLAN, WiMAX, etc.), this model has to change, if=20
> > mobility across the interfaces is needed. In that case, it=20
> does become an issue.
>=20
> But then this draft still isn't relevant -- you're still back=20
> in the RFC 4093 scenario, and the solution of=20
> draft-ietf-mip4-vpn-problem-solution
> applies, no?
>=20

Hmmm.. I'm not sure. The solution in
draft-ietf-mip4-vpn-problem-solution assumes that the external HA is
part of the enterprise network and handles mobility for all types of
external connectivity. However, in the case under discussion here, the
cellular HA will handle mobility only for the cellular access networks;
there may be other untrusted networks that the MN has to support without
that HA.=20

Here's a scenario:=20

Let's say that a laptop is connected via ethernet to the intranet, via
WLAN to an untrusted AP and via a data card to a cellular network. It
must now do - direct MIP4 to the i-HA on ethernet, MOBIKE over WLAN, and
MIP-IPsec-MIP (no MOBIKE) on the cellular interface. Alternately, it may
ignore the cellular MIP service and just do MOBIKE with the corporate
VPN GW even over the cellular interface, but I am not sure that is a
practical option, given that there may be times when it is good to use
the available cellular mobility service and that in order to use other
services in the cellular network, it may have to use MIP as well.=20

Vidya
=20

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Wed Dec 13 15:16:09 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GuaWJ-0001bF-MQ; Wed, 13 Dec 2006 15:16:03 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GuaWI-0001bA-RK
	for mip4@ietf.org; Wed, 13 Dec 2006 15:16:02 -0500
Received: from av9-2-sn2.hy.skanova.net ([81.228.8.180])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GuaWG-0006AP-27
	for mip4@ietf.org; Wed, 13 Dec 2006 15:16:02 -0500
Received: by av9-2-sn2.hy.skanova.net (Postfix, from userid 502)
	id F3B4B385B3; Wed, 13 Dec 2006 21:15:58 +0100 (CET)
Received: from smtp4-1-sn2.hy.skanova.net (smtp4-1-sn2.hy.skanova.net
	[81.228.8.92]) by av9-2-sn2.hy.skanova.net (Postfix) with ESMTP
	id CEA2D3815D; Wed, 13 Dec 2006 21:15:58 +0100 (CET)
Received: from shiraz.levkowetz.com (81-232-110-214-no16.tbcn.telia.com
	[81.232.110.214])
	by smtp4-1-sn2.hy.skanova.net (Postfix) with ESMTP id A4B7737E53;
	Wed, 13 Dec 2006 21:15:58 +0100 (CET)
Received: from localhost ([127.0.0.1])
	by shiraz.levkowetz.com with esmtp (Exim 4.63)
	(envelope-from <henrik@levkowetz.com>)
	id 1GuaWD-0007cJ-MM; Wed, 13 Dec 2006 21:15:57 +0100
Message-ID: <45805F79.9000908@levkowetz.com>
Date: Wed, 13 Dec 2006 21:15:53 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Thunderbird 1.5.0.8 (Macintosh/20061025)
MIME-Version: 1.0
To: "Narayanan, Vidya" <vidyan@qualcomm.com>
Subject: Re: [Mip4] WGLC Comments: draft-ietf-mip4-mobike-connectivity-01.txt
References: <C24CB51D5AA800449982D9BCB903251335E896@NAEX13.na.qualcomm.com>
In-Reply-To: <C24CB51D5AA800449982D9BCB903251335E896@NAEX13.na.qualcomm.com>
X-Enigmail-Version: 0.94.1.2
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: vidyan@qualcomm.com, mip4@ietf.org,
	henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on shiraz.levkowetz.com);
	SAEximRunCond expanded to false
X-Spam-Score: 0.1 (/)
X-Scan-Signature: ded6070f7eed56e10c4f4d0d5043d9c7
Cc: Mobile IPv4 Mailing List <mip4@ietf.org>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0138172325=="
Errors-To: mip4-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============0138172325==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enigACDB0FED1AB1167242BBB332"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigACDB0FED1AB1167242BBB332
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable


on 2006-12-13 20:30 Narayanan, Vidya said the following:
>> >>=20
>> >=20
>> > UDP port 434 traffic to HA cannot always be bypassed and that's the =

>> > problem. We want to selectively bypass it only when a subnet change =

>> > just occurred - I don't see how there is a good way to do that. At=20
>> > other times, you want to send MIP RRQs through the VPN tunnel (to=20
>> > register the TIA as the CoA, for instance).
>>=20
>> There's no need to create time-dependent or conditional rules here.
>> Any port 434 from TIA to HA goes through the tunnel.  Any=20
>> port 434 to HA from other addresses doesn't.
>>=20
>=20
> I don't believe RFC4301 allows this sort of SPD rules set up. The IP
> address cannot be a variable in the SPD. Here, the local address of the=

> MN is changing every time.

No, how do you figure that?  As soon as the VPN is set up, TIA is stable,=

the local address of the MN is the TIA and is stable, and there's no need=

to change the rule setup.

> So, this involves dynamically updating the
> SPD value to create a bypass rule for the acquired address and then
> sending the RRQ - however, MNs almost never have admin access to create=

> such SPD rules and I think it would create a security vulnerability to
> enable something like this in software.=20

See above.  There's no need for dynamic rule update.

>> [snip]=20
>> >=20
>> > That is the point - it says "a local address has been acquired"=20
>> > without stating implications of "what if there was an FA the MN=20
>> > found". Given that FAs in trusted networks are allowed by the=20
>> > solution, that behavior needs to be clarified.
>>=20
>> The inside-outside detection mechanism is described in more=20
>> detail in=20
>> http://tools.ietf.org/html/draft-ietf-mip4-vpn-problem-solution,
>> if I remember correctly.  If so, a reference to it might=20
>> help.  If the text can be read as if you could send the=20
>> detection registration to an FA instead of the HA, it should=20
>> be clarified, although I have a hard time reading it that way.
>>=20
>=20
> Perhaps, we are talking about different things here. My question is
> basically this - when the MN changed subnets, it doesn't know if that i=
s
> a trusted or untrusted subnet; if it sees an FA on that subnet, should
> it use that FA, assuming it is a trusted subnet first or should it
> ignore that and acquire an address to use as CCoA? If the subnet ends u=
p
> being trusted, it could be using that FA without a problem. If not, tha=
t
> address has to be the VPN tunnel outer address.=20

Checking draft-ietf-mip4-vpn-problem-solution, we find that this is
all very clearly described there, so I'd suggest that referencing that
draft would provide answers to all of the above. =20

> If an MN is configured to always use an FA CoA mode within the trusted
> network and CCoA mode only when the VPN TIA is used as the CoA, it pose=
s
> a problem.=20

In that case, you'll of course have to complete the inside-outside
determination first, and then re-register if you haven't registered
according to this configuration.  (I've not come across clients with
rules like this, though.)

>> >> Sending a RRQ to the i-HA using the acquired local address=20
>> >> constitutes a simple and feasible test of inside/outsideness, and=20
>> >> that's what's desired here.
>> >>=20
>> > <snip>
>> >=20
>> >>=20
>> >> > 5. Is a scenario where an MN may connect via a cellular=20
>> network in=20
>> >> > scope for the document? If so, there are a couple of cases
>> >> to consider here.
>> >> > The cellular network may be offering MIP separately.=20
>> This is not an=20
>> >> > issue when the MIP client for the cellular network is in
>> >> the cellular
>> >> > modem. But, when the MIP client in the host attempts to=20
>> handle that=20
>> >> > mobility as well, there might be a problem. This leads to a=20
>> >> > MIP-IPsec-MIP layering, which I'm not sure we want to get
>> >> into :) May
>> >> > be we need to say that it is out of scope, but I'd like to
>> >> hear other
>> >> > views on this.
>> >>=20
>> >> I don't see the problem.  If a MIP client in the cellular modem=20
>> >> provides what is (to it) a stable inner IP address, it does so=20
>> >> completely transparently to the IPsec and inner nested MIP tunnel, =

>> >> resulting in less IP address changes for the IPsec.  So?  This is=20
>> >> essentially an application of RFC
>> >> 4093 and should be unproblematic.
>> >>=20
>> >=20
>> > I already said that if the MIP client is in the modem, it is not an =

>> > issue. It is an issue when the MIP client in the host is=20
>> expected to=20
>> > handle MIP for cellular access too - I don't think this model is=20
>> > deployed today, but, as cellular networks adopt various access=20
>> > technologies (WLAN, WiMAX, etc.), this model has to change, if=20
>> > mobility across the interfaces is needed. In that case, it=20
>> does become an issue.
>>=20
>> But then this draft still isn't relevant -- you're still back=20
>> in the RFC 4093 scenario, and the solution of=20
>> draft-ietf-mip4-vpn-problem-solution
>> applies, no?
>>=20
>=20
> Hmmm.. I'm not sure. The solution in
> draft-ietf-mip4-vpn-problem-solution assumes that the external HA is
> part of the enterprise network and handles mobility for all types of
> external connectivity. However, in the case under discussion here, the
> cellular HA will handle mobility only for the cellular access networks;=

> there may be other untrusted networks that the MN has to support withou=
t
> that HA.=20
>=20
> Here's a scenario:=20
>=20
> Let's say that a laptop is connected via ethernet to the intranet, via
> WLAN to an untrusted AP and via a data card to a cellular network. It
> must now do - direct MIP4 to the i-HA on ethernet, MOBIKE over WLAN, an=
d
> MIP-IPsec-MIP (no MOBIKE) on the cellular interface. Alternately, it ma=
y
> ignore the cellular MIP service and just do MOBIKE with the corporate
> VPN GW even over the cellular interface, but I am not sure that is a
> practical option, given that there may be times when it is good to use
> the available cellular mobility service and that in order to use other
> services in the cellular network, it may have to use MIP as well.=20

This means that it has a double-MIP client setup according to
draft-ietf-mip4-vpn-problem-solution when it is using IPsec over MIP
over cellular; the IPsec TIA from this setup is available to the
inner MIP client in the same way as the local address from the WLAN
and the MOBIKE TIA.

Yes, it is complex, but no, I don't see that we're missing any
components here...


	Henrik


--------------enigACDB0FED1AB1167242BBB332
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iD8DBQFFgF95eVhrtTJkXCMRAoZrAJ0Z+ikHzkONZVf46pzN+n/wjwDaMgCg4LMQ
fr9BmQrFyDhUtwrRjC0hs2w=
=/opJ
-----END PGP SIGNATURE-----

--------------enigACDB0FED1AB1167242BBB332--


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

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

--===============0138172325==--




From mip4-bounces@ietf.org Wed Dec 13 15:42:10 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GuavR-0005Rv-SY; Wed, 13 Dec 2006 15:42:01 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GuavR-0005Rq-8X
	for mip4@ietf.org; Wed, 13 Dec 2006 15:42:01 -0500
Received: from ithilien.qualcomm.com ([129.46.51.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GuavP-0001TC-QF
	for mip4@ietf.org; Wed, 13 Dec 2006 15:42:01 -0500
Received: from magus.qualcomm.com (magus.qualcomm.com [129.46.61.148])
	by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	kBDKfv9H019345
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Wed, 13 Dec 2006 12:41:58 -0800
Received: from SANEXCAS02.na.qualcomm.com (sanexcas02.qualcomm.com
	[172.30.36.176])
	by magus.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id kBDKfuho005295; 
	Wed, 13 Dec 2006 12:41:57 -0800 (PST)
Received: from NAEX13.na.qualcomm.com ([129.46.51.248]) by
	SANEXCAS02.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 13 Dec 2006 12:41:56 -0800
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
Subject: RE: [Mip4] WGLC Comments: draft-ietf-mip4-mobike-connectivity-01.txt
Date: Wed, 13 Dec 2006 12:41:56 -0800
Message-ID: <C24CB51D5AA800449982D9BCB903251335E8B0@NAEX13.na.qualcomm.com>
In-Reply-To: <45805F79.9000908@levkowetz.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip4] WGLC Comments: draft-ietf-mip4-mobike-connectivity-01.txt
Thread-Index: Acce85YxFwsYgyucTauRCzC+1156HgAAZ/SA
From: "Narayanan, Vidya" <vidyan@qualcomm.com>
To: "Henrik Levkowetz" <henrik@levkowetz.com>
X-OriginalArrivalTime: 13 Dec 2006 20:41:56.0236 (UTC)
	FILETIME=[20FA04C0:01C71EF7]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4
Cc: Mobile IPv4 Mailing List <mip4@ietf.org>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org


<snip>

> >=20
> > I don't believe RFC4301 allows this sort of SPD rules set=20
> up. The IP=20
> > address cannot be a variable in the SPD. Here, the local address of=20
> > the MN is changing every time.
>=20
> No, how do you figure that?  As soon as the VPN is set up,=20
> TIA is stable, the local address of the MN is the TIA and is=20
> stable, and there's no need to change the rule setup.
>=20

No, this is not correct. When the MN is trying to register the TIA as
the CoA, it always goes through the VPN - there is no confusion there.
It is the case where the MN has a VPN, but has changed subnets and is
trying to determine the direct reachability of the HA on that subnet -
here, it will attempt to register the newly acquired local address with
the HA to determine if that address can be treated as a MIP CCoA
(trusted network case) or it needs to be treated as a VPN tunnel outer
address (untrusted network case) - so, the RRQ in discussion here is
sent not with the TIA, but with the newly acquired local address. Hence
the problem.=20

> > So, this involves dynamically updating the SPD value to create a=20
> > bypass rule for the acquired address and then sending the RRQ -=20
> > however, MNs almost never have admin access to create such=20
> SPD rules=20
> > and I think it would create a security vulnerability to enable=20
> > something like this in software.
>=20
> See above.  There's no need for dynamic rule update.
>=20

Please see above explanation.=20

> >> [snip]
> >> >=20
> >> > That is the point - it says "a local address has been acquired"=20
> >> > without stating implications of "what if there was an FA the MN=20
> >> > found". Given that FAs in trusted networks are allowed by the=20
> >> > solution, that behavior needs to be clarified.
> >>=20
> >> The inside-outside detection mechanism is described in=20
> more detail in=20
> >> http://tools.ietf.org/html/draft-ietf-mip4-vpn-problem-solution,
> >> if I remember correctly.  If so, a reference to it might help.  If=20
> >> the text can be read as if you could send the detection=20
> registration=20
> >> to an FA instead of the HA, it should be clarified,=20
> although I have a=20
> >> hard time reading it that way.
> >>=20
> >=20
> > Perhaps, we are talking about different things here. My question is=20
> > basically this - when the MN changed subnets, it doesn't=20
> know if that=20
> > is a trusted or untrusted subnet; if it sees an FA on that subnet,=20
> > should it use that FA, assuming it is a trusted subnet=20
> first or should=20
> > it ignore that and acquire an address to use as CCoA? If the subnet=20
> > ends up being trusted, it could be using that FA without a=20
> problem. If=20
> > not, that address has to be the VPN tunnel outer address.
>=20
> Checking draft-ietf-mip4-vpn-problem-solution, we find that=20
> this is all very clearly described there, so I'd suggest that=20
> referencing that draft would provide answers to all of the above. =20
>=20


Could you please point me to the section in
draft-ietf-mip4-vpn-problem-solution that points to that? Since that
solution uses MIP for both external and internal mobility, an MN can
always use an FA and it's not a problem. The problem arises here
because, the MN cannot use an FA for external mobility, but can do so
for internal mobility. I see this as a scenario specific to this
solution. What am I missing here?=20

<snip>

>=20
> This means that it has a double-MIP client setup according to=20
> draft-ietf-mip4-vpn-problem-solution when it is using IPsec=20
> over MIP over cellular; the IPsec TIA from this setup is=20
> available to the inner MIP client in the same way as the=20
> local address from the WLAN and the MOBIKE TIA.
>=20
> Yes, it is complex, but no, I don't see that we're missing=20
> any components here...
>=20

This draft starts off describing that it is an alternative to the double
MIP solution. But, it appears that in a particular scenario, the double
MIP solution needs to be employed even if the solution in this draft is
in use. That's why I wonder if it is worth describing it. I was not
claiming that there is a missing component - there is a missing
connection between the components.=20

Vidya

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Wed Dec 13 15:48:24 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gub1c-000842-R5; Wed, 13 Dec 2006 15:48:24 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gub1b-00080m-5P
	for mip4@ietf.org; Wed, 13 Dec 2006 15:48:23 -0500
Received: from roof.dave.sonera.fi ([131.177.130.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gub1W-0002Tc-FK
	for mip4@ietf.org; Wed, 13 Dec 2006 15:48:23 -0500
Received: from roof.dave.sonera.fi (localhost [127.0.0.1]) by
	roof.dave.sonera.fi (Sendmail) with ESMTP id kBDKmHtc016365 for
	<mip4@ietf.org>; Wed, 13 Dec 2006 22:48:17 +0200 (EET)
Received: from [131.177.105.121] (ws121.secureuser.sonera.fi
	[131.177.105.121]) by roof.dave.sonera.fi (Sendmail) with ESMTP
	id kBDKmAGa016345; Wed, 13 Dec 2006 22:48:10 +0200 (EET)
Message-ID: <4580670B.8070607@teliasonera.com>
Date: Wed, 13 Dec 2006 22:48:11 +0200
From: Jouni Korhonen <jouni.korhonen@teliasonera.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: "Narayanan, Vidya" <vidyan@qualcomm.com>
Subject: Re: [Mip4] WGLC Comments: draft-ietf-mip4-mobike-connectivity-01.txt
References: <C24CB51D5AA800449982D9BCB903251335E865@NAEX13.na.qualcomm.com>
In-Reply-To: <C24CB51D5AA800449982D9BCB903251335E865@NAEX13.na.qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.6 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: Mobile IPv4 Mailing List <mip4@ietf.org>,
	Henrik Levkowetz <henrik@levkowetz.com>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

[snip]
> 
> I already said that if the MIP client is in the modem, it is not an
> issue. It is an issue when the MIP client in the host is expected to
> handle MIP for cellular access too - I don't think this model is
> deployed today, but, as cellular networks adopt various access
> technologies (WLAN, WiMAX, etc.), this model has to change, if mobility
> across the interfaces is needed. In that case, it does become an issue. 

As this draft is mostly intended to enterprise use cases (where the 
enterprise runs its own HA and VPN gateway) I assume that the IT manager 
planning to roll out laptops with a mobility service would not select 
e.g. CMIP mode for the WiMAX access nor intentionally create overlapping 
mobility service solutions etc.

Cheers,
	Jouni


> 
> Regards,
> Vidya
> 
>>
>> 	Henrik
>>
>>
> 

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Wed Dec 13 16:36:18 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gubly-00028V-Nv; Wed, 13 Dec 2006 16:36:18 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gublx-00028B-Kw
	for mip4@ietf.org; Wed, 13 Dec 2006 16:36:17 -0500
Received: from av8-2-sn3.vrr.skanova.net ([81.228.9.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gublw-0002rR-1m
	for mip4@ietf.org; Wed, 13 Dec 2006 16:36:17 -0500
Received: by av8-2-sn3.vrr.skanova.net (Postfix, from userid 502)
	id 3B0C03861F; Wed, 13 Dec 2006 22:36:15 +0100 (CET)
Received: from smtp3-1-sn3.vrr.skanova.net (smtp3-1-sn3.vrr.skanova.net
	[81.228.9.101]) by av8-2-sn3.vrr.skanova.net (Postfix) with ESMTP
	id 151E337EB0; Wed, 13 Dec 2006 22:36:15 +0100 (CET)
Received: from shiraz.levkowetz.com (81-232-110-214-no16.tbcn.telia.com
	[81.232.110.214])
	by smtp3-1-sn3.vrr.skanova.net (Postfix) with ESMTP id 962D037E4F;
	Wed, 13 Dec 2006 22:36:14 +0100 (CET)
Received: from localhost ([127.0.0.1])
	by shiraz.levkowetz.com with esmtp (Exim 4.63)
	(envelope-from <henrik@levkowetz.com>)
	id 1Gublq-0003hQ-3i; Wed, 13 Dec 2006 22:36:10 +0100
Message-ID: <45807249.1090909@levkowetz.com>
Date: Wed, 13 Dec 2006 22:36:09 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Thunderbird 1.5.0.8 (Macintosh/20061025)
MIME-Version: 1.0
To: "Narayanan, Vidya" <vidyan@qualcomm.com>
Subject: Re: [Mip4] WGLC Comments: draft-ietf-mip4-mobike-connectivity-01.txt
References: <C24CB51D5AA800449982D9BCB903251335E8B0@NAEX13.na.qualcomm.com>
In-Reply-To: <C24CB51D5AA800449982D9BCB903251335E8B0@NAEX13.na.qualcomm.com>
X-Enigmail-Version: 0.94.1.2
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: vidyan@qualcomm.com, mip4@ietf.org,
	henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on shiraz.levkowetz.com);
	SAEximRunCond expanded to false
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 6ba8aaf827dcb437101951262f69b3de
Cc: Mobile IPv4 Mailing List <mip4@ietf.org>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1468923224=="
Errors-To: mip4-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============1468923224==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enigB1586BE99C86EFA7E09607B7"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigB1586BE99C86EFA7E09607B7
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable



on 2006-12-13 21:41 Narayanan, Vidya said the following:
> <snip>
>=20
>> >=20
>> > I don't believe RFC4301 allows this sort of SPD rules set=20
>> up. The IP=20
>> > address cannot be a variable in the SPD. Here, the local address of =

>> > the MN is changing every time.
>>=20
>> No, how do you figure that?  As soon as the VPN is set up,=20
>> TIA is stable, the local address of the MN is the TIA and is=20
>> stable, and there's no need to change the rule setup.
>>=20
>=20
> No, this is not correct. When the MN is trying to register the TIA as
> the CoA, it always goes through the VPN - there is no confusion there.
> It is the case where the MN has a VPN, but has changed subnets and is
> trying to determine the direct reachability of the HA on that subnet -
> here, it will attempt to register the newly acquired local address with=

> the HA to determine if that address can be treated as a MIP CCoA
> (trusted network case) or it needs to be treated as a VPN tunnel outer
> address (untrusted network case) - so, the RRQ in discussion here is
> sent not with the TIA, but with the newly acquired local address.

*Exactly*.  So rules which says that port 434 from TIA to HA always go
through the tunnel, port 434 from non-TIA to HA never goes to tunnel
will work.  No need for anything more complex.

> Hence
> the problem.=20

Nope, no problem :-)

>> > So, this involves dynamically updating the SPD value to create a=20
>> > bypass rule for the acquired address and then sending the RRQ -=20
>> > however, MNs almost never have admin access to create such=20
>> SPD rules=20
>> > and I think it would create a security vulnerability to enable=20
>> > something like this in software.
>>=20
>> See above.  There's no need for dynamic rule update.
>>=20
>=20
> Please see above explanation.=20

Again, there's no need for dynamic rule updates.

>> >> [snip]
>> >> >=20
>> >> > That is the point - it says "a local address has been acquired"=20
>> >> > without stating implications of "what if there was an FA the MN=20
>> >> > found". Given that FAs in trusted networks are allowed by the=20
>> >> > solution, that behavior needs to be clarified.
>> >>=20
>> >> The inside-outside detection mechanism is described in=20
>> more detail in=20
>> >> http://tools.ietf.org/html/draft-ietf-mip4-vpn-problem-solution,
>> >> if I remember correctly.  If so, a reference to it might help.  If =

>> >> the text can be read as if you could send the detection=20
>> registration=20
>> >> to an FA instead of the HA, it should be clarified,=20
>> although I have a=20
>> >> hard time reading it that way.
>> >>=20
>> >=20
>> > Perhaps, we are talking about different things here. My question is =

>> > basically this - when the MN changed subnets, it doesn't=20
>> know if that=20
>> > is a trusted or untrusted subnet; if it sees an FA on that subnet,=20
>> > should it use that FA, assuming it is a trusted subnet=20
>> first or should=20
>> > it ignore that and acquire an address to use as CCoA? If the subnet =

>> > ends up being trusted, it could be using that FA without a=20
>> problem. If=20
>> > not, that address has to be the VPN tunnel outer address.
>>=20
>> Checking draft-ietf-mip4-vpn-problem-solution, we find that=20
>> this is all very clearly described there, so I'd suggest that=20
>> referencing that draft would provide answers to all of the above. =20
>>=20
>=20
>=20
> Could you please point me to the section in
> draft-ietf-mip4-vpn-problem-solution that points to that? Since that
> solution uses MIP for both external and internal mobility, an MN can
> always use an FA and it's not a problem. The problem arises here
> because, the MN cannot use an FA for external mobility, but can do so
> for internal mobility. I see this as a scenario specific to this
> solution. What am I missing here?=20

You're missing that this is a specific mechanism to determine whether
you're inside or outside, and exactly how that is to be performed is
described in section 3, with handling of FAs (if you want to do that,
which I'd choose only doing when the previous connection was inside)
in subsection 3.4.

Once the inside-outside determination has been done, you can apply
policies or rules you have about exactly what's permitted / mandatory
in the different situations.  This may involve re-registration,
depending on your inside-outside determination implementation and
your policies.

> <snip>
>=20
>>=20
>> This means that it has a double-MIP client setup according to=20
>> draft-ietf-mip4-vpn-problem-solution when it is using IPsec=20
>> over MIP over cellular; the IPsec TIA from this setup is=20
>> available to the inner MIP client in the same way as the=20
>> local address from the WLAN and the MOBIKE TIA.
>>=20
>> Yes, it is complex, but no, I don't see that we're missing=20
>> any components here...
>>=20
>=20
> This draft starts off describing that it is an alternative to the doubl=
e
> MIP solution. But, it appears that in a particular scenario, the double=

> MIP solution needs to be employed even if the solution in this draft is=

> in use. That's why I wonder if it is worth describing it. I was not
> claiming that there is a missing component - there is a missing
> connection between the components.=20

Ok.  I'm fine with the current partition and description, but if the
authors want to update according to your suggestion, that's fine with
me too.


	Henrik


--------------enigB1586BE99C86EFA7E09607B7
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iD8DBQFFgHJJeVhrtTJkXCMRAletAJ0XcE5i0FL7iacyJ1ZQ0+wWIRYIogCgp4gL
jy73/4EZPlM4otkpMUx+Q2w=
=IShZ
-----END PGP SIGNATURE-----

--------------enigB1586BE99C86EFA7E09607B7--


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

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

--===============1468923224==--




From mip4-bounces@ietf.org Wed Dec 13 17:23:00 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GucV2-0005eM-Ga; Wed, 13 Dec 2006 17:22:52 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GucUz-0005ZL-Sv
	for mip4@ietf.org; Wed, 13 Dec 2006 17:22:49 -0500
Received: from ithilien.qualcomm.com ([129.46.51.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GucQn-0001AT-SM
	for mip4@ietf.org; Wed, 13 Dec 2006 17:18:35 -0500
Received: from magus.qualcomm.com (magus.qualcomm.com [129.46.61.148])
	by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	kBDMIRRr004316
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Wed, 13 Dec 2006 14:18:28 -0800
Received: from sanexcas01.na.qualcomm.com (sanexcas01.qualcomm.com
	[172.30.36.175])
	by magus.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id kBDMI3Ls012310; 
	Wed, 13 Dec 2006 14:18:26 -0800 (PST)
Received: from NAEX13.na.qualcomm.com ([129.46.51.248]) by
	sanexcas01.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 13 Dec 2006 14:18:23 -0800
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
Subject: RE: [Mip4] WGLC Comments: draft-ietf-mip4-mobike-connectivity-01.txt
Date: Wed, 13 Dec 2006 14:18:23 -0800
Message-ID: <C24CB51D5AA800449982D9BCB903251335E8E3@NAEX13.na.qualcomm.com>
In-Reply-To: <45807249.1090909@levkowetz.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip4] WGLC Comments: draft-ietf-mip4-mobike-connectivity-01.txt
Thread-Index: Acce/r3QlPvyMkxEQ5+1odQ5YhMT2gABHQ8g
From: "Narayanan, Vidya" <vidyan@qualcomm.com>
To: "Henrik Levkowetz" <henrik@levkowetz.com>
X-OriginalArrivalTime: 13 Dec 2006 22:18:23.0597 (UTC)
	FILETIME=[9A8339D0:01C71F04]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Cc: Mobile IPv4 Mailing List <mip4@ietf.org>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org


<snip>

>=20
> *Exactly*.  So rules which says that port 434 from TIA to HA=20
> always go through the tunnel, port 434 from non-TIA to HA=20
> never goes to tunnel will work.  No need for anything more complex.
>=20

A rule to the effect of "UDP Port =3D 434, Local IP address !=3D TIA, =
Remote
IP address =3D HA --> Bypass" is not something that can be set up, in
accordance with RFC4301, as far as I know. =20

<snip>

>=20
> You're missing that this is a specific mechanism to determine=20
> whether you're inside or outside, and exactly how that is to=20
> be performed is described in section 3, with handling of FAs=20
> (if you want to do that, which I'd choose only doing when the=20
> previous connection was inside) in subsection 3.4.
>=20
> Once the inside-outside determination has been done, you can=20
> apply policies or rules you have about exactly what's=20
> permitted / mandatory in the different situations.  This may=20
> involve re-registration, depending on your inside-outside=20
> determination implementation and your policies.
>=20

So, what you are saying is this then - if the MN is moving from an
untrusted network, it needs to first acquire an IP address, try reaching
the HA with it; if the HA is not reachable, use that address as the VPN
tunnel outer address; if it is reachable, either operate in CCoA mode or
then use an FA and re-register with the FA. OTOH, if the MN is moving
from a trusted network, it may use an FA first; determine that the HA is
unreachable, subsequently acquire an IP address and set up a VPN. Is
that correct?=20

But, regardless of this issue, I think just bypassing the VPN is an
issue, since I don't think a bypass entry as you indicate is feasible in
IPsec.=20

Vidya

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Wed Dec 13 17:28:42 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gucag-000882-Io; Wed, 13 Dec 2006 17:28:42 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gucae-00087V-QU
	for mip4@ietf.org; Wed, 13 Dec 2006 17:28:40 -0500
Received: from ithilien.qualcomm.com ([129.46.51.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gucad-0003YD-EY
	for mip4@ietf.org; Wed, 13 Dec 2006 17:28:40 -0500
Received: from sabrina.qualcomm.com (sabrina.qualcomm.com [129.46.61.150])
	by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	kBDMScgO006068
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Wed, 13 Dec 2006 14:28:38 -0800
Received: from SANEXCAS03.na.qualcomm.com (sanexcas03.qualcomm.com
	[172.30.32.65])
	by sabrina.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	kBDMSaqt015358; Wed, 13 Dec 2006 14:28:37 -0800
Received: from NAEX13.na.qualcomm.com ([129.46.51.248]) by
	SANEXCAS03.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 13 Dec 2006 14:28:36 -0800
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
Subject: RE: [Mip4] WGLC Comments: draft-ietf-mip4-mobike-connectivity-01.txt
Date: Wed, 13 Dec 2006 14:28:37 -0800
Message-ID: <C24CB51D5AA800449982D9BCB903251335E8E9@NAEX13.na.qualcomm.com>
In-Reply-To: <4580670B.8070607@teliasonera.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip4] WGLC Comments: draft-ietf-mip4-mobike-connectivity-01.txt
Thread-Index: Acce+Mx/dNM6/dMhSIiuUT/KgpR9+AAC9Fpw
From: "Narayanan, Vidya" <vidyan@qualcomm.com>
To: "Jouni Korhonen" <jouni.korhonen@teliasonera.com>
X-OriginalArrivalTime: 13 Dec 2006 22:28:36.0751 (UTC)
	FILETIME=[07FB19F0:01C71F06]
X-Spam-Score: 0.6 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Cc: Mobile IPv4 Mailing List <mip4@ietf.org>,
	Henrik Levkowetz <henrik@levkowetz.com>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

=20

> -----Original Message-----
> From: Jouni Korhonen [mailto:jouni.korhonen@teliasonera.com]=20
> Sent: Wednesday, December 13, 2006 12:48 PM
> To: Narayanan, Vidya
> Cc: Henrik Levkowetz; Mobile IPv4 Mailing List
> Subject: Re: [Mip4] WGLC Comments:=20
> draft-ietf-mip4-mobike-connectivity-01.txt
>=20
> [snip]
> >=20
> > I already said that if the MIP client is in the modem, it is not an=20
> > issue. It is an issue when the MIP client in the host is=20
> expected to=20
> > handle MIP for cellular access too - I don't think this model is=20
> > deployed today, but, as cellular networks adopt various access=20
> > technologies (WLAN, WiMAX, etc.), this model has to change, if=20
> > mobility across the interfaces is needed. In that case, it=20
> does become an issue.
>=20
> As this draft is mostly intended to enterprise use cases=20
> (where the enterprise runs its own HA and VPN gateway) I=20
> assume that the IT manager planning to roll out laptops with=20
> a mobility service would not select e.g. CMIP mode for the=20
> WiMAX access nor intentionally create overlapping mobility=20
> service solutions etc.
>=20

Maybe, but, I'm not so sure. There are times when I use cellular data
cards and WLAN access on my laptop without connecting to the enterprise.
So, in such situations, I'd want to use mobility on the cellular
network. The setup has to be then such that MIP in the cellular network
is disabled when I'm connected to the enterprise network, and not
otherwise.=20

It can be done, of course. It may be worth noting for sake of clarity.=20

Vidya

> Cheers,
> 	Jouni
>=20
>=20
> >=20
> > Regards,
> > Vidya
> >=20
> >>
> >> 	Henrik
> >>
> >>
> >=20
>=20

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Wed Dec 13 17:42:36 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Guco2-0006yl-QF; Wed, 13 Dec 2006 17:42:30 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Guco1-0006yC-D5
	for mip4@ietf.org; Wed, 13 Dec 2006 17:42:29 -0500
Received: from av7-2-sn3.vrr.skanova.net ([81.228.9.182])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gucnx-0005yD-W5
	for mip4@ietf.org; Wed, 13 Dec 2006 17:42:29 -0500
Received: by av7-2-sn3.vrr.skanova.net (Postfix, from userid 502)
	id D9DFB3811E; Wed, 13 Dec 2006 23:42:05 +0100 (CET)
Received: from smtp3-1-sn3.vrr.skanova.net (smtp3-1-sn3.vrr.skanova.net
	[81.228.9.101]) by av7-2-sn3.vrr.skanova.net (Postfix) with ESMTP
	id B1D1337FA9; Wed, 13 Dec 2006 23:42:05 +0100 (CET)
Received: from shiraz.levkowetz.com (81-232-110-214-no16.tbcn.telia.com
	[81.232.110.214])
	by smtp3-1-sn3.vrr.skanova.net (Postfix) with ESMTP id AC0B337E46;
	Wed, 13 Dec 2006 23:42:24 +0100 (CET)
Received: from localhost ([127.0.0.1])
	by shiraz.levkowetz.com with esmtp (Exim 4.63)
	(envelope-from <henrik@levkowetz.com>)
	id 1Gucnw-0000HD-0g; Wed, 13 Dec 2006 23:42:24 +0100
Message-ID: <458081CD.3090004@levkowetz.com>
Date: Wed, 13 Dec 2006 23:42:21 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Thunderbird 1.5.0.8 (Macintosh/20061025)
MIME-Version: 1.0
To: "Narayanan, Vidya" <vidyan@qualcomm.com>
Subject: Re: [Mip4] WGLC Comments: draft-ietf-mip4-mobike-connectivity-01.txt
References: <C24CB51D5AA800449982D9BCB903251335E8E3@NAEX13.na.qualcomm.com>
In-Reply-To: <C24CB51D5AA800449982D9BCB903251335E8E3@NAEX13.na.qualcomm.com>
X-Enigmail-Version: 0.94.1.2
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: vidyan@qualcomm.com, mip4@ietf.org,
	henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on shiraz.levkowetz.com);
	SAEximRunCond expanded to false
X-Spam-Score: 0.1 (/)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Cc: Mobile IPv4 Mailing List <mip4@ietf.org>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1210606936=="
Errors-To: mip4-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============1210606936==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enigC9B3436D1490DF4CC2419C3D"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigC9B3436D1490DF4CC2419C3D
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable



on 2006-12-13 23:18 Narayanan, Vidya said the following:
> <snip>
>=20
>>=20
>> *Exactly*.  So rules which says that port 434 from TIA to HA=20
>> always go through the tunnel, port 434 from non-TIA to HA=20
>> never goes to tunnel will work.  No need for anything more complex.
>>=20
>=20
> A rule to the effect of "UDP Port =3D 434, Local IP address !=3D TIA, R=
emote
> IP address =3D HA --> Bypass" is not something that can be set up, in
> accordance with RFC4301, as far as I know. =20

Why on earth not?  You'd say UDP, Port=3D434, Dest=3DHA, Src=3DTIA (which=

is a known, fixed address, just as HA is) --> Tunnel, and if this
isn't taken, you have UDP, Port=3D434, Dest=3DHA --> Bypass.


>=20
> <snip>
>=20
>>=20
>> You're missing that this is a specific mechanism to determine=20
>> whether you're inside or outside, and exactly how that is to=20
>> be performed is described in section 3, with handling of FAs=20
>> (if you want to do that, which I'd choose only doing when the=20
>> previous connection was inside) in subsection 3.4.
>>=20
>> Once the inside-outside determination has been done, you can=20
>> apply policies or rules you have about exactly what's=20
>> permitted / mandatory in the different situations.  This may=20
>> involve re-registration, depending on your inside-outside=20
>> determination implementation and your policies.
>>=20
>=20
> So, what you are saying is this then - if the MN is moving from an
> untrusted network, it needs to first acquire an IP address, try reachin=
g
> the HA with it; if the HA is not reachable, use that address as the VPN=

> tunnel outer address; if it is reachable, either operate in CCoA mode o=
r
> then use an FA and re-register with the FA. OTOH, if the MN is moving
> from a trusted network, it may use an FA first; determine that the HA i=
s
> unreachable, subsequently acquire an IP address and set up a VPN. Is
> that correct?=20

Yup.

> But, regardless of this issue, I think just bypassing the VPN is an
> issue, since I don't think a bypass entry as you indicate is feasible i=
n
> IPsec.

Oh, yes.  You'll have to explain why a simple fixed-src-addr,
fixed-dest-addr, fixed-dest-port rule isn't feasible - I see no
problem with it at all.


	Henrik



--------------enigC9B3436D1490DF4CC2419C3D
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iD8DBQFFgIHNeVhrtTJkXCMRAkLTAKCeuvmnRB9UqD6vGS1hSKyisI/zOQCfX+3q
7IYK0DQXu366sn1uhS3q4CI=
=oxk2
-----END PGP SIGNATURE-----

--------------enigC9B3436D1490DF4CC2419C3D--


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

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

--===============1210606936==--




From mip4-bounces@ietf.org Wed Dec 13 21:26:26 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GugIj-0003PG-7e; Wed, 13 Dec 2006 21:26:25 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GugIi-0003Ov-Dl
	for mip4@ietf.org; Wed, 13 Dec 2006 21:26:24 -0500
Received: from mail2.azairenet.com ([66.92.223.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GugIg-00087G-H3
	for mip4@ietf.org; Wed, 13 Dec 2006 21:26:24 -0500
Received: from [127.0.0.1] ([66.92.223.6]) by mail2.azairenet.com over TLS
	secured channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 13 Dec 2006 18:26:19 -0800
Message-ID: <4580B64B.3080906@azairenet.com>
Date: Wed, 13 Dec 2006 18:26:19 -0800
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: Henrik Levkowetz <henrik@levkowetz.com>
Subject: Re: [Mip4] WGLC Comments: draft-ietf-mip4-mobike-connectivity-01.txt
References: <C24CB51D5AA800449982D9BCB903251335E8E3@NAEX13.na.qualcomm.com>
	<458081CD.3090004@levkowetz.com>
In-Reply-To: <458081CD.3090004@levkowetz.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 14 Dec 2006 02:26:19.0078 (UTC)
	FILETIME=[3CFD7E60:01C71F27]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Cc: "Narayanan, Vidya" <vidyan@qualcomm.com>,
	Mobile IPv4 Mailing List <mip4@ietf.org>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Henrik Levkowetz wrote:
> 
> on 2006-12-13 23:18 Narayanan, Vidya said the following:
>> <snip>
>>
>>> *Exactly*.  So rules which says that port 434 from TIA to HA 
>>> always go through the tunnel, port 434 from non-TIA to HA 
>>> never goes to tunnel will work.  No need for anything more complex.
>>>
>> A rule to the effect of "UDP Port = 434, Local IP address != TIA, Remote
>> IP address = HA --> Bypass" is not something that can be set up, in
>> accordance with RFC4301, as far as I know.  
> 
> Why on earth not?  You'd say UDP, Port=434, Dest=HA, Src=TIA (which
> is a known, fixed address, just as HA is) --> Tunnel, and if this
> isn't taken, you have UDP, Port=434, Dest=HA --> Bypass.

It is actually trivial to setup SPD entries so that
you can send one registration request from the local
IP address with the destination set to the HA so that
it bypasses the IPsec engine. There will be one for
the registration request with source address set to
the TIA.

So agree with Henrik here.

Vijay

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Wed Dec 13 21:40:03 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GugVp-0002si-3X; Wed, 13 Dec 2006 21:39:57 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GugVo-0002sd-4g
	for mip4@ietf.org; Wed, 13 Dec 2006 21:39:56 -0500
Received: from mail2.azairenet.com ([66.92.223.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GugVm-0001Xb-MF
	for mip4@ietf.org; Wed, 13 Dec 2006 21:39:56 -0500
Received: from [127.0.0.1] ([66.92.223.6]) by mail2.azairenet.com over TLS
	secured channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 13 Dec 2006 18:39:53 -0800
Message-ID: <4580B979.5050706@azairenet.com>
Date: Wed, 13 Dec 2006 18:39:53 -0800
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: Henrik Levkowetz <henrik@levkowetz.com>
Subject: Re: [Mip4] WGLC Comments: draft-ietf-mip4-mobike-connectivity-01.txt
References: <C24CB51D5AA800449982D9BCB903251335E896@NAEX13.na.qualcomm.com>
	<45805F79.9000908@levkowetz.com>
In-Reply-To: <45805F79.9000908@levkowetz.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 14 Dec 2006 02:39:53.0239 (UTC)
	FILETIME=[22449A70:01C71F29]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Cc: "Narayanan, Vidya" <vidyan@qualcomm.com>,
	Mobile IPv4 Mailing List <mip4@ietf.org>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Hello,

Henrik Levkowetz wrote:

> Checking draft-ietf-mip4-vpn-problem-solution, we find that this is
> all very clearly described there, so I'd suggest that referencing that
> draft would provide answers to all of the above.  

Yes, we already reference draft-ietf-mip4-vpn-problem-solution.

    Security boundary detection is based on the reachability of the i-HA
    from the mobile node's current point of attachment.  Whenever the
    mobile node detects that it has moved to a new IP subnet [9] and its
    IP address changes, it sends a Registration Request to the i-HA
    without any VPN encapsulation.  If the mobile node receives a
    Registration Reply, then it is assumes that it is on a trusted
    network.  This is based on the mechanism described in [6] to detect
    attachment to the internal trusted network.  The mobile node should
    re-transmit the Registration Request if it does not receive the
    Registration Reply within a timeout period.  The number of times the
    mobile node should re-transmit the Registration Request and the
    timeout period for receiving the Registration Reply are configurable
    on the mobile node.

    [6]   Vaarala, S. and E. Klovning, "Mobile IPv4 Traversal Across
          IPsec-based VPN Gateways",
          draft-ietf-mip4-vpn-problem-solution-02 (work in progress),
          November 2005.

The only difference is that in this document a MOBIKE update
is sent to the VPN gateway rather than a registration request
to the external HA.

Vijay

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Wed Dec 13 21:45:54 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GugbR-0005Af-R8; Wed, 13 Dec 2006 21:45:45 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GugbP-00059j-R5
	for mip4@ietf.org; Wed, 13 Dec 2006 21:45:43 -0500
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GugbN-0002FJ-DN
	for mip4@ietf.org; Wed, 13 Dec 2006 21:45:43 -0500
Received: from crowley.qualcomm.com (crowley.qualcomm.com [129.46.61.151])
	by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	kBE2jYdm023949
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Wed, 13 Dec 2006 18:45:34 -0800
Received: from SANEXCAS02.na.qualcomm.com (sanexcas02.qualcomm.com
	[172.30.36.176])
	by crowley.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	kBE2jXuw024063; Wed, 13 Dec 2006 18:45:33 -0800 (PST)
Received: from NAEX13.na.qualcomm.com ([129.46.51.248]) by
	SANEXCAS02.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 13 Dec 2006 18:45:32 -0800
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
Subject: RE: [Mip4] WGLC Comments: draft-ietf-mip4-mobike-connectivity-01.txt
Date: Wed, 13 Dec 2006 18:45:36 -0800
Message-ID: <C24CB51D5AA800449982D9BCB903251335E935@NAEX13.na.qualcomm.com>
In-Reply-To: <4580B64B.3080906@azairenet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip4] WGLC Comments: draft-ietf-mip4-mobike-connectivity-01.txt
Thread-Index: AccfJ0e6BKU9avvNSZCd4K1DDpWdOAAALEbw
From: "Narayanan, Vidya" <vidyan@qualcomm.com>
To: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>,
	"Henrik Levkowetz" <henrik@levkowetz.com>
X-OriginalArrivalTime: 14 Dec 2006 02:45:32.0987 (UTC)
	FILETIME=[ECC608B0:01C71F29]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
Cc: Mobile IPv4 Mailing List <mip4@ietf.org>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

=20

> -----Original Message-----
> From: Vijay Devarapalli [mailto:vijay.devarapalli@AzaireNet.com]=20
> Sent: Wednesday, December 13, 2006 6:26 PM
> To: Henrik Levkowetz
> Cc: Narayanan, Vidya; Mobile IPv4 Mailing List
> Subject: Re: [Mip4] WGLC Comments:=20
> draft-ietf-mip4-mobike-connectivity-01.txt
>=20
> Henrik Levkowetz wrote:
> >=20
> > on 2006-12-13 23:18 Narayanan, Vidya said the following:
> >> <snip>
> >>
> >>> *Exactly*.  So rules which says that port 434 from TIA to=20
> HA always=20
> >>> go through the tunnel, port 434 from non-TIA to HA never goes to=20
> >>> tunnel will work.  No need for anything more complex.
> >>>
> >> A rule to the effect of "UDP Port =3D 434, Local IP address !=3D =
TIA,=20
> >> Remote IP address =3D HA --> Bypass" is not something that=20
> can be set=20
> >> up, in accordance with RFC4301, as far as I know.
> >=20
> > Why on earth not?  You'd say UDP, Port=3D434, Dest=3DHA,=20
> Src=3DTIA (which is=20
> > a known, fixed address, just as HA is) --> Tunnel, and if=20
> this isn't=20
> > taken, you have UDP, Port=3D434, Dest=3DHA --> Bypass.
>=20
> It is actually trivial to setup SPD entries so that you can=20
> send one registration request from the local IP address with=20
> the destination set to the HA so that it bypasses the IPsec=20
> engine. There will be one for the registration request with=20
> source address set to the TIA.
>=20

I am missing something. In a typical remote access VPN setup, there will
be one SA used to protect any traffic being sent from the host. So, the
SPD entry will specify a range of remote IP addresses (typically, either
everything or configured enterprise subnets) that should be protected.
There are corporate VPNs that don't allow any bypass, period. For those
setups, all outbound traffic will be sent using that SA and all
unprotected inbound traffic will be discarded. Where bypassing is
allowed, specific bypass rules need to be in place. If the PROTECT
condition applies (say, where the remote address falls within the range
of configured subnets), the packet will be sent via the VPN tunnel. If
there is a BYPASS rule that applies, it will be bypassed. All other
packets will be discarded. The HA IP address will fall under the range
of addresses within the enterprise subnets that would be setup for a
PROTECT condition in the SPD.=20

If you are relying on the order of SPD entries for the bypass rule to
catch it before the protect rule, it is problematic, since that will
result in all RRQs being bypassed. If you go through the protect rule
first, it is going to be protected, given that the HA IP address is
likely to be part of the range of addresses that need protection.=20

Also, I'd say that if you expect MIP-specific IPsec SPD entries to be
cumpulsorily present on the host/VPN GW, this document needs to spell
those out. My main problem here is that the document is written such
that it just uses a corporate VPN with MOBIKE capability. I don't see
how that is sufficient.=20

Vidya

> So agree with Henrik here.
>=20
> Vijay
>=20

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Wed Dec 13 22:26:17 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GuhEf-00010X-9J; Wed, 13 Dec 2006 22:26:17 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GuhEe-00010Q-02
	for mip4@ietf.org; Wed, 13 Dec 2006 22:26:16 -0500
Received: from mail2.azairenet.com ([66.92.223.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GuhEc-0007t8-Dj
	for mip4@ietf.org; Wed, 13 Dec 2006 22:26:15 -0500
Received: from [127.0.0.1] ([66.92.223.6]) by mail2.azairenet.com over TLS
	secured channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 13 Dec 2006 19:26:11 -0800
Message-ID: <4580C443.7040701@azairenet.com>
Date: Wed, 13 Dec 2006 19:25:55 -0800
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: "Narayanan, Vidya" <vidyan@qualcomm.com>
Subject: Re: [Mip4] WGLC Comments: draft-ietf-mip4-mobike-connectivity-01.txt
References: <C24CB51D5AA800449982D9BCB903251335E82F@NAEX13.na.qualcomm.com>
In-Reply-To: <C24CB51D5AA800449982D9BCB903251335E82F@NAEX13.na.qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 14 Dec 2006 03:26:11.0391 (UTC)
	FILETIME=[9A2CF4F0:01C71F2F]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d
Cc: Mobile IPv4 Mailing List <mip4@ietf.org>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

hi Vidya,

Narayanan, Vidya wrote:
> Overall, I support advancing this draft. But, I think it requires some
> clarifications.  
> 
> 1. The draft states: 
> 
> "The Mobile IP tunnel uses reverse tunneling through the
>    home agent [8]."
> 
>>From this, it is not clear if reverse tunneling is mandated or not. This
> should be clarified. When using the HoA for communication, reverse
> tunneling probably needs to be mandated when accessing via a VPN -
> otherwise, the VPN GW is going to drop the packets. If the VPN is set up
> to bypass such packets as well, it will work, if the HoA is a routable
> address and if there is no ingress filtering on the local network. But,
> I'm not sure we need to allow such a scenario. Alternately, the MN may
> use its VPN TIA for communication. 

The intention was to use reverse tunneling all the
time when coming through an IPsec VPN gateway. How
about the following text?

    The solution described above results in a Mobile IP tunnel inside an
    IPsec tunnel.  The Mobile IP tunnel is between the mobile node and
    the home agent and the IPsec tunnel is between the MN and the mVPN
    gateway.  The mobile node MUST reverse tunnel through the home agent
    [8] when the Mobile IP tunnel is inside an IPsec tunnel.

> 3. Some VPNs support bypass mode/split tunneling when the host is
> attached via an untrusted network - such traffic will not have any
> mobility support as well. This is not too different from a MIP MN using
> it's CoA for local communication - however, since this document ties the
> VPN to MIP, I think it is good to note this - especially to avoid any
> implementation issues (ambiguities with respect to what packets go
> through MIP processing prior to IPsec processing and what don't). Any
> attempt to route packets meant to bypass the VPN through the MIP stack
> will result in dropped packets. 

Would the following text address your concern?

    Some IPsec VPN implementations allow a host to send traffic directly
    to the Internet when attached to an untrusted network.  This traffic
    bypasses the IPsec tunnel with the VPN gateway.  This document does
    not prevent such traffic from being sent out from the host, but there
    will be no mobility or session continuity for the traffic.  Any data
    traffic that is sent through the Mobile IP tunnel with the home agent
    is always sent through the VPN gateway.

> 4. The document doesn't touch on simultaneous bindings and I think it
> should. Some enterprises treat the internal wireless access networks
> similar to untrusted networks (thereby requiring a VPN over it) and it
> is quite common to have simultaneous wired and wireless connectivity.
> One of those may be routed through a VPN, while the other may be routed
> directly. 

The typical behavior when this happens would be for
the client to indicate to the user it is connected to
the trusted network and terminate the IPsec tunnel.
Only the wired connection would be used. At least
thats my experience.

> Is the MN allowed to register both interfaces with the HA?
> Unfortunately, the only form of simultaneous bindings supported by
> RFC3344 is bicasting, which is not-so-desirable here, since, there may
> be long periods of time when wired and wireless interfaces are
> simultaneously active. So, perhaps the right thing to do is to recommend
> against simultaneous bindings, but, I'm not sure. 

If you are attached to the trusted network, you
should stop using the connection from the untrusted
network.

Vijay

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Wed Dec 13 22:42:22 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GuhUE-0000ZQ-AE; Wed, 13 Dec 2006 22:42:22 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GuhUC-0000ZC-VG
	for mip4@ietf.org; Wed, 13 Dec 2006 22:42:20 -0500
Received: from ithilien.qualcomm.com ([129.46.51.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GuhUB-0000xi-GM
	for mip4@ietf.org; Wed, 13 Dec 2006 22:42:20 -0500
Received: from crowley.qualcomm.com (crowley.qualcomm.com [129.46.61.151])
	by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	kBE3gCHB020633
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Wed, 13 Dec 2006 19:42:13 -0800
Received: from sanexcas01.na.qualcomm.com (sanexcas01.qualcomm.com
	[172.30.36.175])
	by crowley.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	kBE3gAUW009655; Wed, 13 Dec 2006 19:42:11 -0800 (PST)
Received: from NAEX13.na.qualcomm.com ([129.46.51.248]) by
	sanexcas01.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 13 Dec 2006 19:42:10 -0800
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
Subject: RE: [Mip4] WGLC Comments: draft-ietf-mip4-mobike-connectivity-01.txt
Date: Wed, 13 Dec 2006 19:42:20 -0800
Message-ID: <C24CB51D5AA800449982D9BCB903251335E93D@NAEX13.na.qualcomm.com>
In-Reply-To: <4580C443.7040701@azairenet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip4] WGLC Comments: draft-ietf-mip4-mobike-connectivity-01.txt
Thread-Index: AccfL6E8LWY6fF4aTrC/WAFYjLGybwAAQb9Q
From: "Narayanan, Vidya" <vidyan@qualcomm.com>
To: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
X-OriginalArrivalTime: 14 Dec 2006 03:42:10.0005 (UTC)
	FILETIME=[D58DD850:01C71F31]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68ba2b07ef271dba6ee42a93832cfa4c
Cc: Mobile IPv4 Mailing List <mip4@ietf.org>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Hi Vijay,=20

> -----Original Message-----
> From: Vijay Devarapalli [mailto:vijay.devarapalli@azairenet.com]=20
> Sent: Wednesday, December 13, 2006 7:26 PM
> To: Narayanan, Vidya
> Cc: Mobile IPv4 Mailing List
> Subject: Re: [Mip4] WGLC Comments:=20
> draft-ietf-mip4-mobike-connectivity-01.txt
>=20
> hi Vidya,
>=20
> Narayanan, Vidya wrote:
> > Overall, I support advancing this draft. But, I think it=20
> requires some=20
> > clarifications.
> >=20
> > 1. The draft states:=20
> >=20
> > "The Mobile IP tunnel uses reverse tunneling through the
> >    home agent [8]."
> >=20
> >>From this, it is not clear if reverse tunneling is mandated or not.=20
> >>This
> > should be clarified. When using the HoA for communication, reverse=20
> > tunneling probably needs to be mandated when accessing via a VPN -=20
> > otherwise, the VPN GW is going to drop the packets. If the=20
> VPN is set=20
> > up to bypass such packets as well, it will work, if the HoA is a=20
> > routable address and if there is no ingress filtering on the local=20
> > network. But, I'm not sure we need to allow such a scenario.=20
> > Alternately, the MN may use its VPN TIA for communication.
>=20
> The intention was to use reverse tunneling all the time when=20
> coming through an IPsec VPN gateway. How about the following text?
>=20
>     The solution described above results in a Mobile IP=20
> tunnel inside an
>     IPsec tunnel.  The Mobile IP tunnel is between the mobile node and
>     the home agent and the IPsec tunnel is between the MN and the mVPN
>     gateway.  The mobile node MUST reverse tunnel through the=20
> home agent
>     [8] when the Mobile IP tunnel is inside an IPsec tunnel.
>=20

Sounds good.=20

> > 3. Some VPNs support bypass mode/split tunneling when the host is=20
> > attached via an untrusted network - such traffic will not have any=20
> > mobility support as well. This is not too different from a MIP MN=20
> > using it's CoA for local communication - however, since=20
> this document=20
> > ties the VPN to MIP, I think it is good to note this -=20
> especially to=20
> > avoid any implementation issues (ambiguities with respect to what=20
> > packets go through MIP processing prior to IPsec processing=20
> and what=20
> > don't). Any attempt to route packets meant to bypass the=20
> VPN through=20
> > the MIP stack will result in dropped packets.
>=20
> Would the following text address your concern?
>=20
>     Some IPsec VPN implementations allow a host to send=20
> traffic directly
>     to the Internet when attached to an untrusted network. =20
> This traffic
>     bypasses the IPsec tunnel with the VPN gateway.  This=20
> document does
>     not prevent such traffic from being sent out from the=20
> host, but there
>     will be no mobility or session continuity for the=20
> traffic.  Any data
>     traffic that is sent through the Mobile IP tunnel with=20
> the home agent
>     is always sent through the VPN gateway.
>=20

Sounds good too.=20

> > 4. The document doesn't touch on simultaneous bindings and=20
> I think it=20
> > should. Some enterprises treat the internal wireless access=20
> networks=20
> > similar to untrusted networks (thereby requiring a VPN over=20
> it) and it=20
> > is quite common to have simultaneous wired and wireless=20
> connectivity.
> > One of those may be routed through a VPN, while the other may be=20
> > routed directly.
>=20
> The typical behavior when this happens would be for the=20
> client to indicate to the user=20

Which client? MIP or IPsec? My IPsec client does not indicate that.=20

>it is connected to the trusted=20
> network and terminate the IPsec tunnel.
> Only the wired connection would be used. At least thats my experience.
>=20

Well, an example is this - we use IPsec over internal WLANs to access
the network. There are several times I forget to disconnect my VPN when
I undock and dock my laptop and it stays on, along with my ethernet
connection. In the cases where we are only talking about external to
internal network transition, it is not that important, since a gap in
physical/RF connectivity is going to cause the VPN to disconnect,
alerting the user of the same. However, if the transition is seamless,
which is hopefully what the world is moving towards, this is a problem.=20

> > Is the MN allowed to register both interfaces with the HA?
> > Unfortunately, the only form of simultaneous bindings supported by
> > RFC3344 is bicasting, which is not-so-desirable here,=20
> since, there may=20
> > be long periods of time when wired and wireless interfaces are=20
> > simultaneously active. So, perhaps the right thing to do is to=20
> > recommend against simultaneous bindings, but, I'm not sure.
>=20
> If you are attached to the trusted network, you should stop=20
> using the connection from the untrusted network.

What I've said above holds. Additionally, I sometimes keep a data card
(say, EV-DO) connected while I'm also attached to an internal network -
this is especially true if I frequently disconnect from the direct
intranet connection, since keeping the data card connected provides more
seamlessness than trying to connect after I've lost my network
connection.=20

So, I think we should be planning for having multiple simultaneously
active interfaces and not ruling them out. We can rule them out from a
MIP perspective (say, no simultaneous bindings) and that's probably
okay.=20

Vidya

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Wed Dec 13 22:55:09 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GuhgX-00052q-78; Wed, 13 Dec 2006 22:55:05 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GuhgV-00051L-Vb
	for mip4@ietf.org; Wed, 13 Dec 2006 22:55:03 -0500
Received: from mail2.azairenet.com ([66.92.223.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GuhgU-0002Ur-CX
	for mip4@ietf.org; Wed, 13 Dec 2006 22:55:03 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip4] WGLC Comments: draft-ietf-mip4-mobike-connectivity-01.txt
Date: Wed, 13 Dec 2006 19:54:58 -0800
Message-ID: <D4AE20519DDD544A98B3AE9235C8A4C252603F@moe.corp.azairenet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip4] WGLC Comments: draft-ietf-mip4-mobike-connectivity-01.txt
Thread-Index: AccfL6E8LWY6fF4aTrC/WAFYjLGybwAAQb9QAACN9SA=
From: "Vijay Devarapalli" <Vijay.Devarapalli@AzaireNet.com>
To: "Narayanan, Vidya" <vidyan@qualcomm.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
Cc: Mobile IPv4 Mailing List <mip4@ietf.org>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

> > > 4. The document doesn't touch on simultaneous bindings and=20
> > I think it=20
> > > should. Some enterprises treat the internal wireless access=20
> > networks=20
> > > similar to untrusted networks (thereby requiring a VPN over=20
> > it) and it=20
> > > is quite common to have simultaneous wired and wireless=20
> > connectivity.
> > > One of those may be routed through a VPN, while the other may be=20
> > > routed directly.
> >=20
> > The typical behavior when this happens would be for the=20
> > client to indicate to the user=20
>=20
> Which client? MIP or IPsec? My IPsec client does not indicate that.=20

The IPsec VPN client.

> >it is connected to the trusted=20
> > network and terminate the IPsec tunnel.
> > Only the wired connection would be used. At least thats my=20
> experience.
> >=20
>=20
> Well, an example is this - we use IPsec over internal WLANs to access
> the network. There are several times I forget to disconnect=20
> my VPN when
> I undock and dock my laptop and it stays on, along with my ethernet
> connection. In the cases where we are only talking about external to
> internal network transition, it is not that important, since a gap in
> physical/RF connectivity is going to cause the VPN to disconnect,
> alerting the user of the same. However, if the transition is seamless,
> which is hopefully what the world is moving towards, this is=20
> a problem.=20

Once you dock the laptop, the policy configuration on
your laptop should start using the ethernet connection
and not use the VPN tunnel anymore. From my experience
the VPN tunnel is disconnected once you plug into the
campus wired network.

I am not talking about the gap in connectivity at all.

> > > Is the MN allowed to register both interfaces with the HA?
> > > Unfortunately, the only form of simultaneous bindings supported by
> > > RFC3344 is bicasting, which is not-so-desirable here,=20
> > since, there may=20
> > > be long periods of time when wired and wireless interfaces are=20
> > > simultaneously active. So, perhaps the right thing to do is to=20
> > > recommend against simultaneous bindings, but, I'm not sure.
> >=20
> > If you are attached to the trusted network, you should stop=20
> > using the connection from the untrusted network.
>=20
> What I've said above holds. Additionally, I sometimes keep a data card
> (say, EV-DO) connected while I'm also attached to an internal=20
> network -
> this is especially true if I frequently disconnect from the direct
> intranet connection, since keeping the data card connected=20
> provides more
> seamlessness than trying to connect after I've lost my network
> connection.=20
>=20
> So, I think we should be planning for having multiple simultaneously
> active interfaces and not ruling them out. We can rule them out from a
> MIP perspective (say, no simultaneous bindings) and that's probably
> okay.=20

I am all for simultanouesly active interfaces. But being
connected to a corporate intranet and at the same time
have an interface active into an untrusted network is a
bad idea.

Vijay

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Thu Dec 14 05:56:41 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GuoGV-0002Yh-6x; Thu, 14 Dec 2006 05:56:39 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GuoGT-0002YM-Pr
	for mip4@ietf.org; Thu, 14 Dec 2006 05:56:37 -0500
Received: from av10-1-sn2.hy.skanova.net ([81.228.8.181])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GuoGQ-0003q6-CM
	for mip4@ietf.org; Thu, 14 Dec 2006 05:56:37 -0500
Received: by av10-1-sn2.hy.skanova.net (Postfix, from userid 502)
	id B6F813C997; Thu, 14 Dec 2006 11:56:33 +0100 (CET)
Received: from smtp4-2-sn2.hy.skanova.net (smtp4-2-sn2.hy.skanova.net
	[81.228.8.93]) by av10-1-sn2.hy.skanova.net (Postfix) with ESMTP
	id 9987637FE7; Thu, 14 Dec 2006 11:56:33 +0100 (CET)
Received: from shiraz.levkowetz.com (81-232-110-214-no16.tbcn.telia.com
	[81.232.110.214])
	by smtp4-2-sn2.hy.skanova.net (Postfix) with ESMTP id 18C0F37E44;
	Thu, 14 Dec 2006 11:56:32 +0100 (CET)
Received: from localhost ([127.0.0.1])
	by shiraz.levkowetz.com with esmtp (Exim 4.63)
	(envelope-from <henrik@levkowetz.com>)
	id 1GuoGO-0000GP-6t; Thu, 14 Dec 2006 11:56:32 +0100
Message-ID: <45812DDD.8000808@levkowetz.com>
Date: Thu, 14 Dec 2006 11:56:29 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Thunderbird 1.5.0.8 (Macintosh/20061025)
MIME-Version: 1.0
To: "Narayanan, Vidya" <vidyan@qualcomm.com>
Subject: Re: [Mip4] WGLC Comments: draft-ietf-mip4-mobike-connectivity-01.txt
References: <C24CB51D5AA800449982D9BCB903251335E935@NAEX13.na.qualcomm.com>
In-Reply-To: <C24CB51D5AA800449982D9BCB903251335E935@NAEX13.na.qualcomm.com>
X-Enigmail-Version: 0.94.1.2
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: vidyan@qualcomm.com, vijay.devarapalli@azairenet.com,
	mip4@ietf.org, henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on shiraz.levkowetz.com);
	SAEximRunCond expanded to false
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 3a4bc66230659131057bb68ed51598f8
Cc: Mobile IPv4 Mailing List <mip4@ietf.org>,
	Vijay Devarapalli <vijay.devarapalli@azairenet.com>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0586524581=="
Errors-To: mip4-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============0586524581==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig768E628B53E7EF5B878D544C"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig768E628B53E7EF5B878D544C
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable


on 2006-12-14 03:45 Narayanan, Vidya said the following:
> =20
>=20
>> -----Original Message-----
>> From: Vijay Devarapalli [mailto:vijay.devarapalli@AzaireNet.com]=20
>> Sent: Wednesday, December 13, 2006 6:26 PM
>> To: Henrik Levkowetz
>> Cc: Narayanan, Vidya; Mobile IPv4 Mailing List
>> Subject: Re: [Mip4] WGLC Comments:=20
>> draft-ietf-mip4-mobike-connectivity-01.txt
>>=20
>> Henrik Levkowetz wrote:
>> >=20
>> > on 2006-12-13 23:18 Narayanan, Vidya said the following:
>> >> <snip>
>> >>
>> >>> *Exactly*.  So rules which says that port 434 from TIA to=20
>> HA always=20
>> >>> go through the tunnel, port 434 from non-TIA to HA never goes to=20
>> >>> tunnel will work.  No need for anything more complex.
>> >>>
>> >> A rule to the effect of "UDP Port =3D 434, Local IP address !=3D TI=
A,=20
>> >> Remote IP address =3D HA --> Bypass" is not something that=20
>> can be set=20
>> >> up, in accordance with RFC4301, as far as I know.
>> >=20
>> > Why on earth not?  You'd say UDP, Port=3D434, Dest=3DHA,=20
>> Src=3DTIA (which is=20
>> > a known, fixed address, just as HA is) --> Tunnel, and if=20
>> this isn't=20
>> > taken, you have UDP, Port=3D434, Dest=3DHA --> Bypass.
>>=20
>> It is actually trivial to setup SPD entries so that you can=20
>> send one registration request from the local IP address with=20
>> the destination set to the HA so that it bypasses the IPsec=20
>> engine. There will be one for the registration request with=20
>> source address set to the TIA.
>>=20
>=20
> I am missing something. In a typical remote access VPN setup, there wil=
l
> be one SA used to protect any traffic being sent from the host. So, the=

> SPD entry will specify a range of remote IP addresses (typically, eithe=
r
> everything or configured enterprise subnets) that should be protected.
> There are corporate VPNs that don't allow any bypass, period. For those=

> setups, all outbound traffic will be sent using that SA and all
> unprotected inbound traffic will be discarded. Where bypassing is
> allowed, specific bypass rules need to be in place. If the PROTECT
> condition applies (say, where the remote address falls within the range=

> of configured subnets), the packet will be sent via the VPN tunnel. If
> there is a BYPASS rule that applies, it will be bypassed. All other
> packets will be discarded. The HA IP address will fall under the range
> of addresses within the enterprise subnets that would be setup for a
> PROTECT condition in the SPD.=20
>=20
> If you are relying on the order of SPD entries for the bypass rule to
> catch it before the protect rule, it is problematic, since that will
> result in all RRQs being bypassed. If you go through the protect rule
> first, it is going to be protected, given that the HA IP address is
> likely to be part of the range of addresses that need protection.=20

WHOA!!!

RFC 4301 clearly specifies that the SPD is an *ordered* database, exactly=

for cases like this, where rules overlap and it is important to process
them in the correct order.  This is also what I'd expect from practical
experience.

This is just not a problem.

> Also, I'd say that if you expect MIP-specific IPsec SPD entries to be
> cumpulsorily present on the host/VPN GW, this document needs to spell
> those out. My main problem here is that the document is written such
> that it just uses a corporate VPN with MOBIKE capability. I don't see
> how that is sufficient.=20

Actually, since MIP implementations need to have low-level access to raw
incoming packets, to do their job right, they work through mechanisms
like xBSD's BPF-taps or Windows' various slots low in the IP stack where
drivers can attach.  So the choice of using SPD entries to bypass the
VPN tunnel is only one way of doing this; there are other ways which
also will work fine, and practical experience is probably needed to
determine what approach will be best in which market.  I don't think we
should put all of that in this draft; as an implementor, this seems to me=

like something which has to be worked out, but doesn't need to be covered=

in the document necessarily.


	Henrik


--------------enig768E628B53E7EF5B878D544C
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iD8DBQFFgS3deVhrtTJkXCMRAkdiAJoCkYFVFiJ0GVo8kk5nEGTY/f4tfgCdFowr
Su0HRn5KkFXrrCUaiomh1iI=
=182M
-----END PGP SIGNATURE-----

--------------enig768E628B53E7EF5B878D544C--


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

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

--===============0586524581==--




From mip4-bounces@ietf.org Thu Dec 14 09:05:08 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GurCq-0004nS-4B; Thu, 14 Dec 2006 09:05:04 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GurCo-0004nM-9x
	for mip4@ietf.org; Thu, 14 Dec 2006 09:05:02 -0500
Received: from 213.80.52.78.dataphone.se ([213.80.52.78]
	helo=mailgw.local.ipunplugged.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GurCm-0007SA-09
	for mip4@ietf.org; Thu, 14 Dec 2006 09:05:02 -0500
Received: from [127.0.0.1] (echo.local.ipunplugged.com [192.168.4.74])
	by mailgw.local.ipunplugged.com (8.12.8/8.12.3) with ESMTP id
	kBEE4qpI009501 for <mip4@ietf.org>; Thu, 14 Dec 2006 15:04:54 +0100
Message-ID: <458159FE.6080204@ipunplugged.com>
Date: Thu, 14 Dec 2006 15:04:46 +0100
From: Hans Sjostrand <hans@ipunplugged.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: mip4@ietf.org
References: <BE4B07D4197BF34EB3B753DD34EBCD130125E6C2@de01exm67.ds.mot.com>
In-Reply-To: <BE4B07D4197BF34EB3B753DD34EBCD130125E6C2@de01exm67.ds.mot.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: clamd / ClamAV version 0.75.1, clamav-milter version 0.75c
	on mailgw.local.ipunplugged.com
X-Virus-Status: Clean
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36
Subject: [Mip4] Some comments on WGLC:
	draft-ietf-mip4-mobike-connectivity-01.txt
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Hi,

Sorry for being late. There are a few things in the draft that I would 
like to have clarified before agreeing to sending it to IESG.

1. Access mode home seams to be forgotten.

In figure 1 there is a access mode called {home}, but I can't find it 
described anywhere in the document. Is the access mode forgotten or 
omitted on purpose? Since the (in my experience) by far most common 
roaming case is a guy (or girl) leaving his desk for a wireless network 
it's really interesting. And most of the wireless networks are 
considered insecure. I'd really like some description and requirements 
for the home access mode before advancing the document.

2. Whats a few milliseconds worth?

In section 3.2 there is a line stating "The mobile node attempts Foreign 
Agent discovery and CoA address acquisition through DHCP simultaneously 
in order to avoid the delay in discovering a foreign agent when there is 
no foreign agent available.". Apart from not complying with the RFC 2119 
keywords rules, I read it as a statement. The sending of a solicitation 
and waiting for an advertisements is normally a case of split seconds. 
Why start a DHCP cycle which only saves a couple of milliseconds an then 
rely on DHCP servers which normally introduces in order of magnitudes 
longer delays?

A "MAY" is of course ok to have for the really, really eager ones. 
Please add one for clarity.

3. Dual tunnel a normative reference

In my mind the references to the dual tunnel draft can't be considered 
as only informative. The internal/external detection is pretty central 
to this solution. And leaving the security consideration section to an 
informative draft I would assume is a bit OTT. It will be very hard to 
progress this draft through IESG without the dual tunnel draft also 
being advanced in the same time. Comments on that?

I've missed a lot of IETF meetings so I'm not that updated on the dual 
tunnel draft. Is the plans to advance it or scrap it? It's timed out in 
the draft repository. Have anyone implemented it? Sorry if I'm missing 
some obvious information or kicking in open doors. But I think it's 
relevant information in this context.

4. Movement detection and security.

In section 34. there is a sentence stating "Whenever the mobile node 
detects that it has moved to a new IP subnet [9] and its IP address 
changes". Again a lack of keywords. But I think this sentence is a 
potential security problem. It's not about subnets. It should be crystal 
clear that ANY detection of network movement whatsoever MUST result in a 
state that a security boundary may have been crossed and it sends a 
Registration Request to the i-HA.

5. Internet FA's

In this draft it seams that FA's on internet is silently ignored. 
Atleast those are not mentioned anyware that I find. I assume this is 
because the solution doesn't work with internet FA's. I think this is a 
limitation that might be worth mentioning.

Besides that, a good assumption is often a good idea.It's a bit hard to 
know of a FA is inside or outside. Thats why we wrote RFC3846. We have 
been using a RFC3846 agent NAI in  FA's to make an educated guess if 
it's a intranet FA or a internet FA. It's maybe therefore a good idea to 
reference RFC3846 "Mobile IPv4 Extension for Carrying Network Access 
Identifiers" and describe how agent NAIs could be used.

In our solution, if the suffix part of the FA NAI is known as an 
intranet identifier to the MN, then teh MN go against the i-HA.

Best regards
/// Hasse



-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Thu Dec 14 09:57:10 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gus1G-00051c-6U; Thu, 14 Dec 2006 09:57:10 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gus1F-00051W-Mf
	for mip4@ietf.org; Thu, 14 Dec 2006 09:57:09 -0500
Received: from firewall.codebay.fi ([212.68.7.211])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gus1C-00043o-Co
	for mip4@ietf.org; Thu, 14 Dec 2006 09:57:09 -0500
Received: from [172.20.100.195] (helo=[192.168.92.130])
	by firewall.codebay.fi with esmtp (Exim 4.63)
	(envelope-from <sami.vaarala@iki.fi>)
	id 1Gus13-00063S-ON; Thu, 14 Dec 2006 16:56:57 +0200
Message-ID: <4581642A.1060902@iki.fi>
Date: Thu, 14 Dec 2006 16:48:10 +0200
From: Sami Vaarala <sami.vaarala@iki.fi>
User-Agent: Icedove 1.5.0.8 (X11/20061128)
MIME-Version: 1.0
To: Hans Sjostrand <hans@ipunplugged.com>
Subject: Re: [Mip4] Some comments on
	WGLC:	draft-ietf-mip4-mobike-connectivity-01.txt
References: <BE4B07D4197BF34EB3B753DD34EBCD130125E6C2@de01exm67.ds.mot.com>
	<458159FE.6080204@ipunplugged.com>
In-Reply-To: <458159FE.6080204@ipunplugged.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Cc: mip4@ietf.org
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Hi,

Hans Sjostrand wrote:
> I've missed a lot of IETF meetings so I'm not that updated on the dual 
> tunnel draft. Is the plans to advance it or scrap it? It's timed out in 
> the draft repository. Have anyone implemented it? Sorry if I'm missing 
> some obvious information or kicking in open doors. But I think it's 
> relevant information in this context.

The draft has timed out because there haven't been any changes requested
since last revision - it's been basically sitting and waiting for WG
progress.  I haven't been attending late IETF meetings either so I'm not
really why the draft hasn't advanced in the WG.

BR,

-Sami

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Thu Dec 14 13:31:43 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GuvMo-0003hQ-PF; Thu, 14 Dec 2006 13:31:38 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GuvMn-0003ge-6m
	for mip4@ietf.org; Thu, 14 Dec 2006 13:31:37 -0500
Received: from av8-2-sn3.vrr.skanova.net ([81.228.9.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GuvMl-00027f-QD
	for mip4@ietf.org; Thu, 14 Dec 2006 13:31:37 -0500
Received: by av8-2-sn3.vrr.skanova.net (Postfix, from userid 502)
	id 3ABCD38811; Thu, 14 Dec 2006 19:31:35 +0100 (CET)
Received: from smtp3-2-sn3.vrr.skanova.net (smtp3-2-sn3.vrr.skanova.net
	[81.228.9.102]) by av8-2-sn3.vrr.skanova.net (Postfix) with ESMTP
	id 05E0E38933; Thu, 14 Dec 2006 19:31:35 +0100 (CET)
Received: from shiraz.levkowetz.com (81-232-110-214-no16.tbcn.telia.com
	[81.232.110.214])
	by smtp3-2-sn3.vrr.skanova.net (Postfix) with ESMTP id B40B937E4C;
	Thu, 14 Dec 2006 19:31:34 +0100 (CET)
Received: from localhost ([127.0.0.1])
	by shiraz.levkowetz.com with esmtp (Exim 4.63)
	(envelope-from <henrik@levkowetz.com>)
	id 1GuvMk-0001H1-2O; Thu, 14 Dec 2006 19:31:34 +0100
Message-ID: <45819882.4060602@levkowetz.com>
Date: Thu, 14 Dec 2006 19:31:30 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Thunderbird 1.5.0.8 (Macintosh/20061025)
MIME-Version: 1.0
To: Sami Vaarala <sami.vaarala@iki.fi>
Subject: Re: [Mip4] Some comments
	on	WGLC:	draft-ietf-mip4-mobike-connectivity-01.txt
References: <BE4B07D4197BF34EB3B753DD34EBCD130125E6C2@de01exm67.ds.mot.com>	<458159FE.6080204@ipunplugged.com>
	<4581642A.1060902@iki.fi>
In-Reply-To: <4581642A.1060902@iki.fi>
X-Enigmail-Version: 0.94.1.2
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: sami.vaarala@iki.fi, hans@ipunplugged.com, mip4@ietf.org,
	henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on shiraz.levkowetz.com);
	SAEximRunCond expanded to false
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Cc: Hans Sjostrand <hans@ipunplugged.com>, mip4@ietf.org
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1151026764=="
Errors-To: mip4-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============1151026764==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enigB5B64395FDF036E198C86C20"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigB5B64395FDF036E198C86C20
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi,

on 2006-12-14 15:48 Sami Vaarala said the following:
> Hi,
>=20
> Hans Sjostrand wrote:
>> I've missed a lot of IETF meetings so I'm not that updated on the dual=
=20
>> tunnel draft. Is the plans to advance it or scrap it? It's timed out i=
n=20
>> the draft repository. Have anyone implemented it? Sorry if I'm missing=
=20
>> some obvious information or kicking in open doors. But I think it's=20
>> relevant information in this context.
>=20
> The draft has timed out because there haven't been any changes requeste=
d
> since last revision - it's been basically sitting and waiting for WG
> progress.  I haven't been attending late IETF meetings either so I'm no=
t
> really why the draft hasn't advanced in the WG.

The next thing to do is to do the Sheperd writeup and submit for publicat=
ion.
It's just a matter of not finding the cycles to do this, and it is now
high on my list of things to do.

When we send in the request for publication, we'll ask for the current
draft to be made active again -- at least at this time I don't see a need=

to re-submit the same text.


	Henrik


--------------enigB5B64395FDF036E198C86C20
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iD8DBQFFgZiCeVhrtTJkXCMRAk6lAJ0bsgxoJ41uG8vrxhokY6YBI39ErQCg17v6
/+8PFxmfGjlhygvsDBjYuGc=
=PfVp
-----END PGP SIGNATURE-----

--------------enigB5B64395FDF036E198C86C20--


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

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

--===============1151026764==--




From mip4-bounces@ietf.org Thu Dec 14 15:01:30 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Guwlf-0006EZ-Kt; Thu, 14 Dec 2006 15:01:23 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Guwl4-00063o-Sa
	for mip4@ietf.org; Thu, 14 Dec 2006 15:00:46 -0500
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Guwhu-0002x1-4x
	for mip4@ietf.org; Thu, 14 Dec 2006 14:57:32 -0500
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
	kBEJvMQ1005550
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Thu, 14 Dec 2006 11:57:23 -0800
Received: from SANEXCAS02.na.qualcomm.com (sanexcas02.qualcomm.com
	[172.30.36.176])
	by magus.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id kBEJuLce028652; 
	Thu, 14 Dec 2006 11:57:20 -0800 (PST)
Received: from NAEX13.na.qualcomm.com ([129.46.51.248]) by
	SANEXCAS02.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 14 Dec 2006 11:57:10 -0800
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
Subject: RE: [Mip4] WGLC Comments: draft-ietf-mip4-mobike-connectivity-01.txt
Date: Thu, 14 Dec 2006 11:57:12 -0800
Message-ID: <C24CB51D5AA800449982D9BCB903251335E9B7@NAEX13.na.qualcomm.com>
In-Reply-To: <D4AE20519DDD544A98B3AE9235C8A4C252603F@moe.corp.azairenet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip4] WGLC Comments: draft-ietf-mip4-mobike-connectivity-01.txt
Thread-Index: AccfL6E8LWY6fF4aTrC/WAFYjLGybwAAQb9QAACN9SAAIaZXYA==
From: "Narayanan, Vidya" <vidyan@qualcomm.com>
To: "Vijay Devarapalli" <Vijay.Devarapalli@azairenet.com>
X-OriginalArrivalTime: 14 Dec 2006 19:57:10.0744 (UTC)
	FILETIME=[0AB63580:01C71FBA]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Cc: Mobile IPv4 Mailing List <mip4@ietf.org>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

>=20
> Once you dock the laptop, the policy configuration on your=20
> laptop should start using the ethernet connection and not use=20
> the VPN tunnel anymore.=20

Sure, that can be a policy thing.=20

> From my experience the VPN tunnel is=20
> disconnected once you plug into the campus wired network.
>=20

>From my experience, it is not :) It happens to me almost everyday, since
we use VPNs over our internal WLAN access. I have my ethernet plugged in
to the corporate network and my VPN up, since I previously had my
ethernet disconnected. I realize much later (when my computer is showing
signs of being sluggish :)) and then disconnect my VPN.. Sometimes, I
never realize and the VPN stays up until I lose connectivity.=20

> I am not talking about the gap in connectivity at all.
>=20
> > > > Is the MN allowed to register both interfaces with the HA?
> > > > Unfortunately, the only form of simultaneous bindings=20
> supported by
> > > > RFC3344 is bicasting, which is not-so-desirable here,
> > > since, there may
> > > > be long periods of time when wired and wireless interfaces are=20
> > > > simultaneously active. So, perhaps the right thing to do is to=20
> > > > recommend against simultaneous bindings, but, I'm not sure.
> > >=20
> > > If you are attached to the trusted network, you should stop using=20
> > > the connection from the untrusted network.
> >=20

I don't understand this. You can have a policy to stop using your
untrusted connection - that doesn't mean that connection is *disabled* -
it only means that data is not going through that connection at that
time.=20

> > What I've said above holds. Additionally, I sometimes keep=20
> a data card=20
> > (say, EV-DO) connected while I'm also attached to an=20
> internal network=20
> > - this is especially true if I frequently disconnect from=20
> the direct=20
> > intranet connection, since keeping the data card connected provides=20
> > more seamlessness than trying to connect after I've lost my network=20
> > connection.
> >=20
> > So, I think we should be planning for having multiple=20
> simultaneously=20
> > active interfaces and not ruling them out. We can rule them=20
> out from a=20
> > MIP perspective (say, no simultaneous bindings) and that's probably=20
> > okay.
>=20
> I am all for simultanouesly active interfaces. But being=20
> connected to a corporate intranet and at the same time have=20
> an interface active into an untrusted network is a bad idea.
>=20

Why so?=20

Vidya

> Vijay
>=20

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Thu Dec 14 17:32:00 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Guz7P-0006wo-Vz; Thu, 14 Dec 2006 17:31:59 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Guz7N-0006wj-UY
	for mip4@ietf.org; Thu, 14 Dec 2006 17:31:57 -0500
Received: from mail2.azairenet.com ([66.92.223.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Guz7L-0002Np-KA
	for mip4@ietf.org; Thu, 14 Dec 2006 17:31:57 -0500
Received: from [127.0.0.1] ([66.92.223.6]) by mail2.azairenet.com over TLS
	secured channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 14 Dec 2006 14:31:54 -0800
Message-ID: <4581D0D8.2020407@azairenet.com>
Date: Thu, 14 Dec 2006 14:31:52 -0800
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: Hans Sjostrand <hans@ipunplugged.com>
Subject: Re: [Mip4] Some comments on
	WGLC:	draft-ietf-mip4-mobike-connectivity-01.txt
References: <BE4B07D4197BF34EB3B753DD34EBCD130125E6C2@de01exm67.ds.mot.com>
	<458159FE.6080204@ipunplugged.com>
In-Reply-To: <458159FE.6080204@ipunplugged.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 14 Dec 2006 22:31:54.0146 (UTC)
	FILETIME=[A80CF020:01C71FCF]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c83ccb5cc10e751496398f1233ca9c3a
Cc: mip4@ietf.org
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Hans Sjostrand wrote:
> Hi,
> 
> Sorry for being late. There are a few things in the draft that I would 
> like to have clarified before agreeing to sending it to IESG.
> 
> 1. Access mode home seams to be forgotten.
> 
> In figure 1 there is a access mode called {home}, but I can't find it 
> described anywhere in the document. Is the access mode forgotten or 
> omitted on purpose? 

The {home} in the figure refers to the fact that the
link on which the i-HA is present is the home link.
It is not an access mode. There are only four access
modes even in draft-ietf-mip4-vpn-problem-solution.

> 2. Whats a few milliseconds worth?
> 
> In section 3.2 there is a line stating "The mobile node attempts Foreign 
> Agent discovery and CoA address acquisition through DHCP simultaneously 
> in order to avoid the delay in discovering a foreign agent when there is 
> no foreign agent available.". Apart from not complying with the RFC 2119 
> keywords rules, I read it as a statement. The sending of a solicitation 
> and waiting for an advertisements is normally a case of split seconds. 
> Why start a DHCP cycle which only saves a couple of milliseconds an then 
> rely on DHCP servers which normally introduces in order of magnitudes 
> longer delays?

Discovering a FA might take more than a few
milliseconds, especially if the FA does not send
out agent advertisements frequently and the mobile
node has to solicit for agents on the link. If the
mobile node is soliciting by sending agent
solicitations it can take upto 3 seconds before it
can conclude that there is no foreign agent on the
link.

> 3. Dual tunnel a normative reference
> 
> In my mind the references to the dual tunnel draft can't be considered 
> as only informative. The internal/external detection is pretty central 
> to this solution. And leaving the security consideration section to an 
> informative draft I would assume is a bit OTT. It will be very hard to 
> progress this draft through IESG without the dual tunnel draft also 
> being advanced in the same time. Comments on that?

This makes sense. I don't remember why I had
draft-ietf-mip4-vpn-problem-solution as an
Informative reference. Could be because the status
of draft-ietf-mip4-vpn-problem-solution might have
been unknown.

> 4. Movement detection and security.
> 
> In section 34. there is a sentence stating "Whenever the mobile node 
> detects that it has moved to a new IP subnet [9] and its IP address 
> changes". Again a lack of keywords. 

This sentence just describes what the MN must do.
What would you like to see here?

> But I think this sentence is a 
> potential security problem. 

Can you elaborate a little bit more on the security
problem?

> It's not about subnets. It should be crystal 
> clear that ANY detection of network movement whatsoever MUST result in a 
> state that a security boundary may have been crossed and it sends a 
> Registration Request to the i-HA.

Even when there is no subnet change? Why?

> 5. Internet FA's
> 
> In this draft it seams that FA's on internet is silently ignored. 
> Atleast those are not mentioned anyware that I find. I assume this is 
> because the solution doesn't work with internet FA's. I think this is a 
> limitation that might be worth mentioning.

If the mobile node does not have an external Home
Agent that it can reach when it is attached to an
untrusted network, it cannot obviously use the FA
on the untrusted network. If there is an external
home agent that it can use, then
draft-ietf-mip4-vpn-problem-solution would apply.

> Besides that, a good assumption is often a good idea.It's a bit hard to 
> know of a FA is inside or outside. Thats why we wrote RFC3846. We have 
> been using a RFC3846 agent NAI in  FA's to make an educated guess if 
> it's a intranet FA or a internet FA. It's maybe therefore a good idea to 
> reference RFC3846 "Mobile IPv4 Extension for Carrying Network Access 
> Identifiers" and describe how agent NAIs could be used.
> 
> In our solution, if the suffix part of the FA NAI is known as an 
> intranet identifier to the MN, then teh MN go against the i-HA.

The Agent Advertisement is not protected. So I am
not sure we should be using the NAI extension from
RFC 3846, unless rogue foreign agents on a link are
not considered possible.

Another option is for the MN to always acquire a
CoA from the access network and send a registration
request to the i-HA. Once the MN detects that it is
attached to a trusted network, it can switch the FA
CoA mode if an FA is available on the trusted
network. Will this work for you?

Vijay

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Thu Dec 14 17:45:19 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GuzKF-0003V4-JW; Thu, 14 Dec 2006 17:45:15 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GuzKE-0003Ua-Ae
	for mip4@ietf.org; Thu, 14 Dec 2006 17:45:14 -0500
Received: from av11-2-sn2.hy.skanova.net ([81.228.8.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GuzKC-0004CK-P8
	for mip4@ietf.org; Thu, 14 Dec 2006 17:45:14 -0500
Received: by av11-2-sn2.hy.skanova.net (Postfix, from userid 502)
	id E1FEB37F2F; Thu, 14 Dec 2006 23:45:09 +0100 (CET)
Received: from smtp4-2-sn2.hy.skanova.net (smtp4-2-sn2.hy.skanova.net
	[81.228.8.93]) by av11-2-sn2.hy.skanova.net (Postfix) with ESMTP
	id BA50C37ECD; Thu, 14 Dec 2006 23:45:09 +0100 (CET)
Received: from shiraz.levkowetz.com (81-232-110-214-no16.tbcn.telia.com
	[81.232.110.214])
	by smtp4-2-sn2.hy.skanova.net (Postfix) with ESMTP id 7152537E42;
	Thu, 14 Dec 2006 23:45:09 +0100 (CET)
Received: from localhost ([127.0.0.1])
	by shiraz.levkowetz.com with esmtp (Exim 4.63)
	(envelope-from <henrik@levkowetz.com>)
	id 1GuzK8-00059G-9i; Thu, 14 Dec 2006 23:45:08 +0100
Message-ID: <4581D3F3.20509@levkowetz.com>
Date: Thu, 14 Dec 2006 23:45:07 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Thunderbird 1.5.0.8 (Macintosh/20061025)
MIME-Version: 1.0
To: "Narayanan, Vidya" <vidyan@qualcomm.com>
Subject: Re: [Mip4] WGLC Comments: draft-ietf-mip4-mobike-connectivity-01.txt
References: <C24CB51D5AA800449982D9BCB903251335E935@NAEX13.na.qualcomm.com>
In-Reply-To: <C24CB51D5AA800449982D9BCB903251335E935@NAEX13.na.qualcomm.com>
X-Enigmail-Version: 0.94.1.2
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: vidyan@qualcomm.com, vijay.devarapalli@azairenet.com,
	mip4@ietf.org, henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on shiraz.levkowetz.com);
	SAEximRunCond expanded to false
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 2086112c730e13d5955355df27e3074b
Cc: Mobile IPv4 Mailing List <mip4@ietf.org>,
	Vijay Devarapalli <vijay.devarapalli@azairenet.com>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1434411367=="
Errors-To: mip4-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============1434411367==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig9BDB224F22EE8B1821737A1E"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig9BDB224F22EE8B1821737A1E
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Re-sending this.  Vidya, I still haven't seen a response from you to
this.  Is our discussion complete regarding these points?

	Henrik

on 2006-12-14 03:45 Narayanan, Vidya said the following:
> =20
>=20
>> -----Original Message-----
>> From: Vijay Devarapalli [mailto:vijay.devarapalli@AzaireNet.com]=20
>> Sent: Wednesday, December 13, 2006 6:26 PM
>> To: Henrik Levkowetz
>> Cc: Narayanan, Vidya; Mobile IPv4 Mailing List
>> Subject: Re: [Mip4] WGLC Comments:=20
>> draft-ietf-mip4-mobike-connectivity-01.txt
>>=20
>> Henrik Levkowetz wrote:
>> >=20
>> > on 2006-12-13 23:18 Narayanan, Vidya said the following:
>> >> <snip>
>> >>
>> >>> *Exactly*.  So rules which says that port 434 from TIA to=20
>> HA always=20
>> >>> go through the tunnel, port 434 from non-TIA to HA never goes to=20
>> >>> tunnel will work.  No need for anything more complex.
>> >>>
>> >> A rule to the effect of "UDP Port =3D 434, Local IP address !=3D TI=
A,=20
>> >> Remote IP address =3D HA --> Bypass" is not something that=20
>> can be set=20
>> >> up, in accordance with RFC4301, as far as I know.
>> >=20
>> > Why on earth not?  You'd say UDP, Port=3D434, Dest=3DHA,=20
>> Src=3DTIA (which is=20
>> > a known, fixed address, just as HA is) --> Tunnel, and if=20
>> this isn't=20
>> > taken, you have UDP, Port=3D434, Dest=3DHA --> Bypass.
>>=20
>> It is actually trivial to setup SPD entries so that you can=20
>> send one registration request from the local IP address with=20
>> the destination set to the HA so that it bypasses the IPsec=20
>> engine. There will be one for the registration request with=20
>> source address set to the TIA.
>>=20
>=20
> I am missing something. In a typical remote access VPN setup, there wil=
l
> be one SA used to protect any traffic being sent from the host. So, the=

> SPD entry will specify a range of remote IP addresses (typically, eithe=
r
> everything or configured enterprise subnets) that should be protected.
> There are corporate VPNs that don't allow any bypass, period. For those=

> setups, all outbound traffic will be sent using that SA and all
> unprotected inbound traffic will be discarded. Where bypassing is
> allowed, specific bypass rules need to be in place. If the PROTECT
> condition applies (say, where the remote address falls within the range=

> of configured subnets), the packet will be sent via the VPN tunnel. If
> there is a BYPASS rule that applies, it will be bypassed. All other
> packets will be discarded. The HA IP address will fall under the range
> of addresses within the enterprise subnets that would be setup for a
> PROTECT condition in the SPD.=20
>=20
> If you are relying on the order of SPD entries for the bypass rule to
> catch it before the protect rule, it is problematic, since that will
> result in all RRQs being bypassed. If you go through the protect rule
> first, it is going to be protected, given that the HA IP address is
> likely to be part of the range of addresses that need protection.=20

WHOA!!!

RFC 4301 clearly specifies that the SPD is an *ordered* database, exactly=

for cases like this, where rules overlap and it is important to process
them in the correct order.  This is also what I'd expect from practical
experience.

This is just not a problem.

> Also, I'd say that if you expect MIP-specific IPsec SPD entries to be
> cumpulsorily present on the host/VPN GW, this document needs to spell
> those out. My main problem here is that the document is written such
> that it just uses a corporate VPN with MOBIKE capability. I don't see
> how that is sufficient.=20

Actually, since MIP implementations need to have low-level access to raw
incoming packets, to do their job right, they work through mechanisms
like xBSD's BPF-taps or Windows' various slots low in the IP stack where
drivers can attach.  So the choice of using SPD entries to bypass the
VPN tunnel is only one way of doing this; there are other ways which
also will work fine, and practical experience is probably needed to
determine what approach will be best in which market.  I don't think we
should put all of that in this draft; as an implementor, this seems to me=

like something which has to be worked out, but doesn't need to be covered=

in the document necessarily.


	Henrik




--------------enig9BDB224F22EE8B1821737A1E
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iD8DBQFFgdPzeVhrtTJkXCMRAoRKAKCbpIzt6SKvhVbmw4pNzRjrWZNCNACfYMPp
DN213Tln1cV3xUcWhi7t5Ws=
=M3Pi
-----END PGP SIGNATURE-----

--------------enig9BDB224F22EE8B1821737A1E--


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

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

--===============1434411367==--




From mip4-bounces@ietf.org Thu Dec 14 18:47:58 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gv0Is-0003tW-KS; Thu, 14 Dec 2006 18:47:54 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gv0Iq-0003tM-VA
	for mip4@ietf.org; Thu, 14 Dec 2006 18:47:52 -0500
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gv0Io-0006aP-C5
	for mip4@ietf.org; Thu, 14 Dec 2006 18:47:52 -0500
Received: from crowley.qualcomm.com (crowley.qualcomm.com [129.46.61.151])
	by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	kBENllNG030598
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Thu, 14 Dec 2006 15:47:48 -0800
Received: from SANEXCAS03.na.qualcomm.com (sanexcas03.qualcomm.com
	[172.30.32.65])
	by crowley.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	kBENlkuJ005869; Thu, 14 Dec 2006 15:47:46 -0800 (PST)
Received: from NAEX13.na.qualcomm.com ([129.46.51.248]) by
	SANEXCAS03.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 14 Dec 2006 15:47:45 -0800
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
Subject: RE: [Mip4] WGLC Comments: draft-ietf-mip4-mobike-connectivity-01.txt
Date: Thu, 14 Dec 2006 15:47:57 -0800
Message-ID: <C24CB51D5AA800449982D9BCB903251335E9FB@NAEX13.na.qualcomm.com>
In-Reply-To: <4581D3F3.20509@levkowetz.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip4] WGLC Comments: draft-ietf-mip4-mobike-connectivity-01.txt
Thread-Index: Accf0Y2Y4/4/bq8/SgqXLjNF+PSvCQAB6qEA
From: "Narayanan, Vidya" <vidyan@qualcomm.com>
To: "Henrik Levkowetz" <henrik@levkowetz.com>
X-OriginalArrivalTime: 14 Dec 2006 23:47:45.0948 (UTC)
	FILETIME=[4122CDC0:01C71FDA]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93e7fb8fef2e780414389440f367c879
Cc: Mobile IPv4 Mailing List <mip4@ietf.org>,
	Vijay Devarapalli <vijay.devarapalli@azairenet.com>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Hi Henrik,
Apologies for the delay. Vijay and I also exchanged a lot of emails
offline on the topic. Eventually, we figured out that we agree on what
needs to be done (that a bypass entry for the local IP address needs to
be there), but disagree on whether the draft should be providing clarity
on this. I feel that it will help to have some text in the draft, but,
will leave it up to the authors to decide.=20

Also, I think it is worth mentioning that enterprise IP addresses may be
visible on untrusted networks, due to transmission of the RRQ, while
bypassing the VPN - the i-HA IP address will be available in the clear.=20

Regards,
Vidya=20

> -----Original Message-----
> From: Henrik Levkowetz [mailto:henrik@levkowetz.com]=20
> Sent: Thursday, December 14, 2006 2:45 PM
> To: Narayanan, Vidya
> Cc: Vijay Devarapalli; Mobile IPv4 Mailing List
> Subject: Re: [Mip4] WGLC Comments:=20
> draft-ietf-mip4-mobike-connectivity-01.txt
>=20
> Re-sending this.  Vidya, I still haven't seen a response from=20
> you to this.  Is our discussion complete regarding these points?
>=20
> 	Henrik
>=20
> on 2006-12-14 03:45 Narayanan, Vidya said the following:
> > =20
> >=20
> >> -----Original Message-----
> >> From: Vijay Devarapalli [mailto:vijay.devarapalli@AzaireNet.com]
> >> Sent: Wednesday, December 13, 2006 6:26 PM
> >> To: Henrik Levkowetz
> >> Cc: Narayanan, Vidya; Mobile IPv4 Mailing List
> >> Subject: Re: [Mip4] WGLC Comments:=20
> >> draft-ietf-mip4-mobike-connectivity-01.txt
> >>=20
> >> Henrik Levkowetz wrote:
> >> >=20
> >> > on 2006-12-13 23:18 Narayanan, Vidya said the following:
> >> >> <snip>
> >> >>
> >> >>> *Exactly*.  So rules which says that port 434 from TIA to
> >> HA always
> >> >>> go through the tunnel, port 434 from non-TIA to HA=20
> never goes to=20
> >> >>> tunnel will work.  No need for anything more complex.
> >> >>>
> >> >> A rule to the effect of "UDP Port =3D 434, Local IP=20
> address !=3D TIA,=20
> >> >> Remote IP address =3D HA --> Bypass" is not something that
> >> can be set
> >> >> up, in accordance with RFC4301, as far as I know.
> >> >=20
> >> > Why on earth not?  You'd say UDP, Port=3D434, Dest=3DHA,
> >> Src=3DTIA (which is
> >> > a known, fixed address, just as HA is) --> Tunnel, and if
> >> this isn't
> >> > taken, you have UDP, Port=3D434, Dest=3DHA --> Bypass.
> >>=20
> >> It is actually trivial to setup SPD entries so that you=20
> can send one=20
> >> registration request from the local IP address with the=20
> destination=20
> >> set to the HA so that it bypasses the IPsec engine. There=20
> will be one=20
> >> for the registration request with source address set to the TIA.
> >>=20
> >=20
> > I am missing something. In a typical remote access VPN setup, there=20
> > will be one SA used to protect any traffic being sent from=20
> the host.=20
> > So, the SPD entry will specify a range of remote IP addresses=20
> > (typically, either everything or configured enterprise=20
> subnets) that should be protected.
> > There are corporate VPNs that don't allow any bypass, period. For=20
> > those setups, all outbound traffic will be sent using that=20
> SA and all=20
> > unprotected inbound traffic will be discarded. Where bypassing is=20
> > allowed, specific bypass rules need to be in place. If the PROTECT=20
> > condition applies (say, where the remote address falls within the=20
> > range of configured subnets), the packet will be sent via the VPN=20
> > tunnel. If there is a BYPASS rule that applies, it will be=20
> bypassed.=20
> > All other packets will be discarded. The HA IP address will=20
> fall under=20
> > the range of addresses within the enterprise subnets that would be=20
> > setup for a PROTECT condition in the SPD.
> >=20
> > If you are relying on the order of SPD entries for the=20
> bypass rule to=20
> > catch it before the protect rule, it is problematic, since=20
> that will=20
> > result in all RRQs being bypassed. If you go through the=20
> protect rule=20
> > first, it is going to be protected, given that the HA IP address is=20
> > likely to be part of the range of addresses that need protection.
>=20
> WHOA!!!
>=20
> RFC 4301 clearly specifies that the SPD is an *ordered*=20
> database, exactly for cases like this, where rules overlap=20
> and it is important to process them in the correct order. =20
> This is also what I'd expect from practical experience.
>=20
> This is just not a problem.
>=20
> > Also, I'd say that if you expect MIP-specific IPsec SPD=20
> entries to be=20
> > cumpulsorily present on the host/VPN GW, this document=20
> needs to spell=20
> > those out. My main problem here is that the document is=20
> written such=20
> > that it just uses a corporate VPN with MOBIKE capability. I=20
> don't see=20
> > how that is sufficient.
>=20
> Actually, since MIP implementations need to have low-level=20
> access to raw incoming packets, to do their job right, they=20
> work through mechanisms like xBSD's BPF-taps or Windows'=20
> various slots low in the IP stack where drivers can attach. =20
> So the choice of using SPD entries to bypass the VPN tunnel=20
> is only one way of doing this; there are other ways which=20
> also will work fine, and practical experience is probably=20
> needed to determine what approach will be best in which=20
> market.  I don't think we should put all of that in this=20
> draft; as an implementor, this seems to me like something=20
> which has to be worked out, but doesn't need to be covered in=20
> the document necessarily.
>=20
>=20
> 	Henrik
>=20
>=20
>=20
>=20

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Thu Dec 14 19:16:06 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gv0k7-0006Q4-U6; Thu, 14 Dec 2006 19:16:03 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gv0k7-0006Pz-5U
	for mip4@ietf.org; Thu, 14 Dec 2006 19:16:03 -0500
Received: from av7-1-sn3.vrr.skanova.net ([81.228.9.181])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gv0k4-0003RO-Jv
	for mip4@ietf.org; Thu, 14 Dec 2006 19:16:03 -0500
Received: by av7-1-sn3.vrr.skanova.net (Postfix, from userid 502)
	id 560BE37EF8; Fri, 15 Dec 2006 01:15:36 +0100 (CET)
Received: from smtp3-1-sn3.vrr.skanova.net (smtp3-1-sn3.vrr.skanova.net
	[81.228.9.101]) by av7-1-sn3.vrr.skanova.net (Postfix) with ESMTP
	id 2754537EC5; Fri, 15 Dec 2006 01:15:36 +0100 (CET)
Received: from shiraz.levkowetz.com (81-232-110-214-no16.tbcn.telia.com
	[81.232.110.214])
	by smtp3-1-sn3.vrr.skanova.net (Postfix) with ESMTP id 4477B37E47;
	Fri, 15 Dec 2006 01:15:55 +0100 (CET)
Received: from localhost ([127.0.0.1])
	by shiraz.levkowetz.com with esmtp (Exim 4.63)
	(envelope-from <henrik@levkowetz.com>)
	id 1Gv0jy-0001Mx-Ii; Fri, 15 Dec 2006 01:15:54 +0100
Message-ID: <4581E938.6080400@levkowetz.com>
Date: Fri, 15 Dec 2006 01:15:52 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Thunderbird 1.5.0.8 (Macintosh/20061025)
MIME-Version: 1.0
To: "Narayanan, Vidya" <vidyan@qualcomm.com>
Subject: Re: [Mip4] WGLC Comments: draft-ietf-mip4-mobike-connectivity-01.txt
References: <C24CB51D5AA800449982D9BCB903251335E9FB@NAEX13.na.qualcomm.com>
In-Reply-To: <C24CB51D5AA800449982D9BCB903251335E9FB@NAEX13.na.qualcomm.com>
X-Enigmail-Version: 0.94.1.2
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: vidyan@qualcomm.com, vijay.devarapalli@azairenet.com,
	mip4@ietf.org, henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on shiraz.levkowetz.com);
	SAEximRunCond expanded to false
X-Spam-Score: 0.1 (/)
X-Scan-Signature: ded6070f7eed56e10c4f4d0d5043d9c7
Cc: Mobile IPv4 Mailing List <mip4@ietf.org>,
	Vijay Devarapalli <vijay.devarapalli@azairenet.com>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2016889880=="
Errors-To: mip4-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============2016889880==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig540EF77CC2794B8B78B29581"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig540EF77CC2794B8B78B29581
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable



on 2006-12-15 00:47 Narayanan, Vidya said the following:
> Hi Henrik,
> Apologies for the delay. Vijay and I also exchanged a lot of emails
> offline on the topic. Eventually, we figured out that we agree on what
> needs to be done (that a bypass entry for the local IP address needs to=

> be there), but disagree on whether the draft should be providing clarit=
y
> on this. I feel that it will help to have some text in the draft, but,
> will leave it up to the authors to decide.=20

Ok.  So I take it this means that you don't have any further reservations=

with regards to the ability to specify bypass SPD entries or effect bypas=
s
in other ways.

> Also, I think it is worth mentioning that enterprise IP addresses may b=
e
> visible on untrusted networks, due to transmission of the RRQ, while
> bypassing the VPN - the i-HA IP address will be available in the clear.=
=20

New topic here.  The observation seems to be correct.  I'll leave it up t=
o
the authors whether they want to comment further on this.


	Henrik


> Regards,
> Vidya=20
>=20
>> -----Original Message-----
>> From: Henrik Levkowetz [mailto:henrik@levkowetz.com]=20
>> Sent: Thursday, December 14, 2006 2:45 PM
>> To: Narayanan, Vidya
>> Cc: Vijay Devarapalli; Mobile IPv4 Mailing List
>> Subject: Re: [Mip4] WGLC Comments:=20
>> draft-ietf-mip4-mobike-connectivity-01.txt
>>=20
>> Re-sending this.  Vidya, I still haven't seen a response from=20
>> you to this.  Is our discussion complete regarding these points?
>>=20
>> 	Henrik
>>=20
>> on 2006-12-14 03:45 Narayanan, Vidya said the following:
>> > =20
>> >=20
>> >> -----Original Message-----
>> >> From: Vijay Devarapalli [mailto:vijay.devarapalli@AzaireNet.com]
>> >> Sent: Wednesday, December 13, 2006 6:26 PM
>> >> To: Henrik Levkowetz
>> >> Cc: Narayanan, Vidya; Mobile IPv4 Mailing List
>> >> Subject: Re: [Mip4] WGLC Comments:=20
>> >> draft-ietf-mip4-mobike-connectivity-01.txt
>> >>=20
>> >> Henrik Levkowetz wrote:
>> >> >=20
>> >> > on 2006-12-13 23:18 Narayanan, Vidya said the following:
>> >> >> <snip>
>> >> >>
>> >> >>> *Exactly*.  So rules which says that port 434 from TIA to
>> >> HA always
>> >> >>> go through the tunnel, port 434 from non-TIA to HA=20
>> never goes to=20
>> >> >>> tunnel will work.  No need for anything more complex.
>> >> >>>
>> >> >> A rule to the effect of "UDP Port =3D 434, Local IP=20
>> address !=3D TIA,=20
>> >> >> Remote IP address =3D HA --> Bypass" is not something that
>> >> can be set
>> >> >> up, in accordance with RFC4301, as far as I know.
>> >> >=20
>> >> > Why on earth not?  You'd say UDP, Port=3D434, Dest=3DHA,
>> >> Src=3DTIA (which is
>> >> > a known, fixed address, just as HA is) --> Tunnel, and if
>> >> this isn't
>> >> > taken, you have UDP, Port=3D434, Dest=3DHA --> Bypass.
>> >>=20
>> >> It is actually trivial to setup SPD entries so that you=20
>> can send one=20
>> >> registration request from the local IP address with the=20
>> destination=20
>> >> set to the HA so that it bypasses the IPsec engine. There=20
>> will be one=20
>> >> for the registration request with source address set to the TIA.
>> >>=20
>> >=20
>> > I am missing something. In a typical remote access VPN setup, there =

>> > will be one SA used to protect any traffic being sent from=20
>> the host.=20
>> > So, the SPD entry will specify a range of remote IP addresses=20
>> > (typically, either everything or configured enterprise=20
>> subnets) that should be protected.
>> > There are corporate VPNs that don't allow any bypass, period. For=20
>> > those setups, all outbound traffic will be sent using that=20
>> SA and all=20
>> > unprotected inbound traffic will be discarded. Where bypassing is=20
>> > allowed, specific bypass rules need to be in place. If the PROTECT=20
>> > condition applies (say, where the remote address falls within the=20
>> > range of configured subnets), the packet will be sent via the VPN=20
>> > tunnel. If there is a BYPASS rule that applies, it will be=20
>> bypassed.=20
>> > All other packets will be discarded. The HA IP address will=20
>> fall under=20
>> > the range of addresses within the enterprise subnets that would be=20
>> > setup for a PROTECT condition in the SPD.
>> >=20
>> > If you are relying on the order of SPD entries for the=20
>> bypass rule to=20
>> > catch it before the protect rule, it is problematic, since=20
>> that will=20
>> > result in all RRQs being bypassed. If you go through the=20
>> protect rule=20
>> > first, it is going to be protected, given that the HA IP address is =

>> > likely to be part of the range of addresses that need protection.
>>=20
>> WHOA!!!
>>=20
>> RFC 4301 clearly specifies that the SPD is an *ordered*=20
>> database, exactly for cases like this, where rules overlap=20
>> and it is important to process them in the correct order. =20
>> This is also what I'd expect from practical experience.
>>=20
>> This is just not a problem.
>>=20
>> > Also, I'd say that if you expect MIP-specific IPsec SPD=20
>> entries to be=20
>> > cumpulsorily present on the host/VPN GW, this document=20
>> needs to spell=20
>> > those out. My main problem here is that the document is=20
>> written such=20
>> > that it just uses a corporate VPN with MOBIKE capability. I=20
>> don't see=20
>> > how that is sufficient.
>>=20
>> Actually, since MIP implementations need to have low-level=20
>> access to raw incoming packets, to do their job right, they=20
>> work through mechanisms like xBSD's BPF-taps or Windows'=20
>> various slots low in the IP stack where drivers can attach. =20
>> So the choice of using SPD entries to bypass the VPN tunnel=20
>> is only one way of doing this; there are other ways which=20
>> also will work fine, and practical experience is probably=20
>> needed to determine what approach will be best in which=20
>> market.  I don't think we should put all of that in this=20
>> draft; as an implementor, this seems to me like something=20
>> which has to be worked out, but doesn't need to be covered in=20
>> the document necessarily.
>>=20
>>=20
>> 	Henrik
>>=20
>>=20
>>=20
>>=20
>=20


--------------enig540EF77CC2794B8B78B29581
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iD8DBQFFgek4eVhrtTJkXCMRAsvSAKCHTr7l2TWvQvl0VF5Ap3jyVHjhFACfUoam
ksVK8nWO3T4yu93HlIhS2co=
=S8UB
-----END PGP SIGNATURE-----

--------------enig540EF77CC2794B8B78B29581--


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

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

--===============2016889880==--




From mip4-bounces@ietf.org Thu Dec 14 19:27:32 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gv0vC-0002eR-7U; Thu, 14 Dec 2006 19:27:30 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gv0vA-0002bR-Gs
	for mip4@ietf.org; Thu, 14 Dec 2006 19:27:28 -0500
Received: from mail2.azairenet.com ([66.92.223.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gv0v9-0005Ad-0d
	for mip4@ietf.org; Thu, 14 Dec 2006 19:27:28 -0500
Received: from [127.0.0.1] ([66.92.223.6]) by mail2.azairenet.com over TLS
	secured channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 14 Dec 2006 16:27:24 -0800
Message-ID: <4581EBE9.6010607@azairenet.com>
Date: Thu, 14 Dec 2006 16:27:21 -0800
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: Henrik Levkowetz <henrik@levkowetz.com>
Subject: Re: [Mip4] WGLC Comments: draft-ietf-mip4-mobike-connectivity-01.txt
References: <C24CB51D5AA800449982D9BCB903251335E9FB@NAEX13.na.qualcomm.com>
	<4581E938.6080400@levkowetz.com>
In-Reply-To: <4581E938.6080400@levkowetz.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 15 Dec 2006 00:27:24.0635 (UTC)
	FILETIME=[CAF1A2B0:01C71FDF]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: "Narayanan, Vidya" <vidyan@qualcomm.com>,
	Mobile IPv4 Mailing List <mip4@ietf.org>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Henrik Levkowetz wrote:

>> Also, I think it is worth mentioning that enterprise IP addresses may be
>> visible on untrusted networks, due to transmission of the RRQ, while
>> bypassing the VPN - the i-HA IP address will be available in the clear. 
> 
> New topic here.  The observation seems to be correct.  I'll leave it up to
> the authors whether they want to comment further on this.

We could add the following text in the Security
Considerations section.

    When the mobile node sends a registration request to the i-HA from an
    untrusted network that does not go through the IPsec tunnel, it may
    be leaking the i-HA's address and its own home address to the
    untrusted network.  This may be a concern in some deployments.

Vijay

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Thu Dec 14 19:41:36 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gv18p-0007or-0k; Thu, 14 Dec 2006 19:41:35 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gv18o-0007om-6I
	for mip4@ietf.org; Thu, 14 Dec 2006 19:41:34 -0500
Received: from av9-1-sn2.hy.skanova.net ([81.228.8.179])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gv18m-0006qp-P2
	for mip4@ietf.org; Thu, 14 Dec 2006 19:41:34 -0500
Received: by av9-1-sn2.hy.skanova.net (Postfix, from userid 502)
	id E3EB037F36; Fri, 15 Dec 2006 01:41:31 +0100 (CET)
Received: from smtp4-1-sn2.hy.skanova.net (smtp4-1-sn2.hy.skanova.net
	[81.228.8.92]) by av9-1-sn2.hy.skanova.net (Postfix) with ESMTP
	id BCEF037E8D; Fri, 15 Dec 2006 01:41:31 +0100 (CET)
Received: from shiraz.levkowetz.com (81-232-110-214-no16.tbcn.telia.com
	[81.232.110.214])
	by smtp4-1-sn2.hy.skanova.net (Postfix) with ESMTP id 6070C37E44;
	Fri, 15 Dec 2006 01:41:31 +0100 (CET)
Received: from localhost ([127.0.0.1])
	by shiraz.levkowetz.com with esmtp (Exim 4.63)
	(envelope-from <henrik@levkowetz.com>)
	id 1Gv18l-0005zu-37; Fri, 15 Dec 2006 01:41:31 +0100
Message-ID: <4581EF3A.7030602@levkowetz.com>
Date: Fri, 15 Dec 2006 01:41:30 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Thunderbird 1.5.0.8 (Macintosh/20061025)
MIME-Version: 1.0
To: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
Subject: Re: [Mip4] WGLC Comments: draft-ietf-mip4-mobike-connectivity-01.txt
References: <C24CB51D5AA800449982D9BCB903251335E9FB@NAEX13.na.qualcomm.com>
	<4581E938.6080400@levkowetz.com> <4581EBE9.6010607@azairenet.com>
In-Reply-To: <4581EBE9.6010607@azairenet.com>
X-Enigmail-Version: 0.94.1.2
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: vijay.devarapalli@azairenet.com, vidyan@qualcomm.com,
	mip4@ietf.org, henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on shiraz.levkowetz.com);
	SAEximRunCond expanded to false
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Cc: "Narayanan, Vidya" <vidyan@qualcomm.com>,
	Mobile IPv4 Mailing List <mip4@ietf.org>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1801343411=="
Errors-To: mip4-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============1801343411==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enig9B748D06C299FA8B4FB0DDA7"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig9B748D06C299FA8B4FB0DDA7
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi Vijay,

on 2006-12-15 01:27 Vijay Devarapalli said the following:
> Henrik Levkowetz wrote:
>=20
>>> Also, I think it is worth mentioning that enterprise IP addresses may=
 be
>>> visible on untrusted networks, due to transmission of the RRQ, while
>>> bypassing the VPN - the i-HA IP address will be available in the clea=
r.=20
>>=20
>> New topic here.  The observation seems to be correct.  I'll leave it u=
p to
>> the authors whether they want to comment further on this.
>=20
> We could add the following text in the Security
> Considerations section.
>=20
>     When the mobile node sends a registration request to the i-HA from =
an
>     untrusted network that does not go through the IPsec tunnel, it may=

>     be leaking the i-HA's address and its own home address to the
>     untrusted network.  This may be a concern in some deployments.

Works for me.


	Henrik


--------------enig9B748D06C299FA8B4FB0DDA7
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iD8DBQFFge86eVhrtTJkXCMRAkLIAKC8UsYIVxAzId+aqTw6Q8296/lrTgCfR7g9
BmfouSMBRJjLwDc8cQJ5FCw=
=4R8f
-----END PGP SIGNATURE-----

--------------enig9B748D06C299FA8B4FB0DDA7--


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

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

--===============1801343411==--




From mip4-bounces@ietf.org Thu Dec 14 19:48:42 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gv1Fb-0001yM-3M; Thu, 14 Dec 2006 19:48:35 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gv1Fa-0001yH-8A
	for mip4@ietf.org; Thu, 14 Dec 2006 19:48:34 -0500
Received: from ithilien.qualcomm.com ([129.46.51.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gv1FY-0007q0-T1
	for mip4@ietf.org; Thu, 14 Dec 2006 19:48:34 -0500
Received: from neophyte.qualcomm.com (neophyte.qualcomm.com [129.46.61.149])
	by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	kBF0mUSv030007
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Thu, 14 Dec 2006 16:48:31 -0800
Received: from SANEXCAS03.na.qualcomm.com (sanexcas03.qualcomm.com
	[172.30.32.65])
	by neophyte.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	kBF0mTUp018117; Thu, 14 Dec 2006 16:48:30 -0800
Received: from NAEX13.na.qualcomm.com ([129.46.51.248]) by
	SANEXCAS03.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 14 Dec 2006 16:48:29 -0800
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
Subject: RE: [Mip4] WGLC Comments: draft-ietf-mip4-mobike-connectivity-01.txt
Date: Thu, 14 Dec 2006 16:48:25 -0800
Message-ID: <C24CB51D5AA800449982D9BCB903251335EA1D@NAEX13.na.qualcomm.com>
In-Reply-To: <4581EF3A.7030602@levkowetz.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip4] WGLC Comments: draft-ietf-mip4-mobike-connectivity-01.txt
Thread-Index: Accf4co9sqlB8IQCQRS34FSVRmzN0QAAOwbw
From: "Narayanan, Vidya" <vidyan@qualcomm.com>
To: "Henrik Levkowetz" <henrik@levkowetz.com>,
	"Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
X-OriginalArrivalTime: 15 Dec 2006 00:48:29.0737 (UTC)
	FILETIME=[BD00E190:01C71FE2]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Cc: Mobile IPv4 Mailing List <mip4@ietf.org>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Sounds good to me too. =20

> -----Original Message-----
> From: Henrik Levkowetz [mailto:henrik@levkowetz.com]=20
> Sent: Thursday, December 14, 2006 4:42 PM
> To: Vijay Devarapalli
> Cc: Narayanan, Vidya; Mobile IPv4 Mailing List
> Subject: Re: [Mip4] WGLC Comments:=20
> draft-ietf-mip4-mobike-connectivity-01.txt
>=20
> Hi Vijay,
>=20
> on 2006-12-15 01:27 Vijay Devarapalli said the following:
> > Henrik Levkowetz wrote:
> >=20
> >>> Also, I think it is worth mentioning that enterprise IP addresses=20
> >>> may be visible on untrusted networks, due to transmission of the=20
> >>> RRQ, while bypassing the VPN - the i-HA IP address will=20
> be available in the clear.
> >>=20
> >> New topic here.  The observation seems to be correct. =20
> I'll leave it=20
> >> up to the authors whether they want to comment further on this.
> >=20
> > We could add the following text in the Security Considerations=20
> > section.
> >=20
> >     When the mobile node sends a registration request to=20
> the i-HA from an
> >     untrusted network that does not go through the IPsec=20
> tunnel, it may
> >     be leaking the i-HA's address and its own home address to the
> >     untrusted network.  This may be a concern in some deployments.
>=20
> Works for me.
>=20
>=20
> 	Henrik
>=20
>=20

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Fri Dec 15 01:02:40 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gv69R-00059O-3E; Fri, 15 Dec 2006 01:02:33 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gv69P-00057g-Ac
	for mip4@ietf.org; Fri, 15 Dec 2006 01:02:31 -0500
Received: from ns.academica.fi ([82.133.251.2])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gv69N-0008HT-08
	for mip4@ietf.org; Fri, 15 Dec 2006 01:02:31 -0500
Received: from [82.133.140.68] (ip82-133-140-68.customer.academica.fi
	[82.133.140.68])
	by ns.academica.fi (Postfix) with ESMTP id 5F1CD19979D;
	Fri, 15 Dec 2006 07:00:04 +0200 (EET)
Message-ID: <45823A04.4020800@iki.fi>
Date: Fri, 15 Dec 2006 08:00:36 +0200
From: Sami Vaarala <sami.vaarala@iki.fi>
User-Agent: Icedove 1.5.0.8 (X11/20061128)
MIME-Version: 1.0
To: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
Subject: Re: [Mip4] WGLC Comments: draft-ietf-mip4-mobike-connectivity-01.txt
References: <C24CB51D5AA800449982D9BCB903251335E9FB@NAEX13.na.qualcomm.com>	<4581E938.6080400@levkowetz.com>
	<4581EBE9.6010607@azairenet.com>
In-Reply-To: <4581EBE9.6010607@azairenet.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Cc: "Narayanan, Vidya" <vidyan@qualcomm.com>,
	Mobile IPv4 Mailing List <mip4@ietf.org>,
	Henrik Levkowetz <henrik@levkowetz.com>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Vijay Devarapalli wrote:
> Henrik Levkowetz wrote:
> 
>>> Also, I think it is worth mentioning that enterprise IP addresses may be
>>> visible on untrusted networks, due to transmission of the RRQ, while
>>> bypassing the VPN - the i-HA IP address will be available in the clear. 
>>
>> New topic here.  The observation seems to be correct.  I'll leave it 
>> up to
>> the authors whether they want to comment further on this.
> 
> We could add the following text in the Security
> Considerations section.
> 
>    When the mobile node sends a registration request to the i-HA from an
>    untrusted network that does not go through the IPsec tunnel, it may
>    be leaking the i-HA's address and its own home address to the
>    untrusted network.  This may be a concern in some deployments.

I can live with that, though I think the potential concern is a bit wider.
How about this:

     When the mobile node sends a registration request to the i-HA from an
     untrusted network that does not go through the IPsec tunnel, the request
     leaks some information possibly useful for an attacker.  In particular,
     the request reveals the i-HA address (and other address information),
     the user's NAI (if present), and may provide data which allows an
     off-line brute-force attack on the MN-HA authentication key.

I guess an underlying assumption here has been that the i-MIP setup is not
considered to be confidential.  Some users may be uncomfortable with their
username (NAI) being revealed.

-Sami

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Fri Dec 15 01:53:24 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gv6wb-0006wB-Q8; Fri, 15 Dec 2006 01:53:21 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gv6wY-0006u4-DR
	for mip4@ietf.org; Fri, 15 Dec 2006 01:53:18 -0500
Received: from mail2.azairenet.com ([66.92.223.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gv6ut-0006P2-HL
	for mip4@ietf.org; Fri, 15 Dec 2006 01:51:36 -0500
Received: from [127.0.0.1] ([66.92.223.6]) by mail2.azairenet.com over TLS
	secured channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 14 Dec 2006 22:51:34 -0800
Message-ID: <458245F4.7030905@azairenet.com>
Date: Thu, 14 Dec 2006 22:51:32 -0800
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: Sami Vaarala <sami.vaarala@iki.fi>
Subject: Re: [Mip4] WGLC Comments: draft-ietf-mip4-mobike-connectivity-01.txt
References: <C24CB51D5AA800449982D9BCB903251335E9FB@NAEX13.na.qualcomm.com>	<4581E938.6080400@levkowetz.com>
	<4581EBE9.6010607@azairenet.com> <45823A04.4020800@iki.fi>
In-Reply-To: <45823A04.4020800@iki.fi>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 15 Dec 2006 06:51:34.0562 (UTC)
	FILETIME=[75C56020:01C72015]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Cc: "Narayanan, Vidya" <vidyan@qualcomm.com>,
	Mobile IPv4 Mailing List <mip4@ietf.org>,
	Henrik Levkowetz <henrik@levkowetz.com>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Sami Vaarala wrote:
> Vijay Devarapalli wrote:
>> Henrik Levkowetz wrote:
>>
>>>> Also, I think it is worth mentioning that enterprise IP addresses 
>>>> may be
>>>> visible on untrusted networks, due to transmission of the RRQ, while
>>>> bypassing the VPN - the i-HA IP address will be available in the clear. 
>>>
>>> New topic here.  The observation seems to be correct.  I'll leave it 
>>> up to
>>> the authors whether they want to comment further on this.
>>
>> We could add the following text in the Security
>> Considerations section.
>>
>>    When the mobile node sends a registration request to the i-HA from an
>>    untrusted network that does not go through the IPsec tunnel, it may
>>    be leaking the i-HA's address and its own home address to the
>>    untrusted network.  This may be a concern in some deployments.
> 
> I can live with that, though I think the potential concern is a bit wider.
> How about this:
> 
>     When the mobile node sends a registration request to the i-HA from an
>     untrusted network that does not go through the IPsec tunnel, the 
> request
>     leaks some information possibly useful for an attacker.  In particular,
>     the request reveals the i-HA address (and other address information),
>     the user's NAI (if present), and may provide data which allows an
>     off-line brute-force attack on the MN-HA authentication key.
> 
> I guess an underlying assumption here has been that the i-MIP setup is not
> considered to be confidential.  Some users may be uncomfortable with their
> username (NAI) being revealed.

None of these registration requests from the untrusted
network including the registration request from the
mobile node make to the i-HA. They are all dropped at
the Enterprise firewall.

So I don't understand the brute-force attack on the
MN-HA authentication key.

BTW, this text needs to be added to
draft-ietf-mip4-vpn-problem-solution too.

Vijay

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Fri Dec 15 02:32:05 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gv7Y5-0004gm-Ac; Fri, 15 Dec 2006 02:32:05 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gv7Y3-0004gd-KV
	for mip4@ietf.org; Fri, 15 Dec 2006 02:32:03 -0500
Received: from firewall.codebay.fi ([212.68.7.211])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gv7Y2-00049B-6I
	for mip4@ietf.org; Fri, 15 Dec 2006 02:32:03 -0500
Received: from [172.20.100.198] (helo=[192.168.92.130])
	by firewall.codebay.fi with esmtp (Exim 4.63)
	(envelope-from <sami.vaarala@iki.fi>)
	id 1Gv7Xp-0006Tz-2g; Fri, 15 Dec 2006 09:31:49 +0200
Message-ID: <45824C9B.7070905@iki.fi>
Date: Fri, 15 Dec 2006 09:19:55 +0200
From: Sami Vaarala <sami.vaarala@iki.fi>
User-Agent: Icedove 1.5.0.8 (X11/20061128)
MIME-Version: 1.0
To: Vijay Devarapalli <vijay.devarapalli@AzaireNet.com>
Subject: Re: [Mip4] WGLC Comments: draft-ietf-mip4-mobike-connectivity-01.txt
References: <C24CB51D5AA800449982D9BCB903251335E9FB@NAEX13.na.qualcomm.com>	<4581E938.6080400@levkowetz.com>
	<4581EBE9.6010607@azairenet.com> <45823A04.4020800@iki.fi>
	<458245F4.7030905@azairenet.com>
In-Reply-To: <458245F4.7030905@azairenet.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
Cc: "Narayanan, Vidya" <vidyan@qualcomm.com>,
	Mobile IPv4 Mailing List <mip4@ietf.org>,
	Henrik Levkowetz <henrik@levkowetz.com>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Vijay Devarapalli wrote:
> Sami Vaarala wrote:
>> Vijay Devarapalli wrote:
>>> Henrik Levkowetz wrote:
>>>
>>>>> Also, I think it is worth mentioning that enterprise IP addresses 
>>>>> may be
>>>>> visible on untrusted networks, due to transmission of the RRQ, while
>>>>> bypassing the VPN - the i-HA IP address will be available in the 
>>>>> clear. 
>>>>
>>>> New topic here.  The observation seems to be correct.  I'll leave it 
>>>> up to
>>>> the authors whether they want to comment further on this.
>>>
>>> We could add the following text in the Security
>>> Considerations section.
>>>
>>>    When the mobile node sends a registration request to the i-HA from an
>>>    untrusted network that does not go through the IPsec tunnel, it may
>>>    be leaking the i-HA's address and its own home address to the
>>>    untrusted network.  This may be a concern in some deployments.
>>
>> I can live with that, though I think the potential concern is a bit 
>> wider.
>> How about this:
>>
>>     When the mobile node sends a registration request to the i-HA from an
>>     untrusted network that does not go through the IPsec tunnel, the 
>> request
>>     leaks some information possibly useful for an attacker.  In 
>> particular,
>>     the request reveals the i-HA address (and other address information),
>>     the user's NAI (if present), and may provide data which allows an
>>     off-line brute-force attack on the MN-HA authentication key.
>>
>> I guess an underlying assumption here has been that the i-MIP setup is 
>> not
>> considered to be confidential.  Some users may be uncomfortable with 
>> their
>> username (NAI) being revealed.
> 
> None of these registration requests from the untrusted
> network including the registration request from the
> mobile node make to the i-HA. They are all dropped at
> the Enterprise firewall.

When the MN visits an untrusted network and attempts to send an RRQ to
the i-HA, the RRQ is visible potentially to anyone, including any
attackers.  The RRQ has an authenticator (which may be, for instance,
HMAC-based).  Given the full RRQ packet, a brute force attack on the
HMAC key can be launched; this is an off-line attack because all you
need is the RRQ and you can begin churning away on possible HMAC keys,
the MN-HA authentication data will give you the correct answer for
comparison.  This attack doesn't involve the i-HA in any way, all you
need is the RRQ packet.

> BTW, this text needs to be added to
> draft-ietf-mip4-vpn-problem-solution too.

Yup, already added.

BR,

-Sami

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Fri Dec 15 02:40:58 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gv7gg-00081b-H7; Fri, 15 Dec 2006 02:40:58 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gv7gf-00081S-MU
	for mip4@ietf.org; Fri, 15 Dec 2006 02:40:57 -0500
Received: from mail2.azairenet.com ([66.92.223.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gv7ge-0005SC-Bz
	for mip4@ietf.org; Fri, 15 Dec 2006 02:40:57 -0500
Received: from [127.0.0.1] ([66.92.223.6]) by mail2.azairenet.com over TLS
	secured channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 14 Dec 2006 23:40:55 -0800
Message-ID: <45825186.1060908@azairenet.com>
Date: Thu, 14 Dec 2006 23:40:54 -0800
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: Sami Vaarala <sami.vaarala@iki.fi>
Subject: Re: [Mip4] WGLC Comments: draft-ietf-mip4-mobike-connectivity-01.txt
References: <C24CB51D5AA800449982D9BCB903251335E9FB@NAEX13.na.qualcomm.com>	<4581E938.6080400@levkowetz.com>
	<4581EBE9.6010607@azairenet.com> <45823A04.4020800@iki.fi>
	<458245F4.7030905@azairenet.com> <45824C9B.7070905@iki.fi>
In-Reply-To: <45824C9B.7070905@iki.fi>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 15 Dec 2006 07:40:55.0602 (UTC)
	FILETIME=[5AB03920:01C7201C]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d
Cc: "Narayanan, Vidya" <vidyan@qualcomm.com>,
	Mobile IPv4 Mailing List <mip4@ietf.org>,
	Henrik Levkowetz <henrik@levkowetz.com>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Sami Vaarala wrote:
> Vijay Devarapalli wrote:
>> Sami Vaarala wrote:
>>> Vijay Devarapalli wrote:
>>>> Henrik Levkowetz wrote:
>>>>
>>>>>> Also, I think it is worth mentioning that enterprise IP addresses 
>>>>>> may be
>>>>>> visible on untrusted networks, due to transmission of the RRQ, while
>>>>>> bypassing the VPN - the i-HA IP address will be available in the 
>>>>>> clear. 
>>>>>
>>>>> New topic here.  The observation seems to be correct.  I'll leave 
>>>>> it up to
>>>>> the authors whether they want to comment further on this.
>>>>
>>>> We could add the following text in the Security
>>>> Considerations section.
>>>>
>>>>    When the mobile node sends a registration request to the i-HA 
>>>> from an
>>>>    untrusted network that does not go through the IPsec tunnel, it may
>>>>    be leaking the i-HA's address and its own home address to the
>>>>    untrusted network.  This may be a concern in some deployments.
>>>
>>> I can live with that, though I think the potential concern is a bit 
>>> wider.
>>> How about this:
>>>
>>>     When the mobile node sends a registration request to the i-HA 
>>> from an
>>>     untrusted network that does not go through the IPsec tunnel, the 
>>> request
>>>     leaks some information possibly useful for an attacker.  In 
>>> particular,
>>>     the request reveals the i-HA address (and other address 
>>> information),
>>>     the user's NAI (if present), and may provide data which allows an
>>>     off-line brute-force attack on the MN-HA authentication key.
>>>
>>> I guess an underlying assumption here has been that the i-MIP setup 
>>> is not
>>> considered to be confidential.  Some users may be uncomfortable with 
>>> their
>>> username (NAI) being revealed.
>>
>> None of these registration requests from the untrusted
>> network including the registration request from the
>> mobile node make to the i-HA. They are all dropped at
>> the Enterprise firewall.
> 
> When the MN visits an untrusted network and attempts to send an RRQ to
> the i-HA, the RRQ is visible potentially to anyone, including any
> attackers.  The RRQ has an authenticator (which may be, for instance,
> HMAC-based).  Given the full RRQ packet, a brute force attack on the
> HMAC key can be launched; this is an off-line attack because all you
> need is the RRQ and you can begin churning away on possible HMAC keys,
> the MN-HA authentication data will give you the correct answer for
> comparison.  This attack doesn't involve the i-HA in any way, all you
> need is the RRQ packet.

RFC 3344 is susceptible to this attack.

Vijay

> 
>> BTW, this text needs to be added to
>> draft-ietf-mip4-vpn-problem-solution too.
> 
> Yup, already added.
> 
> BR,
> 
> -Sami


-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Fri Dec 15 02:50:47 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gv7qB-0003dY-Re; Fri, 15 Dec 2006 02:50:47 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gv7qB-0003dQ-3z
	for mip4@ietf.org; Fri, 15 Dec 2006 02:50:47 -0500
Received: from firewall.codebay.fi ([212.68.7.211])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gv7q9-00076x-P8
	for mip4@ietf.org; Fri, 15 Dec 2006 02:50:47 -0500
Received: from [172.20.100.198] (helo=[192.168.92.130])
	by firewall.codebay.fi with esmtp (Exim 4.63)
	(envelope-from <sami.vaarala@iki.fi>)
	id 1Gv7q6-0006Un-Lo; Fri, 15 Dec 2006 09:50:42 +0200
Message-ID: <45825108.40207@iki.fi>
Date: Fri, 15 Dec 2006 09:38:48 +0200
From: Sami Vaarala <sami.vaarala@iki.fi>
User-Agent: Icedove 1.5.0.8 (X11/20061128)
MIME-Version: 1.0
To: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
Subject: Re: [Mip4] WGLC Comments: draft-ietf-mip4-mobike-connectivity-01.txt
References: <C24CB51D5AA800449982D9BCB903251335E9FB@NAEX13.na.qualcomm.com>	<4581E938.6080400@levkowetz.com>	<4581EBE9.6010607@azairenet.com>
	<45823A04.4020800@iki.fi>	<458245F4.7030905@azairenet.com>
	<45824C9B.7070905@iki.fi> <45825186.1060908@azairenet.com>
In-Reply-To: <45825186.1060908@azairenet.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Cc: "Narayanan, Vidya" <vidyan@qualcomm.com>,
	Mobile IPv4 Mailing List <mip4@ietf.org>,
	Henrik Levkowetz <henrik@levkowetz.com>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Vijay Devarapalli wrote:
>> When the MN visits an untrusted network and attempts to send an RRQ to
>> the i-HA, the RRQ is visible potentially to anyone, including any
>> attackers.  The RRQ has an authenticator (which may be, for instance,
>> HMAC-based).  Given the full RRQ packet, a brute force attack on the
>> HMAC key can be launched; this is an off-line attack because all you
>> need is the RRQ and you can begin churning away on possible HMAC keys,
>> the MN-HA authentication data will give you the correct answer for
>> comparison.  This attack doesn't involve the i-HA in any way, all you
>> need is the RRQ packet.
> 
> RFC 3344 is susceptible to this attack.

Naturally, and this is why this wasn't mentioned in security
considerations earlier.  I was personally assuming this would be
clear from context.

However, the point was raised that although the dual MIP solution in
general protects leaks of traffic intended for the internal network,
the i-HA RRQ will leak and reveal some information anyway.  It might
be worth mentioning.  At least if we mention that the i-HA address can
be seen from the i-HA RRQ, we should IMO also mention that the i-HA
RRQ is wide open for all other kinds of abuse as well.

BR,

-Sami

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Fri Dec 15 03:44:56 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gv8gV-0007BY-NJ; Fri, 15 Dec 2006 03:44:51 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gv8gU-0007BK-99
	for mip4@ietf.org; Fri, 15 Dec 2006 03:44:50 -0500
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gv8gS-0005bh-Tt
	for mip4@ietf.org; Fri, 15 Dec 2006 03:44:50 -0500
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
	kBF8ijcv005007
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Fri, 15 Dec 2006 00:44:45 -0800
Received: from SANEXCAS03.na.qualcomm.com (sanexcas03.qualcomm.com
	[172.30.32.65])
	by magus.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id kBF8iiCe000136; 
	Fri, 15 Dec 2006 00:44:45 -0800 (PST)
Received: from NAEX13.na.qualcomm.com ([129.46.51.248]) by
	SANEXCAS03.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 15 Dec 2006 00:44:44 -0800
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
Subject: RE: [Mip4] WGLC Comments: draft-ietf-mip4-mobike-connectivity-01.txt
Date: Fri, 15 Dec 2006 00:44:37 -0800
Message-ID: <C24CB51D5AA800449982D9BCB903251335EA41@NAEX13.na.qualcomm.com>
In-Reply-To: <45825108.40207@iki.fi>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip4] WGLC Comments: draft-ietf-mip4-mobike-connectivity-01.txt
Thread-Index: AccgHb5c2uQE/1UcSYO/tqmISWYRhgAB0R9w
From: "Narayanan, Vidya" <vidyan@qualcomm.com>
To: "Sami Vaarala" <sami.vaarala@iki.fi>,
	"Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
X-OriginalArrivalTime: 15 Dec 2006 08:44:44.0389 (UTC)
	FILETIME=[44D2C150:01C72025]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Cc: Mobile IPv4 Mailing List <mip4@ietf.org>,
	Henrik Levkowetz <henrik@levkowetz.com>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

I agree with Sami here. In RFC3344, there is no notion of "enterprise"
level of security. A typical enterprise network will be sensitive to
revealing of internal IP addresses, user names and any crypto data. The
text that Sami sent looks good to me.=20

Vidya=20

> -----Original Message-----
> From: Sami Vaarala [mailto:sami.vaarala@iki.fi]=20
> Sent: Thursday, December 14, 2006 11:39 PM
> To: Vijay Devarapalli
> Cc: Narayanan, Vidya; Mobile IPv4 Mailing List; Henrik Levkowetz
> Subject: Re: [Mip4] WGLC Comments:=20
> draft-ietf-mip4-mobike-connectivity-01.txt
>=20
> Vijay Devarapalli wrote:
> >> When the MN visits an untrusted network and attempts to=20
> send an RRQ=20
> >> to the i-HA, the RRQ is visible potentially to anyone,=20
> including any=20
> >> attackers.  The RRQ has an authenticator (which may be,=20
> for instance,=20
> >> HMAC-based).  Given the full RRQ packet, a brute force=20
> attack on the=20
> >> HMAC key can be launched; this is an off-line attack=20
> because all you=20
> >> need is the RRQ and you can begin churning away on possible HMAC=20
> >> keys, the MN-HA authentication data will give you the=20
> correct answer=20
> >> for comparison.  This attack doesn't involve the i-HA in=20
> any way, all=20
> >> you need is the RRQ packet.
> >=20
> > RFC 3344 is susceptible to this attack.
>=20
> Naturally, and this is why this wasn't mentioned in security=20
> considerations earlier.  I was personally assuming this would=20
> be clear from context.
>=20
> However, the point was raised that although the dual MIP=20
> solution in general protects leaks of traffic intended for=20
> the internal network, the i-HA RRQ will leak and reveal some=20
> information anyway.  It might be worth mentioning.  At least=20
> if we mention that the i-HA address can be seen from the i-HA=20
> RRQ, we should IMO also mention that the i-HA RRQ is wide=20
> open for all other kinds of abuse as well.
>=20
> BR,
>=20
> -Sami
>=20

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Fri Dec 15 11:05:08 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GvFYU-0002SE-89; Fri, 15 Dec 2006 11:05:02 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GvFYS-0002QC-TY
	for mip4@ietf.org; Fri, 15 Dec 2006 11:05:00 -0500
Received: from mail2.azairenet.com ([66.92.223.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GvFWl-00004w-L7
	for mip4@ietf.org; Fri, 15 Dec 2006 11:03:17 -0500
Received: from [127.0.0.1] ([66.92.223.6]) by mail2.azairenet.com over TLS
	secured channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 15 Dec 2006 08:03:12 -0800
Message-ID: <4582C73F.1090309@azairenet.com>
Date: Fri, 15 Dec 2006 08:03:11 -0800
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: "Narayanan, Vidya" <vidyan@qualcomm.com>
Subject: Re: [Mip4] WGLC Comments: draft-ietf-mip4-mobike-connectivity-01.txt
References: <C24CB51D5AA800449982D9BCB903251335EA41@NAEX13.na.qualcomm.com>
In-Reply-To: <C24CB51D5AA800449982D9BCB903251335EA41@NAEX13.na.qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 15 Dec 2006 16:03:12.0738 (UTC)
	FILETIME=[85D23C20:01C72062]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Cc: Sami Vaarala <sami.vaarala@iki.fi>,
	Mobile IPv4 Mailing List <mip4@ietf.org>,
	Henrik Levkowetz <henrik@levkowetz.com>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Sami, Vidya,

I am not convinced that there is anything special
here. Any protocol that uses a hash function to
generate a MAC is susceptible to brute force
attacks.

I agree that the IP addresses and possibly the
NAI is revealed.

Vijay

Narayanan, Vidya wrote:
> I agree with Sami here. In RFC3344, there is no notion of "enterprise"
> level of security. A typical enterprise network will be sensitive to
> revealing of internal IP addresses, user names and any crypto data. The
> text that Sami sent looks good to me. 
> 
> Vidya 
> 
>> -----Original Message-----
>> From: Sami Vaarala [mailto:sami.vaarala@iki.fi] 
>> Sent: Thursday, December 14, 2006 11:39 PM
>> To: Vijay Devarapalli
>> Cc: Narayanan, Vidya; Mobile IPv4 Mailing List; Henrik Levkowetz
>> Subject: Re: [Mip4] WGLC Comments: 
>> draft-ietf-mip4-mobike-connectivity-01.txt
>>
>> Vijay Devarapalli wrote:
>>>> When the MN visits an untrusted network and attempts to 
>> send an RRQ 
>>>> to the i-HA, the RRQ is visible potentially to anyone, 
>> including any 
>>>> attackers.  The RRQ has an authenticator (which may be, 
>> for instance, 
>>>> HMAC-based).  Given the full RRQ packet, a brute force 
>> attack on the 
>>>> HMAC key can be launched; this is an off-line attack 
>> because all you 
>>>> need is the RRQ and you can begin churning away on possible HMAC 
>>>> keys, the MN-HA authentication data will give you the 
>> correct answer 
>>>> for comparison.  This attack doesn't involve the i-HA in 
>> any way, all 
>>>> you need is the RRQ packet.
>>> RFC 3344 is susceptible to this attack.
>> Naturally, and this is why this wasn't mentioned in security 
>> considerations earlier.  I was personally assuming this would 
>> be clear from context.
>>
>> However, the point was raised that although the dual MIP 
>> solution in general protects leaks of traffic intended for 
>> the internal network, the i-HA RRQ will leak and reveal some 
>> information anyway.  It might be worth mentioning.  At least 
>> if we mention that the i-HA address can be seen from the i-HA 
>> RRQ, we should IMO also mention that the i-HA RRQ is wide 
>> open for all other kinds of abuse as well.
>>
>> BR,
>>
>> -Sami
>>


-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Fri Dec 15 11:44:06 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GvGAE-0002eZ-61; Fri, 15 Dec 2006 11:44:02 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GvGAC-0002cc-LG
	for mip4@ietf.org; Fri, 15 Dec 2006 11:44:00 -0500
Received: from ithilien.qualcomm.com ([129.46.51.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GvGAB-0006X4-7v
	for mip4@ietf.org; Fri, 15 Dec 2006 11:44:00 -0500
Received: from neophyte.qualcomm.com (neophyte.qualcomm.com [129.46.61.149])
	by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	kBFGhrkb013140
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Fri, 15 Dec 2006 08:43:54 -0800
Received: from SANEXCAS02.na.qualcomm.com (sanexcas02.qualcomm.com
	[172.30.36.176])
	by neophyte.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	kBFGhqj4027896; Fri, 15 Dec 2006 08:43:52 -0800
Received: from NAEX13.na.qualcomm.com ([129.46.51.248]) by
	SANEXCAS02.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 15 Dec 2006 08:43:52 -0800
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
Subject: RE: [Mip4] WGLC Comments: draft-ietf-mip4-mobike-connectivity-01.txt
Date: Fri, 15 Dec 2006 08:43:40 -0800
Message-ID: <C24CB51D5AA800449982D9BCB903251335EA5A@NAEX13.na.qualcomm.com>
In-Reply-To: <4582C73F.1090309@azairenet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip4] WGLC Comments: draft-ietf-mip4-mobike-connectivity-01.txt
Thread-Index: AccgYo494MNkcDKmSBaJpgkiH1ZlxAABUVQA
From: "Narayanan, Vidya" <vidyan@qualcomm.com>
To: "Vijay Devarapalli" <vijay.devarapalli@AzaireNet.com>
X-OriginalArrivalTime: 15 Dec 2006 16:43:52.0295 (UTC)
	FILETIME=[33E91770:01C72068]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Cc: Sami Vaarala <sami.vaarala@iki.fi>,
	Mobile IPv4 Mailing List <mip4@ietf.org>,
	Henrik Levkowetz <henrik@levkowetz.com>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

=20

> -----Original Message-----
> From: Vijay Devarapalli [mailto:vijay.devarapalli@AzaireNet.com]=20
> Sent: Friday, December 15, 2006 8:03 AM
> To: Narayanan, Vidya
> Cc: Sami Vaarala; Mobile IPv4 Mailing List; Henrik Levkowetz
> Subject: Re: [Mip4] WGLC Comments:=20
> draft-ietf-mip4-mobike-connectivity-01.txt
>=20
> Sami, Vidya,
>=20
> I am not convinced that there is anything special here. Any=20
> protocol that uses a hash function to generate a MAC is=20
> susceptible to brute force attacks.
>=20

Well, it is the same thing as the IP address and NAI - if the
registrations were only limited to be inside the trusted network, this
would not have been available to an attacker in the untrusted network.=20

I don't feel strongly about having this text though. I see Sami's point
and agree with that, but, if you don't include the text on brute force
attacks, that's fine with me.=20

Vidya

> I agree that the IP addresses and possibly the NAI is revealed.
>=20
> Vijay
>=20
> Narayanan, Vidya wrote:
> > I agree with Sami here. In RFC3344, there is no notion of=20
> "enterprise"
> > level of security. A typical enterprise network will be=20
> sensitive to=20
> > revealing of internal IP addresses, user names and any crypto data.=20
> > The text that Sami sent looks good to me.
> >=20
> > Vidya
> >=20
> >> -----Original Message-----
> >> From: Sami Vaarala [mailto:sami.vaarala@iki.fi]
> >> Sent: Thursday, December 14, 2006 11:39 PM
> >> To: Vijay Devarapalli
> >> Cc: Narayanan, Vidya; Mobile IPv4 Mailing List; Henrik Levkowetz
> >> Subject: Re: [Mip4] WGLC Comments:=20
> >> draft-ietf-mip4-mobike-connectivity-01.txt
> >>
> >> Vijay Devarapalli wrote:
> >>>> When the MN visits an untrusted network and attempts to
> >> send an RRQ
> >>>> to the i-HA, the RRQ is visible potentially to anyone,
> >> including any
> >>>> attackers.  The RRQ has an authenticator (which may be,
> >> for instance,
> >>>> HMAC-based).  Given the full RRQ packet, a brute force
> >> attack on the
> >>>> HMAC key can be launched; this is an off-line attack
> >> because all you
> >>>> need is the RRQ and you can begin churning away on possible HMAC=20
> >>>> keys, the MN-HA authentication data will give you the
> >> correct answer
> >>>> for comparison.  This attack doesn't involve the i-HA in
> >> any way, all
> >>>> you need is the RRQ packet.
> >>> RFC 3344 is susceptible to this attack.
> >> Naturally, and this is why this wasn't mentioned in security=20
> >> considerations earlier.  I was personally assuming this would be=20
> >> clear from context.
> >>
> >> However, the point was raised that although the dual MIP=20
> solution in=20
> >> general protects leaks of traffic intended for the=20
> internal network,=20
> >> the i-HA RRQ will leak and reveal some information anyway.=20
>  It might=20
> >> be worth mentioning.  At least if we mention that the i-HA address=20
> >> can be seen from the i-HA RRQ, we should IMO also mention that the=20
> >> i-HA RRQ is wide open for all other kinds of abuse as well.
> >>
> >> BR,
> >>
> >> -Sami
> >>
>=20
>=20

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Fri Dec 15 21:41:35 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GvPUT-000514-OL; Fri, 15 Dec 2006 21:41:33 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GvPUR-00050v-5K
	for mip4@ietf.org; Fri, 15 Dec 2006 21:41:31 -0500
Received: from ns.academica.fi ([82.133.251.2])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GvPUP-0007b8-Ib
	for mip4@ietf.org; Fri, 15 Dec 2006 21:41:30 -0500
Received: from [82.133.140.68] (ip82-133-140-68.customer.academica.fi
	[82.133.140.68])
	by ns.academica.fi (Postfix) with ESMTP id E926A199AF5;
	Sat, 16 Dec 2006 03:39:08 +0200 (EET)
Message-ID: <45835C6C.1090404@iki.fi>
Date: Sat, 16 Dec 2006 04:39:40 +0200
From: Sami Vaarala <sami.vaarala@iki.fi>
User-Agent: Icedove 1.5.0.8 (X11/20061128)
MIME-Version: 1.0
To: "Narayanan, Vidya" <vidyan@qualcomm.com>
Subject: Re: [Mip4] WGLC Comments: draft-ietf-mip4-mobike-connectivity-01.txt
References: <C24CB51D5AA800449982D9BCB903251335EA5A@NAEX13.na.qualcomm.com>
In-Reply-To: <C24CB51D5AA800449982D9BCB903251335EA5A@NAEX13.na.qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Cc: Mobile IPv4 Mailing List <mip4@ietf.org>,
	Vijay Devarapalli <vijay.devarapalli@AzaireNet.com>,
	Henrik Levkowetz <henrik@levkowetz.com>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Narayanan, Vidya wrote:
>  
> 
>> -----Original Message-----
>> From: Vijay Devarapalli [mailto:vijay.devarapalli@AzaireNet.com] 
>> Sent: Friday, December 15, 2006 8:03 AM
>> To: Narayanan, Vidya
>> Cc: Sami Vaarala; Mobile IPv4 Mailing List; Henrik Levkowetz
>> Subject: Re: [Mip4] WGLC Comments: 
>> draft-ietf-mip4-mobike-connectivity-01.txt
>>
>> Sami, Vidya,
>>
>> I am not convinced that there is anything special here. Any 
>> protocol that uses a hash function to generate a MAC is 
>> susceptible to brute force attacks.
>>
> 
> Well, it is the same thing as the IP address and NAI - if the
> registrations were only limited to be inside the trusted network, this
> would not have been available to an attacker in the untrusted network. 
> 
> I don't feel strongly about having this text though. I see Sami's point
> and agree with that, but, if you don't include the text on brute force
> attacks, that's fine with me. 

Right, I also think this attack is rather obvious.  I just think that
if we mention that the i-HA address can be easily seen from the RRQ,
many other attacks are also possible: they are all part of the same
"problem".  So I'd prefer that we either (a) don't mention this at all
(because it's fairly obvious), or (b) mention that there are several
vulnerabilities related to the attacker seeing the inner MIP RRQ,
including address/NAI leakage and brute force attacks.

Either way (with or without a security considerations issue) works
for me.  I don't think the clarification is necessary, but it doesn't
do any harm either.

BR,

-Sami

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Sun Dec 17 06:06:50 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gvtqe-000698-PA; Sun, 17 Dec 2006 06:06:28 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gvtqb-000692-TQ
	for mip4@ietf.org; Sun, 17 Dec 2006 06:06:25 -0500
Received: from michael.checkpoint.com ([194.29.32.68])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gvtqa-0005tp-DG
	for mip4@ietf.org; Sun, 17 Dec 2006 06:06:25 -0500
Received: from ysheffer.ad.checkpoint.com (localhost [127.0.0.1])
	by michael.checkpoint.com (8.12.10+Sun/8.12.10) with ESMTP id
	kBHB6H67001776; Sun, 17 Dec 2006 13:06:17 +0200 (IST)
Message-Id: <200612171106.kBHB6H67001776@michael.checkpoint.com>
Date: Sun, 17 Dec 2006 13:06:17 +0200
From: Yaron Sheffer <yaronf@checkpoint.com>
Subject: RE: [Mip4] Some comments
	on	WGLC:	draft-ietf-mip4-mobike-connectivity-01.txt
To: Vijay Devarapalli <vijay.devarapalli@azairenet.com>,
	Hans Sjostrand <hans@ipunplugged.com>
In-reply-to: <4581D0D8.2020407@azairenet.com>
MIME-Version: 1.0
X-Mailer: Sun Outlook Connector 7.1.228.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: QUOTED-PRINTABLE
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Cc: mip4@ietf.org
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

> -----Original Message-----
> From: Vijay Devarapalli [mailto:vijay.devarapalli@azairenet.com]
> Sent: Friday, December 15, 2006 0:32
> To: Hans Sjostrand
> Cc: mip4@ietf.org
> Subject: Re: [Mip4] Some comments on WGLC: draft-ietf-mip4-mobike-
> connectivity-01.txt
>=20
> Hans Sjostrand wrote:
> > Hi,
> >
[...]
>=20
> > 4. Movement detection and security.
> >
> > In section 34. there is a sentence stating "Whenever the mobile node
> > detects that it has moved to a new IP subnet [9] and its IP address
> > changes". Again a lack of keywords.
>=20
> This sentence just describes what the MN must do.
> What would you like to see here?
>=20
> > But I think this sentence is a
> > potential security problem.
>=20
> Can you elaborate a little bit more on the security
> problem?
>=20
> > It's not about subnets. It should be crystal
> > clear that ANY detection of network movement whatsoever MUST result in =
a
> > state that a security boundary may have been crossed and it sends a
> > Registration Request to the i-HA.
>=20
> Even when there is no subnet change? Why?
>=20
Because you can get an address on 192.168.0.0/16 from the enterprise DHCP s=
erver on the LAN, and immediately later another address on this subnet, or =
even the same one, from the untrusted WLAN (which uses a different NAT). Th=
is can be detected through layer-2 indications, but there are weirder cases=
 when even that won't work.

Regards,
=09Yaron=20


-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Sun Dec 17 14:31:15 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gw1j1-0004nK-Ms; Sun, 17 Dec 2006 14:31:07 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gw1j0-0004nB-C8
	for mip4@ietf.org; Sun, 17 Dec 2006 14:31:06 -0500
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gw1iy-00044E-T9
	for mip4@ietf.org; Sun, 17 Dec 2006 14:31:06 -0500
Received: from neophyte.qualcomm.com (neophyte.qualcomm.com [129.46.61.149])
	by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	kBHJUtYP028314
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Sun, 17 Dec 2006 11:30:56 -0800
Received: from sanexcas01.na.qualcomm.com (sanexcas01.qualcomm.com
	[172.30.36.175])
	by neophyte.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	kBHJUsQc021467; Sun, 17 Dec 2006 11:30:55 -0800
Received: from NAEX13.na.qualcomm.com ([129.46.51.248]) by
	sanexcas01.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sun, 17 Dec 2006 11:30:54 -0800
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
Subject: RE: [Mip4] Some comments
	onWGLC:	draft-ietf-mip4-mobike-connectivity-01.txt
Date: Sun, 17 Dec 2006 11:30:53 -0800
Message-ID: <C24CB51D5AA800449982D9BCB90325133C901D@NAEX13.na.qualcomm.com>
In-Reply-To: <4581D0D8.2020407@azairenet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip4] Some comments
	onWGLC:	draft-ietf-mip4-mobike-connectivity-01.txt
Thread-Index: Accf0PKGds1lsLkrSHSb0cNRcAkm5gCP9Slg
From: "Narayanan, Vidya" <vidyan@qualcomm.com>
To: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>,
	"Hans Sjostrand" <hans@ipunplugged.com>
X-OriginalArrivalTime: 17 Dec 2006 19:30:54.0745 (UTC)
	FILETIME=[DE951890:01C72211]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
Cc: mip4@ietf.org
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

>=20
> > 5. Internet FA's
> >=20
> > In this draft it seams that FA's on internet is silently ignored.=20
> > Atleast those are not mentioned anyware that I find. I=20
> assume this is=20
> > because the solution doesn't work with internet FA's. I=20
> think this is=20
> > a limitation that might be worth mentioning.
>=20
> If the mobile node does not have an external Home Agent that=20
> it can reach when it is attached to an untrusted network, it=20
> cannot obviously use the FA on the untrusted network. If=20
> there is an external home agent that it can use, then=20
> draft-ietf-mip4-vpn-problem-solution would apply.
>=20

This doesn't seem to make sense. This draft needs to talk about the
behavior of an MN that supports this solution. In this particular
solution, external FAs cannot be used.=20

> > Besides that, a good assumption is often a good idea.It's a=20
> bit hard=20
> > to know of a FA is inside or outside. Thats why we wrote=20
> RFC3846. We=20
> > have been using a RFC3846 agent NAI in  FA's to make an=20
> educated guess=20
> > if it's a intranet FA or a internet FA. It's maybe therefore a good=20
> > idea to reference RFC3846 "Mobile IPv4 Extension for=20
> Carrying Network=20
> > Access Identifiers" and describe how agent NAIs could be used.
> >=20
> > In our solution, if the suffix part of the FA NAI is known as an=20
> > intranet identifier to the MN, then teh MN go against the i-HA.
>=20
> The Agent Advertisement is not protected. So I am not sure we=20
> should be using the NAI extension from RFC 3846, unless rogue=20
> foreign agents on a link are not considered possible.
>=20
> Another option is for the MN to always acquire a CoA from the=20
> access network and send a registration request to the i-HA.=20
> Once the MN detects that it is attached to a trusted network,=20
> it can switch the FA CoA mode if an FA is available on the=20
> trusted network. Will this work for you?

This seems to be the only thing that will work for this draft. Here is
what I had said in one of my earlier emails to Henrik on this topic:=20

"If the MN is moving from an untrusted network, it needs to first
acquire an IP address, try reaching the HA with it; if the HA is not
reachable, use that address as the VPN tunnel outer address; if it is
reachable, either operate in CCoA mode or then use an FA and re-register
with the FA. OTOH, if the MN is moving from a trusted network, it may
use an FA first; determine that the HA is unreachable, subsequently
acquire an IP address and set up a VPN. "

I think the draft can use some text on this.=20

Vidya

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Mon Dec 18 12:41:29 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GwMUQ-00028E-Vy; Mon, 18 Dec 2006 12:41:26 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GwMUP-000282-7K
	for mip4@ietf.org; Mon, 18 Dec 2006 12:41:25 -0500
Received: from 213.80.52.78.dataphone.se ([213.80.52.78]
	helo=mailgw.local.ipunplugged.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GwMUN-0008Ql-KD
	for mip4@ietf.org; Mon, 18 Dec 2006 12:41:25 -0500
Received: from [127.0.0.1] (echo.local.ipunplugged.com [192.168.4.74])
	by mailgw.local.ipunplugged.com (8.12.8/8.12.3) with ESMTP id
	kBIHf4pI004421; Mon, 18 Dec 2006 18:41:12 +0100
Message-ID: <4586D2AE.8030809@ipunplugged.com>
Date: Mon, 18 Dec 2006 18:41:02 +0100
From: Hans Sjostrand <hans@ipunplugged.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
Subject: Re: [Mip4] Some comments on WGLC:
	draft-ietf-mip4-mobike-connectivity-01.txt
References: <BE4B07D4197BF34EB3B753DD34EBCD130125E6C2@de01exm67.ds.mot.com>
	<458159FE.6080204@ipunplugged.com> <4581D0D8.2020407@azairenet.com>
In-Reply-To: <4581D0D8.2020407@azairenet.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: clamd / ClamAV version 0.75.1, clamav-milter version 0.75c
	on mailgw.local.ipunplugged.com
X-Virus-Status: Clean
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 20f22c03b5c66958bff5ef54fcda6e48
Cc: mip4@ietf.org
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Hi Vijay,

some comments embedded.

Vijay Devarapalli wrote:
> Hans Sjostrand wrote:
>> Hi,
>>
>> Sorry for being late. There are a few things in the draft that I 
>> would like to have clarified before agreeing to sending it to IESG.
>>
>> 1. Access mode home seams to be forgotten.
>>
>> In figure 1 there is a access mode called {home}, but I can't find it 
>> described anywhere in the document. Is the access mode forgotten or 
>> omitted on purpose? 
>
> The {home} in the figure refers to the fact that the
> link on which the i-HA is present is the home link.
> It is not an access mode. There are only four access
> modes even in draft-ietf-mip4-vpn-problem-solution.

I maintain that a mobile ip working document should describe the home 
mode. It's central and important. There are also other places where the 
FA and collocated away cases are described. But not the home case.

>
>> 2. Whats a few milliseconds worth?
>>
>> In section 3.2 there is a line stating "The mobile node attempts 
>> Foreign Agent discovery and CoA address acquisition through DHCP 
>> simultaneously in order to avoid the delay in discovering a foreign 
>> agent when there is no foreign agent available.". Apart from not 
>> complying with the RFC 2119 keywords rules, I read it as a statement. 
>> The sending of a solicitation and waiting for an advertisements is 
>> normally a case of split seconds. Why start a DHCP cycle which only 
>> saves a couple of milliseconds an then rely on DHCP servers which 
>> normally introduces in order of magnitudes longer delays?
>
> Discovering a FA might take more than a few
> milliseconds, especially if the FA does not send
> out agent advertisements frequently and the mobile
> node has to solicit for agents on the link. If the
> mobile node is soliciting by sending agent
> solicitations it can take upto 3 seconds before it
> can conclude that there is no foreign agent on the
> link.

Firstly I don't think that a complimentary document should start 
defining MN behavior. That is regardless of handover performance. We 
should simple leave that to RFC3344. If you have concerns with handover 
performance and FA discovery, please take that in the RFC3344bis 
discussion. Do not write some new MN behavior in a complementary document.

A FA might for some reason not send out broadcast or multicast 
advertisements, thats true. But an FA SHOULD (section 2.3 in rfc3344) 
respond to Agent Solicitations. And a MN that doesn't solicitate on a 
new link seams a but passive in my mind, but thats implementation. In my 
experience a MN normally pics up a FA in almost notime.

>>
>> In section 34. there is a sentence stating "Whenever the mobile node 
>> detects that it has moved to a new IP subnet [9] and its IP address 
>> changes". Again a lack of keywords. 
> 4. Movement detection and security.
>
> This sentence just describes what the MN must do.
> What would you like to see here?

Again, I don't think that we should define up new behaviors. RFC3344 
states.
-    A mobile node SHOULD initiate a registration whenever it detects a 
change in its network connectivity.

Thats pretty good for me. It's then up to each implementation to make 
it's own determination what "network connectivity" means.
>
>> But I think this sentence is a potential security problem. 
>
> Can you elaborate a little bit more on the security
> problem?

RFC4436 openly admits "In general, adjustment of the security 
configuration based on DNAv4 is NOT RECOMMENDED.". Therefore, assuming 
that they'll do the trick is a bit optimistic. I think there are quite a 
few security considerations to be elaborated here.

>
>> It's not about subnets. It should be crystal clear that ANY detection 
>> of network movement whatsoever MUST result in a state that a security 
>> boundary may have been crossed and it sends a Registration Request to 
>> the i-HA.
>
> Even when there is no subnet change? Why?

Assume that you are on a trusted network. And the computer associates 
with a new BSSID (i.e. a different AP than before). What would you have 
wanted your VPN vendor to do.
a) Accept the new nice AP that so kindly did let you in and continue to 
send clear text traffic.
b) Stop sending traffic until a registration procedure against the i-HA 
has made it clear that no security boundary has been passed.

My choice is clear. And I think the RFC4436 guys agree since they point 
out that arp and dhcp is NOT a security feature. Therefore, subnets are 
not the for making sure security boundaries are crossed or not.

>
>> 5. Internet FA's
>>
>> In this draft it seams that FA's on internet is silently ignored. 
>> Atleast those are not mentioned anyware that I find. I assume this is 
>> because the solution doesn't work with internet FA's. I think this is 
>> a limitation that might be worth mentioning.
>
> If the mobile node does not have an external Home
> Agent that it can reach when it is attached to an
> untrusted network, it cannot obviously use the FA
> on the untrusted network. If there is an external
> home agent that it can use, then
> draft-ietf-mip4-vpn-problem-solution would apply.

There are no external home agent in this context. Atleast not in the 
terminology the solutions part of the document that I read through. It 
was just a suggestion to be fair to readers of this document that an 
internet FA is unusable and if one is detected it should discarded as a 
possible agent. Not a big thing.

>
>> Besides that, a good assumption is often a good idea.It's a bit hard 
>> to know of a FA is inside or outside. Thats why we wrote RFC3846. We 
>> have been using a RFC3846 agent NAI in  FA's to make an educated 
>> guess if it's a intranet FA or a internet FA. It's maybe therefore a 
>> good idea to reference RFC3846 "Mobile IPv4 Extension for Carrying 
>> Network Access Identifiers" and describe how agent NAIs could be used.
>>
>> In our solution, if the suffix part of the FA NAI is known as an 
>> intranet identifier to the MN, then teh MN go against the i-HA.
>
> The Agent Advertisement is not protected. So I am
> not sure we should be using the NAI extension from
> RFC 3846, unless rogue foreign agents on a link are
> not considered possible.
>
> Another option is for the MN to always acquire a
> CoA from the access network and send a registration
> request to the i-HA. Once the MN detects that it is
> attached to a trusted network, it can switch the FA
> CoA mode if an FA is available on the trusted
> network. Will this work for you?
>
> Vijay
>
I know that advertisements isn't protected, thats why I sued works like 
"assumption" and "educated guess". This was probably more 
implementation. A smart implementation could make assumptions and 
educated guesses but it's ok for me to leave it at that.

Please, no new requirements for MN behavior to acquire a CoA or not.

Regards

/// Hasse



-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Mon Dec 18 13:00:35 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GwMmt-0002Ix-P1; Mon, 18 Dec 2006 13:00:31 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GwMms-0002Is-U4
	for mip4@ietf.org; Mon, 18 Dec 2006 13:00:30 -0500
Received: from 213.80.52.78.dataphone.se ([213.80.52.78]
	helo=mailgw.local.ipunplugged.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GwMmr-0002f0-0V
	for mip4@ietf.org; Mon, 18 Dec 2006 13:00:30 -0500
Received: from [127.0.0.1] (echo.local.ipunplugged.com [192.168.4.74])
	by mailgw.local.ipunplugged.com (8.12.8/8.12.3) with ESMTP id
	kBII0GpI004496; Mon, 18 Dec 2006 19:00:22 +0100
Message-ID: <4586D72F.2000103@ipunplugged.com>
Date: Mon, 18 Dec 2006 19:00:15 +0100
From: Hans Sjostrand <hans@ipunplugged.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: "Narayanan, Vidya" <vidyan@qualcomm.com>
Subject: Re: [Mip4] Some comments on WGLC:
	draft-ietf-mip4-mobike-connectivity-01.txt
References: <C24CB51D5AA800449982D9BCB90325133C901D@NAEX13.na.qualcomm.com>
In-Reply-To: <C24CB51D5AA800449982D9BCB90325133C901D@NAEX13.na.qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: clamd / ClamAV version 0.75.1, clamav-milter version 0.75c
	on mailgw.local.ipunplugged.com
X-Virus-Status: Clean
X-Spam-Score: 0.1 (/)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
Cc: mip4@ietf.org, Vijay Devarapalli <vijay.devarapalli@azairenet.com>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Comments in the end.

>>> Besides that, a good assumption is often a good idea.It's a 
>>>       
>> bit hard 
>>     
>>> to know of a FA is inside or outside. Thats why we wrote 
>>>       
>> RFC3846. We 
>>     
>>> have been using a RFC3846 agent NAI in  FA's to make an 
>>>       
>> educated guess 
>>     
>>> if it's a intranet FA or a internet FA. It's maybe therefore a good 
>>> idea to reference RFC3846 "Mobile IPv4 Extension for 
>>>       
>> Carrying Network 
>>     
>>> Access Identifiers" and describe how agent NAIs could be used.
>>>
>>> In our solution, if the suffix part of the FA NAI is known as an 
>>> intranet identifier to the MN, then teh MN go against the i-HA.
>>>       
>> The Agent Advertisement is not protected. So I am not sure we 
>> should be using the NAI extension from RFC 3846, unless rogue 
>> foreign agents on a link are not considered possible.
>>
>> Another option is for the MN to always acquire a CoA from the 
>> access network and send a registration request to the i-HA. 
>> Once the MN detects that it is attached to a trusted network, 
>> it can switch the FA CoA mode if an FA is available on the 
>> trusted network. Will this work for you?
>>     
>
> This seems to be the only thing that will work for this draft. Here is
> what I had said in one of my earlier emails to Henrik on this topic: 
>
> "If the MN is moving from an untrusted network, it needs to first
> acquire an IP address, try reaching the HA with it; if the HA is not
> reachable, use that address as the VPN tunnel outer address; if it is
> reachable, either operate in CCoA mode or then use an FA and re-register
> with the FA. OTOH, if the MN is moving from a trusted network, it may
> use an FA first; determine that the HA is unreachable, subsequently
> acquire an IP address and set up a VPN. "
>
> I think the draft can use some text on this. 
>
> Vidya

Formally you are right Vidya. Thats why I thought it was a good idea to 
introduce an "educated guess".

If you, for example via RFC3846 advertisements, recognize that you most 
probably are inside you could start by registering with the i-HA. And 
vice versa, if you make an educated guess that your outside, then you 
could start of by doing a VPN tunnel.

This is however completely informational and it's only about handover 
performance. It's only the IKE mobility exchange and the MIP 
registration exchange that is valid indications of actual location and 
security policy to apply.

We should not mandate behavior here, the specification should be open 
for implementation.

Best regards
/// Hasse





-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Mon Dec 18 16:19:51 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GwPtn-0006Ye-6k; Mon, 18 Dec 2006 16:19:51 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GwPtm-0006W5-GM
	for mip4@ietf.org; Mon, 18 Dec 2006 16:19:50 -0500
Received: from ithilien.qualcomm.com ([129.46.51.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GwPtj-0002bd-VD
	for mip4@ietf.org; Mon, 18 Dec 2006 16:19:50 -0500
Received: from hamtaro.qualcomm.com (hamtaro.qualcomm.com [129.46.61.157])
	by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	kBILJfC7030294
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Mon, 18 Dec 2006 13:19:42 -0800
Received: from sanexcas01.na.qualcomm.com (sanexcas01.qualcomm.com
	[172.30.36.175])
	by hamtaro.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	kBILJe2f016663; Mon, 18 Dec 2006 13:19:41 -0800 (PST)
Received: from NAEX13.na.qualcomm.com ([129.46.51.248]) by
	sanexcas01.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 18 Dec 2006 13:19:40 -0800
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
Subject: RE: [Mip4] Some comments on
	WGLC:draft-ietf-mip4-mobike-connectivity-01.txt
Date: Mon, 18 Dec 2006 13:19:39 -0800
Message-ID: <C24CB51D5AA800449982D9BCB90325133C90D0@NAEX13.na.qualcomm.com>
In-Reply-To: <4586D72F.2000103@ipunplugged.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip4] Some comments on
	WGLC:draft-ietf-mip4-mobike-connectivity-01.txt
Thread-Index: Acciz+J4v60CfssNRdaGbKHJTrR8vAAGgPSw
From: "Narayanan, Vidya" <vidyan@qualcomm.com>
To: "Hans Sjostrand" <hans@ipunplugged.com>
X-OriginalArrivalTime: 18 Dec 2006 21:19:40.0553 (UTC)
	FILETIME=[3AAE1F90:01C722EA]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 287c806b254c6353fcb09ee0e53bbc5e
Cc: mip4@ietf.org, Vijay Devarapalli <vijay.devarapalli@azairenet.com>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

=20

> -----Original Message-----
> From: Hans Sjostrand [mailto:hans@ipunplugged.com]=20
> Sent: Monday, December 18, 2006 10:00 AM
> To: Narayanan, Vidya
> Cc: mip4@ietf.org; Vijay Devarapalli
> Subject: Re: [Mip4] Some comments on=20
> WGLC:draft-ietf-mip4-mobike-connectivity-01.txt
>=20
> Comments in the end.
>=20
> >>> Besides that, a good assumption is often a good idea.It's a
> >>>      =20
> >> bit hard
> >>    =20
> >>> to know of a FA is inside or outside. Thats why we wrote
> >>>      =20
> >> RFC3846. We
> >>    =20
> >>> have been using a RFC3846 agent NAI in  FA's to make an
> >>>      =20
> >> educated guess
> >>    =20
> >>> if it's a intranet FA or a internet FA. It's maybe=20
> therefore a good=20
> >>> idea to reference RFC3846 "Mobile IPv4 Extension for
> >>>      =20
> >> Carrying Network
> >>    =20
> >>> Access Identifiers" and describe how agent NAIs could be used.
> >>>
> >>> In our solution, if the suffix part of the FA NAI is known as an=20
> >>> intranet identifier to the MN, then teh MN go against the i-HA.
> >>>      =20
> >> The Agent Advertisement is not protected. So I am not sure=20
> we should=20
> >> be using the NAI extension from RFC 3846, unless rogue=20
> foreign agents=20
> >> on a link are not considered possible.
> >>
> >> Another option is for the MN to always acquire a CoA from=20
> the access=20
> >> network and send a registration request to the i-HA.
> >> Once the MN detects that it is attached to a trusted=20
> network, it can=20
> >> switch the FA CoA mode if an FA is available on the=20
> trusted network.=20
> >> Will this work for you?
> >>    =20
> >
> > This seems to be the only thing that will work for this=20
> draft. Here is=20
> > what I had said in one of my earlier emails to Henrik on this topic:
> >
> > "If the MN is moving from an untrusted network, it needs to first=20
> > acquire an IP address, try reaching the HA with it; if the=20
> HA is not=20
> > reachable, use that address as the VPN tunnel outer=20
> address; if it is=20
> > reachable, either operate in CCoA mode or then use an FA and=20
> > re-register with the FA. OTOH, if the MN is moving from a trusted=20
> > network, it may use an FA first; determine that the HA is=20
> unreachable,=20
> > subsequently acquire an IP address and set up a VPN. "
> >
> > I think the draft can use some text on this.=20
> >
> > Vidya
>=20
> Formally you are right Vidya. Thats why I thought it was a=20
> good idea to introduce an "educated guess".
>=20
> If you, for example via RFC3846 advertisements, recognize=20
> that you most probably are inside you could start by=20
> registering with the i-HA. And vice versa, if you make an=20
> educated guess that your outside, then you could start of by=20
> doing a VPN tunnel.
>=20

The problem is that if there are any statements about using
RFC3846-style FAAs, the document also has to talk about security issues
with masquerading FAs. I'm not sure that is worth getting into. But, I'd
be fine with such text, as long as the security implications are
appropriately pointed out.=20

Regards,
Vidya

> This is however completely informational and it's only about=20
> handover performance. It's only the IKE mobility exchange and=20
> the MIP registration exchange that is valid indications of=20
> actual location and security policy to apply.
>=20
> We should not mandate behavior here, the specification should=20
> be open for implementation.
>=20
> Best regards
> /// Hasse
>=20
>=20
>=20
>=20
>=20
> --
> Mip4 mailing list: Mip4@ietf.org
>     Web interface: https://www1.ietf.org/mailman/listinfo/mip4
>      Charter page: http://www.ietf.org/html.charters/mip4-charter.html
> Supplemental site: http://www.mip4.org/
>=20

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Mon Dec 18 16:38:18 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GwQBe-0002e8-BO; Mon, 18 Dec 2006 16:38:18 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GwQBc-0002c9-Kv
	for mip4@ietf.org; Mon, 18 Dec 2006 16:38:16 -0500
Received: from 213.80.52.78.dataphone.se ([213.80.52.78]
	helo=mailgw.local.ipunplugged.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GwQBa-0006Qe-O2
	for mip4@ietf.org; Mon, 18 Dec 2006 16:38:16 -0500
Received: from [127.0.0.1] (c43.local.ipunplugged.com [192.168.4.242])
	by mailgw.local.ipunplugged.com (8.12.8/8.12.3) with ESMTP id
	kBILc6pI005649; Mon, 18 Dec 2006 22:38:08 +0100
Message-ID: <45870A3C.1090803@ipunplugged.com>
Date: Mon, 18 Dec 2006 22:38:04 +0100
From: Hans Sjostrand <hans@ipunplugged.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: "Narayanan, Vidya" <vidyan@qualcomm.com>
Subject: Re: [Mip4] Some comments on
	WGLC:draft-ietf-mip4-mobike-connectivity-01.txt
References: <C24CB51D5AA800449982D9BCB90325133C90D0@NAEX13.na.qualcomm.com>
In-Reply-To: <C24CB51D5AA800449982D9BCB90325133C90D0@NAEX13.na.qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: clamd / ClamAV version 0.75.1, clamav-milter version 0.75c
	on mailgw.local.ipunplugged.com
X-Virus-Status: Clean
X-Spam-Score: 0.1 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: mip4@ietf.org, Vijay Devarapalli <vijay.devarapalli@azairenet.com>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org


> The problem is that if there are any statements about using
> RFC3846-style FAAs, the document also has to talk about security issues
> with masquerading FAs. I'm not sure that is worth getting into. But, I'd
> be fine with such text, as long as the security implications are
> appropriately pointed out. 
>
> Regards,
> Vidya
>
>   

It wasn't a good idea at all to mix implementation and specification. 
I'll simply pull back anything I've proposed along with "Besides that, a 
good assumption is often a good idea....." It will just confuse people 
and possibly delay the draft.

What matters is that the draft doesn't prevent these things by 
overspecifying the order events of which things could be made. Then I'm 
happy.

Best regards
/// Hasse




-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Tue Dec 19 11:41:29 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gwi1m-0000ZS-Qa; Tue, 19 Dec 2006 11:41:18 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gwi1l-0000Xz-Nt
	for mip4@ietf.org; Tue, 19 Dec 2006 11:41:17 -0500
Received: from mail128.messagelabs.com ([216.82.250.131])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1Gwi1k-0003U4-Dq
	for mip4@ietf.org; Tue, 19 Dec 2006 11:41:17 -0500
X-VirusChecked: Checked
X-Env-Sender: pete.mccann@motorola.com
X-Msg-Ref: server-15.tower-128.messagelabs.com!1166544504!8670744!1
X-StarScan-Version: 5.5.10.7; banners=-,-,-
X-Originating-IP: [129.188.136.8]
Received: (qmail 25777 invoked from network); 19 Dec 2006 16:08:25 -0000
Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8)
	by server-15.tower-128.messagelabs.com with SMTP;
	19 Dec 2006 16:08:25 -0000
Received: from il06exr04.mot.com (il06exr04.mot.com [129.188.137.134])
	by motgate8.mot.com (8.12.11/Motorola) with ESMTP id kBJG8OcU018769
	for <mip4@ietf.org>; Tue, 19 Dec 2006 09:08:24 -0700 (MST)
Received: from de01exm67.ds.mot.com (de01exm67.am.mot.com [10.176.8.18])
	by il06exr04.mot.com (8.13.1/8.13.0) with ESMTP id kBJG8OSu029835
	for <mip4@ietf.org>; Tue, 19 Dec 2006 10:08:24 -0600 (CST)
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: Tue, 19 Dec 2006 11:08:23 -0500
Message-ID: <BE4B07D4197BF34EB3B753DD34EBCD130133C9B2@de01exm67.ds.mot.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Summing up: draft-ietf-mip4-mobike-connectivity-01.txt
Thread-Index: Accjh+ikWUL9hq+yRkKMiEpp5RlO3A==
From: "McCann Peter-A001034" <pete.mccann@motorola.com>
To: <mip4@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Subject: [Mip4] Summing up: draft-ietf-mip4-mobike-connectivity-01.txt
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Here is an attempted round-up of the issues that have been discussed:

1. Use of an FA

If the MN is on the trusted network, then an FA can be used.
There was a proposal from Vidya to put in the following text:

   "If the MN is moving from an untrusted network, it needs to first
acquire an IP address, try
    reaching the HA with it; if the HA is not reachable, use that
address as the VPN=20
    tunnel outer address; if it is reachable, either operate in CCoA
mode or then use an FA=20
    and re-register with the FA. OTOH, if the MN is moving from a
trusted network, it may=20
    use an FA first; determine that the HA is unreachable, subsequently
acquire an IP=20
    address and set up a VPN. "

However, there was a complaint that this might be over-specification.
Can the MN attempt to use an FA before it determines that it is on a
trusted network?  It seems to me that this is ok, the Registration Reply
will contain the MN-HA Authenticator if the FA can reach the HA,
otherwise
the MN will get no response or a response that fails the Authentication
check.
Personally I don't see the difference between the case of starting on an
untrusted
network vs. starting on the trusted network: the procedure could be the
same.

2. Bypass VPN for Registration Requests

There was discussion on whether it is feasible to bypass a VPN tunnel=20
for the Registration Request.  I think the discussion concluded that
it was possible, but perhaps some text needs to be added describing
the SAD.  Does anyone have some concrete text to propose?

3. Security considerations for exposing the Registration Request

This one seems pretty simple, there is a short list of concerns that
could be written into the draft.  Vijay, can you draft some text?

Anything else outstanding that I missed?

-Pete

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Tue Dec 19 13:32:47 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gwjld-0007XU-I2; Tue, 19 Dec 2006 13:32:45 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gwjlc-0007XP-FA
	for mip4@ietf.org; Tue, 19 Dec 2006 13:32:44 -0500
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gwjla-0008Hs-W3
	for mip4@ietf.org; Tue, 19 Dec 2006 13:32:44 -0500
Received: from totoro.qualcomm.com (totoro.qualcomm.com [129.46.61.158])
	by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	kBJIWfJ6007909
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Tue, 19 Dec 2006 10:32:42 -0800
Received: from sanexcas01.na.qualcomm.com (sanexcas01.qualcomm.com
	[172.30.36.175])
	by totoro.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id kBJIWeDa000506;
	Tue, 19 Dec 2006 10:32:41 -0800 (PST)
Received: from NAEX13.na.qualcomm.com ([129.46.51.248]) by
	sanexcas01.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 19 Dec 2006 10:32:40 -0800
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
Subject: RE: [Mip4] Summing up: draft-ietf-mip4-mobike-connectivity-01.txt
Date: Tue, 19 Dec 2006 10:32:38 -0800
Message-ID: <C24CB51D5AA800449982D9BCB90325133C9160@NAEX13.na.qualcomm.com>
In-Reply-To: <BE4B07D4197BF34EB3B753DD34EBCD130133C9B2@de01exm67.ds.mot.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip4] Summing up: draft-ietf-mip4-mobike-connectivity-01.txt
Thread-Index: Accjh+ikWUL9hq+yRkKMiEpp5RlO3AAE+qcg
From: "Narayanan, Vidya" <vidyan@qualcomm.com>
To: "McCann Peter-A001034" <pete.mccann@motorola.com>, <mip4@ietf.org>
X-OriginalArrivalTime: 19 Dec 2006 18:32:40.0909 (UTC)
	FILETIME=[10EB87D0:01C7239C]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Cc: 
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

I believe there are a couple of other things that Vijay already
suggested text for (Reverse tunneling; lack of mobility in VPN bypass
mode). One issue that I think is still open is support for multiple
interfaces (simultaneous bindings clarification).=20

Vidya

> -----Original Message-----
> From: McCann Peter-A001034 [mailto:pete.mccann@motorola.com]=20
> Sent: Tuesday, December 19, 2006 8:08 AM
> To: mip4@ietf.org
> Subject: [Mip4] Summing up: draft-ietf-mip4-mobike-connectivity-01.txt
>=20
> Here is an attempted round-up of the issues that have been discussed:
>=20
> 1. Use of an FA
>=20
> If the MN is on the trusted network, then an FA can be used.
> There was a proposal from Vidya to put in the following text:
>=20
>    "If the MN is moving from an untrusted network, it needs=20
> to first acquire an IP address, try
>     reaching the HA with it; if the HA is not reachable, use=20
> that address as the VPN=20
>     tunnel outer address; if it is reachable, either operate=20
> in CCoA mode or then use an FA=20
>     and re-register with the FA. OTOH, if the MN is moving=20
> from a trusted network, it may=20
>     use an FA first; determine that the HA is unreachable,=20
> subsequently acquire an IP=20
>     address and set up a VPN. "
>=20
> However, there was a complaint that this might be over-specification.
> Can the MN attempt to use an FA before it determines that it=20
> is on a trusted network?  It seems to me that this is ok, the=20
> Registration Reply will contain the MN-HA Authenticator if=20
> the FA can reach the HA, otherwise the MN will get no=20
> response or a response that fails the Authentication check.
> Personally I don't see the difference between the case of=20
> starting on an untrusted network vs. starting on the trusted=20
> network: the procedure could be the same.
>=20
> 2. Bypass VPN for Registration Requests
>=20
> There was discussion on whether it is feasible to bypass a=20
> VPN tunnel for the Registration Request.  I think the=20
> discussion concluded that it was possible, but perhaps some=20
> text needs to be added describing the SAD.  Does anyone have=20
> some concrete text to propose?
>=20
> 3. Security considerations for exposing the Registration Request
>=20
> This one seems pretty simple, there is a short list of=20
> concerns that could be written into the draft.  Vijay, can=20
> you draft some text?
>=20
> Anything else outstanding that I missed?
>=20
> -Pete
>=20
> --
> Mip4 mailing list: Mip4@ietf.org
>     Web interface: https://www1.ietf.org/mailman/listinfo/mip4
>      Charter page: http://www.ietf.org/html.charters/mip4-charter.html
> Supplemental site: http://www.mip4.org/
>=20

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Tue Dec 19 13:38:06 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gwjqo-0002UM-OG; Tue, 19 Dec 2006 13:38:06 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gwjqn-0002Qf-F3
	for mip4@ietf.org; Tue, 19 Dec 2006 13:38:05 -0500
Received: from p-mail2.rd.francetelecom.com ([195.101.245.16])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gwjql-00015Z-VK
	for mip4@ietf.org; Tue, 19 Dec 2006 13:38:05 -0500
Received: from ftrdmel3.rd.francetelecom.fr ([10.193.117.155]) by
	ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 19 Dec 2006 19:37:59 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 19 Dec 2006 19:38:19 +0100
Message-ID: <14FD20369E52DE478BD9612D63BE21B4070F83E7@ftrdmel3.rd.francetelecom.fr>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: I-D ACTION:draft-antoine-mip4-lowlatency-handoff-triggers-00.txt
Thread-Index: AccjnNqm0UGWCeTSQ7SCkkkpZuYI6w==
From: "ANTOINE Stephane RD-ILAB-LON" <stephane.antoine@orange-ftgroup.com>
To: <mip4@ietf.org>
X-OriginalArrivalTime: 19 Dec 2006 18:37:59.0989 (UTC)
	FILETIME=[CF1B4650:01C7239C]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: ff03b0075c3fc728d7d60a15b4ee1ad2
Subject: [Mip4] I-D
	ACTION:draft-antoine-mip4-lowlatency-handoff-triggers-00.txt
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1288277329=="
Errors-To: mip4-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1288277329==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7239C.CEDD94D1"

This is a multi-part message in MIME format.

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

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


Title                          : Using Higher Layer Triggers for Low
Latency Handoffs in MIPv4
Author(s)                  : S. Antoine
Filename                   :
draft-antoine-mip4-lowlatency-handoff-triggers-00.txt
Pages                        : 9
Date                          : 2006-12-15


   This document introduces the use of triggers coming from layers
   higher than the link layer to initiate the Low Latency Handoff in
   Mobile IPv4 (MIPv4) .  The Low Latency Handoff for MIPv4 assumes
   availability of Layer 2 (L2) triggers that contain Layer 3 (L3)
   information for the Mobile Node (MN) to handoff.  However, the low
   latency draft does not describe the method by which the L2 trigger is

   produced neither does it explicitly describe by what mechanism the L3
   information present in the L2 trigger is acquired.  The Low Latency
   Handoff for MIPv4 relies on availability of the L2 trigger.  However
   relying only on the link information to initiate a handoff does not
   generally gather enough information for the MN to handoff to the most
   suitable available access network.  Information from higher layers
   such as Higher Layer Triggers can be used to command a MN to quickly
   move from one access to another one.  Using Higher Layer Triggers to
   initiate the handoff enables the implementation of policy based
   handoff to garantee load balancing of the wireless networks and
   Quality of Services to the end users.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-antoine-mip4-lowlatency-handof
f-triggers-00.txt


------_=_NextPart_001_01C7239C.CEDD94D1
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.2900.3020" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV>A New Internet-Draft is available from the on-line Internet-Drafts=20
<BR>directories.<BR><BR><BR>	Title&nbsp;&nbsp;<SPAN=20
class=3D523322818-19122006>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;=20
</SPAN>: Using Higher Layer Triggers for Low Latency Handoffs in=20
MIPv4<BR>	Author(s)<SPAN=20
class=3D523322818-19122006>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;</SPAN>&nbsp;<SPAN=20
class=3D523322818-19122006>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;=20
</SPAN>:&nbsp;S. Antoine<BR>	Filename&nbsp;<SPAN=20
class=3D523322818-19122006>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
</SPAN>:=20
draft-antoine-mip4-lowlatency-handoff-triggers-00.txt<BR>	=
Pages&nbsp;&nbsp;<SPAN=20
class=3D523322818-19122006>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;=20
</SPAN>: 9<BR>	Date&nbsp;&nbsp;<SPAN=20
class=3D523322818-19122006>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;=20
</SPAN>: 2006-12-15<BR>	<BR><BR>&nbsp;&nbsp; This document introduces =
the use of=20
triggers coming from layers<BR>&nbsp;&nbsp; higher than the link layer =
to=20
initiate the Low Latency Handoff in<BR>&nbsp;&nbsp; Mobile IPv4 (MIPv4) =
.&nbsp;=20
The Low Latency Handoff for MIPv4 assumes<BR>&nbsp;&nbsp; availability =
of Layer=20
2 (L2) triggers that contain Layer 3 (L3)<BR>&nbsp;&nbsp; information =
for the=20
Mobile Node (MN) to handoff.&nbsp; However, the low<BR>&nbsp;&nbsp; =
latency=20
draft does not describe the method by which the L2 trigger=20
is<BR><BR>&nbsp;&nbsp; produced neither does it explicitly describe by =
what=20
mechanism the L3<BR>&nbsp;&nbsp; information present in the L2 trigger =
is=20
acquired.&nbsp; The Low Latency<BR>&nbsp;&nbsp; Handoff for MIPv4 relies =
on=20
availability of the L2 trigger.&nbsp; However<BR>&nbsp;&nbsp; relying =
only on=20
the link information to initiate a handoff does not<BR>&nbsp;&nbsp; =
generally=20
gather enough information for the MN to handoff to the =
most<BR>&nbsp;&nbsp;=20
suitable available access network.&nbsp; Information from higher=20
layers<BR>&nbsp;&nbsp; such as Higher Layer Triggers can be used to =
command a MN=20
to quickly<BR>&nbsp;&nbsp; move from one access to another one.&nbsp; =
Using=20
Higher Layer Triggers to<BR>&nbsp;&nbsp; initiate the handoff enables =
the=20
implementation of policy based<BR>&nbsp;&nbsp; handoff to garantee load=20
balancing of the wireless networks and<BR>&nbsp;&nbsp; Quality of =
Services to=20
the end users.<BR><BR><BR>A URL for this Internet-Draft is:<BR><A=20
href=3D"http://www.ietf.org/internet-drafts/draft-antoine-mip4-lowlatency=
-handoff-triggers-00.txt">http://www.ietf.org/internet-drafts/draft-antoi=
ne-mip4-lowlatency-handoff-triggers-00.txt</A><BR></DIV></BODY></HTML>

------_=_NextPart_001_01C7239C.CEDD94D1--


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

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

--===============1288277329==--




From mip4-bounces@ietf.org Tue Dec 19 14:43:52 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GwksS-0000qF-Bv; Tue, 19 Dec 2006 14:43:52 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GwksQ-0000q7-Kv
	for mip4@ietf.org; Tue, 19 Dec 2006 14:43:50 -0500
Received: from mail2.azairenet.com ([66.92.223.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GwksO-0000bX-Ab
	for mip4@ietf.org; Tue, 19 Dec 2006 14:43:50 -0500
Received: from [127.0.0.1] ([66.92.223.6]) by mail2.azairenet.com over TLS
	secured channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 19 Dec 2006 11:43:47 -0800
Message-ID: <458840EE.9070204@azairenet.com>
Date: Tue, 19 Dec 2006 11:43:42 -0800
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: Sami Vaarala <sami.vaarala@iki.fi>
Subject: Re: [Mip4] WGLC Comments: draft-ietf-mip4-mobike-connectivity-01.txt
References: <C24CB51D5AA800449982D9BCB903251335EA5A@NAEX13.na.qualcomm.com>
	<45835C6C.1090404@iki.fi>
In-Reply-To: <45835C6C.1090404@iki.fi>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 19 Dec 2006 19:43:47.0022 (UTC)
	FILETIME=[FFB8B6E0:01C723A5]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Cc: "Narayanan, Vidya" <vidyan@qualcomm.com>,
	Mobile IPv4 Mailing List <mip4@ietf.org>,
	Henrik Levkowetz <henrik@levkowetz.com>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Sami Vaarala wrote:
> Narayanan, Vidya wrote:
>>  
>>
>>> -----Original Message-----
>>> From: Vijay Devarapalli [mailto:vijay.devarapalli@AzaireNet.com] 
>>> Sent: Friday, December 15, 2006 8:03 AM
>>> To: Narayanan, Vidya
>>> Cc: Sami Vaarala; Mobile IPv4 Mailing List; Henrik Levkowetz
>>> Subject: Re: [Mip4] WGLC Comments: 
>>> draft-ietf-mip4-mobike-connectivity-01.txt
>>>
>>> Sami, Vidya,
>>>
>>> I am not convinced that there is anything special here. Any protocol 
>>> that uses a hash function to generate a MAC is susceptible to brute 
>>> force attacks.
>>>
>>
>> Well, it is the same thing as the IP address and NAI - if the
>> registrations were only limited to be inside the trusted network, this
>> would not have been available to an attacker in the untrusted network.
>> I don't feel strongly about having this text though. I see Sami's point
>> and agree with that, but, if you don't include the text on brute force
>> attacks, that's fine with me. 
> 
> Right, I also think this attack is rather obvious.  I just think that
> if we mention that the i-HA address can be easily seen from the RRQ,
> many other attacks are also possible: they are all part of the same
> "problem".  So I'd prefer that we either (a) don't mention this at all
> (because it's fairly obvious), or (b) mention that there are several
> vulnerabilities related to the attacker seeing the inner MIP RRQ,
> including address/NAI leakage and brute force attacks.
> 
> Either way (with or without a security considerations issue) works
> for me.  I don't think the clarification is necessary, but it doesn't
> do any harm either.

Here is some new text

    When the mobile node sends a registration request to the i-HA from an
    untrusted network that does not go through the IPsec tunnel, it may
    be leaking the i-HA's address, its own identity including the NAI and
    the home address, and the Authenticator value in the authentication
    extensions to the untrusted network.  This may be a concern in some
    deployments.

Vijay

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Tue Dec 19 14:59:08 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gwl7E-0002KB-QL; Tue, 19 Dec 2006 14:59:08 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gwl7C-0002K4-Sl
	for mip4@ietf.org; Tue, 19 Dec 2006 14:59:06 -0500
Received: from mail2.azairenet.com ([66.92.223.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gwl7B-0003ke-F2
	for mip4@ietf.org; Tue, 19 Dec 2006 14:59:06 -0500
Received: from [127.0.0.1] ([66.92.223.6]) by mail2.azairenet.com over TLS
	secured channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 19 Dec 2006 11:59:04 -0800
Message-ID: <45884487.2050209@azairenet.com>
Date: Tue, 19 Dec 2006 11:59:03 -0800
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: Yaron Sheffer <yaronf@checkpoint.com>, 
	Hans Sjostrand <hans@ipunplugged.com>
Subject: Re: [Mip4] Some comments
	on	WGLC:	draft-ietf-mip4-mobike-connectivity-01.txt
References: <200612171106.kBHB6H67001776@michael.checkpoint.com>
In-Reply-To: <200612171106.kBHB6H67001776@michael.checkpoint.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 19 Dec 2006 19:59:04.0291 (UTC)
	FILETIME=[2274DB30:01C723A8]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Cc: mip4@ietf.org
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Hi Yaron,

Yaron Sheffer wrote:

>>> It's not about subnets. It should be crystal
>>> clear that ANY detection of network movement whatsoever MUST result in a
>>> state that a security boundary may have been crossed and it sends a
>>> Registration Request to the i-HA.

>> Even when there is no subnet change? Why?
>>
> Because you can get an address on 192.168.0.0/16 from the enterprise DHCP server on the LAN, and immediately later another address on this subnet, or even the same one, from the untrusted WLAN (which uses a different NAT). This can be detected through layer-2 indications, but there are weirder cases when even that won't work.

Implicit in my reply was that DNAv4 (RFC 4436) is
used for movement detection. With DNAv4, the mobile
node will be able to detect movement to another subnet
for the scenario you mention above.

Hans Sjostrand wrote:
>>>
>>> In section 34. there is a sentence stating "Whenever the mobile node detects that it has moved to a new IP subnet [9] and its IP address changes". Again a lack of keywords. 
>> 4. Movement detection and security.
>>
>> This sentence just describes what the MN must do.
>> What would you like to see here?
> 
> Again, I don't think that we should define up new behaviors. RFC3344 states.
> -    A mobile node SHOULD initiate a registration whenever it detects a change in its network connectivity.
> 
> Thats pretty good for me. It's then up to each implementation to make it's own determination what "network connectivity" means.

>>
>>> It's not about subnets. It should be crystal clear that ANY detection of network movement whatsoever MUST result in a state that a security boundary may have been crossed and it sends a Registration Request to the i-HA.
>>
>> Even when there is no subnet change? Why?
> 
> Assume that you are on a trusted network. And the computer associates with a new BSSID (i.e. a different AP than before). What would you have wanted your VPN vendor to do.
> a) Accept the new nice AP that so kindly did let you in and continue to send clear text traffic.
> b) Stop sending traffic until a registration procedure against the i-HA has made it clear that no security boundary has been passed.
> 
> My choice is clear. And I think the RFC4436 guys agree since they point out that arp and dhcp is NOT a security feature. Therefore, subnets are not the for making sure security boundaries are crossed or not. 

Ok. We will go with what 3344 says. Here is the new
text in section 3.4

    Security boundary detection is based on the reachability of the i-HA
    from the mobile node's current point of attachment.  Whenever the
    mobile node detects a change in network connectivity, it sends a
    Registration Request to the i-HA without any VPN encapsulation.

This will also remove the reference to RFC 4436.

Vijay





-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Tue Dec 19 15:42:39 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GwlnL-0000Si-BQ; Tue, 19 Dec 2006 15:42:39 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GwlnK-0000QO-37
	for mip4@ietf.org; Tue, 19 Dec 2006 15:42:38 -0500
Received: from av10-1-sn2.hy.skanova.net ([81.228.8.181])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1GwlnI-0006lv-7F
	for mip4@ietf.org; Tue, 19 Dec 2006 15:42:38 -0500
Received: by av10-1-sn2.hy.skanova.net (Postfix, from userid 502)
	id 139DB3840C; Tue, 19 Dec 2006 21:42:35 +0100 (CET)
Received: from smtp4-2-sn2.hy.skanova.net (smtp4-2-sn2.hy.skanova.net
	[81.228.8.93]) by av10-1-sn2.hy.skanova.net (Postfix) with ESMTP
	id F039138358; Tue, 19 Dec 2006 21:42:34 +0100 (CET)
Received: from shiraz.levkowetz.com (81-232-110-214-no16.tbcn.telia.com
	[81.232.110.214])
	by smtp4-2-sn2.hy.skanova.net (Postfix) with ESMTP id E0C1037E42;
	Tue, 19 Dec 2006 21:42:34 +0100 (CET)
Received: from localhost ([127.0.0.1])
	by shiraz.levkowetz.com with esmtp (Exim 4.63)
	(envelope-from <henrik@levkowetz.com>)
	id 1GwlnG-0005av-J7; Tue, 19 Dec 2006 21:42:34 +0100
Message-ID: <45884EB8.1010909@levkowetz.com>
Date: Tue, 19 Dec 2006 21:42:32 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Thunderbird 1.5.0.8 (Macintosh/20061025)
MIME-Version: 1.0
To: McCann Peter-A001034 <pete.mccann@motorola.com>
Subject: Re: [Mip4] Summing up: draft-ietf-mip4-mobike-connectivity-01.txt
References: <BE4B07D4197BF34EB3B753DD34EBCD130133C9B2@de01exm67.ds.mot.com>
In-Reply-To: <BE4B07D4197BF34EB3B753DD34EBCD130133C9B2@de01exm67.ds.mot.com>
X-Enigmail-Version: 0.94.1.2
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: pete.mccann@motorola.com, mip4@ietf.org,
	henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on shiraz.levkowetz.com);
	SAEximRunCond expanded to false
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Cc: mip4@ietf.org
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1595474028=="
Errors-To: mip4-bounces@ietf.org

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============1595474028==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enigE86F6F7357AB9FB5A5A6B2AF"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigE86F6F7357AB9FB5A5A6B2AF
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi Pete,

on 2006-12-19 17:08 McCann Peter-A001034 said the following:
> Here is an attempted round-up of the issues that have been discussed:
>=20

=2E..
> 2. Bypass VPN for Registration Requests
>=20
> There was discussion on whether it is feasible to bypass a VPN tunnel=20
> for the Registration Request.  I think the discussion concluded that
> it was possible, but perhaps some text needs to be added describing
> the SAD.  Does anyone have some concrete text to propose?

[Co-chair hat off]

Actually, I'd say this is a bit of over-specification, too.  Although
bypass rules should work fine, there are other ways of doing this than
to add bypass rules, too; for some implementations it would be much more
natural to simply use for instance a BPF tap or equivalent to do this.


	Henrik


--------------enigE86F6F7357AB9FB5A5A6B2AF
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iD8DBQFFiE65eVhrtTJkXCMRAhUpAKCnDvlWhDL2W/ATr/6QTv1GRNEO1wCfW89D
5v5o9TMb9LCgpHt16xB3fp8=
=xVSe
-----END PGP SIGNATURE-----

--------------enigE86F6F7357AB9FB5A5A6B2AF--


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

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

--===============1595474028==--




From mip4-bounces@ietf.org Tue Dec 19 19:20:28 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GwpC4-0003px-7Y; Tue, 19 Dec 2006 19:20:24 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GwpC3-0003ps-MT
	for mip4@ietf.org; Tue, 19 Dec 2006 19:20:23 -0500
Received: from mail2.azairenet.com ([66.92.223.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GwpC2-0003ba-7A
	for mip4@ietf.org; Tue, 19 Dec 2006 19:20:23 -0500
Received: from [127.0.0.1] ([66.92.223.6]) by mail2.azairenet.com over TLS
	secured channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 19 Dec 2006 16:20:21 -0800
Message-ID: <458881C4.9060401@azairenet.com>
Date: Tue, 19 Dec 2006 16:20:20 -0800
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: McCann Peter-A001034 <pete.mccann@motorola.com>, 
	"Narayanan, Vidya" <vidyan@qualcomm.com>,
	Hans Sjostrand <hans@ipunplugged.com>
Subject: Re: [Mip4] Summing up: draft-ietf-mip4-mobike-connectivity-01.txt
References: <BE4B07D4197BF34EB3B753DD34EBCD130133C9B2@de01exm67.ds.mot.com>
In-Reply-To: <BE4B07D4197BF34EB3B753DD34EBCD130133C9B2@de01exm67.ds.mot.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 20 Dec 2006 00:20:21.0248 (UTC)
	FILETIME=[A2A6A800:01C723CC]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248
Cc: 'Mobile IPv4 Mailing List' <mip4@ietf.org>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

McCann Peter-A001034 wrote:
> Here is an attempted round-up of the issues that have been discussed:
> 
> 1. Use of an FA
> 
> If the MN is on the trusted network, then an FA can be used.
> There was a proposal from Vidya to put in the following text:
> 
>    "If the MN is moving from an untrusted network, it needs to first
> acquire an IP address, try
>     reaching the HA with it; if the HA is not reachable, use that
> address as the VPN 
>     tunnel outer address; if it is reachable, either operate in CCoA
> mode or then use an FA 
>     and re-register with the FA. OTOH, if the MN is moving from a
> trusted network, it may 
>     use an FA first; determine that the HA is unreachable, subsequently
> acquire an IP 
>     address and set up a VPN. "
> 
> However, there was a complaint that this might be over-specification.
> Can the MN attempt to use an FA before it determines that it is on a
> trusted network?  It seems to me that this is ok, the Registration Reply
> will contain the MN-HA Authenticator if the FA can reach the HA,
> otherwise
> the MN will get no response or a response that fails the Authentication
> check.
> Personally I don't see the difference between the case of starting on an
> untrusted
> network vs. starting on the trusted network: the procedure could be the
> same.

Currently the draft already says

3.1.2.  Access mode: 'f'

    This access mode is standard Mobile IPv4 [2] with a foreign agent
    care-of address.  The mobile node can use this mode only when it
    detects that it is connected to an internal trusted network and also
    detects a foreign agent on the access network.

This addresses part of Hans' concerns about using
Internet FAs.

Now coming to the mobile node's behavior, there seems
to be consensus for the mobile node to always configure
a CoA, check reachability to the i-HA and and if
connected to a trusted network, may use a FA if one
available on the trusted access network. If we agree on
this, I can propose some text.

> 2. Bypass VPN for Registration Requests
> 
> There was discussion on whether it is feasible to bypass a VPN tunnel 
> for the Registration Request.  I think the discussion concluded that
> it was possible, but perhaps some text needs to be added describing
> the SAD.  Does anyone have some concrete text to propose?

I don't think any text is needed. You can bypass the
SPD using either a higher priority SPD entry with
source address set to the local IP address or using
some implementation specific mechanisms.

> 3. Security considerations for exposing the Registration Request
> 
> This one seems pretty simple, there is a short list of concerns that
> could be written into the draft.  Vijay, can you draft some text?

Sent updated text this morning.

Narayanan, Vidya wrote:
> One issue that I think is still open is support for multiple
> interfaces (simultaneous bindings clarification). 

The mobile should be able to use simultaneous bindings.
I wasn't planning to prohibit it.

Vijay


-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Wed Dec 20 02:02:36 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GwvT5-0002C0-B9; Wed, 20 Dec 2006 02:02:23 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GwvT4-0002Br-2D
	for mip4@ietf.org; Wed, 20 Dec 2006 02:02:22 -0500
Received: from ns.academica.fi ([82.133.251.2])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GwvT2-0005vz-Op
	for mip4@ietf.org; Wed, 20 Dec 2006 02:02:22 -0500
Received: from [82.133.140.68] (ip82-133-140-68.customer.academica.fi
	[82.133.140.68])
	by ns.academica.fi (Postfix) with ESMTP id 51CE7199B26;
	Wed, 20 Dec 2006 07:59:49 +0200 (EET)
Message-ID: <4588DF84.8060607@iki.fi>
Date: Wed, 20 Dec 2006 09:00:20 +0200
From: Sami Vaarala <sami.vaarala@iki.fi>
User-Agent: Icedove 1.5.0.8 (X11/20061128)
MIME-Version: 1.0
To: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
Subject: Re: [Mip4] WGLC Comments: draft-ietf-mip4-mobike-connectivity-01.txt
References: <C24CB51D5AA800449982D9BCB903251335EA5A@NAEX13.na.qualcomm.com>	<45835C6C.1090404@iki.fi>
	<458840EE.9070204@azairenet.com>
In-Reply-To: <458840EE.9070204@azairenet.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Cc: "Narayanan, Vidya" <vidyan@qualcomm.com>,
	Mobile IPv4 Mailing List <mip4@ietf.org>,
	Henrik Levkowetz <henrik@levkowetz.com>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Vijay Devarapalli wrote:
> Here is some new text
> 
 >    When the mobile node sends a registration request to the i-HA from an
 >    untrusted network that does not go through the IPsec tunnel, it may
 >    be leaking the i-HA's address, its own identity including the NAI and
 >    the home address, and the Authenticator value in the authentication
 >    extensions to the untrusted network.  This may be a concern in some
 >    deployments.

Sounds best so far.  But why "it may be leaking"?  It is leaking this
information with 100% certainty (we're not assuming any trust in the
network).  Whether anyone is listening is another matter :-)  So how
about this refinement:

    When the mobile node sends a registration request to the i-HA from an
    untrusted network that does not go through the IPsec tunnel, it leaks
    the i-HA's address, its own identity including the NAI and the home
    address, and the Authenticator value in the authentication extensions
    to the untrusted network.  This may be a concern in some deployments.

BR,

-Sami

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Wed Dec 20 02:22:35 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gwvmc-0004Yf-Cm; Wed, 20 Dec 2006 02:22:34 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gwvma-0004YP-Rt
	for mip4@ietf.org; Wed, 20 Dec 2006 02:22:32 -0500
Received: from mail2.azairenet.com ([66.92.223.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GwvmY-0001p7-Hr
	for mip4@ietf.org; Wed, 20 Dec 2006 02:22:32 -0500
Received: from [127.0.0.1] ([66.92.223.6]) by mail2.azairenet.com over TLS
	secured channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 19 Dec 2006 23:22:29 -0800
Message-ID: <4588E4B3.7070008@azairenet.com>
Date: Tue, 19 Dec 2006 23:22:27 -0800
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: Sami Vaarala <sami.vaarala@iki.fi>
Subject: Re: [Mip4] WGLC Comments: draft-ietf-mip4-mobike-connectivity-01.txt
References: <C24CB51D5AA800449982D9BCB903251335EA5A@NAEX13.na.qualcomm.com>	<45835C6C.1090404@iki.fi>
	<458840EE.9070204@azairenet.com> <4588DF84.8060607@iki.fi>
In-Reply-To: <4588DF84.8060607@iki.fi>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 20 Dec 2006 07:22:29.0566 (UTC)
	FILETIME=[9B8145E0:01C72407]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Cc: "Narayanan, Vidya" <vidyan@qualcomm.com>,
	Mobile IPv4 Mailing List <mip4@ietf.org>,
	Henrik Levkowetz <henrik@levkowetz.com>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Sami Vaarala wrote:
> Vijay Devarapalli wrote:
>> Here is some new text
>>
>  >    When the mobile node sends a registration request to the i-HA from an
>  >    untrusted network that does not go through the IPsec tunnel, it may
>  >    be leaking the i-HA's address, its own identity including the NAI and
>  >    the home address, and the Authenticator value in the authentication
>  >    extensions to the untrusted network.  This may be a concern in some
>  >    deployments.
> 
> Sounds best so far.  But why "it may be leaking"?  It is leaking this
> information with 100% certainty (we're not assuming any trust in the
> network).  Whether anyone is listening is another matter :-)  So how
> about this refinement:
> 
>    When the mobile node sends a registration request to the i-HA from an
>    untrusted network that does not go through the IPsec tunnel, it leaks
>    the i-HA's address, its own identity including the NAI and the home
>    address, and the Authenticator value in the authentication extensions
>    to the untrusted network.  This may be a concern in some deployments.

Ok. Replaced "leak" by "reveal".

    When the mobile node sends a registration request to the i-HA from an
    untrusted network that does not go through the IPsec tunnel, it will
    reveal the i-HA's address, its own identity including the NAI and the
    home address, and the Authenticator value in the authentication
    extensions to the untrusted network.  This may be a concern in some
    deployments.

Vijay

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Wed Dec 20 10:19:24 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gx3E0-00053g-IT; Wed, 20 Dec 2006 10:19:20 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GwxXy-0003t2-HT; Wed, 20 Dec 2006 04:15:34 -0500
Received: from csmail.ucc.ie ([143.239.211.231])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GwxXx-0003Qk-1z; Wed, 20 Dec 2006 04:15:34 -0500
Received: from [143.239.201.197] (sapelo.ucc.ie [143.239.201.197])
	by csmail.ucc.ie (Postfix) with ESMTP id 4FFD95C035;
	Wed, 20 Dec 2006 09:15:30 +0000 (GMT)
Message-ID: <4588FF32.20406@cs.ucc.ie>
Date: Wed, 20 Dec 2006 09:15:30 +0000
From: "Cormac J. Sreenan" <cjs@cs.ucc.ie>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: "Cormac J. Sreenan" <cjs@cs.ucc.ie>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db
X-Mailman-Approved-At: Wed, 20 Dec 2006 10:19:19 -0500
Cc: 
Subject: [Mip4] CFP: Workshop on Embedded Networked Sensors (EmNets'07)
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org


Our apologies if you receive multiple copies of the EmNets CFP.

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

***********************************************************
			CALL FOR PAPERS

	Fourth Workshop on Embedded Networked Sensors
			(EmNets 2007)
			
			Cork, Ireland
			25-26 June 2007

		     www.cs.ucc.ie/emnets2007
***********************************************************

The Fourth Workshop on Embedded Networked Sensors (EmNets 2007) brings
together wireless sensor network researchers from academic and industrial
backgrounds to present groundbreaking results that will shed light on present
and future research challenges. The workshop emphasises results from
experiments or deployments that quantify the challenges in the wireless
sensor systems of today as well as early results from new ideas that introduce
promising approaches that will define the challenges in the wireless
sensor systems of tomorrow. We especially welcome papers reporting on
results that refute common assumptions, deployment experiences, novel and
original approaches, and, more generally, papers that will help inform and
guide research.

The EmNets Program Committee discourages submissions that are short 
versions of papers that will be submitted to other conferences in the 
near future, since its goal is to engage the research community in a 
discussion of future challenges and issues.

Topics of interest include, but are not limited to:
Validation/refutation of prior results
Application experiences: measurements, successes and failures
Future applications: requirements and challenges
Hardware platforms, tradeoffs, and trends
Data and network storage 
Delay-tolerant networking
Management, debugging, and troubleshooting
Network and software reliability
Network and system architectures
Software bug detection and tools
Energy sources, scavenging, and low-power operation
Human-Computer interfaces for sensornets
Benchmarks and evaluation suites

All papers will be subject to peer review. Accepted papers will
appear in a formal published proceedings.

IMPORTANT DATES:

Submission Deadline: March 9, 2007 (5 pages)
Notification: April 30, 2007
Camera Ready Due: May 21, 2007
Workshop: June 25-6, 2007

ORGANIZATION:

General Chair: 
    Cormac J. Sreenan, University College Cork
    cjs@cs.ucc.ie

Program Co-Chairs: 
    Philip Levis, Stanford University
    pal@cs.stanford.edu

    Joe Paradiso, MIT
    joep@media.mit.edu

Technical Program Committee:
Jan Beutel, ETH Zurich
Kieren Delaney, Cork Institute of Technology
Terry Dishongh, Intel Corporation
Henri Dubois-Ferriere, EPFL
Deborah Estrin, UCLA
David Gay, Intel Research Berkeley
Michel Goraczo, Microsoft Research
Margaret Martonosi, Princeton University
Mike Masquelier, Motorola
G.Q. Maguire Jr., KTH Sweden
Paddy Nixon, University College Dublin
Robert Poor, Adozu, Inc.
Frank Schmidt, EnOcean
John Regehr, University of Utah
Frank Schmidt, EnOcean
Randy Smith, Sun Microsystems
Jack Stankovic, University of Virginia
Robert Szewczyk, Moteiv Inc.
Henry Tirri, Nokia
Peter van der Stok, Philips, Eindhoven University of Technology 
Guang-Zhong Yang, Imperial College London 
Kazuo Yano, Hitachi
------------------------------------------------------------------


-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Wed Dec 20 10:26:31 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gx3Kx-0000LI-K7; Wed, 20 Dec 2006 10:26:31 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gx3Kw-0000L9-V2
	for mip4@ietf.org; Wed, 20 Dec 2006 10:26:30 -0500
Received: from 213.80.52.78.dataphone.se ([213.80.52.78]
	helo=mailgw.local.ipunplugged.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gx3Kt-0004Yr-3o
	for mip4@ietf.org; Wed, 20 Dec 2006 10:26:30 -0500
Received: from [127.0.0.1] (echo.local.ipunplugged.com [192.168.4.74])
	by mailgw.local.ipunplugged.com (8.12.8/8.12.3) with ESMTP id
	kBKFQ98m003115; Wed, 20 Dec 2006 16:26:18 +0100
Message-ID: <45895610.6040701@ipunplugged.com>
Date: Wed, 20 Dec 2006 16:26:08 +0100
From: Hans Sjostrand <hans@ipunplugged.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: McCann Peter-A001034 <pete.mccann@motorola.com>,
	Vijay Devarapalli <vijay.devarapalli@azairenet.com>
Subject: Re: [Mip4] Summing up: draft-ietf-mip4-mobike-connectivity-01.txt
References: <BE4B07D4197BF34EB3B753DD34EBCD130133C9B2@de01exm67.ds.mot.com>
In-Reply-To: <BE4B07D4197BF34EB3B753DD34EBCD130133C9B2@de01exm67.ds.mot.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: clamd / ClamAV version 0.75.1, clamav-milter version 0.75c
	on mailgw.local.ipunplugged.com
X-Virus-Status: Clean
X-Spam-Score: 0.1 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: mip4@ietf.org
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Pete and Vijay,

Some thoughts

1. Access mode home seams to be forgotten.
The answer there seams to be "Yes". Is the intention to pass WGLC 
without taking home mode in consideration?

3. Dual tunnel a normative reference
Vijay has proposed to make Dual tunnel a normative reference. I was sort 
of hoping that the draft-ietf-mip4-mobike-connectivity could be made 
self sufficient instead. But if it is the intention of the editors and 
working group to push these as a bundle I'm not the person to question 
that.

Regards
/// Hasse

>
> Anything else outstanding that I missed?
>
> -Pete
>
>   



-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Wed Dec 20 15:50:08 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gx8O6-0003pV-1K; Wed, 20 Dec 2006 15:50:06 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gx8O2-0003p3-UZ; Wed, 20 Dec 2006 15:50:02 -0500
Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Gx8O1-0001jG-SO; Wed, 20 Dec 2006 15:50:02 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id B50FB26EBE;
	Wed, 20 Dec 2006 20:50:01 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1Gx8O1-0002ZR-JM; Wed, 20 Dec 2006 15:50:01 -0500
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
To: ietf-announce@ietf.org
From: IESG Secretary <iesg-secretary@ietf.org>
Message-Id: <E1Gx8O1-0002ZR-JM@stiedprstage1.ietf.org>
Date: Wed, 20 Dec 2006 15:50:01 -0500
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 501044f827b673024f6a4cb1d46e67d2
Cc: Pete McCann <mccap@petoni.org>, mip4@ietf.org,
	Henrik Levkowetz <henrik@levkowetz.com>
Subject: [Mip4] WG Action: RECHARTER: Mobility for IPv4 (mip4) 
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

The Mobility for IPv4 (mip4) working group in the Internet Area of the
IETF has been rechartered.  For additional information, please contact the
Area Directors or the working group Chairs.

+++

Mobility for IPv4 (mip4)
------------------------

Current Status: Active Working Group

Chair(s):
Henrik Levkowetz <henrik@levkowetz.com>
Pete McCann <mccap@petoni.org>

Internet Area Director(s):
Jari Arkko <jari.arkko@piuha.net>
Mark Townsley <townsley@cisco.com>

Internet Area Advisor:
Jari Arkko <jari.arkko@piuha.net>

Mailing Lists:
General Discussion:mip4@ietf.org
To Subscribe: mip4-request@ietf.org
In Body: subscribe
Archive: http://www.ietf.org/mail-archive/web/mip4/index.html

Description of Working Group:

IP mobility support for IPv4 nodes (hosts and routers) is specified in
RFC3344. RFC 3344 mobility allows a node to continue using its
"permanent" home address as it moves around the Internet. The Mobile
IP protocols support transparency above the IP layer, including
maintenance of active TCP connections and UDP port bindings. Besides
the basic Mobile IPv4 (MIPv4) protocols, several other drafts deal
with concerns such as optimization, security, extensions, AAA support,
and deployment issues.

MIPv4 is currently being deployed on a wide basis (e.g., in cdma2000
networks). The scope of the deployment is on a fairly large scale and
accordingly, the MIP4 WG will focus on deployment issues and on
addressing known deficiencies and shortcomings in the protocol that
have come up as a result of deployment experience. Specifically, the
working group will complete the work items to facilitate interactions
with AAA environments, interactions with enterprise environments when
MIPv4 is used therein, and updating existing protocol specifications
in accordance with deployment needs and advancing those protocols that
are on the standards track.

Work expected to be done by the MIP4 WG as proposed by this charter is
as follows:

1. MIPv4 has been a proposed standard for several years. It has been
adopted by other standard development organizations and has been
deployed commercially. One of the next steps for the WG is to advance
the protocol to draft standard status. As part of advancing base
Mobile IP specs to DS, the MIPv4 NAI RFC (2794) will be revised to
reflect implementation experience.

2. Work items that are pending from the previous Mobile IP WG, which
will be completed by the MIP4 WG, are:

- completion of the MIB for the revised base Mobile IP specification
(2006bis)

- regional registration draft.

3. The MIP4 WG will also complete the work on MIPv4 interactions in
VPN scenarios. This work will involve identifying the requirements and
a solution development for MIPv4 operation in the presence of IPsec
VPNs.

4. Additionally, a proposal has been made for how MOBIKE could work
together with MIPv4. This proposal does not describe any new protocol,
but formulates a best current practice for deploying MOBIKE together
with MIPv4. The working group will adopt and complete this document.

5. Some issues have been raised with respect to RFC3519. These will be
identified and addressed as appropriate, through errata, revision of
RFC 3519, and/or supplemental documents as needed.

6. It has been proposed that the FMIP protocol, which has been
standardised for MIPv6 in the MIPSHOP working group, should also be
published as an experimental protocol for MIPv4. A draft for this
exists. The working group will take up and carry this work forward to
publication

7. An extension to carry generic strings in the Registration Reply
message has been proposed. The purpose is to supply supplemental
human-readable information intended to the MN user. The working group
will complete the specification and applicability statement of such an
extension.

8. RADIUS attributes for MIP4. A set of RADIUS attributes has been
proposed for MIPv4.

The working group will first produce a requirements specification,
describing how the work differs from the requirements in RFC 2977 and
the functionality provided by RFC 4004 (the MIPv4 Diameter App). The
reason why this first step is required is that RFC 3127 shows that
full RFC 2977 functionality can't be provided by even a considerably
extended RADIUS, so we need to match the requirements to what can be
done within RADIUS.

Provided the requirements work finds approval with ADs and RADEXT WG,
the workgroup will complete the specification of MIPv4 RADIUS
attributes, solicit feedback from the RADEXT WG, adjust, and submit
this for publication. Note that the work may require extensions to the
RADIUS attribute space which will be handled outside the MIP4 WG.

9. MIPv4 Extension for Configuration Options.

Several drafts have proposed extensions to help improve configuration
of MIPv4 clients. The latest proposal is for a general configuration
option extension which could carry information such as e.g., DNS
address and DHCP server address. The working group will take on and
complete one proposal for a configuration option extension.

10. Dual-stack Support

There have been several proposals for how to enable an IPv6 connection
over a network that supports Mobile IPv4. A protocol enhancement to
MIPv4 would allow for IPv6 support in a region where Mobile IPv4 has
already been implemented and deployed. This would allow a dual stack
mobile node to maintain IPv6 connectivity when using MIPv4. The
solution would therefore be applicable only to networks that are
not deploying Mobile IPv6.

The working group will take on and complete one proposal for IPv6 over
Mobile IPv4. This work is restricted to a small protocol extension
similar to current Mobile IPv4 functionality. Support for advanced
Mobile IPv6 functionality is strictly outside the scope.

A problem statement covering both Mobile IPv4 and IPv6 dual-stack
issues is expected to come out of MIP6 WG, and will not be developed
in MIP4 WG.


11. MIPv4 Moving Network Support

The Network Mobility (nemo) working group deals with the problem of
mobility of a whole network, such as might exist inside a vehicle,
train, or airplane. The nemo working group has developed draft
specifications for both IPv6 and IPv4 mobile networks. However, it has
been recognized that the IPv4 version of the protocol can be viewed as
an extension of the basic Mobile IPv4 protocol, and there is good reason
to do this extension in the mip4 working group. The working group will
take on the MIPv4 network mobility internet draft and progress it along
the standards track. In addition, the working group will take up
extensions to the basic MIPv4 moving network support in the areas of
dynamic prefix assignment and foreign agent support.


12. Asynchronous Notification Mechanism

In some situations, there is a need for Mobile IPv4 entities, such
as the home agent, foreign agent and mobile node to send and
receive asynchronous notification events related to the operation
of the MIPv4 protocol. A couple of examples of such events are
registration revocation from a home agent to a foreign agent in
order to terminate the service (to release resources and end
charging), and notification of pending HA shutdown and indication
of alternative serving HA, from a HA to the mobile node.

The base Mobile IP Specification [RFC3344] does not have a
provision for this. A new MIPv4 message pair which would support
asynchronous notifications, and a notification model describing
how to use these messages has been proposed. The working group
will take on the existing MIPv4 notification message draft as a
starting point, review and update it as needed, and progress it as
a standards track document. In addition, the working group will
also consider defining specific usages of the notification message
based on the examples in the current document.


Goals and Milestones:

Done AAA Keys for MIPv4 to IESG
Done MIPv4 VPN interaction problem statement to IESG
Done Low latency handover to experimental
Done Experimental MIPv4 message and extensions draft to IESG
Done Dynamic Home Agent assignment protocol solution to IESG
Done Revised MIPv4 Challenge/Response (3012bis) to IESG
Done Regional registration document to IESG
Jan 2007 MIPv4 Mobike interaction (BCP) to the IESG
Feb 2007 MIPv4 Extension for Config. Options (Proposed Std.) to
the IESG
Dec 2006 MIPv4 VPN interaction (BCP) to the IESG
May 2007 RADIUS Extensions for MIPv4 to the RADEXT WG for comment
Jan 2007 Revised MIPv4 specification to IESG for Draft Std.
Dec 2006 Generic Strings for MIPv4 (Proposed Std.) to the IESG
Mar 2007 MIPv4 RADIUS Extensions Requirements to the IESG
Dec 2006 FMIPv4 (Experimental) to the IESG
Sep 2007 RADIUS Extensions for MIPv4 (Proposed Std.) to the IESG
Nov 2007 Revised rfc2794bis (NAI extension) (Draft Std.) to the IESG
Aug 2007 Revised MIB for MIPv4 (Proposed Std.) to IESG
Apr 2007 Dual-stack MIPv4 (Draft Std.) to IESG
Jul 2007 Notification Mechanism (Draft Std.) to IESG
Sep 2007 Base MIPv4 Mobile Network Support (Draft Std.) to IESG
Nov 2007 MIPv4 Mobile Network Support for FAs (Draft Std.) to IESG
Nov 2007 MIPv4 Mobile Network Support Dynamic Address Assignment
(Draft Std.) to IESG

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Fri Dec 22 14:11:31 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GxpnX-0001on-RZ; Fri, 22 Dec 2006 14:11:15 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GxpnW-0001nt-U9
	for mip4@ietf.org; Fri, 22 Dec 2006 14:11:14 -0500
Received: from mail2.azairenet.com ([66.92.223.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GxpnS-0005O6-Gw
	for mip4@ietf.org; Fri, 22 Dec 2006 14:11:14 -0500
Received: from [127.0.0.1] ([66.92.223.6]) by mail2.azairenet.com over TLS
	secured channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 22 Dec 2006 11:11:09 -0800
Message-ID: <458C2DCA.2060004@azairenet.com>
Date: Fri, 22 Dec 2006 11:11:06 -0800
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: McCann Peter-A001034 <pete.mccann@motorola.com>, 
	"Narayanan, Vidya" <vidyan@qualcomm.com>,
	Hans Sjostrand <hans@ipunplugged.com>
Subject: Re: [Mip4] Summing up: draft-ietf-mip4-mobike-connectivity-01.txt
References: <BE4B07D4197BF34EB3B753DD34EBCD130133C9B2@de01exm67.ds.mot.com>
	<458881C4.9060401@azairenet.com>
In-Reply-To: <458881C4.9060401@azairenet.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 22 Dec 2006 19:11:09.0358 (UTC)
	FILETIME=[F01A24E0:01C725FC]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Cc: 'Mobile IPv4 Mailing List' <mip4@ietf.org>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Hello,

Vijay Devarapalli wrote:
> 3.1.2.  Access mode: 'f'
> 
>    This access mode is standard Mobile IPv4 [2] with a foreign agent
>    care-of address.  The mobile node can use this mode only when it
>    detects that it is connected to an internal trusted network and also
>    detects a foreign agent on the access network.
> 
> This addresses part of Hans' concerns about using
> Internet FAs.
> 
> Now coming to the mobile node's behavior, there seems
> to be consensus for the mobile node to always configure
> a CoA, check reachability to the i-HA and and if
> connected to a trusted network, may use a FA if one
> available on the trusted access network. If we agree on
> this, I can propose some text.

Here is some text to address this.

In section 3, add the following two paragraphs.

    Whenever the mobile node attaches to a new link, it may encounter a
    foreign agent.  The mobile node MUST not use the foreign agent
    care-of address with the i-HA when attached to an untrusted access
    network.  The default behavior for the mobile node is to always
    configure an address from the access link using DHCP.  The mobile
    node then checks if it is attached to a trusted access network by
    sending a registration request to the i-HA in the co-located care-of
    address mode.  If the mobile node discovers that it is attached to a
    trusted access network, then it MAY start using foreign agent care-of
    address with the i-HA.  In order to do this, the mobile node has to
    perform a new registration with the i-HA.

    The mobile node can use a foreign agent on a untrusted access
    network, if there is an external home agent that the mobile node is
    able to use.  The use of an external home agent in the untrusted
    access network and a home agent in the trusted access network at the
    same time is described in detail in [6].

In section 3.2, replace

    When the mobile node is inside the enterprise network and attached to
    the intranet, it uses Mobile IPv4 [2] for subnet mobility.  The
    mobile node uses a foreign agent care-of address, if a foreign agent
    is available.  Otherwise it acquires an address through DHCP on the
    access link and uses it as the co-located care-of address for Mobile
    IP.

with the following

    When the mobile node is inside the enterprise network and attached to
    the intranet, it uses Mobile IPv4 [2] for subnet mobility.  The
    mobile node always configures a care-of address address through DHCP
    on the access link and uses it as the co-located care-of address.
    The mobile node MAY use a foreign agent care-of address, if a foreign
    agent is available.  However, the foreign agent care-of address is
    used only when the mobile node is attached to the trusted access
    network.

You can find the pre02 version of the draft at
http://dvijay.com/ietf/internet-drafts/mip4/mipsec.txt

Vijay

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Fri Dec 22 14:21:03 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Gxpwz-00076k-Dl; Fri, 22 Dec 2006 14:21:01 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Gxpwx-00076c-U8
	for mip4@ietf.org; Fri, 22 Dec 2006 14:20:59 -0500
Received: from mail2.azairenet.com ([66.92.223.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gxpww-0006rg-Kr
	for mip4@ietf.org; Fri, 22 Dec 2006 14:20:59 -0500
Received: from [127.0.0.1] ([66.92.223.6]) by mail2.azairenet.com over TLS
	secured channel with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 22 Dec 2006 11:20:57 -0800
Message-ID: <458C301B.2030104@azairenet.com>
Date: Fri, 22 Dec 2006 11:20:59 -0800
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: Hans Sjostrand <hans@ipunplugged.com>
Subject: Re: [Mip4] Summing up: draft-ietf-mip4-mobike-connectivity-01.txt
References: <BE4B07D4197BF34EB3B753DD34EBCD130133C9B2@de01exm67.ds.mot.com>
	<45895610.6040701@ipunplugged.com>
In-Reply-To: <45895610.6040701@ipunplugged.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 22 Dec 2006 19:20:57.0913 (UTC)
	FILETIME=[4EE88290:01C725FE]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Cc: mip4@ietf.org, McCann Peter-A001034 <pete.mccann@motorola.com>
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Hans Sjostrand wrote:
> Pete and Vijay,
> 
> Some thoughts
> 
> 1. Access mode home seams to be forgotten.
> The answer there seams to be "Yes". Is the intention to pass WGLC 
> without taking home mode in consideration?

The home address has not been considered as an access
mode in any of the MIP4 VPN documents so far. We can
either continue not counting this as an access mode,
or add a new access mode to the draft.

3.1.1.  Access mode: 'h'

    This access mode is standard Mobile IPv4 [2] when the mobile node is
    attached to its home link.  The mobile node must detect that it is
    connected to home link before using this mode.

It seems unnecessary to me. Comments anyone else?

> 3. Dual tunnel a normative reference
> Vijay has proposed to make Dual tunnel a normative reference. I was sort 
> of hoping that the draft-ietf-mip4-mobike-connectivity could be made 
> self sufficient instead. But if it is the intention of the editors and 
> working group to push these as a bundle I'm not the person to question 
> that.

Yes, this is an issue. For now, I am hoping both
documents will advance as proposed standards. If ever
we need to make draft-ietf-mip4-mobike-connectivity
self contained, then we would have to add more text
on crossing security boundaries to the draft.

Vijay

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Wed Dec 27 19:55:17 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GzjXz-00039P-WC; Wed, 27 Dec 2006 19:55:04 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GziCP-0007Bw-Ei
	for mip4@ietf.org; Wed, 27 Dec 2006 18:28:41 -0500
Received: from achilles.noc.ntua.gr ([2001:648:2000:de::210])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GziCJ-00086c-Fa
	for mip4@ietf.org; Wed, 27 Dec 2006 18:28:41 -0500
Received: from ektor.telecom.ece.ntua.gr (ektor.telecom.ece.ntua.gr
	[147.102.7.1])
	by achilles.noc.ntua.gr (8.13.8/8.13.8) with ESMTP id kBRNSCMO048985;
	Thu, 28 Dec 2006 01:28:12 +0200 (EET)
	(envelope-from pimrc07-bounces@telecom.ntua.gr)
Received: from localhost (localhost.telecom.ece.ntua.gr [127.0.0.1])
	by ektor.telecom.ece.ntua.gr (Postfix) with ESMTP id C17D78A368;
	Thu, 28 Dec 2006 01:28:11 +0200 (EET)
X-Virus-Scanned: ClamAV version 0.88.7,
	clamav-milter version 0.88.7 on achilles.noc.ntua.gr
X-Virus-Scanned: Clam AntiVirus on ektor.telecom.ece.ntua.gr
Received: from ektor.telecom.ece.ntua.gr ([127.0.0.1])
	by localhost (ektor.telecom.ece.ntua.gr [127.0.0.1]) (amavisd-new,
	port 10024)
	with ESMTP id wNSYrXE2+rvy; Thu, 28 Dec 2006 01:28:10 +0200 (EET)
Received: from ektor.telecom.ece.ntua.gr (localhost.telecom.ece.ntua.gr
	[127.0.0.1])
	by ektor.telecom.ece.ntua.gr (Postfix) with ESMTP id 499248A288;
	Thu, 28 Dec 2006 01:25:07 +0200 (EET)
X-Original-To: pimrc07@telecom.ntua.gr
Delivered-To: pimrc07@telecom.ntua.gr
Received: from localhost (localhost.telecom.ece.ntua.gr [127.0.0.1])
	by ektor.telecom.ece.ntua.gr (Postfix) with ESMTP id 03E048A283
	for <pimrc07@telecom.ntua.gr>; Thu, 28 Dec 2006 01:21:02 +0200 (EET)
X-Virus-Scanned: Clam AntiVirus on ektor.telecom.ece.ntua.gr
Received: from ektor.telecom.ece.ntua.gr ([127.0.0.1])
	by localhost (ektor.telecom.ece.ntua.gr [127.0.0.1]) (amavisd-new,
	port 10024) with ESMTP id 06ZwBWXiACTv for <pimrc07@telecom.ntua.gr>;
	Thu, 28 Dec 2006 01:20:58 +0200 (EET)
Received: from harry (ppp076-057.dsl.hol.gr [89.210.76.57])
	by ektor.telecom.ece.ntua.gr (Postfix) with ESMTP id 1D2B98A281
	for <pimrc07@telecom.ntua.gr>; Thu, 28 Dec 2006 01:20:58 +0200 (EET)
Message-ID: <005d01c72a0d$aa1c95d0$1ab2a8c0@telecom.ntua.gr>
To: <pimrc07@telecom.ntua.gr>
Date: Thu, 28 Dec 2006 01:20:57 +0200
Organization: NTUA
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3028
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
X-Mailman-Approved-At: Thu, 28 Dec 2006 01:24:18 +0200
From: PIMRC 2007 <pimrc07@telecom.ntua.gr>
X-BeenThere: pimrc07@telecom.ntua.gr
X-Mailman-Version: 2.1.8
Precedence: list
List-Archive: <http://www.telecom.ntua.gr/pipermail/pimrc07>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Virus-Status: Clean
X-Spam-Score: 0.5 (/)
X-Scan-Signature: a87a9cdae4ac5d3fbeee75cd0026d632
X-Mailman-Approved-At: Wed, 27 Dec 2006 19:55:03 -0500
Cc: 
Subject: [Mip4] [pimrc07] CFP: IEEE PIMRC 2007, Athens, Greece
X-BeenThere: mip4@ietf.org
Reply-To: pimrc07@telecom.ntua.gr
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

[Apologies if you receive multiple copies of this CFP]


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

CALL FOR PAPERS AND WORKSHOP PROPOSALS

                            IEEE PIMRC 2007

            18th IEEE International Symposium on
Personal, Indoor and Mobile Radio Communications,
            September, 3-6, 2007, Athens, Greece
                     http://www.pimrc2007.org

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


Conference Main Theme: Wireless Entropy

Overview

PIMRC 2007 provides a global forum for presenting the most recent
advances, the future technical challenges and business opportunities that
comprise the contemporary landscape in wireless communications. The
organizers endeavour to attract contributions covering not only
conventional areas of wireless communications (e.g., physical layer), but
also emerging areas with high potential for essential scientific and
societal impact such as wireless sensors for biomedical applications and
non-trivial pervasive computing services. The latter areas are expected to
facilitate the development of a broad vision of innovative future
applications in wireless communications. The high quality IEEE endorsed
technical programme, will also include tutorials, workshops, exhibitions,
panel discussions and keynote presentations from leading experts coming
from the academic community, industry, as well as regulatory and
standardisation
bodies.

PIMRC 2007 will be held in Athens, Greece, September 3-6, 2007 i.e. one
week following the peak of Greece's beautiful summer season.


Call for Papers

Authors are invited to submit high-quality papers describing original and
previously unpublished contributions in a wide range of topics in wireless
communications. These topics are clustered into the following three major
categories:

1) Physical Layer and MAC
2) Mobile and Wireless Networks
3) Applications, Services and Business Models

Papers should be in English, strictly not exceeding 5 double-column pages
(3,000 words), in Adobe PDF format (which is the only accepted format for
PIMRC 2007). Authors should use the relevant IEEE template, ensuring an
IEEE Xplore compatible PDF-format.

To access the full list of topics, submission guidelines, as well as venue
and travel information please visit: www.pimrc2007.org

Important Dates

Full papers due:  March 3rd, 2007
Acceptance notice:   May 31st, 2007
Final manuscript due:  June 16th, 2007
Conference dates: September 3-6, 2007


Call for Workshop Proposals

We solicit workshop proposals on new and emerging topics in wireless
communication and networks, services, and applications. A proposal should
focus on a specific theme of current interest seeking for high-quality
submissions. Proposals for one-day workshops to be held in conjunction with
the main conference are solicited. A proposal can be a maximum of 2 pages
long and should clearly identify the theme and specific topics of interest
which define the scope of the workshop. It should also stress how it intends
to provide more insight into the proposed topics with respect to the main
conference. The proposal should include the workshop chairs and a tentative
list of program committee members.

The organizers of approved workshops will be responsible for advertising
their workshops, inviting experts, reviewing submitted papers, and
collecting camera-ready copies of accepted papers. The rest of the
organizational details (registrations, workshop rooms, etc.) will be
covered by the PIMRC Organizing Committee.

Proposal Submission:

Please send workshop proposals in PDF format by March 1, 2007 to the
workshop co-chairs, Dr. Charalambos Skianis (skianis@iit.demokritos.gr), Dr.
Nikos Passas (passas@di.uoa.gr) and Dr. Nikos Papadakis
(nkpap@telecom.ntua.gr).

Important Dates:

Proposal submission due: March 1, 2007
Notification of acceptance: April 1, 2007
Workshop date: September 3, 2007 

_______________________________________________
pimrc07 mailing list
pimrc07@telecom.ntua.gr
http://www.telecom.ntua.gr/mailman/listinfo/pimrc07

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Wed Dec 27 19:55:17 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GzjXz-00039K-PG; Wed, 27 Dec 2006 19:55:03 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GzfuN-0005MG-00; Wed, 27 Dec 2006 16:01:55 -0500
Received: from ozzie.acm.org ([63.118.7.46])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GzfuF-0002XV-IY; Wed, 27 Dec 2006 16:01:54 -0500
Received: from ozzie (localhost) by ozzie.acm.org (LSMTP for Windows NT v1.1b)
	with SMTP id <4.00294412@ozzie.acm.org>;
	Wed, 27 Dec 2006 16:05:25 -0500
Received: by LISTSERV.ACM.ORG (LISTSERV-TCP/IP release 14.3) with spool id
	19647810 for SENSORNET@LISTSERV.ACM.ORG; Wed, 27 Dec 2006 16:05:13
	-0500
Received: from psmtp.com (exprod7mx55.postini.com) by ozzie.acm.org (LSMTP for
	Windows NT v1.1b) with SMTP id <2.00293E7D@ozzie.acm.org>; Wed, 27
	Dec 2006 16:05:13 -0500
Received: from source ([63.118.7.109]) (using SSLv3) by exprod7mx55.postini.com
	([64.18.6.14]) with SMTP; Wed, 27 Dec 2006 13:01:24 PST
Received: from psmtp.com ([64.18.2.83]) by acm26-4.acm.org (ACM Email
	Forwarding Service) with SMTP id FHC95322 for <sensornet@acm.org>;
	Wed, 27 Dec 2006 16:01:22 -0500
Received: from source ([13.1.64.93]) by exprod7mx81.postini.com ([64.18.6.14])
	with SMTP; Wed, 27 Dec 2006 15:01:23 CST
Received: from [13.2.19.35] ([13.2.19.35]) by alpha.xerox.com with SMTP id
	<220232(1)>; Wed, 27 Dec 2006 13:01:10 PST
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-pstn-levels: (S:36.54759/99.90000 R:95.9108 P:95.9108 M:97.0282 C:98.6951 )
X-pstn-settings: 5 (2.0000:0.0000) s gt3 gt2 GT1 r p m c
X-pstn-addresses: from <yzhang@parc.com> [283/18]
X-pstn-levels: (S:36.54759/99.90000 R:95.9108 P:95.9108 M:97.0282 C:98.6951 )
X-pstn-settings: 4 (1.5000:1.5000) s gt3 gt2 gt1 r p m c
X-pstn-addresses: from <yzhang@parc.com> [141/11]
Message-ID: <4592DF16.30007@parc.com>
Date: Wed, 27 Dec 2006 13:01:10 PST
From: Ying Zhang <yzhang@PARC.COM>
X-To: sensornet@acm.org
To: SENSORNET@LISTSERV.ACM.ORG
Precedence: list
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf3becbbd6d1a45acbe2ffd4ab88bdc2
X-Mailman-Approved-At: Wed, 27 Dec 2006 19:55:03 -0500
Cc: 
Subject: [Mip4] CFP: IPSN07 Workshop
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Reply-To: Ying Zhang <yzhang@PARC.COM>
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

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

[Apologies if you receive multiple copies of this message.]


**************************************************************
      C A L L    F O R   P A P E R S

              IPSN 2007 Workshop
Data Sharing and Interoperability on the World-wide Sensor Web (DSI'07)
      (http://research.microsoft.com/~sumann/DSI07)
      April 24, 2007, Cambridge, Massachusetts, USA

(co-located with IPSN 2007, http://www.cse.wustl.edu/~lu/ipsn07.html)
-------------------------------------------------------------------

Over the last five years, the research community supporting embedded
sensing has benefited from the experiences of numerous real-world
deployments. Actual scientific applications are on the rise, and a
number of new environmental observatories are moving from planning to
implementation (NEON, WATERS). In parallel, we have seen an expansion
in the use smartphones and other consumer devices, supported by the
cellular network and capable of capturing acoustics and images,
creating a host of citizen-initiated sensing projects (e.g.,
videothevote.org).

While many algorithms for networking and control of embedded sensing
platforms anticipate within-deployment scaling of observational
resources, the introduction of diverse environmental observatories and
the variety of new urban applications suggests that interoperability,
and for the purpose of this workshop the ``sharing" of data and
models, represents another, equally important, kind of scaling. In
this workshop, we focus directly on the implications of widely shared
sensor data, models and algorithms, and the systems that might support
this.

Simply put, data is the raison d'etre of any sensing exercise. While
few researchers in the field would argue the point, too much attention
has been paid to the networking of distributed sensing and not enough
emphasis has been placed on the tools to manage, share, analyze, and
understand the data. Hosted in coordination with IPSN (emphasizing
algorithms for communications, coding theory, and distributed
estimation) and SPOTS (focusing on hardware and complete platforms),
this workshop will examine the various uses of data associated with
embedded sensing.


Topics of interest (but not limited to):
     - Data interoperability
     - Data Semantics
     - Extracting information from data and sensor data fusion
     - Managing data uncertainty
     - Systems for data integrity
     - Modeling sensor data
     - Managing spatial and temporal data (e.g., indexing, caching,
       query processing, etc.)
     - Automated or semi-automated processing of ad-hoc sensor data
     - Architecture to connect multiple sensor deployments together
     - Data visualization
     - Mash-up applications (the ability to pull in data/tools from
       multiple places and render it at a client) and workflows


Submissions:

     Authors are requested to submit original papers of no more than
     6 pages (standard IEEE proceedings two-column format),
     including figures, tables, and references in PDF that include
     contact information of all the authors.  If you have any
     questions regarding the submission process, please send e-mail
     to either Mark Hansen (cocteau@stat.ucla.edu) or
     Suman Nath (sumann@microsoft.com).
     See http://research.microsoft.com/~sumann/DSI07/ for submission
     instructions.


Important Dates:
          Papers due: Friday, February 23, 2007
          Notification: Friday, March 30, 2007
          Camera Ready: Friday, April 13, 2007
          Workshop: Tuesday, April 24, 2007


Organizing Committee:
          Mark Hansen, UCLA (PC Co-Chair)
          Suman Nath, Microsoft Research (PC Co-Chair)


Program Committee:
          Karl Aberer, EPFL
          Matthew Arrott, UCSD
          Amol Deshpande, University of Maryland
          Max Egenhofer, University of Maine
          Mark Hansen, UCLA
          Suman Nath, Microsoft Research
          Mani Srivastava, UCLA
          Andreas Terzis, JHU
          John Wilbanks, Science Commons

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Fri Dec 29 09:38:34 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H0IsJ-0003rC-1p; Fri, 29 Dec 2006 09:38:23 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H0IsH-0003r1-Rs; Fri, 29 Dec 2006 09:38:21 -0500
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1H0Is5-0008BT-T4; Fri, 29 Dec 2006 09:38:21 -0500
Received: from p130.piuha.net (localhost [127.0.0.1])
	by p130.piuha.net (Postfix) with ESMTP id 2EFEA898A6;
	Fri, 29 Dec 2006 16:38:06 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id AD54D898A4;
	Fri, 29 Dec 2006 16:38:05 +0200 (EET)
Message-ID: <4595284F.5000204@piuha.net>
Date: Fri, 29 Dec 2006 16:38:07 +0200
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 1.5.0.8 (X11/20061117)
MIME-Version: 1.0
To: "Soliman, Hesham" <Hesham@elevatemobile.com>, 
	"Tsirtsis, George" <tsirtsis@qualcomm.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: 9af087f15dbdd4c64ae6bbcdbc5b1d44
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>,
	Mobile IPv4 Mailing List <mip4@ietf.org>
Subject: [Mip4] AD review of draft-ietf-mip6-dsmip-problem-02.txt
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org

Hi all,

I reviewed this document. While I agree with
its conclusions, the draft still needs another
revision.

Here are the detailed comments:

Technical:
>    - Double the amount of configuration in the mobile node and the home
>
>      agent (e.g., security associations). 
... and later ...
>    In addition, deploying both protocols will require duplication of
>    security credentials on mobile nodes and home agents. This includes,
>    IPsec security associations, keying material, and new authentication
>    protocols for Mobile IPv6, in addition to the security credentials
>    and associations required by Mobile IPv4. Such duplication is again
>    significant with no gain to the operator or the mobile node.
 
Is this true under all circumstances? For instance,
is it true if one uses RFC 4285 or EAP for Mobile IPv6
authentication?

Depending on the answer, please reword
and add the necessary explanations.
>    - Local network optimizations for handovers will also need to be 
>      duplicated.
Only insofar as  they are bound to the mobility
protocol. There are a large number of optimizations
(L2 pre-auth etc) that deal with other aspects of the
handover problem and do not impact what happens
at IP or IP mobility layers.

Please reword.
> 3.1. Implementation burdens
>    
>    As mentioned above, a node that is IPv4 and IPv6 capable must also be
>
>    MIPv4 and MIPv6 capable to roam within the Internet. Clearly this
>    will add implementation efforts, which, we argue, are not necessary.
>
>    
>    In addition to the implementation efforts, some vendors may not
>    support both protocols in either mobile nodes or home agents.
>    Although this is more of a commercial issue, it does affect the
>    large-scale deployment of mobile devices on the Internet. 
>     
I'm not sure this section reflects the complete
picture. In a situation where host vendors
are independent of those who deploy the
mobility infrastructure, for instance, its
not clear that there is any reduction in
implementation effort.

Please reword for better balance.
 
>   Checking nits according to http://www.ietf.org/ID-Checklist.html:
>   * The document seems to lack a Security Considerations section.
>   

This is needed (not just the section but the
content as well).

>    Further work in this area, possibly independent of Mobile IP, may
>    also be of interest to some parties in which case it should be dealt
>    with separately from the incremental Mobile IP based changes.
This statement seems out of place. Or at least I could
not think of what specific further work you were thinking
of.
> 3.0 Problem description 
I am missing an explanation of why various existing,
non-mobility related transition mechanisms are insufficient
for solving the issues listed in this document. I believe
they are insufficient, but the document needs to explain
why.

Please add the explanation.

Editorial:

Overall, this document needs an editorial
cleanup and better formatting. Random
linefeeds in particular are making it hard
to read.
> 1. Terminology
>    
>    In addition to [KEYWORDS], this draft uses the following terms as
You do not use any keywords.
>   * The document seems to lack an IANA Considerations section.
>   
This is optional, but I normally insert a "There are no IANA
considerations." text just to make it clear that the IANA does
not have to read the entire document.
>   * The document seems to lack separate sections for Informative/Normative
>     References.
>   
This is needed.
>     
>     Checking conformance with RFC 3978/3979 boilerplate...
>
>   * The document seems to lack an RFC 3978 Section 5.5 Disclaimer -- however,
>     there's a paragraph with a matching beginning. Boilerplate error?
>   * The document seems to lack an RFC 3979 Section 5, para 1 IPR Disclosure
>     Acknowledgement -- however, there's a paragraph with a matching beginning.
>     Boilerplate error?
>   * The document seems to lack an RFC 3979 Section 5, para 2 IPR Disclosure
>     Acknowledgement -- however, there's a paragraph with a matching beginning.
>     Boilerplate error?
>
>   Checking nits according to http://www.ietf.org/ietf/1id-guidelines.txt:
>   * The document seems to lack a 1id_guidelines paragraph about
>     Internet-Drafts being working documents -- however, there's a paragraph
>     with a matching beginning. Boilerplate error?
>   * The document seems to lack a 1id_guidelines paragraph about 6 months
>     document validity -- however, there's a paragraph with a matching
>     beginning. Boilerplate error?
>   * The document seems to lack a 1id_guidelines paragraph about the list of
>     current Internet-Drafts -- however, there's a paragraph with a matching
>     beginning. Boilerplate error?
>   - The page length should not exceed 58 lines per page, but there was 7
>     longer pages, the longest (page 6) being 68 lines
>   - It seems as if not all pages are separated by form feeds - found 0 form
>     feeds but 7 pages
>   
Hesham, please, move to xml2rfc. Its so much easier
for everyone. You don't need any software, btw,
you can convert to text at xml.resource.org.
>   Miscellaneous warnings:
>   - The "Author's Address" (or "Authors' Addresses") section title is
>     misspelled.
>   
Please fix.

>    We argue that all of the above will hinder the deployment of Mobile
>    IPv6 as well as any dual stack solution in a mobile environment. We
I would suggest saying "makes harder to deploy ..." instead
of "will hinder". This could be just a language issue, but
my understanding is that "hinder" can be interpreted
as "block" -- and I'm not sure I would agree with such
a strong statement.
>    clearly inefficient since it requires: 
s/clearly// (better style)

> Each of these systems 
>      requiring their own sets of optimizations that may include
>      hierarchical Mobile IPv4, hierarchical Mobile IPv6 and Fast 
>      Handoffs for Mobile IPv4, mechanisms that are currently in 
>      development in the IETF. 
The list seems a bit out of place, and somewhat arbitrary.
I would suggest s/optimizations .*/optimizations./

> Deploying both in a dual stack mobile node
> introduces a number of inefficiencies.
s/inefficiencies/problems/ (a pure mip6+mip4 solution
would block either v4 or v6 communications, depending
on which type of access network you are in)
> The draft
>    also hints on how the current [MIPv4] and [MIPv6] protocols could be
>    extended so that they can support mobility management for a dual
>    stack node. 
References in abstract.

Also, I'm not sure you really talk or should talk about the "how"
part. Suggested rewording: "The draft also discusses requirements
for the Mobile IPv4 and Mobile IPv6 protocols so that they can
support ..."

> 2. Introduction and motivation 
This section focuses on the argument that we need
to have one mobility protocol handle both protocol
versions. I would suggest the addition of the basic
connectivity problem explanation before bullet
list.
> 3.4. The impossibility of maintaining IP connectivity 
I would start with this in Section 3.

--Jari


-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/



From mip4-bounces@ietf.org Fri Dec 29 15:50:48 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H0Oge-0005Dh-H6; Fri, 29 Dec 2006 15:50:44 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H0OgV-0005Br-64; Fri, 29 Dec 2006 15:50:35 -0500
Received: from ns3.neustar.com ([156.154.24.138])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1H0OgT-00072n-4a; Fri, 29 Dec 2006 15:50:35 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id A5F7E17624;
	Fri, 29 Dec 2006 20:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1H0Ofy-0000er-8d; Fri, 29 Dec 2006 15:50:02 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1H0Ofy-0000er-8d@stiedprstage1.ietf.org>
Date: Fri, 29 Dec 2006 15:50:02 -0500
X-Spam-Score: -2.5 (--)
X-Scan-Signature: 31247fb3be228bb596db9127becad0bc
Cc: mip4@ietf.org
Subject: [Mip4] I-D ACTION:draft-ietf-mip4-dsmipv4-01.txt 
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>,
	<mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-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 IPv4 Working Group of the IETF.

	Title		: Dual Stack Mobile IPv4
	Author(s)	: G. Tsirtsis, et al.
	Filename	: draft-ietf-mip4-dsmipv4-01.txt
	Pages		: 23
	Date		: 2006-12-29
	
This specification provides IPv6 extensions to the Mobile IPv4
   protocol.  The extensions allow a dual stack node to use IPv4 and
   IPv6 home addresses as well as to move between IPv4 and dual stack
   network infrastructures.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mip4-dsmipv4-01.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-mip4-dsmipv4-01.txt".

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

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

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

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-ietf-mip4-dsmipv4-01.txt

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

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


--OtherAccess--

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

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

--NextPart--




