From mip6-bounces@ietf.org Sun Jul 02 16:02:34 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fx88N-0002ib-Dr; Sun, 02 Jul 2006 16:01:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fx88M-0002iW-7X
	for mip6@ietf.org; Sun, 02 Jul 2006 16:01:34 -0400
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fx88K-0007Lu-O0
	for mip6@ietf.org; Sun, 02 Jul 2006 16:01:34 -0400
Received: from p130.piuha.net (localhost [127.0.0.1])
	by p130.piuha.net (Postfix) with ESMTP id D594A898B8;
	Sun,  2 Jul 2006 23:01:30 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id 5798D898B6;
	Sun,  2 Jul 2006 23:01:30 +0300 (EEST)
Message-ID: <44A82617.9060400@kolumbus.fi>
Date: Sun, 02 Jul 2006 23:01:27 +0300
From: Jari Arkko <jari.arkko@kolumbus.fi>
User-Agent: Mozilla Thunderbird 1.0.8 (X11/20060502)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Rajeev Koodli <rajeev.koodli@nokia.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: 1.1 (+)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>
Subject: [Mip6] some comments on draft-ietf-mip6-location-privacy-ps
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org


I happened to read this draft today and had a few comments:

>    This document is only concerned with IP Address Location Privacy in
>    the presence of IP Mobility, as applied to Mobile IPv6.  It does not
>    address the overall profiling problem.  Specifically, it does not
>    concern itself with MAC addresses.  Some other work may address the
>    problem of profiling IP and MAC identifiers (see for instance [1]).

This reads a little bit like MAC addresses would be the only problem.
I presume that there are other location privacy issues beyond those
listed in this draft, and that there are plenty of other privacy issues.
Suggested rewrite:

   This document is only concerned with IP address location privacy in
   the context of Mobile IPv6.  It does not address the overall privacy
   problem. For instance, it does not address privacy issues related to
   MAC addresses or the relationship of IP and MAC addresses [1].

>    Location privacy may be compromised if an on-looker is present on
>    the MN - HA path (when bidirectional tunneling is used), or when the
>    on-looker is present on the MN and CN path (when route optimization
>    is used).

This needs to be explained in more detail. From what I can see,
location privacy is always revealed on the mn-ha path, given the
location of the various options and headers in the binding updates.
You should also talk about the effect or lack thereof of applying
ESP with encryption.

>  Whenever it is involved
>    in IP communication, its correspondents can see an IP address valid
>    on the home network.  Elaborating further, the users involved in peer
>    - peer communication are likely to see a user-friendly identifier
>    such as a SIP URI, and the communication end-points in the IP
>    stack will see IP addresses.  Users uninterested in or unaware of
>    IP communication details will not see any difference when the MN
>    acquires a new IP address.  Of course any user can ``tcpdump'' or
>    ``ethereal'' a session, capture IP packets and map the MN's IP
>    address to an approximate geo-location.  When this mapping reveals a
>    ``home location'' of the user, the correspondent can conclude that
>    the user has not roamed.

This does not appear to follow. Assuming there's bidirectional tunneling
going on, the user is unaware of possible roaming.

>    The above description is valid regardless of whether a Home Address
>    is static or is dynamically allocated. 

Hmm... this seems to need more explanation or perhaps a more in-depth
treatment. Getting a dynamically allocated home address is similar to
running RFC 3041. If you do that, and employ different care-of addresses
for your different communications, it seems that you will be able
provide better location privacy protection, no?

>    Finally, it is also worthwhile to note that both the Home Address
>    and the Care of Address could be subject to profiling, just as
>    any other user traffic.  However, applying existing techniques to
>    thwart profiling may have implications to Mobile IPv6 signaling
>    performance.  For instance, changing the Care of Address often would
>    cause additional Return Routability and binding management signaling.
>    And, changing the Home Address often has implications on IPSec
>    security association management.  These issues need to be addressed
>    in the solutions.

Need to be? Perhaps the conclusion is a bit too quick. Changing
care of addresses "often" for privacy reasons would probably be
either much less often that a fast moving mobile node makes handovers,
or at least fairly infrequent, so is there need for optimizing the process?

The specific issue with IPsec SA management probably needs to
be spelled out too. For instance, if you used the same IKE SA for
everything, it would be kind of silly to worry about privacy. So
that implies multiple IKE SAs.

>  IPSec

IPsec

Missing stuff: I would have expected a good summary of conditions under
which location privacy is not a problem and a set of recommendations
on how networks and policies should be set up to prevent location
disclosure.

--Jari


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



From mip6-bounces@ietf.org Sun Jul 02 16:42:14 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fx8ko-0002UR-NU; Sun, 02 Jul 2006 16:41:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fx8kn-0002UM-GT
	for mip6@ietf.org; Sun, 02 Jul 2006 16:41:17 -0400
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fx8kl-0000zO-Qg
	for mip6@ietf.org; Sun, 02 Jul 2006 16:41:17 -0400
Received: from p130.piuha.net (localhost [127.0.0.1])
	by p130.piuha.net (Postfix) with ESMTP id DC12C898B8;
	Sun,  2 Jul 2006 23:41:14 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id 85009898B6;
	Sun,  2 Jul 2006 23:41:14 +0300 (EEST)
Message-ID: <44A82F67.6080105@kolumbus.fi>
Date: Sun, 02 Jul 2006 23:41:11 +0300
From: Jari Arkko <jari.arkko@kolumbus.fi>
User-Agent: Mozilla Thunderbird 1.0.8 (X11/20060502)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Mobile IPv6 Mailing List <mip6@ietf.org>
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: 225414c974e0d6437992164e91287a51
Cc: Gopal Dommety <gdommety@cisco.com>,
	Basavaraj Patil <basavaraj.patil@nokia.com>
Subject: [Mip6] new charter proposal
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org


Here's a new charter proposal that the chairs and me have worked
on. We would like some list discussion on whether this meets the
group's expectations. There will also be a short slot in Montreal to
talk about it. As has been indicated earlier, this is not a general
re-charter for potential new work but rather a cleanup and
re-alignment to what is already being worked on.

Mobility for IPv6 (mip6)

Last Modified: 2006-07-02

Chair(s):
Basavaraj Patil <basavaraj.patil@nokia.com>
Gopal Dommety <gdommety@cisco.com>

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: mip6@ietf.org
To Subscribe: https://www.ietf.org/mailman/listinfo/mip6
Archive: http://www.ietf.org/mail-archive/web/mip6/index.html

Description of Working Group:

Mobile IPv6 (MIP6) specifies routing support which permits an IPv6
host to continue using its home address as it moves around the
Internet, enabling continuity of sessions. Mobile IPv6 supports
transparency above the IP layer, including maintenance of active TCP
connections and UDP port bindings. The base specifications for Mobile
IPv6 consist of:

     o RFC 3775
     o RFC 3776

The primary goal of the MIP6 working group will be to enhance base
IPv6 mobility by continuing work on developments that are required for
wide-scale deployments. Additionally the working group will ensure
that any issues identified by implementation and interoperability
experience are addressed, and that the base specifications are
maintained. The group will also produce informational documentation,
such as design rationale documents or description of specific issues
within the protocol.

Deployment considerations call for work to reduce per-mobile node
configuration and enrollment effort, solutions to enable dual-stack
operation, mechanisms to support high-availabity home agents, and ways
to employ Mobile IPv6 in the presence of firewalls.

Work items related to base specification maintenance include:

 - Create and maintain an issue list that is generated on the basis of
   implementation and interoperability experience. Address specific
   issues with specific updates or revisions of the base
   specification.  This work relates only to corrections and
   clarifications. The working group shall not revisit design
   decisions or change the protocol.

 - Update RFC 3776 to specify the usage of IKEv2 for the establishment
   of the IPsec SA between the MN and HA. This work also provides a
   way for a mobile node to change its home address or employ multiple
   home addresses as needed.

 - Update the IANA considerations of RFC 3775 to allow extensions for
   experimental purposes as well passing of optional vendor-specific
   information.

Work items related to large scale deployment include:

 - Bootstrapping Mobile IPv6: A bootstrapping mechanism is intended to
   be used when the device is turned on the very first time and
   activates Mobile IPv6, or periodically such as when powering
   on. The WG should investigate and define the scope before solving
   the problem.

   Work on the problem statement and the solutions needed for various
   deployment scenarios.

 - Capture the AAA requirements needed for bootstrapping and
   deployment, and work with the Radext and DiME WGs on the solutions.

 - A Solution for MIP6 session continuity for dual stack hosts which
   attach to IPv4 access networks. Additionally provide a mechanism
   for carrying IPv4 packets via the Home agent for MIP6 capable
   dual-stack hosts. This work will be done in collaboration with the
   NEMO WG.

 - A protocol based solution for enhancing the reliability of home
   agents and a method to force a host to switch home agents.

 - Work on solutions to deal with firewalls and the problems that
   firewalls cause as identified in RFC 4487.

Work items related to informational documentation include:

 - Produce a problem statement relating to location privacy and the
   use of Mobile IPv6. Work with the IRTF MOBOPTS RG on developing the
   solution.

 - Produce a design rationale that documents the historical
   thinking behind the introduction of an alternative security
   mechanism, the Authentication Protocol (RFC 4285).

It should be noted that some of the features that are directly related
to Mobile IPv6 are being worked on in the MONAMI6, MIPSHOP, and NEMO
working groups. The specific extensions from these groups are out of
scope for the MIP6 working group. In particular, all optimizations are
out of scope. However, MIP6 may assist these groups when they use
features listed above and have requirements on them.

Milestones:

Done          Submit I-D 'MIPv6 operation with IKEV2 and the revised
        IPsec Architecture' to IESG for publication as a
        Proposed Standard.

Jul 2006    Submit I-D 'Motivation for Authentication I-D' to IESG
        for publication as Informational.

Aug 2006    Submit I-D 'Bootstrapping solution for Integrated Scenario'
        to IESG for publication as a Proposed Standard.

Aug 2006    Submit I-D 'Bootstrapping solution for split Scenario' to IESG
        for publication as a Proposed Standard.

Sep 2006    Submit I-D 'Goals for AAA HA Interface' to IESG for
        publication as Informational.

Nov 2006    Submit I-D 'Address Location Privacy and Mobile IPv6 Problem
        Statement' to IESG for publication as Informational.

Dec 2006    Submit I-D 'Home agent reliability' to IESG for publication
        as a Proposed Standard.

Dec 2006    Submit I-D 'Mobile IPv6 Experimental Allocations' to IESG for
        publication as a Proposed Standard.

Dec 2006    Submit I-D 'Mobile IPv6 Dual-Stack Operation' to IESG for
        publication as a Proposed Standard.

Apr 2007    Submit I-D 'Mobile IPv6 Operation with Firewalls' to IESG
        for publication as Informational.

May 2007    Submit I-D(s) related to specific updates and corrections
        of RFC 3775 to IESG for publication as Proposed Standard.

Note that there is one missing piece in the above: draft-ietf-mip6-cn-ipsec.
I would like to shepherd that through as an info/exp document instead
of incorporating it in the charter above. One reason for that is that
its ready and I can take it forward, but I generally want to avoid
making alternate designs Proposed Standard unless we have some
significant reasons for doing otherwise. But I'll listen to the group's
input on this too.

--Jari


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



From mip6-bounces@ietf.org Mon Jul 03 01:36:42 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FxH5y-0004WE-JS; Mon, 03 Jul 2006 01:35:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FxH5x-0004W2-41
	for mip6@ietf.org; Mon, 03 Jul 2006 01:35:41 -0400
Received: from mout.perfora.net ([217.160.230.41])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FxH5v-0006F1-OV
	for mip6@ietf.org; Mon, 03 Jul 2006 01:35:41 -0400
Received: from [68.126.193.27] (helo=IBM52A5038A94F)
	by mrelay.perfora.net (node=mrelayus1) with ESMTP (Nemesis),
	id 0MKp2t-1FxH5n3dCZ-0003K2; Mon, 03 Jul 2006 01:35:36 -0400
From: "Alper Yegin" <alper.yegin@yegin.org>
To: "'Jari Arkko'" <jari.arkko@kolumbus.fi>,
	"'Mobile IPv6 Mailing List'" <mip6@ietf.org>
Subject: RE: [Mip6] new charter proposal
Date: Sun, 2 Jul 2006 22:35:27 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
In-reply-to: <44A82F67.6080105@kolumbus.fi>
Thread-index: AcaeF//RHsdIhpMfQM+B/kuayBDtvQASgx6A
Message-ID: <0MKp2t-1FxH5n3dCZ-0003K2@mrelay.perfora.net>
X-Provags-ID: perfora.net abuse@perfora.net
	login:abf7a4bb310ea4dfc9b6841113e2970f
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2bf730a014b318fd3efd65b39b48818c
Cc: 'Gopal Dommety' <gdommety@cisco.com>,
	'Basavaraj Patil' <basavaraj.patil@nokia.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi Jari,

Assuming the group will decide to progress the draft-jang-mip6-hiopt-00.txt
as a standalone document, would you suggest we take it up in the MIP6 WG or
the DHC WG?

Alper

> -----Original Message-----
> From: Jari Arkko [mailto:jari.arkko@kolumbus.fi]
> Sent: Sunday, July 02, 2006 1:41 PM
> To: Mobile IPv6 Mailing List
> Cc: Gopal Dommety; Basavaraj Patil
> Subject: [Mip6] new charter proposal
> 
> 
> Here's a new charter proposal that the chairs and me have worked
> on. We would like some list discussion on whether this meets the
> group's expectations. There will also be a short slot in Montreal to
> talk about it. As has been indicated earlier, this is not a general
> re-charter for potential new work but rather a cleanup and
> re-alignment to what is already being worked on.
> 
> Mobility for IPv6 (mip6)
> 
> Last Modified: 2006-07-02
> 
> Chair(s):
> Basavaraj Patil <basavaraj.patil@nokia.com>
> Gopal Dommety <gdommety@cisco.com>
> 
> 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: mip6@ietf.org
> To Subscribe: https://www.ietf.org/mailman/listinfo/mip6
> Archive: http://www.ietf.org/mail-archive/web/mip6/index.html
> 
> Description of Working Group:
> 
> Mobile IPv6 (MIP6) specifies routing support which permits an IPv6
> host to continue using its home address as it moves around the
> Internet, enabling continuity of sessions. Mobile IPv6 supports
> transparency above the IP layer, including maintenance of active TCP
> connections and UDP port bindings. The base specifications for Mobile
> IPv6 consist of:
> 
>      o RFC 3775
>      o RFC 3776
> 
> The primary goal of the MIP6 working group will be to enhance base
> IPv6 mobility by continuing work on developments that are required for
> wide-scale deployments. Additionally the working group will ensure
> that any issues identified by implementation and interoperability
> experience are addressed, and that the base specifications are
> maintained. The group will also produce informational documentation,
> such as design rationale documents or description of specific issues
> within the protocol.
> 
> Deployment considerations call for work to reduce per-mobile node
> configuration and enrollment effort, solutions to enable dual-stack
> operation, mechanisms to support high-availabity home agents, and ways
> to employ Mobile IPv6 in the presence of firewalls.
> 
> Work items related to base specification maintenance include:
> 
>  - Create and maintain an issue list that is generated on the basis of
>    implementation and interoperability experience. Address specific
>    issues with specific updates or revisions of the base
>    specification.  This work relates only to corrections and
>    clarifications. The working group shall not revisit design
>    decisions or change the protocol.
> 
>  - Update RFC 3776 to specify the usage of IKEv2 for the establishment
>    of the IPsec SA between the MN and HA. This work also provides a
>    way for a mobile node to change its home address or employ multiple
>    home addresses as needed.
> 
>  - Update the IANA considerations of RFC 3775 to allow extensions for
>    experimental purposes as well passing of optional vendor-specific
>    information.
> 
> Work items related to large scale deployment include:
> 
>  - Bootstrapping Mobile IPv6: A bootstrapping mechanism is intended to
>    be used when the device is turned on the very first time and
>    activates Mobile IPv6, or periodically such as when powering
>    on. The WG should investigate and define the scope before solving
>    the problem.
> 
>    Work on the problem statement and the solutions needed for various
>    deployment scenarios.
> 
>  - Capture the AAA requirements needed for bootstrapping and
>    deployment, and work with the Radext and DiME WGs on the solutions.
> 
>  - A Solution for MIP6 session continuity for dual stack hosts which
>    attach to IPv4 access networks. Additionally provide a mechanism
>    for carrying IPv4 packets via the Home agent for MIP6 capable
>    dual-stack hosts. This work will be done in collaboration with the
>    NEMO WG.
> 
>  - A protocol based solution for enhancing the reliability of home
>    agents and a method to force a host to switch home agents.
> 
>  - Work on solutions to deal with firewalls and the problems that
>    firewalls cause as identified in RFC 4487.
> 
> Work items related to informational documentation include:
> 
>  - Produce a problem statement relating to location privacy and the
>    use of Mobile IPv6. Work with the IRTF MOBOPTS RG on developing the
>    solution.
> 
>  - Produce a design rationale that documents the historical
>    thinking behind the introduction of an alternative security
>    mechanism, the Authentication Protocol (RFC 4285).
> 
> It should be noted that some of the features that are directly related
> to Mobile IPv6 are being worked on in the MONAMI6, MIPSHOP, and NEMO
> working groups. The specific extensions from these groups are out of
> scope for the MIP6 working group. In particular, all optimizations are
> out of scope. However, MIP6 may assist these groups when they use
> features listed above and have requirements on them.
> 
> Milestones:
> 
> Done          Submit I-D 'MIPv6 operation with IKEV2 and the revised
>         IPsec Architecture' to IESG for publication as a
>         Proposed Standard.
> 
> Jul 2006    Submit I-D 'Motivation for Authentication I-D' to IESG
>         for publication as Informational.
> 
> Aug 2006    Submit I-D 'Bootstrapping solution for Integrated Scenario'
>         to IESG for publication as a Proposed Standard.
> 
> Aug 2006    Submit I-D 'Bootstrapping solution for split Scenario' to IESG
>         for publication as a Proposed Standard.
> 
> Sep 2006    Submit I-D 'Goals for AAA HA Interface' to IESG for
>         publication as Informational.
> 
> Nov 2006    Submit I-D 'Address Location Privacy and Mobile IPv6 Problem
>         Statement' to IESG for publication as Informational.
> 
> Dec 2006    Submit I-D 'Home agent reliability' to IESG for publication
>         as a Proposed Standard.
> 
> Dec 2006    Submit I-D 'Mobile IPv6 Experimental Allocations' to IESG for
>         publication as a Proposed Standard.
> 
> Dec 2006    Submit I-D 'Mobile IPv6 Dual-Stack Operation' to IESG for
>         publication as a Proposed Standard.
> 
> Apr 2007    Submit I-D 'Mobile IPv6 Operation with Firewalls' to IESG
>         for publication as Informational.
> 
> May 2007    Submit I-D(s) related to specific updates and corrections
>         of RFC 3775 to IESG for publication as Proposed Standard.
> 
> Note that there is one missing piece in the above: draft-ietf-mip6-cn-
> ipsec.
> I would like to shepherd that through as an info/exp document instead
> of incorporating it in the charter above. One reason for that is that
> its ready and I can take it forward, but I generally want to avoid
> making alternate designs Proposed Standard unless we have some
> significant reasons for doing otherwise. But I'll listen to the group's
> input on this too.
> 
> --Jari
> 
> 
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6


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



From mip6-bounces@ietf.org Mon Jul 03 02:05:43 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FxHY9-0003jr-Ly; Mon, 03 Jul 2006 02:04:49 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FxHY7-0003i8-1i
	for mip6@ietf.org; Mon, 03 Jul 2006 02:04:47 -0400
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FxHJi-0007pK-WB
	for mip6@ietf.org; Mon, 03 Jul 2006 01:49:56 -0400
Received: from p130.piuha.net (localhost [127.0.0.1])
	by p130.piuha.net (Postfix) with ESMTP id 86910898BC;
	Mon,  3 Jul 2006 08:49:53 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id 3D90E898B9;
	Mon,  3 Jul 2006 08:49:53 +0300 (EEST)
Message-ID: <44A8AFFD.3080804@kolumbus.fi>
Date: Mon, 03 Jul 2006 08:49:49 +0300
From: Jari Arkko <jari.arkko@kolumbus.fi>
User-Agent: Mozilla Thunderbird 1.0.8 (X11/20060502)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Alper Yegin <alper.yegin@yegin.org>
Subject: Re: [Mip6] new charter proposal
References: <0MKp2t-1FxH5n3dCZ-0003K2@mrelay.perfora.net>
In-Reply-To: <0MKp2t-1FxH5n3dCZ-0003K2@mrelay.perfora.net>
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: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: 'Mobile IPv6 Mailing List' <mip6@ietf.org>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Alper Yegin wrote:

>Hi Jari,
>
>Assuming the group will decide to progress the draft-jang-mip6-hiopt-00.txt
>as a standalone document, would you suggest we take it up in the MIP6 WG or
>the DHC WG?
>  
>
First: there's a work item in the proposed charter for bootstrapping
work. Depending on what makes sense to the group and chairs you
can break it up in multiple drafts if you want to. Charters or milestone
lists do not normally prevent you from doing that.

And the charter language on bootstrapping also allows you to
design the protocol mechanisms that you think you need.

As for the specific working group, we are trying to follow a model
where the DHCP-using WG is responsible for the actual document, but
that there is review from the DHC working group. For instance,
a parallel WGLC in both groups. This model makes the group with
specific application knowledge responsible on what they want to
do, and DHC responsible for ensuring that you are not breaking
DHCP.

--Jari



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



From mip6-bounces@ietf.org Mon Jul 03 04:27:01 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FxJkq-0008HV-47; Mon, 03 Jul 2006 04:26:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FxJkp-0008HQ-89
	for mip6@ietf.org; Mon, 03 Jul 2006 04:26:03 -0400
Received: from mout.perfora.net ([217.160.230.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FxJkn-0003Le-TV
	for mip6@ietf.org; Mon, 03 Jul 2006 04:26:03 -0400
Received: from [68.126.193.27] (helo=IBM52A5038A94F)
	by mrelay.perfora.net (node=mrelayus1) with ESMTP (Nemesis),
	id 0MKp2t-1FxJkj3hst-0003Ih; Mon, 03 Jul 2006 04:26:01 -0400
From: "Alper Yegin" <alper.yegin@yegin.org>
To: "'Vijay Devarapalli'" <vijay.devarapalli@azairenet.com>,
	"'Kent Leung \(kleung\)'" <kleung@cisco.com>
Subject: RE: [dhcwg] RE: [Mip6] [Updated] DHCP Option
	forHomeInformationDiscovery inMIPv6
Date: Mon, 3 Jul 2006 01:25:53 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
In-reply-to: <44A0620F.5090408@azairenet.com>
Thread-index: AcaZcal0wyAI6+N2TjKbYT9GBoEE/wFBusxw
Message-ID: <0MKp2t-1FxJkj3hst-0003Ih@mrelay.perfora.net>
X-Provags-ID: perfora.net abuse@perfora.net
	login:abf7a4bb310ea4dfc9b6841113e2970f
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f2984bf50fb52a9e56055f779793d783
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

> there is one issue.
> 
> draft-jang just does not define the DHCP options. it goes further.
> abstract of draft-jang says
> 
>     This draft defines a DHCP-based scheme to enable dynamic discovery of
>     Mobile IPv6 home agent address, home address, and home subnet.  New
>     DHCP options are defined to carry the information from a DHCP server
>     to the DHCP client running on the mobile node.

What is "further" in this? The words "dynamic discovery?" This is what DHCP
gives you for anything that you use it for.


> section 4.2 further goes and ahead and specifies mobile node
> behavior. the draft just does not define the options. 

These are all within the scope of defining a new DHCP option.

> it is also
> incomplete because it neither describes the scope of the problem

This is all defined in the Introduction section. If you have specific
comments, let us know and we'll fix it up.

> it is trying to address nor gives a complete solution.

Complete solution, I suspect, is the architecture you are referring to.
Again, this is a "protocol" document, not an "architecture" document.

> we can't have two documents that both describe how to use DHCP
> for MIP6 bootstrapping.

That's not happening. draft-jang-mip6-hiopt-00 defines a protocol
specification. draft-ietf-mip6-bootstrapping-integrated-dhc-01 defines the
architecture and refers to the former for the specific protocol details.

>From your other e-mail:

> > If the use cases are not limited to only bootstrapping,

> what other use cases? are those use cases specific to Mobile IPv6?
> do they fit into the MIP6 WG charter?

I had explained the use of statically configured DHCP servers earlier,
remember?

....

Vijay, we have circled around your concerns many times by now. I'm going to
stop now and see you in Montreal.

Alper




> 
> Vijay
> 
> Kent Leung (kleung) wrote:
> > Hi Kuntal and Vijay.
> >
> > See my posting, "Generalizing draft-jang-dhc-haopt for MIPv6 support in
> > DHCP", back on Jan 4, 2006 on this topic.  I proposed to keep the 2
> > drafts separate, one for defining DHCPv6 opcodes for MIPv6 parameters
> > and a bootstrap draft that references the DHCP options needed to achieve
> > its function.
> >
> > I agree there's no need to drag in references other to say that there's
> > value for the DHCP MIPv6 options.  3GPP2/WiMAX specs can reference the
> > DHCPv6 opcodes for MIPv6 draft/RFC, much like what MIPv6 bootstrap would
> > have done.
> >
> > As for what Vijay said about the WiMAX scheme, definitely true that it
> > doesn't conform to DHCP RFC 3315.  But we should keep the issues
> > separate.  I haven't read all the emails on the thread.  Just jumping in
> > to say the following:
> >
> >  - Keep 2 separate self contained drafts
> >  - IETF MIPv6 bootstrap draft references DHCP for MIPv6 draft
> >  - WiMAX and 3GPP2 can also reference DHCP for MIPv6 draft for their
> > bootstrapping schemes
> >
> > Just some explanatory comments:
> >  - 3GPP2 conforms to DHCPv6 in its bootstrapping scheme
> >  - WiMAX does not conform to DHCPv6 when using proxy DHCP server scheme
> >
> > But *ALL* of the above bootstrapping schemes use the same DHCP options
> > for MIPv6 parameters.  That's what justifies an independent DHCP for
> > MIPv6 draft, IMHO.
> >
> > Kent
> >
> >
> >
> >
> >>-----Original Message-----
> >>From: Chowdhury, Kuntal [mailto:kchowdhury@starentnetworks.com]
> >>Sent: Thursday, June 22, 2006 7:19 PM
> >>To: Vijay Devarapalli; Behcet Sarikaya
> >>Cc: mip6@ietf.org; Heejin Jang; dhcwg@ietf.org
> >>Subject: RE: [dhcwg] RE: [Mip6] [Updated] DHCP Option for
> >>HomeInformationDiscovery inMIPv6
> >>
> >>Sorry, I am not getting this. Why are we dragging WiMAX and
> >>3GPP2 references to justify the need for basic DHCP op-codes
> >>for HoA/HL/HA info?
> >>
> >>draft-jang-mip6-hiopt-00.txt defines the DHCPv6 op-codes for
> >>HA, HoA and HL info.
> >>
> >>draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt is the
> >>MIP6 bootstrapping solution that leverages DHCPv6 for HA/HL
> >>bootstrapping.
> >>
> >>There are tons of I-Ds and solutions in IETF that leverage other I-Ds.
> >>So, what is so special here? The decision to NOT merge these
> >>I-Ds was taken in the bootstrap DT. Why are we wasting
> >>people's time here to revisit basic decisions?
> >>
> >>-Kuntal
> >>
> >>
> >>
> >>>-----Original Message-----
> >>>From: Vijay Devarapalli [mailto:vijay.devarapalli@azairenet.com]
> >>>Sent: Thursday, June 22, 2006 12:55 PM
> >>>To: Behcet Sarikaya
> >>>Cc: mip6@ietf.org; Heejin Jang; dhcwg@ietf.org
> >>>Subject: Re: [dhcwg] RE: [Mip6] [Updated] DHCP Option for Home
> >>>InformationDiscovery inMIPv6
> >>>
> >>>Behcet Sarikaya wrote:
> >>>
> >>>>Hi Vijay,
> >>>>The idea in the present WiMAX document is quite simple:
> >>>>it uses EAP-PKMv2 (which is like 802.11i) authentication
> >>
> >>and during
> >>EAP
> >>
> >>>>transaction, they assume that AAA server determines that
> >>
> >>the MS is a
> >>
> >>>>CMIPv6 authorized user based on the AAA profile and it
> >>
> >>will include
> >>all
> >>
> >>>>the so-called bootstrapping info in the Access-Accept. Then MS can
> >>
> >>use
> >>
> >>>>RFC 3736 to make a DHCP Information Request to DHCP Relay
> >>
> >>colocated
> >>with
> >>
> >>>>NAS and use draft-jang (extended now with HoA) and receive all the
> >>
> >>info
> >>
> >>>>to configure MIP6.
> >>>
> >>>the DHCP Relay replies to the MN without relaying the DHCP request
> >>>from the MN to a DHCP server? this is not allowed with the current
> >>>IETF specs.
> >>>
> >>>
> >>>>  In this setup can you make a case for
> >>>>draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt?
> >>>
> >>>as far as I am concerned,
> >>>draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt
> >>>is the document that describes how to use DHCPv6 for MIPv6
> >>>bootstrapping. as for the setup in the WiMAX NWG, it is
> >>
> >>something that
> >>
> >>>doesn't conform to the IETF DHCP specs.
> >>>
> >>>Vijay
> >>><snip>
> >>
> 
> 
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6


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



From mip6-bounces@ietf.org Tue Jul 04 10:24:16 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fxlow-0000hd-5F; Tue, 04 Jul 2006 10:24:10 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fxlou-0000hT-Ud
	for mip6@ietf.org; Tue, 04 Jul 2006 10:24:08 -0400
Received: from neon.tcs.hut.fi ([130.233.215.20])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fxlos-0007XL-DQ
	for mip6@ietf.org; Tue, 04 Jul 2006 10:24:08 -0400
Received: from rhea.tcs.hut.fi (rhea.tcs.hut.fi [130.233.215.147])
	by neon.tcs.hut.fi (Postfix) with ESMTP id C0E528014C1;
	Tue,  4 Jul 2006 17:24:04 +0300 (EEST)
Date: Tue, 4 Jul 2006 17:24:04 +0300 (EEST)
From: Wassim Haddad <whaddad@tcs.hut.fi>
To: Jari Arkko <jari.arkko@kolumbus.fi>
Subject: Re: [Mip6] some comments on draft-ietf-mip6-location-privacy-ps
In-Reply-To: <44A82617.9060400@kolumbus.fi>
Message-ID: <Pine.LNX.4.58.0607041701370.12761@rhea.tcs.hut.fi>
References: <44A82617.9060400@kolumbus.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 1.1 (+)
X-Scan-Signature: 5ebbf074524e58e662bc8209a6235027
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>,
	Rajeev Koodli <rajeev.koodli@nokia.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi,

Just to mention that tracking the BU messages via the sequence number is also
one efficient way to link BU messages together and also to learn different
pseudo-HoA(s) and build a profile of the user. Correlating between these
data and other info accumulated from other observations (e.g., if we take
into consideration that most mobile devices will also have a WLAN interface
with possibly a static MAC address) may lead to breaking the user's privacy...

IMHO, it makes sense to mention this issue in a "problem statement" draft
regardless if there is (or not) a solution.


Regards,

Wassim H.


On Sun, 2 Jul 2006, Jari Arkko wrote:

>
> I happened to read this draft today and had a few comments:
>
> >    This document is only concerned with IP Address Location Privacy in
> >    the presence of IP Mobility, as applied to Mobile IPv6.  It does not
> >    address the overall profiling problem.  Specifically, it does not
> >    concern itself with MAC addresses.  Some other work may address the
> >    problem of profiling IP and MAC identifiers (see for instance [1]).
>
> This reads a little bit like MAC addresses would be the only problem.
> I presume that there are other location privacy issues beyond those
> listed in this draft, and that there are plenty of other privacy issues.
> Suggested rewrite:
>
>    This document is only concerned with IP address location privacy in
>    the context of Mobile IPv6.  It does not address the overall privacy
>    problem. For instance, it does not address privacy issues related to
>    MAC addresses or the relationship of IP and MAC addresses [1].
>
> >    Location privacy may be compromised if an on-looker is present on
> >    the MN - HA path (when bidirectional tunneling is used), or when the
> >    on-looker is present on the MN and CN path (when route optimization
> >    is used).
>
> This needs to be explained in more detail. From what I can see,
> location privacy is always revealed on the mn-ha path, given the
> location of the various options and headers in the binding updates.
> You should also talk about the effect or lack thereof of applying
> ESP with encryption.
>
> >  Whenever it is involved
> >    in IP communication, its correspondents can see an IP address valid
> >    on the home network.  Elaborating further, the users involved in peer
> >    - peer communication are likely to see a user-friendly identifier
> >    such as a SIP URI, and the communication end-points in the IP
> >    stack will see IP addresses.  Users uninterested in or unaware of
> >    IP communication details will not see any difference when the MN
> >    acquires a new IP address.  Of course any user can ``tcpdump'' or
> >    ``ethereal'' a session, capture IP packets and map the MN's IP
> >    address to an approximate geo-location.  When this mapping reveals a
> >    ``home location'' of the user, the correspondent can conclude that
> >    the user has not roamed.
>
> This does not appear to follow. Assuming there's bidirectional tunneling
> going on, the user is unaware of possible roaming.
>
> >    The above description is valid regardless of whether a Home Address
> >    is static or is dynamically allocated.
>
> Hmm... this seems to need more explanation or perhaps a more in-depth
> treatment. Getting a dynamically allocated home address is similar to
> running RFC 3041. If you do that, and employ different care-of addresses
> for your different communications, it seems that you will be able
> provide better location privacy protection, no?
>
> >    Finally, it is also worthwhile to note that both the Home Address
> >    and the Care of Address could be subject to profiling, just as
> >    any other user traffic.  However, applying existing techniques to
> >    thwart profiling may have implications to Mobile IPv6 signaling
> >    performance.  For instance, changing the Care of Address often would
> >    cause additional Return Routability and binding management signaling.
> >    And, changing the Home Address often has implications on IPSec
> >    security association management.  These issues need to be addressed
> >    in the solutions.
>
> Need to be? Perhaps the conclusion is a bit too quick. Changing
> care of addresses "often" for privacy reasons would probably be
> either much less often that a fast moving mobile node makes handovers,
> or at least fairly infrequent, so is there need for optimizing the process?
>
> The specific issue with IPsec SA management probably needs to
> be spelled out too. For instance, if you used the same IKE SA for
> everything, it would be kind of silly to worry about privacy. So
> that implies multiple IKE SAs.
>
> >  IPSec
>
> IPsec
>
> Missing stuff: I would have expected a good summary of conditions under
> which location privacy is not a problem and a set of recommendations
> on how networks and policies should be set up to prevent location
> disclosure.
>
> --Jari
>
>
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
>
>

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



From mip6-bounces@ietf.org Tue Jul 04 11:50:28 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FxnAL-0000cn-Tz; Tue, 04 Jul 2006 11:50:21 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FxnAL-0000c3-Fh
	for mip6@ietf.org; Tue, 04 Jul 2006 11:50:21 -0400
Received: from nf-out-0910.google.com ([64.233.182.189])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fxmyq-0004mA-9F
	for mip6@ietf.org; Tue, 04 Jul 2006 11:38:28 -0400
Received: by nf-out-0910.google.com with SMTP id m19so914378nfc
	for <mip6@ietf.org>; Tue, 04 Jul 2006 08:38:27 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=rWCiFeHRAQtjd4oDkcecd2ucSMHsPTYb1yilPuFaYbW+2ScMP80bTIGWJAAUMh0yCsuxeKcuzzQD1xq4Qxe269kA+ATW4SmoeOt5vA6gh5RcJ8DbUiDN4NaECRS5B1bhz+ekXo+twrBblERIl5xGDVTDXors7Aumb3Z3ayTkOHg=
Received: by 10.49.27.10 with SMTP id e10mr3391764nfj;
	Tue, 04 Jul 2006 08:38:26 -0700 (PDT)
Received: by 10.49.40.6 with HTTP; Tue, 4 Jul 2006 08:38:26 -0700 (PDT)
Message-ID: <eaa74a7e0607040838i3585c1e1y9520f2c9ac518f64@mail.gmail.com>
Date: Tue, 4 Jul 2006 17:38:26 +0200
From: "Gerardo Giaretta" <gerardo.giaretta@gmail.com>
To: "Jari Arkko" <jari.arkko@kolumbus.fi>
Subject: Re: [Mip6] new charter proposal
In-Reply-To: <44A82F67.6080105@kolumbus.fi>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <44A82F67.6080105@kolumbus.fi>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 48472a944c87678fcfe8db15ffecdfff
Cc: Gopal Dommety <gdommety@cisco.com>,
	Mobile IPv6 Mailing List <mip6@ietf.org>,
	Basavaraj Patil <basavaraj.patil@nokia.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi Jari,

thanks for providing the charter proposal. One question: is there any
plan to produce docs on bootstrapping of rfc4285?

In the charter proposal it is mentioned that the rationale behind
rfc4285 will be produced. Are we going to take a step forward and
specify bootstrapping mechanisms also for rfc4285? Or are they
considered specific of SDOs that are using rfc4285 (i.e. WiMAX Forum,
3GPP2) and therefore not standardized in IETF?

--Gerardo

On 7/2/06, Jari Arkko <jari.arkko@kolumbus.fi> wrote:
>
> Here's a new charter proposal that the chairs and me have worked
> on. We would like some list discussion on whether this meets the
> group's expectations. There will also be a short slot in Montreal to
> talk about it. As has been indicated earlier, this is not a general
> re-charter for potential new work but rather a cleanup and
> re-alignment to what is already being worked on.
>
> Mobility for IPv6 (mip6)
>
> Last Modified: 2006-07-02
>
> Chair(s):
> Basavaraj Patil <basavaraj.patil@nokia.com>
> Gopal Dommety <gdommety@cisco.com>
>
> 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: mip6@ietf.org
> To Subscribe: https://www.ietf.org/mailman/listinfo/mip6
> Archive: http://www.ietf.org/mail-archive/web/mip6/index.html
>
> Description of Working Group:
>
> Mobile IPv6 (MIP6) specifies routing support which permits an IPv6
> host to continue using its home address as it moves around the
> Internet, enabling continuity of sessions. Mobile IPv6 supports
> transparency above the IP layer, including maintenance of active TCP
> connections and UDP port bindings. The base specifications for Mobile
> IPv6 consist of:
>
>      o RFC 3775
>      o RFC 3776
>
> The primary goal of the MIP6 working group will be to enhance base
> IPv6 mobility by continuing work on developments that are required for
> wide-scale deployments. Additionally the working group will ensure
> that any issues identified by implementation and interoperability
> experience are addressed, and that the base specifications are
> maintained. The group will also produce informational documentation,
> such as design rationale documents or description of specific issues
> within the protocol.
>
> Deployment considerations call for work to reduce per-mobile node
> configuration and enrollment effort, solutions to enable dual-stack
> operation, mechanisms to support high-availabity home agents, and ways
> to employ Mobile IPv6 in the presence of firewalls.
>
> Work items related to base specification maintenance include:
>
>  - Create and maintain an issue list that is generated on the basis of
>    implementation and interoperability experience. Address specific
>    issues with specific updates or revisions of the base
>    specification.  This work relates only to corrections and
>    clarifications. The working group shall not revisit design
>    decisions or change the protocol.
>
>  - Update RFC 3776 to specify the usage of IKEv2 for the establishment
>    of the IPsec SA between the MN and HA. This work also provides a
>    way for a mobile node to change its home address or employ multiple
>    home addresses as needed.
>
>  - Update the IANA considerations of RFC 3775 to allow extensions for
>    experimental purposes as well passing of optional vendor-specific
>    information.
>
> Work items related to large scale deployment include:
>
>  - Bootstrapping Mobile IPv6: A bootstrapping mechanism is intended to
>    be used when the device is turned on the very first time and
>    activates Mobile IPv6, or periodically such as when powering
>    on. The WG should investigate and define the scope before solving
>    the problem.
>
>    Work on the problem statement and the solutions needed for various
>    deployment scenarios.
>
>  - Capture the AAA requirements needed for bootstrapping and
>    deployment, and work with the Radext and DiME WGs on the solutions.
>
>  - A Solution for MIP6 session continuity for dual stack hosts which
>    attach to IPv4 access networks. Additionally provide a mechanism
>    for carrying IPv4 packets via the Home agent for MIP6 capable
>    dual-stack hosts. This work will be done in collaboration with the
>    NEMO WG.
>
>  - A protocol based solution for enhancing the reliability of home
>    agents and a method to force a host to switch home agents.
>
>  - Work on solutions to deal with firewalls and the problems that
>    firewalls cause as identified in RFC 4487.
>
> Work items related to informational documentation include:
>
>  - Produce a problem statement relating to location privacy and the
>    use of Mobile IPv6. Work with the IRTF MOBOPTS RG on developing the
>    solution.
>
>  - Produce a design rationale that documents the historical
>    thinking behind the introduction of an alternative security
>    mechanism, the Authentication Protocol (RFC 4285).
>
> It should be noted that some of the features that are directly related
> to Mobile IPv6 are being worked on in the MONAMI6, MIPSHOP, and NEMO
> working groups. The specific extensions from these groups are out of
> scope for the MIP6 working group. In particular, all optimizations are
> out of scope. However, MIP6 may assist these groups when they use
> features listed above and have requirements on them.
>
> Milestones:
>
> Done          Submit I-D 'MIPv6 operation with IKEV2 and the revised
>         IPsec Architecture' to IESG for publication as a
>         Proposed Standard.
>
> Jul 2006    Submit I-D 'Motivation for Authentication I-D' to IESG
>         for publication as Informational.
>
> Aug 2006    Submit I-D 'Bootstrapping solution for Integrated Scenario'
>         to IESG for publication as a Proposed Standard.
>
> Aug 2006    Submit I-D 'Bootstrapping solution for split Scenario' to IESG
>         for publication as a Proposed Standard.
>
> Sep 2006    Submit I-D 'Goals for AAA HA Interface' to IESG for
>         publication as Informational.
>
> Nov 2006    Submit I-D 'Address Location Privacy and Mobile IPv6 Problem
>         Statement' to IESG for publication as Informational.
>
> Dec 2006    Submit I-D 'Home agent reliability' to IESG for publication
>         as a Proposed Standard.
>
> Dec 2006    Submit I-D 'Mobile IPv6 Experimental Allocations' to IESG for
>         publication as a Proposed Standard.
>
> Dec 2006    Submit I-D 'Mobile IPv6 Dual-Stack Operation' to IESG for
>         publication as a Proposed Standard.
>
> Apr 2007    Submit I-D 'Mobile IPv6 Operation with Firewalls' to IESG
>         for publication as Informational.
>
> May 2007    Submit I-D(s) related to specific updates and corrections
>         of RFC 3775 to IESG for publication as Proposed Standard.
>
> Note that there is one missing piece in the above: draft-ietf-mip6-cn-ipsec.
> I would like to shepherd that through as an info/exp document instead
> of incorporating it in the charter above. One reason for that is that
> its ready and I can take it forward, but I generally want to avoid
> making alternate designs Proposed Standard unless we have some
> significant reasons for doing otherwise. But I'll listen to the group's
> input on this too.
>
> --Jari
>
>
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
>

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



From mip6-bounces@ietf.org Tue Jul 04 14:03:25 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FxpEw-0006LH-S4; Tue, 04 Jul 2006 14:03:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FxpEv-0006HI-QX
	for mip6@ietf.org; Tue, 04 Jul 2006 14:03:13 -0400
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FxpEu-0002DR-HE
	for mip6@ietf.org; Tue, 04 Jul 2006 14:03:13 -0400
Received: from p130.piuha.net (localhost [127.0.0.1])
	by p130.piuha.net (Postfix) with ESMTP id 9FF35898B9;
	Tue,  4 Jul 2006 21:03:11 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id 5B2F3898B6;
	Tue,  4 Jul 2006 21:03:11 +0300 (EEST)
Message-ID: <44AAAD5B.5010203@kolumbus.fi>
Date: Tue, 04 Jul 2006 21:03:07 +0300
From: Jari Arkko <jari.arkko@kolumbus.fi>
User-Agent: Mozilla Thunderbird 1.0.8 (X11/20060502)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Gerardo Giaretta <gerardo.giaretta@gmail.com>
Subject: Re: [Mip6] new charter proposal
References: <44A82F67.6080105@kolumbus.fi>
	<eaa74a7e0607040838i3585c1e1y9520f2c9ac518f64@mail.gmail.com>
In-Reply-To: <eaa74a7e0607040838i3585c1e1y9520f2c9ac518f64@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi Gerardo,

> thanks for providing the charter proposal. One question: is there any
> plan to produce docs on bootstrapping of rfc4285?
>
> In the charter proposal it is mentioned that the rationale behind
> rfc4285 will be produced. Are we going to take a step forward and
> specify bootstrapping mechanisms also for rfc4285? 

The design rationale was really a separate thing. The version
of the charter that I posted does not include coverage of RFC
4285 in other ways.

But its a good question what the scope of the bootstrapping
work should be. What does the working group think? How
did we define it in the problem statement?

Ideally, I would not like to see that RFC 4285 causes divergent
solutions for every other part of the technology along with it. Can
we design our DHCP options and AAA interfaces so that they
don't care whether its IKEv2 or authentication option at the
bottom?

--Jari


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



From mip6-bounces@ietf.org Tue Jul 04 14:37:21 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fxplv-0002mw-Du; Tue, 04 Jul 2006 14:37:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fxplu-0002kX-If
	for mip6@ietf.org; Tue, 04 Jul 2006 14:37:18 -0400
Received: from rodin.i2r.a-star.edu.sg ([192.122.139.27])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fxpls-0004z5-1G
	for mip6@ietf.org; Tue, 04 Jul 2006 14:37:18 -0400
Received: from rodin.i2r.a-star.edu.sg (localhost [127.0.0.1])
	by rodin.i2r.a-star.edu.sg (8.13.1/8.13.1) with ESMTP id k64Ib7aI022823
	for <mip6@ietf.org>; Wed, 5 Jul 2006 02:37:08 +0800 (SGT)
Received: from newmailhost.i2r.a-star.edu.sg ([192.122.134.76])
	by rodin.i2r.a-star.edu.sg (8.13.1/8.13.1) with ESMTP id k64Ib7pW022813
	for <mip6@ietf.org>; Wed, 5 Jul 2006 02:37:07 +0800 (SGT)
Received: from mailbe01.teak.local.net ([192.122.134.10])
	by mailhost.lit.org.sg
	(Sun Java System Messaging Server 6.1 HotFix 0.06 (built Nov 11 2004))
	with ESMTP id <0J1W00CDI6DXP050@mailhost.lit.org.sg> for mip6@ietf.org;
	Wed, 05 Jul 2006 02:37:09 +0800 (SGT)
Received: from mailfe01.teak.local.net ([192.122.134.9])
	by mailbe01.teak.local.net with Microsoft SMTPSVC(6.0.3790.1830); Wed,
	05 Jul 2006 02:36:47 +0800
Received: from D8ZXLJ1S ([192.168.137.186]) by mailfe01.teak.local.net with
	Microsoft SMTPSVC(6.0.3790.1830); Wed, 05 Jul 2006 02:36:46 +0800
Date: Wed, 05 Jul 2006 02:37:23 +0800
From: QIU Ying <qiuying@i2r.a-star.edu.sg>
Subject: Re: [Mip6] some comments on draft-ietf-mip6-location-privacy-ps
To: Jari Arkko <jari.arkko@kolumbus.fi>,
	Rajeev Koodli <rajeev.koodli@nokia.com>
Message-id: <008b01c69f98$e3e726e0$ba89a8c0@D8ZXLJ1S>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
X-Mailer: Microsoft Outlook Express 6.00.2900.2869
Content-type: text/plain; format=flowed; charset=Windows-1252;
	reply-type=original
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
X-OriginalArrivalTime: 04 Jul 2006 18:36:46.0909 (UTC)
	FILETIME=[CE2626D0:01C69F98]
X-Spam-Score: 1.1 (+)
X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024
Cc: mip6@ietf.org, "Qiu, Ying" <qiuying@i2r.a-star.edu.sg>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org


Hi, Jari

My 2 cents inline.

> Date: Sun, 02 Jul 2006 23:01:27 +0300
> From: Jari Arkko <jari.arkko@kolumbus.fi>
> Subject: [Mip6] some comments on draft-ietf-mip6-location-privacy-ps

>>    Location privacy may be compromised if an on-looker is present on
>>    the MN - HA path (when bidirectional tunneling is used), or when the
>>    on-looker is present on the MN and CN path (when route optimization
>>    is used).
>
> This needs to be explained in more detail. From what I can see,
> location privacy is always revealed on the mn-ha path, given the
> location of the various options and headers in the binding updates.

More than that, such as SPI, seq#, lifetime, also the mentioned MAC.

>>    The above description is valid regardless of whether a Home Address
>>    is static or is dynamically allocated.
>
> Hmm... this seems to need more explanation or perhaps a more in-depth
> treatment. Getting a dynamically allocated home address is similar to
> running RFC 3041. If you do that, and employ different care-of addresses
> for your different communications, it seems that you will be able
> provide better location privacy protection, no?

It should be able to provide better location privacy protection if different 
care-of address is used for different communications. The more random 
information reveal to an eavesdropper, the more difficult to be profiled the 
MN's activities by the eavesdropper. The question: is it worth to do that 
since the CoA might already change very frequently?

>>    Finally, it is also worthwhile to note that both the Home Address
>>    and the Care of Address could be subject to profiling, just as
>>    any other user traffic.  However, applying existing techniques to
>>    thwart profiling may have implications to Mobile IPv6 signaling
>>    performance.  For instance, changing the Care of Address often would
>>    cause additional Return Routability and binding management signaling.
>>    And, changing the Home Address often has implications on IPSec
>>    security association management.  These issues need to be addressed
>>    in the solutions.
>
> Need to be? Perhaps the conclusion is a bit too quick. Changing
> care of addresses "often" for privacy reasons would probably be
> either much less often that a fast moving mobile node makes handovers,
> or at least fairly infrequent, so is there need for optimizing the 
> process?

I think current frequency is enough, as often as the handovers or 7 minutes 
as RR.

> The specific issue with IPsec SA management probably needs to
> be spelled out too. For instance, if you used the same IKE SA for
> everything, it would be kind of silly to worry about privacy. So
> that implies multiple IKE SAs.

We could use the same SA for a while but change its SPI, since the cost of 
negotiating the session keys is considerable.

Regards
Qiu Ying

>
> Missing stuff: I would have expected a good summary of conditions under
> which location privacy is not a problem and a set of recommendations
> on how networks and policies should be set up to prevent location
> disclosure.
>
> --Jari
>
>
>


------------ Institute For Infocomm Research - Disclaimer -------------
This email is confidential and may be privileged.  If you are not the intended recipient, please delete it and notify us immediately. Please do not copy or use it for any purpose, or disclose its contents to any other person. Thank you.
--------------------------------------------------------

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



From mip6-bounces@ietf.org Wed Jul 05 02:33:29 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fy0ws-00029h-SJ; Wed, 05 Jul 2006 02:33:22 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fxrzq-0005gr-6D; Tue, 04 Jul 2006 16:59:50 -0400
Received: from mailman.ufsc.br ([150.162.1.5])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Fxrzl-0003aG-HK; Tue, 04 Jul 2006 16:59:50 -0400
Received: from localhost (localhost [127.0.0.1])
	by mailman.ufsc.br (Postfix) with ESMTP id 56DD57D8A6;
	Tue,  4 Jul 2006 17:49:08 -0300 (BRT)
Received: from mailman.ufsc.br ([127.0.0.1])
	by localhost (mailman.ufsc.br [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 04378-05; Tue,  4 Jul 2006 17:49:07 -0300 (BRT)
Received: from mailman.ufsc.br (mailman.ufsc.br [150.162.1.5])
	by mailman.ufsc.br (Postfix) with ESMTP id C1D947D803;
	Tue,  4 Jul 2006 17:47:58 -0300 (BRT)
X-Original-To: researchers@mailman.ufsc.br
Delivered-To: researchers@mailman.ufsc.br
Received: from localhost (localhost [127.0.0.1])
	by mailman.ufsc.br (Postfix) with ESMTP id E476D7D801
	for <researchers@mailman.ufsc.br>; Tue,  4 Jul 2006 17:47:49 -0300 (BRT)
Received: from mailman.ufsc.br ([127.0.0.1])
	by localhost (mailman.ufsc.br [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 03973-07 for <researchers@mailman.ufsc.br>;
	Tue,  4 Jul 2006 17:47:44 -0300 (BRT)
Received: from rot.barddal.br (44054.static.fln.virtua.com.br [200.174.44.54])
	by mailman.ufsc.br (Postfix) with ESMTP id 118737D7FC
	for <researchers@mailman.ufsc.br>; Tue,  4 Jul 2006 17:47:41 -0300 (BRT)
Received: from Xuxu (201-11-104-175.fnsce703.dsl.brasiltelecom.net.br
	[201.11.104.175] (may be forged)) (authenticated bits=0)
	by rot.barddal.br (8.13.1/8.13.1) with ESMTP id k64KjSbS023737;
	Tue, 4 Jul 2006 20:45:29 GMT
Message-ID: <034401c69faa$d6847720$9f00a8c0@Xuxu>
From: "Profa Mirela Sechi Moretti Annoni Notare" <mirela@barddal.br>
To: <researchers@mailman.ufsc.br>
Date: Tue, 4 Jul 2006 17:45:42 -0300
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Antivirus: avast! (VPS 0627-0, 03/07/2006), Outbound message
X-Antivirus-Status: Clean
X-barddal-MailScanner-Information: Please contact the ISP for more information
X-barddal-MailScanner: Found to be clean
X-barddal-MailScanner-From: mirela@barddal.br
X-Virus-Scanned: by amavisd-new at mailman.ufsc.br
X-BeenThere: researchers@mailman.ufsc.br
X-Mailman-Version: 2.1.5
Precedence: list
X-Virus-Scanned: by amavisd-new at mailman.ufsc.br
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 6a45e05c1e4343200aa6b327df2c43fc
X-Mailman-Approved-At: Wed, 05 Jul 2006 02:33:21 -0400
Cc: =?iso-8859-1?Q?Jos=E9_M_Parente_de_Oliveira?= <parente@ita.br>
Subject: [Mip6] [Researchers] SSI'2006 - 8th International Symposium on
	System and Information Security
X-BeenThere: mip6@ietf.org
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

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

                        CALL FOR PAPERS

                           SSI=B42006
8th International Symposium on System and Information Security
             Sao Jose dos Campos, Sao Paulo, Brazil
                    November 08-10, 2006

           THESIS AND DISSERTATIONS AWARD

       Summary-Paper Submission Deadline: September 11, 2006

                http://www.ssi.org.br/english/

                       Organized by
       Technological Institute of Aeronautics - ITA
             Department of Computer Science
         and Casimiro Montenegro Filho Foundation

-------------------------------------------------------------
INTRODUCTION

The International Symposium on System and Information Security (SSI)
is organized by Technological Institute of Aeronautics (ITA)
and is the foremost event of its kind in Latin America.

Each year, researchers, students, and practitioners from
academia, industry, and government organizations convene
in Sao Jose' dos Campos, Brazil, to present and discuss
the latest research and developments in the area.

SSI'2006 is selecting the best works in System and
Information Security area, finished, defended and approved
from Jan 01, 2006 to Jul 31, 2006, in the following categories:
    . Under graduation conclusion works;
    . Master dissertation; and
    . PhD thesis.

The award objective is to promote and disseminate the work
of young researchers and stimulate the Brazilian and
Latin-American students that finished their phd, master
and under graduation studies to take part at SSI'2006.

For the submission, the candidates must send papers that
are summaries of their academic final works.

These papers must be 10 to 20 pages long, including
eventual figures, tables and references.
In order to distinguish from regular papers, these works
are here called of "summary-papers".

SSI'2006 aims at providing a larger dissemination of the
high quality material generated by the symposium due the
publication of the accepted papers in the Electronic
Proceedings at conference site.

-------------------------------------------------------------
THE AWARD

It will be chosen one paper in each category among the
summary-papers submitted that conforms the established
requirements.

The certificates will be given in the SSI'2006 award ceremony.
All the awarded authors will receive Certificate proving the
SSI'2006 award, and informing the category.

Moreover, depending of the finance availability, the winner
of each category, if Brazilians, will receive 100% of the
tickets (from home to SSI), plus hotel and SSI'2006 fees.

-------------------------------------------------------------
CERTIFICATION OF FINISHED AND APPROVED WORK

The candidates must send the official CONCLUSION
CERTIFICATE to the Award Coordinator - SSI'2006 CTD
A/C Profa. Mirela Sechi Moretti Annoni Notare
by fax - number (48)3234-2344.

In the case of PhD thesis or master dissertation, the
certification must inform: the title of the defended and
approved work, the defense date, the adviser and co-adviser
names, and the signature of the program coordinator.

In the case of under graduate conclusion works, the certification
must inform: the title of the work, the month and year of the
conclusion, the name of the adviser and co-adviser,and the
signature of the program coordinator.

-------------------------------------------------------------
JUDGMENT

The works will be judge by a committee coordinated by Profa.
Mirela Sechi Moretti Annoni Notare (Barddal Fundation, Brazil).

The committee member names will be available at the
conference site, as soon as possible.

-------------------------------------------------------------
TOPICS

The summary-papers must include or be related to one or more
of the following topics:

  . Artificial Intelligence methods in system security
  . Authentication, access control and auditing
  . Computer forensics
  . Cryptography
  . Database security
  . Dependability
  . Digital certificates and Public Key Infrastructure - PKI
  . Digital Rights Management
  . E-commerce security
  . Firewalls and other security tools
  . Formal methods in system security
  . Internet/Web security
  . Intrusion detection and prevention
  . Management of enterprise security
  . Mobile code and agent security
  . Network security
  . New security paradigms
  . Operating systems security
  . Risk/vulnerability analysis, assessment and management
  . Security in electronic voting systems
  . Security of distributed systems
  . Security of emerging technologies
  . Security policies
  . Secure programming
  . Security in P2P and Grid computing
  . Threats and information warfare
  . Trust management
  . User privacy and anonymity
  . Viruses and other malicious code
  . Wireless and ubiquitous computing security

-------------------------------------------------------------
IMPORTANT DATES

Summary-papers submission: 11/09/2006
Acceptance Notification: 02/10/2006
Camera-ready version: 13/10/2006

-------------------------------------------------------------
INSTRUCTIONS TO THE AUTHORS

The summary-papers can be in Portuguese or in English, and
must be in the format .pdf  (or .ps).

The submission is in electronic form only. Summary-papers
should be submitted by the deadline to:
https://submissoes.sbc.org.br/ssi2006 following the link ssi2006TD

The summary-papers follow the same format of the regular papers.
Papers must use 10-point Times New Roman font and have at
most twenty (20) A4 (not Letter) single-spaced, two-column,
unnumbered pages. The page limit include all figures, tables,
and references. Margins should be: left 3 cm, and bottom, top
and right 2 cm. The space between columns should be 1 cm.
Title in font size 10, bold, caps and centered.

Differently of the regular papers,the summary-papers must
include the author identification, affiliation, lab and involved projects=
.

The summary-papers must have the following organizational structure:
  . Introduction;
  . Declaration of the problem/research object;
  . Description of the previous and related works,
    showing why the problem is not yet well solved;
  . Hypothesis and research questions [optional];
  . Proposed solution;
  . Method used to solve the problem;
  . Research contribution;
  . Research results;
  . Conclusion;
  . References.

Templates to write the papers are available at
http://www.ssi.org.br (link "authors").
The available formats are: Latex Unix,
Latex Windows, Star Office e MS Word (.rtf).
The template aims at facilitating formatting the
summary-paper in the required format.

-------------------------------------------------------------
ACCESS TO THE FULL TEXTS OF THESIS,
DISSERTATIONS AND UNDER GRADUATION
CONCLUSION WORKS

The candidates can make available in the web (via URL or FTP)
their full works, in .pdf format, for the more detailed
reading and evaluation by the committee - just in case some
committee member consider that relevant.
(these addresses should be informed during the submission)

Important to emphasize that the committee member is not
imposed to read the full texts - but read the summary-papers only.

-------------------------------------------------------------
ORGANIZING COMMITTEE

GENERAL CHAIR
Jose M. Parente de Oliveira - ITA, Brazil

TECHNICAL PROGRAM COMMITTEE CO-CHAIRS
Carlos Becker Westphall - Federal Univ. Santa Catarina, Brazil
Jos=E9 Carlos Brustoloni - University of Pittsburgh, USA

THESIS AND DISSERTATION AWARD CHAIR
Mirela Sechi Moretti Annoni Notare  - Fac. Barddal/SC

-------------------------------------------------------------
FURTHER INFORMATION

Conference announcements and updated information will be
available at: http://www.ssi.org.br

For other information, please send email to the general chair,
Jose M. Parente de Oliveira (dir@ssi.org.br).

ITA - Technological Institute of Aeronautics
Computer Science Division
A/C Prof. Jose' M. Parente de Oliveira [General Chair]
Praca Mal. Eduardo Gomes, 50 - Vila das Acacias
12228-901 Sao Jose dos Campos-SP - BRAZIL

Phone +55(12) 3947-6869 [Secretary]
Fax +55(12) 3947-5989=20


--=20
Esta mensagem foi verificada pelo sistema de antiv=EDrus e
 acredita-se estar livre de perigo.

_______________________________________________
Researchers mailing list
Researchers@mailman.ufsc.br
http://mailman.ufsc.br/mailman/listinfo/researchers

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



From mip6-bounces@ietf.org Wed Jul 05 07:39:58 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fy5jV-0007S6-Ea; Wed, 05 Jul 2006 07:39:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fy5jU-0007S1-Ly
	for mip6@ietf.org; Wed, 05 Jul 2006 07:39:52 -0400
Received: from py-out-1112.google.com ([64.233.166.183])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fy5jS-0003kb-E9
	for mip6@ietf.org; Wed, 05 Jul 2006 07:39:52 -0400
Received: by py-out-1112.google.com with SMTP id t32so2176202pyc
	for <mip6@ietf.org>; Wed, 05 Jul 2006 04:39:50 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=oRSWOuvfQddZE0KLObnMU3J6otRnS1jcxJOnTcARiuacC0wJFLKXHFg6qr9mV22J5er4mR0jvc75piedkThSeNBwqDQ0zC2p4F4d5z0Y9yhEky3gue4/vEX3iCkviamU/LvqS9LgzS2X5yxEwKcUUzaJTirtxQyz3bPcTCYzdZk=
Received: by 10.35.99.14 with SMTP id b14mr5037793pym;
	Wed, 05 Jul 2006 04:39:50 -0700 (PDT)
Received: by 10.35.111.9 with HTTP; Wed, 5 Jul 2006 04:39:50 -0700 (PDT)
Message-ID: <729b68be0607050439u4780a160r8356c034db39b04f@mail.gmail.com>
Date: Wed, 5 Jul 2006 13:39:50 +0200
From: "Jean-Michel Combes" <jeanmichel.combes@gmail.com>
To: "Jari Arkko" <jari.arkko@kolumbus.fi>
Subject: Re: [Mip6] new charter proposal
In-Reply-To: <44A82F67.6080105@kolumbus.fi>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <44A82F67.6080105@kolumbus.fi>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Cc: Gopal Dommety <gdommety@cisco.com>,
	Mobile IPv6 Mailing List <mip6@ietf.org>,
	Basavaraj Patil <basavaraj.patil@nokia.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi Jari,

2006/7/2, Jari Arkko <jari.arkko@kolumbus.fi>:
>
> Here's a new charter proposal that the chairs and me have worked
> on. We would like some list discussion on whether this meets the
> group's expectations. There will also be a short slot in Montreal to
> talk about it. As has been indicated earlier, this is not a general
> re-charter for potential new work but rather a cleanup and
> re-alignment to what is already being worked on.
>

[snip]

>
> Note that there is one missing piece in the above: draft-ietf-mip6-cn-ipsec.
> I would like to shepherd that through as an info/exp document instead
> of incorporating it in the charter above. One reason for that is that
> its ready and I can take it forward, but I generally want to avoid
> making alternate designs Proposed Standard unless we have some
> significant reasons for doing otherwise.

IMO, the draft-ietf-mip6-cn-ipsec should become Proposed Standard. The
main reasons are :
- No heavy modifications in the MIPv6 implementation (in fact, just to
be able to desactivate the RR mechanism)
- To have a mechanism that allows a strong security for RO

Thanks.

Best regards.

JMC.

> But I'll listen to the group's
> input on this too.
>
> --Jari
>
>
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
>

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



From mip6-bounces@ietf.org Wed Jul 05 08:17:14 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fy6Jd-0005ub-7b; Wed, 05 Jul 2006 08:17:13 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fy6Jb-0005uW-F2
	for mip6@ietf.org; Wed, 05 Jul 2006 08:17:11 -0400
Received: from ithilien.qualcomm.com ([129.46.51.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fy6Ja-0007sh-2t
	for mip6@ietf.org; Wed, 05 Jul 2006 08:17:11 -0400
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
	k65CH59b014624
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Wed, 5 Jul 2006 05:17:06 -0700
Received: from NAEXBR02.na.qualcomm.com (naexbr02.qualcomm.com [10.46.92.109])
	by crowley.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	k65CH57G024579; Wed, 5 Jul 2006 05:17:05 -0700 (PDT)
Received: from NAEX14.na.qualcomm.com ([10.47.5.242]) by
	NAEXBR02.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 5 Jul 2006 05:16:57 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] new charter proposal
Date: Wed, 5 Jul 2006 05:17:02 -0700
Message-ID: <7EB20EA0938B4D42A2D82689365C9B7A07CE55@NAEX14.na.qualcomm.com>
In-Reply-To: <729b68be0607050439u4780a160r8356c034db39b04f@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] new charter proposal
Thread-Index: AcagKjVt1z7LjzFVSNiI7aAN/y2yFAAAlOsQ
From: "Soliman, Hesham" <hsoliman@qualcomm.com>
To: "Jari Arkko" <jari.arkko@kolumbus.fi>
X-OriginalArrivalTime: 05 Jul 2006 12:16:57.0936 (UTC)
	FILETIME=[E9469500:01C6A02C]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de
Cc: Gopal Dommety <gdommety@cisco.com>,
	Mobile IPv6 Mailing List <mip6@ietf.org>,
	Basavaraj Patil <basavaraj.patil@nokia.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi Jari,=20

I didn't see a specific mention of:

http://www.ietf.org/internet-drafts/draft-ietf-mip6-dsmip-problem-02.txt

It's in the current charter. Is this covered under the DSMIP work
anyway? It's been ready for WGLC for a while.=20

Hesham

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



From mip6-bounces@ietf.org Wed Jul 05 08:28:12 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fy6UE-0007bN-UQ; Wed, 05 Jul 2006 08:28:10 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fy6UD-0007bI-HP
	for mip6@ietf.org; Wed, 05 Jul 2006 08:28:09 -0400
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fy6UC-0000Tw-7a
	for mip6@ietf.org; Wed, 05 Jul 2006 08:28:09 -0400
Received: from p130.piuha.net (localhost [127.0.0.1])
	by p130.piuha.net (Postfix) with ESMTP id 0F9EE898A9;
	Wed,  5 Jul 2006 15:28:07 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id C73A28988E;
	Wed,  5 Jul 2006 15:28:06 +0300 (EEST)
Message-ID: <44ABB053.6010809@piuha.net>
Date: Wed, 05 Jul 2006 15:28:03 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Mozilla Thunderbird 1.0.8 (X11/20060502)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Soliman, Hesham" <hsoliman@qualcomm.com>
Subject: Re: [Mip6] new charter proposal
References: <7EB20EA0938B4D42A2D82689365C9B7A07CE55@NAEX14.na.qualcomm.com>
In-Reply-To: <7EB20EA0938B4D42A2D82689365C9B7A07CE55@NAEX14.na.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: d6b246023072368de71562c0ab503126
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Soliman, Hesham wrote:

>Hi Jari, 
>
>I didn't see a specific mention of:
>
>http://www.ietf.org/internet-drafts/draft-ietf-mip6-dsmip-problem-02.txt
>
>It's in the current charter. Is this covered under the DSMIP work
>anyway?
>  
>
Good question. I wouldn't mind having a problem statement document
too if the group wants that. Question: there's a brief description of
the problem/motivation/scope/scenarios in the beginning of the
solution draft. Is that insufficient?

--Jari


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



From mip6-bounces@ietf.org Wed Jul 05 08:36:39 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fy6cQ-0006q2-Nc; Wed, 05 Jul 2006 08:36:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fy6cO-0006px-Mn
	for mip6@ietf.org; Wed, 05 Jul 2006 08:36:36 -0400
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fy6cN-0001M6-Bg
	for mip6@ietf.org; Wed, 05 Jul 2006 08:36:36 -0400
Received: from sabrina.qualcomm.com (sabrina.qualcomm.com [129.46.61.150])
	by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k65CaX0N030353
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Wed, 5 Jul 2006 05:36:34 -0700
Received: from NAEXBR03.na.qualcomm.com (naexbr03.qualcomm.com
	[129.46.134.172])
	by sabrina.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	k65CaQko004102; Wed, 5 Jul 2006 05:36:33 -0700 (PDT)
Received: from NAEX14.na.qualcomm.com ([10.47.5.242]) by
	NAEXBR03.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 5 Jul 2006 05:33:29 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] new charter proposal
Date: Wed, 5 Jul 2006 05:33:24 -0700
Message-ID: <7EB20EA0938B4D42A2D82689365C9B7A07CE58@NAEX14.na.qualcomm.com>
In-Reply-To: <44ABB053.6010809@piuha.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] new charter proposal
Thread-Index: AcagLn+CHsYGDYyhSjuVCBxfx+SRrgAABXwA
From: "Soliman, Hesham" <hsoliman@qualcomm.com>
To: "Jari Arkko" <jari.arkko@piuha.net>
X-OriginalArrivalTime: 05 Jul 2006 12:33:29.0315 (UTC)
	FILETIME=[382F0330:01C6A02F]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org



 > >http://www.ietf.org/internet-drafts/draft-ietf-mip6-dsmip-pr
oblem-02.txt
 > >
 > >It's in the current charter. Is this covered under the DSMIP work
 > >anyway?
 > > =20
 > >
 > Good question. I wouldn't mind having a problem statement document
 > too if the group wants that. Question: there's a brief description of
 > the problem/motivation/scope/scenarios in the beginning of the
 > solution draft. Is that insufficient?

=3D> Depends on who you ask :). Given the amount of questions that we
continue to get about the problem and why this is needed I would think
it's insufficient. I think this will be a good document to point people
to when these issues come up. Thomas just asked for the same thing
recently on the list. So I think it's helpful to have it.=20

Hesham

 >=20
 > --Jari
 >=20
 >=20

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



From mip6-bounces@ietf.org Wed Jul 05 08:56:25 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fy6vU-0003aU-GL; Wed, 05 Jul 2006 08:56:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fy6vT-0003aM-Tk
	for mip6@ietf.org; Wed, 05 Jul 2006 08:56:19 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fy6Ik-0007pa-EY
	for mip6@ietf.org; Wed, 05 Jul 2006 08:16:18 -0400
Received: from nf-out-0910.google.com ([64.233.182.190])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Fy6FS-0008Qu-4l
	for mip6@ietf.org; Wed, 05 Jul 2006 08:12:55 -0400
Received: by nf-out-0910.google.com with SMTP id m19so1081203nfc
	for <mip6@ietf.org>; Wed, 05 Jul 2006 05:12:50 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=aqvHBzz5L2/wk7TSSq+5I3+ktr2TLI8hPpyKLPU610kMaAwykC7e5rmutNHTkTWpgjZsthSueTiBLG6Tyfrm9mbAF9wxSrVrdwthtoQINGKZBJJwV5QwmnLHD7BlZR/nNeqcH26IXeqjvepq5uGErFKo6dGXxsBnfPV4iLx6dCM=
Received: by 10.49.41.10 with SMTP id t10mr3888524nfj;
	Wed, 05 Jul 2006 05:12:50 -0700 (PDT)
Received: by 10.49.40.6 with HTTP; Wed, 5 Jul 2006 05:12:50 -0700 (PDT)
Message-ID: <eaa74a7e0607050512h6753ef1jb641f31d5fb1d001@mail.gmail.com>
Date: Wed, 5 Jul 2006 14:12:50 +0200
From: "Gerardo Giaretta" <gerardo.giaretta@gmail.com>
To: "Jari Arkko" <jari.arkko@kolumbus.fi>
Subject: Re: [Mip6] new charter proposal
In-Reply-To: <44AAAD5B.5010203@kolumbus.fi>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <44A82F67.6080105@kolumbus.fi>
	<eaa74a7e0607040838i3585c1e1y9520f2c9ac518f64@mail.gmail.com>
	<44AAAD5B.5010203@kolumbus.fi>
X-Spam-Score: -2.5 (--)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

> > In the charter proposal it is mentioned that the rationale behind
> > rfc4285 will be produced. Are we going to take a step forward and
> > specify bootstrapping mechanisms also for rfc4285?
>
> The design rationale was really a separate thing. The version
> of the charter that I posted does not include coverage of RFC
> 4285 in other ways.
>
> But its a good question what the scope of the bootstrapping
> work should be. What does the working group think? How
> did we define it in the problem statement?
>

The problem statement is mainly focused on IPsec SA between MN and HA.
Also some references to rfc4285 have been deleted during IESG
discussio based on Sam's comments.

> Ideally, I would not like to see that RFC 4285 causes divergent
> solutions for every other part of the technology along with it. Can
> we design our DHCP options and AAA interfaces so that they
> don't care whether its IKEv2 or authentication option at the
> bottom?
>

I guess yes. I think that at least HA discovery defined using DNS and
DHCP can be applied even in case rfc4285. Some more thoughts are
needed for HoA assignment, since so far it is specified for IKEv2, at
least in split scenario.

Obviously the way the SA is set up is different if either IPsec or
rfc4285 are used.

The question is: are the SDOs that have pushed for rfc4285 interested
in a bootstrapping solution developed in IETF?

--Gerardo

> --Jari
>
>

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



From mip6-bounces@ietf.org Wed Jul 05 08:57:49 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fy6wv-0003wS-NR; Wed, 05 Jul 2006 08:57:49 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fy6wt-0003wN-KQ
	for mip6@ietf.org; Wed, 05 Jul 2006 08:57:47 -0400
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fy6ws-0003gJ-Bl
	for mip6@ietf.org; Wed, 05 Jul 2006 08:57:47 -0400
Received: from p130.piuha.net (localhost [127.0.0.1])
	by p130.piuha.net (Postfix) with ESMTP id AA52B898A9;
	Wed,  5 Jul 2006 15:57:45 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id 6C2A98988E;
	Wed,  5 Jul 2006 15:57:45 +0300 (EEST)
Message-ID: <44ABB745.1090408@piuha.net>
Date: Wed, 05 Jul 2006 15:57:41 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Mozilla Thunderbird 1.0.8 (X11/20060502)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Gerardo Giaretta <gerardo.giaretta@gmail.com>
Subject: Re: [Mip6] new charter proposal
References: <44A82F67.6080105@kolumbus.fi>	
	<eaa74a7e0607040838i3585c1e1y9520f2c9ac518f64@mail.gmail.com>	
	<44AAAD5B.5010203@kolumbus.fi>
	<eaa74a7e0607050512h6753ef1jb641f31d5fb1d001@mail.gmail.com>
In-Reply-To: <eaa74a7e0607050512h6753ef1jb641f31d5fb1d001@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Gerardo Giaretta wrote:

> The question is: are the SDOs that have pushed for rfc4285 interested
> in a bootstrapping solution developed in IETF?

That is indeed a relevant question.

--Jari



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



From mip6-bounces@ietf.org Wed Jul 05 08:58:12 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fy6xI-00040H-4j; Wed, 05 Jul 2006 08:58:12 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fy6xH-00040B-4N
	for mip6@ietf.org; Wed, 05 Jul 2006 08:58:11 -0400
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fy6xF-0003lT-RT
	for mip6@ietf.org; Wed, 05 Jul 2006 08:58:11 -0400
Received: from il06exr01.mot.com (il06exr01.mot.com [129.188.137.131])
	by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id k65Cw54M010981
	for <mip6@ietf.org>; Wed, 5 Jul 2006 05:58:05 -0700 (MST)
Received: from ZMY16EXM66.ds.mot.com (zmy16exm66.ap.mot.com [10.179.4.26])
	by il06exr01.mot.com (8.13.5/8.13.0) with ESMTP id k65Cw3qB001223
	for <mip6@ietf.org>; Wed, 5 Jul 2006 07:58:04 -0500 (CDT)
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: [Mip6] new charter proposal
Date: Wed, 5 Jul 2006 20:58:03 +0800
Message-ID: <C82A9B11BE247C4E952DC733EA98DAA1016F8D4B@ZMY16EXM66.ds.mot.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] new charter proposal
Thread-Index: Acaflnx7ZNrxyp1eRS+p0Yfodr9LlgAlAD1A
From: "Ram O V Vishnu-A14676" <vishnu@motorola.com>
To: "Jari Arkko" <jari.arkko@kolumbus.fi>,
	"Gerardo Giaretta" <gerardo.giaretta@gmail.com>
X-Brightmail-Tracker: AAAAAQAAAAQ=
X-White-List-Member: TRUE
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi,

Sorry if I am interrupting a chain. Quick comments/questions:

<snip>
>But its a good question what the scope of the bootstrapping work should
be. What does the working group think? How >>did we define it in the
problem statement?

Vishnu> Yes, we think 4285 + bootstrapping is a good idea.=20

<snip>
>Ideally, I would not like to see that RFC 4285 causes divergent
solutions for every other part of the technology >along with it. Can we
design our DHCP options and AAA interfaces so that they don't care
whether its IKEv2 or >authentication option at the bottom?

Vishnu> In general its possible that the AAA interfaces be designed
agnostic of the south-side interfaces. But how does DHCP options come
into picture? Also, I guess, whether two different AAA client
applications (end-points) would need to use the same/similar interface
(towards AAA) is also a good question.

Regards,
Vishnu.

Motorola India Electronics Pvt Ltd
+91 9844178052
[*] General



-----Original Message-----
From: Jari Arkko [mailto:jari.arkko@kolumbus.fi]=20
Sent: Tuesday, July 04, 2006 11:33 PM
To: Gerardo Giaretta
Cc: Mobile IPv6 Mailing List
Subject: Re: [Mip6] new charter proposal


Hi Gerardo,

> thanks for providing the charter proposal. One question: is there any=20
> plan to produce docs on bootstrapping of rfc4285?
>
> In the charter proposal it is mentioned that the rationale behind=20
> rfc4285 will be produced. Are we going to take a step forward and=20
> specify bootstrapping mechanisms also for rfc4285?

The design rationale was really a separate thing. The version of the
charter that I posted does not include coverage of RFC 4285 in other
ways.

But its a good question what the scope of the bootstrapping work should
be. What does the working group think? How did we define it in the
problem statement?

Ideally, I would not like to see that RFC 4285 causes divergent
solutions for every other part of the technology along with it. Can we
design our DHCP options and AAA interfaces so that they don't care
whether its IKEv2 or authentication option at the bottom?

--Jari


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

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



From mip6-bounces@ietf.org Wed Jul 05 09:23:13 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fy7LT-00059N-UU; Wed, 05 Jul 2006 09:23:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fy7LS-00055G-Px
	for mip6@ietf.org; Wed, 05 Jul 2006 09:23:10 -0400
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fy7LS-0007bd-4l
	for mip6@ietf.org; Wed, 05 Jul 2006 09:23:10 -0400
Received: from p130.piuha.net (localhost [127.0.0.1])
	by p130.piuha.net (Postfix) with ESMTP id 3D6CA898A9;
	Wed,  5 Jul 2006 16:23:09 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id DFF3C8988E;
	Wed,  5 Jul 2006 16:23:08 +0300 (EEST)
Message-ID: <44ABBD38.80808@piuha.net>
Date: Wed, 05 Jul 2006 16:23:04 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Mozilla Thunderbird 1.0.8 (X11/20060502)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
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: 21bf7a2f1643ae0bf20c1e010766eb78
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>
Subject: [Mip6] AD review of draft-ietf-mip6-cn-ipsec
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Francis,

I have reviewed this document. Please find my comments and
questions below.

In general, the document is in reasonable shape for something
to be published as Experimental (my current assumption), but I
found a number of issues below that I'd like you to correct before
we can take the document further. This means one new revision.
Some of the comments probably need some discussion as well.

Here are the comments:

>    When a packet carrying a home address option is protected by a
>    suitable IPsec security association, the home address option SHOULD
>    be considered valid.

I think there should be a discussion somewhere (perhaps Section 2)
about the type of SA creation procedure and trust that is required
to make the above decision. See RFC 4449 Section 2 first two bullet
items for an example, and consider saying something about whether
this mechanism is applicable with BTNS or opportunistic IPsec.

The implications may also be different for triangular routing
and route optimization. It seems that all we need for triangular
routing is that the original address (the one that you send
traffic back to) was used in the IKE exchange. That is, a dynamic
SA is needed, but it can be of any type. For route optimization,
we'd like to know and trust the entity at the other end.

>    -  when an alternate care-of address option is present and is not
>       checked using the state cookie mechanism [cookie], the alternate
>       care-of address MUST match the source address in the IP header or
>       the home address itself.  Any binding update which does not
>       fulfill this requirement MUST be rejected.

This makes [cookie] a normative reference in my opinion. Is that
being published? If not, I would suggest deleting the part about it.

> In special circumstances where the home
>    address can be unusable, IKE MUST be run over a care-of address but
>    this has many known drawbacks:
>    -  a care-of address can not be used for authentication nor
>       authorization.
>    -  security associations do not survive handoffs.
>    -  the establishment of transport mode IPsec security association
>       using the home address as the mobile node traffic selector raises
>       a policy / authorization issue.

I agree with the above, but I worry what this implies. Can you document
what the special circumstances are? How is the policy / authorization
issue resolved?

> In binding updates the new requirements are:

I would like to understand what happens when the peers use RFC 3775
while at the same time for other reasons use IPsec between themselves,
and ONE (not both) support the mechanism specified here. How do they
know what they should do? Is there a missing negotiation step somewhere?

>    Note that
>    some operators can not propose Mobile IPv6 based services knowing
>    that the Mobile IPv6 security is based on assumptions.

:-)

If you can write a specific problem statement, please do. If not, leave
it out.

(The assumptions include, for instance, that on-path attackers can
disturb your communications. They can already do so without Mobile
IPv6, too...)

>    -  no care-of address test is required when ingress filtering can
>       reject fake care-of addresses from a rogue mobile node but a
>       correspondent node can use the return routability state cookie
>       procedure to get extra insurance as well as the support of real
>       alternate care-of addresses.

Ingress filtering helps only when it is deployed. But you already knew
that we have agreed to disagree on that point.

If you cut away the state cookie reference (as suggested earlier),
I would suggest that you include a statement similar to RFC 4449
about the trust needed to take care-of addresses without verifying
them.

>    When the home address is bound to a public key, for instance when the
>    home address is a Cryptographically Generated Addresses [RFC3972],
>    the strong authentication MAY be replaced by an address ownership
>    proof.  In this case the public key MAY be transported by IKE from
>    the mobile node to the correspondent node, for instance in a
>    Certificate payload of type 11 ([IKEv2] section 3.6).  Auxiliary
>    parameters MAY be transported in an Identification payload of type
>    ID_KEY_ID...

This would work, but I worry about the lack of details here. How would
the peers know they are using RFC 3972 to authenticate in IKE? How are
the CGA parameters transported? Suggestion: if we can not provide
full details, leave this part to another document.

>    -  in order to avoid granting any extra privilege by a side effect of
>       using IPsec, the peers (i.e., the mobile and correspondent nodes)
>       may restrict the traffic selectors to the protection of mobility
>       signaling only.  This should be applied to any dubious cases,
>       including by default when security administration is known to be
>       too light.

I am not sure I follow. Can the specific vulnerability be documented
here? Note: if you only include mobility signaling then triangular
routing is not possible. And it would be surprising if regular payload
traffic protected by IPsec would caused privilege elevation, assuming
the peers were OK with doing IPsec for their traffic. Is there some
vulnerability related to the use of Mobile IPv6 in this case?

>    But any stronger mechanism (i.e., more secure than the
>    return routability procedure) MAY be used, including of course IPsec
>    (cf. [RFC3775] Appendix 3 "New Authorization Methods").

I'm troubled by the "MAY" in this context. It does not appear
to be a direct quote from anywhere, and this document should
not grant rights to use "any" mechanism. It should state that
its defining a specific new mechanism, not anything about other
mechanisms.

>    mobility signaling for routing optimizations.  The configuration

maybe "... for route optimization" (there's just one kind).

>    This document uses the "MUST", "SHOULD", "MAY", ..., key words
>    according to [RFC2119].  IKE terminology is copied from IKEv2
>    [IKEv2].

Please use the standard template keyword statement:

      The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
      NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED",  "MAY", and
      "OPTIONAL" in this document are to be interpreted as described in
      RFC 2119.

>    send the packets via the home till a binding update is processed.

s/till/until/

>    Auxiliary
>    parameters MAY be transported in an Identification payload of type
>    ID_KEY_ID...

Too many dots.

--Jari


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



From mip6-bounces@ietf.org Wed Jul 05 09:31:35 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fy7Ta-00025D-Rm; Wed, 05 Jul 2006 09:31:34 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fy7TZ-000257-Jw
	for mip6@ietf.org; Wed, 05 Jul 2006 09:31:33 -0400
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fy7TX-0007nT-5o
	for mip6@ietf.org; Wed, 05 Jul 2006 09:31:33 -0400
Received: from p130.piuha.net (localhost [127.0.0.1])
	by p130.piuha.net (Postfix) with ESMTP id C0C64898A9;
	Wed,  5 Jul 2006 16:31:29 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id 8A3598988E;
	Wed,  5 Jul 2006 16:31:29 +0300 (EEST)
Message-ID: <44ABBF2D.2030509@piuha.net>
Date: Wed, 05 Jul 2006 16:31:25 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Mozilla Thunderbird 1.0.8 (X11/20060502)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Jean-Michel Combes <jeanmichel.combes@gmail.com>
Subject: Re: [Mip6] new charter proposal
References: <44A82F67.6080105@kolumbus.fi>
	<729b68be0607050439u4780a160r8356c034db39b04f@mail.gmail.com>
In-Reply-To: <729b68be0607050439u4780a160r8356c034db39b04f@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Jean-Michel Combes wrote:

> IMO, the draft-ietf-mip6-cn-ipsec should become Proposed Standard. The
> main reasons are :
> - No heavy modifications in the MIPv6 implementation (in fact, just to
> be able to desactivate the RR mechanism)
> - To have a mechanism that allows a strong security for RO

Thanks for the input.

(Just to explain my viewpoint:  What you say above is not by itself a
sufficient reason for a Proposed Standard designation. The standards
track series exists as IETF's recommendation of what protocols we
believe should be employed. This recommendation is not just about
the technical feasibility and properties of the solution. We also need
to think about how many features implementations will have. We
need to think about interoperability, practical configuration feasibility,
applicability to different situations, expectations of what gets really
deployed, etc. My evaluation of the situation is that this is an
interesting tool for some situations, certainly worth documenting,
but not quite general enough to be a PS. It is also substantially
easier to publish Experimental RFCs; if deployment experience
shows that its great we could easily revisit the standards
track designation decision later.)

--Jari


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



From mip6-bounces@ietf.org Wed Jul 05 09:59:19 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fy7uL-0005PU-Ku; Wed, 05 Jul 2006 09:59:13 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fy7uK-0005PN-7h
	for mip6@ietf.org; Wed, 05 Jul 2006 09:59:12 -0400
Received: from py-out-1112.google.com ([64.233.166.180])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fy7uH-0004Ps-W8
	for mip6@ietf.org; Wed, 05 Jul 2006 09:59:12 -0400
Received: by py-out-1112.google.com with SMTP id t32so2228742pyc
	for <mip6@ietf.org>; Wed, 05 Jul 2006 06:59:09 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=eP0X7woQA3Dd15niFTibZGWkLgp23+6ACXwrvn18r/MKFi4Ht4yMrF8gpFDFrTZfGgB3nn+NU7e5/IMgA+DHm1DWQFzL7x1wmHx276TxJAfjRAsLH36j9n8bWsoFO5hFD69FHyMaalcYoB45zShB1DlQrY5KZEQNEZkdksMeUN4=
Received: by 10.35.101.9 with SMTP id d9mr3289556pym;
	Wed, 05 Jul 2006 06:59:09 -0700 (PDT)
Received: by 10.35.111.9 with HTTP; Wed, 5 Jul 2006 06:59:09 -0700 (PDT)
Message-ID: <729b68be0607050659t49e705cbr9e8457905ebfa2eb@mail.gmail.com>
Date: Wed, 5 Jul 2006 15:59:09 +0200
From: "Jean-Michel Combes" <jeanmichel.combes@gmail.com>
To: "Jari Arkko" <jari.arkko@piuha.net>
Subject: Re: [Mip6] new charter proposal
In-Reply-To: <44ABBF2D.2030509@piuha.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <44A82F67.6080105@kolumbus.fi>
	<729b68be0607050439u4780a160r8356c034db39b04f@mail.gmail.com>
	<44ABBF2D.2030509@piuha.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi again,

2006/7/5, Jari Arkko <jari.arkko@piuha.net>:
> Jean-Michel Combes wrote:
>
> > IMO, the draft-ietf-mip6-cn-ipsec should become Proposed Standard. The
> > main reasons are :
> > - No heavy modifications in the MIPv6 implementation (in fact, just to
> > be able to desactivate the RR mechanism)
> > - To have a mechanism that allows a strong security for RO
>
> Thanks for the input.
>
> (Just to explain my viewpoint:  What you say above is not by itself a
> sufficient reason for a Proposed Standard designation. The standards
> track series exists as IETF's recommendation of what protocols we
> believe should be employed.

IMO, if an operator will want to deploy a MIPv6 based service allowing
RO, he will employ one with strong security especially if this
provided service is not free.
Indeed, like customer, will you accept to pay for a service knowing
that the operator will not be able to garantee the security?
Moreover, do you think that a operator will accept to sully its
reputation in providing a weak security based service?
Clearly, a strong security mechanism is needed and IETF has to recommend one.

> This recommendation is not just about
> the technical feasibility and properties of the solution. We also need
> to think about how many features implementations will have. We
> need to think about interoperability,

IPsec is mandatory in IPv6.

>  practical configuration feasibility,

IPsec/IKE are RFC and already implemented and used.

> applicability to different situations,

One MN and one CN can already set IPsec connexions between them after
the use of RR.

>  expectations of what gets really
> deployed,

I wrote above what is my feeling about deployment.

> etc. My evaluation of the situation is that this is an
> interesting tool for some situations, certainly worth documenting,
> but not quite general enough to be a PS. It is also substantially
> easier to publish Experimental RFCs; if deployment experience
> shows that its great we could easily revisit the standards
> track designation decision later.)

I hope you understand my point of view and my fears.

Thanks.

Best regards.

JMC.

>
> --Jari
>
>

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



From mip6-bounces@ietf.org Wed Jul 05 13:40:33 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FyBMT-0000Sn-Vr; Wed, 05 Jul 2006 13:40:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FyBMS-0000Sf-EW
	for mip6@ietf.org; Wed, 05 Jul 2006 13:40:28 -0400
Received: from [2001:660:7301:3192:211:43ff:fea3:7e4b]
	(helo=laposte.rennes.enst-bretagne.fr)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FyBMR-0005tH-5L
	for mip6@ietf.org; Wed, 05 Jul 2006 13:40:28 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by laposte.rennes.enst-bretagne.fr (8.13.4/8.13.4/2004.10.03) with
	ESMTP id k65HeD70002256; Wed, 5 Jul 2006 19:40:13 +0200
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[192.44.77.29])
	by laposte.rennes.enst-bretagne.fr (8.13.4/8.13.4/2004.09.01) with
	ESMTP id k65HeADa002252; Wed, 5 Jul 2006 19:40:10 +0200
Received: from givry.rennes.enst-bretagne.fr
	(localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.13.1/8.13.1) with ESMTP id
	k65HeA3a093061; Wed, 5 Jul 2006 19:40:10 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200607051740.k65HeA3a093061@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@point6.net>
To: Jari Arkko <jari.arkko@piuha.net>
In-reply-to: Your message of Wed, 05 Jul 2006 16:23:04 +0300.
	<44ABBD38.80808@piuha.net> 
Date: Wed, 05 Jul 2006 19:40:10 +0200
X-Virus-Scanned: amavisd-new at enst-bretagne.fr
X-Spam-Score: -2.8 (--)
X-Scan-Signature: f884eb1d4ec5a230688d7edc526ea665
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>
Subject: [Mip6] Re: AD review of draft-ietf-mip6-cn-ipsec 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Some short answers inline:

   In general, the document is in reasonable shape for something
   to be published as Experimental (my current assumption),

=> I completely disagree about the experimental. BTW I can't understand
why your arguments don't apply to RFC 4449 which is standard track.

   >    When a packet carrying a home address option is protected by a
   >    suitable IPsec security association, the home address option SHOULD
   >    be considered valid.
   
   I think there should be a discussion somewhere (perhaps Section 2)
   about the type of SA creation procedure and trust that is required

=> by "suitable" I mean an IPsec SA which provides the right thing,
for instance full origin authentication. The way it is established
and can be trusted is more an IKE issue, i.e., if you can establish
untrustable SAs you are in trouble with and without MIPv6.

   to make the above decision. See RFC 4449 Section 2 first two bullet
   items for an example,

=> these points are supposed to be already handled by IPsec.

   and consider saying something about whether
   this mechanism is applicable with BTNS or opportunistic IPsec.
   
=> opportunistic IPsec is supposed to be safe, BTNS is a problem
(this is why many people raise a concern about possible confusion
between BTNS and IPsec).

   The implications may also be different for triangular routing
   and route optimization. It seems that all we need for triangular
   routing is that the original address (the one that you send
   traffic back to) was used in the IKE exchange.

=> no, IKE uses strong mutual authentication and has nothing to do
with the return routability madness.

   That is, a dynamic SA is needed, but it can be of any type.

=> type? I can't see your idea.

   For route optimization,
   we'd like to know and trust the entity at the other end.
   
=> in general in IPsec, we'd like to know and trust the entity at
the other end...

   >    -  when an alternate care-of address option is present and is not
   >       checked using the state cookie mechanism [cookie], the alternate
   >       care-of address MUST match the source address in the IP header or
   >       the home address itself.  Any binding update which does not
   >       fulfill this requirement MUST be rejected.
   
   This makes [cookie] a normative reference in my opinion. Is that
   being published?

=> [cookie] is a good candidate for an experimental document. I am afraid
I am a bit late to refresh it but it will be possible next week...

   If not, I would suggest deleting the part about it.
   
=> I already moved many things from IPsec-CN to [cookie], I can finish
this (:-)...

   > In special circumstances where the home
   >    address can be unusable, IKE MUST be run over a care-of address but
   >    this has many known drawbacks:
   >    -  a care-of address can not be used for authentication nor
   >       authorization.
   >    -  security associations do not survive handoffs.
   >    -  the establishment of transport mode IPsec security association
   >       using the home address as the mobile node traffic selector raises
   >       a policy / authorization issue.
   
   I agree with the above, but I worry what this implies. Can you document
   what the special circumstances are?

=> when the home address is not routable (i.e., the home address is not
a real address).

   How is the policy / authorization issue resolved?

=> this policy / authorization issue is from RFC 2409:


   The identities of the SAs negotiated in Quick Mode are implicitly
   assumed to be the IP addresses of the ISAKMP peers, without any
   implied constraints on the protocol or port numbers allowed, unless
   client identifiers are specified in Quick Mode.  If ISAKMP is acting
   as a client negotiator on behalf of another party, the identities of
   the parties MUST be passed as IDci and then IDcr.  Local policy will
   dictate whether the proposals are acceptable for the identities
   specified.

So the solution is an explicit setup to get at least ownership of
the home address. Of course the usual way, put it in a SubjectAltName
of the MN certificate, is only half of the solution because one could
like to check if the address is the one IKE runs over, and it is not
the case... My intention here is to raise the point but to given
the burden to solve it to the special circumstances mechanisms.
   
   > In binding updates the new requirements are:
   
   I would like to understand what happens when the peers use RFC 3775
   while at the same time for other reasons use IPsec between themselves,
   and ONE (not both) support the mechanism specified here. How do they
   know what they should do?

=> if the MN doesn't support it, it'll just loose a faster and stronger
way to do RO. If the CN doesn't support it, it'll reject the BU. There
is no ambiguous error case. BTW I am afraid there can be a bidding down
attack...

   Is there a missing negotiation step somewhere?
   
=> There is no standardized way to manage IPsec polices and what one
can do with IPsec SAs is IMHO exactly in the scope of IPsec policies.

   >    Note that
   >    some operators can not propose Mobile IPv6 based services knowing
   >    that the Mobile IPv6 security is based on assumptions.
   
=> I leave this to my co-author who is an employee of an operator
which has this position.
   
   >    -  no care-of address test is required when ingress filtering can
   >       reject fake care-of addresses from a rogue mobile node but a
   >       correspondent node can use the return routability state cookie
   >       procedure to get extra insurance as well as the support of real
   >       alternate care-of addresses.
   
   Ingress filtering helps only when it is deployed. But you already knew
   that we have agreed to disagree on that point.
   
=> it seems you are trying to read between the lines.

   If you cut away the state cookie reference (as suggested earlier),

=> IMHO it (the state cookie stuff) is an useful mechanism when
there is no care-of address test and someone wants a return routability
check. So I prefer to find a way to keep it.

   >    When the home address is bound to a public key, for instance when the
   >    home address is a Cryptographically Generated Addresses [RFC3972],
   >    the strong authentication MAY be replaced by an address ownership
   >    proof.  In this case the public key MAY be transported by IKE from
   >    the mobile node to the correspondent node, for instance in a
   >    Certificate payload of type 11 ([IKEv2] section 3.6).  Auxiliary
   >    parameters MAY be transported in an Identification payload of type
   >    ID_KEY_ID...
   
   This would work, but I worry about the lack of details here. How would
   the peers know they are using RFC 3972 to authenticate in IKE?

=> because it is in the PAD (RFC 4301 section 4.4.3).

   How are the CGA parameters transported?

=> ID_KEY_ID (RFC 4306 section 3.5):
            An opaque octet stream which may be used to pass vendor-
            specific information necessary to do certain proprietary
            types of identification.

   Suggestion: if we can not provide
   full details, leave this part to another document.
   
=> what I propose works, it is just not the only way to do it.

   >    -  in order to avoid granting any extra privilege by a side effect of
   >       using IPsec, the peers (i.e., the mobile and correspondent nodes)
   >       may restrict the traffic selectors to the protection of mobility
   >       signaling only.  This should be applied to any dubious cases,
   >       including by default when security administration is known to be
   >       too light.
   
   I am not sure I follow. Can the specific vulnerability be documented
   here?

=> as it is written: you grant the authorization to use IPsec to protect
mobility and someone tries to apply IPsec to something else. And
the solution is to constraint the scope.

   Note: if you only include mobility signaling then triangular
   routing is not possible.

=> yes and this is a good example of the vulnerability: you try to
authorize the triangular routing for a traffic and by a side effect
you give unexpected/unwanted security property to this traffic.

   And it would be surprising if regular payload
   traffic protected by IPsec would caused privilege elevation, assuming
   the peers were OK with doing IPsec for their traffic.

=> no, the problem is when they are OK with doing IPsec for mobility
and IPsec is spread to the traffic itself.

   Is there some
   vulnerability related to the use of Mobile IPv6 in this case?
   
=> there is possible pitfall in the policy configuration so IMHO
we had to document it.

   >    But any stronger mechanism (i.e., more secure than the
   >    return routability procedure) MAY be used, including of course IPsec
   >    (cf. [RFC3775] Appendix 3 "New Authorization Methods").
   
   I'm troubled by the "MAY" in this context. It does not appear
   to be a direct quote from anywhere, and this document should

=> the Appendixes are not normative so they don't include uppercase
keywords even the text is pretty clear. Is it your concern?

   not grant rights to use "any" mechanism. It should state that
   its defining a specific new mechanism, not anything about other
   mechanisms.
   
Regards
   
Francis.Dupont@point6.net

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



From mip6-bounces@ietf.org Wed Jul 05 14:04:18 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FyBjV-0002Jf-5k; Wed, 05 Jul 2006 14:04:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FyBjT-0002Hh-Ml
	for mip6@ietf.org; Wed, 05 Jul 2006 14:04:15 -0400
Received: from mgw-ext14.nokia.com ([131.228.20.173])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FyBjT-0007lQ-2x
	for mip6@ietf.org; Wed, 05 Jul 2006 14:04:15 -0400
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145])
	by mgw-ext14.nokia.com (Switch-3.1.8/Switch-3.1.7) with ESMTP id
	k65I4Br6021939; Wed, 5 Jul 2006 21:04:14 +0300
Received: from esebh002.NOE.Nokia.com ([172.21.138.77]) by
	esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 5 Jul 2006 21:04:08 +0300
Received: from [172.18.141.192] ([172.18.141.192]) by esebh002.NOE.Nokia.com
	with Microsoft SMTPSVC(5.0.2195.6881); 
	Wed, 5 Jul 2006 21:04:08 +0300
Message-ID: <44ABFF17.90508@iprg.nokia.com>
Date: Wed, 05 Jul 2006 11:04:07 -0700
From: Rajeev Koodli <rajeev@iprg.nokia.com>
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@kolumbus.fi>
Subject: Re: [Mip6] some comments on draft-ietf-mip6-location-privacy-ps
References: <44A82617.9060400@kolumbus.fi>
In-Reply-To: <44A82617.9060400@kolumbus.fi>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 05 Jul 2006 18:04:08.0542 (UTC)
	FILETIME=[6948CFE0:01C6A05D]
X-Spam-Score: 1.1 (+)
X-Scan-Signature: 88b11fc64c1bfdb4425294ef5374ca07
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>,
	Rajeev Koodli <rajeev.koodli@nokia.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org


Hi Jari,

Jari Arkko wrote:

>Suggested rewrite:
>
>   This document is only concerned with IP address location privacy in
>   the context of Mobile IPv6.  It does not address the overall privacy
>   problem. For instance, it does not address privacy issues related to
>   MAC addresses or the relationship of IP and MAC addresses [1].
>
>  
>
Okay.

>>   Location privacy may be compromised if an on-looker is present on
>>   the MN - HA path (when bidirectional tunneling is used), or when the
>>   on-looker is present on the MN and CN path (when route optimization
>>   is used).
>>    
>>
>
>This needs to be explained in more detail. From what I can see,
>location privacy is always revealed on the mn-ha path, given the
>location of the various options and headers in the binding updates.
>You should also talk about the effect or lack thereof of applying
>ESP with encryption.
>
>  
>
I would like to be clear about one thing. We are dealing primarily with 
HoA and CoA revealing
here. These are the "identifiers" whose disclosure leads to compromise 
in location privacy. The
other parameters by themselves are either not enough to compromise 
location privacy or are essentially
the same as the general "profiling" problem.

So, on the MN-HA path, if the HoA is revealed, yes, that would lead to a 
compromise in location
privacy.

The other thing I would like to mention is that the specifics of use of 
ESP etc are solutions. I am
hoping to produce a crisp problem statement document.

>> Whenever it is involved
>>   in IP communication, its correspondents can see an IP address valid
>>   on the home network.  Elaborating further, the users involved in peer
>>   - peer communication are likely to see a user-friendly identifier
>>   such as a SIP URI, and the communication end-points in the IP
>>   stack will see IP addresses.  Users uninterested in or unaware of
>>   IP communication details will not see any difference when the MN
>>   acquires a new IP address.  Of course any user can ``tcpdump'' or
>>   ``ethereal'' a session, capture IP packets and map the MN's IP
>>   address to an approximate geo-location.  When this mapping reveals a
>>   ``home location'' of the user, the correspondent can conclude that
>>   the user has not roamed.
>>    
>>
>
>This does not appear to follow. Assuming there's bidirectional tunneling
>going on, the user is unaware of possible roaming.
>
>  
>
This paragraph is about the user being at home though.."Consider a 
Mobile Node at its home network..."

It's only saying that a user has to be able to actually see the IP 
address beyond the user
identifier (such as a SIP URI) and map that IP address a geo-location to 
know where the user is.

>>   The above description is valid regardless of whether a Home Address
>>   is static or is dynamically allocated. 
>>    
>>
>
>Hmm... this seems to need more explanation or perhaps a more in-depth
>treatment. Getting a dynamically allocated home address is similar to
>running RFC 3041. If you do that, and employ different care-of addresses
>for your different communications, it seems that you will be able
>provide better location privacy protection, no?
>
>  
>
The sentence above ("The above description is valid ..") is used in the 
context of the rest of the
section. It is saying that the granularity of mapping the HoA (either 
dynamically assigned or statically
assigned) to a geo-location is almost the same (which is stated in the 
sentence that follows the above
sentence). This is because the network prefix maps to the same physical 
location.

It's the same thing with 3041. When you combine that with different 
CoAs, it does not change the
problem fundamentally; it's perhaps one way to deal with the problem. 
The basic problem is:

- revealing HoA with global scope, no matter how it is assigned, to an 
on-looker compromises
  location privacy.
- revealing CoA together with HoA reveals to a CN that the MN has 
roamed. Does not matter
  how they are assigned.

>>   Finally, it is also worthwhile to note that both the Home Address
>>   and the Care of Address could be subject to profiling, just as
>>   any other user traffic.  However, applying existing techniques to
>>   thwart profiling may have implications to Mobile IPv6 signaling
>>   performance.  For instance, changing the Care of Address often would
>>   cause additional Return Routability and binding management signaling.
>>   And, changing the Home Address often has implications on IPSec
>>   security association management.  These issues need to be addressed
>>   in the solutions.
>>    
>>
>
>Need to be? Perhaps the conclusion is a bit too quick. Changing
>care of addresses "often" for privacy reasons would probably be
>either much less often that a fast moving mobile node makes handovers,
>or at least fairly infrequent, so is there need for optimizing the process?
>
>  
>
Ah, if the CoA change does not happen often, there is nothing to do. 
Agree that there is no need
to optimize the process. The intention was to note the cost of changing 
the CoA and HoA.
How about the reword of the last sentence:

"Solutions should be careful in considering the cost of change of either 
CoA or HoA on signaling.
For instance, changing the Care of Address often would cause additional 
Return Routability and
binding management signaling. And, changing the Home Address often has 
implications on IPsec
 security association management. These issues need to be addressed in 
the solutions."

>The specific issue with IPsec SA management probably needs to
>be spelled out too. For instance, if you used the same IKE SA for
>everything, it would be kind of silly to worry about privacy. So
>that implies multiple IKE SAs.
>
>  
>
Would you consider this a "profiling" problem or "location privacy" 
problem?

>> IPSec
>>    
>>
>
>IPsec
>
>  
>
noted.

>Missing stuff: I would have expected a good summary of conditions under
>which location privacy is not a problem and a set of recommendations
>on how networks and policies should be set up to prevent location
>disclosure.
>
>  
>
The recommendation is what I am hoping the solutions draft will provide.
Compared to privacy at large, Mobile IP introduces a specific problem 
due to the use of HoA and CoA.
When a global identifier such as HoA is used from visited networks, 
on-lookers can figure out
roaming. When HoA is used in conjunction with CoA, a CN can figure out 
that the MN has
roamed. This specific problem is what this ID is trying to specify.

I see the above problem existing wherever Mobile IP is supported 
regardless of network
conditions. We can issue guidelines such as "use ESP in reverse 
tunneling to hide HoA", and that's
what I am hoping to have in the solutions document (which will also 
address route optimization's
implications).

Thanks for your input.

-Rajeev


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


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



From mip6-bounces@ietf.org Wed Jul 05 14:06:13 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FyBlN-0004uk-TE; Wed, 05 Jul 2006 14:06:13 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FyBlM-0004oH-Nf
	for mip6@ietf.org; Wed, 05 Jul 2006 14:06:12 -0400
Received: from mgw-ext12.nokia.com ([131.228.20.171])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FyBlL-0007nm-AY
	for mip6@ietf.org; Wed, 05 Jul 2006 14:06:12 -0400
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211])
	by mgw-ext12.nokia.com (Switch-3.1.8/Switch-3.1.7) with ESMTP id
	k65I63JW005395; Wed, 5 Jul 2006 21:06:07 +0300
Received: from esebh002.NOE.Nokia.com ([172.21.138.77]) by
	esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 5 Jul 2006 21:06:06 +0300
Received: from [172.18.141.192] ([172.18.141.192]) by esebh002.NOE.Nokia.com
	with Microsoft SMTPSVC(5.0.2195.6881); 
	Wed, 5 Jul 2006 21:06:05 +0300
Message-ID: <44ABFF8D.9080007@iprg.nokia.com>
Date: Wed, 05 Jul 2006 11:06:05 -0700
From: Rajeev Koodli <rajeev@iprg.nokia.com>
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@kolumbus.fi>
Subject: Re: [Mip6] new charter proposal
References: <44A82F67.6080105@kolumbus.fi>
In-Reply-To: <44A82F67.6080105@kolumbus.fi>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 05 Jul 2006 18:06:06.0153 (UTC)
	FILETIME=[AF62D390:01C6A05D]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: Gopal Dommety <gdommety@cisco.com>,
	Mobile IPv6 Mailing List <mip6@ietf.org>,
	Basavaraj Patil <basavaraj.patil@nokia.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org


Hi Jari,

Jari Arkko wrote:

>Nov 2006    Submit I-D 'Address Location Privacy and Mobile IPv6 Problem
>        Statement' to IESG for publication as Informational.
>
>  
>
The ID went through WG LC; I have incorporated the comments.
I think we can send this to IESG by September (taking remaining 
discussion into
consideration).

-Rajeev



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



From mip6-bounces@ietf.org Wed Jul 05 15:39:00 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FyDD6-0005No-TB; Wed, 05 Jul 2006 15:38:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FyDD5-0005Mf-LY
	for mip6@ietf.org; Wed, 05 Jul 2006 15:38:55 -0400
Received: from mail1.azairenet.com ([66.92.223.4] helo=bart.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FyDD4-0004Dz-BM
	for mip6@ietf.org; Wed, 05 Jul 2006 15:38:55 -0400
Received: from [10.1.210.17] ([10.1.210.17]) by bart.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Wed, 5 Jul 2006 12:38:52 -0700
Message-ID: <44AC1547.5030404@azairenet.com>
Date: Wed, 05 Jul 2006 12:38:47 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.4 (Windows/20060516)
MIME-Version: 1.0
To: "Soliman, Hesham" <hsoliman@qualcomm.com>
Subject: Re: [Mip6] new charter proposal
References: <7EB20EA0938B4D42A2D82689365C9B7A07CE58@NAEX14.na.qualcomm.com>
In-Reply-To: <7EB20EA0938B4D42A2D82689365C9B7A07CE58@NAEX14.na.qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 05 Jul 2006 19:38:52.0563 (UTC)
	FILETIME=[A5399630:01C6A06A]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Soliman, Hesham wrote:
> 
>  > >http://www.ietf.org/internet-drafts/draft-ietf-mip6-dsmip-pr
> oblem-02.txt
>  > >
>  > >It's in the current charter. Is this covered under the DSMIP work
>  > >anyway?
>  > >  
>  > >
>  > Good question. I wouldn't mind having a problem statement document
>  > too if the group wants that. Question: there's a brief description of
>  > the problem/motivation/scope/scenarios in the beginning of the
>  > solution draft. Is that insufficient?
> 
> => Depends on who you ask :). Given the amount of questions that we
> continue to get about the problem and why this is needed I would think
> it's insufficient. I think this will be a good document to point people
> to when these issues come up. Thomas just asked for the same thing
> recently on the list. So I think it's helpful to have it. 

there is an issue here. I understand MIPv6 WG working on
a problem statement to justify DS-MIPv6. but I don't see
the point in MIPv6 WG justifying the need for DS-MIPv4.
perhaps the problem statement for DS-MIPv4 should be done
in the MIP4 WG (if at all MIP4 WG does DS-MIPv4).

Vijay

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


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



From mip6-bounces@ietf.org Wed Jul 05 16:40:26 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FyEAS-0002Um-Vi; Wed, 05 Jul 2006 16:40:16 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FyEAR-0002Uh-TX
	for mip6@ietf.org; Wed, 05 Jul 2006 16:40:15 -0400
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FyEAQ-0002sN-KG
	for mip6@ietf.org; Wed, 05 Jul 2006 16:40:15 -0400
Received: from p130.piuha.net (localhost [127.0.0.1])
	by p130.piuha.net (Postfix) with ESMTP id E853D898A9;
	Wed,  5 Jul 2006 23:40:13 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id 9E6328986D;
	Wed,  5 Jul 2006 23:40:13 +0300 (EEST)
Message-ID: <44AC23A9.9030508@piuha.net>
Date: Wed, 05 Jul 2006 23:40:09 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Mozilla Thunderbird 1.0.8 (X11/20060502)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Rajeev Koodli <rajeev@iprg.nokia.com>
Subject: Re: [Mip6] new charter proposal
References: <44A82F67.6080105@kolumbus.fi> <44ABFF8D.9080007@iprg.nokia.com>
In-Reply-To: <44ABFF8D.9080007@iprg.nokia.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: 68c8cc8a64a9d0402e43b8eee9fc4199
Cc: Gopal Dommety <gdommety@cisco.com>,
	Mobile IPv6 Mailing List <mip6@ietf.org>,
	Basavaraj Patil <basavaraj.patil@nokia.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Rajeev Koodli wrote:

> The ID went through WG LC; I have incorporated the comments.
> I think we can send this to IESG by September (taking remaining
> discussion into
> consideration).

Ok.

--Jari



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



From mip6-bounces@ietf.org Wed Jul 05 17:07:59 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FyEbG-0004Mu-Fz; Wed, 05 Jul 2006 17:07:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FyEbF-0004Mp-K3
	for mip6@ietf.org; Wed, 05 Jul 2006 17:07:57 -0400
Received: from [2001:660:7301:3192:211:43ff:fea3:7e4b]
	(helo=laposte.rennes.enst-bretagne.fr)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FyEbE-0005ug-3Q
	for mip6@ietf.org; Wed, 05 Jul 2006 17:07:57 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by laposte.rennes.enst-bretagne.fr (8.13.4/8.13.4/2004.10.03) with
	ESMTP id k65L7q11014011; Wed, 5 Jul 2006 23:07:52 +0200
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[192.44.77.29])
	by laposte.rennes.enst-bretagne.fr (8.13.4/8.13.4/2004.09.01) with
	ESMTP id k65L7nZG013998; Wed, 5 Jul 2006 23:07:49 +0200
Received: from givry.rennes.enst-bretagne.fr
	(localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.13.1/8.13.1) with ESMTP id
	k65L7l5V093536; Wed, 5 Jul 2006 23:07:47 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200607052107.k65L7l5V093536@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@point6.net>
To: "Jean-Michel Combes" <jeanmichel.combes@gmail.com>
Subject: Re: [Mip6] new charter proposal 
In-reply-to: Your message of Wed, 05 Jul 2006 15:59:09 +0200.
	<729b68be0607050659t49e705cbr9e8457905ebfa2eb@mail.gmail.com> 
Date: Wed, 05 Jul 2006 23:07:47 +0200
X-Virus-Scanned: amavisd-new at enst-bretagne.fr
X-Spam-Score: -2.8 (--)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   > We need to think about interoperability, ...

=> BTW I implemented it (as the main part was to adapt the MIPv6 MN
automaton to alternative to RR it should be easy to port to IKEv2 /
racoon2).

Regards

Francis.Dupont@point6.net

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



From mip6-bounces@ietf.org Wed Jul 05 17:53:27 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FyFJE-0002fz-NU; Wed, 05 Jul 2006 17:53:24 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FyFJD-0002bD-GH
	for mip6@ietf.org; Wed, 05 Jul 2006 17:53:23 -0400
Received: from [2001:660:7301:3192:211:43ff:fea3:7e4b]
	(helo=laposte.rennes.enst-bretagne.fr)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FyFJC-00023J-CI
	for mip6@ietf.org; Wed, 05 Jul 2006 17:53:23 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by laposte.rennes.enst-bretagne.fr (8.13.4/8.13.4/2004.10.03) with
	ESMTP id k65LrLxC017568; Wed, 5 Jul 2006 23:53:21 +0200
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[192.44.77.29])
	by laposte.rennes.enst-bretagne.fr (8.13.4/8.13.4/2004.09.01) with
	ESMTP id k65LrI2C017564; Wed, 5 Jul 2006 23:53:18 +0200
Received: from givry.rennes.enst-bretagne.fr
	(localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.13.1/8.13.1) with ESMTP id
	k65LrEdM093651; Wed, 5 Jul 2006 23:53:14 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200607052153.k65LrEdM093651@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@point6.net>
To: Jari Arkko <jari.arkko@piuha.net>
In-reply-to: Your message of Wed, 05 Jul 2006 16:23:04 +0300.
	<44ABBD38.80808@piuha.net> 
Date: Wed, 05 Jul 2006 23:53:14 +0200
X-Virus-Scanned: amavisd-new at enst-bretagne.fr
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>
Subject: [Mip6] Re: AD review of draft-ietf-mip6-cn-ipsec 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Short second/higher level pass...

   Francis,
   
=> we are two authors (:-)...

A general comment: the idea is to take benefit of IPsec when IPsec
is already available, i.e., for many reasons IPsec should not be pushed
only to protect mobility. As RFC 4449, in special cases an alternative
to RO is used, in fact IMHO RFC 4449 and IPsec-CN are two faces of
the same concept so I don't understand why they should receive a very
different consideration...
To finish the main security concern against RO is MN impersonization
and solutions based on strong authentications will be always far
more secure than RR...
   
   (The assumptions include, for instance, that on-path attackers can
   disturb your communications. They can already do so without Mobile
   IPv6, too...)
   
=> no, impersonation by an attacker at the right place in the path(s)
is a real (and first order) issue. The RR was proposed because there
is no general solution to this problem but you can't assume than
the limits of RO about security are acceptable by everybody.
So we have an explicit alternate mechanism (RFC 4449), another one
using the standard network layer security (CN-IPsec) and perhaps
will get something from the CGA & co stuff. BTW this was known at
the RFC 3775 time so provisions were made for further (at that time)
work...

   >    -  no care-of address test is required when ingress filtering can

=> note that ingress filtering and return routability check are two
versions of the same mechanism, in particular both share the same
limit (no defense against an attacker at the right place in the path)
The main difference is that ingress filtering is passive, which is better
when you can trust it is used at the right place, when RR is active,
so more expensive but doesn't rely on someone else's policy.
BTW in my new job we use labelization which makes ingress filtering
seems like a toy (:-)...
To finish the lack of ingress filtering general deployment is a major
(i.e., first order) threat against the Internet itself, so it is a minor
(i.e., second order) threat against mobility.

   >      as well as the support of real alternate care-of addresses.

=> this is the real reason I introduced the state cookie RR: at the
beginning I simply forbid real alternate care-ofs but it was not
very clear if they would be never needed...
To use it when it is not required is a concession to the indirect
flooding attack paranoia so I don't understand why you'd like to
reject it (or it is for a formal concern?)
   
   If you cut away the state cookie reference (as suggested earlier),
   I would suggest that you include a statement similar to RFC 4449
   about the trust needed to take care-of addresses without verifying
   them.
   
=> I don't like the RFC 4449 to deal with the problem... My idea is
to provide an easy tool to perform the RR test when the CN believes
there can be a problem, i.e., not when ingress filtering is deployed,
not when the MN can be trusted, etc, i.e., not only the check is at
the initiative of the CN but the CN can choose its default policy.

   This would work, but I worry about the lack of details here. How would
   the peers know they are using RFC 3972 to authenticate in IKE? How are
   the CGA parameters transported? Suggestion: if we can not provide
   full details, leave this part to another document.
   
=> suggestion: move it to a not normative appendix?

   >    -  in order to avoid granting any extra privilege by a side effect of
   >       using IPsec

=> two extra comments:
 - I've already seen cases where "there is IPsec" was changed into
 "now everything is safe so may be done", i.e., the pitfall is real.
 - a good security admin should understand the issue and just avoid
 IPsec for the only protection of mobility (i.e., as I've explained
 in the introduction of this message, the protection of IPsec is
 not enough as a reason to jump to IPsec).
   
   >    But any stronger mechanism (i.e., more secure than the
   >    return routability procedure) MAY be used, including of course IPsec
   >    (cf. [RFC3775] Appendix 3 "New Authorization Methods").
   
=> I'll put a *may* to stress it without interfering with keywords.
   
   >    This document uses the "MUST", "SHOULD", "MAY", ..., key words
   >    according to [RFC2119].  IKE terminology is copied from IKEv2
   >    [IKEv2].
   
   Please use the standard template keyword statement:
   
=> if the standard template is required it should be a macro in xml2rfc!

Regards
   
Francis.Dupont@point6.net

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



From mip6-bounces@ietf.org Wed Jul 05 17:59:34 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FyFPC-0006m1-Ec; Wed, 05 Jul 2006 17:59:34 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FyFPB-0006lw-IJ
	for mip6@ietf.org; Wed, 05 Jul 2006 17:59:33 -0400
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FyFPA-0002kY-9R
	for mip6@ietf.org; Wed, 05 Jul 2006 17:59:33 -0400
Received: from p130.piuha.net (localhost [127.0.0.1])
	by p130.piuha.net (Postfix) with ESMTP id 20A44898A9;
	Thu,  6 Jul 2006 00:59:31 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id D64C28986D;
	Thu,  6 Jul 2006 00:59:30 +0300 (EEST)
Message-ID: <44AC363E.4030604@piuha.net>
Date: Thu, 06 Jul 2006 00:59:26 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Mozilla Thunderbird 1.0.8 (X11/20060502)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Francis Dupont <Francis.Dupont@point6.net>
References: <200607051740.k65HeA3a093061@givry.rennes.enst-bretagne.fr>
In-Reply-To: <200607051740.k65HeA3a093061@givry.rennes.enst-bretagne.fr>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>
Subject: [Mip6] Re: AD review of draft-ietf-mip6-cn-ipsec
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Francis,

>=> BTW I can't understand
>why your arguments don't apply to RFC 4449 which is standard track.
>  
>
FWIW, the arguments would have applied to RFC 4449 too
had it been my call, but it wasn't.

--Jari


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



From mip6-bounces@ietf.org Wed Jul 05 18:57:26 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FyGJ8-0003fq-97; Wed, 05 Jul 2006 18:57:22 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FyGJ6-0003fl-Ul
	for mip6@ietf.org; Wed, 05 Jul 2006 18:57:20 -0400
Received: from mail1.azairenet.com ([66.92.223.4] helo=bart.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FyGJ5-0000Py-K4
	for mip6@ietf.org; Wed, 05 Jul 2006 18:57:20 -0400
Received: from [10.1.201.28] ([10.1.201.28]) by bart.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Wed, 5 Jul 2006 15:57:15 -0700
Message-ID: <44AC43CA.9000607@azairenet.com>
Date: Wed, 05 Jul 2006 15:57:14 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.4 (Windows/20060516)
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>
Subject: Re: [Mip6] new charter proposal
References: <44A82F67.6080105@kolumbus.fi>		<eaa74a7e0607040838i3585c1e1y9520f2c9ac518f64@mail.gmail.com>		<44AAAD5B.5010203@kolumbus.fi>	<eaa74a7e0607050512h6753ef1jb641f31d5fb1d001@mail.gmail.com>
	<44ABB745.1090408@piuha.net>
In-Reply-To: <44ABB745.1090408@piuha.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 05 Jul 2006 22:57:15.0702 (UTC)
	FILETIME=[5C0C7560:01C6A086]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Jari Arkko wrote:
> Gerardo Giaretta wrote:
> 
>> The question is: are the SDOs that have pushed for rfc4285 interested
>> in a bootstrapping solution developed in IETF?
> 
> That is indeed a relevant question.

I saw a bunch of hacks in SDOs like 3GPP2 and Wimax that
are adopting RFC 4285. that was one of the reasons, I
wrote up
http://www.ietf.org/internet-drafts/draft-devarapalli-mip6-authprotocol-bootstrap-01.txt
this will work with both DNS and DHCP based HA discovery.
it mainly describes HoA configuration and SA setup.

personally, I think IKEv2 and IPsec should be used for
MIPv6 (I spent some effort in advocating this in 3GPP2).
but since the SDOs seem to prefer RFC 4285, I would
rather have them use a bootstrapping solution for RFC
4285 that is standardized in the IETF.

also I think SDOs sometimes try to avoid creating an
IETF dependency for obvious reasons. :)

Vijay

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



From mip6-bounces@ietf.org Wed Jul 05 19:34:40 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FyGtE-00082x-1m; Wed, 05 Jul 2006 19:34:40 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FyGtC-0007z3-Ov
	for mip6@ietf.org; Wed, 05 Jul 2006 19:34:38 -0400
Received: from mail1.azairenet.com ([66.92.223.4] helo=bart.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FyGtB-0004R7-9k
	for mip6@ietf.org; Wed, 05 Jul 2006 19:34:38 -0400
Received: from [10.1.201.28] ([10.1.201.28]) by bart.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Wed, 5 Jul 2006 16:34:32 -0700
Message-ID: <44AC4C85.70109@azairenet.com>
Date: Wed, 05 Jul 2006 16:34:29 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.4 (Windows/20060516)
MIME-Version: 1.0
To: Jean-Michel Combes <jeanmichel.combes@gmail.com>
Subject: Re: [Mip6] new charter proposal
References: <44A82F67.6080105@kolumbus.fi>
	<729b68be0607050439u4780a160r8356c034db39b04f@mail.gmail.com>
In-Reply-To: <729b68be0607050439u4780a160r8356c034db39b04f@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 05 Jul 2006 23:34:32.0091 (UTC)
	FILETIME=[910A56B0:01C6A08B]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Cc: Gopal Dommety <gdommety@cisco.com>, Jari Arkko <jari.arkko@kolumbus.fi>,
	Basavaraj Patil <basavaraj.patil@nokia.com>,
	Mobile IPv6 Mailing List <mip6@ietf.org>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Jean-Michel Combes wrote:

> IMO, the draft-ietf-mip6-cn-ipsec should become Proposed Standard. The
> main reasons are :
> - No heavy modifications in the MIPv6 implementation (in fact, just to
> be able to desactivate the RR mechanism)
> - To have a mechanism that allows a strong security for RO

if this were possible, we would have had MIPv6 standardized back
in 2000-2001. I remember Jeff Schiller blasting us in December
2000 for assuming trust between the MN and the CN to be out of
scope. this is exactly what draft-ietf-mip6-cn-ipsec assumes.

then we had to design the return routability mechanism.

Vijay

> 
> Thanks.
> 
> Best regards.
> 
> JMC.
> 
>> But I'll listen to the group's
>> input on this too.
>>
>> --Jari
>>
>>
>> _______________________________________________
>> Mip6 mailing list
>> Mip6@ietf.org
>> https://www1.ietf.org/mailman/listinfo/mip6
>>
> 
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6


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



From mip6-bounces@ietf.org Wed Jul 05 19:58:19 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FyHFy-00007d-2I; Wed, 05 Jul 2006 19:58:10 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FyHFx-00007T-My
	for mip6@ietf.org; Wed, 05 Jul 2006 19:58:09 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FyGKr-0000Rs-B7
	for mip6@ietf.org; Wed, 05 Jul 2006 18:59:09 -0400
Received: from mail1.azairenet.com ([66.92.223.4] helo=bart.corp.azairenet.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1FyGAa-0000Na-R0
	for mip6@ietf.org; Wed, 05 Jul 2006 18:48:34 -0400
Received: from [10.1.201.28] ([10.1.201.28]) by bart.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Wed, 5 Jul 2006 15:48:24 -0700
Message-ID: <44AC41AB.2080003@azairenet.com>
Date: Wed, 05 Jul 2006 15:48:11 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.4 (Windows/20060516)
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>
Subject: Re: [Mip6] new charter proposal
References: <7EB20EA0938B4D42A2D82689365C9B7A07CE55@NAEX14.na.qualcomm.com>
	<44ABB053.6010809@piuha.net>
In-Reply-To: <44ABB053.6010809@piuha.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 05 Jul 2006 22:48:24.0918 (UTC)
	FILETIME=[1FAD3F60:01C6A085]
X-Spam-Score: -2.1 (--)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>, "Soliman,
	Hesham" <hsoliman@qualcomm.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Jari Arkko wrote:
> Soliman, Hesham wrote:
> 
>> Hi Jari, 
>>
>> I didn't see a specific mention of:
>>
>> http://www.ietf.org/internet-drafts/draft-ietf-mip6-dsmip-problem-02.txt
>>
>> It's in the current charter. Is this covered under the DSMIP work
>> anyway?
>>  
>>
> Good question. I wouldn't mind having a problem statement document
> too if the group wants that. Question: there's a brief description of
> the problem/motivation/scope/scenarios in the beginning of the
> solution draft. Is that insufficient?

FWIW, I think the problem description in
draft-ietf-mip6-nemo-v4traversal-02.txt is sufficient.

Vijay

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



From mip6-bounces@ietf.org Wed Jul 05 20:27:33 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FyHiO-000537-E7; Wed, 05 Jul 2006 20:27:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FyHiN-00051M-TB
	for mip6@ietf.org; Wed, 05 Jul 2006 20:27:31 -0400
Received: from py-out-1112.google.com ([64.233.166.182])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FyHiM-0008BC-L7
	for mip6@ietf.org; Wed, 05 Jul 2006 20:27:31 -0400
Received: by py-out-1112.google.com with SMTP id m51so179729pye
	for <mip6@ietf.org>; Wed, 05 Jul 2006 17:27:30 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=F9jKf9j7bnN6BWgE94l6bXVePNoNYI6h4I1vJqaAkS24PB3Dev8q80hEBammSA8WYNva0XZZ1D4EZhusZZpI/xBUxRTILVzaMaVH2VPmWdRfRCaixT1uVKzyjKbCTXu1w2gpgYiIU3SkUEPRaZ1YkfiJl5EsCncmnj13fFZf2jk=
Received: by 10.35.134.12 with SMTP id l12mr25079pyn;
	Wed, 05 Jul 2006 17:27:30 -0700 (PDT)
Received: by 10.35.111.9 with HTTP; Wed, 5 Jul 2006 17:27:30 -0700 (PDT)
Message-ID: <729b68be0607051727j43201378udef644c06de3e60c@mail.gmail.com>
Date: Thu, 6 Jul 2006 02:27:30 +0200
From: "Jean-Michel Combes" <jeanmichel.combes@gmail.com>
To: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
Subject: Re: [Mip6] new charter proposal
In-Reply-To: <44AC4C85.70109@azairenet.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <44A82F67.6080105@kolumbus.fi>
	<729b68be0607050439u4780a160r8356c034db39b04f@mail.gmail.com>
	<44AC4C85.70109@azairenet.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
Cc: Gopal Dommety <gdommety@cisco.com>, Jari Arkko <jari.arkko@kolumbus.fi>,
	Basavaraj Patil <basavaraj.patil@nokia.com>,
	Mobile IPv6 Mailing List <mip6@ietf.org>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi Vijay,

the main reason was that protocols standardized in the IETF had to be
independent from the architecture. Today, I am not sure that is still
true (i.e. too many dependencies regarding where and how the protocols
are deployed, and today, some 'recent' RFC are architecture
dependent). But this is another debate ;)

To come back to your comment, it is true that trust between MN and CN
is needed for draft-ietf-mip6-cn-ipsec but if we have such one, shall
we put away a technical solution from IETF standardization?

Best regards.

JMC.

2006/7/6, Vijay Devarapalli <vijay.devarapalli@azairenet.com>:
> Jean-Michel Combes wrote:
>
> > IMO, the draft-ietf-mip6-cn-ipsec should become Proposed Standard. The
> > main reasons are :
> > - No heavy modifications in the MIPv6 implementation (in fact, just to
> > be able to desactivate the RR mechanism)
> > - To have a mechanism that allows a strong security for RO
>
> if this were possible, we would have had MIPv6 standardized back
> in 2000-2001. I remember Jeff Schiller blasting us in December
> 2000 for assuming trust between the MN and the CN to be out of
> scope. this is exactly what draft-ietf-mip6-cn-ipsec assumes.
>
> then we had to design the return routability mechanism.
>
> Vijay
>
> >
> > Thanks.
> >
> > Best regards.
> >
> > JMC.
> >
> >> But I'll listen to the group's
> >> input on this too.
> >>
> >> --Jari
> >>
> >>
> >> _______________________________________________
> >> Mip6 mailing list
> >> Mip6@ietf.org
> >> https://www1.ietf.org/mailman/listinfo/mip6
> >>
> >
> > _______________________________________________
> > Mip6 mailing list
> > Mip6@ietf.org
> > https://www1.ietf.org/mailman/listinfo/mip6
>
>

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



From mip6-bounces@ietf.org Wed Jul 05 20:31:48 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FyHmW-0007MZ-13; Wed, 05 Jul 2006 20:31:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FyHmV-0007MU-B0
	for mip6@ietf.org; Wed, 05 Jul 2006 20:31:47 -0400
Received: from mail1.azairenet.com ([66.92.223.4] helo=bart.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FyHmT-0000A5-WF
	for mip6@ietf.org; Wed, 05 Jul 2006 20:31:47 -0400
Received: from [10.1.201.28] ([10.1.201.28]) by bart.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Wed, 5 Jul 2006 17:31:44 -0700
Message-ID: <44AC59EF.6000803@azairenet.com>
Date: Wed, 05 Jul 2006 17:31:43 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.4 (Windows/20060516)
MIME-Version: 1.0
To: Jean-Michel Combes <jeanmichel.combes@gmail.com>
Subject: Re: [Mip6] new charter proposal
References: <44A82F67.6080105@kolumbus.fi>	
	<729b68be0607050439u4780a160r8356c034db39b04f@mail.gmail.com>	
	<44AC4C85.70109@azairenet.com>
	<729b68be0607051727j43201378udef644c06de3e60c@mail.gmail.com>
In-Reply-To: <729b68be0607051727j43201378udef644c06de3e60c@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 06 Jul 2006 00:31:44.0035 (UTC)
	FILETIME=[8EA36F30:01C6A093]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Cc: Gopal Dommety <gdommety@cisco.com>, Jari Arkko <jari.arkko@kolumbus.fi>,
	Basavaraj Patil <basavaraj.patil@nokia.com>,
	Mobile IPv6 Mailing List <mip6@ietf.org>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Jean-Michel Combes wrote:
> Hi Vijay,
> 
> the main reason was that protocols standardized in the IETF had to be
> independent from the architecture. Today, I am not sure that is still
> true (i.e. too many dependencies regarding where and how the protocols
> are deployed, and today, some 'recent' RFC are architecture
> dependent). But this is another debate ;)
> 
> To come back to your comment, it is true that trust between MN and CN
> is needed for draft-ietf-mip6-cn-ipsec but if we have such one, shall
> we put away a technical solution from IETF standardization?

note that I am not opposed to standardizing
draft-ietf-mip6-cn-ipsec. my email was in response to
your comment about cn-ipsec being stronger than return
routability. my main point is that they assume different
security models.

Vijay

> 
> Best regards.
> 
> JMC.
> 
> 2006/7/6, Vijay Devarapalli <vijay.devarapalli@azairenet.com>:
>> Jean-Michel Combes wrote:
>>
>> > IMO, the draft-ietf-mip6-cn-ipsec should become Proposed Standard. The
>> > main reasons are :
>> > - No heavy modifications in the MIPv6 implementation (in fact, just to
>> > be able to desactivate the RR mechanism)
>> > - To have a mechanism that allows a strong security for RO
>>
>> if this were possible, we would have had MIPv6 standardized back
>> in 2000-2001. I remember Jeff Schiller blasting us in December
>> 2000 for assuming trust between the MN and the CN to be out of
>> scope. this is exactly what draft-ietf-mip6-cn-ipsec assumes.
>>
>> then we had to design the return routability mechanism.
>>
>> Vijay
>>
>> >
>> > Thanks.
>> >
>> > Best regards.
>> >
>> > JMC.
>> >
>> >> But I'll listen to the group's
>> >> input on this too.
>> >>
>> >> --Jari
>> >>
>> >>
>> >> _______________________________________________
>> >> Mip6 mailing list
>> >> Mip6@ietf.org
>> >> https://www1.ietf.org/mailman/listinfo/mip6
>> >>
>> >
>> > _______________________________________________
>> > Mip6 mailing list
>> > Mip6@ietf.org
>> > https://www1.ietf.org/mailman/listinfo/mip6
>>
>>


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



From mip6-bounces@ietf.org Wed Jul 05 20:47:11 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FyI1O-0001vh-ET; Wed, 05 Jul 2006 20:47:10 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FyI1M-0001vc-N8
	for mip6@ietf.org; Wed, 05 Jul 2006 20:47:08 -0400
Received: from py-out-1112.google.com ([64.233.166.177])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FyI1L-0002Tz-GJ
	for mip6@ietf.org; Wed, 05 Jul 2006 20:47:08 -0400
Received: by py-out-1112.google.com with SMTP id m51so183386pye
	for <mip6@ietf.org>; Wed, 05 Jul 2006 17:47:07 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=G7GMmgbDQEt2YXsjF/xsnL0neopxKZ0eQxth7e83vmg8K+LtTiBzVladwQy2qDv0aDSvcRNKXbcNF3llZPmtFpuAg8MGp6YPRKY9OAufvgKwzhJWTNJFE4bWCeULnMrMunWF6df/1yb0sAq7YyI0MyLhj2YRmUdtK9Jo2uKgo9k=
Received: by 10.35.88.18 with SMTP id q18mr41642pyl;
	Wed, 05 Jul 2006 17:47:07 -0700 (PDT)
Received: by 10.35.111.9 with HTTP; Wed, 5 Jul 2006 17:47:07 -0700 (PDT)
Message-ID: <729b68be0607051747r185019b1p7faef024db8c19e7@mail.gmail.com>
Date: Thu, 6 Jul 2006 02:47:07 +0200
From: "Jean-Michel Combes" <jeanmichel.combes@gmail.com>
To: "Francis Dupont" <Francis.Dupont@point6.net>
Subject: Re: [Mip6] Re: AD review of draft-ietf-mip6-cn-ipsec
In-Reply-To: <200607051740.k65HeA3a093061@givry.rennes.enst-bretagne.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <44ABBD38.80808@piuha.net>
	<200607051740.k65HeA3a093061@givry.rennes.enst-bretagne.fr>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi Jari,

2006/7/5, Francis Dupont <Francis.Dupont@point6.net>:
> Some short answers inline:
>

>
>    >    Note that
>    >    some operators can not propose Mobile IPv6 based services knowing
>    >    that the Mobile IPv6 security is based on assumptions.
>
> => I leave this to my co-author who is an employee of an operator
> which has this position.

I think I tried to explain the advantages of such a draft for an
operator in one of my previous emails :)

Do you want we clearly mention such motivations in the draft?

Best regards.

JMC.

>
>
> Regards
>
> Francis.Dupont@point6.net
>
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
>

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



From mip6-bounces@ietf.org Wed Jul 05 20:54:53 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FyI8q-0002AC-I6; Wed, 05 Jul 2006 20:54:52 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FyI8o-0002A7-Oq
	for mip6@ietf.org; Wed, 05 Jul 2006 20:54:51 -0400
Received: from py-out-1112.google.com ([64.233.166.177])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FyI8n-0003Pl-IA
	for mip6@ietf.org; Wed, 05 Jul 2006 20:54:50 -0400
Received: by py-out-1112.google.com with SMTP id m51so184937pye
	for <mip6@ietf.org>; Wed, 05 Jul 2006 17:54:49 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=j5ZY2PkWefwDgXUJt4PfMzb6AiBRZCfEOgjjm75uFySIQ5ktu+Dk9bT2GYuJW6XR5BQBPAb3QvWuXSOedzdCjODq+ib2zNPvGQtifp60rG8Pz2GazMZGxEMAwYLgnfHFxUaijZKYHPMep98TZ08AZfZ4gTLTqXpKXpg2kI1ocO4=
Received: by 10.35.134.12 with SMTP id l12mr53917pyn;
	Wed, 05 Jul 2006 17:54:49 -0700 (PDT)
Received: by 10.35.111.9 with HTTP; Wed, 5 Jul 2006 17:54:49 -0700 (PDT)
Message-ID: <729b68be0607051754j61f9c756qfe8d48fed58de46f@mail.gmail.com>
Date: Thu, 6 Jul 2006 02:54:49 +0200
From: "Jean-Michel Combes" <jeanmichel.combes@gmail.com>
To: "Francis Dupont" <Francis.Dupont@point6.net>
Subject: Re: [Mip6] Re: AD review of draft-ietf-mip6-cn-ipsec
In-Reply-To: <200607052153.k65LrEdM093651@givry.rennes.enst-bretagne.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <44ABBD38.80808@piuha.net>
	<200607052153.k65LrEdM093651@givry.rennes.enst-bretagne.fr>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

2006/7/5, Francis Dupont <Francis.Dupont@point6.net>:
> Short second/higher level pass...
>

>
>    This would work, but I worry about the lack of details here. How would
>    the peers know they are using RFC 3972 to authenticate in IKE? How are
>    the CGA parameters transported? Suggestion: if we can not provide
>    full details, leave this part to another document.
>
> => suggestion: move it to a not normative appendix?
>

draft-laganier-ike-ipv6-cga-01 may be cited but it is expired :(

Best regards.

JMC.

>
> Regards
>
> Francis.Dupont@point6.net
>
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
>

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



From mip6-bounces@ietf.org Wed Jul 05 20:58:49 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FyICd-0002le-2k; Wed, 05 Jul 2006 20:58:47 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FyICc-0002lZ-5f
	for mip6@ietf.org; Wed, 05 Jul 2006 20:58:46 -0400
Received: from mail1.azairenet.com ([66.92.223.4] helo=bart.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FyICb-0003jB-Ku
	for mip6@ietf.org; Wed, 05 Jul 2006 20:58:46 -0400
Received: from [10.1.201.28] ([10.1.201.28]) by bart.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Wed, 5 Jul 2006 17:58:44 -0700
Message-ID: <44AC6042.4030604@azairenet.com>
Date: Wed, 05 Jul 2006 17:58:42 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.4 (Windows/20060516)
MIME-Version: 1.0
To: Alper Yegin <alper.yegin@yegin.org>
Subject: Re: [dhcwg] RE: [Mip6] [Updated] DHCP Option
	forHomeInformationDiscovery inMIPv6
References: <0MKp2t-1FxJkj3hst-0003Ih@mrelay.perfora.net>
In-Reply-To: <0MKp2t-1FxJkj3hst-0003Ih@mrelay.perfora.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 06 Jul 2006 00:58:44.0571 (UTC)
	FILETIME=[548D9AB0:01C6A097]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ec7c6dab5a62df223002ae71b5179d41
Cc: mip6@ietf.org, "'Kent Leung \(kleung\)'" <kleung@cisco.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Alper,

we don't define architectures in the IETF. 
draft-ietf-mip6-bootstrapping-integrated-dhc is supposed to be the only 
bootstrapping *solution* for the integrated scenario. thats the reason 
it is currently a WG document and draft-jang isnt.

lets continue this discussion at the IETF meeting. an offline meeting 
with the working group chairs before the MIP6 WG meeting would help, I 
think.

Vijay

Alper Yegin wrote:
>> there is one issue.
>>
>> draft-jang just does not define the DHCP options. it goes further.
>> abstract of draft-jang says
>>
>>     This draft defines a DHCP-based scheme to enable dynamic discovery of
>>     Mobile IPv6 home agent address, home address, and home subnet.  New
>>     DHCP options are defined to carry the information from a DHCP server
>>     to the DHCP client running on the mobile node.
> 
> What is "further" in this? The words "dynamic discovery?" This is what DHCP
> gives you for anything that you use it for.
> 
> 
>> section 4.2 further goes and ahead and specifies mobile node
>> behavior. the draft just does not define the options. 
> 
> These are all within the scope of defining a new DHCP option.
> 
>> it is also
>> incomplete because it neither describes the scope of the problem
> 
> This is all defined in the Introduction section. If you have specific
> comments, let us know and we'll fix it up.
> 
>> it is trying to address nor gives a complete solution.
> 
> Complete solution, I suspect, is the architecture you are referring to.
> Again, this is a "protocol" document, not an "architecture" document.
> 
>> we can't have two documents that both describe how to use DHCP
>> for MIP6 bootstrapping.
> 
> That's not happening. draft-jang-mip6-hiopt-00 defines a protocol
> specification. draft-ietf-mip6-bootstrapping-integrated-dhc-01 defines the
> architecture and refers to the former for the specific protocol details.
> 
> From your other e-mail:
> 
>>> If the use cases are not limited to only bootstrapping,
> 
>> what other use cases? are those use cases specific to Mobile IPv6?
>> do they fit into the MIP6 WG charter?
> 
> I had explained the use of statically configured DHCP servers earlier,
> remember?
> 
> ....
> 
> Vijay, we have circled around your concerns many times by now. I'm going to
> stop now and see you in Montreal.
> 
> Alper
> 
> 
> 
> 
>> Vijay
>>
>> Kent Leung (kleung) wrote:
>>> Hi Kuntal and Vijay.
>>>
>>> See my posting, "Generalizing draft-jang-dhc-haopt for MIPv6 support in
>>> DHCP", back on Jan 4, 2006 on this topic.  I proposed to keep the 2
>>> drafts separate, one for defining DHCPv6 opcodes for MIPv6 parameters
>>> and a bootstrap draft that references the DHCP options needed to achieve
>>> its function.
>>>
>>> I agree there's no need to drag in references other to say that there's
>>> value for the DHCP MIPv6 options.  3GPP2/WiMAX specs can reference the
>>> DHCPv6 opcodes for MIPv6 draft/RFC, much like what MIPv6 bootstrap would
>>> have done.
>>>
>>> As for what Vijay said about the WiMAX scheme, definitely true that it
>>> doesn't conform to DHCP RFC 3315.  But we should keep the issues
>>> separate.  I haven't read all the emails on the thread.  Just jumping in
>>> to say the following:
>>>
>>>  - Keep 2 separate self contained drafts
>>>  - IETF MIPv6 bootstrap draft references DHCP for MIPv6 draft
>>>  - WiMAX and 3GPP2 can also reference DHCP for MIPv6 draft for their
>>> bootstrapping schemes
>>>
>>> Just some explanatory comments:
>>>  - 3GPP2 conforms to DHCPv6 in its bootstrapping scheme
>>>  - WiMAX does not conform to DHCPv6 when using proxy DHCP server scheme
>>>
>>> But *ALL* of the above bootstrapping schemes use the same DHCP options
>>> for MIPv6 parameters.  That's what justifies an independent DHCP for
>>> MIPv6 draft, IMHO.
>>>
>>> Kent
>>>
>>>
>>>
>>>
>>>> -----Original Message-----
>>>> From: Chowdhury, Kuntal [mailto:kchowdhury@starentnetworks.com]
>>>> Sent: Thursday, June 22, 2006 7:19 PM
>>>> To: Vijay Devarapalli; Behcet Sarikaya
>>>> Cc: mip6@ietf.org; Heejin Jang; dhcwg@ietf.org
>>>> Subject: RE: [dhcwg] RE: [Mip6] [Updated] DHCP Option for
>>>> HomeInformationDiscovery inMIPv6
>>>>
>>>> Sorry, I am not getting this. Why are we dragging WiMAX and
>>>> 3GPP2 references to justify the need for basic DHCP op-codes
>>>> for HoA/HL/HA info?
>>>>
>>>> draft-jang-mip6-hiopt-00.txt defines the DHCPv6 op-codes for
>>>> HA, HoA and HL info.
>>>>
>>>> draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt is the
>>>> MIP6 bootstrapping solution that leverages DHCPv6 for HA/HL
>>>> bootstrapping.
>>>>
>>>> There are tons of I-Ds and solutions in IETF that leverage other I-Ds.
>>>> So, what is so special here? The decision to NOT merge these
>>>> I-Ds was taken in the bootstrap DT. Why are we wasting
>>>> people's time here to revisit basic decisions?
>>>>
>>>> -Kuntal
>>>>
>>>>
>>>>
>>>>> -----Original Message-----
>>>>> From: Vijay Devarapalli [mailto:vijay.devarapalli@azairenet.com]
>>>>> Sent: Thursday, June 22, 2006 12:55 PM
>>>>> To: Behcet Sarikaya
>>>>> Cc: mip6@ietf.org; Heejin Jang; dhcwg@ietf.org
>>>>> Subject: Re: [dhcwg] RE: [Mip6] [Updated] DHCP Option for Home
>>>>> InformationDiscovery inMIPv6
>>>>>
>>>>> Behcet Sarikaya wrote:
>>>>>
>>>>>> Hi Vijay,
>>>>>> The idea in the present WiMAX document is quite simple:
>>>>>> it uses EAP-PKMv2 (which is like 802.11i) authentication
>>>> and during
>>>> EAP
>>>>
>>>>>> transaction, they assume that AAA server determines that
>>>> the MS is a
>>>>
>>>>>> CMIPv6 authorized user based on the AAA profile and it
>>>> will include
>>>> all
>>>>
>>>>>> the so-called bootstrapping info in the Access-Accept. Then MS can
>>>> use
>>>>
>>>>>> RFC 3736 to make a DHCP Information Request to DHCP Relay
>>>> colocated
>>>> with
>>>>
>>>>>> NAS and use draft-jang (extended now with HoA) and receive all the
>>>> info
>>>>
>>>>>> to configure MIP6.
>>>>> the DHCP Relay replies to the MN without relaying the DHCP request
>>>> >from the MN to a DHCP server? this is not allowed with the current
>>>>> IETF specs.
>>>>>
>>>>>
>>>>>>  In this setup can you make a case for
>>>>>> draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt?
>>>>> as far as I am concerned,
>>>>> draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt
>>>>> is the document that describes how to use DHCPv6 for MIPv6
>>>>> bootstrapping. as for the setup in the WiMAX NWG, it is
>>>> something that
>>>>
>>>>> doesn't conform to the IETF DHCP specs.
>>>>>
>>>>> Vijay
>>>>> <snip>
>>
>> _______________________________________________
>> Mip6 mailing list
>> Mip6@ietf.org
>> https://www1.ietf.org/mailman/listinfo/mip6
> 


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



From mip6-bounces@ietf.org Thu Jul 06 02:14:23 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FyN7u-00058k-8T; Thu, 06 Jul 2006 02:14:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FyN7s-00052w-HX; Thu, 06 Jul 2006 02:14:12 -0400
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1FyN7q-0008Oc-Pu; Thu, 06 Jul 2006 02:14:12 -0400
Received: from p130.piuha.net (localhost [127.0.0.1])
	by p130.piuha.net (Postfix) with ESMTP id 1E909898BC;
	Thu,  6 Jul 2006 09:14:10 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id C1414898B9;
	Thu,  6 Jul 2006 09:14:09 +0300 (EEST)
Message-ID: <44ACAA2D.5060504@piuha.net>
Date: Thu, 06 Jul 2006 09:14:05 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Mozilla Thunderbird 1.0.8 (X11/20060502)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: mip6@ietf.org
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: c0bedb65cce30976f0bf60a0a39edea4
Cc: mip4@ietf.org
Subject: [Mip6] summary of the ds-mip4 discussion for mip4 rechartering
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

I am summarizing the discussion so that we can conclude and move
forward. Its been a long discussion and there were also some topics
outside the MIP4 chartering question. For instance, at the end there
was a subthread about the scalability of the current DS-MIPv6
solution.

First, a number of question marks were raised about what actually is
proposed. I believe clarifications were received on all questions. The
essence of the proposal is to enable IPv6 usage in scenarios where
MIPv4 is currently deployed. We need to make the charter text clearer
since this was not immediately obvious to everyone.

There were promises to update earlier problem statement drafts that
people asked for.

There was also a discussion of how this work should be divided to
particular documents. In this case I believe a narrowly scoped, small
document is better than attempting to combine everything to a single
document. Given the clarification of the scope of the work above, most
people seemed to agree that the MIPv4 and MIPv6 parts should be in
separate documents.

It is still unclear to me what the best approach is with regards to the
problem statement part, though. From my point of view we need
one, and either that is published as a common document in MIP6
or we need a separate one for MIP4.

A number of concerns were also raised:

- Is there a real-world demand and customers for this? (According to
  George there is).

- That there is overlap for handling both IPv4 and IPv6 traffic.
  (Right, but its hard to get away from that if you intend to allow
  both IPv4 and IPv6 to be used regardless of what MIP infrastructure
  you are running on. Also part of the motivation for DS-MIPv6 is
  making it possible to use IPv4 Internet while still getting the
  benefits of Mobile IPv6 mobility; Personally, I believe we
  should definately keep  IPv4 home address functionality
  in the DS-MIPv6 work.)

- A number of arguments from the earlier MIP4 list discussion were
  pointed to. E.g., it would be better and more desirable to deploy
  MIPv6 at the time that you deploy IPv6, and the impact to market
  demand for MIPv6.

- There is no danger of getting into a v6-only access network (true,
  but DS-MIPv4 is not addressing that; a clarification of the charter
  may be needed here)

A fairly small number of people stated an opinion about the proposed
work. The result is similar to the earlier discussion on the MIP4
list, i.e., there is no agreement but I think there is rough consensus
for doing the work.

Personally, I do think that this extension to MIP4 makes sense and I
am going forward with the rechartering process. But a revised charter
will first need to be written. Also, we should not overemphasize the
significance of the extension. The main problem is not whether MIP4
deployments get to do IPv6 or not. The main question is what happens
to all those current deployments that do not have either mobility or
IPv6. With that in mind, I also do not think we should add a lot of
functionality into DS-MIPv4. The scope of the work needs to be
very constrained.

--Jari


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



From mip6-bounces@ietf.org Thu Jul 06 04:34:47 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FyPJq-0007hq-Hp; Thu, 06 Jul 2006 04:34:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FyPJp-0007hl-9a
	for mip6@ietf.org; Thu, 06 Jul 2006 04:34:41 -0400
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FyPJn-0001Fg-US
	for mip6@ietf.org; Thu, 06 Jul 2006 04:34:41 -0400
Received: from sabrina.qualcomm.com (sabrina.qualcomm.com [129.46.61.150])
	by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k668YUHN018744
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Thu, 6 Jul 2006 01:34:31 -0700
Received: from NAEXBR03.na.qualcomm.com (naexbr03.qualcomm.com
	[129.46.134.172])
	by sabrina.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	k668YTnQ014256; Thu, 6 Jul 2006 01:34:30 -0700 (PDT)
Received: from NAEX14.na.qualcomm.com ([10.47.5.242]) by
	NAEXBR03.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 6 Jul 2006 01:34:29 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] new charter proposal
Date: Thu, 6 Jul 2006 01:34:26 -0700
Message-ID: <7EB20EA0938B4D42A2D82689365C9B7A07CF8E@NAEX14.na.qualcomm.com>
In-Reply-To: <44AC1547.5030404@azairenet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] new charter proposal
Thread-Index: AcagaqqUqOWQJXU1TliovkuQwYSWAQAbA32g
From: "Soliman, Hesham" <hsoliman@qualcomm.com>
To: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
X-OriginalArrivalTime: 06 Jul 2006 08:34:29.0209 (UTC)
	FILETIME=[FF3A3C90:01C6A0D6]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org


 > > =3D> Depends on who you ask :). Given the amount of questions that =
we
 > > continue to get about the problem and why this is needed I=20
 > would think
 > > it's insufficient. I think this will be a good document to=20
 > point people
 > > to when these issues come up. Thomas just asked for the same thing
 > > recently on the list. So I think it's helpful to have it.=20
 >=20
 > there is an issue here. I understand MIPv6 WG working on
 > a problem statement to justify DS-MIPv6. but I don't see
 > the point in MIPv6 WG justifying the need for DS-MIPv4.

=3D> The nature of the problem is that it is specific to MIP. We don't,
AFAICS, get specific about v4 or v6 in describing the problem in
general. The results were two separate work items in the two different
groups. So a general problem statement, but specific solutions in WGs.

Hesham

 > perhaps the problem statement for DS-MIPv4 should be done
 > in the MIP4 WG (if at all MIP4 WG does DS-MIPv4).
 >=20
 > Vijay
 >=20
 > >=20
 > > Hesham
 > >=20
 > >  >=20
 > >  > --Jari
 > >  >=20
 > >  >=20
 > >=20
 > > _______________________________________________
 > > Mip6 mailing list
 > > Mip6@ietf.org
 > > https://www1.ietf.org/mailman/listinfo/mip6
 >=20
 >=20

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



From mip6-bounces@ietf.org Thu Jul 06 08:33:40 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FyT2y-0003hz-Ao; Thu, 06 Jul 2006 08:33:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FyT2w-0003gT-Ve
	for mip6@ietf.org; Thu, 06 Jul 2006 08:33:30 -0400
Received: from smtp2.int-evry.fr ([157.159.10.45])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FyT2w-00031A-C7
	for mip6@ietf.org; Thu, 06 Jul 2006 08:33:30 -0400
Received: from ipv6-3.int-evry.fr (ipv6-3.int-evry.fr [157.159.100.76])
	by smtp2.int-evry.fr (Postfix) with ESMTP id BE74C2FE5A;
	Thu,  6 Jul 2006 14:33:27 +0200 (CEST)
Received: from jb by ipv6-3.int-evry.fr with local (Exim 4.52)
	id 1FyT48-0001A4-TA; Thu, 06 Jul 2006 14:34:44 +0200
Date: Thu, 6 Jul 2006 14:34:44 +0200
From: Julien Bournelle <julien.bournelle@int-evry.fr>
To: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
Subject: Re: [dhcwg] RE: [Mip6] [Updated] DHCP Option
	forHomeInformationDiscovery inMIPv6
Message-ID: <20060706123444.GA4460@ipv6-3.int-evry.fr>
References: <0MKp2t-1FxJkj3hst-0003Ih@mrelay.perfora.net>
	<44AC6042.4030604@azairenet.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <44AC6042.4030604@azairenet.com>
User-Agent: Mutt/1.5.9i
X-INT-MailScanner-Information: Please contact the ISP for more information
X-INT-MailScanner: Found to be clean
X-INT-MailScanner-MCPCheck: 
X-INT-MailScanner-SpamCheck: 
X-MailScanner-From: jb@int-evry.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ff0adf256e4dd459cc25215cfa732ac1
Cc: mip6@ietf.org, "'Kent Leung \(kleung\)'" <kleung@cisco.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi all,

On Wed, Jul 05, 2006 at 05:58:42PM -0700, Vijay Devarapalli wrote:
> Alper,
> 
> we don't define architectures in the IETF. 
> draft-ietf-mip6-bootstrapping-integrated-dhc is supposed to be the only 
> bootstrapping *solution* for the integrated scenario. thats the reason 
> it is currently a WG document and draft-jang isnt.

 I'm not sure that the intent was to be the only bootstrapping solution
 for the integrated scenario. We have added the suffix -dhc to specify
 that the delivery of HA information to the MN was based on DHCP but
 others solutions may be possible (cf.
 draft-bournelle-pana-mip6-01.txt).

 My 2 cents,

 Julien

> 
> lets continue this discussion at the IETF meeting. an offline meeting 
> with the working group chairs before the MIP6 WG meeting would help, I 
> think.
> 
> Vijay
> 
> Alper Yegin wrote:
> >>there is one issue.
> >>
> >>draft-jang just does not define the DHCP options. it goes further.
> >>abstract of draft-jang says
> >>
> >>    This draft defines a DHCP-based scheme to enable dynamic discovery of
> >>    Mobile IPv6 home agent address, home address, and home subnet.  New
> >>    DHCP options are defined to carry the information from a DHCP server
> >>    to the DHCP client running on the mobile node.
> >
> >What is "further" in this? The words "dynamic discovery?" This is what DHCP
> >gives you for anything that you use it for.
> >
> >
> >>section 4.2 further goes and ahead and specifies mobile node
> >>behavior. the draft just does not define the options. 
> >
> >These are all within the scope of defining a new DHCP option.
> >
> >>it is also
> >>incomplete because it neither describes the scope of the problem
> >
> >This is all defined in the Introduction section. If you have specific
> >comments, let us know and we'll fix it up.
> >
> >>it is trying to address nor gives a complete solution.
> >
> >Complete solution, I suspect, is the architecture you are referring to.
> >Again, this is a "protocol" document, not an "architecture" document.
> >
> >>we can't have two documents that both describe how to use DHCP
> >>for MIP6 bootstrapping.
> >
> >That's not happening. draft-jang-mip6-hiopt-00 defines a protocol
> >specification. draft-ietf-mip6-bootstrapping-integrated-dhc-01 defines the
> >architecture and refers to the former for the specific protocol details.
> >
> >From your other e-mail:
> >
> >>>If the use cases are not limited to only bootstrapping,
> >
> >>what other use cases? are those use cases specific to Mobile IPv6?
> >>do they fit into the MIP6 WG charter?
> >
> >I had explained the use of statically configured DHCP servers earlier,
> >remember?
> >
> >....
> >
> >Vijay, we have circled around your concerns many times by now. I'm going to
> >stop now and see you in Montreal.
> >
> >Alper
> >
> >
> >
> >
> >>Vijay
> >>
> >>Kent Leung (kleung) wrote:
> >>>Hi Kuntal and Vijay.
> >>>
> >>>See my posting, "Generalizing draft-jang-dhc-haopt for MIPv6 support in
> >>>DHCP", back on Jan 4, 2006 on this topic.  I proposed to keep the 2
> >>>drafts separate, one for defining DHCPv6 opcodes for MIPv6 parameters
> >>>and a bootstrap draft that references the DHCP options needed to achieve
> >>>its function.
> >>>
> >>>I agree there's no need to drag in references other to say that there's
> >>>value for the DHCP MIPv6 options.  3GPP2/WiMAX specs can reference the
> >>>DHCPv6 opcodes for MIPv6 draft/RFC, much like what MIPv6 bootstrap would
> >>>have done.
> >>>
> >>>As for what Vijay said about the WiMAX scheme, definitely true that it
> >>>doesn't conform to DHCP RFC 3315.  But we should keep the issues
> >>>separate.  I haven't read all the emails on the thread.  Just jumping in
> >>>to say the following:
> >>>
> >>> - Keep 2 separate self contained drafts
> >>> - IETF MIPv6 bootstrap draft references DHCP for MIPv6 draft
> >>> - WiMAX and 3GPP2 can also reference DHCP for MIPv6 draft for their
> >>>bootstrapping schemes
> >>>
> >>>Just some explanatory comments:
> >>> - 3GPP2 conforms to DHCPv6 in its bootstrapping scheme
> >>> - WiMAX does not conform to DHCPv6 when using proxy DHCP server scheme
> >>>
> >>>But *ALL* of the above bootstrapping schemes use the same DHCP options
> >>>for MIPv6 parameters.  That's what justifies an independent DHCP for
> >>>MIPv6 draft, IMHO.
> >>>
> >>>Kent
> >>>
> >>>
> >>>
> >>>
> >>>>-----Original Message-----
> >>>>From: Chowdhury, Kuntal [mailto:kchowdhury@starentnetworks.com]
> >>>>Sent: Thursday, June 22, 2006 7:19 PM
> >>>>To: Vijay Devarapalli; Behcet Sarikaya
> >>>>Cc: mip6@ietf.org; Heejin Jang; dhcwg@ietf.org
> >>>>Subject: RE: [dhcwg] RE: [Mip6] [Updated] DHCP Option for
> >>>>HomeInformationDiscovery inMIPv6
> >>>>
> >>>>Sorry, I am not getting this. Why are we dragging WiMAX and
> >>>>3GPP2 references to justify the need for basic DHCP op-codes
> >>>>for HoA/HL/HA info?
> >>>>
> >>>>draft-jang-mip6-hiopt-00.txt defines the DHCPv6 op-codes for
> >>>>HA, HoA and HL info.
> >>>>
> >>>>draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt is the
> >>>>MIP6 bootstrapping solution that leverages DHCPv6 for HA/HL
> >>>>bootstrapping.
> >>>>
> >>>>There are tons of I-Ds and solutions in IETF that leverage other I-Ds.
> >>>>So, what is so special here? The decision to NOT merge these
> >>>>I-Ds was taken in the bootstrap DT. Why are we wasting
> >>>>people's time here to revisit basic decisions?
> >>>>
> >>>>-Kuntal
> >>>>
> >>>>
> >>>>
> >>>>>-----Original Message-----
> >>>>>From: Vijay Devarapalli [mailto:vijay.devarapalli@azairenet.com]
> >>>>>Sent: Thursday, June 22, 2006 12:55 PM
> >>>>>To: Behcet Sarikaya
> >>>>>Cc: mip6@ietf.org; Heejin Jang; dhcwg@ietf.org
> >>>>>Subject: Re: [dhcwg] RE: [Mip6] [Updated] DHCP Option for Home
> >>>>>InformationDiscovery inMIPv6
> >>>>>
> >>>>>Behcet Sarikaya wrote:
> >>>>>
> >>>>>>Hi Vijay,
> >>>>>>The idea in the present WiMAX document is quite simple:
> >>>>>>it uses EAP-PKMv2 (which is like 802.11i) authentication
> >>>>and during
> >>>>EAP
> >>>>
> >>>>>>transaction, they assume that AAA server determines that
> >>>>the MS is a
> >>>>
> >>>>>>CMIPv6 authorized user based on the AAA profile and it
> >>>>will include
> >>>>all
> >>>>
> >>>>>>the so-called bootstrapping info in the Access-Accept. Then MS can
> >>>>use
> >>>>
> >>>>>>RFC 3736 to make a DHCP Information Request to DHCP Relay
> >>>>colocated
> >>>>with
> >>>>
> >>>>>>NAS and use draft-jang (extended now with HoA) and receive all the
> >>>>info
> >>>>
> >>>>>>to configure MIP6.
> >>>>>the DHCP Relay replies to the MN without relaying the DHCP request
> >>>>>from the MN to a DHCP server? this is not allowed with the current
> >>>>>IETF specs.
> >>>>>
> >>>>>
> >>>>>> In this setup can you make a case for
> >>>>>>draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt?
> >>>>>as far as I am concerned,
> >>>>>draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt
> >>>>>is the document that describes how to use DHCPv6 for MIPv6
> >>>>>bootstrapping. as for the setup in the WiMAX NWG, it is
> >>>>something that
> >>>>
> >>>>>doesn't conform to the IETF DHCP specs.
> >>>>>
> >>>>>Vijay
> >>>>><snip>
> >>
> >>_______________________________________________
> >>Mip6 mailing list
> >>Mip6@ietf.org
> >>https://www1.ietf.org/mailman/listinfo/mip6
> >
> 
> 
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6

-- 
julien.bournelle at int-evry.fr

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



From mip6-bounces@ietf.org Thu Jul 06 13:25:48 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FyXbk-0004Lb-D7; Thu, 06 Jul 2006 13:25:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FyXbi-0004LW-Kl
	for mip6@ietf.org; Thu, 06 Jul 2006 13:25:42 -0400
Received: from mail1.azairenet.com ([66.92.223.4] helo=bart.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FyXbh-0006QX-TQ
	for mip6@ietf.org; Thu, 06 Jul 2006 13:25:42 -0400
Received: from [10.1.201.28] ([10.1.201.28]) by bart.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Thu, 6 Jul 2006 10:25:39 -0700
Message-ID: <44AD478E.8090606@azairenet.com>
Date: Thu, 06 Jul 2006 10:25:34 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.4 (Windows/20060516)
MIME-Version: 1.0
To: Julien Bournelle <julien.bournelle@int-evry.fr>
Subject: Re: [dhcwg] RE: [Mip6] [Updated] DHCP Option
	forHomeInformationDiscovery inMIPv6
References: <0MKp2t-1FxJkj3hst-0003Ih@mrelay.perfora.net>
	<44AC6042.4030604@azairenet.com>
	<20060706123444.GA4460@ipv6-3.int-evry.fr>
In-Reply-To: <20060706123444.GA4460@ipv6-3.int-evry.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 06 Jul 2006 17:25:39.0110 (UTC)
	FILETIME=[332B3460:01C6A121]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d008c19e97860b8641c1851f84665a75
Cc: mip6@ietf.org, "'Kent Leung \(kleung\)'" <kleung@cisco.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Julien Bournelle wrote:
> Hi all,
> 
> On Wed, Jul 05, 2006 at 05:58:42PM -0700, Vijay Devarapalli wrote:
>> Alper,
>>
>> we don't define architectures in the IETF. 
>> draft-ietf-mip6-bootstrapping-integrated-dhc is supposed to be the only 
>> bootstrapping *solution* for the integrated scenario. thats the reason 
>> it is currently a WG document and draft-jang isnt.
> 
>  I'm not sure that the intent was to be the only bootstrapping solution
>  for the integrated scenario. We have added the suffix -dhc to specify
>  that the delivery of HA information to the MN was based on DHCP but
>  others solutions may be possible (cf.
>  draft-bournelle-pana-mip6-01.txt).

hmm... we discussed a bunch of options (including PANA)
for the integrated scenario and concluded on DHCP. so
in that sense, we are standardizing only one solution
(based on DHCP) for the integrated scenario. a solution
based on PANA is possible if there is a need for it.

Vijay

> 
>  My 2 cents,
> 
>  Julien
> 
>> lets continue this discussion at the IETF meeting. an offline meeting 
>> with the working group chairs before the MIP6 WG meeting would help, I 
>> think.
>>
>> Vijay
>>
>> Alper Yegin wrote:
>>>> there is one issue.
>>>>
>>>> draft-jang just does not define the DHCP options. it goes further.
>>>> abstract of draft-jang says
>>>>
>>>>    This draft defines a DHCP-based scheme to enable dynamic discovery of
>>>>    Mobile IPv6 home agent address, home address, and home subnet.  New
>>>>    DHCP options are defined to carry the information from a DHCP server
>>>>    to the DHCP client running on the mobile node.
>>> What is "further" in this? The words "dynamic discovery?" This is what DHCP
>>> gives you for anything that you use it for.
>>>
>>>
>>>> section 4.2 further goes and ahead and specifies mobile node
>>>> behavior. the draft just does not define the options. 
>>> These are all within the scope of defining a new DHCP option.
>>>
>>>> it is also
>>>> incomplete because it neither describes the scope of the problem
>>> This is all defined in the Introduction section. If you have specific
>>> comments, let us know and we'll fix it up.
>>>
>>>> it is trying to address nor gives a complete solution.
>>> Complete solution, I suspect, is the architecture you are referring to.
>>> Again, this is a "protocol" document, not an "architecture" document.
>>>
>>>> we can't have two documents that both describe how to use DHCP
>>>> for MIP6 bootstrapping.
>>> That's not happening. draft-jang-mip6-hiopt-00 defines a protocol
>>> specification. draft-ietf-mip6-bootstrapping-integrated-dhc-01 defines the
>>> architecture and refers to the former for the specific protocol details.
>>>
>> >From your other e-mail:
>>>>> If the use cases are not limited to only bootstrapping,
>>>> what other use cases? are those use cases specific to Mobile IPv6?
>>>> do they fit into the MIP6 WG charter?
>>> I had explained the use of statically configured DHCP servers earlier,
>>> remember?
>>>
>>> ....
>>>
>>> Vijay, we have circled around your concerns many times by now. I'm going to
>>> stop now and see you in Montreal.
>>>
>>> Alper
>>>
>>>
>>>
>>>
>>>> Vijay
>>>>
>>>> Kent Leung (kleung) wrote:
>>>>> Hi Kuntal and Vijay.
>>>>>
>>>>> See my posting, "Generalizing draft-jang-dhc-haopt for MIPv6 support in
>>>>> DHCP", back on Jan 4, 2006 on this topic.  I proposed to keep the 2
>>>>> drafts separate, one for defining DHCPv6 opcodes for MIPv6 parameters
>>>>> and a bootstrap draft that references the DHCP options needed to achieve
>>>>> its function.
>>>>>
>>>>> I agree there's no need to drag in references other to say that there's
>>>>> value for the DHCP MIPv6 options.  3GPP2/WiMAX specs can reference the
>>>>> DHCPv6 opcodes for MIPv6 draft/RFC, much like what MIPv6 bootstrap would
>>>>> have done.
>>>>>
>>>>> As for what Vijay said about the WiMAX scheme, definitely true that it
>>>>> doesn't conform to DHCP RFC 3315.  But we should keep the issues
>>>>> separate.  I haven't read all the emails on the thread.  Just jumping in
>>>>> to say the following:
>>>>>
>>>>> - Keep 2 separate self contained drafts
>>>>> - IETF MIPv6 bootstrap draft references DHCP for MIPv6 draft
>>>>> - WiMAX and 3GPP2 can also reference DHCP for MIPv6 draft for their
>>>>> bootstrapping schemes
>>>>>
>>>>> Just some explanatory comments:
>>>>> - 3GPP2 conforms to DHCPv6 in its bootstrapping scheme
>>>>> - WiMAX does not conform to DHCPv6 when using proxy DHCP server scheme
>>>>>
>>>>> But *ALL* of the above bootstrapping schemes use the same DHCP options
>>>>> for MIPv6 parameters.  That's what justifies an independent DHCP for
>>>>> MIPv6 draft, IMHO.
>>>>>
>>>>> Kent
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Chowdhury, Kuntal [mailto:kchowdhury@starentnetworks.com]
>>>>>> Sent: Thursday, June 22, 2006 7:19 PM
>>>>>> To: Vijay Devarapalli; Behcet Sarikaya
>>>>>> Cc: mip6@ietf.org; Heejin Jang; dhcwg@ietf.org
>>>>>> Subject: RE: [dhcwg] RE: [Mip6] [Updated] DHCP Option for
>>>>>> HomeInformationDiscovery inMIPv6
>>>>>>
>>>>>> Sorry, I am not getting this. Why are we dragging WiMAX and
>>>>>> 3GPP2 references to justify the need for basic DHCP op-codes
>>>>>> for HoA/HL/HA info?
>>>>>>
>>>>>> draft-jang-mip6-hiopt-00.txt defines the DHCPv6 op-codes for
>>>>>> HA, HoA and HL info.
>>>>>>
>>>>>> draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt is the
>>>>>> MIP6 bootstrapping solution that leverages DHCPv6 for HA/HL
>>>>>> bootstrapping.
>>>>>>
>>>>>> There are tons of I-Ds and solutions in IETF that leverage other I-Ds.
>>>>>> So, what is so special here? The decision to NOT merge these
>>>>>> I-Ds was taken in the bootstrap DT. Why are we wasting
>>>>>> people's time here to revisit basic decisions?
>>>>>>
>>>>>> -Kuntal
>>>>>>
>>>>>>
>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: Vijay Devarapalli [mailto:vijay.devarapalli@azairenet.com]
>>>>>>> Sent: Thursday, June 22, 2006 12:55 PM
>>>>>>> To: Behcet Sarikaya
>>>>>>> Cc: mip6@ietf.org; Heejin Jang; dhcwg@ietf.org
>>>>>>> Subject: Re: [dhcwg] RE: [Mip6] [Updated] DHCP Option for Home
>>>>>>> InformationDiscovery inMIPv6
>>>>>>>
>>>>>>> Behcet Sarikaya wrote:
>>>>>>>
>>>>>>>> Hi Vijay,
>>>>>>>> The idea in the present WiMAX document is quite simple:
>>>>>>>> it uses EAP-PKMv2 (which is like 802.11i) authentication
>>>>>> and during
>>>>>> EAP
>>>>>>
>>>>>>>> transaction, they assume that AAA server determines that
>>>>>> the MS is a
>>>>>>
>>>>>>>> CMIPv6 authorized user based on the AAA profile and it
>>>>>> will include
>>>>>> all
>>>>>>
>>>>>>>> the so-called bootstrapping info in the Access-Accept. Then MS can
>>>>>> use
>>>>>>
>>>>>>>> RFC 3736 to make a DHCP Information Request to DHCP Relay
>>>>>> colocated
>>>>>> with
>>>>>>
>>>>>>>> NAS and use draft-jang (extended now with HoA) and receive all the
>>>>>> info
>>>>>>
>>>>>>>> to configure MIP6.
>>>>>>> the DHCP Relay replies to the MN without relaying the DHCP request
>>>>>> >from the MN to a DHCP server? this is not allowed with the current
>>>>>>> IETF specs.
>>>>>>>
>>>>>>>
>>>>>>>> In this setup can you make a case for
>>>>>>>> draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt?
>>>>>>> as far as I am concerned,
>>>>>>> draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt
>>>>>>> is the document that describes how to use DHCPv6 for MIPv6
>>>>>>> bootstrapping. as for the setup in the WiMAX NWG, it is
>>>>>> something that
>>>>>>
>>>>>>> doesn't conform to the IETF DHCP specs.
>>>>>>>
>>>>>>> Vijay
>>>>>>> <snip>
>>>> _______________________________________________
>>>> Mip6 mailing list
>>>> Mip6@ietf.org
>>>> https://www1.ietf.org/mailman/listinfo/mip6
>>
>> _______________________________________________
>> Mip6 mailing list
>> Mip6@ietf.org
>> https://www1.ietf.org/mailman/listinfo/mip6
> 


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



From mip6-bounces@ietf.org Thu Jul 06 15:04:31 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FyZ9J-0008Qd-Cq; Thu, 06 Jul 2006 15:04:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FyZ9I-0008Nm-KW
	for mip6@ietf.org; Thu, 06 Jul 2006 15:04:28 -0400
Received: from mail1.azairenet.com ([66.92.223.4] helo=bart.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FyZ9H-00052w-Bu
	for mip6@ietf.org; Thu, 06 Jul 2006 15:04:28 -0400
Received: from [10.1.201.28] ([10.1.201.28]) by bart.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Thu, 6 Jul 2006 12:04:24 -0700
Message-ID: <44AD5EB4.7000100@azairenet.com>
Date: Thu, 06 Jul 2006 12:04:20 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.4 (Windows/20060516)
MIME-Version: 1.0
To: Francis Dupont <Francis.Dupont@point6.net>
Subject: Re: [Mip6] new charter proposal
References: <200607061733.k66HXfvf096521@givry.rennes.enst-bretagne.fr>
In-Reply-To: <200607061733.k66HXfvf096521@givry.rennes.enst-bretagne.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 06 Jul 2006 19:04:24.0414 (UTC)
	FILETIME=[FEECD7E0:01C6A12E]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Cc: Gopal Dommety <gdommety@cisco.com>, Jari Arkko <jari.arkko@kolumbus.fi>,
	Basavaraj Patil <basavaraj.patil@nokia.com>,
	Mobile IPv6 Mailing List <mip6@ietf.org>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Francis Dupont wrote:
>  In your previous mail you wrote:
> 
>    note that I am not opposed to standardizing
>    draft-ietf-mip6-cn-ipsec. my email was in response to
>    your comment about cn-ipsec being stronger than return
>    routability. my main point is that they assume different
>    security models.
>    
> => Vijay, it seems you are trying to break an open door: if the
> cn-ipsec is stronger than return routability, it is because
> it assume a different (and narrower) security model...

I guess we agree. since they assume different security models
we can't claim one is better than the other.

Vijay

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



From mip6-bounces@ietf.org Thu Jul 06 16:52:05 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FyapN-0003tb-JG; Thu, 06 Jul 2006 16:52:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FyapL-0003tE-QC
	for mip6@ietf.org; Thu, 06 Jul 2006 16:51:59 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FyXya-0008TW-VG
	for mip6@ietf.org; Thu, 06 Jul 2006 13:49:20 -0400
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1FyXk1-0001CA-My
	for mip6@ietf.org; Thu, 06 Jul 2006 13:34:19 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by laposte.rennes.enst-bretagne.fr (8.13.4/8.13.4/2004.10.03) with
	ESMTP id k66HXhxV027149; Thu, 6 Jul 2006 19:33:43 +0200
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[192.44.77.29])
	by laposte.rennes.enst-bretagne.fr (8.13.4/8.13.4/2004.09.01) with
	ESMTP id k66HXgRV027145; Thu, 6 Jul 2006 19:33:42 +0200
Received: from givry.rennes.enst-bretagne.fr
	(localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.13.1/8.13.1) with ESMTP id
	k66HXfvf096521; Thu, 6 Jul 2006 19:33:41 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200607061733.k66HXfvf096521@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@point6.net>
To: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
Subject: Re: [Mip6] new charter proposal 
In-reply-to: Your message of Wed, 05 Jul 2006 17:31:43 PDT.
	<44AC59EF.6000803@azairenet.com> 
Date: Thu, 06 Jul 2006 19:33:41 +0200
X-Virus-Scanned: amavisd-new at enst-bretagne.fr
X-Spam-Score: -1.9 (-)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Cc: Gopal Dommety <gdommety@cisco.com>, Jari Arkko <jari.arkko@kolumbus.fi>,
	Basavaraj Patil <basavaraj.patil@nokia.com>,
	Mobile IPv6 Mailing List <mip6@ietf.org>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   note that I am not opposed to standardizing
   draft-ietf-mip6-cn-ipsec. my email was in response to
   your comment about cn-ipsec being stronger than return
   routability. my main point is that they assume different
   security models.
   
=> Vijay, it seems you are trying to break an open door: if the
cn-ipsec is stronger than return routability, it is because
it assume a different (and narrower) security model...

Regards

Francis.Dupont@point6.net

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



From mip6-bounces@ietf.org Fri Jul 07 05:47:21 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fymvc-00013s-5a; Fri, 07 Jul 2006 05:47:16 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fymva-00013f-Sl
	for mip6@ietf.org; Fri, 07 Jul 2006 05:47:14 -0400
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FymvZ-0000Q5-JB
	for mip6@ietf.org; Fri, 07 Jul 2006 05:47:14 -0400
Received: from p130.piuha.net (localhost [127.0.0.1])
	by p130.piuha.net (Postfix) with ESMTP id 354C9898B6;
	Fri,  7 Jul 2006 12:47:12 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id 5F2948989C;
	Fri,  7 Jul 2006 12:47:11 +0300 (EEST)
Message-ID: <44AD5344.30107@piuha.net>
Date: Thu, 06 Jul 2006 21:15:32 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Mozilla Thunderbird 1.0.8 (X11/20060502)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Jean-Michel Combes <jeanmichel.combes@gmail.com>
Subject: Re: [Mip6] Re: AD review of draft-ietf-mip6-cn-ipsec
References: <44ABBD38.80808@piuha.net>	
	<200607052153.k65LrEdM093651@givry.rennes.enst-bretagne.fr>
	<729b68be0607051754j61f9c756qfe8d48fed58de46f@mail.gmail.com>
In-Reply-To: <729b68be0607051754j61f9c756qfe8d48fed58de46f@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: Francis Dupont <Francis.Dupont@point6.net>,
	Mobile IPv6 Mailing List <mip6@ietf.org>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Jean-Michel Combes wrote:

>>
>>    This would work, but I worry about the lack of details here. How
>> would
>>    the peers know they are using RFC 3972 to authenticate in IKE? How
>> are
>>    the CGA parameters transported? Suggestion: if we can not provide
>>    full details, leave this part to another document.
>>
>> => suggestion: move it to a not normative appendix?
>>
>
> draft-laganier-ike-ipv6-cga-01 may be cited but it is expired :(

Right. The goal should be that the cn-ipsec RFC is
either self-contained or points to other, already published
RFCs for its normative behaviour.

(And its often a good idea to not put many independent
things in the same RFC. You can always publish the next
RFC.)

--Jari



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

From mip6-bounces@ietf.org Fri Jul 07 05:47:21 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fymvf-00015M-VB; Fri, 07 Jul 2006 05:47:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fymve-00014L-79
	for mip6@ietf.org; Fri, 07 Jul 2006 05:47:18 -0400
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fymvc-0000QG-UT
	for mip6@ietf.org; Fri, 07 Jul 2006 05:47:18 -0400
Received: from p130.piuha.net (localhost [127.0.0.1])
	by p130.piuha.net (Postfix) with ESMTP id 43DE4898B6;
	Fri,  7 Jul 2006 12:47:16 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id 7557E8989C;
	Fri,  7 Jul 2006 12:47:15 +0300 (EEST)
Message-ID: <44AD597D.7050001@piuha.net>
Date: Thu, 06 Jul 2006 21:42:05 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Mozilla Thunderbird 1.0.8 (X11/20060502)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Jean-Michel Combes From mip6-bounces@ietf.org Fri Jul 07 05:47:21 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fymvc-00013s-5a; Fri, 07 Jul 2006 05:47:16 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fymva-00013f-Sl
	for mip6@ietf.org; Fri, 07 Jul 2006 05:47:14 -0400
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FymvZ-0000Q5-JB
	for mip6@ietf.org; Fri, 07 Jul 2006 05:47:14 -0400
Received: from p130.piuha.net (localhost [127.0.0.1])
	by p130.piuha.net (Postfix) with ESMTP id 354C9898B6;
	Fri,  7 Jul 2006 12:47:12 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id 5F2948989C;
	Fri,  7 Jul 2006 12:47:11 +0300 (EEST)
Message-ID: <44AD5344.30107@piuha.net>
Date: Thu, 06 Jul 2006 21:15:32 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Mozilla Thunderbird 1.0.8 (X11/20060502)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Jean-Michel Combes <jeanmichel.combes@gmail.com>
Subject: Re: [Mip6] Re: AD review of draft-ietf-mip6-cn-ipsec
References: <44ABBD38.80808@piuha.net>	
	<200607052153.k65LrEdM093651@givry.rennes.enst-bretagne.fr>
	<729b68be0607051754j61f9c756qfe8d48fed58de46f@mail.gmail.com>
In-Reply-To: <729b68be0607051754j61f9c756qfe8d48fed58de46f@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: Francis Dupont <Francis.Dupont@point6.net>,
	Mobile IPv6 Mailing List <mip6@ietf.org>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Jean-Michel Combes wrote:

>>
>>    This would work, but I worry about the lack of details here. How
>> would
>>    the peers know they are using RFC 3972 to authenticate in IKE? How
>> are
>>    the CGA parameters transported? Suggestion: if we can not provide
>>    full details, leave this part to another document.
>>
>> => suggestion: move it to a not normative appendix?
>>
>
> draft-laganier-ike-ipv6-cga-01 may be cited but it is expired :(

Right. The goal should be that the cn-ipsec RFC is
either self-contained or points to other, already published
RFCs for its normative behaviour.

(And its often a good idea to not put many independent
things in the same RFC. You can always publish the next
RFC.)

--Jari



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

From mip6-bounces@ietf.org Fri Jul 07 05:47:21 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fymvf-00015M-VB; Fri, 07 Jul 2006 05:47:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fymve-00014L-79
	for mip6@ietf.org; Fri, 07 Jul 2006 05:47:18 -0400
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fymvc-0000QG-UT
	for mip6@ietf.org; Fri, 07 Jul 2006 05:47:18 -0400
Received: from p130.piuha.net (localhost [127.0.0.1])
	by p130.piuha.net (Postfix) with ESMTP id 43DE4898B6;
	Fri,  7 Jul 2006 12:47:16 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id 7557E8989C;
	Fri,  7 Jul 2006 12:47:15 +0300 (EEST)
Message-ID: <44AD597D.7050001@piuha.net>
Date: Thu, 06 Jul 2006 21:42:05 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Mozilla Thunderbird 1.0.8 (X11/20060502)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Jean-Michel Combes <jeanmichel.combes@gmail.com>
Subject: Re: [Mip6] Re: AD review of draft-ietf-mip6-cn-ipsec
References: <44ABBD38.80808@piuha.net>	
	<200607051740.k65HeA3a093061@givry.rennes.enst-bretagne.fr>
	<729b68be0607051747r185019b1p7faef024db8c19e7@mail.gmail.com>
In-Reply-To: <729b68be0607051747r185019b1p7faef024db8c19e7@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Cc: Francis Dupont <Francis.Dupont@point6.net>,
	Mobile IPv6 Mailing List <mip6@ietf.org>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Jean-Michel Combes wrote:

> I think I tried to explain the advantages of such a draft for an
> operator in one of my previous emails :)
>
> Do you want we clearly mention such motivations in the draft?

You should definately describe the security properties
of the method you are describing. It is often also useful
to describe differences to other, earlier methods. The
description needs to be explained in technical terms and
be complete and accurate, however.

--Jari



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





<jeanmichel.combes@gmail.com>
Subject: Re: [Mip6] Re: AD review of draft-ietf-mip6-cn-ipsec
References: <44ABBD38.80808@piuha.net>	
	<200607051740.k65HeA3a093061@givry.rennes.enst-bretagne.fr>
	<729b68be0607051747r185019b1p7faef024db8c19e7@mail.gmail.com>
In-Reply-To: <729b68be0607051747r185019b1p7faef024db8c19e7@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Cc: Francis Dupont <Francis.Dupont@point6.net>,
	Mobile IPv6 Mailing List <mip6@ietf.org>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Jean-Michel Combes wrote:

> I think I tried to explain the advantages of such a draft for an
> operator in one of my previous emails :)
>
> Do you want we clearly mention such motivations in the draft?

You should definately describe the security properties
of the method you are describing. It is often also useful
to describe differences to other, earlier methods. The
description needs to be explained in technical terms and
be complete and accurate, however.

--Jari



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





From mip6-bounces@ietf.org Fri Jul 07 05:47:26 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fymvh-00016b-Gm; Fri, 07 Jul 2006 05:47:21 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fymvf-00015B-RJ
	for mip6@ietf.org; Fri, 07 Jul 2006 05:47:19 -0400
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fymvf-0000QM-4Z
	for mip6@ietf.org; Fri, 07 Jul 2006 05:47:19 -0400
Received: from p130.piuha.net (localhost [127.0.0.1])
	by p130.piuha.net (Postfix) with ESMTP id 3C9F1898B7;
	Fri,  7 Jul 2006 12:47:18 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id 2006A8989C;
	Fri,  7 Jul 2006 12:47:16 +0300 (EEST)
Message-ID: <44AD64E0.6040908@piuha.net>
Date: Thu, 06 Jul 2006 22:30:40 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Mozilla Thunderbird 1.0.8 (X11/20060502)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Rajeev Koodli <rajeev@iprg.nokia.com>
Subject: Re: [Mip6] some comments on draft-ietf-mip6-location-privacy-ps
References: <44A82617.9060400@kolumbus.fi> <44ABFF17.90508@iprg.nokia.com>
In-Reply-To: <44ABFF17.90508@iprg.nokia.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: 1.1 (+)
X-Scan-Signature: cdb443e3957ca9b4c5b55e78cfcf4b26
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>,
	Rajeev Koodli <rajeev.koodli@nokia.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi Rajeev,

Thanks for your quick response.  I'm continuing the discussion
inline for the remaining points:

>
>>>   Location privacy may be compromised if an on-looker is present on
>>>   the MN - HA path (when bidirectional tunneling is used), or when the
>>>   on-looker is present on the MN and CN path (when route optimization
>>>   is used).
>>>   
>>
>>
>> This needs to be explained in more detail. From what I can see,
>> location privacy is always revealed on the mn-ha path, given the
>> location of the various options and headers in the binding updates.
>> You should also talk about the effect or lack thereof of applying
>> ESP with encryption.
>>
>>  
>>
> I would like to be clear about one thing. We are dealing primarily
> with HoA and CoA revealing
> here. These are the "identifiers" whose disclosure leads to compromise
> in location privacy. The
> other parameters by themselves are either not enough to compromise
> location privacy or are essentially
> the same as the general "profiling" problem.
>
> So, on the MN-HA path, if the HoA is revealed, yes, that would lead to
> a compromise in location
> privacy.

I don't think you can entirely get away from the identity privacy problem.
Any disclosure of the host's identity may lead to a location privacy
problem,
if the attacker can associate your identity with the different traffic
streams
at different places.

But I agree that you need to draw a line somewhere where you stop
describing the details. But please provide some details at least
as examples. For instance, you could mention HAO, IPsec/IKE SPIs,
the use of the same IID, etc.

> The other thing I would like to mention is that the specifics of use
> of ESP etc are solutions. I am
> hoping to produce a crisp problem statement document.

Yes, indeed it is useful to avoid going into the solution space. However,
I would like the document to talk about the properties and possibilities
of *current* solutions. E.g., if you configure your network this way then
it implies that for the location privacy. Such a description is very useful
when evaluating the need for future solutions in this space.

>>> Whenever it is involved
>>>   in IP communication, its correspondents can see an IP address valid
>>>   on the home network.  Elaborating further, the users involved in peer
>>>   - peer communication are likely to see a user-friendly identifier
>>>   such as a SIP URI, and the communication end-points in the IP
>>>   stack will see IP addresses.  Users uninterested in or unaware of
>>>   IP communication details will not see any difference when the MN
>>>   acquires a new IP address.  Of course any user can ``tcpdump'' or
>>>   ``ethereal'' a session, capture IP packets and map the MN's IP
>>>   address to an approximate geo-location.  When this mapping reveals a
>>>   ``home location'' of the user, the correspondent can conclude that
>>>   the user has not roamed.
>>>   
>>
>>
>> This does not appear to follow. Assuming there's bidirectional tunneling
>> going on, the user is unaware of possible roaming.
>>
>>  
>>
> This paragraph is about the user being at home though.."Consider a
> Mobile Node at its home network..."

Ah, I see. Perhaps you could delete the sentence about the
correspondent node's conclusion.

>>>   The above description is valid regardless of whether a Home Address
>>>   is static or is dynamically allocated.   
>>
>>
>> Hmm... this seems to need more explanation or perhaps a more in-depth
>> treatment. Getting a dynamically allocated home address is similar to
>> running RFC 3041. If you do that, and employ different care-of addresses
>> for your different communications, it seems that you will be able
>> provide better location privacy protection, no?
>>
> The sentence above ("The above description is valid ..") is used in
> the context of the rest of the
> section. It is saying that the granularity of mapping the HoA (either
> dynamically assigned or statically
> assigned) to a geo-location is almost the same (which is stated in the
> sentence that follows the above
> sentence). This is because the network prefix maps to the same
> physical location.
>
> It's the same thing with 3041. When you combine that with different
> CoAs, it does not change the
> problem fundamentally; it's perhaps one way to deal with the problem.
> The basic problem is:
>
> - revealing HoA with global scope, no matter how it is assigned, to an
> on-looker compromises
>  location privacy.
> - revealing CoA together with HoA reveals to a CN that the MN has
> roamed. Does not matter
>  how they are assigned.

Right, I see.

But location privacy problem doesn't exist in a vacuum. Whether you can
associate the location to a useful identity is the question. If you
change your
global identifier, then according to the definition you have in Section
1 there
appears to be no problem.

>>>   Finally, it is also worthwhile to note that both the Home Address
>>>   and the Care of Address could be subject to profiling, just as
>>>   any other user traffic.  However, applying existing techniques to
>>>   thwart profiling may have implications to Mobile IPv6 signaling
>>>   performance.  For instance, changing the Care of Address often would
>>>   cause additional Return Routability and binding management signaling.
>>>   And, changing the Home Address often has implications on IPSec
>>>   security association management.  These issues need to be addressed
>>>   in the solutions.
>>>   
>>
>>
>> Need to be? Perhaps the conclusion is a bit too quick. Changing
>> care of addresses "often" for privacy reasons would probably be
>> either much less often that a fast moving mobile node makes handovers,
>> or at least fairly infrequent, so is there need for optimizing the
>> process?
>
> Ah, if the CoA change does not happen often, there is nothing to do.
> Agree that there is no need
> to optimize the process. The intention was to note the cost of
> changing the CoA and HoA.
> How about the reword of the last sentence:
>
> "Solutions should be careful in considering the cost of change of
> either CoA or HoA on signaling.
> For instance, changing the Care of Address often would cause
> additional Return Routability and
> binding management signaling. And, changing the Home Address often has
> implications on IPsec
> security association management. These issues need to be addressed in
> the solutions."

This is better, but I would still like to see more discussion of what
situations current solutions can and can not handle.

>> The specific issue with IPsec SA management probably needs to
>> be spelled out too. For instance, if you used the same IKE SA for
>> everything, it would be kind of silly to worry about privacy. So
>> that implies multiple IKE SAs.
>>
> Would you consider this a "profiling" problem or "location privacy"
> problem?

The SA management is basically a profiling problem. But if you
explain what current mechanisms can do for the protection of
your location privacy, you may end up explaining that changing,
e.g., home address is not sufficient if you still use the same IKE SA.

>> Missing stuff: I would have expected a good summary of conditions under
>> which location privacy is not a problem and a set of recommendations
>> on how networks and policies should be set up to prevent location
>> disclosure.
>>
>>  
>>
> The recommendation is what I am hoping the solutions draft will provide.
> Compared to privacy at large, Mobile IP introduces a specific problem
> due to the use of HoA and CoA.
> When a global identifier such as HoA is used from visited networks,
> on-lookers can figure out
> roaming. When HoA is used in conjunction with CoA, a CN can figure out
> that the MN has
> roamed. This specific problem is what this ID is trying to specify.
>
> I see the above problem existing wherever Mobile IP is supported
> regardless of network
> conditions. We can issue guidelines such as "use ESP in reverse
> tunneling to hide HoA", and that's
> what I am hoping to have in the solutions document (which will also
> address route optimization's
> implications).

Ah. Is there a MOBOPTS solution draft that I can go read?

Many of my issues above are related to the scope of the document,
and they go away if we only define the problem without considering
to what extent it can be mitigated with the current Mobile IPv6 protocol.
I think the document would be more useful, if it did the latter. But we
can talk about that.

--Jari



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



From mip6-bounces@ietf.org Fri Jul 07 15:08:23 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fyvgb-0001xM-1t; Fri, 07 Jul 2006 15:08:21 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FyvgZ-0001v6-M7
	for mip6@ietf.org; Fri, 07 Jul 2006 15:08:19 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FyvgZ-0002wu-KS
	for mip6@ietf.org; Fri, 07 Jul 2006 15:08:19 -0400
Received: from smtp16.orange.fr ([193.252.23.89])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Fyvaq-0000s1-4a
	for mip6@ietf.org; Fri, 07 Jul 2006 15:02:26 -0400
Received: from wwinf1613 (wwinf1613 [172.22.147.57])
	by mwinf1601.orange.fr (SMTP Server) with ESMTP id 88AD97000085
	for <mip6@ietf.org>; Fri,  7 Jul 2006 21:02:16 +0200 (CEST)
X-ME-UUID: 20060707190216559.88AD97000085@mwinf1601.orange.fr
Message-ID: <16578861.1152298936549.JavaMail.www@wwinf1613>
From: Eric Njedjou <eric.ntonfo@wanadoo.fr>
To: "mip6  [mip6]" <mip6@ietf.org>
Mime-Version: 1.0
X-Originating-IP: [67.68.249.59]
X-Wum-Nature: EMAIL-NATURE
X-WUM-FROM: |~|
X-WUM-TO: |~|
X-WUM-REPLYTO: |~|
Date: Fri,  7 Jul 2006 21:02:16 +0200 (CEST)
X-Spam-Score: -2.1 (--)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Subject: [Mip6] GOMM ad-hoc BOF in Montreal
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: eric.ntonfo@wanadoo.fr
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0247507753=="
Errors-To: mip6-bounces@ietf.org

--===============0247507753==
Content-Type: multipart/alternative; 
	boundary="----=_Part_119998_29161593.1152298936496"

------=_Part_119998_29161593.1152298936496
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

 
Dear all,
Following the Dallas IETF ad-hoc meeting on "the right mobility architecture for the Internet", strong interest was given to the gloabl IP mobility management problem that was presented. As a follow-up, Julien Riera, Telemaco Melia, Jouni Korhonen and I are setting up a second ad-hoc meeting during the upcoming Montreal IETF.
Meeting title GlObal IP Mobility Management ad-hoc BOF (GOMM)
Date: Monday, 10th of July
Time: 7pm50 - 8 pm 50
Room: TBD 
---------------------------------------------------
Agenda:
1)Introduction and wrap-up (5 min): Eric Njedjou
2Network Initiated handovers: problem statement (15min): Telemaco Melia
draft-melia-mobopts-niho-ps-01.txt 
3) Problem statement for Global IP Mobility Management (25 min): Eric Njedjou
draft-njedjou-globalmm-ps-00.txt
4)Better Understanding 3GPP requirements on IP mobility at IETF (5min): 
5)Conclusions and next steps (mailing list set-up announcement, official BOF plan for November,...) (10 min): Eric Njedjou
-------------------------------------------------------
The purpose of this ad-hoc meeting is to extend the presentation of the problem to a wider audience than in Dallas and foster more discussions.
draft-njedjou-globalmm-ps-00.txt has been updated based on reviews and comments as provided by many folks.
Thank you in advance for participating to this "GOMM" ad-hoc BOF discussions
Best Regards

Eric Njedjou 
------=_Part_119998_29161593.1152298936496
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

<P> </P>
<P>Dear all,</P>
<P>Following the Dallas IETF ad-hoc meeting on "the right mobility architecture for the Internet", strong interest was given to the gloabl IP mobility management problem that was presented. As a follow-up, Julien Riera, Telemaco Melia, Jouni Korhonen and I are setting up a <B>second ad-hoc meeting during the upcoming Montreal IETF</B>.</P><B>
<P>Meeting&nbsp;title</B> <U>G</U>l<U>O</U>bal IP <U>M</U>obility <U>M</U>anagement ad-hoc BOF (GOMM)</P><B>
<P>Date:</B> Monday, 10th of July</P><B>
<P>Time:</B> 7pm50 - 8 pm 50</P><B>
<P>Room:</B> TBD </P><B>
<P>---------------------------------------------------</P>
<P>Agenda:</P></B>
<P>1)Introduction and wrap-up (5 min): <I>Eric Njedjou</P></I>
<P>2Network Initiated handovers: problem statement (15min): <I>Telemaco Melia</P></I>
<P>draft-melia-mobopts-niho-ps-01.txt </P>
<P>3) Problem statement for Global IP Mobility Management (25 min): <I>Eric Njedjou</P></I>
<P>draft-njedjou-globalmm-ps-00.txt</P>
<P>4)Better Understanding 3GPP requirements on IP mobility at IETF&nbsp;(5min): </P>
<P>5)Conclusions and next steps (mailing list set-up announcement, official BOF plan&nbsp;for November,...) (10 min):<I> Eric Njedjou</P></I>
<P>-------------------------------------------------------</P>
<P>The purpose of this ad-hoc meeting is to extend the presentation of the problem to a wider audience than in Dallas and foster more discussions.</P>
<P>draft-njedjou-globalmm-ps-00.txt has been updated based on reviews and comments as provided by many folks.</P>
<P>Thank you in advance for participating to this "GOMM" ad-hoc BOF discussions</P>
<P>Best Regards</P>
<P>&nbsp;</P>
<P>Eric Njedjou </P>
<P><BR><BR></P>
------=_Part_119998_29161593.1152298936496--



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

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

--===============0247507753==--





From mip6-bounces@ietf.org Fri Jul 07 19:01:17 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FyzJr-000379-Ow; Fri, 07 Jul 2006 19:01:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FyzJr-000374-5z
	for mip6@ietf.org; Fri, 07 Jul 2006 19:01:07 -0400
Received: from key1.docomolabs-usa.com ([216.98.102.225]
	helo=fridge.docomolabs-usa.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FyzJp-0002US-Pu
	for mip6@ietf.org; Fri, 07 Jul 2006 19:01:07 -0400
Message-ID: <0b3f01c6a219$693dfcb0$616015ac@dcml.docomolabsusa.com>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Jari Arkko" <jari.arkko@kolumbus.fi>,
	"Rajeev Koodli" <rajeev.koodli@nokia.com>
References: <44A82617.9060400@kolumbus.fi>
Subject: Re: [Mip6] some comments on draft-ietf-mip6-location-privacy-ps
Date: Fri, 7 Jul 2006 15:51:55 -0700
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Spam-Score: 4.2 (++++)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

> I happened to read this draft today and had a few comments:
>
>>    This document is only concerned with IP Address Location Privacy in
>>    the presence of IP Mobility, as applied to Mobile IPv6.  It does not
>>    address the overall profiling problem.  Specifically, it does not
>>    concern itself with MAC addresses.  Some other work may address the
>>    problem of profiling IP and MAC identifiers (see for instance [1]).
>
> This reads a little bit like MAC addresses would be the only problem.
> I presume that there are other location privacy issues beyond those
> listed in this draft, and that there are plenty of other privacy issues.
> Suggested rewrite:
>
>   This document is only concerned with IP address location privacy in
>   the context of Mobile IPv6.  It does not address the overall privacy
>   problem. For instance, it does not address privacy issues related to
>   MAC addresses or the relationship of IP and MAC addresses [1].
>

I would recommend saying "location privacy" here. I think there is a 
distinction between location privacy and privacy in general. Privacy in 
general is a much larger topic, which this draft doesn't really address.

            jak





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



From mip6-bounces@ietf.org Fri Jul 07 19:50:31 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fz05e-0007VW-Aa; Fri, 07 Jul 2006 19:50:30 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fz05d-0007VQ-L8
	for mip6@ietf.org; Fri, 07 Jul 2006 19:50:29 -0400
Received: from mgw-ext13.nokia.com ([131.228.20.172])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fz05d-0002bv-5B
	for mip6@ietf.org; Fri, 07 Jul 2006 19:50:29 -0400
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211])
	by mgw-ext13.nokia.com (Switch-3.1.8/Switch-3.1.7) with ESMTP id
	k67NoRP8011239; Sat, 8 Jul 2006 02:50:28 +0300
Received: from esebh002.NOE.Nokia.com ([172.21.138.77]) by
	esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 8 Jul 2006 02:50:26 +0300
Received: from [172.18.141.192] ([172.18.141.192]) by esebh002.NOE.Nokia.com
	with Microsoft SMTPSVC(5.0.2195.6881); 
	Sat, 8 Jul 2006 02:50:26 +0300
Message-ID: <44AEF340.5010305@iprg.nokia.com>
Date: Fri, 07 Jul 2006 16:50:24 -0700
From: Rajeev Koodli <rajeev@iprg.nokia.com>
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>
Subject: Re: [Mip6] some comments on draft-ietf-mip6-location-privacy-ps
References: <44A82617.9060400@kolumbus.fi> <44ABFF17.90508@iprg.nokia.com>
	<44AD64E0.6040908@piuha.net>
In-Reply-To: <44AD64E0.6040908@piuha.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 07 Jul 2006 23:50:26.0475 (UTC)
	FILETIME=[1EB947B0:01C6A220]
X-Spam-Score: 1.1 (+)
X-Scan-Signature: 7da5a831c477fb6ef97f379a05fb683c
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>,
	Rajeev Koodli <rajeev.koodli@nokia.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org


Hi Jari,

yes, there is a MobOpts solutions document. It is addressing the problems
specified in the ps document.

Regarding scoping, I see your point. What you can do with current MIP6
protocol is to use reverse tunneling with ESP. However, with RR and BU/BAck
messages, you do expose the HoA. Beyond that, I am open to your thoughts
on what could be done with current protocol.

more comments inline..

Jari Arkko wrote:

>But I agree that you need to draw a line somewhere where you stop
>describing the details. But please provide some details at least
>as examples. For instance, you could mention HAO, IPsec/IKE SPIs,
>the use of the same IID, etc.
>
>  
>
Ok. This is the profiling of fixed fields. I will write some text. If 
you have something in
mind, that's welcome too :-)

>Yes, indeed it is useful to avoid going into the solution space. However,
>I would like the document to talk about the properties and possibilities
>of *current* solutions. E.g., if you configure your network this way then
>it implies that for the location privacy. Such a description is very useful
>when evaluating the need for future solutions in this space.
>
>  
>
Could you elaborate further?

(I think the primary problem here is the disclosure of HoA and CoA. 
These are the addresses
which have global scope and are specific to MIP. And, they can 
compromise location privacy.
I don't know what kind of network settings you have in mind which would 
allow hiding them)

>Ah, I see. Perhaps you could delete the sentence about the
>correspondent node's conclusion.
>
>  
>
Ok, I will see how to rephrase it.

>Right, I see.
>
>But location privacy problem doesn't exist in a vacuum. Whether you can
>associate the location to a useful identity is the question. If you
>change your
>global identifier, then according to the definition you have in Section
>1 there
>appears to be no problem.
>
>  
>
You could change HoA, but if the network prefix maps to a known 
location, then you can figure
out that some user from ISP X has roamed to network Y.

>>"Solutions should be careful in considering the cost of change of
>>either CoA or HoA on signaling.
>>For instance, changing the Care of Address often would cause
>>additional Return Routability and
>>binding management signaling. And, changing the Home Address often has
>>implications on IPsec
>>security association management. These issues need to be addressed in
>>the solutions."
>>    
>>
>
>This is better, but I would still like to see more discussion of what
>situations current solutions can and can not handle.
>
>  
>
hmm.. There are two issues here. First, what's the problem. And, second, 
what are the existing
solutions. Are you saying that the problem does not exist under certain 
assumptions or or you saying
there are solutions? If it's the latter, I agree; and the scope of this 
document is to merely specify the
problem and leave out existing and possibly new mechanisms to the 
solutions draft.

>The SA management is basically a profiling problem. But if you
>explain what current mechanisms can do for the protection of
>your location privacy, you may end up explaining that changing,
>e.g., home address is not sufficient if you still use the same IKE SA.
>
>  
>
In that case, how is the problem specific to MIP6? (I realize MIP6 uses 
IKE, but so do many
other protocols).

>Ah. Is there a MOBOPTS solution draft that I can go read?
>
>  
>
draft-irtf-mobopts-location-privacy-solutions-02.txt

It still needs work. And, your input here is useful.

>Many of my issues above are related to the scope of the document,
>and they go away if we only define the problem without considering
>to what extent it can be mitigated with the current Mobile IPv6 protocol.
>I think the document would be more useful, if it did the latter. But we
>can talk about that.
>
>  
>
Right. The scope I have assumed is primarily MIP6 addresses and location 
privacy. In the solutions
document, we are considering the implications of profiling fields such 
as the Sequence Number.
I tend to think that the solutions, including the existing ones, belong 
to the solutions document. So, if we
agree on the problems here, I think we can happily consider the 
solutions in the mobopts document.

Regards,

-Rajeev

>--Jari
>
>
>  
>


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



From mip6-bounces@ietf.org Sun Jul 09 06:54:16 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FzWvJ-0000UJ-IV; Sun, 09 Jul 2006 06:54:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FzWvI-0000UD-GJ
	for mip6@ietf.org; Sun, 09 Jul 2006 06:54:00 -0400
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FzWvH-0006UD-5f
	for mip6@ietf.org; Sun, 09 Jul 2006 06:54:00 -0400
Received: from p130.piuha.net (localhost [127.0.0.1])
	by p130.piuha.net (Postfix) with ESMTP id CA1F1898A9;
	Sun,  9 Jul 2006 13:53:54 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id 3E1F18989C;
	Sun,  9 Jul 2006 13:53:49 +0300 (EEST)
Message-ID: <44B0E02F.2080003@piuha.net>
Date: Sun, 09 Jul 2006 13:53:35 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Mozilla Thunderbird 1.0.8 (X11/20060502)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Francis Dupont <Francis.Dupont@point6.net>
References: <200607052153.k65LrEdM093651@givry.rennes.enst-bretagne.fr>
In-Reply-To: <200607052153.k65LrEdM093651@givry.rennes.enst-bretagne.fr>
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: c54bc2f42d02429833c0ca4b8725abd7
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>
Subject: [Mip6] Re: AD review of draft-ietf-mip6-cn-ipsec
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi Francis,

Continuing the discussion inline:

>To finish the main security concern against RO is MN impersonization
>and solutions based on strong authentications will be always far
>more secure than RR...
>  
>
It is not always a strictly ordered relationship. For instance,
RFC 4449 is more secure in terms of authenticating the
Binding Updates, but less secure in terms of  making it
possible for the mobile node to lie about its address.

>   (The assumptions include, for instance, that on-path attackers can
>   disturb your communications. They can already do so without Mobile
>   IPv6, too...)
>   
>=> no, impersonation by an attacker at the right place in the path(s)
>is a real (and first order) issue. 
>
This is true but you have to remember the limits of our
technology EVEN if you use things like RFC 4449. For instance,
on-path attackers will see your data packets. On-path attackers
will generally be able to DoS your connection by, e.g., dropping
packets. Or copy your packets elsewhere. Adding better security
for the mobility signaling helps protect the mobility signaling,
but it isn't always clear that it provides more protection if you
think about the entire system; Binding Updates can be secure
but you are still vulnerable for on-path attackers. What does
help is end-to-end protection of your traffic (but that's at least
partially an orthogonal issue).

>The RR was proposed because there
>is no general solution to this problem but you can't assume than
>the limits of RO about security are acceptable by everybody.
>So we have an explicit alternate mechanism (RFC 4449), another one
>using the standard network layer security (CN-IPsec) and perhaps
>will get something from the CGA & co stuff. BTW this was known at
>the RFC 3775 time so provisions were made for further (at that time)
>work...
>
>   >    -  no care-of address test is required when ingress filtering can
>
>=> note that ingress filtering and return routability check are two
>versions of the same mechanism, in particular both share the same
>limit (no defense against an attacker at the right place in the path)
>The main difference is that ingress filtering is passive, which is better
>when you can trust it is used at the right place, when RR is active,
>so more expensive but doesn't rely on someone else's policy.
>  
>
Right.

To conclude the discussion about the security properties, its
clear that there are security differences between cn-ipsec and
RR. The security of the cn-ipsec mechanism needs to be described
in the draft, obviously. And if you want you can also discuss the
relationship to RR. In both cases the description needs to be
accurate, complete, and formulated in technical terms. I think
we agree that changes and more text is needed, so perhaps it
would be best for you to write the next version and then we
can take another look.

>BTW in my new job we use labelization which makes ingress filtering
>seems like a toy (:-)...
>To finish the lack of ingress filtering general deployment is a major
>(i.e., first order) threat against the Internet itself, so it is a minor
>(i.e., second order) threat against mobility.
>
>   >      as well as the support of real alternate care-of addresses.
>
>=> this is the real reason I introduced the state cookie RR: at the
>beginning I simply forbid real alternate care-ofs but it was not
>very clear if they would be never needed...
>To use it when it is not required is a concession to the indirect
>flooding attack paranoia so I don't understand why you'd like to
>reject it (or it is for a formal concern?)
>  
>
The concern I had was only formal at this stage. Your draft needs to be
self-contained
or contain references to existing RFCs (or to drafts that are known to
become
RFCs soon). Otherwise your draft would sit in the RFC Editor queue forever,
waiting for references to become stable.

>   If you cut away the state cookie reference (as suggested earlier),
>   I would suggest that you include a statement similar to RFC 4449
>   about the trust needed to take care-of addresses without verifying
>   them.
>   
>=> I don't like the RFC 4449 to deal with the problem... My idea is
>to provide an easy tool to perform the RR test when the CN believes
>there can be a problem, i.e., not when ingress filtering is deployed,
>not when the MN can be trusted, etc, i.e., not only the check is at
>the initiative of the CN but the CN can choose its default policy.
>
>   This would work, but I worry about the lack of details here. How would
>   the peers know they are using RFC 3972 to authenticate in IKE? How are
>   the CGA parameters transported? Suggestion: if we can not provide
>   full details, leave this part to another document.
>   
>=> suggestion: move it to a not normative appendix?
>  
>
I would like to see it either officially defined or dropped. Note: I
have not
reviewed the state cookie draft recently, so I don't know if it would bring
new technical issues to worry about. My initial reaction was that you
should drop the functionality and then publish later the cookie thing
as an extension.

>   >    -  in order to avoid granting any extra privilege by a side effect of
>   >       using IPsec
>
>=> two extra comments:
> - I've already seen cases where "there is IPsec" was changed into
> "now everything is safe so may be done", i.e., the pitfall is real.
> - a good security admin should understand the issue and just avoid
> IPsec for the only protection of mobility (i.e., as I've explained
> in the introduction of this message, the protection of IPsec is
> not enough as a reason to jump to IPsec).
>  
>
Yes -- please explain these things in the document.

>   >    But any stronger mechanism (i.e., more secure than the
>   >    return routability procedure) MAY be used, including of course IPsec
>   >    (cf. [RFC3775] Appendix 3 "New Authorization Methods").
>   
>=> I'll put a *may* to stress it without interfering with keywords.
>  
>
OK.

>   
>   >    This document uses the "MUST", "SHOULD", "MAY", ..., key words
>   >    according to [RFC2119].  IKE terminology is copied from IKEv2
>   >    [IKEv2].
>   
>   Please use the standard template keyword statement:
>   
>=> if the standard template is required it should be a macro in xml2rfc!
>  
>
Perhaps, but our general policy is that you have to pass idnits before
getting through AD review phase.  The above is a part of the idnits check.

--Jari


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



From mip6-bounces@ietf.org Sun Jul 09 19:52:24 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fzj4O-0006xJ-Sl; Sun, 09 Jul 2006 19:52:12 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fzj4N-0006xE-RL
	for mip6@ietf.org; Sun, 09 Jul 2006 19:52:11 -0400
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fzj4L-0000Yh-Hl
	for mip6@ietf.org; Sun, 09 Jul 2006 19:52:11 -0400
Received: from il06exr03.mot.com (il06exr03.mot.com [129.188.137.133])
	by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id k69Nq6Qn013545;
	Sun, 9 Jul 2006 16:52:06 -0700 (MST)
Received: from [10.129.40.14] ([10.129.40.14])
	by il06exr03.mot.com (8.13.1/8.13.0) with ESMTP id k69Nq4wb002633;
	Sun, 9 Jul 2006 18:52:05 -0500 (CDT)
Message-ID: <44B196A2.6090303@motorola.com>
Date: Mon, 10 Jul 2006 01:52:02 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@kolumbus.fi>
Subject: Re: [Mip6] new charter proposal
References: <44A82F67.6080105@kolumbus.fi>	<eaa74a7e0607040838i3585c1e1y9520f2c9ac518f64@mail.gmail.com>
	<44AAAD5B.5010203@kolumbus.fi>
In-Reply-To: <44AAAD5B.5010203@kolumbus.fi>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAQAAAAQ=
X-White-List-Member: TRUE
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Jari Arkko wrote:
> Hi Gerardo,
> 
>> thanks for providing the charter proposal. One question: is there
>> any plan to produce docs on bootstrapping of rfc4285?
>> 
>> In the charter proposal it is mentioned that the rationale behind 
>> rfc4285 will be produced. Are we going to take a step forward and 
>> specify bootstrapping mechanisms also for rfc4285?
> 
> The design rationale was really a separate thing. The version of the
> charter that I posted does not include coverage of RFC 4285 in other
> ways.
> 
> But its a good question what the scope of the bootstrapping work
> should be. What does the working group think? How did we define it in
> the problem statement?

I think the current bootstrapping text in the proposed Charter leaves
place for bootstrapping for/with rfc4285 (auth for MIP6).  I think the
current text is not limited to the drafts split or integrated.

I also continue to think that a bootstrapping HA address/HoA  with 
DHAAD+MPD (not based on DNS nor DHCP) makes sense and may be accomodated 
by proposed Charter text.

> Ideally, I would not like to see that RFC 4285 causes divergent 
> solutions for every other part of the technology along with it. Can 
> we design our DHCP options and AAA interfaces so that they don't care
> whether its IKEv2 or authentication option at the bottom?

Sounds a logical suggestion.

Alex


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



From mip6-bounces@ietf.org Sun Jul 09 19:56:56 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fzj8x-0007uB-DZ; Sun, 09 Jul 2006 19:56:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fzj8v-0007tG-Da
	for mip6@ietf.org; Sun, 09 Jul 2006 19:56:53 -0400
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fzj8u-0001D5-5V
	for mip6@ietf.org; Sun, 09 Jul 2006 19:56:53 -0400
Received: from il06exr01.mot.com (il06exr01.mot.com [129.188.137.131])
	by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id k69NulDT013688;
	Sun, 9 Jul 2006 16:56:47 -0700 (MST)
Received: from [10.129.40.14] ([10.129.40.14])
	by il06exr01.mot.com (8.13.5/8.13.0) with ESMTP id k69Nujea008055;
	Sun, 9 Jul 2006 18:56:46 -0500 (CDT)
Message-ID: <44B197BB.2010003@motorola.com>
Date: Mon, 10 Jul 2006 01:56:43 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: "Soliman, Hesham" <hsoliman@qualcomm.com>
Subject: Re: [Mip6] new charter proposal
References: <7EB20EA0938B4D42A2D82689365C9B7A07CE58@NAEX14.na.qualcomm.com>
In-Reply-To: <7EB20EA0938B4D42A2D82689365C9B7A07CE58@NAEX14.na.qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAQAAAAQ=
X-White-List-Member: TRUE
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Soliman, Hesham wrote:
> 
>>> http://www.ietf.org/internet-drafts/draft-ietf-mip6-dsmip-pr
> oblem-02.txt
>>> 
>>> It's in the current charter. Is this covered under the DSMIP work
>>>  anyway?
>>> 
>>> 
>> Good question. I wouldn't mind having a problem statement document 
>> too if the group wants that. Question: there's a brief description
>> of the problem/motivation/scope/scenarios in the beginning of the 
>> solution draft. Is that insufficient?
> 
> => Depends on who you ask :). Given the amount of questions that we 
> continue to get about the problem and why this is needed I would
> think it's insufficient. I think this will be a good document to
> point people to when these issues come up. Thomas just asked for the
> same thing recently on the list. So I think it's helpful to have it.
> 
Could it contain the problem statement from draft-wakikawa and from the
scenarios draft?

The only problem in draft-dsmip-problem that the reader is left with is
that it is inefficient to have both MIP4 and MIP6 running on the mobile.
  I don't think it is.  Draft-wakikawa has some wording on multiple
encapsulation as a problem, which makes more sense to me, IMHO.

Alex


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



From mip6-bounces@ietf.org Sun Jul 09 20:09:50 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FzjLR-0006vq-Gz; Sun, 09 Jul 2006 20:09:49 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FzjLQ-0006vd-CG
	for mip6@ietf.org; Sun, 09 Jul 2006 20:09:48 -0400
Received: from motgate5.mot.com ([144.189.100.105])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FzjLO-0001oJ-Vz
	for mip6@ietf.org; Sun, 09 Jul 2006 20:09:48 -0400
Received: from az33exr04.mot.com (az33exr04.mot.com [10.64.251.234])
	by motgate5.mot.com (8.12.11/Motgate5) with ESMTP id k6A09TuN020738;
	Sun, 9 Jul 2006 17:09:33 -0700 (MST)
Received: from [10.129.40.14] ([10.129.40.14])
	by az33exr04.mot.com (8.13.1/8.13.0) with ESMTP id k6A09Q4s012252;
	Sun, 9 Jul 2006 19:09:27 -0500 (CDT)
Message-ID: <44B19AB4.5000905@motorola.com>
Date: Mon, 10 Jul 2006 02:09:24 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
Subject: Re: [Mip6] new charter proposal
References: <7EB20EA0938B4D42A2D82689365C9B7A07CE55@NAEX14.na.qualcomm.com>	<44ABB053.6010809@piuha.net>
	<44AC41AB.2080003@azairenet.com>
In-Reply-To: <44AC41AB.2080003@azairenet.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAQAAAAQ=
X-White-List-Member: TRUE
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>, "Soliman,
	Hesham" <hsoliman@qualcomm.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Vijay Devarapalli wrote:
> Jari Arkko wrote:
>> Soliman, Hesham wrote:
>> 
>>> Hi Jari, I didn't see a specific mention of:
>>> 
>>> http://www.ietf.org/internet-drafts/draft-ietf-mip6-dsmip-problem-02.txt
>>> 
>>> 
>>> It's in the current charter. Is this covered under the DSMIP work
>>>  anyway?
>>> 
>>> 
>> Good question. I wouldn't mind having a problem statement document 
>> too if the group wants that. Question: there's a brief description
>> of the problem/motivation/scope/scenarios in the beginning of the 
>> solution draft. Is that insufficient?
> 
> FWIW, I think the problem description in 
> draft-ietf-mip6-nemo-v4traversal-02.txt is sufficient.

Which section please?  I can't seem to find one.

Or you mean draft-ietf-mip6-dsmip-problem-02.txt?  That which lists
problems "implementation burdens", "operational burdens", "mm
inefficiencies" and "impossibility of maintaining IP connectivity".

Alex


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



From mip6-bounces@ietf.org Mon Jul 10 10:30:30 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FzwmF-0003Om-Jj; Mon, 10 Jul 2006 10:30:23 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FzwmE-0003OF-C4
	for mip6@ietf.org; Mon, 10 Jul 2006 10:30:22 -0400
Received: from mail1.azairenet.com ([66.92.223.4] helo=bart.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FzwmD-0001zD-3t
	for mip6@ietf.org; Mon, 10 Jul 2006 10:30:22 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] new charter proposal
Date: Mon, 10 Jul 2006 07:30:18 -0700
Message-ID: <C8E1D942CB394746BE5CFEB7D97610E701BC986F@bart.corp.azairenet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] new charter proposal
Thread-Index: AcajtSj6mo6vAG7vSmKLR3O03mBMGwAeAssg
From: "Vijay Devarapalli" <Vijay.Devarapalli@AzaireNet.com>
To: "Alexandru Petrescu" <alexandru.petrescu@motorola.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>, "Soliman,
	Hesham" <hsoliman@qualcomm.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

> > FWIW, I think the problem description in=20
> > draft-ietf-mip6-nemo-v4traversal-02.txt is sufficient.
>=20
> Which section please?  I can't seem to find one.

most of section 1, 1.1 and 1.2. there is no separate=20
problem statement section.

Vijay

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



From mip6-bounces@ietf.org Mon Jul 10 13:10:27 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FzzH1-0004as-9t; Mon, 10 Jul 2006 13:10:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FzzGz-0004ai-F5
	for mip6@ietf.org; Mon, 10 Jul 2006 13:10:17 -0400
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FzzGw-0004Zn-PX
	for mip6@ietf.org; Mon, 10 Jul 2006 13:10:17 -0400
Received: from wee.isi.edu (wee.isi.edu [128.9.168.112])
	by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id k6AH9Gu21846
	for <mip6@ietf.org>; Mon, 10 Jul 2006 10:09:16 -0700 (PDT)
From: Wei Ye <weiye@ISI.EDU>
To: mip6@ietf.org
Content-Type: text/plain; charset=UTF-8
Date: Mon, 10 Jul 2006 10:09:10 -0700
Message-Id: <1152551350.9960.19.camel@wee.isi.edu>
Mime-Version: 1.0
X-Mailer: Evolution 2.6.2 (2.6.2-1.fc5.5) 
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: weiye@isi.edu
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by boreas.isi.edu id
	k6AH9Gu21846
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 90e8b0e368115979782f8b3d811b226b
Subject: [Mip6] ACM SenSys 2006: Travel Grants, Posters, Demos and Workshops
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

ACM SenSys 2006: Travel Grants, Posters, Demos and Workshops

Our Apologies if you have received multiple copies of this email.

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

The 4th ACM Conference on Embedded Networked Sensor Systems
November 1-3, 2006
Boulder, Colorado, USA
http://sensys.acm.org/2006/

Sponsored by ACM SIGCOMM, SIGMOBILE, SIGARCH, SIGOPS, SIGMETRICS and =20
SIGBED; with support from NSF.

The 4th ACM Conference on Embedded Networked Sensor Systems (SenSys) =20
is a highly selective, single-track forum for the presentation of =20
research results on systems issues in the area of embedded, networked=20
sensors. Distributed systems based on networked sensors and actuators =20
with embedded computation capabilities allow for an instrumentation =20
of the physical world at an unprecedented scale and density, thus =20
enabling a new generation of monitoring and control applications. =20
This conference provides an ideal venue to address the research =20
challenges facing the design, deployment, use, and fundamental limits =20
of these systems. Sensor networks require contributions from many =20
fields, from wireless communication and networking, embedded systems =20
and hardware, distributed systems, data management, and applications, =20
so we welcome cross-disciplinary work.


ACM SenSys 2006: Student Travel Grants
--------------------------------------

We will assist around 17 US-based graduate students to attend this
meeting. The amount of support provided to each student will be $881=20
on average, or the actual documented amount of expenses, whichever is
less. It covers travel, lodging, registration, and meals. All travel
support is made possible by a travel grant from the US National=20
Science Foundation (NSF).
    =20
Important Dates

Travel applications due: September 1, 2006
Notification of awards: September 8, 2006
Acceptance by recipients: September 15, 2006

Application Procedure

Applications for the travel award should be received electronically by
Haiyun Luo (haiyun@cs.uiuc.edu) by Friday, September 1, 2006. Please
make sure that you receive an email confirmation of your submission.
An application will consist of the student's vita, a letter from the
student, and a letter from the student's advisor.

The letter from the student should include:

  1. A brief summary of research interests and accomplishments to date
  2. A description of areas reflected in the SenSys 2006 program that=20
     would impact the students research
  3. Importance of attend the conference to the students research
     activities =20

In addition, the student's advisor should send a letter of
recommendation to the committee. It should include:=20

  1. Confirmation that the student is a Ph.D. candidate in good=20
     standing
  2. The suitability SenSys 2006 program to the students research area
  3. Ways in which attending the conference would benefit the
     particular student=20
  4. The strengths and potential contributions of the student.

The awards will be announced by Friday, September 8, 2006. Recipients
will be required to accept the award by Friday, September 15, 2006, so
that alternates can be notified in the event that a recipient
declines.

Award Selection Committee

Nirupama Bulusu, Portland State U.
Deepak Ganesan, UMass
Haiyun Luo, UIUC
Shivakant Mishra, U. of Colorado
Sergio Servetto, Cornell=20


CALL FOR POSTERS
----------------

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

POSTER SUBMISSION INSTRUCTIONS

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

sensys06-poster-chairs@isi.edu

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

IMPORTANT DATES

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

BASIC INFORMATION ABOUT POSTERS

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

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

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


CALL FOR DEMOS
--------------

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

DEMO SUBMISSION INSTRUCTIONS

Please send a two-page description of your demo to=20

sensys06-demo-chairs@isi.edu

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

IMPORTANT DATES

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

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


Workshop on Distributed Smart Cameras (DSC-06)
----------------------------------------------

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

Boulder, Colorado, USA
October 31, 2006

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

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

Topics of interest include, but are not limited to:

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

Submission Instructions:

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

Important Dates:

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

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

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


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

Mobile Device Centric Sensory Networks and Applications

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

Boulder, Colorado, USA
October 31, 200

SCOPE

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

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

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

Topics of interest include but are not limited to:

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

WORKSHOP CO-ORGANIZERS

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

TECHNICAL PROGRAM COMMITTEE

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

IMPORTANT DATES

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

SUBMISSION INSTRUCTIONS

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

All papers should meet the following formatting rules:

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

Questions, inquiries

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



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



From mip6-bounces@ietf.org Mon Jul 10 15:50:40 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G01m5-0008I8-0t; Mon, 10 Jul 2006 15:50:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G01lj-00077V-6T; Mon, 10 Jul 2006 15:50:11 -0400
Received: from smtp16.orange.fr ([193.252.23.89])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1G01lh-0003LE-LP; Mon, 10 Jul 2006 15:50:11 -0400
Received: from wwinf1606 (wwinf1606 [172.22.147.33])
	by mwinf1603.orange.fr (SMTP Server) with ESMTP id 6B1E67000084;
	Mon, 10 Jul 2006 21:50:04 +0200 (CEST)
X-ME-UUID: 20060710195004438.6B1E67000084@mwinf1603.orange.fr
Message-ID: <6217835.1152561004426.JavaMail.www@wwinf1606>
From: Eric Njedjou <eric.ntonfo@wanadoo.fr>
To: "mip6  [mip6]" <mip6@ietf.org>, mipshop@ietf.org, netlmm@ietf.org
Mime-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_59819_31736026.1152561004412"
X-Originating-IP: [132.219.20.229]
X-Wum-Nature: EMAIL-NATURE
X-WUM-FROM: |~|
X-WUM-TO: |~||~||~|
X-WUM-REPLYTO: |~|
Date: Mon, 10 Jul 2006 21:50:04 +0200 (CEST)
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 68ba2b07ef271dba6ee42a93832cfa4c
Cc: 
Subject: [Mip6] GOMM Ad-Hoc BOF in Room 159a
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: eric.ntonfo@wanadoo.fr
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

------=_Part_59819_31736026.1152561004412
Content-Type: multipart/alternative; 
	boundary="----=_Part_59820_6139471.1152561004412"

------=_Part_59820_6139471.1152561004412
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi all,
The GOMM Ad-Hoc meeting will take place in Room 159a from 7p55 to 8pm50

Eric



> Message du 06/07/06 23:25
> De : "Eric Njedjou"=20
> A : mipshop@ietf.org, mip6@ietf.org, netlmm@ietf.org
> Copie =C3=A0 :=20
> Objet : [netlmm] GOMM Ad-Hoc BOF in Montreal
>=20
>=20
> Dear all,
> Following the Dallas IETF ad-hoc meeting on "the right mobility architect=
ure for the Internet", strong interest was given to the gloabl IP mobility =
management problem that was presented. As a follow-up, Julien Riera, Telema=
co Melia, Jouni Korhonen and I are setting up a second ad-hoc meeting durin=
g the upcoming Montreal IETF.
> Meeting title GlObal IP Mobility Management ad-hoc BOF (GOMM)
> Date: Monday, 10th of July
> Time: 7pm50 - 8 pm 50
> Room: TBD=20
> ---------------------------------------------------
> Agenda:
> 1)Introduction and wrap-up (5 min): Eric Njedjou
> 2Network Initiated handovers: problem statement (15min): Telemaco Melia
> draft-melia-mobopts-niho-ps-01.txt=20
> 3) Problem statement for Global IP Mobility Management (25 min): Eric Nje=
djou
> draft-njedjou-globalmm-ps-00.txt
> 4)Better Understanding 3GPP requirements on IP mobility at IETF (5min):=
=20
> 5)Conclusions and next steps (mailing list set-up announcement, official =
BOF plan for November,...) (10 min): Eric Njedjou
> -------------------------------------------------------
> The purpose of this ad-hoc meeting is to extend the presentation of the p=
roblem to a wider audience than in Dallas and foster more discussions.
> draft-njedjou-globalmm-ps-00.txt has been updated based on reviews and co=
mments as provided by many folks.
> Thank you in advance for participating to this "GOMM" ad-hoc BOF discussi=
ons
> Best Regards
> Eric Njedjou=20
>=20
>=20
>=20
> =20



Eric Njedjou


21, Square L=C3=A9on Bourgeois


35000 Rennes
------=_Part_59820_6139471.1152561004412
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<P>Hi all,</P>
<P>The GOMM Ad-Hoc meeting will take place in <STRONG>Room 159a</STRONG> fr=
om <STRONG>7p55 to 8pm50</STRONG><BR><BR>Eric<BR><BR><BR></P>
<BLOCKQUOTE style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #ff0=
000 2px solid">&gt; Message du 06/07/06 23:25<BR>&gt; De : "Eric Njedjou" <=
ERIC.NTONFO@WANADOO.FR><BR>&gt; A : mipshop@ietf.org, mip6@ietf.org, netlmm=
@ietf.org<BR>&gt; Copie =C3=A0 : <BR>&gt; Objet : [netlmm] GOMM Ad-Hoc BOF =
in Montreal<BR>&gt; <BR>&gt; <FONT size=3D2>
<P>&gt; Dear all,</P>
<P>&gt; Following the Dallas IETF ad-hoc meeting on "the right mobility arc=
hitecture for the Internet", strong interest was given to the gloabl IP mob=
ility management problem that was presented. As a follow-up, Julien Riera, =
Telemaco Melia, Jouni Korhonen and I are setting up a <B>second ad-hoc meet=
ing during the upcoming Montreal IETF</B>.</P><B>
<P>&gt; Meeting&nbsp;title</B> <U>G</U>l<U>O</U>bal IP <U>M</U>obility <U>M=
</U>anagement ad-hoc BOF (GOMM)</P><B>
<P>&gt; Date:</B> Monday, 10th of July</P><B>
<P>&gt; Time:</B> 7pm50 - 8 pm 50</P><B>
<P>&gt; Room:</B> TBD </P><B>
<P>&gt; ---------------------------------------------------</P>
<P>&gt; Agenda:</P></B>
<P>&gt; 1)Introduction and wrap-up (5 min): <I>Eric Njedjou</P></I>
<P>&gt; 2Network Initiated handovers: problem statement (15min): <I>Telemac=
o Melia</P></I>
<P>&gt; draft-melia-mobopts-niho-ps-01.txt </P>
<P>&gt; 3) Problem statement for Global IP Mobility Management (25 min): <I=
>Eric Njedjou</P></I>
<P>&gt; draft-njedjou-globalmm-ps-00.txt</P>
<P>&gt; 4)Better Understanding 3GPP requirements on IP mobility at IETF&nbs=
p;(5min): </P>
<P>&gt; 5)Conclusions and next steps (mailing list set-up announcement, off=
icial BOF plan&nbsp;for November,...) (10 min):<I> Eric Njedjou</P></I>
<P>&gt; -------------------------------------------------------</P>
<P>&gt; The purpose of this ad-hoc meeting is to extend the presentation of=
 the problem to a wider audience than in Dallas and foster more discussions=
.</P>
<P>&gt; draft-njedjou-globalmm-ps-00.txt has been updated based on reviews =
and comments as provided by many folks.</P>
<P>&gt; Thank you in advance for participating to this "GOMM" ad-hoc BOF di=
scussions</P>
<P>&gt; Best Regards</P>
<P>&gt; Eric Njedjou </P>
<P>&gt; </FONT><BR>&gt; <BR>&gt; </P>
<P>&gt; &nbsp;</P></BLOCKQUOTE>
<P><BR><BR></P>
<P>Eric Njedjou</P><BR>
<P>21, Square L=C3=A9on Bourgeois</P><BR>
<P>35000 Rennes</P>
------=_Part_59820_6139471.1152561004412--

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

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

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

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

------=_Part_59819_31736026.1152561004412--





From mip6-bounces@ietf.org Mon Jul 10 16:10:18 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G025B-00030y-Dc; Mon, 10 Jul 2006 16:10:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G0259-00030U-NK; Mon, 10 Jul 2006 16:10:15 -0400
Received: from smtp5.orange.fr ([193.252.22.26])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1G0258-00055D-7N; Mon, 10 Jul 2006 16:10:15 -0400
Received: from smtp16.orange.fr (mwinf1603 [172.22.147.25])
	by mwinf0505.orange.fr (SMTP Server) with ESMTP id 161AB740BC2C;
	Mon, 10 Jul 2006 21:52:11 +0200 (CEST)
Received: from wwinf1606 (wwinf1606 [172.22.147.33])
	by mwinf1603.orange.fr (SMTP Server) with ESMTP id 99F1A7000088;
	Mon, 10 Jul 2006 21:52:10 +0200 (CEST)
X-ME-UUID: 20060710195210630.99F1A7000088@mwinf1603.orange.fr
Message-ID: <29324215.1152561130617.JavaMail.www@wwinf1606>
From: Eric Njedjou <eric.ntonfo@wanadoo.fr>
To: "mip6  [mip6]" <mip6@ietf.org>, "mipshop  [mipshop]" <mipshop@ietf.org>,
	"netlmm  [netlmm]" <netlmm@ietf.org>
Mime-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_59838_13205823.1152561130604"
X-Originating-IP: [132.219.20.229]
X-Wum-Nature: EMAIL-NATURE
X-WUM-FROM: |~|
X-WUM-TO: |~||~||~|
X-WUM-REPLYTO: |~|
Date: Mon, 10 Jul 2006 21:52:10 +0200 (CEST)
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 68ba2b07ef271dba6ee42a93832cfa4c
Cc: 
Subject: [Mip6] GOMM Ad-Hoc BOF in Room 159a
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: eric.ntonfo@wanadoo.fr
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

------=_Part_59838_13205823.1152561130604
Content-Type: multipart/alternative; 
	boundary="----=_Part_59839_21254016.1152561130605"

------=_Part_59839_21254016.1152561130605
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi all,
The GOMM ad-hoc meeting will take place in Room 159a from 7pm55 to 8pm50

Eric



> Message du 06/07/06 23:25
> De : "Eric Njedjou"=20
> A : mipshop@ietf.org, mip6@ietf.org, netlmm@ietf.org
> Copie =C3=A0 :=20
> Objet : [Mipshop] GOMM Ad-Hoc BOF in Montreal
>=20
>=20
> Dear all,
> Following the Dallas IETF ad-hoc meeting on "the right mobility architect=
ure for the Internet", strong interest was given to the gloabl IP mobility =
management problem that was presented. As a follow-up, Julien Riera, Telema=
co Melia, Jouni Korhonen and I are setting up a second ad-hoc meeting durin=
g the upcoming Montreal IETF.
> Meeting title GlObal IP Mobility Management ad-hoc BOF (GOMM)
> Date: Monday, 10th of July
> Time: 7pm50 - 8 pm 50
> Room: TBD=20
> ---------------------------------------------------
> Agenda:
> 1)Introduction and wrap-up (5 min): Eric Njedjou
> 2Network Initiated handovers: problem statement (15min): Telemaco Melia
> draft-melia-mobopts-niho-ps-01.txt=20
> 3) Problem statement for Global IP Mobility Management (25 min): Eric Nje=
djou
> draft-njedjou-globalmm-ps-00.txt
> 4)Better Understanding 3GPP requirements on IP mobility at IETF (5min):=
=20
> 5)Conclusions and next steps (mailing list set-up announcement, official =
BOF plan for November,...) (10 min): Eric Njedjou
> -------------------------------------------------------
> The purpose of this ad-hoc meeting is to extend the presentation of the p=
roblem to a wider audience than in Dallas and foster more discussions.
> draft-njedjou-globalmm-ps-00.txt has been updated based on reviews and co=
mments as provided by many folks.
> Thank you in advance for participating to this "GOMM" ad-hoc BOF discussi=
ons
> Best Regards
> Eric Njedjou=20
>=20
>=20
>=20
> =20



Eric Njedjou


21, Square L=C3=A9on Bourgeois


35000 Rennes
------=_Part_59839_21254016.1152561130605
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<P>Hi all,</P>
<P>The GOMM ad-hoc meeting will take place in <STRONG>Room 159a</STRONG> fr=
om <STRONG>7pm55 to 8pm50</STRONG><BR><BR>Eric<BR><BR><BR></P>
<BLOCKQUOTE style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #ff0=
000 2px solid">&gt; Message du 06/07/06 23:25<BR>&gt; De : "Eric Njedjou" <=
ERIC.NTONFO@WANADOO.FR><BR>&gt; A : mipshop@ietf.org, mip6@ietf.org, netlmm=
@ietf.org<BR>&gt; Copie =C3=A0 : <BR>&gt; Objet : [Mipshop] GOMM Ad-Hoc BOF=
 in Montreal<BR>&gt; <BR>&gt; <FONT size=3D2>
<P>&gt; Dear all,</P>
<P>&gt; Following the Dallas IETF ad-hoc meeting on "the right mobility arc=
hitecture for the Internet", strong interest was given to the gloabl IP mob=
ility management problem that was presented. As a follow-up, Julien Riera, =
Telemaco Melia, Jouni Korhonen and I are setting up a <B>second ad-hoc meet=
ing during the upcoming Montreal IETF</B>.</P><B>
<P>&gt; Meeting&nbsp;title</B> <U>G</U>l<U>O</U>bal IP <U>M</U>obility <U>M=
</U>anagement ad-hoc BOF (GOMM)</P><B>
<P>&gt; Date:</B> Monday, 10th of July</P><B>
<P>&gt; Time:</B> 7pm50 - 8 pm 50</P><B>
<P>&gt; Room:</B> TBD </P><B>
<P>&gt; ---------------------------------------------------</P>
<P>&gt; Agenda:</P></B>
<P>&gt; 1)Introduction and wrap-up (5 min): <I>Eric Njedjou</P></I>
<P>&gt; 2Network Initiated handovers: problem statement (15min): <I>Telemac=
o Melia</P></I>
<P>&gt; draft-melia-mobopts-niho-ps-01.txt </P>
<P>&gt; 3) Problem statement for Global IP Mobility Management (25 min): <I=
>Eric Njedjou</P></I>
<P>&gt; draft-njedjou-globalmm-ps-00.txt</P>
<P>&gt; 4)Better Understanding 3GPP requirements on IP mobility at IETF&nbs=
p;(5min): </P>
<P>&gt; 5)Conclusions and next steps (mailing list set-up announcement, off=
icial BOF plan&nbsp;for November,...) (10 min):<I> Eric Njedjou</P></I>
<P>&gt; -------------------------------------------------------</P>
<P>&gt; The purpose of this ad-hoc meeting is to extend the presentation of=
 the problem to a wider audience than in Dallas and foster more discussions=
.</P>
<P>&gt; draft-njedjou-globalmm-ps-00.txt has been updated based on reviews =
and comments as provided by many folks.</P>
<P>&gt; Thank you in advance for participating to this "GOMM" ad-hoc BOF di=
scussions</P>
<P>&gt; Best Regards</P>
<P>&gt; Eric Njedjou </P>
<P>&gt; </FONT><BR>&gt; <BR>&gt; </P>
<P>&gt; &nbsp;</P></BLOCKQUOTE>
<P><BR><BR></P>
<P>Eric Njedjou</P><BR>
<P>21, Square L=C3=A9on Bourgeois</P><BR>
<P>35000 Rennes</P>
------=_Part_59839_21254016.1152561130605--

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

_______________________________________________
Mipshop mailing list
Mipshop@ietf.org
https://www1.ietf.org/mailman/listinfo/mipshop

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

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

------=_Part_59838_13205823.1152561130604--





From mip6-bounces@ietf.org Mon Jul 10 17:24:53 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G03ET-0003So-HN; Mon, 10 Jul 2006 17:23:57 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G03ES-0003SY-6D; Mon, 10 Jul 2006 17:23:56 -0400
Received: from smtp16.orange.fr ([193.252.23.89])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1G03ER-0008Cc-N1; Mon, 10 Jul 2006 17:23:56 -0400
Received: from wwinf1605 (wwinf1605 [172.22.147.32])
	by mwinf1604.orange.fr (SMTP Server) with ESMTP id B85687000087;
	Mon, 10 Jul 2006 23:23:54 +0200 (CEST)
X-ME-UUID: 20060710212354755.B85687000087@mwinf1604.orange.fr
Message-ID: <19133097.1152566634746.JavaMail.www@wwinf1605>
From: Eric Njedjou <eric.ntonfo@wanadoo.fr>
To: "mip6  [mip6]" <mip6@ietf.org>, "mipshop  [mipshop]" <mipshop@ietf.org>,
	"netlmm  [netlmm]" <netlmm@ietf.org>
Mime-Version: 1.0
X-Originating-IP: [132.219.20.229]
X-Wum-Nature: EMAIL-NATURE
X-WUM-FROM: |~|
X-WUM-TO: |~||~||~|
X-WUM-REPLYTO: |~|
Date: Mon, 10 Jul 2006 23:23:54 +0200 (CEST)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 2e8fc473f5174be667965460bd5288ba
Cc: 
Subject: [Mip6] typo: GOMM Ad-Hoc BOF in Room 519a !!
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: eric.ntonfo@wanadoo.fr
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2100488639=="
Errors-To: mip6-bounces@ietf.org

--===============2100488639==
Content-Type: multipart/alternative; 
	boundary="----=_Part_428939_3886241.1152566634729"

------=_Part_428939_3886241.1152566634729
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable


There was a typo about the room
It's 519a !!


Thanx

> Message du 10/07/06 22:10
> De : "Eric Njedjou"=20
> A : "mip6  [mip6]" , "mipshop  [mipshop]" , "netlmm  [netlmm]"=20
> Copie =C3=A0 :=20
> Objet : [Mip6] GOMM Ad-Hoc BOF in Room 159a
>=20
>=20
> Hi all,
> The GOMM ad-hoc meeting will take place in Room 159a from 7pm55 to 8pm50
>=20
> Eric
>=20
>=20
>=20
> Message du 06/07/06 23:25
> > De : "Eric Njedjou"=20
> > A : mipshop@ietf.org, mip6@ietf.org, netlmm@ietf.org
> > Copie =C3=A0 :=20
> > Objet : [Mipshop] GOMM Ad-Hoc BOF in Montreal
> >=20
> >=20
> > Dear all,
> > Following the Dallas IETF ad-hoc meeting on "the right mobility archite=
cture for the Internet", strong interest was given to the gloabl IP mobilit=
y management problem that was presented. As a follow-up, Julien Riera, Tele=
maco Melia, Jouni Korhonen and I are setting up a second ad-hoc meeting dur=
ing the upcoming Montreal IETF.
> > Meeting title GlObal IP Mobility Management ad-hoc BOF (GOMM)
> > Date: Monday, 10th of July
> > Time: 7pm50 - 8 pm 50
> > Room: TBD=20
> > ---------------------------------------------------
> > Agenda:
> > 1)Introduction and wrap-up (5 min): Eric Njedjou
> > 2Network Initiated handovers: problem statement (15min): Telemaco Melia
> > draft-melia-mobopts-niho-ps-01.txt=20
> > 3) Problem statement for Global IP Mobility Management (25 min): Eric N=
jedjou
> > draft-njedjou-globalmm-ps-00.txt
> > 4)Better Understanding 3GPP requirements on IP mobility at IETF (5min):=
=20
> > 5)Conclusions and next steps (mailing list set-up announcement, officia=
l BOF plan for November,...) (10 min): Eric Njedjou
> > -------------------------------------------------------
> > The purpose of this ad-hoc meeting is to extend the presentation of the=
 problem to a wider audience than in Dallas and foster more discussions.
> > draft-njedjou-globalmm-ps-00.txt has been updated based on reviews and =
comments as provided by many folks.
> > Thank you in advance for participating to this "GOMM" ad-hoc BOF discus=
sions
> > Best Regards
> > Eric Njedjou=20
> >=20
> >=20
> >=20
> > =20
>=20
>=20
>=20
> Eric Njedjou

>=20
> 21, Square L=C3=A9on Bourgeois

>=20
> 35000 Rennes
>
> [ (pas de nom de fichier) (0.1 Ko) ]
> [ (pas de nom de fichier) (0.1 Ko) ]



Eric Njedjou


21, Square L=C3=A9on Bourgeois


35000 Rennes
------=_Part_428939_3886241.1152566634729
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<P><BR>There was a typo about the room</P>
<P>It's 519a !!<BR><BR><BR>Thanx<BR></P>
<BLOCKQUOTE style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #ff0=
000 2px solid">&gt; Message du 10/07/06 22:10<BR>&gt; De : "Eric Njedjou" <=
ERIC.NTONFO@WANADOO.FR><BR>&gt; A : "mip6 &nbsp;[mip6]" <MIP6@IETF.ORG>, "m=
ipshop &nbsp;[mipshop]" <MIPSHOP@IETF.ORG>, "netlmm &nbsp;[netlmm]" <NETLMM=
@IETF.ORG><BR>&gt; Copie =C3=A0 : <BR>&gt; Objet : [Mip6] GOMM Ad-Hoc BOF i=
n Room 159a<BR>&gt; <BR>&gt;=20
<P>&gt; Hi all,</P>
<P>&gt; The GOMM ad-hoc meeting will take place in <STRONG>Room 159a</STRON=
G> from <STRONG>7pm55 to 8pm50</STRONG><BR>&gt; <BR>&gt; Eric<BR>&gt; <BR>&=
gt; <BR>&gt; </P>
<BLOCKQUOTE style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #ff0=
000 2px solid">&gt; Message du 06/07/06 23:25<BR>&gt; &gt; De : "Eric Njedj=
ou" <ERIC.NTONFO@WANADOO.FR><BR>&gt; &gt; A : mipshop@ietf.org, mip6@ietf.o=
rg, netlmm@ietf.org<BR>&gt; &gt; Copie =C3=A0 : <BR>&gt; &gt; Objet : [Mips=
hop] GOMM Ad-Hoc BOF in Montreal<BR>&gt; &gt; <BR>&gt; &gt; <FONT size=3D2>
<P>&gt; &gt; Dear all,</P>
<P>&gt; &gt; Following the Dallas IETF ad-hoc meeting on "the right mobilit=
y architecture for the Internet", strong interest was given to the gloabl I=
P mobility management problem that was presented. As a follow-up, Julien Ri=
era, Telemaco Melia, Jouni Korhonen and I are setting up a <B>second ad-hoc=
 meeting during the upcoming Montreal IETF</B>.</P><B>
<P>&gt; &gt; Meeting&nbsp;title</B> <U>G</U>l<U>O</U>bal IP <U>M</U>obility=
 <U>M</U>anagement ad-hoc BOF (GOMM)</P><B>
<P>&gt; &gt; Date:</B> Monday, 10th of July</P><B>
<P>&gt; &gt; Time:</B> 7pm50 - 8 pm 50</P><B>
<P>&gt; &gt; Room:</B> TBD </P><B>
<P>&gt; &gt; ---------------------------------------------------</P>
<P>&gt; &gt; Agenda:</P></B>
<P>&gt; &gt; 1)Introduction and wrap-up (5 min): <I>Eric Njedjou</P></I>
<P>&gt; &gt; 2Network Initiated handovers: problem statement (15min): <I>Te=
lemaco Melia</P></I>
<P>&gt; &gt; draft-melia-mobopts-niho-ps-01.txt </P>
<P>&gt; &gt; 3) Problem statement for Global IP Mobility Management (25 min=
): <I>Eric Njedjou</P></I>
<P>&gt; &gt; draft-njedjou-globalmm-ps-00.txt</P>
<P>&gt; &gt; 4)Better Understanding 3GPP requirements on IP mobility at IET=
F&nbsp;(5min): </P>
<P>&gt; &gt; 5)Conclusions and next steps (mailing list set-up announcement=
, official BOF plan&nbsp;for November,...) (10 min):<I> Eric Njedjou</P></I=
>
<P>&gt; &gt; -------------------------------------------------------</P>
<P>&gt; &gt; The purpose of this ad-hoc meeting is to extend the presentati=
on of the problem to a wider audience than in Dallas and foster more discus=
sions.</P>
<P>&gt; &gt; draft-njedjou-globalmm-ps-00.txt has been updated based on rev=
iews and comments as provided by many folks.</P>
<P>&gt; &gt; Thank you in advance for participating to this "GOMM" ad-hoc B=
OF discussions</P>
<P>&gt; &gt; Best Regards</P>
<P>&gt; &gt; Eric Njedjou </P>
<P>&gt; &gt; </FONT><BR>&gt; &gt; <BR>&gt; &gt; </P>
<P>&gt; &gt; &nbsp;</P></BLOCKQUOTE>
<P>&gt; <BR>&gt; <BR>&gt; </P>
<P>&gt; Eric Njedjou</P><BR>&gt;=20
<P>&gt; 21, Square L=C3=A9on Bourgeois</P><BR>&gt;=20
<P>&gt; 35000 Rennes</P>&gt;<BR>&gt; [ (pas de nom de fichier) (0.1 Ko) ]<B=
R>&gt; [ (pas de nom de fichier) (0.1 Ko) ]</BLOCKQUOTE>
<P><BR><BR></P>
<P>Eric Njedjou</P><BR>
<P>21, Square L=C3=A9on Bourgeois</P><BR>
<P>35000 Rennes</P>
------=_Part_428939_3886241.1152566634729--



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

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

--===============2100488639==--





From mip6-bounces@ietf.org Mon Jul 10 17:52:08 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G03eq-0001Lc-4C; Mon, 10 Jul 2006 17:51:12 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G03Yd-0007aE-DH; Mon, 10 Jul 2006 17:44:47 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1G021L-0004lr-7g; Mon, 10 Jul 2006 16:06:19 -0400
Received: from mgw-ext14.nokia.com ([131.228.20.173])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1G01ok-0008GH-8v; Mon, 10 Jul 2006 15:53:24 -0400
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145])
	by mgw-ext14.nokia.com (Switch-3.1.8/Switch-3.1.7) with ESMTP id
	k6AJrESi014936; Mon, 10 Jul 2006 22:53:17 +0300
Received: from esebh101.NOE.Nokia.com ([172.21.138.177]) by
	esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 10 Jul 2006 22:53:16 +0300
Received: from trebe101.NOE.Nokia.com ([172.22.124.61]) by
	esebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 10 Jul 2006 22:53:15 +0300
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 10 Jul 2006 22:53:15 +0300
Message-ID: <58357EDC7884E24BAD684C1B2D91F96D07E29C@trebe101.NOE.Nokia.com>
In-Reply-To: <645728.1152221132130.JavaMail.www@wwinf1609>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [netlmm] GOMM Ad-Hoc BOF in Montreal
Thread-Index: AcahQtCI2m4X4MCERf6rJxYQu9CeegDF0hiA
From: <Markku.Ala-Vannesluoma@nokia.com>
To: <eric.ntonfo@wanadoo.fr>, <mipshop@ietf.org>, <mip6@ietf.org>,
	<netlmm@ietf.org>
X-OriginalArrivalTime: 10 Jul 2006 19:53:15.0591 (UTC)
	FILETIME=[7BB1F570:01C6A45A]
X-Spam-Score: -1.2 (-)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87
Cc: 
Subject: [Mip6] RE: [netlmm] GOMM Ad-Hoc BOF in Montreal
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1764830557=="
Errors-To: mip6-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1764830557==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C6A45A.7B63C9D1"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C6A45A.7B63C9D1
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: base64

SXMgdGhlcmUgYWxyZWFkeSBhIHJvb20gcmVzZXJ2ZWQgZm9yIHRoaXMgYWQtaG9jIEJPRj8NCiAN
CkNoZWVycywNCk1hcmtrdQ0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogZXh0
IEVyaWMgTmplZGpvdSBbbWFpbHRvOmVyaWMubnRvbmZvQHdhbmFkb28uZnJdDQpTZW50OiAwNiBK
dWx5LCAyMDA2IDE3OjI2DQpUbzogbWlwc2hvcEBpZXRmLm9yZzsgbWlwNkBpZXRmLm9yZzsgbmV0
bG1tQGlldGYub3JnDQpTdWJqZWN0OiBbbmV0bG1tXSBHT01NIEFkLUhvYyBCT0YgaW4gTW9udHJl
YWwNCg0KDQpEZWFyIGFsbCwNCg0KRm9sbG93aW5nIHRoZSBEYWxsYXMgSUVURiBhZC1ob2MgbWVl
dGluZyBvbiAidGhlIHJpZ2h0IG1vYmlsaXR5IGFyY2hpdGVjdHVyZSBmb3IgdGhlIEludGVybmV0
Iiwgc3Ryb25nIGludGVyZXN0IHdhcyBnaXZlbiB0byB0aGUgZ2xvYWJsIElQIG1vYmlsaXR5IG1h
bmFnZW1lbnQgcHJvYmxlbSB0aGF0IHdhcyBwcmVzZW50ZWQuIEFzIGEgZm9sbG93LXVwLCBKdWxp
ZW4gUmllcmEsIFRlbGVtYWNvIE1lbGlhLCBKb3VuaSBLb3Job25lbiBhbmQgSSBhcmUgc2V0dGlu
ZyB1cCBhIHNlY29uZCBhZC1ob2MgbWVldGluZyBkdXJpbmcgdGhlIHVwY29taW5nIE1vbnRyZWFs
IElFVEYuDQoNCk1lZXRpbmcgdGl0bGUgR2xPYmFsIElQIE1vYmlsaXR5IE1hbmFnZW1lbnQgYWQt
aG9jIEJPRiAoR09NTSkNCg0KRGF0ZTogTW9uZGF5LCAxMHRoIG9mIEp1bHkNCg0KVGltZTogN3Bt
NTAgLSA4IHBtIDUwDQoNClJvb206IFRCRCANCg0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQoNCkFnZW5kYToNCg0KMSlJbnRyb2R1Y3Rpb24gYW5k
IHdyYXAtdXAgKDUgbWluKTogRXJpYyBOamVkam91DQoNCjJOZXR3b3JrIEluaXRpYXRlZCBoYW5k
b3ZlcnM6IHByb2JsZW0gc3RhdGVtZW50ICgxNW1pbik6IFRlbGVtYWNvIE1lbGlhDQoNCmRyYWZ0
LW1lbGlhLW1vYm9wdHMtbmloby1wcy0wMS50eHQgDQoNCjMpIFByb2JsZW0gc3RhdGVtZW50IGZv
ciBHbG9iYWwgSVAgTW9iaWxpdHkgTWFuYWdlbWVudCAoMjUgbWluKTogRXJpYyBOamVkam91DQoN
CmRyYWZ0LW5qZWRqb3UtZ2xvYmFsbW0tcHMtMDAudHh0DQoNCjQpQmV0dGVyIFVuZGVyc3RhbmRp
bmcgM0dQUCByZXF1aXJlbWVudHMgb24gSVAgbW9iaWxpdHkgYXQgSUVURiAoNW1pbik6IA0KDQo1
KUNvbmNsdXNpb25zIGFuZCBuZXh0IHN0ZXBzIChtYWlsaW5nIGxpc3Qgc2V0LXVwIGFubm91bmNl
bWVudCwgb2ZmaWNpYWwgQk9GIHBsYW4gZm9yIE5vdmVtYmVyLC4uLikgKDEwIG1pbik6IEVyaWMg
TmplZGpvdQ0KDQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tDQoNClRoZSBwdXJwb3NlIG9mIHRoaXMgYWQtaG9jIG1lZXRpbmcgaXMgdG8gZXh0
ZW5kIHRoZSBwcmVzZW50YXRpb24gb2YgdGhlIHByb2JsZW0gdG8gYSB3aWRlciBhdWRpZW5jZSB0
aGFuIGluIERhbGxhcyBhbmQgZm9zdGVyIG1vcmUgZGlzY3Vzc2lvbnMuDQoNCmRyYWZ0LW5qZWRq
b3UtZ2xvYmFsbW0tcHMtMDAudHh0IGhhcyBiZWVuIHVwZGF0ZWQgYmFzZWQgb24gcmV2aWV3cyBh
bmQgY29tbWVudHMgYXMgcHJvdmlkZWQgYnkgbWFueSBmb2xrcy4NCg0KVGhhbmsgeW91IGluIGFk
dmFuY2UgZm9yIHBhcnRpY2lwYXRpbmcgdG8gdGhpcyAiR09NTSIgYWQtaG9jIEJPRiBkaXNjdXNz
aW9ucw0KDQpCZXN0IFJlZ2FyZHMNCg0KRXJpYyBOamVkam91IA0KDQoNCg0KDQoNCiANCg0K

------_=_NextPart_001_01C6A45A.7B63C9D1
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv
L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgSFRUUC1FUVVJVj0iQ29udGVudC1UeXBlIiBDT05U
RU5UPSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9dXRmLTgiPg0KDQoNCjxNRVRBIGNvbnRlbnQ9Ik1TSFRN
TCA2LjAwLjI4MDAuMTU1NiIgbmFtZT1HRU5FUkFUT1I+PC9IRUFEPg0KPEJPRFk+DQo8RElWPjxT
UEFOIGNsYXNzPTQ4MTMwNTAxOS0xMDA3MjAwNj48Rk9OVCBmYWNlPUFyaWFsIGNvbG9yPSMwMDAw
ZmYgc2l6ZT0yPklzIA0KdGhlcmUgYWxyZWFkeSBhIHJvb20gcmVzZXJ2ZWQgZm9yIHRoaXMgYWQt
aG9jIEJPRj88L0ZPTlQ+PC9TUEFOPjwvRElWPg0KPERJVj48U1BBTiBjbGFzcz00ODEzMDUwMTkt
MTAwNzIwMDY+PEZPTlQgZmFjZT1BcmlhbCBjb2xvcj0jMDAwMGZmIA0Kc2l6ZT0yPjwvRk9OVD48
L1NQQU4+Jm5ic3A7PC9ESVY+DQo8RElWPjxTUEFOIGNsYXNzPTQ4MTMwNTAxOS0xMDA3MjAwNj48
Rk9OVCBmYWNlPUFyaWFsIGNvbG9yPSMwMDAwZmYgDQpzaXplPTI+Q2hlZXJzLDwvRk9OVD48L1NQ
QU4+PC9ESVY+DQo8RElWPjxTUEFOIGNsYXNzPTQ4MTMwNTAxOS0xMDA3MjAwNj48Rk9OVCBmYWNl
PUFyaWFsIGNvbG9yPSMwMDAwZmYgDQpzaXplPTI+TWFya2t1PC9GT05UPjwvU1BBTj48L0RJVj4N
CjxCTE9DS1FVT1RFIGRpcj1sdHIgDQpzdHlsZT0iUEFERElORy1MRUZUOiA1cHg7IE1BUkdJTi1M
RUZUOiA1cHg7IEJPUkRFUi1MRUZUOiAjMDAwMGZmIDJweCBzb2xpZDsgTUFSR0lOLVJJR0hUOiAw
cHgiPg0KICA8RElWIGNsYXNzPU91dGxvb2tNZXNzYWdlSGVhZGVyIGRpcj1sdHIgYWxpZ249bGVm
dD48Rk9OVCBmYWNlPVRhaG9tYSANCiAgc2l6ZT0yPi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0t
PEJSPjxCPkZyb206PC9CPiBleHQgRXJpYyBOamVkam91IA0KICBbbWFpbHRvOmVyaWMubnRvbmZv
QHdhbmFkb28uZnJdPEJSPjxCPlNlbnQ6PC9CPiAwNiBKdWx5LCAyMDA2IA0KICAxNzoyNjxCUj48
Qj5Ubzo8L0I+IG1pcHNob3BAaWV0Zi5vcmc7IG1pcDZAaWV0Zi5vcmc7IA0KICBuZXRsbW1AaWV0
Zi5vcmc8QlI+PEI+U3ViamVjdDo8L0I+IFtuZXRsbW1dIEdPTU0gQWQtSG9jIEJPRiBpbiANCiAg
TW9udHJlYWw8QlI+PEJSPjwvRk9OVD48L0RJVj48Rk9OVCBzaXplPTI+DQogIDxQPkRlYXIgYWxs
LDwvUD4NCiAgPFA+Rm9sbG93aW5nIHRoZSBEYWxsYXMgSUVURiBhZC1ob2MgbWVldGluZyBvbiAi
dGhlIHJpZ2h0IG1vYmlsaXR5IA0KICBhcmNoaXRlY3R1cmUgZm9yIHRoZSBJbnRlcm5ldCIsIHN0
cm9uZyBpbnRlcmVzdCB3YXMgZ2l2ZW4gdG8gdGhlIGdsb2FibCBJUCANCiAgbW9iaWxpdHkgbWFu
YWdlbWVudCBwcm9ibGVtIHRoYXQgd2FzIHByZXNlbnRlZC4gQXMgYSBmb2xsb3ctdXAsIEp1bGll
biBSaWVyYSwgDQogIFRlbGVtYWNvIE1lbGlhLCBKb3VuaSBLb3Job25lbiBhbmQgSSBhcmUgc2V0
dGluZyB1cCBhIDxCPnNlY29uZCBhZC1ob2MgbWVldGluZyANCiAgZHVyaW5nIHRoZSB1cGNvbWlu
ZyBNb250cmVhbCBJRVRGPC9CPi48L1A+PEI+DQogIDxQPk1lZXRpbmcmbmJzcDt0aXRsZTwvQj4g
PFU+RzwvVT5sPFU+TzwvVT5iYWwgSVAgPFU+TTwvVT5vYmlsaXR5IA0KICA8VT5NPC9VPmFuYWdl
bWVudCBhZC1ob2MgQk9GIChHT01NKTwvUD48Qj4NCiAgPFA+RGF0ZTo8L0I+IE1vbmRheSwgMTB0
aCBvZiBKdWx5PC9QPjxCPg0KICA8UD5UaW1lOjwvQj4gN3BtNTAgLSA4IHBtIDUwPC9QPjxCPg0K
ICA8UD5Sb29tOjwvQj4gVEJEIDwvUD48Qj4NCiAgPFA+LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tPC9QPg0KICA8UD5BZ2VuZGE6PC9QPjwvQj4NCiAg
PFA+MSlJbnRyb2R1Y3Rpb24gYW5kIHdyYXAtdXAgKDUgbWluKTogPEk+RXJpYyBOamVkam91PC9Q
PjwvST4NCiAgPFA+Mk5ldHdvcmsgSW5pdGlhdGVkIGhhbmRvdmVyczogcHJvYmxlbSBzdGF0ZW1l
bnQgKDE1bWluKTogPEk+VGVsZW1hY28gDQogIE1lbGlhPC9QPjwvST4NCiAgPFA+ZHJhZnQtbWVs
aWEtbW9ib3B0cy1uaWhvLXBzLTAxLnR4dCA8L1A+DQogIDxQPjMpIFByb2JsZW0gc3RhdGVtZW50
IGZvciBHbG9iYWwgSVAgTW9iaWxpdHkgTWFuYWdlbWVudCAoMjUgbWluKTogPEk+RXJpYyANCiAg
TmplZGpvdTwvUD48L0k+DQogIDxQPmRyYWZ0LW5qZWRqb3UtZ2xvYmFsbW0tcHMtMDAudHh0PC9Q
Pg0KICA8UD40KUJldHRlciBVbmRlcnN0YW5kaW5nIDNHUFAgcmVxdWlyZW1lbnRzIG9uIElQIG1v
YmlsaXR5IGF0IA0KICBJRVRGJm5ic3A7KDVtaW4pOiA8L1A+DQogIDxQPjUpQ29uY2x1c2lvbnMg
YW5kIG5leHQgc3RlcHMgKG1haWxpbmcgbGlzdCBzZXQtdXAgYW5ub3VuY2VtZW50LCBvZmZpY2lh
bCANCiAgQk9GIHBsYW4mbmJzcDtmb3IgTm92ZW1iZXIsLi4uKSAoMTAgbWluKTo8ST4gRXJpYyBO
amVkam91PC9QPjwvST4NCiAgPFA+LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLTwvUD4NCiAgPFA+VGhlIHB1cnBvc2Ugb2YgdGhpcyBhZC1ob2Mg
bWVldGluZyBpcyB0byBleHRlbmQgdGhlIHByZXNlbnRhdGlvbiBvZiB0aGUgDQogIHByb2JsZW0g
dG8gYSB3aWRlciBhdWRpZW5jZSB0aGFuIGluIERhbGxhcyBhbmQgZm9zdGVyIG1vcmUgZGlzY3Vz
c2lvbnMuPC9QPg0KICA8UD5kcmFmdC1uamVkam91LWdsb2JhbG1tLXBzLTAwLnR4dCBoYXMgYmVl
biB1cGRhdGVkIGJhc2VkIG9uIHJldmlld3MgYW5kIA0KICBjb21tZW50cyBhcyBwcm92aWRlZCBi
eSBtYW55IGZvbGtzLjwvUD4NCiAgPFA+VGhhbmsgeW91IGluIGFkdmFuY2UgZm9yIHBhcnRpY2lw
YXRpbmcgdG8gdGhpcyAiR09NTSIgYWQtaG9jIEJPRiANCiAgZGlzY3Vzc2lvbnM8L1A+DQogIDxQ
PkJlc3QgUmVnYXJkczwvUD4NCiAgPFA+RXJpYyBOamVkam91IDwvUD4NCiAgPFA+PC9GT05UPjxC
Uj48QlI+PC9QPg0KICA8UD4mbmJzcDs8L1A+PC9CTE9DS1FVT1RFPjwvQk9EWT48L0hUTUw+DQo=

------_=_NextPart_001_01C6A45A.7B63C9D1--


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

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

--===============1764830557==--




From mip6-bounces@ietf.org Tue Jul 11 10:58:12 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G0Jgd-0001Wg-HX; Tue, 11 Jul 2006 10:58:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G0Jgb-0001Wb-Rm
	for mip6@ietf.org; Tue, 11 Jul 2006 10:58:05 -0400
Received: from concorde.inria.fr ([192.93.2.39])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G0Jga-0006PK-FY
	for mip6@ietf.org; Tue, 11 Jul 2006 10:58:05 -0400
Received: from iseran-2.local (h11b0-net84db.lab.risq.net [132.219.17.176]
	(may be forged)) (authenticated bits=0)
	by concorde.inria.fr (8.13.6/8.13.6) with ESMTP id k6BEw19F029603
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <mip6@ietf.org>; Tue, 11 Jul 2006 16:58:03 +0200
Date: Tue, 11 Jul 2006 16:58:02 +0200
From: Thierry Ernst <thierry.ernst@inria.fr>
To: mip6@ietf.org
Subject: Re: [Mip6] Draft agenda for MIP6 WG meeting at IETF66
Message-Id: <20060711165802.4abe41b3.thierry.ernst@inria.fr>
In-Reply-To: <C0BF1FDB.1C5A8%basavaraj.patil@nokia.com>
References: <C0BF1FDB.1C5A8%basavaraj.patil@nokia.com>
Organization: INRIA
X-Mailer: Sylpheed version 0.9.12 (GTK+ 1.2.10; powerpc-apple-darwin7.8.0)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Miltered: at concorde with ID 44B3BC79.001 by Joe's j-chkmail
	(http://j-chkmail.ensmp.fr)!
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org



> THURSDAY, July 13, 2006
> 0900-1130 Morning Session I
> Room 518AB
> 
> =========================================
>
> 3. Mobile IPv6 support for dual stack Hosts and Routers (DSMIPv6)
>    I-D: draft-ietf-mip6-nemo-v4traversal-01.txt
> 
>    Hesham Soliman                    15 Mins

I would like to request MIP6 chairs to make it clear that this draft is
a common doc between the NEMO WG and the MIP6 WG, though the draft can
only be listed from the MIP6 WG page, due to technical reasons (this is
the reason why it's useful to repeat this).

Thanks,
Thierry, NEMO WG chair.



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



From mip6-bounces@ietf.org Wed Jul 12 16:17:40 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G0l8X-0007qH-Hm; Wed, 12 Jul 2006 16:16:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G0l8W-0007pT-0Q
	for mip6@ietf.org; Wed, 12 Jul 2006 16:16:44 -0400
Received: from motgate5.mot.com ([144.189.100.105])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G0l8U-0003pI-MG
	for mip6@ietf.org; Wed, 12 Jul 2006 16:16:43 -0400
Received: from az33exr03.mot.com (az33exr03.mot.com [10.64.251.233])
	by motgate5.mot.com (8.12.11/Motgate5) with ESMTP id k6CKGcLR011056;
	Wed, 12 Jul 2006 13:16:38 -0700 (MST)
Received: from [10.19.253.205] (mvp-10-19-253-205.corp.mot.com [10.19.253.205])
	by az33exr03.mot.com (8.13.1/8.13.0) with ESMTP id k6CKGa6i014380;
	Wed, 12 Jul 2006 15:16:37 -0500 (CDT)
Message-ID: <44B558A1.9050000@motorola.com>
Date: Wed, 12 Jul 2006 22:16:33 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: Thierry Ernst <thierry.ernst@inria.fr>
Subject: Re: [Mip6] Draft agenda for MIP6 WG meeting at IETF66
References: <C0BF1FDB.1C5A8%basavaraj.patil@nokia.com>
	<20060711165802.4abe41b3.thierry.ernst@inria.fr>
In-Reply-To: <20060711165802.4abe41b3.thierry.ernst@inria.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAQAAAAQ=
X-White-List-Member: TRUE
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Thierry Ernst wrote:
> 
>> THURSDAY, July 13, 2006 0900-1130 Morning Session I Room 518AB
>> 
>> =========================================
>> 
>> 3. Mobile IPv6 support for dual stack Hosts and Routers (DSMIPv6) 
>> I-D: draft-ietf-mip6-nemo-v4traversal-01.txt
>> 
>> Hesham Soliman                    15 Mins
> 
> I would like to request MIP6 chairs to make it clear that this draft
> is a common doc between the NEMO WG and the MIP6 WG, though the draft
> can only be listed from the MIP6 WG page, due to technical reasons
> (this is the reason why it's useful to repeat this).

Administratively speaking, is this draft supposed to be Last Call'ed in
both WGs?  Is its advancement conditioned by passing a LC in both WGs or 
in only one (which one)?

Alex

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



From mip6-bounces@ietf.org Wed Jul 12 17:31:35 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G0mI6-0004aN-1F; Wed, 12 Jul 2006 17:30:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G0mI4-0004a7-EW
	for mip6@ietf.org; Wed, 12 Jul 2006 17:30:40 -0400
Received: from mail1.azairenet.com ([66.92.223.4] helo=bart.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G0mI2-0005J8-4E
	for mip6@ietf.org; Wed, 12 Jul 2006 17:30:40 -0400
Received: from [10.1.210.6] ([10.1.210.6]) by bart.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Wed, 12 Jul 2006 14:30:35 -0700
Message-ID: <44B569F9.4050900@azairenet.com>
Date: Wed, 12 Jul 2006 14:30:33 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.4 (Windows/20060516)
MIME-Version: 1.0
To: Alexandru Petrescu <alexandru.petrescu@motorola.com>
Subject: Re: [Mip6] Draft agenda for MIP6 WG meeting at IETF66
References: <C0BF1FDB.1C5A8%basavaraj.patil@nokia.com>	<20060711165802.4abe41b3.thierry.ernst@inria.fr>
	<44B558A1.9050000@motorola.com>
In-Reply-To: <44B558A1.9050000@motorola.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 12 Jul 2006 21:30:35.0820 (UTC)
	FILETIME=[6991AEC0:01C6A5FA]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Cc: mip6@ietf.org, Thierry Ernst <thierry.ernst@inria.fr>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

we can have a simultaneous last call in two working groups.

Vijay

Alexandru Petrescu wrote:
> Thierry Ernst wrote:
>>
>>> THURSDAY, July 13, 2006 0900-1130 Morning Session I Room 518AB
>>>
>>> =========================================
>>>
>>> 3. Mobile IPv6 support for dual stack Hosts and Routers (DSMIPv6) 
>>> I-D: draft-ietf-mip6-nemo-v4traversal-01.txt
>>>
>>> Hesham Soliman                    15 Mins
>>
>> I would like to request MIP6 chairs to make it clear that this draft
>> is a common doc between the NEMO WG and the MIP6 WG, though the draft
>> can only be listed from the MIP6 WG page, due to technical reasons
>> (this is the reason why it's useful to repeat this).
> 
> Administratively speaking, is this draft supposed to be Last Call'ed in
> both WGs?  Is its advancement conditioned by passing a LC in both WGs or 
> in only one (which one)?
> 
> Alex
> 
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6


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



From mip6-bounces@ietf.org Wed Jul 12 19:38:04 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G0oGT-00020j-0p; Wed, 12 Jul 2006 19:37:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G0oGS-0001zk-2C
	for mip6@ietf.org; Wed, 12 Jul 2006 19:37:08 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G0mW9-0006K3-7i
	for mip6@ietf.org; Wed, 12 Jul 2006 17:45:13 -0400
Received: from neon.tcs.hut.fi ([130.233.215.20])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1G0mNl-00065W-TH
	for mip6@ietf.org; Wed, 12 Jul 2006 17:36:35 -0400
Received: from rhea.tcs.hut.fi (rhea.tcs.hut.fi [130.233.215.147])
	by neon.tcs.hut.fi (Postfix) with ESMTP id D979D800A40;
	Thu, 13 Jul 2006 00:36:25 +0300 (EEST)
Date: Thu, 13 Jul 2006 00:36:25 +0300 (EEST)
From: Wassim Haddad <whaddad@tcs.hut.fi>
To: mip6@ietf.org
Message-ID: <Pine.LNX.4.58.0607130034480.21842@rhea.tcs.hut.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: <Pine.LNX.4.58.0607130034482.21842@rhea.tcs.hut.fi>
X-Spam-Score: -2.6 (--)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: Wassim.Haddad@ericsson.com
Subject: [Mip6] I-D ACTION:draft-haddad-mipshop-mobisig-del-01.txt  (fwd)
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi,

FYI,

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


	Title		: Mobility Signaling Delegation in OptiSEND
	Author(s)	: W. Haddad, et al.
	Filename	: draft-haddad-mipshop-mobisig-del-01.txt

This memo describes a mechanism, which delegates the exchange of
mobility signaling messages between the mobile node and the
correspondent node(s) to the network infrastructure.  Goals outlining
the proposed delegation are to further reduce the IP handoff latency
and to relieve the mobile node from exchanging a considerable amount
of signaling messages with the CN(s) while retaining full control on
the critical ones.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-haddad-mipshop-mobisig-del-01.txt

Comments appreciated.


Regards,

Wassim H.

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



From mip6-bounces@ietf.org Thu Jul 13 08:40:38 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G10US-0000m1-AJ; Thu, 13 Jul 2006 08:40:24 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G10UQ-0000lw-GJ
	for mip6@ietf.org; Thu, 13 Jul 2006 08:40:22 -0400
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G10UP-0001nU-7Z
	for mip6@ietf.org; Thu, 13 Jul 2006 08:40:22 -0400
Received: from p130.piuha.net (localhost [127.0.0.1])
	by p130.piuha.net (Postfix) with ESMTP id C168A898B8;
	Thu, 13 Jul 2006 15:40:19 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id A8CB88989C;
	Thu, 13 Jul 2006 15:40:18 +0300 (EEST)
Message-ID: <44B63F1F.9000209@piuha.net>
Date: Thu, 13 Jul 2006 08:39:59 -0400
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Mozilla Thunderbird 1.0.8 (X11/20060502)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Alexandru Petrescu <alexandru.petrescu@motorola.com>
Subject: Re: [Mip6] Draft agenda for MIP6 WG meeting at IETF66
References: <C0BF1FDB.1C5A8%basavaraj.patil@nokia.com>	<20060711165802.4abe41b3.thierry.ernst@inria.fr>
	<44B558A1.9050000@motorola.com>
In-Reply-To: <44B558A1.9050000@motorola.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: 1ac7cc0a4cd376402b85bc1961a86ac2
Cc: mip6@ietf.org, Thierry Ernst <thierry.ernst@inria.fr>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Alexandru Petrescu wrote:

> Administratively speaking, is this draft supposed to be Last Call'ed in
> both WGs?

Yes.

> Is its advancement conditioned by passing a LC in both WGs or in only
> one (which one)?

Both.

--Jari


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



From mip6-bounces@ietf.org Thu Jul 13 15:58:29 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G17KK-0001wl-SX; Thu, 13 Jul 2006 15:58:24 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G17KJ-0001wa-77
	for mip6@ietf.org; Thu, 13 Jul 2006 15:58:23 -0400
Received: from mgw-ext12.nokia.com ([131.228.20.171])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G17KG-0004iM-PZ
	for mip6@ietf.org; Thu, 13 Jul 2006 15:58:23 -0400
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
	by mgw-ext12.nokia.com (Switch-3.1.8/Switch-3.1.7) with ESMTP id
	k6DJwIZQ008704; Thu, 13 Jul 2006 22:58:18 +0300
Received: from daebh102.NOE.Nokia.com ([10.241.35.112]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 13 Jul 2006 03:24:42 +0300
Received: from daebe101.NOE.Nokia.com ([10.241.35.113]) by
	daebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 12 Jul 2006 19:24:40 -0500
Received: from 10.241.58.44 ([10.241.58.44]) by daebe101.NOE.Nokia.com
	([10.241.35.113]) with Microsoft Exchange Server HTTP-DAV ; 
	Thu, 13 Jul 2006 00:24:39 +0000
User-Agent: Microsoft-Entourage/11.2.4.060510
Date: Wed, 12 Jul 2006 19:24:41 -0500
From: Basavaraj Patil <basavaraj.patil@nokia.com>
To: <mip6@ietf.org>
Message-ID: <C0DAFCF9.1E42E%basavaraj.patil@nokia.com>
Thread-Topic: Chairs for the MIP6 WG meeting at IETF66
Thread-Index: AcamErth+d/1+hIFEdukWgARJNUNiA==
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 13 Jul 2006 00:24:40.0263 (UTC)
	FILETIME=[BAF13570:01C6A612]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Cc: Gopal Dommety <gdommety@cisco.com>, Jari Arkko <jari.arkko@kolumbus.fi>
Subject: [Mip6] Chairs for the MIP6 WG meeting at IETF66
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org


Hello,

Gopal and myself will be unable to attend the MIP6 WG meeting at the ongoing
IETF66 meeting.
The MIP6 WG will be chaired by Hesham Soliman and Vijay Devarapalli.

We appreciate their willingness to chair the WG meeting.

-Basavaraj


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



From mip6-bounces@ietf.org Thu Jul 13 16:07:20 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G17Sx-00036u-SU; Thu, 13 Jul 2006 16:07:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G17Sx-00036p-3l
	for mip6@ietf.org; Thu, 13 Jul 2006 16:07:19 -0400
Received: from mgw-ext11.nokia.com ([131.228.20.170])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G17Sv-0005Cn-K9
	for mip6@ietf.org; Thu, 13 Jul 2006 16:07:19 -0400
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
	by mgw-ext11.nokia.com (Switch-3.1.8/Switch-3.1.7) with ESMTP id
	k6DJ7CUp025476; Thu, 13 Jul 2006 22:07:16 +0300
Received: from daebh102.NOE.Nokia.com ([10.241.35.112]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 13 Jul 2006 04:16:36 +0300
Received: from daebe101.NOE.Nokia.com ([10.241.35.113]) by
	daebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 12 Jul 2006 20:14:44 -0500
Received: from 10.241.58.44 ([10.241.58.44]) by daebe101.NOE.Nokia.com
	([10.241.35.113]) with Microsoft Exchange Server HTTP-DAV ; 
	Thu, 13 Jul 2006 01:14:43 +0000
User-Agent: Microsoft-Entourage/11.2.4.060510
Date: Wed, 12 Jul 2006 20:14:45 -0500
Subject: Re: [Mip6] Draft agenda for MIP6 WG meeting at IETF66
From: Basavaraj Patil <basavaraj.patil@nokia.com>
To: ext Thierry Ernst <thierry.ernst@inria.fr>, <mip6@ietf.org>
Message-ID: <C0DB08B5.1E437%basavaraj.patil@nokia.com>
Thread-Topic: [Mip6] Draft agenda for MIP6 WG meeting at IETF66
Thread-Index: AcamGbnn+LKvFxIMEdukWgARJNUNiA==
In-Reply-To: <20060711165802.4abe41b3.thierry.ernst@inria.fr>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 13 Jul 2006 01:14:44.0374 (UTC)
	FILETIME=[B9882B60:01C6A619]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Cc: 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org


As Thierry has mentioned, I-D: draft-ietf-mip6-nemo-v4traversal-01.txt is a
MIP6/NEMO WG document. Progressing the document forward will require WG LC
to be done across both WGs.

Comments related to this I-D should be cross posted to the NEMO WG as well.

-Raj


On 7/11/06 9:58 AM, "ext Thierry Ernst" <thierry.ernst@inria.fr> wrote:

> 
> 
>> THURSDAY, July 13, 2006
>> 0900-1130 Morning Session I
>> Room 518AB
>> 
>> =========================================
>> 
>> 3. Mobile IPv6 support for dual stack Hosts and Routers (DSMIPv6)
>>    I-D: draft-ietf-mip6-nemo-v4traversal-01.txt
>> 
>>    Hesham Soliman                    15 Mins
> 
> I would like to request MIP6 chairs to make it clear that this draft is
> a common doc between the NEMO WG and the MIP6 WG, though the draft can
> only be listed from the MIP6 WG page, due to technical reasons (this is
> the reason why it's useful to repeat this).
> 
> Thanks,
> Thierry, NEMO WG chair.
> 
> 
> 
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6


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



From mip6-bounces@ietf.org Thu Jul 13 18:01:31 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G19FM-0003YA-Sy; Thu, 13 Jul 2006 18:01:24 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G19FL-0003Y5-UK
	for mip6@ietf.org; Thu, 13 Jul 2006 18:01:23 -0400
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G19FK-0003r8-FC
	for mip6@ietf.org; Thu, 13 Jul 2006 18:01:23 -0400
Received: from il06exr03.mot.com (il06exr03.mot.com [129.188.137.133])
	by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id k6DM1Kun004635;
	Thu, 13 Jul 2006 15:01:20 -0700 (MST)
Received: from [10.31.25.120] ([10.31.25.120])
	by il06exr03.mot.com (8.13.1/8.13.0) with ESMTP id k6DM1I28001329;
	Thu, 13 Jul 2006 17:01:19 -0500 (CDT)
Message-ID: <44B6C29C.1050308@motorola.com>
Date: Fri, 14 Jul 2006 00:01:00 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: Henrik Levkowetz <henrik@levkowetz.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAQAAAAQ=
X-White-List-Member: TRUE
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>
Subject: [Mip6] topology about v4-v6 migration
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi Henrik, per your request on the scenario of IPv6-IPv4 deployment I
mentioned today in the MIP6 WG meeting.  Below is the topology I've
had in mind:


   +--+
   |CN|
   +--+
    |
  ------------------
/ IPv6-only        \____
\ "island" network /    |
  ------------------     |
                         |
                         |
                         |
  ----------------       |    +---+     -------------    +----------+
/ IPv4-only      \__IPv4_____|GW |____/ IPv6-only   \___| HA       |
\ access network /  Internet +---+    \ home network/   | IPv6-only|
  ----------------                      -------------    +----------+
       .
       |
     +--+
     |MN|
     +--+


The MN is "owned" by an IPv6 HA deep in an IPv6-only network,
presumably some operator's network.  MN connects to another operator's
IPv4-only wireless access.  It needs to communicate with an IPv6-only
CN, present on an IPv6-only "island" network.

The IPv4-only access network, the IPv6-only home network and the
IPv6-only "island" network are connected together on the IPv4
Internet.

The comment I've had is how to support this.  Thanks.

Alex
PS: the other NAT traversal and keepalive for maintaining state I'll
     send privately next week.

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



From mip6-bounces@ietf.org Fri Jul 14 10:47:48 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G1OxD-0002jn-Ox; Fri, 14 Jul 2006 10:47:43 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G1OxC-0002ja-SH
	for mip6@ietf.org; Fri, 14 Jul 2006 10:47:42 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G1OlL-0007Gs-Di
	for mip6@ietf.org; Fri, 14 Jul 2006 10:35:27 -0400
Received: from av11-2-sn2.hy.skanova.net ([81.228.8.184])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1G1OVM-0006Vv-Qs
	for mip6@ietf.org; Fri, 14 Jul 2006 10:18:57 -0400
Received: by av11-2-sn2.hy.skanova.net (Postfix, from userid 502)
	id C9A24380BA; Fri, 14 Jul 2006 15:48:56 +0200 (CEST)
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 BC21E37F9C; Fri, 14 Jul 2006 15:48:56 +0200 (CEST)
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 90C6E37E45;
	Fri, 14 Jul 2006 15:48:56 +0200 (CEST)
Received: from localhost ([127.0.0.1])
	by shiraz.levkowetz.com with esmtp (Exim 4.62)
	(envelope-from <henrik@levkowetz.com>)
	id 1G1O2K-0005C5-7y; Fri, 14 Jul 2006 15:48:56 +0200
Message-ID: <44B7A0C6.8040202@levkowetz.com>
Date: Fri, 14 Jul 2006 09:48:54 -0400
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Thunderbird 1.5.0.4 (Macintosh/20060530)
MIME-Version: 1.0
To: Alexandru Petrescu <alexandru.petrescu@motorola.com>
References: <44B6C29C.1050308@motorola.com>
In-Reply-To: <44B6C29C.1050308@motorola.com>
X-Enigmail-Version: 0.94.0.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on shiraz.levkowetz.com);
	SAEximRunCond expanded to false
X-Spam-Score: -2.5 (--)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>
Subject: [Mip6] Re: topology about v4-v6 migration
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi Alex,

on 2006-07-13 18:01 Alexandru Petrescu said the following:
> Hi Henrik, per your request on the scenario of IPv6-IPv4 deployment I
> mentioned today in the MIP6 WG meeting.  Below is the topology I've
> had in mind:
> 
> 
>    +--+
>    |CN|
>    +--+
>     |
>   ------------------
> / IPv6-only        \____
> \ "island" network /    |
>   ------------------     |
>                          |
>                          |
>                          |
>   ----------------       |    +---+     -------------    +----------+
> / IPv4-only      \__IPv4_____|GW |____/ IPv6-only   \___| HA       |
> \ access network /  Internet +---+    \ home network/   | IPv6-only|
>   ----------------                      -------------    +----------+
>        .
>        |
>      +--+
>      |MN|
>      +--+
> 
> 
> The MN is "owned" by an IPv6 HA deep in an IPv6-only network,
> presumably some operator's network.  MN connects to another operator's
> IPv4-only wireless access.  It needs to communicate with an IPv6-only
> CN, present on an IPv6-only "island" network.
> 
> The IPv4-only access network, the IPv6-only home network and the
> IPv6-only "island" network are connected together on the IPv4
> Internet.
> 
> The comment I've had is how to support this.  Thanks.

Ok, got it.  The way I understand this is that the MN will be sending
and receiving IPv6 traffic to/from the CN via the HA.

The issue of how the IPv6 traffic moves between the Home network and
CN can be solved by any kind of non-mobility IPv6 over IPv4 technology
-- teredo, 6over4, isatap or whatever.  I will assume this is not part
of the problem to be solved here, since we already have a number of
solutions to this.

The remaining problem of the MN sending IPv6 traffic to/from the HA
over the IPv4 network to the HA, using MIPv6 for mobility support,
is a valid one, sure.  (And it is solved by the DSMIPv6 work.)


Regards,

	Henrik




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



From mip6-bounces@ietf.org Fri Jul 14 12:29:44 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G1QXt-0001Ub-St; Fri, 14 Jul 2006 12:29:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G1QXs-0001St-Jb
	for mip6@ietf.org; Fri, 14 Jul 2006 12:29:40 -0400
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G1QXr-0002cs-AR
	for mip6@ietf.org; Fri, 14 Jul 2006 12:29:40 -0400
Received: from il06exr02.mot.com (il06exr02.mot.com [129.188.137.132])
	by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id k6EGTWMA004738;
	Fri, 14 Jul 2006 09:29:32 -0700 (MST)
Received: from [10.31.17.176] ([10.31.17.176])
	by il06exr02.mot.com (8.13.1/8.13.0) with ESMTP id k6EGTVWo006655;
	Fri, 14 Jul 2006 11:29:31 -0500 (CDT)
Message-ID: <44B7C66B.8030304@motorola.com>
Date: Fri, 14 Jul 2006 18:29:31 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: Henrik Levkowetz <henrik@levkowetz.com>
References: <44B6C29C.1050308@motorola.com> <44B7A0C6.8040202@levkowetz.com>
In-Reply-To: <44B7A0C6.8040202@levkowetz.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAQAAAAQ=
X-White-List-Member: TRUE
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>
Subject: [Mip6] Re: topology about v4-v6 migration
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi Henrik, thanks for the message.

Henrik Levkowetz wrote:
> Hi Alex,
> 
> on 2006-07-13 18:01 Alexandru Petrescu said the following:
>> Hi Henrik, per your request on the scenario of IPv6-IPv4 deployment
>>  I mentioned today in the MIP6 WG meeting.  Below is the topology 
>> I've had in mind:
>> 

   +--+
   |CN|
   +--+
    |
  ------------------
/ IPv6-only        \____
\ "island" network /    |
  ------------------     |
                         |
                         |
                         |
  ----------------       |    +---+     -------------    +----------+
/ IPv4-only      \__IPv4_____|GW |____/ IPv6-only   \___| HA       |
\ access network /  Internet +---+    \ home network/   | IPv6-only|
  ----------------                      -------------    +----------+
       .
       |
     +--+
     |MN|
     +--+


>> The MN is "owned" by an IPv6 HA deep in an IPv6-only network, 
>> presumably some operator's network.  MN connects to another 
>> operator's IPv4-only wireless access.  It needs to communicate with
>>  an IPv6-only CN, present on an IPv6-only "island" network.
>> 
>> The IPv4-only access network, the IPv6-only home network and the 
>> IPv6-only "island" network are connected together on the IPv4 
>> Internet.
>> 
>> The comment I've had is how to support this.  Thanks.
> 
> Ok, got it.  The way I understand this is that the MN will be sending
>  and receiving IPv6 traffic to/from the CN via the HA.

Yes.

> The issue of how the IPv6 traffic moves between the Home network and
>  CN can be solved by any kind of non-mobility IPv6 over IPv4 
> technology -- teredo, 6over4, isatap or whatever.

Exactly.  STUN, 6to4 too.  The non-mobility IPv6 over IPv4 technology
would run between GW (pictured) and a border router on CN's IPv6
island (router not pictured).

> I will assume this is not part of the problem to be solved here, 
> since we already have a number of solutions to this.

YEs.

> The remaining problem of the MN sending IPv6 traffic to/from the HA 
> over the IPv4 network to the HA, using MIPv6 for mobility support, is
>  a valid one, sure.  (And it is solved by the DSMIPv6 work.)

Ok, the problem is valid in this space, good to know.

I am not sure though how DS-MIPv6 current solution solves it.  The doubt
I have is about the DS-MIPv6 tunnel MN-HA ending in HA's IPv4 address.
Is this so?

Also, maybe DS-MIPv6 assumes a form of IPv4-in-IPv6 encapsulation
between the GW (pictured) and the HA?

We have both mentioned existing v4-v6 transitioning methods, no need to
enhance them, just re-use them - ok.  But not sure between what and
what.  When I think re-using transitioning schemes is IPv6-in-IPv4
between GW and border on IPv6 Internet.  This is _not_ IPv4-in-IPv6
between GW and HA.  Do you assume this latter?

Any clarification helpful, thanks,

Alex


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



From mip6-bounces@ietf.org Fri Jul 14 13:26:37 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G1RQx-0004ga-C2; Fri, 14 Jul 2006 13:26:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G1RQv-0004fz-SG
	for mip6@ietf.org; Fri, 14 Jul 2006 13:26:33 -0400
Received: from av8-2-sn3.vrr.skanova.net ([81.228.9.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G1RQu-00089S-Bz
	for mip6@ietf.org; Fri, 14 Jul 2006 13:26:33 -0400
Received: by av8-2-sn3.vrr.skanova.net (Postfix, from userid 502)
	id B876238341; Fri, 14 Jul 2006 19:26:31 +0200 (CEST)
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 A7A06382D4; Fri, 14 Jul 2006 19:26:31 +0200 (CEST)
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 7CD2737E45;
	Fri, 14 Jul 2006 19:26:31 +0200 (CEST)
Received: from localhost ([127.0.0.1])
	by shiraz.levkowetz.com with esmtp (Exim 4.62)
	(envelope-from <henrik@levkowetz.com>)
	id 1G1RQt-0002M9-2g; Fri, 14 Jul 2006 19:26:31 +0200
Message-ID: <44B7D3C6.8000903@levkowetz.com>
Date: Fri, 14 Jul 2006 13:26:30 -0400
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Thunderbird 1.5.0.4 (Macintosh/20060530)
MIME-Version: 1.0
To: Alexandru Petrescu <alexandru.petrescu@motorola.com>
References: <44B6C29C.1050308@motorola.com> <44B7A0C6.8040202@levkowetz.com>
	<44B7C66B.8030304@motorola.com>
In-Reply-To: <44B7C66B.8030304@motorola.com>
X-Enigmail-Version: 0.94.0.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 127.0.0.1
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: 92df29fa99cf13e554b84c8374345c17
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>
Subject: [Mip6] Re: topology about v4-v6 migration
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi Alex,

  Snipping some stuff, and responding inline:

on 2006-07-14 12:29 Alexandru Petrescu said the following:
...
>> on 2006-07-13 18:01 Alexandru Petrescu said the following:
>>> Hi Henrik, per your request on the scenario of IPv6-IPv4 deployment
>>>  I mentioned today in the MIP6 WG meeting.  Below is the topology 
>>> I've had in mind:
>>> 
> 
>    +--+
>    |CN|
>    +--+
>     |
>   ------------------
> / IPv6-only        \____
> \ "island" network /    |
>   ------------------     |
>                          |
>                          |
>                          |
>   ----------------       |    +---+     -------------    +----------+
> / IPv4-only      \__IPv4_____|GW |____/ IPv6-only   \___| HA       |
> \ access network /  Internet +---+    \ home network/   | IPv6-only|
>   ----------------                      -------------    +----------+
>        .
>        |
>      +--+
>      |MN|
>      +--+
> 
> 
>>> The MN is "owned" by an IPv6 HA deep in an IPv6-only network, 
>>> presumably some operator's network.  MN connects to another 
>>> operator's IPv4-only wireless access.  It needs to communicate with
>>>  an IPv6-only CN, present on an IPv6-only "island" network.
>>> 
>>> The IPv4-only access network, the IPv6-only home network and the 
>>> IPv6-only "island" network are connected together on the IPv4 
>>> Internet

...

> I am not sure though how DS-MIPv6 current solution solves it.  The doubt
> I have is about the DS-MIPv6 tunnel MN-HA ending in HA's IPv4 address.
> Is this so?

More precise is to say that the HA has to be reachable through an
IPv4 address somehow.  This could be an address on the GW which
is forwarded to the HA through a tunnel, exactly as you mention
next:

> Also, maybe DS-MIPv6 assumes a form of IPv4-in-IPv6 encapsulation
> between the GW (pictured) and the HA?
> 
> We have both mentioned existing v4-v6 transitioning methods, no need to
> enhance them, just re-use them - ok.  But not sure between what and
> what.  When I think re-using transitioning schemes is IPv6-in-IPv4
> between GW and border on IPv6 Internet.  This is _not_ IPv4-in-IPv6
> between GW and HA.  Do you assume this latter?

Some kind of tunnelled forwarding between HA and the IPv4 address on
the GW would be necessary, yes.  Exactly what is used is not
important, as long as the HA is reachable through that IPv4 address
and is aware that it has that IPv4 address.

Regards,

	Henrik

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



From mip6-bounces@ietf.org Fri Jul 14 18:39:08 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G1WIY-0005ZH-5E; Fri, 14 Jul 2006 18:38:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G1WIV-0005Xs-HB; Fri, 14 Jul 2006 18:38:11 -0400
Received: from nit.isi.edu ([128.9.160.116])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1G1Viu-0005Ep-CS; Fri, 14 Jul 2006 18:01:25 -0400
Received: from nit.isi.edu (loopback [127.0.0.1])
	by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id k6EM1Nt3018313; 
	Fri, 14 Jul 2006 15:01:23 -0700
Received: (from apache@localhost)
	by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id k6EM1NNt018312;
	Fri, 14 Jul 2006 15:01:23 -0700
Date: Fri, 14 Jul 2006 15:01:23 -0700
Message-Id: <200607142201.k6EM1NNt018312@nit.isi.edu>
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
X-Spam-Score: -14.8 (--------------)
X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81
Cc: mip6@ietf.org, rfc-editor@rfc-editor.org
Subject: [Mip6] RFC 4584 on Extension to Sockets API for Mobile IPv6
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org


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

        
        RFC 4584

        Title:      Extension to Sockets API for 
                    Mobile IPv6 
        Author:     S. Chakrabarti, E. Nordmark
        Status:     Informational
        Date:       July 2006
        Mailbox:    samitac2@gmail.com, 
                    erik.nordmark@sun.com
        Pages:      25
        Characters: 53995
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mip6-mipext-advapi-07.txt

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

This document describes data structures and API support for Mobile
IPv6 as an extension to the Advanced Socket API for IPv6.

Just as the Advanced Sockets API for IPv6 gives access to various
extension headers and the ICMPv6 protocol, this document specifies
the same level of access for Mobile IPv6 components.  It specifies a
mechanism for applications to retrieve and set information for
Mobility Header messages, Home Address destination options, and
Routing Header Type 2 extension headers.  It also specifies the
common data structures and definitions that might be used by certain
advanced Mobile IPv6 socket applications.  This memo provides information 
for the Internet community.

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

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

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

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

help: ways_to_get_rfcs. For example:

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

        help: ways_to_get_rfcs

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

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


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

...



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



From mip6-bounces@ietf.org Mon Jul 17 18:03:22 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G2bBF-0000xI-Et; Mon, 17 Jul 2006 18:03:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G2bBE-0000xD-JX
	for mip6@ietf.org; Mon, 17 Jul 2006 18:03:08 -0400
Received: from key1.docomolabs-usa.com ([216.98.102.225]
	helo=fridge.docomolabs-usa.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G2bBD-0006wL-7Y
	for mip6@ietf.org; Mon, 17 Jul 2006 18:03:08 -0400
Message-ID: <040001c6a9ed$08e20010$196115ac@dcml.docomolabsusa.com>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: <mip6@ietf.org>
Date: Mon, 17 Jul 2006 15:04:54 -0700
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="Windows-1252";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Subject: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

I was at Wimax Forum last week and I think I now understand why they and 
3GPP2 want to use RFC 4285 auth option rather than IPsec. One issue - lack 
of EAP support for client auth - is solved by IKEv2 and they seem to now be 
moving in the direction of recommending IKEv2 if people want to deploy 
IPsec. But the other issue is a bit more complex. 802.16, like most cellular 
protocols, has extensive support for dormant mode, and Wimax Forum is 
supporting dormant mode in their network design. If IPsec is used, then 
there is a risk when a mobile node goes into dormant mode that the IPsec SA 
may time out. It is unfortunate that this was not brought up when the 
discussion about RFC 4285 was happening, but I think this might be something 
that the WG could work on now as part of the new charter. This would make 
IKEv2/IPsec more attractive as a security option for cellular operators.

Comments?

            jak



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



From mip6-bounces@ietf.org Mon Jul 17 18:43:56 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G2boe-000407-Tp; Mon, 17 Jul 2006 18:43:52 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G2boc-000401-US
	for mip6@ietf.org; Mon, 17 Jul 2006 18:43:50 -0400
Received: from mail1.azairenet.com ([66.92.223.4] helo=bart.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G2bob-00029h-Iv
	for mip6@ietf.org; Mon, 17 Jul 2006 18:43:50 -0400
Received: from [10.1.201.20] ([10.1.201.20]) by bart.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Mon, 17 Jul 2006 15:43:46 -0700
Message-ID: <44BC129E.7050901@azairenet.com>
Date: Mon, 17 Jul 2006 15:43:42 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.4 (Windows/20060516)
MIME-Version: 1.0
To: James Kempf <kempf@docomolabs-usa.com>
Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
References: <040001c6a9ed$08e20010$196115ac@dcml.docomolabsusa.com>
In-Reply-To: <040001c6a9ed$08e20010$196115ac@dcml.docomolabsusa.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 17 Jul 2006 22:43:46.0267 (UTC)
	FILETIME=[768B7AB0:01C6A9F2]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

the dormant mode extensions sounds good to me. we could do
this extension. one issue to consider - what triggers this
message? how does Mobile IP know the mobile node is going
into a dormant mode. if we have the trigger we should be
okay.

but we have to check if this was the issue. with IKEv1 you
could negotiate a lifetime for the IPsec SA. IKEv2 does not
have the IPsec SA lifetime feature. so keepalives are
needed.

James Kempf wrote:
> I was at Wimax Forum last week and I think I now understand why they and 
> 3GPP2 want to use RFC 4285 auth option rather than IPsec. One issue - 
> lack of EAP support for client auth - is solved by IKEv2 and they seem 
> to now be moving in the direction of recommending IKEv2 if people want 
> to deploy IPsec. 

yes this was one of the main issues.

the way I saw it folks in 3GPP2 liked RFC 4285 because it
is very similar to the MIPv4 mechanism and they were
comfortable with it.

Vijay

But the other issue is a bit more complex. 802.16, like
> most cellular protocols, has extensive support for dormant mode, and 
> Wimax Forum is supporting dormant mode in their network design. If IPsec 
> is used, then there is a risk when a mobile node goes into dormant mode 
> that the IPsec SA may time out. It is unfortunate that this was not 
> brought up when the discussion about RFC 4285 was happening, but I think 
> this might be something that the WG could work on now as part of the new 
> charter. This would make IKEv2/IPsec more attractive as a security 
> option for cellular operators.
> 
> Comments?
> 
>            jak
> 
> 
> 
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6


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



From mip6-bounces@ietf.org Tue Jul 18 07:03:58 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G2nMm-0004TG-Le; Tue, 18 Jul 2006 07:03:52 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G2nMl-0004TB-BS
	for mip6@ietf.org; Tue, 18 Jul 2006 07:03:51 -0400
Received: from py-out-1112.google.com ([64.233.166.178])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G2nMj-0007bB-3K
	for mip6@ietf.org; Tue, 18 Jul 2006 07:03:51 -0400
Received: by py-out-1112.google.com with SMTP id n25so1886646pyg
	for <mip6@ietf.org>; Tue, 18 Jul 2006 04:03:48 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=WJ+sFwcVhrSmwIquWrrNF5AnlaAoMmKCI6QDVuZRUqUvFX34HndDXGx902pGkufaAtx7T7mHfWRdZSWxhxyJcp79t64ydvmVnAwBoySYxzMa24ELeqOJDrubrxKL7r+IKPm76FaqgALvBuwSnQVga66sFlPOLSyPMQDNVDarfL4=
Received: by 10.35.121.9 with SMTP id y9mr5339516pym;
	Tue, 18 Jul 2006 04:03:48 -0700 (PDT)
Received: by 10.35.111.9 with HTTP; Tue, 18 Jul 2006 04:03:48 -0700 (PDT)
Message-ID: <729b68be0607180403o6915425dke00541f8a5124de4@mail.gmail.com>
Date: Tue, 18 Jul 2006 13:03:48 +0200
From: "Jean-Michel Combes" <jeanmichel.combes@gmail.com>
To: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
In-Reply-To: <44BC129E.7050901@azairenet.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <040001c6a9ed$08e20010$196115ac@dcml.docomolabsusa.com>
	<44BC129E.7050901@azairenet.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Cc: mip6@ietf.org, James Kempf <kempf@docomolabs-usa.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi,

I didn't follow the works about "Dormant Mode Host" DT in the Seamoby
WG but was there not such a issue debated in this DT?

Best regards.

JMC.

2006/7/18, Vijay Devarapalli <vijay.devarapalli@azairenet.com>:
> the dormant mode extensions sounds good to me. we could do
> this extension. one issue to consider - what triggers this
> message? how does Mobile IP know the mobile node is going
> into a dormant mode. if we have the trigger we should be
> okay.
>
> but we have to check if this was the issue. with IKEv1 you
> could negotiate a lifetime for the IPsec SA. IKEv2 does not
> have the IPsec SA lifetime feature. so keepalives are
> needed.
>
> James Kempf wrote:
> > I was at Wimax Forum last week and I think I now understand why they and
> > 3GPP2 want to use RFC 4285 auth option rather than IPsec. One issue -
> > lack of EAP support for client auth - is solved by IKEv2 and they seem
> > to now be moving in the direction of recommending IKEv2 if people want
> > to deploy IPsec.
>
> yes this was one of the main issues.
>
> the way I saw it folks in 3GPP2 liked RFC 4285 because it
> is very similar to the MIPv4 mechanism and they were
> comfortable with it.
>
> Vijay
>
> But the other issue is a bit more complex. 802.16, like
> > most cellular protocols, has extensive support for dormant mode, and
> > Wimax Forum is supporting dormant mode in their network design. If IPsec
> > is used, then there is a risk when a mobile node goes into dormant mode
> > that the IPsec SA may time out. It is unfortunate that this was not
> > brought up when the discussion about RFC 4285 was happening, but I think
> > this might be something that the WG could work on now as part of the new
> > charter. This would make IKEv2/IPsec more attractive as a security
> > option for cellular operators.
> >
> > Comments?
> >
> >            jak
> >
> >
> >
> > _______________________________________________
> > Mip6 mailing list
> > Mip6@ietf.org
> > https://www1.ietf.org/mailman/listinfo/mip6
>
>
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
>

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



From mip6-bounces@ietf.org Tue Jul 18 07:31:23 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G2nnM-0002Fg-HH; Tue, 18 Jul 2006 07:31:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G2nnL-0002Bs-IK
	for mip6@ietf.org; Tue, 18 Jul 2006 07:31:19 -0400
Received: from py-out-1112.google.com ([64.233.166.182])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G2nnK-0001Qd-Cn
	for mip6@ietf.org; Tue, 18 Jul 2006 07:31:19 -0400
Received: by py-out-1112.google.com with SMTP id n25so1894596pyg
	for <mip6@ietf.org>; Tue, 18 Jul 2006 04:31:18 -0700 (PDT)
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=Nr45vnh21s0v2c1+Xe+8RD2BIE4JJCdM4aRvS1aJqwmpjGCZ7qsNtvFT5OekWuXziGqf7SmGIFa7XEr8xUyeuHh3jQhx7w1l6V2sQ4Ql0bE3ItANkrIAku0yW+kwI6RJ0MLYAe96IP4Kf8DEnByubX7UQmOZWnPKrBCWUGhNRfI=
Received: by 10.35.9.15 with SMTP id m15mr5370248pyi;
	Tue, 18 Jul 2006 04:31:18 -0700 (PDT)
Received: by 10.35.111.9 with HTTP; Tue, 18 Jul 2006 04:31:17 -0700 (PDT)
Message-ID: <729b68be0607180431m773dc847qed3e7350819a8d04@mail.gmail.com>
Date: Tue, 18 Jul 2006 13:31:18 +0200
From: "Jean-Michel Combes" <jeanmichel.combes@gmail.com>
To: "Mobile IPv6 Mailing List" <mip6@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: 68c8cc8a64a9d0402e43b8eee9fc4199
Subject: [Mip6] New charter item: HA assignment
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi,

as promised during the mip6 session, here is a point which, IMO, is
important from a MSP's point of view:
Actually, the bootstrapping solution, in the split scenario, only
propose a HA discovery mechanism (i.e. the MN receives a list of HA,
from DNS, and chooses one of them). The MSP has no easy solution to
enforce one MN to have a specific HA.

Best regards.

JMC.

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



From mip6-bounces@ietf.org Tue Jul 18 10:36:43 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G2qga-0004YI-4m; Tue, 18 Jul 2006 10:36:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G2qgY-0004YD-UM
	for mip6@ietf.org; Tue, 18 Jul 2006 10:36:30 -0400
Received: from web60324.mail.yahoo.com ([209.73.178.132])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1G2qgY-0003gG-Gw
	for mip6@ietf.org; Tue, 18 Jul 2006 10:36:30 -0400
Received: (qmail 30269 invoked by uid 60001); 18 Jul 2006 14:36:30 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=Message-ID:Received:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type;
	b=SsdCh0Z7wlYFdvZYrk1hX+KetIGUVGQSxWkF5H5Up77+eDSJF6hyOowbX+xcbu/VMASAIiYqZ4abzF9Q8US3LjP4InhRFVoJujuGtxYvfNjVHhxKdTi2OX2exqqaGDRjgunXnkxIKGT+KZvCOq918vDqdRL7eChuZJ4QcBvTjxI=
	; 
Message-ID: <20060718143630.30267.qmail@web60324.mail.yahoo.com>
Received: from [12.129.211.52] by web60324.mail.yahoo.com via HTTP;
	Tue, 18 Jul 2006 07:36:30 PDT
Date: Tue, 18 Jul 2006 07:36:30 -0700 (PDT)
From: Behcet Sarikaya <behcetsarikaya@yahoo.com>
Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
To: Jean-Michel Combes <jeanmichel.combes@gmail.com>,
	Vijay Devarapalli <vijay.devarapalli@azairenet.com>
In-Reply-To: <729b68be0607180403o6915425dke00541f8a5124de4@mail.gmail.com>
MIME-Version: 1.0
X-Spam-Score: 0.5 (/)
X-Scan-Signature: cf3becbbd6d1a45acbe2ffd4ab88bdc2
Cc: mip6@ietf.org, James Kempf <kempf@docomolabs-usa.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Behcet Sarikaya <sarikaya@ieee.org>
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1839086060=="
Errors-To: mip6-bounces@ietf.org

--===============1839086060==
Content-Type: multipart/alternative; boundary="0-1211617642-1153233390=:29451"

--0-1211617642-1153233390=:29451
Content-Type: text/plain; charset=us-ascii

Hi Jean-Michel,
  Seamoby WG had the dormant mode "things" in its charter, but after producing an architecture document (now RFC 3154) it got dropped from the charter.

Regards,

--behcet

----- Original Message ----
From: Jean-Michel Combes <jeanmichel.combes@gmail.com>
To: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
Cc: mip6@ietf.org; James Kempf <kempf@docomolabs-usa.com>
Sent: Tuesday, July 18, 2006 6:03:48 AM
Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?

Hi,

I didn't follow the works about "Dormant Mode Host" DT in the Seamoby
WG but was there not such a issue debated in this DT?

Best regards.

JMC.

2006/7/18, Vijay Devarapalli <vijay.devarapalli@azairenet.com>:
> the dormant mode extensions sounds good to me. we could do
> this extension. one issue to consider - what triggers this
> message? how does Mobile IP know the mobile node is going
> into a dormant mode. if we have the trigger we should be
> okay.
>
> but we have to check if this was the issue. with IKEv1 you
> could negotiate a lifetime for the IPsec SA. IKEv2 does not
> have the IPsec SA lifetime feature. so keepalives are
> needed.
>
> James Kempf wrote:
> > I was at Wimax Forum last week and I think I now understand why they and
> > 3GPP2 want to use RFC 4285 auth option rather than IPsec. One issue -
> > lack of EAP support for client auth - is solved by IKEv2 and they seem
> > to now be moving in the direction of recommending IKEv2 if people want
> > to deploy IPsec.
>
> yes this was one of the main issues.
>
> the way I saw it folks in 3GPP2 liked RFC 4285 because it
> is very similar to the MIPv4 mechanism and they were
> comfortable with it.
>
> Vijay
>
> But the other issue is a bit more complex. 802.16, like
> > most cellular protocols, has extensive support for dormant mode, and
> > Wimax Forum is supporting dormant mode in their network design. If IPsec
> > is used, then there is a risk when a mobile node goes into dormant mode
> > that the IPsec SA may time out. It is unfortunate that this was not
> > brought up when the discussion about RFC 4285 was happening, but I think
> > this might be something that the WG could work on now as part of the new
> > charter. This would make IKEv2/IPsec more attractive as a security
> > option for cellular operators.
> >
> > Comments?
> >
> >            jak
> >
> >
> >
> > _______________________________________________
> > Mip6 mailing list
> > Mip6@ietf.org
> > https://www1.ietf.org/mailman/listinfo/mip6
>
>
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
>

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





--0-1211617642-1153233390=:29451
Content-Type: text/html; charset=us-ascii

<html><head><style type="text/css"><!-- DIV {margin:0px} --></style></head><body><div style="font-family:times new roman, new york, times, serif;font-size:12pt"><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;">Hi Jean-Michel,<br>&nbsp; Seamoby WG had the dormant mode "things" in its charter, but after producing an architecture document (now RFC 3154) it got dropped from the charter.<br><br>Regards,<br><br>--behcet<br><br><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;">----- Original Message ----<br>From: Jean-Michel Combes &lt;jeanmichel.combes@gmail.com&gt;<br>To: Vijay Devarapalli &lt;vijay.devarapalli@azairenet.com&gt;<br>Cc: mip6@ietf.org; James Kempf &lt;kempf@docomolabs-usa.com&gt;<br>Sent: Tuesday, July 18, 2006 6:03:48 AM<br>Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?<br><br><div>Hi,<br><br>I didn't follow the works about "Dormant Mode Host" DT in the Seamoby<br>WG but
 was there not such a issue debated in this DT?<br><br>Best regards.<br><br>JMC.<br><br>2006/7/18, Vijay Devarapalli &lt;vijay.devarapalli@azairenet.com&gt;:<br>&gt; the dormant mode extensions sounds good to me. we could do<br>&gt; this extension. one issue to consider - what triggers this<br>&gt; message? how does Mobile IP know the mobile node is going<br>&gt; into a dormant mode. if we have the trigger we should be<br>&gt; okay.<br>&gt;<br>&gt; but we have to check if this was the issue. with IKEv1 you<br>&gt; could negotiate a lifetime for the IPsec SA. IKEv2 does not<br>&gt; have the IPsec SA lifetime feature. so keepalives are<br>&gt; needed.<br>&gt;<br>&gt; James Kempf wrote:<br>&gt; &gt; I was at Wimax Forum last week and I think I now understand why they and<br>&gt; &gt; 3GPP2 want to use RFC 4285 auth option rather than IPsec. One issue -<br>&gt; &gt; lack of EAP support for client auth - is solved by IKEv2 and they seem<br>&gt; &gt; to now be moving in the
 direction of recommending IKEv2 if people want<br>&gt; &gt; to deploy IPsec.<br>&gt;<br>&gt; yes this was one of the main issues.<br>&gt;<br>&gt; the way I saw it folks in 3GPP2 liked RFC 4285 because it<br>&gt; is very similar to the MIPv4 mechanism and they were<br>&gt; comfortable with it.<br>&gt;<br>&gt; Vijay<br>&gt;<br>&gt; But the other issue is a bit more complex. 802.16, like<br>&gt; &gt; most cellular protocols, has extensive support for dormant mode, and<br>&gt; &gt; Wimax Forum is supporting dormant mode in their network design. If IPsec<br>&gt; &gt; is used, then there is a risk when a mobile node goes into dormant mode<br>&gt; &gt; that the IPsec SA may time out. It is unfortunate that this was not<br>&gt; &gt; brought up when the discussion about RFC 4285 was happening, but I think<br>&gt; &gt; this might be something that the WG could work on now as part of the new<br>&gt; &gt; charter. This would make IKEv2/IPsec more attractive as a security<br>&gt; &gt;
 option for cellular operators.<br>&gt; &gt;<br>&gt; &gt; Comments?<br>&gt; &gt;<br>&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;jak<br>&gt; &gt;<br>&gt; &gt;<br>&gt; &gt;<br>&gt; &gt; _______________________________________________<br>&gt; &gt; Mip6 mailing list<br>&gt; &gt; Mip6@ietf.org<br>&gt; &gt; <a target="_blank" href="https://www1.ietf.org/mailman/listinfo/mip6">https://www1.ietf.org/mailman/listinfo/mip6</a><br>&gt;<br>&gt;<br>&gt; _______________________________________________<br>&gt; Mip6 mailing list<br>&gt; Mip6@ietf.org<br>&gt; <a target="_blank" href="https://www1.ietf.org/mailman/listinfo/mip6">https://www1.ietf.org/mailman/listinfo/mip6</a><br>&gt;<br><br>_______________________________________________<br>Mip6 mailing list<br>Mip6@ietf.org<br><a target="_blank" href="https://www1.ietf.org/mailman/listinfo/mip6">https://www1.ietf.org/mailman/listinfo/mip6</a><br></div></div><br></div></div></body></html>
--0-1211617642-1153233390=:29451--


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

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

--===============1839086060==--




From mip6-bounces@ietf.org Tue Jul 18 12:15:21 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G2sEB-0000BF-Av; Tue, 18 Jul 2006 12:15:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G2sEA-0000BA-Cx
	for mip6@ietf.org; Tue, 18 Jul 2006 12:15:18 -0400
Received: from key1.docomolabs-usa.com ([216.98.102.225]
	helo=fridge.docomolabs-usa.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G2sE8-0002sQ-Uz
	for mip6@ietf.org; Tue, 18 Jul 2006 12:15:18 -0400
Message-ID: <01bc01c6aa85$a057f8d0$196115ac@dcml.docomolabsusa.com>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
References: <040001c6a9ed$08e20010$196115ac@dcml.docomolabsusa.com>
	<44BC129E.7050901@azairenet.com>
Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
Date: Tue, 18 Jul 2006 09:17:11 -0700
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="Windows-1252";
	reply-type=response
Content-Transfer-Encoding: 7bit
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

For security, the message would need to be sent within an SA. There is a 
question about which.

One possibility is to do a Mobility Extension (call the messages Sleeping 
and WakingUp) and send it within the IPsec SA between the HA and MN. The MN 
sends the Sleeping message when it is about to go into dormant mode, it 
sends the WakingUp message when it comes out again. The WakingUp message 
isn't needed for the MN to get mobility service, it is just there for 
optimizing the SA timeouts. This would require a special API on the HA 
between the MIP code and IKE code for the HA to extend the IPsec SA 
lifetime, similar to the one for IKEv1 mobility. The solution would only be 
applicable to Mobile IP.

The other possibility is to do an IKEv2 INFORMATIONAL message that is sent 
within the IKE SA. It works similarly, but there would be no need for any 
API on the HA, since the IKE code itself would process it (actually, I 
proposed something like this to the Mobike WG but they didn't see the need 
for it). This would be applicable to both Mobike and Mobile IP (and any 
other security protocol that uses IKEv2, so maybe HIP as well).

One question is, does the HA need to do anything else if the MN goes into 
dormant mode? I think there are lots of things it could do (lengthen the BU 
timeout, apply a filter that is either mobile specified or part of the 
user's service profile with the operator to only allow specific traffic 
through, etc.) but I would really like to keep things simple.

            jak

----- Original Message ----- 
From: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
To: "James Kempf" <kempf@docomolabs-usa.com>
Cc: <mip6@ietf.org>
Sent: Monday, July 17, 2006 3:43 PM
Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?


> the dormant mode extensions sounds good to me. we could do
> this extension. one issue to consider - what triggers this
> message? how does Mobile IP know the mobile node is going
> into a dormant mode. if we have the trigger we should be
> okay.
>
> but we have to check if this was the issue. with IKEv1 you
> could negotiate a lifetime for the IPsec SA. IKEv2 does not
> have the IPsec SA lifetime feature. so keepalives are
> needed.
>
> James Kempf wrote:
>> I was at Wimax Forum last week and I think I now understand why they and 
>> 3GPP2 want to use RFC 4285 auth option rather than IPsec. One issue - 
>> lack of EAP support for client auth - is solved by IKEv2 and they seem to 
>> now be moving in the direction of recommending IKEv2 if people want to 
>> deploy IPsec.
>
> yes this was one of the main issues.
>
> the way I saw it folks in 3GPP2 liked RFC 4285 because it
> is very similar to the MIPv4 mechanism and they were
> comfortable with it.
>
> Vijay
>
> But the other issue is a bit more complex. 802.16, like
>> most cellular protocols, has extensive support for dormant mode, and 
>> Wimax Forum is supporting dormant mode in their network design. If IPsec 
>> is used, then there is a risk when a mobile node goes into dormant mode 
>> that the IPsec SA may time out. It is unfortunate that this was not 
>> brought up when the discussion about RFC 4285 was happening, but I think 
>> this might be something that the WG could work on now as part of the new 
>> charter. This would make IKEv2/IPsec more attractive as a security option 
>> for cellular operators.
>>
>> Comments?
>>
>>            jak
>>
>>
>>
>> _______________________________________________
>> Mip6 mailing list
>> Mip6@ietf.org
>> https://www1.ietf.org/mailman/listinfo/mip6
>
> 



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



From mip6-bounces@ietf.org Tue Jul 18 13:01:04 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G2swM-0001Xj-MV; Tue, 18 Jul 2006 13:00:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G2swI-0001Tw-Tj
	for mip6@ietf.org; Tue, 18 Jul 2006 13:00:54 -0400
Received: from key1.docomolabs-usa.com ([216.98.102.225]
	helo=fridge.docomolabs-usa.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G2siU-0000wh-ME
	for mip6@ietf.org; Tue, 18 Jul 2006 12:46:40 -0400
Message-ID: <021001c6aa89$fdf60c80$196115ac@dcml.docomolabsusa.com>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Jean-Michel Combes" <jeanmichel.combes@gmail.com>,
	"Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
References: <040001c6a9ed$08e20010$196115ac@dcml.docomolabsusa.com>
	<44BC129E.7050901@azairenet.com>
	<729b68be0607180403o6915425dke00541f8a5124de4@mail.gmail.com>
Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
Date: Tue, 18 Jul 2006 09:48:27 -0700
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=response
Content-Transfer-Encoding: 7bit
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Seamboy looked at "IP paging". This was a much more ambitious and far 
reaching proposal, involving a IP level location management system separate 
from Mobile IP specifically for dormant mode hosts. What I'm proposing is 
much, much simpler, just a MIP or IKE message to tell the HA when the MN 
goes into or comes out of dormant mode.

            jak

----- Original Message ----- 
From: "Jean-Michel Combes" <jeanmichel.combes@gmail.com>
To: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
Cc: "James Kempf" <kempf@docomolabs-usa.com>; <mip6@ietf.org>
Sent: Tuesday, July 18, 2006 4:03 AM
Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?


> Hi,
>
> I didn't follow the works about "Dormant Mode Host" DT in the Seamoby
> WG but was there not such a issue debated in this DT?
>
> Best regards.
>
> JMC.
>
> 2006/7/18, Vijay Devarapalli <vijay.devarapalli@azairenet.com>:
>> the dormant mode extensions sounds good to me. we could do
>> this extension. one issue to consider - what triggers this
>> message? how does Mobile IP know the mobile node is going
>> into a dormant mode. if we have the trigger we should be
>> okay.
>>
>> but we have to check if this was the issue. with IKEv1 you
>> could negotiate a lifetime for the IPsec SA. IKEv2 does not
>> have the IPsec SA lifetime feature. so keepalives are
>> needed.
>>
>> James Kempf wrote:
>> > I was at Wimax Forum last week and I think I now understand why they 
>> > and
>> > 3GPP2 want to use RFC 4285 auth option rather than IPsec. One issue -
>> > lack of EAP support for client auth - is solved by IKEv2 and they seem
>> > to now be moving in the direction of recommending IKEv2 if people want
>> > to deploy IPsec.
>>
>> yes this was one of the main issues.
>>
>> the way I saw it folks in 3GPP2 liked RFC 4285 because it
>> is very similar to the MIPv4 mechanism and they were
>> comfortable with it.
>>
>> Vijay
>>
>> But the other issue is a bit more complex. 802.16, like
>> > most cellular protocols, has extensive support for dormant mode, and
>> > Wimax Forum is supporting dormant mode in their network design. If 
>> > IPsec
>> > is used, then there is a risk when a mobile node goes into dormant mode
>> > that the IPsec SA may time out. It is unfortunate that this was not
>> > brought up when the discussion about RFC 4285 was happening, but I 
>> > think
>> > this might be something that the WG could work on now as part of the 
>> > new
>> > charter. This would make IKEv2/IPsec more attractive as a security
>> > option for cellular operators.
>> >
>> > Comments?
>> >
>> >            jak
>> >
>> >
>> >
>> > _______________________________________________
>> > Mip6 mailing list
>> > Mip6@ietf.org
>> > https://www1.ietf.org/mailman/listinfo/mip6
>>
>>
>> _______________________________________________
>> Mip6 mailing list
>> Mip6@ietf.org
>> https://www1.ietf.org/mailman/listinfo/mip6
>>
> 



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



From mip6-bounces@ietf.org Tue Jul 18 13:29:14 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G2tNc-00059W-AC; Tue, 18 Jul 2006 13:29:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G2swF-0001Pt-Dc
	for mip6@ietf.org; Tue, 18 Jul 2006 13:00:51 -0400
Received: from motgate5.mot.com ([144.189.100.105])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G2skz-0002Do-Kk
	for mip6@ietf.org; Tue, 18 Jul 2006 12:49:14 -0400
Received: from az33exr03.mot.com (az33exr03.mot.com [10.64.251.233])
	by motgate5.mot.com (8.12.11/Motorola) with ESMTP id k6IGnBDC005105;
	Tue, 18 Jul 2006 09:49:11 -0700 (MST)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by az33exr03.mot.com (8.13.1/8.13.0) with ESMTP id k6IGn9Ah019913;
	Tue, 18 Jul 2006 11:49:10 -0500 (CDT)
Message-ID: <44BD1105.5040904@motorola.com>
Date: Tue, 18 Jul 2006 18:49:09 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: Jean-Michel Combes <jeanmichel.combes@gmail.com>
Subject: Re: [Mip6] New charter item: HA assignment
References: <729b68be0607180431m773dc847qed3e7350819a8d04@mail.gmail.com>
In-Reply-To: <729b68be0607180431m773dc847qed3e7350819a8d04@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAQAAAAQ=
X-White-List-Member: TRUE
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Jean-Michel Combes wrote:
> Hi,
> 
> as promised during the mip6 session, here is a point which, IMO, is 
> important from a MSP's point of view: Actually, the bootstrapping 
> solution, in the split scenario, only propose a HA discovery 
> mechanism (i.e. the MN receives a list of HA, from DNS, and chooses 
> one of them). The MSP has no easy solution to enforce one MN to have 
> a specific HA.

One possible way is for a HA to stop sending BAck, at which point an MN
would send DHAAD Request again, and a different HA replies back DHAAD,
so end result is MN is assigned a new HA.

Another way is for the new HA to send Binding Refresh Request to MN
(even if it has no BC entry for it).

Another way, if the split bootstrapping advances, is for the MSP to
dynamically update the DNS data about HAs, so when MN bootstraps it
obtains a different HA.

If the HA address is discovered with DHCP then I think the DHCP Server
can send specific messages to MN (unsolicited by MN).

It would require relaxing some language in rfc 3775 and probably 
extending BRR.

It would be helpful to know when would an MSP like the MN to choose a
different HA, for what reasons.

Alex


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



From mip6-bounces@ietf.org Tue Jul 18 14:23:55 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G2uEc-0007B7-5k; Tue, 18 Jul 2006 14:23:54 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G2uEa-0007Az-AO
	for mip6@ietf.org; Tue, 18 Jul 2006 14:23:52 -0400
Received: from mx0.starentnetworks.com ([12.38.223.203])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G2uEZ-0003jx-Sr
	for mip6@ietf.org; Tue, 18 Jul 2006 14:23:52 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mx0.starentnetworks.com (Postfix) with ESMTP id 2F66790012;
	Tue, 18 Jul 2006 14:23:48 -0400 (EDT)
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 13086-04; Tue, 18 Jul 2006 14:23:43 -0400 (EDT)
Received: from exchtewks1.starentnetworks.com (exchtewks1.starentnetworks.com
	[12.33.233.52]) by mx0.starentnetworks.com (Postfix) with ESMTP;
	Tue, 18 Jul 2006 14:23:43 -0400 (EDT)
X-MessageTextProcessor: DisclaimIt (2.70.271) [Starent Networks Corp.]
Received: from exchtewks2.starentnetworks.com ([12.33.232.12]) by
	exchtewks1.starentnetworks.com with Microsoft
	SMTPSVC(6.0.3790.1830); Tue, 18 Jul 2006 14:20:11 -0400
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
Date: Tue, 18 Jul 2006 14:20:11 -0400
Message-ID: <7CCD07160348804497EF29E9EA5560D73C52AD@exchtewks2.starentnetworks.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
thread-index: Acaqh1NuwgwIGr0yTsCWEGY4/UG0JAAD3SAw
From: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
To: "James Kempf" <kempf@docomolabs-usa.com>
Importance: normal
Priority: normal
X-OriginalArrivalTime: 18 Jul 2006 18:20:11.0483 (UTC)
	FILETIME=[CE9CB2B0:01C6AA96]
X-Virus-Scanned: amavisd-new 2.2.1 (20041222) at mx0.starentnetworks.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0770535483960d190d4a0d020e7060bd
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

James,

This is a good discussion. Indeed the need for IPsec keepalives (or DPD)
over the air when the MN is dormant (or idle) is an issue in the
cellular networks. The issue is Not that there are no mip6 messages
defined or the HA is not aware of dormancy. It is more of a paging
channel capacity issue, MN's battery life issue and the signaling
overhead to transport the keepalives for a dormant MN issue.

So, any new message however small won't solve the problem, IMHO.

-Kuntal


> -----Original Message-----
> From: James Kempf [mailto:kempf@docomolabs-usa.com]
> Sent: Tuesday, July 18, 2006 11:17 AM
> To: Vijay Devarapalli
> Cc: mip6@ietf.org
> Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert to
HA?
>=20
> For security, the message would need to be sent within an SA. There is
a
> question about which.
>=20
> One possibility is to do a Mobility Extension (call the messages
Sleeping
> and WakingUp) and send it within the IPsec SA between the HA and MN.
The
> MN
> sends the Sleeping message when it is about to go into dormant mode,
it
> sends the WakingUp message when it comes out again. The WakingUp
message
> isn't needed for the MN to get mobility service, it is just there for
> optimizing the SA timeouts. This would require a special API on the HA
> between the MIP code and IKE code for the HA to extend the IPsec SA
> lifetime, similar to the one for IKEv1 mobility. The solution would
only
> be
> applicable to Mobile IP.
>=20
> The other possibility is to do an IKEv2 INFORMATIONAL message that is
sent
> within the IKE SA. It works similarly, but there would be no need for
any
> API on the HA, since the IKE code itself would process it (actually, I
> proposed something like this to the Mobike WG but they didn't see the
need
> for it). This would be applicable to both Mobike and Mobile IP (and
any
> other security protocol that uses IKEv2, so maybe HIP as well).
>=20
> One question is, does the HA need to do anything else if the MN goes
into
> dormant mode? I think there are lots of things it could do (lengthen
the
> BU
> timeout, apply a filter that is either mobile specified or part of the
> user's service profile with the operator to only allow specific
traffic
> through, etc.) but I would really like to keep things simple.
>=20
>             jak
>=20
> ----- Original Message -----
> From: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
> To: "James Kempf" <kempf@docomolabs-usa.com>
> Cc: <mip6@ietf.org>
> Sent: Monday, July 17, 2006 3:43 PM
> Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert to
HA?
>=20
>=20
> > the dormant mode extensions sounds good to me. we could do
> > this extension. one issue to consider - what triggers this
> > message? how does Mobile IP know the mobile node is going
> > into a dormant mode. if we have the trigger we should be
> > okay.
> >
> > but we have to check if this was the issue. with IKEv1 you
> > could negotiate a lifetime for the IPsec SA. IKEv2 does not
> > have the IPsec SA lifetime feature. so keepalives are
> > needed.
> >
> > James Kempf wrote:
> >> I was at Wimax Forum last week and I think I now understand why
they
> and
> >> 3GPP2 want to use RFC 4285 auth option rather than IPsec. One issue
-
> >> lack of EAP support for client auth - is solved by IKEv2 and they
seem
> to
> >> now be moving in the direction of recommending IKEv2 if people want
to
> >> deploy IPsec.
> >
> > yes this was one of the main issues.
> >
> > the way I saw it folks in 3GPP2 liked RFC 4285 because it
> > is very similar to the MIPv4 mechanism and they were
> > comfortable with it.
> >
> > Vijay
> >
> > But the other issue is a bit more complex. 802.16, like
> >> most cellular protocols, has extensive support for dormant mode,
and
> >> Wimax Forum is supporting dormant mode in their network design. If
> IPsec
> >> is used, then there is a risk when a mobile node goes into dormant
mode
> >> that the IPsec SA may time out. It is unfortunate that this was not
> >> brought up when the discussion about RFC 4285 was happening, but I
> think
> >> this might be something that the WG could work on now as part of
the
> new
> >> charter. This would make IKEv2/IPsec more attractive as a security
> option
> >> for cellular operators.
> >>
> >> Comments?
> >>
> >>            jak
> >>
> >>
> >>
> >> _______________________________________________
> >> Mip6 mailing list
> >> Mip6@ietf.org
> >> https://www1.ietf.org/mailman/listinfo/mip6
> >
> >
>=20
>=20
>=20
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6


"This email message and any attachments are confidential information of =
Starent Networks, Corp. The information transmitted may not be used to =
create or change any contractual obligations of Starent Networks, Corp.  =
Any review, retransmission, dissemination or other use of, or taking of =
any action in reliance upon this e-mail and its attachments by persons =
or entities other than the intended recipient is prohibited. If you are =
not the intended recipient, please notify the sender immediately -- by =
replying to this message or by sending an email to =
postmaster@starentnetworks.com -- and destroy all copies of this message =
and any attachments without reading or disclosing their contents. Thank =
you."

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



From mip6-bounces@ietf.org Tue Jul 18 14:30:25 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G2uKs-0001qO-Au; Tue, 18 Jul 2006 14:30:22 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G2uKq-0001qJ-TW
	for mip6@ietf.org; Tue, 18 Jul 2006 14:30:20 -0400
Received: from mx0.starentnetworks.com ([12.38.223.203])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G2uKp-0004Dv-I8
	for mip6@ietf.org; Tue, 18 Jul 2006 14:30:20 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mx0.starentnetworks.com (Postfix) with ESMTP id 330EE90012;
	Tue, 18 Jul 2006 14:30:16 -0400 (EDT)
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 13287-02; Tue, 18 Jul 2006 14:30:11 -0400 (EDT)
Received: from exchtewks1.starentnetworks.com (exchtewks1.starentnetworks.com
	[12.33.233.52]) by mx0.starentnetworks.com (Postfix) with ESMTP;
	Tue, 18 Jul 2006 14:30:11 -0400 (EDT)
X-MessageTextProcessor: DisclaimIt (2.70.271) [Starent Networks Corp.]
Received: from exchtewks2.starentnetworks.com ([12.33.232.12]) by
	exchtewks1.starentnetworks.com with Microsoft
	SMTPSVC(6.0.3790.1830); Tue, 18 Jul 2006 14:26:38 -0400
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] New charter item: HA assignment
Date: Tue, 18 Jul 2006 14:26:38 -0400
Message-ID: <7CCD07160348804497EF29E9EA5560D73C52AE@exchtewks2.starentnetworks.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] New charter item: HA assignment
thread-index: AcaqkaD8fy7FszUGRmScxtlVkZBO9gABdLlQ
From: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
To: "Alexandru Petrescu" <alexandru.petrescu@motorola.com>,
	"Jean-Michel Combes" <jeanmichel.combes@gmail.com>
Importance: normal
Priority: normal
X-OriginalArrivalTime: 18 Jul 2006 18:26:38.0868 (UTC)
	FILETIME=[B582F540:01C6AA97]
X-Virus-Scanned: amavisd-new 2.2.1 (20041222) at mx0.starentnetworks.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Alex,

What you describe will require many round trips for the network (MSP) to
assign a HA. There is a fundamental difference between discovery and
assignment. What Jean-Michel brought up is the need in the industry for
HA assignment.

In the integrated scenario solution document we used AAA infrastructure
and DHCP to _assign_ the HA. May be operators interested in HA
assignment should use that instead of DNS.

-Kuntal


> -----Original Message-----
> From: Alexandru Petrescu [mailto:alexandru.petrescu@motorola.com]
> Sent: Tuesday, July 18, 2006 11:49 AM
> To: Jean-Michel Combes
> Cc: Mobile IPv6 Mailing List
> Subject: Re: [Mip6] New charter item: HA assignment
>=20
> Jean-Michel Combes wrote:
> > Hi,
> >
> > as promised during the mip6 session, here is a point which, IMO, is
> > important from a MSP's point of view: Actually, the bootstrapping
> > solution, in the split scenario, only propose a HA discovery
> > mechanism (i.e. the MN receives a list of HA, from DNS, and chooses
> > one of them). The MSP has no easy solution to enforce one MN to have
> > a specific HA.
>=20
> One possible way is for a HA to stop sending BAck, at which point an
MN
> would send DHAAD Request again, and a different HA replies back DHAAD,
> so end result is MN is assigned a new HA.
>=20
> Another way is for the new HA to send Binding Refresh Request to MN
> (even if it has no BC entry for it).
>=20
> Another way, if the split bootstrapping advances, is for the MSP to
> dynamically update the DNS data about HAs, so when MN bootstraps it
> obtains a different HA.
>=20
> If the HA address is discovered with DHCP then I think the DHCP Server
> can send specific messages to MN (unsolicited by MN).
>=20
> It would require relaxing some language in rfc 3775 and probably
> extending BRR.
>=20
> It would be helpful to know when would an MSP like the MN to choose a
> different HA, for what reasons.
>=20
> Alex
>=20
>=20
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6


"This email message and any attachments are confidential information of =
Starent Networks, Corp. The information transmitted may not be used to =
create or change any contractual obligations of Starent Networks, Corp.  =
Any review, retransmission, dissemination or other use of, or taking of =
any action in reliance upon this e-mail and its attachments by persons =
or entities other than the intended recipient is prohibited. If you are =
not the intended recipient, please notify the sender immediately -- by =
replying to this message or by sending an email to =
postmaster@starentnetworks.com -- and destroy all copies of this message =
and any attachments without reading or disclosing their contents. Thank =
you."

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



From mip6-bounces@ietf.org Tue Jul 18 14:30:37 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G2uL7-0001rn-Lc; Tue, 18 Jul 2006 14:30:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G2uL6-0001rf-7Y
	for mip6@ietf.org; Tue, 18 Jul 2006 14:30:36 -0400
Received: from mail1.azairenet.com ([66.92.223.4] helo=bart.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G2uL4-0004EC-U4
	for mip6@ietf.org; Tue, 18 Jul 2006 14:30:36 -0400
Received: from [10.1.201.20] ([10.1.201.20]) by bart.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Tue, 18 Jul 2006 11:30:33 -0700
Message-ID: <44BD28C9.50403@azairenet.com>
Date: Tue, 18 Jul 2006 11:30:33 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.4 (Windows/20060516)
MIME-Version: 1.0
To: Jean-Michel Combes <jeanmichel.combes@gmail.com>
Subject: Re: [Mip6] New charter item: HA assignment
References: <729b68be0607180431m773dc847qed3e7350819a8d04@mail.gmail.com>
In-Reply-To: <729b68be0607180431m773dc847qed3e7350819a8d04@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 18 Jul 2006 18:30:33.0049 (UTC)
	FILETIME=[41182490:01C6AA98]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Jean-Michel Combes wrote:
> Hi,
> 
> as promised during the mip6 session, here is a point which, IMO, is
> important from a MSP's point of view:
> Actually, the bootstrapping solution, in the split scenario, only
> propose a HA discovery mechanism (i.e. the MN receives a list of HA,
> from DNS, and chooses one of them). The MSP has no easy solution to
> enforce one MN to have a specific HA.

do you want an entity in the MSP to assign the HA
to the MN?

we can come up with some hacks to the HA discovery
mechanism to force the MN to pick a particular HA,
but I would rather avoid it. it would be better if
you tell us what the scenario and which are the
entities involved. then we can design a solution
for the specific scenario.

another option is to use HA Switch mechanism described
in http://www.ietf.org/internet-drafts/draft-ietf-mip6-ha-switch-00.txt

Vijay

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



From mip6-bounces@ietf.org Tue Jul 18 14:40:12 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G2uUM-0002LS-V4; Tue, 18 Jul 2006 14:40:10 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G2uUM-0002LN-Ep
	for mip6@ietf.org; Tue, 18 Jul 2006 14:40:10 -0400
Received: from key1.docomolabs-usa.com ([216.98.102.225]
	helo=fridge.docomolabs-usa.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G2uUL-0005Bb-0U
	for mip6@ietf.org; Tue, 18 Jul 2006 14:40:10 -0400
Message-ID: <02fc01c6aa99$de869d00$196115ac@dcml.docomolabsusa.com>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Alexandru Petrescu" <alexandru.petrescu@motorola.com>,
	"Jean-Michel Combes" <jeanmichel.combes@gmail.com>
References: <729b68be0607180431m773dc847qed3e7350819a8d04@mail.gmail.com>
	<44BD1105.5040904@motorola.com>
Subject: Re: [Mip6] New charter item: HA assignment
Date: Tue, 18 Jul 2006 11:42:06 -0700
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=response
Content-Transfer-Encoding: 7bit
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: 34d35111647d654d033d58d318c0d21a
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

So there are three ways I can think of that one could go about assigning an 
HA.

1) The MN uses the weights returned with the DNS SRV record from RFC 2782 to 
guide its selection of HAs. Less preferred HAs are later in the preference 
ordering. The authors of RFC 2782 complain about weights being a relatively 
coarse-grained mechanism that isn't up to providing dynamic load balancing. 
I think the time granularity of the SRV updates would  be about 15 seconds 
minimum, if dynamic DNS is used, since I'm told that is about the amount of 
time one should expect it to take for a dynamic DNS update to propagate.

2) For a more dynamic mechanism, the HA initially tried by the MN can turn 
down the MN's request to perform IKEv2. Or the HA could deny the MN an HoA. 
This would cause the MN to roll over to the next HA on the list. When the MN 
hit the right HA, the IKEv2 transaction would succeed. This has the 
disadvantage that it increases the amount of time the MN needs to bootstrap.

3) Immediately after the MN finishes the IKEv2 transaction, the first HA 
could send a HA Switch message (draft-ietf-mip6-ha-switch-00.txt) within the 
IPsec SA, telling the MN to go elsewhere. The MN would be delayed  by the 
amount of time needed to do the IKEv2 transaction, but that does provide 
security. This seems like it would be the most direct way.

I think a combination of these three mechanisms would be sufficient to 
provide HA assignment for the kinds of deployment scenerios that the split 
scenerio was designed to accommodate. The first mechanism would provide load 
balancing over longer periods while the second would provide support for 
fast transients, and the third would provide a way to directly and securely 
tell an MN where to go. Ideally, the MN wouldn't have to go through more 
than one additional HA before it got service, reducing the amount of lag.

On the other hand, if you want a way to say "thou shalt use this HA" without 
a lot of initial negotiation, then I'd suggest using the intergrated 
scenerio and simply let DHCP assign the MN to an HA (though that would 
require DHCP security).

If these are insufficient, then the only other suggestion is that an IKEv2 
INFORMATIONAL message be defined directing the MN to try IKEv2 with another 
node (which would be the preferred HA). Such a message could be used for VPN 
server load balancing too.

            jak






----- Original Message ----- 
From: "Alexandru Petrescu" <alexandru.petrescu@motorola.com>
To: "Jean-Michel Combes" <jeanmichel.combes@gmail.com>
Cc: "Mobile IPv6 Mailing List" <mip6@ietf.org>
Sent: Tuesday, July 18, 2006 9:49 AM
Subject: Re: [Mip6] New charter item: HA assignment


> Jean-Michel Combes wrote:
>> Hi,
>>
>> as promised during the mip6 session, here is a point which, IMO, is 
>> important from a MSP's point of view: Actually, the bootstrapping 
>> solution, in the split scenario, only propose a HA discovery mechanism 
>> (i.e. the MN receives a list of HA, from DNS, and chooses one of them). 
>> The MSP has no easy solution to enforce one MN to have a specific HA.
>
> One possible way is for a HA to stop sending BAck, at which point an MN
> would send DHAAD Request again, and a different HA replies back DHAAD,
> so end result is MN is assigned a new HA.
>
> Another way is for the new HA to send Binding Refresh Request to MN
> (even if it has no BC entry for it).
>
> Another way, if the split bootstrapping advances, is for the MSP to
> dynamically update the DNS data about HAs, so when MN bootstraps it
> obtains a different HA.
>
> If the HA address is discovered with DHCP then I think the DHCP Server
> can send specific messages to MN (unsolicited by MN).
>
> It would require relaxing some language in rfc 3775 and probably extending 
> BRR.
>
> It would be helpful to know when would an MSP like the MN to choose a
> different HA, for what reasons.
>
> Alex
>
>
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
> 



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



From mip6-bounces@ietf.org Tue Jul 18 14:41:33 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G2uVh-0002eE-Oe; Tue, 18 Jul 2006 14:41:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G2uVg-0002e9-Ai
	for mip6@ietf.org; Tue, 18 Jul 2006 14:41:32 -0400
Received: from key1.docomolabs-usa.com ([216.98.102.225]
	helo=fridge.docomolabs-usa.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G2uVf-0005LB-Ol
	for mip6@ietf.org; Tue, 18 Jul 2006 14:41:32 -0400
Message-ID: <030401c6aa9a$0ff8ffe0$196115ac@dcml.docomolabsusa.com>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
References: <7CCD07160348804497EF29E9EA5560D73C52AD@exchtewks2.starentnetworks.com>
Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
Date: Tue, 18 Jul 2006 11:43:29 -0700
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: 2a76bcd37b1c8a21336eb0a1ea6bbf48
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Kuntal,

The intent is not to introduce something that the MN would send during 
dormant mode. Indeed, as you have described, this would negatively impact 
battery life.

The intent is to provide a way for the MN to say that it is about to go into 
dormant mode, so please lengthen the IPsec SA timeout to avoid having it 
expire for some longer period of time.

            jak

----- Original Message ----- 
From: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
To: "James Kempf" <kempf@docomolabs-usa.com>
Cc: <mip6@ietf.org>
Sent: Tuesday, July 18, 2006 11:20 AM
Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?


James,

This is a good discussion. Indeed the need for IPsec keepalives (or DPD)
over the air when the MN is dormant (or idle) is an issue in the
cellular networks. The issue is Not that there are no mip6 messages
defined or the HA is not aware of dormancy. It is more of a paging
channel capacity issue, MN's battery life issue and the signaling
overhead to transport the keepalives for a dormant MN issue.

So, any new message however small won't solve the problem, IMHO.

-Kuntal


> -----Original Message-----
> From: James Kempf [mailto:kempf@docomolabs-usa.com]
> Sent: Tuesday, July 18, 2006 11:17 AM
> To: Vijay Devarapalli
> Cc: mip6@ietf.org
> Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert to
HA?
>
> For security, the message would need to be sent within an SA. There is
a
> question about which.
>
> One possibility is to do a Mobility Extension (call the messages
Sleeping
> and WakingUp) and send it within the IPsec SA between the HA and MN.
The
> MN
> sends the Sleeping message when it is about to go into dormant mode,
it
> sends the WakingUp message when it comes out again. The WakingUp
message
> isn't needed for the MN to get mobility service, it is just there for
> optimizing the SA timeouts. This would require a special API on the HA
> between the MIP code and IKE code for the HA to extend the IPsec SA
> lifetime, similar to the one for IKEv1 mobility. The solution would
only
> be
> applicable to Mobile IP.
>
> The other possibility is to do an IKEv2 INFORMATIONAL message that is
sent
> within the IKE SA. It works similarly, but there would be no need for
any
> API on the HA, since the IKE code itself would process it (actually, I
> proposed something like this to the Mobike WG but they didn't see the
need
> for it). This would be applicable to both Mobike and Mobile IP (and
any
> other security protocol that uses IKEv2, so maybe HIP as well).
>
> One question is, does the HA need to do anything else if the MN goes
into
> dormant mode? I think there are lots of things it could do (lengthen
the
> BU
> timeout, apply a filter that is either mobile specified or part of the
> user's service profile with the operator to only allow specific
traffic
> through, etc.) but I would really like to keep things simple.
>
>             jak
>
> ----- Original Message -----
> From: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
> To: "James Kempf" <kempf@docomolabs-usa.com>
> Cc: <mip6@ietf.org>
> Sent: Monday, July 17, 2006 3:43 PM
> Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert to
HA?
>
>
> > the dormant mode extensions sounds good to me. we could do
> > this extension. one issue to consider - what triggers this
> > message? how does Mobile IP know the mobile node is going
> > into a dormant mode. if we have the trigger we should be
> > okay.
> >
> > but we have to check if this was the issue. with IKEv1 you
> > could negotiate a lifetime for the IPsec SA. IKEv2 does not
> > have the IPsec SA lifetime feature. so keepalives are
> > needed.
> >
> > James Kempf wrote:
> >> I was at Wimax Forum last week and I think I now understand why
they
> and
> >> 3GPP2 want to use RFC 4285 auth option rather than IPsec. One issue
-
> >> lack of EAP support for client auth - is solved by IKEv2 and they
seem
> to
> >> now be moving in the direction of recommending IKEv2 if people want
to
> >> deploy IPsec.
> >
> > yes this was one of the main issues.
> >
> > the way I saw it folks in 3GPP2 liked RFC 4285 because it
> > is very similar to the MIPv4 mechanism and they were
> > comfortable with it.
> >
> > Vijay
> >
> > But the other issue is a bit more complex. 802.16, like
> >> most cellular protocols, has extensive support for dormant mode,
and
> >> Wimax Forum is supporting dormant mode in their network design. If
> IPsec
> >> is used, then there is a risk when a mobile node goes into dormant
mode
> >> that the IPsec SA may time out. It is unfortunate that this was not
> >> brought up when the discussion about RFC 4285 was happening, but I
> think
> >> this might be something that the WG could work on now as part of
the
> new
> >> charter. This would make IKEv2/IPsec more attractive as a security
> option
> >> for cellular operators.
> >>
> >> Comments?
> >>
> >>            jak
> >>
> >>
> >>
> >> _______________________________________________
> >> Mip6 mailing list
> >> Mip6@ietf.org
> >> https://www1.ietf.org/mailman/listinfo/mip6
> >
> >
>
>
>
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6


"This email message and any attachments are confidential information of 
Starent Networks, Corp. The information transmitted may not be used to 
create or change any contractual obligations of Starent Networks, Corp.  Any 
review, retransmission, dissemination or other use of, or taking of any 
action in reliance upon this e-mail and its attachments by persons or 
entities other than the intended recipient is prohibited. If you are not the 
intended recipient, please notify the sender immediately -- by replying to 
this message or by sending an email to postmaster@starentnetworks.com -- and 
destroy all copies of this message and any attachments without reading or 
disclosing their contents. Thank you."



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



From mip6-bounces@ietf.org Tue Jul 18 15:07:45 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G2uv0-0005Xe-MV; Tue, 18 Jul 2006 15:07:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G2uuz-0005XG-7l
	for mip6@ietf.org; Tue, 18 Jul 2006 15:07:41 -0400
Received: from mail1.azairenet.com ([66.92.223.4] helo=bart.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G2uuy-0000wa-QZ
	for mip6@ietf.org; Tue, 18 Jul 2006 15:07:41 -0400
Received: from [10.1.201.0] ([10.1.201.0]) by bart.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Tue, 18 Jul 2006 12:07:38 -0700
Message-ID: <44BD3119.5020000@azairenet.com>
Date: Tue, 18 Jul 2006 12:06:01 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Debian Thunderbird 1.0.2 (X11/20060423)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: James Kempf <kempf@docomolabs-usa.com>
Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
References: <040001c6a9ed$08e20010$196115ac@dcml.docomolabsusa.com>
	<44BC129E.7050901@azairenet.com>
	<01bc01c6aa85$a057f8d0$196115ac@dcml.docomolabsusa.com>
In-Reply-To: <01bc01c6aa85$a057f8d0$196115ac@dcml.docomolabsusa.com>
Content-Type: text/plain; charset=Windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 18 Jul 2006 19:07:38.0724 (UTC)
	FILETIME=[6FB33240:01C6AA9D]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 36c793b20164cfe75332aa66ddb21196
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

James Kempf wrote:
> For security, the message would need to be sent within an SA. There is a 
> question about which.

if it is going to be an extension to Mobile IPv6 messages, it
can only be sent within the IPsec SA that was created for
protecting the Mobile IPv6 messages. the MN somehow would need
to indicate to the HA that it wants the IKE SA also be kept
around while it goes dormant

> One possibility is to do a Mobility Extension (call the messages 
> Sleeping and WakingUp) and send it within the IPsec SA between the HA 
> and MN. The MN sends the Sleeping message when it is about to go into 
> dormant mode, it sends the WakingUp message when it comes out again. The 
> WakingUp message isn't needed for the MN to get mobility service, it is 
> just there for optimizing the SA timeouts. This would require a special 
> API on the HA between the MIP code and IKE code for the HA to extend the 
> IPsec SA lifetime, similar to the one for IKEv1 mobility. The solution 
> would only be applicable to Mobile IP.

you probably don't need a "Wakingup" message. just send some
data.

> The other possibility is to do an IKEv2 INFORMATIONAL message that is 
> sent within the IKE SA. It works similarly, but there would be no need 
> for any API on the HA, since the IKE code itself would process it 
> (actually, I proposed something like this to the Mobike WG but they 
> didn't see the need for it). This would be applicable to both Mobike and 
> Mobile IP (and any other security protocol that uses IKEv2, so maybe HIP 
> as well).

I think extending IKE would be better than doing this as a
Mobile IP extension. it is a generic problem of trying to keep
the IPsec SA (negotiated using IKEv2) alive when the MN wants
to go into a dormant mode. one problem is that there is no WG
to do this extension. it would have to be an individual
submission.

> One question is, does the HA need to do anything else if the MN goes 
> into dormant mode? I think there are lots of things it could do 
> (lengthen the BU timeout, apply a filter that is either mobile specified 
> or part of the user's service profile with the operator to only allow 
> specific traffic through, etc.) but I would really like to keep things 
> simple.

agree. lets just do a simple extension. :)

Vijay

> 
>            jak
> 
> ----- Original Message ----- From: "Vijay Devarapalli" 
> <vijay.devarapalli@azairenet.com>
> To: "James Kempf" <kempf@docomolabs-usa.com>
> Cc: <mip6@ietf.org>
> Sent: Monday, July 17, 2006 3:43 PM
> Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
> 
> 
>> the dormant mode extensions sounds good to me. we could do
>> this extension. one issue to consider - what triggers this
>> message? how does Mobile IP know the mobile node is going
>> into a dormant mode. if we have the trigger we should be
>> okay.
>>
>> but we have to check if this was the issue. with IKEv1 you
>> could negotiate a lifetime for the IPsec SA. IKEv2 does not
>> have the IPsec SA lifetime feature. so keepalives are
>> needed.
>>
>> James Kempf wrote:
>>
>>> I was at Wimax Forum last week and I think I now understand why they 
>>> and 3GPP2 want to use RFC 4285 auth option rather than IPsec. One 
>>> issue - lack of EAP support for client auth - is solved by IKEv2 and 
>>> they seem to now be moving in the direction of recommending IKEv2 if 
>>> people want to deploy IPsec.
>>
>>
>> yes this was one of the main issues.
>>
>> the way I saw it folks in 3GPP2 liked RFC 4285 because it
>> is very similar to the MIPv4 mechanism and they were
>> comfortable with it.
>>
>> Vijay
>>
>> But the other issue is a bit more complex. 802.16, like
>>
>>> most cellular protocols, has extensive support for dormant mode, and 
>>> Wimax Forum is supporting dormant mode in their network design. If 
>>> IPsec is used, then there is a risk when a mobile node goes into 
>>> dormant mode that the IPsec SA may time out. It is unfortunate that 
>>> this was not brought up when the discussion about RFC 4285 was 
>>> happening, but I think this might be something that the WG could work 
>>> on now as part of the new charter. This would make IKEv2/IPsec more 
>>> attractive as a security option for cellular operators.
>>>
>>> Comments?
>>>
>>>            jak
>>>
>>>
>>>
>>> _______________________________________________
>>> Mip6 mailing list
>>> Mip6@ietf.org
>>> https://www1.ietf.org/mailman/listinfo/mip6
>>
>>
>>
> 
> 


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



From mip6-bounces@ietf.org Tue Jul 18 15:15:52 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G2v2s-0006jV-KL; Tue, 18 Jul 2006 15:15:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G2v2r-0006jQ-Iq
	for mip6@ietf.org; Tue, 18 Jul 2006 15:15:49 -0400
Received: from mx0.starentnetworks.com ([12.38.223.203])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G2v2p-0001fH-2L
	for mip6@ietf.org; Tue, 18 Jul 2006 15:15:49 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mx0.starentnetworks.com (Postfix) with ESMTP id 78D0590027;
	Tue, 18 Jul 2006 15:15:43 -0400 (EDT)
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 14218-09; Tue, 18 Jul 2006 15:15:38 -0400 (EDT)
Received: from exchtewks1.starentnetworks.com (exchtewks1.starentnetworks.com
	[12.33.233.52]) by mx0.starentnetworks.com (Postfix) with ESMTP;
	Tue, 18 Jul 2006 15:15:38 -0400 (EDT)
X-MessageTextProcessor: DisclaimIt (2.70.271) [Starent Networks Corp.]
Received: from exchtewks2.starentnetworks.com ([12.33.232.12]) by
	exchtewks1.starentnetworks.com with Microsoft
	SMTPSVC(6.0.3790.1830); Tue, 18 Jul 2006 15:12:06 -0400
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
Date: Tue, 18 Jul 2006 15:12:06 -0400
Message-ID: <7CCD07160348804497EF29E9EA5560D73C52AF@exchtewks2.starentnetworks.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
thread-index: AcaqmVAhmNOXAD8ET9yK5OIIKnkM3AAAZFUA
From: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
To: "James Kempf" <kempf@docomolabs-usa.com>
Importance: normal
Priority: normal
X-OriginalArrivalTime: 18 Jul 2006 19:12:06.0888 (UTC)
	FILETIME=[0F89C680:01C6AA9E]
X-Virus-Scanned: amavisd-new 2.2.1 (20041222) at mx0.starentnetworks.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8a85b14f27c9dcbe0719e27d46abc1f8
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

James,

OK, I understand the intent (possible solution) better now. Besides
IPsec keepalives which happen periodically, there is Dead Peer Detection
(DPD) in use today. This gets triggered when the IPsec stack does not
detect any bearer traffic for a peer.  =20

So, there needs to be some additional hooks defined for the MIP6 stack
to manipulate IPsec keepalives and DPD.

-Kuntal


> -----Original Message-----
> From: James Kempf [mailto:kempf@docomolabs-usa.com]
> Sent: Tuesday, July 18, 2006 1:43 PM
> To: Chowdhury, Kuntal
> Cc: mip6@ietf.org
> Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert to
HA?
>=20
> Kuntal,
>=20
> The intent is not to introduce something that the MN would send during
> dormant mode. Indeed, as you have described, this would negatively
impact
> battery life.
>=20
> The intent is to provide a way for the MN to say that it is about to
go
> into
> dormant mode, so please lengthen the IPsec SA timeout to avoid having
it
> expire for some longer period of time.
>=20
>             jak
>=20
> ----- Original Message -----
> From: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
> To: "James Kempf" <kempf@docomolabs-usa.com>
> Cc: <mip6@ietf.org>
> Sent: Tuesday, July 18, 2006 11:20 AM
> Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode Alert to
HA?
>=20
>=20
> James,
>=20
> This is a good discussion. Indeed the need for IPsec keepalives (or
DPD)
> over the air when the MN is dormant (or idle) is an issue in the
> cellular networks. The issue is Not that there are no mip6 messages
> defined or the HA is not aware of dormancy. It is more of a paging
> channel capacity issue, MN's battery life issue and the signaling
> overhead to transport the keepalives for a dormant MN issue.
>=20
> So, any new message however small won't solve the problem, IMHO.
>=20
> -Kuntal
>=20
>=20
> > -----Original Message-----
> > From: James Kempf [mailto:kempf@docomolabs-usa.com]
> > Sent: Tuesday, July 18, 2006 11:17 AM
> > To: Vijay Devarapalli
> > Cc: mip6@ietf.org
> > Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert
to
> HA?
> >
> > For security, the message would need to be sent within an SA. There
is
> a
> > question about which.
> >
> > One possibility is to do a Mobility Extension (call the messages
> Sleeping
> > and WakingUp) and send it within the IPsec SA between the HA and MN.
> The
> > MN
> > sends the Sleeping message when it is about to go into dormant mode,
> it
> > sends the WakingUp message when it comes out again. The WakingUp
> message
> > isn't needed for the MN to get mobility service, it is just there
for
> > optimizing the SA timeouts. This would require a special API on the
HA
> > between the MIP code and IKE code for the HA to extend the IPsec SA
> > lifetime, similar to the one for IKEv1 mobility. The solution would
> only
> > be
> > applicable to Mobile IP.
> >
> > The other possibility is to do an IKEv2 INFORMATIONAL message that
is
> sent
> > within the IKE SA. It works similarly, but there would be no need
for
> any
> > API on the HA, since the IKE code itself would process it (actually,
I
> > proposed something like this to the Mobike WG but they didn't see
the
> need
> > for it). This would be applicable to both Mobike and Mobile IP (and
> any
> > other security protocol that uses IKEv2, so maybe HIP as well).
> >
> > One question is, does the HA need to do anything else if the MN goes
> into
> > dormant mode? I think there are lots of things it could do (lengthen
> the
> > BU
> > timeout, apply a filter that is either mobile specified or part of
the
> > user's service profile with the operator to only allow specific
> traffic
> > through, etc.) but I would really like to keep things simple.
> >
> >             jak
> >
> > ----- Original Message -----
> > From: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
> > To: "James Kempf" <kempf@docomolabs-usa.com>
> > Cc: <mip6@ietf.org>
> > Sent: Monday, July 17, 2006 3:43 PM
> > Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert
to
> HA?
> >
> >
> > > the dormant mode extensions sounds good to me. we could do
> > > this extension. one issue to consider - what triggers this
> > > message? how does Mobile IP know the mobile node is going
> > > into a dormant mode. if we have the trigger we should be
> > > okay.
> > >
> > > but we have to check if this was the issue. with IKEv1 you
> > > could negotiate a lifetime for the IPsec SA. IKEv2 does not
> > > have the IPsec SA lifetime feature. so keepalives are
> > > needed.
> > >
> > > James Kempf wrote:
> > >> I was at Wimax Forum last week and I think I now understand why
> they
> > and
> > >> 3GPP2 want to use RFC 4285 auth option rather than IPsec. One
issue
> -
> > >> lack of EAP support for client auth - is solved by IKEv2 and they
> seem
> > to
> > >> now be moving in the direction of recommending IKEv2 if people
want
> to
> > >> deploy IPsec.
> > >
> > > yes this was one of the main issues.
> > >
> > > the way I saw it folks in 3GPP2 liked RFC 4285 because it
> > > is very similar to the MIPv4 mechanism and they were
> > > comfortable with it.
> > >
> > > Vijay
> > >
> > > But the other issue is a bit more complex. 802.16, like
> > >> most cellular protocols, has extensive support for dormant mode,
> and
> > >> Wimax Forum is supporting dormant mode in their network design.
If
> > IPsec
> > >> is used, then there is a risk when a mobile node goes into
dormant
> mode
> > >> that the IPsec SA may time out. It is unfortunate that this was
not
> > >> brought up when the discussion about RFC 4285 was happening, but
I
> > think
> > >> this might be something that the WG could work on now as part of
> the
> > new
> > >> charter. This would make IKEv2/IPsec more attractive as a
security
> > option
> > >> for cellular operators.
> > >>
> > >> Comments?
> > >>
> > >>            jak
> > >>
> > >>
> > >>
> > >> _______________________________________________
> > >> Mip6 mailing list
> > >> Mip6@ietf.org
> > >> https://www1.ietf.org/mailman/listinfo/mip6
> > >
> > >
> >
> >
> >
> > _______________________________________________
> > Mip6 mailing list
> > Mip6@ietf.org
> > https://www1.ietf.org/mailman/listinfo/mip6
>=20
>=20
> "This email message and any attachments are confidential information
of
> Starent Networks, Corp. The information transmitted may not be used to
> create or change any contractual obligations of Starent Networks,
Corp.
> Any
> review, retransmission, dissemination or other use of, or taking of
any
> action in reliance upon this e-mail and its attachments by persons or
> entities other than the intended recipient is prohibited. If you are
not
> the
> intended recipient, please notify the sender immediately -- by
replying to
> this message or by sending an email to postmaster@starentnetworks.com
--
> and
> destroy all copies of this message and any attachments without reading
or
> disclosing their contents. Thank you."
>=20


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



From mip6-bounces@ietf.org Tue Jul 18 15:31:29 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G2vHz-0001kj-Hr; Tue, 18 Jul 2006 15:31:27 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G2vHz-0001ke-21
	for mip6@ietf.org; Tue, 18 Jul 2006 15:31:27 -0400
Received: from motgate4.mot.com ([144.189.100.102])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G2vHx-00030M-Ml
	for mip6@ietf.org; Tue, 18 Jul 2006 15:31:27 -0400
Received: from az33exr04.mot.com (az33exr04.mot.com [10.64.251.234])
	by motgate4.mot.com (8.12.11/Motorola) with ESMTP id k6IJVEoG006349;
	Tue, 18 Jul 2006 12:31:14 -0700 (MST)
Received: from [10.193.154.111] ([10.193.154.111])
	by az33exr04.mot.com (8.13.1/8.13.0) with ESMTP id k6IJV7CK010742;
	Tue, 18 Jul 2006 14:31:09 -0500 (CDT)
Message-ID: <44BD36F9.3020400@motorola.com>
Date: Tue, 18 Jul 2006 21:31:05 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: James Kempf <kempf@docomolabs-usa.com>
Subject: Re: [Mip6] New charter item: HA assignment
References: <729b68be0607180431m773dc847qed3e7350819a8d04@mail.gmail.com>
	<44BD1105.5040904@motorola.com>
	<02fc01c6aa99$de869d00$196115ac@dcml.docomolabsusa.com>
In-Reply-To: <02fc01c6aa99$de869d00$196115ac@dcml.docomolabsusa.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAQAAAAQ=
X-White-List-Member: TRUE
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

James Kempf wrote:
> So there are three ways I can think of that one could go about 
> assigning an HA.
> 
> 1) The MN uses the weights returned with the DNS SRV record from RFC 
> 2782 to guide its selection of HAs. Less preferred HAs are later in 
> the preference ordering. The authors of RFC 2782 complain about 
> weights being a relatively coarse-grained mechanism that isn't up to 
> providing dynamic load balancing. I think the time granularity of the
>  SRV updates would  be about 15 seconds minimum, if dynamic DNS is 
> used, since I'm told that is about the amount of time one should 
> expect it to take for a dynamic DNS update to propagate.

I agree that 15 seconds is more on the lower boundary...  On Internet it
can take days.

Within one operator's network it could be much lower though.

> 2) For a more dynamic mechanism, the HA initially tried by the MN can
>  turn down the MN's request to perform IKEv2. Or the HA could deny 
> the MN an HoA. This would cause the MN to roll over to the next HA on
>  the list. When the MN hit the right HA, the IKEv2 transaction would 
> succeed. This has the disadvantage that it increases the amount of 
> time the MN needs to bootstrap.
> 
> 3) Immediately after the MN finishes the IKEv2 transaction, the first
>  HA could send a HA Switch message (draft-ietf-mip6-ha-switch-00.txt)
>  within the IPsec SA, telling the MN to go elsewhere. The MN would be
>  delayed by the amount of time needed to do the IKEv2 transaction,
> but that does provide security. This seems like it would be the most 
> direct way.

What if the HA Switch message gets lost?  That's not a TCP message I
suppose.  I haven't read the HA switch draft in detail... is there
retransmission of it?  Is it needed?

Alex

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



From mip6-bounces@ietf.org Tue Jul 18 15:34:36 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G2vL2-0002Df-Hp; Tue, 18 Jul 2006 15:34:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G2vL0-0002Da-Rf
	for mip6@ietf.org; Tue, 18 Jul 2006 15:34:34 -0400
Received: from key1.docomolabs-usa.com ([216.98.102.225]
	helo=fridge.docomolabs-usa.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G2vL0-0003Ax-7o
	for mip6@ietf.org; Tue, 18 Jul 2006 15:34:34 -0400
Message-ID: <033201c6aaa1$787be580$196115ac@dcml.docomolabsusa.com>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Tsirtsis, George" <tsirtsis@qualcomm.com>,
	"Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
References: <7EB20EA0938B4D42A2D82689365C9B7A0CBDE3@NAEX14.na.qualcomm.com>
Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
Date: Tue, 18 Jul 2006 12:36:31 -0700
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: dd7e0c3fd18d19cffdd4de99a114001d
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

I don't know. What do operators typically set the SA lifetime to? Though 
perhaps this is an unanswerable question because, as yet, has anybody 
deployed MIPv6?

My only observation is that this seems to be an issue with Wimax Forum, and 
one of the primary motivators for wanting to use the RFC 4285 Auth Option. 
If IETF and the MIP6 WG would like to encourage them to use IKE (as seemed 
to be the sentiment when RFC 4285 was discussed, and one of the reasons why 
it is not PS), it might be worthwhile to try to address their concerns.

            jak

----- Original Message ----- 
From: "Tsirtsis, George" <tsirtsis@qualcomm.com>
To: "James Kempf" <kempf@docomolabs-usa.com>; "Chowdhury, Kuntal" 
<kchowdhury@starentnetworks.com>
Cc: <mip6@ietf.org>
Sent: Tuesday, July 18, 2006 12:10 PM
Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?


May I ask, what is the typical lifetime of the SA and what would you
lengthen it to?
George

> -----Original Message-----
> From: James Kempf [mailto:kempf@docomolabs-usa.com]
> Sent: Tuesday, July 18, 2006 2:43 PM
> To: Chowdhury, Kuntal
> Cc: mip6@ietf.org
> Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert to
HA?
>
> Kuntal,
>
> The intent is not to introduce something that the MN would send during
> dormant mode. Indeed, as you have described, this would negatively
impact
> battery life.
>
> The intent is to provide a way for the MN to say that it is about to
go
> into
> dormant mode, so please lengthen the IPsec SA timeout to avoid having
it
> expire for some longer period of time.
>
>             jak
>
> ----- Original Message -----
> From: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
> To: "James Kempf" <kempf@docomolabs-usa.com>
> Cc: <mip6@ietf.org>
> Sent: Tuesday, July 18, 2006 11:20 AM
> Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode Alert to
HA?
>
>
> James,
>
> This is a good discussion. Indeed the need for IPsec keepalives (or
DPD)
> over the air when the MN is dormant (or idle) is an issue in the
> cellular networks. The issue is Not that there are no mip6 messages
> defined or the HA is not aware of dormancy. It is more of a paging
> channel capacity issue, MN's battery life issue and the signaling
> overhead to transport the keepalives for a dormant MN issue.
>
> So, any new message however small won't solve the problem, IMHO.
>
> -Kuntal
>
>
> > -----Original Message-----
> > From: James Kempf [mailto:kempf@docomolabs-usa.com]
> > Sent: Tuesday, July 18, 2006 11:17 AM
> > To: Vijay Devarapalli
> > Cc: mip6@ietf.org
> > Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert
to
> HA?
> >
> > For security, the message would need to be sent within an SA. There
is
> a
> > question about which.
> >
> > One possibility is to do a Mobility Extension (call the messages
> Sleeping
> > and WakingUp) and send it within the IPsec SA between the HA and MN.
> The
> > MN
> > sends the Sleeping message when it is about to go into dormant mode,
> it
> > sends the WakingUp message when it comes out again. The WakingUp
> message
> > isn't needed for the MN to get mobility service, it is just there
for
> > optimizing the SA timeouts. This would require a special API on the
HA
> > between the MIP code and IKE code for the HA to extend the IPsec SA
> > lifetime, similar to the one for IKEv1 mobility. The solution would
> only
> > be
> > applicable to Mobile IP.
> >
> > The other possibility is to do an IKEv2 INFORMATIONAL message that
is
> sent
> > within the IKE SA. It works similarly, but there would be no need
for
> any
> > API on the HA, since the IKE code itself would process it (actually,
I
> > proposed something like this to the Mobike WG but they didn't see
the
> need
> > for it). This would be applicable to both Mobike and Mobile IP (and
> any
> > other security protocol that uses IKEv2, so maybe HIP as well).
> >
> > One question is, does the HA need to do anything else if the MN goes
> into
> > dormant mode? I think there are lots of things it could do (lengthen
> the
> > BU
> > timeout, apply a filter that is either mobile specified or part of
the
> > user's service profile with the operator to only allow specific
> traffic
> > through, etc.) but I would really like to keep things simple.
> >
> >             jak
> >
> > ----- Original Message -----
> > From: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
> > To: "James Kempf" <kempf@docomolabs-usa.com>
> > Cc: <mip6@ietf.org>
> > Sent: Monday, July 17, 2006 3:43 PM
> > Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert
to
> HA?
> >
> >
> > > the dormant mode extensions sounds good to me. we could do
> > > this extension. one issue to consider - what triggers this
> > > message? how does Mobile IP know the mobile node is going
> > > into a dormant mode. if we have the trigger we should be
> > > okay.
> > >
> > > but we have to check if this was the issue. with IKEv1 you
> > > could negotiate a lifetime for the IPsec SA. IKEv2 does not
> > > have the IPsec SA lifetime feature. so keepalives are
> > > needed.
> > >
> > > James Kempf wrote:
> > >> I was at Wimax Forum last week and I think I now understand why
> they
> > and
> > >> 3GPP2 want to use RFC 4285 auth option rather than IPsec. One
issue
> -
> > >> lack of EAP support for client auth - is solved by IKEv2 and they
> seem
> > to
> > >> now be moving in the direction of recommending IKEv2 if people
want
> to
> > >> deploy IPsec.
> > >
> > > yes this was one of the main issues.
> > >
> > > the way I saw it folks in 3GPP2 liked RFC 4285 because it
> > > is very similar to the MIPv4 mechanism and they were
> > > comfortable with it.
> > >
> > > Vijay
> > >
> > > But the other issue is a bit more complex. 802.16, like
> > >> most cellular protocols, has extensive support for dormant mode,
> and
> > >> Wimax Forum is supporting dormant mode in their network design.
If
> > IPsec
> > >> is used, then there is a risk when a mobile node goes into
dormant
> mode
> > >> that the IPsec SA may time out. It is unfortunate that this was
not
> > >> brought up when the discussion about RFC 4285 was happening, but
I
> > think
> > >> this might be something that the WG could work on now as part of
> the
> > new
> > >> charter. This would make IKEv2/IPsec more attractive as a
security
> > option
> > >> for cellular operators.
> > >>
> > >> Comments?
> > >>
> > >>            jak
> > >>
> > >>
> > >>
> > >> _______________________________________________
> > >> Mip6 mailing list
> > >> Mip6@ietf.org
> > >> https://www1.ietf.org/mailman/listinfo/mip6
> > >
> > >
> >
> >
> >
> > _______________________________________________
> > Mip6 mailing list
> > Mip6@ietf.org
> > https://www1.ietf.org/mailman/listinfo/mip6
>
>
> "This email message and any attachments are confidential information
of
> Starent Networks, Corp. The information transmitted may not be used to
> create or change any contractual obligations of Starent Networks,
Corp.
> Any
> review, retransmission, dissemination or other use of, or taking of
any
> action in reliance upon this e-mail and its attachments by persons or
> entities other than the intended recipient is prohibited. If you are
not
> the
> intended recipient, please notify the sender immediately -- by
replying to
> this message or by sending an email to postmaster@starentnetworks.com
--

> and
> destroy all copies of this message and any attachments without reading
or
> disclosing their contents. Thank you."
>
>
>
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6



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



From mip6-bounces@ietf.org Tue Jul 18 15:36:25 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G2vMn-0002hJ-SB; Tue, 18 Jul 2006 15:36:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G2vMm-0002hE-A4
	for mip6@ietf.org; Tue, 18 Jul 2006 15:36:24 -0400
Received: from key1.docomolabs-usa.com ([216.98.102.225]
	helo=fridge.docomolabs-usa.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G2vMk-0003Nm-Tl
	for mip6@ietf.org; Tue, 18 Jul 2006 15:36:24 -0400
Message-ID: <033b01c6aaa1$b935b880$196115ac@dcml.docomolabsusa.com>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Alexandru Petrescu" <alexandru.petrescu@motorola.com>
References: <729b68be0607180431m773dc847qed3e7350819a8d04@mail.gmail.com>
	<44BD1105.5040904@motorola.com>
	<02fc01c6aa99$de869d00$196115ac@dcml.docomolabsusa.com>
	<44BD36F9.3020400@motorola.com>
Subject: Re: [Mip6] New charter item: HA assignment
Date: Tue, 18 Jul 2006 12:38:19 -0700
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=response
Content-Transfer-Encoding: 7bit
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

>> 3) Immediately after the MN finishes the IKEv2 transaction, the first
>>  HA could send a HA Switch message (draft-ietf-mip6-ha-switch-00.txt)
>>  within the IPsec SA, telling the MN to go elsewhere. The MN would be
>>  delayed by the amount of time needed to do the IKEv2 transaction,
>> but that does provide security. This seems like it would be the most 
>> direct way.
>
> What if the HA Switch message gets lost?  That's not a TCP message I
> suppose.  I haven't read the HA switch draft in detail... is there
> retransmission of it?  Is it needed?
>

Like any MIP message, it doesn't use reliable transport. Perhaps we need to 
define retransmission, or require retransmission as defined by RFC 3775.

            jak 



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



From mip6-bounces@ietf.org Tue Jul 18 15:38:48 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G2vP5-0003Q7-BH; Tue, 18 Jul 2006 15:38:47 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G2vP4-0003Px-28
	for mip6@ietf.org; Tue, 18 Jul 2006 15:38:46 -0400
Received: from warlock.qualcomm.com ([129.46.50.49])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G2vP2-0003cm-G2
	for mip6@ietf.org; Tue, 18 Jul 2006 15:38:46 -0400
Received: from numenor.qualcomm.com (numenor.qualcomm.com [129.46.51.58])
	by warlock.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k6IJBgHM019517
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL)
	for <mip6@ietf.org>; Tue, 18 Jul 2006 12:11:44 -0700 (PDT)
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
	k6IJB18b012967
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Tue, 18 Jul 2006 12:11:03 -0700
Received: from NAEXBR03.na.qualcomm.com (naexbr03.qualcomm.com
	[129.46.134.172])
	by magus.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id k6IJ9vF0005279; 
	Tue, 18 Jul 2006 12:10:59 -0700 (PDT)
Received: from NAEX14.na.qualcomm.com ([10.47.5.242]) by
	NAEXBR03.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 18 Jul 2006 12:10:58 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
Date: Tue, 18 Jul 2006 12:10:56 -0700
Message-ID: <7EB20EA0938B4D42A2D82689365C9B7A0CBDE3@NAEX14.na.qualcomm.com>
In-Reply-To: <030401c6aa9a$0ff8ffe0$196115ac@dcml.docomolabsusa.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
Thread-Index: AcaqnEBLTx1XX4XLTXKxGnqpsIOacAAAXBiw
From: "Tsirtsis, George" <tsirtsis@qualcomm.com>
To: "James Kempf" <kempf@docomolabs-usa.com>,
	"Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
X-OriginalArrivalTime: 18 Jul 2006 19:10:58.0041 (UTC)
	FILETIME=[E6808E90:01C6AA9D]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a4a24b484706be629f915bfb1a3e4771
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

May I ask, what is the typical lifetime of the SA and what would you
lengthen it to?
George=20

> -----Original Message-----
> From: James Kempf [mailto:kempf@docomolabs-usa.com]
> Sent: Tuesday, July 18, 2006 2:43 PM
> To: Chowdhury, Kuntal
> Cc: mip6@ietf.org
> Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert to
HA?
>=20
> Kuntal,
>=20
> The intent is not to introduce something that the MN would send during
> dormant mode. Indeed, as you have described, this would negatively
impact
> battery life.
>=20
> The intent is to provide a way for the MN to say that it is about to
go
> into
> dormant mode, so please lengthen the IPsec SA timeout to avoid having
it
> expire for some longer period of time.
>=20
>             jak
>=20
> ----- Original Message -----
> From: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
> To: "James Kempf" <kempf@docomolabs-usa.com>
> Cc: <mip6@ietf.org>
> Sent: Tuesday, July 18, 2006 11:20 AM
> Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode Alert to
HA?
>=20
>=20
> James,
>=20
> This is a good discussion. Indeed the need for IPsec keepalives (or
DPD)
> over the air when the MN is dormant (or idle) is an issue in the
> cellular networks. The issue is Not that there are no mip6 messages
> defined or the HA is not aware of dormancy. It is more of a paging
> channel capacity issue, MN's battery life issue and the signaling
> overhead to transport the keepalives for a dormant MN issue.
>=20
> So, any new message however small won't solve the problem, IMHO.
>=20
> -Kuntal
>=20
>=20
> > -----Original Message-----
> > From: James Kempf [mailto:kempf@docomolabs-usa.com]
> > Sent: Tuesday, July 18, 2006 11:17 AM
> > To: Vijay Devarapalli
> > Cc: mip6@ietf.org
> > Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert
to
> HA?
> >
> > For security, the message would need to be sent within an SA. There
is
> a
> > question about which.
> >
> > One possibility is to do a Mobility Extension (call the messages
> Sleeping
> > and WakingUp) and send it within the IPsec SA between the HA and MN.
> The
> > MN
> > sends the Sleeping message when it is about to go into dormant mode,
> it
> > sends the WakingUp message when it comes out again. The WakingUp
> message
> > isn't needed for the MN to get mobility service, it is just there
for
> > optimizing the SA timeouts. This would require a special API on the
HA
> > between the MIP code and IKE code for the HA to extend the IPsec SA
> > lifetime, similar to the one for IKEv1 mobility. The solution would
> only
> > be
> > applicable to Mobile IP.
> >
> > The other possibility is to do an IKEv2 INFORMATIONAL message that
is
> sent
> > within the IKE SA. It works similarly, but there would be no need
for
> any
> > API on the HA, since the IKE code itself would process it (actually,
I
> > proposed something like this to the Mobike WG but they didn't see
the
> need
> > for it). This would be applicable to both Mobike and Mobile IP (and
> any
> > other security protocol that uses IKEv2, so maybe HIP as well).
> >
> > One question is, does the HA need to do anything else if the MN goes
> into
> > dormant mode? I think there are lots of things it could do (lengthen
> the
> > BU
> > timeout, apply a filter that is either mobile specified or part of
the
> > user's service profile with the operator to only allow specific
> traffic
> > through, etc.) but I would really like to keep things simple.
> >
> >             jak
> >
> > ----- Original Message -----
> > From: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
> > To: "James Kempf" <kempf@docomolabs-usa.com>
> > Cc: <mip6@ietf.org>
> > Sent: Monday, July 17, 2006 3:43 PM
> > Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert
to
> HA?
> >
> >
> > > the dormant mode extensions sounds good to me. we could do
> > > this extension. one issue to consider - what triggers this
> > > message? how does Mobile IP know the mobile node is going
> > > into a dormant mode. if we have the trigger we should be
> > > okay.
> > >
> > > but we have to check if this was the issue. with IKEv1 you
> > > could negotiate a lifetime for the IPsec SA. IKEv2 does not
> > > have the IPsec SA lifetime feature. so keepalives are
> > > needed.
> > >
> > > James Kempf wrote:
> > >> I was at Wimax Forum last week and I think I now understand why
> they
> > and
> > >> 3GPP2 want to use RFC 4285 auth option rather than IPsec. One
issue
> -
> > >> lack of EAP support for client auth - is solved by IKEv2 and they
> seem
> > to
> > >> now be moving in the direction of recommending IKEv2 if people
want
> to
> > >> deploy IPsec.
> > >
> > > yes this was one of the main issues.
> > >
> > > the way I saw it folks in 3GPP2 liked RFC 4285 because it
> > > is very similar to the MIPv4 mechanism and they were
> > > comfortable with it.
> > >
> > > Vijay
> > >
> > > But the other issue is a bit more complex. 802.16, like
> > >> most cellular protocols, has extensive support for dormant mode,
> and
> > >> Wimax Forum is supporting dormant mode in their network design.
If
> > IPsec
> > >> is used, then there is a risk when a mobile node goes into
dormant
> mode
> > >> that the IPsec SA may time out. It is unfortunate that this was
not
> > >> brought up when the discussion about RFC 4285 was happening, but
I
> > think
> > >> this might be something that the WG could work on now as part of
> the
> > new
> > >> charter. This would make IKEv2/IPsec more attractive as a
security
> > option
> > >> for cellular operators.
> > >>
> > >> Comments?
> > >>
> > >>            jak
> > >>
> > >>
> > >>
> > >> _______________________________________________
> > >> Mip6 mailing list
> > >> Mip6@ietf.org
> > >> https://www1.ietf.org/mailman/listinfo/mip6
> > >
> > >
> >
> >
> >
> > _______________________________________________
> > Mip6 mailing list
> > Mip6@ietf.org
> > https://www1.ietf.org/mailman/listinfo/mip6
>=20
>=20
> "This email message and any attachments are confidential information
of
> Starent Networks, Corp. The information transmitted may not be used to
> create or change any contractual obligations of Starent Networks,
Corp.
> Any
> review, retransmission, dissemination or other use of, or taking of
any
> action in reliance upon this e-mail and its attachments by persons or
> entities other than the intended recipient is prohibited. If you are
not
> the
> intended recipient, please notify the sender immediately -- by
replying to
> this message or by sending an email to postmaster@starentnetworks.com
--
> and
> destroy all copies of this message and any attachments without reading
or
> disclosing their contents. Thank you."
>=20
>=20
>=20
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6

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



From mip6-bounces@ietf.org Tue Jul 18 15:46:52 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G2vWt-0006PB-Gc; Tue, 18 Jul 2006 15:46:51 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G2vWs-0006P6-Cu
	for mip6@ietf.org; Tue, 18 Jul 2006 15:46:50 -0400
Received: from atlrel7.hp.com ([156.153.255.213])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G2vWr-0005Kk-4B
	for mip6@ietf.org; Tue, 18 Jul 2006 15:46:50 -0400
Received: from smtp2.fc.hp.com (smtp.fc.hp.com [15.11.136.114])
	by atlrel7.hp.com (Postfix) with ESMTP id 67D6237095;
	Tue, 18 Jul 2006 15:46:48 -0400 (EDT)
Received: from [16.116.96.215] (spaceshipone.zko.hp.com [16.116.96.215])
	by smtp2.fc.hp.com (Postfix) with ESMTP id A21EF514AC;
	Tue, 18 Jul 2006 19:46:47 +0000 (UTC)
Message-ID: <44BD3AA6.7070906@hp.com>
Date: Tue, 18 Jul 2006 15:46:46 -0400
From: Brian Haley <brian.haley@hp.com>
Organization: Open Source and Linux Organization
User-Agent: Thunderbird 1.5.0.4 (X11/20060615)
MIME-Version: 1.0
To: Alexandru Petrescu <alexandru.petrescu@motorola.com>
Subject: Re: [Mip6] New charter item: HA assignment
References: <729b68be0607180431m773dc847qed3e7350819a8d04@mail.gmail.com>
	<44BD1105.5040904@motorola.com>
In-Reply-To: <44BD1105.5040904@motorola.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Didn't want to hijack the thread, but wanted to respond to Alex's 
comment below.

Alexandru Petrescu wrote:
> Jean-Michel Combes wrote:
>> Hi,
>>
>> as promised during the mip6 session, here is a point which, IMO, is 
>> important from a MSP's point of view: Actually, the bootstrapping 
>> solution, in the split scenario, only propose a HA discovery mechanism 
>> (i.e. the MN receives a list of HA, from DNS, and chooses one of 
>> them). The MSP has no easy solution to enforce one MN to have a 
>> specific HA.
> 
> One possible way is for a HA to stop sending BAck, at which point an MN
> would send DHAAD Request again, and a different HA replies back DHAAD,
> so end result is MN is assigned a new HA.
> 
> Another way is for the new HA to send Binding Refresh Request to MN
> (even if it has no BC entry for it).

BRR is sent from CN to MN, it is not defined to be sent from HA.  I know 
you brought-up extending it at the WG meeting (instead of using HA 
switch), but I couldn't remember all the reasons we didn't do that. 
IPsec is the other problem since the message has no protection, but 
needs it.

-Brian

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



From mip6-bounces@ietf.org Tue Jul 18 15:50:25 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G2vaL-0003uh-81; Tue, 18 Jul 2006 15:50:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G2vaJ-0003sZ-VA
	for mip6@ietf.org; Tue, 18 Jul 2006 15:50:23 -0400
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G2vaJ-0006w9-CL
	for mip6@ietf.org; Tue, 18 Jul 2006 15:50:23 -0400
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
	k6IJoKEt018547
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Tue, 18 Jul 2006 12:50:21 -0700
Received: from NAEXBR02.na.qualcomm.com (naexbr02.qualcomm.com [10.46.92.109])
	by neophyte.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	k6IJlxJK027799; Tue, 18 Jul 2006 12:50:19 -0700 (PDT)
Received: from NAEX14.na.qualcomm.com ([10.47.5.242]) by
	NAEXBR02.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 18 Jul 2006 12:49:13 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
Date: Tue, 18 Jul 2006 12:49:12 -0700
Message-ID: <7EB20EA0938B4D42A2D82689365C9B7A0CBDEE@NAEX14.na.qualcomm.com>
In-Reply-To: <033201c6aaa1$787be580$196115ac@dcml.docomolabsusa.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
Thread-Index: AcaqoT0oJd81saAuThGdaMylszp3AwAAc5kA
From: "Tsirtsis, George" <tsirtsis@qualcomm.com>
To: "James Kempf" <kempf@docomolabs-usa.com>,
	"Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
X-OriginalArrivalTime: 18 Jul 2006 19:49:13.0078 (UTC)
	FILETIME=[3E736960:01C6AAA3]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 24d000849df6f171c5ec1cca2ea21b82
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

I guess the important thing is to understand how the typical SA lifetime
relates to the typical MIP6 Binding Lifetime. The MN will have to at
least wake up to refresh its binding.

George

> -----Original Message-----
> From: James Kempf [mailto:kempf@docomolabs-usa.com]
> Sent: Tuesday, July 18, 2006 3:37 PM
> To: Tsirtsis, George; Chowdhury, Kuntal
> Cc: mip6@ietf.org
> Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert to
HA?
>=20
> I don't know. What do operators typically set the SA lifetime to?
Though
> perhaps this is an unanswerable question because, as yet, has anybody
> deployed MIPv6?
>=20
> My only observation is that this seems to be an issue with Wimax
Forum,
> and
> one of the primary motivators for wanting to use the RFC 4285 Auth
Option.
> If IETF and the MIP6 WG would like to encourage them to use IKE (as
seemed
> to be the sentiment when RFC 4285 was discussed, and one of the
reasons
> why
> it is not PS), it might be worthwhile to try to address their
concerns.
>=20
>             jak
>=20
> ----- Original Message -----
> From: "Tsirtsis, George" <tsirtsis@qualcomm.com>
> To: "James Kempf" <kempf@docomolabs-usa.com>; "Chowdhury, Kuntal"
> <kchowdhury@starentnetworks.com>
> Cc: <mip6@ietf.org>
> Sent: Tuesday, July 18, 2006 12:10 PM
> Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode Alert to
HA?
>=20
>=20
> May I ask, what is the typical lifetime of the SA and what would you
> lengthen it to?
> George
>=20
> > -----Original Message-----
> > From: James Kempf [mailto:kempf@docomolabs-usa.com]
> > Sent: Tuesday, July 18, 2006 2:43 PM
> > To: Chowdhury, Kuntal
> > Cc: mip6@ietf.org
> > Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert
to
> HA?
> >
> > Kuntal,
> >
> > The intent is not to introduce something that the MN would send
during
> > dormant mode. Indeed, as you have described, this would negatively
> impact
> > battery life.
> >
> > The intent is to provide a way for the MN to say that it is about to
> go
> > into
> > dormant mode, so please lengthen the IPsec SA timeout to avoid
having
> it
> > expire for some longer period of time.
> >
> >             jak
> >
> > ----- Original Message -----
> > From: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
> > To: "James Kempf" <kempf@docomolabs-usa.com>
> > Cc: <mip6@ietf.org>
> > Sent: Tuesday, July 18, 2006 11:20 AM
> > Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode Alert
to
> HA?
> >
> >
> > James,
> >
> > This is a good discussion. Indeed the need for IPsec keepalives (or
> DPD)
> > over the air when the MN is dormant (or idle) is an issue in the
> > cellular networks. The issue is Not that there are no mip6 messages
> > defined or the HA is not aware of dormancy. It is more of a paging
> > channel capacity issue, MN's battery life issue and the signaling
> > overhead to transport the keepalives for a dormant MN issue.
> >
> > So, any new message however small won't solve the problem, IMHO.
> >
> > -Kuntal
> >
> >
> > > -----Original Message-----
> > > From: James Kempf [mailto:kempf@docomolabs-usa.com]
> > > Sent: Tuesday, July 18, 2006 11:17 AM
> > > To: Vijay Devarapalli
> > > Cc: mip6@ietf.org
> > > Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode
Alert
> to
> > HA?
> > >
> > > For security, the message would need to be sent within an SA.
There
> is
> > a
> > > question about which.
> > >
> > > One possibility is to do a Mobility Extension (call the messages
> > Sleeping
> > > and WakingUp) and send it within the IPsec SA between the HA and
MN.
> > The
> > > MN
> > > sends the Sleeping message when it is about to go into dormant
mode,
> > it
> > > sends the WakingUp message when it comes out again. The WakingUp
> > message
> > > isn't needed for the MN to get mobility service, it is just there
> for
> > > optimizing the SA timeouts. This would require a special API on
the
> HA
> > > between the MIP code and IKE code for the HA to extend the IPsec
SA
> > > lifetime, similar to the one for IKEv1 mobility. The solution
would
> > only
> > > be
> > > applicable to Mobile IP.
> > >
> > > The other possibility is to do an IKEv2 INFORMATIONAL message that
> is
> > sent
> > > within the IKE SA. It works similarly, but there would be no need
> for
> > any
> > > API on the HA, since the IKE code itself would process it
(actually,
> I
> > > proposed something like this to the Mobike WG but they didn't see
> the
> > need
> > > for it). This would be applicable to both Mobike and Mobile IP
(and
> > any
> > > other security protocol that uses IKEv2, so maybe HIP as well).
> > >
> > > One question is, does the HA need to do anything else if the MN
goes
> > into
> > > dormant mode? I think there are lots of things it could do
(lengthen
> > the
> > > BU
> > > timeout, apply a filter that is either mobile specified or part of
> the
> > > user's service profile with the operator to only allow specific
> > traffic
> > > through, etc.) but I would really like to keep things simple.
> > >
> > >             jak
> > >
> > > ----- Original Message -----
> > > From: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
> > > To: "James Kempf" <kempf@docomolabs-usa.com>
> > > Cc: <mip6@ietf.org>
> > > Sent: Monday, July 17, 2006 3:43 PM
> > > Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode
Alert
> to
> > HA?
> > >
> > >
> > > > the dormant mode extensions sounds good to me. we could do
> > > > this extension. one issue to consider - what triggers this
> > > > message? how does Mobile IP know the mobile node is going
> > > > into a dormant mode. if we have the trigger we should be
> > > > okay.
> > > >
> > > > but we have to check if this was the issue. with IKEv1 you
> > > > could negotiate a lifetime for the IPsec SA. IKEv2 does not
> > > > have the IPsec SA lifetime feature. so keepalives are
> > > > needed.
> > > >
> > > > James Kempf wrote:
> > > >> I was at Wimax Forum last week and I think I now understand why
> > they
> > > and
> > > >> 3GPP2 want to use RFC 4285 auth option rather than IPsec. One
> issue
> > -
> > > >> lack of EAP support for client auth - is solved by IKEv2 and
they
> > seem
> > > to
> > > >> now be moving in the direction of recommending IKEv2 if people
> want
> > to
> > > >> deploy IPsec.
> > > >
> > > > yes this was one of the main issues.
> > > >
> > > > the way I saw it folks in 3GPP2 liked RFC 4285 because it
> > > > is very similar to the MIPv4 mechanism and they were
> > > > comfortable with it.
> > > >
> > > > Vijay
> > > >
> > > > But the other issue is a bit more complex. 802.16, like
> > > >> most cellular protocols, has extensive support for dormant
mode,
> > and
> > > >> Wimax Forum is supporting dormant mode in their network design.
> If
> > > IPsec
> > > >> is used, then there is a risk when a mobile node goes into
> dormant
> > mode
> > > >> that the IPsec SA may time out. It is unfortunate that this was
> not
> > > >> brought up when the discussion about RFC 4285 was happening,
but
> I
> > > think
> > > >> this might be something that the WG could work on now as part
of
> > the
> > > new
> > > >> charter. This would make IKEv2/IPsec more attractive as a
> security
> > > option
> > > >> for cellular operators.
> > > >>
> > > >> Comments?
> > > >>
> > > >>            jak
> > > >>
> > > >>
> > > >>
> > > >> _______________________________________________
> > > >> Mip6 mailing list
> > > >> Mip6@ietf.org
> > > >> https://www1.ietf.org/mailman/listinfo/mip6
> > > >
> > > >
> > >
> > >
> > >
> > > _______________________________________________
> > > Mip6 mailing list
> > > Mip6@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/mip6
> >
> >
> > "This email message and any attachments are confidential information
> of
> > Starent Networks, Corp. The information transmitted may not be used
to
> > create or change any contractual obligations of Starent Networks,
> Corp.
> > Any
> > review, retransmission, dissemination or other use of, or taking of
> any
> > action in reliance upon this e-mail and its attachments by persons
or
> > entities other than the intended recipient is prohibited. If you are
> not
> > the
> > intended recipient, please notify the sender immediately -- by
> replying to
> > this message or by sending an email to
postmaster@starentnetworks.com
> --
>=20
> > and
> > destroy all copies of this message and any attachments without
reading
> or
> > disclosing their contents. Thank you."
> >
> >
> >
> > _______________________________________________
> > Mip6 mailing list
> > Mip6@ietf.org
> > https://www1.ietf.org/mailman/listinfo/mip6
>=20


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



From mip6-bounces@ietf.org Tue Jul 18 16:06:21 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G2vpj-0006uO-P2; Tue, 18 Jul 2006 16:06:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G2vpj-0006tz-42
	for mip6@ietf.org; Tue, 18 Jul 2006 16:06:19 -0400
Received: from key1.docomolabs-usa.com ([216.98.102.225]
	helo=fridge.docomolabs-usa.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G2vpi-0002Mw-Et
	for mip6@ietf.org; Tue, 18 Jul 2006 16:06:19 -0400
Message-ID: <035101c6aaa5$e8097ee0$196115ac@dcml.docomolabsusa.com>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Tsirtsis, George" <tsirtsis@qualcomm.com>,
	"Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
References: <7EB20EA0938B4D42A2D82689365C9B7A0CBDEE@NAEX14.na.qualcomm.com>
Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
Date: Tue, 18 Jul 2006 13:08:16 -0700
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: 9f79b8e383fd3af2b1b5b1d0910f6094
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Yes, that's true. The two are not coupled as in MIPv4.

Do you have any idea what the typical 3GPP2 operator practice is for MIPv4?

            jak

----- Original Message ----- 
From: "Tsirtsis, George" <tsirtsis@qualcomm.com>
To: "James Kempf" <kempf@docomolabs-usa.com>; "Chowdhury, Kuntal" 
<kchowdhury@starentnetworks.com>
Cc: <mip6@ietf.org>
Sent: Tuesday, July 18, 2006 12:49 PM
Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?


I guess the important thing is to understand how the typical SA lifetime
relates to the typical MIP6 Binding Lifetime. The MN will have to at
least wake up to refresh its binding.

George

> -----Original Message-----
> From: James Kempf [mailto:kempf@docomolabs-usa.com]
> Sent: Tuesday, July 18, 2006 3:37 PM
> To: Tsirtsis, George; Chowdhury, Kuntal
> Cc: mip6@ietf.org
> Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert to
HA?
>
> I don't know. What do operators typically set the SA lifetime to?
Though
> perhaps this is an unanswerable question because, as yet, has anybody
> deployed MIPv6?
>
> My only observation is that this seems to be an issue with Wimax
Forum,
> and
> one of the primary motivators for wanting to use the RFC 4285 Auth
Option.
> If IETF and the MIP6 WG would like to encourage them to use IKE (as
seemed
> to be the sentiment when RFC 4285 was discussed, and one of the
reasons
> why
> it is not PS), it might be worthwhile to try to address their
concerns.
>
>             jak
>
> ----- Original Message -----
> From: "Tsirtsis, George" <tsirtsis@qualcomm.com>
> To: "James Kempf" <kempf@docomolabs-usa.com>; "Chowdhury, Kuntal"
> <kchowdhury@starentnetworks.com>
> Cc: <mip6@ietf.org>
> Sent: Tuesday, July 18, 2006 12:10 PM
> Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode Alert to
HA?
>
>
> May I ask, what is the typical lifetime of the SA and what would you
> lengthen it to?
> George
>
> > -----Original Message-----
> > From: James Kempf [mailto:kempf@docomolabs-usa.com]
> > Sent: Tuesday, July 18, 2006 2:43 PM
> > To: Chowdhury, Kuntal
> > Cc: mip6@ietf.org
> > Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert
to
> HA?
> >
> > Kuntal,
> >
> > The intent is not to introduce something that the MN would send
during
> > dormant mode. Indeed, as you have described, this would negatively
> impact
> > battery life.
> >
> > The intent is to provide a way for the MN to say that it is about to
> go
> > into
> > dormant mode, so please lengthen the IPsec SA timeout to avoid
having
> it
> > expire for some longer period of time.
> >
> >             jak
> >
> > ----- Original Message -----
> > From: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
> > To: "James Kempf" <kempf@docomolabs-usa.com>
> > Cc: <mip6@ietf.org>
> > Sent: Tuesday, July 18, 2006 11:20 AM
> > Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode Alert
to
> HA?
> >
> >
> > James,
> >
> > This is a good discussion. Indeed the need for IPsec keepalives (or
> DPD)
> > over the air when the MN is dormant (or idle) is an issue in the
> > cellular networks. The issue is Not that there are no mip6 messages
> > defined or the HA is not aware of dormancy. It is more of a paging
> > channel capacity issue, MN's battery life issue and the signaling
> > overhead to transport the keepalives for a dormant MN issue.
> >
> > So, any new message however small won't solve the problem, IMHO.
> >
> > -Kuntal
> >
> >
> > > -----Original Message-----
> > > From: James Kempf [mailto:kempf@docomolabs-usa.com]
> > > Sent: Tuesday, July 18, 2006 11:17 AM
> > > To: Vijay Devarapalli
> > > Cc: mip6@ietf.org
> > > Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode
Alert
> to
> > HA?
> > >
> > > For security, the message would need to be sent within an SA.
There
> is
> > a
> > > question about which.
> > >
> > > One possibility is to do a Mobility Extension (call the messages
> > Sleeping
> > > and WakingUp) and send it within the IPsec SA between the HA and
MN.
> > The
> > > MN
> > > sends the Sleeping message when it is about to go into dormant
mode,
> > it
> > > sends the WakingUp message when it comes out again. The WakingUp
> > message
> > > isn't needed for the MN to get mobility service, it is just there
> for
> > > optimizing the SA timeouts. This would require a special API on
the
> HA
> > > between the MIP code and IKE code for the HA to extend the IPsec
SA
> > > lifetime, similar to the one for IKEv1 mobility. The solution
would
> > only
> > > be
> > > applicable to Mobile IP.
> > >
> > > The other possibility is to do an IKEv2 INFORMATIONAL message that
> is
> > sent
> > > within the IKE SA. It works similarly, but there would be no need
> for
> > any
> > > API on the HA, since the IKE code itself would process it
(actually,
> I
> > > proposed something like this to the Mobike WG but they didn't see
> the
> > need
> > > for it). This would be applicable to both Mobike and Mobile IP
(and
> > any
> > > other security protocol that uses IKEv2, so maybe HIP as well).
> > >
> > > One question is, does the HA need to do anything else if the MN
goes
> > into
> > > dormant mode? I think there are lots of things it could do
(lengthen
> > the
> > > BU
> > > timeout, apply a filter that is either mobile specified or part of
> the
> > > user's service profile with the operator to only allow specific
> > traffic
> > > through, etc.) but I would really like to keep things simple.
> > >
> > >             jak
> > >
> > > ----- Original Message -----
> > > From: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
> > > To: "James Kempf" <kempf@docomolabs-usa.com>
> > > Cc: <mip6@ietf.org>
> > > Sent: Monday, July 17, 2006 3:43 PM
> > > Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode
Alert
> to
> > HA?
> > >
> > >
> > > > the dormant mode extensions sounds good to me. we could do
> > > > this extension. one issue to consider - what triggers this
> > > > message? how does Mobile IP know the mobile node is going
> > > > into a dormant mode. if we have the trigger we should be
> > > > okay.
> > > >
> > > > but we have to check if this was the issue. with IKEv1 you
> > > > could negotiate a lifetime for the IPsec SA. IKEv2 does not
> > > > have the IPsec SA lifetime feature. so keepalives are
> > > > needed.
> > > >
> > > > James Kempf wrote:
> > > >> I was at Wimax Forum last week and I think I now understand why
> > they
> > > and
> > > >> 3GPP2 want to use RFC 4285 auth option rather than IPsec. One
> issue
> > -
> > > >> lack of EAP support for client auth - is solved by IKEv2 and
they
> > seem
> > > to
> > > >> now be moving in the direction of recommending IKEv2 if people
> want
> > to
> > > >> deploy IPsec.
> > > >
> > > > yes this was one of the main issues.
> > > >
> > > > the way I saw it folks in 3GPP2 liked RFC 4285 because it
> > > > is very similar to the MIPv4 mechanism and they were
> > > > comfortable with it.
> > > >
> > > > Vijay
> > > >
> > > > But the other issue is a bit more complex. 802.16, like
> > > >> most cellular protocols, has extensive support for dormant
mode,
> > and
> > > >> Wimax Forum is supporting dormant mode in their network design.
> If
> > > IPsec
> > > >> is used, then there is a risk when a mobile node goes into
> dormant
> > mode
> > > >> that the IPsec SA may time out. It is unfortunate that this was
> not
> > > >> brought up when the discussion about RFC 4285 was happening,
but
> I
> > > think
> > > >> this might be something that the WG could work on now as part
of
> > the
> > > new
> > > >> charter. This would make IKEv2/IPsec more attractive as a
> security
> > > option
> > > >> for cellular operators.
> > > >>
> > > >> Comments?
> > > >>
> > > >>            jak
> > > >>
> > > >>
> > > >>
> > > >> _______________________________________________
> > > >> Mip6 mailing list
> > > >> Mip6@ietf.org
> > > >> https://www1.ietf.org/mailman/listinfo/mip6
> > > >
> > > >
> > >
> > >
> > >
> > > _______________________________________________
> > > Mip6 mailing list
> > > Mip6@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/mip6
> >
> >
> > "This email message and any attachments are confidential information
> of
> > Starent Networks, Corp. The information transmitted may not be used
to
> > create or change any contractual obligations of Starent Networks,
> Corp.
> > Any
> > review, retransmission, dissemination or other use of, or taking of
> any
> > action in reliance upon this e-mail and its attachments by persons
or
> > entities other than the intended recipient is prohibited. If you are
> not
> > the
> > intended recipient, please notify the sender immediately -- by
> replying to
> > this message or by sending an email to
postmaster@starentnetworks.com
> --
>
> > and
> > destroy all copies of this message and any attachments without
reading
> or
> > disclosing their contents. Thank you."
> >
> >
> >
> > _______________________________________________
> > Mip6 mailing list
> > Mip6@ietf.org
> > https://www1.ietf.org/mailman/listinfo/mip6
>




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



From mip6-bounces@ietf.org Tue Jul 18 16:33:40 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G2wGB-0003zj-2y; Tue, 18 Jul 2006 16:33:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G2wGA-0003ze-DX
	for mip6@ietf.org; Tue, 18 Jul 2006 16:33:38 -0400
Received: from mx0.starentnetworks.com ([12.38.223.203])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G2wG9-0003Vd-Mj
	for mip6@ietf.org; Tue, 18 Jul 2006 16:33:38 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mx0.starentnetworks.com (Postfix) with ESMTP id 4723B90028;
	Tue, 18 Jul 2006 16:33:34 -0400 (EDT)
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 15880-10; Tue, 18 Jul 2006 16:33:28 -0400 (EDT)
Received: from exchtewks1.starentnetworks.com (exchtewks1.starentnetworks.com
	[12.33.233.52]) by mx0.starentnetworks.com (Postfix) with ESMTP;
	Tue, 18 Jul 2006 16:33:06 -0400 (EDT)
X-MessageTextProcessor: DisclaimIt (2.70.271) [Starent Networks Corp.]
Received: from exchtewks2.starentnetworks.com ([12.33.232.12]) by
	exchtewks1.starentnetworks.com with Microsoft
	SMTPSVC(6.0.3790.1830); Tue, 18 Jul 2006 16:27:40 -0400
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
Date: Tue, 18 Jul 2006 16:26:49 -0400
Message-ID: <7CCD07160348804497EF29E9EA5560D73C52B3@exchtewks2.starentnetworks.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
thread-index: AcaqoT0oJd81saAuThGdaMylszp3AwAAc5kAAAEz96A=
From: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
To: "Tsirtsis, George" <tsirtsis@qualcomm.com>
Importance: normal
Priority: normal
X-OriginalArrivalTime: 18 Jul 2006 20:27:40.0867 (UTC)
	FILETIME=[9E001130:01C6AAA8]
X-Virus-Scanned: amavisd-new 2.2.1 (20041222) at mx0.starentnetworks.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bc102ac530ba955ef81f1f75b8bebe44
Cc: mip6@ietf.org, James Kempf <kempf@docomolabs-usa.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org



> -----Original Message-----
> From: Tsirtsis, George [mailto:tsirtsis@qualcomm.com]
> Sent: Tuesday, July 18, 2006 2:49 PM
> To: James Kempf; Chowdhury, Kuntal
> Cc: mip6@ietf.org
> Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode Alert to
HA?
>=20
> I guess the important thing is to understand how the typical SA
lifetime
> relates to the typical MIP6 Binding Lifetime. The MN will have to at
> least wake up to refresh its binding.

[KC>] IPsec DPD has nothing to do with IPsec SA lifetime. So, even if
someone sets MIP6 BCE lifetime =3D IPsec SA lifetime, it won't stop =
IPsec
stack to send DPD messages to the peer (MN). MN waking up and refreshing
its MIP6 BCE is a basic requirement for MIP6 protocol to work.=20

>=20
> George
>=20
> > -----Original Message-----
> > From: James Kempf [mailto:kempf@docomolabs-usa.com]
> > Sent: Tuesday, July 18, 2006 3:37 PM
> > To: Tsirtsis, George; Chowdhury, Kuntal
> > Cc: mip6@ietf.org
> > Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert
to
> HA?
> >
> > I don't know. What do operators typically set the SA lifetime to?
> Though
> > perhaps this is an unanswerable question because, as yet, has
anybody
> > deployed MIPv6?
> >
> > My only observation is that this seems to be an issue with Wimax
> Forum,
> > and
> > one of the primary motivators for wanting to use the RFC 4285 Auth
> Option.
> > If IETF and the MIP6 WG would like to encourage them to use IKE (as
> seemed
> > to be the sentiment when RFC 4285 was discussed, and one of the
> reasons
> > why
> > it is not PS), it might be worthwhile to try to address their
> concerns.
> >
> >             jak
> >
> > ----- Original Message -----
> > From: "Tsirtsis, George" <tsirtsis@qualcomm.com>
> > To: "James Kempf" <kempf@docomolabs-usa.com>; "Chowdhury, Kuntal"
> > <kchowdhury@starentnetworks.com>
> > Cc: <mip6@ietf.org>
> > Sent: Tuesday, July 18, 2006 12:10 PM
> > Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode Alert
to
> HA?
> >
> >
> > May I ask, what is the typical lifetime of the SA and what would you
> > lengthen it to?
> > George
> >
> > > -----Original Message-----
> > > From: James Kempf [mailto:kempf@docomolabs-usa.com]
> > > Sent: Tuesday, July 18, 2006 2:43 PM
> > > To: Chowdhury, Kuntal
> > > Cc: mip6@ietf.org
> > > Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode
Alert
> to
> > HA?
> > >
> > > Kuntal,
> > >
> > > The intent is not to introduce something that the MN would send
> during
> > > dormant mode. Indeed, as you have described, this would negatively
> > impact
> > > battery life.
> > >
> > > The intent is to provide a way for the MN to say that it is about
to
> > go
> > > into
> > > dormant mode, so please lengthen the IPsec SA timeout to avoid
> having
> > it
> > > expire for some longer period of time.
> > >
> > >             jak
> > >
> > > ----- Original Message -----
> > > From: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
> > > To: "James Kempf" <kempf@docomolabs-usa.com>
> > > Cc: <mip6@ietf.org>
> > > Sent: Tuesday, July 18, 2006 11:20 AM
> > > Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode
Alert
> to
> > HA?
> > >
> > >
> > > James,
> > >
> > > This is a good discussion. Indeed the need for IPsec keepalives
(or
> > DPD)
> > > over the air when the MN is dormant (or idle) is an issue in the
> > > cellular networks. The issue is Not that there are no mip6
messages
> > > defined or the HA is not aware of dormancy. It is more of a paging
> > > channel capacity issue, MN's battery life issue and the signaling
> > > overhead to transport the keepalives for a dormant MN issue.
> > >
> > > So, any new message however small won't solve the problem, IMHO.
> > >
> > > -Kuntal
> > >
> > >
> > > > -----Original Message-----
> > > > From: James Kempf [mailto:kempf@docomolabs-usa.com]
> > > > Sent: Tuesday, July 18, 2006 11:17 AM
> > > > To: Vijay Devarapalli
> > > > Cc: mip6@ietf.org
> > > > Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode
> Alert
> > to
> > > HA?
> > > >
> > > > For security, the message would need to be sent within an SA.
> There
> > is
> > > a
> > > > question about which.
> > > >
> > > > One possibility is to do a Mobility Extension (call the messages
> > > Sleeping
> > > > and WakingUp) and send it within the IPsec SA between the HA and
> MN.
> > > The
> > > > MN
> > > > sends the Sleeping message when it is about to go into dormant
> mode,
> > > it
> > > > sends the WakingUp message when it comes out again. The WakingUp
> > > message
> > > > isn't needed for the MN to get mobility service, it is just
there
> > for
> > > > optimizing the SA timeouts. This would require a special API on
> the
> > HA
> > > > between the MIP code and IKE code for the HA to extend the IPsec
> SA
> > > > lifetime, similar to the one for IKEv1 mobility. The solution
> would
> > > only
> > > > be
> > > > applicable to Mobile IP.
> > > >
> > > > The other possibility is to do an IKEv2 INFORMATIONAL message
that
> > is
> > > sent
> > > > within the IKE SA. It works similarly, but there would be no
need
> > for
> > > any
> > > > API on the HA, since the IKE code itself would process it
> (actually,
> > I
> > > > proposed something like this to the Mobike WG but they didn't
see
> > the
> > > need
> > > > for it). This would be applicable to both Mobike and Mobile IP
> (and
> > > any
> > > > other security protocol that uses IKEv2, so maybe HIP as well).
> > > >
> > > > One question is, does the HA need to do anything else if the MN
> goes
> > > into
> > > > dormant mode? I think there are lots of things it could do
> (lengthen
> > > the
> > > > BU
> > > > timeout, apply a filter that is either mobile specified or part
of
> > the
> > > > user's service profile with the operator to only allow specific
> > > traffic
> > > > through, etc.) but I would really like to keep things simple.
> > > >
> > > >             jak
> > > >
> > > > ----- Original Message -----
> > > > From: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
> > > > To: "James Kempf" <kempf@docomolabs-usa.com>
> > > > Cc: <mip6@ietf.org>
> > > > Sent: Monday, July 17, 2006 3:43 PM
> > > > Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode
> Alert
> > to
> > > HA?
> > > >
> > > >
> > > > > the dormant mode extensions sounds good to me. we could do
> > > > > this extension. one issue to consider - what triggers this
> > > > > message? how does Mobile IP know the mobile node is going
> > > > > into a dormant mode. if we have the trigger we should be
> > > > > okay.
> > > > >
> > > > > but we have to check if this was the issue. with IKEv1 you
> > > > > could negotiate a lifetime for the IPsec SA. IKEv2 does not
> > > > > have the IPsec SA lifetime feature. so keepalives are
> > > > > needed.
> > > > >
> > > > > James Kempf wrote:
> > > > >> I was at Wimax Forum last week and I think I now understand
why
> > > they
> > > > and
> > > > >> 3GPP2 want to use RFC 4285 auth option rather than IPsec. One
> > issue
> > > -
> > > > >> lack of EAP support for client auth - is solved by IKEv2 and
> they
> > > seem
> > > > to
> > > > >> now be moving in the direction of recommending IKEv2 if
people
> > want
> > > to
> > > > >> deploy IPsec.
> > > > >
> > > > > yes this was one of the main issues.
> > > > >
> > > > > the way I saw it folks in 3GPP2 liked RFC 4285 because it
> > > > > is very similar to the MIPv4 mechanism and they were
> > > > > comfortable with it.
> > > > >
> > > > > Vijay
> > > > >
> > > > > But the other issue is a bit more complex. 802.16, like
> > > > >> most cellular protocols, has extensive support for dormant
> mode,
> > > and
> > > > >> Wimax Forum is supporting dormant mode in their network
design.
> > If
> > > > IPsec
> > > > >> is used, then there is a risk when a mobile node goes into
> > dormant
> > > mode
> > > > >> that the IPsec SA may time out. It is unfortunate that this
was
> > not
> > > > >> brought up when the discussion about RFC 4285 was happening,
> but
> > I
> > > > think
> > > > >> this might be something that the WG could work on now as part
> of
> > > the
> > > > new
> > > > >> charter. This would make IKEv2/IPsec more attractive as a
> > security
> > > > option
> > > > >> for cellular operators.
> > > > >>
> > > > >> Comments?
> > > > >>
> > > > >>            jak
> > > > >>
> > > > >>
> > > > >>
> > > > >> _______________________________________________
> > > > >> Mip6 mailing list
> > > > >> Mip6@ietf.org
> > > > >> https://www1.ietf.org/mailman/listinfo/mip6
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > > > _______________________________________________
> > > > Mip6 mailing list
> > > > Mip6@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/mip6
> > >
> > >
> > > "This email message and any attachments are confidential
information
> > of
> > > Starent Networks, Corp. The information transmitted may not be
used
> to
> > > create or change any contractual obligations of Starent Networks,
> > Corp.
> > > Any
> > > review, retransmission, dissemination or other use of, or taking
of
> > any
> > > action in reliance upon this e-mail and its attachments by persons
> or
> > > entities other than the intended recipient is prohibited. If you
are
> > not
> > > the
> > > intended recipient, please notify the sender immediately -- by
> > replying to
> > > this message or by sending an email to
> postmaster@starentnetworks.com
> > --
> >
> > > and
> > > destroy all copies of this message and any attachments without
> reading
> > or
> > > disclosing their contents. Thank you."
> > >
> > >
> > >
> > > _______________________________________________
> > > Mip6 mailing list
> > > Mip6@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/mip6
> >


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



From mip6-bounces@ietf.org Tue Jul 18 16:55:57 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G2wbk-00069H-7S; Tue, 18 Jul 2006 16:55:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G2wbj-00069C-Is
	for mip6@ietf.org; Tue, 18 Jul 2006 16:55:55 -0400
Received: from atlrel6.hp.com ([156.153.255.205])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G2wbi-0005ws-AQ
	for mip6@ietf.org; Tue, 18 Jul 2006 16:55:55 -0400
Received: from smtp2.fc.hp.com (smtp2.fc.hp.com [15.11.136.114])
	by atlrel6.hp.com (Postfix) with ESMTP id CFF90358B9;
	Tue, 18 Jul 2006 16:55:53 -0400 (EDT)
Received: from [16.116.96.215] (spaceshipone.zko.hp.com [16.116.96.215])
	by smtp2.fc.hp.com (Postfix) with ESMTP id BC9F4513F6;
	Tue, 18 Jul 2006 20:55:52 +0000 (UTC)
Message-ID: <44BD4AD8.6080606@hp.com>
Date: Tue, 18 Jul 2006 16:55:52 -0400
From: Brian Haley <brian.haley@hp.com>
Organization: Open Source and Linux Organization
User-Agent: Thunderbird 1.5.0.4 (X11/20060615)
MIME-Version: 1.0
To: Alexandru Petrescu <alexandru.petrescu@motorola.com>
Subject: Re: [Mip6] New charter item: HA assignment
References: <729b68be0607180431m773dc847qed3e7350819a8d04@mail.gmail.com>	<44BD1105.5040904@motorola.com>	<02fc01c6aa99$de869d00$196115ac@dcml.docomolabsusa.com>
	<44BD36F9.3020400@motorola.com>
In-Reply-To: <44BD36F9.3020400@motorola.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>,
	James Kempf <kempf@docomolabs-usa.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

>> 3) Immediately after the MN finishes the IKEv2 transaction, the first
>>  HA could send a HA Switch message (draft-ietf-mip6-ha-switch-00.txt)
>>  within the IPsec SA, telling the MN to go elsewhere. The MN would be
>>  delayed by the amount of time needed to do the IKEv2 transaction,
>> but that does provide security. This seems like it would be the most 
>> direct way.
> 
> What if the HA Switch message gets lost?  That's not a TCP message I
> suppose.  I haven't read the HA switch draft in detail... is there
> retransmission of it?  Is it needed?

Section 4.2 covers retransmissions.  The HA knows the MN got the message 
once it deletes its binding.

-Brian

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



From mip6-bounces@ietf.org Tue Jul 18 17:38:21 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G2xGh-0002um-Jn; Tue, 18 Jul 2006 17:38:15 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G2xGf-0002ug-PI
	for mip6@ietf.org; Tue, 18 Jul 2006 17:38:13 -0400
Received: from mail1.azairenet.com ([66.92.223.4] helo=bart.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G2xGd-00024h-4c
	for mip6@ietf.org; Tue, 18 Jul 2006 17:38:13 -0400
Received: from [10.1.201.0] ([10.1.201.0]) by bart.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Tue, 18 Jul 2006 14:38:04 -0700
Message-ID: <44BD5463.6040301@azairenet.com>
Date: Tue, 18 Jul 2006 14:36:35 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Debian Thunderbird 1.0.2 (X11/20060423)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Tsirtsis, George" <tsirtsis@qualcomm.com>
Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
References: <7EB20EA0938B4D42A2D82689365C9B7A0CBDE3@NAEX14.na.qualcomm.com>
In-Reply-To: <7EB20EA0938B4D42A2D82689365C9B7A0CBDE3@NAEX14.na.qualcomm.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 18 Jul 2006 21:38:04.0140 (UTC)
	FILETIME=[734462C0:01C6AAB2]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 96e0f8497f38c15fbfc8f6f315bcdecb
Cc: mip6@ietf.org, James Kempf <kempf@docomolabs-usa.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Tsirtsis, George wrote:
> May I ask, what is the typical lifetime of the SA and what would you
> lengthen it to?
> George 

with IKEv2 there is no ability to negotiate a lifetime for
the IPsec SA. it is purely local policy. the initiator and
the responder decide independently on how to set the SA
lifetimes.

many IPsec implementations implement two timers. 1) idle
timer 2) DPD timer. the idle timer gets reset everytime there
is some traffic received over the IPsec SA. DPD is triggered
once in a while. as long as the other end responds to the
DPD message, the IPsec SA is not deleted. some implementations
combine these two timers and trigger DPD whenever the idle
timer expires.

I never understood why IKEv2 does not have the ability to
negotiate a lifetime for the IPsec SA (and not worry about
having to send keepalives/data traffic for that duration).

Vijay

> 
> 
>>-----Original Message-----
>>From: James Kempf [mailto:kempf@docomolabs-usa.com]
>>Sent: Tuesday, July 18, 2006 2:43 PM
>>To: Chowdhury, Kuntal
>>Cc: mip6@ietf.org
>>Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert to
> 
> HA?
> 
>>Kuntal,
>>
>>The intent is not to introduce something that the MN would send during
>>dormant mode. Indeed, as you have described, this would negatively
> 
> impact
> 
>>battery life.
>>
>>The intent is to provide a way for the MN to say that it is about to
> 
> go
> 
>>into
>>dormant mode, so please lengthen the IPsec SA timeout to avoid having
> 
> it
> 
>>expire for some longer period of time.
>>
>>            jak
>>
>>----- Original Message -----
>>From: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
>>To: "James Kempf" <kempf@docomolabs-usa.com>
>>Cc: <mip6@ietf.org>
>>Sent: Tuesday, July 18, 2006 11:20 AM
>>Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode Alert to
> 
> HA?
> 
>>
>>James,
>>
>>This is a good discussion. Indeed the need for IPsec keepalives (or
> 
> DPD)
> 
>>over the air when the MN is dormant (or idle) is an issue in the
>>cellular networks. The issue is Not that there are no mip6 messages
>>defined or the HA is not aware of dormancy. It is more of a paging
>>channel capacity issue, MN's battery life issue and the signaling
>>overhead to transport the keepalives for a dormant MN issue.
>>
>>So, any new message however small won't solve the problem, IMHO.
>>
>>-Kuntal
>>
>>
>>
>>>-----Original Message-----
>>>From: James Kempf [mailto:kempf@docomolabs-usa.com]
>>>Sent: Tuesday, July 18, 2006 11:17 AM
>>>To: Vijay Devarapalli
>>>Cc: mip6@ietf.org
>>>Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert
> 
> to
> 
>>HA?
>>
>>>For security, the message would need to be sent within an SA. There
> 
> is
> 
>>a
>>
>>>question about which.
>>>
>>>One possibility is to do a Mobility Extension (call the messages
>>
>>Sleeping
>>
>>>and WakingUp) and send it within the IPsec SA between the HA and MN.
>>
>>The
>>
>>>MN
>>>sends the Sleeping message when it is about to go into dormant mode,
>>
>>it
>>
>>>sends the WakingUp message when it comes out again. The WakingUp
>>
>>message
>>
>>>isn't needed for the MN to get mobility service, it is just there
> 
> for
> 
>>>optimizing the SA timeouts. This would require a special API on the
> 
> HA
> 
>>>between the MIP code and IKE code for the HA to extend the IPsec SA
>>>lifetime, similar to the one for IKEv1 mobility. The solution would
>>
>>only
>>
>>>be
>>>applicable to Mobile IP.
>>>
>>>The other possibility is to do an IKEv2 INFORMATIONAL message that
> 
> is
> 
>>sent
>>
>>>within the IKE SA. It works similarly, but there would be no need
> 
> for
> 
>>any
>>
>>>API on the HA, since the IKE code itself would process it (actually,
> 
> I
> 
>>>proposed something like this to the Mobike WG but they didn't see
> 
> the
> 
>>need
>>
>>>for it). This would be applicable to both Mobike and Mobile IP (and
>>
>>any
>>
>>>other security protocol that uses IKEv2, so maybe HIP as well).
>>>
>>>One question is, does the HA need to do anything else if the MN goes
>>
>>into
>>
>>>dormant mode? I think there are lots of things it could do (lengthen
>>
>>the
>>
>>>BU
>>>timeout, apply a filter that is either mobile specified or part of
> 
> the
> 
>>>user's service profile with the operator to only allow specific
>>
>>traffic
>>
>>>through, etc.) but I would really like to keep things simple.
>>>
>>>            jak
>>>
>>>----- Original Message -----
>>>From: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
>>>To: "James Kempf" <kempf@docomolabs-usa.com>
>>>Cc: <mip6@ietf.org>
>>>Sent: Monday, July 17, 2006 3:43 PM
>>>Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert
> 
> to
> 
>>HA?
>>
>>>
>>>>the dormant mode extensions sounds good to me. we could do
>>>>this extension. one issue to consider - what triggers this
>>>>message? how does Mobile IP know the mobile node is going
>>>>into a dormant mode. if we have the trigger we should be
>>>>okay.
>>>>
>>>>but we have to check if this was the issue. with IKEv1 you
>>>>could negotiate a lifetime for the IPsec SA. IKEv2 does not
>>>>have the IPsec SA lifetime feature. so keepalives are
>>>>needed.
>>>>
>>>>James Kempf wrote:
>>>>
>>>>>I was at Wimax Forum last week and I think I now understand why
>>
>>they
>>
>>>and
>>>
>>>>>3GPP2 want to use RFC 4285 auth option rather than IPsec. One
> 
> issue
> 
>>-
>>
>>>>>lack of EAP support for client auth - is solved by IKEv2 and they
>>
>>seem
>>
>>>to
>>>
>>>>>now be moving in the direction of recommending IKEv2 if people
> 
> want
> 
>>to
>>
>>>>>deploy IPsec.
>>>>
>>>>yes this was one of the main issues.
>>>>
>>>>the way I saw it folks in 3GPP2 liked RFC 4285 because it
>>>>is very similar to the MIPv4 mechanism and they were
>>>>comfortable with it.
>>>>
>>>>Vijay
>>>>
>>>>But the other issue is a bit more complex. 802.16, like
>>>>
>>>>>most cellular protocols, has extensive support for dormant mode,
>>
>>and
>>
>>>>>Wimax Forum is supporting dormant mode in their network design.
> 
> If
> 
>>>IPsec
>>>
>>>>>is used, then there is a risk when a mobile node goes into
> 
> dormant
> 
>>mode
>>
>>>>>that the IPsec SA may time out. It is unfortunate that this was
> 
> not
> 
>>>>>brought up when the discussion about RFC 4285 was happening, but
> 
> I
> 
>>>think
>>>
>>>>>this might be something that the WG could work on now as part of
>>
>>the
>>
>>>new
>>>
>>>>>charter. This would make IKEv2/IPsec more attractive as a
> 
> security
> 
>>>option
>>>
>>>>>for cellular operators.
>>>>>
>>>>>Comments?
>>>>>
>>>>>           jak
>>>>>
>>>>>
>>>>>
>>>>>_______________________________________________
>>>>>Mip6 mailing list
>>>>>Mip6@ietf.org
>>>>>https://www1.ietf.org/mailman/listinfo/mip6
>>>>
>>>>
>>>
>>>
>>>_______________________________________________
>>>Mip6 mailing list
>>>Mip6@ietf.org
>>>https://www1.ietf.org/mailman/listinfo/mip6
>>
>>
>>"This email message and any attachments are confidential information
> 
> of
> 
>>Starent Networks, Corp. The information transmitted may not be used to
>>create or change any contractual obligations of Starent Networks,
> 
> Corp.
> 
>>Any
>>review, retransmission, dissemination or other use of, or taking of
> 
> any
> 
>>action in reliance upon this e-mail and its attachments by persons or
>>entities other than the intended recipient is prohibited. If you are
> 
> not
> 
>>the
>>intended recipient, please notify the sender immediately -- by
> 
> replying to
> 
>>this message or by sending an email to postmaster@starentnetworks.com
> 
> --
> 
>>and
>>destroy all copies of this message and any attachments without reading
> 
> or
> 
>>disclosing their contents. Thank you."
>>
>>
>>
>>_______________________________________________
>>Mip6 mailing list
>>Mip6@ietf.org
>>https://www1.ietf.org/mailman/listinfo/mip6
> 
> 
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6


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



From mip6-bounces@ietf.org Tue Jul 18 17:43:59 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G2xMF-0003aO-82; Tue, 18 Jul 2006 17:43:59 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G2xMD-0003Zr-SN
	for mip6@ietf.org; Tue, 18 Jul 2006 17:43:57 -0400
Received: from mail1.azairenet.com ([66.92.223.4] helo=bart.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G2xMC-0003ap-8F
	for mip6@ietf.org; Tue, 18 Jul 2006 17:43:57 -0400
Received: from [10.1.201.0] ([10.1.201.0]) by bart.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Tue, 18 Jul 2006 14:43:54 -0700
Message-ID: <44BD55BE.8090407@azairenet.com>
Date: Tue, 18 Jul 2006 14:42:22 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Debian Thunderbird 1.0.2 (X11/20060423)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: James Kempf <kempf@docomolabs-usa.com>
Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
References: <7EB20EA0938B4D42A2D82689365C9B7A0CBDE3@NAEX14.na.qualcomm.com>
	<033201c6aaa1$787be580$196115ac@dcml.docomolabsusa.com>
In-Reply-To: <033201c6aaa1$787be580$196115ac@dcml.docomolabsusa.com>
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 18 Jul 2006 21:43:54.0651 (UTC)
	FILETIME=[44301EB0:01C6AAB3]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2b3349545af520ba354ccdc9e1a03fc1
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

James Kempf wrote:
> I don't know. What do operators typically set the SA lifetime to? Though 
> perhaps this is an unanswerable question because, as yet, has anybody 
> deployed MIPv6?

this is more of an IPsec issue. it depends on the local policy
on the initiator and responder. however, as long as there is
traffic and there are responses to DPD messages, the IPsec SA
is not deleted.

Vijay

> 
> My only observation is that this seems to be an issue with Wimax Forum, 
> and one of the primary motivators for wanting to use the RFC 4285 Auth 
> Option. If IETF and the MIP6 WG would like to encourage them to use IKE 
> (as seemed to be the sentiment when RFC 4285 was discussed, and one of 
> the reasons why it is not PS), it might be worthwhile to try to address 
> their concerns.
> 
>            jak
> 
> ----- Original Message ----- From: "Tsirtsis, George" 
> <tsirtsis@qualcomm.com>
> To: "James Kempf" <kempf@docomolabs-usa.com>; "Chowdhury, Kuntal" 
> <kchowdhury@starentnetworks.com>
> Cc: <mip6@ietf.org>
> Sent: Tuesday, July 18, 2006 12:10 PM
> Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
> 
> 
> May I ask, what is the typical lifetime of the SA and what would you
> lengthen it to?
> George
> 
>> -----Original Message-----
>> From: James Kempf [mailto:kempf@docomolabs-usa.com]
>> Sent: Tuesday, July 18, 2006 2:43 PM
>> To: Chowdhury, Kuntal
>> Cc: mip6@ietf.org
>> Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert to
> 
> HA?
> 
>>
>> Kuntal,
>>
>> The intent is not to introduce something that the MN would send during
>> dormant mode. Indeed, as you have described, this would negatively
> 
> impact
> 
>> battery life.
>>
>> The intent is to provide a way for the MN to say that it is about to
> 
> go
> 
>> into
>> dormant mode, so please lengthen the IPsec SA timeout to avoid having
> 
> it
> 
>> expire for some longer period of time.
>>
>>             jak
>>
>> ----- Original Message -----
>> From: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
>> To: "James Kempf" <kempf@docomolabs-usa.com>
>> Cc: <mip6@ietf.org>
>> Sent: Tuesday, July 18, 2006 11:20 AM
>> Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode Alert to
> 
> HA?
> 
>>
>>
>> James,
>>
>> This is a good discussion. Indeed the need for IPsec keepalives (or
> 
> DPD)
> 
>> over the air when the MN is dormant (or idle) is an issue in the
>> cellular networks. The issue is Not that there are no mip6 messages
>> defined or the HA is not aware of dormancy. It is more of a paging
>> channel capacity issue, MN's battery life issue and the signaling
>> overhead to transport the keepalives for a dormant MN issue.
>>
>> So, any new message however small won't solve the problem, IMHO.
>>
>> -Kuntal
>>
>>
>> > -----Original Message-----
>> > From: James Kempf [mailto:kempf@docomolabs-usa.com]
>> > Sent: Tuesday, July 18, 2006 11:17 AM
>> > To: Vijay Devarapalli
>> > Cc: mip6@ietf.org
>> > Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert
> 
> to
> 
>> HA?
>> >
>> > For security, the message would need to be sent within an SA. There
> 
> is
> 
>> a
>> > question about which.
>> >
>> > One possibility is to do a Mobility Extension (call the messages
>> Sleeping
>> > and WakingUp) and send it within the IPsec SA between the HA and MN.
>> The
>> > MN
>> > sends the Sleeping message when it is about to go into dormant mode,
>> it
>> > sends the WakingUp message when it comes out again. The WakingUp
>> message
>> > isn't needed for the MN to get mobility service, it is just there
> 
> for
> 
>> > optimizing the SA timeouts. This would require a special API on the
> 
> HA
> 
>> > between the MIP code and IKE code for the HA to extend the IPsec SA
>> > lifetime, similar to the one for IKEv1 mobility. The solution would
>> only
>> > be
>> > applicable to Mobile IP.
>> >
>> > The other possibility is to do an IKEv2 INFORMATIONAL message that
> 
> is
> 
>> sent
>> > within the IKE SA. It works similarly, but there would be no need
> 
> for
> 
>> any
>> > API on the HA, since the IKE code itself would process it (actually,
> 
> I
> 
>> > proposed something like this to the Mobike WG but they didn't see
> 
> the
> 
>> need
>> > for it). This would be applicable to both Mobike and Mobile IP (and
>> any
>> > other security protocol that uses IKEv2, so maybe HIP as well).
>> >
>> > One question is, does the HA need to do anything else if the MN goes
>> into
>> > dormant mode? I think there are lots of things it could do (lengthen
>> the
>> > BU
>> > timeout, apply a filter that is either mobile specified or part of
> 
> the
> 
>> > user's service profile with the operator to only allow specific
>> traffic
>> > through, etc.) but I would really like to keep things simple.
>> >
>> >             jak
>> >
>> > ----- Original Message -----
>> > From: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
>> > To: "James Kempf" <kempf@docomolabs-usa.com>
>> > Cc: <mip6@ietf.org>
>> > Sent: Monday, July 17, 2006 3:43 PM
>> > Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert
> 
> to
> 
>> HA?
>> >
>> >
>> > > the dormant mode extensions sounds good to me. we could do
>> > > this extension. one issue to consider - what triggers this
>> > > message? how does Mobile IP know the mobile node is going
>> > > into a dormant mode. if we have the trigger we should be
>> > > okay.
>> > >
>> > > but we have to check if this was the issue. with IKEv1 you
>> > > could negotiate a lifetime for the IPsec SA. IKEv2 does not
>> > > have the IPsec SA lifetime feature. so keepalives are
>> > > needed.
>> > >
>> > > James Kempf wrote:
>> > >> I was at Wimax Forum last week and I think I now understand why
>> they
>> > and
>> > >> 3GPP2 want to use RFC 4285 auth option rather than IPsec. One
> 
> issue
> 
>> -
>> > >> lack of EAP support for client auth - is solved by IKEv2 and they
>> seem
>> > to
>> > >> now be moving in the direction of recommending IKEv2 if people
> 
> want
> 
>> to
>> > >> deploy IPsec.
>> > >
>> > > yes this was one of the main issues.
>> > >
>> > > the way I saw it folks in 3GPP2 liked RFC 4285 because it
>> > > is very similar to the MIPv4 mechanism and they were
>> > > comfortable with it.
>> > >
>> > > Vijay
>> > >
>> > > But the other issue is a bit more complex. 802.16, like
>> > >> most cellular protocols, has extensive support for dormant mode,
>> and
>> > >> Wimax Forum is supporting dormant mode in their network design.
> 
> If
> 
>> > IPsec
>> > >> is used, then there is a risk when a mobile node goes into
> 
> dormant
> 
>> mode
>> > >> that the IPsec SA may time out. It is unfortunate that this was
> 
> not
> 
>> > >> brought up when the discussion about RFC 4285 was happening, but
> 
> I
> 
>> > think
>> > >> this might be something that the WG could work on now as part of
>> the
>> > new
>> > >> charter. This would make IKEv2/IPsec more attractive as a
> 
> security
> 
>> > option
>> > >> for cellular operators.
>> > >>
>> > >> Comments?
>> > >>
>> > >>            jak
>> > >>
>> > >>
>> > >>
>> > >> _______________________________________________
>> > >> Mip6 mailing list
>> > >> Mip6@ietf.org
>> > >> https://www1.ietf.org/mailman/listinfo/mip6
>> > >
>> > >
>> >
>> >
>> >
>> > _______________________________________________
>> > Mip6 mailing list
>> > Mip6@ietf.org
>> > https://www1.ietf.org/mailman/listinfo/mip6
>>
>>
>> "This email message and any attachments are confidential information
> 
> of
> 
>> Starent Networks, Corp. The information transmitted may not be used to
>> create or change any contractual obligations of Starent Networks,
> 
> Corp.
> 
>> Any
>> review, retransmission, dissemination or other use of, or taking of
> 
> any
> 
>> action in reliance upon this e-mail and its attachments by persons or
>> entities other than the intended recipient is prohibited. If you are
> 
> not
> 
>> the
>> intended recipient, please notify the sender immediately -- by
> 
> replying to
> 
>> this message or by sending an email to postmaster@starentnetworks.com
> 
> -- 
> 
>> and
>> destroy all copies of this message and any attachments without reading
> 
> or
> 
>> disclosing their contents. Thank you."
>>
>>
>>
>> _______________________________________________
>> Mip6 mailing list
>> Mip6@ietf.org
>> https://www1.ietf.org/mailman/listinfo/mip6
> 
> 
> 
> 
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6



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



From mip6-bounces@ietf.org Tue Jul 18 17:50:11 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G2xSD-0004ld-GK; Tue, 18 Jul 2006 17:50:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G2xSD-0004lY-0A
	for mip6@ietf.org; Tue, 18 Jul 2006 17:50:09 -0400
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G2xSA-0004Nn-Bg
	for mip6@ietf.org; Tue, 18 Jul 2006 17:50:08 -0400
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
	k6ILnwkx006263
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Tue, 18 Jul 2006 14:49:58 -0700
Received: from NAEXBR03.na.qualcomm.com (naexbr03.qualcomm.com
	[129.46.134.172])
	by crowley.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	k6ILjjHg003052; Tue, 18 Jul 2006 14:49:57 -0700 (PDT)
Received: from NAEX14.na.qualcomm.com ([10.47.5.242]) by
	NAEXBR03.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 18 Jul 2006 14:47:28 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
Date: Tue, 18 Jul 2006 14:47:27 -0700
Message-ID: <7EB20EA0938B4D42A2D82689365C9B7A0CBE20@NAEX14.na.qualcomm.com>
In-Reply-To: <44BD55BE.8090407@azairenet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
Thread-Index: Acaqs0qRyE/rx7MVRjuNAlTPAALevQAADs8Q
From: "Tsirtsis, George" <tsirtsis@qualcomm.com>
To: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>,
	"James Kempf" <kempf@docomolabs-usa.com>
X-OriginalArrivalTime: 18 Jul 2006 21:47:28.0092 (UTC)
	FILETIME=[C368A1C0:01C6AAB3]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 509eeaf340e89c687918a6101c6def35
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

So how often PDP messages are sent is also local policy? In which case
it can be configured to a time that makes sense for MIP or a given
deployment scenario.
George

> -----Original Message-----
> From: Vijay Devarapalli [mailto:vijay.devarapalli@azairenet.com]
> Sent: Tuesday, July 18, 2006 5:42 PM
> To: James Kempf
> Cc: Tsirtsis, George; Chowdhury, Kuntal; mip6@ietf.org
> Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert to
HA?
>=20
> James Kempf wrote:
> > I don't know. What do operators typically set the SA lifetime to?
Though
> > perhaps this is an unanswerable question because, as yet, has
anybody
> > deployed MIPv6?
>=20
> this is more of an IPsec issue. it depends on the local policy
> on the initiator and responder. however, as long as there is
> traffic and there are responses to DPD messages, the IPsec SA
> is not deleted.
>=20
> Vijay
>=20
> >
> > My only observation is that this seems to be an issue with Wimax
Forum,
> > and one of the primary motivators for wanting to use the RFC 4285
Auth
> > Option. If IETF and the MIP6 WG would like to encourage them to use
IKE
> > (as seemed to be the sentiment when RFC 4285 was discussed, and one
of
> > the reasons why it is not PS), it might be worthwhile to try to
address
> > their concerns.
> >
> >            jak
> >
> > ----- Original Message ----- From: "Tsirtsis, George"
> > <tsirtsis@qualcomm.com>
> > To: "James Kempf" <kempf@docomolabs-usa.com>; "Chowdhury, Kuntal"
> > <kchowdhury@starentnetworks.com>
> > Cc: <mip6@ietf.org>
> > Sent: Tuesday, July 18, 2006 12:10 PM
> > Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode Alert
to
> HA?
> >
> >
> > May I ask, what is the typical lifetime of the SA and what would you
> > lengthen it to?
> > George
> >
> >> -----Original Message-----
> >> From: James Kempf [mailto:kempf@docomolabs-usa.com]
> >> Sent: Tuesday, July 18, 2006 2:43 PM
> >> To: Chowdhury, Kuntal
> >> Cc: mip6@ietf.org
> >> Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert
to
> >
> > HA?
> >
> >>
> >> Kuntal,
> >>
> >> The intent is not to introduce something that the MN would send
during
> >> dormant mode. Indeed, as you have described, this would negatively
> >
> > impact
> >
> >> battery life.
> >>
> >> The intent is to provide a way for the MN to say that it is about
to
> >
> > go
> >
> >> into
> >> dormant mode, so please lengthen the IPsec SA timeout to avoid
having
> >
> > it
> >
> >> expire for some longer period of time.
> >>
> >>             jak
> >>
> >> ----- Original Message -----
> >> From: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
> >> To: "James Kempf" <kempf@docomolabs-usa.com>
> >> Cc: <mip6@ietf.org>
> >> Sent: Tuesday, July 18, 2006 11:20 AM
> >> Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode Alert
to
> >
> > HA?
> >
> >>
> >>
> >> James,
> >>
> >> This is a good discussion. Indeed the need for IPsec keepalives (or
> >
> > DPD)
> >
> >> over the air when the MN is dormant (or idle) is an issue in the
> >> cellular networks. The issue is Not that there are no mip6 messages
> >> defined or the HA is not aware of dormancy. It is more of a paging
> >> channel capacity issue, MN's battery life issue and the signaling
> >> overhead to transport the keepalives for a dormant MN issue.
> >>
> >> So, any new message however small won't solve the problem, IMHO.
> >>
> >> -Kuntal
> >>
> >>
> >> > -----Original Message-----
> >> > From: James Kempf [mailto:kempf@docomolabs-usa.com]
> >> > Sent: Tuesday, July 18, 2006 11:17 AM
> >> > To: Vijay Devarapalli
> >> > Cc: mip6@ietf.org
> >> > Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode
Alert
> >
> > to
> >
> >> HA?
> >> >
> >> > For security, the message would need to be sent within an SA.
There
> >
> > is
> >
> >> a
> >> > question about which.
> >> >
> >> > One possibility is to do a Mobility Extension (call the messages
> >> Sleeping
> >> > and WakingUp) and send it within the IPsec SA between the HA and
MN.
> >> The
> >> > MN
> >> > sends the Sleeping message when it is about to go into dormant
mode,
> >> it
> >> > sends the WakingUp message when it comes out again. The WakingUp
> >> message
> >> > isn't needed for the MN to get mobility service, it is just there
> >
> > for
> >
> >> > optimizing the SA timeouts. This would require a special API on
the
> >
> > HA
> >
> >> > between the MIP code and IKE code for the HA to extend the IPsec
SA
> >> > lifetime, similar to the one for IKEv1 mobility. The solution
would
> >> only
> >> > be
> >> > applicable to Mobile IP.
> >> >
> >> > The other possibility is to do an IKEv2 INFORMATIONAL message
that
> >
> > is
> >
> >> sent
> >> > within the IKE SA. It works similarly, but there would be no need
> >
> > for
> >
> >> any
> >> > API on the HA, since the IKE code itself would process it
(actually,
> >
> > I
> >
> >> > proposed something like this to the Mobike WG but they didn't see
> >
> > the
> >
> >> need
> >> > for it). This would be applicable to both Mobike and Mobile IP
(and
> >> any
> >> > other security protocol that uses IKEv2, so maybe HIP as well).
> >> >
> >> > One question is, does the HA need to do anything else if the MN
goes
> >> into
> >> > dormant mode? I think there are lots of things it could do
(lengthen
> >> the
> >> > BU
> >> > timeout, apply a filter that is either mobile specified or part
of
> >
> > the
> >
> >> > user's service profile with the operator to only allow specific
> >> traffic
> >> > through, etc.) but I would really like to keep things simple.
> >> >
> >> >             jak
> >> >
> >> > ----- Original Message -----
> >> > From: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
> >> > To: "James Kempf" <kempf@docomolabs-usa.com>
> >> > Cc: <mip6@ietf.org>
> >> > Sent: Monday, July 17, 2006 3:43 PM
> >> > Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode
Alert
> >
> > to
> >
> >> HA?
> >> >
> >> >
> >> > > the dormant mode extensions sounds good to me. we could do
> >> > > this extension. one issue to consider - what triggers this
> >> > > message? how does Mobile IP know the mobile node is going
> >> > > into a dormant mode. if we have the trigger we should be
> >> > > okay.
> >> > >
> >> > > but we have to check if this was the issue. with IKEv1 you
> >> > > could negotiate a lifetime for the IPsec SA. IKEv2 does not
> >> > > have the IPsec SA lifetime feature. so keepalives are
> >> > > needed.
> >> > >
> >> > > James Kempf wrote:
> >> > >> I was at Wimax Forum last week and I think I now understand
why
> >> they
> >> > and
> >> > >> 3GPP2 want to use RFC 4285 auth option rather than IPsec. One
> >
> > issue
> >
> >> -
> >> > >> lack of EAP support for client auth - is solved by IKEv2 and
they
> >> seem
> >> > to
> >> > >> now be moving in the direction of recommending IKEv2 if people
> >
> > want
> >
> >> to
> >> > >> deploy IPsec.
> >> > >
> >> > > yes this was one of the main issues.
> >> > >
> >> > > the way I saw it folks in 3GPP2 liked RFC 4285 because it
> >> > > is very similar to the MIPv4 mechanism and they were
> >> > > comfortable with it.
> >> > >
> >> > > Vijay
> >> > >
> >> > > But the other issue is a bit more complex. 802.16, like
> >> > >> most cellular protocols, has extensive support for dormant
mode,
> >> and
> >> > >> Wimax Forum is supporting dormant mode in their network
design.
> >
> > If
> >
> >> > IPsec
> >> > >> is used, then there is a risk when a mobile node goes into
> >
> > dormant
> >
> >> mode
> >> > >> that the IPsec SA may time out. It is unfortunate that this
was
> >
> > not
> >
> >> > >> brought up when the discussion about RFC 4285 was happening,
but
> >
> > I
> >
> >> > think
> >> > >> this might be something that the WG could work on now as part
of
> >> the
> >> > new
> >> > >> charter. This would make IKEv2/IPsec more attractive as a
> >
> > security
> >
> >> > option
> >> > >> for cellular operators.
> >> > >>
> >> > >> Comments?
> >> > >>
> >> > >>            jak
> >> > >>
> >> > >>
> >> > >>
> >> > >> _______________________________________________
> >> > >> Mip6 mailing list
> >> > >> Mip6@ietf.org
> >> > >> https://www1.ietf.org/mailman/listinfo/mip6
> >> > >
> >> > >
> >> >
> >> >
> >> >
> >> > _______________________________________________
> >> > Mip6 mailing list
> >> > Mip6@ietf.org
> >> > https://www1.ietf.org/mailman/listinfo/mip6
> >>
> >>
> >> "This email message and any attachments are confidential
information
> >
> > of
> >
> >> Starent Networks, Corp. The information transmitted may not be used
to
> >> create or change any contractual obligations of Starent Networks,
> >
> > Corp.
> >
> >> Any
> >> review, retransmission, dissemination or other use of, or taking of
> >
> > any
> >
> >> action in reliance upon this e-mail and its attachments by persons
or
> >> entities other than the intended recipient is prohibited. If you
are
> >
> > not
> >
> >> the
> >> intended recipient, please notify the sender immediately -- by
> >
> > replying to
> >
> >> this message or by sending an email to
postmaster@starentnetworks.com
> >
> > --
> >
> >> and
> >> destroy all copies of this message and any attachments without
reading
> >
> > or
> >
> >> disclosing their contents. Thank you."
> >>
> >>
> >>
> >> _______________________________________________
> >> Mip6 mailing list
> >> Mip6@ietf.org
> >> https://www1.ietf.org/mailman/listinfo/mip6
> >
> >
> >
> >
> > _______________________________________________
> > Mip6 mailing list
> > Mip6@ietf.org
> > https://www1.ietf.org/mailman/listinfo/mip6
>=20


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



From mip6-bounces@ietf.org Tue Jul 18 18:04:43 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G2xgF-0003JO-9C; Tue, 18 Jul 2006 18:04:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G2xgD-0003JJ-BS
	for mip6@ietf.org; Tue, 18 Jul 2006 18:04:37 -0400
Received: from motgate3.mot.com ([144.189.100.103])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G2xgB-0005IR-Ut
	for mip6@ietf.org; Tue, 18 Jul 2006 18:04:37 -0400
Received: from az33exr03.mot.com (az33exr03.mot.com [10.64.251.233])
	by motgate3.mot.com (8.12.11/Motorola) with ESMTP id k6IM4XI5018215;
	Tue, 18 Jul 2006 15:04:33 -0700 (MST)
Received: from [10.169.4.192] (mvp-10-169-4-192.corp.mot.com [10.169.4.192])
	by az33exr03.mot.com (8.13.1/8.13.0) with ESMTP id k6IM4S8I006068;
	Tue, 18 Jul 2006 17:04:29 -0500 (CDT)
Message-ID: <44BD5AEA.6020209@motorola.com>
Date: Wed, 19 Jul 2006 00:04:26 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: Brian Haley <brian.haley@hp.com>
Subject: Re: [Mip6] New charter item: HA assignment
References: <729b68be0607180431m773dc847qed3e7350819a8d04@mail.gmail.com>
	<44BD1105.5040904@motorola.com> <44BD3AA6.7070906@hp.com>
In-Reply-To: <44BD3AA6.7070906@hp.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAQAAAAQ=
X-White-List-Member: TRUE
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Brian Haley wrote:
> Didn't want to hijack the thread, but wanted to respond to Alex's 
> comment below.
> 
> Alexandru Petrescu wrote:
>> Jean-Michel Combes wrote:
>>> Hi,
>>> 
>>> as promised during the mip6 session, here is a point which, IMO,
>>>  is important from a MSP's point of view: Actually, the 
>>> bootstrapping solution, in the split scenario, only propose a HA
>>>  discovery mechanism (i.e. the MN receives a list of HA, from
>>> DNS, and chooses one of them). The MSP has no easy solution to 
>>> enforce one MN to have a specific HA.
>> 
>> One possible way is for a HA to stop sending BAck, at which point 
>> an MN would send DHAAD Request again, and a different HA replies 
>> back DHAAD, so end result is MN is assigned a new HA.
>> 
>> Another way is for the new HA to send Binding Refresh Request to MN
>>  (even if it has no BC entry for it).
> 
> BRR is sent from CN to MN, it is not defined to be sent from HA.

I think that depends on each one's interpretation of "correspondent".  I
see BRR very well sent by HA to MN if BCE lifetime expired and BU was lost.

> I know you brought-up extending it at the WG meeting (instead of 
> using HA switch), but I couldn't remember all the reasons we didn't 
> do that. IPsec is the other problem since the message has no 
> protection, but needs it.

Mostly ok with that, but I can't completely agree until I haven't read
the draft.  BRR is a Mobility Header, so assumed to be ok with IPsec.

IPsec is anyways a sensitive issue because we're talking three parties:
two HAs (an initial and an "assigned") and one MN, presumably HAs
exchange SAs.  Do you use the CA concept?

I'll have to read it.

Alex


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



From mip6-bounces@ietf.org Tue Jul 18 18:06:01 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G2xhZ-0004s3-Hu; Tue, 18 Jul 2006 18:06:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G2xhY-0004rs-Ax
	for mip6@ietf.org; Tue, 18 Jul 2006 18:06:00 -0400
Received: from mail1.azairenet.com ([66.92.223.4] helo=bart.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G2xhV-0005Ka-Kk
	for mip6@ietf.org; Tue, 18 Jul 2006 18:06:00 -0400
Received: from [10.1.201.20] ([10.1.201.20]) by bart.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Tue, 18 Jul 2006 15:05:54 -0700
Message-ID: <44BD5B3E.9080607@azairenet.com>
Date: Tue, 18 Jul 2006 15:05:50 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.4 (Windows/20060516)
MIME-Version: 1.0
To: "Tsirtsis, George" <tsirtsis@qualcomm.com>
Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
References: <7EB20EA0938B4D42A2D82689365C9B7A0CBE20@NAEX14.na.qualcomm.com>
In-Reply-To: <7EB20EA0938B4D42A2D82689365C9B7A0CBE20@NAEX14.na.qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 18 Jul 2006 22:05:54.0946 (UTC)
	FILETIME=[57252620:01C6AAB6]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a630332fa112280ecc4c4186b5c9ea83
Cc: mip6@ietf.org, James Kempf <kempf@docomolabs-usa.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Tsirtsis, George wrote:
> So how often PDP messages are sent is also local policy? 

I guess you meant DPD. yes it is local policy. the initiator
and responder configure this independently.

> In which case
> it can be configured to a time that makes sense for MIP or a given
> deployment scenario.

Yes. however, the IPsec implementation should allow for
sufficiently large values for DPD timer. but then again
DPD exists so that unwanted IPsec state is removed if
the other end goes down or if there is no traffic for a
long time.

Vijay

> George
> 
>> -----Original Message-----
>> From: Vijay Devarapalli [mailto:vijay.devarapalli@azairenet.com]
>> Sent: Tuesday, July 18, 2006 5:42 PM
>> To: James Kempf
>> Cc: Tsirtsis, George; Chowdhury, Kuntal; mip6@ietf.org
>> Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert to
> HA?
>> James Kempf wrote:
>>> I don't know. What do operators typically set the SA lifetime to?
> Though
>>> perhaps this is an unanswerable question because, as yet, has
> anybody
>>> deployed MIPv6?
>> this is more of an IPsec issue. it depends on the local policy
>> on the initiator and responder. however, as long as there is
>> traffic and there are responses to DPD messages, the IPsec SA
>> is not deleted.
>>
>> Vijay
>>
>>> My only observation is that this seems to be an issue with Wimax
> Forum,
>>> and one of the primary motivators for wanting to use the RFC 4285
> Auth
>>> Option. If IETF and the MIP6 WG would like to encourage them to use
> IKE
>>> (as seemed to be the sentiment when RFC 4285 was discussed, and one
> of
>>> the reasons why it is not PS), it might be worthwhile to try to
> address
>>> their concerns.
>>>
>>>            jak
>>>
>>> ----- Original Message ----- From: "Tsirtsis, George"
>>> <tsirtsis@qualcomm.com>
>>> To: "James Kempf" <kempf@docomolabs-usa.com>; "Chowdhury, Kuntal"
>>> <kchowdhury@starentnetworks.com>
>>> Cc: <mip6@ietf.org>
>>> Sent: Tuesday, July 18, 2006 12:10 PM
>>> Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode Alert
> to
>> HA?
>>>
>>> May I ask, what is the typical lifetime of the SA and what would you
>>> lengthen it to?
>>> George
>>>
>>>> -----Original Message-----
>>>> From: James Kempf [mailto:kempf@docomolabs-usa.com]
>>>> Sent: Tuesday, July 18, 2006 2:43 PM
>>>> To: Chowdhury, Kuntal
>>>> Cc: mip6@ietf.org
>>>> Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert
> to
>>> HA?
>>>
>>>> Kuntal,
>>>>
>>>> The intent is not to introduce something that the MN would send
> during
>>>> dormant mode. Indeed, as you have described, this would negatively
>>> impact
>>>
>>>> battery life.
>>>>
>>>> The intent is to provide a way for the MN to say that it is about
> to
>>> go
>>>
>>>> into
>>>> dormant mode, so please lengthen the IPsec SA timeout to avoid
> having
>>> it
>>>
>>>> expire for some longer period of time.
>>>>
>>>>             jak
>>>>
>>>> ----- Original Message -----
>>>> From: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
>>>> To: "James Kempf" <kempf@docomolabs-usa.com>
>>>> Cc: <mip6@ietf.org>
>>>> Sent: Tuesday, July 18, 2006 11:20 AM
>>>> Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode Alert
> to
>>> HA?
>>>
>>>>
>>>> James,
>>>>
>>>> This is a good discussion. Indeed the need for IPsec keepalives (or
>>> DPD)
>>>
>>>> over the air when the MN is dormant (or idle) is an issue in the
>>>> cellular networks. The issue is Not that there are no mip6 messages
>>>> defined or the HA is not aware of dormancy. It is more of a paging
>>>> channel capacity issue, MN's battery life issue and the signaling
>>>> overhead to transport the keepalives for a dormant MN issue.
>>>>
>>>> So, any new message however small won't solve the problem, IMHO.
>>>>
>>>> -Kuntal
>>>>
>>>>
>>>>> -----Original Message-----
>>>>> From: James Kempf [mailto:kempf@docomolabs-usa.com]
>>>>> Sent: Tuesday, July 18, 2006 11:17 AM
>>>>> To: Vijay Devarapalli
>>>>> Cc: mip6@ietf.org
>>>>> Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode
> Alert
>>> to
>>>
>>>> HA?
>>>>> For security, the message would need to be sent within an SA.
> There
>>> is
>>>
>>>> a
>>>>> question about which.
>>>>>
>>>>> One possibility is to do a Mobility Extension (call the messages
>>>> Sleeping
>>>>> and WakingUp) and send it within the IPsec SA between the HA and
> MN.
>>>> The
>>>>> MN
>>>>> sends the Sleeping message when it is about to go into dormant
> mode,
>>>> it
>>>>> sends the WakingUp message when it comes out again. The WakingUp
>>>> message
>>>>> isn't needed for the MN to get mobility service, it is just there
>>> for
>>>
>>>>> optimizing the SA timeouts. This would require a special API on
> the
>>> HA
>>>
>>>>> between the MIP code and IKE code for the HA to extend the IPsec
> SA
>>>>> lifetime, similar to the one for IKEv1 mobility. The solution
> would
>>>> only
>>>>> be
>>>>> applicable to Mobile IP.
>>>>>
>>>>> The other possibility is to do an IKEv2 INFORMATIONAL message
> that
>>> is
>>>
>>>> sent
>>>>> within the IKE SA. It works similarly, but there would be no need
>>> for
>>>
>>>> any
>>>>> API on the HA, since the IKE code itself would process it
> (actually,
>>> I
>>>
>>>>> proposed something like this to the Mobike WG but they didn't see
>>> the
>>>
>>>> need
>>>>> for it). This would be applicable to both Mobike and Mobile IP
> (and
>>>> any
>>>>> other security protocol that uses IKEv2, so maybe HIP as well).
>>>>>
>>>>> One question is, does the HA need to do anything else if the MN
> goes
>>>> into
>>>>> dormant mode? I think there are lots of things it could do
> (lengthen
>>>> the
>>>>> BU
>>>>> timeout, apply a filter that is either mobile specified or part
> of
>>> the
>>>
>>>>> user's service profile with the operator to only allow specific
>>>> traffic
>>>>> through, etc.) but I would really like to keep things simple.
>>>>>
>>>>>             jak
>>>>>
>>>>> ----- Original Message -----
>>>>> From: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
>>>>> To: "James Kempf" <kempf@docomolabs-usa.com>
>>>>> Cc: <mip6@ietf.org>
>>>>> Sent: Monday, July 17, 2006 3:43 PM
>>>>> Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode
> Alert
>>> to
>>>
>>>> HA?
>>>>>
>>>>>> the dormant mode extensions sounds good to me. we could do
>>>>>> this extension. one issue to consider - what triggers this
>>>>>> message? how does Mobile IP know the mobile node is going
>>>>>> into a dormant mode. if we have the trigger we should be
>>>>>> okay.
>>>>>>
>>>>>> but we have to check if this was the issue. with IKEv1 you
>>>>>> could negotiate a lifetime for the IPsec SA. IKEv2 does not
>>>>>> have the IPsec SA lifetime feature. so keepalives are
>>>>>> needed.
>>>>>>
>>>>>> James Kempf wrote:
>>>>>>> I was at Wimax Forum last week and I think I now understand
> why
>>>> they
>>>>> and
>>>>>>> 3GPP2 want to use RFC 4285 auth option rather than IPsec. One
>>> issue
>>>
>>>> -
>>>>>>> lack of EAP support for client auth - is solved by IKEv2 and
> they
>>>> seem
>>>>> to
>>>>>>> now be moving in the direction of recommending IKEv2 if people
>>> want
>>>
>>>> to
>>>>>>> deploy IPsec.
>>>>>> yes this was one of the main issues.
>>>>>>
>>>>>> the way I saw it folks in 3GPP2 liked RFC 4285 because it
>>>>>> is very similar to the MIPv4 mechanism and they were
>>>>>> comfortable with it.
>>>>>>
>>>>>> Vijay
>>>>>>
>>>>>> But the other issue is a bit more complex. 802.16, like
>>>>>>> most cellular protocols, has extensive support for dormant
> mode,
>>>> and
>>>>>>> Wimax Forum is supporting dormant mode in their network
> design.
>>> If
>>>
>>>>> IPsec
>>>>>>> is used, then there is a risk when a mobile node goes into
>>> dormant
>>>
>>>> mode
>>>>>>> that the IPsec SA may time out. It is unfortunate that this
> was
>>> not
>>>
>>>>>>> brought up when the discussion about RFC 4285 was happening,
> but
>>> I
>>>
>>>>> think
>>>>>>> this might be something that the WG could work on now as part
> of
>>>> the
>>>>> new
>>>>>>> charter. This would make IKEv2/IPsec more attractive as a
>>> security
>>>
>>>>> option
>>>>>>> for cellular operators.
>>>>>>>
>>>>>>> Comments?
>>>>>>>
>>>>>>>            jak
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Mip6 mailing list
>>>>>>> Mip6@ietf.org
>>>>>>> https://www1.ietf.org/mailman/listinfo/mip6
>>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Mip6 mailing list
>>>>> Mip6@ietf.org
>>>>> https://www1.ietf.org/mailman/listinfo/mip6
>>>>
>>>> "This email message and any attachments are confidential
> information
>>> of
>>>
>>>> Starent Networks, Corp. The information transmitted may not be used
> to
>>>> create or change any contractual obligations of Starent Networks,
>>> Corp.
>>>
>>>> Any
>>>> review, retransmission, dissemination or other use of, or taking of
>>> any
>>>
>>>> action in reliance upon this e-mail and its attachments by persons
> or
>>>> entities other than the intended recipient is prohibited. If you
> are
>>> not
>>>
>>>> the
>>>> intended recipient, please notify the sender immediately -- by
>>> replying to
>>>
>>>> this message or by sending an email to
> postmaster@starentnetworks.com
>>> --
>>>
>>>> and
>>>> destroy all copies of this message and any attachments without
> reading
>>> or
>>>
>>>> disclosing their contents. Thank you."
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Mip6 mailing list
>>>> Mip6@ietf.org
>>>> https://www1.ietf.org/mailman/listinfo/mip6
>>>
>>>
>>>
>>> _______________________________________________
>>> Mip6 mailing list
>>> Mip6@ietf.org
>>> https://www1.ietf.org/mailman/listinfo/mip6
> 


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



From mip6-bounces@ietf.org Tue Jul 18 18:11:23 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G2xml-0000u8-DQ; Tue, 18 Jul 2006 18:11:23 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G2xmk-0000u3-DR
	for mip6@ietf.org; Tue, 18 Jul 2006 18:11:22 -0400
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G2xmj-0005WP-NO
	for mip6@ietf.org; Tue, 18 Jul 2006 18:11:22 -0400
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
	k6IMBEnh010628
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Tue, 18 Jul 2006 15:11:14 -0700
Received: from NAEXBR02.na.qualcomm.com (naexbr02.qualcomm.com [10.46.92.109])
	by neophyte.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	k6IMAcHC022001; Tue, 18 Jul 2006 15:11:12 -0700 (PDT)
Received: from NAEX14.na.qualcomm.com ([10.47.5.242]) by
	NAEXBR02.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 18 Jul 2006 15:10:43 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
Date: Tue, 18 Jul 2006 15:10:43 -0700
Message-ID: <7EB20EA0938B4D42A2D82689365C9B7A0CBE2B@NAEX14.na.qualcomm.com>
In-Reply-To: <44BD5B3E.9080607@azairenet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
Thread-Index: Acaqtl8qx1y+EovdQ2GAaGOt8PwkNwAACmZw
From: "Tsirtsis, George" <tsirtsis@qualcomm.com>
To: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
X-OriginalArrivalTime: 18 Jul 2006 22:10:43.0823 (UTC)
	FILETIME=[035447F0:01C6AAB7]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: efb5d987e2484f3d9a304cc31a003441
Cc: mip6@ietf.org, James Kempf <kempf@docomolabs-usa.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Yes, I meant DPD.=20

There is a fate sharing here between MIP6 state and IPSEC state. I guess
the SA lifetime and DPD timer was introduced to catch the general case
but they do not make sense to be much different than the MIP lifetime
when that is used.

It is indeed strange, however, that IPSEC does not allow for negotiation
of these parameters. I guess people will have to use reasonable values
in each deployment depending what they are doing.

George

> -----Original Message-----
> From: Vijay Devarapalli [mailto:vijay.devarapalli@azairenet.com]
> Sent: Tuesday, July 18, 2006 6:06 PM
> To: Tsirtsis, George
> Cc: James Kempf; Chowdhury, Kuntal; mip6@ietf.org
> Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert to
HA?
>=20
> Tsirtsis, George wrote:
> > So how often PDP messages are sent is also local policy?
>=20
> I guess you meant DPD. yes it is local policy. the initiator
> and responder configure this independently.
>=20
> > In which case
> > it can be configured to a time that makes sense for MIP or a given
> > deployment scenario.
>=20
> Yes. however, the IPsec implementation should allow for
> sufficiently large values for DPD timer. but then again
> DPD exists so that unwanted IPsec state is removed if
> the other end goes down or if there is no traffic for a
> long time.
>=20
> Vijay
>=20
> > George
> >
> >> -----Original Message-----
> >> From: Vijay Devarapalli [mailto:vijay.devarapalli@azairenet.com]
> >> Sent: Tuesday, July 18, 2006 5:42 PM
> >> To: James Kempf
> >> Cc: Tsirtsis, George; Chowdhury, Kuntal; mip6@ietf.org
> >> Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert
to
> > HA?
> >> James Kempf wrote:
> >>> I don't know. What do operators typically set the SA lifetime to?
> > Though
> >>> perhaps this is an unanswerable question because, as yet, has
> > anybody
> >>> deployed MIPv6?
> >> this is more of an IPsec issue. it depends on the local policy
> >> on the initiator and responder. however, as long as there is
> >> traffic and there are responses to DPD messages, the IPsec SA
> >> is not deleted.
> >>
> >> Vijay
> >>
> >>> My only observation is that this seems to be an issue with Wimax
> > Forum,
> >>> and one of the primary motivators for wanting to use the RFC 4285
> > Auth
> >>> Option. If IETF and the MIP6 WG would like to encourage them to
use
> > IKE
> >>> (as seemed to be the sentiment when RFC 4285 was discussed, and
one
> > of
> >>> the reasons why it is not PS), it might be worthwhile to try to
> > address
> >>> their concerns.
> >>>
> >>>            jak
> >>>
> >>> ----- Original Message ----- From: "Tsirtsis, George"
> >>> <tsirtsis@qualcomm.com>
> >>> To: "James Kempf" <kempf@docomolabs-usa.com>; "Chowdhury, Kuntal"
> >>> <kchowdhury@starentnetworks.com>
> >>> Cc: <mip6@ietf.org>
> >>> Sent: Tuesday, July 18, 2006 12:10 PM
> >>> Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode
Alert
> > to
> >> HA?
> >>>
> >>> May I ask, what is the typical lifetime of the SA and what would
you
> >>> lengthen it to?
> >>> George
> >>>
> >>>> -----Original Message-----
> >>>> From: James Kempf [mailto:kempf@docomolabs-usa.com]
> >>>> Sent: Tuesday, July 18, 2006 2:43 PM
> >>>> To: Chowdhury, Kuntal
> >>>> Cc: mip6@ietf.org
> >>>> Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode
Alert
> > to
> >>> HA?
> >>>
> >>>> Kuntal,
> >>>>
> >>>> The intent is not to introduce something that the MN would send
> > during
> >>>> dormant mode. Indeed, as you have described, this would
negatively
> >>> impact
> >>>
> >>>> battery life.
> >>>>
> >>>> The intent is to provide a way for the MN to say that it is about
> > to
> >>> go
> >>>
> >>>> into
> >>>> dormant mode, so please lengthen the IPsec SA timeout to avoid
> > having
> >>> it
> >>>
> >>>> expire for some longer period of time.
> >>>>
> >>>>             jak
> >>>>
> >>>> ----- Original Message -----
> >>>> From: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
> >>>> To: "James Kempf" <kempf@docomolabs-usa.com>
> >>>> Cc: <mip6@ietf.org>
> >>>> Sent: Tuesday, July 18, 2006 11:20 AM
> >>>> Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode
Alert
> > to
> >>> HA?
> >>>
> >>>>
> >>>> James,
> >>>>
> >>>> This is a good discussion. Indeed the need for IPsec keepalives
(or
> >>> DPD)
> >>>
> >>>> over the air when the MN is dormant (or idle) is an issue in the
> >>>> cellular networks. The issue is Not that there are no mip6
messages
> >>>> defined or the HA is not aware of dormancy. It is more of a
paging
> >>>> channel capacity issue, MN's battery life issue and the signaling
> >>>> overhead to transport the keepalives for a dormant MN issue.
> >>>>
> >>>> So, any new message however small won't solve the problem, IMHO.
> >>>>
> >>>> -Kuntal
> >>>>
> >>>>
> >>>>> -----Original Message-----
> >>>>> From: James Kempf [mailto:kempf@docomolabs-usa.com]
> >>>>> Sent: Tuesday, July 18, 2006 11:17 AM
> >>>>> To: Vijay Devarapalli
> >>>>> Cc: mip6@ietf.org
> >>>>> Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode
> > Alert
> >>> to
> >>>
> >>>> HA?
> >>>>> For security, the message would need to be sent within an SA.
> > There
> >>> is
> >>>
> >>>> a
> >>>>> question about which.
> >>>>>
> >>>>> One possibility is to do a Mobility Extension (call the messages
> >>>> Sleeping
> >>>>> and WakingUp) and send it within the IPsec SA between the HA and
> > MN.
> >>>> The
> >>>>> MN
> >>>>> sends the Sleeping message when it is about to go into dormant
> > mode,
> >>>> it
> >>>>> sends the WakingUp message when it comes out again. The WakingUp
> >>>> message
> >>>>> isn't needed for the MN to get mobility service, it is just
there
> >>> for
> >>>
> >>>>> optimizing the SA timeouts. This would require a special API on
> > the
> >>> HA
> >>>
> >>>>> between the MIP code and IKE code for the HA to extend the IPsec
> > SA
> >>>>> lifetime, similar to the one for IKEv1 mobility. The solution
> > would
> >>>> only
> >>>>> be
> >>>>> applicable to Mobile IP.
> >>>>>
> >>>>> The other possibility is to do an IKEv2 INFORMATIONAL message
> > that
> >>> is
> >>>
> >>>> sent
> >>>>> within the IKE SA. It works similarly, but there would be no
need
> >>> for
> >>>
> >>>> any
> >>>>> API on the HA, since the IKE code itself would process it
> > (actually,
> >>> I
> >>>
> >>>>> proposed something like this to the Mobike WG but they didn't
see
> >>> the
> >>>
> >>>> need
> >>>>> for it). This would be applicable to both Mobike and Mobile IP
> > (and
> >>>> any
> >>>>> other security protocol that uses IKEv2, so maybe HIP as well).
> >>>>>
> >>>>> One question is, does the HA need to do anything else if the MN
> > goes
> >>>> into
> >>>>> dormant mode? I think there are lots of things it could do
> > (lengthen
> >>>> the
> >>>>> BU
> >>>>> timeout, apply a filter that is either mobile specified or part
> > of
> >>> the
> >>>
> >>>>> user's service profile with the operator to only allow specific
> >>>> traffic
> >>>>> through, etc.) but I would really like to keep things simple.
> >>>>>
> >>>>>             jak
> >>>>>
> >>>>> ----- Original Message -----
> >>>>> From: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
> >>>>> To: "James Kempf" <kempf@docomolabs-usa.com>
> >>>>> Cc: <mip6@ietf.org>
> >>>>> Sent: Monday, July 17, 2006 3:43 PM
> >>>>> Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode
> > Alert
> >>> to
> >>>
> >>>> HA?
> >>>>>
> >>>>>> the dormant mode extensions sounds good to me. we could do
> >>>>>> this extension. one issue to consider - what triggers this
> >>>>>> message? how does Mobile IP know the mobile node is going
> >>>>>> into a dormant mode. if we have the trigger we should be
> >>>>>> okay.
> >>>>>>
> >>>>>> but we have to check if this was the issue. with IKEv1 you
> >>>>>> could negotiate a lifetime for the IPsec SA. IKEv2 does not
> >>>>>> have the IPsec SA lifetime feature. so keepalives are
> >>>>>> needed.
> >>>>>>
> >>>>>> James Kempf wrote:
> >>>>>>> I was at Wimax Forum last week and I think I now understand
> > why
> >>>> they
> >>>>> and
> >>>>>>> 3GPP2 want to use RFC 4285 auth option rather than IPsec. One
> >>> issue
> >>>
> >>>> -
> >>>>>>> lack of EAP support for client auth - is solved by IKEv2 and
> > they
> >>>> seem
> >>>>> to
> >>>>>>> now be moving in the direction of recommending IKEv2 if people
> >>> want
> >>>
> >>>> to
> >>>>>>> deploy IPsec.
> >>>>>> yes this was one of the main issues.
> >>>>>>
> >>>>>> the way I saw it folks in 3GPP2 liked RFC 4285 because it
> >>>>>> is very similar to the MIPv4 mechanism and they were
> >>>>>> comfortable with it.
> >>>>>>
> >>>>>> Vijay
> >>>>>>
> >>>>>> But the other issue is a bit more complex. 802.16, like
> >>>>>>> most cellular protocols, has extensive support for dormant
> > mode,
> >>>> and
> >>>>>>> Wimax Forum is supporting dormant mode in their network
> > design.
> >>> If
> >>>
> >>>>> IPsec
> >>>>>>> is used, then there is a risk when a mobile node goes into
> >>> dormant
> >>>
> >>>> mode
> >>>>>>> that the IPsec SA may time out. It is unfortunate that this
> > was
> >>> not
> >>>
> >>>>>>> brought up when the discussion about RFC 4285 was happening,
> > but
> >>> I
> >>>
> >>>>> think
> >>>>>>> this might be something that the WG could work on now as part
> > of
> >>>> the
> >>>>> new
> >>>>>>> charter. This would make IKEv2/IPsec more attractive as a
> >>> security
> >>>
> >>>>> option
> >>>>>>> for cellular operators.
> >>>>>>>
> >>>>>>> Comments?
> >>>>>>>
> >>>>>>>            jak
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> _______________________________________________
> >>>>>>> Mip6 mailing list
> >>>>>>> Mip6@ietf.org
> >>>>>>> https://www1.ietf.org/mailman/listinfo/mip6
> >>>>>>
> >>>>>
> >>>>>
> >>>>> _______________________________________________
> >>>>> Mip6 mailing list
> >>>>> Mip6@ietf.org
> >>>>> https://www1.ietf.org/mailman/listinfo/mip6
> >>>>
> >>>> "This email message and any attachments are confidential
> > information
> >>> of
> >>>
> >>>> Starent Networks, Corp. The information transmitted may not be
used
> > to
> >>>> create or change any contractual obligations of Starent Networks,
> >>> Corp.
> >>>
> >>>> Any
> >>>> review, retransmission, dissemination or other use of, or taking
of
> >>> any
> >>>
> >>>> action in reliance upon this e-mail and its attachments by
persons
> > or
> >>>> entities other than the intended recipient is prohibited. If you
> > are
> >>> not
> >>>
> >>>> the
> >>>> intended recipient, please notify the sender immediately -- by
> >>> replying to
> >>>
> >>>> this message or by sending an email to
> > postmaster@starentnetworks.com
> >>> --
> >>>
> >>>> and
> >>>> destroy all copies of this message and any attachments without
> > reading
> >>> or
> >>>
> >>>> disclosing their contents. Thank you."
> >>>>
> >>>>
> >>>>
> >>>> _______________________________________________
> >>>> Mip6 mailing list
> >>>> Mip6@ietf.org
> >>>> https://www1.ietf.org/mailman/listinfo/mip6
> >>>
> >>>
> >>>
> >>> _______________________________________________
> >>> Mip6 mailing list
> >>> Mip6@ietf.org
> >>> https://www1.ietf.org/mailman/listinfo/mip6
> >


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



From mip6-bounces@ietf.org Tue Jul 18 18:49:07 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G2yNG-0005lu-Ao; Tue, 18 Jul 2006 18:49:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G2yNE-0005lp-Np
	for mip6@ietf.org; Tue, 18 Jul 2006 18:49:04 -0400
Received: from mout.perfora.net ([217.160.230.41])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G2yND-0006ni-HE
	for mip6@ietf.org; Tue, 18 Jul 2006 18:49:04 -0400
Received: from [207.62.247.10] (helo=IBM52A5038A94F)
	by mrelay.perfora.net (node=mrelayus1) with ESMTP (Nemesis),
	id 0MKp2t-1G2yNA0sVT-00042Y; Tue, 18 Jul 2006 18:49:02 -0400
From: "Alper Yegin" <alper.yegin@yegin.org>
To: "'Jean-Michel Combes'" <jeanmichel.combes@gmail.com>,
	"'Mobile IPv6 Mailing List'" <mip6@ietf.org>
Subject: RE: [Mip6] New charter item: HA assignment
Date: Tue, 18 Jul 2006 15:48:57 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
Thread-Index: AcaqXbJ/HSKTj8yYTIeBwOl05qpv9wAXlm7Q
In-Reply-To: <729b68be0607180431m773dc847qed3e7350819a8d04@mail.gmail.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
Message-ID: <0MKp2t-1G2yNA0sVT-00042Y@mrelay.perfora.net>
X-Provags-ID: perfora.net abuse@perfora.net
	login:abf7a4bb310ea4dfc9b6841113e2970f
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Cc: 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi JMC,

In the split scenario, DHCP can be used for HA assignment when the ASP and
the MSP are the same. 

Alper


> -----Original Message-----
> From: Jean-Michel Combes [mailto:jeanmichel.combes@gmail.com]
> Sent: Tuesday, July 18, 2006 4:31 AM
> To: Mobile IPv6 Mailing List
> Subject: [Mip6] New charter item: HA assignment
> 
> Hi,
> 
> as promised during the mip6 session, here is a point which, IMO, is
> important from a MSP's point of view:
> Actually, the bootstrapping solution, in the split scenario, only
> propose a HA discovery mechanism (i.e. the MN receives a list of HA,
> from DNS, and chooses one of them). The MSP has no easy solution to
> enforce one MN to have a specific HA.
> 
> Best regards.
> 
> JMC.
> 
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6


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



From mip6-bounces@ietf.org Tue Jul 18 19:26:43 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G2yxe-0002De-0a; Tue, 18 Jul 2006 19:26:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G2yxc-0002DZ-Tt
	for mip6@ietf.org; Tue, 18 Jul 2006 19:26:40 -0400
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G2yxc-0000Qt-5e
	for mip6@ietf.org; Tue, 18 Jul 2006 19:26:40 -0400
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
	k6INQYBf024217
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Tue, 18 Jul 2006 16:26:35 -0700
Received: from NAEXBR02.na.qualcomm.com (naexbr02.qualcomm.com [10.46.92.109])
	by neophyte.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	k6INPwui021257; Tue, 18 Jul 2006 16:26:34 -0700 (PDT)
Received: from NAEX13.na.qualcomm.com ([129.46.51.248]) by
	NAEXBR02.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 18 Jul 2006 16:26:33 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
Date: Tue, 18 Jul 2006 16:26:31 -0700
Message-ID: <C24CB51D5AA800449982D9BCB90325130A11E4@NAEX13.na.qualcomm.com>
In-Reply-To: <7EB20EA0938B4D42A2D82689365C9B7A0CBE2B@NAEX14.na.qualcomm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
Thread-Index: Acaqtl8qx1y+EovdQ2GAaGOt8PwkNwAACmZwAAKxUdA=
From: "Narayanan, Vidya" <vidyan@qualcomm.com>
To: "Tsirtsis, George" <tsirtsis@qualcomm.com>,
	"Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
X-OriginalArrivalTime: 18 Jul 2006 23:26:33.0482 (UTC)
	FILETIME=[9B2326A0:01C6AAC1]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 054490fec19f6a94c68e63428d06db69
Cc: mip6@ietf.org, James Kempf <kempf@docomolabs-usa.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

I'm just catching up with this discussion.=20

If the IPsec idle timer is at least equal to the BU lifetime, why is
there a need for any other signaling related to dormant mode? Given that
the timer values are a matter of policy, this should be do-able.=20

Vidya

> -----Original Message-----
> From: Tsirtsis, George [mailto:tsirtsis@qualcomm.com]=20
> Sent: Tuesday, July 18, 2006 3:11 PM
> To: Vijay Devarapalli
> Cc: mip6@ietf.org; James Kempf
> Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode=20
> Alert to HA?
>=20
> Yes, I meant DPD.=20
>=20
> There is a fate sharing here between MIP6 state and IPSEC=20
> state. I guess the SA lifetime and DPD timer was introduced=20
> to catch the general case but they do not make sense to be=20
> much different than the MIP lifetime when that is used.
>=20
> It is indeed strange, however, that IPSEC does not allow for=20
> negotiation of these parameters. I guess people will have to=20
> use reasonable values in each deployment depending what they=20
> are doing.
>=20
> George
>=20
> > -----Original Message-----
> > From: Vijay Devarapalli [mailto:vijay.devarapalli@azairenet.com]
> > Sent: Tuesday, July 18, 2006 6:06 PM
> > To: Tsirtsis, George
> > Cc: James Kempf; Chowdhury, Kuntal; mip6@ietf.org
> > Subject: Re: [Mip6] New Charter Item:Support for Dormant=20
> Mode Alert to
> HA?
> >=20
> > Tsirtsis, George wrote:
> > > So how often PDP messages are sent is also local policy?
> >=20
> > I guess you meant DPD. yes it is local policy. the initiator and=20
> > responder configure this independently.
> >=20
> > > In which case
> > > it can be configured to a time that makes sense for MIP=20
> or a given=20
> > > deployment scenario.
> >=20
> > Yes. however, the IPsec implementation should allow for=20
> sufficiently=20
> > large values for DPD timer. but then again DPD exists so=20
> that unwanted=20
> > IPsec state is removed if the other end goes down or if there is no=20
> > traffic for a long time.
> >=20
> > Vijay
> >=20
> > > George
> > >
> > >> -----Original Message-----
> > >> From: Vijay Devarapalli [mailto:vijay.devarapalli@azairenet.com]
> > >> Sent: Tuesday, July 18, 2006 5:42 PM
> > >> To: James Kempf
> > >> Cc: Tsirtsis, George; Chowdhury, Kuntal; mip6@ietf.org
> > >> Subject: Re: [Mip6] New Charter Item:Support for Dormant=20
> Mode Alert
> to
> > > HA?
> > >> James Kempf wrote:
> > >>> I don't know. What do operators typically set the SA=20
> lifetime to?
> > > Though
> > >>> perhaps this is an unanswerable question because, as yet, has
> > > anybody
> > >>> deployed MIPv6?
> > >> this is more of an IPsec issue. it depends on the local=20
> policy on=20
> > >> the initiator and responder. however, as long as there=20
> is traffic=20
> > >> and there are responses to DPD messages, the IPsec SA is not=20
> > >> deleted.
> > >>
> > >> Vijay
> > >>
> > >>> My only observation is that this seems to be an issue with Wimax
> > > Forum,
> > >>> and one of the primary motivators for wanting to use=20
> the RFC 4285
> > > Auth
> > >>> Option. If IETF and the MIP6 WG would like to encourage them to
> use
> > > IKE
> > >>> (as seemed to be the sentiment when RFC 4285 was discussed, and
> one
> > > of
> > >>> the reasons why it is not PS), it might be worthwhile to try to
> > > address
> > >>> their concerns.
> > >>>
> > >>>            jak
> > >>>
> > >>> ----- Original Message ----- From: "Tsirtsis, George"
> > >>> <tsirtsis@qualcomm.com>
> > >>> To: "James Kempf" <kempf@docomolabs-usa.com>;=20
> "Chowdhury, Kuntal"
> > >>> <kchowdhury@starentnetworks.com>
> > >>> Cc: <mip6@ietf.org>
> > >>> Sent: Tuesday, July 18, 2006 12:10 PM
> > >>> Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode
> Alert
> > > to
> > >> HA?
> > >>>
> > >>> May I ask, what is the typical lifetime of the SA and what would
> you
> > >>> lengthen it to?
> > >>> George
> > >>>
> > >>>> -----Original Message-----
> > >>>> From: James Kempf [mailto:kempf@docomolabs-usa.com]
> > >>>> Sent: Tuesday, July 18, 2006 2:43 PM
> > >>>> To: Chowdhury, Kuntal
> > >>>> Cc: mip6@ietf.org
> > >>>> Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode
> Alert
> > > to
> > >>> HA?
> > >>>
> > >>>> Kuntal,
> > >>>>
> > >>>> The intent is not to introduce something that the MN would send
> > > during
> > >>>> dormant mode. Indeed, as you have described, this would
> negatively
> > >>> impact
> > >>>
> > >>>> battery life.
> > >>>>
> > >>>> The intent is to provide a way for the MN to say that=20
> it is about
> > > to
> > >>> go
> > >>>
> > >>>> into
> > >>>> dormant mode, so please lengthen the IPsec SA timeout to avoid
> > > having
> > >>> it
> > >>>
> > >>>> expire for some longer period of time.
> > >>>>
> > >>>>             jak
> > >>>>
> > >>>> ----- Original Message -----
> > >>>> From: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
> > >>>> To: "James Kempf" <kempf@docomolabs-usa.com>
> > >>>> Cc: <mip6@ietf.org>
> > >>>> Sent: Tuesday, July 18, 2006 11:20 AM
> > >>>> Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode
> Alert
> > > to
> > >>> HA?
> > >>>
> > >>>>
> > >>>> James,
> > >>>>
> > >>>> This is a good discussion. Indeed the need for IPsec keepalives
> (or
> > >>> DPD)
> > >>>
> > >>>> over the air when the MN is dormant (or idle) is an=20
> issue in the=20
> > >>>> cellular networks. The issue is Not that there are no mip6
> messages
> > >>>> defined or the HA is not aware of dormancy. It is more of a
> paging
> > >>>> channel capacity issue, MN's battery life issue and=20
> the signaling=20
> > >>>> overhead to transport the keepalives for a dormant MN issue.
> > >>>>
> > >>>> So, any new message however small won't solve the=20
> problem, IMHO.
> > >>>>
> > >>>> -Kuntal
> > >>>>
> > >>>>
> > >>>>> -----Original Message-----
> > >>>>> From: James Kempf [mailto:kempf@docomolabs-usa.com]
> > >>>>> Sent: Tuesday, July 18, 2006 11:17 AM
> > >>>>> To: Vijay Devarapalli
> > >>>>> Cc: mip6@ietf.org
> > >>>>> Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode
> > > Alert
> > >>> to
> > >>>
> > >>>> HA?
> > >>>>> For security, the message would need to be sent within an SA.
> > > There
> > >>> is
> > >>>
> > >>>> a
> > >>>>> question about which.
> > >>>>>
> > >>>>> One possibility is to do a Mobility Extension (call=20
> the messages
> > >>>> Sleeping
> > >>>>> and WakingUp) and send it within the IPsec SA between=20
> the HA and
> > > MN.
> > >>>> The
> > >>>>> MN
> > >>>>> sends the Sleeping message when it is about to go into dormant
> > > mode,
> > >>>> it
> > >>>>> sends the WakingUp message when it comes out again.=20
> The WakingUp
> > >>>> message
> > >>>>> isn't needed for the MN to get mobility service, it is just
> there
> > >>> for
> > >>>
> > >>>>> optimizing the SA timeouts. This would require a=20
> special API on
> > > the
> > >>> HA
> > >>>
> > >>>>> between the MIP code and IKE code for the HA to=20
> extend the IPsec
> > > SA
> > >>>>> lifetime, similar to the one for IKEv1 mobility. The solution
> > > would
> > >>>> only
> > >>>>> be
> > >>>>> applicable to Mobile IP.
> > >>>>>
> > >>>>> The other possibility is to do an IKEv2 INFORMATIONAL message
> > > that
> > >>> is
> > >>>
> > >>>> sent
> > >>>>> within the IKE SA. It works similarly, but there would be no
> need
> > >>> for
> > >>>
> > >>>> any
> > >>>>> API on the HA, since the IKE code itself would process it
> > > (actually,
> > >>> I
> > >>>
> > >>>>> proposed something like this to the Mobike WG but they didn't
> see
> > >>> the
> > >>>
> > >>>> need
> > >>>>> for it). This would be applicable to both Mobike and Mobile IP
> > > (and
> > >>>> any
> > >>>>> other security protocol that uses IKEv2, so maybe HIP=20
> as well).
> > >>>>>
> > >>>>> One question is, does the HA need to do anything else=20
> if the MN
> > > goes
> > >>>> into
> > >>>>> dormant mode? I think there are lots of things it could do
> > > (lengthen
> > >>>> the
> > >>>>> BU
> > >>>>> timeout, apply a filter that is either mobile=20
> specified or part
> > > of
> > >>> the
> > >>>
> > >>>>> user's service profile with the operator to only=20
> allow specific
> > >>>> traffic
> > >>>>> through, etc.) but I would really like to keep things simple.
> > >>>>>
> > >>>>>             jak
> > >>>>>
> > >>>>> ----- Original Message -----
> > >>>>> From: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
> > >>>>> To: "James Kempf" <kempf@docomolabs-usa.com>
> > >>>>> Cc: <mip6@ietf.org>
> > >>>>> Sent: Monday, July 17, 2006 3:43 PM
> > >>>>> Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode
> > > Alert
> > >>> to
> > >>>
> > >>>> HA?
> > >>>>>
> > >>>>>> the dormant mode extensions sounds good to me. we=20
> could do this=20
> > >>>>>> extension. one issue to consider - what triggers=20
> this message?=20
> > >>>>>> how does Mobile IP know the mobile node is going=20
> into a dormant=20
> > >>>>>> mode. if we have the trigger we should be okay.
> > >>>>>>
> > >>>>>> but we have to check if this was the issue. with IKEv1 you=20
> > >>>>>> could negotiate a lifetime for the IPsec SA. IKEv2 does not=20
> > >>>>>> have the IPsec SA lifetime feature. so keepalives are needed.
> > >>>>>>
> > >>>>>> James Kempf wrote:
> > >>>>>>> I was at Wimax Forum last week and I think I now understand
> > > why
> > >>>> they
> > >>>>> and
> > >>>>>>> 3GPP2 want to use RFC 4285 auth option rather than=20
> IPsec. One
> > >>> issue
> > >>>
> > >>>> -
> > >>>>>>> lack of EAP support for client auth - is solved by IKEv2 and
> > > they
> > >>>> seem
> > >>>>> to
> > >>>>>>> now be moving in the direction of recommending=20
> IKEv2 if people
> > >>> want
> > >>>
> > >>>> to
> > >>>>>>> deploy IPsec.
> > >>>>>> yes this was one of the main issues.
> > >>>>>>
> > >>>>>> the way I saw it folks in 3GPP2 liked RFC 4285 because it is=20
> > >>>>>> very similar to the MIPv4 mechanism and they were=20
> comfortable=20
> > >>>>>> with it.
> > >>>>>>
> > >>>>>> Vijay
> > >>>>>>
> > >>>>>> But the other issue is a bit more complex. 802.16, like
> > >>>>>>> most cellular protocols, has extensive support for dormant
> > > mode,
> > >>>> and
> > >>>>>>> Wimax Forum is supporting dormant mode in their network
> > > design.
> > >>> If
> > >>>
> > >>>>> IPsec
> > >>>>>>> is used, then there is a risk when a mobile node goes into
> > >>> dormant
> > >>>
> > >>>> mode
> > >>>>>>> that the IPsec SA may time out. It is unfortunate that this
> > > was
> > >>> not
> > >>>
> > >>>>>>> brought up when the discussion about RFC 4285 was happening,
> > > but
> > >>> I
> > >>>
> > >>>>> think
> > >>>>>>> this might be something that the WG could work on=20
> now as part
> > > of
> > >>>> the
> > >>>>> new
> > >>>>>>> charter. This would make IKEv2/IPsec more attractive as a
> > >>> security
> > >>>
> > >>>>> option
> > >>>>>>> for cellular operators.
> > >>>>>>>
> > >>>>>>> Comments?
> > >>>>>>>
> > >>>>>>>            jak
> > >>>>>>>
> > >>>>>>>
> > >>>>>>>
> > >>>>>>> _______________________________________________
> > >>>>>>> Mip6 mailing list
> > >>>>>>> Mip6@ietf.org
> > >>>>>>> https://www1.ietf.org/mailman/listinfo/mip6
> > >>>>>>
> > >>>>>
> > >>>>>
> > >>>>> _______________________________________________
> > >>>>> Mip6 mailing list
> > >>>>> Mip6@ietf.org
> > >>>>> https://www1.ietf.org/mailman/listinfo/mip6
> > >>>>
> > >>>> "This email message and any attachments are confidential
> > > information
> > >>> of
> > >>>
> > >>>> Starent Networks, Corp. The information transmitted may not be
> used
> > > to
> > >>>> create or change any contractual obligations of=20
> Starent Networks,
> > >>> Corp.
> > >>>
> > >>>> Any
> > >>>> review, retransmission, dissemination or other use of,=20
> or taking
> of
> > >>> any
> > >>>
> > >>>> action in reliance upon this e-mail and its attachments by
> persons
> > > or
> > >>>> entities other than the intended recipient is=20
> prohibited. If you
> > > are
> > >>> not
> > >>>
> > >>>> the
> > >>>> intended recipient, please notify the sender immediately -- by
> > >>> replying to
> > >>>
> > >>>> this message or by sending an email to
> > > postmaster@starentnetworks.com
> > >>> --
> > >>>
> > >>>> and
> > >>>> destroy all copies of this message and any attachments without
> > > reading
> > >>> or
> > >>>
> > >>>> disclosing their contents. Thank you."
> > >>>>
> > >>>>
> > >>>>
> > >>>> _______________________________________________
> > >>>> Mip6 mailing list
> > >>>> Mip6@ietf.org
> > >>>> https://www1.ietf.org/mailman/listinfo/mip6
> > >>>
> > >>>
> > >>>
> > >>> _______________________________________________
> > >>> Mip6 mailing list
> > >>> Mip6@ietf.org
> > >>> https://www1.ietf.org/mailman/listinfo/mip6
> > >
>=20
>=20
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
>=20

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



From mip6-bounces@ietf.org Wed Jul 19 04:15:09 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G37Cu-0008Ct-Nw; Wed, 19 Jul 2006 04:15:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G37Cs-0008Co-Rm
	for mip6@ietf.org; Wed, 19 Jul 2006 04:14:58 -0400
Received: from cluster-d.mailcontrol.com ([217.69.20.190])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G37Cq-0002dN-9o
	for mip6@ietf.org; Wed, 19 Jul 2006 04:14:58 -0400
Received: from hhe500-02.hbg.de.pan.eu (gate.eu.panasonic.com [194.173.20.12])
	by rly34d.srv.mailcontrol.com (MailControl) with SMTP id
	k6J8ErDK020366 for <mip6@ietf.org>; Wed, 19 Jul 2006 09:14:53 +0100
Received: from eundadmi01.pan.eu(10.100.96.64) by hhe500-02.hbg.de.pan.eu via
	smtp id 269a_5414d4c6_16f9_11db_94cc_0030482aac25;
	Wed, 19 Jul 2006 09:36:44 +0200
Received: from VPN-MRelay-01.PRDCG.Panasonic.de ([10.100.176.55])
	by eundadmi01.pan.eu (Lotus Domino Release 6.5.2)
	with ESMTP id 2006071910144530-1145248 ;
	Wed, 19 Jul 2006 10:14:45 +0200 
X-Spam-Status: No, hits=0.0 required=6.5
	tests=ALL_TRUSTED: -2.867,AWL: 0.667,BAYES_00: -1.665,
	SARE_RECV_ADDR: 0.027
X-Spam-Level: 
Received: from localhost ([127.0.0.1]) by VPN-MRelay-01.PRDCG.Panasonic.de
	for mip6@ietf.org; Wed, 19 Jul 2006 10:18:25 +0200
Subject: RE: [Mip6] New charter item: HA assignment
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.5
In-reply-to: <02fc01c6aa99$de869d00$196115ac@dcml.docomolabsusa.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] New charter item: HA assignment
Thread-Index: AcaqnuENMqTBn5ziQrepX9vUM9hGwQAa3PuQ
To: <mip6@ietf.org>
Message-ID: <4D2F935F08D41A4C8866693F4F0D7C4FD44CE2@lan-ex-01.panasonic.de>
Date: Wed, 19 Jul 2006 10:14:38 +0200
From: "Kilian Weniger" <Kilian.Weniger@eu.panasonic.com>
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Content-Type: text/plain;
	charset="us-ascii"
X-Scanned-By: MailControl A-07-00-10 (www.mailcontrol.com) on 10.68.0.144
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 03169bfe4792634a390035a01a6c6d2f
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Another possible solution is described in
draft-dupont-ikev2-haassign-01.txt. The MN sends the IKE_SA_INIT to an
anycast HA address and let the anycast receiver forward the message to
the "best" HA. In this case, the "best" HA may be different for every MN
and would be selected based on the source address of the IKE_SA_INIT.

-Kilian

> -----Original Message-----
> From: James Kempf [mailto:kempf@docomolabs-usa.com]=20
> Sent: Dienstag, 18. Juli 2006 20:42
> To: Alexandru Petrescu; Jean-Michel Combes
> Cc: Mobile IPv6 Mailing List
> Subject: Re: [Mip6] New charter item: HA assignment
>=20
> So there are three ways I can think of that one could go=20
> about assigning an=20
> HA.
>=20
> 1) The MN uses the weights returned with the DNS SRV record=20
> from RFC 2782 to=20
> guide its selection of HAs. Less preferred HAs are later in=20
> the preference=20
> ordering. The authors of RFC 2782 complain about weights=20
> being a relatively=20
> coarse-grained mechanism that isn't up to providing dynamic=20
> load balancing.=20
> I think the time granularity of the SRV updates would  be=20
> about 15 seconds=20
> minimum, if dynamic DNS is used, since I'm told that is about=20
> the amount of=20
> time one should expect it to take for a dynamic DNS update to=20
> propagate.
>=20
> 2) For a more dynamic mechanism, the HA initially tried by=20
> the MN can turn=20
> down the MN's request to perform IKEv2. Or the HA could deny=20
> the MN an HoA.=20
> This would cause the MN to roll over to the next HA on the=20
> list. When the MN=20
> hit the right HA, the IKEv2 transaction would succeed. This has the=20
> disadvantage that it increases the amount of time the MN=20
> needs to bootstrap.
>=20
> 3) Immediately after the MN finishes the IKEv2 transaction,=20
> the first HA=20
> could send a HA Switch message=20
> (draft-ietf-mip6-ha-switch-00.txt) within the=20
> IPsec SA, telling the MN to go elsewhere. The MN would be=20
> delayed  by the=20
> amount of time needed to do the IKEv2 transaction, but that=20
> does provide=20
> security. This seems like it would be the most direct way.
>=20
> I think a combination of these three mechanisms would be=20
> sufficient to=20
> provide HA assignment for the kinds of deployment scenerios=20
> that the split=20
> scenerio was designed to accommodate. The first mechanism=20
> would provide load=20
> balancing over longer periods while the second would provide=20
> support for=20
> fast transients, and the third would provide a way to=20
> directly and securely=20
> tell an MN where to go. Ideally, the MN wouldn't have to go=20
> through more=20
> than one additional HA before it got service, reducing the=20
> amount of lag.
>=20
> On the other hand, if you want a way to say "thou shalt use=20
> this HA" without=20
> a lot of initial negotiation, then I'd suggest using the intergrated=20
> scenerio and simply let DHCP assign the MN to an HA (though=20
> that would=20
> require DHCP security).
>=20
> If these are insufficient, then the only other suggestion is=20
> that an IKEv2=20
> INFORMATIONAL message be defined directing the MN to try=20
> IKEv2 with another=20
> node (which would be the preferred HA). Such a message could=20
> be used for VPN=20
> server load balancing too.
>=20
>             jak
>=20
>=20
>=20
>=20
>=20
>=20
> ----- Original Message -----=20
> From: "Alexandru Petrescu" <alexandru.petrescu@motorola.com>
> To: "Jean-Michel Combes" <jeanmichel.combes@gmail.com>
> Cc: "Mobile IPv6 Mailing List" <mip6@ietf.org>
> Sent: Tuesday, July 18, 2006 9:49 AM
> Subject: Re: [Mip6] New charter item: HA assignment
>=20
>=20
> > Jean-Michel Combes wrote:
> >> Hi,
> >>
> >> as promised during the mip6 session, here is a point=20
> which, IMO, is=20
> >> important from a MSP's point of view: Actually, the bootstrapping=20
> >> solution, in the split scenario, only propose a HA=20
> discovery mechanism=20
> >> (i.e. the MN receives a list of HA, from DNS, and chooses=20
> one of them).=20
> >> The MSP has no easy solution to enforce one MN to have a=20
> specific HA.
> >
> > One possible way is for a HA to stop sending BAck, at which=20
> point an MN
> > would send DHAAD Request again, and a different HA replies=20
> back DHAAD,
> > so end result is MN is assigned a new HA.
> >
> > Another way is for the new HA to send Binding Refresh Request to MN
> > (even if it has no BC entry for it).
> >
> > Another way, if the split bootstrapping advances, is for the MSP to
> > dynamically update the DNS data about HAs, so when MN bootstraps it
> > obtains a different HA.
> >
> > If the HA address is discovered with DHCP then I think the=20
> DHCP Server
> > can send specific messages to MN (unsolicited by MN).
> >
> > It would require relaxing some language in rfc 3775 and=20
> probably extending=20
> > BRR.
> >
> > It would be helpful to know when would an MSP like the MN=20
> to choose a
> > different HA, for what reasons.
> >
> > Alex
> >
> >
> > _______________________________________________
> > Mip6 mailing list
> > Mip6@ietf.org
> > https://www1.ietf.org/mailman/listinfo/mip6
> >=20
>=20
>=20
>=20
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
>=20
>=20


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



From mip6-bounces@ietf.org Wed Jul 19 04:39:03 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G37a6-0001DZ-Ba; Wed, 19 Jul 2006 04:38:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G37a4-0001DR-Sx
	for mip6@ietf.org; Wed, 19 Jul 2006 04:38:56 -0400
Received: from nf-out-0910.google.com ([64.233.182.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G37a4-0004rN-9B
	for mip6@ietf.org; Wed, 19 Jul 2006 04:38:56 -0400
Received: by nf-out-0910.google.com with SMTP id n15so187995nfc
	for <mip6@ietf.org>; Wed, 19 Jul 2006 01:38:55 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=YtkmMZ5QYvrDmbyIun4i/8OARDbP0oFKfipyALNAy9qBIzQEaQ7wWmKiA/WnBBk7bsD4opSJPNKssvCMyCj0d/jWci7loYxW7XPLmL4SMnokvAYJd7EONzh4eds1wzFn5BSD0U+nVIY7MUKQIyglWM7+P/9ZaKVOBgvUQIsvQgw=
Received: by 10.48.220.15 with SMTP id s15mr1438457nfg;
	Wed, 19 Jul 2006 01:38:55 -0700 (PDT)
Received: by 10.49.40.6 with HTTP; Wed, 19 Jul 2006 01:38:55 -0700 (PDT)
Message-ID: <eaa74a7e0607190138j79868bd3u48371dbcb8673fcb@mail.gmail.com>
Date: Wed, 19 Jul 2006 10:38:55 +0200
From: "Gerardo Giaretta" <gerardo.giaretta@gmail.com>
To: "Tsirtsis, George" <tsirtsis@qualcomm.com>, 
	"James Kempf" <kempf@docomolabs-usa.com>
Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
In-Reply-To: <7EB20EA0938B4D42A2D82689365C9B7A0CBDEE@NAEX14.na.qualcomm.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <033201c6aaa1$787be580$196115ac@dcml.docomolabsusa.com>
	<7EB20EA0938B4D42A2D82689365C9B7A0CBDEE@NAEX14.na.qualcomm.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3b8eea209b62bd15620865bc4fbef8cd
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

This problem applies also to the 3GPP I-WLAN in case the access
network (that may be any non-3GPP access network and not only WLAN,
despite of the name) supports dormant mode. I agree it is an important
issue to study.

I think there are two issues here:

- one is the SA lifetime. This is really an IKE/IPsec issue and should
be handled in IPsec (concluded) WG. As mentioned, this issue does not
apply only to MIP6; in 3GPP I-WLAN the MN has an IPsec tunnel with the
PDG and if the access network supports dormant mode, the MN cannot go
into dormant mode state in order to keep the SA up. I guess it may
apply also to MOBIKE.

- another issue is the lifetime of the BCE. It seems not acceptable
that the MN needs to go back to active state in order to send a
refresh BU to the HA. For this issue, an extension to MIP6, similar to
the one proposed by James, may make sense.

--Gerardo


On 7/18/06, Tsirtsis, George <tsirtsis@qualcomm.com> wrote:
> I guess the important thing is to understand how the typical SA lifetime
> relates to the typical MIP6 Binding Lifetime. The MN will have to at
> least wake up to refresh its binding.
>
> George
>
> > -----Original Message-----
> > From: James Kempf [mailto:kempf@docomolabs-usa.com]
> > Sent: Tuesday, July 18, 2006 3:37 PM
> > To: Tsirtsis, George; Chowdhury, Kuntal
> > Cc: mip6@ietf.org
> > Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert to
> HA?
> >
> > I don't know. What do operators typically set the SA lifetime to?
> Though
> > perhaps this is an unanswerable question because, as yet, has anybody
> > deployed MIPv6?
> >
> > My only observation is that this seems to be an issue with Wimax
> Forum,
> > and
> > one of the primary motivators for wanting to use the RFC 4285 Auth
> Option.
> > If IETF and the MIP6 WG would like to encourage them to use IKE (as
> seemed
> > to be the sentiment when RFC 4285 was discussed, and one of the
> reasons
> > why
> > it is not PS), it might be worthwhile to try to address their
> concerns.
> >
> >             jak
> >
> > ----- Original Message -----
> > From: "Tsirtsis, George" <tsirtsis@qualcomm.com>
> > To: "James Kempf" <kempf@docomolabs-usa.com>; "Chowdhury, Kuntal"
> > <kchowdhury@starentnetworks.com>
> > Cc: <mip6@ietf.org>
> > Sent: Tuesday, July 18, 2006 12:10 PM
> > Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode Alert to
> HA?
> >
> >
> > May I ask, what is the typical lifetime of the SA and what would you
> > lengthen it to?
> > George
> >
> > > -----Original Message-----
> > > From: James Kempf [mailto:kempf@docomolabs-usa.com]
> > > Sent: Tuesday, July 18, 2006 2:43 PM
> > > To: Chowdhury, Kuntal
> > > Cc: mip6@ietf.org
> > > Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert
> to
> > HA?
> > >
> > > Kuntal,
> > >
> > > The intent is not to introduce something that the MN would send
> during
> > > dormant mode. Indeed, as you have described, this would negatively
> > impact
> > > battery life.
> > >
> > > The intent is to provide a way for the MN to say that it is about to
> > go
> > > into
> > > dormant mode, so please lengthen the IPsec SA timeout to avoid
> having
> > it
> > > expire for some longer period of time.
> > >
> > >             jak
> > >
> > > ----- Original Message -----
> > > From: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
> > > To: "James Kempf" <kempf@docomolabs-usa.com>
> > > Cc: <mip6@ietf.org>
> > > Sent: Tuesday, July 18, 2006 11:20 AM
> > > Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode Alert
> to
> > HA?
> > >
> > >
> > > James,
> > >
> > > This is a good discussion. Indeed the need for IPsec keepalives (or
> > DPD)
> > > over the air when the MN is dormant (or idle) is an issue in the
> > > cellular networks. The issue is Not that there are no mip6 messages
> > > defined or the HA is not aware of dormancy. It is more of a paging
> > > channel capacity issue, MN's battery life issue and the signaling
> > > overhead to transport the keepalives for a dormant MN issue.
> > >
> > > So, any new message however small won't solve the problem, IMHO.
> > >
> > > -Kuntal
> > >
> > >
> > > > -----Original Message-----
> > > > From: James Kempf [mailto:kempf@docomolabs-usa.com]
> > > > Sent: Tuesday, July 18, 2006 11:17 AM
> > > > To: Vijay Devarapalli
> > > > Cc: mip6@ietf.org
> > > > Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode
> Alert
> > to
> > > HA?
> > > >
> > > > For security, the message would need to be sent within an SA.
> There
> > is
> > > a
> > > > question about which.
> > > >
> > > > One possibility is to do a Mobility Extension (call the messages
> > > Sleeping
> > > > and WakingUp) and send it within the IPsec SA between the HA and
> MN.
> > > The
> > > > MN
> > > > sends the Sleeping message when it is about to go into dormant
> mode,
> > > it
> > > > sends the WakingUp message when it comes out again. The WakingUp
> > > message
> > > > isn't needed for the MN to get mobility service, it is just there
> > for
> > > > optimizing the SA timeouts. This would require a special API on
> the
> > HA
> > > > between the MIP code and IKE code for the HA to extend the IPsec
> SA
> > > > lifetime, similar to the one for IKEv1 mobility. The solution
> would
> > > only
> > > > be
> > > > applicable to Mobile IP.
> > > >
> > > > The other possibility is to do an IKEv2 INFORMATIONAL message that
> > is
> > > sent
> > > > within the IKE SA. It works similarly, but there would be no need
> > for
> > > any
> > > > API on the HA, since the IKE code itself would process it
> (actually,
> > I
> > > > proposed something like this to the Mobike WG but they didn't see
> > the
> > > need
> > > > for it). This would be applicable to both Mobike and Mobile IP
> (and
> > > any
> > > > other security protocol that uses IKEv2, so maybe HIP as well).
> > > >
> > > > One question is, does the HA need to do anything else if the MN
> goes
> > > into
> > > > dormant mode? I think there are lots of things it could do
> (lengthen
> > > the
> > > > BU
> > > > timeout, apply a filter that is either mobile specified or part of
> > the
> > > > user's service profile with the operator to only allow specific
> > > traffic
> > > > through, etc.) but I would really like to keep things simple.
> > > >
> > > >             jak
> > > >
> > > > ----- Original Message -----
> > > > From: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
> > > > To: "James Kempf" <kempf@docomolabs-usa.com>
> > > > Cc: <mip6@ietf.org>
> > > > Sent: Monday, July 17, 2006 3:43 PM
> > > > Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode
> Alert
> > to
> > > HA?
> > > >
> > > >
> > > > > the dormant mode extensions sounds good to me. we could do
> > > > > this extension. one issue to consider - what triggers this
> > > > > message? how does Mobile IP know the mobile node is going
> > > > > into a dormant mode. if we have the trigger we should be
> > > > > okay.
> > > > >
> > > > > but we have to check if this was the issue. with IKEv1 you
> > > > > could negotiate a lifetime for the IPsec SA. IKEv2 does not
> > > > > have the IPsec SA lifetime feature. so keepalives are
> > > > > needed.
> > > > >
> > > > > James Kempf wrote:
> > > > >> I was at Wimax Forum last week and I think I now understand why
> > > they
> > > > and
> > > > >> 3GPP2 want to use RFC 4285 auth option rather than IPsec. One
> > issue
> > > -
> > > > >> lack of EAP support for client auth - is solved by IKEv2 and
> they
> > > seem
> > > > to
> > > > >> now be moving in the direction of recommending IKEv2 if people
> > want
> > > to
> > > > >> deploy IPsec.
> > > > >
> > > > > yes this was one of the main issues.
> > > > >
> > > > > the way I saw it folks in 3GPP2 liked RFC 4285 because it
> > > > > is very similar to the MIPv4 mechanism and they were
> > > > > comfortable with it.
> > > > >
> > > > > Vijay
> > > > >
> > > > > But the other issue is a bit more complex. 802.16, like
> > > > >> most cellular protocols, has extensive support for dormant
> mode,
> > > and
> > > > >> Wimax Forum is supporting dormant mode in their network design.
> > If
> > > > IPsec
> > > > >> is used, then there is a risk when a mobile node goes into
> > dormant
> > > mode
> > > > >> that the IPsec SA may time out. It is unfortunate that this was
> > not
> > > > >> brought up when the discussion about RFC 4285 was happening,
> but
> > I
> > > > think
> > > > >> this might be something that the WG could work on now as part
> of
> > > the
> > > > new
> > > > >> charter. This would make IKEv2/IPsec more attractive as a
> > security
> > > > option
> > > > >> for cellular operators.
> > > > >>
> > > > >> Comments?
> > > > >>
> > > > >>            jak
> > > > >>
> > > > >>
> > > > >>
> > > > >> _______________________________________________
> > > > >> Mip6 mailing list
> > > > >> Mip6@ietf.org
> > > > >> https://www1.ietf.org/mailman/listinfo/mip6
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > > > _______________________________________________
> > > > Mip6 mailing list
> > > > Mip6@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/mip6
> > >
> > >
> > > "This email message and any attachments are confidential information
> > of
> > > Starent Networks, Corp. The information transmitted may not be used
> to
> > > create or change any contractual obligations of Starent Networks,
> > Corp.
> > > Any
> > > review, retransmission, dissemination or other use of, or taking of
> > any
> > > action in reliance upon this e-mail and its attachments by persons
> or
> > > entities other than the intended recipient is prohibited. If you are
> > not
> > > the
> > > intended recipient, please notify the sender immediately -- by
> > replying to
> > > this message or by sending an email to
> postmaster@starentnetworks.com
> > --
> >
> > > and
> > > destroy all copies of this message and any attachments without
> reading
> > or
> > > disclosing their contents. Thank you."
> > >
> > >
> > >
> > > _______________________________________________
> > > Mip6 mailing list
> > > Mip6@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/mip6
> >
>
>
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
>

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



From mip6-bounces@ietf.org Wed Jul 19 09:28:06 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G3C5l-000163-Td; Wed, 19 Jul 2006 09:27:57 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G3C5k-00015y-Ow
	for mip6@ietf.org; Wed, 19 Jul 2006 09:27:56 -0400
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G3C5k-0002Hg-1i
	for mip6@ietf.org; Wed, 19 Jul 2006 09:27:56 -0400
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
	k6JDRiHj007172
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Wed, 19 Jul 2006 06:27:44 -0700
Received: from NAEXBR03.na.qualcomm.com (naexbr03.qualcomm.com
	[129.46.134.172])
	by crowley.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	k6JDRb2m000163; Wed, 19 Jul 2006 06:27:39 -0700 (PDT)
Received: from NAEX14.na.qualcomm.com ([10.47.5.242]) by
	NAEXBR03.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 19 Jul 2006 06:27:36 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
Date: Wed, 19 Jul 2006 06:27:35 -0700
Message-ID: <7EB20EA0938B4D42A2D82689365C9B7A0CBE8B@NAEX14.na.qualcomm.com>
In-Reply-To: <eaa74a7e0607190138j79868bd3u48371dbcb8673fcb@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
Thread-Index: AcarD7ph9mKzS+hsT9S9RXcdi/ZfHAAJm6EA
From: "Tsirtsis, George" <tsirtsis@qualcomm.com>
To: "Gerardo Giaretta" <gerardo.giaretta@gmail.com>,
	"James Kempf" <kempf@docomolabs-usa.com>
X-OriginalArrivalTime: 19 Jul 2006 13:27:36.0104 (UTC)
	FILETIME=[19343280:01C6AB37]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d437399464e10b52abe9a34ed7e712d0
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

IMHO It would be a mistake to introduce a mechanism that allows the MN
to stop sending BUs. This would essentially result in "hard state" which
is bad.=20

Everyone repeat after me "hard state is bad"! ok, just joking :-)

Seriously though, all we are talking about here is manipulating a set of
timers we have for all these processes so that the maintenance of the
soft state associated with MIP and IPSEC does not affect the mobile's
battery life. Set these timers to values in the order of many minutes or
even better hours and the power consumption becomes negligible since the
MN can be in dormant mode for most of the time. One should also
time-align such timers when possible so that the MN can wake up once,
refresh all its timers and then go back to sleep.

Regards
George

> -----Original Message-----
> From: Gerardo Giaretta [mailto:gerardo.giaretta@gmail.com]
> Sent: Wednesday, July 19, 2006 4:39 AM
> To: Tsirtsis, George; James Kempf
> Cc: Chowdhury, Kuntal; mip6@ietf.org
> Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert to
HA?
>=20
> This problem applies also to the 3GPP I-WLAN in case the access
> network (that may be any non-3GPP access network and not only WLAN,
> despite of the name) supports dormant mode. I agree it is an important
> issue to study.
>=20
> I think there are two issues here:
>=20
> - one is the SA lifetime. This is really an IKE/IPsec issue and should
> be handled in IPsec (concluded) WG. As mentioned, this issue does not
> apply only to MIP6; in 3GPP I-WLAN the MN has an IPsec tunnel with the
> PDG and if the access network supports dormant mode, the MN cannot go
> into dormant mode state in order to keep the SA up. I guess it may
> apply also to MOBIKE.
>=20
> - another issue is the lifetime of the BCE. It seems not acceptable
> that the MN needs to go back to active state in order to send a
> refresh BU to the HA. For this issue, an extension to MIP6, similar to
> the one proposed by James, may make sense.
>=20
> --Gerardo
>=20
>=20
> On 7/18/06, Tsirtsis, George <tsirtsis@qualcomm.com> wrote:
> > I guess the important thing is to understand how the typical SA
lifetime
> > relates to the typical MIP6 Binding Lifetime. The MN will have to at
> > least wake up to refresh its binding.
> >
> > George
> >
> > > -----Original Message-----
> > > From: James Kempf [mailto:kempf@docomolabs-usa.com]
> > > Sent: Tuesday, July 18, 2006 3:37 PM
> > > To: Tsirtsis, George; Chowdhury, Kuntal
> > > Cc: mip6@ietf.org
> > > Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode
Alert to
> > HA?
> > >
> > > I don't know. What do operators typically set the SA lifetime to?
> > Though
> > > perhaps this is an unanswerable question because, as yet, has
anybody
> > > deployed MIPv6?
> > >
> > > My only observation is that this seems to be an issue with Wimax
> > Forum,
> > > and
> > > one of the primary motivators for wanting to use the RFC 4285 Auth
> > Option.
> > > If IETF and the MIP6 WG would like to encourage them to use IKE
(as
> > seemed
> > > to be the sentiment when RFC 4285 was discussed, and one of the
> > reasons
> > > why
> > > it is not PS), it might be worthwhile to try to address their
> > concerns.
> > >
> > >             jak
> > >
> > > ----- Original Message -----
> > > From: "Tsirtsis, George" <tsirtsis@qualcomm.com>
> > > To: "James Kempf" <kempf@docomolabs-usa.com>; "Chowdhury, Kuntal"
> > > <kchowdhury@starentnetworks.com>
> > > Cc: <mip6@ietf.org>
> > > Sent: Tuesday, July 18, 2006 12:10 PM
> > > Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode
Alert to
> > HA?
> > >
> > >
> > > May I ask, what is the typical lifetime of the SA and what would
you
> > > lengthen it to?
> > > George
> > >
> > > > -----Original Message-----
> > > > From: James Kempf [mailto:kempf@docomolabs-usa.com]
> > > > Sent: Tuesday, July 18, 2006 2:43 PM
> > > > To: Chowdhury, Kuntal
> > > > Cc: mip6@ietf.org
> > > > Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode
Alert
> > to
> > > HA?
> > > >
> > > > Kuntal,
> > > >
> > > > The intent is not to introduce something that the MN would send
> > during
> > > > dormant mode. Indeed, as you have described, this would
negatively
> > > impact
> > > > battery life.
> > > >
> > > > The intent is to provide a way for the MN to say that it is
about to
> > > go
> > > > into
> > > > dormant mode, so please lengthen the IPsec SA timeout to avoid
> > having
> > > it
> > > > expire for some longer period of time.
> > > >
> > > >             jak
> > > >
> > > > ----- Original Message -----
> > > > From: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
> > > > To: "James Kempf" <kempf@docomolabs-usa.com>
> > > > Cc: <mip6@ietf.org>
> > > > Sent: Tuesday, July 18, 2006 11:20 AM
> > > > Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode
Alert
> > to
> > > HA?
> > > >
> > > >
> > > > James,
> > > >
> > > > This is a good discussion. Indeed the need for IPsec keepalives
(or
> > > DPD)
> > > > over the air when the MN is dormant (or idle) is an issue in the
> > > > cellular networks. The issue is Not that there are no mip6
messages
> > > > defined or the HA is not aware of dormancy. It is more of a
paging
> > > > channel capacity issue, MN's battery life issue and the
signaling
> > > > overhead to transport the keepalives for a dormant MN issue.
> > > >
> > > > So, any new message however small won't solve the problem, IMHO.
> > > >
> > > > -Kuntal
> > > >
> > > >
> > > > > -----Original Message-----
> > > > > From: James Kempf [mailto:kempf@docomolabs-usa.com]
> > > > > Sent: Tuesday, July 18, 2006 11:17 AM
> > > > > To: Vijay Devarapalli
> > > > > Cc: mip6@ietf.org
> > > > > Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode
> > Alert
> > > to
> > > > HA?
> > > > >
> > > > > For security, the message would need to be sent within an SA.
> > There
> > > is
> > > > a
> > > > > question about which.
> > > > >
> > > > > One possibility is to do a Mobility Extension (call the
messages
> > > > Sleeping
> > > > > and WakingUp) and send it within the IPsec SA between the HA
and
> > MN.
> > > > The
> > > > > MN
> > > > > sends the Sleeping message when it is about to go into dormant
> > mode,
> > > > it
> > > > > sends the WakingUp message when it comes out again. The
WakingUp
> > > > message
> > > > > isn't needed for the MN to get mobility service, it is just
there
> > > for
> > > > > optimizing the SA timeouts. This would require a special API
on
> > the
> > > HA
> > > > > between the MIP code and IKE code for the HA to extend the
IPsec
> > SA
> > > > > lifetime, similar to the one for IKEv1 mobility. The solution
> > would
> > > > only
> > > > > be
> > > > > applicable to Mobile IP.
> > > > >
> > > > > The other possibility is to do an IKEv2 INFORMATIONAL message
that
> > > is
> > > > sent
> > > > > within the IKE SA. It works similarly, but there would be no
need
> > > for
> > > > any
> > > > > API on the HA, since the IKE code itself would process it
> > (actually,
> > > I
> > > > > proposed something like this to the Mobike WG but they didn't
see
> > > the
> > > > need
> > > > > for it). This would be applicable to both Mobike and Mobile IP
> > (and
> > > > any
> > > > > other security protocol that uses IKEv2, so maybe HIP as
well).
> > > > >
> > > > > One question is, does the HA need to do anything else if the
MN
> > goes
> > > > into
> > > > > dormant mode? I think there are lots of things it could do
> > (lengthen
> > > > the
> > > > > BU
> > > > > timeout, apply a filter that is either mobile specified or
part of
> > > the
> > > > > user's service profile with the operator to only allow
specific
> > > > traffic
> > > > > through, etc.) but I would really like to keep things simple.
> > > > >
> > > > >             jak
> > > > >
> > > > > ----- Original Message -----
> > > > > From: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
> > > > > To: "James Kempf" <kempf@docomolabs-usa.com>
> > > > > Cc: <mip6@ietf.org>
> > > > > Sent: Monday, July 17, 2006 3:43 PM
> > > > > Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode
> > Alert
> > > to
> > > > HA?
> > > > >
> > > > >
> > > > > > the dormant mode extensions sounds good to me. we could do
> > > > > > this extension. one issue to consider - what triggers this
> > > > > > message? how does Mobile IP know the mobile node is going
> > > > > > into a dormant mode. if we have the trigger we should be
> > > > > > okay.
> > > > > >
> > > > > > but we have to check if this was the issue. with IKEv1 you
> > > > > > could negotiate a lifetime for the IPsec SA. IKEv2 does not
> > > > > > have the IPsec SA lifetime feature. so keepalives are
> > > > > > needed.
> > > > > >
> > > > > > James Kempf wrote:
> > > > > >> I was at Wimax Forum last week and I think I now understand
why
> > > > they
> > > > > and
> > > > > >> 3GPP2 want to use RFC 4285 auth option rather than IPsec.
One
> > > issue
> > > > -
> > > > > >> lack of EAP support for client auth - is solved by IKEv2
and
> > they
> > > > seem
> > > > > to
> > > > > >> now be moving in the direction of recommending IKEv2 if
people
> > > want
> > > > to
> > > > > >> deploy IPsec.
> > > > > >
> > > > > > yes this was one of the main issues.
> > > > > >
> > > > > > the way I saw it folks in 3GPP2 liked RFC 4285 because it
> > > > > > is very similar to the MIPv4 mechanism and they were
> > > > > > comfortable with it.
> > > > > >
> > > > > > Vijay
> > > > > >
> > > > > > But the other issue is a bit more complex. 802.16, like
> > > > > >> most cellular protocols, has extensive support for dormant
> > mode,
> > > > and
> > > > > >> Wimax Forum is supporting dormant mode in their network
design.
> > > If
> > > > > IPsec
> > > > > >> is used, then there is a risk when a mobile node goes into
> > > dormant
> > > > mode
> > > > > >> that the IPsec SA may time out. It is unfortunate that this
was
> > > not
> > > > > >> brought up when the discussion about RFC 4285 was
happening,
> > but
> > > I
> > > > > think
> > > > > >> this might be something that the WG could work on now as
part
> > of
> > > > the
> > > > > new
> > > > > >> charter. This would make IKEv2/IPsec more attractive as a
> > > security
> > > > > option
> > > > > >> for cellular operators.
> > > > > >>
> > > > > >> Comments?
> > > > > >>
> > > > > >>            jak
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >> _______________________________________________
> > > > > >> Mip6 mailing list
> > > > > >> Mip6@ietf.org
> > > > > >> https://www1.ietf.org/mailman/listinfo/mip6
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > > _______________________________________________
> > > > > Mip6 mailing list
> > > > > Mip6@ietf.org
> > > > > https://www1.ietf.org/mailman/listinfo/mip6
> > > >
> > > >
> > > > "This email message and any attachments are confidential
information
> > > of
> > > > Starent Networks, Corp. The information transmitted may not be
used
> > to
> > > > create or change any contractual obligations of Starent
Networks,
> > > Corp.
> > > > Any
> > > > review, retransmission, dissemination or other use of, or taking
of
> > > any
> > > > action in reliance upon this e-mail and its attachments by
persons
> > or
> > > > entities other than the intended recipient is prohibited. If you
are
> > > not
> > > > the
> > > > intended recipient, please notify the sender immediately -- by
> > > replying to
> > > > this message or by sending an email to
> > postmaster@starentnetworks.com
> > > --
> > >
> > > > and
> > > > destroy all copies of this message and any attachments without
> > reading
> > > or
> > > > disclosing their contents. Thank you."
> > > >
> > > >
> > > >
> > > > _______________________________________________
> > > > Mip6 mailing list
> > > > Mip6@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/mip6
> > >
> >
> >
> > _______________________________________________
> > Mip6 mailing list
> > Mip6@ietf.org
> > https://www1.ietf.org/mailman/listinfo/mip6
> >

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



From mip6-bounces@ietf.org Wed Jul 19 11:54:58 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G3ENu-0007G8-Ty; Wed, 19 Jul 2006 11:54:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G3ENt-0007F9-Se
	for mip6@ietf.org; Wed, 19 Jul 2006 11:54:49 -0400
Received: from key1.docomolabs-usa.com ([216.98.102.225]
	helo=fridge.docomolabs-usa.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G3ENt-0005E9-2c
	for mip6@ietf.org; Wed, 19 Jul 2006 11:54:49 -0400
Message-ID: <018c01c6ab4b$ee713010$196115ac@dcml.docomolabsusa.com>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Narayanan, Vidya" <vidyan@qualcomm.com>,
	"Tsirtsis, George" <tsirtsis@qualcomm.com>,
	"Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
References: <C24CB51D5AA800449982D9BCB90325130A11E4@NAEX13.na.qualcomm.com>
Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
Date: Wed, 19 Jul 2006 08:47:56 -0700
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: 2f0065339d489fe5a2873ea9ad776d1a
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

The operator may want to keep active mode timers short, then set them longer 
only if the mobile goes into dormant mode.

            jak



----- Original Message ----- 
From: "Narayanan, Vidya" <vidyan@qualcomm.com>
To: "Tsirtsis, George" <tsirtsis@qualcomm.com>; "Vijay Devarapalli" 
<vijay.devarapalli@azairenet.com>
Cc: <mip6@ietf.org>; "James Kempf" <kempf@docomolabs-usa.com>
Sent: Tuesday, July 18, 2006 4:26 PM
Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?


I'm just catching up with this discussion.

If the IPsec idle timer is at least equal to the BU lifetime, why is
there a need for any other signaling related to dormant mode? Given that
the timer values are a matter of policy, this should be do-able.

Vidya

> -----Original Message-----
> From: Tsirtsis, George [mailto:tsirtsis@qualcomm.com]
> Sent: Tuesday, July 18, 2006 3:11 PM
> To: Vijay Devarapalli
> Cc: mip6@ietf.org; James Kempf
> Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode
> Alert to HA?
>
> Yes, I meant DPD.
>
> There is a fate sharing here between MIP6 state and IPSEC
> state. I guess the SA lifetime and DPD timer was introduced
> to catch the general case but they do not make sense to be
> much different than the MIP lifetime when that is used.
>
> It is indeed strange, however, that IPSEC does not allow for
> negotiation of these parameters. I guess people will have to
> use reasonable values in each deployment depending what they
> are doing.
>
> George
>
> > -----Original Message-----
> > From: Vijay Devarapalli [mailto:vijay.devarapalli@azairenet.com]
> > Sent: Tuesday, July 18, 2006 6:06 PM
> > To: Tsirtsis, George
> > Cc: James Kempf; Chowdhury, Kuntal; mip6@ietf.org
> > Subject: Re: [Mip6] New Charter Item:Support for Dormant
> Mode Alert to
> HA?
> >
> > Tsirtsis, George wrote:
> > > So how often PDP messages are sent is also local policy?
> >
> > I guess you meant DPD. yes it is local policy. the initiator and
> > responder configure this independently.
> >
> > > In which case
> > > it can be configured to a time that makes sense for MIP
> or a given
> > > deployment scenario.
> >
> > Yes. however, the IPsec implementation should allow for
> sufficiently
> > large values for DPD timer. but then again DPD exists so
> that unwanted
> > IPsec state is removed if the other end goes down or if there is no
> > traffic for a long time.
> >
> > Vijay
> >
> > > George
> > >
> > >> -----Original Message-----
> > >> From: Vijay Devarapalli [mailto:vijay.devarapalli@azairenet.com]
> > >> Sent: Tuesday, July 18, 2006 5:42 PM
> > >> To: James Kempf
> > >> Cc: Tsirtsis, George; Chowdhury, Kuntal; mip6@ietf.org
> > >> Subject: Re: [Mip6] New Charter Item:Support for Dormant
> Mode Alert
> to
> > > HA?
> > >> James Kempf wrote:
> > >>> I don't know. What do operators typically set the SA
> lifetime to?
> > > Though
> > >>> perhaps this is an unanswerable question because, as yet, has
> > > anybody
> > >>> deployed MIPv6?
> > >> this is more of an IPsec issue. it depends on the local
> policy on
> > >> the initiator and responder. however, as long as there
> is traffic
> > >> and there are responses to DPD messages, the IPsec SA is not
> > >> deleted.
> > >>
> > >> Vijay
> > >>
> > >>> My only observation is that this seems to be an issue with Wimax
> > > Forum,
> > >>> and one of the primary motivators for wanting to use
> the RFC 4285
> > > Auth
> > >>> Option. If IETF and the MIP6 WG would like to encourage them to
> use
> > > IKE
> > >>> (as seemed to be the sentiment when RFC 4285 was discussed, and
> one
> > > of
> > >>> the reasons why it is not PS), it might be worthwhile to try to
> > > address
> > >>> their concerns.
> > >>>
> > >>>            jak
> > >>>
> > >>> ----- Original Message ----- From: "Tsirtsis, George"
> > >>> <tsirtsis@qualcomm.com>
> > >>> To: "James Kempf" <kempf@docomolabs-usa.com>;
> "Chowdhury, Kuntal"
> > >>> <kchowdhury@starentnetworks.com>
> > >>> Cc: <mip6@ietf.org>
> > >>> Sent: Tuesday, July 18, 2006 12:10 PM
> > >>> Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode
> Alert
> > > to
> > >> HA?
> > >>>
> > >>> May I ask, what is the typical lifetime of the SA and what would
> you
> > >>> lengthen it to?
> > >>> George
> > >>>
> > >>>> -----Original Message-----
> > >>>> From: James Kempf [mailto:kempf@docomolabs-usa.com]
> > >>>> Sent: Tuesday, July 18, 2006 2:43 PM
> > >>>> To: Chowdhury, Kuntal
> > >>>> Cc: mip6@ietf.org
> > >>>> Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode
> Alert
> > > to
> > >>> HA?
> > >>>
> > >>>> Kuntal,
> > >>>>
> > >>>> The intent is not to introduce something that the MN would send
> > > during
> > >>>> dormant mode. Indeed, as you have described, this would
> negatively
> > >>> impact
> > >>>
> > >>>> battery life.
> > >>>>
> > >>>> The intent is to provide a way for the MN to say that
> it is about
> > > to
> > >>> go
> > >>>
> > >>>> into
> > >>>> dormant mode, so please lengthen the IPsec SA timeout to avoid
> > > having
> > >>> it
> > >>>
> > >>>> expire for some longer period of time.
> > >>>>
> > >>>>             jak
> > >>>>
> > >>>> ----- Original Message -----
> > >>>> From: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
> > >>>> To: "James Kempf" <kempf@docomolabs-usa.com>
> > >>>> Cc: <mip6@ietf.org>
> > >>>> Sent: Tuesday, July 18, 2006 11:20 AM
> > >>>> Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode
> Alert
> > > to
> > >>> HA?
> > >>>
> > >>>>
> > >>>> James,
> > >>>>
> > >>>> This is a good discussion. Indeed the need for IPsec keepalives
> (or
> > >>> DPD)
> > >>>
> > >>>> over the air when the MN is dormant (or idle) is an
> issue in the
> > >>>> cellular networks. The issue is Not that there are no mip6
> messages
> > >>>> defined or the HA is not aware of dormancy. It is more of a
> paging
> > >>>> channel capacity issue, MN's battery life issue and
> the signaling
> > >>>> overhead to transport the keepalives for a dormant MN issue.
> > >>>>
> > >>>> So, any new message however small won't solve the
> problem, IMHO.
> > >>>>
> > >>>> -Kuntal
> > >>>>
> > >>>>
> > >>>>> -----Original Message-----
> > >>>>> From: James Kempf [mailto:kempf@docomolabs-usa.com]
> > >>>>> Sent: Tuesday, July 18, 2006 11:17 AM
> > >>>>> To: Vijay Devarapalli
> > >>>>> Cc: mip6@ietf.org
> > >>>>> Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode
> > > Alert
> > >>> to
> > >>>
> > >>>> HA?
> > >>>>> For security, the message would need to be sent within an SA.
> > > There
> > >>> is
> > >>>
> > >>>> a
> > >>>>> question about which.
> > >>>>>
> > >>>>> One possibility is to do a Mobility Extension (call
> the messages
> > >>>> Sleeping
> > >>>>> and WakingUp) and send it within the IPsec SA between
> the HA and
> > > MN.
> > >>>> The
> > >>>>> MN
> > >>>>> sends the Sleeping message when it is about to go into dormant
> > > mode,
> > >>>> it
> > >>>>> sends the WakingUp message when it comes out again.
> The WakingUp
> > >>>> message
> > >>>>> isn't needed for the MN to get mobility service, it is just
> there
> > >>> for
> > >>>
> > >>>>> optimizing the SA timeouts. This would require a
> special API on
> > > the
> > >>> HA
> > >>>
> > >>>>> between the MIP code and IKE code for the HA to
> extend the IPsec
> > > SA
> > >>>>> lifetime, similar to the one for IKEv1 mobility. The solution
> > > would
> > >>>> only
> > >>>>> be
> > >>>>> applicable to Mobile IP.
> > >>>>>
> > >>>>> The other possibility is to do an IKEv2 INFORMATIONAL message
> > > that
> > >>> is
> > >>>
> > >>>> sent
> > >>>>> within the IKE SA. It works similarly, but there would be no
> need
> > >>> for
> > >>>
> > >>>> any
> > >>>>> API on the HA, since the IKE code itself would process it
> > > (actually,
> > >>> I
> > >>>
> > >>>>> proposed something like this to the Mobike WG but they didn't
> see
> > >>> the
> > >>>
> > >>>> need
> > >>>>> for it). This would be applicable to both Mobike and Mobile IP
> > > (and
> > >>>> any
> > >>>>> other security protocol that uses IKEv2, so maybe HIP
> as well).
> > >>>>>
> > >>>>> One question is, does the HA need to do anything else
> if the MN
> > > goes
> > >>>> into
> > >>>>> dormant mode? I think there are lots of things it could do
> > > (lengthen
> > >>>> the
> > >>>>> BU
> > >>>>> timeout, apply a filter that is either mobile
> specified or part
> > > of
> > >>> the
> > >>>
> > >>>>> user's service profile with the operator to only
> allow specific
> > >>>> traffic
> > >>>>> through, etc.) but I would really like to keep things simple.
> > >>>>>
> > >>>>>             jak
> > >>>>>
> > >>>>> ----- Original Message -----
> > >>>>> From: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
> > >>>>> To: "James Kempf" <kempf@docomolabs-usa.com>
> > >>>>> Cc: <mip6@ietf.org>
> > >>>>> Sent: Monday, July 17, 2006 3:43 PM
> > >>>>> Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode
> > > Alert
> > >>> to
> > >>>
> > >>>> HA?
> > >>>>>
> > >>>>>> the dormant mode extensions sounds good to me. we
> could do this
> > >>>>>> extension. one issue to consider - what triggers
> this message?
> > >>>>>> how does Mobile IP know the mobile node is going
> into a dormant
> > >>>>>> mode. if we have the trigger we should be okay.
> > >>>>>>
> > >>>>>> but we have to check if this was the issue. with IKEv1 you
> > >>>>>> could negotiate a lifetime for the IPsec SA. IKEv2 does not
> > >>>>>> have the IPsec SA lifetime feature. so keepalives are needed.
> > >>>>>>
> > >>>>>> James Kempf wrote:
> > >>>>>>> I was at Wimax Forum last week and I think I now understand
> > > why
> > >>>> they
> > >>>>> and
> > >>>>>>> 3GPP2 want to use RFC 4285 auth option rather than
> IPsec. One
> > >>> issue
> > >>>
> > >>>> -
> > >>>>>>> lack of EAP support for client auth - is solved by IKEv2 and
> > > they
> > >>>> seem
> > >>>>> to
> > >>>>>>> now be moving in the direction of recommending
> IKEv2 if people
> > >>> want
> > >>>
> > >>>> to
> > >>>>>>> deploy IPsec.
> > >>>>>> yes this was one of the main issues.
> > >>>>>>
> > >>>>>> the way I saw it folks in 3GPP2 liked RFC 4285 because it is
> > >>>>>> very similar to the MIPv4 mechanism and they were
> comfortable
> > >>>>>> with it.
> > >>>>>>
> > >>>>>> Vijay
> > >>>>>>
> > >>>>>> But the other issue is a bit more complex. 802.16, like
> > >>>>>>> most cellular protocols, has extensive support for dormant
> > > mode,
> > >>>> and
> > >>>>>>> Wimax Forum is supporting dormant mode in their network
> > > design.
> > >>> If
> > >>>
> > >>>>> IPsec
> > >>>>>>> is used, then there is a risk when a mobile node goes into
> > >>> dormant
> > >>>
> > >>>> mode
> > >>>>>>> that the IPsec SA may time out. It is unfortunate that this
> > > was
> > >>> not
> > >>>
> > >>>>>>> brought up when the discussion about RFC 4285 was happening,
> > > but
> > >>> I
> > >>>
> > >>>>> think
> > >>>>>>> this might be something that the WG could work on
> now as part
> > > of
> > >>>> the
> > >>>>> new
> > >>>>>>> charter. This would make IKEv2/IPsec more attractive as a
> > >>> security
> > >>>
> > >>>>> option
> > >>>>>>> for cellular operators.
> > >>>>>>>
> > >>>>>>> Comments?
> > >>>>>>>
> > >>>>>>>            jak
> > >>>>>>>
> > >>>>>>>
> > >>>>>>>
> > >>>>>>> _______________________________________________
> > >>>>>>> Mip6 mailing list
> > >>>>>>> Mip6@ietf.org
> > >>>>>>> https://www1.ietf.org/mailman/listinfo/mip6
> > >>>>>>
> > >>>>>
> > >>>>>
> > >>>>> _______________________________________________
> > >>>>> Mip6 mailing list
> > >>>>> Mip6@ietf.org
> > >>>>> https://www1.ietf.org/mailman/listinfo/mip6
> > >>>>
> > >>>> "This email message and any attachments are confidential
> > > information
> > >>> of
> > >>>
> > >>>> Starent Networks, Corp. The information transmitted may not be
> used
> > > to
> > >>>> create or change any contractual obligations of
> Starent Networks,
> > >>> Corp.
> > >>>
> > >>>> Any
> > >>>> review, retransmission, dissemination or other use of,
> or taking
> of
> > >>> any
> > >>>
> > >>>> action in reliance upon this e-mail and its attachments by
> persons
> > > or
> > >>>> entities other than the intended recipient is
> prohibited. If you
> > > are
> > >>> not
> > >>>
> > >>>> the
> > >>>> intended recipient, please notify the sender immediately -- by
> > >>> replying to
> > >>>
> > >>>> this message or by sending an email to
> > > postmaster@starentnetworks.com
> > >>> --
> > >>>
> > >>>> and
> > >>>> destroy all copies of this message and any attachments without
> > > reading
> > >>> or
> > >>>
> > >>>> disclosing their contents. Thank you."
> > >>>>
> > >>>>
> > >>>>
> > >>>> _______________________________________________
> > >>>> Mip6 mailing list
> > >>>> Mip6@ietf.org
> > >>>> https://www1.ietf.org/mailman/listinfo/mip6
> > >>>
> > >>>
> > >>>
> > >>> _______________________________________________
> > >>> Mip6 mailing list
> > >>> Mip6@ietf.org
> > >>> https://www1.ietf.org/mailman/listinfo/mip6
> > >
>
>
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
>



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



From mip6-bounces@ietf.org Wed Jul 19 12:09:00 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G3Ebb-0001nL-Ff; Wed, 19 Jul 2006 12:08:59 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G3Ebb-0001mw-3Z
	for mip6@ietf.org; Wed, 19 Jul 2006 12:08:59 -0400
Received: from key1.docomolabs-usa.com ([216.98.102.225]
	helo=fridge.docomolabs-usa.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G3EbY-0007od-NU
	for mip6@ietf.org; Wed, 19 Jul 2006 12:08:59 -0400
Message-ID: <01bc01c6ab4d$e6e2e9e0$196115ac@dcml.docomolabsusa.com>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Gerardo Giaretta" <gerardo.giaretta@gmail.com>,
	"Tsirtsis, George" <tsirtsis@qualcomm.com>
References: <033201c6aaa1$787be580$196115ac@dcml.docomolabsusa.com>
	<7EB20EA0938B4D42A2D82689365C9B7A0CBDEE@NAEX14.na.qualcomm.com>
	<eaa74a7e0607190138j79868bd3u48371dbcb8673fcb@mail.gmail.com>
Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
Date: Wed, 19 Jul 2006 09:10:49 -0700
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=response
Content-Transfer-Encoding: 7bit
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Gerardo,

----- Original Message ----- 
From: "Gerardo Giaretta" <gerardo.giaretta@gmail.com>
To:> - one is the SA lifetime. This is really an IKE/IPsec issue and should
> be handled in IPsec (concluded) WG. As mentioned, this issue does not
> apply only to MIP6; in 3GPP I-WLAN the MN has an IPsec tunnel with the
> PDG and if the access network supports dormant mode, the MN cannot go
> into dormant mode state in order to keep the SA up. I guess it may
> apply also to MOBIKE.
>

The IPsec WG doesn't exist anymore and neither does MOBIKE. MOBIKE was 
closed recently. If the MIP WG decides that this is a problem that needs to 
be solved, it cannot simply hand the problem off to another WG. Either a new 
WG would need to be formed or the MIP WG would need to do the work itself.

> - another issue is the lifetime of the BCE. It seems not acceptable
> that the MN needs to go back to active state in order to send a
> refresh BU to the HA. For this issue, an extension to MIP6, similar to
> the one proposed by James, may make sense.
>

As George brought up, the two are linked. Unfortunately, given the way IETF 
designs protocols (as "piece parts"), its difficult to optimize if two 
independently designed protocols have in softstate dependences when used 
together.

Perhaps we would solve the problem by defining an IKEv2 INFORMATIONAL 
message to negotiate the timeout, then let the MN include a Mobility Header 
Option to lengthen the BCE lifetime into that. This would limit the message 
exchange to one roundtrip (presuming no retransmission), which I believe is 
important because an MN that wants to go into dormant mode probably doesn't 
want to conduct a lot of messaging with the HA.

            jak 



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



From mip6-bounces@ietf.org Wed Jul 19 12:10:03 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G3Ecd-00023o-4P; Wed, 19 Jul 2006 12:10:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G3Ecb-00023X-Uh
	for mip6@ietf.org; Wed, 19 Jul 2006 12:10:01 -0400
Received: from atlrel6.hp.com ([156.153.255.205])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G3EcZ-0007sa-Ld
	for mip6@ietf.org; Wed, 19 Jul 2006 12:10:01 -0400
Received: from smtp1.fc.hp.com (smtp.fc.hp.com [15.15.136.127])
	by atlrel6.hp.com (Postfix) with ESMTP id D57783882B;
	Wed, 19 Jul 2006 12:09:56 -0400 (EDT)
Received: from [16.116.96.215] (spaceshipone.zko.hp.com [16.116.96.215])
	by smtp1.fc.hp.com (Postfix) with ESMTP id 641CC53D9B;
	Wed, 19 Jul 2006 16:09:56 +0000 (UTC)
Message-ID: <44BE5953.6080602@hp.com>
Date: Wed, 19 Jul 2006 12:09:55 -0400
From: Brian Haley <brian.haley@hp.com>
Organization: Open Source and Linux Organization
User-Agent: Thunderbird 1.5.0.4 (X11/20060615)
MIME-Version: 1.0
To: Alexandru Petrescu <alexandru.petrescu@motorola.com>
Subject: Re: [Mip6] New charter item: HA assignment
References: <729b68be0607180431m773dc847qed3e7350819a8d04@mail.gmail.com>
	<44BD1105.5040904@motorola.com> <44BD3AA6.7070906@hp.com>
	<44BD5AEA.6020209@motorola.com>
In-Reply-To: <44BD5AEA.6020209@motorola.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org


>>> Another way is for the new HA to send Binding Refresh Request to MN
>>>  (even if it has no BC entry for it).
>>
>> BRR is sent from CN to MN, it is not defined to be sent from HA.
> 
> I think that depends on each one's interpretation of "correspondent".  I
> see BRR very well sent by HA to MN if BCE lifetime expired and BU was lost.

I don't know how you can interpret 3775 (or implement it) such that a HA 
can be a CN of the same MN at the same time.  You're the HA or you 
aren't, and HAs don't send BRRs - TAHI would have a test for it if they 
could :)

>> I know you brought-up extending it at the WG meeting (instead of using 
>> HA switch), but I couldn't remember all the reasons we didn't do that. 
>> IPsec is the other problem since the message has no protection, but 
>> needs it.
> 
> Mostly ok with that, but I can't completely agree until I haven't read
> the draft.  BRR is a Mobility Header, so assumed to be ok with IPsec.

But 3776 doesn't define the use of IPsec for a BRR.

> IPsec is anyways a sensitive issue because we're talking three parties:
> two HAs (an initial and an "assigned") and one MN, presumably HAs
> exchange SAs.  Do you use the CA concept?

CA == ??

> I'll have to read it.

Please do, I'd appreciate any comments.

-Brian

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



From mip6-bounces@ietf.org Wed Jul 19 12:27:01 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G3Et1-0001Tf-9r; Wed, 19 Jul 2006 12:26:59 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G3Esz-0001Ta-Vc
	for mip6@ietf.org; Wed, 19 Jul 2006 12:26:57 -0400
Received: from key1.docomolabs-usa.com ([216.98.102.225]
	helo=fridge.docomolabs-usa.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G3Esy-0001wL-JC
	for mip6@ietf.org; Wed, 19 Jul 2006 12:26:57 -0400
Message-ID: <020a01c6ab50$68e3c9d0$196115ac@dcml.docomolabsusa.com>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Tsirtsis, George" <tsirtsis@qualcomm.com>,
	"Gerardo Giaretta" <gerardo.giaretta@gmail.com>
References: <7EB20EA0938B4D42A2D82689365C9B7A0CBE8B@NAEX14.na.qualcomm.com>
Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
Date: Wed, 19 Jul 2006 09:28:47 -0700
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org


----- Original Message ----- 
From: "Tsirtsis, George" <tsirtsis@qualcomm.com>
To: "Gerardo Giaretta" <gerardo.giaretta@gmail.com>; "James Kempf" 
<kempf@docomolabs-usa.com>
Cc: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>; <mip6@ietf.org>
Sent: Wednesday, July 19, 2006 6:27 AM
Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?


IMHO It would be a mistake to introduce a mechanism that allows the MN
to stop sending BUs. This would essentially result in "hard state" which
is bad.

Everyone repeat after me "hard state is bad"! ok, just joking :-)

jak>> No, it isn't a joke. You're right.

Seriously though, all we are talking about here is manipulating a set of
timers we have for all these processes so that the maintenance of the
soft state associated with MIP and IPSEC does not affect the mobile's
battery life. Set these timers to values in the order of many minutes or
even better hours and the power consumption becomes negligible since the
MN can be in dormant mode for most of the time. One should also
time-align such timers when possible so that the MN can wake up once,
refresh all its timers and then go back to sleep.

jak>> I think the issue is that some operators may want to have a policy 
that has different timer values for dormant and active mode hosts. And what 
if the timer values are set differently for different kinds of mobile 
devices? A timer for an iPac might be different from a Toyota Prius, 
because the amount of power available would be quite different.

jak>> Anyway, there's still an issue with IKEv2 not allowing the timer value 
to be negotiated.

            jak 



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



From mip6-bounces@ietf.org Wed Jul 19 12:31:05 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G3Eww-0002S8-4J; Wed, 19 Jul 2006 12:31:02 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G3Ewu-0002S3-Je
	for mip6@ietf.org; Wed, 19 Jul 2006 12:31:00 -0400
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G3Ewt-0002yQ-9Z
	for mip6@ietf.org; Wed, 19 Jul 2006 12:31:00 -0400
Received: from magus.qualcomm.com (magus.qualcomm.com [129.46.61.148])
	by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k6JGUqM0006427
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Wed, 19 Jul 2006 09:30:54 -0700
Received: from NAEXBR02.na.qualcomm.com (naexbr02.qualcomm.com [10.46.92.109])
	by magus.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	k6JGUpV9013421; Wed, 19 Jul 2006 09:30:52 -0700 (PDT)
Received: from NAEX14.na.qualcomm.com ([10.47.5.242]) by
	NAEXBR02.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 19 Jul 2006 09:30:51 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
Date: Wed, 19 Jul 2006 09:30:46 -0700
Message-ID: <7EB20EA0938B4D42A2D82689365C9B7A0CBEBC@NAEX14.na.qualcomm.com>
In-Reply-To: <7EB20EA0938B4D42A2D82689365C9B7A0CBE8B@NAEX14.na.qualcomm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
Thread-Index: AcarD7ph9mKzS+hsT9S9RXcdi/ZfHAAJm6EAAAaDhyA=
From: "Soliman, Hesham" <hsoliman@qualcomm.com>
To: "Tsirtsis, George" <tsirtsis@qualcomm.com>,
	"Gerardo Giaretta" <gerardo.giaretta@gmail.com>,
	"James Kempf" <kempf@docomolabs-usa.com>
X-OriginalArrivalTime: 19 Jul 2006 16:30:51.0210 (UTC)
	FILETIME=[B2CC3AA0:01C6AB50]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org


 > > - another issue is the lifetime of the BCE. It seems not acceptable
 > > that the MN needs to go back to active state in order to send a
 > > refresh BU to the HA.=20

=3D> I think this is too radical. It's perfectly acceptable to do that =
if
it only happens once an hour or once every two hours ...etc. If it
happens once a minute then of course it's a problem. I don't think you
can make a blanket statement that disregards the frequency of the
updates.=20

 > MIP6, similar to
 > > the one proposed by James, may make sense.

=3D> Too premature IMO.=20

Hesham

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



From mip6-bounces@ietf.org Wed Jul 19 12:41:51 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G3F7O-0003kQ-MT; Wed, 19 Jul 2006 12:41:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G3F7N-0003j0-5Q
	for mip6@ietf.org; Wed, 19 Jul 2006 12:41:49 -0400
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G3F7L-0000Aa-Pb
	for mip6@ietf.org; Wed, 19 Jul 2006 12:41:49 -0400
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
	k6JGfg2F008614
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Wed, 19 Jul 2006 09:41:43 -0700
Received: from NAEXBR02.na.qualcomm.com (naexbr02.qualcomm.com [10.46.92.109])
	by neophyte.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	k6JGdfxf019705; Wed, 19 Jul 2006 09:41:41 -0700 (PDT)
Received: from NAEX14.na.qualcomm.com ([10.47.5.242]) by
	NAEXBR02.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 19 Jul 2006 09:41:36 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
Date: Wed, 19 Jul 2006 09:41:34 -0700
Message-ID: <7EB20EA0938B4D42A2D82689365C9B7A0CBEC2@NAEX14.na.qualcomm.com>
In-Reply-To: <020a01c6ab50$68e3c9d0$196115ac@dcml.docomolabsusa.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
Thread-Index: AcarUDAOmdeC5IQCTLGGYBXOg4MwLQAAXKPA
From: "Tsirtsis, George" <tsirtsis@qualcomm.com>
To: "James Kempf" <kempf@docomolabs-usa.com>,
	"Gerardo Giaretta" <gerardo.giaretta@gmail.com>
X-OriginalArrivalTime: 19 Jul 2006 16:41:36.0844 (UTC)
	FILETIME=[33A028C0:01C6AB52]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

James,

Yes, as Vijay also indicated it would be good if IKEv2 had a way to
negotiate timers.

WRT MIP, however, lengthening the lifetime could simply be a matter for
sending another BU before going to dormant mode, rather than introducing
a whole new message.

My point is that it is not clear to me that MIP/IPSEC and other
protocols need to understand "dormancy" as a mode of operation, as long
as the soft state timers can be negotiated at will (within policy limits
of course).

George

> -----Original Message-----
> From: James Kempf [mailto:kempf@docomolabs-usa.com]
> Sent: Wednesday, July 19, 2006 12:29 PM
> To: Tsirtsis, George; Gerardo Giaretta
> Cc: Chowdhury, Kuntal; mip6@ietf.org
> Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert to
HA?
>=20
>=20
> ----- Original Message -----
> From: "Tsirtsis, George" <tsirtsis@qualcomm.com>
> To: "Gerardo Giaretta" <gerardo.giaretta@gmail.com>; "James Kempf"
> <kempf@docomolabs-usa.com>
> Cc: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>;
<mip6@ietf.org>
> Sent: Wednesday, July 19, 2006 6:27 AM
> Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode Alert to
HA?
>=20
>=20
> IMHO It would be a mistake to introduce a mechanism that allows the MN
> to stop sending BUs. This would essentially result in "hard state"
which
> is bad.
>=20
> Everyone repeat after me "hard state is bad"! ok, just joking :-)
>=20
> jak>> No, it isn't a joke. You're right.
>=20
> Seriously though, all we are talking about here is manipulating a set
of
> timers we have for all these processes so that the maintenance of the
> soft state associated with MIP and IPSEC does not affect the mobile's
> battery life. Set these timers to values in the order of many minutes
or
> even better hours and the power consumption becomes negligible since
the
> MN can be in dormant mode for most of the time. One should also
> time-align such timers when possible so that the MN can wake up once,
> refresh all its timers and then go back to sleep.
>=20
> jak>> I think the issue is that some operators may want to have a
policy
> that has different timer values for dormant and active mode hosts. And
> what
> if the timer values are set differently for different kinds of mobile
> devices? A timer for an iPac might be different from a Toyota Prius,
> because the amount of power available would be quite different.
>=20
> jak>> Anyway, there's still an issue with IKEv2 not allowing the timer
> value
> to be negotiated.
>=20
>             jak
>=20


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



From mip6-bounces@ietf.org Wed Jul 19 13:47:11 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G3G8Z-0005cy-6V; Wed, 19 Jul 2006 13:47:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G3G8X-0005cs-P8
	for mip6@ietf.org; Wed, 19 Jul 2006 13:47:05 -0400
Received: from motgate2.mot.com ([144.189.100.101])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G3G8V-0001np-BL
	for mip6@ietf.org; Wed, 19 Jul 2006 13:47:05 -0400
Received: from az33exr04.mot.com (az33exr04.mot.com [10.64.251.234])
	by motgate2.mot.com (8.12.11/Motorola) with ESMTP id k6JHkvl9012900;
	Wed, 19 Jul 2006 10:47:01 -0700 (MST)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by az33exr04.mot.com (8.13.1/8.13.0) with ESMTP id k6JHktTt005326;
	Wed, 19 Jul 2006 12:46:56 -0500 (CDT)
Message-ID: <44BE700D.5070700@motorola.com>
Date: Wed, 19 Jul 2006 19:46:53 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: Brian Haley <brian.haley@hp.com>
Subject: Re: [Mip6] New charter item: HA assignment
References: <729b68be0607180431m773dc847qed3e7350819a8d04@mail.gmail.com>
	<44BD1105.5040904@motorola.com> <44BD3AA6.7070906@hp.com>
	<44BD5AEA.6020209@motorola.com> <44BE5953.6080602@hp.com>
In-Reply-To: <44BE5953.6080602@hp.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAQAAAAQ=
X-White-List-Member: TRUE
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9a2be21919e71dc6faef12b370c4ecf5
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Brian Haley wrote:
> 
>>>> Another way is for the new HA to send Binding Refresh Request 
>>>> to MN (even if it has no BC entry for it).
>>> 
>>> BRR is sent from CN to MN, it is not defined to be sent from HA.
>> 
>> I think that depends on each one's interpretation of 
>> "correspondent".  I see BRR very well sent by HA to MN if BCE 
>> lifetime expired and BU was lost.
> 
> I don't know how you can interpret 3775 (or implement it) such that a
>  HA can be a CN of the same MN at the same time.

I don't see the problem with that.

For some implementations it is useful/easy to have HA send BRR to MN.
In this way MN does not need to implement additional timer of receiving
BAck, only a timer for re-transmitting BU and to respond to BRR.

Wrt to how to read rfc3775 and think that CN can be a HA, this is an
exercise indeed, but I'm tempted to do it because I also had
to do it when thinking CN can be a MN.  And, if one thinks NEMOv6 then,
and MN is a MR and MR can be a HA for mobiles in its moving network...
CN can be a HA.

In the end, the BRR message should be implemented as send and receive in
any entity running Mobile IPv6: CN, HA, MH, MR.

Take this 3775 text:
> If the sender knows that the Binding Cache entry is still in active 
> use, it MAY send a Binding Refresh Request message to the mobile node
>  in an attempt to avoid this overhead and latency due to deleting and
>  recreating the Binding Cache entry.

What "sender" maintains a Binding Cache?  Both CN and HA, only MN
doesn't.  So MN would not send BRR.  But if MN is a CN to another MN
then MN would send BRR too.

Take this other 3775 text:
> This message [BRR] is always sent to the home address of the mobile 
> node.

So HA sends BRR to the HoA, HA (same entity) intercepts it because proxy
ND for HoA, and encapsulates and sends it to CoA.

> You're the HA or you aren't, and HAs don't send BRRs - TAHI would 
> have a test for it if they could :)

I suppose TAHI's interpretation of 3775 is that HA doesn't send BRRs.
Some implementations don't conform to TAHI then.

>>> I know you brought-up extending it at the WG meeting (instead of
>>>  using HA switch), but I couldn't remember all the reasons we 
>>> didn't do that. IPsec is the other problem since the message has
>>>  no protection, but needs it.
>> 
>> Mostly ok with that, but I can't completely agree until I haven't 
>> read the draft.  BRR is a Mobility Header, so assumed to be ok with
>>  IPsec.
> 
> But 3776 doesn't define the use of IPsec for a BRR.

Indeed, it hasn't text about BRR and IPsec.  But BRR is like a BAck
isn't it?  They use the same SA, so same IPsec processing rules would
apply, no?

>> IPsec is anyways a sensitive issue because we're talking three 
>> parties: two HAs (an initial and an "assigned") and one MN, 
>> presumably HAs exchange SAs.  Do you use the CA concept?
> 
> CA == ??

(Cert Authority...)

Remark also that BRR has currently no content, but is extensible to have
new mobility options, so one may wonder why was it made extensible.

Anyways, any other opinion on whether HA should send BRR or not is
useful to the discussion.

And you're right that it could be that BRR is sent only by CN.

>> I'll have to read it.
> 
> Please do, I'd appreciate any comments.

I'll have to read in detail.

For ha-switch:
-the content of ha-switch is same as DHAAD Reply.  While DHAAD Req
  arguably has anycast IPsec issues, DHAAD Reply doesn't.
-sec considerations section does not ack that an attacker HA may DoS a
  legitimate HA, both of which have SAs with MN.

For hareliability:
-not sure how HA SA and IPsec state synchronization can happen.
  It's out of scope for this doc - ok, but how can it happen?
-"All the home agents in the redundant home agent set share a virtual
   address and the routing will ensure only the Active Home Agent will be
   reachable using that virtual address." - is this DHAAD?

Just comments, it may be I haven't understood correctly the draft,
I'll read later, thanks,

Alex

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



From mip6-bounces@ietf.org Wed Jul 19 13:58:21 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G3GJP-0005Wb-Gy; Wed, 19 Jul 2006 13:58:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G3GJN-0005WV-Jt
	for mip6@ietf.org; Wed, 19 Jul 2006 13:58:17 -0400
Received: from mail1.azairenet.com ([66.92.223.4] helo=bart.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G3GJL-00029O-O4
	for mip6@ietf.org; Wed, 19 Jul 2006 13:58:17 -0400
Received: from [10.1.201.20] ([10.1.201.20]) by bart.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Wed, 19 Jul 2006 10:58:07 -0700
Message-ID: <44BE72AC.7080302@azairenet.com>
Date: Wed, 19 Jul 2006 10:58:04 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.4 (Windows/20060516)
MIME-Version: 1.0
To: James Kempf <kempf@docomolabs-usa.com>
Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
References: <033201c6aaa1$787be580$196115ac@dcml.docomolabsusa.com>	<7EB20EA0938B4D42A2D82689365C9B7A0CBDEE@NAEX14.na.qualcomm.com>	<eaa74a7e0607190138j79868bd3u48371dbcb8673fcb@mail.gmail.com>
	<01bc01c6ab4d$e6e2e9e0$196115ac@dcml.docomolabsusa.com>
In-Reply-To: <01bc01c6ab4d$e6e2e9e0$196115ac@dcml.docomolabsusa.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 19 Jul 2006 17:58:07.0973 (UTC)
	FILETIME=[E426D950:01C6AB5C]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

James Kempf wrote:
> Gerardo,
> 
> ----- Original Message ----- From: "Gerardo Giaretta" 
> <gerardo.giaretta@gmail.com>
> To:> - one is the SA lifetime. This is really an IKE/IPsec issue and should
>> be handled in IPsec (concluded) WG. As mentioned, this issue does not
>> apply only to MIP6; in 3GPP I-WLAN the MN has an IPsec tunnel with the
>> PDG and if the access network supports dormant mode, the MN cannot go
>> into dormant mode state in order to keep the SA up. I guess it may
>> apply also to MOBIKE.
>>
> 
> The IPsec WG doesn't exist anymore and neither does MOBIKE. MOBIKE was 
> closed recently. If the MIP WG decides that this is a problem that needs 
> to be solved, it cannot simply hand the problem off to another WG. 
> Either a new WG would need to be formed or the MIP WG would need to do 
> the work itself.

the work is too minor to form a WG. another option is an
individual submission with reviews from MIP6 WG and the
IPsec and MOBIKE mailing lists (which are still around).

> As George brought up, the two are linked. Unfortunately, given the way 
> IETF designs protocols (as "piece parts"), its difficult to optimize if 
> two independently designed protocols have in softstate dependences when 
> used together.
> 
> Perhaps we would solve the problem by defining an IKEv2 INFORMATIONAL 
> message to negotiate the timeout, then let the MN include a Mobility 
> Header Option to lengthen the BCE lifetime into that. 

oh no... these have to be two separate messages. mobility
options can be sent only in mobility header messages which
in turn can't be combined with any other protocol payload.
(piggybacking was removed. :)).

Vijay

This would limit
> the message exchange to one roundtrip (presuming no retransmission), 
> which I believe is important because an MN that wants to go into dormant 
> mode probably doesn't want to conduct a lot of messaging with the HA.
> 
>            jak
> 
> 
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6


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



From mip6-bounces@ietf.org Wed Jul 19 13:59:25 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G3GKT-0005kU-AS; Wed, 19 Jul 2006 13:59:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G3GKS-0005kP-LR
	for mip6@ietf.org; Wed, 19 Jul 2006 13:59:24 -0400
Received: from mail1.azairenet.com ([66.92.223.4] helo=bart.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G3GKR-0002Gw-0S
	for mip6@ietf.org; Wed, 19 Jul 2006 13:59:24 -0400
Received: from [10.1.201.20] ([10.1.201.20]) by bart.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Wed, 19 Jul 2006 10:59:20 -0700
Message-ID: <44BE72F8.9070103@azairenet.com>
Date: Wed, 19 Jul 2006 10:59:20 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.4 (Windows/20060516)
MIME-Version: 1.0
To: "Tsirtsis, George" <tsirtsis@qualcomm.com>
Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
References: <7EB20EA0938B4D42A2D82689365C9B7A0CBEC2@NAEX14.na.qualcomm.com>
In-Reply-To: <7EB20EA0938B4D42A2D82689365C9B7A0CBEC2@NAEX14.na.qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 19 Jul 2006 17:59:20.0472 (UTC)
	FILETIME=[0F5D5180:01C6AB5D]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6cca30437e2d04f45110f2ff8dc1b1d5
Cc: mip6@ietf.org, James Kempf <kempf@docomolabs-usa.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Tsirtsis, George wrote:

> WRT MIP, however, lengthening the lifetime could simply be a matter for
> sending another BU before going to dormant mode, rather than introducing
> a whole new message.

agree.

Vijay

> 
> My point is that it is not clear to me that MIP/IPSEC and other
> protocols need to understand "dormancy" as a mode of operation, as long
> as the soft state timers can be negotiated at will (within policy limits
> of course).
> 
> George
> 
>> -----Original Message-----
>> From: James Kempf [mailto:kempf@docomolabs-usa.com]
>> Sent: Wednesday, July 19, 2006 12:29 PM
>> To: Tsirtsis, George; Gerardo Giaretta
>> Cc: Chowdhury, Kuntal; mip6@ietf.org
>> Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert to
> HA?
>>
>> ----- Original Message -----
>> From: "Tsirtsis, George" <tsirtsis@qualcomm.com>
>> To: "Gerardo Giaretta" <gerardo.giaretta@gmail.com>; "James Kempf"
>> <kempf@docomolabs-usa.com>
>> Cc: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>;
> <mip6@ietf.org>
>> Sent: Wednesday, July 19, 2006 6:27 AM
>> Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode Alert to
> HA?
>>
>> IMHO It would be a mistake to introduce a mechanism that allows the MN
>> to stop sending BUs. This would essentially result in "hard state"
> which
>> is bad.
>>
>> Everyone repeat after me "hard state is bad"! ok, just joking :-)
>>
>> jak>> No, it isn't a joke. You're right.
>>
>> Seriously though, all we are talking about here is manipulating a set
> of
>> timers we have for all these processes so that the maintenance of the
>> soft state associated with MIP and IPSEC does not affect the mobile's
>> battery life. Set these timers to values in the order of many minutes
> or
>> even better hours and the power consumption becomes negligible since
> the
>> MN can be in dormant mode for most of the time. One should also
>> time-align such timers when possible so that the MN can wake up once,
>> refresh all its timers and then go back to sleep.
>>
>> jak>> I think the issue is that some operators may want to have a
> policy
>> that has different timer values for dormant and active mode hosts. And
>> what
>> if the timer values are set differently for different kinds of mobile
>> devices? A timer for an iPac might be different from a Toyota Prius,
>> because the amount of power available would be quite different.
>>
>> jak>> Anyway, there's still an issue with IKEv2 not allowing the timer
>> value
>> to be negotiated.
>>
>>             jak
>>
> 
> 
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6


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



From mip6-bounces@ietf.org Wed Jul 19 14:04:41 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G3GPS-0001p0-M6; Wed, 19 Jul 2006 14:04:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G3GPM-0001mc-6P
	for mip6@ietf.org; Wed, 19 Jul 2006 14:04:28 -0400
Received: from nf-out-0910.google.com ([64.233.182.185])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G3GPK-00037A-JV
	for mip6@ietf.org; Wed, 19 Jul 2006 14:04:28 -0400
Received: by nf-out-0910.google.com with SMTP id n15so365082nfc
	for <mip6@ietf.org>; Wed, 19 Jul 2006 11:04:25 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=TfUYW4FLfrClVnG3/XX5Iw3GZY87xmmzvZD75fEOBYV0ZVROQYBe0mQ0GyGhxVZfpHjdIX2RlBuPXeMWgnxUXkGS/eb2mTtaQ+VfRD7oLHgM3eejrsz4+0YefxojN6ywu320n+WXG4cdyM+rJ4nSIvs68OPzhQFKH0rfNLSFgNs=
Received: by 10.48.1.3 with SMTP id 3mr1894135nfa;
	Wed, 19 Jul 2006 11:02:47 -0700 (PDT)
Received: by 10.49.40.6 with HTTP; Wed, 19 Jul 2006 11:02:46 -0700 (PDT)
Message-ID: <eaa74a7e0607191102mc01d5afoe18c7191cf988c77@mail.gmail.com>
Date: Wed, 19 Jul 2006 20:02:46 +0200
From: "Gerardo Giaretta" <gerardo.giaretta@gmail.com>
To: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
In-Reply-To: <44BE72AC.7080302@azairenet.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <033201c6aaa1$787be580$196115ac@dcml.docomolabsusa.com>
	<7EB20EA0938B4D42A2D82689365C9B7A0CBDEE@NAEX14.na.qualcomm.com>
	<eaa74a7e0607190138j79868bd3u48371dbcb8673fcb@mail.gmail.com>
	<01bc01c6ab4d$e6e2e9e0$196115ac@dcml.docomolabsusa.com>
	<44BE72AC.7080302@azairenet.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Cc: mip6@ietf.org, James Kempf <kempf@docomolabs-usa.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

> > To:> - one is the SA lifetime. This is really an IKE/IPsec issue and should
> >> be handled in IPsec (concluded) WG. As mentioned, this issue does not
> >> apply only to MIP6; in 3GPP I-WLAN the MN has an IPsec tunnel with the
> >> PDG and if the access network supports dormant mode, the MN cannot go
> >> into dormant mode state in order to keep the SA up. I guess it may
> >> apply also to MOBIKE.
> >>
> >
> > The IPsec WG doesn't exist anymore and neither does MOBIKE. MOBIKE was
> > closed recently. If the MIP WG decides that this is a problem that needs
> > to be solved, it cannot simply hand the problem off to another WG.
> > Either a new WG would need to be formed or the MIP WG would need to do
> > the work itself.
>
> the work is too minor to form a WG. another option is an
> individual submission with reviews from MIP6 WG and the
> IPsec and MOBIKE mailing lists (which are still around).
>
> > As George brought up, the two are linked. Unfortunately, given the way
> > IETF designs protocols (as "piece parts"), its difficult to optimize if
> > two independently designed protocols have in softstate dependences when
> > used together.
> >
> > Perhaps we would solve the problem by defining an IKEv2 INFORMATIONAL
> > message to negotiate the timeout, then let the MN include a Mobility
> > Header Option to lengthen the BCE lifetime into that.
>
> oh no... these have to be two separate messages. mobility
> options can be sent only in mobility header messages which
> in turn can't be combined with any other protocol payload.
> (piggybacking was removed. :)).
>

I still see the IPsec/MOBIKE problem as separate from the MIP6 one.
Again it applies also to other scenarios than MIP6 mobility.

This was also discussed in WiMAX Forum for WiMAX and 3GPP
interworking. And IKEv2 does not allow to negotiate lifetimes.

Do people think that everybody can be fine just setting proper timers
administratively?

--Gerardo

> Vijay
>
> This would limit
> > the message exchange to one roundtrip (presuming no retransmission),
> > which I believe is important because an MN that wants to go into dormant
> > mode probably doesn't want to conduct a lot of messaging with the HA.
> >
> >            jak
> >
> >
> > _______________________________________________
> > Mip6 mailing list
> > Mip6@ietf.org
> > https://www1.ietf.org/mailman/listinfo/mip6
>
>

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



From mip6-bounces@ietf.org Wed Jul 19 14:06:43 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G3GRU-00042O-LE; Wed, 19 Jul 2006 14:06:40 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G3GRQ-000402-Dh
	for mip6@ietf.org; Wed, 19 Jul 2006 14:06:36 -0400
Received: from mail1.azairenet.com ([66.92.223.4] helo=bart.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G3GRO-0003UT-S5
	for mip6@ietf.org; Wed, 19 Jul 2006 14:06:36 -0400
Received: from [10.1.201.20] ([10.1.201.20]) by bart.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Wed, 19 Jul 2006 11:06:32 -0700
Message-ID: <44BE74A8.6000001@azairenet.com>
Date: Wed, 19 Jul 2006 11:06:32 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.4 (Windows/20060516)
MIME-Version: 1.0
To: Gerardo Giaretta <gerardo.giaretta@gmail.com>
Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
References: <033201c6aaa1$787be580$196115ac@dcml.docomolabsusa.com>	
	<7EB20EA0938B4D42A2D82689365C9B7A0CBDEE@NAEX14.na.qualcomm.com>	
	<eaa74a7e0607190138j79868bd3u48371dbcb8673fcb@mail.gmail.com>	
	<01bc01c6ab4d$e6e2e9e0$196115ac@dcml.docomolabsusa.com>	
	<44BE72AC.7080302@azairenet.com>
	<eaa74a7e0607191102mc01d5afoe18c7191cf988c77@mail.gmail.com>
In-Reply-To: <eaa74a7e0607191102mc01d5afoe18c7191cf988c77@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 19 Jul 2006 18:06:32.0810 (UTC)
	FILETIME=[110EDCA0:01C6AB5E]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Cc: mip6@ietf.org, James Kempf <kempf@docomolabs-usa.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Gerardo Giaretta wrote:

> I still see the IPsec/MOBIKE problem as separate from the MIP6 one.
> Again it applies also to other scenarios than MIP6 mobility.
> 
> This was also discussed in WiMAX Forum for WiMAX and 3GPP
> interworking. And IKEv2 does not allow to negotiate lifetimes.
> 
> Do people think that everybody can be fine just setting proper timers
> administratively?

IMO, an extension to IKEv2 to signal going to dormant mode,
which will avoid the mobile node having to send
keepalives/active traffic or respond to DPD messages, will
be useful.

Vijay

> 
> --Gerardo
> 
>> Vijay
>>
>> This would limit
>> > the message exchange to one roundtrip (presuming no retransmission),
>> > which I believe is important because an MN that wants to go into 
>> dormant
>> > mode probably doesn't want to conduct a lot of messaging with the HA.
>> >
>> >            jak
>> >
>> >
>> > _______________________________________________
>> > Mip6 mailing list
>> > Mip6@ietf.org
>> > https://www1.ietf.org/mailman/listinfo/mip6
>>
>>


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



From mip6-bounces@ietf.org Wed Jul 19 15:54:28 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G3I7l-00063L-VC; Wed, 19 Jul 2006 15:54:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G3I7k-00063G-LA
	for mip6@ietf.org; Wed, 19 Jul 2006 15:54:24 -0400
Received: from key1.docomolabs-usa.com ([216.98.102.225]
	helo=fridge.docomolabs-usa.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G3I7j-0003uA-9Z
	for mip6@ietf.org; Wed, 19 Jul 2006 15:54:24 -0400
Message-ID: <02b001c6ab6d$66dde180$196115ac@dcml.docomolabsusa.com>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Gerardo Giaretta" <gerardo.giaretta@gmail.com>,
	"Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
References: <033201c6aaa1$787be580$196115ac@dcml.docomolabsusa.com>
	<7EB20EA0938B4D42A2D82689365C9B7A0CBDEE@NAEX14.na.qualcomm.com>
	<eaa74a7e0607190138j79868bd3u48371dbcb8673fcb@mail.gmail.com>
	<01bc01c6ab4d$e6e2e9e0$196115ac@dcml.docomolabsusa.com>
	<44BE72AC.7080302@azairenet.com>
	<eaa74a7e0607191102mc01d5afoe18c7191cf988c77@mail.gmail.com>
Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
Date: Wed, 19 Jul 2006 12:56:19 -0700
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=response
Content-Transfer-Encoding: 7bit
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

> Do people think that everybody can be fine just setting proper timers
> administratively?
>


No, I don't think so. I think the mobile node needs the ability to negotiate 
the timer values.

            jak 



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



From mip6-bounces@ietf.org Wed Jul 19 16:42:54 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G3Isc-0002eb-Be; Wed, 19 Jul 2006 16:42:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G3Isb-0002eV-0m
	for mip6@ietf.org; Wed, 19 Jul 2006 16:42:49 -0400
Received: from atlrel7.hp.com ([156.153.255.213])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G3IsX-0002wg-IQ
	for mip6@ietf.org; Wed, 19 Jul 2006 16:42:49 -0400
Received: from smtp1.fc.hp.com (smtp1.fc.hp.com [15.15.136.127])
	by atlrel7.hp.com (Postfix) with ESMTP id 0F7F434209;
	Wed, 19 Jul 2006 16:42:45 -0400 (EDT)
Received: from [16.116.96.215] (spaceshipone.zko.hp.com [16.116.96.215])
	by smtp1.fc.hp.com (Postfix) with ESMTP id 963F554179;
	Wed, 19 Jul 2006 20:42:44 +0000 (UTC)
Message-ID: <44BE9943.7060308@hp.com>
Date: Wed, 19 Jul 2006 16:42:43 -0400
From: Brian Haley <brian.haley@hp.com>
Organization: Open Source and Linux Organization
User-Agent: Thunderbird 1.5.0.4 (X11/20060615)
MIME-Version: 1.0
To: Alexandru Petrescu <alexandru.petrescu@motorola.com>
Subject: Re: [Mip6] New charter item: HA assignment
References: <729b68be0607180431m773dc847qed3e7350819a8d04@mail.gmail.com>
	<44BD1105.5040904@motorola.com> <44BD3AA6.7070906@hp.com>
	<44BD5AEA.6020209@motorola.com> <44BE5953.6080602@hp.com>
	<44BE700D.5070700@motorola.com>
In-Reply-To: <44BE700D.5070700@motorola.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 67c1ea29f88502ef6a32ccec927970f0
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Alex,

>>>>> Another way is for the new HA to send Binding Refresh Request to MN 
>>>>> (even if it has no BC entry for it).
>>>>
>>>> BRR is sent from CN to MN, it is not defined to be sent from HA.
>>>
>>> I think that depends on each one's interpretation of 
>>> "correspondent".  I see BRR very well sent by HA to MN if BCE 
>>> lifetime expired and BU was lost.
>>
>> I don't know how you can interpret 3775 (or implement it) such that a
>>  HA can be a CN of the same MN at the same time.
> 
> I don't see the problem with that.
> 
> For some implementations it is useful/easy to have HA send BRR to MN.
> In this way MN does not need to implement additional timer of receiving
> BAck, only a timer for re-transmitting BU and to respond to BRR.
> 
> Wrt to how to read rfc3775 and think that CN can be a HA, this is an
> exercise indeed, but I'm tempted to do it because I also had
> to do it when thinking CN can be a MN.  And, if one thinks NEMOv6 then,
> and MN is a MR and MR can be a HA for mobiles in its moving network...
> CN can be a HA.
> 
> In the end, the BRR message should be implemented as send and receive in
> any entity running Mobile IPv6: CN, HA, MH, MR.

I'll agree to disagree.

> Take this 3775 text:
>> If the sender knows that the Binding Cache entry is still in active 
>> use, it MAY send a Binding Refresh Request message to the mobile node
>>  in an attempt to avoid this overhead and latency due to deleting and
>>  recreating the Binding Cache entry.

You're taking this out of context, this text was from this section of 3775:

   9. Correspondent Node Operation
   9.5.5.  Sending Binding Refresh Requests

> What "sender" maintains a Binding Cache?  Both CN and HA, only MN
> doesn't.  So MN would not send BRR.  But if MN is a CN to another MN
> then MN would send BRR too.

All nodes that implement mobility should have a binding cache, a MN is 
technically a CN.

> Take this other 3775 text:
>> This message [BRR] is always sent to the home address of the mobile node.
> 
> So HA sends BRR to the HoA, HA (same entity) intercepts it because proxy
> ND for HoA, and encapsulates and sends it to CoA.

You forgot the rest of the section:

    The correspondent node MAY retransmit Binding Refresh Request
    messages as long as the rate limitation is applied.  The
    correspondent node MUST stop retransmitting when it receives a
    Binding Update.

Again, you omitted the CN-specific text.

>> You're the HA or you aren't, and HAs don't send BRRs - TAHI would have 
>> a test for it if they could :)
> 
> I suppose TAHI's interpretation of 3775 is that HA doesn't send BRRs.
> Some implementations don't conform to TAHI then.

There are no implementations that conform to your interpretation, at 
least not at any Connectathon or ETSI event I've been to.  I didn't even 
implement BRR in my code since it's optional and mobility can continue 
without it, just not optimized.

> Remark also that BRR has currently no content, but is extensible to have
> new mobility options, so one may wonder why was it made extensible.

Well, all the mobility headers in 3775 support options (ie no fixed 
Length field), they all just don't have ones defined.

> Anyways, any other opinion on whether HA should send BRR or not is
> useful to the discussion.

I will not continue down that rathole, this is the last email...

> For ha-switch:
> -the content of ha-switch is same as DHAAD Reply.  While DHAAD Req
>  arguably has anycast IPsec issues, DHAAD Reply doesn't.

It is very similar to a DHAAD Reply.

> -sec considerations section does not ack that an attacker HA may DoS a
>  legitimate HA, both of which have SAs with MN.

The current ha-switch draft doesn't mention other HAs because the -00 
version has no support for the ha-reliability draft - the HA sending the 
switch must be the MNs current HA.  When we extend it to support it 
we'll add some text.  I would assume that any HA a MN has a security 
relationship with should be trusted enough to not send rogue DoS packets 
to it.

> For hareliability:
> -not sure how HA SA and IPsec state synchronization can happen.
>  It's out of scope for this doc - ok, but how can it happen?

The group of HAs share a trust relationship, maybe one of the other 
authors can answer that question as it's not my strong point.

> -"All the home agents in the redundant home agent set share a virtual
>   address and the routing will ensure only the Active Home Agent will be
>   reachable using that virtual address." - is this DHAAD?

No, just a virtual IPv6 address.

If you have comments on the other drafts you should probably start a new 
thread.

-Brian

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



From mip6-bounces@ietf.org Wed Jul 19 17:08:53 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G3JHm-0004Ci-0f; Wed, 19 Jul 2006 17:08:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G3JHk-0004CP-TH
	for mip6@ietf.org; Wed, 19 Jul 2006 17:08:48 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G3IQh-00007f-1I
	for mip6@ietf.org; Wed, 19 Jul 2006 16:13:59 -0400
Received: from key1.docomolabs-usa.com ([216.98.102.225]
	helo=fridge.docomolabs-usa.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1G3I43-0001vO-NT
	for mip6@ietf.org; Wed, 19 Jul 2006 15:50:37 -0400
Message-ID: <029101c6ab6c$dacc5640$196115ac@dcml.docomolabsusa.com>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Tsirtsis, George" <tsirtsis@qualcomm.com>,
	"Gerardo Giaretta" <gerardo.giaretta@gmail.com>
References: <7EB20EA0938B4D42A2D82689365C9B7A0CBEC2@NAEX14.na.qualcomm.com>
Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
Date: Wed, 19 Jul 2006 12:52:24 -0700
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Yes, as Vijay also indicated it would be good if IKEv2 had a way to
negotiate timers.

jak>> OK.

WRT MIP, however, lengthening the lifetime could simply be a matter for
sending another BU before going to dormant mode, rather than introducing
a whole new message.

jak>> Sure, that would work.

My point is that it is not clear to me that MIP/IPSEC and other
protocols need to understand "dormancy" as a mode of operation, as long
as the soft state timers can be negotiated at will (within policy limits
of course).

jak>> Yes, I agree. I am not arguing that we need to introduce any 
additional concept of "dormancy", despite the provisional names I gave to 
the proposed messages. I'd like to get the minimum set of functionality that 
will support Wimax Forum and other customers of MIP6, to encourage them to 
use IPsec and the rest of the MIP6 design, rather than coming up with their 
own solutions.

jak>> It sounds to me like that minimal set of functionality may be some way 
to negotiate the IKEv2 timers.

                 jak 



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



From mip6-bounces@ietf.org Wed Jul 19 17:14:15 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G3JN0-0005gs-Pt; Wed, 19 Jul 2006 17:14:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G3JMz-0005gl-1b
	for mip6@ietf.org; Wed, 19 Jul 2006 17:14:13 -0400
Received: from key1.docomolabs-usa.com ([216.98.102.225]
	helo=fridge.docomolabs-usa.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G3JMx-0002Pg-FK
	for mip6@ietf.org; Wed, 19 Jul 2006 17:14:13 -0400
Message-ID: <034e01c6ab78$8aa4d000$196115ac@dcml.docomolabsusa.com>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Brian Haley" <brian.haley@hp.com>,
	"Alexandru Petrescu" <alexandru.petrescu@motorola.com>
References: <729b68be0607180431m773dc847qed3e7350819a8d04@mail.gmail.com><44BD1105.5040904@motorola.com>
	<44BD3AA6.7070906@hp.com><44BD5AEA.6020209@motorola.com>
	<44BE5953.6080602@hp.com><44BE700D.5070700@motorola.com>
	<44BE9943.7060308@hp.com>
Subject: Re: [Mip6] New charter item: HA assignment
Date: Wed, 19 Jul 2006 14:16:03 -0700
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=response
Content-Transfer-Encoding: 7bit
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

>> For hareliability:
>> -not sure how HA SA and IPsec state synchronization can happen.
>>  It's out of scope for this doc - ok, but how can it happen?
>
> The group of HAs share a trust relationship, maybe one of the other 
> authors can answer that question as it's not my strong point.
>

Any "synchronication" would need to be at a pretty gross level. For example, 
all HAs have access to the same AAA backend so that they can authenticate an 
EAPoIPsec transaction. I don't think any attempt to synchronize by having 
the HAs share SA state would be acceptable to the Security Directorate, as 
it would raise an issue of cascading effects if one HA was compromised.

            jak 



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



From mip6-bounces@ietf.org Wed Jul 19 18:01:40 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G3K6r-0003Gn-7i; Wed, 19 Jul 2006 18:01:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G3K6o-0003Em-9V
	for mip6@ietf.org; Wed, 19 Jul 2006 18:01:34 -0400
Received: from ithilien.qualcomm.com ([129.46.51.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G3K3h-00053X-05
	for mip6@ietf.org; Wed, 19 Jul 2006 17:58:23 -0400
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
	k6JLwBEQ007340
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Wed, 19 Jul 2006 14:58:12 -0700
Received: from NAEXBR03.na.qualcomm.com (naexbr03.qualcomm.com
	[129.46.134.172])
	by magus.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id k6JLw8ii024445; 
	Wed, 19 Jul 2006 14:58:10 -0700 (PDT)
Received: from NAEX13.na.qualcomm.com ([129.46.51.248]) by
	NAEXBR03.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 19 Jul 2006 14:58:08 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
Date: Wed, 19 Jul 2006 14:55:49 -0700
Message-ID: <C24CB51D5AA800449982D9BCB90325130AC85A@NAEX13.na.qualcomm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
Thread-Index: AcarS7IRgAZ4svPKRqu9kOmYdgsjZgAMmbCS
References: <C24CB51D5AA800449982D9BCB90325130A11E4@NAEX13.na.qualcomm.com>
	<018c01c6ab4b$ee713010$196115ac@dcml.docomolabsusa.com>
From: "Narayanan, Vidya" <vidyan@qualcomm.com>
To: "James Kempf" <kempf@docomolabs-usa.com>,
	"Tsirtsis, George" <tsirtsis@qualcomm.com>,
	"Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
X-OriginalArrivalTime: 19 Jul 2006 21:58:08.0730 (UTC)
	FILETIME=[6BABFBA0:01C6AB7E]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: cc961b79af8d22f2640d5180a0dbc035
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0056664305=="
Errors-To: mip6-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0056664305==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C6AB7E.6B266693"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C6AB7E.6B266693
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

What would be the motivation for maintaining such mode specific timer =
values?=20
=20
Vidya

________________________________

From: James Kempf [mailto:kempf@docomolabs-usa.com]
Sent: Wed 7/19/2006 8:47 AM
To: Narayanan, Vidya; Tsirtsis, George; Vijay Devarapalli
Cc: mip6@ietf.org
Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert to =
HA?



The operator may want to keep active mode timers short, then set them =
longer
only if the mobile goes into dormant mode.

            jak



----- Original Message -----
From: "Narayanan, Vidya" <vidyan@qualcomm.com>
To: "Tsirtsis, George" <tsirtsis@qualcomm.com>; "Vijay Devarapalli"
<vijay.devarapalli@azairenet.com>
Cc: <mip6@ietf.org>; "James Kempf" <kempf@docomolabs-usa.com>
Sent: Tuesday, July 18, 2006 4:26 PM
Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode Alert to =
HA?


I'm just catching up with this discussion.

If the IPsec idle timer is at least equal to the BU lifetime, why is
there a need for any other signaling related to dormant mode? Given that
the timer values are a matter of policy, this should be do-able.

Vidya

> -----Original Message-----
> From: Tsirtsis, George [mailto:tsirtsis@qualcomm.com]
> Sent: Tuesday, July 18, 2006 3:11 PM
> To: Vijay Devarapalli
> Cc: mip6@ietf.org; James Kempf
> Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode
> Alert to HA?
>
> Yes, I meant DPD.
>
> There is a fate sharing here between MIP6 state and IPSEC
> state. I guess the SA lifetime and DPD timer was introduced
> to catch the general case but they do not make sense to be
> much different than the MIP lifetime when that is used.
>
> It is indeed strange, however, that IPSEC does not allow for
> negotiation of these parameters. I guess people will have to
> use reasonable values in each deployment depending what they
> are doing.
>
> George
>
> > -----Original Message-----
> > From: Vijay Devarapalli [mailto:vijay.devarapalli@azairenet.com]
> > Sent: Tuesday, July 18, 2006 6:06 PM
> > To: Tsirtsis, George
> > Cc: James Kempf; Chowdhury, Kuntal; mip6@ietf.org
> > Subject: Re: [Mip6] New Charter Item:Support for Dormant
> Mode Alert to
> HA?
> >
> > Tsirtsis, George wrote:
> > > So how often PDP messages are sent is also local policy?
> >
> > I guess you meant DPD. yes it is local policy. the initiator and
> > responder configure this independently.
> >
> > > In which case
> > > it can be configured to a time that makes sense for MIP
> or a given
> > > deployment scenario.
> >
> > Yes. however, the IPsec implementation should allow for
> sufficiently
> > large values for DPD timer. but then again DPD exists so
> that unwanted
> > IPsec state is removed if the other end goes down or if there is no
> > traffic for a long time.
> >
> > Vijay
> >
> > > George
> > >
> > >> -----Original Message-----
> > >> From: Vijay Devarapalli [mailto:vijay.devarapalli@azairenet.com]
> > >> Sent: Tuesday, July 18, 2006 5:42 PM
> > >> To: James Kempf
> > >> Cc: Tsirtsis, George; Chowdhury, Kuntal; mip6@ietf.org
> > >> Subject: Re: [Mip6] New Charter Item:Support for Dormant
> Mode Alert
> to
> > > HA?
> > >> James Kempf wrote:
> > >>> I don't know. What do operators typically set the SA
> lifetime to?
> > > Though
> > >>> perhaps this is an unanswerable question because, as yet, has
> > > anybody
> > >>> deployed MIPv6?
> > >> this is more of an IPsec issue. it depends on the local
> policy on
> > >> the initiator and responder. however, as long as there
> is traffic
> > >> and there are responses to DPD messages, the IPsec SA is not
> > >> deleted.
> > >>
> > >> Vijay
> > >>
> > >>> My only observation is that this seems to be an issue with Wimax
> > > Forum,
> > >>> and one of the primary motivators for wanting to use
> the RFC 4285
> > > Auth
> > >>> Option. If IETF and the MIP6 WG would like to encourage them to
> use
> > > IKE
> > >>> (as seemed to be the sentiment when RFC 4285 was discussed, and
> one
> > > of
> > >>> the reasons why it is not PS), it might be worthwhile to try to
> > > address
> > >>> their concerns.
> > >>>
> > >>>            jak
> > >>>
> > >>> ----- Original Message ----- From: "Tsirtsis, George"
> > >>> <tsirtsis@qualcomm.com>
> > >>> To: "James Kempf" <kempf@docomolabs-usa.com>;
> "Chowdhury, Kuntal"
> > >>> <kchowdhury@starentnetworks.com>
> > >>> Cc: <mip6@ietf.org>
> > >>> Sent: Tuesday, July 18, 2006 12:10 PM
> > >>> Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode
> Alert
> > > to
> > >> HA?
> > >>>
> > >>> May I ask, what is the typical lifetime of the SA and what would
> you
> > >>> lengthen it to?
> > >>> George
> > >>>
> > >>>> -----Original Message-----
> > >>>> From: James Kempf [mailto:kempf@docomolabs-usa.com]
> > >>>> Sent: Tuesday, July 18, 2006 2:43 PM
> > >>>> To: Chowdhury, Kuntal
> > >>>> Cc: mip6@ietf.org
> > >>>> Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode
> Alert
> > > to
> > >>> HA?
> > >>>
> > >>>> Kuntal,
> > >>>>
> > >>>> The intent is not to introduce something that the MN would send
> > > during
> > >>>> dormant mode. Indeed, as you have described, this would
> negatively
> > >>> impact
> > >>>
> > >>>> battery life.
> > >>>>
> > >>>> The intent is to provide a way for the MN to say that
> it is about
> > > to
> > >>> go
> > >>>
> > >>>> into
> > >>>> dormant mode, so please lengthen the IPsec SA timeout to avoid
> > > having
> > >>> it
> > >>>
> > >>>> expire for some longer period of time.
> > >>>>
> > >>>>             jak
> > >>>>
> > >>>> ----- Original Message -----
> > >>>> From: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
> > >>>> To: "James Kempf" <kempf@docomolabs-usa.com>
> > >>>> Cc: <mip6@ietf.org>
> > >>>> Sent: Tuesday, July 18, 2006 11:20 AM
> > >>>> Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode
> Alert
> > > to
> > >>> HA?
> > >>>
> > >>>>
> > >>>> James,
> > >>>>
> > >>>> This is a good discussion. Indeed the need for IPsec keepalives
> (or
> > >>> DPD)
> > >>>
> > >>>> over the air when the MN is dormant (or idle) is an
> issue in the
> > >>>> cellular networks. The issue is Not that there are no mip6
> messages
> > >>>> defined or the HA is not aware of dormancy. It is more of a
> paging
> > >>>> channel capacity issue, MN's battery life issue and
> the signaling
> > >>>> overhead to transport the keepalives for a dormant MN issue.
> > >>>>
> > >>>> So, any new message however small won't solve the
> problem, IMHO.
> > >>>>
> > >>>> -Kuntal
> > >>>>
> > >>>>
> > >>>>> -----Original Message-----
> > >>>>> From: James Kempf [mailto:kempf@docomolabs-usa.com]
> > >>>>> Sent: Tuesday, July 18, 2006 11:17 AM
> > >>>>> To: Vijay Devarapalli
> > >>>>> Cc: mip6@ietf.org
> > >>>>> Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode
> > > Alert
> > >>> to
> > >>>
> > >>>> HA?
> > >>>>> For security, the message would need to be sent within an SA.
> > > There
> > >>> is
> > >>>
> > >>>> a
> > >>>>> question about which.
> > >>>>>
> > >>>>> One possibility is to do a Mobility Extension (call
> the messages
> > >>>> Sleeping
> > >>>>> and WakingUp) and send it within the IPsec SA between
> the HA and
> > > MN.
> > >>>> The
> > >>>>> MN
> > >>>>> sends the Sleeping message when it is about to go into dormant
> > > mode,
> > >>>> it
> > >>>>> sends the WakingUp message when it comes out again.
> The WakingUp
> > >>>> message
> > >>>>> isn't needed for the MN to get mobility service, it is just
> there
> > >>> for
> > >>>
> > >>>>> optimizing the SA timeouts. This would require a
> special API on
> > > the
> > >>> HA
> > >>>
> > >>>>> between the MIP code and IKE code for the HA to
> extend the IPsec
> > > SA
> > >>>>> lifetime, similar to the one for IKEv1 mobility. The solution
> > > would
> > >>>> only
> > >>>>> be
> > >>>>> applicable to Mobile IP.
> > >>>>>
> > >>>>> The other possibility is to do an IKEv2 INFORMATIONAL message
> > > that
> > >>> is
> > >>>
> > >>>> sent
> > >>>>> within the IKE SA. It works similarly, but there would be no
> need
> > >>> for
> > >>>
> > >>>> any
> > >>>>> API on the HA, since the IKE code itself would process it
> > > (actually,
> > >>> I
> > >>>
> > >>>>> proposed something like this to the Mobike WG but they didn't
> see
> > >>> the
> > >>>
> > >>>> need
> > >>>>> for it). This would be applicable to both Mobike and Mobile IP
> > > (and
> > >>>> any
> > >>>>> other security protocol that uses IKEv2, so maybe HIP
> as well).
> > >>>>>
> > >>>>> One question is, does the HA need to do anything else
> if the MN
> > > goes
> > >>>> into
> > >>>>> dormant mode? I think there are lots of things it could do
> > > (lengthen
> > >>>> the
> > >>>>> BU
> > >>>>> timeout, apply a filter that is either mobile
> specified or part
> > > of
> > >>> the
> > >>>
> > >>>>> user's service profile with the operator to only
> allow specific
> > >>>> traffic
> > >>>>> through, etc.) but I would really like to keep things simple.
> > >>>>>
> > >>>>>             jak
> > >>>>>
> > >>>>> ----- Original Message -----
> > >>>>> From: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
> > >>>>> To: "James Kempf" <kempf@docomolabs-usa.com>
> > >>>>> Cc: <mip6@ietf.org>
> > >>>>> Sent: Monday, July 17, 2006 3:43 PM
> > >>>>> Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode
> > > Alert
> > >>> to
> > >>>
> > >>>> HA?
> > >>>>>
> > >>>>>> the dormant mode extensions sounds good to me. we
> could do this
> > >>>>>> extension. one issue to consider - what triggers
> this message?
> > >>>>>> how does Mobile IP know the mobile node is going
> into a dormant
> > >>>>>> mode. if we have the trigger we should be okay.
> > >>>>>>
> > >>>>>> but we have to check if this was the issue. with IKEv1 you
> > >>>>>> could negotiate a lifetime for the IPsec SA. IKEv2 does not
> > >>>>>> have the IPsec SA lifetime feature. so keepalives are needed.
> > >>>>>>
> > >>>>>> James Kempf wrote:
> > >>>>>>> I was at Wimax Forum last week and I think I now understand
> > > why
> > >>>> they
> > >>>>> and
> > >>>>>>> 3GPP2 want to use RFC 4285 auth option rather than
> IPsec. One
> > >>> issue
> > >>>
> > >>>> -
> > >>>>>>> lack of EAP support for client auth - is solved by IKEv2 and
> > > they
> > >>>> seem
> > >>>>> to
> > >>>>>>> now be moving in the direction of recommending
> IKEv2 if people
> > >>> want
> > >>>
> > >>>> to
> > >>>>>>> deploy IPsec.
> > >>>>>> yes this was one of the main issues.
> > >>>>>>
> > >>>>>> the way I saw it folks in 3GPP2 liked RFC 4285 because it is
> > >>>>>> very similar to the MIPv4 mechanism and they were
> comfortable
> > >>>>>> with it.
> > >>>>>>
> > >>>>>> Vijay
> > >>>>>>
> > >>>>>> But the other issue is a bit more complex. 802.16, like
> > >>>>>>> most cellular protocols, has extensive support for dormant
> > > mode,
> > >>>> and
> > >>>>>>> Wimax Forum is supporting dormant mode in their network
> > > design.
> > >>> If
> > >>>
> > >>>>> IPsec
> > >>>>>>> is used, then there is a risk when a mobile node goes into
> > >>> dormant
> > >>>
> > >>>> mode
> > >>>>>>> that the IPsec SA may time out. It is unfortunate that this
> > > was
> > >>> not
> > >>>
> > >>>>>>> brought up when the discussion about RFC 4285 was happening,
> > > but
> > >>> I
> > >>>
> > >>>>> think
> > >>>>>>> this might be something that the WG could work on
> now as part
> > > of
> > >>>> the
> > >>>>> new
> > >>>>>>> charter. This would make IKEv2/IPsec more attractive as a
> > >>> security
> > >>>
> > >>>>> option
> > >>>>>>> for cellular operators.
> > >>>>>>>
> > >>>>>>> Comments?
> > >>>>>>>
> > >>>>>>>            jak
> > >>>>>>>
> > >>>>>>>
> > >>>>>>>
> > >>>>>>> _______________________________________________
> > >>>>>>> Mip6 mailing list
> > >>>>>>> Mip6@ietf.org
> > >>>>>>> https://www1.ietf.org/mailman/listinfo/mip6
> > >>>>>>
> > >>>>>
> > >>>>>
> > >>>>> _______________________________________________
> > >>>>> Mip6 mailing list
> > >>>>> Mip6@ietf.org
> > >>>>> https://www1.ietf.org/mailman/listinfo/mip6
> > >>>>
> > >>>> "This email message and any attachments are confidential
> > > information
> > >>> of
> > >>>
> > >>>> Starent Networks, Corp. The information transmitted may not be
> used
> > > to
> > >>>> create or change any contractual obligations of
> Starent Networks,
> > >>> Corp.
> > >>>
> > >>>> Any
> > >>>> review, retransmission, dissemination or other use of,
> or taking
> of
> > >>> any
> > >>>
> > >>>> action in reliance upon this e-mail and its attachments by
> persons
> > > or
> > >>>> entities other than the intended recipient is
> prohibited. If you
> > > are
> > >>> not
> > >>>
> > >>>> the
> > >>>> intended recipient, please notify the sender immediately -- by
> > >>> replying to
> > >>>
> > >>>> this message or by sending an email to
> > > postmaster@starentnetworks.com
> > >>> --
> > >>>
> > >>>> and
> > >>>> destroy all copies of this message and any attachments without
> > > reading
> > >>> or
> > >>>
> > >>>> disclosing their contents. Thank you."
> > >>>>
> > >>>>
> > >>>>
> > >>>> _______________________________________________
> > >>>> Mip6 mailing list
> > >>>> Mip6@ietf.org
> > >>>> https://www1.ietf.org/mailman/listinfo/mip6
> > >>>
> > >>>
> > >>>
> > >>> _______________________________________________
> > >>> Mip6 mailing list
> > >>> Mip6@ietf.org
> > >>> https://www1.ietf.org/mailman/listinfo/mip6
> > >
>
>
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
>





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

<HTML dir=3Dltr><HEAD><TITLE>Re: [Mip6] New Charter Item:Support for =
Dormant Mode Alert to HA?</TITLE>=0A=
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dunicode">=0A=
<META content=3D"MSHTML 6.00.2900.2912" name=3DGENERATOR></HEAD>=0A=
<BODY>=0A=
<DIV id=3DidOWAReplyText53505 dir=3Dltr>=0A=
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 size=3D2>What would be =
the motivation for maintaining such mode specific timer values? =
</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Vidya</FONT></DIV></DIV>=0A=
<DIV dir=3Dltr><BR>=0A=
<HR tabIndex=3D-1>=0A=
<FONT face=3DTahoma size=3D2><B>From:</B> James Kempf =
[mailto:kempf@docomolabs-usa.com]<BR><B>Sent:</B> Wed 7/19/2006 8:47 =
AM<BR><B>To:</B> Narayanan, Vidya; Tsirtsis, George; Vijay =
Devarapalli<BR><B>Cc:</B> mip6@ietf.org<BR><B>Subject:</B> Re: [Mip6] =
New Charter Item:Support for Dormant Mode Alert to =
HA?<BR></FONT><BR></DIV>=0A=
<DIV>=0A=
<P><FONT size=3D2>The operator may want to keep active mode timers =
short, then set them longer<BR>only if the mobile goes into dormant =
mode.<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; jak<BR><BR><BR><BR>----- Original Message -----<BR>From: =
"Narayanan, Vidya" &lt;vidyan@qualcomm.com&gt;<BR>To: "Tsirtsis, George" =
&lt;tsirtsis@qualcomm.com&gt;; "Vijay =
Devarapalli"<BR>&lt;vijay.devarapalli@azairenet.com&gt;<BR>Cc: =
&lt;mip6@ietf.org&gt;; "James Kempf" =
&lt;kempf@docomolabs-usa.com&gt;<BR>Sent: Tuesday, July 18, 2006 4:26 =
PM<BR>Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode =
Alert to HA?<BR><BR><BR>I'm just catching up with this =
discussion.<BR><BR>If the IPsec idle timer is at least equal to the BU =
lifetime, why is<BR>there a need for any other signaling related to =
dormant mode? Given that<BR>the timer values are a matter of policy, =
this should be do-able.<BR><BR>Vidya<BR><BR>&gt; -----Original =
Message-----<BR>&gt; From: Tsirtsis, George [<A =
href=3D"mailto:tsirtsis@qualcomm.com">mailto:tsirtsis@qualcomm.com</A>]<B=
R>&gt; Sent: Tuesday, July 18, 2006 3:11 PM<BR>&gt; To: Vijay =
Devarapalli<BR>&gt; Cc: mip6@ietf.org; James Kempf<BR>&gt; Subject: RE: =
[Mip6] New Charter Item:Support for Dormant Mode<BR>&gt; Alert to =
HA?<BR>&gt;<BR>&gt; Yes, I meant DPD.<BR>&gt;<BR>&gt; There is a fate =
sharing here between MIP6 state and IPSEC<BR>&gt; state. I guess the SA =
lifetime and DPD timer was introduced<BR>&gt; to catch the general case =
but they do not make sense to be<BR>&gt; much different than the MIP =
lifetime when that is used.<BR>&gt;<BR>&gt; It is indeed strange, =
however, that IPSEC does not allow for<BR>&gt; negotiation of these =
parameters. I guess people will have to<BR>&gt; use reasonable values in =
each deployment depending what they<BR>&gt; are doing.<BR>&gt;<BR>&gt; =
George<BR>&gt;<BR>&gt; &gt; -----Original Message-----<BR>&gt; &gt; =
From: Vijay Devarapalli [<A =
href=3D"mailto:vijay.devarapalli@azairenet.com">mailto:vijay.devarapalli@=
azairenet.com</A>]<BR>&gt; &gt; Sent: Tuesday, July 18, 2006 6:06 =
PM<BR>&gt; &gt; To: Tsirtsis, George<BR>&gt; &gt; Cc: James Kempf; =
Chowdhury, Kuntal; mip6@ietf.org<BR>&gt; &gt; Subject: Re: [Mip6] New =
Charter Item:Support for Dormant<BR>&gt; Mode Alert to<BR>&gt; =
HA?<BR>&gt; &gt;<BR>&gt; &gt; Tsirtsis, George wrote:<BR>&gt; &gt; &gt; =
So how often PDP messages are sent is also local policy?<BR>&gt; =
&gt;<BR>&gt; &gt; I guess you meant DPD. yes it is local policy. the =
initiator and<BR>&gt; &gt; responder configure this =
independently.<BR>&gt; &gt;<BR>&gt; &gt; &gt; In which case<BR>&gt; &gt; =
&gt; it can be configured to a time that makes sense for MIP<BR>&gt; or =
a given<BR>&gt; &gt; &gt; deployment scenario.<BR>&gt; &gt;<BR>&gt; &gt; =
Yes. however, the IPsec implementation should allow for<BR>&gt; =
sufficiently<BR>&gt; &gt; large values for DPD timer. but then again DPD =
exists so<BR>&gt; that unwanted<BR>&gt; &gt; IPsec state is removed if =
the other end goes down or if there is no<BR>&gt; &gt; traffic for a =
long time.<BR>&gt; &gt;<BR>&gt; &gt; Vijay<BR>&gt; &gt;<BR>&gt; &gt; =
&gt; George<BR>&gt; &gt; &gt;<BR>&gt; &gt; &gt;&gt; -----Original =
Message-----<BR>&gt; &gt; &gt;&gt; From: Vijay Devarapalli [<A =
href=3D"mailto:vijay.devarapalli@azairenet.com">mailto:vijay.devarapalli@=
azairenet.com</A>]<BR>&gt; &gt; &gt;&gt; Sent: Tuesday, July 18, 2006 =
5:42 PM<BR>&gt; &gt; &gt;&gt; To: James Kempf<BR>&gt; &gt; &gt;&gt; Cc: =
Tsirtsis, George; Chowdhury, Kuntal; mip6@ietf.org<BR>&gt; &gt; &gt;&gt; =
Subject: Re: [Mip6] New Charter Item:Support for Dormant<BR>&gt; Mode =
Alert<BR>&gt; to<BR>&gt; &gt; &gt; HA?<BR>&gt; &gt; &gt;&gt; James Kempf =
wrote:<BR>&gt; &gt; &gt;&gt;&gt; I don't know. What do operators =
typically set the SA<BR>&gt; lifetime to?<BR>&gt; &gt; &gt; =
Though<BR>&gt; &gt; &gt;&gt;&gt; perhaps this is an unanswerable =
question because, as yet, has<BR>&gt; &gt; &gt; anybody<BR>&gt; &gt; =
&gt;&gt;&gt; deployed MIPv6?<BR>&gt; &gt; &gt;&gt; this is more of an =
IPsec issue. it depends on the local<BR>&gt; policy on<BR>&gt; &gt; =
&gt;&gt; the initiator and responder. however, as long as there<BR>&gt; =
is traffic<BR>&gt; &gt; &gt;&gt; and there are responses to DPD =
messages, the IPsec SA is not<BR>&gt; &gt; &gt;&gt; deleted.<BR>&gt; =
&gt; &gt;&gt;<BR>&gt; &gt; &gt;&gt; Vijay<BR>&gt; &gt; &gt;&gt;<BR>&gt; =
&gt; &gt;&gt;&gt; My only observation is that this seems to be an issue =
with Wimax<BR>&gt; &gt; &gt; Forum,<BR>&gt; &gt; &gt;&gt;&gt; and one of =
the primary motivators for wanting to use<BR>&gt; the RFC 4285<BR>&gt; =
&gt; &gt; Auth<BR>&gt; &gt; &gt;&gt;&gt; Option. If IETF and the MIP6 WG =
would like to encourage them to<BR>&gt; use<BR>&gt; &gt; &gt; =
IKE<BR>&gt; &gt; &gt;&gt;&gt; (as seemed to be the sentiment when RFC =
4285 was discussed, and<BR>&gt; one<BR>&gt; &gt; &gt; of<BR>&gt; &gt; =
&gt;&gt;&gt; the reasons why it is not PS), it might be worthwhile to =
try to<BR>&gt; &gt; &gt; address<BR>&gt; &gt; &gt;&gt;&gt; their =
concerns.<BR>&gt; &gt; &gt;&gt;&gt;<BR>&gt; &gt; =
&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; jak<BR>&gt; &gt; &gt;&gt;&gt;<BR>&gt; &gt; &gt;&gt;&gt; ----- =
Original Message ----- From: "Tsirtsis, George"<BR>&gt; &gt; =
&gt;&gt;&gt; &lt;tsirtsis@qualcomm.com&gt;<BR>&gt; &gt; &gt;&gt;&gt; To: =
"James Kempf" &lt;kempf@docomolabs-usa.com&gt;;<BR>&gt; "Chowdhury, =
Kuntal"<BR>&gt; &gt; &gt;&gt;&gt; =
&lt;kchowdhury@starentnetworks.com&gt;<BR>&gt; &gt; &gt;&gt;&gt; Cc: =
&lt;mip6@ietf.org&gt;<BR>&gt; &gt; &gt;&gt;&gt; Sent: Tuesday, July 18, =
2006 12:10 PM<BR>&gt; &gt; &gt;&gt;&gt; Subject: RE: [Mip6] New Charter =
Item:Support for Dormant Mode<BR>&gt; Alert<BR>&gt; &gt; &gt; to<BR>&gt; =
&gt; &gt;&gt; HA?<BR>&gt; &gt; &gt;&gt;&gt;<BR>&gt; &gt; &gt;&gt;&gt; =
May I ask, what is the typical lifetime of the SA and what would<BR>&gt; =
you<BR>&gt; &gt; &gt;&gt;&gt; lengthen it to?<BR>&gt; &gt; &gt;&gt;&gt; =
George<BR>&gt; &gt; &gt;&gt;&gt;<BR>&gt; &gt; &gt;&gt;&gt;&gt; =
-----Original Message-----<BR>&gt; &gt; &gt;&gt;&gt;&gt; From: James =
Kempf [<A =
href=3D"mailto:kempf@docomolabs-usa.com">mailto:kempf@docomolabs-usa.com<=
/A>]<BR>&gt; &gt; &gt;&gt;&gt;&gt; Sent: Tuesday, July 18, 2006 2:43 =
PM<BR>&gt; &gt; &gt;&gt;&gt;&gt; To: Chowdhury, Kuntal<BR>&gt; &gt; =
&gt;&gt;&gt;&gt; Cc: mip6@ietf.org<BR>&gt; &gt; &gt;&gt;&gt;&gt; =
Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode<BR>&gt; =
Alert<BR>&gt; &gt; &gt; to<BR>&gt; &gt; &gt;&gt;&gt; HA?<BR>&gt; &gt; =
&gt;&gt;&gt;<BR>&gt; &gt; &gt;&gt;&gt;&gt; Kuntal,<BR>&gt; &gt; =
&gt;&gt;&gt;&gt;<BR>&gt; &gt; &gt;&gt;&gt;&gt; The intent is not to =
introduce something that the MN would send<BR>&gt; &gt; &gt; =
during<BR>&gt; &gt; &gt;&gt;&gt;&gt; dormant mode. Indeed, as you have =
described, this would<BR>&gt; negatively<BR>&gt; &gt; &gt;&gt;&gt; =
impact<BR>&gt; &gt; &gt;&gt;&gt;<BR>&gt; &gt; &gt;&gt;&gt;&gt; battery =
life.<BR>&gt; &gt; &gt;&gt;&gt;&gt;<BR>&gt; &gt; &gt;&gt;&gt;&gt; The =
intent is to provide a way for the MN to say that<BR>&gt; it is =
about<BR>&gt; &gt; &gt; to<BR>&gt; &gt; &gt;&gt;&gt; go<BR>&gt; &gt; =
&gt;&gt;&gt;<BR>&gt; &gt; &gt;&gt;&gt;&gt; into<BR>&gt; &gt; =
&gt;&gt;&gt;&gt; dormant mode, so please lengthen the IPsec SA timeout =
to avoid<BR>&gt; &gt; &gt; having<BR>&gt; &gt; &gt;&gt;&gt; it<BR>&gt; =
&gt; &gt;&gt;&gt;<BR>&gt; &gt; &gt;&gt;&gt;&gt; expire for some longer =
period of time.<BR>&gt; &gt; &gt;&gt;&gt;&gt;<BR>&gt; &gt; =
&gt;&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; jak<BR>&gt; &gt; &gt;&gt;&gt;&gt;<BR>&gt; &gt; =
&gt;&gt;&gt;&gt; ----- Original Message -----<BR>&gt; &gt; =
&gt;&gt;&gt;&gt; From: "Chowdhury, Kuntal" =
&lt;kchowdhury@starentnetworks.com&gt;<BR>&gt; &gt; &gt;&gt;&gt;&gt; To: =
"James Kempf" &lt;kempf@docomolabs-usa.com&gt;<BR>&gt; &gt; =
&gt;&gt;&gt;&gt; Cc: &lt;mip6@ietf.org&gt;<BR>&gt; &gt; &gt;&gt;&gt;&gt; =
Sent: Tuesday, July 18, 2006 11:20 AM<BR>&gt; &gt; &gt;&gt;&gt;&gt; =
Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode<BR>&gt; =
Alert<BR>&gt; &gt; &gt; to<BR>&gt; &gt; &gt;&gt;&gt; HA?<BR>&gt; &gt; =
&gt;&gt;&gt;<BR>&gt; &gt; &gt;&gt;&gt;&gt;<BR>&gt; &gt; &gt;&gt;&gt;&gt; =
James,<BR>&gt; &gt; &gt;&gt;&gt;&gt;<BR>&gt; &gt; &gt;&gt;&gt;&gt; This =
is a good discussion. Indeed the need for IPsec keepalives<BR>&gt; =
(or<BR>&gt; &gt; &gt;&gt;&gt; DPD)<BR>&gt; &gt; &gt;&gt;&gt;<BR>&gt; =
&gt; &gt;&gt;&gt;&gt; over the air when the MN is dormant (or idle) is =
an<BR>&gt; issue in the<BR>&gt; &gt; &gt;&gt;&gt;&gt; cellular networks. =
The issue is Not that there are no mip6<BR>&gt; messages<BR>&gt; &gt; =
&gt;&gt;&gt;&gt; defined or the HA is not aware of dormancy. It is more =
of a<BR>&gt; paging<BR>&gt; &gt; &gt;&gt;&gt;&gt; channel capacity =
issue, MN's battery life issue and<BR>&gt; the signaling<BR>&gt; &gt; =
&gt;&gt;&gt;&gt; overhead to transport the keepalives for a dormant MN =
issue.<BR>&gt; &gt; &gt;&gt;&gt;&gt;<BR>&gt; &gt; &gt;&gt;&gt;&gt; So, =
any new message however small won't solve the<BR>&gt; problem, =
IMHO.<BR>&gt; &gt; &gt;&gt;&gt;&gt;<BR>&gt; &gt; &gt;&gt;&gt;&gt; =
-Kuntal<BR>&gt; &gt; &gt;&gt;&gt;&gt;<BR>&gt; &gt; =
&gt;&gt;&gt;&gt;<BR>&gt; &gt; &gt;&gt;&gt;&gt;&gt; -----Original =
Message-----<BR>&gt; &gt; &gt;&gt;&gt;&gt;&gt; From: James Kempf [<A =
href=3D"mailto:kempf@docomolabs-usa.com">mailto:kempf@docomolabs-usa.com<=
/A>]<BR>&gt; &gt; &gt;&gt;&gt;&gt;&gt; Sent: Tuesday, July 18, 2006 =
11:17 AM<BR>&gt; &gt; &gt;&gt;&gt;&gt;&gt; To: Vijay Devarapalli<BR>&gt; =
&gt; &gt;&gt;&gt;&gt;&gt; Cc: mip6@ietf.org<BR>&gt; &gt; =
&gt;&gt;&gt;&gt;&gt; Subject: Re: [Mip6] New Charter Item:Support for =
Dormant Mode<BR>&gt; &gt; &gt; Alert<BR>&gt; &gt; &gt;&gt;&gt; =
to<BR>&gt; &gt; &gt;&gt;&gt;<BR>&gt; &gt; &gt;&gt;&gt;&gt; HA?<BR>&gt; =
&gt; &gt;&gt;&gt;&gt;&gt; For security, the message would need to be =
sent within an SA.<BR>&gt; &gt; &gt; There<BR>&gt; &gt; &gt;&gt;&gt; =
is<BR>&gt; &gt; &gt;&gt;&gt;<BR>&gt; &gt; &gt;&gt;&gt;&gt; a<BR>&gt; =
&gt; &gt;&gt;&gt;&gt;&gt; question about which.<BR>&gt; &gt; =
&gt;&gt;&gt;&gt;&gt;<BR>&gt; &gt; &gt;&gt;&gt;&gt;&gt; One possibility =
is to do a Mobility Extension (call<BR>&gt; the messages<BR>&gt; &gt; =
&gt;&gt;&gt;&gt; Sleeping<BR>&gt; &gt; &gt;&gt;&gt;&gt;&gt; and =
WakingUp) and send it within the IPsec SA between<BR>&gt; the HA =
and<BR>&gt; &gt; &gt; MN.<BR>&gt; &gt; &gt;&gt;&gt;&gt; The<BR>&gt; &gt; =
&gt;&gt;&gt;&gt;&gt; MN<BR>&gt; &gt; &gt;&gt;&gt;&gt;&gt; sends the =
Sleeping message when it is about to go into dormant<BR>&gt; &gt; &gt; =
mode,<BR>&gt; &gt; &gt;&gt;&gt;&gt; it<BR>&gt; &gt; &gt;&gt;&gt;&gt;&gt; =
sends the WakingUp message when it comes out again.<BR>&gt; The =
WakingUp<BR>&gt; &gt; &gt;&gt;&gt;&gt; message<BR>&gt; &gt; =
&gt;&gt;&gt;&gt;&gt; isn't needed for the MN to get mobility service, it =
is just<BR>&gt; there<BR>&gt; &gt; &gt;&gt;&gt; for<BR>&gt; &gt; =
&gt;&gt;&gt;<BR>&gt; &gt; &gt;&gt;&gt;&gt;&gt; optimizing the SA =
timeouts. This would require a<BR>&gt; special API on<BR>&gt; &gt; &gt; =
the<BR>&gt; &gt; &gt;&gt;&gt; HA<BR>&gt; &gt; &gt;&gt;&gt;<BR>&gt; &gt; =
&gt;&gt;&gt;&gt;&gt; between the MIP code and IKE code for the HA =
to<BR>&gt; extend the IPsec<BR>&gt; &gt; &gt; SA<BR>&gt; &gt; =
&gt;&gt;&gt;&gt;&gt; lifetime, similar to the one for IKEv1 mobility. =
The solution<BR>&gt; &gt; &gt; would<BR>&gt; &gt; &gt;&gt;&gt;&gt; =
only<BR>&gt; &gt; &gt;&gt;&gt;&gt;&gt; be<BR>&gt; &gt; =
&gt;&gt;&gt;&gt;&gt; applicable to Mobile IP.<BR>&gt; &gt; =
&gt;&gt;&gt;&gt;&gt;<BR>&gt; &gt; &gt;&gt;&gt;&gt;&gt; The other =
possibility is to do an IKEv2 INFORMATIONAL message<BR>&gt; &gt; &gt; =
that<BR>&gt; &gt; &gt;&gt;&gt; is<BR>&gt; &gt; &gt;&gt;&gt;<BR>&gt; &gt; =
&gt;&gt;&gt;&gt; sent<BR>&gt; &gt; &gt;&gt;&gt;&gt;&gt; within the IKE =
SA. It works similarly, but there would be no<BR>&gt; need<BR>&gt; &gt; =
&gt;&gt;&gt; for<BR>&gt; &gt; &gt;&gt;&gt;<BR>&gt; &gt; &gt;&gt;&gt;&gt; =
any<BR>&gt; &gt; &gt;&gt;&gt;&gt;&gt; API on the HA, since the IKE code =
itself would process it<BR>&gt; &gt; &gt; (actually,<BR>&gt; &gt; =
&gt;&gt;&gt; I<BR>&gt; &gt; &gt;&gt;&gt;<BR>&gt; &gt; =
&gt;&gt;&gt;&gt;&gt; proposed something like this to the Mobike WG but =
they didn't<BR>&gt; see<BR>&gt; &gt; &gt;&gt;&gt; the<BR>&gt; &gt; =
&gt;&gt;&gt;<BR>&gt; &gt; &gt;&gt;&gt;&gt; need<BR>&gt; &gt; =
&gt;&gt;&gt;&gt;&gt; for it). This would be applicable to both Mobike =
and Mobile IP<BR>&gt; &gt; &gt; (and<BR>&gt; &gt; &gt;&gt;&gt;&gt; =
any<BR>&gt; &gt; &gt;&gt;&gt;&gt;&gt; other security protocol that uses =
IKEv2, so maybe HIP<BR>&gt; as well).<BR>&gt; &gt; =
&gt;&gt;&gt;&gt;&gt;<BR>&gt; &gt; &gt;&gt;&gt;&gt;&gt; One question is, =
does the HA need to do anything else<BR>&gt; if the MN<BR>&gt; &gt; &gt; =
goes<BR>&gt; &gt; &gt;&gt;&gt;&gt; into<BR>&gt; &gt; =
&gt;&gt;&gt;&gt;&gt; dormant mode? I think there are lots of things it =
could do<BR>&gt; &gt; &gt; (lengthen<BR>&gt; &gt; &gt;&gt;&gt;&gt; =
the<BR>&gt; &gt; &gt;&gt;&gt;&gt;&gt; BU<BR>&gt; &gt; =
&gt;&gt;&gt;&gt;&gt; timeout, apply a filter that is either =
mobile<BR>&gt; specified or part<BR>&gt; &gt; &gt; of<BR>&gt; &gt; =
&gt;&gt;&gt; the<BR>&gt; &gt; &gt;&gt;&gt;<BR>&gt; &gt; =
&gt;&gt;&gt;&gt;&gt; user's service profile with the operator to =
only<BR>&gt; allow specific<BR>&gt; &gt; &gt;&gt;&gt;&gt; =
traffic<BR>&gt; &gt; &gt;&gt;&gt;&gt;&gt; through, etc.) but I would =
really like to keep things simple.<BR>&gt; &gt; =
&gt;&gt;&gt;&gt;&gt;<BR>&gt; &gt; =
&gt;&gt;&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; jak<BR>&gt; &gt; &gt;&gt;&gt;&gt;&gt;<BR>&gt; &gt; =
&gt;&gt;&gt;&gt;&gt; ----- Original Message -----<BR>&gt; &gt; =
&gt;&gt;&gt;&gt;&gt; From: "Vijay Devarapalli" =
&lt;vijay.devarapalli@azairenet.com&gt;<BR>&gt; &gt; =
&gt;&gt;&gt;&gt;&gt; To: "James Kempf" =
&lt;kempf@docomolabs-usa.com&gt;<BR>&gt; &gt; &gt;&gt;&gt;&gt;&gt; Cc: =
&lt;mip6@ietf.org&gt;<BR>&gt; &gt; &gt;&gt;&gt;&gt;&gt; Sent: Monday, =
July 17, 2006 3:43 PM<BR>&gt; &gt; &gt;&gt;&gt;&gt;&gt; Subject: Re: =
[Mip6] New Charter Item:Support for Dormant Mode<BR>&gt; &gt; &gt; =
Alert<BR>&gt; &gt; &gt;&gt;&gt; to<BR>&gt; &gt; &gt;&gt;&gt;<BR>&gt; =
&gt; &gt;&gt;&gt;&gt; HA?<BR>&gt; &gt; &gt;&gt;&gt;&gt;&gt;<BR>&gt; &gt; =
&gt;&gt;&gt;&gt;&gt;&gt; the dormant mode extensions sounds good to me. =
we<BR>&gt; could do this<BR>&gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt; =
extension. one issue to consider - what triggers<BR>&gt; this =
message?<BR>&gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt; how does Mobile IP know =
the mobile node is going<BR>&gt; into a dormant<BR>&gt; &gt; =
&gt;&gt;&gt;&gt;&gt;&gt; mode. if we have the trigger we should be =
okay.<BR>&gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt;<BR>&gt; &gt; =
&gt;&gt;&gt;&gt;&gt;&gt; but we have to check if this was the issue. =
with IKEv1 you<BR>&gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt; could negotiate a =
lifetime for the IPsec SA. IKEv2 does not<BR>&gt; &gt; =
&gt;&gt;&gt;&gt;&gt;&gt; have the IPsec SA lifetime feature. so =
keepalives are needed.<BR>&gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt;<BR>&gt; =
&gt; &gt;&gt;&gt;&gt;&gt;&gt; James Kempf wrote:<BR>&gt; &gt; =
&gt;&gt;&gt;&gt;&gt;&gt;&gt; I was at Wimax Forum last week and I think =
I now understand<BR>&gt; &gt; &gt; why<BR>&gt; &gt; &gt;&gt;&gt;&gt; =
they<BR>&gt; &gt; &gt;&gt;&gt;&gt;&gt; and<BR>&gt; &gt; =
&gt;&gt;&gt;&gt;&gt;&gt;&gt; 3GPP2 want to use RFC 4285 auth option =
rather than<BR>&gt; IPsec. One<BR>&gt; &gt; &gt;&gt;&gt; issue<BR>&gt; =
&gt; &gt;&gt;&gt;<BR>&gt; &gt; &gt;&gt;&gt;&gt; -<BR>&gt; &gt; =
&gt;&gt;&gt;&gt;&gt;&gt;&gt; lack of EAP support for client auth - is =
solved by IKEv2 and<BR>&gt; &gt; &gt; they<BR>&gt; &gt; &gt;&gt;&gt;&gt; =
seem<BR>&gt; &gt; &gt;&gt;&gt;&gt;&gt; to<BR>&gt; &gt; =
&gt;&gt;&gt;&gt;&gt;&gt;&gt; now be moving in the direction of =
recommending<BR>&gt; IKEv2 if people<BR>&gt; &gt; &gt;&gt;&gt; =
want<BR>&gt; &gt; &gt;&gt;&gt;<BR>&gt; &gt; &gt;&gt;&gt;&gt; to<BR>&gt; =
&gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; deploy IPsec.<BR>&gt; &gt; =
&gt;&gt;&gt;&gt;&gt;&gt; yes this was one of the main issues.<BR>&gt; =
&gt; &gt;&gt;&gt;&gt;&gt;&gt;<BR>&gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt; the =
way I saw it folks in 3GPP2 liked RFC 4285 because it is<BR>&gt; &gt; =
&gt;&gt;&gt;&gt;&gt;&gt; very similar to the MIPv4 mechanism and they =
were<BR>&gt; comfortable<BR>&gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt; with =
it.<BR>&gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt;<BR>&gt; &gt; =
&gt;&gt;&gt;&gt;&gt;&gt; Vijay<BR>&gt; &gt; =
&gt;&gt;&gt;&gt;&gt;&gt;<BR>&gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt; But the =
other issue is a bit more complex. 802.16, like<BR>&gt; &gt; =
&gt;&gt;&gt;&gt;&gt;&gt;&gt; most cellular protocols, has extensive =
support for dormant<BR>&gt; &gt; &gt; mode,<BR>&gt; &gt; =
&gt;&gt;&gt;&gt; and<BR>&gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; Wimax =
Forum is supporting dormant mode in their network<BR>&gt; &gt; &gt; =
design.<BR>&gt; &gt; &gt;&gt;&gt; If<BR>&gt; &gt; &gt;&gt;&gt;<BR>&gt; =
&gt; &gt;&gt;&gt;&gt;&gt; IPsec<BR>&gt; &gt; =
&gt;&gt;&gt;&gt;&gt;&gt;&gt; is used, then there is a risk when a mobile =
node goes into<BR>&gt; &gt; &gt;&gt;&gt; dormant<BR>&gt; &gt; =
&gt;&gt;&gt;<BR>&gt; &gt; &gt;&gt;&gt;&gt; mode<BR>&gt; &gt; =
&gt;&gt;&gt;&gt;&gt;&gt;&gt; that the IPsec SA may time out. It is =
unfortunate that this<BR>&gt; &gt; &gt; was<BR>&gt; &gt; &gt;&gt;&gt; =
not<BR>&gt; &gt; &gt;&gt;&gt;<BR>&gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; =
brought up when the discussion about RFC 4285 was happening,<BR>&gt; =
&gt; &gt; but<BR>&gt; &gt; &gt;&gt;&gt; I<BR>&gt; &gt; =
&gt;&gt;&gt;<BR>&gt; &gt; &gt;&gt;&gt;&gt;&gt; think<BR>&gt; &gt; =
&gt;&gt;&gt;&gt;&gt;&gt;&gt; this might be something that the WG could =
work on<BR>&gt; now as part<BR>&gt; &gt; &gt; of<BR>&gt; &gt; =
&gt;&gt;&gt;&gt; the<BR>&gt; &gt; &gt;&gt;&gt;&gt;&gt; new<BR>&gt; &gt; =
&gt;&gt;&gt;&gt;&gt;&gt;&gt; charter. This would make IKEv2/IPsec more =
attractive as a<BR>&gt; &gt; &gt;&gt;&gt; security<BR>&gt; &gt; =
&gt;&gt;&gt;<BR>&gt; &gt; &gt;&gt;&gt;&gt;&gt; option<BR>&gt; &gt; =
&gt;&gt;&gt;&gt;&gt;&gt;&gt; for cellular operators.<BR>&gt; &gt; =
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<BR>&gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; =
Comments?<BR>&gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt;<BR>&gt; &gt; =
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp; jak<BR>&gt; &gt; =
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<BR>&gt; &gt; =
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<BR>&gt; &gt; =
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<BR>&gt; &gt; &gt;&gt;&gt;&gt;&gt;&gt;&gt; =
_______________________________________________<BR>&gt; &gt; =
&gt;&gt;&gt;&gt;&gt;&gt;&gt; Mip6 mailing list<BR>&gt; &gt; =
&gt;&gt;&gt;&gt;&gt;&gt;&gt; Mip6@ietf.org<BR>&gt; &gt; =
&gt;&gt;&gt;&gt;&gt;&gt;&gt; <A =
href=3D"https://www1.ietf.org/mailman/listinfo/mip6">https://www1.ietf.or=
g/mailman/listinfo/mip6</A><BR>&gt; &gt; =
&gt;&gt;&gt;&gt;&gt;&gt;<BR>&gt; &gt; &gt;&gt;&gt;&gt;&gt;<BR>&gt; &gt; =
&gt;&gt;&gt;&gt;&gt;<BR>&gt; &gt; &gt;&gt;&gt;&gt;&gt; =
_______________________________________________<BR>&gt; &gt; =
&gt;&gt;&gt;&gt;&gt; Mip6 mailing list<BR>&gt; &gt; &gt;&gt;&gt;&gt;&gt; =
Mip6@ietf.org<BR>&gt; &gt; &gt;&gt;&gt;&gt;&gt; <A =
href=3D"https://www1.ietf.org/mailman/listinfo/mip6">https://www1.ietf.or=
g/mailman/listinfo/mip6</A><BR>&gt; &gt; &gt;&gt;&gt;&gt;<BR>&gt; &gt; =
&gt;&gt;&gt;&gt; "This email message and any attachments are =
confidential<BR>&gt; &gt; &gt; information<BR>&gt; &gt; &gt;&gt;&gt; =
of<BR>&gt; &gt; &gt;&gt;&gt;<BR>&gt; &gt; &gt;&gt;&gt;&gt; Starent =
Networks, Corp. The information transmitted may not be<BR>&gt; =
used<BR>&gt; &gt; &gt; to<BR>&gt; &gt; &gt;&gt;&gt;&gt; create or change =
any contractual obligations of<BR>&gt; Starent Networks,<BR>&gt; &gt; =
&gt;&gt;&gt; Corp.<BR>&gt; &gt; &gt;&gt;&gt;<BR>&gt; &gt; =
&gt;&gt;&gt;&gt; Any<BR>&gt; &gt; &gt;&gt;&gt;&gt; review, =
retransmission, dissemination or other use of,<BR>&gt; or taking<BR>&gt; =
of<BR>&gt; &gt; &gt;&gt;&gt; any<BR>&gt; &gt; &gt;&gt;&gt;<BR>&gt; &gt; =
&gt;&gt;&gt;&gt; action in reliance upon this e-mail and its attachments =
by<BR>&gt; persons<BR>&gt; &gt; &gt; or<BR>&gt; &gt; &gt;&gt;&gt;&gt; =
entities other than the intended recipient is<BR>&gt; prohibited. If =
you<BR>&gt; &gt; &gt; are<BR>&gt; &gt; &gt;&gt;&gt; not<BR>&gt; &gt; =
&gt;&gt;&gt;<BR>&gt; &gt; &gt;&gt;&gt;&gt; the<BR>&gt; &gt; =
&gt;&gt;&gt;&gt; intended recipient, please notify the sender =
immediately -- by<BR>&gt; &gt; &gt;&gt;&gt; replying to<BR>&gt; &gt; =
&gt;&gt;&gt;<BR>&gt; &gt; &gt;&gt;&gt;&gt; this message or by sending an =
email to<BR>&gt; &gt; &gt; postmaster@starentnetworks.com<BR>&gt; &gt; =
&gt;&gt;&gt; --<BR>&gt; &gt; &gt;&gt;&gt;<BR>&gt; &gt; &gt;&gt;&gt;&gt; =
and<BR>&gt; &gt; &gt;&gt;&gt;&gt; destroy all copies of this message and =
any attachments without<BR>&gt; &gt; &gt; reading<BR>&gt; &gt; =
&gt;&gt;&gt; or<BR>&gt; &gt; &gt;&gt;&gt;<BR>&gt; &gt; &gt;&gt;&gt;&gt; =
disclosing their contents. Thank you."<BR>&gt; &gt; =
&gt;&gt;&gt;&gt;<BR>&gt; &gt; &gt;&gt;&gt;&gt;<BR>&gt; &gt; =
&gt;&gt;&gt;&gt;<BR>&gt; &gt; &gt;&gt;&gt;&gt; =
_______________________________________________<BR>&gt; &gt; =
&gt;&gt;&gt;&gt; Mip6 mailing list<BR>&gt; &gt; &gt;&gt;&gt;&gt; =
Mip6@ietf.org<BR>&gt; &gt; &gt;&gt;&gt;&gt; <A =
href=3D"https://www1.ietf.org/mailman/listinfo/mip6">https://www1.ietf.or=
g/mailman/listinfo/mip6</A><BR>&gt; &gt; &gt;&gt;&gt;<BR>&gt; &gt; =
&gt;&gt;&gt;<BR>&gt; &gt; &gt;&gt;&gt;<BR>&gt; &gt; &gt;&gt;&gt; =
_______________________________________________<BR>&gt; &gt; =
&gt;&gt;&gt; Mip6 mailing list<BR>&gt; &gt; &gt;&gt;&gt; =
Mip6@ietf.org<BR>&gt; &gt; &gt;&gt;&gt; <A =
href=3D"https://www1.ietf.org/mailman/listinfo/mip6">https://www1.ietf.or=
g/mailman/listinfo/mip6</A><BR>&gt; &gt; &gt;<BR>&gt;<BR>&gt;<BR>&gt; =
_______________________________________________<BR>&gt; Mip6 mailing =
list<BR>&gt; Mip6@ietf.org<BR>&gt; <A =
href=3D"https://www1.ietf.org/mailman/listinfo/mip6">https://www1.ietf.or=
g/mailman/listinfo/mip6</A><BR>&gt;<BR><BR><BR></FONT></P></DIV></BODY></=
HTML>
------_=_NextPart_001_01C6AB7E.6B266693--


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

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

--===============0056664305==--




From mip6-bounces@ietf.org Wed Jul 19 18:04:50 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G3K9u-0004ix-KP; Wed, 19 Jul 2006 18:04:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G3K9t-0004iI-2t
	for mip6@ietf.org; Wed, 19 Jul 2006 18:04:45 -0400
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G3K9r-0005hl-Lb
	for mip6@ietf.org; Wed, 19 Jul 2006 18:04:45 -0400
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
	k6JM4cVx031393
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Wed, 19 Jul 2006 15:04:39 -0700
Received: from NAEXBR03.na.qualcomm.com (naexbr03.qualcomm.com
	[129.46.134.172])
	by neophyte.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	k6JM33Ui027964; Wed, 19 Jul 2006 15:04:38 -0700 (PDT)
Received: from NAEX13.na.qualcomm.com ([129.46.51.248]) by
	NAEXBR03.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 19 Jul 2006 15:04:17 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
Date: Wed, 19 Jul 2006 15:01:13 -0700
Message-ID: <C24CB51D5AA800449982D9BCB90325130AC85B@NAEX13.na.qualcomm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
Thread-Index: AcarD7ph9mKzS+hsT9S9RXcdi/ZfHAAJm6EAAAaDhyAAC6igcw==
References: <7EB20EA0938B4D42A2D82689365C9B7A0CBEBC@NAEX14.na.qualcomm.com>
From: "Narayanan, Vidya" <vidyan@qualcomm.com>
To: "Soliman, Hesham" <hsoliman@qualcomm.com>,
	"Tsirtsis, George" <tsirtsis@qualcomm.com>,
	"Gerardo Giaretta" <gerardo.giaretta@gmail.com>,
	"James Kempf" <kempf@docomolabs-usa.com>
X-OriginalArrivalTime: 19 Jul 2006 22:04:17.0120 (UTC)
	FILETIME=[473FD600:01C6AB7F]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0076307105=="
Errors-To: mip6-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0076307105==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C6AB7F.46C530C5"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C6AB7F.46C530C5
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I agree. I'm surprised this is seen as a big problem.=20
=20
Vidya

________________________________

From: Soliman, Hesham [mailto:hsoliman@qualcomm.com]
Sent: Wed 7/19/2006 9:30 AM
To: Tsirtsis, George; Gerardo Giaretta; James Kempf
Cc: mip6@ietf.org
Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode Alert to =
HA?




 > > - another issue is the lifetime of the BCE. It seems not acceptable
 > > that the MN needs to go back to active state in order to send a
 > > refresh BU to the HA.

=3D> I think this is too radical. It's perfectly acceptable to do that =
if
it only happens once an hour or once every two hours ...etc. If it
happens once a minute then of course it's a problem. I don't think you
can make a blanket statement that disregards the frequency of the
updates.

 > MIP6, similar to
 > > the one proposed by James, may make sense.

=3D> Too premature IMO.

Hesham

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



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

<HTML dir=3Dltr><HEAD><TITLE>RE: [Mip6] New Charter Item:Support for =
Dormant Mode Alert to HA?</TITLE>=0A=
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dunicode">=0A=
<META content=3D"MSHTML 6.00.2900.2912" name=3DGENERATOR></HEAD>=0A=
<BODY>=0A=
<DIV id=3DidOWAReplyText76253 dir=3Dltr>=0A=
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 size=3D2>I agree. I'm =
surprised this is seen as a big problem. </FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Vidya</FONT></DIV></DIV>=0A=
<DIV dir=3Dltr><BR>=0A=
<HR tabIndex=3D-1>=0A=
<FONT face=3DTahoma size=3D2><B>From:</B> Soliman, Hesham =
[mailto:hsoliman@qualcomm.com]<BR><B>Sent:</B> Wed 7/19/2006 9:30 =
AM<BR><B>To:</B> Tsirtsis, George; Gerardo Giaretta; James =
Kempf<BR><B>Cc:</B> mip6@ietf.org<BR><B>Subject:</B> RE: [Mip6] New =
Charter Item:Support for Dormant Mode Alert to HA?<BR></FONT><BR></DIV>=0A=
<DIV><BR>=0A=
<P><FONT size=3D2>&nbsp;&gt; &gt; - another issue is the lifetime of the =
BCE. It seems not acceptable<BR>&nbsp;&gt; &gt; that the MN needs to go =
back to active state in order to send a<BR>&nbsp;&gt; &gt; refresh BU to =
the HA.<BR><BR>=3D&gt; I think this is too radical. It's perfectly =
acceptable to do that if<BR>it only happens once an hour or once every =
two hours ...etc. If it<BR>happens once a minute then of course it's a =
problem. I don't think you<BR>can make a blanket statement that =
disregards the frequency of the<BR>updates.<BR><BR>&nbsp;&gt; MIP6, =
similar to<BR>&nbsp;&gt; &gt; the one proposed by James, may make =
sense.<BR><BR>=3D&gt; Too premature =
IMO.<BR><BR>Hesham<BR><BR>_______________________________________________=
<BR>Mip6 mailing list<BR>Mip6@ietf.org<BR><A =
href=3D"https://www1.ietf.org/mailman/listinfo/mip6">https://www1.ietf.or=
g/mailman/listinfo/mip6</A><BR></FONT></P></DIV></BODY></HTML>
------_=_NextPart_001_01C6AB7F.46C530C5--


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

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

--===============0076307105==--




From mip6-bounces@ietf.org Wed Jul 19 18:08:48 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G3KDl-0005SG-U8; Wed, 19 Jul 2006 18:08:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G3KDk-0005SB-Rm
	for mip6@ietf.org; Wed, 19 Jul 2006 18:08:44 -0400
Received: from key1.docomolabs-usa.com ([216.98.102.225]
	helo=fridge.docomolabs-usa.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G3KDk-0006Bk-23
	for mip6@ietf.org; Wed, 19 Jul 2006 18:08:44 -0400
Message-ID: <039e01c6ab80$222017d0$196115ac@dcml.docomolabsusa.com>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Narayanan, Vidya" <vidyan@qualcomm.com>,
	"Tsirtsis, George" <tsirtsis@qualcomm.com>,
	"Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
References: <C24CB51D5AA800449982D9BCB90325130A11E4@NAEX13.na.qualcomm.com>
	<018c01c6ab4b$ee713010$196115ac@dcml.docomolabsusa.com>
	<C24CB51D5AA800449982D9BCB90325130AC85A@NAEX13.na.qualcomm.com>
Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
Date: Wed, 19 Jul 2006 15:10:24 -0700
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: 56904003e9d74831849863e83b1962ec
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Maybe the incidence of mobiles dropping out is higher for active than 
dormant mode mobiles?

Also, another reason for not having the timers have policy fixed values is 
so that the timers can be set depending on the kind of device. I mentioned 
this in a response to George.

            jak

----- Original Message ----- 
From: "Narayanan, Vidya" <vidyan@qualcomm.com>
To: "James Kempf" <kempf@docomolabs-usa.com>; "Tsirtsis, George" 
<tsirtsis@qualcomm.com>; "Vijay Devarapalli" 
<vijay.devarapalli@azairenet.com>
Cc: <mip6@ietf.org>
Sent: Wednesday, July 19, 2006 2:55 PM
Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?


What would be the motivation for maintaining such mode specific timer 
values?

Vidya

________________________________

From: James Kempf [mailto:kempf@docomolabs-usa.com]
Sent: Wed 7/19/2006 8:47 AM
To: Narayanan, Vidya; Tsirtsis, George; Vijay Devarapalli
Cc: mip6@ietf.org
Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?



The operator may want to keep active mode timers short, then set them longer
only if the mobile goes into dormant mode.

            jak



----- Original Message -----
From: "Narayanan, Vidya" <vidyan@qualcomm.com>
To: "Tsirtsis, George" <tsirtsis@qualcomm.com>; "Vijay Devarapalli"
<vijay.devarapalli@azairenet.com>
Cc: <mip6@ietf.org>; "James Kempf" <kempf@docomolabs-usa.com>
Sent: Tuesday, July 18, 2006 4:26 PM
Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?


I'm just catching up with this discussion.

If the IPsec idle timer is at least equal to the BU lifetime, why is
there a need for any other signaling related to dormant mode? Given that
the timer values are a matter of policy, this should be do-able.

Vidya

> -----Original Message-----
> From: Tsirtsis, George [mailto:tsirtsis@qualcomm.com]
> Sent: Tuesday, July 18, 2006 3:11 PM
> To: Vijay Devarapalli
> Cc: mip6@ietf.org; James Kempf
> Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode
> Alert to HA?
>
> Yes, I meant DPD.
>
> There is a fate sharing here between MIP6 state and IPSEC
> state. I guess the SA lifetime and DPD timer was introduced
> to catch the general case but they do not make sense to be
> much different than the MIP lifetime when that is used.
>
> It is indeed strange, however, that IPSEC does not allow for
> negotiation of these parameters. I guess people will have to
> use reasonable values in each deployment depending what they
> are doing.
>
> George
>
> > -----Original Message-----
> > From: Vijay Devarapalli [mailto:vijay.devarapalli@azairenet.com]
> > Sent: Tuesday, July 18, 2006 6:06 PM
> > To: Tsirtsis, George
> > Cc: James Kempf; Chowdhury, Kuntal; mip6@ietf.org
> > Subject: Re: [Mip6] New Charter Item:Support for Dormant
> Mode Alert to
> HA?
> >
> > Tsirtsis, George wrote:
> > > So how often PDP messages are sent is also local policy?
> >
> > I guess you meant DPD. yes it is local policy. the initiator and
> > responder configure this independently.
> >
> > > In which case
> > > it can be configured to a time that makes sense for MIP
> or a given
> > > deployment scenario.
> >
> > Yes. however, the IPsec implementation should allow for
> sufficiently
> > large values for DPD timer. but then again DPD exists so
> that unwanted
> > IPsec state is removed if the other end goes down or if there is no
> > traffic for a long time.
> >
> > Vijay
> >
> > > George
> > >
> > >> -----Original Message-----
> > >> From: Vijay Devarapalli [mailto:vijay.devarapalli@azairenet.com]
> > >> Sent: Tuesday, July 18, 2006 5:42 PM
> > >> To: James Kempf
> > >> Cc: Tsirtsis, George; Chowdhury, Kuntal; mip6@ietf.org
> > >> Subject: Re: [Mip6] New Charter Item:Support for Dormant
> Mode Alert
> to
> > > HA?
> > >> James Kempf wrote:
> > >>> I don't know. What do operators typically set the SA
> lifetime to?
> > > Though
> > >>> perhaps this is an unanswerable question because, as yet, has
> > > anybody
> > >>> deployed MIPv6?
> > >> this is more of an IPsec issue. it depends on the local
> policy on
> > >> the initiator and responder. however, as long as there
> is traffic
> > >> and there are responses to DPD messages, the IPsec SA is not
> > >> deleted.
> > >>
> > >> Vijay
> > >>
> > >>> My only observation is that this seems to be an issue with Wimax
> > > Forum,
> > >>> and one of the primary motivators for wanting to use
> the RFC 4285
> > > Auth
> > >>> Option. If IETF and the MIP6 WG would like to encourage them to
> use
> > > IKE
> > >>> (as seemed to be the sentiment when RFC 4285 was discussed, and
> one
> > > of
> > >>> the reasons why it is not PS), it might be worthwhile to try to
> > > address
> > >>> their concerns.
> > >>>
> > >>>            jak
> > >>>
> > >>> ----- Original Message ----- From: "Tsirtsis, George"
> > >>> <tsirtsis@qualcomm.com>
> > >>> To: "James Kempf" <kempf@docomolabs-usa.com>;
> "Chowdhury, Kuntal"
> > >>> <kchowdhury@starentnetworks.com>
> > >>> Cc: <mip6@ietf.org>
> > >>> Sent: Tuesday, July 18, 2006 12:10 PM
> > >>> Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode
> Alert
> > > to
> > >> HA?
> > >>>
> > >>> May I ask, what is the typical lifetime of the SA and what would
> you
> > >>> lengthen it to?
> > >>> George
> > >>>
> > >>>> -----Original Message-----
> > >>>> From: James Kempf [mailto:kempf@docomolabs-usa.com]
> > >>>> Sent: Tuesday, July 18, 2006 2:43 PM
> > >>>> To: Chowdhury, Kuntal
> > >>>> Cc: mip6@ietf.org
> > >>>> Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode
> Alert
> > > to
> > >>> HA?
> > >>>
> > >>>> Kuntal,
> > >>>>
> > >>>> The intent is not to introduce something that the MN would send
> > > during
> > >>>> dormant mode. Indeed, as you have described, this would
> negatively
> > >>> impact
> > >>>
> > >>>> battery life.
> > >>>>
> > >>>> The intent is to provide a way for the MN to say that
> it is about
> > > to
> > >>> go
> > >>>
> > >>>> into
> > >>>> dormant mode, so please lengthen the IPsec SA timeout to avoid
> > > having
> > >>> it
> > >>>
> > >>>> expire for some longer period of time.
> > >>>>
> > >>>>             jak
> > >>>>
> > >>>> ----- Original Message -----
> > >>>> From: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
> > >>>> To: "James Kempf" <kempf@docomolabs-usa.com>
> > >>>> Cc: <mip6@ietf.org>
> > >>>> Sent: Tuesday, July 18, 2006 11:20 AM
> > >>>> Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode
> Alert
> > > to
> > >>> HA?
> > >>>
> > >>>>
> > >>>> James,
> > >>>>
> > >>>> This is a good discussion. Indeed the need for IPsec keepalives
> (or
> > >>> DPD)
> > >>>
> > >>>> over the air when the MN is dormant (or idle) is an
> issue in the
> > >>>> cellular networks. The issue is Not that there are no mip6
> messages
> > >>>> defined or the HA is not aware of dormancy. It is more of a
> paging
> > >>>> channel capacity issue, MN's battery life issue and
> the signaling
> > >>>> overhead to transport the keepalives for a dormant MN issue.
> > >>>>
> > >>>> So, any new message however small won't solve the
> problem, IMHO.
> > >>>>
> > >>>> -Kuntal
> > >>>>
> > >>>>
> > >>>>> -----Original Message-----
> > >>>>> From: James Kempf [mailto:kempf@docomolabs-usa.com]
> > >>>>> Sent: Tuesday, July 18, 2006 11:17 AM
> > >>>>> To: Vijay Devarapalli
> > >>>>> Cc: mip6@ietf.org
> > >>>>> Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode
> > > Alert
> > >>> to
> > >>>
> > >>>> HA?
> > >>>>> For security, the message would need to be sent within an SA.
> > > There
> > >>> is
> > >>>
> > >>>> a
> > >>>>> question about which.
> > >>>>>
> > >>>>> One possibility is to do a Mobility Extension (call
> the messages
> > >>>> Sleeping
> > >>>>> and WakingUp) and send it within the IPsec SA between
> the HA and
> > > MN.
> > >>>> The
> > >>>>> MN
> > >>>>> sends the Sleeping message when it is about to go into dormant
> > > mode,
> > >>>> it
> > >>>>> sends the WakingUp message when it comes out again.
> The WakingUp
> > >>>> message
> > >>>>> isn't needed for the MN to get mobility service, it is just
> there
> > >>> for
> > >>>
> > >>>>> optimizing the SA timeouts. This would require a
> special API on
> > > the
> > >>> HA
> > >>>
> > >>>>> between the MIP code and IKE code for the HA to
> extend the IPsec
> > > SA
> > >>>>> lifetime, similar to the one for IKEv1 mobility. The solution
> > > would
> > >>>> only
> > >>>>> be
> > >>>>> applicable to Mobile IP.
> > >>>>>
> > >>>>> The other possibility is to do an IKEv2 INFORMATIONAL message
> > > that
> > >>> is
> > >>>
> > >>>> sent
> > >>>>> within the IKE SA. It works similarly, but there would be no
> need
> > >>> for
> > >>>
> > >>>> any
> > >>>>> API on the HA, since the IKE code itself would process it
> > > (actually,
> > >>> I
> > >>>
> > >>>>> proposed something like this to the Mobike WG but they didn't
> see
> > >>> the
> > >>>
> > >>>> need
> > >>>>> for it). This would be applicable to both Mobike and Mobile IP
> > > (and
> > >>>> any
> > >>>>> other security protocol that uses IKEv2, so maybe HIP
> as well).
> > >>>>>
> > >>>>> One question is, does the HA need to do anything else
> if the MN
> > > goes
> > >>>> into
> > >>>>> dormant mode? I think there are lots of things it could do
> > > (lengthen
> > >>>> the
> > >>>>> BU
> > >>>>> timeout, apply a filter that is either mobile
> specified or part
> > > of
> > >>> the
> > >>>
> > >>>>> user's service profile with the operator to only
> allow specific
> > >>>> traffic
> > >>>>> through, etc.) but I would really like to keep things simple.
> > >>>>>
> > >>>>>             jak
> > >>>>>
> > >>>>> ----- Original Message -----
> > >>>>> From: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
> > >>>>> To: "James Kempf" <kempf@docomolabs-usa.com>
> > >>>>> Cc: <mip6@ietf.org>
> > >>>>> Sent: Monday, July 17, 2006 3:43 PM
> > >>>>> Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode
> > > Alert
> > >>> to
> > >>>
> > >>>> HA?
> > >>>>>
> > >>>>>> the dormant mode extensions sounds good to me. we
> could do this
> > >>>>>> extension. one issue to consider - what triggers
> this message?
> > >>>>>> how does Mobile IP know the mobile node is going
> into a dormant
> > >>>>>> mode. if we have the trigger we should be okay.
> > >>>>>>
> > >>>>>> but we have to check if this was the issue. with IKEv1 you
> > >>>>>> could negotiate a lifetime for the IPsec SA. IKEv2 does not
> > >>>>>> have the IPsec SA lifetime feature. so keepalives are needed.
> > >>>>>>
> > >>>>>> James Kempf wrote:
> > >>>>>>> I was at Wimax Forum last week and I think I now understand
> > > why
> > >>>> they
> > >>>>> and
> > >>>>>>> 3GPP2 want to use RFC 4285 auth option rather than
> IPsec. One
> > >>> issue
> > >>>
> > >>>> -
> > >>>>>>> lack of EAP support for client auth - is solved by IKEv2 and
> > > they
> > >>>> seem
> > >>>>> to
> > >>>>>>> now be moving in the direction of recommending
> IKEv2 if people
> > >>> want
> > >>>
> > >>>> to
> > >>>>>>> deploy IPsec.
> > >>>>>> yes this was one of the main issues.
> > >>>>>>
> > >>>>>> the way I saw it folks in 3GPP2 liked RFC 4285 because it is
> > >>>>>> very similar to the MIPv4 mechanism and they were
> comfortable
> > >>>>>> with it.
> > >>>>>>
> > >>>>>> Vijay
> > >>>>>>
> > >>>>>> But the other issue is a bit more complex. 802.16, like
> > >>>>>>> most cellular protocols, has extensive support for dormant
> > > mode,
> > >>>> and
> > >>>>>>> Wimax Forum is supporting dormant mode in their network
> > > design.
> > >>> If
> > >>>
> > >>>>> IPsec
> > >>>>>>> is used, then there is a risk when a mobile node goes into
> > >>> dormant
> > >>>
> > >>>> mode
> > >>>>>>> that the IPsec SA may time out. It is unfortunate that this
> > > was
> > >>> not
> > >>>
> > >>>>>>> brought up when the discussion about RFC 4285 was happening,
> > > but
> > >>> I
> > >>>
> > >>>>> think
> > >>>>>>> this might be something that the WG could work on
> now as part
> > > of
> > >>>> the
> > >>>>> new
> > >>>>>>> charter. This would make IKEv2/IPsec more attractive as a
> > >>> security
> > >>>
> > >>>>> option
> > >>>>>>> for cellular operators.
> > >>>>>>>
> > >>>>>>> Comments?
> > >>>>>>>
> > >>>>>>>            jak
> > >>>>>>>
> > >>>>>>>
> > >>>>>>>
> > >>>>>>> _______________________________________________
> > >>>>>>> Mip6 mailing list
> > >>>>>>> Mip6@ietf.org
> > >>>>>>> https://www1.ietf.org/mailman/listinfo/mip6
> > >>>>>>
> > >>>>>
> > >>>>>
> > >>>>> _______________________________________________
> > >>>>> Mip6 mailing list
> > >>>>> Mip6@ietf.org
> > >>>>> https://www1.ietf.org/mailman/listinfo/mip6
> > >>>>
> > >>>> "This email message and any attachments are confidential
> > > information
> > >>> of
> > >>>
> > >>>> Starent Networks, Corp. The information transmitted may not be
> used
> > > to
> > >>>> create or change any contractual obligations of
> Starent Networks,
> > >>> Corp.
> > >>>
> > >>>> Any
> > >>>> review, retransmission, dissemination or other use of,
> or taking
> of
> > >>> any
> > >>>
> > >>>> action in reliance upon this e-mail and its attachments by
> persons
> > > or
> > >>>> entities other than the intended recipient is
> prohibited. If you
> > > are
> > >>> not
> > >>>
> > >>>> the
> > >>>> intended recipient, please notify the sender immediately -- by
> > >>> replying to
> > >>>
> > >>>> this message or by sending an email to
> > > postmaster@starentnetworks.com
> > >>> --
> > >>>
> > >>>> and
> > >>>> destroy all copies of this message and any attachments without
> > > reading
> > >>> or
> > >>>
> > >>>> disclosing their contents. Thank you."
> > >>>>
> > >>>>
> > >>>>
> > >>>> _______________________________________________
> > >>>> Mip6 mailing list
> > >>>> Mip6@ietf.org
> > >>>> https://www1.ietf.org/mailman/listinfo/mip6
> > >>>
> > >>>
> > >>>
> > >>> _______________________________________________
> > >>> Mip6 mailing list
> > >>> Mip6@ietf.org
> > >>> https://www1.ietf.org/mailman/listinfo/mip6
> > >
>
>
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
>







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



From mip6-bounces@ietf.org Wed Jul 19 18:11:12 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G3KG6-0005lk-0a; Wed, 19 Jul 2006 18:11:10 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G3KG4-0005jI-W1
	for mip6@ietf.org; Wed, 19 Jul 2006 18:11:08 -0400
Received: from key1.docomolabs-usa.com ([216.98.102.225]
	helo=fridge.docomolabs-usa.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G3KG3-0006Hp-Go
	for mip6@ietf.org; Wed, 19 Jul 2006 18:11:08 -0400
Message-ID: <03a501c6ab80$79d03690$196115ac@dcml.docomolabsusa.com>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Narayanan, Vidya" <vidyan@qualcomm.com>,
	"Soliman, Hesham" <hsoliman@qualcomm.com>,
	"Tsirtsis, George" <tsirtsis@qualcomm.com>,
	"Gerardo Giaretta" <gerardo.giaretta@gmail.com>
References: <7EB20EA0938B4D42A2D82689365C9B7A0CBEBC@NAEX14.na.qualcomm.com>
	<C24CB51D5AA800449982D9BCB90325130AC85B@NAEX13.na.qualcomm.com>
Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
Date: Wed, 19 Jul 2006 15:12:51 -0700
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

It seems to be an issue with Wimax Forum, and one of the motivating reasons 
why they and 3GPP2 insisted upon the RFC 4285 Auth option.

To turn this around, do you or anyone have an idea why IKEv2 doesn't allow 
the timer values to be negotiated? Was this just a matter of simplification 
or was there some security issue?

            jak

----- Original Message ----- 
From: "Narayanan, Vidya" <vidyan@qualcomm.com>
To: "Soliman, Hesham" <hsoliman@qualcomm.com>; "Tsirtsis, George" 
<tsirtsis@qualcomm.com>; "Gerardo Giaretta" <gerardo.giaretta@gmail.com>; 
"James Kempf" <kempf@docomolabs-usa.com>
Cc: <mip6@ietf.org>
Sent: Wednesday, July 19, 2006 3:01 PM
Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?


I agree. I'm surprised this is seen as a big problem.

Vidya

________________________________

From: Soliman, Hesham [mailto:hsoliman@qualcomm.com]
Sent: Wed 7/19/2006 9:30 AM
To: Tsirtsis, George; Gerardo Giaretta; James Kempf
Cc: mip6@ietf.org
Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?




 > > - another issue is the lifetime of the BCE. It seems not acceptable
 > > that the MN needs to go back to active state in order to send a
 > > refresh BU to the HA.

=> I think this is too radical. It's perfectly acceptable to do that if
it only happens once an hour or once every two hours ...etc. If it
happens once a minute then of course it's a problem. I don't think you
can make a blanket statement that disregards the frequency of the
updates.

 > MIP6, similar to
 > > the one proposed by James, may make sense.

=> Too premature IMO.

Hesham

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





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



From mip6-bounces@ietf.org Wed Jul 19 19:32:25 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G3LWd-0005U8-Oz; Wed, 19 Jul 2006 19:32:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G3LWb-0005Tx-Rv
	for mip6@ietf.org; Wed, 19 Jul 2006 19:32:17 -0400
Received: from ithilien.qualcomm.com ([129.46.51.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G3LWb-0005TG-03
	for mip6@ietf.org; Wed, 19 Jul 2006 19:32:17 -0400
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
	k6JNWBtU022405
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Wed, 19 Jul 2006 16:32:11 -0700
Received: from NAEXBR02.na.qualcomm.com (naexbr02.qualcomm.com [10.46.92.109])
	by crowley.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	k6JNWAJI020263; Wed, 19 Jul 2006 16:32:10 -0700 (PDT)
Received: from NAEX13.na.qualcomm.com ([129.46.51.248]) by
	NAEXBR02.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 19 Jul 2006 16:32:10 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
Date: Wed, 19 Jul 2006 16:32:03 -0700
Message-ID: <C24CB51D5AA800449982D9BCB90325130A131B@NAEX13.na.qualcomm.com>
In-Reply-To: <039e01c6ab80$222017d0$196115ac@dcml.docomolabsusa.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
Thread-Index: Acarf+uvZ9SvxftiSgWiumd5O5RlrAACy+4A
From: "Narayanan, Vidya" <vidyan@qualcomm.com>
To: "James Kempf" <kempf@docomolabs-usa.com>,
	"Tsirtsis, George" <tsirtsis@qualcomm.com>,
	"Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
X-OriginalArrivalTime: 19 Jul 2006 23:32:10.0287 (UTC)
	FILETIME=[8E4D43F0:01C6AB8B]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b7b1e91f6d312d4248b994050b22d659
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org


>=20
> Maybe the incidence of mobiles dropping out is higher for=20
> active than dormant mode mobiles?
>=20

Hmmm.. I'm not so sure. Given that the IPsec SA under discussion is
really for MIP6, I can see why the BU lifetime and the IPsec idle timer
can be in sync without a problem. So, I am surprised that there are
independent requirements here.=20

> Also, another reason for not having the timers have policy=20
> fixed values is so that the timers can be set depending on=20
> the kind of device. I mentioned this in a response to George.
>=20

Yes, I recall that. But, whatever considerations are given to the type
of device would, I'd think, apply to the BU lifetime as well.=20

Vidya


>             jak
>=20
> ----- Original Message -----
> From: "Narayanan, Vidya" <vidyan@qualcomm.com>
> To: "James Kempf" <kempf@docomolabs-usa.com>; "Tsirtsis, George"=20
> <tsirtsis@qualcomm.com>; "Vijay Devarapalli"=20
> <vijay.devarapalli@azairenet.com>
> Cc: <mip6@ietf.org>
> Sent: Wednesday, July 19, 2006 2:55 PM
> Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode=20
> Alert to HA?
>=20
>=20
> What would be the motivation for maintaining such mode specific timer=20
> values?
>=20
> Vidya
>=20
> ________________________________
>=20
> From: James Kempf [mailto:kempf@docomolabs-usa.com]
> Sent: Wed 7/19/2006 8:47 AM
> To: Narayanan, Vidya; Tsirtsis, George; Vijay Devarapalli
> Cc: mip6@ietf.org
> Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode=20
> Alert to HA?
>=20
>=20
>=20
> The operator may want to keep active mode timers short, then=20
> set them longer
> only if the mobile goes into dormant mode.
>=20
>             jak
>=20
>=20
>=20
> ----- Original Message -----
> From: "Narayanan, Vidya" <vidyan@qualcomm.com>
> To: "Tsirtsis, George" <tsirtsis@qualcomm.com>; "Vijay Devarapalli"
> <vijay.devarapalli@azairenet.com>
> Cc: <mip6@ietf.org>; "James Kempf" <kempf@docomolabs-usa.com>
> Sent: Tuesday, July 18, 2006 4:26 PM
> Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode=20
> Alert to HA?
>=20
>=20
> I'm just catching up with this discussion.
>=20
> If the IPsec idle timer is at least equal to the BU lifetime, why is
> there a need for any other signaling related to dormant mode?=20
> Given that
> the timer values are a matter of policy, this should be do-able.
>=20
> Vidya
>=20
> > -----Original Message-----
> > From: Tsirtsis, George [mailto:tsirtsis@qualcomm.com]
> > Sent: Tuesday, July 18, 2006 3:11 PM
> > To: Vijay Devarapalli
> > Cc: mip6@ietf.org; James Kempf
> > Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode
> > Alert to HA?
> >
> > Yes, I meant DPD.
> >
> > There is a fate sharing here between MIP6 state and IPSEC
> > state. I guess the SA lifetime and DPD timer was introduced
> > to catch the general case but they do not make sense to be
> > much different than the MIP lifetime when that is used.
> >
> > It is indeed strange, however, that IPSEC does not allow for
> > negotiation of these parameters. I guess people will have to
> > use reasonable values in each deployment depending what they
> > are doing.
> >
> > George
> >
> > > -----Original Message-----
> > > From: Vijay Devarapalli [mailto:vijay.devarapalli@azairenet.com]
> > > Sent: Tuesday, July 18, 2006 6:06 PM
> > > To: Tsirtsis, George
> > > Cc: James Kempf; Chowdhury, Kuntal; mip6@ietf.org
> > > Subject: Re: [Mip6] New Charter Item:Support for Dormant
> > Mode Alert to
> > HA?
> > >
> > > Tsirtsis, George wrote:
> > > > So how often PDP messages are sent is also local policy?
> > >
> > > I guess you meant DPD. yes it is local policy. the initiator and
> > > responder configure this independently.
> > >
> > > > In which case
> > > > it can be configured to a time that makes sense for MIP
> > or a given
> > > > deployment scenario.
> > >
> > > Yes. however, the IPsec implementation should allow for
> > sufficiently
> > > large values for DPD timer. but then again DPD exists so
> > that unwanted
> > > IPsec state is removed if the other end goes down or if=20
> there is no
> > > traffic for a long time.
> > >
> > > Vijay
> > >
> > > > George
> > > >
> > > >> -----Original Message-----
> > > >> From: Vijay Devarapalli=20
> [mailto:vijay.devarapalli@azairenet.com]
> > > >> Sent: Tuesday, July 18, 2006 5:42 PM
> > > >> To: James Kempf
> > > >> Cc: Tsirtsis, George; Chowdhury, Kuntal; mip6@ietf.org
> > > >> Subject: Re: [Mip6] New Charter Item:Support for Dormant
> > Mode Alert
> > to
> > > > HA?
> > > >> James Kempf wrote:
> > > >>> I don't know. What do operators typically set the SA
> > lifetime to?
> > > > Though
> > > >>> perhaps this is an unanswerable question because, as yet, has
> > > > anybody
> > > >>> deployed MIPv6?
> > > >> this is more of an IPsec issue. it depends on the local
> > policy on
> > > >> the initiator and responder. however, as long as there
> > is traffic
> > > >> and there are responses to DPD messages, the IPsec SA is not
> > > >> deleted.
> > > >>
> > > >> Vijay
> > > >>
> > > >>> My only observation is that this seems to be an issue=20
> with Wimax
> > > > Forum,
> > > >>> and one of the primary motivators for wanting to use
> > the RFC 4285
> > > > Auth
> > > >>> Option. If IETF and the MIP6 WG would like to=20
> encourage them to
> > use
> > > > IKE
> > > >>> (as seemed to be the sentiment when RFC 4285 was=20
> discussed, and
> > one
> > > > of
> > > >>> the reasons why it is not PS), it might be worthwhile=20
> to try to
> > > > address
> > > >>> their concerns.
> > > >>>
> > > >>>            jak
> > > >>>
> > > >>> ----- Original Message ----- From: "Tsirtsis, George"
> > > >>> <tsirtsis@qualcomm.com>
> > > >>> To: "James Kempf" <kempf@docomolabs-usa.com>;
> > "Chowdhury, Kuntal"
> > > >>> <kchowdhury@starentnetworks.com>
> > > >>> Cc: <mip6@ietf.org>
> > > >>> Sent: Tuesday, July 18, 2006 12:10 PM
> > > >>> Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode
> > Alert
> > > > to
> > > >> HA?
> > > >>>
> > > >>> May I ask, what is the typical lifetime of the SA and=20
> what would
> > you
> > > >>> lengthen it to?
> > > >>> George
> > > >>>
> > > >>>> -----Original Message-----
> > > >>>> From: James Kempf [mailto:kempf@docomolabs-usa.com]
> > > >>>> Sent: Tuesday, July 18, 2006 2:43 PM
> > > >>>> To: Chowdhury, Kuntal
> > > >>>> Cc: mip6@ietf.org
> > > >>>> Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode
> > Alert
> > > > to
> > > >>> HA?
> > > >>>
> > > >>>> Kuntal,
> > > >>>>
> > > >>>> The intent is not to introduce something that the MN=20
> would send
> > > > during
> > > >>>> dormant mode. Indeed, as you have described, this would
> > negatively
> > > >>> impact
> > > >>>
> > > >>>> battery life.
> > > >>>>
> > > >>>> The intent is to provide a way for the MN to say that
> > it is about
> > > > to
> > > >>> go
> > > >>>
> > > >>>> into
> > > >>>> dormant mode, so please lengthen the IPsec SA=20
> timeout to avoid
> > > > having
> > > >>> it
> > > >>>
> > > >>>> expire for some longer period of time.
> > > >>>>
> > > >>>>             jak
> > > >>>>
> > > >>>> ----- Original Message -----
> > > >>>> From: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
> > > >>>> To: "James Kempf" <kempf@docomolabs-usa.com>
> > > >>>> Cc: <mip6@ietf.org>
> > > >>>> Sent: Tuesday, July 18, 2006 11:20 AM
> > > >>>> Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode
> > Alert
> > > > to
> > > >>> HA?
> > > >>>
> > > >>>>
> > > >>>> James,
> > > >>>>
> > > >>>> This is a good discussion. Indeed the need for IPsec=20
> keepalives
> > (or
> > > >>> DPD)
> > > >>>
> > > >>>> over the air when the MN is dormant (or idle) is an
> > issue in the
> > > >>>> cellular networks. The issue is Not that there are no mip6
> > messages
> > > >>>> defined or the HA is not aware of dormancy. It is more of a
> > paging
> > > >>>> channel capacity issue, MN's battery life issue and
> > the signaling
> > > >>>> overhead to transport the keepalives for a dormant MN issue.
> > > >>>>
> > > >>>> So, any new message however small won't solve the
> > problem, IMHO.
> > > >>>>
> > > >>>> -Kuntal
> > > >>>>
> > > >>>>
> > > >>>>> -----Original Message-----
> > > >>>>> From: James Kempf [mailto:kempf@docomolabs-usa.com]
> > > >>>>> Sent: Tuesday, July 18, 2006 11:17 AM
> > > >>>>> To: Vijay Devarapalli
> > > >>>>> Cc: mip6@ietf.org
> > > >>>>> Subject: Re: [Mip6] New Charter Item:Support for=20
> Dormant Mode
> > > > Alert
> > > >>> to
> > > >>>
> > > >>>> HA?
> > > >>>>> For security, the message would need to be sent=20
> within an SA.
> > > > There
> > > >>> is
> > > >>>
> > > >>>> a
> > > >>>>> question about which.
> > > >>>>>
> > > >>>>> One possibility is to do a Mobility Extension (call
> > the messages
> > > >>>> Sleeping
> > > >>>>> and WakingUp) and send it within the IPsec SA between
> > the HA and
> > > > MN.
> > > >>>> The
> > > >>>>> MN
> > > >>>>> sends the Sleeping message when it is about to go=20
> into dormant
> > > > mode,
> > > >>>> it
> > > >>>>> sends the WakingUp message when it comes out again.
> > The WakingUp
> > > >>>> message
> > > >>>>> isn't needed for the MN to get mobility service, it is just
> > there
> > > >>> for
> > > >>>
> > > >>>>> optimizing the SA timeouts. This would require a
> > special API on
> > > > the
> > > >>> HA
> > > >>>
> > > >>>>> between the MIP code and IKE code for the HA to
> > extend the IPsec
> > > > SA
> > > >>>>> lifetime, similar to the one for IKEv1 mobility.=20
> The solution
> > > > would
> > > >>>> only
> > > >>>>> be
> > > >>>>> applicable to Mobile IP.
> > > >>>>>
> > > >>>>> The other possibility is to do an IKEv2=20
> INFORMATIONAL message
> > > > that
> > > >>> is
> > > >>>
> > > >>>> sent
> > > >>>>> within the IKE SA. It works similarly, but there would be no
> > need
> > > >>> for
> > > >>>
> > > >>>> any
> > > >>>>> API on the HA, since the IKE code itself would process it
> > > > (actually,
> > > >>> I
> > > >>>
> > > >>>>> proposed something like this to the Mobike WG but=20
> they didn't
> > see
> > > >>> the
> > > >>>
> > > >>>> need
> > > >>>>> for it). This would be applicable to both Mobike=20
> and Mobile IP
> > > > (and
> > > >>>> any
> > > >>>>> other security protocol that uses IKEv2, so maybe HIP
> > as well).
> > > >>>>>
> > > >>>>> One question is, does the HA need to do anything else
> > if the MN
> > > > goes
> > > >>>> into
> > > >>>>> dormant mode? I think there are lots of things it could do
> > > > (lengthen
> > > >>>> the
> > > >>>>> BU
> > > >>>>> timeout, apply a filter that is either mobile
> > specified or part
> > > > of
> > > >>> the
> > > >>>
> > > >>>>> user's service profile with the operator to only
> > allow specific
> > > >>>> traffic
> > > >>>>> through, etc.) but I would really like to keep=20
> things simple.
> > > >>>>>
> > > >>>>>             jak
> > > >>>>>
> > > >>>>> ----- Original Message -----
> > > >>>>> From: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
> > > >>>>> To: "James Kempf" <kempf@docomolabs-usa.com>
> > > >>>>> Cc: <mip6@ietf.org>
> > > >>>>> Sent: Monday, July 17, 2006 3:43 PM
> > > >>>>> Subject: Re: [Mip6] New Charter Item:Support for=20
> Dormant Mode
> > > > Alert
> > > >>> to
> > > >>>
> > > >>>> HA?
> > > >>>>>
> > > >>>>>> the dormant mode extensions sounds good to me. we
> > could do this
> > > >>>>>> extension. one issue to consider - what triggers
> > this message?
> > > >>>>>> how does Mobile IP know the mobile node is going
> > into a dormant
> > > >>>>>> mode. if we have the trigger we should be okay.
> > > >>>>>>
> > > >>>>>> but we have to check if this was the issue. with IKEv1 you
> > > >>>>>> could negotiate a lifetime for the IPsec SA. IKEv2 does not
> > > >>>>>> have the IPsec SA lifetime feature. so keepalives=20
> are needed.
> > > >>>>>>
> > > >>>>>> James Kempf wrote:
> > > >>>>>>> I was at Wimax Forum last week and I think I now=20
> understand
> > > > why
> > > >>>> they
> > > >>>>> and
> > > >>>>>>> 3GPP2 want to use RFC 4285 auth option rather than
> > IPsec. One
> > > >>> issue
> > > >>>
> > > >>>> -
> > > >>>>>>> lack of EAP support for client auth - is solved=20
> by IKEv2 and
> > > > they
> > > >>>> seem
> > > >>>>> to
> > > >>>>>>> now be moving in the direction of recommending
> > IKEv2 if people
> > > >>> want
> > > >>>
> > > >>>> to
> > > >>>>>>> deploy IPsec.
> > > >>>>>> yes this was one of the main issues.
> > > >>>>>>
> > > >>>>>> the way I saw it folks in 3GPP2 liked RFC 4285=20
> because it is
> > > >>>>>> very similar to the MIPv4 mechanism and they were
> > comfortable
> > > >>>>>> with it.
> > > >>>>>>
> > > >>>>>> Vijay
> > > >>>>>>
> > > >>>>>> But the other issue is a bit more complex. 802.16, like
> > > >>>>>>> most cellular protocols, has extensive support for dormant
> > > > mode,
> > > >>>> and
> > > >>>>>>> Wimax Forum is supporting dormant mode in their network
> > > > design.
> > > >>> If
> > > >>>
> > > >>>>> IPsec
> > > >>>>>>> is used, then there is a risk when a mobile node goes into
> > > >>> dormant
> > > >>>
> > > >>>> mode
> > > >>>>>>> that the IPsec SA may time out. It is unfortunate=20
> that this
> > > > was
> > > >>> not
> > > >>>
> > > >>>>>>> brought up when the discussion about RFC 4285 was=20
> happening,
> > > > but
> > > >>> I
> > > >>>
> > > >>>>> think
> > > >>>>>>> this might be something that the WG could work on
> > now as part
> > > > of
> > > >>>> the
> > > >>>>> new
> > > >>>>>>> charter. This would make IKEv2/IPsec more attractive as a
> > > >>> security
> > > >>>
> > > >>>>> option
> > > >>>>>>> for cellular operators.
> > > >>>>>>>
> > > >>>>>>> Comments?
> > > >>>>>>>
> > > >>>>>>>            jak
> > > >>>>>>>
> > > >>>>>>>
> > > >>>>>>>
> > > >>>>>>> _______________________________________________
> > > >>>>>>> Mip6 mailing list
> > > >>>>>>> Mip6@ietf.org
> > > >>>>>>> https://www1.ietf.org/mailman/listinfo/mip6
> > > >>>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>> _______________________________________________
> > > >>>>> Mip6 mailing list
> > > >>>>> Mip6@ietf.org
> > > >>>>> https://www1.ietf.org/mailman/listinfo/mip6
> > > >>>>
> > > >>>> "This email message and any attachments are confidential
> > > > information
> > > >>> of
> > > >>>
> > > >>>> Starent Networks, Corp. The information transmitted=20
> may not be
> > used
> > > > to
> > > >>>> create or change any contractual obligations of
> > Starent Networks,
> > > >>> Corp.
> > > >>>
> > > >>>> Any
> > > >>>> review, retransmission, dissemination or other use of,
> > or taking
> > of
> > > >>> any
> > > >>>
> > > >>>> action in reliance upon this e-mail and its attachments by
> > persons
> > > > or
> > > >>>> entities other than the intended recipient is
> > prohibited. If you
> > > > are
> > > >>> not
> > > >>>
> > > >>>> the
> > > >>>> intended recipient, please notify the sender=20
> immediately -- by
> > > >>> replying to
> > > >>>
> > > >>>> this message or by sending an email to
> > > > postmaster@starentnetworks.com
> > > >>> --
> > > >>>
> > > >>>> and
> > > >>>> destroy all copies of this message and any=20
> attachments without
> > > > reading
> > > >>> or
> > > >>>
> > > >>>> disclosing their contents. Thank you."
> > > >>>>
> > > >>>>
> > > >>>>
> > > >>>> _______________________________________________
> > > >>>> Mip6 mailing list
> > > >>>> Mip6@ietf.org
> > > >>>> https://www1.ietf.org/mailman/listinfo/mip6
> > > >>>
> > > >>>
> > > >>>
> > > >>> _______________________________________________
> > > >>> Mip6 mailing list
> > > >>> Mip6@ietf.org
> > > >>> https://www1.ietf.org/mailman/listinfo/mip6
> > > >
> >
> >
> > _______________________________________________
> > Mip6 mailing list
> > Mip6@ietf.org
> > https://www1.ietf.org/mailman/listinfo/mip6
> >
>=20
>=20
>=20
>=20
>=20
>=20
>=20

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



From mip6-bounces@ietf.org Wed Jul 19 19:59:36 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G3Lwo-0000fJ-7x; Wed, 19 Jul 2006 19:59:22 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G3Lwn-0000fE-Ba
	for mip6@ietf.org; Wed, 19 Jul 2006 19:59:21 -0400
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G3Lwl-0001P5-T2
	for mip6@ietf.org; Wed, 19 Jul 2006 19:59:21 -0400
Received: from sabrina.qualcomm.com (sabrina.qualcomm.com [129.46.61.150])
	by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k6JNxF56015959
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Wed, 19 Jul 2006 16:59:15 -0700
Received: from NAEXBR02.na.qualcomm.com (naexbr02.qualcomm.com [10.46.92.109])
	by sabrina.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	k6JNxDVM009192; Wed, 19 Jul 2006 16:59:14 -0700 (PDT)
Received: from NAEX13.na.qualcomm.com ([129.46.51.248]) by
	NAEXBR02.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 19 Jul 2006 16:59:14 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
Date: Wed, 19 Jul 2006 16:59:09 -0700
Message-ID: <C24CB51D5AA800449982D9BCB90325130A1323@NAEX13.na.qualcomm.com>
In-Reply-To: <03a501c6ab80$79d03690$196115ac@dcml.docomolabsusa.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
Thread-Index: AcargEMPlJQPHPxqSe+RDuOB4Y76sAACqlHA
From: "Narayanan, Vidya" <vidyan@qualcomm.com>
To: "James Kempf" <kempf@docomolabs-usa.com>,
	"Soliman, Hesham" <hsoliman@qualcomm.com>,
	"Tsirtsis, George" <tsirtsis@qualcomm.com>,
	"Gerardo Giaretta" <gerardo.giaretta@gmail.com>
X-OriginalArrivalTime: 19 Jul 2006 23:59:14.0232 (UTC)
	FILETIME=[563F9B80:01C6AB8F]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5ebbf074524e58e662bc8209a6235027
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Yes, I was actually coming to that :) Before I wrote about that, I
wanted to understand the motivation better and hence my questions.=20

Now, before we go down the path of concluding that IKEv2 needs to
support timer/lifetime negotiation, we should take a look at why this
functionality didn't make it into IKEv2 (since IKE supported it).=20

Supporting lifetime or timer negotiation in a key management protocol is
really seen as a wasteful feature for the following reasons:=20

1. The key management protocol itself really has no control over the
enforcement of these lifetimes or timers.=20

2. Even with negotiated lifetimes, IKEv2 and IPsec allow either party to
re-key at any time.=20

3. Either party may reboot or lose state and lifetime or timers don't
have any value then.=20

For all these reasons, it was felt that there is no real reason for
IKEv2 to do this functionality. Independent management of lifetimes and
timers by the initiator and responder is really the most flexible way of
handling this.=20

As I said in my earlier emails, all the concerns tied to the IPsec timer
values seem to equally apply to the BU lifetime as well - hence, I am
not yet seeing a need for adding this functionality to IKEv2 per say.=20

I'm not sure about WiMAX, but at least in 3gpp2, this was not one of the
reasons for using the AUTH protocol as far as I know. Two reasons why
AUTH protocol was originally chosen as opposed to IPsec - before IKEv2,
there wasn't a way to utilize AAA-based credentials with IPsec (IKE
didn't support EAP). Also, even with EAP/IKEv2, the number of messages
seemed to be a concern (e.g., in a failure/recovery scenario, all
mobiles try to do EAP/IKEv2 with the HA, which could be a problem). And,
currently, 3gpp2 is already revisiting the option of requiring IPsec for
MIP6 in place of the AUTH protocol.=20

Vidya


> -----Original Message-----
> From: James Kempf [mailto:kempf@docomolabs-usa.com]=20
> Sent: Wednesday, July 19, 2006 3:13 PM
> To: Narayanan, Vidya; Soliman, Hesham; Tsirtsis, George;=20
> Gerardo Giaretta
> Cc: mip6@ietf.org
> Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode=20
> Alert to HA?
>=20
> It seems to be an issue with Wimax Forum, and one of the=20
> motivating reasons why they and 3GPP2 insisted upon the RFC=20
> 4285 Auth option.
>=20
> To turn this around, do you or anyone have an idea why IKEv2=20
> doesn't allow the timer values to be negotiated? Was this=20
> just a matter of simplification or was there some security issue?
>=20
>             jak
>=20
> ----- Original Message -----
> From: "Narayanan, Vidya" <vidyan@qualcomm.com>
> To: "Soliman, Hesham" <hsoliman@qualcomm.com>; "Tsirtsis, George"=20
> <tsirtsis@qualcomm.com>; "Gerardo Giaretta"=20
> <gerardo.giaretta@gmail.com>; "James Kempf" <kempf@docomolabs-usa.com>
> Cc: <mip6@ietf.org>
> Sent: Wednesday, July 19, 2006 3:01 PM
> Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode=20
> Alert to HA?
>=20
>=20
> I agree. I'm surprised this is seen as a big problem.
>=20
> Vidya
>=20
> ________________________________
>=20
> From: Soliman, Hesham [mailto:hsoliman@qualcomm.com]
> Sent: Wed 7/19/2006 9:30 AM
> To: Tsirtsis, George; Gerardo Giaretta; James Kempf
> Cc: mip6@ietf.org
> Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode=20
> Alert to HA?
>=20
>=20
>=20
>=20
>  > > - another issue is the lifetime of the BCE. It seems not=20
> acceptable  > > that the MN needs to go back to active state=20
> in order to send a  > > refresh BU to the HA.
>=20
> =3D> I think this is too radical. It's perfectly acceptable to=20
> do that if it only happens once an hour or once every two=20
> hours ...etc. If it happens once a minute then of course it's=20
> a problem. I don't think you can make a blanket statement=20
> that disregards the frequency of the updates.
>=20
>  > MIP6, similar to
>  > > the one proposed by James, may make sense.
>=20
> =3D> Too premature IMO.
>=20
> Hesham
>=20
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
>=20
>=20
>=20
>=20
>=20

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



From mip6-bounces@ietf.org Thu Jul 20 09:01:32 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G3Y9e-00028u-7T; Thu, 20 Jul 2006 09:01:26 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G3Y9c-00028O-Ux
	for mip6@ietf.org; Thu, 20 Jul 2006 09:01:24 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G3Y9c-0005QL-TY
	for mip6@ietf.org; Thu, 20 Jul 2006 09:01:24 -0400
Received: from motgate2.mot.com ([144.189.100.101])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1G3Y9N-0001zu-5m
	for mip6@ietf.org; Thu, 20 Jul 2006 09:01:10 -0400
Received: from az33exr01.mot.com (az33exr01.mot.com [10.64.251.231])
	by motgate2.mot.com (8.12.11/Motorola) with ESMTP id k6KD0xOJ024890;
	Thu, 20 Jul 2006 06:00:59 -0700 (MST)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by az33exr01.mot.com (8.13.1/8.13.0) with ESMTP id k6KD0vMU024760;
	Thu, 20 Jul 2006 08:00:58 -0500 (CDT)
Message-ID: <44BF7E88.9060305@motorola.com>
Date: Thu, 20 Jul 2006 15:00:56 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: Brian Haley <brian.haley@hp.com>
Subject: Re: [Mip6] New charter item: HA assignment
References: <729b68be0607180431m773dc847qed3e7350819a8d04@mail.gmail.com>
	<44BD1105.5040904@motorola.com> <44BD3AA6.7070906@hp.com>
	<44BD5AEA.6020209@motorola.com> <44BE5953.6080602@hp.com>
	<44BE700D.5070700@motorola.com> <44BE9943.7060308@hp.com>
In-Reply-To: <44BE9943.7060308@hp.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAQAAAAQ=
X-White-List-Member: TRUE
X-Spam-Score: -2.6 (--)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Brian, thanks for the message.

Brian Haley wrote:
> Alex,
> 
>>>>>> Another way is for the new HA to send Binding Refresh 
>>>>>> Request to MN (even if it has no BC entry for it).
>>>>> 
>>>>> BRR is sent from CN to MN, it is not defined to be sent from 
>>>>> HA.
>>>> 
>>>> I think that depends on each one's interpretation of 
>>>> "correspondent".  I see BRR very well sent by HA to MN if BCE 
>>>> lifetime expired and BU was lost.
>>> 
>>> I don't know how you can interpret 3775 (or implement it) such 
>>> that a HA can be a CN of the same MN at the same time.
>> 
>> I don't see the problem with that.
>> 
>> For some implementations it is useful/easy to have HA send BRR to 
>> MN. In this way MN does not need to implement additional timer of 
>> receiving BAck, only a timer for re-transmitting BU and to respond 
>> to BRR.
>> 
>> Wrt to how to read rfc3775 and think that CN can be a HA, this is 
>> an exercise indeed, but I'm tempted to do it because I also had to 
>> do it when thinking CN can be a MN.  And, if one thinks NEMOv6 
>> then, and MN is a MR and MR can be a HA for mobiles in its moving 
>> network... CN can be a HA.
>> 
>> In the end, the BRR message should be implemented as send and 
>> receive in any entity running Mobile IPv6: CN, HA, MH, MR.
> 
> I'll agree to disagree.
> 
>> Take this 3775 text:
>>> If the sender knows that the Binding Cache entry is still in 
>>> active use, it MAY send a Binding Refresh Request message to the 
>>> mobile node in an attempt to avoid this overhead and latency due 
>>> to deleting and recreating the Binding Cache entry.
> 
> You're taking this out of context,

Brian, I tried to keep quoted text short, it was not my intention to
confuse.  Indeed, most 3775 text about BRR specifically says CN, no BRR
text says HA.  My point was to say that "CN" can be interpreted as "HA".
  I agree we disagree about that.

>>> You're the HA or you aren't, and HAs don't send BRRs - TAHI would
>>>  have a test for it if they could :)
>> 
>> I suppose TAHI's interpretation of 3775 is that HA doesn't send 
>> BRRs. Some implementations don't conform to TAHI then.
> 
> There are no implementations that conform to your interpretation, at 
> least not at any Connectathon or ETSI event I've been to.

That is a good point to know, informative, thanks.

> I didn't even implement BRR in my code since it's optional and 
> mobility can continue without it, just not optimized.

I have same reasoning about other parts of MIP6.

Alex


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



From mip6-bounces@ietf.org Thu Jul 20 10:17:49 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G3ZLU-0003p5-MZ; Thu, 20 Jul 2006 10:17:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G3ZLT-0003jG-F0
	for mip6@ietf.org; Thu, 20 Jul 2006 10:17:43 -0400
Received: from py-out-1112.google.com ([64.233.166.182])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G3ZBr-0002UR-BH
	for mip6@ietf.org; Thu, 20 Jul 2006 10:07:48 -0400
Received: by py-out-1112.google.com with SMTP id n25so774918pyg
	for <mip6@ietf.org>; Thu, 20 Jul 2006 07:07:47 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=XDDgHAfXCAi2fPjMtmGRJfQ85k005xOPjRJGwlDttyl43M5ATXRflnX6uOZp5o+ufYfd05oCaQcbE0c6P3NPaNbWPBNuhNYQqGvphUJ7AGAU/3KB5AAE5SZM5sm26kAlC3JJLNJEflPdnwkZkWJf41v+wMXXL8E/GtzCaHu+ZFY=
Received: by 10.35.38.17 with SMTP id q17mr1126166pyj;
	Thu, 20 Jul 2006 07:07:46 -0700 (PDT)
Received: by 10.35.111.9 with HTTP; Thu, 20 Jul 2006 07:07:46 -0700 (PDT)
Message-ID: <729b68be0607200707t352c93aeu4708adf12e3eee8e@mail.gmail.com>
Date: Thu, 20 Jul 2006 16:07:46 +0200
From: "Jean-Michel Combes" <jeanmichel.combes@gmail.com>
To: "Alexandru Petrescu" <alexandru.petrescu@motorola.com>
Subject: Re: [Mip6] New charter item: HA assignment
In-Reply-To: <44BD1105.5040904@motorola.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <729b68be0607180431m773dc847qed3e7350819a8d04@mail.gmail.com>
	<44BD1105.5040904@motorola.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi Alex,

2006/7/18, Alexandru Petrescu <alexandru.petrescu@motorola.com>:
> Jean-Michel Combes wrote:
> > Hi,
> >
> > as promised during the mip6 session, here is a point which, IMO, is
> > important from a MSP's point of view: Actually, the bootstrapping
> > solution, in the split scenario, only propose a HA discovery
> > mechanism (i.e. the MN receives a list of HA, from DNS, and chooses
> > one of them). The MSP has no easy solution to enforce one MN to have
> > a specific HA.
>
> One possible way is for a HA to stop sending BAck, at which point an MN
> would send DHAAD Request again, and a different HA replies back DHAAD,
> so end result is MN is assigned a new HA.

Normally, the DHAAD reply is again a list of HAs.

>
> Another way is for the new HA to send Binding Refresh Request to MN
> (even if it has no BC entry for it).

IIRC, only CNs send BRR to MN. Am I wrong?

>
> Another way, if the split bootstrapping advances, is for the MSP to
> dynamically update the DNS data about HAs, so when MN bootstraps it
> obtains a different HA.

Again here, this is a list of HAs.

>
> If the HA address is discovered with DHCP then I think the DHCP Server
> can send specific messages to MN (unsolicited by MN).

But, here, you are doing the assumption there is a DHCP Server or
Relay in the Access Network, which is not always the case.

>
> It would require relaxing some language in rfc 3775 and probably
> extending BRR.
>
> It would be helpful to know when would an MSP like the MN to choose a
> different HA, for what reasons.

If an operator sets up different types of mobility like MIPv6, HMIPv6,
NEMO or Monami6. I don't think that all the operator's HAs will
support all these services :)

Best regards.

JMC.

>
> Alex
>
>

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



From mip6-bounces@ietf.org Thu Jul 20 10:23:03 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G3ZQb-0007q5-Nl; Thu, 20 Jul 2006 10:23:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G3ZQa-0007pz-T3
	for mip6@ietf.org; Thu, 20 Jul 2006 10:23:00 -0400
Received: from py-out-1112.google.com ([64.233.166.177])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G3ZQZ-0003Wn-D6
	for mip6@ietf.org; Thu, 20 Jul 2006 10:23:00 -0400
Received: by py-out-1112.google.com with SMTP id n25so781868pyg
	for <mip6@ietf.org>; Thu, 20 Jul 2006 07:22:59 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=nqREFBsUgZot0Nue2WGsojYIwzb9UyZkp9Ir/EkD6mJCcsc8FpuyiC2JOqm8Id/FqxnO9zwneyOjYnea8oktQWxy4VtCs1ZYxJrhUOrtyEWqL/PmVDhY1gjbCjuVMck7Ud6UtB3gmiTUMENn+uKg8BKLAsYNyb5siysHb+S4aYc=
Received: by 10.35.121.9 with SMTP id y9mr1151827pym;
	Thu, 20 Jul 2006 07:22:59 -0700 (PDT)
Received: by 10.35.111.9 with HTTP; Thu, 20 Jul 2006 07:22:58 -0700 (PDT)
Message-ID: <729b68be0607200722o26487064j70c958b4b25b6d69@mail.gmail.com>
Date: Thu, 20 Jul 2006 16:22:58 +0200
From: "Jean-Michel Combes" <jeanmichel.combes@gmail.com>
To: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
Subject: Re: [Mip6] New charter item: HA assignment
In-Reply-To: <7CCD07160348804497EF29E9EA5560D73C52AE@exchtewks2.starentnetworks.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <7CCD07160348804497EF29E9EA5560D73C52AE@exchtewks2.starentnetworks.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 31247fb3be228bb596db9127becad0bc
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>,
	Alexandru Petrescu <alexandru.petrescu@motorola.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi Kuntal,

2006/7/18, Chowdhury, Kuntal <kchowdhury@starentnetworks.com>:
> Alex,
>
> What you describe will require many round trips for the network (MSP) to
> assign a HA.

I totally agree with you.

> There is a fundamental difference between discovery and
> assignment. What Jean-Michel brought up is the need in the industry for
> HA assignment.

Exactly :)

>
> In the integrated scenario solution document we used AAA infrastructure
> and DHCP to _assign_ the HA. May be operators interested in HA
> assignment should use that instead of DNS.

But this only works in the case there is a DHCP Relay in the Access Network.
BTW, I asked sometime ago on the DHC ML, why is it not possible to use
directly the unicast address of a DHCP Server (cf. RFC 3315, section
18.2.1) and I never had a clear answer :(

Best regards.

JMC.

>
> -Kuntal
>
>
> > -----Original Message-----
> > From: Alexandru Petrescu [mailto:alexandru.petrescu@motorola.com]
> > Sent: Tuesday, July 18, 2006 11:49 AM
> > To: Jean-Michel Combes
> > Cc: Mobile IPv6 Mailing List
> > Subject: Re: [Mip6] New charter item: HA assignment
> >
> > Jean-Michel Combes wrote:
> > > Hi,
> > >
> > > as promised during the mip6 session, here is a point which, IMO, is
> > > important from a MSP's point of view: Actually, the bootstrapping
> > > solution, in the split scenario, only propose a HA discovery
> > > mechanism (i.e. the MN receives a list of HA, from DNS, and chooses
> > > one of them). The MSP has no easy solution to enforce one MN to have
> > > a specific HA.
> >
> > One possible way is for a HA to stop sending BAck, at which point an
> MN
> > would send DHAAD Request again, and a different HA replies back DHAAD,
> > so end result is MN is assigned a new HA.
> >
> > Another way is for the new HA to send Binding Refresh Request to MN
> > (even if it has no BC entry for it).
> >
> > Another way, if the split bootstrapping advances, is for the MSP to
> > dynamically update the DNS data about HAs, so when MN bootstraps it
> > obtains a different HA.
> >
> > If the HA address is discovered with DHCP then I think the DHCP Server
> > can send specific messages to MN (unsolicited by MN).
> >
> > It would require relaxing some language in rfc 3775 and probably
> > extending BRR.
> >
> > It would be helpful to know when would an MSP like the MN to choose a
> > different HA, for what reasons.
> >
> > Alex
> >
> >
> > _______________________________________________
> > Mip6 mailing list
> > Mip6@ietf.org
> > https://www1.ietf.org/mailman/listinfo/mip6
>
>
> "This email message and any attachments are confidential information of Starent Networks, Corp. The information transmitted may not be used to create or change any contractual obligations of Starent Networks, Corp.  Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this e-mail and its attachments by persons or entities other than the intended recipient is prohibited. If you are not the intended recipient, please notify the sender immediately -- by replying to this message or by sending an email to postmaster@starentnetworks.com -- and destroy all copies of this message and any attachments without reading or disclosing their contents. Thank you."
>

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



From mip6-bounces@ietf.org Thu Jul 20 10:58:40 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G3Zz5-0006qX-1b; Thu, 20 Jul 2006 10:58:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G3Zz2-0006oa-BT
	for mip6@ietf.org; Thu, 20 Jul 2006 10:58:36 -0400
Received: from zcars04f.nortel.com ([47.129.242.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G3Zql-0005ez-9f
	for mip6@ietf.org; Thu, 20 Jul 2006 10:50:05 -0400
Received: from zrc2hxm2.corp.nortel.com (zrc2hxm2.corp.nortel.com
	[47.103.123.73])
	by zcars04f.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	k6KEnkJ12839; Thu, 20 Jul 2006 10:49:46 -0400 (EDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
Date: Thu, 20 Jul 2006 09:49:45 -0500
Message-ID: <62B9B0847CC47543B6B3B5E26BD268E60B5F6412@zrc2hxm2.corp.nortel.com>
In-Reply-To: <C24CB51D5AA800449982D9BCB90325130A1323@NAEX13.na.qualcomm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
thread-index: AcargEMPlJQPHPxqSe+RDuOB4Y76sAACqlHAACAUDpA=
From: "Mohamed Khalil" <mkhalil@nortel.com>
To: "Narayanan, Vidya" <vidyan@qualcomm.com>,
	"James Kempf" <kempf@docomolabs-usa.com>,
	"Soliman, Hesham" <hsoliman@qualcomm.com>,
	"Tsirtsis, George" <tsirtsis@qualcomm.com>,
	"Gerardo Giaretta" <gerardo.giaretta@gmail.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org



Hi Vidya,


I'm not sure about WiMAX, but at least in 3gpp2, this was not one of the
reasons for using the AUTH protocol as far as I know. Two reasons why
AUTH protocol was originally chosen as opposed to IPsec - before IKEv2,
there wasn't a way to utilize AAA-based credentials with IPsec (IKE
didn't support EAP). Also, even with EAP/IKEv2, the number of messages
seemed to be a concern (e.g., in a failure/recovery scenario, all
mobiles try to do EAP/IKEv2 with the HA, which could be a problem). And,
currently, 3gpp2 is already revisiting the option of requiring IPsec for
MIP6 in place of the AUTH protocol.

The reason 3gpp2 adopted AUTH protocol because it is simple and easy to
manage. Regarding your statement "requiring IPsec for MIP6 in place of
the AUTH", I don't think that 3gpp2 precluded the usage of IPSec since
they are supporting 3775.

Vidya


> -----Original Message-----
> From: James Kempf [mailto:kempf@docomolabs-usa.com]
> Sent: Wednesday, July 19, 2006 3:13 PM
> To: Narayanan, Vidya; Soliman, Hesham; Tsirtsis, George;=20
> Gerardo Giaretta
> Cc: mip6@ietf.org
> Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode=20
> Alert to HA?
>=20
> It seems to be an issue with Wimax Forum, and one of the
> motivating reasons why they and 3GPP2 insisted upon the RFC=20
> 4285 Auth option.
>=20
> To turn this around, do you or anyone have an idea why IKEv2
> doesn't allow the timer values to be negotiated? Was this=20
> just a matter of simplification or was there some security issue?
>=20
>             jak
>=20
> ----- Original Message -----
> From: "Narayanan, Vidya" <vidyan@qualcomm.com>
> To: "Soliman, Hesham" <hsoliman@qualcomm.com>; "Tsirtsis, George"
> <tsirtsis@qualcomm.com>; "Gerardo Giaretta"=20
> <gerardo.giaretta@gmail.com>; "James Kempf" <kempf@docomolabs-usa.com>
> Cc: <mip6@ietf.org>
> Sent: Wednesday, July 19, 2006 3:01 PM
> Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode=20
> Alert to HA?
>=20
>=20
> I agree. I'm surprised this is seen as a big problem.
>=20
> Vidya
>=20
> ________________________________
>=20
> From: Soliman, Hesham [mailto:hsoliman@qualcomm.com]
> Sent: Wed 7/19/2006 9:30 AM
> To: Tsirtsis, George; Gerardo Giaretta; James Kempf
> Cc: mip6@ietf.org
> Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode
> Alert to HA?
>=20
>=20
>=20
>=20
>  > > - another issue is the lifetime of the BCE. It seems not
> acceptable  > > that the MN needs to go back to active state=20
> in order to send a  > > refresh BU to the HA.
>=20
> =3D> I think this is too radical. It's perfectly acceptable to
> do that if it only happens once an hour or once every two=20
> hours ...etc. If it happens once a minute then of course it's=20
> a problem. I don't think you can make a blanket statement=20
> that disregards the frequency of the updates.
>=20
>  > MIP6, similar to
>  > > the one proposed by James, may make sense.
>=20
> =3D> Too premature IMO.
>=20
> Hesham
>=20
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
>=20
>=20
>=20
>=20
>=20

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

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



From mip6-bounces@ietf.org Thu Jul 20 10:58:42 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G3Zz8-0006xt-Fj; Thu, 20 Jul 2006 10:58:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G3Zz7-0006wT-QZ
	for mip6@ietf.org; Thu, 20 Jul 2006 10:58:41 -0400
Received: from motgate4.mot.com ([144.189.100.102])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G3Zpf-0005NO-KK
	for mip6@ietf.org; Thu, 20 Jul 2006 10:48:56 -0400
Received: from az33exr04.mot.com (az33exr04.mot.com [10.64.251.234])
	by motgate4.mot.com (8.12.11/Motorola) with ESMTP id k6KEmrqq025780;
	Thu, 20 Jul 2006 07:48:54 -0700 (MST)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by az33exr04.mot.com (8.13.1/8.13.0) with ESMTP id k6KEmqJC013458;
	Thu, 20 Jul 2006 09:48:52 -0500 (CDT)
Message-ID: <44BF97D3.9010308@motorola.com>
Date: Thu, 20 Jul 2006 16:48:51 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: Jean-Michel Combes <jeanmichel.combes@gmail.com>
Subject: Re: [Mip6] New charter item: HA assignment
References: <729b68be0607180431m773dc847qed3e7350819a8d04@mail.gmail.com>	
	<44BD1105.5040904@motorola.com>
	<729b68be0607200707t352c93aeu4708adf12e3eee8e@mail.gmail.com>
In-Reply-To: <729b68be0607200707t352c93aeu4708adf12e3eee8e@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAQAAAAQ=
X-White-List-Member: TRUE
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Jean-Michel Combes wrote:
> Hi Alex,
> 
> 2006/7/18, Alexandru Petrescu <alexandru.petrescu@motorola.com>:
>> Jean-Michel Combes wrote:
>>> Hi,
>>> 
>>> as promised during the mip6 session, here is a point which, IMO,
>>> is important from a MSP's point of view: Actually, the
>>> bootstrapping solution, in the split scenario, only propose a HA
>>> discovery mechanism (i.e. the MN receives a list of HA, from DNS,
>>> and chooses one of them). The MSP has no easy solution to enforce
>>> one MN to have a specific HA.
>> 
>> One possible way is for a HA to stop sending BAck, at which point
>> an MN would send DHAAD Request again, and a different HA replies
>> back DHAAD, so end result is MN is assigned a new HA.
> 
> Normally, the DHAAD reply is again a list of HAs.

Yes, and the MN can choose the first.  The important thing is when that
list changes.

>> Another way is for the new HA to send Binding Refresh Request to MN
>>  (even if it has no BC entry for it).
> 
> IIRC, only CNs send BRR to MN. Am I wrong?

Seems I'm the only one who believes HA can send BRRs.  Another
opinion(s) here agrees with you.

3775 says CN sends BRR and doesn't say HA must not send BRR.

>> Another way, if the split bootstrapping advances, is for the MSP to
>>  dynamically update the DNS data about HAs, so when MN bootstraps
>> it obtains a different HA.
> 
> Again here, this is a list of HAs.
> 
>> 
>> If the HA address is discovered with DHCP then I think the DHCP
>> Server can send specific messages to MN (unsolicited by MN).
> 
> But, here, you are doing the assumption there is a DHCP Server or 
> Relay in the Access Network, which is not always the case.

Right, depends on the industry needs.

>> It would require relaxing some language in rfc 3775 and probably 
>> extending BRR.
>> 
>> It would be helpful to know when would an MSP like the MN to choose
>> a different HA, for what reasons.
> 
> If an operator sets up different types of mobility like MIPv6,
> HMIPv6, NEMO or Monami6. I don't think that all the operator's HAs
> will support all these services :)

So you see an MN initially using a certain MIP6 HA, and then at some
point operator decide that that particular mobile should use a HMIPv6
HA?  What would be the scenario?

Alex

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



From mip6-bounces@ietf.org Thu Jul 20 11:35:00 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G3aYD-0006iP-L9; Thu, 20 Jul 2006 11:34:57 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G3aY6-0006JM-3r
	for mip6@ietf.org; Thu, 20 Jul 2006 11:34:50 -0400
Received: from ithilien.qualcomm.com ([129.46.51.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G3aRt-0003iK-0R
	for mip6@ietf.org; Thu, 20 Jul 2006 11:28:26 -0400
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
	k6KFSIm6008857
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Thu, 20 Jul 2006 08:28:20 -0700
Received: from NAEXBR03.na.qualcomm.com (naexbr03.qualcomm.com
	[129.46.134.172])
	by magus.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id k6KFSH3K018235; 
	Thu, 20 Jul 2006 08:28:18 -0700 (PDT)
Received: from NAEX14.na.qualcomm.com ([10.47.5.242]) by
	NAEXBR03.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 20 Jul 2006 08:28:11 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
Date: Thu, 20 Jul 2006 08:28:08 -0700
Message-ID: <7EB20EA0938B4D42A2D82689365C9B7A0CBFC0@NAEX14.na.qualcomm.com>
In-Reply-To: <03a501c6ab80$79d03690$196115ac@dcml.docomolabsusa.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
Thread-Index: AcargENdaAS6dbskSsGGTbjskUPR7QAkHlCQ
From: "Soliman, Hesham" <hsoliman@qualcomm.com>
To: "James Kempf" <kempf@docomolabs-usa.com>,
	"Narayanan, Vidya" <vidyan@qualcomm.com>,
	"Tsirtsis, George" <tsirtsis@qualcomm.com>,
	"Gerardo Giaretta" <gerardo.giaretta@gmail.com>
X-OriginalArrivalTime: 20 Jul 2006 15:28:11.0193 (UTC)
	FILETIME=[1C10EA90:01C6AC11]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 31247fb3be228bb596db9127becad0bc
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

=20
 > It seems to be an issue with Wimax Forum, and one of the=20
 > motivating reasons=20
 > why they and 3GPP2 insisted upon the RFC 4285 Auth option.

=3D> Honestly, if that's what motivated them to do 4285 then I'm worried
about the rest
of their system! I *think* 4285 was done to avoid implementing IKE/IPsec
primarily. That makes more sense to me than doing it to avoid confusion
about timers which can be set properly by an admin.=20

 >=20
 > To turn this around, do you or anyone have an idea why IKEv2=20
 > doesn't allow=20
 > the timer values to be negotiated? Was this just a matter of=20
 > simplification=20
 > or was there some security issue?

=3D> Sounds like a strange design choice to me, the old one allowed for
timer negotiation.=20

Hesham

 >=20
 >             jak
 >=20
 > ----- Original Message -----=20
 > From: "Narayanan, Vidya" <vidyan@qualcomm.com>
 > To: "Soliman, Hesham" <hsoliman@qualcomm.com>; "Tsirtsis, George"=20
 > <tsirtsis@qualcomm.com>; "Gerardo Giaretta"=20
 > <gerardo.giaretta@gmail.com>;=20
 > "James Kempf" <kempf@docomolabs-usa.com>
 > Cc: <mip6@ietf.org>
 > Sent: Wednesday, July 19, 2006 3:01 PM
 > Subject: RE: [Mip6] New Charter Item:Support for Dormant=20
 > Mode Alert to HA?
 >=20
 >=20
 > I agree. I'm surprised this is seen as a big problem.
 >=20
 > Vidya
 >=20
 > ________________________________
 >=20
 > From: Soliman, Hesham [mailto:hsoliman@qualcomm.com]
 > Sent: Wed 7/19/2006 9:30 AM
 > To: Tsirtsis, George; Gerardo Giaretta; James Kempf
 > Cc: mip6@ietf.org
 > Subject: RE: [Mip6] New Charter Item:Support for Dormant=20
 > Mode Alert to HA?
 >=20
 >=20
 >=20
 >=20
 >  > > - another issue is the lifetime of the BCE. It seems=20
 > not acceptable
 >  > > that the MN needs to go back to active state in order to send a
 >  > > refresh BU to the HA.
 >=20
 > =3D> I think this is too radical. It's perfectly acceptable to=20
 > do that if
 > it only happens once an hour or once every two hours ...etc. If it
 > happens once a minute then of course it's a problem. I don't=20
 > think you
 > can make a blanket statement that disregards the frequency of the
 > updates.
 >=20
 >  > MIP6, similar to
 >  > > the one proposed by James, may make sense.
 >=20
 > =3D> Too premature IMO.
 >=20
 > Hesham
 >=20
 > _______________________________________________
 > Mip6 mailing list
 > Mip6@ietf.org
 > https://www1.ietf.org/mailman/listinfo/mip6
 >=20
 >=20
 >=20
 >=20
 >=20

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



From mip6-bounces@ietf.org Thu Jul 20 11:56:14 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G3asn-00053z-5l; Thu, 20 Jul 2006 11:56:13 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G3asl-00051v-1W
	for mip6@ietf.org; Thu, 20 Jul 2006 11:56:11 -0400
Received: from web60315.mail.yahoo.com ([209.73.178.138])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1G3aqy-0006Fx-5C
	for mip6@ietf.org; Thu, 20 Jul 2006 11:54:21 -0400
Received: (qmail 68905 invoked by uid 60001); 20 Jul 2006 15:54:14 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=Message-ID:Received:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type;
	b=FX64PYBDNKb2wq8FOt1hrPxmZQZXl4bnLj1ty+4PyiYJh0UeDbMSQAodC6VN7iBbJc9+u5U/5RCLJJYoUzwgpxW/QlGEm2V+R+1DWdhEMomNP4dDLqQH6V6rxkLr9/yS828fKXBp9nO7ybB+0jZFtO2kHOSBOkPVGUkunBnMXPo=
	; 
Message-ID: <20060720155414.68903.qmail@web60315.mail.yahoo.com>
Received: from [12.129.211.52] by web60315.mail.yahoo.com via HTTP;
	Thu, 20 Jul 2006 08:54:14 PDT
Date: Thu, 20 Jul 2006 08:54:14 -0700 (PDT)
From: Behcet Sarikaya <behcetsarikaya@yahoo.com>
Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
To: Vijay Devarapalli <vijay.devarapalli@azairenet.com>,
	James Kempf <kempf@docomolabs-usa.com>
In-Reply-To: <44BE72AC.7080302@azairenet.com>
MIME-Version: 1.0
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Behcet Sarikaya <sarikaya@ieee.org>
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0369963812=="
Errors-To: mip6-bounces@ietf.org

--===============0369963812==
Content-Type: multipart/alternative; boundary="0-844933085-1153410854=:43759"

--0-844933085-1153410854=:43759
Content-Type: text/plain; charset=us-ascii



----- Original Message ----
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
To: James Kempf <kempf@docomolabs-usa.com>
Cc: mip6@ietf.org
Sent: Wednesday, July 19, 2006 12:58:04 PM
Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?

James Kempf wrote:
> Gerardo,
> 
> ----- Original Message ----- From: "Gerardo Giaretta" 
> <gerardo.giaretta@gmail.com>
> To:> - one is the SA lifetime. This is really an IKE/IPsec issue and should
>> be handled in IPsec (concluded) WG. As mentioned, this issue does not
>> apply only to MIP6; in 3GPP I-WLAN the MN has an IPsec tunnel with the
>> PDG and if the access network supports dormant mode, the MN cannot go
>> into dormant mode state in order to keep the SA up. I guess it may
>> apply also to MOBIKE.
>>
> 
> The IPsec WG doesn't exist anymore and neither does MOBIKE. MOBIKE was 
> closed recently. If the MIP WG decides that this is a problem that needs 
> to be solved, it cannot simply hand the problem off to another WG. 
> Either a new WG would need to be formed or the MIP WG would need to do 
> the work itself.

the work is too minor to form a WG. another option is an
individual submission with reviews from MIP6 WG and the
IPsec and MOBIKE mailing lists (which are still around).
==> I agree with James. There are more and more issues coming up with IP aspects of the dormant mode from SDOs (a new one just popped up today in WiMAX) and an issue was mentioned in one of mobopts presentations in IETF 66.
I do not think that an individual submission is going to do it. Maybe a PS might help.

Regards,

Behcet
-- the rest is snipped.






--0-844933085-1153410854=:43759
Content-Type: text/html; charset=us-ascii

<html><head><style type="text/css"><!-- DIV {margin:0px} --></style></head><body><div style="font-family:times new roman, new york, times, serif;font-size:12pt"><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;"><br><br><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;">----- Original Message ----<br>From: Vijay Devarapalli &lt;vijay.devarapalli@azairenet.com&gt;<br>To: James Kempf &lt;kempf@docomolabs-usa.com&gt;<br>Cc: mip6@ietf.org<br>Sent: Wednesday, July 19, 2006 12:58:04 PM<br>Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?<br><br><div>James Kempf wrote:<br>&gt; Gerardo,<br>&gt; <br>&gt; ----- Original Message ----- From: "Gerardo Giaretta" <br>&gt; &lt;gerardo.giaretta@gmail.com&gt;<br>&gt; To:&gt; - one is the SA lifetime. This is really an IKE/IPsec issue and should<br>&gt;&gt; be handled in IPsec (concluded) WG. As mentioned, this issue does not<br>&gt;&gt; apply only to MIP6;
 in 3GPP I-WLAN the MN has an IPsec tunnel with the<br>&gt;&gt; PDG and if the access network supports dormant mode, the MN cannot go<br>&gt;&gt; into dormant mode state in order to keep the SA up. I guess it may<br>&gt;&gt; apply also to MOBIKE.<br>&gt;&gt;<br>&gt; <br>&gt; The IPsec WG doesn't exist anymore and neither does MOBIKE. MOBIKE was <br>&gt; closed recently. If the MIP WG decides that this is a problem that needs <br>&gt; to be solved, it cannot simply hand the problem off to another WG. <br>&gt; Either a new WG would need to be formed or the MIP WG would need to do <br>&gt; the work itself.<br><br>the work is too minor to form a WG. another option is an<br>individual submission with reviews from MIP6 WG and the<br>IPsec and MOBIKE mailing lists (which are still around).<br>==&gt; I agree with James. There are more and more issues coming up with IP aspects of the dormant mode from SDOs (a new one just popped up today in WiMAX) and an issue was mentioned in one
 of mobopts presentations in IETF 66.<br>I do not think that an individual submission is going to do it. Maybe a PS might help.<br><br>Regards,<br><br>Behcet<br>-- the rest is snipped.<br><br></div></div><br></div></div></body></html>
--0-844933085-1153410854=:43759--


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

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

--===============0369963812==--




From mip6-bounces@ietf.org Thu Jul 20 12:15:15 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G3bBD-0003cX-50; Thu, 20 Jul 2006 12:15:15 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G3bAU-0002Xo-5c
	for mip6@ietf.org; Thu, 20 Jul 2006 12:14:30 -0400
Received: from py-out-1112.google.com ([64.233.166.179])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G3b2L-0000Lw-EA
	for mip6@ietf.org; Thu, 20 Jul 2006 12:06:05 -0400
Received: by py-out-1112.google.com with SMTP id n25so826471pyg
	for <mip6@ietf.org>; Thu, 20 Jul 2006 09:06:04 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=cW0SO43uooaXOdE4hB7kDupLD+CFogY1hhUytjOEMyV7BnHyJ/V40HwjKoJUmWlieOiRo3lRzCMhPSxeAWt3NInduqu4qRhPR/+32oSes3HQJn/MhFlZJlezpNh2jRwFn1a7WqPKyKX5JkwHFekjmhgf84X3bZc/BLVGSeWYkWg=
Received: by 10.35.29.6 with SMTP id g6mr1305241pyj;
	Thu, 20 Jul 2006 09:06:04 -0700 (PDT)
Received: by 10.35.111.9 with HTTP; Thu, 20 Jul 2006 09:06:04 -0700 (PDT)
Message-ID: <729b68be0607200906g427688b1l2b127997fb3ba9b4@mail.gmail.com>
Date: Thu, 20 Jul 2006 18:06:04 +0200
From: "Jean-Michel Combes" <jeanmichel.combes@gmail.com>
To: "James Kempf" <kempf@docomolabs-usa.com>
Subject: Re: [Mip6] New charter item: HA assignment
In-Reply-To: <02fc01c6aa99$de869d00$196115ac@dcml.docomolabsusa.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <729b68be0607180431m773dc847qed3e7350819a8d04@mail.gmail.com>
	<44BD1105.5040904@motorola.com>
	<02fc01c6aa99$de869d00$196115ac@dcml.docomolabsusa.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68ba2b07ef271dba6ee42a93832cfa4c
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>,
	Alexandru Petrescu <alexandru.petrescu@motorola.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi James,

2006/7/18, James Kempf <kempf@docomolabs-usa.com>:
> So there are three ways I can think of that one could go about assigning an
> HA.
>
> 1) The MN uses the weights returned with the DNS SRV record from RFC 2782 to
> guide its selection of HAs. Less preferred HAs are later in the preference
> ordering. The authors of RFC 2782 complain about weights being a relatively
> coarse-grained mechanism that isn't up to providing dynamic load balancing.
> I think the time granularity of the SRV updates would  be about 15 seconds
> minimum, if dynamic DNS is used, since I'm told that is about the amount of
> time one should expect it to take for a dynamic DNS update to propagate.

This is discovery and not assignment. Nothing prevents the MN to
choose the HA it wants.
Another problem is this solution has no granularity: you cannot play
with the weights depending which MN requests the HAs list.

BTW, be careful with the update of the DNS:
- if DNSSEC is used: real-time update not possible
- take account the time the update will be propagated to the secondary
servers/cache DNS

The 2 main reasons I said I didn't like this solution at the beginning
of the discussion about the split scenario draft but this is out of
scope here :)

>
> 2) For a more dynamic mechanism, the HA initially tried by the MN can turn
> down the MN's request to perform IKEv2. Or the HA could deny the MN an HoA.
> This would cause the MN to roll over to the next HA on the list. When the MN
> hit the right HA, the IKEv2 transaction would succeed. This has the
> disadvantage that it increases the amount of time the MN needs to bootstrap.

That could work but I agree about the increase about the amount of time.

>
> 3) Immediately after the MN finishes the IKEv2 transaction, the first HA
> could send a HA Switch message (draft-ietf-mip6-ha-switch-00.txt) within the
> IPsec SA, telling the MN to go elsewhere. The MN would be delayed  by the
> amount of time needed to do the IKEv2 transaction, but that does provide
> security. This seems like it would be the most direct way.

Why not.

>
> I think a combination of these three mechanisms would be sufficient to
> provide HA assignment for the kinds of deployment scenerios that the split
> scenerio was designed to accommodate. The first mechanism would provide load
> balancing over longer periods while the second would provide support for
> fast transients, and the third would provide a way to directly and securely
> tell an MN where to go. Ideally, the MN wouldn't have to go through more
> than one additional HA before it got service, reducing the amount of lag.
>
> On the other hand, if you want a way to say "thou shalt use this HA" without
> a lot of initial negotiation, then I'd suggest using the intergrated
> scenerio and simply let DHCP assign the MN to an HA (though that would
> require DHCP security).

Yes but we need solutions for all the scenarios. I don't see an
operator sending a message to a mobility subscriber saying "You are
not in an integrated case: please, stop using the IETF network if you
want to bootstrap your IPv6 mobility service" ;)

>
> If these are insufficient, then the only other suggestion is that an IKEv2
> INFORMATIONAL message be defined directing the MN to try IKEv2 with another
> node (which would be the preferred HA). Such a message could be used for VPN
> server load balancing too.

Maybe too depend to a specific service: I am not sure that IPsec guys
will accept such an addition in IKEv2.

Best regards.

JMC.

>
>             jak
>
>
>
>
>
>
> ----- Original Message -----
> From: "Alexandru Petrescu" <alexandru.petrescu@motorola.com>
> To: "Jean-Michel Combes" <jeanmichel.combes@gmail.com>
> Cc: "Mobile IPv6 Mailing List" <mip6@ietf.org>
> Sent: Tuesday, July 18, 2006 9:49 AM
> Subject: Re: [Mip6] New charter item: HA assignment
>
>
> > Jean-Michel Combes wrote:
> >> Hi,
> >>
> >> as promised during the mip6 session, here is a point which, IMO, is
> >> important from a MSP's point of view: Actually, the bootstrapping
> >> solution, in the split scenario, only propose a HA discovery mechanism
> >> (i.e. the MN receives a list of HA, from DNS, and chooses one of them).
> >> The MSP has no easy solution to enforce one MN to have a specific HA.
> >
> > One possible way is for a HA to stop sending BAck, at which point an MN
> > would send DHAAD Request again, and a different HA replies back DHAAD,
> > so end result is MN is assigned a new HA.
> >
> > Another way is for the new HA to send Binding Refresh Request to MN
> > (even if it has no BC entry for it).
> >
> > Another way, if the split bootstrapping advances, is for the MSP to
> > dynamically update the DNS data about HAs, so when MN bootstraps it
> > obtains a different HA.
> >
> > If the HA address is discovered with DHCP then I think the DHCP Server
> > can send specific messages to MN (unsolicited by MN).
> >
> > It would require relaxing some language in rfc 3775 and probably extending
> > BRR.
> >
> > It would be helpful to know when would an MSP like the MN to choose a
> > different HA, for what reasons.
> >
> > Alex
> >
> >
> > _______________________________________________
> > Mip6 mailing list
> > Mip6@ietf.org
> > https://www1.ietf.org/mailman/listinfo/mip6
> >
>
>
>

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



From mip6-bounces@ietf.org Thu Jul 20 12:20:18 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G3bG5-0007Nq-G9; Thu, 20 Jul 2006 12:20:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G3bG4-0007Nb-GR
	for mip6@ietf.org; Thu, 20 Jul 2006 12:20:16 -0400
Received: from key1.docomolabs-usa.com ([216.98.102.225]
	helo=fridge.docomolabs-usa.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G3bG3-00022C-F0
	for mip6@ietf.org; Thu, 20 Jul 2006 12:20:16 -0400
Message-ID: <01f501c6ac18$9d9ccf50$196115ac@dcml.docomolabsusa.com>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Narayanan, Vidya" <vidyan@qualcomm.com>,
	"Tsirtsis, George" <tsirtsis@qualcomm.com>,
	"Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
References: <C24CB51D5AA800449982D9BCB90325130A131B@NAEX13.na.qualcomm.com>
Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
Date: Thu, 20 Jul 2006 09:21:54 -0700
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: 1fb4c76a9d88e8fb8b791f63f8d1b07f
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Vidya,

The fact is that MIP and IKE are managed by two completely different 
protocols. RFC 4301 does not specify anything about timeouts in the SPD or 
SAD, which would allow some kind of per host or per application timeout 
customization. Your proposal means that the operator would have to manage 
its HA with the same timeouts for the HA to mobile node MIP traffic as for, 
say, signaling traffic between two HAs doing the HA reliability protocol or 
some other IPsec application, because the basic IPsec architecture provides 
no way to differentiate between the timing requirements of the two. I think 
this is unreasonable, as the ability of the two to respond to keepalives 
could be quite different. Furthermore, RFC 4306 says this about why any 
timeouts were left out of IKEv2 (Section 2.4):

   Numbers of retries and lengths of timeouts are not covered in this
   specification because they do not affect interoperability.  It is
   suggested that messages be retransmitted at least a dozen times over
   a period of at least several minutes before giving up on an SA, but
   different environments may require different rules.

As with other cases involving mobile nodes and IKEv2 (whence came MOBIKE), 
this does not address the needs of wireless. An implementation on a laptop 
with 802.11, which doesn't have proper dormant mode support, doesn't need 
the ability to lengthen the timeout for dormant mode because it will be 
woken up by the AP when a keepalive arrives. An implementation on a 
cellphone which does have proper dormant mode support won't, or, at least, 
it shouldn't if we want to provide proper support for dormant mode. Should 
the combined BU/SA timeout be the same for both? If so and it is set to the 
802.11 timeout, having no way for the cellphone to lengthen its timeout when 
it goes into dormant mode means drastically reduced cellphone battery 
lifetime and unhappy customers. If it is set to the expected cellphone 
dormant mode lifetime then the SAD has a bunch of entries for laptops, whose 
owners have closed the lids and jumped on a plane, hanging around when they 
aren't needed. The effect won't be to prohibit interoperability, but it will 
result in a considerable amount of unnecessary traffic and reduced customer 
satisfaction.

Furthermore, IKEv1 had a way to do lifetime negotiation (Section 4.5 in RFC 
2407) via the SA lifetime in the ISAKMP messaging. So I don't quite 
understand why you are opposed to adding an IKEv2 INFORMATIONAL exchange for 
this purpose.

Your point about 3GPP2 needing EAP support is also a concern to Wimax Forum, 
as I mentioned in the original email that started this thread, but, in 
addition, I was hearing that they were concerned about IPsec SA timeout 
during dormant mode. I sent email to the Wimax Forum list, and Raj confirmed 
that this was, indeed, a concern.

And finally regarding your point:

    As I said in my earlier emails, all the concerns tied to the IPsec timer
    values seem to equally apply to the BU lifetime as well - hence, I am
    not yet seeing a need for adding this functionality to IKEv2 per say.

The problem is that it is possible to extend the binding lifetime by sending 
a BU just before the mobile node goes into dormant mode, but there is no 
support in IKEv2 for extending the SA lifetime.

        jak



----- Original Message ----- 
From: "Narayanan, Vidya" <vidyan@qualcomm.com>
To: "James Kempf" <kempf@docomolabs-usa.com>; "Tsirtsis, George" 
<tsirtsis@qualcomm.com>; "Vijay Devarapalli" 
<vijay.devarapalli@azairenet.com>
Cc: <mip6@ietf.org>
Sent: Wednesday, July 19, 2006 4:32 PM
Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?



>
> Maybe the incidence of mobiles dropping out is higher for
> active than dormant mode mobiles?
>

Hmmm.. I'm not so sure. Given that the IPsec SA under discussion is
really for MIP6, I can see why the BU lifetime and the IPsec idle timer
can be in sync without a problem. So, I am surprised that there are
independent requirements here.

> Also, another reason for not having the timers have policy
> fixed values is so that the timers can be set depending on
> the kind of device. I mentioned this in a response to George.
>

Yes, I recall that. But, whatever considerations are given to the type
of device would, I'd think, apply to the BU lifetime as well.

Vidya


>             jak
>
> ----- Original Message -----
> From: "Narayanan, Vidya" <vidyan@qualcomm.com>
> To: "James Kempf" <kempf@docomolabs-usa.com>; "Tsirtsis, George"
> <tsirtsis@qualcomm.com>; "Vijay Devarapalli"
> <vijay.devarapalli@azairenet.com>
> Cc: <mip6@ietf.org>
> Sent: Wednesday, July 19, 2006 2:55 PM
> Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode
> Alert to HA?
>
>
> What would be the motivation for maintaining such mode specific timer
> values?
>
> Vidya
>
> ________________________________
>
> From: James Kempf [mailto:kempf@docomolabs-usa.com]
> Sent: Wed 7/19/2006 8:47 AM
> To: Narayanan, Vidya; Tsirtsis, George; Vijay Devarapalli
> Cc: mip6@ietf.org
> Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode
> Alert to HA?
>
>
>
> The operator may want to keep active mode timers short, then
> set them longer
> only if the mobile goes into dormant mode.
>
>             jak
>
>
>
> ----- Original Message -----
> From: "Narayanan, Vidya" <vidyan@qualcomm.com>
> To: "Tsirtsis, George" <tsirtsis@qualcomm.com>; "Vijay Devarapalli"
> <vijay.devarapalli@azairenet.com>
> Cc: <mip6@ietf.org>; "James Kempf" <kempf@docomolabs-usa.com>
> Sent: Tuesday, July 18, 2006 4:26 PM
> Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode
> Alert to HA?
>
>
> I'm just catching up with this discussion.
>
> If the IPsec idle timer is at least equal to the BU lifetime, why is
> there a need for any other signaling related to dormant mode?
> Given that
> the timer values are a matter of policy, this should be do-able.
>
> Vidya
>
> > -----Original Message-----
> > From: Tsirtsis, George [mailto:tsirtsis@qualcomm.com]
> > Sent: Tuesday, July 18, 2006 3:11 PM
> > To: Vijay Devarapalli
> > Cc: mip6@ietf.org; James Kempf
> > Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode
> > Alert to HA?
> >
> > Yes, I meant DPD.
> >
> > There is a fate sharing here between MIP6 state and IPSEC
> > state. I guess the SA lifetime and DPD timer was introduced
> > to catch the general case but they do not make sense to be
> > much different than the MIP lifetime when that is used.
> >
> > It is indeed strange, however, that IPSEC does not allow for
> > negotiation of these parameters. I guess people will have to
> > use reasonable values in each deployment depending what they
> > are doing.
> >
> > George
> >
> > > -----Original Message-----
> > > From: Vijay Devarapalli [mailto:vijay.devarapalli@azairenet.com]
> > > Sent: Tuesday, July 18, 2006 6:06 PM
> > > To: Tsirtsis, George
> > > Cc: James Kempf; Chowdhury, Kuntal; mip6@ietf.org
> > > Subject: Re: [Mip6] New Charter Item:Support for Dormant
> > Mode Alert to
> > HA?
> > >
> > > Tsirtsis, George wrote:
> > > > So how often PDP messages are sent is also local policy?
> > >
> > > I guess you meant DPD. yes it is local policy. the initiator and
> > > responder configure this independently.
> > >
> > > > In which case
> > > > it can be configured to a time that makes sense for MIP
> > or a given
> > > > deployment scenario.
> > >
> > > Yes. however, the IPsec implementation should allow for
> > sufficiently
> > > large values for DPD timer. but then again DPD exists so
> > that unwanted
> > > IPsec state is removed if the other end goes down or if
> there is no
> > > traffic for a long time.
> > >
> > > Vijay
> > >
> > > > George
> > > >
> > > >> -----Original Message-----
> > > >> From: Vijay Devarapalli
> [mailto:vijay.devarapalli@azairenet.com]
> > > >> Sent: Tuesday, July 18, 2006 5:42 PM
> > > >> To: James Kempf
> > > >> Cc: Tsirtsis, George; Chowdhury, Kuntal; mip6@ietf.org
> > > >> Subject: Re: [Mip6] New Charter Item:Support for Dormant
> > Mode Alert
> > to
> > > > HA?
> > > >> James Kempf wrote:
> > > >>> I don't know. What do operators typically set the SA
> > lifetime to?
> > > > Though
> > > >>> perhaps this is an unanswerable question because, as yet, has
> > > > anybody
> > > >>> deployed MIPv6?
> > > >> this is more of an IPsec issue. it depends on the local
> > policy on
> > > >> the initiator and responder. however, as long as there
> > is traffic
> > > >> and there are responses to DPD messages, the IPsec SA is not
> > > >> deleted.
> > > >>
> > > >> Vijay
> > > >>
> > > >>> My only observation is that this seems to be an issue
> with Wimax
> > > > Forum,
> > > >>> and one of the primary motivators for wanting to use
> > the RFC 4285
> > > > Auth
> > > >>> Option. If IETF and the MIP6 WG would like to
> encourage them to
> > use
> > > > IKE
> > > >>> (as seemed to be the sentiment when RFC 4285 was
> discussed, and
> > one
> > > > of
> > > >>> the reasons why it is not PS), it might be worthwhile
> to try to
> > > > address
> > > >>> their concerns.
> > > >>>
> > > >>>            jak
> > > >>>
> > > >>> ----- Original Message ----- From: "Tsirtsis, George"
> > > >>> <tsirtsis@qualcomm.com>
> > > >>> To: "James Kempf" <kempf@docomolabs-usa.com>;
> > "Chowdhury, Kuntal"
> > > >>> <kchowdhury@starentnetworks.com>
> > > >>> Cc: <mip6@ietf.org>
> > > >>> Sent: Tuesday, July 18, 2006 12:10 PM
> > > >>> Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode
> > Alert
> > > > to
> > > >> HA?
> > > >>>
> > > >>> May I ask, what is the typical lifetime of the SA and
> what would
> > you
> > > >>> lengthen it to?
> > > >>> George
> > > >>>
> > > >>>> -----Original Message-----
> > > >>>> From: James Kempf [mailto:kempf@docomolabs-usa.com]
> > > >>>> Sent: Tuesday, July 18, 2006 2:43 PM
> > > >>>> To: Chowdhury, Kuntal
> > > >>>> Cc: mip6@ietf.org
> > > >>>> Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode
> > Alert
> > > > to
> > > >>> HA?
> > > >>>
> > > >>>> Kuntal,
> > > >>>>
> > > >>>> The intent is not to introduce something that the MN
> would send
> > > > during
> > > >>>> dormant mode. Indeed, as you have described, this would
> > negatively
> > > >>> impact
> > > >>>
> > > >>>> battery life.
> > > >>>>
> > > >>>> The intent is to provide a way for the MN to say that
> > it is about
> > > > to
> > > >>> go
> > > >>>
> > > >>>> into
> > > >>>> dormant mode, so please lengthen the IPsec SA
> timeout to avoid
> > > > having
> > > >>> it
> > > >>>
> > > >>>> expire for some longer period of time.
> > > >>>>
> > > >>>>             jak
> > > >>>>
> > > >>>> ----- Original Message -----
> > > >>>> From: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
> > > >>>> To: "James Kempf" <kempf@docomolabs-usa.com>
> > > >>>> Cc: <mip6@ietf.org>
> > > >>>> Sent: Tuesday, July 18, 2006 11:20 AM
> > > >>>> Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode
> > Alert
> > > > to
> > > >>> HA?
> > > >>>
> > > >>>>
> > > >>>> James,
> > > >>>>
> > > >>>> This is a good discussion. Indeed the need for IPsec
> keepalives
> > (or
> > > >>> DPD)
> > > >>>
> > > >>>> over the air when the MN is dormant (or idle) is an
> > issue in the
> > > >>>> cellular networks. The issue is Not that there are no mip6
> > messages
> > > >>>> defined or the HA is not aware of dormancy. It is more of a
> > paging
> > > >>>> channel capacity issue, MN's battery life issue and
> > the signaling
> > > >>>> overhead to transport the keepalives for a dormant MN issue.
> > > >>>>
> > > >>>> So, any new message however small won't solve the
> > problem, IMHO.
> > > >>>>
> > > >>>> -Kuntal
> > > >>>>
> > > >>>>
> > > >>>>> -----Original Message-----
> > > >>>>> From: James Kempf [mailto:kempf@docomolabs-usa.com]
> > > >>>>> Sent: Tuesday, July 18, 2006 11:17 AM
> > > >>>>> To: Vijay Devarapalli
> > > >>>>> Cc: mip6@ietf.org
> > > >>>>> Subject: Re: [Mip6] New Charter Item:Support for
> Dormant Mode
> > > > Alert
> > > >>> to
> > > >>>
> > > >>>> HA?
> > > >>>>> For security, the message would need to be sent
> within an SA.
> > > > There
> > > >>> is
> > > >>>
> > > >>>> a
> > > >>>>> question about which.
> > > >>>>>
> > > >>>>> One possibility is to do a Mobility Extension (call
> > the messages
> > > >>>> Sleeping
> > > >>>>> and WakingUp) and send it within the IPsec SA between
> > the HA and
> > > > MN.
> > > >>>> The
> > > >>>>> MN
> > > >>>>> sends the Sleeping message when it is about to go
> into dormant
> > > > mode,
> > > >>>> it
> > > >>>>> sends the WakingUp message when it comes out again.
> > The WakingUp
> > > >>>> message
> > > >>>>> isn't needed for the MN to get mobility service, it is just
> > there
> > > >>> for
> > > >>>
> > > >>>>> optimizing the SA timeouts. This would require a
> > special API on
> > > > the
> > > >>> HA
> > > >>>
> > > >>>>> between the MIP code and IKE code for the HA to
> > extend the IPsec
> > > > SA
> > > >>>>> lifetime, similar to the one for IKEv1 mobility.
> The solution
> > > > would
> > > >>>> only
> > > >>>>> be
> > > >>>>> applicable to Mobile IP.
> > > >>>>>
> > > >>>>> The other possibility is to do an IKEv2
> INFORMATIONAL message
> > > > that
> > > >>> is
> > > >>>
> > > >>>> sent
> > > >>>>> within the IKE SA. It works similarly, but there would be no
> > need
> > > >>> for
> > > >>>
> > > >>>> any
> > > >>>>> API on the HA, since the IKE code itself would process it
> > > > (actually,
> > > >>> I
> > > >>>
> > > >>>>> proposed something like this to the Mobike WG but
> they didn't
> > see
> > > >>> the
> > > >>>
> > > >>>> need
> > > >>>>> for it). This would be applicable to both Mobike
> and Mobile IP
> > > > (and
> > > >>>> any
> > > >>>>> other security protocol that uses IKEv2, so maybe HIP
> > as well).
> > > >>>>>
> > > >>>>> One question is, does the HA need to do anything else
> > if the MN
> > > > goes
> > > >>>> into
> > > >>>>> dormant mode? I think there are lots of things it could do
> > > > (lengthen
> > > >>>> the
> > > >>>>> BU
> > > >>>>> timeout, apply a filter that is either mobile
> > specified or part
> > > > of
> > > >>> the
> > > >>>
> > > >>>>> user's service profile with the operator to only
> > allow specific
> > > >>>> traffic
> > > >>>>> through, etc.) but I would really like to keep
> things simple.
> > > >>>>>
> > > >>>>>             jak
> > > >>>>>
> > > >>>>> ----- Original Message -----
> > > >>>>> From: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
> > > >>>>> To: "James Kempf" <kempf@docomolabs-usa.com>
> > > >>>>> Cc: <mip6@ietf.org>
> > > >>>>> Sent: Monday, July 17, 2006 3:43 PM
> > > >>>>> Subject: Re: [Mip6] New Charter Item:Support for
> Dormant Mode
> > > > Alert
> > > >>> to
> > > >>>
> > > >>>> HA?
> > > >>>>>
> > > >>>>>> the dormant mode extensions sounds good to me. we
> > could do this
> > > >>>>>> extension. one issue to consider - what triggers
> > this message?
> > > >>>>>> how does Mobile IP know the mobile node is going
> > into a dormant
> > > >>>>>> mode. if we have the trigger we should be okay.
> > > >>>>>>
> > > >>>>>> but we have to check if this was the issue. with IKEv1 you
> > > >>>>>> could negotiate a lifetime for the IPsec SA. IKEv2 does not
> > > >>>>>> have the IPsec SA lifetime feature. so keepalives
> are needed.
> > > >>>>>>
> > > >>>>>> James Kempf wrote:
> > > >>>>>>> I was at Wimax Forum last week and I think I now
> understand
> > > > why
> > > >>>> they
> > > >>>>> and
> > > >>>>>>> 3GPP2 want to use RFC 4285 auth option rather than
> > IPsec. One
> > > >>> issue
> > > >>>
> > > >>>> -
> > > >>>>>>> lack of EAP support for client auth - is solved
> by IKEv2 and
> > > > they
> > > >>>> seem
> > > >>>>> to
> > > >>>>>>> now be moving in the direction of recommending
> > IKEv2 if people
> > > >>> want
> > > >>>
> > > >>>> to
> > > >>>>>>> deploy IPsec.
> > > >>>>>> yes this was one of the main issues.
> > > >>>>>>
> > > >>>>>> the way I saw it folks in 3GPP2 liked RFC 4285
> because it is
> > > >>>>>> very similar to the MIPv4 mechanism and they were
> > comfortable
> > > >>>>>> with it.
> > > >>>>>>
> > > >>>>>> Vijay
> > > >>>>>>
> > > >>>>>> But the other issue is a bit more complex. 802.16, like
> > > >>>>>>> most cellular protocols, has extensive support for dormant
> > > > mode,
> > > >>>> and
> > > >>>>>>> Wimax Forum is supporting dormant mode in their network
> > > > design.
> > > >>> If
> > > >>>
> > > >>>>> IPsec
> > > >>>>>>> is used, then there is a risk when a mobile node goes into
> > > >>> dormant
> > > >>>
> > > >>>> mode
> > > >>>>>>> that the IPsec SA may time out. It is unfortunate
> that this
> > > > was
> > > >>> not
> > > >>>
> > > >>>>>>> brought up when the discussion about RFC 4285 was
> happening,
> > > > but
> > > >>> I
> > > >>>
> > > >>>>> think
> > > >>>>>>> this might be something that the WG could work on
> > now as part
> > > > of
> > > >>>> the
> > > >>>>> new
> > > >>>>>>> charter. This would make IKEv2/IPsec more attractive as a
> > > >>> security
> > > >>>
> > > >>>>> option
> > > >>>>>>> for cellular operators.
> > > >>>>>>>
> > > >>>>>>> Comments?
> > > >>>>>>>
> > > >>>>>>>            jak
> > > >>>>>>>
> > > >>>>>>>
> > > >>>>>>>
> > > >>>>>>> _______________________________________________
> > > >>>>>>> Mip6 mailing list
> > > >>>>>>> Mip6@ietf.org
> > > >>>>>>> https://www1.ietf.org/mailman/listinfo/mip6
> > > >>>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>> _______________________________________________
> > > >>>>> Mip6 mailing list
> > > >>>>> Mip6@ietf.org
> > > >>>>> https://www1.ietf.org/mailman/listinfo/mip6
> > > >>>>
> > > >>>> "This email message and any attachments are confidential
> > > > information
> > > >>> of
> > > >>>
> > > >>>> Starent Networks, Corp. The information transmitted
> may not be
> > used
> > > > to
> > > >>>> create or change any contractual obligations of
> > Starent Networks,
> > > >>> Corp.
> > > >>>
> > > >>>> Any
> > > >>>> review, retransmission, dissemination or other use of,
> > or taking
> > of
> > > >>> any
> > > >>>
> > > >>>> action in reliance upon this e-mail and its attachments by
> > persons
> > > > or
> > > >>>> entities other than the intended recipient is
> > prohibited. If you
> > > > are
> > > >>> not
> > > >>>
> > > >>>> the
> > > >>>> intended recipient, please notify the sender
> immediately -- by
> > > >>> replying to
> > > >>>
> > > >>>> this message or by sending an email to
> > > > postmaster@starentnetworks.com
> > > >>> --
> > > >>>
> > > >>>> and
> > > >>>> destroy all copies of this message and any
> attachments without
> > > > reading
> > > >>> or
> > > >>>
> > > >>>> disclosing their contents. Thank you."
> > > >>>>
> > > >>>>
> > > >>>>
> > > >>>> _______________________________________________
> > > >>>> Mip6 mailing list
> > > >>>> Mip6@ietf.org
> > > >>>> https://www1.ietf.org/mailman/listinfo/mip6
> > > >>>
> > > >>>
> > > >>>
> > > >>> _______________________________________________
> > > >>> Mip6 mailing list
> > > >>> Mip6@ietf.org
> > > >>> https://www1.ietf.org/mailman/listinfo/mip6
> > > >
> >
> >
> > _______________________________________________
> > Mip6 mailing list
> > Mip6@ietf.org
> > https://www1.ietf.org/mailman/listinfo/mip6
> >
>
>
>
>
>
>
>



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



From mip6-bounces@ietf.org Thu Jul 20 12:20:38 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G3bGQ-0007UU-Qw; Thu, 20 Jul 2006 12:20:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G3bGQ-0007UP-5b
	for mip6@ietf.org; Thu, 20 Jul 2006 12:20:38 -0400
Received: from py-out-1112.google.com ([64.233.166.182])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G3bGO-000231-Ur
	for mip6@ietf.org; Thu, 20 Jul 2006 12:20:38 -0400
Received: by py-out-1112.google.com with SMTP id n25so832068pyg
	for <mip6@ietf.org>; Thu, 20 Jul 2006 09:20:36 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=tLDA/xEmO05FjRGmqXEbN9Ka9jwP4sCOcsuPsg+bZZ5WhoJhi2oIhqmj9CQYL9cn5wAbUro715ySviSR2nGjD+ZuYLxD2NNvPYzqEqV31Ok/fOtAW7IfqznAv8WkO9leivdqomnFSm+Rh1kgq6fbLyVBQiXDJJHK1SFN0qLIiJk=
Received: by 10.35.78.13 with SMTP id f13mr1320453pyl;
	Thu, 20 Jul 2006 09:20:36 -0700 (PDT)
Received: by 10.35.111.9 with HTTP; Thu, 20 Jul 2006 09:20:36 -0700 (PDT)
Message-ID: <729b68be0607200920r74c3811am21b38b0ef105eff8@mail.gmail.com>
Date: Thu, 20 Jul 2006 18:20:36 +0200
From: "Jean-Michel Combes" <jeanmichel.combes@gmail.com>
To: "Alper Yegin" <alper.yegin@yegin.org>
Subject: Re: [Mip6] New charter item: HA assignment
In-Reply-To: <0MKp2t-1G2yNA0sVT-00042Y@mrelay.perfora.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <729b68be0607180431m773dc847qed3e7350819a8d04@mail.gmail.com>
	<0MKp2t-1G2yNA0sVT-00042Y@mrelay.perfora.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi Alper,

IMO, this is more a sub-case of the integrated scenario.

Best regards.

JMC.

2006/7/19, Alper Yegin <alper.yegin@yegin.org>:
> Hi JMC,
>
> In the split scenario, DHCP can be used for HA assignment when the ASP and
> the MSP are the same.
>
> Alper
>
>
> > -----Original Message-----
> > From: Jean-Michel Combes [mailto:jeanmichel.combes@gmail.com]
> > Sent: Tuesday, July 18, 2006 4:31 AM
> > To: Mobile IPv6 Mailing List
> > Subject: [Mip6] New charter item: HA assignment
> >
> > Hi,
> >
> > as promised during the mip6 session, here is a point which, IMO, is
> > important from a MSP's point of view:
> > Actually, the bootstrapping solution, in the split scenario, only
> > propose a HA discovery mechanism (i.e. the MN receives a list of HA,
> > from DNS, and chooses one of them). The MSP has no easy solution to
> > enforce one MN to have a specific HA.
> >
> > Best regards.
> >
> > JMC.
> >
> > _______________________________________________
> > Mip6 mailing list
> > Mip6@ietf.org
> > https://www1.ietf.org/mailman/listinfo/mip6
>
>

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



From mip6-bounces@ietf.org Thu Jul 20 12:25:37 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G3bLE-0004LS-2V; Thu, 20 Jul 2006 12:25:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G3bLC-0004Ko-OY
	for mip6@ietf.org; Thu, 20 Jul 2006 12:25:34 -0400
Received: from py-out-1112.google.com ([64.233.166.183])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G3bLC-0002BI-DI
	for mip6@ietf.org; Thu, 20 Jul 2006 12:25:34 -0400
Received: by py-out-1112.google.com with SMTP id n25so833993pyg
	for <mip6@ietf.org>; Thu, 20 Jul 2006 09:25:34 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=lHkzQ2ctw/vRSg6pqhkG7h9fvgmRdbJ6nCNnJV7JoLkYBuWwtWi89YunbGJASDjEotome5KEz+hpt2WRXHcNjKItBPIThgew/stegFQl3AfVaAP1H+VTuFxLTiZE9qWaPH+b38D4tJijTg7QFhenz7PBgB/utTPeR+ofU4915IY=
Received: by 10.35.27.2 with SMTP id e2mr1333078pyj;
	Thu, 20 Jul 2006 09:25:33 -0700 (PDT)
Received: by 10.35.111.9 with HTTP; Thu, 20 Jul 2006 09:25:33 -0700 (PDT)
Message-ID: <729b68be0607200925m4c228d6eo651ad6c79fd1c295@mail.gmail.com>
Date: Thu, 20 Jul 2006 18:25:33 +0200
From: "Jean-Michel Combes" <jeanmichel.combes@gmail.com>
To: "Kilian Weniger" <Kilian.Weniger@eu.panasonic.com>
Subject: Re: [Mip6] New charter item: HA assignment
In-Reply-To: <4D2F935F08D41A4C8866693F4F0D7C4FD44CE2@lan-ex-01.panasonic.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <02fc01c6aa99$de869d00$196115ac@dcml.docomolabsusa.com>
	<4D2F935F08D41A4C8866693F4F0D7C4FD44CE2@lan-ex-01.panasonic.de>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0cff8c3ec906d056784362c06f5f88c1
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi Kilian,

2006/7/19, Kilian Weniger <Kilian.Weniger@eu.panasonic.com>:
> Another possible solution is described in
> draft-dupont-ikev2-haassign-01.txt. The MN sends the IKE_SA_INIT to an
> anycast HA address and let the anycast receiver forward the message to
> the "best" HA. In this case, the "best" HA may be different for every MN
> and would be selected based on the source address of the IKE_SA_INIT.

This is a possible solution. Now, the problem is what mechanism to use
to forward the message to the "best" HA? Maybe, this is a sub-case of
use for the future HA reliability protocol?

Best regards.

JMC.

>
> -Kilian
>
> > -----Original Message-----
> > From: James Kempf [mailto:kempf@docomolabs-usa.com]
> > Sent: Dienstag, 18. Juli 2006 20:42
> > To: Alexandru Petrescu; Jean-Michel Combes
> > Cc: Mobile IPv6 Mailing List
> > Subject: Re: [Mip6] New charter item: HA assignment
> >
> > So there are three ways I can think of that one could go
> > about assigning an
> > HA.
> >
> > 1) The MN uses the weights returned with the DNS SRV record
> > from RFC 2782 to
> > guide its selection of HAs. Less preferred HAs are later in
> > the preference
> > ordering. The authors of RFC 2782 complain about weights
> > being a relatively
> > coarse-grained mechanism that isn't up to providing dynamic
> > load balancing.
> > I think the time granularity of the SRV updates would  be
> > about 15 seconds
> > minimum, if dynamic DNS is used, since I'm told that is about
> > the amount of
> > time one should expect it to take for a dynamic DNS update to
> > propagate.
> >
> > 2) For a more dynamic mechanism, the HA initially tried by
> > the MN can turn
> > down the MN's request to perform IKEv2. Or the HA could deny
> > the MN an HoA.
> > This would cause the MN to roll over to the next HA on the
> > list. When the MN
> > hit the right HA, the IKEv2 transaction would succeed. This has the
> > disadvantage that it increases the amount of time the MN
> > needs to bootstrap.
> >
> > 3) Immediately after the MN finishes the IKEv2 transaction,
> > the first HA
> > could send a HA Switch message
> > (draft-ietf-mip6-ha-switch-00.txt) within the
> > IPsec SA, telling the MN to go elsewhere. The MN would be
> > delayed  by the
> > amount of time needed to do the IKEv2 transaction, but that
> > does provide
> > security. This seems like it would be the most direct way.
> >
> > I think a combination of these three mechanisms would be
> > sufficient to
> > provide HA assignment for the kinds of deployment scenerios
> > that the split
> > scenerio was designed to accommodate. The first mechanism
> > would provide load
> > balancing over longer periods while the second would provide
> > support for
> > fast transients, and the third would provide a way to
> > directly and securely
> > tell an MN where to go. Ideally, the MN wouldn't have to go
> > through more
> > than one additional HA before it got service, reducing the
> > amount of lag.
> >
> > On the other hand, if you want a way to say "thou shalt use
> > this HA" without
> > a lot of initial negotiation, then I'd suggest using the intergrated
> > scenerio and simply let DHCP assign the MN to an HA (though
> > that would
> > require DHCP security).
> >
> > If these are insufficient, then the only other suggestion is
> > that an IKEv2
> > INFORMATIONAL message be defined directing the MN to try
> > IKEv2 with another
> > node (which would be the preferred HA). Such a message could
> > be used for VPN
> > server load balancing too.
> >
> >             jak
> >
> >
> >
> >
> >
> >
> > ----- Original Message -----
> > From: "Alexandru Petrescu" <alexandru.petrescu@motorola.com>
> > To: "Jean-Michel Combes" <jeanmichel.combes@gmail.com>
> > Cc: "Mobile IPv6 Mailing List" <mip6@ietf.org>
> > Sent: Tuesday, July 18, 2006 9:49 AM
> > Subject: Re: [Mip6] New charter item: HA assignment
> >
> >
> > > Jean-Michel Combes wrote:
> > >> Hi,
> > >>
> > >> as promised during the mip6 session, here is a point
> > which, IMO, is
> > >> important from a MSP's point of view: Actually, the bootstrapping
> > >> solution, in the split scenario, only propose a HA
> > discovery mechanism
> > >> (i.e. the MN receives a list of HA, from DNS, and chooses
> > one of them).
> > >> The MSP has no easy solution to enforce one MN to have a
> > specific HA.
> > >
> > > One possible way is for a HA to stop sending BAck, at which
> > point an MN
> > > would send DHAAD Request again, and a different HA replies
> > back DHAAD,
> > > so end result is MN is assigned a new HA.
> > >
> > > Another way is for the new HA to send Binding Refresh Request to MN
> > > (even if it has no BC entry for it).
> > >
> > > Another way, if the split bootstrapping advances, is for the MSP to
> > > dynamically update the DNS data about HAs, so when MN bootstraps it
> > > obtains a different HA.
> > >
> > > If the HA address is discovered with DHCP then I think the
> > DHCP Server
> > > can send specific messages to MN (unsolicited by MN).
> > >
> > > It would require relaxing some language in rfc 3775 and
> > probably extending
> > > BRR.
> > >
> > > It would be helpful to know when would an MSP like the MN
> > to choose a
> > > different HA, for what reasons.
> > >
> > > Alex
> > >
> > >
> > > _______________________________________________
> > > Mip6 mailing list
> > > Mip6@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/mip6
> > >
> >
> >
> >
> > _______________________________________________
> > Mip6 mailing list
> > Mip6@ietf.org
> > https://www1.ietf.org/mailman/listinfo/mip6
> >
> >
>
>
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
>

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



From mip6-bounces@ietf.org Thu Jul 20 12:35:57 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G3bVB-0003nC-Ds; Thu, 20 Jul 2006 12:35:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G3bVA-0003i1-5s
	for mip6@ietf.org; Thu, 20 Jul 2006 12:35:52 -0400
Received: from key1.docomolabs-usa.com ([216.98.102.225]
	helo=fridge.docomolabs-usa.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G3bV8-0002R8-Nj
	for mip6@ietf.org; Thu, 20 Jul 2006 12:35:52 -0400
Message-ID: <023601c6ac1a$d04e7e10$196115ac@dcml.docomolabsusa.com>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Soliman, Hesham" <hsoliman@qualcomm.com>,
	"Narayanan, Vidya" <vidyan@qualcomm.com>,
	"Tsirtsis, George" <tsirtsis@qualcomm.com>,
	"Gerardo Giaretta" <gerardo.giaretta@gmail.com>
References: <7EB20EA0938B4D42A2D82689365C9B7A0CBFC0@NAEX14.na.qualcomm.com>
Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
Date: Thu, 20 Jul 2006 09:37:38 -0700
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

 > It seems to be an issue with Wimax Forum, and one of the
 > motivating reasons
 > why they and 3GPP2 insisted upon the RFC 4285 Auth option.

=> Honestly, if that's what motivated them to do 4285 then I'm worried
about the rest
of their system! I *think* 4285 was done to avoid implementing IKE/IPsec
primarily. That makes more sense to me than doing it to avoid confusion
about timers which can be set properly by an admin.

jak>> They now also specify IKEv2, but default is 4285. The other reason 
originally for not wanting to use IKE was lack of EAP support, same as for 
pp2, but that has now changed with IKEv2.

 >
 > To turn this around, do you or anyone have an idea why IKEv2
 > doesn't allow
 > the timer values to be negotiated? Was this just a matter of
 > simplification
 > or was there some security issue?

=> Sounds like a strange design choice to me, the old one allowed for
timer negotiation.

jak>> See my response to Vidya on this, it's mentioned in RFC 4306. I think 
it was primarily for simplification. IKEv1 had timers as part of ISAKMP. 
ISAKMP was stripped out in IKEv2, largely for the better, but in the process 
I think they dropped a couple of things that might have been useful in some 
cases.

jak>> Anyway, do you have any objection to putting an IKEv2 INFORMATIONAL 
message into the charter? Or do you think it should be done elsewhere (and 
if so, any suggestions about where)?

            jak


 >
 >             jak
 >
 > ----- Original Message ----- 
 > From: "Narayanan, Vidya" <vidyan@qualcomm.com>
 > To: "Soliman, Hesham" <hsoliman@qualcomm.com>; "Tsirtsis, George"
 > <tsirtsis@qualcomm.com>; "Gerardo Giaretta"
 > <gerardo.giaretta@gmail.com>;
 > "James Kempf" <kempf@docomolabs-usa.com>
 > Cc: <mip6@ietf.org>
 > Sent: Wednesday, July 19, 2006 3:01 PM
 > Subject: RE: [Mip6] New Charter Item:Support for Dormant
 > Mode Alert to HA?
 >
 >
 > I agree. I'm surprised this is seen as a big problem.
 >
 > Vidya
 >
 > ________________________________
 >
 > From: Soliman, Hesham [mailto:hsoliman@qualcomm.com]
 > Sent: Wed 7/19/2006 9:30 AM
 > To: Tsirtsis, George; Gerardo Giaretta; James Kempf
 > Cc: mip6@ietf.org
 > Subject: RE: [Mip6] New Charter Item:Support for Dormant
 > Mode Alert to HA?
 >
 >
 >
 >
 >  > > - another issue is the lifetime of the BCE. It seems
 > not acceptable
 >  > > that the MN needs to go back to active state in order to send a
 >  > > refresh BU to the HA.
 >
 > => I think this is too radical. It's perfectly acceptable to
 > do that if
 > it only happens once an hour or once every two hours ...etc. If it
 > happens once a minute then of course it's a problem. I don't
 > think you
 > can make a blanket statement that disregards the frequency of the
 > updates.
 >
 >  > MIP6, similar to
 >  > > the one proposed by James, may make sense.
 >
 > => Too premature IMO.
 >
 > Hesham
 >
 > _______________________________________________
 > Mip6 mailing list
 > Mip6@ietf.org
 > https://www1.ietf.org/mailman/listinfo/mip6
 >
 >
 >
 >
 >



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



From mip6-bounces@ietf.org Thu Jul 20 12:54:56 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G3bnb-0007lc-QN; Thu, 20 Jul 2006 12:54:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G3bna-0007ir-Bz
	for mip6@ietf.org; Thu, 20 Jul 2006 12:54:54 -0400
Received: from key1.docomolabs-usa.com ([216.98.102.225]
	helo=fridge.docomolabs-usa.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G3bfb-0003s2-Qo
	for mip6@ietf.org; Thu, 20 Jul 2006 12:46:41 -0400
Message-ID: <024c01c6ac1c$50dd9b00$196115ac@dcml.docomolabsusa.com>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Jean-Michel Combes" <jeanmichel.combes@gmail.com>
References: <729b68be0607180431m773dc847qed3e7350819a8d04@mail.gmail.com>
	<44BD1105.5040904@motorola.com>
	<02fc01c6aa99$de869d00$196115ac@dcml.docomolabsusa.com>
	<729b68be0607200906g427688b1l2b127997fb3ba9b4@mail.gmail.com>
Subject: Re: [Mip6] New charter item: HA assignment
Date: Thu, 20 Jul 2006 09:48:24 -0700
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=response
Content-Transfer-Encoding: 7bit
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>,
	Alexandru Petrescu <alexandru.petrescu@motorola.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Jean-Michel,

>> On the other hand, if you want a way to say "thou shalt use this HA" 
>> without
>> a lot of initial negotiation, then I'd suggest using the intergrated
>> scenerio and simply let DHCP assign the MN to an HA (though that would
>> require DHCP security).
>
> Yes but we need solutions for all the scenarios. I don't see an
> operator sending a message to a mobility subscriber saying "You are
> not in an integrated case: please, stop using the IETF network if you
> want to bootstrap your IPv6 mobility service" ;)
>

The assumption behind the integrated scenerio is that the operator has 
deployed it and that there is configuration from the operator when the 
terminal first boots up instructing the terminal to henceforth try DHCP for 
HA configuration prior to rolling over to the split scenerio method.

>>
>> If these are insufficient, then the only other suggestion is that an 
>> IKEv2
>> INFORMATIONAL message be defined directing the MN to try IKEv2 with 
>> another
>> node (which would be the preferred HA). Such a message could be used for 
>> VPN
>> server load balancing too.
>
> Maybe too depend to a specific service: I am not sure that IPsec guys
> will accept such an addition in IKEv2.
>

IPsec WG is no more. Adding INFORMATIONAL messages to IKEv2 is OK, of 
course, it would need to go through SAAG review as with every other security 
item, and they might object.

Anyway, it seems that HA assignment can be done using the HA Switch message 
within the IPsec SA, at some expense to establish the SA with the original 
HA. But I believe that expense would be needed in any case to establish 
security, and it won't be acceptable from a security standpoint to send an 
HA assignment message without security. An IKEv2 message would reduce the 
amount of security configuration slightly, but is it really necessary?

            jak




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



From mip6-bounces@ietf.org Thu Jul 20 13:14:06 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G3c66-00055k-6s; Thu, 20 Jul 2006 13:14:02 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G3c65-00055I-8K
	for mip6@ietf.org; Thu, 20 Jul 2006 13:14:01 -0400
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G3c13-0006mC-Uq
	for mip6@ietf.org; Thu, 20 Jul 2006 13:08:51 -0400
Received: from magus.qualcomm.com (magus.qualcomm.com [129.46.61.148])
	by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k6KH8ins014893
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Thu, 20 Jul 2006 10:08:45 -0700
Received: from NAEXBR03.na.qualcomm.com (naexbr03.qualcomm.com
	[129.46.134.172])
	by magus.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id k6KH5WRQ027146; 
	Thu, 20 Jul 2006 10:08:44 -0700 (PDT)
Received: from NAEX14.na.qualcomm.com ([10.47.5.242]) by
	NAEXBR03.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 20 Jul 2006 10:08:39 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
Date: Thu, 20 Jul 2006 10:08:28 -0700
Message-ID: <7EB20EA0938B4D42A2D82689365C9B7A0CBFFF@NAEX14.na.qualcomm.com>
In-Reply-To: <023601c6ac1a$d04e7e10$196115ac@dcml.docomolabsusa.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
Thread-Index: AcasGpuGWx+tPG3NS4q5N8WNVaobTwABAVeg
From: "Soliman, Hesham" <hsoliman@qualcomm.com>
To: "James Kempf" <kempf@docomolabs-usa.com>,
	"Narayanan, Vidya" <vidyan@qualcomm.com>,
	"Tsirtsis, George" <tsirtsis@qualcomm.com>,
	"Gerardo Giaretta" <gerardo.giaretta@gmail.com>
X-OriginalArrivalTime: 20 Jul 2006 17:08:39.0335 (UTC)
	FILETIME=[251E6370:01C6AC1F]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

=20
 > jak>> Anyway, do you have any objection to putting an IKEv2=20
 > INFORMATIONAL=20
 > message into the charter? Or do you think it should be done=20
 > elsewhere (and=20
 > if so, any suggestions about where)?

=3D> Well, I don't think it's a serious issue to begin with, because a
reasonable admin will set the timers to a reasonable time. But, to
answer your question, I don't mind having an additional IKEv2 message
provided that it is not sent with the BU and doesn't require MIP6 and
IPsec implementations to cooperate. So if the new message basically sets
the lifetime for the SA, regardless of who's using the SA (MIP or some
other app) then I'm ok with it.

Hesham


 >=20
 >             jak
 >=20
 >=20
 >  >
 >  >             jak
 >  >
 >  > ----- Original Message -----=20
 >  > From: "Narayanan, Vidya" <vidyan@qualcomm.com>
 >  > To: "Soliman, Hesham" <hsoliman@qualcomm.com>; "Tsirtsis, George"
 >  > <tsirtsis@qualcomm.com>; "Gerardo Giaretta"
 >  > <gerardo.giaretta@gmail.com>;
 >  > "James Kempf" <kempf@docomolabs-usa.com>
 >  > Cc: <mip6@ietf.org>
 >  > Sent: Wednesday, July 19, 2006 3:01 PM
 >  > Subject: RE: [Mip6] New Charter Item:Support for Dormant
 >  > Mode Alert to HA?
 >  >
 >  >
 >  > I agree. I'm surprised this is seen as a big problem.
 >  >
 >  > Vidya
 >  >
 >  > ________________________________
 >  >
 >  > From: Soliman, Hesham [mailto:hsoliman@qualcomm.com]
 >  > Sent: Wed 7/19/2006 9:30 AM
 >  > To: Tsirtsis, George; Gerardo Giaretta; James Kempf
 >  > Cc: mip6@ietf.org
 >  > Subject: RE: [Mip6] New Charter Item:Support for Dormant
 >  > Mode Alert to HA?
 >  >
 >  >
 >  >
 >  >
 >  >  > > - another issue is the lifetime of the BCE. It seems
 >  > not acceptable
 >  >  > > that the MN needs to go back to active state in=20
 > order to send a
 >  >  > > refresh BU to the HA.
 >  >
 >  > =3D> I think this is too radical. It's perfectly acceptable to
 >  > do that if
 >  > it only happens once an hour or once every two hours ...etc. If it
 >  > happens once a minute then of course it's a problem. I don't
 >  > think you
 >  > can make a blanket statement that disregards the frequency of the
 >  > updates.
 >  >
 >  >  > MIP6, similar to
 >  >  > > the one proposed by James, may make sense.
 >  >
 >  > =3D> Too premature IMO.
 >  >
 >  > Hesham
 >  >
 >  > _______________________________________________
 >  > Mip6 mailing list
 >  > Mip6@ietf.org
 >  > https://www1.ietf.org/mailman/listinfo/mip6
 >  >
 >  >
 >  >
 >  >
 >  >
 >=20
 >=20
 >=20

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



From mip6-bounces@ietf.org Thu Jul 20 13:54:15 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G3ciw-0008JR-4Z; Thu, 20 Jul 2006 13:54:10 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G3civ-0008Gv-Ah
	for mip6@ietf.org; Thu, 20 Jul 2006 13:54:09 -0400
Received: from mail1.azairenet.com ([66.92.223.4] helo=bart.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G3caH-0002nu-3y
	for mip6@ietf.org; Thu, 20 Jul 2006 13:45:14 -0400
Received: from [10.1.201.0] ([10.1.201.0]) by bart.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Thu, 20 Jul 2006 10:45:10 -0700
Message-ID: <44BFC0C5.2000705@azairenet.com>
Date: Thu, 20 Jul 2006 10:43:33 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Debian Thunderbird 1.0.2 (X11/20060423)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Jean-Michel Combes <jeanmichel.combes@gmail.com>
Subject: Re: [Mip6] New charter item: HA assignment
References: <729b68be0607180431m773dc847qed3e7350819a8d04@mail.gmail.com>	
	<44BD28C9.50403@azairenet.com>
	<729b68be0607200744p4ed083c0l4f7a4cddb0897fa7@mail.gmail.com>
In-Reply-To: <729b68be0607200744p4ed083c0l4f7a4cddb0897fa7@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 20 Jul 2006 17:45:10.0720 (UTC)
	FILETIME=[3F493400:01C6AC24]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Jean-Michel Combes wrote:

>> we can come up with some hacks to the HA discovery
>> mechanism to force the MN to pick a particular HA,
>> but I would rather avoid it. it would be better if
>> you tell us what the scenario and which are the
>> entities involved. then we can design a solution
>> for the specific scenario.
> 
> 
> A MSP wants to assign a specific HA to a specific MN because:
> - the HAs are owned by the MSP (the main reason!!! :)
> - the MN uses a specific mobility mechanism (e.g. MIPv6, HMIPv6, NEMO, 
> Monami6)
> - the operator wants to loadbalance the charge on the different HAs it
> owns during the bootstrapping (e.g to avoid DoS attacks)
> - the operator offers different types of QoS on the HAs

by scenario I meant the specific deployment. it might be
better to handle this deployment specific instead of trying
to design a generic solution.

Vijay

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



From mip6-bounces@ietf.org Thu Jul 20 18:51:24 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G3hMQ-0003c9-Vz; Thu, 20 Jul 2006 18:51:15 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G3hLq-0001wF-Ou
	for mip6@ietf.org; Thu, 20 Jul 2006 18:50:38 -0400
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G3hGw-0008N0-Uz
	for mip6@ietf.org; Thu, 20 Jul 2006 18:45:35 -0400
Received: from magus.qualcomm.com (magus.qualcomm.com [129.46.61.148])
	by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k6KMjPfF010460
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Thu, 20 Jul 2006 15:45:25 -0700
Received: from NAEXBR03.na.qualcomm.com (naexbr03.qualcomm.com
	[129.46.134.172])
	by magus.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id k6KMipbm015501; 
	Thu, 20 Jul 2006 15:45:24 -0700 (PDT)
Received: from NAEX13.na.qualcomm.com ([129.46.51.248]) by
	NAEXBR03.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 20 Jul 2006 15:45:21 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
Date: Thu, 20 Jul 2006 15:45:02 -0700
Message-ID: <C24CB51D5AA800449982D9BCB90325130A143B@NAEX13.na.qualcomm.com>
In-Reply-To: <01f501c6ac18$9d9ccf50$196115ac@dcml.docomolabsusa.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
Thread-Index: AcasGGPN7GKI8KDfSPO0fmsGtyx6gwAMAQUA
From: "Narayanan, Vidya" <vidyan@qualcomm.com>
To: "James Kempf" <kempf@docomolabs-usa.com>,
	"Tsirtsis, George" <tsirtsis@qualcomm.com>,
	"Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
X-OriginalArrivalTime: 20 Jul 2006 22:45:21.0276 (UTC)
	FILETIME=[2E69F3C0:01C6AC4E]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: fd911903d9eb33179d1ec28b0417afe8
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org


>=20
> The fact is that MIP and IKE are managed by two completely=20
> different protocols. RFC 4301 does not specify anything about=20
> timeouts in the SPD or SAD, which would allow some kind of=20
> per host or per application timeout customization. Your=20
> proposal means that the operator would have to manage its HA=20
> with the same timeouts for the HA to mobile node MIP traffic=20
> as for, say, signaling traffic between two HAs doing the HA=20
> reliability protocol or some other IPsec application, because=20
> the basic IPsec architecture provides no way to differentiate=20
> between the timing requirements of the two.=20

I don't see why this is the case. The timers are managed per IPsec
session - so, why would the timer values be the same for HA to MN and HA
to HA or other entity IPsec sessions?=20

> I think this is=20
> unreasonable, as the ability of the two to respond to=20
> keepalives could be quite different. Furthermore, RFC 4306=20
> says this about why any timeouts were left out of IKEv2 (Section 2.4):
>=20
>    Numbers of retries and lengths of timeouts are not covered in this
>    specification because they do not affect interoperability.  It is
>    suggested that messages be retransmitted at least a dozen=20
> times over
>    a period of at least several minutes before giving up on an SA, but
>    different environments may require different rules.
>=20

I had stated some of the reasons in one of my earlier emails - timer
and/or lifetime negotiation in a key management protocol is typically
not very useful.=20

> As with other cases involving mobile nodes and IKEv2 (whence=20
> came MOBIKE), this does not address the needs of wireless. An=20
> implementation on a laptop with 802.11, which doesn't have=20
> proper dormant mode support, doesn't need the ability to=20
> lengthen the timeout for dormant mode because it will be=20
> woken up by the AP when a keepalive arrives. An=20
> implementation on a cellphone which does have proper dormant=20
> mode support won't, or, at least, it shouldn't if we want to=20
> provide proper support for dormant mode. Should the combined=20
> BU/SA timeout be the same for both? If so and it is set to the
> 802.11 timeout, having no way for the cellphone to lengthen=20
> its timeout when it goes into dormant mode means drastically=20
> reduced cellphone battery lifetime and unhappy customers. If=20
> it is set to the expected cellphone dormant mode lifetime=20
> then the SAD has a bunch of entries for laptops, whose owners=20
> have closed the lids and jumped on a plane, hanging around=20
> when they aren't needed. The effect won't be to prohibit=20
> interoperability, but it will result in a considerable amount=20
> of unnecessary traffic and reduced customer satisfaction.
>=20

There are two sides to this problem - one is the capability for MNs to
request a certain lifetime/timer value - here, when a mobile is entering
dormant mode, it doesn't always know how long it is going to be in
dormant mode. So, what is the timer value being requested? The second
side of the problem is that the server can, at any time, get rid of the
SA depending on resources it has. So, the fact that a mobile requested
an extension of lifetime doesn't particularly matter.=20

> Furthermore, IKEv1 had a way to do lifetime negotiation=20
> (Section 4.5 in RFC
> 2407) via the SA lifetime in the ISAKMP messaging. So I don't=20
> quite understand why you are opposed to adding an IKEv2=20
> INFORMATIONAL exchange for this purpose.
>=20

IKEv2 acknowledged the lack of this feature and decided it is not
needed. So, a careful scrutiny of whether we need it is quite important.


> Your point about 3GPP2 needing EAP support is also a concern=20
> to Wimax Forum, as I mentioned in the original email that=20
> started this thread, but, in addition, I was hearing that=20
> they were concerned about IPsec SA timeout during dormant=20
> mode. I sent email to the Wimax Forum list, and Raj confirmed=20
> that this was, indeed, a concern.
>=20
> And finally regarding your point:
>=20
>     As I said in my earlier emails, all the concerns tied to=20
> the IPsec timer
>     values seem to equally apply to the BU lifetime as well -=20
> hence, I am
>     not yet seeing a need for adding this functionality to=20
> IKEv2 per say.
>=20
> The problem is that it is possible to extend the binding=20
> lifetime by sending a BU just before the mobile node goes=20
> into dormant mode, but there is no support in IKEv2 for=20
> extending the SA lifetime.
>=20


But, is a mobile that is about to go into dormant really sending a BU
and waiting for a BA before going dormant? If all upper layer protocols
took that approach, the mobile will potentially have to send a lot of
messages prior to entering dormant mode - that doesn't seem to be a good
design, IMHO. If we consider the fact that a mobile, at any time, may be
dealing with lifetimes in various protocols (say, MIP, IKEv2, SIP, TLS,
etc.), I would think it would be much more expensive to send all these
messages prior to going dormant.=20

Vidya


>         jak
>=20
>=20
>=20
> ----- Original Message -----
> From: "Narayanan, Vidya" <vidyan@qualcomm.com>
> To: "James Kempf" <kempf@docomolabs-usa.com>; "Tsirtsis, George"=20
> <tsirtsis@qualcomm.com>; "Vijay Devarapalli"=20
> <vijay.devarapalli@azairenet.com>
> Cc: <mip6@ietf.org>
> Sent: Wednesday, July 19, 2006 4:32 PM
> Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode=20
> Alert to HA?
>=20
>=20
>=20
> >
> > Maybe the incidence of mobiles dropping out is higher for
> > active than dormant mode mobiles?
> >
>=20
> Hmmm.. I'm not so sure. Given that the IPsec SA under discussion is
> really for MIP6, I can see why the BU lifetime and the IPsec=20
> idle timer
> can be in sync without a problem. So, I am surprised that there are
> independent requirements here.
>=20
> > Also, another reason for not having the timers have policy
> > fixed values is so that the timers can be set depending on
> > the kind of device. I mentioned this in a response to George.
> >
>=20
> Yes, I recall that. But, whatever considerations are given to the type
> of device would, I'd think, apply to the BU lifetime as well.
>=20
> Vidya
>=20
>=20
> >             jak
> >
> > ----- Original Message -----
> > From: "Narayanan, Vidya" <vidyan@qualcomm.com>
> > To: "James Kempf" <kempf@docomolabs-usa.com>; "Tsirtsis, George"
> > <tsirtsis@qualcomm.com>; "Vijay Devarapalli"
> > <vijay.devarapalli@azairenet.com>
> > Cc: <mip6@ietf.org>
> > Sent: Wednesday, July 19, 2006 2:55 PM
> > Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode
> > Alert to HA?
> >
> >
> > What would be the motivation for maintaining such mode=20
> specific timer
> > values?
> >
> > Vidya
> >
> > ________________________________
> >
> > From: James Kempf [mailto:kempf@docomolabs-usa.com]
> > Sent: Wed 7/19/2006 8:47 AM
> > To: Narayanan, Vidya; Tsirtsis, George; Vijay Devarapalli
> > Cc: mip6@ietf.org
> > Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode
> > Alert to HA?
> >
> >
> >
> > The operator may want to keep active mode timers short, then
> > set them longer
> > only if the mobile goes into dormant mode.
> >
> >             jak
> >
> >
> >
> > ----- Original Message -----
> > From: "Narayanan, Vidya" <vidyan@qualcomm.com>
> > To: "Tsirtsis, George" <tsirtsis@qualcomm.com>; "Vijay Devarapalli"
> > <vijay.devarapalli@azairenet.com>
> > Cc: <mip6@ietf.org>; "James Kempf" <kempf@docomolabs-usa.com>
> > Sent: Tuesday, July 18, 2006 4:26 PM
> > Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode
> > Alert to HA?
> >
> >
> > I'm just catching up with this discussion.
> >
> > If the IPsec idle timer is at least equal to the BU lifetime, why is
> > there a need for any other signaling related to dormant mode?
> > Given that
> > the timer values are a matter of policy, this should be do-able.
> >
> > Vidya
> >
> > > -----Original Message-----
> > > From: Tsirtsis, George [mailto:tsirtsis@qualcomm.com]
> > > Sent: Tuesday, July 18, 2006 3:11 PM
> > > To: Vijay Devarapalli
> > > Cc: mip6@ietf.org; James Kempf
> > > Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode
> > > Alert to HA?
> > >
> > > Yes, I meant DPD.
> > >
> > > There is a fate sharing here between MIP6 state and IPSEC
> > > state. I guess the SA lifetime and DPD timer was introduced
> > > to catch the general case but they do not make sense to be
> > > much different than the MIP lifetime when that is used.
> > >
> > > It is indeed strange, however, that IPSEC does not allow for
> > > negotiation of these parameters. I guess people will have to
> > > use reasonable values in each deployment depending what they
> > > are doing.
> > >
> > > George
> > >
> > > > -----Original Message-----
> > > > From: Vijay Devarapalli [mailto:vijay.devarapalli@azairenet.com]
> > > > Sent: Tuesday, July 18, 2006 6:06 PM
> > > > To: Tsirtsis, George
> > > > Cc: James Kempf; Chowdhury, Kuntal; mip6@ietf.org
> > > > Subject: Re: [Mip6] New Charter Item:Support for Dormant
> > > Mode Alert to
> > > HA?
> > > >
> > > > Tsirtsis, George wrote:
> > > > > So how often PDP messages are sent is also local policy?
> > > >
> > > > I guess you meant DPD. yes it is local policy. the initiator and
> > > > responder configure this independently.
> > > >
> > > > > In which case
> > > > > it can be configured to a time that makes sense for MIP
> > > or a given
> > > > > deployment scenario.
> > > >
> > > > Yes. however, the IPsec implementation should allow for
> > > sufficiently
> > > > large values for DPD timer. but then again DPD exists so
> > > that unwanted
> > > > IPsec state is removed if the other end goes down or if
> > there is no
> > > > traffic for a long time.
> > > >
> > > > Vijay
> > > >
> > > > > George
> > > > >
> > > > >> -----Original Message-----
> > > > >> From: Vijay Devarapalli
> > [mailto:vijay.devarapalli@azairenet.com]
> > > > >> Sent: Tuesday, July 18, 2006 5:42 PM
> > > > >> To: James Kempf
> > > > >> Cc: Tsirtsis, George; Chowdhury, Kuntal; mip6@ietf.org
> > > > >> Subject: Re: [Mip6] New Charter Item:Support for Dormant
> > > Mode Alert
> > > to
> > > > > HA?
> > > > >> James Kempf wrote:
> > > > >>> I don't know. What do operators typically set the SA
> > > lifetime to?
> > > > > Though
> > > > >>> perhaps this is an unanswerable question because,=20
> as yet, has
> > > > > anybody
> > > > >>> deployed MIPv6?
> > > > >> this is more of an IPsec issue. it depends on the local
> > > policy on
> > > > >> the initiator and responder. however, as long as there
> > > is traffic
> > > > >> and there are responses to DPD messages, the IPsec SA is not
> > > > >> deleted.
> > > > >>
> > > > >> Vijay
> > > > >>
> > > > >>> My only observation is that this seems to be an issue
> > with Wimax
> > > > > Forum,
> > > > >>> and one of the primary motivators for wanting to use
> > > the RFC 4285
> > > > > Auth
> > > > >>> Option. If IETF and the MIP6 WG would like to
> > encourage them to
> > > use
> > > > > IKE
> > > > >>> (as seemed to be the sentiment when RFC 4285 was
> > discussed, and
> > > one
> > > > > of
> > > > >>> the reasons why it is not PS), it might be worthwhile
> > to try to
> > > > > address
> > > > >>> their concerns.
> > > > >>>
> > > > >>>            jak
> > > > >>>
> > > > >>> ----- Original Message ----- From: "Tsirtsis, George"
> > > > >>> <tsirtsis@qualcomm.com>
> > > > >>> To: "James Kempf" <kempf@docomolabs-usa.com>;
> > > "Chowdhury, Kuntal"
> > > > >>> <kchowdhury@starentnetworks.com>
> > > > >>> Cc: <mip6@ietf.org>
> > > > >>> Sent: Tuesday, July 18, 2006 12:10 PM
> > > > >>> Subject: RE: [Mip6] New Charter Item:Support for=20
> Dormant Mode
> > > Alert
> > > > > to
> > > > >> HA?
> > > > >>>
> > > > >>> May I ask, what is the typical lifetime of the SA and
> > what would
> > > you
> > > > >>> lengthen it to?
> > > > >>> George
> > > > >>>
> > > > >>>> -----Original Message-----
> > > > >>>> From: James Kempf [mailto:kempf@docomolabs-usa.com]
> > > > >>>> Sent: Tuesday, July 18, 2006 2:43 PM
> > > > >>>> To: Chowdhury, Kuntal
> > > > >>>> Cc: mip6@ietf.org
> > > > >>>> Subject: Re: [Mip6] New Charter Item:Support for=20
> Dormant Mode
> > > Alert
> > > > > to
> > > > >>> HA?
> > > > >>>
> > > > >>>> Kuntal,
> > > > >>>>
> > > > >>>> The intent is not to introduce something that the MN
> > would send
> > > > > during
> > > > >>>> dormant mode. Indeed, as you have described, this would
> > > negatively
> > > > >>> impact
> > > > >>>
> > > > >>>> battery life.
> > > > >>>>
> > > > >>>> The intent is to provide a way for the MN to say that
> > > it is about
> > > > > to
> > > > >>> go
> > > > >>>
> > > > >>>> into
> > > > >>>> dormant mode, so please lengthen the IPsec SA
> > timeout to avoid
> > > > > having
> > > > >>> it
> > > > >>>
> > > > >>>> expire for some longer period of time.
> > > > >>>>
> > > > >>>>             jak
> > > > >>>>
> > > > >>>> ----- Original Message -----
> > > > >>>> From: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
> > > > >>>> To: "James Kempf" <kempf@docomolabs-usa.com>
> > > > >>>> Cc: <mip6@ietf.org>
> > > > >>>> Sent: Tuesday, July 18, 2006 11:20 AM
> > > > >>>> Subject: RE: [Mip6] New Charter Item:Support for=20
> Dormant Mode
> > > Alert
> > > > > to
> > > > >>> HA?
> > > > >>>
> > > > >>>>
> > > > >>>> James,
> > > > >>>>
> > > > >>>> This is a good discussion. Indeed the need for IPsec
> > keepalives
> > > (or
> > > > >>> DPD)
> > > > >>>
> > > > >>>> over the air when the MN is dormant (or idle) is an
> > > issue in the
> > > > >>>> cellular networks. The issue is Not that there are no mip6
> > > messages
> > > > >>>> defined or the HA is not aware of dormancy. It is more of a
> > > paging
> > > > >>>> channel capacity issue, MN's battery life issue and
> > > the signaling
> > > > >>>> overhead to transport the keepalives for a dormant=20
> MN issue.
> > > > >>>>
> > > > >>>> So, any new message however small won't solve the
> > > problem, IMHO.
> > > > >>>>
> > > > >>>> -Kuntal
> > > > >>>>
> > > > >>>>
> > > > >>>>> -----Original Message-----
> > > > >>>>> From: James Kempf [mailto:kempf@docomolabs-usa.com]
> > > > >>>>> Sent: Tuesday, July 18, 2006 11:17 AM
> > > > >>>>> To: Vijay Devarapalli
> > > > >>>>> Cc: mip6@ietf.org
> > > > >>>>> Subject: Re: [Mip6] New Charter Item:Support for
> > Dormant Mode
> > > > > Alert
> > > > >>> to
> > > > >>>
> > > > >>>> HA?
> > > > >>>>> For security, the message would need to be sent
> > within an SA.
> > > > > There
> > > > >>> is
> > > > >>>
> > > > >>>> a
> > > > >>>>> question about which.
> > > > >>>>>
> > > > >>>>> One possibility is to do a Mobility Extension (call
> > > the messages
> > > > >>>> Sleeping
> > > > >>>>> and WakingUp) and send it within the IPsec SA between
> > > the HA and
> > > > > MN.
> > > > >>>> The
> > > > >>>>> MN
> > > > >>>>> sends the Sleeping message when it is about to go
> > into dormant
> > > > > mode,
> > > > >>>> it
> > > > >>>>> sends the WakingUp message when it comes out again.
> > > The WakingUp
> > > > >>>> message
> > > > >>>>> isn't needed for the MN to get mobility service,=20
> it is just
> > > there
> > > > >>> for
> > > > >>>
> > > > >>>>> optimizing the SA timeouts. This would require a
> > > special API on
> > > > > the
> > > > >>> HA
> > > > >>>
> > > > >>>>> between the MIP code and IKE code for the HA to
> > > extend the IPsec
> > > > > SA
> > > > >>>>> lifetime, similar to the one for IKEv1 mobility.
> > The solution
> > > > > would
> > > > >>>> only
> > > > >>>>> be
> > > > >>>>> applicable to Mobile IP.
> > > > >>>>>
> > > > >>>>> The other possibility is to do an IKEv2
> > INFORMATIONAL message
> > > > > that
> > > > >>> is
> > > > >>>
> > > > >>>> sent
> > > > >>>>> within the IKE SA. It works similarly, but there=20
> would be no
> > > need
> > > > >>> for
> > > > >>>
> > > > >>>> any
> > > > >>>>> API on the HA, since the IKE code itself would process it
> > > > > (actually,
> > > > >>> I
> > > > >>>
> > > > >>>>> proposed something like this to the Mobike WG but
> > they didn't
> > > see
> > > > >>> the
> > > > >>>
> > > > >>>> need
> > > > >>>>> for it). This would be applicable to both Mobike
> > and Mobile IP
> > > > > (and
> > > > >>>> any
> > > > >>>>> other security protocol that uses IKEv2, so maybe HIP
> > > as well).
> > > > >>>>>
> > > > >>>>> One question is, does the HA need to do anything else
> > > if the MN
> > > > > goes
> > > > >>>> into
> > > > >>>>> dormant mode? I think there are lots of things it could do
> > > > > (lengthen
> > > > >>>> the
> > > > >>>>> BU
> > > > >>>>> timeout, apply a filter that is either mobile
> > > specified or part
> > > > > of
> > > > >>> the
> > > > >>>
> > > > >>>>> user's service profile with the operator to only
> > > allow specific
> > > > >>>> traffic
> > > > >>>>> through, etc.) but I would really like to keep
> > things simple.
> > > > >>>>>
> > > > >>>>>             jak
> > > > >>>>>
> > > > >>>>> ----- Original Message -----
> > > > >>>>> From: "Vijay Devarapalli"=20
> <vijay.devarapalli@azairenet.com>
> > > > >>>>> To: "James Kempf" <kempf@docomolabs-usa.com>
> > > > >>>>> Cc: <mip6@ietf.org>
> > > > >>>>> Sent: Monday, July 17, 2006 3:43 PM
> > > > >>>>> Subject: Re: [Mip6] New Charter Item:Support for
> > Dormant Mode
> > > > > Alert
> > > > >>> to
> > > > >>>
> > > > >>>> HA?
> > > > >>>>>
> > > > >>>>>> the dormant mode extensions sounds good to me. we
> > > could do this
> > > > >>>>>> extension. one issue to consider - what triggers
> > > this message?
> > > > >>>>>> how does Mobile IP know the mobile node is going
> > > into a dormant
> > > > >>>>>> mode. if we have the trigger we should be okay.
> > > > >>>>>>
> > > > >>>>>> but we have to check if this was the issue. with=20
> IKEv1 you
> > > > >>>>>> could negotiate a lifetime for the IPsec SA.=20
> IKEv2 does not
> > > > >>>>>> have the IPsec SA lifetime feature. so keepalives
> > are needed.
> > > > >>>>>>
> > > > >>>>>> James Kempf wrote:
> > > > >>>>>>> I was at Wimax Forum last week and I think I now
> > understand
> > > > > why
> > > > >>>> they
> > > > >>>>> and
> > > > >>>>>>> 3GPP2 want to use RFC 4285 auth option rather than
> > > IPsec. One
> > > > >>> issue
> > > > >>>
> > > > >>>> -
> > > > >>>>>>> lack of EAP support for client auth - is solved
> > by IKEv2 and
> > > > > they
> > > > >>>> seem
> > > > >>>>> to
> > > > >>>>>>> now be moving in the direction of recommending
> > > IKEv2 if people
> > > > >>> want
> > > > >>>
> > > > >>>> to
> > > > >>>>>>> deploy IPsec.
> > > > >>>>>> yes this was one of the main issues.
> > > > >>>>>>
> > > > >>>>>> the way I saw it folks in 3GPP2 liked RFC 4285
> > because it is
> > > > >>>>>> very similar to the MIPv4 mechanism and they were
> > > comfortable
> > > > >>>>>> with it.
> > > > >>>>>>
> > > > >>>>>> Vijay
> > > > >>>>>>
> > > > >>>>>> But the other issue is a bit more complex. 802.16, like
> > > > >>>>>>> most cellular protocols, has extensive support=20
> for dormant
> > > > > mode,
> > > > >>>> and
> > > > >>>>>>> Wimax Forum is supporting dormant mode in their network
> > > > > design.
> > > > >>> If
> > > > >>>
> > > > >>>>> IPsec
> > > > >>>>>>> is used, then there is a risk when a mobile=20
> node goes into
> > > > >>> dormant
> > > > >>>
> > > > >>>> mode
> > > > >>>>>>> that the IPsec SA may time out. It is unfortunate
> > that this
> > > > > was
> > > > >>> not
> > > > >>>
> > > > >>>>>>> brought up when the discussion about RFC 4285 was
> > happening,
> > > > > but
> > > > >>> I
> > > > >>>
> > > > >>>>> think
> > > > >>>>>>> this might be something that the WG could work on
> > > now as part
> > > > > of
> > > > >>>> the
> > > > >>>>> new
> > > > >>>>>>> charter. This would make IKEv2/IPsec more=20
> attractive as a
> > > > >>> security
> > > > >>>
> > > > >>>>> option
> > > > >>>>>>> for cellular operators.
> > > > >>>>>>>
> > > > >>>>>>> Comments?
> > > > >>>>>>>
> > > > >>>>>>>            jak
> > > > >>>>>>>
> > > > >>>>>>>
> > > > >>>>>>>
> > > > >>>>>>> _______________________________________________
> > > > >>>>>>> Mip6 mailing list
> > > > >>>>>>> Mip6@ietf.org
> > > > >>>>>>> https://www1.ietf.org/mailman/listinfo/mip6
> > > > >>>>>>
> > > > >>>>>
> > > > >>>>>
> > > > >>>>> _______________________________________________
> > > > >>>>> Mip6 mailing list
> > > > >>>>> Mip6@ietf.org
> > > > >>>>> https://www1.ietf.org/mailman/listinfo/mip6
> > > > >>>>
> > > > >>>> "This email message and any attachments are confidential
> > > > > information
> > > > >>> of
> > > > >>>
> > > > >>>> Starent Networks, Corp. The information transmitted
> > may not be
> > > used
> > > > > to
> > > > >>>> create or change any contractual obligations of
> > > Starent Networks,
> > > > >>> Corp.
> > > > >>>
> > > > >>>> Any
> > > > >>>> review, retransmission, dissemination or other use of,
> > > or taking
> > > of
> > > > >>> any
> > > > >>>
> > > > >>>> action in reliance upon this e-mail and its attachments by
> > > persons
> > > > > or
> > > > >>>> entities other than the intended recipient is
> > > prohibited. If you
> > > > > are
> > > > >>> not
> > > > >>>
> > > > >>>> the
> > > > >>>> intended recipient, please notify the sender
> > immediately -- by
> > > > >>> replying to
> > > > >>>
> > > > >>>> this message or by sending an email to
> > > > > postmaster@starentnetworks.com
> > > > >>> --
> > > > >>>
> > > > >>>> and
> > > > >>>> destroy all copies of this message and any
> > attachments without
> > > > > reading
> > > > >>> or
> > > > >>>
> > > > >>>> disclosing their contents. Thank you."
> > > > >>>>
> > > > >>>>
> > > > >>>>
> > > > >>>> _______________________________________________
> > > > >>>> Mip6 mailing list
> > > > >>>> Mip6@ietf.org
> > > > >>>> https://www1.ietf.org/mailman/listinfo/mip6
> > > > >>>
> > > > >>>
> > > > >>>
> > > > >>> _______________________________________________
> > > > >>> Mip6 mailing list
> > > > >>> Mip6@ietf.org
> > > > >>> https://www1.ietf.org/mailman/listinfo/mip6
> > > > >
> > >
> > >
> > > _______________________________________________
> > > Mip6 mailing list
> > > Mip6@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/mip6
> > >
> >
> >
> >
> >
> >
> >
> >
>=20
>=20
>=20

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



From mip6-bounces@ietf.org Fri Jul 21 06:00:44 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G3roB-00009c-3Q; Fri, 21 Jul 2006 06:00:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G3ro9-00009O-Qp
	for mip6@ietf.org; Fri, 21 Jul 2006 06:00:33 -0400
Received: from m5-85.163.com ([202.108.5.85])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1G3rbz-0002T2-71
	for mip6@ietf.org; Fri, 21 Jul 2006 05:48:01 -0400
Received: from faint (unknown [218.249.29.11])
	by smtp14 (Coremail) with SMTP id wKjRD0WAjwKNosBEA1dvAg==.55465S2;
	Fri, 21 Jul 2006 17:46:54 +0800 (CST)
Date: Fri, 21 Jul 2006 17:47:38 +0800
From: "Tony" <guanjian8632@163.com>
To: "mip6" <mip6@ietf.org>
Organization: Beijing JiaoTong University IP lab
X-mailer: Foxmail 5.0 [cn]
Mime-Version: 1.0
Message-Id: <44C0A28E.044978.32690>
X-Spam-Score: 3.0 (+++)
X-Scan-Signature: 08e48e05374109708c00c6208b534009
Subject: [Mip6] Does somebody implement mobile IP multicast in router?
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: guanjian8632@163.com
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1308849739=="
Errors-To: mip6-bounces@ietf.org

--===============1308849739==
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: base64


SGl+DQoJVGhlcmUgaXMgbG90cyBvZiBtb2JpbGUgbXVsdGljYXN0IHNjaGVtZXMgcHJvcG9zZWQs
IGJ1dCBsaXR0bGUgaW1wbGVtZW50IGV4Y2VwdCBzaW11bGF0aW9uLg0KRG9lcyBzb21lYm9keSBp
bXBsZW1lbnQgbW9iaWxlIElQIG11bHRpY2FzdCBpbiByb3V0ZXI/DQoNCg0KICChoaGhoaGhoaGh
oaGhoVRvbnkNCqGhoaGhoaGhoaGhoaGhoaFndWFuamlhbjg2MzJAMTYzLmNvbQ0KoaGhoaGhoaGh
oaGhoaGhoaGhoaEyMDA2LTA3LTIxDQo=




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

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

--===============1308849739==--



From mip6-bounces@ietf.org Fri Jul 21 09:27:17 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G3v25-0000mQ-Br; Fri, 21 Jul 2006 09:27:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G3v23-0000m3-Mb
	for mip6@ietf.org; Fri, 21 Jul 2006 09:27:07 -0400
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G3v22-0004Wz-Es
	for mip6@ietf.org; Fri, 21 Jul 2006 09:27:07 -0400
Received: from il06exr01.mot.com (il06exr01.mot.com [129.188.137.131])
	by motgate8.mot.com (8.12.11/Motorola) with ESMTP id k6LDR2b1003399;
	Fri, 21 Jul 2006 06:27:02 -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 k6LDR162019770;
	Fri, 21 Jul 2006 08:27:02 -0500 (CDT)
Message-ID: <44C0D624.1040808@motorola.com>
Date: Fri, 21 Jul 2006 15:27:00 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: guanjian8632@163.com
Subject: Re: [Mip6] Does somebody implement mobile IP multicast in router?
References: <44C0A28E.044978.32690>
In-Reply-To: <44C0A28E.044978.32690>
Content-Type: text/plain; charset=GB2312
X-Brightmail-Tracker: AAAAAQAAAAQ=
X-White-List-Member: TRUE
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by motgate8.mot.com id
	k6LDR2b1003399
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Cc: mip6 <mip6@ietf.org>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Tony wrote:
> Hi~ There is lots of mobile multicast schemes proposed, but little
> implement except simulation. Does somebody implement mobile IP
> multicast in router?

I think yes.

What "multicast" do you mean?

MLDv2?  PIM-SM?

Alex

>=20
>=20
> =A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1Tony =A1=A1=A1=A1=A1=A1=A1=A1=
=A1=A1=A1=A1=A1=A1=A1=A1guanjian8632@163.com =A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=
=A1=A1=A1=A1=A1=A1=A1=A1=A1=A12006-07-21
>=20
>=20
> -----------------------------------------------------------------------=
-
>=20
>=20
> _______________________________________________ Mip6 mailing list=20
> Mip6@ietf.org https://www1.ietf.org/mailman/listinfo/mip6


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



From mip6-bounces@ietf.org Fri Jul 21 10:24:01 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G3vv6-000271-0x; Fri, 21 Jul 2006 10:24:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G3vv4-00026j-Gt
	for mip6@ietf.org; Fri, 21 Jul 2006 10:23:58 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G3vv4-00008a-FN
	for mip6@ietf.org; Fri, 21 Jul 2006 10:23:58 -0400
Received: from zcars04f.nortel.com ([47.129.242.57])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1G3vjF-00084D-5X
	for mip6@ietf.org; Fri, 21 Jul 2006 10:11:46 -0400
Received: from zrc2hxm2.corp.nortel.com (zrc2hxm2.corp.nortel.com
	[47.103.123.73])
	by zcars04f.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	k6LEBHv29049; Fri, 21 Jul 2006 10:11:18 -0400 (EDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: SDO needs (was RE: [Mip6] New Charter Item:Support for Dormant
	Mode	Alert to HA?)
Date: Fri, 21 Jul 2006 09:11:16 -0500
Message-ID: <62B9B0847CC47543B6B3B5E26BD268E60B5F642A@zrc2hxm2.corp.nortel.com>
In-Reply-To: <0MKp2t-1G3iPI2kcA-000411@mrelay.perfora.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: SDO needs (was RE: [Mip6] New Charter Item:Support for Dormant
	Mode	Alert to HA?)
thread-index: AcasGGPJbL2evV7hSaa2mIco75XgnAAO/lYgAB7BY/A=
From: "Mohamed Khalil" <mkhalil@nortel.com>
To: "Alper Yegin" <alper.yegin@yegin.org>,
	"James Kempf" <kempf@docomolabs-usa.com>,
	"Narayanan, Vidya" <vidyan@qualcomm.com>,
	"Tsirtsis, George" <tsirtsis@qualcomm.com>,
	"Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
X-Spam-Score: -2.6 (--)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org



 I am not aware of any collective and official discussion around this
subject to be conveyed to IETF.

This is the same feedback I got from people involved in the WiMax
activities.

Alper






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

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



From mip6-bounces@ietf.org Sun Jul 23 09:35:06 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G4e6e-0005bF-RE; Sun, 23 Jul 2006 09:34:52 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G48w3-0004lj-3I
	for mip6@ietf.org; Sat, 22 Jul 2006 00:17:51 -0400
Received: from ug-out-1314.google.com ([66.249.92.174])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G48w0-0005yE-NB
	for mip6@ietf.org; Sat, 22 Jul 2006 00:17:51 -0400
Received: by ug-out-1314.google.com with SMTP id m2so1626294uge
	for <mip6@ietf.org>; Fri, 21 Jul 2006 21:17:47 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references;
	b=SUO19uv9FTA/oqnmkr/oYuRAPK4lcW72mARKJLXdF2qyMlYBLhtAj+JzpqNo9LsdoOCa4MpuGrt5yYFgN6+V90ohhWQAOkIiNfkh42rdq4TT4ObvgJoJylf4lGgTN0qhxKgXTJSqVLoGOovN6vI2KauWwj5TEoeqrR7DxiBQA6M=
Received: by 10.78.177.3 with SMTP id z3mr698389hue;
	Fri, 21 Jul 2006 21:17:47 -0700 (PDT)
Received: by 10.78.67.5 with HTTP; Fri, 21 Jul 2006 21:17:47 -0700 (PDT)
Message-ID: <c46ad13f0607212117h330f33e3jca72298aafda6f8e@mail.gmail.com>
Date: Fri, 21 Jul 2006 21:17:47 -0700
From: "Anurag Uxa" <uxaanurag@gmail.com>
To: "Alexandru Petrescu" <alexandru.petrescu@motorola.com>
Subject: Re: [Mip6] Does somebody implement mobile IP multicast in router?
In-Reply-To: <44C0D624.1040808@motorola.com>
MIME-Version: 1.0
References: <44C0D624.1040808@motorola.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36
X-Mailman-Approved-At: Sun, 23 Jul 2006 09:34:50 -0400
Cc: mip6 <mip6@ietf.org>, guanjian8632@163.com
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0137154303=="
Errors-To: mip6-bounces@ietf.org

--===============0137154303==
Content-Type: multipart/alternative; 
	boundary="----=_Part_128273_28624360.1153541867288"

------=_Part_128273_28624360.1153541867288
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi Alex,

Yes we have implemented the multicast forwarding at router and integrated
with pim-sm. we do support to mldv1 & v2 at host side in ipv6 stack. Top of
this we have mipv6 running.

Regards
Anurag.


On 7/21/06, Alexandru Petrescu <alexandru.petrescu@motorola.com> wrote:
>
> Tony wrote:
> > Hi~ There is lots of mobile multicast schemes proposed, but little
> > implement except simulation. Does somebody implement mobile IP
> > multicast in router?
>
> I think yes.
>
> What "multicast" do you mean?
>
> MLDv2?  PIM-SM?
>
> Alex
>
> >
> >
> > Tony guanjian8632@163.com 2006-07-21
> >
> >
> > ------------------------------------------------------------------------
> >
> >
> > _______________________________________________ Mip6 mailing list
> > Mip6@ietf.org https://www1.ietf.org/mailman/listinfo/mip6
>
>
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
>
> ______________________________________________________________________
>
> ______________________________________________________________________
> This email has been scanned by the MessageLabs Email Security System.
> For more information please visit http://www.messagelabs.com/email
> ______________________________________________________________________
>

------=_Part_128273_28624360.1153541867288
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<div>Hi Alex,</div>
<div>&nbsp;</div>
<div>Yes we have implemented the mulFrom mip6-bounces@ietf.org Sun Jul 23 09:35:06 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G4e6e-0005bF-RE; Sun, 23 Jul 2006 09:34:52 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G48w3-0004lj-3I
	for mip6@ietf.org; Sat, 22 Jul 2006 00:17:51 -0400
Received: from ug-out-1314.google.com ([66.249.92.174])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G48w0-0005yE-NB
	for mip6@ietf.org; Sat, 22 Jul 2006 00:17:51 -0400
Received: by ug-out-1314.google.com with SMTP id m2so1626294uge
	for <mip6@ietf.org>; Fri, 21 Jul 2006 21:17:47 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references;
	b=SUO19uv9FTA/oqnmkr/oYuRAPK4lcW72mARKJLXdF2qyMlYBLhtAj+JzpqNo9LsdoOCa4MpuGrt5yYFgN6+V90ohhWQAOkIiNfkh42rdq4TT4ObvgJoJylf4lGgTN0qhxKgXTJSqVLoGOovN6vI2KauWwj5TEoeqrR7DxiBQA6M=
Received: by 10.78.177.3 with SMTP id z3mr698389hue;
	Fri, 21 Jul 2006 21:17:47 -0700 (PDT)
Received: by 10.78.67.5 with HTTP; Fri, 21 Jul 2006 21:17:47 -0700 (PDT)
Message-ID: <c46ad13f0607212117h330f33e3jca72298aafda6f8e@mail.gmail.com>
Date: Fri, 21 Jul 2006 21:17:47 -0700
From: "Anurag Uxa" <uxaanurag@gmail.com>
To: "Alexandru Petrescu" <alexandru.petrescu@motorola.com>
Subject: Re: [Mip6] Does somebody implement mobile IP multicast in router?
In-Reply-To: <44C0D624.1040808@motorola.com>
MIME-Version: 1.0
References: <44C0D624.1040808@motorola.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36
X-Mailman-Approved-At: Sun, 23 Jul 2006 09:34:50 -0400
Cc: mip6 <mip6@ietf.org>, guanjian8632@163.com
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0137154303=="
Errors-To: mip6-bounces@ietf.org

--===============0137154303==
Content-Type: multipart/alternative; 
	boundary="----=_Part_128273_28624360.1153541867288"

------=_Part_128273_28624360.1153541867288
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi Alex,

Yes we have implemented the multicast forwarding at router and integrated
with pim-sm. we do support to mldv1 & v2 at host side in ipv6 stack. Top of
this we have mipv6 running.

Regards
Anurag.


On 7/21/06, Alexandru Petrescu <alexandru.petrescu@motorola.com> wrote:
>
> Tony wrote:
> > Hi~ There is lots of mobile multicast schemes proposed, but little
> > implement except simulation. Does somebody implement mobile IP
> > multicast in router?
>
> I think yes.
>
> What "multicast" do you mean?
>
> MLDv2?  PIM-SM?
>
> Alex
>
> >
> >
> > Tony guanjian8632@163.com 2006-07-21
> >
> >
> > ------------------------------------------------------------------------
> >
> >
> > _______________________________________________ Mip6 mailing list
> > Mip6@ietf.org https://www1.ietf.org/mailman/listinfo/mip6
>
>
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
>
> ______________________________________________________________________
>
> ______________________________________________________________________
> This email has been scanned by the MessageLabs Email Security System.
> For more information please visit http://www.messagelabs.com/email
> ______________________________________________________________________
>

------=_Part_128273_28624360.1153541867288
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<div>Hi Alex,</div>
<div>&nbsp;</div>
<div>Yes we have implemented the multicast forwarding at router and integrated with pim-sm. we do support to mldv1 &amp; v2 at host side in ipv6 stack. Top of this we have mipv6 running.</div>
<div>&nbsp;</div>
<div>Regards</div>
<div>Anurag.<br><br>&nbsp;</div>
<div><span class="gmail_quote">On 7/21/06, <b class="gmail_sendername">Alexandru Petrescu</b> &lt;<a href="mailto:alexandru.petrescu@motorola.com">alexandru.petrescu@motorola.com</a>&gt; wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Tony wrote:<br>&gt; Hi~ There is lots of mobile multicast schemes proposed, but little<br>&gt; implement except simulation. Does somebody implement mobile IP
<br>&gt; multicast in router?<br><br>I think yes.<br><br>What &quot;multicast&quot; do you mean?<br><br>MLDv2?&nbsp;&nbsp;PIM-SM?<br><br>Alex<br><br>&gt;<br>&gt;<br>&gt; Tony <a href="mailto:guanjian8632@163.com">guanjian8632@163.com
</a> 2006-07-21<br>&gt;<br>&gt;<br>&gt; ------------------------------------------------------------------------<br>&gt;<br>&gt;<br>&gt; _______________________________________________ Mip6 mailing list<br>&gt; <a href="mailto:Mip6@ietf.org">
Mip6@ietf.org</a> <a href="https://www1.ietf.org/mailman/listinfo/mip6">https://www1.ietf.org/mailman/listinfo/mip6</a><br><br><br>_______________________________________________<br>Mip6 mailing list<br><a href="mailto:Mip6@ietf.org">
Mip6@ietf.org</a><br><a href="https://www1.ietf.org/mailman/listinfo/mip6">https://www1.ietf.org/mailman/listinfo/mip6</a><br><br>______________________________________________________________________<br><br>______________________________________________________________________
<br>This email has been scanned by the MessageLabs Email Security System.<br>For more information please visit <a href="http://www.messagelabs.com/email">http://www.messagelabs.com/email</a><br>______________________________________________________________________
<br></blockquote></div><br>

------=_Part_128273_28624360.1153541867288--


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

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

--===============0137154303==--




From mip6-bounces@ietf.org Sun Jul 23 09:35:06 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G4e6f-0005bK-4g; Sun, 23 Jul 2006 09:34:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G4Px0-0002or-Kw
	for mip6@ietf.org; Sat, 22 Jul 2006 18:27:58 -0400
Received: from dash.ece.ufl.edu ([128.227.220.23] helo=ece.ufl.edu)
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1G4Px0-0005WH-5w
	for mip6@ietf.org; Sat, 22 Jul 2006 18:27:58 -0400
Received: (qmail 60128 invoked by uid 0); 22 Jul 2006 22:16:30 -0000
Received: from 207.46.89.16 by dash.ece.ufl.edu (envelope-from
	<wu@ece.ufl.edu>, uid 0) with qmail-scanner-1.25 
	(uvscan: v4.40.0/vJul 22 05:46.  
	Clear:RC:0(207.46.89.16):SA:0(0.1/5.0):. 
	Processed in 1.249421 secs); 22 Jul 2006 22:16:30 -0000
X-Spam-Status: No, hits=0.1 required=5.0
Received: from unknown (HELO mars) (207.46.89.16)
	by dot.ece.ufl.edu with SMTP; 22 Jul 2006 22:16:29 -0000
Message-ID: <00d401c6adde$0019e5c0$eea417ac@mars>
From: "Dr. Dapeng Oliver Wu" <wu@ece.ufl.edu>
To: <mip6@ietf.org>
Date: Sat, 22 Jul 2006 18:27:19 -0400
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.2869
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 2ed806e2f53ff1a061ad4f97e00345ac
X-Mailman-Approved-At: Sun, 23 Jul 2006 09:34:50 -0400
Subject: [Mip6] INFOCOM 2007 CFP: Paper registration deadline on July 24,
	2006  and clarification on INFOCOM mini-conferences 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailmanticast forwarding at router and integrated with pim-sm. we do support to mldv1 &amp; v2 at host side in ipv6 stack. Top of this we have mipv6 running.</div>
<div>&nbsp;</div>
<div>Regards</div>
<div>Anurag.<br><br>&nbsp;</div>
<div><span class="gmail_quote">On 7/21/06, <b class="gmail_sendername">Alexandru Petrescu</b> &lt;<a href="mailto:alexandru.petrescu@motorola.com">alexandru.petrescu@motorola.com</a>&gt; wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Tony wrote:<br>&gt; Hi~ There is lots of mobile multicast schemes proposed, but little<br>&gt; implement except simulation. Does somebody implement mobile IP
<br>&gt; multicast in router?<br><br>I think yes.<br><br>What &quot;multicast&quot; do you mean?<br><br>MLDv2?&nbsp;&nbsp;PIM-SM?<br><br>Alex<br><br>&gt;<br>&gt;<br>&gt; Tony <a href="mailto:guanjian8632@163.com">guanjian8632@163.com
</a> 2006-07-21<br>&gt;<br>&gt;<br>&gt; ------------------------------------------------------------------------<br>&gt;<br>&gt;<br>&gt; _______________________________________________ Mip6 mailing list<br>&gt; <a href="mailto:Mip6@ietf.org">
Mip6@ietf.org</a> <a href="https://www1.ietf.org/mailman/listinfo/mip6">https://www1.ietf.org/mailman/listinfo/mip6</a><br><br><br>_______________________________________________<br>Mip6 mailing list<br><a href="mailto:Mip6@ietf.org">
Mip6@ietf.org</a><br><a href="https://www1.ietf.org/mailman/listinfo/mip6">https://www1.ietf.org/mailman/listinfo/mip6</a><br><br>______________________________________________________________________<br><br>______________________________________________________________________
<br>This email has been scanned by the MessageLabs Email Security System.<br>For more information please visit <a href="http://www.messagelabs.com/email">http://www.messagelabs.com/email</a><br>______________________________________________________________________
<br></blockquote></div><br>

------=_Part_128273_28624360.1153541867288--


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

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

--===============0137154303==--




From mip6-bounces@ietf.org Sun Jul 23 09:35:06 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G4e6f-0005bK-4g; Sun, 23 Jul 2006 09:34:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G4Px0-0002or-Kw
	for mip6@ietf.org; Sat, 22 Jul 2006 18:27:58 -0400
Received: from dash.ece.ufl.edu ([128.227.220.23] helo=ece.ufl.edu)
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1G4Px0-0005WH-5w
	for mip6@ietf.org; Sat, 22 Jul 2006 18:27:58 -0400
Received: (qmail 60128 invoked by uid 0); 22 Jul 2006 22:16:30 -0000
Received: from 207.46.89.16 by dash.ece.ufl.edu (envelope-from
	<wu@ece.ufl.edu>, uid 0) with qmail-scanner-1.25 
	(uvscan: v4.40.0/vJul 22 05:46.  
	Clear:RC:0(207.46.89.16):SA:0(0.1/5.0):. 
	Processed in 1.249421 secs); 22 Jul 2006 22:16:30 -0000
X-Spam-Status: No, hits=0.1 required=5.0
Received: from unknown (HELO mars) (207.46.89.16)
	by dot.ece.ufl.edu with SMTP; 22 Jul 2006 22:16:29 -0000
Message-ID: <00d401c6adde$0019e5c0$eea417ac@mars>
From: "Dr. Dapeng Oliver Wu" <wu@ece.ufl.edu>
To: <mip6@ietf.org>
Date: Sat, 22 Jul 2006 18:27:19 -0400
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.2869
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 2ed806e2f53ff1a061ad4f97e00345ac
X-Mailman-Approved-At: Sun, 23 Jul 2006 09:34:50 -0400
Subject: [Mip6] INFOCOM 2007 CFP: Paper registration deadline on July 24,
	2006  and clarification on INFOCOM mini-conferences 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1700130177=="
Errors-To: mip6-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1700130177==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_00D1_01C6ADBC.778A3140"

This is a multi-part message in MIME format.

------=_NextPart_000_00D1_01C6ADBC.778A3140
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


[Please accept our apologies if you receive multiple copies of this =
message.]=20

=20
INFOCOM 2007 will be held in Anchorage, Alaska, on May 6-12, 2007. The=20
deadline for paper submissions is 5 pm EST, August 1, 2006. However,=20
papers MUST be registered in EDAS by July 24, 2006. Please note the=20
following changes to the submission process this year:

(i) Each paper submission is limited to 9 pages.
(ii) Upon submission in EDAS, authors will be asked to indicate whether=20
they wish an abbreviated version (5 pages) of their paper to be=20
considered for inclusion in special-topics INFOCOM mini-conferences in=20
the event that the paper cannot be included in the main conference =
program.


The following is a brief explanation about the Infocom Mini-Conference =
process.

All submitted papers will be considered as regular papers submissions
for Infocom.  AFTER the infocom selection is done, papers that did
not make it into Infocom will be considered for topical
mini-conference to be held on the Friday immediately following
Infocom.  Hence, the mini-conference can be viewed as an opportunity
to get your work published fast even if you did not get your paper
accepted into Infocom.

The following are answers to frequently asked questions about the
mini-conferences:

1)   In order to have your paper considered for the Mini-conference,
you must indicate when registering your paper that you want your
paper to be considered for the mini-conference.

2) Selecting that your paper should be considered for mini-conference
will not affect the chances of your paper being accepted to Infocom.
Reviewers and TPC members will not know about your choice when they
make a decision about your paper for Infocom.

3) The topics of the mini-conference will only be determined after
the Infocom selection process has been completed.

4)  Papers will be considered for the mini-conferences by a subset of
the Infocom TPC from the pool of papers that did not make it into
Infocom (whose authors indicated that they want their paper
considered for the mini-conference).

The website of INFOCOM 2007 is =
http://www.comsoc.org/confs/infocom/2007/.

------=_NextPart_000_00D1_01C6ADBC.778A3140
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns:o =3D "urn:schemas-microsoft-com:office:office"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.2912" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>
<DIV><FONT face=3DArial size=3D2><SPAN lang=3DEN-US style=3D"FONT-SIZE: =
10pt"><o:p><SPAN=20
lang=3DEN-US style=3D"FONT-SIZE: 10pt"><SPAN style=3D"mso-spacerun: =
yes"></SPAN><o:p>
<DIV><FONT face=3DArial size=3D2><FONT face=3D"Times New Roman" =
size=3D3>[Please accept=20
our apologies if you receive multiple copies of this message.]=20
</FONT></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><FONT face=3D"Times New Roman" =
size=3D3></FONT><FONT=20
face=3D"Times New Roman" size=3D3></FONT><BR>&nbsp;</DIV></FONT>
<DIV>INFOCOM 2007 will be held in Anchorage, Alaska, on May 6-12, 2007. =
The=20
<BR>deadline for paper submissions is 5 pm EST, August 1, 2006. However, =

<BR>papers MUST be registered in E/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1700130177=="
Errors-To: mip6-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1700130177==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_00D1_01C6ADBC.778A3140"

This is a multi-part message in MIME format.

------=_NextPart_000_00D1_01C6ADBC.778A3140
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


[Please accept our apologies if you receive multiple copies of this =
message.]=20

=20
INFOCOM 2007 will be held in Anchorage, Alaska, on May 6-12, 2007. The=20
deadline for paper submissions is 5 pm EST, August 1, 2006. However,=20
papers MUST be registered in EDAS by July 24, 2006. Please note the=20
following changes to the submission process this year:

(i) Each paper submission is limited to 9 pages.
(ii) Upon submission in EDAS, authors will be asked to indicate whether=20
they wish an abbreviated version (5 pages) of their paper to be=20
considered for inclusion in special-topics INFOCOM mini-conferences in=20
the event that the paper cannot be included in the main conference =
program.


The following is a brief explanation about the Infocom Mini-Conference =
process.

All submitted papers will be considered as regular papers submissions
for Infocom.  AFTER the infocom selection is done, papers that did
not make it into Infocom will be considered for topical
mini-conference to be held on the Friday immediately following
Infocom.  Hence, the mini-conference can be viewed as an opportunity
to get your work published fast even if you did not get your paper
accepted into Infocom.

The following are answers to frequently asked questions about the
mini-conferences:

1)   In order to have your paper considered for the Mini-conference,
you must indicate when registering your paper that you want your
paper to be considered for the mini-conference.

2) Selecting that your paper should be considered for mini-conference
will not affect the chances of your paper being accepted to Infocom.
Reviewers and TPC members will not know about your choice when they
make a decision about your paper for Infocom.

3) The topics of the mini-conference will only be determined after
the Infocom selection process has been completed.

4)  Papers will be considered for the mini-conferences by a subset of
the Infocom TPC from the pool of papers that did not make it into
Infocom (whose authors indicated that they want their paper
considered for the mini-conference).

The website of INFOCOM 2007 is =
http://www.comsoc.org/confs/infocom/2007/.

------=_NextPart_000_00D1_01C6ADBC.778A3140
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns:o =3D "urn:schemas-microsoft-com:office:office"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.2912" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>
<DIV><FONT face=3DArial size=3D2><SPAN lang=3DEN-US style=3D"FONT-SIZE: =
10pt"><o:p><SPAN=20
lang=3DEN-US style=3D"FONT-SIZE: 10pt"><SPAN style=3D"mso-spacerun: =
yes"></SPAN><o:p>
<DIV><FONT face=3DArial size=3D2><FONT face=3D"Times New Roman" =
size=3D3>[Please accept=20
our apologies if you receive multiple copies of this message.]=20
</FONT></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><FONT face=3D"Times New Roman" =
size=3D3></FONT><FONT=20
face=3D"Times New Roman" size=3D3></FONT><BR>&nbsp;</DIV></FONT>
<DIV>INFOCOM 2007 will be held in Anchorage, Alaska, on May 6-12, 2007. =
The=20
<BR>deadline for paper submissions is 5 pm EST, August 1, 2006. However, =

<BR>papers MUST be registered in EDAS by July 24, 2006. Please note the=20
<BR>following changes to the submission process this year:<BR><BR>(i) =
Each paper=20
submission is limited to 9 pages.<BR>(ii) Upon submission in EDAS, =
authors will=20
be asked to indicate whether <BR>they wish an abbreviated version (5 =
pages) of=20
their paper to be <BR>considered for inclusion in special-topics INFOCOM =

mini-conferences in <BR>the event that the paper cannot be included in =
the main=20
conference program.<BR><BR><BR>The following is a brief explanation =
about the=20
Infocom Mini-Conference process.<BR><BR>All submitted papers will be =
considered=20
as regular papers submissions<BR>for Infocom. &nbsp;AFTER the infocom =
selection=20
is done, papers that did<BR>not make it into Infocom will be considered =
for=20
topical<BR>mini-conference to be held on the Friday immediately=20
following<BR>Infocom. &nbsp;Hence, the mini-conference can be viewed as =
an=20
opportunity<BR>to get your work published fast even if you did not get =
your=20
paper<BR>accepted into Infocom.<BR><BR>The following are answers to =
frequently=20
asked questions about the<BR>mini-conferences:<BR><BR>1) &nbsp; In order =
to have=20
your paper considered for the Mini-conference,<BR>you must indicate when =

registering your paper that you want your<BR>paper to be considered for =
the=20
mini-conference.<BR><BR>2) Selecting that your paper should be =
considered for=20
mini-conference<BR>will not affect the chances of your paper being =
accepted to=20
Infocom.<BR>Reviewers and TPC members will not know about your choice =
when=20
they<BR>make a decision about your paper for Infocom.<BR><BR>3) The =
topics of=20
the mini-conference will only be determined after<BR>the Infocom =
selection=20
process has been completed.<BR><BR>4) &nbsp;Papers will be considered =
for the=20
mini-conferences by a subset of<BR>the Infocom TPC from the pool of =
papers that=20
did not make it into<BR>Infocom (whose authors indicated that they want =
their=20
paper<BR>considered for the=20
mini-conference).<BR></DIV></o:p></SPAN></DIV></o:p></SPAN></FONT></FONT>=
</DIV>
<DIV><FONT face=3DArial size=3D2>The website of INFOCOM 2007 is&nbsp;<A=20
href=3D"http://www.comsoc.org/confs/infocom/2007/">http://www.comsoc.org/=
confs/infocom/2007/</A>.<BR></FONT></DIV></BODY></HTML>

------=_NextPart_000_00D1_01C6ADBC.778A3140--



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

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

--===============1700130177==--





DAS by July 24, 2006. Please note the=20
<BR>following changes to the submission process this year:<BR><BR>(i) =
Each paper=20
submission is limited to 9 pages.<BR>(ii) Upon submission in EDAS, =
authors will=20
be asked to indicate whether <BR>they wish an abbreviated version (5 =
pages) of=20
their paper to be <BR>considered for inclusion in special-topics INFOCOM =

mini-conferences in <BR>the event that the paper cannot be included in =
the main=20
conference program.<BR><BR><BR>The following is a brief explanation =
about the=20
Infocom Mini-Conference process.<BR><BR>All submitted papers will be =
considered=20
as regular papers submissions<BR>for Infocom. &nbsp;AFTER the infocom =
selection=20
is done, papers that did<BR>not make it into Infocom will be considered =
for=20
topical<BR>mini-conference to be held on the Friday immediately=20
following<BR>Infocom. &nbsp;Hence, the mini-conference can be viewed as =
an=20
opportunity<BR>to get your work published fast even if you did not get =
your=20
paper<BR>accepted into Infocom.<BR><BR>The following are answers to =
frequently=20
asked questions about the<BR>mini-conferences:<BR><BR>1) &nbsp; In order =
to have=20
your paper considered for the Mini-conference,<BR>you must indicate when =

registering your paper that you want your<BR>paper to be considered for =
the=20
mini-conference.<BR><BR>2) Selecting that your paper should be =
considered for=20
mini-conference<BR>will not affect the chances of your paper being =
accepted to=20
Infocom.<BR>Reviewers and TPC members will not know about your choice =
when=20
they<BR>make a decision about your paper for Infocom.<BR><BR>3) The =
topics of=20
the mini-conference will only be determined after<BR>the Infocom =
selection=20
process has been completed.<BR><BR>4) &nbsp;Papers will be considered =
for the=20
mini-conferences by a subset of<BR>the Infocom TPC from the pool of =
papers that=20
did not make it into<BR>Infocom (whose authors indicated that they want =
their=20
paper<BR>considered for the=20
mini-conference).<BR></DIV></o:p></SPAN></DIV></o:p></SPAN></FONT></FONT>=
</DIV>
<DIV><FONT face=3DArial size=3D2>The website of INFOCOM 2007 is&nbsp;<A=20
href=3D"http://www.comsoc.org/confs/infocom/2007/">http://www.comsoc.org/=
confs/infocom/2007/</A>.<BR></FONT></DIV></BODY></HTML>

------=_NextPart_000_00D1_01C6ADBC.778A3140--



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

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

--===============1700130177==--





From mip6-bounces@ietf.org Sun Jul 23 13:19:50 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G4hcD-0006Ky-At; Sun, 23 Jul 2006 13:19:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G4hcB-0006Kt-Ke
	for mip6@ietf.org; Sun, 23 Jul 2006 13:19:39 -0400
Received: from web60323.mail.yahoo.com ([209.73.178.131])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1G4hcA-0000xZ-9Q
	for mip6@ietf.org; Sun, 23 Jul 2006 13:19:39 -0400
Received: (qmail 45433 invoked by uid 60001); 23 Jul 2006 17:19:23 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=Message-ID:Received:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type;
	b=tYPuWEYfSgV2pm4f+zCG3fSwpuYshF0cP8/URRiHw0qnwcSfI2Bzl9e06uv2VKDwWmvVYhb2BaUspozYmlzpqFqDNaZNb9sWN9ifIvhdiCbmLHJS+p/b521KEx5SAu8Y0vCMDqQtDYqeRA74Is19BhuMQG5wFpyQo4HePo+6xUg=
	; 
Message-ID: <20060723171923.45431.qmail@web60323.mail.yahoo.com>
Received: from [67.166.240.5] by web60323.mail.yahoo.com via HTTP;
	Sun, 23 Jul 2006 10:19:23 PDT
Date: Sun, 23 Jul 2006 10:19:23 -0700 (PDT)
From: Behcet Sarikaya <behcetsarikaya@yahoo.com>
Subject: Re: SDO needs (was RE: [Mip6] New Charter Item:Support for Dormant
	Mode Alert to HA?)
To: Alper Yegin <alper.yegin@yegin.org>,
	James Kempf <kempf@docomolabs-usa.com>,
	"Narayanan, Vidya" <vidyan@qualcomm.com>,
	"Tsirtsis, George" <tsirtsis@qualcomm.com>,
	Vijay Devarapalli <vijay.devarapalli@azairenet.com>
In-Reply-To: <0MKp2t-1G3iPI2kcA-000411@mrelay.perfora.net>
MIME-Version: 1.0
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Behcet Sarikaya <sarikaya@ieee.org>
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0797330732=="
Errors-To: mip6-bounces@ietf.org

--===============0797330732==
Content-Type: multipart/alternative; boundary="0-1603189681-1153675163=:44894"

--0-1603189681-1153675163=:44894
Content-Type: text/plain; charset=us-ascii

I agree with this. Whatever has been discussed so far do not seem to require any major protocol work, the solutions are in specific ways of using already defined protocols and probably this could be done in SDOs, we have so many good experts in SDOs.
What could be done in IETF is something like pana is doing but for dormant mode signaling. 

Regards,

--behcet

----- Original Message ----
From: Alper Yegin <alper.yegin@yegin.org>
To: James Kempf <kempf@docomolabs-usa.com>; "Narayanan, Vidya" <vidyan@qualcomm.com>; "Tsirtsis, George" <tsirtsis@qualcomm.com>; Vijay Devarapalli <vijay.devarapalli@azairenet.com>
Cc: mip6@ietf.org
Sent: Thursday, July 20, 2006 6:58:13 PM
Subject: SDO needs (was RE: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?)

> Your point about 3GPP2 needing EAP support is also a concern to Wimax
> Forum,
> as I mentioned in the original email that started this thread, but, in
> addition, I was hearing that they were concerned about IPsec SA timeout
> during dormant mode. I sent email to the Wimax Forum list, and Raj
> confirmed
> that this was, indeed, a concern.

I think this can only be reported as "the opinion of one WiMAX Forum
member", as opposed to the collective and official view of the WiMAX Forum.
I think we should be careful about how to carry and use information between
IETF and other SDOs. In this particular instance, I'm saying this as not
only a member of this IETF community, but also as a WiMAX Forum NWG Security
lead and also someone involved with forming a liaison between the two
organizations. I am not aware of any collective and official discussion
around this subject to be conveyed to IETF.

Alper






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





--0-1603189681-1153675163=:44894
Content-Type: text/html; charset=us-ascii

<html><head><style type="text/css"><!-- DIV {margin:0px} --></style></head><body><div style="font-family:courier, monaco, monospace, sans-serif;font-size:12pt"><div style="font-family: courier,monaco,monospace,sans-serif; font-size: 12pt;">I agree with this. Whatever has been discussed so far do not seem to require any major protocol work, the solutions are in specific ways of using already defined protocols and probably this could be done in SDOs, we have so many good experts in SDOs.<br>What could be done in IETF is something like pana is doing but for dormant mode signaling. <br><br>Regards,<br><br>--behcet<br><br><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;">----- Original Message ----<br>From: Alper Yegin &lt;alper.yegin@yegin.org&gt;<br>To: James Kempf &lt;kempf@docomolabs-usa.com&gt;; "Narayanan, Vidya" &lt;vidyan@qualcomm.com&gt;; "Tsirtsis, George" &lt;tsirtsis@qualcomm.com&gt;; Vijay Devarapalli
 &lt;vijay.devarapalli@azairenet.com&gt;<br>Cc: mip6@ietf.org<br>Sent: Thursday, July 20, 2006 6:58:13 PM<br>Subject: SDO needs (was RE: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?)<br><br><div>&gt; Your point about 3GPP2 needing EAP support is also a concern to Wimax<br>&gt; Forum,<br>&gt; as I mentioned in the original email that started this thread, but, in<br>&gt; addition, I was hearing that they were concerned about IPsec SA timeout<br>&gt; during dormant mode. I sent email to the Wimax Forum list, and Raj<br>&gt; confirmed<br>&gt; that this was, indeed, a concern.<br><br>I think this can only be reported as "the opinion of one WiMAX Forum<br>member", as opposed to the collective and official view of the WiMAX Forum.<br>I think we should be careful about how to carry and use information between<br>IETF and other SDOs. In this particular instance, I'm saying this as not<br>only a member of this IETF community, but also as a WiMAX Forum NWG
 Security<br>lead and also someone involved with forming a liaison between the two<br>organizations. I am not aware of any collective and official discussion<br>around this subject to be conveyed to IETF.<br><br>Alper<br><br><br><br><br><br><br>_______________________________________________<br>Mip6 mailing list<br>Mip6@ietf.org<br><a target="_blank" href="https://www1.ietf.org/mailman/listinfo/mip6">https://www1.ietf.org/mailman/listinfo/mip6</a><br></div></div><br></div></div></body></html>
--0-1603189681-1153675163=:44894--


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

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

--===============0797330732==--




From mip6-bounces@ietf.org Mon Jul 24 07:40:58 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G4ynj-0007az-5S; Mon, 24 Jul 2006 07:40:43 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G4ynh-0007as-TG
	for mip6@ietf.org; Mon, 24 Jul 2006 07:40:41 -0400
Received: from cluster-d.mailcontrol.com ([217.69.20.190])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G4yng-0008Kq-CC
	for mip6@ietf.org; Mon, 24 Jul 2006 07:40:41 -0400
Received: from rly30d.srv.mailcontrol.com (localhost.localdomain [127.0.0.1])
	by rly30d.srv.mailcontrol.com (MailControl) with ESMTP id
	k6OBeVdb026936
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <mip6@ietf.org>; Mon, 24 Jul 2006 12:40:31 +0100
Received: from submission.mailcontrol.com (submission.mailcontrol.com
	[212.158.48.250])
	by rly30d.srv.mailcontrol.com (MailControl) id k6OBdhmV024311
	for mip6@ietf.org; Mon, 24 Jul 2006 12:39:43 +0100
Received: from hhe500-02.hbg.de.pan.eu (gate.eu.panasonic.com [194.173.20.12])
	by rly30d-eth0.srv.mailcontrol.com (envelope-sender
	Kilian.Weniger@eu.panasonic.com) (MIMEDefang) with ESMTP id
	k6OBdeEm024130; Mon, 24 Jul 2006 12:39:43 +0100 (BST)
Received: from eundadmi01.pan.eu(10.100.96.64) by hhe500-02.hbg.de.pan.eu via
	smtp id 776e_d19728a0_1b03_11db_9b97_0030482aac25;
	Mon, 24 Jul 2006 13:01:54 +0200
Received: from VPN-MRelay-01.PRDCG.Panasonic.de ([10.100.176.55])
	by eundadmi01.pan.eu (Lotus Domino Release 6.5.4FP3)
	with ESMTP id 2006072413393015-71833 ;
	Mon, 24 Jul 2006 13:39:30 +0200 
X-Spam-Status: No, hits=0.0 required=6.5
	tests=ALL_TRUSTED: -2.867,AWL: 0.672,BAYES_00: -1.665,
	SARE_RECV_ADDR: 0.027
X-Spam-Level: 
Received: from localhost ([127.0.0.1]) by VPN-MRelay-01.PRDCG.Panasonic.de;
	Mon, 24 Jul 2006 13:43:11 +0200
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.5
Subject: RE: [Mip6] New charter item: HA assignment
In-reply-to: <024c01c6ac1c$50dd9b00$196115ac@dcml.docomolabsusa.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] New charter item: HA assignment
Thread-Index: AcasH8w6zezntFJtTOWUw3HNmVKyTwC8M/gA
To: "James Kempf" <kempf@docomolabs-usa.com>
Message-ID: <4D2F935F08D41A4C8866693F4F0D7C4FD44FCC@lan-ex-01.panasonic.de>
Date: Mon, 24 Jul 2006 13:39:23 +0200
From: "Kilian Weniger" <Kilian.Weniger@eu.panasonic.com>
Content-class: urn:content-classes:message
Content-Type: text/plain;
	charset="us-ascii"
X-Scanned-By: MailControl A-07-00-11 (www.mailcontrol.com) on 10.68.1.140
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.1 (/)
X-Scan-Signature: a8a20a483a84f747e56475e290ee868e
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi James,=20

> -----Original Message-----
> From: James Kempf [mailto:kempf@docomolabs-usa.com]=20
> Sent: Donnerstag, 20. Juli 2006 18:48
> To: Jean-Michel Combes
> Cc: Mobile IPv6 Mailing List; Alexandru Petrescu
> Subject: Re: [Mip6] New charter item: HA assignment
>=20
> Jean-Michel,
>=20
> >> On the other hand, if you want a way to say "thou shalt=20
> use this HA"=20
> >> without
> >> a lot of initial negotiation, then I'd suggest using the=20
> intergrated
> >> scenerio and simply let DHCP assign the MN to an HA=20
> (though that would
> >> require DHCP security).
> >
> > Yes but we need solutions for all the scenarios. I don't see an
> > operator sending a message to a mobility subscriber saying "You are
> > not in an integrated case: please, stop using the IETF=20
> network if you
> > want to bootstrap your IPv6 mobility service" ;)
> >
>=20
> The assumption behind the integrated scenerio is that the=20
> operator has=20
> deployed it and that there is configuration from the operator=20
> when the=20
> terminal first boots up instructing the terminal to=20
> henceforth try DHCP for=20
> HA configuration prior to rolling over to the split scenerio method.
>=20
> >>
> >> If these are insufficient, then the only other suggestion=20
> is that an=20
> >> IKEv2
> >> INFORMATIONAL message be defined directing the MN to try=20
> IKEv2 with=20
> >> another
> >> node (which would be the preferred HA). Such a message=20
> could be used for=20
> >> VPN
> >> server load balancing too.
> >
> > Maybe too depend to a specific service: I am not sure that=20
> IPsec guys
> > will accept such an addition in IKEv2.
> >
>=20
> IPsec WG is no more. Adding INFORMATIONAL messages to IKEv2 is OK, of=20
> course, it would need to go through SAAG review as with every=20
> other security=20
> item, and they might object.
>=20
> Anyway, it seems that HA assignment can be done using the HA=20
> Switch message=20
> within the IPsec SA, at some expense to establish the SA with=20
> the original=20
> HA. But I believe that expense would be needed in any case to=20
> establish=20
> security, and it won't be acceptable from a security=20
> standpoint to send an=20
> HA assignment message without security. An IKEv2 message=20
> would reduce the=20
> amount of security configuration slightly, but is it really necessary?
>=20

Another drawback of the HA switch solution is that it may not fulfill
one of the requirements stated by Jean-Michel:=20
"- the operator wants to loadbalance the charge on the different HAs it
owns during the bootstrapping (e.g to avoid DoS attacks)"

If the initial HA is overloaded (e.g., due to DoS attack) and all new
MNs select the same initial HA within a longer period of time (according
to the weights in DNS), new MNs cannot get mobility service or only
after a timeout when falling back to another HA (and if all MNs fall
back to the same HA, the new HA may be overloaded soon as well).=20

However, the problem depends on how the initial HA is selected.
Anycasting can be used to prevent that new MNs select the same initial
HA. For instance, the IKE_SA_INIT can be anycasted. But if this is done,
you can easily get rid of the unnecessary SA establishment and the
switch message by requiring the receiver HA to forward the IKE_SA_INIT
to a MN-specific and low-loaded HA (see
draft-dupont-ikev2-haassign-01.txt for details).=20

-Kilian

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


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



From mip6-bounces@ietf.org Mon Jul 24 10:50:46 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G51lT-0004xY-9w; Mon, 24 Jul 2006 10:50:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G51lR-0004mz-4j
	for mip6@ietf.org; Mon, 24 Jul 2006 10:50:33 -0400
Received: from py-out-1112.google.com ([64.233.166.181])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G51lP-00029k-U2
	for mip6@ietf.org; Mon, 24 Jul 2006 10:50:33 -0400
Received: by py-out-1112.google.com with SMTP id t32so2630010pyc
	for <mip6@ietf.org>; Mon, 24 Jul 2006 07:50:31 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=QoP2DBw2AJ9g5HnKGfs97G8OtTRY6Q12fwgHePe3uqSxpDirzJy4MQleXc5HRDCYdI8GrOJVSiCP5zcdAIwqIsuoaJmhzOTZn0+Ea0Kh44WNO++NamyvZvVwTy570xWFaqfYvSDjJ1hc3dfwVXRMoQXLPI8tj55Sz2Sd9dOeiZY=
Received: by 10.35.63.2 with SMTP id q2mr7722507pyk;
	Mon, 24 Jul 2006 07:50:31 -0700 (PDT)
Received: by 10.35.111.9 with HTTP; Mon, 24 Jul 2006 07:50:31 -0700 (PDT)
Message-ID: <729b68be0607240750w63c7362ck9ae59d99283f2d16@mail.gmail.com>
Date: Mon, 24 Jul 2006 16:50:31 +0200
From: "Jean-Michel Combes" <jeanmichel.combes@gmail.com>
To: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
Subject: Re: [Mip6] New charter item: HA assignment
In-Reply-To: <44BFC0C5.2000705@azairenet.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <729b68be0607180431m773dc847qed3e7350819a8d04@mail.gmail.com>
	<44BD28C9.50403@azairenet.com>
	<729b68be0607200744p4ed083c0l4f7a4cddb0897fa7@mail.gmail.com>
	<44BFC0C5.2000705@azairenet.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi Vijay,

sorry but I don't understand your question ...

Why do you need a specific scenario? We have already one: the split
scenario. This is the same but the MSP wants to assign the HA because
of the previous technical reasons I cited.

Best regards.

JMC.

2006/7/20, Vijay Devarapalli <vijay.devarapalli@azairenet.com>:
> Jean-Michel Combes wrote:
>
> >> we can come up with some hacks to the HA discovery
> >> mechanism to force the MN to pick a particular HA,
> >> but I would rather avoid it. it would be better if
> >> you tell us what the scenario and which are the
> >> entities involved. then we can design a solution
> >> for the specific scenario.
> >
> >
> > A MSP wants to assign a specific HA to a specific MN because:
> > - the HAs are owned by the MSP (the main reason!!! :)
> > - the MN uses a specific mobility mechanism (e.g. MIPv6, HMIPv6, NEMO,
> > Monami6)
> > - the operator wants to loadbalance the charge on the different HAs it
> > owns during the bootstrapping (e.g to avoid DoS attacks)
> > - the operator offers different types of QoS on the HAs
>
> by scenario I meant the specific deployment. it might be
> better to handle this deployment specific instead of trying
> to design a generic solution.
>
> Vijay
>

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



From mip6-bounces@ietf.org Mon Jul 24 11:53:50 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G52ke-0000VD-6N; Mon, 24 Jul 2006 11:53:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G52kc-0000V8-NF
	for mip6@ietf.org; Mon, 24 Jul 2006 11:53:46 -0400
Received: from mail1.azairenet.com ([66.92.223.4] helo=bart.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G52kb-00020A-DM
	for mip6@ietf.org; Mon, 24 Jul 2006 11:53:46 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
Subject: RE: [Mip6] New charter item: HA assignment
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 24 Jul 2006 08:53:08 -0700
Message-ID: <C8E1D942CB394746BE5CFEB7D97610E70169AA4B@bart.corp.azairenet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] New charter item: HA assignment
Thread-Index: AcavMIYSX9DKW3F1RbytlZ6bsQx8kAACLvyq
From: "Vijay Devarapalli" <Vijay.Devarapalli@AzaireNet.com>
To: "Jean-Michel Combes" <jeanmichel.combes@gmail.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

the specific deployment, as in France Telcom's network
somewhere in some country.

Vijay

-----Original Message-----
From: Jean-Michel Combes [mailto:jeanmichel.combes@gmail.com]
Sent: Mon 7/24/2006 7:50 AM
To: Vijay Devarapalli
Cc: Mobile IPv6 Mailing List
Subject: Re: [Mip6] New charter item: HA assignment
=20
Hi Vijay,

sorry but I don't understand your question ...

Why do you need a specific scenario? We have already one: the split
scenario. This is the same but the MSP wants to assign the HA because
of the previous technical reasons I cited.

Best regards.

JMC.

2006/7/20, Vijay Devarapalli <vijay.devarapalli@azairenet.com>:
> Jean-Michel Combes wrote:
>
> >> we can come up with some hacks to the HA discovery
> >> mechanism to force the MN to pick a particular HA,
> >> but I would rather avoid it. it would be better if
> >> you tell us what the scenario and which are the
> >> entities involved. then we can design a solution
> >> for the specific scenario.
> >
> >
> > A MSP wants to assign a specific HA to a specific MN because:
> > - the HAs are owned by the MSP (the main reason!!! :)
> > - the MN uses a specific mobility mechanism (e.g. MIPv6, HMIPv6, =
NEMO,
> > Monami6)
> > - the operator wants to loadbalance the charge on the different HAs =
it
> > owns during the bootstrapping (e.g to avoid DoS attacks)
> > - the operator offers different types of QoS on the HAs
>
> by scenario I meant the specific deployment. it might be
> better to handle this deployment specific instead of trying
> to design a generic solution.
>
> Vijay
>


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



From mip6-bounces@ietf.org Mon Jul 24 13:13:41 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G53zq-00031c-8Q; Mon, 24 Jul 2006 13:13:34 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G53zp-00031X-GM
	for mip6@ietf.org; Mon, 24 Jul 2006 13:13:33 -0400
Received: from key1.docomolabs-usa.com ([216.98.102.225]
	helo=fridge.docomolabs-usa.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G53zo-0004ic-1Y
	for mip6@ietf.org; Mon, 24 Jul 2006 13:13:33 -0400
Subject: RE: SDO needs (was RE: [Mip6] New Charter Item:Support for Dormant
	Mode Alert to HA?)
MIME-Version: 1.0
Date: Mon, 24 Jul 2006 10:14:49 -0700
Message-ID: <2FD61F37AFF16D4DB46149330E4273C7095A49@dcl-ex.dcml.docomolabs-usa.com>
References: <0MKp2t-1G3iPI2kcA-000411@mrelay.perfora.net>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Alper Yegin" <alper.yegin@yegin.org>,
	"Narayanan, Vidya" <vidyan@qualcomm.com>,
	"Tsirtsis, George" <tsirtsis@qualcomm.com>,
	"Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: b22590c27682ace61775ee7b453b40d3
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0573011646=="
Errors-To: mip6-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0573011646==
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C6AF44.CAFD7DF4"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C6AF44.CAFD7DF4
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Alper,
=20
I sent email to the NWG list requesting responses, and Raj replied that =
he thought it would be useful. I'm not sure what Raj's role is, I =
believe he is Team lead for IPv6.=20
=20
          jak

________________________________

From: Alper Yegin [mailto:alper.yegin@yegin.org]
Sent: Thu 7/20/2006 4:58 PM
To: James Kempf; 'Narayanan, Vidya'; 'Tsirtsis, George'; 'Vijay =
Devarapalli'
Cc: mip6@ietf.org
Subject: SDO needs (was RE: [Mip6] New Charter Item:Support for Dormant =
Mode Alert to HA?)



> Your point about 3GPP2 needing EAP support is also a concern to Wimax
> Forum,
> as I mentioned in the original email that started this thread, but, in
> addition, I was hearing that they were concerned about IPsec SA =
timeout
> during dormant mode. I sent email to the Wimax Forum list, and Raj
> confirmed
> that this was, indeed, a concern.

I think this can only be reported as "the opinion of one WiMAX Forum
member", as opposed to the collective and official view of the WiMAX =
Forum.
I think we should be careful about how to carry and use information =
between
IETF and other SDOs. In this particular instance, I'm saying this as not
only a member of this IETF community, but also as a WiMAX Forum NWG =
Security
lead and also someone involved with forming a liaison between the two
organizations. I am not aware of any collective and official discussion
around this subject to be conveyed to IETF.

Alper








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

<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">=0A=
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">=0A=
<HTML>=0A=
<HEAD>=0A=
=0A=
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7638.1">=0A=
<TITLE>SDO needs (was  RE: [Mip6] New Charter Item:Support for Dormant =
Mode Alert to HA?)</TITLE>=0A=
</HEAD>=0A=
<BODY>=0A=
<DIV id=3DidOWAReplyText95127 dir=3Dltr>=0A=
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 =
size=3D2>Alper,</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>I sent email to the NWG list =
requesting =0A=
responses, and Raj replied that he thought it would be useful. I'm not =
sure what =0A=
Raj's role is, I believe he is Team lead for IPv6. </FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial =0A=
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =0A=
jak</FONT></DIV></DIV>=0A=
<DIV dir=3Dltr><BR>=0A=
<HR tabIndex=3D-1>=0A=
<FONT face=3DTahoma size=3D2><B>From:</B> Alper Yegin =0A=
[mailto:alper.yegin@yegin.org]<BR><B>Sent:</B> Thu 7/20/2006 4:58 =0A=
PM<BR><B>To:</B> James Kempf; 'Narayanan, Vidya'; 'Tsirtsis, George'; =
'Vijay =0A=
Devarapalli'<BR><B>Cc:</B> mip6@ietf.org<BR><B>Subject:</B> SDO needs =
(was RE: =0A=
[Mip6] New Charter Item:Support for Dormant Mode Alert to =0A=
HA?)<BR></FONT><BR></DIV>=0A=
<DIV>=0A=
<P><FONT size=3D2>&gt; Your point about 3GPP2 needing EAP support is =
also a =0A=
concern to Wimax<BR>&gt; Forum,<BR>&gt; as I mentioned in the original =
email =0A=
that started this thread, but, in<BR>&gt; addition, I was hearing that =
they were =0A=
concerned about IPsec SA timeout<BR>&gt; during dormant mode. I sent =
email to =0A=
the Wimax Forum list, and Raj<BR>&gt; confirmed<BR>&gt; that this was, =
indeed, a =0A=
concern.<BR><BR>I think this can only be reported as "the opinion of one =
WiMAX =0A=
Forum<BR>member", as opposed to the collective and official view of the =
WiMAX =0A=
Forum.<BR>I think we should be careful about how to carry and use =
information =0A=
between<BR>IETF and other SDOs. In this particular instance, I'm saying =
this as =0A=
not<BR>only a member of this IETF community, but also as a WiMAX Forum =
NWG =0A=
Security<BR>lead and also someone involved with forming a liaison =
between the =0A=
two<BR>organizations. I am not aware of any collective and official =0A=
discussion<BR>around this subject to be conveyed to =0A=
IETF.<BR><BR>Alper<BR><BR><BR><BR><BR><BR></FONT></P></DIV>=0A=
=0A=
</BODY>=0A=
</HTML>
------_=_NextPart_001_01C6AF44.CAFD7DF4--


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

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

--===============0573011646==--




From mip6-bounces@ietf.org Mon Jul 24 13:28:38 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G54EO-0003IC-SP; Mon, 24 Jul 2006 13:28:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G54EN-0003I0-Gx
	for mip6@ietf.org; Mon, 24 Jul 2006 13:28:35 -0400
Received: from mail1.azairenet.com ([66.92.223.4] helo=bart.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G54EM-0005lY-6c
	for mip6@ietf.org; Mon, 24 Jul 2006 13:28:35 -0400
Received: from [10.1.201.0] ([10.1.201.0]) by bart.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Mon, 24 Jul 2006 10:28:30 -0700
Message-ID: <44C502D8.3020100@azairenet.com>
Date: Mon, 24 Jul 2006 10:26:48 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.2 (X11/20060516)
MIME-Version: 1.0
To: Kilian Weniger <Kilian.Weniger@eu.panasonic.com>
Subject: Re: [Mip6] New charter item: HA assignment
References: <4D2F935F08D41A4C8866693F4F0D7C4FD44FCC@lan-ex-01.panasonic.de>
In-Reply-To: <4D2F935F08D41A4C8866693F4F0D7C4FD44FCC@lan-ex-01.panasonic.de>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 24 Jul 2006 17:28:30.0970 (UTC)
	FILETIME=[950A75A0:01C6AF46]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Cc: mip6@ietf.org, James Kempf <kempf@docomolabs-usa.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Kilian Weniger wrote:

> However, the problem depends on how the initial HA is selected.
> Anycasting can be used to prevent that new MNs select the same initial
> HA. For instance, the IKE_SA_INIT can be anycasted. 

is there another instance of using anycast for load balancing.
just curious.

> But if this is done,
> you can easily get rid of the unnecessary SA establishment and the
> switch message by requiring the receiver HA to forward the IKE_SA_INIT
> to a MN-specific and low-loaded HA (see

how do you do this? you would still need a HA-to-HA protocol to
forward the IKE_SA_INIT message to another HA. when you send a
message to an anycast address routing decides which HA receives
the message.

I have seen anycast used to direct a user to the "nearest" server.
"nearest" means nearest by routing hops. when all the HAs on the
same link, I wonder if anycast gets any load balancing at all.

Vijay

> draft-dupont-ikev2-haassign-01.txt for details). 






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


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



From mip6-bounces@ietf.org Mon Jul 24 14:24:50 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G556f-0005bm-M8; Mon, 24 Jul 2006 14:24:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G556e-0005bh-Dj
	for mip6@ietf.org; Mon, 24 Jul 2006 14:24:40 -0400
Received: from key1.docomolabs-usa.com ([216.98.102.225]
	helo=fridge.docomolabs-usa.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G556d-0004vN-0r
	for mip6@ietf.org; Mon, 24 Jul 2006 14:24:40 -0400
Message-ID: <00e701c6af4e$ba0d46e0$196115ac@dcml.docomolabsusa.com>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Kilian Weniger" <Kilian.Weniger@eu.panasonic.com>
References: <4D2F935F08D41A4C8866693F4F0D7C4FD44FCC@lan-ex-01.panasonic.de>
Subject: Re: [Mip6] New charter item: HA assignment
Date: Mon, 24 Jul 2006 11:26:48 -0700
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Kilian,

Another drawback of the HA switch solution is that it may not fulfill
one of the requirements stated by Jean-Michel:
"- the operator wants to loadbalance the charge on the different HAs it
owns during the bootstrapping (e.g to avoid DoS attacks)"

If the initial HA is overloaded (e.g., due to DoS attack) and all new
MNs select the same initial HA within a longer period of time (according
to the weights in DNS), new MNs cannot get mobility service or only
after a timeout when falling back to another HA (and if all MNs fall
back to the same HA, the new HA may be overloaded soon as well).

However, the problem depends on how the initial HA is selected.
Anycasting can be used to prevent that new MNs select the same initial
HA. For instance, the IKE_SA_INIT can be anycasted. But if this is done,
you can easily get rid of the unnecessary SA establishment and the
switch message by requiring the receiver HA to forward the IKE_SA_INIT
to a MN-specific and low-loaded HA (see
draft-dupont-ikev2-haassign-01.txt for details).

jak>> So what happens if the machine hosting the anycast address is under 
DoS attack?

            jak




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



From mip6-bounces@ietf.org Mon Jul 24 14:33:46 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G55FS-000119-5d; Mon, 24 Jul 2006 14:33:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G55FR-000114-Km
	for mip6@ietf.org; Mon, 24 Jul 2006 14:33:45 -0400
Received: from key1.docomolabs-usa.com ([216.98.102.225]
	helo=fridge.docomolabs-usa.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G55FP-0006mO-6e
	for mip6@ietf.org; Mon, 24 Jul 2006 14:33:45 -0400
Message-ID: <011101c6af4f$fe1fec60$196115ac@dcml.docomolabsusa.com>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>,
	"Kilian Weniger" <Kilian.Weniger@eu.panasonic.com>
References: <4D2F935F08D41A4C8866693F4F0D7C4FD44FCC@lan-ex-01.panasonic.de>
	<44C502D8.3020100@azairenet.com>
Subject: Re: [Mip6] New charter item: HA assignment
Date: Mon, 24 Jul 2006 11:35:52 -0700
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=response
Content-Transfer-Encoding: 7bit
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

The other problem with this solution is that there is still no secure way 
for a collection of unicast server addresses to get assigned to an anycast 
address, except for static configuration. So how would the operator be able 
to add HAs to the anycast address?

At least, with the DNS solution, the update of the DNS can be automated 
using dynamic DNS.

                        jak

----- Original Message ----- 
From: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
To: "Kilian Weniger" <Kilian.Weniger@eu.panasonic.com>
Cc: "James Kempf" <kempf@docomolabs-usa.com>; <mip6@ietf.org>
Sent: Monday, July 24, 2006 10:26 AM
Subject: Re: [Mip6] New charter item: HA assignment


> Kilian Weniger wrote:
>
>> However, the problem depends on how the initial HA is selected.
>> Anycasting can be used to prevent that new MNs select the same initial
>> HA. For instance, the IKE_SA_INIT can be anycasted.
>
> is there another instance of using anycast for load balancing.
> just curious.
>
>> But if this is done,
>> you can easily get rid of the unnecessary SA establishment and the
>> switch message by requiring the receiver HA to forward the IKE_SA_INIT
>> to a MN-specific and low-loaded HA (see
>
> how do you do this? you would still need a HA-to-HA protocol to
> forward the IKE_SA_INIT message to another HA. when you send a
> message to an anycast address routing decides which HA receives
> the message.
>
> I have seen anycast used to direct a user to the "nearest" server.
> "nearest" means nearest by routing hops. when all the HAs on the
> same link, I wonder if anycast gets any load balancing at all.
>
> Vijay
>
>> draft-dupont-ikev2-haassign-01.txt for details).
>
>
>
>
>
>
>>
>> -Kilian
>>
>>>             jak
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Mip6 mailing list
>>> Mip6@ietf.org
>>> https://www1.ietf.org/mailman/listinfo/mip6
>>>
>>>
>>
>>
>> _______________________________________________
>> Mip6 mailing list
>> Mip6@ietf.org
>> https://www1.ietf.org/mailman/listinfo/mip6
>
> 



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



From mip6-bounces@ietf.org Mon Jul 24 14:55:02 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G55a1-000169-Qz; Mon, 24 Jul 2006 14:55:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G55a0-000162-Hb
	for mip6@ietf.org; Mon, 24 Jul 2006 14:55:00 -0400
Received: from ithilien.qualcomm.com ([129.46.51.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G55Zx-0002qH-MR
	for mip6@ietf.org; Mon, 24 Jul 2006 14:55:00 -0400
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
	k6OIsnWP016266
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Mon, 24 Jul 2006 11:54:50 -0700
Received: from NAEXBR02.na.qualcomm.com (naexbr02.qualcomm.com [10.46.92.109])
	by crowley.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	k6OIsYYn023528; Mon, 24 Jul 2006 11:54:48 -0700 (PDT)
Received: from NAEX13.na.qualcomm.com ([129.46.51.248]) by
	NAEXBR02.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 24 Jul 2006 11:54:44 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
Date: Mon, 24 Jul 2006 11:54:45 -0700
Message-ID: <C24CB51D5AA800449982D9BCB90325130A15DE@NAEX13.na.qualcomm.com>
In-Reply-To: <2FD61F37AFF16D4DB46149330E4273C7095A48@dcl-ex.dcml.docomolabs-usa.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
Thread-Index: AcavRCYWRkyqS/cmQaKJ461QcYLkPAADm6Rw
From: "Narayanan, Vidya" <vidyan@qualcomm.com>
To: "James Kempf" <kempf@docomolabs-usa.com>,
	"Tsirtsis, George" <tsirtsis@qualcomm.com>,
	"Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
X-OriginalArrivalTime: 24 Jul 2006 18:54:44.0753 (UTC)
	FILETIME=[A0DB1810:01C6AF52]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 85e99493ec37f9acef29c7843dbf2e68
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1598292578=="
Errors-To: mip6-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1598292578==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C6AF52.A08ACB06"

This is a multi-part message in MIME format.

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

I am just not seeing a good technical reason why this is needed.=20
=20
Going in and out of dormancy could happen often and the net idle time is
also unpredictable. Given that, I don't think it is a good idea to have
to send messages and wait for acks before entering dormant mode.=20
=20
If there is a good reason why WiMAX needs it, then perhaps something can
be defined specifically for WiMAX (even a vendor specific payload should
do) - I don't see a general purpose need for this functionality. I just
verified with some 3gpp2 folks that there has been no discussion related
to this in 3gpp2 and also that they don't see the mobile being required
to send any messages before going dormant.=20

Vidya


________________________________

	From: James Kempf [mailto:kempf@docomolabs-usa.com]=20
	Sent: Monday, July 24, 2006 10:12 AM
	To: Narayanan, Vidya; Tsirtsis, George; Vijay Devarapalli
	Cc: mip6@ietf.org
	Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode
Alert to HA?
=09
=09
	Clearly, we disagree about the need for the WG to work on
something here.=20
	=20
	                   jak

________________________________

	From: Narayanan, Vidya [mailto:vidyan@qualcomm.com]
	Sent: Thu 7/20/2006 3:45 PM
	To: James Kempf; Tsirtsis, George; Vijay Devarapalli
	Cc: mip6@ietf.org
	Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode
Alert to HA?
=09
=09


	>
	> The fact is that MIP and IKE are managed by two completely
	> different protocols. RFC 4301 does not specify anything about
	> timeouts in the SPD or SAD, which would allow some kind of
	> per host or per application timeout customization. Your
	> proposal means that the operator would have to manage its HA
	> with the same timeouts for the HA to mobile node MIP traffic
	> as for, say, signaling traffic between two HAs doing the HA
	> reliability protocol or some other IPsec application, because
	> the basic IPsec architecture provides no way to differentiate
	> between the timing requirements of the two.
=09
	I don't see why this is the case. The timers are managed per
IPsec
	session - so, why would the timer values be the same for HA to
MN and HA
	to HA or other entity IPsec sessions?
=09
	> I think this is
	> unreasonable, as the ability of the two to respond to
	> keepalives could be quite different. Furthermore, RFC 4306
	> says this about why any timeouts were left out of IKEv2
(Section 2.4):
	>
	>    Numbers of retries and lengths of timeouts are not covered
in this
	>    specification because they do not affect interoperability.
It is
	>    suggested that messages be retransmitted at least a dozen
	> times over
	>    a period of at least several minutes before giving up on an
SA, but
	>    different environments may require different rules.
	>
=09
	I had stated some of the reasons in one of my earlier emails -
timer
	and/or lifetime negotiation in a key management protocol is
typically
	not very useful.
=09
	> As with other cases involving mobile nodes and IKEv2 (whence
	> came MOBIKE), this does not address the needs of wireless. An
	> implementation on a laptop with 802.11, which doesn't have
	> proper dormant mode support, doesn't need the ability to
	> lengthen the timeout for dormant mode because it will be
	> woken up by the AP when a keepalive arrives. An
	> implementation on a cellphone which does have proper dormant
	> mode support won't, or, at least, it shouldn't if we want to
	> provide proper support for dormant mode. Should the combined
	> BU/SA timeout be the same for both? If so and it is set to the
	> 802.11 timeout, having no way for the cellphone to lengthen
	> its timeout when it goes into dormant mode means drastically
	> reduced cellphone battery lifetime and unhappy customers. If
	> it is set to the expected cellphone dormant mode lifetime
	> then the SAD has a bunch of entries for laptops, whose owners
	> have closed the lids and jumped on a plane, hanging around
	> when they aren't needed. The effect won't be to prohibit
	> interoperability, but it will result in a considerable amount
	> of unnecessary traffic and reduced customer satisfaction.
	>
=09
	There are two sides to this problem - one is the capability for
MNs to
	request a certain lifetime/timer value - here, when a mobile is
entering
	dormant mode, it doesn't always know how long it is going to be
in
	dormant mode. So, what is the timer value being requested? The
second
	side of the problem is that the server can, at any time, get rid
of the
	SA depending on resources it has. So, the fact that a mobile
requested
	an extension of lifetime doesn't particularly matter.
=09
	> Furthermore, IKEv1 had a way to do lifetime negotiation
	> (Section 4.5 in RFC
	> 2407) via the SA lifetime in the ISAKMP messaging. So I don't
	> quite understand why you are opposed to adding an IKEv2
	> INFORMATIONAL exchange for this purpose.
	>
=09
	IKEv2 acknowledged the lack of this feature and decided it is
not
	needed. So, a careful scrutiny of whether we need it is quite
important.
=09
=09
	> Your point about 3GPP2 needing EAP support is also a concern
	> to Wimax Forum, as I mentioned in the original email that
	> started this thread, but, in addition, I was hearing that
	> they were concerned about IPsec SA timeout during dormant
	> mode. I sent email to the Wimax Forum list, and Raj confirmed
	> that this was, indeed, a concern.
	>
	> And finally regarding your point:
	>
	>     As I said in my earlier emails, all the concerns tied to
	> the IPsec timer
	>     values seem to equally apply to the BU lifetime as well -
	> hence, I am
	>     not yet seeing a need for adding this functionality to
	> IKEv2 per say.
	>
	> The problem is that it is possible to extend the binding
	> lifetime by sending a BU just before the mobile node goes
	> into dormant mode, but there is no support in IKEv2 for
	> extending the SA lifetime.
	>
=09
=09
	But, is a mobile that is about to go into dormant really sending
a BU
	and waiting for a BA before going dormant? If all upper layer
protocols
	took that approach, the mobile will potentially have to send a
lot of
	messages prior to entering dormant mode - that doesn't seem to
be a good
	design, IMHO. If we consider the fact that a mobile, at any
time, may be
	dealing with lifetimes in various protocols (say, MIP, IKEv2,
SIP, TLS,
	etc.), I would think it would be much more expensive to send all
these
	messages prior to going dormant.
=09
	Vidya
=09
=09
=09


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>RE: [Mip6] New Charter Item:Support for Dormant Mode =
Alert to HA?</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.2912" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D869424518-24072006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>I am just not seeing a good technical reason =
why this is=20
needed. </FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D869424518-24072006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D869424518-24072006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Going in and out of dormancy could happen often =
and the net=20
idle time is also unpredictable. Given that, I don't think it is a good =
idea to=20
have to send messages and wait for acks before entering dormant mode.=20
</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D869424518-24072006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D869424518-24072006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>If there is a good reason why WiMAX needs it, =
then perhaps=20
something can be defined specifically for WiMAX (even a vendor specific =
payload=20
should do) - I don't see a general purpose need for this functionality. =
I just=20
verified with some 3gpp2 folks that there has been no discussion related =
to this=20
in 3gpp2 and also that they don't see the mobile being required to send =
any=20
messages before going dormant. </FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D869424518-24072006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2><BR>Vidya</FONT></SPAN></DIV></DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> James Kempf=20
  [mailto:kempf@docomolabs-usa.com] <BR><B>Sent:</B> Monday, July 24, =
2006 10:12=20
  AM<BR><B>To:</B> Narayanan, Vidya; Tsirtsis, George; Vijay=20
  Devarapalli<BR><B>Cc:</B> mip6@ietf.org<BR><B>Subject:</B> RE: [Mip6] =
New=20
  Charter Item:Support for Dormant Mode Alert to =
HA?<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV id=3DidOWAReplyText90255 dir=3Dltr>
  <DIV dir=3Dltr><FONT face=3DArial color=3D#000000 size=3D2>Clearly, we =
disagree about=20
  the need for the WG to work on something here. </FONT></DIV>
  <DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV dir=3Dltr><FONT face=3DArial=20
  =
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  jak</FONT></DIV></DIV>
  <DIV dir=3Dltr><BR>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Narayanan, Vidya=20
  [mailto:vidyan@qualcomm.com]<BR><B>Sent:</B> Thu 7/20/2006 3:45=20
  PM<BR><B>To:</B> James Kempf; Tsirtsis, George; Vijay=20
  Devarapalli<BR><B>Cc:</B> mip6@ietf.org<BR><B>Subject:</B> RE: [Mip6] =
New=20
  Charter Item:Support for Dormant Mode Alert to =
HA?<BR></FONT><BR></DIV>
  <DIV><BR>
  <P><FONT size=3D2>&gt;<BR>&gt; The fact is that MIP and IKE are =
managed by two=20
  completely<BR>&gt; different protocols. RFC 4301 does not specify =
anything=20
  about<BR>&gt; timeouts in the SPD or SAD, which would allow some kind=20
  of<BR>&gt; per host or per application timeout customization. =
Your<BR>&gt;=20
  proposal means that the operator would have to manage its HA<BR>&gt; =
with the=20
  same timeouts for the HA to mobile node MIP traffic<BR>&gt; as for, =
say,=20
  signaling traffic between two HAs doing the HA<BR>&gt; reliability =
protocol or=20
  some other IPsec application, because<BR>&gt; the basic IPsec =
architecture=20
  provides no way to differentiate<BR>&gt; between the timing =
requirements of=20
  the two.<BR><BR>I don't see why this is the case. The timers are =
managed per=20
  IPsec<BR>session - so, why would the timer values be the same for HA =
to MN and=20
  HA<BR>to HA or other entity IPsec sessions?<BR><BR>&gt; I think this=20
  is<BR>&gt; unreasonable, as the ability of the two to respond =
to<BR>&gt;=20
  keepalives could be quite different. Furthermore, RFC 4306<BR>&gt; =
says this=20
  about why any timeouts were left out of IKEv2 (Section=20
  2.4):<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp; Numbers of retries and lengths =
of=20
  timeouts are not covered in this<BR>&gt;&nbsp;&nbsp;&nbsp; =
specification=20
  because they do not affect interoperability.&nbsp; It=20
  is<BR>&gt;&nbsp;&nbsp;&nbsp; suggested that messages be retransmitted =
at least=20
  a dozen<BR>&gt; times over<BR>&gt;&nbsp;&nbsp;&nbsp; a period of at =
least=20
  several minutes before giving up on an SA, =
but<BR>&gt;&nbsp;&nbsp;&nbsp;=20
  different environments may require different rules.<BR>&gt;<BR><BR>I =
had=20
  stated some of the reasons in one of my earlier emails - =
timer<BR>and/or=20
  lifetime negotiation in a key management protocol is typically<BR>not =
very=20
  useful.<BR><BR>&gt; As with other cases involving mobile nodes and =
IKEv2=20
  (whence<BR>&gt; came MOBIKE), this does not address the needs of =
wireless.=20
  An<BR>&gt; implementation on a laptop with 802.11, which doesn't =
have<BR>&gt;=20
  proper dormant mode support, doesn't need the ability to<BR>&gt; =
lengthen the=20
  timeout for dormant mode because it will be<BR>&gt; woken up by the AP =
when a=20
  keepalive arrives. An<BR>&gt; implementation on a cellphone which does =
have=20
  proper dormant<BR>&gt; mode support won't, or, at least, it shouldn't =
if we=20
  want to<BR>&gt; provide proper support for dormant mode. Should the=20
  combined<BR>&gt; BU/SA timeout be the same for both? If so and it is =
set to=20
  the<BR>&gt; 802.11 timeout, having no way for the cellphone to=20
  lengthen<BR>&gt; its timeout when it goes into dormant mode means=20
  drastically<BR>&gt; reduced cellphone battery lifetime and unhappy =
customers.=20
  If<BR>&gt; it is set to the expected cellphone dormant mode =
lifetime<BR>&gt;=20
  then the SAD has a bunch of entries for laptops, whose owners<BR>&gt; =
have=20
  closed the lids and jumped on a plane, hanging around<BR>&gt; when =
they aren't=20
  needed. The effect won't be to prohibit<BR>&gt; interoperability, but =
it will=20
  result in a considerable amount<BR>&gt; of unnecessary traffic and =
reduced=20
  customer satisfaction.<BR>&gt;<BR><BR>There are two sides to this =
problem -=20
  one is the capability for MNs to<BR>request a certain lifetime/timer =
value -=20
  here, when a mobile is entering<BR>dormant mode, it doesn't always =
know how=20
  long it is going to be in<BR>dormant mode. So, what is the timer value =
being=20
  requested? The second<BR>side of the problem is that the server can, =
at any=20
  time, get rid of the<BR>SA depending on resources it has. So, the fact =
that a=20
  mobile requested<BR>an extension of lifetime doesn't particularly=20
  matter.<BR><BR>&gt; Furthermore, IKEv1 had a way to do lifetime=20
  negotiation<BR>&gt; (Section 4.5 in RFC<BR>&gt; 2407) via the SA =
lifetime in=20
  the ISAKMP messaging. So I don't<BR>&gt; quite understand why you are =
opposed=20
  to adding an IKEv2<BR>&gt; INFORMATIONAL exchange for this=20
  purpose.<BR>&gt;<BR><BR>IKEv2 acknowledged the lack of this feature =
and=20
  decided it is not<BR>needed. So, a careful scrutiny of whether we need =
it is=20
  quite important.<BR><BR><BR>&gt; Your point about 3GPP2 needing EAP =
support is=20
  also a concern<BR>&gt; to Wimax Forum, as I mentioned in the original =
email=20
  that<BR>&gt; started this thread, but, in addition, I was hearing =
that<BR>&gt;=20
  they were concerned about IPsec SA timeout during dormant<BR>&gt; =
mode. I sent=20
  email to the Wimax Forum list, and Raj confirmed<BR>&gt; that this =
was,=20
  indeed, a concern.<BR>&gt;<BR>&gt; And finally regarding your=20
  point:<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp; As I said in my earlier =
emails,=20
  all the concerns tied to<BR>&gt; the IPsec=20
  timer<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp; values seem to equally apply to =
the BU=20
  lifetime as well -<BR>&gt; hence, I am<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp; =
not yet=20
  seeing a need for adding this functionality to<BR>&gt; IKEv2 per=20
  say.<BR>&gt;<BR>&gt; The problem is that it is possible to extend the=20
  binding<BR>&gt; lifetime by sending a BU just before the mobile node=20
  goes<BR>&gt; into dormant mode, but there is no support in IKEv2 =
for<BR>&gt;=20
  extending the SA lifetime.<BR>&gt;<BR><BR><BR>But, is a mobile that is =
about=20
  to go into dormant really sending a BU<BR>and waiting for a BA before =
going=20
  dormant? If all upper layer protocols<BR>took that approach, the =
mobile will=20
  potentially have to send a lot of<BR>messages prior to entering =
dormant mode -=20
  that doesn't seem to be a good<BR>design, IMHO. If we consider the =
fact that a=20
  mobile, at any time, may be<BR>dealing with lifetimes in various =
protocols=20
  (say, MIP, IKEv2, SIP, TLS,<BR>etc.), I would think it would be much =
more=20
  expensive to send all these<BR>messages prior to going=20
  =
dormant.<BR><BR>Vidya<BR><BR><BR></FONT></P></DIV></BLOCKQUOTE></BODY></H=
TML>

------_=_NextPart_001_01C6AF52.A08ACB06--


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

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

--===============1598292578==--




From mip6-bounces@ietf.org Mon Jul 24 15:05:34 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G55kD-0007fR-K7; Mon, 24 Jul 2006 15:05:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G55kC-0007eo-H1
	for mip6@ietf.org; Mon, 24 Jul 2006 15:05:32 -0400
Received: from key1.docomolabs-usa.com ([216.98.102.225]
	helo=fridge.docomolabs-usa.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G55kB-0005Tg-Bc
	for mip6@ietf.org; Mon, 24 Jul 2006 15:05:32 -0400
Message-ID: <016b01c6af54$6f1b6da0$196115ac@dcml.docomolabsusa.com>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Narayanan, Vidya" <vidyan@qualcomm.com>,
	"Tsirtsis, George" <tsirtsis@qualcomm.com>,
	"Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
References: <C24CB51D5AA800449982D9BCB90325130A15DD@NAEX13.na.qualcomm.com>
Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
Date: Mon, 24 Jul 2006 12:07:40 -0700
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: 1069eb5b3f212f2b9b575eaf2aff5119
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Like I said, we disagree. No need to waste any more network bandwidth on 
discussion.

            jak

----- Original Message ----- 
From: "Narayanan, Vidya" <vidyan@qualcomm.com>
To: "James Kempf" <kempf@docomolabs-usa.com>; "Tsirtsis, George" 
<tsirtsis@qualcomm.com>; "Vijay Devarapalli" 
<vijay.devarapalli@azairenet.com>
Cc: <mip6@ietf.org>
Sent: Monday, July 24, 2006 11:51 AM
Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?


I am just not seeing a good technical reason why this is needed.

Going in and out of dormancy could happen often and the net idle time is
also unpredictable. Given that, I don't think it is a good idea to have
to send messages and wait for acks before entering dormant mode.

If there is a good reason why WiMAX needs it, then perhaps something can
be defined specifically for WiMAX (even a vendor specific payload should
do) - I don't see a general purpose need for this functionality. I just
verified with some 3gpp2 folks that there has been no discussion related
to this in 3gpp2 and also that they don't see the mobile being required
to send any messages before going dormant.

Vidya


________________________________

From: James Kempf [mailto:kempf@docomolabs-usa.com]
Sent: Monday, July 24, 2006 10:12 AM
To: Narayanan, Vidya; Tsirtsis, George; Vijay Devarapalli
Cc: mip6@ietf.org
Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode
Alert to HA?


Clearly, we disagree about the need for the WG to work on
something here.

                   jak

________________________________

From: Narayanan, Vidya [mailto:vidyan@qualcomm.com]
Sent: Thu 7/20/2006 3:45 PM
To: James Kempf; Tsirtsis, George; Vijay Devarapalli
Cc: mip6@ietf.org
Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode
Alert to HA?




>
> The fact is that MIP and IKE are managed by two completely
> different protocols. RFC 4301 does not specify anything about
> timeouts in the SPD or SAD, which would allow some kind of
> per host or per application timeout customization. Your
> proposal means that the operator would have to manage its HA
> with the same timeouts for the HA to mobile node MIP traffic
> as for, say, signaling traffic between two HAs doing the HA
> reliability protocol or some other IPsec application, because
> the basic IPsec architecture provides no way to differentiate
> between the timing requirements of the two.

I don't see why this is the case. The timers are managed per
IPsec
session - so, why would the timer values be the same for HA to
MN and HA
to HA or other entity IPsec sessions?

> I think this is
> unreasonable, as the ability of the two to respond to
> keepalives could be quite different. Furthermore, RFC 4306
> says this about why any timeouts were left out of IKEv2
(Section 2.4):
>
>    Numbers of retries and lengths of timeouts are not covered
in this
>    specification because they do not affect interoperability.
It is
>    suggested that messages be retransmitted at least a dozen
> times over
>    a period of at least several minutes before giving up on an
SA, but
>    different environments may require different rules.
>

I had stated some of the reasons in one of my earlier emails -
timer
and/or lifetime negotiation in a key management protocol is
typically
not very useful.

> As with other cases involving mobile nodes and IKEv2 (whence
> came MOBIKE), this does not address the needs of wireless. An
> implementation on a laptop with 802.11, which doesn't have
> proper dormant mode support, doesn't need the ability to
> lengthen the timeout for dormant mode because it will be
> woken up by the AP when a keepalive arrives. An
> implementation on a cellphone which does have proper dormant
> mode support won't, or, at least, it shouldn't if we want to
> provide proper support for dormant mode. Should the combined
> BU/SA timeout be the same for both? If so and it is set to the
> 802.11 timeout, having no way for the cellphone to lengthen
> its timeout when it goes into dormant mode means drastically
> reduced cellphone battery lifetime and unhappy customers. If
> it is set to the expected cellphone dormant mode lifetime
> then the SAD has a bunch of entries for laptops, whose owners
> have closed the lids and jumped on a plane, hanging around
> when they aren't needed. The effect won't be to prohibit
> interoperability, but it will result in a considerable amount
> of unnecessary traffic and reduced customer satisfaction.
>

There are two sides to this problem - one is the capability for
MNs to
request a certain lifetime/timer value - here, when a mobile is
entering
dormant mode, it doesn't always know how long it is going to be
in
dormant mode. So, what is the timer value being requested? The
second
side of the problem is that the server can, at any time, get rid
of the
SA depending on resources it has. So, the fact that a mobile
requested
an extension of lifetime doesn't particularly matter.

> Furthermore, IKEv1 had a way to do lifetime negotiation
> (Section 4.5 in RFC
> 2407) via the SA lifetime in the ISAKMP messaging. So I don't
> quite understand why you are opposed to adding an IKEv2
> INFORMATIONAL exchange for this purpose.
>

IKEv2 acknowledged the lack of this feature and decided it is
not
needed. So, a careful scrutiny of whether we need it is quite
important.


> Your point about 3GPP2 needing EAP support is also a concern
> to Wimax Forum, as I mentioned in the original email that
> started this thread, but, in addition, I was hearing that
> they were concerned about IPsec SA timeout during dormant
> mode. I sent email to the Wimax Forum list, and Raj confirmed
> that this was, indeed, a concern.
>
> And finally regarding your point:
>
>     As I said in my earlier emails, all the concerns tied to
> the IPsec timer
>     values seem to equally apply to the BU lifetime as well -
> hence, I am
>     not yet seeing a need for adding this functionality to
> IKEv2 per say.
>
> The problem is that it is possible to extend the binding
> lifetime by sending a BU just before the mobile node goes
> into dormant mode, but there is no support in IKEv2 for
> extending the SA lifetime.
>


But, is a mobile that is about to go into dormant really sending
a BU
and waiting for a BA before going dormant? If all upper layer
protocols
took that approach, the mobile will potentially have to send a
lot of
messages prior to entering dormant mode - that doesn't seem to
be a good
design, IMHO. If we consider the fact that a mobile, at any
time, may be
dealing with lifetimes in various protocols (say, MIP, IKEv2,
SIP, TLS,
etc.), I would think it would be much more expensive to send all
these
messages prior to going dormant.

Vidya


>         jak
>
>
>
> ----- Original Message -----
> From: "Narayanan, Vidya" <vidyan@qualcomm.com>
> To: "James Kempf" <kempf@docomolabs-usa.com>; "Tsirtsis,
George"
> <tsirtsis@qualcomm.com>; "Vijay Devarapalli"
> <vijay.devarapalli@azairenet.com>
> Cc: <mip6@ietf.org>
> Sent: Wednesday, July 19, 2006 4:32 PM
> Subject: RE: [Mip6] New Charter Item:Support for Dormant Mode
> Alert to HA?
>
>
>
> >
> > Maybe the incidence of mobiles dropping out is higher for
> > active than dormant mode mobiles?
> >
>
> Hmmm.. I'm not so sure. Given that the IPsec SA under
discussion is
> really for MIP6, I can see why the BU lifetime and the IPsec
> idle timer
> can be in sync without a problem. So, I am surprised that
there are
> independent requirements here.
>
> > Also, another reason for not having the timers have policy
> > fixed values is so that the timers can be set depending on
> > the kind of device. I mentioned this in a response to
George.
> >
>
> Yes, I recall that. But, whatever considerations are given to
the type
> of device would, I'd think, apply to the BU lifetime as well.
>
> Vidya
>
>
> >             jak
> >
> > ----- Original Message -----
> > From: "Narayanan, Vidya" <vidyan@qualcomm.com>
> > To: "James Kempf" <kempf@docomolabs-usa.com>; "Tsirtsis,
George"
> > <tsirtsis@qualcomm.com>; "Vijay Devarapalli"
> > <vijay.devarapalli@azairenet.com>
> > Cc: <mip6@ietf.org>
> > Sent: Wednesday, July 19, 2006 2:55 PM
> > Subject: RE: [Mip6] New Charter Item:Support for Dormant
Mode
> > Alert to HA?
> >
> >
> > What would be the motivation for maintaining such mode
> specific timer
> > values?
> >
> > Vidya
> >
> > ________________________________
> >
> > From: James Kempf [mailto:kempf@docomolabs-usa.com]
> > Sent: Wed 7/19/2006 8:47 AM
> > To: Narayanan, Vidya; Tsirtsis, George; Vijay Devarapalli
> > Cc: mip6@ietf.org
> > Subject: Re: [Mip6] New Charter Item:Support for Dormant
Mode
> > Alert to HA?
> >
> >
> >
> > The operator may want to keep active mode timers short, then
> > set them longer
> > only if the mobile goes into dormant mode.
> >
> >             jak
> >
> >
> >
> > ----- Original Message -----
> > From: "Narayanan, Vidya" <vidyan@qualcomm.com>
> > To: "Tsirtsis, George" <tsirtsis@qualcomm.com>; "Vijay
Devarapalli"
> > <vijay.devarapalli@azairenet.com>
> > Cc: <mip6@ietf.org>; "James Kempf"
<kempf@docomolabs-usa.com>
> > Sent: Tuesday, July 18, 2006 4:26 PM
> > Subject: RE: [Mip6] New Charter Item:Support for Dormant
Mode
> > Alert to HA?
> >
> >
> > I'm just catching up with this discussion.
> >
> > If the IPsec idle timer is at least equal to the BU
lifetime, why is
> > there a need for any other signaling related to dormant
mode?
> > Given that
> > the timer values are a matter of policy, this should be
do-able.
> >
> > Vidya
> >
> > > -----Original Message-----
> > > From: Tsirtsis, George [mailto:tsirtsis@qualcomm.com]
> > > Sent: Tuesday, July 18, 2006 3:11 PM
> > > To: Vijay Devarapalli
> > > Cc: mip6@ietf.org; James Kempf
> > > Subject: RE: [Mip6] New Charter Item:Support for Dormant
Mode
> > > Alert to HA?
> > >
> > > Yes, I meant DPD.
> > >
> > > There is a fate sharing here between MIP6 state and IPSEC
> > > state. I guess the SA lifetime and DPD timer was
introduced
> > > to catch the general case but they do not make sense to be
> > > much different than the MIP lifetime when that is used.
> > >
> > > It is indeed strange, however, that IPSEC does not allow
for
> > > negotiation of these parameters. I guess people will have
to
> > > use reasonable values in each deployment depending what
they
> > > are doing.
> > >
> > > George
> > >
> > > > -----Original Message-----
> > > > From: Vijay Devarapalli
[mailto:vijay.devarapalli@azairenet.com]
> > > > Sent: Tuesday, July 18, 2006 6:06 PM
> > > > To: Tsirtsis, George
> > > > Cc: James Kempf; Chowdhury, Kuntal; mip6@ietf.org
> > > > Subject: Re: [Mip6] New Charter Item:Support for Dormant
> > > Mode Alert to
> > > HA?
> > > >
> > > > Tsirtsis, George wrote:
> > > > > So how often PDP messages are sent is also local
policy?
> > > >
> > > > I guess you meant DPD. yes it is local policy. the
initiator and
> > > > responder configure this independently.
> > > >
> > > > > In which case
> > > > > it can be configured to a time that makes sense for
MIP
> > > or a given
> > > > > deployment scenario.
> > > >
> > > > Yes. however, the IPsec implementation should allow for
> > > sufficiently
> > > > large values for DPD timer. but then again DPD exists so
> > > that unwanted
> > > > IPsec state is removed if the other end goes down or if
> > there is no
> > > > traffic for a long time.
> > > >
> > > > Vijay
> > > >
> > > > > George
> > > > >
> > > > >> -----Original Message-----
> > > > >> From: Vijay Devarapalli
> > [mailto:vijay.devarapalli@azairenet.com]
> > > > >> Sent: Tuesday, July 18, 2006 5:42 PM
> > > > >> To: James Kempf
> > > > >> Cc: Tsirtsis, George; Chowdhury, Kuntal;
mip6@ietf.org
> > > > >> Subject: Re: [Mip6] New Charter Item:Support for
Dormant
> > > Mode Alert
> > > to
> > > > > HA?
> > > > >> James Kempf wrote:
> > > > >>> I don't know. What do operators typically set the SA
> > > lifetime to?
> > > > > Though
> > > > >>> perhaps this is an unanswerable question because,
> as yet, has
> > > > > anybody
> > > > >>> deployed MIPv6?
> > > > >> this is more of an IPsec issue. it depends on the
local
> > > policy on
> > > > >> the initiator and responder. however, as long as
there
> > > is traffic
> > > > >> and there are responses to DPD messages, the IPsec SA
is not
> > > > >> deleted.
> > > > >>
> > > > >> Vijay
> > > > >>
> > > > >>> My only observation is that this seems to be an
issue
> > with Wimax
> > > > > Forum,
> > > > >>> and one of the primary motivators for wanting to use
> > > the RFC 4285
> > > > > Auth
> > > > >>> Option. If IETF and the MIP6 WG would like to
> > encourage them to
> > > use
> > > > > IKE
> > > > >>> (as seemed to be the sentiment when RFC 4285 was
> > discussed, and
> > > one
> > > > > of
> > > > >>> the reasons why it is not PS), it might be
worthwhile
> > to try to
> > > > > address
> > > > >>> their concerns.
> > > > >>>
> > > > >>>            jak
> > > > >>>
> > > > >>> ----- Original Message ----- From: "Tsirtsis,
George"
> > > > >>> <tsirtsis@qualcomm.com>
> > > > >>> To: "James Kempf" <kempf@docomolabs-usa.com>;
> > > "Chowdhury, Kuntal"
> > > > >>> <kchowdhury@starentnetworks.com>
> > > > >>> Cc: <mip6@ietf.org>
> > > > >>> Sent: Tuesday, July 18, 2006 12:10 PM
> > > > >>> Subject: RE: [Mip6] New Charter Item:Support for
> Dormant Mode
> > > Alert
> > > > > to
> > > > >> HA?
> > > > >>>
> > > > >>> May I ask, what is the typical lifetime of the SA
and
> > what would
> > > you
> > > > >>> lengthen it to?
> > > > >>> George
> > > > >>>
> > > > >>>> -----Original Message-----
> > > > >>>> From: James Kempf [mailto:kempf@docomolabs-usa.com]
> > > > >>>> Sent: Tuesday, July 18, 2006 2:43 PM
> > > > >>>> To: Chowdhury, Kuntal
> > > > >>>> Cc: mip6@ietf.org
> > > > >>>> Subject: Re: [Mip6] New Charter Item:Support for
> Dormant Mode
> > > Alert
> > > > > to
> > > > >>> HA?
> > > > >>>
> > > > >>>> Kuntal,
> > > > >>>>
> > > > >>>> The intent is not to introduce something that the
MN
> > would send
> > > > > during
> > > > >>>> dormant mode. Indeed, as you have described, this
would
> > > negatively
> > > > >>> impact
> > > > >>>
> > > > >>>> battery life.
> > > > >>>>
> > > > >>>> The intent is to provide a way for the MN to say
that
> > > it is about
> > > > > to
> > > > >>> go
> > > > >>>
> > > > >>>> into
> > > > >>>> dormant mode, so please lengthen the IPsec SA
> > timeout to avoid
> > > > > having
> > > > >>> it
> > > > >>>
> > > > >>>> expire for some longer period of time.
> > > > >>>>
> > > > >>>>             jak
> > > > >>>>
> > > > >>>> ----- Original Message -----
> > > > >>>> From: "Chowdhury, Kuntal"
<kchowdhury@starentnetworks.com>
> > > > >>>> To: "James Kempf" <kempf@docomolabs-usa.com>
> > > > >>>> Cc: <mip6@ietf.org>
> > > > >>>> Sent: Tuesday, July 18, 2006 11:20 AM
> > > > >>>> Subject: RE: [Mip6] New Charter Item:Support for
> Dormant Mode
> > > Alert
> > > > > to
> > > > >>> HA?
> > > > >>>
> > > > >>>>
> > > > >>>> James,
> > > > >>>>
> > > > >>>> This is a good discussion. Indeed the need for
IPsec
> > keepalives
> > > (or
> > > > >>> DPD)
> > > > >>>
> > > > >>>> over the air when the MN is dormant (or idle) is an
> > > issue in the
> > > > >>>> cellular networks. The issue is Not that there are
no mip6
> > > messages
> > > > >>>> defined or the HA is not aware of dormancy. It is
more of a
> > > paging
> > > > >>>> channel capacity issue, MN's battery life issue and
> > > the signaling
> > > > >>>> overhead to transport the keepalives for a dormant
> MN issue.
> > > > >>>>
> > > > >>>> So, any new message however small won't solve the
> > > problem, IMHO.
> > > > >>>>
> > > > >>>> -Kuntal
> > > > >>>>
> > > > >>>>
> > > > >>>>> -----Original Message-----
> > > > >>>>> From: James Kempf
[mailto:kempf@docomolabs-usa.com]
> > > > >>>>> Sent: Tuesday, July 18, 2006 11:17 AM
> > > > >>>>> To: Vijay Devarapalli
> > > > >>>>> Cc: mip6@ietf.org
> > > > >>>>> Subject: Re: [Mip6] New Charter Item:Support for
> > Dormant Mode
> > > > > Alert
> > > > >>> to
> > > > >>>
> > > > >>>> HA?
> > > > >>>>> For security, the message would need to be sent
> > within an SA.
> > > > > There
> > > > >>> is
> > > > >>>
> > > > >>>> a
> > > > >>>>> question about which.
> > > > >>>>>
> > > > >>>>> One possibility is to do a Mobility Extension
(call
> > > the messages
> > > > >>>> Sleeping
> > > > >>>>> and WakingUp) and send it within the IPsec SA
between
> > > the HA and
> > > > > MN.
> > > > >>>> The
> > > > >>>>> MN
> > > > >>>>> sends the Sleeping message when it is about to go
> > into dormant
> > > > > mode,
> > > > >>>> it
> > > > >>>>> sends the WakingUp message when it comes out
again.
> > > The WakingUp
> > > > >>>> message
> > > > >>>>> isn't needed for the MN to get mobility service,
> it is just
> > > there
> > > > >>> for
> > > > >>>
> > > > >>>>> optimizing the SA timeouts. This would require a
> > > special API on
> > > > > the
> > > > >>> HA
> > > > >>>
> > > > >>>>> between the MIP code and IKE code for the HA to
> > > extend the IPsec
> > > > > SA
> > > > >>>>> lifetime, similar to the one for IKEv1 mobility.
> > The solution
> > > > > would
> > > > >>>> only
> > > > >>>>> be
> > > > >>>>> applicable to Mobile IP.
> > > > >>>>>
> > > > >>>>> The other possibility is to do an IKEv2
> > INFORMATIONAL message
> > > > > that
> > > > >>> is
> > > > >>>
> > > > >>>> sent
> > > > >>>>> within the IKE SA. It works similarly, but there
> would be no
> > > need
> > > > >>> for
> > > > >>>
> > > > >>>> any
> > > > >>>>> API on the HA, since the IKE code itself would
process it
> > > > > (actually,
> > > > >>> I
> > > > >>>
> > > > >>>>> proposed something like this to the Mobike WG but
> > they didn't
> > > see
> > > > >>> the
> > > > >>>
> > > > >>>> need
> > > > >>>>> for it). This would be applicable to both Mobike
> > and Mobile IP
> > > > > (and
> > > > >>>> any
> > > > >>>>> other security protocol that uses IKEv2, so maybe
HIP
> > > as well).
> > > > >>>>>
> > > > >>>>> One question is, does the HA need to do anything
else
> > > if the MN
> > > > > goes
> > > > >>>> into
> > > > >>>>> dormant mode? I think there are lots of things it
could do
> > > > > (lengthen
> > > > >>>> the
> > > > >>>>> BU
> > > > >>>>> timeout, apply a filter that is either mobile
> > > specified or part
> > > > > of
> > > > >>> the
> > > > >>>
> > > > >>>>> user's service profile with the operator to only
> > > allow specific
> > > > >>>> traffic
> > > > >>>>> through, etc.) but I would really like to keep
> > things simple.
> > > > >>>>>
> > > > >>>>>             jak
> > > > >>>>>
> > > > >>>>> ----- Original Message -----
> > > > >>>>> From: "Vijay Devarapalli"
> <vijay.devarapalli@azairenet.com>
> > > > >>>>> To: "James Kempf" <kempf@docomolabs-usa.com>
> > > > >>>>> Cc: <mip6@ietf.org>
> > > > >>>>> Sent: Monday, July 17, 2006 3:43 PM
> > > > >>>>> Subject: Re: [Mip6] New Charter Item:Support for
> > Dormant Mode
> > > > > Alert
> > > > >>> to
> > > > >>>
> > > > >>>> HA?
> > > > >>>>>
> > > > >>>>>> the dormant mode extensions sounds good to me. we
> > > could do this
> > > > >>>>>> extension. one issue to consider - what triggers
> > > this message?
> > > > >>>>>> how does Mobile IP know the mobile node is going
> > > into a dormant
> > > > >>>>>> mode. if we have the trigger we should be okay.
> > > > >>>>>>
> > > > >>>>>> but we have to check if this was the issue. with
> IKEv1 you
> > > > >>>>>> could negotiate a lifetime for the IPsec SA.
> IKEv2 does not
> > > > >>>>>> have the IPsec SA lifetime feature. so keepalives
> > are needed.
> > > > >>>>>>
> > > > >>>>>> James Kempf wrote:
> > > > >>>>>>> I was at Wimax Forum last week and I think I now
> > understand
> > > > > why
> > > > >>>> they
> > > > >>>>> and
> > > > >>>>>>> 3GPP2 want to use RFC 4285 auth option rather
than
> > > IPsec. One
> > > > >>> issue
> > > > >>>
> > > > >>>> -
> > > > >>>>>>> lack of EAP support for client auth - is solved
> > by IKEv2 and
> > > > > they
> > > > >>>> seem
> > > > >>>>> to
> > > > >>>>>>> now be moving in the direction of recommending
> > > IKEv2 if people
> > > > >>> want
> > > > >>>
> > > > >>>> to
> > > > >>>>>>> deploy IPsec.
> > > > >>>>>> yes this was one of the main issues.
> > > > >>>>>>
> > > > >>>>>> the way I saw it folks in 3GPP2 liked RFC 4285
> > because it is
> > > > >>>>>> very similar to the MIPv4 mechanism and they were
> > > comfortable
> > > > >>>>>> with it.
> > > > >>>>>>
> > > > >>>>>> Vijay
> > > > >>>>>>
> > > > >>>>>> But the other issue is a bit more complex.
802.16, like
> > > > >>>>>>> most cellular protocols, has extensive support
> for dormant
> > > > > mode,
> > > > >>>> and
> > > > >>>>>>> Wimax Forum is supporting dormant mode in their
network
> > > > > design.
> > > > >>> If
> > > > >>>
> > > > >>>>> IPsec
> > > > >>>>>>> is used, then there is a risk when a mobile
> node goes into
> > > > >>> dormant
> > > > >>>
> > > > >>>> mode
> > > > >>>>>>> that the IPsec SA may time out. It is
unfortunate
> > that this
> > > > > was
> > > > >>> not
> > > > >>>
> > > > >>>>>>> brought up when the discussion about RFC 4285
was
> > happening,
> > > > > but
> > > > >>> I
> > > > >>>
> > > > >>>>> think
> > > > >>>>>>> this might be something that the WG could work
on
> > > now as part
> > > > > of
> > > > >>>> the
> > > > >>>>> new
> > > > >>>>>>> charter. This would make IKEv2/IPsec more
> attractive as a
> > > > >>> security
> > > > >>>
> > > > >>>>> option
> > > > >>>>>>> for cellular operators.
> > > > >>>>>>>
> > > > >>>>>>> Comments?
> > > > >>>>>>>
> > > > >>>>>>>            jak
> > > > >>>>>>>
> > > > >>>>>>>
> > > > >>>>>>>
> > > > >>>>>>> _______________________________________________
> > > > >>>>>>> Mip6 mailing list
> > > > >>>>>>> Mip6@ietf.org
> > > > >>>>>>> https://www1.ietf.org/mailman/listinfo/mip6
> > > > >>>>>>
> > > > >>>>>
> > > > >>>>>
> > > > >>>>> _______________________________________________
> > > > >>>>> Mip6 mailing list
> > > > >>>>> Mip6@ietf.org
> > > > >>>>> https://www1.ietf.org/mailman/listinfo/mip6
> > > > >>>>
> > > > >>>> "This email message and any attachments are
confidential
> > > > > information
> > > > >>> of
> > > > >>>
> > > > >>>> Starent Networks, Corp. The information transmitted
> > may not be
> > > used
> > > > > to
> > > > >>>> create or change any contractual obligations of
> > > Starent Networks,
> > > > >>> Corp.
> > > > >>>
> > > > >>>> Any
> > > > >>>> review, retransmission, dissemination or other use
of,
> > > or taking
> > > of
> > > > >>> any
> > > > >>>
> > > > >>>> action in reliance upon this e-mail and its
attachments by
> > > persons
> > > > > or
> > > > >>>> entities other than the intended recipient is
> > > prohibited. If you
> > > > > are
> > > > >>> not
> > > > >>>
> > > > >>>> the
> > > > >>>> intended recipient, please notify the sender
> > immediately -- by
> > > > >>> replying to
> > > > >>>
> > > > >>>> this message or by sending an email to
> > > > > postmaster@starentnetworks.com
> > > > >>> --
> > > > >>>
> > > > >>>> and
> > > > >>>> destroy all copies of this message and any
> > attachments without
> > > > > reading
> > > > >>> or
> > > > >>>
> > > > >>>> disclosing their contents. Thank you."
> > > > >>>>
> > > > >>>>
> > > > >>>>
> > > > >>>> _______________________________________________
> > > > >>>> Mip6 mailing list
> > > > >>>> Mip6@ietf.org
> > > > >>>> https://www1.ietf.org/mailman/listinfo/mip6
> > > > >>>
> > > > >>>
> > > > >>>
> > > > >>> _______________________________________________
> > > > >>> Mip6 mailing list
> > > > >>> Mip6@ietf.org
> > > > >>> https://www1.ietf.org/mailman/listinfo/mip6
> > > > >
> > >
> > >
> > > _______________________________________________
> > > Mip6 mailing list
> > > Mip6@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/mip6
> > >
> >
> >
> >
> >
> >
> >
> >
>
>
>





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



From mip6-bounces@ietf.org Mon Jul 24 15:10:10 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G55og-0000u3-5B; Mon, 24 Jul 2006 15:10:10 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G55of-0000tx-Ha
	for mip6@ietf.org; Mon, 24 Jul 2006 15:10:09 -0400
Received: from mail1.azairenet.com ([66.92.223.4] helo=bart.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G55oe-0006WR-5b
	for mip6@ietf.org; Mon, 24 Jul 2006 15:10:09 -0400
Received: from [10.1.201.0] ([10.1.201.0]) by bart.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Mon, 24 Jul 2006 12:10:06 -0700
Message-ID: <44C51AA2.8070003@azairenet.com>
Date: Mon, 24 Jul 2006 12:08:18 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.2 (X11/20060516)
MIME-Version: 1.0
To: James Kempf <kempf@docomolabs-usa.com>
Subject: Re: [Mip6] New charter item: HA assignment
References: <4D2F935F08D41A4C8866693F4F0D7C4FD44FCC@lan-ex-01.panasonic.de>
	<44C502D8.3020100@azairenet.com>
	<011101c6af4f$fe1fec60$196115ac@dcml.docomolabsusa.com>
In-Reply-To: <011101c6af4f$fe1fec60$196115ac@dcml.docomolabsusa.com>
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 24 Jul 2006 19:10:06.0501 (UTC)
	FILETIME=[C642AD50:01C6AF54]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Cc: mip6@ietf.org, Kilian Weniger <Kilian.Weniger@eu.panasonic.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

hi Jim,

I think manual configuration is sufficient in this case. it is
not too often that home agents get added to or deleted from the
the anycast group.

Vijay

James Kempf wrote:
> The other problem with this solution is that there is still no secure 
> way for a collection of unicast server addresses to get assigned to an 
> anycast address, except for static configuration. So how would the 
> operator be able to add HAs to the anycast address?
> 
> At least, with the DNS solution, the update of the DNS can be automated 
> using dynamic DNS.
> 
>                        jak
> 
> ----- Original Message ----- From: "Vijay Devarapalli" 
> <vijay.devarapalli@azairenet.com>
> To: "Kilian Weniger" <Kilian.Weniger@eu.panasonic.com>
> Cc: "James Kempf" <kempf@docomolabs-usa.com>; <mip6@ietf.org>
> Sent: Monday, July 24, 2006 10:26 AM
> Subject: Re: [Mip6] New charter item: HA assignment
> 
> 
>> Kilian Weniger wrote:
>>
>>> However, the problem depends on how the initial HA is selected.
>>> Anycasting can be used to prevent that new MNs select the same initial
>>> HA. For instance, the IKE_SA_INIT can be anycasted.
>>
>> is there another instance of using anycast for load balancing.
>> just curious.
>>
>>> But if this is done,
>>> you can easily get rid of the unnecessary SA establishment and the
>>> switch message by requiring the receiver HA to forward the IKE_SA_INIT
>>> to a MN-specific and low-loaded HA (see
>>
>> how do you do this? you would still need a HA-to-HA protocol to
>> forward the IKE_SA_INIT message to another HA. when you send a
>> message to an anycast address routing decides which HA receives
>> the message.
>>
>> I have seen anycast used to direct a user to the "nearest" server.
>> "nearest" means nearest by routing hops. when all the HAs on the
>> same link, I wonder if anycast gets any load balancing at all.
>>
>> Vijay
>>
>>> draft-dupont-ikev2-haassign-01.txt for details).
>>
>>
>>
>>
>>
>>
>>>
>>> -Kilian
>>>
>>>>             jak
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Mip6 mailing list
>>>> Mip6@ietf.org
>>>> https://www1.ietf.org/mailman/listinfo/mip6
>>>>
>>>>
>>>
>>>
>>> _______________________________________________
>>> Mip6 mailing list
>>> Mip6@ietf.org
>>> https://www1.ietf.org/mailman/listinfo/mip6
>>
>>
> 
> 


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



From mip6-bounces@ietf.org Mon Jul 24 15:14:41 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G55t1-0002Pu-Go; Mon, 24 Jul 2006 15:14:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G55sz-0002L0-LL
	for mip6@ietf.org; Mon, 24 Jul 2006 15:14:37 -0400
Received: from key1.docomolabs-usa.com ([216.98.102.225]
	helo=fridge.docomolabs-usa.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G55sy-0000E1-7I
	for mip6@ietf.org; Mon, 24 Jul 2006 15:14:37 -0400
Message-ID: <018a01c6af55$b4c1f990$196115ac@dcml.docomolabsusa.com>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
References: <4D2F935F08D41A4C8866693F4F0D7C4FD44FCC@lan-ex-01.panasonic.de>
	<44C502D8.3020100@azairenet.com>
	<011101c6af4f$fe1fec60$196115ac@dcml.docomolabsusa.com>
	<44C51AA2.8070003@azairenet.com>
Subject: Re: [Mip6] New charter item: HA assignment
Date: Mon, 24 Jul 2006 12:16:46 -0700
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=response
Content-Transfer-Encoding: 7bit
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: 057ebe9b96adec30a7efb2aeda4c26a4
Cc: mip6@ietf.org, Kilian Weniger <Kilian.Weniger@eu.panasonic.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

I thought the whole point of  the anycast proposal  and Kilian and 
Jean-Marie's argumet against DNS was load balancing and that DNS is 
insufficient because it does not provide fast enough dynamic update. If that 
is the case, then I would think that the ability to quickly add and remove 
addresses from the anycast group would be crucial to removing HAs that are 
loading and adding new ones that aren't.


            jak

----- Original Message ----- 
From: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
To: "James Kempf" <kempf@docomolabs-usa.com>
Cc: "Kilian Weniger" <Kilian.Weniger@eu.panasonic.com>; <mip6@ietf.org>
Sent: Monday, July 24, 2006 12:08 PM
Subject: Re: [Mip6] New charter item: HA assignment


> hi Jim,
>
> I think manual configuration is sufficient in this case. it is
> not too often that home agents get added to or deleted from the
> the anycast group.
>
> Vijay
>
> James Kempf wrote:
>> The other problem with this solution is that there is still no secure way 
>> for a collection of unicast server addresses to get assigned to an 
>> anycast address, except for static configuration. So how would the 
>> operator be able to add HAs to the anycast address?
>>
>> At least, with the DNS solution, the update of the DNS can be automated 
>> using dynamic DNS.
>>
>>                        jak
>>
>> ----- Original Message ----- From: "Vijay Devarapalli" 
>> <vijay.devarapalli@azairenet.com>
>> To: "Kilian Weniger" <Kilian.Weniger@eu.panasonic.com>
>> Cc: "James Kempf" <kempf@docomolabs-usa.com>; <mip6@ietf.org>
>> Sent: Monday, July 24, 2006 10:26 AM
>> Subject: Re: [Mip6] New charter item: HA assignment
>>
>>
>>> Kilian Weniger wrote:
>>>
>>>> However, the problem depends on how the initial HA is selected.
>>>> Anycasting can be used to prevent that new MNs select the same initial
>>>> HA. For instance, the IKE_SA_INIT can be anycasted.
>>>
>>> is there another instance of using anycast for load balancing.
>>> just curious.
>>>
>>>> But if this is done,
>>>> you can easily get rid of the unnecessary SA establishment and the
>>>> switch message by requiring the receiver HA to forward the IKE_SA_INIT
>>>> to a MN-specific and low-loaded HA (see
>>>
>>> how do you do this? you would still need a HA-to-HA protocol to
>>> forward the IKE_SA_INIT message to another HA. when you send a
>>> message to an anycast address routing decides which HA receives
>>> the message.
>>>
>>> I have seen anycast used to direct a user to the "nearest" server.
>>> "nearest" means nearest by routing hops. when all the HAs on the
>>> same link, I wonder if anycast gets any load balancing at all.
>>>
>>> Vijay
>>>
>>>> draft-dupont-ikev2-haassign-01.txt for details).
>>>
>>>
>>>
>>>
>>>
>>>
>>>>
>>>> -Kilian
>>>>
>>>>>             jak
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Mip6 mailing list
>>>>> Mip6@ietf.org
>>>>> https://www1.ietf.org/mailman/listinfo/mip6
>>>>>
>>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Mip6 mailing list
>>>> Mip6@ietf.org
>>>> https://www1.ietf.org/mailman/listinfo/mip6
>>>
>>>
>>
>>
>
> 



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



From mip6-bounces@ietf.org Mon Jul 24 15:18:47 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G55x0-0004JE-Oo; Mon, 24 Jul 2006 15:18:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G55wz-0004J8-5Q
	for mip6@ietf.org; Mon, 24 Jul 2006 15:18:45 -0400
Received: from mail1.azairenet.com ([66.92.223.4] helo=bart.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G55wx-0001VD-Ow
	for mip6@ietf.org; Mon, 24 Jul 2006 15:18:45 -0400
Received: from [10.1.201.0] ([10.1.201.0]) by bart.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Mon, 24 Jul 2006 12:18:42 -0700
Message-ID: <44C51CAB.6030704@azairenet.com>
Date: Mon, 24 Jul 2006 12:16:59 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.2 (X11/20060516)
MIME-Version: 1.0
To: James Kempf <kempf@docomolabs-usa.com>
Subject: Re: [Mip6] New charter item: HA assignment
References: <4D2F935F08D41A4C8866693F4F0D7C4FD44FCC@lan-ex-01.panasonic.de>
	<44C502D8.3020100@azairenet.com>
	<011101c6af4f$fe1fec60$196115ac@dcml.docomolabsusa.com>
	<44C51AA2.8070003@azairenet.com>
	<018a01c6af55$b4c1f990$196115ac@dcml.docomolabsusa.com>
In-Reply-To: <018a01c6af55$b4c1f990$196115ac@dcml.docomolabsusa.com>
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 24 Jul 2006 19:18:42.0382 (UTC)
	FILETIME=[F9BFDEE0:01C6AF55]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 36c793b20164cfe75332aa66ddb21196
Cc: mip6@ietf.org, Kilian Weniger <Kilian.Weniger@eu.panasonic.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

James Kempf wrote:
> I thought the whole point of  the anycast proposal  and Kilian and 
> Jean-Marie's argumet against DNS was load balancing and that DNS is 
> insufficient because it does not provide fast enough dynamic update. If 
> that is the case, then I would think that the ability to quickly add and 
> remove addresses from the anycast group would be crucial to removing HAs 
> that are loading and adding new ones that aren't.

load balancing does not necessarily mean removing/adding a HA
from/to the list of HAs. I think it is more about directing the
users to the right HA. you can have a pretty stable anycast
group and still direct the MN to a specific HA.

Vijay

> 
> 
>            jak
> 
> ----- Original Message ----- From: "Vijay Devarapalli" 
> <vijay.devarapalli@azairenet.com>
> To: "James Kempf" <kempf@docomolabs-usa.com>
> Cc: "Kilian Weniger" <Kilian.Weniger@eu.panasonic.com>; <mip6@ietf.org>
> Sent: Monday, July 24, 2006 12:08 PM
> Subject: Re: [Mip6] New charter item: HA assignment
> 
> 
>> hi Jim,
>>
>> I think manual configuration is sufficient in this case. it is
>> not too often that home agents get added to or deleted from the
>> the anycast group.
>>
>> Vijay
>>
>> James Kempf wrote:
>>> The other problem with this solution is that there is still no secure 
>>> way for a collection of unicast server addresses to get assigned to 
>>> an anycast address, except for static configuration. So how would the 
>>> operator be able to add HAs to the anycast address?
>>>
>>> At least, with the DNS solution, the update of the DNS can be 
>>> automated using dynamic DNS.
>>>
>>>                        jak
>>>
>>> ----- Original Message ----- From: "Vijay Devarapalli" 
>>> <vijay.devarapalli@azairenet.com>
>>> To: "Kilian Weniger" <Kilian.Weniger@eu.panasonic.com>
>>> Cc: "James Kempf" <kempf@docomolabs-usa.com>; <mip6@ietf.org>
>>> Sent: Monday, July 24, 2006 10:26 AM
>>> Subject: Re: [Mip6] New charter item: HA assignment
>>>
>>>
>>>> Kilian Weniger wrote:
>>>>
>>>>> However, the problem depends on how the initial HA is selected.
>>>>> Anycasting can be used to prevent that new MNs select the same initial
>>>>> HA. For instance, the IKE_SA_INIT can be anycasted.
>>>>
>>>> is there another instance of using anycast for load balancing.
>>>> just curious.
>>>>
>>>>> But if this is done,
>>>>> you can easily get rid of the unnecessary SA establishment and the
>>>>> switch message by requiring the receiver HA to forward the IKE_SA_INIT
>>>>> to a MN-specific and low-loaded HA (see
>>>>
>>>> how do you do this? you would still need a HA-to-HA protocol to
>>>> forward the IKE_SA_INIT message to another HA. when you send a
>>>> message to an anycast address routing decides which HA receives
>>>> the message.
>>>>
>>>> I have seen anycast used to direct a user to the "nearest" server.
>>>> "nearest" means nearest by routing hops. when all the HAs on the
>>>> same link, I wonder if anycast gets any load balancing at all.
>>>>
>>>> Vijay
>>>>
>>>>> draft-dupont-ikev2-haassign-01.txt for details).
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>
>>>>> -Kilian
>>>>>
>>>>>>             jak
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Mip6 mailing list
>>>>>> Mip6@ietf.org
>>>>>> https://www1.ietf.org/mailman/listinfo/mip6
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Mip6 mailing list
>>>>> Mip6@ietf.org
>>>>> https://www1.ietf.org/mailman/listinfo/mip6
>>>>
>>>>
>>>
>>>
>>
>>
> 
> 


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



From mip6-bounces@ietf.org Mon Jul 24 15:20:03 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G55yF-00056W-Qq; Mon, 24 Jul 2006 15:20:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G55yE-00056R-Dw
	for mip6@ietf.org; Mon, 24 Jul 2006 15:20:02 -0400
Received: from mgw-ext11.nokia.com ([131.228.20.170])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G55yB-0002E6-Vc
	for mip6@ietf.org; Mon, 24 Jul 2006 15:20:02 -0400
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
	by mgw-ext11.nokia.com (Switch-3.1.8/Switch-3.1.7) with ESMTP id
	k6OIJv28026389 for <mip6@ietf.org>; Mon, 24 Jul 2006 21:19:59 +0300
Received: from daebh102.NOE.Nokia.com ([10.241.35.112]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 24 Jul 2006 22:19:53 +0300
Received: from daebe101.NOE.Nokia.com ([10.241.35.113]) by
	daebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 24 Jul 2006 14:19:51 -0500
Received: from 172.19.244.128 ([172.19.244.128]) by daebe101.NOE.Nokia.com
	([10.241.35.113]) with Microsoft Exchange Server HTTP-DAV ; 
	Mon, 24 Jul 2006 19:19:51 +0000
User-Agent: Microsoft-Entourage/11.2.5.060620
Date: Mon, 24 Jul 2006 14:19:51 -0500
From: Basavaraj Patil <basavaraj.patil@nokia.com>
To: <mip6@ietf.org>
Message-ID: <C0EA8787.1F6C6%basavaraj.patil@nokia.com>
Thread-Topic: Regarding the charter revision w.r.t the IPsec SA and IKEv2
Thread-Index: AcavViKmYRHoQhtJEduSsQARJNUNiA==
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 24 Jul 2006 19:19:51.0338 (UTC)
	FILETIME=[22D9B8A0:01C6AF56]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: "Eronen Pasi \(Nokia-NRC/Helsinki\)" <Pasi.Eronen@nokia.com>
Subject: [Mip6] Regarding the charter revision w.r.t the IPsec SA and IKEv2
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org


In discussions with Pasi Eronen, I believe there is really nothing specific
that needs to be done w.r.t MIP6 and IKEv2 as far as dead-peer-detection is
concerned. 

Pasi's comment was:
"
When using IPsec for MIP6, there is no need to send any keepalives.
IKE may do Dead Peer Detection (DPD) occasionally, but this is a
configurable parameter (just like binding lifetime) and doing DPD,
say, once every 8 hours does not seem unacceptable to me. And doing
DPD (and Binding Updates) every N hours is IMHO *MUCH* better solution
than introducing hard state (as someone already pointed out on the
list).

(In the NAT case, we typically need keepalives every 30 seconds, and
the endpoints can't choose any other internal since it depends on the
NAT, not the endpoints.)
"

Hence I believe that there is not really any concern as far as IPsec/IKEv2
is concerned in the context of MIP6.

-Raj

P.s: I had to forward Pasi's note since he is not registered on the MIP6
list 


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



From mip6-bounces@ietf.org Mon Jul 24 16:21:02 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G56vE-0001vd-Pw; Mon, 24 Jul 2006 16:21:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G56vD-0001vG-M1
	for mip6@ietf.org; Mon, 24 Jul 2006 16:20:59 -0400
Received: from ithilien.qualcomm.com ([129.46.51.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G56vC-0007mD-9z
	for mip6@ietf.org; Mon, 24 Jul 2006 16:20:59 -0400
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
	k6OKKuKM000390
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Mon, 24 Jul 2006 13:20:57 -0700
Received: from NAEXBR02.na.qualcomm.com (naexbr02.qualcomm.com [10.46.92.109])
	by sabrina.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	k6OKKfE2007360; Mon, 24 Jul 2006 13:20:56 -0700 (PDT)
Received: from NAEX13.na.qualcomm.com ([129.46.51.248]) by
	NAEXBR02.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 24 Jul 2006 13:20:55 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] Regarding the charter revision w.r.t the IPsec SA and IKEv2
Date: Mon, 24 Jul 2006 13:20:55 -0700
Message-ID: <C24CB51D5AA800449982D9BCB90325130A15EF@NAEX13.na.qualcomm.com>
In-Reply-To: <C0EA8787.1F6C6%basavaraj.patil@nokia.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] Regarding the charter revision w.r.t the IPsec SA and
	IKEv2
Thread-Index: AcavViKmYRHoQhtJEduSsQARJNUNiAACHJIQ
From: "Narayanan, Vidya" <vidyan@qualcomm.com>
To: "Basavaraj Patil" <basavaraj.patil@nokia.com>, <mip6@ietf.org>
X-OriginalArrivalTime: 24 Jul 2006 20:20:55.0295 (UTC)
	FILETIME=[AABD30F0:01C6AF5E]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Cc: "Eronen Pasi \(Nokia-NRC/Helsinki\)" <Pasi.Eronen@nokia.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

This was my understanding as well. It is a matter of policy and timer
configuration.=20

Vidya

> -----Original Message-----
> From: Basavaraj Patil [mailto:basavaraj.patil@nokia.com]=20
> Sent: Monday, July 24, 2006 12:20 PM
> To: mip6@ietf.org
> Cc: Eronen Pasi (Nokia-NRC/Helsinki)
> Subject: [Mip6] Regarding the charter revision w.r.t the=20
> IPsec SA and IKEv2
>=20
>=20
> In discussions with Pasi Eronen, I believe there is really=20
> nothing specific that needs to be done w.r.t MIP6 and IKEv2=20
> as far as dead-peer-detection is concerned.=20
>=20
> Pasi's comment was:
> "
> When using IPsec for MIP6, there is no need to send any keepalives.
> IKE may do Dead Peer Detection (DPD) occasionally, but this=20
> is a configurable parameter (just like binding lifetime) and=20
> doing DPD, say, once every 8 hours does not seem unacceptable=20
> to me. And doing DPD (and Binding Updates) every N hours is=20
> IMHO *MUCH* better solution than introducing hard state (as=20
> someone already pointed out on the list).
>=20
> (In the NAT case, we typically need keepalives every 30=20
> seconds, and the endpoints can't choose any other internal=20
> since it depends on the NAT, not the endpoints.) "
>=20
> Hence I believe that there is not really any concern as far=20
> as IPsec/IKEv2 is concerned in the context of MIP6.
>=20
> -Raj
>=20
> P.s: I had to forward Pasi's note since he is not registered=20
> on the MIP6 list=20
>=20
>=20
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
>=20

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



From mip6-bounces@ietf.org Mon Jul 24 16:24:03 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G56yB-00049L-8X; Mon, 24 Jul 2006 16:24:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G56yA-00046G-23
	for mip6@ietf.org; Mon, 24 Jul 2006 16:24:02 -0400
Received: from mail1.azairenet.com ([66.92.223.4] helo=bart.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G56y8-0000M0-KB
	for mip6@ietf.org; Mon, 24 Jul 2006 16:24:02 -0400
Received: from [10.1.201.0] ([10.1.201.0]) by bart.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Mon, 24 Jul 2006 13:23:58 -0700
Message-ID: <44C52BF7.4070207@azairenet.com>
Date: Mon, 24 Jul 2006 13:22:15 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.2 (X11/20060516)
MIME-Version: 1.0
To: Basavaraj Patil <basavaraj.patil@nokia.com>
Subject: Re: [Mip6] Regarding the charter revision w.r.t the IPsec SA and IKEv2
References: <C0EA8787.1F6C6%basavaraj.patil@nokia.com>
In-Reply-To: <C0EA8787.1F6C6%basavaraj.patil@nokia.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 24 Jul 2006 20:23:58.0761 (UTC)
	FILETIME=[1817E190:01C6AF5F]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Cc: mip6@ietf.org, "Eronen Pasi \(Nokia-NRC/Helsinki\)" <Pasi.Eronen@nokia.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Basavaraj Patil wrote:
> In discussions with Pasi Eronen, I believe there is really nothing specific
> that needs to be done w.r.t MIP6 and IKEv2 as far as dead-peer-detection is
> concerned. 
> 
> Pasi's comment was:
> "
> When using IPsec for MIP6, there is no need to send any keepalives.
> IKE may do Dead Peer Detection (DPD) occasionally, but this is a
> configurable parameter (just like binding lifetime) and doing DPD,
> say, once every 8 hours does not seem unacceptable to me. And doing
> DPD (and Binding Updates) every N hours is IMHO *MUCH* better solution
> than introducing hard state (as someone already pointed out on the
> list).

yes, the DPD timer is configurable, but it does not change
dynamically based on whether the mobile node is dormant or
not. the proposed extension lets you change the DPD timer
on the responder dynamically. currently you are stuck with
a fixed DPD timer.

take the mobile IP binding cache state for example. the
binding cache lifetime can be changed at any time by sending
a BU with a different lifetime.

Vijay


> (In the NAT case, we typically need keepalives every 30 seconds, and
> the endpoints can't choose any other internal since it depends on the
> NAT, not the endpoints.)
> "
> 
> Hence I believe that there is not really any concern as far as IPsec/IKEv2
> is concerned in the context of MIP6.
> 
> -Raj
> 
> P.s: I had to forward Pasi's note since he is not registered on the MIP6
> list 
> 
> 
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6


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



From mip6-bounces@ietf.org Mon Jul 24 16:43:02 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G57GW-0007Tc-W2; Mon, 24 Jul 2006 16:43:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G57GU-0007IS-VW
	for mip6@ietf.org; Mon, 24 Jul 2006 16:42:58 -0400
Received: from key1.docomolabs-usa.com ([216.98.102.225]
	helo=fridge.docomolabs-usa.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G57GT-0002P1-Ic
	for mip6@ietf.org; Mon, 24 Jul 2006 16:42:58 -0400
Message-ID: <026401c6af62$0ca4a390$196115ac@dcml.docomolabsusa.com>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Basavaraj Patil" <basavaraj.patil@nokia.com>, <mip6@ietf.org>
References: <C0EA8787.1F6C6%basavaraj.patil@nokia.com>
Subject: Re: [Mip6] Regarding the charter revision w.r.t the IPsec SA and IKEv2
Date: Mon, 24 Jul 2006 13:45:07 -0700
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Cc: "Eronen Pasi \(Nokia-NRC/Helsinki\)" <Pasi.Eronen@nokia.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Raj,

Perhaps you could convey this message to NWG?

            jak

----- Original Message ----- 
From: "Basavaraj Patil" <basavaraj.patil@nokia.com>
To: <mip6@ietf.org>
Cc: "Eronen Pasi (Nokia-NRC/Helsinki)" <Pasi.Eronen@nokia.com>
Sent: Monday, July 24, 2006 12:19 PM
Subject: [Mip6] Regarding the charter revision w.r.t the IPsec SA and IKEv2


>
> In discussions with Pasi Eronen, I believe there is really nothing 
> specific
> that needs to be done w.r.t MIP6 and IKEv2 as far as dead-peer-detection 
> is
> concerned.
>
> Pasi's comment was:
> "
> When using IPsec for MIP6, there is no need to send any keepalives.
> IKE may do Dead Peer Detection (DPD) occasionally, but this is a
> configurable parameter (just like binding lifetime) and doing DPD,
> say, once every 8 hours does not seem unacceptable to me. And doing
> DPD (and Binding Updates) every N hours is IMHO *MUCH* better solution
> than introducing hard state (as someone already pointed out on the
> list).
>
> (In the NAT case, we typically need keepalives every 30 seconds, and
> the endpoints can't choose any other internal since it depends on the
> NAT, not the endpoints.)
> "
>
> Hence I believe that there is not really any concern as far as IPsec/IKEv2
> is concerned in the context of MIP6.
>
> -Raj
>
> P.s: I had to forward Pasi's note since he is not registered on the MIP6
> list
>
>
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
> 



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



From mip6-bounces@ietf.org Mon Jul 24 16:55:24 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G57SU-0004uv-VB; Mon, 24 Jul 2006 16:55:22 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G57ST-0004ul-Ig
	for mip6@ietf.org; Mon, 24 Jul 2006 16:55:21 -0400
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G57SS-0005cP-6G
	for mip6@ietf.org; Mon, 24 Jul 2006 16:55:21 -0400
Received: from sabrina.qualcomm.com (sabrina.qualcomm.com [129.46.61.150])
	by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k6OKtFrE023626
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Mon, 24 Jul 2006 13:55:16 -0700
Received: from NAEXBR02.na.qualcomm.com (naexbr02.qualcomm.com [10.46.92.109])
	by sabrina.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	k6OKt5SC021553; Mon, 24 Jul 2006 13:55:14 -0700 (PDT)
Received: from NAEX13.na.qualcomm.com ([129.46.51.248]) by
	NAEXBR02.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 24 Jul 2006 13:53:03 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] Regarding the charter revision w.r.t the IPsec SA and IKEv2
Date: Mon, 24 Jul 2006 13:53:02 -0700
Message-ID: <C24CB51D5AA800449982D9BCB90325130A15F6@NAEX13.na.qualcomm.com>
In-Reply-To: <44C52BF7.4070207@azairenet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] Regarding the charter revision w.r.t the IPsec SA and
	IKEv2
Thread-Index: AcavYZIxqN4JTiERQVSfqRSX4PnEdwAAQltg
From: "Narayanan, Vidya" <vidyan@qualcomm.com>
To: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>,
	"Basavaraj Patil" <basavaraj.patil@nokia.com>
X-OriginalArrivalTime: 24 Jul 2006 20:53:03.0650 (UTC)
	FILETIME=[2820D020:01C6AF63]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Cc: mip6@ietf.org, "Eronen Pasi \(Nokia-NRC/Helsinki\)" <Pasi.Eronen@nokia.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

>=20
> Basavaraj Patil wrote:
> > In discussions with Pasi Eronen, I believe there is really nothing=20
> > specific that needs to be done w.r.t MIP6 and IKEv2 as far as=20
> > dead-peer-detection is concerned.
> >=20
> > Pasi's comment was:
> > "
> > When using IPsec for MIP6, there is no need to send any keepalives.
> > IKE may do Dead Peer Detection (DPD) occasionally, but this is a=20
> > configurable parameter (just like binding lifetime) and doing DPD,=20
> > say, once every 8 hours does not seem unacceptable to me. And doing=20
> > DPD (and Binding Updates) every N hours is IMHO *MUCH*=20
> better solution=20
> > than introducing hard state (as someone already pointed out on the=20
> > list).
>=20
> yes, the DPD timer is configurable, but it does not change=20
> dynamically based on whether the mobile node is dormant or=20
> not. the proposed extension lets you change the DPD timer on=20
> the responder dynamically. currently you are stuck with a=20
> fixed DPD timer.
>=20
> take the mobile IP binding cache state for example. the=20
> binding cache lifetime can be changed at any time by sending=20
> a BU with a different lifetime.
>=20

But, do you really see a mobile that is about to enter dormant mode
sending these messages to change the lifetime?=20

Vidya


> Vijay
>=20
>=20
> > (In the NAT case, we typically need keepalives every 30=20
> seconds, and=20
> > the endpoints can't choose any other internal since it=20
> depends on the=20
> > NAT, not the endpoints.) "
> >=20
> > Hence I believe that there is not really any concern as far as=20
> > IPsec/IKEv2 is concerned in the context of MIP6.
> >=20
> > -Raj
> >=20
> > P.s: I had to forward Pasi's note since he is not registered on the=20
> > MIP6 list
> >=20
> >=20
> > _______________________________________________
> > Mip6 mailing list
> > Mip6@ietf.org
> > https://www1.ietf.org/mailman/listinfo/mip6
>=20
>=20
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
>=20

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



From mip6-bounces@ietf.org Mon Jul 24 17:25:41 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G57vm-0003lt-53; Mon, 24 Jul 2006 17:25:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G57vk-0003lS-JM
	for mip6@ietf.org; Mon, 24 Jul 2006 17:25:36 -0400
Received: from mail1.azairenet.com ([66.92.223.4] helo=bart.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G57vj-0000yG-9S
	for mip6@ietf.org; Mon, 24 Jul 2006 17:25:36 -0400
Received: from [10.1.201.19] ([10.1.201.19]) by bart.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Mon, 24 Jul 2006 14:25:33 -0700
Message-ID: <44C53ACC.7000104@azairenet.com>
Date: Mon, 24 Jul 2006 14:25:32 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.4 (Windows/20060516)
MIME-Version: 1.0
To: "Narayanan, Vidya" <vidyan@qualcomm.com>
Subject: Re: [Mip6] Regarding the charter revision w.r.t the IPsec SA and IKEv2
References: <C24CB51D5AA800449982D9BCB90325130A15F6@NAEX13.na.qualcomm.com>
In-Reply-To: <C24CB51D5AA800449982D9BCB90325130A15F6@NAEX13.na.qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 24 Jul 2006 21:25:33.0345 (UTC)
	FILETIME=[B23CA910:01C6AF67]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Cc: mip6@ietf.org, "Eronen Pasi \(Nokia-NRC/Helsinki\)" <Pasi.Eronen@nokia.com>,
	Basavaraj Patil <basavaraj.patil@nokia.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Narayanan, Vidya wrote:
>> Basavaraj Patil wrote:
>>> In discussions with Pasi Eronen, I believe there is really nothing 
>>> specific that needs to be done w.r.t MIP6 and IKEv2 as far as 
>>> dead-peer-detection is concerned.
>>>
>>> Pasi's comment was:
>>> "
>>> When using IPsec for MIP6, there is no need to send any keepalives.
>>> IKE may do Dead Peer Detection (DPD) occasionally, but this is a 
>>> configurable parameter (just like binding lifetime) and doing DPD, 
>>> say, once every 8 hours does not seem unacceptable to me. And doing 
>>> DPD (and Binding Updates) every N hours is IMHO *MUCH* 
>> better solution 
>>> than introducing hard state (as someone already pointed out on the 
>>> list).
>> yes, the DPD timer is configurable, but it does not change 
>> dynamically based on whether the mobile node is dormant or 
>> not. the proposed extension lets you change the DPD timer on 
>> the responder dynamically. currently you are stuck with a 
>> fixed DPD timer.
>>
>> take the mobile IP binding cache state for example. the 
>> binding cache lifetime can be changed at any time by sending 
>> a BU with a different lifetime.
>>
> 
> But, do you really see a mobile that is about to enter dormant mode
> sending these messages to change the lifetime? 

why is it hard?

Vijay

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



From mip6-bounces@ietf.org Mon Jul 24 17:40:08 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G589n-0002uT-4u; Mon, 24 Jul 2006 17:40:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G589m-0002uN-BV
	for mip6@ietf.org; Mon, 24 Jul 2006 17:40:06 -0400
Received: from ithilien.qualcomm.com ([129.46.51.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G589k-0002W5-V6
	for mip6@ietf.org; Mon, 24 Jul 2006 17:40:06 -0400
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
	k6OLe2c4014074
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Mon, 24 Jul 2006 14:40:03 -0700
Received: from NAEXBR03.na.qualcomm.com (naexbr03.qualcomm.com
	[129.46.134.172])
	by crowley.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	k6OLe08p028886; Mon, 24 Jul 2006 14:40:01 -0700 (PDT)
Received: from NAEX13.na.qualcomm.com ([129.46.51.248]) by
	NAEXBR03.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 24 Jul 2006 14:40:00 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] Regarding the charter revision w.r.t the IPsec SA and IKEv2
Date: Mon, 24 Jul 2006 14:39:59 -0700
Message-ID: <C24CB51D5AA800449982D9BCB90325130A15FF@NAEX13.na.qualcomm.com>
In-Reply-To: <44C53ACC.7000104@azairenet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] Regarding the charter revision w.r.t the IPsec SA and
	IKEv2
Thread-Index: AcavZ8lCtw+MktrhTuCuRh+er4XqcwAAReMA
From: "Narayanan, Vidya" <vidyan@qualcomm.com>
To: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
X-OriginalArrivalTime: 24 Jul 2006 21:40:00.0235 (UTC)
	FILETIME=[B6F193B0:01C6AF69]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: mip6@ietf.org, "Eronen Pasi \(Nokia-NRC/Helsinki\)" <Pasi.Eronen@nokia.com>,
	Basavaraj Patil <basavaraj.patil@nokia.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

> >>
> >=20
> > But, do you really see a mobile that is about to enter dormant mode=20
> > sending these messages to change the lifetime?
>=20
> why is it hard?
>=20

Nothing is hard in software :) It seems impractical though - as I said
in one of my earlier emails, mobiles may frequently go in and out of
dormant mode and the duration of dormancy is often unpredictable. If all
timers and lifetimes relating to upper layer protocols need to be
refreshed with messages prior to entering dormant mode, it seems
unnecessarily complicated. The mobile will then have to wait for acks
and if those fail, do retransmissions, etc. Seems more of a battery
power issue to do this every time it enters dormant mode than to say
that something must be refreshed every 8 hours or so. That too, note
that there is a problem only if the mobile happens to be in dormant mode
after 8 hours when the DPD kicks in.=20

Keeping it simple seems to be sufficient - talking to some lower layer
folks, it seems to cost more to have to send a message prior to dormancy
periodically than even have to, say, redo IKEv2 every 8 hours.=20

Vidya

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



From mip6-bounces@ietf.org Mon Jul 24 17:46:03 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G58FW-0004xU-1n; Mon, 24 Jul 2006 17:46:02 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G58FU-0004xO-3V
	for mip6@ietf.org; Mon, 24 Jul 2006 17:46:00 -0400
Received: from mgw-ext13.nokia.com ([131.228.20.172])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G58FS-0003dD-JE
	for mip6@ietf.org; Mon, 24 Jul 2006 17:46:00 -0400
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
	by mgw-ext13.nokia.com (Switch-3.1.8/Switch-3.1.7) with ESMTP id
	k6OLjtgg005759; Tue, 25 Jul 2006 00:45:55 +0300
Received: from daebh102.NOE.Nokia.com ([10.241.35.112]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 25 Jul 2006 00:45:54 +0300
Received: from daebe101.NOE.Nokia.com ([10.241.35.113]) by
	daebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 24 Jul 2006 16:45:52 -0500
Received: from 172.19.244.128 ([172.19.244.128]) by daebe101.NOE.Nokia.com
	([10.241.35.113]) with Microsoft Exchange Server HTTP-DAV ; 
	Mon, 24 Jul 2006 21:45:52 +0000
User-Agent: Microsoft-Entourage/11.2.5.060620
Date: Mon, 24 Jul 2006 16:45:51 -0500
Subject: Re: [Mip6] Regarding the charter revision w.r.t the IPsec SA and IKEv2
From: Basavaraj Patil <basavaraj.patil@nokia.com>
To: ext Vijay Devarapalli <vijay.devarapalli@AzaireNet.com>
Message-ID: <C0EAA9BF.1FA4C%basavaraj.patil@nokia.com>
Thread-Topic: [Mip6] Regarding the charter revision w.r.t the IPsec SA and
	IKEv2
Thread-Index: AcavaogExk8EaBtdEduSsQARJNUNiA==
In-Reply-To: <44C52BF7.4070207@azairenet.com>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 24 Jul 2006 21:45:52.0505 (UTC)
	FILETIME=[88E9B690:01C6AF6A]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Cc: mip6@ietf.org, "Eronen Pasi \(Nokia-NRC/Helsinki\)" <Pasi.Eronen@nokia.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org




On 7/24/06 3:22 PM, "ext Vijay Devarapalli"
<vijay.devarapalli@AzaireNet.com> wrote:

> Basavaraj Patil wrote:
>> In discussions with Pasi Eronen, I believe there is really nothing specific
>> that needs to be done w.r.t MIP6 and IKEv2 as far as dead-peer-detection is
>> concerned. 
>> 
>> Pasi's comment was:
>> "
>> When using IPsec for MIP6, there is no need to send any keepalives.
>> IKE may do Dead Peer Detection (DPD) occasionally, but this is a
>> configurable parameter (just like binding lifetime) and doing DPD,
>> say, once every 8 hours does not seem unacceptable to me. And doing
>> DPD (and Binding Updates) every N hours is IMHO *MUCH* better solution
>> than introducing hard state (as someone already pointed out on the
>> list).
> 
> yes, the DPD timer is configurable, but it does not change
> dynamically based on whether the mobile node is dormant or
> not. the proposed extension lets you change the DPD timer
> on the responder dynamically. currently you are stuck with
> a fixed DPD timer.
> 

Sure... But the point is that as long as you do not have an issue of MNs
having to transition from dormant to active to do a keep-alive then you do
not need anything else. If the static timer is set to a fairly large value
then the MN can go into dormant mode and stay in such for maybe several
hours even. So I think configurable timers are sufficient.

> take the mobile IP binding cache state for example. the
> binding cache lifetime can be changed at any time by sending
> a BU with a different lifetime.

True. But I don't think the two are analogous.

-Raj

> 
> Vijay
> 
> 
>> (In the NAT case, we typically need keepalives every 30 seconds, and
>> the endpoints can't choose any other internal since it depends on the
>> NAT, not the endpoints.)
>> "
>> 
>> Hence I believe that there is not really any concern as far as IPsec/IKEv2
>> is concerned in the context of MIP6.
>> 
>> -Raj
>> 
>> P.s: I had to forward Pasi's note since he is not registered on the MIP6
>> list 
>> 
>> 
>> _______________________________________________
>> Mip6 mailing list
>> Mip6@ietf.org
>> https://www1.ietf.org/mailman/listinfo/mip6
> 


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



From mip6-bounces@ietf.org Mon Jul 24 17:46:16 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G58Fk-0005ES-NB; Mon, 24 Jul 2006 17:46:16 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G58Fj-0005EN-Cu
	for mip6@ietf.org; Mon, 24 Jul 2006 17:46:15 -0400
Received: from mail1.azairenet.com ([66.92.223.4] helo=bart.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G58Fi-0003e1-32
	for mip6@ietf.org; Mon, 24 Jul 2006 17:46:15 -0400
Received: from [10.1.201.19] ([10.1.201.19]) by bart.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Mon, 24 Jul 2006 14:46:13 -0700
Message-ID: <44C53FA4.7040708@azairenet.com>
Date: Mon, 24 Jul 2006 14:46:12 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.4 (Windows/20060516)
MIME-Version: 1.0
To: "Narayanan, Vidya" <vidyan@qualcomm.com>
Subject: Re: [Mip6] Regarding the charter revision w.r.t the IPsec SA and IKEv2
References: <C24CB51D5AA800449982D9BCB90325130A15FF@NAEX13.na.qualcomm.com>
In-Reply-To: <C24CB51D5AA800449982D9BCB90325130A15FF@NAEX13.na.qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 24 Jul 2006 21:46:13.0064 (UTC)
	FILETIME=[952AC480:01C6AF6A]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: mip6@ietf.org, "Eronen Pasi \(Nokia-NRC/Helsinki\)" <Pasi.Eronen@nokia.com>,
	Basavaraj Patil <basavaraj.patil@nokia.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

hi Vidya,

lets address Pasi's comments first. what you bring up
is a different issue.

Vijay

Narayanan, Vidya wrote:
>>> But, do you really see a mobile that is about to enter dormant mode 
>>> sending these messages to change the lifetime?
>> why is it hard?
>>
> 
> Nothing is hard in software :) It seems impractical though - as I said
> in one of my earlier emails, mobiles may frequently go in and out of
> dormant mode and the duration of dormancy is often unpredictable. If all
> timers and lifetimes relating to upper layer protocols need to be
> refreshed with messages prior to entering dormant mode, it seems
> unnecessarily complicated. The mobile will then have to wait for acks
> and if those fail, do retransmissions, etc. Seems more of a battery
> power issue to do this every time it enters dormant mode than to say
> that something must be refreshed every 8 hours or so. That too, note
> that there is a problem only if the mobile happens to be in dormant mode
> after 8 hours when the DPD kicks in. 
> 
> Keeping it simple seems to be sufficient - talking to some lower layer
> folks, it seems to cost more to have to send a message prior to dormancy
> periodically than even have to, say, redo IKEv2 every 8 hours. 
> 
> Vidya


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



From mip6-bounces@ietf.org Mon Jul 24 17:46:19 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G58Fn-0005Ia-BV; Mon, 24 Jul 2006 17:46:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G58Fm-0005IF-Sz
	for mip6@ietf.org; Mon, 24 Jul 2006 17:46:18 -0400
Received: from mgw-ext14.nokia.com ([131.228.20.173])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G58Fl-0003e9-C4
	for mip6@ietf.org; Mon, 24 Jul 2006 17:46:18 -0400
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143])
	by mgw-ext14.nokia.com (Switch-3.1.8/Switch-3.1.7) with ESMTP id
	k6OLkCtX032616; Tue, 25 Jul 2006 00:46:13 +0300
Received: from daebh102.NOE.Nokia.com ([10.241.35.112]) by
	esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 25 Jul 2006 00:46:12 +0300
Received: from daebe101.NOE.Nokia.com ([10.241.35.113]) by
	daebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 24 Jul 2006 16:46:10 -0500
Received: from 172.19.244.128 ([172.19.244.128]) by daebe101.NOE.Nokia.com
	([10.241.35.113]) with Microsoft Exchange Server HTTP-DAV ; 
	Mon, 24 Jul 2006 21:46:09 +0000
User-Agent: Microsoft-Entourage/11.2.5.060620
Date: Mon, 24 Jul 2006 16:46:09 -0500
Subject: Re: [Mip6] Regarding the charter revision w.r.t the IPsec SA and IKEv2
From: Basavaraj Patil <basavaraj.patil@nokia.com>
To: ext James Kempf <kempf@docomolabs-usa.com>, <mip6@ietf.org>
Message-ID: <C0EAA9D1.1FA4D%basavaraj.patil@nokia.com>
Thread-Topic: [Mip6] Regarding the charter revision w.r.t the IPsec SA and
	IKEv2
Thread-Index: AcavapK+0SAUuBtdEduSsQARJNUNiA==
In-Reply-To: <026401c6af62$0ca4a390$196115ac@dcml.docomolabsusa.com>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 24 Jul 2006 21:46:10.0020 (UTC)
	FILETIME=[935A4A40:01C6AF6A]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
Cc: "Eronen Pasi \(Nokia-NRC/Helsinki\)" <Pasi.Eronen@nokia.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org


Will do..

-Raj


On 7/24/06 3:45 PM, "ext James Kempf" <kempf@docomolabs-usa.com> wrote:

> Raj,
> 
> Perhaps you could convey this message to NWG?
> 
>             jak
> 
> ----- Original Message -----
> From: "Basavaraj Patil" <basavaraj.patil@nokia.com>
> To: <mip6@ietf.org>
> Cc: "Eronen Pasi (Nokia-NRC/Helsinki)" <Pasi.Eronen@nokia.com>
> Sent: Monday, July 24, 2006 12:19 PM
> Subject: [Mip6] Regarding the charter revision w.r.t the IPsec SA and IKEv2
> 
> 
>> 
>> In discussions with Pasi Eronen, I believe there is really nothing
>> specific
>> that needs to be done w.r.t MIP6 and IKEv2 as far as dead-peer-detection
>> is
>> concerned.
>> 
>> Pasi's comment was:
>> "
>> When using IPsec for MIP6, there is no need to send any keepalives.
>> IKE may do Dead Peer Detection (DPD) occasionally, but this is a
>> configurable parameter (just like binding lifetime) and doing DPD,
>> say, once every 8 hours does not seem unacceptable to me. And doing
>> DPD (and Binding Updates) every N hours is IMHO *MUCH* better solution
>> than introducing hard state (as someone already pointed out on the
>> list).
>> 
>> (In the NAT case, we typically need keepalives every 30 seconds, and
>> the endpoints can't choose any other internal since it depends on the
>> NAT, not the endpoints.)
>> "
>> 
>> Hence I believe that there is not really any concern as far as IPsec/IKEv2
>> is concerned in the context of MIP6.
>> 
>> -Raj
>> 
>> P.s: I had to forward Pasi's note since he is not registered on the MIP6
>> list
>> 
>> 
>> _______________________________________________
>> Mip6 mailing list
>> Mip6@ietf.org
>> https://www1.ietf.org/mailman/listinfo/mip6
>> 
> 
> 


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



From mip6-bounces@ietf.org Mon Jul 24 17:52:52 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G58M5-0001M8-Bn; Mon, 24 Jul 2006 17:52:49 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G58M3-0001Lv-QP
	for mip6@ietf.org; Mon, 24 Jul 2006 17:52:47 -0400
Received: from mgw-ext13.nokia.com ([131.228.20.172])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G58M2-0004Pm-B6
	for mip6@ietf.org; Mon, 24 Jul 2006 17:52:47 -0400
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143])
	by mgw-ext13.nokia.com (Switch-3.1.8/Switch-3.1.7) with ESMTP id
	k6OLqgx0010079; Tue, 25 Jul 2006 00:52:42 +0300
Received: from daebh101.NOE.Nokia.com ([10.241.35.111]) by
	esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 25 Jul 2006 00:52:42 +0300
Received: from daebe101.NOE.Nokia.com ([10.241.35.113]) by
	daebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 24 Jul 2006 16:52:38 -0500
Received: from 172.19.244.128 ([172.19.244.128]) by daebe101.NOE.Nokia.com
	([10.241.35.113]) with Microsoft Exchange Server HTTP-DAV ; 
	Mon, 24 Jul 2006 21:52:37 +0000
User-Agent: Microsoft-Entourage/11.2.5.060620
Date: Mon, 24 Jul 2006 16:52:36 -0500
Subject: Re: [Mip6] Regarding the charter revision w.r.t the IPsec SA and IKEv2
From: Basavaraj Patil <basavaraj.patil@nokia.com>
To: "ext Narayanan, Vidya" <vidyan@qualcomm.com>,
	Vijay Devarapalli <vijay.devarapalli@azairenet.com>
Message-ID: <C0EAAB54.1FA5B%basavaraj.patil@nokia.com>
Thread-Topic: [Mip6] Regarding the charter revision w.r.t the IPsec SA and
	IKEv2
Thread-Index: AcavZ8lCtw+MktrhTuCuRh+er4XqcwAAReMAAACmJ9M=
In-Reply-To: <C24CB51D5AA800449982D9BCB90325130A15FF@NAEX13.na.qualcomm.com>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 24 Jul 2006 21:52:38.0122 (UTC)
	FILETIME=[7AADF4A0:01C6AF6B]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Cc: mip6@ietf.org, "Eronen Pasi \(Nokia-NRC/Helsinki\)" <Pasi.Eronen@nokia.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org


I agree with Vidya. There is not an explicit reason to change the timer just
before the MN decides that it is going to transition to dormant mode. The
concern here is primarily about battery usage and I think that as long as
the IKEv2 timer is configured to a fairly high value, it will not be an
issue.

-Raj


On 7/24/06 4:39 PM, "ext Narayanan, Vidya" <vidyan@qualcomm.com> wrote:

>>>> 
>>> 
>>> But, do you really see a mobile that is about to enter dormant mode
>>> sending these messages to change the lifetime?
>> 
>> why is it hard?
>> 
> 
> Nothing is hard in software :) It seems impractical though - as I said
> in one of my earlier emails, mobiles may frequently go in and out of
> dormant mode and the duration of dormancy is often unpredictable. If all
> timers and lifetimes relating to upper layer protocols need to be
> refreshed with messages prior to entering dormant mode, it seems
> unnecessarily complicated. The mobile will then have to wait for acks
> and if those fail, do retransmissions, etc. Seems more of a battery
> power issue to do this every time it enters dormant mode than to say
> that something must be refreshed every 8 hours or so. That too, note
> that there is a problem only if the mobile happens to be in dormant mode
> after 8 hours when the DPD kicks in.
> 
> Keeping it simple seems to be sufficient - talking to some lower layer
> folks, it seems to cost more to have to send a message prior to dormancy
> periodically than even have to, say, redo IKEv2 every 8 hours.
> 
> Vidya


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



From mip6-bounces@ietf.org Mon Jul 24 17:59:06 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G58S9-0004XO-S8; Mon, 24 Jul 2006 17:59:05 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G58S8-0004XH-Cs
	for mip6@ietf.org; Mon, 24 Jul 2006 17:59:04 -0400
Received: from mgw-ext13.nokia.com ([131.228.20.172])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G58S6-000509-Pv
	for mip6@ietf.org; Mon, 24 Jul 2006 17:59:04 -0400
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145])
	by mgw-ext13.nokia.com (Switch-3.1.8/Switch-3.1.7) with ESMTP id
	k6OLwuIk013019; Tue, 25 Jul 2006 00:58:59 +0300
Received: from daebh102.NOE.Nokia.com ([10.241.35.112]) by
	esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 25 Jul 2006 00:58:58 +0300
Received: from daebe101.NOE.Nokia.com ([10.241.35.113]) by
	daebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 24 Jul 2006 16:58:55 -0500
Received: from 172.19.244.128 ([172.19.244.128]) by daebe101.NOE.Nokia.com
	([10.241.35.113]) with Microsoft Exchange Server HTTP-DAV ; 
	Mon, 24 Jul 2006 21:58:55 +0000
User-Agent: Microsoft-Entourage/11.2.5.060620
Date: Mon, 24 Jul 2006 16:58:54 -0500
Subject: Re: [Mip6] Regarding the charter revision w.r.t the IPsec SA and IKEv2
From: Basavaraj Patil <basavaraj.patil@nokia.com>
To: ext Vijay Devarapalli <vijay.devarapalli@AzaireNet.com>
Message-ID: <C0EAACCE.1FA63%basavaraj.patil@nokia.com>
Thread-Topic: [Mip6] Regarding the charter revision w.r.t the IPsec SA and
	IKEv2
Thread-Index: AcavbFq4mSOf2htfEduSsQARJNUNiA==
In-Reply-To: <44C5404C.3040203@azairenet.com>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 24 Jul 2006 21:58:55.0656 (UTC)
	FILETIME=[5BB51280:01C6AF6C]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Cc: mip6@ietf.org, "Eronen Pasi \(Nokia-NRC/Helsinki\)" <Pasi.Eronen@nokia.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org




On 7/24/06 4:49 PM, "ext Vijay Devarapalli"
<vijay.devarapalli@AzaireNet.com> wrote:

.
> 
>>> take the mobile IP binding cache state for example. the
>>> binding cache lifetime can be changed at any time by sending
>>> a BU with a different lifetime.
>> 
>> True. But I don't think the two are analogous.
> 
> they are. the lifetime for a binding cache entry at the HA
> can dynamically change based on signaling messages from the
> MN. the lifetime for IPsec SA state does not today because
> there is no message from the MN negotiating the lifetime.
> 

So in what instances would an MN update the binding lifetime at the HA? Do
you believe that an MN would do this on a random basis. Or more so when the
MN triggers some threshold associated with the lifetime.
The MN can send BUs to the HA and change the lifetime at any time. But I
don't think an MN would do this just because for example it is going into a
dormant mode. So what would be the benefit of having the ability to change
the IPsec SA lifetime on a dynamic basis? An MN does not really know as to
how long it is going to be dormant. So if the lifetime is configured to a
large enough value, that is good enough.

-Raj

> Vijay


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



From mip6-bounces@ietf.org Mon Jul 24 18:04:27 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G58XK-0006ME-QN; Mon, 24 Jul 2006 18:04:26 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G58XJ-0006M3-Ad
	for mip6@ietf.org; Mon, 24 Jul 2006 18:04:25 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G58XJ-0005bD-8j
	for mip6@ietf.org; Mon, 24 Jul 2006 18:04:25 -0400
Received: from mail1.azairenet.com ([66.92.223.4] helo=bart.corp.azairenet.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1G58Ia-00025i-E4
	for mip6@ietf.org; Mon, 24 Jul 2006 17:49:13 -0400
Received: from [10.1.201.19] ([10.1.201.19]) by bart.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Mon, 24 Jul 2006 14:49:01 -0700
Message-ID: <44C5404C.3040203@azairenet.com>
Date: Mon, 24 Jul 2006 14:49:00 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.4 (Windows/20060516)
MIME-Version: 1.0
To: Basavaraj Patil <basavaraj.patil@nokia.com>
Subject: Re: [Mip6] Regarding the charter revision w.r.t the IPsec SA and IKEv2
References: <C0EAA9BF.1FA4C%basavaraj.patil@nokia.com>
In-Reply-To: <C0EAA9BF.1FA4C%basavaraj.patil@nokia.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 24 Jul 2006 21:49:01.0566 (UTC)
	FILETIME=[F99A21E0:01C6AF6A]
X-Spam-Score: -2.2 (--)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Cc: mip6@ietf.org, "Eronen Pasi \(Nokia-NRC/Helsinki\)" <Pasi.Eronen@nokia.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Basavaraj Patil wrote:
> 
> 
> On 7/24/06 3:22 PM, "ext Vijay Devarapalli"
> <vijay.devarapalli@AzaireNet.com> wrote:
> 
>> Basavaraj Patil wrote:
>>> In discussions with Pasi Eronen, I believe there is really nothing specific
>>> that needs to be done w.r.t MIP6 and IKEv2 as far as dead-peer-detection is
>>> concerned. 
>>>
>>> Pasi's comment was:
>>> "
>>> When using IPsec for MIP6, there is no need to send any keepalives.
>>> IKE may do Dead Peer Detection (DPD) occasionally, but this is a
>>> configurable parameter (just like binding lifetime) and doing DPD,
>>> say, once every 8 hours does not seem unacceptable to me. And doing
>>> DPD (and Binding Updates) every N hours is IMHO *MUCH* better solution
>>> than introducing hard state (as someone already pointed out on the
>>> list).
>> yes, the DPD timer is configurable, but it does not change
>> dynamically based on whether the mobile node is dormant or
>> not. the proposed extension lets you change the DPD timer
>> on the responder dynamically. currently you are stuck with
>> a fixed DPD timer.
>>
> 
> Sure... But the point is that as long as you do not have an issue of MNs
> having to transition from dormant to active to do a keep-alive then you do
> not need anything else. If the static timer is set to a fairly large value
> then the MN can go into dormant mode and stay in such for maybe several
> hours even. So I think configurable timers are sufficient.

having a large DPD timer has its negatives. we don't want
to do that. its better if DPD is done more frequently.

>> take the mobile IP binding cache state for example. the
>> binding cache lifetime can be changed at any time by sending
>> a BU with a different lifetime.
> 
> True. But I don't think the two are analogous.

they are. the lifetime for a binding cache entry at the HA
can dynamically change based on signaling messages from the
MN. the lifetime for IPsec SA state does not today because
there is no message from the MN negotiating the lifetime.

Vijay

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



From mip6-bounces@ietf.org Mon Jul 24 18:37:01 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G592q-0004iA-B1; Mon, 24 Jul 2006 18:37:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G592p-0004i4-1G
	for mip6@ietf.org; Mon, 24 Jul 2006 18:36:59 -0400
Received: from ithilien.qualcomm.com ([129.46.51.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G592m-0000ry-Lf
	for mip6@ietf.org; Mon, 24 Jul 2006 18:36:59 -0400
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
	k6OMar2A023810
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Mon, 24 Jul 2006 15:36:54 -0700
Received: from NAEXBR03.na.qualcomm.com (naexbr03.qualcomm.com
	[129.46.134.172])
	by magus.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id k6OMaq0j017844; 
	Mon, 24 Jul 2006 15:36:53 -0700 (PDT)
Received: from NAEX13.na.qualcomm.com ([129.46.51.248]) by
	NAEXBR03.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 24 Jul 2006 15:36:52 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] Regarding the charter revision w.r.t the IPsec SA and IKEv2
Date: Mon, 24 Jul 2006 15:36:51 -0700
Message-ID: <C24CB51D5AA800449982D9BCB90325130A1625@NAEX13.na.qualcomm.com>
In-Reply-To: <44C5404C.3040203@azairenet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] Regarding the charter revision w.r.t the IPsec SA and
	IKEv2
Thread-Index: Acavb5oTEE9X8ihmRIaBgcXnHEPqVAAAYyIQ
From: "Narayanan, Vidya" <vidyan@qualcomm.com>
To: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>,
	"Basavaraj Patil" <basavaraj.patil@nokia.com>
X-OriginalArrivalTime: 24 Jul 2006 22:36:52.0699 (UTC)
	FILETIME=[A8EE42B0:01C6AF71]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Cc: mip6@ietf.org, "Eronen Pasi \(Nokia-NRC/Helsinki\)" <Pasi.Eronen@nokia.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org


<snip>

> >=20
> > Sure... But the point is that as long as you do not have an=20
> issue of=20
> > MNs having to transition from dormant to active to do a keep-alive=20
> > then you do not need anything else. If the static timer is set to a=20
> > fairly large value then the MN can go into dormant mode and stay in=20
> > such for maybe several hours even. So I think configurable=20
> timers are sufficient.
>=20
> having a large DPD timer has its negatives. we don't want to=20
> do that. its better if DPD is done more frequently.
>=20

Sure, it is a tradeoff. However, I still see this as a policy issue.=20

> >> take the mobile IP binding cache state for example. the=20
> binding cache=20
> >> lifetime can be changed at any time by sending a BU with a=20
> different=20
> >> lifetime.
> >=20
> > True. But I don't think the two are analogous.
>=20
> they are. the lifetime for a binding cache entry at the HA=20
> can dynamically change based on signaling messages from the=20
> MN. the lifetime for IPsec SA state does not today because=20
> there is no message from the MN negotiating the lifetime.
>=20

When would you imagine the MN sending such messages to change the
lifetime? Sending these messages triggered by events such as dormant
mode have other significant problems. Also, what does it really mean
that an MN requested a certain lifetime in IKEv2? If the HA is short in
resources, it is going to purge that SA, period. Alternately, you can
have a policy to say that as long as the HA has resources, the lifetime
of the SA is fairly large.=20

Vidya=20

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



From mip6-bounces@ietf.org Tue Jul 25 04:41:12 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G5ITT-0007NE-30; Tue, 25 Jul 2006 04:41:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G5ITR-0007N2-6r
	for mip6@ietf.org; Tue, 25 Jul 2006 04:41:05 -0400
Received: from cluster-d.mailcontrol.com ([217.69.20.190])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G5ITP-0007d8-LU
	for mip6@ietf.org; Tue, 25 Jul 2006 04:41:05 -0400
Received: from rly37d.srv.mailcontrol.com (localhost.localdomain [127.0.0.1])
	by rly37d.srv.mailcontrol.com (MailControl) with ESMTP id
	k6P8f0ut028596
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <mip6@ietf.org>; Tue, 25 Jul 2006 09:41:02 +0100
Received: from submission.mailcontrol.com (submission.mailcontrol.com
	[212.158.48.250])
	by rly37d.srv.mailcontrol.com (MailControl) id k6P8enPX027909
	for mip6@ietf.org; Tue, 25 Jul 2006 09:40:49 +0100
Received: from hhe500-02.hbg.de.pan.eu (gate.eu.panasonic.com [194.173.20.12])
	by rly37d-eth0.srv.mailcontrol.com (envelope-sender
	Kilian.Weniger@eu.panasonic.com) (MIMEDefang) with ESMTP id
	k6P8emaV027883; Tue, 25 Jul 2006 09:40:49 +0100 (BST)
Received: from eundadmi01.pan.eu(10.100.96.64) by hhe500-02.hbg.de.pan.eu via
	smtp id 4e7d_019d6b94_1bb4_11db_8ac9_0030482aac25;
	Tue, 25 Jul 2006 10:03:06 +0200
Received: from VPN-MRelay-01.PRDCG.Panasonic.de ([10.100.176.55])
	by eundadmi01.pan.eu (Lotus Domino Release 6.5.4FP3)
	with ESMTP id 2006072510404508-116500 ;
	Tue, 25 Jul 2006 10:40:45 +0200 
X-Spam-Status: No, hits=0.0 required=6.5
	tests=ALL_TRUSTED: -2.867,AWL: 0.677,BAYES_00: -1.665,
	SARE_RECV_ADDR: 0.027
X-Spam-Level: 
Received: from localhost ([127.0.0.1]) by VPN-MRelay-01.PRDCG.Panasonic.de;
	Tue, 25 Jul 2006 10:44:26 +0200
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.5
Subject: RE: [Mip6] New charter item: HA assignment
In-reply-to: <44C502D8.3020100@azairenet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] New charter item: HA assignment
Thread-Index: AcavRprv6Z90Xo6xSAy2E6cOeDSzWAAeZ/1Q
To: "Vijay Devarapalli" <vijay.devarapalli@AzaireNet.com>
Message-ID: <4D2F935F08D41A4C8866693F4F0D7C4FD4505A@lan-ex-01.panasonic.de>
Date: Tue, 25 Jul 2006 10:40:37 +0200
From: "Kilian Weniger" <Kilian.Weniger@eu.panasonic.com>
Content-class: urn:content-classes:message
Content-Type: text/plain;
	charset="us-ascii"
X-Scanned-By: MailControl A-07-00-10 (www.mailcontrol.com) on 10.68.1.147
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 2ed806e2f53ff1a061ad4f97e00345ac
Cc: mip6@ietf.org, James Kempf <kempf@docomolabs-usa.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi Vijay,=20

> -----Original Message-----
> From: Vijay Devarapalli [mailto:vijay.devarapalli@AzaireNet.com]=20
> Sent: Montag, 24. Juli 2006 19:27
> To: Kilian Weniger
> Cc: James Kempf; mip6@ietf.org
> Subject: Re: [Mip6] New charter item: HA assignment
>=20
> Kilian Weniger wrote:
>=20
> > However, the problem depends on how the initial HA is selected.
> > Anycasting can be used to prevent that new MNs select the=20
> same initial
> > HA. For instance, the IKE_SA_INIT can be anycasted.=20
>=20
> is there another instance of using anycast for load balancing.
> just curious.

Maybe not for fine-grained load balancing, but for coarse-grained load
balancing or load distribution.=20
draft-ietf-grow-anycast-04.txt says:

  "Load-balancing between Anycast Nodes is typically difficult to
   achieve (load distribution between nodes is generally unbalanced in
   terms of request and traffic load).  Distribution of load between
   nodes for the purposes of reliability, and coarse-grained
   distribution of load for the purposes of making popular services
   scalable can often be achieved, however."

The draft also states load distribution and DoS resilience as objective
for anycasting:

  "1.  Coarse ("unbalanced") distribution of load across nodes, to allow
       infrastructure to scale to increased numbers of queries and to
       accommodate transient query peaks;

   2.  Mitigation of non-distributed denial of service attacks by
       localising damage to single anycast nodes;"

Anyhow, in my proposal the IKE_SA_INIT anycasting is not primarily for
load balancing, but for load distribution and reliability. The actual
load balancing can be done by forwarding the IKE_SA_INIT by the receiver
HA to a specific HA.=20

>=20
> > But if this is done,
> > you can easily get rid of the unnecessary SA establishment and the
> > switch message by requiring the receiver HA to forward the=20
> IKE_SA_INIT
> > to a MN-specific and low-loaded HA (see
>=20
> how do you do this? you would still need a HA-to-HA protocol to
> forward the IKE_SA_INIT message to another HA. when you send a
> message to an anycast address routing decides which HA receives
> the message.
=20
Yes, you would need HA-to-HA communication.

The HA receiving the anycast IKE_SA_INIT would forward it to an HA that
is able to serve the MN and that is not overloaded. The forwarding could
be done by encapsulating the IKE_SA_INIT (in new message or
IP-in-IP/Ipsec SA).

Note that it is assumed that all HAs know or can determine the load of
other HAs on the link and that they know or can determine which HA(s)
are able to serve a specific MN (pre-configured rules or by querying a
server such as AAA). How this is done is TBD, but I guess this is needed
for the HA switch solution as well.


> I have seen anycast used to direct a user to the "nearest" server.
> "nearest" means nearest by routing hops. when all the HAs on the
> same link, I wonder if anycast gets any load balancing at all.
>=20

There are multiple possible techniques to deploy anycast in such
scenario, some of them might be applicable.=20
RFC1546 describes one that is based on ARP:=20

  "On a shared media network, such as an Ethernet and or Token Ring, it
   must be possible to transmit an anycast datagram to a server also on
   the same network without consulting a (possibly non-existent) router.
   There are at least two ways this can be done.

   One approach is to ARP for the anycast address.  Servers which
   support the anycast address can reply to the ARP request, and the
   sending host can transmit to the first server that responds.  This
   approach is reminiscent of the ARP hack (RFC 1027) and like the ARP
   hack, requires ARP cache timeouts for the anycast addresses be kept
   small (around 1 minute), so that if an anycast server goes down,
   hosts will promptly flush the ARP entry and query for other servers
   supporting the anycast address."

draft-ietf-grow-anycast-04.txt mentiones hash-based methods for
*equal-cost paths*:

  "...applying equal-cost
   multi-path (ECMP) selection algorithms which cause a single node to
   be selected for a single multi-packet transaction.  For an example of
   the use of hash-based ECMP selection in anycast service distribution,
   see [ISC-TN-2004-1].

  "ther ECMP selection algorithms are commonly available, including
   those in which packets from the same flow are not guaranteed to be
   routed towards the same destination.  ECMP algorithms which select a
   route on a per-packet basis rather than per-flow are commonly
   referred to as performing "Per Packet Load Balancing" (PPLB)."


-Kilian


> Vijay
>=20
> > draft-dupont-ikev2-haassign-01.txt for details).=20
>=20
>=20
>=20
>=20
>=20
>=20
> >=20
> > -Kilian
> >=20
> >>             jak
> >>
> >>
> >>
> >>
> >> _______________________________________________
> >> Mip6 mailing list
> >> Mip6@ietf.org
> >> https://www1.ietf.org/mailman/listinfo/mip6
> >>
> >>
> >=20
> >=20
> > _______________________________________________
> > Mip6 mailing list
> > Mip6@ietf.org
> > https://www1.ietf.org/mailman/listinfo/mip6
>=20
>=20
>=20


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



From mip6-bounces@ietf.org Tue Jul 25 04:50:01 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G5Ic4-0002yl-H3; Tue, 25 Jul 2006 04:50:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G5Ic3-0002yg-Q0
	for mip6@ietf.org; Tue, 25 Jul 2006 04:49:59 -0400
Received: from cluster-d.mailcontrol.com ([217.69.20.190])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G5Ic3-0001o8-8g
	for mip6@ietf.org; Tue, 25 Jul 2006 04:49:59 -0400
Received: from rly36d.srv.mailcontrol.com (localhost.localdomain [127.0.0.1])
	by rly36d.srv.mailcontrol.com (MailControl) with ESMTP id
	k6P8nhRL020670
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <mip6@ietf.org>; Tue, 25 Jul 2006 09:49:52 +0100
Received: from submission.mailcontrol.com (submission.mailcontrol.com
	[212.158.48.250])
	by rly36d.srv.mailcontrol.com (MailControl) id k6P8mk4D016523
	for mip6@ietf.org; Tue, 25 Jul 2006 09:48:46 +0100
Received: from hhe500-02.hbg.de.pan.eu (gate.eu.panasonic.com [194.173.20.12])
	by rly36d-eth0.srv.mailcontrol.com (envelope-sender
	Kilian.Weniger@eu.panasonic.com) (MIMEDefang) with ESMTP id
	k6P8mbCr015851; Tue, 25 Jul 2006 09:48:46 +0100 (BST)
Received: from eundadmi01.pan.eu(10.100.96.64) by hhe500-02.hbg.de.pan.eu via
	smtp id 4eb6_19685346_1bb5_11db_9768_0030482aac25;
	Tue, 25 Jul 2006 10:10:56 +0200
Received: from VPN-MRelay-01.PRDCG.Panasonic.de ([10.100.176.55])
	by eundadmi01.pan.eu (Lotus Domino Release 6.5.4FP3)
	with ESMTP id 2006072510483279-117221 ;
	Tue, 25 Jul 2006 10:48:32 +0200 
X-Spam-Status: No, hits=0.0 required=6.5
	tests=ALL_TRUSTED: -2.867,AWL: 0.673,BAYES_00: -1.665,
	SARE_RECV_ADDR: 0.027
X-Spam-Level: 
Received: from localhost ([127.0.0.1]) by VPN-MRelay-01.PRDCG.Panasonic.de;
	Tue, 25 Jul 2006 10:52:14 +0200
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.5
Subject: RE: [Mip6] New charter item: HA assignment
In-reply-to: <44C51CAB.6030704@azairenet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] New charter item: HA assignment
Thread-Index: AcavVgETZMuUnWpdTyikVRj0a8kb0QAcCbkw
To: "Vijay Devarapalli" <vijay.devarapalli@AzaireNet.com>,
	"James Kempf" <kempf@docomolabs-usa.com>
Message-ID: <4D2F935F08D41A4C8866693F4F0D7C4FD4505C@lan-ex-01.panasonic.de>
Date: Tue, 25 Jul 2006 10:48:26 +0200
From: "Kilian Weniger" <Kilian.Weniger@eu.panasonic.com>
Content-class: urn:content-classes:message
Content-Type: text/plain;
	charset="us-ascii"
X-Scanned-By: MailControl A-07-00-11 (www.mailcontrol.com) on 10.68.1.146
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 42e3ed3f10a1d8bef690f09da16f507a
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Right, I assumed a more or less stable anycast group. BTW, I'm not
against the DNS solution per se. It may make sense to combine it with
other methods, e.g., if anycast is used, different anycast HA addresses
could be obtained from DNS for different mobility services
("_mip6._ipv6.example.com" for MIPv6, "_nemo._ipv6.example.com" for
NEMO, "_dsmip6._ipv6.example.com" for DSMIPv6 etc.).

-Kilian

> -----Original Message-----
> From: Vijay Devarapalli [mailto:vijay.devarapalli@AzaireNet.com]=20
> Sent: Montag, 24. Juli 2006 21:17
> To: James Kempf
> Cc: Kilian Weniger; mip6@ietf.org
> Subject: Re: [Mip6] New charter item: HA assignment
>=20
> James Kempf wrote:
> > I thought the whole point of  the anycast proposal  and Kilian and=20
> > Jean-Marie's argumet against DNS was load balancing and that DNS is=20
> > insufficient because it does not provide fast enough=20
> dynamic update. If=20
> > that is the case, then I would think that the ability to=20
> quickly add and=20
> > remove addresses from the anycast group would be crucial to=20
> removing HAs=20
> > that are loading and adding new ones that aren't.
>=20
> load balancing does not necessarily mean removing/adding a HA
> from/to the list of HAs. I think it is more about directing the
> users to the right HA. you can have a pretty stable anycast
> group and still direct the MN to a specific HA.
>=20
> Vijay
>=20
> >=20
> >=20
> >            jak
> >=20
> > ----- Original Message ----- From: "Vijay Devarapalli"=20
> > <vijay.devarapalli@azairenet.com>
> > To: "James Kempf" <kempf@docomolabs-usa.com>
> > Cc: "Kilian Weniger" <Kilian.Weniger@eu.panasonic.com>;=20
> <mip6@ietf.org>
> > Sent: Monday, July 24, 2006 12:08 PM
> > Subject: Re: [Mip6] New charter item: HA assignment
> >=20
> >=20
> >> hi Jim,
> >>
> >> I think manual configuration is sufficient in this case. it is
> >> not too often that home agents get added to or deleted from the
> >> the anycast group.
> >>
> >> Vijay
> >>
> >> James Kempf wrote:
> >>> The other problem with this solution is that there is=20
> still no secure=20
> >>> way for a collection of unicast server addresses to get=20
> assigned to=20
> >>> an anycast address, except for static configuration. So=20
> how would the=20
> >>> operator be able to add HAs to the anycast address?
> >>>
> >>> At least, with the DNS solution, the update of the DNS can be=20
> >>> automated using dynamic DNS.
> >>>
> >>>                        jak
> >>>
> >>> ----- Original Message ----- From: "Vijay Devarapalli"=20
> >>> <vijay.devarapalli@azairenet.com>
> >>> To: "Kilian Weniger" <Kilian.Weniger@eu.panasonic.com>
> >>> Cc: "James Kempf" <kempf@docomolabs-usa.com>; <mip6@ietf.org>
> >>> Sent: Monday, July 24, 2006 10:26 AM
> >>> Subject: Re: [Mip6] New charter item: HA assignment
> >>>
> >>>
> >>>> Kilian Weniger wrote:
> >>>>
> >>>>> However, the problem depends on how the initial HA is selected.
> >>>>> Anycasting can be used to prevent that new MNs select=20
> the same initial
> >>>>> HA. For instance, the IKE_SA_INIT can be anycasted.
> >>>>
> >>>> is there another instance of using anycast for load balancing.
> >>>> just curious.
> >>>>
> >>>>> But if this is done,
> >>>>> you can easily get rid of the unnecessary SA=20
> establishment and the
> >>>>> switch message by requiring the receiver HA to forward=20
> the IKE_SA_INIT
> >>>>> to a MN-specific and low-loaded HA (see
> >>>>
> >>>> how do you do this? you would still need a HA-to-HA protocol to
> >>>> forward the IKE_SA_INIT message to another HA. when you send a
> >>>> message to an anycast address routing decides which HA receives
> >>>> the message.
> >>>>
> >>>> I have seen anycast used to direct a user to the=20
> "nearest" server.
> >>>> "nearest" means nearest by routing hops. when all the HAs on the
> >>>> same link, I wonder if anycast gets any load balancing at all.
> >>>>
> >>>> Vijay
> >>>>
> >>>>> draft-dupont-ikev2-haassign-01.txt for details).
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>>
> >>>>> -Kilian
> >>>>>
> >>>>>>             jak
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> _______________________________________________
> >>>>>> Mip6 mailing list
> >>>>>> Mip6@ietf.org
> >>>>>> https://www1.ietf.org/mailman/listinfo/mip6
> >>>>>>
> >>>>>>
> >>>>>
> >>>>>
> >>>>> _______________________________________________
> >>>>> Mip6 mailing list
> >>>>> Mip6@ietf.org
> >>>>> https://www1.ietf.org/mailman/listinfo/mip6
> >>>>
> >>>>
> >>>
> >>>
> >>
> >>
> >=20
> >=20
>=20
>=20
>=20


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



From mip6-bounces@ietf.org Tue Jul 25 09:59:32 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G5NRU-0002df-A5; Tue, 25 Jul 2006 09:59:24 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G5NRT-0002dX-3n
	for mip6@ietf.org; Tue, 25 Jul 2006 09:59:23 -0400
Received: from [2001:660:7301:3192:211:43ff:fea3:7e4b]
	(helo=laposte.rennes.enst-bretagne.fr)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G5NRQ-00070x-9v
	for mip6@ietf.org; Tue, 25 Jul 2006 09:59:23 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by laposte.rennes.enst-bretagne.fr (8.13.4/8.13.4/2004.10.03) with
	ESMTP id k6PDxCDP009293; Tue, 25 Jul 2006 15:59:12 +0200
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[192.44.77.29])
	by laposte.rennes.enst-bretagne.fr (8.13.4/8.13.4/2004.09.01) with
	ESMTP id k6PDv2DY009084; Tue, 25 Jul 2006 15:57:02 +0200
Received: from givry.rennes.enst-bretagne.fr
	(localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.13.1/8.13.1) with ESMTP id
	k6PDv1xT065992; Tue, 25 Jul 2006 15:57:01 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200607251357.k6PDv1xT065992@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@point6.net>
To: "Gerardo Giaretta" <gerardo.giaretta@gmail.com>
Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA? 
In-reply-to: Your message of Wed, 19 Jul 2006 10:38:55 +0200.
	<eaa74a7e0607190138j79868bd3u48371dbcb8673fcb@mail.gmail.com> 
Date: Tue, 25 Jul 2006 15:57:01 +0200
X-Virus-Scanned: amavisd-new at enst-bretagne.fr
X-Spam-Score: -2.8 (--)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Cc: mip6@ietf.org, James Kempf <kempf@docomolabs-usa.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

I've not so arbitrary pick up one of the messages to answer...

IMHO there are three issues to address: DPD, SA lifetimes, BCE.

About Dead Peer Detection, RFC 4306 is very flexible. I believe there is
no reason in this case to have each peer polling the other, i.e., one sends
polls and says its peer is dead when it doesn't receive a small number of
acks in a row, the other says its peer is dead when it doesn't receive a
small (perhaps a bit larger) number of polls in a row.
We have already in practice the HA in a passive mode, i.e., it is *never*
the IKE initiator. To make the MN the active polling side and the HA the
passive one seems the right way to go (but I'll come back about DPD).

Security Association lifetimes: IKEv1 can negociate them but this is a
major operational issue to get this right. IKEv2 relies on the config
so the idea should be to have a good config. BTW at least the IKE SA
lifetime should be in the PAD so there is no issue to put a large value
(i.e., almost infinite) on a HA for MNs but not for other HAs.
Again we need only rekeys initiated by one side, of course this side
should be the MN, i.e., HAs should use almost infinite lifetimes.

What is the real limit? The only thing which really requires a rekey
is the sequence number exhaution but smaller sequence numbers are on
32 bits: I can't see an issue for low traffic SAs, i.e., the IKE SA,
the BU/BA transport SA, the HOTI/HOT SA, etc. The only problem can
be with a payload SA when the MN should actively rekey in time, so
IMHO the only case we can be in trouble (but in fact independtly of IPsec)
is a dormant node receiving a lot of protected traffic...

BCE: even very unreasonable BCE lifetimes are a bit small (a few days,
16 bit value in 4 second unit). If we add something IMHO this is the first
place as the MIPv6 code can really take benefit to know the node is dormant.

Come back to DPD: a passive DPD should have a good way to distinguish
between a dormant and a dead node so I propose to add a new "private
status" notification in DPD poll with in the data the delay to the next
poll in second. So the passive DPD code becomes very easy to implement,
and a MN going to the dormant node has only to send a poll with a large
delay and wait for the ack. BTW this needs only a document, and an
experimental RFC if we prefer a "IANA status" type.

Regards

Francis.Dupont@point6.net

PS: about RFC 4285, the whole story was laziness vs. security
(or if you prefer cost vs. security)...

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



From mip6-bounces@ietf.org Tue Jul 25 12:34:27 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G5PrS-0004lk-V5; Tue, 25 Jul 2006 12:34:22 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G5PrR-0004lf-M6
	for mip6@ietf.org; Tue, 25 Jul 2006 12:34:21 -0400
Received: from key1.docomolabs-usa.com ([216.98.102.225]
	helo=fridge.docomolabs-usa.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G5PrQ-0003nA-7Y
	for mip6@ietf.org; Tue, 25 Jul 2006 12:34:21 -0400
Message-ID: <04b901c6b008$7bb452c0$196115ac@dcml.docomolabsusa.com>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Vijay Devarapalli" <vijay.devarapalli@AzaireNet.com>,
	"Kilian Weniger" <Kilian.Weniger@eu.panasonic.com>
References: <4D2F935F08D41A4C8866693F4F0D7C4FD4505A@lan-ex-01.panasonic.de>
Subject: Re: [Mip6] New charter item: HA assignment
Date: Tue, 25 Jul 2006 09:36:30 -0700
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Yes, you would need HA-to-HA communication.

The HA receiving the anycast IKE_SA_INIT would forward it to an HA that
is able to serve the MN and that is not overloaded. The forwarding could
be done by encapsulating the IKE_SA_INIT (in new message or
IP-in-IP/Ipsec SA).

Note that it is assumed that all HAs know or can determine the load of
other HAs on the link and that they know or can determine which HA(s)
are able to serve a specific MN (pre-configured rules or by querying a
server such as AAA). How this is done is TBD, but I guess this is needed
for the HA switch solution as well.

jak>> How would this be any better than having the MN first contact the HA 
and receiving a rejection, then having the MN contact another HA? It seems 
to me like this would distribute the load of forwarding to the MN, so the 
first HA - which might already be close to its load limit - wouldn't have to 
do any extra work. Just fire off a simple rejection of the IKE transaction.

jak>> It also wouldn't require an additional HA-HA load balancing protocol.


> I have seen anycast used to direct a user to the "nearest" server.
> "nearest" means nearest by routing hops. when all the HAs on the
> same link, I wonder if anycast gets any load balancing at all.
>

There are multiple possible techniques to deploy anycast in such
scenario, some of them might be applicable.
RFC1546 describes one that is based on ARP:

  "On a shared media network, such as an Ethernet and or Token Ring, it
   must be possible to transmit an anycast datagram to a server also on
   the same network without consulting a (possibly non-existent) router.
   There are at least two ways this can be done.

   One approach is to ARP for the anycast address.  Servers which
   support the anycast address can reply to the ARP request, and the
   sending host can transmit to the first server that responds.  This
   approach is reminiscent of the ARP hack (RFC 1027) and like the ARP
   hack, requires ARP cache timeouts for the anycast addresses be kept
   small (around 1 minute), so that if an anycast server goes down,
   hosts will promptly flush the ARP entry and query for other servers
   supporting the anycast address."

draft-ietf-grow-anycast-04.txt mentiones hash-based methods for
*equal-cost paths*:

  "...applying equal-cost
   multi-path (ECMP) selection algorithms which cause a single node to
   be selected for a single multi-packet transaction.  For an example of
   the use of hash-based ECMP selection in anycast service distribution,
   see [ISC-TN-2004-1].

  "ther ECMP selection algorithms are commonly available, including
   those in which packets from the same flow are not guaranteed to be
   routed towards the same destination.  ECMP algorithms which select a
   route on a per-packet basis rather than per-flow are commonly
   referred to as performing "Per Packet Load Balancing" (PPLB)."


jak>> I don't see any routing based metric as being particularly useful in 
this case. The figure of merit in terms of which server gets traffic isn't 
primarily going to be routing. It might be load, or some other factor, like 
having particular HAs serve VoIP v.s. best effort traffic.

                 jak 



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



From mip6-bounces@ietf.org Tue Jul 25 12:36:30 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G5PtW-0005xq-6t; Tue, 25 Jul 2006 12:36:30 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G5PtU-0005uA-Ez
	for mip6@ietf.org; Tue, 25 Jul 2006 12:36:28 -0400
Received: from key1.docomolabs-usa.com ([216.98.102.225]
	helo=fridge.docomolabs-usa.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G5PtT-00042H-V5
	for mip6@ietf.org; Tue, 25 Jul 2006 12:36:28 -0400
Message-ID: <04be01c6b008$c829d710$196115ac@dcml.docomolabsusa.com>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Vijay Devarapalli" <vijay.devarapalli@AzaireNet.com>,
	"Kilian Weniger" <Kilian.Weniger@eu.panasonic.com>
References: <4D2F935F08D41A4C8866693F4F0D7C4FD4505C@lan-ex-01.panasonic.de>
Subject: Re: [Mip6] New charter item: HA assignment
Date: Tue, 25 Jul 2006 09:38:39 -0700
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: 1449ead51a2ff026dcb23465f5379250
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Combining anycast with DNS is certainly an option. We could put something 
about that into the split draft. Anybody else have an opinion on that?

But I think there is a general problem with using anycast for server load 
balancing, or in any case where the measure for which server gets the 
traffic isn't some routing-based metric. This isn't something the MIP6 WG 
can take up, though.

                jak

----- Original Message ----- 
From: "Kilian Weniger" <Kilian.Weniger@eu.panasonic.com>
To: "Vijay Devarapalli" <vijay.devarapalli@AzaireNet.com>; "James Kempf" 
<kempf@docomolabs-usa.com>
Cc: <mip6@ietf.org>
Sent: Tuesday, July 25, 2006 1:48 AM
Subject: RE: [Mip6] New charter item: HA assignment


Right, I assumed a more or less stable anycast group. BTW, I'm not
against the DNS solution per se. It may make sense to combine it with
other methods, e.g., if anycast is used, different anycast HA addresses
could be obtained from DNS for different mobility services
("_mip6._ipv6.example.com" for MIPv6, "_nemo._ipv6.example.com" for
NEMO, "_dsmip6._ipv6.example.com" for DSMIPv6 etc.).

-Kilian

> -----Original Message-----
> From: Vijay Devarapalli [mailto:vijay.devarapalli@AzaireNet.com]
> Sent: Montag, 24. Juli 2006 21:17
> To: James Kempf
> Cc: Kilian Weniger; mip6@ietf.org
> Subject: Re: [Mip6] New charter item: HA assignment
>
> James Kempf wrote:
> > I thought the whole point of  the anycast proposal  and Kilian and
> > Jean-Marie's argumet against DNS was load balancing and that DNS is
> > insufficient because it does not provide fast enough
> dynamic update. If
> > that is the case, then I would think that the ability to
> quickly add and
> > remove addresses from the anycast group would be crucial to
> removing HAs
> > that are loading and adding new ones that aren't.
>
> load balancing does not necessarily mean removing/adding a HA
> from/to the list of HAs. I think it is more about directing the
> users to the right HA. you can have a pretty stable anycast
> group and still direct the MN to a specific HA.
>
> Vijay
>
> >
> >
> >            jak
> >
> > ----- Original Message ----- From: "Vijay Devarapalli"
> > <vijay.devarapalli@azairenet.com>
> > To: "James Kempf" <kempf@docomolabs-usa.com>
> > Cc: "Kilian Weniger" <Kilian.Weniger@eu.panasonic.com>;
> <mip6@ietf.org>
> > Sent: Monday, July 24, 2006 12:08 PM
> > Subject: Re: [Mip6] New charter item: HA assignment
> >
> >
> >> hi Jim,
> >>
> >> I think manual configuration is sufficient in this case. it is
> >> not too often that home agents get added to or deleted from the
> >> the anycast group.
> >>
> >> Vijay
> >>
> >> James Kempf wrote:
> >>> The other problem with this solution is that there is
> still no secure
> >>> way for a collection of unicast server addresses to get
> assigned to
> >>> an anycast address, except for static configuration. So
> how would the
> >>> operator be able to add HAs to the anycast address?
> >>>
> >>> At least, with the DNS solution, the update of the DNS can be
> >>> automated using dynamic DNS.
> >>>
> >>>                        jak
> >>>
> >>> ----- Original Message ----- From: "Vijay Devarapalli"
> >>> <vijay.devarapalli@azairenet.com>
> >>> To: "Kilian Weniger" <Kilian.Weniger@eu.panasonic.com>
> >>> Cc: "James Kempf" <kempf@docomolabs-usa.com>; <mip6@ietf.org>
> >>> Sent: Monday, July 24, 2006 10:26 AM
> >>> Subject: Re: [Mip6] New charter item: HA assignment
> >>>
> >>>
> >>>> Kilian Weniger wrote:
> >>>>
> >>>>> However, the problem depends on how the initial HA is selected.
> >>>>> Anycasting can be used to prevent that new MNs select
> the same initial
> >>>>> HA. For instance, the IKE_SA_INIT can be anycasted.
> >>>>
> >>>> is there another instance of using anycast for load balancing.
> >>>> just curious.
> >>>>
> >>>>> But if this is done,
> >>>>> you can easily get rid of the unnecessary SA
> establishment and the
> >>>>> switch message by requiring the receiver HA to forward
> the IKE_SA_INIT
> >>>>> to a MN-specific and low-loaded HA (see
> >>>>
> >>>> how do you do this? you would still need a HA-to-HA protocol to
> >>>> forward the IKE_SA_INIT message to another HA. when you send a
> >>>> message to an anycast address routing decides which HA receives
> >>>> the message.
> >>>>
> >>>> I have seen anycast used to direct a user to the
> "nearest" server.
> >>>> "nearest" means nearest by routing hops. when all the HAs on the
> >>>> same link, I wonder if anycast gets any load balancing at all.
> >>>>
> >>>> Vijay
> >>>>
> >>>>> draft-dupont-ikev2-haassign-01.txt for details).
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>>
> >>>>> -Kilian
> >>>>>
> >>>>>>             jak
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> _______________________________________________
> >>>>>> Mip6 mailing list
> >>>>>> Mip6@ietf.org
> >>>>>> https://www1.ietf.org/mailman/listinfo/mip6
> >>>>>>
> >>>>>>
> >>>>>
> >>>>>
> >>>>> _______________________________________________
> >>>>> Mip6 mailing list
> >>>>> Mip6@ietf.org
> >>>>> https://www1.ietf.org/mailman/listinfo/mip6
> >>>>
> >>>>
> >>>
> >>>
> >>
> >>
> >
> >
>
>
>




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



From mip6-bounces@ietf.org Tue Jul 25 13:05:53 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G5QLk-0001Di-Vi; Tue, 25 Jul 2006 13:05:40 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G5QLj-0001Dd-BX
	for mip6@ietf.org; Tue, 25 Jul 2006 13:05:39 -0400
Received: from cluster-d.mailcontrol.com ([217.69.20.190])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G5QLh-00087K-HK
	for mip6@ietf.org; Tue, 25 Jul 2006 13:05:39 -0400
Received: from rly03d.srv.mailcontrol.com (localhost.localdomain [127.0.0.1])
	by rly03d.srv.mailcontrol.com (MailControl) with ESMTP id
	k6PH5A0f005425
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <mip6@ietf.org>; Tue, 25 Jul 2006 18:05:25 +0100
Received: from submission.mailcontrol.com (submission.mailcontrol.com
	[212.158.48.250])
	by rly03d.srv.mailcontrol.com (MailControl) id k6PH4aYW004396
	for mip6@ietf.org; Tue, 25 Jul 2006 18:04:36 +0100
Received: from hhe500-02.hbg.de.pan.eu (gate.eu.panasonic.com [194.173.20.12])
	by rly03d-eth0.srv.mailcontrol.com (envelope-sender
	Kilian.Weniger@eu.panasonic.com) (MIMEDefang) with ESMTP id
	k6PH4YHG004327; Tue, 25 Jul 2006 18:04:36 +0100 (BST)
Received: from eundadmi01.pan.eu(10.100.96.64) by hhe500-02.hbg.de.pan.eu via
	smtp id 4eb6_634117d8_1bfa_11db_9768_0030482aac25;
	Tue, 25 Jul 2006 18:26:55 +0200
Received: from VPN-MRelay-01.PRDCG.Panasonic.de ([10.100.176.55])
	by eundadmi01.pan.eu (Lotus Domino Release 6.5.4FP3)
	with ESMTP id 2006072519042486-148338 ;
	Tue, 25 Jul 2006 19:04:24 +0200 
X-Spam-Status: No, hits=0.0 required=6.5
	tests=ALL_TRUSTED: -2.867,AWL: 0.670,BAYES_00: -1.665,
	SARE_RECV_ADDR: 0.027
X-Spam-Level: 
Received: from localhost ([127.0.0.1]) by VPN-MRelay-01.PRDCG.Panasonic.de;
	Tue, 25 Jul 2006 19:08:07 +0200
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.5
Subject: RE: [Mip6] New charter item: HA assignment
In-reply-to: <04b901c6b008$7bb452c0$196115ac@dcml.docomolabsusa.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] New charter item: HA assignment
Thread-Index: AcawCDLu5OpH/sjRSkWpXucQmmzhfQAAQYuw
To: "James Kempf" <kempf@docomolabs-usa.com>,
	"Vijay Devarapalli" <vijay.devarapalli@AzaireNet.com>
Message-ID: <4D2F935F08D41A4C8866693F4F0D7C4FD45118@lan-ex-01.panasonic.de>
Date: Tue, 25 Jul 2006 19:04:18 +0200
From: "Kilian Weniger" <Kilian.Weniger@eu.panasonic.com>
Content-class: urn:content-classes:message
Content-Type: text/plain;
	charset="us-ascii"
X-Scanned-By: MailControl A-07-00-10 (www.mailcontrol.com) on 10.68.1.113
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 2086112c730e13d5955355df27e3074b
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

> -----Original Message-----
> From: James Kempf [mailto:kempf@docomolabs-usa.com]=20
> Sent: Dienstag, 25. Juli 2006 18:37
> To: Vijay Devarapalli; Kilian Weniger
> Cc: mip6@ietf.org
> Subject: Re: [Mip6] New charter item: HA assignment
>=20
> Yes, you would need HA-to-HA communication.
>=20
> The HA receiving the anycast IKE_SA_INIT would forward it to=20
> an HA that
> is able to serve the MN and that is not overloaded. The=20
> forwarding could
> be done by encapsulating the IKE_SA_INIT (in new message or
> IP-in-IP/Ipsec SA).
>=20
> Note that it is assumed that all HAs know or can determine the load of
> other HAs on the link and that they know or can determine which HA(s)
> are able to serve a specific MN (pre-configured rules or by querying a
> server such as AAA). How this is done is TBD, but I guess=20
> this is needed
> for the HA switch solution as well.
>=20
> jak>> How would this be any better than having the MN first=20
> contact the HA=20
> and receiving a rejection, then having the MN contact another=20
> HA? It seems=20
> to me like this would distribute the load of forwarding to=20
> the MN, so the=20
> first HA - which might already be close to its load limit -=20
> wouldn't have to=20
> do any extra work. Just fire off a simple rejection of the=20
> IKE transaction.

The concern was that the initial HA should not be the same for all new
MNs starting the bootstrapping procedure in a certain period of time.
Otherwise all new MNs may be blocked or delayed when the initial HA is
overloaded or under attack ro completely unavailable during this period
of time. The idea was to anycast the IKE_SA_INIT to ensure that the
initial HA is not the same for all new MNs starting the bootstrapping
procedure. Consequently, only a subset of the new MNs would be
blocked/delayed...

Another option would be that the MNs use some randomization in selecting
the initial HA from the HA list obtained via DNS (i.e., not always
selecting the first HA with the highest weight).=20

>=20
> jak>> It also wouldn't require an additional HA-HA load=20
> balancing protocol.

Ok, I was comparing with the HA switch mechnism, which would need
information about the load of other HAs to propose a new (low-loaded) HA
to the MN.

>=20
>=20
> > I have seen anycast used to direct a user to the "nearest" server.
> > "nearest" means nearest by routing hops. when all the HAs on the
> > same link, I wonder if anycast gets any load balancing at all.
> >
>=20
> There are multiple possible techniques to deploy anycast in such
> scenario, some of them might be applicable.
> RFC1546 describes one that is based on ARP:
>=20
>   "On a shared media network, such as an Ethernet and or=20
> Token Ring, it
>    must be possible to transmit an anycast datagram to a=20
> server also on
>    the same network without consulting a (possibly=20
> non-existent) router.
>    There are at least two ways this can be done.
>=20
>    One approach is to ARP for the anycast address.  Servers which
>    support the anycast address can reply to the ARP request, and the
>    sending host can transmit to the first server that responds.  This
>    approach is reminiscent of the ARP hack (RFC 1027) and like the ARP
>    hack, requires ARP cache timeouts for the anycast addresses be kept
>    small (around 1 minute), so that if an anycast server goes down,
>    hosts will promptly flush the ARP entry and query for other servers
>    supporting the anycast address."
>=20
> draft-ietf-grow-anycast-04.txt mentiones hash-based methods for
> *equal-cost paths*:
>=20
>   "...applying equal-cost
>    multi-path (ECMP) selection algorithms which cause a single node to
>    be selected for a single multi-packet transaction.  For an=20
> example of
>    the use of hash-based ECMP selection in anycast service=20
> distribution,
>    see [ISC-TN-2004-1].
>=20
>   "ther ECMP selection algorithms are commonly available, including
>    those in which packets from the same flow are not guaranteed to be
>    routed towards the same destination.  ECMP algorithms=20
> which select a
>    route on a per-packet basis rather than per-flow are commonly
>    referred to as performing "Per Packet Load Balancing" (PPLB)."
>=20
>=20
> jak>> I don't see any routing based metric as being=20
> particularly useful in=20
> this case. The figure of merit in terms of which server gets=20
> traffic isn't=20
> primarily going to be routing. It might be load, or some=20
> other factor, like=20
> having particular HAs serve VoIP v.s. best effort traffic.

As I said, the purpose of anycasting the IKE_SA_INIT was to ensure that
the initial HA for bootstrapping is not the same for all MNs. The actual
load balancing and QoS/MN-specific HA selection would be done by
forwarding the IKE_SA_INIT by the receiver HA to another HA.

-Kilian

>=20
>                  jak=20
>=20
>=20
>=20
>=20


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



From mip6-bounces@ietf.org Tue Jul 25 14:53:49 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G5S2K-0003bt-40; Tue, 25 Jul 2006 14:53:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G5S2H-0003bh-Hi
	for mip6@ietf.org; Tue, 25 Jul 2006 14:53:41 -0400
Received: from mail1.azairenet.com ([66.92.223.4] helo=bart.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G5S2H-0003B2-0z
	for mip6@ietf.org; Tue, 25 Jul 2006 14:53:41 -0400
Received: from [10.1.201.0] ([10.1.201.0]) by bart.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Tue, 25 Jul 2006 11:53:39 -0700
Message-ID: <44C6684A.1090309@azairenet.com>
Date: Tue, 25 Jul 2006 11:51:54 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.2 (X11/20060516)
MIME-Version: 1.0
To: James Kempf <kempf@docomolabs-usa.com>
Subject: Re: [Mip6] New charter item: HA assignment
References: <4D2F935F08D41A4C8866693F4F0D7C4FD4505C@lan-ex-01.panasonic.de>
	<04be01c6b008$c829d710$196115ac@dcml.docomolabsusa.com>
In-Reply-To: <04be01c6b008$c829d710$196115ac@dcml.docomolabsusa.com>
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 25 Jul 2006 18:53:39.0120 (UTC)
	FILETIME=[A4260B00:01C6B01B]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0e9ebc0cbd700a87c0637ad0e2c91610
Cc: mip6@ietf.org, Kilian Weniger <Kilian.Weniger@eu.panasonic.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

James Kempf wrote:
> Combining anycast with DNS is certainly an option. We could put 
> something about that into the split draft. Anybody else have an opinion 
> on that?

the MN using DNS to obtain the anycast address for the home
agents is briefly mentioned in RFC 3775. see appendix A.5.
but we should elaborate more on this in the split scenario
solution draft.

Vijay

> But I think there is a general problem with using anycast for server 
> load balancing, or in any case where the measure for which server gets 
> the traffic isn't some routing-based metric. This isn't something the 
> MIP6 WG can take up, though.
> 
>                jak
> 
> ----- Original Message ----- From: "Kilian Weniger" 
> <Kilian.Weniger@eu.panasonic.com>
> To: "Vijay Devarapalli" <vijay.devarapalli@AzaireNet.com>; "James Kempf" 
> <kempf@docomolabs-usa.com>
> Cc: <mip6@ietf.org>
> Sent: Tuesday, July 25, 2006 1:48 AM
> Subject: RE: [Mip6] New charter item: HA assignment
> 
> 
> Right, I assumed a more or less stable anycast group. BTW, I'm not
> against the DNS solution per se. It may make sense to combine it with
> other methods, e.g., if anycast is used, different anycast HA addresses
> could be obtained from DNS for different mobility services
> ("_mip6._ipv6.example.com" for MIPv6, "_nemo._ipv6.example.com" for
> NEMO, "_dsmip6._ipv6.example.com" for DSMIPv6 etc.).
> 
> -Kilian
> 
>> -----Original Message-----
>> From: Vijay Devarapalli [mailto:vijay.devarapalli@AzaireNet.com]
>> Sent: Montag, 24. Juli 2006 21:17
>> To: James Kempf
>> Cc: Kilian Weniger; mip6@ietf.org
>> Subject: Re: [Mip6] New charter item: HA assignment
>>
>> James Kempf wrote:
>> > I thought the whole point of  the anycast proposal  and Kilian and
>> > Jean-Marie's argumet against DNS was load balancing and that DNS is
>> > insufficient because it does not provide fast enough
>> dynamic update. If
>> > that is the case, then I would think that the ability to
>> quickly add and
>> > remove addresses from the anycast group would be crucial to
>> removing HAs
>> > that are loading and adding new ones that aren't.
>>
>> load balancing does not necessarily mean removing/adding a HA
>> from/to the list of HAs. I think it is more about directing the
>> users to the right HA. you can have a pretty stable anycast
>> group and still direct the MN to a specific HA.
>>
>> Vijay
>>
>> >
>> >
>> >            jak
>> >
>> > ----- Original Message ----- From: "Vijay Devarapalli"
>> > <vijay.devarapalli@azairenet.com>
>> > To: "James Kempf" <kempf@docomolabs-usa.com>
>> > Cc: "Kilian Weniger" <Kilian.Weniger@eu.panasonic.com>;
>> <mip6@ietf.org>
>> > Sent: Monday, July 24, 2006 12:08 PM
>> > Subject: Re: [Mip6] New charter item: HA assignment
>> >
>> >
>> >> hi Jim,
>> >>
>> >> I think manual configuration is sufficient in this case. it is
>> >> not too often that home agents get added to or deleted from the
>> >> the anycast group.
>> >>
>> >> Vijay
>> >>
>> >> James Kempf wrote:
>> >>> The other problem with this solution is that there is
>> still no secure
>> >>> way for a collection of unicast server addresses to get
>> assigned to
>> >>> an anycast address, except for static configuration. So
>> how would the
>> >>> operator be able to add HAs to the anycast address?
>> >>>
>> >>> At least, with the DNS solution, the update of the DNS can be
>> >>> automated using dynamic DNS.
>> >>>
>> >>>                        jak
>> >>>
>> >>> ----- Original Message ----- From: "Vijay Devarapalli"
>> >>> <vijay.devarapalli@azairenet.com>
>> >>> To: "Kilian Weniger" <Kilian.Weniger@eu.panasonic.com>
>> >>> Cc: "James Kempf" <kempf@docomolabs-usa.com>; <mip6@ietf.org>
>> >>> Sent: Monday, July 24, 2006 10:26 AM
>> >>> Subject: Re: [Mip6] New charter item: HA assignment
>> >>>
>> >>>
>> >>>> Kilian Weniger wrote:
>> >>>>
>> >>>>> However, the problem depends on how the initial HA is selected.
>> >>>>> Anycasting can be used to prevent that new MNs select
>> the same initial
>> >>>>> HA. For instance, the IKE_SA_INIT can be anycasted.
>> >>>>
>> >>>> is there another instance of using anycast for load balancing.
>> >>>> just curious.
>> >>>>
>> >>>>> But if this is done,
>> >>>>> you can easily get rid of the unnecessary SA
>> establishment and the
>> >>>>> switch message by requiring the receiver HA to forward
>> the IKE_SA_INIT
>> >>>>> to a MN-specific and low-loaded HA (see
>> >>>>
>> >>>> how do you do this? you would still need a HA-to-HA protocol to
>> >>>> forward the IKE_SA_INIT message to another HA. when you send a
>> >>>> message to an anycast address routing decides which HA receives
>> >>>> the message.
>> >>>>
>> >>>> I have seen anycast used to direct a user to the
>> "nearest" server.
>> >>>> "nearest" means nearest by routing hops. when all the HAs on the
>> >>>> same link, I wonder if anycast gets any load balancing at all.
>> >>>>
>> >>>> Vijay
>> >>>>
>> >>>>> draft-dupont-ikev2-haassign-01.txt for details).
>> >>>>
>> >>>>
>> >>>>
>> >>>>
>> >>>>
>> >>>>
>> >>>>>
>> >>>>> -Kilian
>> >>>>>
>> >>>>>>             jak
>> >>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>> _______________________________________________
>> >>>>>> Mip6 mailing list
>> >>>>>> Mip6@ietf.org
>> >>>>>> https://www1.ietf.org/mailman/listinfo/mip6
>> >>>>>>
>> >>>>>>
>> >>>>>
>> >>>>>
>> >>>>> _______________________________________________
>> >>>>> Mip6 mailing list
>> >>>>> Mip6@ietf.org
>> >>>>> https://www1.ietf.org/mailman/listinfo/mip6
>> >>>>
>> >>>>
>> >>>
>> >>>
>> >>
>> >>
>> >
>> >
>>
>>
>>
> 
> 
> 


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



From mip6-bounces@ietf.org Tue Jul 25 15:29:50 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G5SbF-00056p-9I; Tue, 25 Jul 2006 15:29:49 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G5SbD-0004yX-PZ
	for mip6@ietf.org; Tue, 25 Jul 2006 15:29:47 -0400
Received: from key1.docomolabs-usa.com ([216.98.102.225]
	helo=fridge.docomolabs-usa.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G5SbC-00017C-TW
	for mip6@ietf.org; Tue, 25 Jul 2006 15:29:47 -0400
Message-ID: <060601c6b020$f7ceb900$196115ac@dcml.docomolabsusa.com>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
References: <4D2F935F08D41A4C8866693F4F0D7C4FD4505C@lan-ex-01.panasonic.de>
	<04be01c6b008$c829d710$196115ac@dcml.docomolabsusa.com>
	<44C6684A.1090309@azairenet.com>
Subject: Re: [Mip6] New charter item: HA assignment
Date: Tue, 25 Jul 2006 12:31:46 -0700
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=response
Content-Transfer-Encoding: 7bit
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: 43317e64100dd4d87214c51822b582d1
Cc: mip6@ietf.org, Kilian Weniger <Kilian.Weniger@eu.panasonic.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Right, but that is for DHAAD. I thought the proposal here was for the MN to 
send the IKE_SA_INIT to the anycast address, for the anycast address to 
forward it to an HA, then for that HA to respond.

            jak

----- Original Message ----- 
From: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
To: "James Kempf" <kempf@docomolabs-usa.com>
Cc: "Kilian Weniger" <Kilian.Weniger@eu.panasonic.com>; <mip6@ietf.org>
Sent: Tuesday, July 25, 2006 11:51 AM
Subject: Re: [Mip6] New charter item: HA assignment


> James Kempf wrote:
>> Combining anycast with DNS is certainly an option. We could put something 
>> about that into the split draft. Anybody else have an opinion on that?
>
> the MN using DNS to obtain the anycast address for the home
> agents is briefly mentioned in RFC 3775. see appendix A.5.
> but we should elaborate more on this in the split scenario
> solution draft.
>
> Vijay
>
>> But I think there is a general problem with using anycast for server load 
>> balancing, or in any case where the measure for which server gets the 
>> traffic isn't some routing-based metric. This isn't something the MIP6 WG 
>> can take up, though.
>>
>>                jak
>>
>> ----- Original Message ----- From: "Kilian Weniger" 
>> <Kilian.Weniger@eu.panasonic.com>
>> To: "Vijay Devarapalli" <vijay.devarapalli@AzaireNet.com>; "James Kempf" 
>> <kempf@docomolabs-usa.com>
>> Cc: <mip6@ietf.org>
>> Sent: Tuesday, July 25, 2006 1:48 AM
>> Subject: RE: [Mip6] New charter item: HA assignment
>>
>>
>> Right, I assumed a more or less stable anycast group. BTW, I'm not
>> against the DNS solution per se. It may make sense to combine it with
>> other methods, e.g., if anycast is used, different anycast HA addresses
>> could be obtained from DNS for different mobility services
>> ("_mip6._ipv6.example.com" for MIPv6, "_nemo._ipv6.example.com" for
>> NEMO, "_dsmip6._ipv6.example.com" for DSMIPv6 etc.).
>>
>> -Kilian
>>
>>> -----Original Message-----
>>> From: Vijay Devarapalli [mailto:vijay.devarapalli@AzaireNet.com]
>>> Sent: Montag, 24. Juli 2006 21:17
>>> To: James Kempf
>>> Cc: Kilian Weniger; mip6@ietf.org
>>> Subject: Re: [Mip6] New charter item: HA assignment
>>>
>>> James Kempf wrote:
>>> > I thought the whole point of  the anycast proposal  and Kilian and
>>> > Jean-Marie's argumet against DNS was load balancing and that DNS is
>>> > insufficient because it does not provide fast enough
>>> dynamic update. If
>>> > that is the case, then I would think that the ability to
>>> quickly add and
>>> > remove addresses from the anycast group would be crucial to
>>> removing HAs
>>> > that are loading and adding new ones that aren't.
>>>
>>> load balancing does not necessarily mean removing/adding a HA
>>> from/to the list of HAs. I think it is more about directing the
>>> users to the right HA. you can have a pretty stable anycast
>>> group and still direct the MN to a specific HA.
>>>
>>> Vijay
>>>
>>> >
>>> >
>>> >            jak
>>> >
>>> > ----- Original Message ----- From: "Vijay Devarapalli"
>>> > <vijay.devarapalli@azairenet.com>
>>> > To: "James Kempf" <kempf@docomolabs-usa.com>
>>> > Cc: "Kilian Weniger" <Kilian.Weniger@eu.panasonic.com>;
>>> <mip6@ietf.org>
>>> > Sent: Monday, July 24, 2006 12:08 PM
>>> > Subject: Re: [Mip6] New charter item: HA assignment
>>> >
>>> >
>>> >> hi Jim,
>>> >>
>>> >> I think manual configuration is sufficient in this case. it is
>>> >> not too often that home agents get added to or deleted from the
>>> >> the anycast group.
>>> >>
>>> >> Vijay
>>> >>
>>> >> James Kempf wrote:
>>> >>> The other problem with this solution is that there is
>>> still no secure
>>> >>> way for a collection of unicast server addresses to get
>>> assigned to
>>> >>> an anycast address, except for static configuration. So
>>> how would the
>>> >>> operator be able to add HAs to the anycast address?
>>> >>>
>>> >>> At least, with the DNS solution, the update of the DNS can be
>>> >>> automated using dynamic DNS.
>>> >>>
>>> >>>                        jak
>>> >>>
>>> >>> ----- Original Message ----- From: "Vijay Devarapalli"
>>> >>> <vijay.devarapalli@azairenet.com>
>>> >>> To: "Kilian Weniger" <Kilian.Weniger@eu.panasonic.com>
>>> >>> Cc: "James Kempf" <kempf@docomolabs-usa.com>; <mip6@ietf.org>
>>> >>> Sent: Monday, July 24, 2006 10:26 AM
>>> >>> Subject: Re: [Mip6] New charter item: HA assignment
>>> >>>
>>> >>>
>>> >>>> Kilian Weniger wrote:
>>> >>>>
>>> >>>>> However, the problem depends on how the initial HA is selected.
>>> >>>>> Anycasting can be used to prevent that new MNs select
>>> the same initial
>>> >>>>> HA. For instance, the IKE_SA_INIT can be anycasted.
>>> >>>>
>>> >>>> is there another instance of using anycast for load balancing.
>>> >>>> just curious.
>>> >>>>
>>> >>>>> But if this is done,
>>> >>>>> you can easily get rid of the unnecessary SA
>>> establishment and the
>>> >>>>> switch message by requiring the receiver HA to forward
>>> the IKE_SA_INIT
>>> >>>>> to a MN-specific and low-loaded HA (see
>>> >>>>
>>> >>>> how do you do this? you would still need a HA-to-HA protocol to
>>> >>>> forward the IKE_SA_INIT message to another HA. when you send a
>>> >>>> message to an anycast address routing decides which HA receives
>>> >>>> the message.
>>> >>>>
>>> >>>> I have seen anycast used to direct a user to the
>>> "nearest" server.
>>> >>>> "nearest" means nearest by routing hops. when all the HAs on the
>>> >>>> same link, I wonder if anycast gets any load balancing at all.
>>> >>>>
>>> >>>> Vijay
>>> >>>>
>>> >>>>> draft-dupont-ikev2-haassign-01.txt for details).
>>> >>>>
>>> >>>>
>>> >>>>
>>> >>>>
>>> >>>>
>>> >>>>
>>> >>>>>
>>> >>>>> -Kilian
>>> >>>>>
>>> >>>>>>             jak
>>> >>>>>>
>>> >>>>>>
>>> >>>>>>
>>> >>>>>>
>>> >>>>>> _______________________________________________
>>> >>>>>> Mip6 mailing list
>>> >>>>>> Mip6@ietf.org
>>> >>>>>> https://www1.ietf.org/mailman/listinfo/mip6
>>> >>>>>>
>>> >>>>>>
>>> >>>>>
>>> >>>>>
>>> >>>>> _______________________________________________
>>> >>>>> Mip6 mailing list
>>> >>>>> Mip6@ietf.org
>>> >>>>> https://www1.ietf.org/mailman/listinfo/mip6
>>> >>>>
>>> >>>>
>>> >>>
>>> >>>
>>> >>
>>> >>
>>> >
>>> >
>>>
>>>
>>>
>>
>>
>>
>
> 



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



From mip6-bounces@ietf.org Tue Jul 25 17:26:20 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G5UPq-0004jO-JV; Tue, 25 Jul 2006 17:26:10 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G5UPo-0004jD-Qn
	for mip6@ietf.org; Tue, 25 Jul 2006 17:26:08 -0400
Received: from mail1.azairenet.com ([66.92.223.4] helo=bart.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G5UPm-00070G-7l
	for mip6@ietf.org; Tue, 25 Jul 2006 17:26:08 -0400
Received: from [10.1.201.0] ([10.1.201.0]) by bart.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Tue, 25 Jul 2006 14:26:03 -0700
Message-ID: <44C68C03.1070508@azairenet.com>
Date: Tue, 25 Jul 2006 14:24:19 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.2 (X11/20060516)
MIME-Version: 1.0
To: James Kempf <kempf@docomolabs-usa.com>
Subject: Re: [Mip6] New charter item: HA assignment
References: <4D2F935F08D41A4C8866693F4F0D7C4FD4505C@lan-ex-01.panasonic.de>
	<04be01c6b008$c829d710$196115ac@dcml.docomolabsusa.com>
	<44C6684A.1090309@azairenet.com>
	<060601c6b020$f7ceb900$196115ac@dcml.docomolabsusa.com>
In-Reply-To: <060601c6b020$f7ceb900$196115ac@dcml.docomolabsusa.com>
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 25 Jul 2006 21:26:03.0955 (UTC)
	FILETIME=[EEE52030:01C6B030]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 501044f827b673024f6a4cb1d46e67d2
Cc: mip6@ietf.org, Kilian Weniger <Kilian.Weniger@eu.panasonic.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

James Kempf wrote:
> Right, but that is for DHAAD. I thought the proposal here was for the MN 
> to send the IKE_SA_INIT to the anycast address, for the anycast address 
> to forward it to an HA, then for that HA to respond.

ofcourse. just pointing that configuring an anycast address
in the DNS instead of the actual HA IPv6 address was written
up in RFC 3775. I guess it would be the same anycast address
whether it is used for DHAAD or IKE_SA_INIT.

Vijay

> 
>            jak
> 
> ----- Original Message ----- From: "Vijay Devarapalli" 
> <vijay.devarapalli@azairenet.com>
> To: "James Kempf" <kempf@docomolabs-usa.com>
> Cc: "Kilian Weniger" <Kilian.Weniger@eu.panasonic.com>; <mip6@ietf.org>
> Sent: Tuesday, July 25, 2006 11:51 AM
> Subject: Re: [Mip6] New charter item: HA assignment
> 
> 
>> James Kempf wrote:
>>> Combining anycast with DNS is certainly an option. We could put 
>>> something about that into the split draft. Anybody else have an 
>>> opinion on that?
>>
>> the MN using DNS to obtain the anycast address for the home
>> agents is briefly mentioned in RFC 3775. see appendix A.5.
>> but we should elaborate more on this in the split scenario
>> solution draft.
>>
>> Vijay
>>
>>> But I think there is a general problem with using anycast for server 
>>> load balancing, or in any case where the measure for which server 
>>> gets the traffic isn't some routing-based metric. This isn't 
>>> something the MIP6 WG can take up, though.
>>>
>>>                jak
>>>
>>> ----- Original Message ----- From: "Kilian Weniger" 
>>> <Kilian.Weniger@eu.panasonic.com>
>>> To: "Vijay Devarapalli" <vijay.devarapalli@AzaireNet.com>; "James 
>>> Kempf" <kempf@docomolabs-usa.com>
>>> Cc: <mip6@ietf.org>
>>> Sent: Tuesday, July 25, 2006 1:48 AM
>>> Subject: RE: [Mip6] New charter item: HA assignment
>>>
>>>
>>> Right, I assumed a more or less stable anycast group. BTW, I'm not
>>> against the DNS solution per se. It may make sense to combine it with
>>> other methods, e.g., if anycast is used, different anycast HA addresses
>>> could be obtained from DNS for different mobility services
>>> ("_mip6._ipv6.example.com" for MIPv6, "_nemo._ipv6.example.com" for
>>> NEMO, "_dsmip6._ipv6.example.com" for DSMIPv6 etc.).
>>>
>>> -Kilian
>>>
>>>> -----Original Message-----
>>>> From: Vijay Devarapalli [mailto:vijay.devarapalli@AzaireNet.com]
>>>> Sent: Montag, 24. Juli 2006 21:17
>>>> To: James Kempf
>>>> Cc: Kilian Weniger; mip6@ietf.org
>>>> Subject: Re: [Mip6] New charter item: HA assignment
>>>>
>>>> James Kempf wrote:
>>>> > I thought the whole point of  the anycast proposal  and Kilian and
>>>> > Jean-Marie's argumet against DNS was load balancing and that DNS is
>>>> > insufficient because it does not provide fast enough
>>>> dynamic update. If
>>>> > that is the case, then I would think that the ability to
>>>> quickly add and
>>>> > remove addresses from the anycast group would be crucial to
>>>> removing HAs
>>>> > that are loading and adding new ones that aren't.
>>>>
>>>> load balancing does not necessarily mean removing/adding a HA
>>>> from/to the list of HAs. I think it is more about directing the
>>>> users to the right HA. you can have a pretty stable anycast
>>>> group and still direct the MN to a specific HA.
>>>>
>>>> Vijay
>>>>
>>>> >
>>>> >
>>>> >            jak
>>>> >
>>>> > ----- Original Message ----- From: "Vijay Devarapalli"
>>>> > <vijay.devarapalli@azairenet.com>
>>>> > To: "James Kempf" <kempf@docomolabs-usa.com>
>>>> > Cc: "Kilian Weniger" <Kilian.Weniger@eu.panasonic.com>;
>>>> <mip6@ietf.org>
>>>> > Sent: Monday, July 24, 2006 12:08 PM
>>>> > Subject: Re: [Mip6] New charter item: HA assignment
>>>> >
>>>> >
>>>> >> hi Jim,
>>>> >>
>>>> >> I think manual configuration is sufficient in this case. it is
>>>> >> not too often that home agents get added to or deleted from the
>>>> >> the anycast group.
>>>> >>
>>>> >> Vijay
>>>> >>
>>>> >> James Kempf wrote:
>>>> >>> The other problem with this solution is that there is
>>>> still no secure
>>>> >>> way for a collection of unicast server addresses to get
>>>> assigned to
>>>> >>> an anycast address, except for static configuration. So
>>>> how would the
>>>> >>> operator be able to add HAs to the anycast address?
>>>> >>>
>>>> >>> At least, with the DNS solution, the update of the DNS can be
>>>> >>> automated using dynamic DNS.
>>>> >>>
>>>> >>>                        jak
>>>> >>>
>>>> >>> ----- Original Message ----- From: "Vijay Devarapalli"
>>>> >>> <vijay.devarapalli@azairenet.com>
>>>> >>> To: "Kilian Weniger" <Kilian.Weniger@eu.panasonic.com>
>>>> >>> Cc: "James Kempf" <kempf@docomolabs-usa.com>; <mip6@ietf.org>
>>>> >>> Sent: Monday, July 24, 2006 10:26 AM
>>>> >>> Subject: Re: [Mip6] New charter item: HA assignment
>>>> >>>
>>>> >>>
>>>> >>>> Kilian Weniger wrote:
>>>> >>>>
>>>> >>>>> However, the problem depends on how the initial HA is selected.
>>>> >>>>> Anycasting can be used to prevent that new MNs select
>>>> the same initial
>>>> >>>>> HA. For instance, the IKE_SA_INIT can be anycasted.
>>>> >>>>
>>>> >>>> is there another instance of using anycast for load balancing.
>>>> >>>> just curious.
>>>> >>>>
>>>> >>>>> But if this is done,
>>>> >>>>> you can easily get rid of the unnecessary SA
>>>> establishment and the
>>>> >>>>> switch message by requiring the receiver HA to forward
>>>> the IKE_SA_INIT
>>>> >>>>> to a MN-specific and low-loaded HA (see
>>>> >>>>
>>>> >>>> how do you do this? you would still need a HA-to-HA protocol to
>>>> >>>> forward the IKE_SA_INIT message to another HA. when you send a
>>>> >>>> message to an anycast address routing decides which HA receives
>>>> >>>> the message.
>>>> >>>>
>>>> >>>> I have seen anycast used to direct a user to the
>>>> "nearest" server.
>>>> >>>> "nearest" means nearest by routing hops. when all the HAs on the
>>>> >>>> same link, I wonder if anycast gets any load balancing at all.
>>>> >>>>
>>>> >>>> Vijay
>>>> >>>>
>>>> >>>>> draft-dupont-ikev2-haassign-01.txt for details).
>>>> >>>>
>>>> >>>>
>>>> >>>>
>>>> >>>>
>>>> >>>>
>>>> >>>>
>>>> >>>>>
>>>> >>>>> -Kilian
>>>> >>>>>
>>>> >>>>>>             jak
>>>> >>>>>>
>>>> >>>>>>
>>>> >>>>>>
>>>> >>>>>>
>>>> >>>>>> _______________________________________________
>>>> >>>>>> Mip6 mailing list
>>>> >>>>>> Mip6@ietf.org
>>>> >>>>>> https://www1.ietf.org/mailman/listinfo/mip6
>>>> >>>>>>
>>>> >>>>>>
>>>> >>>>>
>>>> >>>>>
>>>> >>>>> _______________________________________________
>>>> >>>>> Mip6 mailing list
>>>> >>>>> Mip6@ietf.org
>>>> >>>>> https://www1.ietf.org/mailman/listinfo/mip6
>>>> >>>>
>>>> >>>>
>>>> >>>
>>>> >>>
>>>> >>
>>>> >>
>>>> >
>>>> >
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
>>
> 
> 


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



From mip6-bounces@ietf.org Wed Jul 26 08:04:42 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G5i7s-0003BN-0u; Wed, 26 Jul 2006 08:04:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G5i7q-0003BI-Pe
	for mip6@ietf.org; Wed, 26 Jul 2006 08:04:30 -0400
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G5i7p-0006JI-DE
	for mip6@ietf.org; Wed, 26 Jul 2006 08:04:30 -0400
Received: from il06exr03.mot.com (il06exr03.mot.com [129.188.137.133])
	by motgate8.mot.com (8.12.11/Motorola) with ESMTP id k6QC3qvC022475;
	Wed, 26 Jul 2006 05:03:52 -0700 (MST)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by il06exr03.mot.com (8.13.1/8.13.0) with ESMTP id k6QC3p2Y012258;
	Wed, 26 Jul 2006 07:03:51 -0500 (CDT)
Message-ID: <44C75A26.20602@motorola.com>
Date: Wed, 26 Jul 2006 14:03:50 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: James Kempf <kempf@docomolabs-usa.com>
Subject: Re: [Mip6] New charter item: HA assignment
References: <4D2F935F08D41A4C8866693F4F0D7C4FD4505C@lan-ex-01.panasonic.de>
	<04be01c6b008$c829d710$196115ac@dcml.docomolabsusa.com>
In-Reply-To: <04be01c6b008$c829d710$196115ac@dcml.docomolabsusa.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAQAAAAQ=
X-White-List-Member: TRUE
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 33cc095b503da4365ce57c727e553cf1
Cc: mip6@ietf.org, Kilian Weniger <Kilian.Weniger@eu.panasonic.com>,
	Vijay Devarapalli <vijay.devarapalli@AzaireNet.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

James Kempf wrote:
> Combining anycast with DNS is certainly an option. We could put 
> something about that into the split draft. Anybody else have an
> opinion on that?

I do, I think the text to be put should say something about the anycast
address as the AAAA record for an fqdn of HA.  I think it should also
say something about IPsec using anycast addresses and, if impossible -
why, then IANA-reserve an apparently-anycast (not really anycast)
address that works ok with IPsec.

> But I think there is a general problem with using anycast for server
>  load balancing, or in any case where the measure for which server
> gets the traffic isn't some routing-based metric. This isn't
> something the MIP6 WG can take up, though.

I think I agree.

Alex

> 
> jak
> 
> ----- Original Message ----- From: "Kilian Weniger" 
> <Kilian.Weniger@eu.panasonic.com> To: "Vijay Devarapalli"
> <vijay.devarapalli@AzaireNet.com>; "James Kempf" 
> <kempf@docomolabs-usa.com> Cc: <mip6@ietf.org> Sent: Tuesday, July
> 25, 2006 1:48 AM Subject: RE: [Mip6] New charter item: HA assignment
> 
> 
> Right, I assumed a more or less stable anycast group. BTW, I'm not 
> against the DNS solution per se. It may make sense to combine it with
>  other methods, e.g., if anycast is used, different anycast HA
> addresses could be obtained from DNS for different mobility services 
> ("_mip6._ipv6.example.com" for MIPv6, "_nemo._ipv6.example.com" for 
> NEMO, "_dsmip6._ipv6.example.com" for DSMIPv6 etc.).
> 
> -Kilian
> 
>> -----Original Message----- From: Vijay Devarapalli
>> [mailto:vijay.devarapalli@AzaireNet.com] Sent: Montag, 24. Juli
>> 2006 21:17 To: James Kempf Cc: Kilian Weniger; mip6@ietf.org 
>> Subject: Re: [Mip6] New charter item: HA assignment
>> 
>> James Kempf wrote:
>>> I thought the whole point of  the anycast proposal  and Kilian
>>> and Jean-Marie's argumet against DNS was load balancing and that
>>> DNS is insufficient because it does not provide fast enough
>> dynamic update. If
>>> that is the case, then I would think that the ability to
>> quickly add and
>>> remove addresses from the anycast group would be crucial to
>> removing HAs
>>> that are loading and adding new ones that aren't.
>> 
>> load balancing does not necessarily mean removing/adding a HA 
>> from/to the list of HAs. I think it is more about directing the 
>> users to the right HA. you can have a pretty stable anycast group
>> and still direct the MN to a specific HA.
>> 
>> Vijay
>> 
>>> 
>>> 
>>> jak
>>> 
>>> ----- Original Message ----- From: "Vijay Devarapalli" 
>>> <vijay.devarapalli@azairenet.com> To: "James Kempf"
>>> <kempf@docomolabs-usa.com> Cc: "Kilian Weniger"
>>> <Kilian.Weniger@eu.panasonic.com>;
>> <mip6@ietf.org>
>>> Sent: Monday, July 24, 2006 12:08 PM Subject: Re: [Mip6] New
>>> charter item: HA assignment
>>> 
>>> 
>>>> hi Jim,
>>>> 
>>>> I think manual configuration is sufficient in this case. it is 
>>>> not too often that home agents get added to or deleted from the
>>>>  the anycast group.
>>>> 
>>>> Vijay
>>>> 
>>>> James Kempf wrote:
>>>>> The other problem with this solution is that there is
>> still no secure
>>>>> way for a collection of unicast server addresses to get
>> assigned to
>>>>> an anycast address, except for static configuration. So
>> how would the
>>>>> operator be able to add HAs to the anycast address?
>>>>> 
>>>>> At least, with the DNS solution, the update of the DNS can be
>>>>>  automated using dynamic DNS.
>>>>> 
>>>>> jak
>>>>> 
>>>>> ----- Original Message ----- From: "Vijay Devarapalli" 
>>>>> <vijay.devarapalli@azairenet.com> To: "Kilian Weniger"
>>>>> <Kilian.Weniger@eu.panasonic.com> Cc: "James Kempf"
>>>>> <kempf@docomolabs-usa.com>; <mip6@ietf.org> Sent: Monday,
>>>>> July 24, 2006 10:26 AM Subject: Re: [Mip6] New charter item:
>>>>> HA assignment
>>>>> 
>>>>> 
>>>>>> Kilian Weniger wrote:
>>>>>> 
>>>>>>> However, the problem depends on how the initial HA is
>>>>>>> selected. Anycasting can be used to prevent that new MNs
>>>>>>> select
>> the same initial
>>>>>>> HA. For instance, the IKE_SA_INIT can be anycasted.
>>>>>> 
>>>>>> is there another instance of using anycast for load
>>>>>> balancing. just curious.
>>>>>> 
>>>>>>> But if this is done, you can easily get rid of the
>>>>>>> unnecessary SA
>> establishment and the
>>>>>>> switch message by requiring the receiver HA to forward
>> the IKE_SA_INIT
>>>>>>> to a MN-specific and low-loaded HA (see
>>>>>> 
>>>>>> how do you do this? you would still need a HA-to-HA
>>>>>> protocol to forward the IKE_SA_INIT message to another HA.
>>>>>> when you send a message to an anycast address routing
>>>>>> decides which HA receives the message.
>>>>>> 
>>>>>> I have seen anycast used to direct a user to the
>> "nearest" server.
>>>>>> "nearest" means nearest by routing hops. when all the HAs
>>>>>> on the same link, I wonder if anycast gets any load
>>>>>> balancing at all.
>>>>>> 
>>>>>> Vijay
>>>>>> 
>>>>>>> draft-dupont-ikev2-haassign-01.txt for details).
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>>> 
>>>>>>> -Kilian
>>>>>>> 
>>>>>>>> jak
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>> _______________________________________________ Mip6
>>>>>>>> mailing list Mip6@ietf.org 
>>>>>>>> https://www1.ietf.org/mailman/listinfo/mip6
>>>>>>>> 
>>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> _______________________________________________ Mip6
>>>>>>> mailing list Mip6@ietf.org 
>>>>>>> https://www1.ietf.org/mailman/listinfo/mip6
>>>>>> 
>>>>>> 
>>>>> 
>>>>> 
>>>> 
>>>> 
>>> 
>>> 
>> 
>> 
>> 
> 
> 
> 
> 
> _______________________________________________ Mip6 mailing list 
> Mip6@ietf.org https://www1.ietf.org/mailman/listinfo/mip6
> 


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



From mip6-bounces@ietf.org Wed Jul 26 11:58:15 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G5llz-0000vV-PX; Wed, 26 Jul 2006 11:58:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G5lly-0000sa-0f
	for mip6@ietf.org; Wed, 26 Jul 2006 11:58:10 -0400
Received: from key1.docomolabs-usa.com ([216.98.102.225]
	helo=fridge.docomolabs-usa.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G5llw-0005yg-K4
	for mip6@ietf.org; Wed, 26 Jul 2006 11:58:09 -0400
Message-ID: <07b501c6b0cc$9a25e6f0$196115ac@dcml.docomolabsusa.com>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Alexandru Petrescu" <alexandru.petrescu@motorola.com>
References: <4D2F935F08D41A4C8866693F4F0D7C4FD4505C@lan-ex-01.panasonic.de>
	<04be01c6b008$c829d710$196115ac@dcml.docomolabsusa.com>
	<44C75A26.20602@motorola.com>
Subject: Re: [Mip6] New charter item: HA assignment
Date: Wed, 26 Jul 2006 09:00:23 -0700
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=response
Content-Transfer-Encoding: 7bit
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Cc: mip6@ietf.org, Kilian Weniger <Kilian.Weniger@eu.panasonic.com>,
	Vijay Devarapalli <vijay.devarapalli@AzaireNet.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Alex,

> I do, I think the text to be put should say something about the anycast
> address as the AAAA record for an fqdn of HA.  I think it should also
> say something about IPsec using anycast addresses and, if impossible -
> why, then IANA-reserve an apparently-anycast (not really anycast)
> address that works ok with IPsec.
>

I don't think the anycast address should be included in the quad A record 
for an HA. If an HA is advertised in the DNS, then the address should be the 
address for that HA, just as for any other node. Otherwise, the semantics of 
what is an not a quad A for an HA become muddy.

However, I do think that an anycast fqdn could be included in a SRV RR. The 
fqdn would resolve to an anycast address. Perhaps there is some naming 
convention on the fqdn for anycast HA addresses  (like "www" for World Wide 
Web servers or "ftp" for FTP servers). This would make the semantics clear.

Regarding IPsec using anycast addresses, I believe the idea here is that the 
MN initiates the IKE transaction with the anycast address, which then 
forwards it (using some undetermined algorithm) to an HA. The MN then 
continues the IKE transaction with the HA at the HA's unicast address. I 
don't believe that the idea is that the MN's MIP6 signaling protected with 
IPsec goes to the anycast address after the initial forwarded IKE packet. 
The node hosting the anycast address won't keep any IKE state. It just acts 
as a forwarding agent.

In any event, we'll need to check with the IKE guys whether this is an 
appropriate approach. I'm not sure whether the IKE Initiatator can switch 
destination addresses in midstream, after it has started a transaction. I 
don't think there is a security issue, because authentication happens based 
on the server cert and client credentials after the IKE_SA_INIT but there 
might be an implementation issue with how IKE implementations typically 
work.

            jak





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



From mip6-bounces@ietf.org Wed Jul 26 13:37:44 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G5nKH-0007hk-RG; Wed, 26 Jul 2006 13:37:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G5nKH-0007hf-2i
	for mip6@ietf.org; Wed, 26 Jul 2006 13:37:41 -0400
Received: from motgate2.mot.com ([144.189.100.101])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G5nKF-00067h-JD
	for mip6@ietf.org; Wed, 26 Jul 2006 13:37:41 -0400
Received: from az33exr01.mot.com (az33exr01.mot.com [10.64.251.231])
	by motgate2.mot.com (8.12.11/Motorola) with ESMTP id k6QHbO1Q021887;
	Wed, 26 Jul 2006 10:37:24 -0700 (MST)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by az33exr01.mot.com (8.13.1/8.13.0) with ESMTP id k6QHbLHQ011158;
	Wed, 26 Jul 2006 12:37:22 -0500 (CDT)
Message-ID: <44C7A850.6060403@motorola.com>
Date: Wed, 26 Jul 2006 19:37:20 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: James Kempf <kempf@docomolabs-usa.com>
Subject: Re: [Mip6] New charter item: HA assignment
References: <4D2F935F08D41A4C8866693F4F0D7C4FD4505C@lan-ex-01.panasonic.de>
	<04be01c6b008$c829d710$196115ac@dcml.docomolabsusa.com>
	<44C75A26.20602@motorola.com>
	<07b501c6b0cc$9a25e6f0$196115ac@dcml.docomolabsusa.com>
In-Reply-To: <07b501c6b0cc$9a25e6f0$196115ac@dcml.docomolabsusa.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAQAAAAQ=
X-White-List-Member: TRUE
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
Cc: mip6@ietf.org, Kilian Weniger <Kilian.Weniger@eu.panasonic.com>,
	Vijay Devarapalli <vijay.devarapalli@AzaireNet.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

James Kempf wrote:
> Alex,
> 
>> I do, I think the text to be put should say something about the 
>> anycast address as the AAAA record for an fqdn of HA.  I think it 
>> should also say something about IPsec using anycast addresses and,
>>  if impossible - why, then IANA-reserve an apparently-anycast (not
>>  really anycast) address that works ok with IPsec.
>> 
> 
> I don't think the anycast address should be included in the quad A 
> record for an HA. If an HA is advertised in the DNS, then the address
>  should be the address for that HA, just as for any other node. 
> Otherwise, the semantics of what is an not a quad A for an HA become
>  muddy.

I'm not sure about the semantics of quad A being confused(?) Is the
definition of quad A saying it MUST be a unicast address? or just that
it has to be 128bit long?  I thought one can put a multicast 128bit
address as a quad A (and a 32bit multicast as A).

> However, I do think that an anycast fqdn could be included in a SRV 
> RR. The fqdn would resolve to an anycast address.

Now I'm confused.  If the fqdn resolves into an anycast address then the
only way to achieve that is to have the anycast addres as quad A, no?

> Perhaps there is some naming convention on the fqdn for anycast HA 
> addresses  (like "www" for World Wide Web servers or "ftp" for FTP 
> servers). This would make the semantics clear.

Last time I checked the SRV RFC there wasn't one.

> Regarding IPsec using anycast addresses, I believe the idea here is 
> that the MN initiates the IKE transaction with the anycast address, 
> which then forwards it (using some undetermined algorithm) to an HA.
> The MN then continues the IKE transaction with the HA at the HA's 
> unicast address. I don't believe that the idea is that the MN's MIP6
>  signaling protected with IPsec goes to the anycast address after the
>  initial forwarded IKE packet. The node hosting the anycast address 
> won't keep any IKE state. It just acts as a forwarding agent.

The node hosting the anycast address may become a single point of 
failure, that's why the anycast address should be "hosted" by each HA, no?

In a way, it is even possible to define a new multicast address, to 
which all HAs subscribe, valid on the home link, and the MN does 
IPsec'ed DHAAD Request to that multicast address; provided that IPsec 
implementation accepts a multicast address as part of the SA.

> In any event, we'll need to check with the IKE guys whether this is 
> an appropriate approach. I'm not sure whether the IKE Initiatator can
>  switch destination addresses in midstream, after it has started a 
> transaction. I don't think there is a security issue, because 
> authentication happens based on the server cert and client 
> credentials after the IKE_SA_INIT but there might be an 
> implementation issue with how IKE implementations typically work.

Yes.

Alex


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



From mip6-bounces@ietf.org Wed Jul 26 13:45:31 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G5nRr-0005f3-C6; Wed, 26 Jul 2006 13:45:31 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G5nRp-0005ey-PR
	for mip6@ietf.org; Wed, 26 Jul 2006 13:45:29 -0400
Received: from key1.docomolabs-usa.com ([216.98.102.225]
	helo=fridge.docomolabs-usa.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G5nRo-00076I-Cj
	for mip6@ietf.org; Wed, 26 Jul 2006 13:45:29 -0400
Message-ID: <089f01c6b0db$92ba09f0$196115ac@dcml.docomolabsusa.com>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Alexandru Petrescu" <alexandru.petrescu@motorola.com>
References: <4D2F935F08D41A4C8866693F4F0D7C4FD4505C@lan-ex-01.panasonic.de>
	<04be01c6b008$c829d710$196115ac@dcml.docomolabsusa.com>
	<44C75A26.20602@motorola.com>
	<07b501c6b0cc$9a25e6f0$196115ac@dcml.docomolabsusa.com>
	<44C7A850.6060403@motorola.com>
Subject: Re: [Mip6] New charter item: HA assignment
Date: Wed, 26 Jul 2006 10:47:33 -0700
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=response
Content-Transfer-Encoding: 7bit
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Cc: mip6@ietf.org, Kilian Weniger <Kilian.Weniger@eu.panasonic.com>,
	Vijay Devarapalli <vijay.devarapalli@AzaireNet.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Alex

> I'm not sure about the semantics of quad A being confused(?) Is the
> definition of quad A saying it MUST be a unicast address? or just that
> it has to be 128bit long?  I thought one can put a multicast 128bit
> address as a quad A (and a 32bit multicast as A).
>

My point was if the fqdn is intended to identify an HA, then it should 
include an HA address in the quad A. If an fqdn for an anycast address 
acting as a front end for a group of HAs is desired, then it should be 
identified as such. When an application goes to resolve the fqdn, I think it 
should know what it is getting.

>> However, I do think that an anycast fqdn could be included in a SRV RR. 
>> The fqdn would resolve to an anycast address.
>
> Now I'm confused.  If the fqdn resolves into an anycast address then the
> only way to achieve that is to have the anycast addres as quad A, no?
>

See above.

>> Perhaps there is some naming convention on the fqdn for anycast HA 
>> addresses  (like "www" for World Wide Web servers or "ftp" for FTP 
>> servers). This would make the semantics clear.
>
> Last time I checked the SRV RFC there wasn't one.
>

Not for the SRV RR. For the anycast fqdn. For example:

mipanycast-625.msp.com -Anycast address for 625 subnet in msp's nettwork
ha1-625.msp.com - HA1 in 625 subnet

> The node hosting the anycast address may become a single point of failure, 
> that's why the anycast address should be "hosted" by each HA, no?
>

My understanding is that the way most anycast is deployed, the address is 
hosted by a router.

> In a way, it is even possible to define a new multicast address, to which 
> all HAs subscribe, valid on the home link, and the MN does IPsec'ed DHAAD 
> Request to that multicast address; provided that IPsec implementation 
> accepts a multicast address as part of the SA.
>

I don't know how DHAAD will help. The issue is establishing the IPsec SA 
with the home agent, not finding a home agent. The whole point of using the 
anycast is to have the home agent assigned, not selected by the MN.

           jak



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



From mip6-bounces@ietf.org Wed Jul 26 14:02:26 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G5niD-0004VC-7B; Wed, 26 Jul 2006 14:02:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G5niC-0004V7-Mq
	for mip6@ietf.org; Wed, 26 Jul 2006 14:02:24 -0400
Received: from web82012.mail.mud.yahoo.com ([66.163.178.25])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1G5niB-0008C2-9l
	for mip6@ietf.org; Wed, 26 Jul 2006 14:02:24 -0400
Received: (qmail 29275 invoked by uid 60001); 26 Jul 2006 18:02:21 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=sbcglobal.net;
	h=Message-ID:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding;
	b=lxS2LLdqZDxIAsoG+B2mYDgQdu5FRoF7rBA0j0d4QgieHbYwlzyN0iFIFl5ctd8CUjMqasE9qulHHVOUi7fI8XRy/ZnAkEiBSqONsDYdEed9RIVYkPGjtUb8mVQGMgLYP+Az2ls86J6V7Ujm42g+wKxhI9IJ+hdcZYf7awMYAa8=
	; 
Message-ID: <20060726180221.29271.qmail@web82012.mail.mud.yahoo.com>
Received: from [152.131.12.192] by web82012.mail.mud.yahoo.com via HTTP;
	Wed, 26 Jul 2006 11:02:21 PDT
Date: Wed, 26 Jul 2006 11:02:21 -0700 (PDT)
From: Greg Woodhouse <gregory.woodhouse@sbcglobal.net>
Subject: Re: [Mip6] New charter item: HA assignment
To: Alexandru Petrescu <alexandru.petrescu@motorola.com>,
	James Kempf <kempf@docomolabs-usa.com>
In-Reply-To: <44C7A850.6060403@motorola.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Cc: mip6@ietf.org, Kilian Weniger <Kilian.Weniger@eu.panasonic.com>,
	Vijay Devarapalli <vijay.devarapalli@AzaireNet.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org



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

> > 
> > I don't think the anycast address should be included in the quad A 
> > record for an HA. If an HA is advertised in the DNS, then the
> address
> >  should be the address for that HA, just as for any other node. 
> > Otherwise, the semantics of what is an not a quad A for an HA
> become
> >  muddy.
> 
> I'm not sure about the semantics of quad A being confused(?) Is the
> definition of quad A saying it MUST be a unicast address? or just
> that
> it has to be 128bit long?  I thought one can put a multicast 128bit
> address as a quad A (and a 32bit multicast as A).
> 

Way back in RFC 1034, A records are defined as identifying host
addresses. Can an anycast address be called a host address? I don't
know if DNSv6 addresses this issue (I'll have to look), but there is
certainly a problem here: The semantics of anycast addresses are not
the same as the semantics of unicast addresses, and if both are
identified by AAAA records, there is at least an implication that they
are the same sort of "thing" when they are not. On the other hand, you
may wish the FQDN in a URI to be anycast for load balancing purposes. 

Of course, this isn't really a mobility issue.

===
Gregory Woodhouse  <gregory.woodhouse@sbcglobal.net>

"Judge a man by his questions not his answers."
--Voltaire

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



From mip6-bounces@ietf.org Wed Jul 26 14:57:51 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G5oZm-0003f8-VX; Wed, 26 Jul 2006 14:57:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G5oZl-0003f3-L6
	for mip6@ietf.org; Wed, 26 Jul 2006 14:57:45 -0400
Received: from motgate2.mot.com ([144.189.100.101])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G5oZk-0004D9-2w
	for mip6@ietf.org; Wed, 26 Jul 2006 14:57:45 -0400
Received: from az33exr02.mot.com (az33exr02.mot.com [10.64.251.232])
	by motgate2.mot.com (8.12.11/Motorola) with ESMTP id k6QIvG18009036;
	Wed, 26 Jul 2006 11:57:16 -0700 (MST)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by az33exr02.mot.com (8.13.1/8.13.0) with ESMTP id k6QIvDuR014111;
	Wed, 26 Jul 2006 13:57:14 -0500 (CDT)
Message-ID: <44C7BB08.1060702@motorola.com>
Date: Wed, 26 Jul 2006 20:57:12 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: James Kempf <kempf@docomolabs-usa.com>
Subject: Re: [Mip6] New charter item: HA assignment
References: <4D2F935F08D41A4C8866693F4F0D7C4FD4505C@lan-ex-01.panasonic.de>
	<04be01c6b008$c829d710$196115ac@dcml.docomolabsusa.com>
	<44C75A26.20602@motorola.com>
	<07b501c6b0cc$9a25e6f0$196115ac@dcml.docomolabsusa.com>
	<44C7A850.6060403@motorola.com>
	<089f01c6b0db$92ba09f0$196115ac@dcml.docomolabsusa.com>
In-Reply-To: <089f01c6b0db$92ba09f0$196115ac@dcml.docomolabsusa.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAQAAAAQ=
X-White-List-Member: TRUE
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 944ecb6e61f753561f559a497458fb4f
Cc: mip6@ietf.org, Kilian Weniger <Kilian.Weniger@eu.panasonic.com>,
	Vijay Devarapalli <vijay.devarapalli@AzaireNet.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

James Kempf wrote:
> Alex
> 
>> I'm not sure about the semantics of quad A being confused(?) Is the
>>  definition of quad A saying it MUST be a unicast address? or just 
>> that it has to be 128bit long?  I thought one can put a multicast 
>> 128bit address as a quad A (and a 32bit multicast as A).
>> 
> 
> My point was if the fqdn is intended to identify an HA, then it 
> should include an HA address in the quad A. If an fqdn for an anycast
>  address acting as a front end for a group of HAs is desired, then it
>  should be identified as such. When an application goes to resolve 
> the fqdn, I think it should know what it is getting.
> 
>>> However, I do think that an anycast fqdn could be included in a 
>>> SRV RR. The fqdn would resolve to an anycast address.
>> 
>> Now I'm confused.  If the fqdn resolves into an anycast address 
>> then the only way to achieve that is to have the anycast addres as 
>> quad A, no?
>> 
> 
> See above.
> 
>>> Perhaps there is some naming convention on the fqdn for anycast 
>>> HA addresses  (like "www" for World Wide Web servers or "ftp" for
>>>  FTP servers). This would make the semantics clear.
>> 
>> Last time I checked the SRV RFC there wasn't one.
>> 
> 
> Not for the SRV RR. For the anycast fqdn. For example:
> 
> mipanycast-625.msp.com -Anycast address for 625 subnet in msp's 
> nettwork ha1-625.msp.com - HA1 in 625 subnet
> 
>> The node hosting the anycast address may become a single point of 
>> failure, that's why the anycast address should be "hosted" by each 
>> HA, no?
>> 
> 
> My understanding is that the way most anycast is deployed, the 
> address is hosted by a router.

If deploying anycast needs a single point of failure then I'd suggest
not using anycast addresses for DHAAD.  I.e. modify DHAAD such that it
does not use anycast addressing at all.

The implementation is really straightforward.  Decide on a unique
address to be assigned on every HA, with the prefix of the home link.
Assign this address on every HA (in addition to the unique
EUID-64+prefix address).  Have IPsec SA on MN between its HoA and this
address.  The rest will work.  The HAs synchronize themselves about who
should reply and who should not, the MN chooses the MN at top of list.

>> In a way, it is even possible to define a new multicast address, to
>>  which all HAs subscribe, valid on the home link, and the MN does 
>> IPsec'ed DHAAD Request to that multicast address; provided that 
>> IPsec implementation accepts a multicast address as part of the SA.
>> 
>> 
>> 
>> 
>> 
> 
> I don't know how DHAAD will help. The issue is establishing the IPsec
>  SA with the home agent, not finding a home agent. The whole point of
>  using the anycast is to have the home agent assigned, not selected 
> by the MN.

James, let me detour here.

I don't see the link between the necessity of anycast addresses and the
necessity of assigning the HA.  DHAAD already does anycast and DHAAD can
help achieve the result of assigning the HA.

HA stops responding BAck, change preferences in RAs so a different HA
gets on top of the list.  Then MN does DHAAD and obtains the address of
a different HA (the address that operator decide to be on top of the
list).  Alternatively, HA instead of stopping BAck to provoke MN to do
DHAAD, it  can send a ha-switch-like message to MN to instruct it to do
DHAAD.  There can even be a "Unsolicited DHAAD Reply" periodic message,
just like unsolicited NA.

Analogically, DHCP works this way:  Server sends Reconfigure to Client
and Client initiates a new transaction to obtain whatever new parameters
the admin decides to re-number.  DHCPv6 does not seem to have a
mechanism for a Server to assign another Server to a Client.

Re the operator needs to _enforce_ an HA to a MN, not
giving it any option.  A protocol with similar semantics is Router
Renumbering.  An admin propagates a Router Renumbering message to a
bunch of routers.  But even then the router to be renumbered has the
freedom to execute it or not.  (1) there is a Result Message sent by the
router back to admin.  (2) prior to executing the command, the router
must successfully match-prefix with a prefix in its routing table (if
that prefix is not in its table because ospf might have removed it, the
renumbering fails).

Assigning the HA should happen this way too (like in DHCP: HA sends a
trigger and MN initiates the reconfiguration, like in RouterRenum: MN
has freedom to execute a received command or not).

My two cents worth,

Alex

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



From mip6-bounces@ietf.org Wed Jul 26 15:22:23 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G5oxX-0007bb-Ix; Wed, 26 Jul 2006 15:22:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G5oxW-0007bW-3z
	for mip6@ietf.org; Wed, 26 Jul 2006 15:22:18 -0400
Received: from mail1.azairenet.com ([66.92.223.4] helo=bart.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G5oxU-00075m-QM
	for mip6@ietf.org; Wed, 26 Jul 2006 15:22:18 -0400
Received: from [10.1.201.0] ([10.1.201.0]) by bart.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Wed, 26 Jul 2006 12:22:15 -0700
Message-ID: <44C7C078.7060801@azairenet.com>
Date: Wed, 26 Jul 2006 12:20:24 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.2 (X11/20060516)
MIME-Version: 1.0
To: James Kempf <kempf@docomolabs-usa.com>
Subject: Re: [Mip6] New charter item: HA assignment
References: <4D2F935F08D41A4C8866693F4F0D7C4FD4505C@lan-ex-01.panasonic.de>
	<04be01c6b008$c829d710$196115ac@dcml.docomolabsusa.com>
	<44C75A26.20602@motorola.com>
	<07b501c6b0cc$9a25e6f0$196115ac@dcml.docomolabsusa.com>
In-Reply-To: <07b501c6b0cc$9a25e6f0$196115ac@dcml.docomolabsusa.com>
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 26 Jul 2006 19:22:15.0494 (UTC)
	FILETIME=[CD99AE60:01C6B0E8]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Cc: mip6@ietf.org, Kilian Weniger <Kilian.Weniger@eu.panasonic.com>,
	Alexandru Petrescu <alexandru.petrescu@motorola.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

James Kempf wrote:
> In any event, we'll need to check with the IKE guys whether this is an 
> appropriate approach. 

Francis did check with the IPsec folks before
draft-dupont-ikev2-haassign was written up. there was some
discussion on the IPsec mailing list on this.

I'm not sure whether the IKE Initiatator can
> switch destination addresses in midstream, after it has started a 
> transaction. I don't think there is a security issue, because 
> authentication happens based on the server cert and client credentials 
> after the IKE_SA_INIT but there might be an implementation issue with 
> how IKE implementations typically work.

the draft uses a cookie based mechanism described in section
2.6 of RFC 4306. if an IKE implementation supports section
2.6 then there is no concern. IMO, the following is the only
difference. RFC 4306 says

    To accomplish this,
    a responder SHOULD -- when it detects a large number of half-open
    IKE_SAs -- reject initial IKE messages unless they contain a Notify
    payload of type COOKIE. It SHOULD instead send an unprotected IKE
    message as a response and include COOKIE Notify payload with the
    cookie data to be returned.

draft-dupont-ikev2-haassign says
    1.  the MN sends an IKE_SA_INIT request to the HA anycast address
    2.  the anycast receiver forwards the request to the "best" HA
    3.  the HA answers using its own address as the source address and
        includes an "under attack" cookie in its replies

the trigger at the responder for including the COOKIE Notify
payload is different.

Vijay

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



From mip6-bounces@ietf.org Wed Jul 26 15:29:27 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G5p4R-0002V6-51; Wed, 26 Jul 2006 15:29:27 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G5p4P-0002V1-Ol
	for mip6@ietf.org; Wed, 26 Jul 2006 15:29:25 -0400
Received: from mail1.azairenet.com ([66.92.223.4] helo=bart.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G5p4O-00081D-Ew
	for mip6@ietf.org; Wed, 26 Jul 2006 15:29:25 -0400
Received: from [10.1.201.0] ([10.1.201.0]) by bart.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Wed, 26 Jul 2006 12:29:22 -0700
Message-ID: <44C7C227.2050208@azairenet.com>
Date: Wed, 26 Jul 2006 12:27:35 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.2 (X11/20060516)
MIME-Version: 1.0
To: Greg Woodhouse <gregory.woodhouse@sbcglobal.net>
Subject: Re: [Mip6] New charter item: HA assignment
References: <20060726180221.29271.qmail@web82012.mail.mud.yahoo.com>
In-Reply-To: <20060726180221.29271.qmail@web82012.mail.mud.yahoo.com>
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 26 Jul 2006 19:29:22.0546 (UTC)
	FILETIME=[CC24A520:01C6B0E9]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Cc: mip6@ietf.org, Kilian Weniger <Kilian.Weniger@eu.panasonic.com>,
	James Kempf <kempf@docomolabs-usa.com>,
	Alexandru Petrescu <alexandru.petrescu@motorola.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

I don't think there is any restriction on placing an anycast
address in a AAAA record. I am not certain, though.

Vijay

Greg Woodhouse wrote:
> 
> --- Alexandru Petrescu <alexandru.petrescu@motorola.com> wrote:
> 
>>> I don't think the anycast address should be included in the quad A 
>>> record for an HA. If an HA is advertised in the DNS, then the
>> address
>>>  should be the address for that HA, just as for any other node. 
>>> Otherwise, the semantics of what is an not a quad A for an HA
>> become
>>>  muddy.
>> I'm not sure about the semantics of quad A being confused(?) Is the
>> definition of quad A saying it MUST be a unicast address? or just
>> that
>> it has to be 128bit long?  I thought one can put a multicast 128bit
>> address as a quad A (and a 32bit multicast as A).
>>
> 
> Way back in RFC 1034, A records are defined as identifying host
> addresses. Can an anycast address be called a host address? I don't
> know if DNSv6 addresses this issue (I'll have to look), but there is
> certainly a problem here: The semantics of anycast addresses are not
> the same as the semantics of unicast addresses, and if both are
> identified by AAAA records, there is at least an implication that they
> are the same sort of "thing" when they are not. On the other hand, you
> may wish the FQDN in a URI to be anycast for load balancing purposes. 
> 
> Of course, this isn't really a mobility issue.
> 
> ===
> Gregory Woodhouse  <gregory.woodhouse@sbcglobal.net>
> 
> "Judge a man by his questions not his answers."
> --Voltaire


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



From mip6-bounces@ietf.org Wed Jul 26 17:50:41 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G5rGx-0000ZX-T2; Wed, 26 Jul 2006 17:50:31 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G5rGw-0000ZM-Lu
	for mip6@ietf.org; Wed, 26 Jul 2006 17:50:30 -0400
Received: from [2001:660:7301:3192:211:43ff:fea3:7e4b]
	(helo=laposte.rennes.enst-bretagne.fr)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G5rGv-0003DW-2o
	for mip6@ietf.org; Wed, 26 Jul 2006 17:50:30 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by laposte.rennes.enst-bretagne.fr (8.13.4/8.13.4/2004.10.03) with
	ESMTP id k6QLoE9v020825; Wed, 26 Jul 2006 23:50:14 +0200
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[192.44.77.29])
	by laposte.rennes.enst-bretagne.fr (8.13.4/8.13.4/2004.09.01) with
	ESMTP id k6QLnZQx020749; Wed, 26 Jul 2006 23:49:35 +0200
Received: from givry.rennes.enst-bretagne.fr
	(localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.13.1/8.13.1) with ESMTP id
	k6QLnS3R072454; Wed, 26 Jul 2006 23:49:29 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200607262149.k6QLnS3R072454@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@point6.net>
To: "James Kempf" <kempf@docomolabs-usa.com>
Subject: Re: [Mip6] New charter item: HA assignment 
In-reply-to: Your message of Wed, 26 Jul 2006 09:00:23 PDT.
	<07b501c6b0cc$9a25e6f0$196115ac@dcml.docomolabsusa.com> 
Date: Wed, 26 Jul 2006 23:49:28 +0200
X-Virus-Scanned: amavisd-new at enst-bretagne.fr
X-Spam-Score: -2.8 (--)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Cc: mip6@ietf.org, Kilian Weniger <Kilian.Weniger@eu.panasonic.com>,
	Alexandru Petrescu <alexandru.petrescu@motorola.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   In any event, we'll need to check with the IKE guys whether this is an 
   appropriate approach.

=> as Vijay mentioned this was done.

   I'm not sure whether the IKE Initiatator can switch 
   destination addresses in midstream, after it has started a transaction.

=> in fact it can only when no state has been built (this gave the idea
behind the IKE HA assignment I-D).

Regards

Francis.Dupont@point6.net

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



From mip6-bounces@ietf.org Wed Jul 26 17:53:07 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G5rJT-0002KV-BO; Wed, 26 Jul 2006 17:53:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G5rJS-0002KQ-9Q
	for mip6@ietf.org; Wed, 26 Jul 2006 17:53:06 -0400
Received: from [2001:660:7301:3192:211:43ff:fea3:7e4b]
	(helo=laposte.rennes.enst-bretagne.fr)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G5rJR-0003U8-FB
	for mip6@ietf.org; Wed, 26 Jul 2006 17:53:06 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by laposte.rennes.enst-bretagne.fr (8.13.4/8.13.4/2004.10.03) with
	ESMTP id k6QLqL0w020972; Wed, 26 Jul 2006 23:52:21 +0200
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[192.44.77.29])
	by laposte.rennes.enst-bretagne.fr (8.13.4/8.13.4/2004.09.01) with
	ESMTP id k6QLpISq020863; Wed, 26 Jul 2006 23:51:18 +0200
Received: from givry.rennes.enst-bretagne.fr
	(localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.13.1/8.13.1) with ESMTP id
	k6QLpIiL072472; Wed, 26 Jul 2006 23:51:18 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200607262151.k6QLpIiL072472@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@point6.net>
To: Alexandru Petrescu <alexandru.petrescu@motorola.com>
Subject: Re: [Mip6] New charter item: HA assignment 
In-reply-to: Your message of Wed, 26 Jul 2006 19:37:20 +0200.
	<44C7A850.6060403@motorola.com> 
Date: Wed, 26 Jul 2006 23:51:18 +0200
X-Virus-Scanned: amavisd-new at enst-bretagne.fr
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de
Cc: mip6@ietf.org, Kilian Weniger <Kilian.Weniger@eu.panasonic.com>,
	James Kempf <kempf@docomolabs-usa.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   provided that IPsec 
   implementation accepts a multicast address as part of the SA.
   
=> it should not in this context...

Regards

Francis.Dupont@point6.net

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



From mip6-bounces@ietf.org Wed Jul 26 17:54:55 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G5rLC-0003Rp-Rj; Wed, 26 Jul 2006 17:54:54 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G5rLB-0003Rk-64
	for mip6@ietf.org; Wed, 26 Jul 2006 17:54:53 -0400
Received: from [2001:660:7301:3192:211:43ff:fea3:7e4b]
	(helo=laposte.rennes.enst-bretagne.fr)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G5rLA-0003YG-Fs
	for mip6@ietf.org; Wed, 26 Jul 2006 17:54:53 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by laposte.rennes.enst-bretagne.fr (8.13.4/8.13.4/2004.10.03) with
	ESMTP id k6QLsbNB021226; Wed, 26 Jul 2006 23:54:37 +0200
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[192.44.77.29])
	by laposte.rennes.enst-bretagne.fr (8.13.4/8.13.4/2004.09.01) with
	ESMTP id k6QLrEhh021115; Wed, 26 Jul 2006 23:53:14 +0200
Received: from givry.rennes.enst-bretagne.fr
	(localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.13.1/8.13.1) with ESMTP id
	k6QLrEkt072488; Wed, 26 Jul 2006 23:53:14 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200607262153.k6QLrEkt072488@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@point6.net>
To: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
Subject: Re: [Mip6] New charter item: HA assignment 
In-reply-to: Your message of Wed, 26 Jul 2006 12:20:24 PDT.
	<44C7C078.7060801@azairenet.com> 
Date: Wed, 26 Jul 2006 23:53:14 +0200
X-Virus-Scanned: amavisd-new at enst-bretagne.fr
X-Spam-Score: -2.8 (--)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Cc: mip6@ietf.org, Kilian Weniger <Kilian.Weniger@eu.panasonic.com>,
	James Kempf <kempf@docomolabs-usa.com>,
	Alexandru Petrescu <alexandru.petrescu@motorola.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   James Kempf wrote:
   > In any event, we'll need to check with the IKE guys whether this is an 
   > appropriate approach. 
   
   Francis did check with the IPsec folks before
   draft-dupont-ikev2-haassign was written up. there was some
   discussion on the IPsec mailing list on this.
   
   I'm not sure whether the IKE Initiatator can
   > switch destination addresses in midstream, after it has started a 
   > transaction. I don't think there is a security issue, because 
   > authentication happens based on the server cert and client credentials 
   > after the IKE_SA_INIT but there might be an implementation issue with 
   > how IKE implementations typically work.
   
   the draft uses a cookie based mechanism described in section
   2.6 of RFC 4306. if an IKE implementation supports section
   2.6 then there is no concern. IMO, the following is the only
   difference. RFC 4306 says
   
       To accomplish this,
       a responder SHOULD -- when it detects a large number of half-open
       IKE_SAs -- reject initial IKE messages unless they contain a Notify
       payload of type COOKIE. It SHOULD instead send an unprotected IKE
       message as a response and include COOKIE Notify payload with the
       cookie data to be returned.
   
   draft-dupont-ikev2-haassign says
       1.  the MN sends an IKE_SA_INIT request to the HA anycast address
       2.  the anycast receiver forwards the request to the "best" HA
       3.  the HA answers using its own address as the source address and
           includes an "under attack" cookie in its replies
   
   the trigger at the responder for including the COOKIE Notify
   payload is different.
   
Thanks Vijay! BTW this mechanism provides assignment and HA switch
re-assignment, so they should cover all scenarios, shouldn't they?

Francis.Dupont@point6.net

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



From mip6-bounces@ietf.org Wed Jul 26 17:55:01 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G5rLJ-0003VV-5U; Wed, 26 Jul 2006 17:55:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G5rLH-0003Ud-6s
	for mip6@ietf.org; Wed, 26 Jul 2006 17:54:59 -0400
Received: from [2001:660:7301:3192:211:43ff:fea3:7e4b]
	(helo=laposte.rennes.enst-bretagne.fr)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G5rLG-0003YV-Md
	for mip6@ietf.org; Wed, 26 Jul 2006 17:54:59 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by laposte.rennes.enst-bretagne.fr (8.13.4/8.13.4/2004.10.03) with
	ESMTP id k6QLslZR021328; Wed, 26 Jul 2006 23:54:47 +0200
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[192.44.77.29])
	by laposte.rennes.enst-bretagne.fr (8.13.4/8.13.4/2004.09.01) with
	ESMTP id k6QLsWXL021179; Wed, 26 Jul 2006 23:54:32 +0200
Received: from givry.rennes.enst-bretagne.fr
	(localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.13.1/8.13.1) with ESMTP id
	k6QLsVma072499; Wed, 26 Jul 2006 23:54:31 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200607262154.k6QLsVma072499@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@point6.net>
To: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
Subject: Re: [Mip6] New charter item: HA assignment 
In-reply-to: Your message of Wed, 26 Jul 2006 12:27:35 PDT.
	<44C7C227.2050208@azairenet.com> 
Date: Wed, 26 Jul 2006 23:54:31 +0200
X-Virus-Scanned: amavisd-new at enst-bretagne.fr
X-Spam-Score: -2.8 (--)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Cc: Kilian Weniger <Kilian.Weniger@eu.panasonic.com>,
	James Kempf <kempf@docomolabs-usa.com>,
	Alexandru Petrescu <alexandru.petrescu@motorola.com>, mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   I don't think there is any restriction on placing an anycast
   address in a AAAA record. I am not certain, though.
   
=> I agree. IMHO the only constraint is that the client should be
ready to get an anycast address.

Regards

Francis.Dupont@point6.net

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



From mip6-bounces@ietf.org Wed Jul 26 18:01:52 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G5rRu-0008MC-LG; Wed, 26 Jul 2006 18:01:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G5rRs-0008M7-IY
	for mip6@ietf.org; Wed, 26 Jul 2006 18:01:48 -0400
Received: from [2001:660:7301:3192:211:43ff:fea3:7e4b]
	(helo=laposte.rennes.enst-bretagne.fr)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G5rRs-00054D-1m
	for mip6@ietf.org; Wed, 26 Jul 2006 18:01:48 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by laposte.rennes.enst-bretagne.fr (8.13.4/8.13.4/2004.10.03) with
	ESMTP id k6QM1hil021801; Thu, 27 Jul 2006 00:01:43 +0200
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[192.44.77.29])
	by laposte.rennes.enst-bretagne.fr (8.13.4/8.13.4/2004.09.01) with
	ESMTP id k6QM07JS021700; Thu, 27 Jul 2006 00:00:07 +0200
Received: from givry.rennes.enst-bretagne.fr
	(localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.13.1/8.13.1) with ESMTP id
	k6QM06qs072546; Thu, 27 Jul 2006 00:00:06 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200607262200.k6QM06qs072546@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@point6.net>
To: "Jean-Michel Combes" <jeanmichel.combes@gmail.com>
Subject: Re: [Mip6] New charter item: HA assignment 
In-reply-to: Your message of Thu, 20 Jul 2006 18:06:04 +0200.
	<729b68be0607200906g427688b1l2b127997fb3ba9b4@mail.gmail.com> 
Date: Thu, 27 Jul 2006 00:00:06 +0200
X-Virus-Scanned: amavisd-new at enst-bretagne.fr
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>,
	James Kempf <kempf@docomolabs-usa.com>,
	Alexandru Petrescu <alexandru.petrescu@motorola.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   BTW, be careful with the update of the DNS:
   - if DNSSEC is used: real-time update not possible

=> this is not true: it works but as it needs the key online usually
it is considered as not very desirable.

   - take account the time the update will be propagated to the secondary
   servers/cache DNS
   
=> I fact the reason to not use dynamic upate of SRV RRs for load balancing
is already explained in RFC 2782, so why not follow the explicit
not recommendation about this?

   Maybe too depend to a specific service: I am not sure that IPsec guys
   will accept such an addition in IKEv2.
   
=> not MIPv6 guys are already tired by random proposals to addition to
their protocols by MIPv6 guys (:-)...

Regards

Francis.Dupont@point6.net

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



From mip6-bounces@ietf.org Wed Jul 26 20:13:42 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G5tVM-0008DF-59; Wed, 26 Jul 2006 20:13:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G5tVK-0008D6-N5
	for mip6@ietf.org; Wed, 26 Jul 2006 20:13:30 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G5q7S-0000N8-JZ
	for mip6@ietf.org; Wed, 26 Jul 2006 16:36:38 -0400
Received: from key1.docomolabs-usa.com ([216.98.102.225]
	helo=fridge.docomolabs-usa.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1G5pxa-0000vK-4n
	for mip6@ietf.org; Wed, 26 Jul 2006 16:26:26 -0400
Message-ID: <094e01c6b0f2$14a91f80$196115ac@dcml.docomolabsusa.com>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Alexandru Petrescu" <alexandru.petrescu@motorola.com>
References: <4D2F935F08D41A4C8866693F4F0D7C4FD4505C@lan-ex-01.panasonic.de>
	<04be01c6b008$c829d710$196115ac@dcml.docomolabsusa.com>
	<44C75A26.20602@motorola.com>
	<07b501c6b0cc$9a25e6f0$196115ac@dcml.docomolabsusa.com>
	<44C7A850.6060403@motorola.com>
	<089f01c6b0db$92ba09f0$196115ac@dcml.docomolabsusa.com>
	<44C7BB08.1060702@motorola.com>
Subject: Re: [Mip6] New charter item: HA assignment
Date: Wed, 26 Jul 2006 13:28:40 -0700
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=response
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Cc: mip6@ietf.org, Kilian Weniger <Kilian.Weniger@eu.panasonic.com>,
	Vijay Devarapalli <vijay.devarapalli@AzaireNet.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

> If deploying anycast needs a single point of failure then I'd suggest
> not using anycast addresses for DHAAD.  I.e. modify DHAAD such that it
> does not use anycast addressing at all.
>
> The implementation is really straightforward.  Decide on a unique
> address to be assigned on every HA, with the prefix of the home link.
> Assign this address on every HA (in addition to the unique
> EUID-64+prefix address).  Have IPsec SA on MN between its HoA and this
> address.  The rest will work.  The HAs synchronize themselves about who
> should reply and who should not, the MN chooses the MN at top of list.
>

I think Francis' way of doing it is simpler. The operater can deploy the 
anycast address wherever they want, and use it as a front end to a 
collection of HAs.

> I don't see the link between the necessity of anycast addresses and the
> necessity of assigning the HA.  DHAAD already does anycast and DHAAD can
> help achieve the result of assigning the HA.
>
> HA stops responding BAck, change preferences in RAs so a different HA
> gets on top of the list.  Then MN does DHAAD and obtains the address of
> a different HA (the address that operator decide to be on top of the
> list).  Alternatively, HA instead of stopping BAck to provoke MN to do
> DHAAD, it  can send a ha-switch-like message to MN to instruct it to do
> DHAAD.  There can even be a "Unsolicited DHAAD Reply" periodic message,
> just like unsolicited NA.
>
> Analogically, DHCP works this way:  Server sends Reconfigure to Client
> and Client initiates a new transaction to obtain whatever new parameters
> the admin decides to re-number.  DHCPv6 does not seem to have a
> mechanism for a Server to assign another Server to a Client.
>
> Re the operator needs to _enforce_ an HA to a MN, not
> giving it any option.  A protocol with similar semantics is Router
> Renumbering.  An admin propagates a Router Renumbering message to a
> bunch of routers.  But even then the router to be renumbered has the
> freedom to execute it or not.  (1) there is a Result Message sent by the
> router back to admin.  (2) prior to executing the command, the router
> must successfully match-prefix with a prefix in its routing table (if
> that prefix is not in its table because ospf might have removed it, the
> renumbering fails).
>
> Assigning the HA should happen this way too (like in DHCP: HA sends a
> trigger and MN initiates the reconfiguration, like in RouterRenum: MN
> has freedom to execute a received command or not).
>
>

Well, we clearly disagree on this, Alex.


            jak 



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



From mip6-bounces@ietf.org Thu Jul 27 08:07:43 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G64e8-0005bc-L7; Thu, 27 Jul 2006 08:07:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G64e6-0005bX-DD
	for mip6@ietf.org; Thu, 27 Jul 2006 08:07:18 -0400
Received: from py-out-1112.google.com ([64.233.166.181])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G64e5-00009c-3F
	for mip6@ietf.org; Thu, 27 Jul 2006 08:07:18 -0400
Received: by py-out-1112.google.com with SMTP id t32so231690pyc
	for <mip6@ietf.org>; Thu, 27 Jul 2006 05:07:16 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=fEaHP3sW03+6lxlrKSQr0HLrDziw5h1yffz/q5j1rhY7iL4Tm3Wag4rRHkbTQySnE3pTczNhC1m27dsfB2uVhEdXJz1Tb65KB2lkLDthm9RSEh2c6+FjY/L2A4CpWoCPyoH/Edh8ib2EAFis0Y1MTpj0Ib6+gGEfdmJLiUHU9gM=
Received: by 10.35.38.17 with SMTP id q17mr13204463pyj;
	Thu, 27 Jul 2006 05:07:16 -0700 (PDT)
Received: from ?203.178.143.202? ( [203.178.143.202])
	by mx.gmail.com with ESMTP id y78sm408710pyg.2006.07.27.05.07.15;
	Thu, 27 Jul 2006 05:07:16 -0700 (PDT)
Message-ID: <44C8AC67.3060703@gmail.com>
Date: Thu, 27 Jul 2006 21:07:03 +0900
From: Ryuji Wakikawa <ryuji.wakikawa@gmail.com>
User-Agent: Thunderbird 1.5.0.4 (Macintosh/20060530)
MIME-Version: 1.0
To: Alexandru Petrescu <alexandru.petrescu@motorola.com>
Subject: Re: [Mip6] New charter item: HA assignment
References: <729b68be0607180431m773dc847qed3e7350819a8d04@mail.gmail.com>	<44BD1105.5040904@motorola.com>
	<44BD3AA6.7070906@hp.com>	<44BD5AEA.6020209@motorola.com>
	<44BE5953.6080602@hp.com>	<44BE700D.5070700@motorola.com>
	<44BE9943.7060308@hp.com> <44BF7E88.9060305@motorola.com>
In-Reply-To: <44BF7E88.9060305@motorola.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 386e0819b1192672467565a524848168
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>, Brian Haley <brian.haley@hp.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi Alex

Brian seems not to respond you any more, but let me try again:-)

 From MN side, there is big difference between CN and HA,
which is home registration flag in BUL.
If MN sends BU to a HA without home flag, the HA can be treated as a CN.
Note that the HA shouldn't be one with which MN associates.

Otherwise, HA is HA, and NOT CN.

Some MN may discard BRR from its HAwhich bul entry has the home flag.

regards,
ryuji



Alexandru Petrescu wrote:
> Brian, thanks for the message.
> 
> Brian Haley wrote:
>> Alex,
>>
>>>>>>> Another way is for the new HA to send Binding Refresh Request to 
>>>>>>> MN (even if it has no BC entry for it).
>>>>>>
>>>>>> BRR is sent from CN to MN, it is not defined to be sent from HA.
>>>>>
>>>>> I think that depends on each one's interpretation of 
>>>>> "correspondent".  I see BRR very well sent by HA to MN if BCE 
>>>>> lifetime expired and BU was lost.
>>>>
>>>> I don't know how you can interpret 3775 (or implement it) such that 
>>>> a HA can be a CN of the same MN at the same time.
>>>
>>> I don't see the problem with that.
>>>
>>> For some implementations it is useful/easy to have HA send BRR to MN. 
>>> In this way MN does not need to implement additional timer of 
>>> receiving BAck, only a timer for re-transmitting BU and to respond to 
>>> BRR.
>>>
>>> Wrt to how to read rfc3775 and think that CN can be a HA, this is an 
>>> exercise indeed, but I'm tempted to do it because I also had to do it 
>>> when thinking CN can be a MN.  And, if one thinks NEMOv6 then, and MN 
>>> is a MR and MR can be a HA for mobiles in its moving network... CN 
>>> can be a HA.
>>>
>>> In the end, the BRR message should be implemented as send and receive 
>>> in any entity running Mobile IPv6: CN, HA, MH, MR.
>>
>> I'll agree to disagree.
>>
>>> Take this 3775 text:
>>>> If the sender knows that the Binding Cache entry is still in active 
>>>> use, it MAY send a Binding Refresh Request message to the mobile 
>>>> node in an attempt to avoid this overhead and latency due to 
>>>> deleting and recreating the Binding Cache entry.
>>
>> You're taking this out of context,
> 
> Brian, I tried to keep quoted text short, it was not my intention to
> confuse.  Indeed, most 3775 text about BRR specifically says CN, no BRR
> text says HA.  My point was to say that "CN" can be interpreted as "HA".
>  I agree we disagree about that.
> 
>>>> You're the HA or you aren't, and HAs don't send BRRs - TAHI would
>>>>  have a test for it if they could :)
>>>
>>> I suppose TAHI's interpretation of 3775 is that HA doesn't send BRRs. 
>>> Some implementations don't conform to TAHI then.
>>
>> There are no implementations that conform to your interpretation, at 
>> least not at any Connectathon or ETSI event I've been to.
> 
> That is a good point to know, informative, thanks.
> 
>> I didn't even implement BRR in my code since it's optional and 
>> mobility can continue without it, just not optimized.
> 
> I have same reasoning about other parts of MIP6.
> 
> Alex
> 
> 
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
> 


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



From mip6-bounces@ietf.org Thu Jul 27 08:08:26 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G64fC-0005qx-BA; Thu, 27 Jul 2006 08:08:26 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G5luR-00060E-Ji
	for mip6@ietf.org; Wed, 26 Jul 2006 12:06:55 -0400
Received: from smtp107.biz.mail.mud.yahoo.com ([68.142.200.255])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1G5luP-0006zg-PR
	for mip6@ietf.org; Wed, 26 Jul 2006 12:06:55 -0400
Received: (qmail 73739 invoked from network); 26 Jul 2006 16:06:53 -0000
Received: from unknown (HELO YEOBS)
	(boonsain.yeo@sensimesh.com@218.186.174.131 with login)
	by smtp107.biz.mail.mud.yahoo.com with SMTP; 26 Jul 2006 16:06:52 -0000
Message-ID: <03cc01c6b0cd$7f94a4b0$6901a8c0@Wavex.com>
From: "Boon Sain Yeo" <boonyeo@ieee.org>
To: <performance@msr.csm.ornl.gov>, <tchen@seas.smu.edu>,
	<sigmetrics-bb@merlot.usc.edu>, <mobisys@acm.org>, <sigmob@acm.org>,
	<announce@tcos.org>, <ccamp@ops.ietf.org>, <cnom@lrg.ufsc.br>,
	<comm-theory@ieee.org>, <dbworld@cs.wisc.edu>, <ifip_nm@bbcr.uwaterloo.ca>,
	<ifip-tc6@informatik.rwth-aachen.de>, <info-confs@comsoc.org>,
	<itc@ieee.org>, <list@4gforum.com>, <manet@ietf.org>, <mip4@ietf.org>,
	<mip6@ietf.org>, <mobicom@acm.org>, <mpls@ietf.org>,
	<multicomm@comsoc.org>, <ontc@comsoc.org>, <podc@acm.org>,
	<sigcomm-members@acm.org>, <siksleden@cs.uu.nl>, <tccc@cs.columbia.edu>,
	<tci-announce@computer.org>, <testnet@canarie.ca>
Date: Thu, 27 Jul 2006 00:06:35 +0800
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="Windows-1252";
	reply-type=original
Content-Transfer-Encoding: 7bit
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.2869
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 2086112c730e13d5955355df27e3074b
X-Mailman-Approved-At: Thu, 27 Jul 2006 08:08:24 -0400
Cc: 
Subject: [Mip6] CFP - ISWPC 2007, San Juan, Pureto Rico
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

(Apologies if you receive multiple copies of this message)

----------------------------------------------------------------------
International Symposium on Wireless Pervasive Computing 2007
                      (ISWPC 2007)

         5-7 February 2007, San Juan, Puerto Rico, USA
                 http://www.iswpc.org/2007/


                    Technically Sponsored By:
IEEE Communications Society and IEEE Vehicular Technology Society

         Hosted By: University of Puerto Rico at Mayaguez

      *** Submission Deadline  --  August 20, 2006 ****

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

SCOPE

Wireless pervasive computing is a rapidly growing area that has attracted 
significant attention due to its potential impact on the quality of 
lifestyles of individuals. To enable wireless pervasive computing, it is 
necessary to integrate technologies from the fields of communications, 
signal processing, distributed computing, and numerous other fields. The aim 
of this symposium is to provide a platform for researchers in the area of 
wireless pervasive computing and related areas to showcase their results, 
launch new ideas, as well as to interact with colleagues from these areas.

The scope of the symposium covers all enabling technologies of wireless 
pervasive computing. This includes a huge variety of topics ranging from 
wireless communications and networking to services and applications of 
pervasive computing. A series of panel and tutorials will also seek to 
inform and invoke interaction among researchers which are interested in this 
area.

----------------------------------------------------------------------
TOPICS OF INTEREST (INCLUDE BUT ARE NOT LIMITED TO THE FOLLOWING)

- Ad hoc networks
- Air interfaces (e.g. CDMA, OFDM, TDMA)
- Bluetooth technologies
- Coding and modulation techniques
- Cognitive radio
- Cooperative communications technologies
- Cross-layer design
- Detection and estimation
- Diversity techniques & equalization
- Dynamic spectrum management
- Healthcare applications
- Hybrid wireless networks
- Interference avoidance
- Interoperation of WLAN and other wireless systems
- Localization and tracking techniques
- Location management techniques Middleware
- MIMO systems
- Multimedia systems
- Multirate and multicarrier communications
- Multi-user Detection
- PCS, GPRS, EDGE, 3GPP, UMTS, GSM and B3G systems
- Power control Programmable radio
- Propagation and channel characterization
- QoS Support in wireless systems
- Resource management and interference management
- RF systems Security applications
- Signal processing
- Signal separation and interference rejection
- Speech and video processing
- Switching and routing techniques
- UWB
- Wearable devices
- WiMAX
- Wireless access techniques
- Wireless multicasting
- Wireless multimedia
- Wireless network architecture
- Wireless security
- Wireless sensor networks
- Wireless systems design
- WLANs and WPANs

----------------------------------------------------------------------
PAPER SUBMISSION GUIDELINES

Acceptance will be based on an extended abstract of about 1500 words (two 
pages in the standard IEEE conference format). The extended abstract should 
include diagrams, initial results, and details required for the reviewers to 
assess the contribution of your work. A short summary of approximately 150 
words is also required at the time of submission of the extended abstract. 
Extended abstracts must be submitted electronically by August 20, 2006 , via 
EDAS (http://edas.info). Proceedings of the conference will be available on 
IEEE Xplore after the event.

----------------------------------------------------------------------
PANEL SESSIONS & TUTORIALS

Proposals for Tutorial and Panel Sessions are also being solicited. 
Tutorials (half-day or full-day sessions) are intended to provide in-depth 
learning on a specific topic of interest to the participants. Panel sessions 
are 60 minutes long. They present leaders in a particular area discussing a 
topic of interest within the scope of the symposium. Proposals for Tutorials 
and Panel sessions should consist of 1000 words summary, a 150 word 
abstract, and a cover page listing the details of the author(s). For further 
details, please contact either the Tutorial Chair, Prof. Xiaoyan Hong 
(hxy@cs.ua.edu), or Panel Chair, Prof. Wilson Rivera (wrivera@ece.uprm.edu).

----------------------------------------------------------------------
IMPORTANT DATES

Submission of Papers, proposals for tutorials and panel sessions:
=>  August 20, 2006
Notification of Acceptance:
=>  October 1, 2006
Submission of camera-ready versions of accepted papers:
=>  November 18, 2006

----------------------------------------------------------------------
                        http://www.iswpc.org/2007/
----------------------------------------------------------------------





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



From mip6-bounces@ietf.org Thu Jul 27 08:45:01 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G65EZ-0003zk-6y; Thu, 27 Jul 2006 08:44:59 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G65EX-0003vp-Ju
	for mip6@ietf.org; Thu, 27 Jul 2006 08:44:57 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G65EX-0003VR-Hh
	for mip6@ietf.org; Thu, 27 Jul 2006 08:44:57 -0400
Received: from motgate4.mot.com ([144.189.100.102])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1G658b-0002Cj-S6
	for mip6@ietf.org; Thu, 27 Jul 2006 08:38:51 -0400
Received: from az33exr02.mot.com (az33exr02.mot.com [10.64.251.232])
	by motgate4.mot.com (8.12.11/Motorola) with ESMTP id k6RCcfh0016177;
	Thu, 27 Jul 2006 05:38:42 -0700 (MST)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by az33exr02.mot.com (8.13.1/8.13.0) with ESMTP id k6RCcd4W023966;
	Thu, 27 Jul 2006 07:38:40 -0500 (CDT)
Message-ID: <44C8B3CE.7080501@motorola.com>
Date: Thu, 27 Jul 2006 14:38:38 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: Ryuji Wakikawa <ryuji.wakikawa@gmail.com>
Subject: Re: [Mip6] New charter item: HA assignment
References: <729b68be0607180431m773dc847qed3e7350819a8d04@mail.gmail.com>	<44BD1105.5040904@motorola.com>
	<44BD3AA6.7070906@hp.com>	<44BD5AEA.6020209@motorola.com>
	<44BE5953.6080602@hp.com>	<44BE700D.5070700@motorola.com>
	<44BE9943.7060308@hp.com> <44BF7E88.9060305@motorola.com>
	<44C8AC67.3060703@gmail.com>
In-Reply-To: <44C8AC67.3060703@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAQAAAAQ=
X-White-List-Member: TRUE
X-Spam-Score: -2.6 (--)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>, Brian Haley <brian.haley@hp.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Ryuji Wakikawa wrote:
> Hi Alex
> 
> Brian seems not to respond you any more, but let me try again:-)

That's fine :-)

> From MN side, there is big difference between CN and HA, which is
> home registration flag in BUL. If MN sends BU to a HA without home
> flag, the HA can be treated as a CN. Note that the HA shouldn't be
> one with which MN associates.

That is right.  MN puts a specific flag in BU to HA, and not to CN.  But 
BRR is sent by CN (not by MN).  Anyways.

> Otherwise, HA is HA, and NOT CN.

Ok.

> Some MN may discard BRR from its HAwhich bul entry has the home flag.

Is this requested to happen so?  Is this behaviour a MUST, a SHOULD, a MAY?

Alex


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



From mip6-bounces@ietf.org Thu Jul 27 11:26:57 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G67lD-0005Ki-H4; Thu, 27 Jul 2006 11:26:51 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G67lC-0005Kd-2p
	for mip6@ietf.org; Thu, 27 Jul 2006 11:26:50 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G64i3-0000L7-Ur
	for mip6@ietf.org; Thu, 27 Jul 2006 08:11:23 -0400
Received: from py-out-1112.google.com ([64.233.166.176])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1G64Xj-0001J9-8J
	for mip6@ietf.org; Thu, 27 Jul 2006 08:00:45 -0400
Received: by py-out-1112.google.com with SMTP id s49so227618pyc
	for <mip6@ietf.org>; Thu, 27 Jul 2006 05:00:40 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=KS8n8ZmiU2IAd/inOMClxzC0MnNeQclDMeiWjYhTQPzD8zCKoWQNlCXQ77o9uoaWY75Ybe/4TaGzqJ3Zl9oT+2Z4X9gPgJDrzB81xAIsJo9emeEZck6lS7JDcEwkhk8tHNL2ns1MdZ1KXBSXsTUNV+CQRFpsitbsSZVJFxffe3o=
Received: by 10.35.60.15 with SMTP id n15mr13073542pyk;
	Thu, 27 Jul 2006 05:00:39 -0700 (PDT)
Received: from ?203.178.143.202? ( [203.178.143.202])
	by mx.gmail.com with ESMTP id i64sm400239pye.2006.07.27.05.00.38;
	Thu, 27 Jul 2006 05:00:39 -0700 (PDT)
Message-ID: <44C8AAD0.8030803@gmail.com>
Date: Thu, 27 Jul 2006 21:00:16 +0900
From: Ryuji Wakikawa <ryuji.wakikawa@gmail.com>
User-Agent: Thunderbird 1.5.0.4 (Macintosh/20060530)
MIME-Version: 1.0
To: Francis Dupont <Francis.Dupont@point6.net>
Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
References: <200607251357.k6PDv1xT065992@givry.rennes.enst-bretagne.fr>
In-Reply-To: <200607251357.k6PDv1xT065992@givry.rennes.enst-bretagne.fr>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
X-Spam-Score: -2.5 (--)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Cc: mip6@ietf.org, James Kempf <kempf@docomolabs-usa.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi Francis and all.

First of all, i think the dormant mode is useful in some scenario.

And, I agree with Francis here. The experimental RFC sounds reasonable.
This is easiest way to achieve the dormant mode on MN, IMO.

BTW, we should not define new method to lengthen the BC lifetime, other
than BU.
It is hard to predict how much time MN needs for the dormant mode.
Re-sending BU or freezing lifetime value is better.

regards,
ryuji

Francis Dupont wrote:
> I've not so arbitrary pick up one of the messages to answer...
>
> IMHO there are three issues to address: DPD, SA lifetimes, BCE.
>
> About Dead Peer Detection, RFC 4306 is very flexible. I believe there is
> no reason in this case to have each peer polling the other, i.e., one sends
> polls and says its peer is dead when it doesn't receive a small number of
> acks in a row, the other says its peer is dead when it doesn't receive a
> small (perhaps a bit larger) number of polls in a row.
> We have already in practice the HA in a passive mode, i.e., it is *never*
> the IKE initiator. To make the MN the active polling side and the HA the
> passive one seems the right way to go (but I'll come back about DPD).
>
> Security Association lifetimes: IKEv1 can negociate them but this is a
> major operational issue to get this right. IKEv2 relies on the config
> so the idea should be to have a good config. BTW at least the IKE SA
> lifetime should be in the PAD so there is no issue to put a large value
> (i.e., almost infinite) on a HA for MNs but not for other HAs.
> Again we need only rekeys initiated by one side, of course this side
> should be the MN, i.e., HAs should use almost infinite lifetimes.
>
> What is the real limit? The only thing which really requires a rekey
> is the sequence number exhaution but smaller sequence numbers are on
> 32 bits: I can't see an issue for low traffic SAs, i.e., the IKE SA,
> the BU/BA transport SA, the HOTI/HOT SA, etc. The only problem can
> be with a payload SA when the MN should actively rekey in time, so
> IMHO the only case we can be in trouble (but in fact independtly of IPsec)
> is a dormant node receiving a lot of protected traffic...
>
> BCE: even very unreasonable BCE lifetimes are a bit small (a few days,
> 16 bit value in 4 second unit). If we add something IMHO this is the first
> place as the MIPv6 code can really take benefit to know the node is dormant.
>
> Come back to DPD: a passive DPD should have a good way to distinguish
> between a dormant and a dead node so I propose to add a new "private
> status" notification in DPD poll with in the data the delay to the next
> poll in second. So the passive DPD code becomes very easy to implement,
> and a MN going to the dormant node has only to send a poll with a large
> delay and wait for the ack. BTW this needs only a document, and an
> experimental RFC if we prefer a "IANA status" type.
>
> Regards
>
> Francis.Dupont@point6.net
>
> PS: about RFC 4285, the whole story was laziness vs. security
> (or if you prefer cost vs. security)...
>
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
>
>   


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



From mip6-bounces@ietf.org Thu Jul 27 11:49:25 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G6872-0001Zp-GL; Thu, 27 Jul 2006 11:49:24 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G6870-0001Sp-0k
	for mip6@ietf.org; Thu, 27 Jul 2006 11:49:22 -0400
Received: from key1.docomolabs-usa.com ([216.98.102.225]
	helo=fridge.docomolabs-usa.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G686y-0003CR-KQ
	for mip6@ietf.org; Thu, 27 Jul 2006 11:49:21 -0400
Message-ID: <03cd01c6b194$87a34c20$5a6015ac@dcml.docomolabsusa.com>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Francis Dupont" <Francis.Dupont@point6.net>,
	"Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
References: <200607262153.k6QLrEkt072488@givry.rennes.enst-bretagne.fr>
Subject: Re: [Mip6] New charter item: HA assignment 
Date: Thu, 27 Jul 2006 08:51:31 -0700
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Cc: mip6@ietf.org, Kilian Weniger <Kilian.Weniger@eu.panasonic.com>,
	Alexandru Petrescu <alexandru.petrescu@motorola.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

> Thanks Vijay! BTW this mechanism provides assignment and HA switch
> re-assignment, so they should cover all scenarios, shouldn't they?
>

Not sure what you mean by switch reassignment, but I think there is still a 
need for a message from the HA to the MN to tell it when to switch if the HA 
is, for example, going down. The switch message may include an anycast 
address, or it may include a unicast address for specific HAs.

            jak 



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



From mip6-bounces@ietf.org Thu Jul 27 11:58:45 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G68G2-0008Ew-Tw; Thu, 27 Jul 2006 11:58:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G68G1-0008Er-QN
	for mip6@ietf.org; Thu, 27 Jul 2006 11:58:41 -0400
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G68Fz-0007kb-Ra
	for mip6@ietf.org; Thu, 27 Jul 2006 11:58:41 -0400
Received: from il06exr04.mot.com (il06exr04.mot.com [129.188.137.134])
	by motgate8.mot.com (8.12.11/Motorola) with ESMTP id k6RFwEdZ008955;
	Thu, 27 Jul 2006 08:58:14 -0700 (MST)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by il06exr04.mot.com (8.13.1/8.13.0) with ESMTP id k6RFwCiw021659;
	Thu, 27 Jul 2006 10:58:13 -0500 (CDT)
Message-ID: <44C8E293.9030205@motorola.com>
Date: Thu, 27 Jul 2006 17:58:11 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: James Kempf <kempf@docomolabs-usa.com>
Subject: Re: [Mip6] New charter item: HA assignment
References: <200607262153.k6QLrEkt072488@givry.rennes.enst-bretagne.fr>
	<03cd01c6b194$87a34c20$5a6015ac@dcml.docomolabsusa.com>
In-Reply-To: <03cd01c6b194$87a34c20$5a6015ac@dcml.docomolabsusa.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAQAAAAQ=
X-White-List-Member: TRUE
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: Francis Dupont <Francis.Dupont@point6.net>, mip6@ietf.org,
	Kilian Weniger <Kilian.Weniger@eu.panasonic.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

James Kempf wrote:
>> Thanks Vijay! BTW this mechanism provides assignment and HA switch
>> re-assignment, so they should cover all scenarios, shouldn't they?
>>
> 
> Not sure what you mean by switch reassignment, but I think there is 
> still a need for a message from the HA to the MN to tell it when to 
> switch if the HA is, for example, going down. The switch message may 
> include an anycast address, or it may include a unicast address for 
> specific HAs.

Would an Unsolicited DHAAD Reply fit the bill?

I agree there is a need for a message with the semantics you propose, 
and I do know that ha-switch is a potential good candidate.

Alex


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



From mip6-bounces@ietf.org Thu Jul 27 12:06:16 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G68NK-0007ga-Dv; Thu, 27 Jul 2006 12:06:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G68NJ-0007e6-55
	for mip6@ietf.org; Thu, 27 Jul 2006 12:06:13 -0400
Received: from key1.docomolabs-usa.com ([216.98.102.225]
	helo=fridge.docomolabs-usa.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G68NH-0003Jv-O3
	for mip6@ietf.org; Thu, 27 Jul 2006 12:06:13 -0400
Message-ID: <03f101c6b196$e5f29950$5a6015ac@dcml.docomolabsusa.com>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Alexandru Petrescu" <alexandru.petrescu@motorola.com>
References: <200607262153.k6QLrEkt072488@givry.rennes.enst-bretagne.fr>
	<03cd01c6b194$87a34c20$5a6015ac@dcml.docomolabsusa.com>
	<44C8E293.9030205@motorola.com>
Subject: Re: [Mip6] New charter item: HA assignment
Date: Thu, 27 Jul 2006 09:08:28 -0700
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=response
Content-Transfer-Encoding: 7bit
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Cc: Francis Dupont <Francis.Dupont@point6.net>, mip6@ietf.org,
	Kilian Weniger <Kilian.Weniger@eu.panasonic.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Actually, no. I was thinking of draft-ietf-mip6-ha-switch-00.txt.

        jak

----- Original Message ----- 
From: "Alexandru Petrescu" <alexandru.petrescu@motorola.com>
To: "James Kempf" <kempf@docomolabs-usa.com>
Cc: "Francis Dupont" <Francis.Dupont@point6.net>; "Vijay Devarapalli" 
<vijay.devarapalli@azairenet.com>; <mip6@ietf.org>; "Kilian Weniger" 
<Kilian.Weniger@eu.panasonic.com>
Sent: Thursday, July 27, 2006 8:58 AM
Subject: Re: [Mip6] New charter item: HA assignment


> James Kempf wrote:
>>> Thanks Vijay! BTW this mechanism provides assignment and HA switch
>>> re-assignment, so they should cover all scenarios, shouldn't they?
>>>
>>
>> Not sure what you mean by switch reassignment, but I think there is still 
>> a need for a message from the HA to the MN to tell it when to switch if 
>> the HA is, for example, going down. The switch message may include an 
>> anycast address, or it may include a unicast address for specific HAs.
>
> Would an Unsolicited DHAAD Reply fit the bill?
>
> I agree there is a need for a message with the semantics you propose, and 
> I do know that ha-switch is a potential good candidate.
>
> Alex
>
> 



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



From mip6-bounces@ietf.org Thu Jul 27 17:53:36 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G6DnP-0006wW-GE; Thu, 27 Jul 2006 17:53:31 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G6DnN-0006wN-Ni
	for mip6@ietf.org; Thu, 27 Jul 2006 17:53:29 -0400
Received: from [2001:660:7301:3192:211:43ff:fea3:7e4b]
	(helo=laposte.rennes.enst-bretagne.fr)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G6DnM-0007en-3R
	for mip6@ietf.org; Thu, 27 Jul 2006 17:53:29 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by laposte.rennes.enst-bretagne.fr (8.13.4/8.13.4/2004.10.03) with
	ESMTP id k6RLqXnx004451; Thu, 27 Jul 2006 23:52:33 +0200
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[192.44.77.29])
	by laposte.rennes.enst-bretagne.fr (8.13.4/8.13.4/2004.09.01) with
	ESMTP id k6RLqU0r004437; Thu, 27 Jul 2006 23:52:30 +0200
Received: from givry.rennes.enst-bretagne.fr
	(localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.13.1/8.13.1) with ESMTP id
	k6RLqTaH076805; Thu, 27 Jul 2006 23:52:29 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200607272152.k6RLqTaH076805@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@point6.net>
To: "James Kempf" <kempf@docomolabs-usa.com>
Subject: Re: [Mip6] New charter item: HA assignment 
In-reply-to: Your message of Thu, 27 Jul 2006 08:51:31 PDT.
	<03cd01c6b194$87a34c20$5a6015ac@dcml.docomolabsusa.com> 
Date: Thu, 27 Jul 2006 23:52:29 +0200
X-Virus-Scanned: amavisd-new at enst-bretagne.fr
X-Spam-Score: -2.8 (--)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Cc: mip6@ietf.org, Kilian Weniger <Kilian.Weniger@eu.panasonic.com>,
	Alexandru Petrescu <alexandru.petrescu@motorola.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   > Thanks Vijay! BTW this mechanism provides assignment and HA switch
   > re-assignment, so they should cover all scenarios, shouldn't they?
   
   Not sure what you mean by switch reassignment,

=> HA switch provides re-assignment (i.e., not initial assignment).

   but I think there is still a need for a message from the HA to the
   MN to tell it when to switch if the HA is, for example, going down.

=> I agree: there is a clear operational need for this.

Regards
   
Francis.Dupont@point6.net

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



From mip6-bounces@ietf.org Thu Jul 27 17:54:53 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G6Doj-00014A-Ok; Thu, 27 Jul 2006 17:54:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G6Doh-00011f-JX
	for mip6@ietf.org; Thu, 27 Jul 2006 17:54:51 -0400
Received: from [2001:660:7301:3192:211:43ff:fea3:7e4b]
	(helo=laposte.rennes.enst-bretagne.fr)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G6Dog-0007uC-2R
	for mip6@ietf.org; Thu, 27 Jul 2006 17:54:51 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by laposte.rennes.enst-bretagne.fr (8.13.4/8.13.4/2004.10.03) with
	ESMTP id k6RLs3W8004568; Thu, 27 Jul 2006 23:54:03 +0200
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[192.44.77.29])
	by laposte.rennes.enst-bretagne.fr (8.13.4/8.13.4/2004.09.01) with
	ESMTP id k6RLs2ld004559; Thu, 27 Jul 2006 23:54:02 +0200
Received: from givry.rennes.enst-bretagne.fr
	(localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.13.1/8.13.1) with ESMTP id
	k6RLs2PN076818; Thu, 27 Jul 2006 23:54:02 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200607272154.k6RLs2PN076818@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@point6.net>
To: Alexandru Petrescu <alexandru.petrescu@motorola.com>
Subject: Re: [Mip6] New charter item: HA assignment 
In-reply-to: Your message of Thu, 27 Jul 2006 17:58:11 +0200.
	<44C8E293.9030205@motorola.com> 
Date: Thu, 27 Jul 2006 23:54:02 +0200
X-Virus-Scanned: amavisd-new at enst-bretagne.fr
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: mip6@ietf.org, Kilian Weniger <Kilian.Weniger@eu.panasonic.com>,
	James Kempf <kempf@docomolabs-usa.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   James Kempf wrote:
   >> Thanks Vijay! BTW this mechanism provides assignment and HA switch
   >> re-assignment, so they should cover all scenarios, shouldn't they?
   >>
   > 
   > Not sure what you mean by switch reassignment, but I think there is 
   > still a need for a message from the HA to the MN to tell it when to 
   > switch if the HA is, for example, going down. The switch message may 
   > include an anycast address, or it may include a unicast address for 
   > specific HAs.
   
   Would an Unsolicited DHAAD Reply fit the bill?
   
=> no, the message must be protected.

Francis.Dupont@point6.net

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



From mip6-bounces@ietf.org Fri Jul 28 14:14:22 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G6Wqi-0004bY-5c; Fri, 28 Jul 2006 14:14:12 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G6Wqg-0004bK-FG
	for mip6@ietf.org; Fri, 28 Jul 2006 14:14:10 -0400
Received: from motgate2.mot.com ([144.189.100.101])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G6Wqf-0004vc-1J
	for mip6@ietf.org; Fri, 28 Jul 2006 14:14:10 -0400
Received: from az33exr01.mot.com (az33exr01.mot.com [10.64.251.231])
	by motgate2.mot.com (8.12.11/Motorola) with ESMTP id k6SIDvCZ015114;
	Fri, 28 Jul 2006 11:13:57 -0700 (MST)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by az33exr01.mot.com (8.13.1/8.13.0) with ESMTP id k6SIDs8K000304;
	Fri, 28 Jul 2006 13:13:55 -0500 (CDT)
Message-ID: <44CA53E1.20600@motorola.com>
Date: Fri, 28 Jul 2006 20:13:53 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: James Kempf <kempf@docomolabs-usa.com>
Subject: Re: [Mip6] New charter item: HA assignment
References: <200607272154.k6RLs2PN076818@givry.rennes.enst-bretagne.fr>
In-Reply-To: <200607272154.k6RLs2PN076818@givry.rennes.enst-bretagne.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAQAAAAQ=
X-White-List-Member: TRUE
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Cc: mip6@ietf.org, Kilian Weniger <Kilian.Weniger@eu.panasonic.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Francis Dupont wrote:
> In your previous mail you wrote:
> 
> James Kempf wrote:
>>>> Thanks Vijay! BTW this mechanism provides assignment and HA 
>>>> switch re-assignment, so they should cover all scenarios, 
>>>> shouldn't they?
>>> 
>>> Not sure what you mean by switch reassignment, but I think there
>>> is still a need for a message from the HA to the MN to tell it
>>> when to switch if the HA is, for example, going down. The switch
>>> message may include an anycast address, or it may include a
>>> unicast address for specific HAs.
>> 
>> Would an Unsolicited DHAAD Reply fit the bill?

> => no, the message must be protected.

I guess Reply being an unicast ICMP, could be protected.

Alex

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



From mip6-bounces@ietf.org Fri Jul 28 20:16:43 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G6cVJ-0005fj-MT; Fri, 28 Jul 2006 20:16:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G6cVI-0005fe-4c
	for mip6@ietf.org; Fri, 28 Jul 2006 20:16:28 -0400
Received: from motgate3.mot.com ([144.189.100.103])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G6cVH-0007NN-Kz
	for mip6@ietf.org; Fri, 28 Jul 2006 20:16:28 -0400
Received: from az33exr02.mot.com (az33exr02.mot.com [10.64.251.232])
	by motgate3.mot.com (8.12.11/Motorola) with ESMTP id k6T0GAhZ026720;
	Fri, 28 Jul 2006 17:16:11 -0700 (MST)
Received: from [10.169.4.67] (mvp-10-169-4-67.corp.mot.com [10.169.4.67])
	by az33exr02.mot.com (8.13.1/8.13.0) with ESMTP id k6T0FqWj007297;
	Fri, 28 Jul 2006 19:15:53 -0500 (CDT)
Message-ID: <44CAA8B6.4040807@motorola.com>
Date: Sat, 29 Jul 2006 02:15:50 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: James Kempf <kempf@docomolabs-usa.com>
Subject: Re: Comments on draft-ietf-mip6-ha-switch-00.txt (was: [Mip6] New
	charter item: HA assignment)
References: <200607262153.k6QLrEkt072488@givry.rennes.enst-bretagne.fr>
	<03cd01c6b194$87a34c20$5a6015ac@dcml.docomolabsusa.com>
	<44C8E293.9030205@motorola.com>
	<03f101c6b196$e5f29950$5a6015ac@dcml.docomolabsusa.com>
In-Reply-To: <03f101c6b196$e5f29950$5a6015ac@dcml.docomolabsusa.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAQAAAAQ=
X-White-List-Member: TRUE
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a87a9cdae4ac5d3fbeee75cd0026d632
Cc: Francis Dupont <Francis.Dupont@point6.net>, mip6@ietf.org,
	Kilian Weniger <Kilian.Weniger@eu.panasonic.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

James Kempf wrote:
> Actually, no. I was thinking of draft-ietf-mip6-ha-switch-00.txt.

The draft looks good.

It describes a message exchange between HA and MN.  A HA
Switch message (a Mobility Header) is sent by HA to MN, optionally
providing a list of alternate Home Agents.  The MN replies back with a
BU requesting deletion of the current BCE.  Subsequently the MN performs
IKE with a randomly chosen HA in the provided list or HA discovery
otherwise.  The HA Switch message uses IPsec.

Could you please clarify whether HA Switch considers only HAs on a same
home link, or can accomodate on different links too.  Because if the
latter then it's clear that a Home Address should be acquired too, in
which case ongoing sessions will be interrupted, a thing which should
absolutely be mentioned.

> A Mobile IPv6 home agent provides mobile nodes with two basic 
> services - a rendezvous server where correspondent nodes can find the
>  current care-of address for the mobile node, and as an overlay 
> router to tunnel traffic to/from the mobile node at its current 
> care-of address.

I think this is the first time I see this description of Mobile IPv6 HA.
  I like it (HA=rdv point+overlay router).

> Periodically, a mobility service provider may want to shut-down home
>  agent services at a set of IPv6 addresses and bring service back up
>  at a new set of addresses.

Makes sense.

> There are various reasons why a mobility service provider might want
>  to do this; an example is if the service provider revokes the
> account of a user it has reason to believe might use the old home
> agent address to disrupt service for other users.  With a signaling 
> message, the service provider could inform mobile nodes to look for a
>  new home agent.

Makes no sense.

It's sufficient for HA to revoke the key of a disruptive MN and it's
recommended to do that instead of renumbering its HAs and inform all
other MNs to switch, too much work.

It might have made sense if a majority of MNs were disruptive.

> The home agent addresses field should be constructed as described in 
> Section 10.5.1 of [3775].

That cited section is 2-pages long and starts with a description on how
to build a home agent list and ends with what should be put in the Home
Agent Addresses field.

What that means is basically (1) how to collect information from HA RAs
and (2) how to sort the HA addresses in the Home Agent Addresses field.

But this spec mentions scenarios "overloaded", "load balancing",
"maintenance", "functional load balancing", "HA renumbering" without
providing means to convert these words into actual Preference and
Lifetime values in the RA.  I'd have preferred that.

Also, this spec says that MN chooses randomly the HA in the HA list, so
no reason to order the list before sending it.

> 4.2 Retransmissions

It's good to have re-transmissions.

However, since their very goal is to provide reliability against packet
loss or re-ordering it would be interesting to have an id in the
message, and echoed back.

Doing so would avoid a situation where the HA sends a switch to MN
suggesting another HA1, then HA1 goes down, and HA sends another switch
with HA2 inside.  If the first switch message is lost and HA receives
BU/0 then MN has no more connectivity (because HA1 is down and HA
believes MN responded to the right switch message).

> Upon receipt of a Home Agent Switch message, the mobile node MUST 
> stop using its current home agent for services and MUST delete its 
> home binding by sending a Binding Update message as described in [2].
> 
> 
> 
I'm not sure about the MUST above, I'd rather make it a SHOULD.  Because
otherwise someone may come up with the idea that even if the HA is
loaded and needs to switch MN to another HA then MN is probably in a
situation where it absolutely wants to continue using this HA, so send
it back a new message "I don't want to switch".  When can this happen?
If MN is in the middle of a HoTI/HoT it surely doesn't want to switch HAs.

> If the Home Agent Switch message contains a list of alternate home 
> agent addresses, the mobile node SHOULD select a home agent at random
> 
> 
> 
... so no need to order the HA list (?).

My two cents worth.

Alex


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



From mip6-bounces@ietf.org Fri Jul 28 21:59:57 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G6e7O-0002or-1N; Fri, 28 Jul 2006 21:59:54 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G6e7M-0002om-0l
	for mip6@ietf.org; Fri, 28 Jul 2006 21:59:52 -0400
Received: from szxga02-in.huawei.com ([61.144.161.54])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G6e7L-000166-1Y
	for mip6@ietf.org; Fri, 28 Jul 2006 21:59:51 -0400
Received: from huawei.com (szxga02-in [172.24.2.6])
	by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0J35006BA7MYOE@szxga02-in.huawei.com> for
	mip6@ietf.org; Sat, 29 Jul 2006 10:16:11 +0800 (CST)
Received: from huawei.com ([172.24.1.18])
	by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0J3500F5C7MY9D@szxga02-in.huawei.com> for
	mip6@ietf.org; Sat, 29 Jul 2006 10:16:10 +0800 (CST)
Received: from l49370 ([10.70.67.93])
	by szxml03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTPA id <0J3500MUF6ZEA2@szxml03-in.huawei.com> for
	mip6@ietf.org; Sat, 29 Jul 2006 10:02:03 +0800 (CST)
Date: Sat, 29 Jul 2006 09:59:04 +0800
From: liujixing <liujixing@huawei.com>
Subject: Re: Comments on draft-ietf-mip6-ha-switch-00.txt (was: [Mip6]
	Newcharter item: HA assignment)
To: Alexandru Petrescu <alexandru.petrescu@motorola.com>,
	James Kempf <kempf@docomolabs-usa.com>
Message-id: <006501c6b2b2$91a859d0$5d43460a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
References: <200607262153.k6QLrEkt072488@givry.rennes.enst-bretagne.fr>
	<03cd01c6b194$87a34c20$5a6015ac@dcml.docomolabsusa.com>
	<44C8E293.9030205@motorola.com>
	<03f101c6b196$e5f29950$5a6015ac@dcml.docomolabsusa.com>
	<44CAA8B6.4040807@motorola.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 093efd19b5f651b2707595638f6c4003
Cc: Francis Dupont <Francis.Dupont@point6.net>, mip6@ietf.org,
	Kilian Weniger <Kilian.Weniger@eu.panasonic.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

 A HA Switch message  is sent by HA to MN, optionally
providing a list of alternate Home Agents. The HA Switch message may also providing a lifetime for maintaining mobility service continually. The MN can perform
IKE with a chosen HA in the provided list or HA discovery otherwise before the lifetime expires.  The HA will stop providing service to the MN when the lifetime expires.

In addition to the Mobility Header, could the ICMP message be used to send HA Switch? The ICMP message(a new type needed)  can be protected using IPSec. 

thanks.
----- Original Message ----- 
From: "Alexandru Petrescu" <alexandru.petrescu@motorola.com>
To: "James Kempf" <kempf@docomolabs-usa.com>
Cc: "Francis Dupont" <Francis.Dupont@point6.net>; <mip6@ietf.org>; "Kilian Weniger" <Kilian.Weniger@eu.panasonic.com>
Sent: Saturday, July 29, 2006 8:15 AM
Subject: Re: Comments on draft-ietf-mip6-ha-switch-00.txt (was: [Mip6] Newcharter item: HA assignment)


> James Kempf wrote:
>> Actually, no. I was thinking of draft-ietf-mip6-ha-switch-00.txt.
> 
> The draft looks good.
> 
> It describes a message exchange between HA and MN.  A HA
> Switch message (a Mobility Header) is sent by HA to MN, optionally
> providing a list of alternate Home Agents.  The MN replies back with a
> BU requesting deletion of the current BCE.  Subsequently the MN performs
> IKE with a randomly chosen HA in the provided list or HA discovery
> otherwise.  The HA Switch message uses IPsec.
> 
> Could you please clarify whether HA Switch considers only HAs on a same
> home link, or can accomodate on different links too.  Because if the
> latter then it's clear that a Home Address should be acquired too, in
> which case ongoing sessions will be interrupted, a thing which should
> absolutely be mentioned.
> 
>> A Mobile IPv6 home agent provides mobile nodes with two basic 
>> services - a rendezvous server where correspondent nodes can find the
>>  current care-of address for the mobile node, and as an overlay 
>> router to tunnel traffic to/from the mobile node at its current 
>> care-of address.
> 
> I think this is the first time I see this description of Mobile IPv6 HA.
>  I like it (HA=rdv point+overlay router).
> 
>> Periodically, a mobility service provider may want to shut-down home
>>  agent services at a set of IPv6 addresses and bring service back up
>>  at a new set of addresses.
> 
> Makes sense.
> 
>> There are various reasons why a mobility service provider might want
>>  to do this; an example is if the service provider revokes the
>> account of a user it has reason to believe might use the old home
>> agent address to disrupt service for other users.  With a signaling 
>> message, the service provider could inform mobile nodes to look for a
>>  new home agent.
> 
> Makes no sense.
> 
> It's sufficient for HA to revoke the key of a disruptive MN and it's
> recommended to do that instead of renumbering its HAs and inform all
> other MNs to switch, too much work.
> 
> It might have made sense if a majority of MNs were disruptive.
> 
>> The home agent addresses field should be constructed as described in 
>> Section 10.5.1 of [3775].
> 
> That cited section is 2-pages long and starts with a description on how
> to build a home agent list and ends with what should be put in the Home
> Agent Addresses field.
> 
> What that means is basically (1) how to collect information from HA RAs
> and (2) how to sort the HA addresses in the Home Agent Addresses field.
> 
> But this spec mentions scenarios "overloaded", "load balancing",
> "maintenance", "functional load balancing", "HA renumbering" without
> providing means to convert these words into actual Preference and
> Lifetime values in the RA.  I'd have preferred that.
> 
> Also, this spec says that MN chooses randomly the HA in the HA list, so
> no reason to order the list before sending it.
> 
>> 4.2 Retransmissions
> 
> It's good to have re-transmissions.
> 
> However, since their very goal is to provide reliability against packet
> loss or re-ordering it would be interesting to have an id in the
> message, and echoed back.
> 
> Doing so would avoid a situation where the HA sends a switch to MN
> suggesting another HA1, then HA1 goes down, and HA sends another switch
> with HA2 inside.  If the first switch message is lost and HA receives
> BU/0 then MN has no more connectivity (because HA1 is down and HA
> believes MN responded to the right switch message).
> 
>> Upon receipt of a Home Agent Switch message, the mobile node MUST 
>> stop using its current home agent for services and MUST delete its 
>> home binding by sending a Binding Update message as described in [2].
>> 
>> 
>> 
> I'm not sure about the MUST above, I'd rather make it a SHOULD.  Because
> otherwise someone may come up with the idea that even if the HA is
> loaded and needs to switch MN to another HA then MN is probably in a
> situation where it absolutely wants to continue using this HA, so send
> it back a new message "I don't want to switch".  When can this happen?
> If MN is in the middle of a HoTI/HoT it surely doesn't want to switch HAs.
> 
>> If the Home Agent Switch message contains a list of alternate home 
>> agent addresses, the mobile node SHOULD select a home agent at random
>> 
>> 
>> 
> ... so no need to order the HA list (?).
> 
> My two cents worth.
> 
> Alex
> 
> 
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
>

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



