From mip6-bounces@ietf.org Sat Oct 01 03:49:02 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ELc7B-0005Yl-Ot; Sat, 01 Oct 2005 03:49:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ELc79-0005Yg-5q
	for mip6@megatron.ietf.org; Sat, 01 Oct 2005 03:48:59 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA03283
	for <mip6@ietf.org>; Sat, 1 Oct 2005 03:48:56 -0400 (EDT)
Received: from av11-1-sn2.hy.skanova.net ([81.228.8.183])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ELcFA-0006FL-IL
	for mip6@ietf.org; Sat, 01 Oct 2005 03:57:17 -0400
Received: by av11-1-sn2.hy.skanova.net (Postfix, from userid 502)
	id 6C62538047; Sat,  1 Oct 2005 09:48:35 +0200 (CEST)
Received: from smtp4-2-sn2.hy.skanova.net (smtp4-2-sn2.hy.skanova.net
	[81.228.8.93]) by av11-1-sn2.hy.skanova.net (Postfix) with ESMTP
	id 53D943802F; Sat,  1 Oct 2005 09:48:35 +0200 (CEST)
Received: from shiraz.levkowetz.com (81-224-201-50-no45.tbcn.telia.com
	[81.224.201.50])
	by smtp4-2-sn2.hy.skanova.net (Postfix) with ESMTP id AC0EA37E44;
	Sat,  1 Oct 2005 09:48:34 +0200 (CEST)
Received: from localhost ([127.0.0.1])
	by shiraz.levkowetz.com with esmtp (Exim 4.52)
	id 1ELc6j-0008TN-U2; Sat, 01 Oct 2005 09:48:33 +0200
Message-ID: <433E3F51.4000206@levkowetz.com>
Date: Sat, 01 Oct 2005 09:48:33 +0200
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Mozilla Thunderbird 1.0.6 (Macintosh/20050716)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: franckle@cmu.edu
Subject: Re: [Mip6] Fwd: Re: draft-ietf-mip6-firewalls-02.txt
References: <50330.141.151.141.45.1128133661.squirrel@141.151.141.45>
In-Reply-To: <50330.141.151.141.45.1128133661.squirrel@141.151.141.45>
X-Enigmail-Version: 0.89.5.0
X-Enigmail-Supports: pgp-inline, pgp-mime
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: 0fa76816851382eb71b0a882ccdc29ac
Content-Transfer-Encoding: 7bit
Cc: gdommety@cisco.com, mip6@ietf.org, stefano.faccin@nokia.com,
	smb@research.att.com, 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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org



on 2005-10-01 04:27 Franck Le said the following:

>> Henrik's Review:
> [..]
>> * While the problems described in 5.1, 5.2 and 5.4 may require product and
>> protocol modifications, the problems in 5.3 have more a character of
>> installation and configuration mistakes, and should maybe be labelled as
>> such.
> 
> I agree with you. I was just afraid that we may start discussing
> solutions but we can add few sentences to highlight these
> differences. We could explain in the conclusion that "Some of the
> issues described in this document may require changes to firewalls or
> to the protocols. Others may only require the appropriate rules and
> configuration to be in place."

That might be good, but I was actually aiming for some text at the start
of 5.3 that indicated that it's in a different class, so that it's clear
when you read the text that this one is a bit different.

>> * MIPv6 permits the use of AH as an alternative to ESP in some cases - I
>> wonder if this document should cover this case, as well.  I believe that
>> AH may have less problems than ESP, but it also gives less protection.
>> ESP is in particular recommended for the HoT and HoTI messages between HA
>> and MN.
> 
> I agree with your comment and analysis. As you pointed out, AH is
> permitted in the MIPv6 spec., however it seems that the
> recommendation for ESP was stronger. For this reason, we focused on
> ESP.

Maybe add a comment (in the Security Considerations Section?) to this
effect?

<snip> points where we seem to agree

>> Section 5.3, para. 2:
>> 
>> 
>> Issue 1: If the firewall(s) block ESP traffic, many of the MIPv6 signaling
>> (e.g.  Binding Update, HoT) may be dropped ...
>> 
>> ...snip... performing Route Optimization, since Binding Update, HoT and
>> other MIPv6 signaling must be protected by IPsec ESP.
>> 
>> I don't see how this differs from Section 5.1, and don't see that it
>> belongs here.
> 
> The issues are similar as you pointed out. However the firewall in
> section 5.1 is the one protecting the MN (e.g. FW in the visited
> network) while the firewall in section 5.3 is the one protecting the
> HA.
> 
> I hope this clarifies the intentions. However I agree that the
> current text can be confusing.
> 
> Therefore, at the beginning of section 5.3, we will sub /Let's
> consider a MN moving into a network protected by firewall(s). The
> following issues may exist:/ with /In the scenarios where the Home
> Agent is in a network protected by firewall(s), the following issues
> may exist:/
> 
> and in issue 1, we will sub /If the firewall(s) block ESP traffic/ by
> /If the firewall(s) protecting the Home Agent block ESP traffic/> 
> Would this be clearer?

That might work.  I'd like to see it in context when you have a new
rev. ready.

> Thank you again for all your comments!

You're welcome :-)


	Henrik

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



From mip6-bounces@ietf.org Sat Oct 01 23:39:18 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ELuh2-0005G5-JH; Sat, 01 Oct 2005 23:39:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ELuge-0005Fl-8G
	for mip6@megatron.ietf.org; Sat, 01 Oct 2005 23:38:52 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA11580
	for <mip6@ietf.org>; Sat, 1 Oct 2005 23:38:46 -0400 (EDT)
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ELuon-0007ck-TI
	for mip6@ietf.org; Sat, 01 Oct 2005 23:47:18 -0400
Message-ID: <082e01c5c702$c810bf90$196115ac@dcml.docomolabsusa.com>
From: "James Kempf" <Kempf@docomolabs-usa.com>
To: "Vijay Devarapallli" <dvijay@gmail.com>
References: <4D2F935F08D41A4C8866693F4F0D7C4F4D5C6E@lan-ex-01.panasonic.de>
	<068401c5c5ed$c6499800$196115ac@dcml.docomolabsusa.com>
	<f1f4dcdc0509301658j18665804l61df84f6eab66ba7@mail.gmail.com>
Subject: Re: [Mip6] review of draft-ietf-mip6-bootstrapping-split-00.txt
Date: Sat, 1 Oct 2005 20:38: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: 0.0 (/)
X-Scan-Signature: 2e8fc473f5174be667965460bd5288ba
Content-Transfer-Encoding: 7bit
Cc: Gerardo Giaretta <Gerardo.Giaretta@tilab.com>, mip6@ietf.org,
	Kilian Weniger <Kilian.Weniger@eu.panasonic.com>,
	Vijay Devarapalli <vijayd@iprg.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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

I still don't see what the problem is with the text I provided.

Suppose we try an example. Let's suppose Alice's MSP is Bob's Mobile IP 
Service (domain name: bobsmova.com). Suppose Bob owns an access network that 
covers Palo Alto and Mountain View in California (actually, Bob might not 
own any access network at all, but for the moment, let's suppose he does). 
Now, suppose Alice is moving north on El Camino Real in Palo Alto and is 
using Bob's HA (ha1.bobsmova.com). She's got an HoA in the subnet routed by 
ha1.bobsmova.com, which just so happens to cover that part of El Camino Real 
between San Antonio and the intersection of Charleston and Arastadero. 
Suppose Alice is paranoid about people tracking her movements so she never 
does route optimization so people never see her care of address, but she 
does put her HoA into the DNS so that people can SIP call her, at 
alice.bobsmova.com (Bob also acts as her MSA). Since ha1.bobsmova.com is 
local to Palo Alto, Alice has obtained a local HA and HoA.

Now, let's suppose Alice goes to Tucson in order to attend a conference. 
Alice is driving north on Speedway. She uses Bob's Mobile IP service there 
too, and she's got a HoA in Bob's network. Maybe the HA is even 
ha1.bobsmova.com. She puts that HoA into Bob's DNS at alice.bobsmova.com, 
and she never uses route optimization.

How can anybody deduce any geographical information about Alice? If Alice 
never exposes her care of address and always uses her home address, how can 
they tell if she's between San Antonio and the Charleston/Arastadero 
intersection in Palo Alto (covered by the subnet that her home address is 
in), or if she's between the Page Mill Road/Oregon Expressway intersection 
and the Charleston/Arastadero intersection in Palo Alto (which is in Bob's 
network but is not covered by the subnet that Alice 's home address is in), 
or, for that matter, whether she is in Palto Alto at all and not in Tucson 
(which is not covered by Bob's access network)?

            jakb

----- Original Message ----- 
From: "Vijay Devarapallli" <dvijay@gmail.com>
To: "James Kempf" <Kempf@docomolabs-usa.com>
Cc: "Gerardo Giaretta" <Gerardo.Giaretta@tilab.com>; "Vijay Devarapalli" 
<vijayd@iprg.nokia.com>; "Kilian Weniger" <Kilian.Weniger@eu.panasonic.com>; 
<mip6@ietf.org>
Sent: Friday, September 30, 2005 4:58 PM
Subject: Re: [Mip6] review of draft-ietf-mip6-bootstrapping-split-00.txt


there is some confusion.

Jim, Kilian's main concern is when the MN configures a HA
from the visited link (using location specific HA FQDN).
the issue is if the MN configures a HA and HoA from the
visited link and then has its DNS entry updated, then the
CN knows where the MN is currently located. the MN can
continue doing DNS updates for home address configured from
the home link. causes no harm. but when it does a DNS update
for the home address configured from a HA on a visited link,
it immediately reveals its location to the CN. maybe we
could add the following to the security considerations section

  A mobile node could hide its location from its correspondent
  node by reverse tunneling all traffic through the home agent.
  The same mobile node could roam and configure a home agent
  and home address from a visited link. If the home agent
  updates the DNS entry of the mobile node with its new home
  address, then this may reveal the current location of the
  mobile node to the correspondent node. In such a if the mobile
  node does not want the correspondent node to know its current
  location, then it should not request the home agent to update
  the DNS entry.

comments?

Vijay

On 9/30/05, James Kempf <Kempf@docomolabs-usa.com> wrote:
> Comments.
>
> "Note that local HA assignment combined with DNS updates may violate the
> location privacy of MN. A known solution to location privacy is to hide
> the CoA from CN by using reverse tunneling to the HA
> [draft-koodli-mip6-location-privacy-solutions-00.txt]. However, reverse
> tunneling may significantly decrease routing efficiency, depending on
> how far the HA is off the direct path between MN and CN.The
> bootstrapping solution supports local HA assignment to improve routing
> efficiency, but since the HoA obtained from a local HA assignment
> topologically belongs to the visited network, it contains location
> information. Consequently, it must carefully be considered to whom this
> HoA is revealed and whether DNS updates are requested for this HoA. The
> latter can even enable others to track MN's movement, if the MN uses an
> eager strategy for local HA assignment. On the other hand, if the HoA is
> hidden from other nodes, they cannot reach the MN at this HoA and, thus,
> cannot benefit from the local HA assignment in terms of routing
> efficiency. "
>
>  jak>> I have a couple problems with this:
>
> 1)  Reverse tunneling is the default in IPv6, that is to say, if an HA is
> used, reverse tunneling must be used, unless the traffic is route 
> optimized.
> So it is more accurate to say that in order to protect privacy, the MN 
> must
> not route optimize traffic.
>
> 2) The solution in draft-ietf-mip6-bootstrapping-split does not specify
> anything for local home agent assignment. There is nothing in the protocol
> to actually move the HA from the MSP's network to the serving network. The
> MN gets to choose an HA from whatever HAs the MSP's DNS SRV RR advertises.
> If that happens to be in the serving network, then correspondents will be
> able to obtain some information about where the MN is, but it could 
> equally
> well be on the other side of the globe.
>
> Note that the integrated scenerio (which the DT is currently working on)
> will have a mechanism whereby a local home agent can be assigned, since 
> the
> MN gets the HA address from the local DHCP server.
>
> 3) Since the HoA doesn't change once the MN has established it, I fail to
> see how an attacker can track the MN's location. Once the MN has 
> established
> the HoA, it will appear to be at a fixed topological location in the MSP's
> network regardless of where the care of address is, if route optimization 
> is
> not used.
>
> So I think the risk is considerably less that is portrayed by the above
> text. I think the following text would be more accurate:
>
>     Updating the mobile node's FQDN in the DNS
>     with the mobile node's home address has the
>     potential to expose some information about
>     the mobile node's location to correspondents
>     if the home agent selected by the mobile
>     node is in the serving network access provider's
>     network (that is, the serving network access
>     provider is also acting as the mobility service
>     provider). The risk here is not as deep as
>     with route optimization, since the mobile node
>     will effectively appear to be at a fixed topological
>     location in the mobility service provider's network
>     regardless of where the care of address is. To
>     mitigate the risk, the mobile node should
>     either not request DNS update or be careful
>     to select a home agent that is not within the
>     serving network access provider's network.
>
>
>             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 Sun Oct 02 09:57:51 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EM4Lf-0006zo-7K; Sun, 02 Oct 2005 09:57:51 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EM4Lc-0006zb-TX
	for mip6@megatron.ietf.org; Sun, 02 Oct 2005 09:57:48 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA16128
	for <mip6@ietf.org>; Sun, 2 Oct 2005 09:57:47 -0400 (EDT)
Received: from av9-1-sn2.hy.skanova.net ([81.228.8.179])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EM4Tt-0001Z9-W4
	for mip6@ietf.org; Sun, 02 Oct 2005 10:06:22 -0400
Received: by av9-1-sn2.hy.skanova.net (Postfix, from userid 502)
	id 5B8F637E8F; Sun,  2 Oct 2005 15:57:28 +0200 (CEST)
Received: from smtp4-2-sn2.hy.skanova.net (smtp4-2-sn2.hy.skanova.net
	[81.228.8.93])
	by av9-1-sn2.hy.skanova.net (Postfix) with ESMTP id 4898737E88
	for <mip6@ietf.org>; Sun,  2 Oct 2005 15:57:28 +0200 (CEST)
Received: from shiraz.levkowetz.com (81-224-201-50-no45.tbcn.telia.com
	[81.224.201.50])
	by smtp4-2-sn2.hy.skanova.net (Postfix) with ESMTP id 3963E37E44
	for <mip6@ietf.org>; Sun,  2 Oct 2005 15:57:28 +0200 (CEST)
Received: from shiraz.local.levkowetz.com ([192.168.3.14]
	helo=81-224-201-50-no45.tbcn.telia.com)
	by shiraz.levkowetz.com with esmtp (Exim 4.52) id 1EM4LC-00037u-A0
	for mip6@ietf.org; Sun, 02 Oct 2005 15:57:27 +0200
Content-Type: text/plain; charset=utf-8
To: mip6@ietf.org
From: Hannes Tschofenig <tracker-mip6@mip4.org>
Date: Sun, 02 Oct 2005 13:57:18 +0000
MIME-Version: 1.0
Message-Id: <1128261438.05.0.797992579998.issue43@mip4.org>
X-Roundup-Name: Mip6 issue tracker
X-Roundup-Loop: hello
Content-Transfer-Encoding: quoted-printable
X-Helo-Check-Failed: Verification failed for HELO
	81-224-201-50-no45.tbcn.telia.com
X-SA-Exim-Connect-IP: 192.168.3.14
X-SA-Exim-Mail-From: roundup-admin@mip4.org
X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on 
	shiraz.levkowetz.com
X-Spam-Status: No, score=-103.8 required=2.5 tests=ALL_TRUSTED,AWL,BAYES_00,
	USER_IN_WHITELIST,X_HELO_CHECK_FAILED autolearn=ham version=3.0.4
X-SA-Exim-Version: 4.2 (built Thu, 03 Mar 2005 10:44:12 +0100)
X-SA-Exim-Scanned: Yes (on shiraz.levkowetz.com)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Content-Transfer-Encoding: quoted-printable
Subject: [Mip6] [issue43] Review by Steve Bellovin: Dropping of ESP packets
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Mip6 issue tracker <tracker-mip6@mip4.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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org


New submission from Hannes Tschofenig <hannes.tschofenig@siemens.com>:

Steve: > >5.1:
> >	It's not so much that firewalls drop ESP by default, it's that
> >	they can't tell if inbound ESP packets are legitimate, since
> >	there's no useful state created by the outbound ESP packets.

this sentence sounds good to me. let me change the following paragraph from:

"
   Issue 1: When the MN A connects to the network, it should acquire a
      local IP address (CoA), and send a Binding Update to its Home
      Agent to update the HA with its current point of attachment.  The
      Binding Updates and Acknowledgements should be protected by IPsec
      ESP according to the MIPv6 specifications [1].  However, as a
      default rule, many firewalls drop ESP packets.  This may cause the
      Binding Updates and Acknowledgements between the Mobile Nodes and
      their Home Agent to be dropped.
"

to=20

"
   Issue 1: When the MN A connects to the network, it should acquire a
      local IP address (CoA), and send a Binding Update to its Home
      Agent to update the HA with its current point of attachment.  The
      Binding Updates and Acknowledgements should be protected by IPsec
      ESP according to the MIPv6 specifications [1].  However, as a
      default rule, many firewalls drop IPsec ESP packets because they cann=
ot=20
determine whether inbound ESP packets are legitimate, since it is difficult=
 or=20
impossible to create useful state by observing the outbound ESP packets. Th=
is=20
may cause the
      Binding Updates and Acknowledgements between the Mobile Nodes and
      their Home Agent to be dropped.=20
"

----------
category: Editorial
draft: draft-ietf-mip6-firewalls
messages: 162
nosy: bpatil, franckle, hannes, mip6, sfaccin
priority: Should fix
status: Text proposed
title: Review by Steve Bellovin: Dropping of ESP packets

_________________________________________________
Mip6 issue tracker <tracker-mip6@mip4.org>
<http://www.mip4.org/issues/tracker/mip6/issue43>
_________________________________________________

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



From mip6-bounces@ietf.org Sun Oct 02 09:57:51 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EM4Lf-00070D-OT; Sun, 02 Oct 2005 09:57:51 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EM4Lc-0006zc-TV
	for mip6@megatron.ietf.org; Sun, 02 Oct 2005 09:57:49 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA16129
	for <mip6@ietf.org>; Sun, 2 Oct 2005 09:57:47 -0400 (EDT)
Received: from av9-1-sn3.vrr.skanova.net ([81.228.9.185])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EM4Tt-0001ZA-W8
	for mip6@ietf.org; Sun, 02 Oct 2005 10:06:22 -0400
Received: by av9-1-sn3.vrr.skanova.net (Postfix, from userid 502)
	id 56D6A37EB6; Sun,  2 Oct 2005 15:57:29 +0200 (CEST)
Received: from smtp3-2-sn3.vrr.skanova.net (smtp3-2-sn3.vrr.skanova.net
	[81.228.9.102]) by av9-1-sn3.vrr.skanova.net (Postfix) with ESMTP
	id 3FFFF37EB3; Sun,  2 Oct 2005 15:57:29 +0200 (CEST)
Received: from shiraz.levkowetz.com (81-224-201-50-no45.tbcn.telia.com
	[81.224.201.50])
	by smtp3-2-sn3.vrr.skanova.net (Postfix) with ESMTP id D4C3737E43;
	Sun,  2 Oct 2005 15:57:28 +0200 (CEST)
Received: from shiraz.local.levkowetz.com ([192.168.3.14]
	helo=81-224-201-50-no45.tbcn.telia.com)
	by shiraz.levkowetz.com with esmtp (Exim 4.52)
	id 1EM4LH-000384-2M; Sun, 02 Oct 2005 15:57:27 +0200
Content-Type: text/plain; charset=utf-8
To: basavaraj.patil@nokia.com, franckl@andrew.cmu.edu, mip6@ietf.org,
	stefano.faccin@nokia.com
From: Hannes Tschofenig <tracker-mip6@mip4.org>
Date: Sun, 02 Oct 2005 13:57:27 +0000
MIME-Version: 1.0
Message-Id: <1128261438.05.0.797992579998.issue43@mip4.org>
X-Roundup-Name: Mip6 issue tracker
X-Roundup-Loop: hello
Content-Transfer-Encoding: quoted-printable
X-Helo-Check-Failed: Verification failed for HELO
	81-224-201-50-no45.tbcn.telia.com
X-SA-Exim-Connect-IP: 192.168.3.14
X-SA-Exim-Mail-From: roundup-admin@mip4.org
X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on 
	shiraz.levkowetz.com
X-Spam-Status: No, score=-103.8 required=2.5 tests=ALL_TRUSTED,AWL,BAYES_00,
	USER_IN_WHITELIST,X_HELO_CHECK_FAILED autolearn=ham version=3.0.4
X-SA-Exim-Version: 4.2 (built Thu, 03 Mar 2005 10:44:12 +0100)
X-SA-Exim-Scanned: Yes (on shiraz.levkowetz.com)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Content-Transfer-Encoding: quoted-printable
Cc: 
Subject: [Mip6] [issue43] Review by Steve Bellovin: Dropping of ESP packets
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Mip6 issue tracker <tracker-mip6@mip4.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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org


New submission from Hannes Tschofenig <hannes.tschofenig@siemens.com>:

Steve: > >5.1:
> >	It's not so much that firewalls drop ESP by default, it's that
> >	they can't tell if inbound ESP packets are legitimate, since
> >	there's no useful state created by the outbound ESP packets.

this sentence sounds good to me. let me change the following paragraph from:

"
   Issue 1: When the MN A connects to the network, it should acquire a
      local IP address (CoA), and send a Binding Update to its Home
      Agent to update the HA with its current point of attachment.  The
      Binding Updates and Acknowledgements should be protected by IPsec
      ESP according to the MIPv6 specifications [1].  However, as a
      default rule, many firewalls drop ESP packets.  This may cause the
      Binding Updates and Acknowledgements between the Mobile Nodes and
      their Home Agent to be dropped.
"

to=20

"
   Issue 1: When the MN A connects to the network, it should acquire a
      local IP address (CoA), and send a Binding Update to its Home
      Agent to update the HA with its current point of attachment.  The
      Binding Updates and Acknowledgements should be protected by IPsec
      ESP according to the MIPv6 specifications [1].  However, as a
      default rule, many firewalls drop IPsec ESP packets because they cann=
ot=20
determine whether inbound ESP packets are legitimate, since it is difficult=
 or=20
impossible to create useful state by observing the outbound ESP packets. Th=
is=20
may cause the
      Binding Updates and Acknowledgements between the Mobile Nodes and
      their Home Agent to be dropped.=20
"

----------
category: Editorial
draft: draft-ietf-mip6-firewalls
messages: 162
nosy: bpatil, franckle, hannes, mip6, sfaccin
priority: Should fix
status: Text proposed
title: Review by Steve Bellovin: Dropping of ESP packets

_________________________________________________
Mip6 issue tracker <tracker-mip6@mip4.org>
<http://www.mip4.org/issues/tracker/mip6/issue43>
_________________________________________________

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



From mip6-bounces@ietf.org Sun Oct 02 10:06:50 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EM4UM-0002iR-3c; Sun, 02 Oct 2005 10:06:50 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EM4UK-0002iM-1f
	for mip6@megatron.ietf.org; Sun, 02 Oct 2005 10:06:48 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16670
	for <mip6@ietf.org>; Sun, 2 Oct 2005 10:06:46 -0400 (EDT)
Received: from av6-1-sn3.vrr.skanova.net ([81.228.9.179])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EM4ca-0001lU-E9
	for mip6@ietf.org; Sun, 02 Oct 2005 10:15:22 -0400
Received: by av6-1-sn3.vrr.skanova.net (Postfix, from userid 502)
	id 10CA037E8F; Sun,  2 Oct 2005 16:06:37 +0200 (CEST)
Received: from smtp3-1-sn3.vrr.skanova.net (smtp3-1-sn3.vrr.skanova.net
	[81.228.9.101]) by av6-1-sn3.vrr.skanova.net (Postfix) with ESMTP
	id EE35937E8A; Sun,  2 Oct 2005 16:06:36 +0200 (CEST)
Received: from shiraz.levkowetz.com (81-224-201-50-no45.tbcn.telia.com
	[81.224.201.50])
	by smtp3-1-sn3.vrr.skanova.net (Postfix) with ESMTP id DEB5E37E42;
	Sun,  2 Oct 2005 16:06:36 +0200 (CEST)
Received: from shiraz.local.levkowetz.com ([192.168.3.14]
	helo=81-224-201-50-no45.tbcn.telia.com)
	by shiraz.levkowetz.com with esmtp (Exim 4.52)
	id 1EM4U7-0003L1-Jk; Sun, 02 Oct 2005 16:06:36 +0200
Content-Type: text/plain; charset=utf-8
To: basavaraj.patil@nokia.com, franckl@andrew.cmu.edu, mip6@ietf.org,
	stefano.faccin@nokia.com
From: Hannes Tschofenig <tracker-mip6@mip4.org>
Date: Sun, 02 Oct 2005 14:06:35 +0000
MIME-Version: 1.0
Message-Id: <1128261995.57.0.849791705466.issue43@mip4.org>
X-Roundup-Name: Mip6 issue tracker
X-Roundup-Loop: hello
Content-Transfer-Encoding: quoted-printable
X-Helo-Check-Failed: Verification failed for HELO
	81-224-201-50-no45.tbcn.telia.com
X-SA-Exim-Connect-IP: 192.168.3.14
X-SA-Exim-Mail-From: roundup-admin@mip4.org
X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on 
	shiraz.levkowetz.com
X-Spam-Status: No, score=-103.8 required=2.5 tests=ALL_TRUSTED,AWL,BAYES_00,
	MIME_QP_LONG_LINE, USER_IN_WHITELIST, X_HELO_CHECK_FAILED autolearn=ham 
	version=3.0.4
X-SA-Exim-Version: 4.2 (built Thu, 03 Mar 2005 10:44:12 +0100)
X-SA-Exim-Scanned: Yes (on shiraz.levkowetz.com)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Content-Transfer-Encoding: quoted-printable
Cc: 
Subject: [Mip6] [issue43] Review by Steve Bellovin: Dropping of ESP packets
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Mip6 issue tracker <tracker-mip6@mip4.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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org


Hannes Tschofenig <hannes.tschofenig@siemens.com> added the comment:

Steve writes:=20
> >	A more general analysis of the issues presented by 5.1 is that
> >	firewalls are topological elements, not logical ones.  Thus, an
> >	MN behind a firewall is protected by it/subject to its rules,
> >	because it's part of the protected topology.  The particular
> >	issues discussed here are just special cases of that situation.

would it be useful to add the following sentence at the beginning of sectio=
n=20
5=2E1?=20

this would change the text from:=20

"
   Let's consider a MN A, in a network protected by firewall(s).
"

to:

"
   Let us consider a MN A in a network protected by a firewall (or even=20
multiple firewalls).=20
   Since the firewall is a topological element the protection it offers is=20
based on its packet filter rules because it is part of the protected topolo=
gy.
"

_________________________________________________
Mip6 issue tracker <tracker-mip6@mip4.org>
<http://www.mip4.org/issues/tracker/mip6/issue43>
_________________________________________________

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



From mip6-bounces@ietf.org Sun Oct 02 15:43:41 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EM9kL-0008LA-BF; Sun, 02 Oct 2005 15:43:41 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EM9kJ-0008L1-7s
	for mip6@megatron.ietf.org; Sun, 02 Oct 2005 15:43:39 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00305
	for <mip6@ietf.org>; Sun, 2 Oct 2005 15:43:35 -0400 (EDT)
Received: from av12-2-sn2.hy.skanova.net ([81.228.8.186])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EM9sb-0000vv-IB
	for mip6@ietf.org; Sun, 02 Oct 2005 15:52:14 -0400
Received: by av12-2-sn2.hy.skanova.net (Postfix, from userid 502)
	id 7567C37ECA; Sun,  2 Oct 2005 21:43:27 +0200 (CEST)
Received: from smtp4-1-sn2.hy.skanova.net (smtp4-1-sn2.hy.skanova.net
	[81.228.8.92]) by av12-2-sn2.hy.skanova.net (Postfix) with ESMTP
	id 5221F37EC8; Sun,  2 Oct 2005 21:43:27 +0200 (CEST)
Received: from shiraz.levkowetz.com (81-224-201-50-no45.tbcn.telia.com
	[81.224.201.50])
	by smtp4-1-sn2.hy.skanova.net (Postfix) with ESMTP id 09A2937E42;
	Sun,  2 Oct 2005 21:43:26 +0200 (CEST)
Received: from shiraz.local.levkowetz.com ([192.168.3.14]
	helo=81-224-201-50-no45.tbcn.telia.com)
	by shiraz.levkowetz.com with esmtp (Exim 4.52)
	id 1EM9k5-0003lo-S1; Sun, 02 Oct 2005 21:43:26 +0200
Content-Type: text/plain; charset=utf-8
To: basavaraj.patil@nokia.com, franckl@andrew.cmu.edu, mip6@ietf.org,
	stefano.faccin@nokia.com
From: Hannes Tschofenig <tracker-mip6@mip4.org>
Date: Sun, 02 Oct 2005 19:43:25 +0000
MIME-Version: 1.0
Message-Id: <1128282204.56.0.802247410218.issue44@mip4.org>
X-Roundup-Name: Mip6 issue tracker
X-Roundup-Loop: hello
Content-Transfer-Encoding: quoted-printable
X-Helo-Check-Failed: Verification failed for HELO
	81-224-201-50-no45.tbcn.telia.com
X-SA-Exim-Connect-IP: 192.168.3.14
X-SA-Exim-Mail-From: roundup-admin@mip4.org
X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on 
	shiraz.levkowetz.com
X-Spam-Status: No, score=-103.8 required=2.5 tests=ALL_TRUSTED,AWL,BAYES_00,
	MIME_QP_LONG_LINE, USER_IN_WHITELIST, X_HELO_CHECK_FAILED autolearn=ham 
	version=3.0.4
X-SA-Exim-Version: 4.2 (built Thu, 03 Mar 2005 10:44:12 +0100)
X-SA-Exim-Scanned: Yes (on shiraz.levkowetz.com)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86
Content-Transfer-Encoding: quoted-printable
Cc: 
Subject: [Mip6] [issue44] Review by Steve Bellovin: Section 5.3
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Mip6 issue tracker <tracker-mip6@mip4.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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org


New submission from Hannes Tschofenig <hannes.tschofenig@siemens.com>:

Steve wrote:=20
> >
> >5.3:
> >	It's generally safe to permit ESP traffic to a known-locked down
> >	host.  If there's a generic HA, it can be a valid recipient of
> >	IPsec without compromising network security.  The same applies
> >	to Issue 2.  Issue 3 is the same situation described earlier.

Hannes:=20

i agree that some network administrators might allow IPsec protected data=20
traffic to known hosts inside their network to bypass. they, however, need =
to=20
be told that this is an issue with mobile ip.=20

to reflect your comment let me make a proposal to change section 5.3 from:=20

"
5=2E3  Scenario where the HA is in a network protected by firewall(s)

   Let's consider a MN moving into a network protected by firewall(s).
   The following issues may exist:


   Issue 1: If the firewall(s) block ESP traffic, many of the MIPv6
      signaling (e.g.  Binding Update, HoT) may be dropped at the
      firewall(s) preventing MN(s) from updating their binding cache and
      performing Route Optimization, since Binding Update, HoT and other
      MIPv6 signaling must be protected by IPsec ESP.
    =20

   Issue 2: If the firewall(s) protecting the Home Agent block
      unsolicited incoming traffic (e.g. as stateful inspection packet
      filters do), the firewall(s) may drop connection set up requests
      from CN, and packets from MN.

   Issue 3: If the Home Agent is in a network protected by several
      firewalls, a MN/CN's change of IP address may result in the
      traffic to and from the Home Agent passing through a different
      firewall that may not have the states corresponding to the flows.
      As a consequence, packets may be dropped at the firewall.
"

to:

"
5=2E3  Scenario where the HA is in a network protected by firewall(s)

   Let's consider a MN moving into a network protected by firewall(s).
   The following issues may exist:


   Issue 1: If the firewall(s) block ESP traffic, many of the MIPv6
      signaling (e.g.  Binding Update, HoT) may be dropped at the
      firewall(s) preventing MN(s) from updating their binding cache and
      performing Route Optimization, since Binding Update, HoT and other
      MIPv6 signaling must be protected by IPsec ESP.

      Network administrators may allow to bypass IPsec ESP protected traffi=
c to=20
a predefined host within their network.=20
    =20

   Issue 2: If the firewall(s) protecting the Home Agent block
      unsolicited incoming traffic (e.g. as stateful inspection packet
      filters do), the firewall(s) may drop connection set up requests
      from CN, and packets from MN.


      Network administrators may allow to bypass Mobile IP signaling messag=
es=20
to a predefined host within their network.

   Issue 3: If the Home Agent is in a network protected by several
      firewalls, a MN/CN's change of IP address may result in the
      traffic to and from the Home Agent passing through a different
      firewall that may not have the states corresponding to the flows.
      As a consequence, packets may be dropped at the firewall.

      Network administrators may deploy state synchronization mechanisms=20
between firewalls to deal with this problem prior to the introduction of=20
mobility protocols.=20
"

----------
category: Technical
draft: draft-ietf-mip6-firewalls
messages: 164
nosy: bpatil, franckle, hannes, mip6, sfaccin
priority: Should fix
status: Pending
title: Review by Steve Bellovin: Section 5.3

_________________________________________________
Mip6 issue tracker <tracker-mip6@mip4.org>
<http://www.mip4.org/issues/tracker/mip6/issue44>
_________________________________________________

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



From mip6-bounces@ietf.org Sun Oct 02 15:43:41 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EM9kL-0008LZ-TR; Sun, 02 Oct 2005 15:43:41 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EM9kJ-0008L0-7q
	for mip6@megatron.ietf.org; Sun, 02 Oct 2005 15:43:39 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00302
	for <mip6@ietf.org>; Sun, 2 Oct 2005 15:43:35 -0400 (EDT)
Received: from av11-1-sn2.hy.skanova.net ([81.228.8.183])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EM9sb-0000vu-9h
	for mip6@ietf.org; Sun, 02 Oct 2005 15:52:13 -0400
Received: by av11-1-sn2.hy.skanova.net (Postfix, from userid 502)
	id 91CFB37F02; Sun,  2 Oct 2005 21:43:26 +0200 (CEST)
Received: from smtp4-1-sn2.hy.skanova.net (smtp4-1-sn2.hy.skanova.net
	[81.228.8.92])
	by av11-1-sn2.hy.skanova.net (Postfix) with ESMTP id 8248737EFF
	for <mip6@ietf.org>; Sun,  2 Oct 2005 21:43:26 +0200 (CEST)
Received: from shiraz.levkowetz.com (81-224-201-50-no45.tbcn.telia.com
	[81.224.201.50])
	by smtp4-1-sn2.hy.skanova.net (Postfix) with ESMTP id 6E6C537E42
	for <mip6@ietf.org>; Sun,  2 Oct 2005 21:43:26 +0200 (CEST)
Received: from shiraz.local.levkowetz.com ([192.168.3.14]
	helo=81-224-201-50-no45.tbcn.telia.com)
	by shiraz.levkowetz.com with esmtp (Exim 4.52) id 1EM9k4-0003le-Tw
	for mip6@ietf.org; Sun, 02 Oct 2005 21:43:25 +0200
Content-Type: text/plain; charset=utf-8
To: mip6@ietf.org
From: Hannes Tschofenig <tracker-mip6@mip4.org>
Date: Sun, 02 Oct 2005 19:43:24 +0000
MIME-Version: 1.0
Message-Id: <1128282204.56.0.802247410218.issue44@mip4.org>
X-Roundup-Name: Mip6 issue tracker
X-Roundup-Loop: hello
Content-Transfer-Encoding: quoted-printable
X-Helo-Check-Failed: Verification failed for HELO
	81-224-201-50-no45.tbcn.telia.com
X-SA-Exim-Connect-IP: 192.168.3.14
X-SA-Exim-Mail-From: roundup-admin@mip4.org
X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on 
	shiraz.levkowetz.com
X-Spam-Status: No, score=-103.8 required=2.5 tests=ALL_TRUSTED,AWL,BAYES_00,
	MIME_QP_LONG_LINE, USER_IN_WHITELIST, X_HELO_CHECK_FAILED autolearn=ham 
	version=3.0.4
X-SA-Exim-Version: 4.2 (built Thu, 03 Mar 2005 10:44:12 +0100)
X-SA-Exim-Scanned: Yes (on shiraz.levkowetz.com)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86
Content-Transfer-Encoding: quoted-printable
Subject: [Mip6] [issue44] Review by Steve Bellovin: Section 5.3
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Mip6 issue tracker <tracker-mip6@mip4.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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org


New submission from Hannes Tschofenig <hannes.tschofenig@siemens.com>:

Steve wrote:=20
> >
> >5.3:
> >	It's generally safe to permit ESP traffic to a known-locked down
> >	host.  If there's a generic HA, it can be a valid recipient of
> >	IPsec without compromising network security.  The same applies
> >	to Issue 2.  Issue 3 is the same situation described earlier.

Hannes:=20

i agree that some network administrators might allow IPsec protected data=20
traffic to known hosts inside their network to bypass. they, however, need =
to=20
be told that this is an issue with mobile ip.=20

to reflect your comment let me make a proposal to change section 5.3 from:=20

"
5=2E3  Scenario where the HA is in a network protected by firewall(s)

   Let's consider a MN moving into a network protected by firewall(s).
   The following issues may exist:


   Issue 1: If the firewall(s) block ESP traffic, many of the MIPv6
      signaling (e.g.  Binding Update, HoT) may be dropped at the
      firewall(s) preventing MN(s) from updating their binding cache and
      performing Route Optimization, since Binding Update, HoT and other
      MIPv6 signaling must be protected by IPsec ESP.
    =20

   Issue 2: If the firewall(s) protecting the Home Agent block
      unsolicited incoming traffic (e.g. as stateful inspection packet
      filters do), the firewall(s) may drop connection set up requests
      from CN, and packets from MN.

   Issue 3: If the Home Agent is in a network protected by several
      firewalls, a MN/CN's change of IP address may result in the
      traffic to and from the Home Agent passing through a different
      firewall that may not have the states corresponding to the flows.
      As a consequence, packets may be dropped at the firewall.
"

to:

"
5=2E3  Scenario where the HA is in a network protected by firewall(s)

   Let's consider a MN moving into a network protected by firewall(s).
   The following issues may exist:


   Issue 1: If the firewall(s) block ESP traffic, many of the MIPv6
      signaling (e.g.  Binding Update, HoT) may be dropped at the
      firewall(s) preventing MN(s) from updating their binding cache and
      performing Route Optimization, since Binding Update, HoT and other
      MIPv6 signaling must be protected by IPsec ESP.

      Network administrators may allow to bypass IPsec ESP protected traffi=
c to=20
a predefined host within their network.=20
    =20

   Issue 2: If the firewall(s) protecting the Home Agent block
      unsolicited incoming traffic (e.g. as stateful inspection packet
      filters do), the firewall(s) may drop connection set up requests
      from CN, and packets from MN.


      Network administrators may allow to bypass Mobile IP signaling messag=
es=20
to a predefined host within their network.

   Issue 3: If the Home Agent is in a network protected by several
      firewalls, a MN/CN's change of IP address may result in the
      traffic to and from the Home Agent passing through a different
      firewall that may not have the states corresponding to the flows.
      As a consequence, packets may be dropped at the firewall.

      Network administrators may deploy state synchronization mechanisms=20
between firewalls to deal with this problem prior to the introduction of=20
mobility protocols.=20
"

----------
category: Technical
draft: draft-ietf-mip6-firewalls
messages: 164
nosy: bpatil, franckle, hannes, mip6, sfaccin
priority: Should fix
status: Pending
title: Review by Steve Bellovin: Section 5.3

_________________________________________________
Mip6 issue tracker <tracker-mip6@mip4.org>
<http://www.mip4.org/issues/tracker/mip6/issue44>
_________________________________________________

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



From mip6-bounces@ietf.org Sun Oct 02 16:08:11 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EMA83-0001yv-32; Sun, 02 Oct 2005 16:08:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EMA81-0001yh-AE
	for mip6@megatron.ietf.org; Sun, 02 Oct 2005 16:08:09 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01055
	for <mip6@ietf.org>; Sun, 2 Oct 2005 16:08:07 -0400 (EDT)
Received: from av6-1-sn3.vrr.skanova.net ([81.228.9.179])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EMAGL-0001Ye-8A
	for mip6@ietf.org; Sun, 02 Oct 2005 16:16:46 -0400
Received: by av6-1-sn3.vrr.skanova.net (Postfix, from userid 502)
	id D8EC137ED3; Sun,  2 Oct 2005 22:07:58 +0200 (CEST)
Received: from smtp3-1-sn3.vrr.skanova.net (smtp3-1-sn3.vrr.skanova.net
	[81.228.9.101]) by av6-1-sn3.vrr.skanova.net (Postfix) with ESMTP
	id C18E337EA8; Sun,  2 Oct 2005 22:07:58 +0200 (CEST)
Received: from shiraz.levkowetz.com (81-224-201-50-no45.tbcn.telia.com
	[81.224.201.50])
	by smtp3-1-sn3.vrr.skanova.net (Postfix) with ESMTP id 75D9937E47;
	Sun,  2 Oct 2005 22:07:58 +0200 (CEST)
Received: from shiraz.local.levkowetz.com ([192.168.3.14]
	helo=81-224-201-50-no45.tbcn.telia.com)
	by shiraz.levkowetz.com with esmtp (Exim 4.52)
	id 1EMA7p-0004In-71; Sun, 02 Oct 2005 22:07:57 +0200
Content-Type: text/plain; charset=utf-8
To: basavaraj.patil@nokia.com, franckl@andrew.cmu.edu, mip6@ietf.org,
	stefano.faccin@nokia.com
From: Hannes Tschofenig <tracker-mip6@mip4.org>
Date: Sun, 02 Oct 2005 20:07:49 +0000
MIME-Version: 1.0
Message-Id: <1128283669.79.0.666025699096.issue44@mip4.org>
X-Roundup-Name: Mip6 issue tracker
X-Roundup-Loop: hello
Content-Transfer-Encoding: quoted-printable
X-Helo-Check-Failed: Verification failed for HELO
	81-224-201-50-no45.tbcn.telia.com
X-SA-Exim-Connect-IP: 192.168.3.14
X-SA-Exim-Mail-From: roundup-admin@mip4.org
X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on 
	shiraz.levkowetz.com
X-Spam-Status: No, score=-103.8 required=2.5 tests=ALL_TRUSTED,AWL,BAYES_00,
	MIME_QP_LONG_LINE, USER_IN_WHITELIST, X_HELO_CHECK_FAILED autolearn=ham 
	version=3.0.4
X-SA-Exim-Version: 4.2 (built Thu, 03 Mar 2005 10:44:12 +0100)
X-SA-Exim-Scanned: Yes (on shiraz.levkowetz.com)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Content-Transfer-Encoding: quoted-printable
Cc: 
Subject: [Mip6] [issue44] Review by Steve Bellovin: Section 5.3
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Mip6 issue tracker <tracker-mip6@mip4.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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org


Hannes Tschofenig <hannes.tschofenig@siemens.com> added the comment:

Henrik says:=20

> >     Issue 1: If the firewall(s) block ESP traffic, many of the MIPv6
> >        signaling (e.g.  Binding Update, HoT) may be dropped ...
> ...snip...
> >        performing Route Optimization, since Binding Update,=20
> HoT and other
> >        MIPv6 signaling must be protected by IPsec ESP.
>=20
> 	I don't see how this differs from Section 5.1, and don't see
>   	that it belongs here.

I added text to address the different style of the described issues in this=20
section.

_________________________________________________
Mip6 issue tracker <tracker-mip6@mip4.org>
<http://www.mip4.org/issues/tracker/mip6/issue44>
_________________________________________________

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



From mip6-bounces@ietf.org Sun Oct 02 17:05:52 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EMB1s-0008Sn-7j; Sun, 02 Oct 2005 17:05:52 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EMB1p-0008SV-56
	for mip6@megatron.ietf.org; Sun, 02 Oct 2005 17:05:50 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02807
	for <mip6@ietf.org>; Sun, 2 Oct 2005 17:05:46 -0400 (EDT)
Received: from lizzard.sbs.de ([194.138.37.39])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EMBA9-0002eG-OI
	for mip6@ietf.org; Sun, 02 Oct 2005 17:14:26 -0400
Received: from mail1.sbs.de (mail1.sbs.de [192.129.41.35])
	by lizzard.sbs.de (8.12.6/8.12.6) with ESMTP id j92L4Q0X026541;
	Sun, 2 Oct 2005 23:04:46 +0200
Received: from fthw9xpa.ww002.siemens.net (fthw9xpa.ww002.siemens.net
	[157.163.133.222])
	by mail1.sbs.de (8.12.6/8.12.6) with ESMTP id j92L0P2m016766;
	Sun, 2 Oct 2005 23:02:21 +0200
Received: from MCHP7IEA.ww002.siemens.net ([139.25.131.145]) by
	fthw9xpa.ww002.siemens.net with Microsoft SMTPSVC(6.0.3790.0); 
	Sun, 2 Oct 2005 23:02:12 +0200
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
Date: Sun, 2 Oct 2005 23:02:11 +0200
Message-ID: <ECDC9C7BC7809340842C0E7FCF48C39363D155@MCHP7IEA.ww002.siemens.net>
Thread-Topic: Re: draft-ietf-mip6-firewalls-02.txt
Thread-Index: AcW2z4yWOrJTSyfFS1CtFCKkZpQBvgQhk+Aw
From: "Tschofenig, Hannes" <hannes.tschofenig@siemens.com>
To: "Margaret Wasserman" <margaret@thingmagic.com>, <franck.le@nokia.com>,
	<stefano.faccin@nokia.com>, <basavaraj.patil@nokia.com>,
	<Hannes.Tschofenig@siemens.com>
X-OriginalArrivalTime: 02 Oct 2005 21:02:12.0097 (UTC)
	FILETIME=[8F2AEF10:01C5C794]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4ec3642ae9025e273a4a263d640f3300
Content-Transfer-Encoding: quoted-printable
Cc: gdommety@cisco.com, mip6@ietf.org, Henrik Levkowetz <henrik@levkowetz.com>,
	Steve Bellovin <smb@research.att.com>
Subject: [Mip6] AW: Re: draft-ietf-mip6-firewalls-02.txt
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

hi all,=20

i would like to respond to the review comments by steve. i have created =
the corresponding entities in the issue tracker. please find some =
further comments inline:

> -----Urspr=FCngliche Nachricht-----
> Von: Margaret Wasserman [mailto:margaret@thingmagic.com]=20
> Gesendet: Sonntag, 11. September 2005 14:52
> An: franck.le@nokia.com; stefano.faccin@nokia.com;=20
> basavaraj.patil@nokia.com; Tschofenig, Hannes
> Cc: gdommety@cisco.com; Henrik Levkowetz; Steve Bellovin;=20
> mip6@ietf.org
> Betreff: Fwd: Re: draft-ietf-mip6-firewalls-02.txt
>=20
>=20
>=20
> Hi Franck, Stefano, Raj and Hannes,
>=20
> As part of AD Review on draft-ietf-mip6-firewalls-02.txt, I solicited=20
> reviews from Henrik Levkowetz and Steve Bellovin.  I have attached=20
> both Steve's and Henrik's reviews below.  Spencer Dawkins also posted=20
> a gen-art review of this draft (also attached).
>=20
> As you can see, all three reviewers believe that this document is=20
> good work and is close to ready for publication, but they each made a=20
> few minor corrections or editorial suggestions.
>=20
> When a new version is available that addresses all of these comments,=20
> we should be ready to send this document to the IESG for=20
> review/approval.
>=20
> Thanks,
> Margaret
>=20
>=20
> Steve's Review:
>=20
> >It's a pretty good document; I'm glad to see it appearing at last.
> >I've noted a few clarifications that might help.
> >
> >What I'd really like to see in this document, if possible,=20
> is a set of
> >rules and algorithms, as suggestions for site administrators and
> >MIPv6-aware firewall vendors.  But maybe that should be published
> >separately.
> >
> >
> >
> >Section 4:
> >	Some firewalls check TCP sequence numbers as well.
> >
> >	Is UDP behavior significant here?  Application-level proxies for
> >	all sorts of protocols?

stateful packet filtering firewalls turn out to be a problem for mipv6.=20
the occurance of tcp and udp traffic allows the firewall to establish =
state. for tcp more information is available.=20
we mentioned the example with tcp only as an illustration how stateful =
packet filtering firewalls work and why this leads to a problem.=20


> >
> >5.1:
> >	It's not so much that firewalls drop ESP by default, it's that
> >	they can't tell if inbound ESP packets are legitimate, since
> >	there's no useful state created by the outbound ESP packets.

this sentence sounds good to me. let me change the following paragraph =
from:

"
   Issue 1: When the MN A connects to the network, it should acquire a
      local IP address (CoA), and send a Binding Update to its Home
      Agent to update the HA with its current point of attachment.  The
      Binding Updates and Acknowledgements should be protected by IPsec
      ESP according to the MIPv6 specifications [1].  However, as a
      default rule, many firewalls drop ESP packets.  This may cause the
      Binding Updates and Acknowledgements between the Mobile Nodes and
      their Home Agent to be dropped.
"

to=20

"
   Issue 1: When the MN A connects to the network, it should acquire a
      local IP address (CoA), and send a Binding Update to its Home
      Agent to update the HA with its current point of attachment.  The
      Binding Updates and Acknowledgements should be protected by IPsec
      ESP according to the MIPv6 specifications [1].  However, as a
      default rule, many firewalls drop IPsec ESP packets because they =
cannot determine whether inbound ESP packets are legitimate, since it is =
difficult or impossible to create useful state by observing the outbound =
ESP packets. This may cause the
      Binding Updates and Acknowledgements between the Mobile Nodes and
      their Home Agent to be dropped.=20
"

> >
> >	A more general analysis of the issues presented by 5.1 is that
> >	firewalls are topological elements, not logical ones.  Thus, an
> >	MN behind a firewall is protected by it/subject to its rules,
> >	because it's part of the protected topology.  The particular
> >	issues discussed here are just special cases of that situation.

would it be useful to add the following sentence at the beginning of =
section 5.1. this would change the text from:=20

"
   Let's consider a MN A, in a network protected by firewall(s).
"

to:

"
   Let us consider a MN A in a network protected by a firewall (or even =
multiple firewalls).=20
   Since the firewall is a topological element the protection it offers =
is based on its packet filter rules because it is part of the protected =
topology.
"

 =20

> >
> >5.2:
> >	In Figure 2, label CN as "A".

fixed.=20

> >
> >	Issue 3: In many environments with more than one firewall, they
> >	already share state.  This is a necessity because routing is
> >	generally asymmetric.  Consider this:
> >
> >
> >       +----------------+
> >       |                |
> >       |        A      FW1
> >       |                |
> >       |                |
> >       |                |
> >       |                |
> >       |                |
> >       |               FW2      B
> >       |                |
> >       +----------------+
> >
> >	A is closer to FW1, so its packets exit via FW1.  B is closer
> >	to FW2, and they advertise the same CIDR block, so the return
> >	packets will try to go that way.  That fails unless there's
> >	state-sharing, without any mobility.

we know that many firewalls use state sharing already today.=20
we agree that there might even be a problem in general. we thought that =
it might still be good to indicate this problem.=20

a side comment since you raised this issue: do you have some statistics =
that =20
a) show how frequent multi-homed networks are
b) tell us how frequently firewall synchronization is used (if there are =
multiple firewalls)

> >
> >5.3:
> >	It's generally safe to permit ESP traffic to a known-locked down
> >	host.  If there's a generic HA, it can be a valid recipient of
> >	IPsec without compromising network security.  The same applies
> >	to Issue 2.  Issue 3 is the same situation described earlier.

i agree that some network administrators might allow IPsec protected =
data traffic to known hosts inside their network to bypass. they, =
however, need to be told that this is an issue with mobile ip.=20

to reflect your comment let me make a proposal to change section 5.3 =
from:=20
"
5.3  Scenario where the HA is in a network protected by firewall(s)

   Let's consider a MN moving into a network protected by firewall(s).
   The following issues may exist:


   Issue 1: If the firewall(s) block ESP traffic, many of the MIPv6
      signaling (e.g.  Binding Update, HoT) may be dropped at the
      firewall(s) preventing MN(s) from updating their binding cache and
      performing Route Optimization, since Binding Update, HoT and other
      MIPv6 signaling must be protected by IPsec ESP.
    =20

   Issue 2: If the firewall(s) protecting the Home Agent block
      unsolicited incoming traffic (e.g. as stateful inspection packet
      filters do), the firewall(s) may drop connection set up requests
      from CN, and packets from MN.

   Issue 3: If the Home Agent is in a network protected by several
      firewalls, a MN/CN's change of IP address may result in the
      traffic to and from the Home Agent passing through a different
      firewall that may not have the states corresponding to the flows.
      As a consequence, packets may be dropped at the firewall.
"

to:

"
5.3  Scenario where the HA is in a network protected by firewall(s)

   Let's consider a MN moving into a network protected by firewall(s).
   The following issues may exist:


   Issue 1: If the firewall(s) block ESP traffic, many of the MIPv6
      signaling (e.g.  Binding Update, HoT) may be dropped at the
      firewall(s) preventing MN(s) from updating their binding cache and
      performing Route Optimization, since Binding Update, HoT and other
      MIPv6 signaling must be protected by IPsec ESP.

      Network administrators may allow to bypass IPsec ESP protected =
traffic to a predefined host within their network.=20
    =20

   Issue 2: If the firewall(s) protecting the Home Agent block
      unsolicited incoming traffic (e.g. as stateful inspection packet
      filters do), the firewall(s) may drop connection set up requests
      from CN, and packets from MN.


      Network administrators may allow to bypass Mobile IP signaling =
messages to a predefined host within their network.

   Issue 3: If the Home Agent is in a network protected by several
      firewalls, a MN/CN's change of IP address may result in the
      traffic to and from the Home Agent passing through a different
      firewall that may not have the states corresponding to the flows.
      As a consequence, packets may be dropped at the firewall.

      Network administrators may deploy state synchronization mechanisms =
between firewalls=20
      to deal with this problem prior to the introduction of mobility =
protocols.=20
"
> >
> >
> >
> >		--Steven M. Bellovin, http://www.cs.columbia.edu/~smb
> >
>=20
> Henrik's Review:
>=20
>      The document points out real problems, and is reasonably well
> written and formulated.
>=20
>=20
> In summary, I think that
>=20
>    * These are valid problems
>=20
>    * While the problems described in 5.1, 5.2 and 5.4 may require
>      product and protocol modifications, the problems in 5.3 have
>      more a character of installation and configuration mistakes,
>      and should maybe be labelled as such.

i have added a few lines based on the last comment by steve, which goes =
into the same direction.=20
>=20
>    * MIPv6 permits the use of AH as an alternative to ESP in some
>      cases - I wonder if this document should cover this case, as
>      well.  I believe that AH may have less problems than ESP, but
>      it also gives less protection.  ESP is in particular recommended
>      for the HoT and HoTI messages between HA and MN.

the current document covers the 'worst' case. in certain deployment =
cases things might be simpler if you, for example, use ah instead of esp =
or if you use the mipv6-auth protocol instead of ikev1/ikev2.=20

>=20
> (Going into solution space, which doesn't belong in this document,
>   I observe that several of the problems associated with route-
>   optimised traffic might be solved with an approach similar to that
>   used by Teredo.)
>=20
> Minor comments:
>=20
> Section 4:
>=20
>          This section lacks an expansion of HoT. However, if each
> 	abbreviation is expanded on the first of the first few
> 	instances of use, I'd probably be just as happy without
> 	this section.
>=20
>=20
> Section 5.1:
>=20
> >  5.1  Scenario where the Mobile Node is in a network protected by
> >       firewall(s)
>=20
> 	It's in Section 5.4, actually.

section 5.1 deals with a mobile node behind a firewall. section 5.4 =
deals with the mobile node and the home agend being behind a firewall. =
maybe the headline of section 5.4 could be improved.=20


>=20
>=20
> Section 5.2:
>=20
> 	I'd be happier if you did not use the designation 'A' for the
>   	CN here, after having used 'A' for the MN in Section 5.1.
>   	Maybe call the nodes 'C' and 'D' here instead?


that's a good idea.=20
fixed.=20

>=20
>=20
> Section 5.2, para. 22:
>=20
> >        The HoTI is a Mobility Header packet, and the protocol type
> >        differing from the existing states (2), the HoTI=20
> packet will also
> >        be dropped.
>=20
> 	Above sentence is not well formed.
> 	s/the protocol type differing/as the protocol type differs/
>=20
fixed.=20

>=20
> Section 5.3, para. 2:
>=20
> >     Issue 1: If the firewall(s) block ESP traffic, many of the MIPv6
> >        signaling (e.g.  Binding Update, HoT) may be dropped ...
> ...snip...
> >        performing Route Optimization, since Binding Update,=20
> HoT and other
> >        MIPv6 signaling must be protected by IPsec ESP.
>=20
> 	I don't see how this differs from Section 5.1, and don't see
>   	that it belongs here.

i have added text to this section. please see issue 44 =
http://www.mip4.org/issues/tracker/mip6/issue44

>=20
>=20

ciao
hannes

>=20
> 	Henrik
>=20
> Spencer's Review:
>=20
> From: Spencer Dawkins <spencer@mcsr-labs.org>
> To: Gen-Art Mailing List <gen-art@alvestrand.no>
> CC: Margaret Wasserman <margaret...snip... Gopal Dommety=20
> <gdommety@cisco.com>
> Subject: Gen-ART Review of draft-ietf-mip6-firewalls-02.txt
>=20
> Background for those on the CC list, who may be unaware of GenART:
> GenART is the Area Review Team for the General Area of the IETF.  We
> advise the General Area Director (i.e. the IETF/IESG chair) by
> providing more in depth reviews than he could do himself of documents
> that come up for final decision in IESG telechat.  I was selected
> as the GenART member to review this document.  Below is my review,
> which was written specifically with an eye to the GenART process, but
> since I believe that it will be useful to have these comments more
> widely distributed, others outside the GenART group are being copied.
>=20
> Intended status: Informational
>=20
> Summary - this document is very close to being ready for publication=20
> as Informational.
>=20
> I don't believe that Gen-ART reviews for Informational documents need=20
> to say much more than this, but, since I'm typing...
>=20
> - The document is clearly written and well-organized. Other reviewers=20
> might push back on the breezy English style, but I like it.
>=20
> - The first time there's a clue that firewalls are problematic for=20
> NON-mobile users is in the Conclusion:
>=20
>    Current firewalls may not only prevent route optimization but may
>    also prevent regular TCP and UDP sessions from being established in
>    some cases.  This document describes some of the issues between the
>    Mobile IPv6 protocol and current firewall technologies.
>=20
> It might be nice to call this issue out earlier in the draft, so that=20
> it's more obvious what ADDITIONAL problems happen when you go mobile.=20
> Firewalls that drop ESP by default, for instance, are problematic for=20
> non-mobile users - stuff like that.
>=20
> - The stated goal for this document is to enable futher discussion; I=20
> didn't see any thought given to firewalls in transit networks between=20
> the home, visited, and correspondent networks, and I'll bet transit=20
> networks will have something like firewalls in place, in at least=20
> some environments. Even a statement that says "we don't think=20
> firewalls in transit networks will add any requirements for further=20
> work" would be useful.
>=20
> - The assumption that issues called out in this draft will be solved=20
> in MIP6 is stated at the end of the abstract. Although BEHAVE=20
> explicitly declares firewalls to be out of scope, it seems that=20
> what's needed is something like BRIDE of BEHAVE, developing BCP=20
> recommendations for firewall types, just as BEHAVE is doing for NAT=20
> types...
>=20
> Thanks,
>=20
> Spencer
>=20

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



From mip6-bounces@ietf.org Mon Oct 03 08:23:59 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EMPMN-0005mJ-7U; Mon, 03 Oct 2005 08:23:59 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EMPMH-0005mB-70
	for mip6@megatron.ietf.org; Mon, 03 Oct 2005 08:23:57 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA24739
	for <mip6@ietf.org>; Mon, 3 Oct 2005 08:23:52 -0400 (EDT)
Received: from dns2.tilab.com ([163.162.42.5])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EMPUk-0005Uf-A3
	for mip6@ietf.org; Mon, 03 Oct 2005 08:32:39 -0400
Received: from iowa2k01b.cselt.it ([163.162.242.202])
	by dns2.cselt.it (PMDF V6.1 #38895)
	with ESMTP id <0INS00H63AF6K5@dns2.cselt.it> for mip6@ietf.org; Mon,
	03 Oct 2005 14:23:30 +0200 (MEST)
Received: from EXC01B.cselt.it ([163.162.4.199]) by iowa2k01b.cselt.it with
	Microsoft SMTPSVC(6.0.3790.211); Mon, 03 Oct 2005 14:21:18 +0200
Date: Mon, 03 Oct 2005 14:23:29 +0200
From: Gerardo Giaretta <Gerardo.Giaretta@TILAB.COM>
Subject: RE: [Mip6] review of draft-ietf-mip6-bootstrapping-split-00.txt
To: Vijay Devarapallli <dvijay@gmail.com>
Message-id: <DA62A6E0CDD1B34A84557FF1AC850C57016E9B43@EXC01B.cselt.it>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.3790.326
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: quoted-printable
Importance: normal
Priority: normal
Thread-Topic: [Mip6] review of draft-ietf-mip6-bootstrapping-split-00.txt
Thread-Index: AcXGGuSEKUO2fl7USwadZC1vi1DxLAB+TyaQ
Content-class: urn:content-classes:message
X-OriginalArrivalTime: 03 Oct 2005 12:21:18.0796 (UTC)
	FILETIME=[F52968C0:01C5C814]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 995b2e24d23b953c94bac5288c432399
Content-Transfer-Encoding: quoted-printable
Cc: mip6@ietf.org, Kilian Weniger <Kilian.Weniger@eu.panasonic.com>,
	Vijay Devarapalli <vijayd@iprg.nokia.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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Vijay,=20

few comments below...

> there is some confusion.
>=20
> Jim, Kilian's main concern is when the MN configures a HA
> from the visited link (using location specific HA FQDN).
> the issue is if the MN configures a HA and HoA from the
> visited link and then has its DNS entry updated, then the
> CN knows where the MN is currently located. the MN can
> continue doing DNS updates for home address configured from
> the home link. causes no harm. but when it does a DNS update
> for the home address configured from a HA on a visited link,
> it immediately reveals its location to the CN. maybe we
> could add the following to the security considerations section
>=20
>   A mobile node could hide its location from its correspondent
>   node by reverse tunneling all traffic through the home agent.
>   The same mobile node could roam and configure a home agent
>   and home address from a visited link. If the home agent
>   updates the DNS entry of the mobile node with its new home
>   address, then this may reveal the current location of the
>   mobile node to the correspondent node. In such a if the mobile
>   node does not want the correspondent node to know its current
>   location, then it should not request the home agent to update
>   the DNS entry.
>=20
> comments?
>

I would mitigate a little bit this possible threat to the location
privacy of the MN.

First of all, we don't specify a way to allocate a local HA in
draft-ietf-mip6-bootstrapping-split. This is correct since in split
scenario there is no assumption on ASP. Therefore, this text may be more
appropriate to the integrated scenario.

Besides that, based on the HoA, a CN can only guess the location from
which the MN performed the bootstrapping procedure. Subsequent movements
are not visible to CNs if bidirectional tunneling is used. This may or
may not be an issue depending the mobility pattern of the MN, too. I'd
suggest to include a sentence about this in the draft, if we want to
address this issue.

--Gerardo
=20
> Vijay
>=20
> On 9/30/05, James Kempf <Kempf@docomolabs-usa.com> wrote:
> > Comments.
> >
> > "Note that local HA assignment combined with DNS updates=20
> may violate the
> > location privacy of MN. A known solution to location=20
> privacy is to hide
> > the CoA from CN by using reverse tunneling to the HA
> > [draft-koodli-mip6-location-privacy-solutions-00.txt].=20
> However, reverse
> > tunneling may significantly decrease routing efficiency,=20
> depending on
> > how far the HA is off the direct path between MN and CN.The
> > bootstrapping solution supports local HA assignment to=20
> improve routing
> > efficiency, but since the HoA obtained from a local HA assignment
> > topologically belongs to the visited network, it contains location
> > information. Consequently, it must carefully be considered=20
> to whom this
> > HoA is revealed and whether DNS updates are requested for=20
> this HoA. The
> > latter can even enable others to track MN's movement, if=20
> the MN uses an
> > eager strategy for local HA assignment. On the other hand,=20
> if the HoA is
> > hidden from other nodes, they cannot reach the MN at this=20
> HoA and, thus,
> > cannot benefit from the local HA assignment in terms of routing
> > efficiency. "
> >
> >  jak>> I have a couple problems with this:
> >
> > 1)  Reverse tunneling is the default in IPv6, that is to=20
> say, if an HA is
> > used, reverse tunneling must be used, unless the traffic is=20
> route optimized.
> > So it is more accurate to say that in order to protect=20
> privacy, the MN must
> > not route optimize traffic.
> >
> > 2) The solution in draft-ietf-mip6-bootstrapping-split does=20
> not specify
> > anything for local home agent assignment. There is nothing=20
> in the protocol
> > to actually move the HA from the MSP's network to the=20
> serving network. The
> > MN gets to choose an HA from whatever HAs the MSP's DNS SRV=20
> RR advertises.
> > If that happens to be in the serving network, then=20
> correspondents will be
> > able to obtain some information about where the MN is, but=20
> it could equally
> > well be on the other side of the globe.
> >
> > Note that the integrated scenerio (which the DT is=20
> currently working on)
> > will have a mechanism whereby a local home agent can be=20
> assigned, since the
> > MN gets the HA address from the local DHCP server.
> >
> > 3) Since the HoA doesn't change once the MN has established=20
> it, I fail to
> > see how an attacker can track the MN's location. Once the=20
> MN has established
> > the HoA, it will appear to be at a fixed topological=20
> location in the MSP's
> > network regardless of where the care of address is, if=20
> route optimization is
> > not used.
> >
> > So I think the risk is considerably less that is portrayed=20
> by the above
> > text. I think the following text would be more accurate:
> >
> >     Updating the mobile node's FQDN in the DNS
> >     with the mobile node's home address has the
> >     potential to expose some information about
> >     the mobile node's location to correspondents
> >     if the home agent selected by the mobile
> >     node is in the serving network access provider's
> >     network (that is, the serving network access
> >     provider is also acting as the mobility service
> >     provider). The risk here is not as deep as
> >     with route optimization, since the mobile node
> >     will effectively appear to be at a fixed topological
> >     location in the mobility service provider's network
> >     regardless of where the care of address is. To
> >     mitigate the risk, the mobile node should
> >     either not request DNS update or be careful
> >     to select a home agent that is not within the
> >     serving network access provider's network.
> >
> >
> >             jak
> >
> >
> >
> >
> >
> >
> > _______________________________________________
> > Mip6 mailing list
> > Mip6@ietf.org
> > https://www1.ietf.org/mailman/listinfo/mip6
> >
>=20


Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia =
S.p.A.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
CONFIDENTIALITY NOTICE
This message and its attachments are addressed solely to the persons
above and may contain confidential information. If you have received
the message in error, be informed that any use of the content hereof
is prohibited. Please return it immediately to the sender and delete
the message. Should you have any questions, please send an e_mail to
MailAdmin@tilab.com. Thank you
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

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



From mip6-bounces@ietf.org Mon Oct 03 08:27:55 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EMPQB-0006j7-J6; Mon, 03 Oct 2005 08:27:55 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ELX6F-0002d4-3K
	for mip6@megatron.ietf.org; Fri, 30 Sep 2005 22:27:43 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA04229
	for <mip6@ietf.org>; Fri, 30 Sep 2005 22:27:41 -0400 (EDT)
Received: from smtp.andrew.cmu.edu ([128.2.10.82])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ELXED-0006SG-SW
	for mip6@ietf.org; Fri, 30 Sep 2005 22:35:58 -0400
Received: from webmail.andrew.cmu.edu (WEBMAIL9.andrew.cmu.edu [128.2.10.108])
	(user=franckl mech=GSSAPI (56 bits))
	by smtp.andrew.cmu.edu (8.13.4/8.13.4) with ESMTP id j912Rddv009258;
	Fri, 30 Sep 2005 22:27:40 -0400
Received: from 141.151.141.45
	(SquirrelMail authenticated user franckl@ANDREW.CMU.EDU);
	by webmail.andrew.cmu.edu with HTTP;
	Fri, 30 Sep 2005 22:27:41 -0400 (EDT)
Message-ID: <50330.141.151.141.45.1128133661.squirrel@141.151.141.45>
Date: Fri, 30 Sep 2005 22:27:41 -0400 (EDT)
Subject: Re: [Mip6] Fwd: Re: draft-ietf-mip6-firewalls-02.txt
From: "Franck Le" <franckle@cmu.edu>
To: margaret@thingmagic.com, mip6@ietf.org, henrik@levkowetz.com,
	smb@research.att.com
User-Agent: SquirrelMail/1.5.1 [CVS]
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
X-Spam-Score: 0.8 (/)
X-Scan-Signature: c54bc2f42d02429833c0ca4b8725abd7
Content-Transfer-Encoding: 8bit
X-Mailman-Approved-At: Mon, 03 Oct 2005 08:27:54 -0400
Cc: gdommety@cisco.com, stefano.faccin@nokia.com, basavaraj.patil@nokia.com
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: franckle@cmu.edu
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Hello,

Thank you Margaret, Steve, Henrik and Spencer for reviewing the document and for all your comments.

Please find below few questions to make sure I correctly understood your
suggestions, and on ways to incorporate them.

> Steve's Review:
[...] 
> What I'd really like to see in this document, if possible, is a set of 
> rules and algorithms, as suggestions for site administrators and 
> MIPv6-aware firewall vendors.  But maybe that should be published 
> separately.

The objective of this I-D from the perspective of the MIP6 WG and the MIP6 protocol was to raise the awareness w.r.t the issues that firewalls raise in deployment environments. To this end the I-D captures the scenarios and the problems that are posed by the existence of firewalls. The guidelines for firewall administrators and vendors would be potentially a separate document that describes how the issues posed in this I-D may be addressed. While the authors agree that such a document is useful and should be written, we believe that this is a followup to the current I-D and one that can be done independently.

> Section 4: Some firewalls check TCP sequence numbers as well.
> Is UDP behavior significant here?  Application-level proxies for all sorts
> of protocols?

Yes, firewalls now offer a wide range of features. However we did not describe all of them. We instead intended to focus on the features we thought may cause issues with the Mobile IP protocol.

> 5.1: It's not so much that firewalls drop ESP by default, it's that they
> can't tell if inbound ESP packets are legitimate, since there's no useful
> state created by the outbound ESP packets.
> 
> 
> A more general analysis of the issues presented by 5.1 is that firewalls
> are topological elements, not logical ones.  Thus, an MN behind a firewall
> is protected by it/subject to its rules, because it's part of the
> protected topology.  The particular issues discussed here are just special
> cases of that situation.

I agree with you. Would adding the following sentence capture your comment? 
"The issues described above result from the fact that the MN is behind the firewall. Consequently, the MNs communication capability with other nodes is affected by the firewall rules."

> 5.2: In Figure 2, label CN as "A".
> 
> 
> Issue 3: In many environments with more than one firewall, they already
> share state.  This is a necessity because routing is generally asymmetric.
> Consider this:
> 
> 
> +----------------+ |                | |        A      FW1 |                |
>  |                | |                | |                | |                |
>  |               FW2      B |                | +----------------+
> 
> 
> A is closer to FW1, so its packets exit via FW1.  B is closer to FW2, and
> they advertise the same CIDR block, so the return packets will try to go
> that way.  That fails unless there's state-sharing, without any mobility.

Yes. As you pointed out, many firewalls already share state (e.g. firewall clusters dealing with asymmetric routes). In such cases, Mobile IP does not create new issues. However I was thinking that when firewalls share the states, they all have to store the same information. When considering large networks, one firewall may not be enough to support all the users. Instead we may need several of them. 

When a user moves between areas served by different firewalls which do not share states, we may have the issues described in the document. Would you agree? 

I will update the document adding the current state of the art you highlighted, and clarifying scenarios when mobility may present new issues. 

> 5.3: It's generally safe to permit ESP traffic to a known-locked down host.
> If there's a generic HA, it can be a valid recipient of IPsec without
> compromising network security.  The same applies to Issue 2.  Issue 3 is
> the same situation described earlier.

I agree with you. This would work well if the firewall can be configured with the HA of the MN. However when the MN is roaming to a visited network, it may be more difficult to configure the firewall(s) protecting the visited network with the MN's HA. What do you think?
I guess you are moving to the solution space :)

> Henrik's Review:
[..]
> * While the problems described in 5.1, 5.2 and 5.4 may require product and
> protocol modifications, the problems in 5.3 have more a character of
> installation and configuration mistakes, and should maybe be labelled as
> such.

I agree with you. I was just afraid that we may start discussing solutions but we can add few sentences to highlight these differences. We could explain in the conclusion that "Some of the issues described in this document may require changes to firewalls or to the protocols. Others may only require the appropriate rules and configuration to be in place." 

> * MIPv6 permits the use of AH as an alternative to ESP in some cases - I
> wonder if this document should cover this case, as well.  I believe that
> AH may have less problems than ESP, but it also gives less protection.
> ESP is in particular recommended for the HoT and HoTI messages between HA
> and MN.

I agree with your comment and analysis. As you pointed out, AH is permitted in the MIPv6 spec., however it seems that the recommendation for ESP was stronger. For this reason, we focused on ESP.

> Section 4:
> 
> 
> This section lacks an expansion of HoT. However, if each abbreviation is
> expanded on the first of the first few instances of use, I'd probably be
> just as happy without this section.

Thank you for pointing this out. We will address that as you suggested.

> Section 5.1:
> 
> 
> 5.1  Scenario where the Mobile Node is in a network protected by 
> firewall(s)
> 
> It's in Section 5.4, actually.

Yes, we will move that section in section 5.1

> Section 5.2:
> 
> 
> I'd be happier if you did not use the designation 'A' for the CN here,
> after having used 'A' for the MN in Section 5.1. Maybe call the nodes 'C'
> and 'D' here instead?

That is a good point. I agree this may be misleading.

> Section 5.2, para. 22:
> 
> 
> The HoTI is a Mobility Header packet, and the protocol type differing from
> the existing states (2), the HoTI packet will also be dropped.
> 
> Above sentence is not well formed. s/the protocol type differing/as the
> protocol type differs/

Thank you.

> Section 5.3, para. 2:
> 
> 
> Issue 1: If the firewall(s) block ESP traffic, many of the MIPv6 signaling
> (e.g.  Binding Update, HoT) may be dropped ...
> 
> ...snip... performing Route Optimization, since Binding Update, HoT and
> other MIPv6 signaling must be protected by IPsec ESP.
> 
> I don't see how this differs from Section 5.1, and don't see that it
> belongs here.

The issues are similar as you pointed out. However the firewall in section 5.1 is the one protecting the MN (e.g. FW in the visited network) while the firewall in section 5.3 is the one protecting the HA. 

I hope this clarifies the intentions. However I agree that the current text can be confusing. 

Therefore, at the beginning of section 5.3, we will sub /Let's consider a MN moving into a network protected by firewall(s). The following issues may exist:/ with /In the scenarios where the Home Agent is in a network protected by firewall(s), the following issues may exist:/  

and in issue 1, we will sub /If the firewall(s) block ESP traffic/ by /If the firewall(s) protecting the Home Agent block ESP traffic/ 

Would this be clearer?

Thank you again for all your comments!

Franck




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



From mip6-bounces@ietf.org Mon Oct 03 08:27:57 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EMPQC-0006ja-Ry; Mon, 03 Oct 2005 08:27:57 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EM7uM-0002dt-Na; Sun, 02 Oct 2005 13:45:56 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25392;
	Sun, 2 Oct 2005 13:45:51 -0400 (EDT)
Received: from zeus.cc.ucy.ac.cy ([194.42.1.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1EM82V-0006pH-HV; Sun, 02 Oct 2005 13:54:28 -0400
Received: from Mitsotakis (dhcppol114.polytech.ucy.ac.cy [194.42.10.114])
	by zeus.cc.ucy.ac.cy (8.9.3/8.9.3) with ESMTP id UAA50882;
	Sun, 2 Oct 2005 20:40:20 +0300
Message-Id: <200510021740.UAA50882@zeus.cc.ucy.ac.cy>
From: "Toumpis Stavros" <toumpis@ucy.ac.cy>
To: "Toumpis Stavros" <toumpis@ucy.ac.cy>
Date: Sun, 2 Oct 2005 19:42:43 +0200
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_0023_01C5C789.7C1539E0"
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
Thread-Index: AcXHeLFf/pl5XlSaT+CgLgdkGvxXSQ==
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 6ddc332208ea195635a308de25a77b60
X-Mailman-Approved-At: Mon, 03 Oct 2005 08:27:54 -0400
Cc: 
Subject: [Mip6] WiOpt 2006, Boston, MA, April 3-7: Final Call for Papers
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

This is a multi-part message in MIME format.

------=_NextPart_000_0023_01C5C789.7C1539E0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_001_0024_01C5C789.7C1539E0"


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

   FINAL CALL FOR PAPERS 

SUBMISSION DEADLINE *THIS WEDNESDAY* OCT. 5, 5pm EST 

 

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

WIOPT 2006

 

4th Intl. Symposium on Modeling and Optimization in

Mobile, Ad Hoc, and Wireless Networks (WiOpt'06)

 

Boston, Massachusetts, April 3-7, 2006

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

 

SCOPE OF THE SYMPOSIUM

 

The complexity of mobile, ad hoc, and wireless networks requires

thoroughly founded models capturing their essential characteristics

and new optimization techniques building upon such models. Insights

into both the theoretical aspects of these problems as well as

practical methods and tools are necessary. This symposium intends to

bring together researchers and practitioners working on optimization

issues from different perspectives, including performance analysis,

mobile networking, wireless communication, and optimization theory.

 

Contributions to this conference should show new modeling and

optimization techniques suitable for mobile/wireless networks or

innovative applications of these techniques to improve network

operation. Topics of interest include, but are not limited to:

* Modeling techniques and tools for wireless networks

* Performance characterization & optimization of wireless networks

* Wireless network optimization: Applications, algorithms, and tools

* Protocol design for optimal wireless network utilization

* Models and optimization approaches for energy efficiency, QoS,

bandwidth economy and other aspects of wireless networks

* Models and optimization techniques for non-standard network

paradigms like sensor, vehicular, body area networks

* Security and co-operation models for mobile and ad hoc networks

* Pricing and incentives in wireless networks

* Game theoretic techniques for mobile/wireless networks

 

SUBMISSION INSTRUCTIONS

 

Papers should be submitted as extended abstracts of up to 8 pages,

single column format; and contain sufficient information to allow for

a detailed review. The final manuscript will be 10 pages in

double column format. Selected papers from WiOpt 2006 will appear in

a special issue of ACM/Kluwer Monet.

 

IMPORTANT DATES

 

Submission deadline: Oct. 5, 2005 (5pm EST)

Notification of acceptance: Dec. 5, 2005

Camera-ready copy: Jan. 5, 2006

 

Papers should be submitted in pdf or ps format through the EDAS system

(http://edas.info). For more details, please visit http://www.wiopt.org

 

SPONSORSHIP

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

WiOpt is sponsored by Create-net, ICST, Boston University, INRIA, and Intel,
and technically sponsored by the IEEE Information Theory and Control Systems
Societies and IFIP TC6, WG 6.3 (Performance of Communication Systems).

 


------=_NextPart_001_0024_01C5C789.7C1539E0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

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

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"PlaceName"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"PlaceType"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"State"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"City"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"place"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:595.3pt 841.9pt;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

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

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>&nbsp;&nbsp; FINAL CALL FOR PAPERS =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>SUBMISSION DEADLINE *<b><span =
style=3D'font-weight:
bold'>THIS WEDNESDAY</span></b>* OCT. 5, 5pm EST =
<o:p></o:p></span></font></p>

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

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>WIOPT 2006<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>4th Intl. Symposium on Modeling and =
Optimization in<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>Mobile, Ad Hoc, and Wireless Networks =
(WiOpt'06)<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><st1:place w:st=3D"on"><st1:City w:st=3D"on"><font =
size=3D2
  face=3DArial><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:Arial'>Boston</span></font></st1:Ci=
ty><font
 size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:Arial'>,
 <st1:State =
w:st=3D"on">Massachusetts</st1:State></span></font></st1:place><font
size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:Arial'>,
April 3-7, 2006<o:p></o:p></span></font></p>

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

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>SCOPE OF THE =
SYMPOSIUM<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>The complexity of mobile, ad hoc, and wireless
networks requires<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>thoroughly founded models capturing their =
essential characteristics<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>and new optimization techniques building upon =
such
models. Insights<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>into both the theoretical aspects of these =
problems
as well as<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>practical methods and tools are necessary. =
This
symposium intends to<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>bring together researchers and practitioners =
working
on optimization<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>issues from different perspectives, including
performance analysis,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>mobile networking, wireless communication, and
optimization theory.<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>Contributions to this conference should show =
new
modeling and<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>optimization techniques suitable for =
mobile/wireless
networks or<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>innovative applications of these techniques to
improve network<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>operation. Topics of interest include, but are =
not
limited to:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>* Modeling techniques and tools for wireless =
networks<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>* Performance characterization &amp; =
optimization of
wireless networks<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>* Wireless network optimization: Applications,
algorithms, and tools<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>* Protocol design for optimal wireless network
utilization<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>* Models and optimization approaches for =
energy
efficiency, QoS,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>bandwidth economy and other aspects of =
wireless
networks<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>* Models and optimization techniques for =
non-standard
network<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>paradigms like sensor, vehicular, body area =
networks<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>* Security and co-operation models for mobile =
and ad
hoc networks<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>* Pricing and incentives in wireless =
networks<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>* Game theoretic techniques for =
mobile/wireless
networks<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>SUBMISSION =
INSTRUCTIONS<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>Papers should be submitted as extended =
abstracts of
up to 8 pages,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>single column format; and contain sufficient
information to allow for<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>a detailed review. The final manuscript will =
be 10
pages in<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>double column format. Selected papers from =
WiOpt 2006
will appear in<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>a special issue of ACM/Kluwer =
Monet.<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>IMPORTANT DATES<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>Submission deadline: Oct. 5, 2005 (5pm =
EST)<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>Notification of acceptance: Dec. 5, =
2005<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>Camera-ready copy: Jan. 5, =
2006<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>Papers should be submitted in pdf or ps format
through the EDAS system<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>(http://edas.info). For more details, please =
visit
http://www.wiopt.org<o:p></o:p></span></font></p>

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

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

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


<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-US =
style=3D'font-size:
10.0pt;font-family:Arial'>WiOpt is sponsored by Create-net, ICST, =
<st1:place
w:st=3D"on"><st1:PlaceName w:st=3D"on">Boston</st1:PlaceName> =
<st1:PlaceType w:st=3D"on">University</st1:PlaceType></st1:place>,
INRIA, and Intel, and technically sponsored by the IEEE Information =
Theory and
Control Systems Societies and IFIP TC6, WG 6.3 (Performance of =
Communication
Systems).<o:p></o:p></span></font></p>

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

</div>

</body>

</html>

------=_NextPart_001_0024_01C5C789.7C1539E0--

------=_NextPart_000_0023_01C5C789.7C1539E0
Content-Type: application/pdf;
	name="wiopt06cfp.pdf"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
	filename="wiopt06cfp.pdf"
Content-Transfer-Encoding: base64

JVBERi0xLjQNJeLjz9MNCjYgMCBvYmo8PC9IWzI0NzM2IDE2OTFdL0xpbmVhcml6ZWQgMS9FIDMz
NjY2MS9MIDM0MDU1NC9OIDEvTyA5L1QgMzQwMzg4Pj4NZW5kb2JqDSAgICAgICAgICAgICAgICAg
DQp4cmVmDQo2IDEyMjINCjAwMDAwMDAwMTYgMDAwMDAgbg0KMDAwMDAyNjQyNyAwMDAwMCBuDQow
MDAwMDI0NzM2IDAwMDAwIG4NCjAwMDAwMjY1MDMgMDAwMDAgbg0KMDAwMDAyNjY4MCAwMDAwMCBu
DQowMDAwMDQzNzM0IDAwMDAwIG4NCjAwMDAwNDQyMzYgMDAwMDAgbg0KMDAwMDA0NDc3MiAwMDAw
MCBuDQowMDAwMDQ0OTAyIDAwMDAwIG4NCjAwMDAwNDUzMjEgMDAwMDAgbg0KMDAwMDA0NTM1NSAw
MDAwMCBuDQowMDAwMDQ1Mzk5IDAwMDAwIG4NCjAwMDAwNDU0NDMgMDAwMDAgbg0KMDAwMDA0NTQ4
NyAwMDAwMCBuDQowMDAwMDQ5NjE2IDAwMDAwIG4NCjAwMDAwNDk5OTggMDAwMDAgbg0KMDAwMDA1
NDA5NyAwMDAwMCBuDQowMDAwMDU1OTYwIDAwMDAwIG4NCjAwMDAwNTc2ODEgMDAwMDAgbg0KMDAw
MDA1OTM5MyAwMDAwMCBuDQowMDAwMDYwOTU2IDAwMDAwIG4NCjAwMDAwNjI1MzUgMDAwMDAgbg0K
MDAwMDA2NDQ1NyAwMDAwMCBuDQowMDAwMDY3MTI2IDAwMDAwIG4NCjAwMDAwNjc0MjEgMDAwMDAg
bg0KMDAwMDA2Nzg2MCAwMDAwMCBuDQowMDAwMDY4NDY4IDAwMDAwIG4NCjAwMDAwODQ0MjcgMDAw
MDAgbg0KMDAwMDA4NDcwOSAwMDAwMCBuDQowMDAwMDg0OTQ4IDAwMDAwIG4NCjAwMDAwOTIwMjIg
MDAwMDAgbg0KMDAwMDA5MjI1MSAwMDAwMCBuDQowMDAwMDkyNDQxIDAwMDAwIG4NCjAwMDAwOTI3
MzggMDAwMDAgbg0KMDAwMDA5Mjk4MyAwMDAwMCBuDQowMDAwMTAzODY1IDAwMDAwIG4NCjAwMDAx
MDQxNDUgMDAwMDAgbg0KMDAwMDExMTAzMCAwMDAwMCBuDQowMDAwMTIwMTA2IDAwMDAwIG4NCjAw
MDAxMjIzNjYgMDAwMDAgbg0KMDAwMDEyMjU5OCAwMDAwMCBuDQowMDAwMTIyNzMxIDAwMDAwIG4N
CjAwMDAxMjI5MjYgMDAwMDAgbg0KMDAwMDEyMzA1OSAwMDAwMCBuDQowMDAwMTIzMjU0IDAwMDAw
IG4NCjAwMDAxMjMzOTAgMDAwMDAgbg0KMDAwMDEyMzU4NSAwMDAwMCBuDQowMDAwMTIzNzI1IDAw
MDAwIG4NCjAwMDAxMjM5MjAgMDAwMDAgbg0KMDAwMDEyNDA1NiAwMDAwMCBuDQowMDAwMTI0MTg5
IDAwMDAwIG4NCjAwMDAxMjQzODQgMDAwMDAgbg0KMDAwMDEyNDUyMCAwMDAwMCBuDQowMDAwMTI0
NjU2IDAwMDAwIG4NCjAwMDAxMjQ4NTEgMDAwMDAgbg0KMDAwMDEyNDk5MSAwMDAwMCBuDQowMDAw
MTI1MTI3IDAwMDAwIG4NCjAwMDAxMjUzMjIgMDAwMDAgbg0KMDAwMDEyNTQ2NSAwMDAwMCBuDQow
MDAwMTI1NjA1IDAwMDAwIG4NCjAwMDAxMjU3NDEgMDAwMDAgbg0KMDAwMDEyNTkzNiAwMDAwMCBu
DQowMDAwMTI2MTA3IDAwMDAwIG4NCjAwMDAxMjYyNDcgMDAwMDAgbg0KMDAwMDEyNjM4NyAwMDAw
MCBuDQowMDAwMTI2NTgyIDAwMDAwIG4NCjAwMDAxMjY3NzEgMDAwMDAgbg0KMDAwMDEyNjkxMSAw
MDAwMCBuDQowMDAwMTI3MTA2IDAwMDAwIG4NCjAwMDAxMjczMDEgMDAwMDAgbg0KMDAwMDEyNzQ0
MSAwMDAwMCBuDQowMDAwMTI3NjM2IDAwMDAwIG4NCjAwMDAxMjc4NDAgMDAwMDAgbg0KMDAwMDEy
Nzk4MCAwMDAwMCBuDQowMDAwMTI4MTM1IDAwMDAwIG4NCjAwMDAxMjgzMDAgMDAwMDAgbg0KMDAw
MDEyODUxMCAwMDAwMCBuDQowMDAwMTI4NjUzIDAwMDAwIG4NCjAwMDAxMjg4MDggMDAwMDAgbg0K
MDAwMDEyODk3MyAwMDAwMCBuDQowMDAwMTI5MTY1IDAwMDAwIG4NCjAwMDAxMjkzMTcgMDAwMDAg
bg0KMDAwMDEyOTQ2MCAwMDAwMCBuDQowMDAwMTI5NjE1IDAwMDAwIG4NCjAwMDAxMjk3ODAgMDAw
MDAgbg0KMDAwMDEzMDAwMiAwMDAwMCBuDQowMDAwMTMwMTQyIDAwMDAwIG4NCjAwMDAxMzAyOTEg
MDAwMDAgbg0KMDAwMDEzMDQ0MCAwMDAwMCBuDQowMDAwMTMwNjM1IDAwMDAwIG4NCjAwMDAxMzA3
OTcgMDAwMDAgbg0KMDAwMDEzMDk0MCAwMDAwMCBuDQowMDAwMTMxMDg5IDAwMDAwIG4NCjAwMDAx
MzEyNDEgMDAwMDAgbg0KMDAwMDEzMTQ3NiAwMDAwMCBuDQowMDAwMTMxNjIwIDAwMDAwIG4NCjAw
MDAxMzE3NzYgMDAwMDAgbg0KMDAwMDEzMTk0MiAwMDAwMCBuDQowMDAwMTMyMDk4IDAwMDAwIG4N
CjAwMDAxMzIyOTcgMDAwMDAgbg0KMDAwMDEzMjQ0MSAwMDAwMCBuDQowMDAwMTMyNTk3IDAwMDAw
IG4NCjAwMDAxMzI3NjMgMDAwMDAgbg0KMDAwMDEzMjkxOSAwMDAwMCBuDQowMDAwMTMzMDUzIDAw
MDAwIG4NCjAwMDAxMzMyNDkgMDAwMDAgbg0KMDAwMDEzMzM5NiAwMDAwMCBuDQowMDAwMTMzNTUy
IDAwMDAwIG4NCjAwMDAxMzM3MTggMDAwMDAgbg0KMDAwMDEzMzg3MSAwMDAwMCBuDQowMDAwMTM0
MDE4IDAwMDAwIG4NCjAwMDAxMzQyMTcgMDAwMDAgbg0KMDAwMDEzNDM2NCAwMDAwMCBuDQowMDAw
MTM0NTIwIDAwMDAwIG4NCjAwMDAxMzQ2ODYgMDAwMDAgbg0KMDAwMDEzNDgzOSAwMDAwMCBuDQow
MDAwMTM0OTg5IDAwMDAwIG4NCjAwMDAxMzUxMzMgMDAwMDAgbg0KMDAwMDEzNTMxNyAwMDAwMCBu
DQowMDAwMTM1NDY0IDAwMDAwIG4NCjAwMDAxMzU2MjAgMDAwMDAgbg0KMDAwMDEzNTc4NiAwMDAw
MCBuDQowMDAwMTM1OTM2IDAwMDAwIG4NCjAwMDAxMzYwODkgMDAwMDAgbg0KMDAwMDEzNjMwNiAw
MDAwMCBuDQowMDAwMTM2NDYyIDAwMDAwIG4NCjAwMDAxMzY2MjggMDAwMDAgbg0KMDAwMDEzNjc3
NSAwMDAwMCBuDQowMDAwMTM2OTM4IDAwMDAwIG4NCjAwMDAxMzcwNzIgMDAwMDAgbg0KMDAwMDEz
NzI4MyAwMDAwMCBuDQowMDAwMTM3NDY3IDAwMDAwIG4NCjAwMDAxMzc2MzMgMDAwMDAgbg0KMDAw
MDEzNzg0NyAwMDAwMCBuDQowMDAwMTM4MTE2IDAwMDAwIG4NCjAwMDAxMzgyODIgMDAwMDAgbg0K
MDAwMDEzODQzOCAwMDAwMCBuDQowMDAwMTM4NjA0IDAwMDAwIG4NCjAwMDAxMzg4ODggMDAwMDAg
bg0KMDAwMDEzOTA0NCAwMDAwMCBuDQowMDAwMTM5MjA3IDAwMDAwIG4NCjAwMDAxMzk0ODUgMDAw
MDAgbg0KMDAwMDEzOTY0NCAwMDAwMCBuDQowMDAwMTM5ODA3IDAwMDAwIG4NCjAwMDAxNDAwNzYg
MDAwMDAgbg0KMDAwMDE0MDIzNSAwMDAwMCBuDQowMDAwMTQwMzk0IDAwMDAwIG4NCjAwMDAxNDA2
NjMgMDAwMDAgbg0KMDAwMDE0MDgyNiAwMDAwMCBuDQowMDAwMTQwOTc5IDAwMDAwIG4NCjAwMDAx
NDEyNDUgMDAwMDAgbg0KMDAwMDE0MTQ0MSAwMDAwMCBuDQowMDAwMTQxNzA0IDAwMDAwIG4NCjAw
MDAxNDE5MDAgMDAwMDAgbg0KMDAwMDE0MjE2MyAwMDAwMCBuDQowMDAwMTQyMzU5IDAwMDAwIG4N
CjAwMDAxNDI2MTkgMDAwMDAgbg0KMDAwMDE0MjgxNSAwMDAwMCBuDQowMDAwMTQzMDcyIDAwMDAw
IG4NCjAwMDAxNDMyNjggMDAwMDAgbg0KMDAwMDE0MzUyNSAwMDAwMCBuDQowMDAwMTQzNzIxIDAw
MDAwIG4NCjAwMDAxNDM5NzIgMDAwMDAgbg0KMDAwMDE0NDE2OCAwMDAwMCBuDQowMDAwMTQ0NDE5
IDAwMDAwIG4NCjAwMDAxNDQ2MTUgMDAwMDAgbg0KMDAwMDE0NDg2MyAwMDAwMCBuDQowMDAwMTQ1
MDU5IDAwMDAwIG4NCjAwMDAxNDUyMDAgMDAwMDAgbg0KMDAwMDE0NTQ0MiAwMDAwMCBuDQowMDAw
MTQ1NjM4IDAwMDAwIG4NCjAwMDAxNDU4ODkgMDAwMDAgbg0KMDAwMDE0NjA4NSAwMDAwMCBuDQow
MDAwMTQ2MzMwIDAwMDAwIG4NCjAwMDAxNDY1MjYgMDAwMDAgbg0KMDAwMDE0Njc2NSAwMDAwMCBu
DQowMDAwMTQ2OTIxIDAwMDAwIG4NCjAwMDAxNDcwNzEgMDAwMDAgbg0KMDAwMDE0NzMwNCAwMDAw
MCBuDQowMDAwMTQ3NDU3IDAwMDAwIG4NCjAwMDAxNDc2MDEgMDAwMDAgbg0KMDAwMDE0Nzc1MSAw
MDAwMCBuDQowMDAwMTQ3OTcxIDAwMDAwIG4NCjAwMDAxNDgxMjEgMDAwMDAgbg0KMDAwMDE0ODI5
MyAwMDAwMCBuDQowMDAwMTQ4NTA0IDAwMDAwIG4NCjAwMDAxNDg2NTEgMDAwMDAgbg0KMDAwMDE0
ODgyNiAwMDAwMCBuDQowMDAwMTQ5MDMxIDAwMDAwIG4NCjAwMDAxNDkxNzIgMDAwMDAgbg0KMDAw
MDE0OTMxNiAwMDAwMCBuDQowMDAwMTQ5NDkxIDAwMDAwIG4NCjAwMDAxNDk2OTAgMDAwMDAgbg0K
MDAwMDE0OTgzNCAwMDAwMCBuDQowMDAwMTQ5OTc4IDAwMDAwIG4NCjAwMDAxNTAxNTYgMDAwMDAg
bg0KMDAwMDE1MDM0MyAwMDAwMCBuDQowMDAwMTUwNDkzIDAwMDAwIG4NCjAwMDAxNTA2MzcgMDAw
MDAgbg0KMDAwMDE1MDgxNSAwMDAwMCBuDQowMDAwMTUwOTQ5IDAwMDAwIG4NCjAwMDAxNTExMTgg
MDAwMDAgbg0KMDAwMDE1MTI3NCAwMDAwMCBuDQowMDAwMTUxNDE4IDAwMDAwIG4NCjAwMDAxNTE1
OTYgMDAwMDAgbg0KMDAwMDE1MTczNyAwMDAwMCBuDQowMDAwMTUxODgxIDAwMDAwIG4NCjAwMDAx
NTIwMzcgMDAwMDAgbg0KMDAwMDE1MjE4MSAwMDAwMCBuDQowMDAwMTUyMzU5IDAwMDAwIG4NCjAw
MDAxNTI1MDMgMDAwMDAgbg0KMDAwMDE1MjY2NiAwMDAwMCBuDQowMDAwMTUyODEwIDAwMDAwIG4N
CjAwMDAxNTI5ODUgMDAwMDAgbg0KMDAwMDE1MzEzNSAwMDAwMCBuDQowMDAwMTUzMzA0IDAwMDAw
IG4NCjAwMDAxNTM0NTEgMDAwMDAgbg0KMDAwMDE1MzYyNiAwMDAwMCBuDQowMDAwMTUzODIyIDAw
MDAwIG4NCjAwMDAxNTM5NjkgMDAwMDAgbg0KMDAwMDE1NDE0MSAwMDAwMCBuDQowMDAwMTU0MzA3
IDAwMDAwIG4NCjAwMDAxNTQ0NTcgMDAwMDAgbg0KMDAwMDE1NDYyMyAwMDAwMCBuDQowMDAwMTU0
Nzc5IDAwMDAwIG4NCjAwMDAxNTQ5MjkgMDAwMDAgbg0KMDAwMDE1NTA5MiAwMDAwMCBuDQowMDAw
MTU1MjQ1IDAwMDAwIG4NCjAwMDAxNTU1NDQgMDAwMDAgbg0KMDAwMDE1NTY4OCAwMDAwMCBuDQow
MDAwMTU1ODg0IDAwMDAwIG4NCjAwMDAxNTYwMTggMDAwMDAgbg0KMDAwMDE1NjE3MSAwMDAwMCBu
DQowMDAwMTU2MzY3IDAwMDAwIG4NCjAwMDAxNTY1MTEgMDAwMDAgbg0KMDAwMDE1NjY4MCAwMDAw
MCBuDQowMDAwMTU2ODc2IDAwMDAwIG4NCjAwMDAxNTcwMjMgMDAwMDAgbg0KMDAwMDE1NzE5OCAw
MDAwMCBuDQowMDAwMTU3Mzk0IDAwMDAwIG4NCjAwMDAxNTc1NDEgMDAwMDAgbg0KMDAwMDE1NzY4
OCAwMDAwMCBuDQowMDAwMTU3ODM1IDAwMDAwIG4NCjAwMDAxNTgwMzEgMDAwMDAgbg0KMDAwMDE1
ODE3OCAwMDAwMCBuDQowMDAwMTU4MzIyIDAwMDAwIG4NCjAwMDAxNTg0NjYgMDAwMDAgbg0KMDAw
MDE1ODY2MiAwMDAwMCBuDQowMDAwMTU4Nzk5IDAwMDAwIG4NCjAwMDAxNTg5NDYgMDAwMDAgbg0K
MDAwMDE1OTA4NyAwMDAwMCBuDQowMDAwMTU5MjgzIDAwMDAwIG4NCjAwMDAxNTk0MzAgMDAwMDAg
bg0KMDAwMDE1OTYyNiAwMDAwMCBuDQowMDAwMTU5NzcwIDAwMDAwIG4NCjAwMDAxNTk5MzYgMDAw
MDAgbg0KMDAwMDE2MDA4NiAwMDAwMCBuDQowMDAwMTYwMjMwIDAwMDAwIG4NCjAwMDAxNjAzOTYg
MDAwMDAgbg0KMDAwMDE2MDUzNyAwMDAwMCBuDQowMDAwMTYwNjc4IDAwMDAwIG4NCjAwMDAxNjA4
MjggMDAwMDAgbg0KMDAwMDE2MDk4NyAwMDAwMCBuDQowMDAwMTYxMTQzIDAwMDAwIG4NCjAwMDAx
NjEyODcgMDAwMDAgbg0KMDAwMDE2MTQ1MyAwMDAwMCBuDQowMDAwMTYxNTk3IDAwMDAwIG4NCjAw
MDAxNjE3NDEgMDAwMDAgbg0KMDAwMDE2MTg5NyAwMDAwMCBuDQowMDAwMTYyMDUwIDAwMDAwIG4N
CjAwMDAxNjIyMTYgMDAwMDAgbg0KMDAwMDE2MjM2MCAwMDAwMCBuDQowMDAwMTYyNTI2IDAwMDAw
IG4NCjAwMDAxNjI2NzAgMDAwMDAgbg0KMDAwMDE2MjgxMSAwMDAwMCBuDQowMDAwMTYyOTc3IDAw
MDAwIG4NCjAwMDAxNjMxMjcgMDAwMDAgbg0KMDAwMDE2MzI5NiAwMDAwMCBuDQowMDAwMTYzNDQw
IDAwMDAwIG4NCjAwMDAxNjM2MDYgMDAwMDAgbg0KMDAwMDE2Mzc1MCAwMDAwMCBuDQowMDAwMTYz
OTMxIDAwMDAwIG4NCjAwMDAxNjQwODEgMDAwMDAgbg0KMDAwMDE2NDI1MyAwMDAwMCBuDQowMDAw
MTY0Mzk3IDAwMDAwIG4NCjAwMDAxNjQ1NDEgMDAwMDAgbg0KMDAwMDE2NDY4NSAwMDAwMCBuDQow
MDAwMTY0ODM4IDAwMDAwIG4NCjAwMDAxNjQ5ODUgMDAwMDAgbg0KMDAwMDE2NTEzMiAwMDAwMCBu
DQowMDAwMTY1MzA3IDAwMDAwIG4NCjAwMDAxNjU0NTEgMDAwMDAgbg0KMDAwMDE2NTU5OCAwMDAw
MCBuDQowMDAwMTY1NzQyIDAwMDAwIG4NCjAwMDAxNjU4OTIgMDAwMDAgbg0KMDAwMDE2NjAzNiAw
MDAwMCBuDQowMDAwMTY2MTgzIDAwMDAwIG4NCjAwMDAxNjYzNTggMDAwMDAgbg0KMDAwMDE2NjUw
MiAwMDAwMCBuDQowMDAwMTY2NjQ5IDAwMDAwIG4NCjAwMDAxNjY3OTMgMDAwMDAgbg0KMDAwMDE2
Njk0MCAwMDAwMCBuDQowMDAwMTY3MDg3IDAwMDAwIG4NCjAwMDAxNjcyMzEgMDAwMDAgbg0KMDAw
MDE2NzM3MiAwMDAwMCBuDQowMDAwMTY3NTI1IDAwMDAwIG4NCjAwMDAxNjc2NjkgMDAwMDAgbg0K
MDAwMDE2NzgxNiAwMDAwMCBuDQowMDAwMTY3OTYwIDAwMDAwIG4NCjAwMDAxNjgxMDcgMDAwMDAg
bg0KMDAwMDE2ODI1NCAwMDAwMCBuDQowMDAwMTY4Mzk4IDAwMDAwIG4NCjAwMDAxNjg1MzIgMDAw
MDAgbg0KMDAwMDE2ODY2NiAwMDAwMCBuDQowMDAwMTY4ODE2IDAwMDAwIG4NCjAwMDAxNjg5NjAg
MDAwMDAgbg0KMDAwMDE2OTEwNyAwMDAwMCBuDQowMDAwMTY5MjU0IDAwMDAwIG4NCjAwMDAxNjkz
OTggMDAwMDAgbg0KMDAwMDE2OTU0MiAwMDAwMCBuDQowMDAwMTY5Njg5IDAwMDAwIG4NCjAwMDAx
Njk4MzYgMDAwMDAgbg0KMDAwMDE2OTk4MCAwMDAwMCBuDQowMDAwMTcwMTI3IDAwMDAwIG4NCjAw
MDAxNzAyNzEgMDAwMDAgbg0KMDAwMDE3MDQxOCAwMDAwMCBuDQowMDAwMTcwNTYyIDAwMDAwIG4N
CjAwMDAxNzA3MDYgMDAwMDAgbg0KMDAwMDE3MDg1OSAwMDAwMCBuDQowMDAwMTcxMDAzIDAwMDAw
IG4NCjAwMDAxNzExNDcgMDAwMDAgbg0KMDAwMDE3MTI5NCAwMDAwMCBuDQowMDAwMTcxNDQxIDAw
MDAwIG4NCjAwMDAxNzE1ODUgMDAwMDAgbg0KMDAwMDE3MTcyOSAwMDAwMCBuDQowMDAwMTcxODg4
IDAwMDAwIG4NCjAwMDAxNzIwMzIgMDAwMDAgbg0KMDAwMDE3MjE3NiAwMDAwMCBuDQowMDAwMTcy
MzIzIDAwMDAwIG4NCjAwMDAxNzI0NzAgMDAwMDAgbg0KMDAwMDE3MjYxNCAwMDAwMCBuDQowMDAw
MTcyNzU4IDAwMDAwIG4NCjAwMDAxNzI5MTcgMDAwMDAgbg0KMDAwMDE3MzA2MSAwMDAwMCBuDQow
MDAwMTczMjA1IDAwMDAwIG4NCjAwMDAxNzMzNTIgMDAwMDAgbg0KMDAwMDE3MzQ5OSAwMDAwMCBu
DQowMDAwMTczNjQ2IDAwMDAwIG4NCjAwMDAxNzM3OTAgMDAwMDAgbg0KMDAwMDE3Mzk0OSAwMDAw
MCBuDQowMDAwMTc0MDkzIDAwMDAwIG4NCjAwMDAxNzQyMzcgMDAwMDAgbg0KMDAwMDE3NDM4NCAw
MDAwMCBuDQowMDAwMTc0NTMxIDAwMDAwIG4NCjAwMDAxNzQ2NzggMDAwMDAgbg0KMDAwMDE3NDgy
MiAwMDAwMCBuDQowMDAwMTc0OTgxIDAwMDAwIG4NCjAwMDAxNzUxMjUgMDAwMDAgbg0KMDAwMDE3
NTI2OSAwMDAwMCBuDQowMDAwMTc1NDE2IDAwMDAwIG4NCjAwMDAxNzU1NjAgMDAwMDAgbg0KMDAw
MDE3NTcwNyAwMDAwMCBuDQowMDAwMTc1ODUxIDAwMDAwIG4NCjAwMDAxNzYwMTAgMDAwMDAgbg0K
MDAwMDE3NjE1NCAwMDAwMCBuDQowMDAwMTc2MzAxIDAwMDAwIG4NCjAwMDAxNzY0NDggMDAwMDAg
bg0KMDAwMDE3NjU5NSAwMDAwMCBuDQowMDAwMTc2NzQyIDAwMDAwIG4NCjAwMDAxNzY4OTggMDAw
MDAgbg0KMDAwMDE3NzA0MiAwMDAwMCBuDQowMDAwMTc3MTg2IDAwMDAwIG4NCjAwMDAxNzczMzkg
MDAwMDAgbg0KMDAwMDE3NzQ4MyAwMDAwMCBuDQowMDAwMTc3NjMzIDAwMDAwIG4NCjAwMDAxNzc3
ODAgMDAwMDAgbg0KMDAwMDE3NzkzMyAwMDAwMCBuDQowMDAwMTc4MDgwIDAwMDAwIG4NCjAwMDAx
NzgyMjQgMDAwMDAgbg0KMDAwMDE3ODM3MSAwMDAwMCBuDQowMDAwMTc4NTE1IDAwMDAwIG4NCjAw
MDAxNzg2OTMgMDAwMDAgbg0KMDAwMDE3ODg0MyAwMDAwMCBuDQowMDAwMTc4OTg3IDAwMDAwIG4N
CjAwMDAxNzkxMzcgMDAwMDAgbg0KMDAwMDE3OTI4MSAwMDAwMCBuDQowMDAwMTc5NDI4IDAwMDAw
IG4NCjAwMDAxNzk1NzIgMDAwMDAgbg0KMDAwMDE3OTc0NyAwMDAwMCBuDQowMDAwMTc5OTAwIDAw
MDAwIG4NCjAwMDAxODAwNTMgMDAwMDAgbg0KMDAwMDE4MDE5NyAwMDAwMCBuDQowMDAwMTgwMzQx
IDAwMDAwIG4NCjAwMDAxODA0ODUgMDAwMDAgbg0KMDAwMDE4MDYzMiAwMDAwMCBuDQowMDAwMTgw
Nzg1IDAwMDAwIG4NCjAwMDAxODA5ODEgMDAwMDAgbg0KMDAwMDE4MTEyOCAwMDAwMCBuDQowMDAw
MTgxMzI0IDAwMDAwIG4NCjAwMDAxODE0NzEgMDAwMDAgbg0KMDAwMDE4MTY2NyAwMDAwMCBuDQow
MDAwMTgxODE0IDAwMDAwIG4NCjAwMDAxODIwMTAgMDAwMDAgbg0KMDAwMDE4MjE1NyAwMDAwMCBu
DQowMDAwMTgyMzUzIDAwMDAwIG4NCjAwMDAxODI1MDAgMDAwMDAgbg0KMDAwMDE4MjY5NiAwMDAw
MCBuDQowMDAwMTgyODQzIDAwMDAwIG4NCjAwMDAxODMwMzkgMDAwMDAgbg0KMDAwMDE4MzE4MyAw
MDAwMCBuDQowMDAwMTgzMzc5IDAwMDAwIG4NCjAwMDAxODM1MTYgMDAwMDAgbg0KMDAwMDE4Mzc0
NCAwMDAwMCBuDQowMDAwMTgzODc4IDAwMDAwIG4NCjAwMDAxODQwMTUgMDAwMDAgbg0KMDAwMDE4
NDE1NiAwMDAwMCBuDQowMDAwMTg0Mjk3IDAwMDAwIG4NCjAwMDAxODQ0NDEgMDAwMDAgbg0KMDAw
MDE4NDU3NSAwMDAwMCBuDQowMDAwMTg0NzA5IDAwMDAwIG4NCjAwMDAxODQ4NDMgMDAwMDAgbg0K
MDAwMDE4NDk3NyAwMDAwMCBuDQowMDAwMTg1MTExIDAwMDAwIG4NCjAwMDAxODUyNDggMDAwMDAg
bg0KMDAwMDE4NTM4MiAwMDAwMCBuDQowMDAwMTg1NTIzIDAwMDAwIG4NCjAwMDAxODU2NTcgMDAw
MDAgbg0KMDAwMDE4NTc5NCAwMDAwMCBuDQowMDAwMTg1OTM4IDAwMDAwIG4NCjAwMDAxODYwNzIg
MDAwMDAgbg0KMDAwMDE4NjIwOSAwMDAwMCBuDQowMDAwMTg2MzUzIDAwMDAwIG4NCjAwMDAxODY0
OTAgMDAwMDAgbg0KMDAwMDE4NjYyNyAwMDAwMCBuDQowMDAwMTg2NzgwIDAwMDAwIG4NCjAwMDAx
ODY5MjEgMDAwMDAgbg0KMDAwMDE4NzA3NCAwMDAwMCBuDQowMDAwMTg3MjE1IDAwMDAwIG4NCjAw
MDAxODczNjggMDAwMDAgbg0KMDAwMDE4NzUxMiAwMDAwMCBuDQowMDAwMTg3NjU5IDAwMDAwIG4N
CjAwMDAxODc4MDYgMDAwMDAgbg0KMDAwMDE4Nzk1MyAwMDAwMCBuDQowMDAwMTg4MTAzIDAwMDAw
IG4NCjAwMDAxODgyNDcgMDAwMDAgbg0KMDAwMDE4ODM5MSAwMDAwMCBuDQowMDAwMTg4NTM4IDAw
MDAwIG4NCjAwMDAxODg2OTEgMDAwMDAgbg0KMDAwMDE4ODgzNSAwMDAwMCBuDQowMDAwMTg4OTkx
IDAwMDAwIG4NCjAwMDAxODkxNDcgMDAwMDAgbg0KMDAwMDE4OTMwNiAwMDAwMCBuDQowMDAwMTg5
NDUwIDAwMDAwIG4NCjAwMDAxODk2MTMgMDAwMDAgbg0KMDAwMDE4OTc3NiAwMDAwMCBuDQowMDAw
MTg5OTM5IDAwMDAwIG4NCjAwMDAxOTAxMTMgMDAwMDAgbg0KMDAwMDE5MDI3NiAwMDAwMCBuDQow
MDAwMTkwNDIzIDAwMDAwIG4NCjAwMDAxOTA1ODYgMDAwMDAgbg0KMDAwMDE5MDc1NSAwMDAwMCBu
DQowMDAwMTkwOTI0IDAwMDAwIG4NCjAwMDAxOTExMDIgMDAwMDAgbg0KMDAwMDE5MTI2OCAwMDAw
MCBuDQowMDAwMTkxNDE1IDAwMDAwIG4NCjAwMDAxOTE1ODEgMDAwMDAgbg0KMDAwMDE5MTc1MyAw
MDAwMCBuDQowMDAwMTkxOTI4IDAwMDAwIG4NCjAwMDAxOTIxMTEgMDAwMDAgbg0KMDAwMDE5MjI4
MCAwMDAwMCBuDQowMDAwMTkyNDI3IDAwMDAwIG4NCjAwMDAxOTI1OTMgMDAwMDAgbg0KMDAwMDE5
Mjc2OCAwMDAwMCBuDQowMDAwMTkyOTQ2IDAwMDAwIG4NCjAwMDAxOTMxMzkgMDAwMDAgbg0KMDAw
MDE5MzI4OSAwMDAwMCBuDQowMDAwMTkzNDM2IDAwMDAwIG4NCjAwMDAxOTM1ODYgMDAwMDAgbg0K
MDAwMDE5Mzc1MiAwMDAwMCBuDQowMDAwMTkzOTMwIDAwMDAwIG4NCjAwMDAxOTQxMTEgMDAwMDAg
bg0KMDAwMDE5NDI5NSAwMDAwMCBuDQowMDAwMTk0NDQ1IDAwMDAwIG4NCjAwMDAxOTQ1OTIgMDAw
MDAgbg0KMDAwMDE5NDc0MiAwMDAwMCBuDQowMDAwMTk0OTA4IDAwMDAwIG4NCjAwMDAxOTUwOTIg
MDAwMDAgbg0KMDAwMDE5NTI3NiAwMDAwMCBuDQowMDAwMTk1NDY0IDAwMDAwIG4NCjAwMDAxOTU2
MTcgMDAwMDAgbg0KMDAwMDE5NTc2MSAwMDAwMCBuDQowMDAwMTk1OTExIDAwMDAwIG4NCjAwMDAx
OTYwNzcgMDAwMDAgbg0KMDAwMDE5NjI2MSAwMDAwMCBuDQowMDAwMTk2NDQ4IDAwMDAwIG4NCjAw
MDAxOTY2MzQgMDAwMDAgbg0KMDAwMDE5Njc5MCAwMDAwMCBuDQowMDAwMTk2OTMxIDAwMDAwIG4N
CjAwMDAxOTcwODQgMDAwMDAgbg0KMDAwMDE5NzI1MCAwMDAwMCBuDQowMDAwMTk3NDM3IDAwMDAw
IG4NCjAwMDAxOTc2MjQgMDAwMDAgbg0KMDAwMDE5NzgxMiAwMDAwMCBuDQowMDAwMTk3OTY4IDAw
MDAwIG4NCjAwMDAxOTgxMjQgMDAwMDAgbg0KMDAwMDE5ODI5MCAwMDAwMCBuDQowMDAwMTk4NDc2
IDAwMDAwIG4NCjAwMDAxOTg2NjAgMDAwMDAgbg0KMDAwMDE5ODg0NiAwMDAwMCBuDQowMDAwMTk5
MDA1IDAwMDAwIG4NCjAwMDAxOTkxNjEgMDAwMDAgbg0KMDAwMDE5OTMyNyAwMDAwMCBuDQowMDAw
MTk5NTEzIDAwMDAwIG4NCjAwMDAxOTk3MDAgMDAwMDAgbg0KMDAwMDE5OTg4NyAwMDAwMCBuDQow
MDAwMjAwMDUwIDAwMDAwIG4NCjAwMDAyMDAyMDkgMDAwMDAgbg0KMDAwMDIwMDM3NSAwMDAwMCBu
DQowMDAwMjAwNTU1IDAwMDAwIG4NCjAwMDAyMDA3NDEgMDAwMDAgbg0KMDAwMDIwMDkyNiAwMDAw
MCBuDQowMDAwMjAxMDkyIDAwMDAwIG4NCjAwMDAyMDEyNTggMDAwMDAgbg0KMDAwMDIwMTQyNCAw
MDAwMCBuDQowMDAwMjAxNjA3IDAwMDAwIG4NCjAwMDAyMDE3OTMgMDAwMDAgbg0KMDAwMDIwMTk4
MCAwMDAwMCBuDQowMDAwMjAyMTg1IDAwMDAwIG4NCjAwMDAyMDIzNTEgMDAwMDAgbg0KMDAwMDIw
MjUzNCAwMDAwMCBuDQowMDAwMjAyNzIzIDAwMDAwIG4NCjAwMDAyMDI5MDkgMDAwMDAgbg0KMDAw
MDIwMzExNyAwMDAwMCBuDQowMDAwMjAzMjgzIDAwMDAwIG4NCjAwMDAyMDM0NjYgMDAwMDAgbg0K
MDAwMDIwMzY0NiAwMDAwMCBuDQowMDAwMjAzODI5IDAwMDAwIG4NCjAwMDAyMDQwNDAgMDAwMDAg
bg0KMDAwMDIwNDIwNiAwMDAwMCBuDQowMDAwMjA0Mzk0IDAwMDAwIG4NCjAwMDAyMDQ1OTYgMDAw
MDAgbg0KMDAwMDIwNDgxMCAwMDAwMCBuDQowMDAwMjA0OTc2IDAwMDAwIG4NCjAwMDAyMDUxNTYg
MDAwMDAgbg0KMDAwMDIwNTM1NSAwMDAwMCBuDQowMDAwMjA1NTY5IDAwMDAwIG4NCjAwMDAyMDU3
MzUgMDAwMDAgbg0KMDAwMDIwNTkxNSAwMDAwMCBuDQowMDAwMjA2MTE2IDAwMDAwIG4NCjAwMDAy
MDYzMzMgMDAwMDAgbg0KMDAwMDIwNjQ5OSAwMDAwMCBuDQowMDAwMjA2Njg2IDAwMDAwIG4NCjAw
MDAyMDY4ODkgMDAwMDAgbg0KMDAwMDIwNzEwOSAwMDAwMCBuDQowMDAwMjA3MzEzIDAwMDAwIG4N
CjAwMDAyMDc0OTAgMDAwMDAgbg0KMDAwMDIwNzcxMyAwMDAwMCBuDQowMDAwMjA3OTE4IDAwMDAw
IG4NCjAwMDAyMDgxMDAgMDAwMDAgbg0KMDAwMDIwODMyMyAwMDAwMCBuDQowMDAwMjA4NTM1IDAw
MDAwIG4NCjAwMDAyMDg3MjggMDAwMDAgbg0KMDAwMDIwODk1NCAwMDAwMCBuDQowMDAwMjA5MDkx
IDAwMDAwIG4NCjAwMDAyMDkyNjAgMDAwMDAgbg0KMDAwMDIwOTQxOSAwMDAwMCBuDQowMDAwMjA5
NjMyIDAwMDAwIG4NCjAwMDAyMDk4NjEgMDAwMDAgbg0KMDAwMDIxMDAyNyAwMDAwMCBuDQowMDAw
MjEwMTk2IDAwMDAwIG4NCjAwMDAyMTAzNjUgMDAwMDAgbg0KMDAwMDIxMDU2NCAwMDAwMCBuDQow
MDAwMjEwNzk3IDAwMDAwIG4NCjAwMDAyMTA5NjYgMDAwMDAgbg0KMDAwMDIxMTEzNSAwMDAwMCBu
DQowMDAwMjExMzA0IDAwMDAwIG4NCjAwMDAyMTE0NzAgMDAwMDAgbg0KMDAwMDIxMTY1MCAwMDAw
MCBuDQowMDAwMjExODgzIDAwMDAwIG4NCjAwMDAyMTIwNTIgMDAwMDAgbg0KMDAwMDIxMjIyMSAw
MDAwMCBuDQowMDAwMjEyMzkwIDAwMDAwIG4NCjAwMDAyMTI1NTkgMDAwMDAgbg0KMDAwMDIxMjc1
MSAwMDAwMCBuDQowMDAwMjEyOTg3IDAwMDAwIG4NCjAwMDAyMTMxNTYgMDAwMDAgbg0KMDAwMDIx
MzMyNSAwMDAwMCBuDQowMDAwMjEzNDk0IDAwMDAwIG4NCjAwMDAyMTM2NjMgMDAwMDAgbg0KMDAw
MDIxMzg1OSAwMDAwMCBuDQowMDAwMjE0MDk4IDAwMDAwIG4NCjAwMDAyMTQyNjQgMDAwMDAgbg0K
MDAwMDIxNDQzMyAwMDAwMCBuDQowMDAwMjE0NjAyIDAwMDAwIG4NCjAwMDAyMTQ3NzEgMDAwMDAg
bg0KMDAwMDIxNDk0MCAwMDAwMCBuDQowMDAwMjE1MTEyIDAwMDAwIG4NCjAwMDAyMTUzNTQgMDAw
MDAgbg0KMDAwMDIxNTUyMCAwMDAwMCBuDQowMDAwMjE1Njg5IDAwMDAwIG4NCjAwMDAyMTU4NTgg
MDAwMDAgbg0KMDAwMDIxNjAyNyAwMDAwMCBuDQowMDAwMjE2MTk2IDAwMDAwIG4NCjAwMDAyMTYz
NjggMDAwMDAgbg0KMDAwMDIxNjYxMCAwMDAwMCBuDQowMDAwMjE2Nzc2IDAwMDAwIG4NCjAwMDAy
MTY5NDUgMDAwMDAgbg0KMDAwMDIxNzExNCAwMDAwMCBuDQowMDAwMjE3MjgzIDAwMDAwIG4NCjAw
MDAyMTc0NTIgMDAwMDAgbg0KMDAwMDIxNzYyNCAwMDAwMCBuDQowMDAwMjE3ODY5IDAwMDAwIG4N
CjAwMDAyMTgwMzUgMDAwMDAgbg0KMDAwMDIxODIwNCAwMDAwMCBuDQowMDAwMjE4MzczIDAwMDAw
IG4NCjAwMDAyMTg1NDIgMDAwMDAgbg0KMDAwMDIxODcxMSAwMDAwMCBuDQowMDAwMjE4ODgzIDAw
MDAwIG4NCjAwMDAyMTkxMzEgMDAwMDAgbg0KMDAwMDIxOTI5NyAwMDAwMCBuDQowMDAwMjE5NDY2
IDAwMDAwIG4NCjAwMDAyMTk2MzUgMDAwMDAgbg0KMDAwMDIxOTgwNCAwMDAwMCBuDQowMDAwMjE5
OTczIDAwMDAwIG4NCjAwMDAyMjAxNDUgMDAwMDAgbg0KMDAwMDIyMDM5NiAwMDAwMCBuDQowMDAw
MjIwNTYyIDAwMDAwIG4NCjAwMDAyMjA3MzEgMDAwMDAgbg0KMDAwMDIyMDkwMCAwMDAwMCBuDQow
MDAwMjIxMDY5IDAwMDAwIG4NCjAwMDAyMjEyMzggMDAwMDAgbg0KMDAwMDIyMTQxMCAwMDAwMCBu
DQowMDAwMjIxNjYxIDAwMDAwIG4NCjAwMDAyMjE4MjcgMDAwMDAgbg0KMDAwMDIyMTk5NiAwMDAw
MCBuDQowMDAwMjIyMTY1IDAwMDAwIG4NCjAwMDAyMjIzMzQgMDAwMDAgbg0KMDAwMDIyMjUwMyAw
MDAwMCBuDQowMDAwMjIyNjc1IDAwMDAwIG4NCjAwMDAyMjI5MjkgMDAwMDAgbg0KMDAwMDIyMzA5
NSAwMDAwMCBuDQowMDAwMjIzMjY0IDAwMDAwIG4NCjAwMDAyMjM0MzMgMDAwMDAgbg0KMDAwMDIy
MzYwMiAwMDAwMCBuDQowMDAwMjIzNzcxIDAwMDAwIG4NCjAwMDAyMjM5NDMgMDAwMDAgbg0KMDAw
MDIyNDIwMCAwMDAwMCBuDQowMDAwMjI0MzY5IDAwMDAwIG4NCjAwMDAyMjQ1MzggMDAwMDAgbg0K
MDAwMDIyNDcwNyAwMDAwMCBuDQowMDAwMjI0ODczIDAwMDAwIG4NCjAwMDAyMjUwNDUgMDAwMDAg
bg0KMDAwMDIyNTMwNSAwMDAwMCBuDQowMDAwMjI1NDcxIDAwMDAwIG4NCjAwMDAyMjU2NDAgMDAw
MDAgbg0KMDAwMDIyNTgwOSAwMDAwMCBuDQowMDAwMjI1OTc4IDAwMDAwIG4NCjAwMDAyMjYxNDEg
MDAwMDAgbg0KMDAwMDIyNjMxMyAwMDAwMCBuDQowMDAwMjI2NTczIDAwMDAwIG4NCjAwMDAyMjY3
MzkgMDAwMDAgbg0KMDAwMDIyNjkwOCAwMDAwMCBuDQowMDAwMjI3MDc3IDAwMDAwIG4NCjAwMDAy
MjcyNDYgMDAwMDAgbg0KMDAwMDIyNzQwOSAwMDAwMCBuDQowMDAwMjI3NTgxIDAwMDAwIG4NCjAw
MDAyMjc4NDQgMDAwMDAgbg0KMDAwMDIyODAxMCAwMDAwMCBuDQowMDAwMjI4MTc5IDAwMDAwIG4N
CjAwMDAyMjgzNDggMDAwMDAgbg0KMDAwMDIyODUxNyAwMDAwMCBuDQowMDAwMjI4Njc2IDAwMDAw
IG4NCjAwMDAyMjg4NDggMDAwMDAgbg0KMDAwMDIyOTExMSAwMDAwMCBuDQowMDAwMjI5Mjc3IDAw
MDAwIG4NCjAwMDAyMjk0NDYgMDAwMDAgbg0KMDAwMDIyOTYxNSAwMDAwMCBuDQowMDAwMjI5Nzg0
IDAwMDAwIG4NCjAwMDAyMjk5NTYgMDAwMDAgbg0KMDAwMDIzMDIyNCAwMDAwMCBuDQowMDAwMjMw
MzkwIDAwMDAwIG4NCjAwMDAyMzA1NTkgMDAwMDAgbg0KMDAwMDIzMDcyOCAwMDAwMCBuDQowMDAw
MjMwOTAwIDAwMDAwIG4NCjAwMDAyMzEwNzIgMDAwMDAgbg0KMDAwMDIzMTM0MSAwMDAwMCBuDQow
MDAwMjMxNTA3IDAwMDAwIG4NCjAwMDAyMzE2NzYgMDAwMDAgbg0KMDAwMDIzMTg0NSAwMDAwMCBu
DQowMDAwMjMyMDE3IDAwMDAwIG4NCjAwMDAyMzIxODkgMDAwMDAgbg0KMDAwMDIzMjQ2MSAwMDAw
MCBuDQowMDAwMjMyNjI3IDAwMDAwIG4NCjAwMDAyMzI3OTYgMDAwMDAgbg0KMDAwMDIzMjk2NSAw
MDAwMCBuDQowMDAwMjMzMTM3IDAwMDAwIG4NCjAwMDAyMzMzMDkgMDAwMDAgbg0KMDAwMDIzMzU4
NCAwMDAwMCBuDQowMDAwMjMzNzUwIDAwMDAwIG4NCjAwMDAyMzM5MTkgMDAwMDAgbg0KMDAwMDIz
NDA4OCAwMDAwMCBuDQowMDAwMjM0MjYwIDAwMDAwIG4NCjAwMDAyMzQ0MzIgMDAwMDAgbg0KMDAw
MDIzNDcxMCAwMDAwMCBuDQowMDAwMjM0ODc2IDAwMDAwIG4NCjAwMDAyMzUwNDUgMDAwMDAgbg0K
MDAwMDIzNTIxNCAwMDAwMCBuDQowMDAwMjM1Mzg5IDAwMDAwIG4NCjAwMDAyMzU1NjEgMDAwMDAg
bg0KMDAwMDIzNTgzMCAwMDAwMCBuDQowMDAwMjM1OTY0IDAwMDAwIG4NCjAwMDAyMzYxMzAgMDAw
MDAgbg0KMDAwMDIzNjI5OSAwMDAwMCBuDQowMDAwMjM2NDY4IDAwMDAwIG4NCjAwMDAyMzY2NDMg
MDAwMDAgbg0KMDAwMDIzNjgxNSAwMDAwMCBuDQowMDAwMjM2OTQ5IDAwMDAwIG4NCjAwMDAyMzcy
MDkgMDAwMDAgbg0KMDAwMDIzNzM0MyAwMDAwMCBuDQowMDAwMjM3NTA5IDAwMDAwIG4NCjAwMDAy
Mzc2NzggMDAwMDAgbg0KMDAwMDIzNzg0NyAwMDAwMCBuDQowMDAwMjM4MDIyIDAwMDAwIG4NCjAw
MDAyMzgxOTQgMDAwMDAgbg0KMDAwMDIzODMzMSAwMDAwMCBuDQowMDAwMjM4NTg4IDAwMDAwIG4N
CjAwMDAyMzg3MjIgMDAwMDAgbg0KMDAwMDIzODg4OCAwMDAwMCBuDQowMDAwMjM5MDU3IDAwMDAw
IG4NCjAwMDAyMzkyMjYgMDAwMDAgbg0KMDAwMDIzOTQwNCAwMDAwMCBuDQowMDAwMjM5NTc2IDAw
MDAwIG4NCjAwMDAyMzk3MTMgMDAwMDAgbg0KMDAwMDIzOTk2MiAwMDAwMCBuDQowMDAwMjQwMTI4
IDAwMDAwIG4NCjAwMDAyNDAyOTcgMDAwMDAgbg0KMDAwMDI0MDQ2NiAwMDAwMCBuDQowMDAwMjQw
NjQ0IDAwMDAwIG4NCjAwMDAyNDA4MTYgMDAwMDAgbg0KMDAwMDI0MDk1MyAwMDAwMCBuDQowMDAw
MjQxMTkxIDAwMDAwIG4NCjAwMDAyNDEzMzIgMDAwMDAgbg0KMDAwMDI0MTQ2NiAwMDAwMCBuDQow
MDAwMjQxNjMyIDAwMDAwIG4NCjAwMDAyNDE4MDEgMDAwMDAgbg0KMDAwMDI0MTk2NyAwMDAwMCBu
DQowMDAwMjQyMTQ1IDAwMDAwIG4NCjAwMDAyNDIzMTcgMDAwMDAgbg0KMDAwMDI0MjQ1OCAwMDAw
MCBuDQowMDAwMjQyNjk5IDAwMDAwIG4NCjAwMDAyNDI4NDMgMDAwMDAgbg0KMDAwMDI0Mjk3NyAw
MDAwMCBuDQowMDAwMjQzMTQzIDAwMDAwIG4NCjAwMDAyNDMzMTIgMDAwMDAgbg0KMDAwMDI0MzQ3
OCAwMDAwMCBuDQowMDAwMjQzNjU0IDAwMDAwIG4NCjAwMDAyNDM4MjYgMDAwMDAgbg0KMDAwMDI0
Mzk2NyAwMDAwMCBuDQowMDAwMjQ0MjEyIDAwMDAwIG4NCjAwMDAyNDQzNTkgMDAwMDAgbg0KMDAw
MDI0NDQ5MyAwMDAwMCBuDQowMDAwMjQ0NjU5IDAwMDAwIG4NCjAwMDAyNDQ4MjggMDAwMDAgbg0K
MDAwMDI0NDk5NCAwMDAwMCBuDQowMDAwMjQ1MTcyIDAwMDAwIG4NCjAwMDAyNDUzNDQgMDAwMDAg
bg0KMDAwMDI0NTQ4NSAwMDAwMCBuDQowMDAwMjQ1NzI4IDAwMDAwIG4NCjAwMDAyNDU4NzUgMDAw
MDAgbg0KMDAwMDI0NjAxMiAwMDAwMCBuDQowMDAwMjQ2MTc1IDAwMDAwIG4NCjAwMDAyNDYzNDQg
MDAwMDAgbg0KMDAwMDI0NjUyMiAwMDAwMCBuDQowMDAwMjQ2Njk0IDAwMDAwIG4NCjAwMDAyNDY4
MzggMDAwMDAgbg0KMDAwMDI0NzA4MCAwMDAwMCBuDQowMDAwMjQ3MjM2IDAwMDAwIG4NCjAwMDAy
NDc0MDIgMDAwMDAgbg0KMDAwMDI0NzU3MSAwMDAwMCBuDQowMDAwMjQ3NzUyIDAwMDAwIG4NCjAw
MDAyNDc5MjQgMDAwMDAgbg0KMDAwMDI0ODA2OCAwMDAwMCBuDQowMDAwMjQ4MzAyIDAwMDAwIG4N
CjAwMDAyNDg0NTggMDAwMDAgbg0KMDAwMDI0ODYyNCAwMDAwMCBuDQowMDAwMjQ4NzkzIDAwMDAw
IG4NCjAwMDAyNDg5NzQgMDAwMDAgbg0KMDAwMDI0OTE0NiAwMDAwMCBuDQowMDAwMjQ5MjkzIDAw
MDAwIG4NCjAwMDAyNDk1MjAgMDAwMDAgbg0KMDAwMDI0OTY3OSAwMDAwMCBuDQowMDAwMjQ5ODQ1
IDAwMDAwIG4NCjAwMDAyNTAwMTQgMDAwMDAgbg0KMDAwMDI1MDE5MiAwMDAwMCBuDQowMDAwMjUw
MzY0IDAwMDAwIG4NCjAwMDAyNTA1MTEgMDAwMDAgbg0KMDAwMDI1MDczOSAwMDAwMCBuDQowMDAw
MjUwODk4IDAwMDAwIG4NCjAwMDAyNTEwNjQgMDAwMDAgbg0KMDAwMDI1MTIzMyAwMDAwMCBuDQow
MDAwMjUxNDExIDAwMDAwIG4NCjAwMDAyNTE1ODMgMDAwMDAgbg0KMDAwMDI1MTczMCAwMDAwMCBu
DQowMDAwMjUxOTYzIDAwMDAwIG4NCjAwMDAyNTIxMjIgMDAwMDAgbg0KMDAwMDI1MjI4OCAwMDAw
MCBuDQowMDAwMjUyNDU3IDAwMDAwIG4NCjAwMDAyNTI2MzggMDAwMDAgbg0KMDAwMDI1MjgxMCAw
MDAwMCBuDQowMDAwMjUyOTU3IDAwMDAwIG4NCjAwMDAyNTMxODggMDAwMDAgbg0KMDAwMDI1MzM0
NyAwMDAwMCBuDQowMDAwMjUzNTEzIDAwMDAwIG4NCjAwMDAyNTM2ODIgMDAwMDAgbg0KMDAwMDI1
Mzg2MyAwMDAwMCBuDQowMDAwMjU0MDM1IDAwMDAwIG4NCjAwMDAyNTQxODIgMDAwMDAgbg0KMDAw
MDI1NDQxNCAwMDAwMCBuDQowMDAwMjU0NTczIDAwMDAwIG4NCjAwMDAyNTQ3MzkgMDAwMDAgbg0K
MDAwMDI1NDkwOCAwMDAwMCBuDQowMDAwMjU1MDgzIDAwMDAwIG4NCjAwMDAyNTUyNTUgMDAwMDAg
bg0KMDAwMDI1NTM5OSAwMDAwMCBuDQowMDAwMjU1NjI5IDAwMDAwIG4NCjAwMDAyNTU3ODggMDAw
MDAgbg0KMDAwMDI1NTk1NCAwMDAwMCBuDQowMDAwMjU2MTIzIDAwMDAwIG4NCjAwMDAyNTYyOTgg
MDAwMDAgbg0KMDAwMDI1NjQ3MCAwMDAwMCBuDQowMDAwMjU2NjE0IDAwMDAwIG4NCjAwMDAyNTY4
NDcgMDAwMDAgbg0KMDAwMDI1NzAwNiAwMDAwMCBuDQowMDAwMjU3MTcyIDAwMDAwIG4NCjAwMDAy
NTczNDEgMDAwMDAgbg0KMDAwMDI1NzUxMyAwMDAwMCBuDQowMDAwMjU3Njg1IDAwMDAwIG4NCjAw
MDAyNTc4MjYgMDAwMDAgbg0KMDAwMDI1ODA1OSAwMDAwMCBuDQowMDAwMjU4MjA2IDAwMDAwIG4N
CjAwMDAyNTgzNDcgMDAwMDAgbg0KMDAwMDI1ODUxMyAwMDAwMCBuDQowMDAwMjU4NjgyIDAwMDAw
IG4NCjAwMDAyNTg4NTcgMDAwMDAgbg0KMDAwMDI1OTAyOSAwMDAwMCBuDQowMDAwMjU5MTcwIDAw
MDAwIG4NCjAwMDAyNTk0MDAgMDAwMDAgbg0KMDAwMDI1OTU0NyAwMDAwMCBuDQowMDAwMjU5Njgx
IDAwMDAwIG4NCjAwMDAyNTk4NDcgMDAwMDAgbg0KMDAwMDI2MDAxNiAwMDAwMCBuDQowMDAwMjYw
MTk0IDAwMDAwIG4NCjAwMDAyNjAzNjYgMDAwMDAgbg0KMDAwMDI2MDUwNyAwMDAwMCBuDQowMDAw
MjYwNzQ2IDAwMDAwIG4NCjAwMDAyNjA4OTMgMDAwMDAgbg0KMDAwMDI2MTAyNyAwMDAwMCBuDQow
MDAwMjYxMTkzIDAwMDAwIG4NCjAwMDAyNjEzNjIgMDAwMDAgbg0KMDAwMDI2MTU0MCAwMDAwMCBu
DQowMDAwMjYxNzEyIDAwMDAwIG4NCjAwMDAyNjE4NDkgMDAwMDAgbg0KMDAwMDI2MjA5MSAwMDAw
MCBuDQowMDAwMjYyMjM1IDAwMDAwIG4NCjAwMDAyNjIzNjkgMDAwMDAgbg0KMDAwMDI2MjUzNSAw
MDAwMCBuDQowMDAwMjYyNzA0IDAwMDAwIG4NCjAwMDAyNjI4NzkgMDAwMDAgbg0KMDAwMDI2MzA1
MSAwMDAwMCBuDQowMDAwMjYzMTg4IDAwMDAwIG4NCjAwMDAyNjM0MjUgMDAwMDAgbg0KMDAwMDI2
MzU2NiAwMDAwMCBuDQowMDAwMjYzNzMyIDAwMDAwIG4NCjAwMDAyNjM5MDEgMDAwMDAgbg0KMDAw
MDI2NDA2NCAwMDAwMCBuDQowMDAwMjY0MjM5IDAwMDAwIG4NCjAwMDAyNjQ0MTEgMDAwMDAgbg0K
MDAwMDI2NDU0OCAwMDAwMCBuDQowMDAwMjY0Njk4IDAwMDAwIG4NCjAwMDAyNjQ5MTMgMDAwMDAg
bg0KMDAwMDI2NTA1MCAwMDAwMCBuDQowMDAwMjY1MjE2IDAwMDAwIG4NCjAwMDAyNjUzODUgMDAw
MDAgbg0KMDAwMDI2NTU1MSAwMDAwMCBuDQowMDAwMjY1NzI2IDAwMDAwIG4NCjAwMDAyNjU4OTgg
MDAwMDAgbg0KMDAwMDI2NjAzMiAwMDAwMCBuDQowMDAwMjY2MTc5IDAwMDAwIG4NCjAwMDAyNjYz
OTcgMDAwMDAgbg0KMDAwMDI2NjU2MyAwMDAwMCBuDQowMDAwMjY2NzMyIDAwMDAwIG4NCjAwMDAy
NjY4OTggMDAwMDAgbg0KMDAwMDI2NzA3MCAwMDAwMCBuDQowMDAwMjY3MjQyIDAwMDAwIG4NCjAw
MDAyNjczNzYgMDAwMDAgbg0KMDAwMDI2NzUyMyAwMDAwMCBuDQowMDAwMjY3NzQ0IDAwMDAwIG4N
CjAwMDAyNjc5MTAgMDAwMDAgbg0KMDAwMDI2ODA3OSAwMDAwMCBuDQowMDAwMjY4MjQ4IDAwMDAw
IG4NCjAwMDAyNjg0MjAgMDAwMDAgbg0KMDAwMDI2ODU5MiAwMDAwMCBuDQowMDAwMjY4NzI2IDAw
MDAwIG4NCjAwMDAyNjg4NzMgMDAwMDAgbg0KMDAwMDI2OTA5NyAwMDAwMCBuDQowMDAwMjY5MjMx
IDAwMDAwIG4NCjAwMDAyNjkzOTcgMDAwMDAgbg0KMDAwMDI2OTU2NiAwMDAwMCBuDQowMDAwMjY5
NzM1IDAwMDAwIG4NCjAwMDAyNjk5MDcgMDAwMDAgbg0KMDAwMDI3MDA3OSAwMDAwMCBuDQowMDAw
MjcwMjI5IDAwMDAwIG4NCjAwMDAyNzA0NjUgMDAwMDAgbg0KMDAwMDI3MDYzMSAwMDAwMCBuDQow
MDAwMjcwODAwIDAwMDAwIG4NCjAwMDAyNzA5NjkgMDAwMDAgbg0KMDAwMDI3MTEyOCAwMDAwMCBu
DQowMDAwMjcxMjk3IDAwMDAwIG4NCjAwMDAyNzE0NjkgMDAwMDAgbg0KMDAwMDI3MTYxNiAwMDAw
MCBuDQowMDAwMjcxODQ2IDAwMDAwIG4NCjAwMDAyNzIwMTIgMDAwMDAgbg0KMDAwMDI3MjE4MSAw
MDAwMCBuDQowMDAwMjcyMzUwIDAwMDAwIG4NCjAwMDAyNzI1MTMgMDAwMDAgbg0KMDAwMDI3MjY4
MiAwMDAwMCBuDQowMDAwMjcyODU0IDAwMDAwIG4NCjAwMDAyNzMwMDQgMDAwMDAgbg0KMDAwMDI3
MzIzNiAwMDAwMCBuDQowMDAwMjczNDAyIDAwMDAwIG4NCjAwMDAyNzM1NzEgMDAwMDAgbg0KMDAw
MDI3Mzc0MCAwMDAwMCBuDQowMDAwMjczOTA2IDAwMDAwIG4NCjAwMDAyNzQwNzggMDAwMDAgbg0K
MDAwMDI3NDIyOCAwMDAwMCBuDQowMDAwMjc0NDQ4IDAwMDAwIG4NCjAwMDAyNzQ1ODUgMDAwMDAg
bg0KMDAwMDI3NDcyMiAwMDAwMCBuDQowMDAwMjc0ODYzIDAwMDAwIG4NCjAwMDAyNzUwMjkgMDAw
MDAgbg0KMDAwMDI3NTE2NiAwMDAwMCBuDQowMDAwMjc1MzA3IDAwMDAwIG4NCjAwMDAyNzU0NTcg
MDAwMDAgbg0KMDAwMDI3NTY3NiAwMDAwMCBuDQowMDAwMjc1ODEzIDAwMDAwIG4NCjAwMDAyNzU5
ODIgMDAwMDAgbg0KMDAwMDI3NjEyMyAwMDAwMCBuDQowMDAwMjc2MjYwIDAwMDAwIG4NCjAwMDAy
NzY0MDEgMDAwMDAgbg0KMDAwMDI3NjYzNyAwMDAwMCBuDQowMDAwMjc2ODAzIDAwMDAwIG4NCjAw
MDAyNzY5NzIgMDAwMDAgbg0KMDAwMDI3NzE0MSAwMDAwMCBuDQowMDAwMjc3MzEwIDAwMDAwIG4N
CjAwMDAyNzc0NzkgMDAwMDAgbg0KMDAwMDI3NzY0NSAwMDAwMCBuDQowMDAwMjc3ODg0IDAwMDAw
IG4NCjAwMDAyNzgwNTMgMDAwMDAgbg0KMDAwMDI3ODIyMiAwMDAwMCBuDQowMDAwMjc4MzkxIDAw
MDAwIG4NCjAwMDAyNzg1NjAgMDAwMDAgbg0KMDAwMDI3ODczMiAwMDAwMCBuDQowMDAwMjc4OTY3
IDAwMDAwIG4NCjAwMDAyNzkxMzMgMDAwMDAgbg0KMDAwMDI3OTMwMiAwMDAwMCBuDQowMDAwMjc5
NDcxIDAwMDAwIG4NCjAwMDAyNzk2NDAgMDAwMDAgbg0KMDAwMDI3OTgwOSAwMDAwMCBuDQowMDAw
Mjc5OTgxIDAwMDAwIG4NCjAwMDAyODAyMTQgMDAwMDAgbg0KMDAwMDI4MDM4MyAwMDAwMCBuDQow
MDAwMjgwNTUyIDAwMDAwIG4NCjAwMDAyODA3MjEgMDAwMDAgbg0KMDAwMDI4MDg5MCAwMDAwMCBu
DQowMDAwMjgxMDYyIDAwMDAwIG4NCjAwMDAyODEyOTcgMDAwMDAgbg0KMDAwMDI4MTQ2MyAwMDAw
MCBuDQowMDAwMjgxNjMyIDAwMDAwIG4NCjAwMDAyODE4MDEgMDAwMDAgbg0KMDAwMDI4MTk3MCAw
MDAwMCBuDQowMDAwMjgyMTM5IDAwMDAwIG4NCjAwMDAyODIzMTEgMDAwMDAgbg0KMDAwMDI4MjU0
NSAwMDAwMCBuDQowMDAwMjgyNzExIDAwMDAwIG4NCjAwMDAyODI4ODAgMDAwMDAgbg0KMDAwMDI4
MzA0OSAwMDAwMCBuDQowMDAwMjgzMjE4IDAwMDAwIG4NCjAwMDAyODMzODcgMDAwMDAgbg0KMDAw
MDI4MzU1OSAwMDAwMCBuDQowMDAwMjgzNzkwIDAwMDAwIG4NCjAwMDAyODM5NTYgMDAwMDAgbg0K
MDAwMDI4NDEyNSAwMDAwMCBuDQowMDAwMjg0Mjk0IDAwMDAwIG4NCjAwMDAyODQ0NjMgMDAwMDAg
bg0KMDAwMDI4NDYzMiAwMDAwMCBuDQowMDAwMjg0ODA1IDAwMDAwIG4NCjAwMDAyODUwNDAgMDAw
MDAgbg0KMDAwMDI4NTIwNyAwMDAwMCBuDQowMDAwMjg1Mzc3IDAwMDAwIG4NCjAwMDAyODU1NDcg
MDAwMDAgbg0KMDAwMDI4NTcxNyAwMDAwMCBuDQowMDAwMjg1ODg3IDAwMDAwIG4NCjAwMDAyODYw
NjAgMDAwMDAgbg0KMDAwMDI4NjI5OCAwMDAwMCBuDQowMDAwMjg2NDY1IDAwMDAwIG4NCjAwMDAy
ODY2MzUgMDAwMDAgbg0KMDAwMDI4NjgwNSAwMDAwMCBuDQowMDAwMjg2OTc1IDAwMDAwIG4NCjAw
MDAyODcxNDUgMDAwMDAgbg0KMDAwMDI4NzMxOCAwMDAwMCBuDQowMDAwMjg3NTYxIDAwMDAwIG4N
CjAwMDAyODc3MzEgMDAwMDAgbg0KMDAwMDI4NzkwMSAwMDAwMCBuDQowMDAwMjg4MDY4IDAwMDAw
IG4NCjAwMDAyODgyMzggMDAwMDAgbg0KMDAwMDI4ODQ4MSAwMDAwMCBuDQowMDAwMjg4NjUxIDAw
MDAwIG4NCjAwMDAyODg4MjEgMDAwMDAgbg0KMDAwMDI4ODk5MSAwMDAwMCBuDQowMDAwMjg5MTYx
IDAwMDAwIG4NCjAwMDAyODkzMzQgMDAwMDAgbg0KMDAwMDI4OTU3NCAwMDAwMCBuDQowMDAwMjg5
NzQxIDAwMDAwIG4NCjAwMDAyODk5MDggMDAwMDAgbg0KMDAwMDI5MDA3OCAwMDAwMCBuDQowMDAw
MjkwMjQ4IDAwMDAwIG4NCjAwMDAyOTA0MTggMDAwMDAgbg0KMDAwMDI5MDU5MSAwMDAwMCBuDQow
MDAwMjkwODMxIDAwMDAwIG4NCjAwMDAyOTA5OTggMDAwMDAgbg0KMDAwMDI5MTE2NSAwMDAwMCBu
DQowMDAwMjkxMzM1IDAwMDAwIG4NCjAwMDAyOTE1MDUgMDAwMDAgbg0KMDAwMDI5MTY3NSAwMDAw
MCBuDQowMDAwMjkxODQ4IDAwMDAwIG4NCjAwMDAyOTIwODUgMDAwMDAgbg0KMDAwMDI5MjI1MiAw
MDAwMCBuDQowMDAwMjkyNDE5IDAwMDAwIG4NCjAwMDAyOTI1ODkgMDAwMDAgbg0KMDAwMDI5Mjc1
NiAwMDAwMCBuDQowMDAwMjkyOTI2IDAwMDAwIG4NCjAwMDAyOTMwOTkgMDAwMDAgbg0KMDAwMDI5
MzMzMyAwMDAwMCBuDQowMDAwMjkzNTAwIDAwMDAwIG4NCjAwMDAyOTM2NjcgMDAwMDAgbg0KMDAw
MDI5MzgzNyAwMDAwMCBuDQowMDAwMjk0MDA0IDAwMDAwIG4NCjAwMDAyOTQxNzcgMDAwMDAgbg0K
MDAwMDI5NDM1MCAwMDAwMCBuDQowMDAwMjk0NTgwIDAwMDAwIG4NCjAwMDAyOTQ3NDcgMDAwMDAg
bg0KMDAwMDI5NDkxNCAwMDAwMCBuDQowMDAwMjk1MDg0IDAwMDAwIG4NCjAwMDAyOTUyNzkgMDAw
MDAgbg0KMDAwMDI5NTQ1MiAwMDAwMCBuDQowMDAwMjk1NjgyIDAwMDAwIG4NCjAwMDAyOTU4NDkg
MDAwMDAgbg0KMDAwMDI5NjA0NiAwMDAwMCBuDQowMDAwMjk2MjQ2IDAwMDAwIG4NCjAwMDAyOTY0
MTkgMDAwMDAgbg0KMDAwMDI5NjY0NiAwMDAwMCBuDQowMDAwMjk2ODEzIDAwMDAwIG4NCjAwMDAy
OTcwMTMgMDAwMDAgbg0KMDAwMDI5NzIxMyAwMDAwMCBuDQowMDAwMjk3Mzg2IDAwMDAwIG4NCjAw
MDAyOTc2MTAgMDAwMDAgbg0KMDAwMDI5Nzc3NyAwMDAwMCBuDQowMDAwMjk3OTczIDAwMDAwIG4N
CjAwMDAyOTgxNzMgMDAwMDAgbg0KMDAwMDI5ODM0NiAwMDAwMCBuDQowMDAwMjk4NTY3IDAwMDAw
IG4NCjAwMDAyOTg3MzQgMDAwMDAgbg0KMDAwMDI5ODkzMSAwMDAwMCBuDQowMDAwMjk5MTMwIDAw
MDAwIG4NCjAwMDAyOTkzMDMgMDAwMDAgbg0KMDAwMDI5OTUyNCAwMDAwMCBuDQowMDAwMjk5NzIz
IDAwMDAwIG4NCjAwMDAyOTk5MjEgMDAwMDAgbg0KMDAwMDMwMDA4OCAwMDAwMCBuDQowMDAwMzAw
MzA2IDAwMDAwIG4NCjAwMDAzMDA1MDMgMDAwMDAgbg0KMDAwMDMwMDcwMCAwMDAwMCBuDQowMDAw
MzAwODczIDAwMDAwIG4NCjAwMDAzMDEwODggMDAwMDAgbg0KMDAwMDMwMTI3NyAwMDAwMCBuDQow
MDAwMzAxNDcyIDAwMDAwIG4NCjAwMDAzMDE2NTggMDAwMDAgbg0KMDAwMDMwMTg3MCAwMDAwMCBu
DQowMDAwMzAyMDUxIDAwMDAwIG4NCjAwMDAzMDIyMjQgMDAwMDAgbg0KMDAwMDMwMjQzNiAwMDAw
MCBuDQowMDAwMzAyNjAzIDAwMDAwIG4NCjAwMDAzMDI3ODQgMDAwMDAgbg0KMDAwMDMwMjk2MiAw
MDAwMCBuDQowMDAwMzAzMTM1IDAwMDAwIG4NCjAwMDAzMDMzNDQgMDAwMDAgbg0KMDAwMDMwMzUx
MSAwMDAwMCBuDQowMDAwMzAzNjg2IDAwMDAwIG4NCjAwMDAzMDM4NjMgMDAwMDAgbg0KMDAwMDMw
NDAzNiAwMDAwMCBuDQowMDAwMzA0MjQyIDAwMDAwIG4NCjAwMDAzMDQ0MjUgMDAwMDAgbg0KMDAw
MDMwNDYxMSAwMDAwMCBuDQowMDAwMzA0NzcxIDAwMDAwIG4NCjAwMDAzMDQ5MjggMDAwMDAgbg0K
MDAwMDMwNTA5NSAwMDAwMCBuDQowMDAwMzA1Mjc0IDAwMDAwIG4NCjAwMDAzMDU0NTMgMDAwMDAg
bg0KMDAwMDMwNTYyNiAwMDAwMCBuDQowMDAwMzA1NzgzIDAwMDAwIG4NCjAwMDAzMDU5NDAgMDAw
MDAgbg0KMDAwMDMwNjEwNyAwMDAwMCBuDQowMDAwMzA2MjgzIDAwMDAwIG4NCjAwMDAzMDY0NjIg
MDAwMDAgbg0KMDAwMDMwNjYzNSAwMDAwMCBuDQowMDAwMzA2Nzg5IDAwMDAwIG4NCjAwMDAzMDY5
NDYgMDAwMDAgbg0KMDAwMDMwNzExMyAwMDAwMCBuDQowMDAwMzA3Mjg5IDAwMDAwIG4NCjAwMDAz
MDc0NjkgMDAwMDAgbg0KMDAwMDMwNzY0MiAwMDAwMCBuDQowMDAwMzA3Nzk2IDAwMDAwIG4NCjAw
MDAzMDc5NTAgMDAwMDAgbg0KMDAwMDMwODExNyAwMDAwMCBuDQowMDAwMzA4Mjk3IDAwMDAwIG4N
CjAwMDAzMDg0NzMgMDAwMDAgbg0KMDAwMDMwODY0NiAwMDAwMCBuDQowMDAwMzA4ODA2IDAwMDAw
IG4NCjAwMDAzMDg5NzAgMDAwMDAgbg0KMDAwMDMwOTEzNyAwMDAwMCBuDQowMDAwMzA5MzEzIDAw
MDAwIG4NCjAwMDAzMDk0ODkgMDAwMDAgbg0KMDAwMDMwOTY2MiAwMDAwMCBuDQowMDAwMzA5ODIy
IDAwMDAwIG4NCjAwMDAzMDk5ODIgMDAwMDAgbg0KMDAwMDMxMDE0OSAwMDAwMCBuDQowMDAwMzEw
MzIyIDAwMDAwIG4NCjAwMDAzMTA0OTggMDAwMDAgbg0KMDAwMDMxMDY3MSAwMDAwMCBuDQowMDAw
MzEwODMxIDAwMDAwIG4NCjAwMDAzMTA5OTEgMDAwMDAgbg0KMDAwMDMxMTE1OCAwMDAwMCBuDQow
MDAwMzExMzM0IDAwMDAwIG4NCjAwMDAzMTE1MTAgMDAwMDAgbg0KMDAwMDMxMTY4MyAwMDAwMCBu
DQowMDAwMzExODQwIDAwMDAwIG4NCjAwMDAzMTIwMDAgMDAwMDAgbg0KMDAwMDMxMjE2NyAwMDAw
MCBuDQowMDAwMzEyMzQwIDAwMDAwIG4NCjAwMDAzMTI1MjAgMDAwMDAgbg0KMDAwMDMxMjY5MCAw
MDAwMCBuDQowMDAwMzEyODQ3IDAwMDAwIG4NCjAwMDAzMTMwMDQgMDAwMDAgbg0KMDAwMDMxMzE3
MSAwMDAwMCBuDQowMDAwMzEzMzQ3IDAwMDAwIG4NCjAwMDAzMTM1MjYgMDAwMDAgbg0KMDAwMDMx
MzY5NiAwMDAwMCBuDQowMDAwMzEzODUzIDAwMDAwIG4NCjAwMDAzMTQwMTAgMDAwMDAgbg0KMDAw
MDMxNDE3NyAwMDAwMCBuDQowMDAwMzE0MzU2IDAwMDAwIG4NCjAwMDAzMTQ1MzIgMDAwMDAgbg0K
MDAwMDMxNDcwMiAwMDAwMCBuDQowMDAwMzE0ODU2IDAwMDAwIG4NCjAwMDAzMTUwMTMgMDAwMDAg
bg0KMDAwMDMxNTE4MCAwMDAwMCBuDQowMDAwMzE1MzUzIDAwMDAwIG4NCjAwMDAzMTU1MjYgMDAw
MDAgbg0KMDAwMDMxNTY5MyAwMDAwMCBuDQowMDAwMzE1ODQ3IDAwMDAwIG4NCjAwMDAzMTYwMDEg
MDAwMDAgbg0KMDAwMDMxNjE2NSAwMDAwMCBuDQowMDAwMzE2MzMyIDAwMDAwIG4NCjAwMDAzMTY0
OTkgMDAwMDAgbg0KMDAwMDMxNjY2NiAwMDAwMCBuDQowMDAwMzE2ODE3IDAwMDAwIG4NCjAwMDAz
MTY5NzEgMDAwMDAgbg0KMDAwMDMxNzEzNSAwMDAwMCBuDQowMDAwMzE3Mjk5IDAwMDAwIG4NCjAw
MDAzMTc0NTAgMDAwMDAgbg0KMDAwMDMxNzYwMSAwMDAwMCBuDQowMDAwMzE3NzU4IDAwMDAwIG4N
CjAwMDAzMTc5MTUgMDAwMDAgbg0KMDAwMDMxODA2NiAwMDAwMCBuDQowMDAwMzE4MjE3IDAwMDAw
IG4NCjAwMDAzMTgzNTUgMDAwMDAgbg0KMDAwMDMxODQ5MyAwMDAwMCBuDQowMDAwMzE4NjQxIDAw
MDAwIG4NCjAwMDAzMTg3OTIgMDAwMDAgbg0KMDAwMDMxODk0MCAwMDAwMCBuDQowMDAwMzE5MDg4
IDAwMDAwIG4NCjAwMDAzMTkyMzYgMDAwMDAgbg0KMDAwMDMxOTM4NCAwMDAwMCBuDQowMDAwMzE5
NTI5IDAwMDAwIG4NCjAwMDAzMTk2NzcgMDAwMDAgbg0KMDAwMDMxOTgyMiAwMDAwMCBuDQowMDAw
MzE5OTY3IDAwMDAwIG4NCjAwMDAzMjAxMDkgMDAwMDAgbg0KMDAwMDMyMDI1NCAwMDAwMCBuDQow
MDAwMzIwMzk2IDAwMDAwIG4NCjAwMDAzMjA1MzggMDAwMDAgbg0KMDAwMDMyMDY4MCAwMDAwMCBu
DQowMDAwMzIwODIyIDAwMDAwIG4NCjAwMDAzMjA5NjAgMDAwMDAgbg0KMDAwMDMyMTEwMiAwMDAw
MCBuDQowMDAwMzIxMjQwIDAwMDAwIG4NCjAwMDAzMjEzNzggMDAwMDAgbg0KMDAwMDMyMTUxNiAw
MDAwMCBuDQowMDAwMzIxNjU0IDAwMDAwIG4NCjAwMDAzMjE3OTkgMDAwMDAgbg0KMDAwMDMyMTk0
MSAwMDAwMCBuDQowMDAwMzIyMDc5IDAwMDAwIG4NCjAwMDAzMjIyMTcgMDAwMDAgbg0KMDAwMDMy
MjM1MiAwMDAwMCBuDQowMDAwMzIzODEzIDAwMDAwIG4NCjAwMDAzMjU1ODUgMDAwMDAgbg0KMDAw
MDMyNzI5OSAwMDAwMCBuDQowMDAwMzI4NjYzIDAwMDAwIG4NCjAwMDAzMzAyNTIgMDAwMDAgbg0K
MDAwMDMzMzMwMiAwMDAwMCBuDQowMDAwMzM0NDQxIDAwMDAwIG4NCjAwMDAzMzY1ODMgMDAwMDAg
bg0KdHJhaWxlcg0KPDwvU2l6ZSAxMjI4L1ByZXYgMzQwMzc4L1Jvb3QgNyAwIFIvSW5mbyA1IDAg
Ui9JRFs8MTRkZmZhOTFjZWEwMTIzYTc1MmI0MzVlMzMyZWQzZTA+PDllNWNhYzAwMjQ4MGMzNDNi
OWNhMjhjNGVkMWRhNmQ4Pl0+Pg0Kc3RhcnR4cmVmDQowDQolJUVPRg0KICAgICAgICAgICANCjgg
MCBvYmo8PC9MZW5ndGggMTYxMC9GaWx0ZXIvRmxhdGVEZWNvZGUvTCAyNTA1L1MgNDI+PnN0cmVh
bQ0KeNrMVe9rHOUWPmdmdmZ2s7uZTbcxyabNmzTqKFXTkiZrbevbbWOjN9e7Ra+s4IfBVhqtxo0o
0eKPU13tktK6VZEg/TAWBZF8WMQLAb/MxYK5WGRRkF4IMvSDBC0SpEgRP3jemSSN/4ELQ/bJec7z
nHPe884CGF8CeFcBwPjiLPz1Y0SP3VDfnQ3//jJ++DMA7diXXMn6fV4aPAmQgjy4r13f/N8/+v93
4B9vnW37tWvwHvioKfwn9vft24Ur+vASpIc20f7gyU89vHo809M4LbqCrqBMR7CEcwnb9POim3bQ
h3AphunAlSP0FFzSasa46WekK/9JT2FJq+nllLNZ9tAeegM9/FxftIc2BVtohF5CU1vRy9ZQ1nOl
hGfgR7xsjpthu+yHvfAxLOGyISw/TS4V6QTauKTXU+Ws2EolmIFlXDCalqPIu2EGpyKy44huqND7
aGstq2JLFX0FTqCmt/Rl29ni9cl99DNquGTJlOj1XXqOLuBFrW5eT4lC6NLTDD9j2EyJjDcMh+H/
eFCfSDjpVrvcAkdohqtqJVqWzMntskhn8BGc16t2K+8XaBQauBNbejUJaeoP9sIUChW1/EwwCKNw
Epa0Yd23q1mxTR6GacxrDkOplCXNaB24kHBMmeUyRuEUHsSLxmRKZEUvG12AK7igV1MiHfbKXQpq
dfaVWSrwNI7D9+y7rIz62WgKruGSIczQ4eguqsGy1qvIXEawG2a5BZayqkr5PpqKlH0zVFWNwjRH
L+p1M8x4W4INME3dPGdFvqhXFbl3naxgqNqfjou0WpmgwEc2HRkts1SgWlDw2lpukX1/j8iOio7y
KUVGlqPOV7Xwi6qKYbhqpMmoSFLKU9jDy7CglBWcUbNKOJaTl73RYNdhgQ7DMaxhQy+azYxXoJ1w
FBYZCrOapp5gJxxjXxUN02F3cA8dZ995pRwX+XzUQt2qZoKttFcVqRmGbTs5Ehw9iVmt1yA+BdEP
Y3AGb+c5122Z8wfhX5x7BVuGSEKHdzPt5haWNcdoJr1NUg32eV7RirGYpHbZw7413KkdNVqWrzZ2
At7HIZ5Vy5ab4BY5QSfhd85tJKkj7IcS1NjIMxZTTYdu5ls2h49x9JOk6PC3yxJ8gGVN+Yq8fweT
38EHNV6GZGOzuJP+DW/jCW3e8NtanfLWwOPhZPFaYi495PDGHqCP8Sx3VLSrDg3SEToVNVhMht1S
RRWsm5O2dMIY5nVpCCZHcBZ9LqMYwzH4jhuMpcIBHmstlrKrOTnCRa4q236BR3dg1aicCeIyFHTN
67FUCWb5hq4qCznGY11TFgN8f1eVrVZO3r2uXM76sdQsFzkfFzlAY3y6ca6fk3tWya5Rbpcx+Ywi
6yJu8D6ahUW9vhF+o7+8BsdBwcdi5UE+/WM4h2u5oKLf63t42yPlEpzFPM6bc5bDbwbut4ZCc/VK
hre9O5Dcr4LVDKjTP0DvMnnBlFbUwv3se0U3+PUlY6Np3udryrcDBnj5v4p2o5gcyvHyP06vRA3O
2X5W7KB90XCGjbIZdlFf1G+PMkpX231lNBtVVeQ76Cl4JoJirchGBCc3wvMmqVfBGvm8WTGbqkgZ
Q91vK6fDuEFlxFI3QQzzq9CLj3sNBt2wfgqW7I7aP8Ud8QlaThfFZC2CsiuIoc25fpuvLqx6uX3D
Y/fbGuzL8BiP3b2xkzX84MYSHqUNS7gjWN+6dGPj1smN652/IXUa39HyhrQpxz+oY3QJU5pYhcEk
1dFR0Yyjogehjp160XDtcgxP43mOumu5X3OuklLR4Ci8GUm5djPn7YASvclSNaOSlo7vBg9x7uta
PjGU8nLeXVTin6cJbXvisl3Oe7fJMfoCH9AahttGec8Nxug/OMK5QZvo8AaCR1n5Fk0aldSK42+T
h7iFivawEVhhu9cvx+kcduJVnaVywSBLvQi/cVXVpMh5W2EP5w5qRaNihY7sl4d4gTvxur7CZG8b
jdGr8Ici2yGTg3uZ3KmNG9JqKuVDcA6dWLlDbKODECtX7KbjK+XXo/Zdq9wOgvbDC/CTIlt8ZXtg
GJ5juKg3LJGVheBueBZ+wKb+ohlkqAAjMAmX0delSRkoBAq28L3tc0/73+LEG8nTi/YFsYIe/I0/
CIneE/xX46f4pwADANIeVuQNCmVuZHN0cmVhbQ1lbmRvYmoNNyAwIG9iajw8L1BhZ2VzIDMgMCBS
L1R5cGUvQ2F0YWxvZy9QYWdlTGFiZWxzIDEgMCBSL01ldGFkYXRhIDQgMCBSPj4NZW5kb2JqDTkg
MCBvYmo8PC9Db250ZW50c1sxOSAwIFIgMjEgMCBSIDIyIDAgUiAyMyAwIFIgMjQgMCBSIDI1IDAg
UiAyNiAwIFIgMjcgMCBSXS9UeXBlL1BhZ2UvUGFyZW50IDMgMCBSL1JvdGF0ZSAwL01lZGlhQm94
WzAgMCA2MTIgNzkyXS9Dcm9wQm94WzAgMCA2MTIgNzkyXS9SZXNvdXJjZXMgMTAgMCBSPj4NZW5k
b2JqDTEwIDAgb2JqPDwvQ29sb3JTcGFjZTw8L0NzNiAxNSAwIFIvQ3M5IDE2IDAgUi9DczEwIDE3
IDAgUi9DczEyIDE4IDAgUj4+L0ZvbnQ8PC9UVDIgMTEgMCBSL1RUNCAxMiAwIFIvVFQ1IDEzIDAg
Ui9UVDcgMTQgMCBSL1RUOSAyMCAwIFI+Pi9YT2JqZWN0PDwvSW0xIDQyIDAgUi9JbTIgNDMgMCBS
L0ltMyA0NCAwIFIvSW00IDQ1IDAgUi9JbTUgNDYgMCBSL0ltNiA0NyAwIFIvSW03IDQ4IDAgUi9J
bTggNDkgMCBSL0ltOSA1MCAwIFIvSW0xMCA1MSAwIFIvSW0xMSA1MiAwIFIvSW0xMiA1MyAwIFIv
SW0xMyA1NCAwIFIvSW0xNCA1NSAwIFIvSW0xNSA1NiAwIFIvSW0xNiA1NyAwIFIvSW0xNyA1OCAw
IFIvSW0xOCA1OSAwIFIvSW0xOSA2MCAwIFIvSW0yMCA2MSAwIFIvSW0yMSA2MiAwIFIvSW0yMiA2
MyAwIFIvSW0yMyA2NCAwIFIvSW0yNCA2NSAwIFIvSW0yNSA2NiAwIFIvSW0yNiA2NyAwIFIvSW0y
NyA2OCAwIFIvSW0yOCA2OSAwIFIvSW0yOSA3MCAwIFIvSW0zMCA3MSAwIFIvSW0zMSA3MiAwIFIv
SW0zMiA3MyAwIFIvSW0zMyA3NCAwIFIvSW0zNCA3NSAwIFIvSW0zNSA3NiAwIFIvSW0zNiA3NyAw
IFIvSW0zNyA3OCAwIFIvSW0zOCA3OSAwIFIvSW0zOSA4MCAwIFIvSW00MCA4MSAwIFIvSW00MSA4
MiAwIFIvSW00MiA4MyAwIFIvSW00MyA4NCAwIFIvSW00NCA4NSAwIFIvSW00NSA4NiAwIFIvSW00
NiA4NyAwIFIvSW00NyA4OCAwIFIvSW00OCA4OSAwIFIvSW00OSA5MCAwIFIvSW01MCA5MSAwIFIv
SW01MSA5MiAwIFIvSW01MiA5MyAwIFIvSW01MyA5NCAwIFIvSW01NCA5NSAwIFIvSW01NSA5NiAw
IFIvSW01NiA5NyAwIFIvSW01NyA5OCAwIFIvSW01OCA5OSAwIFIvSW01OSAxMDAgMCBSL0ltNjAg
MTAxIDAgUi9JbTYxIDEwMiAwIFIvSW02MiAxMDMgMCBSL0ltNjMgMTA0IDAgUi9JbTY0IDEwNSAw
IFIvSW02NSAxMDYgMCBSL0ltNjYgMTA3IDAgUi9JbTY3IDEwOCAwIFIvSW02OCAxMDkgMCBSL0lt
NjkgMTEwIDAgUi9JbTcwIDExMSAwIFIvSW03MSAxMTIgMCBSL0ltNzIgMTEzIDAgUi9JbTczIDEx
NCAwIFIvSW03NCAxMTUgMCBSL0ltNzUgMTE2IDAgUi9JbTc2IDExNyAwIFIvSW03NyAxMTggMCBS
L0ltNzggMTE5IDAgUi9JbTc5IDEyMCAwIFIvSW04MCAxMjEgMCBSL0ltODEgMTIyIDAgUi9JbTgy
IDEyMyAwIFIvSW04MyAxMjQgMCBSL0ltODQgMTI1IDAgUi9JbTg1IDEyNiAwIFIvSW04NiAxMjcg
MCBSL0ltODcgMTI4IDAgUi9JbTg4IDEyOSAwIFIvSW04OSAxMzAgMCBSL0ltOTAgMTMxIDAgUi9J
bTkxIDEzMiAwIFIvSW05MiAxMzMgMCBSL0ltOTMgMTM0IDAgUi9JbTk0IDEzNSAwIFIvSW05NSAx
MzYgMCBSL0ltOTYgMTM3IDAgUi9JbTk3IDEzOCAwIFIvSW05OCAxMzkgMCBSL0ltOTkgMTQwIDAg
Ui9JbTEwMCAxNDEgMCBSL0ltMTAxIDE0MiAwIFIvSW0xMDIgMTQzIDAgUi9JbTEwMyAxNDQgMCBS
L0ltMTA0IDE0NSAwIFIvSW0xMDUgMTQ2IDAgUi9JbTEwNiAxNDcgMCBSL0ltMTA3IDE0OCAwIFIv
SW0xMDggMTQ5IDAgUi9JbTEwOSAxNTAgMCBSL0ltMTEwIDE1MSAwIFIvSW0xMTEgMTUyIDAgUi9J
bTExMiAxNTMgMCBSL0ltMTEzIDE1NCAwIFIvSW0xMTQgMTU1IDAgUi9JbTExNSAxNTYgMCBSL0lt
MTE2IDE1NyAwIFIvSW0xMTcgMTU4IDAgUi9JbTExOCAxNTkgMCBSL0ltMTE5IDE2MCAwIFIvSW0x
MjAgMTYxIDAgUi9JbTEyMSAxNjIgMCBSL0ltMTIyIDE2MyAwIFIvSW0xMjMgMTY0IDAgUi9JbTEy
NCAxNjUgMCBSL0ltMTI1IDE2NiAwIFIvSW0xMjYgMTY3IDAgUi9JbTEyNyAxNjggMCBSL0ltMTI4
IDE2OSAwIFIvSW0xMjkgMTcwIDAgUi9JbTEzMCAxNzEgMCBSL0ltMTMxIDE3MiAwIFIvSW0xMzIg
MTczIDAgUi9JbTEzMyAxNzQgMCBSL0ltMTM0IDE3NSAwIFIvSW0xMzUgMTc2IDAgUi9JbTEzNiAx
NzcgMCBSL0ltMTM3IDE3OCAwIFIvSW0xMzggMTc5IDAgUi9JbTEzOSAxODAgMCBSL0ltMTQwIDE4
MSAwIFIvSW0xNDEgMTgyIDAgUi9JbTE0MiAxODMgMCBSL0ltMTQzIDE4NCAwIFIvSW0xNDQgMTg1
IDAgUi9JbTE0NSAxODYgMCBSL0ltMTQ2IDE4NyAwIFIvSW0xNDcgMTg4IDAgUi9JbTE0OCAxODkg
MCBSL0ltMTQ5IDE5MCAwIFIvSW0xNTAgMTkxIDAgUi9JbTE1MSAxOTIgMCBSL0ltMTUyIDE5MyAw
IFIvSW0xNTMgMTk0IDAgUi9JbTE1NCAxOTUgMCBSL0ltMTU1IDE5NiAwIFIvSW0xNTYgMTk3IDAg
Ui9JbTE1NyAxOTggMCBSL0ltMTU4IDE5OSAwIFIvSW0xNTkgMjAwIDAgUi9JbTE2MCAyMDEgMCBS
L0ltMTYxIDIwMiAwIFIvSW0xNjIgMjAzIDAgUi9JbTE2MyAyMDQgMCBSL0ltMTY0IDIwNSAwIFIv
SW0xNjUgMjA2IDAgUi9JbTE2NiAyMDcgMCBSL0ltMTY3IDIwOCAwIFIvSW0xNjggMjA5IDAgUi9J
bTE2OSAyMTAgMCBSL0ltMTcwIDIxMSAwIFIvSW0xNzEgMjEyIDAgUi9JbTE3MiAyMTMgMCBSL0lt
MTczIDIxNCAwIFIvSW0xNzQgMjE1IDAgUi9JbTE3NSAyMTYgMCBSL0ltMTc2IDIxNyAwIFIvSW0x
NzcgMjE4IDAgUi9JbTE3OCAyMTkgMCBSL0ltMTc5IDIyMCAwIFIvSW0xODAgMjIxIDAgUi9JbTE4
MSAyMjIgMCBSL0ltMTgyIDIyMyAwIFIvSW0xODMgMjI0IDAgUi9JbTE4NCAyMjUgMCBSL0ltMTg1
IDIyNiAwIFIvSW0xODYgMjI3IDAgUi9JbTE4NyAyMjggMCBSL0ltMTg4IDIyOSAwIFIvSW0xODkg
MjMwIDAgUi9JbTE5MCAyMzEgMCBSL0ltMTkxIDIzMiAwIFIvSW0xOTIgMjMzIDAgUi9JbTE5MyAy
MzQgMCBSL0ltMTk0IDIzNSAwIFIvSW0xOTUgMjM2IDAgUi9JbTE5NiAyMzcgMCBSL0ltMTk3IDIz
OCAwIFIvSW0xOTggMjM5IDAgUi9JbTE5OSAyNDAgMCBSL0ltMjAwIDI0MSAwIFIvSW0yMDEgMjQy
IDAgUi9JbTIwMiAyNDMgMCBSL0ltMjAzIDI0NCAwIFIvSW0yMDQgMjQ1IDAgUi9JbTIwNSAyNDYg
MCBSL0ltMjA2IDI0NyAwIFIvSW0yMDcgMjQ4IDAgUi9JbTIwOCAyNDkgMCBSL0ltMjA5IDI1MCAw
IFIvSW0yMTAgMjUxIDAgUi9JbTIxMSAyNTIgMCBSL0ltMjEyIDI1MyAwIFIvSW0yMTMgMjU0IDAg
Ui9JbTIxNCAyNTUgMCBSL0ltMjE1IDI1NiAwIFIvSW0yMTYgMjU3IDAgUi9JbTIxNyAyNTggMCBS
L0ltMjE4IDI1OSAwIFIvSW0yMTkgMjYwIDAgUi9JbTIyMCAyNjEgMCBSL0ltMjIxIDI2MiAwIFIv
SW0yMjIgMjYzIDAgUi9JbTIyMyAyNjQgMCBSL0ltMjI0IDI2NSAwIFIvSW0yMjUgMjY2IDAgUi9J
bTIyNiAyNjcgMCBSL0ltMjI3IDI2OCAwIFIvSW0yMjggMjY5IDAgUi9JbTIyOSAyNzAgMCBSL0lt
MjMwIDI3MSAwIFIvSW0yMzEgMjcyIDAgUi9JbTIzMiAyNzMgMCBSL0ltMjMzIDI3NCAwIFIvSW0y
MzQgMjc1IDAgUi9JbTIzNSAyNzYgMCBSL0ltMjM2IDI3NyAwIFIvSW0yMzcgMjc4IDAgUi9JbTIz
OCAyNzkgMCBSL0ltMjM5IDI4MCAwIFIvSW0yNDAgMjgxIDAgUi9JbTI0MSAyODIgMCBSL0ltMjQy
IDI4MyAwIFIvSW0yNDMgMjg0IDAgUi9JbTI0NCAyODUgMCBSL0ltMjQ1IDI4NiAwIFIvSW0yNDYg
Mjg3IDAgUi9JbTI0NyAyODggMCBSL0ltMjQ4IDI4OSAwIFIvSW0yNDkgMjkwIDAgUi9JbTI1MCAy
OTEgMCBSL0ltMjUxIDI5MiAwIFIvSW0yNTIgMjkzIDAgUi9JbTI1MyAyOTQgMCBSL0ltMjU0IDI5
NSAwIFIvSW0yNTUgMjk2IDAgUi9JbTI1NiAyOTcgMCBSL0ltMjU3IDI5OCAwIFIvSW0yNTggMjk5
IDAgUi9JbTI1OSAzMDAgMCBSL0ltMjYwIDMwMSAwIFIvSW0yNjEgMzAyIDAgUi9JbTI2MiAzMDMg
MCBSL0ltMjYzIDMwNCAwIFIvSW0yNjQgMzA1IDAgUi9JbTI2NSAzMDYgMCBSL0ltMjY2IDMwNyAw
IFIvSW0yNjcgMzA4IDAgUi9JbTI2OCAzMDkgMCBSL0ltMjY5IDMxMCAwIFIvSW0yNzAgMzExIDAg
Ui9JbTI3MSAzMTIgMCBSL0ltMjcyIDMxMyAwIFIvSW0yNzMgMzE0IDAgUi9JbTI3NCAzMTUgMCBS
L0ltMjc1IDMxNiAwIFIvSW0yNzYgMzE3IDAgUi9JbTI3NyAzMTggMCBSL0ltMjc4IDMxOSAwIFIv
SW0yNzkgMzIwIDAgUi9JbTI4MCAzMjEgMCBSL0ltMjgxIDMyMiAwIFIvSW0yODIgMzIzIDAgUi9J
bTI4MyAzMjQgMCBSL0ltMjg0IDMyNSAwIFIvSW0yODUgMzI2IDAgUi9JbTI4NiAzMjcgMCBSL0lt
Mjg3IDMyOCAwIFIvSW0yODggMzI5IDAgUi9JbTI4OSAzMzAgMCBSL0ltMjkwIDMzMSAwIFIvSW0y
OTEgMzMyIDAgUi9JbTI5MiAzMzMgMCBSL0ltMjkzIDMzNCAwIFIvSW0yOTQgMzM1IDAgUi9JbTI5
NSAzMzYgMCBSL0ltMjk2IDMzNyAwIFIvSW0yOTcgMzM4IDAgUi9JbTI5OCAzMzkgMCBSL0ltMjk5
IDM0MCAwIFIvSW0zMDAgMzQxIDAgUi9JbTMwMSAzNDIgMCBSL0ltMzAyIDM0MyAwIFIvSW0zMDMg
MzQ0IDAgUi9JbTMwNCAzNDUgMCBSL0ltMzA1IDM0NiAwIFIvSW0zMDYgMzQ3IDAgUi9JbTMwNyAz
NDggMCBSL0ltMzA4IDM0OSAwIFIvSW0zMDkgMzUwIDAgUi9JbTMxMCAzNTEgMCBSL0ltMzExIDM1
MiAwIFIvSW0zMTIgMzUzIDAgUi9JbTMxMyAzNTQgMCBSL0ltMzE0IDM1NSAwIFIvSW0zMTUgMzU2
IDAgUi9JbTMxNiAzNTcgMCBSL0ltMzE3IDM1OCAwIFIvSW0zMTggMzU5IDAgUi9JbTMxOSAzNjAg
MCBSL0ltMzIwIDM2MSAwIFIvSW0zMjEgMzYyIDAgUi9JbTMyMiAzNjMgMCBSL0ltMzIzIDM2NCAw
IFIvSW0zMjQgMzY1IDAgUi9JbTMyNSAzNjYgMCBSL0ltMzI2IDM2NyAwIFIvSW0zMjcgMzY4IDAg
Ui9JbTMyOCAzNjkgMCBSL0ltMzI5IDM3MCAwIFIvSW0zMzAgMzcxIDAgUi9JbTMzMSAzNzIgMCBS
L0ltMzMyIDM3MyAwIFIvSW0zMzMgMzc0IDAgUi9JbTMzNCAzNzUgMCBSL0ltMzM1IDM3NiAwIFIv
SW0zMzYgMzc3IDAgUi9JbTMzNyAzNzggMCBSL0ltMzM4IDM3OSAwIFIvSW0zMzkgMzgwIDAgUi9J
bTM0MCAzODEgMCBSL0ltMzQxIDM4MiAwIFIvSW0zNDIgMzgzIDAgUi9JbTM0MyAzODQgMCBSL0lt
MzQ0IDM4NSAwIFIvSW0zNDUgMzg2IDAgUi9JbTM0NiAzODcgMCBSL0ltMzQ3IDM4OCAwIFIvSW0z
NDggMzg5IDAgUi9JbTM0OSAzOTAgMCBSL0ltMzUwIDM5MSAwIFIvSW0zNTEgMzkyIDAgUi9JbTM1
MiAzOTMgMCBSL0ltMzUzIDM5NCAwIFIvSW0zNTQgMzk1IDAgUi9JbTM1NSAzOTYgMCBSL0ltMzU2
IDM5NyAwIFIvSW0zNTcgMzk4IDAgUi9JbTM1OCAzOTkgMCBSL0ltMzU5IDQwMCAwIFIvSW0zNjAg
NDAxIDAgUi9JbTM2MSA0MDIgMCBSL0ltMzYyIDQwMyAwIFIvSW0zNjMgNDA0IDAgUi9JbTM2NCA0
MDUgMCBSL0ltMzY1IDQwNiAwIFIvSW0zNjYgNDA3IDAgUi9JbTM2NyA0MDggMCBSL0ltMzY4IDQw
OSAwIFIvSW0zNjkgNDEwIDAgUi9JbTM3MCA0MTEgMCBSL0ltMzcxIDQxMiAwIFIvSW0zNzIgNDEz
IDAgUi9JbTM3MyA0MTQgMCBSL0ltMzc0IDQxNSAwIFIvSW0zNzUgNDE2IDAgUi9JbTM3NiA0MTcg
MCBSL0ltMzc3IDQxOCAwIFIvSW0zNzggNDE5IDAgUi9JbTM3OSA0MjAgMCBSL0ltMzgwIDQyMSAw
IFIvSW0zODEgNDIyIDAgUi9JbTM4MiA0MjMgMCBSL0ltMzgzIDQyNCAwIFIvSW0zODQgNDI1IDAg
Ui9JbTM4NSA0MjYgMCBSL0ltMzg2IDQyNyAwIFIvSW0zODcgNDI4IDAgUi9JbTM4OCA0MjkgMCBS
L0ltMzg5IDQzMCAwIFIvSW0zOTAgNDMxIDAgUi9JbTM5MSA0MzIgMCBSL0ltMzkyIDQzMyAwIFIv
SW0zOTMgNDM0IDAgUi9JbTM5NCA0MzUgMCBSL0ltMzk1IDQzNiAwIFIvSW0zOTYgNDM3IDAgUi9J
bTM5NyA0MzggMCBSL0ltMzk4IDQzOSAwIFIvSW0zOTkgNDQwIDAgUi9JbTQwMCA0NDEgMCBSL0lt
NDAxIDQ0MiAwIFIvSW00MDIgNDQzIDAgUi9JbTQwMyA0NDQgMCBSL0ltNDA0IDQ0NSAwIFIvSW00
MDUgNDQ2IDAgUi9JbTQwNiA0NDcgMCBSL0ltNDA3IDQ0OCAwIFIvSW00MDggNDQ5IDAgUi9JbTQw
OSA0NTAgMCBSL0ltNDEwIDQ1MSAwIFIvSW00MTEgNDUyIDAgUi9JbTQxMiA0NTMgMCBSL0ltNDEz
IDQ1NCAwIFIvSW00MTQgNDU1IDAgUi9JbTQxNSA0NTYgMCBSL0ltNDE2IDQ1NyAwIFIvSW00MTcg
NDU4IDAgUi9JbTQxOCA0NTkgMCBSL0ltNDE5IDQ2MCAwIFIvSW00MjAgNDYxIDAgUi9JbTQyMSA0
NjIgMCBSL0ltNDIyIDQ2MyAwIFIvSW00MjMgNDY0IDAgUi9JbTQyNCA0NjUgMCBSL0ltNDI1IDQ2
NiAwIFIvSW00MjYgNDY3IDAgUi9JbTQyNyA0NjggMCBSL0ltNDI4IDQ2OSAwIFIvSW00MjkgNDcw
IDAgUi9JbTQzMCA0NzEgMCBSL0ltNDMxIDQ3MiAwIFIvSW00MzIgNDczIDAgUi9JbTQzMyA0NzQg
MCBSL0ltNDM0IDQ3NSAwIFIvSW00MzUgNDc2IDAgUi9JbTQzNiA0NzcgMCBSL0ltNDM3IDQ3OCAw
IFIvSW00MzggNDc5IDAgUi9JbTQzOSA0ODAgMCBSL0ltNDQwIDQ4MSAwIFIvSW00NDEgNDgyIDAg
Ui9JbTQ0MiA0ODMgMCBSL0ltNDQzIDQ4NCAwIFIvSW00NDQgNDg1IDAgUi9JbTQ0NSA0ODYgMCBS
L0ltNDQ2IDQ4NyAwIFIvSW00NDcgNDg4IDAgUi9JbTQ0OCA0ODkgMCBSL0ltNDQ5IDQ5MCAwIFIv
SW00NTAgNDkxIDAgUi9JbTQ1MSA0OTIgMCBSL0ltNDUyIDQ5MyAwIFIvSW00NTMgNDk0IDAgUi9J
bTQ1NCA0OTUgMCBSL0ltNDU1IDQ5NiAwIFIvSW00NTYgNDk3IDAgUi9JbTQ1NyA0OTggMCBSL0lt
NDU4IDQ5OSAwIFIvSW00NTkgNTAwIDAgUi9JbTQ2MCA1MDEgMCBSL0ltNDYxIDUwMiAwIFIvSW00
NjIgNTAzIDAgUi9JbTQ2MyA1MDQgMCBSL0ltNDY0IDUwNSAwIFIvSW00NjUgNTA2IDAgUi9JbTQ2
NiA1MDcgMCBSL0ltNDY3IDUwOCAwIFIvSW00NjggNTA5IDAgUi9JbTQ2OSA1MTAgMCBSL0ltNDcw
IDUxMSAwIFIvSW00NzEgNTEyIDAgUi9JbTQ3MiA1MTMgMCBSL0ltNDczIDUxNCAwIFIvSW00NzQg
NTE1IDAgUi9JbTQ3NSA1MTYgMCBSL0ltNDc2IDUxNyAwIFIvSW00NzcgNTE4IDAgUi9JbTQ3OCA1
MTkgMCBSL0ltNDc5IDUyMCAwIFIvSW00ODAgNTIxIDAgUi9JbTQ4MSA1MjIgMCBSL0ltNDgyIDUy
MyAwIFIvSW00ODMgNTI0IDAgUi9JbTQ4NCA1MjUgMCBSL0ltNDg1IDUyNiAwIFIvSW00ODYgNTI3
IDAgUi9JbTQ4NyA1MjggMCBSL0ltNDg4IDUyOSAwIFIvSW00ODkgNTMwIDAgUi9JbTQ5MCA1MzEg
MCBSL0ltNDkxIDUzMiAwIFIvSW00OTIgNTMzIDAgUi9JbTQ5MyA1MzQgMCBSL0ltNDk0IDUzNSAw
IFIvSW00OTUgNTM2IDAgUi9JbTQ5NiA1MzcgMCBSL0ltNDk3IDUzOCAwIFIvSW00OTggNTM5IDAg
Ui9JbTQ5OSA1NDAgMCBSL0ltNTAwIDU0MSAwIFIvSW01MDEgNTQyIDAgUi9JbTUwMiA1NDMgMCBS
L0ltNTAzIDU0NCAwIFIvSW01MDQgNTQ1IDAgUi9JbTUwNSA1NDYgMCBSL0ltNTA2IDU0NyAwIFIv
SW01MDcgNTQ4IDAgUi9JbTUwOCA1NDkgMCBSL0ltNTA5IDU1MCAwIFIvSW01MTAgNTUxIDAgUi9J
bTUxMSA1NTIgMCBSL0ltNTEyIDU1MyAwIFIvSW01MTMgNTU0IDAgUi9JbTUxNCA1NTUgMCBSL0lt
NTE1IDU1NiAwIFIvSW01MTYgNTU3IDAgUi9JbTUxNyA1NTggMCBSL0ltNTE4IDU1OSAwIFIvSW01
MTkgNTYwIDAgUi9JbTUyMCA1NjEgMCBSL0ltNTIxIDU2MiAwIFIvSW01MjIgNTYzIDAgUi9JbTUy
MyA1NjQgMCBSL0ltNTI0IDU2NSAwIFIvSW01MjUgNTY2IDAgUi9JbTUyNiA1NjcgMCBSL0ltNTI3
IDU2OCAwIFIvSW01MjggNTY5IDAgUi9JbTUyOSA1NzAgMCBSL0ltNTMwIDU3MSAwIFIvSW01MzEg
NTcyIDAgUi9JbTUzMiA1NzMgMCBSL0ltNTMzIDU3NCAwIFIvSW01MzQgNTc1IDAgUi9JbTUzNSA1
NzYgMCBSL0ltNTM2IDU3NyAwIFIvSW01MzcgNTc4IDAgUi9JbTUzOCA1NzkgMCBSL0ltNTM5IDU4
MCAwIFIvSW01NDAgNTgxIDAgUi9JbTU0MSA1ODIgMCBSL0ltNTQyIDU4MyAwIFIvSW01NDMgNTg0
IDAgUi9JbTU0NCA1ODUgMCBSL0ltNTQ1IDU4NiAwIFIvSW01NDYgNTg3IDAgUi9JbTU0NyA1ODgg
MCBSL0ltNTQ4IDU4OSAwIFIvSW01NDkgNTkwIDAgUi9JbTU1MCA1OTEgMCBSL0ltNTUxIDU5MiAw
IFIvSW01NTIgNTkzIDAgUi9JbTU1MyA1OTQgMCBSL0ltNTU0IDU5NSAwIFIvSW01NTUgNTk2IDAg
Ui9JbTU1NiA1OTcgMCBSL0ltNTU3IDU5OCAwIFIvSW01NTggNTk5IDAgUi9JbTU1OSA2MDAgMCBS
L0ltNTYwIDYwMSAwIFIvSW01NjEgNjAyIDAgUi9JbTU2MiA2MDMgMCBSL0ltNTYzIDYwNCAwIFIv
SW01NjQgNjA1IDAgUi9JbTU2NSA2MDYgMCBSL0ltNTY2IDYwNyAwIFIvSW01NjcgNjA4IDAgUi9J
bTU2OCA2MDkgMCBSL0ltNTY5IDYxMCAwIFIvSW01NzAgNjExIDAgUi9JbTU3MSA2MTIgMCBSL0lt
NTcyIDYxMyAwIFIvSW01NzMgNjE0IDAgUi9JbTU3NCA2MTUgMCBSL0ltNTc1IDYxNiAwIFIvSW01
NzYgNjE3IDAgUi9JbTU3NyA2MTggMCBSL0ltNTc4IDYxOSAwIFIvSW01NzkgNjIwIDAgUi9JbTU4
MCA2MjEgMCBSL0ltNTgxIDYyMiAwIFIvSW01ODIgNjIzIDAgUi9JbTU4MyA2MjQgMCBSL0ltNTg0
IDYyNSAwIFIvSW01ODUgNjI2IDAgUi9JbTU4NiA2MjcgMCBSL0ltNTg3IDYyOCAwIFIvSW01ODgg
NjI5IDAgUi9JbTU4OSA2MzAgMCBSL0ltNTkwIDYzMSAwIFIvSW01OTEgNjMyIDAgUi9JbTU5MiA2
MzMgMCBSL0ltNTkzIDYzNCAwIFIvSW01OTQgNjM1IDAgUi9JbTU5NSA2MzYgMCBSL0ltNTk2IDYz
NyAwIFIvSW01OTcgNjM4IDAgUi9JbTU5OCA2MzkgMCBSL0ltNTk5IDY0MCAwIFIvSW02MDAgNjQx
IDAgUi9JbTYwMSA2NDIgMCBSL0ltNjAyIDY0MyAwIFIvSW02MDMgNjQ0IDAgUi9JbTYwNCA2NDUg
MCBSL0ltNjA1IDY0NiAwIFIvSW02MDYgNjQ3IDAgUi9JbTYwNyA2NDggMCBSL0ltNjA4IDY0OSAw
IFIvSW02MDkgNjUwIDAgUi9JbTYxMCA2NTEgMCBSL0ltNjExIDY1MiAwIFIvSW02MTIgNjUzIDAg
Ui9JbTYxMyA2NTQgMCBSL0ltNjE0IDY1NSAwIFIvSW02MTUgNjU2IDAgUi9JbTYxNiA2NTcgMCBS
L0ltNjE3IDY1OCAwIFIvSW02MTggNjU5IDAgUi9JbTYxOSA2NjAgMCBSL0ltNjIwIDY2MSAwIFIv
SW02MjEgNjYyIDAgUi9JbTYyMiA2NjMgMCBSL0ltNjIzIDY2NCAwIFIvSW02MjQgNjY1IDAgUi9J
bTYyNSA2NjYgMCBSL0ltNjI2IDY2NyAwIFIvSW02MjcgNjY4IDAgUi9JbTYyOCA2NjkgMCBSL0lt
NjI5IDY3MCAwIFIvSW02MzAgNjcxIDAgUi9JbTYzMSA2NzIgMCBSL0ltNjMyIDY3MyAwIFIvSW02
MzMgNjc0IDAgUi9JbTYzNCA2NzUgMCBSL0ltNjM1IDY3NiAwIFIvSW02MzYgNjc3IDAgUi9JbTYz
NyA2NzggMCBSL0ltNjM4IDY3OSAwIFIvSW02MzkgNjgwIDAgUi9JbTY0MCA2ODEgMCBSL0ltNjQx
IDY4MiAwIFIvSW02NDIgNjgzIDAgUi9JbTY0MyA2ODQgMCBSL0ltNjQ0IDY4NSAwIFIvSW02NDUg
Njg2IDAgUi9JbTY0NiA2ODcgMCBSL0ltNjQ3IDY4OCAwIFIvSW02NDggNjg5IDAgUi9JbTY0OSA2
OTAgMCBSL0ltNjUwIDY5MSAwIFIvSW02NTEgNjkyIDAgUi9JbTY1MiA2OTMgMCBSL0ltNjUzIDY5
NCAwIFIvSW02NTQgNjk1IDAgUi9JbTY1NSA2OTYgMCBSL0ltNjU2IDY5NyAwIFIvSW02NTcgNjk4
IDAgUi9JbTY1OCA2OTkgMCBSL0ltNjU5IDcwMCAwIFIvSW02NjAgNzAxIDAgUi9JbTY2MSA3MDIg
MCBSL0ltNjYyIDcwMyAwIFIvSW02NjMgNzA0IDAgUi9JbTY2NCA3MDUgMCBSL0ltNjY1IDcwNiAw
IFIvSW02NjYgNzA3IDAgUi9JbTY2NyA3MDggMCBSL0ltNjY4IDcwOSAwIFIvSW02NjkgNzEwIDAg
Ui9JbTY3MCA3MTEgMCBSL0ltNjcxIDcxMiAwIFIvSW02NzIgNzEzIDAgUi9JbTY3MyA3MTQgMCBS
L0ltNjc0IDcxNSAwIFIvSW02NzUgNzE2IDAgUi9JbTY3NiA3MTcgMCBSL0ltNjc3IDcxOCAwIFIv
SW02NzggNzE5IDAgUi9JbTY3OSA3MjAgMCBSL0ltNjgwIDcyMSAwIFIvSW02ODEgNzIyIDAgUi9J
bTY4MiA3MjMgMCBSL0ltNjgzIDcyNCAwIFIvSW02ODQgNzI1IDAgUi9JbTY4NSA3MjYgMCBSL0lt
Njg2IDcyNyAwIFIvSW02ODcgNzI4IDAgUi9JbTY4OCA3MjkgMCBSL0ltNjg5IDczMCAwIFIvSW02
OTAgNzMxIDAgUi9JbTY5MSA3MzIgMCBSL0ltNjkyIDczMyAwIFIvSW02OTMgNzM0IDAgUi9JbTY5
NCA3MzUgMCBSL0ltNjk1IDczNiAwIFIvSW02OTYgNzM3IDAgUi9JbTY5NyA3MzggMCBSL0ltNjk4
IDczOSAwIFIvSW02OTkgNzQwIDAgUi9JbTcwMCA3NDEgMCBSL0ltNzAxIDc0MiAwIFIvSW03MDIg
NzQzIDAgUi9JbTcwMyA3NDQgMCBSL0ltNzA0IDc0NSAwIFIvSW03MDUgNzQ2IDAgUi9JbTcwNiA3
NDcgMCBSL0ltNzA3IDc0OCAwIFIvSW03MDggNzQ5IDAgUi9JbTcwOSA3NTAgMCBSL0ltNzEwIDc1
MSAwIFIvSW03MTEgNzUyIDAgUi9JbTcxMiA3NTMgMCBSL0ltNzEzIDc1NCAwIFIvSW03MTQgNzU1
IDAgUi9JbTcxNSA3NTYgMCBSL0ltNzE2IDc1NyAwIFIvSW03MTcgNzU4IDAgUi9JbTcxOCA3NTkg
MCBSL0ltNzE5IDc2MCAwIFIvSW03MjAgNzYxIDAgUi9JbTcyMSA3NjIgMCBSL0ltNzIyIDc2MyAw
IFIvSW03MjMgNzY0IDAgUi9JbTcyNCA3NjUgMCBSL0ltNzI1IDc2NiAwIFIvSW03MjYgNzY3IDAg
Ui9JbTcyNyA3NjggMCBSL0ltNzI4IDc2OSAwIFIvSW03MjkgNzcwIDAgUi9JbTczMCA3NzEgMCBS
L0ltNzMxIDc3MiAwIFIvSW03MzIgNzczIDAgUi9JbTczMyA3NzQgMCBSL0ltNzM0IDc3NSAwIFIv
SW03MzUgNzc2IDAgUi9JbTczNiA3NzcgMCBSL0ltNzM3IDc3OCAwIFIvSW03MzggNzc5IDAgUi9J
bTczOSA3ODAgMCBSL0ltNzQwIDc4MSAwIFIvSW03NDEgNzgyIDAgUi9JbTc0MiA3ODMgMCBSL0lt
NzQzIDc4NCAwIFIvSW03NDQgNzg1IDAgUi9JbTc0NSA3ODYgMCBSL0ltNzQ2IDc4NyAwIFIvSW03
NDcgNzg4IDAgUi9JbTc0OCA3ODkgMCBSL0ltNzQ5IDc5MCAwIFIvSW03NTAgNzkxIDAgUi9JbTc1
MSA3OTIgMCBSL0ltNzUyIDc5MyAwIFIvSW03NTMgNzk0IDAgUi9JbTc1NCA3OTUgMCBSL0ltNzU1
IDc5NiAwIFIvSW03NTYgNzk3IDAgUi9JbTc1NyA3OTggMCBSL0ltNzU4IDc5OSAwIFIvSW03NTkg
ODAwIDAgUi9JbTc2MCA4MDEgMCBSL0ltNzYxIDgwMiAwIFIvSW03NjIgODAzIDAgUi9JbTc2MyA4
MDQgMCBSL0ltNzY0IDgwNSAwIFIvSW03NjUgODA2IDAgUi9JbTc2NiA4MDcgMCBSL0ltNzY3IDgw
OCAwIFIvSW03NjggODA5IDAgUi9JbTc2OSA4MTAgMCBSL0ltNzcwIDgxMSAwIFIvSW03NzEgODEy
IDAgUi9JbTc3MiA4MTMgMCBSL0ltNzczIDgxNCAwIFIvSW03NzQgODE1IDAgUi9JbTc3NSA4MTYg
MCBSL0ltNzc2IDgxNyAwIFIvSW03NzcgODE4IDAgUi9JbTc3OCA4MTkgMCBSL0ltNzc5IDgyMCAw
IFIvSW03ODAgODIxIDAgUi9JbTc4MSA4MjIgMCBSL0ltNzgyIDgyMyAwIFIvSW03ODMgODI0IDAg
Ui9JbTc4NCA4MjUgMCBSL0ltNzg1IDgyNiAwIFIvSW03ODYgODI3IDAgUi9JbTc4NyA4MjggMCBS
L0ltNzg4IDgyOSAwIFIvSW03ODkgODMwIDAgUi9JbTc5MCA4MzEgMCBSL0ltNzkxIDgzMiAwIFIv
SW03OTIgODMzIDAgUi9JbTc5MyA4MzQgMCBSL0ltNzk0IDgzNSAwIFIvSW03OTUgODM2IDAgUi9J
bTc5NiA4MzcgMCBSL0ltNzk3IDgzOCAwIFIvSW03OTggODM5IDAgUi9JbTc5OSA4NDAgMCBSL0lt
ODAwIDg0MSAwIFIvSW04MDEgODQyIDAgUi9JbTgwMiA4NDMgMCBSL0ltODAzIDg0NCAwIFIvSW04
MDQgODQ1IDAgUi9JbTgwNSA4NDYgMCBSL0ltODA2IDg0NyAwIFIvSW04MDcgODQ4IDAgUi9JbTgw
OCA4NDkgMCBSL0ltODA5IDg1MCAwIFIvSW04MTAgODUxIDAgUi9JbTgxMSA4NTIgMCBSL0ltODEy
IDg1MyAwIFIvSW04MTMgODU0IDAgUi9JbTgxNCA4NTUgMCBSL0ltODE1IDg1NiAwIFIvSW04MTYg
ODU3IDAgUi9JbTgxNyA4NTggMCBSL0ltODE4IDg1OSAwIFIvSW04MTkgODYwIDAgUi9JbTgyMCA4
NjEgMCBSL0ltODIxIDg2MiAwIFIvSW04MjIgODYzIDAgUi9JbTgyMyA4NjQgMCBSL0ltODI0IDg2
NSAwIFIvSW04MjUgODY2IDAgUi9JbTgyNiA4NjcgMCBSL0ltODI3IDg2OCAwIFIvSW04MjggODY5
IDAgUi9JbTgyOSA4NzAgMCBSL0ltODMwIDg3MSAwIFIvSW04MzEgODcyIDAgUi9JbTgzMiA4NzMg
MCBSL0ltODMzIDg3NCAwIFIvSW04MzQgODc1IDAgUi9JbTgzNSA4NzYgMCBSL0ltODM2IDg3NyAw
IFIvSW04MzcgODc4IDAgUi9JbTgzOCA4NzkgMCBSL0ltODM5IDg4MCAwIFIvSW04NDAgODgxIDAg
Ui9JbTg0MSA4ODIgMCBSL0ltODQyIDg4MyAwIFIvSW04NDMgODg0IDAgUi9JbTg0NCA4ODUgMCBS
L0ltODQ1IDg4NiAwIFIvSW04NDYgODg3IDAgUi9JbTg0NyA4ODggMCBSL0ltODQ4IDg4OSAwIFIv
SW04NDkgODkwIDAgUi9JbTg1MCA4OTEgMCBSL0ltODUxIDg5MiAwIFIvSW04NTIgODkzIDAgUi9J
bTg1MyA4OTQgMCBSL0ltODU0IDg5NSAwIFIvSW04NTUgODk2IDAgUi9JbTg1NiA4OTcgMCBSL0lt
ODU3IDg5OCAwIFIvSW04NTggODk5IDAgUi9JbTg1OSA5MDAgMCBSL0ltODYwIDkwMSAwIFIvSW04
NjEgOTAyIDAgUi9JbTg2MiA5MDMgMCBSL0ltODYzIDkwNCAwIFIvSW04NjQgOTA1IDAgUi9JbTg2
NSA5MDYgMCBSL0ltODY2IDkwNyAwIFIvSW04NjcgOTA4IDAgUi9JbTg2OCA5MDkgMCBSL0ltODY5
IDkxMCAwIFIvSW04NzAgOTExIDAgUi9JbTg3MSA5MTIgMCBSL0ltODcyIDkxMyAwIFIvSW04NzMg
OTE0IDAgUi9JbTg3NCA5MTUgMCBSL0ltODc1IDkxNiAwIFIvSW04NzYgOTE3IDAgUi9JbTg3NyA5
MTggMCBSL0ltODc4IDkxOSAwIFIvSW04NzkgOTIwIDAgUi9JbTg4MCA5MjEgMCBSL0ltODgxIDky
MiAwIFIvSW04ODIgOTIzIDAgUi9JbTg4MyA5MjQgMCBSL0ltODg0IDkyNSAwIFIvSW04ODUgOTI2
IDAgUi9JbTg4NiA5MjcgMCBSL0ltODg3IDkyOCAwIFIvSW04ODggOTI5IDAgUi9JbTg4OSA5MzAg
MCBSL0ltODkwIDkzMSAwIFIvSW04OTEgOTMyIDAgUi9JbTg5MiA5MzMgMCBSL0ltODkzIDkzNCAw
IFIvSW04OTQgOTM1IDAgUi9JbTg5NSA5MzYgMCBSL0ltODk2IDkzNyAwIFIvSW04OTcgOTM4IDAg
Ui9JbTg5OCA5MzkgMCBSL0ltODk5IDk0MCAwIFIvSW05MDAgOTQxIDAgUi9JbTkwMSA5NDIgMCBS
L0ltOTAyIDk0MyAwIFIvSW05MDMgOTQ0IDAgUi9JbTkwNCA5NDUgMCBSL0ltOTA1IDk0NiAwIFIv
SW05MDYgOTQ3IDAgUi9JbTkwNyA5NDggMCBSL0ltOTA4IDk0OSAwIFIvSW05MDkgOTUwIDAgUi9J
bTkxMCA5NTEgMCBSL0ltOTExIDk1MiAwIFIvSW05MTIgOTUzIDAgUi9JbTkxMyA5NTQgMCBSL0lt
OTE0IDk1NSAwIFIvSW05MTUgOTU2IDAgUi9JbTkxNiA5NTcgMCBSL0ltOTE3IDk1OCAwIFIvSW05
MTggOTU5IDAgUi9JbTkxOSA5NjAgMCBSL0ltOTIwIDk2MSAwIFIvSW05MjEgOTYyIDAgUi9JbTky
MiA5NjMgMCBSL0ltOTIzIDk2NCAwIFIvSW05MjQgOTY1IDAgUi9JbTkyNSA5NjYgMCBSL0ltOTI2
IDk2NyAwIFIvSW05MjcgOTY4IDAgUi9JbTkyOCA5NjkgMCBSL0ltOTI5IDk3MCAwIFIvSW05MzAg
OTcxIDAgUi9JbTkzMSA5NzIgMCBSL0ltOTMyIDk3MyAwIFIvSW05MzMgOTc0IDAgUi9JbTkzNCA5
NzUgMCBSL0ltOTM1IDk3NiAwIFIvSW05MzYgOTc3IDAgUi9JbTkzNyA5NzggMCBSL0ltOTM4IDk3
OSAwIFIvSW05MzkgOTgwIDAgUi9JbTk0MCA5ODEgMCBSL0ltOTQxIDk4MiAwIFIvSW05NDIgOTgz
IDAgUi9JbTk0MyA5ODQgMCBSL0ltOTQ0IDk4NSAwIFIvSW05NDUgOTg2IDAgUi9JbTk0NiA5ODcg
MCBSL0ltOTQ3IDk4OCAwIFIvSW05NDggOTg5IDAgUi9JbTk0OSA5OTAgMCBSL0ltOTUwIDk5MSAw
IFIvSW05NTEgOTkyIDAgUi9JbTk1MiA5OTMgMCBSL0ltOTUzIDk5NCAwIFIvSW05NTQgOTk1IDAg
Ui9JbTk1NSA5OTYgMCBSL0ltOTU2IDk5NyAwIFIvSW05NTcgOTk4IDAgUi9JbTk1OCA5OTkgMCBS
L0ltOTU5IDEwMDAgMCBSL0ltOTYwIDEwMDEgMCBSL0ltOTYxIDEwMDIgMCBSL0ltOTYyIDEwMDMg
MCBSL0ltOTYzIDEwMDQgMCBSL0ltOTY0IDEwMDUgMCBSL0ltOTY1IDEwMDYgMCBSL0ltOTY2IDEw
MDcgMCBSL0ltOTY3IDEwMDggMCBSL0ltOTY4IDEwMDkgMCBSL0ltOTY5IDEwMTAgMCBSL0ltOTcw
IDEwMTEgMCBSL0ltOTcxIDEwMTIgMCBSL0ltOTcyIDEwMTMgMCBSL0ltOTczIDEwMTQgMCBSL0lt
OTc0IDEwMTUgMCBSL0ltOTc1IDEwMTYgMCBSL0ltOTc2IDEwMTcgMCBSL0ltOTc3IDEwMTggMCBS
L0ltOTc4IDEwMTkgMCBSL0ltOTc5IDEwMjAgMCBSL0ltOTgwIDEwMjEgMCBSL0ltOTgxIDEwMjIg
MCBSL0ltOTgyIDEwMjMgMCBSL0ltOTgzIDEwMjQgMCBSL0ltOTg0IDEwMjUgMCBSL0ltOTg1IDEw
MjYgMCBSL0ltOTg2IDEwMjcgMCBSL0ltOTg3IDEwMjggMCBSL0ltOTg4IDEwMjkgMCBSL0ltOTg5
IDEwMzAgMCBSL0ltOTkwIDEwMzEgMCBSL0ltOTkxIDEwMzIgMCBSL0ltOTkyIDEwMzMgMCBSL0lt
OTkzIDEwMzQgMCBSL0ltOTk0IDEwMzUgMCBSL0ltOTk1IDEwMzYgMCBSL0ltOTk2IDEwMzcgMCBS
L0ltOTk3IDEwMzggMCBSL0ltOTk4IDEwMzkgMCBSL0ltOTk5IDEwNDAgMCBSL0ltMTAwMCAxMDQx
IDAgUi9JbTEwMDEgMTA0MiAwIFIvSW0xMDAyIDEwNDMgMCBSL0ltMTAwMyAxMDQ0IDAgUi9JbTEw
MDQgMTA0NSAwIFIvSW0xMDA1IDEwNDYgMCBSL0ltMTAwNiAxMDQ3IDAgUi9JbTEwMDcgMTA0OCAw
IFIvSW0xMDA4IDEwNDkgMCBSL0ltMTAwOSAxMDUwIDAgUi9JbTEwMTAgMTA1MSAwIFIvSW0xMDEx
IDEwNTIgMCBSL0ltMTAxMiAxMDUzIDAgUi9JbTEwMTMgMTA1NCAwIFIvSW0xMDE0IDEwNTUgMCBS
L0ltMTAxNSAxMDU2IDAgUi9JbTEwMTYgMTA1NyAwIFIvSW0xMDE3IDEwNTggMCBSL0ltMTAxOCAx
MDU5IDAgUi9JbTEwMTkgMTA2MCAwIFIvSW0xMDIwIDEwNjEgMCBSL0ltMTAyMSAxMDYyIDAgUi9J
bTEwMjIgMTA2MyAwIFIvSW0xMDIzIDEwNjQgMCBSL0ltMTAyNCAxMDY1IDAgUi9JbTEwMjUgMTA2
NiAwIFIvSW0xMDI2IDEwNjcgMCBSL0ltMTAyNyAxMDY4IDAgUi9JbTEwMjggMTA2OSAwIFIvSW0x
MDI5IDEwNzAgMCBSL0ltMTAzMCAxMDcxIDAgUi9JbTEwMzEgMTA3MiAwIFIvSW0xMDMyIDEwNzMg
MCBSL0ltMTAzMyAxMDc0IDAgUi9JbTEwMzQgMTA3NSAwIFIvSW0xMDM1IDEwNzYgMCBSL0ltMTAz
NiAxMDc3IDAgUi9JbTEwMzcgMTA3OCAwIFIvSW0xMDM4IDEwNzkgMCBSL0ltMTAzOSAxMDgwIDAg
Ui9JbTEwNDAgMTA4MSAwIFIvSW0xMDQxIDEwODIgMCBSL0ltMTA0MiAxMDgzIDAgUi9JbTEwNDMg
MTA4NCAwIFIvSW0xMDQ0IDEwODUgMCBSL0ltMTA0NSAxMDg2IDAgUi9JbTEwNDYgMTA4NyAwIFIv
SW0xMDQ3IDEwODggMCBSL0ltMTA0OCAxMDg5IDAgUi9JbTEwNDkgMTA5MCAwIFIvSW0xMDUwIDEw
OTEgMCBSL0ltMTA1MSAxMDkyIDAgUi9JbTEwNTIgMTA5MyAwIFIvSW0xMDUzIDEwOTQgMCBSL0lt
MTA1NCAxMDk1IDAgUi9JbTEwNTUgMTA5NiAwIFIvSW0xMDU2IDEwOTcgMCBSL0ltMTA1NyAxMDk4
IDAgUi9JbTEwNTggMTA5OSAwIFIvSW0xMDU5IDExMDAgMCBSL0ltMTA2MCAxMTAxIDAgUi9JbTEw
NjEgMTEwMiAwIFIvSW0xMDYyIDExMDMgMCBSL0ltMTA2MyAxMTA0IDAgUi9JbTEwNjQgMTEwNSAw
IFIvSW0xMDY1IDExMDYgMCBSL0ltMTA2NiAxMTA3IDAgUi9JbTEwNjcgMTEwOCAwIFIvSW0xMDY4
IDExMDkgMCBSL0ltMTA2OSAxMTEwIDAgUi9JbTEwNzAgMTExMSAwIFIvSW0xMDcxIDExMTIgMCBS
L0ltMTA3MiAxMTEzIDAgUi9JbTEwNzMgMTExNCAwIFIvSW0xMDc0IDExMTUgMCBSL0ltMTA3NSAx
MTE2IDAgUi9JbTEwNzYgMTExNyAwIFIvSW0xMDc3IDExMTggMCBSL0ltMTA3OCAxMTE5IDAgUi9J
bTEwNzkgMTEyMCAwIFIvSW0xMDgwIDExMjEgMCBSL0ltMTA4MSAxMTIyIDAgUi9JbTEwODIgMTEy
MyAwIFIvSW0xMDgzIDExMjQgMCBSL0ltMTA4NCAxMTI1IDAgUi9JbTEwODUgMTEyNiAwIFIvSW0x
MDg2IDExMjcgMCBSL0ltMTA4NyAxMTI4IDAgUi9JbTEwODggMTEyOSAwIFIvSW0xMDg5IDExMzAg
MCBSL0ltMTA5MCAxMTMxIDAgUi9JbTEwOTEgMTEzMiAwIFIvSW0xMDkyIDExMzMgMCBSL0ltMTA5
MyAxMTM0IDAgUi9JbTEwOTQgMTEzNSAwIFIvSW0xMDk1IDExMzYgMCBSL0ltMTA5NiAxMTM3IDAg
Ui9JbTEwOTcgMTEzOCAwIFIvSW0xMDk4IDExMzkgMCBSL0ltMTA5OSAxMTQwIDAgUi9JbTExMDAg
MTE0MSAwIFIvSW0xMTAxIDExNDIgMCBSL0ltMTEwMiAxMTQzIDAgUi9JbTExMDMgMTE0NCAwIFIv
SW0xMTA0IDExNDUgMCBSL0ltMTEwNSAxMTQ2IDAgUi9JbTExMDYgMTE0NyAwIFIvSW0xMTA3IDEx
NDggMCBSL0ltMTEwOCAxMTQ5IDAgUi9JbTExMDkgMTE1MCAwIFIvSW0xMTEwIDExNTEgMCBSL0lt
MTExMSAxMTUyIDAgUi9JbTExMTIgMTE1MyAwIFIvSW0xMTEzIDExNTQgMCBSL0ltMTExNCAxMTU1
IDAgUi9JbTExMTUgMTE1NiAwIFIvSW0xMTE2IDExNTcgMCBSL0ltMTExNyAxMTU4IDAgUi9JbTEx
MTggMTE1OSAwIFIvSW0xMTE5IDExNjAgMCBSL0ltMTEyMCAxMTYxIDAgUi9JbTExMjEgMTE2MiAw
IFIvSW0xMTIyIDExNjMgMCBSL0ltMTEyMyAxMTY0IDAgUi9JbTExMjQgMTE2NSAwIFIvSW0xMTI1
IDExNjYgMCBSL0ltMTEyNiAxMTY3IDAgUi9JbTExMjcgMTE2OCAwIFIvSW0xMTI4IDExNjkgMCBS
L0ltMTEyOSAxMTcwIDAgUi9JbTExMzAgMTE3MSAwIFIvSW0xMTMxIDExNzIgMCBSL0ltMTEzMiAx
MTczIDAgUi9JbTExMzMgMTE3NCAwIFIvSW0xMTM0IDExNzUgMCBSL0ltMTEzNSAxMTc2IDAgUi9J
bTExMzYgMTE3NyAwIFIvSW0xMTM3IDExNzggMCBSL0ltMTEzOCAxMTc5IDAgUi9JbTExMzkgMTE4
MCAwIFIvSW0xMTQwIDExODEgMCBSL0ltMTE0MSAxMTgyIDAgUi9JbTExNDIgMTE4MyAwIFIvSW0x
MTQzIDExODQgMCBSL0ltMTE0NCAxMTg1IDAgUi9JbTExNDUgMTE4NiAwIFIvSW0xMTQ2IDExODcg
MCBSL0ltMTE0NyAxMTg4IDAgUi9JbTExNDggMTE4OSAwIFIvSW0xMTQ5IDExOTAgMCBSL0ltMTE1
MCAxMTkxIDAgUi9JbTExNTEgMTE5MiAwIFIvSW0xMTUyIDExOTMgMCBSL0ltMTE1MyAxMTk0IDAg
Ui9JbTExNTQgMTE5NSAwIFIvSW0xMTU1IDExOTYgMCBSL0ltMTE1NiAxMTk3IDAgUi9JbTExNTcg
MTE5OCAwIFIvSW0xMTU4IDExOTkgMCBSL0ltMTE1OSAxMjAwIDAgUi9JbTExNjAgMTIwMSAwIFIv
SW0xMTYxIDEyMDIgMCBSL0ltMTE2MiAxMjAzIDAgUi9JbTExNjMgMTIwNCAwIFIvSW0xMTY0IDEy
MDUgMCBSL0ltMTE2NSAxMjA2IDAgUi9JbTExNjYgMTIwNyAwIFIvSW0xMTY3IDEyMDggMCBSL0lt
MTE2OCAxMjA5IDAgUi9JbTExNjkgMTIxMCAwIFIvSW0xMTcwIDEyMTEgMCBSL0ltMTE3MSAxMjEy
IDAgUi9JbTExNzIgMTIxMyAwIFIvSW0xMTczIDEyMTQgMCBSL0ltMTE3NCAxMjE1IDAgUi9JbTEx
NzUgMTIxNiAwIFIvSW0xMTc2IDEyMTcgMCBSL0ltMTE3NyAxMjE4IDAgUi9JbTExNzggMTIxOSAw
IFIvSW0xMTc5IDEyMjAgMCBSL0ltMTE4MCAxMjIxIDAgUi9JbTExODEgMTIyMiAwIFIvSW0xMTgy
IDEyMjMgMCBSL0ltMTE4MyAxMjI0IDAgUi9JbTExODQgMTIyNSAwIFIvSW0xMTg1IDEyMjYgMCBS
Pj4vUHJvY1NldFsvUERGL1RleHQvSW1hZ2VDL0ltYWdlSV0vRXh0R1N0YXRlPDwvR1MxIDEyMjcg
MCBSPj4+Pg1lbmRvYmoNMTEgMCBvYmo8PC9UeXBlL0ZvbnQvRW5jb2RpbmcvV2luQW5zaUVuY29k
aW5nL0Jhc2VGb250L0dJRUhHTStGcmFua2xpbkdvdGhpYy1EZW1pL0ZpcnN0Q2hhciAzMi9MYXN0
Q2hhciAxNDYvU3VidHlwZS9UcnVlVHlwZS9Gb250RGVzY3JpcHRvciAzMyAwIFIvV2lkdGhzWzI1
MCAwIDAgMCAwIDAgMCAwIDI5MyAyOTMgMCAwIDI1NyAyNTcgMjU3IDAgNTg2IDAgNTg2IDU4NiA1
ODYgMCA1ODYgNTg2IDAgMCAwIDAgMCAwIDAgMCAwIDYwOCA2NTEgNjI3IDY0OCA1NzAgNTU0IDAg
NjQ4IDI5MCAzODEgNjMwIDAgODYwIDY0NiA2MzkgNjA0IDAgNjU3IDU4MSA0ODkgNjQ5IDAgODcz
IDAgNTIxIDAgMCAwIDAgMCAwIDAgNTQyIDU0NCA1MTIgNTQwIDUzNSAwIDU1MyA1NDQgMjY1IDAg
NTQzIDI2NSA4MjQgNTQ5IDUzNSA1NDAgMCAzNDcgNDczIDM1MiA1NDIgMCA3MjEgMCA0NDUgNDI4
IDAgMCAwIDAgMCAwIDAgMCAwIDAgMCAwIDAgMCAwIDAgMCAwIDAgMCAwIDAgMCAyNTddPj4NZW5k
b2JqDTEyIDAgb2JqPDwvVHlwZS9Gb250L0VuY29kaW5nL1dpbkFuc2lFbmNvZGluZy9CYXNlRm9u
dC9UaW1lc05ld1JvbWFuUFNNVC9GaXJzdENoYXIgMzIvTGFzdENoYXIgMTUxL1N1YnR5cGUvVHJ1
ZVR5cGUvRm9udERlc2NyaXB0b3IgMzQgMCBSL1dpZHRoc1syNTAgMCAwIDAgMCAwIDc3OCAwIDMz
MyAzMzMgMCAwIDI1MCAzMzMgMjUwIDI3OCA1MDAgMCA1MDAgNTAwIDAgNTAwIDUwMCA1MDAgNTAw
IDAgMjc4IDAgMCAwIDAgMCAwIDcyMiA2NjcgNjY3IDcyMiA2MTEgNTU2IDcyMiA3MjIgMzMzIDM4
OSA3MjIgNjExIDg4OSA3MjIgNzIyIDU1NiA3MjIgNjY3IDU1NiA2MTEgNzIyIDcyMiA5NDQgMCA3
MjIgNjExIDAgMCAwIDAgMCAwIDQ0NCA1MDAgNDQ0IDUwMCA0NDQgMzMzIDUwMCA1MDAgMjc4IDI3
OCA1MDAgMjc4IDc3OCA1MDAgNTAwIDUwMCA1MDAgMzMzIDM4OSAyNzggNTAwIDUwMCA3MjIgNTAw
IDUwMCA0NDQgMCAwIDAgMCAwIDAgMCAwIDAgMCAwIDAgMCAwIDAgMCAwIDAgMCAwIDAgMCAwIDMz
MyAwIDAgMCA1MDAgMTAwMF0+Pg1lbmRvYmoNMTMgMCBvYmo8PC9UeXBlL0ZvbnQvRW5jb2Rpbmcv
SWRlbnRpdHktSC9CYXNlRm9udC9HSUVISU8rU3ltYm9sTVQvU3VidHlwZS9UeXBlMC9EZXNjZW5k
YW50Rm9udHNbMzcgMCBSXS9Ub1VuaWNvZGUgMzggMCBSPj4NZW5kb2JqDTE0IDAgb2JqPDwvVHlw
ZS9Gb250L0VuY29kaW5nL1dpbkFuc2lFbmNvZGluZy9CYXNlRm9udC9UaW1lc05ld1JvbWFuUFMt
Qm9sZE1UL0ZpcnN0Q2hhciAzMi9MYXN0Q2hhciAxMjEvU3VidHlwZS9UcnVlVHlwZS9Gb250RGVz
Y3JpcHRvciAzOSAwIFIvV2lkdGhzWzI1MCAwIDAgMCAwIDAgMCAwIDAgMCAwIDAgMCAzMzMgMCAw
IDUwMCAwIDUwMCAwIDAgMCA1MDAgMCAwIDAgMCAwIDAgMCAwIDAgMCA3MjIgMCA3MjIgNzIyIDY2
NyAwIDc3OCAwIDM4OSAwIDAgNjY3IDk0NCA3MjIgNzc4IDYxMSAwIDcyMiA1NTYgNjY3IDAgNzIy
IDEwMDAgMCAwIDAgMCAwIDAgMCAwIDAgNTAwIDU1NiA0NDQgMCA0NDQgMCA1MDAgNTU2IDI3OCAw
IDU1NiAyNzggODMzIDU1NiA1MDAgNTU2IDAgNDQ0IDM4OSAzMzMgNTU2IDAgMCAwIDUwMF0+Pg1l
bmRvYmoNMTUgMCBvYmpbL0lDQ0Jhc2VkIDI4IDAgUl0NZW5kb2JqDTE2IDAgb2JqWy9JbmRleGVk
IDE1IDAgUiAyNTUgMjkgMCBSXQ1lbmRvYmoNMTcgMCBvYmpbL0luZGV4ZWQgMTUgMCBSIDI1NSAz
MCAwIFJdDWVuZG9iag0xOCAwIG9ialsvSW5kZXhlZCAxNSAwIFIgMjU1IDMxIDAgUl0NZW5kb2Jq
DTE5IDAgb2JqPDwvTGVuZ3RoIDQwNTkvRmlsdGVyL0ZsYXRlRGVjb2RlPj5zdHJlYW0NCkiJxFdb
b9vIFX73r5ingiwsmneRi6JA6k232UUaF9aiKHb7QFMjiTVNyhzKWufX95zzHcq04xRJ0aAxIs7l
3O9zcelyUzsTyZ+ru7OLH64js3VnUVYEaW6KyKRJFISpyaIoyAsz2LPN2Z9WZxerVUwoq81ZlAdh
bEL6wyou4yAzWV4GUW5Wd2eh2dL/Vc0/xzPv2l/96yyKg2UBHFklYRQUc5wgDKOEkbzLD1dvBeUF
myRJnjFhWPMq7WTJ8E+wC6YeLgXjw59fpZ3FQRJ/IfksD5L0E/KFYKz+8rrsyyKI4hf6hiWYvG6g
MgrS9CVGLhj/eH/14frdz+9f45RmGbvxdU78j5HIl6n6MjyhyyrKI1GOdMxOfsnEmUGYlSV79Bdv
tbOm9osg9np/EQWZd+eT1KW3x671E9pYPyaA3xrZjPL76Kd0bfqNUYT+BtdzjHNTCek1iBk/93Y9
uNFVJyTWfHoE7uBndAXcOR3nTGfB90ggkdcD8tb5yyD1KLDvhdYBfCZi5M3CswoD9J3AKXo/R9rK
ZjdXW3XcKLDcHORMRceRXQNuMsTaAt35ETOuqz14AxWsIWIHpsb/5+pHilOiFqUlBff3CMQoV2+V
sXprJPnSIPdsMxjrnO2wHZuqZTPWel0NVT3aoXFjQwWiUiixtK4tG4esafr9ROKu+ViNTY+tgpHV
WLSYFEmiiEJrEi2OJtEoxEQ0W+8IiZ3T+GGQePcH7Kxjtje6a9q1Lkh3WfDtYY913xmngPWO7FkS
nR57RbNs8tRrXWDeKTvXbHdYjc40PmU0Sc/KjT0Mu5jEn9lXUmnSIV8m0OGmHyk4KQrMSGmha38R
SyDmFEw9NgN2ZF2ye+X2tibWlAqE5SwrtB/6m9ZSQHB8kAecOdq2hThxHIRFUsyMSRVaBYkKCEII
e/ahMCCVY05L0T4LlhQF/ZqsuiBHd2sQpZRPsjKZE41P2uUaPH3fkiwiPAVdZ2sKoUo2w2NgVhSY
Bakb02/jfGak9ktiql+J2i95is9Yq0kUZiq3e2QJuYgUqCG86fFxbLvcaw5zENN02I5WF2vyHduM
vUdxg8OBw5HEIqlKTwG35CDeKvktPhIg5Bq52unZQBXC2WqoTwfIimyqP/tnbNjwkgmZpPqc7iDR
fNS74RbfF3IRxAk51LqnB8qIsk3Ubz76iyVzfMnONM6poSiBNgNXH6nOr9QKKRWnEFJnr7nCFN5m
Y4lRxBHLn26UU1GZjECVMSGRUsooCmG5AtoDa0tVwp1TRpV00OGgbuX6IChrnD0D2MqN0pdSvUGl
6eViwEYqJWlNsUYy1Ra9IPUqkH+UDZfPROXB+twoInpN4QHcChkpbhZKUJNAjY+8W0CC/hZCnou7
zBGSD3ZOhlpNLaaCwHeS6Pg9dKBVV3NT9Z2S8yUdVX920ur3WsZL9U041UopspIf/OFgKDmKqP5q
PClAhw/XFT3hRH0WAkjH2YwmU8Gn8THJECcZZLgkSamrUUSkZNqh8bmEUJ3GvpFftgFJwXFScC8Q
EGmE0Wm7wxYI7CeCZAvmE7ZEYA7XU5x1cko+B1VFB+wBm1ZoreXoNbAjk+K0kqwD+SPHRsLicft9
UqED4hbEKoHVM2WAIrKf662ksKEUTTg2nxmmM9hy0FBaCNldp0a8V2VSHWByKmdQ4zA3FihUAnAD
mS2k2UDPAbtJMeAupth6NiEkUwWmzEjZgMI48S5odcQgxBfihKVnBcA5DASYB2JINEH3cqzwMmdp
HeO0Sqg+EShQ8ds/sIGEyQN6NPslgclRZKgmtApSn4D7TmmD4QbU+XanZJwS4niTKYOtTOMFjh3O
ewAbuWODcQt+UEwuC3T8QjNmdIvSLLIpu+FJNKgXUPJTuK9IzHziA3UWnyYiEn55SvgYXuExTDJ4
SRrG6Hq8oSHNupEYLJ/O6vawxsqeT6OTwHLrNl0/7dqGiwUHa0n7ZrSKRZ0Ti++0UtATIcMTQUSN
42V2KgvRqXD8gZ5VBY0NyR+fvSrIYmURY64QDHkcYcLQqem9z9w072IJ7liiopAenepIn0maZDKC
U0EG2L1sJC1i7nSVgAB5rci97PqWk4veAjKPZ/BEzDkizwcGHFQCcHMcWGQOEMMZCEog5Ep3QDG5
VeiXJluoAcRwnG7/jeFgruntFWpQXNlh0w93rFZJZYCV415Y76bxXebxzvxOgnTPbUJGPXJ6tEz/
o0tgD8bXKi8kYDjzLa1FL9c4yvL/gblOT9VJp7/7Cwl0yhaewNtT/VqkmM84ucdjj/0gD8dbbGBA
rMcGjwVOm1LeKqWnjTfSxptNRL+TW/Nmr7gtzePjCxgnHZ+es+12Yt3gmZYpD6dThz7EeOSkUVwp
Cgf37aIuOsXG1PiveJhMybnLIJVJhPKSh31Ztniz8tuCywnMSlW2EegtK+AZilqpZjLAyPgShTK9
4alybNQ73YwCOWa4FboHILWn56YHqt/CBM96ZLQsnwpWpgXL0/ZToY2t5ddMLYF/pR3c+UvpCR9n
jevU2mYtAW2lr+qdtic/0vjbaN8xuOjmTRJY20cwt2iCG2mU/GO7GlfnaEVE7W+gdq0nN5UShQ5C
+ii9cC2t1NhaALSl9dIhld2kuSSJQKtQqh9U4DcuW+u194cOtSx2LOUlQYbK10oiSnlJ0YrLaYTD
qyBDUSkoWZFPEoFfFQ5fGwkFC/5KJIivnpnyCyOBlzSawLp8di/LwzTCPAsALlr9bHRaYMhyTGRy
RoWQUFdObxueztjG/Wx62VO3EInXzHcrnnVmGrRuVQLjrA5azwY7GTAeZhPgToLuwOiVHIDTOZUp
DjOMevMo0yD6zKv0VHwyLT40wlQGzzRWRsgNMj/cui/y+dckvnSQX7xrWx8QZ4jMUX4f5cjgyZbh
zRJjqsjIJZkOHhz5QwUUoOO0w1u0RPAkUubFVZsZ6nACugHuPCWQeNwNKmG9Bmv2yK6HNP+/dPnM
HHs1NHXTbXXQrHRiXT/NrnYabJsHnWGdaWS+1QuMa7MGwTCkORoE9k7mjm85ipWnUSyFYj9U0sR0
jiDm3MLFVz2+gx2b2oyc5LLv8Gkkp+6xOSgKRUDBc2ov/g8xrPLNjSK19mJuAyAJ31HoHfmMqvVw
O00Gly439IagLMzyIudvni4j+ib8z7i6m5tnVpnVMmR3MklotqeXYzqZgLNUfFvtufBH3oDXaoIX
GPI9RS3LKYJLHs2xkeeJVeiDgN1IxNNrk1Om8PDLAR9xoDtjf5uOmFW3xhc5ELGBmK4bhQuPwQLs
DGTYIA2YLbjtVQ6AAcgU+OxBcquvikiqbYo+t1dh5bcV5AacKJ1IcStQN4+g9M7n2fDt27cYFa7o
zQaVza+es9DAUGVWPUH1s4/D5BR7BQwvw2VC9Vbm7C12HEQyamE7mPV0LlBj1bQkQuS5X/2AZb2m
aKr1DZiIhU5kMxhqhk0e3gxKWSIUQ4VM2BlZgkT2PijKaOIwxDKn3t62ptpP1KpBM584VsZNx3Uj
otE82Dh30EMZL7DekJlItzeX1ErfX/zUKohEPVWDwbwnfIaOprrxpHdwqgoxkpteHCHndmiwSsI8
SEycU4nNObTv5lnwhrOA4nNZAENWCRDnKOKpskT/+P5Htkvi/ewvCpL7rxRzHCSX/ya9WnYTR6Lo
r9RqZCSCcPkF2SUkmbaSAMJELIZeOOAO1tB2ZFda4jdmMfO7c+69ZTCPVreUDXYV9biuOvfcc/gZ
OnNxZadhBEDw4DgOrOkzpTpqcTGQKOoN/bM5wlbOZPaYfJlME555spvvI5Lw/Ksl7Q9MiKtu5vGb
G+JLsGOAs9WtTz/zqkn2IwONwzXiVssiu1qn3Nwpou16U77XwuyEj9WqtK72na40gKrZgVAztfe6
dGIaxBiEw0O9FrnQkBPb2MLCkophzp508m5UssNCLErLOv+w74gKRq3KtzTFq4hRQiR0gbR2Jekj
s7k+rSmuPY3DUXiArj4FzmlhiX5ynFH/dI2jQqq90ArPRTx+vr9vUitywiYue1EIPdReu2QNZAnw
vqyg/hO5/ZylNfPTR4UcCdnZupQqWWGUPUDUGgyB/KCCM84Mpxenm+Yi01WjTZpXtSAZwB1qfX4v
bhDZUnGtHnvqZgviI48bcNkkSVKVZsMeb+kwmyJjSEOOVMIklPKgwqQ85hYalwa90iACBV1XRQ3t
pMsO/wd9SvdCssENgotPCvlKQ2EEfsBkq4MD2fbDvQL1rPlD5Em6lXI/INKlgzF5ynWYShqH/xRP
w6vReJYsO7+GDLIX5/UZwOxXELhYeaL7Fi0z4cAbJsTFWFr3c5wYaNRiaHgBQ0Mfd3fAkLb3qIe6
wZCaZTVYOQB6VhmudMuNVWpyXpxbhZJGQQ3FQFo06oVbQBRYQMADhnSHbfD4zaahLXd/11gNlkKN
gJ+IRIbGuTP8qP9aJb0OfY66LdklVLWRbZbObQZ6eUpfZaT0/ivLLGJAxgf6CTLaQkS3IQIfEwy9
NkSOmc5i+4bL6bRiDVp+mDxD8kSUaQA19T2wvKvSYmX751R6S6YhRD37447jQDjYauD8Ej7uAFLi
k4xztEYLQe4wagh8epNwuIsYj4EzBm74mPunsInaDsBrbm8Q7CGTGFvHV5zVmyP5Uhuu/dDKf2bH
CiMz1a6lZwRHjeKgOceQEjhFomU5or8OHsFjjxAyiKJ9BIDQtXruqYcqtaphldWrzbGAMDku8oWm
gQca8WIh4stupxAJ91LZcshdnr2VjDfCMeFFTXtMwmq+ybE7dS2d+yl/ywPt7DpPv0ElLgq4P/gk
FtprUNY3WIi0xcL4nkvHnH9HHTIoEySR59zxOyEjuIQMkCwdRotQ7Mm4/WC4h8eYaIIsHfEqXRhT
6qhcE9WGuGs2OsUbd6fFGvKa6avA5izxfXa61Kik8R3BgapNXsoShTx4gflGGllpB+94Zlc2tX8K
MmY99Uix2VUyYyA1kdQ87aXjOjFPeqle7Sz5hqJp+SyTadlOIMTF/d9F6V/Z0yHweO4ePJKJVw0V
st5Pc0bOG+dfARwFDOVntAdOj+O3DfIWobNGpaQh7LpEqi8dGRDPOwOnBayfiWIP+hD/adyyf6aK
k4ti1IdUO5my1yHOdDJOJrPkSzy9KEfxgLs52+435aiL6dG+GmrL0K4b2QoC1sD4CFAimJJRIQli
/unLSygozmt2JNRTFvLkUodnla3lhV2evO5kFjri8Sy+6apb5nk7ozaQly92mfyHPLOqzs1OxCyQ
AuneP1EeFHWTGl0Vj5I5GKvKUkNi2oVHZOmD+tlVlAm0eWGybZfFKzlW1iRrZbLVpshX6Xa7U6vS
As7uCUz0tX9az7TnW8au38uibqq55q/nQmAtLgvzGOZWdv9WVraSUb4V4DMZTbUYU3cc56jsfFX/
CzAATfy92Q0KZW5kc3RyZWFtDWVuZG9iag0yMCAwIG9iajw8L1R5cGUvRm9udC9FbmNvZGluZy9X
aW5BbnNpRW5jb2RpbmcvQmFzZUZvbnQvR0lFSUFLK0ZyYW5rbGluR290aGljLUJvb2svRmlyc3RD
aGFyIDMyL0xhc3RDaGFyIDExOS9TdWJ0eXBlL1RydWVUeXBlL0ZvbnREZXNjcmlwdG9yIDQxIDAg
Ui9XaWR0aHNbMjUwIDAgMCAwIDAgMCAwIDAgMCAwIDAgMCAyNTAgMCAyNTAgNDU0IDAgMCAwIDAg
MCAwIDAgMCAwIDAgMjUwIDAgMCAwIDAgMCAwIDAgMCAwIDAgMCA1MDggMCAwIDAgMCAwIDAgMCAw
IDAgMCAwIDAgMCAwIDAgMCAwIDAgMCAwIDAgMCAwIDAgMCAwIDUyOSAwIDAgNTM5IDUyMSAwIDQ5
MSA1NDAgMjI5IDAgMCAyMzAgODE0IDAgNTIwIDUzNCAwIDMzMCA0NjQgMzA4IDAgNDUwIDY2NF0+
Pg1lbmRvYmoNMjEgMCBvYmo8PC9MZW5ndGggNDAyOS9GaWx0ZXIvRmxhdGVEZWNvZGU+PnN0cmVh
bQ0KSImUV1tT47gSfs+v0KN8KvGJ7/EjZBgmzIShiNmpU7v7IBIRa2Isynag4Ndvt1q2c2PhFFXB
lu1WX77++lN2NfB9d5wkEzZm2ZfB2B2PxwHLlnDlB2HCspfBn7xsKl04EzfhbPFaN9IZRfzR8TxY
qNlCL5VslKyHTJQr5sR89nV2w7JpjNe/LvE3dgPm/J1dDUbtbiPPHYdeavak7cZjL6Lt/uI3snrQ
ldki5KJcSqYf2FQ/2pVtqZaiUbokd+xq/Zfj0i4X2eC/0zpm0wVEhX+L6fXAY1dw9ZvBTjF7YRM2
Z3/+PWYreKDYwIsCliQpOAWuBbE79tkoiSeskgMvdtNJ+/BxUA/OwXyWJcxj2cMgNRukzEvdScyS
OHYhikeKJ+4is4m8lKUTgquyEpDOgBdsmpsFoSpyHQyHZDjBXdG2ubDmI8ykNT+eoPkRXvrW/gwS
MErciM9F04ihMwrdCWfnum4gV3elepZVrZrXbqvTMYSh6/ldEGm3S+TTLn8oKAiFknDpRPBbiQJ2
jt2YTx1vDAu5efjZsILATbsdx1EfV0g7TnOXfdHbQq1lpQBod6Uzgm0mXD0b8xM39IJoB8J+b8Ij
EzZy/QDgdT3OblQlMVceF9v6g4T4nhtPxl7nYNDWNSDbN5VeV+LRwfgBpqNpDoHXn4ockTtpDQde
a9i3rXABaUy560SczeFHr5Qo9RBvHVNmuJo5I9/1eWbepD3H2F5eBHBt85H0+YjJ8o8WKpmoa7Ut
hEkr5BMTG/fpYlku61oUr2A/4v+eqDgd7yKnj8YCZ+FAnXnjYOUkVLI092vHw4KY9k6gF1TTSEnR
QHfgG5+EUQwtSjAaHYDA6/tjmhcCYjQEhkBtnBHGK5ZDBAZ0y7SSAhYn4JMcXcvmg5DjxE3CHhte
hw1/HxsJYYMuYG8K81NhRVCm8F+6/tZlZ7DHCzYgUAnYLoYtD+hGA3eLPVwkhnYpMZ2xcWoRB8YK
iN9DW49OiukviUiG1OFsdn1rUJIA9jyA3hlmy38Pe35PIIh03GPuoDnX/LKzclU52JLypR7S0rks
ChvAD+IRgIHH721LZf/Z6RZiJosv0yhnr9CIKadfjeUFfoIdAr7eltQ7nenuhRqihip5Idc1uxaN
e/geuhDsuvAexr667Fwsl7IgDBWqrQWkbYYYizBhCPSR4/OL68VeUP6kw49NFjZ2bJKV2K4/F7WA
gPiQ1u5m6OsdrtyLUozg/9RBTOcQkI8FekJXImijdbm3GRHZaLdF/wfey9/IjMDpQDV7tRAHFTjB
1Lf4fVUhWwR8aLn2WldN/iIRPhNeGwuJOwnT+FB07LjCG1ntz6zs92BkPzukt+Oe+AZ+6GUu2+Rn
cpmDakAXImoRY9tFhgOHC1W+1yLjuC9x0OIMjGNPhLyqmyGbmnYI+C9c8/jsPRY+dnOOhAScvh6y
G5NzJ+AK9E5Do+nE1G5T33vVzoqpO/pK5ura5BrMqbKD340uVKb3wdbZCGz3n7mGcMGKXm4EZGWN
TeHD0pAeWChDeX1e4jRi9hpSgMVtrIEFiELUbXvb9fuFdipfIa6R/Csjg/TL0l48NEN6QjMphUv7
KipBdMowAu4ac/pGOejBan2waZ+oMGoxSrPsh/nMdUaBdWDCt28wBadsAXF9UXK9n64TquKinaIX
G7WEVP/MlWaLRlD5TBVBIp0q4jv0e+ayiyei25z+VYZjJc4suCNGVit6hqKb9r8jDrZMjSkzFMs0
XTwgHiDMuahei5bPrZETwH8HYT/BOWrpyvHhS8CpKrHJod4CuGdJqFNH8R61wo6qDCY70ANvLkUp
63xIN3aKmRusb8QNQKAzaoAIu5W1FLSwzPfLHvZlt1177hpSYt/Eb7mBMs+QM5FbiTVDI17h2EO8
iRrF8GZ6zJsngDw3TliIftOlWlv8XmtCL2G0MRgFLoRjC62UBGGbMrOEeYNDE9vb0+slXBC3kyGA
hGDa4OUr8axWakg3FhMEZLrZh/PogI88r2O2KwMZaKoV/Se0xNw0hm3/6pnWFCYo4faNg8brHQ7j
lpRNltl3U7OUF4CigA/72FMbO3Yn9Dm7ESu7fq/p/8EAO2bUS5d9lzWkom6PPzeyhIMisisqTxBI
zU5DUqO+kl/vNMLxlIO2/w4lzpvidchu8ThkM/4R7v2+462pmQElJAbSordNrZ/gnKNRCREmzBOT
jMwwa454AU4hTR51mr/NyLHSPwdn4dSUl4L0G3AnIs7eLXNRKfTeB4r3DRIX0w+mxNx4Ypn+e2UG
wLZ8syOiq6YPsx4Mw0Rr0NOJqekZPVFvuhQHcDwetMCG37cQcGq0qJmxAvUazF3kIZxKHrb0rKRp
vKJ/EI9ncQvJm9Gr9hYmFA0nuj0cUUknv2ysNxazRnndtgDeIvBNKgNKZWjHUGpUWWxUmTnC3Fn8
Wo5JDcdEhmPMt09YT++ENusZslWC3bD5ISF5FXQ7w6HeSBL+S9A3mq0UyzTM/VOjy0jlsDv//VA4
P3F3AwlM2RC1rwLrBQU8m2YkWen2bFs3FciCjys373xVW8q0LdWdTTyNqJDbLkR9+moLZqXVA9WN
zdUyt9+s6X9X2tMN6/daMvS74YKog/m30S/1Rg3ptoNq1BIPCYy5eSxwstFTegSTc/XeQOuZKEg6
5ASoz+fIdihVwOLSDLaE7/GFYyk/QtzA7pkhcY0f4DNdNgfF9Lpi2sH8xaX6zKlYSwc75WxbSGps
IKlZ2cjCzsvDUdnzWxj20yw00wySfC1lgfEHBtrhru/2DfB5AdyVm1QmNNJQUwFSHnS7hgYUMAzA
7KNheum2s3N7r2gm2mlKW1/rvWkqxf89TU9wOpx8fpb6TTS61VSX29IIe1RdyGziPTHu9daCjtax
zIgAyM/PpydwBlvN0JhvIFwO6SEJhAnfQFcdqMPebDstgBB/vq2wyoYJMc1ruivwDo+p0EooGvFQ
2wYyn9HRK3tvwh0LWxACN6KwOvbtTXdDmg5vYTTZPbwdSkWTdFLqjSiRLujwZj47HInHSm1qldqt
rmV5L0mlrTFAAkLQjUa8hG1+OUiAwsyvxr4P4oLr/cY50aQL26QL06Qb06R4ddSm9j3YDPVETd1a
OOjSM4XYbtRzYdrlciFpElbPskGATXVVmg9iN0W+6lPZc5dvuUsW+G1sT6y78BvZrz8+Z6ILudhs
dNMIGBt3GRJod5xDWlcH4+fYjz+MDcSx36oIw5GIsxmdBa08LLshezBej9QJv0ajlX54gFm2rVbb
/bMSoGZXhOyK31srPwzvLayo2IiyaVXIzFI8PbrHJgsMROCUZEaxD6N41Op9c8Z9okNsP4v3OmVX
tX0xsgwOepXBoL5XJU0Vzs513eiyZ6CgJfeUf/4wNLPHCXMIgm2eK7ERG9S0ZqUz7rXGCZpnwMFl
/YlD6x2W7RUHjyjwAGdY6vDsirl5/+y6U0vPIuTKZb8UKSMYNEWTK1kN7cnz+tZwach/7LkX9ILY
zrJfTmJCH/koO+hOl3CcgrtpruBwCD65Dp0Q4KS1Bt0MPx/R+637D/PVttu2EUTf+RX7KBUSzd3l
7pJ+c+MUcNHYaSLAyOWFpmibiGgqpBTB+Yx8cc/s8iZZTAQUKOoHm5Y49zMzZ9gHMP965g5Y9m67
eUBYI8S9C7IfTlx12fvgGjJr4DOD5hWFLduPbNLswDeTI/viV/ej8+kj7X63z9wm+z6lzZHPjm03
mkvJsvyWjHGiHmNh1JuMrMloYBIeb79klWWnkWWEjTXVgk03YHPyGRAJZnRXbqun7AjA5z2ZpSet
ujPNdu5Hyw7NpMapwI1dtTxwJL+5Kw0xR7Coq4U7WJpKny0WhiF5916M6RmwmOFKwHbhgfRpthQD
IPQkenJbVl/qx3JdA0tJXtkRA1WhU2X8OLLa7INTGEs/0ES5iv8D2R0LOwJNibqou3S36P+rTEHp
LxwXq6CSltkDSEKMAtJnBZ6BaPfFpnbU5NWj/dfmqTH+k0QZaIhcoo6fuv9maI7FrZDL1iLvlkQ7
6d5u71Z5ipRTcZ5tye2srGh8nBBSGPki7EM6zpMW5Xb/jFrndTtT7920aYbpzv95MFJ3UOuHT3+M
NuHYA+10/ApFv9ui/Kdk+/XCO3tVa5bW1qmA1emTJ9FQGEEArBJsLkSMAs6BHSS3yjyuJbnuvi28
R3wAeAJcsW9CJtDFcx3Rd3hXxqL/qvDuvd8XlAvhcsE1qSSr7kkICUsa+78FKXtwZC2wyb2iVIIG
GJdB9wSDPmA1lOpGAPr+7c27xTSkQXnhqMP1wgb+wnYMnvhSjW3TCbs8ZlkGqNueCFVNydiZvsA0
VLSEXuMvHVXvjxqWEuncD9qa3IcNb0SQOY2SR4T7OBg4OjhEmvn9fntXTGnj5XUNOLJllixXWM7n
QA3X1F1zYVQwuUlBBdWMCZLst4O9Ey69gxXbwPy63OT3Dc5p0SRpmq3BS+Bz7EN5w5Zf0A+wzXMg
b66NRrNdZmlvueHLTtzaJxW4NBJaKgKda+wumxOnrZJ5hXCeWVqun61GqeklFxO98Wfy1OrWXUvH
x3EXStBlDKrYj8NuifCutXnThn9MOQpOC594T8WKssqQVdD1VT1r/MdwMWgO8j8wqt+uwmFivUJz
Zuxbbu8ftGIbtvCDSPOhXI/7T5PHzWZ9fna2m9JFsNtNpaUFu7xcbyxL9svqoevnr57BbKEfFyOm
CzxSAlkxcawjbAEgSJBPaeGdXRWcXZbe3wetKds55Z4ED2lGaVgO+xz1uzuwOcJUsT9hAwTngH0Q
oaHelihiJ+4Yj+vtzaNtsUOzSlFlerO2Hj3UHRpx22xWuFKei3VZ59uCAZRvymUGtD+w5GnJbtab
vMi/O7i6SxcdLGy+uZQdzge8wSU+J0V3+SqbsYslqGw6s/pu8ypbZXXNrrPNbkpXC3EW9nlym8PU
j0B/nrpy4GQhCgIzSmt15PprD1BsV4I5Frvd9SVI3ZukrpOUPsVM39a4SoGyi3WVr5icmyGybdEx
PvzAwJxLX4CpSGVTtupRyHQkfCnsUeDKLlzZv3oKpSW4uMSHAV5jKlQWQxhmJuQ0aoioOEHZCnJU
hzNjDMMDhGhHQAvm/u1v7Mm+gNJbcFifqIY8Rg9JGCNBLOAQUchGcdgqBrN00LEP3GCdKIgIiCA7
0Chb7Krel6EpJzc0dSCnx0zFbb5IJCBM8EbEnG5qTy7q5Cj+46YkTX/qBycSn2rqQI4HrSD2jR6x
heGl0bmdDD/V2KGgGA/MwklBBhsXFRYt5rgcyXuEGzJuSnwoE57q4KGgGnEQnWJgjQgxZEil0q2M
HpPZc3Bf5mRkHApGI+UaOhj44bD5eHyCgwcyIjjVwaEg+0eAAQCBEtp8DQplbmRzdHJlYW0NZW5k
b2JqDTIyIDAgb2JqPDwvTGVuZ3RoIDE3OTMvRmlsdGVyL0ZsYXRlRGVjb2RlPj5zdHJlYW0NCkiJ
jJc90hw5CIbz7xRzAllC//kmDvcMG7u29v7Jop5phEDqwQ7squ5nBPSrF/j1+w+E11///vz9898P
uNZefvx1FV6hJtdz77W8aumuNO9zev3z5+cXMjCZUBjT8J/Qe9sx8WaCS4kz1fXBxA2TiMkugPc+
MLBn1yKCYQPmG+wuFsHV4CIm1jJyzXV8jPl8uHJKDIMeZ9UNU08MS0wyzZqYBDuB0ZXa8Q8DsQzs
REhYkfABoz9F2VwZh6UNE+xRriA8gfh2wsgbctVlfHonF6MhRoGYFSI4EkioDlQdq/PI1RFicSgs
n/oNHhXSp6okQwrJrpZDfJIhhaCKYDLg4zm2KY6G78qyFxdRHLVeoEcy1A+Y/MED1qRWJpiSWhkw
JbUy0zeS475RssPQ3v6Ur1ueys2kGZtfvIb5k2SyoQaSKYYaSKYaaiAZEgOEK+nOAyzJNVRwHbcj
uYIXMeQb7Ae1du98/fiZYDKJIbkIh6QkE/YM+DJvrmSeTSK5MLrPsLKIhcJq3Oae46wgj6+i+/XP
h5JIOnxcXgfJZEMdJFP2wgOfpzNLZvYPFPjyYeNsOtGNCmE5PlAzJbQy3aBWwRRvUKtkTs7A8wFM
FYtw+3HhYhjBLH5cwQ2LvsQgwWgohGSSoRCSyYZCSOZkD/gi2VDAR1i8u3UWUsP16tLbw1A3bJjH
aaJGl8PHHiRIisBh4lA7gVRvqJ1kgqF2koGDha+18+go8e5/Ne7TYQOHJNKj7JbKrWC2VG5FLM1C
MpZmIZl2qlyY/ujR0rxH4XyYfvA6nITqsOGumXYaGnjZJDMnSsCRkUPVhfD+RpKB76WWSDSUWjLJ
UGrJnFoEK3XG1QRvZLznmXZoEXzoVMxsEX7t46zWCmrfi6CY/r0Ikun+cOvCNViP1p8bKgTrds8z
nRnCUrY50ikEDr7IKyCZOTpu5mG23yrQ0CAkY9GPOqecrsNavIAFj/e80Ofq0q9+unpWcjBOyxvQ
sIZIxiQIec7sKuCimlZZZtUldK5yDw7doljBBG+YUDREAoz5uqmdH4evl/relHK5hBOBSDDEqKD9
xDpCvN1VM6SnmFzOoopY81HZD4nK9iUQSQIp6zy5hiigYglRMPXxQ/sr7DGw5OwAdQ+dyGYIUUF9
D4FPd39XTPDWELHIKOI8yYNH8QgVcxha+PivoTm1hEt3xxCja6hiqETy6UXNfTxQRc7xxV8uiKay
v6Lx+uFciCz2MwVZrWfiGI2/C4nIx/mWn6nIzs6E69nhTCw9CicTCd56piJJONCv1oS+uz8Ty4BK
ALryANYzFRntZ44yZLrDYNaQIklD0Jxvurb3BJQwJBhPb9AqIQVW64nYZ/FpojsGVgVpkhQE1cUs
uu165ggp0B2LVgVpciponfZw9CIIo0EJJLpekcQDaDYgizO3Jk1Ga6CKTI8fZFpXKq6geNB2bjJb
z1QkqQfejxaSST29y5DoYsZqPVORjdU29AcRYP/B3600aMQ+O8JpXFBQIuWsawV4zDhSdgKaonm3
7LWNxGtUHMtSwm6JnyrRtUqHrrXEqKDpOMv2x8cuDSVDYgqaPuNdq7L4c2VImDfKs5JDpbI/bklM
QaSSfqmdiwR8eDhtesxm2yjFxfCeKZH0qNtIHpNml3InjUgmT3fxePV4jO8qjYVIUySSUK+LstZy
bqAJ1k03ZDh4Uss0IGroIJIlMwUlS2aK4obS5FaEmVGQYV1fQy6HIDEzKoeCqiEzBTWWWRU2MrIL
wy63x5FCcFHsRWqrX6Z0Ga1fN0w04cMdaGkKUkHBkJ2CwJqdIkkm17sssTQ/uF+XTHx2Q+3yjuV7
13D16suSFZgPltzg4bSTSNaKCKjaKyLIdrhtrCKxi6W29EOMNTkYQs4bqPpTNQJ1DA0Z9KEhqz40
ebIRZv7x7bmR2kYlfaz7W+00IWgmG/JSUDH4labq4V4yE0YIb7ov1GJqe9J8uRbc4XEa/N5hFNMs
HUZTgfmwGrJKc2kUH0H8KmgCQK2pwfcQFUPCeO7VGmTi6Is6wPn6UX1xGX8zTygfPhkPUUFlfxKf
kzRUD5eSn4T/xVsC1CNa24fHhysN9f0tWQ8a3zGTXXdmGXxeBI9z81gy4g466OLyt+U4ELtth5Ot
+ZkXiOW0W3caTaZTM5pjfgzrYtrzviK8MyumWCOU4Gn0YLtP9GKN7U/OwW6l4ro1SkHiq/v7zLbC
6NfFF6/swXL4AKcpsMcoyPg1Rujrzgs+HZgZoWbynsHG3PPbojRj1Ycm6/esUAWo+pCJaSdRsbQU
9DBwUF4SCt6alyKnOnBA2N9MGC6LxUgEHdoKa7OaYfNGOH0vBSVrXoo8qGMN8fpFIMasDkUe7YMd
V1zCi5Im1PZdbDlJQf31+l+AAQAWdaT5DQplbmRzdHJlYW0NZW5kb2JqDTIzIDAgb2JqPDwvTGVu
Z3RoIDE2NTEvRmlsdGVyL0ZsYXRlRGVjb2RlPj5zdHJlYW0NCkiJlJe9siQ1DIXz+xQTU4Wx5T85
34SQiAegCIGC9w+Qem+7Zcu6o60NdmtnvlH3OceS/O2fj98+/v0oIcMr8p/Q4QWxhZbHwPLq0ELB
GAu8/vjr45df/wKIr2/fIQiID5RaCtA/oRp6i7GnCaUb6mGAhGqoY4zeThA8lVITUC9hVAvKFjQC
FRpYT1C5oVWIhDVEEqLjCao3xBIJaNSArF46Qe2G+BMpeQ2JHw9OUHdJHkukh50QuiTfoGFUWiVf
oWwlYpV8g9JZiIRkASnR+wmCB4rFlHyD8lkIiFmau0HFITmHJcaGE6oOyRXUHJIrqDtSriArEZi/
eLxhHA0p+Q6VmQi8GskYUnZ4DFZgcsieA52OSBLcEDhkV1B2yK6gmYqUQgVDd0VVh4QKmrEYIfNH
SUqYvngxT7Pgj0j3NiG0oP6cEQV5msUO1WgcYamggmYs6G1lcPGZU4qBMyNFV8wMRYoholQ8BiTx
+rGSp1fwOSWbyoTq+fFWwTfG0yoU1I30rYJvkJUHpDRWCxoexVemRZ/iG+VpEykUauktT8gIhFRc
MZ4uoaByLiQFV4wRB6m3Yqw4SMEVZEwO1jtxpaMMeD60vLUM6uWYT5DVHqRJ/D/k7Nwue3xvkmKs
NEiTFGSkQZqkmPzeJMVYzUGapKCZhuu7Z5MU1Cwof6Gd0R2WK4CCzGmxOEtjKbb0Y86uDJqb5eLs
VshoQ6uzWyErQoO+yW/UTxC4rN2gc4aWka6Yc0OB2GXuNqa+9yiNQBJHmFsvtrceacbaN4RHGsK3
HmnG6ifCIwUNK0HCIw0lq909M0lDRhog4hePZ80X6RKGStOvTqgY4kmXdmZYcZAuKej9INOMOZSE
SwqyMiRdUtCUoYWybQ53k9SQEaLFpQ3K0QqRdKkHpPEH/Qf63c7kaHUU6ZKCjOVYuqQYK3fSJQU5
RpmGqsMlBRkhWlxSkOPiQ1CiyrVNyHGWFOO49+yQZyqpQsm69jz7hmY8DU9B4DJpg4wMbSZtkOOu
lOghaJZBmdD7u5JmHHelHfIshbqQkSBpkmI8/U5Bw2HSDoERh8UkBTmuV6mGRqOsPtD765VmHNer
HXKdJFXIGn/SJQV5+p2CmsMlBRl5WFxSkGMLT6QjjTL4kfvVzuTs2MJVIc+GpwpZ/Q7nXUQxYKRB
eqTqzKjW0Nvq0dzvFORpdwrytLsSgM5fTRNytLudcZ0kVag/Osg9dzNpg2bA1xtjQur1DMEJMtKw
urQx4/x0m0srVM75llclzXjaXQ6VCk9ji6Pb7YjHop2Z+Un0XfZkGDbtYDVckorvjLl1QaDpM3o/
MP1cB2J7zuzOeBoXfUQzqcwdvBjnXAq+M9XTuBSUhOQRDbkVBcZRknorKFsJr2GQ4JhPkKelAD15
jGnuxtWaf6t8G+RZoRTU3/d9xaAhHpYneAqagaDJyEsm3YMs2VeyGTNQPmIK9LVY5t7akreaIh07
ZQyNOhKtuTeTvdUUWd5Wi/RP+skyF4lWndU02TzVrl+cp791f7WNfL9S0Cwu5HV5GG9KFGltSrJa
p/Uhxj4nSfemRJNgnbWlXCSz82wF3RsTTT5zJZTlxNFf3HnoaFMHp+tDJNVvyMjJ9RNLOVpV6dM8
T1z/zMn1ftgClW+01NGu3DD0188weA/778+P3396/U3fic/qTNerTAMf6Kf528QumegzTZFWr5WJ
1KMobQwt86fj4eWJgTHuxYIZ2iUiPK8wbKh9X3sYSvTieZ4PjA80YIUqyUyNryH1+iV4mJ5XkjIw
lFmGdkHrVEB4oLRol+4WeoDyGeJKfFehfDHUeK2bHQaLBWEYPH8uplw3yslUm+Gtpn5/OmgcqZtp
Dmd3plvS4fUW1OmYWccBeuKgoGHpDfdA1dCI51fixysMcYZotrJ0M0Mj2RmawVOQGQcIwHFIJyjb
jwcch3FBnc5SntaO4nq8DaqWt0I9BRmB4MfjC1htF1SXRjfEOpKb+XgbZCaiBySo5Qta5/wYdqUZ
ow2iqnal/viU+JDkCaVzpeVkKAgsn3qoU/L5bXFXKWsF3vxaWr5cjl/mX/68czXMAXlg9MlUowDp
wAqPE3PaRz8L8cs2uKBlISqxn9+bK+HzdBuEBgT1OagKGudXyjSz+OnwwKRohaZdY/9Th0KhAZiQ
0RGW06MgsYaifDwoT9IUlA2I3umeyIr5TMPrfwEGAGIdpKwNCmVuZHN0cmVhbQ1lbmRvYmoNMjQg
MCBvYmo8PC9MZW5ndGggMTY0Mi9GaWx0ZXIvRmxhdGVEZWNvZGU+PnN0cmVhbQ0KSImUlzuSbCcM
QPNZxawAgwAJcicOvQbHr1zef2Jxey4g8bFck/X0adCREOKfr+QifPv250L5hoquhFqJvrFEB8V7
qN9//fr67Y9fKeTv3//++vPrn6/g6gRFDw4aFHYQvlByZWJCdoFqRdgxtGcgXZiyZ2J2mfeWy46p
PSDvPP9yrROZoqv82Q4Ev12s2cPISHqY4L2P1JnwMuDSUZ5iwCJPMfFlsqOsYoI4p1eBaQJRKgz8
QxR3UJ4UZr0cK2xW83Y5HMs1uz5IkYl/DJsU4GLzPqUO0n+LXJgyL3YwuUC9PNBBkhaPu4t+QDQf
kpiGiwXqtRGC81xBtRwsLiScs90sQguuPCC13+1ctEiUSDonTHmUXD4YYY3H7fXiIKckIm8P8wah
yWE78sdK1GAZKoo6zZ6/x2ehMU9xlw7VrT+odbQbzSS/X0hJV1AwVa6CYK8PuHx4oRJ3TBwM6l7I
3jnkStvFkl28IvPJfJ73GVux5Q6hxbxiyGReQbaeoaBeF+VpmrL7fioPN1z2E4fSfLuZCu2gYDev
yF4g0UWU5scWoR1y6EwvEHn9N/PY0go7KJnMKyibzCsIDwaFdcXQYFC3XWlegcVuXpF1mC9Jmm+n
Az+QZ6oz6If5pGq+8EqUNkzYZ1iJlwyYvEsmXhQCnGPqhVFd0AIju+FPMG64bDcvQTyLj6/EwP9i
pg8pSHuoWWz3NJUdZGkcC1QvPtjjcYvkB4jSIb15Xhhz41jIaSKVDweO7W0CwSHyqNeHFIomiwpK
JosKykPG031VNZ63iBdQqlSgeexYyP2LpZn070XG5537dupFTHWvP/rwXNo/UiRUvMmkgsLd5HGL
pVdIe1QpjXlkW1HRrlGRhzqBylpb38cHityFU5/5yumGYY/hfcEtEJo8KohmHXqukiIVWYRINXBL
mYqsdpmSrH4mQdrE9xEYPh2qTxPVMqMuENzCgzAnT5FxIpc3J4uJ/FnJO9I8qi7kfO3Uqh9aPB63
UYFB7yo3zHHtVEvRLBBZ3SxksbpZyHpIffNS99FlP+qFp3F1+uCV6R1hC+GFLOWiGbjFxUZ6cWpw
PHRhaUeTDAmlKayKMqzwPkB5I5yaQJ2yjK0LhJN2n45BKYpsUSmqiLBkWUHlNL9vPO+eNKdOVlNo
EgreFpqiwhwarVfxeb1RI1HNyXyy23r1oYDHwthLOERTaAqaG0kbYXQ5jnagwGyPTpE4RSffX3wV
MJU//cCzlFg7RaboFLREV07RKbDao1PkKE2ebJb+Gp/P2nuA+MnDlZvwJcEw3SyQNX/ramCMcCXD
FGErXH343lcZk22U41vuJQ0VukAiQtHOObq3M69LWctzJdMUXqE1ge+gz2TukOFynL8fplmP8BjT
+P1eVV608QjkoF2h6uv9sKjpGkqfCsX353JfL1t4BgV+2Akojq6Yn1YtRYErP+2bocgdwPf2HQ33
5gIJZZt7c9KmVjtVnXCnGDjkR7pQ0KgcdEUdjBhLb90rmSeVRfWpphKHlcBHLowk2ApPQv9DpVqt
3MBZp+LIpFNBp6tampRQ8reOn/g4/AycKxl0DlQ5p3ej5Rk5oF9oCQw50JCpAywrXRM3/C9cNPhf
oHxZbM7BAo4LfjPicg6wpWUnJdF0giJI/7FdKx8rxKcL+pWbism/hMxnQIPZW3OgdllvOkUe1ILB
nAcFXh+mKTvPJG5jjFMeaBliYFwixbXpO/ZOlpMpFwq6VZrMhQLRmgvFkTkXCrw1QJkLBfbso4P5
BZFwbiwSwtHMOJaWB5rTEFxtCQwPmfhCSf0FgZYbdoHAnAYFntqLSIFibudPpkCB9rakQDSlQEGk
U1BlCqjZLA/ZQu1HCG1NSTL1fCcE7n6YV4a8xb1Erg1FqJfcrT6keclFk3jJpMn7s1iR3ttH9AnO
f/79ktkkXkFoMq+g01Qj1Cvm2kCEewVerw8hX4LFm+wraAxDP4lR+hNLKe0VS660m6WPUcUyDC3Q
sYFM+hfoOEEN/QtzbR6T/gW83TSz/gUkg/4FKpN+CmvjH/FRu9b7AFVOM7O0L6F6bCHCvoKCxb5i
rg1E2FdgNNtXYDLZV1Ce7YOcm5r9PjeRy/zvAVoeY5o5NhEhXzLF4l4i1ulTcjyPmM1LLpjES2bM
q/w4q7rqvSvskNIDRn67AXUymsQr6PICm8wP6PtfAQYAZDuvJw0KZW5kc3RyZWFtDWVuZG9iag0y
NSAwIG9iajw8L0xlbmd0aCAxNDkzL0ZpbHRlci9GbGF0ZURlY29kZT4+c3RyZWFtDQpIiYyXOZIe
NwxGc51iTkCRBNfciUOfwbHK5fsnBv9xcwGI1iclqlG/IfsBjeXnn7+Kz19//PPjrx///siuli8/
/rrQvihWF6n38lVqdZS8j/Xr718/fg6mbEzu/GfjKLrxk9JvYH0D2+dn9Qq2Bywupg1KxSXztP5A
obtS+bG2yNi9K+NH8UOG4j2lhwx+3TNuEIXsAv+icoFSj5bJ4EJgKN9OMqFdv2CCwZzqBUT7K3nv
ww72lxsmSL2AZlZFfric2jMflRtTxXW+SYqTKoB2BVVAu4La77Urpr8lL9k3jDObkmun9VRHUl6Q
AEhXUDykc4zjKZ7Gm32/2siA1CdJkHgBJUi8gIByo5jXckMvN6ym+DIqDd0YpNIoqG/mC79Gr6f5
sI7jPOL0f0hCKo2CrAJwmhcQUGkUQ1aloZfbpWWd4m7QO78+fQFlSLuAZmL8/+J7ZsTWXZ+fV0qf
z+EBK2RdQGbNOKwLqCPWTyZ5yLqAsIohoLgJLKe70S9z/UCxjHbxMFitOBmsVJwMVClOpGwO6LVQ
nFyF3J1M29R9ilI9/ZX1Xp6rRZhjSeqQwBPKVk6cBgVk1oldoWDiu0Pid23XwwiSKKCZGDE6L0c0
tpj4CnUIya6PzJ0TRs6ARQUVwKKCzAFjWVSM1UV2gwrqgEEJFb8ZzFnXwPjM1Hz7yDPa/PhLgAwK
CBlyFWS1kcOgYKyxkw3mkRTtBiFdREGri5DzsnmzwZGX+fuOmcsnzbZfkDaiIKSNKAhoI5Kpfsmo
0TQoIKSNKCi+1sLm2iDpQxIXUa7TDzkzw7t0GORftLQLKEHaBWS2k0O7gMx6sWsXTIW0CwiZOhXU
7/KG8cqvxLEc0FDS6YHaqhdiM9vmJQWFdVIQYeqrQgsoQmESkFkqjjAJyBwv9jAJJtthsuUVKEwC
qkteL2eYVkLMp2cmBJ4hLh1xxmgS3QpO3JQ9T3dk4VhPI5vGehpYMdbDM9L8n5b/+bDVDQ7x8+ls
Gx/dN49b80rIbcDPUaQXULwCkS6gIKQLKGjvAqLVD8eJwUYarN6brmdpVgzSCRQUbfObC15xfMgT
Iti8AGdWBF5sdvN+v6KAsv25JOugAoVYQObceIRYQM04icM7Il7LDepIeE8meCi8Agp34bFV1xeU
uE3FOKG4h9cMrYBWTrgez9AGLiVc8i9QskNbxhhMNwhZJBSELBIKOgqFH8vkEd86TrvKaEZ802c2
5QZzYZBlQkLR2/Ftoyh/nzQuH/uEAhRfAa2R0e2384xwpEq4MWSHt432Um4QMiwqCBkWFWQVCQ6t
/U7VDO1c3BSDDIsK6nZoy/qgAqclzXJOfgttUIP9Hl4BBjO8W5YLxugdI7yRj871BhEU3gNKCVli
1UkzJ7jp7UzbC5Jg0orup7F1M8QCRAZNBdV7zRwhTk8CEv8XLxFpQg0MsQJnQnGXsWIsoYRMnwpC
hlAFxXf16VlbFEiAegUlW31cMlhan19kyrD5kyuQ+JNBZlTJICOqZPq79WJwGZlGJHOvMUO5fyYl
cjl/5smHidJ5t5wLkNbXT/GUns3TkN6jIKT3KKi8e69P/VRghcQLqBnmi+vPCkKOxogzR8fcYfMn
WLxtfkt3AQXIvICQtqAgejdvvhay0SooI+LHRhbmTFcKLF6AFRIvIGt/OcULqEPiT6j6N/HZ0TMR
KhBZbBV0n1eFec/QQggWf3IJ8n4yyBIjGWSHkUx9l56Zy7f7ISOrZPrv6zsP/rygxjkCNTWwGs4V
GADpCoqAdQURoF1Br4Nkdo1/VtMNzIB4Ba2SYU8z0RXeHWmOQK3C6gXYIPUC6pD6E+oeUi+g8Ka+
OD8m63oDI6ReQGSrnzM8fw/cFtL8UnqC1Qsw2+rz+sYEZO25p3oBVUi9gNpSL19rqE9P5VVgh9Qf
EP97qU+i4JRnw/teRVubUJDqjSFegfeGIpJeMHS/IYXvJ3O9QcgQqiBkCFVQeQ/XllEL/PpPgAEA
Fq63Xg0KZW5kc3RyZWFtDWVuZG9iag0yNiAwIG9iajw8L0xlbmd0aCAxNTA5L0ZpbHRlci9GbGF0
ZURlY29kZT4+c3RyZWFtDQpIiZSXPXLkOAyFc5+iT8DhP8h8kwnnDBu7pub+yYLSiCQAQcKWA3e5
9ZnkexDw+OPnd/Pw+ef316+vP1/Vxfzx48eF9km5utx7r/1TIbqIH1v7/Pv99WNA7YKCyxsUG7gW
egc4oIAfe5lQn1B345sOO9ldB1zjBgz+AqPbd+i7A0TqLRMuxrvcNihE1xJC9Q6KF1RcJFBxYawU
76C0IKgbFMPxZC13UL4gOKXoG5jqw7mKyS4GVd2ufkHB9ey9jxOCza7a7q0SUHu3SjBdt6oWrJJ0
A0VvsEpAwWCVgOKyKlKXOu6uhjsmGVwSUF469Lrr3fYjQfU+TKaYTKLMVg09UpO2E1EG1t6C7hFl
mskiynSTQ4RJfokNxCFw6WpGnAkmgygTdX8SalDOvZWGDEwo7QbB6KKaSQzM9+9sCvgLG1jLd1Ax
Sc6gatKcQbMgstsXiviSjPZ6hzTdp01zBnWTURTKXneq4O7gFPx4+/KEwmpdTTWJMbMkAp6J9fHY
8R9hXbRyR6b7LQ57t3MxKJvsZVAx2cugqqxE/GUM6P5WdXfN5C+DlIkx/IXxxp8dLEbv02yv5T5F
UHsZEh7tTc6vYmKkJUkIyJIkBERqwo9+pbjFOC1IpPZwrGpyi0HK7BhutQGds8Ojx/i2X9B9kKBu
MaS/uBVXaVCy2sIEg2xhgkFbXUBhuY+4xTgtUKBb+rGyyS0GFc2t7jxqUcb2vEPNPDaJC6qvbgkE
XtxKV2kIst3vMIVwaAr9DuoGizkE3mCxgNS6WPYKJm5OJX4daLoWYAmaAsrLLT7p4hLwSCtpQitp
tnOPjfoFKqnNEio9g8AkPYOaRXrGzMLILpGplfTdNa0w0KsyCh7uIEvmFFBU36w8uvS5u3nTa+nF
pa2SFmSJFfvz5amJYfsfd09gjBoyd2vW40q8pKasxzXjqR/reUuq3J7vXn9j6qrGhHPPzxTaw4sX
s3EL0pIeBJTMrjAwW6yhTANlh9QgtpBWA+jS1j0YpOUUahWDQPcLlg4BJ19YJrcXv2YsEuSWR2mY
J34RqHvlksK8YtCqKXorJF4xhlQTS4jULwZqdxTqF4O0eyv1i0FF9+tvgKj4CadYjJOpj3atu5ck
4d0uCbV3uyT0bpdggn94jze75GJaFaJd/e+skKtpO9zsktAaSuc0ptkNf43qSAcJWHGxTzK9dzYJ
ZVtnk2B57WySqWb5GaglFio/g9p7d+NQy9PoiHFhVD5Q+dM423k49M2nqy/2aLjoCCh0s/xstfck
LJmnCxKVn4HJJD+DDDckCZVN/lCp9AXfhnK2q4wjCV+pizKkYAmBWXoGvidhyTz5TKWnYHpIw5v0
DDKkYQnN6gj9DMqNyl/Hn87ljpEwQVvf2Rkoxpgr1jJ1HYo8dTgqPeUeEtWmPGXAJDxl2q470xyv
UB2vlAPy5bDkorpJdArlp/FHVWegqdswxt5tGGjrNgyydRsGlU36Y9SSWRuOx+sQpGF08h77/kVa
Oo6ArB1HgIaOIxhrx+FgsXQcAVk6joBWx8HQK6JO2M4G4waSJmjpOAKyJh0BGnqOYKxJR4CWpCMg
S9IRUN/UlxkfIys60tJBFpwUM6FWS9DhTDCLT7lo0Z4iySw95R7nRD+yeC03XDGJTxlyv8LrGn5F
tB/rw3m4hF/HGZAqmMRnUDOrz8BukZ8yYL1jCVAbMlR8BkWT+gyaJRKALDWkh7G/dlABw2maAQmy
SXoK/Y+ez1bT4geRnjFPqYpKT0Fjz2er2boOWylu0kfg96vg+hi5AUlwHadFnu8MWBKPgKzyc7Bp
imzyC+apye3yC1Drcrv8AkoG+QU0azhUByLxRBdwuZYPEkGfZ0xtxSQ/g7SYhNJnGBPnhtEmIFGe
MU8NjirPQK3BUeUp1L1JeQaFTfnxlQ9U+YQtDs5SrDgryoxJPZqUZ5AWkYjyjMkW5RljbTkCtFyv
BGS5XwmobcoPlWnQiTuZcU7UGZG6reUQKKCzFuk5ZLhh7dDnPwEGALnDsaUNCmVuZHN0cmVhbQ1l
bmRvYmoNMjcgMCBvYmo8PC9MZW5ndGggMTg1Mi9GaWx0ZXIvRmxhdGVEZWNvZGU+PnN0cmVhbQ0K
SImclzvWHCcQhfN/FbMCxLMKcicKHXkBPg5lH3v/gS890xQU0MI+SqRpfRRcbj349v2Hs9a/fvnr
69evv7+S8fll6x/j8iuEYEIqJacXEZsYraXw+v3H17eLCkIx9VQ2JZTCfknFmyLjY0dFMrGUQmVJ
pZtyyWQsXrpt+uINMdB3QE/WshOUNofDSm5P8YbyzkSu4VdQ3iji8V+xaVpC5Uh8RTnbyVj1KOMF
MEguS9IdXYCmfHcBAd+sGy8gy1ZtxlcWNBxdgKZiT43x6iVQPWBYkqm7haSkGW5Cg80pzpnkt1eh
MT4SVFO5F1Rt05dgbE2hajMyBcfHyg3dOaYXdKK87U5ntWV6RWfUnQgzY/5AmJlqdnHR5DyK4h32
6C6MPSqQFyweiaKpdC6KRukJhTBJLlCjJ46ZqdwJc8VTjqm/0XuvCeUzFEHPHKOo8B8co1F3Lo5G
z1yjKXFNMMWPwiQcMdGF1dIVSbAz12hqco3qELVD0Trg5BpV8lkcrtEz12gqPwjTugThFzRZycJw
5piBSoXPdVHx4mSYvS4atUe6DBTJyANZ6rAx9rMgEwwZfLQkrTCe9LOZ8v0B41YXjcVzXTSajnTR
lBjUm0K9KNE4BKNa6zGEoThRFmw3L/WiKIqkczpr0tSqvUGrKykv45VTXWY0H+iityq9DLLUAXAs
vtF4/JL4Igl2YsnA5I6kGaiY3bk0Ot7WaZAl3z1ixk7SaKbCT3S5h+VkIgqTl3aWTkrvTKWf6OKq
FdYoPaEhGlu3ykv0pPTOlJReP4rSGud7tvXSx9JJ3Z0osueqaPTRaKMqGj3p1DMVOnsmNzumFUOc
GLUpyMxMZ5YZKJJd4oA2j7oEUByXsWjA1AMEuvi7d87oSeGdttniIUljr0iSXI/o4Lb2hBaqWQwj
YT+YWy8PiJk6KdYzVXpFeDZZdQ/xCmX7hELMeHfbGT15rs6U36vZciEaRjFL0vs4rKmqZnt5zNSJ
K2eqmaSYK+vyVkxN0gMJLelu0jN5UsZmKosqgUYtW/5Ek1D8kqQ5lyMtFZXtkZaacqIIjTJyLSZL
xq8ZCMh3K5+hcCSgpuJewO6aA4oMSWfNaU0pATVFRwJqikUM5+bMLvgthyWZH0hoWT7tfwbLkZSK
KnZd76qUctWoBTWXG+QE6iWx1nCVJC8hfySkpppBsiH97PXBWPzC603GBzIg5j0yzORJu5kp2ivZ
XbcFJhONPPB0uxmkVFA+UlJB5VlIv4mGpvqsY7iniwk8azQK8jsVSe66FkBALFQ4kHGmTvrMTCXR
w9EoYqzFxy0p2lBQMN3TyEz1/UVrDxlpv8u87hZVRy+KEApriEKVIx0V5YYeowY7aBmgSk5LslmE
r7NoU1a/5bgk/QMJTfPdR2cyyG6ZRj3zfqdxr2d36xHHj+Jml9aU0lNTdKynJllU8aOUuXY4XkJZ
oKvhDFIi7e6OOpNlJyXLsDxR3u6l7C4cGtlYhHJHUmrqoekk2aGmwlbGcheuGYqSq+xHCf2nk85Q
6hTUb0Wo2OaSmeyeN+MMRP1dQ22bSCg+UlFTDw2nU1FT5aF4+djbWJHBPpCQM0kj0KR7SB3omer0
tFQm+L2e7dIxuKHMUhAqrKlBz5mKUmaVnHxf+AylzSVAygdqN75CxnLXrZnavWchYbUpr8VoNvEm
515Cln6KFwQqKzuhypGEiop2LaFPxt53PEObuTWwCXfKzJDfn6pZGM9LuM1J/41hTalTaWrTZeqx
2it0pnZdJrBMCDNF+3O1pPYGV2y99MHIR+fSVHOGNWWYmbjVxhkqGygU4+8X5UQlKxuM46m6LPFI
/iAtKbmjU2nKb0PlWjHCBVlsMEjdTmEJqUgaiptI+XJ7qvo5k2HcKBUtpZ9HmqHmCmeKH0P5O/Od
IXgpdaLzSSgN5X2oWA3oLyrhfknSMZU1pWIpiqxQUSnYEsth5gWVhXJHsTTl97H49q0zKGGWRXgK
a0rF0lTcxyq1DgKq2YMUEd9SOgg1U7ROR6SicdUZ4aIYl+zFucRHsTS1qRc1VntvWoMN2iAVjXYF
Y4ylKLb7WO1lZk3EJUcxL7ujWJryO8sXQ7BG9hflcclJzMsba1SqvXOssThYEg057nd4j/QJC0B5
EkNx2lOfSg2IISFL4+fOGk6VzwgJc7ioBDHET/xxxnUuwgzzQq9COXohx9GdCQPa658/vn57/Vn/
g8O/E7tPca5vrkwwZwVv4bhGQLvu9pXnEMFAmKMQzDmjuQ8h8JixoU9ALlMIQtf1/zsEaF8wSolQ
2c4hXBdiWt/b+FkfE0B9gw7ru6vglSTrO1kf0WuJwte6ALozpp9YL1xaU4A5vaRPbpbOqAPYN70P
V99K4VopAGrRZ76ZOwWYBkbh+nzKSJBXdHX6bMfLaC51c+/EqR+vvb4qaD9PgtTafAsQ5Xj1K7f3
RAzv9egVM19/RQVhrMtjn8+fnHj9K8AAcWaJdw0KZW5kc3RyZWFtDWVuZG9iag0yOCAwIG9iajw8
L0xlbmd0aCAyNTc1L0ZpbHRlci9GbGF0ZURlY29kZS9OIDMvQWx0ZXJuYXRlL0RldmljZVJHQj4+
c3RyZWFtDQpIiZyWeVRTdxbHf2/JnpCVsMNjDVuAsAaQNWxhkR0EUQhJCAESQkjYBUFEBRRFRISq
lTLWbXRGT0WdLq5jrQ7WferSA/Uw6ug4tBbXjp0XOEedTmem0+8f7/c593fv793fvfed8wCgJ6Wq
tdUwCwCN1qDPSozFFhUUYqQJAAMKIAIRADJ5rS4tOyEH4JLGS7Ba3An8i55eB5BpvSJMysAw8P+J
LdfpDQBAGTgHKJS1cpw7ca6qN+hM9hmceaWVJoZRE+vxBHG2NLFqnr3nfOY52sQKjVaBsylnnUKj
MPFpnFfXGZU4I6k4d9WplfU4X8XZpcqoUeP83BSrUcpqAUDpJrtBKS/H2Q9nuj4nS4LzAgDIdNU7
XPoOG5QNBtOlJNW6Rr1aVW7A3OUemCg0VIwlKeurlAaDMEMmr5TpFZikWqOTaRsBmL/znDim2mJ4
kYNFocHBQn8f0TuF+q+bv1Cm3s7Tk8y5nkH8C29tP+dXPQqAeBavzfq3ttItAIyvBMDy5luby/sA
MPG+Hb74zn34pnkpNxh0Yb6+9fX1Pmql3MdU0Df6nw6/QO+8z8d03JvyYHHKMpmxyoCZ6iavrqo2
6rFanUyuxIQ/HeJfHfjzeXhnKcuUeqUWj8jDp0ytVeHt1irUBnW1FlNr/1MTf2XYTzQ/17i4Y68B
r9gHsC7yAPK3CwDl0gBStA3fgd70LZWSBzLwNd/h3vzczwn691PhPtOjVq2ai5Nk5WByo75ufs/0
WQICoAIm4AErYA+cgTsQAn8QAsJBNIgHySAd5IACsBTIQTnQAD2oBy2gHXSBHrAebALDYDsYA7vB
fnAQjIOPwQnwR3AefAmugVtgEkyDh2AGPAWvIAgiQQyIC1lBDpAr5AX5Q2IoEoqHUqEsqAAqgVSQ
FjJCLdAKqAfqh4ahHdBu6PfQUegEdA66BH0FTUEPoO+glzAC02EebAe7wb6wGI6BU+AceAmsgmvg
JrgTXgcPwaPwPvgwfAI+D1+DJ+GH8CwCEBrCRxwRISJGJEg6UoiUIXqkFelGBpFRZD9yDDmLXEEm
kUfIC5SIclEMFaLhaBKai8rRGrQV7UWH0V3oYfQ0egWdQmfQ1wQGwZbgRQgjSAmLCCpCPaGLMEjY
SfiIcIZwjTBNeEokEvlEATGEmEQsIFYQm4m9xK3EA8TjxEvEu8RZEolkRfIiRZDSSTKSgdRF2kLa
R/qMdJk0TXpOppEdyP7kBHIhWUvuIA+S95A/JV8m3yO/orAorpQwSjpFQWmk9FHGKMcoFynTlFdU
NlVAjaDmUCuo7dQh6n7qGept6hMajeZEC6Vl0tS05bQh2u9on9OmaC/oHLonXUIvohvp6+gf0o/T
v6I/YTAYboxoRiHDwFjH2M04xfia8dyMa+ZjJjVTmLWZjZgdNrts9phJYboyY5hLmU3MQeYh5kXm
IxaF5caSsGSsVtYI6yjrBmuWzWWL2OlsDbuXvYd9jn2fQ+K4ceI5Ck4n5wPOKc5dLsJ15kq4cu4K
7hj3DHeaR+QJeFJeBa+H91veBG/GnGMeaJ5n3mA+Yv6J+SQf4bvxpfwqfh//IP86/6WFnUWMhdJi
jcV+i8sWzyxtLKMtlZbdlgcsr1m+tMKs4q0qrTZYjVvdsUatPa0zreutt1mfsX5kw7MJt5HbdNsc
tLlpC9t62mbZNtt+YHvBdtbO3i7RTme3xe6U3SN7vn20fYX9gP2n9g8cuA6RDmqHAYfPHP6KmWMx
WBU2hJ3GZhxtHZMcjY47HCccXzkJnHKdOpwOON1xpjqLncucB5xPOs+4OLikubS47HW56UpxFbuW
u252Pev6zE3glu+2ym3c7b7AUiAVNAn2Cm67M9yj3GvcR92vehA9xB6VHls9vvSEPYM8yz1HPC96
wV7BXmqvrV6XvAneod5a71HvG0K6MEZYJ9wrnPLh+6T6dPiM+zz2dfEt9N3ge9b3tV+QX5XfmN8t
EUeULOoQHRN95+/pL/cf8b8awAhICGgLOBLwbaBXoDJwW+Cfg7hBaUGrgk4G/SM4JFgfvD/4QYhL
SEnIeyE3xDxxhrhX/HkoITQ2tC3049AXYcFhhrCDYX8PF4ZXhu8Jv79AsEC5YGzB3QinCFnEjojJ
SCyyJPL9yMkoxyhZ1GjUN9HO0YrondH3YjxiKmL2xTyO9YvVx34U+0wSJlkmOR6HxCXGdcdNxHPi
c+OH479OcEpQJexNmEkMSmxOPJ5ESEpJ2pB0Q2onlUt3S2eSQ5KXJZ9OoadkpwynfJPqmapPPZYG
pyWnbUy7vdB1oXbheDpIl6ZvTL+TIcioyfhDJjEzI3Mk8y9ZoqyWrLPZ3Ozi7D3ZT3Nic/pybuW6
5xpzT+Yx84ryduc9y4/L78+fXOS7aNmi8wXWBeqCI4WkwrzCnYWzi+MXb1o8XRRU1FV0fYlgScOS
c0utl1Yt/aSYWSwrPlRCKMkv2VPygyxdNiqbLZWWvlc6I5fIN8sfKqIVA4oHyghlv/JeWURZf9l9
VYRqo+pBeVT5YPkjtUQ9rP62Iqlie8WzyvTKDyt/rMqvOqAha0o0R7UcbaX2dLV9dUP1JZ2Xrks3
WRNWs6lmRp+i31kL1S6pPWLg4T9TF4zuxpXGqbrIupG65/V59Yca2A3ahguNno1rGu81JTT9phlt
ljefbHFsaW+ZWhazbEcr1FraerLNua2zbXp54vJd7dT2yvY/dfh19Hd8vyJ/xbFOu87lnXdXJq7c
22XWpe+6sSp81fbV6Gr16ok1AWu2rHndrej+osevZ7Dnh1557xdrRWuH1v64rmzdRF9w37b1xPXa
9dc3RG3Y1c/ub+q/uzFt4+EBbKB74PtNxZvODQYObt9M3WzcPDmU+k8ApAFb/pi4mSSZkJn8mmia
1ZtCm6+cHJyJnPedZJ3SnkCerp8dn4uf+qBpoNihR6G2oiailqMGo3aj5qRWpMelOKWpphqmi6b9
p26n4KhSqMSpN6mpqhyqj6sCq3Wr6axcrNCtRK24ri2uoa8Wr4uwALB1sOqxYLHWskuywrM4s660
JbSctRO1irYBtnm28Ldot+C4WbjRuUq5wro7urW7LrunvCG8m70VvY++Cr6Evv+/er/1wHDA7MFn
wePCX8Lbw1jD1MRRxM7FS8XIxkbGw8dBx7/IPci8yTrJuco4yrfLNsu2zDXMtc01zbXONs62zzfP
uNA50LrRPNG+0j/SwdNE08bUSdTL1U7V0dZV1tjXXNfg2GTY6Nls2fHadtr724DcBdyK3RDdlt4c
3qLfKd+v4DbgveFE4cziU+Lb42Pj6+Rz5PzlhOYN5pbnH+ep6DLovOlG6dDqW+rl63Dr++yG7RHt
nO4o7rTvQO/M8Fjw5fFy8f/yjPMZ86f0NPTC9VD13vZt9vv3ivgZ+Kj5OPnH+lf65/t3/Af8mP0p
/br+S/7c/23//wIMAPeE8/sKDQplbmRzdHJlYW0NZW5kb2JqDTI5IDAgb2JqPDwvTGVuZ3RoIDIy
Ni9GaWx0ZXIvRmxhdGVEZWNvZGU+PnN0cmVhbQ0KSIkKXBEYuDwwYHmA/zJ/v6V+vot9fZf4ei/y
9l/q77XQy2exj9cCrz2B8WeFHM4wGDu2OSo4KximGjIwMCi5KAkqCQorCwspC4mriiu6KBpWNzlO
b3KcVCysHOfWOFsvYTaD7Gxhh24G2VmOk8sCV4YFrk0Tt5utFNfq2Jfp2BlpWJSnFFUnbN/l2Bbo
OK3esKzCsCBLKbJWySXUMDVIz0tPw10jcEtT4IZix750w6oGt/wSPa8Sx4l5SoGTYhd3xM6bKGw4
PXBzvaiqaOCmqsCVoQyjYBSQCAACDAAxXUYtCg0KZW5kc3RyZWFtDWVuZG9iag0zMCAwIG9iajw8
L0xlbmd0aCAzNzAvRmlsdGVyL0ZsYXRlRGVjb2RlPj5zdHJlYW0NCkiJOsPA8P///6uKilclJa/I
yF7T1LgiIHSeg+N+Ztaz4qJLosLnBAQuSUpdk5O96+z0NCfnXnjYn2tX/jx68v/H9/9fPn87d+7/
61dfN6y/FxT4rKb6x+2bX1Yuv25ldYmb99W0mT+uX////v2Pe/ePMjC8W7DoQUrSDSfnX8+f/711
80VF+RU97W/79v5+9frr1i13La2uGxk+b+/4++nru5XLvxw8+MDf956b8/upkx/Hx9339Pp64tQ9
N/frZqbfjx65pqn479nTjytWvmlufNHTcz8q6t/9ex+WLH3W0vI4IvLLrq3v16+77Wj7cceuF5Mn
v58z59PevTdc3W8bG93S0Hze0/zzyfUf7x697eu5KiT6+++nNyvmv9++7dfXVzf9/N/MmvK6vv7j
0V1fzh//+ejJBSWlz5ePfLtx7u2k/u+bNjxLTv24Z9OvJw+eN9Q/TE99OWvmDS/Pi7ra1zQNGUbB
0AQAAQYAikzTogoNCmVuZHN0cmVhbQ1lbmRvYmoNMzEgMCBvYmo8PC9MZW5ndGggNTM5L0ZpbHRl
ci9GbGF0ZURlY29kZT4+c3RyZWFtDQpIidTB/S/UAQDA4e/uTOlsSqu1fqg1k93sanLc1V2KVabW
qEypNoR5S2oqLzNJybyWsEtFHZc1mUJeqlESIqt5ada8ZWJkF45OXrpPf0fPAxh+09pFSxcfvjA+
xZ9F2nuY1LO8Qnsv377T1o25ArEjYidE9mTrGJnAah9iB0RyRDIKXzAzh/V+TsUjOCLsRHBA2E5m
CRZ7EGQIUh5UYLkX7xgkaoRdCPY8fI5PLIItEhUSB3KfMjrByDiT02hfMm2g+TPD4/yapbufTC1h
tzh3nfBUcp5gMtEzQEUjcbm8akNkR/J9om8jkrK0TGQ6axRYKDgdx+AYK39RByJ2pq4FwYZr94jK
IjAZmyN09aP0o76VpAIuZeMTw46TzM5jAqU/WTpUAax1weMCAUm4hSI/S30L8fm4hyM9QWUTV3Kw
9cTcibI3uAQRkUb1e/SzvO1k3ojMh60eJGqYmkHui9SLxk+sU2OpZOgHq3Zjpaazj4VFvKLZfIh0
Lb2DjP3kYBgKfxaXmDNSUE7fMME3KKnlYhavP2J3HFUg690wc8Y1hE3ulDeQV0ZNM3F5eESSpmXb
URLzySjmfBobDpD6CF0tRVUkaCiq5HAEV+9iXKC4ho2uhKRwp5Rjl6lqoqEDhR+aZ0xNI2xhYJSO
Xh5XY+3CmQSk3qiDCE7h6xBRGZTWYeeJbyx6A2ZOrFYSepN3nQj/iX8CDACJyZLQCg0KZW5kc3Ry
ZWFtDWVuZG9iag0zMiAwIG9iajw8L0xlbmd0aCAxNTg3NC9GaWx0ZXIvRmxhdGVEZWNvZGUvTGVu
Z3RoMSAyNjM3Nj4+c3RyZWFtDQpIidxWeVQURxqvOYEZUXgMhy5HC0EEhqEbGC7x4D4WBQFHgq4y
MzTQOjM9TDeHMQozmyAEVFQ8UIiIBxrURYOBuJqYEBUJEBAUYiJmNUZNvOMtaqohiK6rf+x7m923
3a9e93fW76vv110FWACA0aAAcEBqWGJ05P2DDqeh5ioAliAu0dML/2YBAd+hDGRKtVxrYt1XAMD8
WABYPcocGgnJj7sOgFUYlE+mazPUP9lktQBgYwMAT5KhWpTeeCu2FgD3TgAksZm4PO3omnU7AUiH
MvDNhArT08bOANhFQfmtTDWd1zy7C+a2UwEgmKsilfJ4at4KAFJsYT5ULc/T8rbxS2F8PfRHNHI1
3lY2UAWAfBq0k1qSomEd8JIjjF2rw7WpPXM+AcAFYuLyoY41eDNPIGJqEoHBS/QjahD9wDdxK4wq
vG/KMmJXG0RdUNXOZrGw0egovvGQhc3jATSVL3Dns7gsgx+bxa1OQONR8Qsa2xr7AlsQNHjHAQWg
AAlUAAc0HFOYG0Vezsc122eeWSyrKXGqjImpn6Be5VltMFuFGtjTUANrF9uMc3yl33erJ54L+vu4
PYZHGWao6XOcLDaEI8fM0TF8ziyukYVxtIbGdRqcxqxRS0YlsBgtw3VEIpGhESPRGqUE80YxxiC0
cBs2IKGkWo3rlIRchSSS6XSuXIcj8dkKFUFl4joKCQ1G7a1NA3xRHzQAHbxSrE2hgKF+Xt7SAGlA
yh8BQb/5xbpZPMDRLweovpit14PmbgJPYJUn1U08prD5OGnW0bBl4TGTvlza193bUlC4vG/ULavK
toW7XPevzKFWtxxV7Ai6Zs/LvmkBVKLpPRvKjD4jKH2TYgZm3zVwYtQvS8o+39sQOfMq2ZEmZZ9e
ksHLPb/y25m9j9ePPTSlN1d/LPTs7bPnWrf+teTr4C8mO0ZF7RjL5kBS/VNbOBDXgUP12QuKawoP
p+U113pl68w/msC2TkVjL0T5jP00IWamTcHTRI/Fp7DSo3hFcLDn7b3Kdy5TFZZl4xzeKQnuXBHY
2e7vE9aZ/eDnrK/0Y/2tpTF7j07x+ml8E+/Imn8c95/bd3+Nf1rZtaSO1u7uzvk3uJv62YazRa77
muO2t2elYUFBkENH4HBliyyKG7o+uFz71WHp8U3Li1odWhNlq14EzIU80n+IOaB2Qy2zet6ZJF02
RSMzcDqX1C0c7qnwlZ6KUbchg9NIJKHGkURartYSmgwkEdflEEocSSBJGvNBvYa83WfEIbHRwSHR
sdFJbyPBoaHh8UnhYWJkotI1wA95eY5BFvqhUswL9fudhQEBmJc39rv4v1/AmzjcLUFuZr4r9pDo
bffx99cKG81NZ59J7Mu+cMLbbX/PPZM5Pr9eKXtqMqrzuz+lfNp+6V7Rvqojy5x/WZJsRi3I+zrL
8smx5Huudcnz1nGfeCjMk/W2rVnlpxyTPU+1iXjv+R4s/6hhesyV65Mc98gqlo6vVBUeiYlcv6Bh
h++pAROP7oaATa9wmDvE4UDzyvd5U05eKXi8+NSuO7sXDfAG1k7OctrlPvFcqQVe/FS8jLUyZaOi
1by24E7jZ6LGLlnFQmNF+LGa7Wek+TzHfp0Ht5BX+66J1RpR6M37VtNPG63YZKZKfiqQrm8t3nyO
q610WyJf8cVlYdbGncfTFSGT15Y7em1wLP7gUZrxW3dPPoL8bYfDl20JDptvPBN6bfzjiOT3ilsj
isqcr4tS//9IvBtzQZ2HEtu/GcZwpcLXVvpvQXz9j/vVnzyqr3qF0iWwC8sYStfJrzXsWV4WWfZ9
g/k84ntBvqKMj7V3PCtaFdEbHVh+pYc/tWpPTV7K1YcDyvC4JqEGvVHjW+dhcu4W6VJnOjOVJ43L
70iK62wUh/QJO5c3zXv2SUHnhXUN+Y7RIWaq7g31LNnW5m8kmwPv5O9M3tHriF8srcurPPRtZEjm
HI8lTw6wWZx/QWh16uOK+duIj7sXa90VTvZhyMy/OVkep9kPo2+7jJu7uzBLaux+b2X/DwfWXS6p
/fMFqiXKpKr+TMkZy9WtnIsmzjL+pRnbIrd3zY7o8ZfdHd/ePGGSh7NXx6bzn0+L/LlPHZlz8Qi6
dUxBR37fpKXVD9e6Ye6Wj1pE187WX5kVrI3wEC9FDcYNcNhVc9gsNttslmnR3alpVr2jKNAXvtrK
57+0uweg3tgLuzuK+mC+w7u7gfWX/zgILAINGwqanJubK8mBgRQMlChJtSc8xZEUQZO6RZ4J8cHM
HKROK0EUi5AEPF0iZngtiU0KY7jsj01Bg4bySMOIDIKGE0aHIaEqOUUh3ogHMp1Q6kgKQhjBIZOr
iDQ5TZAaJMcLE6ImTDzfgj0rEbNAzRnB2EIwW05lwk+PJjWYGTp6aCmMEvA0NalJw+xRW0bDEVmO
pA+FGEndYNphu/A19jd+RNsclJzIvNKdh2QV52UyK6MU6/hjaP8N1zuPmvrpLeTeOa6CSIelnbVJ
X/ZHth+k3fk97ztidg/4b28U+s358GFY49S5/XuqpqW6pNjMjhlL+ef4Xt8XgPCq3U8kBWFNgv2O
j1vwyq1XI0Mut61oy5iqmu6oOxFzuq9/ddN1W+MHuZfgR7TVwCNRA2/h4MrYWXDZKECFzOsYLpfD
5lWj+nJGYnH1pXAzKzBbvO7HrtAnmRt+9W/TTLotNGxR/gEsNrx6Th7PoOKyWM+41qgIZU7xI6d0
Kw7bqADAZYcuAi4fhYXw4Xmb6/uCj4AJNXCdoNqh2rXAJZOmtVSgp+ebCBoan7jFwGnSGzgNSZkE
hShxHU2kE0o5jSPEIHGZpuMUw14dno7rcI0SFyNyTRpC0BSSTUE3CqFoHaGkVYsEVLZiAa6kEZoU
I3Qmjoysx/O8DG/jdXIlzWxMcIugcTWuoZGJEImrAMKkGAdMgsJJcuSESq5QMUhezjZSACKnAwWv
K3QSgzrcQw3TQD8EzuChw7OycYqmpr3sR+oE0HXY8eX2ihEvaYD3b8wXaXAT1/lbyadsQLawsZGB
JzbGBB9I2BjbZWLLq5VZbEu2DpAoA5It2bLrK74KhMM4GUgEKUw5TB0STGkDMUfWHIMbAnEbMpM2
hJImhTKhAWZoQin3DIRSsPvtSvIV2nT6o9P39vju973vfe97u7iiTjyptK1uJBTXt9Q1O9GrBVXu
H6fgapLsDHVGusxq1qJcw/LGqkpPs3BYabKzM0eZI0RbU0NMgkQTFoQmPBvdrjTCsCaLljPIFmpN
Jq3BwrFmouPMTJGWK2Z1RGvQDTsPi7hiDo/DNJkgbeAMBTnEMo8lVjNLjHoEObNojtNzjNbCEkTN
FhPHWIrsxGzNn88yFmIxCiqyBayJM3MFhmHynNFASkxaxsIxLOqhgWLWYEG3hSE4s9mK4xGt1TLP
aEJfZAEnzYEZEK64pIjz+8zaSkys2UyGZoVBMDBFVp1gZYgqQ7+LWRMzD9HALI0moucsBkFdj7CW
lGjRR8ZapDWREqupxGhmU8RBFnJFRcRgtMjyWTFIRayowBgNZrbUis5z2qIUVDFwFm6BXyfgrBFn
ZSI6bbG2gDWnETPLyoR5YqqINnQsShWZMdJMPZaBOlyy+orRuVhZ1YQVwu0idfV1QlpVVLldZt9G
0DbjzihrwQ0kcy9DfTG5W501LW7S5HFiHtTVN5MyNymvR5ZLNOJsIs7y8pZG3w6sqG+sFfeMrNVX
9lECM1XwgNOmyfZktmX8J9s8QK+pr6xPq6yqUGcKhUQaNFOdqk7uer4raV2iYAatNOGObGkaaahc
OI40aeWNNerYYfVGGRSmDsGag9czfiatF3Z8apn/RH3r6GdfPKLOdL8e++03L96b3/BocVZazDX9
uIem/EN7v4LaRmdGxWnrR9Zfn3v/h1Txnuj7uTt3nK4pXTLn8lsH8xpenQs39s2NnHEvrb77zo3a
NevfvNn5xsSsI4dqrhUmGK/YEs7+OerYnzr6S9ufnL/517NXty9RnXx49dKBFTZNu/QDdbv0hISi
1C3/g4L+jE+jyJAwX1AkwcHQtfZ36vjBKIVLNcPLexCeuENYhGZU8VdPGVIM0kQHyW/aOlX9BxP2
GXJbg1b/5Q2jum6YeKTGoV7SldE2C/TQCE6ogx9BDVThm0AB1EMzeBArR0wHbqhFmEAF0uugefe0
tuf8iSCkU23g+BfToHl5Q31lo7PBs5yMOv+D1ra1Pzqy5esQ5yHt4m2/XCzblb5yb/fLX7xSqlr6
83k/SFhov3Lhor5u/Av8Nu7otvJm2+51IVdjbv308FcrHyfev5V1YHLndma3qnhMYeuX/JcLjFVj
P2/odx13LG3Jf29z5o6083+/U/ObeEVdpOLY+TN0/ifv3Oh+sgUU/O3Zj06/+P6c0DdXdexup87h
l9+ZoUCFaNqpk0j6lZABa3v/73+1/tUf48gssqvjhidRxCASSmEODXKCNePEr+SMWenYZ6VnLfpO
Dmkcdct2PbzR8ceoBVuOb76+67trWhvbctl9OdL5+mH3wZ2/mDT1xtoPWlYd7ru38Lp701sX+dyM
Yx9OX5aUXbyoP7xDzx0j1/dle253JV1KdmTOqu6r7Ghl6iLV++ffWa1YeCK3cKkmdvPt6dKc366T
hp5Y85MDP3va/HRT5LHGzUmbZEfGRL392rKJn7wdHf7OhIdPtn4W+Xhr4yOgpO3UZgiGsODO4HQA
eNX3ph5ChSQ6LEQSESr+lEiCACTrYVjjLAyBPCD/kAR39r9ENYRaqZMEYNflCwI32ApzxGd84Dm8
Se/7KAPfjKT37x9NeVajpsJFuAut0EiNga3YH0PfIC8cVg9gAwgD3/297bhkNqySnIJX4BR0wykq
Ht6FAfh84L9sVDllpHKxTmTCYyqPSqJmUApqLHyMcByVA11UEnwIPJWC638N6Q/gY7gO2+EgzugS
+h+L9wycoW82U/w+Xsf7ATUB6ZdgJVip2dRs2C/JonKBhtewz8P+EnYt9j9gfxf+hr0bK1AD9pdh
GdKuQSdaOYuxWy9ZgdamwlUxjt1wBe5SCpR/gh7GwUYqhoqCnfB72CPNkxxHb43wKeDa52Vnzcmc
nZE+S6OemZaakjzj+elJ0xKfo6eqyJTJkxKUE+PjJsTGjFdER8nHjR0TGSELDwsNCcbPaApSKD6O
sfXEhyYrVSqVPdWPTxyJ89JE+X0VD9EjhJSjlBJG4ZNG4ZMHcQMP43k9zegEwz2g/5rHgkaN50EY
hVIU40h+JdZVTbNVfDzjcjhQQ0fLCa+/O9Pvimi7J0LG0IxblpoCPbIIBCMQQtmGHkr/AiUCEj2b
0yOBsDGpKXx0Mi9JZIW7ms/b4ECA1qEl5CiGOL0DfRuHswDVApDCB1F8CMOHiuOSKj7PycMG0pPS
593YK4cyR3Kki3Y5F2PknOhjD0gTWY9FiCMr3A4P4YPQuPhQIoWwHuKlhXCwHgc+aR1qPZOO5HDG
tl7Vp+Sj8c3yUcl8AUoUrLimlHrZuCoioF7vesJ3ldqGc1XC0263x6HDXpZGg2iMrc7HqcTNTE3x
zckfAJejWhiz2in4yVYT7wa36OtG0QdRlPXgwji/T8rrZV0063K68n3WGT7PIr7AssgmThBDp7P7
SX4B5ASJHIfOrvIFu9BkYwTHaKdO6Vv2QYrDT0ECG2ASwQMODfCknPBgstEomiU83FngLc8Sk0dl
p1CrZEiLD06U08T7AKuAg751cyTF6aeEJMofgADqab3D69XTRO91eJ29A21lNJHT3p7CQm8D68BR
S2yo1Tvw3gYlr99o5+UOD5WDsRcyQG+yoS964hECiFcurUKfouwBdokt14cCphgmWoQ4PYwKXpz/
hVEHi01FMHBWm12JcbMJsAVh31tILEzkLFxzfxiFmLmzBsPF+EGVSsjWDb15UIYI31Zq8+EEypSH
IW9mMq6PQ+D0BTgxVoHTFuAMqjtoHOUoUFjPYviwaYPXOHmsgvXk8FTsv2G7fXxewdikSondB0mU
UgGSJePOn8tPSEZ4erIXF+UczcuT+WBbn3KuncijsCIIq2mmC0sX2QjrHcwKH8U/0/iP4lKF8g0Q
au1n8Bza+3Sgf0/YGtGlYU3SEeYnSQL3IqiVfPtPzqsFKMrrCp/7v3aBZWEXwQVcfxHBB8KiTNj4
iis1K5Za8UEiaExntE0njYlTSDqFGhQfgSS+6iNarRqamAdtXHwFUBnTaZs4iZOa+p6xE5/RGjvW
Opmaxv37nfvvWsVMH2Hm2+8+zz3n3HPO/aFJGsoVUKwvoZF6N40Uy2mSUk2FQADja4HHlRR6CvAB
87Ryqx5j44EaYBwwAOC13wEqgWeBUcBEXs970W5hOUC7lk7ZRpAma2fwXpdSC76DyvVizK+kZu0Z
9HPtvjKFWlQXufUkzDmoxTiLL4ahmPdTuXYU7XysK8Pc63jl/wJZw6lB+7F1w/iK3NpHpGpDrUPa
NhoMO6AzBcEP4dMiASDgilaF/kzs8cGGKbBnAo1TVlK2No/StRpqUEwg3/qtNsNuGxuwdi5QLtc3
YM145X1qUA9RkvJHEpDXoG62bum/pyT179BplXVLnSfPn6aRqJXcTj9gu6XtsJttjtsk9Wedvg6s
44R7AZ2qFdM6A7SibdzRrSeqpNx/o51+pLWL0eA3ADfwnF4lVoOFZlGWUUwzJC5bt6B3IXx1FnO/
NLqtG1LP3fRA7C5b5H3upIHglepNKsOc31hPJdpvKE8ZRonKSSpWjtBwI4/CxhM0RurTi0Yi9p5m
mdC5F/gh6ZeL5FK64NMummo8SnUco3d8hXMd86nc6JDx1qpXWSfURVTHQHw9x2CdoEMR+53vnk5H
X9MiZIrtNB6Yqi3A3TJgP75piPfwfmcOjZTncPzFGUD8LVIqrb1gjzLFuihtjwN3FQfHBnz0c+Ad
4DDwHvzWDISABwB80ipz5BoHuZVR8DnHLOKG45NjhOMDMe+W/oHu0gbEu4wz29ebVR/lAYVAliOR
MoF0IAs5k8Q5w3HLOROXLeMLcRNnjnHOYY5/tl/ayrF1L4/puY9zUR9B46V+7BuOv//CcX3uY87z
GuttKauGHPDrccRvN/QW4IvonwUfYTvg15/qk7H+YeQV6gBy8VVZC5CPEg65Zl6M5zKrTntcnY67
QV5xTtzHH1KdPizW5loCn9/DE8GoK5zbMf5+jPPu3FuMue5w7jOrE23mfiyXG/5X5prFdePO3cfj
Is7tojV+T5yHnEtxnTWycmWOnrFelve6MrpKL46uVKZEV+h+K1sbetvS6y0dfv1bvOaqB3BP3dZ5
eV84Q97xCipnv0sfL7TOGaft2qRV4O455g2sRd3VimgM28m6GkQVXGuN36GG1NODnCuy7n5B41AD
y5FvnB/9tR9SLY9p22mx+pr1ubaEynlenWSvQb9C5tE43PWrmG+xa6naGqthqCfaS3hHXGivguyH
rS9Zpr6PJqi3rZNGb3pW/4prImzks3gPz2MM+dGsZ1vXYXOLnoHzcHcyvqoojePKOGKdc+zEXMC6
Lm2fYp3SU8Hs7xsYZ3+tRf+vtr9QF88jHzP1RyC3BrjbX8WxWu7EGL9RyCHpq5B1Ku4r3PkaPYGe
dERojeMA2o9ZHzvSaY12Qurnd7wJLqOgzMmfQN858EUf+MZvXZe51W19pl5BHXsZY4xRmH/duqzf
Qrsx9gZUg6fYb5uab33OMaX/WvqctHqMj6HZeM+ajDdpsVZvfWyY1KTxGQWUaTSDJ6KucD7PtU7K
swshh9+5THmfBr+L+mrrM6NOvrknpQ4ct/PAiC3eE4/pnhyPca7hXIu4DuObYxC+RQahX6M1WMe5
divn6BG8LW7nG/DTdJqOHBjgJMTfYZqEuufh2gfkAkGMT8bejT14A8NxTDypH6SDehV9iL0b5btz
TOmvHRO63mZd0duU523E23dzT4iD9hwz4+65/3f8m0A5rrchh2PQjuFNAZQTNIsBu8lxVRQD/eKM
+Z0xLASGYN138S3YxHBUUSri8ibwjB6iLiAINALH4Ls8jFfF3028OwPxTm0H5qCdCwSBQfDraHyU
7yrJ7lPKvKt3b5tTUyXv9HgkX3Lb42+lp0veHOPjsfXH3fb6oxl2/2hyMnMo4USyuzTU7MuUo2/7
/TZnZduc1svmJJfkrfn5cpd7a2JiaWity1UaavP57KE2rxc9Hm9yueyhJigROlNcgp/+A+RQUhMW
fG/Lwi2fblFZ4BaffdAWb7qtzpaklNLQO84kOfpKzIgLWfk29/bZ3MtW64LbbR90ISmpNLS/qAg/
pimn9mVm2Ryzf58tKpS2Dw4L7U/GKfudUH+fO0XOd2Kz5CFDJHfFuNNvy+vy97WP6oTgUBekhrpi
2nXGrqAz7tLOBAjucjrtDe+mY+277KoOZ2zBHt6+Nz1DbtsT2zZrD6x+fGnYfAyYNTNsHv4obJ4+
FTZPHQib3cChD8Lm+38Im5EdYXNHo898a23Y3Az8Yl3Y3Ai81Bg2W4AN65zmJy/4zD+tH2yuA5Ys
Dpt80DL7kkPDl8GmZThkMbAVeAFY2tjPXLM6bC6CgIUQ/jx4AZC6Q1xfL3hbw3qzf2nxarFtjfi0
UcxvFEMLU4YUuAcNTskf6B6Ql9I/190vJ6Wv6c7u40/2ZWYlp2f0Tvam9UpOSfW4XMluV0Jikstw
OF2qprvwQeIKGJVGxFADaiVVqtsoQhHVSMDXkzN7lNNMGek01RFOkx50mpUlIuKtoIrpZZE0AZ5W
FikpqOhw0tTI8IKKiLNy5ox2IVZUYzSiNHcImh7RmjsUkPdbNTNndIhMnl6aje6Mdk10iIVLly/P
vtOqri7wR+ZWTJsRme+vjgznxip/NRXgb3bt7Nragvv+2hP43LlTy2pra+sK6r5mxTf7q/tPk1zM
+X9MB6FuqCDK8eR48vAjMPLlQp3+yUxo8H+shdE2ZTCqRwLl7UaJUfUO6x8hd7I7mFCmB6hMK3K8
qASu3bxw+0IBjR07rFiQJ1WUKJ7UNPHt6HmRe+rqpWibeEV0iSOiOfqz6LBofnQx5AYgd6iU++hu
PTtBVaTcjIygXpYQ0MqoSHnRwdE2ZEjQIYM9JyfoCGVmxnppGeh5vbK3K8kddARs62730CTX60lV
hVv0jZ45ffWSXhV9IloeLYzWi0XiE3FaLIAmT0XfE62iFEYHQ151ly6EEdG9iqJqmtjB9h7c5fEE
JScmB3UcNPraiIB3RIDGglMv4SSPmpuW6xGtHzy9aZMojV6O/kqMhURBPrFJfKHUwc+evWo3KYqu
BjwlAQpcG1aclpOe4xN/jvZX6k6xp+fhpxXfhiqV7FUiwvsvrqs/OIrqjr/v/ri93c3u7e7t/UhC
NJcLAQkSTEiWo1dvpdhGqkOhBEMtRlq0Ik4LI9iOFRgdOxicMqTQsWGYduxMKUJbcPAA/yk4KqVI
AUvLOFqGDq2VH2agWFOE3Lt+v28vOtO73Pvuy7597/v9fD/fH8v2ULzsQ7uFbGqKJOoCNV1AGD2C
etwx/TZAB/6Svw3d4rWJzaleVr6rPsZMlmHzXmNe9WqYdpygzsHBG2bJuuGYpmdtO8D8eWEfytRB
XOJZVpBwcEgN6gfrE4PygawzOoJ/gjmlkRJe3DFdbUFoWa6ZRrkl5jrprs6ebqdNWnSTXwQHFJDA
55erqxYveXzFQw+mYBNMhynwIl/O3+On+Qpl2zv8Br9+4lgVssfR8ruwRvajrmnQQ9N02toCK0Rz
SbNQ9/3AJKUd1G9fJK/vQw1F3k8khAyNOiuwrTCVCiyapvG+ZTmynN4ueWaIM/NlRxO3bMRTooV2
HIckGZ1BSK3Q9YK0Y5hBPItDWooP0r39tCYJjM5KZQIhk8lI2m4kTVPI0NT1AJG3Ntq2JDiKz0qh
nQgkoowzgn4XFO1COeIWxsMRISUeuQW82zUepMgpOef2BK2se0ZbvkWe6OU6lZTPVKU/M8Y6n4B6
YI8sOtrM/zUAe6+BzP/NfwoOvwp62/yjID8+7zv8Zgne4Hv38/PvIsKtyIYFiHArlMpNIULQRNgm
kqlAc5J+YDmoZkOjsM4PGoX2CHVjY2vG0GnWmM4Gus4sz2sdZmEmGzCCkIXIG2F7AiHGlNI0nElq
w5amk698sRPKVOQ7NylkmEScWlt1Txl0nOZBnzzt08m4q5C4sV/DWciEG0k8wq/hTTLM4D6+36BP
xjSgbzSMRrpo3NggyjNu2hBmszgkfBzw2YYoWNoLHSPt466gf+C8IMCvEbx2PVJf6Mi6GOXtXWKM
fIN+IaqTT7SJPa1d5BQNf0q+pXXSxHR0rx2rxOYf9i+9f0c7/yAP1lsnoP4SJPmH/x3hlydAy5Rj
D65Z8eJaufDIrLse3nP7z0++uevcgntuvnrhyitT/rJs4eJ+it8OjIln0WMGc9jvwqlG1nEDk9hk
TkZjDCKp4ZjmJt3wdd1wDCVORsZf1sEkALLEedOIeYZmmLozu65Oe0GRZVAIQcyySi16SJYRUUUR
fk5mMoFOeVUP8aYe1tUFuoBDAFbs6nAQrw/cQgEzLKFSLFbai15hgzqtfcPaNxEdWgtuVyqPNSXX
rUPOnVEC+Y1Dh/jrld3SJH4MnsAk+NjY4Sv8LfjCFTkcOwwnGttmosVfQ46upCzAWtipskXhmSG+
6EiEJgcHi0rEDAo/AF9tCtOZoIk0bNqmhSmqB4iOFhpGoGlyZpuVlLf5mhvH9eN5062lOpe2pZQB
GxlrGDQE+zKBUWOfUWOfkKYrZOgg2wzDVdXmQZcOdTuIOuNEIhb9H4NwXkCICjXaqEgZt6erM41R
nG9pk7oxgXamoUamWMpPK9/kI5N+dXXpO4eu8U/O/a36ADRC+o//4VPvX732vvlrV8uVuX/mM7d/
uqvML52HmVtgFvzs9FhhzYqB7/1g6QNPYZSvQc70Yk1NsPnh7UD4QIhhHPcA7O2JmJVFn1pZNCQe
Vy18r7KBOAOQsMlS3Q7sDpGdPDJMWCFKXEkYkIoZkPIzuZ4G6AlySaV3ydl7FP4TuWfb9oHKvVm1
7+Nv8W/zJ1fnZ78EOvSdHYAG4jF+lNOok4ZMPl9mFO1RdsQLlWZsfKbVZhfCVVjmH9UBmwLJiCuq
ajBDkp4B5gMwzVDVZ2OaH4tpRoiVomrAOQN+YcByA2Rlqx6PGyCpyHumyRIDTRWrDCMGtP3fAQ4D
bAZYCTAAEAI0A35iHV0dS6JPez3xuoCuK7BsqdhVKhaR4B3FSlHcrTF9w7QsCc0pFumH8CyJ0gky
XsYvJHOyPBl2851f519exC9AOQYtQ2rfjd1Qzz9U+5D156j7GkR0riE6NsuyHFsV3qpp9cSu+q0O
JVgnxEbLcVjDVttLbGWyTwRGcFSRT30h96M/NX+dKkjqTwhU9ZZ1xsG807DeLrc4o5UiVu8CkXWc
niKbjbRjfqMepDONjNRoiOVyGLmCkG15uXaVH5Se3v2blaObNl3gNyvPQenaj+4uzFn2/ui6R5et
VvsWbl/5j3ubf79y+JyyjP91+fQZX01WzvMD/fNmP4R87MWIPoMRnWLHQ1OOo+J2HOMsTtpjDvKp
kqfF/Hp4K3LTtA3DZkClGCM8PmQn5SFfMegZRmup5NCzGJsilCMpugJTdAUitK+H+IKAHod1jIlc
qMfTmAsz6lqxGIuCW1OAZBnPdQ+knVEKWQrnIqW4z4tzhBdVCK8wXppVCWOZmp6kGlPyzVEzpJzh
r2jv3Xj+qSNToecWfvIs1uTfQi9MgI/kxSnI8S/x6gGQkp9U4UmYi23aRowO8v9F0QUn2RfDlDmk
e8YQkxMOFs9EFu1JkGOvhg4WR5VSkHowZa7Xy77oykSSETpGnvRSDrsNyIle94xpkB+El6o3jvAd
/BSfArOe27Nr6eaH1b4f85MX+fv8+8o3xn4N6t6nT/dR9/m86MH6sF9cEObVLVLY2hr1SRJxUJIg
tkX3YIshMxbHYhEnYOviHqYSS4qhRnVENTdKHlFv/FkiRMToFaP2VforayTGmfTC2HT5lDIfu+Uq
P8MpCkDgsVDgMTfMkhaIg0QBIUkanh7HnlwTTZcXNWOoAnYgzEQVtLIxrkJ7TQFB9Oj0VHT2wsoz
8CnX+Kvy28pX+Ilq5ZIqrKdzdwrr7wzb9C1KiNRSQqqLIYKOh0oxz9RkQ1oP+y1dXR+L7KUfKxVL
Re8zSz831FV28iO8jx/BRL2bQl/qqvxJ7at8JPnRiXAUT5TZpLBO8rA0r5coG0fJES1OSCCVFWd0
iejwS9HWcJS/TltFWtvVy9KQyB7drzGdGrrOTix+qH8spiRtGSgYdCyIFqrtxDqoj8etsIpXOjuI
yK4fy7dMcpHJd0K3Kw394Z/LVg/MKd7djBmq89TxFOhO+533yTtqCH0sEBorQy/2dKKoop6ik8AU
i/JdCi6JMnhAxHGov8jiEll4sJcWK6oW1/7HdbXASHWV4fvfcx9z5z7nzuzM7IOBZZddYCK0S2Hc
duhekEdq2nQtoUpxLZZIseAaFTVa2eVRSjTG8MaQWNRQW4XQxnYXtjyttLU10pYYW2PSRim1IBuU
olHYvfX7z9wFcTN7zzk3d+6c8//f/33fb6SEYZrrNT2nmeB3UtUNIpUTIqUlSsxj1ISvEz9g60Y6
FKot9CJ3BZNxXxYFd6F60XIqpqGpGvcBA/xjtZYNb9FrALFBiS6l+tM3MAoTWC501iq8ivRVQ14x
t2trg1ObU2B3XU6CU6kxV8MPs7ehZnA8CU7Gr+kAdcSHaU+8N/7HyfhlJLdP3RDXj2xTu+Pz8Sv6
WGUZXFkOTR9SDGzJnTatEhl0u0FZgxzO0Ww24ilcFjv0WYUeNKlbp/kO3a3QvSZFOn3MpIk6mbbj
JNqnGLq+v6aIRpIAHqPxiND7BhmCbCI97SgiNHVhOraiGwTmkC3Q1KmwdviGxZIobzm5fKXbogkQ
XUu+J4dnDG4UnjGo26DxeKVBiVekdbLn8uobKvcKElEqVREDbnCl3AM+mlHPSgrDWJzeIzVxGPa5
UzpGDjTCH1Rxp6f8f1LKEnr9D6Hma7OspkbJHqS+Fz8bX6HLl0bow/h4/HNtybWnANPXxa1X9/M8
weg+6X+eGlIcZomw4kijG/D49nOoZSjC4cgK88AjLlj9MLJgDdWVuGD1Nkykn3BeNyoHt56NpmGi
Ora9XqhAqeoAi6oV+jbGlDPXh5Ws+OtoMCPmptZZAwFQdg7/5XNhcmqOwM0WOUET4NRM+UK+LgO/
TG0zM9q++NLoeSLtP7SE3jS41MWeFrulOPI6zvqn6nj1NajGmK7aUI3+ASOob5S6GGUwCbYqWWer
oVlFyK3gWrQwsYIwxyu4aUzQ2wXJChMrgFzKFU/CPitAFVuH67w+vjmAhTgEvSkPI8PD5f9VRhZD
PZE/vhJUcUZHJlC/F1+Mz1AHDGyJWuLfx+dHRq7U0RPURmXaAkocjt+KV2rfjhfE8+kFOsI+kfWH
ac2F//98ZCs7PE8N8ztAClL589I1DABqYV8q8edyhJ2XWmRLW6t6HniUccpMNFDgbY+59EQrO6eP
JjTdUYKh9dSW9utt2+/iI2rD8yd2dW/77raLb3xz2aovvU7XYl1ffM/LW75wsrf1370LFz2kJLp9
Vu62qLzGWPsgugWhdFx3fdrOpdN2Ou0y6bk7/AhGw/dtcLyH0+QC1F0uSM4ziPO4DskGo94LYFrs
ImrO7kZd2nBzsC252nFxI5W0bnKELsqR7b10fhwH7n1SKR8RGKhnqhvrcoflpJO1ecwFVqvsCdkE
ApjFMsiOkXkjLGa22WYjAV1gJ0G/jY+rn/nZq48Nj8R7z5w7tezT8+Z196rjRhGEe073/WvV6JPq
OHV+vK+xp9r5QB1qUQFGe4DRiVRlbQLUkJGmooRWzX01cWKxfzmCVhqYCRG7itXQ1LTetHJQMmUy
wuVLpDL1B/iayY+F0JcGlmbTamrQ6kToZzkKMxHybLZuh59VmonZi0jsaNYUDmrIbS3xpZTKZCtO
Cj9dCqC4Du9nbMTPO1w0t+PdpcDCZkxHb2gqye4BZCt7FKXY7xxuzXK4s9kwAruEod5finKFSulQ
C2MOAcen5rzxAf1larG/UT7SKiVDJqypUXmzB5bw1p5Syte9JrpDNIeFkorGsXlia/ukfA2u7a1t
M29rnTFB+3j898ovjy9c++aLm+Kz8Qdn4j9Op8kd7/Wufuj78bV3yDpL27QpS3/66K3z6qfef+Ib
Q/HlE0c/cWLxHdW542YdeX7wKmsU/sQF2aXNPqSFqr7dZPMAWKVtjmG/ZkSWXYGrwM1B3GMHmGHT
w6dkM6F0jVa7btgfcSE+GB+ND+iL48vXhrSF5PGvPApMHMOv1CldQ0qAKNcBxnqAIgi26uwW9Gxd
mpscaGRjYyUHTi04a62BvHS77F2qXWXJOnAuHrVMnAbX0pzJlahmYLRjnxt96aXza2jppC9/6oGv
TAJlHjz96vo1fzgt7hs52LtydnX5GnGfdE7Q5EvYSUgPD+o+pQXRTU2py+0FLITHNYZixfqNyMJE
j6ATOq+ywI8boey0WwAePQD0iIHqY6IXgecFRHfp5LLuAChMxTx6El2YkB+GGxTKYTuq73n7a9ri
wuEecNyc47i6A49k6FB7fb4gvLZYrJcgjbqwM0cYpGp6qISea5qGCElRPd/VhKk7hu/DVzrkOIId
vGDQi4g5XxgRTs9JBLQVJWdIbuypr/nXzuk9nNREsBPZLrJqV6VLqkoMB9Wem6X75qGmcDXtvw73
nh6YJhu+qTkLuStkm7OzKlnjUvx0/Mqf345/E/+EFhyltGa+S+3vm+6LUvc2j3wLCTxhtHlNYvfI
FxuqYo5CH70K5l2OzKWUtyJbk1XJF5PDOzbWWAL9YU6OUQlqLm1nEm/TMFPGel3L6bpGmsaP5Nmc
mroqQiVl6CIFf2WamsKGwEI7qjBRyJWHB/GKfk2fjPuJD0X+J3PadU1LWxxCSbiyMMrletk7hkkk
u2QQgyqHMMUek+k3Jfk3KXpLGn24TG15vCg+GS+ir5FOArG4MPortUvkR6+qBjTozo/+JobRDo1T
2pSnI1uw0BgB7HCeN1WPBIObPB/EB38ShkFpt5uqQfvkIezYdQPRwqCfki9WWnYafEIjS2HA7wl2
5gNlE1GTEG7bpqYXJoePZ7MTJCOAkIMJNGEjHCRs5JF2prseQAf2YLQqez+0K8Plrq7yaLlTdoDD
El0zJJ9NgcvhygV33UmTZt7WMtGcNKt1RgfoLZMjDUzH7CaG43e9u3cv+8EzK/5C5e0/CuPhRgoO
PDy4ohXO4ZW5s+9dVX1o9cI9Gx788dL87du3NxzYcsuyVZviWY/R/vFPzLxn4zLEh9mmAKQEiNDX
hxQVKoOTsQ+Mih4mfm6nlfVDatgpgkApsOvJyIYJTxUCGGJDxjEIK3kY4AIVHjOOjvc8FCJlNvlD
JVZY6GcRpwM51QCP7mq4s4s73xpLzZrREdblVJy33TBbMpRLyLtlolFHT3b/4uBrb5xasW5OU9te
mrrkzk8uW9511/3gzNKO+K//vBi/s+CRcX3I+x2PrN547K3e73wVtTsHWf8QWc8rQ0NKDhu0wQo+
U4Mi8pygLGCZzwtYESu3S2T9XVYgD+Ih9/kAXtBg5ZO3XNevuHmWsfzjjpLYC3aSz4E15BoVJNdc
AomRVqTbAtoD1o3MRn7TANyYcaRQU76k8quj5ep1p4gYSSz8l+qyAXKiPOP4vtnNZveSbDa72WST
y30FuLveAUHCuaR33i0dClWxoyhQy1BLVXQqo8MUbC2jWCGgaCnM9A6KJ4jjR5VaqNcDAzctN9ix
ZSojOofWTkXrTP2YubZCS+tI1v6fdzenzUzyvvuR3fd53ud5/r/H8P1CESD0zBNKc9MZErgk+cUR
LyQ/+d1Z7wIz/1a9EPc+0nb+6ubF2xvZxpG/sMbJSdbx9jP6Ee/t8dsPYXcXwg8T2F0NBDY8Kirp
LLE6OCGNxk/BeqKEFRjjdNZGHoghazBshox4cjCq4286fGZyQMbE1lFT7cB0kz8IPa6iw3ACNTcN
n2UVhnSwK+xYTjeZuVk5nqWNpzgo162uR0AtWa4reLKtR55WCPXMM0pzM1mGkCdKRpBPeJNrDj8z
Pn70wIqdvzjQv4qq3r4Rljx/iTVtYq9cuvh3dDwTa2+Btdh1Scaup4SsUAXb0ja+6Ac02elGIZ6G
gh81yrEQ1zkWNqtEhFG2x7JseTBq2pTc9qChCzrCYQqseFxwLvP57L9c6wQF8pyg1wSja+ENylb1
Ky1plt4ijDVa4ubE8Rw5gBzxry92B92UBMUaLwBGOXBFm8wT3AmH2ki7KQCEcBsCQJJrd7PvXTvY
zLR13tO7X3+ImW+eZJnaBnab9tjP2cuNqbV37k95T9zzwRMfs05v8v5XASyC5Q1La6XHhZmCI3yN
7Rmdq2DzZmGhoxjz+YXkgTTMWzjkFzW9P6q2ts7dLXXwpteAlKvqjP49mXzIBX2HBrvodAPQr6tr
1u4ZemudCXpIYuhoBOSY4l5DAhSIDyn8qa/kZ1sx6eiQpEJLD+vZIhMryPNRfWUZspNasIDQZqSr
y+EjNQI0gk35mM37I5zNR930R6AERyKN3pLKzdlS0PGIQtAEFfiS8aJCoTWe76Xq7s7Go+Nbm10N
rNuc63VxW68Lauvtzbn4a87F9RzhcY4u5XiXUOL7RD0BaRXHgclkvYGgy8mS30dNrqJkLn6+0yX6
E0/x7nJ5MksSYCfr3QXfdmxwJG2lkAUdcp1lpbZWaIATfFEnM/2guAxDYUz5NZJP6/UyUuhol9YW
W29OXvePd69dUlr+5IeHf+B95lW9V84+f/+pkf+8tf1H6vXbZnbWxq5Z8dS1K5d77xnOLzf8bONt
5/oc0xL/3PCNZXf85LlEc3FeQYkVHlj98InKmm1Fd/2u6656/seHZy6/S/FOX79w7zfdvpWXDswp
LCzMLnV0MVHi3IpgO4dakxJuqgJBToxMm0Wsh3LZzLnObVBijmoaTBsSg+aGRjeH+irqKaFFZWpF
IRRTjqWZUTGrlp8zcCbqBXxaHujrnlIM9F8gAGq74AFigeGlv12zq9d7Qy93z7/Tw0o8c/+Nj2yr
3Roqr1lSWrGj9jIWR4qHxT4VXofMiAjtR0KGvC8iiRQQMUV1xESYVeRQVdEv9tX6hAFsWQDs/PuU
d5Z1eWfF85c08TzbREe+5dJNvMperKKlOzEye7YvACriSKQQIigaIfWhEZwZIn+UKZt0BC4WJEpi
SNJCorif4AsOZZIajz+oSSlNk1RJFKRQnIVkYGwiIghBYvB3UNfm910uypMYEuKSRocaSbiFV2ga
s03LYTbCn9ngFw7xUYJrpkoVuZogN5em4ttvsuBxglnquTjHSkBXBRAWJhpT9JcUH2GFAMbaxAhv
aZzLHczT7Erv6OuHvPdZdmbeZB2sEBqu3cJO/d7zINSnnfYMW+n7DTuxDDvReARNhiBWyKLRfN4R
qhLtOxZx2ZwSHruRdVHd9/8jN6HGF4RdVcEGvpIsBTibC8IqT96NR2Fp1DLytqwPNePMrwF9zXTL
UYhYTk8nSLPdDhxESdbyLsSR1LrCnmvIN1Siz6VsO1WxXFyzqrxf5QhTpiLuOwjSDVFDVPZ1B9j2
hXj8fNZmUeL6ISs3eWe13nmXrfHeSF9RvOZq7xyzF0+ML7/hzC07+0PFuxcXFz1dOxMq3rN45uqH
a2fE83sPHTq0dMuBIL8+hOWmsH5Us6G7eqBtcZ5knbwdc6O4wBqMeFwe4tf9+/7p6mocpT2aYHpT
i9PCGDc+QUFQEY5ZwKBKQzVF5hV1KNSq7iDjivWU664b51tEZShtiR96Z/X+4mPIA+urW7++83DI
uW1Jzwe1P4jnD/5w0aPvBZqsYNUxEMgLo7KCjlXg0omJrGSz/lEME3NQNuODgs6LgkZSS3qb1kmT
fGZBwdBJvfkNmJDAbhYVSjJ6iDltGm6AeagmKUccy+mbfZXGDaqCi1y7cZ3GUdyiEprQ1k0Gw6qp
cj0wGYjxXMFKCZzD+lnmC7U21Pw+E70L5970ahv++OSy5UtXLPnW9VLEe+29d7wJ1vnBgXe3n9x8
cmS4cvzlHbzqeAelGPygCY3C90ejZHmYFpfHJK4DvITGuAn2EO3BsM4SaRuMkaibnbYB2kqAagFp
gV8VxhFDGWsSxYRWEap5n7Kwg0Fn6XNWrTzAjTH9UDQsHazdkWWpZkbG6BSnG5mx5DdPnnn92YNX
5m647Ipv7+v7jncwvPinz3qffOr92/u44vWKiTuWLrh3gnV/d1NQ70PDkiLEqW+QkYHZFkfirSAm
Kq1fpry0MsFZTFQ7mXJ4J5kAI0uiqsrMkPWQn4oGYRUaOgkp6FKdqmp+1pGiwpIBg1QzkFSebX5m
JQsas9gwUik58Gi6deWtrnh+7DXRe2v+ro1YZxQMvBeeb2N/rQot8CEKpsqbVNJ2Kp+2azc5EV6w
McnZkCD/BkzsTmLBOSBc3PAqb3NzOiERB/6kf6MK7s11xjX/KIGJrUYi+3N2KpezW+hOnxzfpHRV
yX4K35xNP53RWPAQTHKdwBd+FMMkouZsiSUTBgcd3aFxNEptKlDnRXc6ID41mDCFFubiKkO/gZKO
DjfjiIMtuuGaGWrkEEJQHOZi5TGeDprm5BX8GNxiKgHU3MRoWXmwWt7Gj53L5NVILMwygtsE/RIy
W2O0CmxRLMCvWLAqPmK7YgGG0ehmsPxYLG8Y4a15F3/K55O0xmSRJCbYUv7BvFuHzJTL9K2DFGdj
H7amJkZm6vI2DYqk3fuS0P3/H+RrBBhVpyd5Wqvo+PnaMd3np7R415/a9w85659/evXkhHff1Z+2
jF+1Zp13evydU4+fCHlffmjl9O5Epm/H7cMvse4ZD/bMWhRv379j59h9iCT22UehF8JzBEtY5s5Q
bVTUiDSkmoI2lMAmGWYiYVmyHEsmdXQ+lZimkSuOgHpisUw6SehXKuqUoNz+clEYgOwaZZxCinKu
4dxvAQHbe5LTekrmjGTJYqfm3Pilyx8oH/sf+1UXG1URhc/cuX/b3e7eLd3SFom3QbFQacFSVrSB
1kKXgkDFFpRYcdnetgvtbnN3W1MTER9UtJrGH0CMUTQmSuBBU4KKMQbCiz8P+kIEQY1IYqI8gD+R
6G79ZvaiGDUQYzRE7tmdOTNzZuacmfM3z+58rZzRUV6U72yfpx4vG3uLHf6KzSzNH/xK2iP0/Cg/
g/iQaGqFFlRHeTW8f7gad8NFoZUjAiolPLhNE55VE15SmzSpKOQzcf+cl8DsoPFsf8QKsMADPhkP
uqzvanLzhf01FlKw3z/Y8D5BPEAuugAIP5r/ZsUx954GVjU4v2OyyJL2HOh8clR5Kte/pXnpWkVk
OuQn0sbBZ4BeaVrL/IHAXSLlIaYgJVnHlVLOFR9X1TtNX6lp+jTTMLp0rVTXNf9Npsl1pqhaCQWK
fIYeCjBSivxIjzRDN03d7+ckPo48Sq+rr6jrqi+vq8C5h4XjEAl7WJZUjpCNT5RoWl/KDAcJDvKb
P1QQlZDf+Nk0VjVF/LTx/If5szuf/yn/Lou+9AwLPrVbSKo8khvmZ3LblWTuSWUAunI2/zx/GHKG
aahpQZgUZYsVLrWscDFi2EPBYiR2xYpWbG4zjKJt2hVWsLiEwqFgKIwMLmQFiSxhN5YVNM1gnXhV
VEB9yuvCBSlI8L5QWMf8ulPokxLAImAZ4FoTbPtYULj5BmEAUcE4fzh/qGHZY5sWtq9sua0xlH+c
3XhwP1iPvvj4msDJ4E2NYP9l5XZxRzNwiIvAu4/G3iRFOsaKqNGEQmSu4whXirDyCPTGEM7DYIqy
TjdwS4aii5EZcHT6Vq2EGeJNaWz1hRRDNRlTcU2WOltdp96nblY1VdXlo64iqgvj6CrclZBROABE
rppG725ktokPnr4qUgUNa+Cz8wvY4Z9PsrfzffzM/twLR44oK94X3A/zarYDeaVOg+P0qaIJhkKV
VVFNU45xziykznLbSlvUPzaF4bWUJhS6Tuy49gkp3otT1pVTCzXySVnDsynSeTXm5HOu4K2EG/th
zuwpbBqiEh8eHWXT9oINi009m/8AOhn5U2imByXspffoNJ1mMcCPykd8KeBrteFP4JBWrx3SffrN
+hbAAf2EUWHsM/aZG83PfG2+nb6dRXP8pv9G/2b/5kAX4IvfQ7FbfDwYD34cSoQS1nbr63Ap4NXw
eyWxkhcnTZ80BjgRMSNrIrsju8uuBNxbduzSg8nTL8NluAyXKpB4MTEZy0uJC4xV4q/TBT/u1f4A
UcgKIxmKlE2mispfCa66evo11TOo5tpZtTR7znX11DAvej3dQI3e+KLFrbEltHTZzbRiZfstq26l
ztVrbqO1dEfXX+z4+oWZ+ic/ld5AOZNsYEUoZxDkoLkUpVZaRu3USWvodnIoSYM0RHfTPfSEXTEx
gTk2VdO1oL2O5iHuLKHltErSxqmXNpIL2pEC7cSJCwNd/flz3g1d7McvSBGgbb+u+Q6Rh3OqRIt5
0lfSEQ/XgX/r4QZtYsVCU1Qfpm1iox7OaCb3ebhCQV7v4Zzm8mYPV4EPebgOfJeHG/QzP263dbTY
rW48tbE/mbJj6WxfMmEnM3bczrrxbmcg7m600z12R59jt6WyjpuKZ5PpVLzf7hgZdHriCcduSbuD
aVd223djdp89EB+x1zu26/QmM5jidNtYOuG42TjqDUNuMtOdTAj6TK3dnnYlZifSgyNusrcvay9P
Jtx0Jt2TPX/pWttu7u+3JUUGS2ccd9jpro21LV4SW15zToAC/7MWOQPJvzPy354FFLiNOqgFdSvU
NU4pqG0/FD2FnhilKUt9aCXQSlIGZRz/rKTshkEMoHYxwwZlD8oOUDtyzRSoHIylQJHF3LTE+iXN
CMzIAX0c6wrqFoy66EvLdc9R2zCewt59wMVOI6jXyxkuyl7JUWEXB9zYHtcJ2ZMFfaG9ASbrStpu
udq59TMkpG+Xu/7WJ+anwcuInNOLvbPoWy5nuhjJSEmzf8m1WNOGK+iXsv62RsbjOiO5G5Yc1+KE
22gx3EYMO9T84QbOP/9VUuIhjIgTv/h5s2iRvKfkvzbn/6xPwnMq2+kMIl8nadKPltJ89I1ptfCA
hfirEA0EEvevCzV+T1NM6Wr37Fr9tKjHG78/lZvIPWreZ+xA03fOc/8yAJj4gEQKDQplbmRzdHJl
YW0NZW5kb2JqDTMzIDAgb2JqPDwvVHlwZS9Gb250RGVzY3JpcHRvci9Gb250RmlsZTIgMzIgMCBS
L0ZvbnRCQm94Wy0xOTkgLTI1MCAxMDE0IDkzNF0vRm9udE5hbWUvR0lFSEdNK0ZyYW5rbGluR290
aGljLURlbWkvRmxhZ3MgMzIvU3RlbVYgMTQ3L1N0ZW1IIDE0Ny9DYXBIZWlnaHQgNjg2L1hIZWln
aHQgNTA4L0FzY2VudCA5MTYvRGVzY2VudCAtMjE3L0l0YWxpY0FuZ2xlIDAvRm9udEZhbWlseShG
cmFua2xpbiBHb3RoaWMgRGVtaSkvRm9udFN0cmV0Y2gvTm9ybWFsL0ZvbnRXZWlnaHQgNDAwPj4N
ZW5kb2JqDTM0IDAgb2JqPDwvVHlwZS9Gb250RGVzY3JpcHRvci9Gb250QkJveFstNTY4IC0zMDcg
MjAyOCAxMDA3XS9Gb250TmFtZS9UaW1lc05ld1JvbWFuUFNNVC9GbGFncyAzNC9TdGVtViA4Mi9D
YXBIZWlnaHQgNjU2L1hIZWlnaHQgMC9Bc2NlbnQgODkxL0Rlc2NlbnQgLTIxNi9JdGFsaWNBbmds
ZSAwL0ZvbnRGYW1pbHkoVGltZXMgTmV3IFJvbWFuKS9Gb250U3RyZXRjaC9Ob3JtYWwvRm9udFdl
aWdodCA0MDA+Pg1lbmRvYmoNMzUgMCBvYmo8PC9MZW5ndGggNjk5MC9GaWx0ZXIvRmxhdGVEZWNv
ZGUvTGVuZ3RoMSAxMTA0MD4+c3RyZWFtDQpIidxXC1QTZxaePIFEXk1Q16X6A0UFkjABQXlZQwg4
LiSYhIjWuiZhING8mBlARIVERdBqqSI+qaitqEh9FB/bs3Xx6PqgQvFV0fW1sm61Pqr1LaD7D1RB
W3fP2XN2z56dOf+Zuff/7v2//7/35k4QBoIg/ZAShIWMSdJgKRcLmydCzXEEEQpVmvCIefevE/D9
CtTpjPkUCD3UMR9B/EYhCIed7cixPkQP5SLIoHgoe+dYCrO3zq8/gCDBNH6XCddn/bl+Mo4godeh
HG2CCm8xy4kgQ1Kh/J7JSs0oSMdGQ9mBIMxOi92oHxg/EPoaWokgDJdVP8PBZHFqof1RiAc2vRXn
zZw6EkGGD4T4LxwE7pjjfQD6D7QgCAvyQBjdN/1EBF3wKUS6L8FD1CW4x/UILR1b+tiT4cascQmu
QtUlJoMh9UL7cd17ZpgcDoJO5fLCuAw2wzWSyWDXqNF0VNRH479hcIk/Et99qxADQiJ2xILgCAXH
aPpGwev+2D5L6xZca+Z1Los/l1L3PF52qMbl/T7qYjbCEcIUCsobTiy8Xnvo66gjaxaXNQ1p0ug+
QT1fcWWwISXnp9Ih6LtcVgabJ+ivwwmzxpxjA1oij6SAEqcK7MR06QDUjwbwBV4vASKA2YwSqQgN
7ZkI6rU0W3GgofRWh9mWAzQ4kW824kBtt1PSEWhEDzpMqQKpmCwRS8W0E4FMLlekaxVJIjDcGBIz
Ery+Bjp4gGfMSDRKGoGOROE1CYox0ohI6c/i//4GnOv6njmDg7Cci+G5lzOdTuSUBNw1zRKJJU7/
ndxdtfy9vp4Tzmva8tqPRYbuOv3I44MR929UPPfo1/qX3076Q/P3j8p2VjcuCL45O9OHnDbjm1y/
rsOZj0LqMqdUsbvEBt9Mp39TbuWZwMzwM8eFnHnRX1VubUgbd+NOXGC9btWcgLWW0sZxKSumNWyK
PtPpIT7VELOGyYJJ/UZKsCCvWN+18zmjT94o6Sg6s+XBtsJOTufyhNygLWHDL38kwMufixYwPp60
2tDkW1vyYO9+4d4TulXT3Q2Kwxs+Px9VzAm8RIjZpZzaWR79lwnldx/3T/vObckaH0vmc17Uiqby
dZfZjrWhs/VLDlzn567efCTbkJiwvDIwYmVg+cJnWe7vPTz5DOZvMxzRTD/ka9/V5+W3AzqSM+eV
NyWXVQTfEU79/0vibdJhaHCP48H/nMbLnfLfutN/i+LL8+H94nx8UW96wk3gjtkonLDhFOqs/kVK
L4JRWECndJ3+dkP94oqUigsNvlPMF3jFhgqutLnlRdknyWex2Mobp7nvV9dvmDHp1tNOo0K1j29D
f9wQXSf2uHzPPqzOc/xUTpSquEWrat0rSmzjty7eN+XFnpLW9qqG4kAs0cdyauUOhm7jwW8l62If
FG/O3HQ2EL/2Ud2MtX88l5Jo+kA8u2s3k8H6lYS2Tu1Y9fvPzF+eKnKEGYIGJ4Hx24P8jlDMp9hP
wwZN3laaG+Ue9ujjS1d2V11fVPu7dvLoWI/qHecXnfdb2sS65hGs436v/Czl8xMTkk+P0j0MaD44
NE4cHNGy5uqfxqT80GZNyb/WiG70LmkpboubU/N0eag0zO/ZUeHtiztuZMgcyWLRHNTlsQkO7xoW
k8Fk+hRmV9nm7mjdw3jHVt3YgOf2ZcyECa3/lVN/e4QiUWlPwENfZYTcbrXihNGstwCNPZsq0BM4
SM8zWMykCSdIIJd1p+QodIQ0GkVfpSQtRkRGxUTFTEJdjA//4ySkyWhSj1FCQUGBJB8aktBQYrRb
w2EHtpNmyk4UhsvTNfQadsIhAYZCoMazJSI6ryWp2iQ6l6Olo9H4Hj9RSeYcMwUXxJKA3KInSRAJ
xCDNbCTsJKTQy0Ont5iz9JTZbgP5EVI+6kHbcwXMDI1UgPrSgruAN0FPmmDpUXab1Af16jkKNzWe
ZbXbsqSDUX9awxL69bqXQ452otvty3n+W+bhAYM3q8jF8ESg3p3pYjCQhoqTQzdn/f2m38EX1iKZ
ivfUHprbIhmo2RQRfeW06a9RXdg7bVWd+LcaIdjPPjbz4TGHtfLW8S+3h6KrIzJn7dkyPThnVePV
gh84135sr3pcz//Npi/i5zmuPrFPVs22e6sVC/3O4hfiAKc9Yb1lRawXP1hwO+AbsCRmpmEu51jQ
oE519bbq1Kqz8crMBFfRHY8o3W5TY6JiQ5x0Y0fb8o6MI6LNGw+GqFoeLLvLGlJ0zy92y5Ot6XM5
VsPdRYKyUefa/b3IA9wxXw0/eLN5ae6R/dm71msDv+PnzHqyoLB8WzZv6/hnXURAZ+mHhx+M87qV
qQ9Ka90Zm3VF8OmUo/Otqf23J7jBQt7o4lxEXZxz3dF5V8BmogjKp1+92WwWk1ODOstoicF2lqBz
SnyKqv52Qt5lWnl/1HFb3E9813rjf6GQXBxmA/wqRANoJmwG4wV7ACpE6S+/3i+7/iymWwkCow0h
PDYXheS5Y1AXO7oPhkebuthBUD2kJqRkmImiHGRsePi/KIz1LtY+p4vVoDWZSWDECcqcbTbqKRyY
uwuGTjacpKuGwLNxArcZcRHQ27KAmSJBHglhJCApwmykLIU8Ms8wDTdSgLKLAGXCQe8hvPJL10s6
oTdSdEOErYnCrbiNAsMhkxAepEnSAKkEhYvk680WvcFCM3ndW+8GgJ6K5b1to3E0a4XYCt1AHIAr
iAk8Nw8nKXLM6zg7wYPQl8DXYyoCEVExkTCMetghZfk4VKTZ82yUHrLSmfECEQwhiBmBjojkZWhk
EOcoJMw5JopuktKYmOg33AEgs1iAmkaQ8IeIhD0Zz5IAuUKtlWFK3gSZWi1TajGFBiRhGnmqDEtT
JAGZMqlPH07F0jDYhiU8Gq3ElCmxQDtWATI0CqBKhq+YptsdlozJZVoFgKJGq8bk2tSJQJOROE4h
1wKtijbh6RRqDP6xUvbBYyolSFfL5FpMroB20EGaQqmFtOklMI0mA673D+arPCyKI4u/quqewUFF
QTzAaCsioIYdPPBAiRzDIaeMoIi6DKcoMMoVEDDjiC6gcngmiCKeSzAKSVA0UYSsqCuurhjXEDUR
FVxW/UjibZjOGxRw2d3v27/2237TM1PV9are7/eOqhacAud5+AWgLbIuI5VdCARPH39vz7c2Kxb4
ByiUSqEHFZLg6+Id6KqfpadXhnb7KAJcPLDZhdIvQHDznOerV3fD/06CvxPa6BLo7RQg+AcG+Psp
FRM6F5nv6e0t+PrNkzkrOknyVnQquPj5KhVzA9F4TyfvCaji6znPM+itTpexfogqQHB18nFyVyht
BaVCIdPj1O8X+jlcFTjKW4lMu6gx9+PRZeqo3rEYHZOIZSEyQohXx+vDKiomMkL5JhGckjAzwpIx
gWSRqajfGdwpqtjkSCFxqQrjIF6dJIRFCuFqfBTROYkqUVCFhycnvMnAKHVCXGfOyFLebDc4AiNV
b4Gnk61sn71m8n+T5l39sepotW10TJR8zVF9JRG4NYfkGrlGYhi63oOsf6EgUkKww1pigFWF57GC
Dh7+H+dHkuRh3SOpPEhuOrhXPZTjYYWYzerqtErsZDamZyfurilCbIwqzFaITcJc+OfTJXRe8sHv
VDpzzkAuwWqHn17nHv1JbZv33rTApqRFGyzrDgrtsdVfpLul7y5ZdXKlxMPUOLJhsc2LuQ45Kyuf
DJqW2pR/xFBjX7DYY8dZmCZT1syeKuaaWMWB++TnHt62CT/XN67ucFWPzv/r5pK7Wx+1inCh7nHC
8O+KWfyx2vD0iamuDrvX5b7OWj/V2rb14LSpjid//UVrYaflRmMNHoHQ5cn/g/3j3xwG+0oM3pBC
eR72rDksH9bNUh9m9+7GwuEZo6dlaNdr25GP7FHk7Iy5AfwfEic2+FRUX2x7djj+XL9jcv93hve1
c5bP3jNUMxiUkAZxEAZqiAUBovA3HpJKx2hG66PpbTDFdR1qOqMpKSE5MiltReTveh1pOC2BhedM
zi1r3ZWj+vHkiEcFFbKqYnPHh6VOQ9yiIuvzzq89rl3snJ/7sODSrB/nrPt81bCjPxUfZq+CTxfH
3U260tzk8lOEdU3qS79lW4Yc9+l36V5u2Kblnw3YNXqp9IdBw9JyxgQ/ssoKsxiWmky5aSVes81q
/qYIcrT2HSp9L9wqfuG4bX9f9Cp915cJIzLLDj1TDtz5tGWjtjGnpHbUKqPmttsxC0InFXnR0x6f
frw/e/0Dh9s6v51XW5vONceOu3Yq9Kv6pdeKrFTW5zMbVfcKgy6bxhp7ht4jcZ6JJp/sCjW5c8Ci
cVV9ulBtsurgUBFSchpaCu9cDM5r1s68kH8oW3fxZPr9STfGW5dqyRU81TX0+EJipyWnsOuEPsjW
VP/fv79SUzg1sKjJ5dGo124LsnL+7JZdYPl4UGivQA2WD303Tg27G1KCYdr9hLcz0r962MnxXUNu
N2XS5IX/EqZthQX9ru2VVa7eIj432Wbk1Tuo1mgU6avjQuKmOKenfHf/xoqXpgO9CoOvN2TWitF+
jolPM25GTZEuj1QM6m8OH4mvThWV2RSntFSliUdmZn6/aNuTx5rEkoFlfcwyN1wYlTVxzaDay/eF
rKa2idkhaXduiOZlWwsdtbkhlptv7XsqN3YuXT3aL6uPx68n7Xc6fP1po2/LxvJEfVEj3CVSADwA
X8RPwqblm1+2B6KocV/G84QSqYTyUuh1+ajj1TC7XWgX+Y06NzLJwJDUabqf8ovBjveGkXgPZ1vB
HEC88/a+pwsWH/HLwUK3TLxpZYSDv3x7v7lUYAlLwAbmQB20w2kyDvzhjHgFwmEB/RDex/58OA5n
4Da4QgRQMCMZIIjFsBHGwlrYA9M5M7EKvOGBgREMhjEwg6hBAqYQDbvJTfAEL5zDAdwhBxLwey72
PyfT8AkBGSzG1bfCTjgNf4EfYBjOaAvX0fXPxa/ABStKOKTDCbjNO/MbwAQK4RCUQS3cJ7ZkP2lj
j8UqsUH8B2rZgB3YQwhWnzDYDKU47hBcpBZsn2gmpot/FM/DcLS+HFHXwllc6xkRSBAJpwdZmu6V
GC+WIw990Wa0HsUJ0fhCEhzAkdfhNemDoqUC/YCG6waKQ0AKI7HCjUf7ArHirYZs2IQoiqAEjsID
8gFZSi6Rx7Qf1dAa3l/qK/XtU9PxreguPsM1+sIotHY+LIdU1NwMW2A7apbiWn9CaYcOYk8ciCPx
JAEkn6wnB8gLOp5+T1+z/syITWDBLJRlsGb20oDv8NPt0F0R/cVU5JIg5zL0pAvinAeLYAUkwoeQ
ARq0Lg+lANkrR6lAPmtQvoFbcBelBR7AQ4w5HjHKyDgUOYoDmU3mkEDyexJNEskOcoxUk9PkLGkj
T+hkak+nUz8aQKPpCppEC2gFraQ19B79Ba2cwRQskX3EylkdO8+usiYOuDmciovhkrmtXAX3LdfO
PeF0PPAWKLa8it/TsVfnpQsRx4oOYpi4SSxAeYAcj0A0Y8EK8fijV8NxR4lGVCtgJUoacrcOEW2H
3cidnr1jUA1fY5TWoX/r4Qo0Ib5b0AzP4SWSo8dnSkaR94kd8juLuKMsRD+lkAyiIXmkCHmuJFUo
Z8hNRKlDhEE0mC6hKTSDbqI76E56gp6h19ETIpOgJ4Yyd+bF5rMQtoQlse3sY/YJ281KWDU7w+o5
ys3g/LkEbi1XwO3ljnLnuEbuJi/nHfhclAq+ij/Ft0iMJeaSyRKlpFoqMUgzaDXQwRdwDiqhqnfu
k2wygFTCZ6SVcUxDG+gCakivEy13mVihB2YS4PNwt/0ZLXyPXKVTyXwWThYif1oSRUJgFxvO9rI5
0MDHEyXzJxGg5HbAr/w3oOJz6eeM8rmsg7yk5bAU8ujyjjIxmPQHJdlPD2LEZMJMsOHM4Dqdzp0g
ltSG1kiPkGpwlErYdDbDwAhb+9ldNFNpYETaQMV+I7/agpu4zvB/dle7a/mCLIwtWxitWCTHlmVj
c/FNtSVLMgRhx7YM1QJpdbGozVDsSYCOS0lpGUoqgkeZzECml2mmw6SJk2mPDHTkTEr91r7kiRm3
U/oA4dI+lJLJEDpNMep/VrKxU6btY2e60nf++/n/PZc9ux/j/rmFe2uYexufCffIH6UXsLpF/hfo
cxK6yaUn5fCuQeOiZD13iexePL34e/6HuZ+Qau5jgMXyRR/nxxW3JzfDXYMHcPHJ34WbcI27AXvw
qZHQd86nuPe+gU+avfCYK8X9FMbnyKS3p6f7S56uzo72tm1bt7S2bG5ucje6Guqfq3M6Nqkb7Ypt
Q+16a021papyXcVac7lpTVlpSbGxSJZEg4BvrdAYVPuiCnVGqeBUd+50M1mNoSK2QhGlCqr6VvtQ
Jaq7Kas9veh58Aue3rynd9mTmBQPeNyNSlBV6EcBVcmSfUMR5M8HVE2h93W+X+cFpy6UomC3Y4QS
tIwFFEqiSpD2HR9LBaMB7C9TbPSr/qTR3QgZYzGyxcjRKnUyQ6q6ic5wVcHODAdyKVZFa9RAkFar
AVYC5R3B2CgdHIoEA1a7XXM3UuJPqHEKai9d49JdwK+noaKfSnoaZZzdDpxTMo3zqdeyJohHXSWj
6mjsQITyMY3lKHdh3gCt+uYdy1MROzf7I2dXWq18KmgZV5iYSp1V6FtDkZVWO2s1DfvAWM7RF031
YerXcBRDYQWzcWe0CCVnMKXC7oTdVf7+kmqQaaKHFFqk9qpjqUNRnJuaFIXhKftsTY13LncTaoJK
aiSi2mmPVdVigfWZCkgNT12u9irVqy3uxoypPD+wmbI1BaakdCWTXLbpnO7OuNDw8sgSVpH6PK4I
qiQUrCSi4j21sybZDqlEO7rhpRGMoqM4I+O0yB9NmTqZnsVTg8OkKqnPAFeAev8vqzWxgkZ0mD4D
xrJ1srzW0L7EU5eLNjSwJSL5cU6xxm5d3uZuPJ7lfOqkSUGCwweDOLYxrbMZh99uZxN8LuuFOAr0
1FAkLysQt86Ct9mlUS7KLPNLlnV7mOXUkmU5PKriSr6C5xfAOio7l/9rTJVrg2OdlFT+G3Mybw+F
1dDQvogSTEULYxsaWSXl7e3LtgJH1/ojvJUrcJyV1624KA8sOzMhUkIFB/5FfVGPZiUZV6WuIUof
NUV35lvNaLf/l0HZ3CcsSidPwwpl0k7XarlrlbyqvJIUjwULTi40si+VMq60ARs0ufhJN7Z7n7z3
uEk+qg/jyuua8BGequz6HPDVDjEDdwxXICYAOIRRGBJnYIfYATv509CJthGEG22vo82B/kcK9HWu
I5dD/S7EJ4hGRBihIOIIDbEb8S3EENcB7yPOYayHxTPKn4cI4w2/gQrDXtiI1CzchRrhNtSJVtgp
XAcVdU7Mv8VQAgPIOwwnoUKqZTG5P6O8W3Sgz1+xhpfBKXwI7RjbZTgDlVj7DrS1G+qhVzyA+W5D
JfbzM/FP5BDSXYYA6iD3QAD+D9j3CNYxhejjH0IQY58XXLCD34X3dx3c3E/BjzSI9nWIFuFHeE8u
eA55Vn8b8hrScfQZwFgX2nfgePqw1kH+U9iPtBn73c//Dq6TH8AlpAvov1V4BGvJ53peD8HZwpjt
OFYgijAnimQz0r8hHsl7oV66CyHs/8Ulym+Bg2zs8IQfL4zpFMYfxDw+/udwqDDGDJtYLhngnnCd
65Ahdx7vXREv4JyfBDeOzVeku+S7OFYDOi5ADGk/A/bXjmhDdBXQabhCjIhitIdR3iUOQ4JBskEr
xjZhrhG2NtC2GevUUah/d6F+nWKdzTiuvqV4cRc0YIyLN0N4BWAZD/F94yF+5+iUXMKYYxjfzbXg
d9BJ7u08wM+bc2/wZu7FPAUV+e/oFGPJJVjvWwdmrg5/Ts4JE6QSd8dX9fYFve3R22bWcs2zzTZb
lmuafYuRxtnaeiSbvMW3amwtdWabp47JVd6uw/W2mzPVtluI9+paba96Wm2nEc2I4ygzv7qZettE
3cTXJ743cVZog8pKnGVzuezNktu/3FNRVFHUls6SX3s7pPSvpPRlKf01KT0qpb8spfuk9HYp3SSl
XVLaIaU3SRWyWTbJZXKJbJRlWZQFmZNBrsjmbnpdbPNXiCZGRIG1gs6bONayjY5PAo7IHH7d0bV8
iAuFe2m7K5SVcsO0zRWi0uD+SIaQaQ21lHs1S2AkkiU5pjpjZaf2HBCSO3PeWqCaRkJ0PgGhuEIf
hdUsMeKDyqD2EmoOQWik1wKVx3ssPebu8o6+wDOaaKF1Pb0srpVXaHDqQ7CRY+zjixy9LNnekJg2
jNq0rk0zbVrXWmrphVA4QmdqNdrKmFytRi77rnpPsPeAqBpMIqL03PExCz0VV5SM92rhBcEZjSfG
GI0l6VU1GaBeNaBkfCeeYT7BzD41kIETwZFI5oQ3GZj1eX1BNRbQ5mCAxDMN06vSfX8p3Rw0kPi/
9pglcdZlA8s4MP2MjNPMPMAyTrOM0yzjgHdAzxgcD/eS0GAkI0OvhoePTi9zxUacqqjVrvVWmia7
9XnrsltesX4gAHkHivEsLsH3ulIEM7l9bh8z4YJhpjL2ylcwWV7psls/IO8UTCZUl6u94Drm+sL1
MrvAEhwPMGAlc7l57tSs2dbq0tg5w7EjCL/+cBvjpHV5N4hSAnUGIcGDUTQkeJ6rKZKEBIFqub7d
4howPfT0L3oGTI88/aZFD/R4Fj0MLZvt5fZyBza4tuGxws8/9hrgH3jizOun3HXuBj77isE+Bzy5
4i0rkqCmVKwuKX1gZ926Bu6Y7kFP//2WzaRCVDc6t23dvqW1kruxcPHNhYU3Ly5wvjxd0E/H1v+z
n/Y/9mOXEV5Zfn/5dv4JBmwVrUEpzwvITxd4EfkfoxWEIpSewPsFnsAGMlPgOSgjvy3wPOoXCryA
/MMCL8IGzjwyNZk8GEsklXeVkbGk0j9xZOIoqhT/xEuTEy/Fjo5PHFEmDyealEDsaOw/ODWzzpTw
xOFjTPPPFSt45gH1GVpaGugCCSM9BcecHIWgzPSMkmKFoNTi1KKy1BR3T1cPT3/t4MrcpPwc3xD8
XIYQhkqGAoZUhjSGRIZkIK3AsBKIQxgywGxfhnyGPCAugapSYHAG8oqAbBCZCBTPBKtQAIrkAPXr
AVkuYPFECk3Sh7tMgSEYKJPDUApXUwwU8wTSEPsMGSyB0IBBF8oyAos6AnXkAOkgoJ50oBtKwLqC
gOYVA3ERQxmQTGFwB5rjyuABJP0ZtIH2VDLkMiSBbfMF2g9SnQ60NwfoviICaimRhaTOA0C7WMGp
kYlBAOh/ByDrLSs/WAQkz9TAcIbLtS+e3+YrhywHWHixxx5rEL3J58rD////2XE85+AGcrlhKR8A
zYExzQoNCmVuZHN0cmVhbQ1lbmRvYmoNMzYgMCBvYmo8PC9UeXBlL0ZvbnREZXNjcmlwdG9yL0Zv
bnRGaWxlMiAzNSAwIFIvRm9udEJCb3hbMCAtMjIwIDExMTMgMTAwNV0vRm9udE5hbWUvR0lFSElP
K1N5bWJvbE1UL0ZsYWdzIDQvU3RlbVYgMC9DYXBIZWlnaHQgMC9Bc2NlbnQgMTAwNS9EZXNjZW50
IC0yMTkvSXRhbGljQW5nbGUgMC9Gb250RmFtaWx5KFN5bWJvbCkvRm9udFN0cmV0Y2gvTm9ybWFs
L0ZvbnRXZWlnaHQgNDAwPj4NZW5kb2JqDTM3IDAgb2JqPDwvV1szWzI1MF0xMjBbNDU5XV0vVHlw
ZS9Gb250L0Jhc2VGb250L0dJRUhJTytTeW1ib2xNVC9TdWJ0eXBlL0NJREZvbnRUeXBlMi9DSURT
eXN0ZW1JbmZvPDwvT3JkZXJpbmcoSWRlbnRpdHkpL1JlZ2lzdHJ5KEFkb2JlKS9TdXBwbGVtZW50
IDA+Pi9Gb250RGVzY3JpcHRvciAzNiAwIFIvRFcgMTAwMD4+DWVuZG9iag0zOCAwIG9iajw8L0xl
bmd0aCAyMjgvRmlsdGVyL0ZsYXRlRGVjb2RlPj5zdHJlYW0NCkiJVJCxbsMgEIZ3nuLGRhkgNFU7
WCzp4iFtVbvdCZwdpBrQGQ9++wK1EnUAdP/dd/dz/NS+tt4l4B8UTIcJBuct4RwWMggXHJ2HgwTr
TNqieptJR+AZ7tY54dT6IUDTMP6Zk3OiFR76/mkvdsDfySI5P2blKL++s9ItMf7ghD6BAKXA4sD4
6azjm54QeAXvYr9GBFnjwzY7WJyjNkjajwiNEOJRlef5RQF6+z/P5B91GcxVE7tXS6HYBjVSSKlY
Zreq0qX88ObKLETZcF1DtVUMOY+3TcUQy+xy2K8AAwAZ120oCg0KZW5kc3RyZWFtDWVuZG9iag0z
OSAwIG9iajw8L1R5cGUvRm9udERlc2NyaXB0b3IvRm9udEJCb3hbLTU1OCAtMzA3IDIwMzQgMTAy
Nl0vRm9udE5hbWUvVGltZXNOZXdSb21hblBTLUJvbGRNVC9GbGFncyAzNC9TdGVtViAxMzYvQ2Fw
SGVpZ2h0IDY1Ni9YSGVpZ2h0IDAvQXNjZW50IDg5MS9EZXNjZW50IC0yMTYvSXRhbGljQW5nbGUg
MC9Gb250RmFtaWx5KFRpbWVzIE5ldyBSb21hbikvRm9udFN0cmV0Y2gvTm9ybWFsL0ZvbnRXZWln
aHQgNzAwPj4NZW5kb2JqDTQwIDAgb2JqPDwvTGVuZ3RoIDEwNzk3L0ZpbHRlci9GbGF0ZURlY29k
ZS9MZW5ndGgxIDE4NDQwPj5zdHJlYW0NCkiJvFZ5UBRXGn/dcwADArMwXAq2N+AAPcM5QgzjDMoQ
zpkBNRuVZmigzRzY3QMSNxtmTEAjiouoUK6CGlRioga1gqtrVDxQQXDVqOW1Gy0PvDboRkqN7mtY
BLSs7B+7dldX1/u+3/ve773vegABALiCUsAD2WqdZpp/leIulNwDQLIvTRcmJzsKpgLgtQXKsgwm
otDp5canAMRXAIBUG4pYTBOkcATAG6qRHXmF+abWhxJPAHx2ACDYkG8sybs9N9cKgLQVLrKqgCRy
Wy99fgeAaZ1wQlQBFLgCB7hWgB6OxxaY2PlJwS9C4Hg+AKJ0o8VAEIGz3wcgNhvaCzYR8wsFB/nb
4HxoH2BmwkSeKJ+wEoAp8VBvKbQwLNwHfKZgnL6QJgvtpb+MACAQrs97wZHsfbk/kDTAvyfofSRr
cbukVugUXJZY9mQY4oDW2yVfQlEZiiAyV9xF6NinQQUCgGcLRROFCB+xR6MIv16Lp+PSQZIRGwJK
R4C43jcN5AAGWIARkICF32TuxbGh9vjuXsxntR3kgh2z289sdzrEa6i3u3fgdjQetyONqDvvWGX0
parAa3F7/b61P813x4e94omgkA4hE+NuQl4m38HDUWNmSdpMsjJvXMKJRB6uWSRN6ah8sxTTmA2h
snBcximcPYL7FZjKYjKRtIEijJjOkscWEzSJpVtzjBRTQNIMplLiAd7DFFF4BK7Ae58PvYfBgQyP
lodHKiIVH74LCra6wftGBIBnWwpw22LUZgMtZyhSi1TrtwYezfHZqc88oi5PSIo99McLZ863lpYt
veDys9ef2z5uDGqqLGKqWo/kbIq7HyCw/tMDGD1TztYsd9hPMbbmnFRZwOnnx13ufrr8h227pmXc
s5zKjUR//DRfUPxT5cWM889W++6bfL7YdlR1pfvKtRMbFy45qTz43ujExE2+KA8G1Wtu4UFeu/ft
sM5dvKHsr7nzWzbLrbT46/GodzaefD0xwnePNinDp/SFLmTBOVnFEbJWqQzr3mb45DZTK1nuN/KT
JcrOZZM622Mi1J3Wnq55h22+Md6RSduOTJbfHNUsOLDiH8diPrrwZEVM7vL7+lMnzpzpnPOQv+Yq
ar+yKOi7lrSG9nm5srg43M67Ab+Ueh6KoKgYPP+qoU7qdmAPryZ8+AK93n8wZT6MJNs62Ujcv89p
Xq98o6etDIulkmyxhf6436vOb3hVigf3KcYMzKRMJKZjCVMhZc7HdCRdRBlITGuxsLIIXN6Hnpia
hiVrlFM0yRr9TEypUiWk6xPUUizQEKSIxoau0RuHCplMFjU0DqP649DW9Pao+8/OnN+6s6m4ug/w
XnFxcWgRBDEQFGqwmMJgHbEwFGuhS8K06UrOnoUuDMVySjAtmRcq5fiHJuvVHOcYWSgsB9AOz2Pc
bxyESonppstgko9+PbTtiBuAchFqRxBwtuZ2ftVBk3jn1z2bO1qD5Ue7utukm/4mqPP7rP7W/rC0
OX/vHN5M+3Q0Jngo7/mGtcSfrLopDqlclZKzumH7CGFYuOBsfMMVf79zOx4380znyp6l/TjHXXP1
+xsir1TSJWGM6NjLuqogcawtumpq5641M8Zka9uf7HRr6igSFS4aQ+wpbz90uelU4XfC6zlN/xKL
bifSx8ubop2O6qSCoJVrfqhI9JELxgu2fyONWJiempSEV+Y0rEMlXwR0TZw2r/aBzu/qsISM9sfy
hoc31z3/+WTPRfmKuuJf8O49X1Rpz9drFF23dkmWHaoMv7l4aXV27cwNaJZ4Ss+4e7fENS9slTWL
1kh6s2ujrRy3fY57wJP1H8d3wUVCR1hxBQIHniOexgkxfiLOedA5uywRKetJQBwQBI/Ew/txKOI1
oYBlC5lJYWG/4d/eUubvwXfEhQjyEkUA7swJ3Ph8Hio88FrScHn+h661j6r/pNo46i+XHpU9WjCD
X7LI52nTB8b32xxGzT7fEnlyxaLHGar7IY3S9fOOHdvNk427c1z8bKzkS+ani8kt055Z7S4BIPb+
3c0r07LzDGWJuVcDh9Pb5sxYJr5xAF1CZX7vGxix1We7PP3s7+MSHk+s0E9d3Na65auGBp82JnW8
gMXtojr4Ofblubu1e1nPlmddJrF2tefKD8iPXk/zd9MwYH5GwPdVosrwCNmrhmFHZv3fSfzPEnoy
HtdnJ1JN5VMsXFCjxlRGgmGwcCwES6EMtIWBFAZ4ZBFGKpdgKYsZK5LLnHEnbr7QA83UyTxwMTdw
9BBNJ5gCWA5Yi1nmjrv2HYWDlsw1Wcy5sgB8RG8R8ZQMmFdBjha612y/3vktety29o12uQQW+HKu
XZ7T3Hm5X1g7Pibnm62ZVSv3HtJu8Fv/61b11Ou/uxy+hjjdtC8/3iUuvbh5p+uDPZvdGHXm7geH
x/bsXDv6Rs+M6rp8nSPrekr+iCkdN/za3qeeByawLSMrxae3HHZJDJnVpJgcFb/i24rLnTMzGk2H
HTPYiebGWe7m55OcttyNXZgxK3UrivA22h1gEDhk9Z4MTDUUH5xkgnrcVs2NEL6tAvb4UvcFq26c
Vv1aUPMops0c2+1sX294B1Fsf/PqNYpjxYdVge+Ne+LcxXDg4ufFQx1KATx2CBHxhThXLeAVjh81
CCPiptr5Y6B4ZH1Q6X9VkVTpuvV2XrPNztulL6AYzEDSLJVHGQiWxKjewOWcTjJc9NJkHkmTZgMp
xQhzLkaxDGZlIIzBGJamDKyxRMRYc+aSBhZjLVKMLSCxgfN4ZZeL23SaMLBcl4JtiyVNpJnFAiGT
IBGkyXAArs9hRBFBGYkcI8dkqLWBDWAEO0n0to3GcqwTQkzQDMRhcIUQmpxnJRmWiR+Ks9AiCO0H
DnWvFJNHKsKhRwnYz5VFJBSkWKxmloCssiiyWMr1WgUsR+GiTJ0S4gpLaCq/gOVuGTKFIuo1cxim
NBoxLYdgYEFgYL8mc0MxVYJWr9SkiqYrtVplql6ToMPUGp0qWalJSVBjylT1oItMsiZF82/eiwWo
qSt73gvhk6AG0IjGz42RFQeEBFDRcVxC8oLRfDAfDWzZJZCAoBKHX7FuFSlbmUirblfs4qr421XZ
ri+d1h/qwtbRrVbXdupndBRsdeysOy7q1F8dsue9EInoTtvZzr7vOfd87rnn9+7DfUyKiOM26U05
M4ltDkPsVoaYdQjqrbw6vU6vUdsYgqjVZtFrbIY8YrVnz2U0NmIzcyKiBYxFj/9lphB+vdlEci1q
jU2vYVAOFRgZkw3N5qbQW612nI+o7bY5ZgvaIgoaaQ2ugOiNuQZ9v82MI9fCWK1kYFXoBJPGYNdy
WgZGRWi3kbFo5iAaXKXZQnR6m4kT1yGsJrlqtFFjN6gtJNduyTVbmWR+koV6g4GYzDZRNsM7ycDw
AhqzycrMt6PxerUhGUVMept+Qb9M0FgzrspCtGqjOoexphArw4i4dWKq8Dq0DHIZrOhpjQfbQAWG
zFMyOBdLy6qwQ7hdpMJTwaVVSZnbZQ0UgroaK6OoBgtI5K5DeT65a51LatykapET86DCU02K3KTY
gyQXr8RZRZzFxTWVgQos8VQu5WtGVBto+8iBmcpZoFeniHZOq8/4IWUeHF/iKfWklJaV4A/geK6V
CMIaaCkisXgPxVv04hangXoibaD+9BN0BvI/dobQboAlT/7ropH5x5Q9+QnKnnBlb3MvSSFJKpKY
oZo6mcyYppqSmZmufLEbkB/dDsir2wHn5JfbQdvQ8OiQ6FHbX8RpJf5FSRN/4FeBKKUhnxZZ/34V
r1dsUdVXpOtiZG/tI/8cN3LciSrFMvrk5bKrzlMlc1onP+mRXnjWeujxLdXlP3orpDdO7flghSh8
a126m3XM68nfvK2ipET7rOtKgcuxzn/hHVPXtJ8nSbvTPG//tvzy/AdLH8ySHjWY4+fWbLnb8Owf
R2O+fjoy4uOb2S1yWdPr7SR74+Nu2Y4CVUPYTO5bSGPK1vwfvt2v2AVHh0cGnEILhdC2+u/KUc+9
FCVQhX7Jw3BzNYCJVYO+88rxA4JhqtgwycL0c+KeSUe68jUzvY+2rviFckkIe7Tql8rX2jLq00AH
leCEClgMS6AM3wRywAPVsAixYsSyEfMglSCnB+nV2yfWT+ByoT8VlgZ3enwuVFfWuKuXL3OnDtro
ha2utx482XL37hj35/Oyzl2cWHp61Nc2Ny2yNe14z1HdYV53VvzUvq52vX3W9GOFLd7hXabtxrlN
NxW7P/u1TpAwXtB7KW31cGrkuT8PSaqLjj11KXFz7YWJt1oK7inPDV1pLzgu6340qS3t3b4/HPjX
iWHXL+sOp1/f/2a9y7Lhm8i/FF868tUVw/YG2oidSj/gpnBVA43xp/n4r/5IuXqrarxybCDc0udR
tVXWYCGb3NWveyoXB/NB/FI+YI0ECIoBybKlfD9augx31MSKFco1KIvHU63KUKYFuJNM5pCKVGs0
TC6WZDJX9TOmDyp5Ogae7dq9LXlY52HB++myFTbb2EH5k6eMD00f8XMkgsLseU4Rqobx/z4qlTJN
lZ6WkZH/UvZcliWPe5BOj5tXfCw66uDBvsHxbKDg/bmp4vd+U3L8yKaenQpZ4zVDTkHvpPXV5qzR
07WLPyvoyekZGtO0Z+WhqDEtJVdad98ZU3Rpb8fVTZ0dM/emDpV2nfki9sOb8bfPL/z9zvzffdnS
0vjvnWB9cN3SOGTPesk1/caLu8LOrfjCFyN7w+rcKLUdVdytbl8qMWq7P+iIW3521XK7cPIIv/3p
nWtXb8WT27dPz+naZPXqTo+Z8J28vLM991PLaGPZAeOxxZ/e6Hq7KvHbfaNPTP3o6qOFxVE7arWr
N58/u6rj49Jn4s4zb375dJUqq+qq8fjJnDvs+u5tj89Pfqta1Bg9W/cJO70u/R1JX33BlXStT943
rmjL0U96bhSl7O2GZzcAD0rwK2o9CCFS2CpMR7wp8KYeQgkdGxlOi4UCmqJpOgyAXgMhh96mIZAF
5Dta2Nq3gloWYaeOEYBt3Zc4qtAOY/qfhQE49BDcx5EVAP6bHDbw7Gv3X+alEMK3EyS0398rXAjD
6An+e4KpMAz57tFAXcTarsNa3gBn/FMhFzY9V70LVsI+WAsQCYH7e48I/xOI938DLf5y2Aq1fm+Y
D1r50TqY7f8bJKJNW6DJXwdH/dow8N/HXpLq/xyK6JMobULMgPQSWA5iPPPhALRBOzTzVuzGczO8
229VM743BCbt60CIO9dAA3/WIbQFCRtgP56vOlZRf0UNeh7uCQxRFJyFff4FYPe3wxZ/MZj8H0IL
eJF0Hk83WmcFi7BR2AgunCM0AjGUD2phBOrYD4WQl5U5I3P6tKkZ6WkqZWrKlOTJiZN+ljBRMUFO
xo8bO0Y2elT8SOmI4XGxMZJhQ4dEi0VRkRHhQvwVoyCZYuM1DqacHaUpZHUKrUJCWJ2p15jKQqxM
rohJz5sSYGGFSSzEsWW1LKT6ICuTDU96gW5iBQmS+3IUMwbH2dEah1wuY+kEvPRIx2uuk7hYSS6O
IwFyHYf8DzNZUaYMbw7My+P0hU5Yyk14GBOnM3RKE+WV+HSjNFoWhvtA9xULIzie3kxgYRabmIQT
ShBCXfEozlLD77NUHEuNMKJ9r1gQBwxaD+MqVzCuMvSLq3DAM70BvwQZfWKRRqFxi6Ykg08kRlCM
EDIv81G62RQP0Dpmpo+GyCHoj1jOLoa7y9mstYUIKLToCKTEDVAO+TubQ0mAYkEoLgBRbLiGjeDn
JWVslpOFtcSX3OltPiSBosKkaJfC5XzNwQqcaKMPBAnMIhtiqB/vwkWEDUPl/EOGI4RZRLyIc2yF
+FRoudC9ahyHozSONfJOGRuLb4aNSWJzkCPnjZsygZeJLyMc6vWuIWzbfEcoVc49MbbxaLCXUaBC
VMaUZ3PxSQ3GIywBL72L87qTsPVF5YHEcTYHc1PulbC6h3J0v1zOh6nfZa7Ccs7Kcie3MqaceNe6
+dU181bzDmMWKZgy5/dxeb0MN73TlR3QrmGzbPwLbPkO3iXobG1e/1A/Qz5nOUcp1ObJA+GZZ3Fo
OMMUTq0sYOrzkcL+ERxggkTCWaBHBSwpJixYHApkzeQe7kzwFmfyC5bnUSiVOyDFChMkCuL9Ftj/
cF7tQVGdV/zc1+6qwK7osixXvCBg5GFQsRsqGBmIJJapKHphF9tmBaQoOtKieYwPSAiJrg80KgNO
SDrWmU7CHy4GdQU6Q9N2JtqkcSYFU+tMHzNOmyap/yS200y5/Z1vdxklrX1c/fE73/Oec75zzndX
CmZ99umDPVtjPbYc1xfEYmVWZTAUqszKqAwFQ1sjVmdDVoYrKzRUVRVqWxvM4FTEqog1ckQPVx4N
hF3BFmkVTotjprLGv0bPnBuINzfEm4QgRCgi6EMuvCMzkyPvSKSMGtAId270R9sZ1KBfpLLCfHgu
yCPj8RG3ySOd8ZHp5cEsuHGYJJQ6d9ixePq/05Uyb23LqrCU8pDhbdHx8LwKv6LLgagk6wpLs/OR
xqVhTz5kOSeCgoFiEYLXbmSFXflhrcI/rpcGMlxzkebs701ZVRvr/RlrQ9PnFu0p1qdD0HUj65rE
1YXmu8JSqXi3xAVFgq9Q9TzFGFzK5R6XlTlVgXtt/9SzU32O5cKA+x75tCPWJcexmAZwb+/AnVYG
BLWfUhXu14DUTjvkALUCT6P/B8A+zO8CFgInlXMW920GxgBeXwqsAfxAC3AM+AbP4fm8FvJh3gcY
UudQrnaPatR1ZFcnaVA9R6a2FNwAuGgQsqll0yDWDcr/wF1vp0HlExq07cNYOZBApvp8jP+INcfJ
rfyB3OqvqVetIrstRI+ouaSpbutTNY+KYcc55Rw9ATbxqbICIGBMLaEnVNzPygitV6upGnPXy81k
V/5CK9UaGsCXRK80Yb2kypBv0oCtiwbUWmAJ5leC12H+D7H+MrnlZyxLNSGfpVRtAy1WmrBPDc1R
GsV7n1FJGgbnwv6dwm4G7Gabp21i/VmnfwGhY96DgH4vSJPWCeAN4G/Tus0E9HoAQ3RKHZL4fH6u
Dllfgl/WTOmkOLMQFdmWUa1AMUnQex989Ve1iQx7mXUHeq7Rhulr4iybqETgIvAk9SqfUznG0m29
VIT++fJymi3/glbK47TKlkOVthHE2RLKxvnXcOxhjwGeB24CF6l3KAFza4Ag4qOHYzTuK/aPfZhM
24ewZ4iuI04VfPOdBXjeWQbrBB0eZb/z2dOtqX41TKp0hWqAoHIbZ/Ib7Af76bciB8R6x36qEu/h
+Itzg4g/xL11CZwIZtvNOMRZxYBzeA0+GgbeAq4DE/BbL7AJKALmqiT38RzE8RLEkkfELOKG45Nj
hOMDcZ+l5sA+6C5seAV6VAo/cd68o6RC31TaCKy0zyY/0AzkImfSOGc4bqHrqem9EV8ibuKMGOcc
5vhn+9UW2MrxtW4Gz1jHuak5qFrox77h+PsPHNfnK4y8VmusCDgXOeaGX99C7J4BXwcPgyfA49Cz
DX7dpt5D7p+nXq4DnItcCzgfGfDlUfjy+1wbwPXMcpfoH5Qv0wDnFefEV/i71CP0YJnPEjkyk7mu
cG7H+Fsxrpj2bYy57nDuC34jxlwLODY41/5L5prFdWP67ONxEech6aP4+XAeci5xLop8IusdkaN1
1mfiXBsst5ZtpcGXNi3B6lXdU89qXqtHumbdjtdc5QTsvxCLdbyD/cG2c80VPn4edTRWb1Unzp79
8nd6m+uu8jFtFvUWumofUTPXWpuH+jUvreJcEXX3TapWjuE+KEd+XMNcJx3iPpz5eaUVOnopwOPy
negcdTk1Yl6vcgtYT6qoJ6ilylOxGlZJj6ulyO8B7DGf1iuliGPsqSnY54z1sfY96sVvwoCwkd/F
a3gcfdhrUP0Tfte0gC/DjuMcdyK/EzmubN8mu/2bGLsHvX4FTkW9yaaI8BV+rwl/8do7UX/ZVoPr
yaX54B/fDH/F/KjNEn3ibhO+4j1jvtLysfcoNdhLKGJfB3nKumnbQ6Nqs9Av154M/jBW+1fjfl1O
5+Xfwx+TlCpyKw1+OUg5wm+A8i7wEnm1brSfAtj2HHBl9G6Tb8B2xJQmUw3fS2oG5v+Zdtky6bxt
Mf1IdVk3tb04lzH0v0eLtC+wdjZqOudzovWBePd7OE/Eu7gTcdeIXJQp1ZaMuUnWDaHDk9YdsTdi
i9fEY3omx2Oca7ga/RY5K+3DPf0KpaP9S9xJk1y75dvUql60vrSP4VOwDnfokJTnwLmp71N9rPYt
ArgWNqK/Gmv7Y9wXb8fkfdpP6HVx37yPPuYJeZE6IWnaIGJnUD4YRVy+n2dCGo+OMTPuH/tf+/8f
yJPaIL6JYlAn6FWGPInvMwDfeJvtn0jLgIw4Y/xiDJ1AHua1Yd6LDLtJLhvR58BurYxGgMeADgB3
GOWg34zfm7h3KvieAo7j7JrKbkkkSTRLUijZ257irJXM2hTPArPWo5u1XleztK0ZzW3NHn1bs9fV
KDU2odnY5NEbm7yugBSoRzNQ79ED9V7XFelKBM0rEY9+JeJ1XZIuXUbz0mWPfumyFzKo49G03W3z
3Qt2t7n13W3eHa2Qd7S69R2t3pbtkFu2u/WW7d7gVsjBrW49uNVb54dc53frdX7veJ00Oobm6Jhb
Hx3z3hj93ah8dQQdV0fc+tURL2RQd2Fa2ZqCIl/EGi9LKi1Y5it7bkG6r+xnmdmi68f7c1b4fH2Z
xrW+AuPdvmKj6LRprOjLMJYBJ/RM42x/gfFmv2m8BvSfNI3Xu03j6TMFxuCLptGw2jQm+0yjbPWy
Et9qCPv7iow+DJ7pKjBOnzKNk6eeM04dKDD27C039h7OMYY7CowLwNHDBcaRw6YRAh8+YBoD2PRl
4LHSAqO0yzS6IHd3+IwXO03jhQ7TWAN+HLzlgM/oxPqDWHMAbVjwdoevxCc4Lz/KC6OWjXQku32z
CpY68/KTluQ6Fz+SlJ3jXJSVlJHpXGgk6QvSE1O9aYnuXZ5Ed4onMXne/ETnzrkJTtfchITEpIRZ
s+ck2OyOBEVF8ZPkhAXlmYZUXmB4ATuwq9w0dgIpkF3APEAFCm09trs2pVDpUe4qCr5PFLmQeugu
KU5nobPaqfQ4Lzg/cN51qtH2bqeqlzgM5yqHoXzdYVCxw9hQJIWTq6hqc3l4ngTeVB4uyq+KOKgm
vCK/KuzYsMU/JEnHA+gNy4ciEm0Oq4ciMii5on6LPyJ5ebhbR5MnRqTO7mPH9GkpEMhPDzdVbfKH
29ID4RUsnEgPUD4eam/fg3/t+Q99hmaxGk015dJ3Hj7x3z6S+Nsewz/ZrhLgJq4z/N6+3dWxlrTS
anVYsrGQLAE7IGPJLE49aHGJEzKkadq6hAal5UiAAOYqV0sDiZBLTQoBIheSOCEECEcS24CNTUhJ
CZjSI0Ab0jI5cMBk6AwqNdMZGork/m+lZpJpPd6315P2+77/+7+3+p+/Zf9v6/B01IEUSidXfDoV
pePOdx7pRTyL6jsNqL4XmemRgOp9uBMhl9jZgBZ3ooYJHdq9qGPivR2C0mEO1ncIwXqUSHgUsQ5H
+ZIOHi4ZgvXTaHDT35MGBBlBYIcC9oC9EgYMV+6s49C/6R7BAf11msoP4YVoAC6t08pcTJhhWNFf
oeLCEAiqJwgmmjOkEupGh1FQCeEw5ts5mRgDIZXpGfqHZqYHRHT5CrMEo0xnsSxu5+C8y2hSOc5g
j0WVbG2U7pQYVCmRjRVOloytolIuqZRJUArW4IWZxhVPDPwxfx3jAUC4BWAuRv3AxaWVkHZGxu0M
yzHtHiWahS8ZW1Upw4cWX+7v70d4aGf+IHmMrmBI0SQPcz+zgSHYxyBmHZEIWod7hrKHN2OMo8nx
2eh4+IIEPD0pBXEs3EzGN+cP8gdg4dOfSW7p+kU0i6Gdl5l2YsNcO8MXGfG8kaKvy9UBCAoDAwyp
AOXyZXKrv//uzc8+A/ywGpCbgMiEJml2/vkKEzaZGOzgtjHEYKB6HbbYC7pZjWbQTeDRWmzGXYwS
zdUV1IrSRzhqo0vgMYGgPSAH6Ia/f5BMys1hIrlLXGNr/uEWumRPGrpGjrBW5EMj0Iua+QUZb/Xg
02Ec7hm6rjntsuqUJLs/Y7HYCZJDGc7lggJ2mUpUewaO/qmFHbLqEiMRv8WP0hiTtD9dOqr0GCM1
O40i3DOKMNcZoFW32OxqIPWKERtHGt8GtMksrWs0C//Z6mhWpOBRQskqAD5mr41mgUFMSY6tQkmc
DATDET44PFwTDwWq3fFwODjcEHEEql2y3UnghJedrlj1uJo4OfKSyTT3zoFuzOLxo6ZXrpp5M7Kl
Bv/iQvv2H1Ufe3/RvE1Hq5ovHHlqx2l21Xyt24vdvQP5787HO/mfLH9g7vsb/VSVh0CVQ1ADqkuT
JnqrTBaV1WDwEcLIHsrGJMmqB/SwWXqGzmvlcM9icWQEES4LohXZrEyzNY3L8DFGThl7hq4ctdhU
o18nruiURTACsIWCxRLAORaNAVNICXuwBogyNXFHrNrtxfGvkCOHNj95sXPgytvdy3YtWP6rjaub
9nGNdw6++Vs88up1XLMXZ3Pu9M7zx3//Qc8aYPEtYPER1NaBStFqreS0iOd599p+ZyMYUftIJkFF
yC5t1yzftjAWi9ueYSmzUUBhNotZlztj9sCx2QPQzSJqxlhKWfyW40xpqTVl8BkoF6gcDDHaWoqS
TSSVLFQuSUunxAqVw24e+KCaOIpVO6QAZSKNYYCUgYzfOuJ627khhM1n+wZJbvi783/TwMTXTF3+
mhmPLn96Pw7eGMQj83/P37y2E99pXJ/ct4lmVDyfInl2KxqNatF96GMtlGFfCnQbuj2XglylcQPb
athrOOo5VdZXfuobxvLyhmZJSozRayba1TEZkymeoGce8GMi4/Wj7RjHnXArnomIPW7s7hm6cRSs
i3F9yk0nCmBht3tsSuQx7Wat2mhU+cl8kvF7YJqYqqgIldelNvvP+Rk/tbvfr6ZCosOpopAYYkL3
h6ZTt+ulTmZjIE0WbE8Po4Vr0K3QsxAKCnW9QifUeqM0Z5JYBp1cshMUjBSN4C5nZDFAO0EtbuPA
KONgwNT/xVnky4YIhyNh8uGCySUz/nxoRJlq9U1p+sObe5bm2cFPXpj1bKr/1aVJ28JFQr5u9lOp
5LSWNVObup595q/aopY97HM/q564eH1LHy/UjKoLcVzl2un5y1tWb1Mnzlw+4clXW99VZk3J1f90
5uy1K5tmrs43Vj36YOPkqdE6kWXpWtEGxeqCLpLRFM111njG8QVYzyybclZstfIihIuo1wF6h8+I
IrxxpJEbHWMs5rTgEnr1QNNDG5QBgZKxRB21FCSa3v+8bA/aY3YgDoqQrjbf4/WrX2trm39m2sYH
fMzjCxY81Lc318815q5+2LB00TO0r1sBVkJPewNSDvGygZbTCelssDEvE4TbGIZL80aePrtg6mxC
SRSzGp6GE/t3t3GNb72Vb7trhbzXOeJ79G+UNQHT36NpCB798/paAWBj+J42+FBREe5z6MjhaIOm
kGHBYbFhpLK0pvR06ekKFgtO2e3wE9lmo9rYbLpEfKa83AuO1Fxms+oV/X5zukpYJKwViCBIIBhl
4JIk8Boo52qW0k4N+DiDzl49abJ00FuyloZrnZhVoGMTbtBSF/Prasa/lFUGWV1uOrhk7vMdvrkT
f/D69rUNs59v/fmSvoXbXXP/MufFKPPjGTMe3rM/d4bZkW56Y31uN7l18tNNs2+t2LERFfPnErAV
oKrf67rN4pIMwL1+GFjRvaZAriCXI8N7KE+aMrxoS80zfWFiTF7TcQjOJ8htwhAPKS4XsBViBjba
HhyNSRorshNFvmJ+xnD+b5h/78Jg/u7JVbsOLF2+a5cPxwcGcUX+wtUb+YtP91340zsnzn30DkXZ
Bm8A/wKUNOtXatYzdox9orUK+thqlShMKzS5lCkRTVa1xGVjadyPpusB66Vh783wImPb58Ku1FlY
qsuBhakMwIuINIMX/AUvQNrrLZ/UzaxnvlLc6ylZVByIQDJGvLgcx/7LB9zzy/kfHP74SuevF9p2
T5vzynMrH8vkD3L3nerPX7x2O/9pFx7MDyxrPfLJiXNbCx5jNrEi8HlUs1oqhoVULFtZbdhwlaXi
O2W679cqBUqBsZlM5h8aRLPm8aprzZfNjFk0P8Lo0G1F6DS79LevBH25KCBWqK/lCYDSLdMoB5At
k7c96AlXPPMGT27deH0W23ryZUAjgwdWgLoVWNDsvaZeb5eP7PX1mrt973lYHwXyTZuorvfgFgkL
olCiRspivv+wX3WxURVR+Mz92b1399Ltbrelu1YZJBbKStEusNRsZUuFWguhgUrxp4Gl3bZLf7bc
3bY2WJAQgQiJxFB/ohACJqaivqAGE5PGBInRB6KJD4bwArEvpib8mPhAt34z3YYa+TE84IOdc+/M
mXvOnDlz7pkzZ0bc54u0NzQWMEwjGgz4g8FAwBw12QUYOObzRYzgh8EvgooZ9FMve40pTGaROM6Q
gAzPK/L6RL/UVxDxxfDRN+JnPv+wJ98wA0GtxPLt944gku9D9PZHSs5O/hkrEfnM1hJW8mjJ1wrb
T5YBnax8F8L+PktkOSZcgKz5lvDDcGh8Kmuxkb2MNy8d9/rmVsI+Fc0i9VolDsRmpC+VzV4kLzu9
4QN55aEDeUPnZDwP4cGmK4gUzRf/d+HCUhm/eYFzynXnztVEsOeFb1cw1/aDn/48dPT706xu/ZGn
v9m269i3bPnYaPY95pg3uqVhgC8qPpzeczo7Oe/4htrehxesvH7oNDLayclflXYtSwX0cizgcrsN
GmbMN6wWeZyW813Dk5fHWKExlT8aEcPwWx6Xy/S8PpWo4mRz+GXqHQ0vlSlZCK+IHePR/KjwgnGv
TFUeK4SaAbZgeXgVgyss8PrDFUr7pqrsxTNnnG9dvnxyRderblahbNuVzcve2DWx/wN4QzFOhL2I
mw46HFtn6UxnLkVhBvJYRWeVzKE7qoj5ESmRsWtRVfEj3dJ1phTisqN6wLMypjfovfoJXdN11TEP
Ig3aomgyHXYV4z7hVJtwI1mJzRaG31b4cJDC4sWIdtFVWNEBHT9j6NyB8mLRhMRNohnbjyGfh+/s
zZ46lX3nMxZgReo1EeBv/qAuF3G7FHG7DHpbrPIrUicP4sxyRdxROJchKnURdpWJrbTCdXbyaixg
mpFCVsqUoL5YV8oUVqoxXVCZoPaD+rHCNrP3FeUj53f6eacKC1gRtRjGtxixKrfld7stxeV2nZ4y
gampWpVh+g3DdDp0PWI4gTrxazUYT9NVp+mySHU4PApza7qR72ZuN6nceMJQYFtTVR2WPCe4ZUUo
hnOEYvn5qDAhwsQWxfkm9sMcR5OIsjCbuI1Ky4XDODi8PlGFw3hgx7m4hOG9Zcm/GTTXyAta886d
qFBwdxMSYWRVhZ0LCvDoZdlLey5f2Jv98fjFn9JXrghzK79P+NRrEx7l6oSl3CBRCu8KbYAhOnFb
OH8HmLgfYAcl/KY0KU1qSM2oxyR8roUAu7UxbUxfoo85lgGOOOtnYRZmYRYeHMhYqeCcEsWPuwgw
FsTroHsWdQbuIa/vVu/hGZSyOwt4hqj2WXqufh3RhgbauIme39xEL7x475kfUNHoFdRBQkJOLuL0
OC2lp2gtxSlBSeqmXsrQwOQkeAStPEdrpXbqohTZ1I+M6srtIWfxOxX1rlRRLNxIp2WMEuVwFdqO
5nAN+C853AH8eg530m42R/xpzcSw3exQDme0WDVzuEJ5ajiHq7RMrc7hGvC+HO4APpLDnXRTvcTr
Gmv4Wjve09mV7OG1qUxHsoUn0zzOM3a8NdEdtzt5qo03diR4XU8mYffEM8lUT7yLNw72JtriLQle
k7J7U7b8zAcwuoN3xwf59gS3E+3JNIYkWjlEtyTsTBztjj47mW5Ntgj+dDlvSNkS4y2p3kE72d6R
4euTLXYqnWrLzBRdznl1VxeXHGmITifs/kRreW3dmrrq+tD0Aqb0X7I6leq8H8p/aws4ZB01Ug3a
tXDEOPVQJ5wyiZZTLZwzQx3otaCXpDTqON6M5GyFc3ejtTGCg7MNdSO4E1JmD7gSoPWAI4OxKYl1
SZ5BbIgE+OOQK7hr5CbolfUtbk4Dubk7gIuZBtFulyNs1O1So6lZEtCG57RukV8y4J/q76A+9AVv
q5Q2LT9NYvUNctZb38T4FHQZlGPaMXcG39bLkTYoabnSzB21FjI5VWOlXVLPaRnpnNZpqV2/1Lgc
Fq6jNXirqZ5C//gDM+2/Ua64DxRh8X8/bgmtRi8F2oMa83/2JxE5laN0jaJQS0d0zJcnASnH1RXy
zBSRVSHqL93RudUT/YMeMmSo/WTfI32i/XJvyWB2YOIl40nnSXTN6cj91wBGdk2MCg0KZW5kc3Ry
ZWFtDWVuZG9iag00MSAwIG9iajw8L1R5cGUvRm9udERlc2NyaXB0b3IvRm9udEZpbGUyIDQwIDAg
Ui9Gb250QkJveFstMTY0IC0yNTAgMTAxNCA5MTRdL0ZvbnROYW1lL0dJRUlBSytGcmFua2xpbkdv
dGhpYy1Cb29rL0ZsYWdzIDMyL1N0ZW1WIDc4L1N0ZW1IIDc4L0NhcEhlaWdodCA2ODYvWEhlaWdo
dCA1MDgvQXNjZW50IDkxNi9EZXNjZW50IC0yMTcvSXRhbGljQW5nbGUgMC9Gb250RmFtaWx5KEZy
YW5rbGluIEdvdGhpYyBCb29rKS9Gb250U3RyZXRjaC9Ob3JtYWwvRm9udFdlaWdodCA0MDA+Pg1l
bmRvYmoNNDIgMCBvYmo8PC9MZW5ndGggNjczMy9GaWx0ZXIvRENURGVjb2RlL1dpZHRoIDIyNS9I
ZWlnaHQgNzUvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVj
dC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCv/Y/+AAEEpGSUYAAQEBAEgASAAA/9sAQwADAgIDAgID
AwMDBAMDBAUIBQUEBAUKBwcGCAwKDAwLCgsLDQ4SEA0OEQ4LCxAWEBETFBUVFQwPFxgWFBgSFBUU
/9sAQwEDBAQFBAUJBQUJFA0LDRQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQUFBQU
FBQUFBQUFBQUFBQU/8AAEQgASwDhAwEiAAIRAQMRAf/EAB8AAAEFAQEBAQEBAAAAAAAAAAABAgME
BQYHCAkKC//EALUQAAIBAwMCBAMFBQQEAAABfQECAwAEEQUSITFBBhNRYQcicRQygZGhCCNCscEV
UtHwJDNicoIJChYXGBkaJSYnKCkqNDU2Nzg5OkNERUZHSElKU1RVVldYWVpjZGVmZ2hpanN0dXZ3
eHl6g4SFhoeIiYqSk5SVlpeYmZqio6Slpqeoqaqys7S1tre4ubrCw8TFxsfIycrS09TV1tfY2drh
4uPk5ebn6Onq8fLz9PX29/j5+v/EAB8BAAMBAQEBAQEBAQEAAAAAAAABAgMEBQYHCAkKC//EALUR
AAIBAgQEAwQHBQQEAAECdwABAgMRBAUhMQYSQVEHYXETIjKBCBRCkaGxwQkjM1LwFWJy0QoWJDTh
JfEXGBkaJicoKSo1Njc4OTpDREVGR0hJSlNUVVZXWFlaY2RlZmdoaWpzdHV2d3h5eoKDhIWGh4iJ
ipKTlJWWl5iZmqKjpKWmp6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uLj5OXm5+jp6vLz
9PX29/j5+v/aAAwDAQACEQMRAD8A/VOiiigAoor5H/by/a2j+CHhNvCfhm8B8e6xFhGhOW06BuDM
cdHPIQdc5b+HB7MHhKuOrxw9FXb/AA835IxrVY0IOpPZH0D4X+Mvgnxr4v1vwrofiWw1PxBopxf2
EEmZIcHB9jgkKcZweDg129fh94T8L/GL9m/WNE+KaeE9a0mC2kE/228t38qaN/vJPj5lVwSPnwck
EcgV+vvwM+NWgfHz4d6f4r8PyYimHl3Nm7Ay2k4A3xP7gng9wQRwRXt5xkyy5Rq0J89N6N6aS6p2
/D7jiweMeIvGpHll28j0SiiivmD0woorg/Hvxx8A/C/UbbT/ABZ4t0vw/eXMXnwwX9wI2kTONwB7
ZBFaQpzqy5acW35akuSirydjvKK8eP7X3wWAyfiZ4cwP+n5a9Ri1qwn0VNXju4n014BdLdBv3ZiK
7t+fTHOfSrqYetRt7SDV+6aFGcZfC7mhRXj3/DXvwWIz/wALM8Of+By0f8Ne/Bf/AKKX4d/8Dkrb
6ji/+fUv/AX/AJEe2p/zL7z2GivHv+Gvfgv/ANFL8O/+ByUf8Ne/Bf8A6KX4d/8AA5KPqOL/AOfU
vuf+Qe2p/wAy+89horivh/8AGPwR8VJb2Lwj4n03xFJZKjXK6fOJDEGzt3Y6Z2t+Rpnj/wCNPgX4
WXdpa+LvFWmeHri8RpLeO/nEZlVSASueuCRWPsK3tPZcj5u1nf7ty+eNua+h3FFePf8ADXvwX/6K
X4d/8Dko/wCGvfgv/wBFL8O/+ByVt9Rxf/PqX3P/ACI9tT/mX3nsNFePf8Ne/Bf/AKKX4d/8DkoP
7XvwWH/NTPDn/gctH1HF/wDPqX/gL/yD21P+Zfeew0VUlv7aGwa9kmRbRYzM0zH5QgGd2fTFeUj9
r34LEZHxM8Oev/H8v+NY0qFatf2cHK3ZNlynGPxOx7DRXj3/AA178F/+il+Hf/A5KP8Ahr34L/8A
RS/Dv/gclbfUcX/z6l9z/wAiPbU/5l957DRXj3/DXvwX/wCil+Hf/A5K6v4f/GTwR8VJr2Lwh4o0
3xFJZKjXK2E4kMQbO3djpna35GonhMRTi5TptJdWmNVYSdlJfedtRRRXKahRRXzf+1L+2Jo3wHij
8OaFbjxR8R9Q2xWOh22X8p34RpgvIySNqD5n4xgHcOrDYati6qo0Y3b/AKu+yM6lSNKPNN2RuftO
/tLWfwK0W00zSbQ+IviHrZ8jQ/D1uDJLNIx2iR1XkRg/ixGB3K/m94v8dQ/BTxJf61fX9t47+PN9
MZ9Q1mfbc6f4ckI/1cI5Sa5QcbuY4sBVBwaf8WPiRqnwq1TWkuNa/t74364hXxJ4lSQMNCiYYOm2
bDhZQvyySJgIPkToxr5usbN9Qvbe0hdElnkWFWlYKiljgFieAOckngCv13Jcmp4ajeTunu/5v8od
lvLd6aHyOPx8pT5I7/l/wfyPUrTxf8T/AIWz6F8SW1m9ZvFyXUgmv5WuY9Tjjl8uaO5jfKyITxtO
eCCMcY92+BHxWXwZrN38R/hFZNDGsQk8a/C0SlswKfmvdOJ5eNck7eWiyQdyHj2H9tP4YeC7b9jj
wbZ6JrmkSz+FooZNJkS8jzqMSqIrryfm/eElhIdueV96/OLw14l1Xwbr9jrmh38+mavYyia2vLdt
rxuP5jqCDkEEg5ya6cN7LOsLOpGKTu42tZNJ6Jr0tZrWL26oyqznl9aMW7ppPzT62/y6n71fDP4l
+Hvi74M07xT4X1BNQ0m9Tcjr96Nv4o3X+F1PBU8iutr8o/hD+0FqPgr7d8VPh/ZxLHEyP8QPh9C2
y3YEgf2pZLz5aMT8wGfLYjOUYEfo78HPjV4T+O3hGDxD4T1Fb23OFnt3+We1kxzHKn8LfoeoJHNf
luZ5TVwEnNJuF7eafZ/o9mtV2PqsNio10lfX8/T+tDv6/Lf/AIKx/wDJYPBf/YCf/wBHvX6kV+W/
/BWP/ksHgv8A7AT/APo969HhX/kaQ9Jfkcmbf7pL5fmfDcn+qf6Gv3h8P/8AJuWnf9irH/6Sivwf
l/1b/Q1+8Hh//k3LTv8AsVY//SUV9Xxj8OG/xP8AQ8fI/wDl58j8Ho/9Wn0FSJG0hIRWc+iqSajj
/wBWn0Ffa3/BKaJJvjp4pWRFdf8AhHWOGGR/x8w19rmGL+o4WeJ5b8qvbY8LD0frFdUr2ufF/wBk
m/54S/8Afs0fZJv+eEv/AH7Nf0PfYLb/AJ94v++B/hR9gtv+feL/AL4Ffn/+u3/UP/5N/wDan0f9
hL/n5+H/AAT85P8AgkjE8eufEzfG0ZNvYfeUjPzT1m/8Fbf+R7+Hn/YNuv8A0bHX6YRW8UOfLjSP
PXaoGa/M/wD4K2/8j38PP+wbdf8Ao2OuDKsd/aXEEcVy8vMnpe+0bb6HTi6H1bLnSve3+Z8E1N9m
mIBEEhB5BCEg/pULfcP0r95P2f7O3f4E/DstBEWPh7T8koP+feOvvM7zj+yIQn7Pm5m1vb9GfOZf
gVjXJOVrH4QfZJv+eEv/AH7NL9lmBBMEnUf8sz/hX9Dv2C2/594v++B/hR9gtv8An3i/74FfJf67
f9Q//k3/ANqe0siSd/afh/wTm9Z/5JZe/wDYHf8A9EGv5/4f9Wv0Ff0H+Of+RL1//rwn/wDRbV/P
hB/q1+la8FO8cQ/OP6kZ7/y7+f6EiRvIxCIzkc4VSTTvsk3/ADwl/wC/Zr7M/wCCVUaS/HrxGror
r/wjsh+YA/8ALxBX6pfYLb/n3i/74H+Fepm3Ev8AZeKeG9lzWSd+a2/yZyYPKliqKqudvl/wT+eH
7JN/zwl/79mv0D/4JIxPFrvxLDxsmbew+8pGfmnr9G/sFt/z7xf98D/CnxW8UGTHGiE9SqgZr5PM
uKf7Rwk8L7Hl5ra819mntbyPYwuUrDVlV5728v8AgktFFFfBn0B8T/t+/tf+KfgddWXgzwnYPp+o
6rZG5bxFcJuWJCxUpbg8GQYyWPChl4yQR8UfDfULrwL8J/FfxmM0mr+NrrWB4d02+uZDLJps0sDS
zXzE5JlKZSNj0YsecAV+vvxR+E3hb4yeFrjw94t0mHVdPm5XeMSQvjh43HKMPUfyJFfm58Sf2eNX
/Y68Q6our2t341+BPicLZau8A/0i1XdmKVh0S4hY7o5eFblflLYH6RkWNwUsL9UhDlqXTf8A08Se
qT7tfZ2e3VnzuNoVlW9q5Xj0/uvv/wAE8Y/ZG+Bem/tGfGWHw3rutPpunpbS6hc7JALm72suY4y2
fmO4sW5O1Scenp37aWp/CP4cahd/Cfwj8K4dP1XRwjP4lmnkinEjIrZXq064I5kJXOcDgGvBPiN4
A1f4J+MLGfTtWe60+5QahoHifTHaNL23J+SWNxgo4+66feRsj0J7EftieN9VsYLLxlp3hr4j2tum
yM+K9IjuJkXOcCZNknXvuJ96+zq0K2IxMMZSnz00tI8zjZ9/PtZ2PDp1KdGlKhUXLO+9r3PRf2pd
LWy/ZG/ZnmCBXWwucErn76RP/Sud0fw94B/aV0LxXH4V8Bf8K68T+H9JfWX1G3v5bnTLmOJR5sUq
NgW7PklCMrxgjjNey/tFXQ+Hv7PHwo8XT+E/C2u2+rwwm10XUrW9mtNJ8y2EuIUe7ZccbcbQMAcV
8l+Nfj/4z8b6CdAnvbTRvDbNubQ/D9jDp9k57b44gvmdAfnLetcWXxq4jDp0dLSn712t5Ntcq0l2
107HVip06VR+01ulpby79Pkc18PvH2qfDTxZp/iPSGQXVox3wXC7obmJhiSGVf4o3UlWXuD7A163
4t8S6r+y78arTxD8MtTn0Oy1nS7PXLfTJmMght7mMS/Y7hD98ISwGedu0ggnNc78I/A2j6bpE3xH
8d2rzeENOm8nT9J+7J4hvxytqn/TJThpX5AX5RlmAH19+z7+w7rXxk8U3HxU+OayLLqcwvIfDeDG
0gwNgnHWOJVCqsI52qNxGNp6cxxuEw0pVK/wJOLW/M91FLry63fS9u9sMLh69Smow0bd15Lv8+3U
+q/2Uvj7N+0f8JrfxXc6K+iXiXMllPCGLQySIFzJEx6od3fkEEZOMn4e/wCCsf8AyWDwX/2An/8A
R71+nWl6VZ6Jp8Fhp9rBY2VugSG3toxHHGo6BVAAA9hX5i/8FY/+SweC/wDsBP8A+j3r894cnTqZ
zz0Y8sXzWW9lY9/M1KOCak7vTU+HJf8AVv8AQ1+8Hh//AJNy07/sVY//AElFfg/L/q3+hr94PD//
ACblp3/Yqx/+kor6XjH4cN/if6Hl5H/y89Efg9H/AKtPoK7f4VfGXxf8EtdutY8Gat/Y+o3NsbSa
b7PHNuiLK23EisOqjnrxXER/6tPoK9//AGNv2dNI/aW+IeseHdZ1S+0i3stMa/SawCF2YSxptO9S
MYcn6ivuMdUoUcPOeJV4Ja6X/DqeBQhUnWUaLtLoWv8Ah4F8ef8Aoej/AOCy0/8AjVH/AA8C+PP/
AEPR/wDBZaf/ABqvrj/h014F/wCh28Sf982//wAbo/4dNeBf+h28Sf8AfNv/APG6+K/tbhz/AJ9x
/wDAP+Ae/wDVMz/n/E9r/Yf+JfiT4ufs/aV4j8V6j/ausz3d1HJcmFIsqkzKo2ooXgAdq+Sv+Ctv
/I9/Dz/sG3X/AKNjr7t+APwU079n/wCG1n4O0vULvU7O2mmmW5vNvmEyOXIO0AcZr4S/4K2/8j38
PP8AsG3X/o2Ovm8knSqZ/wA9BWg3O2ltLO2h6ePUo5e1Peyv+B8FY49q950D9uT42eGNC07R9M8Z
/ZtO0+3jtLaH+zrZvLiRQqLkxknAAGTk14KxwCa/Rz4a/wDBMTwX44+HXhfxHceMPEFvcavpltfS
QxLBsRpYlcquUJwNxHNfpGb4rL8LCDx8U03pePMfLYGjiarl9XlbvrY+a/8Ah4F8ef8Aoej/AOCy
0/8AjVep/suftm/GH4iftBeCvDev+Lvt+jaheNHdW39n28fmKIZGxuWMMOVHINey/wDDprwL/wBD
t4k/75t//jddd8JP+CcPhH4Q/EjQfGOn+K9cvrzSJzPHbXKwiOQlGTDbUB/iNfI4rNOH50KkaVNc
zTt7nW2mtj3KOFzGNSLnPS+up9QeOf8AkTPEH/XhP/6Lav58IP8AVr9K/oP8c/8AImeIP+vCf/0W
1fz4Qf6tfpRwT/Dr+sf1Iz3/AJd/P9Dt/hV8Y/F/wT1251nwZq39j6lcWxtJZvs8c26IsrFcSKw6
qDn2r1L/AIeBfHn/AKHo/wDgstP/AI1VL9jj9nfSP2lPiLqvhzWdUvtJtrPS2v0lsAhdmEsabTvB
GMOencCvsX/h014F/wCh28Sf982//wAbr3syx+T4fEOGNgnOy+zf01scGEw+OqUlKhK0fU+R/wDh
4F8ef+h6P/gstP8A41X6RfsPfE3xL8XP2ftL8SeLNR/tXWZry7jkuTCkWVSZlUbUULwAO1eK/wDD
prwL/wBDt4k/75t//jdfUXwB+Cenfs/fDa08HaXqF3qlnbTzTrc3u3zCZHLkfKAMDNfFZ5jsoxOF
UMDBKd1tG2ln1se9gKGMpVG8RK6t3uek0UUV8Ge8FUdW0mz17TbnT9QtYb6xuo2hmtrhA8ciEYKs
p4II7Veoo1TugPzk/aM/ZwtfgNpN/bXFje6/8BtUuTPJDb5lv/B945wLq2J+9CSQGU8EcNzhm+JP
ij8KtV+GV9bedNBq2hanEbjSPEFiS1pqUP8Afjb+Fh0aNsMjcEdCf3q1LTbXWNPubC+toryzuY2h
mt50DJIjDDKwPBBBIIr8xP2j/hZe/sh6vdWH9jf8Jn8BfFF0ZG0K7dh/Zt1zxDNy0EwGSko++oKs
G25P6dw/ndSrL2E9Z/8ApXp2n+Euuup83mOChy8+yXXt/wAD8vQwv2pP2ivh98Tv2X/hr4L8Oanc
XfiDQGsRdQS2csSosdm8T4dlCn5iBxnNeGfDL4U2d7pC+NPG7XWn+CIpvIt4LZf9N165H/LrZr/F
zgPL91Ae7cVuJp/wK8Hj/hJItf13x5nMln4Nu9ONgY3z8q3t0HKug7iEZfH8IJr7C/Z88APo9nZf
H743gLfeWlv4T8N29pth0u3IJi8i2HCHaCyrj5FBdjnLL7tWvTyrCunQUkm3vpJt/ZirL5ytZLa7
24IUni6ynVs2l02SXV/5dT0P9nD9ly6u9X0v4kfEzSrW01i0gWLw14PgH+heGrUcooU/en7sx5DE
n733frauK+GvxW0L4pWV3Po7zJNZuI7m0uk2SxEjKk4JBU4OGUkcEZypA7WvyPG4iviKzddWa0t2
XZf1rufW0oQhH3Ar8t/+Csf/ACWDwX/2An/9HvX6kV+cf/BS/wCEfjf4ifFPwneeF/COs+IbSDR2
imn02yeZI385jtJUHBxg89q9zhipCnmUJTaSs99Oh5+aRlPCyUVd6H54S/6t/oa/eDw//wAm5ad/
2Ksf/pKK/GyT9mH4vGNh/wAKw8Vng/8AMKl/+Jr9mtE0y8h+Alhp0lrKl+nhuO3a1KESCQWwXZt6
7s8Y9a+o4tr0qscP7Oadm9mn2PKyalOn7TnVtj8F4/8AVp9BX0t+wh8d/Cn7PvxQ13XfF891Bp93
pDWURtLdpmMhmjfkD2U815vF+zD8XhGv/FsfFfTvpU3/AMTTv+GYfi9/0THxX/4Kpf8A4mvtsXPB
4yhLD1aq5ZaO0lc8KjHEUKqqxg7ryP0t/wCHmvwS/wCghrP/AIKpKP8Ah5r8Ev8AoIaz/wCCqSvz
S/4Zh+L3/RMfFf8A4Kpf/iaP+GYfi9/0THxX/wCCqX/4mvk/9XMl/wCf3/k8f8j2f7Sx3/Pv8Gfr
78C/2ovA37RNzrEHg64vZ5NKSJ7n7XaNBgSbguM9fuGvin/grb/yPfw8/wCwbdf+jY67j/gmH8Lf
GPw51j4hN4q8Lat4dS7gshbtqdo8AmKtNu27gM4yM/UVR/4Kb/Cnxp8RvGngafwt4U1fxFDbWFyk
8mm2bzrGxkQgMVBwSAeDXhYCjhsv4gVOjP8AdpbtrrHvtud+IlVxGXuUo+8+lvM/N9gcECv1Q+FH
/BRD4PeDvhf4Q0HUL7Vlv9L0i0srgJpsjKJI4VRwD3GQa/P7/hmH4vf9Ex8V/wDgql/+Jo/4Zh+L
3/RMfFf/AIKpf/ia+7zLDZdmsYwr1VaOukkv8z57CVMVg23Thv3TP0t/4ea/BL/oIaz/AOCqSk/4
eafBE/8AMQ1n0/5BUlfmn/wzD8Xv+iY+K/8AwVS//E0H9mL4vKQf+FY+K8A/9AqX/wCJrwP9XMl/
5/f+Tx/yPSWZY69vZ/gz9ufF1yl54C1meP8A1cumzOuRjgxMRX8+0H+rX6V/QLq1nPL8OLy2SF3u
W0t41hA+cv5WNuPXPFfiRF+zD8X/AC0/4tj4rHA66VMP/Za4eD61KjHEKcktY7tLubZ1TnUVPkV9
/wBD0X9hL46eFf2f/inrOv8Ai6a6g0+50d7KJrS3MzGQzRvyB2wh59a+6v8Ah5r8Ev8AoIaz/wCC
qSvzS/4Zh+L3/RMfFf8A4Kpf/iaP+GYfi9/0THxX/wCCqX/4mvfx+VZVmNd4itV952Wko9Dz8Pi8
Zhqapwp6ejP0t/4ea/BL/oIaz/4KpK9Q+Bf7Ufgb9om51i38HXF7PJpSRPc/a7RoMCTcFxnr9w1+
QX/DMPxe/wCiY+K//BVL/wDE19vf8Ew/hZ4y+HWs/EFvFXhbVvDqXUFkLdtTs3gExVpt23cBnGV/
MV8xm2SZXhMHOth6l5q1lzJ9V0R62Ex2LrVlCrCyfkz7+ooor85PowooooAK5b4kfDzRPir4J1bw
t4htBeaVqUJilToynqrqf4WU4YHsQK6miqjKUJKcHZoTSkrM/Nv9nv8A4Jt65oHxsuL/AOIMVpde
DdDnM1gElST+1mDfui8YyUQABmVsZOF5BJr7n+Lvwxj+KXhiPTFvjpl1bTGe3uBH5iAtE8Lo6ZGU
eOWRCAQRuyCCBXe0V62MzbF46tGvVlrFWVtvu8+pyUcJSoQcILRnmPwY+Dq/Cq31F5b5L27vfLiE
dvCYoLaCNpGjijDMzNhppWLuzMxfk8CvTqKK8yrVnWm6lR3bOqMVFWQUUUVkUFFFFABRRRQAUUUU
AFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFAH/2QoNCmVuZHN0cmVhbQ1lbmRvYmoNNDMgMCBv
Ymo8PC9MZW5ndGggODkyMy9GaWx0ZXIvRENURGVjb2RlL1dpZHRoIDU4NC9IZWlnaHQgMjI2L0Jp
dHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9J
bWFnZT4+c3RyZWFtDQr/2P/uAA5BZG9iZQBkgAAAAAH/2wCEAAwICAgJCAwJCQwRCwoLERUPDAwP
FRgTExUTExgXEhQUFBQSFxcbHB4cGxckJCcnJCQ1MzMzNTs7Ozs7Ozs7OzsBDQsLDQ4NEA4OEBQO
Dw4UFBARERAUHRQUFRQUHSUaFxcXFxolICMeHh4jICgoJSUoKDIyMDIyOzs7Ozs7Ozs7O//AABEI
AOICSAMBIgACEQEDEQH/xAE/AAABBQEBAQEBAQAAAAAAAAADAAECBAUGBwgJCgsBAAEFAQEBAQEB
AAAAAAAAAAEAAgMEBQYHCAkKCxAAAQQBAwIEAgUHBggFAwwzAQACEQMEIRIxBUFRYRMicYEyBhSR
obFCIyQVUsFiMzRygtFDByWSU/Dh8WNzNRaisoMmRJNUZEXCo3Q2F9JV4mXys4TD03Xj80YnlKSF
tJXE1OT0pbXF1eX1VmZ2hpamtsbW5vY3R1dnd4eXp7fH1+f3EQACAgECBAQDBAUGBwcGBTUBAAIR
AyExEgRBUWFxIhMFMoGRFKGxQiPBUtHwMyRi4XKCkkNTFWNzNPElBhaisoMHJjXC0kSTVKMXZEVV
NnRl4vKzhMPTdePzRpSkhbSVxNTk9KW1xdXl9VZmdoaWprbG1ub2JzdHV2d3h5ent8f/2gAMAwEA
AhEDEQA/APVUkkklKSSSSUpJJJJSkkkklKSSSSUpJJJJSkkkklKSSSSUpJJJJSkkkklKSSSSUpJJ
JJSkkkklKSSSSUpJJJJSkkkklKSSTFzRyQElLpJg4Hggp0lKSSSSUpJJJJSkkkklKSSSSUpJJJJS
kkkklKSSSSUpJJJJSkkkklKSTEgKJtaOUlM0kL12JeuxJSVJC9dicWtKSkiSYEFOkpSSSSSlJJJJ
KUkkkkpSSSSSlJJJJKUkkkkpSo25767HM2DQq8svqDNt8/vCUipJ+0n/ALgS/aT/ANwKkkham7+0
n/uBL9pP/cCpJJWpu/tJ/wC4ESnqAcT6g2xxCzlndbybMXGZcwxDwD80rU9YyxrxIUlkdCy3X0gn
Va6KljwqLupODiAwEAq5c7ZU53gFioFTd/aT/wBwJftJ/wC4FSSStTd/aT/3Am/aT/3AqaSVqdOn
OY9vuEO8FZa4OEhcf1bLtxMnHcwwx+jviuk6XketQHHuEVN1RsfsY53gJUkDNdtxn+eiSmt+03/u
BL9pP/cCpJIWlu/tJ/7gS/aT/wBwKkklaG7+0n/uBN+0n/uBU0znBjXOdoGgkn4JWp1Kc1jx7tHe
CsggiQuA6V1e/KzHEE7S4gDyld1ilxqBKKkySZzmtaXOMNGpJ4XMdY+tRBdj9P7aOv8A/Ip0YmRo
KdvqHVsLp7ZyH+7swalc/l/XHJeSMSoVt/efqVz9lj7Xmyxxe88ucZKipo4ojfVFt27rXVL59TId
B7DT8iqm/IJk2vJ83FQSUlAdEJBkZDTLbXg+TitDD+sfVMUgGz1qx+Y/w+Ky0kDEHcKe96b1mjPq
D2+13DmnkFaIM6rzfEzX4doe0wHGCF3PSc4ZNLTKrTjwypcHQSSVDqnWMXptc2ndafoVDkoAEmgp
vOcGgucYA5Kxc761YGM411B19g7N0H3lc11Href1Bx9R5ZV2qZoPmqCmjh/eRbuZH1u6lZIqaypv
buVQs631a36eS75afkVJJSCER0CE5z84gg32QefcUhnZoAAvsgfyigJI0Oym7X1rqtR9mS/56/lV
7H+tvU6oFoZc3uSIP4LESQMInoFPZ4X1swchwZc11Dz46j71tMsZY0OYdzTwQvMlcwOrZuC4Gp5d
X3rdqCo5Yf3U2+hpLJ6X1/HzmxOywfSYf4LVBBEjhQkEGildMTASWT1vrDMCjSHXP0rZ/E+QSAJN
BSDr3XfsbfQo1yHiQezR4rlDmZbiSb7CTz73f3qFttl1jrbXFz3mXOKgrMICIQl+1ZX+ms/z3f3p
fasr/TWf57v70JM5zWtLnGGjUk8BOoITfasr/TWf57v71qdEtebRbZbZYfzWlzto84nVc1W+/qFw
ZQC2gHnu7/Yuy6J0t9bWlwUGSYOkftSA9FjuLmgo6HVXsaAiKJKkkkklKSSSSUpJJJJSkkkklKSS
SSUpJJJJSlR6kz2tf4GFeQMxm/HcO41SU5KSSSalSSSSSlLO6/X6nS7B+6Q77loqv1Gv1MDIZ+9W
YSUw+qt26lq6hcX9UrIaG9xouzBkSnIQZz9uO7z0WUtDqbvaxviZWegVKSSSQSpJJJJTk/WSucOu
0DWqwEnyWv8AVy8Px2/BUusVet0y9nfbI+Sj9VL5qDUQh6tVOouikD94q2qHU3fQb80SpopJJJqV
JJJJKUqXWsj7P0vIs4Jbtb8SrqwfrfeRh04wOtz5I/qpBTW+quNusaSNeSvQam7awFyf1UxiGhxX
WnRpjsE5DzP1p605pPT8Z0afp3D/AKlcwi5Vzr8q6530nvJP3oStwjwilqkkkkVKSSSSUpJJCyMl
lDJOrj9FvdIkAWVIcy4+pXUz6UyV2/1X3+i3cuI6Zh3ZeT6jhJcV6J0+qvp+EbrjtZW2XSqs5cUr
XJes9Xq6Zj7j7rn6Vs8T4nyXDZOVfl3OvyHF9jvuHkEXqWfZ1DLfkP0B0Y3wb2VVTwhwjxQVJJJJ
6FJJJJKUkkkkpSSSSSlJJJJKZ1W2U2Cytxa5vBC67of1iryoxsmGXD6J7FccnDnscH1mHt1aU2cB
IeKX0PqGdVh477rTDWj5k+AXB52bdnZDr7TqdGt7Nb4BNf1y/qbG0WjZ9n0Le5PEoCbjhQs7qKkk
klIhXGp4VE+r1K70KZGOD7nfvn+5LMtffZ9jp4Olzv8Avq1+l/Y8AAWSXDkNEqLJIk8Mde6Q7HQ+
gsqa0lq6iihtbQAFz9P1nwKwBts/zf8AartH1l6daY9UNPg8Fv5VFwSHQpdlJV6syqwAtcCDwQjh
wPCapdJJJJSkkkklKSSSSUpJJJJSkkkklKSSSSUpM4bmkeIhOkkpw3N2uLfAwmRsxm3Id4HVBTUq
SSSSUpM9oexzTw4EfgnSCSnn/qw815DqzyHEfiu7YZYPguB6eTT1vIrOm2xd5QZqaU5DQ6i6bg3w
CqouU7dkPPgYQk1KkkkklKSSSSUxtbvqez95pH3hYv1Ys9K91M6scW/cVujlc7h/q3W76z7Zduj4
6ohD3jTLQVndRdN4HgFfx3bqmnyWZmGcl5+SRUhSSSQSpJJJJSlyf1kt9frNVA1FTR95XWBcWxxz
Ot328h1mny0RCHtvq7RsoafJbREiPFU+l17MdvwV1FT591jAswc6xjh7HEurd2IKorv+r4DMygtc
0O8PIris3p+RivPsLm9lPDKKqWiKaqSE6/YYcx0/BQOYB9GtxT/ch3VTYTEholxgeaqOyMuzSuvZ
8dU9fS83JcPUl3xTTmA21VSruoMb7aRvd49k2F0zJy7t7gSStzp31XeSC9v4LqsDo9WO0S0SoZTM
t000eh9DFDQ5wQfrdnbW19PrP8u2PwBXTHbVWSdGtEn5LzvqGScrNuvJne47T5DhOxRuV9kFrpJJ
KwhSSSSSlJJKpnZBYBVWf0juT4BCRAFlTYffSww94B8JSZdU/wCg8FC6d0W7JIMTPcrdr+qj9o9o
Ci949k05SStZ3Tb8KN49p0BVVSxkJCwhSSSSKlJJJJKal/6HLrv/ADLPY/58FW0LLq9bGsr7kafE
KOBcbsSqx30i2HDnUaIda76qToGZkehV7dbH+2sefj8kdU6a3Zma6wCa6/awfDk/MoZJcI03OyQl
wMb7PVvdq93c8z4o6lYx9etjdo7SoggiRqEMcQBvZ6qKkkkk9DYw87Iw7A6px292EmCut6V1evJY
CDB7g8grilZwMl2PkNcDDToVHlgCLG4SH0Rjg4SFJUenZAtrBlXlXSpJJJJSkkkklKSSSSUpJJJJ
SkkkklKSSSSU5/Ume5j/AB0VJamezdQT3aZWWgVKSSSQSpJJJJTzmT+h+sDu2+HLt8N4+zB06ALi
+uDZ1aizjcwD7l1WHb/k8n+SnIaziS4k9ymSSTUqSSTEgRJidB8UlLpJJJKUsDqY9HrldnHqtB+M
aLfWJ9ZGbX4uR4O2ffqiFPXdPeHY4Pks60za8+ZRejW7sOf5P8ECZM+KRQpJJJBKkkkklNfqF3oY
N9swWsJHxXNfVij1Lg8iS47p+K1PrXkel0v0x9K5wA+A5TfVLGGhhEIeyx27amiEVMBAAToqROyK
AS1z2gjkSq19WDcPc5v3qnf/ADz/AIqCFqYXdH6e8kgs+9V/2HgfvN+9W0oCVpYVdG6ewzLPvV+n
EwK4hzJVNM47Wuf+6CfuStDtsrraPaAprnekdbdluAkLoQZAKKnP69knH6Ve8GHFu1vzXAjhdd9c
rduFVUDq98keQC5FWMI9N9ygqSSSUiFJJJJKUqWPUcrPJ5AMBXHGGk+AUvq5TvyRI/OUWY6AJD23
ROn11UtJbrC19rfBCxWBtLQEZQJczr+Gy/plx2+5g3t+IXBhel3sD6XsPDmkfgvNXCHuHg4j8VPh
OhCCskkkpUKSSSSUpU+n+x+TR/o7CWjydqriqfzfVOf5+rjzYUJdD4qbFzi2l7hyGmPuWl9W8AGp
phZ7mhzS08EQVufVu5lbQxx1booswOh6JDfzOjC1kbVzeX0m3Cs3sBDCfc3svQm2VOb2XPfWXIx2
VGppBtfoG9wO5UcL4hSXmEkklaWqTPO1pPhqnQsh0MDBy9waP4oSNRPkp7T6v2l1Lfgt9c99Xqy2
lvwXQjhVFy6SSSSlJJJJKUkkkkpSSSSSlJJJJKUkkkkphc0Oqc09wVixGngt1Y2QzZe9vnP3oFSN
JJJBKkkkklOH9ZmQ7EuHLXEE/FbODbu6e1vjCzPrMyenCwcssb9xVrpD92ExHopuJJJIKUsrrOW6
jN6fWOH27nDyGi1Vy31isNnWqKgf5gAgfFEKepKSZjtzGu8QCnQUpZv1hr39Nc//AELg7+C0kDPq
F2FdWdZYT92qSmPQb5wT8FZWP9WrnOxnMPIGoWwiVKSSSQUpJJJJTzH1stNmbjYo4YN5+ei6L6s4
4bQ0xyuSzbPtnX7XDVrHbG/ALvujU+njN+Cch0UkkklONf8Azz/ihol/88/4oaalSSSSSlKF38xb
/Ud+RTULv5i3+o78iSnnfqoT6o/17r0Cv6AXn/1V/nR/r3XoFf0AnIeV+ujz6+NX22l34rnFv/XL
+n0+TP4rAVrH8gQVJJJJyFJJJJKY2/zT/gVf+qjAbAVn3/zFn9UrV+qLdW6KHPuEh7usQwfBSTN+
iE6hSs76J+C82y27cq5vg8/lXpJ4K84zv6bf/XKmw7lBQJJJKZCkkkklKVDOJbn4b+PcWn4FX1n9
X9rsR8wBc0IS2U6Cdj3sduY4tcO40TJIqbP7T6ht2/aHgeRVdznOJc4lzjyTqUySQAGwUpJJByMy
jH0eZceGDUlIkDdSYkAEkwBqSULptbs/MFsEVt0rHl4/NApoy+pWAOHp0z9Ad/6xXadD6M2hrdNV
BkycWg2SA63S8b0qm6LRUWN2MDfBSUSVJJIOUS2h5aYMcpKTJLF9a79933petd++770LU7SSxfWu
/fd96Q6qMd4qscSX6iUrU7SSFj3i5gcEVFSkkkklKSSSSUpZvUWbbg4fnDVaSp9SZNQf+6dUipzk
kkk1KkkkklNHrdfqdLv/AJDd/wByboYI6bUT+cJVrLr9TFur/faQo4NRpw6ajyxsI9FJ0kkkFKHK
46532rr97pna/Z9y6+xwZW95MBrSZ+AXIdCb9oznWnl7yTPxRCHr6htra3wAUkS6vZt8whoJUkWh
wLTw4QfmkkkpxPq+wsvymdmPLR9621Uw8b0MrLdGljwWn5aq2iVKSSSQUpQvtFNFlx4raXH5BTWb
9Ysj7P0m4gw6yGAeM8pKef6DUcjMNp1L3F0/Er0jEYGUtAXEfVPF9zSV3jBDQE5DJJJJJTjX/wA8
/wCKGiX/AM8/4oaalSSSSSlKF38xb/Ud+RTULv5i3+o78iSnnfqr/Oj/AF7r0Cv6AXn/ANVf50f6
916BX9AJyHkfrj/T6f8Ai/4rAXQfXNsZuO795h/Arn1ax/IEFSSSSchSSSSSmF380/4FbH1T+kPg
FkW/zT/gVrfVIy4KDPuPJIe6b9EJ0zfohOokrHgrzjO/pt/9cr0d3B+C83zCHZlxHBeVNh3KChSS
SUyFJJJJKUsr6wte7GpFZh3qT+C1VUzmNeamn95NyfKVBH06vqt1Q924xoSJVp1PVW81sPyP966n
oGDQMXe5oIA1CvOowXfmEKv7kh1K6nhdvVf9Ez7j/enFHWH8Brfg3+8rt/suB+6fuCk3HwR+afuS
9yX7yqeJZ0Xqd+llr4PYe0fgtHB+qYBBc2T3JXXUU4RBMbY8UV2Ti06VN3u/BNJJ3NqaXT+h1Uge
0CFsV1MrENCoHqN35oDR4KTOpWD6bQfhohanRSVerNps8j4FHBB1CKl0HL/o7/gnyMhtDQ5wJnwV
S/PZZU5gaQSkppJJJJqVLnvrBY9nU8YNMAtMroVldV6Rfm5dWRW9rW1iCDyUQp3+iOLsYE+C01k9
KeMdjan8xz2Wo17X/RMooZJJJJKUkkkkpSFks30Pb5T9yKmIkR4pKcNJSsbtsc3wKimpUkkkkpSS
SSSlJJJJKaXWrhR0rJs77IHxKx/qnRL2uhWvrbcGdNZX+dZYPuVj6p0e0ORCHoM+uK63eGipLUzm
TjH+TqstIpUkkkgpSSSSSlJJJJKUuc+t9wP2bFHJJe4eS6Nch1uz7T18sGopAZ/FEIek+q2NtqDl
1Cyeg07MdvwWsipSSSSSnGv/AJ5/xQ0S/wDnn/FDTUqSSSSUpQu/mLf6jvyKahd/MW/1HfkSU879
Vf50f6916BX9ALz/AOqv86P9e69Ar+gE5DzX10rO3Ht7Alv8Vy67X62UGzpReP8ABODj+RcUrOI+
nyQVJJJJ6FJJJJKWeJYR4haX1TfFgB8VnK39XHCvLLCeCoc40BSH0Jn0R8FJQpM1tPkpqFLGxwbW
5x4AJXmlji+17jyXE/ivQer3CjpuRYezCB8SvPPPxU+EaEoKkkklKhSSSSSlKrkmcmpnzKtKqz9L
1DaOGwFHlPp80h7norNuAf6qmjdNr29PP9VBVYpUkkkgliWS/dOgEQpJJg9hO1rmlw7AglJS6SSS
SlfgfFGw+o7bjRb9IcHxCCs/qxNLaspv+DdDvgUQp6DqLgaWkdys9TZlDIw2EGVBIqUkkkgpSSSS
Sml1fLdiYnrN5DgFc6DnuyWAuWX9Z/8Aks/1grH1V/mwiEPVJJJIqUkkkkpSSSSSnKz2bcgn94Sq
6v8AU2aMf8iqCBSpJJJBSkkkklKSSSSU8z9bLd+Xi44/NBLh8eF0f1Zp20NPkuU6u85H1gcBq1ga
3TxC7jolWzGbp2TkN+5u+p7fELGW4RIhYtjdtjm+BIQKmKSSSCVJJJJKUkkkkpRcGgudoGiSfguL
6aDl9UtuOu+w/lXUdYv+z9MyLOPaWj4u0WH9VcfdY1xGvf4ohD3fT69lDR5K0oVN21tHkpoqUkkk
kpxr/wCef8UNEv8A55/xQ01KkkkklKULv5i3+o78imoXfzFv9R35ElPO/VX+dH+vdegV/QC8/wDq
r/Oj/XuvQK/oBOQizqBkYd1JE72EAecaLzhzXMcWO+k0kH4henLhfrJhHF6k9wbFd3ub8e6mwnUh
BcpJJJTIUkkkkpSJhP8ARzG2djyhpISjxClPovT7W2UNg9laXAYXXc/CG2twc0cByPkfWjqt7NjX
NqB0JaNVB7MvBNuj9bupsLG4FTpdO62O0cBcunJLiXOJLjqSeUynjHhFIUkkkipSSSSSliYBJ7ao
XRKjdmb4+k6VDPt2U7B9J5j5LZ+quHLmujRQZjqB2SHsaWbMAj+SqC1rW7cVw8AslQlKkkkkEuX9
ZM+zC6aTUdttx2MI7eK5npeHnPtF1T3CwGZk6rY+t4c4Yje28mPktn6s4dfotc5oRCE9TnOraXCH
R7h5qSNlsDL3AaBBQSpVeqs39OyB3DCR8QrSDmf0O7+oUlNP6u3i3FDDrAUrxnt6hWA4+hu9zfJU
fqpZLo811+TRX9nL49wHKchzkkkk1Klzf1n6h1DFy6K8S01te0lwHiukXNfWQB3U8YH90ohDRH7Z
zqxXfY6ysmSCF131cxLKaxuEI/RcOl2O0lo4WvXSyv6IhFSRJJJJSkkkklKSSSSU181m7Hd4jVZS
23t3MLfEQsVw2uLfAwgVLJJJIJUkkkkpSUxJ8NfuSQc230cO639xhKSnk8KcnrF1p1D7CQvRcBgb
Q34LgPqvSXXhx1kzK9FoEVNCchIsnNbtyXeeq1lndSbFjHeI1QKmmkkkglSSSSSlJJJJKcH633Fu
FVjg/wA8/UfDVW/qpjQ0OhY/1lt9bq9VHapuvxK6z6uUBmO0+Sch2xwnSSSUpJJJJTjX/wA8/wCK
GiX/AM8/4oaalSSSSSlKF38xb/Ud+RTULv5i3+o78iSnnfqr/Oj/AF7r0Cv6AXn/ANVf50f6916B
X9AJyGSyfrF04ZuC4tH6Wr3MWsmIkQiDRsdFPmOo0OhHISW59ZOk/Z7jlUj2PPvA7HxWGrUZCQsL
VJJJIqUkkkkpSSSSSlJJJJKUkkkkpSXx4SVLOyTP2es+530iOyEpCIsqRiczN01Y0w1ehfV3BFNL
TELmfq10ne9r3Bd/j0tqrDR4KqTZtcrJ/mH/AAWOtjJ/mH/BY6aVKSSSQS4f1pqJrxrR+a8h3whb
31cI+zN+Cr5eLXl47qLPou4PgQp9MbbgVenuD40BRQ2cwzkvQUiSSSeSkglSBnu2YOQ7wrJR1m/W
K/0ekXa62RX/AJySnP8Aqnq8HxXb5H9Ed8Fxv1Rpjb5Ls8n+iu+CchyUkkk1Klzf1j/5Uxv6pXSL
m/rH/wAqY39UohD1vQv6MPgtRZfQv6MPgtRFSkkkklKSSSSUpJJJJSlkZbNmQ8Dg6ha6zupMh7X9
iIQKmmkomyscuA+JS9Wr99v3hBLJJR9Wr99v3hL1av32/eElMll/WW41dItA/wAKQz71perV++37
wsD63XtdVjY7XA73btDP0UQpL9Usfg+ELuGiGhcx9VaNtQMLqEUKVPqTZqDu4KuIOWzfjvHcCQkp
yEkxc0ckD4pvVq/fb94TUsklH1av32/eEvVq/fb94SUySHKj6tX77fvCBm5VVOHdbvEtYYg940SU
8o1xzet33Hgvgf2dF6J0uoV47R5LgfqzQbcgWHlx3H5r0bHZtqaE5CVJJJJSkkkklONf/PP+KGp5
Glz5017oXq1fvt+8JqWSSj6tX77fvCXq1fvt+8JKZKF38xb/AFHfkT+rV++37woXW1ehb72/Qd3H
gkp5/wCqv86P9e69Ar+gF5/9Vf50L0Cv6ATkMkkkklIcrHZkVFjwCCI1XE9W6O/DsL69aiePBd4q
+Xh15DCHDlOjIxOinzhJbfU+gPqcX0DTwWLY11Z22AtPmp45InrXmilkkgQeEk9CkkkklKSSSJA1
OiSlJIFuZRXpu3O8G6qs63LyjsrBYw+HKZLJEePkmkmTnbT6VOrzoXeCs9H6Q/ItDn6yZJKs9J+r
llrg57fmu26Z0mrGYNNQoJTMjqll0vpzMapsBaKYCOE6apFk/wAw/wCCx1sZP8w/4LHQKlJJJIJU
ksXrPV7+m9Ro2jfTYz9Iz58haeLm4+WwPpdM/mnQhJSdJKEjoJOgHMpKUuU+tOd9ozK8CvVtOth/
lHstDrP1kx8RhpxHC7KdoCNWt81i9H6ddl5PrWy5zzLnHuiEPV/VfE2Vh0Locv8Ao7/ggdNxRj0g
R2R8v+jv+CKnISTFzW/SIHxTerV++37wmpZLm/rH/wAqY39UrovVq/fb94XOfWFzXdTxtpB9p41R
Cnruhf0YfBaiy+hf0ZvwWoihSSSSSlJJJJKUkkkkpSFk1C2otiUVJJTxfU+h5dlpdW94HkSqH/N7
qH+ls/zivQTWw8hN6Nfgkp8//wCb3UP9LZ/nFL/m91D/AEtn+cV6B6Nfgl6Nfgkp8/8A+b3UP9LZ
/nFPX9Wst1rXWlz443GYXf8Ao1+CXpV+CSnP6RhHGqAIghaaYADQJ0lKTESITpJKec630q6+TUS3
+qYXPn6vdQn+ds/zivQi1p5EqPo1+CSnz/8A5vdQ/wBJZ/nFL/m91D/SWf5xXoHo1+CXo1+CSnz/
AP5vdQ/0ln+cUx+rmc4bXve5p5BJIXoPo1+CXo1+CSnmuhdFOIQXCPBdO0QAPBMGNHAUklKSSSSU
pJJJJTm9WxHXVkM0J7jRcjd9X891hIseP7RXfkAiCoeizwSU8B/ze6h/pbP84pf83uof6Wz/ADiu
/wDQr8EvQr8ElPAf83uof6Wz/OKX/N3qHeyyP6xXf+hX4JehX4JKeY6F0azFcCQuqaIaAotra3hT
SUpJJJJSkkkklI7KWWCHBZOd9X6LwSANVtJJKeGyvqzdWSaiQs2zpnUqzxIHkvSXMa7kIL8Kl/ZE
SkNiVPmpq6g3msH71EjO/wBGB969Fd0mh2sKH7Fx/BH3J91UHzv0uov0aNvwCdnSOoXH3ucfwXor
ej447Qis6dQzgIGUjuSp4TE+qtriC5uq6Dp/1YqrguC6JtFbeAiIKa+PhU0ABoCOnSSUpJJJJSLJ
/mH/AAWOtjJ/mH/BY6BUpJJJBLzX1nAd1HFB7s/itPD6ObMcWUksfHLTCzfrL/yni/1f4rrOhgHG
bPgnIecyavrBRLarzA/kgrOyKuvZPtuueQf3fb+ReiPx6n8hD+w0zMJKeAwfqvc98vBJJ1JXX9K6
LXitBjULUZj1s+iEVJSwAAgJOEgg906SSnmut9LvvJNRLfgYWD/ze6h/pLP84r0Esa7kSm9GvwSU
+f8A/N7qH+ls/wA4omP9Xcr1g60ueRwXGV3no1+CXpV+CSmr0yg0Uhp8FdTAAcJ0lKSSSSUpJJJJ
SkkkklKSSSSUpJJJJSkkkklKSSSSUpJJJJSkkkklKSSSSUpJJJJSkkkklKSSSSUpJJJJSkkkklKS
SSSUpJJJJSkkkklKSSSSUpJJJJSkkkklKSSSSUpJJJJSkkkklKSSSSUpJJJJSkkkklKSSSSUiyQT
Q8DUwsV9tdX848M/rGFvLC610k5XASUh+3YX/civ/OCX27B/7kV/5wWM76qOJJLfxTf80z+5+KFK
Q/WG6q7qWKaXtsAbqWmY1XYdC/ozfguaxfqw6q0Haut6fjmioN4gIqbiSSSSlJJJJKUkkkkpSSSS
SlJJJJKUkkkkpSSSSSlJJJJKUkkkkpSSSSSlJJJJKUkkkkpSSSSSlJJJJKUkkkkpSSSSSlJJJJKU
kkkkpSSSSSlJJJJKUkkkkpSSSSSlJJJJKUkkkkpSSSSSlJJJJKUkkkkpSSSSSlJJJJKUkkkkpSSS
SSlJJJJKUkkkkpSSSSSlJiAeU6SSmOxvgEtjfAKSSSmOxvgFJJJJSkkkklKSSSSUpJJJJSkkkklK
SSSSUpJJJJSkkkklKSXyqkkp+qkl8qpJKfqpJfKqSSn6qSXyqkkp+qkl8qpJKfqpJfKqSSn6qSXy
qkkp+qkl8qpJKfqpJfKqSSn6qSXyqkkp+qkl8qpJKfqpJfKqSSn6qSXyqkkp+qkl8qpJKfqpJfKq
SSn6qSXyqkkp+qkl8qpJKfqpJfKqSSn6qSXyqkkp+qkl8qpJKfqpJfKqSSn6qSXyqkkp+qkl8qpJ
KfqpJfKqSSn6qSXyqkkp+qkl8qpJKfqpJfKqSSn6qSXyqkkp+qkl8qpJKfqpJfKqSSn6qSXyqkkp
+qkl8qpJKfqpJfKqSSn6qSXyqkkp+qkl8qpJKfqpJfKqSSn6qSXyqkkp/9kKDQplbmRzdHJlYW0N
ZW5kb2JqDTQ0IDAgb2JqPDwvTGVuZ3RoIDIxMDUvRmlsdGVyL0ZsYXRlRGVjb2RlL1dpZHRoIDE1
MS9IZWlnaHQgMTExL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE2IDAgUi9UeXBlL1hP
YmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpIieyXCXvjRAyG3YOFhd3VHJ40LjS2AzZ7ZDl2
gYT7+v//CWmOxHYmHjk9Ag/V8zRtbNd+LWk+fZNlj8GOs1MDxOLs/OLUCLE4v7g8NUIkzi4uPzg1
QyTOL558eGqGSJx/9OTpqRkicX758b8U65NTM0Tif4D17PmL58/u5lZ3gAVC2N/PXlB4LpAnxALA
D6kcwnOL9dydEXgQ7OmHxwKhdJblufv2woX7YhRkWuXySLDjsah2MldC5tod6GYLckM/xij9oFiA
RFQ7oZRPVq+3qLCSkGb5Ufk6DougDHgAE452VqLAGhqlNF0DenrGjsMSSpgrn4ZcRfKRK0qWNGqe
ZXNM6NSUHYOFKwyXmRL+W/ije4WQDncuPd5EvTgCS9v0gAiPij6R1qGr4YxazEzM13Qs4bMjlRh/
FCCYxBLieoRsYhWnYgE1s7TvLpKVwVrScgQSsUyYxNW3waLHaMcDHK0EyliG1ZQ7JbkHLHxzbbDh
JbuHhZUSavyczzUJC7CbgFYVTGlhW0dlPwz3vyZhSbov3hzfe0oLo56QSCAXW1enFdFySZWL1IXF
9XXx6e6rcBnmP2hib1kukX7pz24WZVVXyy1XLnlLZDIWypAma8AQ7M+/qJqybJqy3R4irgnBxqIl
aNU9XcEs+7IqLVaxOyQmlJCPhTJKv/bNwMtXr9+8Gh5cYrIo2lXnDoGPkzY2lqud2bMLL+uyfDO8
+q3HqlbDM5h0Ttq4WN6wi31leI1Yw3QVpc/WEEr6+X1XWGA9E0T6/RU+/vXgWOWxlv3D3jwyuNgt
j+8pRUx6Xr4py0G2itpRNX0styMBjhjzBQK9XNxlvi6br/pHWp+sZtBauEEDjbdJawwPC7Sw4zn6
li+r+uvegaVPVqTjcUdi4CqtYSwszP6YLfmm7n8PyaqWwyvBOsKIyz4KC0cazA/uE1ZvBgJBrbVo
ysUelev26J7kCCy3/uShnejq23eDI5iuBXZW0e4VMcuciUyBcbDkzMIZkbrQYwbZqovIWSDjpVPd
xcESDou9qVp62apiJ7V6/94kN46sbFmgOaMlPi0oQa7lm0VLIl+0y14pcfXk6bHI6q1czb+bq5Rd
+j77oUDPUFReH25u6qrFL03VFrtySmHvcwfZcgIRf8P1evsnOtK6LHAZLtygbvy8HioYemgcF+MJ
Y8opRvREW++mcREwkGfRQRrMbK1Q500i9wws2u9oET21qctqs0XsYAyw2o6E4cDIzaEb8rEgN+iX
4yLfdtZbW5eHoh4YHGlwXt8SC+8BtPeMNMOKlKB26bqubJIWnTw1WM2qattiKPegAMYlIo2Va1QI
yEysRze2nW3Xtzc32FI//rTFqlAZlkgUVXrc1o0+lIFlcMCig9t/u03ldJPS9a6lLVj788/BAZYx
id/G7YePtMsmYgBXQcxttq6L9h0lJqzHffuwY9ImZZ0ZK1HiFkxEZOuXxa/DxZ/tNj2HkwVKzWaJ
8cNSeUSLtELbLHbJChH8cn04WdZCyJm5LVY81l6nqh6qpWr2JKEbak6fc3U/WBvf2pvuQWdpfluM
UIH5jn7J+8Ha+IZvelius4pVTBVCKIt1T9lae6q+A23T2oC9NcdpfcjrcrEOrJj1wgn5L92DRTWc
gLEwNKxvO3xyEQVzrdX83vXxyzaiGJHQGLfVLams9g1u47W06SEUSSW1N0y7XJ6xyZUe+rZ1E1mH
YfCMpkvmyogUGqvlJfnv/o28aDVdLS1YWGibqbVGO57p5TFVg9cLWN3WKgJVouXRlEgzKvKsIuaR
gRiwuvIQlCxFRd5N3zpbMkK1CpOngxUcxSJqsbYBmTCQqQObAz4WCPvZm9a+43ujb+VXQTOqpuST
FMjEppOp8pDlSnSxIr0dsFILUetc9W52LBb6NmN6Atjur8NgAOtR2bK1w/vdhUDQtOivnPage6jH
B6JM+L8JWOTldf9um0i5CLWpUpMH1ZQBxsqWNoimOxZ1HbC6a46wxozWFsyo+JidigUoEVrlu6nv
a9h3pss90P0baZw7EofG+HaMuxKFwVuZ99t3DM60l5tl1aQ6SysKky4jD4uGouzYiDCo+yVDja3G
70NbOylFwtWwsTJBWdfK+JHhZave9K9qU1YLUno1ESuzo3E297ddV2WFZr4PUVR1bxjt34HSzuNi
YwFt7yDMx81mjcuxp6a0GRtvrRwnjk52+0Qsv70b6daiar8fuQGQz83MncmpDen2UTA6Y1fX138c
Oke+AbvTsNLF7638T/qcj4/+t3/9feiUNQ3A0niL9ZSHBZgurMMVmt7DF/39+cFTfmfI2WAg1kdP
mFjIpWb0rjIf3+MdouJ1lce6ePIh91rQtP0B8vb8B9h/lLh7AmlYi9DG2cXlB5MeQUYcLcUkLlyC
WEEwE7J8fnE54QFglYew2FzU6BK3mkZPeZmz84sJWCSnNLVxjyCY/+FMDMi0Ux6ATbgWBOZK89Xa
2tHwv/zWmh5CGZsxYR80XhVbacF9gduFJcqpjqnBC1apgESF34pHh+UxWmmg2Ruapx/WU4GxI0HS
leLesewIwe4yzvvmYRz5jNgRg/1tS22FPScT+QBYzhXa6uCnCax2/aNTBDWTADPEtcIut+7xQcIt
Rp+RzOuG3byF2tl2l+l9zl2GSxY+2T9UomcRGVwZTJg9NLtCdcOZwxvOd4aFj9NiJ0s48khst9kC
ylJ0Pdx76E430yTOjaStrpoh1czW+BRU1gkHY2fnEmJiBXECznh27z7RXLrs7oP6nv7G4p2YKoS0
qiHUQ4rBYzzGYzzGY/xn4x8BBgAT/eO6Cg0KZW5kc3RyZWFtDWVuZG9iag00NSAwIG9iajw8L0xl
bmd0aCA4Mi9GaWx0ZXIvRmxhdGVEZWNvZGUvV2lkdGggMjEvSGVpZ2h0IDIvQml0c1BlckNvbXBv
bmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJl
YW0NCkiJOvblSM0Ln7DzIrFX1GMuK0ZflAUxLipEX5SDM+KuqEdflAczNMAMeRhD7sjng4XPbDzO
sPqd5/E7x+V7jhPG4EJm+GJjAGUBAgwAaOY23QoNCmVuZHN0cmVhbQ1lbmRvYmoNNDYgMCBvYmo8
PC9MZW5ndGggNC9XaWR0aCAxL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNl
IDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQrh+9MKDQplbmRzdHJl
YW0NZW5kb2JqDTQ3IDAgb2JqPDwvTGVuZ3RoIDY0L1dpZHRoIDIxL0hlaWdodCAxL0JpdHNQZXJD
b21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+
c3RyZWFtDQrD88Bs5TVCywBIzQFNzgZJzQNMzgVJzQNMzgZJzAJMzgZJzQNMzgVIzQNNzgZIzAJN
zgZIzQNMzgZJzQJIzQEKDQplbmRzdHJlYW0NZW5kb2JqDTQ4IDAgb2JqPDwvTGVuZ3RoIDQvV2lk
dGggMS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9Y
T2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0K4/+4Cg0KZW5kc3RyZWFtDWVuZG9iag00OSAw
IG9iajw8L0xlbmd0aCA2NC9XaWR0aCAyMS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29s
b3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0Kw/O/bOU2
SM0AS84FSs4ETs8ITM4GTc8ITM0GTc4ITM4GTc4ITM4GTs4ITM4GTs4ITM4GTs4JTNIHSc0DSc0D
Cg0KZW5kc3RyZWFtDWVuZG9iag01MCAwIG9iajw8L0xlbmd0aCA3L1dpZHRoIDIvSGVpZ2h0IDEv
Qml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBl
L0ltYWdlPj5zdHJlYW0NCtr/nrz+kQoNCmVuZHN0cmVhbQ1lbmRvYmoNNTEgMCBvYmo8PC9MZW5n
dGggNjQvV2lkdGggMjEvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUg
MCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCsPzwG3lNkXMAEnNA0jNAkzR
BU7PCUzOBkrRA0/QCkrNBU7PCUvNBU/PCUrNBU/PCUrNBU/PCkrOBU7PCEnNAwoNCmVuZHN0cmVh
bQ1lbmRvYmoNNTIgMCBvYmo8PC9MZW5ndGggMTAvV2lkdGggMy9IZWlnaHQgMS9CaXRzUGVyQ29t
cG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0
cmVhbQ0K3P7Gx/90xPyRCg0KZW5kc3RyZWFtDWVuZG9iag01MyAwIG9iajw8L0xlbmd0aCA2NC9X
aWR0aCAyMS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlw
ZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0Kw/PAbeU2Q8sATs4IS84FTc8ITM4GTc4I
S84ETs8JS80FTs8JSs0FT88KTNEFS84ETs4JS80GTs4JS80GSc0DCg0KZW5kc3RyZWFtDWVuZG9i
ag01NCAwIG9iajw8L0xlbmd0aCA3L1dpZHRoIDIvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4
L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCtX9
orX+TgoNCmVuZHN0cmVhbQ1lbmRvYmoNNTUgMCBvYmo8PC9MZW5ndGggNC9XaWR0aCAxL0hlaWdo
dCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3Vi
dHlwZS9JbWFnZT4+c3RyZWFtDQra/9oKDQplbmRzdHJlYW0NZW5kb2JqDTU2IDAgb2JqPDwvTGVu
Z3RoIDY0L1dpZHRoIDIxL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1
IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQrD88Bt5TZDywBLzQVJzQRP
zwlLzQVOzwlLzQVOzwlLzQVOzwlLzQVPzwlKzgVOzwdLzQZOzglLzgVL0QRPzwkKDQplbmRzdHJl
YW0NZW5kb2JqDTU3IDAgb2JqPDwvTGVuZ3RoIDcvV2lkdGggMi9IZWlnaHQgMS9CaXRzUGVyQ29t
cG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0
cmVhbQ0KtP9Wq/9OCg0KZW5kc3RyZWFtDWVuZG9iag01OCAwIG9iajw8L0xlbmd0aCA3L1dpZHRo
IDIvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9i
amVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCrXvocD+tgoNCmVuZHN0cmVhbQ1lbmRvYmoNNTkg
MCBvYmo8PC9MZW5ndGggNjQvV2lkdGggMjEvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0Nv
bG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCsPzwG3l
NkPLAE7OCErOBE7OCUvNBU7PCUvNBU/PCUzRBUrOBE7OCUvNBk7OCEvNBk7PCEvNBk7PCErOBEvN
BQoNCmVuZHN0cmVhbQ1lbmRvYmoNNjAgMCBvYmo8PC9MZW5ndGggMTAvV2lkdGggMy9IZWlnaHQg
MS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5
cGUvSW1hZ2U+PnN0cmVhbQ0Kyv94of8gxvySCg0KZW5kc3RyZWFtDWVuZG9iag02MSAwIG9iajw8
L0xlbmd0aCA3L1dpZHRoIDIvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2Ug
MTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCtPyxKj/fQoNCmVuZHN0
cmVhbQ1lbmRvYmoNNjIgMCBvYmo8PC9MZW5ndGggNjQvV2lkdGggMjEvSGVpZ2h0IDEvQml0c1Bl
ckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdl
Pj5zdHJlYW0NCsPzwG3lNkPLAErNBEvRBErPBErRBE/QCkvNBU7PCUvOBU3PCEzNBk7OCEvOBUrR
BE/PCkrNBU/PCkrNBE7OCQoNCmVuZHN0cmVhbQ1lbmRvYmoNNjMgMCBvYmo8PC9MZW5ndGggMTMv
V2lkdGggNC9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlw
ZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0Kxunxvd7lyevu2OvrCg0KZW5kc3RyZWFt
DWVuZG9iag02NCAwIG9iajw8L0xlbmd0aCAxMC9XaWR0aCAzL0hlaWdodCAxL0JpdHNQZXJDb21w
b25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3Ry
ZWFtDQrV/5iM+guu/1MKDQplbmRzdHJlYW0NZW5kb2JqDTY1IDAgb2JqPDwvTGVuZ3RoIDcvV2lk
dGggMi9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9Y
T2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KufGai/dUCg0KZW5kc3RyZWFtDWVuZG9iag02
NiAwIG9iajw8L0xlbmd0aCA2NC9XaWR0aCAyMS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgv
Q29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0Kw/O/
bOU2SM0ASs4ETc8ISs4ETdAITM4GSc0DSs0ESc0DSs0ESc0DSs0ETs8JSs4FT88JSs0FT88KSs0E
S80FCg0KZW5kc3RyZWFtDWVuZG9iag02NyAwIG9iajw8L0xlbmd0aCA0MC9XaWR0aCAxMy9IZWln
aHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1
YnR5cGUvSW1hZ2U+PnN0cmVhbQ0Kt9rphq3bYo/RSnjMNWnHLGjMJVnFKVTGIEe4OE6/YGS/jKPc
ytb7Cg0KZW5kc3RyZWFtDWVuZG9iag02OCAwIG9iajw8L0xlbmd0aCAxMC9XaWR0aCAzL0hlaWdo
dCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3Vi
dHlwZS9JbWFnZT4+c3RyZWFtDQqZ/huk/zbO/KsKDQplbmRzdHJlYW0NZW5kb2JqDTY5IDAgb2Jq
PDwvTGVuZ3RoIDEwL1dpZHRoIDMvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3Bh
Y2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCt754pP9bHTlPQoN
CmVuZHN0cmVhbQ1lbmRvYmoNNzAgMCBvYmo8PC9MZW5ndGggNjQvV2lkdGggMjEvSGVpZ2h0IDEv
Qml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBl
L0ltYWdlPj5zdHJlYW0NCsPzwG3lNkTLAEnNBErNBEnNBE/PCUvNBU7PB07OCEnNAk3PCEvNBU7P
CEvNBk7OCEvNBk7OCUvOBUvRBE7PCQoNCmVuZHN0cmVhbQ1lbmRvYmoNNzEgMCBvYmo8PC9MZW5n
dGggNTgvV2lkdGggMTkvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUg
MCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCpO73mGP0k6C1kF30jJszixl
zR9Zxw1JuwRAuAA1tAAsswMjtQ4cshgdrVZdu7rukJX+HZ3/J8v/lAoNCmVuZHN0cmVhbQ1lbmRv
YmoNNzIgMCBvYmo8PC9MZW5ndGggMTAvV2lkdGggMy9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50
IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0K
v/Kxce81iO1hCg0KZW5kc3RyZWFtDWVuZG9iag03MyAwIG9iajw8L0xlbmd0aCA2NC9XaWR0aCAy
MS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2Jq
ZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0Kw/PAbeU2Q8sATs8ISs4ETc8ITM4GSc0DTNAFTdEH
Sc0DT88KSs0ESs0ETs8JS80GTs8IS80GTs8JSs4ES80FCg0KZW5kc3RyZWFtDWVuZG9iag03NCAw
IG9iajw8L0xlbmd0aCA2NC9XaWR0aCAyMS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29s
b3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KlLreaJLV
WYvYWYfWT3zNUX7NS3vLQXTJOGzIMGXFI1zBD0y8BD+3ADCyAB2sAACmUl6/wf+DkPwckPwXrf53
Cg0KZW5kc3RyZWFtDWVuZG9iag03NSAwIG9iajw8L0xlbmd0aCAxMC9XaWR0aCAzL0hlaWdodCAx
L0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlw
ZS9JbWFnZT4+c3RyZWFtDQrm+9+X9Gta5hUKDQplbmRzdHJlYW0NZW5kb2JqDTc2IDAgb2JqPDwv
TGVuZ3RoIDY0L1dpZHRoIDIxL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNl
IDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQrD88Bt5TZDywBKzQRK
zQRKzQRNzwhKzQNf1CiH4myS5XxV0RZGzAFJzQNKzQROzwlLzgVL0QRPzwpKzQROzwkKDQplbmRz
dHJlYW0NZW5kb2JqDTc3IDAgb2JqPDwvTGVuZ3RoIDczL1dpZHRoIDI0L0hlaWdodCAxL0JpdHNQ
ZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFn
ZT4+c3RyZWFtDQqv0uN7nttmk9prldtuk9V0mNZyl9VqkdRnj9Nch9BPfsxEdss2bMgkXcITTr0D
QbgAJ64LGLd9kcW9/16I+Q+X/hphrUhRZbEKDQplbmRzdHJlYW0NZW5kb2JqDTc4IDAgb2JqPDwv
TGVuZ3RoIDEwL1dpZHRoIDMvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2Ug
MTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCr3vo17gHm/jPwoNCmVu
ZHN0cmVhbQ1lbmRvYmoNNzkgMCBvYmo8PC9MZW5ndGggMjUvV2lkdGggOC9IZWlnaHQgMS9CaXRz
UGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1h
Z2U+PnN0cmVhbQ0Kw/O/bOU2SM0ASs4ETc4ISs4ESc8DSc8CCg0KZW5kc3RyZWFtDWVuZG9iag04
MCAwIG9iajw8L0xlbmd0aCAzNC9XaWR0aCAxMS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgv
Q29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KxPXI
YNwlQ8sATc4ISc0ET88KSs0ESc4DT88KSs0ES80FCg0KZW5kc3RyZWFtDWVuZG9iag04MSAwIG9i
ajw8L0xlbmd0aCA3OS9XaWR0aCAyNi9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JT
cGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0Km7rXbpvebpbb
dJfXhKTahqbahqbahaXahKXZgaHZcpbWZ4/SWoTSRXXPN2zHJFzCEE29AC+xLkHGq8a6qf85hfcO
l/8cVJlDBwmEMDmdCg0KZW5kc3RyZWFtDWVuZG9iag04MiAwIG9iajw8L0xlbmd0aCAxMy9XaWR0
aCA0L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hP
YmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQrY88uA60pB0Qif9YkKDQplbmRzdHJlYW0NZW5k
b2JqDTgzIDAgb2JqPDwvTGVuZ3RoIDI1L1dpZHRoIDgvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVu
dCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0N
CsPzwG3lNkTLAEnNA0rNBEnNA0zSBE3VBQoNCmVuZHN0cmVhbQ1lbmRvYmoNODQgMCBvYmo8PC9M
ZW5ndGggMzQvV2lkdGggMTEvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2Ug
MTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCsL1xWTiKUjPAk3SB0zR
BUrOBU7OCUrNBU/PCUrNBE7PCQoNCmVuZHN0cmVhbQ1lbmRvYmoNODUgMCBvYmo8PC9MZW5ndGgg
NjEvV2lkdGggMjAvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBS
L1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCoyr3GqV23SX14Oj24ql4Zqz4Jmz
4Jmz4Jmz4Ju04JWu4YWi34Gi2XCV1leD0ER2yjdsxyBZwBFNy3CJ5goNCmVuZHN0cmVhbQ1lbmRv
YmoNODYgMCBvYmo8PC9MZW5ndGggMjIvV2lkdGggNy9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50
IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0K
m/8mj/kcmv8UV5RQAACNAwSGISiMCg0KZW5kc3RyZWFtDWVuZG9iag04NyAwIG9iajw8L0xlbmd0
aCAxMy9XaWR0aCA0L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAg
Ui9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQrn/OCb9HA+yQBz7EMKDQplbmRz
dHJlYW0NZW5kb2JqDTg4IDAgb2JqPDwvTGVuZ3RoIDI1L1dpZHRoIDgvSGVpZ2h0IDEvQml0c1Bl
ckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdl
Pj5zdHJlYW0NCsPzwG3lNkPLAEnNA0jNAlXQFWjYNGvaOQoNCmVuZHN0cmVhbQ1lbmRvYmoNODkg
MCBvYmo8PC9MZW5ndGggMzQvV2lkdGggMTEvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0Nv
bG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCsf2y3jk
SmXVMGrXOWbVLkvNBknOA0rNBE/PCkrNBErNBQoNCmVuZHN0cmVhbQ1lbmRvYmoNOTAgMCBvYmo8
PC9MZW5ndGggOTEvV2lkdGggMzAvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3Bh
Y2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCoyq3WSR2XOX2Imk
4Zuz4qO45azB5azB5a3C5a3C5aq/5aK35Jqw4pOp4X2g2GiP01iEz0V4yyFbwS5e067Lzbv/UIn5
Epb+IZL8GkFyWwAAkQAAigICexwiegoNCmVuZHN0cmVhbQ1lbmRvYmoNOTEgMCBvYmo8PC9MZW5n
dGggMTAvV2lkdGggMy9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAw
IFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KreuUYOAfTNsDCg0KZW5kc3Ry
ZWFtDWVuZG9iag05MiAwIG9iajw8L0xlbmd0aCAxOS9XaWR0aCA2L0hlaWdodCAxL0JpdHNQZXJD
b21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+
c3RyZWFtDQrD88Bt5TZDywBJzQJIzgF04EcKDQplbmRzdHJlYW0NZW5kb2JqDTkzIDAgb2JqPDwv
TGVuZ3RoIDE5L1dpZHRoIDYvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2Ug
MTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NClrSG0rTAkrNBE/PCkrN
BE/PCQoNCmVuZHN0cmVhbQ1lbmRvYmoNOTQgMCBvYmo8PC9MZW5ndGggNjQvV2lkdGggMjEvSGVp
Z2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9T
dWJ0eXBlL0ltYWdlPj5zdHJlYW0NCou021yI3XOY14el25ir5KW55bHE57zN7sHQ8M3b98nX9LzM
7bXG56i+5Jqw4pKp4Xyf2GWN0018zEJ32o+l8QoNCmVuZHN0cmVhbQ1lbmRvYmoNOTUgMCBvYmo8
PC9MZW5ndGggMzEvV2lkdGggMTAvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3Bh
Y2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCqH/K4r1H5X/G4Pi
JixQcAAAlQAAigAAggICZyQscQoNCmVuZHN0cmVhbQ1lbmRvYmoNOTYgMCBvYmo8PC9MZW5ndGgg
MTMvV2lkdGggNC9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIv
VHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KwOypb+YwPssAh+xeCg0KZW5kc3Ry
ZWFtDWVuZG9iag05NyAwIG9iajw8L0xlbmd0aCAxOS9XaWR0aCA2L0hlaWdodCAxL0JpdHNQZXJD
b21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+
c3RyZWFtDQrD88Bt5TZDywBJzQNJzgFu3DwKDQplbmRzdHJlYW0NZW5kb2JqDTk4IDAgb2JqPDwv
TGVuZ3RoIDIyL1dpZHRoIDcvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2Ug
MTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCr3zt1rYGkbNAErNBE/P
CkrNBErNBQoNCmVuZHN0cmVhbQ1lbmRvYmoNOTkgMCBvYmo8PC9MZW5ndGggMTAzL1dpZHRoIDM0
L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmpl
Y3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQqnzeBShdZnjtWGptqVrN2kuOWzxujG1O7N2O/U2/LW
3PPT2/PL1/HK2PS1x+enveSaseGLptpvlNVPfc52luXK6L+m/zSK+hOQ+CeX/xZsvDoSIogAAJIA
AIkAAIMAAHADBFQ9SXgKDQplbmRzdHJlYW0NZW5kb2JqDTEwMCAwIG9iajw8L0xlbmd0aCAxMy9X
aWR0aCA0L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBl
L1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQrR87566T8/yQBq6TAKDQplbmRzdHJlYW0N
ZW5kb2JqDTEwMSAwIG9iajw8L0xlbmd0aCAyNS9XaWR0aCA4L0hlaWdodCAxL0JpdHNQZXJDb21w
b25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3Ry
ZWFtDQrD88Bt5TZDywBJzQRJzQNMzghY0hZl1ysKDQplbmRzdHJlYW0NZW5kb2JqDTEwMiAwIG9i
ajw8L0xlbmd0aCAzNC9XaWR0aCAxMS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JT
cGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KxfXHb+A6W9EZ
X9MgW9YcTc8HSM0DSs0ET88KSs0ET88JCg0KZW5kc3RyZWFtDWVuZG9iag0xMDMgMCBvYmo8PC9M
ZW5ndGggMjUvV2lkdGggOC9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAx
NSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KV4rOWIbSdprXiKfbnbXh
sMTnxNX01t/0Cg0KZW5kc3RyZWFtDWVuZG9iag0xMDQgMCBvYmo8PC9MZW5ndGggNjcvV2lkdGgg
MjIvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9i
amVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCtrj+8bU8LPE56K35Jax3nCW1XiV5Mfb2Lf/Woz/
Eo74JJD6HZf+Fk+JWQEBngAAjwAAiQAAggAAcAAAXgYHQGZ7jAoNCmVuZHN0cmVhbQ1lbmRvYmoN
MTA1IDAgb2JqPDwvTGVuZ3RoIDEzL1dpZHRoIDQvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4
L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCtjz
zX/pSEDLAFfdEwoNCmVuZHN0cmVhbQ1lbmRvYmoNMTA2IDAgb2JqPDwvTGVuZ3RoIDI1L1dpZHRo
IDgvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9i
amVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCsPzwG3lNkPLAE7PCEvOBUjMAUvUA07XBgoNCmVu
ZHN0cmVhbQ1lbmRvYmoNMTA3IDAgb2JqPDwvTGVuZ3RoIDM0L1dpZHRoIDExL0hlaWdodCAxL0Jp
dHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9J
bWFnZT4+c3RyZWFtDQq+88Bk5CdI0QBM0wRHzQBOzghL0QVKzgRPzwpKzQRKzQUKDQplbmRzdHJl
YW0NZW5kb2JqDTEwOCAwIG9iajw8L0xlbmd0aCAyNS9XaWR0aCA4L0hlaWdodCAxL0JpdHNQZXJD
b21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+
c3RyZWFtDQp9pdhFeM9hitJ5m9iLpuGluue6zvDX4/MKDQplbmRzdHJlYW0NZW5kb2JqDTEwOSAw
IG9iajw8L0xlbmd0aCA0L1dpZHRoIDEvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9y
U3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCuHT+woNCmVu
ZHN0cmVhbQ1lbmRvYmoNMTEwIDAgb2JqPDwvTGVuZ3RoIDY0L1dpZHRoIDIxL0hlaWdodCAxL0Jp
dHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9J
bWFnZT4+c3RyZWFtDQrT4PvC0OynveOTsOCVrO3Bz+XB/naJ+BWL9h+M9SOV/xd92S0kQ4gAAKsB
AY0AAIkAAIMAAHEAAWAAAEAeJVAKDQplbmRzdHJlYW0NZW5kb2JqDTExMSAwIG9iajw8L0xlbmd0
aCAxNi9XaWR0aCA1L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAg
Ui9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQra9NB/6UlBywBDzAGc9IMKDQpl
bmRzdHJlYW0NZW5kb2JqDTExMiAwIG9iajw8L0xlbmd0aCAyNS9XaWR0aCA4L0hlaWdodCAxL0Jp
dHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9J
bWFnZT4+c3RyZWFtDQrD88Bt5TZDywBKzQRJzgNJzQNKzwNP0QkKDQplbmRzdHJlYW0NZW5kb2Jq
DTExMyAwIG9iajw8L0xlbmd0aCAzNC9XaWR0aCAxMS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50
IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0K
wPTCYd0mRcsASc0DSc0DSs0FT88KSs0FT88JSs0ET88JCg0KZW5kc3RyZWFtDWVuZG9iag0xMTQg
MCBvYmo8PC9MZW5ndGggMjIvV2lkdGggNy9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29s
b3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KP3HJSXvQ
Y4zSepzYl7LjqsHsytfuCg0KZW5kc3RyZWFtDWVuZG9iag0xMTUgMCBvYmo8PC9MZW5ndGggMTYv
V2lkdGggNS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlw
ZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0K4ND7x7D71cb4/v3/+/78Cg0KZW5kc3Ry
ZWFtDWVuZG9iag0xMTYgMCBvYmo8PC9MZW5ndGggNjcvV2lkdGggMjIvSGVpZ2h0IDEvQml0c1Bl
ckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdl
Pj5zdHJlYW0NCtTh+8bT7aq+5Z+v69Hb8cr+iI76Gon3Go/4JJD6IZX/FFacVQEIpwACnwEBjwAA
iQAAigAAeQABXQABTgAAKVdrdwoNCmVuZHN0cmVhbQ1lbmRvYmoNMTE3IDAgb2JqPDwvTGVuZ3Ro
IDE2L1dpZHRoIDUvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBS
L1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCuL603/qSEHLAEPLAJT2dgoNCmVu
ZHN0cmVhbQ1lbmRvYmoNMTE4IDAgb2JqPDwvTGVuZ3RoIDI1L1dpZHRoIDgvSGVpZ2h0IDEvQml0
c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0lt
YWdlPj5zdHJlYW0NCsPzwG3lNkPLAEnNA0rRBEnPA0rPA1DRCgoNCmVuZHN0cmVhbQ1lbmRvYmoN
MTE5IDAgb2JqPDwvTGVuZ3RoIDM0L1dpZHRoIDExL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQg
OC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQrA
9MJh3SVFywBOzwlKzgRJzQNPzwlLzQZOzwlKzgRKzQUKDQplbmRzdHJlYW0NZW5kb2JqDTEyMCAw
IG9iajw8L0xlbmd0aCAyMi9XaWR0aCA3L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xv
clNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQp6o9cpYshH
eMtokNR+od+ZtOvJ1+4KDQplbmRzdHJlYW0NZW5kb2JqDTEyMSAwIG9iajw8L0xlbmd0aCAxOS9X
aWR0aCA2L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBl
L1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQrXxfnKtP7DrPfLtfzy5//5+vsKDQplbmRz
dHJlYW0NZW5kb2JqDTEyMiAwIG9iajw8L0xlbmd0aCAxMy9XaWR0aCA0L0hlaWdodCAxL0JpdHNQ
ZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFn
ZT4+c3RyZWFtDQrb5vzE1PLB0fzb2/cKDQplbmRzdHJlYW0NZW5kb2JqDTEyMyAwIG9iajw8L0xl
bmd0aCA1Mi9XaWR0aCAxNy9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAx
NSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KnP8mivcbkPkfkfodlv8Y
edsyIkmOAACrAQKTAQKVAQGPAACCAABxAAFeAAFQAAAnHSY3Cg0KZW5kc3RyZWFtDWVuZG9iag0x
MjQgMCBvYmo8PC9MZW5ndGggMTYvV2lkdGggNS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgv
Q29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0K4f/O
eOc+QcsAQ8wAh+5jCg0KZW5kc3RyZWFtDWVuZG9iag0xMjUgMCBvYmo8PC9MZW5ndGggMjUvV2lk
dGggOC9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9Y
T2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0Kw/PAbeU2RMsASc0DSs0ESc0DSs8DUNEKCg0K
ZW5kc3RyZWFtDWVuZG9iag0xMjYgMCBvYmo8PC9MZW5ndGggMzQvV2lkdGggMTEvSGVpZ2h0IDEv
Qml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBl
L0ltYWdlPj5zdHJlYW0NCsD0wmHdJkTLAEnNA0vSBUnOA0zSBU7PCUvOBUvRBE/PCgoNCmVuZHN0
cmVhbQ1lbmRvYmoNMTI3IDAgb2JqPDwvTGVuZ3RoIDE5L1dpZHRoIDYvSGVpZ2h0IDEvQml0c1Bl
ckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdl
Pj5zdHJlYW0NCjVrxihiyEJ1yl6K0J+759Hc8goNCmVuZHN0cmVhbQ1lbmRvYmoNMTI4IDAgb2Jq
PDwvTGVuZ3RoIDIyL1dpZHRoIDcvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3Bh
Y2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCs24+Mqz/cKs9sOt
9sKs9tK8/uDU+goNCmVuZHN0cmVhbQ1lbmRvYmoNMTI5IDAgb2JqPDwvTGVuZ3RoIDg1L1dpZHRo
IDI4L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hP
YmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQrT3frG0PPf6OvI/omP+h6N+RyQ+CSO9yKX/x2R
/RtBjWwBELUBC6ABAJQBAZAAAIoAAIIAAHAAAV4AAU0AADQAAA5rc4PC7rZk2C0+yQA9yQB/6lkK
DQplbmRzdHJlYW0NZW5kb2JqDTEzMCAwIG9iajw8L0xlbmd0aCAyNS9XaWR0aCA4L0hlaWdodCAx
L0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlw
ZS9JbWFnZT4+c3RyZWFtDQrD879s5TZIzQBLzgVNzghLzgVJzwNQ0QoKDQplbmRzdHJlYW0NZW5k
b2JqDTEzMSAwIG9iajw8L0xlbmd0aCAzNC9XaWR0aCAxMS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9u
ZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVh
bQ0KwPTCYd0mRMsASs0ETs8JS80FTs8IS80GTs8JS84FSc0ECg0KZW5kc3RyZWFtDWVuZG9iag0x
MzIgMCBvYmo8PC9MZW5ndGggMTYvV2lkdGggNS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgv
Q29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KlrnU
EU/AIVrBW4nWqb7lCg0KZW5kc3RyZWFtDWVuZG9iag0xMzMgMCBvYmo8PC9MZW5ndGggMzEvV2lk
dGggMTAvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUv
WE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCuHR+sq0+sex+sOt9sOt9sOt9sOs9sOr99PH
/eLp9woNCmVuZHN0cmVhbQ1lbmRvYmoNMTM0IDAgb2JqPDwvTGVuZ3RoIDQvV2lkdGggMS9IZWln
aHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1
YnR5cGUvSW1hZ2U+PnN0cmVhbQ0K3uT7Cg0KZW5kc3RyZWFtDWVuZG9iag0xMzUgMCBvYmo8PC9M
ZW5ndGggNzkvV2lkdGggMjYvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2Ug
MTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCsr+hZH9H477Hoz3Hoz4
G4z4Hpj/F2jERRE7pQAIsgADnQEClAEClQEBjwAAgQAAcAABYAABRQAAOAAAC0xJVqHTh2DdIEPK
AD/JAH/qWAoNCmVuZHN0cmVhbQ1lbmRvYmoNMTM2IDAgb2JqPDwvTGVuZ3RoIDUyL1dpZHRoIDE3
L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmpl
Y3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpmjtE4ZdCOqd3Q1PPg0frOufjErffHsvrJs/fDrfbD
rfbErvfEsfbMwPXT3PLZ5f3X3fcKDQplbmRzdHJlYW0NZW5kb2JqDTEzNyAwIG9iajw8L0xlbmd0
aCAzNC9XaWR0aCAxMS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAw
IFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KwPTCYd0lRcsATs8JS80GTs8I
S80GTs8IS80GTs4JSc0DCg0KZW5kc3RyZWFtDWVuZG9iag0xMzggMCBvYmo8PC9MZW5ndGggODIv
V2lkdGggMjcvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5
cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCsD/aYr4Fo35HJH4JI74HpH6HJX/F33j
MydpjQAftAASsAAAowEClAEBkAAAiQAAggAAcQABXwABRAAALwAABVxaYZHWaVbZDUbMAETMAInu
ZQoNCmVuZHN0cmVhbQ1lbmRvYmoNMTM5IDAgb2JqPDwvTGVuZ3RoIDEzNi9XaWR0aCA0NS9IZWln
aHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1
YnR5cGUvSW1hZ2U+PnN0cmVhbQ0Kv8ns1cn83s76zbj3xa/3xq/6wqz2w632xq/3xa33xq72x7r1
wsrzxtPtxtTrx9HzvsrusOObnP8uivgZjvgekfscjPYik/4ZivYkPpZ7AC29AB2rARCnAAOdAQKU
AQGOAACKAACBAABxAABXAAA8AAArAgIafo6BhuNTRNAASc8DQsoAnPuACg0KZW5kc3RyZWFtDWVu
ZG9iag0xNDAgMCBvYmo8PC9MZW5ndGggMzQvV2lkdGggMTEvSGVpZ2h0IDEvQml0c1BlckNvbXBv
bmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJl
YW0NCr70wGLfJ0TLAEnNA0/PCkrNBU7PCEvNBk7PCUvNBUnNAwoNCmVuZHN0cmVhbQ1lbmRvYmoN
MTQxIDAgb2JqPDwvTGVuZ3RoIDI1L1dpZHRoIDgvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4
L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCsPz
wG3lNkPLAEnNA0rNBEnNA0rPA0/RCQoNCmVuZHN0cmVhbQ1lbmRvYmoNMTQyIDAgb2JqPDwvTGVu
Z3RoIDM0L1dpZHRoIDExL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1
IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQrJ9spf2yNFzABKzQROzwlK
zQRKzQROzwlLzQZOzwlJzQMKDQplbmRzdHJlYW0NZW5kb2JqDTE0MyAwIG9iajw8L0xlbmd0aCAx
NTEvV2lkdGggNTAvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBS
L1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCuHV+d3S/9vP/9nJ/tbF+NjG+cuz
+MWs9sav9sav9siw98iw+Miw98i09r+s9byw8rS/6bbH6LfI6LfG6LTF56m96qS+2aDhf5j8K4z3
HI35Hpj/HI/7HEukbgZBvQAutAAbrAENpwADmwEBjwAAigAAigAAdwAAZwAAVgAAPwAAHC4qSpe+
i23jMT3IAErNA0TOA6f3lQoNCmVuZHN0cmVhbQ1lbmRvYmoNMTQ0IDAgb2JqPDwvTGVuZ3RoIDI1
L1dpZHRoIDgvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5
cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCsPzwG3lNkPLAEnNA07PCEvOBUrPBErQ
AwoNCmVuZHN0cmVhbQ1lbmRvYmoNMTQ1IDAgb2JqPDwvTGVuZ3RoIDMxL1dpZHRoIDEwL0hlaWdo
dCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3Vi
dHlwZS9JbWFnZT4+c3RyZWFtDQpl1S1K1wBJzABHzABJzQNPzwpKzQVPzwpKzQRKzQQKDQplbmRz
dHJlYW0NZW5kb2JqDTE0NiAwIG9iajw8L0xlbmd0aCAxNDUvV2lkdGggNDgvSGVpZ2h0IDEvQml0
c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0lt
YWdlPj5zdHJlYW0NCtXe8tHV/cu698Ou9se19si1+Mu3+sq3+ci0+Mq1+cGv87So8KGl6ZSp4piz
4Jqz4aW65Kq/5aO35KG345mx342k5IavzZbpapz/JpD9Fpf9FWK6WxBMuwA3wAErrgEMrQABpQEC
kwEClQEBkAAAgwAAcQABYAABTQAAOgAAFnJygJrgeFLWCkXLAEjNAV3fHQoNCmVuZHN0cmVhbQ1l
bmRvYmoNMTQ3IDAgb2JqPDwvTGVuZ3RoIDI4L1dpZHRoIDkvSGVpZ2h0IDEvQml0c1BlckNvbXBv
bmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJl
YW0NCsPzwG3lNkPLAEnNA0zSBUnPA03OB0vQBZzsjAoNCmVuZHN0cmVhbQ1lbmRvYmoNMTQ4IDAg
b2JqPDwvTGVuZ3RoIDMxL1dpZHRoIDEwL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xv
clNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQqk6Y5o4jFi
3yhU0hVKzQVPzwpKzQVPzwpKzQRPzwkKDQplbmRzdHJlYW0NZW5kb2JqDTE0OSAwIG9iajw8L0xl
bmd0aCAxMzYvV2lkdGggNDUvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2Ug
MTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCrS563l80nN74HaE5IGR
6HqJ6HiI5GmB0mCJ0WiQ03ea14Kk2Yal2pGq3JWu34+o25Co242o236g2WyP23GluZbvUZb8G2fB
VhtZtgA4wgAvsQAbqgENpQADmwEClQEBkQAAhwAAggAAcAABXAABRgAAHB4VPJy0lnjpQTnHAEvN
BEXLAHfuQgoNCmVuZHN0cmVhbQ1lbmRvYmoNMTUwIDAgb2JqPDwvTGVuZ3RoIDI4L1dpZHRoIDkv
SGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVj
dC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCsPzwG3lNkPLAEnNA07OCEvOBUjNAkrPA3XgSgoNCmVu
ZHN0cmVhbQ1lbmRvYmoNMTUxIDAgb2JqPDwvTGVuZ3RoIDI4L1dpZHRoIDkvSGVpZ2h0IDEvQml0
c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0lt
YWdlPj5zdHJlYW0NCs/409P/2Z7pjFLREEvOBUrNBU7PCUrNBEvNBQoNCmVuZHN0cmVhbQ1lbmRv
YmoNMTUyIDAgb2JqPDwvTGVuZ3RoIDEzNi9XaWR0aCA0NS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9u
ZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVh
bQ0KpcfYEhqlAA+mACOuATi1EUi/HFbALWXFRXfKU4HNYInSapHUc5fWdZjWdprXdpnWdZjWcZXV
Y4zSUn7SR3TSY6WTablkHVy0BUHDBDi1ACCtARCoAAOdAQKUAQKVAQGQAACBAAB6AAFoAAFNAAA8
AQEbb2yBnOF4StMIQMkATs8ISM8BlO90Cg0KZW5kc3RyZWFtDWVuZG9iag0xNTMgMCBvYmo8PC9M
ZW5ndGggMzEvV2lkdGggMTAvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2Ug
MTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCsPzwG3lNkPLAErNBErO
BEnNA0nNA0jNAUnPAonjbAoNCmVuZHN0cmVhbQ1lbmRvYmoNMTU0IDAgb2JqPDwvTGVuZ3RoIDIy
L1dpZHRoIDcvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5
cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCqnunlfXF0bMAEnNA0nNA0rNA0/PCgoN
CmVuZHN0cmVhbQ1lbmRvYmoNMTU1IDAgb2JqPDwvTGVuZ3RoIDEzMy9XaWR0aCA0NC9IZWlnaHQg
MS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5
cGUvSW1hZ2U+PnN0cmVhbQ0KvdDnERmuAA6nACCsAC2uBkK4Ek28IVrBNGnGPHDKSXfQUoDMWYTQ
YInSZY3TZIzUXIfRVoPOTn7MQnXKNWrHKF/FG1PFBUPBAzi0ACCsARapAQ6mAAObAQKUAQGPAACI
AACCAABwAAFdAAFPAAApNC9Vo8OYcuQ5PMgAS80ESM0BXOAZCg0KZW5kc3RyZWFtDWVuZG9iag0x
NTYgMCBvYmo8PC9MZW5ndGggNjQvV2lkdGggMjEvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4
L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCsPz
wG3lNkPLAE7OCEzRBUrPBEnNA0nNA0jNAUnPAmPYL3/iXYbhZHfcU13TJUrNBEjNAknNA0nOA0rN
BUnNAwoNCmVuZHN0cmVhbQ1lbmRvYmoNMTU3IDAgb2JqPDwvTGVuZ3RoIDEzMC9XaWR0aCA0My9I
ZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0
L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KFRmqAAemARKnARupADSzATu1CUa5H1rAKGDEMmfGPHHI
RHXLRXXPRnbMRnTPRHbKQnTKN2zILmXFI13CEU6+Aj64ADSyACOqARGpAQ2pAAObAQKVAQGQAACJ
AACDAAB6AABmAAFWAAA9Dgs3kZeekehlR80BTM4FTM4HRMsAg/VXCg0KZW5kc3RyZWFtDWVuZG9i
ag0xNTggMCBvYmo8PC9MZW5ndGggNjQvV2lkdGggMjEvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVu
dCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0N
CsPzwG3lNkPLAErNBEnNA0/PCUvOBUnNA0nNA0jMAknPAknPAkvPBEHMAEjNA0nNA0nNA0nOA0zS
Bk7PCUnNAwoNCmVuZHN0cmVhbQ1lbmRvYmoNMTU5IDAgb2JqPDwvTGVuZ3RoIDEzMC9XaWR0aCA0
My9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2Jq
ZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KKCypBAScAASgARKsACKtATGzATi1B0S4D0u8GlS/
JV3CKGDDKWDEMGXGLmXFJ1/DI1zCHVfAFVG+C0i7ADW0ACuvLUy8Lj25AAClAACjAQKUAQKVAQGO
AACIAAB/AABtAAFgAABGBwQvdHKJpeSJUNQWRssDTc4HRswBUNkRqfiYCg0KZW5kc3RyZWFtDWVu
ZG9iag0xNjAgMCBvYmo8PC9MZW5ndGggNjQvV2lkdGggMjEvSGVpZ2h0IDEvQml0c1BlckNvbXBv
bmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJl
YW0NCsPzwG3lNkPLAE3OB0rOBE7PCUvNBUrNBUnNA0nOA0nNA0jNAk3OCEnNBE3OCErOBEnNA0vN
Bk7OCUvNBknNAwoNCmVuZHN0cmVhbQ1lbmRvYmoNMTYxIDAgb2JqPDwvTGVuZ3RoIDEyNy9XaWR0
aCA0Mi9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9Y
T2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KQ06tBgiYAACWAAGqARKpARiqACiwADWzATe0
BUK4CES5Ek28E069Ek29F1O/EEy8BEK4BkW5Az62ACauCyKtUWfEs8PthYflFBqtAACQAQGSAQGP
AACKAACEAAByAABeAABOAgA4WlJ8sNmdaeIrQMkAUM8LS84GQ88Ag+pVCg0KZW5kc3RyZWFtDWVu
ZG9iag0xNjIgMCBvYmo8PC9MZW5ndGggNjQvV2lkdGggMjEvSGVpZ2h0IDEvQml0c1BlckNvbXBv
bmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJl
YW0NCsPzwG3lNkPLAEvNBUrNBE/PCUvOBU3OB0zNBkrRA0nOA0nNA0nNA0nNA0rNBEvSBEnOA07O
CUvNBk7PCUnNAwoNCmVuZHN0cmVhbQ1lbmRvYmoNMTYzIDAgb2JqPDwvTGVuZ3RoIDEyNC9XaWR0
aCA0MS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9Y
T2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KaX+7Cg2TAACTAQKVAAagARKoAROqABqvACSt
ADWzADSzATa0BD23ADe1BkG4BD62ADGyACmwACKsIzKyeYfRwsjznaXxeojuYWvbFBafAACFAACI
AACGAACAAABxAABQAgA3Ukh9ss+mcOQ6PsgATs4HSc0ER8sAYOoaCg0KZW5kc3RyZWFtDWVuZG9i
ag0xNjQgMCBvYmo8PC9MZW5ndGggNjQvV2lkdGggMjEvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVu
dCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0N
CsPzwG3lNkPLAE7OCErNBE7OCUzRBkrOBE7OCUzNBknNA0nOA0nNA0nOA0/PCkvRBUvOBUrNBE/P
CkrNBEnNAwoNCmVuZHN0cmVhbQ1lbmRvYmoNMTY1IDAgb2JqPDwvTGVuZ3RoIDEyNC9XaWR0aCA0
MS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2Jq
ZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0Kqr/WDhGRAACSAQKVAQKXAASfAAOgAAKpAROoAByr
ACCtACGuACawACSvABurABaqABepHSmsSVfDo6jjvMP0ho7tb3vneYXqf4vwWGHSCQyQAAB7AAB4
AABwAABVAgA+Tkd8udKrguo/PckATs4IS84GTM4GSdABkO1pCg0KZW5kc3RyZWFtDWVuZG9iag0x
NjYgMCBvYmo8PC9MZW5ndGggNjQvV2lkdGggMjEvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4
L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCsPz
wG3lNkXMAEnNA0rNBU7OCEzNBk7QCErNBE7OCUrOBUvRBEnOA0zRBU7PCUvNBk7PCEvNBk7QCUnN
A0nNAwoNCmVuZHN0cmVhbQ1lbmRvYmoNMTY3IDAgb2JqPDwvTGVuZ3RoIDExOC9XaWR0aCAzOS9I
ZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0
L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KKDGVAgOKAQGVAQGTAQKVAQKUAQOXAASjAASfAA6iAAug
AAigAAaiCw2kJiayS1LFl53XvMT4n6fxb3zocn3oeYXqeITqd4PreYXrTlXCDQ+BAABtAABSBgVD
VVB+r82qeOdCPskATs4ITM4GSM0CQcoAdfI9Cg0KZW5kc3RyZWFtDWVuZG9iag0xNjggMCBvYmo8
PC9MZW5ndGggNjQvV2lkdGggMjEvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3Bh
Y2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCsPzv2zlNkjNAErO
BE3OCEzNBk3OCEzRB0nOA0/OCUvNBU7PCkvNBU/PCkrNBU/PCUrNBVDPCkrRBEvOBUnNAwoNCmVu
ZHN0cmVhbQ1lbmRvYmoNMTY5IDAgb2JqPDwvTGVuZ3RoIDExOC9XaWR0aCAzOS9IZWlnaHQgMS9C
aXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUv
SW1hZ2U+PnN0cmVhbQ0KboS4AwV/AACFAACBAACNAACNAACPAACZAACTAwWWExWeJSSmOTu5bHHL
oKPjsbTzoqzxe4XrcHvneITqeITqeITqeITqeITrhY/ydH7iJCmVAABVGhdSZGiFtN+ld+U8PskA
Ts4ITM4GSMwCRs0AWN8crfmdCg0KZW5kc3RyZWFtDWVuZG9iag0xNzAgMCBvYmo8PC9MZW5ndGgg
NjQvV2lkdGggMjEvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBS
L1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCsPzwG3lNkPLAEvOBUnNA0/PCkvN
BU7PCUvNBUzOB0zOBk3OCEzOBk3OB0rNBE/PCUrNBU3OB0zNB07PCUnNAgoNCmVuZHN0cmVhbQ1l
bmRvYmoNMTcxIDAgb2JqPDwvTGVuZ3RoIDExNS9XaWR0aCAzOC9IZWlnaHQgMS9CaXRzUGVyQ29t
cG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0
cmVhbQ0Ky+LjMDKWGxyHHB2PIiSZJCaZKC2fMDasRka6WVzCd4DZmJviqqzxrLj0k57wcX7pcXzo
d4PqeITqeITqdoLpdYHpfIjvg4/wanPVLTKbBgdhAABHXmd+suyUaeEoPskATM4HTM4HR8wCS9IC
RcoDkehxCg0KZW5kc3RyZWFtDWVuZG9iag0xNzIgMCBvYmo8PC9MZW5ndGggNjQvV2lkdGggMjEv
SGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVj
dC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCsPzwG3lNkPLAE7PCEvPBEzOB03NB03OCEvOBknNA1DP
Ck3OB1DPCkzOBknNA0/PCkrNBEvOBU3OCEnNA0vOBgoNCmVuZHN0cmVhbQ1lbmRvYmoNMTczIDAg
b2JqPDwvTGVuZ3RoIDEwL1dpZHRoIDMvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9y
U3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCtfh9s/Y/7G9
8AoNCmVuZHN0cmVhbQ1lbmRvYmoNMTc0IDAgb2JqPDwvTGVuZ3RoIDEwOS9XaWR0aCAzNi9IZWln
aHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1
YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KlZzegonWhIzdkZjcjpXblaLkmKbrpqbxqKvynafyipXwdYLq
cn/pcX3oeITqeIXqeITqeITqeITqfIbtfojwcXzmT1q7Fx15AABQAABGAQA+MUdCWrspTdgGSM0B
SM0CSMwDTdMFQ84AYcU8Cg0KZW5kc3RyZWFtDWVuZG9iag0xNzUgMCBvYmo8PC9MZW5ndGggNjQv
V2lkdGggMjEvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5
cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCsPzwG3lNkPLAEnNA03RBknPA03OB0zO
B07OCEjMAUnNAUnNAUnNAUrNA0jMAU3OB0rNBU3OCEvOBknNA07OCQoNCmVuZHN0cmVhbQ1lbmRv
YmoNMTc2IDAgb2JqPDwvTGVuZ3RoIDExOC9XaWR0aCAzOS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9u
ZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVh
bQ0KucD1h5b4e4f4jJfxkpzykZzyjpjxhI3ugIrsdoLrdIHpb3vnb3rncn3oeITqeITqeIXqdoLq
dIDpeITqe4fuforvfIXmY2vNLDKUAwVbAABGAAA8AAA1AAAsAAATITwZWr8mVNoMR8oBTNIETNUD
PaIVg6mGCg0KZW5kc3RyZWFtDWVuZG9iag0xNzcgMCBvYmo8PC9MZW5ndGggNjQvV2lkdGggMjEv
SGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVj
dC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCsPzwG3lNkPLAEnNA03OB03OB0nNA0nNAU3ZAlrfF2Tj
KGrlMGnkL2PjJljeE0TMAEjMAUvOBk3OCErNBEvOBgoNCmVuZHN0cmVhbQ1lbmRvYmoNMTc4IDAg
b2JqPDwvTGVuZ3RoIDExMi9XaWR0aCAzNy9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29s
b3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KvMjsk6X2
gIz6anTna3bmcHzncXzocXzneITqd4PqeITqd4Tqd4PqdYDpeITqeIXqeoXsf4nwforycX3nW2TL
OT2cCQ1lAABDAABAAAA8AAAvAAApAAAaAAAHAAACJ0saWcQjV+EOTtkEMJQCXXlcCg0KZW5kc3Ry
ZWFtDWVuZG9iag0xNzkgMCBvYmo8PC9MZW5ndGggNjQvV2lkdGggMjEvSGVpZ2h0IDEvQml0c1Bl
ckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdl
Pj5zdHJlYW0NCsPzwG3lNkXMAErNBEnNA0zOBkTMAGHhJH3cTpvlfLPsoMDvsr7vsLLsnZjjdGvY
Ok7RCU/PCUnNBEnNA07OCAoNCmVuZHN0cmVhbQ1lbmRvYmoNMTgwIDAgb2JqPDwvTGVuZ3RoIDEw
Ni9XaWR0aCAzNS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIv
VHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0K1ebwtbz3jZvzhI/9gI36fIfvg47x
fIjtgIvufIfsgIvufIfsfojvfovzf4vzfYjpdX/cU1zBMjiZCw1nAABNAAA+AAA9AAAxAAAtAAAd
AAAVAAAJAAAAAAABAAAELFcbVtIWKpMASGlJCg0KZW5kc3RyZWFtDWVuZG9iag0xODEgMCBvYmo8
PC9MZW5ndGggMjUvV2lkdGggOC9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFj
ZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0Kw/O/bOU2R8wAS84F
Sc0CRswAcuk+rO2aCg0KZW5kc3RyZWFtDWVuZG9iag0xODIgMCBvYmo8PC9MZW5ndGggMTkvV2lk
dGggNi9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9Y
T2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0Kse6nWNkYSs0DSs0ESc0DS84GCg0KZW5kc3Ry
ZWFtDWVuZG9iag0xODMgMCBvYmo8PC9MZW5ndGggMTAwL1dpZHRoIDMzL0hlaWdodCAxL0JpdHNQ
ZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFn
ZT4+c3RyZWFtDQrP3PC3vfefqe52heFvd9Z3guyAiu94hO9+iO1zf+p1gN9eaMtTWrg/RZchKHYE
BVEAAD0AADQAADgAAC8AACcAACMAABsAABAAAAoAAAAAAAIAAAIAAAEFCAMXRAJDaz6ltbsKDQpl
bmRzdHJlYW0NZW5kb2JqDTE4NCAwIG9iajw8L0xlbmd0aCAyMi9XaWR0aCA3L0hlaWdodCAxL0Jp
dHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9J
bWFnZT4+c3RyZWFtDQrD88Bt5TZDywBJzQNDywB67EzI+MgKDQplbmRzdHJlYW0NZW5kb2JqDTE4
NSAwIG9iajw8L0xlbmd0aCAxMy9XaWR0aCA0L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9D
b2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQqX54Oc
/IKX93ya74YKDQplbmRzdHJlYW0NZW5kb2JqDTE4NiAwIG9iajw8L0xlbmd0aCAxOS9XaWR0aCA2
L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmpl
Y3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQqG32FQ0w1HzABJzQNJzQNOzgkKDQplbmRzdHJlYW0N
ZW5kb2JqDTE4NyAwIG9iajw8L0xlbmd0aCA4OC9XaWR0aCAyOS9IZWlnaHQgMS9CaXRzUGVyQ29t
cG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0
cmVhbQ0KkJ3DQEOFLzN8Nz2HOT+SNjyMLzWJJSx0EhRUAQFAAAA0AAApAAAuAAAxAAAtAAAgAAAf
AAAUAAAPAAAKAAAAAAABAAACAAACAAACAAAABwgKLi01ucTCCg0KZW5kc3RyZWFtDWVuZG9iag0x
ODggMCBvYmo8PC9MZW5ndGggMTkvV2lkdGggNi9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgv
Q29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0Kw/PA
beU2Q8sAR80AZ+Urwfa8Cg0KZW5kc3RyZWFtDWVuZG9iag0xODkgMCBvYmo8PC9MZW5ndGggNDAv
V2lkdGggMTMvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5
cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCp7tjXHtPUTNAEHKAEHLAEPLAF/fIlLR
EEnMA0nNAknNA0zOBknNAgoNCmVuZHN0cmVhbQ1lbmRvYmoNMTkwIDAgb2JqPDwvTGVuZ3RoIDc5
L1dpZHRoIDI2L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9U
eXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQqIjJUtOUEAAAMAAA8AABcAABwAABoA
AB8AACEAACgAACEAACEAACMAABwAAA0AABAAAAoAAAAAAAEAAAIAAAIAAAIAAAAAAAAPExJPWVcK
DQplbmRzdHJlYW0NZW5kb2JqDTE5MSAwIG9iajw8L0xlbmd0aCAxNi9XaWR0aCA1L0hlaWdodCAx
L0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlw
ZS9JbWFnZT4+c3RyZWFtDQrD88Bt5TZDywBJ0AOq7pEKDQplbmRzdHJlYW0NZW5kb2JqDTE5MiAw
IG9iajw8L0xlbmd0aCA0My9XaWR0aCAxNC9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29s
b3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KpeqVW+AY
QcoASc0DSc0DSc0DSc0DR80ASM0BSc0DTM4GS88FTc4HSc0DCg0KZW5kc3RyZWFtDWVuZG9iag0x
OTMgMCBvYmo8PC9MZW5ndGggNzMvV2lkdGggMjQvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4
L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCrHI
xFdpbRsgLgAACgAADgAAEwAAHQAAEQAAFQAADgAADgAAEAAACgAAAAAAAAAAAQAAAgAAAgAAAgAA
AAAAAAICBDtHQ3KDfQoNCmVuZHN0cmVhbQ1lbmRvYmoNMTk0IDAgb2JqPDwvTGVuZ3RoIDEwL1dp
ZHRoIDMvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUv
WE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCq7A+FJowq7A4AoNCmVuZHN0cmVhbQ1lbmRv
YmoNMTk1IDAgb2JqPDwvTGVuZ3RoIDEzL1dpZHRoIDQvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVu
dCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0N
CsPzwG3lNkPMAFrZHQoNCmVuZHN0cmVhbQ1lbmRvYmoNMTk2IDAgb2JqPDwvTGVuZ3RoIDQzL1dp
ZHRoIDE0L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBl
L1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpn2DFI0gJJzQJJzQNJzQNJzQNJzQJJzQNJ
zQNKzQRNzgdL0AVLzgZJzQMKDQplbmRzdHJlYW0NZW5kb2JqDTE5NyAwIG9iajw8L0xlbmd0aCA2
Ny9XaWR0aCAyMi9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIv
VHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0K1+zjjJeXTVtiICgkAAIHAAAAAAAA
AAAIAAAAAAAAAAAAAAABAAACAAACAAAAAAAAAAAAAAAAAAACOURAW2dkvs7HCg0KZW5kc3RyZWFt
DWVuZG9iag0xOTggMCBvYmo8PC9MZW5ndGggMTMvV2lkdGggNC9IZWlnaHQgMS9CaXRzUGVyQ29t
cG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0
cmVhbQ0KmKLeLjevAACHWGXPCg0KZW5kc3RyZWFtDWVuZG9iag0xOTkgMCBvYmo8PC9MZW5ndGgg
MTMvV2lkdGggNC9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIv
VHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0Kw/PAbOU2Q8wAceFCCg0KZW5kc3Ry
ZWFtDWVuZG9iag0yMDAgMCBvYmo8PC9MZW5ndGggNDYvV2lkdGggMTUvSGVpZ2h0IDEvQml0c1Bl
ckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdl
Pj5zdHJlYW0NCqztoFfdI0PKAUvNBEzOBkrPA0nNA0vNBknNA0nPA0nNA0vOBkrMBE3OB0nNAwoN
CmVuZHN0cmVhbQ1lbmRvYmoNMjAxIDAgb2JqPDwvTGVuZ3RoIDU1L1dpZHRoIDE4L0hlaWdodCAx
L0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlw
ZS9JbWFnZT4+c3RyZWFtDQrV6OGXoqBiaWlBTkokLCsRFhUAAAMAAAAAAAAAAAAAAAAAAAAGCg0V
GRstNjZSYVxkcW27ycQKDQplbmRzdHJlYW0NZW5kb2JqDTIwMiAwIG9iajw8L0xlbmd0aCAxOS9X
aWR0aCA2L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBl
L1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQptb74gIasAAJAAAJMEBKN/js4KDQplbmRz
dHJlYW0NZW5kb2JqDTIwMyAwIG9iajw8L0xlbmd0aCAxMy9XaWR0aCA0L0hlaWdodCAxL0JpdHNQ
ZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFn
ZT4+c3RyZWFtDQrD88Bs5TY9ygCA5VsKDQplbmRzdHJlYW0NZW5kb2JqDTIwNCAwIG9iajw8L0xl
bmd0aCA0Ni9XaWR0aCAxNS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAx
NSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KmueAVNkYSM0CSs4ETc4G
TtEISs0EUM4KSs4ES9MDTM4HTc8ISs8ES84GSc0DCg0KZW5kc3RyZWFtDWVuZG9iag0yMDUgMCBv
Ymo8PC9MZW5ndGggNC9XaWR0aCAxL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNw
YWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQrF1OUKDQplbmRz
dHJlYW0NZW5kb2JqDTIwNiAwIG9iajw8L0xlbmd0aCAzNy9XaWR0aCAxMi9IZWlnaHQgMS9CaXRz
UGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1h
Z2U+PnN0cmVhbQ0Kw9TPnqimhYuLZ29vXG5nUmJdUWFcWmxmVF9ed3x+i5CQrLezCg0KZW5kc3Ry
ZWFtDWVuZG9iag0yMDcgMCBvYmo8PC9MZW5ndGggMjUvV2lkdGggOC9IZWlnaHQgMS9CaXRzUGVy
Q29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+
PnN0cmVhbQ0Kf4fMREvJBwmYAACNAACRDBCmQESqrsHiCg0KZW5kc3RyZWFtDWVuZG9iag0yMDgg
MCBvYmo8PC9MZW5ndGggMTMvV2lkdGggNC9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29s
b3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0Kw/PAbeU2
PMkAhedjCg0KZW5kc3RyZWFtDWVuZG9iag0yMDkgMCBvYmo8PC9MZW5ndGggNDYvV2lkdGggMTUv
SGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVj
dC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCpnnf1vcGUnNAkrNBEvOBk3NCEzOB03OB0zOBkvQBU/P
CkrNBE3RB03OCEjNAgoNCmVuZHN0cmVhbQ1lbmRvYmoNMjEwIDAgb2JqPDwvTGVuZ3RoIDEwL1dp
ZHRoIDMvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUv
WE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCrDE25S03KKu2goNCmVuZHN0cmVhbQ1lbmRv
YmoNMjExIDAgb2JqPDwvTGVuZ3RoIDEzL1dpZHRoIDQvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVu
dCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0N
CuP68dfr49bq4+T48AoNCmVuZHN0cmVhbQ1lbmRvYmoNMjEyIDAgb2JqPDwvTGVuZ3RoIDI1L1dp
ZHRoIDgvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUv
WE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCoaL0VRgxwwSmQAAjwAAkgEDly44t217yAoN
CmVuZHN0cmVhbQ1lbmRvYmoNMjEzIDAgb2JqPDwvTGVuZ3RoIDEzL1dpZHRoIDQvSGVpZ2h0IDEv
Qml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBl
L0ltYWdlPj5zdHJlYW0NCsPzwG3lNj3KAHzkVQoNCmVuZHN0cmVhbQ1lbmRvYmoNMjE0IDAgb2Jq
PDwvTGVuZ3RoIDQ2L1dpZHRoIDE1L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNw
YWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQqk65Vc4CFHywJK
zQRMzgdLzwRP0ApKzQVQzwpKzAVPzwlKzAVQzwtKzQRNzgcKDQplbmRzdHJlYW0NZW5kb2JqDTIx
NSAwIG9iajw8L0xlbmd0aCAxMy9XaWR0aCA0L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9D
b2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQq1wt+J
mdB/oOdtiMcKDQplbmRzdHJlYW0NZW5kb2JqDTIxNiAwIG9iajw8L0xlbmd0aCAzMS9XaWR0aCAx
MC9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2Jq
ZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0Klp/XdYTaPEe3CQmlAACJAACMAACXJCuzUViyrbjh
Cg0KZW5kc3RyZWFtDWVuZG9iag0yMTcgMCBvYmo8PC9MZW5ndGggMTMvV2lkdGggNC9IZWlnaHQg
MS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5
cGUvSW1hZ2U+PnN0cmVhbQ0Kw/PAaOM1OskAZt4zCg0KZW5kc3RyZWFtDWVuZG9iag0yMTggMCBv
Ymo8PC9MZW5ndGggNDMvV2lkdGggMTQvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9y
U3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCmLYLUbQAU3O
BknNBErQA0/QCkrNBUzOBk3OCE3PB0rQBUzOBknNA03OCAoNCmVuZHN0cmVhbQ1lbmRvYmoNMjE5
IDAgb2JqPDwvTGVuZ3RoIDE5L1dpZHRoIDYvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0Nv
bG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCqq223uC
yGJ51lJt0lhsyV5zyAoNCmVuZHN0cmVhbQ1lbmRvYmoNMjIwIDAgb2JqPDwvTGVuZ3RoIDM3L1dp
ZHRoIDEyL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBl
L1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQqOm9J/leFhaslCRrkXHaMAAJAAAIcAAIoA
AJwqN7tSWrOjrNwKDQplbmRzdHJlYW0NZW5kb2JqDTIyMSAwIG9iajw8L0xlbmd0aCAxNi9XaWR0
aCA1L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hP
YmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQrD88Bn4zVBywBP0wzB9LQKDQplbmRzdHJlYW0N
ZW5kb2JqDTIyMiAwIG9iajw8L0xlbmd0aCA0My9XaWR0aCAxNC9IZWlnaHQgMS9CaXRzUGVyQ29t
cG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0
cmVhbQ0Kk+N1Vd4PRssASs0ESc0DT88LSs0ER8wAS84FSc0DStAETM8GSc4DStADCg0KZW5kc3Ry
ZWFtDWVuZG9iag0yMjMgMCBvYmo8PC9MZW5ndGggNjQvV2lkdGggMjEvSGVpZ2h0IDEvQml0c1Bl
ckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdl
Pj5zdHJlYW0NCr/N5IuUzFlwxTVLwjM/wCYyth8jrSovsio0rSoxrx8kpQwRnAAAiQAAhgAAiQAA
jwwQpSIsq01ewWFwv6q34woNCmVuZHN0cmVhbQ1lbmRvYmoNMjI0IDAgb2JqPDwvTGVuZ3RoIDE2
L1dpZHRoIDUvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5
cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCsPzwG7lNkPLAEbMAIv1YwoNCmVuZHN0
cmVhbQ1lbmRvYmoNMjI1IDAgb2JqPDwvTGVuZ3RoIDQwL1dpZHRoIDEzL0hlaWdodCAxL0JpdHNQ
ZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFn
ZT4+c3RyZWFtDQqJ52pk6iZCzQBAyQBEywBCywBZ3hVO0AlJzANKzQNMzgdJzQNK0QQKDQplbmRz
dHJlYW0NZW5kb2JqDTIyNiAwIG9iajw8L0xlbmd0aCAzNC9XaWR0aCAxMS9IZWlnaHQgMS9CaXRz
UGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1h
Z2U+PnN0cmVhbQ0Ken/GZnbOS1u0O0m0NUO2LzqrMDmsNkOvQVG4WWvMX2y6Cg0KZW5kc3RyZWFt
DWVuZG9iag0yMjcgMCBvYmo8PC9MZW5ndGggMTkvV2lkdGggNi9IZWlnaHQgMS9CaXRzUGVyQ29t
cG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0
cmVhbQ0Kw/PAbeU2Q8sASc4CTtIJre2SCg0KZW5kc3RyZWFtDWVuZG9iag0yMjggMCBvYmo8PC9M
ZW5ndGggMzQvV2lkdGggMTEvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2Ug
MTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCn/gXor3ZIbyXontaKzp
kX3cU0/SDEfMAEnNA0zOB0nMAwoNCmVuZHN0cmVhbQ1lbmRvYmoNMjI5IDAgb2JqPDwvTGVuZ3Ro
IDI1L1dpZHRoIDgvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBS
L1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCsPzwG3lNkPLAEnNA0fNAGblKqLn
hdv73goNCmVuZHN0cmVhbQ1lbmRvYmoNMjMwIDAgb2JqPDwvTGVuZ3RoIDE5L1dpZHRoIDYvSGVp
Z2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9T
dWJ0eXBlL0ltYWdlPj5zdHJlYW0NCqrsnVfZFkrNA0rNBEzOB0jNAgoNCmVuZHN0cmVhbQ1lbmRv
YmoNMjMxIDAgb2JqPDwvTGVuZ3RoIDMxL1dpZHRoIDEwL0hlaWdodCAxL0JpdHNQZXJDb21wb25l
bnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFt
DQrD88Bt5TZDywBJzQNJzQNFywBa4BeE8luo6Y/G8roKDQplbmRzdHJlYW0NZW5kb2JqDTIzMiAw
IG9iajw8L0xlbmd0aCAyMi9XaWR0aCA3L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xv
clNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQqw6ply2kZP
0gpLzgVJzQNJzQNNzggKDQplbmRzdHJlYW0NZW5kb2JqDTIzMyAwIG9iajw8L0xlbmd0aCAxNDcv
RmlsdGVyL0ZsYXRlRGVjb2RlL1dpZHRoIDIxL0hlaWdodCAzL0JpdHNQZXJDb21wb25lbnQgOC9D
b2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpIiTr8
+UDuUzPn0wyeZ5khyP0Mg8Mphsh7YlnPrcrfeJa/9q1445X53CLukbzrWQb3M4ye55i9LoBU+p5j
P4ykHcj1OsfieZYJyPY+x+JwksHxFIMtmLQ/iTAfqMD7AovveXaPs0xw7V4gETavsyDtQHN8z3GA
2VAtXmeZfc6xA3VBbTnD4nOODcgGCDAAEYBNgQoNCmVuZHN0cmVhbQ1lbmRvYmoNMjM0IDAgb2Jq
PDwvTGVuZ3RoIDEzL1dpZHRoIDQvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3Bh
Y2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCs3i7LbG3rC/2sDS
6QoNCmVuZHN0cmVhbQ1lbmRvYmoNMjM1IDAgb2JqPDwvTGVuZ3RoIDY0L1dpZHRoIDIxL0hlaWdo
dCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3Vi
dHlwZS9JbWFnZT4+c3RyZWFtDQrD88Bt5TZDywBKzwNJzgJJzQNNzghNzghK0ANNzwdKzQRNzgdL
0ARJzQNJzQJJzwRNzwhNzwdK0ARMzgdJzQMKDQplbmRzdHJlYW0NZW5kb2JqDTIzNiAwIG9iajw8
L0xlbmd0aCA0L1dpZHRoIDEvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2Ug
MTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCub78goNCmVuZHN0cmVh
bQ1lbmRvYmoNMjM3IDAgb2JqPDwvTGVuZ3RoIDIyL1dpZHRoIDcvSGVpZ2h0IDEvQml0c1BlckNv
bXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5z
dHJlYW0NCsDU5W12vkdWtzdCrjI9qz5Ls15uuwoNCmVuZHN0cmVhbQ1lbmRvYmoNMjM4IDAgb2Jq
PDwvTGVuZ3RoIDY0L1dpZHRoIDIxL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNw
YWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQrD879s5TZHzABK
zQRMzgdL0AVMzwZJzQNN0QdNzghJzQNMzgZO0QhL0QRJzgJNzQhMzgdJzQJO0QhMzgdIzQIKDQpl
bmRzdHJlYW0NZW5kb2JqDTIzOSAwIG9iajw8L0xlbmd0aCAxMy9XaWR0aCA0L0hlaWdodCAxL0Jp
dHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9J
bWFnZT4+c3RyZWFtDQqHjstIVq51fMTK3ecKDQplbmRzdHJlYW0NZW5kb2JqDTI0MCAwIG9iajw8
L0xlbmd0aCAzNy9XaWR0aCAxMi9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFj
ZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KqbzYPUuzCQyXAACB
AACBAACAAAB5KDGmrtPaqrnYU1uxWmm6Cg0KZW5kc3RyZWFtDWVuZG9iag0yNDEgMCBvYmo8PC9M
ZW5ndGggNjQvV2lkdGggMjEvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2Ug
MTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCsPzwG3lNkbMAEnNA0vN
Bk/RCErNBEzOB03OB0rQBE3PCEnNA0/PCkvPBU3PCEzNB0nNAk3OCEzOBkrQBE7OCQoNCmVuZHN0
cmVhbQ1lbmRvYmoNMjQyIDAgb2JqPDwvTGVuZ3RoIDE2L1dpZHRoIDUvSGVpZ2h0IDEvQml0c1Bl
ckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdl
Pj5zdHJlYW0NCqOw1RgengAAjREWo1ptuAoNCmVuZHN0cmVhbQ1lbmRvYmoNMjQzIDAgb2JqPDwv
TGVuZ3RoIDQzL1dpZHRoIDE0L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNl
IDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQq/1uE4RbAAAIQAAIUM
DpRRY7lpf8NeccNte7vC0+M+S7YAAI4CAo5LVbQKDQplbmRzdHJlYW0NZW5kb2JqDTI0NCAwIG9i
ajw8L0xlbmd0aCA2NC9XaWR0aCAyMS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JT
cGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0Kw/PAbeU2Q8sA
Tc4HSs0ETs4JS80FTs8JS80FTNAHTc4HTc4ITM4GTc4ITM4HSc0DTc4HTM4HTc8HSs8ETM4GCg0K
ZW5kc3RyZWFtDWVuZG9iag0yNDUgMCBvYmo8PC9MZW5ndGggMTYvV2lkdGggNS9IZWlnaHQgMS9C
aXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUv
SW1hZ2U+PnN0cmVhbQ0KWW20BwiTBQeSAgOQLDKhCg0KZW5kc3RyZWFtDWVuZG9iag0yNDYgMCBv
Ymo8PC9MZW5ndGggMTYvV2lkdGggNS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JT
cGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KcYjKAACKAACG
ISiigpnGCg0KZW5kc3RyZWFtDWVuZG9iag0yNDcgMCBvYmo8PC9MZW5ndGggMTYvV2lkdGggNS9I
ZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0
L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KAgOVAwSMAACHND+0qL3YCg0KZW5kc3RyZWFtDWVuZG9i
ag0yNDggMCBvYmo8PC9MZW5ndGggNjQvV2lkdGggMjEvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVu
dCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0N
CsPzwG3lNkPLAEvOBUrRBE/PCkvNBU7PCUvNBU/PCkrNBEvOBU3OCEzOBkjNAkjNA1DPC0rNBU/P
CkrNBE3OCAoNCmVuZHN0cmVhbQ1lbmRvYmoNMjQ5IDAgb2JqPDwvTGVuZ3RoIDE2L1dpZHRoIDUv
SGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVj
dC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCo+syh4knQAAhQIDkGV2ugoNCmVuZHN0cmVhbQ1lbmRv
YmoNMjUwIDAgb2JqPDwvTGVuZ3RoIDEzL1dpZHRoIDQvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVu
dCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0N
CiMrnQAAiAwPlGNwvwoNCmVuZHN0cmVhbQ1lbmRvYmoNMjUxIDAgb2JqPDwvTGVuZ3RoIDEzL1dp
ZHRoIDQvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUv
WE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCjtItAAAggMFmFBYsgoNCmVuZHN0cmVhbQ1l
bmRvYmoNMjUyIDAgb2JqPDwvTGVuZ3RoIDY0L1dpZHRoIDIxL0hlaWdodCAxL0JpdHNQZXJDb21w
b25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3Ry
ZWFtDQrD88Bt5TZDywBNzgdL0AVOzwlLzQVLzgVOzghMzgZMzghJzQRQzwtOzghOzghOzglLzgZJ
zQRPzwpKzQRMzgYKDQplbmRzdHJlYW0NZW5kb2JqDTI1MyAwIG9iajw8L0xlbmd0aCA3L1dpZHRo
IDIvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9i
amVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCmqBvXqWxgoNCmVuZHN0cmVhbQ1lbmRvYmoNMjU0
IDAgb2JqPDwvTGVuZ3RoIDE2L1dpZHRoIDUvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0Nv
bG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCqnB2wYI
lQAAhiAmoKC21AoNCmVuZHN0cmVhbQ1lbmRvYmoNMjU1IDAgb2JqPDwvTGVuZ3RoIDEwL1dpZHRo
IDMvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9i
amVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCrnI4YOg2XuMxgoNCmVuZHN0cmVhbQ1lbmRvYmoN
MjU2IDAgb2JqPDwvTGVuZ3RoIDY0L1dpZHRoIDIxL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQg
OC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQrD
88Bt5TZDywBLzgVJzQRPzwlLzQVIzQJQzwtLzQVPzwlJzQNIzQBHzQBGzABHzABIzQJJzQNMzgZO
zghIzQIKDQplbmRzdHJlYW0NZW5kb2JqDTI1NyAwIG9iajw8L0xlbmd0aCAxNi9XaWR0aCA1L0hl
aWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3Qv
U3VidHlwZS9JbWFnZT4+c3RyZWFtDQqPr9UBAY8AAIMrNaa72+AKDQplbmRzdHJlYW0NZW5kb2Jq
DTI1OCAwIG9iajw8L0xlbmd0aCA2NC9XaWR0aCAyMS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50
IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0K
w/PAbeU2Q8sATc4HTNEFS84FSc0DTc4ITM4GRswARcwAWNsYcuZBh+1kk/B4dt1OTc4ITM4FSs0E
S84FSc0DCg0KZW5kc3RyZWFtDWVuZG9iag0yNTkgMCBvYmo8PC9MZW5ndGggMTMvV2lkdGggNC9I
ZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0
L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0Kg5/HAgKLAACOMDSpCg0KZW5kc3RyZWFtDWVuZG9iag0y
NjAgMCBvYmo8PC9MZW5ndGggMzQvV2lkdGggMTEvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4
L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCsPz
wG3lNkPLAEvNBUrPBEnNA03OCEvOBUPLAGzjNpjygQoNCmVuZHN0cmVhbQ1lbmRvYmoNMjYxIDAg
b2JqPDwvTGVuZ3RoIDE5L1dpZHRoIDYvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9y
U3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCrTysFfWF0jN
AkrNBE3OCEnNAwoNCmVuZHN0cmVhbQ1lbmRvYmoNMjYyIDAgb2JqPDwvTGVuZ3RoIDEzL1dpZHRo
IDQvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9i
amVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCsDW4bXL37nP4tHo6QoNCmVuZHN0cmVhbQ1lbmRv
YmoNMjYzIDAgb2JqPDwvTGVuZ3RoIDM0L1dpZHRoIDExL0hlaWdodCAxL0JpdHNQZXJDb21wb25l
bnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFt
DQq1ytyxyN1hd7gBAYkAAIodIZmoudayyNysv9u3zebN4OkKDQplbmRzdHJlYW0NZW5kb2JqDTI2
NCAwIG9iajw8L0xlbmd0aCAxMC9XaWR0aCAzL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9D
b2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQrL5uyx
xdu80+cKDQplbmRzdHJlYW0NZW5kb2JqDTI2NSAwIG9iajw8L0xlbmd0aCAxMC9XaWR0aCAzL0hl
aWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3Qv
U3VidHlwZS9JbWFnZT4+c3RyZWFtDQrM5e2vwtrF3usKDQplbmRzdHJlYW0NZW5kb2JqDTI2NiAw
IG9iajw8L0xlbmd0aCAxOS9XaWR0aCA2L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xv
clNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQq81OiIlcp4
gsVwfcKEksm/2eoKDQplbmRzdHJlYW0NZW5kb2JqDTI2NyAwIG9iajw8L0xlbmd0aCAyOC9XaWR0
aCA5L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hP
YmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQrD88Bt5TZDywBNzgdKzQRIzQJKzgJX2hKU8XkK
DQplbmRzdHJlYW0NZW5kb2JqDTI2OCAwIG9iajw8L0xlbmd0aCAyNS9XaWR0aCA4L0hlaWdodCAx
L0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlw
ZS9JbWFnZT4+c3RyZWFtDQrZ+dvQ/M2W54JR0hBLzQVKzQRLzgZJzQMKDQplbmRzdHJlYW0NZW5k
b2JqDTI2OSAwIG9iajw8L0xlbmd0aCAxMy9XaWR0aCA0L0hlaWdodCAxL0JpdHNQZXJDb21wb25l
bnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFt
DQoxO58wOqk7SKiEnsYKDQplbmRzdHJlYW0NZW5kb2JqDTI3MCAwIG9iajw8L0xlbmd0aCAzNC9X
aWR0aCAxMS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlw
ZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KNkGrLDaoEhaRAACLAQKPBgiNKDCkLjio
KzSmPUu6eo3GCg0KZW5kc3RyZWFtDWVuZG9iag0yNzEgMCBvYmo8PC9MZW5ndGggMTMvV2lkdGgg
NC9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2Jq
ZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KfZbULjilMz20anG6Cg0KZW5kc3RyZWFtDWVuZG9i
ag0yNzIgMCBvYmo8PC9MZW5ndGggMTMvV2lkdGggNC9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50
IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0K
eJDULTajRFO+l6HPCg0KZW5kc3RyZWFtDWVuZG9iag0yNzMgMCBvYmo8PC9MZW5ndGggMjUvV2lk
dGggOC9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9Y
T2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KWWW+Mj2rGyGgFBidEBacGiCfNUCsYGzACg0K
ZW5kc3RyZWFtDWVuZG9iag0yNzQgMCBvYmo8PC9MZW5ndGggMjIvV2lkdGggNy9IZWlnaHQgMS9C
aXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUv
SW1hZ2U+PnN0cmVhbQ0Kw/PAbeU2Q8sAS84FSs0ESM4AXN0aCg0KZW5kc3RyZWFtDWVuZG9iag0y
NzUgMCBvYmo8PC9MZW5ndGggMzQvV2lkdGggMTEvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4
L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCtz6
4avvkYjeXGndNmflN1XSGEnNBEvNBUnNA0nOAkvSBAoNCmVuZHN0cmVhbQ1lbmRvYmoNMjc2IDAg
b2JqPDwvTGVuZ3RoIDEzL1dpZHRoIDQvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9y
U3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NChYYlgAAhwYH
i3uQwwoNCmVuZHN0cmVhbQ1lbmRvYmoNMjc3IDAgb2JqPDwvTGVuZ3RoIDM0L1dpZHRoIDExL0hl
aWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3Qv
U3VidHlwZS9JbWFnZT4+c3RyZWFtDQoFB48AAIYAAIQAAIoAAYwAAIgAAIQAAIMAAIEDBZVjcLwK
DQplbmRzdHJlYW0NZW5kb2JqDTI3OCAwIG9iajw8L0xlbmd0aCAxMy9XaWR0aCA0L0hlaWdodCAx
L0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlw
ZS9JbWFnZT4+c3RyZWFtDQpWabkAAIEAAJFWVrMKDQplbmRzdHJlYW0NZW5kb2JqDTI3OSAwIG9i
ajw8L0xlbmd0aCAxMC9XaWR0aCAzL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNw
YWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpabb0AAH4OEp4K
DQplbmRzdHJlYW0NZW5kb2JqDTI4MCAwIG9iajw8L0xlbmd0aCAzNC9XaWR0aCAxMS9IZWlnaHQg
MS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5
cGUvSW1hZ2U+PnN0cmVhbQ0KNDqsBgaUAAB/AACOBQeTAACIAACFAACDCwyXMjWhrcPgCg0KZW5k
c3RyZWFtDWVuZG9iag0yODEgMCBvYmo8PC9MZW5ndGggMTkvV2lkdGggNi9IZWlnaHQgMS9CaXRz
UGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1h
Z2U+PnN0cmVhbQ0Kw/PAbeU2Q8sASc0DSc4CUtQNCg0KZW5kc3RyZWFtDWVuZG9iag0yODIgMCBv
Ymo8PC9MZW5ndGggMzcvV2lkdGggMTIvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9y
U3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCrftpnPkRVff
H1HaCkTMAD/JAEXLAEnNA0nNA07PCErNBErPAwoNCmVuZHN0cmVhbQ1lbmRvYmoNMjgzIDAgb2Jq
PDwvTGVuZ3RoIDEzL1dpZHRoIDQvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3Bh
Y2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCiAlnAAAjA8SlYOa
xgoNCmVuZHN0cmVhbQ1lbmRvYmoNMjg0IDAgb2JqPDwvTGVuZ3RoIDM0L1dpZHRoIDExL0hlaWdo
dCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3Vi
dHlwZS9JbWFnZT4+c3RyZWFtDQp8mMh4kck/TaYAAIoAAI0QFJJnfb56lMh0jcOGpNWqxdoKDQpl
bmRzdHJlYW0NZW5kb2JqDTI4NSAwIG9iajw8L0xlbmd0aCAxMy9XaWR0aCA0L0hlaWdodCAxL0Jp
dHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9J
bWFnZT4+c3RyZWFtDQpccbwAAIUHCphjZroKDQplbmRzdHJlYW0NZW5kb2JqDTI4NiAwIG9iajw8
L0xlbmd0aCA0OS9XaWR0aCAxNi9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFj
ZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KZnvCAACDDxKUSVWy
Nj2fAACIJi+ggJ7Uq7narbvaj63ZPkysBAWOAACLAACRPUu6Cg0KZW5kc3RyZWFtDWVuZG9iag0y
ODcgMCBvYmo8PC9MZW5ndGggMTkvV2lkdGggNi9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgv
Q29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0Kw/PA
beU2Q8sASM0CRs4Aj+9vCg0KZW5kc3RyZWFtDWVuZG9iag0yODggMCBvYmo8PC9MZW5ndGggNDAv
V2lkdGggMTMvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5
cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCrLtn13cKkXPAEHKAEfMAUrRBErOA0nN
A0nNA0nNA0zOBk7OCUnNAwoNCmVuZHN0cmVhbQ1lbmRvYmoNMjg5IDAgb2JqPDwvTGVuZ3RoIDEz
L1dpZHRoIDQvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5
cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCh4imwAAjA4RlICUxAoNCmVuZHN0cmVh
bQ1lbmRvYmoNMjkwIDAgb2JqPDwvTGVuZ3RoIDEzL1dpZHRoIDQvSGVpZ2h0IDEvQml0c1BlckNv
bXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5z
dHJlYW0NCnyXxAICjQAAmCssnAoNCmVuZHN0cmVhbQ1lbmRvYmoNMjkxIDAgb2JqPDwvTGVuZ3Ro
IDEzL1dpZHRoIDQvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBS
L1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NClxxvAAAhQYHl2BjuQoNCmVuZHN0
cmVhbQ1lbmRvYmoNMjkyIDAgb2JqPDwvTGVuZ3RoIDIyL1dpZHRoIDcvSGVpZ2h0IDEvQml0c1Bl
ckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdl
Pj5zdHJlYW0NCmd+xAAAgwICiQkNkgMFj1psu7/U4goNCmVuZHN0cmVhbQ1lbmRvYmoNMjkzIDAg
b2JqPDwvTGVuZ3RoIDE2L1dpZHRoIDUvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9y
U3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCm12vxQaogIE
jQAAjWJwvgoNCmVuZHN0cmVhbQ1lbmRvYmoNMjk0IDAgb2JqPDwvTGVuZ3RoIDE2L1dpZHRoIDUv
SGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVj
dC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCsPzwG3lNkPLAEnOAVzZIAoNCmVuZHN0cmVhbQ1lbmRv
YmoNMjk1IDAgb2JqPDwvTGVuZ3RoIDQzL1dpZHRoIDE0L0hlaWdodCAxL0JpdHNQZXJDb21wb25l
bnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFt
DQrC8blo4DBF0QBGzQBJzgFJzgFK0AJJzQJOzwhKzQROzwhKzQNLzgVJzQMKDQplbmRzdHJlYW0N
ZW5kb2JqDTI5NiAwIG9iajw8L0xlbmd0aCAxMy9XaWR0aCA0L0hlaWdodCAxL0JpdHNQZXJDb21w
b25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3Ry
ZWFtDQoeIpsAAIwPEpSBl8UKDQplbmRzdHJlYW0NZW5kb2JqDTI5NyAwIG9iajw8L0xlbmd0aCAx
Ni9XaWR0aCA1L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9U
eXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQqAnMQCAo0AAIkuNaTa8O0KDQplbmRz
dHJlYW0NZW5kb2JqDTI5OCAwIG9iajw8L0xlbmd0aCAxMy9XaWR0aCA0L0hlaWdodCAxL0JpdHNQ
ZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFn
ZT4+c3RyZWFtDQpccbwAAIUGCZhiZbkKDQplbmRzdHJlYW0NZW5kb2JqDTI5OSAwIG9iajw8L0xl
bmd0aCAxOS9XaWR0aCA2L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1
IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpof8UAAIIAAI0AAIxLW7nK
4uoKDQplbmRzdHJlYW0NZW5kb2JqDTMwMCAwIG9iajw8L0xlbmd0aCAxMy9XaWR0aCA0L0hlaWdo
dCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3Vi
dHlwZS9JbWFnZT4+c3RyZWFtDQpgZbsGCZcAAIcfKKoKDQplbmRzdHJlYW0NZW5kb2JqDTMwMSAw
IG9iajw8L0xlbmd0aCAxNi9XaWR0aCA1L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xv
clNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQrD88Bt5TZD
ywBHzQCT8HYKDQplbmRzdHJlYW0NZW5kb2JqDTMwMiAwIG9iajw8L0xlbmd0aCA0My9XaWR0aCAx
NC9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2Jq
ZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KettOSNkEUdMPZtswbd07at02WdcZQcsASMwCTs8J
TM4HTs4JSc4DS9IECg0KZW5kc3RyZWFtDWVuZG9iag0zMDMgMCBvYmo8PC9MZW5ndGggMTMvV2lk
dGggNC9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9Y
T2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KHiKbAACMDhGUgJXFCg0KZW5kc3RyZWFtDWVu
ZG9iag0zMDQgMCBvYmo8PC9MZW5ndGggMTYvV2lkdGggNS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9u
ZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVh
bQ0KfZfCAgOOAACLLTenw+PiCg0KZW5kc3RyZWFtDWVuZG9iag0zMDUgMCBvYmo8PC9MZW5ndGgg
MTMvV2lkdGggNC9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIv
VHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KXHG8AACFBgeXYGO4Cg0KZW5kc3Ry
ZWFtDWVuZG9iag0zMDYgMCBvYmo8PC9MZW5ndGggMTYvV2lkdGggNS9IZWlnaHQgMS9CaXRzUGVy
Q29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+
PnN0cmVhbQ0KboXGAACDAACIHyajnKrVCg0KZW5kc3RyZWFtDWVuZG9iag0zMDcgMCBvYmo8PC9M
ZW5ndGggMTYvV2lkdGggNS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAx
NSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KqbbYKzSoAACLAACMe43K
Cg0KZW5kc3RyZWFtDWVuZG9iag0zMDggMCBvYmo8PC9MZW5ndGggMTMvV2lkdGggNC9IZWlnaHQg
MS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5
cGUvSW1hZ2U+PnN0cmVhbQ0KxvTEZ+M2QMoAVNUQCg0KZW5kc3RyZWFtDWVuZG9iag0zMDkgMCBv
Ymo8PC9MZW5ndGggMTAvV2lkdGggMy9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JT
cGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0Kv/G0Yd4rh+hr
Cg0KZW5kc3RyZWFtDWVuZG9iag0zMTAgMCBvYmo8PC9MZW5ndGggMjIvV2lkdGggNy9IZWlnaHQg
MS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5
cGUvSW1hZ2U+PnN0cmVhbQ0KieJuV9kUSMwBSc0DS80FSc0DSs8DCg0KZW5kc3RyZWFtDWVuZG9i
ag0zMTEgMCBvYmo8PC9MZW5ndGggMTMvV2lkdGggNC9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50
IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0K
HiKbAACMDhGUf5PECg0KZW5kc3RyZWFtDWVuZG9iag0zMTIgMCBvYmo8PC9MZW5ndGggMTYvV2lk
dGggNS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9Y
T2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KfZjCAgKMAACJLDasxuTjCg0KZW5kc3RyZWFt
DWVuZG9iag0zMTMgMCBvYmo8PC9MZW5ndGggMTMvV2lkdGggNC9IZWlnaHQgMS9CaXRzUGVyQ29t
cG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0
cmVhbQ0KXHG8AACFBwmYYma6Cg0KZW5kc3RyZWFtDWVuZG9iag0zMTQgMCBvYmo8PC9MZW5ndGgg
MTYvV2lkdGggNS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIv
VHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KbIPEAACIAACLRFGzx9bkCg0KZW5k
c3RyZWFtDWVuZG9iag0zMTUgMCBvYmo8PC9MZW5ndGggMTYvV2lkdGggNS9IZWlnaHQgMS9CaXRz
UGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1h
Z2U+PnN0cmVhbQ0K2fHtUmK6AACFAACGWm7CCg0KZW5kc3RyZWFtDWVuZG9iag0zMTYgMCBvYmo8
PC9MZW5ndGggMTMvV2lkdGggNC9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFj
ZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KxPPBauQ2QcwAZt0v
Cg0KZW5kc3RyZWFtDWVuZG9iag0zMTcgMCBvYmo8PC9MZW5ndGggNC9XaWR0aCAxL0hlaWdodCAx
L0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlw
ZS9JbWFnZT4+c3RyZWFtDQqm7JcKDQplbmRzdHJlYW0NZW5kb2JqDTMxOCAwIG9iajw8L0xlbmd0
aCA0L1dpZHRoIDEvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBS
L1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCt385goNCmVuZHN0cmVhbQ1lbmRv
YmoNMzE5IDAgb2JqPDwvTGVuZ3RoIDE5L1dpZHRoIDYvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVu
dCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0N
Cqrwn1vZH0bMAEnNA07PCUnNAwoNCmVuZHN0cmVhbQ1lbmRvYmoNMzIwIDAgb2JqPDwvTGVuZ3Ro
IDEzL1dpZHRoIDQvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBS
L1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NClxxvAAAhQUHl2BiuAoNCmVuZHN0
cmVhbQ1lbmRvYmoNMzIxIDAgb2JqPDwvTGVuZ3RoIDE2L1dpZHRoIDUvSGVpZ2h0IDEvQml0c1Bl
ckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdl
Pj5zdHJlYW0NCn2YwgICjAAAhCs0psbk4woNCmVuZHN0cmVhbQ1lbmRvYmoNMzIyIDAgb2JqPDwv
TGVuZ3RoIDE2L1dpZHRoIDUvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2Ug
MTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCm+GxQAAhAAAhVVmu9rv
7goNCmVuZHN0cmVhbQ1lbmRvYmoNMzIzIDAgb2JqPDwvTGVuZ3RoIDEzL1dpZHRoIDQvSGVpZ2h0
IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0
eXBlL0ltYWdlPj5zdHJlYW0NCnN7wQsNlgAAhTpJsQoNCmVuZHN0cmVhbQ1lbmRvYmoNMzI0IDAg
b2JqPDwvTGVuZ3RoIDEzL1dpZHRoIDQvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9y
U3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCsPzwGXiND7K
AH7mVwoNCmVuZHN0cmVhbQ1lbmRvYmoNMzI1IDAgb2JqPDwvTGVuZ3RoIDE2L1dpZHRoIDUvSGVp
Z2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9T
dWJ0eXBlL0ltYWdlPj5zdHJlYW0NCq7ql33jTWDXKGvaMYjfYgoNCmVuZHN0cmVhbQ1lbmRvYmoN
MzI2IDAgb2JqPDwvTGVuZ3RoIDE2L1dpZHRoIDUvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4
L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCp7r
jFLVEEfMAErNBUnNAwoNCmVuZHN0cmVhbQ1lbmRvYmoNMzI3IDAgb2JqPDwvTGVuZ3RoIDEzL1dp
ZHRoIDQvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUv
WE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCh4imwAAjA8SlIGYxgoNCmVuZHN0cmVhbQ1l
bmRvYmoNMzI4IDAgb2JqPDwvTGVuZ3RoIDE2L1dpZHRoIDUvSGVpZ2h0IDEvQml0c1BlckNvbXBv
bmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJl
YW0NCn2XwgIDjgAAjCs0o8bk4woNCmVuZHN0cmVhbQ1lbmRvYmoNMzI5IDAgb2JqPDwvTGVuZ3Ro
IDEzL1dpZHRoIDQvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBS
L1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NClxxvAAAhQUGl19huAoNCmVuZHN0
cmVhbQ1lbmRvYmoNMzMwIDAgb2JqPDwvTGVuZ3RoIDE2L1dpZHRoIDUvSGVpZ2h0IDEvQml0c1Bl
ckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdl
Pj5zdHJlYW0NCmqBxQAAgwAAglpvv+D58goNCmVuZHN0cmVhbQ1lbmRvYmoNMzMxIDAgb2JqPDwv
TGVuZ3RoIDEzL1dpZHRoIDQvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2Ug
MTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCn2CxBAUnQAAhTI8rgoN
CmVuZHN0cmVhbQ1lbmRvYmoNMzMyIDAgb2JqPDwvTGVuZ3RoIDEzL1dpZHRoIDQvSGVpZ2h0IDEv
Qml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBl
L0ltYWdlPj5zdHJlYW0NCsPzwGvkNjjHAIfoawoNCmVuZHN0cmVhbQ1lbmRvYmoNMzMzIDAgb2Jq
PDwvTGVuZ3RoIDIyL1dpZHRoIDcvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3Bh
Y2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCpTib1LYF07aCEXN
AErWAU3YDnXZSAoNCmVuZHN0cmVhbQ1lbmRvYmoNMzM0IDAgb2JqPDwvTGVuZ3RoIDEzL1dpZHRo
IDQvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9i
amVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCm7aPEzSBkjNAknNAwoNCmVuZHN0cmVhbQ1lbmRv
YmoNMzM1IDAgb2JqPDwvTGVuZ3RoIDEzL1dpZHRoIDQvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVu
dCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0N
ClxxuwAAiQYIn15htwoNCmVuZHN0cmVhbQ1lbmRvYmoNMzM2IDAgb2JqPDwvTGVuZ3RoIDE2L1dp
ZHRoIDUvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUv
WE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCn2XwgIDjgAAjis0pMbk4woNCmVuZHN0cmVh
bQ1lbmRvYmoNMzM3IDAgb2JqPDwvTGVuZ3RoIDE2L1dpZHRoIDUvSGVpZ2h0IDEvQml0c1BlckNv
bXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5z
dHJlYW0NCm6FxgAAgwAAg1dqvdzz7woNCmVuZHN0cmVhbQ1lbmRvYmoNMzM4IDAgb2JqPDwvTGVu
Z3RoIDEzL1dpZHRoIDQvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUg
MCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCnyCxBAUnAAAhTI7rgoNCmVu
ZHN0cmVhbQ1lbmRvYmoNMzM5IDAgb2JqPDwvTGVuZ3RoIDEzL1dpZHRoIDQvSGVpZ2h0IDEvQml0
c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0lt
YWdlPj5zdHJlYW0NCsPzwG3lNj7KAJPsewoNCmVuZHN0cmVhbQ1lbmRvYmoNMzQwIDAgb2JqPDwv
TGVuZ3RoIDI4L1dpZHRoIDkvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2Ug
MTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCq7rmlTZG0fQAknNA0nN
A0nNA0nOBEvWDZzmhAoNCmVuZHN0cmVhbQ1lbmRvYmoNMzQxIDAgb2JqPDwvTGVuZ3RoIDEzL1dp
ZHRoIDQvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUv
WE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCpHjdVLVDkfMAEnNAwoNCmVuZHN0cmVhbQ1l
bmRvYmoNMzQyIDAgb2JqPDwvTGVuZ3RoIDEzL1dpZHRoIDQvSGVpZ2h0IDEvQml0c1BlckNvbXBv
bmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJl
YW0NClxxvAAAhgcKmmJmuQoNCmVuZHN0cmVhbQ1lbmRvYmoNMzQzIDAgb2JqPDwvTGVuZ3RoIDE2
L1dpZHRoIDUvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5
cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCn2YwgICjAAAhis0pMbk4woNCmVuZHN0
cmVhbQ1lbmRvYmoNMzQ0IDAgb2JqPDwvTGVuZ3RoIDE2L1dpZHRoIDUvSGVpZ2h0IDEvQml0c1Bl
ckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdl
Pj5zdHJlYW0NCmyDxAAAiAAAilZou9vx7goNCmVuZHN0cmVhbQ1lbmRvYmoNMzQ1IDAgb2JqPDwv
TGVuZ3RoIDEzL1dpZHRoIDQvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2Ug
MTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCnR5wgoMmgAAhTxHsgoN
CmVuZHN0cmVhbQ1lbmRvYmoNMzQ2IDAgb2JqPDwvTGVuZ3RoIDEzL1dpZHRoIDQvSGVpZ2h0IDEv
Qml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBl
L0ltYWdlPj5zdHJlYW0NCsPzwGzlNkHLAJHsdgoNCmVuZHN0cmVhbQ1lbmRvYmoNMzQ3IDAgb2Jq
PDwvTGVuZ3RoIDI4L1dpZHRoIDkvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3Bh
Y2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCoPeWFPbD0jNAUrN
BEnNA0nNA0nNA0rRBWzYPAoNCmVuZHN0cmVhbQ1lbmRvYmoNMzQ4IDAgb2JqPDwvTGVuZ3RoIDEz
L1dpZHRoIDQvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5
cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCqjsnFXWE0bMAEnNAwoNCmVuZHN0cmVh
bQ1lbmRvYmoNMzQ5IDAgb2JqPDwvTGVuZ3RoIDEzL1dpZHRoIDQvSGVpZ2h0IDEvQml0c1BlckNv
bXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5z
dHJlYW0NCiInnQAAjA4RlH+TxAoNCmVuZHN0cmVhbQ1lbmRvYmoNMzUwIDAgb2JqPDwvTGVuZ3Ro
IDE2L1dpZHRoIDUvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBS
L1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCn2XwgIDjgAAjCs0pMbk4woNCmVu
ZHN0cmVhbQ1lbmRvYmoNMzUxIDAgb2JqPDwvTGVuZ3RoIDE2L1dpZHRoIDUvSGVpZ2h0IDEvQml0
c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0lt
YWdlPj5zdHJlYW0NCuX68llouwEBhwAAhVRlvAoNCmVuZHN0cmVhbQ1lbmRvYmoNMzUyIDAgb2Jq
PDwvTGVuZ3RoIDE2L1dpZHRoIDUvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3Bh
Y2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCm+GxgAAhAAAhVFj
u9br7QoNCmVuZHN0cmVhbQ1lbmRvYmoNMzUzIDAgb2JqPDwvTGVuZ3RoIDEzL1dpZHRoIDQvSGVp
Z2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9T
dWJ0eXBlL0ltYWdlPj5zdHJlYW0NCsPzwGXiND7KAIvqbQoNCmVuZHN0cmVhbQ1lbmRvYmoNMzU0
IDAgb2JqPDwvTGVuZ3RoIDI4L1dpZHRoIDkvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0Nv
bG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCobfXVTa
D0fMAE7PCUzRBUnOA0jNAkzRBWXVLAoNCmVuZHN0cmVhbQ1lbmRvYmoNMzU1IDAgb2JqPDwvTGVu
Z3RoIDEzL1dpZHRoIDQvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUg
MCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCq7uplXWE0bMAEnNAwoNCmVu
ZHN0cmVhbQ1lbmRvYmoNMzU2IDAgb2JqPDwvTGVuZ3RoIDEzL1dpZHRoIDQvSGVpZ2h0IDEvQml0
c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0lt
YWdlPj5zdHJlYW0NCh8jmwAAjA8SlIKYxgoNCmVuZHN0cmVhbQ1lbmRvYmoNMzU3IDAgb2JqPDwv
TGVuZ3RoIDE2L1dpZHRoIDUvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2Ug
MTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCn2XwgIDjgAAjys0pMbk
4woNCmVuZHN0cmVhbQ1lbmRvYmoNMzU4IDAgb2JqPDwvTGVuZ3RoIDE2L1dpZHRoIDUvSGVpZ2h0
IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0
eXBlL0ltYWdlPj5zdHJlYW0NCr/S4kBOswAAigAAiHOKxQoNCmVuZHN0cmVhbQ1lbmRvYmoNMzU5
IDAgb2JqPDwvTGVuZ3RoIDE2L1dpZHRoIDUvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0Nv
bG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCmyDxAAA
iAAAiztJsL3M4QoNCmVuZHN0cmVhbQ1lbmRvYmoNMzYwIDAgb2JqPDwvTGVuZ3RoIDEzL1dpZHRo
IDQvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9i
amVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCsPzwGrkNUHMAHrlTwoNCmVuZHN0cmVhbQ1lbmRv
YmoNMzYxIDAgb2JqPDwvTGVuZ3RoIDI4L1dpZHRoIDkvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVu
dCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0N
CpfmfFndGEbMAErNBEnOA0nNA03PCE3SBmXVLQoNCmVuZHN0cmVhbQ1lbmRvYmoNMzYyIDAgb2Jq
PDwvTGVuZ3RoIDEzL1dpZHRoIDQvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3Bh
Y2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCqvtoFXWE0bMAEnN
AwoNCmVuZHN0cmVhbQ1lbmRvYmoNMzYzIDAgb2JqPDwvTGVuZ3RoIDEzL1dpZHRoIDQvSGVpZ2h0
IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0
eXBlL0ltYWdlPj5zdHJlYW0NCh4imwAAjA4RlH+UxAoNCmVuZHN0cmVhbQ1lbmRvYmoNMzY0IDAg
b2JqPDwvTGVuZ3RoIDE2L1dpZHRoIDUvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9y
U3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCn2XwgIDjgAA
jSs0pMbk4woNCmVuZHN0cmVhbQ1lbmRvYmoNMzY1IDAgb2JqPDwvTGVuZ3RoIDEzL1dpZHRoIDQv
SGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVj
dC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCoSLyBQYnQAAhxgeoAoNCmVuZHN0cmVhbQ1lbmRvYmoN
MzY2IDAgb2JqPDwvTGVuZ3RoIDE2L1dpZHRoIDUvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4
L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCmqB
xAAAiQUHjxIWnIqQywoNCmVuZHN0cmVhbQ1lbmRvYmoNMzY3IDAgb2JqPDwvTGVuZ3RoIDEzL1dp
ZHRoIDQvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUv
WE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCsPzwGXiNEDKAGHbJQoNCmVuZHN0cmVhbQ1l
bmRvYmoNMzY4IDAgb2JqPDwvTGVuZ3RoIDI4L1dpZHRoIDkvSGVpZ2h0IDEvQml0c1BlckNvbXBv
bmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJl
YW0NCrjxsFnaI0fMAErOBEnNA0nNA0nNAkzSBn7fWwoNCmVuZHN0cmVhbQ1lbmRvYmoNMzY5IDAg
b2JqPDwvTGVuZ3RoIDEzL1dpZHRoIDQvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9y
U3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCpPkelLVD0fM
AEnNAwoNCmVuZHN0cmVhbQ1lbmRvYmoNMzcwIDAgb2JqPDwvTGVuZ3RoIDE2L1dpZHRoIDUvSGVp
Z2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9T
dWJ0eXBlL0ltYWdlPj5zdHJlYW0NCqax1y01pwAAjwECjFZmuwoNCmVuZHN0cmVhbQ1lbmRvYmoN
MzcxIDAgb2JqPDwvTGVuZ3RoIDE2L1dpZHRoIDUvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4
L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCn2Y
wgICjAAAhSs0pMbk4woNCmVuZHN0cmVhbQ1lbmRvYmoNMzcyIDAgb2JqPDwvTGVuZ3RoIDE2L1dp
ZHRoIDUvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUv
WE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCmuDxQAAhAEBigAAhzA4qQoNCmVuZHN0cmVh
bQ1lbmRvYmoNMzczIDAgb2JqPDwvTGVuZ3RoIDE2L1dpZHRoIDUvSGVpZ2h0IDEvQml0c1BlckNv
bXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5z
dHJlYW0NCsPzwGzkNkLLAEjOAqfymAoNCmVuZHN0cmVhbQ1lbmRvYmoNMzc0IDAgb2JqPDwvTGVu
Z3RoIDI1L1dpZHRoIDgvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUg
MCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCn3cUVXdDkfNAEzOB03OCEbN
AFPXEavvpAoNCmVuZHN0cmVhbQ1lbmRvYmoNMzc1IDAgb2JqPDwvTGVuZ3RoIDEzL1dpZHRoIDQv
SGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVj
dC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCm/YPE7UB0jNAknNAwoNCmVuZHN0cmVhbQ1lbmRvYmoN
Mzc2IDAgb2JqPDwvTGVuZ3RoIDEzL1dpZHRoIDQvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4
L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCh8j
mwAAjA4RlH+UxAoNCmVuZHN0cmVhbQ1lbmRvYmoNMzc3IDAgb2JqPDwvTGVuZ3RoIDIyL1dpZHRo
IDcvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9i
amVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCm+GxgAAgwAAiQEBiQUGjRwimYah1AoNCmVuZHN0
cmVhbQ1lbmRvYmoNMzc4IDAgb2JqPDwvTGVuZ3RoIDEzL1dpZHRoIDQvSGVpZ2h0IDEvQml0c1Bl
ckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdl
Pj5zdHJlYW0NClxxuwAAigYIn19itwoNCmVuZHN0cmVhbQ1lbmRvYmoNMzc5IDAgb2JqPDwvTGVu
Z3RoIDE5L1dpZHRoIDYvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUg
MCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCtPk6oKb0hkgmAcIkgMEjiEn
pAoNCmVuZHN0cmVhbQ1lbmRvYmoNMzgwIDAgb2JqPDwvTGVuZ3RoIDE2L1dpZHRoIDUvSGVpZ2h0
IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0
eXBlL0ltYWdlPj5zdHJlYW0NCsPzwG3lNkPLAEfNAHLlQgoNCmVuZHN0cmVhbQ1lbmRvYmoNMzgx
IDAgb2JqPDwvTGVuZ3RoIDIyL1dpZHRoIDcvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0Nv
bG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCsb0xnnm
TU3QCEbRCEzTCFXYEo7kdAoNCmVuZHN0cmVhbQ1lbmRvYmoNMzgyIDAgb2JqPDwvTGVuZ3RoIDE2
L1dpZHRoIDUvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5
cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCqnrmVXVFEjNAUnNA0nNAwoNCmVuZHN0
cmVhbQ1lbmRvYmoNMzgzIDAgb2JqPDwvTGVuZ3RoIDEzL1dpZHRoIDQvSGVpZ2h0IDEvQml0c1Bl
ckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdl
Pj5zdHJlYW0NCh8jmwAAigwPkoCWxQoNCmVuZHN0cmVhbQ1lbmRvYmoNMzg0IDAgb2JqPDwvTGVu
Z3RoIDE2L1dpZHRoIDUvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUg
MCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCnqVwQICjQAAiyozpMTi4goN
CmVuZHN0cmVhbQ1lbmRvYmoNMzg1IDAgb2JqPDwvTGVuZ3RoIDEzL1dpZHRoIDQvSGVpZ2h0IDEv
Qml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBl
L0ltYWdlPj5zdHJlYW0NClpuugAAiAUHn2BjtwoNCmVuZHN0cmVhbQ1lbmRvYmoNMzg2IDAgb2Jq
PDwvTGVuZ3RoIDQ2L1dpZHRoIDE1L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNw
YWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQppgMUAAIIAAIor
NKY4Q6cEBowMD5QdIZc3Qac4QKcdIZcOEZQAAJABApEhJZwKDQplbmRzdHJlYW0NZW5kb2JqDTM4
NyAwIG9iajw8L0xlbmd0aCAxOS9XaWR0aCA2L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9D
b2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQrD88Bt
5TZDywBIzQJJzwKM5mgKDQplbmRzdHJlYW0NZW5kb2JqDTM4OCAwIG9iajw8L0xlbmd0aCAxMy9X
aWR0aCA0L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBl
L1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQqm6pSJ6WiH5Gau8KcKDQplbmRzdHJlYW0N
ZW5kb2JqDTM4OSAwIG9iajw8L0xlbmd0aCAxOS9XaWR0aCA2L0hlaWdodCAxL0JpdHNQZXJDb21w
b25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3Ry
ZWFtDQrB9cFo4DJHzgFJzQJJzQNJzQMKDQplbmRzdHJlYW0NZW5kb2JqDTM5MCAwIG9iajw8L0xl
bmd0aCAxMy9XaWR0aCA0L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1
IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQoXGpQKDJIXHJB6kMEKDQpl
bmRzdHJlYW0NZW5kb2JqDTM5MSAwIG9iajw8L0xlbmd0aCAxNi9XaWR0aCA1L0hlaWdodCAxL0Jp
dHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9J
bWFnZT4+c3RyZWFtDQp7lMQMDpQKDI4uOafE4uQKDQplbmRzdHJlYW0NZW5kb2JqDTM5MiAwIG9i
ajw8L0xlbmd0aCAxMy9XaWR0aCA0L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNw
YWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpidr0JC4QLDZ5Z
WrIKDQplbmRzdHJlYW0NZW5kb2JqDTM5MyAwIG9iajw8L0xlbmd0aCA0My9XaWR0aCAxNC9IZWln
aHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1
YnR5cGUvSW1hZ2U+PnN0cmVhbQ0Kb4bGAACDAACEUWGvstTbTl+pCgyNBQeSCAqWBwmVAgKQAgKN
DRCSOUWtCg0KZW5kc3RyZWFtDWVuZG9iag0zOTQgMCBvYmo8PC9MZW5ndGggMjIvV2lkdGggNy9I
ZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0
L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0Kw/PAbeU2Q8sASc0DSM0AUtcMgeJbCg0KZW5kc3RyZWFt
DWVuZG9iag0zOTUgMCBvYmo8PC9MZW5ndGggMjIvV2lkdGggNy9IZWlnaHQgMS9CaXRzUGVyQ29t
cG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0
cmVhbQ0KtPCrb+I7Sc0CSMwBSc0DSs0ESc0DCg0KZW5kc3RyZWFtDWVuZG9iag0zOTYgMCBvYmo8
PC9MZW5ndGggMTMvV2lkdGggNC9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFj
ZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0Keo3CcIXAeZHFstHd
Cg0KZW5kc3RyZWFtDWVuZG9iag0zOTcgMCBvYmo8PC9MZW5ndGggMTMvV2lkdGggNC9IZWlnaHQg
MS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5
cGUvSW1hZ2U+PnN0cmVhbQ0KqsnWcYbAc4nEiZvJCg0KZW5kc3RyZWFtDWVuZG9iag0zOTggMCBv
Ymo8PC9MZW5ndGggMTMvV2lkdGggNC9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JT
cGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0Ko8TcbYC7dovJ
nqzSCg0KZW5kc3RyZWFtDWVuZG9iag0zOTkgMCBvYmo8PC9MZW5ndGggMTYvV2lkdGggNS9IZWln
aHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1
YnR5cGUvSW1hZ2U+PnN0cmVhbQ0Kb4fFAACIAACJV2q74/fxCg0KZW5kc3RyZWFtDWVuZG9iag00
MDAgMCBvYmo8PC9MZW5ndGggMjIvV2lkdGggNy9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgv
Q29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0Knrva
VGWzMz2kKzKeMzqlTFmxlrXZCg0KZW5kc3RyZWFtDWVuZG9iag00MDEgMCBvYmo8PC9MZW5ndGgg
NjQvV2lkdGggMjEvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBS
L1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCsPzwG3lNkPLAEnNA0nNA0fMAE/U
CmHUKonha6XqmbbxtLLxrJ7pjXncUFbVFUnOAUjMAknNA0rNBE7PCUnNAwoNCmVuZHN0cmVhbQ1l
bmRvYmoNNDAyIDAgb2JqPDwvTGVuZ3RoIDE2L1dpZHRoIDUvSGVpZ2h0IDEvQml0c1BlckNvbXBv
bmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJl
YW0NCmuDxQAAhAAAhFpuv+H48goNCmVuZHN0cmVhbQ1lbmRvYmoNNDAzIDAgb2JqPDwvTGVuZ3Ro
IDY0L1dpZHRoIDIxL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAg
Ui9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQrD88Bt5TZDywBJzQNJzQNJzQNI
zAFM0gVJ0QtR1RBW1hRU1hNK0g1N0wlHzQBIzQJJzQNL0QRJzgNKzQRJzgMKDQplbmRzdHJlYW0N
ZW5kb2JqDTQwNCAwIG9iajw8L0xlbmd0aCAxNi9XaWR0aCA1L0hlaWdodCAxL0JpdHNQZXJDb21w
b25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3Ry
ZWFtDQprg8QAAIgAAIlWaLvb8e4KDQplbmRzdHJlYW0NZW5kb2JqDTQwNSAwIG9iajw8L0xlbmd0
aCA2NC9XaWR0aCAyMS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAw
IFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0Kw/PAbeU2RMsASc0DSs0ESc0D
Sc0DSc0CTM4GSMwBRswARswAR8wASM0BSc0DSc0DSs0ESc0DSs0ESc4DS9IECg0KZW5kc3RyZWFt
DWVuZG9iag00MDYgMCBvYmo8PC9MZW5ndGggMTYvV2lkdGggNS9IZWlnaHQgMS9CaXRzUGVyQ29t
cG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0
cmVhbQ0Kb4bGAACEAACFVmm83PLuCg0KZW5kc3RyZWFtDWVuZG9iag00MDcgMCBvYmo8PC9MZW5n
dGggNjQvV2lkdGggMjEvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUg
MCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCsPzv2zlNkjNAEvOBU3OCEvO
BUrNBEnNA0rNBEnNA0rNBEnNA0/PCkrNBErNBEnOBE7PCUrNBU7PCUvNBUnNAwoNCmVuZHN0cmVh
bQ1lbmRvYmoNNDA4IDAgb2JqPDwvTGVuZ3RoIDE2L1dpZHRoIDUvSGVpZ2h0IDEvQml0c1BlckNv
bXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5z
dHJlYW0NCmyDxAAAiAAAiVltvt/48QoNCmVuZHN0cmVhbQ1lbmRvYmoNNDA5IDAgb2JqPDwvTGVu
Z3RoIDY0L1dpZHRoIDIxL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1
IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQrD88Bt5TZDywBJzQNKzQRL
0QRP0ApLzQVOzwlLzgVNzwhLzgVNzwhKzQVOzwlM0QVKzgRJzQNM0gZOzwlJzQMKDQplbmRzdHJl
YW0NZW5kb2JqDTQxMCAwIG9iajw8L0xlbmd0aCAxNi9XaWR0aCA1L0hlaWdodCAxL0JpdHNQZXJD
b21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+
c3RyZWFtDQpvhsYAAIQAAIRXabzc8+8KDQplbmRzdHJlYW0NZW5kb2JqDTQxMSAwIG9iajw8L0xl
bmd0aCA2NC9XaWR0aCAyMS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAx
NSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0Kw/PAbeU2Q8sASc0DTs8I
S84FTs8JS80GTs8JTNEHSc4ES9EESs4ESc0DSs0ESc0ETs8JS80GTs8JS80FSc0DCg0KZW5kc3Ry
ZWFtDWVuZG9iag00MTIgMCBvYmo8PC9MZW5ndGggMTYvV2lkdGggNS9IZWlnaHQgMS9CaXRzUGVy
Q29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+
PnN0cmVhbQ0KbYTJAACEAACFWW3A3vfxCg0KZW5kc3RyZWFtDWVuZG9iag00MTMgMCBvYmo8PC9M
ZW5ndGggNjQvV2lkdGggMjEvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2Ug
MTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCsPzwG3lNkPLAErNBErN
BE/PCUvNBU7PCUvOBU3PCErNBErOBE7PCUrNBU/OCUrOBEzSBU7PCUvNBk7PCUnNAwoNCmVuZHN0
cmVhbQ1lbmRvYmoNNDE0IDAgb2JqPDwvTGVuZ3RoIDEzL1dpZHRoIDQvSGVpZ2h0IDEvQml0c1Bl
ckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdl
Pj5zdHJlYW0NCnaMyh0jmR0jmmN2wAoNCmVuZHN0cmVhbQ1lbmRvYmoNNDE1IDAgb2JqPDwvTGVu
Z3RoIDY0L1dpZHRoIDIxL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1
IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQrD88Bt5TZDywBOzwhLzwVN
zghMzQVOzwlM0QZJzgNKzQROzwlM0gZJzgNPzgpKzQVPzwlKzQVPzwpKzQRKzQQKDQplbmRzdHJl
YW0NZW5kb2JqDTQxNiAwIG9iajw8L0xlbmd0aCA3L1dpZHRoIDIvSGVpZ2h0IDEvQml0c1BlckNv
bXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5z
dHJlYW0NCrDN5bHO5QoNCmVuZHN0cmVhbQ1lbmRvYmoNNDE3IDAgb2JqPDwvTGVuZ3RoIDc3L0Zp
bHRlci9GbGF0ZURlY29kZS9XaWR0aCAyMS9IZWlnaHQgMi9CaXRzUGVyQ29tcG9uZW50IDgvQ29s
b3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KSIk6/PlA
7lMzl9MMnmeZvS+yep5n9j/H6X2W1e88Cul1ltUfnWTxP891+PP+nKdmnmcZvM+x+gE1nkPXiEM7
F1A70EaAAAMAA9AyvgoNCmVuZHN0cmVhbQ1lbmRvYmoNNDE4IDAgb2JqPDwvTGVuZ3RoIDQvV2lk
dGggMS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9Y
T2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0Kk6jzCg0KZW5kc3RyZWFtDWVuZG9iag00MTkg
MCBvYmo8PC9MZW5ndGggNy9XaWR0aCAyL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xv
clNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQqMou9Ra9AK
DQplbmRzdHJlYW0NZW5kb2JqDTQyMCAwIG9iajw8L0xlbmd0aCAxMC9XaWR0aCAzL0hlaWdodCAx
L0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlw
ZS9JbWFnZT4+c3RyZWFtDQqLoe9TcN5PcM8KDQplbmRzdHJlYW0NZW5kb2JqDTQyMSAwIG9iajw8
L0xlbmd0aCAxMC9XaWR0aCAzL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNl
IDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQp0jOhGY9g/XMoKDQpl
bmRzdHJlYW0NZW5kb2JqDTQyMiAwIG9iajw8L0xlbmd0aCAxMy9XaWR0aCA0L0hlaWdodCAxL0Jp
dHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9J
bWFnZT4+c3RyZWFtDQqpwfWoufmqu/mjtvMKDQplbmRzdHJlYW0NZW5kb2JqDTQyMyAwIG9iajw8
L0xlbmd0aCA0L1dpZHRoIDEvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2Ug
MTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCsfX6QoNCmVuZHN0cmVh
bQ1lbmRvYmoNNDI0IDAgb2JqPDwvTGVuZ3RoIDQvV2lkdGggMS9IZWlnaHQgMS9CaXRzUGVyQ29t
cG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0
cmVhbQ0Kx9/vCg0KZW5kc3RyZWFtDWVuZG9iag00MjUgMCBvYmo8PC9MZW5ndGggNC9XaWR0aCAx
L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmpl
Y3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQrs7/UKDQplbmRzdHJlYW0NZW5kb2JqDTQyNiAwIG9i
ajw8L0xlbmd0aCA0L1dpZHRoIDEvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3Bh
Y2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCu7w+AoNCmVuZHN0
cmVhbQ1lbmRvYmoNNDI3IDAgb2JqPDwvTGVuZ3RoIDQvV2lkdGggMS9IZWlnaHQgMS9CaXRzUGVy
Q29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+
PnN0cmVhbQ0K2dzkCg0KZW5kc3RyZWFtDWVuZG9iag00MjggMCBvYmo8PC9MZW5ndGggNy9XaWR0
aCAyL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hP
YmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQrk7fXO1doKDQplbmRzdHJlYW0NZW5kb2JqDTQy
OSAwIG9iajw8L0xlbmd0aCA0L1dpZHRoIDEvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0Nv
bG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCr/M9woN
CmVuZHN0cmVhbQ1lbmRvYmoNNDMwIDAgb2JqPDwvTGVuZ3RoIDEwL1dpZHRoIDMvSGVpZ2h0IDEv
Qml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBl
L0ltYWdlPj5zdHJlYW0NCoKX5GmB3Xuj7goNCmVuZHN0cmVhbQ1lbmRvYmoNNDMxIDAgb2JqPDwv
TGVuZ3RoIDQvV2lkdGggMS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAx
NSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0K19zvCg0KZW5kc3RyZWFt
DWVuZG9iag00MzIgMCBvYmo8PC9MZW5ndGggNy9XaWR0aCAyL0hlaWdodCAxL0JpdHNQZXJDb21w
b25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3Ry
ZWFtDQqTp/CWpdwKDQplbmRzdHJlYW0NZW5kb2JqDTQzMyAwIG9iajw8L0xlbmd0aCAxMy9XaWR0
aCA0L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hP
YmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpxh9tHYs1JY8twlNkKDQplbmRzdHJlYW0NZW5k
b2JqDTQzNCAwIG9iajw8L0xlbmd0aCA0L1dpZHRoIDEvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVu
dCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0N
Cqe48woNCmVuZHN0cmVhbQ1lbmRvYmoNNDM1IDAgb2JqPDwvTGVuZ3RoIDcvV2lkdGggMi9IZWln
aHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1
YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KmazxYHnaCg0KZW5kc3RyZWFtDWVuZG9iag00MzYgMCBvYmo8
PC9MZW5ndGggMTMvV2lkdGggNC9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFj
ZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KYXraTWfKSWHJj5/d
Cg0KZW5kc3RyZWFtDWVuZG9iag00MzcgMCBvYmo8PC9MZW5ndGggNy9XaWR0aCAyL0hlaWdodCAx
L0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlw
ZS9JbWFnZT4+c3RyZWFtDQrd4/ZfesEKDQplbmRzdHJlYW0NZW5kb2JqDTQzOCAwIG9iajw8L0xl
bmd0aCA3L1dpZHRoIDIvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUg
MCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCoug7mmC4goNCmVuZHN0cmVh
bQ1lbmRvYmoNNDM5IDAgb2JqPDwvTGVuZ3RoIDIyL1dpZHRoIDcvSGVpZ2h0IDEvQml0c1BlckNv
bXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5z
dHJlYW0NCnqM20ZgyUdixWh8zLa/446d1E5mvgoNCmVuZHN0cmVhbQ1lbmRvYmoNNDQwIDAgb2Jq
PDwvTGVuZ3RoIDEwL1dpZHRoIDMvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3Bh
Y2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCoyh701o3YCszwoN
CmVuZHN0cmVhbQ1lbmRvYmoNNDQxIDAgb2JqPDwvTGVuZ3RoIDIyL1dpZHRoIDcvSGVpZ2h0IDEv
Qml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBl
L0ltYWdlPj5zdHJlYW0NCp6w7VZ00UJcv0hhv0NdvEZfuE1iuAoNCmVuZHN0cmVhbQ1lbmRvYmoN
NDQyIDAgb2JqPDwvTGVuZ3RoIDEwL1dpZHRoIDMvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4
L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCoOa
6kto13qQ8AoNCmVuZHN0cmVhbQ1lbmRvYmoNNDQzIDAgb2JqPDwvTGVuZ3RoIDIyL1dpZHRoIDcv
SGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVj
dC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCtzo9Zux6Vh2zUBZuUhhukdetkphtQoNCmVuZHN0cmVh
bQ1lbmRvYmoNNDQ0IDAgb2JqPDwvTGVuZ3RoIDEzL1dpZHRoIDQvSGVpZ2h0IDEvQml0c1BlckNv
bXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5z
dHJlYW0NCoWa61Jt2FFr1ZKq3woNCmVuZHN0cmVhbQ1lbmRvYmoNNDQ1IDAgb2JqPDwvTGVuZ3Ro
IDE2L1dpZHRoIDUvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBS
L1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCq/F7Ft5zENbtkVdtEhgswoNCmVu
ZHN0cmVhbQ1lbmRvYmoNNDQ2IDAgb2JqPDwvTGVuZ3RoIDE2L1dpZHRoIDUvSGVpZ2h0IDEvQml0
c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0lt
YWdlPj5zdHJlYW0NCoWb6lFu2VRt1E1o0a/J6woNCmVuZHN0cmVhbQ1lbmRvYmoNNDQ3IDAgb2Jq
PDwvTGVuZ3RoIDE2L1dpZHRoIDUvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3Bh
Y2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCqu73k5htERbs0Rc
r0hftAoNCmVuZHN0cmVhbQ1lbmRvYmoNNDQ4IDAgb2JqPDwvTGVuZ3RoIDE5L1dpZHRoIDYvSGVp
Z2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9T
dWJ0eXBlL0ltYWdlPj5zdHJlYW0NCoSa6lFt2FRt1U9qz1h21NXm9goNCmVuZHN0cmVhbQ1lbmRv
YmoNNDQ5IDAgb2JqPDwvTGVuZ3RoIDEzL1dpZHRoIDQvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVu
dCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0N
CoWTzT9YsUBXr0dfsgoNCmVuZHN0cmVhbQ1lbmRvYmoNNDUwIDAgb2JqPDwvTGVuZ3RoIDEzL1dp
ZHRoIDQvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUv
WE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCrKysq+vr66usLGxsQoNCmVuZHN0cmVhbQ1l
bmRvYmoNNDUxIDAgb2JqPDwvTGVuZ3RoIDE2L1dpZHRoIDUvSGVpZ2h0IDEvQml0c1BlckNvbXBv
bmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJl
YW0NCre3t66urq+vr6+vr7OzswoNCmVuZHN0cmVhbQ1lbmRvYmoNNDUyIDAgb2JqPDwvTGVuZ3Ro
IDIyL1dpZHRoIDcvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBS
L1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCoCW6VJt2FRt01Fs0Etky2KA1czc
8goNCmVuZHN0cmVhbQ1lbmRvYmoNNDUzIDAgb2JqPDwvTGVuZ3RoIDEzL1dpZHRoIDQvSGVpZ2h0
IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0
eXBlL0ltYWdlPj5zdHJlYW0NCoOSyD5WrUBXrEherwoNCmVuZHN0cmVhbQ1lbmRvYmoNNDU0IDAg
b2JqPDwvTGVuZ3RoIDI1L1dpZHRoIDgvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9y
U3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCqioqJWVlZOT
k5OTk5KSkpmZmaWlpaqqqgoNCmVuZHN0cmVhbQ1lbmRvYmoNNDU1IDAgb2JqPDwvTGVuZ3RoIDI1
L1dpZHRoIDgvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5
cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCqmpqZaWlpKSkpOTk5OTk5KSkpeXl6mp
qQoNCmVuZHN0cmVhbQ1lbmRvYmoNNDU2IDAgb2JqPDwvTGVuZ3RoIDI4L1dpZHRoIDkvSGVpZ2h0
IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0
eXBlL0ltYWdlPj5zdHJlYW0NCoCX6lFt2FNs01Bs0FBqzExlx1NuzYSf29nh8goNCmVuZHN0cmVh
bQ1lbmRvYmoNNDU3IDAgb2JqPDwvTGVuZ3RoIDEzL1dpZHRoIDQvSGVpZ2h0IDEvQml0c1BlckNv
bXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5z
dHJlYW0NCmd4vzxUqT1YqUdbqwoNCmVuZHN0cmVhbQ1lbmRvYmoNNDU4IDAgb2JqPDwvTGVuZ3Ro
IDMxL1dpZHRoIDEwL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAg
Ui9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQqhoaGdnZ2enp6enp6enp6enp6e
np6enp6enp6goKAKDQplbmRzdHJlYW0NZW5kb2JqDTQ1OSAwIG9iajw8L0xlbmd0aCAzMS9XaWR0
aCAxMC9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9Y
T2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KmJiYkZGRjY2NiIiIh4eHh4eHioqKj4+Pj4+P
l5eXCg0KZW5kc3RyZWFtDWVuZG9iag00NjAgMCBvYmo8PC9MZW5ndGggMzEvV2lkdGggMTAvSGVp
Z2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9T
dWJ0eXBlL0ltYWdlPj5zdHJlYW0NCpqampKSko+Pj4qKioeHh4eHh4eHh4qKio+Pj5iYmAoNCmVu
ZHN0cmVhbQ1lbmRvYmoNNDYxIDAgb2JqPDwvTGVuZ3RoIDIzL0ZpbHRlci9GbGF0ZURlY29kZS9X
aWR0aCAyMS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlw
ZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KSImaNm3aggUL5pEFgBoBAgwA2Fkm1woN
CmVuZHN0cmVhbQ1lbmRvYmoNNDYyIDAgb2JqPDwvTGVuZ3RoIDMxL1dpZHRoIDEwL0hlaWdodCAx
L0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlw
ZS9JbWFnZT4+c3RyZWFtDQp+lelRbNdTbdNQbM9OZ8tJZMdHX8FNaMZqf8u9xd8KDQplbmRzdHJl
YW0NZW5kb2JqDTQ2MyAwIG9iajw8L0xlbmd0aCAxNi9XaWR0aCA1L0hlaWdodCAxL0JpdHNQZXJD
b21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+
c3RyZWFtDQqNmMc7VapAV6ZAVaJHXKoKDQplbmRzdHJlYW0NZW5kb2JqDTQ2NCAwIG9iajw8L0xl
bmd0aCAzMS9XaWR0aCAxMC9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAx
NSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0Kg4ODkpKSj4+Pj4+Pj4+P
j4+Pj4+Pj4+Pj4+PkZGRCg0KZW5kc3RyZWFtDWVuZG9iag00NjUgMCBvYmo8PC9MZW5ndGggMzcv
V2lkdGggMTIvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5
cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCpKSkomJiYaGhoeHh4mJiY+Pj4+Pj4+P
j4+Pj4+Pj5KSkoyMjAoNCmVuZHN0cmVhbQ1lbmRvYmoNNDY2IDAgb2JqPDwvTGVuZ3RoIDM3L1dp
ZHRoIDEyL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBl
L1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQqRkZGKioqHh4eIiIiHh4eMjIyPj4+Pj4+P
j4+Pj4+VlZWSkpIKDQplbmRzdHJlYW0NZW5kb2JqDTQ2NyAwIG9iajw8L0xlbmd0aCAyNy9GaWx0
ZXIvRmxhdGVEZWNvZGUvV2lkdGggMjIvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9y
U3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCkiJSkhIKC8v
nzJlSj9ZYObMmQABBgCh/yQ3Cg0KZW5kc3RyZWFtDWVuZG9iag00NjggMCBvYmo8PC9MZW5ndGgg
MzQvV2lkdGggMTEvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBS
L1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCoCX61Ft11Nt009rz1Jt0GV/2GN7
0UxmwkRdvERfu5Cf1woNCmVuZHN0cmVhbQ1lbmRvYmoNNDY5IDAgb2JqPDwvTGVuZ3RoIDE2L1dp
ZHRoIDUvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUv
WE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCqGu2DpTp0BWpD9UoEJWpAoNCmVuZHN0cmVh
bQ1lbmRvYmoNNDcwIDAgb2JqPDwvTGVuZ3RoIDM0L1dpZHRoIDExL0hlaWdodCAxL0JpdHNQZXJD
b21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+
c3RyZWFtDQpaWlqKioqIiIiHh4eHh4eHh4eHh4eHh4eHh4eHh4eNjY0KDQplbmRzdHJlYW0NZW5k
b2JqDTQ3MSAwIG9iajw8L0xlbmd0aCA0MC9XaWR0aCAxMy9IZWlnaHQgMS9CaXRzUGVyQ29tcG9u
ZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVh
bQ0KkZGRgoKChISEg4ODjY2NsrKyxMTEwsLCwsLCwsLCw8PDoKCgjY2NCg0KZW5kc3RyZWFtDWVu
ZG9iag00NzIgMCBvYmo8PC9MZW5ndGggNDMvV2lkdGggMTQvSGVpZ2h0IDEvQml0c1BlckNvbXBv
bmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJl
YW0NCpCQkIKCgoODg4SEhIeHh5CQkLOzs8TExMLCwsLCwsLCwsXFxa2trZWVlQoNCmVuZHN0cmVh
bQ1lbmRvYmoNNDczIDAgb2JqPDwvTGVuZ3RoIDMyL0ZpbHRlci9GbGF0ZURlY29kZS9XaWR0aCAy
My9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2Jq
ZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KSImKiIiwt7dvbGzs7u5uJx10dnZOnz4dIMAAnKQj
LwoNCmVuZHN0cmVhbQ1lbmRvYmoNNDc0IDAgb2JqPDwvTGVuZ3RoIDM3L1dpZHRoIDEyL0hlaWdo
dCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3Vi
dHlwZS9JbWFnZT4+c3RyZWFtDQqAmOxQbNdSbdNQbNBOaMuOptjS2uuCnNVDXbxHYLpAV7OcqNcK
DQplbmRzdHJlYW0NZW5kb2JqDTQ3NSAwIG9iajw8L0xlbmd0aCAxNi9XaWR0aCA1L0hlaWdodCAx
L0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlw
ZS9JbWFnZT4+c3RyZWFtDQqfrdg4UKNAVKI8UZ9BVJwKDQplbmRzdHJlYW0NZW5kb2JqDTQ3NiAw
IG9iajw8L0xlbmd0aCAzNC9XaWR0aCAxMS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29s
b3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KQkJChoaG
mJiYlJSUlJSUlJSUlJSUlJSUlJSUk5OTm5ubCg0KZW5kc3RyZWFtDWVuZG9iag00NzcgMCBvYmo8
PC9MZW5ndGggNDMvV2lkdGggMTQvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3Bh
Y2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCouLi39/f4CAgIaG
hqOjo8DAwL6+vr6+vr6+vr6+vr+/v76+vrW1tZmZmQoNCmVuZHN0cmVhbQ1lbmRvYmoNNDc4IDAg
b2JqPDwvTGVuZ3RoIDQ2L1dpZHRoIDE1L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xv
clNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQqOjo59fX2A
gICAgICKioq0tLS/v7++vr6+vr6+vr6+vr6+vr6+vr68vLylpaUKDQplbmRzdHJlYW0NZW5kb2Jq
DTQ3OSAwIG9iajw8L0xlbmd0aCA0Mi9GaWx0ZXIvRmxhdGVEZWNvZGUvV2lkdGggMjQvSGVpZ2h0
IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0
eXBlL0ltYWdlPj5zdHJlYW0NCkiJio6O1tfXDwwM7OvrmzZt2pQpU6YSDaaAweTJk1euXAkQYAA/
5SdYCg0KZW5kc3RyZWFtDWVuZG9iag00ODAgMCBvYmo8PC9MZW5ndGggMTkvV2lkdGggNi9IZWln
aHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1
YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KgpnsUWzXU23TUGzQSWTKiZnTCg0KZW5kc3RyZWFtDWVuZG9i
ag00ODEgMCBvYmo8PC9MZW5ndGggMTYvV2lkdGggNS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50
IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0K
dIfRQly6SGG4P1eyoK7aCg0KZW5kc3RyZWFtDWVuZG9iag00ODIgMCBvYmo8PC9MZW5ndGggMTkv
V2lkdGggNi9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlw
ZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KrbneOVCiQFWhPVKeO06dRFKXCg0KZW5k
c3RyZWFtDWVuZG9iag00ODMgMCBvYmo8PC9MZW5ndGggMzQvV2lkdGggMTEvSGVpZ2h0IDEvQml0
c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0lt
YWdlPj5zdHJlYW0NCjc3N5OTk7u7u7W1tbW1tbW1tbW1tbW1tbW1tbW1tby8vAoNCmVuZHN0cmVh
bQ1lbmRvYmoNNDg0IDAgb2JqPDwvTGVuZ3RoIDQ2L1dpZHRoIDE1L0hlaWdodCAxL0JpdHNQZXJD
b21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+
c3RyZWFtDQqOjo56enp9fX2EhISsrKy3t7e0tLS0tLS0tLS0tLS0tLS0tLS0tLS3t7exsbEKDQpl
bmRzdHJlYW0NZW5kb2JqDTQ4NSAwIG9iajw8L0xlbmd0aCA0OS9XaWR0aCAxNi9IZWlnaHQgMS9C
aXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUv
SW1hZ2U+PnN0cmVhbQ0KiYmJe3t7fX19gYGBmZmZtra2tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0
tra2xMTECg0KZW5kc3RyZWFtDWVuZG9iag00ODYgMCBvYmo8PC9MZW5ndGggMzMvRmlsdGVyL0Zs
YXRlRGVjb2RlL1dpZHRoIDI0L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNl
IDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpIiYqOjjY2NjYyMurv
79+zZ89WssC+ffsAAgwAFeQuigoNCmVuZHN0cmVhbQ1lbmRvYmoNNDg3IDAgb2JqPDwvTGVuZ3Ro
IDE5L1dpZHRoIDYvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBS
L1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCn+V6lFs11Nt01Brz0pjyXSK2AoN
CmVuZHN0cmVhbQ1lbmRvYmoNNDg4IDAgb2JqPDwvTGVuZ3RoIDE2L1dpZHRoIDUvSGVpZ2h0IDEv
Qml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBl
L0ltYWdlPj5zdHJlYW0NCpmo30JcuUhft0JZtGJ3vQoNCmVuZHN0cmVhbQ1lbmRvYmoNNDg5IDAg
b2JqPDwvTGVuZ3RoIDE5L1dpZHRoIDYvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9y
U3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCqOv2DhPoD5T
nzxPnTtMmUFQlAoNCmVuZHN0cmVhbQ1lbmRvYmoNNDkwIDAgb2JqPDwvTGVuZ3RoIDM0L1dpZHRo
IDExL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hP
YmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQo3NzeNjY2zs7Otra2tra2urq6tra2tra2tra2t
ra21tbUKDQplbmRzdHJlYW0NZW5kb2JqDTQ5MSAwIG9iajw8L0xlbmd0aCA1Mi9XaWR0aCAxNy9I
ZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0
L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KjIyMd3d3enp6h4eHqqqqrq6urKysrKysrKysrKysrKys
rKysrKysrKysrKysr6+vs7OzCg0KZW5kc3RyZWFtDWVuZG9iag00OTIgMCBvYmo8PC9MZW5ndGgg
NTIvV2lkdGggMTcvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBS
L1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCo2NjXV1dXp6ent7e6GhobCwsKys
rKysrKysrKysrKysrKysrKysrKysrKysrK6ursDAwAoNCmVuZHN0cmVhbQ1lbmRvYmoNNDkzIDAg
b2JqPDwvTGVuZ3RoIDM3L0ZpbHRlci9GbGF0ZURlY29kZS9XaWR0aCAyNC9IZWlnaHQgMS9CaXRz
UGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1h
Z2U+PnN0cmVhbQ0KSImKjo42BoPOzs4tW7asxQDrwACP+Jo1azZv3gwQYADaESybCg0KZW5kc3Ry
ZWFtDWVuZG9iag00OTQgMCBvYmo8PC9MZW5ndGggMjIvV2lkdGggNy9IZWlnaHQgMS9CaXRzUGVy
Q29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+
PnN0cmVhbQ0KgJbpUm3YU23TUGzRUGrNS2THbIjVCg0KZW5kc3RyZWFtDWVuZG9iag00OTUgMCBv
Ymo8PC9MZW5ndGggMTMvV2lkdGggNC9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JT
cGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0Kg5XVOlSzO1Sx
iZfHCg0KZW5kc3RyZWFtDWVuZG9iag00OTYgMCBvYmo8PC9MZW5ndGggMTkvV2lkdGggNi9IZWln
aHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1
YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KjpnHOU6fPFGdPE6bO0qVPU+UCg0KZW5kc3RyZWFtDWVuZG9i
ag00OTcgMCBvYmo8PC9MZW5ndGggMzQvV2lkdGggMTEvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVu
dCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0N
Cjc3N4qKiq6urqioqKioqKioqKioqKioqKioqKioqLCwsAoNCmVuZHN0cmVhbQ1lbmRvYmoNNDk4
IDAgb2JqPDwvTGVuZ3RoIDUyL1dpZHRoIDE3L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9D
b2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQp7e3t1
dXV4eHienp6rq6uoqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKi3t7cKDQplbmRzdHJl
YW0NZW5kb2JqDTQ5OSAwIG9iajw8L0xlbmd0aCA1NS9XaWR0aCAxOC9IZWlnaHQgMS9CaXRzUGVy
Q29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+
PnN0cmVhbQ0KdnZ2dHR0dnZ2ioqKqKioqampqKioqKioqKioqKioqKioqKioqKioqKioqKioqKio
qampvr6+Cg0KZW5kc3RyZWFtDWVuZG9iag01MDAgMCBvYmo8PC9MZW5ndGggMzUvRmlsdGVyL0Zs
YXRlRGVjb2RlL1dpZHRoIDI0L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNl
IDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpIiYqOjjY2NjYxMWlr
a1u3bt0K0sHy5cuBGgECDACzEStaCg0KZW5kc3RyZWFtDWVuZG9iag01MDEgMCBvYmo8PC9MZW5n
dGggMjUvV2lkdGggOC9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAw
IFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KgZjqUm3ZU23TUGzQUGrNUGjK
R2LFjqbdCg0KZW5kc3RyZWFtDWVuZG9iag01MDIgMCBvYmo8PC9MZW5ndGggMTAvV2lkdGggMy9I
ZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0
L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KrLnogZXYnafjCg0KZW5kc3RyZWFtDWVuZG9iag01MDMg
MCBvYmo8PC9MZW5ndGggMjIvV2lkdGggNy9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29s
b3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0Kbn25OU+e
PFCePE2aO0qVOUqUOkqTCg0KZW5kc3RyZWFtDWVuZG9iag01MDQgMCBvYmo8PC9MZW5ndGggMzQv
V2lkdGggMTEvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5
cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCjc3N4SEhKampqGhoaGhoaKioqGhoaGh
oaGhoaGhoampqQoNCmVuZHN0cmVhbQ1lbmRvYmoNNTA1IDAgb2JqPDwvTGVuZ3RoIDU1L1dpZHRo
IDE4L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hP
YmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQqEhIRxcXF7e3ubm5ujo6OhoaGhoaGhoaGioqKi
oqKhoaGhoaGhoaGhoaGhoaGhoaGhoaG1tbUKDQplbmRzdHJlYW0NZW5kb2JqDTUwNiAwIG9iajw8
L0xlbmd0aCAzNi9GaWx0ZXIvRmxhdGVEZWNvZGUvV2lkdGggMTkvSGVpZ2h0IDEvQml0c1BlckNv
bXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5z
dHJlYW0NCkiJamxszM/PLyoq6ujoWLJkyUIiwIIFC7Zs2QIQYAC0jSJLCg0KZW5kc3RyZWFtDWVu
ZG9iag01MDcgMCBvYmo8PC9MZW5ndGggMzcvRmlsdGVyL0ZsYXRlRGVjb2RlL1dpZHRoIDI0L0hl
aWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3Qv
U3VidHlwZS9JbWFnZT4+c3RyZWFtDQpIiYqOjjY2NjYxMWlsbFy+fPlCDLAIDPCLL1u2DCDAAH6U
KbMKDQplbmRzdHJlYW0NZW5kb2JqDTUwOCAwIG9iajw8L0xlbmd0aCAyNS9XaWR0aCA4L0hlaWdo
dCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3Vi
dHlwZS9JbWFnZT4+c3RyZWFtDQp+lOlRbNdTbdNQbM9QactNaMdGYMKeqdYKDQplbmRzdHJlYW0N
ZW5kb2JqDTUwOSAwIG9iajw8L0xlbmd0aCAyNS9XaWR0aCA4L0hlaWdodCAxL0JpdHNQZXJDb21w
b25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3Ry
ZWFtDQqfq9g5T6A7UJw8Tps8S5U5SpM4R483UI8KDQplbmRzdHJlYW0NZW5kb2JqDTUxMCAwIG9i
ajw8L0xlbmd0aCAzNC9XaWR0aCAxMS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JT
cGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KNzc3fX19nZ2d
mJiYmJiYmJiYmJiYmJiYmJiYl5eXoaGhCg0KZW5kc3RyZWFtDWVuZG9iag01MTEgMCBvYmo8PC9M
ZW5ndGggMzUvRmlsdGVyL0ZsYXRlRGVjb2RlL1dpZHRoIDE5L0hlaWdodCAxL0JpdHNQZXJDb21w
b25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3Ry
ZWFtDQpIiaqtrc3Pz6+urp4+ffrMmTNnEAGAKpcvXw4QYACZ8yDgCg0KZW5kc3RyZWFtDWVuZG9i
ag01MTIgMCBvYmo8PC9MZW5ndGggMzMvRmlsdGVyL0ZsYXRlRGVjb2RlL1dpZHRoIDIwL0hlaWdo
dCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3Vi
dHlwZS9JbWFnZT4+c3RyZWFtDQpIiaqqqsrOzi4oKGhpaZk1a9YMosGmTZsAAgwA6dkiYAoNCmVu
ZHN0cmVhbQ1lbmRvYmoNNTEzIDAgb2JqPDwvTGVuZ3RoIDM1L0ZpbHRlci9GbGF0ZURlY29kZS9X
aWR0aCAyNC9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlw
ZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KSImKjo42NjY2MTGprq6eO3fuDNLB9OnT
gRoBAgwAN/wncwoNCmVuZHN0cmVhbQ1lbmRvYmoNNTE0IDAgb2JqPDwvTGVuZ3RoIDI4L1dpZHRo
IDkvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9i
amVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCoCX6VFt2FNt01Bs0FBpzE9oyU1mxkhfv3GOzgoN
CmVuZHN0cmVhbQ1lbmRvYmoNNTE1IDAgb2JqPDwvTGVuZ3RoIDI1L1dpZHRoIDgvSGVpZ2h0IDEv
Qml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBl
L0ltYWdlPj5zdHJlYW0NCmd4ujlOnDxPnDxMmDlLkzlIkjJLiDJTjgoNCmVuZHN0cmVhbQ1lbmRv
YmoNNTE2IDAgb2JqPDwvTGVuZ3RoIDM0L1dpZHRoIDExL0hlaWdodCAxL0JpdHNQZXJDb21wb25l
bnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFt
DQo4ODh3d3eTk5OPj4+Pj4+Pj4+Pj4+Pj4+Pj4+Ojo6YmJgKDQplbmRzdHJlYW0NZW5kb2JqDTUx
NyAwIG9iajw8L0xlbmd0aCAzNS9GaWx0ZXIvRmxhdGVEZWNvZGUvV2lkdGggMjAvSGVpZ2h0IDEv
Qml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBl
L0ltYWdlPj5zdHJlYW0NCkiJqqioyMrKKisr6+vrmzBhQj9xAKh43rx5AAEGAMcvILAKDQplbmRz
dHJlYW0NZW5kb2JqDTUxOCAwIG9iajw8L0xlbmd0aCAzNi9GaWx0ZXIvRmxhdGVEZWNvZGUvV2lk
dGggMjAvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUv
WE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCkiJSk9Pz8zMLCgo6O7unjBhQj9xoLe3d9my
ZQABBgC1ayB0Cg0KZW5kc3RyZWFtDWVuZG9iag01MTkgMCBvYmo8PC9MZW5ndGggMzYvRmlsdGVy
L0ZsYXRlRGVjb2RlL1dpZHRoIDI0L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNw
YWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpIiYqOjjY2NjY1
NS0tLZ0yZUo/6aCvr2/y5MkAAQYA8/glRQoNCmVuZHN0cmVhbQ1lbmRvYmoNNTIwIDAgb2JqPDwv
TGVuZ3RoIDMxL1dpZHRoIDEwL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNl
IDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQp/lulRbdhTbdNQbM9Q
acxPaMlMZsVLYsFGZL6fvdgKDQplbmRzdHJlYW0NZW5kb2JqDTUyMSAwIG9iajw8L0xlbmd0aCAy
OC9XaWR0aCA5L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9U
eXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQqcqdU7UJ87T5w8TZk7S5Q4SZM3SYsn
ToM5TI8KDQplbmRzdHJlYW0NZW5kb2JqDTUyMiAwIG9iajw8L0xlbmd0aCAzNC9XaWR0aCAxMS9I
ZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0
L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KODg4cXFxioqKhoaGhoaGhoaGhoaGhoaGhoaGhYWFkJCQ
Cg0KZW5kc3RyZWFtDWVuZG9iag01MjMgMCBvYmo8PC9MZW5ndGggMjkvRmlsdGVyL0ZsYXRlRGVj
b2RlL1dpZHRoIDIwL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAg
Ui9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpIiSopKUlPTy8pKWkjBbS2tk6b
Ng0gwACSph7NCg0KZW5kc3RyZWFtDWVuZG9iag01MjQgMCBvYmo8PC9MZW5ndGggMzUvRmlsdGVy
L0ZsYXRlRGVjb2RlL1dpZHRoIDIxL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNw
YWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpIicrKykpOTs7K
ympsbGxvb28jGrS0tMyfPx8gwADetCAjCg0KZW5kc3RyZWFtDWVuZG9iag01MjUgMCBvYmo8PC9M
ZW5ndGggMzQvRmlsdGVyL0ZsYXRlRGVjb2RlL1dpZHRoIDI0L0hlaWdodCAxL0JpdHNQZXJDb21w
b25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3Ry
ZWFtDQpIiYqOjjY2NjY1Nc3Ly+vq6mojHbS2tgI1AgQYAK3bIxEKDQplbmRzdHJlYW0NZW5kb2Jq
DTUyNiAwIG9iajw8L0xlbmd0aCAzNC9XaWR0aCAxMS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50
IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0K
fZXoUWvXU2zTUGvPUGnMTmjITWXDS2TAQ126ZITL1uL2Cg0KZW5kc3RyZWFtDWVuZG9iag01Mjcg
MCBvYmo8PC9MZW5ndGggMzQvV2lkdGggMTEvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0Nv
bG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCtTZ7mt8
vTlPnTxPnDxMmTtKlDhJlDdIjClQgzBGhjtLjgoNCmVuZHN0cmVhbQ1lbmRvYmoNNTI4IDAgb2Jq
PDwvTGVuZ3RoIDM0L1dpZHRoIDExL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNw
YWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQo4ODhtbW2FhYWB
gYGBgYGCgoKBgYGBgYGBgYGAgICLi4sKDQplbmRzdHJlYW0NZW5kb2JqDTUyOSAwIG9iajw8L0xl
bmd0aCAzMi9GaWx0ZXIvRmxhdGVEZWNvZGUvV2lkdGggMjEvSGVpZ2h0IDEvQml0c1BlckNvbXBv
bmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJl
YW0NCkiJSk5OTktLKy0tbW5ubiQaNIDBpEmTAAIMAMlyHyQKDQplbmRzdHJlYW0NZW5kb2JqDTUz
MCAwIG9iajw8L0xlbmd0aCAzNS9GaWx0ZXIvRmxhdGVEZWNvZGUvV2lkdGggMjEvSGVpZ2h0IDEv
Qml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBl
L0ltYWdlPj5zdHJlYW0NCkiJio+PT0hIyMjIaGhoaGpqaiQa1NfXz507FyDAALjgHvoKDQplbmRz
dHJlYW0NZW5kb2JqDTUzMSAwIG9iajw8L0xlbmd0aCAzNi9GaWx0ZXIvRmxhdGVEZWNvZGUvV2lk
dGggMjQvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUv
WE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCkiJio6ONjY2NjU1zc7Obmtra8QATWCAX7y1
tRUgwACJ1SHuCg0KZW5kc3RyZWFtDWVuZG9iag01MzIgMCBvYmo8PC9MZW5ndGggNzMvV2lkdGgg
MjQvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9i
amVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCn6V6lFs11Nt01Br0FBpzE5nx0xlw0xlwktlw0Va
tVJjtIWOv5ykzXWCvkhesDxRnzxQnDxMmDpLkzlIkS9NhytLhTVChTdHhwoNCmVuZHN0cmVhbQ1l
bmRvYmoNNTMzIDAgb2JqPDwvTGVuZ3RoIDM0L1dpZHRoIDExL0hlaWdodCAxL0JpdHNQZXJDb21w
b25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3Ry
ZWFtDQo4ODhqamqAgIB9fX19fX19fX19fX19fX19fX18fHyHh4cKDQplbmRzdHJlYW0NZW5kb2Jq
DTUzNCAwIG9iajw8L0xlbmd0aCAzMi9GaWx0ZXIvRmxhdGVEZWNvZGUvV2lkdGggMjEvSGVpZ2h0
IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0
eXBlL0ltYWdlPj5zdHJlYW0NCkiJysnJSUxMzMvLq6urqyUFVFdX9/f3AwQYALArHkMKDQplbmRz
dHJlYW0NZW5kb2JqDTUzNSAwIG9iajw8L0xlbmd0aCAzOC9GaWx0ZXIvRmxhdGVEZWNvZGUvV2lk
dGggMjIvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUv
WE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCkiJSkxMjI6OTkxMrKioqKurqyUa1NTUVFdX
T548GSDAAPRHH1oKDQplbmRzdHJlYW0NZW5kb2JqDTUzNiAwIG9iajw8L0xlbmd0aCAzNS9GaWx0
ZXIvRmxhdGVEZWNvZGUvV2lkdGggMjQvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9y
U3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCkiJio6ONjY2
NjU1zcjIaGxsrMUAdWCAXxyoESDAAGpeIPIKDQplbmRzdHJlYW0NZW5kb2JqDTUzNyAwIG9iajw8
L0xlbmd0aCA3Ni9XaWR0aCAyNS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFj
ZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0Kf5brUWzXUmzSUGvP
UGnLTmjHTWfGTmfHQVOrNkaKIjVcHzNXJztbLUFrMkOIOkyZPlOjPE2ZOkuTOUmSM0uJKU2ENUOG
MkGBMkKACg0KZW5kc3RyZWFtDWVuZG9iag01MzggMCBvYmo8PC9MZW5ndGggMzQvV2lkdGggMTEv
SGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVj
dC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCjg4OGRkZHZ2dnR0dHR0dHR0dHR0dHR0dHR0dHNzc35+
fgoNCmVuZHN0cmVhbQ1lbmRvYmoNNTM5IDAgb2JqPDwvTGVuZ3RoIDMyL0ZpbHRlci9GbGF0ZURl
Y29kZS9XaWR0aCAyMS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAw
IFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KSIlKTk6Oj4/Pzc0tLS0tIQUU
Fxc3NDQABBgAc00cKgoNCmVuZHN0cmVhbQ1lbmRvYmoNNTQwIDAgb2JqPDwvTGVuZ3RoIDI5L0Zp
bHRlci9GbGF0ZURlY29kZS9XaWR0aCAyMi9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29s
b3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KSIkKDw+P
iIhISkoqIR0UFxdXVlYCBBgAs3kdFAoNCmVuZHN0cmVhbQ1lbmRvYmoNNTQxIDAgb2JqPDwvTGVu
Z3RoIDMyL0ZpbHRlci9GbGF0ZURlY29kZS9XaWR0aCAyNC9IZWlnaHQgMS9CaXRzUGVyQ29tcG9u
ZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVh
bQ0KSImytrY2NTW1t7cvKCgoLS0tIQtUVFQABBgAGzUenQoNCmVuZHN0cmVhbQ1lbmRvYmoNNTQy
IDAgb2JqPDwvTGVuZ3RoIDc5L1dpZHRoIDI2L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9D
b2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQqBl+tR
bNdTbdNQbM9QactOaMhPactEVa4nQGgEMRULVx0OaScNZSMMZyUHTRUJOCcpPnI8R5g9TJg4SZI2
SYsoT4QzRYc0QoIwQH0yQXwKDQplbmRzdHJlYW0NZW5kb2JqDTU0MyAwIG9iajw8L0xlbmd0aCAz
NC9XaWR0aCAxMS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIv
VHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KOTk5XV1dbm5ua2tra2trbGxsa2tr
a2tra2trampqdnZ2Cg0KZW5kc3RyZWFtDWVuZG9iag01NDQgMCBvYmo8PC9MZW5ndGggMzcvRmls
dGVyL0ZsYXRlRGVjb2RlL1dpZHRoIDIyL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xv
clNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpIiUpPT4+J
iUlJSckGg5ycnGy8AFlBVlZWdXU1QIABAIrhG3wKDQplbmRzdHJlYW0NZW5kb2JqDTU0NSAwIG9i
ajw8L0xlbmd0aCA1MS9GaWx0ZXIvRmxhdGVEZWNvZGUvV2lkdGggNDYvSGVpZ2h0IDEvQml0c1Bl
ckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdl
Pj5zdHJlYW0NCkiJCgsDgfj4+BwwyCYFZGZmtrS0JCcnGxsbm5ubR0ZG5uXlkWQCHOTn5wMEGAAG
FTfbCg0KZW5kc3RyZWFtDWVuZG9iag01NDYgMCBvYmo8PC9MZW5ndGggODIvV2lkdGggMjcvSGVp
Z2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9T
dWJ0eXBlL0ltYWdlPj5zdHJlYW0NCoGX61Fs11Nt01Brz1Bpy1BqzEtfwypAdAdGGwSAFACIAQCA
AAB/AAB/AACDAACFAgJtDA49Ky4/eTtKmDhIjilQhDFGhzRCgzFAfjBAeTI/fAoNCmVuZHN0cmVh
bQ1lbmRvYmoNNTQ3IDAgb2JqPDwvTGVuZ3RoIDM0L1dpZHRoIDExL0hlaWdodCAxL0JpdHNQZXJD
b21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+
c3RyZWFtDQo5OTlWVlZkZGRiYmJiYmJiYmJiYmJiYmJiYmJhYWFubm4KDQplbmRzdHJlYW0NZW5k
b2JqDTU0OCAwIG9iajw8L0xlbmd0aCAyOS9GaWx0ZXIvRmxhdGVEZWNvZGUvV2lkdGggMjMvSGVp
Z2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9T
dWJ0eXBlL0ltYWdlPj5zdHJlYW0NCkiJysjIiI6OTkhISCILxMfHNzQ0AAQYAJt2GrMKDQplbmRz
dHJlYW0NZW5kb2JqDTU0OSAwIG9iajw8L0xlbmd0aCA0OC9GaWx0ZXIvRmxhdGVEZWNvZGUvV2lk
dGggNDYvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUv
WE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCkiJCgwEgaioqOTk5CQSQTIYODs7m5mZmZub
BwcHp6SkkGoIBKSlpQEEGACy0zLjCg0KZW5kc3RyZWFtDWVuZG9iag01NTAgMCBvYmo8PC9MZW5n
dGggODIvV2lkdGggMjcvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUg
MCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCn6V6VFs11Jt01Brz1BpzFFp
zjFDhAdQIQGGCQCCAAB/AgCJEACgPQCgQgB6AACBAACGAAJ7BQ5FLDM8gzJPjCxLhTZDhTJBgDBA
ejA+eDA+dwoNCmVuZHN0cmVhbQ1lbmRvYmoNNTUxIDAgb2JqPDwvTGVuZ3RoIDM0L1dpZHRoIDEx
L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmpl
Y3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQo5OTlSUlJeXl5cXFxcXFxcXFxcXFxcXFxcXFxbW1to
aGgKDQplbmRzdHJlYW0NZW5kb2JqDTU1MiAwIG9iajw8L0xlbmd0aCAyOS9GaWx0ZXIvRmxhdGVE
ZWNvZGUvV2lkdGggMjMvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUg
MCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCkiJSkpKio6Ojo2NjSELREVF
5eXlAQQYAGljGQ8KDQplbmRzdHJlYW0NZW5kb2JqDTU1MyAwIG9iajw8L0xlbmd0aCA1MC9GaWx0
ZXIvRmxhdGVEZWNvZGUvV2lkdGggNDYvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9y
U3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCkiJ8vf39/Pz
CwkJiY2NjSEdxMXF+fj4mJubm5mZeXl5AblkGAIE8fHxAAEGAPC9MAEKDQplbmRzdHJlYW0NZW5k
b2JqDTU1NCAwIG9iajw8L0xlbmd0aCA4NS9XaWR0aCAyOC9IZWlnaHQgMS9CaXRzUGVyQ29tcG9u
ZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVh
bQ0KfZXpUWzXU23TUGvQUWvOTV/BG0FUAHgPAIgAAH8AAIYKALt5AN+9APnyAL5/AIURAH8AAIIA
AIYAA2EMIEBbLkqLNUOGMkGAMEB8MD95Ljx1Lz5vCg0KZW5kc3RyZWFtDWVuZG9iag01NTUgMCBv
Ymo8PC9MZW5ndGggMzQvV2lkdGggMTEvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9y
U3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCjk5OVNTU19f
X11dXV1dXV1dXV1dXV1dXV1dXVxcXGlpaQoNCmVuZHN0cmVhbQ1lbmRvYmoNNTU2IDAgb2JqPDwv
TGVuZ3RoIDM2L0ZpbHRlci9GbGF0ZURlY29kZS9XaWR0aCAyMy9IZWlnaHQgMS9CaXRzUGVyQ29t
cG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0
cmVhbQ0KSIlKTU2NiIiIiYmJi4uLxQZwiUNAVFRUTU0NQIABAHFDGXIKDQplbmRzdHJlYW0NZW5k
b2JqDTU1NyAwIG9iajw8L0xlbmd0aCA1Mi9GaWx0ZXIvRmxhdGVEZWNvZGUvV2lkdGggNDYvSGVp
Z2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9T
dWJ0eXBlL0ltYWdlPj5zdHJlYW0NCkiJCgoK8vLyCgoKiouLi8UGcIlDQHx8fGhoqIWFhZmZGdAc
IJcMQ4AgISEBIMAAE9AwkQoNCmVuZHN0cmVhbQ1lbmRvYmoNNTU4IDAgb2JqPDwvTGVuZ3RoIDg4
L1dpZHRoIDI5L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9U
eXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQp/lulRbddTbdNQa89SbNJEUaULcngA
oT0AfgAAfgAAsmMA69YA//8A//8A//8A6NYAljMAfAAAgQAAhQAAeAARRjk0QIg0Q4MwQH0wQHku
PHYrO3EwPnIKDQplbmRzdHJlYW0NZW5kb2JqDTU1OSAwIG9iajw8L0xlbmd0aCA1My9GaWx0ZXIv
RmxhdGVEZWNvZGUvV2lkdGggNDYvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3Bh
Y2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCkiJCggI8PDwCAkJ
iYuLi8UGcIlDQHx8fHBwsLm5uZmZmZeXF5BLhiFAkJCQABBgAA4SMIIKDQplbmRzdHJlYW0NZW5k
b2JqDTU2MCAwIG9iajw8L0xlbmd0aCAyNi9GaWx0ZXIvRmxhdGVEZWNvZGUvV2lkdGggMjMvSGVp
Z2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9T
dWJ0eXBlL0ltYWdlPj5zdHJlYW0NCkiJSk1NDQsLi4mJiSUXJCYmAgQYAG4uGR4KDQplbmRzdHJl
YW0NZW5kb2JqDTU2MSAwIG9iajw8L0xlbmd0aCA5MS9XaWR0aCAzMC9IZWlnaHQgMS9CaXRzUGVy
Q29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+
PnN0cmVhbQ0KfpXpUWzXU23TUGzPU2vRPEONCZWmANenAH4AAHoAAKRNAP//AP//AP//AP//AP//
APDhAJxAAIIGAIAAAIIAAIEADFUiMT58MUCBMEB5Lz14LDxxKzhvMD5vCg0KZW5kc3RyZWFtDWVu
ZG9iag01NjIgMCBvYmo8PC9MZW5ndGggNTQvRmlsdGVyL0ZsYXRlRGVjb2RlL1dpZHRoIDQ2L0hl
aWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3Qv
U3VidHlwZS9JbWFnZT4+c3RyZWFtDQpIifLz83NzcwsJCYmPj4/FBuJgAKssUFdwcLC5ubmZmZmX
lxceQ7CKw0FCQgJAgAEAC40wfwoNCmVuZHN0cmVhbQ1lbmRvYmoNNTYzIDAgb2JqPDwvTGVuZ3Ro
IDMxL0ZpbHRlci9GbGF0ZURlY29kZS9XaWR0aCAyMy9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50
IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0K
SIkKDQ0NCwuLxQ3iYACrbExMTGZmJkCAAQBjaRkPCg0KZW5kc3RyZWFtDWVuZG9iag01NjQgMCBv
Ymo8PC9MZW5ndGggOTEvV2lkdGggMzAvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9y
U3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCn6V6FFs11Nt
01Bs0VFkxyJOdwDe4QDfyQCABwB4AAC/hwD//wD//wD//wD//wD//wD//wDdvwCHEACGCQCAAACG
AAFsBSM2XTJAgDA+eS08cyw6cSg3ajA9bgoNCmVuZHN0cmVhbQ1lbmRvYmoNNTY1IDAgb2JqPDwv
TGVuZ3RoIDYxL0ZpbHRlci9GbGF0ZURlY29kZS9XaWR0aCA0Ni9IZWlnaHQgMS9CaXRzUGVyQ29t
cG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0
cmVhbQ0KSIny9vZ2dnYOCQmJj4+PxQbi4uKAsuHh4UAGpixQV3BwsLm5uZmZmZeXFx5DsIrDQUJC
AkCAAQDvNDA9Cg0KZW5kc3RyZWFtDWVuZG9iag01NjYgMCBvYmo8PC9MZW5ndGggNDIvRmlsdGVy
L0ZsYXRlRGVjb2RlL1dpZHRoIDI0L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNw
YWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpIiUpISPD29o6K
iorFBmJiYuLi4iIjIwMDA4EMXGoSExMBAgwApzoZzwoNCmVuZHN0cmVhbQ1lbmRvYmoNNTY3IDAg
b2JqPDwvTGVuZ3RoIDk0L1dpZHRoIDMxL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xv
clNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQp9lehRbNdS
bdJQbNFRYMMbaYUA7+kA//8AyZoAhxAAyJEA//8A//8A//8A//8A//8A//8A//8AzZ0AsGEAjRoA
fwAAhAAAdwEfRlMyPH8uPHQsOnEqOG0nNmkwPG0KDQplbmRzdHJlYW0NZW5kb2JqDTU2OCAwIG9i
ajw8L0xlbmd0aCA3L1dpZHRoIDIvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3Bh
Y2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NClBQUFNTTgoNCmVu
ZHN0cmVhbQ1lbmRvYmoNNTY5IDAgb2JqPDwvTGVuZ3RoIDM3L1dpZHRoIDEyL0hlaWdodCAxL0Jp
dHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9J
bWFnZT4+c3RyZWFtDQpdXV1ISEhaWlpeXl5dXV1eXl5eXl5dXV1dXV1dXV1aWlp7e3sKDQplbmRz
dHJlYW0NZW5kb2JqDTU3MCAwIG9iajw8L0xlbmd0aCAyOC9XaWR0aCA5L0hlaWdodCAxL0JpdHNQ
ZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFn
ZT4+c3RyZWFtDQpeXl5dXV1dXV1dXV1dXV1dXV1dXV1dXV1gYGAKDQplbmRzdHJlYW0NZW5kb2Jq
DTU3MSAwIG9iajw8L0xlbmd0aCA2Mi9GaWx0ZXIvRmxhdGVEZWNvZGUvV2lkdGggNDcvSGVpZ2h0
IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0
eXBlL0ltYWdlPj5zdHJlYW0NCkiJioqKsrOz8/T0jMUB4uLivL29nZycIiMjgWxMBfHx8UDtZmZm
5ubmISEhQC4uo/CDhIQEgAADAFfjMOIKDQplbmRzdHJlYW0NZW5kb2JqDTU3MiAwIG9iajw8L0xl
bmd0aCA5Ny9XaWR0aCAzMi9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAx
NSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KfpXpUWzXU23TUW3SUF2/
HHGMAPv0AP//AP//AM2fAOLKAP//AP//AP//AP//AP//AP//AP//AP/+APbuAL19AHoAAIAAAIMA
AHsBHEZQMTp8LDtxKzhuKDhpKDRmLTppCg0KZW5kc3RyZWFtDWVuZG9iag01NzMgMCBvYmo8PC9M
ZW5ndGggMzQvV2lkdGggMTEvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2Ug
MTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCk5OTk1NTV9fX11dXV1d
XV1dXV1dXV1dXV1dXV1dXWBgYAoNCmVuZHN0cmVhbQ1lbmRvYmoNNTc0IDAgb2JqPDwvTGVuZ3Ro
IDM3L1dpZHRoIDEyL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAg
Ui9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpcXFxGRkZbW1teXl5dXV1dXV1d
XV1dXV1dXV1dXV1dXV1hYWEKDQplbmRzdHJlYW0NZW5kb2JqDTU3NSAwIG9iajw8L0xlbmd0aCAz
Ny9XaWR0aCAxMi9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIv
VHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KTExMPj4+SEhIXV1dXV1dXl5eXl5e
XV1dXV1dXV1dXV1dXl5eCg0KZW5kc3RyZWFtDWVuZG9iag01NzYgMCBvYmo8PC9MZW5ndGggNDgv
RmlsdGVyL0ZsYXRlRGVjb2RlL1dpZHRoIDM1L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9D
b2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpIifL0
9LSzswsPD4+Li4vFAPHx8X5+fhYWFpaWlhEREVjVEAMSEhIAAgwAXR0keQoNCmVuZHN0cmVhbQ1l
bmRvYmoNNTc3IDAgb2JqPDwvTGVuZ3RoIDEwMC9XaWR0aCAzMy9IZWlnaHQgMS9CaXRzUGVyQ29t
cG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0
cmVhbQ0Kf5bqUWzXUm3TUW3ST1y/G2+OAPjzAP//AP//AP7+APjxAPz6AP//AP//AP//AP//AP//
AP//AP//AP//AP79AKhTAH8BAH8AAIIAAIAAHFFILTl3KThvJzdpKDVoJzNhJzVnCg0KZW5kc3Ry
ZWFtDWVuZG9iag01NzggMCBvYmo8PC9MZW5ndGggMzcvV2lkdGggMTIvSGVpZ2h0IDEvQml0c1Bl
ckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdl
Pj5zdHJlYW0NCk1NTUFBQVtbW15eXl1dXV1dXV1dXV1dXV1dXV1dXV1dXWJiYgoNCmVuZHN0cmVh
bQ1lbmRvYmoNNTc5IDAgb2JqPDwvTGVuZ3RoIDM3L1dpZHRoIDEyL0hlaWdodCAxL0JpdHNQZXJD
b21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+
c3RyZWFtDQpbW1tERERcXFxeXl5dXV1dXV1dXV1dXV1dXV1dXV1dXV1hYWEKDQplbmRzdHJlYW0N
ZW5kb2JqDTU4MCAwIG9iajw8L0xlbmd0aCAzNy9XaWR0aCAxMi9IZWlnaHQgMS9CaXRzUGVyQ29t
cG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0
cmVhbQ0KTExMPDw8TU1NX19fXV1dXl5eXl5eXV1dXV1dXV1dXV1dYGBgCg0KZW5kc3RyZWFtDWVu
ZG9iag01ODEgMCBvYmo8PC9MZW5ndGggMzQvV2lkdGggMTEvSGVpZ2h0IDEvQml0c1BlckNvbXBv
bmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJl
YW0NCktLSzo6OlBQUF5eXl1dXV1dXV1dXV1dXV1dXV1dXWBgYAoNCmVuZHN0cmVhbQ1lbmRvYmoN
NTgyIDAgb2JqPDwvTGVuZ3RoIDI5L0ZpbHRlci9GbGF0ZURlY29kZS9XaWR0aCAyMy9IZWlnaHQg
MS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5
cGUvSW1hZ2U+PnN0cmVhbQ0KSImKiIiwtLQMDQ2Nj4+PJQskJCQABBgASgEYjgoNCmVuZHN0cmVh
bQ1lbmRvYmoNNTgzIDAgb2JqPDwvTGVuZ3RoIDEwMC9XaWR0aCAzMy9IZWlnaHQgMS9CaXRzUGVy
Q29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+
PnN0cmVhbQ0Kf5frUWzWUm3TUm3TSVawEpCnAP//AP/+APr4AOzaALZuAM+fAP//AP//AP//AP//
AP//AP//AP//AP//AP//ANi5AL2GAJYpAH4AAIUAEF4sMDh1LjxsJjRmKDRkJTFhJzJfCg0KZW5k
c3RyZWFtDWVuZG9iag01ODQgMCBvYmo8PC9MZW5ndGggMzcvV2lkdGggMTIvSGVpZ2h0IDEvQml0
c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0lt
YWdlPj5zdHJlYW0NCk5OTjo6OlRUVF9fX11dXV1dXV1dXV1dXV1dXV1dXV1dXWBgYAoNCmVuZHN0
cmVhbQ1lbmRvYmoNNTg1IDAgb2JqPDwvTGVuZ3RoIDM3L1dpZHRoIDEyL0hlaWdodCAxL0JpdHNQ
ZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFn
ZT4+c3RyZWFtDQpaWlpCQkJcXFxdXV1dXV1eXl5eXl5dXV1dXV1dXV1ZWVl/f38KDQplbmRzdHJl
YW0NZW5kb2JqDTU4NiAwIG9iajw8L0xlbmd0aCAzNy9XaWR0aCAxMi9IZWlnaHQgMS9CaXRzUGVy
Q29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+
PnN0cmVhbQ0KTExMOzs7TU1NX19fXV1dXl5eXl5eXV1dXV1dXV1dXFxcaGhoCg0KZW5kc3RyZWFt
DWVuZG9iag01ODcgMCBvYmo8PC9MZW5ndGggMzcvV2lkdGggMTIvSGVpZ2h0IDEvQml0c1BlckNv
bXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5z
dHJlYW0NCklJSTc3N0lJSV9fX15eXl1dXV1dXV1dXV1dXV1dXV1dXWFhYQoNCmVuZHN0cmVhbQ1l
bmRvYmoNNTg4IDAgb2JqPDwvTGVuZ3RoIDQxL0ZpbHRlci9GbGF0ZURlY29kZS9XaWR0aCAyMi9I
ZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0
L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KSIkKCwsLDg5OTU1NSkqKj49PSEgAkrG4AVA2GQmkpaUB
BBgAJz8YbQoNCmVuZHN0cmVhbQ1lbmRvYmoNNTg5IDAgb2JqPDwvTGVuZ3RoIDEwMy9XaWR0aCAz
NC9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2Jq
ZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0Kf5frUWzXU23TUm3UR1atCZ6gAP//AP//AN/GAMOP
AIIKAIMMAN27AP//AP//AP//AP//AP//AP//AP//AP//AP//AP//AP38AKVMAHwAAIQAEFcrWFuG
V2CCLDdkJDFhJDBdJjFbCg0KZW5kc3RyZWFtDWVuZG9iag01OTAgMCBvYmo8PC9MZW5ndGggMzcv
V2lkdGggMTIvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5
cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCktLSzk5OVNTU19fX11dXV1dXV1dXV1d
XV1dXV1dXV1dXWBgYAoNCmVuZHN0cmVhbQ1lbmRvYmoNNTkxIDAgb2JqPDwvTGVuZ3RoIDM3L1dp
ZHRoIDEyL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBl
L1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpaWlpBQUFbW1teXl5dXV1dXV1dXV1dXV1d
XV1dXV1cXFxpaWkKDQplbmRzdHJlYW0NZW5kb2JqDTU5MiAwIG9iajw8L0xlbmd0aCAzNy9XaWR0
aCAxMi9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9Y
T2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KTExMOTk5SkpKXl5eXl5eXV1dXV1dXV1dXV1d
XV1dXV1dYGBgCg0KZW5kc3RyZWFtDWVuZG9iag01OTMgMCBvYmo8PC9MZW5ndGggMzcvV2lkdGgg
MTIvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9i
amVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCkVFRTU1NUlJSV9fX15eXl1dXV1dXV1dXV1dXV1d
XV1dXWBgYAoNCmVuZHN0cmVhbQ1lbmRvYmoNNTk0IDAgb2JqPDwvTGVuZ3RoIDY0L1dpZHRoIDIx
L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmpl
Y3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQp7e3uNjY2IiIhYWFhRUVFTU1NbW1tdXV1dXV1dXV1d
XV1dXV1dXV1dXV1bW1ttbW2MjIyMjIyLi4uLi4uNjY0KDQplbmRzdHJlYW0NZW5kb2JqDTU5NSAw
IG9iajw8L0xlbmd0aCAxMDYvV2lkdGggMzUvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0Nv
bG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCn+W6lFs
1lNt01Jt1EhZsAqdnAD//wD//wD89wCqVACHDwB+AAB9AQDVrQD//wD//wD//wD//wD//wD//wD/
/wD//wD//wDv5gDVsQCUJwB+AACCAB1eNX19ooGFlj1FaSEsXiQwWScwWgoNCmVuZHN0cmVhbQ1l
bmRvYmoNNTk2IDAgb2JqPDwvTGVuZ3RoIDM0L1dpZHRoIDExL0hlaWdodCAxL0JpdHNQZXJDb21w
b25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3Ry
ZWFtDQo5OTlUVFRgYGBeXl5eXl5eXl5eXl5eXl5eXl5dXV1paWkKDQplbmRzdHJlYW0NZW5kb2Jq
DTU5NyAwIG9iajw8L0xlbmd0aCAzNy9XaWR0aCAxMi9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50
IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0K
WlpaQEBAXFxcX19fXl5eXl5eXl5eXl5eXl5eXl5eW1tbgYGBCg0KZW5kc3RyZWFtDWVuZG9iag01
OTggMCBvYmo8PC9MZW5ndGggMzcvV2lkdGggMTIvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4
L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCktL
Szg4OFRUVGBgYF5eXl5eXl5eXl5eXl5eXl5eXl5eXmFhYQoNCmVuZHN0cmVhbQ1lbmRvYmoNNTk5
IDAgb2JqPDwvTGVuZ3RoIDM3L1dpZHRoIDEyL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9D
b2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpLS0s5
OTlKSkpfX19eXl5eXl5eXl5eXl5eXl5eXl5eXl5hYWEKDQplbmRzdHJlYW0NZW5kb2JqDTYwMCAw
IG9iajw8L0xlbmd0aCAzNy9XaWR0aCAxMi9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29s
b3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KRUVFNTU1
SEhIX19fXl5eXl5eXl5eXl5eXl5eXl5eXl5eYGBgCg0KZW5kc3RyZWFtDWVuZG9iag02MDEgMCBv
Ymo8PC9MZW5ndGggNDAvV2lkdGggMTMvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9y
U3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCj4+PjU1NTY2
NldXV2BgYF5eXl5eXl5eXl5eXl5eXl5eXl1dXW1tbQoNCmVuZHN0cmVhbQ1lbmRvYmoNNjAyIDAg
b2JqPDwvTGVuZ3RoIDEwOS9XaWR0aCAzNi9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29s
b3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KfZToUWzX
Um3SUmzSSly4DZqdAP//AP//AP//AOLHAIILAH8AAH0AAJguAPnyAP//AP//AP//AP//AP//AP//
AP//AP//AP//ALR1AJInAIICAIEAAIMAGFg9T1OEeoOcRlt4ICxXIi1YJC9ZCg0KZW5kc3RyZWFt
DWVuZG9iag02MDMgMCBvYmo8PC9MZW5ndGggMzQvV2lkdGggMTEvSGVpZ2h0IDEvQml0c1BlckNv
bXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5z
dHJlYW0NCjk5OVdXV2VlZWNjY2NjY2NjY2NjY2NjY2NjY2JiYm5ubgoNCmVuZHN0cmVhbQ1lbmRv
YmoNNjA0IDAgb2JqPDwvTGVuZ3RoIDM3L1dpZHRoIDEyL0hlaWdodCAxL0JpdHNQZXJDb21wb25l
bnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFt
DQpLS0tCQkJhYWFkZGRjY2NjY2NjY2NjY2NjY2NjY2NgYGCEhIQKDQplbmRzdHJlYW0NZW5kb2Jq
DTYwNSAwIG9iajw8L0xlbmd0aCAzNy9XaWR0aCAxMi9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50
IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0K
SkpKNzc3WlpaZWVlY2NjY2NjY2NjY2NjY2NjY2NjYGBge3t7Cg0KZW5kc3RyZWFtDWVuZG9iag02
MDYgMCBvYmo8PC9MZW5ndGggMzcvV2lkdGggMTIvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4
L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCktL
Szg4OEtLS2VlZWNjY2NjY2NjY2NjY2NjY2NjY2NjY2ZmZgoNCmVuZHN0cmVhbQ1lbmRvYmoNNjA3
IDAgb2JqPDwvTGVuZ3RoIDM3L1dpZHRoIDEyL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9D
b2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpFRUU0
NDRJSUllZWVjY2NjY2NjY2NjY2NjY2NjY2NjY2NlZWUKDQplbmRzdHJlYW0NZW5kb2JqDTYwOCAw
IG9iajw8L0xlbmd0aCA0MC9XaWR0aCAxMy9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29s
b3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KQEBANzc3
ODg4W1tbZWVlY2NjY2NjY2NjY2NjY2NjY2NjYmJicHBwCg0KZW5kc3RyZWFtDWVuZG9iag02MDkg
MCBvYmo8PC9MZW5ndGggMTA5L1dpZHRoIDM2L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9D
b2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQp9lehR
bddTbdNRbdJMWLYRma4A//8A//8A//8A//8AsWUAewAAfgAAihYA7NgA//8A//8A//8A//8A//8A
//8A//8A//8A7t4AkCMAegAAgQAAfwAAhQANWykmLmpcbZFUZHwgK1YgK1YkL1cKDQplbmRzdHJl
YW0NZW5kb2JqDTYxMCAwIG9iajw8L0xlbmd0aCAzNC9XaWR0aCAxMS9IZWlnaHQgMS9CaXRzUGVy
Q29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+
PnN0cmVhbQ0KOTk5WlpaaWlpZ2dnZ2dnZ2dnZ2dnZ2dnZ2dnZmZmcnJyCg0KZW5kc3RyZWFtDWVu
ZG9iag02MTEgMCBvYmo8PC9MZW5ndGggMzcvV2lkdGggMTIvSGVpZ2h0IDEvQml0c1BlckNvbXBv
bmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJl
YW0NCltbWzk5OVtbW2lpaWdnZ2hoaGhoaGdnZ2dnZ2dnZ2RkZIWFhQoNCmVuZHN0cmVhbQ1lbmRv
YmoNNjEyIDAgb2JqPDwvTGVuZ3RoIDM3L1dpZHRoIDEyL0hlaWdodCAxL0JpdHNQZXJDb21wb25l
bnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFt
DQpKSko2NjZcXFxpaWlnZ2doaGhoaGhnZ2dnZ2dnZ2dmZmZra2sKDQplbmRzdHJlYW0NZW5kb2Jq
DTYxMyAwIG9iajw8L0xlbmd0aCAzNy9XaWR0aCAxMi9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50
IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0K
TExMNjY2TU1NaWlpaGhoZ2dnZ2dnZ2dnZ2dnZ2dnZ2dnampqCg0KZW5kc3RyZWFtDWVuZG9iag02
MTQgMCBvYmo8PC9MZW5ndGggMzcvV2lkdGggMTIvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4
L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCkVF
RTQ0NEtLS2lpaWhoaGdnZ2dnZ2dnZ2dnZ2dnZ2dnZ2pqagoNCmVuZHN0cmVhbQ1lbmRvYmoNNjE1
IDAgb2JqPDwvTGVuZ3RoIDQwL1dpZHRoIDEzL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9D
b2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpAQEA3
Nzc4ODheXl5paWlnZ2dnZ2dnZ2dnZ2dnZ2dnZ2dmZmZ0dHQKDQplbmRzdHJlYW0NZW5kb2JqDTYx
NiAwIG9iajw8L0xlbmd0aCAxMTIvV2lkdGggMzcvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4
L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCn2V
6FFs11Nt01Fs0U1euyCIpQD//gD//wD//wD//wD27gCPIwB9AAB8AACrXQDevwD//wD//wD//wD/
/wD//wD//wD//wD//wClTQB6AAB8AACMGQCJEACEABZXNyIpY1hghVheeR0pVR8qUyMsUwoNCmVu
ZHN0cmVhbQ1lbmRvYmoNNjE3IDAgb2JqPDwvTGVuZ3RoIDM0L1dpZHRoIDExL0hlaWdodCAxL0Jp
dHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9J
bWFnZT4+c3RyZWFtDQo5OTldXV1ubm5sbGxsbGxsbGxsbGxsbGxsbGxra2t3d3cKDQplbmRzdHJl
YW0NZW5kb2JqDTYxOCAwIG9iajw8L0xlbmd0aCAzNy9XaWR0aCAxMi9IZWlnaHQgMS9CaXRzUGVy
Q29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+
PnN0cmVhbQ0KXV1dODg4X19fbm5ubGxsbGxsbGxsbGxsbGxsbGxsaWlpiIiICg0KZW5kc3RyZWFt
DWVuZG9iag02MTkgMCBvYmo8PC9MZW5ndGggMzcvV2lkdGggMTIvSGVpZ2h0IDEvQml0c1BlckNv
bXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5z
dHJlYW0NCkpKSjY2Nl9fX25ubmxsbGxsbGxsbGxsbGxsbGxsbGxsbG5ubgoNCmVuZHN0cmVhbQ1l
bmRvYmoNNjIwIDAgb2JqPDwvTGVuZ3RoIDM3L1dpZHRoIDEyL0hlaWdodCAxL0JpdHNQZXJDb21w
b25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3Ry
ZWFtDQpMTEw0NDROTk5ubm5sbGxsbGxsbGxsbGxsbGxsbGxra2tvb28KDQplbmRzdHJlYW0NZW5k
b2JqDTYyMSAwIG9iajw8L0xlbmd0aCAzNy9XaWR0aCAxMi9IZWlnaHQgMS9CaXRzUGVyQ29tcG9u
ZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVh
bQ0KRUVFNDQ0TU1Nbm5ubGxsbGxsbGxsbGxsbGxsbGxsa2trbm5uCg0KZW5kc3RyZWFtDWVuZG9i
ag02MjIgMCBvYmo8PC9MZW5ndGggNDAvV2lkdGggMTMvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVu
dCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0N
CkBAQDc3Nzg4OGJiYm5ubmxsbGxsbGxsbGxsbGxsbGxsbGtra3l5eQoNCmVuZHN0cmVhbQ1lbmRv
YmoNNjIzIDAgb2JqPDwvTGVuZ3RoIDExNS9XaWR0aCAzOC9IZWlnaHQgMS9CaXRzUGVyQ29tcG9u
ZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVh
bQ0KfpXoUWzXU23TUWzRUF3AHn2aAP/7AP//AP//AP//AP//AM2cAH0AAH4AAI0eAK5dALBqAPr9
AP//AP//AP//AP//AP//AP//AOrUAIcQAJo1AJcwAMSJAIsUAIIAF1M9IShgWGB/SlR2HChRHyhN
JC1QCg0KZW5kc3RyZWFtDWVuZG9iag02MjQgMCBvYmo8PC9MZW5ndGggMzQvV2lkdGggMTEvSGVp
Z2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9T
dWJ0eXBlL0ltYWdlPj5zdHJlYW0NCjk5OV9fX29vb21tbW1tbW1tbW1tbW1tbW1tbWxsbHh4eAoN
CmVuZHN0cmVhbQ1lbmRvYmoNNjI1IDAgb2JqPDwvTGVuZ3RoIDM3L1dpZHRoIDEyL0hlaWdodCAx
L0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlw
ZS9JbWFnZT4+c3RyZWFtDQpdXV04ODhfX19vb29tbW1tbW1tbW1tbW1tbW1tbW1qamqKiooKDQpl
bmRzdHJlYW0NZW5kb2JqDTYyNiAwIG9iajw8L0xlbmd0aCAzNy9XaWR0aCAxMi9IZWlnaHQgMS9C
aXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUv
SW1hZ2U+PnN0cmVhbQ0KSkpKNjY2YWFhb29vbW1tbW1tbW1tbW1tbW1tbW1tbGxsb29vCg0KZW5k
c3RyZWFtDWVuZG9iag02MjcgMCBvYmo8PC9MZW5ndGggMzcvV2lkdGggMTIvSGVpZ2h0IDEvQml0
c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0lt
YWdlPj5zdHJlYW0NCkxMTDMzM01NTW9vb25ubm1tbW1tbW1tbW1tbW1tbW1tbXBwcAoNCmVuZHN0
cmVhbQ1lbmRvYmoNNjI4IDAgb2JqPDwvTGVuZ3RoIDM3L1dpZHRoIDEyL0hlaWdodCAxL0JpdHNQ
ZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFn
ZT4+c3RyZWFtDQpFRUU0NDRNTU1vb29ubm5tbW1tbW1tbW1tbW1tbW1tbW1vb28KDQplbmRzdHJl
YW0NZW5kb2JqDTYyOSAwIG9iajw8L0xlbmd0aCA0MC9XaWR0aCAxMy9IZWlnaHQgMS9CaXRzUGVy
Q29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+
PnN0cmVhbQ0KQEBANzc3ODg4Y2Njb29vbW1tbW1tbW1tbW1tbW1tbW1tbGxsenp6Cg0KZW5kc3Ry
ZWFtDWVuZG9iag02MzAgMCBvYmo8PC9MZW5ndGggMTE4L1dpZHRoIDM5L0hlaWdodCAxL0JpdHNQ
ZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFn
ZT4+c3RyZWFtDQp9lehRbNdTbdNQbNBRYcYhc5cA9/IA//8A//8A//8A//8A//8AwowAfQAAfgAA
mC8AhQkAunwA//8A//8A/fwA9esA/v4A//8A//8Ax5AAihwA3sAAyZQAw4YAfgAAfQEaPUUiK1pc
Y3w+R2gcJU4eJ0kiLE4KDQplbmRzdHJlYW0NZW5kb2JqDTYzMSAwIG9iajw8L0xlbmd0aCAzNC9X
aWR0aCAxMS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlw
ZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KODg4YWFhc3NzcHBwcHBwcHBwcHBwcHBw
cHBwb29venp6Cg0KZW5kc3RyZWFtDWVuZG9iag02MzIgMCBvYmo8PC9MZW5ndGggMzcvV2lkdGgg
MTIvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9i
amVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCl1dXTc3N2FhYXJycnBwcHBwcHBwcHBwcHBwcHBw
cG1tbYyMjAoNCmVuZHN0cmVhbQ1lbmRvYmoNNjMzIDAgb2JqPDwvTGVuZ3RoIDM3L1dpZHRoIDEy
L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmpl
Y3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpKSko2NjZjY2NycnJwcHBwcHBwcHBwcHBwcHBwcHBv
b29ycnIKDQplbmRzdHJlYW0NZW5kb2JqDTYzNCAwIG9iajw8L0xlbmd0aCAzNy9XaWR0aCAxMi9I
ZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0
L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KS0tLMzMzTk5OcnJycHBwcHBwcHBwcHBwcHBwcHBwcHBw
c3NzCg0KZW5kc3RyZWFtDWVuZG9iag02MzUgMCBvYmo8PC9MZW5ndGggMzcvV2lkdGggMTIvSGVp
Z2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9T
dWJ0eXBlL0ltYWdlPj5zdHJlYW0NCkVFRTMzM09PT3JycnBwcHBwcHBwcHBwcHBwcHBwcHBwcHNz
cwoNCmVuZHN0cmVhbQ1lbmRvYmoNNjM2IDAgb2JqPDwvTGVuZ3RoIDQwL1dpZHRoIDEzL0hlaWdo
dCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3Vi
dHlwZS9JbWFnZT4+c3RyZWFtDQpAQEA3Nzc4ODhmZmZycnJwcHBwcHBwcHBwcHBwcHBwcHBvb299
fX0KDQplbmRzdHJlYW0NZW5kb2JqDTYzNyAwIG9iajw8L0xlbmd0aCAxMTgvV2lkdGggMzkvSGVp
Z2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9T
dWJ0eXBlL0ltYWdlPj5zdHJlYW0NCn6V6VFs11Nt01Bs0FJgxR11kgD89wD//wD//wD//wD//wD/
/wDv4ACOHQB+AACDAwB9AACYMgD69wD//wDnzgCQJwDZvAD//wD//wDUqACHDgDo0gD+/gCyYwB9
AAB9ABlCQCMpWlxkgztDZBslSRwmRyIqTAoNCmVuZHN0cmVhbQ1lbmRvYmoNNjM4IDAgb2JqPDwv
TGVuZ3RoIDM0L1dpZHRoIDExL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNl
IDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQo4ODhkZGR4eHh1dXV1
dXV2dnZ1dXV1dXV1dXV0dHSAgIAKDQplbmRzdHJlYW0NZW5kb2JqDTYzOSAwIG9iajw8L0xlbmd0
aCAzNy9XaWR0aCAxMi9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAw
IFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KW1tbPj4+cHBwdnZ2dXV1dnZ2
dnZ2dXV1dXV1dXV1cnJykJCQCg0KZW5kc3RyZWFtDWVuZG9iag02NDAgMCBvYmo8PC9MZW5ndGgg
MzcvV2lkdGggMTIvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBS
L1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCkpKSjY2NmdnZ3h4eHV1dXZ2dnZ2
dnV1dXV1dXV1dXV1dXd3dwoNCmVuZHN0cmVhbQ1lbmRvYmoNNjQxIDAgb2JqPDwvTGVuZ3RoIDM3
L1dpZHRoIDEyL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9U
eXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpLS0szMzNQUFB3d3d1dXV1dXV1dXV1
dXV1dXV1dXV1dXV4eHgKDQplbmRzdHJlYW0NZW5kb2JqDTY0MiAwIG9iajw8L0xlbmd0aCAzNy9X
aWR0aCAxMi9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlw
ZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KRERENDQ0UFBQd3d3dXV1dXV1dXV1dXV1
dXV1dXV1dXV1eHh4Cg0KZW5kc3RyZWFtDWVuZG9iag02NDMgMCBvYmo8PC9MZW5ndGggNDAvV2lk
dGggMTMvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUv
WE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCkBAQDc3Nzg4OGpqand3d3V1dXV1dXV1dXV1
dXV1dXV1dXR0dIGBgQoNCmVuZHN0cmVhbQ1lbmRvYmoNNjQ0IDAgb2JqPDwvTGVuZ3RoIDEyMS9X
aWR0aCA0MC9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlw
ZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KfZbqUWvXU23TUGvQUmXLMGGcAO7tAP//
AP//AP//AP//AP//AP//AMmVAHsAAIAAAIAAAH8AALp1AP//AP//AKNKAHwAAOfOAP//AP//AMaP
AH8CAN28APbwAJEmAH8AA3sJHztMJzBeXWR+KTFTGyZHGyRGHyhJCg0KZW5kc3RyZWFtDWVuZG9i
ag02NDUgMCBvYmo8PC9MZW5ndGggMzQvV2lkdGggMTEvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVu
dCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0N
Cjg4OGdnZ3x8fHl5eXl5eXl5eXl5eXl5eXl5eXh4eIODgwoNCmVuZHN0cmVhbQ1lbmRvYmoNNjQ2
IDAgb2JqPDwvTGVuZ3RoIDM3L1dpZHRoIDEyL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9D
b2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpZWVk+
Pj53d3d6enp5eXl6enp6enp5eXl5eXl5eXl2dnaUlJQKDQplbmRzdHJlYW0NZW5kb2JqDTY0NyAw
IG9iajw8L0xlbmd0aCAzNy9XaWR0aCAxMi9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29s
b3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KSkpKNjY2
aWlpfHx8eXl5enp6enp6eXl5eXl5eXl5eXl5e3t7Cg0KZW5kc3RyZWFtDWVuZG9iag02NDggMCBv
Ymo8PC9MZW5ndGggMzcvV2lkdGggMTIvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9y
U3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCklJSTMzM1FR
UXt7e3l5eXl5eXl5eXl5eXl5eXl5eXh4eHx8fAoNCmVuZHN0cmVhbQ1lbmRvYmoNNjQ5IDAgb2Jq
PDwvTGVuZ3RoIDM3L1dpZHRoIDEyL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNw
YWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpTU1M0NDRSUlJ8
fHx5eXl5eXl5eXl5eXl5eXl5eXl4eHh8fHwKDQplbmRzdHJlYW0NZW5kb2JqDTY1MCAwIG9iajw8
L0xlbmd0aCA0MC9XaWR0aCAxMy9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFj
ZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KQEBANzc3ODg4bGxs
fHx8eXl5eXl5eXl5eXl5eXl5eXl5eHh4hYWFCg0KZW5kc3RyZWFtDWVuZG9iag02NTEgMCBvYmo8
PC9MZW5ndGggMTI0L1dpZHRoIDQxL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNw
YWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQp/lepRbNdSbdNQ
bM9TadA2WZkA29cA//8A//8A//8A//8A//8A//8A9+4AkiUAfQAAgAAAgAAAzJsA/v0A//8A0aQA
egAAlCwA9ewA//8A//8AoUYAfgQA7+AAwoIAewAAhAALbxQiL1IyPGdUXXocJ0YcJUcbJEQcJUUK
DQplbmRzdHJlYW0NZW5kb2JqDTY1MiAwIG9iajw8L0xlbmd0aCAzNy9XaWR0aCAxMi9IZWlnaHQg
MS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5
cGUvSW1hZ2U+PnN0cmVhbQ0KSkpKNjY2bW1tgICAfX19fX19fX19fX19fX19fX19fX19gICACg0K
ZW5kc3RyZWFtDWVuZG9iag02NTMgMCBvYmo8PC9MZW5ndGggMzcvV2lkdGggMTIvSGVpZ2h0IDEv
Qml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBl
L0ltYWdlPj5zdHJlYW0NCllZWT09PXp6en5+fn19fX19fX19fX19fX19fX19fXp6epeXlwoNCmVu
ZHN0cmVhbQ1lbmRvYmoNNjU0IDAgb2JqPDwvTGVuZ3RoIDM3L1dpZHRoIDEyL0hlaWdodCAxL0Jp
dHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9J
bWFnZT4+c3RyZWFtDQpXV1cxMTFYWFiAgIB9fX19fX19fX19fX19fX19fX19fX2BgYEKDQplbmRz
dHJlYW0NZW5kb2JqDTY1NSAwIG9iajw8L0xlbmd0aCAzNC9XaWR0aCAxMS9IZWlnaHQgMS9CaXRz
UGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1h
Z2U+PnN0cmVhbQ0KTExMSkpKfn5+fn5+fX19fX19fX19fX19fX19fX19gICACg0KZW5kc3RyZWFt
DWVuZG9iag02NTYgMCBvYmo8PC9MZW5ndGggNDAvV2lkdGggMTMvSGVpZ2h0IDEvQml0c1BlckNv
bXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5z
dHJlYW0NCkBAQDc3Nzg4OHBwcICAgH19fX19fX19fX19fX19fX19fXx8fImJiQoNCmVuZHN0cmVh
bQ1lbmRvYmoNNjU3IDAgb2JqPDwvTGVuZ3RoIDEyNy9XaWR0aCA0Mi9IZWlnaHQgMS9CaXRzUGVy
Q29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+
PnN0cmVhbQ0Kf5fqUWzXU23TUGzPU2vQQValBMPEAP//AP//AP//AP//AP//AP//AP//ALh4AHsA
AIEAAHsAAKJGAP//AP//APn0AJgzAHcAAKhPAP//AP//APXtAJUsAJQqAO7gAJkxAH0AAIUADGca
HilSREtsRk9oFyFEGyRFGCJAGiJCCg0KZW5kc3RyZWFtDWVuZG9iag02NTggMCBvYmo8PC9MZW5n
dGggMzQvV2lkdGggMTEvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUg
MCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCjg4OGtra4KCgn5+fn5+fn5+
fn5+fn5+fn5+fn19fYiIiAoNCmVuZHN0cmVhbQ1lbmRvYmoNNjU5IDAgb2JqPDwvTGVuZ3RoIDM3
L1dpZHRoIDEyL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9U
eXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpZWVk8PDx7e3t/f39+fn5+fn5+fn5+
fn5+fn5+fn57e3uYmJgKDQplbmRzdHJlYW0NZW5kb2JqDTY2MCAwIG9iajw8L0xlbmd0aCAzNy9X
aWR0aCAxMi9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlw
ZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KSkpKNjY2bm5ugYGBfn5+fn5+fn5+fn5+
fn5+fn5+fn5+gYGBCg0KZW5kc3RyZWFtDWVuZG9iag02NjEgMCBvYmo8PC9MZW5ndGggMzcvV2lk
dGggMTIvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUv
WE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCkNDQzc3N2tra4KCgn5+fn5+fn5+fn5+fn5+
fn5+fn5+foGBgQoNCmVuZHN0cmVhbQ1lbmRvYmoNNjYyIDAgb2JqPDwvTGVuZ3RoIDMxL1dpZHRo
IDEwL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hP
YmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpOTk53d3d/f39+fn5+fn5+fn5+fn5+fn59fX2B
gYEKDQplbmRzdHJlYW0NZW5kb2JqDTY2MyAwIG9iajw8L0xlbmd0aCA0MC9XaWR0aCAxMy9IZWln
aHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1
YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KQEBANzc3ODg4cHBwgYGBfn5+fn5+fn5+fn5+fn5+fn5+fHx8
ioqKCg0KZW5kc3RyZWFtDWVuZG9iag02NjQgMCBvYmo8PC9MZW5ndGggMTI3L1dpZHRoIDQyL0hl
aWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3Qv
U3VidHlwZS9JbWFnZT4+c3RyZWFtDQqAlupRbNdTbdNQa89Sas9FWawHsLQA//8A//8A//8A//8A
//8A//8A//8AtXgAewAAgQAAfQAAlCgA6dQA//8A/v4AoEEAeAAAlCsA9u0A//8A//8AuXUAm0MA
38EAixYAfwAAhQAMZh8fJlNRV3U7RF8YIEIZI0MYID8ZIT0KDQplbmRzdHJlYW0NZW5kb2JqDTY2
NSAwIG9iajw8L0xlbmd0aCAzNC9XaWR0aCAxMS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgv
Q29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KODg4
bm5uhoaGgoKCgoKCgoKCgoKCgoKCgoKCgYGBjIyMCg0KZW5kc3RyZWFtDWVuZG9iag02NjYgMCBv
Ymo8PC9MZW5ndGggMzcvV2lkdGggMTIvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9y
U3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCllZWT09PX9/
f4ODg4KCgoKCgoKCgoKCgoKCgoKCgoCAgJubmwoNCmVuZHN0cmVhbQ1lbmRvYmoNNjY3IDAgb2Jq
PDwvTGVuZ3RoIDM3L1dpZHRoIDEyL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNw
YWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpKSko2NjZxcXGF
hYWCgoKCgoKCgoKCgoKCgoKCgoKCgoKFhYUKDQplbmRzdHJlYW0NZW5kb2JqDTY2OCAwIG9iajw8
L0xlbmd0aCAzNy9XaWR0aCAxMi9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFj
ZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KRUVFNzc3bm5uhoaG
goKCgoKCgoKCgoKCgoKCgoKCgoKChISECg0KZW5kc3RyZWFtDWVuZG9iag02NjkgMCBvYmo8PC9M
ZW5ndGggMzEvV2lkdGggMTAvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2Ug
MTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCn9/f4+Pj42NjY2NjY2N
jY2NjY2NjY2NjY2NjZCQkAoNCmVuZHN0cmVhbQ1lbmRvYmoNNjcwIDAgb2JqPDwvTGVuZ3RoIDQw
L1dpZHRoIDEzL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9U
eXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpAQEA3Nzc4ODh0dHSFhYWCgoKCgoKC
goKCgoKCgoKCgoKBgYGOjo4KDQplbmRzdHJlYW0NZW5kb2JqDTY3MSAwIG9iajw8L0xlbmd0aCAx
MzAvV2lkdGggNDMvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBS
L1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCn6V6VFs11Jt0lBsz1FqzE1buhCO
ngD//wD//wD//wD//wD//wD//wD//wDjxQCFCQB/AACBAAB/AACMGADq1wD//wDgwACAAQB7AADG
kAD8/wD6+wD+/ADRpQDYswCOHAB/AACBAACFABRULyQmVVJcfSUtTxgiQRghPxcgPBcfOwoNCmVu
ZHN0cmVhbQ1lbmRvYmoNNjcyIDAgb2JqPDwvTGVuZ3RoIDM0L1dpZHRoIDExL0hlaWdodCAxL0Jp
dHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9J
bWFnZT4+c3RyZWFtDQo4ODhxcXGLi4uHh4eHh4eHh4eHh4eHh4eHh4eGhoaQkJAKDQplbmRzdHJl
YW0NZW5kb2JqDTY3MyAwIG9iajw8L0xlbmd0aCAzNy9XaWR0aCAxMi9IZWlnaHQgMS9CaXRzUGVy
Q29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+
PnN0cmVhbQ0KWFhYPT09g4ODiIiIh4eHh4eHh4eHh4eHh4eHh4eHhYWFoKCgCg0KZW5kc3RyZWFt
DWVuZG9iag02NzQgMCBvYmo8PC9MZW5ndGggMzcvV2lkdGggMTIvSGVpZ2h0IDEvQml0c1BlckNv
bXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5z
dHJlYW0NCkpKSjY2NnR0dIqKioeHh4eHh4eHh4eHh4eHh4eHh4eHh4qKigoNCmVuZHN0cmVhbQ1l
bmRvYmoNNjc1IDAgb2JqPDwvTGVuZ3RoIDM3L1dpZHRoIDEyL0hlaWdodCAxL0JpdHNQZXJDb21w
b25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3Ry
ZWFtDQpFRUU6Ojp3d3eKioqHh4eHh4eHh4eHh4eHh4eHh4eEhISenp4KDQplbmRzdHJlYW0NZW5k
b2JqDTY3NiAwIG9iajw8L0xlbmd0aCAyOC9XaWR0aCA5L0hlaWdodCAxL0JpdHNQZXJDb21wb25l
bnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFt
DQq6urq4uLi4uLi4uLi4uLi4uLi4uLi4uLi5ubkKDQplbmRzdHJlYW0NZW5kb2JqDTY3NyAwIG9i
ajw8L0xlbmd0aCA0MC9XaWR0aCAxMy9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JT
cGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KQEBANzc3ODg4
eHh4ioqKh4eHh4eHh4eHh4eHh4eHh4eHhoaGkpKSCg0KZW5kc3RyZWFtDWVuZG9iag02NzggMCBv
Ymo8PC9MZW5ndGggMTExL0ZpbHRlci9GbGF0ZURlY29kZS9XaWR0aCA0NC9IZWlnaHQgMS9CaXRz
UGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1h
Z2U+PnN0cmVhbQ0KSImqnfoyMOd6cO7lgJwLAZlnApKOyRdNZfj6geH/fyxooTNDNQNDIxgBGbvK
oOJb8xnKGRimajC8vslweinDv38gwX9/GTZnQNU3ARGjjKu1kXmiZ3ClpLKThKKDhIKtqJyVqLw5
QIABAGkWNg0KDQplbmRzdHJlYW0NZW5kb2JqDTY3OSAwIG9iajw8L0xlbmd0aCAzNC9XaWR0aCAx
MS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2Jq
ZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KODg4c3NzjY2NiYmJiYmJiYmJiYmJiYmJiYmJiIiI
kpKSCg0KZW5kc3RyZWFtDWVuZG9iag02ODAgMCBvYmo8PC9MZW5ndGggMzcvV2lkdGggMTIvSGVp
Z2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9T
dWJ0eXBlL0ltYWdlPj5zdHJlYW0NClhYWD4+PoaGhoqKiomJiYmJiYmJiYmJiYmJiYmJiYeHh6Gh
oQoNCmVuZHN0cmVhbQ1lbmRvYmoNNjgxIDAgb2JqPDwvTGVuZ3RoIDM3L1dpZHRoIDEyL0hlaWdo
dCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3Vi
dHlwZS9JbWFnZT4+c3RyZWFtDQpKSko2NjZ1dXWNjY2JiYmJiYmJiYmJiYmJiYmJiYmJiYmMjIwK
DQplbmRzdHJlYW0NZW5kb2JqDTY4MiAwIG9iajw8L0xlbmd0aCAzNy9XaWR0aCAxMi9IZWlnaHQg
MS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5
cGUvSW1hZ2U+PnN0cmVhbQ0KRUVFPj4+fX19jIyMiYmJiYmJiYmJiYmJiYmJiYmJh4eHoaGhCg0K
ZW5kc3RyZWFtDWVuZG9iag02ODMgMCBvYmo8PC9MZW5ndGggNDAvV2lkdGggMTMvSGVpZ2h0IDEv
Qml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBl
L0ltYWdlPj5zdHJlYW0NCkBAQDc3Nzg4OHp6eo2NjYmJiYmJiYmJiYmJiYmJiYmJiYmJiZSUlAoN
CmVuZHN0cmVhbQ1lbmRvYmoNNjg0IDAgb2JqPDwvTGVuZ3RoIDExNi9GaWx0ZXIvRmxhdGVEZWNv
ZGUvV2lkdGggNDUvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBS
L1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCkiJqp3yIjDnelDu5YCc8wGZpwPT
ThvEzWK4f4vh/38s6MoqhmoGhkYwqmdg6BBkeH6R4dtbhg+PGVaHMVQyMOyrYljgxHB/L0LLikCo
lmYGnkpBJUNP94AiU7s4EXk7CQV7cXlrIWlTMXlDgAADABGPNtQKDQplbmRzdHJlYW0NZW5kb2Jq
DTY4NSAwIG9iajw8L0xlbmd0aCAzNC9XaWR0aCAxMS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50
IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0K
ODg4dXV1j4+Pi4uLi4uLjIyMi4uLi4uLi4uLi4uLlJSUCg0KZW5kc3RyZWFtDWVuZG9iag02ODYg
MCBvYmo8PC9MZW5ndGggMzcvV2lkdGggMTIvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0Nv
bG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NClhYWD4+
PoeHh4yMjIuLi4uLi4uLi4uLi4uLi4uLi4mJiaSkpAoNCmVuZHN0cmVhbQ1lbmRvYmoNNjg3IDAg
b2JqPDwvTGVuZ3RoIDM3L1dpZHRoIDEyL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xv
clNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpKSko2NjZ3
d3ePj4+Li4uLi4uLi4uLi4uLi4uLi4uLi4uOjo4KDQplbmRzdHJlYW0NZW5kb2JqDTY4OCAwIG9i
ajw8L0xlbmd0aCA0MC9XaWR0aCAxMy9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JT
cGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KQUFBPT09eXl5
j4+Pi4uLi4uLi4uLi4uLi4uLi4uLi4uLiYmJpaWlCg0KZW5kc3RyZWFtDWVuZG9iag02ODkgMCBv
Ymo8PC9MZW5ndGggNDAvV2lkdGggMTMvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9y
U3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCkBAQDc3Nzg4
OHt7e46OjouLi4uLi4uLi4uLi4uLi4uLi4qKipaWlgoNCmVuZHN0cmVhbQ1lbmRvYmoNNjkwIDAg
b2JqPDwvTGVuZ3RoIDEzNi9XaWR0aCA0NS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29s
b3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KfZToUWzX
U23TUGvPUGnLUWbLN1uYAdbOAP//AP//AP//AP//AP//AP//AP//AM6dAH4AAIAAAIEAAIAAAH0A
ANSqAMaNAN67ALFiAHoAALRrAJo3AOvXAP//AP//AP//AKtYAHsAAIEAAIQADHQSKDdNUll0IStJ
Fh4+GCA8FB03EhowGR40Cg0KZW5kc3RyZWFtDWVuZG9iag02OTEgMCBvYmo8PC9MZW5ndGggMzQv
V2lkdGggMTEvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5
cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCjc3N3h4eJSUlJCQkJCQkJCQkJCQkJCQ
kJCQkI+Pj5mZmQoNCmVuZHN0cmVhbQ1lbmRvYmoNNjkyIDAgb2JqPDwvTGVuZ3RoIDM3L1dpZHRo
IDEyL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hP
YmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpYWFg/Pz+MjIySkpKQkJCQkJCQkJCQkJCQkJCQ
kJCOjo6np6cKDQplbmRzdHJlYW0NZW5kb2JqDTY5MyAwIG9iajw8L0xlbmd0aCAzNy9XaWR0aCAx
Mi9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2Jq
ZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KSkpKNjY2e3t7lJSUkJCQkJCQkJCQkJCQkJCQkJCQ
kJCQk5OTCg0KZW5kc3RyZWFtDWVuZG9iag02OTQgMCBvYmo8PC9MZW5ndGggNDAvV2lkdGggMTMv
SGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVj
dC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCjs7O09PT5GRkZKSkpCQkJCQkJCQkJCQkJCQkJCQkJCQ
kI+Pj6ioqAoNCmVuZHN0cmVhbQ1lbmRvYmoNNjk1IDAgb2JqPDwvTGVuZ3RoIDQwL1dpZHRoIDEz
L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmpl
Y3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpAQEA3Nzc4ODh/f3+UlJSQkJCQkJCQkJCQkJCQkJCQ
kJCPj4+bm5sKDQplbmRzdHJlYW0NZW5kb2JqDTY5NiAwIG9iajw8L0xlbmd0aCAxMzkvV2lkdGgg
NDYvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9i
amVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCn2V6FFs11Nt0lBrz1Bpy09py0VUpgmtrQD//wD/
/wD//wD//wD//wD//wD//wDx4wCQIQB+AACBAACCAAB8AACZNwDgxQCoVgDZtwCBAwCMHgDNnwDK
lAD//wD58wDWrQDr2ACfPwB9AACBAACEAB5nJz9AX0hPZRUePhcgPBQdOREbMhEXLxceMQoNCmVu
ZHN0cmVhbQ1lbmRvYmoNNjk3IDAgb2JqPDwvTGVuZ3RoIDM0L1dpZHRoIDExL0hlaWdodCAxL0Jp
dHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9J
bWFnZT4+c3RyZWFtDQo3Nzd6enqZmZmUlJSUlJSUlJSUlJSUlJSUlJSTk5OdnZ0KDQplbmRzdHJl
YW0NZW5kb2JqDTY5OCAwIG9iajw8L0xlbmd0aCAzNy9XaWR0aCAxMi9IZWlnaHQgMS9CaXRzUGVy
Q29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+
PnN0cmVhbQ0KWFhYPz8/kJCQlpaWlZWVlJSUlJSUlZWVlJSUlJSUk5OTq6urCg0KZW5kc3RyZWFt
DWVuZG9iag02OTkgMCBvYmo8PC9MZW5ndGggMzcvV2lkdGggMTIvSGVpZ2h0IDEvQml0c1BlckNv
bXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5z
dHJlYW0NCklJSTY2Nn5+fpiYmJWVlZSUlJSUlJWVlZSUlJSUlJWVlZeXlwoNCmVuZHN0cmVhbQ1l
bmRvYmoNNzAwIDAgb2JqPDwvTGVuZ3RoIDQwL1dpZHRoIDEzL0hlaWdodCAxL0JpdHNQZXJDb21w
b25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3Ry
ZWFtDQo+Pj5UVFSXl5eUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSTk5OqqqoKDQplbmRzdHJlYW0N
ZW5kb2JqDTcwMSAwIG9iajw8L0xlbmd0aCA0MC9XaWR0aCAxMy9IZWlnaHQgMS9CaXRzUGVyQ29t
cG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0
cmVhbQ0KQEBANzc3ODg4g4ODmJiYlJSUlJSUlJSUlJSUlJSUlJSUk5OTn5+fCg0KZW5kc3RyZWFt
DWVuZG9iag03MDIgMCBvYmo8PC9MZW5ndGggMTQyL1dpZHRoIDQ3L0hlaWdodCAxL0JpdHNQZXJD
b21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+
c3RyZWFtDQp6kuhOatdSbdNQbM9QacxOaMlOWbocdpgA//sA//8A//8A//8A//8A//8A//8A8+gA
qFIAewAAgQAAgQAAgQAAfQAA06kAypsAsWYAy5gAdgAAwIUA/PoA/PkA//8A160AiRMAy5kAlSoA
fgAAgQAAgwAcTjdRUm8vNlMVHTwWHjoQGjIQFi4TGjEXHTEKDQplbmRzdHJlYW0NZW5kb2JqDTcw
MyAwIG9iajw8L0xlbmd0aCAzNC9XaWR0aCAxMS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgv
Q29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KODg4
e3t7mpqalZWVlZWVlZWVlZWVlZWVlZWVlJSUnp6eCg0KZW5kc3RyZWFtDWVuZG9iag03MDQgMCBv
Ymo8PC9MZW5ndGggMzcvV2lkdGggMTIvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9y
U3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NClhYWD8/P5GR
kZeXl5WVlZWVlZWVlZWVlZWVlZWVlZOTk6ysrAoNCmVuZHN0cmVhbQ1lbmRvYmoNNzA1IDAgb2Jq
PDwvTGVuZ3RoIDM3L1dpZHRoIDEyL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNw
YWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpJSUk2NjZ/f3+Z
mZmVlZWVlZWVlZWVlZWVlZWVlZWVlZWYmJgKDQplbmRzdHJlYW0NZW5kb2JqDTcwNiAwIG9iajw8
L0xlbmd0aCA0MC9XaWR0aCAxMy9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFj
ZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KOzs7XFxcmZmZlZWV
lZWVlZWVlZWVlZWVlZWVlZWVlZWVlJSUqqqqCg0KZW5kc3RyZWFtDWVuZG9iag03MDcgMCBvYmo8
PC9MZW5ndGggNDAvV2lkdGggMTMvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3Bh
Y2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCkBAQDc3Nzg4OISE
hJiYmJWVlZWVlZWVlZWVlZWVlZWVlZSUlKCgoAoNCmVuZHN0cmVhbQ1lbmRvYmoNNzA4IDAgb2Jq
PDwvTGVuZ3RoIDE0NS9XaWR0aCA0OC9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JT
cGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KjaPxY3zhVW/U
T2vPUGrLTWjIT2HGJ2SSAOrjAP//AP//AP//AP//AP//AP//AOviAJMxAH8AAIEAAIEAAIEAAHwA
AJk4APPoAJw+ANGpANStAJIoAPXrAP//AP//AP//ANeuAJEqAL6FAIUIAIAAAIIABHcKN0tVUFJr
GSE+Fh47EBkzGSA2OkBRRFFeMTdICg0KZW5kc3RyZWFtDWVuZG9iag03MDkgMCBvYmo8PC9MZW5n
dGggMzQvV2lkdGggMTEvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUg
MCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCjc3N39/f56enpmZmZmZmZmZ
mZmZmZmZmZmZmZiYmKKiogoNCmVuZHN0cmVhbQ1lbmRvYmoNNzEwIDAgb2JqPDwvTGVuZ3RoIDM3
L1dpZHRoIDEyL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9U
eXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpYWFhAQECUlJSbm5uZmZmZmZmZmZmZ
mZmZmZmZmZmXl5evr68KDQplbmRzdHJlYW0NZW5kb2JqDTcxMSAwIG9iajw8L0xlbmd0aCAzNy9X
aWR0aCAxMi9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlw
ZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KSkpKNTU1goKCnZ2dmZmZmZmZmZmZmZmZ
mZmZmZmZmZmZnJycCg0KZW5kc3RyZWFtDWVuZG9iag03MTIgMCBvYmo8PC9MZW5ndGggNDMvV2lk
dGggMTQvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUv
WE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCjw8PFRUVJubm5qampmZmZmZmZmZmZmZmZmZ
mZmZmZmZmZmZmZmZmaOjowoNCmVuZHN0cmVhbQ1lbmRvYmoNNzEzIDAgb2JqPDwvTGVuZ3RoIDQw
L1dpZHRoIDEzL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9U
eXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpAQEA3Nzc4ODiHh4ednZ2ZmZmZmZmZ
mZmZmZmZmZmZmZmYmJikpKQKDQplbmRzdHJlYW0NZW5kb2JqDTcxNCAwIG9iajw8L0xlbmd0aCAx
MzYvV2lkdGggNDUvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBS
L1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCsne9uTn85Cg3kpnzlBpy01nx1Fm
yjVXkwDUzgD//wD//wD//wD//wD//wD//wDlzQCGEQB+AACBAACBAACAAACCBQDChgD//wCxZQDR
qAD79wC2awD27gD//wD//wD//wDcwQDAhwC2bAB9AAB+AACfOhV5Yk9NYzpDWRMbOA4YMyIrQKeo
sAoNCmVuZHN0cmVhbQ1lbmRvYmoNNzE1IDAgb2JqPDwvTGVuZ3RoIDQvV2lkdGggMS9IZWlnaHQg
MS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5
cGUvSW1hZ2U+PnN0cmVhbQ0KrK+4Cg0KZW5kc3RyZWFtDWVuZG9iag03MTYgMCBvYmo8PC9MZW5n
dGggMzQvV2lkdGggMTEvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUg
MCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCjc3N4KCgqKiop2dnZ2dnZ2d
nZ2dnZ2dnZ2dnZ2dnaampgoNCmVuZHN0cmVhbQ1lbmRvYmoNNzE3IDAgb2JqPDwvTGVuZ3RoIDM3
L1dpZHRoIDEyL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9U
eXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpYWFhAQECZmZmenp6dnZ2dnZ2dnZ2d
nZ2dnZ2dnZ2bm5uysrIKDQplbmRzdHJlYW0NZW5kb2JqDTcxOCAwIG9iajw8L0xlbmd0aCAzNy9X
aWR0aCAxMi9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlw
ZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KSUlJNjY2hYWFoaGhnZ2dnZ2dnZ2dnZ2d
nZ2dnZ2dnJycoKCgCg0KZW5kc3RyZWFtDWVuZG9iag03MTkgMCBvYmo8PC9MZW5ndGggNDMvV2lk
dGggMTQvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUv
WE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCkVFRVdXV52dnZ+fn52dnZ2dnZ2dnZ2dnZ2d
nZ2dnZ2dnZ2dnZ2dnaSkpAoNCmVuZHN0cmVhbQ1lbmRvYmoNNzIwIDAgb2JqPDwvTGVuZ3RoIDQw
L1dpZHRoIDEzL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9U
eXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpAQEA2NjY4ODiKioqhoaGdnZ2dnZ2d
nZ2dnZ2dnZ2dnZ2cnJynp6cKDQplbmRzdHJlYW0NZW5kb2JqDTcyMSAwIG9iajw8L0xlbmd0aCA0
L1dpZHRoIDEvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5
cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCpuw+AoNCmVuZHN0cmVhbQ1lbmRvYmoN
NzIyIDAgb2JqPDwvTGVuZ3RoIDEyNy9XaWR0aCA0Mi9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50
IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0K
b4XWS2bNTmjITGbGTl6+JWSSAPTxAP//AP//AP//AP//AP//AOzbAJ48AH4AAIEAAIEAAIEAAHsA
AKJKAPv4AOPOAL59AOjSAP/+ANy3APr1AP//AP//AP//AL9/AN27ALhyAHoAAH0AANSvFrzDTVFe
PkRcExs4DBYvYWp9Cg0KZW5kc3RyZWFtDWVuZG9iag03MjMgMCBvYmo8PC9MZW5ndGggNC9XaWR0
aCAxL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hP
YmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQra3OMKDQplbmRzdHJlYW0NZW5kb2JqDTcyNCAw
IG9iajw8L0xlbmd0aCAzNC9XaWR0aCAxMS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29s
b3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KNzc3goKC
pKSknp6enp6enp6enp6enp6enp6enp6epqamCg0KZW5kc3RyZWFtDWVuZG9iag03MjUgMCBvYmo8
PC9MZW5ndGggMzcvV2lkdGggMTIvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3Bh
Y2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NClhYWEBAQJqamqCg
oJ6enp6enp6enp6enp+fn56enpycnLOzswoNCmVuZHN0cmVhbQ1lbmRvYmoNNzI2IDAgb2JqPDwv
TGVuZ3RoIDM3L1dpZHRoIDEyL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNl
IDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpJSUk2NjaGhoajo6Oe
np6enp6enp6enp6fn5+fn5+enp6hoaEKDQplbmRzdHJlYW0NZW5kb2JqDTcyNyAwIG9iajw8L0xl
bmd0aCA0My9XaWR0aCAxNC9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAx
NSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KPj4+Xl5eoaGhn5+fnp6e
np6enp6enp6enp6enp6enp6enp6enp6eoqKiCg0KZW5kc3RyZWFtDWVuZG9iag03MjggMCBvYmo8
PC9MZW5ndGggNDAvV2lkdGggMTMvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3Bh
Y2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCkBAQDY2Njg4OIuL
i6Kiop6enp6enp6enp6enp6enp6enp2dnaioqAoNCmVuZHN0cmVhbQ1lbmRvYmoNNzI5IDAgb2Jq
PDwvTGVuZ3RoIDcvV2lkdGggMi9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFj
ZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KnK/yXorcCg0KZW5k
c3RyZWFtDWVuZG9iag03MzAgMCBvYmo8PC9MZW5ndGggMTI0L1dpZHRoIDQxL0hlaWdodCAxL0Jp
dHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9J
bWFnZT4+c3RyZWFtDQpvg9RMZstOaMdMZsRLWbUeeJ4A/fsA//8A//8A//8A//8A9/IAnj4AewAA
gQAAgQAAgQAAfwAAhAcA27gA9usAqV4A2rkA/v4A//8A//8A//8A//8A//8A//8A17MA8eYAsmQA
dwAAoEIA//8LrrBWUmMyNkwKEy84QlcKDQplbmRzdHJlYW0NZW5kb2JqDTczMSAwIG9iajw8L0xl
bmd0aCA0L1dpZHRoIDEvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUg
MCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCuzs7woNCmVuZHN0cmVhbQ1l
bmRvYmoNNzMyIDAgb2JqPDwvTGVuZ3RoIDM0L1dpZHRoIDExL0hlaWdodCAxL0JpdHNQZXJDb21w
b25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3Ry
ZWFtDQo3NzeFhYWnp6eioqKioqKioqKioqKioqKioqKhoaGqqqoKDQplbmRzdHJlYW0NZW5kb2Jq
DTczMyAwIG9iajw8L0xlbmd0aCAzNy9XaWR0aCAxMi9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50
IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0K
WFhYQUFBnZ2dpKSkoqKioqKioqKioqKio6OjoqKioaGht7e3Cg0KZW5kc3RyZWFtDWVuZG9iag03
MzQgMCBvYmo8PC9MZW5ndGggMzcvV2lkdGggMTIvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4
L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCkVF
RTY2NoqKiqenp6KioqKioqKioqKioqOjo6Ojo6KioqampgoNCmVuZHN0cmVhbQ1lbmRvYmoNNzM1
IDAgb2JqPDwvTGVuZ3RoIDQ2L1dpZHRoIDE1L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9D
b2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpMTExc
XFynp6ejo6OioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKnp6cKDQplbmRzdHJlYW0NZW5k
b2JqDTczNiAwIG9iajw8L0xlbmd0aCA0MC9XaWR0aCAxMy9IZWlnaHQgMS9CaXRzUGVyQ29tcG9u
ZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVh
bQ0KQEBANjY2ODg4jo6OpqamoqKioqKioqKioqKioqKioqKioaGhrKysCg0KZW5kc3RyZWFtDWVu
ZG9iag03MzcgMCBvYmo8PC9MZW5ndGggNy9XaWR0aCAyL0hlaWdodCAxL0JpdHNQZXJDb21wb25l
bnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFt
DQqLoO1cd9MKDQplbmRzdHJlYW0NZW5kb2JqDTczOCAwIG9iajw8L0xlbmd0aCA5OC9GaWx0ZXIv
RmxhdGVEZWNvZGUvV2lkdGggNDEvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3Bh
Y2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCkiJym+64p120jft
mG/aYc/wzUIdsxn+/2X4/x+Bbu9laGBnqGdgaIQhILuVm+HJSYZ/fxnm2jHc3s7w5xeKFmT09AxD
AzPDQlcQ++h8j4xwP79kbhEDE9sAgAADACrfOWgKDQplbmRzdHJlYW0NZW5kb2JqDTczOSAwIG9i
ajw8L0xlbmd0aCAzNC9XaWR0aCAxMS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JT
cGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KNzc3iIiIra2t
p6enp6enqKiop6enp6enp6enp6enr6+vCg0KZW5kc3RyZWFtDWVuZG9iag03NDAgMCBvYmo8PC9M
ZW5ndGggMzcvV2lkdGggMTIvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2Ug
MTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCldXV0FBQaKioqmpqaen
p6enp6enp6enp6enp6ampqampru7uwoNCmVuZHN0cmVhbQ1lbmRvYmoNNzQxIDAgb2JqPDwvTGVu
Z3RoIDM3L1dpZHRoIDEyL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1
IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQo1NTVMTEykpKSpqamnp6en
p6enp6enp6enp6enp6empqarq6sKDQplbmRzdHJlYW0NZW5kb2JqDTc0MiAwIG9iajw8L0xlbmd0
aCA0Ni9XaWR0aCAxNS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAw
IFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KQUFBdnZ2rKysp6enp6enp6en
p6enp6enp6enp6enp6enp6enp6enp6enqqqqCg0KZW5kc3RyZWFtDWVuZG9iag03NDMgMCBvYmo8
PC9MZW5ndGggNDAvV2lkdGggMTMvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3Bh
Y2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCkBAQDY2Njg4OJKS
kqurq6enp6enp6enp6enp6enp6enp6amprCwsAoNCmVuZHN0cmVhbQ1lbmRvYmoNNzQ0IDAgb2Jq
PDwvTGVuZ3RoIDcvV2lkdGggMi9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFj
ZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KgJfpXXHMCg0KZW5k
c3RyZWFtDWVuZG9iag03NDUgMCBvYmo8PC9MZW5ndGggODcvRmlsdGVyL0ZsYXRlRGVjb2RlL1dp
ZHRoIDQxL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBl
L1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpIicpvvuyVesIn9YhP6mGPkLWCvXMY/v9H
QQdbGGoYGBpRUS0Dw7k5DH9/MUwzZdiQzPD4KLouOLp/EKR4TQyIPc/Rp9jNxyeNlU8rp6gBIMAA
urI32QoNCmVuZHN0cmVhbQ1lbmRvYmoNNzQ2IDAgb2JqPDwvTGVuZ3RoIDEwL1dpZHRoIDMvSGVp
Z2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9T
dWJ0eXBlL0ltYWdlPj5zdHJlYW0NCnh9iGdqfZujrAoNCmVuZHN0cmVhbQ1lbmRvYmoNNzQ3IDAg
b2JqPDwvTGVuZ3RoIDQvV2lkdGggMS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JT
cGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0K5+fnCg0KZW5k
c3RyZWFtDWVuZG9iag03NDggMCBvYmo8PC9MZW5ndGggMzQvV2lkdGggMTEvSGVpZ2h0IDEvQml0
c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0lt
YWdlPj5zdHJlYW0NCjc3N42NjbGxsaysrKysrKysrKysrKysrKurq6ysrLS0tAoNCmVuZHN0cmVh
bQ1lbmRvYmoNNzQ5IDAgb2JqPDwvTGVuZ3RoIDM3L1dpZHRoIDEyL0hlaWdodCAxL0JpdHNQZXJD
b21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+
c3RyZWFtDQpXV1dCQkKmpqaurq6tra2srKysrKytra2srKysrKysrKzAwMAKDQplbmRzdHJlYW0N
ZW5kb2JqDTc1MCAwIG9iajw8L0xlbmd0aCAzNC9XaWR0aCAxMS9IZWlnaHQgMS9CaXRzUGVyQ29t
cG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0
cmVhbQ0KNDQ0fX19s7OzrKysrKysrKysrKysrKysrKysrKyssLCwCg0KZW5kc3RyZWFtDWVuZG9i
ag03NTEgMCBvYmo8PC9MZW5ndGggNDYvV2lkdGggMTUvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVu
dCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0N
ClJSUmpqarOzs6ysrKysrKysrKysrKysrKysrKysrKysrKysrKysrK2trbOzswoNCmVuZHN0cmVh
bQ1lbmRvYmoNNzUyIDAgb2JqPDwvTGVuZ3RoIDQwL1dpZHRoIDEzL0hlaWdodCAxL0JpdHNQZXJD
b21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+
c3RyZWFtDQpAQEA2NjY4ODiWlpaxsbGsrKysrKysrKysrKysrKysrKysrKy2trYKDQplbmRzdHJl
YW0NZW5kb2JqDTc1MyAwIG9iajw8L0xlbmd0aCAxMC9XaWR0aCAzL0hlaWdodCAxL0JpdHNQZXJD
b21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+
c3RyZWFtDQqKoOxRb9padOEKDQplbmRzdHJlYW0NZW5kb2JqDTc1NCAwIG9iajw8L0xlbmd0aCA5
MC9GaWx0ZXIvRmxhdGVEZWNvZGUvV2lkdGggNDEvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4
L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCkiJ
ym++5JFyzCf1sE/KIZfQ1Xxdsxn+/0dBp6cx1DIwNDAwNCKhagaGtbEg2RWRIPbRLnRdcPT2NkM7
P0OXBMP3DwxHWxTLJBOTKnlEDbwCEgACDAB91jaRCg0KZW5kc3RyZWFtDWVuZG9iag03NTUgMCBv
Ymo8PC9MZW5ndGggMTMvV2lkdGggNC9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JT
cGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KXGFxAAQXAAAR
YGFrCg0KZW5kc3RyZWFtDWVuZG9iag03NTYgMCBvYmo8PC9MZW5ndGggNC9XaWR0aCAxL0hlaWdo
dCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3Vi
dHlwZS9JbWFnZT4+c3RyZWFtDQqstLwKDQplbmRzdHJlYW0NZW5kb2JqDTc1NyAwIG9iajw8L0xl
bmd0aCAzNC9XaWR0aCAxMS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAx
NSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KNzc3jo6OtLS0rq6urq6u
rq6urq6urq6urq6urq6utra2Cg0KZW5kc3RyZWFtDWVuZG9iag03NTggMCBvYmo8PC9MZW5ndGgg
MzcvV2lkdGggMTIvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBS
L1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCldXV0JCQqmpqbCwsK6urq6urq6u
rq6urq6urq6urq2trcHBwQoNCmVuZHN0cmVhbQ1lbmRvYmoNNzU5IDAgb2JqPDwvTGVuZ3RoIDM0
L1dpZHRoIDExL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9U
eXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQplZWWampqysrKurq6urq6urq6urq6u
rq6urq6urq6ysrIKDQplbmRzdHJlYW0NZW5kb2JqDTc2MCAwIG9iajw8L0xlbmd0aCAyNS9GaWx0
ZXIvRmxhdGVEZWNvZGUvV2lkdGggMTUvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9y
U3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCkiJioiIqK2t
3bJlyzpCAKgGIMAAfrIdJgoNCmVuZHN0cmVhbQ1lbmRvYmoNNzYxIDAgb2JqPDwvTGVuZ3RoIDQw
L1dpZHRoIDEzL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9U
eXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpAQEA2NjY4ODiXl5ezs7Ourq6urq6u
rq6urq6urq6urq6urq63t7cKDQplbmRzdHJlYW0NZW5kb2JqDTc2MiAwIG9iajw8L0xlbmd0aCAx
MC9XaWR0aCAzL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9U
eXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQqEmupSbdhSbu0KDQplbmRzdHJlYW0N
ZW5kb2JqDTc2MyAwIG9iajw8L0xlbmd0aCA5NC9GaWx0ZXIvRmxhdGVEZWNvZGUvV2lkdGggNDEv
SGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVj
dC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCkiJymu+6JF01Cf1kHfyAeeg5UITVjH8/4+CTkxmqGVg
aGBgaERCQJF5tgwfHjLMs2coYWA42o2uC45eX2do4WTok2H49YXhQJVCtWhUfBGHoHZpRStAgAEA
XbI2WQoNCmVuZHN0cmVhbQ1lbmRvYmoNNzY0IDAgb2JqPDwvTGVuZ3RoIDE2L1dpZHRoIDUvSGVp
Z2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9T
dWJ0eXBlL0ltYWdlPj5zdHJlYW0NClNXawAGGAsQIwIFFHFyewoNCmVuZHN0cmVhbQ1lbmRvYmoN
NzY1IDAgb2JqPDwvTGVuZ3RoIDQvV2lkdGggMS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgv
Q29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KNT9O
Cg0KZW5kc3RyZWFtDWVuZG9iag03NjYgMCBvYmo8PC9MZW5ndGggMzQvV2lkdGggMTEvSGVpZ2h0
IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0
eXBlL0ltYWdlPj5zdHJlYW0NCjc3N5CQkLa2trCwsLCwsLCwsLCwsLCwsLCwsLCwsLi4uAoNCmVu
ZHN0cmVhbQ1lbmRvYmoNNzY3IDAgb2JqPDwvTGVuZ3RoIDM3L1dpZHRoIDEyL0hlaWdodCAxL0Jp
dHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9J
bWFnZT4+c3RyZWFtDQpXV1dCQkKrq6uysrKwsLCwsLCwsLCwsLCwsLCwsLCvr6/Dw8MKDQplbmRz
dHJlYW0NZW5kb2JqDTc2OCAwIG9iajw8L0xlbmd0aCAzNC9XaWR0aCAxMS9IZWlnaHQgMS9CaXRz
UGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1h
Z2U+PnN0cmVhbQ0KiIiIr6+vsrKysbGxsbGxsbGxsbGxsbGxsbGxsLCwtbW1Cg0KZW5kc3RyZWFt
DWVuZG9iag03NjkgMCBvYmo8PC9MZW5ndGggNDYvV2lkdGggMTUvSGVpZ2h0IDEvQml0c1BlckNv
bXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5z
dHJlYW0NCkdHR5WVlbW1tbCwsLCwsLCwsLCwsLCwsLCwsLCwsLCwsLCwsLCwsLCwsLi4uAoNCmVu
ZHN0cmVhbQ1lbmRvYmoNNzcwIDAgb2JqPDwvTGVuZ3RoIDQwL1dpZHRoIDEzL0hlaWdodCAxL0Jp
dHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9J
bWFnZT4+c3RyZWFtDQpAQEA2NjY4ODiampq1tbWwsLCwsLCwsLCwsLCwsLCwsLCwsLC5ubkKDQpl
bmRzdHJlYW0NZW5kb2JqDTc3MSAwIG9iajw8L0xlbmd0aCAxMC9XaWR0aCAzL0hlaWdodCAxL0Jp
dHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9J
bWFnZT4+c3RyZWFtDQp+lehRbdlJaNQKDQplbmRzdHJlYW0NZW5kb2JqDTc3MiAwIG9iajw8L0xl
bmd0aCA5Mi9GaWx0ZXIvRmxhdGVEZWNvZGUvV2lkdGggNDAvSGVpZ2h0IDEvQml0c1BlckNvbXBv
bmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJl
YW0NCkiJymm84J542DvlgFfSAYegudybNzP8/49A//4yLPFlqGZgaERFdQwMM60YFjoz1DMwNDAw
3N+HogsZnZ7O0MjKcG0Nw94KxmamkOoYRXVHa4cggAADAFUzMu8KDQplbmRzdHJlYW0NZW5kb2Jq
DTc3MyAwIG9iajw8L0xlbmd0aCAxNi9XaWR0aCA1L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQg
OC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQp7
fpIEChwMECEGCRg3OUMKDQplbmRzdHJlYW0NZW5kb2JqDTc3NCAwIG9iajw8L0xlbmd0aCA3L1dp
ZHRoIDIvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUv
WE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCrKzuzsrMQoNCmVuZHN0cmVhbQ1lbmRvYmoN
Nzc1IDAgb2JqPDwvTGVuZ3RoIDMxL1dpZHRoIDEwL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQg
OC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQrA
wMC8vLy8vLy7u7u7u7u7u7u7u7u8vLy7u7u/v78KDQplbmRzdHJlYW0NZW5kb2JqDTc3NiAwIG9i
ajw8L0xlbmd0aCAzNy9XaWR0aCAxMi9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JT
cGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KV1dXQ0NDsLCw
t7e3tbW1tbW1tbW1tbW1tbW1tbW1tLS0x8fHCg0KZW5kc3RyZWFtDWVuZG9iag03NzcgMCBvYmo8
PC9MZW5ndGggMjcvRmlsdGVyL0ZsYXRlRGVjb2RlL1dpZHRoIDE2L0hlaWdodCAxL0JpdHNQZXJD
b21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+
c3RyZWFtDQpIiYqPj58xY8auXbu2EgGOHj0KEGAABEog1woNCmVuZHN0cmVhbQ1lbmRvYmoNNzc4
IDAgb2JqPDwvTGVuZ3RoIDQwL1dpZHRoIDEzL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9D
b2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpAQEA2
NjY4ODienp66urq1tbW1tbW1tbW1tbW1tbW0tLS1tbW9vb0KDQplbmRzdHJlYW0NZW5kb2JqDTc3
OSAwIG9iajw8L0xlbmd0aCAxMy9XaWR0aCA0L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9D
b2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQqFm+pS
btlTbNRdd9sKDQplbmRzdHJlYW0NZW5kb2JqDTc4MCAwIG9iajw8L0xlbmd0aCA5MS9GaWx0ZXIv
RmxhdGVEZWNvZGUvV2lkdGggNDAvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3Bh
Y2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCkiJyqg765F0yCt5
n3fifpuQWcz7djD8/49Av78zzLZkqGFgaMRAzWwMDSwMDQwMdQwMM4wZPjxG0QhHLy8z7G5gONLF
0MTE2MgQWBIvK28ZEZMPEGAA9QAxewoNCmVuZHN0cmVhbQ1lbmRvYmoNNzgxIDAgb2JqPDwvTGVu
Z3RoIDI1L1dpZHRoIDgvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUg
MCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCkpQXwUKHQwQHwcKGBoeKURG
TxcbJQcMEgoNCmVuZHN0cmVhbQ1lbmRvYmoNNzgyIDAgb2JqPDwvTGVuZ3RoIDM0L1dpZHRoIDEx
L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmpl
Y3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQo3NzeVlZXAwMC5ubm5ubm5ubm5ubm5ubm5ubm4uLjB
wcEKDQplbmRzdHJlYW0NZW5kb2JqDTc4MyAwIG9iajw8L0xlbmd0aCAzNy9XaWR0aCAxMi9IZWln
aHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1
YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KV1dXREREs7Ozu7u7ubm5ubm5ubm5ubm5ubm5ubm5uLi4y8vL
Cg0KZW5kc3RyZWFtDWVuZG9iag03ODQgMCBvYmo8PC9MZW5ndGggNDkvV2lkdGggMTYvSGVpZ2h0
IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0
eXBlL0ltYWdlPj5zdHJlYW0NCmZmZqKior29vbm5ubm5ubm5ubm5ubm5ubm5ubm5ubm5ubm5ubm5
ubm5ubq6usfHxwoNCmVuZHN0cmVhbQ1lbmRvYmoNNzg1IDAgb2JqPDwvTGVuZ3RoIDQwL1dpZHRo
IDEzL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hP
YmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpAQEA2NjY4ODihoaG+vr65ubm5ubm5ubm5ubm5
ubm5ubm5ubnCwsIKDQplbmRzdHJlYW0NZW5kb2JqDTc4NiAwIG9iajw8L0xlbmd0aCAxMy9XaWR0
aCA0L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hP
YmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQqBl+pRbNhTbdZad9gKDQplbmRzdHJlYW0NZW5k
b2JqDTc4NyAwIG9iajw8L0xlbmd0aCA4My9GaWx0ZXIvRmxhdGVEZWNvZGUvV2lkdGggNDAvSGVp
Z2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9T
dWJ0eXBlL0ltYWdlPj5zdHJlYW0NCkiJSqs57Z540DNpr3fiPsvAqYx7tjP8/49Av78xzLZkqGFg
aMRADWAEZNQzMDTxMDy/hKIRGX19wzDHiqGagbmROaoxSUbaPDWjEiDAAOBcMZwKDQplbmRzdHJl
YW0NZW5kb2JqDTc4OCAwIG9iajw8L0xlbmd0aCAyNS9XaWR0aCA4L0hlaWdodCAxL0JpdHNQZXJD
b21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+
c3RyZWFtDQoxNUQGChsLDx0IDBoGChQBAgoDBAwJCxIKDQplbmRzdHJlYW0NZW5kb2JqDTc4OSAw
IG9iajw8L0xlbmd0aCAzNC9XaWR0aCAxMS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29s
b3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KNzc3mZmZ
xMTEvb29vb29vr6+vb29vb29vb29vb29xMTECg0KZW5kc3RyZWFtDWVuZG9iag03OTAgMCBvYmo8
PC9MZW5ndGggMzcvV2lkdGggMTIvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3Bh
Y2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCldXV0RERLe3t7+/
v729vb6+vr6+vr29vb29vb29vby8vM7OzgoNCmVuZHN0cmVhbQ1lbmRvYmoNNzkxIDAgb2JqPDwv
TGVuZ3RoIDQ5L1dpZHRoIDE2L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNl
IDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQplZWWoqKjBwcG+vr6+
vr69vb29vb29vb29vb29vb29vb2+vr6+vr69vb29vb3GxsYKDQplbmRzdHJlYW0NZW5kb2JqDTc5
MiAwIG9iajw8L0xlbmd0aCA0MC9XaWR0aCAxMy9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgv
Q29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KQEBA
NjY2ODg4pKSkw8PDvb29vb29vb29vb29vb29vb29vb29xsbGCg0KZW5kc3RyZWFtDWVuZG9iag03
OTMgMCBvYmo8PC9MZW5ndGggMTYvV2lkdGggNS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgv
Q29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KiJ7t
Um7aVG3UTmzPYHfbCg0KZW5kc3RyZWFtDWVuZG9iag03OTQgMCBvYmo8PC9MZW5ndGggNzYvRmls
dGVyL0ZsYXRlRGVjb2RlL1dpZHRoIDQwL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xv
clNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpIiUqvPeWe
uN8jcbd34h5r/2nMmzcw/P+PQP/+MizzZahhYGjEjRoYGOoZGG5tQdGIjP78ZJhvDzHEa6Kfs3O4
gqo1QIABAN26MSYKDQplbmRzdHJlYW0NZW5kb2JqDTc5NSAwIG9iajw8L0xlbmd0aCAyOC9XaWR0
aCA5L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hP
YmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQqHiZYDBhgLDh0JDBoGCxUFCBEFCA8EBAsGCQ4K
DQplbmRzdHJlYW0NZW5kb2JqDTc5NiAwIG9iajw8L0xlbmd0aCAzNC9XaWR0aCAxMS9IZWlnaHQg
MS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5
cGUvSW1hZ2U+PnN0cmVhbQ0KNzc3mZmZxcXFvr6+vr6+vr6+vr6+vr6+vr6+vr6+xcXFCg0KZW5k
c3RyZWFtDWVuZG9iag03OTcgMCBvYmo8PC9MZW5ndGggMzcvV2lkdGggMTIvSGVpZ2h0IDEvQml0
c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0lt
YWdlPj5zdHJlYW0NCldXV0RERLi4uMDAwL6+vr6+vr6+vr6+vr6+vr6+vr29vc/PzwoNCmVuZHN0
cmVhbQ1lbmRvYmoNNzk4IDAgb2JqPDwvTGVuZ3RoIDI3L0ZpbHRlci9GbGF0ZURlY29kZS9XaWR0
aCAxNi9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9Y
T2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KSImqrq7evXv3/v379xEBjh49ChBgAENfIucK
DQplbmRzdHJlYW0NZW5kb2JqDTc5OSAwIG9iajw8L0xlbmd0aCA0MC9XaWR0aCAxMy9IZWlnaHQg
MS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5
cGUvSW1hZ2U+PnN0cmVhbQ0KQEBANjY2ODg4paWlw8PDvr6+vr6+vr6+vr6+vr6+vr6+vr6+x8fH
Cg0KZW5kc3RyZWFtDWVuZG9iag04MDAgMCBvYmo8PC9MZW5ndGggMTYvV2lkdGggNS9IZWlnaHQg
MS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5
cGUvSW1hZ2U+PnN0cmVhbQ0KhJrsUW3YVG7UTmrQXnraCg0KZW5kc3RyZWFtDWVuZG9iag04MDEg
MCBvYmo8PC9MZW5ndGggNzcvRmlsdGVyL0ZsYXRlRGVjb2RlL1dpZHRoIDQwL0hlaWdodCAxL0Jp
dHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9J
bWFnZT4+c3RyZWFtDQpIiUqvPemasNc9cZdXwm4L3ylMmzcx/P+PQL9/MMy1YqhhYGjEjeoYGDql
GF7fQNGIjL6+YehXZqgFKfac6m3vGKSkbQ8QYADV6zEKCg0KZW5kc3RyZWFtDWVuZG9iag04MDIg
MCBvYmo8PC9MZW5ndGggMjgvV2lkdGggOS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29s
b3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KKy9BBgoY
CQ0bCAwVBwkSBAgQBAUNAgQJAgQICg0KZW5kc3RyZWFtDWVuZG9iag04MDMgMCBvYmo8PC9MZW5n
dGggMzQvV2lkdGggMTEvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUg
MCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCjc3N52dncnJycLCwsLCwsLC
wsLCwsLCwsHBwcLCwsnJyQoNCmVuZHN0cmVhbQ1lbmRvYmoNODA0IDAgb2JqPDwvTGVuZ3RoIDM3
L1dpZHRoIDEyL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9U
eXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpXV1dFRUW8vLzExMTCwsLCwsLCwsLC
wsLCwsLCwsLBwcHS0tIKDQplbmRzdHJlYW0NZW5kb2JqDTgwNSAwIG9iajw8L0xlbmd0aCAyNy9G
aWx0ZXIvRmxhdGVEZWNvZGUvV2lkdGggMTYvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0Nv
bG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCkiJ6ujo
OHjw4OHDhw8RAY4ePQoQYABbpCO8Cg0KZW5kc3RyZWFtDWVuZG9iag04MDYgMCBvYmo8PC9MZW5n
dGggNDAvV2lkdGggMTMvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUg
MCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCkBAQDY2Njg4OKioqMfHx8LC
wsLCwsLCwsLCwsLCwsHBwcLCwsrKygoNCmVuZHN0cmVhbQ1lbmRvYmoNODA3IDAgb2JqPDwvTGVu
Z3RoIDE2L1dpZHRoIDUvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUg
MCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCmB85lNs1VJu0k5nzluJ0woN
CmVuZHN0cmVhbQ1lbmRvYmoNODA4IDAgb2JqPDwvTGVuZ3RoIDgyL0ZpbHRlci9GbGF0ZURlY29k
ZS9XaWR0aCA0MC9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIv
VHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KSIlKqznpErfHI2GHR+xOu9CZfCeO
M/z/j0BfXzNMVGWoZWBoxIEaGBgqGRg25DL8+YeiERk9Oc3Qws1Qz8DczBw9J9baJUhRyw4gwAD3
1jGYCg0KZW5kc3RyZWFtDWVuZG9iag04MDkgMCBvYmo8PC9MZW5ndGggMjgvV2lkdGggOS9IZWln
aHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1
YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KISU2BwoYCAwYBgoUBggSBAYOAwQKAQMGAAIECg0KZW5kc3Ry
ZWFtDWVuZG9iag04MTAgMCBvYmo8PC9MZW5ndGggMzQvV2lkdGggMTEvSGVpZ2h0IDEvQml0c1Bl
ckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdl
Pj5zdHJlYW0NCjc3N6Ghoc/Pz8fHx8fHx8jIyMfHx8fHx8fHx8fHx87OzgoNCmVuZHN0cmVhbQ1l
bmRvYmoNODExIDAgb2JqPDwvTGVuZ3RoIDM3L1dpZHRoIDEyL0hlaWdodCAxL0JpdHNQZXJDb21w
b25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3Ry
ZWFtDQpXV1dGRkbAwMDJycnHx8fIyMjIyMjHx8fHx8fHx8fGxsbX19cKDQplbmRzdHJlYW0NZW5k
b2JqDTgxMiAwIG9iajw8L0xlbmd0aCA0OS9XaWR0aCAxNi9IZWlnaHQgMS9CaXRzUGVyQ29tcG9u
ZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVh
bQ0KqqqqzMzMx8fHyMjIyMjIx8fHx8fHx8fHx8fHx8fHx8fHyMjIyMjIx8fHx8fHzMzMCg0KZW5k
c3RyZWFtDWVuZG9iag04MTMgMCBvYmo8PC9MZW5ndGggNDAvV2lkdGggMTMvSGVpZ2h0IDEvQml0
c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0lt
YWdlPj5zdHJlYW0NCkBAQDY2Njg4OKysrM3NzcfHx8fHx8fHx8fHx8fHx8fHx8fHx8/PzwoNCmVu
ZHN0cmVhbQ1lbmRvYmoNODE0IDAgb2JqPDwvTGVuZ3RoIDE2L1dpZHRoIDUvSGVpZ2h0IDEvQml0
c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0lt
YWdlPj5zdHJlYW0NCml/11Ns11Bt0U9nzlaByQoNCmVuZHN0cmVhbQ1lbmRvYmoNODE1IDAgb2Jq
PDwvTGVuZ3RoIDgwL0ZpbHRlci9GbGF0ZURlY29kZS9XaWR0aCA0MC9IZWlnaHQgMS9CaXRzUGVy
Q29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+
PnN0cmVhbQ0KSIlKrT7uErfLI2G7U+SmuNwt7g+eMPz/j0AfnzBMUGCoY2BoxIYaGBhaOBmWeDJ8
eIiiCw1dXslQA1LM2soWNyPeytFfUcsOIMAAcF8zJQoNCmVuZHN0cmVhbQ1lbmRvYmoNODE2IDAg
b2JqPDwvTGVuZ3RoIDI4L1dpZHRoIDkvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9y
U3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCiElMwYJGAcM
FgYJEgUIEQUGDQIECQAAAhMTFAoNCmVuZHN0cmVhbQ1lbmRvYmoNODE3IDAgb2JqPDwvTGVuZ3Ro
IDM0L1dpZHRoIDExL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAg
Ui9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQo2NjaioqLS0tLKysrKysrKysrK
ysrKysrKysrKysrR0dEKDQplbmRzdHJlYW0NZW5kb2JqDTgxOCAwIG9iajw8L0xlbmd0aCAzNy9X
aWR0aCAxMi9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlw
ZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KV1dXRkZGw8PDzc3NysrKysrKysrKysrK
ysrKysrKysrK2dnZCg0KZW5kc3RyZWFtDWVuZG9iag04MTkgMCBvYmo8PC9MZW5ndGggNDkvV2lk
dGggMTYvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUv
WE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCr6+vtDQ0MrKysrKysrKysvLy8vLy8rKysrK
ysvLy8vLy8rKysrKysrKysvLy9HR0QoNCmVuZHN0cmVhbQ1lbmRvYmoNODIwIDAgb2JqPDwvTGVu
Z3RoIDQwL1dpZHRoIDEzL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1
IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpAQEA2NjY4ODiurq7Q0NDK
ysrKysrKysrKysrKysrKysrKysrR0dEKDQplbmRzdHJlYW0NZW5kb2JqDTgyMSAwIG9iajw8L0xl
bmd0aCAxNi9XaWR0aCA1L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1
IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQprf9RPbNRQa85PZsxVgskK
DQplbmRzdHJlYW0NZW5kb2JqDTgyMiAwIG9iajw8L0xlbmd0aCA4MS9GaWx0ZXIvRmxhdGVEZWNv
ZGUvV2lkdGggNDAvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBS
L1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCkiJSqk67hK70z1uq134+uzSXTGP
XzL8/49AH58yLHBgqGdgaMSGgOKtPAyH+hn+/UfRhYbOzGKoYWBoYOBp5wnviTW18VLSsgUIMACr
2jPlCg0KZW5kc3RyZWFtDWVuZG9iag04MjMgMCBvYmo8PC9MZW5ndGggMjgvV2lkdGggOS9IZWln
aHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1
YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KKy07AwYUBwwVBwkSBAcQBAUMAgQJAAABFxcYCg0KZW5kc3Ry
ZWFtDWVuZG9iag04MjQgMCBvYmo8PC9MZW5ndGggMzQvV2lkdGggMTEvSGVpZ2h0IDEvQml0c1Bl
ckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdl
Pj5zdHJlYW0NCjc3N6Ojo9LS0svLy8vLy8vLy8vLy8vLy8vLy8vLy9LS0goNCmVuZHN0cmVhbQ1l
bmRvYmoNODI1IDAgb2JqPDwvTGVuZ3RoIDM3L1dpZHRoIDEyL0hlaWdodCAxL0JpdHNQZXJDb21w
b25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3Ry
ZWFtDQpXV1dGRkbExMTOzs7Ly8vMzMzMzMzLy8vLy8vLy8vLy8va2toKDQplbmRzdHJlYW0NZW5k
b2JqDTgyNiAwIG9iajw8L0xlbmd0aCAyNC9GaWx0ZXIvRmxhdGVEZWNvZGUvV2lkdGggMTYvSGVp
Z2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9T
dWJ0eXBlL0ltYWdlPj5zdHJlYW0NCkiJunPnzpkzZ04TBy5fvgwQYACu9iZfCg0KZW5kc3RyZWFt
DWVuZG9iag04MjcgMCBvYmo8PC9MZW5ndGggNDAvV2lkdGggMTMvSGVpZ2h0IDEvQml0c1BlckNv
bXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5z
dHJlYW0NCkBAQDY2Njg4OLCwsNHR0cvLy8vLy8vLy8vLy8vLy8vLy8vLy9LS0goNCmVuZHN0cmVh
bQ1lbmRvYmoNODI4IDAgb2JqPDwvTGVuZ3RoIDEzL1dpZHRoIDQvSGVpZ2h0IDEvQml0c1BlckNv
bXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5z
dHJlYW0NCmV80U1p0E9mylJ6yAoNCmVuZHN0cmVhbQ1lbmRvYmoNODI5IDAgb2JqPDwvTGVuZ3Ro
IDc5L0ZpbHRlci9GbGF0ZURlY29kZS9XaWR0aCA0MC9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50
IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0K
SIlKqTrqErvDLXaLXfi6zMIdiY8/Mvz/j0BvbjEs9WaoZ2BoxIZqGRjKGRi21qBowUS7KxiqGRga
GKR7ZMMmxOlbuShr2AAEGACbgzONCg0KZW5kc3RyZWFtDWVuZG9iag04MzAgMCBvYmo8PC9MZW5n
dGggMjgvV2lkdGggOS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAw
IFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KLi88AgYTBwsUBQkSBAcNAQIH
AgMIAAABGxscCg0KZW5kc3RyZWFtDWVuZG9iag04MzEgMCBvYmo8PC9MZW5ndGggMzQvV2lkdGgg
MTEvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9i
amVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCjc3N6enp9jY2NDQ0NDQ0NDQ0NDQ0NDQ0NDQ0NDQ
0NbW1goNCmVuZHN0cmVhbQ1lbmRvYmoNODMyIDAgb2JqPDwvTGVuZ3RoIDM3L1dpZHRoIDEyL0hl
aWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3Qv
U3VidHlwZS9JbWFnZT4+c3RyZWFtDQpWVlZHR0fKysrS0tLQ0NDQ0NDQ0NDQ0NDQ0NDPz8/Q0NDe
3t4KDQplbmRzdHJlYW0NZW5kb2JqDTgzMyAwIG9iajw8L0xlbmd0aCAyNC9GaWx0ZXIvRmxhdGVE
ZWNvZGUvV2lkdGggMTYvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUg
MCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCkiJOn78+KVLly4QB+7cuQMQ
YAC4OCcQCg0KZW5kc3RyZWFtDWVuZG9iag04MzQgMCBvYmo8PC9MZW5ndGggNDAvV2lkdGggMTMv
SGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVj
dC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCkBAQDY2Njg4OLOzs9bW1tDQ0NDQ0NDQ0NDQ0NDQ0NDQ
0NDQ0NjY2AoNCmVuZHN0cmVhbQ1lbmRvYmoNODM1IDAgb2JqPDwvTGVuZ3RoIDEzL1dpZHRoIDQv
SGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVj
dC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCmZ7zE5ozU5nylJ6xwoNCmVuZHN0cmVhbQ1lbmRvYmoN
ODM2IDAgb2JqPDwvTGVuZ3RoIDgyL0ZpbHRlci9GbGF0ZURlY29kZS9XaWR0aCA0MC9IZWlnaHQg
MS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5
cGUvSW1hZ2U+PnN0cmVhbQ0KSIlKqTriHL3NNXazXdjatMKtaa8+M/z/j0Dv7jMs9mSoZ2BoxEA1
DAxLvRmO9jN8foOiBROtCGOoZmBoYJDplfNsDdA3d5KQ0QcIMAACUzUGCg0KZW5kc3RyZWFtDWVu
ZG9iag04MzcgMCBvYmo8PC9MZW5ndGggMjgvV2lkdGggOS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9u
ZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVh
bQ0KkJGXAgYRBQkSBQkSAgULJy8uDBQQAAAAHBwdCg0KZW5kc3RyZWFtDWVuZG9iag04MzggMCBv
Ymo8PC9MZW5ndGggMzQvV2lkdGggMTEvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9y
U3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCjc3N6ioqNra
2tLS0tLS0tLS0tLS0tLS0tLS0tLS0tjY2AoNCmVuZHN0cmVhbQ1lbmRvYmoNODM5IDAgb2JqPDwv
TGVuZ3RoIDM3L1dpZHRoIDEyL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNl
IDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpWVlZHR0fLy8vV1dXS
0tLS0tLS0tLS0tLT09PS0tLS0tLg4OAKDQplbmRzdHJlYW0NZW5kb2JqDTg0MCAwIG9iajw8L0xl
bmd0aCAyMS9GaWx0ZXIvRmxhdGVEZWNvZGUvV2lkdGggMTUvSGVpZ2h0IDEvQml0c1BlckNvbXBv
bmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJl
YW0NCkiJunPnziXiwO3btwECDABWviUkCg0KZW5kc3RyZWFtDWVuZG9iag04NDEgMCBvYmo8PC9M
ZW5ndGggNDAvV2lkdGggMTMvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2Ug
MTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCkBAQDY2Njg4OLW1tdjY
2NLS0tLS0tLS0tLS0tLS0tLS0tLS0tnZ2QoNCmVuZHN0cmVhbQ1lbmRvYmoNODQyIDAgb2JqPDwv
TGVuZ3RoIDEwL1dpZHRoIDMvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2Ug
MTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NClx0005nyTxtzAoNCmVu
ZHN0cmVhbQ1lbmRvYmoNODQzIDAgb2JqPDwvTGVuZ3RoIDgyL0ZpbHRlci9GbGF0ZURlY29kZS9X
aWR0aCA0MC9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlw
ZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KSIlKqTrsHL3FNXaTbejq9JKtKZ++MPz/
j0B//zHsKGaoZWBoREX1DAzTtBne3kNRjBV9esowSQ1oAmcLp8M0F/t4XxFRrej4LIAAAwCPBzeS
Cg0KZW5kc3RyZWFtDWVuZG9iag04NDQgMCBvYmo8PC9MZW5ndGggMTYvV2lkdGggNS9IZWlnaHQg
MS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5
cGUvSW1hZ2U+PnN0cmVhbQ0KOkFLAAQNBggRAAAGUlReCg0KZW5kc3RyZWFtDWVuZG9iag04NDUg
MCBvYmo8PC9MZW5ndGggMTAvV2lkdGggMy9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29s
b3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0Kg4aHHx8h
BxoQCg0KZW5kc3RyZWFtDWVuZG9iag04NDYgMCBvYmo8PC9MZW5ndGggMzQvV2lkdGggMTEvSGVp
Z2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9T
dWJ0eXBlL0ltYWdlPj5zdHJlYW0NCjY2Nqqqqtzc3NTU1NTU1NTU1NTU1NTU1NTU1NTU1Nra2goN
CmVuZHN0cmVhbQ1lbmRvYmoNODQ3IDAgb2JqPDwvTGVuZ3RoIDM3L1dpZHRoIDEyL0hlaWdodCAx
L0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlw
ZS9JbWFnZT4+c3RyZWFtDQpWVlZHR0fNzc3X19fU1NTU1NTU1NTU1NTU1NTU1NTU1NTh4eEKDQpl
bmRzdHJlYW0NZW5kb2JqDTg0OCAwIG9iajw8L0xlbmd0aCAyNC9GaWx0ZXIvRmxhdGVEZWNvZGUv
V2lkdGggMTUvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5
cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCkiJevDgwdWrV68QAe7fvw8QYABgYyWN
Cg0KZW5kc3RyZWFtDWVuZG9iag04NDkgMCBvYmo8PC9MZW5ndGggNDAvV2lkdGggMTMvSGVpZ2h0
IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0
eXBlL0ltYWdlPj5zdHJlYW0NCkBAQDY2Njg4OLa2ttvb29TU1NTU1NTU1NTU1NTU1NTU1NTU1Nvb
2woNCmVuZHN0cmVhbQ1lbmRvYmoNODUwIDAgb2JqPDwvTGVuZ3RoIDEwL1dpZHRoIDMvSGVpZ2h0
IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0
eXBlL0ltYWdlPj5zdHJlYW0NClp00ktmx0lmygoNCmVuZHN0cmVhbQ1lbmRvYmoNODUxIDAgb2Jq
PDwvTGVuZ3RoIDc5L0ZpbHRlci9GbGF0ZURlY29kZS9XaWR0aCA0MC9IZWlnaHQgMS9CaXRzUGVy
Q29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+
PnN0cmVhbQ0KSIlKqTjkFLXJNWaDbciqlLzNaa8+Mfz/j4IO9DLUMDA0MjA0wFA9A0MLB8PV1egq
caH18QxVDLxtfO4zvazjXUXEtL39kwACDADTbjj0Cg0KZW5kc3RyZWFtDWVuZG9iag04NTIgMCBv
Ymo8PC9MZW5ndGggMTYvV2lkdGggNS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JT
cGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KaG10AAIMBQgS
AAEIODg/Cg0KZW5kc3RyZWFtDWVuZG9iag04NTMgMCBvYmo8PC9MZW5ndGggNC9XaWR0aCAxL0hl
aWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3Qv
U3VidHlwZS9JbWFnZT4+c3RyZWFtDQo7OzsKDQplbmRzdHJlYW0NZW5kb2JqDTg1NCAwIG9iajw8
L0xlbmd0aCAzNC9XaWR0aCAxMS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFj
ZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KNjY2ra2t4eHh2dnZ
2dnZ2tra2dnZ2dnZ2dnZ2dnZ39/fCg0KZW5kc3RyZWFtDWVuZG9iag04NTUgMCBvYmo8PC9MZW5n
dGggMzcvV2lkdGggMTIvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUg
MCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NClZWVkhISNHR0dzc3NnZ2dra
2tra2tnZ2dnZ2dnZ2dnZ2ebm5goNCmVuZHN0cmVhbQ1lbmRvYmoNODU2IDAgb2JqPDwvTGVuZ3Ro
IDQ2L1dpZHRoIDE1L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAg
Ui9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQq8vLze3t7a2trZ2dnZ2dnZ2dnZ
2dna2trZ2dnZ2dnZ2dnZ2dna2trY2Njj4+MKDQplbmRzdHJlYW0NZW5kb2JqDTg1NyAwIG9iajw8
L0xlbmd0aCA0MC9XaWR0aCAxMy9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFj
ZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KQEBANjY2ODg4urq6
39/f2NjY2dnZ2dnZ2dnZ2dnZ2dnZ2dnZ4ODgCg0KZW5kc3RyZWFtDWVuZG9iag04NTggMCBvYmo8
PC9MZW5ndGggMTAvV2lkdGggMy9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFj
ZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KWnLRS2THUmmzCg0K
ZW5kc3RyZWFtDWVuZG9iag04NTkgMCBvYmo8PC9MZW5ndGggODgvRmlsdGVyL0ZsYXRlRGVjb2Rl
L1dpZHRoIDQxL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9U
eXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpIiUopP+gQudEler1NyMqEjLX1z98x
/P+Pgm7uYGhiZahnYGjnYWjjZGhgYGhkYKhlYLi0DF0lLvTmJkOPBFCL+TQry1obO3sPRlap+sYu
gAADAKt/OxAKDQplbmRzdHJlYW0NZW5kb2JqDTg2MCAwIG9iajw8L0xlbmd0aCAxNi9XaWR0aCA1
L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmpl
Y3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQqWmqMBAg4EBxAAAAVbdWgKDQplbmRzdHJlYW0NZW5k
b2JqDTg2MSAwIG9iajw8L0xlbmd0aCA0L1dpZHRoIDEvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVu
dCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0N
CoiPjAoNCmVuZHN0cmVhbQ1lbmRvYmoNODYyIDAgb2JqPDwvTGVuZ3RoIDM0L1dpZHRoIDExL0hl
aWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3Qv
U3VidHlwZS9JbWFnZT4+c3RyZWFtDQo2NjawsLDm5ubd3d3d3d3e3t7d3d3d3d3d3d3d3d3j4+MK
DQplbmRzdHJlYW0NZW5kb2JqDTg2MyAwIG9iajw8L0xlbmd0aCAzNy9XaWR0aCAxMi9IZWlnaHQg
MS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5
cGUvSW1hZ2U+PnN0cmVhbQ0KVlZWSEhI1dXV4ODg3d3d3d3d3d3d3d3d3d3d3d3d3d3d6urqCg0K
ZW5kc3RyZWFtDWVuZG9iag04NjQgMCBvYmo8PC9MZW5ndGggNDYvV2lkdGggMTUvSGVpZ2h0IDEv
Qml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBl
L0ltYWdlPj5zdHJlYW0NCru7u+Tk5N3d3d3d3d3d3d3d3d3d3d3d3d3d3d3d3d3d3d3d3d3d3dzc
3Ofn5woNCmVuZHN0cmVhbQ1lbmRvYmoNODY1IDAgb2JqPDwvTGVuZ3RoIDQwL1dpZHRoIDEzL0hl
aWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3Qv
U3VidHlwZS9JbWFnZT4+c3RyZWFtDQpAQEA2NjY4ODi+vr7k5OTd3d3d3d3d3d3d3d3d3d3d3d3d
3d3k5OQKDQplbmRzdHJlYW0NZW5kb2JqDTg2NiAwIG9iajw8L0xlbmd0aCA3L1dpZHRoIDIvSGVp
Z2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9T
dWJ0eXBlL0ltYWdlPj5zdHJlYW0NClRtzGNisAoNCmVuZHN0cmVhbQ1lbmRvYmoNODY3IDAgb2Jq
PDwvTGVuZ3RoIDkxL0ZpbHRlci9GbGF0ZURlY29kZS9XaWR0aCA0MS9IZWlnaHQgMS9CaXRzUGVy
Q29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+
PnN0cmVhbQ0KSIlKLj/oELneOWqtVciy5Oz1/c9eMf3/z4CMHh9jaOFgaGBkODeP4d4+hhmGDNUM
DK08DM/OMqCpxIVeXWPoEmOqZ7Cf5mReYW5v783ALBYRnQIQYABzdT05Cg0KZW5kc3RyZWFtDWVu
ZG9iag04NjggMCBvYmo8PC9MZW5ndGggMTMvV2lkdGggNC9IZWlnaHQgMS9CaXRzUGVyQ29tcG9u
ZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVh
bQ0KhoyXAAAIAAAARklMCg0KZW5kc3RyZWFtDWVuZG9iag04NjkgMCBvYmo8PC9MZW5ndGggNC9X
aWR0aCAxL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBl
L1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQq+v78KDQplbmRzdHJlYW0NZW5kb2JqDTg3
MCAwIG9iajw8L0xlbmd0aCAzNC9XaWR0aCAxMS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgv
Q29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KNjY2
sbGx5ubm3t7e3t7e3t7e3t7e3t7e3t7e3t7e5OTkCg0KZW5kc3RyZWFtDWVuZG9iag04NzEgMCBv
Ymo8PC9MZW5ndGggMzcvV2lkdGggMTIvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9y
U3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NClZWVkhISNfX
1+Hh4d7e3t7e3t7e3t7e3t7e3t7e3t7e3urq6goNCmVuZHN0cmVhbQ1lbmRvYmoNODcyIDAgb2Jq
PDwvTGVuZ3RoIDQzL1dpZHRoIDE0L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNw
YWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQrk5OTf39/e3t7e
3t7e3t7e3t7e3t7e3t7e3t7e3t7e3t7e3t7d3d3l5eUKDQplbmRzdHJlYW0NZW5kb2JqDTg3MyAw
IG9iajw8L0xlbmd0aCA0MC9XaWR0aCAxMy9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29s
b3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KQEBANjY2
ODg4vr6+5eXl3t7e3t7e3t7e3t7e3t7e3t7e3t7e5eXlCg0KZW5kc3RyZWFtDWVuZG9iag04NzQg
MCBvYmo8PC9MZW5ndGggNy9XaWR0aCAyL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xv
clNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpacsxWargK
DQplbmRzdHJlYW0NZW5kb2JqDTg3NSAwIG9iajw8L0xlbmd0aCA4Ni9GaWx0ZXIvRmxhdGVEZWNv
ZGUvV2lkdGggNDEvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBS
L1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCkiJSizf7xC5zilyjWXg4tyyLWff
vpf+/58BGd3exlDNwDDNgOHvbxB3dShDOQPD7nIGNGV40LFJDJUMGv2axv1mjnnucnImDExCVbUt
AAEGADUZP5cKDQplbmRzdHJlYW0NZW5kb2JqDTg3NiAwIG9iajw8L0xlbmd0aCAxMC9XaWR0aCAz
L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmpl
Y3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQqTlp8eICZBQmIKDQplbmRzdHJlYW0NZW5kb2JqDTg3
NyAwIG9iajw8L0xlbmd0aCAzNC9XaWR0aCAxMS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgv
Q29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KNjY2
tLS06urq4uLi4uLi4uLi4uLi4uLi4eHh4uLi5+fnCg0KZW5kc3RyZWFtDWVuZG9iag04NzggMCBv
Ymo8PC9MZW5ndGggMzcvV2lkdGggMTIvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9y
U3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NClZWVklJSdra
2uXl5eLi4uLi4uLi4uLi4uLi4uLi4uLi4u3t7QoNCmVuZHN0cmVhbQ1lbmRvYmoNODc5IDAgb2Jq
PDwvTGVuZ3RoIDMxL1dpZHRoIDEwL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNw
YWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQp/f3+Tk5ORkZGR
kZGRkZGRkZGRkZGRkZGQkJCcnJwKDQplbmRzdHJlYW0NZW5kb2JqDTg4MCAwIG9iajw8L0xlbmd0
aCA0My9XaWR0aCAxNC9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAw
IFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0K4uLi4+Pj4uLi4uLi4uLi4uLi
4uLi4uLi4uLi4uLi4uLi4uLi4eHh6urqCg0KZW5kc3RyZWFtDWVuZG9iag04ODEgMCBvYmo8PC9M
ZW5ndGggNDAvV2lkdGggMTMvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2Ug
MTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCkBAQDY2Njg4OMLCwunp
6eLi4uLi4uLi4uLi4uLi4uLi4uLi4ujo6AoNCmVuZHN0cmVhbQ1lbmRvYmoNODgyIDAgb2JqPDwv
TGVuZ3RoIDcvV2lkdGggMi9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAx
NSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KX3jRUmezCg0KZW5kc3Ry
ZWFtDWVuZG9iag04ODMgMCBvYmo8PC9MZW5ndGggMTkvV2lkdGggNi9IZWlnaHQgMS9CaXRzUGVy
Q29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+
PnN0cmVhbQ0KZ3vBQFetQVqrP1enQFWi09fmCg0KZW5kc3RyZWFtDWVuZG9iag04ODQgMCBvYmo8
PC9MZW5ndGggNjQvRmlsdGVyL0ZsYXRlRGVjb2RlL1dpZHRoIDM1L0hlaWdodCAxL0JpdHNQZXJD
b21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+
c3RyZWFtDQpIiXL7/58BGR3rZyhjYFjuB+Ue72OYqsPw7T0DmjI86MQkhkoGs0kWGo3atnFeUtL6
TCzCNg7+AAEGAF42NqwKDQplbmRzdHJlYW0NZW5kb2JqDTg4NSAwIG9iajw8L0xlbmd0aCA3L1dp
ZHRoIDIvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUv
WE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCtbX3NnQ3QoNCmVuZHN0cmVhbQ1lbmRvYmoN
ODg2IDAgb2JqPDwvTGVuZ3RoIDM0L1dpZHRoIDExL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQg
OC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQo2
Nja4uLjw8PDn5+fn5+fn5+fn5+fn5+fn5+fn5+fs7OwKDQplbmRzdHJlYW0NZW5kb2JqDTg4NyAw
IG9iajw8L0xlbmd0aCAzNy9XaWR0aCAxMi9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29s
b3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KVlZWSkpK
3t7e6urq5+fn5+fn5+fn5+fn5+fn5+fn6Ojo8vLyCg0KZW5kc3RyZWFtDWVuZG9iag04ODggMCBv
Ymo8PC9MZW5ndGggMzQvV2lkdGggMTEvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9y
U3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NClxcXIeHh46O
joyMjIyMjIyMjIyMjIyMjIyMjIuLi5ycnAoNCmVuZHN0cmVhbQ1lbmRvYmoNODg5IDAgb2JqPDwv
TGVuZ3RoIDQzL1dpZHRoIDE0L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNl
IDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQrT09Pt7e3n5+fn5+fn
5+fn5+fn5+fn5+fn5+fn5+fn5+fn5+fn5+fs7OwKDQplbmRzdHJlYW0NZW5kb2JqDTg5MCAwIG9i
ajw8L0xlbmd0aCA0MC9XaWR0aCAxMy9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JT
cGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KQEBANjY2ODg4
xsbG7u7u5+fn5+fn5+fn5+fn5+fn5+fn5+fn7e3tCg0KZW5kc3RyZWFtDWVuZG9iag04OTEgMCBv
Ymo8PC9MZW5ndGggNC9XaWR0aCAxL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNw
YWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpsg9EKDQplbmRz
dHJlYW0NZW5kb2JqDTg5MiAwIG9iajw8L0xlbmd0aCAxNi9XaWR0aCA1L0hlaWdodCAxL0JpdHNQ
ZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFn
ZT4+c3RyZWFtDQpid74+Vqs/WKk4TaCosdUKDQplbmRzdHJlYW0NZW5kb2JqDTg5MyAwIG9iajw8
L0xlbmd0aCA2Ny9GaWx0ZXIvRmxhdGVEZWNvZGUvV2lkdGggMzUvSGVpZ2h0IDEvQml0c1BlckNv
bXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5z
dHJlYW0NCkiJcvv/nwGOfv9kWODEUMvAcGcniPv3N8OGOIZHhxmQ1RBEK0KFqjkdZ7jKFWg7Ovlw
8sgwsgj5BUUBBBgAkFo3LQoNCmVuZHN0cmVhbQ1lbmRvYmoNODk0IDAgb2JqPDwvTGVuZ3RoIDM0
L1dpZHRoIDExL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9U
eXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQo2Nja5ubnz8/Pq6urq6urq6urq6urq
6urq6urq6urw8PAKDQplbmRzdHJlYW0NZW5kb2JqDTg5NSAwIG9iajw8L0xlbmd0aCAzNy9XaWR0
aCAxMi9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9Y
T2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KVlZWSkpK4uLi7u7u6urq6urq6urq6urq6+vr
6urq6+vr9fX1Cg0KZW5kc3RyZWFtDWVuZG9iag04OTYgMCBvYmo8PC9MZW5ndGggMzQvV2lkdGgg
MTEvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9i
amVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCkpKSnFxcY6OjomJiYmJiYmJiYmJiYmJiYmJiYiI
iJubmwoNCmVuZHN0cmVhbQ1lbmRvYmoNODk3IDAgb2JqPDwvTGVuZ3RoIDQwL1dpZHRoIDEzL0hl
aWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3Qv
U3VidHlwZS9JbWFnZT4+c3RyZWFtDQr19fXq6urq6urq6urq6urq6urq6urq6urq6urq6urq6urp
6enw8PAKDQplbmRzdHJlYW0NZW5kb2JqDTg5OCAwIG9iajw8L0xlbmd0aCA0MC9XaWR0aCAxMy9I
ZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0
L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KQEBANjY2ODg4yMjI8fHx6urq6urq6urq6urq6urq6urq
6urq8PDwCg0KZW5kc3RyZWFtDWVuZG9iag04OTkgMCBvYmo8PC9MZW5ndGggNC9XaWR0aCAxL0hl
aWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3Qv
U3VidHlwZS9JbWFnZT4+c3RyZWFtDQqHlckKDQplbmRzdHJlYW0NZW5kb2JqDTkwMCAwIG9iajw8
L0xlbmd0aCAxNi9XaWR0aCA1L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNl
IDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQphdbw0TKY3T6M1S5+/
x+EKDQplbmRzdHJlYW0NZW5kb2JqDTkwMSAwIG9iajw8L0xlbmd0aCA3MC9GaWx0ZXIvRmxhdGVE
ZWNvZGUvV2lkdGggMzUvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUg
MCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCkiJcvn3jwGI/v8HoReXGBoY
GebaMPz6CuLeWM9wsAkqRSS6uJ63XtBpprtUd0RASCQPnywblzgDK39Dcz9AgAEAiwE3IwoNCmVu
ZHN0cmVhbQ1lbmRvYmoNOTAyIDAgb2JqPDwvTGVuZ3RoIDM0L1dpZHRoIDExL0hlaWdodCAxL0Jp
dHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9J
bWFnZT4+c3RyZWFtDQo2Nja6urr09PTq6urr6+vr6+vr6+vr6+vr6+vr6+vw8PAKDQplbmRzdHJl
YW0NZW5kb2JqDTkwMyAwIG9iajw8L0xlbmd0aCAzNy9XaWR0aCAxMi9IZWlnaHQgMS9CaXRzUGVy
Q29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+
PnN0cmVhbQ0KVlZWSkpK4+Pj7u7u6+vr6+vr6+vr6+vr6+vr6+vr6+vr9fX1Cg0KZW5kc3RyZWFt
DWVuZG9iag05MDQgMCBvYmo8PC9MZW5ndGggMzcvV2lkdGggMTIvSGVpZ2h0IDEvQml0c1BlckNv
bXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5z
dHJlYW0NCkZGRlFRUYyMjIqKiomJiYmJiYmJiYmJiYmJiYiIiIiIiKKiogoNCmVuZHN0cmVhbQ1l
bmRvYmoNOTA1IDAgb2JqPDwvTGVuZ3RoIDQwL1dpZHRoIDEzL0hlaWdodCAxL0JpdHNQZXJDb21w
b25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3Ry
ZWFtDQr4+Pjs7Ozr6+vr6+vr6+vr6+vr6+vr6+vr6+vr6+vr6+vr6+vy8vIKDQplbmRzdHJlYW0N
ZW5kb2JqDTkwNiAwIG9iajw8L0xlbmd0aCA0MC9XaWR0aCAxMy9IZWlnaHQgMS9CaXRzUGVyQ29t
cG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0
cmVhbQ0KQEBANjY2ODg4ycnJ8/Pz6+vr6+vr6+vr6+vr6+vr6+vr7Ozs8fHxCg0KZW5kc3RyZWFt
DWVuZG9iag05MDcgMCBvYmo8PC9MZW5ndGggNC9XaWR0aCAxL0hlaWdodCAxL0JpdHNQZXJDb21w
b25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3Ry
ZWFtDQrR1t0KDQplbmRzdHJlYW0NZW5kb2JqDTkwOCAwIG9iajw8L0xlbmd0aCAxNi9XaWR0aCA1
L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmpl
Y3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQp+jcZyh8Rqhb5aaarV2esKDQplbmRzdHJlYW0NZW5k
b2JqDTkwOSAwIG9iajw8L0xlbmd0aCA3My9GaWx0ZXIvRmxhdGVEZWNvZGUvV2lkdGggMzUvSGVp
Z2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9T
dWJ0eXBlL0ltYWdlPj5zdHJlYW0NCkiJ8vz/T+HNV5/X35R//2c43s1QwsCws5jh/38QOtLB8Poa
lE0kWh1l0qyitLHQrKZGT8OEhV2MnVuUgZE7LDwaIMAArZ82pwoNCmVuZHN0cmVhbQ1lbmRvYmoN
OTEwIDAgb2JqPDwvTGVuZ3RoIDQvV2lkdGggMS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgv
Q29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0Kzs/P
Cg0KZW5kc3RyZWFtDWVuZG9iag05MTEgMCBvYmo8PC9MZW5ndGggMzQvV2lkdGggMTEvSGVpZ2h0
IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0
eXBlL0ltYWdlPj5zdHJlYW0NCjY2Nr6+vvn5+fDw8PDw8PDw8PDw8PDw8PDw8PHx8fX19QoNCmVu
ZHN0cmVhbQ1lbmRvYmoNOTEyIDAgb2JqPDwvTGVuZ3RoIDM3L1dpZHRoIDEyL0hlaWdodCAxL0Jp
dHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9J
bWFnZT4+c3RyZWFtDQpWVlZLS0vo6Ojz8/Pw8PDw8PDw8PDw8PDw8PDw8PDx8fH4+PgKDQplbmRz
dHJlYW0NZW5kb2JqDTkxMyAwIG9iajw8L0xlbmd0aCAzNy9XaWR0aCAxMi9IZWlnaHQgMS9CaXRz
UGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1h
Z2U+PnN0cmVhbQ0KSEhIPDw8eXl5goKCgICAgICAgICAgICAgICAgICAfn5+lpaWCg0KZW5kc3Ry
ZWFtDWVuZG9iag05MTQgMCBvYmo8PC9MZW5ndGggNDAvV2lkdGggMTMvSGVpZ2h0IDEvQml0c1Bl
ckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdl
Pj5zdHJlYW0NCt3d3fT09PDw8PDw8PDw8PDw8PDw8PDw8PDw8PDw8PDw8O/v7/f39woNCmVuZHN0
cmVhbQ1lbmRvYmoNOTE1IDAgb2JqPDwvTGVuZ3RoIDQwL1dpZHRoIDEzL0hlaWdodCAxL0JpdHNQ
ZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFn
ZT4+c3RyZWFtDQpAQEA2NjY4ODjNzc339/fw8PDw8PDw8PDw8PDw8PDw8PDw8PD19fUKDQplbmRz
dHJlYW0NZW5kb2JqDTkxNiAwIG9iajw8L0xlbmd0aCAxOS9XaWR0aCA2L0hlaWdodCAxL0JpdHNQ
ZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFn
ZT4+c3RyZWFtDQqfr+Srt+Lk5e/o8/zV3+vz8vUKDQplbmRzdHJlYW0NZW5kb2JqDTkxNyAwIG9i
ajw8L0xlbmd0aCA4NS9GaWx0ZXIvRmxhdGVEZWNvZGUvV2lkdGggMzgvSGVpZ2h0IDEvQml0c1Bl
ckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdl
Pj5zdHJlYW0NCkiJWvj8w+lH7y+//Knx4TFDvxzDJE2GX98Y/v9n+PgYhIAM4tGH+8pTTZ23tsst
ne/lFsTFK8vOLcrGKcTAyKmtY9TS1jVt2oymxiaAAAMAhWQ9EAoNCmVuZHN0cmVhbQ1lbmRvYmoN
OTE4IDAgb2JqPDwvTGVuZ3RoIDM0L1dpZHRoIDExL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQg
OC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQo2
NjbAwMD9/f309PT09PT09PT09PT09PT09PT09PT4+PgKDQplbmRzdHJlYW0NZW5kb2JqDTkxOSAw
IG9iajw8L0xlbmd0aCAzNy9XaWR0aCAxMi9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29s
b3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KUlJSTExM
6+vr9/f39fX19PT09PT09fX19PT09PT09fX1+vr6Cg0KZW5kc3RyZWFtDWVuZG9iag05MjAgMCBv
Ymo8PC9MZW5ndGggMzcvV2lkdGggMTIvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9y
U3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCklJSTQ0NJ+f
n8fHx8HBwcLCwsLCwsHBwcHBwcHBwcDAwMjIyAoNCmVuZHN0cmVhbQ1lbmRvYmoNOTIxIDAgb2Jq
PDwvTGVuZ3RoIDI4L1dpZHRoIDkvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3Bh
Y2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCnp6epaWlpWVlZSU
lJSUlJSUlJSUlJSUlJSUlAoNCmVuZHN0cmVhbQ1lbmRvYmoNOTIyIDAgb2JqPDwvTGVuZ3RoIDM3
L1dpZHRoIDEyL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9U
eXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQrY2Nj6+vr09PT09PT09PT09PT09PT0
9PT09PT09PT09PT29vYKDQplbmRzdHJlYW0NZW5kb2JqDTkyMyAwIG9iajw8L0xlbmd0aCA0MC9X
aWR0aCAxMy9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlw
ZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KQEBANjY2ODg40dHR/Pz89PT09PT09PT0
9PT09PT09PT09PT0+fn5Cg0KZW5kc3RyZWFtDWVuZG9iag05MjQgMCBvYmo8PC9MZW5ndGggMTYv
V2lkdGggNS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlw
ZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KRl22fY3Gpq/MnafKsLrdCg0KZW5kc3Ry
ZWFtDWVuZG9iag05MjUgMCBvYmo8PC9MZW5ndGggNzkvRmlsdGVyL0ZsYXRlRGVjb2RlL1dpZHRo
IDM4L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hP
YmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpIiTr4+9fs26+nPXqX9P8/x/d3DNN0GfoVGa6v
Z/j/nwykemZD2JpWoYvXg+OTpWU1WTiE2TmFWDgEmZm5GRkYBQVFFBQUAQIMAKM4OgAKDQplbmRz
dHJlYW0NZW5kb2JqDTkyNiAwIG9iajw8L0xlbmd0aCAzNC9XaWR0aCAxMS9IZWlnaHQgMS9CaXRz
UGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1h
Z2U+PnN0cmVhbQ0KNjY2w8PD////+vr6+vr6+vr6+vr6+vr6+vr6+vr6/Pz8Cg0KZW5kc3RyZWFt
DWVuZG9iag05MjcgMCBvYmo8PC9MZW5ndGggMzcvV2lkdGggMTIvSGVpZ2h0IDEvQml0c1BlckNv
bXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5z
dHJlYW0NCj09PYaGhv////v7+/r6+vr6+vr6+vr6+vr6+vr6+vr6+v39/QoNCmVuZHN0cmVhbQ1l
bmRvYmoNOTI4IDAgb2JqPDwvTGVuZ3RoIDM3L1dpZHRoIDEyL0hlaWdodCAxL0JpdHNQZXJDb21w
b25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3Ry
ZWFtDQpJSUk1NTXMzMz///////////////////////////////////8KDQplbmRzdHJlYW0NZW5k
b2JqDTkyOSAwIG9iajw8L0xlbmd0aCAzMS9XaWR0aCAxMC9IZWlnaHQgMS9CaXRzUGVyQ29tcG9u
ZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVh
bQ0KSkpKg4ODjIyMiYmJiYmJiYmJiYmJioqKh4eHoaGhCg0KZW5kc3RyZWFtDWVuZG9iag05MzAg
MCBvYmo8PC9MZW5ndGggMzcvV2lkdGggMTIvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0Nv
bG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCp2dnf//
//v7+/r6+vr6+vr6+vr6+vr6+vr6+vr6+vr6+vz8/AoNCmVuZHN0cmVhbQ1lbmRvYmoNOTMxIDAg
b2JqPDwvTGVuZ3RoIDQwL1dpZHRoIDEzL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xv
clNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpAQEA2NjY4
ODjT09P////6+vr6+vr6+vr6+vr6+vr6+vr6+vr8/PwKDQplbmRzdHJlYW0NZW5kb2JqDTkzMiAw
IG9iajw8L0xlbmd0aCAxOS9XaWR0aCA2L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xv
clNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpMYbE5U6pI
XKM+Up09UJ/X2uYKDQplbmRzdHJlYW0NZW5kb2JqDTkzMyAwIG9iajw8L0xlbmd0aCA4MS9GaWx0
ZXIvRmxhdGVEZWNvZGUvV2lkdGggMzgvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9y
U3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCkiJmvT/P/f3
Xwqvv7L8/cvw/z/D03MMTRwMkzQYfnwEcUlEop+/BJ84zP7+jXV9rZGWCSObIDunMAuHACsrLxML
JwMDg6ioKECAAQA4NjmGCg0KZW5kc3RyZWFtDWVuZG9iag05MzQgMCBvYmo8PC9MZW5ndGggMzQv
V2lkdGggMTEvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5
cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCjY2NsXFxf//////////////////////
//////////7+/goNCmVuZHN0cmVhbQ1lbmRvYmoNOTM1IDAgb2JqPDwvTGVuZ3RoIDM3L1dpZHRo
IDEyL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hP
YmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpKSkqHh4f/////////////////////////////
///////+/v4KDQplbmRzdHJlYW0NZW5kb2JqDTkzNiAwIG9iajw8L0xlbmd0aCAzNy9XaWR0aCAx
Mi9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2Jq
ZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KlpaW////////////////////////////////////
/////v7+Cg0KZW5kc3RyZWFtDWVuZG9iag05MzcgMCBvYmo8PC9MZW5ndGggMzQvV2lkdGggMTEv
SGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVj
dC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCj4+PmZmZo6OjomJiYmJiYqKiomJiYmJiYmJiYqKipeX
lwoNCmVuZHN0cmVhbQ1lbmRvYmoNOTM4IDAgb2JqPDwvTGVuZ3RoIDQwL1dpZHRoIDEzL0hlaWdo
dCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3Vi
dHlwZS9JbWFnZT4+c3RyZWFtDQpAQEA1NTU5OTnW1tb////////////////////////////////+
/v4KDQplbmRzdHJlYW0NZW5kb2JqDTkzOSAwIG9iajw8L0xlbmd0aCAxOS9XaWR0aCA2L0hlaWdo
dCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3Vi
dHlwZS9JbWFnZT4+c3RyZWFtDQpNY7A+VKU9UqE7T507TZnQ1eYKDQplbmRzdHJlYW0NZW5kb2Jq
DTk0MCAwIG9iajw8L0xlbmd0aCA2OS9GaWx0ZXIvRmxhdGVEZWNvZGUvV2lkdGggMzgvSGVpZ2h0
IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0
eXBlL0ltYWdlPj5zdHJlYW0NCkiJqv33j+H/fxR0aRVDIxvD9fXo4kQg5n//nJ8+5/nxS3vqZGsX
OyZ2QXYOIRYOAVZWXiYWTgYGZhERUYAAAwB/PjqwCg0KZW5kc3RyZWFtDWVuZG9iag05NDEgMCBv
Ymo8PC9MZW5ndGggNy9XaWR0aCAyL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNw
YWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQo7Ozs0NDQKDQpl
bmRzdHJlYW0NZW5kb2JqDTk0MiAwIG9iajw8L0xlbmd0aCA3L1dpZHRoIDIvSGVpZ2h0IDEvQml0
c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0lt
YWdlPj5zdHJlYW0NClxcXDg4OAoNCmVuZHN0cmVhbQ1lbmRvYmoNOTQzIDAgb2JqPDwvTGVuZ3Ro
IDEwL1dpZHRoIDMvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBS
L1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NClBQUDQxM1FtVQoNCmVuZHN0cmVh
bQ1lbmRvYmoNOTQ0IDAgb2JqPDwvTGVuZ3RoIDM0L1dpZHRoIDExL0hlaWdodCAxL0JpdHNQZXJD
b21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+
c3RyZWFtDQo9PT1OTk6KioqIiIiHh4eHh4eHh4eHh4eHh4eGhoaRkZEKDQplbmRzdHJlYW0NZW5k
b2JqDTk0NSAwIG9iajw8L0xlbmd0aCA3L1dpZHRoIDIvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVu
dCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0N
ClVVVXNzcwoNCmVuZHN0cmVhbQ1lbmRvYmoNOTQ2IDAgb2JqPDwvTGVuZ3RoIDEwL1dpZHRoIDMv
SGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVj
dC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCkBAQDc3Nyk6OQoNCmVuZHN0cmVhbQ1lbmRvYmoNOTQ3
IDAgb2JqPDwvTGVuZ3RoIDE5L1dpZHRoIDYvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0Nv
bG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCkxgrT9U
oj1SnjtOnD5NmdbY5goNCmVuZHN0cmVhbQ1lbmRvYmoNOTQ4IDAgb2JqPDwvTGVuZ3RoIDY4L0Zp
bHRlci9GbGF0ZURlY29kZS9XaWR0aCAzOC9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29s
b3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KSIlqefmM
4ddPhv//UdDyMIbNBeiCxKB//1yeP5f591dkzarggGA2HjE2DiEWDgFWVl4mFk4GBiZhYRGAAAMA
rNQ7hgoNCmVuZHN0cmVhbQ1lbmRvYmoNOTQ5IDAgb2JqPDwvTGVuZ3RoIDcvV2lkdGggMi9IZWln
aHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1
YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KOzs7NTU1Cg0KZW5kc3RyZWFtDWVuZG9iag05NTAgMCBvYmo8
PC9MZW5ndGggMzcvV2lkdGggMTIvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3Bh
Y2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCkFBQTc3N3h4eJKS
ko6Ojo6Ojo6Ojo6Ojo6Ojo6Ojo6OjpycnAoNCmVuZHN0cmVhbQ1lbmRvYmoNOTUxIDAgb2JqPDwv
TGVuZ3RoIDEwL1dpZHRoIDMvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2Ug
MTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NClBQUDUyM1FsVgoNCmVu
ZHN0cmVhbQ1lbmRvYmoNOTUyIDAgb2JqPDwvTGVuZ3RoIDcvV2lkdGggMi9IZWlnaHQgMS9CaXRz
UGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1h
Z2U+PnN0cmVhbQ0KTU1Nfn5+Cg0KZW5kc3RyZWFtDWVuZG9iag05NTMgMCBvYmo8PC9MZW5ndGgg
MTAvV2lkdGggMy9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIv
VHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KQEBAODg2KjRECg0KZW5kc3RyZWFt
DWVuZG9iag05NTQgMCBvYmo8PC9MZW5ndGggODUvRmlsdGVyL0ZsYXRlRGVjb2RlL1dpZHRoIDQ0
L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmpl
Y3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpIifKOX2UTOM/Gf46h04SeaUef3XkqP2kGw///6GhL
McOhDizihBDbnz/BDx6I//snsH5dVGg0n6AMC7sAC4cACysvEwsHAwOTiLAoQIABAL9GRDMKDQpl
bmRzdHJlYW0NZW5kb2JqDTk1NSAwIG9iajw8L0xlbmd0aCAzNC9XaWR0aCAxMS9IZWlnaHQgMS9C
aXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUv
SW1hZ2U+PnN0cmVhbQ0KNzc3uLi48PDw5+fn5+fn5+fn5+fn5+fn5+fn5+fn7OzsCg0KZW5kc3Ry
ZWFtDWVuZG9iag05NTYgMCBvYmo8PC9MZW5ndGggMzcvV2lkdGggMTIvSGVpZ2h0IDEvQml0c1Bl
ckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdl
Pj5zdHJlYW0NCklJSX5+fvHx8efn5+fn5+fn5+fn5+fn5+fn5+fn5+jo6PLy8goNCmVuZHN0cmVh
bQ1lbmRvYmoNOTU3IDAgb2JqPDwvTGVuZ3RoIDM3L1dpZHRoIDEyL0hlaWdodCAxL0JpdHNQZXJD
b21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+
c3RyZWFtDQpJSUk2Nja9vb3v7+/n5+fn5+fn5+fn5+fn5+fn5+fm5ubr6+sKDQplbmRzdHJlYW0N
ZW5kb2JqDTk1OCAwIG9iajw8L0xlbmd0aCAzNy9XaWR0aCAxMi9IZWlnaHQgMS9CaXRzUGVyQ29t
cG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0
cmVhbQ0KQkJCLy8vfn5+4+Pj3d3d3Nzc3Nzc3Nzc3Nzc3Nzc29vb5OTkCg0KZW5kc3RyZWFtDWVu
ZG9iag05NTkgMCBvYmo8PC9MZW5ndGggMzcvV2lkdGggMTIvSGVpZ2h0IDEvQml0c1BlckNvbXBv
bmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJl
YW0NCkRERG5ubufn5+jo6Ofn5+fn5+fn5+fn5+fn5+fn5+fn5+jo6AoNCmVuZHN0cmVhbQ1lbmRv
YmoNOTYwIDAgb2JqPDwvTGVuZ3RoIDM0L1dpZHRoIDExL0hlaWdodCAxL0JpdHNQZXJDb21wb25l
bnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFt
DQo2NjasrKzg4ODY2NjY2NjY2NjY2NjY2NjX19fY2Njb29sKDQplbmRzdHJlYW0NZW5kb2JqDTk2
MSAwIG9iajw8L0xlbmd0aCA4OC9GaWx0ZXIvRmxhdGVEZWNvZGUvV2lkdGggNDMvSGVpZ2h0IDEv
Qml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBl
L0ltYWdlPj5zdHJlYW0NCkiJ8olfbeU329p7upHLhNVbbvZPXsGwbj3D///o6HA7Q5cYw4vLWKRw
I8b///0fPVL68YPh4vnQpBRFRS0WVn4WDgFWVl4mFk4GBmZhYRGAAAMAV4JBWQoNCmVuZHN0cmVh
bQ1lbmRvYmoNOTYyIDAgb2JqPDwvTGVuZ3RoIDM3L1dpZHRoIDEyL0hlaWdodCAxL0JpdHNQZXJD
b21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+
c3RyZWFtDQpLS0twcHDd3d3Z2dnY2NjY2NjY2NjY2NjY2NjX19fZ2dnk5OQKDQplbmRzdHJlYW0N
ZW5kb2JqDTk2MyAwIG9iajw8L0xlbmd0aCAzNy9XaWR0aCAxMi9IZWlnaHQgMS9CaXRzUGVyQ29t
cG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0
cmVhbQ0KSUlJNjY2srKy39/f2NjY2NjY2NjY2NjY2NjY2NjY2NjY3NzcCg0KZW5kc3RyZWFtDWVu
ZG9iag05NjQgMCBvYmo8PC9MZW5ndGggMzcvV2lkdGggMTIvSGVpZ2h0IDEvQml0c1BlckNvbXBv
bmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJl
YW0NCkJCQi8vL3h4eNvb29XV1dTU1NTU1NTU1NTU1NTU1NPT09jY2AoNCmVuZHN0cmVhbQ1lbmRv
YmoNOTY1IDAgb2JqPDwvTGVuZ3RoIDM3L1dpZHRoIDEyL0hlaWdodCAxL0JpdHNQZXJDb21wb25l
bnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFt
DQpERERNTU3Dw8Pd3d3Y2NjY2NjY2NjY2NjY2NjY2NjY2NjY2NgKDQplbmRzdHJlYW0NZW5kb2Jq
DTk2NiAwIG9iajw8L0xlbmd0aCA0MC9XaWR0aCAxMy9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50
IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0K
QEBANjY2ODg4urq639/f2NjY2NjY2NjY2NjY2NjY2NjY2dnZ3d3dCg0KZW5kc3RyZWFtDWVuZG9i
ag05NjcgMCBvYmo8PC9MZW5ndGggODQvRmlsdGVyL0ZsYXRlRGVjb2RlL1dpZHRoIDQyL0hlaWdo
dCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3Vi
dHlwZS9JbWFnZT4+c3RyZWFtDQpIifJJWG3lPcPcY6J7xJzNO687BpYynD7P8P8/OtpdyjDVgOHH
ZyxSuJHTq1fqnz8zfPzgXlhoYmDFyMLHyiHAwsrLxMLJwMAkJCQMEGAAY0I/swoNCmVuZHN0cmVh
bQ1lbmRvYmoNOTY4IDAgb2JqPDwvTGVuZ3RoIDM0L1dpZHRoIDExL0hlaWdodCAxL0JpdHNQZXJD
b21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+
c3RyZWFtDQo3Nzebm5vHx8fAwMDAwMDAwMDAwMDAwMDAwMDAwMDHx8cKDQplbmRzdHJlYW0NZW5k
b2JqDTk2OSAwIG9iajw8L0xlbmd0aCAzNy9XaWR0aCAxMi9IZWlnaHQgMS9CaXRzUGVyQ29tcG9u
ZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVh
bQ0KUFBQRUVFtbW1xMTEwMDAwMDAwMDAwMDAwMDAwMDAwMDA0tLSCg0KZW5kc3RyZWFtDWVuZG9i
ag05NzAgMCBvYmo8PC9MZW5ndGggMzcvV2lkdGggMTIvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVu
dCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0N
CklJSTU1NaCgoMbGxsDAwMDAwMDAwMDAwMDAwMDAwMDAwMTExAoNCmVuZHN0cmVhbQ1lbmRvYmoN
OTcxIDAgb2JqPDwvTGVuZ3RoIDM3L1dpZHRoIDEyL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQg
OC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpC
QkIwMDBxcXHFxcXBwcHAwMDAwMDAwMDAwMDAwMDAwMDDw8MKDQplbmRzdHJlYW0NZW5kb2JqDTk3
MiAwIG9iajw8L0xlbmd0aCAzNy9XaWR0aCAxMi9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgv
Q29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KQ0ND
QUFBoqKixcXFwMDAwMDAwMDAwMDAwMDAwMDAwMDAwsLCCg0KZW5kc3RyZWFtDWVuZG9iag05NzMg
MCBvYmo8PC9MZW5ndGggNDAvV2lkdGggMTMvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0Nv
bG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCkBAQDY2
Njg4OKenp8bGxsDAwMDAwMDAwMDAwMDAwMDAwMDAwMjIyAoNCmVuZHN0cmVhbQ1lbmRvYmoNOTc0
IDAgb2JqPDwvTGVuZ3RoIDgyL0ZpbHRlci9GbGF0ZURlY29kZS9XaWR0aCA0MS9IZWlnaHQgMS9C
aXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUv
SW1hZ2U+PnN0cmVhbQ0KSInyjVtt6THZ0LmvoHbjjJk7lZwLGV4+Z/j/HxX9Y1gdwXB7G4Y4PmTz
5o3Ju3dAhl5fp6eTOxMrPwu7ACsrLxMLJwMDk7CwKECAAQC54T7RCg0KZW5kc3RyZWFtDWVuZG9i
ag05NzUgMCBvYmo8PC9MZW5ndGggMzcvV2lkdGggMTIvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVu
dCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0N
CklJSTU1NZ+fn8TExL6+vr6+vr6+vr6+vr6+vr6+vr6+vsLCwgoNCmVuZHN0cmVhbQ1lbmRvYmoN
OTc2IDAgb2JqPDwvTGVuZ3RoIDM3L1dpZHRoIDEyL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQg
OC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpQ
UFBERESzs7PCwsK9vb2+vr6+vr6+vr6+vr6+vr69vb3Q0NAKDQplbmRzdHJlYW0NZW5kb2JqDTk3
NyAwIG9iajw8L0xlbmd0aCAzNy9XaWR0aCAxMi9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgv
Q29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KQkJC
MDAwcHBwxMTEvr6+vr6+vr6+vr6+vr6+vr6+vb29wsLCCg0KZW5kc3RyZWFtDWVuZG9iag05Nzgg
MCBvYmo8PC9MZW5ndGggMzcvV2lkdGggMTIvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0Nv
bG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCkNDQzc3
N4GBgcTExL6+vr6+vr6+vr6+vr6+vr6+vr6+vr+/vwoNCmVuZHN0cmVhbQ1lbmRvYmoNOTc5IDAg
b2JqPDwvTGVuZ3RoIDQwL1dpZHRoIDEzL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xv
clNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpAQEA2NjY4
ODilpaXDw8O+vr6+vr6+vr6+vr6+vr6+vr6+vr7GxsYKDQplbmRzdHJlYW0NZW5kb2JqDTk4MCAw
IG9iajw8L0xlbmd0aCA4NC9GaWx0ZXIvRmxhdGVEZWNvZGUvV2lkdGggNDEvSGVpZ2h0IDEvQml0
c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0lt
YWdlPj5zdHJlYW0NCkiJ8o1ZZuYx0cipp3/K5qr21eJeOQyvnzH8/4+Cvr5iWBrE8OEpujhe5PLs
mdGnTwz//lu29fo5ezOx8LOwC7Cw8jKxcDAwMImLSwAEGAC2yz7pCg0KZW5kc3RyZWFtDWVuZG9i
ag05ODEgMCBvYmo8PC9MZW5ndGggMzQvV2lkdGggMTEvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVu
dCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0N
Cjg4OHp6epeXl5OTk5OTk5OTk5OTk5OTk5OTk5KSkpycnAoNCmVuZHN0cmVhbQ1lbmRvYmoNOTgy
IDAgb2JqPDwvTGVuZ3RoIDM3L1dpZHRoIDEyL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9D
b2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpRUVFA
QECMjIyVlZWTk5OTk5OTk5OTk5OTk5OSkpKRkZGrq6sKDQplbmRzdHJlYW0NZW5kb2JqDTk4MyAw
IG9iajw8L0xlbmd0aCAzNy9XaWR0aCAxMi9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29s
b3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KSkpKNjY2
fX19l5eXk5OTk5OTk5OTk5OTk5OTk5OTkpKSlpaWCg0KZW5kc3RyZWFtDWVuZG9iag05ODQgMCBv
Ymo8PC9MZW5ndGggMzcvV2lkdGggMTIvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9y
U3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCkJCQjIyMl5e
XpeXl5OTk5OTk5OTk5OTk5OTk5OTk5OTk5aWlgoNCmVuZHN0cmVhbQ1lbmRvYmoNOTg1IDAgb2Jq
PDwvTGVuZ3RoIDM3L1dpZHRoIDEyL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNw
YWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpDQ0M4ODhqamqY
mJiTk5OTk5OTk5OTk5OTk5OTk5OTk5OVlZUKDQplbmRzdHJlYW0NZW5kb2JqDTk4NiAwIG9iajw8
L0xlbmd0aCA0MC9XaWR0aCAxMy9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFj
ZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KQEBANzc3ODg4goKC
l5eXk5OTk5OTk5OTk5OTk5OTk5OTk5OTnp6eCg0KZW5kc3RyZWFtDWVuZG9iag05ODcgMCBvYmo8
PC9MZW5ndGggODMvRmlsdGVyL0ZsYXRlRGVjb2RlL1dpZHRoIDQwL0hlaWdodCAxL0JpdHNQZXJD
b21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+
c3RyZWFtDQpIifKKXmzs3OcS2r9i8xHv8E7+9GqGfz8Y/v9HQdfWMSz0Y/jzC10cN7J//tz8/Xsg
Q2XWwvjgcE4uURZ2flZWXiYWLgYGJnFxCYAAAwDWCT0iCg0KZW5kc3RyZWFtDWVuZG9iag05ODgg
MCBvYmo8PC9MZW5ndGggMzQvV2lkdGggMTEvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0Nv
bG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCjk5OTo6
Ojs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozk5OUhISAoNCmVuZHN0cmVhbQ1lbmRvYmoNOTg5IDAgb2Jq
PDwvTGVuZ3RoIDM3L1dpZHRoIDEyL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNw
YWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpUVFQ1NTU7Ozs7
Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs2NjZiYmIKDQplbmRzdHJlYW0NZW5kb2JqDTk5MCAwIG9iajw8
L0xlbmd0aCAzNy9XaWR0aCAxMi9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFj
ZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KSkpKNjY2Ojo6PDw8
Ozs7PDw8PDw8Ozs7Ozs7Ozs7Ozs7PDw8Cg0KZW5kc3RyZWFtDWVuZG9iag05OTEgMCBvYmo8PC9M
ZW5ndGggMzcvV2lkdGggMTIvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2Ug
MTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCkJCQjc3Nzk5OTs7Ozs7
Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozw8PAoNCmVuZHN0cmVhbQ1lbmRvYmoNOTkyIDAgb2JqPDwvTGVu
Z3RoIDM3L1dpZHRoIDEyL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1
IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpBQUE7Ozs8PDw7Ozs7Ozs8
PDw8PDw7Ozs7Ozs7Ozs7Ozs9PT0KDQplbmRzdHJlYW0NZW5kb2JqDTk5MyAwIG9iajw8L0xlbmd0
aCA0MC9XaWR0aCAxMy9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAw
IFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KQEBANzc3ODg4Ojo6PDw8Ozs7
Ozs7Ozs7Ozs7Ozs7Ozs7OTk5SkpKCg0KZW5kc3RyZWFtDWVuZG9iag05OTQgMCBvYmo8PC9MZW5n
dGggODAvRmlsdGVyL0ZsYXRlRGVjb2RlL1dpZHRoIDM5L0hlaWdodCAxL0JpdHNQZXJDb21wb25l
bnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFt
DQpIifKMXKzt0JLfuXL6zB1m1qXcTR0M//8y/P+Pgq5vYDgxAV0QN7J8+dLm7VsgQ3DT+rSERDFR
eSZWPhZWXiYWDgYGJjExCYAAAwAqizvvCg0KZW5kc3RyZWFtDWVuZG9iag05OTUgMCBvYmo8PC9M
ZW5ndGggMzQvV2lkdGggMTEvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2Ug
MTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCjo6OisrKyUlJSYmJiYm
JiYmJiYmJiYmJiYmJiQkJDQ0NAoNCmVuZHN0cmVhbQ1lbmRvYmoNOTk2IDAgb2JqPDwvTGVuZ3Ro
IDM3L1dpZHRoIDEyL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAg
Ui9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpVVVUyMjInJycmJiYmJiYmJiYm
JiYmJiYmJiYmJiYhISFRUVEKDQplbmRzdHJlYW0NZW5kb2JqDTk5NyAwIG9iajw8L0xlbmd0aCAz
Ny9XaWR0aCAxMi9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIv
VHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KS0tLNjY2KysrJiYmJiYmJiYmJiYm
JiYmJycnJycnJiYmJycnCg0KZW5kc3RyZWFtDWVuZG9iag05OTggMCBvYmo8PC9MZW5ndGggMzcv
V2lkdGggMTIvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5
cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCkJCQjg4ODExMSUlJSYmJiYmJiYmJiYm
JiYmJiYmJiYmJicnJwoNCmVuZHN0cmVhbQ1lbmRvYmoNOTk5IDAgb2JqPDwvTGVuZ3RoIDM3L1dp
ZHRoIDEyL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBl
L1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQo7Ozs7OzsxMTElJSUmJiYmJiYmJiYmJiYn
JycnJycmJiYoKCgKDQplbmRzdHJlYW0NZW5kb2JqDTEwMDAgMCBvYmo8PC9MZW5ndGggNDAvV2lk
dGggMTMvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUv
WE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCkBAQDg4ODg4OCkpKSUlJSYmJiYmJiYmJiYm
JiYmJiYmJiQkJDY2NgoNCmVuZHN0cmVhbQ1lbmRvYmoNMTAwMSAwIG9iajw8L0xlbmd0aCA4My9G
aWx0ZXIvRmxhdGVEZWNvZGUvV2lkdGggMzgvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0Nv
bG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCkiJcg6Z
pBXYOnvx7vS8qboGeTz9sxn+/0dH1zcw3N7F8OgEw7ePWGRRkdGbN06vXgEZXPv2pmdkKCtrMzDz
sLLyMrFwMjAwiYmJAwQYAD0YOd4KDQplbmRzdHJlYW0NZW5kb2JqDTEwMDIgMCBvYmo8PC9MZW5n
dGggMzQvV2lkdGggMTEvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUg
MCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCjo6OjExMS8vLy8vLy8vLy8v
Ly8vLy8vLy8vLy0tLT09PQoNCmVuZHN0cmVhbQ1lbmRvYmoNMTAwMyAwIG9iajw8L0xlbmd0aCAz
Ny9XaWR0aCAxMi9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIv
VHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KVFRUNDQ0MDAwLy8vLy8vLy8vLy8v
Ly8vLy8vLy8vKioqWFhYCg0KZW5kc3RyZWFtDWVuZG9iag0xMDA0IDAgb2JqPDwvTGVuZ3RoIDM3
L1dpZHRoIDEyL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9U
eXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpKSko2NjYxMTEuLi4vLy8vLy8vLy8v
Ly8vLy8vLy8vLy8wMDAKDQplbmRzdHJlYW0NZW5kb2JqDTEwMDUgMCBvYmo8PC9MZW5ndGggMzcv
V2lkdGggMTIvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5
cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCkJCQjc3NzQ0NC8vLy8vLy8vLy8vLy8v
Ly8vLy8vLy8vLzAwMAoNCmVuZHN0cmVhbQ1lbmRvYmoNMTAwNiAwIG9iajw8L0xlbmd0aCAzNy9X
aWR0aCAxMi9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlw
ZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KOzs7Ozs7NDQ0Li4uLy8vLy8vLy8vLy8v
Ly8vLy8vLy8vMTExCg0KZW5kc3RyZWFtDWVuZG9iag0xMDA3IDAgb2JqPDwvTGVuZ3RoIDQwL1dp
ZHRoIDEzL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBl
L1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpAQEA4ODg4ODgxMTEvLy8vLy8vLy8vLy8v
Ly8vLy8vLy8tLS0/Pz8KDQplbmRzdHJlYW0NZW5kb2JqDTEwMDggMCBvYmo8PC9MZW5ndGggODYv
RmlsdGVyL0ZsYXRlRGVjb2RlL1dpZHRoIDM4L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9D
b2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpIiTIM
7fBNnT5/8Y7A2AnaBjm8zRMY/v9HR5eXM6wMYpigxHBhMRZZJMT0/3/Akyd6Hz8C2QKr12enpiso
aTOw8LCw8jKxcDIwMImJiQMEGAChPjefCg0KZW5kc3RyZWFtDWVuZG9iag0xMDA5IDAgb2JqPDwv
TGVuZ3RoIDM0L1dpZHRoIDExL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNl
IDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQo5OTk0NDQzMzMzMzMz
MzM0NDQzMzMzMzMzMzMyMjJBQUEKDQplbmRzdHJlYW0NZW5kb2JqDTEwMTAgMCBvYmo8PC9MZW5n
dGggMzcvV2lkdGggMTIvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUg
MCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NClRUVDQ0NDMzMzMzMzMzMzMz
MzMzMzMzMzMzMzMzMy4uLltbWwoNCmVuZHN0cmVhbQ1lbmRvYmoNMTAxMSAwIG9iajw8L0xlbmd0
aCAzNy9XaWR0aCAxMi9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAw
IFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KTExMNjY2NDQ0MzMzMzMzMzMz
MzMzMzMzMzMzMzMzMjIyNDQ0Cg0KZW5kc3RyZWFtDWVuZG9iag0xMDEyIDAgb2JqPDwvTGVuZ3Ro
IDM3L1dpZHRoIDEyL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAg
Ui9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpCQkI3Nzc2NjYzMzMzMzMzMzMz
MzMzMzMzMzMzMzMzMzM0NDQKDQplbmRzdHJlYW0NZW5kb2JqDTEwMTMgMCBvYmo8PC9MZW5ndGgg
MzcvV2lkdGggMTIvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBS
L1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCjw8PDk5OTc3NzMzMzMzMzMzMzMz
MzMzMzMzMzMzMy8vL0tLSwoNCmVuZHN0cmVhbQ1lbmRvYmoNMTAxNCAwIG9iajw8L0xlbmd0aCA0
MC9XaWR0aCAxMy9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIv
VHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KQEBAODg4ODg4NDQ0MjIyMzMzMzMz
MzMzMzMzMzMzMzMzMTExQ0NDCg0KZW5kc3RyZWFtDWVuZG9iag0xMDE1IDAgb2JqPDwvTGVuZ3Ro
IDkxL0ZpbHRlci9GbGF0ZURlY29kZS9XaWR0aCAzNy9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50
IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0K
SIky8+6oaFrV3rfewbdNSy+Nu3c2w///KOjfP4Yl7gzVDAy1jAwXFoEF/6GrASPmv38jHjwwff8e
yObYdzg+K0NHy4iBmYeVlZeJhZOBgVlURAwgwACCSTSKCg0KZW5kc3RyZWFtDWVuZG9iag0xMDE2
IDAgb2JqPDwvTGVuZ3RoIDM3L1dpZHRoIDEyL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9D
b2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpNTU02
NjY6Ojo8PDw7Ozs8PDw8PDw7Ozs7Ozs7Ozs7Ozs8PDwKDQplbmRzdHJlYW0NZW5kb2JqDTEwMTcg
MCBvYmo8PC9MZW5ndGggMzcvV2lkdGggMTIvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0Nv
bG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NClNTUzY2
Njs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7OzY2NmJiYgoNCmVuZHN0cmVhbQ1lbmRvYmoNMTAxOCAw
IG9iajw8L0xlbmd0aCAzNC9XaWR0aCAxMS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29s
b3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KOTk5Pj4+
QEBAQEBAQEBAQEBAQEBAQEBAQEBAPz8/TU1NCg0KZW5kc3RyZWFtDWVuZG9iag0xMDE5IDAgb2Jq
PDwvTGVuZ3RoIDM3L1dpZHRoIDEyL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNw
YWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpMTEw1NTU5OTk7
Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs9PT0KDQplbmRzdHJlYW0NZW5kb2JqDTEwMjAgMCBvYmo8
PC9MZW5ndGggMTA5L1dpZHRoIDM2L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNw
YWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpCUItKWI9lb5o3
RH0oL2QLorAA//8A//8A//8A//8A0KEAlSgAfgAAgQAAgQQAjBcAoUEA7NgA//8A//8A//8A//8A
//8A//8B/v5R4eEr7+8A//8B1NJZb28zMDkAAgoEBQ0CBAgAAAITExQKDQplbmRzdHJlYW0NZW5k
b2JqDTEwMjEgMCBvYmo8PC9MZW5ndGggMzcvV2lkdGggMTIvSGVpZ2h0IDEvQml0c1BlckNvbXBv
bmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJl
YW0NCllZWTU1NT8/P0BAQEBAQEBAQEBAQEBAQEBAQEBAQDw8PGZmZgoNCmVuZHN0cmVhbQ1lbmRv
YmoNMTAyMiAwIG9iajw8L0xlbmd0aCAzNy9XaWR0aCAxMi9IZWlnaHQgMS9CaXRzUGVyQ29tcG9u
ZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVh
bQ0KTU1NNzc3Pj4+QEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQUFBCg0KZW5kc3RyZWFtDWVuZG9i
ag0xMDIzIDAgb2JqPDwvTGVuZ3RoIDM3L1dpZHRoIDEyL0hlaWdodCAxL0JpdHNQZXJDb21wb25l
bnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFt
DQpCQkI2NjY8PDxBQUFAQEBAQEBAQEBAQEBAQEBAQEBAQEBBQUEKDQplbmRzdHJlYW0NZW5kb2Jq
DTEwMjQgMCBvYmo8PC9MZW5ndGggMzcvV2lkdGggMTIvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVu
dCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0N
Cj8/Pzc3Nzo6OkFBQUBAQEBAQEBAQEBAQEBAQEBAQD8/P0ZGRgoNCmVuZHN0cmVhbQ1lbmRvYmoN
MTAyNSAwIG9iajw8L0xlbmd0aCA0MC9XaWR0aCAxMy9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50
IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0K
QEBANzc3ODg4Pz8/QEBAQEBAQEBAQEBAQEBAQEBAQEBAPj4+T09PCg0KZW5kc3RyZWFtDWVuZG9i
ag0xMDI2IDAgb2JqPDwvTGVuZ3RoIDEwNi9XaWR0aCAzNS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9u
ZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVh
bQ0KPUyIQU+HYGqWLzp4IjdfB8C7AP//AP//AP//AMmUAHwAAH8AAIEAAIEAAH4AAHoAAIkUAOrU
AP//AP//AP//AP//AP//Av39TuLiLe7uAP//ANvYUXJvRD5FAAILBAUNAgQKAAADEhITCg0KZW5k
c3RyZWFtDWVuZG9iag0xMDI3IDAgb2JqPDwvTGVuZ3RoIDM0L1dpZHRoIDExL0hlaWdodCAxL0Jp
dHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9J
bWFnZT4+c3RyZWFtDQo5OTlAQEBFRUVERERERERERERERERERERERERCQkJRUVEKDQplbmRzdHJl
YW0NZW5kb2JqDTEwMjggMCBvYmo8PC9MZW5ndGggMzQvV2lkdGggMTEvSGVpZ2h0IDEvQml0c1Bl
ckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdl
Pj5zdHJlYW0NCktLSzw8PEVFRUREREREREREREREREREREREREBAQGZmZgoNCmVuZHN0cmVhbQ1l
bmRvYmoNMTAyOSAwIG9iajw8L0xlbmd0aCAzNy9XaWR0aCAxMi9IZWlnaHQgMS9CaXRzUGVyQ29t
cG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0
cmVhbQ0KUFBQODg4QUFBRERERERERERERERERERERERERERERERERUVFCg0KZW5kc3RyZWFtDWVu
ZG9iag0xMDMwIDAgb2JqPDwvTGVuZ3RoIDM3L1dpZHRoIDEyL0hlaWdodCAxL0JpdHNQZXJDb21w
b25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3Ry
ZWFtDQo/Pz83Nzc9PT1ERERERERERERERERERERERERERERERERFRUUKDQplbmRzdHJlYW0NZW5k
b2JqDTEwMzEgMCBvYmo8PC9MZW5ndGggMzcvV2lkdGggMTIvSGVpZ2h0IDEvQml0c1BlckNvbXBv
bmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJl
YW0NCkVFRTc3Nzs7O0RERERERERERERERERERERERERERENDQ0lJSQoNCmVuZHN0cmVhbQ1lbmRv
YmoNMTAzMiAwIG9iajw8L0xlbmd0aCA0MC9XaWR0aCAxMy9IZWlnaHQgMS9CaXRzUGVyQ29tcG9u
ZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVh
bQ0KQEBANzc3ODg4QkJCREREREREREREREREREREREREREREQkJCU1NTCg0KZW5kc3RyZWFtDWVu
ZG9iag0xMDMzIDAgb2JqPDwvTGVuZ3RoIDEwNi9XaWR0aCAzNS9IZWlnaHQgMS9CaXRzUGVyQ29t
cG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0
cmVhbQ0KPU2IT1uMVmCRKTlyKjBcIqSaAf//AP//APv3AJ8/AHoAAIEAAIEAAIEAAIEAAIEAAHsA
AMuYAP//AP//AP//AP//AP//I/HxadnZFff3AP//A76/Xm1rPj5CAAMLBAUMAgQJAAACExITCg0K
ZW5kc3RyZWFtDWVuZG9iag0xMDM0IDAgb2JqPDwvTGVuZ3RoIDM0L1dpZHRoIDExL0hlaWdodCAx
L0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlw
ZS9JbWFnZT4+c3RyZWFtDQo5OTlERERISEhISEhISEhISEhISEhISEhISEhHR0dVVVUKDQplbmRz
dHJlYW0NZW5kb2JqDTEwMzUgMCBvYmo8PC9MZW5ndGggMzQvV2lkdGggMTEvSGVpZ2h0IDEvQml0
c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0lt
YWdlPj5zdHJlYW0NCkxMTD4+PklJSUhISEhISEhISEhISEhISEhISERERGlpaQoNCmVuZHN0cmVh
bQ1lbmRvYmoNMTAzNiAwIG9iajw8L0xlbmd0aCAzNy9XaWR0aCAxMi9IZWlnaHQgMS9CaXRzUGVy
Q29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+
PnN0cmVhbQ0KU1NTOTk5RUVFSUlJSEhISEhISEhISEhISEhISEhISEhISkpKCg0KZW5kc3RyZWFt
DWVuZG9iag0xMDM3IDAgb2JqPDwvTGVuZ3RoIDM3L1dpZHRoIDEyL0hlaWdodCAxL0JpdHNQZXJD
b21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+
c3RyZWFtDQpPT080NDQ+Pj5JSUlISEhISEhISEhISEhISEhISEhISEhJSUkKDQplbmRzdHJlYW0N
ZW5kb2JqDTEwMzggMCBvYmo8PC9MZW5ndGggMzcvV2lkdGggMTIvSGVpZ2h0IDEvQml0c1BlckNv
bXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5z
dHJlYW0NCklJSTo6Ojw8PEhISEhISEhISEhISEhISEhISEhISEdHR05OTgoNCmVuZHN0cmVhbQ1l
bmRvYmoNMTAzOSAwIG9iajw8L0xlbmd0aCA0MC9XaWR0aCAxMy9IZWlnaHQgMS9CaXRzUGVyQ29t
cG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0
cmVhbQ0KQEBANzc3ODg4RUVFSUlJSEhISEhISEhISEhISEhISEhIR0dHV1dXCg0KZW5kc3RyZWFt
DWVuZG9iag0xMDQwIDAgb2JqPDwvTGVuZ3RoIDEwMy9XaWR0aCAzNC9IZWlnaHQgMS9CaXRzUGVy
Q29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+
PnN0cmVhbQ0KQVGIX2mUQ1B+KjdxKCxaEpCWAP//AP//ANSpAIAAAIAAAIEAAIEAAIEAAIEAAH4A
AIoZAPHkAP//AP//AP//AP//JfHxX93dEvr6AP//Cba9Y2ZqRkdKAAMMBAQMAgQJAAACExIUCg0K
ZW5kc3RyZWFtDWVuZG9iag0xMDQxIDAgb2JqPDwvTGVuZ3RoIDM0L1dpZHRoIDExL0hlaWdodCAx
L0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlw
ZS9JbWFnZT4+c3RyZWFtDQo5OTlHR0dPT09OTk5OTk5OTk5OTk5OTk5OTk5MTExbW1sKDQplbmRz
dHJlYW0NZW5kb2JqDTEwNDIgMCBvYmo8PC9MZW5ndGggMzQvV2lkdGggMTEvSGVpZ2h0IDEvQml0
c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0lt
YWdlPj5zdHJlYW0NCkxMTEFBQU9PT05OTk5OTk5OTk5OTk5OTk5OTkpKSm5ubgoNCmVuZHN0cmVh
bQ1lbmRvYmoNMTA0MyAwIG9iajw8L0xlbmd0aCAzNy9XaWR0aCAxMi9IZWlnaHQgMS9CaXRzUGVy
Q29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+
PnN0cmVhbQ0KVVVVOzs7SkpKT09PTk5OTk5OTk5OTk5OTk5OTk5OTU1NUVFRCg0KZW5kc3RyZWFt
DWVuZG9iag0xMDQ0IDAgb2JqPDwvTGVuZ3RoIDM0L1dpZHRoIDExL0hlaWdodCAxL0JpdHNQZXJD
b21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+
c3RyZWFtDQo/Pz84ODhLS0tPT09OTk5OTk5OTk5OTk5OTk5NTU1PT08KDQplbmRzdHJlYW0NZW5k
b2JqDTEwNDUgMCBvYmo8PC9MZW5ndGggMzcvV2lkdGggMTIvSGVpZ2h0IDEvQml0c1BlckNvbXBv
bmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJl
YW0NCk9PTzw8PD4+Pk5OTk5OTk5OTk5OTk5OTk5OTk5OTk5OTlBQUAoNCmVuZHN0cmVhbQ1lbmRv
YmoNMTA0NiAwIG9iajw8L0xlbmd0aCA0MC9XaWR0aCAxMy9IZWlnaHQgMS9CaXRzUGVyQ29tcG9u
ZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVh
bQ0KQEBANzc3ODg4SkpKT09PTk5OTk5OTk5OTk5OTk5OTk5OTExMXV1dCg0KZW5kc3RyZWFtDWVu
ZG9iag0xMDQ3IDAgb2JqPDwvTGVuZ3RoIDEwMC9XaWR0aCAzMy9IZWlnaHQgMS9CaXRzUGVyQ29t
cG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0
cmVhbQ0KSVeMZW6VNkR5KTdtJilXCIiKAP//AP//AKpXAHsAAIEAAIEAAIEAAIEAAIEAAHsAALp4
AP//AP//AP//AP//Mu7uXt7eCPv7AP//Cbe3ZnBoSEdLAAMMBAUNAgQJAAACFRUWCg0KZW5kc3Ry
ZWFtDWVuZG9iag0xMDQ4IDAgb2JqPDwvTGVuZ3RoIDM0L1dpZHRoIDExL0hlaWdodCAxL0JpdHNQ
ZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFn
ZT4+c3RyZWFtDQo5OTlOTk5YWFhXV1dXV1dXV1dXV1dXV1dXV1dWVlZiYmIKDQplbmRzdHJlYW0N
ZW5kb2JqDTEwNDkgMCBvYmo8PC9MZW5ndGggMzQvV2lkdGggMTEvSGVpZ2h0IDEvQml0c1BlckNv
bXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5z
dHJlYW0NCklJSUZGRllZWVdXV1dXV1dXV1dXV1dXV1dXV1NTU3V1dQoNCmVuZHN0cmVhbQ1lbmRv
YmoNMTA1MCAwIG9iajw8L0xlbmd0aCAzNy9XaWR0aCAxMi9IZWlnaHQgMS9CaXRzUGVyQ29tcG9u
ZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVh
bQ0KWVlZPDw8UFBQWFhYV1dXV1dXV1dXV1dXV1dXV1dXVVVVZ2dnCg0KZW5kc3RyZWFtDWVuZG9i
ag0xMDUxIDAgb2JqPDwvTGVuZ3RoIDM0L1dpZHRoIDExL0hlaWdodCAxL0JpdHNQZXJDb21wb25l
bnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFt
DQpAQEA5OTlSUlJXV1dXV1dXV1dXV1dXV1dXV1dXV1dYWFgKDQplbmRzdHJlYW0NZW5kb2JqDTEw
NTIgMCBvYmo8PC9MZW5ndGggNDAvV2lkdGggMTMvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4
L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCmNj
Y0ZGRjw8PE5OTllZWVdXV1dXV1dXV1dXV1dXV1dXV1RUVHFxcQoNCmVuZHN0cmVhbQ1lbmRvYmoN
MTA1MyAwIG9iajw8L0xlbmd0aCA0MC9XaWR0aCAxMy9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50
IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0K
QEBANzc3ODg4UVFRWFhYV1dXV1dXV1dXV1dXV1dXV1dXVVVVZGRkCg0KZW5kc3RyZWFtDWVuZG9i
ag0xMDU0IDAgb2JqPDwvTGVuZ3RoIDk3L1dpZHRoIDMyL0hlaWdodCAxL0JpdHNQZXJDb21wb25l
bnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFt
DQpRXZFibJAtOm0oN2onKVcKi4YA//8A7uAAihsAfwAAgQAAgQAAgQAAgQAAgAAAgwYA27oA//8A
//8A//9A5+dT4eEF/f0A//8HtLBnZWc/QEgABAwFBAwCBAkAAAIWFhcKDQplbmRzdHJlYW0NZW5k
b2JqDTEwNTUgMCBvYmo8PC9MZW5ndGggMzQvV2lkdGggMTEvSGVpZ2h0IDEvQml0c1BlckNvbXBv
bmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJl
YW0NCjk5OVJSUl1dXVtbW1tbW1tbW1tbW1tbW1tbW1paWmZmZgoNCmVuZHN0cmVhbQ1lbmRvYmoN
MTA1NiAwIG9iajw8L0xlbmd0aCAzNC9XaWR0aCAxMS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50
IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0K
Q0NDVFRUXV1dW1tbW1tbW1tbW1tbW1tbW1tbV1dXfn5+Cg0KZW5kc3RyZWFtDWVuZG9iag0xMDU3
IDAgb2JqPDwvTGVuZ3RoIDM3L1dpZHRoIDEyL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9D
b2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpWVlY/
Pz9RUVFcXFxbW1tbW1tbW1tbW1tbW1tbW1taWlpdXV0KDQplbmRzdHJlYW0NZW5kb2JqDTEwNTgg
MCBvYmo8PC9MZW5ndGggNDMvRmlsdGVyL0ZsYXRlRGVjb2RlL1dpZHRoIDI0L0hlaWdodCAxL0Jp
dHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9J
bWFnZT4+c3RyZWFtDQpIibK1tbWysgoNDY2JiYnGAEDBurq6yMhINzCIiorCVANRBhBgAG97GLUK
DQplbmRzdHJlYW0NZW5kb2JqDTEwNTkgMCBvYmo8PC9MZW5ndGggNDAvV2lkdGggMTMvSGVpZ2h0
IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0
eXBlL0ltYWdlPj5zdHJlYW0NCkBAQDc3Nzg4OFRUVF1dXVtbW1tbW1tbW1tbW1tbW1tbW1lZWWlp
aQoNCmVuZHN0cmVhbQ1lbmRvYmoNMTA2MCAwIG9iajw8L0xlbmd0aCA5Ny9XaWR0aCAzMi9IZWln
aHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1
YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KXWqTW2aIJTVnKDVqKSxZEWNxAfj7APXnAI0cAH0AAIEAAIEA
AIEAAIEAAIEAAHwAALdyAO/fAP//F/j4ZdvbK+/vAP//AP3/GoGGdGxsJyk0AAILBAUNAgQJAAAB
GBgaCg0KZW5kc3RyZWFtDWVuZG9iag0xMDYxIDAgb2JqPDwvTGVuZ3RoIDM0L1dpZHRoIDExL0hl
aWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3Qv
U3VidHlwZS9JbWFnZT4+c3RyZWFtDQo5OTlVVVVhYWFfX19fX19gYGBfX19fX19fX19eXl5ra2sK
DQplbmRzdHJlYW0NZW5kb2JqDTEwNjIgMCBvYmo8PC9MZW5ndGggNDUvRmlsdGVyL0ZsYXRlRGVj
b2RlL1dpZHRoIDIzL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAg
Ui9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpIifL19Y2IiEhISIhHBXFgMGfO
nObmZjc3N3d3dyA3HhtISkoCCDAAhNsZ5AoNCmVuZHN0cmVhbQ1lbmRvYmoNMTA2MyAwIG9iajw8
L0xlbmd0aCA0OC9GaWx0ZXIvRmxhdGVEZWNvZGUvV2lkdGggMjQvSGVpZ2h0IDEvQml0c1BlckNv
bXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5z
dHJlYW0NCkiJSkxMNDc3j4iISExMjMcGMjMzY2NjfXx8PD094+LiEhISMNUA9QIEGACipRnbCg0K
ZW5kc3RyZWFtDWVuZG9iag0xMDY0IDAgb2JqPDwvTGVuZ3RoIDQwL1dpZHRoIDEzL0hlaWdodCAx
L0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlw
ZS9JbWFnZT4+c3RyZWFtDQpAQEA3Nzc4ODhYWFhhYWFfX19fX19fX19fX19fX19fX19eXl5tbW0K
DQplbmRzdHJlYW0NZW5kb2JqDTEwNjUgMCBvYmo8PC9MZW5ndGggOTQvV2lkdGggMzEvSGVpZ2h0
IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0
eXBlL0ltYWdlPj5zdHJlYW0NCmRum1FciCMyaCg0ZCYqWhZFXwDu7gDs1ACFDQB/AACBAACBAACB
AACBAACBAACDBACPHgDZsCv3+2ja2h319QD//wD39CFsdndrcCYnMAADCwQFDQIECQAAARgYGQoN
CmVuZHN0cmVhbQ1lbmRvYmoNMTA2NiAwIG9iajw8L0xlbmd0aCAzNC9XaWR0aCAxMS9IZWlnaHQg
MS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5
cGUvSW1hZ2U+PnN0cmVhbQ0KOTk5V1dXZWVlY2NjY2NjY2NjY2NjY2NjY2NjYmJib29vCg0KZW5k
c3RyZWFtDWVuZG9iag0xMDY3IDAgb2JqPDwvTGVuZ3RoIDQ4L0ZpbHRlci9GbGF0ZURlY29kZS9X
aWR0aCAyMy9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlw
ZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KSIny9fWNjo5OTU1NxgCJiYmVlZUlJSV+
fn5eXl5AkZSUFExlaWlpAAEGAI/6Gk0KDQplbmRzdHJlYW0NZW5kb2JqDTEwNjggMCBvYmo8PC9M
ZW5ndGggNDgvRmlsdGVyL0ZsYXRlRGVjb2RlL1dpZHRoIDIzL0hlaWdodCAxL0JpdHNQZXJDb21w
b25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3Ry
ZWFtDQpIibK2tvbw8EhNTU3GAElJSdnZ2Tk5OWFhYZ6envHx8SkpKZjKgHoBAgwAa4sZpQoNCmVu
ZHN0cmVhbQ1lbmRvYmoNMTA2OSAwIG9iajw8L0xlbmd0aCA0MC9XaWR0aCAxMy9IZWlnaHQgMS9C
aXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUv
SW1hZ2U+PnN0cmVhbQ0KQEBANzc3ODg4W1tbZWVlY2NjY2NjY2NjY2NjY2NjY2NjYmJicXFxCg0K
ZW5kc3RyZWFtDWVuZG9iag0xMDcwIDAgb2JqPDwvTGVuZ3RoIDkxL1dpZHRoIDMwL0hlaWdodCAx
L0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlw
ZS9JbWFnZT4+c3RyZWFtDQpqdJ1JVIIjMGImM2ElK1wcM0gC0MoA58cAfwQAfwAAgQAAgQAAgQAA
gQAAgQAAfAAJhBJOw7Bg3+QP+fkA//8C5eYvXV55cXEhIy0AAwsEBQ0CBAgAAAIVFRYKDQplbmRz
dHJlYW0NZW5kb2JqDTEwNzEgMCBvYmo8PC9MZW5ndGggMzQvV2lkdGggMTEvSGVpZ2h0IDEvQml0
c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0lt
YWdlPj5zdHJlYW0NCjk5OVpaWmtra2hoaGhoaGhoaGhoaGhoaGhoaGdnZ3NzcwoNCmVuZHN0cmVh
bQ1lbmRvYmoNMTA3MiAwIG9iajw8L0xlbmd0aCA0NC9GaWx0ZXIvRmxhdGVEZWNvZGUvV2lkdGgg
MjMvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9i
amVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCkiJ8vX1TUhIyMzMzMAAaWlpRUVFtbW1YWFhoaGh
mAogIDs7GyDAALmgG5QKDQplbmRzdHJlYW0NZW5kb2JqDTEwNzMgMCBvYmo8PC9MZW5ndGggNDgv
RmlsdGVyL0ZsYXRlRGVjb2RlL1dpZHRoIDIzL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9D
b2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpIibKy
svLy8srKysrAAGlpaUVFReXl5fHx8X5+fsnJyZmZmZjKgHoBAgwAl7YbAQoNCmVuZHN0cmVhbQ1l
bmRvYmoNMTA3NCAwIG9iajw8L0xlbmd0aCA0MC9XaWR0aCAxMy9IZWlnaHQgMS9CaXRzUGVyQ29t
cG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0
cmVhbQ0KQEBANzc3ODg4X19fampqaGhoaGhoaGhoaGhoaGhoaGhoZ2dndXV1Cg0KZW5kc3RyZWFt
DWVuZG9iag0xMDc1IDAgb2JqPDwvTGVuZ3RoIDg4L1dpZHRoIDI5L0hlaWdodCAxL0JpdHNQZXJD
b21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+
c3RyZWFtDQpzfqFGUHYiLl4jMF8mL1olJz8JpZQA8t0AlS0AfgAAgQAAgQAAgQAAgQAAfwAOhg9Z
lVJbxr8J/v8A//8Bv8ZDU1d7dHUZGiQABAwEBQ0CBAkAAAIUFBUKDQplbmRzdHJlYW0NZW5kb2Jq
DTEwNzYgMCBvYmo8PC9MZW5ndGggMzQvV2lkdGggMTEvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVu
dCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0N
Cjk5OWBgYHJycm9vb29vb3BwcG9vb29vb29vb25ubnp6egoNCmVuZHN0cmVhbQ1lbmRvYmoNMTA3
NyAwIG9iajw8L0xlbmd0aCA0NS9GaWx0ZXIvRmxhdGVEZWNvZGUvV2lkdGggMjMvSGVpZ2h0IDEv
Qml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBl
L0ltYWdlPj5zdHJlYW0NCkiJ8vb2zsjIKCgoyMcAubm5NTU1DQ0NMTExycnJWNUAQVFREUCAAQD3
QR1xCg0KZW5kc3RyZWFtDWVuZG9iag0xMDc4IDAgb2JqPDwvTGVuZ3RoIDQ3L0ZpbHRlci9GbGF0
ZURlY29kZS9XaWR0aCAyMy9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAx
NSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KSImytraOi4srKirKxwB5
eXk1NTV1dXUpKSkxMTEFBQWYaoCgsLAQIMAA5JkdJgoNCmVuZHN0cmVhbQ1lbmRvYmoNMTA3OSAw
IG9iajw8L0xlbmd0aCA0MC9XaWR0aCAxMy9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29s
b3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KQEBANzc3
ODg4ZWVlcnJyb29vb29vb29vb29vb29vb29vbm5ufHx8Cg0KZW5kc3RyZWFtDWVuZG9iag0xMDgw
IDAgb2JqPDwvTGVuZ3RoIDg4L1dpZHRoIDI5L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9D
b2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpzfKJA
SnQhLV4kMFsjLlopKk8YU0wB3dgAwXoAfAAAgAAAgQAAgQAAgAALfg5TmldPlkoUmT0A+/IA7/Ec
Y2R0ampVV1sFBxIDBg4EBQwCBAgAAAIVFRYKDQplbmRzdHJlYW0NZW5kb2JqDTEwODEgMCBvYmo8
PC9MZW5ndGggNDcvRmlsdGVyL0ZsYXRlRGVjb2RlL1dpZHRoIDIzL0hlaWdodCAxL0JpdHNQZXJD
b21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+
c3RyZWFtDQpIibKysgoKCqqoqCjFACUlJVVVVc3NzXl5eRkZGWVlZZhqgKC8vBwgwAAJiR58Cg0K
ZW5kc3RyZWFtDWVuZG9iag0xMDgyIDAgb2JqPDwvTGVuZ3RoIDQ2L0ZpbHRlci9GbGF0ZURlY29k
ZS9XaWR0aCAyMy9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIv
VHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KSIny8vLKzs4uLy8vxQAlJSV1dXVt
bW2ZYFBWVoappqioaNKkSQABBgAqiR9FCg0KZW5kc3RyZWFtDWVuZG9iag0xMDgzIDAgb2JqPDwv
TGVuZ3RoIDM0L1dpZHRoIDExL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNl
IDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQo4ODhlZWV5eXl2dnZ2
dnZ2dnZ2dnZ2dnZ2dnZ1dXWAgIAKDQplbmRzdHJlYW0NZW5kb2JqDTEwODQgMCBvYmo8PC9MZW5n
dGggODUvV2lkdGggMjgvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUg
MCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCnZ+mzpFcR8rWSQvWSArVyUs
VCcvPQ2CigCyawCHBACAAAB/AAN9ADWNOGmgazuROQOBAADGiACysDVHRIF6eTs/QwEDDQQHEAQF
DAIECQAAAhQUFQoNCmVuZHN0cmVhbQ1lbmRvYmoNMTA4NSAwIG9iajw8L0xlbmd0aCA0NS9GaWx0
ZXIvRmxhdGVEZWNvZGUvV2lkdGggMjMvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9y
U3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCkiJCgoKys7O
Li8vL8MApaWlFRUV7e3t1dXV+fn5mAogaiorKwECDAA8OB97Cg0KZW5kc3RyZWFtDWVuZG9iag0x
MDg2IDAgb2JqPDwvTGVuZ3RoIDQ1L0ZpbHRlci9GbGF0ZURlY29kZS9XaWR0aCAyMy9IZWlnaHQg
MS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5
cGUvSW1hZ2U+PnN0cmVhbQ0KSImytbX18/OrqKgoLy8vQwWlpaVVVVXt7e1AqaKiIkwFEAAUBwgw
ABeKHu4KDQplbmRzdHJlYW0NZW5kb2JqDTEwODcgMCBvYmo8PC9MZW5ndGggNDAvV2lkdGggMTMv
SGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVj
dC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCkBAQDc3Nzg4OGpqanl5eXZ2dnZ2dnZ2dnZ2dnZ2dnZ2
dnV1dYODgwoNCmVuZHN0cmVhbQ1lbmRvYmoNMTA4OCAwIG9iajw8L0xlbmd0aCA4Mi9XaWR0aCAy
Ny9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2Jq
ZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KeYGeOkZuHytVIixYHytUISdQLTlLG0BECoh3AJM5
CIkYGYgtXqRtZ6lrHJMyAIUTAI9JFVVHZl9hdHN1HB8oAgQOBAgQBAUNAgQJAAADEhIUCg0KZW5k
c3RyZWFtDWVuZG9iag0xMDg5IDAgb2JqPDwvTGVuZ3RoIDM3L0ZpbHRlci9GbGF0ZURlY29kZS9X
aWR0aCAyMy9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlw
ZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KSIlycXEJDAxsbGyswwbq6+vb2toaGhqw
ykIAUBYgwABbWCDyCg0KZW5kc3RyZWFtDWVuZG9iag0xMDkwIDAgb2JqPDwvTGVuZ3RoIDQzL0Zp
bHRlci9GbGF0ZURlY29kZS9XaWR0aCAyMi9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29s
b3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KSIkKDw9v
aGior6+vQwVAkdra2sbGxra2NiCjDhsAijc1NQEEGAApHiA4Cg0KZW5kc3RyZWFtDWVuZG9iag0x
MDkxIDAgb2JqPDwvTGVuZ3RoIDM0L0ZpbHRlci9GbGF0ZURlY29kZS9XaWR0aCAyMy9IZWlnaHQg
MS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5
cGUvSW1hZ2U+PnN0cmVhbQ0KSIny9PTMy8vr6upqwwZaW1uxiiMrmDBhAkCAAQCwWiNECg0KZW5k
c3RyZWFtDWVuZG9iag0xMDkyIDAgb2JqPDwvTGVuZ3RoIDc5L1dpZHRoIDI2L0hlaWdodCAxL0Jp
dHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9J
bWFnZT4+c3RyZWFtDQp7hadLVHEbJ1QeKVMfJk4YJEYoMlI3OEogOEM8kZZipKZWmaNFhmEMgzcB
gVsZSEVGSUqCfn9NTVQIDRcFBxEFCBEEBQ0CBAkAAAISEhMKDQplbmRzdHJlYW0NZW5kb2JqDTEw
OTMgMCBvYmo8PC9MZW5ndGggMjkvRmlsdGVyL0ZsYXRlRGVjb2RlL1dpZHRoIDIyL0hlaWdodCAx
L0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlw
ZS9JbWFnZT4+c3RyZWFtDQpIiUpNTW1ubm5vb28jHbS2tvb09AAEGABrRSIzCg0KZW5kc3RyZWFt
DWVuZG9iag0xMDk0IDAgb2JqPDwvTGVuZ3RoIDQwL1dpZHRoIDEzL0hlaWdodCAxL0JpdHNQZXJD
b21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+
c3RyZWFtDQpAQEA3Nzc4ODh4eHiJiYmGhoaGhoaGhoaGhoaGhoaGhoaGhoaSkpIKDQplbmRzdHJl
YW0NZW5kb2JqDTEwOTUgMCBvYmo8PC9MZW5ndGggNzkvV2lkdGggMjYvSGVpZ2h0IDEvQml0c1Bl
ckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdl
Pj5zdHJlYW0NCnqDo2huhC04XCAqUiIrTSYxTSkxUFJXbYKCjYuIkYCDg0xXYCM+OyU4MTI2Omxp
a35+gU1PWAwQHgQIEgYJEgQIDwQFDQIECAAAAhUVFwoNCmVuZHN0cmVhbQ1lbmRvYmoNMTA5NiAw
IG9iajw8L0xlbmd0aCAzNC9XaWR0aCAxMS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29s
b3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KODg4dHR0
jo6OioqKioqKioqKioqKioqKioqKiYmJk5OTCg0KZW5kc3RyZWFtDWVuZG9iag0xMDk3IDAgb2Jq
PDwvTGVuZ3RoIDI5L0ZpbHRlci9GbGF0ZURlY29kZS9XaWR0aCAyMi9IZWlnaHQgMS9CaXRzUGVy
Q29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+
PnN0cmVhbQ0KSImKiorq6enp7u7uIh10dnZOnToVIMAAhiQjLAoNCmVuZHN0cmVhbQ1lbmRvYmoN
MTA5OCAwIG9iajw8L0xlbmd0aCAyNi9GaWx0ZXIvRmxhdGVEZWNvZGUvV2lkdGggMjIvSGVpZ2h0
IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0
eXBlL0ltYWdlPj5zdHJlYW0NCkiJ8vLyamho6O3t7SILdHd3AwQYAHJxIsMKDQplbmRzdHJlYW0N
ZW5kb2JqDTEwOTkgMCBvYmo8PC9MZW5ndGggNDAvV2lkdGggMTMvSGVpZ2h0IDEvQml0c1BlckNv
bXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5z
dHJlYW0NCkBAQDc3Nzg4OHt7e42NjYqKioqKioqKioqKioqKioqKiomJiZWVlQoNCmVuZHN0cmVh
bQ1lbmRvYmoNMTEwMCAwIG9iajw8L0xlbmd0aCA3Ni9XaWR0aCAyNS9IZWlnaHQgMS9CaXRzUGVy
Q29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+
PnN0cmVhbQ0KZW6OgISXY2qBT1p9V2KHY2uDfH+JfoOPcHeMaGlzV1ldZmZrbGpydHN4amtvS09Y
FBkoBQgWBwsVBwkSBAgQBAUMAgQJAAACFxcYCg0KZW5kc3RyZWFtDWVuZG9iag0xMTAxIDAgb2Jq
PDwvTGVuZ3RoIDM0L1dpZHRoIDExL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNw
YWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQo4ODh3d3eSkpKO
jo6Ojo6Ojo6Ojo6Ojo6Ojo6Ojo6Xl5cKDQplbmRzdHJlYW0NZW5kb2JqDTExMDIgMCBvYmo8PC9M
ZW5ndGggMjMvRmlsdGVyL0ZsYXRlRGVjb2RlL1dpZHRoIDIyL0hlaWdodCAxL0JpdHNQZXJDb21w
b25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3Ry
ZWFtDQpIiSorK+sjF/T09KxatQogwAC5KiSjCg0KZW5kc3RyZWFtDWVuZG9iag0xMTAzIDAgb2Jq
PDwvTGVuZ3RoIDI1L0ZpbHRlci9GbGF0ZURlY29kZS9XaWR0aCAyMi9IZWlnaHQgMS9CaXRzUGVy
Q29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+
PnN0cmVhbQ0KSIny9/cvKSmZPHlyH1kAqBEgwACLmiOwCg0KZW5kc3RyZWFtDWVuZG9iag0xMTA0
IDAgb2JqPDwvTGVuZ3RoIDQwL1dpZHRoIDEzL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9D
b2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpAQEA3
Nzc5OTl+fn6RkZGOjo6Ojo6Ojo6Ojo6Ojo6Ojo6NjY2ZmZkKDQplbmRzdHJlYW0NZW5kb2JqDTEx
MDUgMCBvYmo8PC9MZW5ndGggNzMvV2lkdGggMjQvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4
L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCkRQ
fmVshIWHlHh/mmlzlmZrfk5TZzg/VDE4TDI/UUVWZVZhc1RfcDxEUyYrOxIVJggLGggMFgcJEwQI
EAUFDQMECQAAAhYWFwoNCmVuZHN0cmVhbQ1lbmRvYmoNMTEwNiAwIG9iajw8L0xlbmd0aCAzMS9G
aWx0ZXIvRmxhdGVEZWNvZGUvV2lkdGggMjEvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0Nv
bG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCkiJSk5O
njRp0rRp06aSCCZPnrx48WKAAAMAcFIkNAoNCmVuZHN0cmVhbQ1lbmRvYmoNMTEwNyAwIG9iajw8
L0xlbmd0aCAzNC9GaWx0ZXIvRmxhdGVEZWNvZGUvV2lkdGggMjEvSGVpZ2h0IDEvQml0c1BlckNv
bXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5z
dHJlYW0NCkiJ6urqmjp16rRp06ZiA7jEgWDKlCkLFiwACDAAjxgkrwoNCmVuZHN0cmVhbQ1lbmRv
YmoNMTEwOCAwIG9iajw8L0xlbmd0aCAyOC9XaWR0aCA5L0hlaWdodCAxL0JpdHNQZXJDb21wb25l
bnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFt
DQpcX2oDBxMGCRMFCRIECA8EBAwCBAgAAAIbGxwKDQplbmRzdHJlYW0NZW5kb2JqDTExMDkgMCBv
Ymo8PC9MZW5ndGggMjUvV2lkdGggOC9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JT
cGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KLThhMDlZQkld
Nj1XLjdTHiZGChI0bHCBCg0KZW5kc3RyZWFtDWVuZG9iag0xMTEwIDAgb2JqPDwvTGVuZ3RoIDM0
L1dpZHRoIDExL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9U
eXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQo3NzeBgYGhoaGcnJycnJycnJycnJyc
nJycnJybm5ukpKQKDQplbmRzdHJlYW0NZW5kb2JqDTExMTEgMCBvYmo8PC9MZW5ndGggMjcvRmls
dGVyL0ZsYXRlRGVjb2RlL1dpZHRoIDIxL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xv
clNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpIieru7p4/
f/4c0sHs2bM3btwIEGAAwyMmdwoNCmVuZHN0cmVhbQ1lbmRvYmoNMTExMiAwIG9iajw8L0xlbmd0
aCAyNy9GaWx0ZXIvRmxhdGVEZWNvZGUvV2lkdGggMjEvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVu
dCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0N
CkiJKigomDVr1ty5c+eQDubPnw8QYACsWyXnCg0KZW5kc3RyZWFtDWVuZG9iag0xMTEzIDAgb2Jq
PDwvTGVuZ3RoIDQwL1dpZHRoIDEzL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNw
YWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpAQEA2NjY4ODiJ
iYmgoKCcnJycnJycnJycnJycnJycnJycnJympqYKDQplbmRzdHJlYW0NZW5kb2JqDTExMTQgMCBv
Ymo8PC9MZW5ndGggMjUvV2lkdGggOC9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JT
cGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KLTVeGCFGFSFD
FyBDFiBAFh8+Dxc1UlhtCg0KZW5kc3RyZWFtDWVuZG9iag0xMTE1IDAgb2JqPDwvTGVuZ3RoIDI1
L1dpZHRoIDgvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5
cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCi4xOwEEDgYIEgQHEAQFDAIECAAAAhoZ
GwoNCmVuZHN0cmVhbQ1lbmRvYmoNMTExNiAwIG9iajw8L0xlbmd0aCAzNC9XaWR0aCAxMS9IZWln
aHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1
YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KNzc3g4ODpKSkn5+fn5+fn5+fn5+fn5+fn5+fnp6ep6enCg0K
ZW5kc3RyZWFtDWVuZG9iag0xMTE3IDAgb2JqPDwvTGVuZ3RoIDI0L0ZpbHRlci9GbGF0ZURlY29k
ZS9XaWR0aCAyMC9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIv
VHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KSImaMmXKfNLBvHnzVq9eDRBgAGmw
JUUKDQplbmRzdHJlYW0NZW5kb2JqDTExMTggMCBvYmo8PC9MZW5ndGggMjcvRmlsdGVyL0ZsYXRl
RGVjb2RlL1dpZHRoIDIwL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1
IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpIiWpubl68ePF8EsG8efOW
Ll0KEGAAYGslDAoNCmVuZHN0cmVhbQ1lbmRvYmoNMTExOSAwIG9iajw8L0xlbmd0aCA0MC9XaWR0
aCAxMy9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9Y
T2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KQEBANjY2ODg4jIyMo6Ojn5+fn5+fn5+fn5+f
n5+fn5+fn5+fqampCg0KZW5kc3RyZWFtDWVuZG9iag0xMTIwIDAgb2JqPDwvTGVuZ3RoIDIyL1dp
ZHRoIDcvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUv
WE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCio0VxsmRxwlRxkkQxghQA8YNUJIYAoNCmVu
ZHN0cmVhbQ1lbmRvYmoNMTEyMSAwIG9iajw8L0xlbmd0aCAyNS9XaWR0aCA4L0hlaWdodCAxL0Jp
dHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9J
bWFnZT4+c3RyZWFtDQouMDkABA0FCBIEBw8EBAsBBAgAAAEaGRoKDQplbmRzdHJlYW0NZW5kb2Jq
DTExMjIgMCBvYmo8PC9MZW5ndGggMzQvV2lkdGggMTEvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVu
dCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0N
Cjc3N4mJia6urqioqKioqKioqKioqKioqKioqKenp7CwsAoNCmVuZHN0cmVhbQ1lbmRvYmoNMTEy
MyAwIG9iajw8L0xlbmd0aCAyNC9GaWx0ZXIvRmxhdGVEZWNvZGUvV2lkdGggMjAvSGVpZ2h0IDEv
Qml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBl
L0ltYWdlPj5zdHJlYW0NCkiJ2rx58wrSwfLly3fs2AEQYAC5VCevCg0KZW5kc3RyZWFtDWVuZG9i
ag0xMTI0IDAgb2JqPDwvTGVuZ3RoIDI4L0ZpbHRlci9GbGF0ZURlY29kZS9XaWR0aCAyMC9IZWln
aHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1
YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KSImaOnXq6tWrV5AIli1btmfPHoAAAwCmlydnCg0KZW5kc3Ry
ZWFtDWVuZG9iag0xMTI1IDAgb2JqPDwvTGVuZ3RoIDQwL1dpZHRoIDEzL0hlaWdodCAxL0JpdHNQ
ZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFn
ZT4+c3RyZWFtDQpAQEA2NjY4ODiTk5OsrKyoqKioqKioqKioqKioqKioqKinp6exsbEKDQplbmRz
dHJlYW0NZW5kb2JqDTExMjYgMCBvYmo8PC9MZW5ndGggMjIvV2lkdGggNy9IZWlnaHQgMS9CaXRz
UGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1h
Z2U+PnN0cmVhbQ0KKDRVGyRGGyREGCJBGSA/DhYzTFJpCg0KZW5kc3RyZWFtDWVuZG9iag0xMTI3
IDAgb2JqPDwvTGVuZ3RoIDIyL1dpZHRoIDcvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0Nv
bG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCistNQAD
DAQIEAQFDQIECQAAAhQUFQoNCmVuZHN0cmVhbQ1lbmRvYmoNMTEyOCAwIG9iajw8L0xlbmd0aCAz
NC9XaWR0aCAxMS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIv
VHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KNzc3jIyMsbGxq6urq6urq6urq6ur
q6urq6urq6urs7OzCg0KZW5kc3RyZWFtDWVuZG9iag0xMTI5IDAgb2JqPDwvTGVuZ3RoIDI4L0Zp
bHRlci9GbGF0ZURlY29kZS9XaWR0aCAxOS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29s
b3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KSInau3fv
ypUrV5MCVq1atW3bNoAAAwBbYSZiCg0KZW5kc3RyZWFtDWVuZG9iag0xMTMwIDAgb2JqPDwvTGVu
Z3RoIDI0L0ZpbHRlci9GbGF0ZURlY29kZS9XaWR0aCAxOS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9u
ZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVh
bQ0KSInauHHjahLBypUr9+3bBxBgAFTgJlkKDQplbmRzdHJlYW0NZW5kb2JqDTExMzEgMCBvYmo8
PC9MZW5ndGggNDAvV2lkdGggMTMvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3Bh
Y2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCkBAQDY2Njg4OJWV
lbCwsKurq6urq6urq6urq6urq6urq6urq7S0tAoNCmVuZHN0cmVhbQ1lbmRvYmoNMTEzMiAwIG9i
ajw8L0xlbmd0aCAyOC9XaWR0aCA5L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNw
YWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQonMFQaI0MYIkEY
ID4OFzQ3P1XBxM7AxM/Y2eAKDQplbmRzdHJlYW0NZW5kb2JqDTExMzMgMCBvYmo8PC9MZW5ndGgg
MzEvV2lkdGggMTAvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBS
L1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCtXV2MTEx8XGykRGTAAACAQIDwQF
DAIECAAAAhUVFwoNCmVuZHN0cmVhbQ1lbmRvYmoNMTEzNCAwIG9iajw8L0xlbmd0aCAzNC9XaWR0
aCAxMS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9Y
T2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KNzc3kJCQt7e3sbGxsbGxsrKysbGxsbGxsbGx
sbGxubm5Cg0KZW5kc3RyZWFtDWVuZG9iag0xMTM1IDAgb2JqPDwvTGVuZ3RoIDI0L0ZpbHRlci9G
bGF0ZURlY29kZS9XaWR0aCAxOC9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFj
ZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KSIk6dOjQhg0bNpIC
9uzZAxBgAA1qJagKDQplbmRzdHJlYW0NZW5kb2JqDTExMzYgMCBvYmo8PC9MZW5ndGggMjQvRmls
dGVyL0ZsYXRlRGVjb2RlL1dpZHRoIDE4L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xv
clNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpIidqxY8dG
UsCGDRt27NgBEGAAB6MlfgoNCmVuZHN0cmVhbQ1lbmRvYmoNMTEzNyAwIG9iajw8L0xlbmd0aCA0
MC9XaWR0aCAxMy9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIv
VHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KPj4+Nzc3ODg4m5ubtra2sbGxsbGx
sbGxsbGxsbGxsbGxsbGxurq6Cg0KZW5kc3RyZWFtDWVuZG9iag0xMTM4IDAgb2JqPDwvTGVuZ3Ro
IDI4L1dpZHRoIDkvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBS
L1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCigyVBYhQBggPxcfOxIbNxYfNScs
Qx4lO2tvgQoNCmVuZHN0cmVhbQ1lbmRvYmoNMTEzOSAwIG9iajw8L0xlbmd0aCAyOC9XaWR0aCA5
L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmpl
Y3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpXWmYaHSsaHykIChQEBxAFBQ0CBAoAAAMSEhMKDQpl
bmRzdHJlYW0NZW5kb2JqDTExNDAgMCBvYmo8PC9MZW5ndGggMzQvV2lkdGggMTEvSGVpZ2h0IDEv
Qml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBl
L0ltYWdlPj5zdHJlYW0NCjg4OJSUlL6+vre3t7e3t7i4uLe3t7e3t7e3t7e3t76+vgoNCmVuZHN0
cmVhbQ1lbmRvYmoNMTE0MSAwIG9iajw8L0xlbmd0aCAyMS9GaWx0ZXIvRmxhdGVEZWNvZGUvV2lk
dGggMTgvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUv
WE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCkiJOnbs2HYSwcGDBwECDAAviibmCg0KZW5k
c3RyZWFtDWVuZG9iag0xMTQyIDAgb2JqPDwvTGVuZ3RoIDI0L0ZpbHRlci9GbGF0ZURlY29kZS9X
aWR0aCAxOC9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlw
ZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KSIk6ePDgzp07t5MC9u3bBxBgAC2JJtQK
DQplbmRzdHJlYW0NZW5kb2JqDTExNDMgMCBvYmo8PC9MZW5ndGggNDAvV2lkdGggMTMvSGVpZ2h0
IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0
eXBlL0ltYWdlPj5zdHJlYW0NCkhISDU1NTg4OJ+fn729vbe3t7e3t7e3t7e3t7e3t7e3t7e3t8DA
wAoNCmVuZHN0cmVhbQ1lbmRvYmoNMTE0NCAwIG9iajw8L0xlbmd0aCAyOC9XaWR0aCA5L0hlaWdo
dCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3Vi
dHlwZS9JbWFnZT4+c3RyZWFtDQopMlIWHz4YID0UHTkSHDIRFy4MEikDCR9kZ3gKDQplbmRzdHJl
YW0NZW5kb2JqDTExNDUgMCBvYmo8PC9MZW5ndGggMjgvV2lkdGggOS9IZWlnaHQgMS9CaXRzUGVy
Q29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+
PnN0cmVhbQ0KRkhVAAAOAgYQBQcQBAgQBAUMAgQJAAACEhITCg0KZW5kc3RyZWFtDWVuZG9iag0x
MTQ2IDAgb2JqPDwvTGVuZ3RoIDM0L1dpZHRoIDExL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQg
OC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQo+
Pj6ZmZnFxcW+vr6+vr6+vr6+vr6+vr6+vr6+vr7FxcUKDQplbmRzdHJlYW0NZW5kb2JqDTExNDcg
MCBvYmo8PC9MZW5ndGggMjQvRmlsdGVyL0ZsYXRlRGVjb2RlL1dpZHRoIDE3L0hlaWdodCAxL0Jp
dHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9J
bWFnZT4+c3RyZWFtDQpIiTp79uw+osH+/ftPnDgBEGAA4ZkmKQoNCmVuZHN0cmVhbQ1lbmRvYmoN
MTE0OCAwIG9iajw8L0xlbmd0aCAyNC9GaWx0ZXIvRmxhdGVEZWNvZGUvV2lkdGggMTcvSGVpZ2h0
IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0
eXBlL0ltYWdlPj5zdHJlYW0NCkiJOnny5P79+/cRDS5evAgQYADf9SY4Cg0KZW5kc3RyZWFtDWVu
ZG9iag0xMTQ5IDAgb2JqPDwvTGVuZ3RoIDQwL1dpZHRoIDEzL0hlaWdodCAxL0JpdHNQZXJDb21w
b25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3Ry
ZWFtDQpHR0cxMTFSUlK6urrAwMC+vr6+vr6+vr6+vr6+vr6+vr6+vr7Hx8cKDQplbmRzdHJlYW0N
ZW5kb2JqDTExNTAgMCBvYmo8PC9MZW5ndGggMjUvV2lkdGggOC9IZWlnaHQgMS9CaXRzUGVyQ29t
cG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0
cmVhbQ0KKTFRFh47FR05EhsyFBkwERgtCA0iW19wCg0KZW5kc3RyZWFtDWVuZG9iag0xMTUxIDAg
b2JqPDwvTGVuZ3RoIDI4L1dpZHRoIDkvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9y
U3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCktOWwEFEgYK
EwUJEgQIDwQECwIECAAAAhUVFgoNCmVuZHN0cmVhbQ1lbmRvYmoNMTE1MiAwIG9iajw8L0xlbmd0
aCAzNC9XaWR0aCAxMS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAw
IFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KVFRUu7u7xsbGw8PDw8PDw8PD
w8PDw8PDw8PDw8PDy8vLCg0KZW5kc3RyZWFtDWVuZG9iag0xMTUzIDAgb2JqPDwvTGVuZ3RoIDIx
L0ZpbHRlci9GbGF0ZURlY29kZS9XaWR0aCAxNi9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgv
Q29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KSIm6
cOHCYaLBmTNnAAIMAIeEJNMKDQplbmRzdHJlYW0NZW5kb2JqDTExNTQgMCBvYmo8PC9MZW5ndGgg
MjgvRmlsdGVyL0ZsYXRlRGVjb2RlL1dpZHRoIDE2L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQg
OC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpI
iTp79uxhIsChQ4eOHj167do1gAADAIYfJOsKDQplbmRzdHJlYW0NZW5kb2JqDTExNTUgMCBvYmo8
PC9MZW5ndGggMzcvV2lkdGggMTIvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3Bh
Y2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCkZGRjIyMpGRkcrK
ysPDw8PDw8PDw8PDw8PDw8PDw8PDw8vLywoNCmVuZHN0cmVhbQ1lbmRvYmoNMTE1NiAwIG9iajw8
L0xlbmd0aCAyNS9XaWR0aCA4L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNl
IDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQoqMlEUHDkSHTUTGjAS
GC8QFisIDSFkankKDQplbmRzdHJlYW0NZW5kb2JqDTExNTcgMCBvYmo8PC9MZW5ndGggMjUvV2lk
dGggOC9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9Y
T2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KRklWAQUQBwkSBAgQBQYNAwQJAAACFBQVCg0K
ZW5kc3RyZWFtDWVuZG9iag0xMTU4IDAgb2JqPDwvTGVuZ3RoIDM0L1dpZHRoIDExL0hlaWdodCAx
L0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlw
ZS9JbWFnZT4+c3RyZWFtDQpdXV2+vr7KysrHx8fHx8fHx8fHx8fHx8fHx8fHx8fOzs4KDQplbmRz
dHJlYW0NZW5kb2JqDTExNTkgMCBvYmo8PC9MZW5ndGggMjQvRmlsdGVyL0ZsYXRlRGVjb2RlL1dp
ZHRoIDE1L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBl
L1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpIibpy5cpxIsCJEyeuX78OEGAALAojVgoN
CmVuZHN0cmVhbQ1lbmRvYmoNMTE2MCAwIG9iajw8L0xlbmd0aCA0Ni9XaWR0aCAxNS9IZWlnaHQg
MS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5
cGUvSW1hZ2U+PnN0cmVhbQ0K0tLSxsbGx8fHx8fHx8fHx8fHx8fHx8fHx8fHx8fHx8fHx8fHx8fH
ycnJ2NjYCg0KZW5kc3RyZWFtDWVuZG9iag0xMTYxIDAgb2JqPDwvTGVuZ3RoIDM3L1dpZHRoIDEy
L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmpl
Y3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpISEg/Pz+3t7fLy8vHx8fIyMjIyMjHx8fHx8fHx8fH
x8fPz88KDQplbmRzdHJlYW0NZW5kb2JqDTExNjIgMCBvYmo8PC9MZW5ndGggMjUvV2lkdGggOC9I
ZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0
L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KKTFPERo1EhowEhgwERctEBQoBgweZ2x5Cg0KZW5kc3Ry
ZWFtDWVuZG9iag0xMTYzIDAgb2JqPDwvTGVuZ3RoIDI1L1dpZHRoIDgvSGVpZ2h0IDEvQml0c1Bl
ckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdl
Pj5zdHJlYW0NCkhMVwAFDgUIEQQHEAQFDAIECQAAAhoaGwoNCmVuZHN0cmVhbQ1lbmRvYmoNMTE2
NCAwIG9iajw8L0xlbmd0aCAzNC9XaWR0aCAxMS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgv
Q29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0Kj4+P
09PTzc3Nzc3Nzc3Nzc3Nzc3Nzc3Nzc3Nzc3N1NTUCg0KZW5kc3RyZWFtDWVuZG9iag0xMTY1IDAg
b2JqPDwvTGVuZ3RoIDQ2L1dpZHRoIDE1L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xv
clNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQre3t7Q0NDM
zMzNzc3Nzc3Nzc3Nzc3Nzc3Nzc3Nzc3Nzc3Nzc3MzMzU1NTi4uIKDQplbmRzdHJlYW0NZW5kb2Jq
DTExNjYgMCBvYmo8PC9MZW5ndGggNDMvV2lkdGggMTQvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVu
dCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0N
Ct/f387OzszMzM3Nzc3Nzc3Nzc3Nzc3Nzc3Nzc3Nzc3NzczMzNDQ0OHh4QoNCmVuZHN0cmVhbQ1l
bmRvYmoNMTE2NyAwIG9iajw8L0xlbmd0aCAzNy9XaWR0aCAxMi9IZWlnaHQgMS9CaXRzUGVyQ29t
cG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0
cmVhbQ0KXl5eZWVl0tLSzs7Ozc3Nzc3Nzc3Nzc3Nzc3Nzc3Nzc3N1dXVCg0KZW5kc3RyZWFtDWVu
ZG9iag0xMTY4IDAgb2JqPDwvTGVuZ3RoIDIyL1dpZHRoIDcvSGVpZ2h0IDEvQml0c1BlckNvbXBv
bmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJl
YW0NCiUtRhAYLxMYLxAXLRAUKQMKHVhbaQoNCmVuZHN0cmVhbQ1lbmRvYmoNMTE2OSAwIG9iajw8
L0xlbmd0aCAyNS9XaWR0aCA4L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNl
IDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpLT1oAAw0FCBEEBw8E
BAsBAwgAAAEcHB0KDQplbmRzdHJlYW0NZW5kb2JqDTExNzAgMCBvYmo8PC9MZW5ndGggMzQvV2lk
dGggMTEvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUv
WE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCqKiotnZ2dXV1dXV1dXV1dXV1dXV1dXV1dXV
1dXV1dvb2woNCmVuZHN0cmVhbQ1lbmRvYmoNMTE3MSAwIG9iajw8L0xlbmd0aCA0MC9XaWR0aCAx
My9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2Jq
ZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0K5eXl1tbW09PT1NTU1NTU1NTU1NTU1NTU1NTU1NTU
09PT1tbW4eHhCg0KZW5kc3RyZWFtDWVuZG9iag0xMTcyIDAgb2JqPDwvTGVuZ3RoIDQwL1dpZHRo
IDEzL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hP
YmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQrf39/W1tbT09PU1NTU1NTU1NTU1NTU1NTU1NTU
1NTT09PX19fm5uYKDQplbmRzdHJlYW0NZW5kb2JqDTExNzMgMCBvYmo8PC9MZW5ndGggMzQvV2lk
dGggMTEvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUv
WE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCmVlZcvLy9jY2NXV1dXV1dXV1dXV1dXV1dXV
1dXV1dzc3AoNCmVuZHN0cmVhbQ1lbmRvYmoNMTE3NCAwIG9iajw8L0xlbmd0aCAyMi9XaWR0aCA3
L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmpl
Y3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQojK0ARFy4RGC4QFSsNEyUFChxlaHUKDQplbmRzdHJl
YW0NZW5kb2JqDTExNzUgMCBvYmo8PC9MZW5ndGggMjIvV2lkdGggNy9IZWlnaHQgMS9CaXRzUGVy
Q29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+
PnN0cmVhbQ0KRkpTAAELBAgQBAUNAgQIAAABFxcYCg0KZW5kc3RyZWFtDWVuZG9iag0xMTc2IDAg
b2JqPDwvTGVuZ3RoIDMxL1dpZHRoIDEwL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xv
clNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQri4uLp6eno
6Ojn5+fn5+fn5+fn5+fo6Ojo6Ojn5+cKDQplbmRzdHJlYW0NZW5kb2JqDTExNzcgMCBvYmo8PC9M
ZW5ndGggMzQvV2lkdGggMTEvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2Ug
MTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCufn59vb29fX19jY2NjY
2NjY2NjY2NjY2NjY2Nra2uHh4QoNCmVuZHN0cmVhbQ1lbmRvYmoNMTE3OCAwIG9iajw8L0xlbmd0
aCAzNC9XaWR0aCAxMS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAw
IFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0K39/f2tra19fX2NjY2NjY2NjY
2NjY2NjY2NjY29vb6OjoCg0KZW5kc3RyZWFtDWVuZG9iag0xMTc5IDAgb2JqPDwvTGVuZ3RoIDM0
L1dpZHRoIDExL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9U
eXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQqenp7v7+/n5+fn5+fn5+fn5+fn5+fn
5+fn5+fp6enn5+cKDQplbmRzdHJlYW0NZW5kb2JqDTExODAgMCBvYmo8PC9MZW5ndGggMTkvV2lk
dGggNi9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9Y
T2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KISc9DxYtERUrDRMlBAgaVVlmCg0KZW5kc3Ry
ZWFtDWVuZG9iag0xMTgxIDAgb2JqPDwvTGVuZ3RoIDIyL1dpZHRoIDcvSGVpZ2h0IDEvQml0c1Bl
ckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdl
Pj5zdHJlYW0NCklLVQABCwQHDwQFDAEECAAAARkZGgoNCmVuZHN0cmVhbQ1lbmRvYmoNMTE4MiAw
IG9iajw8L0xlbmd0aCAzMS9XaWR0aCAxMC9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29s
b3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0K7e3t5eXl
4eHh4uLi4eHh4ODg4uLi4eHh5ubm5+fnCg0KZW5kc3RyZWFtDWVuZG9iag0xMTgzIDAgb2JqPDwv
TGVuZ3RoIDMxL1dpZHRoIDEwL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNl
IDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQrp6enj4+Pi4uLi4uLh
4eHh4eHi4uLh4eHo6Oju7u4KDQplbmRzdHJlYW0NZW5kb2JqDTExODQgMCBvYmo8PC9MZW5ndGgg
MTkvV2lkdGggNi9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIv
VHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KICY7DhQqDxQnCxIjBAgZWl5pCg0K
ZW5kc3RyZWFtDWVuZG9iag0xMTg1IDAgb2JqPDwvTGVuZ3RoIDE5L1dpZHRoIDYvSGVpZ2h0IDEv
Qml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBl
L0ltYWdlPj5zdHJlYW0NCkVGUQABCQQFDQIECgAAAxMTFAoNCmVuZHN0cmVhbQ1lbmRvYmoNMTE4
NiAwIG9iajw8L0xlbmd0aCAyNS9XaWR0aCA4L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9D
b2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQrn5+fm
5ubl5eXm5ubn5+fl5eXl5eXv7+8KDQplbmRzdHJlYW0NZW5kb2JqDTExODcgMCBvYmo8PC9MZW5n
dGggMjUvV2lkdGggOC9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAw
IFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0K7+/v5eXl5eXl5ubm5+fn5eXl
5ubm6OjoCg0KZW5kc3RyZWFtDWVuZG9iag0xMTg4IDAgb2JqPDwvTGVuZ3RoIDE5L1dpZHRoIDYv
SGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVj
dC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCiAmOQ8TKA0TJAwRIwQIF25xewoNCmVuZHN0cmVhbQ1l
bmRvYmoNMTE4OSAwIG9iajw8L0xlbmd0aCAxOS9XaWR0aCA2L0hlaWdodCAxL0JpdHNQZXJDb21w
b25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3Ry
ZWFtDQpHS1QAAAgEBAsCBAkAAAITExQKDQplbmRzdHJlYW0NZW5kb2JqDTExOTAgMCBvYmo8PC9M
ZW5ndGggNy9XaWR0aCAyL0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1
IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQry8vLf398KDQplbmRzdHJl
YW0NZW5kb2JqDTExOTEgMCBvYmo8PC9MZW5ndGggNy9XaWR0aCAyL0hlaWdodCAxL0JpdHNQZXJD
b21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+
c3RyZWFtDQrv7+/09PQKDQplbmRzdHJlYW0NZW5kb2JqDTExOTIgMCBvYmo8PC9MZW5ndGggMTYv
V2lkdGggNS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlw
ZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KHiI1ChEiCxAiBAcWVlllCg0KZW5kc3Ry
ZWFtDWVuZG9iag0xMTkzIDAgb2JqPDwvTGVuZ3RoIDE5L1dpZHRoIDYvSGVpZ2h0IDEvQml0c1Bl
ckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdl
Pj5zdHJlYW0NCk5RWgAABwQECwEECAAAAhgYGAoNCmVuZHN0cmVhbQ1lbmRvYmoNMTE5NCAwIG9i
ajw8L0xlbmd0aCAxNi9XaWR0aCA1L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNw
YWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQogJzgJDiEMEB8D
BhVtcHsKDQplbmRzdHJlYW0NZW5kb2JqDTExOTUgMCBvYmo8PC9MZW5ndGggMTYvV2lkdGggNS9I
ZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0
L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KREZOAAAGAgQJAAADERETCg0KZW5kc3RyZWFtDWVuZG9i
ag0xMTk2IDAgb2JqPDwvTGVuZ3RoIDE2L1dpZHRoIDUvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVu
dCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0N
CiUpOwkOHgsOHQEEEnV4ggoNCmVuZHN0cmVhbQ1lbmRvYmoNMTE5NyAwIG9iajw8L0xlbmd0aCAx
Ni9XaWR0aCA1L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9U
eXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpKS1IAAAUBBAgAAAIYGBkKDQplbmRz
dHJlYW0NZW5kb2JqDTExOTggMCBvYmo8PC9MZW5ndGggMTMvV2lkdGggNC9IZWlnaHQgMS9CaXRz
UGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1h
Z2U+PnN0cmVhbQ0KIiY1CAsaAgcSWFxmCg0KZW5kc3RyZWFtDWVuZG9iag0xMTk5IDAgb2JqPDwv
TGVuZ3RoIDE2L1dpZHRoIDUvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2Ug
MTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NClFRWAAAAwADBwAAAR0d
HQoNCmVuZHN0cmVhbQ1lbmRvYmoNMTIwMCAwIG9iajw8L0xlbmd0aCAxMy9XaWR0aCA0L0hlaWdo
dCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3Vi
dHlwZS9JbWFnZT4+c3RyZWFtDQoiJzMGCRcBBhFhZW0KDQplbmRzdHJlYW0NZW5kb2JqDTEyMDEg
MCBvYmo8PC9MZW5ndGggMTMvV2lkdGggNC9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29s
b3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KR0dOAAAB
AAABFhYXCg0KZW5kc3RyZWFtDWVuZG9iag0xMjAyIDAgb2JqPDwvTGVuZ3RoIDEwL1dpZHRoIDMv
SGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVj
dC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NChkfKgADC0ZIcAoNCmVuZHN0cmVhbQ1lbmRvYmoNMTIw
MyAwIG9iajw8L0xlbmd0aCAxMy9XaWR0aCA0L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9D
b2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQpPT1UA
AAEAAAAaGhsKDQplbmRzdHJlYW0NZW5kb2JqDTEyMDQgMCBvYmo8PC9MZW5ndGggMTAvV2lkdGgg
My9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2Jq
ZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KGR0nAAAHUG17Cg0KZW5kc3RyZWFtDWVuZG9iag0x
MjA1IDAgb2JqPDwvTGVuZ3RoIDEwL1dpZHRoIDMvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4
L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCkND
RwAAAAwMLQoNCmVuZHN0cmVhbQ1lbmRvYmoNMTIwNiAwIG9iajw8L0xlbmd0aCAxMC9XaWR0aCAz
L0hlaWdodCAxL0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmpl
Y3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQoZGyYBAQxbbWsKDQplbmRzdHJlYW0NZW5kb2JqDTEy
MDcgMCBvYmo8PC9MZW5ndGggMTAvV2lkdGggMy9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgv
Q29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KTE1P
AAAAExIfCg0KZW5kc3RyZWFtDWVuZG9iag0xMjA4IDAgb2JqPDwvTGVuZ3RoIDcvV2lkdGggMi9I
ZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0
L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KDA0XX1dOCg0KZW5kc3RyZWFtDWVuZG9iag0xMjA5IDAg
b2JqPDwvTGVuZ3RoIDEwL1dpZHRoIDMvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9y
U3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NClhYWQAAABEy
KQoNCmVuZHN0cmVhbQ1lbmRvYmoNMTIxMCAwIG9iajw8L0xlbmd0aCA3L1dpZHRoIDIvSGVpZ2h0
IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0
eXBlL0ltYWdlPj5zdHJlYW0NChETHW9kbwoNCmVuZHN0cmVhbQ1lbmRvYmoNMTIxMSAwIG9iajw8
L0xlbmd0aCA3L1dpZHRoIDIvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2Ug
MTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NCkRFRhQTEAoNCmVuZHN0
cmVhbQ1lbmRvYmoNMTIxMiAwIG9iajw8L0xlbmd0aCA3L1dpZHRoIDIvSGVpZ2h0IDEvQml0c1Bl
ckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdl
Pj5zdHJlYW0NChgZJHd7fgoNCmVuZHN0cmVhbQ1lbmRvYmoNMTIxMyAwIG9iajw8L0xlbmd0aCA3
L1dpZHRoIDIvSGVpZ2h0IDEvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5
cGUvWE9iamVjdC9TdWJ0eXBlL0ltYWdlPj5zdHJlYW0NClNVVhEREgoNCmVuZHN0cmVhbQ1lbmRv
YmoNMTIxNCAwIG9iajw8L0xlbmd0aCAxMy9XaWR0aCA0L0hlaWdodCAxL0JpdHNQZXJDb21wb25l
bnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFt
DQo+Vkt8gH5lZ2giIiIKDQplbmRzdHJlYW0NZW5kb2JqDTEyMTUgMCBvYmo8PC9MZW5ndGggMTAv
V2lkdGggMy9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlw
ZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KGBwfBAQHDQ4XCg0KZW5kc3RyZWFtDWVu
ZG9iag0xMjE2IDAgb2JqPDwvTGVuZ3RoIDcvV2lkdGggMi9IZWlnaHQgMS9CaXRzUGVyQ29tcG9u
ZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVh
bQ0KDxEVKA0VCg0KZW5kc3RyZWFtDWVuZG9iag0xMjE3IDAgb2JqPDwvTGVuZ3RoIDcvV2lkdGgg
Mi9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2Jq
ZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KHSInHx8fCg0KZW5kc3RyZWFtDWVuZG9iag0xMjE4
IDAgb2JqPDwvTGVuZ3RoIDQvV2lkdGggMS9IZWlnaHQgMS9CaXRzUGVyQ29tcG9uZW50IDgvQ29s
b3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KcnR2Cg0K
ZW5kc3RyZWFtDWVuZG9iag0xMjE5IDAgb2JqPDwvTGVuZ3RoIDEzMDcvRmlsdGVyL0RDVERlY29k
ZS9XaWR0aCAyNDIvSGVpZ2h0IDE0L0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAg
Ui9UeXBlL1hPYmplY3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQr/2P/uAA5BZG9iZQBkgAAAAAH/
2wCEAAwICAgJCAwJCQwRCwoLERUPDAwPFRgTExUTExgXEhQUFBQSFxcbHB4cGxckJCcnJCQ1MzMz
NTs7Ozs7Ozs7OzsBDQsLDQ4NEA4OEBQODw4UFBARERAUHRQUFRQUHSUaFxcXFxolICMeHh4jICgo
JSUoKDIyMDIyOzs7Ozs7Ozs7O//AABEIAA4A8gMBIgACEQEDEQH/xAE/AAABBQEBAQEBAQAAAAAA
AAADAAECBAUGBwgJCgsBAAEFAQEBAQEBAAAAAAAAAAEAAgMEBQYHCAkKCxAAAQQBAwIEAgUHBggF
AwwzAQACEQMEIRIxBUFRYRMicYEyBhSRobFCIyQVUsFiMzRygtFDByWSU/Dh8WNzNRaisoMmRJNU
ZEXCo3Q2F9JV4mXys4TD03Xj80YnlKSFtJXE1OT0pbXF1eX1VmZ2hpamtsbW5vY3R1dnd4eXp7fH
1+f3EQACAgECBAQDBAUGBwcGBTUBAAIRAyExEgRBUWFxIhMFMoGRFKGxQiPBUtHwMyRi4XKCkkNT
FWNzNPElBhaisoMHJjXC0kSTVKMXZEVVNnRl4vKzhMPTdePzRpSkhbSVxNTk9KW1xdXl9VZmdoaW
prbG1ub2JzdHV2d3h5ent8f/2gAMAwEAAhEDEQA/ANPrX1gzMq+14tfVjVkiuthLdAYkxySszCy+
t9RsdXgMuvLdSA86fEkgIHUp9F8fvfxXof1TGAOhYwwS1w2D1i3n1Y9+7vMq9klwxAxASH9UW14R
Bs5DrfU08h+zvrl/3Eu/7dH/AJNL9nfXL/uJd/26P/Jr0ZOovdzfu/8ANX8GLuPtfOP2d9cv+4l3
/bo/8ml+zvrl/wBxLv8At0f+TXo6SXu5v3f+argxdx9r5x+zvrl/3Eu/7dH/AJNL9nfXL/uJd/26
P/Jr0dJL3c37v/NVwYu4+184/Z31y/7iXf8Abo/8ml+zvrl/3Eu/7dH/AJNejpJe7m/d/wCargxd
x9r5x+zvrl/3Eu/7dH/k0v2d9cv+4l3/AG6P/Jr0dJL3c37v/NVwYu4+184/Z31y/wC4l3/bo/8A
Jpfs765f9xLv+3R/5NejpJe7m/d/5quDF3H2vnH7O+uX/cS7/t0f+TS/Z31y/wC4l3/bo/8AJr0d
JL3c37v/ADVcGLuPtfOP2d9cv+4l3/bo/wDJpHA+uLQXHEuAGpPqj/ya9HWf1t2U3Bf9nYXujWCB
+Upe7m/d/wCargxdx9r5td1TqtDzXcXseOQbHfwKGet54/Pf/wBuO/vVfLN5yLDcCLJ4Kr99eVKD
Ohe/kjhx+H2ugOt554e/X+W7+9I9bzxy9/8A247+9UB328+KcE7fcJbPznyRuX8gjhx+H2t4dczz
w9/+e7+9T/avVNdbNOfe7+9VsRmNumx8O4YADz48LT6W1jan+/d7tdCPyp0RIkWQAfJjnKAvhjde
aNuT154lrLCP+MP/AJJI5XXAYLbJPb1D/wCSW7QK9JKOB071Gwa/WkxxununEAfpX9jF7kv3Pzed
9b6wRPp2/wDbh/8AJKJyeujlln/bh/8AJLorxV4hU3xOiIjE/pfkr3J/ufm5H2vrn7tn/bh/8kp4
vX+qYeU3dZZU+RAc4uafJzT2V08/lVHqvpfZT6hG+R6fjPklKMQCeIHwNJhORkAYVfUXo9n/AM7K
/wDRf9pfX/65+58Elyuv/sn+KSr+3g7j/GZ+LL4/Y//ZCg0KZW5kc3RyZWFtDWVuZG9iag0xMjIw
IDAgb2JqPDwvTGVuZ3RoIDE2MTgvRmlsdGVyL0RDVERlY29kZS9XaWR0aCAyNDIvSGVpZ2h0IDE1
L0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmplY3QvU3VidHlw
ZS9JbWFnZT4+c3RyZWFtDQr/2P/uAA5BZG9iZQBkgAAAAAH/2wCEAAwICAgJCAwJCQwRCwoLERUP
DAwPFRgTExUTExgXEhQUFBQSFxcbHB4cGxckJCcnJCQ1MzMzNTs7Ozs7Ozs7OzsBDQsLDQ4NEA4O
EBQODw4UFBARERAUHRQUFRQUHSUaFxcXFxolICMeHh4jICgoJSUoKDIyMDIyOzs7Ozs7Ozs7O//A
ABEIAA8A8gMBIgACEQEDEQH/xAE/AAABBQEBAQEBAQAAAAAAAAADAAECBAUGBwgJCgsBAAEFAQEB
AQEBAAAAAAAAAAEAAgMEBQYHCAkKCxAAAQQBAwIEAgUHBggFAwwzAQACEQMEIRIxBUFRYRMicYEy
BhSRobFCIyQVUsFiMzRygtFDByWSU/Dh8WNzNRaisoMmRJNUZEXCo3Q2F9JV4mXys4TD03Xj80Yn
lKSFtJXE1OT0pbXF1eX1VmZ2hpamtsbW5vY3R1dnd4eXp7fH1+f3EQACAgECBAQDBAUGBwcGBTUB
AAIRAyExEgRBUWFxIhMFMoGRFKGxQiPBUtHwMyRi4XKCkkNTFWNzNPElBhaisoMHJjXC0kSTVKMX
ZEVVNnRl4vKzhMPTdePzRpSkhbSVxNTk9KW1xdXl9VZmdoaWprbG1ub2JzdHV2d3h5ent8f/2gAM
AwEAAhEDEQA/AK/U/wCZf/X/AIlem9JsZX0TCfY4MY3HqLnOMAewdyvMup/zL/6/8Sur6j9qv6f0
jDl1WC6ik33wRWC4Ae9/0dB4q7nhxziLrSyfANfFLhgTvq9PT1Pp2Q/06cmqx/ZrXAk/BJ/U+nVv
dW/Kqa9phzS8AgjsdVkVdK+rHrY5w8mtmRVY1zCy5rnPIIO0t3az5LHjo5671H9qmKt79kbp3bv5
HkoY48cr4TIgC9tV8pzjVganvo9rXdTbX6tVjX1/vtII08wgftbpf/cun/Pb/euf+qjbfR6g5hd9
igioO8fd/wB95WH067oldLh1DHsusJljq3bQGxx9IJw5cXMWTw18u+qDmNRNAcV7+D6GL6XU+u17
TTG71ARtjxlNRlY2Q0ux7WWtaYcWEOAPyWL1S1lX1XaOn1vNNtbWtAl2ys+5xcRPA0VP6pCzGzcn
FafWx3sa43V+6sPgGNzZAMH8EwYbhKV7E0PAbrvc9Qj33PiXoP2t0v8A7l0/57f71JvUunuY57cm
osZG9weIE6CfiuO+sGH0PHbQem2Me573C7bZ6kDTnUwr3VMPouN0XKPTHse55q9XZZ6kAO0nUwj7
WMiFGXrNDTx1Rxz9VgekWXoR1XphIAy6SToBvb/erS4Tpt31cJxq78a37SXMa63fDN8/S+lwu1fl
1MeWObYSNDtqscPvawhDLi4SBESPmP4JhksWSB9VWZuHVaKbb667TEMc4B2vGhUrcnHpeyu21jH2
aMa4gF3bQLjvrRV63XdrXtY/0WuaXHbq3cQAT3PZFzcm/Jy+iPy6n05DX7bG2NLSSHs9wDvFOHLg
iJvcWfDSwtOajIVsaD1FvUMCmw13ZFVdjeWucAR8im/afTdhf9qq2A7S7eIk6xyuQ60/BZ9ZMh2d
W62iG7mMMOnY2NZCv9Op+quZh2S041LbWyLrdsvDTEHf4EoHDGMIyPFqAbAFapGSRkYitCR9jv8A
7W6X/wBy6f8APb/euc+uvVGtxhXU4Oa4S0gyDPdUumYfQ7eqZlOXYxuJXu9BzrNoMOgQ6ROizvrY
6La2VA/Z2NAqOpBaBDYPfRCWOAlGIJN6m+26YTlIEkB54Gee/KQH4JAfJSO2OJjuVMlgTKdrS4ho
7qVYc920FrR3JgLRxaqa26va+w95HHknxgZbfax5MsYeJ7JcV1VdTQ47DEu36E+aIc4sDfs7N8uj
sQZ7QPFM/wBDT1tvluj+KaunGDvUxnw9uoYwggkcCFNITAqJFAb9WoJQMiTdnvs7mHeAaW3ANfdI
bt4kCduvdaukQuaxzd6LK8gFrza04z2e47jqf9q3DdaGn2OLuwg8+ZTDctVso0VZIGqzrRrKDlXd
bpO51Ysrc7cWsBJA/d8Ur7LHU762lr3AENcNRPiE+EhqOsdUGB0OlHS2DlW6j/Q7f6v8QjPNjGsE
b3SA48adygdR/oVvw/iE+RuMvJUB64/3gl/94kkv/eJJRtl//9kKDQplbmRzdHJlYW0NZW5kb2Jq
DTEyMjEgMCBvYmo8PC9MZW5ndGggMTU2MC9GaWx0ZXIvRENURGVjb2RlL1dpZHRoIDI0Mi9IZWln
aHQgMTUvQml0c1BlckNvbXBvbmVudCA4L0NvbG9yU3BhY2UgMTUgMCBSL1R5cGUvWE9iamVjdC9T
dWJ0eXBlL0ltYWdlPj5zdHJlYW0NCv/Y/+4ADkFkb2JlAGSAAAAAAf/bAIQADAgICAkIDAkJDBEL
CgsRFQ8MDA8VGBMTFRMTGBcSFBQUFBIXFxscHhwbFyQkJyckJDUzMzM1Ozs7Ozs7Ozs7OwENCwsN
Dg0QDg4QFA4PDhQUEBEREBQdFBQVFBQdJRoXFxcXGiUgIx4eHiMgKCglJSgoMjIwMjI7Ozs7Ozs7
Ozs7/8AAEQgADwDyAwEiAAIRAQMRAf/EAT8AAAEFAQEBAQEBAAAAAAAAAAMAAQIEBQYHCAkKCwEA
AQUBAQEBAQEAAAAAAAAAAQACAwQFBgcICQoLEAABBAEDAgQCBQcGCAUDDDMBAAIRAwQhEjEFQVFh
EyJxgTIGFJGhsUIjJBVSwWIzNHKC0UMHJZJT8OHxY3M1FqKygyZEk1RkRcKjdDYX0lXiZfKzhMPT
dePzRieUpIW0lcTU5PSltcXV5fVWZnaGlqa2xtbm9jdHV2d3h5ent8fX5/cRAAICAQIEBAMEBQYH
BwYFNQEAAhEDITESBEFRYXEiEwUygZEUobFCI8FS0fAzJGLhcoKSQ1MVY3M08SUGFqKygwcmNcLS
RJNUoxdkRVU2dGXi8rOEw9N14/NGlKSFtJXE1OT0pbXF1eX1VmZ2hpamtsbW5vYnN0dXZ3eHl6e3
x//aAAwDAQACEQMRAD8Ar9T/AJl/9f8AiV1Gcy3Fq6J1XYX01UUNfHYtAd+IK5fqf8y/+v8AxK9K
6f8AZv2Bh/a9nofZ6t/qxt+gOd2ivZ58E4mr0o+Ra+KPFjI21Rj6z9Je+muiw3W3vaxtYBBG4xLp
8FgV4F2f1vqlWPe6i1hsc3aYDjuja6Oy6DDq+rbL2nDOKbyfbscxzp/k6lWcdvSxl3HG9H7WZ9f0
y02c67415VeOWEL4AdR+kvMJSriI0PRwvqxkY1WPl9PfX6Oc0PNk8vAB8f3fBZPRm/V52O/9qvc2
3d7Npf8ARgfuea7As6Ic1x/V/tuu7Vvqce6RM8Kr6f1S/wC6P+dX/enjPG5H1Djo+k9Qj2j6flPD
e4crr99eYzpvS+m/pK3tD62kxIjYyd3kChmzP6f9YMbMz6WYwyIqcKzLS0AV+J40XRUs6GMik0/Z
vtAaPQ2lm/bBjZBmInhEz29Kd6f7R9Hk+l6xaNdJ27kBniAI8PpqQN7+pJxEm71sV20cX67aV4X/
ABjvyNV361/8hWfGv/qgrue3pbhX+0fRgE+l65aNe+3ciZgwjjkZvp/Z9N3qkBnOn0tEwZABj0/m
ySftXGBPHr84p5XpX/NVleLZdY4ZrdpcJfHqA+WnK2svoeVkZVl7OpX0teZFTfot8h7k7a/qrubs
+xbpG2HVzPaNVrIzzXK4mX+HR+xEcelSA/wdHmcqtln1xpqsG5r6Nrge4LHgrJdiXdP67jYNjiaq
r2uonu17m6/guyc3pn29rnej9v2+yS31dsHgcxCbJb0k5VRyvQ+1CPR9QtFnOm2deU6OeqFacHD9
e6Diu9deK/o8t1T9nH60XjqRLcaBuImZ2N2/R1XQdAPRhVazpLi5gcDbO7kiB9P4KWWz6vHIccz7
L9o03+q5gfxpO4zwj9Pb0pof+zfRiR6noFp17btqbPKJQEfVYAFX6dPBMYESJ01JPi4XQTH1h6qf
Df8A+fFyf1ntL+oP+K9Hqb0sXZBxfR+1EO9f0y0v513xryvM/rDP7Qf8URITyAjtX2BMY8Ma8bcy
Y40S17azpCQ80XFa03DeQANROknspQLNIkaBPZvY+LXVB5eeSVZHCiFJXIADQBoSkSbOrMCE2Q60
Y7vSbucdD4gHlO1FbOkcpxFgja2MGpA1dOWc7JJZ7tuwtOgiS3QE+K2Kuom3IaXh1dLq9zd8AOIP
IhUTj9P3PLntO7gbhoe/dBOK8Mj1murg+kXOgecKvwTjrV/2Ngyxz/q/2uxk+jkt22RYG6eJHzCE
/a2vYBDGiAB4BCxGtrpDGEPIPvcNZciElTRjpZABI1YCaNA2AWDXttY15AI5HxCF1D+hW/D+KnWG
NYBXG0cRqoZ/9Cun93+ISI9BvetV0a9yNbcQr7Uv/vEkl/7xJKNsP//ZCg0KZW5kc3RyZWFtDWVu
ZG9iag0xMjIyIDAgb2JqPDwvTGVuZ3RoIDEyMTAvRmlsdGVyL0RDVERlY29kZS9XaWR0aCAyNDIv
SGVpZ2h0IDE0L0JpdHNQZXJDb21wb25lbnQgOC9Db2xvclNwYWNlIDE1IDAgUi9UeXBlL1hPYmpl
Y3QvU3VidHlwZS9JbWFnZT4+c3RyZWFtDQr/2P/uAA5BZG9iZQBkgAAAAAH/2wCEAAwICAgJCAwJ
CQwRCwoLERUPDAwPFRgTExUTExgXEhQUFBQSFxcbHB4cGxckJCcnJCQ1MzMzNTs7Ozs7Ozs7OzsB
DQsLDQ4NEA4OEBQODw4UFBARERAUHRQUFRQUHSUaFxcXFxolICMeHh4jICgoJSUoKDIyMDIyOzs7
Ozs7Ozs7O//AABEIAA4A8gMBIgACEQEDEQH/xAE/AAABBQEBAQEBAQAAAAAAAAADAAECBAUGBwgJ
CgsBAAEFAQEBAQEBAAAAAAAAAAEAAgMEBQYHCAkKCxAAAQQBAwIEAgUHBggFAwwzAQACEQMEIRIx
BUFRYRMicYEyBhSRobFCIyQVUsFiMzRygtFDByWSU/Dh8WNzNRaisoMmRJNUZEXCo3Q2F9JV4mXy
s4TD03Xj80YnlKSFtJXE1OT0pbXF1eX1VmZ2hpamtsbW5vY3R1dnd4eXp7fH1+f3EQACAgECBAQD
BAUGBwcGBTUBAAIRAyExEgRBUWFxIhMFMoGRFKGxQiPBUtHwMyRi4XKCkkNTFWNzNPElBhaisoMH
JjXC0kSTVKMXZEVVNnRl4vKzhMPTdePzRpSkhbSVxNTk9KW1xdXl9VZmdoaWprbG1ub2JzdHV2d3
h5ent8f/2gAMAwEAAhEDEQA/AAdT/mX/ANf+K9N6IQ7o2CQZH2er/qAuE6/R0tt1zsbIbZQ9xJZt
eHMdPAlsETwtH6sW/WvHwGfYqGZvTzPoeq70yBOu0uIMT5K5zA4hE7eEtD+LBhNAjfXcah7dJYP7
Q+t//lVR/wBvj+9L9ofW/wD8qqP+3x/eqvAe8f8AGDNxDx+x3klg/tD63/8AlVR/2+P70v2h9b//
ACqo/wC3x/elwHvH/GCuIeP2O8ksH9ofW/8A8qqP+3x/el+0Prf/AOVVH/b4/vS4D3j/AIwVxDx+
x3klg/tD63/+VVH/AG+P70v2h9b/APyqo/7fH96XAe8f8YK4h4/Y7ySwf2h9b/8Ayqo/7fH96X7Q
+t//AJVUf9vj+9LgPeP+MFcQ8fsd5JYP7Q+t/wD5VUf9vj+9L9ofW/8A8qqP+3x/elwHvH/GCuIe
P2O8ksH9ofW//wAqqP8At8f3pftD63/+VVH/AG+P70uA94/4wVxDx+x3bBLHDxBXlX1irIzbT4O/
Ku4PUPrfGvSqI/48f3rietOybMqx2Uyuh5HuaHF0a+ICkxRImNR16hbI6dfscfj8isYUNuI7kIYr
brFjZ+DuPuU8dkXA1vaXeHu4+5WIipA+KydGJHg6YUlXByPBn3n+5TByo+iz7z/crQl4H7Gnw+I+
1ss1/ijNCpsdl9mVn+0f7kZtmf8A6Ks/2ijxeB+xZwHvH7QnI8VEmAhGzqH+ir/zih783/R1/wCc
f7kuIdj9iuA9x/jBNXaLaw9vDvFPOuqp45yxV+jbW5u4kGSO/HCm52YWuGxg0MkEz+RASNCwb8km
Gpoir7tlA6gf1K34fxUGftEASGO05JIS9E32MHUMhmLi7hJDXv189jXFCU/SdCNOy6EKmPVHQ9C2
v/eJJdP6X1Y/03/aLZw7+a/0n0fpeSSr+7/Un/itjg/rR+1//9kKDQplbmRzdHJlYW0NZW5kb2Jq
DTEyMjMgMCBvYmo8PC9MZW5ndGggMTQzMy9GaWx0ZXIvRmxhdGVEZWNvZGUvV2lkdGggMTA0L0hl
aWdodCA0Mi9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNyAwIFIvVHlwZS9YT2JqZWN0
L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KSIncl91D2zYQwO/8iR2TL8eBhBh/JE2dGJI0jCSQjRII
gaaMtisba7vS0nWEsv3/zzvJMYVk7K089B5sST7ppzuddDLA9yb4AMI5D2DKg3MEQRQlWRYU9eaj
tLCwoAk3dfZV1wESxiKJET35VzWppVLpBNdSDUVRog6qKCqKqN7hqJksmjnLyueXlqfDFjIZyypm
V0q8aq+iYzmup/plcrfJnU7PCn16tJS1LKv6OKBJwOLK40wm6lJbqmcydeOuPVIyxDWAkoX5dVZv
eBjovq8WEAM2pVVsAuhrLdl/0l7e+GETq51utxOmAJrY2yKFbQt7rKewhuhykCpVsFyb8RvYfayT
wT/+hDs0bqOKU7sWEJ8yJTPp+76dWfZ3a1QY4J5Nr/2h30RL9Zlioo2uTO+DFoEe8aaaueXPckQr
5myqkBjhYbwudcQjgBD7zC2yDA2R3hXMLvJVTWJrIxoLkjl8Rq/U4zFi+Ii1lPLd2TjgHF1Vm4ik
so6YjjlpxCHAc8RM92sATTkAS+jdNB6jKRFnT9LIop8Zx934L04+Q9GAHTYnxFLcW2gxT9q0/OaK
NMtRHW5DJDTHDcYxIEDMyvdy1o7WtTY6JwBDzDXi3kY2clkqRKwmZziih/s3HDJD4/bwYn/Rv4dT
Z4E1QtIb8DWJREZc5YXtPkYrfdtvFGV+rLmKuD3lMFBPlO/hsA3WQYq0Fy6bWSQBxmWFFmnHv8vZ
xFCcKooOunbMYd1GB3v3c2jZDwBeYjbe1a9wT4DGkFdWKIjvcvRfcOjHNuJruOHQDDDvbs1xTntY
p9lAGX+lvaX+xsKbYc6QGd8IucOesr085UzNOPq9FS3amxyuKRDFAe9JIEzOcuSjIuKCLL/F3LvI
2W59uVbrWK0/2C5X8b2s6/J55HBD2EEcCHoE8tzXjUZpsxW+pHmqH84wOT32CDRrj/rx43vH8T5e
XBzGu+Tk00U2my1PZ9TOZv98/sqK/P1udHFx0Vv6PNX8/Nfl5aWlcQMXdxyn9zSyCDbzc/acnipc
4JacksTlFy9O0ul4CrbIVEX1tqY6XSX2xYjb10/n1uebyoNzHuJq8D367f+FMtqt4tfKVMQ7mvPf
b3NSWpCim0Q6mDQaBa1EykIQBLqgacOt7aEWdECeBIXlQJuMx80abE+0q+Uh3x1GoTBp6jAItILS
HY93tWA8Hr4ZaloXlIo2TNzl0PnKOMuuU6vt8HQoDHGYoGzfO2pY6ByA8AXH118oN3hOn+X1luea
dA1RrfrfHcqNdP6WE2/pPkLJ9NzV1tiZQ4fW7gwH8m3+cq59fz1HCZ6NQLt2wMaSqj02lR2C44RM
pVS4gVdgoCdBAvd9/4CyYjvUIaCDNTwD6Nbg0BxAYimYvR/o+R7f3kW6fnS9CuZrIBYFgCuTJYUy
HVQfimm6WeA4kbhSWfpIgYRtFdQ+7rODLmFdLgIdcHJ4zI5jEM7N9U/Hc+sTcxzibHiUuPuG7d1w
rnHkp87YPQiL5RWTc3YbzXDABqwjTZ045wIbIOZA2jy3tuc4Yi7yWy/iwBX2S5kbDvTdk7UCeayB
z+mwBsbpHeNh5JWJS6lxjgOH5OM5juJ5Omv10r6/VaTCZ3Scr5xBy7KYd2qU1XzbtonTUZ+R70Cg
xNSlNSG/SXc5hdb1fFzDBEfbIO1naeyKw4gBhhKzvsLdWsVN1ljCXbqklht0Uaz46iHZkaT7juqO
KQ5aPMPyOOAStI7m7QG7ia5V7f9DiTE0m6ylGS5CqYjVK1Z5wm8g65bLxDLSVfReg11wUwkcfXF6
EjRNLH4gf2bQ3OcODEL0BvMcliVlgZmcEIQogdDTFowobdrRk/4G6DdBIR1DYG6SdOomsW6GJLF/
C0WgAo8okVSU/+J8Q/k+OQ8g396Uh5Z/BRgA7iKoXQoNCmVuZHN0cmVhbQ1lbmRvYmoNMTIyNCAw
IG9iajw8L0xlbmd0aCAyODk2L0ZpbHRlci9EQ1REZWNvZGUvV2lkdGggMTg2L0hlaWdodCA1MC9C
aXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAxNSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUv
SW1hZ2U+PnN0cmVhbQ0K/9j/7gAOQWRvYmUAZIAAAAAB/9sAhAAMCAgICQgMCQkMEQsKCxEVDwwM
DxUYExMVExMYFxIUFBQUEhcXGxweHBsXJCQnJyQkNTMzMzU7Ozs7Ozs7Ozs7AQ0LCw0ODRAODhAU
Dg8OFBQQEREQFB0UFBUUFB0lGhcXFxcaJSAjHh4eIyAoKCUlKCgyMjAyMjs7Ozs7Ozs7Ozv/wAAR
CAAyALoDASIAAhEBAxEB/8QBPwAAAQUBAQEBAQEAAAAAAAAAAwABAgQFBgcICQoLAQABBQEBAQEB
AQAAAAAAAAABAAIDBAUGBwgJCgsQAAEEAQMCBAIFBwYIBQMMMwEAAhEDBCESMQVBUWETInGBMgYU
kaGxQiMkFVLBYjM0coLRQwclklPw4fFjczUWorKDJkSTVGRFwqN0NhfSVeJl8rOEw9N14/NGJ5Sk
hbSVxNTk9KW1xdXl9VZmdoaWprbG1ub2N0dXZ3eHl6e3x9fn9xEAAgIBAgQEAwQFBgcHBgU1AQAC
EQMhMRIEQVFhcSITBTKBkRShsUIjwVLR8DMkYuFygpJDUxVjczTxJQYWorKDByY1wtJEk1SjF2RF
VTZ0ZeLys4TD03Xj80aUpIW0lcTU5PSltcXV5fVWZnaGlqa2xtbm9ic3R1dnd4eXp7fH/9oADAMB
AAIRAxEAPwDrvrZ9aszoWVj1UUV3MuYXEvLgZBiBCxm/4zcz8/ArPwsP/kUv8Zn9MwP+Ls/6pq5r
Hu6VjUNe+h2ZmEyWWktoYO2jCHPP4K5ixYzjiTGyVpJt6un/ABkZVpIZ0w2n/g3l33wwqd3+MHqN
Q3P6Q+tndzy4D79i5+vrf1jbhvysMMxMNjgx7semutoceBO3cfvQ2fW/6wN0syftFZ+lXexj2keB
Baj7MekI/wCMVX4u07/GZnH6GDUB2l7j/AJ6Pr59Y8wuGLh48MEve4O2MHi97nta35lOeh9L6p0h
vXbMSzCfW11uRjY5DW3Mb+dW1xO0Fctl9UvyK/Qra3GwwZbjU+1nxefpPPm4lGOPHL5YDTQ30VZf
RPq79Y8vqeYcZ7qsjYwuvtoY5ldZ/NaHPe7eT5LpFz31H6S3p/RK7XNi/M/S2H+SfoD/ADV0KqZe
HjIjsNEhSSSSYlSSSSSlJJJJKUkkkkpSSSSSlJJJJKUkkkkpSSSSSnz7/GYR9twR3FTz97gub6N0
m/q2aMWpwrYGl91zvosY3lxXQ/4ynA9TxGgGRST97iqWaT0bo1fR6Qf2l1LbZnge5zWH+apHgT3C
vYyRigBudv4rTu4dmRk+n9ibc+zGY8+nUCdhMxua3zWtXh4/QGVZfUq25HULBvx+nu+jWO1mSDr8
Go9NFP1ZoGXlgP67Y2cTGPuFDT/hLR+94BUcPpdvUK7esdRyBTgi3bkZBl1jnnUtYxoOuvfRPMgf
CP8A0j4Idr6rZmTYesdc6g91lbccseXHQuMkVtnSBwAuY6Xhuzc/FwxzdY1h76E+4/cr3V+s1X41
fSum1mjpVB3NY/8AnLH932GT9y0v8XmAcjrTspwlmJWSD/Lf7R+EofJGc9rGg7VsrwfSWMaxjWNE
NaAGjwAWJ9cvrG/6tdGPVGUsyNtja/Se8s3b/wB0hrte63V5d/joz3XP6X0Og7rbXm5zB4n9FX95
JWeve3+qXW87r3SKuq5WMzEryJNFbXue7aCWy6WMiY0hbJmDHPaVU6PgM6b0rEwGCBi0sq8dWtAP
4qHXeos6X0bN6g8wMal9g/rAe0fekp5Tov8AjOqzfrO/6v5uNXjn1H0VZVdu9jrGEgD3MZ9KNPNd
yZgxz2leK9S+o+Qz6j9P+seKx37Tr3ZeYQfca7Hb2PiOWCD967bpX17pz/qJldYe9oz8GhzMpnEX
RtY6J4eYhJTp/VT6y531gfmvfi1UYuFe/GbayxzzY9nLmgsaNvzXRLnP8X3THdN+qWDXYCLr2nJu
nndcd+vyhdE5zWNLnGGtEknsAkp4jrX+MHPwfrW36tYXT6sy+x1ba7PWcyDYN0PArdEDUqx1v60f
W7onTrOo5XRcezHpj1PRynPc0HTcQaBouF+rGffmfXPq/wBa24lufXg+pcKqNu+LD6TCA4idtc6c
ra6l9bepfX/Gu6B9WcUU12NBzLct7GOFcj6LWvcYnmAUlPb/AFT+s2P9ZukM6lRWaDudXbS4hxa9
sTBHI1WysT6ofVur6tdEq6ax/qWSbMizs6x0btvGmkBbaSnjPrd9fsn6vdaxuk4+FXm2ZbWln6Us
c0vdsAc0Vu5K6+g3mlhyA1t0e8VkuaD/ACS4A/gvJsT/ALJf8b1lwO/G6c8uBHG3GGxv32L11JSl
yv16+vNf1TqxtlLMvIyXH9XL9jgwD6ejXaTotzrPWMHovTruo57/AE6KRPm535rGju49l5OL+kdc
6V1rrvWM7Gd1zqNTmdPwxYN1NbNWMDB+cdv+spKfUPqt11v1g6HjdWFYpN4dvqDt21zXFhG6B4LW
Xn/+JjNF31avxPzsXJdp5WNDh+Mr0BJTxn1hxqcj61sycofqXTMQZOQDwdrnlrP7RWVU5vT63/Wj
rDRd1DOcXdPxH8tJ+ja6ezRxouv61idPqpvzs94bjbq7b2ED9IKR+jqPiC7svMOrdVv6rnWZuQQ0
v0ZWDoxg+i0fBXMPrAHQAA/wWlBlZWRl5D8nJsNt1pl73ckrf6SftX1P6rhN1txrG5Qb3LdA4/La
ub3N8QtHoPV/2V1FmSQLKHg1ZFfZ1btHfdyp5xuOnSiPohzl6b/i/wCnfZOifaXiLM15s8PYPaz+
9ce/6tPu6zTi4JN/T8127HymCW+ly+SOCziCvVKamU1MprEMraGtHkBAVfmcgMREfpalMQyJABJM
AakleP230fWX/G7SRYx+JiWNbW4uBa4Y7S6GEaHdYvYCAQQRIOhBQ24uM0hzaWNI1BDQCPwVRclX
E/40+oVt6Pj9Gbc2u7quTVU8FwEVB0uc7vtkDVdsh2Y+PYd1lTHuiJc0Ex80lMK8XHbhtw9odjis
VbCJaWbdsfCF4h1j6s9S6P8AWx31axXub03rV1WxonY+k2bmtd51le6gACBoBwExYxzg5zQXN+i4
jUT4JKVXWyqttVY2sYA1o8ABAWD9e+rs6T9Vs+/1BXfZU6rHEgOL7PZ7QeYmV0ChZTVbHqMa+ONw
Bj70lPn/APiXwKqvq/lZktdblXlrmiCWtrEAO+O4rC+tn1f6n9SfrGz60dDYT059m+yusHbWHR6l
VnIDH9j/AHBeu11VVgitjWA87QB+RSc1rgWuALSIIOoISU5nQvrH0rrvT687CubD2g2Ulzd9bu7X
gHQonXuq0dI6RldQue1gpqc5m4gbnwdrRPclBd9U/qw6/wC0npWIbgd2/wBFk7h34Wm+qqwBtjGv
A1AcAR+KSnzD/Erhix/VOrWuDr3ubVB+kAZse7+0YXqFlldTHWWuDK2iXPcQAB4klNXTTUSa62sJ
52gCfuTvYx7S17Q5p5aRIKSnz91jPr/9aTjteH/Vvobg62uZbk3mQD7fzfnx8V1R+qn1ZrDrGdNx
aXtDotbUxpbIIJmNNCtWummqfTY1k87QB+RSIBBBEg6EFJT5J/iczK8XrfVOlusEWtDqRIhxqcWn
b46OXriE3GxmODmVMa4cENAIRUlPPfXf/kmv+a/nmf0j+a7/AEv4Lm8Pj/vA+j/hF40krOL+b+pW
nd9u/wDrdVfK/wDaBwfoLxlJOG6n6E+pX9Gu/mP5z/tP/M8f4Pz/AHl0y+VUlBl+cpGz9VJL5VSU
aX6qSXyqkkp+qkl8qpJKfqpJfKqSSn6qSXyqkkp+qkl8qpJKfqpJfKqSSn6qSXyqkkp+qkl8qpJK
f//ZCg0KZW5kc3RyZWFtDWVuZG9iag0xMjI1IDAgb2JqPDwvTGVuZ3RoIDk4NC9GaWx0ZXIvRmxh
dGVEZWNvZGUvV2lkdGggMTQ0L0hlaWdodCA3Mi9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFj
ZSAxOCAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0KSInsl/dX1DAcwGt7
MuSwHscJ2DSagDSKAwXBhSeK4kBwI05U3IriVlQcIIqoONBzoLj33nvrv2WS66GiPZ7vRn2+fn64
902app+XXr75VhAsLCwsLCwsLCx+op0oiaKtvZ8REZGSKNmijC5Hd2ATxATLxx7bUZY7OfyMiHPG
y67OCUaXE5Pi6QRdguUjKUBVYVd/Pt2QCnCyoU8KohN0D5aPKKuKgv2uTypQNNLD0McJ6AQ9g+Uj
aQiANL/rE1afSGev1NTeff4Zn4i+6XFx6e3+GZ+26cd9+ofJJ0Oi6SOzL40GZIqiJGUJQvbAQYOH
DM1mV3OG2UR3N/qPR8PtBkkmyD65Lpp/RoykUd4oWe4oZ47OHwMhhnjsuPGCUDChsywrDFehQZIJ
sk8RoPln4iQaTZ6oqqDQPiUNcAEAp04TCqZjVeVNzSjJBNmnWKPPS5tBoxJIn+qcCTRFB86aPWcu
VjUTfRQXXSOCiXeJ4DyhlGhaWN9XKx+6k+YvWFgWi1hMFkVHLi5ewuRwF6NDM8Q+ZCl7qn0ZEwK9
2L5bzt4gXGE0QWh90Mos3m1bRbtVl0TDcu5TYo4PnKT3r6YLpGrFJvtowK33r4FGPhE2R/7gQSMr
1obBR3Wt0/vzDHzWOza4MKSgjZs2h95Htuv9JX/2sW/BSE+QCG6tDL2P6NenaBtmKgDwrEm2LzfX
Z0cSYXuQVDlTAI927jLTZ/cetjqkumZvYq17H6HdeH/dAXN88mhUDzWWoQ7yAdGH2Arhwznm+DRQ
g0XUQIs/oo9Yf5SmKHIs47gZPqhUEGIa6VByouXWGjakqvJki0+dp/5Uh5D7nOYVEJjpOcMOVnLW
U+7F08DaqOmczyenqeF884V1xs8Kjs+0Rp5wsF4Ysc3uhXejsouq7pN96XLzmStXo0PsE7GMeEV0
nx/wNq/XuE/uNff1KVk3bgbk06peVSS9n7dAEQuTIdJaikZWKP4CYD+8dKxdkVCUcOtSQDqt6/lY
33nBW65cHtfcRpjCazRFLpR/x1s6Vqyp6HGnNjCfVt87ou/L0Pv1k+Ft1Jbfnedw3GNCZI9d/B29
dBxw/8HuwHT+hkq+8R+G74FtkHUSsXxY7Gv3b3Y4uj4abZ7QhTS2wTc89rbcBGL85GGBeT5Pq/k/
qPQZjW8+f8FWC98yT0cQPITlQFJVdujlK8Tc8Os6M31y3kB+dtA3hXhBVv3WTB16xL9DqCU1qnCq
ve1bQsz7DxizlAwQjP+YbrYN5VP90qTPmvJl5ddvZqv4iIpc/OBgYMemhYWFhYWFxf/EdwEGADXD
Fm8KDQplbmRzdHJlYW0NZW5kb2JqDTEyMjYgMCBvYmo8PC9MZW5ndGggMTk4OS9GaWx0ZXIvRENU
RGVjb2RlL1dpZHRoIDc3L0hlaWdodCA1OC9CaXRzUGVyQ29tcG9uZW50IDgvQ29sb3JTcGFjZSAx
NSAwIFIvVHlwZS9YT2JqZWN0L1N1YnR5cGUvSW1hZ2U+PnN0cmVhbQ0K/9j/4AAQSkZJRgABAQEA
YABgAAD/2wBDAAgGBgcGBQgHBwcJCQgKDBQNDAsLDBkSEw8UHRofHh0aHBwgJC4nICIsIxwcKDcp
LDAxNDQ0Hyc5PTgyPC4zNDL/2wBDAQkJCQwLDBgNDRgyIRwhMjIyMjIyMjIyMjIyMjIyMjIyMjIy
MjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjL/wAARCAA6AE0DASIAAhEBAxEB/8QAHwAAAQUB
AQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUFBAQAAAF9AQIDAAQRBRIhMUEG
E1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkKFhcYGRolJicoKSo0NTY3ODk6Q0RFRkdISUpTVFVW
V1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWmp6ipqrKztLW2t7i5usLD
xMXGx8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEAAwEBAQEBAQEBAQAAAAAA
AAECAwQFBgcICQoL/8QAtREAAgECBAQDBAcFBAQAAQJ3AAECAxEEBSExBhJBUQdhcRMiMoEIFEKR
obHBCSMzUvAVYnLRChYkNOEl8RcYGRomJygpKjU2Nzg5OkNERUZHSElKU1RVVldYWVpjZGVmZ2hp
anN0dXZ3eHl6goOEhYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3uLm6wsPExcbHyMnK0tPU
1dbX2Nna4uPk5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwD3+iiqeqala6PplzqN7IIra3jM
kjnsBQA69vrXTrR7q9uYra3jGXllcKq/UmuGl+KK3u4eGvD+o6xGrbTdbfIt/r5j8VxOpX+o+KNQ
tL3UbFtQvL4+Zovh8tiGGLtcXGP5H1ruLH4ZQXkcc3iy/n1a4AGLZHMNrD/spGmBj60AZh+IvisX
QU6FoIUniE61H5n+FaUPxOazwfEfh3UNKhP/AC9x4ubcfV06Vuf8K98IeQYf+Eb03yyc4+zrWLff
DK0tUefwreT6Ldkf6tXMltJ/svExIwfagDtbDULPVLOO8sbmK5t5BuSWJwykfUVbrwiwutT8M6ne
XGnWf2HVrIiTVtEiObe9h7z24PQ98CvaNJ1W01rS7fUrCXzLW5QPG2McH196AL9FFFABXnXxHkXV
NY8O+FpH22t7O93ecE5hgUvg+xIA/KvRa828ZEf8LH0mPdhpdGv0TPc7Qf5A0AYOh+LNJ8M6ZeeO
dcSV7zXLlorC3iG6QWyHCIoOMLxn06V03hv4t6Rr2sJpNzYX+k3sq7oUvowgl+hzXlthLbaf4g+G
eoamVi01bHYJpfuLIGbqTx1IPtXofjjxV4UHiPRLObSo9d1D55I3tnDNarwSxI9cE/8AAaAEvvjl
oVrdXAg0vVbyytpPLmvoIQYVP1zWxrnxT8PaLpmm3iG5vjqSB7WC0j3SSL0zgkY54ryDR7XU7Xwh
qV/4R8T2baAzSmfStU2K4H8SsDkcjvkZotHsPEUnhB9HuR4Y1pLSVrZiP9Fb95IGCknIJbdxz1oA
6vXfHGl+J7Q69pEF1Za/4ccXElrdRBZJICQsiHGcjB/Cun+H8iaR4k13w1D/AMeB2anp205RYJeq
j0Abt71wOn6lew+Mdc0vxRDpt9qb6NP/AMTO0PIQRk4fHHb0znFb/gVseNfC4UtvPhZPN69N525o
A9looooA4zxz4uvPDN1ottZpZZ1GdoWlvJCkceFzkkVzF5cX2s+KNC1a91zwrEmmTOzCC7JaRHUq
y/MPQmvUrmztbxQtzbQzgdBIgbH51n3XhjQrq1lt5dIsvLlQo2LdQcEY6gcUAeZ3vheez0iTw5eS
+F7zR/tElxZpf3TxyxxuxK4I5GMnkGqvh/Q08KXD3Oix+CYrh1KmWTU5ZGx6AtnH4VQ13QpNDvbL
R9ZlgiNm5Og6zcxB4WT/AJ9rgEdMdD7V1Vl4o8M2LLZ+LfDVnot3gATNaI9tN/tJIFxj60AchfeC
LHUNQkvZ7HwYJZG3usWszIjH/dHA/Cr+saNJrmm2un3lh4G8izXbb+Tq0kTRD0BUZx3wa7s6z8NR
GWNz4a2gZ6Q5/LFc/qPiTQdRjmi8KeGdOvdo+fU7q1SGzgH94uy/Nj0FAHP6X4IvP7NvtL0iHwtZ
peRhL28ttUluJ1hyN2Nw44+grbthqOleMtR1WwvPDUtpJbR2VlHJqpQwwp0GAp5J5rD8N+HH8Qm7
0/QpdtjdSZ1nW0i8oXWOsFuo6J1GfSvXovCfh6G2jt49E04JGgRM2yEgAcckZoA4KHxZ4i8DQWo8
T3NjrFpclfLeymBuU3HgBDjzVGeo5xXqFrcJd2kVxGsipIgcB02sAfUHkGua8M/D/QfC7efbWwnv
ef8AS7j55AD2X+6O2BXW0AFFFFAFW/0+z1Szks763juLaQYeORcg1wsvwvawidPDfiG/023bP+hT
Bbm357BX6D8a9EooA8r/AOFbeIhIWGp+HQcY3jQ49319K1Lb4X211JHL4m1i+1wxkMlvKRHbofaN
ePzr0CigCGCCG1gSC3jWOKMBURBgKB2AqaiigAooooA//9kKDQplbmRzdHJlYW0NZW5kb2JqDTEy
MjcgMCBvYmo8PC9UeXBlL0V4dEdTdGF0ZS9TQSBmYWxzZS9PUCBmYWxzZS9TTSAwLjAyL29wIGZh
bHNlL09QTSAxPj4NZW5kb2JqDTEgMCBvYmo8PC9OdW1zWzAgMiAwIFJdPj4NZW5kb2JqDTIgMCBv
Ymo8PC9TL0Q+Pg1lbmRvYmoNMyAwIG9iajw8L0NvdW50IDEvS2lkc1s5IDAgUl0vVHlwZS9QYWdl
cz4+DWVuZG9iag00IDAgb2JqPDwvTGVuZ3RoIDMzMjIvVHlwZS9NZXRhZGF0YS9TdWJ0eXBlL1hN
TD4+c3RyZWFtDQo8P3hwYWNrZXQgYmVnaW49J++7vycgaWQ9J1c1TTBNcENlaGlIenJlU3pOVGN6
a2M5ZCc/Pgo8P2Fkb2JlLXhhcC1maWx0ZXJzIGVzYz0iQ1JMRiI/Pg0KPHg6eG1wbWV0YSB4bWxu
czp4PSdhZG9iZTpuczptZXRhLycgeDp4bXB0az0nWE1QIHRvb2xraXQgMi45LjEtMTMsIGZyYW1l
d29yayAxLjYnPg0KPHJkZjpSREYgeG1sbnM6cmRmPSdodHRwOi8vd3d3LnczLm9yZy8xOTk5LzAy
LzIyLXJkZi1zeW50YXgtbnMjJyB4bWxuczppWD0naHR0cDovL25zLmFkb2JlLmNvbS9pWC8xLjAv
Jz4NCjxyZGY6RGVzY3JpcHRpb24gcmRmOmFib3V0PSd1dWlkOmZiZDFlOTA2LTA3MjQtNGIzOC05
ZDc2LTBhOWJiOTU2YzQxYScgeG1sbnM6cGRmPSdodHRwOi8vbnMuYWRvYmUuY29tL3BkZi8xLjMv
JyBwZGY6UHJvZHVjZXI9J0Fjcm9iYXQgRGlzdGlsbGVyIDYuMCAoV2luZG93cyknPjwvcmRmOkRl
c2NyaXB0aW9uPg0KPHJkZjpEZXNjcmlwdGlvbiByZGY6YWJvdXQ9J3V1aWQ6ZmJkMWU5MDYtMDcy
NC00YjM4LTlkNzYtMGE5YmI5NTZjNDFhJyB4bWxuczp4YXA9J2h0dHA6Ly9ucy5hZG9iZS5jb20v
eGFwLzEuMC8nIHhhcDpDcmVhdGVEYXRlPScyMDA1LTEwLTAyVDE5OjI4OjU2KzAyOjAwJyB4YXA6
Q3JlYXRvclRvb2w9J1BTY3JpcHQ1LmRsbCBWZXJzaW9uIDUuMicgeGFwOk1vZGlmeURhdGU9JzIw
MDUtMTAtMDJUMTk6Mjg6NTYrMDI6MDAnPjwvcmRmOkRlc2NyaXB0aW9uPg0KPHJkZjpEZXNjcmlw
dGlvbiByZGY6YWJvdXQ9J3V1aWQ6ZmJkMWU5MDYtMDcyNC00YjM4LTlkNzYtMGE5YmI5NTZjNDFh
JyB4bWxuczp4YXBNTT0naHR0cDovL25zLmFkb2JlLmNvbS94YXAvMS4wL21tLycgeGFwTU06RG9j
dW1lbnRJRD0ndXVpZDpiN2E5NGEwZS1iMjBjLTQxMDgtYTUzMC00NDkyZTA4ODk4NzUnLz4NCjxy
ZGY6RGVzY3JpcHRpb24gcmRmOmFib3V0PSd1dWlkOmZiZDFlOTA2LTA3MjQtNGIzOC05ZDc2LTBh
OWJiOTU2YzQxYScgeG1sbnM6ZGM9J2h0dHA6Ly9wdXJsLm9yZy9kYy9lbGVtZW50cy8xLjEvJyBk
Yzpmb3JtYXQ9J2FwcGxpY2F0aW9uL3BkZic+PGRjOmNyZWF0b3I+PHJkZjpTZXE+PHJkZjpsaT5T
dGF2cm9zIFRvdW1waXM8L3JkZjpsaT48L3JkZjpTZXE+PC9kYzpjcmVhdG9yPjxkYzp0aXRsZT48
cmRmOkFsdD48cmRmOmxpIHhtbDpsYW5nPSd4LWRlZmF1bHQnPndpb3B0MDZ2Mi5wdWI8L3JkZjps
aT48L3JkZjpBbHQ+PC9kYzp0aXRsZT48L3JkZjpEZXNjcmlwdGlvbj4NCjwvcmRmOlJERj4NCjwv
eDp4bXBtZXRhPg0KICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIAog
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgCiAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAKICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgIAogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAKICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIAogICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAKICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIAogICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgCiAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAKICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgIAogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
CiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAKICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIAogICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAKICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIAogICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgCiAgICAgICAgICAgICAgICAgICAg
ICAgICAgIAo8P3hwYWNrZXQgZW5kPSd3Jz8+DQplbmRzdHJlYW0NZW5kb2JqDTUgMCBvYmo8PC9N
b2REYXRlKEQ6MjAwNTEwMDIxOTI4NTYrMDInMDAnKS9DcmVhdGlvbkRhdGUoRDoyMDA1MTAwMjE5
Mjg1NiswMicwMCcpL1RpdGxlKHdpb3B0MDZ2Mi5wdWIpL0NyZWF0b3IoUFNjcmlwdDUuZGxsIFZl
cnNpb24gNS4yKS9Qcm9kdWNlcihBY3JvYmF0IERpc3RpbGxlciA2LjAgXChXaW5kb3dzXCkpL0F1
dGhvcihTdGF2cm9zIFRvdW1waXMpPj4NZW5kb2JqDXhyZWYNCjAgNg0KMDAwMDAwMDAwMCA2NTUz
NSBmDQowMDAwMzM2NjYxIDAwMDAwIG4NCjAwMDAzMzY2OTQgMDAwMDAgbg0KMDAwMDMzNjcxNyAw
MDAwMCBuDQowMDAwMzM2NzY3IDAwMDAwIG4NCjAwMDAzNDAxNjUgMDAwMDAgbg0KdHJhaWxlcg0K
PDwvU2l6ZSA2Pj4NCnN0YXJ0eHJlZg0KMTE2DQolJUVPRg0K

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

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

------=_NextPart_000_0023_01C5C789.7C1539E0--





From mip6-bounces@ietf.org Mon Oct 03 08:27:58 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EMPQE-0006k2-Am; Mon, 03 Oct 2005 08:27:58 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EMLP7-0008BH-Vz; Mon, 03 Oct 2005 04:10:34 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA09928;
	Mon, 3 Oct 2005 04:10:31 -0400 (EDT)
Received: from rodin.i2r.a-star.edu.sg ([192.122.139.27])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1EMLXU-00079S-NJ; Mon, 03 Oct 2005 04:19:16 -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 j938AFiR029819;
	Mon, 3 Oct 2005 16:10:15 +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 j938AC4J029765;
	Mon, 3 Oct 2005 16:10:13 +0800 (SGT)
Received: from bearty ([192.168.152.97])by mailhost.lit.org.sg (Sun Java 
	System Messaging Server 6.1 HotFix 0.06(built Nov 11 2004)) with SMTP
	id 
	<0INR001ZNYOOMSB0@mailhost.lit.org.sg>; Mon,03 Oct 2005 16:10:00 +0800 
	(SGT)
Date: Mon, 03 Oct 2005 16:33:25 +0800
From: Boon Sain Yeo <yeobs@i2r.a-star.edu.sg>
To: <Undisclosed-Recipient:@ietf.org;>
Message-id: <024401c5c7f5$1f36d7d0$6198a8c0@bearty>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Mailer: Microsoft Outlook Express 6.00.2800.1437
X-Priority: 3
X-MSMail-priority: Normal
X-imss-version: 2.031
X-imss-result: Passed
X-imss-scores: Clean:99.90000 C:2 M:3 S:5 R:5
X-imss-settings: Baseline:5 C:4 M:4 S:4 R:4 (1.5000 1.5000)
X-Spam-Score: 0.5 (/)
X-Scan-Signature: e367d58950869b6582535ddf5a673488
X-Mailman-Approved-At: Mon, 03 Oct 2005 08:27:54 -0400
Cc: 
Subject: [Mip6] CFP - SensorWare 2006 (deadline extended)
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-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="===============0147372431=="
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0147372431==
Content-type: multipart/alternative;
	boundary="Boundary_(ID_ym05HW4gMhgnJlDYqaaqaQ)"

This is a multi-part message in MIME format.

--Boundary_(ID_ym05HW4gMhgnJlDYqaaqaQ)
Content-type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 7BIT

(My apologies if you receive multiple copies of this message)

***********************************************************
1st International Workshop on Software for Sensor Networks (SensorWare) - CFP
***********************************************************
 

Welcome to the 1st International Workshop on Software for Sensor Networks (SensorWare) to be held on the 8 January 2006. The workshop is held in conjunction with COMSWARE 2006 in the beautiful and historical city of New Delhi.


Advances in technology have made deployment of miniature sensors a realistic proposition. These sensors are low-power, inexpensive, smart devices with multiple on-board sensors, and are connected through wireless links, so as to form a collaborative sensor network to perform a specific task. As a result, it opens up a new paradigm of ubiquitous computing and enables a range of applications that are previously unrealizable or too costly to be realized. However, given the limitation of on-board hardware, one of the key areas towards achieving superior performance is through the software implementation. The workshop is intended for the presentation and discussion of novel algorithms and software implementation for sensor networks. This workshop, intends to bring together engineering experts and academicians to discuss the current status, technical challenges, standards, fundamental issues, and future services and applications in the form of panels and technical presentation.



Topics of interest include but are not limited to the following:



Operating System 
Efficient algorithms 
Protocol design 
Performance analysis 
Performance related issues 
Sensor applications 
Deployment issues and scenarios 
Middleware 
Sensor security 
Sensor network design and modeling 
 

Workshop co-chairs:

Nirmala Shenoy (ns@rit.edu), RIT, USA
Boon Sain Yeo (boonyeo@ieee.org), Institute for Infocomm Research, Singapore 



TPC Members:

Holger Karl, University of Paderborn, Germany,
Ling-Jyh Chen, Academia Sinica, Taiwan
Kui Wu, University of Victoria, Canada,
Daeyoung Kim, ICU, Korea
Leonard Barolli, Fukuoka Institute of Technology, Japan,
Wei-Peng, Fujitsu Labs of America, USA
Jason Redi, BBN Technologies, USA      
Biao Chen, Syracuse University, USA
Hairong  Qi, University of Tennessee, USA
Xiaojun Cao, Rochester Institute of Technology, USA
Xin Wang, University of Buffalo, USA
James Minseok Kwon, RIT, USA
Wenye Wang, North Carolina State University, USA
Fei Hu, RIT, USA
Robin Chellappa, Deakin Univeristy, Australia  

Technical Papers has to be submitted to the co-chairs at boonyeo@ieee.org. 

Papers should be written in English and should preferably follow the instructions in template.pdf. Preferred maximum paper length is 6 printed pages (10-point font) including figures.


Important Dates:

Paper Submission Deadline: 14 October 2005
Notification Acceptance/Rejection: 14 November 2005
Final Camera-Ready Paper Submission: 2 December 2005

Please visit the workshop website at http://www.sensorware.org for more info.

We look forward to seeing you at SensorWare.

Many thanks
Best regards,

Boon and Nirmala
Workshop co-chairs

--Boundary_(ID_ym05HW4gMhgnJlDYqaaqaQ)
Content-type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1476" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>
<DIV><FONT face=3DArial size=3D2>(My apologies if you receive multiple =
copies of=20
this message)</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial=20
size=3D2>***********************************************************<BR>1=
st=20
International Workshop on Software for Sensor Networks (SensorWare) =96=20
CFP<BR>***********************************************************<BR>&nb=
sp;</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Welcome to the 1st International =
Workshop on=20
Software for Sensor Networks (SensorWare) to be held on the 8 January =
2006. The=20
workshop is held in conjunction with COMSWARE 2006 in the beautiful and=20
historical city of New Delhi.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Advances in technology have made =
deployment of=20
miniature sensors a realistic proposition. These sensors are low-power,=20
inexpensive, smart devices with multiple on-board sensors, and are =
connected=20
through wireless links, so as to form a collaborative sensor network to =
perform=20
a specific task. As a result, it opens up a new paradigm of ubiquitous =
computing=20
and enables a range of applications that are previously unrealizable or =
too=20
costly to be realized. However, given the limitation of on-board =
hardware, one=20
of the key areas towards achieving superior performance is through the =
software=20
implementation. The workshop is intended for the presentation and =
discussion of=20
novel algorithms and software implementation for sensor networks. This =
workshop,=20
intends to bring together engineering experts and academicians to =
discuss the=20
current status, technical challenges, standards, fundamental issues, and =
future=20
services and applications in the form of panels and technical=20
presentation.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Topics of interest include but are not =
limited to=20
the following:</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Operating System <BR>Efficient =
algorithms=20
<BR>Protocol design <BR>Performance analysis <BR>Performance related =
issues=20
<BR>Sensor applications <BR>Deployment issues and scenarios =
<BR>Middleware=20
<BR>Sensor security <BR>Sensor network design and=20
modeling&nbsp;<BR>&nbsp;</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Workshop co-chairs:</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Nirmala Shenoy (<A=20
href=3D"mailto:ns@rit.edu">ns@rit.edu</A>), RIT, USA<BR>Boon Sain Yeo =
(<A=20
href=3D"mailto:boonyeo@ieee.org">boonyeo@ieee.org</A>), Institute for =
Infocomm=20
Research, Singapore </FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>TPC Members:</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Holger Karl, University of Paderborn,=20
Germany,<BR>Ling-Jyh Chen, Academia Sinica, Taiwan<BR>Kui Wu, University =
of=20
Victoria, Canada,<BR>Daeyoung Kim, ICU, Korea<BR>Leonard Barolli, =
Fukuoka=20
Institute of Technology, Japan,<BR>Wei-Peng, Fujitsu Labs of America,=20
USA<BR>Jason Redi, BBN Technologies, USA&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
<BR>Biao=20
Chen, Syracuse University, USA<BR>Hairong&nbsp; Qi, University of =
Tennessee,=20
USA<BR>Xiaojun Cao, Rochester Institute of Technology, USA<BR>Xin Wang,=20
University of Buffalo, USA<BR>James Minseok Kwon, RIT, USA<BR>Wenye =
Wang, North=20
Carolina State University, USA<BR>Fei Hu, RIT, USA<BR>Robin Chellappa, =
Deakin=20
Univeristy, Australia&nbsp; </FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Technical Papers has to be submitted to =
the=20
co-chairs at <A href=3D"mailto:boonyeo@ieee.org">boonyeo@ieee.org</A>.=20
</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Papers should be written in English and =
should=20
preferably follow the instructions in template.pdf. Preferred maximum =
paper=20
length is 6 printed pages (10-point font) including =
figures.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><BR>Important Dates:</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Paper Submission Deadline: =
14&nbsp;October=20
2005<BR>Notification Acceptance/Rejection: 14&nbsp;November =
2005<BR>Final=20
Camera-Ready Paper Submission:&nbsp;2&nbsp;December 2005</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Please visit the workshop website at <A =

href=3D"http://www.sensorware.org">http://www.sensorware.org</A> for =
more=20
info.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>We look forward to seeing you at=20
SensorWare.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Many thanks<BR>Best =
regards,</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Boon and Nirmala<BR>Workshop=20
co-chairs</FONT></DIV></FONT></DIV></BODY></HTML>

--Boundary_(ID_ym05HW4gMhgnJlDYqaaqaQ)--


--===============0147372431==
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

--===============0147372431==--




From mip6-bounces@ietf.org Mon Oct 03 09:23:33 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EMQI1-00087P-6G; Mon, 03 Oct 2005 09:23:33 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EMQI0-00087H-53
	for mip6@megatron.ietf.org; Mon, 03 Oct 2005 09:23:32 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28274
	for <mip6@ietf.org>; Mon, 3 Oct 2005 09:23:30 -0400 (EDT)
Received: from dns1.tilab.com ([163.162.42.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EMQQQ-0007B4-DR
	for mip6@ietf.org; Mon, 03 Oct 2005 09:32:18 -0400
Received: from iowa2k01a.cselt.it ([163.162.242.201])
	by dns1.cselt.it (PMDF V6.0-025 #38895)
	with ESMTP id <0INS0038CD6UIH@dns1.cselt.it> for mip6@ietf.org; Mon,
	03 Oct 2005 15:23:18 +0200 (MEST)
Received: from EXC01B.cselt.it ([163.162.4.199]) by iowa2k01a.cselt.it with
	Microsoft SMTPSVC(6.0.3790.211); Mon, 03 Oct 2005 15:23:18 +0200
Date: Mon, 03 Oct 2005 15:23:17 +0200
From: Gerardo Giaretta <Gerardo.Giaretta@TILAB.COM>
Subject: RE: [Mip6] review of draft-ietf-mip6-bootstrapping-split-00.txt
To: James Kempf <Kempf@docomolabs-usa.com>,
	Vijay Devarapallli <dvijay@gmail.com>
Message-id: <DA62A6E0CDD1B34A84557FF1AC850C57016E9B44@EXC01B.cselt.it>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.3790.326
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: quoted-printable
Importance: normal
Priority: normal
Thread-Topic: [Mip6] review of draft-ietf-mip6-bootstrapping-split-00.txt
thread-index: AcXHAtNxib2XhCLLR7CMsOo4XixvpQBEnXeg
Content-Class: urn:content-classes:message
X-OriginalArrivalTime: 03 Oct 2005 13:23:18.0380 (UTC)
	FILETIME=[9E34E2C0:01C5C81D]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b045c2b078f76b9f842d469de8a32de3
Content-Transfer-Encoding: quoted-printable
Cc: mip6@ietf.org, Kilian Weniger <Kilian.Weniger@eu.panasonic.com>,
	Vijay Devarapalli <vijayd@iprg.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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

> I still don't see what the problem is with the text I provided.
>=20
> Suppose we try an example. Let's suppose Alice's MSP is Bob's=20
> Mobile IP=20
> Service (domain name: bobsmova.com). Suppose Bob owns an=20
> access network that=20
> covers Palo Alto and Mountain View in California (actually,=20
> Bob might not=20
> own any access network at all, but for the moment, let's=20
> suppose he does).=20
> Now, suppose Alice is moving north on El Camino Real in Palo=20
> Alto and is=20
> using Bob's HA (ha1.bobsmova.com). She's got an HoA in the=20
> subnet routed by=20
> ha1.bobsmova.com, which just so happens to cover that part of=20
> El Camino Real=20
> between San Antonio and the intersection of Charleston and=20
> Arastadero.=20
> Suppose Alice is paranoid about people tracking her movements=20
> so she never=20
> does route optimization so people never see her care of=20
> address, but she=20
> does put her HoA into the DNS so that people can SIP call her, at=20
> alice.bobsmova.com (Bob also acts as her MSA). Since=20
> ha1.bobsmova.com is=20
> local to Palo Alto, Alice has obtained a local HA and HoA.
>=20
> Now, let's suppose Alice goes to Tucson in order to attend a=20
> conference.=20
> Alice is driving north on Speedway. She uses Bob's Mobile IP=20
> service there=20
> too, and she's got a HoA in Bob's network. Maybe the HA is even=20
> ha1.bobsmova.com. She puts that HoA into Bob's DNS at=20
> alice.bobsmova.com,=20
> and she never uses route optimization.
>=20
> How can anybody deduce any geographical information about=20
> Alice? If Alice=20
> never exposes her care of address and always uses her home=20
> address, how can=20
> they tell if she's between San Antonio and the Charleston/Arastadero=20
> intersection in Palo Alto (covered by the subnet that her=20
> home address is=20
> in), or if she's between the Page Mill Road/Oregon Expressway=20
> intersection=20
> and the Charleston/Arastadero intersection in Palo Alto=20
> (which is in Bob's=20
> network but is not covered by the subnet that Alice 's home=20
> address is in),=20
> or, for that matter, whether she is in Palto Alto at all and=20
> not in Tucson=20
> (which is not covered by Bob's access network)?
>=20

Exactly. From the HoA, CNs can only guess the location where the MN MAY*
have performed bootstrapping procedure. This may be very different from
the current location of the MN.

* moreover, how the CNs know for sure that the MN bootstrapped with a
local HA if bidirectional tunneling is always used? If this the case
(i.e. the CN does not know if the MN has been alloctaed a local HA or
remote HA), is this a real threat to the location privacy of the MN?

--Gerardo=20


>             jakb
>=20
> ----- Original Message -----=20
> From: "Vijay Devarapallli" <dvijay@gmail.com>
> To: "James Kempf" <Kempf@docomolabs-usa.com>
> Cc: "Gerardo Giaretta" <Gerardo.Giaretta@tilab.com>; "Vijay=20
> Devarapalli"=20
> <vijayd@iprg.nokia.com>; "Kilian Weniger"=20
> <Kilian.Weniger@eu.panasonic.com>;=20
> <mip6@ietf.org>
> Sent: Friday, September 30, 2005 4:58 PM
> Subject: Re: [Mip6] review of=20
> draft-ietf-mip6-bootstrapping-split-00.txt
>=20
>=20
> there is some confusion.
>=20
> Jim, Kilian's main concern is when the MN configures a HA
> from the visited link (using location specific HA FQDN).
> the issue is if the MN configures a HA and HoA from the
> visited link and then has its DNS entry updated, then the
> CN knows where the MN is currently located. the MN can
> continue doing DNS updates for home address configured from
> the home link. causes no harm. but when it does a DNS update
> for the home address configured from a HA on a visited link,
> it immediately reveals its location to the CN. maybe we
> could add the following to the security considerations section
>=20
>   A mobile node could hide its location from its correspondent
>   node by reverse tunneling all traffic through the home agent.
>   The same mobile node could roam and configure a home agent
>   and home address from a visited link. If the home agent
>   updates the DNS entry of the mobile node with its new home
>   address, then this may reveal the current location of the
>   mobile node to the correspondent node. In such a if the mobile
>   node does not want the correspondent node to know its current
>   location, then it should not request the home agent to update
>   the DNS entry.
>=20
> comments?
>=20
> Vijay
>=20
> On 9/30/05, James Kempf <Kempf@docomolabs-usa.com> wrote:
> > Comments.
> >
> > "Note that local HA assignment combined with DNS updates=20
> may violate the
> > location privacy of MN. A known solution to location=20
> privacy is to hide
> > the CoA from CN by using reverse tunneling to the HA
> > [draft-koodli-mip6-location-privacy-solutions-00.txt].=20
> However, reverse
> > tunneling may significantly decrease routing efficiency,=20
> depending on
> > how far the HA is off the direct path between MN and CN.The
> > bootstrapping solution supports local HA assignment to=20
> improve routing
> > efficiency, but since the HoA obtained from a local HA assignment
> > topologically belongs to the visited network, it contains location
> > information. Consequently, it must carefully be considered=20
> to whom this
> > HoA is revealed and whether DNS updates are requested for=20
> this HoA. The
> > latter can even enable others to track MN's movement, if=20
> the MN uses an
> > eager strategy for local HA assignment. On the other hand,=20
> if the HoA is
> > hidden from other nodes, they cannot reach the MN at this=20
> HoA and, thus,
> > cannot benefit from the local HA assignment in terms of routing
> > efficiency. "
> >
> >  jak>> I have a couple problems with this:
> >
> > 1)  Reverse tunneling is the default in IPv6, that is to=20
> say, if an HA is
> > used, reverse tunneling must be used, unless the traffic is route=20
> > optimized.
> > So it is more accurate to say that in order to protect=20
> privacy, the MN=20
> > must
> > not route optimize traffic.
> >
> > 2) The solution in draft-ietf-mip6-bootstrapping-split does=20
> not specify
> > anything for local home agent assignment. There is nothing=20
> in the protocol
> > to actually move the HA from the MSP's network to the=20
> serving network. The
> > MN gets to choose an HA from whatever HAs the MSP's DNS SRV=20
> RR advertises.
> > If that happens to be in the serving network, then=20
> correspondents will be
> > able to obtain some information about where the MN is, but it could=20
> > equally
> > well be on the other side of the globe.
> >
> > Note that the integrated scenerio (which the DT is=20
> currently working on)
> > will have a mechanism whereby a local home agent can be=20
> assigned, since=20
> > the
> > MN gets the HA address from the local DHCP server.
> >
> > 3) Since the HoA doesn't change once the MN has established=20
> it, I fail to
> > see how an attacker can track the MN's location. Once the MN has=20
> > established
> > the HoA, it will appear to be at a fixed topological=20
> location in the MSP's
> > network regardless of where the care of address is, if=20
> route optimization=20
> > is
> > not used.
> >
> > So I think the risk is considerably less that is portrayed=20
> by the above
> > text. I think the following text would be more accurate:
> >
> >     Updating the mobile node's FQDN in the DNS
> >     with the mobile node's home address has the
> >     potential to expose some information about
> >     the mobile node's location to correspondents
> >     if the home agent selected by the mobile
> >     node is in the serving network access provider's
> >     network (that is, the serving network access
> >     provider is also acting as the mobility service
> >     provider). The risk here is not as deep as
> >     with route optimization, since the mobile node
> >     will effectively appear to be at a fixed topological
> >     location in the mobility service provider's network
> >     regardless of where the care of address is. To
> >     mitigate the risk, the mobile node should
> >     either not request DNS update or be careful
> >     to select a home agent that is not within the
> >     serving network access provider's network.
> >
> >
> >             jak
> >
> >
> >
> >
> >
> >
> > _______________________________________________
> > Mip6 mailing list
> > Mip6@ietf.org
> > https://www1.ietf.org/mailman/listinfo/mip6
> >
>=20
>=20
>=20


Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia =
S.p.A.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
CONFIDENTIALITY NOTICE
This message and its attachments are addressed solely to the persons
above and may contain confidential information. If you have received
the message in error, be informed that any use of the content hereof
is prohibited. Please return it immediately to the sender and delete
the message. Should you have any questions, please send an e_mail to=20
MailAdmin@tilab.com. Thank you
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

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



From mip6-bounces@ietf.org Mon Oct 03 09:59:54 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EMQrC-0006SY-K4; Mon, 03 Oct 2005 09:59:54 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EMQrB-0006ST-MO
	for mip6@megatron.ietf.org; Mon, 03 Oct 2005 09:59:53 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29707
	for <mip6@ietf.org>; Mon, 3 Oct 2005 09:59:51 -0400 (EDT)
Received: from av6-1-sn3.vrr.skanova.net ([81.228.9.179])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EMQze-00080H-G5
	for mip6@ietf.org; Mon, 03 Oct 2005 10:08:40 -0400
Received: by av6-1-sn3.vrr.skanova.net (Postfix, from userid 502)
	id 0B64F38316; Mon,  3 Oct 2005 15:59:38 +0200 (CEST)
Received: from smtp3-2-sn3.vrr.skanova.net (smtp3-2-sn3.vrr.skanova.net
	[81.228.9.102])
	by av6-1-sn3.vrr.skanova.net (Postfix) with ESMTP id E4DC438054
	for <mip6@ietf.org>; Mon,  3 Oct 2005 15:59:37 +0200 (CEST)
Received: from shiraz.levkowetz.com (81-224-201-50-no45.tbcn.telia.com
	[81.224.201.50])
	by smtp3-2-sn3.vrr.skanova.net (Postfix) with ESMTP id B70DB37E4A
	for <mip6@ietf.org>; Mon,  3 Oct 2005 15:59:37 +0200 (CEST)
Received: from shiraz.local.levkowetz.com ([192.168.3.14]
	helo=81-224-201-50-no45.tbcn.telia.com)
	by shiraz.levkowetz.com with esmtp (Exim 4.52) id 1EMQqq-0007Xv-Bt
	for mip6@ietf.org; Mon, 03 Oct 2005 15:59:34 +0200
Content-Type: text/plain; charset=utf-8
To: mip6@ietf.org
From: Gerardo <tracker-mip6@mip4.org>
Date: Mon, 03 Oct 2005 13:59:31 +0000
MIME-Version: 1.0
Message-Id: <1128347971.05.0.711264016315.issue45@mip4.org>
X-Roundup-Name: Mip6 issue tracker
X-Roundup-Loop: hello
Content-Transfer-Encoding: quoted-printable
X-Helo-Check-Failed: Verification failed for HELO
	81-224-201-50-no45.tbcn.telia.com
X-SA-Exim-Connect-IP: 192.168.3.14
X-SA-Exim-Mail-From: roundup-admin@mip4.org
X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on 
	shiraz.levkowetz.com
X-Spam-Status: No, score=-103.8 required=2.5 tests=ALL_TRUSTED,AWL,BAYES_00,
	MIME_QP_LONG_LINE, USER_IN_WHITELIST, X_HELO_CHECK_FAILED autolearn=ham 
	version=3.0.4
X-SA-Exim-Version: 4.2 (built Thu, 03 Mar 2005 10:44:12 +0100)
X-SA-Exim-Scanned: Yes (on shiraz.levkowetz.com)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Content-Transfer-Encoding: quoted-printable
Subject: [Mip6] [issue45] Definition of Integrated Scenario
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Mip6 issue tracker <tracker-mip6@mip4.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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org


New submission from Gerardo <gerardo.giaretta@tilab.com>:

The definition of the integrated scenario in draft-ietf-mip6-bootstrap-ps-0=
3=20
is misleading. This depends on the change of terminology we have done from=20
version 02.=20
In integrated scenario, the entity that authenticates and authorizes the us=
er=20
for network access is the same entity that authenticates and authorizes the=20
user for mobility service. Based on section 3, this implies that MSA=3D=3DA=
SA. The=20
description in section 7.2 and the Figure 1 must be corrected.=20

Old text:
"
7=2E2  Integrated ASP network scenario

   In this scenario, the ASP and MSP are the same ASP.
"

Proposed text:
"
7=2E2  Integrated ASP network scenario

   In this scenario, the ASA and MSA are the same entity.
"


Old Figure:

                        +----------------------------+
                        | IASP(ASP+MSP)              |
           +----+    +-----+         +----+          |
           | MN |--- | NAS |         | HA |          |
           +----+    +-----+         +----+          |
                        | \            \             |
                        |  \ +------+   \ +-------+  |
                        |   -|AAA-NA|    -|AAA-MIP|  |
                        |    +------+     +-------+  |
                        +----------------------------+


New Figure:

                        +----------------------------+
                        | IASP(ASA+MSA)              |
           +----+    +-----+         +----+          |
           | MN |--- | NAS |         | HA |          |
           +----+    +-----+         +----+          |
                        | \            \             |
                        |  \ +------+   \ +-------+  |
                        |   -|AAA-NA|    -|AAA-MIP|  |
                        |    +------+     +-------+  |
                        +----------------------------+



More generally, I think terminology should be improved in draft-ietf-mip6-
bootstrap-ps-03. There are several terms with quite similar meanings: MSP,=20
serving MSP, home MSP, MSA. In my view we could keep it very simple using t=
he=20
terms MSP and MSA (and similarly ASP and ASA): the MSP is the entity that=20
provides the Home Agent, the MSA is the entity that authenticates and=20
authorizes the user for mobility service.=20
For example, in Figure 2 I would suggest to have "MSA" in the box on the ri=
ght=20
instead of "home MSP".

--Gerardo

----------
category: Editorial
draft: draft-ietf-mip6-bootstrap-ps
messages: 166
nosy: gerardo
priority: Should fix
status: Pending
title: Definition of Integrated Scenario

_________________________________________________
Mip6 issue tracker <tracker-mip6@mip4.org>
<http://www.mip4.org/issues/tracker/mip6/issue45>
_________________________________________________

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



From mip6-bounces@ietf.org Mon Oct 03 10:16:11 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EMR34-00008X-Sy; Mon, 03 Oct 2005 10:12:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EMR32-00008A-QI
	for mip6@megatron.ietf.org; Mon, 03 Oct 2005 10:12:08 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01380
	for <mip6@ietf.org>; Mon, 3 Oct 2005 10:12:07 -0400 (EDT)
Received: from av6-1-sn3.vrr.skanova.net ([81.228.9.179])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EMRBW-0008On-7J
	for mip6@ietf.org; Mon, 03 Oct 2005 10:20:55 -0400
Received: by av6-1-sn3.vrr.skanova.net (Postfix, from userid 502)
	id 6C68938059; Mon,  3 Oct 2005 16:11:53 +0200 (CEST)
Received: from smtp3-1-sn3.vrr.skanova.net (smtp3-1-sn3.vrr.skanova.net
	[81.228.9.101])
	by av6-1-sn3.vrr.skanova.net (Postfix) with ESMTP id 5736037EEF
	for <mip6@ietf.org>; Mon,  3 Oct 2005 16:11:53 +0200 (CEST)
Received: from shiraz.levkowetz.com (81-224-201-50-no45.tbcn.telia.com
	[81.224.201.50])
	by smtp3-1-sn3.vrr.skanova.net (Postfix) with ESMTP id 4528137E45
	for <mip6@ietf.org>; Mon,  3 Oct 2005 16:11:53 +0200 (CEST)
Received: from shiraz.local.levkowetz.com ([192.168.3.14]
	helo=81-224-201-50-no45.tbcn.telia.com)
	by shiraz.levkowetz.com with esmtp (Exim 4.52) id 1EMR2m-0008Eg-JV
	for mip6@ietf.org; Mon, 03 Oct 2005 16:11:53 +0200
Content-Type: text/plain; charset=utf-8
To: mip6@ietf.org
From: Gerardo <tracker-mip6@mip4.org>
Date: Mon, 03 Oct 2005 14:11:52 +0000
MIME-Version: 1.0
Message-Id: <1128348712.56.0.0484401827909.issue46@mip4.org>
X-Roundup-Name: Mip6 issue tracker
X-Roundup-Loop: hello
Content-Transfer-Encoding: quoted-printable
X-Helo-Check-Failed: Verification failed for HELO
	81-224-201-50-no45.tbcn.telia.com
X-SA-Exim-Connect-IP: 192.168.3.14
X-SA-Exim-Mail-From: roundup-admin@mip4.org
X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on 
	shiraz.levkowetz.com
X-Spam-Status: No, score=-103.8 required=2.5 tests=ALL_TRUSTED,AWL,BAYES_00,
	USER_IN_WHITELIST,X_HELO_CHECK_FAILED autolearn=ham version=3.0.4
X-SA-Exim-Version: 4.2 (built Thu, 03 Mar 2005 10:44:12 +0100)
X-SA-Exim-Scanned: Yes (on shiraz.levkowetz.com)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Content-Transfer-Encoding: quoted-printable
Subject: [Mip6] [issue46] Authorization using PKI
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Mip6 issue tracker <tracker-mip6@mip4.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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org


New submission from Gerardo <gerardo.giaretta@tilab.com>:

Rafa raised this editorial issue concerning the authorization of the servic=
e=20
if public keys are used instead of EAP in IKEv2

This refers to text in section 5.4.
"
Due to all these reasons, the Home Agent may need to contact the MSA in
order to authenticate the Mobile Node and authorize mobility service.
This can be accomplished based on a Public Key Infrastructure if
certificates are used and a PKI is deployed by the MSP and MSA.
"

Some clarifying text is needed. Figure 1 needs to be updated.

----------
category: Editorial
draft: draft-ietf-mip6-bootstrapping-split
messages: 167
nosy: gerardo
priority: Should fix
status: Need clarifying text
title: Authorization using PKI

_________________________________________________
Mip6 issue tracker <tracker-mip6@mip4.org>
<http://www.mip4.org/issues/tracker/mip6/issue46>
_________________________________________________

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



From mip6-bounces@ietf.org Mon Oct 03 10:14:51 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EMR5f-0000TS-MU; Mon, 03 Oct 2005 10:14:51 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EMR5e-0000TG-R3
	for mip6@megatron.ietf.org; Mon, 03 Oct 2005 10:14:50 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01962
	for <mip6@ietf.org>; Mon, 3 Oct 2005 10:14:49 -0400 (EDT)
Received: from av9-1-sn2.hy.skanova.net ([81.228.8.179])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EMRE8-0008Va-7E
	for mip6@ietf.org; Mon, 03 Oct 2005 10:23:37 -0400
Received: by av9-1-sn2.hy.skanova.net (Postfix, from userid 502)
	id D0AB038011; Mon,  3 Oct 2005 16:14:37 +0200 (CEST)
Received: from smtp4-1-sn2.hy.skanova.net (smtp4-1-sn2.hy.skanova.net
	[81.228.8.92])
	by av9-1-sn2.hy.skanova.net (Postfix) with ESMTP id B233238011
	for <mip6@ietf.org>; Mon,  3 Oct 2005 16:14:37 +0200 (CEST)
Received: from shiraz.levkowetz.com (81-224-201-50-no45.tbcn.telia.com
	[81.224.201.50])
	by smtp4-1-sn2.hy.skanova.net (Postfix) with ESMTP id A4AB837E4D
	for <mip6@ietf.org>; Mon,  3 Oct 2005 16:14:37 +0200 (CEST)
Received: from shiraz.local.levkowetz.com ([192.168.3.14]
	helo=81-224-201-50-no45.tbcn.telia.com)
	by shiraz.levkowetz.com with esmtp (Exim 4.52) id 1EMR5Q-0007zA-LF
	for mip6@ietf.org; Mon, 03 Oct 2005 16:14:37 +0200
Content-Type: text/plain; charset=utf-8
To: mip6@ietf.org
From: Gerardo <tracker-mip6@mip4.org>
Date: Mon, 03 Oct 2005 14:14:36 +0000
MIME-Version: 1.0
Message-Id: <1128348876.37.0.810387978271.issue47@mip4.org>
X-Roundup-Name: Mip6 issue tracker
X-Roundup-Loop: hello
Content-Transfer-Encoding: quoted-printable
X-Helo-Check-Failed: Verification failed for HELO
	81-224-201-50-no45.tbcn.telia.com
X-SA-Exim-Connect-IP: 192.168.3.14
X-SA-Exim-Mail-From: roundup-admin@mip4.org
X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on 
	shiraz.levkowetz.com
X-Spam-Status: No, score=-103.8 required=2.5 tests=ALL_TRUSTED,AWL,BAYES_00,
	MIME_QP_LONG_LINE, USER_IN_WHITELIST, X_HELO_CHECK_FAILED autolearn=ham 
	version=3.0.4
X-SA-Exim-Version: 4.2 (built Thu, 03 Mar 2005 10:44:12 +0100)
X-SA-Exim-Scanned: Yes (on shiraz.levkowetz.com)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Content-Transfer-Encoding: quoted-printable
Subject: [Mip6] [issue47] Role of the AAA of the MSP
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Mip6 issue tracker <tracker-mip6@mip4.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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org


New submission from Gerardo <gerardo.giaretta@tilab.com>:

Rafa raised this issue concerning the role of the MSP-AAA in bootstrapping=20
MIPv6.

Rafa wrote:
"
MSP's AAA server is the entity that finally takes decision about if
the mobility service is authorized or not. MSA's AAA server could send
to MSP's AAA some kind of evidences or attributes related with
authenticated user.Following these attributes and internal policies
MSP's AAA server takes a final decision.
"

James, Gerardo:=20
the MSA takes the final decision since it owns the user's profile and user'=
s=20
credentials. The role of the MSP is based on roaming/business agreements.

----------
category: Editorial
draft: draft-ietf-mip6-bootstrapping-split
messages: 168
nosy: gerardo
priority: Should fix
status: Rejected
title: Role of the AAA of the MSP

_________________________________________________
Mip6 issue tracker <tracker-mip6@mip4.org>
<http://www.mip4.org/issues/tracker/mip6/issue47>
_________________________________________________

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



From mip6-bounces@ietf.org Mon Oct 03 10:54:37 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EMRi8-0007Ss-UR; Mon, 03 Oct 2005 10:54:36 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EMRi7-0007RC-K6
	for mip6@megatron.ietf.org; Mon, 03 Oct 2005 10:54:35 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA09247
	for <mip6@ietf.org>; Mon, 3 Oct 2005 10:54:33 -0400 (EDT)
Received: from av9-1-sn2.hy.skanova.net ([81.228.8.179])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EMRqb-0001Za-3g
	for mip6@ietf.org; Mon, 03 Oct 2005 11:03:22 -0400
Received: by av9-1-sn2.hy.skanova.net (Postfix, from userid 502)
	id 38C1438044; Mon,  3 Oct 2005 16:54:25 +0200 (CEST)
Received: from smtp4-2-sn2.hy.skanova.net (smtp4-2-sn2.hy.skanova.net
	[81.228.8.93])
	by av9-1-sn2.hy.skanova.net (Postfix) with ESMTP id 1EB1038038
	for <mip6@ietf.org>; Mon,  3 Oct 2005 16:54:25 +0200 (CEST)
Received: from shiraz.levkowetz.com (81-224-201-50-no45.tbcn.telia.com
	[81.224.201.50])
	by smtp4-2-sn2.hy.skanova.net (Postfix) with ESMTP id 0D5A837E5C
	for <mip6@ietf.org>; Mon,  3 Oct 2005 16:54:25 +0200 (CEST)
Received: from shiraz.local.levkowetz.com ([192.168.3.14]
	helo=81-224-201-50-no45.tbcn.telia.com)
	by shiraz.levkowetz.com with esmtp (Exim 4.52) id 1EMRhv-00029j-PO
	for mip6@ietf.org; Mon, 03 Oct 2005 16:54:24 +0200
Content-Type: text/plain; charset=utf-8
To: mip6@ietf.org
From: Gerardo <tracker-mip6@mip4.org>
Date: Mon, 03 Oct 2005 14:54:23 +0000
MIME-Version: 1.0
Message-Id: <1128351263.75.0.479761074801.issue50@mip4.org>
X-Roundup-Name: Mip6 issue tracker
X-Roundup-Loop: hello
Content-Transfer-Encoding: quoted-printable
X-Helo-Check-Failed: Verification failed for HELO
	81-224-201-50-no45.tbcn.telia.com
X-SA-Exim-Connect-IP: 192.168.3.14
X-SA-Exim-Mail-From: roundup-admin@mip4.org
X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on 
	shiraz.levkowetz.com
X-Spam-Status: No, score=-103.8 required=2.5 tests=ALL_TRUSTED,AWL,BAYES_00,
	USER_IN_WHITELIST,X_HELO_CHECK_FAILED autolearn=ham version=3.0.4
X-SA-Exim-Version: 4.2 (built Thu, 03 Mar 2005 10:44:12 +0100)
X-SA-Exim-Scanned: Yes (on shiraz.levkowetz.com)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Content-Transfer-Encoding: quoted-printable
Subject: [Mip6] [issue50] Identity issue in Home Address auto-configuration
	by the Mobile Node (from Jari's review)
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Mip6 issue tracker <tracker-mip6@mip4.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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org


New submission from Gerardo <gerardo.giaretta@tilab.com>:

Jari wrote:
>>One potential issue (and this is also an issue in [6]) is
>>that the identity given in EAP-based authentication
>>is not necessarily something that you can tie a long-term
>>home address identity to. For instance, the identity
>>could be a pseudonym (e.g. EAP-SIM), or a privacy NAI (e.g.
>>RFC2486bis).=20
>>   =20

Gerardo:
>I see the issue. I guess the same issue applies to VPN that makes use of
>IKEv2-EAP. How is it handled in that case? Since the AAA server knows
>the long-term identity of the MN, maybe the AAA server may have an
>active role to create the matching between the identity and the HoA.


Jari:
"
Well, there may be AAA ways of communicating this to
the home agent/vpn gateway, such as the use of the
Chargeable-User-Identity attribute, or some IP address
attributes. Some work would be need to study whether
those are sufficient or if something else is needed, and
in case all this would have to be documented somewhere
so that implementors would know what to do.
"

----------
category: Technical
draft: draft-ietf-mip6-bootstrapping-split
messages: 171
nosy: gerardo
priority: Should fix
status: Pending
title: Identity issue in Home Address auto-configuration by the Mobile Node=
 (from Jari's review)

_________________________________________________
Mip6 issue tracker <tracker-mip6@mip4.org>
<http://www.mip4.org/issues/tracker/mip6/issue50>
_________________________________________________

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



From mip6-bounces@ietf.org Mon Oct 03 10:57:12 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EMRke-0007sq-3j; Mon, 03 Oct 2005 10:57:12 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EMRkc-0007sl-3A
	for mip6@megatron.ietf.org; Mon, 03 Oct 2005 10:57:10 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA09547
	for <mip6@ietf.org>; Mon, 3 Oct 2005 10:57:08 -0400 (EDT)
Received: from av11-2-sn2.hy.skanova.net ([81.228.8.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EMRt5-0001hL-Ms
	for mip6@ietf.org; Mon, 03 Oct 2005 11:05:57 -0400
Received: by av11-2-sn2.hy.skanova.net (Postfix, from userid 502)
	id 7658A382CE; Mon,  3 Oct 2005 16:56:59 +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 67D0B38022
	for <mip6@ietf.org>; Mon,  3 Oct 2005 16:56:59 +0200 (CEST)
Received: from shiraz.levkowetz.com (81-224-201-50-no45.tbcn.telia.com
	[81.224.201.50])
	by smtp4-2-sn2.hy.skanova.net (Postfix) with ESMTP id 59A6D37E45
	for <mip6@ietf.org>; Mon,  3 Oct 2005 16:56:59 +0200 (CEST)
Received: from shiraz.local.levkowetz.com ([192.168.3.14]
	helo=81-224-201-50-no45.tbcn.telia.com)
	by shiraz.levkowetz.com with esmtp (Exim 4.52) id 1EMRkQ-0002G2-KY
	for mip6@ietf.org; Mon, 03 Oct 2005 16:56:59 +0200
Content-Type: text/plain; charset=utf-8
To: mip6@ietf.org
From: Gerardo <tracker-mip6@mip4.org>
Date: Mon, 03 Oct 2005 14:56:58 +0000
MIME-Version: 1.0
Message-Id: <1128351418.6.0.833749025971.issue51@mip4.org>
X-Roundup-Name: Mip6 issue tracker
X-Roundup-Loop: hello
Content-Transfer-Encoding: quoted-printable
X-Helo-Check-Failed: Verification failed for HELO
	81-224-201-50-no45.tbcn.telia.com
X-SA-Exim-Connect-IP: 192.168.3.14
X-SA-Exim-Mail-From: roundup-admin@mip4.org
X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on 
	shiraz.levkowetz.com
X-Spam-Status: No, score=-103.8 required=2.5 tests=ALL_TRUSTED,AWL,BAYES_00,
	USER_IN_WHITELIST,X_HELO_CHECK_FAILED autolearn=ham version=3.0.4
X-SA-Exim-Version: 4.2 (built Thu, 03 Mar 2005 10:44:12 +0100)
X-SA-Exim-Scanned: Yes (on shiraz.levkowetz.com)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Content-Transfer-Encoding: quoted-printable
Subject: [Mip6] [issue51] CGA check (from Jari's review)
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Mip6 issue tracker <tracker-mip6@mip4.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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org


New submission from Gerardo <gerardo.giaretta@tilab.com>:

Jari wrote:
>>Another issue is that it would seem to be
>>useful that where CGA-based addresses are used that the
>>home agent would actually check the ownership.

Gerardo wrote:
>I think what we should investigate better is how CGAs can be used with
>MIPv6. And this is a problem that is different and seems orthogonal to
>bootstrapping. The HA may check the ownership when receiving a BU (if
>the MN includes a CGA option in the BU), while having this check
>performed during IKEv2 exchange seems to me more problematic.
> =20

Jari wrote:
> I agree

Gerardo:
>The usage of a CGA as HA may be useful to avoid some attacks in the home
>link or having a more secure way to perform the returning home
>procedure. However, I'm not sure if this is a problem related to
>bootstrapping. If the check is done when receiving a BU, I think it is
>orthogonal to bootstrapping. I don't see any reason (e.g. possible
>attacks) why the check should be done during IKEv2 exchange, but maybe
>I'm missing something.

Jari:
> You may be right.

----------
category: Technical
draft: draft-ietf-mip6-bootstrapping-split
messages: 172
nosy: gerardo
priority: Should fix
status: Possible reject
title: CGA check (from Jari's review)

_________________________________________________
Mip6 issue tracker <tracker-mip6@mip4.org>
<http://www.mip4.org/issues/tracker/mip6/issue51>
_________________________________________________

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



From mip6-bounces@ietf.org Mon Oct 03 11:01:10 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EMRoU-00007X-Tx; Mon, 03 Oct 2005 11:01:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EMRoT-00007S-N8
	for mip6@megatron.ietf.org; Mon, 03 Oct 2005 11:01:09 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10038
	for <mip6@ietf.org>; Mon, 3 Oct 2005 11:01:07 -0400 (EDT)
Received: from av11-2-sn2.hy.skanova.net ([81.228.8.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EMRwv-0001tn-6N
	for mip6@ietf.org; Mon, 03 Oct 2005 11:09:56 -0400
Received: by av11-2-sn2.hy.skanova.net (Postfix, from userid 502)
	id B4169382D1; Mon,  3 Oct 2005 17:00:56 +0200 (CEST)
Received: from smtp4-1-sn2.hy.skanova.net (smtp4-1-sn2.hy.skanova.net
	[81.228.8.92])
	by av11-2-sn2.hy.skanova.net (Postfix) with ESMTP id A49A737FCD
	for <mip6@ietf.org>; Mon,  3 Oct 2005 17:00:56 +0200 (CEST)
Received: from shiraz.levkowetz.com (81-224-201-50-no45.tbcn.telia.com
	[81.224.201.50])
	by smtp4-1-sn2.hy.skanova.net (Postfix) with ESMTP id 8F43237E56
	for <mip6@ietf.org>; Mon,  3 Oct 2005 17:00:55 +0200 (CEST)
Received: from shiraz.local.levkowetz.com ([192.168.3.14]
	helo=81-224-201-50-no45.tbcn.telia.com)
	by shiraz.levkowetz.com with esmtp (Exim 4.52) id 1EMRoE-0002Lh-Db
	for mip6@ietf.org; Mon, 03 Oct 2005 17:00:55 +0200
Content-Type: text/plain; charset=utf-8
To: mip6@ietf.org
From: Gerardo <tracker-mip6@mip4.org>
Date: Mon, 03 Oct 2005 15:00:54 +0000
MIME-Version: 1.0
Message-Id: <1128351654.38.0.895324013474.issue52@mip4.org>
X-Roundup-Name: Mip6 issue tracker
X-Roundup-Loop: hello
Content-Transfer-Encoding: quoted-printable
X-Helo-Check-Failed: Verification failed for HELO
	81-224-201-50-no45.tbcn.telia.com
X-SA-Exim-Connect-IP: 192.168.3.14
X-SA-Exim-Mail-From: roundup-admin@mip4.org
X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on 
	shiraz.levkowetz.com
X-Spam-Status: No, score=-103.8 required=2.5 tests=ALL_TRUSTED,AWL,BAYES_00,
	MIME_QP_LONG_LINE, USER_IN_WHITELIST, X_HELO_CHECK_FAILED autolearn=ham 
	version=3.0.4
X-SA-Exim-Version: 4.2 (built Thu, 03 Mar 2005 10:44:12 +0100)
X-SA-Exim-Scanned: Yes (on shiraz.levkowetz.com)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac
Content-Transfer-Encoding: quoted-printable
Subject: [Mip6] [issue52] Address Authorization in DNS update
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Mip6 issue tracker <tracker-mip6@mip4.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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org


New submission from Gerardo <gerardo.giaretta@tilab.com>:

Jari wrote:
>>Hmm. An address authorization issue appears to come to the picture
>>even in the home agent based solution. We don't want a mobile node
>>M1 to take over the DNS name of mobile node M2. That's why the
>>home agent, or someone, needs to authorize the use of a particular
>>fqdn. This is later correctly noted, but not here.
>>
>>
>>
Gerardo wrote:
>So, if I understand correctly, your point is that, even if the HA
>performs the DNS update, it needs to get in touch with the AAA server
>(or equivalent) to check if the MN is authorized to use that particular
>FQDN. If so, I think it makes sense and I'll provide some text to
>address it.
>
>
Jari wrote:
"
Yes. The check may be an implementation issue, but before you
do the check, you need protocols to transport enough information
around so that you'll actually be able to make the check.
"

and Jari wrote:
>>I'm not sure its just an implementation issue. If its the
>>home agent that
>>performs such an update, then its likely that some AAA attributes
>>are needed to support that (authorized-fqdn,
>>feel-free-to-trust-the-mobile-node-
>>on-its-any-request attributes, for instance). Similarly, if its the
>>AAA server that performs the update, then the fqdn needs to be
>>carried in the protocol.
>>

Gerardo wrote:
>Yes. These attributes are needed in the AAA-HA communication and should
>be listed as goals for AAA-HA interface.
>In this draft we did not address AAA backend issues. Do you think that
>text should be improved somehow? A reference to an update of [12] may
be
>useful, as we have done in section 6, paragraph 5.
>

Jari wrote:
"
It might be prudent to at least point out the requirement
to transport this particular piece of information, and perhaps
even stating that at the time of writing this no such attribute
has been defined for commonly used aaa protocols.
"

James wrote:
"
I agree. We need to mention that the HA must perform an address=20
authorization check. Even if the address is a CGA, the HA will have to=20
determine that the MN actually owns the FQDN. If there's an AAA server=20
involved, it can certainly be contacted as Jari mentions, but if not (i.e.=20
PKI) it gets tricky.
"

----------
category: Editorial
draft: draft-ietf-mip6-bootstrapping-split
messages: 173
nosy: gerardo
priority: Should fix
status: Pending
title: Address Authorization in DNS update

_________________________________________________
Mip6 issue tracker <tracker-mip6@mip4.org>
<http://www.mip4.org/issues/tracker/mip6/issue52>
_________________________________________________

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



From mip6-bounces@ietf.org Mon Oct 03 11:03:21 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EMRqb-0000WK-Qx; Mon, 03 Oct 2005 11:03:21 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EMRqZ-0000WC-GH
	for mip6@megatron.ietf.org; Mon, 03 Oct 2005 11:03:19 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10279
	for <mip6@ietf.org>; Mon, 3 Oct 2005 11:03:17 -0400 (EDT)
Received: from av9-2-sn3.vrr.skanova.net ([81.228.9.186])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EMRz3-0001ys-9V
	for mip6@ietf.org; Mon, 03 Oct 2005 11:12:06 -0400
Received: by av9-2-sn3.vrr.skanova.net (Postfix, from userid 502)
	id 6283D380EE; Mon,  3 Oct 2005 17:03:08 +0200 (CEST)
Received: from smtp3-1-sn3.vrr.skanova.net (smtp3-1-sn3.vrr.skanova.net
	[81.228.9.101])
	by av9-2-sn3.vrr.skanova.net (Postfix) with ESMTP id 4C483380D3
	for <mip6@ietf.org>; Mon,  3 Oct 2005 17:03:08 +0200 (CEST)
Received: from shiraz.levkowetz.com (81-224-201-50-no45.tbcn.telia.com
	[81.224.201.50])
	by smtp3-1-sn3.vrr.skanova.net (Postfix) with ESMTP id 3B9E337E4C
	for <mip6@ietf.org>; Mon,  3 Oct 2005 17:03:08 +0200 (CEST)
Received: from shiraz.local.levkowetz.com ([192.168.3.14]
	helo=81-224-201-50-no45.tbcn.telia.com)
	by shiraz.levkowetz.com with esmtp (Exim 4.52) id 1EMRqN-0002NQ-EK
	for mip6@ietf.org; Mon, 03 Oct 2005 17:03:08 +0200
Content-Type: text/plain; charset=utf-8
To: mip6@ietf.org
From: Gerardo <tracker-mip6@mip4.org>
Date: Mon, 03 Oct 2005 15:03:07 +0000
MIME-Version: 1.0
Message-Id: <1128351787.4.0.678037919957.issue53@mip4.org>
X-Roundup-Name: Mip6 issue tracker
X-Roundup-Loop: hello
Content-Transfer-Encoding: quoted-printable
X-Helo-Check-Failed: Verification failed for HELO
	81-224-201-50-no45.tbcn.telia.com
X-SA-Exim-Connect-IP: 192.168.3.14
X-SA-Exim-Mail-From: roundup-admin@mip4.org
X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on 
	shiraz.levkowetz.com
X-Spam-Status: No, score=-103.8 required=2.5 tests=ALL_TRUSTED,AWL,BAYES_00,
	USER_IN_WHITELIST,X_HELO_CHECK_FAILED autolearn=ham version=3.0.4
X-SA-Exim-Version: 4.2 (built Thu, 03 Mar 2005 10:44:12 +0100)
X-SA-Exim-Scanned: Yes (on shiraz.levkowetz.com)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Content-Transfer-Encoding: quoted-printable
Subject: [Mip6] [issue53] HA discovery by location (from Jari's review)
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Mip6 issue tracker <tracker-mip6@mip4.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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org


New submission from Gerardo <gerardo.giaretta@tilab.com>:

>From the draft:=20
> Mobile
> Node to discover a Home Agent placed in a particular location
> (e.g.
> on the visited link). In order to achieve this, the Mobile
> Node must
> be able to construct a DNS request such that the DNS server
> will be
> able to reply with a Home Agent from the requested location.
> This can
> be accomplished by using a specific  naming convention for the
> FQDNs of the Home Agents.

Jari wrote:
"
Possible, but the description is mostly handwaving and would probably
benefit from a more generic solution in any case. Suggest
removing this.
"

James wrote:
"
I'm not in favor of this. The operator may want to use various naming=20
conventions for home agents, based on service type or level of provided=20
service. I don't think signaling out location specifically for a naming=20
convention is the right way to go.

I do think we should define a cannonical name for HAs, like "ftp" is=20
for FTP servers.
"

Vijay:
"
I agree with Jim
"

----------
category: Editorial
draft: draft-ietf-mip6-bootstrapping-split
messages: 174
nosy: gerardo
priority: Should fix
status: Pending
title: HA discovery by location (from Jari's review)

_________________________________________________
Mip6 issue tracker <tracker-mip6@mip4.org>
<http://www.mip4.org/issues/tracker/mip6/issue53>
_________________________________________________

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



From mip6-bounces@ietf.org Mon Oct 03 11:12:11 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EMRz9-0003OK-MX; Mon, 03 Oct 2005 11:12:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EMRz7-0003M3-KW
	for mip6@megatron.ietf.org; Mon, 03 Oct 2005 11:12:09 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA11438
	for <mip6@ietf.org>; Mon, 3 Oct 2005 11:12:07 -0400 (EDT)
Received: from av9-1-sn2.hy.skanova.net ([81.228.8.179])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EMS7b-0002TC-DC
	for mip6@ietf.org; Mon, 03 Oct 2005 11:20:56 -0400
Received: by av9-1-sn2.hy.skanova.net (Postfix, from userid 502)
	id 5C62337FFD; Mon,  3 Oct 2005 16:49:41 +0200 (CEST)
Received: from smtp4-1-sn2.hy.skanova.net (smtp4-1-sn2.hy.skanova.net
	[81.228.8.92])
	by av9-1-sn2.hy.skanova.net (Postfix) with ESMTP id 481D137FF1
	for <mip6@ietf.org>; Mon,  3 Oct 2005 16:49:41 +0200 (CEST)
Received: from shiraz.levkowetz.com (81-224-201-50-no45.tbcn.telia.com
	[81.224.201.50])
	by smtp4-1-sn2.hy.skanova.net (Postfix) with ESMTP id 31A3737E49
	for <mip6@ietf.org>; Mon,  3 Oct 2005 16:49:41 +0200 (CEST)
Received: from shiraz.local.levkowetz.com ([192.168.3.14]
	helo=81-224-201-50-no45.tbcn.telia.com)
	by shiraz.levkowetz.com with esmtp (Exim 4.52) id 1EMRdI-000218-0f
	for mip6@ietf.org; Mon, 03 Oct 2005 16:49:40 +0200
Content-Type: text/plain; charset=utf-8
To: mip6@ietf.org
From: Gerardo <tracker-mip6@mip4.org>
Date: Mon, 03 Oct 2005 14:49:34 +0000
MIME-Version: 1.0
Message-Id: <1128350974.83.0.915629086367.issue49@mip4.org>
X-Roundup-Name: Mip6 issue tracker
X-Roundup-Loop: hello
Content-Transfer-Encoding: quoted-printable
X-Helo-Check-Failed: Verification failed for HELO
	81-224-201-50-no45.tbcn.telia.com
X-SA-Exim-Connect-IP: 192.168.3.14
X-SA-Exim-Mail-From: roundup-admin@mip4.org
X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on 
	shiraz.levkowetz.com
X-Spam-Status: No, score=-103.8 required=2.5 tests=ALL_TRUSTED,AWL,BAYES_00,
	USER_IN_WHITELIST,X_HELO_CHECK_FAILED autolearn=ham version=3.0.4
X-SA-Exim-Version: 4.2 (built Thu, 03 Mar 2005 10:44:12 +0100)
X-SA-Exim-Scanned: Yes (on shiraz.levkowetz.com)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Content-Transfer-Encoding: quoted-printable
Subject: [Mip6] [issue49] HoA validation and DNS update
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Mip6 issue tracker <tracker-mip6@mip4.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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org


New submission from Gerardo <gerardo.giaretta@tilab.com>:

Raised by Francis:
"
I have two concerns:
 the configuration service in IKEv2 was copied from DHCP,
 in fact, you should consider it as a lightweight DHCP service.
 - so in 5.3.2 you cannot use it to validate a HoA configured by
   the MN. BTW in the past I tried to add a validation/registration
   service for stateless autoconfed addresses in DHCPv6, it was
   rejected by the DHC WG.
 - at the contrary this service is the right one for DNS update
   (in the reverse tree: as usual the MN should update the AAAA RR
    because it has the trust over its FQDN, and the guy who allocates
    the address should update the PTR because it has the trust over
    this part of the reverse tree. PS: confirmed as the session).
"

James wrote:
"
What exactly was the issue you had with having the DNS update done via the
BU?
"

Francis wrote:
> =3D> this is not the job of the MIPv6 code and is clearly the job of the
> tool which allocates the HoA: IKE CFG_REQUEST stuff. Here I apply
> my idea that IKE CFG_REQUEST is DHCP-like and DNS update is a classical
> service offered by DHCP. BTW the DNS update must be secured i.e. the
> tools performing it be trusted, so it is not simple...

Vijay wrote:
"
there are two issues. first, this would mean he MN is not in control of=20
the DNS update. the HA does it everytime it replies with a HoA in a=20
CFG_REPLY message. not sure thats a good idea. in some cases,=20
the MN may not want the HoA published in the DNS. it would be=20
good to get an indication from the MN before doing the DNS update.
second, we want to support HoA auto-configuration (RFC 2462, RFC=20
3041, CGA). when the MN autoconfigures a HoA, we dont use=20
CFG_REPLY. the HA doing the update when it sends CFG_REPLY
message supports only assigned HoA.
"

James wrote:
"
I asked Ralph whether the IKEv2 folks had consulted the DHCP WG on the
config and he said no. Perhaps there was some discussion amongst themselves
on this, but he hadn't heard of it. So it is not clear to me that the IKEv2
folks used any specific model of address configuration.
"

----------
category: Technical
draft: draft-ietf-mip6-bootstrapping-split
messages: 170
nosy: gerardo
priority: Should fix
status: Rejected
title: HoA validation and DNS update

_________________________________________________
Mip6 issue tracker <tracker-mip6@mip4.org>
<http://www.mip4.org/issues/tracker/mip6/issue49>
_________________________________________________

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



From mip6-bounces@ietf.org Mon Oct 03 11:25:18 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EMSBq-0006A2-Cr; Mon, 03 Oct 2005 11:25:18 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EMSBp-00069x-8H
	for mip6@megatron.ietf.org; Mon, 03 Oct 2005 11:25:17 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12292
	for <mip6@ietf.org>; Mon, 3 Oct 2005 11:25:15 -0400 (EDT)
Received: from av10-1-sn2.hy.skanova.net ([81.228.8.181])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EMSKK-0002r2-6h
	for mip6@ietf.org; Mon, 03 Oct 2005 11:34:04 -0400
Received: by av10-1-sn2.hy.skanova.net (Postfix, from userid 502)
	id E91C137E8C; Mon,  3 Oct 2005 16:26:17 +0200 (CEST)
Received: from smtp4-1-sn2.hy.skanova.net (smtp4-1-sn2.hy.skanova.net
	[81.228.8.92])
	by av10-1-sn2.hy.skanova.net (Postfix) with ESMTP id B229737E82
	for <mip6@ietf.org>; Mon,  3 Oct 2005 16:26:17 +0200 (CEST)
Received: from shiraz.levkowetz.com (81-224-201-50-no45.tbcn.telia.com
	[81.224.201.50])
	by smtp4-1-sn2.hy.skanova.net (Postfix) with ESMTP id 998C237E4C
	for <mip6@ietf.org>; Mon,  3 Oct 2005 16:26:17 +0200 (CEST)
Received: from shiraz.local.levkowetz.com ([192.168.3.14]
	helo=81-224-201-50-no45.tbcn.telia.com)
	by shiraz.levkowetz.com with esmtp (Exim 4.52) id 1EMRGi-0001YU-C9
	for mip6@ietf.org; Mon, 03 Oct 2005 16:26:17 +0200
Content-Type: text/plain; charset=utf-8
To: mip6@ietf.org
From: Gerardo <tracker-mip6@mip4.org>
Date: Mon, 03 Oct 2005 14:26:16 +0000
MIME-Version: 1.0
Message-Id: <1128349576.33.0.755977165103.issue48@mip4.org>
X-Roundup-Name: Mip6 issue tracker
X-Roundup-Loop: hello
Content-Transfer-Encoding: quoted-printable
X-Helo-Check-Failed: Verification failed for HELO
	81-224-201-50-no45.tbcn.telia.com
X-SA-Exim-Connect-IP: 192.168.3.14
X-SA-Exim-Mail-From: roundup-admin@mip4.org
X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on 
	shiraz.levkowetz.com
X-Spam-Status: No, score=-103.8 required=2.5 tests=ALL_TRUSTED,AWL,BAYES_00,
	MIME_QP_LONG_LINE, USER_IN_WHITELIST, X_HELO_CHECK_FAILED autolearn=ham 
	version=3.0.4
X-SA-Exim-Version: 4.2 (built Thu, 03 Mar 2005 10:44:12 +0100)
X-SA-Exim-Scanned: Yes (on shiraz.levkowetz.com)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Content-Transfer-Encoding: quoted-printable
Subject: [Mip6] [issue48] HA Address discovery: load balancing
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Mip6 issue tracker <tracker-mip6@mip4.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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org


New submission from Gerardo <gerardo.giaretta@tilab.com>:

Li Qin mentioned that using DNS discovery you cannot perform load balancing=20
assigning different HA to different MNs.

Li Qin wrote:
"
I guess that multiple home agents related issues, such as dynamic home
agent assignment, have not been considered in this draft.
"

Vijay wrote:
"
once the mobile node knows the home prefix, it can still do DHAAD if it wan=
ts=20
to.
"

James wrote:
"
The home DNS server can contain multiple HA addresses in the SRV record.
"

Li Qin wrote:
"
In my opinion I think its more like a HA discovery than HA assignment.
If multiple HAs are deployed in home network, is it possible to assign a
HA according to the user's profile, or according to current load of the
HAs in this solution?
"

James wrote:
"
The SRV record contains information that the operator can use to establish a
preference ordering on the servers for clients. That said, I don't believe
it is intended to provide fast, real time information about preferences, say
on the order of seconds., but more over longer periods, since dynamic DNS
updates require some time to propagate, and it would also not be such a good
idea to burden the DNS server with having to handle such frequent updates.
"

Hui wrote:
"
Do you mean that DNS is not suitable for dynamical home agent assignment in=20
this bootstrap solution?
"

James wrote:
"
What I mean is that the operater can use the SRV record preference field for
long term load balancing, and connection refusal for short term load
balancing, due to flash crowds and such.=20
"

Gerardo wrote:
"
The issue is that using DNS solution an operator cannot do a per node load=20
balancing, that is it cannot be sure to allocate a specific HA to a specifi=
c=20
MN. I think this is the main case Li Qin and others were referring to.=20
Instead, this is possible in integrated scenario using DHCP solution.

So, what I suggest is that we state that we do not support a per MN load=20
balancing and this will be supported in the integrated scenario. Then we ca=
n=20
mention that using the SRV RR priorities an operator may perform a load=20
balancing changing the DNS entries, but this is not addressed in the draft=20
since short lifetimes for DNS entries have drawbacks.
"

----------
category: Editorial
draft: draft-ietf-mip6-bootstrapping-split
messages: 169
nosy: gerardo
priority: Must fix
status: Need clarifying text
title: HA Address discovery: load balancing

_________________________________________________
Mip6 issue tracker <tracker-mip6@mip4.org>
<http://www.mip4.org/issues/tracker/mip6/issue48>
_________________________________________________

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



From mip6-bounces@ietf.org Mon Oct 03 23:04:53 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EMd6q-00039A-Me; Mon, 03 Oct 2005 23:04:52 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EMd6p-00038n-E8
	for mip6@megatron.ietf.org; Mon, 03 Oct 2005 23:04:51 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA07110
	for <mip6@ietf.org>; Mon, 3 Oct 2005 23:04:48 -0400 (EDT)
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EMdFP-0002Eg-DN
	for mip6@ietf.org; Mon, 03 Oct 2005 23:13:44 -0400
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id j942WKv14123;
	Mon, 3 Oct 2005 19:32:20 -0700
X-mProtect: <200510040232> Nokia Silicon Valley Messaging Protection
Received: from mvdhcp14172.americas.nokia.com (172.18.141.72,
	claiming to be "[127.0.0.1]")
	by darkstar.iprg.nokia.com smtpdHgqMBL; Mon, 03 Oct 2005 18:15:04 PDT
Message-ID: <4341DEFF.5070805@iprg.nokia.com>
Date: Mon, 03 Oct 2005 18:46:39 -0700
From: Vijay Devarapalli <vijayd@iprg.nokia.com>
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: James Kempf <Kempf@docomolabs-usa.com>
Subject: Re: [Mip6] review of draft-ietf-mip6-bootstrapping-split-00.txt
References: <4D2F935F08D41A4C8866693F4F0D7C4F4D5C6E@lan-ex-01.panasonic.de>
	<068401c5c5ed$c6499800$196115ac@dcml.docomolabsusa.com>
	<f1f4dcdc0509301658j18665804l61df84f6eab66ba7@mail.gmail.com>
	<082e01c5c702$c810bf90$196115ac@dcml.docomolabsusa.com>
In-Reply-To: <082e01c5c702$c810bf90$196115ac@dcml.docomolabsusa.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2bf730a014b318fd3efd65b39b48818c
Content-Transfer-Encoding: 7bit
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

James Kempf wrote:
> I still don't see what the problem is with the text I provided.
> 
> Suppose we try an example. 

okay, lets use the example.

Let's suppose Alice's MSP is Bob's Mobile IP
> Service (domain name: bobsmova.com). Suppose Bob owns an access network 
> that covers Palo Alto and Mountain View in California (actually, Bob 
> might not own any access network at all, but for the moment, let's 
> suppose he does). Now, suppose Alice is moving north on El Camino Real 
> in Palo Alto and is using Bob's HA (ha1.bobsmova.com). She's got an HoA 
> in the subnet routed by ha1.bobsmova.com, which just so happens to cover 
> that part of El Camino Real between San Antonio and the intersection of 
> Charleston and Arastadero. Suppose Alice is paranoid about people 
> tracking her movements so she never does route optimization so people 
> never see her care of address, but she does put her HoA into the DNS so 
> that people can SIP call her, at alice.bobsmova.com (Bob also acts as 
> her MSA). Since ha1.bobsmova.com is local to Palo Alto, Alice has 
> obtained a local HA and HoA.
> 
> Now, let's suppose Alice goes to Tucson in order to attend a conference. 
> Alice is driving north on Speedway. She uses Bob's Mobile IP service 
> there too, and she's got a HoA in Bob's network. Maybe the HA is even 
> ha1.bobsmova.com. She puts that HoA into Bob's DNS at 
> alice.bobsmova.com, and she never uses route optimization.

Kilian was raising a different issue. the issues is valid when
the access service provider also provides a local HA. lets say
Alice goes to Tucson. she wants to download from a server in
Tucson. ha1.bobsmova.com is too far. the MN and the CN are in
Tucson. she configures a local HA and a local HoA. now if
Alice has the DNS entry alice.bobsmova.com updated with the
local HoA, the CNs know Alice is in Tucson.

Vijay

> 
> How can anybody deduce any geographical information about Alice? If 
> Alice never exposes her care of address and always uses her home 
> address, how can they tell if she's between San Antonio and the 
> Charleston/Arastadero intersection in Palo Alto (covered by the subnet 
> that her home address is in), or if she's between the Page Mill 
> Road/Oregon Expressway intersection and the Charleston/Arastadero 
> intersection in Palo Alto (which is in Bob's network but is not covered 
> by the subnet that Alice 's home address is in), or, for that matter, 
> whether she is in Palto Alto at all and not in Tucson (which is not 
> covered by Bob's access network)?
> 
>            jakb
> 
> ----- Original Message ----- From: "Vijay Devarapallli" <dvijay@gmail.com>
> To: "James Kempf" <Kempf@docomolabs-usa.com>
> Cc: "Gerardo Giaretta" <Gerardo.Giaretta@tilab.com>; "Vijay Devarapalli" 
> <vijayd@iprg.nokia.com>; "Kilian Weniger" 
> <Kilian.Weniger@eu.panasonic.com>; <mip6@ietf.org>
> Sent: Friday, September 30, 2005 4:58 PM
> Subject: Re: [Mip6] review of draft-ietf-mip6-bootstrapping-split-00.txt
> 
> 
> there is some confusion.
> 
> Jim, Kilian's main concern is when the MN configures a HA
> from the visited link (using location specific HA FQDN).
> the issue is if the MN configures a HA and HoA from the
> visited link and then has its DNS entry updated, then the
> CN knows where the MN is currently located. the MN can
> continue doing DNS updates for home address configured from
> the home link. causes no harm. but when it does a DNS update
> for the home address configured from a HA on a visited link,
> it immediately reveals its location to the CN. maybe we
> could add the following to the security considerations section
> 
>  A mobile node could hide its location from its correspondent
>  node by reverse tunneling all traffic through the home agent.
>  The same mobile node could roam and configure a home agent
>  and home address from a visited link. If the home agent
>  updates the DNS entry of the mobile node with its new home
>  address, then this may reveal the current location of the
>  mobile node to the correspondent node. In such a if the mobile
>  node does not want the correspondent node to know its current
>  location, then it should not request the home agent to update
>  the DNS entry.
> 
> comments?
> 
> Vijay
> 
> On 9/30/05, James Kempf <Kempf@docomolabs-usa.com> wrote:
> 
>> Comments.
>>
>> "Note that local HA assignment combined with DNS updates may violate the
>> location privacy of MN. A known solution to location privacy is to hide
>> the CoA from CN by using reverse tunneling to the HA
>> [draft-koodli-mip6-location-privacy-solutions-00.txt]. However, reverse
>> tunneling may significantly decrease routing efficiency, depending on
>> how far the HA is off the direct path between MN and CN.The
>> bootstrapping solution supports local HA assignment to improve routing
>> efficiency, but since the HoA obtained from a local HA assignment
>> topologically belongs to the visited network, it contains location
>> information. Consequently, it must carefully be considered to whom this
>> HoA is revealed and whether DNS updates are requested for this HoA. The
>> latter can even enable others to track MN's movement, if the MN uses an
>> eager strategy for local HA assignment. On the other hand, if the HoA is
>> hidden from other nodes, they cannot reach the MN at this HoA and, thus,
>> cannot benefit from the local HA assignment in terms of routing
>> efficiency. "
>>
>>  jak>> I have a couple problems with this:
>>
>> 1)  Reverse tunneling is the default in IPv6, that is to say, if an HA is
>> used, reverse tunneling must be used, unless the traffic is route 
>> optimized.
>> So it is more accurate to say that in order to protect privacy, the MN 
>> must
>> not route optimize traffic.
>>
>> 2) The solution in draft-ietf-mip6-bootstrapping-split does not specify
>> anything for local home agent assignment. There is nothing in the 
>> protocol
>> to actually move the HA from the MSP's network to the serving network. 
>> The
>> MN gets to choose an HA from whatever HAs the MSP's DNS SRV RR 
>> advertises.
>> If that happens to be in the serving network, then correspondents will be
>> able to obtain some information about where the MN is, but it could 
>> equally
>> well be on the other side of the globe.
>>
>> Note that the integrated scenerio (which the DT is currently working on)
>> will have a mechanism whereby a local home agent can be assigned, 
>> since the
>> MN gets the HA address from the local DHCP server.
>>
>> 3) Since the HoA doesn't change once the MN has established it, I fail to
>> see how an attacker can track the MN's location. Once the MN has 
>> established
>> the HoA, it will appear to be at a fixed topological location in the 
>> MSP's
>> network regardless of where the care of address is, if route 
>> optimization is
>> not used.
>>
>> So I think the risk is considerably less that is portrayed by the above
>> text. I think the following text would be more accurate:
>>
>>     Updating the mobile node's FQDN in the DNS
>>     with the mobile node's home address has the
>>     potential to expose some information about
>>     the mobile node's location to correspondents
>>     if the home agent selected by the mobile
>>     node is in the serving network access provider's
>>     network (that is, the serving network access
>>     provider is also acting as the mobility service
>>     provider). The risk here is not as deep as
>>     with route optimization, since the mobile node
>>     will effectively appear to be at a fixed topological
>>     location in the mobility service provider's network
>>     regardless of where the care of address is. To
>>     mitigate the risk, the mobile node should
>>     either not request DNS update or be careful
>>     to select a home agent that is not within the
>>     serving network access provider's network.
>>
>>
>>             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 Mon Oct 03 23:05:07 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EMd75-0003Fi-1p; Mon, 03 Oct 2005 23:05:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EMd72-0003FH-Lb
	for mip6@megatron.ietf.org; Mon, 03 Oct 2005 23:05:04 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA07135
	for <mip6@ietf.org>; Mon, 3 Oct 2005 23:05:01 -0400 (EDT)
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EMdFc-0002FN-Gi
	for mip6@ietf.org; Mon, 03 Oct 2005 23:13:57 -0400
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id j942WXj16072;
	Mon, 3 Oct 2005 19:32:33 -0700
X-mProtect: <200510040232> Nokia Silicon Valley Messaging Protection
Received: from mvdhcp14172.americas.nokia.com (172.18.141.72,
	claiming to be "[127.0.0.1]")
	by darkstar.iprg.nokia.com smtpdGWGe5V; Mon, 03 Oct 2005 18:17:57 PDT
Message-ID: <4341DFBC.8040207@iprg.nokia.com>
Date: Mon, 03 Oct 2005 18:49:48 -0700
From: Vijay Devarapalli <vijayd@iprg.nokia.com>
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Gerardo Giaretta <Gerardo.Giaretta@TILAB.COM>
Subject: Re: [Mip6] review of draft-ietf-mip6-bootstrapping-split-00.txt
References: <DA62A6E0CDD1B34A84557FF1AC850C57016E9B44@EXC01B.cselt.it>
In-Reply-To: <DA62A6E0CDD1B34A84557FF1AC850C57016E9B44@EXC01B.cselt.it>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cbb41f2dbf0f142369614756642005e3
Content-Transfer-Encoding: 7bit
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Gerardo Giaretta wrote:
>>I still don't see what the problem is with the text I provided.
>>
>>Suppose we try an example. Let's suppose Alice's MSP is Bob's 
>>Mobile IP 
>>Service (domain name: bobsmova.com). Suppose Bob owns an 
>>access network that 
>>covers Palo Alto and Mountain View in California (actually, 
>>Bob might not 
>>own any access network at all, but for the moment, let's 
>>suppose he does). 
>>Now, suppose Alice is moving north on El Camino Real in Palo 
>>Alto and is 
>>using Bob's HA (ha1.bobsmova.com). She's got an HoA in the 
>>subnet routed by 
>>ha1.bobsmova.com, which just so happens to cover that part of 
>>El Camino Real 
>>between San Antonio and the intersection of Charleston and 
>>Arastadero. 
>>Suppose Alice is paranoid about people tracking her movements 
>>so she never 
>>does route optimization so people never see her care of 
>>address, but she 
>>does put her HoA into the DNS so that people can SIP call her, at 
>>alice.bobsmova.com (Bob also acts as her MSA). Since 
>>ha1.bobsmova.com is 
>>local to Palo Alto, Alice has obtained a local HA and HoA.
>>
>>Now, let's suppose Alice goes to Tucson in order to attend a 
>>conference. 
>>Alice is driving north on Speedway. She uses Bob's Mobile IP 
>>service there 
>>too, and she's got a HoA in Bob's network. Maybe the HA is even 
>>ha1.bobsmova.com. She puts that HoA into Bob's DNS at 
>>alice.bobsmova.com, 
>>and she never uses route optimization.
>>
>>How can anybody deduce any geographical information about 
>>Alice? If Alice 
>>never exposes her care of address and always uses her home 
>>address, how can 
>>they tell if she's between San Antonio and the Charleston/Arastadero 
>>intersection in Palo Alto (covered by the subnet that her 
>>home address is 
>>in), or if she's between the Page Mill Road/Oregon Expressway 
>>intersection 
>>and the Charleston/Arastadero intersection in Palo Alto 
>>(which is in Bob's 
>>network but is not covered by the subnet that Alice 's home 
>>address is in), 
>>or, for that matter, whether she is in Palto Alto at all and 
>>not in Tucson 
>>(which is not covered by Bob's access network)?
>>
> 
> 
> Exactly. From the HoA, CNs can only guess the location where the MN MAY*
> have performed bootstrapping procedure. This may be very different from
> the current location of the MN.
> 
> * moreover, how the CNs know for sure that the MN bootstrapped with a
> local HA if bidirectional tunneling is always used? If this the case
> (i.e. the CN does not know if the MN has been alloctaed a local HA or
> remote HA), is this a real threat to the location privacy of the MN?

well, the CN earlier used to see a home address from a home agent
in Palo Alto and now it sees a home address from a home agent in
Tuscon.

Vijay

> 
> --Gerardo 
> 
> 
> 
>>            jakb
>>
>>----- Original Message ----- 
>>From: "Vijay Devarapallli" <dvijay@gmail.com>
>>To: "James Kempf" <Kempf@docomolabs-usa.com>
>>Cc: "Gerardo Giaretta" <Gerardo.Giaretta@tilab.com>; "Vijay 
>>Devarapalli" 
>><vijayd@iprg.nokia.com>; "Kilian Weniger" 
>><Kilian.Weniger@eu.panasonic.com>; 
>><mip6@ietf.org>
>>Sent: Friday, September 30, 2005 4:58 PM
>>Subject: Re: [Mip6] review of 
>>draft-ietf-mip6-bootstrapping-split-00.txt
>>
>>
>>there is some confusion.
>>
>>Jim, Kilian's main concern is when the MN configures a HA
>>from the visited link (using location specific HA FQDN).
>>the issue is if the MN configures a HA and HoA from the
>>visited link and then has its DNS entry updated, then the
>>CN knows where the MN is currently located. the MN can
>>continue doing DNS updates for home address configured from
>>the home link. causes no harm. but when it does a DNS update
>>for the home address configured from a HA on a visited link,
>>it immediately reveals its location to the CN. maybe we
>>could add the following to the security considerations section
>>
>>  A mobile node could hide its location from its correspondent
>>  node by reverse tunneling all traffic through the home agent.
>>  The same mobile node could roam and configure a home agent
>>  and home address from a visited link. If the home agent
>>  updates the DNS entry of the mobile node with its new home
>>  address, then this may reveal the current location of the
>>  mobile node to the correspondent node. In such a if the mobile
>>  node does not want the correspondent node to know its current
>>  location, then it should not request the home agent to update
>>  the DNS entry.
>>
>>comments?
>>
>>Vijay
>>
>>On 9/30/05, James Kempf <Kempf@docomolabs-usa.com> wrote:
>>
>>>Comments.
>>>
>>>"Note that local HA assignment combined with DNS updates 
>>
>>may violate the
>>
>>>location privacy of MN. A known solution to location 
>>
>>privacy is to hide
>>
>>>the CoA from CN by using reverse tunneling to the HA
>>>[draft-koodli-mip6-location-privacy-solutions-00.txt]. 
>>
>>However, reverse
>>
>>>tunneling may significantly decrease routing efficiency, 
>>
>>depending on
>>
>>>how far the HA is off the direct path between MN and CN.The
>>>bootstrapping solution supports local HA assignment to 
>>
>>improve routing
>>
>>>efficiency, but since the HoA obtained from a local HA assignment
>>>topologically belongs to the visited network, it contains location
>>>information. Consequently, it must carefully be considered 
>>
>>to whom this
>>
>>>HoA is revealed and whether DNS updates are requested for 
>>
>>this HoA. The
>>
>>>latter can even enable others to track MN's movement, if 
>>
>>the MN uses an
>>
>>>eager strategy for local HA assignment. On the other hand, 
>>
>>if the HoA is
>>
>>>hidden from other nodes, they cannot reach the MN at this 
>>
>>HoA and, thus,
>>
>>>cannot benefit from the local HA assignment in terms of routing
>>>efficiency. "
>>>
>>> jak>> I have a couple problems with this:
>>>
>>>1)  Reverse tunneling is the default in IPv6, that is to 
>>
>>say, if an HA is
>>
>>>used, reverse tunneling must be used, unless the traffic is route 
>>>optimized.
>>>So it is more accurate to say that in order to protect 
>>
>>privacy, the MN 
>>
>>>must
>>>not route optimize traffic.
>>>
>>>2) The solution in draft-ietf-mip6-bootstrapping-split does 
>>
>>not specify
>>
>>>anything for local home agent assignment. There is nothing 
>>
>>in the protocol
>>
>>>to actually move the HA from the MSP's network to the 
>>
>>serving network. The
>>
>>>MN gets to choose an HA from whatever HAs the MSP's DNS SRV 
>>
>>RR advertises.
>>
>>>If that happens to be in the serving network, then 
>>
>>correspondents will be
>>
>>>able to obtain some information about where the MN is, but it could 
>>>equally
>>>well be on the other side of the globe.
>>>
>>>Note that the integrated scenerio (which the DT is 
>>
>>currently working on)
>>
>>>will have a mechanism whereby a local home agent can be 
>>
>>assigned, since 
>>
>>>the
>>>MN gets the HA address from the local DHCP server.
>>>
>>>3) Since the HoA doesn't change once the MN has established 
>>
>>it, I fail to
>>
>>>see how an attacker can track the MN's location. Once the MN has 
>>>established
>>>the HoA, it will appear to be at a fixed topological 
>>
>>location in the MSP's
>>
>>>network regardless of where the care of address is, if 
>>
>>route optimization 
>>
>>>is
>>>not used.
>>>
>>>So I think the risk is considerably less that is portrayed 
>>
>>by the above
>>
>>>text. I think the following text would be more accurate:
>>>
>>>    Updating the mobile node's FQDN in the DNS
>>>    with the mobile node's home address has the
>>>    potential to expose some information about
>>>    the mobile node's location to correspondents
>>>    if the home agent selected by the mobile
>>>    node is in the serving network access provider's
>>>    network (that is, the serving network access
>>>    provider is also acting as the mobility service
>>>    provider). The risk here is not as deep as
>>>    with route optimization, since the mobile node
>>>    will effectively appear to be at a fixed topological
>>>    location in the mobility service provider's network
>>>    regardless of where the care of address is. To
>>>    mitigate the risk, the mobile node should
>>>    either not request DNS update or be careful
>>>    to select a home agent that is not within the
>>>    serving network access provider's network.
>>>
>>>
>>>            jak
>>>
>>>
>>>
>>>
>>>
>>>
>>>_______________________________________________
>>>Mip6 mailing list
>>>Mip6@ietf.org
>>>https://www1.ietf.org/mailman/listinfo/mip6
>>>
>>
>>
>>
> 
> 
> Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia S.p.A.
> 
> ====================================================================
> CONFIDENTIALITY NOTICE
> This message and its attachments are addressed solely to the persons
> above and may contain confidential information. If you have received
> the message in error, be informed that any use of the content hereof
> is prohibited. Please return it immediately to the sender and delete
> the message. Should you have any questions, please send an e_mail to 
> MailAdmin@tilab.com. Thank you
> ====================================================================



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



From mip6-bounces@ietf.org Mon Oct 03 23:05:17 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EMd7F-0003JJ-54; Mon, 03 Oct 2005 23:05:17 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EMd7D-0003JE-BT
	for mip6@megatron.ietf.org; Mon, 03 Oct 2005 23:05:15 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA07146
	for <mip6@ietf.org>; Mon, 3 Oct 2005 23:05:12 -0400 (EDT)
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EMdFm-0002Fo-ST
	for mip6@ietf.org; Mon, 03 Oct 2005 23:14:08 -0400
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id j942WoL19575;
	Mon, 3 Oct 2005 19:32:50 -0700
X-mProtect: <200510040232> Nokia Silicon Valley Messaging Protection
Received: from mvdhcp14172.americas.nokia.com (172.18.141.72,
	claiming to be "[127.0.0.1]")
	by darkstar.iprg.nokia.com smtpdw8lCum; Mon, 03 Oct 2005 18:21:47 PDT
Message-ID: <4341E0A0.9070205@iprg.nokia.com>
Date: Mon, 03 Oct 2005 18:53:36 -0700
From: Vijay Devarapalli <vijayd@iprg.nokia.com>
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Gerardo Giaretta <Gerardo.Giaretta@TILAB.COM>
Subject: Re: [Mip6] review of draft-ietf-mip6-bootstrapping-split-00.txt
References: <DA62A6E0CDD1B34A84557FF1AC850C57016E9B43@EXC01B.cselt.it>
In-Reply-To: <DA62A6E0CDD1B34A84557FF1AC850C57016E9B43@EXC01B.cselt.it>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Content-Transfer-Encoding: 7bit
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Gerardo Giaretta wrote:
> Vijay, 
> 
> few comments below...
> 
> 
>>there is some confusion.
>>
>>Jim, Kilian's main concern is when the MN configures a HA
>>from the visited link (using location specific HA FQDN).
>>the issue is if the MN configures a HA and HoA from the
>>visited link and then has its DNS entry updated, then the
>>CN knows where the MN is currently located. the MN can
>>continue doing DNS updates for home address configured from
>>the home link. causes no harm. but when it does a DNS update
>>for the home address configured from a HA on a visited link,
>>it immediately reveals its location to the CN. maybe we
>>could add the following to the security considerations section
>>
>>  A mobile node could hide its location from its correspondent
>>  node by reverse tunneling all traffic through the home agent.
>>  The same mobile node could roam and configure a home agent
>>  and home address from a visited link. If the home agent
>>  updates the DNS entry of the mobile node with its new home
>>  address, then this may reveal the current location of the
>>  mobile node to the correspondent node. In such a if the mobile
>>  node does not want the correspondent node to know its current
>>  location, then it should not request the home agent to update
>>  the DNS entry.
>>
>>comments?
>>
> 
> 
> I would mitigate a little bit this possible threat to the location
> privacy of the MN.
> 
> First of all, we don't specify a way to allocate a local HA in
> draft-ietf-mip6-bootstrapping-split. This is correct since in split
> scenario there is no assumption on ASP. Therefore, this text may be more
> appropriate to the integrated scenario.

but we do provide a mechanism using DNS. FQDNs could be configured
such that the MN can lookup a HA based on its location.

> Besides that, based on the HoA, a CN can only guess the location from
> which the MN performed the bootstrapping procedure. Subsequent movements
> are not visible to CNs if bidirectional tunneling is used. This may or
> may not be an issue depending the mobility pattern of the MN, too. I'd
> suggest to include a sentence about this in the draft, if we want to
> address this issue.

the issue is about using different home addresses for the same FQDN.
the home addresses could potentially reveal where the MN is located.

Vijay


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



From mip6-bounces@ietf.org Tue Oct 04 09:42:23 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EMn3n-0001Uv-Jk; Tue, 04 Oct 2005 09:42:23 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EMn3j-0001Un-R3
	for mip6@megatron.ietf.org; Tue, 04 Oct 2005 09:42:21 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19528
	for <mip6@ietf.org>; Tue, 4 Oct 2005 09:42:17 -0400 (EDT)
Received: from cluster-d.mailcontrol.com ([217.69.20.190]
	helo=rly24d.srv.mailcontrol.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EMnCP-0001HU-Vh
	for mip6@ietf.org; Tue, 04 Oct 2005 09:51:18 -0400
Received: from hhe500-02.hbg.de.pan.eu (gate.eu.panasonic.com [194.173.20.12])
	by rly24d.srv.mailcontrol.com (MailControl) with SMTP id
	j94Dfw5d008488; Tue, 4 Oct 2005 14:41:58 +0100
Received: from eundadmi01.pan.eu(10.100.96.64) by hhe500-02.hbg.de.pan.eu via
	smtp id 211c_2f5998f0_34dd_11da_9ec2_0030482aac25;
	Tue, 04 Oct 2005 15:45:53 +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 2005100415415458-199973 ;
	Tue, 4 Oct 2005 15:41:54 +0200 
Received: from localhost ([127.0.0.1]) by VPN-MRelay-01.PRDCG.Panasonic.de;
	Tue, 4 Oct 2005 15:43:49 +0200
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Subject: RE: [Mip6] review of draft-ietf-mip6-bootstrapping-split-00.txt
Thread-Topic: [Mip6] review of draft-ietf-mip6-bootstrapping-split-00.txt
Thread-Index: AcXF7cu9TufTtpm/TXOfrqWVZ+qRVwCz+1cg
To: "James Kempf" <Kempf@docomolabs-usa.com>,
	"Gerardo Giaretta" <Gerardo.Giaretta@TILAB.COM>,
	"Vijay Devarapalli" <vijayd@iprg.nokia.com>
Message-ID: <4D2F935F08D41A4C8866693F4F0D7C4F4D5DE0@lan-ex-01.panasonic.de>
Date: Tue, 4 Oct 2005 15:41:42 +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-05-40-00 (www.mailcontrol.com) on 10.68.0.134
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f49c97ce49302a02285a2d36a99eef8c
Content-Transfer-Encoding: quoted-printable
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org


Sorry for the late reply.=20
Vijay already provided some answers that I had in mind. Please see some
further comments below.

> 1)  Reverse tunneling is the default in IPv6, that is to say,=20
> if an HA is=20
> used, reverse tunneling must be used, unless the traffic is=20
> route optimized.=20
> So it is more accurate to say that in order to protect=20
> privacy, the MN must=20
> not route optimize traffic.

I agree. But maybe "...must not use Route Optimization mode" would be
more accurate than "...must not route optimize traffic", since other
mechanisms (e.g., draft-weniger-rota-00.txt) exist that optimize the
route without revealing the CoA to CN.
=20
> 2) The solution in draft-ietf-mip6-bootstrapping-split does=20
> not specify=20
> anything for local home agent assignment. There is nothing in=20

But draft-ietf-mip6-bootstrapping-split supports location-dependent HA
address discovery, as Vijay pointed out. Consequently, MN should be able
to discover and bootstrap an HA from the visited network, i.e., a local
HA, right?=20

> the protocol=20
> to actually move the HA from the MSP's network to the serving=20
> network. The=20

What do you mean by moving the HA? A scenario that I had in mind is what
I called "eager local HA assignment": A MN bootstraps with a local HA
after moving to a new network while being registered with other (e.g.,
previously local) HAs. The other HAs can be used for ongoing
communication sessions, whereas the new (local) HA can be used for
future communication sessions (e.g., for improved routing efficiency in
case of reverse tunneling).

> MN gets to choose an HA from whatever HAs the MSP's DNS SRV=20
> RR advertises.=20

As already mentioned, I had location-dependent HA address discovery in
mind (as mentioned in section 5.1.1 DNS lookup by Home Agent Name).

> If that happens to be in the serving network, then=20
> correspondents will be=20
> able to obtain some information about where the MN is, but it=20
> could equally=20
> well be on the other side of the globe.

I agree that in general other nodes do not know if the HoA in MN's DNS
entry belongs to a local HA or a remote HA, i.e., whether the MN is
currently at the location corresponding to the HoA in DNS or not. I
think this is also the issue Gerardo mentioned in his mail.

The severity of the issue depends on the MN's strategy to select HAs for
bootstrapping and whether this strategy is known. E.g., if most MNs use
local HAs, the MN's HoA obtained from DNS most likely corresponds to
MN's location. If most MNs don't use local HAs, this problem might be
less severe. Maybe different providers force different (default)
strategies, but if the strategy is known, the problem may become severe
again.
Note that it might be beneficial to use HAs from the visited network,
since they can provide good routing efficiency even in case of reverse
tunneling.=20


> Note that the integrated scenerio (which the DT is currently=20
> working on)=20
> will have a mechanism whereby a local home agent can be=20
> assigned, since the=20
> MN gets the HA address from the local DHCP server.

I guess this location privacy issue applies more to the integrated
scenario. But as the integrated scenario can be seen a special case of
the split scenario, it should apply to both.=20

>=20
> 3) Since the HoA doesn't change once the MN has established=20
> it, I fail to=20
> see how an attacker can track the MN's location. Once the MN=20
> has established=20
> the HoA, it will appear to be at a fixed topological location=20
> in the MSP's=20
> network regardless of where the care of address is, if route=20
> optimization is=20
> not used.

Yes, CN cannot track MN's movement by looking at the very MN's HoA that
CN's higher layers are using for communication with MN. The text was not
very clear at this point. The issue is that CN (and any other node)
might be able to track MN's movement by constantly querying MN's DNS
entry. However, this is only possible in the "eager local HA assignment"
scenario, i.e., if the MN always bootstraps with a local HA when
changing networks and requests DNS updates subsequently. As already
mentioned, this would have the benefit of improved routing efficiency in
case of reverse tunneling.=20
BTW, in this scenario the MN's DNS entry may potentially change quite
frequently. Since I currently do not see a motivation for MNs to
frequently bootstrap with different remote HAs, this could be a hint
that the MN's HoAs in DNS belong to local HAs.=20

>=20
> So I think the risk is considerably less that is portrayed by=20
> the above=20
> text. I think the following text would be more accurate:
>=20
>     Updating the mobile node's FQDN in the DNS
>     with the mobile node's home address has the
>     potential to expose some information about
>     the mobile node's location to correspondents
>     if the home agent selected by the mobile
>     node is in the serving network access provider's
>     network (that is, the serving network access
>     provider is also acting as the mobility service
>     provider). The risk here is not as deep as
>     with route optimization, since the mobile node
>     will effectively appear to be at a fixed topological
>     location in the mobility service provider's network
>     regardless of where the care of address is. To
>     mitigate the risk, the mobile node should
>     either not request DNS update or be careful
>     to select a home agent that is not within the
>     serving network access provider's network.
>=20
>=20
>             jak

I'm fine with the first half of the text. In the second half, maybe it
should be made clear that MN only appears to be at a fixed topological
location as long as it does not bootstrap with a new HA and requests DNS
update accordingly. Otherwise, nodes can query DNS to find out the new
MN's HoA and thus the potential new location.


Cheers,

Kilian


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



From mip6-bounces@ietf.org Tue Oct 04 10:19:24 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EMncZ-0003MB-Jy; Tue, 04 Oct 2005 10:18:19 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EMncW-0003K8-K3
	for mip6@megatron.ietf.org; Tue, 04 Oct 2005 10:18:18 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22337
	for <mip6@ietf.org>; Tue, 4 Oct 2005 10:18:12 -0400 (EDT)
Received: from dns2.tilab.com ([163.162.42.5])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EMnlA-0002GP-01
	for mip6@ietf.org; Tue, 04 Oct 2005 10:27:13 -0400
Received: from iowa2k01b.cselt.it ([163.162.242.202])
	by dns2.cselt.it (PMDF V6.1 #38895)
	with ESMTP id <0INU00443ADQOQ@dns2.cselt.it> for mip6@ietf.org; Tue,
	04 Oct 2005 16:17:50 +0200 (MEST)
Received: from EXC01B.cselt.it ([163.162.4.199]) by iowa2k01b.cselt.it with
	Microsoft SMTPSVC(6.0.3790.211); Tue, 04 Oct 2005 16:15:38 +0200
Date: Tue, 04 Oct 2005 16:17:48 +0200
From: Gerardo Giaretta <Gerardo.Giaretta@TILAB.COM>
Subject: RE: [Mip6] review of draft-ietf-mip6-bootstrapping-split-00.txt
To: Kilian Weniger <Kilian.Weniger@eu.panasonic.com>
Message-id: <DA62A6E0CDD1B34A84557FF1AC850C57016E9B7D@EXC01B.cselt.it>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.3790.326
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: quoted-printable
Importance: normal
Priority: normal
Thread-Topic: [Mip6] review of draft-ietf-mip6-bootstrapping-split-00.txt
Thread-Index: AcXF7cu9TufTtpm/TXOfrqWVZ+qRVwCz+1cgAAt0IZA=
Content-class: urn:content-classes:message
X-OriginalArrivalTime: 04 Oct 2005 14:15:38.0312 (UTC)
	FILETIME=[182A3C80:01C5C8EE]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a743e34ab8eb08259de9a7307caed594
Content-Transfer-Encoding: quoted-printable
Cc: mip6@ietf.org, Vijay Devarapalli <vijayd@iprg.nokia.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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Hi Kilian,

please see some quick comments below...

>=20
>=20
> Sorry for the late reply.=20
> Vijay already provided some answers that I had in mind.=20
> Please see some
> further comments below.
>=20
> > 1)  Reverse tunneling is the default in IPv6, that is to say,=20
> > if an HA is=20
> > used, reverse tunneling must be used, unless the traffic is=20
> > route optimized.=20
> > So it is more accurate to say that in order to protect=20
> > privacy, the MN must=20
> > not route optimize traffic.
>=20
> I agree. But maybe "...must not use Route Optimization mode" would be
> more accurate than "...must not route optimize traffic", since other
> mechanisms (e.g., draft-weniger-rota-00.txt) exist that optimize the
> route without revealing the CoA to CN.
> =20
> > 2) The solution in draft-ietf-mip6-bootstrapping-split does=20
> > not specify=20
> > anything for local home agent assignment. There is nothing in=20
>=20
> But draft-ietf-mip6-bootstrapping-split supports location-dependent HA
> address discovery, as Vijay pointed out. Consequently, MN=20
> should be able
> to discover and bootstrap an HA from the visited network,=20
> i.e., a local
> HA, right?=20
>=20

Yes. Note that this is true only if MSP =3D=3D ASP, otherwise we do not =
have
a local HA assignment.

As a side note, the HA discovery based on location-dependent naming is
currently an open issue of the draft. See issue 53 in the issue tracker
(http://www.mip4.org/issues/tracker/mip6/).

> > the protocol=20
> > to actually move the HA from the MSP's network to the serving=20
> > network. The=20
>=20
> What do you mean by moving the HA? A scenario that I had in=20
> mind is what
> I called "eager local HA assignment": A MN bootstraps with a local HA
> after moving to a new network while being registered with other (e.g.,
> previously local) HAs. The other HAs can be used for ongoing
> communication sessions, whereas the new (local) HA can be used for
> future communication sessions (e.g., for improved routing=20
> efficiency in
> case of reverse tunneling).
>=20

I agree that this may be a possible scenario.=20

> > MN gets to choose an HA from whatever HAs the MSP's DNS SRV=20
> > RR advertises.=20
>=20
> As already mentioned, I had location-dependent HA address discovery in
> mind (as mentioned in section 5.1.1 DNS lookup by Home Agent Name).
>=20
> > If that happens to be in the serving network, then=20
> > correspondents will be=20
> > able to obtain some information about where the MN is, but it=20
> > could equally=20
> > well be on the other side of the globe.
>=20
> I agree that in general other nodes do not know if the HoA in MN's DNS
> entry belongs to a local HA or a remote HA, i.e., whether the MN is
> currently at the location corresponding to the HoA in DNS or not. I
> think this is also the issue Gerardo mentioned in his mail.
>=20

Yes, my point is that the CNs cannot be sure if the HA assigned to the
MN is a local or a remote one.

> The severity of the issue depends on the MN's strategy to=20
> select HAs for
> bootstrapping and whether this strategy is known. E.g., if=20
> most MNs use
> local HAs, the MN's HoA obtained from DNS most likely corresponds to
> MN's location. If most MNs don't use local HAs, this problem might be
> less severe. Maybe different providers force different (default)
> strategies, but if the strategy is known, the problem may=20
> become severe
> again.

The CNs should "discover" somehow the HA assignment policies of the
operator. I guess this is not simple if different providers have
different strategies, but I agree that it may be possible as you
mentioned.

> Note that it might be beneficial to use HAs from the visited network,
> since they can provide good routing efficiency even in case of reverse
> tunneling.=20
>=20
>=20
> > Note that the integrated scenerio (which the DT is currently=20
> > working on)=20
> > will have a mechanism whereby a local home agent can be=20
> > assigned, since the=20
> > MN gets the HA address from the local DHCP server.
>=20
> I guess this location privacy issue applies more to the integrated
> scenario. But as the integrated scenario can be seen a special case of
> the split scenario, it should apply to both.=20
>=20

It applies more to integrated scenario because ideally in the split
scenario there is no relationship between the mobility service and the
network access service. But I agree that it may be an issue also in
split scenario since it is possible that MSP=3D=3DASP and that the MN
discovers the HA by a name that is geographic-dependent.

> >=20
> > 3) Since the HoA doesn't change once the MN has established=20
> > it, I fail to=20
> > see how an attacker can track the MN's location. Once the MN=20
> > has established=20
> > the HoA, it will appear to be at a fixed topological location=20
> > in the MSP's=20
> > network regardless of where the care of address is, if route=20
> > optimization is=20
> > not used.
>=20
> Yes, CN cannot track MN's movement by looking at the very=20
> MN's HoA that
> CN's higher layers are using for communication with MN. The=20
> text was not
> very clear at this point. The issue is that CN (and any other node)
> might be able to track MN's movement by constantly querying MN's DNS
> entry. However, this is only possible in the "eager local HA=20
> assignment"
> scenario, i.e., if the MN always bootstraps with a local HA when
> changing networks and requests DNS updates subsequently. As already
> mentioned, this would have the benefit of improved routing=20
> efficiency in
> case of reverse tunneling.=20
> BTW, in this scenario the MN's DNS entry may potentially change quite
> frequently. Since I currently do not see a motivation for MNs to
> frequently bootstrap with different remote HAs, this could be a hint
> that the MN's HoAs in DNS belong to local HAs.=20
>=20
> >=20
> > So I think the risk is considerably less that is portrayed by=20
> > the above=20
> > text. I think the following text would be more accurate:
> >=20
> >     Updating the mobile node's FQDN in the DNS
> >     with the mobile node's home address has the
> >     potential to expose some information about
> >     the mobile node's location to correspondents
> >     if the home agent selected by the mobile
> >     node is in the serving network access provider's
> >     network (that is, the serving network access
> >     provider is also acting as the mobility service
> >     provider). The risk here is not as deep as
> >     with route optimization, since the mobile node
> >     will effectively appear to be at a fixed topological
> >     location in the mobility service provider's network
> >     regardless of where the care of address is. To
> >     mitigate the risk, the mobile node should
> >     either not request DNS update or be careful
> >     to select a home agent that is not within the
> >     serving network access provider's network.
> >=20
> >=20
> >             jak
>=20
> I'm fine with the first half of the text. In the second half, maybe it
> should be made clear that MN only appears to be at a fixed topological
> location as long as it does not bootstrap with a new HA and=20
> requests DNS
> update accordingly. Otherwise, nodes can query DNS to find out the new
> MN's HoA and thus the potential new location.
>=20

okay, I think we are near to reach an agreement.=20
Kilian, can you please send some text based on James' text so that we
can close the issue?

--Gerardo

>=20
> Cheers,
>=20
> Kilian
>=20
>=20


Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia =
S.p.A.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
CONFIDENTIALITY NOTICE
This message and its attachments are addressed solely to the persons
above and may contain confidential information. If you have received
the message in error, be informed that any use of the content hereof
is prohibited. Please return it immediately to the sender and delete
the message. Should you have any questions, please send an e_mail to
MailAdmin@tilab.com. Thank you
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

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



From mip6-bounces@ietf.org Tue Oct 04 11:30:25 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EMokL-0001zc-28; Tue, 04 Oct 2005 11:30:25 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EMokJ-0001zW-9q
	for mip6@megatron.ietf.org; Tue, 04 Oct 2005 11:30:23 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02379
	for <mip6@ietf.org>; Tue, 4 Oct 2005 11:30:18 -0400 (EDT)
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EMosx-0006EX-NC
	for mip6@ietf.org; Tue, 04 Oct 2005 11:39:21 -0400
Message-ID: <038901c5c8f8$84d2cfa0$196115ac@dcml.docomolabsusa.com>
From: "James Kempf" <Kempf@docomolabs-usa.com>
To: "Vijay Devarapalli" <vijayd@iprg.nokia.com>
References: <4D2F935F08D41A4C8866693F4F0D7C4F4D5C6E@lan-ex-01.panasonic.de>
	<068401c5c5ed$c6499800$196115ac@dcml.docomolabsusa.com>
	<f1f4dcdc0509301658j18665804l61df84f6eab66ba7@mail.gmail.com>
	<082e01c5c702$c810bf90$196115ac@dcml.docomolabsusa.com>
	<4341DEFF.5070805@iprg.nokia.com>
Subject: Re: [Mip6] review of draft-ietf-mip6-bootstrapping-split-00.txt
Date: Tue, 4 Oct 2005 08:30:15 -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.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Content-Transfer-Encoding: 7bit
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

> Kilian was raising a different issue. the issues is valid when
> the access service provider also provides a local HA. lets say
> Alice goes to Tucson. she wants to download from a server in
> Tucson. ha1.bobsmova.com is too far. the MN and the CN are in
> Tucson. she configures a local HA and a local HoA. now if
> Alice has the DNS entry alice.bobsmova.com updated with the
> local HoA, the CNs know Alice is in Tucson.
>

Actually, no. What the CN knows is that Alice is now using an MSP with an HA 
in Tucson. She could equally well be in Oracle, Phoenix, or, for that 
matter, Chicago. Bob still might be serving as her MSA, but she may have 
changed her MSP to a Tucson-based MSP.

So I still don't see how being able to allocate a local HA is a problem.

Even if it were a problem, there are a couple other factors to consider.

1) The geographical area covered by a local HA is likely to be large, so the 
risk of location privacy compromise is likely to be relatively minor. It is 
not like using route optimization and exposing the CoA, where the last hop 
link may cover a small area, like an airport waiting lounge or a floor of an 
office building (but could also be quite large too, as is the case in 3G 
networks).

2) We've had some discussion and we have an outstanding issue about the text 
in draft-bootstrapping-split concerning local HA naming conventions. If we 
remove that text (as has been suggested), then there really is no support in 
the split scenario for local HA allocation.

            jak





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



From mip6-bounces@ietf.org Tue Oct 04 17:29:07 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EMuLT-0001HD-SL; Tue, 04 Oct 2005 17:29:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EMuLR-0001H7-27
	for mip6@megatron.ietf.org; Tue, 04 Oct 2005 17:29:05 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10161
	for <mip6@ietf.org>; Tue, 4 Oct 2005 17:29:02 -0400 (EDT)
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EMuU8-0005My-NP
	for mip6@ietf.org; Tue, 04 Oct 2005 17:38:08 -0400
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id j94KubO07597;
	Tue, 4 Oct 2005 13:56:37 -0700
X-mProtect: <200510042056> Nokia Silicon Valley Messaging Protection
Received: from manisht.iprg.nokia.com (205.226.2.40,
	claiming to be "[205.226.2.40]")
	by darkstar.iprg.nokia.com smtpdplsVwI; Tue, 04 Oct 2005 13:56:35 PDT
Message-ID: <4342F402.4050804@iprg.nokia.com>
Date: Tue, 04 Oct 2005 14:28:34 -0700
From: Vijay Devarapalli <vijayd@iprg.nokia.com>
User-Agent: Mozilla Thunderbird 1.0.6-1.4.1 (X11/20050719)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: James Kempf <Kempf@docomolabs-usa.com>
Subject: Re: [Mip6] review of draft-ietf-mip6-bootstrapping-split-00.txt
References: <4D2F935F08D41A4C8866693F4F0D7C4F4D5C6E@lan-ex-01.panasonic.de>
	<068401c5c5ed$c6499800$196115ac@dcml.docomolabsusa.com>
	<f1f4dcdc0509301658j18665804l61df84f6eab66ba7@mail.gmail.com>
	<082e01c5c702$c810bf90$196115ac@dcml.docomolabsusa.com> <4341
In-Reply-To: <038901c5c8f8$84d2cfa0$196115ac@dcml.docomolabsusa.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Content-Transfer-Encoding: 7bit
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

James Kempf wrote:
>> Kilian was raising a different issue. the issues is valid when
>> the access service provider also provides a local HA. lets say
>> Alice goes to Tucson. she wants to download from a server in
>> Tucson. ha1.bobsmova.com is too far. the MN and the CN are in
>> Tucson. she configures a local HA and a local HoA. now if
>> Alice has the DNS entry alice.bobsmova.com updated with the
>> local HoA, the CNs know Alice is in Tucson.
>>
> 
> Actually, no. What the CN knows is that Alice is now using an MSP with 
> an HA in Tucson. She could equally well be in Oracle, Phoenix, or, for 
> that matter, Chicago. Bob still might be serving as her MSA, but she may 
> have changed her MSP to a Tucson-based MSP.

to an extent this is a true. but to the CN it appears as if Alice
who always used to use ha1.bobsmova.com is now suddenly using
a HA in Tuscon. most likely reason is that Alice is roaming in
Tucson.

> Even if it were a problem, there are a couple other factors to consider.
> 
> 1) The geographical area covered by a local HA is likely to be large, so 
> the risk of location privacy compromise is likely to be relatively 
> minor. It is not like using route optimization and exposing the CoA, 
> where the last hop link may cover a small area, like an airport waiting 
> lounge or a floor of an office building (but could also be quite large 
> too, as is the case in 3G networks).

agree.

> 2) We've had some discussion and we have an outstanding issue about the 
> text in draft-bootstrapping-split concerning local HA naming 
> conventions. If we remove that text (as has been suggested), then there 
> really is no support in the split scenario for local HA allocation.

there is some confusion here. the suggestion to remove it was
because the reviewer felt there were not enough details. the
reviewer in fact likes the feature. :) see Jari Arkko's emails.
we (in the bootstrap design team) had deliberately removed the
details because it is very similar to HA lookup by name. there
is nothing new to explain.

Vijay

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



From mip6-bounces@ietf.org Tue Oct 04 17:46:07 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EMubv-00074m-Ba; Tue, 04 Oct 2005 17:46:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EMubt-00074e-QJ
	for mip6@megatron.ietf.org; Tue, 04 Oct 2005 17:46:05 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10921
	for <mip6@ietf.org>; Tue, 4 Oct 2005 17:46:02 -0400 (EDT)
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EMuke-0005mn-PQ
	for mip6@ietf.org; Tue, 04 Oct 2005 17:55:09 -0400
Message-ID: <04d601c5c92d$002cbb50$196115ac@dcml.docomolabsusa.com>
From: "James Kempf" <Kempf@docomolabs-usa.com>
To: "Vijay Devarapalli" <vijayd@iprg.nokia.com>
References: <4D2F935F08D41A4C8866693F4F0D7C4F4D5C6E@lan-ex-01.panasonic.de>
	<068401c5c5ed$c6499800$196115ac@dcml.docomolabsusa.com>
	<f1f4dcdc0509301658j18665804l61df84f6eab66ba7@mail.gmail.com>
	<082e01c5c702$c810bf90$196115ac@dcml.docomolabsusa.com> <4341
	<4342F402.4050804@iprg.nokia.com>
Subject: Re: [Mip6] review of draft-ietf-mip6-bootstrapping-split-00.txt
Date: Tue, 4 Oct 2005 14:45:56 -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.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Content-Transfer-Encoding: 7bit
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

> to an extent this is a true. but to the CN it appears as if Alice
> who always used to use ha1.bobsmova.com is now suddenly using
> a HA in Tuscon. most likely reason is that Alice is roaming in
> Tucson.
>

For an eavesdropper to know that she switched MSPs, they would have to 
monitor multiple conversations with Alice. And the assumption that she is 
roaming in Tucson is just that, an assumption. She could have moved to 
Tucson and she is now on a business trip in Chicago, or maybe the Tucson MSP 
is having a special on service this month ($14.95 for the first three 
months, whereas Bob charges $29.95) and Alice has decided to switch service 
providers even though she still lives in Palo Alto.

In other words, without some kind of outside information about Alice, the 
eavesdropper can't know for sure anything about where she is.

>> 2) We've had some discussion and we have an outstanding issue about the 
>> text in draft-bootstrapping-split concerning local HA naming conventions. 
>> If we remove that text (as has been suggested), then there really is no 
>> support in the split scenario for local HA allocation.
>
> there is some confusion here. the suggestion to remove it was
> because the reviewer felt there were not enough details. the
> reviewer in fact likes the feature. :) see Jari Arkko's emails.
> we (in the bootstrap design team) had deliberately removed the
> details because it is very similar to HA lookup by name. there
> is nothing new to explain.
>

As I (perhaps incorrectly) recall, the issue was defining an interoperable 
cannonical naming standard for naming local HAs. We could certainly do that, 
but I am not sure whether draft-bootstrapping-split is the right place to do 
it in. Actually, I like the feature too, its just I think it will be really 
hard to define such a naming convention, and also, as I mentioned before, 
there are many other dimensions of HA service that one might want to name 
one's HAs after, so one needs to ask the question about why this particular 
one should be singled out.

Anyway, I think it might be better to tackle the topic of location privacy 
in draft-bootstrapping-integrated, since there is very clearly an issue of 
local HA assignment, even if you don't buy my argument about a local 
HA-assigned HoA address really not providing much information about the MN's 
real geographic location.

            jak 



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



From mip6-bounces@ietf.org Wed Oct 05 04:33:20 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EN4iF-0003Ag-QY; Wed, 05 Oct 2005 04:33:19 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EN4iD-00037d-VH
	for mip6@megatron.ietf.org; Wed, 05 Oct 2005 04:33:18 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA06238
	for <mip6@ietf.org>; Wed, 5 Oct 2005 04:33:15 -0400 (EDT)
Received: from cluster-d.mailcontrol.com ([217.69.20.190]
	helo=rly24d.srv.mailcontrol.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EN4r1-0003Vn-Iq
	for mip6@ietf.org; Wed, 05 Oct 2005 04:42:27 -0400
Received: from hhe500-02.hbg.de.pan.eu (gate.eu.panasonic.com [194.173.20.12])
	by rly24d.srv.mailcontrol.com (MailControl) with SMTP id
	j958X15d005829; Wed, 5 Oct 2005 09:33:02 +0100
Received: from eundadmi01.pan.eu(10.100.96.64) by hhe500-02.hbg.de.pan.eu via
	smtp id 0344_332ef788_357b_11da_8bb2_0030482aac25;
	Wed, 05 Oct 2005 10:37:01 +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 2005100510325517-231159 ;
	Wed, 5 Oct 2005 10:32:55 +0200 
Received: from localhost ([127.0.0.1]) by VPN-MRelay-01.PRDCG.Panasonic.de;
	Wed, 5 Oct 2005 10:34:56 +0200
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Subject: RE: [Mip6] review of draft-ietf-mip6-bootstrapping-split-00.txt
Thread-Topic: [Mip6] review of draft-ietf-mip6-bootstrapping-split-00.txt
Thread-Index: AcXF7cu9TufTtpm/TXOfrqWVZ+qRVwCz+1cgAAt0IZAAJqFBIA==
To: "Gerardo Giaretta" <Gerardo.Giaretta@TILAB.COM>
Message-ID: <4D2F935F08D41A4C8866693F4F0D7C4F4D5E91@lan-ex-01.panasonic.de>
Date: Wed, 5 Oct 2005 10:32:49 +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-05-40-00 (www.mailcontrol.com) on 10.68.0.134
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Content-Transfer-Encoding: quoted-printable
Cc: mip6@ietf.org, Vijay Devarapalli <vijayd@iprg.nokia.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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

=20
> okay, I think we are near to reach an agreement.=20
> Kilian, can you please send some text based on James' text so that we
> can close the issue?
>=20
> --Gerardo
>=20

O.k., I tried to incorporate James' comments. How about the following
text

   Updating the mobile node's FQDN in the DNS with the mobile node's=20
   home address has the potential to expose some information about
   the mobile node's location to other nodes if the home agent=20
   selected by the mobile node is local, i.e., it is in the serving=20
   network access provider's network (that is, the serving network=20
   access provider is also acting as the mobility service provider).=20

   For three reasons, the risk here is not as deep as known from Route=20
   Optimization mode [draft-koodli-mip6-location-privacy-00.txt]. First,

   other nodes usually do not know whether the mobile node's home=20
   address belongs to a home agent that is local or remote for the=20
   mobile node and, hence, whether the mobile node is really at the=20
   location corresponding to the home address. Second, the mobile node=20
   (if using reverse tunneling) will effectively appear to be at a fixed

   topological location in the mobility service provider's network=20
   regardless of the current mobile node's location. Thus, only the=20
   location at the time of bootstrapping would be revealed. Third,=20
   depending on the deployment scenario, the geographical area covered=20
   by a local home agent (being the "most local" home agent) may be much

   larger than the area covered by an access router. Since the accuracy=20
   of the location derivable from the address decreases with increasing=20
   coverage, the accuracy may low.

   However, the risk may be high if the mobile node's home agent=20
   selection policy is known. If, for instance, the mobile node=20
   bootstraps with a new local home agent as soon as moving to another=20
   network to improve routing efficiency of future communication=20
   sessions in Bi-directional Tunneling mode, other nodes are able to=20
   track mobile node's movement to some extent by constantly querying=20
   mobile node's DNS entry.=20

   To mitigate the risk, the mobile node should either not request DNS=20
   update or be careful to select a home agent that is not within the
   serving network access provider's network.=20

The text may also be applicable (with some changes) to the solution
draft for the integrated scenario.

Kilian


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



From mip6-bounces@ietf.org Wed Oct 05 04:52:02 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EN50M-0001iV-GR; Wed, 05 Oct 2005 04:52:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EN50L-0001eg-0z
	for mip6@megatron.ietf.org; Wed, 05 Oct 2005 04:52:01 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA07261
	for <mip6@ietf.org>; Wed, 5 Oct 2005 04:51:58 -0400 (EDT)
Received: from cluster-d.mailcontrol.com ([217.69.20.190]
	helo=rly34d.srv.mailcontrol.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EN599-00044Z-Mj
	for mip6@ietf.org; Wed, 05 Oct 2005 05:01:10 -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
	j958pktm002898; Wed, 5 Oct 2005 09:51:46 +0100
Received: from eundadmi01.pan.eu(10.100.96.64) by hhe500-02.hbg.de.pan.eu via
	smtp id 03be_d1558db2_357d_11da_99cc_0030482aac25;
	Wed, 05 Oct 2005 10:55:45 +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 2005100510513458-232462 ;
	Wed, 5 Oct 2005 10:51:34 +0200 
Received: from localhost ([127.0.0.1]) by VPN-MRelay-01.PRDCG.Panasonic.de;
	Wed, 5 Oct 2005 10:53:36 +0200
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Subject: RE: [Mip6] review of draft-ietf-mip6-bootstrapping-split-00.txt
Thread-Topic: [Mip6] review of draft-ietf-mip6-bootstrapping-split-00.txt
Thread-Index: AcXF7cu9TufTtpm/TXOfrqWVZ+qRVwCz+1cgAAt0IZAAJ4fasA==
To: "Gerardo Giaretta" <Gerardo.Giaretta@TILAB.COM>
Message-ID: <4D2F935F08D41A4C8866693F4F0D7C4F4D5EA2@lan-ex-01.panasonic.de>
Date: Wed, 5 Oct 2005 10:51:29 +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-05-40-00 (www.mailcontrol.com) on 10.68.0.144
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Content-Transfer-Encoding: quoted-printable
Cc: mip6@ietf.org, Vijay Devarapalli <vijayd@iprg.nokia.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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

(sending again without superfluous line breaks...)

> okay, I think we are near to reach an agreement.=20
> Kilian, can you please send some text based on James' text so that we
> can close the issue?
>=20
> --Gerardo
>=20

O.k., I tried to incorporate James' comments. How about the following
text

   Updating the mobile node's FQDN in the DNS with the mobile node's=20
   home address has the potential to expose some information about
   the mobile node's location to other nodes if the home agent=20
   selected by the mobile node is local, i.e., it is in the serving=20
   network access provider's network (that is, the serving network=20
   access provider is also acting as the mobility service provider).=20

   For three reasons, the risk here is not as deep as known from Route=20
   Optimization mode [draft-koodli-mip6-location-privacy-00.txt].=20
   First, other nodes usually do not know whether the mobile node's=20
   home address belongs to a home agent that is local or remote for=20
   the mobile node and, hence, whether the mobile node is really at=20
   the location corresponding to the home address. Second, the mobile=20
   node (if using reverse tunneling) will effectively appear to be at=20
   a fixed topological location in the mobility service provider's=20
   network regardless of the current mobile node's location. Thus,=20
   only the location at the time of bootstrapping would be revealed.=20
   Third, depending on the deployment scenario, the geographical area=20
   covered by a local home agent (being the "most local" home agent)=20
   may be much larger than the area covered by an access router. Since=20
   the accuracy of the location derivable from the address decreases=20
   with increasing coverage, the accuracy may low.

   However, the risk may be high if the mobile node's home agent=20
   selection policy is known. If, for instance, the mobile node=20
   bootstraps with a new local home agent as soon as moving to another=20
   network to improve routing efficiency of future communication=20
   sessions in Bi-directional Tunneling mode, other nodes are able to=20
   track mobile node's movement to some extent by constantly querying=20
   mobile node's DNS entry.=20

   To mitigate the risk, the mobile node should either not request DNS=20
   update or be careful to select a home agent that is not within the
   serving network access provider's network.=20

The text may also be applicable (with some changes) to the solution
draft for the integrated scenario.

Kilian



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



From mip6-bounces@ietf.org Wed Oct 05 08:29:21 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EN8Of-0005aW-QO; Wed, 05 Oct 2005 08:29:21 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EN8OZ-0005Wk-IG
	for mip6@megatron.ietf.org; Wed, 05 Oct 2005 08:29:19 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA19809
	for <mip6@ietf.org>; Wed, 5 Oct 2005 08:29:13 -0400 (EDT)
Received: from dns2.tilab.com ([163.162.42.5])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EN8XQ-000294-Qs
	for mip6@ietf.org; Wed, 05 Oct 2005 08:38:26 -0400
Received: from iowa2k01b.cselt.it ([163.162.242.202])
	by dns2.cselt.it (PMDF V6.1 #38895)
	with ESMTP id <0INW00K2C00B3V@dns2.cselt.it> for mip6@ietf.org; Wed,
	05 Oct 2005 14:29:00 +0200 (MEST)
Received: from EXC01B.cselt.it ([163.162.4.199]) by iowa2k01b.cselt.it with
	Microsoft SMTPSVC(6.0.3790.211); Wed, 05 Oct 2005 14:26:47 +0200
Date: Wed, 05 Oct 2005 14:28:58 +0200
From: Gerardo Giaretta <Gerardo.Giaretta@TILAB.COM>
Subject: RE: [Mip6] review of draft-ietf-mip6-bootstrapping-split-00.txt
To: James Kempf <Kempf@docomolabs-usa.com>,
	Vijay Devarapalli <vijayd@iprg.nokia.com>
Message-id: <DA62A6E0CDD1B34A84557FF1AC850C57016E9B92@EXC01B.cselt.it>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.3790.326
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: quoted-printable
Importance: normal
Priority: normal
Thread-Topic: [Mip6] review of draft-ietf-mip6-bootstrapping-split-00.txt
Thread-Index: AcXJLpdNvNJDrU59QnqxBP1x1TQ6TAAVgJxg
Content-class: urn:content-classes:message
X-OriginalArrivalTime: 05 Oct 2005 12:26:47.0421 (UTC)
	FILETIME=[0DDD1AD0:01C5C9A8]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 36c793b20164cfe75332aa66ddb21196
Content-Transfer-Encoding: quoted-printable
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

> > to an extent this is a true. but to the CN it appears as if Alice
> > who always used to use ha1.bobsmova.com is now suddenly using
> > a HA in Tuscon. most likely reason is that Alice is roaming in
> > Tucson.
> >
>=20
> For an eavesdropper to know that she switched MSPs, they=20
> would have to=20
> monitor multiple conversations with Alice. And the assumption=20
> that she is=20
> roaming in Tucson is just that, an assumption. She could have=20
> moved to=20
> Tucson and she is now on a business trip in Chicago, or maybe=20
> the Tucson MSP=20
> is having a special on service this month ($14.95 for the first three=20
> months, whereas Bob charges $29.95) and Alice has decided to=20
> switch service=20
> providers even though she still lives in Palo Alto.
>=20
> In other words, without some kind of outside information=20
> about Alice, the=20
> eavesdropper can't know for sure anything about where she is.
>

This is true, as I mentioned before. In split scenario, CNs can only
make assumptions or guess, but can never be sure that a particular HA is
a local one.
=20
> >> 2) We've had some discussion and we have an outstanding=20
> issue about the=20
> >> text in draft-bootstrapping-split concerning local HA=20
> naming conventions.=20
> >> If we remove that text (as has been suggested), then there=20
> really is no=20
> >> support in the split scenario for local HA allocation.
> >
> > there is some confusion here. the suggestion to remove it was
> > because the reviewer felt there were not enough details. the
> > reviewer in fact likes the feature. :) see Jari Arkko's emails.
> > we (in the bootstrap design team) had deliberately removed the
> > details because it is very similar to HA lookup by name. there
> > is nothing new to explain.
> >
>=20
> As I (perhaps incorrectly) recall, the issue was defining an=20
> interoperable=20
> cannonical naming standard for naming local HAs. We could=20
> certainly do that,=20
> but I am not sure whether draft-bootstrapping-split is the=20
> right place to do=20
> it in. Actually, I like the feature too, its just I think it=20
> will be really=20
> hard to define such a naming convention, and also, as I=20
> mentioned before,=20
> there are many other dimensions of HA service that one might=20
> want to name=20
> one's HAs after, so one needs to ask the question about why=20
> this particular=20
> one should be singled out.
>=20
> Anyway, I think it might be better to tackle the topic of=20
> location privacy=20
> in draft-bootstrapping-integrated, since there is very=20
> clearly an issue of=20
> local HA assignment, even if you don't buy my argument about a local=20
> HA-assigned HoA address really not providing much information=20
> about the MN's=20
> real geographic location.
>=20

James, as you know integrated draft will describe HA discovery based on
DHCP. I don't think the location privacy issue is specific to DHCP based
solution, thought I agree it is more applicable to integrated scenario.=20

Kuntal suggested to change slightly the scope and the title of the split
scenario document, since the solution defined in that draft is
applicable also to integrated scenario. If we decide to do that, I think
the right place to add some text (similar to what you sent few days ago
or Kilian sent today to the list) is the new split scenario document.
This is also beacuse the DNS update procedure by the HA is defined in
that draft.

What do yuo and others think?

--Gerardo



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


Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia =
S.p.A.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
CONFIDENTIALITY NOTICE
This message and its attachments are addressed solely to the persons
above and may contain confidential information. If you have received
the message in error, be informed that any use of the content hereof
is prohibited. Please return it immediately to the sender and delete
the message. Should you have any questions, please send an e_mail to
MailAdmin@tilab.com. Thank you
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

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



From mip6-bounces@ietf.org Wed Oct 05 16:11:32 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ENFbw-0000kq-25; Wed, 05 Oct 2005 16:11:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ENC0J-0005NN-MS
	for mip6@megatron.ietf.org; Wed, 05 Oct 2005 12:20:30 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02644
	for <mip6@ietf.org>; Wed, 5 Oct 2005 12:20:21 -0400 (EDT)
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ENC9A-00005m-27
	for mip6@ietf.org; Wed, 05 Oct 2005 12:29:37 -0400
Message-ID: <067201c5c9c8$ab909a70$196115ac@dcml.docomolabsusa.com>
From: "James Kempf" <Kempf@docomolabs-usa.com>
To: "Gerardo Giaretta" <Gerardo.Giaretta@TILAB.COM>,
	"Kilian Weniger" <Kilian.Weniger@eu.panasonic.com>
References: <4D2F935F08D41A4C8866693F4F0D7C4F4D5E91@lan-ex-01.panasonic.de>
Subject: Re: [Mip6] review of draft-ietf-mip6-bootstrapping-split-00.txt
Date: Wed, 5 Oct 2005 09:20:15 -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.0 (/)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Content-Transfer-Encoding: 7bit
Cc: mip6@ietf.org, Vijay Devarapalli <vijayd@iprg.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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

I think I can agree to this with one exception (marked with jak>> below:

   Updating the mobile node's FQDN in the DNS with the mobile node's
   home address has the potential to expose some information about
   the mobile node's location to other nodes if the home agent
   selected by the mobile node is local, i.e., it is in the serving
   network access provider's network (that is, the serving network
   access provider is also acting as the mobility service provider).

   For three reasons, the risk here is not as deep as known from Route
   Optimization mode [draft-koodli-mip6-location-privacy-00.txt]. First,

   other nodes usually do not know whether the mobile node's home
   address belongs to a home agent that is local or remote for the
   mobile node and, hence, whether the mobile node is really at the
   location corresponding to the home address. Second, the mobile node
   (if using reverse tunneling) will effectively appear to be at a fixed

   topological location in the mobility service provider's network
   regardless of the current mobile node's location. Thus, only the
   location at the time of bootstrapping would be revealed. Third,

jak>> The selection of HoA in and of itself doesn't reveal much about the 
location even at the time of bootstrapping. So I'd like to see this sentence 
("Thus...revealed.") dropped.

   depending on the deployment scenario, the geographical area covered
   by a local home agent (being the "most local" home agent) may be much

   larger than the area covered by an access router. Since the accuracy
   of the location derivable from the address decreases with increasing
   coverage, the accuracy may low.

   However, the risk may be high if the mobile node's home agent
   selection policy is known. If, for instance, the mobile node
   bootstraps with a new local home agent as soon as moving to another
   network to improve routing efficiency of future communication
   sessions in Bi-directional Tunneling mode, other nodes are able to
   track mobile node's movement to some extent by constantly querying
   mobile node's DNS entry.

   To mitigate the risk, the mobile node should either not request DNS
   update or be careful to select a home agent that is not within the
   serving network access provider's network.

Rest of it is OK.

However, before we put this text into the document, I think we need to 
decide whether or not we are going to resolve Issue #53 in favor of removing 
local HA naming from the split scenerio draft or in favor of keeping local 
HA naming in and defining a cannonical local HA naming convention for 
interoperability. If we decide in favor of removing, then I think we should 
save this text and put it into the integrated scenerio draft.

                        jak 



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



From mip6-bounces@ietf.org Wed Oct 05 16:11:37 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ENFc1-0000o9-CY; Wed, 05 Oct 2005 16:11:37 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ENCL7-0004Gt-Oa
	for mip6@megatron.ietf.org; Wed, 05 Oct 2005 12:41:57 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03347
	for <mip6@ietf.org>; Wed, 5 Oct 2005 12:41:54 -0400 (EDT)
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ENCU2-0000c6-IH
	for mip6@ietf.org; Wed, 05 Oct 2005 12:51:11 -0400
Message-ID: <068b01c5c9cb$af1525f0$196115ac@dcml.docomolabsusa.com>
From: "James Kempf" <Kempf@docomolabs-usa.com>
To: "Gerardo Giaretta" <Gerardo.Giaretta@TILAB.COM>,
	"Vijay Devarapalli" <vijayd@iprg.nokia.com>
References: <DA62A6E0CDD1B34A84557FF1AC850C57016E9B92@EXC01B.cselt.it>
Subject: Re: [Mip6] review of draft-ietf-mip6-bootstrapping-split-00.txt
Date: Wed, 5 Oct 2005 09:41:50 -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.0 (/)
X-Scan-Signature: 8fbbaa16f9fd29df280814cb95ae2290
Content-Transfer-Encoding: 7bit
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Gerardo,

I think the text should be added to the document where it is of concern. If 
the split scenerio document does not have any way to identify whether or not 
the HA is local, then it is not of concern. On the other hand, if it does, 
then it is of concern. I think we do agree that the DHCP draft will have a 
way to identify if the HA is local, so it is of concern there.

            jak

----- Original Message ----- 
From: "Gerardo Giaretta" <Gerardo.Giaretta@TILAB.COM>
To: "James Kempf" <Kempf@docomolabs-usa.com>; "Vijay Devarapalli" 
<vijayd@iprg.nokia.com>
Cc: <mip6@ietf.org>; "Kilian Weniger" <Kilian.Weniger@eu.panasonic.com>
Sent: Wednesday, October 05, 2005 5:28 AM
Subject: RE: [Mip6] review of draft-ietf-mip6-bootstrapping-split-00.txt


> > to an extent this is a true. but to the CN it appears as if Alice
> > who always used to use ha1.bobsmova.com is now suddenly using
> > a HA in Tuscon. most likely reason is that Alice is roaming in
> > Tucson.
> >
>
> For an eavesdropper to know that she switched MSPs, they
> would have to
> monitor multiple conversations with Alice. And the assumption
> that she is
> roaming in Tucson is just that, an assumption. She could have
> moved to
> Tucson and she is now on a business trip in Chicago, or maybe
> the Tucson MSP
> is having a special on service this month ($14.95 for the first three
> months, whereas Bob charges $29.95) and Alice has decided to
> switch service
> providers even though she still lives in Palo Alto.
>
> In other words, without some kind of outside information
> about Alice, the
> eavesdropper can't know for sure anything about where she is.
>

This is true, as I mentioned before. In split scenario, CNs can only
make assumptions or guess, but can never be sure that a particular HA is
a local one.

> >> 2) We've had some discussion and we have an outstanding
> issue about the
> >> text in draft-bootstrapping-split concerning local HA
> naming conventions.
> >> If we remove that text (as has been suggested), then there
> really is no
> >> support in the split scenario for local HA allocation.
> >
> > there is some confusion here. the suggestion to remove it was
> > because the reviewer felt there were not enough details. the
> > reviewer in fact likes the feature. :) see Jari Arkko's emails.
> > we (in the bootstrap design team) had deliberately removed the
> > details because it is very similar to HA lookup by name. there
> > is nothing new to explain.
> >
>
> As I (perhaps incorrectly) recall, the issue was defining an
> interoperable
> cannonical naming standard for naming local HAs. We could
> certainly do that,
> but I am not sure whether draft-bootstrapping-split is the
> right place to do
> it in. Actually, I like the feature too, its just I think it
> will be really
> hard to define such a naming convention, and also, as I
> mentioned before,
> there are many other dimensions of HA service that one might
> want to name
> one's HAs after, so one needs to ask the question about why
> this particular
> one should be singled out.
>
> Anyway, I think it might be better to tackle the topic of
> location privacy
> in draft-bootstrapping-integrated, since there is very
> clearly an issue of
> local HA assignment, even if you don't buy my argument about a local
> HA-assigned HoA address really not providing much information
> about the MN's
> real geographic location.
>

James, as you know integrated draft will describe HA discovery based on
DHCP. I don't think the location privacy issue is specific to DHCP based
solution, thought I agree it is more applicable to integrated scenario.

Kuntal suggested to change slightly the scope and the title of the split
scenario document, since the solution defined in that draft is
applicable also to integrated scenario. If we decide to do that, I think
the right place to add some text (similar to what you sent few days ago
or Kilian sent today to the list) is the new split scenario document.
This is also beacuse the DNS update procedure by the HA is defined in
that draft.

What do yuo and others think?

--Gerardo



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


Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia S.p.A.

====================================================================
CONFIDENTIALITY NOTICE
This message and its attachments are addressed solely to the persons
above and may contain confidential information. If you have received
the message in error, be informed that any use of the content hereof
is prohibited. Please return it immediately to the sender and delete
the message. Should you have any questions, please send an e_mail to
MailAdmin@tilab.com. Thank you
====================================================================



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



From mip6-bounces@ietf.org Wed Oct 05 16:11:46 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ENFcA-0000tS-R8; Wed, 05 Oct 2005 16:11:46 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ENCv1-0000tV-MD
	for mip6@megatron.ietf.org; Wed, 05 Oct 2005 13:19:03 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA05501
	for <mip6@ietf.org>; Wed, 5 Oct 2005 13:19:00 -0400 (EDT)
Received: from dns1.tilab.com ([163.162.42.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1END3r-0001lP-0U
	for mip6@ietf.org; Wed, 05 Oct 2005 13:28:17 -0400
Received: from iowa2k01a.cselt.it ([163.162.242.201])
	by dns1.cselt.it (PMDF V6.0-025 #38895)
	with ESMTP id <0INW00M3VDF7MX@dns1.cselt.it> for mip6@ietf.org; Wed,
	05 Oct 2005 19:18:43 +0200 (MEST)
Received: from EXC01B.cselt.it ([163.162.4.199]) by iowa2k01a.cselt.it with
	Microsoft SMTPSVC(6.0.3790.211); Wed, 05 Oct 2005 19:18:43 +0200
Date: Wed, 05 Oct 2005 19:18:42 +0200
From: Gerardo Giaretta <Gerardo.Giaretta@TILAB.COM>
Subject: RE: [Mip6] review of draft-ietf-mip6-bootstrapping-split-00.txt
To: James Kempf <Kempf@docomolabs-usa.com>,
	Vijay Devarapalli <vijayd@iprg.nokia.com>
Message-id: <DA62A6E0CDD1B34A84557FF1AC850C57016E9B96@EXC01B.cselt.it>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.3790.326
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: quoted-printable
Importance: normal
Priority: normal
Thread-Topic: [Mip6] review of draft-ietf-mip6-bootstrapping-split-00.txt
thread-index: AcXJy7ty5woTi/sYTiSryZQ7xtCQ+gABGrzw
Content-Class: urn:content-classes:message
X-OriginalArrivalTime: 05 Oct 2005 17:18:43.0152 (UTC)
	FILETIME=[D60D8D00:01C5C9D0]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 202a3ece0492a8c7e7c8672d5214398f
Content-Transfer-Encoding: quoted-printable
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 > Gerardo,
>=20
> I think the text should be added to the document where it is=20
> of concern. If=20
> the split scenerio document does not have any way to identify=20
> whether or not=20
> the HA is local, then it is not of concern. On the other=20
> hand, if it does,=20
> then it is of concern. I think we do agree that the DHCP=20
> draft will have a=20
> way to identify if the HA is local, so it is of concern there.
>

I agree.

Let's solve issue #53 and decide in which draft include the text.

--Gerardo
=20
>             jak
>=20
> ----- Original Message -----=20
> From: "Gerardo Giaretta" <Gerardo.Giaretta@TILAB.COM>
> To: "James Kempf" <Kempf@docomolabs-usa.com>; "Vijay Devarapalli"=20
> <vijayd@iprg.nokia.com>
> Cc: <mip6@ietf.org>; "Kilian Weniger"=20
> <Kilian.Weniger@eu.panasonic.com>
> Sent: Wednesday, October 05, 2005 5:28 AM
> Subject: RE: [Mip6] review of=20
> draft-ietf-mip6-bootstrapping-split-00.txt
>=20
>=20
> > > to an extent this is a true. but to the CN it appears as if Alice
> > > who always used to use ha1.bobsmova.com is now suddenly using
> > > a HA in Tuscon. most likely reason is that Alice is roaming in
> > > Tucson.
> > >
> >
> > For an eavesdropper to know that she switched MSPs, they
> > would have to
> > monitor multiple conversations with Alice. And the assumption
> > that she is
> > roaming in Tucson is just that, an assumption. She could have
> > moved to
> > Tucson and she is now on a business trip in Chicago, or maybe
> > the Tucson MSP
> > is having a special on service this month ($14.95 for the=20
> first three
> > months, whereas Bob charges $29.95) and Alice has decided to
> > switch service
> > providers even though she still lives in Palo Alto.
> >
> > In other words, without some kind of outside information
> > about Alice, the
> > eavesdropper can't know for sure anything about where she is.
> >
>=20
> This is true, as I mentioned before. In split scenario, CNs can only
> make assumptions or guess, but can never be sure that a=20
> particular HA is
> a local one.
>=20
> > >> 2) We've had some discussion and we have an outstanding
> > issue about the
> > >> text in draft-bootstrapping-split concerning local HA
> > naming conventions.
> > >> If we remove that text (as has been suggested), then there
> > really is no
> > >> support in the split scenario for local HA allocation.
> > >
> > > there is some confusion here. the suggestion to remove it was
> > > because the reviewer felt there were not enough details. the
> > > reviewer in fact likes the feature. :) see Jari Arkko's emails.
> > > we (in the bootstrap design team) had deliberately removed the
> > > details because it is very similar to HA lookup by name. there
> > > is nothing new to explain.
> > >
> >
> > As I (perhaps incorrectly) recall, the issue was defining an
> > interoperable
> > cannonical naming standard for naming local HAs. We could
> > certainly do that,
> > but I am not sure whether draft-bootstrapping-split is the
> > right place to do
> > it in. Actually, I like the feature too, its just I think it
> > will be really
> > hard to define such a naming convention, and also, as I
> > mentioned before,
> > there are many other dimensions of HA service that one might
> > want to name
> > one's HAs after, so one needs to ask the question about why
> > this particular
> > one should be singled out.
> >
> > Anyway, I think it might be better to tackle the topic of
> > location privacy
> > in draft-bootstrapping-integrated, since there is very
> > clearly an issue of
> > local HA assignment, even if you don't buy my argument about a local
> > HA-assigned HoA address really not providing much information
> > about the MN's
> > real geographic location.
> >
>=20
> James, as you know integrated draft will describe HA=20
> discovery based on
> DHCP. I don't think the location privacy issue is specific to=20
> DHCP based
> solution, thought I agree it is more applicable to integrated=20
> scenario.
>=20
> Kuntal suggested to change slightly the scope and the title=20
> of the split
> scenario document, since the solution defined in that draft is
> applicable also to integrated scenario. If we decide to do=20
> that, I think
> the right place to add some text (similar to what you sent=20
> few days ago
> or Kilian sent today to the list) is the new split scenario document.
> This is also beacuse the DNS update procedure by the HA is defined in
> that draft.
>=20
> What do yuo and others think?
>=20
> --Gerardo
>=20
>=20
>=20
> >             jak
> >
> >
> >
> > _______________________________________________
> > Mip6 mailing list
> > Mip6@ietf.org
> > https://www1.ietf.org/mailman/listinfo/mip6
> >
>=20
>=20
> Gruppo Telecom Italia - Direzione e coordinamento di Telecom=20
> Italia S.p.A.
>=20
> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> CONFIDENTIALITY NOTICE
> This message and its attachments are addressed solely to the persons
> above and may contain confidential information. If you have received
> the message in error, be informed that any use of the content hereof
> is prohibited. Please return it immediately to the sender and delete
> the message. Should you have any questions, please send an e_mail to
> MailAdmin@tilab.com. Thank you
> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=20
>=20
>=20


Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia =
S.p.A.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
CONFIDENTIALITY NOTICE
This message and its attachments are addressed solely to the persons
above and may contain confidential information. If you have received
the message in error, be informed that any use of the content hereof
is prohibited. Please return it immediately to the sender and delete
the message. Should you have any questions, please send an e_mail to=20
MailAdmin@tilab.com. Thank you
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

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



From mip6-bounces@ietf.org Wed Oct 05 16:11:48 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ENFcC-0000v2-Ll; Wed, 05 Oct 2005 16:11:48 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1END5D-0004WB-1R
	for mip6@megatron.ietf.org; Wed, 05 Oct 2005 13:29:35 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA05836
	for <mip6@ietf.org>; Wed, 5 Oct 2005 13:29:31 -0400 (EDT)
Received: from dns1.tilab.com ([163.162.42.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ENDE7-00020S-EN
	for mip6@ietf.org; Wed, 05 Oct 2005 13:38:48 -0400
Received: from iowa2k01a.cselt.it ([163.162.242.201])
	by dns1.cselt.it (PMDF V6.0-025 #38895)
	with ESMTP id <0INW00035DX072@dns1.cselt.it> for mip6@ietf.org; Wed,
	05 Oct 2005 19:29:24 +0200 (MEST)
Received: from EXC01B.cselt.it ([163.162.4.199]) by iowa2k01a.cselt.it with
	Microsoft SMTPSVC(6.0.3790.211); Wed, 05 Oct 2005 19:29:24 +0200
Date: Wed, 05 Oct 2005 19:29:24 +0200
From: Gerardo Giaretta <Gerardo.Giaretta@TILAB.COM>
To: mip6@ietf.org
Message-id: <DA62A6E0CDD1B34A84557FF1AC850C57016E9B97@EXC01B.cselt.it>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.3790.326
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: quoted-printable
Importance: normal
Priority: normal
Thread-Topic: [draft-ietf-mip6-bootstrapping-split-00] Issue 53
thread-index: AcXJ0lQqlWRexNzMSN2qMcQXN7bDNA==
Content-Class: urn:content-classes:message
X-OriginalArrivalTime: 05 Oct 2005 17:29:24.0558 (UTC)
	FILETIME=[545C56E0:01C5C9D2]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Content-Transfer-Encoding: quoted-printable
Subject: [Mip6] [draft-ietf-mip6-bootstrapping-split-00] Issue 53
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

I would like to hear your thoughts about issue #53 in
draft-ietf-mip6-bootstrapping-split-00.=20

The current version of the draft states:

        Additionally, it could be useful to provide an ability for the
Mobile=20
        Node to discover a Home Agent placed in a particular location
(e.g.=20
        on the visited link). In order to achieve this, the Mobile Node
must=20
        be able to construct a DNS request such that the DNS server will
be=20
        able to reply with a Home Agent from the requested location.
This can=20
        be accomplished by using a specific  naming convention for the
FQDNs=20
        of the Home Agents. As an example, an operator might assign the
FQDN=20
        "ha.locationA.operator.com" to the Home Agent located in
"location A"=20
        and the FQDN "ha.locationB.operator.com" to the Home Agent
located in=20
        "location B". If the Mobile Node wants to use a Home Agent
located in=20
        "location A", it will set the QNAME to
"ha.locationA.operator.com" in=20
        the DNS request.        =20

In his review, Jari mentioned:
"Possible, but the description is mostly handwaving and would probably
benefit from a more generic solution in any case. Suggest
removing this"

Based on the discussion we've had so far, we have two possible options:

1. remove the text and do not provide a way in
draft-ietf-mip6-bootstrapping-split to identify whether or not the HA is
local (based on Jari comment)

2. define a canonical local HA naming convention for interoperability

Please provide your comments.


--Gerardo









Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia =
S.p.A.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
CONFIDENTIALITY NOTICE
This message and its attachments are addressed solely to the persons
above and may contain confidential information. If you have received
the message in error, be informed that any use of the content hereof
is prohibited. Please return it immediately to the sender and delete
the message. Should you have any questions, please send an e_mail to=20
MailAdmin@tilab.com. Thank you
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

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



From mip6-bounces@ietf.org Wed Oct 05 16:40:48 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ENG4G-0002ky-K9; Wed, 05 Oct 2005 16:40:48 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ENG4F-0002kI-0N
	for mip6@megatron.ietf.org; Wed, 05 Oct 2005 16:40:47 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16626
	for <mip6@ietf.org>; Wed, 5 Oct 2005 16:40:44 -0400 (EDT)
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ENGD8-0007uX-TG
	for mip6@ietf.org; Wed, 05 Oct 2005 16:50:00 -0400
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id j95K4pl01454;
	Wed, 5 Oct 2005 13:04:51 -0700
X-mProtect: <200510052004> Nokia Silicon Valley Messaging Protection
Received: from mvdhcp14172.americas.nokia.com (172.18.141.72,
	claiming to be "[127.0.0.1]")
	by darkstar.iprg.nokia.com smtpdLHrYet; Wed, 05 Oct 2005 13:04:49 PDT
Message-ID: <43443962.2070102@iprg.nokia.com>
Date: Wed, 05 Oct 2005 13:36:50 -0700
From: Vijay Devarapalli <vijayd@iprg.nokia.com>
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Gerardo Giaretta <Gerardo.Giaretta@TILAB.COM>
Subject: Re: [Mip6] review of draft-ietf-mip6-bootstrapping-split-00.txt
References: <DA62A6E0CDD1B34A84557FF1AC850C57016E9B96@EXC01B.cselt.it>
In-Reply-To: <DA62A6E0CDD1B34A84557FF1AC850C57016E9B96@EXC01B.cselt.it>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Content-Transfer-Encoding: 7bit
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Gerardo Giaretta wrote:
>  > Gerardo,
> 
>>I think the text should be added to the document where it is 
>>of concern. If 
>>the split scenerio document does not have any way to identify 
>>whether or not 
>>the HA is local, then it is not of concern. On the other 
>>hand, if it does, 
>>then it is of concern. I think we do agree that the DHCP 
>>draft will have a 
>>way to identify if the HA is local, so it is of concern there.
>>
> 
> 
> I agree.
> 
> Let's solve issue #53 and decide in which draft include the text.

since everybody likes the feature of being able to lookup
a HA based on location, what is the issue? as Jari suggested
add more text?

Vijay



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



From mip6-bounces@ietf.org Wed Oct 05 17:12:26 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ENGYs-0003b8-3E; Wed, 05 Oct 2005 17:12:26 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ENGYq-0003aj-SU
	for mip6@megatron.ietf.org; Wed, 05 Oct 2005 17:12:24 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA27586
	for <mip6@ietf.org>; Wed, 5 Oct 2005 17:12:22 -0400 (EDT)
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ENGhm-0003kq-RK
	for mip6@ietf.org; Wed, 05 Oct 2005 17:21:40 -0400
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id j95Kdwh05622;
	Wed, 5 Oct 2005 13:39:58 -0700
X-mProtect: <200510052039> Nokia Silicon Valley Messaging Protection
Received: from mvdhcp14172.americas.nokia.com (172.18.141.72,
	claiming to be "[127.0.0.1]")
	by darkstar.iprg.nokia.com smtpdc18yby; Wed, 05 Oct 2005 13:39:57 PDT
Message-ID: <4344419E.8090809@iprg.nokia.com>
Date: Wed, 05 Oct 2005 14:11:58 -0700
From: Vijay Devarapalli <vijayd@iprg.nokia.com>
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Gerardo Giaretta <Gerardo.Giaretta@TILAB.COM>
Subject: Re: [Mip6] [draft-ietf-mip6-bootstrapping-split-00] Issue 53
References: <DA62A6E0CDD1B34A84557FF1AC850C57016E9B97@EXC01B.cselt.it>
In-Reply-To: <DA62A6E0CDD1B34A84557FF1AC850C57016E9B97@EXC01B.cselt.it>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Content-Transfer-Encoding: 7bit
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Gerardo Giaretta wrote:
> I would like to hear your thoughts about issue #53 in
> draft-ietf-mip6-bootstrapping-split-00. 
> 
> The current version of the draft states:
> 
>         Additionally, it could be useful to provide an ability for the
> Mobile 
>         Node to discover a Home Agent placed in a particular location
> (e.g. 
>         on the visited link). In order to achieve this, the Mobile Node
> must 
>         be able to construct a DNS request such that the DNS server will
> be 
>         able to reply with a Home Agent from the requested location.
> This can 
>         be accomplished by using a specific  naming convention for the
> FQDNs 
>         of the Home Agents. As an example, an operator might assign the
> FQDN 
>         "ha.locationA.operator.com" to the Home Agent located in
> "location A" 
>         and the FQDN "ha.locationB.operator.com" to the Home Agent
> located in 
>         "location B". If the Mobile Node wants to use a Home Agent
> located in 
>         "location A", it will set the QNAME to
> "ha.locationA.operator.com" in 
>         the DNS request.         
> 
> In his review, Jari mentioned:
> "Possible, but the description is mostly handwaving and would probably
> benefit from a more generic solution in any case. Suggest
> removing this"
> 
> Based on the discussion we've had so far, we have two possible options:
> 
> 1. remove the text and do not provide a way in
> draft-ietf-mip6-bootstrapping-split to identify whether or not the HA is
> local (based on Jari comment)
> 
> 2. define a canonical local HA naming convention for interoperability

I dont think anybody wanted to define a canonical name for local
HA. even in the first two paragraphs of section 5.1.1 we dont
define a canonical name. we only provide an example.

for HA lookup by name, we leave it to the deployment to configure
the MN with the right FQDNs. this means we dont define any
canonical name in section 5.1.1.

for HA lookup by service we need to define something. and we do
that in section 5.1.2.

so we just keep the current text. maybe add more text to make
sure it does not appear like handwaving. Jari, what would like
to see more specifically?

Vijay


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



From mip6-bounces@ietf.org Wed Oct 05 17:21:23 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ENGhX-0003jZ-Fo; Wed, 05 Oct 2005 17:21:23 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ENGhT-0003QQ-8g
	for mip6@megatron.ietf.org; Wed, 05 Oct 2005 17:21:21 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01165
	for <mip6@ietf.org>; Wed, 5 Oct 2005 17:21:16 -0400 (EDT)
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ENGqO-00053m-8x
	for mip6@ietf.org; Wed, 05 Oct 2005 17:30:34 -0400
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id j95Km1W15619;
	Wed, 5 Oct 2005 13:48:01 -0700
X-mProtect: <200510052048> Nokia Silicon Valley Messaging Protection
Received: from mvdhcp14172.americas.nokia.com (172.18.141.72,
	claiming to be "[127.0.0.1]")
	by darkstar.iprg.nokia.com smtpdyi2gtB; Wed, 05 Oct 2005 13:48:00 PDT
Message-ID: <43444382.3060705@iprg.nokia.com>
Date: Wed, 05 Oct 2005 14:20:02 -0700
From: Vijay Devarapalli <vijayd@iprg.nokia.com>
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: James Kempf <Kempf@docomolabs-usa.com>
Subject: Re: [Mip6] review of draft-ietf-mip6-bootstrapping-split-00.txt
References: <4D2F935F08D41A4C8866693F4F0D7C4F4D5E91@lan-ex-01.panasonic.de>
	<067201c5c9c8$ab909a70$196115ac@dcml.docomolabsusa.com>
In-Reply-To: <067201c5c9c8$ab909a70$196115ac@dcml.docomolabsusa.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Content-Transfer-Encoding: 7bit
Cc: Gerardo Giaretta <Gerardo.Giaretta@TILAB.COM>, 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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

James Kempf wrote:
> I think I can agree to this with one exception (marked with jak>> below:
> 
>   Updating the mobile node's FQDN in the DNS with the mobile node's
>   home address has the potential to expose some information about
>   the mobile node's location to other nodes if the home agent
>   selected by the mobile node is local, i.e., it is in the serving
>   network access provider's network (that is, the serving network
>   access provider is also acting as the mobility service provider).
> 
>   For three reasons, the risk here is not as deep as known from Route
>   Optimization mode [draft-koodli-mip6-location-privacy-00.txt]. First,
> 
>   other nodes usually do not know whether the mobile node's home
>   address belongs to a home agent that is local or remote for the
>   mobile node and, hence, whether the mobile node is really at the
>   location corresponding to the home address. Second, the mobile node
>   (if using reverse tunneling) will effectively appear to be at a fixed
> 
>   topological location in the mobility service provider's network
>   regardless of the current mobile node's location. Thus, only the
>   location at the time of bootstrapping would be revealed. Third,
> 
> jak>> The selection of HoA in and of itself doesn't reveal much about 
> the location even at the time of bootstrapping. So I'd like to see this 
> sentence ("Thus...revealed.") dropped.
> 
>   depending on the deployment scenario, the geographical area covered
>   by a local home agent (being the "most local" home agent) may be much
> 
>   larger than the area covered by an access router. Since the accuracy
>   of the location derivable from the address decreases with increasing
>   coverage, the accuracy may low.
> 
>   However, the risk may be high if the mobile node's home agent
>   selection policy is known. If, for instance, the mobile node
>   bootstraps with a new local home agent as soon as moving to another
>   network to improve routing efficiency of future communication
>   sessions in Bi-directional Tunneling mode, other nodes are able to
>   track mobile node's movement to some extent by constantly querying
>   mobile node's DNS entry.
> 
>   To mitigate the risk, the mobile node should either not request DNS
>   update or be careful to select a home agent that is not within the
>   serving network access provider's network.
> 
> Rest of it is OK.

sounds good to me too.

Vijay


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



From mip6-bounces@ietf.org Wed Oct 05 18:41:09 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ENHwj-000384-Nf; Wed, 05 Oct 2005 18:41:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ENHwh-00037z-Dy
	for mip6@megatron.ietf.org; Wed, 05 Oct 2005 18:41:07 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07355
	for <mip6@ietf.org>; Wed, 5 Oct 2005 18:41:04 -0400 (EDT)
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ENI5d-0007zz-5K
	for mip6@ietf.org; Wed, 05 Oct 2005 18:50:23 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id j95Mer51000950;
	Thu, 6 Oct 2005 07:40:53 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id j95MerfJ010935;
	Thu, 6 Oct 2005 07:40:53 +0900 (JST)
Received: from ovp1.toshiba.co.jp [133.199.192.124] by tsb-wall.toshiba.co.jp
	with SMTP id HAA10907 ; Thu, 6 Oct 2005 07:40:53 +0900
Received: from mx2.toshiba.co.jp (localhost [127.0.0.1])
	by ovp1.toshiba.co.jp  with ESMTP id j95Mer4v011387;
	Thu, 6 Oct 2005 07:40:53 +0900 (JST)
Received: from tsbpoa.po.toshiba.co.jp by toshiba.co.jp id j95MeqYT019783;
	Thu, 6 Oct 2005 07:40:52 +0900 (JST)
Received: from steelhead ([172.30.24.109])
	by mail.po.toshiba.co.jp (Sun Java System Messaging Server 6.1 (built
	Apr 28
	2004)) with ESMTPSA id <0INW00JT1SBY4620@mail.po.toshiba.co.jp>; Thu,
	06 Oct 2005 07:40:52 +0900 (JST)
Received: from ohba by steelhead with local (Exim 4.53)
	id 1ENHvF-00053s-Vz; Wed, 05 Oct 2005 15:39:37 -0700
Date: Wed, 05 Oct 2005 18:39:37 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Mip6] [draft-ietf-mip6-bootstrapping-split-00] Issue 53
In-reply-to: <DA62A6E0CDD1B34A84557FF1AC850C57016E9B97@EXC01B.cselt.it>
To: Gerardo Giaretta <Gerardo.Giaretta@TILAB.COM>
Message-id: <20051005223937.GG18626@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
References: <DA62A6E0CDD1B34A84557FF1AC850C57016E9B97@EXC01B.cselt.it>
User-Agent: Mutt/1.5.11
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f66b12316365a3fe519e75911daf28a8
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

As I don't believe we can come up with an acceptable canonical name
for local HA naming, I prefer solution 1.  Also, does the following
example in the first paragraph of section 5.1.1 give much insights to
implementors to understand how to configure an HA name?  If not, I'd
prefer just removing it.

"
  As an example, the Mobile Node could be configured with the name
  "ha1.example.com", where "example.com" is the domain name of the MSP
  granting the mobility service.
"

Regards,

Yoshihiro Ohba

On Wed, Oct 05, 2005 at 07:29:24PM +0200, Gerardo Giaretta wrote:
> I would like to hear your thoughts about issue #53 in
> draft-ietf-mip6-bootstrapping-split-00. 
> 
> The current version of the draft states:
> 
>         Additionally, it could be useful to provide an ability for the
> Mobile 
>         Node to discover a Home Agent placed in a particular location
> (e.g. 
>         on the visited link). In order to achieve this, the Mobile Node
> must 
>         be able to construct a DNS request such that the DNS server will
> be 
>         able to reply with a Home Agent from the requested location.
> This can 
>         be accomplished by using a specific  naming convention for the
> FQDNs 
>         of the Home Agents. As an example, an operator might assign the
> FQDN 
>         "ha.locationA.operator.com" to the Home Agent located in
> "location A" 
>         and the FQDN "ha.locationB.operator.com" to the Home Agent
> located in 
>         "location B". If the Mobile Node wants to use a Home Agent
> located in 
>         "location A", it will set the QNAME to
> "ha.locationA.operator.com" in 
>         the DNS request.         
> 
> In his review, Jari mentioned:
> "Possible, but the description is mostly handwaving and would probably
> benefit from a more generic solution in any case. Suggest
> removing this"
> 
> Based on the discussion we've had so far, we have two possible options:
> 
> 1. remove the text and do not provide a way in
> draft-ietf-mip6-bootstrapping-split to identify whether or not the HA is
> local (based on Jari comment)
> 
> 2. define a canonical local HA naming convention for interoperability
> 
> Please provide your comments.
> 
> 
> --Gerardo
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia S.p.A.
> 
> ====================================================================
> CONFIDENTIALITY NOTICE
> This message and its attachments are addressed solely to the persons
> above and may contain confidential information. If you have received
> the message in error, be informed that any use of the content hereof
> is prohibited. Please return it immediately to the sender and delete
> the message. Should you have any questions, please send an e_mail to 
> MailAdmin@tilab.com. 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 Wed Oct 05 19:33:46 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ENIle-0005zA-1J; Wed, 05 Oct 2005 19:33:46 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ENIlc-0005yF-H5
	for mip6@megatron.ietf.org; Wed, 05 Oct 2005 19:33:44 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09345
	for <mip6@ietf.org>; Wed, 5 Oct 2005 19:33:36 -0400 (EDT)
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ENIuU-000139-Ti
	for mip6@ietf.org; Wed, 05 Oct 2005 19:42:56 -0400
Message-ID: <07d601c5ca05$2f1527d0$196115ac@dcml.docomolabsusa.com>
From: "James Kempf" <Kempf@docomolabs-usa.com>
To: "Vijay Devarapalli" <vijayd@iprg.nokia.com>,
	"Gerardo Giaretta" <Gerardo.Giaretta@TILAB.COM>
References: <DA62A6E0CDD1B34A84557FF1AC850C57016E9B96@EXC01B.cselt.it>
	<43443962.2070102@iprg.nokia.com>
Subject: Re: [Mip6] review of draft-ietf-mip6-bootstrapping-split-00.txt
Date: Wed, 5 Oct 2005 16:33:26 -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.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Content-Transfer-Encoding: 7bit
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

The issue is defining a standardized naming convention for location. Jari? 
Did I capture that correctly?

            jak

----- Original Message ----- 
From: "Vijay Devarapalli" <vijayd@iprg.nokia.com>
To: "Gerardo Giaretta" <Gerardo.Giaretta@TILAB.COM>
Cc: "James Kempf" <Kempf@docomolabs-usa.com>; <mip6@ietf.org>; "Kilian 
Weniger" <Kilian.Weniger@eu.panasonic.com>
Sent: Wednesday, October 05, 2005 1:36 PM
Subject: Re: [Mip6] review of draft-ietf-mip6-bootstrapping-split-00.txt


> Gerardo Giaretta wrote:
>>  > Gerardo,
>>
>>>I think the text should be added to the document where it is of concern. 
>>>If the split scenerio document does not have any way to identify whether 
>>>or not the HA is local, then it is not of concern. On the other hand, if 
>>>it does, then it is of concern. I think we do agree that the DHCP draft 
>>>will have a way to identify if the HA is local, so it is of concern 
>>>there.
>>>
>>
>>
>> I agree.
>>
>> Let's solve issue #53 and decide in which draft include the text.
>
> since everybody likes the feature of being able to lookup
> a HA based on location, what is the issue? as Jari suggested
> add more text?
>
> Vijay
>
>
> 



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



From mip6-bounces@ietf.org Wed Oct 05 19:34:25 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ENImH-0006Mh-Dq; Wed, 05 Oct 2005 19:34:25 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ENImG-0006MM-Dd
	for mip6@megatron.ietf.org; Wed, 05 Oct 2005 19:34:24 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09387
	for <mip6@ietf.org>; Wed, 5 Oct 2005 19:34:21 -0400 (EDT)
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ENIvE-00014j-74
	for mip6@ietf.org; Wed, 05 Oct 2005 19:43:41 -0400
Message-ID: <07db01c5ca05$4f5c8d80$196115ac@dcml.docomolabsusa.com>
From: "James Kempf" <Kempf@docomolabs-usa.com>
To: "Gerardo Giaretta" <Gerardo.Giaretta@TILAB.COM>, <mip6@ietf.org>
References: <DA62A6E0CDD1B34A84557FF1AC850C57016E9B97@EXC01B.cselt.it>
Subject: Re: [Mip6] [draft-ietf-mip6-bootstrapping-split-00] Issue 53
Date: Wed, 5 Oct 2005 16:34:20 -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.0 (/)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Content-Transfer-Encoding: 7bit
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

I think we should remove this text in order to advance this document.

A standardized naming convention for HAs could be done in a separate 
document.

            jak

----- Original Message ----- 
From: "Gerardo Giaretta" <Gerardo.Giaretta@TILAB.COM>
To: <mip6@ietf.org>
Sent: Wednesday, October 05, 2005 10:29 AM
Subject: [Mip6] [draft-ietf-mip6-bootstrapping-split-00] Issue 53


I would like to hear your thoughts about issue #53 in
draft-ietf-mip6-bootstrapping-split-00.

The current version of the draft states:

        Additionally, it could be useful to provide an ability for the
Mobile
        Node to discover a Home Agent placed in a particular location
(e.g.
        on the visited link). In order to achieve this, the Mobile Node
must
        be able to construct a DNS request such that the DNS server will
be
        able to reply with a Home Agent from the requested location.
This can
        be accomplished by using a specific  naming convention for the
FQDNs
        of the Home Agents. As an example, an operator might assign the
FQDN
        "ha.locationA.operator.com" to the Home Agent located in
"location A"
        and the FQDN "ha.locationB.operator.com" to the Home Agent
located in
        "location B". If the Mobile Node wants to use a Home Agent
located in
        "location A", it will set the QNAME to
"ha.locationA.operator.com" in
        the DNS request.

In his review, Jari mentioned:
"Possible, but the description is mostly handwaving and would probably
benefit from a more generic solution in any case. Suggest
removing this"

Based on the discussion we've had so far, we have two possible options:

1. remove the text and do not provide a way in
draft-ietf-mip6-bootstrapping-split to identify whether or not the HA is
local (based on Jari comment)

2. define a canonical local HA naming convention for interoperability

Please provide your comments.


--Gerardo









Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia S.p.A.

====================================================================
CONFIDENTIALITY NOTICE
This message and its attachments are addressed solely to the persons
above and may contain confidential information. If you have received
the message in error, be informed that any use of the content hereof
is prohibited. Please return it immediately to the sender and delete
the message. Should you have any questions, please send an e_mail to
MailAdmin@tilab.com. 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 Wed Oct 05 19:37:25 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ENIpB-0006nC-0V; Wed, 05 Oct 2005 19:37:25 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ENIp7-0006mx-8D
	for mip6@megatron.ietf.org; Wed, 05 Oct 2005 19:37:23 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09454
	for <mip6@ietf.org>; Wed, 5 Oct 2005 19:37:17 -0400 (EDT)
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ENIy4-00018L-KU
	for mip6@ietf.org; Wed, 05 Oct 2005 19:46:38 -0400
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id j95N1xc13946;
	Wed, 5 Oct 2005 16:01:59 -0700
X-mProtect: <200510052301> Nokia Silicon Valley Messaging Protection
Received: from mvdhcp14172.americas.nokia.com (172.18.141.72,
	claiming to be "[127.0.0.1]")
	by darkstar.iprg.nokia.com smtpdChzEjI; Wed, 05 Oct 2005 16:01:57 PDT
Message-ID: <434462E6.9080404@iprg.nokia.com>
Date: Wed, 05 Oct 2005 16:33:58 -0700
From: Vijay Devarapalli <vijayd@iprg.nokia.com>
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Mip6] [draft-ietf-mip6-bootstrapping-split-00] Issue 53
References: <DA62A6E0CDD1B34A84557FF1AC850C57016E9B97@EXC01B.cselt.it>
	<20051005223937.GG18626@steelhead>
In-Reply-To: <20051005223937.GG18626@steelhead>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d2e37451f7f22841e3b6f40c67db0f
Content-Transfer-Encoding: 7bit
Cc: Gerardo Giaretta <Gerardo.Giaretta@TILAB.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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Yoshihiro Ohba wrote:
> As I don't believe we can come up with an acceptable canonical name
> for local HA naming, I prefer solution 1.  Also, does the following
> example in the first paragraph of section 5.1.1 give much insights to
> implementors to understand how to configure an HA name?  If not, I'd
> prefer just removing it.
> 
> "
>   As an example, the Mobile Node could be configured with the name
>   "ha1.example.com", where "example.com" is the domain name of the MSP
>   granting the mobility service.

just to make sure. Yoshi, you are saying the entire
section 5.1.1 needs to be removed. not just the last
paragraph which describes HA lookup by location (which
is what is being discussed here).

Vijay

> "
> 
> Regards,
> 
> Yoshihiro Ohba
> 
> On Wed, Oct 05, 2005 at 07:29:24PM +0200, Gerardo Giaretta wrote:
> 
>>I would like to hear your thoughts about issue #53 in
>>draft-ietf-mip6-bootstrapping-split-00. 
>>
>>The current version of the draft states:
>>
>>        Additionally, it could be useful to provide an ability for the
>>Mobile 
>>        Node to discover a Home Agent placed in a particular location
>>(e.g. 
>>        on the visited link). In order to achieve this, the Mobile Node
>>must 
>>        be able to construct a DNS request such that the DNS server will
>>be 
>>        able to reply with a Home Agent from the requested location.
>>This can 
>>        be accomplished by using a specific  naming convention for the
>>FQDNs 
>>        of the Home Agents. As an example, an operator might assign the
>>FQDN 
>>        "ha.locationA.operator.com" to the Home Agent located in
>>"location A" 
>>        and the FQDN "ha.locationB.operator.com" to the Home Agent
>>located in 
>>        "location B". If the Mobile Node wants to use a Home Agent
>>located in 
>>        "location A", it will set the QNAME to
>>"ha.locationA.operator.com" in 
>>        the DNS request.         
>>
>>In his review, Jari mentioned:
>>"Possible, but the description is mostly handwaving and would probably
>>benefit from a more generic solution in any case. Suggest
>>removing this"
>>
>>Based on the discussion we've had so far, we have two possible options:
>>
>>1. remove the text and do not provide a way in
>>draft-ietf-mip6-bootstrapping-split to identify whether or not the HA is
>>local (based on Jari comment)
>>
>>2. define a canonical local HA naming convention for interoperability
>>
>>Please provide your comments.
>>
>>
>>--Gerardo
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia S.p.A.
>>
>>====================================================================
>>CONFIDENTIALITY NOTICE
>>This message and its attachments are addressed solely to the persons
>>above and may contain confidential information. If you have received
>>the message in error, be informed that any use of the content hereof
>>is prohibited. Please return it immediately to the sender and delete
>>the message. Should you have any questions, please send an e_mail to 
>>MailAdmin@tilab.com. 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 Oct 05 20:06:42 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ENJHW-0000tE-L1; Wed, 05 Oct 2005 20:06:42 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ENJHU-0000su-PO
	for mip6@megatron.ietf.org; Wed, 05 Oct 2005 20:06:40 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA10293
	for <mip6@ietf.org>; Wed, 5 Oct 2005 20:06:39 -0400 (EDT)
Received: from inet-tsb.toshiba.co.jp ([202.33.96.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ENJQR-0001wu-5k
	for mip6@ietf.org; Wed, 05 Oct 2005 20:15:57 -0400
Received: from tsb-wall.toshiba.co.jp ([133.199.160.134])
	by inet-tsb.toshiba.co.jp  with ESMTP id j9606U51004434;
	Thu, 6 Oct 2005 09:06:30 +0900 (JST)
Received: (from root@localhost) by tsb-wall.toshiba.co.jp  id j9606Us4029510;
	Thu, 6 Oct 2005 09:06:30 +0900 (JST)
Received: from ovp1.toshiba.co.jp [133.199.192.124] by tsb-wall.toshiba.co.jp
	with SMTP id KAA29496 ; Thu, 6 Oct 2005 09:06:30 +0900
Received: from mx2.toshiba.co.jp (localhost [127.0.0.1])
	by ovp1.toshiba.co.jp  with ESMTP id j9606T9o016538;
	Thu, 6 Oct 2005 09:06:29 +0900 (JST)
Received: from tsbpoa.po.toshiba.co.jp by toshiba.co.jp id j9605ilw007313;
	Thu, 6 Oct 2005 09:06:28 +0900 (JST)
Received: from steelhead ([172.30.24.109])
	by mail.po.toshiba.co.jp (Sun Java System Messaging Server 6.1 (built
	Apr 28
	2004)) with ESMTPSA id <0INW00JGIWA34L30@mail.po.toshiba.co.jp>; Thu,
	06 Oct 2005 09:06:09 +0900 (JST)
Received: from ohba by steelhead with local (Exim 4.53)
	id 1ENJFq-00059E-Lv; Wed, 05 Oct 2005 17:04:58 -0700
Date: Wed, 05 Oct 2005 20:04:58 -0400
From: Yoshihiro Ohba <yohba@tari.toshiba.com>
Subject: Re: [Mip6] [draft-ietf-mip6-bootstrapping-split-00] Issue 53
In-reply-to: <434462E6.9080404@iprg.nokia.com>
To: Vijay Devarapalli <vijayd@iprg.nokia.com>
Message-id: <20051006000458.GI18626@steelhead>
MIME-version: 1.0
Content-type: text/plain; charset=iso-2022-jp
Content-disposition: inline
References: <DA62A6E0CDD1B34A84557FF1AC850C57016E9B97@EXC01B.cselt.it>
	<20051005223937.GG18626@steelhead> <434462E6.9080404@iprg.nokia.com>
User-Agent: Mutt/1.5.11
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 22bbb45ef41b733eb2d03ee71ece8243
Cc: Gerardo Giaretta <Gerardo.Giaretta@TILAB.COM>, mip6@ietf.org,
	Yoshihiro Ohba <yohba@tari.toshiba.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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Hi Vijay,

On Wed, Oct 05, 2005 at 04:33:58PM -0700, Vijay Devarapalli wrote:
> Yoshihiro Ohba wrote:
> > As I don't believe we can come up with an acceptable canonical name
> > for local HA naming, I prefer solution 1.  Also, does the following
> > example in the first paragraph of section 5.1.1 give much insights to
> > implementors to understand how to configure an HA name?  If not, I'd
> > prefer just removing it.
> > 
> > "
> >   As an example, the Mobile Node could be configured with the name
> >   "ha1.example.com", where "example.com" is the domain name of the MSP
> >   granting the mobility service.
> 
> just to make sure. Yoshi, you are saying the entire
> section 5.1.1 needs to be removed. 

No.  My opinion is:

- Section 5.1.1 should exist.

- The last paragraph of section 5.1.1 is not needed.

- Importance of the last sentence of the first paragraph (quoted
above) of section 5.1.1 is questionable.  (I know this part is not
what is being discussed here, but just a comment.)

Regards,

Yoshihiro Ohba


> not just the last
> paragraph which describes HA lookup by location (which
> is what is being discussed here).
> 
> Vijay
> 
> > "
> > 
> > Regards,
> > 
> > Yoshihiro Ohba
> > 
> > On Wed, Oct 05, 2005 at 07:29:24PM +0200, Gerardo Giaretta wrote:
> > 
> >>I would like to hear your thoughts about issue #53 in
> >>draft-ietf-mip6-bootstrapping-split-00. 
> >>
> >>The current version of the draft states:
> >>
> >>        Additionally, it could be useful to provide an ability for the
> >>Mobile 
> >>        Node to discover a Home Agent placed in a particular location
> >>(e.g. 
> >>        on the visited link). In order to achieve this, the Mobile Node
> >>must 
> >>        be able to construct a DNS request such that the DNS server will
> >>be 
> >>        able to reply with a Home Agent from the requested location.
> >>This can 
> >>        be accomplished by using a specific  naming convention for the
> >>FQDNs 
> >>        of the Home Agents. As an example, an operator might assign the
> >>FQDN 
> >>        "ha.locationA.operator.com" to the Home Agent located in
> >>"location A" 
> >>        and the FQDN "ha.locationB.operator.com" to the Home Agent
> >>located in 
> >>        "location B". If the Mobile Node wants to use a Home Agent
> >>located in 
> >>        "location A", it will set the QNAME to
> >>"ha.locationA.operator.com" in 
> >>        the DNS request.         
> >>
> >>In his review, Jari mentioned:
> >>"Possible, but the description is mostly handwaving and would probably
> >>benefit from a more generic solution in any case. Suggest
> >>removing this"
> >>
> >>Based on the discussion we've had so far, we have two possible options:
> >>
> >>1. remove the text and do not provide a way in
> >>draft-ietf-mip6-bootstrapping-split to identify whether or not the HA is
> >>local (based on Jari comment)
> >>
> >>2. define a canonical local HA naming convention for interoperability
> >>
> >>Please provide your comments.
> >>
> >>
> >>--Gerardo
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia S.p.A.
> >>
> >>====================================================================
> >>CONFIDENTIALITY NOTICE
> >>This message and its attachments are addressed solely to the persons
> >>above and may contain confidential information. If you have received
> >>the message in error, be informed that any use of the content hereof
> >>is prohibited. Please return it immediately to the sender and delete
> >>the message. Should you have any questions, please send an e_mail to 
> >>MailAdmin@tilab.com. 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 Thu Oct 06 05:40:12 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ENSEW-0005Lw-Pu; Thu, 06 Oct 2005 05:40:12 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ENSEU-0005Lr-O1
	for mip6@megatron.ietf.org; Thu, 06 Oct 2005 05:40:10 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA21209
	for <mip6@ietf.org>; Thu, 6 Oct 2005 05:40:08 -0400 (EDT)
Received: from cluster-d.mailcontrol.com ([217.69.20.190]
	helo=rly08d.srv.mailcontrol.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ENSNX-00072K-EH
	for mip6@ietf.org; Thu, 06 Oct 2005 05:49:33 -0400
Received: from hhe500-02.hbg.de.pan.eu (gate.eu.panasonic.com [194.173.20.12])
	by rly08d.srv.mailcontrol.com (MailControl) with SMTP id
	j969doVa017894; Thu, 6 Oct 2005 10:39:50 +0100
Received: from eundadmi01.pan.eu(10.100.96.64) by hhe500-02.hbg.de.pan.eu via
	smtp id 4fd7_b5a88044_364d_11da_9f08_0030482aac25;
	Thu, 06 Oct 2005 11:43:54 +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 2005100611394610-287252 ;
	Thu, 6 Oct 2005 11:39:46 +0200 
Received: from localhost ([127.0.0.1]) by VPN-MRelay-01.PRDCG.Panasonic.de;
	Thu, 6 Oct 2005 11:41:47 +0200
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Subject: RE: [Mip6] review of draft-ietf-mip6-bootstrapping-split-00.txt
Thread-Topic: [Mip6] review of draft-ietf-mip6-bootstrapping-split-00.txt
Thread-Index: AcXJ8eM2/Wal/uS/Q9iNrrHkVh3tNgAWSlgg
To: "James Kempf" <Kempf@docomolabs-usa.com>,
	"Gerardo Giaretta" <Gerardo.Giaretta@TILAB.COM>
Message-ID: <4D2F935F08D41A4C8866693F4F0D7C4F4D5FC9@lan-ex-01.panasonic.de>
Date: Thu, 6 Oct 2005 11:39:39 +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-05-40-00 (www.mailcontrol.com) on 10.68.0.118
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Content-Transfer-Encoding: quoted-printable
Cc: mip6@ietf.org, Vijay Devarapalli <vijayd@iprg.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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org


> jak>> The selection of HoA in and of itself doesn't reveal=20
> much about the=20
> location even at the time of bootstrapping. So I'd like to=20
> see this sentence=20
> ("Thus...revealed.") dropped.

But the sentence (and the entire paragraph) refers to the scenario
described in the first paragraph, which includes updating DNS (not only
HoA selection)? Anyhow, if this is misleading, I don't have problems
with removing the sentence, but I would like to make clear that the
fixed location refers to the location at the time of bootstrapping and
that it may change after bootstrapping again with a different HA. Can
you agree to the following sentence (and we drop the "Thus..revealed"
sentence, as you suggested)?

   "Second, the mobile=20
   node (if using reverse tunneling) will effectively appear to be at=20
   a fixed topological location in the mobility service provider's=20
   as long as it does not bootstrap again with a different home=20
   agent in a different network and request DNS update subsequently."


> interoperability. If we decide in favor of removing, then I=20
> think we should=20
> save this text and put it into the integrated scenerio draft.

I agree that the potential location privacy issue with local HAs should
be described in the sec cons sections in the integrated scenario draft.
But even if the text about location-dependent HA naming is removed from
the split scenario draft, location-dependent HA discovery may still be
possible to some extent by using country code suffixes (the location is
of course much less accurate). Depending on how strict the requirement
for location privacy is, an issue may still exist. If, for instance, a
user from US is on a business trip in Europe and that user roams to
Vodafone Germany, it may discover an HA for bootstrapping using
"ha1.vodafone.de" or "_mip6._ipv6.vodafone.de". When updating DNS with
the new HoA, that may give a hint that the user is currently in Germany.

And even the provider name itself could include some location
information if it is a small provider which only covers a small
geographical area.

What do others think?

Kilian



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



From mip6-bounces@ietf.org Thu Oct 06 07:16:59 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ENTkB-0006Lp-Al; Thu, 06 Oct 2005 07:16:59 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ENNJI-0006Uk-8s; Thu, 06 Oct 2005 00:24:48 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA22031;
	Thu, 6 Oct 2005 00:24:44 -0400 (EDT)
Received: from mail.site.uottawa.ca ([137.122.89.142] ident=root)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1ENNSI-0002ft-6E; Thu, 06 Oct 2005 00:34:07 -0400
Received: from paradise0.site.uottawa.ca (paradise0.site.uottawa.ca
	[137.122.93.16])
	by mail.site.uottawa.ca (8.9.3/8.9.3) with ESMTP id OAA25818
	for <cfp-list@site.uottawa.ca>; Wed, 5 Oct 2005 14:27:24 -0400 (EDT)
Received: from paradise0.site.uottawa.ca (localhost.localdomain [127.0.0.1])
	by paradise0.site.uottawa.ca (8.13.4/8.13.4) with ESMTP id
	j95IbxJ7020790
	for <cfp-list@site.uottawa.ca>; Wed, 5 Oct 2005 14:37:59 -0400
Received: (from mswim2005@localhost)
	by paradise0.site.uottawa.ca (8.13.4/8.13.4/Submit) id j95IbxCx020789
	for cfp-list@site.uottawa.ca; Wed, 5 Oct 2005 14:37:59 -0400
Date: Wed, 5 Oct 2005 14:37:59 -0400
From: MSWiM 2005 <mswim2005@site.uottawa.ca>
Message-Id: <200510051837.j95IbxCx020789@paradise0.site.uottawa.ca>
To: undisclosed-recipients:;
X-Spam-Score: 1.1 (+)
X-Scan-Signature: 057ebe9b96adec30a7efb2aeda4c26a4
X-Mailman-Approved-At: Thu, 06 Oct 2005 07:16:58 -0400
Subject: [Mip6] ACM MSWIM'05 Call For PARTICIPATION
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org


Please send a blank message to rshaikh@site.uottawa.ca with 
the title "UNSUBSCRIBE" if you want to be removed from this mailing list.

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

----------------------------------------------------------------------
         C A L L  for  P A R T I C I P A T I O N
              ***  ACM MSWiM 2005  ***
           The 8th ACM International Symposium on
   Modeling, Analysis and Simulation of Wireless and Mobile Systems  
                 October 10-13, 2005

              www.cs.unibo.it/mswim2005

              Hyatt Regency Montreal  Hotel
                  Montreal, Qc. Canada 

----------------------------------------------------------------------
Main Sponsors: ACM and IEEE
----------------------------------------------------------------------

The 8-th International ACM Symposium on Modeling, Analysis and 
Simulation of Wireless and Mobile Systems (MSWiM 2005) is intended 
to provide an international forum for the discussion and presentation 
of original ideas, recent results and achievements by researchers, 
students, M&S and systems developers on issues and challenges related to 
mobile and wireless systems.

MSWiM 2005 is a highly competitive, single-track conference. This
year's technical program includes (1) outstanding technical papers 
with both theoretical and pratical results of significance on all aspects
of modeling and analysis of wireless and mobile systems,
(2) Two outstanding keynote speakers, (3) a challenging panel session 
on Wireless Mesh Networks, (4) a poster session, 
(5) two tutorials, and (4) three full-day workshops. 

Please find below information concerning registration, hotel
accommodation, and a summary of MSWiM 2005 technical program.

We are looking forward to seeing in Montreal.

A. Boukerche and V. Leung
MSWiM 2005 General Co-Chairs

----------------------------------------------------------------------
                        CONFERENCE HIGHLIGHTS

Technical Program and Registration information can be found at:
        http://www.cs.unibo.it/mswim2005

CONFERENCE HOTEL/VENUE: 

Hyatt Regency Montreal  Hotel

CONFERENCE PROGRAM SUMMARY:
    2 Tutorials,  October 9th, 2005:

        * "Intermittently Connected Mobile Ad Hoc Networks and 
           Delay Tolerant Networks: Overview and Challenges"
           Dr. Zhensheng Zhang, San Diego Research Center

        * "IP-Oriented QoS in the Next Generation Networks: 
          Application to Wireless Networks"
          Dr. Pascal Lorenz, Universite de Haute Alsace, France 


     2 Keynote Speakers:

        October 10th, 2005
        * Prof. Catherine Rosenberg, University of Waterloo, Canada
          "Cross-layer Interactions and Optimizations 
           in Wireless Networks"

        October 11th, 2005
        * Prof. Ian F. Akyildiz, Georgia Insitute of Technology, USA 
          "Grand Challenges For Wireless Sensor Networks"

    10 Technical sessions (October 10-12, 2005)
       covering topics of:
         Multi-hop Networks, Resource Allocations and 
         Congestion Control, Network Connectivity and Radio Coverage 
         Wireless Multimedia, MAC Protocols, Analysis of Wireless
         and Mobile Networks, Vehicular Networks,
         Wireless Sensor Networks, and Energy and power consumption.

     2 Walk-in Poster/Demos Sessions 

     1 Conference Panel on:
         "Wireless Mesh Networking: Challenges and Opportunities" 

     3 one-day ACM workshops on October 13, 2004:

         * Q2SWinet: 1st ACM Workshop on QoS and Security in 
           Wireless and Mobile Networks

         * WMuNeP 2005: 1-st ACM Workshop on Wireless Multimedia 
           Networking and Performance Modeling (WMuNeP 2005)

         * PE-WASUN 2005:  2-nd ACM Workshop on Performance 
           Evaluation of Wireless Ad Hoc, Sensor, 
           and Ubiquitous Networks
                                        
***************************************************************

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



From mip6-bounces@ietf.org Thu Oct 06 12:19:45 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ENYTB-00028C-5I; Thu, 06 Oct 2005 12:19:45 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ENYT3-0001uU-OA
	for mip6@megatron.ietf.org; Thu, 06 Oct 2005 12:19:42 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13090
	for <mip6@ietf.org>; Thu, 6 Oct 2005 12:19:34 -0400 (EDT)
Received: from iramx2.ira.uni-karlsruhe.de ([141.3.10.81]
	ident=[U2FsdGVkX188kuqTxx7IL4aYfNGMAcWrKOk5zr4/4OU=])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ENYcA-0006qy-7w
	for mip6@ietf.org; Thu, 06 Oct 2005 12:29:03 -0400
Received: from irams1.ira.uni-karlsruhe.de ([141.3.10.5])
	by iramx2.ira.uni-karlsruhe.de with esmtps 
	id 1ENYSu-0002JW-5b; Thu, 06 Oct 2005 18:19:34 +0200
Received: from i72archimedes.tm.uni-karlsruhe.de ([141.3.71.83])
	by irams1.ira.uni-karlsruhe.de with esmtpsa 
	id 1ENYSs-0002fB-U4; Thu, 06 Oct 2005 18:19:26 +0200
Message-ID: <43454E8A.4070503@tm.uka.de>
Date: Thu, 06 Oct 2005 18:19:22 +0200
From: Christian Vogt <chvogt@tm.uka.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-DE;
	rv:1.7.10) Gecko/20050716 Thunderbird/1.0.6 Mnenhy/0.7.2.0
X-Accept-Language: de-DE, de, en-us, en
MIME-Version: 1.0
To: MIP6 <mip6@ietf.org>
X-Enigmail-Version: 0.90.0.0
X-Enigmail-Supports: pgp-inline, pgp-mime
X-Spam-Score: -13.8 (-------------)
X-Spam-Status: No
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Cc: TM-RO2 <tm-ro2@tm.uka.de>, Daniel Jungbluth <dj@danju.net>
Subject: [Mip6] Binding Lifetime for De-registrations
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-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="===============0819864453=="
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

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

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig485B88848DD0DC60FB8D6F97
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit

Hi everbody,

one question regarding the binding lifetime for Mobile IPv6
de-registrations.

Mobile nodes must set the Lifetime field in a de-registration Binding
Update (BU) to zero, AND the home and care-of addresses must be equal.
Correspondent nodes delete a binding if the Lifetime field of the BU is
zero OR the home and care-of addresses are equal.

Assume that the mobile node sets the Lifetime field in a de-registration
BU to a non-zero value.  What would be the Lifetime field in the
corresponding Binding Acknowledgement (BA)?

IMO, the Lifetime field in the BA should be zero for a de-registration
regardless of the lifetime used in the BU.  But RFC 3775 does not really
answer this question.  (See sections 6.1.8, 9.5.3, and 9.5.4.)

Is this something for RFC 3775bis?

Regards,
- Christian

--
Christian Vogt, Institute of Telematics, University of Karlsruhe
www.tm.uka.de/~chvogt/pubkey/


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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)

iD8DBQFDRU6OwstEk8gl2rURAhsEAJ0b6Sh/6aUwHpdWQ+irtb78llhhnACgkZLI
/diJ5HNFzIQrgYzaSz+J9qk=
=CEwC
-----END PGP SIGNATURE-----

--------------enig485B88848DD0DC60FB8D6F97--


--===============0819864453==
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

--===============0819864453==--




From mip6-bounces@ietf.org Thu Oct 06 13:01:49 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ENZ7t-00064w-Ed; Thu, 06 Oct 2005 13:01:49 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ENZ7p-00063i-VF
	for mip6@megatron.ietf.org; Thu, 06 Oct 2005 13:01:46 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15251
	for <mip6@ietf.org>; Thu, 6 Oct 2005 13:01:38 -0400 (EDT)
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ENZGr-0000CN-9T
	for mip6@ietf.org; Thu, 06 Oct 2005 13:11:07 -0400
Message-ID: <091401c5ca97$9a133670$196115ac@dcml.docomolabsusa.com>
From: "James Kempf" <Kempf@docomolabs-usa.com>
To: "Gerardo Giaretta" <Gerardo.Giaretta@TILAB.COM>,
	"Kilian Weniger" <Kilian.Weniger@eu.panasonic.com>
References: <4D2F935F08D41A4C8866693F4F0D7C4F4D5FC9@lan-ex-01.panasonic.de>
Subject: Re: [Mip6] review of draft-ietf-mip6-bootstrapping-split-00.txt
Date: Thu, 6 Oct 2005 10:01:32 -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.0 (/)
X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024
Content-Transfer-Encoding: 7bit
Cc: mip6@ietf.org, Vijay Devarapalli <vijayd@iprg.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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

> jak>> The selection of HoA in and of itself doesn't reveal
> much about the
> location even at the time of bootstrapping. So I'd like to
> see this sentence
> ("Thus...revealed.") dropped.

But the sentence (and the entire paragraph) refers to the scenario
described in the first paragraph, which includes updating DNS (not only
HoA selection)? Anyhow, if this is misleading, I don't have problems
with removing the sentence, but I would like to make clear that the
fixed location refers to the location at the time of bootstrapping and
that it may change after bootstrapping again with a different HA.

jak>> The only way an eavesdropper could know, from a DNS-registered home 
address obtained through bootstrapping, that a MN is at a particular 
location is:

1) The eavesdropper has been keeping track of the DNS-registered home 
address in the past and has seen that the newly registered address is 
different,
2) The eavesdropper knows the victim's home MSP, either from previous 
addresses, or from some other way (note: the victim's FQDN doesn't provide 
any information in general about the MSP, because the FQDN is handled by the 
MSA, which might be a separate administrative entity),
2) The eavesdropper knows that the newly registered address belongs to an 
MSP that is not the victim's home MSP and that the current MSP routinely 
uses local home agents,

In addition, the granularity of the information obtained from the home 
address depends on the topological to geographical coverage of the home 
agent. So if the coverage area is, say, the entire Bay Area in California, 
the eavesdropper doesn't get a whole heck of a lot of information about 
where the person is.

jak>> My point is that the eavesdropper needs a lot of additional 
information about the victim and the MSPs that the victim is using before it 
can conclude anything about the location. If you want to put all these 
conditions into the text, I think it would make the description more 
accurate.

Can
you agree to the following sentence (and we drop the "Thus..revealed"
sentence, as you suggested)?

   "Second, the mobile
   node (if using reverse tunneling) will effectively appear to be at
   a fixed topological location in the mobility service provider's
   as long as it does not bootstrap again with a different home
   agent in a different network and request DNS update subsequently."

jak>> That seems OK.

> interoperability. If we decide in favor of removing, then I
> think we should
> save this text and put it into the integrated scenerio draft.

I agree that the potential location privacy issue with local HAs should
be described in the sec cons sections in the integrated scenario draft.
But even if the text about location-dependent HA naming is removed from
the split scenario draft, location-dependent HA discovery may still be
possible to some extent by using country code suffixes (the location is
of course much less accurate). Depending on how strict the requirement
for location privacy is, an issue may still exist. If, for instance, a
user from US is on a business trip in Europe and that user roams to
Vodafone Germany, it may discover an HA for bootstrapping using
"ha1.vodafone.de" or "_mip6._ipv6.vodafone.de". When updating DNS with
the new HoA, that may give a hint that the user is currently in Germany.

jak>> If Vodafone has no local HA service in Germany, then the user will 
always use it's home MSP in the US. So there's no issue.

jak>> We're currently discussing among the authors about what to put in the 
draft regarding local home agent assignment. If there is no text specifying 
how to do it, then I think we don't need to say anything. But I think we do 
need to say something in the integrated scenario draft, because it will be 
possible there.

            jak 



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



From mip6-bounces@ietf.org Thu Oct 06 13:05:16 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ENZBE-0006U1-GY; Thu, 06 Oct 2005 13:05:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ENZBB-0006Tw-Oq
	for mip6@megatron.ietf.org; Thu, 06 Oct 2005 13:05:14 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15341
	for <mip6@ietf.org>; Thu, 6 Oct 2005 13:05:10 -0400 (EDT)
Received: from host50.foretec.com ([65.246.255.50] helo=mx2.foretec.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ENZKI-0000M4-Fc
	for mip6@ietf.org; Thu, 06 Oct 2005 13:14:39 -0400
Received: from p130.piuha.net ([193.234.218.130])
	by mx2.foretec.com with esmtp (Exim 4.24) id 1ENZB7-0002tw-UR
	for mip6@ietf.org; Thu, 06 Oct 2005 13:05:10 -0400
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id 0156F89870;
	Thu,  6 Oct 2005 19:59:32 +0300 (EEST)
Message-ID: <434557FF.5030605@kolumbus.fi>
Date: Thu, 06 Oct 2005 19:59:43 +0300
From: Jari Arkko <jari.arkko@kolumbus.fi>
User-Agent: Mozilla Thunderbird 1.0 (X11/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Christian Vogt <chvogt@tm.uka.de>
Subject: Re: [Mip6] Binding Lifetime for De-registrations
References: <43454E8A.4070503@tm.uka.de>
In-Reply-To: <43454E8A.4070503@tm.uka.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Content-Transfer-Encoding: 7bit
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Christian Vogt wrote:

> Hi everbody,
>
> one question regarding the binding lifetime for Mobile IPv6
> de-registrations.
>
> Mobile nodes must set the Lifetime field in a de-registration Binding
> Update (BU) to zero, AND the home and care-of addresses must be equal.
> Correspondent nodes delete a binding if the Lifetime field of the BU is
> zero OR the home and care-of addresses are equal.
>
> Assume that the mobile node sets the Lifetime field in a de-registration
> BU to a non-zero value.  What would be the Lifetime field in the
> corresponding Binding Acknowledgement (BA)?
>
> IMO, the Lifetime field in the BA should be zero for a de-registration
> regardless of the lifetime used in the BU.  But RFC 3775 does not really
> answer this question.  (See sections 6.1.8, 9.5.3, and 9.5.4.)
>
> Is this something for RFC 3775bis?

Probably.

--Jari



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



From mip6-bounces@ietf.org Thu Oct 06 13:09:20 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ENZFA-0007DR-En; Thu, 06 Oct 2005 13:09:20 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ENZF6-0007DA-MD
	for mip6@megatron.ietf.org; Thu, 06 Oct 2005 13:09:18 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15539
	for <mip6@ietf.org>; Thu, 6 Oct 2005 13:09:13 -0400 (EDT)
From: Basavaraj.Patil@nokia.com
Received: from mgw-ext01.nokia.com ([131.228.20.93])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ENZOC-0000UH-DS
	for mip6@ietf.org; Thu, 06 Oct 2005 13:18:42 -0400
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211])
	by mgw-ext01.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id
	j96H95Vb007467 for <mip6@ietf.org>; Thu, 6 Oct 2005 20:09:06 +0300
Received: from daebh101.NOE.Nokia.com ([10.241.35.111]) by
	esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 6 Oct 2005 20:09:01 +0300
Received: from daebe101.NOE.Nokia.com ([10.241.35.113]) by
	daebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 6 Oct 2005 12:08:30 -0500
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
Date: Thu, 6 Oct 2005 12:08:19 -0500
Message-ID: <456943D540CFC14A8D7138E64843F85301CFD7B4@daebe101.NOE.Nokia.com>
Thread-Topic: Timeslot requests for MIP6 WG agenda at IETF64
Thread-Index: AcXKmIweGBPYSpZFQlWpg1uQMP1DDg==
To: <mip6@ietf.org>
X-OriginalArrivalTime: 06 Oct 2005 17:08:30.0452 (UTC)
	FILETIME=[9344B340:01C5CA98]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Content-Transfer-Encoding: quoted-printable
Subject: [Mip6] Timeslot requests for MIP6 WG agenda at IETF64
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org


Hello,

The MIP6 WG will meet at IETF64. We have currently requested a 2.5 hour
slot
for the meeting. If you need a timeslot on the MIP6 WG agenda, please
send
a request to the chairs with the following information:

1. I-D title
2. Amount of time requested
3. Is the I-D within the scope of the WG charter? If not why is it
important to
   discuss this at the WG meeting?

-Raj

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



From mip6-bounces@ietf.org Thu Oct 06 14:33:21 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ENaYS-0001Mx-VS; Thu, 06 Oct 2005 14:33:20 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ENaYR-0001Ms-5o
	for mip6@megatron.ietf.org; Thu, 06 Oct 2005 14:33:19 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21405
	for <mip6@ietf.org>; Thu, 6 Oct 2005 14:33:17 -0400 (EDT)
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ENahY-0004iZ-GW
	for mip6@ietf.org; Thu, 06 Oct 2005 14:42:46 -0400
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id j96I08D02074;
	Thu, 6 Oct 2005 11:00:08 -0700
X-mProtect: <200510061800> Nokia Silicon Valley Messaging Protection
Received: from manisht.iprg.nokia.com (205.226.2.40,
	claiming to be "[205.226.2.40]")
	by darkstar.iprg.nokia.com smtpdnaPz29; Thu, 06 Oct 2005 11:00:06 PDT
Message-ID: <43456DAA.8040808@iprg.nokia.com>
Date: Thu, 06 Oct 2005 11:32:10 -0700
From: Vijay Devarapalli <vijayd@iprg.nokia.com>
User-Agent: Mozilla Thunderbird 1.0.6-1.4.1 (X11/20050719)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Christian Vogt <chvogt@tm.uka.de>
Subject: Re: [Mip6] Binding Lifetime for De-registrations
References: <43454E8A.4070503@tm.uka.de>
In-Reply-To: <43454E8A.4070503@tm.uka.de>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Content-Transfer-Encoding: 7bit
Cc: MIP6 <mip6@ietf.org>, TM-RO2 <tm-ro2@tm.uka.de>,
	Daniel Jungbluth <dj@danju.net>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Christian Vogt wrote:
> Hi everbody,
> 
> one question regarding the binding lifetime for Mobile IPv6
> de-registrations.
> 
> Mobile nodes must set the Lifetime field in a de-registration Binding
> Update (BU) to zero, AND the home and care-of addresses must be equal.

hmm.. not really. lifetime set to zero is enough for the HA to
treat the BU as a de-registration BU.

> Correspondent nodes delete a binding if the Lifetime field of the BU is
> zero OR the home and care-of addresses are equal.
> 
> Assume that the mobile node sets the Lifetime field in a de-registration
> BU to a non-zero value.  What would be the Lifetime field in the
> corresponding Binding Acknowledgement (BA)?

zero. anyway, it does not matter. if the MN gets a BAck with
status set to 0 (successful) in response to a de-registration
BU that it sent, it knows the HA has removed the binding cache
entry.

> IMO, the Lifetime field in the BA should be zero for a de-registration
> regardless of the lifetime used in the BU.  But RFC 3775 does not really
> answer this question.  (See sections 6.1.8, 9.5.3, and 9.5.4.)
> 
> Is this something for RFC 3775bis?

yes. if its not clear, it should be clarified.

Vijay

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



From mip6-bounces@ietf.org Thu Oct 06 23:05:54 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ENiYT-0005Ai-W7; Thu, 06 Oct 2005 23:05:54 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ENiYS-0005AZ-63
	for mip6@megatron.ietf.org; Thu, 06 Oct 2005 23:05:52 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA04510
	for <mip6@ietf.org>; Thu, 6 Oct 2005 23:05:48 -0400 (EDT)
Received: from av7-2-sn3.vrr.skanova.net ([81.228.9.182])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ENihe-0005xY-FU
	for mip6@ietf.org; Thu, 06 Oct 2005 23:15:22 -0400
Received: by av7-2-sn3.vrr.skanova.net (Postfix, from userid 502)
	id 40F4B3824F; Fri,  7 Oct 2005 04:59:20 +0200 (CEST)
Received: from smtp3-1-sn3.vrr.skanova.net (smtp3-1-sn3.vrr.skanova.net
	[81.228.9.101])
	by av7-2-sn3.vrr.skanova.net (Postfix) with ESMTP id 277713824C
	for <mip6@ietf.org>; Fri,  7 Oct 2005 04:59:20 +0200 (CEST)
Received: from shiraz.levkowetz.com (81-224-201-50-no45.tbcn.telia.com
	[81.224.201.50])
	by smtp3-1-sn3.vrr.skanova.net (Postfix) with ESMTP id 39D3237E42
	for <mip6@ietf.org>; Fri,  7 Oct 2005 05:05:37 +0200 (CEST)
Received: from shiraz.local.levkowetz.com ([192.168.3.14]
	helo=81-224-201-50-no45.tbcn.telia.com)
	by shiraz.levkowetz.com with esmtp (Exim 4.52) id 1ENiYC-0003ql-50
	for mip6@ietf.org; Fri, 07 Oct 2005 05:05:37 +0200
Content-Type: text/plain; charset=utf-8
To: mip6@ietf.org
From: Samita <tracker-mip6@mip4.org>
Date: Fri, 07 Oct 2005 03:05:32 +0000
MIME-Version: 1.0
Message-Id: <1128654332.89.0.88724834672.issue54@mip4.org>
X-Roundup-Name: Mip6 issue tracker
X-Roundup-Loop: hello
Content-Transfer-Encoding: quoted-printable
X-Helo-Check-Failed: Verification failed for HELO
	81-224-201-50-no45.tbcn.telia.com
X-SA-Exim-Connect-IP: 192.168.3.14
X-SA-Exim-Mail-From: roundup-admin@mip4.org
X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on 
	shiraz.levkowetz.com
X-Spam-Status: No, score=-103.8 required=2.5 tests=ALL_TRUSTED,AWL,BAYES_00,
	USER_IN_WHITELIST,X_HELO_CHECK_FAILED autolearn=ham version=3.0.4
X-SA-Exim-Version: 4.2 (built Thu, 03 Mar 2005 10:44:12 +0100)
X-SA-Exim-Scanned: Yes (on shiraz.levkowetz.com)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: a87a9cdae4ac5d3fbeee75cd0026d632
Content-Transfer-Encoding: quoted-printable
Subject: [Mip6] [issue54] Comments by Jari Arkko
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Mip6 issue tracker <tracker-mip6@mip4.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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org


New submission from Samita <Samita.Chakrabarti@eng.sun.com>:

Issue:

1st - agree with the comments in the I-D tracker.

2nd - I think this is a valid API and its standardization
is very useful. Overall, the document is in excellent shape.
Main my concern is what the document
says about its applicability:
 >   The applicability of this API mainly target user-level applications.
>   However, some Mobile IPv6 implementations may take advantage of this
>   API and implement part of the Mobile IPv6 protocol at the user-level.
>   It is up to the implementors to architect which part of the Mobile
>   IPv6 packet processing should be done at the user-level in order to
>   meet the design needs of the particular platform and operating system.
>   The target applications for this socket API is believed to be the=20
>   debugging and diagnostic applications as well as some policy=20
>   applications which would like to receive a copy of protocol=20
>   information at the application layer.=20
>
>   Note that user applications for transferring data between two
>   systems may not need to be mobility aware. Future IPv6 mobility
>   aware applications may use this socket API for per-packet
>   information for further processing at the application layer
>   program interface.
> =20
>
This leaves the impression that its the regular applications
that would be using this. But I would actually see the use
of this API either as an partial implementation of Mobile IPv6
itself in the user space, the construction of new tools & options
over existing Mobile IPv6 (e.g. mh-ping, rr-ping etc), or
very special case applications. Other applications should
probably be using other, higher level APIs such as the
the address selection API. For instance, if the monami6
effort gets completed, there might be a need for a flow-based
API to provide information to the mobility layer about the
desired characteristics so that the multihoming policy
decisions can be made. But I wouldn't actually want to
see applications to use MH operations own their own
to do this control.

>   It is up to the implementors to architect which part of the Mobile
>   IPv6 packet processing should be done at the user-level in order to
>   meet the design needs of the particular platform and operating system.
> =20
>
Perhaps you should warn already here that the implementation
ties itself also to IPsec processing. Maybe s/IPv6 packet/IPv6
and IPsec packet/

>  If the kernel
>  implementation supports this API, it is responsible for extracting
>  the Home address destination option data object and placing it as
>  destination option extension header in compliance with section
>  6.3 of Mobile IPv6 [2] base specification.

And 9.3.1, because presumably some IPsec processing may need
to take place.

Editorial:

>     struct mip6_prefix_advert {    /* Mobile Prefix Adverisements */
>
typo

>      appplications. This is captured in section 2.
>
typo

>   for Mobile Network [4] specific needs. Futhermore, it should be noted
>
typo

>    It is assumed that no portable applications will send routing hader
>
typo

>Expires: Novemebr, 2005                           Erik Nordmark=20
>
typo

>   possible by priviledged users. However, this API does not prevent
>
typo

----
Accepted and fixed in the updated doc.

----------
category: Editorial
draft: draft-ietf-mip6-mipext-advapi
messages: 183
nosy: samita
priority: Should fix
status: Accepted
title: Comments by Jari Arkko

_________________________________________________
Mip6 issue tracker <tracker-mip6@mip4.org>
<http://www.mip4.org/issues/tracker/mip6/issue54>
_________________________________________________

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



From mip6-bounces@ietf.org Thu Oct 06 23:11:10 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ENida-000795-6u; Thu, 06 Oct 2005 23:11:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ENidY-00076r-9N
	for mip6@megatron.ietf.org; Thu, 06 Oct 2005 23:11:08 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA04765
	for <mip6@ietf.org>; Thu, 6 Oct 2005 23:11:04 -0400 (EDT)
Received: from av7-1-sn3.vrr.skanova.net ([81.228.9.181])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ENimj-00069f-G5
	for mip6@ietf.org; Thu, 06 Oct 2005 23:20:38 -0400
Received: by av7-1-sn3.vrr.skanova.net (Postfix, from userid 502)
	id A7D5D38292; Fri,  7 Oct 2005 05:04:39 +0200 (CEST)
Received: from smtp3-1-sn3.vrr.skanova.net (smtp3-1-sn3.vrr.skanova.net
	[81.228.9.101])
	by av7-1-sn3.vrr.skanova.net (Postfix) with ESMTP id 8771C380F1
	for <mip6@ietf.org>; Fri,  7 Oct 2005 05:04:39 +0200 (CEST)
Received: from shiraz.levkowetz.com (81-224-201-50-no45.tbcn.telia.com
	[81.224.201.50])
	by smtp3-1-sn3.vrr.skanova.net (Postfix) with ESMTP id A446837E42
	for <mip6@ietf.org>; Fri,  7 Oct 2005 05:10:56 +0200 (CEST)
Received: from shiraz.local.levkowetz.com ([192.168.3.14]
	helo=81-224-201-50-no45.tbcn.telia.com)
	by shiraz.levkowetz.com with esmtp (Exim 4.52) id 1ENidL-0003yT-Eq
	for mip6@ietf.org; Fri, 07 Oct 2005 05:10:56 +0200
Content-Type: text/plain; charset=utf-8
To: mip6@ietf.org
From: Samita <tracker-mip6@mip4.org>
Date: Fri, 07 Oct 2005 03:10:55 +0000
MIME-Version: 1.0
Message-Id: <1128654655.41.0.528370111838.issue55@mip4.org>
X-Roundup-Name: Mip6 issue tracker
X-Roundup-Loop: hello
Content-Transfer-Encoding: quoted-printable
X-Helo-Check-Failed: Verification failed for HELO
	81-224-201-50-no45.tbcn.telia.com
X-SA-Exim-Connect-IP: 192.168.3.14
X-SA-Exim-Mail-From: roundup-admin@mip4.org
X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on 
	shiraz.levkowetz.com
X-Spam-Status: No, score=-103.8 required=2.5 tests=ALL_TRUSTED,AWL,BAYES_00,
	USER_IN_WHITELIST,X_HELO_CHECK_FAILED autolearn=ham version=3.0.4
X-SA-Exim-Version: 4.2 (built Thu, 03 Mar 2005 10:44:12 +0100)
X-SA-Exim-Scanned: Yes (on shiraz.levkowetz.com)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Content-Transfer-Encoding: quoted-printable
Subject: [Mip6] [issue55] Request to add BIGENIDAN LITTLE_ENDIAN by yoshfuji
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Mip6 issue tracker <tracker-mip6@mip4.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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org


New submission from Samita <Samita.Chakrabarti@eng.sun.com>:

>      #define  MIP6_PA_FLAG_MANAGED    0x8000
>      #define  MIP6_PA_FLAG_OTHER      0x4000
>=20
> Because MIP6_PA_FLAG_MANAGED and/or MIP6_PA_FLAG_OTHER are used
> for 16-bit-wide field (mip6_pa_flags_reserved), I believe that
> their definitions should be fixed as follows:


We have added comments on top of these defines :

  /* Mobile Prefix Advertisement Flags in network-byte order */
        #define  MIP6_PA_FLAG_MANAGED    0x8000
        #define  MIP6_PA_FLAG_OTHER      0x4000

 This is matched with the rest of the definitions. Is this OK?

----------
category: Technical
draft: draft-ietf-mip6-mipext-advapi
messages: 184
nosy: samita
priority: May fix
status: Text proposed
title: Request to add BIGENIDAN LITTLE_ENDIAN by yoshfuji

_________________________________________________
Mip6 issue tracker <tracker-mip6@mip4.org>
<http://www.mip4.org/issues/tracker/mip6/issue55>
_________________________________________________

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



From mip6-bounces@ietf.org Fri Oct 07 06:34:21 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ENpYS-0001ux-VX; Fri, 07 Oct 2005 06:34:20 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ENpYQ-0001uk-5B
	for mip6@megatron.ietf.org; Fri, 07 Oct 2005 06:34:18 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA09551
	for <mip6@ietf.org>; Fri, 7 Oct 2005 06:34:14 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ENphf-0007fn-Tg
	for mip6@ietf.org; Fri, 07 Oct 2005 06:43:53 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id j97AXf515523; Fri, 7 Oct 2005 12:33:41 +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
	j97AXffv072838; Fri, 7 Oct 2005 12:33:41 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200510071033.j97AXffv072838@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Christian Vogt <chvogt@tm.uka.de>
Subject: Re: [Mip6] Binding Lifetime for De-registrations 
In-reply-to: Your message of Thu, 06 Oct 2005 18:19:22 +0200.
	<43454E8A.4070503@tm.uka.de> 
Date: Fri, 07 Oct 2005 12:33:41 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: MIP6 <mip6@ietf.org>, TM-RO2 <tm-ro2@tm.uka.de>,
	Daniel Jungbluth <dj@danju.net>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   one question regarding the binding lifetime for Mobile IPv6
   de-registrations.
   
   Mobile nodes must set the Lifetime field in a de-registration Binding
   Update (BU) to zero, AND the home and care-of addresses must be equal.
   Correspondent nodes delete a binding if the Lifetime field of the BU is
   zero OR the home and care-of addresses are equal.
   
=> this is just an application of the well known principle.

   Assume that the mobile node sets the Lifetime field in a de-registration
   BU to a non-zero value.  What would be the Lifetime field in the
   corresponding Binding Acknowledgement (BA)?
   
=> the lifetime in a BA doesn't need to reflect the BU one (i.e.,
it is the granted lifetime, IMHO this means it should be <=).

   IMO, the Lifetime field in the BA should be zero for a de-registration
   regardless of the lifetime used in the BU.

=> the granted lifetime is clearly zero, so I agree.

   But RFC 3775 does not really answer this question.

=> the RFC is already far too long (:-).

Regards

Francis.Dupont@enst-bretagne.fr

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



From mip6-bounces@ietf.org Sun Oct 09 17:57:59 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EOjB9-0003cp-Ts; Sun, 09 Oct 2005 17:57:59 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EOjB9-0003cg-2W
	for mip6@megatron.ietf.org; Sun, 09 Oct 2005 17:57:59 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13025
	for <mip6@ietf.org>; Sun, 9 Oct 2005 17:57:56 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EOjKu-0007ww-VN
	for mip6@ietf.org; Sun, 09 Oct 2005 18:08:05 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id j99LvIC04920; Sun, 9 Oct 2005 23:57: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
	j99LvIdr084063; Sun, 9 Oct 2005 23:57:18 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200510092157.j99LvIdr084063@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: mip6@ietf.org
Date: Sun, 09 Oct 2005 23:57:18 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 40161b1d86420e0807d771943d981d25
Cc: vijay.devarapalli@nokia.com
Subject: [Mip6] comments about draft-ietf-mip6-ikev2-ipsec-03.txt
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

I'd still like to get an annex with the ASN.1 version of section 6 SPD
entries... But I have some other comments:

 In 3 page 3:
   The mobile node and the home agent must support the packet formats as

=> s/must/MUST/

 In 4.1 page 4:

   o  ESP encapsulation of the payload packets tunneled between the
      mobile node and the home agent MAY be supported and used.

=> I believe the document should restrict choices to only three options:
 - fine granularity: selector on MH types
 - medium granularity/RFC 3776 compatibility: selector on protocol = MH
 - coarse granularity: any protocol (here).

      configuration of home address as described in Section 8.  When the
      home agent receives a configuration payload with a CFG_REQUEST for
      INTERNAL_IP6_ADDR, it must reply with a valid home address for the
      mobile node.  The home agent could pick a home address from a

=> s/could/can/ ?

      local database or from a DHCPv6 server on the home link.

 In 4.3 page 7:

   o  When securing Binding Updates, Binding Acknowledgements, and
      prefix discovery, both the mobile nodes and the home agents MUST
      support and SHOULD use the Encapsulating Security Payload (ESP)
      [6] header in transport mode and MUST use a non-null payload
      authentication algorithm to provide data origin authentication,
      connectionless integrity and optional anti-replay protection.

=> s/optional/when possible/ ?

 In 4.4 page 8 and at many other places:

   o  The mobile node MUST use its Care-of Address as source address in
      protocol exchanges, when using dynamic keying.

=> s/Care-of Address/care-of address/

   o  If the mobile node has used IKEv2 to establish security
      associations with its home agent, it should follow the procedures
      discussed in Section 11.7.1 and 11.7.3 of the base specification
      [2] to determine whether the IKE endpoints can be moved or if IKE
      SA has to be re-established.

=> s/if IKE SA/if the IKE SA/ ?

   o  If the home agent has used IKEv2 to establish security
      associations with the mobile node, it should follow the procedures
      discussed in Section 10.3.1 and 10.3.2 of the base specification
      [2] to determine whether the IKE endpoints can be moved or if IKE
      SA has to be re-established.

=> s/if IKE SA/if the IKE SA/ ?

 In 5 page 8:

   This section describes the SPD and SAD entries that can be used to

=> I propose to add something explaining here and in section 6 that
the care-of address is the primary care-of address. BTW this is required
from time to time and it makes the code for tracking and updating SPD/SAD
far easier to write.

 In 5.1, 5.2 and 5.3 pages 9, 10 and 11: SPD-S entries work both ways
so there are twice the right number of SPD-S entries. I propose to copy
the section 6 stuff.

 In 5.4 page 11 I can't see a trace of the protocol=MH option...

 In 6.1 page 12 I propose to split the paragraph the same way than in
section 5 and to add something about the care-of address.

   The home agent should have named SPD entries per mobile node, based
   on the identity of the mobile node.  The identity of the mobile node
   is stored in the "Name" selector in the SPD [5].  The Home Address
   presented by the mobile node during the IKE negotiation is stored as
   the Remote IP address in the resultant IPsec security associations.
   The home agent MAY also have generic SPD entries to prevent mobility
   header traffic that requires IPsec protection from bypassing the
   IPsec filters.

=> s/Home Address/home address/ , s/Remote/remote/

   ...  The TSi and
   TSr payloads in the above examples will contain many other selectors
   apart from home_address_1.  For the sake of brevity, they are not
   shown here.

=> this statement is fully not understandable for me. I don't believe
the idea is to share SAs. Can you explain or remove this?

 In 6.1.2 page 13 and 6.1.4 page 15:

                       outer src addr = coa,
                       outer dst addr = coa,

=> s/coa/[primary_]care-of_address_1/

 In 6.1.3 page 14:

   In the examples shown above, the home address of the mobile node
   might not be available all the time.  When the mobile node acquires a
   new home address, it must add the address to the corresponding SPD
   entries.

   The TSi and TSr payloads in the above examples will contain many
   other selectors apart from home_address_1.  For brevity, they are not
   show here.

=> IMHO a reference to 6.1.1 is far better.

 In 6.1.4 page 15:

       mobile node SPD-S:
         - IF interface = IPv6 tunnel to home_agent_1 & proto = X

=> this is fully wrong. The SPD-S entry is really similar to the 6.1.2,
i.e., should be:

       mobile node SPD-S:
         - IF source = home_address_1 & destination = any & proto = any
         etc

and

         - IF destination = home_address_1 & proto = X &
              source = CN

=> this doesn't make any sense.

 In 6.2 page 15:

   The mobile node initiates an IKEv2 protocol exchange if the required
   security associations are not present.  The default mechanism used
   for mutual authentication is a shared secret between the mobile node
   and the home agent.  The home agent uses the identity of the mobile
   node to identify the corresponding shared secret.  If public key
   based mechanism is available, it should be the preferred mechanism
   for mutual authentication.  The home agent and the mobile node should
   use their private keys to generate the AUTH payload, when a public
   key based mechanism is used.  The mobile node and the home agent
   should use CERTREQ and CERT payloads if the identities need to be
   verified.  If the mobile node is configured with the home agent
   information including the public key that corresponds to the home
   agent, then the mobile node MAY exclude the CERTREQ payload in
   message 3.  Similarly, the home agent MAY exclude the CERTREQ payload
   in message 2, if it is configured with the mobile node information.

=> this paragraph is pretty bad. Here I try another text:

   The mobile node initiates an IKEv2 protocol exchange if the required
   security associations are not present.  A possible mechanism used
   for mutual authentication is a shared secret between the mobile node
   and the home agent.  The home agent uses the identity of the mobile
   node to identify the corresponding shared secret.  When a public key
   based mechanism is available, it should be the preferred mechanism
   for mutual authentication: private keys are used to generate the AUTH
   payload and identities are verified with certificate informations
   transmitted by CERT payloads or configured. If the mobile node is
   configured with the home agent information including its certificate,
   then the mobile node MAY exclude the CERTREQ payload in its IKE_AUTH
   third message.  Similarly, the home agent MAY exclude the CERTREQ payload
   in its IS_SA_INIT second message, if it is configured with the mobile node
   information.

   ...  The mobile node
   MAY use a range of selectors that includes the mobility message types
   for Binding Update and Binding Acknowledgement to use the same pair
   of IPsec security association for both messages.

=> s/MAY/SHOULD/ because I believe it is a very bad idea to have two
SA pairs.

   After the IKE_AUTH exchange completes, the mobile node initiates
   CREATE_CHILD_SA exchanges to negotiate additional security
   associations for protecting Return Routability signaling, Mobile
   Prefix Discovery messages and optionally payload traffic.

=> I propose:

   After the IKE_AUTH exchange completes, the mobile node initiates
   CREATE_CHILD_SA exchanges to negotiate additional security
   associations for protecting Return Routability signaling or
   optionally payload traffic, and Mobile Prefix Discovery messages.

   ...  If a correspondent node that
   is also a mobile node, initiates the return routability exchange,

=>

   ...  If a correspondent node, that
   is also a mobile node, initiates a return routability exchange,

   When PKI based authentication is used between the mobile node and the
   Home Agent, the identity presented by the mobile node in the IDi
   payload must correspond to the identity in the certificate fetched by
   the Home Agent.

=> s/fetched/got back/ ? My concern is the term "fetch" doesn't match the
case where the certificate is sent in a CERT payload.

   If the mobile node had used its home address in the IDi field,

=> s/If/When/ s/had used/uses/

   implementations are required to match the source address in the outer
   most IP header with the IP address in the IDi field [9].  This
   verification step, however, should be configurable [9].  With Mobile
   IPv6, this verification step will always fail because the source
   address in the outer most IP header is the care-of address and the IP

=> s/outer most// (this is about IKE messages which have no reason to
be encapsulated)

   address in the IDi field is the home address.  Therefore, this
   verification step should be skipped.

=> s/should be skipped/must be disabled/ (MUST?)

 In 6.3 page 18:

   ... on the mobile node
   when it receives the Binding acknowledgement sent by the home agent.

=> I discussed this with Shinta-san and the endpoint update is performed
by the mobile node after it sends the BU, i.e., the MN doesn't wait for
the BA. Cf draft-sugimoto-mip6-pfkey-migrate-01.txt 4.1.2 page 7.

   be initiated to re-establish the IKE SA.

=> s/the/a new/ ?

 In 7 page 19: I don't think it is a good idea to rely on [8].

 In 9 page 20:

   ...  The home agent MAY store the
   assigned home address in the SPD entries created for the mobile node.

=> I'd like to know how this can work if it doesn't store it (:-).

   The use of EAP for authenticating the mobile node to the home agent
   is described in Section 7.  This document recommends that if the EAP

=> "recommends" seems a bit strong.

   method used, supports mutual authentication, then EAP itself be used

=> syntax...

   for authenticating the home agent to the mobile node also.  This runs
   contrary to the recommendation in [4].

=> my concern is that I prefer the recommendation in [4]... and I can't
see why this recommendation should be bad here. Perhaps this is again
the wrong idea a mobile can't perform public key computations? I strongly
suggest to put this EAP extension consideration into another document
(a bootstrapping one for instance).

 In 12 pages 21 and 22: I believe some authors have in fact only the
editor role, this should be reflected.

 In 12.2 page 22:

   [14]  Sugimoto, S., "PF_KEY Extension as an Interface between Mobile
         IPv6 and IPsec/IKE", draft-sugimoto-mip6-pfkey-migrate-01 (work
         in progress), September 2005.

=> me and Masahide Nakamura are co-authors.

Regards

Francis.Dupont@enst-bretagne.fr

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



From mip6-bounces@ietf.org Mon Oct 10 05:50:23 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EOuIZ-0008Ti-MR; Mon, 10 Oct 2005 05:50:23 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EOuIX-0008Ta-PU
	for mip6@megatron.ietf.org; Mon, 10 Oct 2005 05:50:21 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA28462
	for <mip6@ietf.org>; Mon, 10 Oct 2005 05:50:19 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EOuSP-0007ns-3L
	for mip6@ietf.org; Mon, 10 Oct 2005 06:00:34 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id j9A9nmc09097; Mon, 10 Oct 2005 11:49:48 +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
	j9A9nmTV086277; Mon, 10 Oct 2005 11:49:48 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200510100949.j9A9nmTV086277@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Basavaraj.Patil@nokia.com
Subject: Re: [Mip6] Timeslot requests for MIP6 WG agenda at IETF64 
In-reply-to: Your message of Thu, 06 Oct 2005 12:08:19 CDT.
	<456943D540CFC14A8D7138E64843F85301CFD7B4@daebe101.NOE.Nokia.com> 
Date: Mon, 10 Oct 2005 11:49:48 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   If you need a timeslot on the MIP6 WG agenda, please send
   a request to the chairs with the following information:
   
   1. I-D title

=> draft-dupont-mip6-dhaadharmful-00.txt
(to summary current Dynamic Home Agent Address Discovery can be made
secure so I propose to replace it by the DNS SRV RR of
draft-ietf-mip6-bootstrapping-split-00.txt).

   2. Amount of time requested

=> 5 mn of discussion about the idea (adopt or not, if yes how
to proceed). I strongly suggest to begin on the mailing list.

   3. Is the I-D within the scope of the WG charter? If not why is it
   important to discuss this at the WG meeting?
   
=> current DHAAD is in RFC 3775 so the I-D is in the scope.

Thanks

Francis.Dupont@enst-bretagne.fr

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



From mip6-bounces@ietf.org Mon Oct 10 10:46:10 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EOyuo-0006OB-PD; Mon, 10 Oct 2005 10:46:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EOyue-0006Nr-K6
	for mip6@megatron.ietf.org; Mon, 10 Oct 2005 10:46:09 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15209
	for <mip6@ietf.org>; Mon, 10 Oct 2005 10:45:58 -0400 (EDT)
Received: from cluster-d.mailcontrol.com ([217.69.20.190]
	helo=rly02d.srv.mailcontrol.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EOz4Z-0007CI-JB
	for mip6@ietf.org; Mon, 10 Oct 2005 10:56:16 -0400
Received: from hhe500-02.hbg.de.pan.eu (gate.eu.panasonic.com [194.173.20.12])
	by rly02d.srv.mailcontrol.com (MailControl) with SMTP id
	j9AEjguD008825; Mon, 10 Oct 2005 15:45:42 +0100
Received: from eundadmi01.pan.eu(10.100.96.64) by hhe500-02.hbg.de.pan.eu via
	smtp id 58dd_25b22ee2_399d_11da_848f_0030482aac25;
	Mon, 10 Oct 2005 16:50:05 +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 2005101016453918-122958 ;
	Mon, 10 Oct 2005 16:45:39 +0200 
Received: from localhost ([127.0.0.1]) by VPN-MRelay-01.PRDCG.Panasonic.de;
	Mon, 10 Oct 2005 16:47:42 +0200
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Subject: RE: [Mip6] review of draft-ietf-mip6-bootstrapping-split-00.txt
Thread-Topic: [Mip6] review of draft-ietf-mip6-bootstrapping-split-00.txt
Thread-Index: AcXKmWxA/nl8gGx0Qvag8ZCkFZUNKAC7CCGw
To: "James Kempf" <Kempf@docomolabs-usa.com>
Message-ID: <4D2F935F08D41A4C8866693F4F0D7C4F58DAEC@lan-ex-01.panasonic.de>
Date: Mon, 10 Oct 2005 16:45:34 +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-05-40-00 (www.mailcontrol.com) on 10.68.0.112
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0770535483960d190d4a0d020e7060bd
Content-Transfer-Encoding: quoted-printable
Cc: Gerardo Giaretta <Gerardo.Giaretta@TILAB.COM>, mip6@ietf.org,
	Vijay Devarapalli <vijayd@iprg.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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Hi James,

please see comments inline.

> jak>> The only way an eavesdropper could know, from a=20
> DNS-registered home=20
> address obtained through bootstrapping, that a MN is at a particular=20
> location is:
>=20
> 1) The eavesdropper has been keeping track of the DNS-registered home=20
> address in the past and has seen that the newly registered address is=20
> different,
> 2) The eavesdropper knows the victim's home MSP, either from previous=20
> addresses, or from some other way (note: the victim's FQDN=20
> doesn't provide=20
> any information in general about the MSP, because the FQDN is=20
> handled by the=20
> MSA, which might be a separate administrative entity),
> 2) The eavesdropper knows that the newly registered address=20
> belongs to an=20
> MSP that is not the victim's home MSP and that the current=20
> MSP routinely=20
> uses local home agents,

Can you clarify why the eavesdropper needs to know the home MSP of the
victim and/or that the newly registered address is different?

IMO, it is sufficient that the victim uses a DNS-registered HoA of a
nearby HA (e.g., to improve routing efficiency) and that the
eavesdropper knows that this HA is (currently) nearby for the victim. In
this case, the eavesdropper can find out the approx. location by
querying the victim's FQDN in DNS. If the victim constantly obtains
DNS-registered HoAs of "the most nearby" HAs when moving, the
eavesdropper can track the victim's movement. In both cases, I don't see
why the eavesdropper would need to know the victim's home MSP. IMO, it
would only need to know the victim's FQDN and the victim's HA selection
policy. How easy it is for the eavesdropper to determine the victim's HA
selection policy is another issue, but relying on secrecy of the policy
would remind me on "security through obscurity".

Or do you mean that the eavesdropper might not be sure whether the
victim is *currently* nearby to the HA. In the latter case (where DNS is
constantly updated with the most nearby HA) this is trivial, in the
former case the eavesdropper can possibly be more certain that the HA is
still nearby for the victim when the HoA in DNS has recently changed,
but that depends on the movement pattern of the MN. However, I guess
keeping track of an DNS entry is not difficult for an eavesdropper.=20

BTW, I called the HA "nearby" because it even doesn't need to be local.
If the serving access network provider does not provide local HA
bootstrapping service, the MN could select an HA of a nearby network,
i.e., the MSP would be different from ASP and different from home MSP.
This can improve routing efficiency if the home MSP is far away and the
ASP doesn't provide local HA bootstrapping for this user. For instance,
if a user from US roams to Vodafone Germany and Vodafone Germany does
not support local HA bootstrapping for this user, the user may bootstrap
with an HA of T-Mobile Germany to still improve routing efficiency. It
could, e.g., discover an HA in Germany using country code suffixes and a
list of MSPs (e.g., "ha.t-mobile.de", "ha.vodafone.de",...).=20


>=20
> In addition, the granularity of the information obtained from=20
> the home=20
> address depends on the topological to geographical coverage=20
> of the home=20

I totally agree. That's reflected in the text.

> agent. So if the coverage area is, say, the entire Bay Area=20
> in California,=20
> the eavesdropper doesn't get a whole heck of a lot of=20
> information about=20
> where the person is.

I think whether this scenario would be an issue for the user depends on
the location privacy requirements of the user. At least some users don't
even want to disclose whether they are currently on a trip in another
country, e.g., because this can provide a hint to burglars.

>=20
> jak>> My point is that the eavesdropper needs a lot of additional=20
> information about the victim and the MSPs that the victim is=20
> using before it=20
> can conclude anything about the location. If you want to put=20
> all these=20
> conditions into the text, I think it would make the description more=20
> accurate.

see comment above

>=20
> Can
> you agree to the following sentence (and we drop the "Thus..revealed"
> sentence, as you suggested)?
>=20
>    "Second, the mobile
>    node (if using reverse tunneling) will effectively appear to be at
>    a fixed topological location in the mobility service provider's
>    as long as it does not bootstrap again with a different home
>    agent in a different network and request DNS update subsequently."
>=20
> jak>> That seems OK.
>=20
> > interoperability. If we decide in favor of removing, then I
> > think we should
> > save this text and put it into the integrated scenerio draft.
>=20
> I agree that the potential location privacy issue with local=20
> HAs should
> be described in the sec cons sections in the integrated=20
> scenario draft.
> But even if the text about location-dependent HA naming is=20
> removed from
> the split scenario draft, location-dependent HA discovery may still be
> possible to some extent by using country code suffixes (the=20
> location is
> of course much less accurate). Depending on how strict the requirement
> for location privacy is, an issue may still exist. If, for instance, a
> user from US is on a business trip in Europe and that user roams to
> Vodafone Germany, it may discover an HA for bootstrapping using
> "ha1.vodafone.de" or "_mip6._ipv6.vodafone.de". When updating DNS with
> the new HoA, that may give a hint that the user is currently=20
> in Germany.
>=20
> jak>> If Vodafone has no local HA service in Germany, then=20
> the user will=20
> always use it's home MSP in the US. So there's no issue.

As I said above, the user may also use another nearby MSP to improve
routing efficiency and various ways to discover a more or less nearby HA
may exist, e.g., by using country code suffixes.

> jak>> We're currently discussing among the authors about what=20
> to put in the=20
> draft regarding local home agent assignment. If there is no=20
> text specifying=20
> how to do it, then I think we don't need to say anything. But=20
> I think we do=20
> need to say something in the integrated scenario draft,=20
> because it will be=20
> possible there.

I think the issue potentially exists once location-dependent HA
discovery is possible with the solution (plus DNS updates, of course)
and this may be possible (at least to some extent) with the DNS-based
discovery procedure described in the split scenario draft even without
the text about local home agent assigment (e.g., by using country code
suffixes). Hence, I would prefer to add text about this issue in the
integrated scenario draft AND the split scenario draft, even in case you
decide to remove the text about local home agent assigment.

Regards,

Kilian


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



From mip6-bounces@ietf.org Mon Oct 10 12:37:17 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EP0eL-0001K1-Mu; Mon, 10 Oct 2005 12:37:17 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EP0eK-0001Js-8T
	for mip6@megatron.ietf.org; Mon, 10 Oct 2005 12:37:16 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04765
	for <mip6@ietf.org>; Mon, 10 Oct 2005 12:37:13 -0400 (EDT)
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EP0oF-00015N-SE
	for mip6@ietf.org; Mon, 10 Oct 2005 12:47:32 -0400
Message-ID: <10a301c5cdb8$dddd1fa0$196115ac@dcml.docomolabsusa.com>
From: "James Kempf" <Kempf@docomolabs-usa.com>
To: "Kilian Weniger" <Kilian.Weniger@eu.panasonic.com>
References: <4D2F935F08D41A4C8866693F4F0D7C4F58DAEC@lan-ex-01.panasonic.de>
Subject: Re: [Mip6] review of draft-ietf-mip6-bootstrapping-split-00.txt
Date: Mon, 10 Oct 2005 09:37:12 -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.0 (/)
X-Scan-Signature: 16c9da4896bf5539ae3547c6c25f06a0
Content-Transfer-Encoding: 7bit
Cc: Gerardo Giaretta <Gerardo.Giaretta@TILAB.COM>, mip6@ietf.org,
	Vijay Devarapalli <vijayd@iprg.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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

> jak>> The only way an eavesdropper could know, from a
> DNS-registered home
> address obtained through bootstrapping, that a MN is at a particular
> location is:
>
> 1) The eavesdropper has been keeping track of the DNS-registered home
> address in the past and has seen that the newly registered address is
> different,
> 2) The eavesdropper knows the victim's home MSP, either from previous
> addresses, or from some other way (note: the victim's FQDN
> doesn't provide
> any information in general about the MSP, because the FQDN is
> handled by the
> MSA, which might be a separate administrative entity),
> 2) The eavesdropper knows that the newly registered address
> belongs to an
> MSP that is not the victim's home MSP and that the current
> MSP routinely
> uses local home agents,

Can you clarify why the eavesdropper needs to know the home MSP of the
victim and/or that the newly registered address is different?

IMO, it is sufficient that the victim uses a DNS-registered HoA of a
nearby HA (e.g., to improve routing efficiency) and that the

jak>> Given that the attacker only sees the current DNS entry (knows nothing 
more) how is to determine if the HA and HoA are "nearby" to the victim or 
not? Unless the attacker knows somehow specifically the subnet prefixes 
assigned to home addresses by the victim's customary MSP, how can the 
attacker determine that the current HoA is somehow different? And, again, 
even if the attacker knows the prefixes assigned by the customary MSP and it 
sees an HoA with a prefix not in that set, how can the attacker determine 
that the victim is in a particular geographical location when it sees that 
prefix? Returning to my previous example, the victim might be using an MSP 
in Tucson today, though it usually uses one in Palo Alto, but the victim 
might actually be in Chicago and using that MSP because it was the only one 
offered on the hotspot Web page.

The attacker would have to know a) the customary MSP of the victim so it can 
compare the home prefix to whatever the currently registered prefix is b) 
that the current MSP provides local home agent service so that it can tell 
that the victim must be using an MSP with local home agent c) that the HoA 
is from a home agent that is used to provide local home agent service so it 
can tell whether the victim is in the geographical area or using the HA 
remotely d) a detailed topological to geographical mapping that maps the 
subnets of the home MSPs to geographical areas so that it can work out the 
geographical location of the victim.

jak>> I belive there is a threat, and I think it worthwhile to describe it. 
I think the amount of information required (a-d) is rather large, but not 
undoable for a dedicated attacker.


eavesdropper knows that this HA is (currently) nearby for the victim. In
this case, the eavesdropper can find out the approx. location by
querying the victim's FQDN in DNS. If the victim constantly obtains
DNS-registered HoAs of "the most nearby" HAs when moving, the

jak>> There is nothing in RFC 3775 to allow changing HAs frequently, and 
bootstrapping isn't intended to enable this either.

eavesdropper can track the victim's movement. In both cases, I don't see
why the eavesdropper would need to know the victim's home MSP. IMO, it
would only need to know the victim's FQDN and the victim's HA selection
policy. How easy it is for the eavesdropper to determine the victim's HA
selection policy is another issue, but relying on secrecy of the policy
would remind me on "security through obscurity".

Or do you mean that the eavesdropper might not be sure whether the
victim is *currently* nearby to the HA. In the latter case (where DNS is
constantly updated with the most nearby HA) this is trivial, in the
former case the eavesdropper can possibly be more certain that the HA is
still nearby for the victim when the HoA in DNS has recently changed,
but that depends on the movement pattern of the MN. However, I guess
keeping track of an DNS entry is not difficult for an eavesdropper.

jak>> See above.

BTW, I called the HA "nearby" because it even doesn't need to be local.
If the serving access network provider does not provide local HA
bootstrapping service, the MN could select an HA of a nearby network,
i.e., the MSP would be different from ASP and different from home MSP.
This can improve routing efficiency if the home MSP is far away and the
ASP doesn't provide local HA bootstrapping for this user. For instance,
if a user from US roams to Vodafone Germany and Vodafone Germany does
not support local HA bootstrapping for this user, the user may bootstrap
with an HA of T-Mobile Germany to still improve routing efficiency. It
could, e.g., discover an HA in Germany using country code suffixes and a
list of MSPs (e.g., "ha.t-mobile.de", "ha.vodafone.de",...).


>
> In addition, the granularity of the information obtained from
> the home
> address depends on the topological to geographical coverage
> of the home

I totally agree. That's reflected in the text.

> agent. So if the coverage area is, say, the entire Bay Area
> in California,
> the eavesdropper doesn't get a whole heck of a lot of
> information about
> where the person is.

I think whether this scenario would be an issue for the user depends on
the location privacy requirements of the user. At least some users don't
even want to disclose whether they are currently on a trip in another
country, e.g., because this can provide a hint to burglars.

jak>> Yes, that's true. This should be mentioned. However, note that there 
are other ways that an attacker could derive this kind of information, for 
example, the round trip time of the packets. Some of these can't be 
eliminated.

>
> jak>> My point is that the eavesdropper needs a lot of additional
> information about the victim and the MSPs that the victim is
> using before it
> can conclude anything about the location. If you want to put
> all these
> conditions into the text, I think it would make the description more
> accurate.

see comment above

>
> Can
> you agree to the following sentence (and we drop the "Thus..revealed"
> sentence, as you suggested)?
>
>    "Second, the mobile
>    node (if using reverse tunneling) will effectively appear to be at
>    a fixed topological location in the mobility service provider's
>    as long as it does not bootstrap again with a different home
>    agent in a different network and request DNS update subsequently."
>
> jak>> That seems OK.
>
> > interoperability. If we decide in favor of removing, then I
> > think we should
> > save this text and put it into the integrated scenerio draft.
>
> I agree that the potential location privacy issue with local
> HAs should
> be described in the sec cons sections in the integrated
> scenario draft.
> But even if the text about location-dependent HA naming is
> removed from
> the split scenario draft, location-dependent HA discovery may still be
> possible to some extent by using country code suffixes (the
> location is
> of course much less accurate). Depending on how strict the requirement
> for location privacy is, an issue may still exist. If, for instance, a
> user from US is on a business trip in Europe and that user roams to
> Vodafone Germany, it may discover an HA for bootstrapping using
> "ha1.vodafone.de" or "_mip6._ipv6.vodafone.de". When updating DNS with
> the new HoA, that may give a hint that the user is currently
> in Germany.
>
> jak>> If Vodafone has no local HA service in Germany, then
> the user will
> always use it's home MSP in the US. So there's no issue.

As I said above, the user may also use another nearby MSP to improve
routing efficiency and various ways to discover a more or less nearby HA
may exist, e.g., by using country code suffixes.

> jak>> We're currently discussing among the authors about what
> to put in the
> draft regarding local home agent assignment. If there is no
> text specifying
> how to do it, then I think we don't need to say anything. But
> I think we do
> need to say something in the integrated scenario draft,
> because it will be
> possible there.

I think the issue potentially exists once location-dependent HA
discovery is possible with the solution (plus DNS updates, of course)
and this may be possible (at least to some extent) with the DNS-based
discovery procedure described in the split scenario draft even without
the text about local home agent assigment (e.g., by using country code
suffixes). Hence, I would prefer to add text about this issue in the
integrated scenario draft AND the split scenario draft, even in case you
decide to remove the text about local home agent assigment.

jak>> Why are country codes an issue? The DNS name for the MN is always 
fixed, otherwise, potential correspondents can't find it. Thus, if I am 
roaming in Germany and my home MSA is in the US, my FQDN always has the 
".us" country code. Even if I am using a local home agent, the name doesn't 
change. And the HA FQDN is never exposed to the correspondent.

jak>> Regarding putting this text in the draft, I believe we have agreed 
that the split draft will only have a very general statement about local 
HAs, and that any further discussion is out of scope. So it seems to me 
better to put it in the integrated draft, where a more detailed discussion 
will occur.

            jak




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



From mip6-bounces@ietf.org Mon Oct 10 16:06:28 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EP3um-0003Ch-Ka; Mon, 10 Oct 2005 16:06:28 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EP3ul-0003Br-5Q
	for mip6@megatron.ietf.org; Mon, 10 Oct 2005 16:06:27 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21237
	for <mip6@ietf.org>; Mon, 10 Oct 2005 16:06:20 -0400 (EDT)
Received: from dns2.tilab.com ([163.162.42.5])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EP44b-0008LZ-6Z
	for mip6@ietf.org; Mon, 10 Oct 2005 16:16:40 -0400
Received: from iowa2k01b.cselt.it ([163.162.242.202])
	by dns2.cselt.it (PMDF V6.1 #38895)
	with ESMTP id <0IO500J1KUI44B@dns2.cselt.it> for mip6@ietf.org; Mon,
	10 Oct 2005 22:06:04 +0200 (MEST)
Received: from EXC01B.cselt.it ([163.162.4.199]) by iowa2k01b.cselt.it with
	Microsoft SMTPSVC(6.0.3790.211); Mon, 10 Oct 2005 22:03:49 +0200
Date: Mon, 10 Oct 2005 22:06:03 +0200
From: Gerardo Giaretta <Gerardo.Giaretta@TILAB.COM>
Subject: RE: [Mip6] [draft-ietf-mip6-bootstrapping-split-00] Issue 53
To: mip6@ietf.org
Message-id: <DA62A6E0CDD1B34A84557FF1AC850C57016E9BCB@EXC01B.cselt.it>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.3790.326
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: quoted-printable
Importance: normal
Priority: normal
Thread-Topic: [Mip6] [draft-ietf-mip6-bootstrapping-split-00] Issue 53
Thread-Index: AcXKCdxhx2hw+cHJQvOuCteusVv1OADy9ZEw
Content-class: urn:content-classes:message
X-OriginalArrivalTime: 10 Oct 2005 20:03:49.0125 (UTC)
	FILETIME=[BA89D350:01C5CDD5]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4b66a1e94d7d92973ece9e5da449ff80
Content-Transfer-Encoding: quoted-printable
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Based on discussion among authors, the proposed text for section 5.1.1 =
to solve this issue is the following:

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

5.1.1. DNS lookup by Home Agent Name

In this case, the Mobile Node is configured with the Fully Qualified =
Domain Name of the Home Agent. As an example, the Mobile Node could be =
configured with the name "ha1.example.com", where "example.com" is the =
domain name of the MSP granting the mobility service.=20

The Mobile Node constructs a DNS request, by setting the QNAME to the =
name of the Home Agent. The request has QTYPE set to 'AAAA', so that the =
DNS server sends the IPv6 address of the Home Agent. Once the DNS server =
replies to this query, the Mobile Node knows its Home Agent address and =
can run IKEv2 in order to set up an IPsec SA and get a Home Address.

Additionally, the ability to provide a mobile node with a localized home =
agent (e.g. on the visited link) can help to optimize handover =
signaling. There are a variety of ways this can be achieved in an =
interoperable way. One way is to provision the mobile node with an FQDN =
for a local home agent when it configures for the local link. Another =
way is to specify an interoperable naming convention for constructing =
home agent FQDNs based on location. For example, an operator might =
assign the FQDN "ha.locationA.operator.com" to the Home Agent located in =
"location A" and the FQDN "ha.locationB.operator.com" to the Home Agent =
located in "location B". If the Mobile Node wants to use a Home Agent =
located in "location A", it will set the QNAME to =
"ha.locationA.operator.com" in the DNS request. The exact way in which =
localized Home Agents are configured is out of scope for this draft.

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

I think we can consider the issue closed now. Please let me know if you =
have problem with that.

--Gerardo


> -----Original Message-----
> From: Yoshihiro Ohba [mailto:yohba@tari.toshiba.com]=20
> Sent: gioved=EC 6 ottobre 2005 2.05
> To: Vijay Devarapalli
> Cc: Yoshihiro Ohba; Gerardo Giaretta; mip6@ietf.org
> Subject: Re: [Mip6] [draft-ietf-mip6-bootstrapping-split-00] Issue 53
>=20
> Hi Vijay,
>=20
> On Wed, Oct 05, 2005 at 04:33:58PM -0700, Vijay Devarapalli wrote:
> > Yoshihiro Ohba wrote:
> > > As I don't believe we can come up with an acceptable=20
> canonical name
> > > for local HA naming, I prefer solution 1.  Also, does the=20
> following
> > > example in the first paragraph of section 5.1.1 give much=20
> insights to
> > > implementors to understand how to configure an HA name? =20
> If not, I'd
> > > prefer just removing it.
> > >=20
> > > "
> > >   As an example, the Mobile Node could be configured with the name
> > >   "ha1.example.com", where "example.com" is the domain=20
> name of the MSP
> > >   granting the mobility service.
> >=20
> > just to make sure. Yoshi, you are saying the entire
> > section 5.1.1 needs to be removed.=20
>=20
> No.  My opinion is:
>=20
> - Section 5.1.1 should exist.
>=20
> - The last paragraph of section 5.1.1 is not needed.
>=20
> - Importance of the last sentence of the first paragraph (quoted
> above) of section 5.1.1 is questionable.  (I know this part is not
> what is being discussed here, but just a comment.)
>=20
> Regards,
>=20
> Yoshihiro Ohba
>=20
>=20
> > not just the last
> > paragraph which describes HA lookup by location (which
> > is what is being discussed here).
> >=20
> > Vijay
> >=20
> > > "
> > >=20
> > > Regards,
> > >=20
> > > Yoshihiro Ohba
> > >=20
> > > On Wed, Oct 05, 2005 at 07:29:24PM +0200, Gerardo Giaretta wrote:
> > >=20
> > >>I would like to hear your thoughts about issue #53 in
> > >>draft-ietf-mip6-bootstrapping-split-00.=20
> > >>
> > >>The current version of the draft states:
> > >>
> > >>        Additionally, it could be useful to provide an=20
> ability for the
> > >>Mobile=20
> > >>        Node to discover a Home Agent placed in a=20
> particular location
> > >>(e.g.=20
> > >>        on the visited link). In order to achieve this,=20
> the Mobile Node
> > >>must=20
> > >>        be able to construct a DNS request such that the=20
> DNS server will
> > >>be=20
> > >>        able to reply with a Home Agent from the=20
> requested location.
> > >>This can=20
> > >>        be accomplished by using a specific  naming=20
> convention for the
> > >>FQDNs=20
> > >>        of the Home Agents. As an example, an operator=20
> might assign the
> > >>FQDN=20
> > >>        "ha.locationA.operator.com" to the Home Agent located in
> > >>"location A"=20
> > >>        and the FQDN "ha.locationB.operator.com" to the Home Agent
> > >>located in=20
> > >>        "location B". If the Mobile Node wants to use a Home Agent
> > >>located in=20
> > >>        "location A", it will set the QNAME to
> > >>"ha.locationA.operator.com" in=20
> > >>        the DNS request.        =20
> > >>
> > >>In his review, Jari mentioned:
> > >>"Possible, but the description is mostly handwaving and=20
> would probably
> > >>benefit from a more generic solution in any case. Suggest
> > >>removing this"
> > >>
> > >>Based on the discussion we've had so far, we have two=20
> possible options:
> > >>
> > >>1. remove the text and do not provide a way in
> > >>draft-ietf-mip6-bootstrapping-split to identify whether=20
> or not the HA is
> > >>local (based on Jari comment)
> > >>
> > >>2. define a canonical local HA naming convention for=20
> interoperability
> > >>
> > >>Please provide your comments.
> > >>
> > >>
> > >>--Gerardo
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>Gruppo Telecom Italia - Direzione e coordinamento di=20
> Telecom Italia S.p.A.
> > >>
> >=20
> =
>>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> > >>CONFIDENTIALITY NOTICE
> > >>This message and its attachments are addressed solely to=20
> the persons
> > >>above and may contain confidential information. If you=20
> have received
> > >>the message in error, be informed that any use of the=20
> content hereof
> > >>is prohibited. Please return it immediately to the sender=20
> and delete
> > >>the message. Should you have any questions, please send=20
> an e_mail to=20
> > >>MailAdmin@tilab.com. Thank you
> >=20
> =
>>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> > >>
> > >>_______________________________________________
> > >>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
>=20


Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia =
S.p.A.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
CONFIDENTIALITY NOTICE
This message and its attachments are addressed solely to the persons
above and may contain confidential information. If you have received
the message in error, be informed that any use of the content hereof
is prohibited. Please return it immediately to the sender and delete
the message. Should you have any questions, please send an e_mail to
MailAdmin@tilab.com. Thank you
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

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



From mip6-bounces@ietf.org Tue Oct 11 04:37:56 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EPFe0-0002K3-45; Tue, 11 Oct 2005 04:37:56 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EPFdw-0002HN-34
	for mip6@megatron.ietf.org; Tue, 11 Oct 2005 04:37:54 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA08032
	for <mip6@ietf.org>; Tue, 11 Oct 2005 04:37:49 -0400 (EDT)
Received: from cluster-d.mailcontrol.com ([217.69.20.190]
	helo=rly25d.srv.mailcontrol.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EPFnx-0000vM-K3
	for mip6@ietf.org; Tue, 11 Oct 2005 04:48:17 -0400
Received: from hhe500-02.hbg.de.pan.eu (gate.eu.panasonic.com [194.173.20.12])
	by rly25d.srv.mailcontrol.com (MailControl) with SMTP id
	j9B8bajD012816; Tue, 11 Oct 2005 09:37:36 +0100
Received: from eundadmi01.pan.eu(10.100.96.64) by hhe500-02.hbg.de.pan.eu via
	smtp id 7798_e5ca2bc2_3a32_11da_928c_0030482aac25;
	Tue, 11 Oct 2005 10:42:02 +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 2005101110372702-149792 ;
	Tue, 11 Oct 2005 10:37:27 +0200 
Received: from localhost ([127.0.0.1]) by VPN-MRelay-01.PRDCG.Panasonic.de;
	Tue, 11 Oct 2005 10:39:29 +0200
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Subject: RE: [Mip6] review of draft-ietf-mip6-bootstrapping-split-00.txt
Thread-Topic: [Mip6] review of draft-ietf-mip6-bootstrapping-split-00.txt
Thread-Index: AcXNuOUfMELq12tCQp6q08wdVpRsQgAfF1Ug
To: "James Kempf" <Kempf@docomolabs-usa.com>
Message-ID: <4D2F935F08D41A4C8866693F4F0D7C4F58DB38@lan-ex-01.panasonic.de>
Date: Tue, 11 Oct 2005 10:37:21 +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-05-40-00 (www.mailcontrol.com) on 10.68.0.135
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Content-Transfer-Encoding: quoted-printable
Cc: Gerardo Giaretta <Gerardo.Giaretta@TILAB.COM>, mip6@ietf.org,
	Vijay Devarapalli <vijayd@iprg.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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org


> jak>> Given that the attacker only sees the current DNS entry=20
> (knows nothing=20
> more) how is to determine if the HA and HoA are "nearby" to=20
> the victim or=20
> not? Unless the attacker knows somehow specifically the=20

In one example I have given in the last emails the eavesdropper
additionally knows the victim's HA selection policy and this policy is
"always using nearby HAs". IMO, no additional information such as
victim's customary MSP would be needed in this scenario (of course, it
is again assumed that HoAs are DNS-registered).=20

Note that this HA selection policy is not far-fetched because it can
provide good routing efficiency in bi-directional tunneling mode. Also
note that for good routing efficiency of CN-initiated sessions,
DNS-registered HoAs are required.

> subnet prefixes=20
> assigned to home addresses by the victim's customary MSP, how can the=20
> attacker determine that the current HoA is somehow different?=20

Again, if the victim's policy is "always using nearby HAs" (this implies
that the victim only uses its customary MSP if it is close to this MSP)
and the eavesdopper is aware of that, the eavesdropper knows that the
new HA is nearby. I agree that in case the current ASP does not provide
local HA service, the location information is less accurate (as you
mentioned, an eavesdropper may be aware of the local HA support of
ASPs). In this case the MN could bootstrap with an HA of a nearby MSP
(In the worst case "nearby" may mean in the same country).

> And, again,=20
> even if the attacker knows the prefixes assigned by the=20
> customary MSP and it=20
> sees an HoA with a prefix not in that set, how can the=20
> attacker determine=20
> that the victim is in a particular geographical location when=20
> it sees that=20
> prefix? Returning to my previous example, the victim might be=20

see above

> jak>> I belive there is a threat, and I think it worthwhile=20
> to describe it.=20

I agree.

> I think the amount of information required (a-d) is rather=20
> large, but not=20
> undoable for a dedicated attacker.

I think there are scenarios where less information is needed (see
above).

> jak>> There is nothing in RFC 3775 to allow changing HAs=20
> frequently, and=20
> bootstrapping isn't intended to enable this either.

I agree to this, but it is a different question whether a solution
*intends* to enable something or whether it enables something. ;)
So far, I didn't see anything in the split scenario draft that prevents
MNs from bootstrapping with different HAs more or less frequently (at
least frequent enough that enables the policy "always using nearby
HAs").

> jak>> Why are country codes an issue? The DNS name for the MN=20
> is always=20
> fixed, otherwise, potential correspondents can't find it.=20
> Thus, if I am=20
> roaming in Germany and my home MSA is in the US, my FQDN=20
> always has the=20
> ".us" country code. Even if I am using a local home agent,=20
> the name doesn't=20
> change. And the HA FQDN is never exposed to the correspondent.

No, I'm not talking about MN's FQDN, I'm talking about HA's FQDN. The
issue is that location-dependent HA discovery is possible to some extent
by using the country code suffix of an HA's FQDN. If, for example, the
user roams from US to Germany, it can discover an HA located in Germany
by querying, e.g., "ha.t-mobile.de" or "ha.vodafone.de" (or
"_mip6._ipv6.vodafone.de"). This HA would be "nearby", but not
necessarily "local".


Kilian



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



From mip6-bounces@ietf.org Tue Oct 11 05:43:47 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EPGfi-0008Jm-V7; Tue, 11 Oct 2005 05:43:46 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EPGfh-0008Je-3E
	for mip6@megatron.ietf.org; Tue, 11 Oct 2005 05:43:45 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA10546
	for <mip6@ietf.org>; Tue, 11 Oct 2005 05:43:42 -0400 (EDT)
Received: from cluster-d.mailcontrol.com ([217.69.20.190]
	helo=rly22d.srv.mailcontrol.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EPGpk-0002TS-Ux
	for mip6@ietf.org; Tue, 11 Oct 2005 05:54:10 -0400
Received: from hhe500-02.hbg.de.pan.eu (gate.eu.panasonic.com [194.173.20.12])
	by rly22d.srv.mailcontrol.com (MailControl) with SMTP id
	j9B9hVDo022804; Tue, 11 Oct 2005 10:43:31 +0100
Received: from eundadmi01.pan.eu(10.100.96.64) by hhe500-02.hbg.de.pan.eu via
	smtp id 77b8_1b733cc4_3a3c_11da_948b_0030482aac25;
	Tue, 11 Oct 2005 11:47:59 +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 2005101111432816-155012 ;
	Tue, 11 Oct 2005 11:43:28 +0200 
Received: from localhost ([127.0.0.1]) by VPN-MRelay-01.PRDCG.Panasonic.de;
	Tue, 11 Oct 2005 11:45:32 +0200
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Subject: FW: [Mip6] [draft-ietf-mip6-bootstrapping-split-00] Issue 53
Thread-Topic: [Mip6] [draft-ietf-mip6-bootstrapping-split-00] Issue 53
Thread-Index: AcXKCdxhx2hw+cHJQvOuCteusVv1OADy9ZEwABrpDSAAAak1sA==
To: "Gerardo Giaretta" <Gerardo.Giaretta@TILAB.COM>
Message-ID: <4D2F935F08D41A4C8866693F4F0D7C4F58DB5C@lan-ex-01.panasonic.de>
Date: Tue, 11 Oct 2005 11:43:24 +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-05-40-00 (www.mailcontrol.com) on 10.68.0.132
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Content-Transfer-Encoding: quoted-printable
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Hello Gerardo,

> 5.1.1. DNS lookup by Home Agent Name
>
...
> The Mobile Node constructs a DNS request, by setting the=20
> QNAME to the name of the Home Agent. The request has QTYPE=20
> set to 'AAAA', so that the DNS server sends the IPv6 address=20
> of the Home Agent. Once the DNS server replies to this query,=20
> the Mobile Node knows its Home Agent address and can run=20
> IKEv2 in order to set up an IPsec SA and get a Home Address.
>=20
> Additionally, the ability to provide a mobile node with a=20
> localized home agent (e.g. on the visited link) can help to=20
> optimize handover signaling. There are a variety of ways this=20

IMO, an important benefit of local HAs is that they improve routing
efficiency in bi-directional tunneling mode. If optimized handover
signaling is mentioned, I would suggest to mention routing efficiency as
well, e.g.,

"Additionally, the ability to provide a mobile node with a localized
home agent (e.g. on the visited link) can help to optimize handover
signaling *and improve routing efficiency in bi-directional tunneling
mode*."


Kilian


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



From mip6-bounces@ietf.org Tue Oct 11 05:46:07 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EPGhz-0000Ik-I2; Tue, 11 Oct 2005 05:46:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EPGhy-0000Id-A2
	for mip6@megatron.ietf.org; Tue, 11 Oct 2005 05:46:06 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA10645
	for <mip6@ietf.org>; Tue, 11 Oct 2005 05:46:03 -0400 (EDT)
Received: from dns1.tilab.com ([163.162.42.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EPGs2-0002Wj-Dt
	for mip6@ietf.org; Tue, 11 Oct 2005 05:56:31 -0400
Received: from iowa2k01a.cselt.it ([163.162.242.201])
	by dns1.cselt.it (PMDF V6.0-025 #38895)
	with ESMTP id <0IO600I65WGF3P@dns1.cselt.it> for mip6@ietf.org; Tue,
	11 Oct 2005 11:45:51 +0200 (MEST)
Received: from EXC01B.cselt.it ([163.162.4.199]) by iowa2k01a.cselt.it with
	Microsoft SMTPSVC(6.0.3790.211); Tue, 11 Oct 2005 11:45:51 +0200
Date: Tue, 11 Oct 2005 11:45:50 +0200
From: Gerardo Giaretta <Gerardo.Giaretta@TILAB.COM>
Subject: RE: [Mip6] [draft-ietf-mip6-bootstrapping-split-00] Issue 53
To: Kilian Weniger <Kilian.Weniger@eu.panasonic.com>
Message-id: <DA62A6E0CDD1B34A84557FF1AC850C57016E9BD8@EXC01B.cselt.it>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.3790.326
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: quoted-printable
Importance: normal
Priority: normal
Thread-Topic: [Mip6] [draft-ietf-mip6-bootstrapping-split-00] Issue 53
thread-index: AcXKCdxhx2hw+cHJQvOuCteusVv1OADy9ZEwABrpDSAAAak1sAAAHaTw
Content-Class: urn:content-classes:message
X-OriginalArrivalTime: 11 Oct 2005 09:45:51.0093 (UTC)
	FILETIME=[90B8E250:01C5CE48]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Content-Transfer-Encoding: quoted-printable
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Hi Kilian,=20

>=20
> Hello Gerardo,
>=20
> > 5.1.1. DNS lookup by Home Agent Name
> >
> ...
> > The Mobile Node constructs a DNS request, by setting the=20
> > QNAME to the name of the Home Agent. The request has QTYPE=20
> > set to 'AAAA', so that the DNS server sends the IPv6 address=20
> > of the Home Agent. Once the DNS server replies to this query,=20
> > the Mobile Node knows its Home Agent address and can run=20
> > IKEv2 in order to set up an IPsec SA and get a Home Address.
> >=20
> > Additionally, the ability to provide a mobile node with a=20
> > localized home agent (e.g. on the visited link) can help to=20
> > optimize handover signaling. There are a variety of ways this=20
>=20
> IMO, an important benefit of local HAs is that they improve routing
> efficiency in bi-directional tunneling mode. If optimized handover
> signaling is mentioned, I would suggest to mention routing=20
> efficiency as
> well, e.g.,
>=20
> "Additionally, the ability to provide a mobile node with a localized
> home agent (e.g. on the visited link) can help to optimize handover
> signaling *and improve routing efficiency in bi-directional tunneling
> mode*."
>

I agree. I will add the sentence you are suggesting to the draft.

Thanks,
--Gerardo
=20
>=20
> Kilian
>=20
>=20


Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia =
S.p.A.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
CONFIDENTIALITY NOTICE
This message and its attachments are addressed solely to the persons
above and may contain confidential information. If you have received
the message in error, be informed that any use of the content hereof
is prohibited. Please return it immediately to the sender and delete
the message. Should you have any questions, please send an e_mail to=20
MailAdmin@tilab.com. Thank you
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

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



From mip6-bounces@ietf.org Tue Oct 11 09:09:54 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EPJtC-0008JZ-NI; Tue, 11 Oct 2005 09:09:54 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EPJtB-0008JQ-3B
	for mip6@megatron.ietf.org; Tue, 11 Oct 2005 09:09:53 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA22154
	for <mip6@ietf.org>; Tue, 11 Oct 2005 09:09:51 -0400 (EDT)
Received: from cluster-d.mailcontrol.com ([217.69.20.190]
	helo=rly12d.srv.mailcontrol.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EPK3I-0008U5-0B
	for mip6@ietf.org; Tue, 11 Oct 2005 09:20:20 -0400
Received: from hhe500-02.hbg.de.pan.eu (gate.eu.panasonic.com [194.173.20.12])
	by rly12d.srv.mailcontrol.com (MailControl) with SMTP id
	j9BD9gZC002308; Tue, 11 Oct 2005 14:09:42 +0100
Received: from eundadmi01.pan.eu(10.100.96.64) by hhe500-02.hbg.de.pan.eu via
	smtp id 772f_e9c5eeca_3a58_11da_80b8_0030482aac25;
	Tue, 11 Oct 2005 15:14:10 +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 2005101115094011-168142 ;
	Tue, 11 Oct 2005 15:09:40 +0200 
Received: from localhost ([127.0.0.1]) by VPN-MRelay-01.PRDCG.Panasonic.de;
	Tue, 11 Oct 2005 15:11:43 +0200
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Thread-Topic: draft-dupont-mip6-dhaadharmful-00.txt
Thread-Index: AcXNgPDulnM1vXM+THaWXxAJzs5W9gAK0F6A
To: "Francis Dupont" <Francis.Dupont@enst-bretagne.fr>
Message-ID: <4D2F935F08D41A4C8866693F4F0D7C4F58DBC3@lan-ex-01.panasonic.de>
Date: Tue, 11 Oct 2005 15:09:34 +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-05-40-00 (www.mailcontrol.com) on 10.68.0.122
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b5d20af10c334b36874c0264b10f59f1
Content-Transfer-Encoding: quoted-printable
Cc: mip6@ietf.org
Subject: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Hello Francis,

starting the discussions about your draft:

- Section A.3 lists threats and countermeasures for the DNS-based
procedure if no authentication of the DNS server by the client or of the
client by the server is done. E.g., the IKEv2 transaction with a bogus
HA address (obtained from an attacker during DHAAD) would fail because
the HA has to present a certificate to MN during IKEv2 transaction and
the IKE_AUTH message is protected by an authenticator calculated using
the public key in the certificate. Why are the described countermeasures
not sufficient to secure the bootstrapping procedure if no
authentication of the DNS server by the client or of the client by the
server is done, i.e., why is DNSSEC or TSIG/TKEY additionally needed?=20

- Do the same countermeasures also apply to the anycast-based DHAAD? If
so, is the anycast-based DHAAD still considered harmful? Is there an
implicit assumption that it is easier for an attacker to setup a bogus
HA with a certificate which seems trustworthy to the MN than to setup a
bogus DNS server with DNSSEC or TSIG/TKEY which seems trustworthy to the
MN?=20

- Assuming that no authentication of the DNS server by the client or of
the client by the server is done, is there any benefit in terms of
security of using the DNS-based procedure instead of using the
anycast-based DHAAD procedure, i.e., are there any threats specific to
the anycast-based procedure?

Assuming that the anycast-based DHAAD procedure is not considered
harmful (I guess the assumption is wrong when I look at the title of
your draft ;), I think one should carefully think about pros and cons of
both procedures, e.g.,

- A benefit of the anycast-based procedure (which is not realted to
security) is that load conditions can faster be considered for load
balancing. Of course, load balancing can also be achieved by other
means, e.g., by informing the MN to bootstrap with another HA after it
has bootstrapped with a heavily loaded HA, but I think one should again
carefully consider pros and cons of such solutions.

- A benefit of the DNS-based solution is that the prefix of the HA does
not need to be pre-configured on the MN.=20

One approach to get both benefits would be to combine both solutions,
i.e., the MN obtains the HA prefix from DNS and discovers the HA address
via anycast. In this case it may be beneficial to standardize both
procedures. What do you think?

Regards,

Kilian

> -----Original Message-----
> From: mip6-bounces@ietf.org [mailto:mip6-bounces@ietf.org] On=20
> Behalf Of Francis Dupont
> Sent: Montag, 10. Oktober 2005 11:50
> To: Basavaraj.Patil@nokia.com
> Cc: mip6@ietf.org
> Subject: Re: [Mip6] Timeslot requests for MIP6 WG agenda at IETF64=20
>=20
>  In your previous mail you wrote:
>=20
>    If you need a timeslot on the MIP6 WG agenda, please send
>    a request to the chairs with the following information:
>   =20
>    1. I-D title
>=20
> =3D> draft-dupont-mip6-dhaadharmful-00.txt
> (to summary current Dynamic Home Agent Address Discovery can be made
> secure so I propose to replace it by the DNS SRV RR of
> draft-ietf-mip6-bootstrapping-split-00.txt).
>=20
>    2. Amount of time requested
>=20
> =3D> 5 mn of discussion about the idea (adopt or not, if yes how
> to proceed). I strongly suggest to begin on the mailing list.
>=20
>    3. Is the I-D within the scope of the WG charter? If not why is it
>    important to discuss this at the WG meeting?
>   =20
> =3D> current DHAAD is in RFC 3775 so the I-D is in the scope.
>=20
> Thanks
>=20
> Francis.Dupont@enst-bretagne.fr
>=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 Tue Oct 11 17:57:36 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EPS7s-0007NS-Kh; Tue, 11 Oct 2005 17:57:36 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EPS7q-0007NN-Gs
	for mip6@megatron.ietf.org; Tue, 11 Oct 2005 17:57:34 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06389
	for <mip6@ietf.org>; Tue, 11 Oct 2005 17:57:31 -0400 (EDT)
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EPSI1-0002xZ-Lc
	for mip6@ietf.org; Tue, 11 Oct 2005 18:08:06 -0400
Message-ID: <153401c5ceae$c77ac3b0$196115ac@dcml.docomolabsusa.com>
From: "James Kempf" <Kempf@docomolabs-usa.com>
To: "Kilian Weniger" <Kilian.Weniger@eu.panasonic.com>
References: <4D2F935F08D41A4C8866693F4F0D7C4F58DB38@lan-ex-01.panasonic.de>
Subject: Re: [Mip6] review of draft-ietf-mip6-bootstrapping-split-00.txt
Date: Tue, 11 Oct 2005 14:57: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: 0.0 (/)
X-Scan-Signature: b2809b6f39decc6de467dcf252f42af1
Content-Transfer-Encoding: 7bit
Cc: Gerardo Giaretta <Gerardo.Giaretta@TILAB.COM>, mip6@ietf.org,
	Vijay Devarapalli <vijayd@iprg.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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org



> jak>> Given that the attacker only sees the current DNS entry
> (knows nothing
> more) how is to determine if the HA and HoA are "nearby" to
> the victim or
> not? Unless the attacker knows somehow specifically the

In one example I have given in the last emails the eavesdropper
additionally knows the victim's HA selection policy and this policy is
"always using nearby HAs". IMO, no additional information such as
victim's customary MSP would be needed in this scenario (of course, it
is again assumed that HoAs are DNS-registered).

jak>> Just knowing the victim's selection policy is not sufficient. The 
attacker would also have to know the serving ASP's local home agent 
allocation policy - does the serving ASP allocate home agents or not? If it 
doesn't, then the attacker would incorrectly conclude that Alice is in Palo 
Alto when she is actually in Tucson when it saw the DNS entry change to a 
HoA that was provided by Bob' Mobility Service in Palo Alto.

jak>> In addition, how does the attacker know the victim's selection policy? 
What I was trying to suggest is that, short of having the victim tell the 
attacker (which is of course possible, for example, through a spyware 
infection), the attacker would need to observe changes in the victim's DNS 
entry over time and correlate that with information on the local home agent 
allocation policy of the serving ASP.

Note that this HA selection policy is not far-fetched because it can
provide good routing efficiency in bi-directional tunneling mode. Also
note that for good routing efficiency of CN-initiated sessions,
DNS-registered HoAs are required.

> subnet prefixes
> assigned to home addresses by the victim's customary MSP, how can the
> attacker determine that the current HoA is somehow different?

Again, if the victim's policy is "always using nearby HAs" (this implies
that the victim only uses its customary MSP if it is close to this MSP)
and the eavesdopper is aware of that, the eavesdropper knows that the
new HA is nearby. I agree that in case the current ASP does not provide
local HA service, the location information is less accurate (as you
mentioned, an eavesdropper may be aware of the local HA support of
ASPs). In this case the MN could bootstrap with an HA of a nearby MSP
(In the worst case "nearby" may mean in the same country).

> And, again,
> even if the attacker knows the prefixes assigned by the
> customary MSP and it
> sees an HoA with a prefix not in that set, how can the
> attacker determine
> that the victim is in a particular geographical location when
> it sees that
> prefix? Returning to my previous example, the victim might be

see above

> jak>> I belive there is a threat, and I think it worthwhile
> to describe it.

I agree.

> I think the amount of information required (a-d) is rather
> large, but not
> undoable for a dedicated attacker.

I think there are scenarios where less information is needed (see
above).

> jak>> There is nothing in RFC 3775 to allow changing HAs
> frequently, and
> bootstrapping isn't intended to enable this either.

I agree to this, but it is a different question whether a solution
*intends* to enable something or whether it enables something. ;)
So far, I didn't see anything in the split scenario draft that prevents
MNs from bootstrapping with different HAs more or less frequently (at
least frequent enough that enables the policy "always using nearby
HAs").

jak>> OK.

> jak>> Why are country codes an issue? The DNS name for the MN
> is always
> fixed, otherwise, potential correspondents can't find it.
> Thus, if I am
> roaming in Germany and my home MSA is in the US, my FQDN
> always has the
> ".us" country code. Even if I am using a local home agent,
> the name doesn't
> change. And the HA FQDN is never exposed to the correspondent.

No, I'm not talking about MN's FQDN, I'm talking about HA's FQDN. The
issue is that location-dependent HA discovery is possible to some extent
by using the country code suffix of an HA's FQDN. If, for example, the
user roams from US to Germany, it can discover an HA located in Germany
by querying, e.g., "ha.t-mobile.de" or "ha.vodafone.de" (or
"_mip6._ipv6.vodafone.de"). This HA would be "nearby", but not
necessarily "local".

jak>> How does this provide any information about the victim's location? It 
depends on whether the victim actually uses the local home agent or not, 
which, as you mention above, depends on the victim's local home agent 
selection policy. If the victim doesn't use ha.t-mobile.de, but rather 
ha.t-mobile.us, then there's no problem.

jak>> Anyway, Gerardo wants us to come to agreement on this now so that we 
can wrap up the draft prior to the IETF 64 drafts deadline. How about the 
following:

1) We put a two sentence paragraph in the SecCons section of 
draft-mip6-bootstrapping-split that says the following:

    Allocation of a local home agent raises a possible risk of location 
privacy compromise. Since the details of how this threat might be actualized 
depend on how a local home agent is allocated, and local home agent 
allocation is out of scope for this document, the Security Considerations 
section of specifications that describe or include local home agent 
allocation should be consulted for details.

2) We include a detailed description of the location privacy threat and how 
to counter it in the SecCons section of draft-mip6-bootstrapping-integrated, 
which does include a mechanism for local home agent allocation.

            jak




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



From mip6-bounces@ietf.org Tue Oct 11 17:58:26 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EPS8g-0007QU-E6; Tue, 11 Oct 2005 17:58:26 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EPS8e-0007QM-RQ
	for mip6@megatron.ietf.org; Tue, 11 Oct 2005 17:58:24 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06426
	for <mip6@ietf.org>; Tue, 11 Oct 2005 17:58:21 -0400 (EDT)
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EPSIq-0002zD-FV
	for mip6@ietf.org; Tue, 11 Oct 2005 18:08:56 -0400
Message-ID: <153b01c5ceae$e5b198e0$196115ac@dcml.docomolabsusa.com>
From: "James Kempf" <Kempf@docomolabs-usa.com>
To: "Gerardo Giaretta" <Gerardo.Giaretta@TILAB.COM>,
	"Kilian Weniger" <Kilian.Weniger@eu.panasonic.com>
References: <4D2F935F08D41A4C8866693F4F0D7C4F58DB5C@lan-ex-01.panasonic.de>
Subject: Re: [Mip6] [draft-ietf-mip6-bootstrapping-split-00] Issue 53
Date: Tue, 11 Oct 2005 14:58:22 -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.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Content-Transfer-Encoding: 7bit
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Sure.

        jak

----- Original Message ----- 
From: "Kilian Weniger" <Kilian.Weniger@eu.panasonic.com>
To: "Gerardo Giaretta" <Gerardo.Giaretta@TILAB.COM>
Cc: <mip6@ietf.org>
Sent: Tuesday, October 11, 2005 2:43 AM
Subject: FW: [Mip6] [draft-ietf-mip6-bootstrapping-split-00] Issue 53


Hello Gerardo,

> 5.1.1. DNS lookup by Home Agent Name
>
...
> The Mobile Node constructs a DNS request, by setting the 
> QNAME to the name of the Home Agent. The request has QTYPE 
> set to 'AAAA', so that the DNS server sends the IPv6 address 
> of the Home Agent. Once the DNS server replies to this query, 
> the Mobile Node knows its Home Agent address and can run 
> IKEv2 in order to set up an IPsec SA and get a Home Address.
> 
> Additionally, the ability to provide a mobile node with a 
> localized home agent (e.g. on the visited link) can help to 
> optimize handover signaling. There are a variety of ways this 

IMO, an important benefit of local HAs is that they improve routing
efficiency in bi-directional tunneling mode. If optimized handover
signaling is mentioned, I would suggest to mention routing efficiency as
well, e.g.,

"Additionally, the ability to provide a mobile node with a localized
home agent (e.g. on the visited link) can help to optimize handover
signaling *and improve routing efficiency in bi-directional tunneling
mode*."


Kilian


_______________________________________________
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 Oct 11 18:16:26 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EPSQ6-0005Lt-C8; Tue, 11 Oct 2005 18:16:26 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EPSQ5-0005LH-JB
	for mip6@megatron.ietf.org; Tue, 11 Oct 2005 18:16:25 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07055
	for <mip6@ietf.org>; Tue, 11 Oct 2005 18:16:22 -0400 (EDT)
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EPSaH-0003OU-9o
	for mip6@ietf.org; Tue, 11 Oct 2005 18:26:57 -0400
Message-ID: <155a01c5ceb1$6748e190$196115ac@dcml.docomolabsusa.com>
From: "James Kempf" <Kempf@docomolabs-usa.com>
To: "Francis Dupont" <Francis.Dupont@enst-bretagne.fr>,
	"Kilian Weniger" <Kilian.Weniger@eu.panasonic.com>
References: <4D2F935F08D41A4C8866693F4F0D7C4F58DBC3@lan-ex-01.panasonic.de>
Subject: Re: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
Date: Tue, 11 Oct 2005 15:16:18 -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.0 (/)
X-Scan-Signature: 2086112c730e13d5955355df27e3074b
Content-Transfer-Encoding: 7bit
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

>From a deployment standpoint, there are two issues with DHAAD:

- it uses ICMP across the Internet. The trend has been to turn off ICMP 
except for local link communications, to avoid convenient vehicles for DoS. 
I know that one can theoretically configure the firewall to filter on the 
ICMP message type field, but it is easier just to drop it at the firewall 
than to try to figure out what ICMP is good and what is bad.

- AFIK, there is no way currently standardized to securely update anycast 
routing except to manually insert host routes into the subnet router 
handling the anycast address. So maintaining an anycast address would 
require extra maintenance effort, manually inserting and deleting the routes 
when HAs are added or deleted.

            jak

----- Original Message ----- 
From: "Kilian Weniger" <Kilian.Weniger@eu.panasonic.com>
To: "Francis Dupont" <Francis.Dupont@enst-bretagne.fr>
Cc: <mip6@ietf.org>
Sent: Tuesday, October 11, 2005 6:09 AM
Subject: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt


Hello Francis,

starting the discussions about your draft:

- Section A.3 lists threats and countermeasures for the DNS-based
procedure if no authentication of the DNS server by the client or of the
client by the server is done. E.g., the IKEv2 transaction with a bogus
HA address (obtained from an attacker during DHAAD) would fail because
the HA has to present a certificate to MN during IKEv2 transaction and
the IKE_AUTH message is protected by an authenticator calculated using
the public key in the certificate. Why are the described countermeasures
not sufficient to secure the bootstrapping procedure if no
authentication of the DNS server by the client or of the client by the
server is done, i.e., why is DNSSEC or TSIG/TKEY additionally needed?

- Do the same countermeasures also apply to the anycast-based DHAAD? If
so, is the anycast-based DHAAD still considered harmful? Is there an
implicit assumption that it is easier for an attacker to setup a bogus
HA with a certificate which seems trustworthy to the MN than to setup a
bogus DNS server with DNSSEC or TSIG/TKEY which seems trustworthy to the
MN?

- Assuming that no authentication of the DNS server by the client or of
the client by the server is done, is there any benefit in terms of
security of using the DNS-based procedure instead of using the
anycast-based DHAAD procedure, i.e., are there any threats specific to
the anycast-based procedure?

Assuming that the anycast-based DHAAD procedure is not considered
harmful (I guess the assumption is wrong when I look at the title of
your draft ;), I think one should carefully think about pros and cons of
both procedures, e.g.,

- A benefit of the anycast-based procedure (which is not realted to
security) is that load conditions can faster be considered for load
balancing. Of course, load balancing can also be achieved by other
means, e.g., by informing the MN to bootstrap with another HA after it
has bootstrapped with a heavily loaded HA, but I think one should again
carefully consider pros and cons of such solutions.

- A benefit of the DNS-based solution is that the prefix of the HA does
not need to be pre-configured on the MN.

One approach to get both benefits would be to combine both solutions,
i.e., the MN obtains the HA prefix from DNS and discovers the HA address
via anycast. In this case it may be beneficial to standardize both
procedures. What do you think?

Regards,

Kilian

> -----Original Message-----
> From: mip6-bounces@ietf.org [mailto:mip6-bounces@ietf.org] On
> Behalf Of Francis Dupont
> Sent: Montag, 10. Oktober 2005 11:50
> To: Basavaraj.Patil@nokia.com
> Cc: mip6@ietf.org
> Subject: Re: [Mip6] Timeslot requests for MIP6 WG agenda at IETF64
>
>  In your previous mail you wrote:
>
>    If you need a timeslot on the MIP6 WG agenda, please send
>    a request to the chairs with the following information:
>
>    1. I-D title
>
> => draft-dupont-mip6-dhaadharmful-00.txt
> (to summary current Dynamic Home Agent Address Discovery can be made
> secure so I propose to replace it by the DNS SRV RR of
> draft-ietf-mip6-bootstrapping-split-00.txt).
>
>    2. Amount of time requested
>
> => 5 mn of discussion about the idea (adopt or not, if yes how
> to proceed). I strongly suggest to begin on the mailing list.
>
>    3. Is the I-D within the scope of the WG charter? If not why is it
>    important to discuss this at the WG meeting?
>
> => current DHAAD is in RFC 3775 so the I-D is in the scope.
>
> Thanks
>
> Francis.Dupont@enst-bretagne.fr
>
> _______________________________________________
> 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 Oct 12 06:02:48 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EPdRg-0000xE-QX; Wed, 12 Oct 2005 06:02:48 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EPdRZ-0000wx-81
	for mip6@megatron.ietf.org; Wed, 12 Oct 2005 06:02:47 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA10443
	for <mip6@ietf.org>; Wed, 12 Oct 2005 06:02:37 -0400 (EDT)
Received: from cluster-d.mailcontrol.com ([217.69.20.190]
	helo=rly38d.srv.mailcontrol.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EPdbq-0004t1-T9
	for mip6@ietf.org; Wed, 12 Oct 2005 06:13:19 -0400
Received: from hhe500-02.hbg.de.pan.eu (gate.eu.panasonic.com [194.173.20.12])
	by rly38d.srv.mailcontrol.com (MailControl) with SMTP id
	j9CA2PcH032330; Wed, 12 Oct 2005 11:02:25 +0100
Received: from eundadmi01.pan.eu(10.100.96.64) by hhe500-02.hbg.de.pan.eu via
	smtp id 4aa0_ec68f7c6_3b07_11da_92fa_0030482aac25;
	Wed, 12 Oct 2005 12:06:57 +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 2005101212020768-204566 ;
	Wed, 12 Oct 2005 12:02:07 +0200 
Received: from localhost ([127.0.0.1]) by VPN-MRelay-01.PRDCG.Panasonic.de;
	Wed, 12 Oct 2005 12:04:11 +0200
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Subject: RE: [Mip6] review of draft-ietf-mip6-bootstrapping-split-00.txt
Thread-Topic: [Mip6] review of draft-ietf-mip6-bootstrapping-split-00.txt
Thread-Index: AcXOrtFJlkpc5t/JSoaTxShAxElR8AAUGZEg
To: "James Kempf" <Kempf@docomolabs-usa.com>
Message-ID: <4D2F935F08D41A4C8866693F4F0D7C4F58DC87@lan-ex-01.panasonic.de>
Date: Wed, 12 Oct 2005 12:02:01 +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-05-40-00 (www.mailcontrol.com) on 10.68.0.148
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 225414c974e0d6437992164e91287a51
Content-Transfer-Encoding: quoted-printable
Cc: Gerardo Giaretta <Gerardo.Giaretta@TILAB.COM>, mip6@ietf.org,
	Vijay Devarapalli <vijayd@iprg.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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org


> jak>> Just knowing the victim's selection policy is not=20
> sufficient. The=20
> attacker would also have to know the serving ASP's local home agent=20
> allocation policy - does the serving ASP allocate home agents=20
> or not? If it=20
> doesn't, then the attacker would incorrectly conclude that=20
> Alice is in Palo=20
> Alto when she is actually in Tucson when it saw the DNS entry=20
> change to a=20
> HoA that was provided by Bob' Mobility Service in Palo Alto.

I think we are just arguing about the accuracy of location information
revealed. I agree that if the eavesdropper does not know whether the ASP
provides local HA service, there is some uncertainty, but IMO some
location information can still be revealed (with lower accuracy). In the
scenario I described, the victim always selects a "nearby" HA (to
improve routing efficiency), i.e., one that is in or at least close to
the serving ASP (in the worst case the HA is only in the same country
than the serving ASP). Hence, the eavesdropper can conclude that the
victim is in or somewhere close the serving ASP. I agree that the
accuracy of the location information might not be known by the
eavesdropper, at least as long as it does not have additional policy
information.

>=20
> jak>> In addition, how does the attacker know the victim's=20
> selection policy?=20

Yes, that's another issue. One possibility may be that a provider has a
default policy, which the eavesdropper can find out.=20
Anyhow, I think the main point is that we describe the location privacy
issue in the draft, so that others are aware of it and, e.g., try to not
disclose the policy.

> What I was trying to suggest is that, short of having the=20
> victim tell the=20
> attacker (which is of course possible, for example, through a spyware=20
> infection), the attacker would need to observe changes in the=20
> victim's DNS=20
> entry over time and correlate that with information on the=20
> local home agent=20
> allocation policy of the serving ASP.

o.k., I see. I agree that's one way, but maybe not the only one (as you
mentioned yourself).

> jak>> How does this provide any information about the=20
> victim's location? It=20
> depends on whether the victim actually uses the local home=20
> agent or not,=20
> which, as you mention above, depends on the victim's local home agent=20
> selection policy. If the victim doesn't use ha.t-mobile.de,=20
> but rather=20
> ha.t-mobile.us, then there's no problem.

Yes, but I was assuming there would be enough MSPs in Germany, of which
at least one would provide an HA bootstrapping service to the victim (I
think that's not a far-fetched assumption). Then there is a possible
issue.=20
The main point I tried to make clear is that an issue may exist even
without *local HA discovery*, since *nearby HA discovery* might be
possible with the solution. One way could be country code suffixes
(although I agree that the possibly revealed location information would
be of low accuracy).

>=20
> jak>> Anyway, Gerardo wants us to come to agreement on this=20
> now so that we=20
> can wrap up the draft prior to the IETF 64 drafts deadline.=20
> How about the=20
> following:
>=20
> 1) We put a two sentence paragraph in the SecCons section of=20
> draft-mip6-bootstrapping-split that says the following:
>=20
>     Allocation of a local home agent raises a possible risk=20
> of location=20
> privacy compromise. Since the details of how this threat=20
> might be actualized=20
> depend on how a local home agent is allocated, and local home agent=20
> allocation is out of scope for this document, the Security=20
> Considerations=20
> section of specifications that describe or include local home agent=20
> allocation should be consulted for details.
>=20
> 2) We include a detailed description of the location privacy=20
> threat and how=20
> to counter it in the SecCons section of=20
> draft-mip6-bootstrapping-integrated,=20
> which does include a mechanism for local home agent allocation.

If the question is whether to include nothing or a short note, I prefer
the short note of course. However, I tried to make clear that IMO there
can be an issue with the allocation of "nearby", non-local HAs (with
"local HA" defined as HA in serving ASP network and "nearby HA" as HA in
network close to serving ASP network). This issue would be *specific to
the split scenario*. Hence, if you and others agree to the nearby HAs
issue, this should be reflected by the note IMO. However, in this case I
would prefer to add a more detailed description about the issue specific
to the split scenario to the draft - if not now (because of the
deadline) then at least in a later revision.

But why not use the text initially proposed by you, which has already
been agreed by you and Vijay. We can modify it slightly considering the
recent (IMO fruitful) discussions. We can still refine it later, if
necessary. How about this:

   Updating the mobile node's FQDN in the DNS with the mobile node's=20
   home address has the potential to expose some information about
   the mobile node's location to other nodes if the home agent=20
   selected by the mobile node is local or nearby, i.e., it is in or=20
   close to the serving network access provider's network.=20

   For three reasons, the risk here is not as deep as known from Route=20
   Optimization mode [draft-koodli-mip6-location-privacy-00.txt].=20
   First, other nodes usually do not know whether the mobile node's=20
   home address belongs to a home agent that is local, nearby or=20
   remote for the mobile node and, hence, whether the mobile node is=20
   really at the location corresponding to the home address. Second,=20
   the mobile node (if using reverse tunneling) will effectively=20
   appear to be at a fixed topological location in the mobility=20
   service provider's as long as it does not bootstrap again with a=20
   different home agent in a different network and request DNS update=20
   subsequently. Third, depending on the deployment scenario, the=20
   geographical area covered by a local home agent (being the "most=20
   local" home agent) may be much larger than the area covered by an=20
   access router. Since the accuracy of the location derivable from=20
   the address decreases with increasing coverage, the accuracy may be=20
   lower. In case the HA is only nearby, but not local, the accuracy=20
   may be even lower.

   However, the risk may be higher if additional information is known.
   E.g., the mobile node's home agent selection policy and the home=20
   agent allocation policy of ASPs can provide information about=20
   whether an home agent is local, nearby or remote for the mobile=20
   node. If, for instance, the mobile node's home agent selection=20
   policy is to bootstrap with a new local home agent as soon as=20
   moving to another network to improve routing efficiency of future=20
   communication sessions in Bi-directional Tunneling mode, other=20
   nodes being aware of the policies may be able to track mobile=20
   node's movement to some extent by constantly querying mobile=20
   node's DNS entry.=20

   To mitigate the risk, the mobile node should either not request DNS=20
   update or be careful to select a home agent that is local or nearby.=20
   Furthermore, the disclosure of related policy information such as=20
   mobile node's home agent selection policy and the home agent=20
   allocation policy of ASPs should be carefully considered.



Regards,

Kilian



=20



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



From mip6-bounces@ietf.org Wed Oct 12 14:03:08 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EPkwW-0005WX-LG; Wed, 12 Oct 2005 14:03:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EPkwU-0005WO-4Y
	for mip6@megatron.ietf.org; Wed, 12 Oct 2005 14:03:06 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08344
	for <mip6@ietf.org>; Wed, 12 Oct 2005 14:03:01 -0400 (EDT)
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EPl6q-0002HN-1N
	for mip6@ietf.org; Wed, 12 Oct 2005 14:13:48 -0400
Message-ID: <019f01c5cf57$30869d40$196115ac@dcml.docomolabsusa.com>
From: "James Kempf" <Kempf@docomolabs-usa.com>
To: "Kilian Weniger" <Kilian.Weniger@eu.panasonic.com>
References: <4D2F935F08D41A4C8866693F4F0D7C4F58DC87@lan-ex-01.panasonic.de>
Subject: Re: [Mip6] review of draft-ietf-mip6-bootstrapping-split-00.txt
Date: Wed, 12 Oct 2005 11:03:03 -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.0 (/)
X-Scan-Signature: 4b7d60495f1a7f2e853e8cbae7e6dbfc
Content-Transfer-Encoding: 7bit
Cc: Gerardo Giaretta <Gerardo.Giaretta@TILAB.COM>, mip6@ietf.org,
	Vijay Devarapalli <vijayd@iprg.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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

No, I do not agree to this extensive note.

The split scenerio draft specifically says that the details of local home 
agent allocation are *out of scope*. I don't see the point of a detailed 
security analysis of something that is not covered in the draft. If you or 
someone else writes a draft that says how to do local home agent allocation 
in the split scenerio, then that is the right place for an extensive 
analysis.

What do other members of the WG think?

            jak

----- Original Message ----- 
From: "Kilian Weniger" <Kilian.Weniger@eu.panasonic.com>
To: "James Kempf" <Kempf@docomolabs-usa.com>
Cc: "Gerardo Giaretta" <Gerardo.Giaretta@TILAB.COM>; <mip6@ietf.org>; "Vijay 
Devarapalli" <vijayd@iprg.nokia.com>
Sent: Wednesday, October 12, 2005 3:02 AM
Subject: RE: [Mip6] review of draft-ietf-mip6-bootstrapping-split-00.txt



> jak>> Just knowing the victim's selection policy is not
> sufficient. The
> attacker would also have to know the serving ASP's local home agent
> allocation policy - does the serving ASP allocate home agents
> or not? If it
> doesn't, then the attacker would incorrectly conclude that
> Alice is in Palo
> Alto when she is actually in Tucson when it saw the DNS entry
> change to a
> HoA that was provided by Bob' Mobility Service in Palo Alto.

I think we are just arguing about the accuracy of location information
revealed. I agree that if the eavesdropper does not know whether the ASP
provides local HA service, there is some uncertainty, but IMO some
location information can still be revealed (with lower accuracy). In the
scenario I described, the victim always selects a "nearby" HA (to
improve routing efficiency), i.e., one that is in or at least close to
the serving ASP (in the worst case the HA is only in the same country
than the serving ASP). Hence, the eavesdropper can conclude that the
victim is in or somewhere close the serving ASP. I agree that the
accuracy of the location information might not be known by the
eavesdropper, at least as long as it does not have additional policy
information.

>
> jak>> In addition, how does the attacker know the victim's
> selection policy?

Yes, that's another issue. One possibility may be that a provider has a
default policy, which the eavesdropper can find out.
Anyhow, I think the main point is that we describe the location privacy
issue in the draft, so that others are aware of it and, e.g., try to not
disclose the policy.

> What I was trying to suggest is that, short of having the
> victim tell the
> attacker (which is of course possible, for example, through a spyware
> infection), the attacker would need to observe changes in the
> victim's DNS
> entry over time and correlate that with information on the
> local home agent
> allocation policy of the serving ASP.

o.k., I see. I agree that's one way, but maybe not the only one (as you
mentioned yourself).

> jak>> How does this provide any information about the
> victim's location? It
> depends on whether the victim actually uses the local home
> agent or not,
> which, as you mention above, depends on the victim's local home agent
> selection policy. If the victim doesn't use ha.t-mobile.de,
> but rather
> ha.t-mobile.us, then there's no problem.

Yes, but I was assuming there would be enough MSPs in Germany, of which
at least one would provide an HA bootstrapping service to the victim (I
think that's not a far-fetched assumption). Then there is a possible
issue.
The main point I tried to make clear is that an issue may exist even
without *local HA discovery*, since *nearby HA discovery* might be
possible with the solution. One way could be country code suffixes
(although I agree that the possibly revealed location information would
be of low accuracy).

>
> jak>> Anyway, Gerardo wants us to come to agreement on this
> now so that we
> can wrap up the draft prior to the IETF 64 drafts deadline.
> How about the
> following:
>
> 1) We put a two sentence paragraph in the SecCons section of
> draft-mip6-bootstrapping-split that says the following:
>
>     Allocation of a local home agent raises a possible risk
> of location
> privacy compromise. Since the details of how this threat
> might be actualized
> depend on how a local home agent is allocated, and local home agent
> allocation is out of scope for this document, the Security
> Considerations
> section of specifications that describe or include local home agent
> allocation should be consulted for details.
>
> 2) We include a detailed description of the location privacy
> threat and how
> to counter it in the SecCons section of
> draft-mip6-bootstrapping-integrated,
> which does include a mechanism for local home agent allocation.

If the question is whether to include nothing or a short note, I prefer
the short note of course. However, I tried to make clear that IMO there
can be an issue with the allocation of "nearby", non-local HAs (with
"local HA" defined as HA in serving ASP network and "nearby HA" as HA in
network close to serving ASP network). This issue would be *specific to
the split scenario*. Hence, if you and others agree to the nearby HAs
issue, this should be reflected by the note IMO. However, in this case I
would prefer to add a more detailed description about the issue specific
to the split scenario to the draft - if not now (because of the
deadline) then at least in a later revision.

But why not use the text initially proposed by you, which has already
been agreed by you and Vijay. We can modify it slightly considering the
recent (IMO fruitful) discussions. We can still refine it later, if
necessary. How about this:

   Updating the mobile node's FQDN in the DNS with the mobile node's
   home address has the potential to expose some information about
   the mobile node's location to other nodes if the home agent
   selected by the mobile node is local or nearby, i.e., it is in or
   close to the serving network access provider's network.

   For three reasons, the risk here is not as deep as known from Route
   Optimization mode [draft-koodli-mip6-location-privacy-00.txt].
   First, other nodes usually do not know whether the mobile node's
   home address belongs to a home agent that is local, nearby or
   remote for the mobile node and, hence, whether the mobile node is
   really at the location corresponding to the home address. Second,
   the mobile node (if using reverse tunneling) will effectively
   appear to be at a fixed topological location in the mobility
   service provider's as long as it does not bootstrap again with a
   different home agent in a different network and request DNS update
   subsequently. Third, depending on the deployment scenario, the
   geographical area covered by a local home agent (being the "most
   local" home agent) may be much larger than the area covered by an
   access router. Since the accuracy of the location derivable from
   the address decreases with increasing coverage, the accuracy may be
   lower. In case the HA is only nearby, but not local, the accuracy
   may be even lower.

   However, the risk may be higher if additional information is known.
   E.g., the mobile node's home agent selection policy and the home
   agent allocation policy of ASPs can provide information about
   whether an home agent is local, nearby or remote for the mobile
   node. If, for instance, the mobile node's home agent selection
   policy is to bootstrap with a new local home agent as soon as
   moving to another network to improve routing efficiency of future
   communication sessions in Bi-directional Tunneling mode, other
   nodes being aware of the policies may be able to track mobile
   node's movement to some extent by constantly querying mobile
   node's DNS entry.

   To mitigate the risk, the mobile node should either not request DNS
   update or be careful to select a home agent that is local or nearby.
   Furthermore, the disclosure of related policy information such as
   mobile node's home agent selection policy and the home agent
   allocation policy of ASPs should be carefully considered.



Regards,

Kilian









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



From mip6-bounces@ietf.org Thu Oct 13 08:17:01 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EQ217-0004lp-06; Thu, 13 Oct 2005 08:17:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EQ215-0004lk-0G
	for mip6@megatron.ietf.org; Thu, 13 Oct 2005 08:16:59 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA13824
	for <mip6@ietf.org>; Thu, 13 Oct 2005 08:16:54 -0400 (EDT)
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EQ2BZ-0001YU-8m
	for mip6@ietf.org; Thu, 13 Oct 2005 08:27:50 -0400
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id BA6D989870
	for <mip6@ietf.org>; Thu, 13 Oct 2005 15:16:39 +0300 (EEST)
Message-ID: <434E5032.6050907@kolumbus.fi>
Date: Thu, 13 Oct 2005 15:16:50 +0300
From: Jari Arkko <jari.arkko@kolumbus.fi>
User-Agent: Mozilla Thunderbird 1.0 (X11/20041206)
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; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b5d20af10c334b36874c0264b10f59f1
Content-Transfer-Encoding: 7bit
Subject: [Mip6] review of draft-ietf-mip6-dsmip-problem-00.txt
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

I reviewed this draft. Overall, its pretty easy to agree
with what is said. My main concern is that the draft is taking a
relatively narrow view into this problem. For instance, its likely that
we need NATs, corporate VPN compatibility, various extra
mobility features developed over the years, etc. as well
as basic mobility. How do we achieve this? And I don't think
the real issue is minor differences in amount of signaling,
even if us researchers and engineers would like to optimize
everything... the real issue is getting a mobility solution
that works, no matter what environment you are in.
I don't mean that we necessarily need to develop everything
right now, but I'd like to see a description of the whole
problem, and some ideas about how we are going about
addressing it.

More comments below:

>    This draft discusses the issues associated with mobility management
>    for dual stack mobile nodes. Currently, two mobility management
>    protocols are defined for IPv4 and IPv6. Deploying both in a dual
>    stack mobile node introduces a number of inefficiencies

I do not think this is just about ineffiency! We have no connectivity
or at least session survivability without some form of interworking
between different mobility mechanisms.

> 2.4. The impossibility of maintaining connectivity
>
>    A final point to consider is that even if both mobility protocols are
>    supported by a mobile node seamless connectivity would not in fact be
>    guarantied since that also depends on the IPv4/IPv6 capabilities of
>    the networks the mobile is visiting i.e.: a dual stack node
>    attempting to connect via a IPv4 only network would not be able to
>    maintain connectivity of its IPv6 applications and vice versa.

This, to me, is the main problem in fact. If you assume you have
v4 and v6 everywhere, why not just use Mobile IPv6? But the
reality is that we'll find ourselves more or less forever locked
in a situation where there are at least some networks that
are v4 only. From a commercial standpoint, we do not want
to deploy technology that only works some of the time, so I think
people are looking for solutions that work in all cases.
And "work" = "works for the user's ongoing sessions", not
just "we can send mobility protocol signaling messages".

>    - it should be possible to create IPv4 extensions to Mobile IPv6 so
>    that a dual stack mobile node can register its IPv4 and IPv6 HoAs to
>    a dual stack Home Agent using MIPv6 signaling only.

>    - it should be possible to create IPv6 extensions to MIPv4 so that a
>    dual stack mobile node can register its IPv4 and IPv6 HoAs to a dual
>    stack Home Agent using MIPv4 signaling only.

>    - it should also be possible to extend MIPv4 and MIPv6 so that a
>    mobile can register a single CoA (IPv4 or IPv6) to which IPv4 and/or
>    IPv6 packets can be diverted to.

Yes. These are all things that we should do, I think.

But this list is also quite short in comparison to what
has been documented elsewhere, e.g., draft-larsson-v6ops-mip-scenarios.
E.g. transition mechanism-based approaches have not been
mentioned.

Also, there's a body of work that relates to various kinds
of additions over the basic protocols. It would be interesting
to understand the bigger picture of how we are going to
use the additional components (RO, fast handovers, various
auth schemes, ...) in a mixed environment.

> 2.2. Operational burdens
>
>    As mentioned earlier, deploying both protocols will require managing
>    both protocols in the mobile node and the home agent. This adds
>    significant operational issues for the network operator. It would
>    certainly require the network operator to have deep knowledge in both
>    protocols. This might add a significant cost for deployment that an
>    operator cannot justify due to the lack of substantial gains.

Duplicate user credentials are a possibility at this time
(e.g. MIPv4 shared secrets, MIP6 auth option, MIPv6 IKE/IPsec
SAs or keys, IKEv2-based EAP credentials, ...). Probably worthwhile to
mention as a separate item.

> 4. References

References to other work in this space might be appropriate.
Can't give you a good list, but I'm sure there are some items
that could be mentioned here. In fact, even the existing references
in the text such as [MIPv4] are not listed here.

--Jari


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



From mip6-bounces@ietf.org Thu Oct 13 16:32:12 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EQ9kK-00061P-Mt; Thu, 13 Oct 2005 16:32:12 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EQ9kJ-0005yx-1I
	for mip6@megatron.ietf.org; Thu, 13 Oct 2005 16:32:11 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15747
	for <mip6@ietf.org>; Thu, 13 Oct 2005 16:32:07 -0400 (EDT)
Received: from mail.flarion.com ([63.103.94.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EQ9us-0000At-Tt
	for mip6@ietf.org; Thu, 13 Oct 2005 16:43:07 -0400
Received: from ftmailserver.flariontech.com ([10.10.1.140]) by
	mail.flarion.com with Microsoft SMTPSVC(5.0.2195.6713);
	Thu, 13 Oct 2005 16:31:51 -0400
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
Subject: RE: [Mip6] review of draft-ietf-mip6-dsmip-problem-00.txt
Date: Thu, 13 Oct 2005 16:31:51 -0400
Message-ID: <A11736FE943F1A408F8BBB1B9F5FE8AD01D5B83C@ftmailserver.flariontech.com>
Thread-Topic: [Mip6] review of draft-ietf-mip6-dsmip-problem-00.txt
Thread-Index: AcXP8QKh9eGRiNbIRvSZ9lvhHOsABAAQuU+Q
From: "Tsirtsis, George" <G.Tsirtsis@flarion.com>
To: "Jari Arkko" <jari.arkko@kolumbus.fi>,
	"Mobile IPv6 Mailing List" <mip6@ietf.org>
X-OriginalArrivalTime: 13 Oct 2005 20:31:51.0888 (UTC)
	FILETIME=[24C85500:01C5D035]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0770535483960d190d4a0d020e7060bd
Content-Transfer-Encoding: quoted-printable
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Jari,

It might be a good idea to separate v4 to v6 migration and NAT type
issues from enabling MIP to creating bindings for v4 and v6 HoAs.

The v4 to v6 transition and NAT issue has nothing to do with the version
of the HoA; instead it is purely about how to run a given
protocol/application *over* v4 and v6 based networks as well as over
NATs and other such devices.=20

In contrast, the dsmip problem described in the problem statement is
about allowing a single signaling protocol to create and manipulate v4
and v6 HoAs.

What I am arguing is that these as separable/orthogonal problems and it
will be easier to treat them as such.=20


Regards
George

> -----Original Message-----
> From: mip6-bounces@ietf.org [mailto:mip6-bounces@ietf.org] On=20
> Behalf Of Jari Arkko
> Sent: Thursday, October 13, 2005 8:17 AM
> To: Mobile IPv6 Mailing List
> Subject: [Mip6] review of draft-ietf-mip6-dsmip-problem-00.txt
>=20
>=20
> I reviewed this draft. Overall, its pretty easy to agree
> with what is said. My main concern is that the draft is=20
> taking a relatively narrow view into this problem. For=20
> instance, its likely that we need NATs, corporate VPN=20
> compatibility, various extra mobility features developed over=20
> the years, etc. as well as basic mobility. How do we achieve=20
> this? And I don't think the real issue is minor differences=20
> in amount of signaling, even if us researchers and engineers=20
> would like to optimize everything... the real issue is=20
> getting a mobility solution that works, no matter what=20
> environment you are in. I don't mean that we necessarily need=20
> to develop everything right now, but I'd like to see a=20
> description of the whole problem, and some ideas about how we=20
> are going about addressing it.
>=20
> More comments below:
>=20
> >    This draft discusses the issues associated with mobility=20
> management
> >    for dual stack mobile nodes. Currently, two mobility management
> >    protocols are defined for IPv4 and IPv6. Deploying both in a dual
> >    stack mobile node introduces a number of inefficiencies
>=20
> I do not think this is just about ineffiency! We have no=20
> connectivity or at least session survivability without some=20
> form of interworking between different mobility mechanisms.
>=20
> > 2.4. The impossibility of maintaining connectivity
> >
> >    A final point to consider is that even if both mobility=20
> protocols are
> >    supported by a mobile node seamless connectivity would=20
> not in fact be
> >    guarantied since that also depends on the IPv4/IPv6=20
> capabilities of
> >    the networks the mobile is visiting i.e.: a dual stack node
> >    attempting to connect via a IPv4 only network would not=20
> be able to
> >    maintain connectivity of its IPv6 applications and vice versa.
>=20
> This, to me, is the main problem in fact. If you assume you=20
> have v4 and v6 everywhere, why not just use Mobile IPv6? But=20
> the reality is that we'll find ourselves more or less forever=20
> locked in a situation where there are at least some networks=20
> that are v4 only. From a commercial standpoint, we do not=20
> want to deploy technology that only works some of the time,=20
> so I think people are looking for solutions that work in all=20
> cases. And "work" =3D "works for the user's ongoing sessions",=20
> not just "we can send mobility protocol signaling messages".
>=20
> >    - it should be possible to create IPv4 extensions to=20
> Mobile IPv6 so
> >    that a dual stack mobile node can register its IPv4 and=20
> IPv6 HoAs to
> >    a dual stack Home Agent using MIPv6 signaling only.
>=20
> >    - it should be possible to create IPv6 extensions to=20
> MIPv4 so that a
> >    dual stack mobile node can register its IPv4 and IPv6=20
> HoAs to a dual
> >    stack Home Agent using MIPv4 signaling only.
>=20
> >    - it should also be possible to extend MIPv4 and MIPv6 so that a
> >    mobile can register a single CoA (IPv4 or IPv6) to which=20
> IPv4 and/or
> >    IPv6 packets can be diverted to.
>=20
> Yes. These are all things that we should do, I think.
>=20
> But this list is also quite short in comparison to what
> has been documented elsewhere, e.g.,=20
> draft-larsson-v6ops-mip-scenarios.
> E.g. transition mechanism-based approaches have not been mentioned.
>=20
> Also, there's a body of work that relates to various kinds
> of additions over the basic protocols. It would be=20
> interesting to understand the bigger picture of how we are=20
> going to use the additional components (RO, fast handovers,=20
> various auth schemes, ...) in a mixed environment.
>=20
> > 2.2. Operational burdens
> >
> >    As mentioned earlier, deploying both protocols will=20
> require managing
> >    both protocols in the mobile node and the home agent. This adds
> >    significant operational issues for the network operator. It would
> >    certainly require the network operator to have deep=20
> knowledge in both
> >    protocols. This might add a significant cost for=20
> deployment that an
> >    operator cannot justify due to the lack of substantial gains.
>=20
> Duplicate user credentials are a possibility at this time
> (e.g. MIPv4 shared secrets, MIP6 auth option, MIPv6 IKE/IPsec=20
> SAs or keys, IKEv2-based EAP credentials, ...). Probably=20
> worthwhile to mention as a separate item.
>=20
> > 4. References
>=20
> References to other work in this space might be appropriate.=20
> Can't give you a good list, but I'm sure there are some items=20
> that could be mentioned here. In fact, even the existing=20
> references in the text such as [MIPv4] are not listed here.
>=20
> --Jari
>=20
>=20
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
>=20

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D
This email may contain confidential and privileged material for the sole =
use
 of the intended recipient.  Any review or distribution by others is =
strictly
 prohibited.  If you are not the intended recipient please contact the =
sender
 and delete all copies.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D


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



From mip6-bounces@ietf.org Thu Oct 13 18:15:12 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EQBM0-0004Ze-2k; Thu, 13 Oct 2005 18:15:12 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EQBLy-0004ZZ-EC
	for mip6@megatron.ietf.org; Thu, 13 Oct 2005 18:15:10 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21475
	for <mip6@ietf.org>; Thu, 13 Oct 2005 18:15:06 -0400 (EDT)
Received: from mail.flarion.com ([63.103.94.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EQBWZ-00031W-Fe
	for mip6@ietf.org; Thu, 13 Oct 2005 18:26:07 -0400
Received: from ftmailserver.flariontech.com ([10.10.1.140]) by
	mail.flarion.com with Microsoft SMTPSVC(5.0.2195.6713);
	Thu, 13 Oct 2005 18:15:01 -0400
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
Subject: RE: [Mip6] review of draft-ietf-mip6-dsmip-problem-00.txt
Date: Thu, 13 Oct 2005 18:15:00 -0400
Message-ID: <A11736FE943F1A408F8BBB1B9F5FE8AD17DE3C@ftmailserver.flariontech.com>
Thread-Topic: [Mip6] review of draft-ietf-mip6-dsmip-problem-00.txt
Thread-Index: AcXP8QKh9eGRiNbIRvSZ9lvhHOsABAAT6Leg
From: "Soliman, Hesham" <H.Soliman@flarion.com>
To: "Jari Arkko" <jari.arkko@kolumbus.fi>
X-OriginalArrivalTime: 13 Oct 2005 22:15:01.0068 (UTC)
	FILETIME=[8DD240C0:01C5D043]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a8041eca2a724d631b098c15e9048ce9
Content-Transfer-Encoding: quoted-printable
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Jari,=20

Thanks for the detailed review. Some responses inline:

 > I reviewed this draft. Overall, its pretty easy to agree
 > with what is said. My main concern is that the draft is taking a
 > relatively narrow view into this problem. For instance, its=20
 > likely that
 > we need NATs, corporate VPN compatibility, various extra
 > mobility features developed over the years, etc. as well
 > as basic mobility. How do we achieve this? And I don't think
 > the real issue is minor differences in amount of signaling,
 > even if us researchers and engineers would like to optimize
 > everything... the real issue is getting a mobility solution
 > that works, no matter what environment you are in.
 > I don't mean that we necessarily need to develop everything
 > right now, but I'd like to see a description of the whole
 > problem, and some ideas about how we are going about
 > addressing it.

=3D> I like the general tone of what you're saying but it's not=20
clear to me how to incorporate this type of comment in the draft.=20
Let me give some context first. This statement is intended to=20
be narrow in terms of the types of problems encountered. draft-larsson
(which you refer to below) provides a very detailed and solid analysis
of all potential issues of incompatibility for almost all permutations
of MIPv4 and MIPv6. Of course not all those scenarios are relevant
in the real world. So, we decided to focus on the most important
scenarios. Bearing in mind that we are only extending the current
MIP specs. So the idea is that in such a way of working, the dependency
is on the latest MIP protocol. If there is a problem when dealing=20
with VPNs/NATs ...etc and MIP, then this should be done at the=20
root of the dependency tree. At the same time, if the solutions to
the problems outlined in the draft introduce new problems for=20
VPNs/NATs....etc then this should be resolved at the new leaf of
the dependency tree (i.e. if those problems are specific to the=20
new solution).=20

There is evidence for both cases today; for example MIP4 did some
work on NAT traversal independently of the MIP4/MIP6 incompatibilities.=20
So this was done at the root of the dependency tree. On the other hand,=20
the solution we're working on now for MIP6 includes NAT traversal, =
because
it is specific to the problem we're dealing with and is not a general
issue for MIP6. I hope this gives more context to the discussion.


 > More comments below:
 >=20
 > >    This draft discusses the issues associated with=20
 > mobility management
 > >    for dual stack mobile nodes. Currently, two mobility management
 > >    protocols are defined for IPv4 and IPv6. Deploying both=20
 > in a dual
 > >    stack mobile node introduces a number of inefficiencies
 >=20
 > I do not think this is just about ineffiency! We have no connectivity
 > or at least session survivability without some form of interworking
 > between different mobility mechanisms.

=3D> Well, in some cases it's an inefficiency problem, but in other=20
cases (like tunnelling IPv4 in IPv6 on the fly) it's a problem of=20
no connectivity. I think we should reword this paragraph to reflect
that.=20

 > > 2.4. The impossibility of maintaining connectivity
 > >
 > >    A final point to consider is that even if both mobility=20
 > protocols are
 > >    supported by a mobile node seamless connectivity would=20
 > not in fact be
 > >    guarantied since that also depends on the IPv4/IPv6=20
 > capabilities of
 > >    the networks the mobile is visiting i.e.: a dual stack node
 > >    attempting to connect via a IPv4 only network would not=20
 > be able to
 > >    maintain connectivity of its IPv6 applications and vice versa.
 >=20
 > This, to me, is the main problem in fact.=20

=3D> I can't resist a comment on this :) To some people (George
and myself included) running MIP6 and MIP4 in parallel is almost equally =
bad.
I'm saying this because I think it's important for us to think
about MIP as a local mobility solution as well as a global mobility
one.=20

    If you assume you have
 > v4 and v6 everywhere, why not just use Mobile IPv6? But the
 > reality is that we'll find ourselves more or less forever locked
 > in a situation where there are at least some networks that
 > are v4 only. From a commercial standpoint, we do not want
 > to deploy technology that only works some of the time, so I think
 > people are looking for solutions that work in all cases.
 > And "work" =3D "works for the user's ongoing sessions", not
 > just "we can send mobility protocol signaling messages".

=3D> Agreed.

 >=20
 > >    - it should be possible to create IPv4 extensions to=20
 > Mobile IPv6 so
 > >    that a dual stack mobile node can register its IPv4 and=20
 > IPv6 HoAs to
 > >    a dual stack Home Agent using MIPv6 signaling only.
 >=20
 > >    - it should be possible to create IPv6 extensions to=20
 > MIPv4 so that a
 > >    dual stack mobile node can register its IPv4 and IPv6=20
 > HoAs to a dual
 > >    stack Home Agent using MIPv4 signaling only.
 >=20
 > >    - it should also be possible to extend MIPv4 and MIPv6 so that a
 > >    mobile can register a single CoA (IPv4 or IPv6) to=20
 > which IPv4 and/or
 > >    IPv6 packets can be diverted to.
 >=20
 > Yes. These are all things that we should do, I think.
 >=20
 > But this list is also quite short in comparison to what
 > has been documented elsewhere, e.g.,=20
 > draft-larsson-v6ops-mip-scenarios.
 > E.g. transition mechanism-based approaches have not been
 > mentioned.

=3D> Right, intentionally. The assumption is that we can
reference draft-larsson for the entire study. I'm hoping
that draft-larsson is going to be published soon. I talked
to Henrik about this and he's going to pursue that option.

 >=20
 > Also, there's a body of work that relates to various kinds
 > of additions over the basic protocols. It would be interesting
 > to understand the bigger picture of how we are going to
 > use the additional components (RO, fast handovers, various
 > auth schemes, ...) in a mixed environment.

=3D> Agreed. We can elaborate on that. Personally, after looking at=20
this for some time, I find it difficult to do this with FMIP
alone. Also, RO is obviously out of the question for IPv4 - IPv4
communication. But I agree it should be detailed a bit more.

 >=20
 > > 2.2. Operational burdens
 > >
 > >    As mentioned earlier, deploying both protocols will=20
 > require managing
 > >    both protocols in the mobile node and the home agent. This adds
 > >    significant operational issues for the network=20
 > operator. It would
 > >    certainly require the network operator to have deep=20
 > knowledge in both
 > >    protocols. This might add a significant cost for=20
 > deployment that an
 > >    operator cannot justify due to the lack of substantial gains.
 >=20
 > Duplicate user credentials are a possibility at this time
 > (e.g. MIPv4 shared secrets, MIP6 auth option, MIPv6 IKE/IPsec
 > SAs or keys, IKEv2-based EAP credentials, ...). Probably=20
 > worthwhile to
 > mention as a separate item.

=3D> Agreed.

 >=20
 > > 4. References
 >=20
 > References to other work in this space might be appropriate.
 > Can't give you a good list, but I'm sure there are some items
 > that could be mentioned here. In fact, even the existing references
 > in the text such as [MIPv4] are not listed here.

=3D> Sure, sloppy writing. We'll fix that.=20

Hesham

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

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D
This email may contain confidential and privileged material for the sole =
use
 of the intended recipient.  Any review or distribution by others is =
strictly
 prohibited.  If you are not the intended recipient please contact the =
sender
 and delete all copies.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D


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



From mip6-bounces@ietf.org Thu Oct 13 20:03:33 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EQD2r-0008Hh-Op; Thu, 13 Oct 2005 20:03:33 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EQD2q-0008HO-VR
	for mip6@megatron.ietf.org; Thu, 13 Oct 2005 20:03:33 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA05165
	for <mip6@ietf.org>; Thu, 13 Oct 2005 20:03:24 -0400 (EDT)
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EQDDN-0008SY-QO
	for mip6@ietf.org; Thu, 13 Oct 2005 20:14:27 -0400
Message-ID: <0c7901c5d052$aea65840$196115ac@dcml.docomolabsusa.com>
From: "James Kempf" <Kempf@docomolabs-usa.com>
To: <Basavaraj.Patil@nokia.com>, <mip6@ietf.org>
References: <456943D540CFC14A8D7138E64843F85301CFD7B4@daebe101.NOE.Nokia.com>
Subject: Re: [Mip6] Timeslot requests for MIP6 WG agenda at IETF64
Date: Thu, 13 Oct 2005 17:03:18 -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.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Content-Transfer-Encoding: 7bit
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Raj,

I'd like time for draft-haley-mip6-ha-switch-00.txt. I'd like to get a sense 
of whether people think it would make a good WG draft.

            jak

----- Original Message ----- 
From: <Basavaraj.Patil@nokia.com>
To: <mip6@ietf.org>
Sent: Thursday, October 06, 2005 10:08 AM
Subject: [Mip6] Timeslot requests for MIP6 WG agenda at IETF64



Hello,

The MIP6 WG will meet at IETF64. We have currently requested a 2.5 hour
slot
for the meeting. If you need a timeslot on the MIP6 WG agenda, please
send
a request to the chairs with the following information:

1. I-D title
2. Amount of time requested
3. Is the I-D within the scope of the WG charter? If not why is it
important to
   discuss this at the WG meeting?

-Raj

_______________________________________________
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 Fri Oct 14 11:43:37 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EQRib-00009C-3a; Fri, 14 Oct 2005 11:43:37 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EQRiZ-00006L-3m
	for mip6@megatron.ietf.org; Fri, 14 Oct 2005 11:43:35 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24943
	for <mip6@ietf.org>; Fri, 14 Oct 2005 11:43:30 -0400 (EDT)
From: Basavaraj.Patil@nokia.com
Received: from mgw-ext03.nokia.com ([131.228.20.95])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EQRtI-0001MZ-AZ
	for mip6@ietf.org; Fri, 14 Oct 2005 11:54:41 -0400
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
	by mgw-ext03.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id
	j9EFfZKZ015636 for <mip6@ietf.org>; Fri, 14 Oct 2005 18:41:36 +0300
Received: from daebh101.NOE.Nokia.com ([10.241.35.111]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 14 Oct 2005 18:43:24 +0300
Received: from daebe101.NOE.Nokia.com ([10.241.35.113]) by
	daebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 14 Oct 2005 10:43:21 -0500
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
Date: Fri, 14 Oct 2005 10:43:17 -0500
Message-ID: <456943D540CFC14A8D7138E64843F85301DC5DC5@daebe101.NOE.Nokia.com>
Thread-Topic: Reminder: I-D cutoff dates
Thread-Index: AcXQ1f8NF4Kl9QCfQeKwMHrw3B0fgA==
To: <mip6@ietf.org>
X-OriginalArrivalTime: 14 Oct 2005 15:43:21.0619 (UTC)
	FILETIME=[0178A630:01C5D0D6]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Content-Transfer-Encoding: quoted-printable
Subject: [Mip6] Reminder: I-D cutoff dates
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

There are two (2) Internet-Draft cutoff dates for the 64th=20
IETF Meeting in Vancouver, British Columbia, Canada:

October 17th: Cutoff Date for Initial (i.e., version -00)=20
Internet-Draft Submissions=20

All initial Internet-Drafts (version -00) must be submitted by Monday,=20
October 17th at 9:00 AM ET. As always, all initial submissions with a=20
filename beginning with "draft-ietf" must be approved by the=20
appropriate WG Chair before they can be processed or announced.  The=20
Secretariat would appreciate receiving WG Chair approval by Monday,=20
October 10th at 9:00 AM ET.

October 24th: Cutoff Date for Revised (i.e., version -01 and higher)=20
Internet-Draft Submissions=20

All revised Internet-Drafts (version -01 and higher) must be submitted=20
by Monday, October 24th at 9:00 AM ET.

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



From mip6-bounces@ietf.org Fri Oct 14 15:50:26 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EQVZS-0005Zl-E4; Fri, 14 Oct 2005 15:50:26 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EQVZ6-0005NH-CS; Fri, 14 Oct 2005 15:50:04 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07114;
	Fri, 14 Oct 2005 15:49:58 -0400 (EDT)
Received: from [132.151.6.50] (helo=newodin.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1EQVjr-0007nK-DU; Fri, 14 Oct 2005 16:01:12 -0400
Received: from mlee by newodin.ietf.org with local (Exim 4.43)
	id 1EQVZ4-0000md-3X; Fri, 14 Oct 2005 15:50:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1EQVZ4-0000md-3X@newodin.ietf.org>
Date: Fri, 14 Oct 2005 15:50:02 -0400
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1
Cc: mip6@ietf.org
Subject: [Mip6] I-D ACTION:draft-ietf-mip6-location-privacy-ps-00.txt 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

--NextPart

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

	Title		: IP Address Location Privacy and Mobile IPv6:  Problem Statement
	Author(s)	: R. Koodli
	Filename	: draft-ietf-mip6-location-privacy-ps-00.txt
	Pages		: 7
	Date		: 2005-10-14
	
   In this document, we discuss Location Privacy as applicable to
   Mobile IPv6.  We document the concerns arising from revealing Home
   Address to an on-looker and from disclosing Care of Address to a
   correspondent.

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

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


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

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


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

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-mip6-location-privacy-ps-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

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

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

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

ENCODING mime
FILE /internet-drafts/draft-ietf-mip6-location-privacy-ps-00.txt

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

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


--OtherAccess--

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

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

--NextPart--





From mip6-bounces@ietf.org Sun Oct 16 04:45:50 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ER49O-0005la-2l; Sun, 16 Oct 2005 04:45:50 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ER49F-0005lV-Jm
	for mip6@megatron.ietf.org; Sun, 16 Oct 2005 04:45:48 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA18488
	for <mip6@ietf.org>; Sun, 16 Oct 2005 04:45:34 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ER4KK-0004zB-5I
	for mip6@ietf.org; Sun, 16 Oct 2005 04:57:09 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id j9G8j3T06446; Sun, 16 Oct 2005 10:45:03 +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
	j9G8j22u013675; Sun, 16 Oct 2005 10:45:02 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200510160845.j9G8j22u013675@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: "James Kempf" <Kempf@docomolabs-usa.com>
Subject: Re: [Mip6] review of draft-ietf-mip6-bootstrapping-split-00.txt 
In-reply-to: Your message of Wed, 12 Oct 2005 11:03:03 PDT.
	<019f01c5cf57$30869d40$196115ac@dcml.docomolabsusa.com> 
Date: Sun, 16 Oct 2005 10:45:02 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
Cc: Gerardo Giaretta <Gerardo.Giaretta@tilab.com>, mip6@ietf.org,
	Kilian Weniger <Kilian.Weniger@eu.panasonic.com>,
	Vijay Devarapalli <vijayd@iprg.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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   What do other members of the WG think?
   
=> I fully agree! Local HA stuff is clearly out of scope.

Regards

Francis.Dupont@enst-bretagne.fr

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



From mip6-bounces@ietf.org Sun Oct 16 09:08:49 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ER8Ft-0007UW-0L; Sun, 16 Oct 2005 09:08:49 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ER8Fr-0007UJ-09
	for mip6@megatron.ietf.org; Sun, 16 Oct 2005 09:08:47 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01247
	for <mip6@ietf.org>; Sun, 16 Oct 2005 09:08:40 -0400 (EDT)
From: john.loughney@nokia.com
Received: from mgw-ext01.nokia.com ([131.228.20.93])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ER8Qy-0002WN-Pj
	for mip6@ietf.org; Sun, 16 Oct 2005 09:20:17 -0400
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
	by mgw-ext01.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id
	j9GD8SOE002077; Sun, 16 Oct 2005 16:08:34 +0300
Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sun, 16 Oct 2005 16:08:33 +0300
Received: from esebe100.NOE.Nokia.com ([172.21.138.118]) by
	esebh103.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sun, 16 Oct 2005 16:08:35 +0300
Content-class: urn:content-classes:message
Subject: RE: [Mip6] review of draft-ietf-mip6-dsmip-problem-00.txt
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Sun, 16 Oct 2005 16:08:33 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.5.7233.31
Message-ID: <1AA39B75171A7144A73216AED1D7478D012892D4@esebe100.NOE.Nokia.com>
Thread-Topic: [Mip6] review of draft-ietf-mip6-dsmip-problem-00.txt
Thread-Index: AcXP8QKh9eGRiNbIRvSZ9lvhHOsABAAQuU+QAIeYT8A=
To: <G.Tsirtsis@flarion.com>, <jari.arkko@kolumbus.fi>, <mip6@ietf.org>
X-OriginalArrivalTime: 16 Oct 2005 13:08:35.0012 (UTC)
	FILETIME=[B70C6040:01C5D252]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 43317e64100dd4d87214c51822b582d1
Content-Transfer-Encoding: quoted-printable
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

George,

First, I agree that these are separate problems - but are you saying
that they should be addressed seperately in the document, or in separate
documents?  Even if they are split into separate documents, NAT
traversal
will be an issue.  I don't mind if the DSMIP document points to another
document, it will at least need to discuss some operation issues of
running
a dual stack mobile node when a NAT is present.  I'm fine if it just
points
to the NAT traversal document with some operational considerations for
the
dual stack node.

John

>-----Original Message-----
>From: mip6-bounces@ietf.org [mailto:mip6-bounces@ietf.org] On=20
>Behalf Of ext Tsirtsis, George
>Sent: 13 October, 2005 23:32
>To: Jari Arkko; Mobile IPv6 Mailing List
>Subject: RE: [Mip6] review of draft-ietf-mip6-dsmip-problem-00.txt
>
>Jari,
>
>It might be a good idea to separate v4 to v6 migration and NAT=20
>type issues from enabling MIP to creating bindings for v4 and v6 HoAs.
>
>The v4 to v6 transition and NAT issue has nothing to do with=20
>the version of the HoA; instead it is purely about how to run=20
>a given protocol/application *over* v4 and v6 based networks=20
>as well as over NATs and other such devices.=20
>
>In contrast, the dsmip problem described in the problem=20
>statement is about allowing a single signaling protocol to=20
>create and manipulate v4 and v6 HoAs.
>
>What I am arguing is that these as separable/orthogonal=20
>problems and it will be easier to treat them as such.=20
>
>
>Regards
>George
>
>> -----Original Message-----
>> From: mip6-bounces@ietf.org [mailto:mip6-bounces@ietf.org] On Behalf=20
>> Of Jari Arkko
>> Sent: Thursday, October 13, 2005 8:17 AM
>> To: Mobile IPv6 Mailing List
>> Subject: [Mip6] review of draft-ietf-mip6-dsmip-problem-00.txt
>>=20
>>=20
>> I reviewed this draft. Overall, its pretty easy to agree=20
>with what is=20
>> said. My main concern is that the draft is taking a=20
>relatively narrow=20
>> view into this problem. For instance, its likely that we need NATs,=20
>> corporate VPN compatibility, various extra mobility features=20
>developed=20
>> over the years, etc. as well as basic mobility. How do we achieve=20
>> this? And I don't think the real issue is minor differences=20
>in amount=20
>> of signaling, even if us researchers and engineers would like to=20
>> optimize everything... the real issue is getting a mobility solution=20
>> that works, no matter what environment you are in. I don't mean that=20
>> we necessarily need to develop everything right now, but I'd like to=20
>> see a description of the whole problem, and some ideas about how we=20
>> are going about addressing it.
>>=20
>> More comments below:
>>=20
>> >    This draft discusses the issues associated with mobility
management
>> >    for dual stack mobile nodes. Currently, two mobility management
>> >    protocols are defined for IPv4 and IPv6. Deploying both=20
>in a dual
>> >    stack mobile node introduces a number of inefficiencies
>>=20
>> I do not think this is just about ineffiency! We have no=20
>connectivity=20
>> or at least session survivability without some form of interworking=20
>> between different mobility mechanisms.
>>=20
>> > 2.4. The impossibility of maintaining connectivity
>> >
>> >    A final point to consider is that even if both mobility
>> protocols are
>> >    supported by a mobile node seamless connectivity would
>> not in fact be
>> >    guarantied since that also depends on the IPv4/IPv6
>> capabilities of
>> >    the networks the mobile is visiting i.e.: a dual stack node
>> >    attempting to connect via a IPv4 only network would not
>> be able to
>> >    maintain connectivity of its IPv6 applications and vice versa.
>>=20
>> This, to me, is the main problem in fact. If you assume you have v4=20
>> and v6 everywhere, why not just use Mobile IPv6? But the reality is=20
>> that we'll find ourselves more or less forever locked in a situation=20
>> where there are at least some networks that are v4 only. From a=20
>> commercial standpoint, we do not want to deploy technology that only=20
>> works some of the time, so I think people are looking for solutions=20
>> that work in all cases. And "work" =3D "works for the user's ongoing=20
>> sessions", not just "we can send mobility protocol signaling=20
>> messages".
>>=20
>> >    - it should be possible to create IPv4 extensions to
>> Mobile IPv6 so
>> >    that a dual stack mobile node can register its IPv4 and
>> IPv6 HoAs to
>> >    a dual stack Home Agent using MIPv6 signaling only.
>>=20
>> >    - it should be possible to create IPv6 extensions to
>> MIPv4 so that a
>> >    dual stack mobile node can register its IPv4 and IPv6
>> HoAs to a dual
>> >    stack Home Agent using MIPv4 signaling only.
>>=20
>> >    - it should also be possible to extend MIPv4 and MIPv6 so that a
>> >    mobile can register a single CoA (IPv4 or IPv6) to which
>> IPv4 and/or
>> >    IPv6 packets can be diverted to.
>>=20
>> Yes. These are all things that we should do, I think.
>>=20
>> But this list is also quite short in comparison to what has been=20
>> documented elsewhere, e.g., draft-larsson-v6ops-mip-scenarios.
>> E.g. transition mechanism-based approaches have not been mentioned.
>>=20
>> Also, there's a body of work that relates to various kinds of=20
>> additions over the basic protocols. It would be interesting to=20
>> understand the bigger picture of how we are going to use the=20
>> additional components (RO, fast handovers, various auth=20
>schemes, ...)=20
>> in a mixed environment.
>>=20
>> > 2.2. Operational burdens
>> >
>> >    As mentioned earlier, deploying both protocols will
>> require managing
>> >    both protocols in the mobile node and the home agent. This adds
>> >    significant operational issues for the network=20
>operator. It would
>> >    certainly require the network operator to have deep
>> knowledge in both
>> >    protocols. This might add a significant cost for
>> deployment that an
>> >    operator cannot justify due to the lack of substantial gains.
>>=20
>> Duplicate user credentials are a possibility at this time=20
>(e.g. MIPv4=20
>> shared secrets, MIP6 auth option, MIPv6 IKE/IPsec SAs or keys,=20
>> IKEv2-based EAP credentials, ...). Probably worthwhile to=20
>mention as a=20
>> separate item.
>>=20
>> > 4. References
>>=20
>> References to other work in this space might be appropriate.=20
>> Can't give you a good list, but I'm sure there are some items that=20
>> could be mentioned here. In fact, even the existing=20
>references in the=20
>> text such as [MIPv4] are not listed here.
>>=20
>> --Jari
>>=20
>>=20
>> _______________________________________________
>> Mip6 mailing list
>> Mip6@ietf.org
>> https://www1.ietf.org/mailman/listinfo/mip6
>>=20
>
>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>This email may contain confidential and privileged material=20
>for the sole use  of the intended recipient.  Any review or=20
>distribution by others is strictly  prohibited.  If you are=20
>not the intended recipient please contact the sender  and=20
>delete all copies.
>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>
>
>_______________________________________________
>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 Oct 16 16:40:12 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ERFIi-0007hP-UI; Sun, 16 Oct 2005 16:40:12 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ERFIh-0007hE-KV
	for mip6@megatron.ietf.org; Sun, 16 Oct 2005 16:40:11 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21833
	for <mip6@ietf.org>; Sun, 16 Oct 2005 16:40:04 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ERFTs-000501-7h
	for mip6@ietf.org; Sun, 16 Oct 2005 16:51:45 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id j9GKdVl31792; Sun, 16 Oct 2005 22:39:31 +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
	j9GKdVEj015109; Sun, 16 Oct 2005 22:39:31 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200510162039.j9GKdVEj015109@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: "Kilian Weniger" <Kilian.Weniger@eu.panasonic.com>
In-reply-to: Your message of Tue, 11 Oct 2005 15:09:34 +0200.
	<4D2F935F08D41A4C8866693F4F0D7C4F58DBC3@lan-ex-01.panasonic.de> 
Date: Sun, 16 Oct 2005 22:39:31 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 36c793b20164cfe75332aa66ddb21196
Cc: mip6@ietf.org
Subject: [Mip6] Re: draft-dupont-mip6-dhaadharmful-00.txt 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   starting the discussions about your draft:
   
=> in fact I'd like to raise some questions:
 - is a dynamic home agent address discovery mechanism a good thing?
   (I am serious: I know that some people prefer a home agent assignment
    mechanism)
 - is it possible to make the current mechanism secure? (IMHO no but
   any counter-example is wellcome)
 - is the insecurity of the current mechanism enough to phase it out?
   (I am not alone to think so, at least the bootstrap DT shares this
    opinion)
 - is the DNS SRV RR the best candidate to replace the current mechanism?
   (today it is the only candidate... IMHO we can't phase out something
    without proposing a better solution)

   - Section A.3 lists threats and countermeasures for the DNS-based

=> note that sections A.x are from the bootstrapping I-D so if you'd like
to discuss them for themselves this is not the right place (i.e., right
mailing list but wrong message subject).

   procedure if no authentication of the DNS server by the client or of the
   client by the server is done. E.g., the IKEv2 transaction with a bogus
   HA address (obtained from an attacker during DHAAD) would fail because
   the HA has to present a certificate to MN during IKEv2 transaction and
   the IKE_AUTH message is protected by an authenticator calculated using
   the public key in the certificate.

=> this is an explanation of why the current mechanism is not a security
disaster, not how it is secure.

   Why are the described countermeasures
   not sufficient to secure the bootstrapping procedure if no
   authentication of the DNS server by the client or of the client by the
   server is done, i.e., why is DNSSEC or TSIG/TKEY additionally needed? 
   
=> DNSSEC is needed to make it secure: this provides an extra property,
not necessary but very wellcome.

   - Do the same countermeasures also apply to the anycast-based DHAAD?

=> yes.

   If so, is the anycast-based DHAAD still considered harmful?

=> yes because it can't be made secure, even its intrinsic property is
not a disaster (note that if it was the IESG should have rejected it
before RFC 3775 publication).

   Is there an
   implicit assumption that it is easier for an attacker to setup a bogus
   HA with a certificate which seems trustworthy to the MN

=> everyday experience with SSL/TLS shows certificates are too enough
misused so it is better to have a secure mechanism than a fully insecure
mechanism the results should be checked and never trusted.

   than to setup a bogus DNS server with DNSSEC or TSIG/TKEY which
   seems trustworthy to the MN?
   
=> this is the advantage of DNS over X.500: both are directories but
nobody still argues that X.500 is simpler than DNS. And with DNSSEC
you have still the certificate check.

   - Assuming that no authentication of the DNS server by the client or of

=> I believe you don't understand DNSSEC (I recommend the intro I-D)

   the client by the server is done, is there any benefit in terms of
   security of using the DNS-based procedure instead of using the
   anycast-based DHAAD procedure, i.e., are there any threats specific to
   the anycast-based procedure?
   
=> yes, DNSSEC is mainly about the authentication of values, not servers.
Both are not possible with anycast.

   Assuming that the anycast-based DHAAD procedure is not considered
   harmful (I guess the assumption is wrong when I look at the title of
   your draft ;), I think one should carefully think about pros and cons of
   both procedures, e.g.,
   
=> if you don't propose a way to make the anycast-based DHAAD procedure
secure you are simply wasting our time.

   - A benefit of the anycast-based procedure (which is not realted to
   security) is that load conditions can faster be considered for load
   balancing. Of course, load balancing can also be achieved by other
   means, e.g., by informing the MN to bootstrap with another HA after it
   has bootstrapped with a heavily loaded HA, but I think one should again
   carefully consider pros and cons of such solutions.
   
=> perhaps but this is a better argument if you apply it to assignment.

   - A benefit of the DNS-based solution is that the prefix of the HA does
   not need to be pre-configured on the MN. 
   
   One approach to get both benefits would be to combine both solutions,
   i.e., the MN obtains the HA prefix from DNS and discovers the HA address
   via anycast.

=> this is what is implemented by some of us but operators don't like
the current mechanism: some want to change it for something which can be
made secure, some want to change it for an assignment mechanism. Of course
some are in the middle because assignment won't be available in all cases.

   In this case it may be beneficial to standardize both
   procedures. What do you think?
   
=> two procedures to do the same thing are not the right solution.

Regards

Francis.Dupont@enst-bretagne.fr

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



From mip6-bounces@ietf.org Mon Oct 17 04:54:19 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ERQl9-0001KE-9W; Mon, 17 Oct 2005 04:54:19 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ERQl2-0001DX-Gu
	for mip6@megatron.ietf.org; Mon, 17 Oct 2005 04:54:16 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA26530
	for <mip6@ietf.org>; Mon, 17 Oct 2005 04:54:05 -0400 (EDT)
Received: from cluster-d.mailcontrol.com ([217.69.20.190]
	helo=rly36d.srv.mailcontrol.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ERQwK-00068U-EY
	for mip6@ietf.org; Mon, 17 Oct 2005 05:05:53 -0400
Received: from hhe500-02.hbg.de.pan.eu (gate.eu.panasonic.com [194.173.20.12])
	by rly36d.srv.mailcontrol.com (MailControl) with SMTP id
	j9H8roeQ019505; Mon, 17 Oct 2005 09:53:50 +0100
Received: from eundadmi01.pan.eu(10.100.96.64) by hhe500-02.hbg.de.pan.eu via
	smtp id 4109_39915d4e_3eec_11da_837a_0030482aac25;
	Mon, 17 Oct 2005 10:58:45 +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 2005101710524194-363421 ;
	Mon, 17 Oct 2005 10:52:41 +0200 
Received: from localhost ([127.0.0.1]) by VPN-MRelay-01.PRDCG.Panasonic.de;
	Mon, 17 Oct 2005 10:54:46 +0200
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Subject: RE: [Mip6] review of draft-ietf-mip6-bootstrapping-split-00.txt
Thread-Topic: [Mip6] review of draft-ietf-mip6-bootstrapping-split-00.txt
Thread-Index: AcXPVzeswu524TPASXmAIIP7S7OTmQBdFOWw
To: "James Kempf" <Kempf@docomolabs-usa.com>
Message-ID: <4D2F935F08D41A4C8866693F4F0D7C4F58DF82@lan-ex-01.panasonic.de>
Date: Mon, 17 Oct 2005 10:52:35 +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-05-40-01 (www.mailcontrol.com) on 10.68.0.146
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 850245b51c39701e2700a112f3032caa
Content-Transfer-Encoding: quoted-printable
Cc: Gerardo Giaretta <Gerardo.Giaretta@TILAB.COM>, mip6@ietf.org,
	Vijay Devarapalli <vijayd@iprg.nokia.com>, Francis.Dupont@enst-bretagne.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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org


I agree that the split scenario draft says that local HA assignment is
out of scope (although it mentions benefits of local HAs and describes
two examples how a mobile node can be provided with a local HA).=20

My assumption was that local (or nearby) HA assignment is possible with
an implementation complying to the split scenario draft, because the
protocol as described fundamentally supports bootstrapping with any HA
(including local or nearby HAs). Even if a local HA naming convention is
not given in the draft, an operator might, e.g., use its own
local/nearby HA naming convention and provide local/nearby HA service to
its users (or even for roaming users) to improve efficiency. Or a user
on a trip in another country (manually?) discovers a "nearby" HA by
using the country code suffix and bootstraps with this HA. Or would you
say that this does not comply with the split scenario draft?=20

Please don't get me wrong, I fully support the bootstrapping split
scenario solution. I just think that, provided that the assumption above
is correct, including a short note about location privacy in the seccons
section would be good (and I think we already agreed that the issue only
exists in specific scenarios). If the assumption above is not correct, I
agree to the short note James suggested.

Regards,

Kilian


> -----Original Message-----
> From: James Kempf [mailto:Kempf@docomolabs-usa.com]=20
> Sent: Mittwoch, 12. Oktober 2005 20:03
> To: Kilian Weniger
> Cc: Gerardo Giaretta; mip6@ietf.org; Vijay Devarapalli
> Subject: Re: [Mip6] review of=20
> draft-ietf-mip6-bootstrapping-split-00.txt
>=20
> No, I do not agree to this extensive note.
>=20
> The split scenerio draft specifically says that the details=20
> of local home=20
> agent allocation are *out of scope*. I don't see the point of=20
> a detailed=20
> security analysis of something that is not covered in the=20
> draft. If you or=20
> someone else writes a draft that says how to do local home=20
> agent allocation=20
> in the split scenerio, then that is the right place for an extensive=20
> analysis.
>=20
> What do other members of the WG think?
>=20
>             jak
>=20
> ----- Original Message -----=20
> From: "Kilian Weniger" <Kilian.Weniger@eu.panasonic.com>
> To: "James Kempf" <Kempf@docomolabs-usa.com>
> Cc: "Gerardo Giaretta" <Gerardo.Giaretta@TILAB.COM>;=20
> <mip6@ietf.org>; "Vijay=20
> Devarapalli" <vijayd@iprg.nokia.com>
> Sent: Wednesday, October 12, 2005 3:02 AM
> Subject: RE: [Mip6] review of=20
> draft-ietf-mip6-bootstrapping-split-00.txt
>=20
>=20
>=20
> > jak>> Just knowing the victim's selection policy is not
> > sufficient. The
> > attacker would also have to know the serving ASP's local home agent
> > allocation policy - does the serving ASP allocate home agents
> > or not? If it
> > doesn't, then the attacker would incorrectly conclude that
> > Alice is in Palo
> > Alto when she is actually in Tucson when it saw the DNS entry
> > change to a
> > HoA that was provided by Bob' Mobility Service in Palo Alto.
>=20
> I think we are just arguing about the accuracy of location information
> revealed. I agree that if the eavesdropper does not know=20
> whether the ASP
> provides local HA service, there is some uncertainty, but IMO some
> location information can still be revealed (with lower=20
> accuracy). In the
> scenario I described, the victim always selects a "nearby" HA (to
> improve routing efficiency), i.e., one that is in or at least close to
> the serving ASP (in the worst case the HA is only in the same country
> than the serving ASP). Hence, the eavesdropper can conclude that the
> victim is in or somewhere close the serving ASP. I agree that the
> accuracy of the location information might not be known by the
> eavesdropper, at least as long as it does not have additional policy
> information.
>=20
> >
> > jak>> In addition, how does the attacker know the victim's
> > selection policy?
>=20
> Yes, that's another issue. One possibility may be that a=20
> provider has a
> default policy, which the eavesdropper can find out.
> Anyhow, I think the main point is that we describe the=20
> location privacy
> issue in the draft, so that others are aware of it and, e.g.,=20
> try to not
> disclose the policy.
>=20
> > What I was trying to suggest is that, short of having the
> > victim tell the
> > attacker (which is of course possible, for example, through=20
> a spyware
> > infection), the attacker would need to observe changes in the
> > victim's DNS
> > entry over time and correlate that with information on the
> > local home agent
> > allocation policy of the serving ASP.
>=20
> o.k., I see. I agree that's one way, but maybe not the only=20
> one (as you
> mentioned yourself).
>=20
> > jak>> How does this provide any information about the
> > victim's location? It
> > depends on whether the victim actually uses the local home
> > agent or not,
> > which, as you mention above, depends on the victim's local=20
> home agent
> > selection policy. If the victim doesn't use ha.t-mobile.de,
> > but rather
> > ha.t-mobile.us, then there's no problem.
>=20
> Yes, but I was assuming there would be enough MSPs in=20
> Germany, of which
> at least one would provide an HA bootstrapping service to the=20
> victim (I
> think that's not a far-fetched assumption). Then there is a possible
> issue.
> The main point I tried to make clear is that an issue may exist even
> without *local HA discovery*, since *nearby HA discovery* might be
> possible with the solution. One way could be country code suffixes
> (although I agree that the possibly revealed location=20
> information would
> be of low accuracy).
>=20
> >
> > jak>> Anyway, Gerardo wants us to come to agreement on this
> > now so that we
> > can wrap up the draft prior to the IETF 64 drafts deadline.
> > How about the
> > following:
> >
> > 1) We put a two sentence paragraph in the SecCons section of
> > draft-mip6-bootstrapping-split that says the following:
> >
> >     Allocation of a local home agent raises a possible risk
> > of location
> > privacy compromise. Since the details of how this threat
> > might be actualized
> > depend on how a local home agent is allocated, and local home agent
> > allocation is out of scope for this document, the Security
> > Considerations
> > section of specifications that describe or include local home agent
> > allocation should be consulted for details.
> >
> > 2) We include a detailed description of the location privacy
> > threat and how
> > to counter it in the SecCons section of
> > draft-mip6-bootstrapping-integrated,
> > which does include a mechanism for local home agent allocation.
>=20
> If the question is whether to include nothing or a short=20
> note, I prefer
> the short note of course. However, I tried to make clear that=20
> IMO there
> can be an issue with the allocation of "nearby", non-local HAs (with
> "local HA" defined as HA in serving ASP network and "nearby=20
> HA" as HA in
> network close to serving ASP network). This issue would be=20
> *specific to
> the split scenario*. Hence, if you and others agree to the nearby HAs
> issue, this should be reflected by the note IMO. However, in=20
> this case I
> would prefer to add a more detailed description about the=20
> issue specific
> to the split scenario to the draft - if not now (because of the
> deadline) then at least in a later revision.
>=20
> But why not use the text initially proposed by you, which has already
> been agreed by you and Vijay. We can modify it slightly=20
> considering the
> recent (IMO fruitful) discussions. We can still refine it later, if
> necessary. How about this:
>=20
>    Updating the mobile node's FQDN in the DNS with the mobile node's
>    home address has the potential to expose some information about
>    the mobile node's location to other nodes if the home agent
>    selected by the mobile node is local or nearby, i.e., it is in or
>    close to the serving network access provider's network.
>=20
>    For three reasons, the risk here is not as deep as known from Route
>    Optimization mode [draft-koodli-mip6-location-privacy-00.txt].
>    First, other nodes usually do not know whether the mobile node's
>    home address belongs to a home agent that is local, nearby or
>    remote for the mobile node and, hence, whether the mobile node is
>    really at the location corresponding to the home address. Second,
>    the mobile node (if using reverse tunneling) will effectively
>    appear to be at a fixed topological location in the mobility
>    service provider's as long as it does not bootstrap again with a
>    different home agent in a different network and request DNS update
>    subsequently. Third, depending on the deployment scenario, the
>    geographical area covered by a local home agent (being the "most
>    local" home agent) may be much larger than the area covered by an
>    access router. Since the accuracy of the location derivable from
>    the address decreases with increasing coverage, the accuracy may be
>    lower. In case the HA is only nearby, but not local, the accuracy
>    may be even lower.
>=20
>    However, the risk may be higher if additional information is known.
>    E.g., the mobile node's home agent selection policy and the home
>    agent allocation policy of ASPs can provide information about
>    whether an home agent is local, nearby or remote for the mobile
>    node. If, for instance, the mobile node's home agent selection
>    policy is to bootstrap with a new local home agent as soon as
>    moving to another network to improve routing efficiency of future
>    communication sessions in Bi-directional Tunneling mode, other
>    nodes being aware of the policies may be able to track mobile
>    node's movement to some extent by constantly querying mobile
>    node's DNS entry.
>=20
>    To mitigate the risk, the mobile node should either not request DNS
>    update or be careful to select a home agent that is local=20
> or nearby.
>    Furthermore, the disclosure of related policy information such as
>    mobile node's home agent selection policy and the home agent
>    allocation policy of ASPs should be carefully considered.
>=20
>=20
>=20
> Regards,
>=20
> Kilian
>=20
>=20
>=20
>=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 Mon Oct 17 05:08:17 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ERQyf-0005wq-9D; Mon, 17 Oct 2005 05:08:17 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ERQye-0005w5-ES
	for mip6@megatron.ietf.org; Mon, 17 Oct 2005 05:08:16 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA27345
	for <mip6@ietf.org>; Mon, 17 Oct 2005 05:08:09 -0400 (EDT)
Received: from cluster-d.mailcontrol.com ([217.69.20.190]
	helo=rly21d.srv.mailcontrol.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ERR9v-0006aH-Ue
	for mip6@ietf.org; Mon, 17 Oct 2005 05:19:57 -0400
Received: from hhe500-02.hbg.de.pan.eu (gate.eu.panasonic.com [194.173.20.12])
	by rly21d.srv.mailcontrol.com (MailControl) with SMTP id
	j9H982O9016938; Mon, 17 Oct 2005 10:08:02 +0100
Received: from eundadmi01.pan.eu(10.100.96.64) by hhe500-02.hbg.de.pan.eu via
	smtp id 4118_35545e96_3eee_11da_914b_0030482aac25;
	Mon, 17 Oct 2005 11:12:57 +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 2005101711051993-364595 ;
	Mon, 17 Oct 2005 11:05:19 +0200 
Received: from localhost ([127.0.0.1]) by VPN-MRelay-01.PRDCG.Panasonic.de;
	Mon, 17 Oct 2005 11:07:26 +0200
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Thread-Topic: draft-dupont-mip6-dhaadharmful-00.txt 
Thread-Index: AcXSkdFN0tLbK7HvSlex5Sa6WU31rwAZlYaw
To: <Francis.Dupont@enst-bretagne.fr>, "James Kempf" <Kempf@docomolabs-usa.com>
Message-ID: <4D2F935F08D41A4C8866693F4F0D7C4F58DF8D@lan-ex-01.panasonic.de>
Date: Mon, 17 Oct 2005 11:05:16 +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-05-40-01 (www.mailcontrol.com) on 10.68.0.131
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Content-Transfer-Encoding: quoted-printable
Cc: mip6@ietf.org
Subject: [Mip6] RE: draft-dupont-mip6-dhaadharmful-00.txt 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org


Francis, James, thanks for the explanations. Note that I didn't say that
DHAAD is secure or can be made secure. I was just asking about the
reasons why DHAAD is considered harmful, because I couldn't find many
reasons in the draft. Maybe it would be good to include the reasons you
provided in the last mails in the draft?

Regards,

Kilian



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



From mip6-bounces@ietf.org Mon Oct 17 05:45:34 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ERRYj-0000L5-UC; Mon, 17 Oct 2005 05:45:33 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ERRYj-0000L0-02
	for mip6@megatron.ietf.org; Mon, 17 Oct 2005 05:45:33 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA00095
	for <mip6@ietf.org>; Mon, 17 Oct 2005 05:45:25 -0400 (EDT)
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ERRk0-0007wn-Sm
	for mip6@ietf.org; Mon, 17 Oct 2005 05:57:14 -0400
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id j9H9Ca626398;
	Mon, 17 Oct 2005 02:12:36 -0700
X-mProtect: <200510170912> Nokia Silicon Valley Messaging Protection
Received: from esdhcp0352.research.nokia.com (172.21.35.2,
	claiming to be "[127.0.0.1]")
	by darkstar.iprg.nokia.com smtpdC2nx7m; Mon, 17 Oct 2005 02:12:34 PDT
Message-ID: <4353729D.8000400@iprg.nokia.com>
Date: Mon, 17 Oct 2005 02:45:01 -0700
From: Vijay Devarapalli <vijayd@iprg.nokia.com>
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
Subject: Re: [Mip6] Re: draft-dupont-mip6-dhaadharmful-00.txt
References: <200510162039.j9GKdVEj015109@givry.rennes.enst-bretagne.fr>
In-Reply-To: <200510162039.j9GKdVEj015109@givry.rennes.enst-bretagne.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Content-Transfer-Encoding: 7bit
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Francis Dupont wrote:
>  - is the insecurity of the current mechanism enough to phase it out?
>    (I am not alone to think so, at least the bootstrap DT shares this
>     opinion)

I dont the bootstrap DT ever expressed this opinion. for
running DHAAD, the MN needs to be configured with the home
prefix. we wanted a solution with minimal configuration on
the MN. thats why DNS was picked. not just because DHAAD
is not secure.

I anyway dont have illusions about secure DNS being used.
in most cases the security for DNS based HA lookup and
running DHAAD to obtain a list of home agents might be the
same.

now, back to your discussions. :)

Vijay


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



From mip6-bounces@ietf.org Mon Oct 17 16:46:36 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ERbsS-00082g-1W; Mon, 17 Oct 2005 16:46:36 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ERbsO-0007yw-8Z
	for mip6@megatron.ietf.org; Mon, 17 Oct 2005 16:46:34 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA27470
	for <mip6@ietf.org>; Mon, 17 Oct 2005 16:46:24 -0400 (EDT)
Received: from mail.flarion.com ([63.103.94.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ERc3h-0000eF-8R
	for mip6@ietf.org; Mon, 17 Oct 2005 16:58:17 -0400
Received: from mail pickup service by mail.flarion.com with Microsoft SMTPSVC;
	Mon, 17 Oct 2005 16:40:27 -0400
Received: from ftmailserver.flariontech.com ([10.10.1.140]) by
	mail.flarion.com with Microsoft SMTPSVC(5.0.2195.6713);
	Mon, 17 Oct 2005 09:25:23 -0400
Content-Class: urn:content-classes:message
Subject: RE: [Mip6] review of draft-ietf-mip6-dsmip-problem-00.txt
Date: Mon, 17 Oct 2005 09:25:26 -0400
Message-ID: <A11736FE943F1A408F8BBB1B9F5FE8AD01D5B83E@ftmailserver.flariontech.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Thread-Topic: [Mip6] review of draft-ietf-mip6-dsmip-problem-00.txt
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
Thread-Index: AcXP8QKh9eGRiNbIRvSZ9lvhHOsABAAQuU+QAIeYT8AAMqd04A==
From: "Tsirtsis, George" <G.Tsirtsis@flarion.com>
To: <john.loughney@nokia.com>, <jari.arkko@kolumbus.fi>, <mip6@ietf.org>
X-OriginalArrivalTime: 17 Oct 2005 13:25:23.0328 (UTC)
	FILETIME=[3A76F000:01C5D31E]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 03fb21b15d5177c512a4caa19876f30a
Content-Transfer-Encoding: quoted-printable
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Hi John,

I actually think these are entirely orthogonal issues, in which case
they can be defined in different documents without referring to each
other.....but maybe we should first make sure we are talking about the
same thing.

For example, I am not sure what kind of NAT traversal issue we talking
about here? I do understand, however, the v4 to v6 transition issue
which goes like this:
MIP6 signaling running between an MN and an HA requires that IPv6
connectivity is available between that MN and that HA. If there is no
native IPv6 connectivity available then, we have an IPv4 to IPv6
transition issue; i.e., some form of tunneling or other transition
mechanism is required to provide the IPv6 path between the two entities.
As far as I can tell, this has nothing to do with what kind of HoAs are
handled by MIP6. Do you agree so far?

I am not sure what is the NAT traversal issue though...can anyone
illuminate?

Thanks
George

> -----Original Message-----
> From: john.loughney@nokia.com [mailto:john.loughney@nokia.com]=20
> Sent: Sunday, October 16, 2005 9:09 AM
> To: Tsirtsis, George; jari.arkko@kolumbus.fi; mip6@ietf.org
> Subject: RE: [Mip6] review of draft-ietf-mip6-dsmip-problem-00.txt
>=20
>=20
> George,
>=20
> First, I agree that these are separate problems - but are you=20
> saying that they should be addressed seperately in the=20
> document, or in separate documents?  Even if they are split=20
> into separate documents, NAT traversal will be an issue.  I=20
> don't mind if the DSMIP document points to another document,=20
> it will at least need to discuss some operation issues of=20
> running a dual stack mobile node when a NAT is present.  I'm=20
> fine if it just points to the NAT traversal document with=20
> some operational considerations for the dual stack node.
>=20
> John
>=20
> >-----Original Message-----
> >From: mip6-bounces@ietf.org [mailto:mip6-bounces@ietf.org] On
> >Behalf Of ext Tsirtsis, George
> >Sent: 13 October, 2005 23:32
> >To: Jari Arkko; Mobile IPv6 Mailing List
> >Subject: RE: [Mip6] review of draft-ietf-mip6-dsmip-problem-00.txt
> >
> >Jari,
> >
> >It might be a good idea to separate v4 to v6 migration and NAT
> >type issues from enabling MIP to creating bindings for v4=20
> and v6 HoAs.
> >
> >The v4 to v6 transition and NAT issue has nothing to do with
> >the version of the HoA; instead it is purely about how to run=20
> >a given protocol/application *over* v4 and v6 based networks=20
> >as well as over NATs and other such devices.=20
> >
> >In contrast, the dsmip problem described in the problem
> >statement is about allowing a single signaling protocol to=20
> >create and manipulate v4 and v6 HoAs.
> >
> >What I am arguing is that these as separable/orthogonal
> >problems and it will be easier to treat them as such.=20
> >
> >
> >Regards
> >George
> >
> >> -----Original Message-----
> >> From: mip6-bounces@ietf.org [mailto:mip6-bounces@ietf.org]=20
> On Behalf
> >> Of Jari Arkko
> >> Sent: Thursday, October 13, 2005 8:17 AM
> >> To: Mobile IPv6 Mailing List
> >> Subject: [Mip6] review of draft-ietf-mip6-dsmip-problem-00.txt
> >>=20
> >>=20
> >> I reviewed this draft. Overall, its pretty easy to agree
> >with what is
> >> said. My main concern is that the draft is taking a
> >relatively narrow
> >> view into this problem. For instance, its likely that we need NATs,
> >> corporate VPN compatibility, various extra mobility features=20
> >developed
> >> over the years, etc. as well as basic mobility. How do we achieve
> >> this? And I don't think the real issue is minor differences=20
> >in amount
> >> of signaling, even if us researchers and engineers would like to
> >> optimize everything... the real issue is getting a=20
> mobility solution=20
> >> that works, no matter what environment you are in. I don't=20
> mean that=20
> >> we necessarily need to develop everything right now, but=20
> I'd like to=20
> >> see a description of the whole problem, and some ideas=20
> about how we=20
> >> are going about addressing it.
> >>=20
> >> More comments below:
> >>=20
> >> >    This draft discusses the issues associated with mobility
> management
> >> >    for dual stack mobile nodes. Currently, two mobility=20
> management
> >> >    protocols are defined for IPv4 and IPv6. Deploying both
> >in a dual
> >> >    stack mobile node introduces a number of inefficiencies
> >>=20
> >> I do not think this is just about ineffiency! We have no
> >connectivity
> >> or at least session survivability without some form of interworking
> >> between different mobility mechanisms.
> >>=20
> >> > 2.4. The impossibility of maintaining connectivity
> >> >
> >> >    A final point to consider is that even if both mobility
> >> protocols are
> >> >    supported by a mobile node seamless connectivity would
> >> not in fact be
> >> >    guarantied since that also depends on the IPv4/IPv6
> >> capabilities of
> >> >    the networks the mobile is visiting i.e.: a dual stack node
> >> >    attempting to connect via a IPv4 only network would not
> >> be able to
> >> >    maintain connectivity of its IPv6 applications and vice versa.
> >>=20
> >> This, to me, is the main problem in fact. If you assume you have v4
> >> and v6 everywhere, why not just use Mobile IPv6? But the=20
> reality is=20
> >> that we'll find ourselves more or less forever locked in a=20
> situation=20
> >> where there are at least some networks that are v4 only. From a=20
> >> commercial standpoint, we do not want to deploy technology=20
> that only=20
> >> works some of the time, so I think people are looking for=20
> solutions=20
> >> that work in all cases. And "work" =3D "works for the user's =
ongoing=20
> >> sessions", not just "we can send mobility protocol signaling=20
> >> messages".
> >>=20
> >> >    - it should be possible to create IPv4 extensions to
> >> Mobile IPv6 so
> >> >    that a dual stack mobile node can register its IPv4 and
> >> IPv6 HoAs to
> >> >    a dual stack Home Agent using MIPv6 signaling only.
> >>=20
> >> >    - it should be possible to create IPv6 extensions to
> >> MIPv4 so that a
> >> >    dual stack mobile node can register its IPv4 and IPv6
> >> HoAs to a dual
> >> >    stack Home Agent using MIPv4 signaling only.
> >>=20
> >> >    - it should also be possible to extend MIPv4 and=20
> MIPv6 so that a
> >> >    mobile can register a single CoA (IPv4 or IPv6) to which
> >> IPv4 and/or
> >> >    IPv6 packets can be diverted to.
> >>=20
> >> Yes. These are all things that we should do, I think.
> >>=20
> >> But this list is also quite short in comparison to what has been
> >> documented elsewhere, e.g., draft-larsson-v6ops-mip-scenarios.
> >> E.g. transition mechanism-based approaches have not been mentioned.
> >>=20
> >> Also, there's a body of work that relates to various kinds of
> >> additions over the basic protocols. It would be interesting to=20
> >> understand the bigger picture of how we are going to use the=20
> >> additional components (RO, fast handovers, various auth=20
> >schemes, ...)
> >> in a mixed environment.
> >>=20
> >> > 2.2. Operational burdens
> >> >
> >> >    As mentioned earlier, deploying both protocols will
> >> require managing
> >> >    both protocols in the mobile node and the home agent.=20
> This adds
> >> >    significant operational issues for the network
> >operator. It would
> >> >    certainly require the network operator to have deep
> >> knowledge in both
> >> >    protocols. This might add a significant cost for
> >> deployment that an
> >> >    operator cannot justify due to the lack of substantial gains.
> >>=20
> >> Duplicate user credentials are a possibility at this time
> >(e.g. MIPv4
> >> shared secrets, MIP6 auth option, MIPv6 IKE/IPsec SAs or keys,
> >> IKEv2-based EAP credentials, ...). Probably worthwhile to=20
> >mention as a
> >> separate item.
> >>=20
> >> > 4. References
> >>=20
> >> References to other work in this space might be appropriate.
> >> Can't give you a good list, but I'm sure there are some items that=20
> >> could be mentioned here. In fact, even the existing=20
> >references in the
> >> text such as [MIPv4] are not listed here.
> >>=20
> >> --Jari
> >>=20
> >>=20
> >> _______________________________________________
> >> Mip6 mailing list
> >> Mip6@ietf.org
> >> https://www1.ietf.org/mailman/listinfo/mip6
> >>=20
> >
> =
>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >This email may contain confidential and privileged material
> >for the sole use  of the intended recipient.  Any review or=20
> >distribution by others is strictly  prohibited.  If you are=20
> >not the intended recipient please contact the sender  and=20
> >delete all copies.
> =
>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >
> >
> >_______________________________________________
> >Mip6 mailing list
> >Mip6@ietf.org
> >https://www1.ietf.org/mailman/listinfo/mip6
> >
>=20

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D
This email may contain confidential and privileged material for the sole =
use
 of the intended recipient.  Any review or distribution by others is =
strictly
 prohibited.  If you are not the intended recipient please contact the =
sender
 and delete all copies.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D


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



From mip6-bounces@ietf.org Mon Oct 17 21:44:03 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ERgWJ-0007Lg-7G; Mon, 17 Oct 2005 21:44:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ERgWH-0007KK-Nc
	for mip6@megatron.ietf.org; Mon, 17 Oct 2005 21:44:01 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA23193
	for <mip6@ietf.org>; Mon, 17 Oct 2005 21:43:54 -0400 (EDT)
Received: from usaga01-in.huawei.com ([12.129.211.51] helo=huawei.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ERghe-0003a7-O3
	for mip6@ietf.org; Mon, 17 Oct 2005 21:55:51 -0400
Received: from huawei.com (usaga01-in [172.18.4.6])
	by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0IOJ0078W8NISP@usaga01-in.huawei.com> for
	mip6@ietf.org; Mon, 17 Oct 2005 18:40:30 -0700 (PDT)
Received: from huawei.com ([172.17.1.218])
	by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0IOJ00B1W8NHDS@usaga01-in.huawei.com> for
	mip6@ietf.org; Mon, 17 Oct 2005 18:40:30 -0700 (PDT)
Received: from [172.24.1.3] (Forwarded-For: [172.24.2.12])
	by szxmc02-in.huawei.com (mshttpd); Tue, 18 Oct 2005 09:43:48 +0800
Date: Tue, 18 Oct 2005 09:43:48 +0800
From: mayuzhi 03573 <myz@huawei.com>
Subject: [mip6]draft-yuchi-mip6-mntomn-improve-00
To: mip6@ietf.org
Message-id: <eb324ef05e.ef05eeb324@huawei.com>
MIME-version: 1.0
X-Mailer: iPlanet Messenger Express 5.2 HotFix 1.25 (built Mar  3 2004)
Content-type: text/plain; charset=us-ascii
Content-language: zh-CN
Content-transfer-encoding: 7BIT
Content-disposition: inline
X-Accept-Language: zh-CN
Priority: normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Content-Transfer-Encoding: 7BIT
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Dear  all,
  I have submitted a new internet draft to the mip6 working group. Abstract of this draft is as follow:
Any node communicating with a mobile node in Mobile IPv6 is referred to as a "correspondent node" of the mobile node, and may itself be 
either a stationary node or a mobile node. Communication between mobile nodes has additional complexity. This document specifies a 
solution to improve communication procedure between mobile nodes.
A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-yuchi-mip6-mntomn-improve-00.txt

 I would appreciate any feedback and comments.

Regards,
Yuzhi Ma


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



From mip6-bounces@ietf.org Tue Oct 18 00:58:18 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ERjYI-0003MI-Pk; Tue, 18 Oct 2005 00:58:18 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ERjYH-0003M1-31
	for mip6@megatron.ietf.org; Tue, 18 Oct 2005 00:58:17 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA02913
	for <mip6@ietf.org>; Tue, 18 Oct 2005 00:58:08 -0400 (EDT)
Received: from smtp.cce.hp.com ([161.114.21.23] helo=ccerelrim02.cce.hp.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ERjji-0008Tf-KD
	for mip6@ietf.org; Tue, 18 Oct 2005 01:10:08 -0400
Received: from ccerelrim02.cce.hp.com (localhost [127.0.0.1])
	by receive-from-antispam-filter (Postfix) with SMTP id 5BF7633514;
	Mon, 17 Oct 2005 23:56:44 -0500 (CDT)
Received: from mailstation.cce.hp.com (mailstation.cce.hp.com [161.114.20.124])
	(using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits))
	(No client certificate requested)
	by ccerelrim02.cce.hp.com (Postfix) with ESMTP id 269E333186;
	Mon, 17 Oct 2005 23:54:19 -0500 (CDT)
Received: from [192.168.1.100] (c-24-91-248-5.hsd1.ma.comcast.net
	[24.91.248.5]) by mailstation.cce.hp.com (Postfix) with ESMTP
	id CDA004728; Mon, 17 Oct 2005 23:53:02 -0500 (CDT)
Message-ID: <43547FC3.7050503@hp.com>
Date: Tue, 18 Oct 2005 00:53:23 -0400
From: Brian Haley <Brian.Haley@hp.com>
Organization: Linux and Open Source Lab
User-Agent: Thunderbird 1.4.1 (Windows/20051006)
MIME-Version: 1.0
To: mayuzhi 03573 <myz@huawei.com>
Subject: Re: [mip6]draft-yuchi-mip6-mntomn-improve-00
References: <eb324ef05e.ef05eeb324@huawei.com>
In-Reply-To: <eb324ef05e.ef05eeb324@huawei.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-PMX-Version: 5.0.3.165339, Antispam-Engine: 2.1.0.0,
	Antispam-Data: 2005.10.17.39
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 34d35111647d654d033d58d318c0d21a
Content-Transfer-Encoding: 7bit
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

mayuzhi 03573 wrote:
>   I have submitted a new internet draft to the mip6 working group. Abstract of this draft is as follow:
> Any node communicating with a mobile node in Mobile IPv6 is referred to as a "correspondent node" of the mobile node, and may itself be 
> either a stationary node or a mobile node. Communication between mobile nodes has additional complexity. This document specifies a 
> solution to improve communication procedure between mobile nodes.
> A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-yuchi-mip6-mntomn-improve-00.txt
> 
>  I would appreciate any feedback and comments.
> 
> Regards,
> Yuzhi Ma

Hi Yuzhi,

I read your draft about improving MN to MN communications, it seems like 
a simple thing to implement for certain cases.

A few comments:

> 3.1. Mobile Correspondent Node 
> 
>    In order to differentiate between the two communicating mobile nodes, 
>    a new concept called "mobile correspondent node" is introduced.

I don't really like yet another name for a mobile node, you could just 
refer to it as the stationary mobile node.

>    The 
>    initiator of a correspondent registration acts as a mobile node, and 
>    the receiver acts as a mobile correspondent node. The receiver SHOULD 
>    NOT initiate a correspondent registration for the initiator, and both 
>    sides SHOULD maintain this relationship in future communication. A 
>    mobile correspondent node SHOULD inform the mobile node of its new 
>    address, when it moves to a new link. The method for doing this is 
>    specified below.

Doesn't this SHOULD NOT disable route optimization?  If I'm a MN at home 
with a binding for another MN I'm communicating with, then move to a new 
link, I'd want to send a binding update instead of reverse-tunneling.

>     A new option called "Correspondent Address Option" is defined for 
>     the BRR message. This option is used to carry the correspondent 
>     address and its format is: 
>      
>        0                   1                   2                   3 
>         0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 
>                                        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
>                                        |   Type = TBD    |  Length = 16| 
>        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
>        |                                                               | 
>        +                                                               + 
>        |                                                               | 
>        +                   Correspondent Address                       + 
>        |                                                               | 
>        +                                                               + 
>        |                                                               | 
>        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 

You should probably state the alignment necessary for this option:

     The Correspondent Address option has an alignment requirement of
     8n+6.

Or maybe it would be easier to just extend the definition of the 
Alternate Care-of Address option already defined in 3775 so it can be 
used for multiple purposes?  Just a thought.

> 4.3. Mobile Node Operations 
> 
>    When a mobile node receives a BRR message containing a correspondent 
>    address option and the mobile node has a Binding Update List entry 
>    for the address carried by the option, then the mobile node should 
>    start the return routability procedure which is sent to the source of 
>    the BRR message. If the mobile node has a Binding Update List entry 
>    for the source of the BRR, then the mobile node should start the 
>    return routability procedure which is sent to the address carried by 
>    the correspondent address option. 

I don't think the stationary MN would need to do RR in all cases, it 
would depend on whether or not it's tokens have expired.  The only 
message that would have to be sent would be the CoTI from the MN that 
just moved (and the subsequent CoT).  Section 11.6.1 of 3775 describes 
this better than I can.

And to address security concerns, you should use all-caps keywords, for 
example:

      Upon receipt of a BRR message containing a correspondent address
      option, the node MUST verify that there is a corresponding binding
      update list entry for the address before starting the Return
      Routability procedure (if necessary), otherwise the packet MUST be
      dropped.


-Brian

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



From mip6-bounces@ietf.org Tue Oct 18 01:30:18 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ERk3G-00053d-Gl; Tue, 18 Oct 2005 01:30:18 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ERk3E-00053V-3r
	for mip6@megatron.ietf.org; Tue, 18 Oct 2005 01:30:16 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA04680
	for <mip6@ietf.org>; Tue, 18 Oct 2005 01:30:07 -0400 (EDT)
From: john.loughney@nokia.com
Received: from mgw-ext02.nokia.com ([131.228.20.94])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ERkEg-0000t5-F4
	for mip6@ietf.org; Tue, 18 Oct 2005 01:42:07 -0400
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143])
	by mgw-ext02.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id
	j9I5U6XU021529; Tue, 18 Oct 2005 08:30:07 +0300
Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by
	esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 18 Oct 2005 08:29:50 +0300
Received: from esebe100.NOE.Nokia.com ([172.21.138.118]) by
	esebh103.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 18 Oct 2005 08:29:50 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.5.7233.31
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] review of draft-ietf-mip6-dsmip-problem-00.txt
Date: Tue, 18 Oct 2005 08:29:52 +0300
Message-ID: <1AA39B75171A7144A73216AED1D7478D01289529@esebe100.NOE.Nokia.com>
Thread-Topic: [Mip6] review of draft-ietf-mip6-dsmip-problem-00.txt
Thread-Index: AcXP8QKh9eGRiNbIRvSZ9lvhHOsABAAQuU+QAIeYT8AAMqd04AAh0efw
To: <G.Tsirtsis@flarion.com>, <jari.arkko@kolumbus.fi>, <mip6@ietf.org>
X-OriginalArrivalTime: 18 Oct 2005 05:29:50.0902 (UTC)
	FILETIME=[F639FD60:01C5D3A4]
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Content-Transfer-Encoding: quoted-printable
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Hi George,
>I actually think these are entirely orthogonal issues, in=20
>which case they can be defined in different documents without=20
>referring to each other.....but maybe we should first make=20
>sure we are talking about the same thing.

Let's say it like this. After re-reading the problem statement,=20
NAT is not an issue, as the current document is written.  However,
I think that any dual stack MIP implementation will need to be
considered with NAT traversal, along with the transition issues
youlise below.

>For example, I am not sure what kind of NAT traversal issue we=20
>talking about here? I do understand, however, the v4 to v6=20
>transition issue which goes like this:
>MIP6 signaling running between an MN and an HA requires that=20
>IPv6 connectivity is available between that MN and that HA. If=20
>there is no native IPv6 connectivity available then, we have=20
>an IPv4 to IPv6 transition issue; i.e., some form of tunneling=20
>or other transition mechanism is required to provide the IPv6=20
>path between the two entities.
>As far as I can tell, this has nothing to do with what kind of=20
>HoAs are handled by MIP6. Do you agree so far?

Agreed - some solutions might optimize things here, but that is
probably not anything needed to be covered in the problem statement.

>I am not sure what is the NAT traversal issue though...can=20
>anyone illuminate?

My reasoning is that for any reasonable MIPv4 implementation,
you need to worry about NAT traversal - that is just a fact
of life.  Anyone running a dual stack MIP node will need to worry
about NAT traversal. =20

Anyhow, as I mentioned before, as written, the draft doesn't cover
quite cover issues where NAT might impact a solution.  If the WG
is fine with this, then I won't worry about it.

John

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



From mip6-bounces@ietf.org Tue Oct 18 01:37:33 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ERkAH-0006vM-1Q; Tue, 18 Oct 2005 01:37:33 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ERkAE-0006tl-SA
	for mip6@megatron.ietf.org; Tue, 18 Oct 2005 01:37:30 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA04960
	for <mip6@ietf.org>; Tue, 18 Oct 2005 01:37:22 -0400 (EDT)
From: john.loughney@nokia.com
Received: from mgw-ext04.nokia.com ([131.228.20.96])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ERkLh-00014i-9G
	for mip6@ietf.org; Tue, 18 Oct 2005 01:49:22 -0400
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211])
	by mgw-ext04.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id
	j9I5Y3Sa018877; Tue, 18 Oct 2005 08:34:09 +0300
Received: from esebh104.NOE.Nokia.com ([172.21.143.34]) by
	esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 18 Oct 2005 08:37:26 +0300
Received: from esebe100.NOE.Nokia.com ([172.21.138.118]) by
	esebh104.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 18 Oct 2005 08:37:25 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.5.7233.31
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 18 Oct 2005 08:37:26 +0300
Message-ID: <1AA39B75171A7144A73216AED1D7478D0128952A@esebe100.NOE.Nokia.com>
Thread-Topic: Some comments on draft-ietf-mip6-dsmip-problem-00.txt
Thread-Index: AcXP8QKh9eGRiNbIRvSZ9lvhHOsABAAQuU+QAIeYT8AAMqd04AAiCC9w
To: <G.Tsirtsis@flarion.com>, <mip6@ietf.org>
X-OriginalArrivalTime: 18 Oct 2005 05:37:25.0762 (UTC)
	FILETIME=[05581E20:01C5D3A6]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Content-Transfer-Encoding: quoted-printable
Cc: 
Subject: [Mip6] Some comments on draft-ietf-mip6-dsmip-problem-00.txt
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

George & Hesham,

A couple of points on the draft:

> 2.4. The impossibility of maintaining connectivity
>
>   A final point to consider is that even if both mobility protocols
are
>   supported by a mobile node seamless connectivity would not in fact
be
>   guarantied since that also depends on the IPv4/IPv6 capabilities of
>   the networks the mobile is visiting i.e.: a dual stack node
>   attempting to connect via a IPv4 only network would not be able to
>   maintain connectivity of its IPv6 applications and vice versa.

I guess the section title should really be 'The Impossibility of
maintaining
seamless connectivity.' Of course the mobile node can still be connected
to the network, but session continuity make break for some applications.

> 3. Conclusion and recommendations

I found this section a bit weak.  The document does discuss the problem
space quite well, but it seems like you jump into the bulleted list
seems
like you've jumped to conclusions.  I don't necessarily disagree with
the
points, but I think some additional text is needed with some analysis
why those bullets would be useful. I think the overall point you are
making is
that you want to make the MIP signaling to be IP version agnostic, so
that
a Mobile Node can HoAs independent of the MIP version used for
signaling.
The other point of having an single CoA (v4 or v6) seems a bit more
fuzzy=20
for me, so I'd like a bit more background on what you are exactly
getting=20
at.  From a certain perspective, it sounds like you want to make a sort
of
Mobile IP relay, but it isn't entirely clear to me.

thanks,
John

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



From mip6-bounces@ietf.org Tue Oct 18 04:23:37 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ERmkz-0000G8-7I; Tue, 18 Oct 2005 04:23:37 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ERmks-0000FO-MX
	for mip6@megatron.ietf.org; Tue, 18 Oct 2005 04:23:35 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA12545
	for <mip6@ietf.org>; Tue, 18 Oct 2005 04:23:22 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ERmwM-0005Dk-6O
	for mip6@ietf.org; Tue, 18 Oct 2005 04:35:23 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id j9I8MuO21383; Tue, 18 Oct 2005 10:22:56 +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
	j9I8MuwN031616; Tue, 18 Oct 2005 10:22:56 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200510180822.j9I8MuwN031616@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: "Kilian Weniger" <Kilian.Weniger@eu.panasonic.com>
In-reply-to: Your message of Mon, 17 Oct 2005 11:05:16 +0200.
	<4D2F935F08D41A4C8866693F4F0D7C4F58DF8D@lan-ex-01.panasonic.de> 
Date: Tue, 18 Oct 2005 10:22:56 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Cc: mip6@ietf.org, James Kempf <Kempf@docomolabs-usa.com>
Subject: [Mip6] Re: draft-dupont-mip6-dhaadharmful-00.txt 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:
   
   Francis, James, thanks for the explanations. Note that I didn't say that
   DHAAD is secure or can be made secure. I was just asking about the
   reasons why DHAAD is considered harmful, because I couldn't find many
   reasons in the draft. Maybe it would be good to include the reasons you
   provided in the last mails in the draft?
   
=> My reason is it can't be made secure easily, James' one is it is based
on ICMP messages which are too often filtered out and Vijay's is the prefix
name is better than the prefix itself for configuration.
So I'll add James' argument in a new version...

Regards

Francis.Dupont@enst-bretagne.fr

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



From mip6-bounces@ietf.org Tue Oct 18 04:29:31 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ERmqg-0002VH-RN; Tue, 18 Oct 2005 04:29:30 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ERmqe-0002Ux-HZ
	for mip6@megatron.ietf.org; Tue, 18 Oct 2005 04:29:28 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA12818
	for <mip6@ietf.org>; Tue, 18 Oct 2005 04:29:21 -0400 (EDT)
Received: from usaga01-in.huawei.com ([12.129.211.51] helo=huawei.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ERn27-0005NB-EY
	for mip6@ietf.org; Tue, 18 Oct 2005 04:41:21 -0400
Received: from huawei.com (usaga01-in [172.18.4.6])
	by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0IOJ00508REB3K@usaga01-in.huawei.com> for
	mip6@ietf.org; Tue, 18 Oct 2005 01:25:23 -0700 (PDT)
Received: from huawei.com ([172.17.1.218])
	by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0IOJ00G77RE9FQ@usaga01-in.huawei.com> for
	mip6@ietf.org; Tue, 18 Oct 2005 01:25:23 -0700 (PDT)
Received: from [172.24.1.3] (Forwarded-For: [172.24.2.12])
	by szxmc02-in.huawei.com (mshttpd); Tue, 18 Oct 2005 16:28:40 +0800
Date: Tue, 18 Oct 2005 16:28:40 +0800
From: mayuzhi 03573 <myz@huawei.com>
Subject: Re:[mip6]draft-yuchi-mip6-mntomn-improve-00
To: Brian.Haley@hp.com
Message-id: <13396a131266.13126613396a@huawei.com>
MIME-version: 1.0
X-Mailer: iPlanet Messenger Express 5.2 HotFix 1.25 (built Mar  3 2004)
Content-type: text/plain; charset=us-ascii
Content-language: zh-CN
Content-transfer-encoding: 7BIT
Content-disposition: inline
X-Accept-Language: zh-CN
Priority: normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 287c806b254c6353fcb09ee0e53bbc5e
Content-Transfer-Encoding: 7BIT
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Hi Brian,
Thanks for you comments. Please find my inline response.

Brian Haley wrote:
>Hi Yuzhi,

>I read your draft about improving MN to MN communications, it seems like 
>a simple thing to implement for certain cases.

>A few comments:

> 3.1. Mobile Correspondent Node 
> 
>    In order to differentiate between the two communicating mobile nodes, 
>    a new concept called "mobile correspondent node" is introduced.

>I don't really like yet another name for a mobile node, you could just 
>refer to it as the stationary mobile node.

According to the Mobile IPv6 basic protocol, A mobile node has dual nature when it communicates with another 
mobile node. Sometimes its role is mobile node, and sometimes its role is correspondent node. 
The dual role result in additional complexity .It is necessary that the role between two communicating mobile nodes
should be differentiated. I think the "stationary mobile node" may not distinctly differentiate the roles.


>    The 
>    initiator of a correspondent registration acts as a mobile node, and 
>    the receiver acts as a mobile correspondent node. The receiver SHOULD 
>    NOT initiate a correspondent registration for the initiator, and both 
>    sides SHOULD maintain this relationship in future communication. A 
>    mobile correspondent node SHOULD inform the mobile node of its new 
>    address, when it moves to a new link. The method for doing this is 
>    specified below.

>Doesn't this SHOULD NOT disable route optimization?  If I'm a MN at home 
>with a binding for another MN I'm communicating with, then move to a new 
>link, I'd want to send a binding update instead of reverse-tunneling.

I mean once their relationship has set up, a mobile correspondent node SHOULD NOT initiate a correspondent registration for the moblie node . But it can initiate a correspondent registration for third moblie node. 


>     A new option called "Correspondent Address Option" is defined for 
>     the BRR message. This option is used to carry the correspondent 
>     address and its format is: 
>      
>        0                   1                   2                   3 
>         0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 
>                                        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
>                                        |   Type = TBD    |  Length = 16| 
>        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
>        |                                                               | 
>        +                                                               + 
>        |                                                               | 
>        +                   Correspondent Address                       + 
>        |                                                               | 
>        +                                                               + 
>        |                                                               | 
>        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 

>You should probably state the alignment necessary for this option:

>     The Correspondent Address option has an alignment requirement of
>     8n+6.

Accepted


>Or maybe it would be easier to just extend the definition of the 
>Alternate Care-of Address option already defined in 3775 so it can be 
>used for multiple purposes?  Just a thought.

If it dosn't bring additional confusion, I think this is a good idea.


> 4.3. Mobile Node Operations 
> 
>    When a mobile node receives a BRR message containing a correspondent 
>    address option and the mobile node has a Binding Update List entry 
>    for the address carried by the option, then the mobile node should 
>    start the return routability procedure which is sent to the source of 
>    the BRR message. If the mobile node has a Binding Update List entry 
>    for the source of the BRR, then the mobile node should start the 
>    return routability procedure which is sent to the address carried by 
>    the correspondent address option. 

>I don't think the stationary MN would need to do RR in all cases, it 
>would depend on whether or not it's tokens have expired.  The only 
>message that would have to be sent would be the CoTI from the MN that 
>just moved (and the subsequent CoT).  Section 11.6.1 of 3775 describes 
>this better than I can.

Yes, I agree. Some limit condition should be added in this section. 
I will consider it.



>And to address security concerns, you should use all-caps keywords, for 
>example:

>      Upon receipt of a BRR message containing a correspondent address
>      option, the node MUST verify that there is a corresponding binding
>      update list entry for the address before starting the Return
>      Routability procedure (if necessary), otherwise the packet MUST be
>      dropped.

Accepted

>-Brian



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



From mip6-bounces@ietf.org Tue Oct 18 04:36:11 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ERmx9-0004FN-JX; Tue, 18 Oct 2005 04:36:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ERmx7-0004FC-Mz
	for mip6@megatron.ietf.org; Tue, 18 Oct 2005 04:36:09 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA13248
	for <mip6@ietf.org>; Tue, 18 Oct 2005 04:36:02 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ERn8b-0005Zf-L5
	for mip6@ietf.org; Tue, 18 Oct 2005 04:48:03 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id j9I8ZlO22451; Tue, 18 Oct 2005 10:35:47 +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
	j9I8ZlpG031677; Tue, 18 Oct 2005 10:35:47 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200510180835.j9I8ZlpG031677@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Vijay Devarapalli <vijayd@iprg.nokia.com>
Subject: Re: [Mip6] Re: draft-dupont-mip6-dhaadharmful-00.txt 
In-reply-to: Your message of Mon, 17 Oct 2005 02:45:01 PDT.
	<4353729D.8000400@iprg.nokia.com> 
Date: Tue, 18 Oct 2005 10:35:47 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   >  - is the insecurity of the current mechanism enough to phase it out?
   >    (I am not alone to think so, at least the bootstrap DT shares this
   >     opinion)
   
   I dont the bootstrap DT ever expressed this opinion.

=> not explicitely but there should be a good reason to propose
the DNS SRV RR mechanism.

   for running DHAAD, the MN needs to be configured with the home
   prefix.

=> or with its name as it was proposed first many years ago by
someone working for Digital (then Compaq and now HP).

   we wanted a solution with minimal configuration on
   the MN. thats why DNS was picked. not just because DHAAD
   is not secure.
   
=> this is a minor reason so I believed the security was the main one.

   I anyway dont have illusions about secure DNS being used.
   in most cases the security for DNS based HA lookup and
   running DHAAD to obtain a list of home agents might be the
   same.
   
=> I agree secure DNS is today only potential but current DHAAD has
not this potential. And I worked on DNSSEC so I believe in its
future even I understand many don't.

   now, back to your discussions. :)
   
=> IMHO the only strong objection against my proposal can come from
the HA assignment: if someone finds a nice general HA assignment
mechanism any DHAAD will lose interest...

Thanks

Francis.Dupont@enst-bretagne.fr

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



From mip6-bounces@ietf.org Tue Oct 18 05:02:20 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ERnMS-0005Ig-JE; Tue, 18 Oct 2005 05:02:20 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ERnMR-0005Ib-H4
	for mip6@megatron.ietf.org; Tue, 18 Oct 2005 05:02:19 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA14901
	for <mip6@ietf.org>; Tue, 18 Oct 2005 05:02:11 -0400 (EDT)
Received: from mail.sfc.wide.ad.jp ([203.178.142.146])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ERnXr-0006KY-Bd
	for mip6@ietf.org; Tue, 18 Oct 2005 05:14:13 -0400
Received: from iseran.local (unknown [IPv6:2001:200:0:68ff:20a:95ff:fed0:2c78])
	by mail.sfc.wide.ad.jp (Postfix) with ESMTP id BE4BF4C55C
	for <mip6@ietf.org>; Tue, 18 Oct 2005 18:01:47 +0900 (JST)
Date: Tue, 18 Oct 2005 18:01:46 +0900
From: Thierry Ernst <ernst@sfc.wide.ad.jp>
To: mip6@ietf.org
Subject: Re: [mip6]draft-yuchi-mip6-mntomn-improve-00
Message-Id: <20051018180146.3c1386e1.ernst@sfc.wide.ad.jp>
In-Reply-To: <13396a131266.13126613396a@huawei.com>
References: <13396a131266.13126613396a@huawei.com>
Organization: Keio University
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-Spam-Score: 0.0 (/)
X-Scan-Signature: 87a3f533bb300b99e2a18357f3c1563d
Content-Transfer-Encoding: 7bit
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org


IMHO, what is needed to express this scenario is a state machine - not
a new entity name.

Thierry.


On Tue, 18 Oct 2005 16:28:40 +0800
mayuzhi 03573 <myz@huawei.com> wrote:

> Hi Brian,
> Thanks for you comments. Please find my inline response.
> 
> Brian Haley wrote:
> >Hi Yuzhi,
> 
> >I read your draft about improving MN to MN communications, it seems
> >like a simple thing to implement for certain cases.
> 
> >A few comments:
> 
> > 3.1. Mobile Correspondent Node 
> > 
> >    In order to differentiate between the two communicating mobile
> >    nodes, a new concept called "mobile correspondent node" is
> >    introduced.
> 
> >I don't really like yet another name for a mobile node, you could
> >just refer to it as the stationary mobile node.
> 
> According to the Mobile IPv6 basic protocol, A mobile node has dual
> nature when it communicates with another mobile node. Sometimes its
> role is mobile node, and sometimes its role is correspondent node. The
> dual role result in additional complexity .It is necessary that the
> role between two communicating mobile nodes should be differentiated.
> I think the "stationary mobile node" may not distinctly differentiate
> the roles.
> 
> 
> >    The 
> >    initiator of a correspondent registration acts as a mobile node,
> >    and the receiver acts as a mobile correspondent node. The
> >    receiver SHOULD NOT initiate a correspondent registration for the
> >    initiator, and both sides SHOULD maintain this relationship in
> >    future communication. A mobile correspondent node SHOULD inform
> >    the mobile node of its new address, when it moves to a new link.
> >    The method for doing this is specified below.
> 
> >Doesn't this SHOULD NOT disable route optimization?  If I'm a MN at
> >home with a binding for another MN I'm communicating with, then move
> >to a new link, I'd want to send a binding update instead of
> >reverse-tunneling.
> 
> I mean once their relationship has set up, a mobile correspondent node
> SHOULD NOT initiate a correspondent registration for the moblie node .
> But it can initiate a correspondent registration for third moblie
> node. 
> 
> 
> >     A new option called "Correspondent Address Option" is defined
> >     for the BRR message. This option is used to carry the
> >     correspondent address and its format is: 
> >      
> >        0                   1                   2                   3
> >        
> >         0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9
> >         0 1 
> >                                        +-+-+-+-+-+-+-+-+-+-+-+-+-+-
> >                                        +-+-+ 
> >                                        |   Type = TBD    |  Length =
> >                                        |   16| 
> >        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
> >        +-+-+ 
> >        |                                                          
    | 
> >        +                                                            
> >          + 
> >        |                                                          
    | 
> >        +                   Correspondent Address                    
> >          + 
> >        |                                                          
    | 
> >        +                                                            
> >          + 
> >        |                                                          
    | 
> >        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
> >        +-+-+ 
> 
> >You should probably state the alignment necessary for this option:
> 
> >     The Correspondent Address option has an alignment requirement of
> >     8n+6.
> 
> Accepted
> 
> 
> >Or maybe it would be easier to just extend the definition of the 
> >Alternate Care-of Address option already defined in 3775 so it can be
> > used for multiple purposes?  Just a thought.
> 
> If it dosn't bring additional confusion, I think this is a good idea.
> 
> 
> > 4.3. Mobile Node Operations 
> > 
> >    When a mobile node receives a BRR message containing a
> >    correspondent address option and the mobile node has a Binding
> >    Update List entry for the address carried by the option, then the
> >    mobile node should start the return routability procedure which
> >    is sent to the source of the BRR message. If the mobile node has
> >    a Binding Update List entry for the source of the BRR, then the
> >    mobile node should start the return routability procedure which
> >    is sent to the address carried by the correspondent address
> >    option. 
> 
> >I don't think the stationary MN would need to do RR in all cases, it 
> >would depend on whether or not it's tokens have expired.  The only 
> >message that would have to be sent would be the CoTI from the MN that
> > just moved (and the subsequent CoT).  Section 11.6.1 of 3775
> > describes 
> >this better than I can.
> 
> Yes, I agree. Some limit condition should be added in this section. 
> I will consider it.
> 
> 
> 
> >And to address security concerns, you should use all-caps keywords,
> >for example:
> 
> >      Upon receipt of a BRR message containing a correspondent
> >      address option, the node MUST verify that there is a
> >      corresponding binding update list entry for the address before
> >      starting the Return Routability procedure (if necessary),
> >      otherwise the packet MUST be dropped.
> 
> Accepted
> 
> >-Brian
> 
> 
> 

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



From mip6-bounces@ietf.org Tue Oct 18 06:03:09 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ERoJJ-0001JU-Gw; Tue, 18 Oct 2005 06:03:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ERoJH-0001JP-8s
	for mip6@megatron.ietf.org; Tue, 18 Oct 2005 06:03:07 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA18582
	for <mip6@ietf.org>; Tue, 18 Oct 2005 06:02:59 -0400 (EDT)
Received: from usaga01-in.huawei.com ([12.129.211.51] helo=huawei.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ERoUm-00088M-Tr
	for mip6@ietf.org; Tue, 18 Oct 2005 06:15:01 -0400
Received: from huawei.com (usaga01-in [172.18.4.6])
	by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0IOJ00L7MVQ5JX@usaga01-in.huawei.com> for
	mip6@ietf.org; Tue, 18 Oct 2005 02:58:53 -0700 (PDT)
Received: from huawei.com ([172.17.1.218])
	by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0IOJ008ZEVQ3XE@usaga01-in.huawei.com> for
	mip6@ietf.org; Tue, 18 Oct 2005 02:58:53 -0700 (PDT)
Received: from [172.24.1.3] (Forwarded-For: [172.19.1.206])
	by szxmc02-in.huawei.com (mshttpd); Tue, 18 Oct 2005 18:02:10 +0800
Date: Tue, 18 Oct 2005 18:02:10 +0800
From: mayuzhi 03573 <myz@huawei.com>
Subject: Re:[mip6]draft-yuchi-mip6-mntomn-improve-00
To: ernst@sfc.wide.ad.jp, mip6@ietf.org
Message-id: <1456091455aa.1455aa145609@huawei.com>
MIME-version: 1.0
X-Mailer: iPlanet Messenger Express 5.2 HotFix 1.25 (built Mar  3 2004)
Content-type: text/plain; charset=us-ascii
Content-language: zh-CN
Content-transfer-encoding: 7BIT
Content-disposition: inline
X-Accept-Language: zh-CN
Priority: normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: dbb8771284c7a36189745aa720dc20ab
Content-Transfer-Encoding: 7BIT
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Maybe.

Yuzhi Ma

>IMHO, what is needed to express this scenario is a state machine - not
>a new entity name.

>Thierry.


On Tue, 18 Oct 2005 16:28:40 +0800
mayuzhi 03573 <myz@huawei.com> wrote:

> Hi Brian,
> Thanks for you comments. Please find my inline response.
> 
> Brian Haley wrote:
> >Hi Yuzhi,
> 
> >I read your draft about improving MN to MN communications, it seems
> >like a simple thing to implement for certain cases.
> 
> >A few comments:
> 
> > 3.1. Mobile Correspondent Node 
> > 
> >    In order to differentiate between the two communicating mobile
> >    nodes, a new concept called "mobile correspondent node" is
> >    introduced.
> 
> >I don't really like yet another name for a mobile node, you could
> >just refer to it as the stationary mobile node.
> 
> According to the Mobile IPv6 basic protocol, A mobile node has dual
> nature when it communicates with another mobile node. Sometimes its
> role is mobile node, and sometimes its role is correspondent node. The
> dual role result in additional complexity .It is necessary that the
> role between two communicating mobile nodes should be differentiated.
> I think the "stationary mobile node" may not distinctly differentiate
> the roles.
> 
> 
> >    The 
> >    initiator of a correspondent registration acts as a mobile node,
> >    and the receiver acts as a mobile correspondent node. The
> >    receiver SHOULD NOT initiate a correspondent registration for the
> >    initiator, and both sides SHOULD maintain this relationship in
> >    future communication. A mobile correspondent node SHOULD inform
> >    the mobile node of its new address, when it moves to a new link.
> >    The method for doing this is specified below.
> 
> >Doesn't this SHOULD NOT disable route optimization?  If I'm a MN at
> >home with a binding for another MN I'm communicating with, then move
> >to a new link, I'd want to send a binding update instead of
> >reverse-tunneling.
> 
> I mean once their relationship has set up, a mobile correspondent node
> SHOULD NOT initiate a correspondent registration for the moblie node .
> But it can initiate a correspondent registration for third moblie
> node. 
> 
> 
> >     A new option called "Correspondent Address Option" is defined
> >     for the BRR message. This option is used to carry the
> >     correspondent address and its format is: 
> >      
> >        0                   1                   2                   3
> >        
> >         0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9
> >         0 1 
> >                                        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
> >                                        |   Type = TBD    |  Length = 16| 
> >        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
> >        |                                                               | 
> >        +                                                               + 
> >        |                                                               | 
> >        +                   Correspondent Address                       + 
> >        |                                                               | 
> >        +                                                               + 
> >        |                                                               | 
> >        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 
> 
> >You should probably state the alignment necessary for this option:
> 
> >     The Correspondent Address option has an alignment requirement of
> >     8n+6.
> 
> Accepted
> 
> 
> >Or maybe it would be easier to just extend the definition of the 
> >Alternate Care-of Address option already defined in 3775 so it can be
> > used for multiple purposes?  Just a thought.
> 
> If it dosn't bring additional confusion, I think this is a good idea.
> 
> 
> > 4.3. Mobile Node Operations 
> > 
> >    When a mobile node receives a BRR message containing a
> >    correspondent address option and the mobile node has a Binding
> >    Update List entry for the address carried by the option, then the
> >    mobile node should start the return routability procedure which
> >    is sent to the source of the BRR message. If the mobile node has
> >    a Binding Update List entry for the source of the BRR, then the
> >    mobile node should start the return routability procedure which
> >    is sent to the address carried by the correspondent address
> >    option. 
> 
> >I don't think the stationary MN would need to do RR in all cases, it 
> >would depend on whether or not it's tokens have expired.  The only 
> >message that would have to be sent would be the CoTI from the MN that
> > just moved (and the subsequent CoT).  Section 11.6.1 of 3775
> > describes 
> >this better than I can.
> 
> Yes, I agree. Some limit condition should be added in this section. 
> I will consider it.
> 
> 
> 
> >And to address security concerns, you should use all-caps keywords,
> >for example:
> 
> >      Upon receipt of a BRR message containing a correspondent
> >      address option, the node MUST verify that there is a
> >      corresponding binding update list entry for the address before
> >      starting the Return Routability procedure (if necessary),
> >      otherwise the packet MUST be dropped.
> 
> Accepted
> 
> >-Brian



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



From mip6-bounces@ietf.org Tue Oct 18 12:36:14 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ERuRi-0006jd-N7; Tue, 18 Oct 2005 12:36:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ERuRh-0006j1-El
	for mip6@megatron.ietf.org; Tue, 18 Oct 2005 12:36:13 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13441
	for <mip6@ietf.org>; Tue, 18 Oct 2005 12:36:05 -0400 (EDT)
Received: from mail.flarion.com ([63.103.94.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ERudG-0002u7-P3
	for mip6@ietf.org; Tue, 18 Oct 2005 12:48:11 -0400
Received: from ftmailserver.flariontech.com ([10.10.1.140]) by
	mail.flarion.com with Microsoft SMTPSVC(5.0.2195.6713);
	Tue, 18 Oct 2005 12:36:02 -0400
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
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] Some comments on draft-ietf-mip6-dsmip-problem-00.txt
Date: Tue, 18 Oct 2005 12:36:02 -0400
Message-ID: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCD3A@ftmailserver.flariontech.com>
Thread-Topic: Some comments on draft-ietf-mip6-dsmip-problem-00.txt
Thread-Index: AcXP8QKh9eGRiNbIRvSZ9lvhHOsABAAQuU+QAIeYT8AAMqd04AAiCC9wABb4JhA=
From: "Soliman, Hesham" <H.Soliman@flarion.com>
To: <john.loughney@nokia.com>, "Tsirtsis, George" <G.Tsirtsis@flarion.com>,
	<mip6@ietf.org>
X-OriginalArrivalTime: 18 Oct 2005 16:36:02.0358 (UTC)
	FILETIME=[07122560:01C5D402]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d2e37451f7f22841e3b6f40c67db0f
Content-Transfer-Encoding: quoted-printable
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Hi John,

 > A couple of points on the draft:
 >=20
 > > 2.4. The impossibility of maintaining connectivity
 > >
 > >   A final point to consider is that even if both mobility protocols
 > are
 > >   supported by a mobile node seamless connectivity would=20
 > not in fact
 > be
 > >   guarantied since that also depends on the IPv4/IPv6=20
 > capabilities of
 > >   the networks the mobile is visiting i.e.: a dual stack node
 > >   attempting to connect via a IPv4 only network would not=20
 > be able to
 > >   maintain connectivity of its IPv6 applications and vice versa.
 >=20
 > I guess the section title should really be 'The Impossibility of
 > maintaining
 > seamless connectivity.' Of course the mobile node can still=20
 > be connected
 > to the network, but session continuity make break for some=20
 > applications.

=3D> That's true. We were talking about IP connectivity, which, in a=20
mobile environment is practically non-existent if you're not=20
reachable on your home address. But I agree that the wording can be=20
made clearer.

 > I found this section a bit weak.  The document does discuss=20
 > the problem
 > space quite well, but it seems like you jump into the bulleted list
 > seems
 > like you've jumped to conclusions.  I don't necessarily disagree with
 > the
 > points, but I think some additional text is needed with some analysis
 > why those bullets would be useful. I think the overall point you are
 > making is
 > that you want to make the MIP signaling to be IP version agnostic,=20

=3D> Yes.=20

   so
 > that
 > a Mobile Node can HoAs independent of the MIP version used for
 > signaling.

=3D> Yes.

 > The other point of having an single CoA (v4 or v6) seems a bit more
 > fuzzy=20
 > for me, so I'd like a bit more background on what you are exactly
 > getting=20
 > at. =20

=3D> Basically, we are trying to highlight two problems that result from
tying MIP to a particular IP version/address family:

A. One home address cannot be used all the time.=20
B. The MN-HA tunnel cannot be established if the MN is located
in a network that doesn't support the IP version associated=20
with MIP. I.e. MIPv6 cannot setup an MN-HA tunnel in an IPv4-only
network and the same goes for MIPv4.=20

The two points above lead to the need for an IP version agnostic
MIP that can handle IPv4/v6 home addresses, as well as, IPv4/v6
CoAs. And the different permutations of both. =20
We'll try to do a better job in the conclusions section to reflect
that.

   From a certain perspective, it sounds like you want to=20
 > make a sort
 > of
 > Mobile IP relay, but it isn't entirely clear to me.

=3D> Not at all. We still want to keep MIP e2e. You'll soon
see the DSMIPv6 solution and hopefully MIP4 will go in a similar
direction.=20


thx,=20
Hesham

 >=20
 > thanks,
 > John
 >=20
 > _______________________________________________
 > Mip6 mailing list
 > Mip6@ietf.org
 > https://www1.ietf.org/mailman/listinfo/mip6
 >=20

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D
This email may contain confidential and privileged material for the sole =
use
 of the intended recipient.  Any review or distribution by others is =
strictly
 prohibited.  If you are not the intended recipient please contact the =
sender
 and delete all copies.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D


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



From mip6-bounces@ietf.org Tue Oct 18 12:56:59 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ERuln-00056K-46; Tue, 18 Oct 2005 12:56:59 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ERuld-00053p-PQ; Tue, 18 Oct 2005 12:56:51 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14252;
	Tue, 18 Oct 2005 12:56:41 -0400 (EDT)
Received: from [132.151.6.50] (helo=newodin.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1ERuxD-0003Mr-7O; Tue, 18 Oct 2005 13:08:47 -0400
Received: from apache by newodin.ietf.org with local (Exim 4.43)
	id 1ERulc-0003Qe-WC; Tue, 18 Oct 2005 12:56:49 -0400
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <E1ERulc-0003Qe-WC@newodin.ietf.org>
Date: Tue, 18 Oct 2005 12:56:48 -0400
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
Cc: mip6 chair <gdommety@cisco.com>, mip6 mailing list <mip6@ietf.org>,
	Internet Architecture Board <iab@iab.org>,
	mip6 chair <basavaraj.patil@nokia.com>,
	RFC Editor <rfc-editor@rfc-editor.org>
Subject: [Mip6] Document Action: 'Authentication Protocol for Mobile IPv6'
 to Informational RFC 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

The IESG has approved the following document:

- 'Authentication Protocol for Mobile IPv6 '
   <draft-ietf-mip6-auth-protocol-07.txt> as an Informational RFC

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

The IESG contact persons are Margaret Wasserman and Mark Townsley.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mip6-auth-protocol-07.txt

Technical Summary
 
   IPsec is specified as the sole means of securing all signaling
   messages between the Mobile Node and Home agent for Mobile IPv6
   (see RFC 3775).  Some deployments, and 3GPP2 in particular, desire
   a different model for securing signalling between the Mobile Node
   and Home Agent, one that more closely fits their existing Mobile
   IPv4 deployments.  This document proposes an alternate method for
   securing the signaling messages, one based on defining a
   MIPv6-specific authentication extension.
 
Working Group Summary
 
  This document certainly generated controversy within the WG. There
  were some who argued that this approach was not appropriate and that
  we should just stick with "use the IPsec-based approach as defined
  in RFC 3775". Others argued that we should listen to an important
  "customer" and that it was appropriate to put this document forward
  on standards track, since there were likely to be many
  implementations.  In the end, most people recognized the need to be
  pragmatic in dealing with the input from 3GPP2, given that
  3GPP2-based mobile IPv4 is the largest current deployment of
  MIPv4. In the end, the WG supported moving this work forward, but as
  an informational document rather than on the Standards Track.
 
Protocol Quality
 
 This document has been reviewed for the IESG by Thomas Narten.

IESG Note

This RFC is not a candidate for any level of Internet Standard.  RFC
3775 and 3776 define Mobile IPv6 and its security mechanism.  This
document presents an alternate security mechanism for Mobile IPv6 used
in 3GPP2 networks.

The security properties of this mechanism have not been reviewed in
the IETF.  Conducting this review proved difficult because the
standards-track security mechanism for Mobile IPv6 is tightly
integrated into the protocol; extensions to Mobile IPv6 and the core
documents make assumptions about the properties of the security model
without explicitly stating what assumptions are being made.  There is
no documented service model.  Thus it is difficult to replace the
security mechanism and see if the current protocol and future
extensions meet appropriate security requirements both under the
original and new security mechanisms.  If a service model for Mobile
IPv6 security is ever formally defined and reviewed, a mechanism
similar to this one could be produced and fully reviewed.

Section 1.1 of this document provides an applicability statement for
this RFC.  The IESG recommends against the usage of this specification
outside of environments that meet the conditions of that applicability
statement.  In addition the IESG recommends those considering
deploying or implementing this specification conduct a sufficient
security review to meet the conditions of the environments in which
this RFC will be used.


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



From mip6-bounces@ietf.org Tue Oct 18 15:36:04 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ERxFj-0001UB-TG; Tue, 18 Oct 2005 15:36:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ERxFg-0001TB-C6
	for mip6@megatron.ietf.org; Tue, 18 Oct 2005 15:36:01 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23791
	for <mip6@ietf.org>; Tue, 18 Oct 2005 15:35:52 -0400 (EDT)
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ERxRE-0008B0-R8
	for mip6@ietf.org; Tue, 18 Oct 2005 15:47:59 -0400
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id j9IJ2x102717;
	Tue, 18 Oct 2005 12:02:59 -0700
X-mProtect: <200510181902> Nokia Silicon Valley Messaging Protection
Received: from es-nira-18-36.europe.nokia.com (10.162.18.36,
	claiming to be "[127.0.0.1]")
	by darkstar.iprg.nokia.com smtpdCKtef3; Tue, 18 Oct 2005 12:02:56 PDT
Message-ID: <4355109D.3090303@iprg.nokia.com>
Date: Tue, 18 Oct 2005 08:11:25 -0700
From: Vijay Devarapalli <vijayd@iprg.nokia.com>
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
Subject: Re: [Mip6] comments about draft-ietf-mip6-ikev2-ipsec-03.txt
References: <200510092157.j99LvIdr084063@givry.rennes.enst-bretagne.fr>
In-Reply-To: <200510092157.j99LvIdr084063@givry.rennes.enst-bretagne.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.7 (/)
X-Scan-Signature: c2e58d9873012c90703822e287241385
Content-Transfer-Encoding: 7bit
Cc: mip6@ietf.org, vijay.devarapalli@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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

hi Francis,

thanks for the second review.


>  In 4.1 page 4:
> 
>    o  ESP encapsulation of the payload packets tunneled between the
>       mobile node and the home agent MAY be supported and used.
> 
> => I believe the document should restrict choices to only three options:
>  - fine granularity: selector on MH types
>  - medium granularity/RFC 3776 compatibility: selector on protocol = MH
>  - coarse granularity: any protocol (here).

ok. but did you want to see some text. or?

> 
>    o  When securing Binding Updates, Binding Acknowledgements, and
>       prefix discovery, both the mobile nodes and the home agents MUST
>       support and SHOULD use the Encapsulating Security Payload (ESP)
>       [6] header in transport mode and MUST use a non-null payload
>       authentication algorithm to provide data origin authentication,
>       connectionless integrity and optional anti-replay protection.
> 
> => s/optional/when possible/ ?

its optional because the binding updates have a sequence
number which provides replay protection.

> 
>  In 5 page 8:
> 
>    This section describes the SPD and SAD entries that can be used to
> 
> => I propose to add something explaining here and in section 6 that
> the care-of address is the primary care-of address. BTW this is required
> from time to time and it makes the code for tracking and updating SPD/SAD
> far easier to write.

I dont think I understand. are you saying the MN should
use its primary CoA and not any CoA? what if the monami6
WG extends MIPv6 registrations to include multiple CoAs?
I would like to support that with just one SA.

>  In 5.1, 5.2 and 5.3 pages 9, 10 and 11: SPD-S entries work both ways
> so there are twice the right number of SPD-S entries. I propose to copy
> the section 6 stuff.

not if we want to enforce the case where only the MN sends
BU and not BAck to the HA and the HA sends BAck only. right?


>  In 5.4 page 11 I can't see a trace of the protocol=MH option...

5.4 is about payload traffic. that means protocol = 'any'.


>    ...  The TSi and
>    TSr payloads in the above examples will contain many other selectors
>    apart from home_address_1.  For the sake of brevity, they are not
>    shown here.
> 
> => this statement is fully not understandable for me. I don't believe
> the idea is to share SAs. Can you explain or remove this?

I am just saying that we are not showing the TSi or TSr
payload completely in the example configurations. only
those values that are relevant for MIPv6.

>  In 6.1.2 page 13 and 6.1.4 page 15:
> 
>                        outer src addr = coa,
>                        outer dst addr = coa,
> 
> => s/coa/[primary_]care-of_address_1/

see my comment above about primary CoA

>  In 6.1.4 page 15:
> 
>        mobile node SPD-S:
>          - IF interface = IPv6 tunnel to home_agent_1 & proto = X
> 
> => this is fully wrong. The SPD-S entry is really similar to the 6.1.2,
> i.e., should be:
> 
>        mobile node SPD-S:
>          - IF source = home_address_1 & destination = any & proto = any
>          etc

how do you distinguish between payload traffic sent to the HA
and to the CN?

>  In 6.2 page 15:
> 
>    The mobile node initiates an IKEv2 protocol exchange if the required
>    security associations are not present.  The default mechanism used
>    for mutual authentication is a shared secret between the mobile node
>    and the home agent.  The home agent uses the identity of the mobile
>    node to identify the corresponding shared secret.  If public key
>    based mechanism is available, it should be the preferred mechanism
>    for mutual authentication.  The home agent and the mobile node should
>    use their private keys to generate the AUTH payload, when a public
>    key based mechanism is used.  The mobile node and the home agent
>    should use CERTREQ and CERT payloads if the identities need to be
>    verified.  If the mobile node is configured with the home agent
>    information including the public key that corresponds to the home
>    agent, then the mobile node MAY exclude the CERTREQ payload in
>    message 3.  Similarly, the home agent MAY exclude the CERTREQ payload
>    in message 2, if it is configured with the mobile node information.
> 
> => this paragraph is pretty bad. Here I try another text:
> 
>    The mobile node initiates an IKEv2 protocol exchange if the required
>    security associations are not present.  A possible mechanism used
>    for mutual authentication is a shared secret between the mobile node
>    and the home agent.  The home agent uses the identity of the mobile
>    node to identify the corresponding shared secret.  When a public key
>    based mechanism is available, it should be the preferred mechanism
>    for mutual authentication: private keys are used to generate the AUTH
>    payload and identities are verified with certificate informations
>    transmitted by CERT payloads or configured. If the mobile node is
>    configured with the home agent information including its certificate,
>    then the mobile node MAY exclude the CERTREQ payload in its IKE_AUTH
>    third message.  Similarly, the home agent MAY exclude the CERTREQ payload
>    in its IS_SA_INIT second message, if it is configured with the mobile node
>    information.

okay. here is the modified text.

    The mobile node initiates an IKEv2 protocol exchange if the required
    security associations are not present.  A possible mechanism used for
    mutual authentication is a shared secret between the mobile node and
    the home agent.  The home agent uses the identity of the mobile node
    to identify the corresponding shared secret.  When a public key based
    mechanism is available, it should be the preferred mechanism for
    mutual authentication: private keys are used to generate the AUTH
    payload and identities are verified with certificate information
    transmitted by CERT payloads.  If the mobile node is configured with
    the home agent information including the public key that corresponds
    to the home agent, then the mobile node MAY exclude the CERTREQ
    payload in its IKE_AUTH third message.  Similarly, the home agent MAY
    exclude the CERTREQ payload in its IKE_SA_INIT second message if it
    is configured with the mobile node information.


>    ...  The mobile node
>    MAY use a range of selectors that includes the mobility message types
>    for Binding Update and Binding Acknowledgement to use the same pair
>    of IPsec security association for both messages.
> 
> => s/MAY/SHOULD/ because I believe it is a very bad idea to have two
> SA pairs.

why is it a bad idea? without that we cant enforce a policy where
we want the HA to send a BAck, but not a BU.

> 
>    After the IKE_AUTH exchange completes, the mobile node initiates
>    CREATE_CHILD_SA exchanges to negotiate additional security
>    associations for protecting Return Routability signaling, Mobile
>    Prefix Discovery messages and optionally payload traffic.
> 
> => I propose:
> 
>    After the IKE_AUTH exchange completes, the mobile node initiates
>    CREATE_CHILD_SA exchanges to negotiate additional security
>    associations for protecting Return Routability signaling or
>    optionally payload traffic, and Mobile Prefix Discovery messages.

whats the difference?

> 
>    When PKI based authentication is used between the mobile node and the
>    Home Agent, the identity presented by the mobile node in the IDi
>    payload must correspond to the identity in the certificate fetched by
>    the Home Agent.
> 
> => s/fetched/got back/ ? My concern is the term "fetch" doesn't match the
> case where the certificate is sent in a CERT payload.

how about "obtained"?

>    address in the IDi field is the home address.  Therefore, this
>    verification step should be skipped.
> 
> => s/should be skipped/must be disabled/ (MUST?)

changed it to "MUST be disabled".

> 
>  In 6.3 page 18:
> 
>    ... on the mobile node
>    when it receives the Binding acknowledgement sent by the home agent.
> 
> => I discussed this with Shinta-san and the endpoint update is performed
> by the mobile node after it sends the BU, i.e., the MN doesn't wait for
> the BA. Cf draft-sugimoto-mip6-pfkey-migrate-01.txt 4.1.2 page 7.

I dont mind making the change, but do you think the mobile node
can start using the new CoA for tunneled packets before it is
sure the BU has been processed by the HA?

> 
>  In 7 page 19: I don't think it is a good idea to rely on [8].
> 

> 
>    The use of EAP for authenticating the mobile node to the home agent
>    is described in Section 7.  This document recommends that if the EAP
> 
> => "recommends" seems a bit strong.
> 
>    method used, supports mutual authentication, then EAP itself be used
> 
> => syntax...
> 
>    for authenticating the home agent to the mobile node also.  This runs
>    contrary to the recommendation in [4].
> 
> => my concern is that I prefer the recommendation in [4]... and I can't
> see why this recommendation should be bad here. Perhaps this is again
> the wrong idea a mobile can't perform public key computations? I strongly
> suggest to put this EAP extension consideration into another document
> (a bootstrapping one for instance).

there are many EAP methods that support mutual authentication.
when such EAP methods are used, I dont think the mobile node
needs to use public key mechanism to authenticate the home
agent.


>  In 12 pages 21 and 22: I believe some authors have in fact only the
> editor role, this should be reflected.
> 
>  In 12.2 page 22:
> 
>    [14]  Sugimoto, S., "PF_KEY Extension as an Interface between Mobile
>          IPv6 and IPsec/IKE", draft-sugimoto-mip6-pfkey-migrate-01 (work
>          in progress), September 2005.
> 
> => me and Masahide Nakamura are co-authors.

I am using xml2rfc. looks like the bibxml files list only
one author. should the bibxml files be fixed?

Vijay





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



From mip6-bounces@ietf.org Wed Oct 19 02:42:06 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ES7eI-0004MS-0A; Wed, 19 Oct 2005 02:42:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ES7eE-0004MN-L5
	for mip6@megatron.ietf.org; Wed, 19 Oct 2005 02:42:02 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA24891
	for <mip6@ietf.org>; Wed, 19 Oct 2005 02:41:53 -0400 (EDT)
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ES7pv-0000dW-3L
	for mip6@ietf.org; Wed, 19 Oct 2005 02:54:07 -0400
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id j9J697A25971
	for <mip6@ietf.org>; Tue, 18 Oct 2005 23:09:07 -0700
X-mProtect: <200510190609> Nokia Silicon Valley Messaging Protection
Received: from essrv103nok14963.ntc.nokia.com (172.21.149.63,
	claiming to be "[127.0.0.1]")
	by darkstar.iprg.nokia.com smtpdO1zMN6; Tue, 18 Oct 2005 23:09:02 PDT
Message-ID: <4355EA9F.2070903@iprg.nokia.com>
Date: Tue, 18 Oct 2005 23:41:35 -0700
From: Vijay Devarapalli <vijayd@iprg.nokia.com>
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: mip6@ietf.org
Content-Type: multipart/mixed; boundary="------------080407020109000506000001"
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 202a3ece0492a8c7e7c8672d5214398f
Subject: [Mip6] [Fwd: I-D
	ACTION:draft-devarapalli-mip6-ikev1-bootstrap-00.txt]
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

This is a multi-part message in MIME format.
--------------080407020109000506000001
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

hi,

here is a short draft on MIP6 bootstrapping using
IKEv1. the draft talks about 2 options, modecfg
and running DHCP over the IPsec tunnel. the draft
also talks about supporting legacy authentication
mechanisms.

comments are welcome.

Vijay

--------------080407020109000506000001
Content-Type: message/rfc822;
	name="I-D ACTION:draft-devarapalli-mip6-ikev1-bootstrap-00.txt"
Content-Disposition: inline;
	filename="I-D ACTION:draft-devarapalli-mip6-ikev1-bootstrap-00.txt"

Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id NAA03968;
	Tue, 18 Oct 2005 13:19:26 -0700 (PDT)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id j9IJkgj11359;
	Tue, 18 Oct 2005 12:46:42 -0700
X-mProtect: <200510181946> Nokia Silicon Valley Messaging Protection
Received: from mailrelay.iprg.nokia.com (205.226.0.201)
	by darkstar.iprg.nokia.com smtpdWkt5fW; Tue, 18 Oct 2005 12:46:38 PDT
X-Scanned: Tue, 18 Oct 2005 13:19:12 -0700 Nokia Message Protector V1.3.35
	2005042208 - RELEASE
Received: (from root@localhost)
	by mailrelay.iprg.nokia.com (8.12.9/8.12.9) id j9IKJCCL019605;
	Tue, 18 Oct 2005 13:19:12 -0700
Received: from megatron.ietf.org (132.151.6.71)
	by mailrelay.iprg.nokia.com 00Boz3l6; Tue, 18 Oct 2005 13:19:06 PDT
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ERxUD-00075e-Fg; Tue, 18 Oct 2005 15:51:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ERxTK-0006rm-09
	for i-d-announce@megatron.ietf.org; Tue, 18 Oct 2005 15:50:06 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24411
	for <i-d-announce@ietf.org>; Tue, 18 Oct 2005 15:49:58 -0400 (EDT)
Received: from [132.151.6.50] (helo=newodin.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ERxer-0000B7-Vl
	for i-d-announce@ietf.org; Tue, 18 Oct 2005 16:02:03 -0400
Received: from mlee by newodin.ietf.org with local (Exim 4.43)
	id 1ERxTG-0001ad-7s
	for i-d-announce@ietf.org; Tue, 18 Oct 2005 15:50:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1ERxTG-0001ad-7s@newodin.ietf.org>
Date: Tue, 18 Oct 2005 15:50:02 -0400
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Subject: I-D ACTION:draft-devarapalli-mip6-ikev1-bootstrap-00.txt 
X-BeenThere: i-d-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: internet-drafts@ietf.org
List-Id: i-d-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/i-d-announce>,
	<mailto:i-d-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:i-d-announce@ietf.org>
List-Help: <mailto:i-d-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/i-d-announce>,
	<mailto:i-d-announce-request@ietf.org?subject=subscribe>
Sender: i-d-announce-bounces@ietf.org
Errors-To: i-d-announce-bounces@ietf.org

--NextPart

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


	Title		: Mobile IPv6 Bootstrapping with IKEv1
	Author(s)	: V. Devarapalli, M. Parthasarathy
	Filename	: draft-devarapalli-mip6-ikev1-bootstrap-00.txt
	Pages		: 8
	Date		: 2005-10-18
	
   The current Mobile IPv6 bootstrapping mechanisms require the use of
   IKEv2 between the mobile node and the home agent.  If the Mobile IPv6
   signaling messages are protected by IKEv1 and IPsec as described in
   RFC 3776, then the bootstrapping mechanism based on IKEv2 cannot be
   used.  This document describes a bootstrapping mechanism for Mobile
   IPv6 when RFC 3776 is used.

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

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


Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-devarapalli-mip6-ikev1-bootstrap-00.txt".

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


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

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-devarapalli-mip6-ikev1-bootstrap-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

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

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

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

ENCODING mime
FILE /internet-drafts/draft-devarapalli-mip6-ikev1-bootstrap-00.txt

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

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


--OtherAccess--

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

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/i-d-announce

--NextPart--



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

--------------080407020109000506000001--





From mip6-bounces@ietf.org Wed Oct 19 05:49:59 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ESAa7-0007FO-PE; Wed, 19 Oct 2005 05:49:59 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ESAa5-0007Dp-Ro
	for mip6@megatron.ietf.org; Wed, 19 Oct 2005 05:49:57 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA03093
	for <mip6@ietf.org>; Wed, 19 Oct 2005 05:49:49 -0400 (EDT)
Received: from szxga01-in.huawei.com ([61.144.161.53] helo=huawei.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ESAln-0005Tw-2d
	for mip6@ietf.org; Wed, 19 Oct 2005 06:02:04 -0400
Received: from huawei.com (szxga01-in [172.24.2.3])
	by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0IOL006FYQ82OJ@szxga01-in.huawei.com> for
	mip6@ietf.org; Wed, 19 Oct 2005 17:55:14 +0800 (CST)
Received: from szxml02-in ([172.24.1.6])
	by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0IOL00D4VQ82VQ@szxga01-in.huawei.com> for
	mip6@ietf.org; Wed, 19 Oct 2005 17:55:14 +0800 (CST)
Received: from x49105 ([10.110.100.124])
	by szxml02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTPA id <0IOL00MSXQAQ4H@szxml02-in.huawei.com> for
	mip6@ietf.org; Wed, 19 Oct 2005 17:56:51 +0800 (CST)
Date: Wed, 19 Oct 2005 17:49:13 +0800
From: xiazhongqi <xiazhongqi@huawei.com>
In-reply-to: <0IOL003ZLHY2X2@szxga02-in.huawei.com>
To: mip6@ietf.org
Message-id: <000001c5d492$5ca7c620$7c646e0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Mailer: Microsoft Outlook, Build 10.0.6626
Content-type: text/plain; charset=gb2312
Content-transfer-encoding: quoted-printable
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
Content-Transfer-Encoding: quoted-printable
Subject: [Mip6] question about draft-ietf-mip6-location-privacy-ps-00.txt
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

=A1=A1=A1=A1To Rajeev Koodli,
=A1=A1=A1=A1   In your draft, you say that only revealing home of =
address to an
on-looker can compromise the location privacy. I can not understand it. =
It
is known that home of address represent that MN is on home link. When MN
roams to an visited network, if it takes reverse tunnel mode, How can CN
know MN's roaming and it's location?


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



From mip6-bounces@ietf.org Wed Oct 19 09:42:16 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ESECu-0001rL-Nz; Wed, 19 Oct 2005 09:42:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ESECs-0001qs-D6; Wed, 19 Oct 2005 09:42:15 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA18200;
	Wed, 19 Oct 2005 09:42:04 -0400 (EDT)
Received: from iramx1.ira.uni-karlsruhe.de ([141.3.10.80]
	ident=[U2FsdGVkX19jAjaBLdYGl2W587YMZklFUskC3fIpjMk=])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1ESEOb-00042v-Dz; Wed, 19 Oct 2005 09:54:22 -0400
Received: from i72ms2.tm.uni-karlsruhe.de ([141.3.70.17]
	helo=smtp.ipv6.tm.uni-karlsruhe.de)
	by iramx1.ira.uni-karlsruhe.de with esmtps 
	id 1ESECY-0007WX-7J; Wed, 19 Oct 2005 15:42:00 +0200
Received: from [141.3.71.115] (i72ibm03.tm.uni-karlsruhe.de [141.3.71.115])
	by smtp.ipv6.tm.uni-karlsruhe.de (Postfix) with ESMTP id A4E89B28A;
	Wed, 19 Oct 2005 15:41:53 +0200 (CEST)
Message-ID: <43564D21.4000408@tm.uka.de>
Date: Wed, 19 Oct 2005 15:41:53 +0200
From: Christian Vogt <chvogt@tm.uka.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; us-US;
	rv:1.7.5) Gecko/20041206 Thunderbird/1.0 Mnenhy/0.7.2.0
X-Accept-Language: de-DE, de, en-us, en
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@kolumbus.fi>
References: <200508020934.j729Yu6F011152@givry.rennes.enst-bretagne.fr>
	<42EFA3B9.9050604@kolumbus.fi>
In-Reply-To: <42EFA3B9.9050604@kolumbus.fi>
X-Enigmail-Version: 0.92.0.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: -5.3 (-----)
X-Spam-Status: No
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87
Content-Transfer-Encoding: 7bit
Cc: mip6@ietf.org, mipshop@ietf.org,
	Francis Dupont <Francis.Dupont@enst-bretagne.fr>,
	Gregory Daley <greg.daley@eng.monash.edu.au>
Subject: [Mip6] Re: [Mipshop] larger options
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

>> PS: a way to fix it: mark size 255 as oversized option: the real 
>> length is in the two next octets.
>> 
> I don't like this very much, because current code would be unable to
> skip it.

All Mobile IPv6 variants should have incorporated mechanisms to
determine that all parties involved do in fact support the variant.

Furthermore, it would be possible to require in the variant's
specification that oversize options must be supported.

These things said, and given that standard Mobile IPv6 does not use
options of size 255, defining option length 255 to indicate oversize
would be possible, too, existing implementations notwithstanding.

Nonetheless, I do like option concatenation.  It seems to be the only
feasible approach for Mobile IPv6 variants which are unable to determine
in advance that both peers provide the required support.

If I was asked to give a statement on this, I'd say:  Write a document
for oversize options, but leave it to the discretion of Mobile IPv6
variants whether they depend on that oversize document or use option
concatenation instead.

- Christian

-- 
Christian Vogt, Institute of Telematics, University of Karlsruhe
www.tm.uka.de/~chvogt/pubkey/



Jari Arkko wrote:
> Francis Dupont wrote:
> 
>> PS: a way to fix it: mark size 255 as oversized option: the real 
>> length is in the two next octets.
>> 
>> 
> I don't like this very much, because current code would be unable to
> skip it.
> 
>> Another way: use the first bit (length > 127) as oversized option: 
>> length field is extended to two octets and the real length is taken
>> from them with the first bit masked...
>> 
>> 
> See above. And Greg Daley wrote:
> 
>> How about the length in the IPv6 header describes the length of the
>>  entire packet including extended options.  Mobility header length
>> value describes the length of the mobility header with the original
>> option sizes and format.  This aggregated length defined in the MH
>> may be smaller than the total packet size (even counting preceding
>> headers).
>> 
>> An identifier would have to be carried in the mobility header
>> indicating that following the exlicit length in the MH are
>> "extended" mobility options.
> 
> 
> This seems a bit complicated, but I got one idea from this (more
> below).
> 
>> For example the next header=[MH|None], length =residual length of
>> the message.
>> 
>> The second MH could only have Extended length options (except pad?)
>> 
>> 
>> I'm not sure if overloading the MH protocol number is too evil.  In
>> that case, there would have to be an allocation of a new protocol
>> number, and an admission of the problem to IANA...
> 
> 
> Overloading is usually not so good.
> 
> Additional ideas:
> 
> o    The truly long options are rare, there's likely just one (cga). 
> Having a rule in the spec that needs this to concatenate the option
> in question if it appears multiple times would be possible. That is,
> you add, say, four options to carry the lengthy data: 
> optionX(...)optionX(...)optionX(...)optionX(...)
> 
> o    Negotiation. The things are likely to need this are probably 
> going to exchange some other packets prior to this, so you might send
> a negotiation option and get another back to confirm that the peer
> supports an extended format. Then you could send your real data by
> setting a flag in the header, and all options would use a new format
> that uses two byte length field for all options.
> 
> Not sure how good these are either. My current gut feeling is that 
> I'd go for the option concatenation.
> 
> --Jari



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



From mip6-bounces@ietf.org Wed Oct 19 15:56:15 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ESK2p-0004N2-Eq; Wed, 19 Oct 2005 15:56:15 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ESK2n-0004MG-MD
	for mip6@megatron.ietf.org; Wed, 19 Oct 2005 15:56:13 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10264
	for <mip6@ietf.org>; Wed, 19 Oct 2005 15:56:00 -0400 (EDT)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ESKEX-000758-Cv
	for mip6@ietf.org; Wed, 19 Oct 2005 16:08:22 -0400
Received: from il06exr03.mot.com (il06exr03.mot.com [129.188.137.133])
	by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id j9JK7oee014713
	for <mip6@ietf.org>; Wed, 19 Oct 2005 13:07:50 -0700 (MST)
Received: from de01exm69.ds.mot.com (de01exm69.am.mot.com [10.176.8.25])
	by il06exr03.mot.com (8.13.1/8.13.0) with ESMTP id j9JK5qZV019805
	for <mip6@ietf.org>; Wed, 19 Oct 2005 15:05:52 -0500 (CDT)
x-mimeole: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 19 Oct 2005 15:55:59 -0400
Message-ID: <0B40B6F9CB990B428819561A2A55613A0B178F@de01exm69.ds.mot.com>
Thread-Topic: Mip6 and AAA?
Thread-Index: AcXU5yBIVnkV3tBDQWOoRiCnIj6zhg==
From: "Narayanan Vidya-CVN065" <vidya@motorola.com>
To: <mip6@ietf.org>
X-Spam-Score: 1.0 (+)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Subject: [Mip6] Mip6 and AAA?
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-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="===============1636483151=="
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1636483151==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C5D4E7.223FEF70"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C5D4E7.223FEF70
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

All,
In order to use the MN-AAA authentication mobility option defined in the
Auth protocol, are there plans to define a Diameter mip6 application or
RADIUS mip6 attributes? Alternatively, in Diameter, I would think new
AVPs may be defined for the NASREQ application.=20
=20
I'm just trying to understand if any work is done/planned in this space.

=20
Thanks,
Vidya

------_=_NextPart_001_01C5D4E7.223FEF70
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></TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2800.1522" name=3DGENERATOR></HEAD>
<BODY>
<DIV><!-- Converted from text/plain format --><FONT face=3DArial=20
size=3D2>All,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>In order to use the MN-AAA =
authentication mobility=20
option defined in the Auth protocol, are there plans to define a =
Diameter mip6=20
application or RADIUS mip6 attributes? Alternatively, in Diameter, I =
would think=20
new AVPs may be defined for the NASREQ application. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>I'm just trying to understand if any =
work is=20
done/planned in this space. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Thanks,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Vidya</FONT></DIV></BODY></HTML>

------_=_NextPart_001_01C5D4E7.223FEF70--


--===============1636483151==
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

--===============1636483151==--




From mip6-bounces@ietf.org Wed Oct 19 16:41:16 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ESKkO-00016C-Bu; Wed, 19 Oct 2005 16:41:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ESKkM-00015o-VB
	for mip6@megatron.ietf.org; Wed, 19 Oct 2005 16:41:15 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA29950
	for <mip6@ietf.org>; Wed, 19 Oct 2005 16:41:06 -0400 (EDT)
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ESKw7-00063n-5v
	for mip6@ietf.org; Wed, 19 Oct 2005 16:53:27 -0400
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id j9JK8Bu01382;
	Wed, 19 Oct 2005 13:08:11 -0700
X-mProtect: <200510192008> Nokia Silicon Valley Messaging Protection
Received: from es-nira-18-179.europe.nokia.com (10.162.18.179,
	claiming to be "[127.0.0.1]")
	by darkstar.iprg.nokia.com smtpdNJkwMf; Wed, 19 Oct 2005 13:07:50 PDT
Message-ID: <4356AF33.7040707@iprg.nokia.com>
Date: Wed, 19 Oct 2005 13:40:19 -0700
From: Vijay Devarapalli <vijayd@iprg.nokia.com>
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Narayanan Vidya-CVN065 <vidya@motorola.com>
Subject: Re: [Mip6] Mip6 and AAA?
References: <0B40B6F9CB990B428819561A2A55613A0B178F@de01exm69.ds.mot.com>
In-Reply-To: <0B40B6F9CB990B428819561A2A55613A0B178F@de01exm69.ds.mot.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Content-Transfer-Encoding: 7bit
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Narayanan Vidya-CVN065 wrote:
> All,
> In order to use the MN-AAA authentication mobility option defined in the 
> Auth protocol, are there plans to define a Diameter mip6 application or 
> RADIUS mip6 attributes? Alternatively, in Diameter, I would think new 
> AVPs may be defined for the NASREQ application.
>  
> I'm just trying to understand if any work is done/planned in this space.

as part of the mip6 bootstrapping work, we have identified
the need to define some AAA messages between the NAS and the
AAAH and between the HA and the AAAH.

draft-ietf-mip6-aaa-ha-goals-00.txt is supposed to capture
the AAA requirments. the plan is to talk about both RADIUS
and Diameter requirements in the same document. this draft
needs to be updated.

Vijay


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



From mip6-bounces@ietf.org Wed Oct 19 17:33:15 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ESLYh-00031x-6i; Wed, 19 Oct 2005 17:33:15 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ESLYf-00031p-3y
	for mip6@megatron.ietf.org; Wed, 19 Oct 2005 17:33:13 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA05462
	for <mip6@ietf.org>; Wed, 19 Oct 2005 17:33:04 -0400 (EDT)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ESLkT-0008WP-EH
	for mip6@ietf.org; Wed, 19 Oct 2005 17:45:25 -0400
Received: from il06exr03.mot.com (il06exr03.mot.com [129.188.137.133])
	by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id j9JLiwTu004137
	for <mip6@ietf.org>; Wed, 19 Oct 2005 14:44:58 -0700 (MST)
Received: from de01exm69.ds.mot.com (de01exm69.am.mot.com [10.176.8.25])
	by il06exr03.mot.com (8.13.1/8.13.0) with ESMTP id j9JLh0Tu025251
	for <mip6@ietf.org>; Wed, 19 Oct 2005 16:43:01 -0500 (CDT)
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] Mip6 and AAA?
Date: Wed, 19 Oct 2005 17:33:10 -0400
Message-ID: <0B40B6F9CB990B428819561A2A55613A0B180C@de01exm69.ds.mot.com>
Thread-Topic: [Mip6] Mip6 and AAA?
Thread-Index: AcXU7WyUrSOWaAH0R1+0SsHBlQO7rAABaPyg
From: "Narayanan Vidya-CVN065" <vidya@motorola.com>
To: "Vijay Devarapalli" <vijayd@iprg.nokia.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Content-Transfer-Encoding: quoted-printable
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

There isn't a scenario in draft-ietf-mip6-aaa-ha-goals that addresses
the case where the auth protocol is used in place of IPSec SA between
the MN and HA - scenarios 3 & 4 in the draft refer to the case where the
HA is contacting the AAA server for mip6 service authorization, not
necessarily authentication of the MN itself. Of course, this can be
easily extended, but I am not sure if the AAA attributes will be the
same - I would expect different AVPs to be defined for this purpose.=20

Maybe it makes sense to have a scenario 5 there that talks about this
case - the MN sends a BU with the MN-AAA Auth option and the HA sends
the BU to the AAAH for authentication and authorization?=20

Also, draft-tschofenig-mip6-aaa-ha-diameter-00 doesn't really have text
in it about BU exchange between the HA and AAA - not sure if that
matters.=20

Vidya=20

> -----Original Message-----
> From: Vijay Devarapalli [mailto:vijayd@iprg.nokia.com]=20
> Sent: Wednesday, October 19, 2005 3:40 PM
> To: Narayanan Vidya-CVN065
> Cc: mip6@ietf.org
> Subject: Re: [Mip6] Mip6 and AAA?
>=20
> Narayanan Vidya-CVN065 wrote:
> > All,
> > In order to use the MN-AAA authentication mobility option=20
> defined in=20
> > the Auth protocol, are there plans to define a Diameter mip6=20
> > application or RADIUS mip6 attributes? Alternatively, in=20
> Diameter, I=20
> > would think new AVPs may be defined for the NASREQ application.
> > =20
> > I'm just trying to understand if any work is done/planned=20
> in this space.
>=20
> as part of the mip6 bootstrapping work, we have identified=20
> the need to define some AAA messages between the NAS and the=20
> AAAH and between the HA and the AAAH.
>=20
> draft-ietf-mip6-aaa-ha-goals-00.txt is supposed to capture=20
> the AAA requirments. the plan is to talk about both RADIUS=20
> and Diameter requirements in the same document. this draft=20
> needs to be updated.
>=20
> Vijay
>=20
>=20

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



From mip6-bounces@ietf.org Wed Oct 19 17:47:59 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ESLmx-0002BE-L8; Wed, 19 Oct 2005 17:47:59 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ESLmw-0002B6-12
	for mip6@megatron.ietf.org; Wed, 19 Oct 2005 17:47:58 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06194
	for <mip6@ietf.org>; Wed, 19 Oct 2005 17:47:49 -0400 (EDT)
Received: from mail.flarion.com ([63.103.94.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ESLyk-0000TR-OI
	for mip6@ietf.org; Wed, 19 Oct 2005 18:00:10 -0400
Received: from ftmailserver.flariontech.com ([10.10.1.140]) by
	mail.flarion.com with Microsoft SMTPSVC(5.0.2195.6713);
	Wed, 19 Oct 2005 17:47:48 -0400
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
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] Mip6 and AAA?
Date: Wed, 19 Oct 2005 17:47:48 -0400
Message-ID: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCD4F@ftmailserver.flariontech.com>
Thread-Topic: [Mip6] Mip6 and AAA?
Thread-Index: AcXU7WyUrSOWaAH0R1+0SsHBlQO7rAABaPygAADhEAA=
From: "Soliman, Hesham" <H.Soliman@flarion.com>
To: "Narayanan Vidya-CVN065" <vidya@motorola.com>,
	"Vijay Devarapalli" <vijayd@iprg.nokia.com>
X-OriginalArrivalTime: 19 Oct 2005 21:47:48.0492 (UTC)
	FILETIME=[BF356CC0:01C5D4F6]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Content-Transfer-Encoding: quoted-printable
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org



 > Also, draft-tschofenig-mip6-aaa-ha-diameter-00 doesn't=20
 > really have text
 > in it about BU exchange between the HA and AAA - not sure if that
 > matters.=20

=3D> Why do you need to exchange a BU between the AAA and HA?=20
I followed your argument up to that point. I thought you were
talking about getting credentials from AAA to authenticate the=20
BU that comes from the MN.=20

Hesham


 >=20
 > Vidya=20
 >=20
 > > -----Original Message-----
 > > From: Vijay Devarapalli [mailto:vijayd@iprg.nokia.com]=20
 > > Sent: Wednesday, October 19, 2005 3:40 PM
 > > To: Narayanan Vidya-CVN065
 > > Cc: mip6@ietf.org
 > > Subject: Re: [Mip6] Mip6 and AAA?
 > >=20
 > > Narayanan Vidya-CVN065 wrote:
 > > > All,
 > > > In order to use the MN-AAA authentication mobility option=20
 > > defined in=20
 > > > the Auth protocol, are there plans to define a Diameter mip6=20
 > > > application or RADIUS mip6 attributes? Alternatively, in=20
 > > Diameter, I=20
 > > > would think new AVPs may be defined for the NASREQ application.
 > > > =20
 > > > I'm just trying to understand if any work is done/planned=20
 > > in this space.
 > >=20
 > > as part of the mip6 bootstrapping work, we have identified=20
 > > the need to define some AAA messages between the NAS and the=20
 > > AAAH and between the HA and the AAAH.
 > >=20
 > > draft-ietf-mip6-aaa-ha-goals-00.txt is supposed to capture=20
 > > the AAA requirments. the plan is to talk about both RADIUS=20
 > > and Diameter requirements in the same document. this draft=20
 > > needs to be updated.
 > >=20
 > > Vijay
 > >=20
 > >=20
 >=20
 > _______________________________________________
 > Mip6 mailing list
 > Mip6@ietf.org
 > https://www1.ietf.org/mailman/listinfo/mip6
 >=20

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D
This email may contain confidential and privileged material for the sole =
use
 of the intended recipient.  Any review or distribution by others is =
strictly
 prohibited.  If you are not the intended recipient please contact the =
sender
 and delete all copies.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D


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



From mip6-bounces@ietf.org Wed Oct 19 17:54:13 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ESLsz-0004Pl-5J; Wed, 19 Oct 2005 17:54:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ESLsw-0004OS-QQ
	for mip6@megatron.ietf.org; Wed, 19 Oct 2005 17:54:10 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06783
	for <mip6@ietf.org>; Wed, 19 Oct 2005 17:54:01 -0400 (EDT)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ESM4l-0000hd-Av
	for mip6@ietf.org; Wed, 19 Oct 2005 18:06: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 j9JM5uMK007320
	for <mip6@ietf.org>; Wed, 19 Oct 2005 15:05:56 -0700 (MST)
Received: from de01exm69.ds.mot.com (de01exm69.am.mot.com [10.176.8.25])
	by il06exr03.mot.com (8.13.1/8.13.0) with ESMTP id j9JM3wxj014394
	for <mip6@ietf.org>; Wed, 19 Oct 2005 17:03:58 -0500 (CDT)
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] Mip6 and AAA?
Date: Wed, 19 Oct 2005 17:54:05 -0400
Message-ID: <0B40B6F9CB990B428819561A2A55613A0B1822@de01exm69.ds.mot.com>
Thread-Topic: [Mip6] Mip6 and AAA?
Thread-Index: AcXU7WyUrSOWaAH0R1+0SsHBlQO7rAABaPygAADhEAAAADvkIA==
From: "Narayanan Vidya-CVN065" <vidya@motorola.com>
To: "Soliman, Hesham" <H.Soliman@flarion.com>,
	"Vijay Devarapalli" <vijayd@iprg.nokia.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Content-Transfer-Encoding: quoted-printable
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

>=20
> =3D> Why do you need to exchange a BU between the AAA and HA?=20
> I followed your argument up to that point. I thought you were=20
> talking about getting credentials from AAA to authenticate=20
> the BU that comes from the MN.=20
>=20

Thats fine too. In the mip4 world, the RRQ gets sent to the AAA (I think
:)). But, yes, what you say would be just fine.=20

Vidya


> Hesham
>=20
>=20
>  >
>  > Vidya
>  >
>  > > -----Original Message-----
>  > > From: Vijay Devarapalli [mailto:vijayd@iprg.nokia.com] =20
> > > Sent: Wednesday, October 19, 2005 3:40 PM  > > To:=20
> Narayanan Vidya-CVN065  > > Cc: mip6@ietf.org  > > Subject:=20
> Re: [Mip6] Mip6 and AAA?
>  > >
>  > > Narayanan Vidya-CVN065 wrote:
>  > > > All,
>  > > > In order to use the MN-AAA authentication mobility=20
> option  > > defined in  > > > the Auth protocol, are there=20
> plans to define a Diameter mip6  > > > application or RADIUS=20
> mip6 attributes? Alternatively, in  > > Diameter, I  > > >=20
> would think new AVPs may be defined for the NASREQ application.
>  > > >
>  > > > I'm just trying to understand if any work is=20
> done/planned  > > in this space.
>  > >
>  > > as part of the mip6 bootstrapping work, we have=20
> identified  > > the need to define some AAA messages between=20
> the NAS and the  > > AAAH and between the HA and the AAAH.
>  > >
>  > > draft-ietf-mip6-aaa-ha-goals-00.txt is supposed to=20
> capture  > > the AAA requirments. the plan is to talk about=20
> both RADIUS  > > and Diameter requirements in the same=20
> document. this draft  > > needs to be updated.
>  > >
>  > > Vijay
>  > >
>  > >
>  >
>  > _______________________________________________
>  > Mip6 mailing list
>  > Mip6@ietf.org
>  > https://www1.ietf.org/mailman/listinfo/mip6
>  >=20
>=20
> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D
> This email may contain confidential and privileged material=20
> for the sole use  of the intended recipient.  Any review or=20
> distribution by others is strictly  prohibited.  If you are=20
> not the intended recipient please contact the sender  and=20
> delete all copies.
> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=20
>=20

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



From mip6-bounces@ietf.org Wed Oct 19 17:56:29 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ESLvB-0005QU-0a; Wed, 19 Oct 2005 17:56:29 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ESLv9-0005MW-2E
	for mip6@megatron.ietf.org; Wed, 19 Oct 2005 17:56:27 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06941
	for <mip6@ietf.org>; Wed, 19 Oct 2005 17:56:18 -0400 (EDT)
Received: from lizzard.sbs.de ([194.138.37.39])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ESM6x-0000mR-FU
	for mip6@ietf.org; Wed, 19 Oct 2005 18:08:39 -0400
Received: from mail1.sbs.de (mail1.sbs.de [192.129.41.35])
	by lizzard.sbs.de (8.12.6/8.12.6) with ESMTP id j9JLuHJW013622;
	Wed, 19 Oct 2005 23:56:17 +0200
Received: from fthw9xoa.ww002.siemens.net (fthw9xoa.ww002.siemens.net
	[157.163.133.201])
	by mail1.sbs.de (8.12.6/8.12.6) with ESMTP id j9JLuGOk012958;
	Wed, 19 Oct 2005 23:56:17 +0200
Received: from MCHP7IEA.ww002.siemens.net ([139.25.131.145]) by
	fthw9xoa.ww002.siemens.net with Microsoft SMTPSVC(6.0.3790.0); 
	Wed, 19 Oct 2005 23:56:16 +0200
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: AW: [Mip6] Mip6 and AAA?
Date: Wed, 19 Oct 2005 23:55:55 +0200
Message-ID: <ECDC9C7BC7809340842C0E7FCF48C39363D372@MCHP7IEA.ww002.siemens.net>
Thread-Topic: [Mip6] Mip6 and AAA?
Thread-Index: AcXU7WyUrSOWaAH0R1+0SsHBlQO7rAABaPygAADxZMA=
From: "Tschofenig, Hannes" <hannes.tschofenig@siemens.com>
To: "Narayanan Vidya-CVN065" <vidya@motorola.com>,
	"Vijay Devarapalli" <vijayd@iprg.nokia.com>
X-OriginalArrivalTime: 19 Oct 2005 21:56:16.0799 (UTC)
	FILETIME=[EE2EEAF0:01C5D4F7]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Content-Transfer-Encoding: quoted-printable
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

hi vidya,=20

the draft-ietf-mip6-aaa-ha-goals is not up-to-date with the most recent =
work in the mip6 bootstrapping solution design team.=20

additionally, i have to mention that the work has mostly focused on =
ikev2. recently vijay has submitted a draft that talks about ikev1.=20
i have suggested to consider also the mipv6-auth protocol some time =
back.=20

i agree that the parameters needed for an ikev2 preshared secret and the =
parameters needed for the mipv6 auth-protocol are different.
still, i think that this does not justify the need for a new =
application. =20

ciao
hannes



> -----Urspr=FCngliche Nachricht-----
> Von: mip6-bounces@ietf.org [mailto:mip6-bounces@ietf.org] Im=20
> Auftrag von Narayanan Vidya-CVN065
> Gesendet: Mittwoch, 19. Oktober 2005 23:33
> An: Vijay Devarapalli
> Cc: mip6@ietf.org
> Betreff: RE: [Mip6] Mip6 and AAA?
>=20
>=20
> There isn't a scenario in draft-ietf-mip6-aaa-ha-goals that addresses
> the case where the auth protocol is used in place of IPSec SA between
> the MN and HA - scenarios 3 & 4 in the draft refer to the=20
> case where the
> HA is contacting the AAA server for mip6 service authorization, not
> necessarily authentication of the MN itself. Of course, this can be
> easily extended, but I am not sure if the AAA attributes will be the
> same - I would expect different AVPs to be defined for this purpose.=20
>=20
> Maybe it makes sense to have a scenario 5 there that talks about this
> case - the MN sends a BU with the MN-AAA Auth option and the HA sends
> the BU to the AAAH for authentication and authorization?=20
>=20
> Also, draft-tschofenig-mip6-aaa-ha-diameter-00 doesn't really=20
> have text
> in it about BU exchange between the HA and AAA - not sure if that
> matters.=20
>=20
> Vidya=20
>=20
> > -----Original Message-----
> > From: Vijay Devarapalli [mailto:vijayd@iprg.nokia.com]=20
> > Sent: Wednesday, October 19, 2005 3:40 PM
> > To: Narayanan Vidya-CVN065
> > Cc: mip6@ietf.org
> > Subject: Re: [Mip6] Mip6 and AAA?
> >=20
> > Narayanan Vidya-CVN065 wrote:
> > > All,
> > > In order to use the MN-AAA authentication mobility option=20
> > defined in=20
> > > the Auth protocol, are there plans to define a Diameter mip6=20
> > > application or RADIUS mip6 attributes? Alternatively, in=20
> > Diameter, I=20
> > > would think new AVPs may be defined for the NASREQ application.
> > > =20
> > > I'm just trying to understand if any work is done/planned=20
> > in this space.
> >=20
> > as part of the mip6 bootstrapping work, we have identified=20
> > the need to define some AAA messages between the NAS and the=20
> > AAAH and between the HA and the AAAH.
> >=20
> > draft-ietf-mip6-aaa-ha-goals-00.txt is supposed to capture=20
> > the AAA requirments. the plan is to talk about both RADIUS=20
> > and Diameter requirements in the same document. this draft=20
> > needs to be updated.
> >=20
> > Vijay
> >=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 Wed Oct 19 17:58:05 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ESLwj-0006Hl-8D; Wed, 19 Oct 2005 17:58:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ESLwh-0006HD-Vr
	for mip6@megatron.ietf.org; Wed, 19 Oct 2005 17:58:04 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA07076
	for <mip6@ietf.org>; Wed, 19 Oct 2005 17:57:55 -0400 (EDT)
Received: from mail.flarion.com ([63.103.94.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ESM8W-0000qL-Oo
	for mip6@ietf.org; Wed, 19 Oct 2005 18:10:17 -0400
Received: from ftmailserver.flariontech.com ([10.10.1.140]) by
	mail.flarion.com with Microsoft SMTPSVC(5.0.2195.6713); 
	Wed, 19 Oct 2005 17:57:54 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] Mip6 and AAA?
Date: Wed, 19 Oct 2005 17:57:54 -0400
Message-ID: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCD50@ftmailserver.flariontech.com>
Thread-Topic: [Mip6] Mip6 and AAA?
Thread-Index: AcXU7WyUrSOWaAH0R1+0SsHBlQO7rAABaPygAADhEAAAADvkIAAAH6EA
From: "Soliman, Hesham" <H.Soliman@flarion.com>
To: "Narayanan Vidya-CVN065" <vidya@motorola.com>,
	"Vijay Devarapalli" <vijayd@iprg.nokia.com>
X-OriginalArrivalTime: 19 Oct 2005 21:57:54.0980 (UTC)
	FILETIME=[28B42640:01C5D4F8]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248
Content-Transfer-Encoding: quoted-printable
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org


 > > =3D> Why do you need to exchange a BU between the AAA and HA?=20
 > > I followed your argument up to that point. I thought you were=20
 > > talking about getting credentials from AAA to authenticate=20
 > > the BU that comes from the MN.=20
 > >=20
 >=20
 > Thats fine too. In the mip4 world, the RRQ gets sent to the=20
 > AAA (I think
 > :)).=20

=3D> Ah, in the MIPv4 world things are ...emm..different :)=20

Hesham


But, yes, what you say would be just fine.=20
 >=20
 > Vidya
 >=20
 >=20
 > > Hesham
 > >=20
 > >=20
 > >  >
 > >  > Vidya
 > >  >
 > >  > > -----Original Message-----
 > >  > > From: Vijay Devarapalli [mailto:vijayd@iprg.nokia.com] =20
 > > > > Sent: Wednesday, October 19, 2005 3:40 PM  > > To:=20
 > > Narayanan Vidya-CVN065  > > Cc: mip6@ietf.org  > > Subject:=20
 > > Re: [Mip6] Mip6 and AAA?
 > >  > >
 > >  > > Narayanan Vidya-CVN065 wrote:
 > >  > > > All,
 > >  > > > In order to use the MN-AAA authentication mobility=20
 > > option  > > defined in  > > > the Auth protocol, are there=20
 > > plans to define a Diameter mip6  > > > application or RADIUS=20
 > > mip6 attributes? Alternatively, in  > > Diameter, I  > > >=20
 > > would think new AVPs may be defined for the NASREQ application.
 > >  > > >
 > >  > > > I'm just trying to understand if any work is=20
 > > done/planned  > > in this space.
 > >  > >
 > >  > > as part of the mip6 bootstrapping work, we have=20
 > > identified  > > the need to define some AAA messages between=20
 > > the NAS and the  > > AAAH and between the HA and the AAAH.
 > >  > >
 > >  > > draft-ietf-mip6-aaa-ha-goals-00.txt is supposed to=20
 > > capture  > > the AAA requirments. the plan is to talk about=20
 > > both RADIUS  > > and Diameter requirements in the same=20
 > > document. this draft  > > needs to be updated.
 > >  > >
 > >  > > Vijay
 > >  > >
 > >  > >
 > >  >
 > >  > _______________________________________________
 > >  > Mip6 mailing list
 > >  > Mip6@ietf.org
 > >  > https://www1.ietf.org/mailman/listinfo/mip6
 > >  >=20
 > >=20
 > > =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D
 > > This email may contain confidential and privileged material=20
 > > for the sole use  of the intended recipient.  Any review or=20
 > > distribution by others is strictly  prohibited.  If you are=20
 > > not the intended recipient please contact the sender  and=20
 > > delete all copies.
 > > =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D
 > >=20
 > >=20
 >=20

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



From mip6-bounces@ietf.org Wed Oct 19 17:58:55 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ESLxX-0006bY-AO; Wed, 19 Oct 2005 17:58:55 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ESLxV-0006Yz-6v
	for mip6@megatron.ietf.org; Wed, 19 Oct 2005 17:58:53 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA07126
	for <mip6@ietf.org>; Wed, 19 Oct 2005 17:58:44 -0400 (EDT)
Received: from motgate3.mot.com ([144.189.100.103])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ESM9E-0000ri-Ac
	for mip6@ietf.org; Wed, 19 Oct 2005 18:11:06 -0400
Received: from az33exr02.mot.com (az33exr02.mot.com [10.64.251.232])
	by motgate3.mot.com (8.12.11/Motgate3) with ESMTP id j9JMEHFV022483
	for <mip6@ietf.org>; Wed, 19 Oct 2005 15:14:17 -0700 (MST)
Received: from de01exm69.ds.mot.com (de01exm69.am.mot.com [10.176.8.25])
	by az33exr02.mot.com (8.13.1/8.13.0) with ESMTP id j9JM5uMm010929
	for <mip6@ietf.org>; Wed, 19 Oct 2005 17:05:57 -0500 (CDT)
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] Mip6 and AAA?
Date: Wed, 19 Oct 2005 17:58:41 -0400
Message-ID: <0B40B6F9CB990B428819561A2A55613A0B1824@de01exm69.ds.mot.com>
Thread-Topic: [Mip6] Mip6 and AAA?
Thread-Index: AcXU7WyUrSOWaAH0R1+0SsHBlQO7rAABaPygAADhEAAAADvkIAAAHEGw
From: "Narayanan Vidya-CVN065" <vidya@motorola.com>
To: "Soliman, Hesham" <H.Soliman@flarion.com>,
	"Vijay Devarapalli" <vijayd@iprg.nokia.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86
Content-Transfer-Encoding: quoted-printable
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org


Actually, on second thoughts, there may be a problem. If the MN uses
MN-AAA authentication option, the auth data in it is created with the
MN-AAA key - it might not be right to provide the HA with that
credential for it to authenticate the BU.=20

OTOH, if the MN uses the MN-HA auth option (where only the MN and AAA
can derive the MN-HA shared key), the AAA can simply send the
credentials to the HA upon request.=20

So, maybe there are two different cases to consider here.=20

Vidya

> -----Original Message-----
> From: Narayanan Vidya-CVN065=20
> Sent: Wednesday, October 19, 2005 4:54 PM
> To: 'Soliman, Hesham'; Vijay Devarapalli
> Cc: mip6@ietf.org
> Subject: RE: [Mip6] Mip6 and AAA?
>=20
> >=20
> > =3D> Why do you need to exchange a BU between the AAA and HA?=20
> > I followed your argument up to that point. I thought you=20
> were talking=20
> > about getting credentials from AAA to authenticate the BU=20
> that comes=20
> > from the MN.
> >=20
>=20
> Thats fine too. In the mip4 world, the RRQ gets sent to the=20
> AAA (I think :)). But, yes, what you say would be just fine.=20
>=20
> Vidya
>=20
>=20
> > Hesham
> >=20
> >=20
> >  >
> >  > Vidya
> >  >
> >  > > -----Original Message-----
> >  > > From: Vijay Devarapalli [mailto:vijayd@iprg.nokia.com] =20
> > > > Sent: Wednesday, October 19, 2005 3:40 PM  > > To:=20
> > Narayanan Vidya-CVN065  > > Cc: mip6@ietf.org  > > Subject:=20
> > Re: [Mip6] Mip6 and AAA?
> >  > >
> >  > > Narayanan Vidya-CVN065 wrote:
> >  > > > All,
> >  > > > In order to use the MN-AAA authentication mobility=20
> > option  > > defined in  > > > the Auth protocol, are there=20
> > plans to define a Diameter mip6  > > > application or RADIUS=20
> > mip6 attributes? Alternatively, in  > > Diameter, I  > > >=20
> > would think new AVPs may be defined for the NASREQ application.
> >  > > >
> >  > > > I'm just trying to understand if any work is=20
> > done/planned  > > in this space.
> >  > >
> >  > > as part of the mip6 bootstrapping work, we have=20
> > identified  > > the need to define some AAA messages between=20
> > the NAS and the  > > AAAH and between the HA and the AAAH.
> >  > >
> >  > > draft-ietf-mip6-aaa-ha-goals-00.txt is supposed to=20
> > capture  > > the AAA requirments. the plan is to talk about=20
> > both RADIUS  > > and Diameter requirements in the same=20
> > document. this draft  > > needs to be updated.
> >  > >
> >  > > Vijay
> >  > >
> >  > >
> >  >
> >  > _______________________________________________
> >  > Mip6 mailing list
> >  > Mip6@ietf.org
> >  > https://www1.ietf.org/mailman/listinfo/mip6
> >  >=20
> >=20
> > =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D
> > This email may contain confidential and privileged material=20
> > for the sole use  of the intended recipient.  Any review or=20
> > distribution by others is strictly  prohibited.  If you are=20
> > not the intended recipient please contact the sender  and=20
> > delete all copies.
> > =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >=20
> >=20
>=20

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



From mip6-bounces@ietf.org Wed Oct 19 17:59:52 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ESLyS-0006pf-FW; Wed, 19 Oct 2005 17:59:52 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ESLyR-0006pY-Bo
	for mip6@megatron.ietf.org; Wed, 19 Oct 2005 17:59:51 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA07219
	for <mip6@ietf.org>; Wed, 19 Oct 2005 17:59:42 -0400 (EDT)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ESMAE-0000uV-2T
	for mip6@ietf.org; Wed, 19 Oct 2005 18:12:04 -0400
Received: from il06exr01.mot.com (il06exr01.mot.com [129.188.137.131])
	by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id j9JMBVjv008015
	for <mip6@ietf.org>; Wed, 19 Oct 2005 15:11:31 -0700 (MST)
Received: from de01exm69.ds.mot.com (de01exm69.am.mot.com [10.176.8.25])
	by il06exr01.mot.com (8.13.1/8.13.0) with ESMTP id j9JM9P7Z002513
	for <mip6@ietf.org>; Wed, 19 Oct 2005 17:09:26 -0500 (CDT)
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] Mip6 and AAA?
Date: Wed, 19 Oct 2005 17:59:43 -0400
Message-ID: <0B40B6F9CB990B428819561A2A55613A0B1826@de01exm69.ds.mot.com>
Thread-Topic: [Mip6] Mip6 and AAA?
Thread-Index: AcXU7WyUrSOWaAH0R1+0SsHBlQO7rAABaPygAADxZMAAAGDOsA==
From: "Narayanan Vidya-CVN065" <vidya@motorola.com>
To: "Tschofenig, Hannes" <hannes.tschofenig@siemens.com>,
	"Vijay Devarapalli" <vijayd@iprg.nokia.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f66b12316365a3fe519e75911daf28a8
Content-Transfer-Encoding: quoted-printable
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

> still, i think that this does not justify the need for a new=20
> application. =20
>

Agreed. Seems to me like the NASREQ application will work fine.=20

Vidya

=20
> ciao
> hannes
>=20
>=20
>=20
> > -----Urspr=FCngliche Nachricht-----
> > Von: mip6-bounces@ietf.org [mailto:mip6-bounces@ietf.org]=20
> Im Auftrag=20
> > von Narayanan Vidya-CVN065
> > Gesendet: Mittwoch, 19. Oktober 2005 23:33
> > An: Vijay Devarapalli
> > Cc: mip6@ietf.org
> > Betreff: RE: [Mip6] Mip6 and AAA?
> >=20
> >=20
> > There isn't a scenario in draft-ietf-mip6-aaa-ha-goals that=20
> addresses=20
> > the case where the auth protocol is used in place of IPSec=20
> SA between=20
> > the MN and HA - scenarios 3 & 4 in the draft refer to the=20
> case where=20
> > the HA is contacting the AAA server for mip6 service authorization,=20
> > not necessarily authentication of the MN itself. Of course,=20
> this can=20
> > be easily extended, but I am not sure if the AAA attributes will be=20
> > the same - I would expect different AVPs to be defined for this=20
> > purpose.
> >=20
> > Maybe it makes sense to have a scenario 5 there that talks=20
> about this=20
> > case - the MN sends a BU with the MN-AAA Auth option and=20
> the HA sends=20
> > the BU to the AAAH for authentication and authorization?
> >=20
> > Also, draft-tschofenig-mip6-aaa-ha-diameter-00 doesn't really have=20
> > text in it about BU exchange between the HA and AAA - not=20
> sure if that=20
> > matters.
> >=20
> > Vidya
> >=20
> > > -----Original Message-----
> > > From: Vijay Devarapalli [mailto:vijayd@iprg.nokia.com]
> > > Sent: Wednesday, October 19, 2005 3:40 PM
> > > To: Narayanan Vidya-CVN065
> > > Cc: mip6@ietf.org
> > > Subject: Re: [Mip6] Mip6 and AAA?
> > >=20
> > > Narayanan Vidya-CVN065 wrote:
> > > > All,
> > > > In order to use the MN-AAA authentication mobility option
> > > defined in
> > > > the Auth protocol, are there plans to define a Diameter mip6=20
> > > > application or RADIUS mip6 attributes? Alternatively, in
> > > Diameter, I
> > > > would think new AVPs may be defined for the NASREQ application.
> > > > =20
> > > > I'm just trying to understand if any work is done/planned
> > > in this space.
> > >=20
> > > as part of the mip6 bootstrapping work, we have=20
> identified the need=20
> > > to define some AAA messages between the NAS and the AAAH=20
> and between=20
> > > the HA and the AAAH.
> > >=20
> > > draft-ietf-mip6-aaa-ha-goals-00.txt is supposed to=20
> capture the AAA=20
> > > requirments. the plan is to talk about both RADIUS and Diameter=20
> > > requirements in the same document. this draft needs to be updated.
> > >=20
> > > Vijay
> > >=20
> > >=20
> >=20
> > _______________________________________________
> > Mip6 mailing list
> > Mip6@ietf.org
> > https://www1.ietf.org/mailman/listinfo/mip6
> >=20
>=20

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



From mip6-bounces@ietf.org Wed Oct 19 18:06:08 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ESM4W-0000bj-1W; Wed, 19 Oct 2005 18:06:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ESM4U-0000be-UD
	for mip6@megatron.ietf.org; Wed, 19 Oct 2005 18:06:06 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07647
	for <mip6@ietf.org>; Wed, 19 Oct 2005 18:05:58 -0400 (EDT)
Received: from gecko.sbs.de ([194.138.37.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ESMGJ-00018s-It
	for mip6@ietf.org; Wed, 19 Oct 2005 18:18:20 -0400
Received: from mail1.sbs.de (mail1.sbs.de [192.129.41.35])
	by gecko.sbs.de (8.12.6/8.12.6) with ESMTP id j9JM5uAO018868;
	Thu, 20 Oct 2005 00:05:56 +0200
Received: from fthw9xpa.ww002.siemens.net (fthw9xpa.ww002.siemens.net
	[157.163.133.222])
	by mail1.sbs.de (8.12.6/8.12.6) with ESMTP id j9JM5u2x018740;
	Thu, 20 Oct 2005 00:05:56 +0200
Received: from MCHP7IEA.ww002.siemens.net ([139.25.131.145]) by
	fthw9xpa.ww002.siemens.net with Microsoft SMTPSVC(6.0.3790.0); 
	Thu, 20 Oct 2005 00:05:56 +0200
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: AW: [Mip6] Mip6 and AAA?
Date: Thu, 20 Oct 2005 00:05:41 +0200
Message-ID: <ECDC9C7BC7809340842C0E7FCF48C39363D374@MCHP7IEA.ww002.siemens.net>
Thread-Topic: [Mip6] Mip6 and AAA?
Thread-Index: AcXU7WyUrSOWaAH0R1+0SsHBlQO7rAABaPygAADhEAAAAIpBQA==
From: "Tschofenig, Hannes" <hannes.tschofenig@siemens.com>
To: "Soliman, Hesham" <H.Soliman@flarion.com>,
	"Narayanan Vidya-CVN065" <vidya@motorola.com>,
	"Vijay Devarapalli" <vijayd@iprg.nokia.com>
X-OriginalArrivalTime: 19 Oct 2005 22:05:56.0022 (UTC)
	FILETIME=[476D5560:01C5D4F9]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be
Content-Transfer-Encoding: quoted-printable
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

hi hesham,=20

>  > Also, draft-tschofenig-mip6-aaa-ha-diameter-00 doesn't=20
>  > really have text
>  > in it about BU exchange between the HA and AAA - not sure if that
>  > matters.=20
the text should read=20
".. have text in it about the AAA exchange between the HA and the AAA
server triggered by the BU ..."

>=20
> =3D> Why do you need to exchange a BU between the AAA and HA?=20
> I followed your argument up to that point. I thought you were
> talking about getting credentials from AAA to authenticate the=20
> BU that comes from the MN.=20
your observation is correct. we are talking about the AAA interaction.=20


ciao
hannes

>=20
> Hesham
>=20
>=20
>  >=20
>  > Vidya=20
>  >=20
>  > > -----Original Message-----
>  > > From: Vijay Devarapalli [mailto:vijayd@iprg.nokia.com]=20
>  > > Sent: Wednesday, October 19, 2005 3:40 PM
>  > > To: Narayanan Vidya-CVN065
>  > > Cc: mip6@ietf.org
>  > > Subject: Re: [Mip6] Mip6 and AAA?
>  > >=20
>  > > Narayanan Vidya-CVN065 wrote:
>  > > > All,
>  > > > In order to use the MN-AAA authentication mobility option=20
>  > > defined in=20
>  > > > the Auth protocol, are there plans to define a Diameter mip6=20
>  > > > application or RADIUS mip6 attributes? Alternatively, in=20
>  > > Diameter, I=20
>  > > > would think new AVPs may be defined for the NASREQ application.
>  > > > =20
>  > > > I'm just trying to understand if any work is done/planned=20
>  > > in this space.
>  > >=20
>  > > as part of the mip6 bootstrapping work, we have identified=20
>  > > the need to define some AAA messages between the NAS and the=20
>  > > AAAH and between the HA and the AAAH.
>  > >=20
>  > > draft-ietf-mip6-aaa-ha-goals-00.txt is supposed to capture=20
>  > > the AAA requirments. the plan is to talk about both RADIUS=20
>  > > and Diameter requirements in the same document. this draft=20
>  > > needs to be updated.
>  > >=20
>  > > Vijay
>  > >=20
>  > >=20
>  >=20
>  > _______________________________________________
>  > Mip6 mailing list
>  > Mip6@ietf.org
>  > https://www1.ietf.org/mailman/listinfo/mip6
>  >=20
>=20
> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D
> This email may contain confidential and privileged material=20
> for the sole use
>  of the intended recipient.  Any review or distribution by=20
> others is strictly
>  prohibited.  If you are not the intended recipient please=20
> contact the sender
>  and delete all copies.
> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=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 Oct 19 18:15:55 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ESMDz-0006mc-Bh; Wed, 19 Oct 2005 18:15:55 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ESMDx-0006kd-Bi
	for mip6@megatron.ietf.org; Wed, 19 Oct 2005 18:15:53 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08200
	for <mip6@ietf.org>; Wed, 19 Oct 2005 18:15:44 -0400 (EDT)
Received: from dns1.tilab.com ([163.162.42.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ESMPl-0001Qx-4a
	for mip6@ietf.org; Wed, 19 Oct 2005 18:28:06 -0400
Received: from iowa2k01a.cselt.it ([163.162.242.201])
	by dns1.cselt.it (PMDF V6.0-025 #38895)
	with ESMTP id <0IOM0077LOI1RD@dns1.cselt.it> for mip6@ietf.org; Thu,
	20 Oct 2005 00:15:37 +0200 (MEST)
Received: from EXC01B.cselt.it ([163.162.4.199]) by iowa2k01a.cselt.it with
	Microsoft SMTPSVC(6.0.3790.211); Thu, 20 Oct 2005 00:15:37 +0200
Date: Thu, 20 Oct 2005 00:15:37 +0200
From: Gerardo Giaretta <Gerardo.Giaretta@TILAB.COM>
Subject: RE: [Mip6] Mip6 and AAA?
To: Narayanan Vidya-CVN065 <vidya@motorola.com>
Message-id: <DA62A6E0CDD1B34A84557FF1AC850C57016E9C76@EXC01B.cselt.it>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.3790.326
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: quoted-printable
Importance: normal
Priority: normal
Thread-Topic: [Mip6] Mip6 and AAA?
Thread-Index: AcXU7WyUrSOWaAH0R1+0SsHBlQO7rAABaPygAAFpjwA=
Content-class: urn:content-classes:message
X-OriginalArrivalTime: 19 Oct 2005 22:15:37.0710 (UTC)
	FILETIME=[A223E0E0:01C5D4FA]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a8a20a483a84f747e56475e290ee868e
Content-Transfer-Encoding: quoted-printable
Cc: mip6@ietf.org, Vijay Devarapalli <vijayd@iprg.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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Hi Vidya,

as mentioned by Vijay, draft-ietf-mip6-aaa-ha-goals needs to be updated. =
We will not be able to get a 01 version before Vancouver deadline but I =
hope to have a review by the DT just after the meeting. The draft was =
written when the bootstrapping solutions were not specified yet and thus =
some scenarios/considerations may need a complete rephrasing. In the =
Design Team, we have identified that some AAA work (e.g. AVPs) is needed =
for bootstrapping solutions we have defined so far. The draft will be =
updated accordingly.

Concerning mip6-auth stuff, as you know, this is actually out of the =
scope of the bootstrapping DT work. There has been some discussion in =
the DT but so far we have decided to focus on IPsec SA setup. I wonder =
if there is interest to work on a bootstrapping solution for mip6-auth =
and related AAA interaction. Notice that mip6-auth is currenlty =
informational.

--Gerardo

> -----Original Message-----
> From: mip6-bounces@ietf.org [mailto:mip6-bounces@ietf.org] On=20
> Behalf Of Narayanan Vidya-CVN065
> Sent: mercoled=EC 19 ottobre 2005 23.33
> To: Vijay Devarapalli
> Cc: mip6@ietf.org
> Subject: RE: [Mip6] Mip6 and AAA?
>=20
> There isn't a scenario in draft-ietf-mip6-aaa-ha-goals that addresses
> the case where the auth protocol is used in place of IPSec SA between
> the MN and HA - scenarios 3 & 4 in the draft refer to the=20
> case where the
> HA is contacting the AAA server for mip6 service authorization, not
> necessarily authentication of the MN itself. Of course, this can be
> easily extended, but I am not sure if the AAA attributes will be the
> same - I would expect different AVPs to be defined for this purpose.=20
>=20
> Maybe it makes sense to have a scenario 5 there that talks about this
> case - the MN sends a BU with the MN-AAA Auth option and the HA sends
> the BU to the AAAH for authentication and authorization?=20
>=20
> Also, draft-tschofenig-mip6-aaa-ha-diameter-00 doesn't really=20
> have text
> in it about BU exchange between the HA and AAA - not sure if that
> matters.=20
>=20
> Vidya=20
>=20
> > -----Original Message-----
> > From: Vijay Devarapalli [mailto:vijayd@iprg.nokia.com]=20
> > Sent: Wednesday, October 19, 2005 3:40 PM
> > To: Narayanan Vidya-CVN065
> > Cc: mip6@ietf.org
> > Subject: Re: [Mip6] Mip6 and AAA?
> >=20
> > Narayanan Vidya-CVN065 wrote:
> > > All,
> > > In order to use the MN-AAA authentication mobility option=20
> > defined in=20
> > > the Auth protocol, are there plans to define a Diameter mip6=20
> > > application or RADIUS mip6 attributes? Alternatively, in=20
> > Diameter, I=20
> > > would think new AVPs may be defined for the NASREQ application.
> > > =20
> > > I'm just trying to understand if any work is done/planned=20
> > in this space.
> >=20
> > as part of the mip6 bootstrapping work, we have identified=20
> > the need to define some AAA messages between the NAS and the=20
> > AAAH and between the HA and the AAAH.
> >=20
> > draft-ietf-mip6-aaa-ha-goals-00.txt is supposed to capture=20
> > the AAA requirments. the plan is to talk about both RADIUS=20
> > and Diameter requirements in the same document. this draft=20
> > needs to be updated.
> >=20
> > Vijay
> >=20
> >=20
>=20
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
>=20


Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia =
S.p.A.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
CONFIDENTIALITY NOTICE
This message and its attachments are addressed solely to the persons
above and may contain confidential information. If you have received
the message in error, be informed that any use of the content hereof
is prohibited. Please return it immediately to the sender and delete
the message. Should you have any questions, please send an e_mail to=20
MailAdmin@tilab.com. Thank you
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

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



From mip6-bounces@ietf.org Wed Oct 19 18:20:59 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ESMIs-0007jd-W9; Wed, 19 Oct 2005 18:20:59 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ESMIr-0007jV-JQ
	for mip6@megatron.ietf.org; Wed, 19 Oct 2005 18:20:57 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08529
	for <mip6@ietf.org>; Wed, 19 Oct 2005 18:20:48 -0400 (EDT)
Received: from dns1.tilab.com ([163.162.42.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ESMUg-0001b0-Aa
	for mip6@ietf.org; Wed, 19 Oct 2005 18:33:10 -0400
Received: from iowa2k01a.cselt.it ([163.162.242.201])
	by dns1.cselt.it (PMDF V6.0-025 #38895)
	with ESMTP id <0IOM0081ROQN6X@dns1.cselt.it> for mip6@ietf.org; Thu,
	20 Oct 2005 00:20:47 +0200 (MEST)
Received: from EXC01B.cselt.it ([163.162.4.199]) by iowa2k01a.cselt.it with
	Microsoft SMTPSVC(6.0.3790.211); Thu, 20 Oct 2005 00:20:47 +0200
Date: Thu, 20 Oct 2005 00:20:47 +0200
From: Gerardo Giaretta <Gerardo.Giaretta@TILAB.COM>
Subject: RE: [Mip6] Mip6 and AAA?
To: Narayanan Vidya-CVN065 <vidya@motorola.com>
Message-id: <DA62A6E0CDD1B34A84557FF1AC850C57016E9C77@EXC01B.cselt.it>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.3790.326
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: quoted-printable
Importance: normal
Priority: normal
Thread-Topic: [Mip6] Mip6 and AAA?
Thread-Index: AcXU7WyUrSOWaAH0R1+0SsHBlQO7rAABaPygAADxZMAAAGDOsAAAtIFA
Content-class: urn:content-classes:message
X-OriginalArrivalTime: 19 Oct 2005 22:20:47.0788 (UTC)
	FILETIME=[5AF606C0:01C5D4FB]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6ffdee8af20de249c24731d8414917d3
Content-Transfer-Encoding: quoted-printable
Cc: mip6@ietf.org, Vijay Devarapalli <vijayd@iprg.nokia.com>, "Tschofenig,
	Hannes" <hannes.tschofenig@siemens.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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

=20
> > still, i think that this does not justify the need for a new=20
> > application. =20
> >
>=20
> Agreed. Seems to me like the NASREQ application will work fine.=20
>

Are you referring to the AAA-HA interface in mip6-auth case or in IKEv2 =
case (e.g. draft-ietf-mip6-bootstrapping-split)?
=20
--Gerardo

> Vidya
>=20
> =20
> > ciao
> > hannes
> >=20
> >=20
> >=20
> > > -----Urspr=FCngliche Nachricht-----
> > > Von: mip6-bounces@ietf.org [mailto:mip6-bounces@ietf.org]=20
> > Im Auftrag=20
> > > von Narayanan Vidya-CVN065
> > > Gesendet: Mittwoch, 19. Oktober 2005 23:33
> > > An: Vijay Devarapalli
> > > Cc: mip6@ietf.org
> > > Betreff: RE: [Mip6] Mip6 and AAA?
> > >=20
> > >=20
> > > There isn't a scenario in draft-ietf-mip6-aaa-ha-goals that=20
> > addresses=20
> > > the case where the auth protocol is used in place of IPSec=20
> > SA between=20
> > > the MN and HA - scenarios 3 & 4 in the draft refer to the=20
> > case where=20
> > > the HA is contacting the AAA server for mip6 service=20
> authorization,=20
> > > not necessarily authentication of the MN itself. Of course,=20
> > this can=20
> > > be easily extended, but I am not sure if the AAA=20
> attributes will be=20
> > > the same - I would expect different AVPs to be defined for this=20
> > > purpose.
> > >=20
> > > Maybe it makes sense to have a scenario 5 there that talks=20
> > about this=20
> > > case - the MN sends a BU with the MN-AAA Auth option and=20
> > the HA sends=20
> > > the BU to the AAAH for authentication and authorization?
> > >=20
> > > Also, draft-tschofenig-mip6-aaa-ha-diameter-00 doesn't=20
> really have=20
> > > text in it about BU exchange between the HA and AAA - not=20
> > sure if that=20
> > > matters.
> > >=20
> > > Vidya
> > >=20
> > > > -----Original Message-----
> > > > From: Vijay Devarapalli [mailto:vijayd@iprg.nokia.com]
> > > > Sent: Wednesday, October 19, 2005 3:40 PM
> > > > To: Narayanan Vidya-CVN065
> > > > Cc: mip6@ietf.org
> > > > Subject: Re: [Mip6] Mip6 and AAA?
> > > >=20
> > > > Narayanan Vidya-CVN065 wrote:
> > > > > All,
> > > > > In order to use the MN-AAA authentication mobility option
> > > > defined in
> > > > > the Auth protocol, are there plans to define a Diameter mip6=20
> > > > > application or RADIUS mip6 attributes? Alternatively, in
> > > > Diameter, I
> > > > > would think new AVPs may be defined for the NASREQ=20
> application.
> > > > > =20
> > > > > I'm just trying to understand if any work is done/planned
> > > > in this space.
> > > >=20
> > > > as part of the mip6 bootstrapping work, we have=20
> > identified the need=20
> > > > to define some AAA messages between the NAS and the AAAH=20
> > and between=20
> > > > the HA and the AAAH.
> > > >=20
> > > > draft-ietf-mip6-aaa-ha-goals-00.txt is supposed to=20
> > capture the AAA=20
> > > > requirments. the plan is to talk about both RADIUS and Diameter=20
> > > > requirements in the same document. this draft needs to=20
> be updated.
> > > >=20
> > > > Vijay
> > > >=20
> > > >=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
>=20


Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia =
S.p.A.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
CONFIDENTIALITY NOTICE
This message and its attachments are addressed solely to the persons
above and may contain confidential information. If you have received
the message in error, be informed that any use of the content hereof
is prohibited. Please return it immediately to the sender and delete
the message. Should you have any questions, please send an e_mail to=20
MailAdmin@tilab.com. Thank you
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

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



From mip6-bounces@ietf.org Wed Oct 19 18:21:12 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ESMJ5-0007mn-UU; Wed, 19 Oct 2005 18:21:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ESMJ3-0007mL-E3
	for mip6@megatron.ietf.org; Wed, 19 Oct 2005 18:21:09 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08545
	for <mip6@ietf.org>; Wed, 19 Oct 2005 18:21:00 -0400 (EDT)
Received: from motgate5.mot.com ([144.189.100.105])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ESMUl-0001b5-G5
	for mip6@ietf.org; Wed, 19 Oct 2005 18:33:21 -0400
Received: from az33exr03.mot.com (az33exr03.mot.com [10.64.251.233])
	by motgate5.mot.com (8.12.11/Motgate5) with ESMTP id j9JMSxGv008093
	for <mip6@ietf.org>; Wed, 19 Oct 2005 15:28:59 -0700 (MST)
Received: from de01exm69.ds.mot.com (de01exm69.am.mot.com [10.176.8.25])
	by az33exr03.mot.com (8.13.1/8.13.0) with ESMTP id j9JMTrZu009712
	for <mip6@ietf.org>; Wed, 19 Oct 2005 17:29:54 -0500 (CDT)
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] Mip6 and AAA?
Date: Wed, 19 Oct 2005 18:20:50 -0400
Message-ID: <0B40B6F9CB990B428819561A2A55613A0B183E@de01exm69.ds.mot.com>
Thread-Topic: [Mip6] Mip6 and AAA?
Thread-Index: AcXU7WyUrSOWaAH0R1+0SsHBlQO7rAABaPygAAFpjwAAAIYKYA==
From: "Narayanan Vidya-CVN065" <vidya@motorola.com>
To: "Gerardo Giaretta" <Gerardo.Giaretta@TILAB.COM>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 36c793b20164cfe75332aa66ddb21196
Content-Transfer-Encoding: quoted-printable
Cc: mip6@ietf.org, Vijay Devarapalli <vijayd@iprg.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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Hi Gerardo,
=20
> Concerning mip6-auth stuff, as you know, this is actually out=20
> of the scope of the bootstrapping DT work. There has been=20
> some discussion in the DT but so far we have decided to focus=20
> on IPsec SA setup. I wonder if there is interest to work on a=20
> bootstrapping solution for mip6-auth and related AAA=20
> interaction. Notice that mip6-auth is currenlty informational.
>=20

This was my point. If this is out of scope of the DT draft, maybe it =
needs to be addressed separately. But, it seems like the definition of =
such AVPs is important for the deployment of the auth protocol.=20

Vidya


> --Gerardo
>=20
> > -----Original Message-----
> > From: mip6-bounces@ietf.org [mailto:mip6-bounces@ietf.org]=20
> On Behalf=20
> > Of Narayanan Vidya-CVN065
> > Sent: mercoled=EC 19 ottobre 2005 23.33
> > To: Vijay Devarapalli
> > Cc: mip6@ietf.org
> > Subject: RE: [Mip6] Mip6 and AAA?
> >=20
> > There isn't a scenario in draft-ietf-mip6-aaa-ha-goals that=20
> addresses=20
> > the case where the auth protocol is used in place of IPSec=20
> SA between=20
> > the MN and HA - scenarios 3 & 4 in the draft refer to the=20
> case where=20
> > the HA is contacting the AAA server for mip6 service authorization,=20
> > not necessarily authentication of the MN itself. Of course,=20
> this can=20
> > be easily extended, but I am not sure if the AAA attributes will be=20
> > the same - I would expect different AVPs to be defined for this=20
> > purpose.
> >=20
> > Maybe it makes sense to have a scenario 5 there that talks=20
> about this=20
> > case - the MN sends a BU with the MN-AAA Auth option and=20
> the HA sends=20
> > the BU to the AAAH for authentication and authorization?
> >=20
> > Also, draft-tschofenig-mip6-aaa-ha-diameter-00 doesn't really have=20
> > text in it about BU exchange between the HA and AAA - not=20
> sure if that=20
> > matters.
> >=20
> > Vidya
> >=20
> > > -----Original Message-----
> > > From: Vijay Devarapalli [mailto:vijayd@iprg.nokia.com]
> > > Sent: Wednesday, October 19, 2005 3:40 PM
> > > To: Narayanan Vidya-CVN065
> > > Cc: mip6@ietf.org
> > > Subject: Re: [Mip6] Mip6 and AAA?
> > >=20
> > > Narayanan Vidya-CVN065 wrote:
> > > > All,
> > > > In order to use the MN-AAA authentication mobility option
> > > defined in
> > > > the Auth protocol, are there plans to define a Diameter mip6=20
> > > > application or RADIUS mip6 attributes? Alternatively, in
> > > Diameter, I
> > > > would think new AVPs may be defined for the NASREQ application.
> > > > =20
> > > > I'm just trying to understand if any work is done/planned
> > > in this space.
> > >=20
> > > as part of the mip6 bootstrapping work, we have=20
> identified the need=20
> > > to define some AAA messages between the NAS and the AAAH=20
> and between=20
> > > the HA and the AAAH.
> > >=20
> > > draft-ietf-mip6-aaa-ha-goals-00.txt is supposed to=20
> capture the AAA=20
> > > requirments. the plan is to talk about both RADIUS and Diameter=20
> > > requirements in the same document. this draft needs to be updated.
> > >=20
> > > Vijay
> > >=20
> > >=20
> >=20
> > _______________________________________________
> > Mip6 mailing list
> > Mip6@ietf.org
> > https://www1.ietf.org/mailman/listinfo/mip6
> >=20
>=20
>=20
> Gruppo Telecom Italia - Direzione e coordinamento di Telecom=20
> Italia S.p.A.
>=20
> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> CONFIDENTIALITY NOTICE
> This message and its attachments are addressed solely to the=20
> persons above and may contain confidential information. If=20
> you have received the message in error, be informed that any=20
> use of the content hereof is prohibited. Please return it=20
> immediately to the sender and delete the message. Should you=20
> have any questions, please send an e_mail to=20
> MailAdmin@tilab.com. Thank you=20
> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=20

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



From mip6-bounces@ietf.org Wed Oct 19 18:24:54 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ESMMf-0000Nj-SG; Wed, 19 Oct 2005 18:24:53 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ESMMe-0000NN-Dr
	for mip6@megatron.ietf.org; Wed, 19 Oct 2005 18:24:52 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08838
	for <mip6@ietf.org>; Wed, 19 Oct 2005 18:24:43 -0400 (EDT)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ESMYT-0001jR-9Y
	for mip6@ietf.org; Wed, 19 Oct 2005 18:37:05 -0400
Received: from il06exr01.mot.com (il06exr01.mot.com [129.188.137.131])
	by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id j9JMac8F011289
	for <mip6@ietf.org>; Wed, 19 Oct 2005 15:36:38 -0700 (MST)
Received: from de01exm69.ds.mot.com (de01exm69.am.mot.com [10.176.8.25])
	by il06exr01.mot.com (8.13.1/8.13.0) with ESMTP id j9JMYVsG018490
	for <mip6@ietf.org>; Wed, 19 Oct 2005 17:34:32 -0500 (CDT)
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] Mip6 and AAA?
Date: Wed, 19 Oct 2005 18:24:49 -0400
Message-ID: <0B40B6F9CB990B428819561A2A55613A0B1841@de01exm69.ds.mot.com>
Thread-Topic: [Mip6] Mip6 and AAA?
Thread-Index: AcXU7WyUrSOWaAH0R1+0SsHBlQO7rAABaPygAADxZMAAAGDOsAAAtIFAAAAYIpA=
From: "Narayanan Vidya-CVN065" <vidya@motorola.com>
To: "Gerardo Giaretta" <Gerardo.Giaretta@TILAB.COM>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b1c41982e167b872076d0018e4e1dc3c
Content-Transfer-Encoding: quoted-printable
Cc: mip6@ietf.org, Vijay Devarapalli <vijayd@iprg.nokia.com>, "Tschofenig,
	Hannes" <hannes.tschofenig@siemens.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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

> Are you referring to the AAA-HA interface in mip6-auth case=20
> or in IKEv2 case (e.g. draft-ietf-mip6-bootstrapping-split)?
> =20

It seems to definitely apply to the mip6-auth case. I have to think more =
about the IKEv2 case - on the surface, it seems like that should work =
there too.=20

Vidya


> --Gerardo
>=20
> > Vidya
> >=20
> > =20
> > > ciao
> > > hannes
> > >=20
> > >=20
> > >=20
> > > > -----Urspr=FCngliche Nachricht-----
> > > > Von: mip6-bounces@ietf.org [mailto:mip6-bounces@ietf.org]
> > > Im Auftrag
> > > > von Narayanan Vidya-CVN065
> > > > Gesendet: Mittwoch, 19. Oktober 2005 23:33
> > > > An: Vijay Devarapalli
> > > > Cc: mip6@ietf.org
> > > > Betreff: RE: [Mip6] Mip6 and AAA?
> > > >=20
> > > >=20
> > > > There isn't a scenario in draft-ietf-mip6-aaa-ha-goals that
> > > addresses
> > > > the case where the auth protocol is used in place of IPSec
> > > SA between
> > > > the MN and HA - scenarios 3 & 4 in the draft refer to the
> > > case where
> > > > the HA is contacting the AAA server for mip6 service
> > authorization,
> > > > not necessarily authentication of the MN itself. Of course,
> > > this can
> > > > be easily extended, but I am not sure if the AAA
> > attributes will be
> > > > the same - I would expect different AVPs to be defined for this=20
> > > > purpose.
> > > >=20
> > > > Maybe it makes sense to have a scenario 5 there that talks
> > > about this
> > > > case - the MN sends a BU with the MN-AAA Auth option and
> > > the HA sends
> > > > the BU to the AAAH for authentication and authorization?
> > > >=20
> > > > Also, draft-tschofenig-mip6-aaa-ha-diameter-00 doesn't
> > really have
> > > > text in it about BU exchange between the HA and AAA - not
> > > sure if that
> > > > matters.
> > > >=20
> > > > Vidya
> > > >=20
> > > > > -----Original Message-----
> > > > > From: Vijay Devarapalli [mailto:vijayd@iprg.nokia.com]
> > > > > Sent: Wednesday, October 19, 2005 3:40 PM
> > > > > To: Narayanan Vidya-CVN065
> > > > > Cc: mip6@ietf.org
> > > > > Subject: Re: [Mip6] Mip6 and AAA?
> > > > >=20
> > > > > Narayanan Vidya-CVN065 wrote:
> > > > > > All,
> > > > > > In order to use the MN-AAA authentication mobility option
> > > > > defined in
> > > > > > the Auth protocol, are there plans to define a=20
> Diameter mip6=20
> > > > > > application or RADIUS mip6 attributes? Alternatively, in
> > > > > Diameter, I
> > > > > > would think new AVPs may be defined for the NASREQ
> > application.
> > > > > > =20
> > > > > > I'm just trying to understand if any work is done/planned
> > > > > in this space.
> > > > >=20
> > > > > as part of the mip6 bootstrapping work, we have
> > > identified the need
> > > > > to define some AAA messages between the NAS and the AAAH
> > > and between
> > > > > the HA and the AAAH.
> > > > >=20
> > > > > draft-ietf-mip6-aaa-ha-goals-00.txt is supposed to
> > > capture the AAA
> > > > > requirments. the plan is to talk about both RADIUS=20
> and Diameter=20
> > > > > requirements in the same document. this draft needs to
> > be updated.
> > > > >=20
> > > > > Vijay
> > > > >=20
> > > > >=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
> >=20
>=20
>=20
> Gruppo Telecom Italia - Direzione e coordinamento di Telecom=20
> Italia S.p.A.
>=20
> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> CONFIDENTIALITY NOTICE
> This message and its attachments are addressed solely to the=20
> persons above and may contain confidential information. If=20
> you have received the message in error, be informed that any=20
> use of the content hereof is prohibited. Please return it=20
> immediately to the sender and delete the message. Should you=20
> have any questions, please send an e_mail to=20
> MailAdmin@tilab.com. Thank you=20
> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=20

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



From mip6-bounces@ietf.org Wed Oct 19 18:28:10 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ESMPq-0002eo-D8; Wed, 19 Oct 2005 18:28:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ESMPo-0002eg-88
	for mip6@megatron.ietf.org; Wed, 19 Oct 2005 18:28:08 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09056
	for <mip6@ietf.org>; Wed, 19 Oct 2005 18:27:59 -0400 (EDT)
Received: from dns1.tilab.com ([163.162.42.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ESMbb-0001rl-V0
	for mip6@ietf.org; Wed, 19 Oct 2005 18:40:21 -0400
Received: from iowa2k01a.cselt.it ([163.162.242.201])
	by dns1.cselt.it (PMDF V6.0-025 #38895)
	with ESMTP id <0IOM0084AP2LFK@dns1.cselt.it> for mip6@ietf.org; Thu,
	20 Oct 2005 00:27:57 +0200 (MEST)
Received: from EXC01B.cselt.it ([163.162.4.199]) by iowa2k01a.cselt.it with
	Microsoft SMTPSVC(6.0.3790.211); Thu, 20 Oct 2005 00:27:57 +0200
Date: Thu, 20 Oct 2005 00:27:56 +0200
From: Gerardo Giaretta <Gerardo.Giaretta@TILAB.COM>
Subject: RE: [Mip6] Mip6 and AAA?
To: Narayanan Vidya-CVN065 <vidya@motorola.com>
Message-id: <DA62A6E0CDD1B34A84557FF1AC850C57016E9C78@EXC01B.cselt.it>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.3790.326
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: quoted-printable
Importance: normal
Priority: normal
Thread-Topic: [Mip6] Mip6 and AAA?
Thread-Index: AcXU7WyUrSOWaAH0R1+0SsHBlQO7rAABaPygAADxZMAAAGDOsAAAtIFAAAAYIpAAAB+lwA==
Content-class: urn:content-classes:message
X-OriginalArrivalTime: 19 Oct 2005 22:27:57.0335 (UTC)
	FILETIME=[5AFDB270:01C5D4FC]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3fbd9b434023f8abfcb1532abaec7a21
Content-Transfer-Encoding: quoted-printable
Cc: mip6@ietf.org, Vijay Devarapalli <vijayd@iprg.nokia.com>, "Tschofenig,
	Hannes" <hannes.tschofenig@siemens.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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

> > Are you referring to the AAA-HA interface in mip6-auth case=20
> > or in IKEv2 case (e.g. draft-ietf-mip6-bootstrapping-split)?
> > =20
>=20
> It seems to definitely apply to the mip6-auth case. I have to=20
> think more about the IKEv2 case - on the surface, it seems=20
> like that should work there too.=20
>

Diameter EAP Application may be also needed in AAA-HA interface for =
IKEv2 case. In fact, EAP may be used in IKE_AUTH exchange. Obviously =
this does not apply to mip6-auth case.

--Gerardo

=20
> Vidya
>=20
>=20
> > --Gerardo
> >=20
> > > Vidya
> > >=20
> > > =20
> > > > ciao
> > > > hannes
> > > >=20
> > > >=20
> > > >=20
> > > > > -----Urspr=FCngliche Nachricht-----
> > > > > Von: mip6-bounces@ietf.org [mailto:mip6-bounces@ietf.org]
> > > > Im Auftrag
> > > > > von Narayanan Vidya-CVN065
> > > > > Gesendet: Mittwoch, 19. Oktober 2005 23:33
> > > > > An: Vijay Devarapalli
> > > > > Cc: mip6@ietf.org
> > > > > Betreff: RE: [Mip6] Mip6 and AAA?
> > > > >=20
> > > > >=20
> > > > > There isn't a scenario in draft-ietf-mip6-aaa-ha-goals that
> > > > addresses
> > > > > the case where the auth protocol is used in place of IPSec
> > > > SA between
> > > > > the MN and HA - scenarios 3 & 4 in the draft refer to the
> > > > case where
> > > > > the HA is contacting the AAA server for mip6 service
> > > authorization,
> > > > > not necessarily authentication of the MN itself. Of course,
> > > > this can
> > > > > be easily extended, but I am not sure if the AAA
> > > attributes will be
> > > > > the same - I would expect different AVPs to be=20
> defined for this=20
> > > > > purpose.
> > > > >=20
> > > > > Maybe it makes sense to have a scenario 5 there that talks
> > > > about this
> > > > > case - the MN sends a BU with the MN-AAA Auth option and
> > > > the HA sends
> > > > > the BU to the AAAH for authentication and authorization?
> > > > >=20
> > > > > Also, draft-tschofenig-mip6-aaa-ha-diameter-00 doesn't
> > > really have
> > > > > text in it about BU exchange between the HA and AAA - not
> > > > sure if that
> > > > > matters.
> > > > >=20
> > > > > Vidya
> > > > >=20
> > > > > > -----Original Message-----
> > > > > > From: Vijay Devarapalli [mailto:vijayd@iprg.nokia.com]
> > > > > > Sent: Wednesday, October 19, 2005 3:40 PM
> > > > > > To: Narayanan Vidya-CVN065
> > > > > > Cc: mip6@ietf.org
> > > > > > Subject: Re: [Mip6] Mip6 and AAA?
> > > > > >=20
> > > > > > Narayanan Vidya-CVN065 wrote:
> > > > > > > All,
> > > > > > > In order to use the MN-AAA authentication mobility option
> > > > > > defined in
> > > > > > > the Auth protocol, are there plans to define a=20
> > Diameter mip6=20
> > > > > > > application or RADIUS mip6 attributes? Alternatively, in
> > > > > > Diameter, I
> > > > > > > would think new AVPs may be defined for the NASREQ
> > > application.
> > > > > > > =20
> > > > > > > I'm just trying to understand if any work is done/planned
> > > > > > in this space.
> > > > > >=20
> > > > > > as part of the mip6 bootstrapping work, we have
> > > > identified the need
> > > > > > to define some AAA messages between the NAS and the AAAH
> > > > and between
> > > > > > the HA and the AAAH.
> > > > > >=20
> > > > > > draft-ietf-mip6-aaa-ha-goals-00.txt is supposed to
> > > > capture the AAA
> > > > > > requirments. the plan is to talk about both RADIUS=20
> > and Diameter=20
> > > > > > requirements in the same document. this draft needs to
> > > be updated.
> > > > > >=20
> > > > > > Vijay
> > > > > >=20
> > > > > >=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
> > >=20
> >=20
> >=20
> > Gruppo Telecom Italia - Direzione e coordinamento di Telecom=20
> > Italia S.p.A.
> >=20
> > =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> > CONFIDENTIALITY NOTICE
> > This message and its attachments are addressed solely to the=20
> > persons above and may contain confidential information. If=20
> > you have received the message in error, be informed that any=20
> > use of the content hereof is prohibited. Please return it=20
> > immediately to the sender and delete the message. Should you=20
> > have any questions, please send an e_mail to=20
> > MailAdmin@tilab.com. Thank you=20
> > =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >=20
>=20


Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia =
S.p.A.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
CONFIDENTIALITY NOTICE
This message and its attachments are addressed solely to the persons
above and may contain confidential information. If you have received
the message in error, be informed that any use of the content hereof
is prohibited. Please return it immediately to the sender and delete
the message. Should you have any questions, please send an e_mail to=20
MailAdmin@tilab.com. Thank you
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

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



From mip6-bounces@ietf.org Wed Oct 19 18:29:22 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ESMR0-0003F2-AU; Wed, 19 Oct 2005 18:29:22 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ESMQy-0003EO-DQ
	for mip6@megatron.ietf.org; Wed, 19 Oct 2005 18:29:20 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09100
	for <mip6@ietf.org>; Wed, 19 Oct 2005 18:29:11 -0400 (EDT)
Received: from dns2.tilab.com ([163.162.42.5])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ESMcl-0001su-3F
	for mip6@ietf.org; Wed, 19 Oct 2005 18:41:33 -0400
Received: from iowa2k01b.cselt.it ([163.162.242.202])
	by dns2.cselt.it (PMDF V6.1 #38895)
	with ESMTP id <0IOM00K6YP4KZ5@dns2.cselt.it> for mip6@ietf.org; Thu,
	20 Oct 2005 00:29:08 +0200 (MEST)
Received: from EXC01B.cselt.it ([163.162.4.199]) by iowa2k01b.cselt.it with
	Microsoft SMTPSVC(6.0.3790.211); Thu, 20 Oct 2005 00:26:49 +0200
Date: Thu, 20 Oct 2005 00:29:06 +0200
From: Gerardo Giaretta <Gerardo.Giaretta@TILAB.COM>
Subject: RE: [Mip6] Mip6 and AAA?
To: Narayanan Vidya-CVN065 <vidya@motorola.com>
Message-id: <DA62A6E0CDD1B34A84557FF1AC850C57016E9C79@EXC01B.cselt.it>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.3790.326
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: quoted-printable
Importance: normal
Priority: normal
Thread-Topic: [Mip6] Mip6 and AAA?
thread-index: AcXU7WyUrSOWaAH0R1+0SsHBlQO7rAABaPygAAFpjwAAAIYKYAAALqhg
Content-Class: urn:content-classes:message
X-OriginalArrivalTime: 19 Oct 2005 22:26:49.0531 (UTC)
	FILETIME=[3293A0B0:01C5D4FC]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 03169bfe4792634a390035a01a6c6d2f
Content-Transfer-Encoding: quoted-printable
Cc: mip6@ietf.org, Vijay Devarapalli <vijayd@iprg.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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Hi Vidya,=20

> Hi Gerardo,
> =20
> > Concerning mip6-auth stuff, as you know, this is actually out=20
> > of the scope of the bootstrapping DT work. There has been=20
> > some discussion in the DT but so far we have decided to focus=20
> > on IPsec SA setup. I wonder if there is interest to work on a=20
> > bootstrapping solution for mip6-auth and related AAA=20
> > interaction. Notice that mip6-auth is currenlty informational.
> >=20
>=20
> This was my point. If this is out of scope of the DT draft,=20
> maybe it needs to be addressed separately.=20

I agree. Current DT is not "chartered" for that.

> But, it seems like=20
> the definition of such AVPs is important for the deployment=20
> of the auth protocol.=20
>=20

Any hint from 3GPP2 plan about this? mip6-auth most important deployment =
scenario is 3GPP2, AFAIK.

As a side note, notice that some requirements listed in AAA-HA goals =
draft may apply to both IPsec SA and mip6-auth scenarios.

--Gerardo

> Vidya
>=20
>=20
> > --Gerardo
> >=20
> > > -----Original Message-----
> > > From: mip6-bounces@ietf.org [mailto:mip6-bounces@ietf.org]=20
> > On Behalf=20
> > > Of Narayanan Vidya-CVN065
> > > Sent: mercoled=EC 19 ottobre 2005 23.33
> > > To: Vijay Devarapalli
> > > Cc: mip6@ietf.org
> > > Subject: RE: [Mip6] Mip6 and AAA?
> > >=20
> > > There isn't a scenario in draft-ietf-mip6-aaa-ha-goals that=20
> > addresses=20
> > > the case where the auth protocol is used in place of IPSec=20
> > SA between=20
> > > the MN and HA - scenarios 3 & 4 in the draft refer to the=20
> > case where=20
> > > the HA is contacting the AAA server for mip6 service=20
> authorization,=20
> > > not necessarily authentication of the MN itself. Of course,=20
> > this can=20
> > > be easily extended, but I am not sure if the AAA=20
> attributes will be=20
> > > the same - I would expect different AVPs to be defined for this=20
> > > purpose.
> > >=20
> > > Maybe it makes sense to have a scenario 5 there that talks=20
> > about this=20
> > > case - the MN sends a BU with the MN-AAA Auth option and=20
> > the HA sends=20
> > > the BU to the AAAH for authentication and authorization?
> > >=20
> > > Also, draft-tschofenig-mip6-aaa-ha-diameter-00 doesn't=20
> really have=20
> > > text in it about BU exchange between the HA and AAA - not=20
> > sure if that=20
> > > matters.
> > >=20
> > > Vidya
> > >=20
> > > > -----Original Message-----
> > > > From: Vijay Devarapalli [mailto:vijayd@iprg.nokia.com]
> > > > Sent: Wednesday, October 19, 2005 3:40 PM
> > > > To: Narayanan Vidya-CVN065
> > > > Cc: mip6@ietf.org
> > > > Subject: Re: [Mip6] Mip6 and AAA?
> > > >=20
> > > > Narayanan Vidya-CVN065 wrote:
> > > > > All,
> > > > > In order to use the MN-AAA authentication mobility option
> > > > defined in
> > > > > the Auth protocol, are there plans to define a Diameter mip6=20
> > > > > application or RADIUS mip6 attributes? Alternatively, in
> > > > Diameter, I
> > > > > would think new AVPs may be defined for the NASREQ=20
> application.
> > > > > =20
> > > > > I'm just trying to understand if any work is done/planned
> > > > in this space.
> > > >=20
> > > > as part of the mip6 bootstrapping work, we have=20
> > identified the need=20
> > > > to define some AAA messages between the NAS and the AAAH=20
> > and between=20
> > > > the HA and the AAAH.
> > > >=20
> > > > draft-ietf-mip6-aaa-ha-goals-00.txt is supposed to=20
> > capture the AAA=20
> > > > requirments. the plan is to talk about both RADIUS and Diameter=20
> > > > requirements in the same document. this draft needs to=20
> be updated.
> > > >=20
> > > > Vijay
> > > >=20
> > > >=20
> > >=20
> > > _______________________________________________
> > > Mip6 mailing list
> > > Mip6@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/mip6
> > >=20
> >=20
> >=20
> > Gruppo Telecom Italia - Direzione e coordinamento di Telecom=20
> > Italia S.p.A.
> >=20
> > =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> > CONFIDENTIALITY NOTICE
> > This message and its attachments are addressed solely to the=20
> > persons above and may contain confidential information. If=20
> > you have received the message in error, be informed that any=20
> > use of the content hereof is prohibited. Please return it=20
> > immediately to the sender and delete the message. Should you=20
> > have any questions, please send an e_mail to=20
> > MailAdmin@tilab.com. Thank you=20
> > =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >=20
>=20


Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia =
S.p.A.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
CONFIDENTIALITY NOTICE
This message and its attachments are addressed solely to the persons
above and may contain confidential information. If you have received
the message in error, be informed that any use of the content hereof
is prohibited. Please return it immediately to the sender and delete
the message. Should you have any questions, please send an e_mail to
MailAdmin@tilab.com. Thank you
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

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



From mip6-bounces@ietf.org Wed Oct 19 18:32:17 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ESMTp-0004gG-3J; Wed, 19 Oct 2005 18:32:17 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ESMTo-0004g7-7V
	for mip6@megatron.ietf.org; Wed, 19 Oct 2005 18:32:16 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09321
	for <mip6@ietf.org>; Wed, 19 Oct 2005 18:32:07 -0400 (EDT)
Received: from motgate7.mot.com ([129.188.136.7])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ESMfX-0001zL-VE
	for mip6@ietf.org; Wed, 19 Oct 2005 18:44:29 -0400
Received: from az33exr04.mot.com ([10.64.251.234])
	by motgate7.mot.com (8.12.11/Motgate7) with ESMTP id j9JMskJP020370
	for <mip6@ietf.org>; Wed, 19 Oct 2005 15:54:46 -0700 (MST)
Received: from de01exm69.ds.mot.com (de01exm69.am.mot.com [10.176.8.25])
	by az33exr04.mot.com (8.13.1/8.13.0) with ESMTP id j9JMcigt013912
	for <mip6@ietf.org>; Wed, 19 Oct 2005 17:38:45 -0500 (CDT)
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] Mip6 and AAA?
Date: Wed, 19 Oct 2005 18:32:06 -0400
Message-ID: <0B40B6F9CB990B428819561A2A55613A0B1845@de01exm69.ds.mot.com>
Thread-Topic: [Mip6] Mip6 and AAA?
Thread-Index: AcXU7WyUrSOWaAH0R1+0SsHBlQO7rAABaPygAAFpjwAAAIYKYAAALqhgAABKYVA=
From: "Narayanan Vidya-CVN065" <vidya@motorola.com>
To: "Gerardo Giaretta" <Gerardo.Giaretta@TILAB.COM>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 225414c974e0d6437992164e91287a51
Content-Transfer-Encoding: quoted-printable
Cc: mip6@ietf.org, Vijay Devarapalli <vijayd@iprg.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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

> >=20
>=20
> Any hint from 3GPP2 plan about this? mip6-auth most important=20
> deployment scenario is 3GPP2, AFAIK.
>

Yes, this is my understanding too. If some 3gpp2 folks can shed some =
light on this, it would be good.=20

=20
> As a side note, notice that some requirements listed in=20
> AAA-HA goals draft may apply to both IPsec SA and mip6-auth scenarios.
>=20

Actually, this is why I thought the extra scenarios can simply be added =
to that draft. A separate effort here will end up re-visiting some of =
the requirements already present for the IKEv2 case.=20

Vidya


> --Gerardo
>=20
> > Vidya
> >=20
> >=20
> > > --Gerardo
> > >=20
> > > > -----Original Message-----
> > > > From: mip6-bounces@ietf.org [mailto:mip6-bounces@ietf.org]
> > > On Behalf
> > > > Of Narayanan Vidya-CVN065
> > > > Sent: mercoled=EC 19 ottobre 2005 23.33
> > > > To: Vijay Devarapalli
> > > > Cc: mip6@ietf.org
> > > > Subject: RE: [Mip6] Mip6 and AAA?
> > > >=20
> > > > There isn't a scenario in draft-ietf-mip6-aaa-ha-goals that
> > > addresses
> > > > the case where the auth protocol is used in place of IPSec
> > > SA between
> > > > the MN and HA - scenarios 3 & 4 in the draft refer to the
> > > case where
> > > > the HA is contacting the AAA server for mip6 service
> > authorization,
> > > > not necessarily authentication of the MN itself. Of course,
> > > this can
> > > > be easily extended, but I am not sure if the AAA
> > attributes will be
> > > > the same - I would expect different AVPs to be defined for this=20
> > > > purpose.
> > > >=20
> > > > Maybe it makes sense to have a scenario 5 there that talks
> > > about this
> > > > case - the MN sends a BU with the MN-AAA Auth option and
> > > the HA sends
> > > > the BU to the AAAH for authentication and authorization?
> > > >=20
> > > > Also, draft-tschofenig-mip6-aaa-ha-diameter-00 doesn't
> > really have
> > > > text in it about BU exchange between the HA and AAA - not
> > > sure if that
> > > > matters.
> > > >=20
> > > > Vidya
> > > >=20
> > > > > -----Original Message-----
> > > > > From: Vijay Devarapalli [mailto:vijayd@iprg.nokia.com]
> > > > > Sent: Wednesday, October 19, 2005 3:40 PM
> > > > > To: Narayanan Vidya-CVN065
> > > > > Cc: mip6@ietf.org
> > > > > Subject: Re: [Mip6] Mip6 and AAA?
> > > > >=20
> > > > > Narayanan Vidya-CVN065 wrote:
> > > > > > All,
> > > > > > In order to use the MN-AAA authentication mobility option
> > > > > defined in
> > > > > > the Auth protocol, are there plans to define a=20
> Diameter mip6=20
> > > > > > application or RADIUS mip6 attributes? Alternatively, in
> > > > > Diameter, I
> > > > > > would think new AVPs may be defined for the NASREQ
> > application.
> > > > > > =20
> > > > > > I'm just trying to understand if any work is done/planned
> > > > > in this space.
> > > > >=20
> > > > > as part of the mip6 bootstrapping work, we have
> > > identified the need
> > > > > to define some AAA messages between the NAS and the AAAH
> > > and between
> > > > > the HA and the AAAH.
> > > > >=20
> > > > > draft-ietf-mip6-aaa-ha-goals-00.txt is supposed to
> > > capture the AAA
> > > > > requirments. the plan is to talk about both RADIUS=20
> and Diameter=20
> > > > > requirements in the same document. this draft needs to
> > be updated.
> > > > >=20
> > > > > Vijay
> > > > >=20
> > > > >=20
> > > >=20
> > > > _______________________________________________
> > > > Mip6 mailing list
> > > > Mip6@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/mip6
> > > >=20
> > >=20
> > >=20
> > > Gruppo Telecom Italia - Direzione e coordinamento di=20
> Telecom Italia=20
> > > S.p.A.
> > >=20
> > >=20
> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> > > CONFIDENTIALITY NOTICE
> > > This message and its attachments are addressed solely to=20
> the persons=20
> > > above and may contain confidential information. If you=20
> have received=20
> > > the message in error, be informed that any use of the=20
> content hereof=20
> > > is prohibited. Please return it immediately to the sender=20
> and delete=20
> > > the message. Should you have any questions, please send=20
> an e_mail to=20
> > > MailAdmin@tilab.com. Thank you=20
> > >=20
> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> > >=20
> >=20
>=20
>=20
> Gruppo Telecom Italia - Direzione e coordinamento di Telecom=20
> Italia S.p.A.
>=20
> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> CONFIDENTIALITY NOTICE
> This message and its attachments are addressed solely to the=20
> persons above and may contain confidential information. If=20
> you have received the message in error, be informed that any=20
> use of the content hereof is prohibited. Please return it=20
> immediately to the sender and delete the message. Should you=20
> have any questions, please send an e_mail to=20
> MailAdmin@tilab.com. Thank you=20
> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=20

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



From mip6-bounces@ietf.org Thu Oct 20 02:00:59 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ESTU3-00040N-GJ; Thu, 20 Oct 2005 02:00:59 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ESTU2-00040D-1O
	for mip6@megatron.ietf.org; Thu, 20 Oct 2005 02:00:58 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA13670
	for <mip6@ietf.org>; Thu, 20 Oct 2005 02:00:48 -0400 (EDT)
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ESTfp-0001e3-8U
	for mip6@ietf.org; Thu, 20 Oct 2005 02:13:11 -0400
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id j9K5Rjm14514;
	Wed, 19 Oct 2005 22:27:45 -0700
X-mProtect: <200510200527> Nokia Silicon Valley Messaging Protection
Received: from es-nira-17-83.europe.nokia.com (10.162.17.83,
	claiming to be "[127.0.0.1]")
	by darkstar.iprg.nokia.com smtpdbarutt; Wed, 19 Oct 2005 22:27:44 PDT
Message-ID: <43573270.7080704@iprg.nokia.com>
Date: Wed, 19 Oct 2005 23:00:16 -0700
From: Vijay Devarapalli <vijayd@iprg.nokia.com>
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Gerardo Giaretta <Gerardo.Giaretta@TILAB.COM>
Subject: Re: [Mip6] Mip6 and AAA?
References: <DA62A6E0CDD1B34A84557FF1AC850C57016E9C79@EXC01B.cselt.it>
In-Reply-To: <DA62A6E0CDD1B34A84557FF1AC850C57016E9C79@EXC01B.cselt.it>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de
Content-Transfer-Encoding: 7bit
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Gerardo Giaretta wrote:

> 
> Any hint from 3GPP2 plan about this? mip6-auth most important deployment scenario is 3GPP2, AFAIK.

PDSN-AAAH and HA-AAAH interfaces for MIPv6 have been specified
in the 3GPP2 specs itself. no IETF specs needed.

Vijay


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



From mip6-bounces@ietf.org Thu Oct 20 18:50:16 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ESjEm-0006H2-FD; Thu, 20 Oct 2005 18:50:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ESjEZ-00069L-6n; Thu, 20 Oct 2005 18:50:03 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA20158;
	Thu, 20 Oct 2005 18:49:53 -0400 (EDT)
Received: from [132.151.6.50] (helo=newodin.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1ESjQa-0004eR-5B; Thu, 20 Oct 2005 19:02:28 -0400
Received: from mlee by newodin.ietf.org with local (Exim 4.43)
	id 1ESjEX-00065v-LZ; Thu, 20 Oct 2005 18:50:01 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1ESjEX-00065v-LZ@newodin.ietf.org>
Date: Thu, 20 Oct 2005 18:50:01 -0400
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Cc: mip6@ietf.org
Subject: [Mip6] I-D ACTION:draft-ietf-mip6-nemo-v4traversal-00.txt 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

--NextPart

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

	Title		: Dual Stack Mobile IPv6 (DSMIPv6) for Hosts and Routers
	Author(s)	: H. Soliman, et al.
	Filename	: draft-ietf-mip6-nemo-v4traversal-00.txt
	Pages		: 21
	Date		: 2005-10-20
	
   The current Mobile IPv6 and NEMO specification support only IPv6.
   Hence, this specification extends those standards to allow the
   registration of IPv4 addresses and prefixes, respectively, and the
   transport of both IPv4 and IPv6 packets over the tunnel to the HA.
   This specification allows also the Mobile Node to roam over both IPv6
   and IPv4, including the case where Network Address Translation is
   present on the path.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mip6-nemo-v4traversal-00.txt

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


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

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


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

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-mip6-nemo-v4traversal-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

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

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

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

ENCODING mime
FILE /internet-drafts/draft-ietf-mip6-nemo-v4traversal-00.txt

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

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


--OtherAccess--

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

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

--NextPart--




From mip6-bounces@ietf.org Thu Oct 20 18:50:54 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ESjFO-0006U1-Tk; Thu, 20 Oct 2005 18:50:54 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ESjEb-0006BN-JF; Thu, 20 Oct 2005 18:50:05 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA20184;
	Thu, 20 Oct 2005 18:49:55 -0400 (EDT)
Received: from [132.151.6.50] (helo=newodin.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1ESjQa-0004el-IR; Thu, 20 Oct 2005 19:02:29 -0400
Received: from mlee by newodin.ietf.org with local (Exim 4.43)
	id 1ESjEY-00066z-24; Thu, 20 Oct 2005 18:50:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1ESjEY-00066z-24@newodin.ietf.org>
Date: Thu, 20 Oct 2005 18:50:02 -0400
X-Spam-Score: 0.4 (/)
X-Scan-Signature: f66b12316365a3fe519e75911daf28a8
Cc: mip6@ietf.org
Subject: [Mip6] I-D
	ACTION:draft-ietf-mip6-bootstrapping-integrated-dhc-00.txt 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

--NextPart

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

	Title		: MIP6-bootstrapping via DHCPv6 for the Integrated Scenario
	Author(s)	: K. Chowdhury, A. Yegin
	Filename	: draft-ietf-mip6-bootstrapping-integrated-dhc-00.txt
	Pages		: 22
	Date		: 2005-10-20
	
   The Mobile IPv6 bootstrapping problem statement describes two main
   scenarios.  In the first scenario (i.e. the split scenario), the
   mobile node's mobility service is authorized by a different service
   authorizer than the basic network access authorizer.  In the second
   scenario (i.e. the integrated scenario), the mobile node's mobility
   service is authorized by the same service authorizer as the basic
   network access service authorizer.  This document defines a method
   for home agent information discovery based on DHCPv6 for the
   integrated scenario.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mip6-bootstrapping-integrated-dhc-00.txt

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


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

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


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

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-mip6-bootstrapping-integrated-dhc-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

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

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

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

ENCODING mime
FILE /internet-drafts/draft-ietf-mip6-bootstrapping-integrated-dhc-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-mip6-bootstrapping-integrated-dhc-00.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

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


--OtherAccess--

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

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

--NextPart--





From mip6-bounces@ietf.org Thu Oct 20 18:51:17 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ESjFl-0006cO-T7; Thu, 20 Oct 2005 18:51:17 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ESjEd-0006DH-VM; Thu, 20 Oct 2005 18:50:08 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA20200;
	Thu, 20 Oct 2005 18:49:57 -0400 (EDT)
Received: from [132.151.6.50] (helo=newodin.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1ESjQa-0004ed-El; Thu, 20 Oct 2005 19:02:30 -0400
Received: from mlee by newodin.ietf.org with local (Exim 4.43)
	id 1ESjEX-00066a-TM; Thu, 20 Oct 2005 18:50:01 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1ESjEX-00066a-TM@newodin.ietf.org>
Date: Thu, 20 Oct 2005 18:50:01 -0400
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 9a2be21919e71dc6faef12b370c4ecf5
Cc: mip6@ietf.org
Subject: [Mip6] I-D ACTION:draft-ietf-mip6-firewalls-03.txt 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

--NextPart

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

	Title		: Mobile IPv6 and Firewalls: Problem statement
	Author(s)	: F. Le, et al.
	Filename	: draft-ietf-mip6-firewalls-03.txt
	Pages		: 23
	Date		: 2005-10-20
	
Network elements such as firewalls are an integral aspect of a
   majority of IP networks today, given the state of security in the
   Internet, threats, and vulnerabilities to data networks.  Current IP
   networks are predominantly based on IPv4 technology and hence
   firewalls have been designed for these networks.  Deployment of IPv6
   networks is currently progressing, albeit at a slower pace.
   Firewalls for IPv6 networks are still maturing and in development.

   Mobility support for IPv6 has been standardized as specified in RFC
   3775.  Given the fact that Mobile IPv6 is a recent standard, most
   firewalls available for IPv6 networks do not support Mobile IPv6.

   Unless firewalls are aware of Mobile IPv6 protocol details, these
   security devices will interfere in the smooth operation of the
   protocol and can be a detriment to deployment.  This document
   captures the issues that may arise in the deployment of IPv6 networks
   when they support Mobile IPv6 and firewalls.

   The issues are not only applicable to firewalls protecting enterprise
   networks, but are also applicable in 3G mobile networks such as GPRS/
   UMTS and cdma2000 networks.

   The goal of this Internet draft is to highlight the issues with
   firewalls and Mobile IPv6 and act as an enabler for further
   discussion.  Issues identified here can be solved by developing
   appropriate solutions in the MIP6 WG.

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

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


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

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


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

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-mip6-firewalls-03.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

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

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

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

ENCODING mime
FILE /internet-drafts/draft-ietf-mip6-firewalls-03.txt

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

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


--OtherAccess--

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

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

--NextPart--




From mip6-bounces@ietf.org Thu Oct 20 23:01:01 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ESn9R-0001rs-Do; Thu, 20 Oct 2005 23:01:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ESn9Q-0001rg-0L
	for mip6@megatron.ietf.org; Thu, 20 Oct 2005 23:01:00 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA19292
	for <mip6@ietf.org>; Thu, 20 Oct 2005 23:00:49 -0400 (EDT)
Received: from omgo.iij.ad.jp ([202.232.30.157])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ESnLT-0005CU-Oh
	for mip6@ietf.org; Thu, 20 Oct 2005 23:13:28 -0400
Received: OTM-MO id j9L30mNo009778; Fri, 21 Oct 2005 12:00:48 +0900 (JST)
Received: OTM-MIX0 id j9L30lIp028300; Fri, 21 Oct 2005 12:00:47 +0900 (JST)
Received: from localhost (jc-ssh.iij.ad.jp [192.168.174.22])
	by jc-smtp.iij.ad.jp (JC-SMTP/jc-smtp) id j9L30lt1023090
	for <mip6@ietf.org>; Fri, 21 Oct 2005 12:00:47 +0900 (JST)
Date: Fri, 21 Oct 2005 12:00:51 +0900 (JST)
Message-Id: <20051021.120051.88661256.keiichi@iijlab.net>
To: mip6@ietf.org
Subject: Re: [Mip6] I-D ACTION:draft-ietf-mip6-nemo-v4traversal-00.txt 
From: Keiichi SHIMA <keiichi@iijlab.net>
In-Reply-To: <E1ESjEX-00065v-LZ@newodin.ietf.org>
References: <E1ESjEX-00065v-LZ@newodin.ietf.org>
X-Mailer: Mew version 4.2.50 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Content-Transfer-Encoding: 7bit
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Hello Hesham,

I've read the draft and have a few comments. (for now. may send more
later..)


- The draft seems discussing two separate issues.

I think, v4traversal and supporting IPv4 HoA/network are different
issues.  Don't we need to think an scenario, which doesn't need
v4traversal but need IPv4 communication, and vice versa?  In the
previous discussion (two months ago in the MIP6 mailing list, maybe),
you mentioned that separating these two issues add complexity.  But
I'm afraid I still don't understand what complexity is added when we
divide the above two issues.  It should be helpful if you could show
some examples.


- more detailed operational procedure is required

  The draft doesn't describe mobile router/home agent operation when a
  static IPv4 address or IPv4 mobile network prefix is used.  I think
  some text similar to the text in section 5 and 6 of my
  draft(draft-shima-nemo-v4prefix) is required.


- typo in page14,

The source and dst addresses described in a BA message are wrong.

>    B. Binding acknowledgement sent by the home agent:
>               IPv4 header (src=V4ADDR, dst=HAADDR)
>                  [UDP header] (If V4ADDR != V4CoA)
>                    IPv6 header (src=V4CoA, dst=HAADDR)
>                       Route HRD Type 2
>                           HOA (IPv6 home address)
>                       Mobility header
>                           BA ([IPv4 ACK], NAT DET)

The outer source should be HAADDR and dst should be V4ADDR.
The inner source should be HAADDR and dst should be V4CoA.


- in page 16

>    - If the binding update is accepted for the IPv4 home address, the
>      home agent MUST create a binding cache entry for the IPv4 home
>      address/prefix. If a single IPv4 home address were requested, it
                       ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>      MAY be stored in the IPv4-mapped IPv6 address format. The home
       ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>      agent MUST include an IPv4 acknowledgement option in the mobility
>      header containing the binding acknowledgement.

What does the above underlined text mean?  It seems you are discussing
implementation specific thing, which should not be discussed in the
specification.


- (minor) terminology

  I don't think the word 'IPv4 home address' is a good wording, since
  the word is already used by MIP4.  So, maybe other wording, such as
  'IPv4 static address' seems better.


---
Keiichi SHIMA
IIJ Research Laboratory <keiichi@iijlab.net>
KAME Project <keiichi@kame.net>

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



From mip6-bounces@ietf.org Thu Oct 20 23:26:04 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ESnXg-0007H0-46; Thu, 20 Oct 2005 23:26:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ESnXd-0007Gv-Vg
	for mip6@megatron.ietf.org; Thu, 20 Oct 2005 23:26:02 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA20306
	for <mip6@ietf.org>; Thu, 20 Oct 2005 23:25:50 -0400 (EDT)
Received: from mail.flarion.com ([63.103.94.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ESnjf-0005v3-UZ
	for mip6@ietf.org; Thu, 20 Oct 2005 23:38:30 -0400
Received: from ftmailserver.flariontech.com ([10.10.1.140]) by
	mail.flarion.com with Microsoft SMTPSVC(5.0.2195.6713);
	Thu, 20 Oct 2005 23:25:46 -0400
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
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] I-D ACTION:draft-ietf-mip6-nemo-v4traversal-00.txt 
Date: Thu, 20 Oct 2005 23:25:46 -0400
Message-ID: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCD76@ftmailserver.flariontech.com>
Thread-Topic: [Mip6] I-D ACTION:draft-ietf-mip6-nemo-v4traversal-00.txt 
Thread-Index: AcXV7H4z7y0mXnNdTVSP9TvN9o1RzQAAX+Ng
From: "Soliman, Hesham" <H.Soliman@flarion.com>
To: "Keiichi SHIMA" <keiichi@iijlab.net>, <mip6@ietf.org>
X-OriginalArrivalTime: 21 Oct 2005 03:25:46.0997 (UTC)
	FILETIME=[208D7A50:01C5D5EF]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b2809b6f39decc6de467dcf252f42af1
Content-Transfer-Encoding: quoted-printable
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Hello Keiichi,=20

Thanks for the comments. Responses inline.

 >=20
 > - The draft seems discussing two separate issues.
 >=20
 > I think, v4traversal and supporting IPv4 HoA/network are different
 > issues.  Don't we need to think an scenario, which doesn't need
 > v4traversal but need IPv4 communication, and vice versa?

=3D> Absolutely. That's why the draft allows a node to use an IPv4
home address whether it's in an IPv4 or an IPv6 network.

  In the
 > previous discussion (two months ago in the MIP6 mailing list, maybe),
 > you mentioned that separating these two issues add complexity. =20

=3D> Yes.

   But
 > I'm afraid I still don't understand what complexity is added when we
 > divide the above two issues.  It should be helpful if you could show
 > some examples.

=3D> What I was referring to before was writing two different specs in=20
parallel. It's a matter of organisation and working out dependencies=20
between documents. One solution can easily address having IPv4 home=20
or coa as you can see from this document.=20

 >=20
 >=20
 > - more detailed operational procedure is required
 >=20
 >   The draft doesn't describe mobile router/home agent=20
 > operation when a
 >   static IPv4 address or IPv4 mobile network prefix is used. =20

=3D> Could you be specific on what is missing from the current
draft in terms of operation? Meaning, as an implementer, when
you read the draft, what more do you need to know to implement it?

 > - typo in page14,
 >=20
 > The source and dst addresses described in a BA message are wrong.
 >=20
 > >    B. Binding acknowledgement sent by the home agent:
 > >               IPv4 header (src=3DV4ADDR, dst=3DHAADDR)
 > >                  [UDP header] (If V4ADDR !=3D V4CoA)
 > >                    IPv6 header (src=3DV4CoA, dst=3DHAADDR)
 > >                       Route HRD Type 2
 > >                           HOA (IPv6 home address)
 > >                       Mobility header
 > >                           BA ([IPv4 ACK], NAT DET)
 >=20
 > The outer source should be HAADDR and dst should be V4ADDR.
 > The inner source should be HAADDR and dst should be V4CoA.
 >=20

=3D> Thanks, will fix that in the next rev.

 >=20
 > - in page 16
 >=20
 > >    - If the binding update is accepted for the IPv4 home=20
 > address, the
 > >      home agent MUST create a binding cache entry for the IPv4 home
 > >      address/prefix. If a single IPv4 home address were=20
 > requested, it
 >                       =20
 > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 > >      MAY be stored in the IPv4-mapped IPv6 address format. The home
 >        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 > >      agent MUST include an IPv4 acknowledgement option in=20
 > the mobility
 > >      header containing the binding acknowledgement.
 >=20
 > What does the above underlined text mean?  It seems you are=20
 > discussing
 > implementation specific thing, which should not be discussed in the
 > specification.

=3D> The text means that you can store a unicast address in the mapped=20
format if you want (hence the MAY). Conceptual implementation issues=20
are discussed in most specs actually. See for instance RFC 3775, RFC =
2461,=20
IPsec RFCs ....etc.=20

 > - (minor) terminology
 >=20
 >   I don't think the word 'IPv4 home address' is a good wording, since
 >   the word is already used by MIP4.  So, maybe other wording, such as
 >   'IPv4 static address' seems better.

=3D> Hmm, I don't think MIPv4 will sue us for it :) It seems appropriate
for the use. I'm open to suggestions, but IPv4 static address is not =
appropriate
IMO given that it is allocated statically or dynamically.=20

Hesham

 >=20
 >=20
 > ---
 > Keiichi SHIMA
 > IIJ Research Laboratory <keiichi@iijlab.net>
 > KAME Project <keiichi@kame.net>
 >=20
 > _______________________________________________
 > Mip6 mailing list
 > Mip6@ietf.org
 > https://www1.ietf.org/mailman/listinfo/mip6
 >=20

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D
This email may contain confidential and privileged material for the sole =
use
 of the intended recipient.  Any review or distribution by others is =
strictly
 prohibited.  If you are not the intended recipient please contact the =
sender
 and delete all copies.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D


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



From mip6-bounces@ietf.org Fri Oct 21 00:30:34 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ESoY6-0005fL-B2; Fri, 21 Oct 2005 00:30:34 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ESQA0-00013D-Dm; Wed, 19 Oct 2005 22:28:04 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA04589;
	Wed, 19 Oct 2005 22:27:53 -0400 (EDT)
Received: from ms-smtp-04.nyroc.rr.com ([24.24.2.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1ESQLr-0004cg-CH; Wed, 19 Oct 2005 22:40:19 -0400
Received: from hpn307pc2 (cpe-69-204-120-221.rochester.res.rr.com
	[69.204.120.221])
	by ms-smtp-04.nyroc.rr.com (8.12.10/8.12.10) with SMTP id
	j9K2RwV2018914; Wed, 19 Oct 2005 22:27:58 -0400 (EDT)
Message-ID: <006401c5d51d$e3e28bd0$6701a8c0@hpn307pc2>
From: "Wendi Heinzelman" <wheinzel@ece.rochester.edu>
To: <mip6@ietf.org>, <mip4@ietf.org>
Date: Wed, 19 Oct 2005 22:27:59 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Virus-Scanned: Symantec AntiVirus Scan Engine
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Fri, 21 Oct 2005 00:30:33 -0400
Cc: Wendi Heinzelman <wheinzel@ece.rochester.edu>
Subject: [Mip6] SenSys 2005 Final Call for Participation
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

[Note the early registration deadline is October 28, 2005]

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

       Call for Participation
       ACM SenSys 2005
San Diego, November 2-4, 2005
    http://sensys.csail.mit.edu/

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

You are cordially invited to participate in the upcoming 3rd ACM Conference on
Embedded Networked Sensor Systems (SenSys 2005). This is a highly selective
single-track forum for the presentation of research results on systems issues in the
emerging area of embedded, networked sensors. SenSys provides a crossdisciplinary
venue for researchers addressing the rich space of networked sensor
system design issues to interact, present and exchange research results, and
demonstrate their work in a hands-on research exhibition.

Technical Program
This year's program at SenSys consists of 21 high quality papers covering cutting
edge research on a wide range of topics including sensornet services, real-world
deployment experiences, networking, synchronization, applications, design
frameworks, and software support. Complete details of the technical program can be
found at http://sensys.csail.mit.edu.

Keynote Speakers
Two renowned speakers will provide keynote talks: Professor John Delaney from the
University of Washington and Dr. Henry Tirri from Nokia.

Poster Session
SenSys will feature a poster session that will showcase recent and on-going work.
There will be 16 posters featuring a range of cutting-edge research.

Demo Session
Demonstrations showing innovative research and applications will be featured
throughout the conference. There will be 25 demos that include technology, platforms,
and demonstrations of realistic applications of wireless sensor networks.

Registration
Registration can be completed at http://sensys.csail.mit.edu/registration.htm. Early
registration will be available until October 28, 2005.

Accommodations
SenSys will take place in the city of San Diego, in sunny southern California. The
conference will be hosted at the San Diego Marriott Mission Valley hotel, where a
block of rooms has been reserved at a discounted rate (ask for the ACM rate). 
Reservations must be made by contacting the San Diego Marriott Mission Valley 
directly at 1-800-842-5329.

We look forward to seeing you in San Diego for SenSys 2005!

ACM SenSys 2005 is sponsored by SIGCOMM, SIGMOBILE, SIGARCH, 
SIGOPS, SIGMETRICS and SIGBED.

Corporate Sponsors
- Intel
- Microsoft Research
- Nokia
- Crossbow Technology, Inc.
- National Science Foundation
- Chipcon

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

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



From mip6-bounces@ietf.org Fri Oct 21 04:49:21 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ESsaX-0006fq-RA; Fri, 21 Oct 2005 04:49:21 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ESsaV-0006fi-AV
	for mip6@megatron.ietf.org; Fri, 21 Oct 2005 04:49:19 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA07008
	for <mip6@ietf.org>; Fri, 21 Oct 2005 04:49:08 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ESsmb-00085u-SJ
	for mip6@ietf.org; Fri, 21 Oct 2005 05:01:50 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id j9L8mgm10615; Fri, 21 Oct 2005 10:48: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
	j9L8mgut055451; Fri, 21 Oct 2005 10:48:42 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200510210848.j9L8mgut055451@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Vijay Devarapalli <vijayd@iprg.nokia.com>
Subject: Re: [Mip6] comments about draft-ietf-mip6-ikev2-ipsec-03.txt 
In-reply-to: Your message of Tue, 18 Oct 2005 08:11:25 PDT.
	<4355109D.3090303@iprg.nokia.com> 
Date: Fri, 21 Oct 2005 10:48:42 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f0b5a4216bfa030ed8a6f68d1833f8ae
Cc: mip6@ietf.org, vijay.devarapalli@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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   >  In 4.1 page 4:
   > 
   >    o  ESP encapsulation of the payload packets tunneled between the
   >       mobile node and the home agent MAY be supported and used.
   > 
   > => I believe the document should restrict choices to only three options:
   >  - fine granularity: selector on MH types
   >  - medium granularity/RFC 3776 compatibility: selector on protocol = MH
   >  - coarse granularity: any protocol (here).
   
   ok. but did you want to see some text. or?
   
=> yes, I believe it is important to have some text because readers
should both understand they have some choices (note some are needed
for compatibility with current implementations, for instance coarse
grain only selectors for forwarded traffic) but not too many (i.e.,
we recommend a subset of possible profiles).

   > 
   >    o  When securing Binding Updates, Binding Acknowledgements, and
   >       prefix discovery, both the mobile nodes and the home agents MUST
   >       support and SHOULD use the Encapsulating Security Payload (ESP)
   >       [6] header in transport mode and MUST use a non-null payload
   >       authentication algorithm to provide data origin authentication,
   >       connectionless integrity and optional anti-replay protection.
   > 
   > => s/optional/when possible/ ?
   
   its optional because the binding updates have a sequence
   number which provides replay protection.
   
=> no, this sequence number provides sequencing but no replay protection
as it can round up. I strongly disagree here: the IPsec anti-replay
protection is necessary and it was not made mandatory only because it
is not always possible. So I maintain my proposal.

   >  In 5 page 8:
   > 
   >    This section describes the SPD and SAD entries that can be used to
   > 
   > => I propose to add something explaining here and in section 6 that
   > the care-of address is the primary care-of address. BTW this is required
   > from time to time and it makes the code for tracking and updating SPD/SAD
   > far easier to write.
   
   I dont think I understand. are you saying the MN should
   use its primary CoA and not any CoA?

=> yes, IMHO the level for using the primary CoA in place of any CoA
is in some cases MUST and in all cases at least a SHOULD. The RFC 3775
is a bit lax about this (it uses "the CoA" for instance) but here I propose
to be clear.

   what if the monami6
   WG extends MIPv6 registrations to include multiple CoAs?

=> this will be the job of the monami6 WG to produce the proper guidelines.

   I would like to support that with just one SA.
   
=> I agree (I even suggested this with the multiple MR document as you'll
be able to see when it will be published :-).

   >  In 5.1, 5.2 and 5.3 pages 9, 10 and 11: SPD-S entries work both ways
   > so there are twice the right number of SPD-S entries. I propose to copy
   > the section 6 stuff.
   
   not if we want to enforce the case where only the MN sends
   BU and not BAck to the HA and the HA sends BAck only. right?
   
=> no, the section 6 does this so there is no reason to have twice
entries in 5.x. As I explain later one good SPD-S entry does the
right job in both direction without mixing MH types.
I propose to change:
        mobile node SPD-S:
          - IF source = home_address_1 & destination = home_agent_1 &
               proto = MH & mh_type = BU
            Then use SA SA1

          - IF source = home_agent_1 & destination = home_address_1 &
               proto = MH & mh_type = BAck
            Then use SA SA2

into:
      mobile node SPD-S:
         - IF source = home_address_1 & destination = home_agent_1 &
              proto = MH & local_mh_type = BU & remote_mh_type = BAck
           Then use SA SA1 (OUT) and SA2 (IN)
etc.

   
   >  In 5.4 page 11 I can't see a trace of the protocol=MH option...
   
   5.4 is about payload traffic. that means protocol = 'any'.
   
=> so perhaps we should add a subsection here to explain how to do
the protocol=MH option (which is easier than the "any" because it is
not equivalent to a transport mode applied to a tunnel). Note I have
the same concern about 6.1.4 (where currently proto = X ?! :-).
   
   >    ...  The TSi and
   >    TSr payloads in the above examples will contain many other selectors
   >    apart from home_address_1.  For the sake of brevity, they are not
   >    shown here.
   > 
   > => this statement is fully not understandable for me. I don't believe
   > the idea is to share SAs. Can you explain or remove this?
   
   I am just saying that we are not showing the TSi or TSr
   payload completely in the example configurations. only
   those values that are relevant for MIPv6.
   
=> so you can see how to make the text clearer...

   >  In 6.1.2 page 13 and 6.1.4 page 15:
   > 
   >                        outer src addr = coa,
   >                        outer dst addr = coa,
   > 
   > => s/coa/[primary_]care-of_address_1/
   
   see my comment above about primary CoA
   
=> at least the abbrev coa is bad and not sound with the context.

   >  In 6.1.4 page 15:
   > 
   >        mobile node SPD-S:
   >          - IF interface = IPv6 tunnel to home_agent_1 & proto = X
   > 
   > => this is fully wrong. The SPD-S entry is really similar to the 6.1.2,
   > i.e., should be:
   > 
   >        mobile node SPD-S:
   >          - IF source = home_address_1 & destination = any & proto = any
   >          etc
   
   how do you distinguish between payload traffic sent to the HA
   and to the CN?
   
=> so in fact you propose the interface in place of not in the BCE?
IMHO this is correct as it is fully equivalent but:
 - SPD-S entries are symmetrical so there is only one for MN and one for the HA
 - proto is any, not X
 - the second SPD-S entry for the MN should have the same layout than others
   (in fact it is the same than the first one as it should be only one entry)
 - s/coa/.../ as usual
 - we can say one can use a transport mode over the tunnel as it will give
   exactly the same layout for packets and the same selection (proto = any
   in tunnel mode for inner protocol, proto = 41 in transport mode for outer
   protocol).

   >    ...  The mobile node
   >    MAY use a range of selectors that includes the mobility message types
   >    for Binding Update and Binding Acknowledgement to use the same pair
   >    of IPsec security association for both messages.
   > 
   > => s/MAY/SHOULD/ because I believe it is a very bad idea to have two
   > SA pairs.
   
   why is it a bad idea? without that we cant enforce a policy where
   we want the HA to send a BAck, but not a BU.
   
=> you missed the discussion about the selectors for MH:
remote_mh_type=BAck on the MN means the HA can only send BAck.
So the right strict policy is enforced in the examples.
Now why it is a bad idea:
 - it takes time to establish a second SA pair
 - the HA has to find the right IKE SA (if it fails, it will create
   a new IKE session to an unknown CoA). This can't be done using
   the usual way based on the peer address.

   >    After the IKE_AUTH exchange completes, the mobile node initiates
   >    CREATE_CHILD_SA exchanges to negotiate additional security
   >    associations for protecting Return Routability signaling, Mobile
   >    Prefix Discovery messages and optionally payload traffic.
   > 
   > => I propose:
   > 
   >    After the IKE_AUTH exchange completes, the mobile node initiates
   >    CREATE_CHILD_SA exchanges to negotiate additional security
   >    associations for protecting Return Routability signaling or
   >    optionally payload traffic, and Mobile Prefix Discovery messages.
   
   whats the difference?
   
=> X and Y and Z != (X or Z) and Y...
RR (X) and payload (Z) are alternatives.

   > => s/fetched/got back/ ? My concern is the term "fetch" doesn't match the
   > case where the certificate is sent in a CERT payload.
   
   how about "obtained"?
   
=> fine!

   >  In 6.3 page 18:
   > 
   >    ... on the mobile node
   >    when it receives the Binding acknowledgement sent by the home agent.
   > 
   > => I discussed this with Shinta-san and the endpoint update is performed
   > by the mobile node after it sends the BU, i.e., the MN doesn't wait for
   > the BA. Cf draft-sugimoto-mip6-pfkey-migrate-01.txt 4.1.2 page 7.
   
   I dont mind making the change, but do you think the mobile node
   can start using the new CoA for tunneled packets before it is
   sure the BU has been processed by the HA?
   
=> usually it can't use the old CoA... and we can be optimistic.
Note the HA should not check the outer source address (cf RFC 2401(bis))
so if the BU fails the issue will be for returned traffic (CN->HA->MN).

   there are many EAP methods that support mutual authentication.
   when such EAP methods are used, I dont think the mobile node
   needs to use public key mechanism to authenticate the home
   agent.
   
=> IMHO this discussion is not at the right place: it is not a MIPv6
issue but an IPsec issue. So my concern is we should restrict ourselves
to the current IKEv2/2401bis and not rely on still in discussion extensions.
   
   >  In 12 pages 21 and 22: I believe some authors have in fact only the
   > editor role, this should be reflected.
   > 
   >  In 12.2 page 22:
   > 
   >    [14]  Sugimoto, S., "PF_KEY Extension as an Interface between Mobile
   >          IPv6 and IPsec/IKE", draft-sugimoto-mip6-pfkey-migrate-01 (work
   >          in progress), September 2005.
   > 
   > => me and Masahide Nakamura are co-authors.
   
   I am using xml2rfc. looks like the bibxml files list only
   one author. should the bibxml files be fixed?
   
=> argh! It seems it is the case but it can be hard to do it in time.

Thanks

Francis.Dupont@enst-bretagne.fr

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



From mip6-bounces@ietf.org Fri Oct 21 06:30:39 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ESuAZ-0007dT-L1; Fri, 21 Oct 2005 06:30:39 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ESuAX-0007dL-FZ
	for mip6@megatron.ietf.org; Fri, 21 Oct 2005 06:30:37 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA12376
	for <mip6@ietf.org>; Fri, 21 Oct 2005 06:30:25 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ESuMd-0003Au-SF
	for mip6@ietf.org; Fri, 21 Oct 2005 06:43:09 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id j9LATnm20818; Fri, 21 Oct 2005 12:29: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
	j9LATngl056144; Fri, 21 Oct 2005 12:29:50 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200510211029.j9LATngl056144@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Vijay Devarapalli <vijayd@iprg.nokia.com>
Subject: Re: [Mip6] [Fwd: I-D
	ACTION:draft-devarapalli-mip6-ikev1-bootstrap-00.txt] 
In-reply-to: Your message of Tue, 18 Oct 2005 23:41:35 PDT.
	<4355EA9F.2070903@iprg.nokia.com> 
Date: Fri, 21 Oct 2005 12:29:49 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   here is a short draft on MIP6 bootstrapping using
   IKEv1. the draft talks about 2 options, modecfg
   and running DHCP over the IPsec tunnel. the draft
   also talks about supporting legacy authentication
   mechanisms.
   
=> note that modecfg and xauth were not standardized by the IETF
and for xauth according to a very good reason (as xauth was proved
as very bad for a security point of view).
I believe in IKEv2 so I don't know if an IKEv1 bootstrapping work
is a good idea...

Thanks

Francis.Dupont@enst-bretagne.fr

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



From mip6-bounces@ietf.org Fri Oct 21 08:19:04 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ESvop-0007yL-96; Fri, 21 Oct 2005 08:16:19 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ESvon-0007y6-Jm
	for mip6@megatron.ietf.org; Fri, 21 Oct 2005 08:16:17 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17712
	for <mip6@ietf.org>; Fri, 21 Oct 2005 08:16:07 -0400 (EDT)
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ESw0w-0006sP-2e
	for mip6@ietf.org; Fri, 21 Oct 2005 08:28:50 -0400
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id j9LBh9O03280;
	Fri, 21 Oct 2005 04:43:09 -0700
X-mProtect: <200510211143> Nokia Silicon Valley Messaging Protection
Received: from es-mob-wano19288.ntc.nokia.com (172.17.192.88,
	claiming to be "[127.0.0.1]")
	by darkstar.iprg.nokia.com smtpdxAZ5A4; Fri, 21 Oct 2005 04:43:07 PDT
Message-ID: <4358DBF0.7040102@iprg.nokia.com>
Date: Fri, 21 Oct 2005 05:15:44 -0700
From: Vijay Devarapalli <vijayd@iprg.nokia.com>
User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
Subject: Re: [Mip6] comments about draft-ietf-mip6-ikev2-ipsec-03.txt
References: <200510210848.j9L8mgut055451@givry.rennes.enst-bretagne.fr>
In-Reply-To: <200510210848.j9L8mgut055451@givry.rennes.enst-bretagne.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 27ec2ff0f5c3b18b49c722f4f1748838
Content-Transfer-Encoding: 7bit
Cc: mip6@ietf.org, vijay.devarapalli@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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Francis Dupont wrote:
>  In your previous mail you wrote:
> 
>    >  In 4.1 page 4:
>    > 
>    >    o  ESP encapsulation of the payload packets tunneled between the
>    >       mobile node and the home agent MAY be supported and used.
>    > 
>    > => I believe the document should restrict choices to only three options:
>    >  - fine granularity: selector on MH types
>    >  - medium granularity/RFC 3776 compatibility: selector on protocol = MH
>    >  - coarse granularity: any protocol (here).
>    
>    ok. but did you want to see some text. or?
>    
> => yes, I believe it is important to have some text because readers
> should both understand they have some choices (note some are needed
> for compatibility with current implementations, for instance coarse
> grain only selectors for forwarded traffic) but not too many (i.e.,
> we recommend a subset of possible profiles).

can you suggest some text here?

>    > 
>    >    o  When securing Binding Updates, Binding Acknowledgements, and
>    >       prefix discovery, both the mobile nodes and the home agents MUST
>    >       support and SHOULD use the Encapsulating Security Payload (ESP)
>    >       [6] header in transport mode and MUST use a non-null payload
>    >       authentication algorithm to provide data origin authentication,
>    >       connectionless integrity and optional anti-replay protection.
>    > 
>    > => s/optional/when possible/ ?
>    
>    its optional because the binding updates have a sequence
>    number which provides replay protection.
>    
> => no, this sequence number provides sequencing but no replay protection
> as it can round up. I strongly disagree here: the IPsec anti-replay
> protection is necessary and it was not made mandatory only because it
> is not always possible. So I maintain my proposal.

from what I remember, it was made optional because there is
replay protection through BU sequence number. so I have to
disagree. its a 32 bit sequence number. takes a long time
to wrap around.


>    >  In 5 page 8:
>    > 
>    >    This section describes the SPD and SAD entries that can be used to
>    > 
>    > => I propose to add something explaining here and in section 6 that
>    > the care-of address is the primary care-of address. BTW this is required
>    > from time to time and it makes the code for tracking and updating SPD/SAD
>    > far easier to write.
>    
>    I dont think I understand. are you saying the MN should
>    use its primary CoA and not any CoA?
> 
> => yes, IMHO the level for using the primary CoA in place of any CoA
> is in some cases MUST and in all cases at least a SHOULD. The RFC 3775
> is a bit lax about this (it uses "the CoA" for instance) but here I propose
> to be clear.
> 
>    what if the monami6
>    WG extends MIPv6 registrations to include multiple CoAs?
> 
> => this will be the job of the monami6 WG to produce the proper guidelines.
> 
>    I would like to support that with just one SA.
>    
> => I agree (I even suggested this with the multiple MR document as you'll
> be able to see when it will be published :-).

I prefer the looser text so that others can extend it to
support multiple CoAs. otherwise monami6 WG has to
specifically say "RFC 3775 says blah blah.. but.. but we
have to relax the blah blah.. requirement".

> 
>    >  In 5.1, 5.2 and 5.3 pages 9, 10 and 11: SPD-S entries work both ways
>    > so there are twice the right number of SPD-S entries. I propose to copy
>    > the section 6 stuff.
>    
>    not if we want to enforce the case where only the MN sends
>    BU and not BAck to the HA and the HA sends BAck only. right?
>    
> => no, the section 6 does this so there is no reason to have twice
> entries in 5.x. As I explain later one good SPD-S entry does the
> right job in both direction without mixing MH types.
> I propose to change:
>         mobile node SPD-S:
>           - IF source = home_address_1 & destination = home_agent_1 &
>                proto = MH & mh_type = BU
>             Then use SA SA1
> 
>           - IF source = home_agent_1 & destination = home_address_1 &
>                proto = MH & mh_type = BAck
>             Then use SA SA2
> 
> into:
>       mobile node SPD-S:
>          - IF source = home_address_1 & destination = home_agent_1 &
>               proto = MH & local_mh_type = BU & remote_mh_type = BAck
>            Then use SA SA1 (OUT) and SA2 (IN)

okay


>    >  In 5.4 page 11 I can't see a trace of the protocol=MH option...
>    
>    5.4 is about payload traffic. that means protocol = 'any'.
>    
> => so perhaps we should add a subsection here to explain how to do
> the protocol=MH option (which is easier than the "any" because it is
> not equivalent to a transport mode applied to a tunnel). Note I have
> the same concern about 6.1.4 (where currently proto = X ?! :-).

I made a mistake in my earlier mail. it shouldnt have been 'any'.
it should have been 'X', which 'X' stands for a particular
protocol. perhaps thats enough?

>    
>    >    ...  The TSi and
>    >    TSr payloads in the above examples will contain many other selectors
>    >    apart from home_address_1.  For the sake of brevity, they are not
>    >    shown here.
>    > 
>    > => this statement is fully not understandable for me. I don't believe
>    > the idea is to share SAs. Can you explain or remove this?
>    
>    I am just saying that we are not showing the TSi or TSr
>    payload completely in the example configurations. only
>    those values that are relevant for MIPv6.
>    
> => so you can see how to make the text clearer...

how about

    The TSi and
    TSr payloads in the above examples will contain many other selectors
    apart from home_address_1.  For the sake of brevity, we show only
    those values that relevant for Mobile IPv6.

>    >  In 6.1.4 page 15:
>    > 
>    >        mobile node SPD-S:
>    >          - IF interface = IPv6 tunnel to home_agent_1 & proto = X
>    > 
>    > => this is fully wrong. The SPD-S entry is really similar to the 6.1.2,
>    > i.e., should be:
>    > 
>    >        mobile node SPD-S:
>    >          - IF source = home_address_1 & destination = any & proto = any
>    >          etc
>    
>    how do you distinguish between payload traffic sent to the HA
>    and to the CN?
>    
> => so in fact you propose the interface in place of not in the BCE?
> IMHO this is correct as it is fully equivalent but:
>  - SPD-S entries are symmetrical so there is only one for MN and one for the HA
>  - proto is any, not X
>  - the second SPD-S entry for the MN should have the same layout than others
>    (in fact it is the same than the first one as it should be only one entry)
>  - s/coa/.../ as usual
>  - we can say one can use a transport mode over the tunnel as it will give
>    exactly the same layout for packets and the same selection (proto = any
>    in tunnel mode for inner protocol, proto = 41 in transport mode for outer
>    protocol).

how about the following?

        mobile node SPD-S:
          - IF interface = IPv6 tunnel to home_agent_1 & proto = X
            Then use SA ESP tunnel mode
                            IDi = user_1, IDr = home_agent_1,
                            TSi = home_address_1, X, port
                            TSr = any, X, port
                            outer src addr = coa
                            outer dst addr = home_agent_1,
                            inner src addr = home_address_1

        home agent SPD-S:
          - IF interface = IPv6 tunnel to home_address_1 & proto = X
            Then use SA ESP tunnel mode
                            IDi = home_agent_1, IDr = user_1,
                            TSi = any, X, port
                            TSr = home_address_1, X, port
                            outer src addr = home_agent_1,
                            outer dst addr = coa,
                            inner dst addr = home_address_1

> 
>    >    ...  The mobile node
>    >    MAY use a range of selectors that includes the mobility message types
>    >    for Binding Update and Binding Acknowledgement to use the same pair
>    >    of IPsec security association for both messages.
>    > 
>    > => s/MAY/SHOULD/ because I believe it is a very bad idea to have two
>    > SA pairs.
>    
>    why is it a bad idea? without that we cant enforce a policy where
>    we want the HA to send a BAck, but not a BU.
>    
> => you missed the discussion about the selectors for MH:
> remote_mh_type=BAck on the MN means the HA can only send BAck.

hmm... I followed the discussion on the IPsec mailing list.
it seemed like not everybody agreed.

>    >    After the IKE_AUTH exchange completes, the mobile node initiates
>    >    CREATE_CHILD_SA exchanges to negotiate additional security
>    >    associations for protecting Return Routability signaling, Mobile
>    >    Prefix Discovery messages and optionally payload traffic.
>    > 
>    > => I propose:
>    > 
>    >    After the IKE_AUTH exchange completes, the mobile node initiates
>    >    CREATE_CHILD_SA exchanges to negotiate additional security
>    >    associations for protecting Return Routability signaling or
>    >    optionally payload traffic, and Mobile Prefix Discovery messages.
>    
>    whats the difference?
>    
> => X and Y and Z != (X or Z) and Y...
> RR (X) and payload (Z) are alternatives.

the current requirements say the MN must create security
associations to protect RR and MPD messages. payload is
optional. this assumes the payload does not include
RR messages.

> 
>    >  In 6.3 page 18:
>    > 
>    >    ... on the mobile node
>    >    when it receives the Binding acknowledgement sent by the home agent.
>    > 
>    > => I discussed this with Shinta-san and the endpoint update is performed
>    > by the mobile node after it sends the BU, i.e., the MN doesn't wait for
>    > the BA. Cf draft-sugimoto-mip6-pfkey-migrate-01.txt 4.1.2 page 7.
>    
>    I dont mind making the change, but do you think the mobile node
>    can start using the new CoA for tunneled packets before it is
>    sure the BU has been processed by the HA?
>    
> => usually it can't use the old CoA... and we can be optimistic.
> Note the HA should not check the outer source address (cf RFC 2401(bis))
> so if the BU fails the issue will be for returned traffic (CN->HA->MN).

I went back and looked at the text. it talks about the IKE SA.
data traffic wont be sent over the IKE SA. I guess there is
no urgent need to update the IKE SA?

> 
>    there are many EAP methods that support mutual authentication.
>    when such EAP methods are used, I dont think the mobile node
>    needs to use public key mechanism to authenticate the home
>    agent.
>    
> => IMHO this discussion is not at the right place: it is not a MIPv6
> issue but an IPsec issue. So my concern is we should restrict ourselves
> to the current IKEv2/2401bis and not rely on still in discussion extensions.

lets see what the IESG says about this.

Vijay


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



From mip6-bounces@ietf.org Fri Oct 21 08:34:59 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ESw6t-0007QH-Sw; Fri, 21 Oct 2005 08:34:59 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ESw6s-0007QB-9T
	for mip6@megatron.ietf.org; Fri, 21 Oct 2005 08:34:58 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA18766
	for <mip6@ietf.org>; Fri, 21 Oct 2005 08:34:47 -0400 (EDT)
Received: from keskus.netlab.hut.fi ([130.233.154.176])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ESwIz-0007Wu-Sy
	for mip6@ietf.org; Fri, 21 Oct 2005 08:47:31 -0400
Received: from [130.233.154.31] (pc31.netlab.hut.fi [130.233.154.31])
	by keskus.netlab.hut.fi (8.12.10/8.12.10) with ESMTP id j9LCYsU9023976
	for <mip6@ietf.org>; Fri, 21 Oct 2005 15:34:54 +0300 (EET DST)
Message-ID: <4358E0C4.7030307@netlab.hut.fi>
Date: Fri, 21 Oct 2005 15:36:20 +0300
From: Mikko Hautala <mhautala@netlab.hut.fi>
User-Agent: Debian Thunderbird 1.0.2 (X11/20050331)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: mip6@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Content-Transfer-Encoding: 7bit
Subject: [Mip6] Question on return routability ?
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Hi,

I have a simple question on the return routability procedure of
MIPv6 route optimization:

Is the return routability procedure needed every time a MN conducts a
MIPv6 handover ?


I've been reading the MIPv6 RFC and the route optimization design 
background, but
I haven't been able to figure it out explicitly.

I'm about 90% sure, that it is needed, because the care-of-address is 
used when calculating MAC.
Thus every time a MN moves, it must at least update the care-of token 
with COTI/COT messages...


 
Regards,
Mikko Hautala

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



From mip6-bounces@ietf.org Fri Oct 21 08:50:59 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ESwMN-0000p2-OY; Fri, 21 Oct 2005 08:50:59 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ESwMM-0000ox-51
	for mip6@megatron.ietf.org; Fri, 21 Oct 2005 08:50:58 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA19546
	for <mip6@ietf.org>; Fri, 21 Oct 2005 08:50:47 -0400 (EDT)
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ESwYT-00084p-8b
	for mip6@ietf.org; Fri, 21 Oct 2005 09:03:31 -0400
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id j9LCHue31307
	for <mip6@ietf.org>; Fri, 21 Oct 2005 05:17:56 -0700
X-mProtect: <200510211217> Nokia Silicon Valley Messaging Protection
Received: from es-mob-wano19288.ntc.nokia.com (172.17.192.88,
	claiming to be "[127.0.0.1]")
	by darkstar.iprg.nokia.com smtpdH0AvW2; Fri, 21 Oct 2005 05:17:53 PDT
Message-ID: <4358E417.5050709@iprg.nokia.com>
Date: Fri, 21 Oct 2005 05:50:31 -0700
From: Vijay Devarapalli <vijayd@iprg.nokia.com>
User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: mip6@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08e48e05374109708c00c6208b534009
Content-Transfer-Encoding: 7bit
Subject: [Mip6] Francis as co-author for draft-ietf-mip6-ikev2-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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

hi all,

Francis has contributed a lot to improving
draft-ietf-mip6-ikev2-ipsec. so I propose to add him
as a co-author for the spec.

Vijay


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



From mip6-bounces@ietf.org Fri Oct 21 09:58:20 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ESxPY-0000w8-1y; Fri, 21 Oct 2005 09:58:20 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ESxPX-0000vt-7L
	for mip6@megatron.ietf.org; Fri, 21 Oct 2005 09:58:19 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA23025
	for <mip6@ietf.org>; Fri, 21 Oct 2005 09:58:08 -0400 (EDT)
Received: from mail.cs.dal.ca ([129.173.66.204])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ESxbf-0001vR-Vz
	for mip6@ietf.org; Fri, 21 Oct 2005 10:10:53 -0400
Received: from torch (torch [129.173.67.129])
	by mail.cs.dal.ca (Postfix) with ESMTP
	id CBF45B05D; Fri, 21 Oct 2005 10:58:11 -0300 (ADT)
Date: Fri, 21 Oct 2005 10:58:11 -0300 (ADT)
From: Zhen Zhen <zhen@cs.dal.ca>
To: Mikko Hautala <mhautala@netlab.hut.fi>
Subject: Re: [Mip6] Question on return routability ?
In-Reply-To: <4358E0C4.7030307@netlab.hut.fi>
Message-ID: <Pine.GSO.4.58.0510211056540.18695@torch.cs.dal.ca>
References: <4358E0C4.7030307@netlab.hut.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org


Yes, it's true if the handover is across domains.

On Fri, 21 Oct 2005, Mikko Hautala wrote:

> Hi,
>
> I have a simple question on the return routability procedure of
> MIPv6 route optimization:
>
> Is the return routability procedure needed every time a MN conducts a
> MIPv6 handover ?
>
>
> I've been reading the MIPv6 RFC and the route optimization design
> background, but
> I haven't been able to figure it out explicitly.
>
> I'm about 90% sure, that it is needed, because the care-of-address is
> used when calculating MAC.
> Thus every time a MN moves, it must at least update the care-of token
> with COTI/COT messages...
>
>
>
> Regards,
> Mikko Hautala
>
> _______________________________________________
> 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 Fri Oct 21 10:03:13 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ESxUH-0002UG-Gq; Fri, 21 Oct 2005 10:03:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ESxUG-0002Tw-Qb
	for mip6@megatron.ietf.org; Fri, 21 Oct 2005 10:03:12 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23294
	for <mip6@ietf.org>; Fri, 21 Oct 2005 10:03:01 -0400 (EDT)
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ESxgO-00026l-Sm
	for mip6@ietf.org; Fri, 21 Oct 2005 10:15:46 -0400
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id CAE2389848
	for <mip6@ietf.org>; Fri, 21 Oct 2005 17:03:00 +0300 (EEST)
Message-ID: <4358F521.7080205@kolumbus.fi>
Date: Fri, 21 Oct 2005 17:03:13 +0300
From: Jari Arkko <jari.arkko@kolumbus.fi>
User-Agent: Mozilla Thunderbird 1.0 (X11/20041206)
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; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8fbbaa16f9fd29df280814cb95ae2290
Content-Transfer-Encoding: 7bit
Subject: [Mip6] Review of draft-ietf-mip6-bootstrapping-integrated-dhc-00.txt
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org


Hi,

I have read this draft. Thanks for writing this up! This is
indeed an important scenario that we must cover. Overall,
I'm happy with the solution architecture, particularly the
part where DHCP does not need any AAA interface and
the AAA-derived keys are not needed. But I still wonder
if the solution could be simplified some more, given that
the an eventual second authentication and AAA transaction
will be performed when you actually contact the discovered
home agent.

First, if the DHCP relay/NAS is aware of which client
is making the DHCP request, it does not seem necessary
to communicate home network information. The NAS
either got a home network-allocated HA in the AAA
transaction or it didn't. If it did, this can be passed on
in to the DHCP in the relay option. If it didn't, then we
can allow DHCP server to assign local home agents
on a round-robin (or whatever) basis. The latter approach
is nice in the sense that it does not require any additions
to existing NASes, DHCP relays, or AAA.

But I could be missing something.

Some additional points below.

Technical:

>3.2  Bootstrapping Message Sequence, Success Case
>
>   In the success case, the mobile node is able to acquire the home
>   agent address via a DHCPv6 query.  The message flows for home agent
>   allocation in the ASP and the MSP are illustrated below.  Since, in
>   the integrated scenario, the ASA and the MSA are the same, it can be
>   safely assumed that the AAAH used for network access authentication
>   (ASA) has access to the same database as the AAAH used for the
>   mobility service authentication (MSA).  Hence, the same AAAH can
>   authorize the mobile node for network access and mobility service at
>   the same time.
>
At the same time... hmm... there are two complications.
One is that the AAAH does not know at the time the network
access request is being made if the MN even wants mobility
service. This may not be a practical problem, unless only
the AAA infrastructure is taking care of load-balancing -type
issues for the home agents.

The other complication is that presumably, since [BOOT-SPLIT]
is being used for the actual communication with the home agent,
then *another* AAA transaction will be made. So I would say
that what this draft is doing is really only about discovery.
It can not guarantee that the subsequent transaction will
be authorized nor can it prevent that someone who hasn't
gone through the discovery part will be denied service.

This questions the need to spend a lot of effort for the
discovery part.

>   (2) The mobile node sends a DHCPv6 Information Request message
>   [RFC3315] to the All_DHCP_Relay_Agents_and_Servers multicast address.
>   In this message the mobile node (DHCP client) SHALL include the
>   Option Code for Home Network Identifier Option [HAOPT] in the
>   OPTION_ORO, Home Network Identifier Option with id-type set to 1 and
>   the Home Network Identifier field set to the network realm of the
>  
>
Why do we need this option? Presumably, the DHCP relay
is aware which NAS client this is, and picks the correct
information.

>   This section describes a scenario where the mobile node requests for
>   home agent allocation in the ASP by setting the id-type field to zero
>   in the Home Network Identifier Option in the DHCPv6 request message.
>   In this scenario, the ASP becomes the MSP for the duration of the
>   network access authentication session.
>  
>
There's an assumption here about the (non-)interleaving
of mobility and access services that I'm not sure I like.
Presumably you'd want the ASP to become an MSP for a
given duration, possibly at least for a while beyond the
time the mobile node is at this access network. Or at
the very least you should allow this.

>   (3) The Relay Agent intercepts the Information Request from the
>   mobile node and forwards it to the DHCP server.  The Relay Agent
>   (which is the NAS) also includes the received AAA AVP from the AAAH
>   in the OPTION_MIP6-RELAY-Option.
>  
>
>3.5.1  DHC Relay Agent Option to carry Mobile IPv6 parameters
>
Ok, so the basic solution is simply inserting the
discovered home agent information (if any) at the
relay so that the DHCP server can pick it up without
having to have an interface to AAA. This sounds good.
(Is there a reason why the relay can't add the answer
directly to the response?)

>   The transport of the assigned home agent information via the AAA
>   infrastructure (i.e., from the AAA server to the AAA client) to the
>  
>
Do we have existing, standard AAA attributes for the transport
of this information?

>   The communication between the NAS/DHCP relay agent to the DHCP server
>   must be authenticated, integrity and replay protected.  Deployments
>   MAY either rely on lower-layer security, (i.e., physical or link
>   layer security), or rely on security mechanisms specifically defined
>   for DHCPv6, such as [RELAY-IPSEC] or [RFC4030].
>  
>
I wasn't sure if the above means that e.g. dedicated physically
protected link is out of the question.

Anyway, I would recommend "SHOULD be authenticated ...
Deployments MAY rely on physical protection of the links
in question, or security mechanisms designed to protect
link layer, IP layer, or DHCP communications [...]".

Editorial:

>   in the mobile node's home MSP network. in order to provide the mobile
>
s/in/In/

--Jari


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



From mip6-bounces@ietf.org Fri Oct 21 11:29:51 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ESyq7-000676-61; Fri, 21 Oct 2005 11:29:51 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ESyq5-00065x-I4
	for mip6@megatron.ietf.org; Fri, 21 Oct 2005 11:29:49 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08827
	for <mip6@ietf.org>; Fri, 21 Oct 2005 11:29:37 -0400 (EDT)
Received: from yui.nc.u-tokyo.ac.jp ([130.69.251.116])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ESz2D-0000f7-3N
	for mip6@ietf.org; Fri, 21 Oct 2005 11:42:23 -0400
Received: from ryuji-no-powerbook-g4-15.local.sfc.wide.ad.jp
	(p3086-ipbf409marunouchi.tokyo.ocn.ne.jp [218.43.37.86])
	(authenticated bits=0)
	by yui.nc.u-tokyo.ac.jp (8.12.10/8.12.3/Debian-6.4) with ESMTP id
	j9LFTG64016056 for <mip6@ietf.org>; Sat, 22 Oct 2005 00:29:16 +0900
Date: Sat, 22 Oct 2005 00:29:10 +0900
Message-ID: <m28xwm6g8p.wl%ryuji@sfc.wide.ad.jp>
From: Ryuji Wakikawa <ryuji@sfc.wide.ad.jp>
To: mip6@ietf.org
User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.6
	(Marutamachi) APEL/10.6 Emacs/22.0.50
	(powerpc-apple-darwin8.1.0) MULE/5.0 (SAKAKI)
Organization: Keio University/WIDE
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
X-Spam-Score: 0.1 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Subject: [Mip6] comments to integrated DHC doc.
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org


Hello authors of the integrated-dhc document.

Thanks for this draft.
I quickly read the document and have a few questions.

I am confused about hninfo-type, what the difference between
hninfo-type zero and one.  The hinfo-type set to zero indicates "Home
subnet prefix" according to the draft-jang-dhc-haopt.  Can MN use the
128-bit address of reply which hninfo-type is zero as a home agent
address?  Or should MN start DHAAD or fall back to SPLIT?

BTW, what is the status of draft-jang-dhc-haopt?
It looks still individual draft.

In section 3.3, the draft said
   "In the fallback case, the mobile node is not able to acquire the home
   agent information via DHCPv6.  The mobile node performs DNS queries
   to discover the home agent address as defined in [BOOT-SPLIT].  To
   perform DNS based home agent discovery, the mobile node needs to know
   the DNS server address.  How the mobile node knows the DNS server
   address is outside the scope of this document."

Can we assume a DNS address can be provided by DHCPv6 server?  Do you
assume the case where there is no DHCP server here?  If DHCP server
exists and does not provide just home agent information, it can
provide DNS at least.

regards
ryuji


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



From mip6-bounces@ietf.org Fri Oct 21 11:34:47 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ESyut-00018x-PL; Fri, 21 Oct 2005 11:34:47 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ESyur-00018T-GC
	for mip6@megatron.ietf.org; Fri, 21 Oct 2005 11:34:45 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10579
	for <mip6@ietf.org>; Fri, 21 Oct 2005 11:34:34 -0400 (EDT)
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ESz70-0001Q4-U8
	for mip6@ietf.org; Fri, 21 Oct 2005 11:47:20 -0400
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id 64A2089884;
	Fri, 21 Oct 2005 18:34:34 +0300 (EEST)
Message-ID: <43590A97.7000004@kolumbus.fi>
Date: Fri, 21 Oct 2005 18:34:47 +0300
From: Jari Arkko <jari.arkko@kolumbus.fi>
User-Agent: Mozilla Thunderbird 1.0 (X11/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Mikko Hautala <mhautala@netlab.hut.fi>
Subject: Re: [Mip6] Question on return routability ?
References: <4358E0C4.7030307@netlab.hut.fi>
In-Reply-To: <4358E0C4.7030307@netlab.hut.fi>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Content-Transfer-Encoding: 7bit
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Mikko,

The worst case is that you need to run whole procedure for each
movement that changes your care-of address (there are also other
types of movements).

Then there are cases allowed by RFC 3775 where an old (prior
to movement) home test can be used after a movement.

Further optimizations are discussed in various drafts. E.g,
draft-arkko-mipshop-cba-cga discusses a method that reduces
the need to run home tests and makes care-of tests parallel
with actual data flow.

Hope this helps,

--Jari

Mikko Hautala wrote:

> Hi,
>
> I have a simple question on the return routability procedure of
> MIPv6 route optimization:
>
> Is the return routability procedure needed every time a MN conducts a
> MIPv6 handover ?
>
>
> I've been reading the MIPv6 RFC and the route optimization design 
> background, but
> I haven't been able to figure it out explicitly.
>
> I'm about 90% sure, that it is needed, because the care-of-address is 
> used when calculating MAC.
> Thus every time a MN moves, it must at least update the care-of token 
> with COTI/COT messages...
>
>
>
> Regards,
> Mikko Hautala
>
> _______________________________________________
> 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 Fri Oct 21 11:54:23 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ESzDr-0002kn-BI; Fri, 21 Oct 2005 11:54:23 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ESzDp-0002kc-UW
	for mip6@megatron.ietf.org; Fri, 21 Oct 2005 11:54:21 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA14619
	for <mip6@ietf.org>; Fri, 21 Oct 2005 11:54:10 -0400 (EDT)
Received: from dns1.tilab.com ([163.162.42.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ESzPz-0003Fv-0b
	for mip6@ietf.org; Fri, 21 Oct 2005 12:06:56 -0400
Received: from iowa2k01a.cselt.it ([163.162.242.201])
	by dns1.cselt.it (PMDF V6.0-025 #38895)
	with ESMTP id <0IOP00D58W5YCO@dns1.cselt.it> for mip6@ietf.org; Fri,
	21 Oct 2005 17:53:58 +0200 (MEST)
Received: from EXC01B.cselt.it ([163.162.4.199]) by iowa2k01a.cselt.it with
	Microsoft SMTPSVC(6.0.3790.211); Fri, 21 Oct 2005 17:53:58 +0200
Date: Fri, 21 Oct 2005 17:53:57 +0200
From: Gerardo Giaretta <Gerardo.Giaretta@TILAB.COM>
Subject: RE: [Mip6] comments to integrated DHC doc.
To: Ryuji Wakikawa <ryuji@sfc.wide.ad.jp>
Message-id: <DA62A6E0CDD1B34A84557FF1AC850C57016E9CB2@EXC01B.cselt.it>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.3790.326
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: quoted-printable
Importance: normal
Priority: normal
Thread-Topic: [Mip6] comments to integrated DHC doc.
thread-index: AcXWVzFd9YKVNcZXSsCbI2FtE8rmmgAAB/kA
Content-Class: urn:content-classes:message
X-OriginalArrivalTime: 21 Oct 2005 15:53:58.0078 (UTC)
	FILETIME=[A5B8D5E0:01C5D657]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135
Content-Transfer-Encoding: quoted-printable
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Hi Ryuji,=20

just one comment (I let the main authors to answers the others).

>=20
> Hello authors of the integrated-dhc document.
>=20
> Thanks for this draft.
> I quickly read the document and have a few questions.
>=20
> I am confused about hninfo-type, what the difference between
> hninfo-type zero and one.  The hinfo-type set to zero indicates "Home
> subnet prefix" according to the draft-jang-dhc-haopt.  Can MN use the
> 128-bit address of reply which hninfo-type is zero as a home agent
> address?  Or should MN start DHAAD or fall back to SPLIT?
>=20
> BTW, what is the status of draft-jang-dhc-haopt?
> It looks still individual draft.
>

there is still discussion in the DT if this draft can be a standalone
document or if it's better to merge it into integrated DHC draft.

Regards,
--Gerardo
=20
> In section 3.3, the draft said
>    "In the fallback case, the mobile node is not able to=20
> acquire the home
>    agent information via DHCPv6.  The mobile node performs DNS queries
>    to discover the home agent address as defined in [BOOT-SPLIT].  To
>    perform DNS based home agent discovery, the mobile node=20
> needs to know
>    the DNS server address.  How the mobile node knows the DNS server
>    address is outside the scope of this document."
>=20
> Can we assume a DNS address can be provided by DHCPv6 server?  Do you
> assume the case where there is no DHCP server here?  If DHCP server
> exists and does not provide just home agent information, it can
> provide DNS at least.
>=20
> regards
> ryuji
>=20
>=20
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
>=20


Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia =
S.p.A.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
CONFIDENTIALITY NOTICE
This message and its attachments are addressed solely to the persons
above and may contain confidential information. If you have received
the message in error, be informed that any use of the content hereof
is prohibited. Please return it immediately to the sender and delete
the message. Should you have any questions, please send an e_mail to=20
MailAdmin@tilab.com. Thank you
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

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



From mip6-bounces@ietf.org Fri Oct 21 12:37:39 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ESzti-00053U-Uu; Fri, 21 Oct 2005 12:37:38 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ESzth-00053K-Mh
	for mip6@megatron.ietf.org; Fri, 21 Oct 2005 12:37:37 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA17551
	for <mip6@ietf.org>; Fri, 21 Oct 2005 12:37:25 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ET05s-00050E-Bt
	for mip6@ietf.org; Fri, 21 Oct 2005 12:50:13 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id j9LGb1H23727; Fri, 21 Oct 2005 18:37:01 +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
	j9LGb1DJ059988; Fri, 21 Oct 2005 18:37:01 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200510211637.j9LGb1DJ059988@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Vijay Devarapalli <vijayd@iprg.nokia.com>
Subject: Re: [Mip6] comments about draft-ietf-mip6-ikev2-ipsec-03.txt 
In-reply-to: Your message of Fri, 21 Oct 2005 05:15:44 PDT.
	<4358DBF0.7040102@iprg.nokia.com> 
Date: Fri, 21 Oct 2005 18:37:01 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 995b2e24d23b953c94bac5288c432399
Cc: mip6@ietf.org, vijay.devarapalli@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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

=> I'll do a second pass ASAP...

   >    its optional because the binding updates have a sequence
   >    number which provides replay protection.
   >    
   > => no, this sequence number provides sequencing but no replay protection
   > as it can round up. I strongly disagree here: the IPsec anti-replay
   > protection is necessary and it was not made mandatory only because it
   > is not always possible. So I maintain my proposal.
   
   from what I remember, it was made optional because there is
   replay protection through BU sequence number. so I have to
   disagree. its a 32 bit sequence number. takes a long time
   to wrap around.
   
=> two messages... not so a long time! The BU sequence number is *not*
an anti-replay feature at all. Please trust me.
   
   >    >  In 5 page 8:
   >    > 
   >    >    This section describes the SPD and SAD entries that can be used to
   >    > 
   >    > => I propose to add something explaining here and in section 6 that
   >    > the care-of address is the primary care-of address. BTW this is required
   >    > from time to time and it makes the code for tracking and updating SPD/SAD
   >    > far easier to write.
   >    
   >    I dont think I understand. are you saying the MN should
   >    use its primary CoA and not any CoA?
   > 
   > => yes, IMHO the level for using the primary CoA in place of any CoA
   > is in some cases MUST and in all cases at least a SHOULD. The RFC 3775
   > is a bit lax about this (it uses "the CoA" for instance) but here I propose
   > to be clear.
   > 
   >    what if the monami6
   >    WG extends MIPv6 registrations to include multiple CoAs?
   > 
   > => this will be the job of the monami6 WG to produce the proper guidelines.
   > 
   >    I would like to support that with just one SA.
   >    
   > => I agree (I even suggested this with the multiple MR document as you'll
   > be able to see when it will be published :-).
   
   I prefer the looser text so that others can extend it to
   support multiple CoAs. otherwise monami6 WG has to
   specifically say "RFC 3775 says blah blah.. but.. but we
   have to relax the blah blah.. requirement".
   
=> to mess the any CoA/primary CoA issue won't help monami6 WG at all:
this can change the choice between the primary CoA and the extra CoA
in a choice between a CoA in the whole set of possible CoA, so anything
based on addresses will fail from time to time.
I insist!

   >    >  In 5.4 page 11 I can't see a trace of the protocol=MH option...
   >    
   >    5.4 is about payload traffic. that means protocol = 'any'.
   >    
   > => so perhaps we should add a subsection here to explain how to do
   > the protocol=MH option (which is easier than the "any" because it is
   > not equivalent to a transport mode applied to a tunnel). Note I have
   > the same concern about 6.1.4 (where currently proto = X ?! :-).
   
   I made a mistake in my earlier mail. it shouldnt have been 'any'.
   it should have been 'X', which 'X' stands for a particular
   protocol. perhaps thats enough?
   
=> no, X and 'any' are not equivalent. And here the selection must include
the HoT/HoTI MH type (so proto must include MH, i.e., X=MH or 'any').

   how about
   
       The TSi and
       TSr payloads in the above examples will contain many other selectors
       apart from home_address_1.  For the sake of brevity, we show only
       those values that relevant for Mobile IPv6.
   
=> good (so the idea is now cleary that unbounded sharing is allowed).

   > IMHO this is correct as it is fully equivalent but:
   >  - SPD-S entries are symmetrical so there is only one for MN and one for the HA
   >  - proto is any, not X
   >  - the second SPD-S entry for the MN should have the same layout than others
   >    (in fact it is the same than the first one as it should be only one entry)
   >  - s/coa/.../ as usual
   >  - we can say one can use a transport mode over the tunnel as it will give
   >    exactly the same layout for packets and the same selection (proto = any
   >    in tunnel mode for inner protocol, proto = 41 in transport mode for outer
   >    protocol).
   
   how about the following?
   
           mobile node SPD-S:
             - IF interface = IPv6 tunnel to home_agent_1 & proto = X
               Then use SA ESP tunnel mode
                               IDi = user_1, IDr = home_agent_1,
                               TSi = home_address_1, X, port
                               TSr = any, X, port
                               outer src addr = coa
                               outer dst addr = home_agent_1,
                               inner src addr = home_address_1
   
           home agent SPD-S:
             - IF interface = IPv6 tunnel to home_address_1 & proto = X
               Then use SA ESP tunnel mode
                               IDi = home_agent_1, IDr = user_1,
                               TSi = any, X, port
                               TSr = home_address_1, X, port
                               outer src addr = home_agent_1,
                               outer dst addr = coa,
                               inner dst addr = home_address_1
   
=> better. I still don't understand the X, prefer expanded coa abbrev
and have a proposal for the transport mode over tunnel.

   >    why is it a bad idea? without that we cant enforce a policy where
   >    we want the HA to send a BAck, but not a BU.
   >    
   > => you missed the discussion about the selectors for MH:
   > remote_mh_type=BAck on the MN means the HA can only send BAck.
   
   hmm... I followed the discussion on the IPsec mailing list.
   it seemed like not everybody agreed.
   
=> there was no real objection but I agree this interpretation is not
yet in the documents (but here I believe we can forward without waiting
for a new 2401bis).
About the one SA pair, IMHO the main benefit of the fine grain selectors
is they make possible to put the IKE daemon on the HA is the "passive"
mode, i.e., it is never an initiator. This was not true (and is still not
true with coarse grain selectors) before because of the MN-MN case.

   >    >    After the IKE_AUTH exchange completes, the mobile node initiates
   >    >    CREATE_CHILD_SA exchanges to negotiate additional security
   >    >    associations for protecting Return Routability signaling, Mobile
   >    >    Prefix Discovery messages and optionally payload traffic.
   >    > 
   >    > => I propose:
   >    > 
   >    >    After the IKE_AUTH exchange completes, the mobile node initiates
   >    >    CREATE_CHILD_SA exchanges to negotiate additional security
   >    >    associations for protecting Return Routability signaling or
   >    >    optionally payload traffic, and Mobile Prefix Discovery messages.
   >    
   >    whats the difference?
   >    
   > => X and Y and Z != (X or Z) and Y...
   > RR (X) and payload (Z) are alternatives.
   
   the current requirements say the MN must create security
   associations to protect RR and MPD messages. payload is
   optional. this assumes the payload does not include
   RR messages.
   
=> argh! I can see where we disagree: I assume than payload means
all payloads. I have not the time now but we should get the original
text to see who is right... Of course the other TSx stuff applies here.

   > => IMHO this discussion is not at the right place: it is not a MIPv6
   > issue but an IPsec issue. So my concern is we should restrict ourselves
   > to the current IKEv2/2401bis and not rely on still in discussion extensions.
   
   lets see what the IESG says about this.
   
=> a dangerous way to solve our problems... (:-).

Thanks

Francis.Dupont@enst-bretagne.fr


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



From mip6-bounces@ietf.org Fri Oct 21 12:42:37 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ESzyX-0006vb-ED; Fri, 21 Oct 2005 12:42:37 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ESzyU-0006tc-9X
	for mip6@megatron.ietf.org; Fri, 21 Oct 2005 12:42:34 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA17833
	for <mip6@ietf.org>; Fri, 21 Oct 2005 12:42:22 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ET0Ae-0005DI-5O
	for mip6@ietf.org; Fri, 21 Oct 2005 12:55:09 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id j9LGfQH24365; Fri, 21 Oct 2005 18:41:26 +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
	j9LGfQw3060089; Fri, 21 Oct 2005 18:41:26 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200510211641.j9LGfQw3060089@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Mikko Hautala <mhautala@netlab.hut.fi>
Subject: Re: [Mip6] Question on return routability ? 
In-reply-to: Your message of Fri, 21 Oct 2005 15:36:20 +0300.
	<4358E0C4.7030307@netlab.hut.fi> 
Date: Fri, 21 Oct 2005 18:41:26 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   I have a simple question on the return routability procedure of
   MIPv6 route optimization:
   
   Is the return routability procedure needed every time a MN conducts a
   MIPv6 handover ?
   
=> yes, the care-of address check doesn't work for a new address so
something (else than sending a BU) has to be done each time.
   
   I'm about 90% sure, that it is needed, because the care-of-address is 
   used when calculating MAC.
   Thus every time a MN moves, it must at least update the care-of token 
   with COTI/COT messages...
   
=> good hint!

Francis.Dupont@enst-bretagne.fr

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



From mip6-bounces@ietf.org Fri Oct 21 12:59:38 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ET0F0-00017p-3A; Fri, 21 Oct 2005 12:59:38 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ET0Et-00017k-Co
	for mip6@megatron.ietf.org; Fri, 21 Oct 2005 12:59:31 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18679
	for <mip6@ietf.org>; Fri, 21 Oct 2005 12:59:19 -0400 (EDT)
Received: from mail.flarion.com ([63.103.94.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ET0R3-0005oU-EW
	for mip6@ietf.org; Fri, 21 Oct 2005 13:12:06 -0400
Received: from ftmailserver.flariontech.com ([10.10.1.140]) by
	mail.flarion.com with Microsoft SMTPSVC(5.0.2195.6713);
	Fri, 21 Oct 2005 12:59:20 -0400
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
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] comments about draft-ietf-mip6-ikev2-ipsec-03.txt 
Date: Fri, 21 Oct 2005 12:59:20 -0400
Message-ID: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCD83@ftmailserver.flariontech.com>
Thread-Topic: [Mip6] comments about draft-ietf-mip6-ikev2-ipsec-03.txt 
Thread-Index: AcXWX1Ry/83YWua8SFSjHYSjcan16gAASrog
From: "Soliman, Hesham" <H.Soliman@flarion.com>
To: "Francis Dupont" <Francis.Dupont@enst-bretagne.fr>,
	"Vijay Devarapalli" <vijayd@iprg.nokia.com>
X-OriginalArrivalTime: 21 Oct 2005 16:59:20.0133 (UTC)
	FILETIME=[C772EF50:01C5D660]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f0b5a4216bfa030ed8a6f68d1833f8ae
Content-Transfer-Encoding: quoted-printable
Cc: mip6@ietf.org, vijay.devarapalli@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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org



 >    from what I remember, it was made optional because there is
 >    replay protection through BU sequence number. so I have to
 >    disagree. its a 32 bit sequence number. takes a long time
 >    to wrap around.
 >   =20
 > =3D> two messages... not so a long time! The BU sequence=20
 > number is *not*
 > an anti-replay feature at all. Please trust me.

=3D> FWIW, that's correct. The seq no in the BU was never intended
to be an anti-replay protection mechanism. All it does is set
an acceptable window for the next BU. It's used to ensure=20
"ordering" of packets.=20

Hesham


 >   =20
 >    >    >  In 5 page 8:
 >    >    >=20
 >    >    >    This section describes the SPD and SAD entries=20
 > that can be used to
 >    >    >=20
 >    >    > =3D> I propose to add something explaining here and=20
 > in section 6 that
 >    >    > the care-of address is the primary care-of=20
 > address. BTW this is required
 >    >    > from time to time and it makes the code for=20
 > tracking and updating SPD/SAD
 >    >    > far easier to write.
 >    >   =20
 >    >    I dont think I understand. are you saying the MN should
 >    >    use its primary CoA and not any CoA?
 >    >=20
 >    > =3D> yes, IMHO the level for using the primary CoA in=20
 > place of any CoA
 >    > is in some cases MUST and in all cases at least a=20
 > SHOULD. The RFC 3775
 >    > is a bit lax about this (it uses "the CoA" for=20
 > instance) but here I propose
 >    > to be clear.
 >    >=20
 >    >    what if the monami6
 >    >    WG extends MIPv6 registrations to include multiple CoAs?
 >    >=20
 >    > =3D> this will be the job of the monami6 WG to produce=20
 > the proper guidelines.
 >    >=20
 >    >    I would like to support that with just one SA.
 >    >   =20
 >    > =3D> I agree (I even suggested this with the multiple MR=20
 > document as you'll
 >    > be able to see when it will be published :-).
 >   =20
 >    I prefer the looser text so that others can extend it to
 >    support multiple CoAs. otherwise monami6 WG has to
 >    specifically say "RFC 3775 says blah blah.. but.. but we
 >    have to relax the blah blah.. requirement".
 >   =20
 > =3D> to mess the any CoA/primary CoA issue won't help monami6=20
 > WG at all:
 > this can change the choice between the primary CoA and the extra CoA
 > in a choice between a CoA in the whole set of possible CoA,=20
 > so anything
 > based on addresses will fail from time to time.
 > I insist!
 >=20
 >    >    >  In 5.4 page 11 I can't see a trace of the=20
 > protocol=3DMH option...
 >    >   =20
 >    >    5.4 is about payload traffic. that means protocol =3D 'any'.
 >    >   =20
 >    > =3D> so perhaps we should add a subsection here to=20
 > explain how to do
 >    > the protocol=3DMH option (which is easier than the "any"=20
 > because it is
 >    > not equivalent to a transport mode applied to a=20
 > tunnel). Note I have
 >    > the same concern about 6.1.4 (where currently proto =3D X ?! =
:-).
 >   =20
 >    I made a mistake in my earlier mail. it shouldnt have been 'any'.
 >    it should have been 'X', which 'X' stands for a particular
 >    protocol. perhaps thats enough?
 >   =20
 > =3D> no, X and 'any' are not equivalent. And here the=20
 > selection must include
 > the HoT/HoTI MH type (so proto must include MH, i.e., X=3DMH or =
'any').
 >=20
 >    how about
 >   =20
 >        The TSi and
 >        TSr payloads in the above examples will contain many=20
 > other selectors
 >        apart from home_address_1.  For the sake of brevity,=20
 > we show only
 >        those values that relevant for Mobile IPv6.
 >   =20
 > =3D> good (so the idea is now cleary that unbounded sharing is=20
 > allowed).
 >=20
 >    > IMHO this is correct as it is fully equivalent but:
 >    >  - SPD-S entries are symmetrical so there is only one=20
 > for MN and one for the HA
 >    >  - proto is any, not X
 >    >  - the second SPD-S entry for the MN should have the=20
 > same layout than others
 >    >    (in fact it is the same than the first one as it=20
 > should be only one entry)
 >    >  - s/coa/.../ as usual
 >    >  - we can say one can use a transport mode over the=20
 > tunnel as it will give
 >    >    exactly the same layout for packets and the same=20
 > selection (proto =3D any
 >    >    in tunnel mode for inner protocol, proto =3D 41 in=20
 > transport mode for outer
 >    >    protocol).
 >   =20
 >    how about the following?
 >   =20
 >            mobile node SPD-S:
 >              - IF interface =3D IPv6 tunnel to home_agent_1 & proto =
=3D X
 >                Then use SA ESP tunnel mode
 >                                IDi =3D user_1, IDr =3D home_agent_1,
 >                                TSi =3D home_address_1, X, port
 >                                TSr =3D any, X, port
 >                                outer src addr =3D coa
 >                                outer dst addr =3D home_agent_1,
 >                                inner src addr =3D home_address_1
 >   =20
 >            home agent SPD-S:
 >              - IF interface =3D IPv6 tunnel to home_address_1=20
 > & proto =3D X
 >                Then use SA ESP tunnel mode
 >                                IDi =3D home_agent_1, IDr =3D user_1,
 >                                TSi =3D any, X, port
 >                                TSr =3D home_address_1, X, port
 >                                outer src addr =3D home_agent_1,
 >                                outer dst addr =3D coa,
 >                                inner dst addr =3D home_address_1
 >   =20
 > =3D> better. I still don't understand the X, prefer expanded coa =
abbrev
 > and have a proposal for the transport mode over tunnel.
 >=20
 >    >    why is it a bad idea? without that we cant enforce a=20
 > policy where
 >    >    we want the HA to send a BAck, but not a BU.
 >    >   =20
 >    > =3D> you missed the discussion about the selectors for MH:
 >    > remote_mh_type=3DBAck on the MN means the HA can only send BAck.
 >   =20
 >    hmm... I followed the discussion on the IPsec mailing list.
 >    it seemed like not everybody agreed.
 >   =20
 > =3D> there was no real objection but I agree this interpretation is =
not
 > yet in the documents (but here I believe we can forward=20
 > without waiting
 > for a new 2401bis).
 > About the one SA pair, IMHO the main benefit of the fine=20
 > grain selectors
 > is they make possible to put the IKE daemon on the HA is the=20
 > "passive"
 > mode, i.e., it is never an initiator. This was not true (and=20
 > is still not
 > true with coarse grain selectors) before because of the MN-MN case.
 >=20
 >    >    >    After the IKE_AUTH exchange completes, the=20
 > mobile node initiates
 >    >    >    CREATE_CHILD_SA exchanges to negotiate=20
 > additional security
 >    >    >    associations for protecting Return Routability=20
 > signaling, Mobile
 >    >    >    Prefix Discovery messages and optionally=20
 > payload traffic.
 >    >    >=20
 >    >    > =3D> I propose:
 >    >    >=20
 >    >    >    After the IKE_AUTH exchange completes, the=20
 > mobile node initiates
 >    >    >    CREATE_CHILD_SA exchanges to negotiate=20
 > additional security
 >    >    >    associations for protecting Return Routability=20
 > signaling or
 >    >    >    optionally payload traffic, and Mobile Prefix=20
 > Discovery messages.
 >    >   =20
 >    >    whats the difference?
 >    >   =20
 >    > =3D> X and Y and Z !=3D (X or Z) and Y...
 >    > RR (X) and payload (Z) are alternatives.
 >   =20
 >    the current requirements say the MN must create security
 >    associations to protect RR and MPD messages. payload is
 >    optional. this assumes the payload does not include
 >    RR messages.
 >   =20
 > =3D> argh! I can see where we disagree: I assume than payload means
 > all payloads. I have not the time now but we should get the original
 > text to see who is right... Of course the other TSx stuff=20
 > applies here.
 >=20
 >    > =3D> IMHO this discussion is not at the right place: it=20
 > is not a MIPv6
 >    > issue but an IPsec issue. So my concern is we should=20
 > restrict ourselves
 >    > to the current IKEv2/2401bis and not rely on still in=20
 > discussion extensions.
 >   =20
 >    lets see what the IESG says about this.
 >   =20
 > =3D> a dangerous way to solve our problems... (:-).
 >=20
 > Thanks
 >=20
 > Francis.Dupont@enst-bretagne.fr
 >=20
 >=20
 > _______________________________________________
 > Mip6 mailing list
 > Mip6@ietf.org
 > https://www1.ietf.org/mailman/listinfo/mip6
 >=20

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D
This email may contain confidential and privileged material for the sole =
use
 of the intended recipient.  Any review or distribution by others is =
strictly
 prohibited.  If you are not the intended recipient please contact the =
sender
 and delete all copies.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D


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



From mip6-bounces@ietf.org Fri Oct 21 18:50:22 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ET5iQ-0007WS-6X; Fri, 21 Oct 2005 18:50:22 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ET5i7-0007K0-Ls; Fri, 21 Oct 2005 18:50:03 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA23223;
	Fri, 21 Oct 2005 18:49:51 -0400 (EDT)
Received: from [132.151.6.50] (helo=newodin.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1ET5uL-0001DR-0Y; Fri, 21 Oct 2005 19:02:41 -0400
Received: from mlee by newodin.ietf.org with local (Exim 4.43)
	id 1ET5i5-0004vB-SR; Fri, 21 Oct 2005 18:50:01 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1ET5i5-0004vB-SR@newodin.ietf.org>
Date: Fri, 21 Oct 2005 18:50:01 -0400
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43
Cc: mip6@ietf.org
Subject: [Mip6] I-D ACTION:draft-ietf-mip6-bootstrapping-split-01.txt 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

--NextPart

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

	Title		: Mobile IPv6 bootstrapping in split scenario
	Author(s)	: G. Giaretta, et al.
	Filename	: draft-ietf-mip6-bootstrapping-split-01.txt
	Pages		: 33
	Date		: 2005-10-21
	
A Mobile IPv6 node requires a Home Agent address, a home address, 
and IPsec security associations with its Home Agent before it can 
start utilizing Mobile IPv6 service. RFC 3775 requires that some 
or all of these are statically configured. This document defines 
how a Mobile IPv6 node can bootstrap this information from non-
topological information and security credentials preconfigured on 
the Mobile Node. The solution defined in this document solves the 
bootstrapping problem from draft-ietf-mip6-bootstrapping-ps-02 
when the Mobile Node's mobility service is authorized by a 
different service provider than basic network access, and is 
therefore generically applicable to any bootstrapping case.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mip6-bootstrapping-split-01.txt

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


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

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


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

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-mip6-bootstrapping-split-01.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

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

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

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

ENCODING mime
FILE /internet-drafts/draft-ietf-mip6-bootstrapping-split-01.txt

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

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


--OtherAccess--

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

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

--NextPart--




From mip6-bounces@ietf.org Sat Oct 22 04:51:50 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ETF6T-00086Y-LK; Sat, 22 Oct 2005 04:51:49 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ETF6R-00086K-66; Sat, 22 Oct 2005 04:51:47 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA27174;
	Sat, 22 Oct 2005 04:51:35 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1ETFIk-0006Uz-Qy; Sat, 22 Oct 2005 05:04:31 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id j9M8pMH27749; Sat, 22 Oct 2005 10:51:22 +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
	j9M8pL5j064210; Sat, 22 Oct 2005 10:51:21 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200510220851.j9M8pL5j064210@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Christian Vogt <chvogt@tm.uka.de>
In-reply-to: Your message of Wed, 19 Oct 2005 15:41:53 +0200.
	<43564D21.4000408@tm.uka.de> 
Date: Sat, 22 Oct 2005 10:51:21 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: Jari Arkko <jari.arkko@kolumbus.fi>, mipshop@ietf.org,
	Gregory Daley <greg.daley@eng.monash.edu.au>, mip6@ietf.org
Subject: [Mip6] Re: [Mipshop] larger options 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

=> this issue was solved by adopting the concatenation idea:
   
   > o    The truly long options are rare, there's likely just one (cga). 
   > Having a rule in the spec that needs this to concatenate the option
   > in question if it appears multiple times would be possible. That is,
   > you add, say, four options to carry the lengthy data: 
   > optionX(...)optionX(...)optionX(...)optionX(...)
   > 
   > --Jari
   
I can't see a good reason to reopen the issue as the solution works
and needs no new document.

Regards

Francis.Dupont@enst-bretagne.fr

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



From mip6-bounces@ietf.org Sat Oct 22 06:14:13 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ETGOC-0008SB-Eu; Sat, 22 Oct 2005 06:14:12 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ETGOA-0008Mb-IY
	for mip6@megatron.ietf.org; Sat, 22 Oct 2005 06:14:10 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA00809
	for <mip6@ietf.org>; Sat, 22 Oct 2005 06:13:58 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ETGaU-0000j4-NZ
	for mip6@ietf.org; Sat, 22 Oct 2005 06:26:55 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id j9MADiH02267; Sat, 22 Oct 2005 12:13:44 +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
	j9MADilC064652; Sat, 22 Oct 2005 12:13:44 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200510221013.j9MADilC064652@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Vijay Devarapalli <vijayd@iprg.nokia.com>
Subject: Re: [Mip6] comments about draft-ietf-mip6-ikev2-ipsec-03.txt 
In-reply-to: Your message of Fri, 21 Oct 2005 05:15:44 PDT.
	<4358DBF0.7040102@iprg.nokia.com> 
Date: Sat, 22 Oct 2005 12:13:44 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87
Cc: mip6@ietf.org, vijay.devarapalli@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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   >    > => I believe the document should restrict choices to only three options:
   >    >  - fine granularity: selector on MH types
   >    >  - medium granularity/RFC 3776 compatibility: selector on protocol = MH
   >    >  - coarse granularity: any protocol (here).
   >    
   >    ok. but did you want to see some text. or?
   >    
   > => yes, I believe it is important to have some text because readers
   > should both understand they have some choices (note some are needed
   > for compatibility with current implementations, for instance coarse
   > grain only selectors for forwarded traffic) but not too many (i.e.,
   > we recommend a subset of possible profiles).
   
   can you suggest some text here?
   
=> as the issue is a bit complex and is related to 5.4 and 6.1.4 I'll try
to propose a complete text in another message.

   >    >  In 5.4 page 11 I can't see a trace of the protocol=MH option...
   >    
   >    5.4 is about payload traffic. that means protocol = 'any'.
   >    
   > => so perhaps we should add a subsection here to explain how to do
   > the protocol=MH option (which is easier than the "any" because it is
   > not equivalent to a transport mode applied to a tunnel). Note I have
   > the same concern about 6.1.4 (where currently proto = X ?! :-).
   
   I made a mistake in my earlier mail. it shouldnt have been 'any'.
   it should have been 'X', which 'X' stands for a particular
   protocol. perhaps thats enough?
   
=> the word any was overloaded in RFC 3776 section 3.4, in fact there are
3 cases:
 - X is really an any protocol
 - X is MH
 - X stands for all protocols (i.e., 'any')
This has to be solved in the introduction as the DB entries look similar.

   >    >    After the IKE_AUTH exchange completes, the mobile node initiates
   >    >    CREATE_CHILD_SA exchanges to negotiate additional security
   >    >    associations for protecting Return Routability signaling, Mobile
   >    >    Prefix Discovery messages and optionally payload traffic.

=> I withdraw my proposal.

   >    >  In 6.3 page 18:
   >    > 
   >    >    ... on the mobile node
   >    >    when it receives the Binding acknowledgement sent by the home agent.
   >    > 
   >    > => I discussed this with Shinta-san and the endpoint update is performed
   >    > by the mobile node after it sends the BU, i.e., the MN doesn't wait for
   >    > the BA. Cf draft-sugimoto-mip6-pfkey-migrate-01.txt 4.1.2 page 7.
   >    
   >    I dont mind making the change, but do you think the mobile node
   >    can start using the new CoA for tunneled packets before it is
   >    sure the BU has been processed by the HA?
   >    
   > => usually it can't use the old CoA... and we can be optimistic.
   > Note the HA should not check the outer source address (cf RFC 2401(bis))
   > so if the BU fails the issue will be for returned traffic (CN->HA->MN).
   
   I went back and looked at the text. it talks about the IKE SA.
   data traffic wont be sent over the IKE SA. I guess there is
   no urgent need to update the IKE SA?
   
=> The discussion with Shinta-san was about the SPD and SAD update
but the IKE SA can be updated in fact at the same time. The only
thing to wait for the BAck gives is the K flag from the HA so
if the MN but not the HA support the K stuff the IKE SA is not
updated then reestablished... IMHO this doesn't matter and we
have clearly a case of overspecification. I can see two ways
to solve this:
 - remove the "and on the mobile node"
 - add in the "and on the mobile node" the alternative.
I believe the second is a bit better so the text should be:

   If the mobile node moves and its care-of address changes, the IKEv2
   SA might not be valid, unless the mobility extensions defined in [13]
   are implemented by both the mobile node and the home agent.  RFC 3775
   defines a mechanism based on the successful exchange of Binding
   Update and Binding Acknowledgement messages.  The IKE SA endpoints
   are updated on the home agent when it receives the Binding Update
   from the mobile node's new care-of address and on the mobile node
   when it sends the Binding Update to the home agent or when it receives
   the Binding Acknowledgement sent by the home agent.
   This capability to change IKE endpoints is indicated through setting
   the Key Management Capability (K) flag [2] in the Binding Update and
   Binding Acknowledgement messages.  If the mobile node or the home
   agent does not support this capability, then an IKEv2 exchange MUST
   be initiated to re-establish the IKE SA.

(PS: note the uppercase in Acknowledgement)

Thanks

Francis.Dupont@enst-bretagne.fr

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



From mip6-bounces@ietf.org Sat Oct 22 08:16:31 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ETIIZ-0007Y6-3k; Sat, 22 Oct 2005 08:16:31 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ETIIV-0007ST-SF
	for mip6@megatron.ietf.org; Sat, 22 Oct 2005 08:16:27 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA05873
	for <mip6@ietf.org>; Sat, 22 Oct 2005 08:16:17 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ETIUr-0004X7-7h
	for mip6@ietf.org; Sat, 22 Oct 2005 08:29:13 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id j9MCG6H10308; Sat, 22 Oct 2005 14:16:06 +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
	j9MCG6fq064949; Sat, 22 Oct 2005 14:16:06 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200510221216.j9MCG6fq064949@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Vijay Devarapalli <vijayd@iprg.nokia.com>
Date: Sat, 22 Oct 2005 14:16:06 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac
Cc: mip6@ietf.org
Subject: [Mip6] granularity and draft-ietf-mip6-ikev2-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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

I propose to insert this section at the end of 4 (Requirements) before
5 (Manual Configuration) even the only thing which is required is to
have compatible policies on the MN and the HA.
Of course the wording can (should! :-) be improved... and someone
can have a good proposal for the last issue (but please don't open
a can of worms, it doesn't really matter if the IPv6 tunnel is a
(very) virtual interface as payload protection is (very :-) optional).
Another point: I don't know if we have to mention that the HoT[I] selectors
make possible to put the HA IKE in "passive mode", i.e., the HA is never
the initiator (good for IKE, bad for the MN-MN case :-).

Thanks

Francis.Dupont@enst-bretagne.fr

<section title="Selector Granularity Considerations">
<t>
IPsec implementations are not required to support fine grain selectors.
More, applying fine grain selectors on forwarded packets is known to
raise specific problems when some involved fields are not present in
initial fragments, so some implementators may choose to support only
coarse grain selectors (i.e., addresses and in some case protocol) for
forwarded traffic. As finer grain selectors give a better control,
i.e., the protection is only applied when required, the examples in
the document always use the finest granularity.
</t>
<t>
The protection of Binding Updates and Acknowledgement and the protection
of Mobile Prefix Discovery Messages are in transport mode where fine
grain selectors are likely supported.
</t>
<t>
But the protection of Return Routability Messages and the protection of
the Payload Packets are in tunnel mode where fine grain selectors can be
unavailable. In any case the mobile node and the home agent MUST use
compatible policies.
</t>
<t>
The choice is between three profiles:
<list style="symbols">
<t> 
Finest grain selectors, including Mobility Header message type, are available.
This is the case assumed in the examples of the document.
<vspace blankLines="1"/></t>
<t>
The finest grain selector which is available is the protocol selector.
The protection of Return Routability Messages uses a setup similar
to the Payload Packets with the protocol selector set to Mobility Header
messages.
<vspace blankLines="1"/></t>
<t>
The last case is where the protocol selector is not available or for
privacy considerations the whole traffic tunneled between the mobile node
and the home agent is protected. The setup is the same than for
the Payload Packets with the protocol selector set to 'any'.
</t>
</list>
<t>
The last case (protection of all tunneled packets) introduces two new
difficulties:
<list style="symbols">
<t>
This protection can cover the Return Routability Messages so either there is
no specific IPsec database entries for the Return Routability Messages and
the protection for all tunneled packets MUST fulfill the requirements for
the Return Routability Messages, or there are some specific SPD entries
for the protection of the Return Routability Messages with a higher
priority.
<vspace blankLines="1"/></t>
<t>
The standard setup gives the same packet layout and applies to the same
traffic than a transport mode applied to the IPv6-in-IPv6 tunnel.
This document does not try to solve this issue, i.e., it only signals it.
</t>
</list>
</t>
</section>

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



From mip6-bounces@ietf.org Sat Oct 22 12:09:47 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ETLwI-0005WZ-8y; Sat, 22 Oct 2005 12:09:46 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ETLwG-0005Vk-3S
	for mip6@megatron.ietf.org; Sat, 22 Oct 2005 12:09:44 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18231
	for <mip6@ietf.org>; Sat, 22 Oct 2005 12:09:32 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ETM8c-0004Ca-EY
	for mip6@ietf.org; Sat, 22 Oct 2005 12:22:31 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id j9MG9Ef26582; Sat, 22 Oct 2005 18:09: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
	j9MG9Fro065744; Sat, 22 Oct 2005 18:09:15 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200510221609.j9MG9Fro065744@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Vijay Devarapalli <vijayd@iprg.nokia.com>,
	Mohan Parthasarathy <mohan.parthasarathy@nokia.com>
Date: Sat, 22 Oct 2005 18:09:15 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Cc: mip6@ietf.org
Subject: [Mip6] concerns about draft-devarapalli-mip6-ikev1-bootstrap-00.txt
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

I maintain my previous concerns about MODECFG and XAUTH. Now I've read
the whole document and I have some other concerns:
 - there are some normative references to documents which timed out
   many years ago
 - there should be security considerations about the well known
   essential insecurity of XAUTH (*)
 - I am not convinced DHCPv6 can be used over IKE as described:
   DHCPv6 is designed to run between the client and the first relay/server
   over a link using multicast and link-local addresses. So it runs without
   problem over L2TP/PPP between a client and a NAS. Here we have a tunnel
   mode IPsec which is pretty different than a real tunnel interface.
So sections 3.1, 3.2 (HoA config) and 4 (SA setup) are at least questionable.
The remaining spec is the section 5 (DNS update) which is already in
a bootstrapping document... So I am sorry but IMHO there is nothing
really useful today in the document.

Regards

Francis.Dupont@enst-bretagne.fr

(*): If someone knows Jose Puthenkulam, ask him to refresh its I-D.

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



From mip6-bounces@ietf.org Sun Oct 23 05:36:51 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ETcHb-0004zP-4o; Sun, 23 Oct 2005 05:36:51 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ETcHY-0004zK-Vi
	for mip6@megatron.ietf.org; Sun, 23 Oct 2005 05:36:49 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA24767
	for <mip6@ietf.org>; Sun, 23 Oct 2005 05:36:36 -0400 (EDT)
Received: from xproxy.gmail.com ([66.249.82.206])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ETcU4-0003Mj-MP
	for mip6@ietf.org; Sun, 23 Oct 2005 05:49:45 -0400
Received: by xproxy.gmail.com with SMTP id r21so114271wxc
	for <mip6@ietf.org>; Sun, 23 Oct 2005 02:36:46 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
	b=QFKzqhOzPKOAyDlgDTcJHezCu0K/mUWAMfEXC/7TtPrR48UBbpNcfveOdfUF0796nvCd65mIA4mJLWbMdobEixSdRDXKrAon+O40uGDoa8AAFlMKRrTB92jPtMbITiZ8KqkHun3VCYrWa+EA++ze35IzhXyxInIQt4nXHO9/UAQ=
Received: by 10.70.67.13 with SMTP id p13mr2864245wxa;
	Sun, 23 Oct 2005 02:36:46 -0700 (PDT)
Received: by 10.70.66.17 with HTTP; Sun, 23 Oct 2005 02:36:46 -0700 (PDT)
Message-ID: <36cb7a210510230236o73cf33c9oe86829278ca42b70@mail.gmail.com>
Date: Sun, 23 Oct 2005 19:36:46 +1000
From: Henrik Petander <henrik.petander@gmail.com>
To: mip6@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Content-Transfer-Encoding: quoted-printable
Subject: [Mip6] New draft on make-before-break handoffs in Mobile IPv6
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: henrik.petander@iki.fi
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Hi all,

We have written an internet draft on make-before-break handoffs in
Mobile IPv6. The draft proposes improvements to Mobile IPv6 binding
management for make-before-break handoffs to avoid packet loss during hando=
ffs.
The draft is available at the ietf website:

http://www.ietf.org/internet-drafts/draft-petander-mip6-mbb-00.txt


Abstract:

"Mobile IPv6 binding management has been designed for
break-before-make handoffs, which can be performed by hosts equipped
with a single interface. However, a mobile node may be equipped with
multiple interfaces, allowing it to perform make-before-break handoffs
by connecting simultaneously to two overlapping access networks during
the handoff. In theory these handoffs can be lossless, provided that
there is sufficient overlap between the two networks. However, unless
Mobile IPv6 bindings are managed carefully mobile node and
correspondent node will have inconsistent binding state during the
handoff, which will lead to packet loss. In this draft we propose
changes to binding management for lossless make-before-break handoffs.
The proposed changes do not affect the interoperability with Mobile
IPv6 nodes not implementing these changes."

For background information: We measured the performance of Mobile IPv6
in make-before-break handoffs with two interfaces and noticed bad
performance when there was network latency between MN and HA.  Packets
sent between BU and BA were dropped either by HA or MN, depending on
whether handoff in MN was performed when sending BU or receiving BA.
We implemented the MN part of the draft and verified that the proposed
change fixed the problem and allowed lossless handoffs for MIPv6, so
the modifications to MIPv6  work also in practice.

Regards,
Henrik Petander

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



From mip6-bounces@ietf.org Sun Oct 23 23:53:14 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ETtOc-0001PW-5m; Sun, 23 Oct 2005 23:53:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ETtOa-0001PD-7g
	for mip6@megatron.ietf.org; Sun, 23 Oct 2005 23:53:12 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA11018
	for <mip6@ietf.org>; Sun, 23 Oct 2005 23:52:59 -0400 (EDT)
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ETtbF-0001kE-Cb
	for mip6@ietf.org; Mon, 24 Oct 2005 00:06:18 -0400
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id j9O3K1904714;
	Sun, 23 Oct 2005 20:20:01 -0700
X-mProtect: <200510240320> Nokia Silicon Valley Messaging Protection
Received: from da-niradhcp16563.americas.nokia.com (10.241.165.63,
	claiming to be "[127.0.0.1]")
	by darkstar.iprg.nokia.com smtpdIvLqfh; Sun, 23 Oct 2005 20:20:00 PDT
Message-ID: <435C5A8C.7020908@iprg.nokia.com>
Date: Sun, 23 Oct 2005 20:52:44 -0700
From: Vijay Devarapalli <vijayd@iprg.nokia.com>
User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
Subject: Re: [Mip6] comments about draft-ietf-mip6-ikev2-ipsec-03.txt
References: <200510221013.j9MADilC064652@givry.rennes.enst-bretagne.fr>
In-Reply-To: <200510221013.j9MADilC064652@givry.rennes.enst-bretagne.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248
Content-Transfer-Encoding: 7bit
Cc: mip6@ietf.org, vijay.devarapalli@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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Francis Dupont wrote:

>    >    >  In 5.4 page 11 I can't see a trace of the protocol=MH option...
>    >    
>    >    5.4 is about payload traffic. that means protocol = 'any'.
>    >    
>    > => so perhaps we should add a subsection here to explain how to do
>    > the protocol=MH option (which is easier than the "any" because it is
>    > not equivalent to a transport mode applied to a tunnel). Note I have
>    > the same concern about 6.1.4 (where currently proto = X ?! :-).
>    
>    I made a mistake in my earlier mail. it shouldnt have been 'any'.
>    it should have been 'X', which 'X' stands for a particular
>    protocol. perhaps thats enough?
>    
> => the word any was overloaded in RFC 3776 section 3.4, in fact there are
> 3 cases:
>  - X is really an any protocol
>  - X is MH
>  - X stands for all protocols (i.e., 'any')
> This has to be solved in the introduction as the DB entries look similar.

I could add a sentence saying by payload we mean all
traffic excluding MIPv6 signaling messages.


>    >    >  In 6.3 page 18:
>    >    > 
>    >    >    ... on the mobile node
>    >    >    when it receives the Binding acknowledgement sent by the home agent.
>    >    > 
>    >    > => I discussed this with Shinta-san and the endpoint update is performed
>    >    > by the mobile node after it sends the BU, i.e., the MN doesn't wait for
>    >    > the BA. Cf draft-sugimoto-mip6-pfkey-migrate-01.txt 4.1.2 page 7.
>    >    
>    >    I dont mind making the change, but do you think the mobile node
>    >    can start using the new CoA for tunneled packets before it is
>    >    sure the BU has been processed by the HA?
>    >    
>    > => usually it can't use the old CoA... and we can be optimistic.
>    > Note the HA should not check the outer source address (cf RFC 2401(bis))
>    > so if the BU fails the issue will be for returned traffic (CN->HA->MN).
>    
>    I went back and looked at the text. it talks about the IKE SA.
>    data traffic wont be sent over the IKE SA. I guess there is
>    no urgent need to update the IKE SA?
>    
> => The discussion with Shinta-san was about the SPD and SAD update
> but the IKE SA can be updated in fact at the same time. The only
> thing to wait for the BAck gives is the K flag from the HA so
> if the MN but not the HA support the K stuff the IKE SA is not
> updated then reestablished... IMHO this doesn't matter and we
> have clearly a case of overspecification. I can see two ways
> to solve this:
>  - remove the "and on the mobile node"
>  - add in the "and on the mobile node" the alternative.
> I believe the second is a bit better so the text should be:
> 
>    If the mobile node moves and its care-of address changes, the IKEv2
>    SA might not be valid, unless the mobility extensions defined in [13]
>    are implemented by both the mobile node and the home agent.  RFC 3775
>    defines a mechanism based on the successful exchange of Binding
>    Update and Binding Acknowledgement messages.  The IKE SA endpoints
>    are updated on the home agent when it receives the Binding Update
>    from the mobile node's new care-of address and on the mobile node
>    when it sends the Binding Update to the home agent or when it receives
>    the Binding Acknowledgement sent by the home agent.
>    This capability to change IKE endpoints is indicated through setting
>    the Key Management Capability (K) flag [2] in the Binding Update and
>    Binding Acknowledgement messages.  If the mobile node or the home
>    agent does not support this capability, then an IKEv2 exchange MUST
>    be initiated to re-establish the IKE SA.
> 
> (PS: note the uppercase in Acknowledgement)

okay.

Vijay


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



From mip6-bounces@ietf.org Mon Oct 24 00:05:01 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ETta1-0004PT-KH; Mon, 24 Oct 2005 00:05:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ETtZz-0004PJ-SU
	for mip6@megatron.ietf.org; Mon, 24 Oct 2005 00:04:59 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA11433
	for <mip6@ietf.org>; Mon, 24 Oct 2005 00:04:47 -0400 (EDT)
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ETtmf-00022s-6z
	for mip6@ietf.org; Mon, 24 Oct 2005 00:18:06 -0400
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id j9O3Vow12199;
	Sun, 23 Oct 2005 20:31:50 -0700
X-mProtect: <200510240331> Nokia Silicon Valley Messaging Protection
Received: from da-niradhcp16563.americas.nokia.com (10.241.165.63,
	claiming to be "[127.0.0.1]")
	by darkstar.iprg.nokia.com smtpd371nbU; Sun, 23 Oct 2005 20:31:48 PDT
Message-ID: <435C5D51.2060808@iprg.nokia.com>
Date: Sun, 23 Oct 2005 21:04:33 -0700
From: Vijay Devarapalli <vijayd@iprg.nokia.com>
User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>, mip6@ietf.org
References: <200510221059.j9MAx0Od064764@givry.rennes.enst-bretagne.fr>
In-Reply-To: <200510221059.j9MAx0Od064764@givry.rennes.enst-bretagne.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Content-Transfer-Encoding: 7bit
Cc: 
Subject: [Mip6] Re: (primary) coa and draft-ietf-mip6-ikev2-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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Francis Dupont wrote:
> There are still 4 "coa" reported by grep in the I-D (tentative 04).
> 
> I have a new/better argument for the primary CoA:
> in 6.1.2 (RR) the specs for the MN and the HA both uses the CoA in
> the outer header. If the MN could use any CoA the HA knows only the
> registered CoA which is the primary CoA. So in 5 and 6 the CoA is
> the primary CoA...
> 
> I propose to change in 5:
> 
>    For the examples described in this document, a mobile node with home
>    address, "home_address_1", a home agent with address, "home_agent_1"
>    and a user of the mobile node with identity "user_1" are assumed.  If
>    the home address of the mobile node changes, the SPD and SAD entries
>    need to re-created or updated for the new home address.
> 
> into:
> 
>    For the examples described in this document, a mobile node with home
>    address, "home_address_1", primary care-of address, "care_of_address_1",
>    a home agent with address, "home_agent_1"
>    and a user of the mobile node with identity "user_1" are assumed.  If
>    the home address of the mobile node changes, the SPD and SAD entries
>    need to re-created or updated for the new home address.
> 
> and for 6:
> 
>    In the examples shown below, the identity of the user of the mobile
>    node is assumed to be user_1, the home address of the mobile node is
>    assumed to be home_address_1 and the IPv6 address of the Home Agent
>    is assumed to be home_agent_1.
> 
> into:
> 
>    In the examples shown below, the identity of the user of the mobile
>    node is assumed to be user_1, the home address of the mobile node is
>    assumed to be home_address_1, the primary care-of address of the
>    mobile node is assumed to be care_of_address_1 and the IPv6 address
>    of the Home Agent is assumed to be home_agent_1.

okay. I made these changes.

> 
> BTW this defines care_of_address_1 too...
> 
> If we need a SHOULD for the primary care-of address in should be in 6.3
> (K flag). I believe we can constraint a bit the context when the K flag
> is used, I propose to insert before "The IKE SA endpoints" this statement:
> 
> The mobile node establishes the IKE SA with the home address using its
> primary care-of address.

I guess you meant

The mobile node establishes the IKE SA with the home agent using
its primary care-of address.

Vijay


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



From mip6-bounces@ietf.org Mon Oct 24 00:15:59 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ETtkd-0007EH-0z; Mon, 24 Oct 2005 00:15:59 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ETtkb-0007DN-86
	for mip6@megatron.ietf.org; Mon, 24 Oct 2005 00:15:57 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA11907
	for <mip6@ietf.org>; Mon, 24 Oct 2005 00:15:44 -0400 (EDT)
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ETtxG-0002Lg-M6
	for mip6@ietf.org; Mon, 24 Oct 2005 00:29:04 -0400
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id j9O3gm820099;
	Sun, 23 Oct 2005 20:42:48 -0700
X-mProtect: <200510240342> Nokia Silicon Valley Messaging Protection
Received: from da-niradhcp16563.americas.nokia.com (10.241.165.63,
	claiming to be "[127.0.0.1]")
	by darkstar.iprg.nokia.com smtpdLafuhk; Sun, 23 Oct 2005 20:42:46 PDT
Message-ID: <435C5FE2.4030300@iprg.nokia.com>
Date: Sun, 23 Oct 2005 21:15:30 -0700
From: Vijay Devarapalli <vijayd@iprg.nokia.com>
User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
Subject: Re: [Mip6] comments about draft-ietf-mip6-ikev2-ipsec-03.txt
References: <200510211637.j9LGb1DJ059988@givry.rennes.enst-bretagne.fr>
In-Reply-To: <200510211637.j9LGb1DJ059988@givry.rennes.enst-bretagne.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Content-Transfer-Encoding: 7bit
Cc: mip6@ietf.org, vijay.devarapalli@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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Francis Dupont wrote:

>    >    >    After the IKE_AUTH exchange completes, the mobile node initiates
>    >    >    CREATE_CHILD_SA exchanges to negotiate additional security
>    >    >    associations for protecting Return Routability signaling, Mobile
>    >    >    Prefix Discovery messages and optionally payload traffic.
>    >    > 
>    >    > => I propose:
>    >    > 
>    >    >    After the IKE_AUTH exchange completes, the mobile node initiates
>    >    >    CREATE_CHILD_SA exchanges to negotiate additional security
>    >    >    associations for protecting Return Routability signaling or
>    >    >    optionally payload traffic, and Mobile Prefix Discovery messages.
>    >    
>    >    whats the difference?
>    >    
>    > => X and Y and Z != (X or Z) and Y...
>    > RR (X) and payload (Z) are alternatives.
>    
>    the current requirements say the MN must create security
>    associations to protect RR and MPD messages. payload is
>    optional. this assumes the payload does not include
>    RR messages.
>    
> => argh! I can see where we disagree: I assume than payload means
> all payloads. I have not the time now but we should get the original
> text to see who is right... Of course the other TSx stuff applies here.

right. I now see why we were disagreeing. payload means
regular traffic. not IPsec payload. for IPsec everything
that is protected by IPsec becomes payload for IPsec.

Vijay


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



From mip6-bounces@ietf.org Mon Oct 24 00:56:54 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ETuOE-0000o2-Ff; Mon, 24 Oct 2005 00:56:54 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ETuOC-0000kU-QL
	for mip6@megatron.ietf.org; Mon, 24 Oct 2005 00:56:53 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA14611
	for <mip6@ietf.org>; Mon, 24 Oct 2005 00:56:39 -0400 (EDT)
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ETuar-0003bE-Ht
	for mip6@ietf.org; Mon, 24 Oct 2005 01:10:00 -0400
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id j9O4NgH14200;
	Sun, 23 Oct 2005 21:23:42 -0700
X-mProtect: <200510240423> Nokia Silicon Valley Messaging Protection
Received: from da-niradhcp16563.americas.nokia.com (10.241.165.63,
	claiming to be "[127.0.0.1]")
	by darkstar.iprg.nokia.com smtpdPIRHL5; Sun, 23 Oct 2005 21:23:40 PDT
Message-ID: <435C6979.20709@iprg.nokia.com>
Date: Sun, 23 Oct 2005 21:56:25 -0700
From: Vijay Devarapalli <vijayd@iprg.nokia.com>
User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
Subject: Re: [Mip6] granularity and draft-ietf-mip6-ikev2-ipsec
References: <200510221216.j9MCG6fq064949@givry.rennes.enst-bretagne.fr>
In-Reply-To: <200510221216.j9MCG6fq064949@givry.rennes.enst-bretagne.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 825e642946eda55cd9bc654a36dab8c2
Content-Transfer-Encoding: 7bit
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

hi Francis,

thanks for the new text.

Francis Dupont wrote:
> I propose to insert this section at the end of 4 (Requirements) before
> 5 (Manual Configuration) even the only thing which is required is to
> have compatible policies on the MN and the HA.
> Of course the wording can (should! :-) be improved... and someone
> can have a good proposal for the last issue (but please don't open
> a can of worms, it doesn't really matter if the IPv6 tunnel is a
> (very) virtual interface as payload protection is (very :-) optional).
> Another point: I don't know if we have to mention that the HoT[I] selectors
> make possible to put the HA IKE in "passive mode", i.e., the HA is never
> the initiator (good for IKE, bad for the MN-MN case :-).
> 
> Thanks
> 
> Francis.Dupont@enst-bretagne.fr
> 
> <section title="Selector Granularity Considerations">
> <t>
> IPsec implementations are not required to support fine grain selectors.

there is a problem here, since we mention early in the document
that the home agent and mobile SHOULD support Mobility Header
message type as an IPsec selector.

> More, applying fine grain selectors on forwarded packets is known to
> raise specific problems when some involved fields are not present in
> initial fragments, 

I am not sure what fragment means here? do you expect a HoTi
message to fragment ever? maybe we could say

   For various reasons, some implementations may choose to support....

> <t>
> The protection of Binding Updates and Acknowledgement and the protection
> of Mobile Prefix Discovery Messages are in transport mode where fine
> grain selectors are likely supported.
> </t>
> <t>
> But the protection of Return Routability Messages and the protection of
> the Payload Packets are in tunnel mode where fine grain selectors can be
> unavailable. In any case the mobile node and the home agent MUST use
> compatible policies.

hmm.. arent't return routability messages always protected by
tunnel mode whether you support MH message type as a selector?

do we need the above two sentences?

> <t>
> The last case (protection of all tunneled packets) introduces two new
> difficulties:
> <list style="symbols">
> <t>
> This protection can cover the Return Routability Messages so either there is
> no specific IPsec database entries for the Return Routability Messages and
> the protection for all tunneled packets MUST fulfill the requirements for
> the Return Routability Messages, or there are some specific SPD entries
> for the protection of the Return Routability Messages with a higher
> priority.
> <vspace blankLines="1"/></t>
> <t>
> The standard setup gives the same packet layout and applies to the same
> traffic than a transport mode applied to the IPv6-in-IPv6 tunnel.
> This document does not try to solve this issue, i.e., it only signals it.

I cant figure out what you wanted to say in the last paragraph.
so I excluding this for now

here is the re-written section.

5.  Selector Granularity Considerations

    IPsec implementations are compatible with this document even if they
    do not support fine grain selectors such as the Mobility Header
    message type and ICMPv6 message type.  For various reasons, some
    implementations may choose to support only coarse grain selectors
    (i.e., addresses and in some case protocol field) for forwarded
    traffic.  As finer grain selectors give a better control, i.e., the
    protection is only applied when required, the examples in the
    document always use the finest granularity.

    There following describes different ways of setting up IPsec policies
    for protecting Mobile IPv6 messages.

    o  The IPsec implementations on the mobile node and the home agent
       support fine grain selectors, including the Mobility Header
       message type This is the case assumed in the IPsec SPD and SAD
       examples in this document.

    o  The IPsec implementations only support selectors at a protocol
       level.  The protection of Return Routability Messages uses a setup
       similar to the regular payload packets to the correspondent node
       with the protocol selector set to Mobility Header messages.  All
       tunneled Mobility Header messages will be protected.

    o  The last case is where the protocol selector is not available or
       for privacy considerations all traffic tunneled between the mobile
       node and the home agent is protected.  This uses IPsec tunnel SA
       with the protocol selector set to 'any'.

    The last case where all tunneled traffic is protected introduces some
    additional considerations.

    o  If there is just one IPsec SA providing protection for all
       traffic, then the SA MUST fulfill the requirements for protecting
       the Return Routability messages which require confidentiality
       protection.  There can alsco be separate tunnel mode SPD entries
       for protecting the Return Routability messages with a higher
       priority.

Vijay


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



From mip6-bounces@ietf.org Mon Oct 24 02:10:14 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ETvXC-00020N-4t; Mon, 24 Oct 2005 02:10:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ETvX8-0001xq-Us
	for mip6@megatron.ietf.org; Mon, 24 Oct 2005 02:10:11 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA17632
	for <mip6@ietf.org>; Mon, 24 Oct 2005 02:09:57 -0400 (EDT)
Received: from iramx2.ira.uni-karlsruhe.de ([141.3.10.81]
	ident=[U2FsdGVkX193USGfNREkCgy1O3EO3R8L+IGvWY0mx84=])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ETvjp-0005gS-9J
	for mip6@ietf.org; Mon, 24 Oct 2005 02:23:18 -0400
Received: from i72archimedes.tm.uni-karlsruhe.de ([141.3.71.83])
	by iramx2.ira.uni-karlsruhe.de with esmtpsa 
	id 1ETvWp-0001Ge-Vz; Mon, 24 Oct 2005 08:09:55 +0200
Message-ID: <435C7AAF.2050600@tm.uka.de>
Date: Mon, 24 Oct 2005 08:09:51 +0200
From: Christian Vogt <chvogt@tm.uka.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-DE;
	rv:1.7.12) Gecko/20050923 Thunderbird/1.0.7 Mnenhy/0.7.2.0
X-Accept-Language: de-DE, de, en-us, en
MIME-Version: 1.0
To: henrik.petander@iki.fi
Subject: Re: [Mip6] New draft on make-before-break handoffs in Mobile IPv6
References: <36cb7a210510230236o73cf33c9oe86829278ca42b70@mail.gmail.com>
In-Reply-To: <36cb7a210510230236o73cf33c9oe86829278ca42b70@mail.gmail.com>
X-Enigmail-Version: 0.90.0.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: -66.1 (---------------------------------------------------)
X-Spam-Status: No
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Content-Transfer-Encoding: 7bit
Cc: mip6@ietf.org, tm-ro2@tm.uka.de
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Hi Henrik,

interested folks might also want to take a look at the discussion we had
on the Monami6 mailing list, starting here:

http://www1.ietf.org/mail-archive/web/monami6/current/msg00265.html

E.g., that thread attended to make-before-break handoffs with only a
single interface rather than two.

- Christian

-- 
Christian Vogt, Institute of Telematics, University of Karlsruhe
www.tm.uka.de/~chvogt/pubkey/



Henrik Petander wrote:
> Hi all,
> 
> We have written an internet draft on make-before-break handoffs in
> Mobile IPv6. The draft proposes improvements to Mobile IPv6 binding
> management for make-before-break handoffs to avoid packet loss during handoffs.
> The draft is available at the ietf website:
> 
> http://www.ietf.org/internet-drafts/draft-petander-mip6-mbb-00.txt
> 
> 
> Abstract:
> 
> "Mobile IPv6 binding management has been designed for
> break-before-make handoffs, which can be performed by hosts equipped
> with a single interface. However, a mobile node may be equipped with
> multiple interfaces, allowing it to perform make-before-break handoffs
> by connecting simultaneously to two overlapping access networks during
> the handoff. In theory these handoffs can be lossless, provided that
> there is sufficient overlap between the two networks. However, unless
> Mobile IPv6 bindings are managed carefully mobile node and
> correspondent node will have inconsistent binding state during the
> handoff, which will lead to packet loss. In this draft we propose
> changes to binding management for lossless make-before-break handoffs.
> The proposed changes do not affect the interoperability with Mobile
> IPv6 nodes not implementing these changes."
> 
> For background information: We measured the performance of Mobile IPv6
> in make-before-break handoffs with two interfaces and noticed bad
> performance when there was network latency between MN and HA.  Packets
> sent between BU and BA were dropped either by HA or MN, depending on
> whether handoff in MN was performed when sending BU or receiving BA.
> We implemented the MN part of the draft and verified that the proposed
> change fixed the problem and allowed lossless handoffs for MIPv6, so
> the modifications to MIPv6  work also in practice.
> 
> Regards,
> Henrik Petander





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



From mip6-bounces@ietf.org Mon Oct 24 02:59:24 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ETwIm-0006Be-6j; Mon, 24 Oct 2005 02:59:24 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ETwIk-0006Au-7o
	for mip6@megatron.ietf.org; Mon, 24 Oct 2005 02:59:22 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA20169
	for <mip6@ietf.org>; Mon, 24 Oct 2005 02:59:08 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ETwVQ-0007ME-4J
	for mip6@ietf.org; Mon, 24 Oct 2005 03:12:30 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id j9O6wm701469; Mon, 24 Oct 2005 08:58:48 +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
	j9O6wlF6080050; Mon, 24 Oct 2005 08:58:48 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200510240658.j9O6wlF6080050@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Vijay Devarapalli <vijayd@iprg.nokia.com>
Subject: Re: [Mip6] comments about draft-ietf-mip6-ikev2-ipsec-03.txt 
In-reply-to: Your message of Sun, 23 Oct 2005 20:52:44 PDT.
	<435C5A8C.7020908@iprg.nokia.com> 
Date: Mon, 24 Oct 2005 08:58:47 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Cc: mip6@ietf.org, vijay.devarapalli@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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   > => the word any was overloaded in RFC 3776 section 3.4, in fact there are
   > 3 cases:
   >  - X is really an any protocol
   >  - X is MH
   >  - X stands for all protocols (i.e., 'any')
   > This has to be solved in the introduction as the DB entries look similar.
   
   I could add a sentence saying by payload we mean all
   traffic excluding MIPv6 signaling messages.
   
=> this is solved by my section about granularity (where either the 'any'
payload DB entries cover MIPv6 or there are specific prioritary DB entries
for MIPv6 (which is the proper way to implement all traffic excluding MIPv6)).

Thanks

Francis.Dupont@enst-bretagne.fr

PS: all the points should be closed.

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



From mip6-bounces@ietf.org Mon Oct 24 03:01:07 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ETwKR-0006Vp-QP; Mon, 24 Oct 2005 03:01:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ETwKQ-0006Vg-0Y
	for mip6@megatron.ietf.org; Mon, 24 Oct 2005 03:01:06 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA20325
	for <mip6@ietf.org>; Mon, 24 Oct 2005 03:00:52 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ETwX7-0007Pr-NR
	for mip6@ietf.org; Mon, 24 Oct 2005 03:14:14 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id j9O70M701554; Mon, 24 Oct 2005 09:00:22 +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
	j9O70MjA080085; Mon, 24 Oct 2005 09:00:22 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200510240700.j9O70MjA080085@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Vijay Devarapalli <vijayd@iprg.nokia.com>
In-reply-to: Your message of Sun, 23 Oct 2005 21:04:33 PDT.
	<435C5D51.2060808@iprg.nokia.com> 
Date: Mon, 24 Oct 2005 09:00:22 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Cc: mip6@ietf.org
Subject: [Mip6] Re: (primary) coa and draft-ietf-mip6-ikev2-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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   > The mobile node establishes the IKE SA with the home address using its
   > primary care-of address.
   
   I guess you meant
   
   The mobile node establishes the IKE SA with the home agent using
   its primary care-of address.
   
=> oops... of course you're right.

Thanks

Francis.Dupont@enst-bretagne.fr
   

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



From mip6-bounces@ietf.org Mon Oct 24 03:17:25 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ETwaD-000194-Jl; Mon, 24 Oct 2005 03:17:25 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ETwaB-00018q-Ii
	for mip6@megatron.ietf.org; Mon, 24 Oct 2005 03:17:23 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA21225
	for <mip6@ietf.org>; Mon, 24 Oct 2005 03:17:09 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ETwmt-000813-Dr
	for mip6@ietf.org; Mon, 24 Oct 2005 03:30:31 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id j9O7H7703103; Mon, 24 Oct 2005 09:17: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
	j9O7H7NG080170; Mon, 24 Oct 2005 09:17:07 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200510240717.j9O7H7NG080170@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Vijay Devarapalli <vijayd@iprg.nokia.com>
Subject: Re: [Mip6] granularity and draft-ietf-mip6-ikev2-ipsec 
In-reply-to: Your message of Sun, 23 Oct 2005 21:56:25 PDT.
	<435C6979.20709@iprg.nokia.com> 
Date: Mon, 24 Oct 2005 09:17:07 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   > <section title="Selector Granularity Considerations">
   > <t>
   > IPsec implementations are not required to support fine grain selectors.
   
   there is a problem here, since we mention early in the document
   that the home agent and mobile SHOULD support Mobility Header
   message type as an IPsec selector.
   
=> yes, please add a reference to 2401bis after "required".

   > More, applying fine grain selectors on forwarded packets is known to
   > raise specific problems when some involved fields are not present in
   > initial fragments, 
   
   I am not sure what fragment means here? do you expect a HoTi
   message to fragment ever? maybe we could say
   
=> I agree HoTi message should be never fragmented but as in general
a forwarded message can be fragmented some implementors already chose
to support only coarse grain selectors.

      For various reasons, some implementations may choose to support....
   
=> I prefer to give an example of the various reasons but good wording
is the first goal...

   > But the protection of Return Routability Messages and the protection of
   > the Payload Packets are in tunnel mode where fine grain selectors can be
   > unavailable. In any case the mobile node and the home agent MUST use
   > compatible policies.
   
   hmm.. arent't return routability messages always protected by
   tunnel mode whether you support MH message type as a selector?
   
=> yes, they MUST be protected by tunnel mode.

   do we need the above two sentences?
   
=> the first one is an introduction and the second one a requirement.

   > The standard setup gives the same packet layout and applies to the same
   > traffic than a transport mode applied to the IPv6-in-IPv6 tunnel.
   > This document does not try to solve this issue, i.e., it only signals it.
   
   I cant figure out what you wanted to say in the last paragraph.
   so I excluding this for now
   
=> there is an implementation choice between a tunnel mode and a transport
mode over a tunnel a la John Touch. We only signal this as the second has
many advantages but is clearly not standard.

   here is the re-written section.
   
   5.  Selector Granularity Considerations
   
       IPsec implementations are compatible with this document even if they
       do not support fine grain selectors such as the Mobility Header
       message type and ICMPv6 message type.  For various reasons, some
       implementations may choose to support only coarse grain selectors
       (i.e., addresses and in some case protocol field) for forwarded
       traffic.  As finer grain selectors give a better control, i.e., the
       protection is only applied when required, the examples in the
       document always use the finest granularity.
   
       There following describes different ways of setting up IPsec policies
       for protecting Mobile IPv6 messages.
   
       o  The IPsec implementations on the mobile node and the home agent
          support fine grain selectors, including the Mobility Header
          message type This is the case assumed in the IPsec SPD and SAD
          examples in this document.
   
       o  The IPsec implementations only support selectors at a protocol
          level.  The protection of Return Routability Messages uses a setup
          similar to the regular payload packets to the correspondent node
          with the protocol selector set to Mobility Header messages.  All
          tunneled Mobility Header messages will be protected.
   
       o  The last case is where the protocol selector is not available or
          for privacy considerations all traffic tunneled between the mobile
          node and the home agent is protected.  This uses IPsec tunnel SA
          with the protocol selector set to 'any'.
   
       The last case where all tunneled traffic is protected introduces some
       additional considerations.
   
       o  If there is just one IPsec SA providing protection for all
          traffic, then the SA MUST fulfill the requirements for protecting
          the Return Routability messages which require confidentiality
          protection.  There can alsco be separate tunnel mode SPD entries
          for protecting the Return Routability messages with a higher
          priority.
   
=> ok, we can publish this.

Thanks

Francis.Dupont@enst-bretagne.fr

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



From mip6-bounces@ietf.org Mon Oct 24 05:12:13 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ETyNJ-0007TU-5G; Mon, 24 Oct 2005 05:12:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ETyNH-0007Qp-La
	for mip6@megatron.ietf.org; Mon, 24 Oct 2005 05:12:11 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA26283
	for <mip6@ietf.org>; Mon, 24 Oct 2005 05:11:59 -0400 (EDT)
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ETyZz-0003GW-Gh
	for mip6@ietf.org; Mon, 24 Oct 2005 05:25:21 -0400
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id j9O8d2i01176;
	Mon, 24 Oct 2005 01:39:02 -0700
X-mProtect: <200510240839> Nokia Silicon Valley Messaging Protection
Received: from esdhcp09nok080233.ntc.nokia.com (172.21.80.233,
	claiming to be "[127.0.0.1]")
	by darkstar.iprg.nokia.com smtpdrgjeix; Mon, 24 Oct 2005 01:39:00 PDT
Message-ID: <435CA550.7070601@iprg.nokia.com>
Date: Mon, 24 Oct 2005 12:11:44 +0300
From: "Charles E. Perkins" <charliep@iprg.nokia.com>
Organization: Nokia Research Center, Mtn. View
User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923)
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; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Content-Transfer-Encoding: 7bit
Cc: david.kessens@nokia.com, Pekka Savola <pekkas@netcore.fi>
Subject: [Mip6] Securing Mobile IPv6 Route Optimization Using a Static
 Shared Key (revised submission)
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Hello folks,

I have submitted the abovementioned draft to the IETF
Internet Drafts department.  Until it is distributed, I have
made it accessible at the following URL:
   http://people.nokia.net/charliep/txt/mobilev6/precfg.txt


On September 20, 2005, Pekka Savola wrote:

> It would probably be a good idea to also put a bullet point on this in 
> Applicability Statement, so that it's clear that this option is only 
> to be used for BU auth -- because I note that this isn't stated 
> explicitly. For example,
>
>  - This mechanism is used only for authenticating Binding Update
>    messages (and not e.g., data) so the total volume of traffic
>    is low.
>
> (You could also add some extra text referring to the [4] reference 
> here to address other IESG comments relating to whether the use of 
> manual keying is valid in this scenario if you'd like)

Done.  Your suggested text was added to the Applicability Statement,
along with a citation to RFC 4107 and a cross reference to the discussion
in the Security Considerations.

With this modification, I believe that the draft resolves all open issues.

Regards,
Charlie P.


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



From mip6-bounces@ietf.org Mon Oct 24 06:10:24 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ETzHb-0005wK-Nm; Mon, 24 Oct 2005 06:10:23 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ETzHa-0005wB-6D
	for mip6@megatron.ietf.org; Mon, 24 Oct 2005 06:10:22 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA29046
	for <mip6@ietf.org>; Mon, 24 Oct 2005 06:10:09 -0400 (EDT)
Received: from omgo.iij.ad.jp ([202.232.30.157])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ETzUH-0005Dn-TT
	for mip6@ietf.org; Mon, 24 Oct 2005 06:23:31 -0400
Received: OTM-MO id j9OAA4M0019949; Mon, 24 Oct 2005 19:10:04 +0900 (JST)
Received: OTM-MIX0 id j9OAA3jJ008431; Mon, 24 Oct 2005 19:10:04 +0900 (JST)
Received: from localhost (keiichi00.osaka.iij.ad.jp [192.168.64.45])
	by jc-smtp.iij.ad.jp (JC-SMTP/jc-smtp) id j9OAA3Uo004860;
	Mon, 24 Oct 2005 19:10:03 +0900 (JST)
Date: Mon, 24 Oct 2005 19:11:34 +0900 (JST)
Message-Id: <20051024.191134.27213453.keiichi@iijlab.net>
To: H.Soliman@flarion.com
Subject: Re: [Mip6] I-D ACTION:draft-ietf-mip6-nemo-v4traversal-00.txt 
From: Keiichi SHIMA <keiichi@iijlab.net>
In-Reply-To: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCD76@ftmailserver.flariontech.com>
References: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCD76@ftmailserver.flariontech.com>
X-Mailer: Mew version 4.1.50 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8c5db863102a3ada84e0cd52a81a79e
Content-Transfer-Encoding: 7bit
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Hello Hesham,

Please find my comments inline..

From: "Soliman, Hesham" <H.Soliman@flarion.com>
Date: Thu, 20 Oct 2005 23:25:46 -0400
>  > 
>  > - The draft seems discussing two separate issues.
>  > 
>  > I think, v4traversal and supporting IPv4 HoA/network are different
>  > issues.  Don't we need to think an scenario, which doesn't need
>  > v4traversal but need IPv4 communication, and vice versa?
> 
> => Absolutely. That's why the draft allows a node to use an IPv4
> home address whether it's in an IPv4 or an IPv6 network.
> 
>   In the
>  > previous discussion (two months ago in the MIP6 mailing list, maybe),
>  > you mentioned that separating these two issues add complexity.  
> 
> => Yes.
> 
>    But
>  > I'm afraid I still don't understand what complexity is added when we
>  > divide the above two issues.  It should be helpful if you could show
>  > some examples.
> 
> => What I was referring to before was writing two different specs in 
> parallel. It's a matter of organisation and working out dependencies 
> between documents. One solution can easily address having IPv4 home 
> or coa as you can see from this document. 

My point is that having IPv4 CoA and Having IPv4 HoA is different
things and they are orthogonal.  (I think my explanation is not
good...)

Let's consider to implement IPv6 mobile node which supports IPv4
access network, but don't support IPv4 HoA.  Which RFC should we
support?  If we continue to discuss the different things in one draft,
we must also make it clear which section(s) is necessary to implement
what feature.  But I feel it is a bad idea to specify features in such
a manner.  Easier way to make it clear is to divide the specification...


>  > - more detailed operational procedure is required
>  > 
>  >   The draft doesn't describe mobile router/home agent 
>  > operation when a
>  >   static IPv4 address or IPv4 mobile network prefix is used.  
> 
> => Could you be specific on what is missing from the current
> draft in terms of operation? Meaning, as an implementer, when
> you read the draft, what more do you need to know to implement it?

Frankly speaking, I think I can implement the function from the text,
since I already have much knowledge of MIP implementation.  But maybe
the draft at least should mention about

- home agent operation when IPv4 mobile network is behind a mobile
  router
- mobile router operation which has IP4 mobile network
- proxy operation on a home agent when a mobile router use an IPv4
  home address

I'll attach some text from my draft (draft-shima-nemo-v4prefix-01.txt
which should be published in a few days).  Although I don't think the
text can be used as it is, but, I think the same kind of specification
is useful to say.

--quote start-------------------------------------------------------------
6.  Mobile Router operation

   A mobile router which has IPv4 networks on its ingress interface can
   include the IPv4 Mobile Network Prefix option in a Binding Update
   message to its home agent.  After receiving a successful
   acknowledgment from the home agent, the mobile router adds a route
   entry which indicates that all traffic from the IPv4 networks is
   forwarded to the tunnel interface created between the mobile router
   and its home agent.

   A mobile router will receive a Binding Acknowledgment message with
   the IPv4 Mobile Prefix Registration Status Option when a home agent
   supports this extension.  If the Binding Acknowledgment does not
   include the option, the IPv4 prefix registration cannot be used.

   After successful registration of IPv4 network prefixes, a mobile
   router forwards all IPv4 packets which source address is in the range
   of the registered IPv4 prefix to its home agent using an IPv6 tunnel
   created between the mobile router and its home agent, when those IPv4
   packets are received from the ingress interface of the mobile router.
   On the other hand, when the mobile router receives IPv4 packets from
   the tunnel and the destination address of the internal packet is in
   the range of the registered IPv4 prefix, the mobile router forwards
   those IPv4 packets to its ingress interface.

8.  Home Agent operation

   A home agent which supports the IPv4 Mobile Network Prefix Option
   will add a route entry for the IPv4 network prefix when it receives a
   Binding Update message with the option.  A Binding Acknowledgment
   message sent from the home agent must include the IPv4 Mobile Prefix
   Registration Status Option to indicate the processing status of the
   received IPv4 Mobile Prefix Option.

   When a home agent accept the IPv4 Mobile Network Prefix Option, the
   status field of the IPv4 Mobile Network Registration Status Option
   must be set to 0 indicating success.  Otherwise, the status code must
   be filled with an error code as described in section Section 5.2.

   After successful registration of IPv4 prefixes, a home agent start
   forwarding IPv4 packets which destination address is in the range of
   registered IPv4 prefix to the tunnel to the mobile router which
   registered the corresponding IPv4 prefix.  At the same time, the home
   agent also start accepting IPv4 packets sent from the tunnel which
   source address is in the range of the registered IPv4 prefix and
   start forwarding to the IPv4 internet.

   If the Prefix Length field in the incoming IPv4 Mobile Network Prefix
   Option is equal to 32, a home agent treats the value in the IPv4
   Mobile Network Prefix field as an IPv4 Mobile Address.  The address
   must be one of addresses of the IPv4 network that the home agent is
   attached to.  If the validation succeeds, a home agent starts
   proxying the IPv4 node identifier included in the option (after
   checking there is no other nodes which is using the IPv4 address).  A
   home agent will intercept all IPv4 packets delivered to the home
   network if the destination address of the packets is equal to the
   IPv4 Mobile Address.  These intercepted packets will be forwarded to
   the mobile host using an IPv6 tunnel created between the home agent
   and the mobile host.  If a home agent receives IPv4 packets which
   source address is the IPv4 Mobile Address from the IPv6 tunnel
   interface, a home agent will forward the packets to the IPv4
   Internet.
--quote end----------------------------------------------------------------


>  > - in page 16
>  > 
>  > >    - If the binding update is accepted for the IPv4 home 
>  > address, the
>  > >      home agent MUST create a binding cache entry for the IPv4 home
>  > >      address/prefix. If a single IPv4 home address were 
>  > requested, it
>  >                        
>  > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>  > >      MAY be stored in the IPv4-mapped IPv6 address format. The home
>  >        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>  > >      agent MUST include an IPv4 acknowledgement option in 
>  > the mobility
>  > >      header containing the binding acknowledgement.
>  > 
>  > What does the above underlined text mean?  It seems you are 
>  > discussing
>  > implementation specific thing, which should not be discussed in the
>  > specification.
> 
> => The text means that you can store a unicast address in the mapped 
> format if you want (hence the MAY). Conceptual implementation issues 
> are discussed in most specs actually. See for instance RFC 3775, RFC 2461, 
> IPsec RFCs ....etc. 

Some RFC do.  But I just feel that kind of definition is nothing to do
with the protocol and I don't think it is necessary to mention in RFC
(which defines a protocol), IMHO.

 
>  > - (minor) terminology
>  > 
>  >   I don't think the word 'IPv4 home address' is a good wording, since
>  >   the word is already used by MIP4.  So, maybe other wording, such as
>  >   'IPv4 static address' seems better.
> 
> => Hmm, I don't think MIPv4 will sue us for it :) It seems appropriate
> for the use. I'm open to suggestions, but IPv4 static address is not appropriate
> IMO given that it is allocated statically or dynamically. 

Ah, yes.  'static' might be a wrong choice.  It may not cause any
confusion, as long as we use the word 'IPv4 home address' only in
Mobile IPv6 context.  So, then, I don't mind to keep it until we face
any kind of problem.

---
Keiichi SHIMA
IIJ Research Laboratory <keiichi@iijlab.net>
KAME Project <keiichi@kame.net>

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



From mip6-bounces@ietf.org Mon Oct 24 08:00:56 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EU10Z-0001KP-Ub; Mon, 24 Oct 2005 08:00:55 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EU10X-0001Jl-RE
	for mip6@megatron.ietf.org; Mon, 24 Oct 2005 08:00:53 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA04609
	for <mip6@ietf.org>; Mon, 24 Oct 2005 08:00:40 -0400 (EDT)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EU1DH-0000WR-CQ
	for mip6@ietf.org; Mon, 24 Oct 2005 08:14:04 -0400
Received: from il06exr02.mot.com (il06exr02.mot.com [129.188.137.132])
	by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id j9OCCJim001400;
	Mon, 24 Oct 2005 05:12:19 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by il06exr02.mot.com (8.13.1/8.13.0) with ESMTP id j9OC92FX027743;
	Mon, 24 Oct 2005 07:09:02 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id 97E6A865980; Mon, 24 Oct 2005 14:00:25 +0200 (CEST)
Message-ID: <435CCCD9.4070605@motorola.com>
Date: Mon, 24 Oct 2005 14:00:25 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: James Kempf <Kempf@docomolabs-usa.com>
Subject: Re: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
References: <4D2F935F08D41A4C8866693F4F0D7C4F58DBC3@lan-ex-01.panasonic.de>
	<155a01c5ceb1$6748e190$196115ac@dcml.docomolabsusa.com>
In-Reply-To: <155a01c5ceb1$6748e190$196115ac@dcml.docomolabsusa.com>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Content-Transfer-Encoding: 7bit
Cc: mip6@ietf.org, Kilian Weniger <Kilian.Weniger@eu.panasonic.com>,
	Francis Dupont <Francis.Dupont@enst-bretagne.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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Hello to dhaad-harmful contributors and supporters.

James Kempf wrote:

>> From a deployment standpoint, there are two issues with DHAAD:
> 
> 
> - it uses ICMP across the Internet. The trend has been to turn off ICMP
> except for local link communications, to avoid convenient vehicles for
> DoS. I know that one can theoretically configure the firewall to filter
> on the ICMP message type field, but it is easier just to drop it at the
> firewall than to try to figure out what ICMP is good and what is bad.

I think the argument 'some protocol may be blocked by some firewalls'
for considering some protocol harmful and support other protocols
instead, is probably a little bit flawed.

In a sense, the strongest firewalls of some operators block all that is
not HTTP, and I imagine they can even block HTTP-tunnelled traffic.
Which would suggest that only a cleartext HTTP-based HA Discovery may
have the highest chances of getting through.

In another sense, if some operators will open ports (and import SRV
records in their DNS, and provide _full_ DNS service to MNs) because
some IETF Document says so, then the proposed DNS-based HAD scheme may
indeed work and I support its idea.

> - AFIK, there is no way currently standardized to securely update
> anycast routing except to manually insert host routes into the subnet
> router handling the anycast address. So maintaining an anycast address
> would require extra maintenance effort, manually inserting and deleting
> the routes when HAs are added or deleted.

I think the IPsec shortcoming with respect to anycast, and the inability
to securely update anycast routes may not play an important role in
discarding the current DHAAD.

For example, I wonder whether the following normal DHAAD procedure would
be secure enough:

-MN sends DHAAD Request to the anycast address and has SA with that
 anycast address (which is prefix:fdff:ffff:ffff:fffe/128).
-only one HA replies back to MN, IP packet having
 src=prefix:fdff:ffff:ffff:fffe/128
-the HAs communicate with each other with RAs and collaboratively build
 a coherent list of HAs ordered with some priority.

With that scheme I think there is no need to manually insert or delete
routes when HAs are added or deleted.

Would this be secure enough?  Would IPsec allow SAs whose IP address is
an anycast address?

Sorry if I overlook something obvious,

Alex


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



From mip6-bounces@ietf.org Mon Oct 24 08:16:04 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EU1E6-0006QD-1x; Mon, 24 Oct 2005 08:14:54 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EU1E3-0006Q4-WB
	for mip6@megatron.ietf.org; Mon, 24 Oct 2005 08:14:52 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA05988
	for <mip6@ietf.org>; Mon, 24 Oct 2005 08:14:38 -0400 (EDT)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EU1Qn-0001BE-NX
	for mip6@ietf.org; Mon, 24 Oct 2005 08:28:03 -0400
Received: from il06exr01.mot.com (il06exr01.mot.com [129.188.137.131])
	by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id j9OCQdnF003220;
	Mon, 24 Oct 2005 05:26:39 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by il06exr01.mot.com (8.13.1/8.13.0) with ESMTP id j9OCObXG019898;
	Mon, 24 Oct 2005 07:24:38 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id 66525865980; Mon, 24 Oct 2005 14:14:45 +0200 (CEST)
Message-ID: <435CD035.3040303@motorola.com>
Date: Mon, 24 Oct 2005 14:14:45 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: "Soliman, Hesham" <H.Soliman@flarion.com>
Subject: Re: [Mip6] review of draft-ietf-mip6-dsmip-problem-00.txt
References: <A11736FE943F1A408F8BBB1B9F5FE8AD17DE3C@ftmailserver.flariontech.com>
In-Reply-To: <A11736FE943F1A408F8BBB1B9F5FE8AD17DE3C@ftmailserver.flariontech.com>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Content-Transfer-Encoding: 7bit
Cc: Jari Arkko <jari.arkko@kolumbus.fi>,
	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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Hello Hesham, I have the draft too, please allow me to interfere below.

Soliman, Hesham wrote:
>>> 2.4. The impossibility of maintaining connectivity
>>> 
>>> A final point to consider is that even if both mobility protocols
>>> are supported by a mobile node seamless connectivity would not in
>>> fact be guarantied since that also depends on the IPv4/IPv6 
>>> capabilities of the networks the mobile is visiting i.e.: a dual
>>> stack node attempting to connect via a IPv4 only network would
>>> not be able to maintain connectivity of its IPv6 applications and
>>> vice versa.
>> 
>> This, to me, is the main problem in fact.
> 
> => I can't resist a comment on this :) To some people (George and
> myself included) running MIP6 and MIP4 in parallel is almost equally
> bad.

To me, running both MIP6 and MIP4 simultaneously on the MN is no bad.
It is no worse than running both the IPv4 stack and the IPv6 stack.

If we can't imagine a future where all nodes are exclusively IPv6 we
can't imagine a future where all nodes are exclusively MIP6 either, IMHO.

Alex


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



From mip6-bounces@ietf.org Mon Oct 24 08:27:27 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EU1QF-0001S8-94; Mon, 24 Oct 2005 08:27:27 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EU1QD-0001S3-9G
	for mip6@megatron.ietf.org; Mon, 24 Oct 2005 08:27:25 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA06467
	for <mip6@ietf.org>; Mon, 24 Oct 2005 08:27:11 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EU1cu-0001YO-V4
	for mip6@ietf.org; Mon, 24 Oct 2005 08:40:36 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id j9OCQpp30958; Mon, 24 Oct 2005 14:26:51 +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
	j9OCQpGh081634; Mon, 24 Oct 2005 14:26:51 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200510241226.j9OCQpGh081634@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Alexandru Petrescu <alexandru.petrescu@motorola.com>
Subject: Re: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt 
In-reply-to: Your message of Mon, 24 Oct 2005 14:00:25 +0200.
	<435CCCD9.4070605@motorola.com> 
Date: Mon, 24 Oct 2005 14:26:51 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b280b4db656c3ca28dd62e5e0b03daa8
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   Hello to dhaad-harmful contributors and supporters.
   
   > - it uses ICMP across the Internet. The trend has been to turn off ICMP
   > except for local link communications, to avoid convenient vehicles for
   > DoS. I know that one can theoretically configure the firewall to filter
   > on the ICMP message type field, but it is easier just to drop it at the
   > firewall than to try to figure out what ICMP is good and what is bad.
   
   I think the argument 'some protocol may be blocked by some firewalls'
   for considering some protocol harmful and support other protocols
   instead, is probably a little bit flawed.
   
=> unfortunately ICMP is commonly blocked so it is a real operational
issue. Look at draft-davies-v6ops-icmpv6-filtering-bcp-00.txt...

   In a sense, the strongest firewalls of some operators block all that is
   not HTTP, and I imagine they can even block HTTP-tunnelled traffic.
   Which would suggest that only a cleartext HTTP-based HA Discovery may
   have the highest chances of getting through.
   
=> BTW DNS is not filtered out.

   In another sense, if some operators will open ports (and import SRV
   records in their DNS, and provide _full_ DNS service to MNs) because
   some IETF Document says so, then the proposed DNS-based HAD scheme may
   indeed work and I support its idea.
   
=> DNS-based HAD scheme has many advantages. For some (including me)
it can be made secure, for some others it is the ICMP filtering, etc...

   > - AFIK, there is no way currently standardized to securely update
   > anycast routing except to manually insert host routes into the subnet
   > router handling the anycast address. So maintaining an anycast address
   > would require extra maintenance effort, manually inserting and deleting
   > the routes when HAs are added or deleted.
   
=> the routing stuff is in order to make the anycast destination a known
and stable box.

   I think the IPsec shortcoming with respect to anycast, and the inability
   to securely update anycast routes may not play an important role in
   discarding the current DHAAD.
   
   For example, I wonder whether the following normal DHAAD procedure would
   be secure enough:
   
   -MN sends DHAAD Request to the anycast address and has SA with that
    anycast address (which is prefix:fdff:ffff:ffff:fffe/128).

=> currently it is not possible to establish a symmetric IPsec SA
pair with an anycast address.

   -only one HA replies back to MN, IP packet having
    src=prefix:fdff:ffff:ffff:fffe/128
   -the HAs communicate with each other with RAs and collaboratively build
    a coherent list of HAs ordered with some priority.
   
   With that scheme I think there is no need to manually insert or delete
   routes when HAs are added or deleted.
   
   Would this be secure enough?

=> it is a matter of state: an unsecure DHAAD doesn't give a security
disaster...

   Would IPsec allow SAs whose IP address is an anycast address?

=> no because an anycast can't be used as a source address.
   
   Sorry if I overlook something obvious,
   
=> the two questions are:
 - should we keep a DHAAD mechanism or HA assignment is the right thing
   to do?
 - is the DNS-based DHAAD mechanism better enough to replace the ICMP-base
   one?

Regards

Francis.Dupont@enst-bretagne.fr

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



From mip6-bounces@ietf.org Mon Oct 24 08:34:49 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EU1XN-0002kW-5g; Mon, 24 Oct 2005 08:34:49 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EU1XL-0002ja-Au
	for mip6@megatron.ietf.org; Mon, 24 Oct 2005 08:34:47 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA06788
	for <mip6@ietf.org>; Mon, 24 Oct 2005 08:34:33 -0400 (EDT)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EU1k5-0001ni-8p
	for mip6@ietf.org; Mon, 24 Oct 2005 08:47:58 -0400
Received: from il06exr03.mot.com (il06exr03.mot.com [129.188.137.133])
	by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id j9OCkb6W005843
	for <mip6@ietf.org>; Mon, 24 Oct 2005 05:46:37 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by il06exr03.mot.com (8.13.1/8.13.0) with ESMTP id j9OCijlD025828
	for <mip6@ietf.org>; Mon, 24 Oct 2005 07:44:45 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP id DE49D865980
	for <mip6@ietf.org>; Mon, 24 Oct 2005 14:34:43 +0200 (CEST)
Message-ID: <435CD4E3.8000209@motorola.com>
Date: Mon, 24 Oct 2005 14:34:43 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: Mobile IPv6 Mailing List <mip6@ietf.org>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Content-Transfer-Encoding: 7bit
Subject: [Mip6] More comments on draft-ietf-mip6-dsmip-problem.00.txt
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Dears, here are more comments on draft-ietf-mip6-dsmip-problem.00.txt

Overall, the document tries to motivate the need for v4 enhancements to
MIP6 and v6 enhancements to MIP4.  It achieves that mainly by using
'efficiency' arguments - it claims it's not efficient to run both MIP4
and MIP6 on a single MN.

'Efficiency' is something difficult to describe when so little context:
what's efficient for some is total waste for some other.  Argumenting
over efficiency is usually further supported with analysis data, and I
was expecting to see some tables with measurements, that would say that
a small PDA is very slow when running both MIP4 and MIP6, or similar.
These measurements are not provided.  From implementation experience, I
personally don't see a PDA being slowed because both MIP4 and MIP6 run;
that PDA doesn't run any faster when only MIP4 or only MIP6 runs.

The only quantified argument provided is that it's bad for MN to send
two messages whenever handover (a RegReq and a BU).  But this
immediately bears the question: why it's bad?  Is it taking too long?
With respect to what?

It also invites to counter-argument that an MN receiving FA
Advertisements does not necessarily receive RAs simultaneously, i.e. a
change in v4 CoA is not necessarily a change in v6 CoA.  This
'decoupled' change happens when the access network is v4 and v6 access
is through a tunnel.  So it is not true that every change in v4 CoA
demands both RegReq and v6 BU.

So, overall I think the draft has a valuable conclusion (motivate v6
enhancements to MIP4 and viceversa) but has a useless motivation.

For example, assuming that running both MIP4 and MIP6 is not
inefficient, it is possible to have a MIP4/MIP6 DS MN that connects to a
v4 access network, run the full MIP6, run the NAT Traversal part of
MIP4, and obtain an implementation that does not need neither v4
protocolar enhancements to MIP6 nor v6 protocolar enhancements to MIP4.

Alex


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



From mip6-bounces@ietf.org Mon Oct 24 09:44:51 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EU2d9-0007Bb-00; Mon, 24 Oct 2005 09:44:51 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EU2d2-00078G-SA
	for mip6@megatron.ietf.org; Mon, 24 Oct 2005 09:44:49 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10461
	for <mip6@ietf.org>; Mon, 24 Oct 2005 09:44:30 -0400 (EDT)
Received: from motgate4.mot.com ([144.189.100.102])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EU2po-0004BH-5I
	for mip6@ietf.org; Mon, 24 Oct 2005 09:57:56 -0400
Received: from az33exr01.mot.com (az33exr01.mot.com [10.64.251.231])
	by motgate4.mot.com (8.12.11/Motgate4) with ESMTP id j9ODrh1S022133;
	Mon, 24 Oct 2005 06:53:43 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by az33exr01.mot.com (8.13.1/8.13.0) with ESMTP id j9ODuhCV006960;
	Mon, 24 Oct 2005 08:56:44 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id 81B35865980; Mon, 24 Oct 2005 15:44:23 +0200 (CEST)
Message-ID: <435CE537.3070900@motorola.com>
Date: Mon, 24 Oct 2005 15:44:23 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
Subject: Re: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
References: <200510241226.j9OCQpGh081634@givry.rennes.enst-bretagne.fr>
In-Reply-To: <200510241226.j9OCQpGh081634@givry.rennes.enst-bretagne.fr>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6ffdee8af20de249c24731d8414917d3
Content-Transfer-Encoding: 7bit
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Francis Dupont wrote:

>  In your previous mail you wrote:
> 
>    Hello to dhaad-harmful contributors and supporters.
>    
>    > - it uses ICMP across the Internet. The trend has been to turn off ICMP
>    > except for local link communications, to avoid convenient vehicles for
>    > DoS. I know that one can theoretically configure the firewall to filter
>    > on the ICMP message type field, but it is easier just to drop it at the
>    > firewall than to try to figure out what ICMP is good and what is bad.
>    
>    I think the argument 'some protocol may be blocked by some firewalls'
>    for considering some protocol harmful and support other protocols
>    instead, is probably a little bit flawed.
>    
> => unfortunately ICMP is commonly blocked so it is a real operational
> issue. Look at draft-davies-v6ops-icmpv6-filtering-bcp-00.txt...

Thanks, I've looked over the draft.  It provides BCP advice to firewalls
admins as to which ICMPv6 type messages to filter or not, based on an
evaluation of the risks associated with each.

>    In a sense, the strongest firewalls of some operators block all that is
>    not HTTP, and I imagine they can even block HTTP-tunnelled traffic.
>    Which would suggest that only a cleartext HTTP-based HA Discovery may
>    have the highest chances of getting through.
>    
> => BTW DNS is not filtered out.

Well, depends.

In a WiFi deployment, DNS content is filtered (only one IP address is
resolved) prior to payment.  In other WiFi deployment, even after
payment, only the http access is allowed, with a proxy.  In that, the
http proxy performs name resolution for the MN and the MN is not allowed
to perform locally name resolution.  Meaning a DNS-based HAD won't work,
only and http-based HAD would.

Some other operator forces the MN to use a local DNS Server and forbid
the use of a DNS server outside that operator's domain.

I'd go as far as to say that if an operator forces the MN into a local
DNS Server then it may as well force the MN into a local HA as well,
i.e. forbiding the MN to use HAs outside that operator's domain.

I would agree that DNS "is not filtered out" in general but I'd also say
there are many exceptions to that.

>    In another sense, if some operators will open ports (and import SRV
>    records in their DNS, and provide _full_ DNS service to MNs) because
>    some IETF Document says so, then the proposed DNS-based HAD scheme may
>    indeed work and I support its idea.
>    
> => DNS-based HAD scheme has many advantages. For some (including me)
> it can be made secure, for some others it is the ICMP filtering, etc...
> 
>    > - AFIK, there is no way currently standardized to securely update
>    > anycast routing except to manually insert host routes into the subnet
>    > router handling the anycast address. So maintaining an anycast address
>    > would require extra maintenance effort, manually inserting and deleting
>    > the routes when HAs are added or deleted.
>    
> => the routing stuff is in order to make the anycast destination a known
> and stable box.
> 
>    I think the IPsec shortcoming with respect to anycast, and the inability
>    to securely update anycast routes may not play an important role in
>    discarding the current DHAAD.
>    
>    For example, I wonder whether the following normal DHAAD procedure would
>    be secure enough:
>    
>    -MN sends DHAAD Request to the anycast address and has SA with that
>     anycast address (which is prefix:fdff:ffff:ffff:fffe/128).
> 
> => currently it is not possible to establish a symmetric IPsec SA
> pair with an anycast address.
> 
>    -only one HA replies back to MN, IP packet having
>     src=prefix:fdff:ffff:ffff:fffe/128
>    -the HAs communicate with each other with RAs and collaboratively build
>     a coherent list of HAs ordered with some priority.
>    
>    With that scheme I think there is no need to manually insert or delete
>    routes when HAs are added or deleted.
>    
>    Would this be secure enough?
> 
> => it is a matter of state: an unsecure DHAAD doesn't give a security
> disaster...
> 
>    Would IPsec allow SAs whose IP address is an anycast address?
> 
> => no because an anycast can't be used as a source address.

And if it could, would the DHAAD be considered as IPsec-secureable?

I imagine that as the HA-anycast address has been reserved, there may be
a possibility to reserve a "HA-discovery" address in the form
prefix:feff:ffff:ffff:fffe that would be an IP address anycast-like but
not quite anycast, such as to be accepted by IPsec.

> => the two questions are:
>  - should we keep a DHAAD mechanism or HA assignment is the right thing
>    to do?

Both ideas have appeal to me.  Both could be supported by some
argumentation.  I have implemented one of them and that's why I tend to
support it (but it won't be the first time I implement something in an
RFC only to see it discarded later :-).

>  - is the DNS-based DHAAD mechanism better enough to replace the ICMP-base
>    one?

Right, that is a good question.  As presented until now, the DNS-based
seems to have some better aspects than the ICMP-based.

Alex


> 
> Regards
> 
> Francis.Dupont@enst-bretagne.fr


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



From mip6-bounces@ietf.org Mon Oct 24 10:37:43 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EU3SJ-0005T6-GO; Mon, 24 Oct 2005 10:37:43 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EU3SI-0005T1-3L
	for mip6@megatron.ietf.org; Mon, 24 Oct 2005 10:37:42 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12965
	for <mip6@ietf.org>; Mon, 24 Oct 2005 10:37:27 -0400 (EDT)
Received: from motgate3.mot.com ([144.189.100.103])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EU3f3-0005rr-28
	for mip6@ietf.org; Mon, 24 Oct 2005 10:50:54 -0400
Received: from az33exr02.mot.com (az33exr02.mot.com [10.64.251.232])
	by motgate3.mot.com (8.12.11/Motgate3) with ESMTP id j9OErFKO027491;
	Mon, 24 Oct 2005 07:53:19 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by az33exr02.mot.com (8.13.1/8.13.0) with ESMTP id j9OEisoT002146;
	Mon, 24 Oct 2005 09:44:55 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id 9208F865980; Mon, 24 Oct 2005 16:37:29 +0200 (CEST)
Message-ID: <435CF1A9.8030709@motorola.com>
Date: Mon, 24 Oct 2005 16:37:29 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: "Soliman, Hesham" <H.Soliman@flarion.com>
Subject: Re: [Mip6] I-D ACTION:draft-ietf-mip6-nemo-v4traversal-00.txt
References: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCD76@ftmailserver.flariontech.com>
In-Reply-To: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCD76@ftmailserver.flariontech.com>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Content-Transfer-Encoding: 7bit
Cc: mip6@ietf.org, Keiichi SHIMA <keiichi@iijlab.net>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Soliman, Hesham wrote:
> Hello Keiichi, 
> 
> Thanks for the comments. Responses inline.
> 
>  > 
>  > - The draft seems discussing two separate issues.
>  > 
>  > I think, v4traversal and supporting IPv4 HoA/network are different
>  > issues.  Don't we need to think an scenario, which doesn't need
>  > v4traversal but need IPv4 communication, and vice versa?
> 
> => Absolutely. That's why the draft allows a node to use an IPv4
> home address whether it's in an IPv4 or an IPv6 network.

And don't you think that there is a need for a node in a moving network
to use IPv4 fixed address and the Mobile Router to do NEMO and no MIP6?

Alex

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



From mip6-bounces@ietf.org Mon Oct 24 10:40:21 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EU3Ur-000692-13; Mon, 24 Oct 2005 10:40:21 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EU3Up-00068u-A2
	for mip6@megatron.ietf.org; Mon, 24 Oct 2005 10:40:19 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13071
	for <mip6@ietf.org>; Mon, 24 Oct 2005 10:40:04 -0400 (EDT)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EU3hY-0005vA-9a
	for mip6@ietf.org; Mon, 24 Oct 2005 10:53:31 -0400
Received: from il06exr04.mot.com (il06exr04.mot.com [129.188.137.134])
	by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id j9OEq0YN029156;
	Mon, 24 Oct 2005 07:52:05 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by il06exr04.mot.com (8.13.1/8.13.0) with ESMTP id j9OEm4sl007209;
	Mon, 24 Oct 2005 09:48:04 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id 6E65F865980; Mon, 24 Oct 2005 16:40:05 +0200 (CEST)
Message-ID: <435CF245.4010506@motorola.com>
Date: Mon, 24 Oct 2005 16:40:05 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: Keiichi SHIMA <keiichi@iijlab.net>
Subject: Re: [Mip6] I-D ACTION:draft-ietf-mip6-nemo-v4traversal-00.txt
References: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCD76@ftmailserver.flariontech.com>
	<20051024.191134.27213453.keiichi@iijlab.net>
In-Reply-To: <20051024.191134.27213453.keiichi@iijlab.net>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Content-Transfer-Encoding: 7bit
Cc: H.Soliman@flarion.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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Keiichi SHIMA wrote:

> Hello Hesham,
> 
> Please find my comments inline..
> 
> From: "Soliman, Hesham" <H.Soliman@flarion.com>
> Date: Thu, 20 Oct 2005 23:25:46 -0400
> 
>> > 
>> > - The draft seems discussing two separate issues.
>> > 
>> > I think, v4traversal and supporting IPv4 HoA/network are different
>> > issues.  Don't we need to think an scenario, which doesn't need
>> > v4traversal but need IPv4 communication, and vice versa?
>>
>>=> Absolutely. That's why the draft allows a node to use an IPv4
>>home address whether it's in an IPv4 or an IPv6 network.
>>
>>  In the
>> > previous discussion (two months ago in the MIP6 mailing list, maybe),
>> > you mentioned that separating these two issues add complexity.  
>>
>>=> Yes.
>>
>>   But
>> > I'm afraid I still don't understand what complexity is added when we
>> > divide the above two issues.  It should be helpful if you could show
>> > some examples.
>>
>>=> What I was referring to before was writing two different specs in 
>>parallel. It's a matter of organisation and working out dependencies 
>>between documents. One solution can easily address having IPv4 home 
>>or coa as you can see from this document. 
> 
> 
> My point is that having IPv4 CoA and Having IPv4 HoA is different
> things and they are orthogonal.  (I think my explanation is not
> good...)
> 
> Let's consider to implement IPv6 mobile node which supports IPv4
> access network, but don't support IPv4 HoA.  Which RFC should we
> support?  If we continue to discuss the different things in one draft,
> we must also make it clear which section(s) is necessary to implement
> what feature.  But I feel it is a bad idea to specify features in such
> a manner.  Easier way to make it clear is to divide the specification...

Right, I also think the current draft still tries to address too many
scenarios.  I would keep in it only running MIP6 over a v4-only access
network, with NAT traversal.  I would separate from it all NEMO aspects
be it v4 or v6, I would separate also giving v4-home-address through
MIP6 through v4-only access network.

Alex


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



From mip6-bounces@ietf.org Mon Oct 24 10:40:25 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EU3Uv-00069X-ME; Mon, 24 Oct 2005 10:40:25 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EU3Ut-00069S-HA
	for mip6@megatron.ietf.org; Mon, 24 Oct 2005 10:40:23 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13074
	for <mip6@ietf.org>; Mon, 24 Oct 2005 10:40:09 -0400 (EDT)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EU3hf-0005vS-E9
	for mip6@ietf.org; Mon, 24 Oct 2005 10:53:35 -0400
Received: from il06exr02.mot.com (il06exr02.mot.com [129.188.137.132])
	by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id j9OEqFiB029194
	for <mip6@ietf.org>; Mon, 24 Oct 2005 07:52:15 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by il06exr02.mot.com (8.13.1/8.13.0) with ESMTP id j9OEmwe4010443
	for <mip6@ietf.org>; Mon, 24 Oct 2005 09:48:58 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP id D72C8865980
	for <mip6@ietf.org>; Mon, 24 Oct 2005 16:40:20 +0200 (CEST)
Message-ID: <435CF254.6050508@motorola.com>
Date: Mon, 24 Oct 2005 16:40:20 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: Mobile IPv6 Mailing List <mip6@ietf.org>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4
Content-Transfer-Encoding: 7bit
Subject: [Mip6] More comments on draft-ietf-mip6-nemo-v4traversal-00.txt
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Hello to authors of draft-ietf-mip6-nemo-v4traversal-00.txt,

Thanks for providing this draft.  I understand it is the result of the
mip6trans DT and wanted to say thanks to the team as a whole.

I have some comments.

> The current Mobile IPv6 specification and [NEMO] do not allow mobile
>  nodes to use an IPv4 home address or prefix, respectively.

That is largely true.  Note though that recently there is a personal
draft on NEMO for IPv4 home prefix that uses MIP4 and no MIP6.

> Mobile IPv6 offers a number of improvements over Mobile IPv4, mainly
>  due to capabilities inherited from IPv6. For instance, route 
> optimization and Dynamic home agent discovery can only be achieved 
> with Mobile IPv6.

Maybe exemplify MIP6 superiority on MIP4 by something else than DHAAD,
itself being questioned by the dhaad-harmful discussions, and
acknowledged by this draft's section 2.1.

I mean, on one hand the draft says DHAAD is an advantage of MIP6 over
MIP4 and on antoher hand same draft says HA Discovery is not really
specified.

RO is another case.  There are no widely deployed RO-enabled CNs while
IPv4 non-RO CNs are plenty, so one can't really claim MIP6 is superior
to MIP4 because it has RO.

> We also assume that the Home Agent is always reachable through a 
> globally unique IPv4 address.

I would like a DSMIPv6 solution to assume that the HAv6 is only
reachable by its v6 address.  That would help widespread adoption of
IPv6 by offering one less dependency on IPv4.

In case the MN has v4-only applications on it, and needs to continuously
accessed IPv4 Home Address then I suggest porting these applications to
IPv6.  In this case MIP6 is used as an advantage of IPv6: if an
application is ported from IPv4 to IPv6 then it gets ability to run
uninterrupted and use a permanent Home Address, and does not need MIP4.

> For DNS lookup by service, the SRV record defined in [BOOT] is 
> reused.  For instance, if the service name is "mip6ha" and the 
> protocol name is "ipv6" for the SRV record, the mobile node SHOULD 
> send a DNS request with the QNAME set to "mip6ha.ipv6.example.com". 
> The response should contain the home agent's FQDN(s) and may have the
>  corresponding 'AAAA' and 'A' records enclosed as well.

This is another discussion, but I just mention it here.  This method for
HAD does not specify a means for the HAs to co-operate with each other
to establish their preferences.  With DNS-based it is left entirely to
the MN to choose among the HAs addresses.

> 2.3.1 Foreign network supports IPv6

This scenario is not described in the initial list of scenarios at 1.2
"Scenarios considered by this specification".  Section 1.2 only lists
access networks as IPv4.

> 4.1. NAT detection and traversal

This section is very important for proper working of NAT detection and
traversal.  However, it has some issues right now.

> The binding acknowledgement, and all future packets are then
> encapsulated in UDP and IPv4. The source address in the IPv4 header
> is the IPv4 address of the home agent. The destination address is the
> IPv4 address received in the IPv4 header encapsulating the binding
> update (this address will be different from the IPv4 care-of address
> if a NAT were present in the path).
> 
> Upon receiving the binding acknowledgement with the NAT detection 
> option, the mobile node sets the tunnel to the home agent to UDP 
> encapsulation.

Actually there is more to happen between the two paragraphs.  Current
implemented NATs have no idea about this draft, so they don't currently
implement it.

A NAT needs to know a way for forwarding the BAck from the HA to MN.
The v4 dst address in that UDPv4-encapsulated BAck is the NAT address
itself.  In order for NAT to forward the packet to MN (and re-write the
IPv4 dst address) it sometimes uses port numbers.  That's why UDP.  Or,
there's no mention of UDP numbers in this section.

And, when port numbers are used to facilitate ip address rewriting by
NAT, they are not fixed, they're dynamically changing.  Which would
demand more enhancement to this section.

> "Dual Stack Mobile IPv6 (DSMIPv6)"

The title may not be very adapted.  It makes one somehow think about
Dual-Stack MIP4 and MIP6, since 'dual-stack' is usually 'IPv4 stack and
IPv6 stack'.  Or, the mechanism proposed is more about enhancing MIP6
with some v4 features.  Maybe "v4-enhanced MIP6" would be better.

Alex



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



From mip6-bounces@ietf.org Mon Oct 24 10:44:34 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EU3Yw-0006qH-Ss; Mon, 24 Oct 2005 10:44:34 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EU3Yw-0006qC-6E
	for mip6@megatron.ietf.org; Mon, 24 Oct 2005 10:44:34 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13246
	for <mip6@ietf.org>; Mon, 24 Oct 2005 10:44:19 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EU3lh-00062p-Vf
	for mip6@ietf.org; Mon, 24 Oct 2005 10:57:46 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id j9OEhq811743; Mon, 24 Oct 2005 16:43:52 +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
	j9OEhqCk082214; Mon, 24 Oct 2005 16:43:52 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200510241443.j9OEhqCk082214@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Alexandru Petrescu <alexandru.petrescu@motorola.com>
Subject: Re: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt 
In-reply-to: Your message of Mon, 24 Oct 2005 15:44:23 +0200.
	<435CE537.3070900@motorola.com> 
Date: Mon, 24 Oct 2005 16:43:52 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b280b4db656c3ca28dd62e5e0b03daa8
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   >    In a sense, the strongest firewalls of some operators block all that is
   >    not HTTP, and I imagine they can even block HTTP-tunnelled traffic.
   >    Which would suggest that only a cleartext HTTP-based HA Discovery may
   >    have the highest chances of getting through.
   >    
   > => BTW DNS is not filtered out.
   
   Well, depends.
   
   In a WiFi deployment, DNS content is filtered (only one IP address is
   resolved) prior to payment.

=> usually it is only partially filtered because the purpose is to
redirect first HTTP connection, not to make it to fail.

   In other WiFi deployment, even after
   payment, only the http access is allowed, with a proxy.  In that, the
   http proxy performs name resolution for the MN and the MN is not allowed
   to perform locally name resolution.  Meaning a DNS-based HAD won't work,
   only and http-based HAD would.
   
=> proxy only doesn't work well with HTTPS... and HTTP-based HAD
is not very computer oriented (as HTTP is user oriented).

   Some other operator forces the MN to use a local DNS Server and forbid
   the use of a DNS server outside that operator's domain.
   
=> it doesn't matter if the local DNS server is recursive (if it is not
it can't offer an useful service).

   I'd go as far as to say that if an operator forces the MN into a local
   DNS Server then it may as well force the MN into a local HA as well,
   i.e. forbiding the MN to use HAs outside that operator's domain.
   
=> we speak about Internet service, not on-line services connected
to the Internet, even the Internet service can be pretty bad (spurious
filtering, etc).

   I would agree that DNS "is not filtered out" in general but I'd also say
   there are many exceptions to that.

=> so this is a disgression, isn't it?
   
   > => no because an anycast can't be used as a source address.
   
   And if it could, would the DHAAD be considered as IPsec-secureable?
   
=> no because the responder should be stable too.

   > => the two questions are:
   >  - should we keep a DHAAD mechanism or HA assignment is the right thing
   >    to do?
   
   Both ideas have appeal to me.  Both could be supported by some
   argumentation.

=> this is why we should have this discussion.

   I have implemented one of them and that's why I tend to
   support it (but it won't be the first time I implement something in an
   RFC only to see it discarded later :-).
   
=> IMHO HA assignement is far better but there is not yet a mechanism
providing it *and* applicable in the general case.

   >  - is the DNS-based DHAAD mechanism better enough to replace the ICMP-base
   >    one?
   
   Right, that is a good question.

=> thanks

   As presented until now, the DNS-based
   seems to have some better aspects than the ICMP-based.
   
=> so you seem to support the idea developed in the I-D.
   
Regards

Francis.Dupont@enst-bretagne.fr

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



From mip6-bounces@ietf.org Mon Oct 24 10:59:35 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EU3nT-00047x-Hx; Mon, 24 Oct 2005 10:59:35 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EU3nM-00046M-QW
	for mip6@megatron.ietf.org; Mon, 24 Oct 2005 10:59:33 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14094
	for <mip6@ietf.org>; Mon, 24 Oct 2005 10:59:14 -0400 (EDT)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EU407-0006ZG-JK
	for mip6@ietf.org; Mon, 24 Oct 2005 11:12:41 -0400
Received: from il06exr04.mot.com (il06exr04.mot.com [129.188.137.134])
	by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id j9OFBEA7003468;
	Mon, 24 Oct 2005 08:11:14 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by il06exr04.mot.com (8.13.1/8.13.0) with ESMTP id j9OF7J0X016385;
	Mon, 24 Oct 2005 10:07:19 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id F3216865980; Mon, 24 Oct 2005 16:59:19 +0200 (CEST)
Message-ID: <435CF6C7.50600@motorola.com>
Date: Mon, 24 Oct 2005 16:59:19 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
Subject: Re: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
References: <200510241443.j9OEhqCk082214@givry.rennes.enst-bretagne.fr>
In-Reply-To: <200510241443.j9OEhqCk082214@givry.rennes.enst-bretagne.fr>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86
Content-Transfer-Encoding: 7bit
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Francis Dupont wrote:

> In your previous mail you wrote:
> 
>> In a sense, the strongest firewalls of some operators block all
>> that is not HTTP, and I imagine they can even block HTTP-tunnelled
>> traffic. Which would suggest that only a cleartext HTTP-based HA
>> Discovery may have the highest chances of getting through.
>> 
>> => BTW DNS is not filtered out.
> 
> Well, depends.
> 
> In a WiFi deployment, DNS content is filtered (only one IP address is
>  resolved) prior to payment.
> 
> => usually it is only partially filtered because the purpose is to 
> redirect first HTTP connection, not to make it to fail.
> 
> In other WiFi deployment, even after payment, only the http access is
> allowed, with a proxy.  In that, the http proxy performs name
> resolution for the MN and the MN is not allowed to perform locally
> name resolution.  Meaning a DNS-based HAD won't work, only and
> http-based HAD would.
> 
> => proxy only doesn't work well with HTTPS... and HTTP-based HAD is
> not very computer oriented (as HTTP is user oriented).
> 
> Some other operator forces the MN to use a local DNS Server and
> forbid the use of a DNS server outside that operator's domain.
> 
> => it doesn't matter if the local DNS server is recursive (if it is
> not it can't offer an useful service).
> 
> I'd go as far as to say that if an operator forces the MN into a
> local DNS Server then it may as well force the MN into a local HA as
> well, i.e. forbiding the MN to use HAs outside that operator's
> domain.
> 
> => we speak about Internet service, not on-line services connected to
> the Internet, even the Internet service can be pretty bad (spurious 
> filtering, etc).
> 
> I would agree that DNS "is not filtered out" in general but I'd also
> say there are many exceptions to that.
> 
> => so this is a disgression, isn't it?

Well, I don't necessarily intend to deviate discussion.  I think I
intended to say that relying on DNS because ICMP is usually filtered is
probably not a useful argument.

An argument in support of DNS-based HAD could be that it does not
require HA to implement DHAAD, and probably few MIP6 implementations do
DHAAD.

>> => no because an anycast can't be used as a source address.
> 
> And if it could, would the DHAAD be considered as IPsec-secureable?
> 
> => no because the responder should be stable too.

Well, IPsec works for MN and HA right?  So if all HAs on same link have
a common IPsec-friendly anycast-like IPv6 address (in addition to their
unique global IPv6 address) then IPsec for DHAAD may work too, no?

>> => the two questions are: - should we keep a DHAAD mechanism or HA
>> assignment is the right thing to do?
> 
> Both ideas have appeal to me.  Both could be supported by some 
> argumentation.
> 
> => this is why we should have this discussion.
> 
> I have implemented one of them and that's why I tend to support it
> (but it won't be the first time I implement something in an RFC only
> to see it discarded later :-).
> 
> => IMHO HA assignement is far better but there is not yet a mechanism
>  providing it *and* applicable in the general case.

I agree with that.

>> - is the DNS-based DHAAD mechanism better enough to replace the
>> ICMP-base one?
> 
> Right, that is a good question.
> 
> => thanks
> 
> As presented until now, the DNS-based seems to have some better
> aspects than the ICMP-based.
> 
> => so you seem to support the idea developed in the I-D.

Provided that there is no interest in IPsec-friendly non-anycast DHAAD -
yes I support the idea developped in this I-D.

Alex


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



From mip6-bounces@ietf.org Mon Oct 24 11:13:18 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EU40k-0000F7-Ii; Mon, 24 Oct 2005 11:13:18 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EU40f-0008V2-3n
	for mip6@megatron.ietf.org; Mon, 24 Oct 2005 11:13:17 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA14798
	for <mip6@ietf.org>; Mon, 24 Oct 2005 11:12:55 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EU4DN-00070W-7i
	for mip6@ietf.org; Mon, 24 Oct 2005 11:26:22 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id j9OFCnF14745; Mon, 24 Oct 2005 17:12: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
	j9OFCnYV082445; Mon, 24 Oct 2005 17:12:49 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200510241512.j9OFCnYV082445@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Alexandru Petrescu <alexandru.petrescu@motorola.com>
Subject: Re: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt 
In-reply-to: Your message of Mon, 24 Oct 2005 16:59:19 +0200.
	<435CF6C7.50600@motorola.com> 
Date: Mon, 24 Oct 2005 17:12:49 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   > => no because the responder should be stable too.
   
   Well, IPsec works for MN and HA right?

=> yes even if some people tried to change that (:-).

   So if all HAs on same link have
   a common IPsec-friendly anycast-like IPv6 address (in addition to their
   unique global IPv6 address) then IPsec for DHAAD may work too, no?
   
 => this is more an argument for HA-switch (another way to provide
HA assignment)...
The issue with the anycast-like address is the responder must be always
the same box in order to use correctly IPsec. IMHO the best way to
protect current DHAAD is per exchange and not per communication
but the real issue is the effort doesn't worth it.

   Provided that there is no interest in IPsec-friendly non-anycast DHAAD -

=> if you remove the anycast aspect something like the HA-switch will
be better.

   yes I support the idea developped in this I-D.
   
=> thanks

Francis.Dupont@enst-bretagne.fr

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



From mip6-bounces@ietf.org Mon Oct 24 11:21:03 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EU48F-0001tU-A3; Mon, 24 Oct 2005 11:21:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EU48D-0001tN-VI
	for mip6@megatron.ietf.org; Mon, 24 Oct 2005 11:21:02 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15120
	for <mip6@ietf.org>; Mon, 24 Oct 2005 11:20:49 -0400 (EDT)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EU4Kz-0007En-6d
	for mip6@ietf.org; Mon, 24 Oct 2005 11:34:14 -0400
Received: from il06exr02.mot.com (il06exr02.mot.com [129.188.137.132])
	by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id j9OFWngA008073
	for <mip6@ietf.org>; Mon, 24 Oct 2005 08:32:49 -0700 (MST)
Received: from de01exm69.ds.mot.com (de01exm69.am.mot.com [10.176.8.25])
	by il06exr02.mot.com (8.13.1/8.13.0) with ESMTP id j9OFTWHe005197
	for <mip6@ietf.org>; Mon, 24 Oct 2005 10:29:32 -0500 (CDT)
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] draft-dupont-mip6-dhaadharmful-00.txt 
Date: Mon, 24 Oct 2005 11:20:54 -0400
Message-ID: <0B40B6F9CB990B428819561A2A55613A103BA9@de01exm69.ds.mot.com>
Thread-Topic: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt 
Thread-Index: AcXYmAy19R9rZjd5Q6uwsLFw5TPmRAAFeDcg
From: "Narayanan Vidya-CVN065" <vidya@motorola.com>
To: "Francis Dupont" <Francis.Dupont@enst-bretagne.fr>,
	"Petrescu Alexandru-AAP021" <alexandru.petrescu@motorola.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Content-Transfer-Encoding: quoted-printable
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

>   =20
> =3D> the two questions are:
>  - should we keep a DHAAD mechanism or HA assignment is the=20
> right thing
>    to do?
>  - is the DNS-based DHAAD mechanism better enough to replace=20
> the ICMP-base
>    one?
>=20

These are good questions. I believe that a DNS-based mechanism is
largely better than an ICMP-based mechansim. For those who wish to
secure the operation, at least an option is available. Whether DNSSEC
will be widely deployed is a separate question, but at least, it is an
option. Also, it moves away from having to configure the home network
prefix and removes the limitation of dynamic HA assignment within the
same subnet, both of which are big pluses in my mind.=20

Regards,
Vidya

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



From mip6-bounces@ietf.org Mon Oct 24 11:25:49 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EU4Cr-0002lX-Ga; Mon, 24 Oct 2005 11:25:49 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EU4Cq-0002lO-CH
	for mip6@megatron.ietf.org; Mon, 24 Oct 2005 11:25:48 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15356
	for <mip6@ietf.org>; Mon, 24 Oct 2005 11:25:35 -0400 (EDT)
Received: from cluster-d.mailcontrol.com ([217.69.20.190]
	helo=rly37d.srv.mailcontrol.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EU4Pa-0007NP-H5
	for mip6@ietf.org; Mon, 24 Oct 2005 11:39:01 -0400
Received: from hhe500-02.hbg.de.pan.eu (gate.eu.panasonic.com [194.173.20.12])
	by rly37d.srv.mailcontrol.com (MailControl) with SMTP id
	j9OFPUJ4016745; Mon, 24 Oct 2005 16:25:30 +0100
Received: from eundadmi01.pan.eu(10.100.96.64) by hhe500-02.hbg.de.pan.eu via
	smtp id 75a1_2db34ee4_44a3_11da_95cb_0030482aac25;
	Mon, 24 Oct 2005 17:30:58 +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 2005102417252844-25324 ;
	Mon, 24 Oct 2005 17:25:28 +0200 
Received: from localhost ([127.0.0.1]) by VPN-MRelay-01.PRDCG.Panasonic.de;
	Mon, 24 Oct 2005 17:27:36 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
MIME-Version: 1.0
Subject: RE: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt 
Thread-Topic: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt 
Thread-Index: AcXYqXbXIA/i8BXYScS1SYiWXuH9KAAAVacg
To: <Francis.Dupont@enst-bretagne.fr>,
	"Alexandru Petrescu" <alexandru.petrescu@motorola.com>
Message-ID: <4D2F935F08D41A4C8866693F4F0D7C4F58E63B@lan-ex-01.panasonic.de>
Date: Mon, 24 Oct 2005 17:25:22 +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-05-40-01 (www.mailcontrol.com) on 10.68.0.147
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Content-Transfer-Encoding: quoted-printable
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Hi Francis, Alex,

>    Both ideas have appeal to me.  Both could be supported by some
>    argumentation.
>=20
> =3D> this is why we should have this discussion.

I agree that DNS-based DHAAD can be more secure, but one advantage of
anycast-based DHAAD I can see is that load balancing is better supported
since load conditions can be considered faster (probably cannot be
distributed fast enough in DNS).

> =3D> IMHO HA assignement is far better but there is not yet a =
mechanism
> providing it *and* applicable in the general case.

Security-wise yes. But which entity assigns the HA? And how do you
discover this HA assignment entity? And what about the signaling
overhead then? And the signaling overhead can be pretty high, e.g., if
MN first needs to request DNS to discover assignment entity and
subsequently establishes SA with assignment entity, gets HA assigned and
finally establishes SA with this HA.

Wouldn't it be possible to integrate HA discovery and assignment somehow
in an IKEv2 exchange, similar as HoA assignment is integrated in IKE
exchange in the bootstrapping solution? E.g., the first IKE message
(IKE_SA_INIT) sent by MN would have anycast address as destination
address (reply and all other IKE messages use unicast addresses as
source/destination) and the Configuration Payload in the IKE_AUTH may
contain an HA address for assignment to MN (only used if the HA that
received the anycast IKE_SA_INIT shall not be used, e.g., because this
HA is overloaded).=20

>=20
>    >  - is the DNS-based DHAAD mechanism better enough to=20
> replace the ICMP-base
>    >    one?

What about the alternative to change the transport protocol, e.g.,
UDP-based instead of ICMP-based anycast DHAAD?

> - AFIK, there is no way currently standardized to securely update
> anycast routing except to manually insert host routes into the subnet
> router handling the anycast address. So maintaining an anycast address
> would require extra maintenance effort, manually inserting and
deleting
> the routes when HAs are added or deleted.

Interesting point, but isn't such a mechnism needed for almost all
anycast-based protocols? I.e., isn't there a need for such a
standardized mechanism anyway?

Regards,

Kilian


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



From mip6-bounces@ietf.org Mon Oct 24 11:34:29 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EU4LF-0006K7-Il; Mon, 24 Oct 2005 11:34:29 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EU4LD-0006Jx-AZ
	for mip6@megatron.ietf.org; Mon, 24 Oct 2005 11:34:27 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15792
	for <mip6@ietf.org>; Mon, 24 Oct 2005 11:34:14 -0400 (EDT)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EU4Xz-0007gh-Mh
	for mip6@ietf.org; Mon, 24 Oct 2005 11:47: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 j9OFkFEP010808;
	Mon, 24 Oct 2005 08:46:15 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by il06exr02.mot.com (8.13.1/8.13.0) with ESMTP id j9OFgwMm013319;
	Mon, 24 Oct 2005 10:42:58 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id D0D20865980; Mon, 24 Oct 2005 17:34:20 +0200 (CEST)
Message-ID: <435CFEFC.3040405@motorola.com>
Date: Mon, 24 Oct 2005 17:34:20 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: Narayanan Vidya-CVN065 <vidya@motorola.com>
Subject: Re: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
References: <0B40B6F9CB990B428819561A2A55613A103BA9@de01exm69.ds.mot.com>
In-Reply-To: <0B40B6F9CB990B428819561A2A55613A103BA9@de01exm69.ds.mot.com>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Content-Transfer-Encoding: 7bit
Cc: mip6@ietf.org, Kilian Weniger <Kilian.Weniger@eu.panasonic.com>,
	Francis Dupont <Francis.Dupont@enst-bretagne.fr>,
	James Kempf <Kempf@docomolabs-usa.com>,
	Petrescu Alexandru-AAP021 <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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Narayanan Vidya-CVN065 wrote:
>> 
>> => the two questions are: - should we keep a DHAAD mechanism or HA
>>  assignment is the right thing to do? - is the DNS-based DHAAD 
>> mechanism better enough to replace the ICMP-base one?
>> 
> 
> These are good questions. I believe that a DNS-based mechanism is 
> largely better than an ICMP-based mechansim. For those who wish to 
> secure the operation, at least an option is available. Whether DNSSEC
>  will be widely deployed is a separate question, but at least, it is
>  an option.

It follows, yes.

Let's compare to RO.  RO is a solution when MN and CN can't use
IPsec/IKE because PKI may not be deployed everywhere.

Same with non-anycast DHAAD, probably.  DNS-based HAD is a solution when
DNSSEC is deployed everywhere, otherwise use non-anycast DHAAD, no?

> Also, it moves away from having to configure the home network prefix

Yes, but it enforces the configuration of (textual variations of)
"home.com".  A real advantage for DNS-based easying the bootstrapping
would have been if there was nothing to pre-configure.

> and removes the limitation of dynamic HA assignment within the same 
> subnet, both of which are big pluses in my mind.

One may see multiple-subnet HAs for a single MN as a big plus, but it is
not at all clear whether a MN could continue using the same HoA after
changing its HA from one subnet to another.  And, if when the MN
switches its HA on another link is changing its HoA as well - it is
equivalent to running DHAAD with a different subnet prefix.

Alex

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



From mip6-bounces@ietf.org Mon Oct 24 11:42:52 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EU4TM-0007tx-AU; Mon, 24 Oct 2005 11:42:52 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EU4TK-0007ts-U1
	for mip6@megatron.ietf.org; Mon, 24 Oct 2005 11:42:51 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16110
	for <mip6@ietf.org>; Mon, 24 Oct 2005 11:42:38 -0400 (EDT)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EU4g5-0007uD-Eo
	for mip6@ietf.org; Mon, 24 Oct 2005 11:56:03 -0400
Received: from il06exr03.mot.com (il06exr03.mot.com [129.188.137.133])
	by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id j9OFsXXM012413;
	Mon, 24 Oct 2005 08:54:33 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by il06exr03.mot.com (8.13.1/8.13.0) with ESMTP id j9OFqZHT027439;
	Mon, 24 Oct 2005 10:52:38 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id 8728C865980; Mon, 24 Oct 2005 17:42:35 +0200 (CEST)
Message-ID: <435D00EB.1080707@motorola.com>
Date: Mon, 24 Oct 2005 17:42:35 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
Subject: Re: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
References: <200510241512.j9OFCnYV082445@givry.rennes.enst-bretagne.fr>
In-Reply-To: <200510241512.j9OFCnYV082445@givry.rennes.enst-bretagne.fr>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Content-Transfer-Encoding: 7bit
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Francis Dupont wrote:

> In your previous mail you wrote:
> 
>> => no because the responder should be stable too.
> 
> Well, IPsec works for MN and HA right?
> 
> => yes even if some people tried to change that (:-).
> 
> So if all HAs on same link have a common IPsec-friendly anycast-like
> IPv6 address (in addition to their unique global IPv6 address) then
> IPsec for DHAAD may work too, no?
> 
> => this is more an argument for HA-switch (another way to provide HA
> assignment)...

Thanks, where is HA-switch discussed, drafted?

> The issue with the anycast-like address is the responder must be
> always the same box in order to use correctly IPsec.

I don't buy into that.  It's like saying that because of IPsec two boxes
aren't allowed to have same IPv6 address.  It's also ignoring that the
"unique IP address per box" concept no longer exists since "server farms
and blades", "IP over VIA" and "modem connected to PDA" got widespread use.

> IMHO the best way to protect current DHAAD is per exchange and not
> per communication but the real issue is the effort doesn't worth it.

exchange vs. communication?

Alex


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



From mip6-bounces@ietf.org Mon Oct 24 11:46:16 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EU4We-0001En-FP; Mon, 24 Oct 2005 11:46:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EU4Wb-0001AY-Vn
	for mip6@megatron.ietf.org; Mon, 24 Oct 2005 11:46:14 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16327
	for <mip6@ietf.org>; Mon, 24 Oct 2005 11:46:01 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EU4jM-000819-Rj
	for mip6@ietf.org; Mon, 24 Oct 2005 11:59:26 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id j9OFjUf18341; Mon, 24 Oct 2005 17:45: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
	j9OFjUKx082679; Mon, 24 Oct 2005 17:45:30 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200510241545.j9OFjUKx082679@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: "Kilian Weniger" <Kilian.Weniger@eu.panasonic.com>
Subject: Re: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt 
In-reply-to: Your message of Mon, 24 Oct 2005 17:25:22 +0200.
	<4D2F935F08D41A4C8866693F4F0D7C4F58E63B@lan-ex-01.panasonic.de> 
Date: Mon, 24 Oct 2005 17:45:30 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
Cc: 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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   I agree that DNS-based DHAAD can be more secure, but one advantage of
   anycast-based DHAAD I can see is that load balancing is better supported
   since load conditions can be considered faster (probably cannot be
   distributed fast enough in DNS).
   
=> IMHO load balancing should not be provided by a DHAAD mechanism
but by HA assignment or HA-switch.

   > => IMHO HA assignement is far better but there is not yet a mechanism
   > providing it *and* applicable in the general case.
   
   Security-wise yes. But which entity assigns the HA?

=> the network (the MSP in the bootstrapping terminology).

   And how do you discover this HA assignment entity?

=> this is something to specify with the whole HA assignment mechanism.
We don't discuss about a particular mechanism but about the function.

   And what about the signaling
   overhead then? And the signaling overhead can be pretty high, e.g., if
   MN first needs to request DNS to discover assignment entity and
   subsequently establishes SA with assignment entity, gets HA assigned and
   finally establishes SA with this HA.
   
   Wouldn't it be possible to integrate HA discovery and assignment somehow
   in an IKEv2 exchange,

=> this is the Security Gateway discovery issue. It is in the scope
of the IPsec WG but I am afraid we should not wait for a solution
from them, on another hand it has to be secure and IPsec people
should be better...

   similar as HoA assignment is integrated in IKE
   exchange in the bootstrapping solution? E.g., the first IKE message
   (IKE_SA_INIT) sent by MN would have anycast address as destination
   address (reply and all other IKE messages use unicast addresses as
   source/destination) and the Configuration Payload in the IKE_AUTH may
   contain an HA address for assignment to MN (only used if the HA that
   received the anycast IKE_SA_INIT shall not be used, e.g., because this
   HA is overloaded). 
   
=> note this is in fact Security Gateway assignment.

   > 
   >    >  - is the DNS-based DHAAD mechanism better enough to 
   > replace the ICMP-base
   >    >    one?
   
   What about the alternative to change the transport protocol, e.g.,
   UDP-based instead of ICMP-based anycast DHAAD?
   
=> the ICMP filtering issue is only one part of the problem.

   > - AFIK, there is no way currently standardized to securely update
   > anycast routing except to manually insert host routes into the subnet
   > router handling the anycast address. So maintaining an anycast address
   > would require extra maintenance effort, manually inserting and
   deleting
   > the routes when HAs are added or deleted.
   
   Interesting point, but isn't such a mechnism needed for almost all
   anycast-based protocols? I.e., isn't there a need for such a
   standardized mechanism anyway?
   
=> no, the anycast-based protocols are request/reply protocols so
they don't need responder stability.

Regards

Francis.Dupont@enst-bretagne.fr

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



From mip6-bounces@ietf.org Mon Oct 24 11:47:01 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EU4XM-0001UK-W0; Mon, 24 Oct 2005 11:47:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EU4XK-0001U4-DG
	for mip6@megatron.ietf.org; Mon, 24 Oct 2005 11:46:59 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16375
	for <mip6@ietf.org>; Mon, 24 Oct 2005 11:46:45 -0400 (EDT)
Received: from ftpbox.mot.com ([129.188.136.101])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EU4k6-00083h-Nu
	for mip6@ietf.org; Mon, 24 Oct 2005 12:00:11 -0400
Received: from az33exr04.mot.com (az33exr04.mot.com [10.64.251.234])
	by ftpbox.mot.com (Motorola/Ftpbox) with ESMTP id j9OFkrsL005677
	for <mip6@ietf.org>; Mon, 24 Oct 2005 08:46:53 -0700 (MST)
Received: from de01exm69.ds.mot.com (de01exm69.am.mot.com [10.176.8.25])
	by az33exr04.mot.com (8.13.1/8.13.0) with ESMTP id j9OFraip003236
	for <mip6@ietf.org>; Mon, 24 Oct 2005 10:53:37 -0500 (CDT)
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] draft-dupont-mip6-dhaadharmful-00.txt
Date: Mon, 24 Oct 2005 11:46:50 -0400
Message-ID: <0B40B6F9CB990B428819561A2A55613A103BE0@de01exm69.ds.mot.com>
Thread-Topic: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
Thread-Index: AcXYsGlrnzXsdgzfT1aAn+lCyqbcKAAANWeA
From: "Narayanan Vidya-CVN065" <vidya@motorola.com>
To: "Petrescu Alexandru-AAP021" <alexandru.petrescu@motorola.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Content-Transfer-Encoding: quoted-printable
Cc: mip6@ietf.org, Kilian Weniger <Kilian.Weniger@eu.panasonic.com>,
	Francis Dupont <Francis.Dupont@enst-bretagne.fr>,
	James Kempf <Kempf@docomolabs-usa.com>,
	Petrescu Alexandru-AAP021 <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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Hi Alex,
=20
> Let's compare to RO.  RO is a solution when MN and CN can't=20
> use IPsec/IKE because PKI may not be deployed everywhere.
>=20
> Same with non-anycast DHAAD, probably.  DNS-based HAD is a=20
> solution when DNSSEC is deployed everywhere, otherwise use=20
> non-anycast DHAAD, no?
>=20

This is just my ignorance - what is non-anycast DHAAD? :)=20


> > Also, it moves away from having to configure the home network prefix
>=20
> Yes, but it enforces the configuration of (textual variations=20
> of) "home.com".  A real advantage for DNS-based easying the=20
> bootstrapping would have been if there was nothing to pre-configure.
>=20


When you are doing discovery based on service name - say, "mip6" - this
is equivalent to zero config - it is a well known service name and
doesn't really require per-MN configuration.=20


> > and removes the limitation of dynamic HA assignment within the same=20
> > subnet, both of which are big pluses in my mind.
>=20
> One may see multiple-subnet HAs for a single MN as a big=20
> plus, but it is not at all clear whether a MN could continue=20
> using the same HoA after changing its HA from one subnet to=20
> another.  And, if when the MN switches its HA on another link=20
> is changing its HoA as well - it is equivalent to running=20
> DHAAD with a different subnet prefix.

Here, we are talking about two different aspects. I was referring to HA
assignment during bootstrapping, which can be done across subnets - so,
load balancing across subnets or assignment based on geographic
proximity becomes feasible. You are talking about a HA switch, that may
happen after a particular HA has been assigned. This seems to be a
different beast that needs to be tackled separately. But, yes, for a HA
switch, it still needs to be ironed out whether an MN can actually
continue to use the same HoA.=20

Vidya

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



From mip6-bounces@ietf.org Mon Oct 24 11:50:33 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EU4an-0002Zr-Cs; Mon, 24 Oct 2005 11:50:33 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EU4aj-0002ZL-VA
	for mip6@megatron.ietf.org; Mon, 24 Oct 2005 11:50:30 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16651
	for <mip6@ietf.org>; Mon, 24 Oct 2005 11:50:16 -0400 (EDT)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EU4nW-0008Dy-44
	for mip6@ietf.org; Mon, 24 Oct 2005 12:03:42 -0400
Received: from il06exr03.mot.com (il06exr03.mot.com [129.188.137.133])
	by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id j9OG2H80014028;
	Mon, 24 Oct 2005 09:02:17 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by il06exr03.mot.com (8.13.1/8.13.0) with ESMTP id j9OG0Maw001538;
	Mon, 24 Oct 2005 11:00:23 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id 1E601865980; Mon, 24 Oct 2005 17:50:23 +0200 (CEST)
Message-ID: <435D02BF.1080605@motorola.com>
Date: Mon, 24 Oct 2005 17:50:23 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: Narayanan Vidya-CVN065 <vidya@motorola.com>
Subject: Re: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
References: <0B40B6F9CB990B428819561A2A55613A103BE0@de01exm69.ds.mot.com>
In-Reply-To: <0B40B6F9CB990B428819561A2A55613A103BE0@de01exm69.ds.mot.com>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Content-Transfer-Encoding: 7bit
Cc: mip6@ietf.org, Kilian Weniger <Kilian.Weniger@eu.panasonic.com>,
	Francis Dupont <Francis.Dupont@enst-bretagne.fr>,
	James Kempf <Kempf@docomolabs-usa.com>,
	Petrescu Alexandru-AAP021 <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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Narayanan Vidya-CVN065 wrote:

> Hi Alex,
>  
>> Let's compare to RO.  RO is a solution when MN and CN can't
>> use IPsec/IKE because PKI may not be deployed everywhere.
>>
>> Same with non-anycast DHAAD, probably.  DNS-based HAD is a
>> solution when DNSSEC is deployed everywhere, otherwise use
>> non-anycast DHAAD, no?
>>
> 
> This is just my ignorance - what is non-anycast DHAAD? :)

Sorry, term just been invented minutes ago, it's like having a version
of DHAAD without using anycast addresses, because current DHAAD delies
on anycast addresses and IPsec can't run with them.

>> > Also, it moves away from having to configure the home network prefix
>>
>> Yes, but it enforces the configuration of (textual variations
>> of) "home.com".  A real advantage for DNS-based easying the
>> bootstrapping would have been if there was nothing to pre-configure.
>>
> 
> 
> When you are doing discovery based on service name - say, "mip6" - this
> is equivalent to zero config - it is a well known service name and
> doesn't really require per-MN configuration.

My turn to be ignorant, is it like MN could interrogate local DNS
telling it "give me the address of my HA"?  What would DNS use to
identify that MN and send it back its proper HA (and not some other MN's
HA)?

Alex


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



From mip6-bounces@ietf.org Mon Oct 24 11:57:42 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EU4hi-0005z9-Ol; Mon, 24 Oct 2005 11:57:42 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EU4hh-0005z4-Db
	for mip6@megatron.ietf.org; Mon, 24 Oct 2005 11:57:41 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17252
	for <mip6@ietf.org>; Mon, 24 Oct 2005 11:57:28 -0400 (EDT)
Received: from av7-2-sn3.vrr.skanova.net ([81.228.9.182])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EU4uS-000073-RP
	for mip6@ietf.org; Mon, 24 Oct 2005 12:10:54 -0400
Received: by av7-2-sn3.vrr.skanova.net (Postfix, from userid 502)
	id 5EFC737E8E; Mon, 24 Oct 2005 17:49:35 +0200 (CEST)
Received: from smtp3-2-sn3.vrr.skanova.net (smtp3-2-sn3.vrr.skanova.net
	[81.228.9.102]) by av7-2-sn3.vrr.skanova.net (Postfix) with ESMTP
	id 4021637E4C; Mon, 24 Oct 2005 17:49:35 +0200 (CEST)
Received: from shiraz.levkowetz.com (81-224-201-50-no45.tbcn.telia.com
	[81.224.201.50])
	by smtp3-2-sn3.vrr.skanova.net (Postfix) with ESMTP id B2D8A37E45;
	Mon, 24 Oct 2005 17:57:14 +0200 (CEST)
Received: from localhost ([127.0.0.1])
	by shiraz.levkowetz.com with esmtp (Exim 4.54)
	id 1EU4hG-0000Lu-7d; Mon, 24 Oct 2005 17:57:14 +0200
Message-ID: <435D0459.8050605@levkowetz.com>
Date: Mon, 24 Oct 2005 17:57:13 +0200
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Mozilla Thunderbird 1.0.7 (Macintosh/20050923)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Alexandru Petrescu <alexandru.petrescu@motorola.com>
Subject: Re: [Mip6] More comments on draft-ietf-mip6-nemo-v4traversal-00.txt
References: <435CF254.6050508@motorola.com>
In-Reply-To: <435CF254.6050508@motorola.com>
X-Enigmail-Version: 0.93.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: 93e7fb8fef2e780414389440f367c879
Content-Transfer-Encoding: 7bit
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Hi Alexandru,

on 2005-10-24 16:40 Alexandru Petrescu said the following:
[...]
> I have some comments.
> 
>> The current Mobile IPv6 specification and [NEMO] do not allow mobile
>>  nodes to use an IPv4 home address or prefix, respectively.
> 
> That is largely true.  Note though that recently there is a personal
> draft on NEMO for IPv4 home prefix that uses MIP4 and no MIP6.

Right.  But that isn't in the current spec, which is the base for what
this draft is attempting to expand.  We should check the draft you
refer to (name?) to make sure good ideas are incorporated in the
v4traversal work, though.

>> Mobile IPv6 offers a number of improvements over Mobile IPv4, mainly
>>  due to capabilities inherited from IPv6. For instance, route 
>> optimization and Dynamic home agent discovery can only be achieved 
>> with Mobile IPv6.
> 
> Maybe exemplify MIP6 superiority on MIP4 by something else than DHAAD,
> itself being questioned by the dhaad-harmful discussions, and
> acknowledged by this draft's section 2.1.

Humm?  The draft says "Dynamic home agent discovery", not DHAAD.  We've
been keeping up with what's being proposed in the bootstrapping work.

> I mean, on one hand the draft says DHAAD is an advantage of MIP6 over
> MIP4 and on antoher hand same draft says HA Discovery is not really
> specified.
> 
> RO is another case.  There are no widely deployed RO-enabled CNs while
> IPv4 non-RO CNs are plenty, so one can't really claim MIP6 is superior
> to MIP4 because it has RO.

No?  So the future potential of RO is of no interest?

>> We also assume that the Home Agent is always reachable through a 
>> globally unique IPv4 address.
> 
> I would like a DSMIPv6 solution to assume that the HAv6 is only
> reachable by its v6 address.  That would help widespread adoption of
> IPv6 by offering one less dependency on IPv4.

If we're trying to solve the problem of providing MIPv6 functionality
for a MN / MR which only has IPv4 access, it is not a solution to say
that the HA only is reachable through a IPv6 address...

Or have I misunderstood the drift of your comment??

> In case the MN has v4-only applications on it, and needs to continuously
> accessed IPv4 Home Address then I suggest porting these applications to
> IPv6.  In this case MIP6 is used as an advantage of IPv6: if an
> application is ported from IPv4 to IPv6 then it gets ability to run
> uninterrupted and use a permanent Home Address, and does not need MIP4.

I think this still does not in any way solve the problem of a MIPv6
MN/MR which finds itself in a visited network with only IPv4 access...

>> For DNS lookup by service, the SRV record defined in [BOOT] is 
>> reused.  For instance, if the service name is "mip6ha" and the 
>> protocol name is "ipv6" for the SRV record, the mobile node SHOULD 
>> send a DNS request with the QNAME set to "mip6ha.ipv6.example.com". 
>> The response should contain the home agent's FQDN(s) and may have the
>>  corresponding 'AAAA' and 'A' records enclosed as well.
> 
> This is another discussion, but I just mention it here.  This method for
> HAD does not specify a means for the HAs to co-operate with each other
> to establish their preferences.  With DNS-based it is left entirely to
> the MN to choose among the HAs addresses.

No.  Look at the SRV specification again.  It provides for priorities
between multiple choices, and fallback to backup hosts if the preferred
ones are down.

>> 2.3.1 Foreign network supports IPv6
> 
> This scenario is not described in the initial list of scenarios at 1.2
> "Scenarios considered by this specification".  Section 1.2 only lists
> access networks as IPv4.

Should be fixed.

>> 4.1. NAT detection and traversal
> 
> This section is very important for proper working of NAT detection and
> traversal.  However, it has some issues right now.
> 
>> The binding acknowledgement, and all future packets are then
>> encapsulated in UDP and IPv4. The source address in the IPv4 header
>> is the IPv4 address of the home agent. The destination address is the
>> IPv4 address received in the IPv4 header encapsulating the binding
>> update (this address will be different from the IPv4 care-of address
>> if a NAT were present in the path).
>> 
>> Upon receiving the binding acknowledgement with the NAT detection 
>> option, the mobile node sets the tunnel to the home agent to UDP 
>> encapsulation.
> 
> Actually there is more to happen between the two paragraphs.  Current
> implemented NATs have no idea about this draft, so they don't currently
> implement it.

No NAT should ever implement this draft.  I think there's some mis-
understanding here.

> A NAT needs to know a way for forwarding the BAck from the HA to MN.
> The v4 dst address in that UDPv4-encapsulated BAck is the NAT address
> itself.  In order for NAT to forward the packet to MN (and re-write the
> IPv4 dst address) it sometimes uses port numbers.  That's why UDP.  Or,
> there's no mention of UDP numbers in this section.

??  You can't have UDP encapsulation without UDP numbers.  I don't
understand...

> And, when port numbers are used to facilitate ip address rewriting by
> NAT, they are not fixed, they're dynamically changing.  Which would
> demand more enhancement to this section.

Hmm.  I don't see that.  MIPv4 NAT traversal (RFC 3519) definitely works,
and the protocol as described here uses the same basic mechanism.

Could you suggest some text?


>> "Dual Stack Mobile IPv6 (DSMIPv6)"
> 
> The title may not be very adapted.  It makes one somehow think about
> Dual-Stack MIP4 and MIP6, since 'dual-stack' is usually 'IPv4 stack and
> IPv6 stack'.  Or, the mechanism proposed is more about enhancing MIP6
> with some v4 features.  Maybe "v4-enhanced MIP6" would be better.

Agreed.  That should be fixed in the next revision.


	Henrik

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



From mip6-bounces@ietf.org Mon Oct 24 12:18:57 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EU4u2-0000l6-Cs; Mon, 24 Oct 2005 12:10:26 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EU4tw-0000kf-PG
	for mip6@megatron.ietf.org; Mon, 24 Oct 2005 12:10:24 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18132
	for <mip6@ietf.org>; Mon, 24 Oct 2005 12:10:07 -0400 (EDT)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EU56g-0000bO-R0
	for mip6@ietf.org; Mon, 24 Oct 2005 12:23:33 -0400
Received: from il06exr01.mot.com (il06exr01.mot.com [129.188.137.131])
	by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id j9OGM8qJ017946
	for <mip6@ietf.org>; Mon, 24 Oct 2005 09:22:08 -0700 (MST)
Received: from de01exm69.ds.mot.com (de01exm69.am.mot.com [10.176.8.25])
	by il06exr01.mot.com (8.13.1/8.13.0) with ESMTP id j9OGK6sc009577
	for <mip6@ietf.org>; Mon, 24 Oct 2005 11:20:07 -0500 (CDT)
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] draft-dupont-mip6-dhaadharmful-00.txt
Date: Mon, 24 Oct 2005 12:10:13 -0400
Message-ID: <0B40B6F9CB990B428819561A2A55613A103C28@de01exm69.ds.mot.com>
Thread-Topic: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
Thread-Index: AcXYsqX41Ujf0HOvQ8mQLfwNTBRU/AAAj9Jg
From: "Narayanan Vidya-CVN065" <vidya@motorola.com>
To: "Petrescu Alexandru-AAP021" <alexandru.petrescu@motorola.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Content-Transfer-Encoding: quoted-printable
Cc: mip6@ietf.org, Kilian Weniger <Kilian.Weniger@eu.panasonic.com>,
	Francis Dupont <Francis.Dupont@enst-bretagne.fr>,
	James Kempf <Kempf@docomolabs-usa.com>,
	Petrescu Alexandru-AAP021 <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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org


> Sorry, term just been invented minutes ago, it's like having=20
> a version of DHAAD without using anycast addresses, because=20
> current DHAAD delies on anycast addresses and IPsec can't run=20
> with them.


OK. So, what is the destination address for DHAAD?=20

> >=20
> > When you are doing discovery based on service name - say, "mip6" -=20
> > this is equivalent to zero config - it is a well known service name=20
> > and doesn't really require per-MN configuration.
>=20
> My turn to be ignorant, is it like MN could interrogate local=20
> DNS telling it "give me the address of my HA"?  What would=20
> DNS use to identify that MN and send it back its proper HA=20
> (and not some other MN's HA)?
>=20

Typically, I have seen DNS-based HA discovery to use say,
"mip6.domain1.com", where the MN belongs to domain1.com. If the MN is
trying to discover an HA in the local domain it is connected to, it
could simply use a service-based discovery using "mip6" as the service
name - in this case, a HA locally present in that domain would be
returned. If the MN is discovering a home agent in its domain, it would
use the former. It already knows its domain (for other purposes) and
"mip6" is a well-known prefix in this case.=20

Vidya

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



From mip6-bounces@ietf.org Mon Oct 24 12:18:58 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EU4u3-0000lF-2C; Mon, 24 Oct 2005 12:10:27 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EU4tw-0000ke-LA
	for mip6@megatron.ietf.org; Mon, 24 Oct 2005 12:10:24 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18130
	for <mip6@ietf.org>; Mon, 24 Oct 2005 12:10:07 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EU56h-0000bB-4k
	for mip6@ietf.org; Mon, 24 Oct 2005 12:23:33 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id j9OGA2f20246; Mon, 24 Oct 2005 18:10: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
	j9OGA2rV082832; Mon, 24 Oct 2005 18:10:02 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200510241610.j9OGA2rV082832@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Alexandru Petrescu <alexandru.petrescu@motorola.com>
Subject: Re: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt 
In-reply-to: Your message of Mon, 24 Oct 2005 17:42:35 +0200.
	<435D00EB.1080707@motorola.com> 
Date: Mon, 24 Oct 2005 18:10:02 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   > => this is more an argument for HA-switch (another way to provide HA
   > assignment)...
   
   Thanks, where is HA-switch discussed, drafted?
   
=> draft-haley-mip6-ha-switch-00.txt and (more general)
draft-devarapalli-mip6-nemo-local-haha-00.txt

I believe one of these I-Ds was proposed for the MIPv6 agenda.

   > The issue with the anycast-like address is the responder must be
   > always the same box in order to use correctly IPsec.
   
   I don't buy into that.  It's like saying that because of IPsec two boxes
   aren't allowed to have same IPv6 address.  It's also ignoring that the
   "unique IP address per box" concept no longer exists since "server farms
   and blades", "IP over VIA" and "modem connected to PDA" got widespread use.
   
=> multiple sources don't work well when two of the security services
are "source origin authentication" and "anti-replay". IPsec is just
not the right protocol here.

   > IMHO the best way to protect current DHAAD is per exchange and not
   > per communication but the real issue is the effort doesn't worth it.
   
   exchange vs. communication?
   
=> exchange := request/reply, communication:= stream of exchanges.
IPsec or SSL/TLS are stream/session oriented, an exchange oriented
security protocol should use per message signature and similar ideas,
not a session key with an anti-replay mechanism.
The problem here is the standard security protocol (IPsec) is not
convenient and to add security from scratch is known to be hard,
so it is better to use something more suitable, DNSSEC is fine because
it has both (in an exchange oriented style BTW) transaction and data
protections...

Regards

Francis.Dupont@enst-bretagne.fr

   

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



From mip6-bounces@ietf.org Mon Oct 24 12:29:11 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EU5CB-0001X2-Nd; Mon, 24 Oct 2005 12:29:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EU5C9-0001Wo-S4
	for mip6@megatron.ietf.org; Mon, 24 Oct 2005 12:29:09 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18994
	for <mip6@ietf.org>; Mon, 24 Oct 2005 12:28:56 -0400 (EDT)
Received: from cluster-d.mailcontrol.com ([217.69.20.190]
	helo=rly27d.srv.mailcontrol.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EU5Ov-0001C1-LO
	for mip6@ietf.org; Mon, 24 Oct 2005 12:42:23 -0400
Received: from hhe500-02.hbg.de.pan.eu (gate.eu.panasonic.com [194.173.20.12])
	by rly27d.srv.mailcontrol.com (MailControl) with SMTP id
	j9OGSwQ1030504; Mon, 24 Oct 2005 17:28:58 +0100
Received: from eundadmi01.pan.eu(10.100.96.64) by hhe500-02.hbg.de.pan.eu via
	smtp id 7571_0b9bc346_44ac_11da_95b5_0030482aac25;
	Mon, 24 Oct 2005 18:34:27 +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 2005102418285167-27978 ;
	Mon, 24 Oct 2005 18:28:51 +0200 
Received: from localhost ([127.0.0.1]) by VPN-MRelay-01.PRDCG.Panasonic.de;
	Mon, 24 Oct 2005 18:30:59 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
MIME-Version: 1.0
Subject: RE: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt 
Thread-Topic: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt 
Thread-Index: AcXYshVqC3Cr5Dl6R92gdU43XTtRpwAAV9iw
To: <Francis.Dupont@enst-bretagne.fr>
Message-ID: <4D2F935F08D41A4C8866693F4F0D7C4F58E662@lan-ex-01.panasonic.de>
Date: Mon, 24 Oct 2005 18:28:46 +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-05-40-01 (www.mailcontrol.com) on 10.68.0.137
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976
Content-Transfer-Encoding: quoted-printable
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org


> =3D> IMHO load balancing should not be provided by a DHAAD mechanism
> but by HA assignment or HA-switch.

I agree that HA-switch is needed (not only for load balancing), but if
an DHAAD mechanism already supports load balancing, signaling overhead
and delay can be saved by skipping a subsequent HA-switch. If MNs
frequently bootstrap with new HAs (e.g., when always using local HAs),
the saved signaling overhead and delay might be significant.=20

>    Wouldn't it be possible to integrate HA discovery and=20
> assignment somehow
>    in an IKEv2 exchange,
>=20
> =3D> this is the Security Gateway discovery issue. It is in the scope
> of the IPsec WG but I am afraid we should not wait for a solution
> from them, on another hand it has to be secure and IPsec people
> should be better...
>=20
>    similar as HoA assignment is integrated in IKE
>    exchange in the bootstrapping solution? E.g., the first IKE message
>    (IKE_SA_INIT) sent by MN would have anycast address as destination
>    address (reply and all other IKE messages use unicast addresses as
>    source/destination) and the Configuration Payload in the=20
> IKE_AUTH may
>    contain an HA address for assignment to MN (only used if=20
> the HA that
>    received the anycast IKE_SA_INIT shall not be used, e.g.,=20
> because this
>    HA is overloaded).=20
>   =20
> =3D> note this is in fact Security Gateway assignment.

o.k., good to know. That sounds like an efficient (low signaling
overhead+load balancing support) and secure HA discovery/assignment
mechanism, but unfortunately it is not yet available.

>    > - AFIK, there is no way currently standardized to securely update
>    > anycast routing except to manually insert host routes=20
> into the subnet
>    > router handling the anycast address. So maintaining an=20
> anycast address
>    > would require extra maintenance effort, manually inserting and
>    deleting
>    > the routes when HAs are added or deleted.
>   =20
>    Interesting point, but isn't such a mechnism needed for almost all
>    anycast-based protocols? I.e., isn't there a need for such a
>    standardized mechanism anyway?
>   =20
> =3D> no, the anycast-based protocols are request/reply protocols so
> they don't need responder stability.

Yes, but I think James point was that the subnet routers have to know
which hosts have configured which anycast addresses. RFC1546 (page 5)
discusses some possible solutions and proposes to advertise configured
anycast addresses to routers by using multicast (possibly with an
enhanced IGMP):

"Hosts which wish to receive datagrams for a particular anycast
   address will have to advertise to routers that they have joined the
   anycast address.  On shared media networks, the best mechanism is
   probably for a host to periodically multicast information about the
   anycast addresses it supports (possibly using an enhanced version of
   IGMP).  The multicast messages ensure that any routers on the network
   hear that the anycast address is supported on the local subnet and
   can advertise that fact (if appropriate) to neighboring routers.
   Note that if there are no routers on the subnet, the multicast
   messages would simply simply ignored.  (The multicasting approach is
   suggested because it seems likely to be simpler and more reliable
   than developing a registration protocol, in which an anycast server
   must register itself with each router on its local network)."

After quickly searching for anycast in RFC3376, I guess IGMP doesn't
support that.


Regards,

Kilian


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



From mip6-bounces@ietf.org Mon Oct 24 12:30:59 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EU5Dv-0001gq-5y; Mon, 24 Oct 2005 12:30:59 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EU5Du-0001gl-90
	for mip6@megatron.ietf.org; Mon, 24 Oct 2005 12:30:58 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19051
	for <mip6@ietf.org>; Mon, 24 Oct 2005 12:30:45 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EU5Qe-0001DN-4o
	for mip6@ietf.org; Mon, 24 Oct 2005 12:44:11 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id j9OGUIf21564; Mon, 24 Oct 2005 18:30: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
	j9OGUJJ6082956; Mon, 24 Oct 2005 18:30:19 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200510241630.j9OGUJJ6082956@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Alexandru Petrescu <alexandru.petrescu@motorola.com>
Subject: Re: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt 
In-reply-to: Your message of Mon, 24 Oct 2005 17:50:23 +0200.
	<435D02BF.1080605@motorola.com> 
Date: Mon, 24 Oct 2005 18:30:19 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   > This is just my ignorance - what is non-anycast DHAAD? :)
   
   Sorry, term just been invented minutes ago, it's like having a version
   of DHAAD without using anycast addresses, because current DHAAD delies
   on anycast addresses and IPsec can't run with them.
   
=> what I don't understand is how the MN gets first the non-anycast
address? If it has already a HA and wants just to get other available
HA IMHO HA-switch (as a re-assignment mechanism) is a better solution.

   > When you are doing discovery based on service name - say, "mip6" - this
   > is equivalent to zero config - it is a well known service name and
   > doesn't really require per-MN configuration.
   
=> I disagree a bit: you need a name (FQDN) to query about.

   My turn to be ignorant, is it like MN could interrogate local DNS
   telling it "give me the address of my HA"?  What would DNS use to
   identify that MN and send it back its proper HA (and not some other MN's
   HA)?
   
=> a property of the DNS (and of the current DHAAD but this could be changed)
is the answer should never rely on who sends the question or where it comes
from. So "my HA" doesn't make sense, but of course "myHA.example.com"
or "...msp.example.com" do.

Regards

Francis.Dupont@enst-bretagne.fr

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



From mip6-bounces@ietf.org Mon Oct 24 12:38:00 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EU5Ki-0002IC-PO; Mon, 24 Oct 2005 12:38:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EU5Kh-0002I7-Tt
	for mip6@megatron.ietf.org; Mon, 24 Oct 2005 12:38:00 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19277
	for <mip6@ietf.org>; Mon, 24 Oct 2005 12:37:46 -0400 (EDT)
Received: from motgate.mot.com ([129.188.136.100])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EU5XT-0001Qh-Nb
	for mip6@ietf.org; Mon, 24 Oct 2005 12:51:13 -0400
Received: from az33exr03.mot.com (az33exr03.mot.com [10.64.251.233])
	by motgate.mot.com (Motorola/Motgate) with ESMTP id j9OGbuTD009751
	for <mip6@ietf.org>; Mon, 24 Oct 2005 09:37:56 -0700 (MST)
Received: from de01exm69.ds.mot.com (de01exm69.am.mot.com [10.176.8.25])
	by az33exr03.mot.com (8.13.1/8.13.0) with ESMTP id j9OGl8gL010561
	for <mip6@ietf.org>; Mon, 24 Oct 2005 11:47:09 -0500 (CDT)
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] draft-dupont-mip6-dhaadharmful-00.txt 
Date: Mon, 24 Oct 2005 12:37:53 -0400
Message-ID: <0B40B6F9CB990B428819561A2A55613A103C54@de01exm69.ds.mot.com>
Thread-Topic: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt 
Thread-Index: AcXYuFm+XXDljWT8Qv6YaaKmF1lymwAAFx2Q
From: "Narayanan Vidya-CVN065" <vidya@motorola.com>
To: <Francis.Dupont@enst-bretagne.fr>,
	"Petrescu Alexandru-AAP021" <alexandru.petrescu@motorola.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Content-Transfer-Encoding: quoted-printable
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

>   =20
> =3D> what I don't understand is how the MN gets first the=20
> non-anycast address?

I have the same confusion.=20

> If it has already a HA and wants just to=20
> get other available HA IMHO HA-switch (as a re-assignment=20
> mechanism) is a better solution.=20

Yes, this is a switch case and not a bootstrapping case.=20

>=20
>    > When you are doing discovery based on service name -=20
> say, "mip6" - this
>    > is equivalent to zero config - it is a well known=20
> service name and
>    > doesn't really require per-MN configuration.
>   =20
> =3D> I disagree a bit: you need a name (FQDN) to query about.
>=20

True. The FQDN can be a common and well-known one - that was really my
point.=20

>   =20
> =3D> a property of the DNS (and of the current DHAAD but this=20
> could be changed) is the answer should never rely on who=20
> sends the question or where it comes from. So "my HA" doesn't=20
> make sense, but of course "myHA.example.com"
> or "...msp.example.com" do.
>=20

Yes, so - "example.com" is something the MN already knows (it most
likely belongs to example.com"). If "myHA" is the well known service
name for mip6 HAs, "myHA.example.com" can be created by the MN easily. I
suppose one could argue that it still requires *some* configuration - it
seems to be still better than configuring a particular home subnet to
me.=20

Thanks,
Vidya

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



From mip6-bounces@ietf.org Mon Oct 24 12:43:24 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EU5Pw-0004zN-L2; Mon, 24 Oct 2005 12:43:24 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EU5Pr-0004vr-J9
	for mip6@megatron.ietf.org; Mon, 24 Oct 2005 12:43:19 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19702
	for <mip6@ietf.org>; Mon, 24 Oct 2005 12:43:06 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EU5ce-0001dE-3v
	for mip6@ietf.org; Mon, 24 Oct 2005 12:56:32 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id j9OGgtf22529; Mon, 24 Oct 2005 18:42:55 +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
	j9OGgtJV083109; Mon, 24 Oct 2005 18:42:55 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200510241642.j9OGgtJV083109@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: "Kilian Weniger" <Kilian.Weniger@eu.panasonic.com>
Subject: Re: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt 
In-reply-to: Your message of Mon, 24 Oct 2005 18:28:46 +0200.
	<4D2F935F08D41A4C8866693F4F0D7C4F58E662@lan-ex-01.panasonic.de> 
Date: Mon, 24 Oct 2005 18:42:55 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   > => IMHO load balancing should not be provided by a DHAAD mechanism
   > but by HA assignment or HA-switch.
   
=> I should have written "HA assignement or HA re-assignment like
HA-switch".

   I agree that HA-switch is needed (not only for load balancing),

=> yes, we should get HA-switch deployed before DNSSEC (:-).

   but if
   an DHAAD mechanism already supports load balancing, signaling overhead
   and delay can be saved by skipping a subsequent HA-switch.

=> HA-switch is re-assignment. It has a higher overhead if there is
no assignment but it can do dynamic load balancing, i.e., balance the
load after the initial phase.

   If MNs
   frequently bootstrap with new HAs (e.g., when always using local HAs),
   the saved signaling overhead and delay might be significant. 
   
=> local HAs is a better case of HA assignment (i.e., there can be
a mechanism available on this case but not general).

   > => note this is in fact Security Gateway assignment.
   
   o.k., good to know. That sounds like an efficient (low signaling
   overhead+load balancing support) and secure HA discovery/assignment
   mechanism, but unfortunately it is not yet available.
   
=> I'll be more optimistic: there is no general already specified
mechanism.

   >    
   > => no, the anycast-based protocols are request/reply protocols so
   > they don't need responder stability.
   
   Yes, but I think James point was that the subnet routers have to know
   which hosts have configured which anycast addresses. RFC1546 (page 5)
   discusses some possible solutions and proposes to advertise configured
   anycast addresses to routers by using multicast (possibly with an
   enhanced IGMP):
   
=> anycast and multicast are two variations of the same destination
group addressing. IMHO anycast is a bit easier because there is no
collision issue on replies.

Regards

Francis.Dupont@enst-bretagne.fr

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



From mip6-bounces@ietf.org Mon Oct 24 12:48:16 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EU5UZ-00065Z-JU; Mon, 24 Oct 2005 12:48:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EU5UY-00064K-68
	for mip6@megatron.ietf.org; Mon, 24 Oct 2005 12:48:10 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19959
	for <mip6@ietf.org>; Mon, 24 Oct 2005 12:47:57 -0400 (EDT)
Received: from mail.flarion.com ([63.103.94.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EU5hK-0001mw-5C
	for mip6@ietf.org; Mon, 24 Oct 2005 13:01:23 -0400
Received: from ftmailserver.flariontech.com ([10.10.1.140]) by
	mail.flarion.com with Microsoft SMTPSVC(5.0.2195.6713);
	Mon, 24 Oct 2005 12:47:51 -0400
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
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] I-D ACTION:draft-ietf-mip6-nemo-v4traversal-00.txt 
Date: Mon, 24 Oct 2005 12:47:51 -0400
Message-ID: <A11736FE943F1A408F8BBB1B9F5FE8AD17DE46@ftmailserver.flariontech.com>
Thread-Topic: [Mip6] I-D ACTION:draft-ietf-mip6-nemo-v4traversal-00.txt 
Thread-Index: AcXYgx5EJ/KPhTgbRVSyx9WcFfJRlgANmM+w
From: "Soliman, Hesham" <H.Soliman@flarion.com>
To: "Keiichi SHIMA" <keiichi@iijlab.net>
X-OriginalArrivalTime: 24 Oct 2005 16:47:51.0232 (UTC)
	FILETIME=[AC123C00:01C5D8BA]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Content-Transfer-Encoding: quoted-printable
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org




 > My point is that having IPv4 CoA and Having IPv4 HoA is different
 > things and they are orthogonal.  (I think my explanation is not
 > good...)

=3D> Agreed. If you are trying to provide a complete transition
mechanism you might want to solve more than one issue. Some of=20
the issues might be orthogonal to each other, but still crucial
for the overall problem. For example, NAT traversal is a separate
problem that may or may not be needed, depending on where the MN is=20
located, but we still solved it in the current draft.=20

 > Let's consider to implement IPv6 mobile node which supports IPv4
 > access network, but don't support IPv4 HoA.  Which RFC should we
 > support? =20

=3D> I don't understand. There are no RFCs for this case today. If
you're talking about the "future" RFC, then this hypothetical
MN would be supporting parts of the current draft (future RFC).
The current draft doesn't say that the MN MUST implement the IPv4
home address option.=20

   If we continue to discuss the different things in=20
 > one draft,
 > we must also make it clear which section(s) is necessary to implement
 > what feature.  But I feel it is a bad idea to specify=20
 > features in such
 > a manner.  Easier way to make it clear is to divide the=20
 > specification...

=3D> This is a product management issue. I've been through this=20
exercise many times before and it's pretty straight forward to
mention what features are not supported. =20

 > Frankly speaking, I think I can implement the function from the text,
 > since I already have much knowledge of MIP implementation.  But maybe
 > the draft at least should mention about

=3D> Good to see that you can implement it. I'll take a look at the=20
text you sent and give you some feedback. Thanks for your suggestion,=20
it looks like this could be useful for the draft.

Hesham

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D
This email may contain confidential and privileged material for the sole =
use
 of the intended recipient.  Any review or distribution by others is =
strictly
 prohibited.  If you are not the intended recipient please contact the =
sender
 and delete all copies.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D


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



From mip6-bounces@ietf.org Mon Oct 24 12:51:22 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EU5Xe-0007P5-8z; Mon, 24 Oct 2005 12:51:22 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EU5Xa-0007Jn-Np
	for mip6@megatron.ietf.org; Mon, 24 Oct 2005 12:51:18 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20162
	for <mip6@ietf.org>; Mon, 24 Oct 2005 12:51:05 -0400 (EDT)
Received: from dns1.tilab.com ([163.162.42.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EU5kK-0001uF-Rm
	for mip6@ietf.org; Mon, 24 Oct 2005 13:04:32 -0400
Received: from iowa2k01a.cselt.it ([163.162.242.201])
	by dns1.cselt.it (PMDF V6.0-025 #38895)
	with ESMTP id <0IOV0080VIT31Y@dns1.cselt.it> for mip6@ietf.org; Mon,
	24 Oct 2005 18:51:03 +0200 (MEST)
Received: from EXC01B.cselt.it ([163.162.4.199]) by iowa2k01a.cselt.it with
	Microsoft SMTPSVC(6.0.3790.211); Mon, 24 Oct 2005 18:51:03 +0200
Date: Mon, 24 Oct 2005 18:51:03 +0200
From: Gerardo Giaretta <Gerardo.Giaretta@TILAB.COM>
Subject: RE: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
To: Kilian Weniger <Kilian.Weniger@eu.panasonic.com>,
	Francis.Dupont@enst-bretagne.fr,
	Alexandru Petrescu <alexandru.petrescu@motorola.com>
Message-id: <DA62A6E0CDD1B34A84557FF1AC850C57016E9CCA@EXC01B.cselt.it>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.3790.326
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: quoted-printable
Importance: normal
Priority: normal
Thread-Topic: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
thread-index: AcXYqXbXIA/i8BXYScS1SYiWXuH9KAAAVacgAAMu7pA=
Content-Class: urn:content-classes:message
X-OriginalArrivalTime: 24 Oct 2005 16:51:03.0562 (UTC)
	FILETIME=[1EB576A0:01C5D8BB]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 944ecb6e61f753561f559a497458fb4f
Content-Transfer-Encoding: quoted-printable
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Hi Kilian, all,=20

> Hi Francis, Alex,
>=20
> >    Both ideas have appeal to me.  Both could be supported by some
> >    argumentation.
> >=20
> > =3D> this is why we should have this discussion.
>=20
> I agree that DNS-based DHAAD can be more secure, but one advantage of
> anycast-based DHAAD I can see is that load balancing is=20
> better supported
> since load conditions can be considered faster (probably cannot be
> distributed fast enough in DNS).
>

As pointed out in draft-ietf-mip6-bootstrapping-split-01, DNS-based HA
discovery may be used only to achieve coarse-grained load balancing by
dynamically updating the SRV RR priorities. On the other hand, DHAAD
cannot be used to load balance using different HAs in different subnet.
I still think that achieving a good load balancing solution during HA
discovery/assignment is very difficult in split scenario. I tend to
agree with Francis that in this scenario the load balancing issue may be
solved by a HA switch solution.

In integrated scenario it is a little bit easier and also a per-MN load
balancing can be achieved relying on the AAA infrastructure (see the
integrated scenario draft based on DHCP). IMO, an even better per-MN
load balancing support is achieved performing HA discovery during
network access authentication (e.g. via EAP or PANA), but this was
discarded by the DT because of well-known reasons.

--Gerardo

=20
> > =3D> IMHO HA assignement is far better but there is not yet a=20
> mechanism
> > providing it *and* applicable in the general case.
>=20
> Security-wise yes. But which entity assigns the HA? And how do you
> discover this HA assignment entity? And what about the signaling
> overhead then? And the signaling overhead can be pretty high, e.g., if
> MN first needs to request DNS to discover assignment entity and
> subsequently establishes SA with assignment entity, gets HA=20
> assigned and
> finally establishes SA with this HA.
>=20
> Wouldn't it be possible to integrate HA discovery and=20
> assignment somehow
> in an IKEv2 exchange, similar as HoA assignment is integrated in IKE
> exchange in the bootstrapping solution? E.g., the first IKE message
> (IKE_SA_INIT) sent by MN would have anycast address as destination
> address (reply and all other IKE messages use unicast addresses as
> source/destination) and the Configuration Payload in the IKE_AUTH may
> contain an HA address for assignment to MN (only used if the HA that
> received the anycast IKE_SA_INIT shall not be used, e.g., because this
> HA is overloaded).=20
>=20
> >=20
> >    >  - is the DNS-based DHAAD mechanism better enough to=20
> > replace the ICMP-base
> >    >    one?
>=20
> What about the alternative to change the transport protocol, e.g.,
> UDP-based instead of ICMP-based anycast DHAAD?
>=20
> > - AFIK, there is no way currently standardized to securely update
> > anycast routing except to manually insert host routes into=20
> the subnet
> > router handling the anycast address. So maintaining an=20
> anycast address
> > would require extra maintenance effort, manually inserting and
> deleting
> > the routes when HAs are added or deleted.
>=20
> Interesting point, but isn't such a mechnism needed for almost all
> anycast-based protocols? I.e., isn't there a need for such a
> standardized mechanism anyway?
>=20
> Regards,
>=20
> Kilian
>=20
>=20
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
>=20


Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia =
S.p.A.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
CONFIDENTIALITY NOTICE
This message and its attachments are addressed solely to the persons
above and may contain confidential information. If you have received
the message in error, be informed that any use of the content hereof
is prohibited. Please return it immediately to the sender and delete
the message. Should you have any questions, please send an e_mail to=20
MailAdmin@tilab.com. Thank you
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

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



From mip6-bounces@ietf.org Mon Oct 24 12:53:42 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EU5Zu-0000Bk-89; Mon, 24 Oct 2005 12:53:42 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EU5Zq-0000Be-3t
	for mip6@megatron.ietf.org; Mon, 24 Oct 2005 12:53:38 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20304
	for <mip6@ietf.org>; Mon, 24 Oct 2005 12:53:24 -0400 (EDT)
Received: from p-mail1.rd.francetelecom.com ([195.101.245.15])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EU5mb-0001zi-6u
	for mip6@ietf.org; Mon, 24 Oct 2005 13:06:51 -0400
Received: from ftrdmel3.rd.francetelecom.fr ([10.193.117.155]) by
	ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.211); 
	Mon, 24 Oct 2005 18:53:33 +0200
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] draft-dupont-mip6-dhaadharmful-00.txt 
Date: Mon, 24 Oct 2005 18:53:29 +0200
Message-ID: <D2AA6DF1AEE4404F8D983B68BAC97CD2022B914B@ftrdmel3.rd.francetelecom.fr>
Thread-Topic: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt 
Thread-Index: AcXYmAy19R9rZjd5Q6uwsLFw5TPmRAAFeDcgAAJ6ldA=
From: "COMBES Jean-Michel RD-MAPS-ISS" <jeanmichel.combes@francetelecom.com>
To: "Narayanan Vidya-CVN065" <vidya@motorola.com>,
	"Francis Dupont" <Francis.Dupont@enst-bretagne.fr>,
	"Petrescu Alexandru-AAP021" <alexandru.petrescu@motorola.com>
X-OriginalArrivalTime: 24 Oct 2005 16:53:33.0872 (UTC)
	FILETIME=[784CF300:01C5D8BB]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
Content-Transfer-Encoding: quoted-printable
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Hi,

IMO, we MUST have a solution permitting:=20
o the MSP to assign only the HA he wants to allocate
AND
o the MN to pick a HA in from a HA list if the MSP allows such a thing

For the moment, with these proposals, the MSP has not the possibility to
manage its HA as he wants ...

Regarding the two present solutions:
o DNS-based DHAAD
I don't like this solution because such mechanism gives the location,
for a MSP, of all its HA, which are the MIPv6 point of failure and so
the prioritized targets for "bad guys". You give the stick to be beaten
... :(
o ICMP-based mechanism
Here again, the present mechanism gives all the HA but I think it may be
simply modified to give only one HA if the MSP wants to assign HA.
The main issue is regarding its security ... Maybe Alexandru's proposal
or HAHA proposal would be interesting.

Best regards.

JMC.

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

> -----Original Message-----
> From: mip6-bounces@ietf.org [mailto:mip6-bounces@ietf.org] On=20
> Behalf Of Narayanan Vidya-CVN065
> Sent: Monday, October 24, 2005 5:21 PM
> To: Francis Dupont; Petrescu Alexandru-AAP021
> Cc: mip6@ietf.org; Kilian Weniger; James Kempf
> Subject: RE: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt=20
>=20
> >   =20
> > =3D> the two questions are:
> >  - should we keep a DHAAD mechanism or HA assignment is the right=20
> > thing
> >    to do?
> >  - is the DNS-based DHAAD mechanism better enough to replace the=20
> > ICMP-base
> >    one?
> >=20
>=20
> These are good questions. I believe that a DNS-based=20
> mechanism is largely better than an ICMP-based mechansim. For=20
> those who wish to secure the operation, at least an option is=20
> available. Whether DNSSEC will be widely deployed is a=20
> separate question, but at least, it is an option. Also, it=20
> moves away from having to configure the home network prefix=20
> and removes the limitation of dynamic HA assignment within=20
> the same subnet, both of which are big pluses in my mind.=20
>=20
> Regards,
> Vidya
>=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 Oct 24 12:55:38 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EU5bm-0000iB-M4; Mon, 24 Oct 2005 12:55:38 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EU5bk-0000i6-Fx
	for mip6@megatron.ietf.org; Mon, 24 Oct 2005 12:55:36 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20368
	for <mip6@ietf.org>; Mon, 24 Oct 2005 12:55:22 -0400 (EDT)
Received: from dns1.tilab.com ([163.162.42.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EU5oK-00021i-S9
	for mip6@ietf.org; Mon, 24 Oct 2005 13:08:37 -0400
Received: from iowa2k01a.cselt.it ([163.162.242.201])
	by dns1.cselt.it (PMDF V6.0-025 #38895)
	with ESMTP id <0IOV0085NJ021Y@dns1.cselt.it> for mip6@ietf.org; Mon,
	24 Oct 2005 18:55:14 +0200 (MEST)
Received: from EXC01B.cselt.it ([163.162.4.199]) by iowa2k01a.cselt.it with
	Microsoft SMTPSVC(6.0.3790.211); Mon, 24 Oct 2005 18:55:14 +0200
Date: Mon, 24 Oct 2005 18:55:13 +0200
From: Gerardo Giaretta <Gerardo.Giaretta@TILAB.COM>
Subject: RE: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
To: Kilian Weniger <Kilian.Weniger@eu.panasonic.com>,
	Francis.Dupont@enst-bretagne.fr
Message-id: <DA62A6E0CDD1B34A84557FF1AC850C57016E9CCB@EXC01B.cselt.it>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.3790.326
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: quoted-printable
Importance: normal
Priority: normal
Thread-Topic: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
thread-index: AcXYshVqC3Cr5Dl6R92gdU43XTtRpwAAV9iwAAH0bOA=
Content-Class: urn:content-classes:message
X-OriginalArrivalTime: 24 Oct 2005 16:55:14.0046 (UTC)
	FILETIME=[B40249E0:01C5D8BB]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ff03b0075c3fc728d7d60a15b4ee1ad2
Content-Transfer-Encoding: quoted-printable
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 > > =3D> IMHO load balancing should not be provided by a DHAAD =
mechanism
> > but by HA assignment or HA-switch.
>=20
> I agree that HA-switch is needed (not only for load balancing), but if
> an DHAAD mechanism already supports load balancing, signaling overhead
> and delay can be saved by skipping a subsequent HA-switch. If MNs
> frequently bootstrap with new HAs (e.g., when always using local HAs),
> the saved signaling overhead and delay might be significant.=20
>=20

I agree that HA switch may have large signaling overhead. However, as
said in my previous post I think it is quite difficult to achieve load
balancing in spit scenario during HA discovery if we rule out DHAAD. In
integrated scenario, the issue may be less tricky.

--Gerardo


> >    Wouldn't it be possible to integrate HA discovery and=20
> > assignment somehow
> >    in an IKEv2 exchange,
> >=20
> > =3D> this is the Security Gateway discovery issue. It is in the =
scope
> > of the IPsec WG but I am afraid we should not wait for a solution
> > from them, on another hand it has to be secure and IPsec people
> > should be better...
> >=20
> >    similar as HoA assignment is integrated in IKE
> >    exchange in the bootstrapping solution? E.g., the first=20
> IKE message
> >    (IKE_SA_INIT) sent by MN would have anycast address as=20
> destination
> >    address (reply and all other IKE messages use unicast=20
> addresses as
> >    source/destination) and the Configuration Payload in the=20
> > IKE_AUTH may
> >    contain an HA address for assignment to MN (only used if=20
> > the HA that
> >    received the anycast IKE_SA_INIT shall not be used, e.g.,=20
> > because this
> >    HA is overloaded).=20
> >   =20
> > =3D> note this is in fact Security Gateway assignment.
>=20
> o.k., good to know. That sounds like an efficient (low signaling
> overhead+load balancing support) and secure HA discovery/assignment
> mechanism, but unfortunately it is not yet available.
>=20
> >    > - AFIK, there is no way currently standardized to=20
> securely update
> >    > anycast routing except to manually insert host routes=20
> > into the subnet
> >    > router handling the anycast address. So maintaining an=20
> > anycast address
> >    > would require extra maintenance effort, manually inserting and
> >    deleting
> >    > the routes when HAs are added or deleted.
> >   =20
> >    Interesting point, but isn't such a mechnism needed for=20
> almost all
> >    anycast-based protocols? I.e., isn't there a need for such a
> >    standardized mechanism anyway?
> >   =20
> > =3D> no, the anycast-based protocols are request/reply protocols so
> > they don't need responder stability.
>=20
> Yes, but I think James point was that the subnet routers have to know
> which hosts have configured which anycast addresses. RFC1546 (page 5)
> discusses some possible solutions and proposes to advertise configured
> anycast addresses to routers by using multicast (possibly with an
> enhanced IGMP):
>=20
> "Hosts which wish to receive datagrams for a particular anycast
>    address will have to advertise to routers that they have joined the
>    anycast address.  On shared media networks, the best mechanism is
>    probably for a host to periodically multicast information about the
>    anycast addresses it supports (possibly using an enhanced=20
> version of
>    IGMP).  The multicast messages ensure that any routers on=20
> the network
>    hear that the anycast address is supported on the local subnet and
>    can advertise that fact (if appropriate) to neighboring routers.
>    Note that if there are no routers on the subnet, the multicast
>    messages would simply simply ignored.  (The multicasting=20
> approach is
>    suggested because it seems likely to be simpler and more reliable
>    than developing a registration protocol, in which an anycast server
>    must register itself with each router on its local network)."
>=20
> After quickly searching for anycast in RFC3376, I guess IGMP doesn't
> support that.
>=20
>=20
> Regards,
>=20
> Kilian
>=20
>=20
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
>=20


Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia =
S.p.A.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
CONFIDENTIALITY NOTICE
This message and its attachments are addressed solely to the persons
above and may contain confidential information. If you have received
the message in error, be informed that any use of the content hereof
is prohibited. Please return it immediately to the sender and delete
the message. Should you have any questions, please send an e_mail to=20
MailAdmin@tilab.com. Thank you
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

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



From mip6-bounces@ietf.org Mon Oct 24 13:04:50 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EU5kg-00032m-8q; Mon, 24 Oct 2005 13:04:50 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EU5kc-0002zk-OH
	for mip6@megatron.ietf.org; Mon, 24 Oct 2005 13:04:46 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20866
	for <mip6@ietf.org>; Mon, 24 Oct 2005 13:04:33 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EU5xN-0002Le-Rs
	for mip6@ietf.org; Mon, 24 Oct 2005 13:18:00 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id j9OH4Ef24049
	for <mip6@ietf.org>; Mon, 24 Oct 2005 19:04: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
	j9OH4EEP083244
	for <mip6@ietf.org>; Mon, 24 Oct 2005 19:04:14 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200510241704.j9OH4EEP083244@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: mip6@ietf.org
Date: Mon, 24 Oct 2005 19:04:14 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Subject: [Mip6] IPsec and return to home
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

In RFC 3776 and 3776bis (IKEv2) there is:

   o  When the mobile node returns home and de-registers with the Home
      Agent, the tunnel between the home agent and the mobile node's
      care-of address is torn down.  The security policy entries, which
      were used for protecting tunneled traffic between the mobile node
      and the home agent MUST be made inactive (for instance, by
      removing them and installing them back later through an API).  The
      corresponding security associations could be kept as they are or
      deleted depending on how they were created.  If the security
      associations were created dynamically using IKE, they are
      automatically deleted when they expire.  If the security
      associations were created through manual configuration, they MUST
      be retained and used later when the mobile node moves away from
      home again.  The security associations protecting Binding Updates
      and Acknowledgements, and prefix discovery SHOULD NOT be deleted
      as they do not depend on care-of addresses and can be used again.

This is a bit problematic to support in some current KAME OSs because
the mandatory control on the position in the SPD of new entries is
not supported, i.e., if some SPD entries are removed and inserted
back the order is not preserved... Even it is really a bug I've looked
for alternatives and IMHO the tunnel IPsec DB entries must be made
inactive only when they can give spurious protection to packets,
i.e., with the local_mh_type=HoTi and remote_mh_type=HoT there will
never be an interesting packet matching the IPsec DB entries and
it doesn't matter to keep them. This is a new benefit of the fine
grain selectors of 2401bis.
If at the opposite there is an ESP tunnel for all packets and someone
wants to keep privacy, the obvious solution is to keep the registration
(and of course the IPsec database entries).

Francis.Dupont@enst-bretagne.fr

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



From mip6-bounces@ietf.org Mon Oct 24 13:09:01 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EU5oi-0005Tt-V1; Mon, 24 Oct 2005 13:09:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EU5og-0005RU-UO
	for mip6@megatron.ietf.org; Mon, 24 Oct 2005 13:08:59 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21091
	for <mip6@ietf.org>; Mon, 24 Oct 2005 13:08:45 -0400 (EDT)
Received: from p-mail2.rd.francetelecom.com ([195.101.245.16])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EU61T-0002UL-Qi
	for mip6@ietf.org; Mon, 24 Oct 2005 13:22:12 -0400
Received: from ftrdmel3.rd.francetelecom.fr ([10.193.117.155]) by
	ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.211); 
	Mon, 24 Oct 2005 19:08:56 +0200
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] draft-dupont-mip6-dhaadharmful-00.txt
Date: Mon, 24 Oct 2005 19:08:51 +0200
Message-ID: <D2AA6DF1AEE4404F8D983B68BAC97CD2022B914C@ftrdmel3.rd.francetelecom.fr>
Thread-Topic: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
Thread-Index: AcXYqXbXIA/i8BXYScS1SYiWXuH9KAAAVacgAAMu7pAAAUyfkA==
From: "COMBES Jean-Michel RD-MAPS-ISS" <jeanmichel.combes@francetelecom.com>
To: "Gerardo Giaretta" <Gerardo.Giaretta@TILAB.COM>,
	"Kilian Weniger" <Kilian.Weniger@eu.panasonic.com>,
	<Francis.Dupont@enst-bretagne.fr>,
	"Alexandru Petrescu" <alexandru.petrescu@motorola.com>
X-OriginalArrivalTime: 24 Oct 2005 17:08:56.0247 (UTC)
	FILETIME=[9E143470:01C5D8BD]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3d7f2f6612d734db849efa86ea692407
Content-Transfer-Encoding: quoted-printable
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Hi, =20

> -----Original Message-----
> From: mip6-bounces@ietf.org [mailto:mip6-bounces@ietf.org] On=20
> Behalf Of Gerardo Giaretta
> Sent: Monday, October 24, 2005 6:51 PM
> To: Kilian Weniger; Francis.Dupont@enst-bretagne.fr;=20
> Alexandru Petrescu
> Cc: mip6@ietf.org
> Subject: RE: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
>=20
> Hi Kilian, all,=20
>=20
> > Hi Francis, Alex,
> >=20
> > >    Both ideas have appeal to me.  Both could be supported by some
> > >    argumentation.
> > >=20
> > > =3D> this is why we should have this discussion.
> >=20
> > I agree that DNS-based DHAAD can be more secure, but one=20
> advantage of=20
> > anycast-based DHAAD I can see is that load balancing is better=20
> > supported since load conditions can be considered faster (probably=20
> > cannot be distributed fast enough in DNS).
> >
>=20
> As pointed out in draft-ietf-mip6-bootstrapping-split-01,=20
> DNS-based HA discovery may be used only to achieve=20
> coarse-grained load balancing by dynamically updating the SRV=20
> RR priorities.

If you want to update the DNS servers frequently, DNSSEC cannot be
usable:
- for each update you will have to sign the zone
- for each update you will have to transfer the signed zone to the
secondary servers
...

So forget DNSSEC in such a case: result, no more security.

>  On the other hand, DHAAD cannot be used to=20
> load balance using different HAs in different subnet.
> I still think that achieving a good load balancing solution=20
> during HA discovery/assignment is very difficult in split=20
> scenario. I tend to agree with Francis that in this scenario=20
> the load balancing issue may be solved by a HA switch solution.
>=20
> In integrated scenario it is a little bit easier and also a=20
> per-MN load balancing can be achieved relying on the AAA=20
> infrastructure (see the integrated scenario draft based on=20
> DHCP). IMO, an even better per-MN load balancing support is=20
> achieved performing HA discovery during network access=20
> authentication (e.g. via EAP or PANA), but this was discarded=20
> by the DT because of well-known reasons.
>=20
> --Gerardo

Best regards.

JMC.

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

>=20
> =20
> > > =3D> IMHO HA assignement is far better but there is not yet a
> > mechanism
> > > providing it *and* applicable in the general case.
> >=20
> > Security-wise yes. But which entity assigns the HA? And how do you=20
> > discover this HA assignment entity? And what about the signaling=20
> > overhead then? And the signaling overhead can be pretty=20
> high, e.g., if=20
> > MN first needs to request DNS to discover assignment entity and=20
> > subsequently establishes SA with assignment entity, gets HA=20
> assigned=20
> > and finally establishes SA with this HA.
> >=20
> > Wouldn't it be possible to integrate HA discovery and assignment=20
> > somehow in an IKEv2 exchange, similar as HoA assignment is=20
> integrated=20
> > in IKE exchange in the bootstrapping solution? E.g., the first IKE=20
> > message
> > (IKE_SA_INIT) sent by MN would have anycast address as destination=20
> > address (reply and all other IKE messages use unicast addresses as
> > source/destination) and the Configuration Payload in the=20
> IKE_AUTH may=20
> > contain an HA address for assignment to MN (only used if=20
> the HA that=20
> > received the anycast IKE_SA_INIT shall not be used, e.g.,=20
> because this=20
> > HA is overloaded).
> >=20
> > >=20
> > >    >  - is the DNS-based DHAAD mechanism better enough to replace=20
> > > the ICMP-base
> > >    >    one?
> >=20
> > What about the alternative to change the transport protocol, e.g.,=20
> > UDP-based instead of ICMP-based anycast DHAAD?
> >=20
> > > - AFIK, there is no way currently standardized to securely update=20
> > > anycast routing except to manually insert host routes into
> > the subnet
> > > router handling the anycast address. So maintaining an
> > anycast address
> > > would require extra maintenance effort, manually inserting and
> > deleting
> > > the routes when HAs are added or deleted.
> >=20
> > Interesting point, but isn't such a mechnism needed for almost all=20
> > anycast-based protocols? I.e., isn't there a need for such a=20
> > standardized mechanism anyway?
> >=20
> > Regards,
> >=20
> > Kilian
> >=20
> >=20
> > _______________________________________________
> > Mip6 mailing list
> > Mip6@ietf.org
> > https://www1.ietf.org/mailman/listinfo/mip6
> >=20
>=20
>=20
> Gruppo Telecom Italia - Direzione e coordinamento di Telecom=20
> Italia S.p.A.
>=20
> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> CONFIDENTIALITY NOTICE
> This message and its attachments are addressed solely to the=20
> persons above and may contain confidential information. If=20
> you have received the message in error, be informed that any=20
> use of the content hereof is prohibited. Please return it=20
> immediately to the sender and delete the message. Should you=20
> have any questions, please send an e_mail to=20
> MailAdmin@tilab.com. Thank you=20
> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=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 Oct 24 13:11:38 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EU5rG-0006CX-Na; Mon, 24 Oct 2005 13:11:38 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EU5rA-0006A1-Th
	for mip6@megatron.ietf.org; Mon, 24 Oct 2005 13:11:37 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21198
	for <mip6@ietf.org>; Mon, 24 Oct 2005 13:11:19 -0400 (EDT)
Received: from dns1.tilab.com ([163.162.42.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EU63y-0002Yr-15
	for mip6@ietf.org; Mon, 24 Oct 2005 13:24:46 -0400
Received: from iowa2k01a.cselt.it ([163.162.242.201])
	by dns1.cselt.it (PMDF V6.0-025 #38895)
	with ESMTP id <0IOV00872JQYG0@dns1.cselt.it> for mip6@ietf.org; Mon,
	24 Oct 2005 19:11:22 +0200 (MEST)
Received: from EXC01B.cselt.it ([163.162.4.199]) by iowa2k01a.cselt.it with
	Microsoft SMTPSVC(6.0.3790.211); Mon, 24 Oct 2005 19:11:22 +0200
Date: Mon, 24 Oct 2005 19:11:21 +0200
From: Gerardo Giaretta <Gerardo.Giaretta@TILAB.COM>
Subject: RE: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
To: COMBES Jean-Michel RD-MAPS-ISS <jeanmichel.combes@francetelecom.com>
Message-id: <DA62A6E0CDD1B34A84557FF1AC850C57016E9CCF@EXC01B.cselt.it>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.3790.326
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: quoted-printable
Importance: normal
Priority: normal
Thread-Topic: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
thread-index: AcXYmAy19R9rZjd5Q6uwsLFw5TPmRAAFeDcgAAJ6ldAAAVGoIA==
Content-Class: urn:content-classes:message
X-OriginalArrivalTime: 24 Oct 2005 17:11:22.0062 (UTC)
	FILETIME=[F4FDCEE0:01C5D8BD]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 825e642946eda55cd9bc654a36dab8c2
Content-Transfer-Encoding: quoted-printable
Cc: mip6@ietf.org, Kilian Weniger <Kilian.Weniger@eu.panasonic.com>,
	Francis Dupont <Francis.Dupont@enst-bretagne.fr>,
	Petrescu Alexandru-AAP021 <alexandru.petrescu@motorola.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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Hi Jean-Michel,=20

> Hi,
>=20
> IMO, we MUST have a solution permitting:=20
> o the MSP to assign only the HA he wants to allocate
> AND
> o the MN to pick a HA in from a HA list if the MSP allows such a thing
>=20

I think this is possible using DNS-based scheme defined in
draft-ietf-mip6-bootstrapping-split-01.
If in your opinion exposing HA addresses in DNS is an issue, in
integrated scenario a DHCP-based solution may be used (see the
integarted scenario draft).=20

> For the moment, with these proposals, the MSP has not the=20
> possibility to
> manage its HA as he wants ...
>=20

Why in DNS-based solution you think this is not possible?=20

> Regarding the two present solutions:
> o DNS-based DHAAD
> I don't like this solution because such mechanism gives the location,
> for a MSP, of all its HA, which are the MIPv6 point of failure and so
> the prioritized targets for "bad guys". You give the stick to=20
> be beaten
> ... :(

Sorry are you referring to DNS-based HA discovery defined in
draft-ietf-mip6-bootstrapping-split-01 or something else? I'm getting
confused with the acronym DHAAD since it is usually used to refer the
solution defined in rfc3775.

--Gerardo

> o ICMP-based mechanism
> Here again, the present mechanism gives all the HA but I=20
> think it may be
> simply modified to give only one HA if the MSP wants to assign HA.
> The main issue is regarding its security ... Maybe=20
> Alexandru's proposal
> or HAHA proposal would be interesting.
>=20
> Best regards.
>=20
> JMC.
>=20
> France Telecom - R&D Division - MAPS/NSS  =20
> Jean-Michel COMBES, Internet/Intranet Security
> E-Mail: jeanmichel.combes@francetelecom.com
> Phone: +33 (0)1 45 29 45 94
> Fax: +33 (0)1 45 29 65 19
> Mobile: +33 (0)6 07 29 30 16=20
> =20
>=20
> > -----Original Message-----
> > From: mip6-bounces@ietf.org [mailto:mip6-bounces@ietf.org] On=20
> > Behalf Of Narayanan Vidya-CVN065
> > Sent: Monday, October 24, 2005 5:21 PM
> > To: Francis Dupont; Petrescu Alexandru-AAP021
> > Cc: mip6@ietf.org; Kilian Weniger; James Kempf
> > Subject: RE: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt=20
> >=20
> > >   =20
> > > =3D> the two questions are:
> > >  - should we keep a DHAAD mechanism or HA assignment is the right=20
> > > thing
> > >    to do?
> > >  - is the DNS-based DHAAD mechanism better enough to replace the=20
> > > ICMP-base
> > >    one?
> > >=20
> >=20
> > These are good questions. I believe that a DNS-based=20
> > mechanism is largely better than an ICMP-based mechansim. For=20
> > those who wish to secure the operation, at least an option is=20
> > available. Whether DNSSEC will be widely deployed is a=20
> > separate question, but at least, it is an option. Also, it=20
> > moves away from having to configure the home network prefix=20
> > and removes the limitation of dynamic HA assignment within=20
> > the same subnet, both of which are big pluses in my mind.=20
> >=20
> > Regards,
> > Vidya
> >=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


Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia =
S.p.A.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
CONFIDENTIALITY NOTICE
This message and its attachments are addressed solely to the persons
above and may contain confidential information. If you have received
the message in error, be informed that any use of the content hereof
is prohibited. Please return it immediately to the sender and delete
the message. Should you have any questions, please send an e_mail to=20
MailAdmin@tilab.com. Thank you
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

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



From mip6-bounces@ietf.org Mon Oct 24 13:13:32 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EU5t6-0006ls-TT; Mon, 24 Oct 2005 13:13:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EU5t3-0006jB-Lg
	for mip6@megatron.ietf.org; Mon, 24 Oct 2005 13:13:30 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21281
	for <mip6@ietf.org>; Mon, 24 Oct 2005 13:13:16 -0400 (EDT)
Received: from dns2.tilab.com ([163.162.42.5])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EU65o-0002cL-Jn
	for mip6@ietf.org; Mon, 24 Oct 2005 13:26:43 -0400
Received: from iowa2k01b.cselt.it ([163.162.242.202])
	by dns2.cselt.it (PMDF V6.1 #38895)
	with ESMTP id <0IOV00A6ZJU5FQ@dns2.cselt.it> for mip6@ietf.org; Mon,
	24 Oct 2005 19:13:17 +0200 (MEST)
Received: from EXC01B.cselt.it ([163.162.4.199]) by iowa2k01b.cselt.it with
	Microsoft SMTPSVC(6.0.3790.211); Mon, 24 Oct 2005 19:10:56 +0200
Date: Mon, 24 Oct 2005 19:13:16 +0200
From: Gerardo Giaretta <Gerardo.Giaretta@TILAB.COM>
Subject: RE: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
To: COMBES Jean-Michel RD-MAPS-ISS <jeanmichel.combes@francetelecom.com>
Message-id: <DA62A6E0CDD1B34A84557FF1AC850C57016E9CD0@EXC01B.cselt.it>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.3790.326
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: quoted-printable
Importance: normal
Priority: normal
Thread-Topic: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
thread-index: AcXYqXbXIA/i8BXYScS1SYiWXuH9KAAAVacgAAMu7pAAAUyfkAAAUpTw
Content-Class: urn:content-classes:message
X-OriginalArrivalTime: 24 Oct 2005 17:10:56.0359 (UTC)
	FILETIME=[E5ABD770:01C5D8BD]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2a76bcd37b1c8a21336eb0a1ea6bbf48
Content-Transfer-Encoding: quoted-printable
Cc: mip6@ietf.org, Kilian Weniger <Kilian.Weniger@eu.panasonic.com>,
	Francis.Dupont@enst-bretagne.fr,
	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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

> > > >    Both ideas have appeal to me.  Both could be=20
> supported by some
> > > >    argumentation.
> > > >=20
> > > > =3D> this is why we should have this discussion.
> > >=20
> > > I agree that DNS-based DHAAD can be more secure, but one=20
> > advantage of=20
> > > anycast-based DHAAD I can see is that load balancing is better=20
> > > supported since load conditions can be considered faster=20
> (probably=20
> > > cannot be distributed fast enough in DNS).
> > >
> >=20
> > As pointed out in draft-ietf-mip6-bootstrapping-split-01,=20
> > DNS-based HA discovery may be used only to achieve=20
> > coarse-grained load balancing by dynamically updating the SRV=20
> > RR priorities.
>=20
> If you want to update the DNS servers frequently, DNSSEC cannot be
> usable:
> - for each update you will have to sign the zone
> - for each update you will have to transfer the signed zone to the
> secondary servers
> ...
>=20

This is why the draft says that it can be used only for a coarse-grained
load balancing. We are not saying that DNS-based scheme can be used as
an efficient load balancing solution.

--Gerardo

> So forget DNSSEC in such a case: result, no more security.
>=20
> >  On the other hand, DHAAD cannot be used to=20
> > load balance using different HAs in different subnet.
> > I still think that achieving a good load balancing solution=20
> > during HA discovery/assignment is very difficult in split=20
> > scenario. I tend to agree with Francis that in this scenario=20
> > the load balancing issue may be solved by a HA switch solution.
> >=20
> > In integrated scenario it is a little bit easier and also a=20
> > per-MN load balancing can be achieved relying on the AAA=20
> > infrastructure (see the integrated scenario draft based on=20
> > DHCP). IMO, an even better per-MN load balancing support is=20
> > achieved performing HA discovery during network access=20
> > authentication (e.g. via EAP or PANA), but this was discarded=20
> > by the DT because of well-known reasons.
> >=20
> > --Gerardo
>=20
> Best regards.
>=20
> JMC.
>=20
> France Telecom - R&D Division - MAPS/NSS  =20
> Jean-Michel COMBES, Internet/Intranet Security
> E-Mail: jeanmichel.combes@francetelecom.com
> Phone: +33 (0)1 45 29 45 94
> Fax: +33 (0)1 45 29 65 19
> Mobile: +33 (0)6 07 29 30 16
>=20
> >=20
> > =20
> > > > =3D> IMHO HA assignement is far better but there is not yet a
> > > mechanism
> > > > providing it *and* applicable in the general case.
> > >=20
> > > Security-wise yes. But which entity assigns the HA? And=20
> how do you=20
> > > discover this HA assignment entity? And what about the signaling=20
> > > overhead then? And the signaling overhead can be pretty=20
> > high, e.g., if=20
> > > MN first needs to request DNS to discover assignment entity and=20
> > > subsequently establishes SA with assignment entity, gets HA=20
> > assigned=20
> > > and finally establishes SA with this HA.
> > >=20
> > > Wouldn't it be possible to integrate HA discovery and assignment=20
> > > somehow in an IKEv2 exchange, similar as HoA assignment is=20
> > integrated=20
> > > in IKE exchange in the bootstrapping solution? E.g., the=20
> first IKE=20
> > > message
> > > (IKE_SA_INIT) sent by MN would have anycast address as=20
> destination=20
> > > address (reply and all other IKE messages use unicast addresses as
> > > source/destination) and the Configuration Payload in the=20
> > IKE_AUTH may=20
> > > contain an HA address for assignment to MN (only used if=20
> > the HA that=20
> > > received the anycast IKE_SA_INIT shall not be used, e.g.,=20
> > because this=20
> > > HA is overloaded).
> > >=20
> > > >=20
> > > >    >  - is the DNS-based DHAAD mechanism better enough=20
> to replace=20
> > > > the ICMP-base
> > > >    >    one?
> > >=20
> > > What about the alternative to change the transport=20
> protocol, e.g.,=20
> > > UDP-based instead of ICMP-based anycast DHAAD?
> > >=20
> > > > - AFIK, there is no way currently standardized to=20
> securely update=20
> > > > anycast routing except to manually insert host routes into
> > > the subnet
> > > > router handling the anycast address. So maintaining an
> > > anycast address
> > > > would require extra maintenance effort, manually inserting and
> > > deleting
> > > > the routes when HAs are added or deleted.
> > >=20
> > > Interesting point, but isn't such a mechnism needed for=20
> almost all=20
> > > anycast-based protocols? I.e., isn't there a need for such a=20
> > > standardized mechanism anyway?
> > >=20
> > > Regards,
> > >=20
> > > Kilian
> > >=20
> > >=20
> > > _______________________________________________
> > > Mip6 mailing list
> > > Mip6@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/mip6
> > >=20
> >=20
> >=20
> > Gruppo Telecom Italia - Direzione e coordinamento di Telecom=20
> > Italia S.p.A.
> >=20
> > =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> > CONFIDENTIALITY NOTICE
> > This message and its attachments are addressed solely to the=20
> > persons above and may contain confidential information. If=20
> > you have received the message in error, be informed that any=20
> > use of the content hereof is prohibited. Please return it=20
> > immediately to the sender and delete the message. Should you=20
> > have any questions, please send an e_mail to=20
> > MailAdmin@tilab.com. Thank you=20
> > =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >=20
> > _______________________________________________
> > Mip6 mailing list
> > Mip6@ietf.org
> > https://www1.ietf.org/mailman/listinfo/mip6
> >=20
>=20


Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia =
S.p.A.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
CONFIDENTIALITY NOTICE
This message and its attachments are addressed solely to the persons
above and may contain confidential information. If you have received
the message in error, be informed that any use of the content hereof
is prohibited. Please return it immediately to the sender and delete
the message. Should you have any questions, please send an e_mail to
MailAdmin@tilab.com. Thank you
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

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



From mip6-bounces@ietf.org Mon Oct 24 13:23:59 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EU63D-0000g0-Ph; Mon, 24 Oct 2005 13:23:59 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EU63B-0000fs-PW
	for mip6@megatron.ietf.org; Mon, 24 Oct 2005 13:23:58 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21775
	for <mip6@ietf.org>; Mon, 24 Oct 2005 13:23:44 -0400 (EDT)
Received: from p-mail2.rd.francetelecom.com ([195.101.245.16])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EU6Fz-0002wk-2F
	for mip6@ietf.org; Mon, 24 Oct 2005 13:37:11 -0400
Received: from ftrdmel3.rd.francetelecom.fr ([10.193.117.155]) by
	ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.211); 
	Mon, 24 Oct 2005 19:23:54 +0200
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] draft-dupont-mip6-dhaadharmful-00.txt
Date: Mon, 24 Oct 2005 19:23:51 +0200
Message-ID: <D2AA6DF1AEE4404F8D983B68BAC97CD2022B914D@ftrdmel3.rd.francetelecom.fr>
Thread-Topic: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
Thread-Index: AcXYmAy19R9rZjd5Q6uwsLFw5TPmRAAFeDcgAAJ6ldAAAVGoIAAAcJUw
From: "COMBES Jean-Michel RD-MAPS-ISS" <jeanmichel.combes@francetelecom.com>
To: "Gerardo Giaretta" <Gerardo.Giaretta@TILAB.COM>
X-OriginalArrivalTime: 24 Oct 2005 17:23:54.0919 (UTC)
	FILETIME=[B5BAAB70:01C5D8BF]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 789c141a303c09204b537a4078e2a63f
Content-Transfer-Encoding: quoted-printable
Cc: mip6@ietf.org, Kilian Weniger <Kilian.Weniger@eu.panasonic.com>,
	Francis Dupont <Francis.Dupont@enst-bretagne.fr>,
	Petrescu Alexandru-AAP021 <alexandru.petrescu@motorola.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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org


> -----Original Message-----
> From: Gerardo Giaretta [mailto:Gerardo.Giaretta@TILAB.COM]=20
> Sent: Monday, October 24, 2005 7:11 PM
> To: COMBES Jean-Michel RD-MAPS-ISS
> Cc: mip6@ietf.org; Kilian Weniger; James Kempf; Narayanan=20
> Vidya-CVN065; Francis Dupont; Petrescu Alexandru-AAP021
> Subject: RE: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
>=20
> Hi Jean-Michel,=20
>=20
> > Hi,
> >=20
> > IMO, we MUST have a solution permitting:=20
> > o the MSP to assign only the HA he wants to allocate AND o=20
> the MN to=20
> > pick a HA in from a HA list if the MSP allows such a thing
> >=20
>=20
> I think this is possible using DNS-based scheme defined in
> draft-ietf-mip6-bootstrapping-split-01.

How?

> If in your opinion exposing HA addresses in DNS is an issue, in
> integrated scenario a DHCP-based solution may be used (see the
> integarted scenario draft).=20
>=20
> > For the moment, with these proposals, the MSP has not the=20
> > possibility to
> > manage its HA as he wants ...
> >=20
>=20
> Why in DNS-based solution you think this is not possible?=20

This is the MN that will choose the HA from the listed HA in the DNS.

>=20
> > Regarding the two present solutions:
> > o DNS-based DHAAD
> > I don't like this solution because such mechanism gives the=20
> location,
> > for a MSP, of all its HA, which are the MIPv6 point of=20
> failure and so
> > the prioritized targets for "bad guys". You give the stick to=20
> > be beaten
> > ... :(
>=20
> Sorry are you referring to DNS-based HA discovery defined in
> draft-ietf-mip6-bootstrapping-split-01

Yes.

>  or something else? I'm getting
> confused with the acronym DHAAD since it is usually used to refer the
> solution defined in rfc3775.

Sorry :)

JMC.

>=20
> --Gerardo
>=20
> > o ICMP-based mechanism
> > Here again, the present mechanism gives all the HA but I=20
> > think it may be
> > simply modified to give only one HA if the MSP wants to assign HA.
> > The main issue is regarding its security ... Maybe=20
> > Alexandru's proposal
> > or HAHA proposal would be interesting.
> >=20
> > Best regards.
> >=20
> > JMC.
> >=20
> > France Telecom - R&D Division - MAPS/NSS  =20
> > Jean-Michel COMBES, Internet/Intranet Security
> > E-Mail: jeanmichel.combes@francetelecom.com
> > Phone: +33 (0)1 45 29 45 94
> > Fax: +33 (0)1 45 29 65 19
> > Mobile: +33 (0)6 07 29 30 16=20
> > =20
> >=20
> > > -----Original Message-----
> > > From: mip6-bounces@ietf.org [mailto:mip6-bounces@ietf.org] On=20
> > > Behalf Of Narayanan Vidya-CVN065
> > > Sent: Monday, October 24, 2005 5:21 PM
> > > To: Francis Dupont; Petrescu Alexandru-AAP021
> > > Cc: mip6@ietf.org; Kilian Weniger; James Kempf
> > > Subject: RE: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt=20
> > >=20
> > > >   =20
> > > > =3D> the two questions are:
> > > >  - should we keep a DHAAD mechanism or HA assignment is=20
> the right=20
> > > > thing
> > > >    to do?
> > > >  - is the DNS-based DHAAD mechanism better enough to=20
> replace the=20
> > > > ICMP-base
> > > >    one?
> > > >=20
> > >=20
> > > These are good questions. I believe that a DNS-based=20
> > > mechanism is largely better than an ICMP-based mechansim. For=20
> > > those who wish to secure the operation, at least an option is=20
> > > available. Whether DNSSEC will be widely deployed is a=20
> > > separate question, but at least, it is an option. Also, it=20
> > > moves away from having to configure the home network prefix=20
> > > and removes the limitation of dynamic HA assignment within=20
> > > the same subnet, both of which are big pluses in my mind.=20
> > >=20
> > > Regards,
> > > Vidya
> > >=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
>=20
>=20
> Gruppo Telecom Italia - Direzione e coordinamento di Telecom=20
> Italia S.p.A.
>=20
> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> CONFIDENTIALITY NOTICE
> This message and its attachments are addressed solely to the persons
> above and may contain confidential information. If you have received
> the message in error, be informed that any use of the content hereof
> is prohibited. Please return it immediately to the sender and delete
> the message. Should you have any questions, please send an e_mail to=20
> MailAdmin@tilab.com. Thank you
> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=20

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



From mip6-bounces@ietf.org Mon Oct 24 13:41:20 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EU6K0-0006SW-Jv; Mon, 24 Oct 2005 13:41:20 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EU6Jy-0006SP-LY
	for mip6@megatron.ietf.org; Mon, 24 Oct 2005 13:41:18 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22581
	for <mip6@ietf.org>; Mon, 24 Oct 2005 13:41:05 -0400 (EDT)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EU6Wl-0003VK-2k
	for mip6@ietf.org; Mon, 24 Oct 2005 13:54:32 -0400
Received: from il06exr01.mot.com (il06exr01.mot.com [129.188.137.131])
	by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id j9OHr4Nx003683
	for <mip6@ietf.org>; Mon, 24 Oct 2005 10:53:04 -0700 (MST)
Received: from de01exm69.ds.mot.com (de01exm69.am.mot.com [10.176.8.25])
	by il06exr01.mot.com (8.13.1/8.13.0) with ESMTP id j9OHp36P018865
	for <mip6@ietf.org>; Mon, 24 Oct 2005 12:51:03 -0500 (CDT)
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] draft-dupont-mip6-dhaadharmful-00.txt
Date: Mon, 24 Oct 2005 13:41:09 -0400
Message-ID: <0B40B6F9CB990B428819561A2A55613A103CB0@de01exm69.ds.mot.com>
Thread-Topic: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
Thread-Index: AcXYshVqC3Cr5Dl6R92gdU43XTtRpwAAV9iwAAH0bOAAAXzvsA==
From: "Narayanan Vidya-CVN065" <vidya@motorola.com>
To: "Gerardo Giaretta" <Gerardo.Giaretta@TILAB.COM>,
	"Kilian Weniger" <Kilian.Weniger@eu.panasonic.com>,
	<Francis.Dupont@enst-bretagne.fr>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Content-Transfer-Encoding: quoted-printable
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

>=20
> I agree that HA switch may have large signaling overhead.=20
> However, as said in my previous post I think it is quite=20
> difficult to achieve load balancing in spit scenario during=20
> HA discovery if we rule out DHAAD. In integrated scenario,=20
> the issue may be less tricky.
>=20

Hopefully, the system is not causing a lot of HA switching due to load
balancing - that would be a very unstable system. I would expect that
load balancing based HA assignment can be made at the beginning and it
would be very rare that a switch in HA for a given MN happens
subsequently due to load balancing.=20

DNS can't provide the best load balancing mechanism - however, a
commonly used method may be to use DNS to get the IP address of a HA and
have that HA assign the right HA based on load balancing (and whatever
other parameters) - so, this is almost like doing a HA switch once (at
the time of bootstrapping, say). Hopefully, after that, the MN will
continue to use that HA except in some rare cases when it is asked to
switch again.=20

Vidya

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



From mip6-bounces@ietf.org Mon Oct 24 13:41:33 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EU6KD-0006Wa-61; Mon, 24 Oct 2005 13:41:33 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EU6KC-0006WP-08
	for mip6@megatron.ietf.org; Mon, 24 Oct 2005 13:41:32 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22591
	for <mip6@ietf.org>; Mon, 24 Oct 2005 13:41:18 -0400 (EDT)
Received: from p-mail1.rd.francetelecom.com ([195.101.245.15])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EU6Wy-0003W0-1q
	for mip6@ietf.org; Mon, 24 Oct 2005 13:54:45 -0400
Received: from ftrdmel3.rd.francetelecom.fr ([10.193.117.155]) by
	ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.211); 
	Mon, 24 Oct 2005 19:41:26 +0200
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
Date: Mon, 24 Oct 2005 19:41:23 +0200
Message-ID: <D2AA6DF1AEE4404F8D983B68BAC97CD2022B914F@ftrdmel3.rd.francetelecom.fr>
Thread-Topic: General comments/questions on MIPv6 bootstrapping
Thread-Index: AcXYwgWkDQ/0p1XTTKS68lKcHibQsg==
From: "COMBES Jean-Michel RD-MAPS-ISS" <jeanmichel.combes@francetelecom.com>
To: <mip6@ietf.org>
X-OriginalArrivalTime: 24 Oct 2005 17:41:26.0966 (UTC)
	FILETIME=[28CC4D60:01C5D8C2]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Content-Transfer-Encoding: quoted-printable
Subject: [Mip6] General comments/questions on MIPv6 bootstrapping
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Hi again,

I was waiting for the proposal for the integrated scenario before to do
this email.

I have 2 main comments/questions.

The first one is regarding the fact that we have two (very) different
mechanisms for only one functionality (on one side DNS+IKEv2, on the
other side PANA+AAA+DCHP). So, personally, I am a little afraid how all
this will be managed in the user's terminal and in the MSP's network.
E.g., what will be the trigger in the terminal to know which is the
bootstrapping mechanism the terminal has to use?

My second comment is regarding the interoperability with NEMO. I believe
that if MIPv6 is deployed soon, NEMO will be deployed at the same time
because the protocol is as mature as MIPv6. So I would like to know if
the bootstrapping mechanisms working for MIPv6, will work with NEMO too.
I would like to avoid to add new mechanisms again and so increase the
complexity in a deployement architecture.

Thanks.

Best regards.

JMC.

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

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



From mip6-bounces@ietf.org Mon Oct 24 13:58:49 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EU6av-00044W-Du; Mon, 24 Oct 2005 13:58:49 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EU6as-000440-UJ
	for mip6@megatron.ietf.org; Mon, 24 Oct 2005 13:58:47 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23463
	for <mip6@ietf.org>; Mon, 24 Oct 2005 13:58:33 -0400 (EDT)
Received: from p-mail2.rd.francetelecom.com ([195.101.245.16])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EU6ng-00046X-Hg
	for mip6@ietf.org; Mon, 24 Oct 2005 14:12:00 -0400
Received: from ftrdmel3.rd.francetelecom.fr ([10.193.117.155]) by
	ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.211); 
	Mon, 24 Oct 2005 19:58:44 +0200
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] draft-dupont-mip6-dhaadharmful-00.txt
Date: Mon, 24 Oct 2005 19:58:40 +0200
Message-ID: <D2AA6DF1AEE4404F8D983B68BAC97CD2022B9151@ftrdmel3.rd.francetelecom.fr>
Thread-Topic: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
Thread-Index: AcXYshVqC3Cr5Dl6R92gdU43XTtRpwAAV9iwAAH0bOAAAXzvsAAAnOUg
From: "COMBES Jean-Michel RD-MAPS-ISS" <jeanmichel.combes@francetelecom.com>
To: "Narayanan Vidya-CVN065" <vidya@motorola.com>,
	"Gerardo Giaretta" <Gerardo.Giaretta@TILAB.COM>,
	"Kilian Weniger" <Kilian.Weniger@eu.panasonic.com>,
	<Francis.Dupont@enst-bretagne.fr>
X-OriginalArrivalTime: 24 Oct 2005 17:58:44.0059 (UTC)
	FILETIME=[92F422B0:01C5D8C4]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
Content-Transfer-Encoding: quoted-printable
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org


=20

> -----Original Message-----
> From: mip6-bounces@ietf.org [mailto:mip6-bounces@ietf.org] On=20
> Behalf Of Narayanan Vidya-CVN065
> Sent: Monday, October 24, 2005 7:41 PM
> To: Gerardo Giaretta; Kilian Weniger; Francis.Dupont@enst-bretagne.fr
> Cc: mip6@ietf.org
> Subject: RE: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
>=20
> >=20
> > I agree that HA switch may have large signaling overhead.=20
> > However, as said in my previous post I think it is quite=20
> difficult to=20
> > achieve load balancing in spit scenario during HA discovery=20
> if we rule=20
> > out DHAAD. In integrated scenario, the issue may be less tricky.
> >=20
>=20
> Hopefully, the system is not causing a lot of HA switching=20
> due to load balancing - that would be a very unstable system.=20
> I would expect that load balancing based HA assignment can be=20
> made at the beginning and it would be very rare that a switch=20
> in HA for a given MN happens subsequently due to load balancing.

Maybe but we have to take such a scenario into account.
=20
>=20
> DNS can't provide the best load balancing mechanism -=20
> however, a commonly used method may be to use DNS to get the=20
> IP address of a HA and have that HA assign the right HA based=20
> on load balancing (and whatever other parameters)

So, why this HA - the one assigning the right HA - needs to have HA
functionality?

>  - so, this=20
> is almost like doing a HA switch once (at the time of=20
> bootstrapping, say). Hopefully, after that, the MN will=20
> continue to use that HA except in some rare cases when it is=20
> asked to switch again.=20
>=20
> Vidya
>=20
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
>=20

JMC.

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

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



From mip6-bounces@ietf.org Mon Oct 24 14:08:07 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EU6jv-0006oq-QP; Mon, 24 Oct 2005 14:08:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EU6jt-0006oB-JH
	for mip6@megatron.ietf.org; Mon, 24 Oct 2005 14:08:05 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23895
	for <mip6@ietf.org>; Mon, 24 Oct 2005 14:07:52 -0400 (EDT)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EU6wd-0004OB-2L
	for mip6@ietf.org; Mon, 24 Oct 2005 14:21:19 -0400
Received: from il06exr04.mot.com (il06exr04.mot.com [129.188.137.134])
	by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id j9OIJpFJ008345
	for <mip6@ietf.org>; Mon, 24 Oct 2005 11:19:51 -0700 (MST)
Received: from de01exm69.ds.mot.com (de01exm69.am.mot.com [10.176.8.25])
	by il06exr04.mot.com (8.13.1/8.13.0) with ESMTP id j9OIFuq5018966
	for <mip6@ietf.org>; Mon, 24 Oct 2005 13:15:56 -0500 (CDT)
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] draft-dupont-mip6-dhaadharmful-00.txt
Date: Mon, 24 Oct 2005 14:07:56 -0400
Message-ID: <0B40B6F9CB990B428819561A2A55613A103CE1@de01exm69.ds.mot.com>
Thread-Topic: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
Thread-Index: AcXYshVqC3Cr5Dl6R92gdU43XTtRpwAAV9iwAAH0bOAAAXzvsAAAnOUgAAByKzA=
From: "Narayanan Vidya-CVN065" <vidya@motorola.com>
To: "COMBES Jean-Michel RD-MAPS-ISS" <jeanmichel.combes@francetelecom.com>,
	"Gerardo Giaretta" <Gerardo.Giaretta@TILAB.COM>,
	"Kilian Weniger" <Kilian.Weniger@eu.panasonic.com>,
	<Francis.Dupont@enst-bretagne.fr>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Content-Transfer-Encoding: quoted-printable
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

> >=20
> > DNS can't provide the best load balancing mechanism - however, a=20
> > commonly used method may be to use DNS to get the IP=20
> address of a HA=20
> > and have that HA assign the right HA based on load balancing (and=20
> > whatever other parameters)
>=20
> So, why this HA - the one assigning the right HA - needs to=20
> have HA functionality?
>=20

It doesn't. It would be a light-weight "HA assigning entity" - but it
may very well be a logical entity collocated with the HA.=20

Vidya

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



From mip6-bounces@ietf.org Mon Oct 24 14:16:53 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EU6sO-0001Gv-WA; Mon, 24 Oct 2005 14:16:53 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EU6sN-0001Gp-MU
	for mip6@megatron.ietf.org; Mon, 24 Oct 2005 14:16:51 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24366
	for <mip6@ietf.org>; Mon, 24 Oct 2005 14:16:37 -0400 (EDT)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EU75B-0004gI-9r
	for mip6@ietf.org; Mon, 24 Oct 2005 14:30:05 -0400
Received: from il06exr02.mot.com (il06exr02.mot.com [129.188.137.132])
	by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id j9OISdmB009731;
	Mon, 24 Oct 2005 11:28:39 -0700 (MST)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by il06exr02.mot.com (8.13.1/8.13.0) with ESMTP id j9OIPJ6H026996;
	Mon, 24 Oct 2005 13:25:20 -0500 (CDT)
Message-ID: <435D250B.6040507@motorola.com>
Date: Mon, 24 Oct 2005 20:16:43 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: Henrik Levkowetz <henrik@levkowetz.com>
Subject: Re: [Mip6] More comments on draft-ietf-mip6-nemo-v4traversal-00.txt
References: <435CF254.6050508@motorola.com> <435D0459.8050605@levkowetz.com>
In-Reply-To: <435D0459.8050605@levkowetz.com>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 17bdfcaea25d1444baef0e24abc38874
Content-Transfer-Encoding: 7bit
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Henrik Levkowetz wrote:

> Hi Alexandru,
> 
> on 2005-10-24 16:40 Alexandru Petrescu said the following:
> [...]
> 
>>I have some comments.
>>
>>
>>>The current Mobile IPv6 specification and [NEMO] do not allow mobile
>>> nodes to use an IPv4 home address or prefix, respectively.
>>
>>That is largely true.  Note though that recently there is a personal
>>draft on NEMO for IPv4 home prefix that uses MIP4 and no MIP6.
> 
> Right.  But that isn't in the current spec, which is the base for what
> this draft is attempting to expand.  We should check the draft you
> refer to (name?) to make sure good ideas are incorporated in the
> v4traversal work, though.

The draft I'm referring to proposes a message extension to MIP4
Registration Request and Reply such as to carry Mobile Network Prefixes,
or home prefixes.  The name of the draft is
http://www.ietf.org/internet-drafts/draft-leung-nemov4-base-00.txt

>>>Mobile IPv6 offers a number of improvements over Mobile IPv4, mainly
>>> due to capabilities inherited from IPv6. For instance, route 
>>>optimization and Dynamic home agent discovery can only be achieved 
>>>with Mobile IPv6.
>>
>>Maybe exemplify MIP6 superiority on MIP4 by something else than DHAAD,
>>itself being questioned by the dhaad-harmful discussions, and
>>acknowledged by this draft's section 2.1.
> 
> 
> Humm?  The draft says "Dynamic home agent discovery", not DHAAD.  We've
> been keeping up with what's being proposed in the bootstrapping work.

Oh, sorry terminology error on my part.  "Dynamic home agent discovery"
sounds so much like DHAAD of RFC3775 so I may have mis-interpreted.  If
so, it still looks a bit uncomfortable to claim MIP6 is better than MIP4
because it does "Dynamic home agent discovery", an operation not yet
standardized.

But I agree I may have a different way of expecting the future than
others, so I'd avoid speculating further.

>>RO is another case.  There are no widely deployed RO-enabled CNs while
>>IPv4 non-RO CNs are plenty, so one can't really claim MIP6 is superior
>>to MIP4 because it has RO.
> 
> No?  So the future potential of RO is of no interest?

It is.  What I've learned is that when IPv6 CNs get deployed they'll
most likely be RO-enabled, which would make MIP6 superiority statements
necessarily weighted by 'when IPv6 gets deployed'.

>>>We also assume that the Home Agent is always reachable through a 
>>>globally unique IPv4 address.
>>
>>I would like a DSMIPv6 solution to assume that the HAv6 is only
>>reachable by its v6 address.  That would help widespread adoption of
>>IPv6 by offering one less dependency on IPv4.
> 
> 
> If we're trying to solve the problem of providing MIPv6 functionality
> for a MN / MR which only has IPv4 access, it is not a solution to say
> that the HA only is reachable through a IPv6 address...
> 
> Or have I misunderstood the drift of your comment??

Sorry, I'm not trying to drift.  The problem was initially to make a v6
MN capable to do MIP6 even if connected to a v4-only access network,
eventually through NAT.  The essential mechanism proposed in the draft
(v4 address in BU) was the original motivator.

That problem had no requirement to give v4 Home Address to a MIP6-only
MN.  To develop a solution for that initial problem, there is no need
for HA to have a public v4 address.  Requiring the HA to have a public
v4 address is further enhancing the problem.

Once a v4 and a v6 public addresses are required for HA, it leads (IMHO)
to MN to run both MIP4 and MIP6.  Running both MIP4 and MIP6 being
inefficient is questionable.

There exist no widely-deployed IPv6-only access network.  If it existed,
then it would have generated a need for MNs that run MIP6 and need a v4
Home Address to connect to a v4 HA.

>>In case the MN has v4-only applications on it, and needs to continuously
>>accessed IPv4 Home Address then I suggest porting these applications to
>>IPv6.  In this case MIP6 is used as an advantage of IPv6: if an
>>application is ported from IPv4 to IPv6 then it gets ability to run
>>uninterrupted and use a permanent Home Address, and does not need MIP4.
> 
> 
> I think this still does not in any way solve the problem of a MIPv6
> MN/MR which finds itself in a visited network with only IPv4 access...

Well, I think it does.  If all user applications on that MN are
IPv6-enabled then the MN would use only pppd/dhcpcd to get an IPv4 "CoA"
and some UDPv4 tunnelling software and a an IPv6 default route towards
the tunnel interface, and send BU through it.  Then user launches IPv6
html browser (or whatever other IPv6-enabled user application) and
continuous access to the v6 Home Address is ok.

>>>For DNS lookup by service, the SRV record defined in [BOOT] is 
>>>reused.  For instance, if the service name is "mip6ha" and the 
>>>protocol name is "ipv6" for the SRV record, the mobile node SHOULD 
>>>send a DNS request with the QNAME set to "mip6ha.ipv6.example.com". 
>>>The response should contain the home agent's FQDN(s) and may have the
>>> corresponding 'AAAA' and 'A' records enclosed as well.
>>
>>This is another discussion, but I just mention it here.  This method for
>>HAD does not specify a means for the HAs to co-operate with each other
>>to establish their preferences.  With DNS-based it is left entirely to
>>the MN to choose among the HAs addresses.
> 
> 
> No.  Look at the SRV specification again.  It provides for priorities
> between multiple choices, and fallback to backup hosts if the preferred
> ones are down.

Thanks, I have to re-check that.  I think I meant to say that the DNS
method would still require the HAs to co-ordinate amongst themselves to
tell DNS what those priorities are.  I think MIP6 doesn't say how to do
that, today.

>>>2.3.1 Foreign network supports IPv6
>>
>>This scenario is not described in the initial list of scenarios at 1.2
>>"Scenarios considered by this specification".  Section 1.2 only lists
>>access networks as IPv4.
> 
> 
> Should be fixed.

I was thinking to suggest to fix it by leaving the 'Scenarios' section
as is, because there exist no widely deployed IPv6-only access networks.

>>>4.1. NAT detection and traversal
>>
>>This section is very important for proper working of NAT detection and
>>traversal.  However, it has some issues right now.
>>
>>
>>>The binding acknowledgement, and all future packets are then
>>>encapsulated in UDP and IPv4. The source address in the IPv4 header
>>>is the IPv4 address of the home agent. The destination address is the
>>>IPv4 address received in the IPv4 header encapsulating the binding
>>>update (this address will be different from the IPv4 care-of address
>>>if a NAT were present in the path).
>>>
>>>Upon receiving the binding acknowledgement with the NAT detection 
>>>option, the mobile node sets the tunnel to the home agent to UDP 
>>>encapsulation.
>>
>>Actually there is more to happen between the two paragraphs.  Current
>>implemented NATs have no idea about this draft, so they don't currently
>>implement it.
> 
> 
> No NAT should ever implement this draft.  I think there's some mis-
> understanding here.

I think I've just written it as a statement and I don't suggest this
draft to modify the NATs.  I think I am in agreement with you by saying
that this draft does not modify the NATs.

>>A NAT needs to know a way for forwarding the BAck from the HA to MN.
>>The v4 dst address in that UDPv4-encapsulated BAck is the NAT address
>>itself.  In order for NAT to forward the packet to MN (and re-write the
>>IPv4 dst address) it sometimes uses port numbers.  That's why UDP.  Or,
>>there's no mention of UDP numbers in this section.
> 
> 
> ??  You can't have UDP encapsulation without UDP numbers.  I don't
> understand...

Sorry, I think I meant to say that the HA should exchange the port
numbers received in the UDP-encapsulated BU and use them to fill the
port numbers for the UDP-encapsulated BAck (src becomes dst and
viceversa).  But this may be seen as natural UDP processing...

>>And, when port numbers are used to facilitate ip address rewriting by
>>NAT, they are not fixed, they're dynamically changing.  Which would
>>demand more enhancement to this section.
> 
> 
> Hmm.  I don't see that.  MIPv4 NAT traversal (RFC 3519) definitely works,
> and the protocol as described here uses the same basic mechanism.

Oh well, I see, thanks for pointing to RFC 3519.

First, the draft has no mention of RFC 3519, so it should.  For example,
RFC 3519 has a relatively deep discussion on what happens when the
mapping is lost at NAT, a thing which should happen in this draft too.
Up to the authors to refer to the RFC or re-describe here the mechanism
to use BU/BAck as 'heartbeat' or 'keepalive'.

Second, I think RFC 3519 describes no means for MN to discover what UDP
port numbers are open at NAT.  The worst NAT I've experimented with has
very few of them; and it's not 25 nor 80, it's 1755.  My knowledge of
RFC 3519 may be not very good, please indicate if I'm wrong.

IMHO, what is needed is for both MN and HA to gain dynamic knowledge of
both the IPv4 public address of NAT _and_ the UDP port numbers that are
open at NAT.  Without that MN and HA can't communicate.

Third, RFC 3519 does describe a means to re-establish NAT state (or
mapping) when the HA does not reply.  However, it does not - and
probably can not - provide a means for NAT to explicitely indicate MN
that its state has changed.  This may have an unfortunate effect on MN,
because all it sees is that its HA does not reply back.  Or, with NEMOv6
DHAAD - again DHAAD :-) - the MN may take this lack of BAck from HA as a
need to switch to another HA.

> Could you suggest some text?

Too early for me to suggest text since what I've said above is just
recognizing some particular NAT behaviour that makes RFC 3519 not work
in all NAT cases, IMHO.

Probably the best thing I could suggest is the draft to refer to RFC
3519, in a first phase.

>>>"Dual Stack Mobile IPv6 (DSMIPv6)"
>>
>>The title may not be very adapted.  It makes one somehow think about
>>Dual-Stack MIP4 and MIP6, since 'dual-stack' is usually 'IPv4 stack and
>>IPv6 stack'.  Or, the mechanism proposed is more about enhancing MIP6
>>with some v4 features.  Maybe "v4-enhanced MIP6" would be better.
> 
> 
> Agreed.  That should be fixed in the next revision.

Thanks for noting.

Alex


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



From mip6-bounces@ietf.org Mon Oct 24 14:20:51 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EU6wF-0001jc-36; Mon, 24 Oct 2005 14:20:51 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EU6w9-0001jJ-5A
	for mip6@megatron.ietf.org; Mon, 24 Oct 2005 14:20:49 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24545
	for <mip6@ietf.org>; Mon, 24 Oct 2005 14:20:30 -0400 (EDT)
Received: from motgate.mot.com ([129.188.136.100])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EU78t-0004mi-5W
	for mip6@ietf.org; Mon, 24 Oct 2005 14:33:58 -0400
Received: from az33exr04.mot.com (az33exr04.mot.com [10.64.251.234])
	by motgate.mot.com (Motorola/Motgate) with ESMTP id j9OIKZTD015191;
	Mon, 24 Oct 2005 11:20:35 -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 j9OIRIcG009978;
	Mon, 24 Oct 2005 13:27:19 -0500 (CDT)
Message-ID: <435D25EF.2000302@motorola.com>
Date: Mon, 24 Oct 2005 20:20:31 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
Subject: Re: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
References: <200510241610.j9OGA2rV082832@givry.rennes.enst-bretagne.fr>
In-Reply-To: <200510241610.j9OGA2rV082832@givry.rennes.enst-bretagne.fr>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Content-Transfer-Encoding: 7bit
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Francis Dupont wrote:

>  In your previous mail you wrote:
> 
>    > => this is more an argument for HA-switch (another way to provide HA
>    > assignment)...
>    
>    Thanks, where is HA-switch discussed, drafted?
>    
> => draft-haley-mip6-ha-switch-00.txt and (more general)
> draft-devarapalli-mip6-nemo-local-haha-00.txt
> 
> I believe one of these I-Ds was proposed for the MIPv6 agenda.
> 
>    > The issue with the anycast-like address is the responder must be
>    > always the same box in order to use correctly IPsec.
>    
>    I don't buy into that.  It's like saying that because of IPsec two boxes
>    aren't allowed to have same IPv6 address.  It's also ignoring that the
>    "unique IP address per box" concept no longer exists since "server farms
>    and blades", "IP over VIA" and "modem connected to PDA" got widespread use.
>    
> => multiple sources don't work well when two of the security services
> are "source origin authentication" and "anti-replay". IPsec is just
> not the right protocol here.

I intuitively agree.  I was thinking we may look at msec WG results for
help securing DHAAD, but if solution is not immediately available then
jus use some other 'group' address for the HAs instead of the anycast
address.  I would also look at e.g. SEND, because ND normally uses
groups a lot.

>    > IMHO the best way to protect current DHAAD is per exchange and not
>    > per communication but the real issue is the effort doesn't worth it.
>    
>    exchange vs. communication?
>    
> => exchange := request/reply, communication:= stream of exchanges.
> IPsec or SSL/TLS are stream/session oriented, an exchange oriented
> security protocol should use per message signature and similar ideas,
> not a session key with an anti-replay mechanism.
> The problem here is the standard security protocol (IPsec) is not
> convenient and to add security from scratch is known to be hard,
> so it is better to use something more suitable, DNSSEC is fine because
> it has both (in an exchange oriented style BTW) transaction and data
> protections...

Ok, let try to parse that...

Alex


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



From mip6-bounces@ietf.org Mon Oct 24 14:27:27 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EU72d-00043T-7l; Mon, 24 Oct 2005 14:27:27 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EU72b-00043G-CA
	for mip6@megatron.ietf.org; Mon, 24 Oct 2005 14:27:25 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24897
	for <mip6@ietf.org>; Mon, 24 Oct 2005 14:27:11 -0400 (EDT)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EU7FO-0004zm-Am
	for mip6@ietf.org; Mon, 24 Oct 2005 14:40:39 -0400
Received: from il06exr02.mot.com (il06exr02.mot.com [129.188.137.132])
	by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id j9OIdCOo011339;
	Mon, 24 Oct 2005 11:39:12 -0700 (MST)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by il06exr02.mot.com (8.13.1/8.13.0) with ESMTP id j9OIZp9N001060;
	Mon, 24 Oct 2005 13:35:52 -0500 (CDT)
Message-ID: <435D2783.8080702@motorola.com>
Date: Mon, 24 Oct 2005 20:27:15 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: Narayanan Vidya-CVN065 <vidya@motorola.com>
Subject: Re: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
References: <0B40B6F9CB990B428819561A2A55613A103C28@de01exm69.ds.mot.com>
In-Reply-To: <0B40B6F9CB990B428819561A2A55613A103C28@de01exm69.ds.mot.com>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Content-Transfer-Encoding: 7bit
Cc: mip6@ietf.org, Kilian Weniger <Kilian.Weniger@eu.panasonic.com>,
	Francis Dupont <Francis.Dupont@enst-bretagne.fr>,
	James Kempf <Kempf@docomolabs-usa.com>,
	Petrescu Alexandru-AAP021 <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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Narayanan Vidya-CVN065 wrote:

> 
>> Sorry, term just been invented minutes ago, it's like having
>> a version of DHAAD without using anycast addresses, because
>> current DHAAD delies on anycast addresses and IPsec can't run
>> with them.
> 
> 
> OK. So, what is the destination address for DHAAD?

The DHAAD Request would be sent to a 'reserved' address that is derived
from the home link prefix, called 'all HAs for DHAAD".  The HAs select
amongst themselves a 'leader' and only one of them replies back, using
src IPv6 address as its own globally unique IPv6 address (not the
'reserved' address).

Example of such reserved address could be
3ffe:dddd:eeee:aaaa:fefff:ffff:ffff:ffee (note the common part
                    fefff:ffff:ffff:ffee)

Every HA on the home link would have the address
3ffe:dddd:eeee:aaaa:fefff:ffff:ffff:ffee assigned to its interface and
do NA for it as if it were a normal IPv6 address, and it would also have
 assigned its globally unique IPv6 address (derived from
3ffe:dddd:eeee:aaaa:EUI-64).

The HAs select amongst themselves a leader with the tool that MIP6
provides which is the H bit in the RA a HA sends on the link.

>> > When you are doing discovery based on service name - say, "mip6" -
>> > this is equivalent to zero config - it is a well known service name
>> > and doesn't really require per-MN configuration.
>>
>> My turn to be ignorant, is it like MN could interrogate local
>> DNS telling it "give me the address of my HA"?  What would
>> DNS use to identify that MN and send it back its proper HA
>> (and not some other MN's HA)?
>>
> 
> Typically, I have seen DNS-based HA discovery to use say,
> "mip6.domain1.com", where the MN belongs to domain1.com. If the MN is
> trying to discover an HA in the local domain it is connected to, it
> could simply use a service-based discovery using "mip6" as the service
> name - in this case, a HA locally present in that domain would be
> returned. If the MN is discovering a home agent in its domain, it would
> use the former. It already knows its domain (for other purposes) and
> "mip6" is a well-known prefix in this case.

"For other purposes"?  How does it auto-configure that domain1.com
without having IP up?  IP must be up for that auto-configuration to
work, otherwise it will have to be handwritten on the mobile somehow.

Just some remarks...

Alex


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



From mip6-bounces@ietf.org Mon Oct 24 14:31:23 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EU76R-0005b4-3x; Mon, 24 Oct 2005 14:31:23 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EU76O-0005ar-Q1
	for mip6@megatron.ietf.org; Mon, 24 Oct 2005 14:31:20 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25063
	for <mip6@ietf.org>; Mon, 24 Oct 2005 14:31:07 -0400 (EDT)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EU7JA-00056Z-Ro
	for mip6@ietf.org; Mon, 24 Oct 2005 14:44:35 -0400
Received: from il06exr04.mot.com (il06exr04.mot.com [129.188.137.134])
	by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id j9OIh4t3011882;
	Mon, 24 Oct 2005 11:43:04 -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 j9OId7EN027887;
	Mon, 24 Oct 2005 13:39:08 -0500 (CDT)
Message-ID: <435D286B.4060708@motorola.com>
Date: Mon, 24 Oct 2005 20:31:07 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
Subject: Re: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
References: <200510241630.j9OGUJJ6082956@givry.rennes.enst-bretagne.fr>
In-Reply-To: <200510241630.j9OGUJJ6082956@givry.rennes.enst-bretagne.fr>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Content-Transfer-Encoding: 7bit
Cc: James Kempf <Kempf@docomolabs-usa.com>, 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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Francis Dupont wrote:

> In your previous mail you wrote:
> 
>> This is just my ignorance - what is non-anycast DHAAD? :)
> 
> Sorry, term just been invented minutes ago, it's like having a 
> version of DHAAD without using anycast addresses, because current 
> DHAAD delies on anycast addresses and IPsec can't run with them.
> 
> => what I don't understand is how the MN gets first the non-anycast 
> address?

Well, if we say that the non-anycast address is reserved somehow, then
it is sufficient for the user of MN to preconfigure the home prefix on
it, manually somehow.  Then add to it the 'reserved' feff:ffff:ffff:ffee
(which is not anycast) and it obtains a reserved IPv6 address that says
"all HAs on the home link for DHAAD".

> If it has already a HA and wants just to get other available HA IMHO 
> HA-switch (as a re-assignment mechanism) is a better solution.

Well, DHAAD Reply contains a list of HAs ordered by priorities.  Once it
has that list the MN could switch to another one, provided of course
that the HAs have their BCs synched.

>> When you are doing discovery based on service name - say, "mip6" - 
>> this is equivalent to zero config - it is a well known service name
>>  and doesn't really require per-MN configuration.
> 
> => I disagree a bit: you need a name (FQDN) to query about.
> 
> My turn to be ignorant, is it like MN could interrogate local DNS 
> telling it "give me the address of my HA"?  What would DNS use to 
> identify that MN and send it back its proper HA (and not some other 
> MN's HA)?
> 
> => a property of the DNS (and of the current DHAAD but this could be 
> changed) is the answer should never rely on who sends the question or
>  where it comes from. So "my HA" doesn't make sense, but of course 
> "myHA.example.com" or "...msp.example.com" do.

I agree, the user still has to pre-configure "example.com" on mobile.

Alex


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



From mip6-bounces@ietf.org Mon Oct 24 14:34:40 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EU79c-0006uY-5S; Mon, 24 Oct 2005 14:34:40 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EU79Z-0006tu-RE
	for mip6@megatron.ietf.org; Mon, 24 Oct 2005 14:34:37 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25258
	for <mip6@ietf.org>; Mon, 24 Oct 2005 14:34:24 -0400 (EDT)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EU7MM-0005Fr-Lq
	for mip6@ietf.org; Mon, 24 Oct 2005 14:47:52 -0400
Received: from il06exr04.mot.com (il06exr04.mot.com [129.188.137.134])
	by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id j9OIkOpR012434;
	Mon, 24 Oct 2005 11:46:24 -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 j9OIgRRS029176;
	Mon, 24 Oct 2005 13:42:28 -0500 (CDT)
Message-ID: <435D2933.8060103@motorola.com>
Date: Mon, 24 Oct 2005 20:34:27 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: Narayanan Vidya-CVN065 <vidya@motorola.com>
Subject: Re: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
References: <0B40B6F9CB990B428819561A2A55613A103C54@de01exm69.ds.mot.com>
In-Reply-To: <0B40B6F9CB990B428819561A2A55613A103C54@de01exm69.ds.mot.com>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Content-Transfer-Encoding: 7bit
Cc: mip6@ietf.org, Kilian Weniger <Kilian.Weniger@eu.panasonic.com>,
	Francis.Dupont@enst-bretagne.fr, James Kempf <Kempf@docomolabs-usa.com>,
	Petrescu Alexandru-AAP021 <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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Narayanan Vidya-CVN065 wrote:

>>   
>> => what I don't understand is how the MN gets first the
>> non-anycast address?
> 
> I have the same confusion.

It manually configures its home link prefix (instead of pre-configuring
"home.com") and then it adds to it a 'reserved' suffix like
feff:ffff:ffff:ffee which is not anycast.

>> If it has already a HA and wants just to
>> get other available HA IMHO HA-switch (as a re-assignment
>> mechanism) is a better solution.
> 
> Yes, this is a switch case and not a bootstrapping case.
> 
>>
>>    > When you are doing discovery based on service name -
>> say, "mip6" - this
>>    > is equivalent to zero config - it is a well known
>> service name and
>>    > doesn't really require per-MN configuration.
>>   
>> => I disagree a bit: you need a name (FQDN) to query about.
>>
> 
> True. The FQDN can be a common and well-known one - that was really my
> point.

It can't be "well-known" like "well-known port numbers".  A user of a
mobile may pre-configure "home.com" while another may reconfigure
"house.com", if the two users have different home networks, different
home providers.

>> => a property of the DNS (and of the current DHAAD but this
>> could be changed) is the answer should never rely on who
>> sends the question or where it comes from. So "my HA" doesn't
>> make sense, but of course "myHA.example.com"
>> or "...msp.example.com" do.
>>
> 
> Yes, so - "example.com" is something the MN already knows (it most
> likely belongs to example.com"). If "myHA" is the well known service
> name for mip6 HAs, "myHA.example.com" can be created by the MN easily. I
> suppose one could argue that it still requires *some* configuration - it
> seems to be still better than configuring a particular home subnet to me.

Same with non-anycast DHAAD, the mobile must have some
pre-configuration, like the home link prefix, which makes more sense
that pre-configuring a domain name I believe.

Alex


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



From mip6-bounces@ietf.org Mon Oct 24 14:40:35 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EU7FL-0000B2-4T; Mon, 24 Oct 2005 14:40:35 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EU7FJ-0000Ax-8g
	for mip6@megatron.ietf.org; Mon, 24 Oct 2005 14:40:33 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25500
	for <mip6@ietf.org>; Mon, 24 Oct 2005 14:40:19 -0400 (EDT)
Received: from ftpbox.mot.com ([129.188.136.101])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EU7S6-0005QO-Cn
	for mip6@ietf.org; Mon, 24 Oct 2005 14:53:47 -0400
Received: from az33exr04.mot.com (az33exr04.mot.com [10.64.251.234])
	by ftpbox.mot.com (Motorola/Ftpbox) with ESMTP id j9OIeSsL005065;
	Mon, 24 Oct 2005 11:40:28 -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 j9OIlBtb021831;
	Mon, 24 Oct 2005 13:47:12 -0500 (CDT)
Message-ID: <435D2A96.6020108@motorola.com>
Date: Mon, 24 Oct 2005 20:40:22 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: Gerardo Giaretta <Gerardo.Giaretta@TILAB.COM>
Subject: Re: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
References: <DA62A6E0CDD1B34A84557FF1AC850C57016E9CCB@EXC01B.cselt.it>
In-Reply-To: <DA62A6E0CDD1B34A84557FF1AC850C57016E9CCB@EXC01B.cselt.it>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Content-Transfer-Encoding: 7bit
Cc: mip6@ietf.org, Kilian Weniger <Kilian.Weniger@eu.panasonic.com>,
	Francis.Dupont@enst-bretagne.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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Gerardo Giaretta wrote:

>  > > => IMHO load balancing should not be provided by a DHAAD mechanism
> 
>>>but by HA assignment or HA-switch.
>>
>>I agree that HA-switch is needed (not only for load balancing), but if
>>an DHAAD mechanism already supports load balancing, signaling overhead
>>and delay can be saved by skipping a subsequent HA-switch. If MNs
>>frequently bootstrap with new HAs (e.g., when always using local HAs),
>>the saved signaling overhead and delay might be significant. 
>>
> 
> 
> I agree that HA switch may have large signaling overhead. However, as
> said in my previous post I think it is quite difficult to achieve load
> balancing in spit scenario during HA discovery if we rule out DHAAD. In
> integrated scenario, the issue may be less tricky.

Assume for a moment that RFC 3775 DHAAD had no issue with using IPsec
and that anycast implementation were deployed, dynamic update of routes
such that anycast really works.

Would then RFC 3775 DHAAD provide 'load balancing'?

I'm asking because I think it is not at all clear for everyone what
'load balancing' is and how MIP6 is concerned by load balancing.

My own take on this is that even if RFC 3775 worked it wouldn't provide
'load balancing' per se.  But, if the HAs co-ordinated themselves
somehow with some existing load balancing protocol then load balancing
would be achieved, because the HA list provided in DHAAD Reply and the
HA list used by MN would allow MN to switch towards wherever the load is
minimal.

Alex


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



From mip6-bounces@ietf.org Mon Oct 24 14:58:59 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EU7X9-0005jG-1N; Mon, 24 Oct 2005 14:58:59 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EU7X7-0005jB-GF
	for mip6@megatron.ietf.org; Mon, 24 Oct 2005 14:58:57 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26247
	for <mip6@ietf.org>; Mon, 24 Oct 2005 14:58:41 -0400 (EDT)
From: Basavaraj.Patil@nokia.com
Received: from mgw-ext01.nokia.com ([131.228.20.93])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EU7js-0005vI-Cp
	for mip6@ietf.org; Mon, 24 Oct 2005 15:12:09 -0400
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211])
	by mgw-ext01.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id
	j9OIwqwX017705 for <mip6@ietf.org>; Mon, 24 Oct 2005 21:58:52 +0300
Received: from daebh101.NOE.Nokia.com ([10.241.35.111]) by
	esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 24 Oct 2005 21:58:52 +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 Oct 2005 13:58:25 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5.7233.31
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 24 Oct 2005 13:58:27 -0500
Message-ID: <456943D540CFC14A8D7138E64843F85301E89CBA@daebe101.NOE.Nokia.com>
Thread-Topic: Draft Agenda for meeting at IETF64
Thread-Index: AcXYzOpFn+pkOXq6T7ypUHjMZNOQ6g==
To: <mip6@ietf.org>
X-OriginalArrivalTime: 24 Oct 2005 18:58:25.0926 (UTC)
	FILETIME=[E9E9AA60:01C5D8CC]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de
Content-Transfer-Encoding: quoted-printable
Subject: [Mip6] Draft Agenda for meeting at IETF64
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org


Hello,

The draft agenda of the meeting is posted at:
http://www3.ietf.org/proceedings/05nov/agenda/mip6.txt

Please review the same and if you have requested a slot and
do not see it on the agenda, please contact me.

-BPa

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



From mip6-bounces@ietf.org Mon Oct 24 15:15:00 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EU7me-0001U1-1T; Mon, 24 Oct 2005 15:15:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EU7mc-0001Tw-8i
	for mip6@megatron.ietf.org; Mon, 24 Oct 2005 15:14:58 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26897
	for <mip6@ietf.org>; Mon, 24 Oct 2005 15:14:44 -0400 (EDT)
Received: from av7-1-sn3.vrr.skanova.net ([81.228.9.181])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EU7zP-0006NC-QC
	for mip6@ietf.org; Mon, 24 Oct 2005 15:28:12 -0400
Received: by av7-1-sn3.vrr.skanova.net (Postfix, from userid 502)
	id 19F7837F26; Mon, 24 Oct 2005 21:07:07 +0200 (CEST)
Received: from smtp3-2-sn3.vrr.skanova.net (smtp3-2-sn3.vrr.skanova.net
	[81.228.9.102]) by av7-1-sn3.vrr.skanova.net (Postfix) with ESMTP
	id F1B3A37F18; Mon, 24 Oct 2005 21:07:06 +0200 (CEST)
Received: from shiraz.levkowetz.com (81-224-201-50-no45.tbcn.telia.com
	[81.224.201.50])
	by smtp3-2-sn3.vrr.skanova.net (Postfix) with ESMTP id 1321D37E46;
	Mon, 24 Oct 2005 21:14:46 +0200 (CEST)
Received: from localhost ([127.0.0.1])
	by shiraz.levkowetz.com with esmtp (Exim 4.54)
	id 1EU7mQ-0001w3-AV; Mon, 24 Oct 2005 21:14:46 +0200
Message-ID: <435D32A5.4010400@levkowetz.com>
Date: Mon, 24 Oct 2005 21:14:45 +0200
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Mozilla Thunderbird 1.0.7 (Macintosh/20050923)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Alexandru Petrescu <alexandru.petrescu@motorola.com>
Subject: Re: [Mip6] More comments on draft-ietf-mip6-nemo-v4traversal-00.txt
References: <435CF254.6050508@motorola.com> <435D0459.8050605@levkowetz.com>
	<435D250B.6040507@motorola.com>
In-Reply-To: <435D250B.6040507@motorola.com>
X-Enigmail-Version: 0.93.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: 6907f330301e69261fa73bed91449a20
Content-Transfer-Encoding: 7bit
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Hi Alexandru,

on 2005-10-24 20:16 Alexandru Petrescu said the following:
> Henrik Levkowetz wrote:
> 
>> Hi Alexandru,
>> 
>> on 2005-10-24 16:40 Alexandru Petrescu said the following:
>> [...]
>> 
>>>I have some comments.
>>>
>>>
>>>>The current Mobile IPv6 specification and [NEMO] do not allow mobile
>>>> nodes to use an IPv4 home address or prefix, respectively.
>>>
>>>That is largely true.  Note though that recently there is a personal
>>>draft on NEMO for IPv4 home prefix that uses MIP4 and no MIP6.
>> 
>> Right.  But that isn't in the current spec, which is the base for what
>> this draft is attempting to expand.  We should check the draft you
>> refer to (name?) to make sure good ideas are incorporated in the
>> v4traversal work, though.
> 
> The draft I'm referring to proposes a message extension to MIP4
> Registration Request and Reply such as to carry Mobile Network Prefixes,
> or home prefixes.  The name of the draft is
> http://www.ietf.org/internet-drafts/draft-leung-nemov4-base-00.txt

Right.  I know about this one.

[...]
>>>RO is another case.  There are no widely deployed RO-enabled CNs while
>>>IPv4 non-RO CNs are plenty, so one can't really claim MIP6 is superior
>>>to MIP4 because it has RO.
>> 
>> No?  So the future potential of RO is of no interest?
> 
> It is.  What I've learned is that when IPv6 CNs get deployed they'll
> most likely be RO-enabled, which would make MIP6 superiority statements
> necessarily weighted by 'when IPv6 gets deployed'.

Ok.  (Oh, by the way, over the last 6 months the AAAA DNS queries to my
server has increased from a very low level till currently 20-25% of
the A queries, indicating that more and more IPv6 enabled boxes are
coming online.  That doesn't necessarily mean they have IPv6 connectivity,
but it's still encouraging.)

>>>>We also assume that the Home Agent is always reachable through a 
>>>>globally unique IPv4 address.
>>>
>>>I would like a DSMIPv6 solution to assume that the HAv6 is only
>>>reachable by its v6 address.  That would help widespread adoption of
>>>IPv6 by offering one less dependency on IPv4.
>> 
>> If we're trying to solve the problem of providing MIPv6 functionality
>> for a MN / MR which only has IPv4 access, it is not a solution to say
>> that the HA only is reachable through a IPv6 address...
>> 
>> Or have I misunderstood the drift of your comment??
> 
> Sorry, I'm not trying to drift.  The problem was initially to make a v6
> MN capable to do MIP6 even if connected to a v4-only access network,
> eventually through NAT.  The essential mechanism proposed in the draft
> (v4 address in BU) was the original motivator.
> 
> That problem had no requirement to give v4 Home Address to a MIP6-only
> MN.  To develop a solution for that initial problem, there is no need
> for HA to have a public v4 address.  Requiring the HA to have a public
> v4 address is further enhancing the problem.

No.  Here we seem to radically disagree.  If my MN/MR has only IPv4
connectivity, the only way I can reach the HA is through a public
IPv4 address.

> Once a v4 and a v6 public addresses are required for HA, it leads (IMHO)
> to MN to run both MIP4 and MIP6.  Running both MIP4 and MIP6 being
> inefficient is questionable.
> 
> There exist no widely-deployed IPv6-only access network.  If it existed,
> then it would have generated a need for MNs that run MIP6 and need a v4
> Home Address to connect to a v4 HA.
> 
>>>In case the MN has v4-only applications on it, and needs to continuously
>>>accessed IPv4 Home Address then I suggest porting these applications to
>>>IPv6.  In this case MIP6 is used as an advantage of IPv6: if an
>>>application is ported from IPv4 to IPv6 then it gets ability to run
>>>uninterrupted and use a permanent Home Address, and does not need MIP4.
>> 
>> 
>> I think this still does not in any way solve the problem of a MIPv6
>> MN/MR which finds itself in a visited network with only IPv4 access...
> 
> Well, I think it does.  If all user applications on that MN are
> IPv6-enabled then the MN would use only pppd/dhcpcd to get an IPv4 "CoA"
> and some UDPv4 tunnelling software and a an IPv6 default route towards
> the tunnel interface, and send BU through it.  Then user launches IPv6
> html browser (or whatever other IPv6-enabled user application) and
> continuous access to the v6 Home Address is ok.

Oh, but then you assume that there is an IPv6 tunnel interface
available, which is fine, of course, if that actually happens to be the
case in every visited network you roam into, which I strongly doubt...

So we seem to disagree on the need for this solution, not on the details
of the actual proposed solution.

>>>>For DNS lookup by service, the SRV record defined in [BOOT] is 
>>>>reused.  For instance, if the service name is "mip6ha" and the 
>>>>protocol name is "ipv6" for the SRV record, the mobile node SHOULD 
>>>>send a DNS request with the QNAME set to "mip6ha.ipv6.example.com". 
>>>>The response should contain the home agent's FQDN(s) and may have the
>>>> corresponding 'AAAA' and 'A' records enclosed as well.
>>>
>>>This is another discussion, but I just mention it here.  This method for
>>>HAD does not specify a means for the HAs to co-operate with each other
>>>to establish their preferences.  With DNS-based it is left entirely to
>>>the MN to choose among the HAs addresses.
>> 
>> 
>> No.  Look at the SRV specification again.  It provides for priorities
>> between multiple choices, and fallback to backup hosts if the preferred
>> ones are down.
> 
> Thanks, I have to re-check that.  I think I meant to say that the DNS
> method would still require the HAs to co-ordinate amongst themselves to
> tell DNS what those priorities are.  I think MIP6 doesn't say how to do
> that, today.

The SRV specification permits the DNS lookup to bring back preference
information.  If the HAs want to adjust that information dynamically, on
the fly, I'm sure it can be done.  Possibly with dynamic DNS updates,
but I haven't looked into that.  I don't see that MIPv6 needs to add
anything MIPv6 specific to this.

[...]
>>>Actually there is more to happen between the two paragraphs.  Current
>>>implemented NATs have no idea about this draft, so they don't currently
>>>implement it.
>> 
>> 
>> No NAT should ever implement this draft.  I think there's some mis-
>> understanding here.
> 
> I think I've just written it as a statement and I don't suggest this
> draft to modify the NATs.  I think I am in agreement with you by saying
> that this draft does not modify the NATs.

Ok, cool.

>>>A NAT needs to know a way for forwarding the BAck from the HA to MN.
>>>The v4 dst address in that UDPv4-encapsulated BAck is the NAT address
>>>itself.  In order for NAT to forward the packet to MN (and re-write the
>>>IPv4 dst address) it sometimes uses port numbers.  That's why UDP.  Or,
>>>there's no mention of UDP numbers in this section.
>> 
>> 
>> ??  You can't have UDP encapsulation without UDP numbers.  I don't
>> understand...
> 
> Sorry, I think I meant to say that the HA should exchange the port
> numbers received in the UDP-encapsulated BU and use them to fill the
> port numbers for the UDP-encapsulated BAck (src becomes dst and
> viceversa).  But this may be seen as natural UDP processing...

Yes.

>>>And, when port numbers are used to facilitate ip address rewriting by
>>>NAT, they are not fixed, they're dynamically changing.  Which would
>>>demand more enhancement to this section.
>> 
>> 
>> Hmm.  I don't see that.  MIPv4 NAT traversal (RFC 3519) definitely works,
>> and the protocol as described here uses the same basic mechanism.
> 
> Oh well, I see, thanks for pointing to RFC 3519.
> 
> First, the draft has no mention of RFC 3519, so it should.  For example,
> RFC 3519 has a relatively deep discussion on what happens when the
> mapping is lost at NAT, a thing which should happen in this draft too.
> Up to the authors to refer to the RFC or re-describe here the mechanism
> to use BU/BAck as 'heartbeat' or 'keepalive'.

Yes, I think we will expand this section.

> Second, I think RFC 3519 describes no means for MN to discover what UDP
> port numbers are open at NAT.  The worst NAT I've experimented with has
> very few of them; and it's not 25 nor 80, it's 1755.  My knowledge of
> RFC 3519 may be not very good, please indicate if I'm wrong.

No that's right.  Although I'd see that as a Firewall function, rather
than a NAT, but that's quibbling about words.

> IMHO, what is needed is for both MN and HA to gain dynamic knowledge of
> both the IPv4 public address of NAT _and_ the UDP port numbers that are
> open at NAT.  Without that MN and HA can't communicate.

Well, the HA expects connections at a fixed port number anyway - if you
can't connect to that, you'll have to fall back to something which
strongly resembles port-scanning; and then have a HA which listens
on all ports for your special signature, and responds to that.  Such
a mechanism would be possible, of course, but should probably be
separately specified (if at all) ...

> Third, RFC 3519 does describe a means to re-establish NAT state (or
> mapping) when the HA does not reply.  However, it does not - and
> probably can not - provide a means for NAT to explicitely indicate MN
> that its state has changed.  This may have an unfortunate effect on MN,
> because all it sees is that its HA does not reply back.  Or, with NEMOv6
> DHAAD - again DHAAD :-) - the MN may take this lack of BAck from HA as a
> need to switch to another HA.

Something such as this seems close to what MIDCOM is working at; but I
haven't checked it out specifically.

>> Could you suggest some text?
> 
> Too early for me to suggest text since what I've said above is just
> recognizing some particular NAT behaviour that makes RFC 3519 not work
> in all NAT cases, IMHO.

Mmm.  I've not seen many failures of 3519; there are some corner
cases which will be fixed in an upcoming revision, but nothing relevant
to this.  The problem you describe comes more under Firewall traversal
than NAT traversal; especially if you have to scan to find port 1755,
and then configure your server to listen to that port...  I don't think
we should go there, as part of mip6-nemo-v4traversal.

> Probably the best thing I could suggest is the draft to refer to RFC
> 3519, in a first phase.

Oh, we will, I'm sure.

>>>>"Dual Stack Mobile IPv6 (DSMIPv6)"
>>>
>>>The title may not be very adapted.  It makes one somehow think about
>>>Dual-Stack MIP4 and MIP6, since 'dual-stack' is usually 'IPv4 stack and
>>>IPv6 stack'.  Or, the mechanism proposed is more about enhancing MIP6
>>>with some v4 features.  Maybe "v4-enhanced MIP6" would be better.
>> 
>> 
>> Agreed.  That should be fixed in the next revision.
> 
> Thanks for noting.

Sure.

Regards,

	Henrik

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



From mip6-bounces@ietf.org Mon Oct 24 16:32:40 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EU8zo-00042R-KK; Mon, 24 Oct 2005 16:32:40 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EU8zn-000420-32
	for mip6@megatron.ietf.org; Mon, 24 Oct 2005 16:32:39 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15341
	for <mip6@ietf.org>; Mon, 24 Oct 2005 16:32:23 -0400 (EDT)
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EU9CX-0005ki-Q3
	for mip6@ietf.org; Mon, 24 Oct 2005 16:45:53 -0400
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id j9OJxOt16020;
	Mon, 24 Oct 2005 12:59:24 -0700
X-mProtect: <200510241959> Nokia Silicon Valley Messaging Protection
Received: from mvdhcp14184.americas.nokia.com (172.18.141.84,
	claiming to be "[127.0.0.1]")
	by darkstar.iprg.nokia.com smtpd6vTOwH; Mon, 24 Oct 2005 12:59:22 PDT
Message-ID: <435D44CA.3080707@iprg.nokia.com>
Date: Mon, 24 Oct 2005 13:32:10 -0700
From: Vijay Devarapalli <vijayd@iprg.nokia.com>
User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: COMBES Jean-Michel RD-MAPS-ISS <jeanmichel.combes@francetelecom.com>
Subject: Re: [Mip6] General comments/questions on MIPv6 bootstrapping
References: <D2AA6DF1AEE4404F8D983B68BAC97CD2022B914F@ftrdmel3.rd.francetelecom.fr>
In-Reply-To: <D2AA6DF1AEE4404F8D983B68BAC97CD2022B914F@ftrdmel3.rd.francetelecom.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
Content-Transfer-Encoding: 7bit
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

COMBES Jean-Michel RD-MAPS-ISS wrote:
> Hi again,
> 
> I was waiting for the proposal for the integrated scenario before to do
> this email.
> 
> I have 2 main comments/questions.
> 
> The first one is regarding the fact that we have two (very) different
> mechanisms for only one functionality (on one side DNS+IKEv2, on the
> other side PANA+AAA+DCHP). 

there are 4 mains problems in MIP6 bootstrapping

1. home agent discovery
2. home address configuration
3. security association setup
4. DNS update for the MN

draft-ietf-mip6-bootstrapping-split and
draft-ietf-mip6-bootstrapping-integrated-dhc differ only
on 1). the solutions for 2), 3) and 4) are the same in
both drafts.

 > So, personally, I am a little afraid how all
> this will be managed in the user's terminal and in the MSP's network.
> E.g., what will be the trigger in the terminal to know which is the
> bootstrapping mechanism the terminal has to use?

we have some text on this in the integrated draft. the
mobile node could be configured to use either DHCPv6 or
DNS for HA discovery. based on the configuration the MN
uses a particular mechanism for HA discovery. in case
both are available and the MN gets a response through
a DHCP reply and DNS reply, the DHCP response has
precedence. do you see a need for more text on this? let
us know if there are any issues we havent considered.

> My second comment is regarding the interoperability with NEMO. I believe
> that if MIPv6 is deployed soon, NEMO will be deployed at the same time
> because the protocol is as mature as MIPv6. So I would like to know if
> the bootstrapping mechanisms working for MIPv6, will work with NEMO too.
> I would like to avoid to add new mechanisms again and so increase the
> complexity in a deployement architecture.

for NEMO, in addition to the 4 problems listed above, a
mobile network prefix needs to be configured. for that
there are two drafts being progressed in the NEMO WG.

http://www.ietf.org/internet-drafts/draft-ietf-nemo-dhcpv6-pd-00.txt
http://www.ietf.org/internet-drafts/draft-ietf-nemo-prefix-delegation-00.txt

these drafts were written up even before the boostrapping
work started in the MIP6 WG. is there anything else that
needs to be addressed for NEMO bootstrapping?

Vijay



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



From mip6-bounces@ietf.org Tue Oct 25 04:25:15 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUK7P-0000Fe-L7; Tue, 25 Oct 2005 04:25:15 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUK7J-0008Sd-RG
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 04:25:14 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA29496
	for <mip6@ietf.org>; Tue, 25 Oct 2005 04:24:54 -0400 (EDT)
Received: from cluster-d.mailcontrol.com ([217.69.20.190]
	helo=rly32d.srv.mailcontrol.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUKKE-0002Ud-In
	for mip6@ietf.org; Tue, 25 Oct 2005 04:38:31 -0400
Received: from hhe500-02.hbg.de.pan.eu (gate.eu.panasonic.com [194.173.20.12])
	by rly32d.srv.mailcontrol.com (MailControl) with SMTP id
	j9P8Otsf015095; Tue, 25 Oct 2005 09:24:55 +0100
Received: from eundadmi01.pan.eu(10.100.96.64) by hhe500-02.hbg.de.pan.eu via
	smtp id 72cd_98ef744c_4531_11da_8cbc_0030482aac25;
	Tue, 25 Oct 2005 10:30:27 +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 2005102510244995-49748 ;
	Tue, 25 Oct 2005 10:24:49 +0200 
Received: from localhost ([127.0.0.1]) by VPN-MRelay-01.PRDCG.Panasonic.de;
	Tue, 25 Oct 2005 10:26:56 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
MIME-Version: 1.0
Subject: RE: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
Thread-Topic: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
Thread-Index: AcXYqXbXIA/i8BXYScS1SYiWXuH9KAAAVacgAAMu7pAAH2NZIA==
To: "COMBES Jean-Michel RD-MAPS-ISS" <jeanmichel.combes@francetelecom.com>,
	"Gerardo Giaretta" <Gerardo.Giaretta@TILAB.COM>,
	<Francis.Dupont@enst-bretagne.fr>,
	"Alexandru Petrescu" <alexandru.petrescu@motorola.com>,
	"James Kempf" <Kempf@docomolabs-usa.com>,
	"Narayanan Vidya-CVN065" <vidya@motorola.com>
Message-ID: <4D2F935F08D41A4C8866693F4F0D7C4F58E6DA@lan-ex-01.panasonic.de>
Date: Tue, 25 Oct 2005 10:24:42 +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-05-40-01 (www.mailcontrol.com) on 10.68.0.142
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Content-Transfer-Encoding: quoted-printable
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org


> Would then RFC 3775 DHAAD provide 'load balancing'?
>
> I'm asking because I think it is not at all clear for everyone what
> 'load balancing' is and how MIP6 is concerned by load balancing.
> My own take on this is that even if RFC 3775 worked it wouldn't
provide
> 'load balancing' per se.  But, if the HAs co-ordinated themselves
> somehow with some existing load balancing protocol then load balancing
> would be achieved, because the HA list provided in DHAAD Reply and the
> HA list used by MN would allow MN to switch towards wherever the load
is
> minimal.

Yes, some co-ordination between HAs on the home link is required to
provide dynamic load balancing. I think this can already be achieved
with DHAAD as defined in RFC3775 by including load condition in the Home
Agent Information Option in Ras.=20

> As pointed out in draft-ietf-mip6-bootstrapping-split-01, DNS-based HA
> discovery may be used only to achieve coarse-grained load balancing by
> dynamically updating the SRV RR priorities. On the other hand, DHAAD
> cannot be used to load balance using different HAs in=20
> different subnet.

I agree, RFC3775 DHAAD cannot provide load balancing between different
HAs on different subnets. Besides the minimal pre-configuration, this is
an advantage of the DNS-based discovery. But I think anycast-based HA
discovery has advantages as well, e.g., it can support fine-grained load
balancing and can decrease delay and signaling overhead during
bootstrapping. Maybe a combination might become a good solution, e.g.,

1. The MN gets an HA prefix with the DNS-based discovery mechanism (as
defined in bootstrapping solution). This minimizes the pre-configuration
of the MN and can achieve (coarse-grained) load balancing between HAs of
different subnets.

2. The MN starts anycast-based HA discovery (not necessarily as defined
in RFC3775) using the discovered HA prefix to get the HA address. This
can support fine-grained load balancing between HAs on the same link and
thus results in fast and efficient HA discovery (since subsequent HA
re-assignment for load balancing is not necessarily required). A
possible secure and efficient method could be the IKE Security Gateway
discovery/assignment mechanism mentioned by Francis.

3. When load conditions change dramatically or the HA crashs, the MN
changes its HA using an HA-switch mechanism (this mechanism could also
provide an optional fine-grained load balancing between HAs of different
subnets).

> > So, why this HA - the one assigning the right HA - needs to=20
> > have HA functionality?
> >=20
> It doesn't. It would be a light-weight "HA assigning entity" - but it
> may very well be a logical entity collocated with the HA.=20

IMHO, a separate assignment entity would be possible, but it would
probably increase signaling overhead and delay, because the MN has to
establish another SA during bootstrapping (one to DNS, one to the
assignment entity and finally one to the assigned HA).=20


Regards,

Kilian



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



From mip6-bounces@ietf.org Tue Oct 25 05:25:23 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUL3a-0003pQ-Qx; Tue, 25 Oct 2005 05:25:22 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUL3X-0003pI-Ir
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 05:25:21 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA02389
	for <mip6@ietf.org>; Tue, 25 Oct 2005 05:25:04 -0400 (EDT)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EULGR-0003uR-LQ
	for mip6@ietf.org; Tue, 25 Oct 2005 05:38:41 -0400
Received: from il06exr03.mot.com (il06exr03.mot.com [129.188.137.133])
	by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id j9P9b21n029043;
	Tue, 25 Oct 2005 02:37:06 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by il06exr03.mot.com (8.13.1/8.13.0) with ESMTP id j9P9Z8rF006821;
	Tue, 25 Oct 2005 04:35:09 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id 0D7AC865980; Tue, 25 Oct 2005 11:25:06 +0200 (CEST)
Message-ID: <435DF9F1.60203@motorola.com>
Date: Tue, 25 Oct 2005 11:25:05 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: Henrik Levkowetz <henrik@levkowetz.com>
Subject: Re: [Mip6] More comments on draft-ietf-mip6-nemo-v4traversal-00.txt
References: <435CF254.6050508@motorola.com> <435D0459.8050605@levkowetz.com>
	<435D250B.6040507@motorola.com> <435D32A5.4010400@levkowetz.com>
In-Reply-To: <435D32A5.4010400@levkowetz.com>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e472ca43d56132790a46d9eefd95f0a5
Content-Transfer-Encoding: 7bit
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Henrik Levkowetz wrote:
>>>>> We also assume that the Home Agent is always reachable 
>>>>> through a globally unique IPv4 address.
>>>> 
>>>> I would like a DSMIPv6 solution to assume that the HAv6 is only
>>>>  reachable by its v6 address.  That would help widespread 
>>>> adoption of IPv6 by offering one less dependency on IPv4.
>>> 
>>> If we're trying to solve the problem of providing MIPv6 
>>> functionality for a MN / MR which only has IPv4 access, it is not
>>>  a solution to say that the HA only is reachable through a IPv6 
>>> address...
>>> 
>>> Or have I misunderstood the drift of your comment??
>> 
>> Sorry, I'm not trying to drift.  The problem was initially to make
>>  a v6 MN capable to do MIP6 even if connected to a v4-only access 
>> network, eventually through NAT.  The essential mechanism proposed
>>  in the draft (v4 address in BU) was the original motivator.
>> 
>> That problem had no requirement to give v4 Home Address to a 
>> MIP6-only MN.  To develop a solution for that initial problem, 
>> there is no need for HA to have a public v4 address.  Requiring the
>>  HA to have a public v4 address is further enhancing the problem.
> 
> No.  Here we seem to radically disagree.  If my MN/MR has only IPv4 
> connectivity, the only way I can reach the HA is through a public 
> IPv4 address.

It sounds logical that when needs MN to reach the de-capsulating Gateway
that latter needs a v4 address.  Remark though that that Gateway that
strips out the the inner IPv6 packet of its UDPv4 header does not need
to be the IPv6 HA.  Which gives the possibility for the HA to be a box
different than the Gateway, and thus the HA to run IPv6 exclusively.  It
is a good thing to have the v6 HA separated from the de-capsulating Gateway.

If we require the HA to run both IPv4 and IPv6 it means that the HA can
not be placed in an IPv6-exclusively network.

>> Well, I think it does.  If all user applications on that MN are 
>> IPv6-enabled then the MN would use only pppd/dhcpcd to get an IPv4
>>  "CoA" and some UDPv4 tunnelling software and a an IPv6 default 
>> route towards the tunnel interface, and send BU through it.  Then 
>> user launches IPv6 html browser (or whatever other IPv6-enabled 
>> user application) and continuous access to the v6 Home Address is 
>> ok.
> 
> Oh, but then you assume that there is an IPv6 tunnel interface 
> available, which is fine, of course, if that actually happens to be 
> the case in every visited network you roam into, which I strongly 
> doubt...

I am assuming that an IPv6-in-UDPv4 tunnel interface is possible in the
MN, whenver MN connects to a v4-exclusively network.  When the MN
connects to a network that is v6-capable that tunnel is not put up.

I doubt it's impossible to have a IPv6-in-UDPv4 tunnel interface that MN
uses whenever connecting to a v4-only network.  The MN can even receive
RAs on that interface that are sent by the Gateway (the Gateway
maintains the other IPv6-in-UDPv4 tunnel interface).

> So we seem to disagree on the need for this solution, not on the 
> details of the actual proposed solution.

We seem to disagree on the possibility/impossibility to have double
encapsulation IPv6-in-IPv6-in-UDPv4 performed by MN.  We haven't yet
discussed advantages/disavdntages of using IPv6-in-UDPv4.

> The SRV specification permits the DNS lookup to bring back preference
>  information.  If the HAs want to adjust that information 
> dynamically, on the fly, I'm sure it can be done.  Possibly with 
> dynamic DNS updates, but I haven't looked into that.  I don't see 
> that MIPv6 needs to add anything MIPv6 specific to this.

Yes, HAs could do DNS updating to update that information at the DNS
servers, but what is not specified is how the HAs achieve that
co-ordination amongst themselves.  MIP6 does not specify a way for the
HAs to decide priorities amongst them; it does however offer a tool to
exchange info with the H bit in the RAs.

>> Second, I think RFC 3519 describes no means for MN to discover what
>>  UDP port numbers are open at NAT.  The worst NAT I've experimented
>>  with has very few of them; and it's not 25 nor 80, it's 1755.  My
>>  knowledge of RFC 3519 may be not very good, please indicate if I'm
>>  wrong.
> 
> 
> No that's right.  Although I'd see that as a Firewall function, 
> rather than a NAT, but that's quibbling about words.

Right, I think it is obvious that most deployed NATs in commercial
networks employ firewall filtering as well.

>> IMHO, what is needed is for both MN and HA to gain dynamic 
>> knowledge of both the IPv4 public address of NAT _and_ the UDP port
>>  numbers that are open at NAT.  Without that MN and HA can't 
>> communicate.
> 
> 
> Well, the HA expects connections at a fixed port number anyway - if 
> you can't connect to that, you'll have to fall back to something 
> which strongly resembles port-scanning;

I'd name that "UDP path discovery" or "dynamic tunnel setup" instead of
"port-scanning" which has a negative reasonance (port-scanning is what
an outside attacker does to find open ports and exploit buffer overflows).

> and then have a HA which listens on all ports for your special 
> signature, and responds to that.  Such a mechanism would be possible,
>  of course, but should probably be separately specified (if at all) 
> ...

Well, I think without it the NAT traversal alone is less applicable.

>> Third, RFC 3519 does describe a means to re-establish NAT state (or
>>  mapping) when the HA does not reply.  However, it does not - and 
>> probably can not - provide a means for NAT to explicitely indicate
>>  MN that its state has changed.  This may have an unfortunate
>> effect on MN, because all it sees is that its HA does not reply
>> back. Or, with NEMOv6 DHAAD - again DHAAD :-) - the MN may take
>> this lack of BAck from HA as a need to switch to another HA.
> 
> 
> Something such as this seems close to what MIDCOM is working at; but
>  I haven't checked it out specifically.

I think so.  NAT explicitely instructing MN about state change is
probably better dealt with by MIDCOM.  Here we may want to make sure
that NAT discovery does not interfere with BU/BAck error processing.

>>> Could you suggest some text?
>> 
>> Too early for me to suggest text since what I've said above is just
>>  recognizing some particular NAT behaviour that makes RFC 3519 not
>>  work in all NAT cases, IMHO.
> 
> 
> Mmm.  I've not seen many failures of 3519; there are some corner 
> cases which will be fixed in an upcoming revision, but nothing 
> relevant to this.  The problem you describe comes more under Firewall
>  traversal than NAT traversal; especially if you have to scan to find
>  port 1755, and then configure your server to listen to that port...
>  I don't think we should go there, as part of mip6-nemo-v4traversal.

I understand the oppinion, it's good to conceptually separate.

Personally, I'm for stripping out other parts from mip6-nemo-v4traversal
(e.g. strip out  v4 access to MN, to LFN, connect to a v6-network) and
concentrate more on the connect to v4-only network case, with more
NAT/FW traversal features - that's what deployments with the largest
number of wireless mobile nodes do.

Let me exemplify those here for sake of completeness:

All providers of Internet access to wireless mobile nodes (WiFi, GPRS,
UMTS) I've tried do one the following:

-offer a v4 address that is private behind NAT, or offer a public v4
 address.  But in both cases, the address is subject to change whenever
 either a re-connection is made (pppd or dhcpd) by the user or the
 connection is lost due to wireless changes.  The access to wireless
 mobile nodes I've tried does not have the ability to provide a
 permanent v4 address (like the ISP at home may provide).  However, in
 the GPRS and UMTS cases the address is stable with respect to changing
 Base Stations.
-use firewalls between MN and Internet, with various ports blocked.

Alex

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



From mip6-bounces@ietf.org Tue Oct 25 05:39:24 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EULHA-0001HT-Lr; Tue, 25 Oct 2005 05:39:24 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EULH8-0001Dz-43
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 05:39:22 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA03090
	for <mip6@ietf.org>; Tue, 25 Oct 2005 05:39:07 -0400 (EDT)
Received: from av6-1-sn3.vrr.skanova.net ([81.228.9.179])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EULU3-0004GA-Mu
	for mip6@ietf.org; Tue, 25 Oct 2005 05:52:44 -0400
Received: by av6-1-sn3.vrr.skanova.net (Postfix, from userid 502)
	id E817D38085; Tue, 25 Oct 2005 11:39:11 +0200 (CEST)
Received: from smtp3-2-sn3.vrr.skanova.net (smtp3-2-sn3.vrr.skanova.net
	[81.228.9.102]) by av6-1-sn3.vrr.skanova.net (Postfix) with ESMTP
	id CC2803806C; Tue, 25 Oct 2005 11:39:11 +0200 (CEST)
Received: from shiraz.levkowetz.com (81-224-201-50-no45.tbcn.telia.com
	[81.224.201.50])
	by smtp3-2-sn3.vrr.skanova.net (Postfix) with ESMTP id AE79B37E49;
	Tue, 25 Oct 2005 11:39:11 +0200 (CEST)
Received: from localhost ([127.0.0.1])
	by shiraz.levkowetz.com with esmtp (Exim 4.54)
	id 1EULGx-0004xN-7d; Tue, 25 Oct 2005 11:39:11 +0200
Message-ID: <435DFD3F.4020309@levkowetz.com>
Date: Tue, 25 Oct 2005 11:39:11 +0200
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Mozilla Thunderbird 1.0.7 (Macintosh/20050923)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Alexandru Petrescu <alexandru.petrescu@motorola.com>
Subject: Re: [Mip6] More comments on draft-ietf-mip6-nemo-v4traversal-00.txt
References: <435CF254.6050508@motorola.com> <435D0459.8050605@levkowetz.com>
	<435D250B.6040507@motorola.com>
	<435D32A5.4010400@levkowetz.com> <435DF9F1.60203@motorola.com>
In-Reply-To: <435DF9F1.60203@motorola.com>
X-Enigmail-Version: 0.93.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: e8c5db863102a3ada84e0cd52a81a79e
Content-Transfer-Encoding: 7bit
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Hi Alexandru,

on 2005-10-25 11:25 Alexandru Petrescu said the following:
> Henrik Levkowetz wrote:
[...]
>> No.  Here we seem to radically disagree.  If my MN/MR has only IPv4 
>> connectivity, the only way I can reach the HA is through a public 
>> IPv4 address.
> 
> It sounds logical that when needs MN to reach the de-capsulating Gateway
> that latter needs a v4 address.  Remark though that that Gateway that
> strips out the the inner IPv6 packet of its UDPv4 header does not need
> to be the IPv6 HA.  Which gives the possibility for the HA to be a box
> different than the Gateway, and thus the HA to run IPv6 exclusively.  It
> is a good thing to have the v6 HA separated from the de-capsulating Gateway.
> 
> If we require the HA to run both IPv4 and IPv6 it means that the HA can
> not be placed in an IPv6-exclusively network.

Yes.  Which is why we write that the HA must be reachable through
an IPv4 address, instead of writing that the HA must have and IPv4
address on an interface.

>>> Well, I think it does.  If all user applications on that MN are 
>>> IPv6-enabled then the MN would use only pppd/dhcpcd to get an IPv4
>>>  "CoA" and some UDPv4 tunnelling software and a an IPv6 default 
>>> route towards the tunnel interface, and send BU through it.  Then 
>>> user launches IPv6 html browser (or whatever other IPv6-enabled 
>>> user application) and continuous access to the v6 Home Address is 
>>> ok.
>> 
>> Oh, but then you assume that there is an IPv6 tunnel interface 
>> available, which is fine, of course, if that actually happens to be 
>> the case in every visited network you roam into, which I strongly 
>> doubt...
> 
> I am assuming that an IPv6-in-UDPv4 tunnel interface is possible in the
> MN, whenver MN connects to a v4-exclusively network.  When the MN
> connects to a network that is v6-capable that tunnel is not put up.
> 
> I doubt it's impossible to have a IPv6-in-UDPv4 tunnel interface that MN
> uses whenever connecting to a v4-only network.  The MN can even receive
> RAs on that interface that are sent by the Gateway (the Gateway
> maintains the other IPv6-in-UDPv4 tunnel interface).

Hmm.  Now you have a new animal here, a IPv6-in-UDPv4 tunnel.  I think
at this point it is appropriate to check whether you have read
draft-larsson-v6ops-mip-scenarios-01?  I think we cover a lot of
ground there that we seem bound to go over again here if you
haven't read it...

>> So we seem to disagree on the need for this solution, not on the 
>> details of the actual proposed solution.
> 
> We seem to disagree on the possibility/impossibility to have double
> encapsulation IPv6-in-IPv6-in-UDPv4 performed by MN.  We haven't yet
> discussed advantages/disavdntages of using IPv6-in-UDPv4.

Well, I'll disagree on your statement here - I don't think this is
our disagreement :-)

>> The SRV specification permits the DNS lookup to bring back preference
>>  information.  If the HAs want to adjust that information 
>> dynamically, on the fly, I'm sure it can be done.  Possibly with 
>> dynamic DNS updates, but I haven't looked into that.  I don't see 
>> that MIPv6 needs to add anything MIPv6 specific to this.
> 
> Yes, HAs could do DNS updating to update that information at the DNS
> servers, but what is not specified is how the HAs achieve that
> co-ordination amongst themselves.  MIP6 does not specify a way for the
> HAs to decide priorities amongst them; it does however offer a tool to
> exchange info with the H bit in the RAs.

Agreed.

>>> Second, I think RFC 3519 describes no means for MN to discover what
>>>  UDP port numbers are open at NAT.  The worst NAT I've experimented
>>>  with has very few of them; and it's not 25 nor 80, it's 1755.  My
>>>  knowledge of RFC 3519 may be not very good, please indicate if I'm
>>>  wrong.
>> 
>> 
>> No that's right.  Although I'd see that as a Firewall function, 
>> rather than a NAT, but that's quibbling about words.
> 
> Right, I think it is obvious that most deployed NATs in commercial
> networks employ firewall filtering as well.

Yes.  But calling it a NAT problem confuses the issue, when it is
a Firewall problem.

>>> IMHO, what is needed is for both MN and HA to gain dynamic 
>>> knowledge of both the IPv4 public address of NAT _and_ the UDP port
>>>  numbers that are open at NAT.  Without that MN and HA can't 
>>> communicate.
>> 
>> 
>> Well, the HA expects connections at a fixed port number anyway - if 
>> you can't connect to that, you'll have to fall back to something 
>> which strongly resembles port-scanning;
> 
> I'd name that "UDP path discovery" or "dynamic tunnel setup" instead of
> "port-scanning" which has a negative reasonance (port-scanning is what
> an outside attacker does to find open ports and exploit buffer overflows).

Ok.

>> and then have a HA which listens on all ports for your special 
>> signature, and responds to that.  Such a mechanism would be possible,
>>  of course, but should probably be separately specified (if at all) 
>> ...
> 
> Well, I think without it the NAT traversal alone is less applicable.

Marginally.

>>> Third, RFC 3519 does describe a means to re-establish NAT state (or
>>>  mapping) when the HA does not reply.  However, it does not - and 
>>> probably can not - provide a means for NAT to explicitely indicate
>>>  MN that its state has changed.  This may have an unfortunate
>>> effect on MN, because all it sees is that its HA does not reply
>>> back. Or, with NEMOv6 DHAAD - again DHAAD :-) - the MN may take
>>> this lack of BAck from HA as a need to switch to another HA.
>> 
>> 
>> Something such as this seems close to what MIDCOM is working at; but
>>  I haven't checked it out specifically.
> 
> I think so.  NAT explicitely instructing MN about state change is
> probably better dealt with by MIDCOM.  Here we may want to make sure
> that NAT discovery does not interfere with BU/BAck error processing.

NAT discovery and NAT keepalives are separate things.  I agree that
NAT keepalives are needed, with sufficient frequency and some
adaptability.

>>>> Could you suggest some text?
>>> 
>>> Too early for me to suggest text since what I've said above is just
>>>  recognizing some particular NAT behaviour that makes RFC 3519 not
>>>  work in all NAT cases, IMHO.
>> 
>> 
>> Mmm.  I've not seen many failures of 3519; there are some corner 
>> cases which will be fixed in an upcoming revision, but nothing 
>> relevant to this.  The problem you describe comes more under Firewall
>>  traversal than NAT traversal; especially if you have to scan to find
>>  port 1755, and then configure your server to listen to that port...
>>  I don't think we should go there, as part of mip6-nemo-v4traversal.
> 
> I understand the oppinion, it's good to conceptually separate.

Ok.

> Personally, I'm for stripping out other parts from mip6-nemo-v4traversal
> (e.g. strip out  v4 access to MN, to LFN, connect to a v6-network) and
> concentrate more on the connect to v4-only network case, with more
> NAT/FW traversal features - that's what deployments with the largest
> number of wireless mobile nodes do.
> 
> Let me exemplify those here for sake of completeness:
> 
> All providers of Internet access to wireless mobile nodes (WiFi, GPRS,
> UMTS) I've tried do one the following:
> 
> -offer a v4 address that is private behind NAT, or offer a public v4
>  address.  But in both cases, the address is subject to change whenever
>  either a re-connection is made (pppd or dhcpd) by the user or the
>  connection is lost due to wireless changes.  The access to wireless
>  mobile nodes I've tried does not have the ability to provide a
>  permanent v4 address (like the ISP at home may provide).  However, in
>  the GPRS and UMTS cases the address is stable with respect to changing
>  Base Stations.

This scenario we can handle with MIP and NAT traversal.

> -use firewalls between MN and Internet, with various ports blocked.

This is harder, and the best is probably to vote with your feet - i.e.,
choose providers which don't do such silliness, as far as possible.


	Henrik


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



From mip6-bounces@ietf.org Tue Oct 25 05:53:14 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EULUY-0005is-PA; Tue, 25 Oct 2005 05:53:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EULUT-0005h5-73
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 05:53:13 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA03576
	for <mip6@ietf.org>; Tue, 25 Oct 2005 05:52:54 -0400 (EDT)
Received: from motgate7.mot.com ([129.188.136.7])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EULhP-0004ZK-7s
	for mip6@ietf.org; Tue, 25 Oct 2005 06:06:31 -0400
Received: from az33exr01.mot.com ([10.64.251.231])
	by motgate7.mot.com (8.12.11/Motgate7) with ESMTP id j9PAFd2b014175;
	Tue, 25 Oct 2005 03:15:39 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by az33exr01.mot.com (8.13.1/8.13.0) with ESMTP id j9PA55YT010167;
	Tue, 25 Oct 2005 05:05:07 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id B2265865980; Tue, 25 Oct 2005 11:52:43 +0200 (CEST)
Message-ID: <435E006B.3090909@motorola.com>
Date: Tue, 25 Oct 2005 11:52:43 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: Kilian Weniger <Kilian.Weniger@eu.panasonic.com>
Subject: Re: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
References: <4D2F935F08D41A4C8866693F4F0D7C4F58E6DA@lan-ex-01.panasonic.de>
In-Reply-To: <4D2F935F08D41A4C8866693F4F0D7C4F58E6DA@lan-ex-01.panasonic.de>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Content-Transfer-Encoding: 7bit
Cc: Gerardo Giaretta <Gerardo.Giaretta@TILAB.COM>, mip6@ietf.org,
	James Kempf <Kempf@docomolabs-usa.com>, Francis.Dupont@enst-bretagne.fr,
	Alexandru Petrescu <alexandru.petrescu@motorola.com>,
	COMBES Jean-Michel RD-MAPS-ISS <jeanmichel.combes@francetelecom.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Kilian Weniger wrote:

>> Would then RFC 3775 DHAAD provide 'load balancing'?
>> 
>> I'm asking because I think it is not at all clear for everyone what
>>  'load balancing' is and how MIP6 is concerned by load balancing. 
>> My own take on this is that even if RFC 3775 worked it wouldn't
> 
> provide
> 
>> 'load balancing' per se.  But, if the HAs co-ordinated themselves 
>> somehow with some existing load balancing protocol then load
>> balancing would be achieved, because the HA list provided in DHAAD
>> Reply and the HA list used by MN would allow MN to switch towards
>> wherever the load
> 
> is
> 
>> minimal.
> 
> 
> Yes, some co-ordination between HAs on the home link is required to 
> provide dynamic load balancing. I think this can already be achieved 
> with DHAAD as defined in RFC3775 by including load condition in the
> Home Agent Information Option in Ras.

I agree, a HA may convert its load condition into a combination of HA
Preference and Lifetime sent in the RAs.  Every other HA receives this
RA, so they could collectively build a common ordered HA list.  One of
the HAs sends it to the MN.

The 'conversion' part the HA that would convert its load condition
into Preference and Lifetime is not specified though.

>> As pointed out in draft-ietf-mip6-bootstrapping-split-01, DNS-based
>> HA discovery may be used only to achieve coarse-grained load
>> balancing by dynamically updating the SRV RR priorities. On the
>> other hand, DHAAD cannot be used to load balance using different
>> HAs in different subnet.
> 
> I agree, RFC3775 DHAAD cannot provide load balancing between
> different HAs on different subnets.

I think it is impossible to provide load balancing between different HAs
on different subnets while maintaining a permanent Home Address for the
Mobile Node.

Initial assignment of a less loaded HA from a different subnet, together
with a different HoA, is possible though.

And this latter thing could be approximately achieved with DHAAD:
pre-configure two different subnet prefixes on the MN, let MN do DHAAD
once for each home subnet, and let MN choose one of the HAs.

> Besides the minimal pre-configuration, this is an advantage of the
> DNS-based discovery. But I think anycast-based HA discovery has
> advantages as well, e.g., it can support fine-grained load balancing
> and can decrease delay and signaling overhead during bootstrapping.
> Maybe a combination might become a good solution, e.g.,
> 
> 1. The MN gets an HA prefix with the DNS-based discovery mechanism
> (as defined in bootstrapping solution). This minimizes the
> pre-configuration of the MN and can achieve (coarse-grained) load
> balancing between HAs of different subnets.
> 
> 2. The MN starts anycast-based HA discovery (not necessarily as
> defined in RFC3775) using the discovered HA prefix to get the HA
> address. This can support fine-grained load balancing between HAs on
> the same link and thus results in fast and efficient HA discovery
> (since subsequent HA re-assignment for load balancing is not
> necessarily required). A possible secure and efficient method could
> be the IKE Security Gateway discovery/assignment mechanism mentioned
> by Francis.
> 
> 3. When load conditions change dramatically or the HA crashs, the MN 
> changes its HA using an HA-switch mechanism (this mechanism could
> also provide an optional fine-grained load balancing between HAs of
> different subnets).

This looks like a good overall picture combining all the stuff together.
 It has some good parts, IMHO.

Alex


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



From mip6-bounces@ietf.org Tue Oct 25 06:22:03 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EULwR-0006lT-BG; Tue, 25 Oct 2005 06:22:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EULwP-0006l3-8x
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 06:22:01 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA04954
	for <mip6@ietf.org>; Tue, 25 Oct 2005 06:21:45 -0400 (EDT)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUM9L-0005Ko-5C
	for mip6@ietf.org; Tue, 25 Oct 2005 06:35:23 -0400
Received: from il06exr02.mot.com (il06exr02.mot.com [129.188.137.132])
	by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id j9PAXqF4010108;
	Tue, 25 Oct 2005 03:33:52 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by il06exr02.mot.com (8.13.1/8.13.0) with ESMTP id j9PAUXSg019430;
	Tue, 25 Oct 2005 05:30:33 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id 9F807865980; Tue, 25 Oct 2005 12:21:55 +0200 (CEST)
Message-ID: <435E0743.4030904@motorola.com>
Date: Tue, 25 Oct 2005 12:21:55 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: Henrik Levkowetz <henrik@levkowetz.com>
Subject: Re: [Mip6] More comments on draft-ietf-mip6-nemo-v4traversal-00.txt
References: <435CF254.6050508@motorola.com> <435D0459.8050605@levkowetz.com>
	<435D250B.6040507@motorola.com>
	<435D32A5.4010400@levkowetz.com> <435DF9F1.60203@motorola.com>
	<435DFD3F.4020309@levkowetz.com>
In-Reply-To: <435DFD3F.4020309@levkowetz.com>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 932cba6e0228cc603da43d861a7e09d8
Content-Transfer-Encoding: 7bit
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Henrik Levkowetz wrote:
>> If we require the HA to run both IPv4 and IPv6 it means that the HA
>> can not be placed in an IPv6-exclusively network.
> 
> Yes.  Which is why we write that the HA must be reachable through an
> IPv4 address, instead of writing that the HA must have and IPv4 
> address on an interface.

I am surprised by the formulation?!

Ok, so the HA must be reachable through a v4 address, not necessarily
have an IPv4 address on an interface, I agree.

[...]
>>> Oh, but then you assume that there is an IPv6 tunnel interface 
>>> available, which is fine, of course, if that actually happens to
>>> be the case in every visited network you roam into, which I
>>> strongly doubt...
>> 
>> I am assuming that an IPv6-in-UDPv4 tunnel interface is possible in
>> the MN, whenver MN connects to a v4-exclusively network.  When the
>> MN connects to a network that is v6-capable that tunnel is not put
>> up.
>> 
>> I doubt it's impossible to have a IPv6-in-UDPv4 tunnel interface
>> that MN uses whenever connecting to a v4-only network.  The MN can
>> even receive RAs on that interface that are sent by the Gateway
>> (the Gateway maintains the other IPv6-in-UDPv4 tunnel interface).
> 
> Hmm.  Now you have a new animal here, a IPv6-in-UDPv4 tunnel.  I
> think at this point it is appropriate to check whether you have read 
> draft-larsson-v6ops-mip-scenarios-01?  I think we cover a lot of 
> ground there that we seem bound to go over again here if you haven't
> read it...

Ok, I quickly skimmed through it.  Nice work.  It includes discussion of
various way of encapsulating v6 in v4.  Should I understand that I'm
directed to this draft for its evaluation of IPv6-in-UDPv4 has higher
transport overhead, which is an inefficiency?

I am not sure I understand what - other than the claimed inefficiency -
are the disadvantages of using IPv6-in-UDPv4 tunnel interface.

I could explain further what I mean by IPv6-in-UDPv4.  The MN maintains
a virtual interface called u0, the Gateway too.  This interface is IPv4
and IPv6 enabled.  All packets MN sends to its u0 will be encapsulated
by tunnelling software into UDPv4 and sent to the Gateway, which
decapsulates.  The tunnelling software on Gateway dynamically puts up
its u0 and parametered with the local/remote IP addresses and port
numbers.  Same on the MN.  Additionally the Gateway sends IPv6 RAs on
that interface, so the MN can auto-configure a CoA and do MIP6 mobility
unmodified.  I don't see anything wrong with that.

>>> So we seem to disagree on the need for this solution, not on the
>>>  details of the actual proposed solution.
>> 
>> We seem to disagree on the possibility/impossibility to have double
>>  encapsulation IPv6-in-IPv6-in-UDPv4 performed by MN.  We haven't
>> yet discussed advantages/disavdntages of using IPv6-in-UDPv4.
> 
> Well, I'll disagree on your statement here - I don't think this is 
> our disagreement :-)

So what is our disagreement?

>>> No that's right.  Although I'd see that as a Firewall function, 
>>> rather than a NAT, but that's quibbling about words.
>> 
>> Right, I think it is obvious that most deployed NATs in commercial 
>> networks employ firewall filtering as well.
> 
> Yes.  But calling it a NAT problem confuses the issue, when it is a
> Firewall problem.

Ok, I'll call it a Firewall problem and suggest to be dealt with in this
document.

>>> and then have a HA which listens on all ports for your special 
>>> signature, and responds to that.  Such a mechanism would be
>>> possible, of course, but should probably be separately specified
>>> (if at all) ...
>> 
>> Well, I think without it the NAT traversal alone is less
>> applicable.
> 
> Marginally.

Ok, let me put it other way: this document is useless without Firewall
traversal.

> NAT discovery and NAT keepalives are separate things.  I agree that 
> NAT keepalives are needed, with sufficient frequency and some 
> adaptability.

Ok.

>> Personally, I'm for stripping out other parts from
>> mip6-nemo-v4traversal (e.g. strip out  v4 access to MN, to LFN,
>> connect to a v6-network) and concentrate more on the connect to
>> v4-only network case, with more NAT/FW traversal features - that's
>> what deployments with the largest number of wireless mobile nodes
>> do.
>> 
>> Let me exemplify those here for sake of completeness:
>> 
>> All providers of Internet access to wireless mobile nodes (WiFi,
>> GPRS, UMTS) I've tried do one the following:
>> 
>> -offer a v4 address that is private behind NAT, or offer a public
>> v4 address.  But in both cases, the address is subject to change
>> whenever either a re-connection is made (pppd or dhcpd) by the user
>> or the connection is lost due to wireless changes.  The access to
>> wireless mobile nodes I've tried does not have the ability to
>> provide a permanent v4 address (like the ISP at home may provide).
>> However, in the GPRS and UMTS cases the address is stable with
>> respect to changing Base Stations.
> 
> 
> This scenario we can handle with MIP and NAT traversal.

I agree, but I wanted to say that MN's v4 public address is more subject
to change than when the v4 address is private (the NAT public v4 address
is more stable).  Which in the context of IPv6-IPv6-in-UDPv4 tunnel
means some dynamic adaptation.  But I think we don't agree about
IPv6-in-IPv6-in-UDPv4 in the first place.

>> -use firewalls between MN and Internet, with various ports blocked.
>> 
> 
> This is harder, and the best is probably to vote with your feet -
> i.e., choose providers which don't do such silliness, as far as
> possible.

Well I often do what my bank allows me to do, and the cheaper cell
wireless subscriptions are the ones that are most firewalled.  The most
expensive subscriptions are the ones where I could have my own Firewall
rules.  The cheapest subscriptions are the ones used by the largest
number of people, so potential wider deployment for this solution if it
addresses the Firewall aspects.

Alex

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



From mip6-bounces@ietf.org Tue Oct 25 06:29:03 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUM3C-0000lg-Up; Tue, 25 Oct 2005 06:29:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUM3B-0000jx-DI
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 06:29:01 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA05368
	for <mip6@ietf.org>; Tue, 25 Oct 2005 06:28:48 -0400 (EDT)
Received: from cluster-d.mailcontrol.com ([217.69.20.190]
	helo=rly15d.srv.mailcontrol.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUMG6-0005ZA-LW
	for mip6@ietf.org; Tue, 25 Oct 2005 06:42:24 -0400
Received: from hhe500-02.hbg.de.pan.eu (gate.eu.panasonic.com [194.173.20.12])
	by rly15d.srv.mailcontrol.com (MailControl) with SMTP id
	j9PASmCL027700; Tue, 25 Oct 2005 11:28:48 +0100
Received: from eundadmi01.pan.eu(10.100.96.64) by hhe500-02.hbg.de.pan.eu via
	smtp id 72ba_e74c6f8a_4542_11da_8e2f_0030482aac25;
	Tue, 25 Oct 2005 12:34:20 +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 2005102512284361-59590 ;
	Tue, 25 Oct 2005 12:28:43 +0200 
Received: from localhost ([127.0.0.1]) by VPN-MRelay-01.PRDCG.Panasonic.de;
	Tue, 25 Oct 2005 12:30:53 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
MIME-Version: 1.0
Subject: RE: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
Thread-Topic: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
Thread-Index: AcXZSeqkUrX9TPzTTNqgNArCQhVJwwAAoqeA
To: "Alexandru Petrescu" <alexandru.petrescu@motorola.com>
Message-ID: <4D2F935F08D41A4C8866693F4F0D7C4F58E728@lan-ex-01.panasonic.de>
Date: Tue, 25 Oct 2005 12:28:39 +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-05-40-01 (www.mailcontrol.com) on 10.68.0.125
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Content-Transfer-Encoding: quoted-printable
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

=20
> I think it is impossible to provide load balancing between=20
> different HAs
> on different subnets while maintaining a permanent Home=20
> Address for the
> Mobile Node.
=20
I wouldn't say that it is impossible, at least not if you think of load
balancing in terms of the amount of data traffic routed over an HA in
bi-directional tunneling mode. For instance, draft-weniger-rota-01 or
draft-thubert-nemo-global-haha-01.txt might in principle enable load
balancing between different HAs on different subnets while maintaining a
permanent Home Address. However, both solutions are not specifically
designed for load balancing, e.g., a mechanism to exchange load
conditions across subnets would be needed.

Regards,

Kilian


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



From mip6-bounces@ietf.org Tue Oct 25 07:04:47 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUMbn-0004TA-Cw; Tue, 25 Oct 2005 07:04:47 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUMbm-0004Sa-8Y
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 07:04:46 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA06710
	for <mip6@ietf.org>; Tue, 25 Oct 2005 07:04:32 -0400 (EDT)
Received: from av9-1-sn3.vrr.skanova.net ([81.228.9.185])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUMoi-0006KE-ME
	for mip6@ietf.org; Tue, 25 Oct 2005 07:18:09 -0400
Received: by av9-1-sn3.vrr.skanova.net (Postfix, from userid 502)
	id 4890C38091; Tue, 25 Oct 2005 13:04:36 +0200 (CEST)
Received: from smtp3-2-sn3.vrr.skanova.net (smtp3-2-sn3.vrr.skanova.net
	[81.228.9.102]) by av9-1-sn3.vrr.skanova.net (Postfix) with ESMTP
	id 27E7C38051; Tue, 25 Oct 2005 13:04:36 +0200 (CEST)
Received: from shiraz.levkowetz.com (81-224-201-50-no45.tbcn.telia.com
	[81.224.201.50])
	by smtp3-2-sn3.vrr.skanova.net (Postfix) with ESMTP id 0A0DF37E49;
	Tue, 25 Oct 2005 13:04:35 +0200 (CEST)
Received: from localhost ([127.0.0.1])
	by shiraz.levkowetz.com with esmtp (Exim 4.54)
	id 1EUMbb-0001HZ-Hv; Tue, 25 Oct 2005 13:04:35 +0200
Message-ID: <435E1143.8000001@levkowetz.com>
Date: Tue, 25 Oct 2005 13:04:35 +0200
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Mozilla Thunderbird 1.0.7 (Macintosh/20050923)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Alexandru Petrescu <alexandru.petrescu@motorola.com>
Subject: Re: [Mip6] More comments on draft-ietf-mip6-nemo-v4traversal-00.txt
References: <435CF254.6050508@motorola.com> <435D0459.8050605@levkowetz.com>
	<435D250B.6040507@motorola.com>
	<435D32A5.4010400@levkowetz.com> <435DF9F1.60203@motorola.com>
	<435DFD3F.4020309@levkowetz.com> <435E0743.4030904@motorola.com>
In-Reply-To: <435E0743.4030904@motorola.com>
X-Enigmail-Version: 0.93.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: a1852b4f554b02e7e4548cc7928acc1f
Content-Transfer-Encoding: 7bit
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Hi,

on 2005-10-25 12:21 Alexandru Petrescu said the following:
> Henrik Levkowetz wrote:
[...]
>> Hmm.  Now you have a new animal here, a IPv6-in-UDPv4 tunnel.  I
>> think at this point it is appropriate to check whether you have read 
>> draft-larsson-v6ops-mip-scenarios-01?  I think we cover a lot of 
>> ground there that we seem bound to go over again here if you haven't
>> read it...
> 
> Ok, I quickly skimmed through it.  Nice work.  It includes discussion of
> various way of encapsulating v6 in v4.  Should I understand that I'm
> directed to this draft for its evaluation of IPv6-in-UDPv4 has higher
> transport overhead, which is an inefficiency?
> 
> I am not sure I understand what - other than the claimed inefficiency -
> are the disadvantages of using IPv6-in-UDPv4 tunnel interface.

Personally I think it's the overhead both in tunnelling and setup.
There may be complexity and deployment issues, too, but those have
had less scrutiny.

> I could explain further what I mean by IPv6-in-UDPv4.  The MN maintains
> a virtual interface called u0, the Gateway too.  This interface is IPv4
> and IPv6 enabled.  All packets MN sends to its u0 will be encapsulated
> by tunnelling software into UDPv4 and sent to the Gateway, which
> decapsulates.  The tunnelling software on Gateway dynamically puts up
> its u0 and parametered with the local/remote IP addresses and port
> numbers.  Same on the MN.  Additionally the Gateway sends IPv6 RAs on
> that interface, so the MN can auto-configure a CoA and do MIP6 mobility
> unmodified.  I don't see anything wrong with that.

This sounds very close to Pascal Thubert's Doors proposal, which has
been discussed in the design team, without the team settling on one
proposed solution yet.

>>>> So we seem to disagree on the need for this solution, not on the
>>>>  details of the actual proposed solution.
>>> 
>>> We seem to disagree on the possibility/impossibility to have double
>>>  encapsulation IPv6-in-IPv6-in-UDPv4 performed by MN.  We haven't
>>> yet discussed advantages/disavdntages of using IPv6-in-UDPv4.
>> 
>> Well, I'll disagree on your statement here - I don't think this is 
>> our disagreement :-)
> 
> So what is our disagreement?

The need for a different solution than the MIPv6-integrated 
IPv6-in-UDPv4 solution proposed in the current draft.

>>>> No that's right.  Although I'd see that as a Firewall function, 
>>>> rather than a NAT, but that's quibbling about words.
>>> 
>>> Right, I think it is obvious that most deployed NATs in commercial 
>>> networks employ firewall filtering as well.
>> 
>> Yes.  But calling it a NAT problem confuses the issue, when it is a
>> Firewall problem.
> 
> Ok, I'll call it a Firewall problem and suggest to be dealt with in this
> document.

Right.  I believe that this problem is both large and complex, and
would delay the current document for a year or more.  I'd rather
see this as a separate activity.

>>>> and then have a HA which listens on all ports for your special 
>>>> signature, and responds to that.  Such a mechanism would be
>>>> possible, of course, but should probably be separately specified
>>>> (if at all) ...
>>> 
>>> Well, I think without it the NAT traversal alone is less
>>> applicable.
>> 
>> Marginally.
> 
> Ok, let me put it other way: this document is useless without Firewall
> traversal.

Useless?  Hmm.  Disagreement.


[...]
>>> All providers of Internet access to wireless mobile nodes (WiFi,
>>> GPRS, UMTS) I've tried do one the following:
>>> 
>>> -offer a v4 address that is private behind NAT, or offer a public
>>> v4 address.  But in both cases, the address is subject to change
>>> whenever either a re-connection is made (pppd or dhcpd) by the user
>>> or the connection is lost due to wireless changes.  The access to
>>> wireless mobile nodes I've tried does not have the ability to
>>> provide a permanent v4 address (like the ISP at home may provide).
>>> However, in the GPRS and UMTS cases the address is stable with
>>> respect to changing Base Stations.
>> 
>> 
>> This scenario we can handle with MIP and NAT traversal.
> 
> I agree, but I wanted to say that MN's v4 public address is more subject
> to change than when the v4 address is private (the NAT public v4 address
> is more stable).

Agreed.

> Which in the context of IPv6-IPv6-in-UDPv4 tunnel
> means some dynamic adaptation.  But I think we don't agree about
> IPv6-in-IPv6-in-UDPv4 in the first place.
> 
>>> -use firewalls between MN and Internet, with various ports blocked.
>>> 
>> 
>> This is harder, and the best is probably to vote with your feet -
>> i.e., choose providers which don't do such silliness, as far as
>> possible.
> 
> Well I often do what my bank allows me to do, and the cheaper cell
> wireless subscriptions are the ones that are most firewalled.  The most
> expensive subscriptions are the ones where I could have my own Firewall
> rules.  The cheapest subscriptions are the ones used by the largest
> number of people, so potential wider deployment for this solution if it
> addresses the Firewall aspects.

Agreed.  But consider this:  If you're talking about cellular services,
rather than in general, it's not even a classic firewall issue, as
some (most?) cellular operators will open and close ports dynamically
dependent on what other services you are using at the time.  So the
only ports found open in that case will probably be the ones you are
already using for a service, and thus not necessarily available for
another service, or with more than one server...

	Henrik

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



From mip6-bounces@ietf.org Tue Oct 25 08:19:35 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUNdS-00017A-7I; Tue, 25 Oct 2005 08:10:34 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUNdR-000175-Er
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 08:10:33 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA11003
	for <mip6@ietf.org>; Tue, 25 Oct 2005 08:10:19 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUNqN-0008Rg-Ks
	for mip6@ietf.org; Tue, 25 Oct 2005 08:23:57 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id j9PC9sd08943; Tue, 25 Oct 2005 14:09:54 +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
	j9PC9rAF096467; Tue, 25 Oct 2005 14:09:53 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200510251209.j9PC9rAF096467@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: "COMBES Jean-Michel RD-MAPS-ISS" <jeanmichel.combes@francetelecom.com>
Subject: Re: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt 
In-reply-to: Your message of Mon, 24 Oct 2005 19:08:51 +0200.
	<D2AA6DF1AEE4404F8D983B68BAC97CD2022B914C@ftrdmel3.rd.francetelecom.fr>
Date: Tue, 25 Oct 2005 14:09:53 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Cc: Gerardo Giaretta <Gerardo.Giaretta@tilab.com>, 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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   If you want to update the DNS servers frequently, DNSSEC cannot be
   usable:
   - for each update you will have to sign the zone
   - for each update you will have to transfer the signed zone to the
   secondary servers
   ...
   
=> this is not true: you can use dynamic updates and you can put
the critical RRs in a small zone in order to mitigate the main issue
of dynamic updates with DNSSEC (the private key must be online).

   So forget DNSSEC in such a case: result, no more security.
   
=> I disagree: the only real problem with DNSSEC is it is not yet
deployed.

Regards

Francis.Dupont@enst-bretagne.fr

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



From mip6-bounces@ietf.org Tue Oct 25 08:15:55 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUNid-0002zC-I9; Tue, 25 Oct 2005 08:15:55 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUNib-0002v8-FO
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 08:15:53 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA12078
	for <mip6@ietf.org>; Tue, 25 Oct 2005 08:15:39 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUNvX-0000Oz-Nj
	for mip6@ietf.org; Tue, 25 Oct 2005 08:29:16 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id j9PCFTd09400
	for <mip6@ietf.org>; Tue, 25 Oct 2005 14:15:29 +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
	j9PCFTFu096498
	for <mip6@ietf.org>; Tue, 25 Oct 2005 14:15:29 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200510251215.j9PCFTFu096498@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: mip6@ietf.org
Date: Tue, 25 Oct 2005 14:15:29 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Subject: [Mip6] load balancing and HA (re-)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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

If HA assignment can help load balancing by selecting a less loaded HA,
it works only in the bootstrapping phase and as the load is not
proportional to the number of served MN (i.e., the load doesn't come only
from background traffic) IMHO it is more important to be able to
move some MNs from an overloaded HA, i.e., load balancing is a good
reason to ask for HA re-assignement but not for HA assignment.

So I believe we should work on HA-HA and HA-switch documents and
as the HA-switch is more mature make it a WG item and submit it
to IESG review ASAP?

Regards

Francis.Dupont@enst-bretagne.fr

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



From mip6-bounces@ietf.org Tue Oct 25 08:19:38 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUNdL-00016e-4i; Tue, 25 Oct 2005 08:10:27 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUNdI-00016W-Ui
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 08:10:25 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA10995
	for <mip6@ietf.org>; Tue, 25 Oct 2005 08:10:10 -0400 (EDT)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUNqG-0008SH-5J
	for mip6@ietf.org; Tue, 25 Oct 2005 08:23:48 -0400
Received: from il06exr04.mot.com (il06exr04.mot.com [129.188.137.134])
	by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id j9PCMJMr026254;
	Tue, 25 Oct 2005 05:22:19 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by il06exr04.mot.com (8.13.1/8.13.0) with ESMTP id j9PCINMO020979;
	Tue, 25 Oct 2005 07:18:24 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id 2199C865980; Tue, 25 Oct 2005 14:10:22 +0200 (CEST)
Message-ID: <435E20AE.1060005@motorola.com>
Date: Tue, 25 Oct 2005 14:10:22 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: Henrik Levkowetz <henrik@levkowetz.com>
Subject: Re: [Mip6] More comments on draft-ietf-mip6-nemo-v4traversal-00.txt
References: <435CF254.6050508@motorola.com> <435D0459.8050605@levkowetz.com>
	<435D250B.6040507@motorola.com>
	<435D32A5.4010400@levkowetz.com> <435DF9F1.60203@motorola.com>
	<435DFD3F.4020309@levkowetz.com> <435E0743.4030904@motorola.com>
	<435E1143.8000001@levkowetz.com>
In-Reply-To: <435E1143.8000001@levkowetz.com>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 67c1ea29f88502ef6a32ccec927970f0
Content-Transfer-Encoding: 7bit
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Hello Henrik,

Henrik Levkowetz wrote:
>> I am not sure I understand what - other than the claimed
>> inefficiency - are the disadvantages of using IPv6-in-UDPv4 tunnel
>> interface.
> 
> Personally I think it's the overhead both in tunnelling and setup. 
> There may be complexity and deployment issues, too, but those have 
> had less scrutiny.

Ok.

>> I could explain further what I mean by IPv6-in-UDPv4.  The MN
>> maintains a virtual interface called u0, the Gateway too.  This
>> interface is IPv4 and IPv6 enabled.  All packets MN sends to its u0
>> will be encapsulated by tunnelling software into UDPv4 and sent to
>> the Gateway, which decapsulates.  The tunnelling software on
>> Gateway dynamically puts up its u0 and parametered with the
>> local/remote IP addresses and port numbers.  Same on the MN.
>> Additionally the Gateway sends IPv6 RAs on that interface, so the
>> MN can auto-configure a CoA and do MIP6 mobility unmodified.  I
>> don't see anything wrong with that.
> 
> This sounds very close to Pascal Thubert's Doors proposal, which has 
> been discussed in the design team, without the team settling on one 
> proposed solution yet.

Yes, it is very close to Pascal's proposal.

>>>>> So we seem to disagree on the need for this solution, not on
>>>>> the details of the actual proposed solution.
>>>> 
>>>> We seem to disagree on the possibility/impossibility to have
>>>> double encapsulation IPv6-in-IPv6-in-UDPv4 performed by MN.  We
>>>> haven't yet discussed advantages/disavdntages of using
>>>> IPv6-in-UDPv4.
>>> 
>>> Well, I'll disagree on your statement here - I don't think this
>>> is our disagreement :-)
>> 
>> So what is our disagreement?
> 
> The need for a different solution than the MIPv6-integrated 
> IPv6-in-UDPv4 solution proposed in the current draft.

Right, we don't agree on the need for a different solution than the one
presented in the draft.  We haven't discussed the security of it either.

>>>>> No that's right.  Although I'd see that as a Firewall
>>>>> function, rather than a NAT, but that's quibbling about
>>>>> words.
>>>> 
>>>> Right, I think it is obvious that most deployed NATs in
>>>> commercial networks employ firewall filtering as well.
>>> 
>>> Yes.  But calling it a NAT problem confuses the issue, when it is
>>> a Firewall problem.
>> 
>> Ok, I'll call it a Firewall problem and suggest to be dealt with in
>> this document.
> 
> Right.  I believe that this problem is both large and complex, and 
> would delay the current document for a year or more.  I'd rather see
> this as a separate activity.

Ok, UDP path discovery through arbitrary Firewalls may be large and
complex and may take too long time to specify.  And if the users of this
document are satisfied with it without UDP path discovery - I'm fine.

>>>>> and then have a HA which listens on all ports for your
>>>>> special signature, and responds to that.  Such a mechanism
>>>>> would be possible, of course, but should probably be
>>>>> separately specified (if at all) ...
>>>> 
>>>> Well, I think without it the NAT traversal alone is less 
>>>> applicable.
>>> 
>>> Marginally.
>> 
>> Ok, let me put it other way: this document is useless without
>> Firewall traversal.
> 
> Useless?  Hmm.  Disagreement.

Probably 'useless' was too strong a word.

It is important to identify who are the potential users of the solution
described in this draft.

>>>> -use firewalls between MN and Internet, with various ports
>>>> blocked.
>>>> 
>>> 
>>> This is harder, and the best is probably to vote with your feet -
>>>  i.e., choose providers which don't do such silliness, as far as 
>>> possible.
>> 
>> Well I often do what my bank allows me to do, and the cheaper cell 
>> wireless subscriptions are the ones that are most firewalled.  The
>> most expensive subscriptions are the ones where I could have my own
>> Firewall rules.  The cheapest subscriptions are the ones used by
>> the largest number of people, so potential wider deployment for
>> this solution if it addresses the Firewall aspects.
> 
> 
> Agreed.  But consider this:  If you're talking about cellular
> services, rather than in general, it's not even a classic firewall
> issue, as some (most?) cellular operators will open and close ports
> dynamically dependent on what other services you are using at the
> time.  So the only ports found open in that case will probably be the
> ones you are already using for a service, and thus not necessarily
> available for another service, or with more than one server...

Even in that case, the dynamic behaviour of the Firewalls could be
discovered dynamically by the MN, at least in theory, and in some
manually-helped automatic practical cases.

Alex

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



From mip6-bounces@ietf.org Tue Oct 25 08:22:44 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUNpE-0006pS-Bt; Tue, 25 Oct 2005 08:22:44 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUNpD-0006pK-3I
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 08:22:43 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA13032
	for <mip6@ietf.org>; Tue, 25 Oct 2005 08:22:29 -0400 (EDT)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUO29-0000nk-Gk
	for mip6@ietf.org; Tue, 25 Oct 2005 08:36:06 -0400
Received: from il06exr04.mot.com (il06exr04.mot.com [129.188.137.134])
	by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id j9PCYYvq028116;
	Tue, 25 Oct 2005 05:34:34 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by il06exr04.mot.com (8.13.1/8.13.0) with ESMTP id j9PCUdoM025256;
	Tue, 25 Oct 2005 07:30:40 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id E47F1865980; Tue, 25 Oct 2005 14:22:37 +0200 (CEST)
Message-ID: <435E238D.4070506@motorola.com>
Date: Tue, 25 Oct 2005 14:22:37 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: Kilian Weniger <Kilian.Weniger@eu.panasonic.com>
Subject: Re: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
References: <4D2F935F08D41A4C8866693F4F0D7C4F58E728@lan-ex-01.panasonic.de>
In-Reply-To: <4D2F935F08D41A4C8866693F4F0D7C4F58E728@lan-ex-01.panasonic.de>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Content-Transfer-Encoding: 7bit
Cc: 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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Kilian Weniger wrote:
>> I think it is impossible to provide load balancing between 
>> different HAs on different subnets while maintaining a permanent 
>> Home Address for the Mobile Node.
> 
> I wouldn't say that it is impossible, at least not if you think of 
> load balancing in terms of the amount of data traffic routed over an 
> HA in bi-directional tunneling mode. For instance, 
> draft-weniger-rota-01 or draft-thubert-nemo-global-haha-01.txt might 
> in principle enable load balancing between different HAs on different
>  subnets while maintaining a permanent Home Address.

For Global HAHA: after a new HA is selected, the packets from CN to HoA
must reach the new HA instead of the old HA; this can be achieved with
some form of route update, or tunneling.  If route updates can be used
on a global scale (Global HAHA) then there's no need of Mobile IPv6 at
all, just update the routes between CN and HoA and make MN keep the same
HoA wherever it goes.  If tunnelling between old HA and new HA is used
then after each HA re-selection all previous HAs are being used,
tunnelling from one to another.

For draft-weniger-rota-01: I have to read it first.

> However, both solutions are not specifically designed for load
> balancing, e.g., a mechanism to exchange load conditions across
> subnets would be needed.

I agree.

Alex

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



From mip6-bounces@ietf.org Tue Oct 25 08:24:22 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUNqo-00077T-11; Tue, 25 Oct 2005 08:24:22 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUNqm-00077G-1Z
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 08:24:20 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA13121
	for <mip6@ietf.org>; Tue, 25 Oct 2005 08:24:05 -0400 (EDT)
Received: from 33.106-14-84.ripe.coltfrance.com ([84.14.106.33]
	helo=proxy.6wind.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1EUO3j-0000pF-CX
	for mip6@ietf.org; Tue, 25 Oct 2005 08:37:43 -0400
Received: from [10.16.0.164] (unknown [10.16.0.164])
	by proxy.6wind.com (Postfix) with ESMTP id BAD31525F84;
	Tue, 25 Oct 2005 14:23:58 +0200 (CEST)
Message-ID: <435E23B8.7090004@6wind.com>
Date: Tue, 25 Oct 2005 14:23:20 +0200
From: Jean-Mickael Guerin <jean-mickael.guerin@6wind.com>
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: mip6@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Content-Transfer-Encoding: 7bit
Subject: [Mip6] mipext-advapi-04: sending HAO
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Hi,

Quoting section 3:

    For sending Home Address destination option, ancillary data can be 
    used to specify the option content for a single datagram. This
    only applies to datagram and raw sockets; not to TCP sockets.
    Advanced API [1] document restricts one IPV6_xxx ancillary data
    object for a particular extension header in the control buffer.
    Thus there would be a single ancillary data object for Home address
    destination option in a ancillary data buffer. If the kernel
    implementation supports this API, it is responsible for extracting
    the Home address destination option data object and placing it as
    destination option extension header in compliance with section
    6.3 of Mobile IPv6 [2] base specification.

I believe there is one assumption that should be explicitly written - when 
a system supports mip advanced api, then the kernel is in charge of swapping source
 address and HAO content before sending the packet.

I would like to be sure that my MIP6 application behaves the same across all systems,
which sets HoA as source address and care-of address as HAO before the call to sendmsg().

Regards,

Jean-Mickael


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



From mip6-bounces@ietf.org Tue Oct 25 08:39:02 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUO50-0004MQ-Q6; Tue, 25 Oct 2005 08:39:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUO4v-0004ME-Aw
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 08:39:01 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA13924
	for <mip6@ietf.org>; Tue, 25 Oct 2005 08:38:43 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUOHr-0001E9-LY
	for mip6@ietf.org; Tue, 25 Oct 2005 08:52:21 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id j9PCcSd11466; Tue, 25 Oct 2005 14:38:28 +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
	j9PCcR4a096662; Tue, 25 Oct 2005 14:38:27 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200510251238.j9PCcR4a096662@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Alexandru Petrescu <alexandru.petrescu@motorola.com>
Subject: Re: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt 
In-reply-to: Your message of Mon, 24 Oct 2005 20:27:15 +0200.
	<435D2783.8080702@motorola.com> 
Date: Tue, 25 Oct 2005 14:38:27 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
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>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   > OK. So, what is the destination address for DHAAD?
   
   The DHAAD Request would be sent to a 'reserved' address that is derived
   from the home link prefix, called 'all HAs for DHAAD".  The HAs select
   amongst themselves a 'leader' and only one of them replies back, using
   src IPv6 address as its own globally unique IPv6 address (not the
   'reserved' address).
   
=> this is not enough different from the current DHAAD, i.e., in
place of the routing choice for the anycast group member, you propose
to elect a HA master. All the IPsec issues remain.

   Example of such reserved address could be
   3ffe:dddd:eeee:aaaa:fefff:ffff:ffff:ffee (note the common part
                       fefff:ffff:ffff:ffee)
   
   Every HA on the home link would have the address
   3ffe:dddd:eeee:aaaa:fefff:ffff:ffff:ffee assigned to its interface and
   do NA for it as if it were a normal IPv6 address, and it would also have
    assigned its globally unique IPv6 address (derived from
   3ffe:dddd:eeee:aaaa:EUI-64).
   
   The HAs select amongst themselves a leader with the tool that MIP6
   provides which is the H bit in the RA a HA sends on the link.
   
=> for the election I propose to use the HA with the lowest IID...

If we'd like to make the non-anycast DHAAD compatible it is better
to use another well known address and to give it to the master.
But this is very similar to VRRP and there is already a VRRP/HA I-D
so I believe we should first look at this I-D which seems a good
complement to the HA-switch stuff (VRRP is transparent and should be
more efficient but can only switch the HA instance, not the whole HA,
IMHO both don't address the same problem).

Regards

Francis.Dupont@enst-bretagne.fr

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



From mip6-bounces@ietf.org Tue Oct 25 08:45:41 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUOBR-0000ee-Rr; Tue, 25 Oct 2005 08:45:41 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUOBQ-0000eW-Js
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 08:45:40 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA14324
	for <mip6@ietf.org>; Tue, 25 Oct 2005 08:45:26 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUOOM-0001PX-MX
	for mip6@ietf.org; Tue, 25 Oct 2005 08:59:04 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id j9PCjDd12075; Tue, 25 Oct 2005 14:45:13 +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
	j9PCjDbg096705; Tue, 25 Oct 2005 14:45:13 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200510251245.j9PCjDbg096705@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Alexandru Petrescu <alexandru.petrescu@motorola.com>
Subject: Re: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt 
In-reply-to: Your message of Mon, 24 Oct 2005 20:31:07 +0200.
	<435D286B.4060708@motorola.com> 
Date: Tue, 25 Oct 2005 14:45:13 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   > If it has already a HA and wants just to get other available HA IMHO 
   > HA-switch (as a re-assignment mechanism) is a better solution.
   
   Well, DHAAD Reply contains a list of HAs ordered by priorities.  Once it
   has that list the MN could switch to another one, provided of course
   that the HAs have their BCs synched.
   
=> I don't believe the BCs should be synched. In (any) DHAAD reselection
or HA-switch, the MN knows it will use a different HA so it will start
a new bootstrapping phase. But if the HA change is transparent (i.e.,
if the MN doesn't know it is switching from a HA to another one, note
this seems to imply the HA address stays the same so a VRRP-like
mechanism) the BCs and IPsec state must be synched or synchable.

Regards

Francis.Dupont@enst-bretagne.fr

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



From mip6-bounces@ietf.org Tue Oct 25 08:48:07 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUODn-0001r5-Sz; Tue, 25 Oct 2005 08:48:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUODm-0001ny-MS
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 08:48:06 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA14419
	for <mip6@ietf.org>; Tue, 25 Oct 2005 08:47:52 -0400 (EDT)
Received: from dns2.tilab.com ([163.162.42.5])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUOQe-0001T4-UL
	for mip6@ietf.org; Tue, 25 Oct 2005 09:01:30 -0400
Received: from iowa2k01b.cselt.it ([163.162.242.202])
	by dns2.cselt.it (PMDF V6.1 #38895)
	with ESMTP id <0IOX00D8227M31@dns2.cselt.it> for mip6@ietf.org; Tue,
	25 Oct 2005 14:47:46 +0200 (MEST)
Received: from EXC01B.cselt.it ([163.162.4.199]) by iowa2k01b.cselt.it with
	Microsoft SMTPSVC(6.0.3790.211); Tue, 25 Oct 2005 14:45:25 +0200
Date: Tue, 25 Oct 2005 14:47:46 +0200
From: Gerardo Giaretta <Gerardo.Giaretta@TILAB.COM>
Subject: RE: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
To: COMBES Jean-Michel RD-MAPS-ISS <jeanmichel.combes@francetelecom.com>
Message-id: <DA62A6E0CDD1B34A84557FF1AC850C57016E9CD8@EXC01B.cselt.it>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.3790.326
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: quoted-printable
Importance: normal
Priority: normal
Thread-Topic: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
thread-index: AcXYmAy19R9rZjd5Q6uwsLFw5TPmRAAFeDcgAAJ6ldAAAVGoIAAAcJUwACiY8KA=
Content-Class: urn:content-classes:message
X-OriginalArrivalTime: 25 Oct 2005 12:45:25.0234 (UTC)
	FILETIME=[F864D520:01C5D961]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6ba8aaf827dcb437101951262f69b3de
Content-Transfer-Encoding: quoted-printable
Cc: mip6@ietf.org, Kilian Weniger <Kilian.Weniger@eu.panasonic.com>,
	Francis Dupont <Francis.Dupont@enst-bretagne.fr>,
	Petrescu Alexandru-AAP021 <alexandru.petrescu@motorola.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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

> > If in your opinion exposing HA addresses in DNS is an issue, in
> > integrated scenario a DHCP-based solution may be used (see the
> > integarted scenario draft).=20
> >=20
> > > For the moment, with these proposals, the MSP has not the=20
> > > possibility to
> > > manage its HA as he wants ...
> > >=20
> >=20
> > Why in DNS-based solution you think this is not possible?=20
>=20
> This is the MN that will choose the HA from the listed HA in the DNS.
>=20

Not entirely. The SRV specification, as Henrik mentioned before in
another thread, provides for priorities between multiple Home Agents.
The list of HAs with priorities may be considered similar to the list
received by the MN via DHAAD. The MN will choose based on these
priorities. Otherwise, in integrated scenario, DHCP can be used. As
mentioned before, if you need a very strict control on the HA assignment
by the operator, IMHO the best way is to perform it during network
access authentication, but unfortunately this is not a general solution.


--Gerardo

> >=20
> > > Regarding the two present solutions:
> > > o DNS-based DHAAD
> > > I don't like this solution because such mechanism gives the=20
> > location,
> > > for a MSP, of all its HA, which are the MIPv6 point of=20
> > failure and so
> > > the prioritized targets for "bad guys". You give the stick to=20
> > > be beaten
> > > ... :(
> >=20
> > Sorry are you referring to DNS-based HA discovery defined in
> > draft-ietf-mip6-bootstrapping-split-01
>=20
> Yes.
>=20
> >  or something else? I'm getting
> > confused with the acronym DHAAD since it is usually used to=20
> refer the
> > solution defined in rfc3775.
>=20
> Sorry :)
>=20
> JMC.
>=20
> >=20
> > --Gerardo
> >=20
> > > o ICMP-based mechanism
> > > Here again, the present mechanism gives all the HA but I=20
> > > think it may be
> > > simply modified to give only one HA if the MSP wants to assign HA.
> > > The main issue is regarding its security ... Maybe=20
> > > Alexandru's proposal
> > > or HAHA proposal would be interesting.
> > >=20
> > > Best regards.
> > >=20
> > > JMC.
> > >=20
> > > France Telecom - R&D Division - MAPS/NSS  =20
> > > Jean-Michel COMBES, Internet/Intranet Security
> > > E-Mail: jeanmichel.combes@francetelecom.com
> > > Phone: +33 (0)1 45 29 45 94
> > > Fax: +33 (0)1 45 29 65 19
> > > Mobile: +33 (0)6 07 29 30 16=20
> > > =20
> > >=20
> > > > -----Original Message-----
> > > > From: mip6-bounces@ietf.org [mailto:mip6-bounces@ietf.org] On=20
> > > > Behalf Of Narayanan Vidya-CVN065
> > > > Sent: Monday, October 24, 2005 5:21 PM
> > > > To: Francis Dupont; Petrescu Alexandru-AAP021
> > > > Cc: mip6@ietf.org; Kilian Weniger; James Kempf
> > > > Subject: RE: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt=20
> > > >=20
> > > > >   =20
> > > > > =3D> the two questions are:
> > > > >  - should we keep a DHAAD mechanism or HA assignment is=20
> > the right=20
> > > > > thing
> > > > >    to do?
> > > > >  - is the DNS-based DHAAD mechanism better enough to=20
> > replace the=20
> > > > > ICMP-base
> > > > >    one?
> > > > >=20
> > > >=20
> > > > These are good questions. I believe that a DNS-based=20
> > > > mechanism is largely better than an ICMP-based mechansim. For=20
> > > > those who wish to secure the operation, at least an option is=20
> > > > available. Whether DNSSEC will be widely deployed is a=20
> > > > separate question, but at least, it is an option. Also, it=20
> > > > moves away from having to configure the home network prefix=20
> > > > and removes the limitation of dynamic HA assignment within=20
> > > > the same subnet, both of which are big pluses in my mind.=20
> > > >=20
> > > > Regards,
> > > > Vidya
> > > >=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
> >=20
> >=20
> > Gruppo Telecom Italia - Direzione e coordinamento di Telecom=20
> > Italia S.p.A.
> >=20
> > =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> > CONFIDENTIALITY NOTICE
> > This message and its attachments are addressed solely to the persons
> > above and may contain confidential information. If you have received
> > the message in error, be informed that any use of the content hereof
> > is prohibited. Please return it immediately to the sender and delete
> > the message. Should you have any questions, please send an=20
> e_mail to=20
> > MailAdmin@tilab.com. Thank you
> > =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >=20
>=20


Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia =
S.p.A.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
CONFIDENTIALITY NOTICE
This message and its attachments are addressed solely to the persons
above and may contain confidential information. If you have received
the message in error, be informed that any use of the content hereof
is prohibited. Please return it immediately to the sender and delete
the message. Should you have any questions, please send an e_mail to
MailAdmin@tilab.com. Thank you
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

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



From mip6-bounces@ietf.org Tue Oct 25 08:49:45 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUOFN-0002Dq-48; Tue, 25 Oct 2005 08:49:45 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUOFL-0002Df-T4
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 08:49:43 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA14485
	for <mip6@ietf.org>; Tue, 25 Oct 2005 08:49:29 -0400 (EDT)
Received: from motgate2.mot.com ([144.189.100.101])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUOSI-0001Vo-Es
	for mip6@ietf.org; Tue, 25 Oct 2005 09:03:07 -0400
Received: from az33exr03.mot.com (az33exr03.mot.com [10.64.251.233])
	by motgate2.mot.com (8.12.11/Motgate2) with ESMTP id j9PD4ZhJ009978;
	Tue, 25 Oct 2005 06:04:35 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by az33exr03.mot.com (8.13.1/8.13.0) with ESMTP id j9PCwdXw003598;
	Tue, 25 Oct 2005 07:58:40 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id 70A71865980; Tue, 25 Oct 2005 14:49:21 +0200 (CEST)
Message-ID: <435E29D1.4040606@motorola.com>
Date: Tue, 25 Oct 2005 14:49:21 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
Subject: Re: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
References: <200510251245.j9PCjDbg096705@givry.rennes.enst-bretagne.fr>
In-Reply-To: <200510251245.j9PCjDbg096705@givry.rennes.enst-bretagne.fr>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Content-Transfer-Encoding: 7bit
Cc: James Kempf <Kempf@docomolabs-usa.com>, 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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Francis Dupont wrote:
> In your previous mail you wrote:
> 
>> If it has already a HA and wants just to get other available HA
>> IMHO HA-switch (as a re-assignment mechanism) is a better solution.
>> 
> 
> Well, DHAAD Reply contains a list of HAs ordered by priorities.  Once
> it has that list the MN could switch to another one, provided of
> course that the HAs have their BCs synched.
> 
> => I don't believe the BCs should be synched. In (any) DHAAD
> reselection or HA-switch, the MN knows it will use a different HA so
> it will start a new bootstrapping phase.

I agree.

> But if the HA change is transparent (i.e., if the MN doesn't know it
> is switching from a HA to another one, note this seems to imply the
> HA address stays the same so a VRRP-like mechanism) the BCs and IPsec
> state must be synched or synchable.

Right.

Alex

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



From mip6-bounces@ietf.org Tue Oct 25 08:50:14 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUOFq-0002KD-Jn; Tue, 25 Oct 2005 08:50:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUOFp-0002Io-C6
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 08:50:13 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA14505
	for <mip6@ietf.org>; Tue, 25 Oct 2005 08:49:59 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUOSm-0001WY-Tb
	for mip6@ietf.org; Tue, 25 Oct 2005 09:03:37 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id j9PCnsd12376; Tue, 25 Oct 2005 14:49:54 +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
	j9PCns73096749; Tue, 25 Oct 2005 14:49:54 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200510251249.j9PCns73096749@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Alexandru Petrescu <alexandru.petrescu@motorola.com>
Subject: Re: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt 
In-reply-to: Your message of Mon, 24 Oct 2005 20:34:27 +0200.
	<435D2933.8060103@motorola.com> 
Date: Tue, 25 Oct 2005 14:49:54 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   Same with non-anycast DHAAD, the mobile must have some
   pre-configuration, like the home link prefix, which makes more sense
   that pre-configuring a domain name I believe.
   
=> IMHO to pre-config the home link prefix or to pre-config a domain
name which will be resolved into the home link prefix are equivalent.
The DNS request adds an indirection which can be used to make the home
link prefix dynamic... The choice between is clearly a matter of taste
and it is very easy to implement both.

Regards

Francis.Dupont@enst-bretagne.fr

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



From mip6-bounces@ietf.org Tue Oct 25 08:51:10 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUOGj-0002d8-VM; Tue, 25 Oct 2005 08:51:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUOGi-0002cu-AG
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 08:51:08 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA14610
	for <mip6@ietf.org>; Tue, 25 Oct 2005 08:50:54 -0400 (EDT)
Received: from dns2.tilab.com ([163.162.42.5])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUOTe-0001ZA-Mu
	for mip6@ietf.org; Tue, 25 Oct 2005 09:04:32 -0400
Received: from iowa2k01b.cselt.it ([163.162.242.202])
	by dns2.cselt.it (PMDF V6.1 #38895)
	with ESMTP id <0IOX00D9D2CX09@dns2.cselt.it> for mip6@ietf.org; Tue,
	25 Oct 2005 14:50:57 +0200 (MEST)
Received: from EXC01B.cselt.it ([163.162.4.199]) by iowa2k01b.cselt.it with
	Microsoft SMTPSVC(6.0.3790.211); Tue, 25 Oct 2005 14:48:35 +0200
Date: Tue, 25 Oct 2005 14:50:57 +0200
From: Gerardo Giaretta <Gerardo.Giaretta@TILAB.COM>
Subject: RE: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
To: Narayanan Vidya-CVN065 <vidya@motorola.com>
Message-id: <DA62A6E0CDD1B34A84557FF1AC850C57016E9CD9@EXC01B.cselt.it>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.3790.326
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: quoted-printable
Importance: normal
Priority: normal
Thread-Topic: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
thread-index: AcXYshVqC3Cr5Dl6R92gdU43XTtRpwAAV9iwAAH0bOAAAXzvsAAoTRCg
Content-Class: urn:content-classes:message
X-OriginalArrivalTime: 25 Oct 2005 12:48:35.0890 (UTC)
	FILETIME=[6A08A120:01C5D962]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Content-Transfer-Encoding: quoted-printable
Cc: mip6@ietf.org, Kilian Weniger <Kilian.Weniger@eu.panasonic.com>,
	Francis.Dupont@enst-bretagne.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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Hi Vidya,=20

> >=20
> > I agree that HA switch may have large signaling overhead.=20
> > However, as said in my previous post I think it is quite=20
> > difficult to achieve load balancing in spit scenario during=20
> > HA discovery if we rule out DHAAD. In integrated scenario,=20
> > the issue may be less tricky.
> >=20
>=20
> Hopefully, the system is not causing a lot of HA switching due to load
> balancing - that would be a very unstable system. I would expect that
> load balancing based HA assignment can be made at the beginning and it
> would be very rare that a switch in HA for a given MN happens
> subsequently due to load balancing.=20
>=20

I agree that HA switching due to load balancing will not be very
frequent.

> DNS can't provide the best load balancing mechanism - however, a
> commonly used method may be to use DNS to get the IP address=20
> of a HA and
> have that HA assign the right HA based on load balancing (and whatever
> other parameters) - so, this is almost like doing a HA switch once (at
> the time of bootstrapping, say). Hopefully, after that, the MN will
> continue to use that HA except in some rare cases when it is asked to
> switch again.=20
>=20

This may be a good solution. However, notice that based on DHCP a better
load balancing HA assignment can be provided.=20

--Gerardo

> Vidya
>=20


Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia =
S.p.A.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
CONFIDENTIALITY NOTICE
This message and its attachments are addressed solely to the persons
above and may contain confidential information. If you have received
the message in error, be informed that any use of the content hereof
is prohibited. Please return it immediately to the sender and delete
the message. Should you have any questions, please send an e_mail to
MailAdmin@tilab.com. Thank you
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

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



From mip6-bounces@ietf.org Tue Oct 25 08:54:46 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUOKE-00036d-3G; Tue, 25 Oct 2005 08:54:46 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUOKD-00036Y-E2
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 08:54:45 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA14735
	for <mip6@ietf.org>; Tue, 25 Oct 2005 08:54:31 -0400 (EDT)
Received: from motgate7.mot.com ([129.188.136.7])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUOXB-0001eO-39
	for mip6@ietf.org; Tue, 25 Oct 2005 09:08:09 -0400
Received: from az33exr02.mot.com ([10.64.251.232])
	by motgate7.mot.com (8.12.11/Motgate7) with ESMTP id j9PDHQfx001713;
	Tue, 25 Oct 2005 06:17:27 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by az33exr02.mot.com (8.13.1/8.13.0) with ESMTP id j9PD1vQn024575;
	Tue, 25 Oct 2005 08:01:58 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id 08FF08637F4; Tue, 25 Oct 2005 14:54:30 +0200 (CEST)
Message-ID: <435E2B06.8020206@motorola.com>
Date: Tue, 25 Oct 2005 14:54:30 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
Subject: Re: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
References: <200510251238.j9PCcR4a096662@givry.rennes.enst-bretagne.fr>
In-Reply-To: <200510251238.j9PCcR4a096662@givry.rennes.enst-bretagne.fr>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
Content-Transfer-Encoding: 7bit
Cc: James Kempf <Kempf@docomolabs-usa.com>, 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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Francis Dupont wrote:

>  In your previous mail you wrote:
> 
>    > OK. So, what is the destination address for DHAAD?
>    
>    The DHAAD Request would be sent to a 'reserved' address that is derived
>    from the home link prefix, called 'all HAs for DHAAD".  The HAs select
>    amongst themselves a 'leader' and only one of them replies back, using
>    src IPv6 address as its own globally unique IPv6 address (not the
>    'reserved' address).
>    
> => this is not enough different from the current DHAAD, i.e., in
> place of the routing choice for the anycast group member, you propose
> to elect a HA master. All the IPsec issues remain.

I'm not sure I understand.  Isn't it possible for MN to have an SA with
'all HAs for DHAAD' address?

Remark that the HA that replies back to MN (1) is not necessarily the HA
that is going to 'serve' the MN and (2) will use its own global unicast
address as src of DHAAD Reply so IPsec would be fine.

Again, this working assumes that all HAs have the same coherent list of
HAs and priorities and that any HA may send back to MN the DHAAD Reply,
and the HA that sends the Reply is not necessarily the HA that is first
priority.  But the MN will use the HA Address that is the first priority
in the received list of HA addresses.

>    Example of such reserved address could be
>    3ffe:dddd:eeee:aaaa:fefff:ffff:ffff:ffee (note the common part
>                        fefff:ffff:ffff:ffee)
>    
>    Every HA on the home link would have the address
>    3ffe:dddd:eeee:aaaa:fefff:ffff:ffff:ffee assigned to its interface and
>    do NA for it as if it were a normal IPv6 address, and it would also have
>     assigned its globally unique IPv6 address (derived from
>    3ffe:dddd:eeee:aaaa:EUI-64).
>    
>    The HAs select amongst themselves a leader with the tool that MIP6
>    provides which is the H bit in the RA a HA sends on the link.
>    
> => for the election I propose to use the HA with the lowest IID...

Well, it sounds as a good practical idea to me.  An HA may use all the
IIDs from all received H-bit RAs to build a common ordered list.  Or
otherwise the HAs may use manually pre-configured priority information
to be sent in the RAs.

> If we'd like to make the non-anycast DHAAD compatible it is better
> to use another well known address and to give it to the master.
> But this is very similar to VRRP and there is already a VRRP/HA I-D
> so I believe we should first look at this I-D which seems a good
> complement to the HA-switch stuff (VRRP is transparent and should be
> more efficient but can only switch the HA instance, not the whole HA,
> IMHO both don't address the same problem).

I have to check that.

Alex


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



From mip6-bounces@ietf.org Tue Oct 25 08:57:36 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUOMy-0004DG-EB; Tue, 25 Oct 2005 08:57:36 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUOMx-0004CI-5k
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 08:57:35 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA14933
	for <mip6@ietf.org>; Tue, 25 Oct 2005 08:57:20 -0400 (EDT)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUOZu-0001jr-Tz
	for mip6@ietf.org; Tue, 25 Oct 2005 09:10:59 -0400
Received: from il06exr04.mot.com (il06exr04.mot.com [129.188.137.134])
	by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id j9PD94uH003599;
	Tue, 25 Oct 2005 06:09:04 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by il06exr04.mot.com (8.13.1/8.13.0) with ESMTP id j9PD59xU010352;
	Tue, 25 Oct 2005 08:05:09 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id 5B4AE865980; Tue, 25 Oct 2005 14:57:07 +0200 (CEST)
Message-ID: <435E2BA3.6030005@motorola.com>
Date: Tue, 25 Oct 2005 14:57:07 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
Subject: Re: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
References: <200510251249.j9PCns73096749@givry.rennes.enst-bretagne.fr>
In-Reply-To: <200510251249.j9PCns73096749@givry.rennes.enst-bretagne.fr>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Content-Transfer-Encoding: 7bit
Cc: James Kempf <Kempf@docomolabs-usa.com>, 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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Francis Dupont wrote:

>  In your previous mail you wrote:
> 
>    Same with non-anycast DHAAD, the mobile must have some
>    pre-configuration, like the home link prefix, which makes more sense
>    that pre-configuring a domain name I believe.
>    
> => IMHO to pre-config the home link prefix or to pre-config a domain
> name which will be resolved into the home link prefix are equivalent.
> The DNS request adds an indirection which can be used to make the home
> link prefix dynamic... The choice between is clearly a matter of taste
> and it is very easy to implement both.

I don't know how to make DNS resolve calls in the kernel and I'd like to
keep all MIP6 IP mobility management in the kernel.

Alex


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



From mip6-bounces@ietf.org Tue Oct 25 08:58:45 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUOO5-0004Vc-BU; Tue, 25 Oct 2005 08:58:45 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUOO3-0004VU-Rm
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 08:58:43 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA14997
	for <mip6@ietf.org>; Tue, 25 Oct 2005 08:58:29 -0400 (EDT)
Received: from dns1.tilab.com ([163.162.42.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUOb1-0001lk-Bq
	for mip6@ietf.org; Tue, 25 Oct 2005 09:12:07 -0400
Received: from iowa2k01a.cselt.it ([163.162.242.201])
	by dns1.cselt.it (PMDF V6.0-025 #38895)
	with ESMTP id <0IOX0045S2PLAQ@dns1.cselt.it> for mip6@ietf.org; Tue,
	25 Oct 2005 14:58:33 +0200 (MEST)
Received: from EXC01B.cselt.it ([163.162.4.199]) by iowa2k01a.cselt.it with
	Microsoft SMTPSVC(6.0.3790.211); Tue, 25 Oct 2005 14:58:33 +0200
Date: Tue, 25 Oct 2005 14:58:32 +0200
From: Gerardo Giaretta <Gerardo.Giaretta@TILAB.COM>
Subject: RE: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
To: Alexandru Petrescu <alexandru.petrescu@motorola.com>
Message-id: <DA62A6E0CDD1B34A84557FF1AC850C57016E9CDA@EXC01B.cselt.it>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.3790.326
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: quoted-printable
Importance: normal
Priority: normal
Thread-Topic: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
thread-index: AcXYym/ZcG6HaeMWTYmcyBNV4eHLzwAmFq4A
Content-Class: urn:content-classes:message
X-OriginalArrivalTime: 25 Oct 2005 12:58:33.0205 (UTC)
	FILETIME=[CE0FAA50:01C5D963]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
Content-Transfer-Encoding: quoted-printable
Cc: mip6@ietf.org, Kilian Weniger <Kilian.Weniger@eu.panasonic.com>,
	Francis.Dupont@enst-bretagne.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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 > >  > > =3D> IMHO load balancing should not be provided by a=20
> DHAAD mechanism
> >=20
> >>>but by HA assignment or HA-switch.
> >>
> >>I agree that HA-switch is needed (not only for load=20
> balancing), but if
> >>an DHAAD mechanism already supports load balancing,=20
> signaling overhead
> >>and delay can be saved by skipping a subsequent HA-switch. If MNs
> >>frequently bootstrap with new HAs (e.g., when always using=20
> local HAs),
> >>the saved signaling overhead and delay might be significant.=20
> >>
> >=20
> >=20
> > I agree that HA switch may have large signaling overhead.=20
> However, as
> > said in my previous post I think it is quite difficult to=20
> achieve load
> > balancing in spit scenario during HA discovery if we rule=20
> out DHAAD. In
> > integrated scenario, the issue may be less tricky.
>=20
> Assume for a moment that RFC 3775 DHAAD had no issue with using IPsec
> and that anycast implementation were deployed, dynamic update=20
> of routes
> such that anycast really works.
>=20
> Would then RFC 3775 DHAAD provide 'load balancing'?
>=20

IMHO, no.

> I'm asking because I think it is not at all clear for everyone what
> 'load balancing' is and how MIP6 is concerned by load balancing.
>=20
> My own take on this is that even if RFC 3775 worked it=20
> wouldn't provide
> 'load balancing' per se.  But, if the HAs co-ordinated themselves
> somehow with some existing load balancing protocol then load balancing
> would be achieved, because the HA list provided in DHAAD Reply and the
> HA list used by MN would allow MN to switch towards wherever=20
> the load is
> minimal.
>=20

This is one reason why it would not be enough. Another one is that it
does not provide load balancing across subnets. Other HA assignment or
other solutions (e.g. HA switch) mechanisms do that.=20

--Gerardo

> Alex
>=20
>=20


Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia =
S.p.A.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
CONFIDENTIALITY NOTICE
This message and its attachments are addressed solely to the persons
above and may contain confidential information. If you have received
the message in error, be informed that any use of the content hereof
is prohibited. Please return it immediately to the sender and delete
the message. Should you have any questions, please send an e_mail to=20
MailAdmin@tilab.com. Thank you
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

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



From mip6-bounces@ietf.org Tue Oct 25 09:03:44 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUOSu-0005xo-I1; Tue, 25 Oct 2005 09:03:44 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUOSt-0005x8-3O
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 09:03:43 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15360
	for <mip6@ietf.org>; Tue, 25 Oct 2005 09:03:28 -0400 (EDT)
Received: from p-mail1.rd.francetelecom.com ([195.101.245.15])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUOfn-0001vH-36
	for mip6@ietf.org; Tue, 25 Oct 2005 09:17:06 -0400
Received: from ftrdmel3.rd.francetelecom.fr ([10.193.117.155]) by
	ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 25 Oct 2005 15:03:37 +0200
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] draft-dupont-mip6-dhaadharmful-00.txt 
Date: Tue, 25 Oct 2005 15:02:32 +0200
Message-ID: <D2AA6DF1AEE4404F8D983B68BAC97CD2022B9153@ftrdmel3.rd.francetelecom.fr>
Thread-Topic: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt 
Thread-Index: AcXZXRtrLl4wumsmQSuwHs2Yc88GsAAAwJQA
From: "COMBES Jean-Michel RD-MAPS-ISS" <jeanmichel.combes@francetelecom.com>
To: <Francis.Dupont@enst-bretagne.fr>
X-OriginalArrivalTime: 25 Oct 2005 13:03:37.0473 (UTC)
	FILETIME=[836B4710:01C5D964]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
Content-Transfer-Encoding: quoted-printable
Cc: Gerardo Giaretta <Gerardo.Giaretta@tilab.com>, 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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org



> -----Original Message-----
> From: Francis.Dupont@enst-bretagne.fr=20
> [mailto:Francis.Dupont@enst-bretagne.fr]=20
> Sent: Tuesday, October 25, 2005 2:10 PM
> To: COMBES Jean-Michel RD-MAPS-ISS
> Cc: Gerardo Giaretta; Kilian Weniger; Alexandru Petrescu;=20
> mip6@ietf.org
> Subject: Re: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt=20
>=20
>  In your previous mail you wrote:
>=20
>    If you want to update the DNS servers frequently, DNSSEC cannot be
>    usable:
>    - for each update you will have to sign the zone
>    - for each update you will have to transfer the signed zone to the
>    secondary servers
>    ...
>   =20
> =3D> this is not true: you can use dynamic updates and you can=20
> put the critical RRs in a small zone in order to mitigate the=20
> main issue of dynamic updates with DNSSEC=20

Maybe, this is a solution but that will depend a lot on the number of HA
the MSP will manage and you will still have to transfer the signed zone
to the secondary servers.


> (the private key=20
> must be online).

Which private key? The one used to sign the zone or to secure the
updates?
If this is the first one, the habit is to avoid to put it online (I know
you know that :)

>=20
>    So forget DNSSEC in such a case: result, no more security.
>   =20
> =3D> I disagree: the only real problem with DNSSEC is it is not=20
> yet deployed.

This is for me another issue (BTW, today, IKEv2 is not deployed too and
most of the work in mip6 are on IKEv2).

>=20
> Regards
>=20
> Francis.Dupont@enst-bretagne.fr
>=20

Regards.

JMC.

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

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



From mip6-bounces@ietf.org Tue Oct 25 09:03:45 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUOSv-0005yG-2h; Tue, 25 Oct 2005 09:03:45 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUOSu-0005xj-5D
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 09:03:44 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15387
	for <mip6@ietf.org>; Tue, 25 Oct 2005 09:03:29 -0400 (EDT)
Received: from ftpbox.mot.com ([129.188.136.101])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUOfq-0001vf-SH
	for mip6@ietf.org; Tue, 25 Oct 2005 09:17:08 -0400
Received: from az33exr02.mot.com (az33exr02.mot.com [10.64.251.232])
	by ftpbox.mot.com (Motorola/Ftpbox) with ESMTP id j9PD3e0n023610;
	Tue, 25 Oct 2005 06:03:40 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by az33exr02.mot.com (8.13.1/8.13.0) with ESMTP id j9PDB4Ud029731;
	Tue, 25 Oct 2005 08:11:05 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id EA1BC865980; Tue, 25 Oct 2005 15:03:37 +0200 (CEST)
Message-ID: <435E2D29.8070509@motorola.com>
Date: Tue, 25 Oct 2005 15:03:37 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
Subject: Re: [Mip6] load balancing and HA (re-)assignment
References: <200510251215.j9PCFTFu096498@givry.rennes.enst-bretagne.fr>
In-Reply-To: <200510251215.j9PCFTFu096498@givry.rennes.enst-bretagne.fr>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Content-Transfer-Encoding: 7bit
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Francis Dupont wrote:

> If HA assignment can help load balancing by selecting a less loaded
> HA, it works only in the bootstrapping phase and as the load is not 
> proportional to the number of served MN (i.e., the load doesn't come
> only from background traffic) IMHO it is more important to be able to
>  move some MNs from an overloaded HA, i.e., load balancing is a good 
> reason to ask for HA re-assignement but not for HA assignment.

I think I agree with this perspective.

> So I believe we should work on HA-HA and HA-switch documents and as
> the HA-switch is more mature make it a WG item and submit it to IESG
> review ASAP?

Before making it a WG item I'd look at whether bootstrapping with DHCPv6
doesn't involve use of some pre-defined DHCPv6 message ("re-acquire"?)
that is sent by server to client and that could be reused or extended to
do the semantics of HA Switch message.

Otherwise, the HA switch draft looks simple and rational and is
something good to work on and advance probably quickly, IMHO.

Alex


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



From mip6-bounces@ietf.org Tue Oct 25 09:06:35 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUOVf-0007Lv-GC; Tue, 25 Oct 2005 09:06:35 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUOVd-0007Fm-Gt
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 09:06:33 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15649
	for <mip6@ietf.org>; Tue, 25 Oct 2005 09:06:19 -0400 (EDT)
Received: from dns2.tilab.com ([163.162.42.5])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUOib-00022i-25
	for mip6@ietf.org; Tue, 25 Oct 2005 09:19:57 -0400
Received: from iowa2k01b.cselt.it ([163.162.242.202])
	by dns2.cselt.it (PMDF V6.1 #38895)
	with ESMTP id <0IOX00E6D32N4T@dns2.cselt.it> for mip6@ietf.org; Tue,
	25 Oct 2005 15:06:23 +0200 (MEST)
Received: from EXC01B.cselt.it ([163.162.4.199]) by iowa2k01b.cselt.it with
	Microsoft SMTPSVC(6.0.3790.211); Tue, 25 Oct 2005 15:04:02 +0200
Date: Tue, 25 Oct 2005 15:06:23 +0200
From: Gerardo Giaretta <Gerardo.Giaretta@TILAB.COM>
Subject: RE: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
To: Kilian Weniger <Kilian.Weniger@eu.panasonic.com>
Message-id: <DA62A6E0CDD1B34A84557FF1AC850C57016E9CDB@EXC01B.cselt.it>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.3790.326
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: quoted-printable
Importance: normal
Priority: normal
Thread-Topic: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
thread-index: AcXYqXbXIA/i8BXYScS1SYiWXuH9KAAAVacgAAMu7pAAH2NZIAALuRIg
Content-Class: urn:content-classes:message
X-OriginalArrivalTime: 25 Oct 2005 13:04:02.0093 (UTC)
	FILETIME=[9217FDD0:01C5D964]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 37af5f8fbf6f013c5b771388e24b09e7
Content-Transfer-Encoding: quoted-printable
Cc: mip6@ietf.org, James Kempf <Kempf@docomolabs-usa.com>,
	Francis.Dupont@enst-bretagne.fr,
	Alexandru Petrescu <alexandru.petrescu@motorola.com>,
	COMBES Jean-Michel RD-MAPS-ISS <jeanmichel.combes@francetelecom.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Hi Kilian,=20

please see some comments below...

>=20
> > Would then RFC 3775 DHAAD provide 'load balancing'?
> >
> > I'm asking because I think it is not at all clear for everyone what
> > 'load balancing' is and how MIP6 is concerned by load balancing.
> > My own take on this is that even if RFC 3775 worked it wouldn't
> provide
> > 'load balancing' per se.  But, if the HAs co-ordinated themselves
> > somehow with some existing load balancing protocol then=20
> load balancing
> > would be achieved, because the HA list provided in DHAAD=20
> Reply and the
> > HA list used by MN would allow MN to switch towards=20
> wherever the load
> is
> > minimal.
>=20
> Yes, some co-ordination between HAs on the home link is required to
> provide dynamic load balancing. I think this can already be achieved
> with DHAAD as defined in RFC3775 by including load condition=20
> in the Home
> Agent Information Option in Ras.=20
>=20
> > As pointed out in draft-ietf-mip6-bootstrapping-split-01,=20
> DNS-based HA
> > discovery may be used only to achieve coarse-grained load=20
> balancing by
> > dynamically updating the SRV RR priorities. On the other hand, DHAAD
> > cannot be used to load balance using different HAs in=20
> > different subnet.
>=20
> I agree, RFC3775 DHAAD cannot provide load balancing between different
> HAs on different subnets. Besides the minimal=20
> pre-configuration, this is
> an advantage of the DNS-based discovery. But I think anycast-based HA
> discovery has advantages as well, e.g., it can support=20
> fine-grained load
> balancing and can decrease delay and signaling overhead during
> bootstrapping. Maybe a combination might become a good solution, e.g.,
>=20
> 1. The MN gets an HA prefix with the DNS-based discovery mechanism (as
> defined in bootstrapping solution). This minimizes the=20
> pre-configuration
> of the MN and can achieve (coarse-grained) load balancing=20
> between HAs of
> different subnets.
>=20
> 2. The MN starts anycast-based HA discovery (not necessarily=20
> as defined
> in RFC3775) using the discovered HA prefix to get the HA address. This
> can support fine-grained load balancing between HAs on the=20
> same link and
> thus results in fast and efficient HA discovery (since subsequent HA
> re-assignment for load balancing is not necessarily required). A
> possible secure and efficient method could be the IKE Security Gateway
> discovery/assignment mechanism mentioned by Francis.
>=20

A similar approach was discussed in the DT: the MN could get a HA prefix
via DNS and then perform DHAAD. However, we agreed that a pure DNS-based
mechanism is better and does not have security concerns as DHAAD.=20


> 3. When load conditions change dramatically or the HA crashs, the MN
> changes its HA using an HA-switch mechanism (this mechanism could also
> provide an optional fine-grained load balancing between HAs=20
> of different
> subnets).
>

I would simplify the procedure a bit: get rid of DHAAD and use HA switch
when a HA re-assignment is needed for any reason (e.g. load balancing).

--Gerardo
=20
> > > So, why this HA - the one assigning the right HA - needs to=20
> > > have HA functionality?
> > >=20
> > It doesn't. It would be a light-weight "HA assigning=20
> entity" - but it
> > may very well be a logical entity collocated with the HA.=20
>=20
> IMHO, a separate assignment entity would be possible, but it would
> probably increase signaling overhead and delay, because the MN has to
> establish another SA during bootstrapping (one to DNS, one to the
> assignment entity and finally one to the assigned HA).=20
>=20
>=20
> Regards,
>=20
> Kilian
>=20
>=20
>=20


Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia =
S.p.A.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
CONFIDENTIALITY NOTICE
This message and its attachments are addressed solely to the persons
above and may contain confidential information. If you have received
the message in error, be informed that any use of the content hereof
is prohibited. Please return it immediately to the sender and delete
the message. Should you have any questions, please send an e_mail to
MailAdmin@tilab.com. Thank you
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

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



From mip6-bounces@ietf.org Tue Oct 25 09:07:05 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUOW9-0007eD-Px; Tue, 25 Oct 2005 09:07:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUOW6-0007dg-Nu
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 09:07:04 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15672
	for <mip6@ietf.org>; Tue, 25 Oct 2005 09:06:48 -0400 (EDT)
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUOj3-00023D-BQ
	for mip6@ietf.org; Tue, 25 Oct 2005 09:20:26 -0400
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id 479E089848
	for <mip6@ietf.org>; Tue, 25 Oct 2005 16:06:39 +0300 (EEST)
Message-ID: <435E2DEB.9020803@kolumbus.fi>
Date: Tue, 25 Oct 2005 16:06:51 +0300
From: Jari Arkko <jari.arkko@kolumbus.fi>
User-Agent: Mozilla Thunderbird 1.0 (X11/20041206)
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; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135
Content-Transfer-Encoding: 7bit
Subject: [Mip6] Review of draft-ietf-mip6-location-privacy-ps-00.txt
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Hi Rajeev,

Thanks for writing a draft on this important issue.
Here are some initial comments:

>   This problem is
>   particularly applicable to Mobile IP where the Home Address on a
>   visited network can reveal device roaming and, together with a
>   user identifier (such as an NAI), can reveal user roaming.  When
>   roaming is revealed, it could lead to more targetted profiling.  Even
>
The part about user identifier comes somewhat out of the
blue here. Are we talking about user identifier and NAI
usage in general? This goes much, much beyond Mobile IPv6.
Or are we talking about Mobile IPv6 use of NAIs? We'd have
to look at the different usage types. One is within IKEv2/EAP
and one is in the auth protocol. They have very different
implications. Also, NAI usage in network access (and also
in IKEv2) has typically a capability for pseudonym usage.

>   Even
>   when the binding between user identifier and the Home Address is
>   unavailable, freely available tools on the Internet can map the Home
>   Address to the owner of the Home Prefix, which can reveal that a user
>   from a particular ISP has roamed. 
>
There seems to be two different problems, one is being
able to see that someone (identified by a home address)
is moving with a specific pattern. The other problem is
identifying that this someone is John Smith or that he is
a customer of Joe's Broadband.

>In addition, a user may not wish to reveal roaming to correspondent(s).
>
It may be worthile to add some discussion about the
different participants. Presumably we can't avoid revealing
information to our home network (or can we?), but most
definately want to avoid revealing information to outsiders,
and probably also in many cases to correspondent nodes.
There may also be different types of outsiders. Complete
strangers (e.g. open 802.11) vs. local access network owners.

(Some discussion of this appears later in the document,
but I'm not sure it provides a full discussion.)

>   2.1. Disclosing the Care of Address
>
The fact that you do not need to reveal care-of address
to correspondent nodes in Mobile IPv6 could perhaps be
mentioned already here.

>The assumption here is that the
>   correspondent somehow knows the Home Address of the MN. For instance,
>   a correspondent may obtain it from DNS, which may contain the Home
>   Address or the IP address of an agent to which the user identifier
>  
>
Hmm... in Mobile IPv6 the home address is always known
to the correspondent. Can you clarify what you mean here?

>When equipped with an ability to inspect
>   packets ``on the wire'', an on-looker can determine that the MN has
>   roamed and could possibly also determine that the user has roamed.
>
I'm not sure I understand teh MN-user distinction.

--Jari


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



From mip6-bounces@ietf.org Tue Oct 25 09:18:31 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUOhD-00050K-NN; Tue, 25 Oct 2005 09:18:31 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUOhC-0004wU-6p
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 09:18:30 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA16203
	for <mip6@ietf.org>; Tue, 25 Oct 2005 09:18:15 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUOu8-0002Jx-Uu
	for mip6@ietf.org; Tue, 25 Oct 2005 09:31:54 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id j9PDI8d14524; Tue, 25 Oct 2005 15:18:08 +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
	j9PDI8Xo097275; Tue, 25 Oct 2005 15:18:08 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200510251318.j9PDI8Xo097275@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Alexandru Petrescu <alexandru.petrescu@motorola.com>
Subject: Re: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt 
In-reply-to: Your message of Mon, 24 Oct 2005 20:40:22 +0200.
	<435D2A96.6020108@motorola.com> 
Date: Tue, 25 Oct 2005 15:18:08 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Cc: Gerardo Giaretta <Gerardo.Giaretta@tilab.com>, 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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   My own take on this is that even if RFC 3775 worked it wouldn't provide
   'load balancing' per se.  But, if the HAs co-ordinated themselves
   somehow with some existing load balancing protocol then load balancing
   would be achieved, because the HA list provided in DHAAD Reply and the
   HA list used by MN would allow MN to switch towards wherever the load is
   minimal.
   
=> my concern is the last "to switch" is in fact "to select".
Without good ideas of real world conditions we can't decide:
 - whether the 'load balancing' in the bootstrapping phase is enough
 - what is the level of 'reactivity' needed to provide this 'load
   balancing', in particular whether the DNS SRV RR mechanism is
   reactive enough (cf RFC 2782 which warns against dynamic weights
   but explains the difference between priorities+weights and precedences)
The only positive thing is the DNS SRV RR mechanism is already heavily
used so it can be considered as mature (i.e., we know where we are going
if we adopt it).
So I propose to close this thread about 'load balancing'.

Regards

Francis.Dupont@enst-bretagne.fr

PS: if someone knows (or has a free student who can write) a
theorical or operational report about DNS SRV RR weights
I am interested.


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



From mip6-bounces@ietf.org Tue Oct 25 09:25:29 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUOnx-0007BF-AQ; Tue, 25 Oct 2005 09:25:29 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUOnw-0007BA-F4
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 09:25:28 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA16584
	for <mip6@ietf.org>; Tue, 25 Oct 2005 09:25:13 -0400 (EDT)
Received: from p-mail2.rd.francetelecom.com ([195.101.245.16])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUP0t-0002VE-6x
	for mip6@ietf.org; Tue, 25 Oct 2005 09:38:52 -0400
Received: from ftrdmel3.rd.francetelecom.fr ([10.193.117.155]) by
	ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 25 Oct 2005 15:25:25 +0200
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] draft-dupont-mip6-dhaadharmful-00.txt
Date: Tue, 25 Oct 2005 15:20:43 +0200
Message-ID: <D2AA6DF1AEE4404F8D983B68BAC97CD2022B9155@ftrdmel3.rd.francetelecom.fr>
Thread-Topic: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
Thread-Index: AcXYmAy19R9rZjd5Q6uwsLFw5TPmRAAFeDcgAAJ6ldAAAVGoIAAAcJUwACiY8KAAANR4wA==
From: "COMBES Jean-Michel RD-MAPS-ISS" <jeanmichel.combes@francetelecom.com>
To: "Gerardo Giaretta" <Gerardo.Giaretta@TILAB.COM>
X-OriginalArrivalTime: 25 Oct 2005 13:25:25.0236 (UTC)
	FILETIME=[8EE81340:01C5D967]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Content-Transfer-Encoding: quoted-printable
Cc: mip6@ietf.org, Kilian Weniger <Kilian.Weniger@eu.panasonic.com>,
	Francis Dupont <Francis.Dupont@enst-bretagne.fr>,
	Petrescu Alexandru-AAP021 <alexandru.petrescu@motorola.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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org


> -----Original Message-----
> From: Gerardo Giaretta [mailto:Gerardo.Giaretta@TILAB.COM]=20
> Sent: Tuesday, October 25, 2005 2:48 PM
> To: COMBES Jean-Michel RD-MAPS-ISS
> Cc: mip6@ietf.org; Kilian Weniger; James Kempf; Narayanan=20
> Vidya-CVN065; Francis Dupont; Petrescu Alexandru-AAP021
> Subject: RE: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
>=20
> > > If in your opinion exposing HA addresses in DNS is an issue, in=20
> > > integrated scenario a DHCP-based solution may be used (see the=20
> > > integarted scenario draft).
> > >=20
> > > > For the moment, with these proposals, the MSP has not the=20
> > > > possibility to manage its HA as he wants ...
> > > >=20
> > >=20
> > > Why in DNS-based solution you think this is not possible?=20
> >=20
> > This is the MN that will choose the HA from the listed HA=20
> in the DNS.
> >=20
>=20
> Not entirely. The SRV specification, as Henrik mentioned=20
> before in another thread, provides for priorities between=20
> multiple Home Agents.
> The list of HAs with priorities may be considered similar to=20
> the list received by the MN via DHAAD. The MN will choose=20
> based on these priorities.

What does prevent the MN to contact the HA he wants? Nothing as far as I
can see.

>  Otherwise, in integrated scenario,=20
> DHCP can be used. As mentioned before, if you need a very=20
> strict control on the HA assignment by the operator, IMHO the=20
> best way is to perform it during network access=20
> authentication, but unfortunately this is not a general solution.

Agree. But I think a operator must have the possibility to assign the HA
in any cases.

>=20
>=20
> --Gerardo

Regards.

JMC.

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

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



From mip6-bounces@ietf.org Tue Oct 25 09:28:03 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUOqR-0007Sm-Ma; Tue, 25 Oct 2005 09:28:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUOqP-0007Sh-RX
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 09:28:01 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA16705
	for <mip6@ietf.org>; Tue, 25 Oct 2005 09:27:47 -0400 (EDT)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUP3N-0002Yl-Kt
	for mip6@ietf.org; Tue, 25 Oct 2005 09:41:26 -0400
Received: from il06exr02.mot.com (il06exr02.mot.com [129.188.137.132])
	by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id j9PDdkuY009645;
	Tue, 25 Oct 2005 06:39:46 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by il06exr02.mot.com (8.13.1/8.13.0) with ESMTP id j9PDaRZ7008256;
	Tue, 25 Oct 2005 08:36:28 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id 5832D865980; Tue, 25 Oct 2005 15:27:49 +0200 (CEST)
Message-ID: <435E32D4.7000702@motorola.com>
Date: Tue, 25 Oct 2005 15:27:48 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: Gerardo Giaretta <Gerardo.Giaretta@TILAB.COM>
Subject: Re: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
References: <DA62A6E0CDD1B34A84557FF1AC850C57016E9CDB@EXC01B.cselt.it>
In-Reply-To: <DA62A6E0CDD1B34A84557FF1AC850C57016E9CDB@EXC01B.cselt.it>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6d95a152022472c7d6cdf886a0424dc6
Content-Transfer-Encoding: 7bit
Cc: mip6@ietf.org, Kilian Weniger <Kilian.Weniger@eu.panasonic.com>,
	James Kempf <Kempf@docomolabs-usa.com>, Francis.Dupont@enst-bretagne.fr,
	Alexandru Petrescu <alexandru.petrescu@motorola.com>,
	COMBES Jean-Michel RD-MAPS-ISS <jeanmichel.combes@francetelecom.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Gerardo Giaretta wrote:

> Hi Kilian,
> 
> please see some comments below...
> 
> 
>>> Would then RFC 3775 DHAAD provide 'load balancing'?
>>> 
>>> I'm asking because I think it is not at all clear for everyone
>>> what 'load balancing' is and how MIP6 is concerned by load
>>> balancing. My own take on this is that even if RFC 3775 worked it
>>> wouldn't
>> 
>> provide
>> 
>>> 'load balancing' per se.  But, if the HAs co-ordinated themselves
>>>  somehow with some existing load balancing protocol then
>> 
>> load balancing
>> 
>>> would be achieved, because the HA list provided in DHAAD
>> 
>> Reply and the
>> 
>>> HA list used by MN would allow MN to switch towards
>> 
>> wherever the load is
>> 
>>> minimal.
>> 
>> Yes, some co-ordination between HAs on the home link is required to
>>  provide dynamic load balancing. I think this can already be
>> achieved with DHAAD as defined in RFC3775 by including load
>> condition in the Home Agent Information Option in Ras.
>> 
>> 
>>> As pointed out in draft-ietf-mip6-bootstrapping-split-01,
>> 
>> DNS-based HA
>> 
>>> discovery may be used only to achieve coarse-grained load
>> 
>> balancing by
>> 
>>> dynamically updating the SRV RR priorities. On the other hand,
>>> DHAAD cannot be used to load balance using different HAs in 
>>> different subnet.
>> 
>> I agree, RFC3775 DHAAD cannot provide load balancing between
>> different HAs on different subnets. Besides the minimal 
>> pre-configuration, this is an advantage of the DNS-based discovery.
>> But I think anycast-based HA discovery has advantages as well,
>> e.g., it can support fine-grained load balancing and can decrease
>> delay and signaling overhead during bootstrapping. Maybe a
>> combination might become a good solution, e.g.,
>> 
>> 1. The MN gets an HA prefix with the DNS-based discovery mechanism
>> (as defined in bootstrapping solution). This minimizes the 
>> pre-configuration of the MN and can achieve (coarse-grained) load
>> balancing between HAs of different subnets.
>> 
>> 2. The MN starts anycast-based HA discovery (not necessarily as
>> defined in RFC3775) using the discovered HA prefix to get the HA
>> address. This can support fine-grained load balancing between HAs
>> on the same link and thus results in fast and efficient HA
>> discovery (since subsequent HA re-assignment for load balancing is
>> not necessarily required). A possible secure and efficient method
>> could be the IKE Security Gateway discovery/assignment mechanism
>> mentioned by Francis.
>> 
> 
> 
> A similar approach was discussed in the DT: the MN could get a HA
> prefix via DNS and then perform DHAAD. However, we agreed that a pure
> DNS-based mechanism is better and does not have security concerns as
> DHAAD.
> 
> 
> 
>> 3. When load conditions change dramatically or the HA crashs, the
>> MN changes its HA using an HA-switch mechanism (this mechanism
>> could also provide an optional fine-grained load balancing between
>> HAs of different subnets).

Sorry Kilian, I forgot to say that when the current HA is overloaded or
crashes it has little chance to send the HA Switch message right?

> I would simplify the procedure a bit: get rid of DHAAD and use HA
> switch when a HA re-assignment is needed for any reason (e.g. load
> balancing).

Gerardo, a non-anycast yet-to-be-specified DHAAD together with MPD is
really simple bootstrapping, and in some cases even implemented.

Real simplification would be for the HA Switch message to be simplified
and just be used as a trigger that would make MN re-start the DHAAD
procedure to acquire the new HA.  For example, the HA Switch message
could be defined as just being extensible, and example of extension
could be list of HA Addresses that MN could use as hints; but still
recommend use DHAAD Req/Rep.  (DHAAD Reply contains a list of HAs.)

The HA Switch message could be used just like the 3775 Binding Refresh
Request message (sent by HA to MN to make it send a new BU).

It could also be used just like DHCPv6 "Reconfigure" message.

Alex


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



From mip6-bounces@ietf.org Tue Oct 25 09:32:34 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUOuo-0000Cw-CI; Tue, 25 Oct 2005 09:32:34 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUOun-0000Cp-EF
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 09:32:33 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA16955
	for <mip6@ietf.org>; Tue, 25 Oct 2005 09:32:19 -0400 (EDT)
Received: from dns1.tilab.com ([163.162.42.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUP7k-0002ga-BH
	for mip6@ietf.org; Tue, 25 Oct 2005 09:45:57 -0400
Received: from iowa2k01a.cselt.it ([163.162.242.201])
	by dns1.cselt.it (PMDF V6.0-025 #38895)
	with ESMTP id <0IOX0069349Y2J@dns1.cselt.it> for mip6@ietf.org; Tue,
	25 Oct 2005 15:32:22 +0200 (MEST)
Received: from EXC01B.cselt.it ([163.162.4.199]) by iowa2k01a.cselt.it with
	Microsoft SMTPSVC(6.0.3790.211); Tue, 25 Oct 2005 15:32:22 +0200
Date: Tue, 25 Oct 2005 15:32:22 +0200
From: Gerardo Giaretta <Gerardo.Giaretta@TILAB.COM>
Subject: RE: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
To: COMBES Jean-Michel RD-MAPS-ISS <jeanmichel.combes@francetelecom.com>
Message-id: <DA62A6E0CDD1B34A84557FF1AC850C57016E9CDC@EXC01B.cselt.it>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.3790.326
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: quoted-printable
Importance: normal
Priority: normal
Thread-Topic: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
thread-index: AcXYmAy19R9rZjd5Q6uwsLFw5TPmRAAFeDcgAAJ6ldAAAVGoIAAAcJUwACiY8KAAANR4wAAAykkA
Content-Class: urn:content-classes:message
X-OriginalArrivalTime: 25 Oct 2005 13:32:22.0564 (UTC)
	FILETIME=[87A74640:01C5D968]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024
Content-Transfer-Encoding: quoted-printable
Cc: mip6@ietf.org, Kilian Weniger <Kilian.Weniger@eu.panasonic.com>,
	Francis Dupont <Francis.Dupont@enst-bretagne.fr>,
	Petrescu Alexandru-AAP021 <alexandru.petrescu@motorola.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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

> > > > If in your opinion exposing HA addresses in DNS is an issue, in=20
> > > > integrated scenario a DHCP-based solution may be used (see the=20
> > > > integarted scenario draft).
> > > >=20
> > > > > For the moment, with these proposals, the MSP has not the=20
> > > > > possibility to manage its HA as he wants ...
> > > > >=20
> > > >=20
> > > > Why in DNS-based solution you think this is not possible?=20
> > >=20
> > > This is the MN that will choose the HA from the listed HA=20
> > in the DNS.
> > >=20
> >=20
> > Not entirely. The SRV specification, as Henrik mentioned=20
> > before in another thread, provides for priorities between=20
> > multiple Home Agents.
> > The list of HAs with priorities may be considered similar to=20
> > the list received by the MN via DHAAD. The MN will choose=20
> > based on these priorities.
>=20
> What does prevent the MN to contact the HA he wants? Nothing=20
> as far as I
> can see.
>=20

I agree. This is true also for DHAAD.=20
Besides the motivation why a MN will prevent another HA that is
theoretically more loaded, the operator may let the HA refuse the IPsec
SA setup during IKEv2 through its AAA infrastructure. But I agree this
is not a clean approach.

> >  Otherwise, in integrated scenario,=20
> > DHCP can be used. As mentioned before, if you need a very=20
> > strict control on the HA assignment by the operator, IMHO the=20
> > best way is to perform it during network access=20
> > authentication, but unfortunately this is not a general solution.
>=20
> Agree. But I think a operator must have the possibility to=20
> assign the HA
> in any cases.
>=20

DHCP-based solution seems to achieve this. Do you see any issue on that?

--Gerardo

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


Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia =
S.p.A.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
CONFIDENTIALITY NOTICE
This message and its attachments are addressed solely to the persons
above and may contain confidential information. If you have received
the message in error, be informed that any use of the content hereof
is prohibited. Please return it immediately to the sender and delete
the message. Should you have any questions, please send an e_mail to=20
MailAdmin@tilab.com. Thank you
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

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



From mip6-bounces@ietf.org Tue Oct 25 10:14:32 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUPZQ-0000oY-3h; Tue, 25 Oct 2005 10:14:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUPZO-0000oT-6y
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 10:14:30 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19609
	for <mip6@ietf.org>; Tue, 25 Oct 2005 10:14:15 -0400 (EDT)
Received: from cluster-d.mailcontrol.com ([217.69.20.190]
	helo=rly08d.srv.mailcontrol.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUPmL-0003x6-EG
	for mip6@ietf.org; Tue, 25 Oct 2005 10:27:54 -0400
Received: from hhe500-02.hbg.de.pan.eu (gate.eu.panasonic.com [194.173.20.12])
	by rly08d.srv.mailcontrol.com (MailControl) with SMTP id
	j9PEEJVa008189; Tue, 25 Oct 2005 15:14:19 +0100
Received: from eundadmi01.pan.eu(10.100.96.64) by hhe500-02.hbg.de.pan.eu via
	smtp id 7325_68dc6b1c_4562_11da_8ade_0030482aac25;
	Tue, 25 Oct 2005 16:19:52 +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 2005102516141677-73865 ;
	Tue, 25 Oct 2005 16:14:16 +0200 
Received: from localhost ([127.0.0.1]) by VPN-MRelay-01.PRDCG.Panasonic.de;
	Tue, 25 Oct 2005 16:16:26 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
MIME-Version: 1.0
Subject: RE: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
Thread-Topic: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
Thread-Index: AcXYqXbXIA/i8BXYScS1SYiWXuH9KAAAVacgAAMu7pAAH2NZIAALuRIgAAHKS9A=
To: "Gerardo Giaretta" <Gerardo.Giaretta@TILAB.COM>
Message-ID: <4D2F935F08D41A4C8866693F4F0D7C4F58E783@lan-ex-01.panasonic.de>
Date: Tue, 25 Oct 2005 16:14:12 +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-05-40-01 (www.mailcontrol.com) on 10.68.0.118
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976
Content-Transfer-Encoding: quoted-printable
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Hello Gerardo,=20

please see comments below...

...
> > I agree, RFC3775 DHAAD cannot provide load balancing=20
> between different
> > HAs on different subnets. Besides the minimal=20
> > pre-configuration, this is
> > an advantage of the DNS-based discovery. But I think=20
> anycast-based HA
> > discovery has advantages as well, e.g., it can support=20
> > fine-grained load
> > balancing and can decrease delay and signaling overhead during
> > bootstrapping. Maybe a combination might become a good=20
> solution, e.g.,
> >=20
> > 1. The MN gets an HA prefix with the DNS-based discovery=20
> mechanism (as
> > defined in bootstrapping solution). This minimizes the=20
> > pre-configuration
> > of the MN and can achieve (coarse-grained) load balancing=20
> > between HAs of
> > different subnets.
> >=20
> > 2. The MN starts anycast-based HA discovery (not necessarily=20
> > as defined
> > in RFC3775) using the discovered HA prefix to get the HA=20
> address. This
> > can support fine-grained load balancing between HAs on the=20
> > same link and
> > thus results in fast and efficient HA discovery (since subsequent HA
> > re-assignment for load balancing is not necessarily required). A
> > possible secure and efficient method could be the IKE=20
> Security Gateway
> > discovery/assignment mechanism mentioned by Francis.
> >=20
>=20
> A similar approach was discussed in the DT: the MN could get=20
> a HA prefix
> via DNS and then perform DHAAD. However, we agreed that a=20
> pure DNS-based
> mechanism is better and does not have security concerns as DHAAD.=20

O.k., I see. Can you recall the reasons, why a pure DNS-based mechanism
was considered better?=20
Any reasons apart from the ICMP and security issue?

Note that it would be possible to use an anycast-based discovery
mechanism=20
different from RFC3775 DHAAD, which is secure (e.g., the=20
IKE Security Gateway discovery/assignment mechanism mentioned by
Francis) and which doesn't=20
have the deployment (ICMP) issue.

>=20
>=20
> > 3. When load conditions change dramatically or the HA crashs, the MN
> > changes its HA using an HA-switch mechanism (this mechanism=20
> could also
> > provide an optional fine-grained load balancing between HAs=20
> > of different
> > subnets).
> >
>=20
> I would simplify the procedure a bit: get rid of DHAAD and=20
> use HA switch
> when a HA re-assignment is needed for any reason (e.g. load=20
> balancing).

O.k., I think it's just a matter of efficiency.=20
Without RFC3775 DHAAD, an additional HA-switch might be needed after
every bootstrapping.
I agree with Francis that the "real world" requirements for load
balancing must be known=20
to be able to make a good decision.

Regards,

Kilian


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



From mip6-bounces@ietf.org Tue Oct 25 10:20:11 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUPet-0001fI-AE; Tue, 25 Oct 2005 10:20:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUPem-0001eY-8M
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 10:20:09 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19842
	for <mip6@ietf.org>; Tue, 25 Oct 2005 10:19:49 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUPrj-000459-96
	for mip6@ietf.org; Tue, 25 Oct 2005 10:33:28 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id j9PEJSd18892; Tue, 25 Oct 2005 16:19:28 +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
	j9PEJRQA005655; Tue, 25 Oct 2005 16:19:27 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200510251419.j9PEJRQA005655@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: "Kilian Weniger" <Kilian.Weniger@eu.panasonic.com>
Subject: Re: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt 
In-reply-to: Your message of Tue, 25 Oct 2005 10:24:42 +0200.
	<4D2F935F08D41A4C8866693F4F0D7C4F58E6DA@lan-ex-01.panasonic.de> 
Date: Tue, 25 Oct 2005 16:19:27 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d
Cc: Gerardo Giaretta <Gerardo.Giaretta@tilab.com>, mip6@ietf.org,
	James Kempf <Kempf@docomolabs-usa.com>,
	Alexandru Petrescu <alexandru.petrescu@motorola.com>,
	COMBES Jean-Michel RD-MAPS-ISS <jeanmichel.combes@francetelecom.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   Yes, some co-ordination between HAs on the home link is required to
   provide dynamic load balancing. I think this can already be achieved
   with DHAAD as defined in RFC3775 by including load condition in the Home
   Agent Information Option in Ras. 
   
=> there is no such "load condition" defined in RFC 3775...

   I agree, RFC3775 DHAAD cannot provide load balancing between different
   HAs on different subnets. Besides the minimal pre-configuration, this is
   an advantage of the DNS-based discovery. But I think anycast-based HA
   discovery has advantages as well, e.g., it can support fine-grained load
   balancing and can decrease delay and signaling overhead during

=> DNS has caching so is more efficient in term of delays.
For the signaling DNS and ICMP are at the same order.

   bootstrapping. Maybe a combination might become a good solution, e.g.,
   
   1. The MN gets an HA prefix with the DNS-based discovery mechanism (as
   defined in bootstrapping solution). This minimizes the pre-configuration
   of the MN and can achieve (coarse-grained) load balancing between HAs of
   different subnets.
   
   2. The MN starts anycast-based HA discovery (not necessarily as defined

=> if you'd like to provide a two phase mechanism (which should not be
low delay and without signaling overhead :-) you should NOT use anycast
addresses as they have only drawbacks at this stage.

   in RFC3775) using the discovered HA prefix to get the HA address. This
   can support fine-grained load balancing between HAs on the same link and

=> you have to prove this 'load balancing' is not an illusion.

   thus results in fast and efficient HA discovery (since subsequent HA
   re-assignment for load balancing is not necessarily required). A
   possible secure and efficient method could be the IKE Security Gateway
   discovery/assignment mechanism mentioned by Francis.
   
=> IMHO assignment is better but it can't be proposed as a general
mechanism today.

   3. When load conditions change dramatically or the HA crashs, the MN
   changes its HA using an HA-switch mechanism (this mechanism could also
   provide an optional fine-grained load balancing between HAs of different
   subnets).
   
=> HA-switch doesn't work when the HA becomes unavailable, it works only
when the HA knows it will become unavailable or when another HA is far
better.

   > > So, why this HA - the one assigning the right HA - needs to 
   > > have HA functionality?
   > > 
   > It doesn't. It would be a light-weight "HA assigning entity" - but it
   > may very well be a logical entity collocated with the HA. 
   
   IMHO, a separate assignment entity would be possible, but it would
   probably increase signaling overhead and delay, because the MN has to
   establish another SA during bootstrapping (one to DNS, one to the
   assignment entity and finally one to the assigned HA). 
   
=> no, DNSSEC provides its own security and needs no SA, in particular
in this case.

Regards

Francis.Dupont@enst-bretagne.fr

PS: I believe that without concrete numbers showing a dynamic load
balancing at the bootstrapping phase is needed with its characterics,
in particular the time scale, we are looping. So again I propose
to close the 'load balancing' question.

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



From mip6-bounces@ietf.org Tue Oct 25 10:36:35 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUPul-0000Db-1L; Tue, 25 Oct 2005 10:36:35 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUPuj-0000DW-Hn
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 10:36:33 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20850
	for <mip6@ietf.org>; Tue, 25 Oct 2005 10:36:18 -0400 (EDT)
Received: from p-mail1.rd.francetelecom.com ([195.101.245.15])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUQ7f-0004b2-Vf
	for mip6@ietf.org; Tue, 25 Oct 2005 10:49:58 -0400
Received: from ftrdmel3.rd.francetelecom.fr ([10.193.117.155]) by
	ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 25 Oct 2005 16:36:28 +0200
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] draft-dupont-mip6-dhaadharmful-00.txt
Date: Tue, 25 Oct 2005 16:33:40 +0200
Message-ID: <D2AA6DF1AEE4404F8D983B68BAC97CD2022B9158@ftrdmel3.rd.francetelecom.fr>
Thread-Topic: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
Thread-Index: AcXYmAy19R9rZjd5Q6uwsLFw5TPmRAAFeDcgAAJ6ldAAAVGoIAAAcJUwACiY8KAAANR4wAAAykkAAAC7GwA=
From: "COMBES Jean-Michel RD-MAPS-ISS" <jeanmichel.combes@francetelecom.com>
To: "Gerardo Giaretta" <Gerardo.Giaretta@TILAB.COM>
X-OriginalArrivalTime: 25 Oct 2005 14:36:28.0689 (UTC)
	FILETIME=[7C1F6010:01C5D971]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5d7a7e767f20255fce80fa0b77fb2433
Content-Transfer-Encoding: quoted-printable
Cc: mip6@ietf.org, Kilian Weniger <Kilian.Weniger@eu.panasonic.com>,
	Francis Dupont <Francis.Dupont@enst-bretagne.fr>,
	Petrescu Alexandru-AAP021 <alexandru.petrescu@motorola.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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org


=20

> -----Original Message-----
> From: Gerardo Giaretta [mailto:Gerardo.Giaretta@TILAB.COM]=20
> Sent: Tuesday, October 25, 2005 3:32 PM
> To: COMBES Jean-Michel RD-MAPS-ISS
> Cc: mip6@ietf.org; Kilian Weniger; James Kempf; Narayanan=20
> Vidya-CVN065; Francis Dupont; Petrescu Alexandru-AAP021
> Subject: RE: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
>=20
> > > > > If in your opinion exposing HA addresses in DNS is an=20
> issue, in=20
> > > > > integrated scenario a DHCP-based solution may be used=20
> (see the=20
> > > > > integarted scenario draft).
> > > > >=20
> > > > > > For the moment, with these proposals, the MSP has not the=20
> > > > > > possibility to manage its HA as he wants ...
> > > > > >=20
> > > > >=20
> > > > > Why in DNS-based solution you think this is not possible?=20
> > > >=20
> > > > This is the MN that will choose the HA from the listed HA
> > > in the DNS.
> > > >=20
> > >=20
> > > Not entirely. The SRV specification, as Henrik mentioned=20
> before in=20
> > > another thread, provides for priorities between multiple Home=20
> > > Agents.
> > > The list of HAs with priorities may be considered similar to the=20
> > > list received by the MN via DHAAD. The MN will choose=20
> based on these=20
> > > priorities.
> >=20
> > What does prevent the MN to contact the HA he wants?=20
> Nothing as far as=20
> > I can see.
> >=20
>=20
> I agree. This is true also for DHAAD.

Yes if the MN knows all the HA but in the case where DHAAD only provide
one HA, it will be harder for the MN to choose another one.
=20
> Besides the motivation why a MN will prevent another HA that=20
> is theoretically more loaded, the operator may let the HA=20
> refuse the IPsec SA setup during IKEv2 through its AAA=20
> infrastructure. But I agree this is not a clean approach.

Agree.

>=20
> > >  Otherwise, in integrated scenario, DHCP can be used. As=20
> mentioned=20
> > > before, if you need a very strict control on the HA assignment by=20
> > > the operator, IMHO the best way is to perform it during network=20
> > > access authentication, but unfortunately this is not a general=20
> > > solution.
> >=20
> > Agree. But I think a operator must have the possibility to=20
> assign the=20
> > HA in any cases.
> >=20
>=20
> DHCP-based solution seems to achieve this. Do you see any=20
> issue on that?

Drawback with a DHCP based solution (in the split case): you have to
deploy a DHCP-Relay in all the potential Access Network because even if
the MN knows the DHCP server's unicast address, this one will refuse to
communicate directly with the MN (cf. RFC3315, section 22.12).

So, the possible solutions I see :=20
- the Vidya's proposal on an entity playing the role of a lightweight HA
and after doing HA switch
- the Alexandru's proposal on a pseudo anycast address with DHAAD
(modified to only send one HA address) to be able to secure it

JMC.


>=20
> --Gerardo
>=20
> > >=20
> > >=20
> > > --Gerardo
> >=20
> > Regards.
> >=20
> > JMC.
> >=20
> > France Telecom - R&D Division - MAPS/NSS  =20
> > Jean-Michel COMBES, Internet/Intranet Security
> > E-Mail: jeanmichel.combes@francetelecom.com
> > Phone: +33 (0)1 45 29 45 94
> > Fax: +33 (0)1 45 29 65 19
> > Mobile: +33 (0)6 07 29 30 16
> >=20
>=20
>=20
> Gruppo Telecom Italia - Direzione e coordinamento di Telecom=20
> Italia S.p.A.
>=20
> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> CONFIDENTIALITY NOTICE
> This message and its attachments are addressed solely to the persons
> above and may contain confidential information. If you have received
> the message in error, be informed that any use of the content hereof
> is prohibited. Please return it immediately to the sender and delete
> the message. Should you have any questions, please send an e_mail to=20
> MailAdmin@tilab.com. Thank you
> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=20

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



From mip6-bounces@ietf.org Tue Oct 25 11:03:45 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUQL3-000198-1x; Tue, 25 Oct 2005 11:03:45 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUQL1-00018e-CT
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 11:03:43 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25290
	for <mip6@ietf.org>; Tue, 25 Oct 2005 11:03:27 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUQXy-0006Nr-GP
	for mip6@ietf.org; Tue, 25 Oct 2005 11:17:07 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id j9PF3Ld23469; Tue, 25 Oct 2005 17:03:21 +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
	j9PF3MDI006998; Tue, 25 Oct 2005 17:03:22 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200510251503.j9PF3MDI006998@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Gerardo Giaretta <Gerardo.Giaretta@tilab.com>
Subject: Re: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt 
In-reply-to: Your message of Tue, 25 Oct 2005 14:47:46 +0200.
	<DA62A6E0CDD1B34A84557FF1AC850C57016E9CD8@EXC01B.cselt.it> 
Date: Tue, 25 Oct 2005 17:03:22 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: mip6@ietf.org, Kilian Weniger <Kilian.Weniger@eu.panasonic.com>,
	Petrescu Alexandru-AAP021 <alexandru.petrescu@motorola.com>,
	James Kempf <Kempf@docomolabs-usa.com>,
	COMBES Jean-Michel RD-MAPS-ISS <jeanmichel.combes@francetelecom.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   > This is the MN that will choose the HA from the listed HA in the DNS.
   
   Not entirely. The SRV specification, as Henrik mentioned before in
   another thread, provides for priorities between multiple Home Agents.
   The list of HAs with priorities may be considered similar to the list
   received by the MN via DHAAD. The MN will choose based on these
   priorities.

=> this is not fully accurate: the SRV mechanism uses weights too
(cf RFC 2782). It can be used for a static load balancing, something
the ICMP-based mechanism has not.

   As mentioned before, if you need a very strict control on the HA assignment
   by the operator, IMHO the best way is to perform it during network
   access authentication, but unfortunately this is not a general solution.
   
=> we agree about this point.

Thanks

Francis.Dupont@enst-bretagne.fr

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



From mip6-bounces@ietf.org Tue Oct 25 11:09:40 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUQQm-0005Cn-GA; Tue, 25 Oct 2005 11:09:40 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUQQk-0005Bk-I1
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 11:09:38 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27592
	for <mip6@ietf.org>; Tue, 25 Oct 2005 11:09:23 -0400 (EDT)
Received: from cluster-d.mailcontrol.com ([217.69.20.190]
	helo=rly26d.srv.mailcontrol.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUQdi-0007Fr-AT
	for mip6@ietf.org; Tue, 25 Oct 2005 11:23:03 -0400
Received: from hhe500-02.hbg.de.pan.eu (gate.eu.panasonic.com [194.173.20.12])
	by rly26d.srv.mailcontrol.com (MailControl) with SMTP id
	j9PF9Qbh025866; Tue, 25 Oct 2005 16:09:26 +0100
Received: from eundadmi01.pan.eu(10.100.96.64) by hhe500-02.hbg.de.pan.eu via
	smtp id 7250_1c5b3c66_456a_11da_9e2a_0030482aac25;
	Tue, 25 Oct 2005 17:15:00 +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 2005102517092345-77072 ;
	Tue, 25 Oct 2005 17:09:23 +0200 
Received: from localhost ([127.0.0.1]) by VPN-MRelay-01.PRDCG.Panasonic.de;
	Tue, 25 Oct 2005 17:11:31 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
MIME-Version: 1.0
Subject: RE: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt 
Thread-Topic: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt 
Thread-Index: AcXZbznF2fCJ1gL1SJm1cUgZ9ocsxwAALY2g
To: <Francis.Dupont@enst-bretagne.fr>
Message-ID: <4D2F935F08D41A4C8866693F4F0D7C4F58E79B@lan-ex-01.panasonic.de>
Date: Tue, 25 Oct 2005 17:09:17 +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-05-40-01 (www.mailcontrol.com) on 10.68.0.136
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d16ce744298aacf98517bc7c108bd198
Content-Transfer-Encoding: quoted-printable
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Hi Francis,=20

>    Yes, some co-ordination between HAs on the home link is required to
>    provide dynamic load balancing. I think this can already=20
> be achieved
>    with DHAAD as defined in RFC3775 by including load=20
> condition in the Home
>    Agent Information Option in Ras.=20
>   =20
> =3D> there is no such "load condition" defined in RFC 3775...

RFC3775 says:

	"...the sending home agent MAY
      dynamically set the Home Agent Preference value, for example
      basing it on the number of mobile nodes it is currently serving or
      on its remaining resources for serving additional mobile nodes;
	such dynamic settings are beyond the scope of this document."

Since the preference value is needed for ordering HAs on the *same link*
only,
my thinking was that an MSP could configure its HAs to use an arbitrary
function for=20
dynamic preference value calculation (e.g., based on load conditions).

>=20
>    I agree, RFC3775 DHAAD cannot provide load balancing=20
> between different
>    HAs on different subnets. Besides the minimal=20
> pre-configuration, this is
>    an advantage of the DNS-based discovery. But I think=20
> anycast-based HA
>    discovery has advantages as well, e.g., it can support=20
> fine-grained load
>    balancing and can decrease delay and signaling overhead during
>=20
> =3D> DNS has caching so is more efficient in term of delays.
> For the signaling DNS and ICMP are at the same order.

I think this is a misunderstanding. I didn't mean the signaling delay
for DNS/DHAAD request/reply. I agree that they should be in the same
order.
I meant that delay and signaling overhead can be reduced if
the HA discovery/assignment is intergrated in IKE exchange that is
needed for bootstrapping anyway, e.g., the anycast IKE_SA_INIT is
replied by=20
the HA with the lowest load (would require co-ordination between HAs)

>=20
>    bootstrapping. Maybe a combination might become a good=20
> solution, e.g.,
>   =20
>    1. The MN gets an HA prefix with the DNS-based discovery=20
> mechanism (as
>    defined in bootstrapping solution). This minimizes the=20
> pre-configuration
>    of the MN and can achieve (coarse-grained) load balancing=20
> between HAs of
>    different subnets.
>   =20
>    2. The MN starts anycast-based HA discovery (not=20
> necessarily as defined
>=20
> =3D> if you'd like to provide a two phase mechanism (which should not =
be
> low delay and without signaling overhead :-) you should NOT=20
> use anycast
> addresses as they have only drawbacks at this stage.

see above

>=20
>    in RFC3775) using the discovered HA prefix to get the HA=20
> address. This
>    can support fine-grained load balancing between HAs on the=20
> same link and
>=20
> =3D> you have to prove this 'load balancing' is not an illusion.

As I said in a previous mail, I agree with you that it depends on=20
the "real world" conditions/requirements on load balancing.

>=20
>    thus results in fast and efficient HA discovery (since=20
> subsequent HA
>    re-assignment for load balancing is not necessarily required). A
>    possible secure and efficient method could be the IKE=20
> Security Gateway
>    discovery/assignment mechanism mentioned by Francis.
>   =20
> =3D> IMHO assignment is better but it can't be proposed as a general
> mechanism today.
>=20
>    3. When load conditions change dramatically or the HA=20
> crashs, the MN
>    changes its HA using an HA-switch mechanism (this=20
> mechanism could also
>    provide an optional fine-grained load balancing between=20
> HAs of different
>    subnets).
>   =20
> =3D> HA-switch doesn't work when the HA becomes unavailable, it=20
> works only
> when the HA knows it will become unavailable or when another HA is far
> better.
>=20

I think Alex had the same comment. I think we had a different
understanding=20
of the term HA-switch. For me, the HA-switch mechanism includes
switching the HAs.
If the HA crashes, the MN has to detect the HA unavalability by itself
and=20
trigger the HA-switch mechanism (i.e., bootstrap with new HA).


>    > > So, why this HA - the one assigning the right HA - needs to=20
>    > > have HA functionality?
>    > >=20
>    > It doesn't. It would be a light-weight "HA assigning=20
> entity" - but it
>    > may very well be a logical entity collocated with the HA.=20
>   =20
>    IMHO, a separate assignment entity would be possible, but it would
>    probably increase signaling overhead and delay, because=20
> the MN has to
>    establish another SA during bootstrapping (one to DNS, one to the
>    assignment entity and finally one to the assigned HA).=20
>   =20
> =3D> no, DNSSEC provides its own security and needs no SA, in =
particular
> in this case.

You are right, but you still need an additional SA to the assignment
entity.

>=20
> Regards
>=20
> Francis.Dupont@enst-bretagne.fr
>=20
> PS: I believe that without concrete numbers showing a dynamic load
> balancing at the bootstrapping phase is needed with its characterics,
> in particular the time scale, we are looping. So again I propose
> to close the 'load balancing' question.

o.k.


Regards,

Kilian


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



From mip6-bounces@ietf.org Tue Oct 25 11:21:29 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUQcD-0007R7-OW; Tue, 25 Oct 2005 11:21:29 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUQcB-0007MW-Hf
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 11:21:27 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29130
	for <mip6@ietf.org>; Tue, 25 Oct 2005 11:21:12 -0400 (EDT)
Received: from p-mail2.rd.francetelecom.com ([195.101.245.16])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUQp9-0007tn-7c
	for mip6@ietf.org; Tue, 25 Oct 2005 11:34:52 -0400
Received: from ftrdmel3.rd.francetelecom.fr ([10.193.117.155]) by
	ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 25 Oct 2005 17:21:24 +0200
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] General comments/questions on MIPv6 bootstrapping
Date: Tue, 25 Oct 2005 17:20:09 +0200
Message-ID: <D2AA6DF1AEE4404F8D983B68BAC97CD2022B915A@ftrdmel3.rd.francetelecom.fr>
Thread-Topic: [Mip6] General comments/questions on MIPv6 bootstrapping
Thread-Index: AcXY2gvNGL3/4nIlRnOIjBMy/NvwzAAgqC8A
From: "COMBES Jean-Michel RD-MAPS-ISS" <jeanmichel.combes@francetelecom.com>
To: "Vijay Devarapalli" <vijayd@iprg.nokia.com>
X-OriginalArrivalTime: 25 Oct 2005 15:21:24.0111 (UTC)
	FILETIME=[C2B821F0:01C5D977]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a8a20a483a84f747e56475e290ee868e
Content-Transfer-Encoding: quoted-printable
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org


=20
=20

> -----Original Message-----
> From: Vijay Devarapalli [mailto:vijayd@iprg.nokia.com]=20
> Sent: Monday, October 24, 2005 10:32 PM
> To: COMBES Jean-Michel RD-MAPS-ISS
> Cc: mip6@ietf.org
> Subject: Re: [Mip6] General comments/questions on MIPv6 bootstrapping
>=20
> COMBES Jean-Michel RD-MAPS-ISS wrote:
> > Hi again,
> >=20
> > I was waiting for the proposal for the integrated scenario=20
> before to=20
> > do this email.
> >=20
> > I have 2 main comments/questions.
> >=20
> > The first one is regarding the fact that we have two (very)=20
> different=20
> > mechanisms for only one functionality (on one side=20
> DNS+IKEv2, on the=20
> > other side PANA+AAA+DCHP).
>=20
> there are 4 mains problems in MIP6 bootstrapping
>=20
> 1. home agent discovery
> 2. home address configuration
> 3. security association setup
> 4. DNS update for the MN
>=20
> draft-ietf-mip6-bootstrapping-split and
> draft-ietf-mip6-bootstrapping-integrated-dhc differ only on=20
> 1). the solutions for 2), 3) and 4) are the same in both drafts.

OK.

>=20
>  > So, personally, I am a little afraid how all
> > this will be managed in the user's terminal and in the=20
> MSP's network.
> > E.g., what will be the trigger in the terminal to know which is the=20
> > bootstrapping mechanism the terminal has to use?
>=20
> we have some text on this in the integrated draft. the mobile=20
> node could be configured to use either DHCPv6 or DNS for HA=20
> discovery. based on the configuration the MN uses a=20
> particular mechanism for HA discovery. in case both are=20
> available and the MN gets a response through a DHCP reply and=20
> DNS reply, the DHCP response has precedence. do you see a=20
> need for more text on this? let us know if there are any=20
> issues we havent considered.

Maybe, some text is needed to explain how and when the MN knows that it
cannot get the HA address with the DHCP-based mechanism and decides to
use finally DNS-based mechanism.

>=20
> > My second comment is regarding the interoperability with NEMO. I=20
> > believe that if MIPv6 is deployed soon, NEMO will be=20
> deployed at the=20
> > same time because the protocol is as mature as MIPv6. So I=20
> would like=20
> > to know if the bootstrapping mechanisms working for MIPv6,=20
> will work with NEMO too.
> > I would like to avoid to add new mechanisms again and so=20
> increase the=20
> > complexity in a deployement architecture.
>=20
> for NEMO, in addition to the 4 problems listed above, a=20
> mobile network prefix needs to be configured. for that there=20
> are two drafts being progressed in the NEMO WG.
>=20
> http://www.ietf.org/internet-drafts/draft-ietf-nemo-dhcpv6-pd-00.txt
> http://www.ietf.org/internet-drafts/draft-ietf-nemo-prefix-del
> egation-00.txt
>=20
> these drafts were written up even before the boostrapping=20
> work started in the MIP6 WG. is there anything else that=20
> needs to be addressed for NEMO bootstrapping?

IMO, the other one is to be able to do the difference between a MIPv6 HA
discovery and a NEMO HA discovery. But it seems that the DHCP-based and
the DNS-based mechanisms are easily adaptable to allow this.

>=20
> Vijay
>=20
>=20
>=20

Regards.=20

JMC.

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

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



From mip6-bounces@ietf.org Tue Oct 25 11:23:34 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUQeE-0008HP-Jd; Tue, 25 Oct 2005 11:23:34 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUQe5-0008E8-NP
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 11:23:32 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29234
	for <mip6@ietf.org>; Tue, 25 Oct 2005 11:23:10 -0400 (EDT)
Received: from ftpbox.mot.com ([129.188.136.101])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUQr3-0007xA-NE
	for mip6@ietf.org; Tue, 25 Oct 2005 11:36:50 -0400
Received: from az33exr01.mot.com (az33exr01.mot.com [10.64.251.231])
	by ftpbox.mot.com (Motorola/Ftpbox) with ESMTP id j9PFNE0n012392;
	Tue, 25 Oct 2005 08:23:14 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by az33exr01.mot.com (8.13.1/8.13.0) with ESMTP id j9PFZXlN020735;
	Tue, 25 Oct 2005 10:35:35 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id CDE9D865980; Tue, 25 Oct 2005 17:23:10 +0200 (CEST)
Message-ID: <435E4DDE.4060202@motorola.com>
Date: Tue, 25 Oct 2005 17:23:10 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
Subject: Re: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
References: <200510251503.j9PF3MDI006998@givry.rennes.enst-bretagne.fr>
In-Reply-To: <200510251503.j9PF3MDI006998@givry.rennes.enst-bretagne.fr>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Content-Transfer-Encoding: 7bit
Cc: Gerardo Giaretta <Gerardo.Giaretta@tilab.com>, mip6@ietf.org,
	Kilian Weniger <Kilian.Weniger@eu.panasonic.com>,
	James Kempf <Kempf@docomolabs-usa.com>,
	Petrescu Alexandru-AAP021 <alexandru.petrescu@motorola.com>,
	COMBES Jean-Michel RD-MAPS-ISS <jeanmichel.combes@francetelecom.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Francis Dupont wrote:
>  In your previous mail you wrote:
> 
>    > This is the MN that will choose the HA from the listed HA in the DNS.
>    
>    Not entirely. The SRV specification, as Henrik mentioned before in
>    another thread, provides for priorities between multiple Home Agents.
>    The list of HAs with priorities may be considered similar to the list
>    received by the MN via DHAAD. The MN will choose based on these
>    priorities.
> 
> => this is not fully accurate: the SRV mechanism uses weights too
> (cf RFC 2782). It can be used for a static load balancing, something
> the ICMP-based mechanism has not.

Well, although the DHAAD Reply only contains a list of HA addresses and
there's no 'weight' field associated to each address, the order these
addresses appear in the list should be interpreted as priority.

If that's not expressive enough, the DHAAD Reply or the HA Switch
messages could be extended to introduce 'weight' or 'priority' fields.
Remark that the H-bit RAs sent by HAs do contain such priority fields
for each HA address.

I think.

Alex

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



From mip6-bounces@ietf.org Tue Oct 25 11:35:41 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUQpx-0004s8-HQ; Tue, 25 Oct 2005 11:35:41 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUQpv-0004rZ-0i
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 11:35:39 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00012
	for <mip6@ietf.org>; Tue, 25 Oct 2005 11:35:23 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUR2t-0008It-H0
	for mip6@ietf.org; Tue, 25 Oct 2005 11:49:04 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id j9PFZDd25880; Tue, 25 Oct 2005 17:35: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
	j9PFZETS007152; Tue, 25 Oct 2005 17:35:14 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200510251535.j9PFZETS007152@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Alexandru Petrescu <alexandru.petrescu@motorola.com>
Subject: Re: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt 
In-reply-to: Your message of Tue, 25 Oct 2005 14:54:30 +0200.
	<435E2B06.8020206@motorola.com> 
Date: Tue, 25 Oct 2005 17:35:14 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   > => this is not enough different from the current DHAAD, i.e., in
   > place of the routing choice for the anycast group member, you propose
   > to elect a HA master. All the IPsec issues remain.
   
   I'm not sure I understand.  Isn't it possible for MN to have an SA with
   'all HAs for DHAAD' address?
   
=> two cases:
 - it is an anycast address so it can't be used as a source address, etc,
   and IPsec problems still apply.
 - it is not an anycast address, i.e., it is assigned to a box which can
   use it as a standard unicast address during a reasonable time.
   There is no more IPsec problems but a direct VRRP-like solution
   seems to be better as it solved all the problems.

   Remark that the HA that replies back to MN (1) is not necessarily the HA
   that is going to 'serve' the MN and (2) will use its own global unicast
   address as src of DHAAD Reply so IPsec would be fine.
   
=> no because to make IPsec happy the destination of the request and
the source of the reply must be the same. And I don't speak how
to setup the IPsec SA pairs...

   Again, this working assumes that all HAs have the same coherent list of
   HAs and priorities and that any HA may send back to MN the DHAAD Reply,
   and the HA that sends the Reply is not necessarily the HA that is first
   priority.  But the MN will use the HA Address that is the first priority
   in the received list of HA addresses.
   
=> we agree: current DHAAD design is not stupid, it has only two real
problems:
 - the DHAAD idea itself is in danger because HA assignment is better
 - the current mechanism has some operational issues, mainly its lack
   of reasonably easy security and the spurious but common ICMP filtering.
My draft is about the second but the first is more critical and drastic...

   > => for the election I propose to use the HA with the lowest IID...
   
   Well, it sounds as a good practical idea to me.

=> the idea is from OSPF and its Designated Router.

   An HA may use all the
   IIDs from all received H-bit RAs to build a common ordered list.  Or
   otherwise the HAs may use manually pre-configured priority information
   to be sent in the RAs.
   
=> as you've mentioned the priority is not used for replying to
requests.

   > If we'd like to make the non-anycast DHAAD compatible it is better
   > to use another well known address and to give it to the master.
   > But this is very similar to VRRP and there is already a VRRP/HA I-D
   > so I believe we should first look at this I-D which seems a good
   > complement to the HA-switch stuff (VRRP is transparent and should be
   > more efficient but can only switch the HA instance, not the whole HA,
   > IMHO both don't address the same problem).
   
   I have to check that.
   
=> VRRP is very fine for transparent failover (note that IMHO failover
is more important than load balancing and a good failover mechanism
should be as transparent as possible), and it is the only proposal
for this function (HA-switch can move the service, including to
another part of the infrastructure, for server maintenance for instance,
but can't help in case of server crash).

Regards

Francis.Dupont@enst-bretagne.fr

PS: in IPsec the only difficult thing to do with redunctant servers is
the anti-replay function but as we know it is not critical for MIPv6,
i.e., it always take times for the BU sequence number to wrap out
in standard conditions (increment by one and not a zillion of BUs
per seconds). So IMHO the VRRP-like idea should work for MIPv6
(BCEs) and IPsec (SAs).

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



From mip6-bounces@ietf.org Tue Oct 25 11:40:08 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUQuG-0005rM-SS; Tue, 25 Oct 2005 11:40:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUQuE-0005ph-EG
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 11:40:06 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00316
	for <mip6@ietf.org>; Tue, 25 Oct 2005 11:39:51 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUR7B-0008RQ-SA
	for mip6@ietf.org; Tue, 25 Oct 2005 11:53:31 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id j9PFdhd26426; Tue, 25 Oct 2005 17:39:44 +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
	j9PFdiX3007182; Tue, 25 Oct 2005 17:39:44 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200510251539.j9PFdiX3007182@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Alexandru Petrescu <alexandru.petrescu@motorola.com>
Subject: Re: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt 
In-reply-to: Your message of Tue, 25 Oct 2005 14:57:07 +0200.
	<435E2BA3.6030005@motorola.com> 
Date: Tue, 25 Oct 2005 17:39:44 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   I don't know how to make DNS resolve calls in the kernel

=> I know how (it is needed to implement good opportunistic encryption).

   and I'd like to keep all MIP6 IP mobility management in the kernel.

=> MIPL (Linux) and SHISA (BSD) have just done the opposite move.
   
BTW bootstrapping begins by the configuration so I don't believe you
really need to add a DNS resolver in your kernel...

Regards

Francis.Dupont@enst-bretagne.fr

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



From mip6-bounces@ietf.org Tue Oct 25 11:42:45 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUQwn-0006Vg-6B; Tue, 25 Oct 2005 11:42:45 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUQwi-0006RF-CC
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 11:42:42 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00526
	for <mip6@ietf.org>; Tue, 25 Oct 2005 11:42:24 -0400 (EDT)
Received: from rodin.i2r.a-star.edu.sg ([192.122.139.27])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUR9d-00005w-QE
	for mip6@ietf.org; Tue, 25 Oct 2005 11:56:05 -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 j9PFgPId015635
	for <mip6@ietf.org>; Tue, 25 Oct 2005 23:42:26 +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 j9PFgPAh015621for
	<mip6@ietf.org>; Tue, 25 Oct 2005 23:42:25 +0800 (SGT)
Received: from i2r.a-star.edu.sg (localhost [127.0.0.1])by 
	mailhost.lit.org.sg (Sun Java System Messaging Server 6.1 HotFix
	0.06(built
	Nov 11 2004)) with ESMTP id <0IOX001LJAAT6Q30@mailhost.lit.org.sg> 
	formip6@ietf.org; Tue, 25 Oct 2005 23:42:29 +0800 (SGT)
Received: from [192.122.139.152] by mailhost.lit.org.sg (mshttpd); Tue,25 
	Oct 2005 23:42:29 +0800
Date: Tue, 25 Oct 2005 23:42:29 +0800
From: Qiu Ying <qiuying@i2r.a-star.edu.sg>
To: jari.arkko@kolumbus.fi, mip6@ietf.org
Message-id: <67b996723cc2.435ec2e5@i2r.a-star.edu.sg>
MIME-version: 1.0
X-Mailer: Sun Java(tm) System Messenger Express 6.1 HotFix 0.06 (built Nov 
	112004)
Content-type: text/plain;
	charset=iso-8859-7
Content-language: en
Content-transfer-encoding: quoted-printable
Content-disposition: inline
X-Accept-Language: en
Priority: normal
X-imss-version: 2.033
X-imss-result: Passed
X-imss-scores: Clean:99.90000 C:2 M:6 S:5 R:5
X-imss-settings: Baseline:5 C:4 M:4 S:4 R:4 (1.5000 1.5000)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68ba2b07ef271dba6ee42a93832cfa4c
Content-Transfer-Encoding: quoted-printable
Cc: fanzhao828@gmail.com, rajeev@iprg.nokia.com
Subject: [Mip6] Re: Mip6] Review of
	draft-ietf-mip6-location-privacy-ps-00.txt
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Date=3A Tue=2C 25 Oct 2005 16=3A06=3A51 +0300
From=3A Jari Arkko =3Cjari=2Earkko=40kolumbus=2Efi=3E
Subject=3A =5BMip6=5D Review of draft-ietf-mip6-location-privacy-ps-00=2E=
txt
To=3A Mobile IPv6 Mailing List =3Cmip6=40ietf=2Eorg=3E

Hi=2C Jari
Please see my opinions inline =


=3EHi Rajeev=2C

=3EThanks for writing a draft on this important issue=2E
=3EHere are some initial comments=3A

=3E=3E   This problem is
=3E=3E   particularly applicable to Mobile IP where the Home Address on =
a
=3E=3E   visited network can reveal device roaming and=2C together with =
a
=3E=3E   user identifier (such as an NAI)=2C can reveal user roaming=2E =
 When
=3E=3E   roaming is revealed=2C it could lead to more targetted profilin=
g=2E  Even
=3E=3E
=3EThe part about user identifier comes somewhat out of the
=3Eblue here=2E Are we talking about user identifier and NAI
=3Eusage in general=3F This goes much=2C much beyond Mobile IPv6=2E
=3EOr are we talking about Mobile IPv6 use of NAIs=3F We=27d have
=3Eto look at the different usage types=2E One is within IKEv2/EAP
=3Eand one is in the auth protocol=2E They have very different
=3Eimplications=2E Also=2C NAI usage in network access (and also
=3Ein IKEv2) has typically a capability for pseudonym usage=2E

I guess Rajeev means that if one gets the IP address=2C it is can simply=
 translate the IP to an easily understanding identity=2E In fact=2C the =
draft focus on how to hide the telephone number (i=2Ee home addresses)=2C=
 not on how to translate a caller ID to a user name=2E

=3E=3E   Even
=3E=3E   when the binding between user identifier and the Home Address i=
s
=3E=3E   unavailable=2C freely available tools on the Internet can map t=
he Home
=3E=3E   Address to the owner of the Home Prefix=2C which can reveal tha=
t a user
=3E=3E   from a particular ISP has roamed=2E =

=3E=3E
=3EThere seems to be two different problems=2C one is being
=3Eable to see that someone (identified by a home address)
=3Eis moving with a specific pattern=2E The other problem is
=3Eidentifying that this someone is John Smith or that he is
=3Ea customer of Joe=27s Broadband=2E

It is true they are different issues=2E Let=A2s consider a scenario=2C i=
f an eavesdropper get an Ericsson IP address aa=3Abb=3Acc=3Axx and he do=
es not know who owns the IP=2E But the eavesdropper profiles the IP aa=3A=
bb=3Acc=3Axx appears in IETF62 and IETF63=2C now it appears again in IET=
F64 Vancouver=2E Then the eavesdropper bets the aa=3Abb=3Acc=3Axx belong=
s to Jari because Jari works for Ericsson and always attends IETF=2E =



=3E=3EIn addition=2C a user may not wish to reveal roaming to correspond=
ent(s)=2E
=3E=3E
=3EIt may be worthile to add some discussion about the
=3Edifferent participants=2E Presumably we can=27t avoid revealing
=3Einformation to our home network (or can we=3F)=2C =


In some special scenarios=2C such as MN always is the initiator and neve=
r a responder in the communications and HA would like to provide looser =
authentication=2C we can conceal MN=A2s information to the home network=2E=
 We will discuss this issue in mibopts=2C Vancover=2E  =


=3Ebut most
=3Edefinately want to avoid revealing information to outsiders=2C
=3Eand probably also in many cases to correspondent nodes=2E
=3EThere may also be different types of outsiders=2E Complete
=3Estrangers (e=2Eg=2E open 802=2E11) vs=2E local access network owners=2E=


To conceal the information to outsiders is much easier than conceal to C=
N because we much keep the continuous communication with CN=2E In order =
to hide the information from an on-looker=2C we can just break the relat=
ionship between CoA and HoA=2E

=3E(Some discussion of this appears later in the document=2C
=3Ebut I=27m not sure it provides a full discussion=2E)

=3E=3E   2=2E1=2E Disclosing the Care of Address
=3E=3E
=3E=3EThe fact that you do not need to reveal care-of address
=3E=3Eto correspondent nodes in Mobile IPv6 could perhaps be
=3E=3Ementioned already here=2E

=3E=3EThe assumption here is that the
=3E=3E   correspondent somehow knows the Home Address of the MN=2E For i=
nstance=2C
=3E=3E   a correspondent may obtain it from DNS=2C which may contain the=
 Home
=3E=3E   Address or the IP address of an agent to which the user identif=
ier
=3E=3E  =

=3EHmm=2E=2E=2E in Mobile IPv6 the home address is always known
=3Eto the correspondent=2E Can you clarify what you mean here=3F

If the correspondent is a public server=2C such as Yahoo=2C it does not =
care who are connecting to it=2E Hence the real HoA is not necessary to =
reveal to CN=2E Even in some case=2C the CN must know whom it is talking=
 with=2C the MN may not like to reveal its current location to the CN=2E=
  Therefore=2C we should consider how to hide the CoA to CN=2E

Regards
Qiu Ying



=3E=3EWhen equipped with an ability to inspect
=3E=3E   packets =60=60on the wire=27=27=2C an on-looker can determine t=
hat the MN has
=3E=3E   roamed and could possibly also determine that the user has roam=
ed=2E
=3E=3E
=3EI=27m not sure I understand teh MN-user distinction=2E
=3E
=3E--Jari




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



From mip6-bounces@ietf.org Tue Oct 25 11:51:51 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUR5b-0002At-4R; Tue, 25 Oct 2005 11:51:51 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUR5Y-0002Ao-QT
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 11:51:48 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01167
	for <mip6@ietf.org>; Tue, 25 Oct 2005 11:51:33 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EURIW-0000Ob-OA
	for mip6@ietf.org; Tue, 25 Oct 2005 12:05:14 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id j9PFpPd27563; Tue, 25 Oct 2005 17:51:25 +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
	j9PFpQXE007256; Tue, 25 Oct 2005 17:51:26 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200510251551.j9PFpQXE007256@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Alexandru Petrescu <alexandru.petrescu@motorola.com>
Subject: Re: [Mip6] load balancing and HA (re-)assignment 
In-reply-to: Your message of Tue, 25 Oct 2005 15:03:37 +0200.
	<435E2D29.8070509@motorola.com> 
Date: Tue, 25 Oct 2005 17:51:26 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   Before making it a WG item I'd look at whether bootstrapping with DHCPv6
   doesn't involve use of some pre-defined DHCPv6 message ("re-acquire"?)

=> the "reconfigure" message

   that is sent by server to client and that could be reused or extended to
   do the semantics of HA Switch message.
   
=> I believe it is the right answer when DHCPv6 is used (but I have
to read the last general bootstrapping I-D).

   Otherwise, the HA switch draft looks simple and rational and is
   something good to work on and advance probably quickly, IMHO.
   
=> we agree and the HA switch draft is already in the agenda of
the next meeting.

Thanks

Francis.Dupont@enst-bretagne.fr

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



From mip6-bounces@ietf.org Tue Oct 25 11:59:10 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EURCg-0005Fq-AH; Tue, 25 Oct 2005 11:59:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EURCe-0005Fl-DT
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 11:59:08 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01548
	for <mip6@ietf.org>; Tue, 25 Oct 2005 11:58:53 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EURPQ-0000Za-9F
	for mip6@ietf.org; Tue, 25 Oct 2005 12:12:21 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id j9PFwcd28467; Tue, 25 Oct 2005 17:58:38 +0200
Received: from givry.rennes.enst-bretagne.fr
	(localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.13.1/8.13.1) with ESMTP id
	j9PFwdoT007287; Tue, 25 Oct 2005 17:58:39 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200510251558.j9PFwdoT007287@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: "COMBES Jean-Michel RD-MAPS-ISS" <jeanmichel.combes@francetelecom.com>
Subject: Re: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt 
In-reply-to: Your message of Tue, 25 Oct 2005 15:02:32 +0200.
	<D2AA6DF1AEE4404F8D983B68BAC97CD2022B9153@ftrdmel3.rd.francetelecom.fr>
Date: Tue, 25 Oct 2005 17:58:39 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Cc: Gerardo Giaretta <Gerardo.Giaretta@tilab.com>, 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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   >    If you want to update the DNS servers frequently, DNSSEC cannot be
   >    usable:
   >    - for each update you will have to sign the zone
   >    - for each update you will have to transfer the signed zone to the
   >    secondary servers
   >    ...
   >    
   > => this is not true: you can use dynamic updates and you can 
   > put the critical RRs in a small zone in order to mitigate the 
   > main issue of dynamic updates with DNSSEC 
   
   Maybe, this is a solution but that will depend a lot on the number of HA
   the MSP will manage

=> I can't see why... dynamic update is a valid way to manage leaf zones.

   and you will still have to transfer the signed zone to the
   secondary servers.
   
=> the propagation of updates is a part of the dynamic update mechanism
(i.e., you have not to worry about).
   
   > (the private key 
   > must be online).
   
   Which private key?

=> the private part of the zone signing key pair.

   The one used to sign the zone or to secure the updates?

=> the first one.

   If this is the first one, the habit is to avoid to put it online (I know
   you know that :)
   
=> this is why DNSSEC and dynamic updates are not "friendly".

   >    So forget DNSSEC in such a case: result, no more security.
   >    
   > => I disagree: the only real problem with DNSSEC is it is not 
   > yet deployed.
   
   This is for me another issue (BTW, today, IKEv2 is not deployed too and
   most of the work in mip6 are on IKEv2).
   
=> this is because IKEv1 is so limited (cf my comments about the
bootstrapping with IKEv1 I-D). And DNSSEC is an infrastructure, something
which is always hard to deploy.

Regards

Francis.Dupont@enst-bretagne.fr

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



From mip6-bounces@ietf.org Tue Oct 25 12:18:19 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EURVC-0001ph-V4; Tue, 25 Oct 2005 12:18:18 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EURVB-0001pP-Um
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 12:18:18 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02505
	for <mip6@ietf.org>; Tue, 25 Oct 2005 12:18:02 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EURiA-00016c-1Y
	for mip6@ietf.org; Tue, 25 Oct 2005 12:31:43 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id j9PGHpd29967; Tue, 25 Oct 2005 18:17:51 +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
	j9PGHq9a007409; Tue, 25 Oct 2005 18:17:52 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200510251617.j9PGHq9a007409@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: "COMBES Jean-Michel RD-MAPS-ISS" <jeanmichel.combes@francetelecom.com>
Subject: Re: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt 
In-reply-to: Your message of Tue, 25 Oct 2005 15:20:43 +0200.
	<D2AA6DF1AEE4404F8D983B68BAC97CD2022B9155@ftrdmel3.rd.francetelecom.fr>
Date: Tue, 25 Oct 2005 18:17:52 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Cc: Gerardo Giaretta <Gerardo.Giaretta@tilab.com>, mip6@ietf.org,
	Kilian Weniger <Kilian.Weniger@eu.panasonic.com>,
	Petrescu Alexandru-AAP021 <alexandru.petrescu@motorola.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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   But I think a operator must have the possibility to assign the HA
   in any cases.
   
=> is it a request to provide a HA assignment mechanism in any cases?

And if the answer is yes do other operators agree?

And if again the answer is yes is it a request to put the highest
priority on the topics and to phase out DHAAD as soon as the WG
specifies a HA assignment mechanism covering the general case or some
mechanisms covering together every cases (if the previous fails)?

Thanks

Francis.Dupont@enst-bretagne.fr

PS: I'll try to involve the IPsec people into the HA assignment
in IKEv2 which IMHO is the missing part.

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



From mip6-bounces@ietf.org Tue Oct 25 12:21:55 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EURYh-0004yg-3R; Tue, 25 Oct 2005 12:21:55 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EURYf-0004yV-1D
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 12:21:53 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02763
	for <mip6@ietf.org>; Tue, 25 Oct 2005 12:21:37 -0400 (EDT)
Received: from p-mail2.rd.francetelecom.com ([195.101.245.16])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EURld-0001Fr-DR
	for mip6@ietf.org; Tue, 25 Oct 2005 12:35:18 -0400
Received: from ftrdmel3.rd.francetelecom.fr ([10.193.117.155]) by
	ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 25 Oct 2005 18:21:49 +0200
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] draft-dupont-mip6-dhaadharmful-00.txt 
Date: Tue, 25 Oct 2005 18:21:48 +0200
Message-ID: <D2AA6DF1AEE4404F8D983B68BAC97CD2022B915D@ftrdmel3.rd.francetelecom.fr>
Thread-Topic: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt 
Thread-Index: AcXZfQPtTONJPKfqTteIKpPjrLVTegAAFRtQ
From: "COMBES Jean-Michel RD-MAPS-ISS" <jeanmichel.combes@francetelecom.com>
To: <Francis.Dupont@enst-bretagne.fr>
X-OriginalArrivalTime: 25 Oct 2005 16:21:49.0221 (UTC)
	FILETIME=[33740550:01C5D980]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Content-Transfer-Encoding: quoted-printable
Cc: Gerardo Giaretta <Gerardo.Giaretta@tilab.com>, 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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org


> -----Original Message-----
> From: Francis.Dupont@enst-bretagne.fr=20
> [mailto:Francis.Dupont@enst-bretagne.fr]=20
> Sent: Tuesday, October 25, 2005 5:59 PM
> To: COMBES Jean-Michel RD-MAPS-ISS
> Cc: Gerardo Giaretta; Kilian Weniger; Alexandru Petrescu;=20
> mip6@ietf.org
> Subject: Re: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt=20
>=20
>  In your previous mail you wrote:
>=20
>    >    If you want to update the DNS servers frequently,=20
> DNSSEC cannot be
>    >    usable:
>    >    - for each update you will have to sign the zone
>    >    - for each update you will have to transfer the=20
> signed zone to the
>    >    secondary servers
>    >    ...
>    >   =20
>    > =3D> this is not true: you can use dynamic updates and you can=20
>    > put the critical RRs in a small zone in order to mitigate the=20
>    > main issue of dynamic updates with DNSSEC=20
>   =20
>    Maybe, this is a solution but that will depend a lot on=20
> the number of HA
>    the MSP will manage
>=20
> =3D> I can't see why... dynamic update is a valid way to manage=20
> leaf zones.

My concern was about the signature of the zone and so the size of this
zone.=20

>=20
>    and you will still have to transfer the signed zone to the
>    secondary servers.
>   =20
> =3D> the propagation of updates is a part of the dynamic update=20
> mechanism (i.e., you have not to worry about).

Ok .. but how long the propagation will take? We can have cache problems
too ...
I am not sure this is a good solution to modify DNS data frequently if
DNSSEC is used.

>   =20
>    > (the private key=20
>    > must be online).
>   =20
>    Which private key?
>=20
> =3D> the private part of the zone signing key pair.
>=20
>    The one used to sign the zone or to secure the updates?
>=20
> =3D> the first one.
>=20
>    If this is the first one, the habit is to avoid to put it=20
> online (I know
>    you know that :)
>   =20
> =3D> this is why DNSSEC and dynamic updates are not "friendly".
>=20
>    >    So forget DNSSEC in such a case: result, no more security.
>    >   =20
>    > =3D> I disagree: the only real problem with DNSSEC is it is not=20
>    > yet deployed.
>   =20
>    This is for me another issue (BTW, today, IKEv2 is not=20
> deployed too and
>    most of the work in mip6 are on IKEv2).
>   =20
> =3D> this is because IKEv1 is so limited (cf my comments about=20
> the bootstrapping with IKEv1 I-D). And DNSSEC is an=20
> infrastructure, something which is always hard to deploy.
>=20
> Regards
>=20
> Francis.Dupont@enst-bretagne.fr
>=20

Regards.

JMC.

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



From mip6-bounces@ietf.org Tue Oct 25 12:24:31 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EURbD-0006IK-Rn; Tue, 25 Oct 2005 12:24:31 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EURb8-0006IC-K8
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 12:24:30 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02938
	for <mip6@ietf.org>; Tue, 25 Oct 2005 12:24:11 -0400 (EDT)
Received: from motgate5.mot.com ([144.189.100.105])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EURo6-0001KJ-UX
	for mip6@ietf.org; Tue, 25 Oct 2005 12:37:52 -0400
Received: from az33exr01.mot.com (az33exr01.mot.com [10.64.251.231])
	by motgate5.mot.com (8.12.11/Motgate5) with ESMTP id j9PGWNdW022416;
	Tue, 25 Oct 2005 09:32:23 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by az33exr01.mot.com (8.13.1/8.13.0) with ESMTP id j9PGaSWS004187;
	Tue, 25 Oct 2005 11:36:30 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id 3C10D865980; Tue, 25 Oct 2005 18:24:05 +0200 (CEST)
Message-ID: <435E5C25.4030106@motorola.com>
Date: Tue, 25 Oct 2005 18:24:05 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
Subject: Re: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
References: <200510251535.j9PFZETS007152@givry.rennes.enst-bretagne.fr>
In-Reply-To: <200510251535.j9PFZETS007152@givry.rennes.enst-bretagne.fr>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 34d35111647d654d033d58d318c0d21a
Content-Transfer-Encoding: 7bit
Cc: James Kempf <Kempf@docomolabs-usa.com>, 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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Francis Dupont wrote:

>  In your previous mail you wrote:
> 
>    > => this is not enough different from the current DHAAD, i.e., in
>    > place of the routing choice for the anycast group member, you propose
>    > to elect a HA master. All the IPsec issues remain.
>    
>    I'm not sure I understand.  Isn't it possible for MN to have an SA with
>    'all HAs for DHAAD' address?
>    
> => two cases:
>  - it is an anycast address so it can't be used as a source address, etc,
>    and IPsec problems still apply.
>  - it is not an anycast address, i.e., it is assigned to a box which can
>    use it as a standard unicast address during a reasonable time.
>    There is no more IPsec problems but a direct VRRP-like solution
>    seems to be better as it solved all the problems.

I see, so a reserved address that is not anycast could help DHAAD.

>    Remark that the HA that replies back to MN (1) is not necessarily the HA
>    that is going to 'serve' the MN and (2) will use its own global unicast
>    address as src of DHAAD Reply so IPsec would be fine.
>    
> => no because to make IPsec happy the destination of the request and
> the source of the reply must be the same. And I don't speak how
> to setup the IPsec SA pairs...

Oh?  That's tough indeed.  So the src address of DHAAD Reply should be
that reserved non-anycast address then.

>    Again, this working assumes that all HAs have the same coherent list of
>    HAs and priorities and that any HA may send back to MN the DHAAD Reply,
>    and the HA that sends the Reply is not necessarily the HA that is first
>    priority.  But the MN will use the HA Address that is the first priority
>    in the received list of HA addresses.
>    
> => we agree: current DHAAD design is not stupid, it has only two real
> problems:
>  - the DHAAD idea itself is in danger because HA assignment is better

By "HA assignment" you mean HA Switch message and draft?  If yes, that
draft alone does not help for bootstrapping IMHO.  If DHAAD can be made
to work with non-anycast addresses then DHAAD+MPD is a good idea to do
bootstrapping simple (MPD is Mobile Prefix Discovery).

>  - the current mechanism has some operational issues, mainly its lack
>    of reasonably easy security and the spurious but common ICMP filtering.
> My draft is about the second but the first is more critical and drastic...

I don't see anything critical or drastic in HA assignment being proposed
as better than DHAAD.  It can complement DHAAD and work together with it
(HA Switch, DHAAD Req, DHAAD Reply).  I don't think HA Switch is about
to remove DHAAD altogether.

If DHAAD disappears altogether it's because it's bound to anycast
addresses and nobody cared to put on paper the non-anycast DHAAD that
works ok on at least two implementations.

>    > => for the election I propose to use the HA with the lowest IID...
>    
>    Well, it sounds as a good practical idea to me.
> 
> => the idea is from OSPF and its Designated Router.
> 
>    An HA may use all the
>    IIDs from all received H-bit RAs to build a common ordered list.  Or
>    otherwise the HAs may use manually pre-configured priority information
>    to be sent in the RAs.
>    
> => as you've mentioned the priority is not used for replying to
> requests.
> 
>    > If we'd like to make the non-anycast DHAAD compatible it is better
>    > to use another well known address and to give it to the master.
>    > But this is very similar to VRRP and there is already a VRRP/HA I-D
>    > so I believe we should first look at this I-D which seems a good
>    > complement to the HA-switch stuff (VRRP is transparent and should be
>    > more efficient but can only switch the HA instance, not the whole HA,
>    > IMHO both don't address the same problem).
>    
>    I have to check that.
>    
> => VRRP is very fine for transparent failover (note that IMHO failover
> is more important than load balancing and a good failover mechanism
> should be as transparent as possible), and it is the only proposal
> for this function (HA-switch can move the service, including to
> another part of the infrastructure, for server maintenance for instance,
> but can't help in case of server crash).

I think I agree, although my experience with VRRP is very limited.

Alex


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



From mip6-bounces@ietf.org Tue Oct 25 12:26:45 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EURdN-0007Dt-M7; Tue, 25 Oct 2005 12:26:45 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EURdM-0007Dg-71
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 12:26:44 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03086
	for <mip6@ietf.org>; Tue, 25 Oct 2005 12:26:28 -0400 (EDT)
Received: from mail.flarion.com ([63.103.94.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EURqK-0001Oc-RM
	for mip6@ietf.org; Tue, 25 Oct 2005 12:40:10 -0400
Received: from ftmailserver.flariontech.com ([10.10.1.140]) by
	mail.flarion.com with Microsoft SMTPSVC(5.0.2195.6713);
	Tue, 25 Oct 2005 12:26:32 -0400
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
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] I-D ACTION:draft-ietf-mip6-nemo-v4traversal-00.txt
Date: Tue, 25 Oct 2005 12:26:32 -0400
Message-ID: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCDA9@ftmailserver.flariontech.com>
Thread-Topic: [Mip6] I-D ACTION:draft-ietf-mip6-nemo-v4traversal-00.txt
Thread-Index: AcXYqHrD+axB1pKER8Kaep9QG6uovAA2EaLw
From: "Soliman, Hesham" <H.Soliman@flarion.com>
To: "Alexandru Petrescu" <alexandru.petrescu@motorola.com>
X-OriginalArrivalTime: 25 Oct 2005 16:26:33.0132 (UTC)
	FILETIME=[DCAD66C0:01C5D980]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Content-Transfer-Encoding: quoted-printable
Cc: mip6@ietf.org, Keiichi SHIMA <keiichi@iijlab.net>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org




 > > =3D> Absolutely. That's why the draft allows a node to use an IPv4
 > > home address whether it's in an IPv4 or an IPv6 network.
 >=20
 > And don't you think that there is a need for a node in a=20
 > moving network
 > to use IPv4 fixed address and the Mobile Router to do NEMO=20
 > and no MIP6?

=3D> And that scenario is also supported in the draft. What's your =
point?

Hesham

 >=20
 > Alex
 >=20

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D
This email may contain confidential and privileged material for the sole =
use
 of the intended recipient.  Any review or distribution by others is =
strictly
 prohibited.  If you are not the intended recipient please contact the =
sender
 and delete all copies.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D


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



From mip6-bounces@ietf.org Tue Oct 25 12:28:47 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EURfL-0000cH-Te; Tue, 25 Oct 2005 12:28:47 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EURfJ-0000aF-Tv
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 12:28:45 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03209
	for <mip6@ietf.org>; Tue, 25 Oct 2005 12:28:30 -0400 (EDT)
Received: from mail.flarion.com ([63.103.94.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EURsJ-0001St-IL
	for mip6@ietf.org; Tue, 25 Oct 2005 12:42:11 -0400
Received: from ftmailserver.flariontech.com ([10.10.1.140]) by
	mail.flarion.com with Microsoft SMTPSVC(5.0.2195.6713);
	Tue, 25 Oct 2005 12:28:36 -0400
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
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] I-D ACTION:draft-ietf-mip6-nemo-v4traversal-00.txt
Date: Tue, 25 Oct 2005 12:28:36 -0400
Message-ID: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCDAA@ftmailserver.flariontech.com>
Thread-Topic: [Mip6] I-D ACTION:draft-ietf-mip6-nemo-v4traversal-00.txt
Thread-Index: AcXYqNfl4mQbZ6/ITfGqrFG+vI0RugA2BoAA
From: "Soliman, Hesham" <H.Soliman@flarion.com>
To: "Alexandru Petrescu" <alexandru.petrescu@motorola.com>,
	"Keiichi SHIMA" <keiichi@iijlab.net>
X-OriginalArrivalTime: 25 Oct 2005 16:28:36.0944 (UTC)
	FILETIME=[26799D00:01C5D981]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Content-Transfer-Encoding: quoted-printable
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Alex,=20

 > Right, I also think the current draft still tries to address too many
 > scenarios.  I would keep in it only running MIP6 over a=20
 > v4-only access
 > network, with NAT traversal.  I would separate from it all=20
 > NEMO aspects
 > be it v4 or v6, I would separate also giving v4-home-address through
 > MIP6 through v4-only access network.

=3D> If this is a matter of taste then we can disagree on this
without discussion. But I prefer it to be a technical matter
that we can discuss. So, if there are reasons for your preference
above please state them so we can discuss them.

Hesham

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D
This email may contain confidential and privileged material for the sole =
use
 of the intended recipient.  Any review or distribution by others is =
strictly
 prohibited.  If you are not the intended recipient please contact the =
sender
 and delete all copies.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D


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



From mip6-bounces@ietf.org Tue Oct 25 12:31:45 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EURiD-0001Es-3C; Tue, 25 Oct 2005 12:31:45 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EURiB-0001Ei-0i
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 12:31:43 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03368
	for <mip6@ietf.org>; Tue, 25 Oct 2005 12:31:27 -0400 (EDT)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EURvA-0001Wl-LV
	for mip6@ietf.org; Tue, 25 Oct 2005 12:45:08 -0400
Received: from az33exr01.mot.com ([10.64.251.231])
	by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id j9PGhQNC018949;
	Tue, 25 Oct 2005 09:43:31 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by az33exr01.mot.com (8.13.1/8.13.0) with ESMTP id j9PGhrab009520;
	Tue, 25 Oct 2005 11:43:54 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id D4394865980; Tue, 25 Oct 2005 18:31:29 +0200 (CEST)
Message-ID: <435E5DE1.30708@motorola.com>
Date: Tue, 25 Oct 2005 18:31:29 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: "Soliman, Hesham" <H.Soliman@flarion.com>
Subject: Re: [Mip6] I-D ACTION:draft-ietf-mip6-nemo-v4traversal-00.txt
References: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCDA9@ftmailserver.flariontech.com>
In-Reply-To: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCDA9@ftmailserver.flariontech.com>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Content-Transfer-Encoding: 7bit
Cc: mip6@ietf.org, Keiichi SHIMA <keiichi@iijlab.net>,
	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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Soliman, Hesham wrote:
>>> => Absolutely. That's why the draft allows a node to use an IPv4 
>>> home address whether it's in an IPv4 or an IPv6 network.
>> 
>> And don't you think that there is a need for a node in a moving
>> network to use IPv4 fixed address and the Mobile Router to do NEMO
>>  and no MIP6?
> 
> => And that scenario is also supported in the draft. What's your
> point?

Hesham, my point above clarified: there is no need for this draft to
address that scenario.

Alex


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



From mip6-bounces@ietf.org Tue Oct 25 12:32:28 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EURiu-0001OO-JJ; Tue, 25 Oct 2005 12:32:28 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EURis-0001Nf-Pj
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 12:32:27 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03413
	for <mip6@ietf.org>; Tue, 25 Oct 2005 12:32:11 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EURvq-0001Xh-W2
	for mip6@ietf.org; Tue, 25 Oct 2005 12:45:52 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id j9PGW4H31680; Tue, 25 Oct 2005 18:32:04 +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
	j9PGW4MC007527; Tue, 25 Oct 2005 18:32:04 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200510251632.j9PGW4MC007527@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Alexandru Petrescu <alexandru.petrescu@motorola.com>
Subject: Re: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt 
In-reply-to: Your message of Tue, 25 Oct 2005 15:27:48 +0200.
	<435E32D4.7000702@motorola.com> 
Date: Tue, 25 Oct 2005 18:32:04 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Cc: Gerardo Giaretta <Gerardo.Giaretta@tilab.com>, mip6@ietf.org,
	Kilian Weniger <Kilian.Weniger@eu.panasonic.com>,
	James Kempf <Kempf@docomolabs-usa.com>,
	COMBES Jean-Michel RD-MAPS-ISS <jeanmichel.combes@francetelecom.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   Real simplification would be for the HA Switch message to be simplified
   and just be used as a trigger that would make MN re-start the DHAAD
   procedure to acquire the new HA.

=> it doesn't need to be simplified, I quote here the I-D:

   # of Addresses
 
     A 16-bit unsigned integer indicating the number of IPv6 home agent
     addresses in the message.  If set to zero, the mobile node MUST
     perform home agent discovery.

So it can already do what you want... (another reason to like it? :-)

Regards

Francis.Dupont@enst-bretagne.fr

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



From mip6-bounces@ietf.org Tue Oct 25 12:34:08 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EURkW-0001xI-7W; Tue, 25 Oct 2005 12:34:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EURkV-0001x3-9E
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 12:34:07 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03516
	for <mip6@ietf.org>; Tue, 25 Oct 2005 12:33:51 -0400 (EDT)
Received: from mail.flarion.com ([63.103.94.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EURxU-0001bS-II
	for mip6@ietf.org; Tue, 25 Oct 2005 12:47:32 -0400
Received: from ftmailserver.flariontech.com ([10.10.1.140]) by
	mail.flarion.com with Microsoft SMTPSVC(5.0.2195.6713);
	Tue, 25 Oct 2005 12:33:56 -0400
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
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] I-D ACTION:draft-ietf-mip6-nemo-v4traversal-00.txt
Date: Tue, 25 Oct 2005 12:33:56 -0400
Message-ID: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCDAB@ftmailserver.flariontech.com>
Thread-Topic: [Mip6] I-D ACTION:draft-ietf-mip6-nemo-v4traversal-00.txt
Thread-Index: AcXZgZUY4uQOlK6IQ8ynWP9ri+QSTgAABXjA
From: "Soliman, Hesham" <H.Soliman@flarion.com>
To: "Alexandru Petrescu" <alexandru.petrescu@motorola.com>
X-OriginalArrivalTime: 25 Oct 2005 16:33:56.0757 (UTC)
	FILETIME=[E5193450:01C5D981]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Content-Transfer-Encoding: quoted-printable
Cc: mip6@ietf.org, Keiichi SHIMA <keiichi@iijlab.net>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org



 > > =3D> And that scenario is also supported in the draft. What's your
 > > point?
 >=20
 > Hesham, my point above clarified: there is no need for this draft to
 > address that scenario.

=3D> Ah, well, the point of the draft is to introduce IPv4 extensions
to MIPv6 so that it can support IPv4 CoAs/HoAs. So I don't see
why we should distinguish an HoA used by a host from an HoA used
by a router. The title of draft is clear that this is an effort
for hosts and routers.

Hesham

 >=20
 > Alex
 >=20
 >=20

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D
This email may contain confidential and privileged material for the sole =
use
 of the intended recipient.  Any review or distribution by others is =
strictly
 prohibited.  If you are not the intended recipient please contact the =
sender
 and delete all copies.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D


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



From mip6-bounces@ietf.org Tue Oct 25 12:38:14 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EURoU-0002hY-7z; Tue, 25 Oct 2005 12:38:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EURoS-0002gc-HL
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 12:38:12 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03834
	for <mip6@ietf.org>; Tue, 25 Oct 2005 12:37:56 -0400 (EDT)
Received: from motgate4.mot.com ([144.189.100.102])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUS1Q-0001lq-SE
	for mip6@ietf.org; Tue, 25 Oct 2005 12:51:38 -0400
Received: from az33exr01.mot.com (az33exr01.mot.com [10.64.251.231])
	by motgate4.mot.com (8.12.11/Motgate4) with ESMTP id j9PGlH92004785;
	Tue, 25 Oct 2005 09:47:22 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by az33exr01.mot.com (8.13.1/8.13.0) with ESMTP id j9PGoJDR015102;
	Tue, 25 Oct 2005 11:50:20 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id 4D5F9865980; Tue, 25 Oct 2005 18:37:56 +0200 (CEST)
Message-ID: <435E5F64.1050805@motorola.com>
Date: Tue, 25 Oct 2005 18:37:56 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: "Soliman, Hesham" <H.Soliman@flarion.com>
Subject: Re: [Mip6] I-D ACTION:draft-ietf-mip6-nemo-v4traversal-00.txt
References: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCDAA@ftmailserver.flariontech.com>
In-Reply-To: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCDAA@ftmailserver.flariontech.com>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Content-Transfer-Encoding: 7bit
Cc: mip6@ietf.org, Keiichi SHIMA <keiichi@iijlab.net>,
	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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Soliman, Hesham wrote:

> Alex,
> 
>> Right, I also think the current draft still tries to address too 
>> many scenarios.  I would keep in it only running MIP6 over a 
>> v4-only access network, with NAT traversal.  I would separate from
>>  it all NEMO aspects be it v4 or v6, I would separate also giving 
>> v4-home-address through MIP6 through v4-only access network.
> 
> => If this is a matter of taste then we can disagree on this without
>  discussion. But I prefer it to be a technical matter that we can 
> discuss.

Absolutely, so do I.  So I will use the efficiency argument.  The
efficiency argument is used throughout the document to motivate some of
the decisions.  I'll use the same argument if you agree.

> So, if there are reasons for your preference above please state them 
> so we can discuss them.

Yes, the technical reason for that draft to not address giving v4 access
to LFNs by an IPv6 MR connecting to a v4-only network is the following.

A MIP4 MR connecting to a v4 access network can give IPv4 access
naturally to its IPv4 LFNs.  An MR that would use MIP6 (instead of MIP4)
to give IPv4 access to LFNs when MR connected to v4-only access network
is inefficient.  The inefficiency comes from v4-in-v6-in-v4
encapsulation, whereas if MIP4 were used in this case it would have been
v4-in-v4.

Would you discuss?

Alex

> 
> Hesham
> 
> =========================================================== This 
> email may contain confidential and privileged material for the sole 
> use of the intended recipient.  Any review or distribution by others
>  is strictly prohibited.  If you are not the intended recipient
> please contact the sender and delete all copies. 
> ===========================================================


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



From mip6-bounces@ietf.org Tue Oct 25 12:40:24 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EURqa-0003HH-Sf; Tue, 25 Oct 2005 12:40:24 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EURqY-0003Gy-3w
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 12:40:22 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03990
	for <mip6@ietf.org>; Tue, 25 Oct 2005 12:40:06 -0400 (EDT)
Received: from motgate7.mot.com ([129.188.136.7])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUS3X-0001qH-C8
	for mip6@ietf.org; Tue, 25 Oct 2005 12:53:47 -0400
Received: from az33exr01.mot.com ([10.64.251.231])
	by motgate7.mot.com (8.12.11/Motgate7) with ESMTP id j9PH38W1011198;
	Tue, 25 Oct 2005 10:03:08 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by az33exr01.mot.com (8.13.1/8.13.0) with ESMTP id j9PGqZb3016815;
	Tue, 25 Oct 2005 11:52:36 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id D5D06865980; Tue, 25 Oct 2005 18:40:11 +0200 (CEST)
Message-ID: <435E5FEB.3070700@motorola.com>
Date: Tue, 25 Oct 2005 18:40:11 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
Subject: Re: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
References: <200510251632.j9PGW4MC007527@givry.rennes.enst-bretagne.fr>
In-Reply-To: <200510251632.j9PGW4MC007527@givry.rennes.enst-bretagne.fr>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Content-Transfer-Encoding: 7bit
Cc: Gerardo Giaretta <Gerardo.Giaretta@tilab.com>, mip6@ietf.org,
	Kilian Weniger <Kilian.Weniger@eu.panasonic.com>,
	Alexandru Petrescu <alexandru.petrescu@motorola.com>,
	James Kempf <Kempf@docomolabs-usa.com>,
	COMBES Jean-Michel RD-MAPS-ISS <jeanmichel.combes@francetelecom.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Francis Dupont wrote:

>  In your previous mail you wrote:
> 
>    Real simplification would be for the HA Switch message to be simplified
>    and just be used as a trigger that would make MN re-start the DHAAD
>    procedure to acquire the new HA.
> 
> => it doesn't need to be simplified, I quote here the I-D:
> 
>    # of Addresses
>  
>      A 16-bit unsigned integer indicating the number of IPv6 home agent
>      addresses in the message.  If set to zero, the mobile node MUST
>      perform home agent discovery.
> 
> So it can already do what you want... (another reason to like it? :-)

That's good, thanks for pointing it.  Is that "home agent discovery" DHAAD?

Alex

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



From mip6-bounces@ietf.org Tue Oct 25 12:45:14 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EURvF-0005uz-TT; Tue, 25 Oct 2005 12:45:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EURvC-0005sX-D0
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 12:45:10 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04348
	for <mip6@ietf.org>; Tue, 25 Oct 2005 12:44:56 -0400 (EDT)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUS8B-00021N-1x
	for mip6@ietf.org; Tue, 25 Oct 2005 12:58:36 -0400
Received: from az33exr01.mot.com ([10.64.251.231])
	by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id j9PGv13s021664;
	Tue, 25 Oct 2005 09:57:02 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by az33exr01.mot.com (8.13.1/8.13.0) with ESMTP id j9PGvS1v020809;
	Tue, 25 Oct 2005 11:57:29 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id 124D2865980; Tue, 25 Oct 2005 18:45:05 +0200 (CEST)
Message-ID: <435E6110.9050709@motorola.com>
Date: Tue, 25 Oct 2005 18:45:04 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: "Soliman, Hesham" <H.Soliman@flarion.com>
Subject: Re: [Mip6] I-D ACTION:draft-ietf-mip6-nemo-v4traversal-00.txt
References: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCDAB@ftmailserver.flariontech.com>
In-Reply-To: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCDAB@ftmailserver.flariontech.com>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Content-Transfer-Encoding: 7bit
Cc: mip6@ietf.org, Keiichi SHIMA <keiichi@iijlab.net>,
	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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Soliman, Hesham wrote:

> 
>>> => And that scenario is also supported in the draft. What's your
>>>  point?
>> 
>> Hesham, my point above clarified: there is no need for this draft 
>> to address that scenario.
> 
> => Ah, well, the point of the draft is to introduce IPv4 extensions 
> to MIPv6 so that it can support IPv4 CoAs/HoAs.

I do not agree with the MR obtaining a v4 CoA and then sending a BU with
a v4 Mobile Network Prefix.

It is natural for MR to obtain a v4 CoA and then send a MIP4 RegReq
containing a v4 Mobile Network Prefix (and not a v6 BU).  Would you
agree with this?

> So I don't see why we should distinguish an HoA used by a host from 
> an HoA used by a router.

Normally I agree, but here we talk IP version numbers.

> The title of draft is clear that this is an effort for hosts and
> routers.

Well, ok with title as long as it does not try to give v4 access to LFNs
with v6 MR connected to a v4 network.

The title is fine with me if it addresses giving v6 addresses to LFNs
(not v4 addresses) by a MIP6 MR connecting to a v4-only network.

Alex


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



From mip6-bounces@ietf.org Tue Oct 25 12:55:51 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUS5X-0003Ju-1e; Tue, 25 Oct 2005 12:55:51 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUS5V-0003JL-Fl
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 12:55:49 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04865
	for <mip6@ietf.org>; Tue, 25 Oct 2005 12:55:35 -0400 (EDT)
Received: from mail.flarion.com ([63.103.94.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUSIU-0002J2-8r
	for mip6@ietf.org; Tue, 25 Oct 2005 13:09:15 -0400
Received: from ftmailserver.flariontech.com ([10.10.1.140]) by
	mail.flarion.com with Microsoft SMTPSVC(5.0.2195.6713);
	Tue, 25 Oct 2005 12:55:29 -0400
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
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] I-D ACTION:draft-ietf-mip6-nemo-v4traversal-00.txt
Date: Tue, 25 Oct 2005 12:55:29 -0400
Message-ID: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCDAC@ftmailserver.flariontech.com>
Thread-Topic: [Mip6] I-D ACTION:draft-ietf-mip6-nemo-v4traversal-00.txt
Thread-Index: AcXZg3WpsaWSMFJdQy+0HLDMbGJ7ywAARazg
From: "Soliman, Hesham" <H.Soliman@flarion.com>
To: "Alexandru Petrescu" <alexandru.petrescu@motorola.com>
X-OriginalArrivalTime: 25 Oct 2005 16:55:29.0929 (UTC)
	FILETIME=[E7E39790:01C5D984]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Content-Transfer-Encoding: quoted-printable
Cc: mip6@ietf.org, Keiichi SHIMA <keiichi@iijlab.net>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org



 > > =3D> Ah, well, the point of the draft is to introduce IPv4=20
 > extensions=20
 > > to MIPv6 so that it can support IPv4 CoAs/HoAs.
 >=20
 > I do not agree with the MR obtaining a v4 CoA and then=20
 > sending a BU with
 > a v4 Mobile Network Prefix.

=3D> Why?

 >=20
 > It is natural for MR to obtain a v4 CoA and then send a MIP4 RegReq
 > containing a v4 Mobile Network Prefix (and not a v6 BU).  Would you
 > agree with this?

=3D> Please read the problem statement where it is clearly stated that
running MIPv4 and MIPv6 simultaneously in inefficient and prevent a node
from having mobility across different networks supporting different
IP versions.

 >=20
 > > So I don't see why we should distinguish an HoA used by a=20
 > host from=20
 > > an HoA used by a router.
 >=20
 > Normally I agree, but here we talk IP version numbers.

=3D> The whole point of this work is to make MIP work without
being tied to "version numbers"..

 >=20
 > > The title of draft is clear that this is an effort for hosts and
 > > routers.
 >=20
 > Well, ok with title as long as it does not try to give v4=20
 > access to LFNs
 > with v6 MR connected to a v4 network.

=3D> Technical reasons please. It's really difficult to discuss issues
this way.

Hesham

 >=20
 > The title is fine with me if it addresses giving v6 addresses to LFNs
 > (not v4 addresses) by a MIP6 MR connecting to a v4-only network.
 >=20
 > Alex
 >=20
 >=20

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D
This email may contain confidential and privileged material for the sole =
use
 of the intended recipient.  Any review or distribution by others is =
strictly
 prohibited.  If you are not the intended recipient please contact the =
sender
 and delete all copies.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D


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



From mip6-bounces@ietf.org Tue Oct 25 12:56:18 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUS5y-0003P7-NX; Tue, 25 Oct 2005 12:56:18 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUS5w-0003P0-En
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 12:56:16 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04891
	for <mip6@ietf.org>; Tue, 25 Oct 2005 12:56:02 -0400 (EDT)
Received: from coliposte.enst-bretagne.fr ([192.108.115.12])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUSIu-0002Jv-MC
	for mip6@ietf.org; Tue, 25 Oct 2005 13:09:42 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by coliposte.enst-bretagne.fr (8.12.10/8.12.10/2004.10.03) with ESMTP
	id j9PGtrhR017670; Tue, 25 Oct 2005 18:55:53 +0200
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by coliposte.enst-bretagne.fr (8.12.10/8.12.10/2004.09.01) with ESMTP
	id j9PGt3ls017495; Tue, 25 Oct 2005 18:55:03 +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
	j9PGt4Ta007676; Tue, 25 Oct 2005 18:55:04 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200510251655.j9PGt4Ta007676@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Gerardo Giaretta <Gerardo.Giaretta@tilab.com>
Subject: Re: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt 
In-reply-to: Your message of Tue, 25 Oct 2005 15:32:22 +0200.
	<DA62A6E0CDD1B34A84557FF1AC850C57016E9CDC@EXC01B.cselt.it> 
Date: Tue, 25 Oct 2005 18:55:04 +0200
X-Virus-Scanned: amavisd-new at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: mip6@ietf.org, Kilian Weniger <Kilian.Weniger@eu.panasonic.com>,
	Petrescu Alexandru-AAP021 <alexandru.petrescu@motorola.com>,
	James Kempf <Kempf@docomolabs-usa.com>,
	COMBES Jean-Michel RD-MAPS-ISS <jeanmichel.combes@francetelecom.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   Besides the motivation why a MN will prevent another HA that is
   theoretically more loaded, the operator may let the HA refuse the IPsec
   SA setup during IKEv2 through its AAA infrastructure. But I agree this
   is not a clean approach.
   
=> it is not so bad but:
 - it is not so easy to implement (another IKE/MIPv6 interaction,
   the MIPv6 codes I know try other HAs when BUs fail)
 - with a timeout it is not efficient, with an ICMP message it is
   a security hole (trivial DoS)
 - any secured mechanism will take time and participate to the load

   DHCP-based solution seems to achieve this. Do you see any issue on that?
   
=> I know well DHCPv6 and I don't believe it is the right tool for
this job. I'll comment the general bootstrapping draft
(draft-ietf-mip6-bootstrapping-integrated-dhc-00.txt isn't it?)
because there are many ways to use DHCPv6, including just transmitting
AAA stuff to the MN...

Regards

Francis.Dupont@enst-bretagne.fr

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



From mip6-bounces@ietf.org Tue Oct 25 13:17:07 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUSQ6-0003oL-TP; Tue, 25 Oct 2005 13:17:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUSQ2-0003nn-Kz
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 13:17:04 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06764
	for <mip6@ietf.org>; Tue, 25 Oct 2005 13:16:48 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUSd1-0003AC-8A
	for mip6@ietf.org; Tue, 25 Oct 2005 13:30:28 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id j9PHGdi11888; Tue, 25 Oct 2005 19:16:39 +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
	j9PHGe8o007841; Tue, 25 Oct 2005 19:16:40 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200510251716.j9PHGe8o007841@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: "COMBES Jean-Michel RD-MAPS-ISS" <jeanmichel.combes@francetelecom.com>
Subject: Re: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt 
In-reply-to: Your message of Tue, 25 Oct 2005 16:33:40 +0200.
	<D2AA6DF1AEE4404F8D983B68BAC97CD2022B9158@ftrdmel3.rd.francetelecom.fr>
Date: Tue, 25 Oct 2005 19:16:40 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Cc: Gerardo Giaretta <Gerardo.Giaretta@tilab.com>, mip6@ietf.org,
	Kilian Weniger <Kilian.Weniger@eu.panasonic.com>,
	Petrescu Alexandru-AAP021 <alexandru.petrescu@motorola.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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   Drawback with a DHCP based solution (in the split case): you have to
   deploy a DHCP-Relay in all the potential Access Network because even if
   the MN knows the DHCP server's unicast address, this one will refuse to
   communicate directly with the MN (cf. RFC3315, section 22.12).
   
=> I confirm: there must be a DHCP relay on each link (a real IPv6
link with link-local addresses and multicast). After relays can talk
with the server through multicast routers, routers or a relay chain.

This should be in the applicability statement for the DHCP-based solution.

Regards

Francis.Dupont@enst-bretagne.fr

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



From mip6-bounces@ietf.org Tue Oct 25 13:20:25 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUSTJ-0006S6-1h; Tue, 25 Oct 2005 13:20:25 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUSTG-0006PS-I1
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 13:20:22 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06919
	for <mip6@ietf.org>; Tue, 25 Oct 2005 13:20:08 -0400 (EDT)
Received: from p-mail2.rd.francetelecom.com ([195.101.245.16])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUSgF-0003FH-8D
	for mip6@ietf.org; Tue, 25 Oct 2005 13:33:48 -0400
Received: from ftrdmel3.rd.francetelecom.fr ([10.193.117.155]) by
	ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.211); 
	Tue, 25 Oct 2005 19:20:19 +0200
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] draft-dupont-mip6-dhaadharmful-00.txt 
Date: Tue, 25 Oct 2005 19:20:15 +0200
Message-ID: <D2AA6DF1AEE4404F8D983B68BAC97CD2022B9160@ftrdmel3.rd.francetelecom.fr>
Thread-Topic: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt 
Thread-Index: AcXZf689CBaoBopgRj+sgvvqt+pVmQAA6N6A
From: "COMBES Jean-Michel RD-MAPS-ISS" <jeanmichel.combes@francetelecom.com>
To: <Francis.Dupont@enst-bretagne.fr>
X-OriginalArrivalTime: 25 Oct 2005 17:20:19.0442 (UTC)
	FILETIME=[5FB53D20:01C5D988]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Content-Transfer-Encoding: quoted-printable
Cc: Gerardo Giaretta <Gerardo.Giaretta@tilab.com>, mip6@ietf.org,
	Kilian Weniger <Kilian.Weniger@eu.panasonic.com>,
	Petrescu Alexandru-AAP021 <alexandru.petrescu@motorola.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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org



> -----Original Message-----
> From: Francis.Dupont@enst-bretagne.fr=20
> [mailto:Francis.Dupont@enst-bretagne.fr]=20
> Sent: Tuesday, October 25, 2005 6:18 PM
> To: COMBES Jean-Michel RD-MAPS-ISS
> Cc: Gerardo Giaretta; mip6@ietf.org; Kilian Weniger; James=20
> Kempf; Narayanan Vidya-CVN065; Petrescu Alexandru-AAP021
> Subject: Re: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt=20
>=20
>  In your previous mail you wrote:
>=20
>    But I think a operator must have the possibility to assign the HA
>    in any cases.
>   =20
> =3D> is it a request to provide a HA assignment mechanism in any =
cases?

Yes.

>=20
> And if the answer is yes do other operators agree?
>=20
> And if again the answer is yes is it a request to put the=20
> highest priority on the topics and to phase out DHAAD as soon=20
> as the WG specifies a HA assignment mechanism covering the=20
> general case or some mechanisms covering together every cases=20
> (if the previous fails)?
>=20
> Thanks
>=20
> Francis.Dupont@enst-bretagne.fr
>=20
> PS: I'll try to involve the IPsec people into the HA=20
> assignment in IKEv2 which IMHO is the missing part.
>=20

Regards.

JMC.

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



From mip6-bounces@ietf.org Tue Oct 25 13:20:29 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUSTN-0006Ui-TK; Tue, 25 Oct 2005 13:20:29 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUSTK-0006Th-B6
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 13:20:27 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06931
	for <mip6@ietf.org>; Tue, 25 Oct 2005 13:20:12 -0400 (EDT)
Received: from motgate7.mot.com ([129.188.136.7])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUSgK-0003Fk-AB
	for mip6@ietf.org; Tue, 25 Oct 2005 13:33:52 -0400
Received: from az33exr03.mot.com ([10.64.251.233])
	by motgate7.mot.com (8.12.11/Motgate7) with ESMTP id j9PHhHJU023717;
	Tue, 25 Oct 2005 10:43:17 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by az33exr03.mot.com (8.13.1/8.13.0) with ESMTP id j9PHTb7s013977;
	Tue, 25 Oct 2005 12:29:38 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id 2CE11865980; Tue, 25 Oct 2005 19:20:21 +0200 (CEST)
Message-ID: <435E6955.7080505@motorola.com>
Date: Tue, 25 Oct 2005 19:20:21 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: "Soliman, Hesham" <H.Soliman@flarion.com>
Subject: Re: [Mip6] I-D ACTION:draft-ietf-mip6-nemo-v4traversal-00.txt
References: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCDAC@ftmailserver.flariontech.com>
In-Reply-To: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCDAC@ftmailserver.flariontech.com>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac
Content-Transfer-Encoding: 7bit
Cc: mip6@ietf.org, Keiichi SHIMA <keiichi@iijlab.net>,
	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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Hesham, for the discussion sake I strive to answer your technical questions.

Soliman, Hesham wrote:
>>> => Ah, well, the point of the draft is to introduce IPv4
>> extensions
>>> to MIPv6 so that it can support IPv4 CoAs/HoAs.
>> 
>> I do not agree with the MR obtaining a v4 CoA and then sending a BU
>>  with a v4 Mobile Network Prefix.
> 
> => Why?

Because MIP4 could do it better.  Using MIP4 instead of MIP6 in this
particular scenario would avoid going through v6, so a level of
encapsulation eliminated.

Don't you think so?

>> It is natural for MR to obtain a v4 CoA and then send a MIP4 RegReq
>>  containing a v4 Mobile Network Prefix (and not a v6 BU).  Would 
>> you agree with this?
> 
> => Please read the problem statement where it is clearly stated that
>  running MIPv4 and MIPv6 simultaneously in inefficient

I've read it.  Two technical reasons raised my interest: (1) MIP6 is
better than MIP4 because has DHAAD and RO, (2) sending BU and RegReq
each time is not efficient.

For (1): DHAAD is not clear in terms of spec, and RO is not yet widely
deployed.

For (2): it's not necessary to send a BU and a RegReq simultaneously
when the MN changes only its v4 CoA and keeps its v6 CoA.  From a
particular implementation experience one may see that the v4 address
changes and the v6 address may be kept the same.

Are there other technical reasons in the draft?

> [running MIP4 and MIP6 simultaneously] prevent a node from having 
> mobility across different networks supporting different IP versions.

This can not be true, tell me.  Having both MIP4 and MIP6 in a same
node can not prevent mobility across different networks supporting
different IP versions.  On the contrary - it helps.  Because it would
use MIP4 when connecting to a v4 network and MIP6 when connecting to a
v6 network.

If the application needs to have a permanent v4/v6 Home Address even if
connected to the other IP version network then yes, one could use
enhancements.  But even in that case I have remarks I'd keep separate.

>>> So I don't see why we should distinguish an HoA used by a host 
>>> from an HoA used by a router.
>> 
>> Normally I agree, but here we talk IP version numbers.
> 
> => The whole point of this work is to make MIP work without being 
> tied to "version numbers"..

That's a good goal.  But more precise would be to make MIP6 (not MIP)
beeing tied to "version numbers".

>>> The title of draft is clear that this is an effort for hosts and
>>>  routers.
>> 
>> Well, ok with title as long as it does not try to give v4 access to
>>  LFNs with v6 MR connected to a v4 network.
> 
> => Technical reasons please. It's really difficult to discuss issues
>  this way.

Technical reasons above.

Would you care to provide technical counter-reasons?

Alex

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



From mip6-bounces@ietf.org Tue Oct 25 13:38:30 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUSko-0004Lf-2Z; Tue, 25 Oct 2005 13:38:30 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUSkm-0004Io-5Y
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 13:38:28 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07807
	for <mip6@ietf.org>; Tue, 25 Oct 2005 13:38:14 -0400 (EDT)
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUSxm-0003k2-3N
	for mip6@ietf.org; Tue, 25 Oct 2005 13:51:54 -0400
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id j9PH5Gt05158
	for <mip6@ietf.org>; Tue, 25 Oct 2005 10:05:16 -0700
X-mProtect: <200510251705> Nokia Silicon Valley Messaging Protection
Received: from mvdhcp14172.americas.nokia.com (172.18.141.72,
	claiming to be "[127.0.0.1]")
	by darkstar.iprg.nokia.com smtpdIAFlCG; Tue, 25 Oct 2005 10:05:15 PDT
Message-ID: <435E6D7D.5030007@iprg.nokia.com>
Date: Tue, 25 Oct 2005 10:38:05 -0700
From: Rajeev Koodli <rajeev@iprg.nokia.com>
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: mip6@ietf.org
Content-Type: multipart/mixed; boundary="------------010303030100030608000907"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a8a20a483a84f747e56475e290ee868e
Subject: [Mip6] [Fwd: [Mobopts] MIP6 Route Optimization Enhancements
	Document]
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

This is a multi-part message in MIME format.
--------------010303030100030608000907
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit


--------------010303030100030608000907
Content-Type: message/rfc822;
	name="[Mobopts] MIP6 Route Optimization Enhancements Document"
Content-Disposition: inline;
	filename="[Mobopts] MIP6 Route Optimization Enhancements Document"

Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id KAA27679;
	Tue, 25 Oct 2005 10:36:21 -0700 (PDT)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id j9PH3KD04091;
	Tue, 25 Oct 2005 10:03:20 -0700
Received: from mailrelay.iprg.nokia.com (205.226.0.201)
	by darkstar.iprg.nokia.com smtpdfX7ybp; Tue, 25 Oct 2005 10:03:19 PDT
X-Scanned: Tue, 25 Oct 2005 10:35:57 -0700 Nokia Message Protector V1.3.35
	2005042208 - RELEASE
Received: (from root@localhost)
	by mailrelay.iprg.nokia.com (8.12.9/8.12.9) id j9PHZvYW000498;
	Tue, 25 Oct 2005 10:35:57 -0700
X-pstn-settings: 5 (1.50000:1.50000) p:5 r:4 m:4 c:5
X-pstn-version: pase:2.23
X-pstn-levels: s:99.90000/99.90000 p:95.91080 r:95.91080 m:97.02319 c:98.76780
X-pstn-address: from <mobopts-bounces@irtf.org>
X-pstn-spam: N
Received: from megatron.ietf.org (132.151.6.71)
	by mailrelay.iprg.nokia.com 00MnJ2D8; Tue, 25 Oct 2005 10:35:55 PDT
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUSgL-00011P-Ul; Tue, 25 Oct 2005 13:33:54 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUSgG-00010c-TR
	for mobopts@megatron.ietf.org; Tue, 25 Oct 2005 13:33:49 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07510
	for <mobopts@irtf.org>; Tue, 25 Oct 2005 13:33:35 -0400 (EDT)
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUStF-0003ZL-Et
	for mobopts@irtf.org; Tue, 25 Oct 2005 13:47:15 -0400
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id j9PH0ZY01463;
	Tue, 25 Oct 2005 10:00:35 -0700
X-mProtect: <200510251700> Nokia Silicon Valley Messaging Protection
Received: from mvdhcp14172.americas.nokia.com (172.18.141.72,
	claiming to be "[127.0.0.1]")
	by darkstar.iprg.nokia.com smtpdnVLVDI; Tue, 25 Oct 2005 10:00:33 PDT
Message-ID: <435E6C62.1070407@iprg.nokia.com>
Date: Tue, 25 Oct 2005 10:33:22 -0700
From: Rajeev Koodli <rajeev@IPRG.nokia.com>
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "mobopts@irtf.org" <mobopts@irtf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
X-Spam-Score: 2.4 (++)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Cc: William Arbaugh <waa@cs.umd.edu>
Subject: [Mobopts] MIP6 Route Optimization Enhancements Document
X-BeenThere: mobopts@irtf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IP Mobility Optimizations <mobopts.irtf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mobopts>,
	<mailto:mobopts-request@irtf.org?subject=unsubscribe>
List-Post: <mailto:mobopts@irtf.org>
List-Help: <mailto:mobopts-request@irtf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mobopts>,
	<mailto:mobopts-request@irtf.org?subject=subscribe>
Sender: mobopts-bounces@irtf.org
Errors-To: mobopts-bounces@irtf.org
Content-Transfer-Encoding: 7bit


Hello folks,

draft-irtf-mobopts-ro-enhancements-04.txt has undergone a very good 
review by the members of the RG as well as the MIP6 WG. It is time to 
issue the Last Call for comments before we progress this document 
towards an RFC.

Please provide your comments on the list by November 7, 2005 so that we 
can discuss them during the meeting in Vancouver.

Thanks,

-Rajeev




_______________________________________________
Mobopts mailing list
Mobopts@irtf.org
https://www1.ietf.org/mailman/listinfo/mobopts

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

--------------010303030100030608000907--





From mip6-bounces@ietf.org Tue Oct 25 13:38:57 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUSlF-0004cs-S7; Tue, 25 Oct 2005 13:38:57 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUSlE-0004cf-6P
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 13:38:56 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07837
	for <mip6@ietf.org>; Tue, 25 Oct 2005 13:38:42 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUSyD-0003l2-7g
	for mip6@ietf.org; Tue, 25 Oct 2005 13:52:22 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id j9PHcci13882; Tue, 25 Oct 2005 19:38:38 +0200
Received: from givry.rennes.enst-bretagne.fr
	(localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.13.1/8.13.1) with ESMTP id
	j9PHcdQa008026; Tue, 25 Oct 2005 19:38:39 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200510251738.j9PHcdQa008026@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: "Kilian Weniger" <Kilian.Weniger@eu.panasonic.com>
Subject: Re: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt 
In-reply-to: Your message of Tue, 25 Oct 2005 17:09:17 +0200.
	<4D2F935F08D41A4C8866693F4F0D7C4F58E79B@lan-ex-01.panasonic.de> 
Date: Tue, 25 Oct 2005 19:38:39 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   > => there is no such "load condition" defined in RFC 3775...
   
   RFC3775 says:
   
   	"...the sending home agent MAY
         dynamically set the Home Agent Preference value, for example
         basing it on the number of mobile nodes it is currently serving or
         on its remaining resources for serving additional mobile nodes;
   	such dynamic settings are beyond the scope of this document."
   
=> there is a large difference between a parameter which MAY be derived
from load condition and a load condition field in a message.
   
   > => DNS has caching so is more efficient in term of delays.
   > For the signaling DNS and ICMP are at the same order.
   
   I think this is a misunderstanding. I didn't mean the signaling delay
   for DNS/DHAAD request/reply. I agree that they should be in the same
   order.
   I meant that delay and signaling overhead can be reduced if
   the HA discovery/assignment is intergrated in IKE exchange that is
   needed for bootstrapping anyway, e.g., the anycast IKE_SA_INIT is
   replied by 
   the HA with the lowest load (would require co-ordination between HAs)
   
=> so you compare with a potential mechanism about we have no details...
I still believe caching will always give an advantage to DNS, i.e.,
the DNS cache should be closer than the HA in the common case.

   I think Alex had the same comment. I think we had a different
   understanding of the term HA-switch.

=> for me HA-switch is the mechanism described in
draft-haley-mip6-ha-switch-00.txt. Obviously a HA can't crash
and after send HA-switch messages.

   trigger the HA-switch mechanism (i.e., bootstrap with new HA).

=> this is HA reselection.
   
Regards

Francis.Dupont@enst-bretagne.fr

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



From mip6-bounces@ietf.org Tue Oct 25 13:40:24 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUSme-0004s6-B3; Tue, 25 Oct 2005 13:40:24 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUSmb-0004rR-IN
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 13:40:21 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07969
	for <mip6@ietf.org>; Tue, 25 Oct 2005 13:40:07 -0400 (EDT)
Received: from ftpbox.mot.com ([129.188.136.101])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUSzY-0003oN-8V
	for mip6@ietf.org; Tue, 25 Oct 2005 13:53:47 -0400
Received: from az33exr01.mot.com (az33exr01.mot.com [10.64.251.231])
	by ftpbox.mot.com (Motorola/Ftpbox) with ESMTP id j9PHe70n002893;
	Tue, 25 Oct 2005 10:40:07 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by az33exr01.mot.com (8.13.1/8.13.0) with ESMTP id j9PHqSna026565;
	Tue, 25 Oct 2005 12:52:29 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id A6667865980; Tue, 25 Oct 2005 19:40:04 +0200 (CEST)
Message-ID: <435E6DF4.3070403@motorola.com>
Date: Tue, 25 Oct 2005 19:40:04 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: Henrik Levkowetz <henrik@levkowetz.com>
Subject: Re: [Mip6] More comments on draft-ietf-mip6-nemo-v4traversal-00.txt
References: <435CF254.6050508@motorola.com> <435D0459.8050605@levkowetz.com>
	<435D250B.6040507@motorola.com>
	<435D32A5.4010400@levkowetz.com> <435DF9F1.60203@motorola.com>
	<435DFD3F.4020309@levkowetz.com>
In-Reply-To: <435DFD3F.4020309@levkowetz.com>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Content-Transfer-Encoding: 7bit
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Henrik Levkowetz wrote:
> Hi Alexandru,
> 
> on 2005-10-25 11:25 Alexandru Petrescu said the following:
> 
>> Henrik Levkowetz wrote:
> 
> [...]
> 
>>> No.  Here we seem to radically disagree.  If my MN/MR has only
>>> IPv4 connectivity, the only way I can reach the HA is through a
>>> public IPv4 address.
>> 
>> It sounds logical that when needs MN to reach the de-capsulating
>> Gateway that latter needs a v4 address.  Remark though that that
>> Gateway that strips out the the inner IPv6 packet of its UDPv4
>> header does not need to be the IPv6 HA.  Which gives the
>> possibility for the HA to be a box different than the Gateway, and
>> thus the HA to run IPv6 exclusively.  It is a good thing to have
>> the v6 HA separated from the de-capsulating Gateway.
>> 
>> If we require the HA to run both IPv4 and IPv6 it means that the HA
>> can not be placed in an IPv6-exclusively network.
> 
> 
> Yes.  Which is why we write that the HA must be reachable through an
> IPv4 address, instead of writing that the HA must have and IPv4 
> address on an interface.

The draft also says that the MN sends packets to the HA IPv4 address in
section 4.2 "Mobile node operation":
> - The destination address in the IPv4 header is the home agent's IPv4
> address.

What I am trying to suggest is that a v6 HA does not need to be
connected directly on a v6 network.  Moreover, there exist v6-only
infrastructure networks and they're supposed to grow, and the v6 HAs may
very well live there.

Alex

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



From mip6-bounces@ietf.org Tue Oct 25 13:48:52 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUSuq-0007fh-Kh; Tue, 25 Oct 2005 13:48:52 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUSuo-0007fO-Px
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 13:48:50 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08581
	for <mip6@ietf.org>; Tue, 25 Oct 2005 13:48:36 -0400 (EDT)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUT7p-00047A-0v
	for mip6@ietf.org; Tue, 25 Oct 2005 14:02:17 -0400
Received: from il06exr02.mot.com (il06exr02.mot.com [129.188.137.132])
	by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id j9PI0ik4002507
	for <mip6@ietf.org>; Tue, 25 Oct 2005 11:00:44 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by il06exr02.mot.com (8.13.1/8.13.0) with ESMTP id j9PHvSmD025437
	for <mip6@ietf.org>; Tue, 25 Oct 2005 12:57:28 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP id 9A57C865980
	for <mip6@ietf.org>; Tue, 25 Oct 2005 19:48:48 +0200 (CEST)
Message-ID: <435E7000.6030500@motorola.com>
Date: Tue, 25 Oct 2005 19:48:48 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: Mobile IPv6 Mailing List <mip6@ietf.org>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Content-Transfer-Encoding: 7bit
Subject: [Mip6] Security Considerations section of
	draft-ietf-mip6-nemo-v4traversal-00.txt
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Hello again to authors of draft-ietf-mip6-nemo-v4traversal-00.txt,

Please let me deviate the discussion to the Security Considerations
section.  It is very good that the draft has this section contributed
from the start since the security aspects are important.

It currently describes a method by which the v6 HA may use the inherent
security established with the v6 Home Address to deduce that the v4 HoA
contained in the BU is securely communicated.

While the method may make sense, maybe some flaws are still possible.

For example, it may be possible that an IPv6 attacker MN that has good
credentials with its HA (verifiable by IPsec with respect to its v6 HoA)
abuses the v4 address of another legitimate MN of same v6 HA.  The
attacker may include the legitimate's MN v4 address in its BU.  Do you
think this would not be possible?

Another example is with the NAT traversal scheme.  The current text
describes that if two IPv4 addresses in a certain packet don't match
then the HA advises the MN to use a certain Refresh Time (with the NAT
detection option).  So I think it is possible for an attacker MN to fake
the IPv4 address of another MN, such that the legitimate MN receives NAT
Detection Options although there's no NAT in place.  Do you think this
would not be possible?

Alex


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



From mip6-bounces@ietf.org Tue Oct 25 13:54:54 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUT0g-0008EI-Qj; Tue, 25 Oct 2005 13:54:54 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUT0e-0008E9-I6
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 13:54:52 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08900
	for <mip6@ietf.org>; Tue, 25 Oct 2005 13:54:38 -0400 (EDT)
Received: from motgate3.mot.com ([144.189.100.103])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUTDe-0004Gz-NM
	for mip6@ietf.org; Tue, 25 Oct 2005 14:08:19 -0400
Received: from az33exr03.mot.com (az33exr03.mot.com [10.64.251.233])
	by motgate3.mot.com (8.12.11/Motgate3) with ESMTP id j9PIAXXj029607;
	Tue, 25 Oct 2005 11:10:37 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by az33exr03.mot.com (8.13.1/8.13.0) with ESMTP id j9PI3x6N005913;
	Tue, 25 Oct 2005 13:04:00 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id E3706865980; Tue, 25 Oct 2005 19:54:43 +0200 (CEST)
Message-ID: <435E7163.3030004@motorola.com>
Date: Tue, 25 Oct 2005 19:54:43 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: Alexandru Petrescu <alexandru.petrescu@motorola.com>
Subject: Re: [Mip6] More comments on draft-ietf-mip6-nemo-v4traversal-00.txt
References: <435CF254.6050508@motorola.com> <435D0459.8050605@levkowetz.com>
	<435D250B.6040507@motorola.com>
	<435D32A5.4010400@levkowetz.com> <435DF9F1.60203@motorola.com>
	<435DFD3F.4020309@levkowetz.com> <435E6DF4.3070403@motorola.com>
In-Reply-To: <435E6DF4.3070403@motorola.com>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Content-Transfer-Encoding: 7bit
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>,
	Henrik Levkowetz <henrik@levkowetz.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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Alexandru Petrescu wrote:

> Henrik Levkowetz wrote:
> 
>> Hi Alexandru,
>> 
>> on 2005-10-25 11:25 Alexandru Petrescu said the following:
>> 
>> 
>>> Henrik Levkowetz wrote:
>> 
>> [...]
>> 
>> 
>>>> No.  Here we seem to radically disagree.  If my MN/MR has only 
>>>> IPv4 connectivity, the only way I can reach the HA is through a
>>>>  public IPv4 address.
>>> 
>>> It sounds logical that when needs MN to reach the de-capsulating 
>>> Gateway that latter needs a v4 address.  Remark though that that 
>>> Gateway that strips out the the inner IPv6 packet of its UDPv4 
>>> header does not need to be the IPv6 HA.  Which gives the 
>>> possibility for the HA to be a box different than the Gateway,
>>> and thus the HA to run IPv6 exclusively.  It is a good thing to
>>> have the v6 HA separated from the de-capsulating Gateway.
>>> 
>>> If we require the HA to run both IPv4 and IPv6 it means that the
>>> HA can not be placed in an IPv6-exclusively network.
>> 
>> 
>> Yes.  Which is why we write that the HA must be reachable through
>> an IPv4 address, instead of writing that the HA must have and IPv4
>>  address on an interface.
> 
> 
> The draft also says that the MN sends packets to the HA IPv4 address
> in section 4.2 "Mobile node operation":
> 
>> - The destination address in the IPv4 header is the home agent's
>> IPv4 address.
> 
> 
> What I am trying to suggest is that a v6 HA does not need to be 
> connected directly on a v6 network.
                          ^^^
Sorry I meant v4, "a v6 HA does not need to be connected directly on a
                   v4 network".

> Moreover, there exist v6-only infrastructure networks and they're
> supposed to grow, and the v6 HAs may very well live there.

Alex


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



From mip6-bounces@ietf.org Tue Oct 25 14:01:09 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUT6j-0000y2-SB; Tue, 25 Oct 2005 14:01:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUT6i-0000xr-38
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 14:01:08 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09359
	for <mip6@ietf.org>; Tue, 25 Oct 2005 14:00:54 -0400 (EDT)
Received: from mail.flarion.com ([63.103.94.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUTJh-0004TZ-FY
	for mip6@ietf.org; Tue, 25 Oct 2005 14:14:34 -0400
Received: from ftmailserver.flariontech.com ([10.10.1.140]) by
	mail.flarion.com with Microsoft SMTPSVC(5.0.2195.6713);
	Tue, 25 Oct 2005 14:00:57 -0400
Content-Class: urn:content-classes:message
Subject: RE: [Mip6] I-D ACTION:draft-ietf-mip6-nemo-v4traversal-00.txt
Date: Tue, 25 Oct 2005 14:00:55 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Message-ID: <A11736FE943F1A408F8BBB1B9F5FE8AD17DE47@ftmailserver.flariontech.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
Thread-Topic: [Mip6] I-D ACTION:draft-ietf-mip6-nemo-v4traversal-00.txt
Thread-Index: AcXZiGNYuEeE68+XRVWTVfugCJTW3QABFqcQ
From: "Soliman, Hesham" <H.Soliman@flarion.com>
To: "Alexandru Petrescu" <alexandru.petrescu@motorola.com>
X-OriginalArrivalTime: 25 Oct 2005 18:00:57.0585 (UTC)
	FILETIME=[0CF45610:01C5D98E]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86
Content-Transfer-Encoding: quoted-printable
Cc: mip6@ietf.org, Keiichi SHIMA <keiichi@iijlab.net>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Alex,=20

Thanks for the reasoning. Comments inline


 > >> I do not agree with the MR obtaining a v4 CoA and then=20
 > sending a BU
 > >>  with a v4 Mobile Network Prefix.
 > >=20
 > > =3D> Why?
 >=20
 > Because MIP4 could do it better.  Using MIP4 instead of MIP6 in this
 > particular scenario would avoid going through v6, so a level of
 > encapsulation eliminated.

=3D> MIPv4 does not do it any better, whatever your definition of=20
"better" might be. It does it differently. There is less encapsulation
in the case where the MN is using an FA and no NATs are located between
the MN and the HA. However, this argument becomes less significant when
you consider the following:

- The whole point of the draft is to allow MIPv6 to be used regardless
of the access network capabilities. Please read the problem statement.=20
- Most large scale deployments of IPv4 in public networks use NATs. For
those scenarios there is no difference in encapsulation.

 > >> It is natural for MR to obtain a v4 CoA and then send a=20
 > MIP4 RegReq
 > >>  containing a v4 Mobile Network Prefix (and not a v6 BU).  Would=20
 > >> you agree with this?
 > >=20
 > > =3D> Please read the problem statement where it is clearly=20
 > stated that
 > >  running MIPv4 and MIPv6 simultaneously in inefficient
 >=20
 > I've read it.  Two technical reasons raised my interest: (1) MIP6 is
 > better than MIP4 because has DHAAD and RO, (2) sending BU and RegReq
 > each time is not efficient.

=3D> This is not the problem statement. I was referring to:
http://www.ietf.org/internet-drafts/draft-ietf-mip6-dsmip-problem-00.txt

 > > [running MIP4 and MIP6 simultaneously] prevent a node from having=20
 > > mobility across different networks supporting different IP=20
 > versions.
 >=20
 > This can not be true, tell me.  Having both MIP4 and MIP6 in a same
 > node can not prevent mobility across different networks supporting
 > different IP versions. =20

=3D> Please read the draft above.


 > If the application needs to have a permanent v4/v6 Home=20
 > Address even if
 > connected to the other IP version network then yes, one could use
 > enhancements. =20

=3D> So, you are aware of those problems.=20

  But even in that case I have remarks I'd keep=20
 > separate.

=3D> What are they?

 > >> Normally I agree, but here we talk IP version numbers.
 > >=20
 > > =3D> The whole point of this work is to make MIP work without being =

 > > tied to "version numbers"..
 >=20
 > That's a good goal.  But more precise would be to make MIP6 (not MIP)
 > beeing tied to "version numbers".

=3D> I assume you meant "..not being tied to...". If you agree it's a =
good
goal then I'm very confused about your objections.

Hesham

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D
This email may contain confidential and privileged material for the sole =
use
 of the intended recipient.  Any review or distribution by others is =
strictly
 prohibited.  If you are not the intended recipient please contact the =
sender
 and delete all copies.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D


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



From mip6-bounces@ietf.org Tue Oct 25 14:14:17 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUTJR-0001wA-TK; Tue, 25 Oct 2005 14:14:17 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUTJQ-0001vh-02
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 14:14:16 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10063
	for <mip6@ietf.org>; Tue, 25 Oct 2005 14:14:01 -0400 (EDT)
Received: from mail.flarion.com ([63.103.94.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUTWN-0004sO-9T
	for mip6@ietf.org; Tue, 25 Oct 2005 14:27:42 -0400
Received: from ftmailserver.flariontech.com ([10.10.1.140]) by
	mail.flarion.com with Microsoft SMTPSVC(5.0.2195.6713);
	Tue, 25 Oct 2005 14:14:02 -0400
Content-Class: urn:content-classes:message
Subject: RE: [Mip6] Security Considerations section
	ofdraft-ietf-mip6-nemo-v4traversal-00.txt
Date: Tue, 25 Oct 2005 14:14:00 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Message-ID: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCDAE@ftmailserver.flariontech.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
Thread-Topic: [Mip6] Security Considerations section
	ofdraft-ietf-mip6-nemo-v4traversal-00.txt
Thread-Index: AcXZj1zcEitRcXgtSmKv4g+ABb+i3wAABF6w
From: "Soliman, Hesham" <H.Soliman@flarion.com>
To: "Alexandru Petrescu" <alexandru.petrescu@motorola.com>,
	"Mobile IPv6 Mailing List" <mip6@ietf.org>
X-OriginalArrivalTime: 25 Oct 2005 18:14:02.0663 (UTC)
	FILETIME=[E0E5BB70:01C5D98F]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Content-Transfer-Encoding: quoted-printable
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org



 > Please let me deviate the discussion to the Security Considerations
 > section.  It is very good that the draft has this section contributed
 > from the start since the security aspects are important.
 >=20
 > It currently describes a method by which the v6 HA may use=20
 > the inherent
 > security established with the v6 Home Address to deduce that=20
 > the v4 HoA
 > contained in the BU is securely communicated.
 >=20
 > While the method may make sense, maybe some flaws are still possible.
 >=20
 > For example, it may be possible that an IPv6 attacker MN=20
 > that has good
 > credentials with its HA (verifiable by IPsec with respect to=20
 > its v6 HoA)
 > abuses the v4 address of another legitimate MN of same v6 HA.    The
 > attacker may include the legitimate's MN v4 address in its=20
 > BU.  Do you
 > think this would not be possible?

=3D> No that's not possible. The HA knows the IPv4 address corresponding
to the MN's IPv6 HoA. Just like it would know the home prefix =
corresponding
to the IPv6 HoA of the MR.=20


 > Another example is with the NAT traversal scheme.  The current text
 > describes that if two IPv4 addresses in a certain packet don't match
 > then the HA advises the MN to use a certain Refresh Time=20
 > (with the NAT
 > detection option).  So I think it is possible for an=20
 > attacker MN to fake
 > the IPv4 address of another MN, such that the legitimate MN=20
 > receives NAT
 > Detection Options although there's no NAT in place.  Do you=20
 > think this
 > would not be possible?

=3D> Of course, but that attack is known for all NAT detection schemes
including IKE-based schemes. There is no free lunch with NATs. If people
deploy them, they suffer the consequences.

Hesham

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

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D
This email may contain confidential and privileged material for the sole =
use
 of the intended recipient.  Any review or distribution by others is =
strictly
 prohibited.  If you are not the intended recipient please contact the =
sender
 and delete all copies.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D


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



From mip6-bounces@ietf.org Tue Oct 25 14:24:50 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUTTe-0005eF-KS; Tue, 25 Oct 2005 14:24:50 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUTTY-0005bN-D6
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 14:24:48 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10689
	for <mip6@ietf.org>; Tue, 25 Oct 2005 14:24:30 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUTgX-0005Ba-QU
	for mip6@ietf.org; Tue, 25 Oct 2005 14:38:11 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id j9PIO1i16944; Tue, 25 Oct 2005 20:24:01 +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
	j9PIO1CB008312; Tue, 25 Oct 2005 20:24:01 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200510251824.j9PIO1CB008312@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Alexandru Petrescu <alexandru.petrescu@motorola.com>
Subject: Re: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt 
In-reply-to: Your message of Tue, 25 Oct 2005 18:24:05 +0200.
	<435E5C25.4030106@motorola.com> 
Date: Tue, 25 Oct 2005 20:24:01 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   > => we agree: current DHAAD design is not stupid, it has only two real
   > problems:
   >  - the DHAAD idea itself is in danger because HA assignment is better
   
   By "HA assignment" you mean HA Switch message and draft?

=> no, I mean a HA assignment mechanism in general, including
(i.e., mainly :-) any still to be invented mechanism.
HA switch message is fine but is clearly *re*-assignment.

   If yes, that
   draft alone does not help for bootstrapping IMHO.  If DHAAD can be made
   to work with non-anycast addresses then DHAAD+MPD is a good idea to do
   bootstrapping simple (MPD is Mobile Prefix Discovery).
   
=> I don't understand why MPD is for when you have HA discovery/assignment
(the mobile prefix is simply the prefix of the HA address)... I should
have missed something, for instance there is more than one MP?

   >  - the current mechanism has some operational issues, mainly its lack
   >    of reasonably easy security and the spurious but common ICMP filtering.
   > My draft is about the second but the first is more critical and drastic...
   
   I don't see anything critical or drastic in HA assignment being proposed
   as better than DHAAD.

=> the question is drastic, i.e., if the answer is yes all discussions about
the best DHAAD mechanism are lost bits...

   It can complement DHAAD and work together with it
   (HA Switch, DHAAD Req, DHAAD Reply).  I don't think HA Switch is about
   to remove DHAAD altogether.

=> HA assignment should as it will give no choice, i.e., nothing to
discover.
   
   If DHAAD disappears altogether it's because it's bound to anycast
   addresses and nobody cared to put on paper the non-anycast DHAAD that
   works ok on at least two implementations.
   
=> I make a difference between the DHAAD function and the current
mechanism. Here the first question is about the function and the
second about the mechanism.

   I think I agree, although my experience with VRRP is very limited.
   
=> I have a (bad in fact :-) experience with HSRP which is the
Cisco proprietary protocol before VRRP.

Regards

Francis.Dupont@enst-bretagne.fr

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



From mip6-bounces@ietf.org Tue Oct 25 14:28:51 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUTXW-0007fG-Te; Tue, 25 Oct 2005 14:28:50 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUTXV-0007fB-Ik
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 14:28:49 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10918
	for <mip6@ietf.org>; Tue, 25 Oct 2005 14:28:35 -0400 (EDT)
Received: from av9-1-sn3.vrr.skanova.net ([81.228.9.185])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUTkV-0005JS-3m
	for mip6@ietf.org; Tue, 25 Oct 2005 14:42:16 -0400
Received: by av9-1-sn3.vrr.skanova.net (Postfix, from userid 502)
	id 3D97F37EE3; Tue, 25 Oct 2005 20:28:30 +0200 (CEST)
Received: from smtp3-2-sn3.vrr.skanova.net (smtp3-2-sn3.vrr.skanova.net
	[81.228.9.102]) by av9-1-sn3.vrr.skanova.net (Postfix) with ESMTP
	id 20B9737E89; Tue, 25 Oct 2005 20:28:30 +0200 (CEST)
Received: from shiraz.levkowetz.com (81-224-201-50-no45.tbcn.telia.com
	[81.224.201.50])
	by smtp3-2-sn3.vrr.skanova.net (Postfix) with ESMTP id CDB5737E43;
	Tue, 25 Oct 2005 20:28:29 +0200 (CEST)
Received: from localhost ([127.0.0.1])
	by shiraz.levkowetz.com with esmtp (Exim 4.54)
	id 1EUTXB-0001MD-AK; Tue, 25 Oct 2005 20:28:29 +0200
Message-ID: <435E794D.8090207@levkowetz.com>
Date: Tue, 25 Oct 2005 20:28:29 +0200
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Mozilla Thunderbird 1.0.7 (Macintosh/20050923)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Alexandru Petrescu <alexandru.petrescu@motorola.com>
Subject: Re: [Mip6] More comments on draft-ietf-mip6-nemo-v4traversal-00.txt
References: <435CF254.6050508@motorola.com> <435D0459.8050605@levkowetz.com>
	<435D250B.6040507@motorola.com>
	<435D32A5.4010400@levkowetz.com> <435DF9F1.60203@motorola.com>
	<435DFD3F.4020309@levkowetz.com> <435E6DF4.3070403@motorola.com>
In-Reply-To: <435E6DF4.3070403@motorola.com>
X-Enigmail-Version: 0.93.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: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Content-Transfer-Encoding: 7bit
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Hi,

on 2005-10-25 19:40 Alexandru Petrescu said the following:
> Henrik Levkowetz wrote:

[...]
>> Yes.  Which is why we write that the HA must be reachable through an
>> IPv4 address, instead of writing that the HA must have and IPv4 
>> address on an interface.
> 
> The draft also says that the MN sends packets to the HA IPv4 address in
> section 4.2 "Mobile node operation":
>> - The destination address in the IPv4 header is the home agent's IPv4
>> address.

Right, needs fixing.

> What I am trying to suggest is that a v6 HA does not need to be
> connected directly on a v6 network.  Moreover, there exist v6-only
> infrastructure networks and they're supposed to grow, and the v6 HAs may
> very well live there.

No-one's disagreeing, as far as I know.


	Henrik

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



From mip6-bounces@ietf.org Tue Oct 25 14:29:55 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUTYZ-0008Cz-MV; Tue, 25 Oct 2005 14:29:55 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUTYX-0008Cf-1K
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 14:29:53 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10989
	for <mip6@ietf.org>; Tue, 25 Oct 2005 14:29:38 -0400 (EDT)
Received: from av9-1-sn3.vrr.skanova.net ([81.228.9.185])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUTlW-0005LV-Lm
	for mip6@ietf.org; Tue, 25 Oct 2005 14:43:19 -0400
Received: by av9-1-sn3.vrr.skanova.net (Postfix, from userid 502)
	id 037A337F48; Tue, 25 Oct 2005 20:29:42 +0200 (CEST)
Received: from smtp3-2-sn3.vrr.skanova.net (smtp3-2-sn3.vrr.skanova.net
	[81.228.9.102]) by av9-1-sn3.vrr.skanova.net (Postfix) with ESMTP
	id DB6A937E89; Tue, 25 Oct 2005 20:29:42 +0200 (CEST)
Received: from shiraz.levkowetz.com (81-224-201-50-no45.tbcn.telia.com
	[81.224.201.50])
	by smtp3-2-sn3.vrr.skanova.net (Postfix) with ESMTP id CFC7437E42;
	Tue, 25 Oct 2005 20:29:42 +0200 (CEST)
Received: from localhost ([127.0.0.1])
	by shiraz.levkowetz.com with esmtp (Exim 4.54)
	id 1EUTYM-0001MU-IE; Tue, 25 Oct 2005 20:29:42 +0200
Message-ID: <435E7996.5020204@levkowetz.com>
Date: Tue, 25 Oct 2005 20:29:42 +0200
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Mozilla Thunderbird 1.0.7 (Macintosh/20050923)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Alexandru Petrescu <alexandru.petrescu@motorola.com>
Subject: Re: [Mip6] More comments on draft-ietf-mip6-nemo-v4traversal-00.txt
References: <435CF254.6050508@motorola.com> <435D0459.8050605@levkowetz.com>
	<435D250B.6040507@motorola.com>
	<435D32A5.4010400@levkowetz.com> <435DF9F1.60203@motorola.com>
	<435DFD3F.4020309@levkowetz.com>
	<435E6DF4.3070403@motorola.com> <435E7163.3030004@motorola.com>
In-Reply-To: <435E7163.3030004@motorola.com>
X-Enigmail-Version: 0.93.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: 1ac7cc0a4cd376402b85bc1961a86ac2
Content-Transfer-Encoding: 7bit
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org



on 2005-10-25 19:54 Alexandru Petrescu said the following:
[...]
>> What I am trying to suggest is that a v6 HA does not need to be 
>> connected directly on a v6 network.
>                           ^^^
> Sorry I meant v4, "a v6 HA does not need to be connected directly on a
>                    v4 network".

Well, no-one's disagreeing with this either, as far as I know :-)


	Henrik

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



From mip6-bounces@ietf.org Tue Oct 25 14:37:06 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUTfW-0002OT-QA; Tue, 25 Oct 2005 14:37:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUTfU-0002ON-LJ
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 14:37:05 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11412
	for <mip6@ietf.org>; Tue, 25 Oct 2005 14:36:50 -0400 (EDT)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUTsV-0005aS-9F
	for mip6@ietf.org; Tue, 25 Oct 2005 14:50:31 -0400
Received: from il06exr03.mot.com (il06exr03.mot.com [129.188.137.133])
	by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id j9PImrve010537;
	Tue, 25 Oct 2005 11:48:53 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by il06exr03.mot.com (8.13.1/8.13.0) with ESMTP id j9PIl0mW029957;
	Tue, 25 Oct 2005 13:47:01 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id 05CC2865980; Tue, 25 Oct 2005 20:36:57 +0200 (CEST)
Message-ID: <435E7B48.3050900@motorola.com>
Date: Tue, 25 Oct 2005 20:36:56 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: "Soliman, Hesham" <H.Soliman@flarion.com>
Subject: Re: [Mip6] I-D ACTION:draft-ietf-mip6-nemo-v4traversal-00.txt
References: <A11736FE943F1A408F8BBB1B9F5FE8AD17DE47@ftmailserver.flariontech.com>
In-Reply-To: <A11736FE943F1A408F8BBB1B9F5FE8AD17DE47@ftmailserver.flariontech.com>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c83ccb5cc10e751496398f1233ca9c3a
Content-Transfer-Encoding: 7bit
Cc: mip6@ietf.org, Keiichi SHIMA <keiichi@iijlab.net>,
	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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Soliman, Hesham wrote:
>> Because MIP4 could do it better.  Using MIP4 instead of MIP6 in 
>> this particular scenario would avoid going through v6, so a level 
>> of encapsulation eliminated.
> 
> => MIPv4 does not do it any better, whatever your definition of 
> "better" might be. It does it differently. There is less 
> encapsulation in the case where the MN is using an FA and no NATs are
>  located between the MN and the HA.

The fact that FAs or NATs are present don't influence MR having to
encapsulate packets from a v4 LFN.  Whatever MR connects to - v4 or v6,
FA or NAT - the MR must encapsulate packets from LFN, for NEMO reasons.

If MR connects to a v4 network and MIP6 is used (no MIP4) then MR
encapsulates LFN IPv4 packets in IPv6 and then again in IPv4.  That IPv6
encapsulation is pure overhead.

> However, this argument becomes less significant when you consider the
>  following:
> 
> - The whole point of the draft is to allow MIPv6 to be used 
> regardless of the access network capabilities.

Yes, I agree.  It goes further than just that though, at least because
it suggests offering IPv4 access to LFNs, without real MIP4 support.

For example, although the draft proposes using permanent IPv4 Home
Addresses with MIP6, and suggests HA has an IPv4 address, it says
nothing about that HA doing proxy ARP for the v4 address received in the BU.

> Please read the problem statement. - Most large scale deployments of
>  IPv4 in public networks use NATs.

YEs, and most large scale deployments use Firewalls coupled to NATs and
there's no large scale IPv6 access network deployments for wireless
mobiles.  Hence the suggestion to move focus from v4-LFN to Firewall
traversal.

> For those scenarios there is no difference in encapsulation.

See above where I explain that MIP6 MR giving IPv4 LFN unnecessarily
encapsulates in v6 when connecting to a v4 network.

>>>> It is natural for MR to obtain a v4 CoA and then send a
>> MIP4 RegReq
>>>> containing a v4 Mobile Network Prefix (and not a v6 BU).  Would
>>>>  you agree with this?
>>> 
>>> => Please read the problem statement where it is clearly
>> stated that
>>> running MIPv4 and MIPv6 simultaneously in inefficient
>> 
>> I've read it.  Two technical reasons raised my interest: (1) MIP6 
>> is better than MIP4 because has DHAAD and RO, (2) sending BU and 
>> RegReq each time is not efficient.
> 
> => This is not the problem statement. I was referring to: 
> http://www.ietf.org/internet-drafts/draft-ietf-mip6-dsmip-problem-00.txt
> 
So what I've read in the DSMIPv6 draft about MIP6 being selected over
MIP4 because RO and DHAAD is not conformant to:
http://www.ietf.org/internet-drafts/draft-ietf-mip6-dsmip-problem-00.txt

>>> [running MIP4 and MIP6 simultaneously] prevent a node from having
>>>  mobility across different networks supporting different IP
>> versions.
>> 
>> This can not be true, tell me.  Having both MIP4 and MIP6 in a same
>>  node can not prevent mobility across different networks supporting
>>  different IP versions.
> 
> => Please read the draft above.
> 
> 
>> If the application needs to have a permanent v4/v6 Home Address 
>> even if connected to the other IP version network then yes, one 
>> could use enhancements.
> 
> => So, you are aware of those problems.

I am deeply aware of the following problem: a MIPv6 MH connecting to a
NAT-v4-only network can't normally use its permanent IPv6 Home Address.

I am not aware of a problem where an IPv4 LFN with an IPv6 MR connecting
to a v4-only network needs to communicate.  The problem statement may
mention it though, but I don't find it to be a problem other than on paper.

>> But even in that case I have remarks I'd keep separate.
> 
> => What are they?

See the Security thread and wonder how could one protect against the
threats mentioned there and think that using IPv4 IPsec (in addition to
IPv6 IPsec) may be a good solution.

>>>> Normally I agree, but here we talk IP version numbers.
>>> 
>>> => The whole point of this work is to make MIP work without being
>>>  tied to "version numbers"..
>> 
>> That's a good goal.  But more precise would be to make MIP6 (not 
>> MIP) beeing tied to "version numbers".
> 
> => I assume you meant "..not being tied to...". If you agree it's a 
> good goal then I'm very confused about your objections.

Yes, that's what I meant.  I agree it is a good goal to the point of
thinking it may be a too high goal to provide all possible combinations
of v4/v6 MR/MH/LFN simply with v4 enhancements of MIP6.

Alex

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



From mip6-bounces@ietf.org Tue Oct 25 14:42:21 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUTka-0003OV-2y; Tue, 25 Oct 2005 14:42:20 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUTkY-0003OH-Gn
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 14:42:18 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11735
	for <mip6@ietf.org>; Tue, 25 Oct 2005 14:42:04 -0400 (EDT)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUTxX-0005k8-T9
	for mip6@ietf.org; Tue, 25 Oct 2005 14:55:45 -0400
Received: from il06exr02.mot.com (il06exr02.mot.com [129.188.137.132])
	by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id j9PIs55X011459;
	Tue, 25 Oct 2005 11:54:05 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by il06exr02.mot.com (8.13.1/8.13.0) with ESMTP id j9PIomYe019548;
	Tue, 25 Oct 2005 13:50:49 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id 408EF865980; Tue, 25 Oct 2005 20:42:09 +0200 (CEST)
Message-ID: <435E7C81.6000204@motorola.com>
Date: Tue, 25 Oct 2005 20:42:09 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: "Soliman, Hesham" <H.Soliman@flarion.com>
Subject: Re: [Mip6] Security Considerations section
	ofdraft-ietf-mip6-nemo-v4traversal-00.txt
References: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCDAE@ftmailserver.flariontech.com>
In-Reply-To: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCDAE@ftmailserver.flariontech.com>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Content-Transfer-Encoding: 7bit
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Soliman, Hesham wrote:

> 
>> Please let me deviate the discussion to the Security Considerations
>>  section.  It is very good that the draft has this section 
>> contributed from the start since the security aspects are 
>> important.
>> 
>> It currently describes a method by which the v6 HA may use the 
>> inherent security established with the v6 Home Address to deduce 
>> that the v4 HoA contained in the BU is securely communicated.
>> 
>> While the method may make sense, maybe some flaws are still 
>> possible.
>> 
>> For example, it may be possible that an IPv6 attacker MN that has 
>> good credentials with its HA (verifiable by IPsec with respect to 
>> its v6 HoA) abuses the v4 address of another legitimate MN of same 
>> v6 HA.    The attacker may include the legitimate's MN v4 address 
>> in its BU.  Do you think this would not be possible?
> 
> => No that's not possible. The HA knows the IPv4 address 
> corresponding to the MN's IPv6 HoA. Just like it would know the home 
> prefix corresponding to the IPv6 HoA of the MR.

How does it know it?  The NEMOv6 spec has a Prefix Table for that, and
the NEMOv4 personal draft too.  This draft does not have such a table.

> Therefore, in order to authorize the mobile node's IPv4 home address 
> binding, the home agent MUST store the IPv4 address corresponding to 
> the IPv6 address that is allocated to a mobile node.

Do you think this text is sufficient?  Don't you think that using IPv4
IPsec makes more sense?

>> Another example is with the NAT traversal scheme.  The current text
>>  describes that if two IPv4 addresses in a certain packet don't 
>> match then the HA advises the MN to use a certain Refresh Time 
>> (with the NAT detection option).  So I think it is possible for an 
>> attacker MN to fake the IPv4 address of another MN, such that the 
>> legitimate MN receives NAT Detection Options although there's no 
>> NAT in place.  Do you think this would not be possible?
> 
> => Of course, but that attack is known for all NAT detection schemes
>  including IKE-based schemes. There is no free lunch with NATs. If 
> people deploy them, they suffer the consequences.

That's rhetoric, right?  Too easy to claim weaknesses in some protocol
are due to another protocol.

This makes me think I'm not very sure who are the customers of this
draft and whether they can delegate responsibility to operator's
deployed NATs.

Alex


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



From mip6-bounces@ietf.org Tue Oct 25 14:44:29 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUTmf-0003vM-CD; Tue, 25 Oct 2005 14:44:29 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUTmd-0003v8-AX
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 14:44:27 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11846
	for <mip6@ietf.org>; Tue, 25 Oct 2005 14:44:13 -0400 (EDT)
Received: from motgate2.mot.com ([144.189.100.101])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUTzc-0005nx-Sf
	for mip6@ietf.org; Tue, 25 Oct 2005 14:57:54 -0400
Received: from az33exr03.mot.com (az33exr03.mot.com [10.64.251.233])
	by motgate2.mot.com (8.12.11/Motgate2) with ESMTP id j9PIxYSb024253
	for <mip6@ietf.org>; Tue, 25 Oct 2005 11:59:34 -0700 (MST)
Received: from de01exm69.ds.mot.com (de01exm69.am.mot.com [10.176.8.25])
	by az33exr03.mot.com (8.13.1/8.13.0) with ESMTP id j9PIrcZu006307
	for <mip6@ietf.org>; Tue, 25 Oct 2005 13:53:39 -0500 (CDT)
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] draft-dupont-mip6-dhaadharmful-00.txt 
Date: Tue, 25 Oct 2005 14:44:22 -0400
Message-ID: <0B40B6F9CB990B428819561A2A55613A1040ED@de01exm69.ds.mot.com>
Thread-Topic: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt 
Thread-Index: AcXZkWUtIZDXIkuHTTCENS11aAZPqgAAi7og
From: "Narayanan Vidya-CVN065" <vidya@motorola.com>
To: <Francis.Dupont@enst-bretagne.fr>,
	"Petrescu Alexandru-AAP021" <alexandru.petrescu@motorola.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 34d35111647d654d033d58d318c0d21a
Content-Transfer-Encoding: quoted-printable
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

I'm trying to catch up with the plethora of emails here :)=20

Lets distinguish VRRP-based mechanisms from "load balancing" mechanisms
- fundamentally, one aims at failover and the other aims at load
balancing. Architecturally, these are different.=20

A few questions to ask here may be the following:=20

1. Are we working on failover mechanisms in the WG?=20

2. Are we working on load balancing mechanisms in the WG?=20

3. Do we expect a common architecture/solution to solve the two?=20

If the answer to 3 is 'yes', then I think we are limited in the number
of solutions to consider (and this, I believe, is likely to be a good
thing).=20

Regards,
Vidya

> -----Original Message-----
> From: Francis.Dupont@enst-bretagne.fr=20
> [mailto:Francis.Dupont@enst-bretagne.fr]=20
> Sent: Tuesday, October 25, 2005 1:24 PM
> To: Petrescu Alexandru-AAP021
> Cc: Narayanan Vidya-CVN065; mip6@ietf.org; Kilian Weniger; James Kempf
> Subject: Re: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt=20
>=20
>  In your previous mail you wrote:
>=20
>    > =3D> we agree: current DHAAD design is not stupid, it has=20
> only two real
>    > problems:
>    >  - the DHAAD idea itself is in danger because HA=20
> assignment is better
>   =20
>    By "HA assignment" you mean HA Switch message and draft?
>=20
> =3D> no, I mean a HA assignment mechanism in general, including=20
> (i.e., mainly :-) any still to be invented mechanism.
> HA switch message is fine but is clearly *re*-assignment.
>=20
>    If yes, that
>    draft alone does not help for bootstrapping IMHO.  If=20
> DHAAD can be made
>    to work with non-anycast addresses then DHAAD+MPD is a=20
> good idea to do
>    bootstrapping simple (MPD is Mobile Prefix Discovery).
>   =20
> =3D> I don't understand why MPD is for when you have HA=20
> discovery/assignment (the mobile prefix is simply the prefix=20
> of the HA address)... I should have missed something, for=20
> instance there is more than one MP?
>=20
>    >  - the current mechanism has some operational issues,=20
> mainly its lack
>    >    of reasonably easy security and the spurious but=20
> common ICMP filtering.
>    > My draft is about the second but the first is more=20
> critical and drastic...
>   =20
>    I don't see anything critical or drastic in HA assignment=20
> being proposed
>    as better than DHAAD.
>=20
> =3D> the question is drastic, i.e., if the answer is yes all=20
> discussions about the best DHAAD mechanism are lost bits...
>=20
>    It can complement DHAAD and work together with it
>    (HA Switch, DHAAD Req, DHAAD Reply).  I don't think HA=20
> Switch is about
>    to remove DHAAD altogether.
>=20
> =3D> HA assignment should as it will give no choice, i.e.,=20
> nothing to discover.
>   =20
>    If DHAAD disappears altogether it's because it's bound to anycast
>    addresses and nobody cared to put on paper the non-anycast=20
> DHAAD that
>    works ok on at least two implementations.
>   =20
> =3D> I make a difference between the DHAAD function and the=20
> current mechanism. Here the first question is about the=20
> function and the second about the mechanism.
>=20
>    I think I agree, although my experience with VRRP is very limited.
>   =20
> =3D> I have a (bad in fact :-) experience with HSRP which is=20
> the Cisco proprietary protocol before VRRP.
>=20
> Regards
>=20
> Francis.Dupont@enst-bretagne.fr
>=20

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



From mip6-bounces@ietf.org Tue Oct 25 14:51:27 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUTtP-0000Xm-4v; Tue, 25 Oct 2005 14:51:27 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUTtN-0000Vj-MC
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 14:51:25 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12215
	for <mip6@ietf.org>; Tue, 25 Oct 2005 14:51:11 -0400 (EDT)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUU6M-000606-7x
	for mip6@ietf.org; Tue, 25 Oct 2005 15:04:52 -0400
Received: from il06exr01.mot.com (il06exr01.mot.com [129.188.137.131])
	by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id j9PJ3C4k012988;
	Tue, 25 Oct 2005 12:03:12 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by il06exr01.mot.com (8.13.1/8.13.0) with ESMTP id j9PJ1Bgb026492;
	Tue, 25 Oct 2005 14:01:12 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id 9601E865980; Tue, 25 Oct 2005 20:51:16 +0200 (CEST)
Message-ID: <435E7EA4.2070202@motorola.com>
Date: Tue, 25 Oct 2005 20:51:16 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
Subject: Re: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
References: <200510251824.j9PIO1CB008312@givry.rennes.enst-bretagne.fr>
In-Reply-To: <200510251824.j9PIO1CB008312@givry.rennes.enst-bretagne.fr>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
Content-Transfer-Encoding: 7bit
Cc: James Kempf <Kempf@docomolabs-usa.com>, 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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Francis, please allow me slight remarks, don't take as corrections.

Francis Dupont wrote:

>  In your previous mail you wrote:
> 
>    > => we agree: current DHAAD design is not stupid, it has only two real
>    > problems:
>    >  - the DHAAD idea itself is in danger because HA assignment is better
>    
>    By "HA assignment" you mean HA Switch message and draft?
> 
> => no, I mean a HA assignment mechanism in general, including
> (i.e., mainly :-) any still to be invented mechanism.
> HA switch message is fine but is clearly *re*-assignment.
> 
>    If yes, that
>    draft alone does not help for bootstrapping IMHO.  If DHAAD can be made
>    to work with non-anycast addresses then DHAAD+MPD is a good idea to do
>    bootstrapping simple (MPD is Mobile Prefix Discovery).
>    
> => I don't understand why MPD is for when you have HA discovery/assignment
> (the mobile prefix is simply the prefix of the HA address)... I should
> have missed something, for instance there is more than one MP?

"MP" could be misinterpreted as "Mobile Prefix" which isn't.

MPD is more like: Mobile       Prefix Discovery, a prefix discovery
performed by a mobile.

There's only one MPD.

DHAAD doesn't provide a prefix length field in DHAAD Reply, so the MN
can't know it.  MPD is the equivalent of local RS/RA for a MN that is
away from home.

For bootstrapping, MN could do DHAAD to get the HA's full address and
then interrogate that HA with MPD Sol and get Response, and then call
the stateless address autoconfiguration functions easily.

HA-Switch and DHAAD+MPD could also be used when the home link is
re-numbered.

>    >  - the current mechanism has some operational issues, mainly its lack
>    >    of reasonably easy security and the spurious but common ICMP filtering.
>    > My draft is about the second but the first is more critical and drastic...
>    
>    I don't see anything critical or drastic in HA assignment being proposed
>    as better than DHAAD.
> 
> => the question is drastic, i.e., if the answer is yes all discussions about
> the best DHAAD mechanism are lost bits...

I agree.

[... snip because I don't know]

Alex


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



From mip6-bounces@ietf.org Tue Oct 25 14:54:43 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUTwZ-00023r-O0; Tue, 25 Oct 2005 14:54:43 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUTwX-00023m-LK
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 14:54:41 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12421
	for <mip6@ietf.org>; Tue, 25 Oct 2005 14:54:27 -0400 (EDT)
Received: from mail.flarion.com ([63.103.94.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUU9Y-00065j-1x
	for mip6@ietf.org; Tue, 25 Oct 2005 15:08:08 -0400
Received: from ftmailserver.flariontech.com ([10.10.1.140]) by
	mail.flarion.com with Microsoft SMTPSVC(5.0.2195.6713);
	Tue, 25 Oct 2005 14:54:28 -0400
Content-Class: urn:content-classes:message
Subject: RE: [Mip6] I-D ACTION:draft-ietf-mip6-nemo-v4traversal-00.txt
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 25 Oct 2005 14:54:26 -0400
Message-ID: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCDAF@ftmailserver.flariontech.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
Thread-Topic: [Mip6] I-D ACTION:draft-ietf-mip6-nemo-v4traversal-00.txt
Thread-Index: AcXZkxV0B5Pp/+PUTp+9tUdRrIb0jgAALDuA
From: "Soliman, Hesham" <H.Soliman@flarion.com>
To: "Alexandru Petrescu" <alexandru.petrescu@motorola.com>
X-OriginalArrivalTime: 25 Oct 2005 18:54:28.0448 (UTC)
	FILETIME=[86C72600:01C5D995]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 29dc808194f5fb921c09d0040806d6eb
Content-Transfer-Encoding: quoted-printable
Cc: mip6@ietf.org, Keiichi SHIMA <keiichi@iijlab.net>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org


=20
 > > =3D> MIPv4 does not do it any better, whatever your definition of=20
 > > "better" might be. It does it differently. There is less=20
 > > encapsulation in the case where the MN is using an FA and=20
 > no NATs are
 > >  located between the MN and the HA.
 >=20
 > The fact that FAs or NATs are present don't influence MR having to
 > encapsulate packets from a v4 LFN.  Whatever MR connects to=20
 > - v4 or v6,
 > FA or NAT - the MR must encapsulate packets from LFN, for=20
 > NEMO reasons.

=3D> You're discussing a separate topic here. I didn't make any comments
about this. Are you talking about MIPv4? If so, then there is no=20
encapsulation. MIPv4 assumes that it is possible for the MN to
use it's home address in a foreign network and that ingress=20
filtering will not drop the packet. It also allows the FA to reverse
tunnel. If you choose reverse tunnelling then I don't understand
where the extra overhead in encapsulation is.

 > If MR connects to a v4 network and MIP6 is used (no MIP4) then MR
 > encapsulates LFN IPv4 packets in IPv6 and then again in=20
 > IPv4. =20

=3D> No! Please read the draft again. The draft says:
 - IPv6 in IPv4 (foreign network using public IPv4 addresses only)
 - IPv6 in UDP/IPv4 (if a NAT is detected).

That IPv6
 > encapsulation is pure overhead.

=3D> Yes and we don't do it...

 > Yes, I agree.  It goes further than just that though, at=20
 > least because
 > it suggests offering IPv4 access to LFNs, without real MIP4 support.

=3D> That's the *goal* of the draft. We discussed this in IETF when the
scenarios and requirements were presented. No one disagreed with
this requirement.

 > For example, although the draft proposes using permanent IPv4 Home
 > Addresses with MIP6, and suggests HA has an IPv4 address, it says
 > nothing about that HA doing proxy ARP for the v4 address=20
 > received in the BU.

=3D> Sure, we can add that.=20

 >=20
 > > Please read the problem statement. - Most large scale=20
 > deployments of
 > >  IPv4 in public networks use NATs.
 >=20
 > YEs, and most large scale deployments use Firewalls coupled=20
 > to NATs and
 > there's no large scale IPv6 access network deployments for wireless
 > mobiles.  Hence the suggestion to move focus from v4-LFN to Firewall
 > traversal.

=3D> I disagree. FW traversal sounds like port scanning. We're not in=20
the business of standardising attacks on a closed network.=20
What do you do if a FW disables the mobility header?? Should we
encapsulate MIPv6 in HTTP?

 > > For those scenarios there is no difference in encapsulation.
 >=20
 > See above where I explain that MIP6 MR giving IPv4 LFN unnecessarily
 > encapsulates in v6 when connecting to a v4 network.

=3D> You're objecting to something we never did. I agree it's not =
needed!
We don't do that.

 > > =3D> This is not the problem statement. I was referring to:=20
 > >=20
http://www.ietf.org/internet-drafts/draft-ietf-mip6-dsmip-problem-00.txt
>=20
 >So what I've read in the DSMIPv6 draft about MIP6 being selected over
 >MIP4 because RO and DHAAD is not conformant to:
 =
>http://www.ietf.org/internet-drafts/draft-ietf-mip6-dsmip-problem-00.txt=


=3D> MIPv6 was not chosen over MIPv4. We're standardising a MIPv6 =
solution
in the MIP6 WG and I'm going to ask the MIP4 WG to do the same thing=20
for MIPv4. I don't know why you assume we *chose* MIPv6 over MIPv4.



 >I am deeply aware of the following problem: a MIPv6 MH connecting to a
 >NAT-v4-only network can't normally use its permanent IPv6 Home =
Address.

 >I am not aware of a problem where an IPv4 LFN with an IPv6 MR =
connecting
 >to a v4-only network needs to communicate.  The problem statement may
 > mention it though, but I don't find it to be a problem other than on =
paper.

=3D> Do you assume that all hosts will use IPv6 applications and=20
only communicate with other IPv6 hosts? If the answer is no, then
you need to provide them a stable IPv4 address (read:home address).=20
And you need to provide mobility for that address. This is what the
draft does.

>=20
> =3D> What are they?

 >See the Security thread and wonder how could one protect against the
 >threats mentioned there and think that using IPv4 IPsec (in addition =
to=20
 >IPv6 IPsec) may be a good solution.

=3D> See my reply. BTW, there is no IPv4 IPsec and IPv6 IPsec. The same=20
protocol works for both.


  > =3D> I assume you meant "..not being tied to...". If you agree it's =
a=20
  > good goal then I'm very confused about your objections.

 >Yes, that's what I meant.  I agree it is a good goal to the point of
 >thinking it may be a too high goal to provide all possible =
combinations
 >of v4/v6 MR/MH/LFN simply with v4 enhancements of MIP6.

=3D> I think the draft proves that this goal is easily achievable.

Hesham



=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D
This email may contain confidential and privileged material for the sole =
use
 of the intended recipient.  Any review or distribution by others is =
strictly
 prohibited.  If you are not the intended recipient please contact the =
sender
 and delete all copies.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D


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



From mip6-bounces@ietf.org Tue Oct 25 14:56:26 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUTyE-0002EP-Bz; Tue, 25 Oct 2005 14:56:26 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUTyC-0002Dw-C0
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 14:56:24 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12488
	for <mip6@ietf.org>; Tue, 25 Oct 2005 14:56:09 -0400 (EDT)
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUUBC-00067n-0A
	for mip6@ietf.org; Tue, 25 Oct 2005 15:09:51 -0400
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id j9PINAM16365;
	Tue, 25 Oct 2005 11:23:10 -0700
X-mProtect: <200510251823> Nokia Silicon Valley Messaging Protection
Received: from mvdhcp14184.americas.nokia.com (172.18.141.84,
	claiming to be "[127.0.0.1]")
	by darkstar.iprg.nokia.com smtpdAUI6DJ; Tue, 25 Oct 2005 11:23:08 PDT
Message-ID: <435E7FBE.5080109@iprg.nokia.com>
Date: Tue, 25 Oct 2005 11:55:58 -0700
From: Vijay Devarapalli <vijayd@iprg.nokia.com>
User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: COMBES Jean-Michel RD-MAPS-ISS <jeanmichel.combes@francetelecom.com>
Subject: Re: [Mip6] General comments/questions on MIPv6 bootstrapping
References: <D2AA6DF1AEE4404F8D983B68BAC97CD2022B915A@ftrdmel3.rd.francetelecom.fr>
In-Reply-To: <D2AA6DF1AEE4404F8D983B68BAC97CD2022B915A@ftrdmel3.rd.francetelecom.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Content-Transfer-Encoding: 7bit
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

COMBES Jean-Michel RD-MAPS-ISS wrote:

>>>E.g., what will be the trigger in the terminal to know which is the 
>>>bootstrapping mechanism the terminal has to use?
>>
>>we have some text on this in the integrated draft. the mobile 
>>node could be configured to use either DHCPv6 or DNS for HA 
>>discovery. based on the configuration the MN uses a 
>>particular mechanism for HA discovery. in case both are 
>>available and the MN gets a response through a DHCP reply and 
>>DNS reply, the DHCP response has precedence. do you see a 
>>need for more text on this? let us know if there are any 
>>issues we havent considered.
> 
> 
> Maybe, some text is needed to explain how and when the MN knows that it
> cannot get the HA address with the DHCP-based mechanism and decides to
> use finally DNS-based mechanism.

there is some text in section 3.3 on this.

    In the fallback case, the mobile node is not able to acquire the home
    agent information via DHCPv6.  The mobile node performs DNS queries
    to discover the home agent address as defined in [BOOT-SPLIT].  To
    perform DNS based home agent discovery, the mobile node needs to know
    the DNS server address.  How the mobile node knows the DNS server
    address is outside the scope of this document.

the current assumption is that the if the MN finds no HA
information in the DHCP reply when it had requested the
HA information, it falls back to using DNS.

>>
>>for NEMO, in addition to the 4 problems listed above, a 
>>mobile network prefix needs to be configured. for that there 
>>are two drafts being progressed in the NEMO WG.
>>
>>http://www.ietf.org/internet-drafts/draft-ietf-nemo-dhcpv6-pd-00.txt
>>http://www.ietf.org/internet-drafts/draft-ietf-nemo-prefix-del
>>egation-00.txt
>>
>>these drafts were written up even before the boostrapping 
>>work started in the MIP6 WG. is there anything else that 
>>needs to be addressed for NEMO bootstrapping?
> 
> 
> IMO, the other one is to be able to do the difference between a MIPv6 HA
> discovery and a NEMO HA discovery. But it seems that the DHCP-based and
> the DNS-based mechanisms are easily adaptable to allow this.

to my understanding, that is correct. there is no plan
to develop another mechanism to discover a HA in the
NEMO WG. MIP6 bootstrap mechanisms for HA discovery,
MR HoA configuration, IPsec SA setup and DNS update for
the HoA should be re-used in NEMO.

Vijay


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



From mip6-bounces@ietf.org Tue Oct 25 14:59:27 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUU19-0002jC-1T; Tue, 25 Oct 2005 14:59:27 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUU16-0002iv-Jz
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 14:59:24 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12628
	for <mip6@ietf.org>; Tue, 25 Oct 2005 14:59:10 -0400 (EDT)
Received: from mail.flarion.com ([63.103.94.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUUE7-0006Cr-Hf
	for mip6@ietf.org; Tue, 25 Oct 2005 15:12:51 -0400
Received: from ftmailserver.flariontech.com ([10.10.1.140]) by
	mail.flarion.com with Microsoft SMTPSVC(5.0.2195.6713);
	Tue, 25 Oct 2005 14:59:12 -0400
Content-Class: urn:content-classes:message
Subject: RE: [Mip6] Security Considerations section
	ofdraft-ietf-mip6-nemo-v4traversal-00.txt
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 25 Oct 2005 14:59:10 -0400
Message-ID: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCDB0@ftmailserver.flariontech.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
Thread-Topic: [Mip6] Security Considerations section
	ofdraft-ietf-mip6-nemo-v4traversal-00.txt
Thread-Index: AcXZk88FC+xyRhPERVGQ8iY2vIceqwAAepqA
From: "Soliman, Hesham" <H.Soliman@flarion.com>
To: "Alexandru Petrescu" <alexandru.petrescu@motorola.com>
X-OriginalArrivalTime: 25 Oct 2005 18:59:12.0166 (UTC)
	FILETIME=[2FE31460:01C5D996]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Content-Transfer-Encoding: quoted-printable
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org


=20
 > > =3D> No that's not possible. The HA knows the IPv4 address=20
 > > corresponding to the MN's IPv6 HoA. Just like it would=20
 > know the home=20
 > > prefix corresponding to the IPv6 HoA of the MR.
 >=20
 > How does it know it?  The NEMOv6 spec has a Prefix Table for=20
 > that, and
 > the NEMOv4 personal draft too.  This draft does not have=20
 > such a table.

=3D> A "Table" is an implementation specific issue. I agree that
it should be explicitly stated in the draft. We can add that.
But FWIW that is the assumption in the draft today. We can
explicitly add that in the next one.=20

 >=20
 > > Therefore, in order to authorize the mobile node's IPv4=20
 > home address=20
 > > binding, the home agent MUST store the IPv4 address=20
 > corresponding to=20
 > > the IPv6 address that is allocated to a mobile node.
 >=20
 > Do you think this text is sufficient?  Don't you think that=20
 > using IPv4
 > IPsec makes more sense?

=3D> There is no such thing as "IPv4 IPsec". Yes I do think it's
sufficient.

 > > =3D> Of course, but that attack is known for all NAT=20
 > detection schemes
 > >  including IKE-based schemes. There is no free lunch with NATs. If=20
 > > people deploy them, they suffer the consequences.
 >=20
 > That's rhetoric, right?  Too easy to claim weaknesses in=20
 > some protocol
 > are due to another protocol.

=3D> Huh? I didn't claim that. I said that this is a common problem.
A NAT is a MITM. NAT detection is about detecting a MITM. Of course,
that MITM could be a NAT or an attacker. But no one has a way of knowing
that today. So my point is, NATs are bad and we can't get something out =
of
nothing.

Hesham

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D
This email may contain confidential and privileged material for the sole =
use
 of the intended recipient.  Any review or distribution by others is =
strictly
 prohibited.  If you are not the intended recipient please contact the =
sender
 and delete all copies.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D


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



From mip6-bounces@ietf.org Tue Oct 25 15:20:11 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUULD-0003gd-OZ; Tue, 25 Oct 2005 15:20:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUULC-0003fy-7b
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 15:20:10 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13860
	for <mip6@ietf.org>; Tue, 25 Oct 2005 15:19:55 -0400 (EDT)
Received: from motgate.mot.com ([129.188.136.100])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUUYD-0006qF-7e
	for mip6@ietf.org; Tue, 25 Oct 2005 15:33:37 -0400
Received: from az33exr03.mot.com (az33exr03.mot.com [10.64.251.233])
	by motgate.mot.com (Motorola/Motgate) with ESMTP id j9PJK7PX006914;
	Tue, 25 Oct 2005 12:20:08 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by az33exr03.mot.com (8.13.1/8.13.0) with ESMTP id j9PJTLFk002058;
	Tue, 25 Oct 2005 14:29:22 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id 60647865980; Tue, 25 Oct 2005 21:20:05 +0200 (CEST)
Message-ID: <435E8565.8020105@motorola.com>
Date: Tue, 25 Oct 2005 21:20:05 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: "Soliman, Hesham" <H.Soliman@flarion.com>
Subject: Re: [Mip6] Security Considerations section
	ofdraft-ietf-mip6-nemo-v4traversal-00.txt
References: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCDB0@ftmailserver.flariontech.com>
In-Reply-To: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCDB0@ftmailserver.flariontech.com>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
Content-Transfer-Encoding: 7bit
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Soliman, Hesham wrote:
> 
>>> => No that's not possible. The HA knows the IPv4 address 
>>> corresponding to the MN's IPv6 HoA. Just like it would
>> know the home
>>> prefix corresponding to the IPv6 HoA of the MR.
>> 
>> How does it know it?  The NEMOv6 spec has a Prefix Table for that, 
>> and the NEMOv4 personal draft too.  This draft does not have such a
>> table.
> 
> => A "Table" is an implementation specific issue.

So isn't this targetting the implementors?

> I agree that it should be explicitly stated in the draft. We can add 
> that. But FWIW that is the assumption in the draft today. We can 
> explicitly add that in the next one.

Yes, I agree.

>>> Therefore, in order to authorize the mobile node's IPv4 home 
>>> address binding, the home agent MUST store the IPv4 address
>> corresponding to
>>> the IPv6 address that is allocated to a mobile node.
>> 
>> Do you think this text is sufficient?  Don't you think that using 
>> IPv4 IPsec makes more sense?
> 
> => There is no such thing as "IPv4 IPsec". Yes I do think it's 
> sufficient.

Ok, I don't.  IPv4 IPsec is IPsec for IPv4.

>>> => Of course, but that attack is known for all NAT detection 
>>> schemes including IKE-based schemes. There is no free lunch with 
>>> NATs. If people deploy them, they suffer the consequences.
>> 
>> That's rhetoric, right?  Too easy to claim weaknesses in some 
>> protocol are due to another protocol.
> 
> => Huh? I didn't claim that. I said that this is a common problem. A 
> NAT is a MITM.

Well, most deployed NATs won't attack anyone, while most MiTMs will.

> NAT detection is about detecting a MITM. Of course, that MITM could
> be a NAT or an attacker.

There should be some mechanisms of distinguishing a temporary MiTM from
a NAT being there for years with same IPv4 public address.

Additionally, the simple mechanism of comparing v4 addresses in the
packet received by HA could be enhanced to mitigate the attack I've
described.  It is sufficient for the MN receiving the fake "NAT Detected
Option" to re-interrogate the HA about that.  This is more secure.

> But no one has a way of knowing that today.

I'm not suggesting to invent something nobody did.  Just to say that the
mechanism proposed in the draft is obviously insecure.  If enhancements
are not proposed then the threats should be acknowledged though.

> So my point is, NATs are bad and we can't get something out of
> nothing.

I somehow agree.

Alex

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



From mip6-bounces@ietf.org Tue Oct 25 15:25:22 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUUQE-00060K-Fs; Tue, 25 Oct 2005 15:25:22 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUUQD-00060C-KT
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 15:25:21 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14190
	for <mip6@ietf.org>; Tue, 25 Oct 2005 15:25:06 -0400 (EDT)
Received: from mail.flarion.com ([63.103.94.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUUdD-00070m-K3
	for mip6@ietf.org; Tue, 25 Oct 2005 15:38:48 -0400
Received: from ftmailserver.flariontech.com ([10.10.1.140]) by
	mail.flarion.com with Microsoft SMTPSVC(5.0.2195.6713);
	Tue, 25 Oct 2005 15:25:11 -0400
Content-Class: urn:content-classes:message
Subject: RE: [Mip6] Security Considerations section
	ofdraft-ietf-mip6-nemo-v4traversal-00.txt
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 25 Oct 2005 15:25:09 -0400
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
Message-ID: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCDB1@ftmailserver.flariontech.com>
Thread-Topic: [Mip6] Security Considerations section
	ofdraft-ietf-mip6-nemo-v4traversal-00.txt
Thread-Index: AcXZmR/bOswz4chxSOeDC5jF3p36bgAAFSYg
From: "Soliman, Hesham" <H.Soliman@flarion.com>
To: "Alexandru Petrescu" <alexandru.petrescu@motorola.com>
X-OriginalArrivalTime: 25 Oct 2005 19:25:11.0291 (UTC)
	FILETIME=[D132ACB0:01C5D999]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Content-Transfer-Encoding: quoted-printable
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org



 > >> Do you think this text is sufficient?  Don't you think that using=20
 > >> IPv4 IPsec makes more sense?
 > >=20
 > > =3D> There is no such thing as "IPv4 IPsec". Yes I do think it's=20
 > > sufficient.
 >=20
 > Ok, I don't.  IPv4 IPsec is IPsec for IPv4.

=3D> So please explain why or suggest improvements.

 > Well, most deployed NATs won't attack anyone, while most MiTMs will.
 >=20
 > > NAT detection is about detecting a MITM. Of course, that MITM could
 > > be a NAT or an attacker.
 >=20
 > There should be some mechanisms of distinguishing a=20
 > temporary MiTM from
 > a NAT being there for years with same IPv4 public address.

=3D> I'd love to know how to do that.

 > > But no one has a way of knowing that today.
 >=20
 > I'm not suggesting to invent something nobody did.  Just to=20
 > say that the
 > mechanism proposed in the draft is obviously insecure.  If=20
 > enhancements
 > are not proposed then the threats should be acknowledged though.

=3D> That we can do. It's probably best to reference RFC 3519 as it
has a more detailed analysis of the threats and an IAB statement
about the negative impacts of NAT traversal.

Hesham

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D
This email may contain confidential and privileged material for the sole =
use
 of the intended recipient.  Any review or distribution by others is =
strictly
 prohibited.  If you are not the intended recipient please contact the =
sender
 and delete all copies.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D


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



From mip6-bounces@ietf.org Tue Oct 25 15:25:25 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUUQH-00063k-Fk; Tue, 25 Oct 2005 15:25:25 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUUQA-0005xf-I9
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 15:25:22 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14185
	for <mip6@ietf.org>; Tue, 25 Oct 2005 15:25:04 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUUdA-00070c-Ee
	for mip6@ietf.org; Tue, 25 Oct 2005 15:38:45 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id j9PJOs221323; Tue, 25 Oct 2005 21:24:54 +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
	j9PJOtHE008854; Tue, 25 Oct 2005 21:24:55 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200510251924.j9PJOtHE008854@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: "Narayanan Vidya-CVN065" <vidya@motorola.com>
Subject: Re: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt 
In-reply-to: Your message of Tue, 25 Oct 2005 14:44:22 EDT.
	<0B40B6F9CB990B428819561A2A55613A1040ED@de01exm69.ds.mot.com> 
Date: Tue, 25 Oct 2005 21:24:55 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
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>,
	Petrescu Alexandru-AAP021 <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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   I'm trying to catch up with the plethora of emails here :) 
   
=> good luck (:-)

   Lets distinguish VRRP-based mechanisms from "load balancing" mechanisms
   - fundamentally, one aims at failover and the other aims at load
   balancing. Architecturally, these are different. 
   
   A few questions to ask here may be the following: 
   
   1. Are we working on failover mechanisms in the WG? 
   
=> yes, "Improving home agent reliability" is in the charter and
clearly something needed for deployment.

   2. Are we working on load balancing mechanisms in the WG? 
   
=> it is not explicitely in the charter.

   3. Do we expect a common architecture/solution to solve the two? 
   
=> I believe the answer is no because failover is far easier.

   If the answer to 3 is 'yes', then I think we are limited in the number
   of solutions to consider (and this, I believe, is likely to be a good
   thing). 
   
=> but a 'yes' to 3 can be an obstacle to find quickly good solutions
for failover...

Regards

Francis.Dupont@enst-bretagne.fr

PS: the right way is to get feedback from operators: the goal of the IETF
is not to produce X pages of junk specs per day, but to provide good
(i.e., fulfilling real requirements) specs to operators and customers.
At least it should be the goal...

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



From mip6-bounces@ietf.org Tue Oct 25 15:39:31 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUUdv-0003bw-B9; Tue, 25 Oct 2005 15:39:31 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUUdt-0003aE-KJ
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 15:39:29 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14894
	for <mip6@ietf.org>; Tue, 25 Oct 2005 15:39:15 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUUqu-0007Oz-NT
	for mip6@ietf.org; Tue, 25 Oct 2005 15:52:57 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id j9PJcs222964; Tue, 25 Oct 2005 21:38:54 +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
	j9PJcspQ008946; Tue, 25 Oct 2005 21:38:54 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200510251938.j9PJcspQ008946@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Alexandru Petrescu <alexandru.petrescu@motorola.com>
Subject: Re: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt 
In-reply-to: Your message of Tue, 25 Oct 2005 20:51:16 +0200.
	<435E7EA4.2070202@motorola.com> 
Date: Tue, 25 Oct 2005 21:38:54 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   >    If yes, that
   >    draft alone does not help for bootstrapping IMHO.  If DHAAD can be made
   >    to work with non-anycast addresses then DHAAD+MPD is a good idea to do
   >    bootstrapping simple (MPD is Mobile Prefix Discovery).
   >    
   > => I don't understand why MPD is for when you have HA discovery/assignment
   > (the mobile prefix is simply the prefix of the HA address)... I should
   > have missed something, for instance there is more than one MP?
   
=> I mean Mobile Prefix for MP.

   "MP" could be misinterpreted as "Mobile Prefix" which isn't.
   
=> it is.

   DHAAD doesn't provide a prefix length field in DHAAD Reply, so the MN
   can't know it.  MPD is the equivalent of local RS/RA for a MN that is
   away from home.
   
=> but in fact the prefix length is 64 bits so this is not enough
to explain the necessity of MPD.

   HA-Switch and DHAAD+MPD could also be used when the home link is
   re-numbered.

=> this is a very unlikely event.

Regards

Francis.Dupont@enst-bretagne.fr

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



From mip6-bounces@ietf.org Tue Oct 25 15:54:29 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUUsP-0008PW-T3; Tue, 25 Oct 2005 15:54:29 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUUsO-0008P4-41
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 15:54:28 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16337
	for <mip6@ietf.org>; Tue, 25 Oct 2005 15:54:13 -0400 (EDT)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUV5I-00088o-SR
	for mip6@ietf.org; Tue, 25 Oct 2005 16:07:55 -0400
Received: from il06exr01.mot.com (il06exr01.mot.com [129.188.137.131])
	by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id j9PK6AtZ023506
	for <mip6@ietf.org>; Tue, 25 Oct 2005 13:06:10 -0700 (MST)
Received: from de01exm69.ds.mot.com (de01exm69.am.mot.com [10.176.8.25])
	by il06exr01.mot.com (8.13.1/8.13.0) with ESMTP id j9PK4A8K024304
	for <mip6@ietf.org>; Tue, 25 Oct 2005 15:04:10 -0500 (CDT)
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] draft-dupont-mip6-dhaadharmful-00.txt 
Date: Tue, 25 Oct 2005 15:54:06 -0400
Message-ID: <0B40B6F9CB990B428819561A2A55613A10416E@de01exm69.ds.mot.com>
Thread-Topic: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt 
Thread-Index: AcXZmden90FGxjanR6GWQ3RjjXy6dgAA1E1A
From: "Narayanan Vidya-CVN065" <vidya@motorola.com>
To: <Francis.Dupont@enst-bretagne.fr>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Content-Transfer-Encoding: quoted-printable
Cc: mip6@ietf.org, Kilian Weniger <Kilian.Weniger@eu.panasonic.com>,
	James Kempf <Kempf@docomolabs-usa.com>,
	Petrescu Alexandru-AAP021 <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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

>   =20
>    1. Are we working on failover mechanisms in the WG?=20
>   =20
> =3D> yes, "Improving home agent reliability" is in the charter=20
> and clearly something needed for deployment.
>=20

Yes, it seems to be in the charter. But, I recall that the chairs were
questioning this in Paris - there seemed to be some feeling that this
can be vendor specific for the moment and it was agreed that we would
discuss on the ML to decide if it is critical enough to be looked at in
the WG right now. I might have missed the discussion - was there a
consensus on this?=20

Anyway, I would agree that this is important.=20


>    2. Are we working on load balancing mechanisms in the WG?=20
>   =20
> =3D> it is not explicitely in the charter.

But, there certainly is a lot of discussion on this topic on the ML :)=20

>=20
>    3. Do we expect a common architecture/solution to solve the two?=20
>   =20
> =3D> I believe the answer is no because failover is far easier.
>=20
>    If the answer to 3 is 'yes', then I think we are limited=20
> in the number
>    of solutions to consider (and this, I believe, is likely=20
> to be a good
>    thing).=20
>   =20
> =3D> but a 'yes' to 3 can be an obstacle to find quickly good=20
> solutions for failover...


Agreed. But, looking at the number of discussions that are hinging on
load balancing, we must either consciously keep them separate or combine
them. Combining them is good from an architectural standpoint, but, as
you say, it is likely to delay quick solutions for failover.=20

>=20
> PS: the right way is to get feedback from operators: the goal=20
> of the IETF is not to produce X pages of junk specs per day,=20
> but to provide good (i.e., fulfilling real requirements)=20
> specs to operators and customers.
> At least it should be the goal...
>=20

I second that :)=20

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



From mip6-bounces@ietf.org Tue Oct 25 15:54:47 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUUsh-0000AQ-T5; Tue, 25 Oct 2005 15:54:47 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUUse-00008Y-Th
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 15:54:45 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16406
	for <mip6@ietf.org>; Tue, 25 Oct 2005 15:54:30 -0400 (EDT)
Received: from motgate4.mot.com ([144.189.100.102])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUV5d-0008AV-Nc
	for mip6@ietf.org; Tue, 25 Oct 2005 16:08:12 -0400
Received: from az33exr04.mot.com (az33exr04.mot.com [10.64.251.234])
	by motgate4.mot.com (8.12.11/Motgate4) with ESMTP id j9PK3nuj019610;
	Tue, 25 Oct 2005 13:03:53 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by az33exr04.mot.com (8.13.1/8.13.0) with ESMTP id j9PK1Fjw011129;
	Tue, 25 Oct 2005 15:01:16 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id 102FA865980; Tue, 25 Oct 2005 21:54:29 +0200 (CEST)
Message-ID: <435E8D74.8090703@motorola.com>
Date: Tue, 25 Oct 2005 21:54:28 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: "Soliman, Hesham" <H.Soliman@flarion.com>
Subject: Re: [Mip6] I-D ACTION:draft-ietf-mip6-nemo-v4traversal-00.txt
References: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCDAF@ftmailserver.flariontech.com>
In-Reply-To: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCDAF@ftmailserver.flariontech.com>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 36c793b20164cfe75332aa66ddb21196
Content-Transfer-Encoding: 7bit
Cc: mip6@ietf.org, Keiichi SHIMA <keiichi@iijlab.net>,
	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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Soliman, Hesham wrote:
>>> => MIPv4 does not do it any better, whatever your definition of 
>>> "better" might be. It does it differently. There is less 
>>> encapsulation in the case where the MN is using an FA and
>> no NATs are
>>> located between the MN and the HA.
>> 
>> The fact that FAs or NATs are present don't influence MR having to
>>  encapsulate packets from a v4 LFN.  Whatever MR connects to - v4
>> or v6, FA or NAT - the MR must encapsulate packets from LFN, for
>> NEMO reasons.
> 
> => You're discussing a separate topic here. I didn't make any 
> comments about this. Are you talking about MIPv4?

Yes, I am talking about MIPv4.

> If so, then there is no encapsulation. MIPv4 assumes that it is 
> possible for the MN to use it's home address in a foreign network and
>  that ingress filtering will not drop the packet. It also allows the 
> FA to reverse tunnel. If you choose reverse tunnelling then I don't 
> understand where the extra overhead in encapsulation is.

I agree.  The extra overhead may appear if a DSMIPv6 MR is used to give
v4 access to LFNs, instead of MIP4.  I don't think DSMIPv6 draft tries
to give v4 access to LFNs, because it does not encode MNPs in its
messaging, which is a good thing.

>> If MR connects to a v4 network and MIP6 is used (no MIP4) then MR 
>> encapsulates LFN IPv4 packets in IPv6 and then again in IPv4.
> 
> => No! Please read the draft again. The draft says: - IPv6 in IPv4 
> (foreign network using public IPv4 addresses only) - IPv6 in UDP/IPv4
>  (if a NAT is detected).

Ok, I read.  I agree.

>> YEs, and most large scale deployments use Firewalls coupled to NATs
>>  and there's no large scale IPv6 access network deployments for 
>> wireless mobiles.  Hence the suggestion to move focus from v4-LFN 
>> to Firewall traversal.
> 
> => I disagree. FW traversal sounds like port scanning. We're not in 
> the business of standardising attacks on a closed network.

We aren't, so call it UDP path discovery instead of port scanning.

> What do you do if a FW disables the mobility header?? Should we 
> encapsulate MIPv6 in HTTP?

Well, people could do whatever they want.  If attacks are going to
happen because of the Mobility Header then that's sure being disabled.

About encapsulating MIP6 over HTTP.  People who absolutely want to run
IPv6 on their nodes today go to encapsulating v6 in many things and it
works.

But I agree there's only so much it can be done about some NAT/FW
traversal scheme.

>>> For those scenarios there is no difference in encapsulation.
>> 
>> See above where I explain that MIP6 MR giving IPv4 LFN 
>> unnecessarily encapsulates in v6 when connecting to a v4 network.
> 
> => You're objecting to something we never did. I agree it's not 
> needed! We don't do that.

I think I agree I'm objecting to something I may have misinterpreted.
So I suggest that since this draft talks about NEMO at several places to
mention that this draft does not offer enhancements to NEMOv6 MR to give
IPv4 access to LFNs.

Let me explain:  the abstract says
      "The current Mobile IPv6 and NEMO specification support only IPv6.
       Hence, this specification extends those standards to allow the
       registration of IPv4 addresses and prefixes, respectively"

Why would one need to register IPv4 addresses and prefixes with MIP6 and
not with MIP4?

This specification should provide something to offer IPv6 permanent Home
Addresses to a MIP6 node connecting to a v4-only network, no?  I don't
think there is any need to provide IPv4 Home Addresses to MN with MIP6
(when MN connects to a v4 network).

> => MIPv6 was not chosen over MIPv4. We're standardising a MIPv6 
> solution in the MIP6 WG and I'm going to ask the MIP4 WG to do the 
> same thing for MIPv4. I don't know why you assume we *chose* MIPv6 
> over MIPv4.

Right...

>> I am deeply aware of the following problem: a MIPv6 MH connecting 
>> to a NAT-v4-only network can't normally use its permanent IPv6 Home
>>  Address.
> 
>> I am not aware of a problem where an IPv4 LFN with an IPv6 MR 
>> connecting to a v4-only network needs to communicate.  The problem 
>> statement may mention it though, but I don't find it to be a 
>> problem other than on paper.
> 
> => Do you assume that all hosts will use IPv6 applications and only 
> communicate with other IPv6 hosts?

Right, some applications are still v4.

> If the answer is no, then you need to provide them a stable IPv4 
> address (read:home address). And you need to provide mobility for
> that address. This is what the draft does.

Yes, and please provide it with MIP4, not with v4 MIP6 enhancements.
MIP4 does it better when it comes to IPv4 Home Addresses, no?

Alex

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



From mip6-bounces@ietf.org Tue Oct 25 15:58:04 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUUvs-0001eD-O5; Tue, 25 Oct 2005 15:58:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUUvq-0001dp-TW
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 15:58:02 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17385
	for <mip6@ietf.org>; Tue, 25 Oct 2005 15:57:47 -0400 (EDT)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUV8q-00006v-Op
	for mip6@ietf.org; Tue, 25 Oct 2005 16:11:30 -0400
Received: from il06exr01.mot.com (il06exr01.mot.com [129.188.137.131])
	by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id j9PK9sVX024094;
	Tue, 25 Oct 2005 13:09:54 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by il06exr01.mot.com (8.13.1/8.13.0) with ESMTP id j9PK7rQk025663;
	Tue, 25 Oct 2005 15:07:54 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id 8451A865980; Tue, 25 Oct 2005 21:57:58 +0200 (CEST)
Message-ID: <435E8E46.9090709@motorola.com>
Date: Tue, 25 Oct 2005 21:57:58 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: "Soliman, Hesham" <H.Soliman@flarion.com>
Subject: Re: [Mip6] Security Considerations section
	ofdraft-ietf-mip6-nemo-v4traversal-00.txt
References: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCDB1@ftmailserver.flariontech.com>
In-Reply-To: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCDB1@ftmailserver.flariontech.com>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Content-Transfer-Encoding: 7bit
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Soliman, Hesham wrote:
>>>> Do you think this text is sufficient?  Don't you think that
>>>> using IPv4 IPsec makes more sense?
>>> 
>>> => There is no such thing as "IPv4 IPsec". Yes I do think it's 
>>> sufficient.
>> 
>> Ok, I don't.  IPv4 IPsec is IPsec for IPv4.
> 
> => So please explain why or suggest improvements.

Here's why: an MN connecting to a v4-only network could use MIP4 and
IPsec to maintain permanent reachability at an IPv4 Home Address.  Does
this make sense?  Should I suggest text about it?

>>> NAT detection is about detecting a MITM. Of course, that MITM
>>> could be a NAT or an attacker.
>> 
>> There should be some mechanisms of distinguishing a temporary MiTM
>> from a NAT being there for years with same IPv4 public address.
> 
> => I'd love to know how to do that.

Probe it daily and draw conclusions after 6 months.

>>> But no one has a way of knowing that today.
>> 
>> I'm not suggesting to invent something nobody did.  Just to say
>> that the mechanism proposed in the draft is obviously insecure.  If
>>  enhancements are not proposed then the threats should be
>> acknowledged though.
> 
> => That we can do. It's probably best to reference RFC 3519 as it has
> a more detailed analysis of the threats and an IAB statement about
> the negative impacts of NAT traversal.

Yes, please reference RFC 3519.

Alex

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



From mip6-bounces@ietf.org Tue Oct 25 16:25:07 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUVC6-0003ZN-P2; Tue, 25 Oct 2005 16:14:50 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUVC5-0003Z8-1a
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 16:14:49 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24505
	for <mip6@ietf.org>; Tue, 25 Oct 2005 16:14:34 -0400 (EDT)
Received: from mail.flarion.com ([63.103.94.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUVP5-0002mi-Ce
	for mip6@ietf.org; Tue, 25 Oct 2005 16:28:16 -0400
Received: from ftmailserver.flariontech.com ([10.10.1.140]) by
	mail.flarion.com with Microsoft SMTPSVC(5.0.2195.6713);
	Tue, 25 Oct 2005 16:14:37 -0400
Content-Class: urn:content-classes:message
Subject: RE: [Mip6] I-D ACTION:draft-ietf-mip6-nemo-v4traversal-00.txt
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 25 Oct 2005 16:14:36 -0400
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
Message-ID: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCDB2@ftmailserver.flariontech.com>
Thread-Topic: [Mip6] I-D ACTION:draft-ietf-mip6-nemo-v4traversal-00.txt
Thread-Index: AcXZne2DO4QOpWs5RQGSc7y3O+DyKgAAkm2g
From: "Soliman, Hesham" <H.Soliman@flarion.com>
To: "Alexandru Petrescu" <alexandru.petrescu@motorola.com>
X-OriginalArrivalTime: 25 Oct 2005 20:14:37.0953 (UTC)
	FILETIME=[B9775F10:01C5D9A0]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1
Content-Transfer-Encoding: quoted-printable
Cc: mip6@ietf.org, Keiichi SHIMA <keiichi@iijlab.net>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org





 >=20
 > I agree.  The extra overhead may appear if a DSMIPv6 MR is=20
 > used to give
 > v4 access to LFNs, instead of MIP4.=20

=3D> I can't see hoe this could possibly be true.

  I don't think DSMIPv6=20
 > draft tries
 > to give v4 access to LFNs, because it does not encode MNPs in its
 > messaging, which is a good thing.

=3D> It does. The address/prefix format allows an MR to request an=20
IPv4 prefix.

 > > =3D> I disagree. FW traversal sounds like port scanning.=20
 > We're not in=20
 > > the business of standardising attacks on a closed network.
 >=20
 > We aren't, so call it UDP path discovery instead of port scanning.

=3D> It doesn't matter what you call it, it's still port scanning.
IETF should not be trying to penetrate closed networks despite=20
the administrator.

 > > =3D> You're objecting to something we never did. I agree it's not=20
 > > needed! We don't do that.
 >=20
 > I think I agree I'm objecting to something I may have misinterpreted.
 > So I suggest that since this draft talks about NEMO at=20
 > several places to
 > mention that this draft does not offer enhancements to=20
 > NEMOv6 MR to give
 > IPv4 access to LFNs.
 >=20
 > Let me explain:  the abstract says
 >       "The current Mobile IPv6 and NEMO specification=20
 > support only IPv6.
 >        Hence, this specification extends those standards to allow the
 >        registration of IPv4 addresses and prefixes, respectively"
 >=20
 > Why would one need to register IPv4 addresses and prefixes=20
 > with MIP6 and
 > not with MIP4?

=3D> Please read the problem statement.

 >=20
 > Right, some applications are still v4.
 >=20
 > > If the answer is no, then you need to provide them a stable IPv4=20
 > > address (read:home address). And you need to provide mobility for
 > > that address. This is what the draft does.
 >=20
 > Yes, and please provide it with MIP4, not with v4 MIP6 enhancements.
 > MIP4 does it better when it comes to IPv4 Home Addresses, no?

=3D> Please read the problem statement, otherwise it's not useful to =
continue
this discussion.=20

Hesham

 >=20
 > Alex
 >=20

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D
This email may contain confidential and privileged material for the sole =
use
 of the intended recipient.  Any review or distribution by others is =
strictly
 prohibited.  If you are not the intended recipient please contact the =
sender
 and delete all copies.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D


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



From mip6-bounces@ietf.org Tue Oct 25 16:25:08 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUVCl-0003dO-Lc; Tue, 25 Oct 2005 16:15:31 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUVCf-0003cz-RS
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 16:15:30 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24547
	for <mip6@ietf.org>; Tue, 25 Oct 2005 16:15:11 -0400 (EDT)
Received: from mail.flarion.com ([63.103.94.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUVPg-0002o1-Fu
	for mip6@ietf.org; Tue, 25 Oct 2005 16:28:53 -0400
Received: from ftmailserver.flariontech.com ([10.10.1.140]) by
	mail.flarion.com with Microsoft SMTPSVC(5.0.2195.6713);
	Tue, 25 Oct 2005 16:15:15 -0400
Content-Class: urn:content-classes:message
Subject: RE: [Mip6] Security Considerations section
	ofdraft-ietf-mip6-nemo-v4traversal-00.txt
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 25 Oct 2005 16:15:14 -0400
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
Message-ID: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCDB3@ftmailserver.flariontech.com>
Thread-Topic: [Mip6] Security Considerations section
	ofdraft-ietf-mip6-nemo-v4traversal-00.txt
Thread-Index: AcXZnmZCP+7qckniRiqC6Lbv4flaHgAAlmkw
From: "Soliman, Hesham" <H.Soliman@flarion.com>
To: "Alexandru Petrescu" <alexandru.petrescu@motorola.com>
X-OriginalArrivalTime: 25 Oct 2005 20:15:15.0875 (UTC)
	FILETIME=[D011CF30:01C5D9A0]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Content-Transfer-Encoding: quoted-printable
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

=20
 > > =3D> So please explain why or suggest improvements.
 >=20
 > Here's why: an MN connecting to a v4-only network could use MIP4 and
 > IPsec to maintain permanent reachability at an IPv4 Home=20
 > Address.  Does
 > this make sense?  Should I suggest text about it?

=3D> No. Please read the problem statement.=20

Hesham

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D
This email may contain confidential and privileged material for the sole =
use
 of the intended recipient.  Any review or distribution by others is =
strictly
 prohibited.  If you are not the intended recipient please contact the =
sender
 and delete all copies.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D


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



From mip6-bounces@ietf.org Tue Oct 25 16:25:10 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUVEp-0004MR-Ek; Tue, 25 Oct 2005 16:17:39 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUVEo-0004MB-JU
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 16:17:38 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24809
	for <mip6@ietf.org>; Tue, 25 Oct 2005 16:17:23 -0400 (EDT)
Received: from motgate2.mot.com ([144.189.100.101])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUVRl-0002uG-I1
	for mip6@ietf.org; Tue, 25 Oct 2005 16:31:05 -0400
Received: from az33exr01.mot.com (az33exr01.mot.com [10.64.251.231])
	by motgate2.mot.com (8.12.11/Motgate2) with ESMTP id j9PKWQe0019151;
	Tue, 25 Oct 2005 13:32:31 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by az33exr01.mot.com (8.13.1/8.13.0) with ESMTP id j9PKTbfW003669;
	Tue, 25 Oct 2005 15:29:39 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id A6EE0865980; Tue, 25 Oct 2005 22:17:13 +0200 (CEST)
Message-ID: <435E92C9.5030206@motorola.com>
Date: Tue, 25 Oct 2005 22:17:13 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: "Soliman, Hesham" <H.Soliman@flarion.com>
Subject: Re: [Mip6] I-D ACTION:draft-ietf-mip6-nemo-v4traversal-00.txt
References: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCDAF@ftmailserver.flariontech.com>
In-Reply-To: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCDAF@ftmailserver.flariontech.com>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Content-Transfer-Encoding: 7bit
Cc: mip6@ietf.org, Keiichi SHIMA <keiichi@iijlab.net>,
	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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Soliman, Hesham wrote:
>> Yes, I agree.  It goes further than just that though, at least 
>> because it suggests offering IPv4 access to LFNs, without real MIP4
>>  support.
> 
> => That's the *goal* of the draft. We discussed this in IETF when the
>  scenarios and requirements were presented. No one disagreed with 
> this requirement.

I was there at the last meeting and I disagreed at the microphone about
this solution offering v4 access to LFNs.  That's my rememberings.
Whether that gets through or not is another issue.

Anyways, not between me and you to agree, right?  It's a WG.

Alex


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



From mip6-bounces@ietf.org Tue Oct 25 16:35:10 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUVVm-0007WH-Kg; Tue, 25 Oct 2005 16:35:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUVVj-0007VR-GX
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 16:35:08 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02012
	for <mip6@ietf.org>; Tue, 25 Oct 2005 16:34:52 -0400 (EDT)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUVih-0005cb-AQ
	for mip6@ietf.org; Tue, 25 Oct 2005 16:48:34 -0400
Received: from il06exr01.mot.com (il06exr01.mot.com [129.188.137.131])
	by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id j9PKkp9D029958;
	Tue, 25 Oct 2005 13:46:56 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by il06exr01.mot.com (8.13.1/8.13.0) with ESMTP id j9PKio9c010828;
	Tue, 25 Oct 2005 15:44:51 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id 370A9865980; Tue, 25 Oct 2005 22:34:55 +0200 (CEST)
Message-ID: <435E96EF.3020000@motorola.com>
Date: Tue, 25 Oct 2005 22:34:55 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: "Soliman, Hesham" <H.Soliman@flarion.com>
Subject: Re: [Mip6] I-D ACTION:draft-ietf-mip6-nemo-v4traversal-00.txt
References: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCDB2@ftmailserver.flariontech.com>
In-Reply-To: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCDB2@ftmailserver.flariontech.com>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
Content-Transfer-Encoding: 7bit
Cc: mip6@ietf.org, Keiichi SHIMA <keiichi@iijlab.net>,
	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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

[snipping some stuff for whatever reason]
Soliman, Hesham wrote:
>> I don't think DSMIPv6 draft tries to give v4 access to LFNs, 
>> because it does not encode MNPs in its messaging, which is a good 
>> thing.
> 
> => It does. The address/prefix format allows an MR to request an IPv4
>  prefix.

Well, ok.  That was precisely what I was trying to avoid.

Usually IPv4 prefixes are requested with DHCP-PD.

IPv4 prefixes may be registered with a Registration Request too.

Why using an IPv6 BU for that, especially when connected to a v4-only
network?  My claim is that there's no advantage in doing that.

>> We aren't, so call it UDP path discovery instead of port scanning.
> 
> => It doesn't matter what you call it, it's still port scanning. IETF
>  should not be trying to penetrate closed networks despite the 
> administrator.

How about non-intrusive UDP path detection then?

>>> => You're objecting to something we never did. I agree it's not 
>>> needed! We don't do that.
>> 
>> I think I agree I'm objecting to something I may have 
>> misinterpreted. So I suggest that since this draft talks about NEMO
>>  at several places to mention that this draft does not offer 
>> enhancements to NEMOv6 MR to give IPv4 access to LFNs.
>> 
>> Let me explain:  the abstract says "The current Mobile IPv6 and 
>> NEMO specification support only IPv6. Hence, this specification 
>> extends those standards to allow the registration of IPv4 addresses
>>  and prefixes, respectively"
>> 
>> Why would one need to register IPv4 addresses and prefixes with 
>> MIP6 and not with MIP4?
> 
> => Please read the problem statement.

The problem statement mostly says "running MIP4 and MIP6 simultaneously
is a burden" and the DSMIPv6 solution looks nothing short of a bigger
burden.

Would you please summarize your thoughts in a few lines about why not
using MIPv4 for v4 Home Addresses?  If it's not possible to have a 3
liner on that for a 30seconds elevator speech I don't think the problem
is valid.

A good problem shows that something breaks, while the only thing
mentioned in the Problem Statement that may seem to break is the following:
> A final point to consider is that even if both mobility protocols are
>  supported by a mobile node seamless connectivity would not in fact
> be guarantied since that also depends on the IPv4/IPv6 capabilities
> of the networks the mobile is visiting i.e.: a dual stack node 
> attempting to connect via a IPv4 only network would not be able to 
> maintain connectivity of its IPv6 applications and vice versa.

which is basically presenting an apparent paradox: if both MIP6 and MIP4
are run then no seamless IPv4 and IPv6 connectivity, because an
application can't seamlessly switch its stream from v4 to v6.  Well, an
application seamlessly switching its streaming from a v4 socket to a v6
socket is something not in the field of MIP I believe, and could be
achieved without MIP techniques.

If you wish, we could discuss the above paragraph separately.  My
conclusion about it is that it addresses a problem that is not in the
scope of MIP itself, or largely surpasses it.

>> Yes, and please provide it with MIP4, not with v4 MIP6 
>> enhancements. MIP4 does it better when it comes to IPv4 Home 
>> Addresses, no?
> 
> => Please read the problem statement, otherwise it's not useful to 
> continue this discussion.

I've just read.

The problem statement draft is not the problem I know.

I guess you won't agree to the relevance of the problem I know (MIPv6
MN, v6 app, connect to v4-only access network), so let me also say I
don't agree with the problem statement.

Alex

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



From mip6-bounces@ietf.org Tue Oct 25 16:42:20 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUVci-0004N1-3a; Tue, 25 Oct 2005 16:42:20 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUVcg-0004Mj-Nq
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 16:42:18 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05300
	for <mip6@ietf.org>; Tue, 25 Oct 2005 16:42:03 -0400 (EDT)
Received: from mail.flarion.com ([63.103.94.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUVpf-0006rS-5d
	for mip6@ietf.org; Tue, 25 Oct 2005 16:55:46 -0400
Received: from ftmailserver.flariontech.com ([10.10.1.140]) by
	mail.flarion.com with Microsoft SMTPSVC(5.0.2195.6713);
	Tue, 25 Oct 2005 16:42:04 -0400
Content-Class: urn:content-classes:message
Subject: RE: [Mip6] I-D ACTION:draft-ietf-mip6-nemo-v4traversal-00.txt
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 25 Oct 2005 16:42:02 -0400
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
Message-ID: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCDB6@ftmailserver.flariontech.com>
Thread-Topic: [Mip6] I-D ACTION:draft-ietf-mip6-nemo-v4traversal-00.txt
Thread-Index: AcXZo5K1rupoFqBYSn230Lw9zY9LhQAADbyQ
From: "Soliman, Hesham" <H.Soliman@flarion.com>
To: "Alexandru Petrescu" <alexandru.petrescu@motorola.com>
X-OriginalArrivalTime: 25 Oct 2005 20:42:04.0250 (UTC)
	FILETIME=[8EBC5BA0:01C5D9A4]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Content-Transfer-Encoding: quoted-printable
Cc: mip6@ietf.org, Keiichi SHIMA <keiichi@iijlab.net>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org



 > > =3D> Please read the problem statement.
 >=20
 > The problem statement mostly says "running MIP4 and MIP6=20
 > simultaneously
 > is a burden" and the DSMIPv6 solution looks nothing short of a bigger
 > burden.
 >=20
 > Would you please summarize your thoughts in a few lines about why not
 > using MIPv4 for v4 Home Addresses?  If it's not possible to have a 3
 > liner on that for a 30seconds elevator speech I don't think=20
 > the problem
 > is valid.

=3D> Ok, then you don't think the problem is valid. I've summarized all
my thoughts in the problem statement. If you don't want to read it
that's too bad. If you have comments on it (like the one below)
then I'll be happy to discuss them.

 > A good problem shows that something breaks, while the only thing
 > mentioned in the Problem Statement that may seem to break is=20
 > the following:
 > > A final point to consider is that even if both mobility=20
 > protocols are
 > >  supported by a mobile node seamless connectivity would not in fact
 > > be guarantied since that also depends on the IPv4/IPv6 capabilities
 > > of the networks the mobile is visiting i.e.: a dual stack node=20
 > > attempting to connect via a IPv4 only network would not be able to=20
 > > maintain connectivity of its IPv6 applications and vice versa.
 >=20
 > which is basically presenting an apparent paradox: if both=20
 > MIP6 and MIP4
 > are run then no seamless IPv4 and IPv6 connectivity, because an
 > application can't seamlessly switch its stream from v4 to=20
 > v6.  Well, an
 > application seamlessly switching its streaming from a v4=20
 > socket to a v6
 > socket is something not in the field of MIP I believe, and could be
 > achieved without MIP techniques.

=3D> I'm afraid you didn't understand the draft. We are working under
the premise that MIP is used to manage mobility. Other techniques
are outside the scope of this draft and this mailing list.=20

Based on that, we state that if you have an IPv4 home address and=20
you appear in an IPv6-only network you won't be able to maintain
connections using MIPv4 only. Similarly, if you have an IPv6
home address and you appear in an IPv4-only network, then you
won't be able to maintain connectivity to that address using=20
MIPv4 as specified today.=20

The same goes for CoAs.

 > I've just read.
 >=20
 > The problem statement draft is not the problem I know.
 >=20
 > I guess you won't agree to the relevance of the problem I know (MIPv6
 > MN, v6 app, connect to v4-only access network), so let me also say I
 > don't agree with the problem statement.

=3D> ok.=20

Hesham

 >=20
 > Alex
 >=20

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D
This email may contain confidential and privileged material for the sole =
use
 of the intended recipient.  Any review or distribution by others is =
strictly
 prohibited.  If you are not the intended recipient please contact the =
sender
 and delete all copies.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D


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



From mip6-bounces@ietf.org Tue Oct 25 16:47:29 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUVhg-0008Eh-T8; Tue, 25 Oct 2005 16:47:28 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUVha-0008Be-BU
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 16:47:27 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA08059
	for <mip6@ietf.org>; Tue, 25 Oct 2005 16:47:06 -0400 (EDT)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUVuZ-0007uo-Es
	for mip6@ietf.org; Tue, 25 Oct 2005 17:00:49 -0400
Received: from il06exr03.mot.com (il06exr03.mot.com [129.188.137.133])
	by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id j9PKx5kO001961;
	Tue, 25 Oct 2005 13:59:05 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by il06exr03.mot.com (8.13.1/8.13.0) with ESMTP id j9PKvCqp029918;
	Tue, 25 Oct 2005 15:57:13 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id B5369865980; Tue, 25 Oct 2005 22:47:08 +0200 (CEST)
Message-ID: <435E99CC.3090309@motorola.com>
Date: Tue, 25 Oct 2005 22:47:08 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
Subject: Re: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
References: <200510251938.j9PJcspQ008946@givry.rennes.enst-bretagne.fr>
In-Reply-To: <200510251938.j9PJcspQ008946@givry.rennes.enst-bretagne.fr>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Content-Transfer-Encoding: 7bit
Cc: James Kempf <Kempf@docomolabs-usa.com>, 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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Francis Dupont wrote:
>  In your previous mail you wrote:
> 
>    >    If yes, that
>    >    draft alone does not help for bootstrapping IMHO.  If DHAAD can be made
>    >    to work with non-anycast addresses then DHAAD+MPD is a good idea to do
>    >    bootstrapping simple (MPD is Mobile Prefix Discovery).
>    >    
>    > => I don't understand why MPD is for when you have HA discovery/assignment
>    > (the mobile prefix is simply the prefix of the HA address)... I should
>    > have missed something, for instance there is more than one MP?
>    
> => I mean Mobile Prefix for MP.
> 
>    "MP" could be misinterpreted as "Mobile Prefix" which isn't.
>    
> => it is.

Well, the Prefix is the prefix of a fixed home link, advertised in fixed
RAs sent by its routers.  A "Mobile Prefix" would be more like the
prefix of the Mobile Network Prefix which moves together with the moving
network, I think.

But ok, it's also like a "Mobile Network" moves or is fixed depending
who one talks to.

>    DHAAD doesn't provide a prefix length field in DHAAD Reply, so the MN
>    can't know it.  MPD is the equivalent of local RS/RA for a MN that is
>    away from home.
>    
> => but in fact the prefix length is 64 bits so this is not enough
> to explain the necessity of MPD.

Well, ok.  When plens are shorter than 64bits please pad with 0s between
prefix and IID, and don't use these zeros as network identifier.

>    HA-Switch and DHAAD+MPD could also be used when the home link is
>    re-numbered.
> 
> => this is a very unlikely event.

Well, ok, a discussion could be held about what are the minimal parts of
MIP6 which are really necessary and in what contexts.

Alex

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



From mip6-bounces@ietf.org Tue Oct 25 16:57:57 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUVrp-0008VV-7A; Tue, 25 Oct 2005 16:57:57 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUVrn-0008VL-TV
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 16:57:55 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12915
	for <mip6@ietf.org>; Tue, 25 Oct 2005 16:57:40 -0400 (EDT)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUW4p-0001M7-A7
	for mip6@ietf.org; Tue, 25 Oct 2005 17:11:23 -0400
Received: from il06exr02.mot.com (il06exr02.mot.com [129.188.137.132])
	by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id j9PL9iNq003702;
	Tue, 25 Oct 2005 14:09:44 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by il06exr02.mot.com (8.13.1/8.13.0) with ESMTP id j9PL6P6Z022766;
	Tue, 25 Oct 2005 16:06:26 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id A6FA8865980; Tue, 25 Oct 2005 22:57:47 +0200 (CEST)
Message-ID: <435E9C4B.2050607@motorola.com>
Date: Tue, 25 Oct 2005 22:57:47 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: "Soliman, Hesham" <H.Soliman@flarion.com>
Subject: Re: [Mip6] I-D ACTION:draft-ietf-mip6-nemo-v4traversal-00.txt
References: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCDB6@ftmailserver.flariontech.com>
In-Reply-To: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCDB6@ftmailserver.flariontech.com>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
Content-Transfer-Encoding: 7bit
Cc: mip6@ietf.org, Keiichi SHIMA <keiichi@iijlab.net>,
	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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Soliman, Hesham wrote:

> 
>>> => Please read the problem statement.
>> 
>> The problem statement mostly says "running MIP4 and MIP6 
>> simultaneously is a burden" and the DSMIPv6 solution looks nothing
>>  short of a bigger burden.
>> 
>> Would you please summarize your thoughts in a few lines about why 
>> not using MIPv4 for v4 Home Addresses?  If it's not possible to 
>> have a 3 liner on that for a 30seconds elevator speech I don't 
>> think the problem is valid.
> 
> => Ok, then you don't think the problem is valid. I've summarized all
>  my thoughts in the problem statement. If you don't want to read it 
> that's too bad. If you have comments on it (like the one below) then
>  I'll be happy to discuss them.

Good then.

>> A good problem shows that something breaks, while the only thing 
>> mentioned in the Problem Statement that may seem to break is the 
>> following:
>>> A final point to consider is that even if both mobility
>> protocols are
>>> supported by a mobile node seamless connectivity would not in 
>>> fact be guarantied since that also depends on the IPv4/IPv6 
>>> capabilities of the networks the mobile is visiting i.e.: a dual
>>>  stack node attempting to connect via a IPv4 only network would 
>>> not be able to maintain connectivity of its IPv6 applications and
>>>  vice versa.
>> 
>> which is basically presenting an apparent paradox: if both MIP6 and
>>  MIP4 are run then no seamless IPv4 and IPv6 connectivity, because
>>  an application can't seamlessly switch its stream from v4 to v6. 
>> Well, an application seamlessly switching its streaming from a v4 
>> socket to a v6 socket is something not in the field of MIP I 
>> believe, and could be achieved without MIP techniques.
> 
> => I'm afraid you didn't understand the draft. We are working under 
> the premise that MIP is used to manage mobility. Other techniques are
>  outside the scope of this draft and this mailing list.
> 
> Based on that, we state that if you have an IPv4 home address and you
>  appear in an IPv6-only network you won't be able to maintain 
> connections using MIPv4 only.

Absolutely.  Note though that the urgency of a solution for this
scenario is much lower than the urgency of a solution for a v6 MN
connecting to a v4-only network, simply because there are much more
v4-only wireless access networks (than v6), no?

> Similarly, if you have an IPv6 home address and you appear in an 
> IPv4-only network, then you won't be able to maintain connectivity to
>  that address using MIPv4 as specified today.

Absolutely.  And this scenario is more urgent to be solved.

And the two scenarios lead to the immediate question: why not running
both MIP4 and MIP6 on the mobile, so that when it connects to the
v4-only access it uses MIP4 and when it connects to the v6-only access
it uses MIP6.  This would not solve the second scenario you've described
above, though, but it would solve the problem of "MIP6 node on v6
network" and the problem of "MIP4 node on v4 network".

I hope the answer is not 'because it is a burden'.  Running both MIP4
and MIP6 on a same MN should break something, which we could identify
and try to solve.  Currently it doesn't break anything, no?

Alex


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



From mip6-bounces@ietf.org Tue Oct 25 17:17:15 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUWAV-0004XL-AL; Tue, 25 Oct 2005 17:17:15 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUWAT-0004Sg-15
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 17:17:13 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15292
	for <mip6@ietf.org>; Tue, 25 Oct 2005 17:16:57 -0400 (EDT)
Received: from mail.flarion.com ([63.103.94.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUWNV-0002NE-4r
	for mip6@ietf.org; Tue, 25 Oct 2005 17:30:41 -0400
Received: from ftmailserver.flariontech.com ([10.10.1.140]) by
	mail.flarion.com with Microsoft SMTPSVC(5.0.2195.6713);
	Tue, 25 Oct 2005 17:16:58 -0400
Content-Class: urn:content-classes:message
Subject: RE: [Mip6] I-D ACTION:draft-ietf-mip6-nemo-v4traversal-00.txt
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 25 Oct 2005 17:16:57 -0400
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
Message-ID: <A11736FE943F1A408F8BBB1B9F5FE8AD17DE48@ftmailserver.flariontech.com>
Thread-Topic: [Mip6] I-D ACTION:draft-ietf-mip6-nemo-v4traversal-00.txt
Thread-Index: AcXZpsHXBOh5qx/gSL6Hsuk4LRH8zwAAbIew
From: "Soliman, Hesham" <H.Soliman@flarion.com>
To: "Alexandru Petrescu" <alexandru.petrescu@motorola.com>
X-OriginalArrivalTime: 25 Oct 2005 21:16:58.0984 (UTC)
	FILETIME=[6F4B6680:01C5D9A9]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135
Content-Transfer-Encoding: quoted-printable
Cc: mip6@ietf.org, Keiichi SHIMA <keiichi@iijlab.net>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org



 > > =3D> I'm afraid you didn't understand the draft. We are=20
 > working under=20
 > > the premise that MIP is used to manage mobility. Other=20
 > techniques are
 > >  outside the scope of this draft and this mailing list.
 > >=20
 > > Based on that, we state that if you have an IPv4 home=20
 > address and you
 > >  appear in an IPv6-only network you won't be able to maintain=20
 > > connections using MIPv4 only.
 >=20
 > Absolutely.  Note though that the urgency of a solution for this
 > scenario is much lower than the urgency of a solution for a v6 MN
 > connecting to a v4-only network, simply because there are much more
 > v4-only wireless access networks (than v6), no?

=3D> That's a strange conclusion IMO. If you agree the vast majority
of the Internet is v4 and hopefully slowly migrating to v6. Why would
you want to allow a MN to obtain a v4 CoA, while communicating with
everyone in the IPv4 Internet using an IPv6 home address??
Makes no sense to me. Either you think most of the Internet is=20
v4 or not. You can't use that argument for the CoA and not for=20
the HoA.=20

 > And the two scenarios lead to the immediate question: why not running
 > both MIP4 and MIP6 on the mobile, so that when it connects to the
 > v4-only access it uses MIP4 and when it connects to the=20
 > v6-only access
 > it uses MIP6. =20

=3D> We keep going back in circles. If you're questioning assumptions =
then
please address the problem statement. It contains answers to all=20
this. If you don't agree with those answers then we can discuss them
in that context.

 > I hope the answer is not 'because it is a burden'.  Running both MIP4
 > and MIP6 on a same MN should break something, which we could identify
 > and try to solve.  Currently it doesn't break anything, no?

=3D> It does! breaks roaming between v4 and v6 networks...
It also practically breaks the mobility management for those=20
relying on MIP for real local mobility. It's pointless to send=20
to signals to the same local agent for v4 and v6.=20

Hesham

 >=20
 > Alex
 >=20
 >=20

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D
This email may contain confidential and privileged material for the sole =
use
 of the intended recipient.  Any review or distribution by others is =
strictly
 prohibited.  If you are not the intended recipient please contact the =
sender
 and delete all copies.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D


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



From mip6-bounces@ietf.org Tue Oct 25 17:35:41 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUWSL-00064B-Ii; Tue, 25 Oct 2005 17:35:41 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUWSI-00063x-Pb
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 17:35:39 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16162
	for <mip6@ietf.org>; Tue, 25 Oct 2005 17:35:23 -0400 (EDT)
Received: from motgate3.mot.com ([144.189.100.103])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUWfK-0002u2-Sl
	for mip6@ietf.org; Tue, 25 Oct 2005 17:49:07 -0400
Received: from az33exr03.mot.com (az33exr03.mot.com [10.64.251.233])
	by motgate3.mot.com (8.12.11/Motgate3) with ESMTP id j9PLpJM7021067;
	Tue, 25 Oct 2005 14:51:23 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by az33exr03.mot.com (8.13.1/8.13.0) with ESMTP id j9PLijst022530;
	Tue, 25 Oct 2005 16:44:46 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id C7A47865980; Tue, 25 Oct 2005 23:35:28 +0200 (CEST)
Message-ID: <435EA520.9070603@motorola.com>
Date: Tue, 25 Oct 2005 23:35:28 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: "Soliman, Hesham" <H.Soliman@flarion.com>
Subject: Re: [Mip6] I-D ACTION:draft-ietf-mip6-nemo-v4traversal-00.txt
References: <A11736FE943F1A408F8BBB1B9F5FE8AD17DE48@ftmailserver.flariontech.com>
In-Reply-To: <A11736FE943F1A408F8BBB1B9F5FE8AD17DE48@ftmailserver.flariontech.com>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 386e0819b1192672467565a524848168
Content-Transfer-Encoding: 7bit
Cc: mip6@ietf.org, Keiichi SHIMA <keiichi@iijlab.net>,
	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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Soliman, Hesham wrote:

> 
>>> => I'm afraid you didn't understand the draft. We are
>> working under
>>> the premise that MIP is used to manage mobility. Other
>> techniques are
>>> outside the scope of this draft and this mailing list.
>>> 
>>> Based on that, we state that if you have an IPv4 home
>> address and you
>>> appear in an IPv6-only network you won't be able to maintain 
>>> connections using MIPv4 only.
>> 
>> Absolutely.  Note though that the urgency of a solution for this 
>> scenario is much lower than the urgency of a solution for a v6 MN 
>> connecting to a v4-only network, simply because there are much more
>>  v4-only wireless access networks (than v6), no?
> 
> => That's a strange conclusion IMO. If you agree the vast majority of
>  the Internet is v4 and hopefully slowly migrating to v6.

Hesham, right, let's synchronize.  I was not saying vast majority of
Internet is v4, I was saying vast majority of wireless access systems
are v4.  In this case, the second scenario you've described in the
Problem Statement draft (v6 MN, v6 app, v4-only access network) is the
most valid and urgent.  Would you agree?

> Why would you want to allow a MN to obtain a v4 CoA, while 
> communicating with everyone in the IPv4 Internet using an IPv6 home 
> address?? Makes no sense to me.

Makes no sense to me on paper either, but let's address that later in
3-4 years when v6-only wireless access networks are more prevalent, so
implementation feedback could help.   Would you agree?

> Either you think most of the Internet is v4 or not.

I can't even dare at guessing Internet being more v4 or more v6, but I
know most wireless access systems for end-user consumers are v4.

> You can't use that argument for the CoA and not for the HoA.

Oh, I see.  No I can't.  Fact is though that I can logically say that
a marketed wireless device has more chances to acquire an IPv4 CoA than
an IPv6 CoA.

I can't compare number of available CoAs to available HoAs v4 or v6 and
I don't think I need that comparison to motivate the problem of a v6-HoA
 MN, v6 app on a v4-exclusively access network.

>> And the two scenarios lead to the immediate question: why not 
>> running both MIP4 and MIP6 on the mobile, so that when it connects 
>> to the v4-only access it uses MIP4 and when it connects to the 
>> v6-only access it uses MIP6.
> 
> => We keep going back in circles. If you're questioning assumptions 
> then please address the problem statement. It contains answers to all
>  this. If you don't agree with those answers then we can discuss them
>  in that context.

Hesham, I keep being forwarded to the DS Problem Statement draft.
Whether one believes it or not - I have read it.  I have even identified
a paragraph with respect to which you've enlightened me - thanks for that.

To stop turning in circles, and knowing it's not us deciding, let's
deal.  I already said I believe IPv6 MN connecting to v4-only network
and v6 app is a problem and needs a solution.  I do.  Would you agree
with anything I've asked about?  Most notably about using MIP4 for
managing an IPv4 Home Address?  Or about MIP4 doing v4 prefixes instead
of MIP6 doing v4 prefixes?

>> I hope the answer is not 'because it is a burden'.  Running both 
>> MIP4 and MIP6 on a same MN should break something, which we could 
>> identify and try to solve.  Currently it doesn't break anything, 
>> no?
> 
> => It does! breaks roaming between v4 and v6 networks...

Ok, how about this: a v6 MN with MIPv6 using MIP4's UDP traversal and
running v6 app.  This would not break mobility between v4 and v6 access
networks for that v6 app.

> It also practically breaks the mobility management for those relying
> on MIP for real local mobility. It's pointless to send to signals to
> the same local agent for v4 and v6.

Is it more meaningful to send one single larger BU than two smaller BU
and RegReq?

Alex


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



From mip6-bounces@ietf.org Tue Oct 25 17:54:14 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUWkI-0006rQ-Op; Tue, 25 Oct 2005 17:54:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUWkG-0006qX-RI
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 17:54:12 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA17311
	for <mip6@ietf.org>; Tue, 25 Oct 2005 17:53:57 -0400 (EDT)
Received: from mail.flarion.com ([63.103.94.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUWxJ-0003VO-2Z
	for mip6@ietf.org; Tue, 25 Oct 2005 18:07:41 -0400
Received: from ftmailserver.flariontech.com ([10.10.1.140]) by
	mail.flarion.com with Microsoft SMTPSVC(5.0.2195.6713);
	Tue, 25 Oct 2005 17:54:03 -0400
Content-Class: urn:content-classes:message
Subject: RE: [Mip6] I-D ACTION:draft-ietf-mip6-nemo-v4traversal-00.txt
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 25 Oct 2005 17:54:01 -0400
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
Message-ID: <A11736FE943F1A408F8BBB1B9F5FE8AD17DE49@ftmailserver.flariontech.com>
Thread-Topic: [Mip6] I-D ACTION:draft-ietf-mip6-nemo-v4traversal-00.txt
Thread-Index: AcXZrAj+9R4+bJxjSa2Gi4MV6Pxi+AAANYFg
From: "Soliman, Hesham" <H.Soliman@flarion.com>
To: "Alexandru Petrescu" <alexandru.petrescu@motorola.com>
X-OriginalArrivalTime: 25 Oct 2005 21:54:03.0437 (UTC)
	FILETIME=[9D2BFDD0:01C5D9AE]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f66b12316365a3fe519e75911daf28a8
Content-Transfer-Encoding: quoted-printable
Cc: mip6@ietf.org, Keiichi SHIMA <keiichi@iijlab.net>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org




 > Hesham, right, let's synchronize.  I was not saying vast majority of
 > Internet is v4, I was saying vast majority of wireless access systems
 > are v4.  In this case, the second scenario you've described in the
 > Problem Statement draft (v6 MN, v6 app, v4-only access=20
 > network) is the
 > most valid and urgent.  Would you agree?

=3D> No. v4 access, v4 app. There is no dependency between
the access and the app that uses the HoA.

 >=20
 > > Why would you want to allow a MN to obtain a v4 CoA, while=20
 > > communicating with everyone in the IPv4 Internet using an=20
 > IPv6 home=20
 > > address?? Makes no sense to me.
 >=20
 > Makes no sense to me on paper either, but let's address that later in
 > 3-4 years when v6-only wireless access networks are more=20
 > prevalent, so
 > implementation feedback could help.   Would you agree?

=3D> What is the relationship to this discussion? Implementation of =
what?

 > > You can't use that argument for the CoA and not for the HoA.
 >=20
 > Oh, I see.  No I can't.  Fact is though that I can logically say that
 > a marketed wireless device has more chances to acquire an=20
 > IPv4 CoA than
 > an IPv6 CoA.

=3D> Yet you seem to assume that it's ok to communicate with
other IPv4 hosts using that IPv6 HoA.

 > I can't compare number of available CoAs to available HoAs=20

=3D> That's irrelevant, the relevant number is the number of=20
CNs using IPv4.

 >=20
 > To stop turning in circles, and knowing it's not us deciding, let's
 > deal.  I already said I believe IPv6 MN connecting to v4-only network
 > and v6 app is a problem and needs a solution.  I do.  Would you agree
 > with anything I've asked about?  Most notably about using MIP4 for
 > managing an IPv4 Home Address?  Or about MIP4 doing v4=20
 > prefixes instead
 > of MIP6 doing v4 prefixes?

=3D> No I don't agree with that as stated earlier.=20

 > Ok, how about this: a v6 MN with MIPv6 using MIP4's UDP traversal and
 > running v6 app.  This would not break mobility between v4=20
 > and v6 access
 > networks for that v6 app.

=3D> What if some radical app decided to use IPv4?? How can you
exclude the v4 apps?

 >=20
 > > It also practically breaks the mobility management for=20
 > those relying
 > > on MIP for real local mobility. It's pointless to send to=20
 > signals to
 > > the same local agent for v4 and v6.
 >=20
 > Is it more meaningful to send one single larger BU than two=20
 > smaller BU
 > and RegReq?

=3D> Yes. A lot more useful and efficient.

Hesham

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D
This email may contain confidential and privileged material for the sole =
use
 of the intended recipient.  Any review or distribution by others is =
strictly
 prohibited.  If you are not the intended recipient please contact the =
sender
 and delete all copies.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D


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



From mip6-bounces@ietf.org Tue Oct 25 17:57:27 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUWnP-0007xc-17; Tue, 25 Oct 2005 17:57:27 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUWnJ-0007t3-Iu
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 17:57:25 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA17461
	for <mip6@ietf.org>; Tue, 25 Oct 2005 17:57:06 -0400 (EDT)
From: Basavaraj.Patil@nokia.com
Received: from mgw-ext03.nokia.com ([131.228.20.95])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUX0K-0003at-PT
	for mip6@ietf.org; Tue, 25 Oct 2005 18:10:50 -0400
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
	by mgw-ext03.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id
	j9PLsv8S023625; Wed, 26 Oct 2005 00:54:57 +0300
Received: from daebh102.NOE.Nokia.com ([10.241.35.112]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 26 Oct 2005 00:57:13 +0300
Received: from daebe101.NOE.Nokia.com ([10.241.35.113]) by
	daebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 25 Oct 2005 16:57:06 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5.7233.31
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] draft-dupont-mip6-dhaadharmful-00.txt 
Date: Tue, 25 Oct 2005 16:57:06 -0500
Message-ID: <456943D540CFC14A8D7138E64843F85301E8A7B6@daebe101.NOE.Nokia.com>
Thread-Topic: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt 
Thread-Index: AcXZmden90FGxjanR6GWQ3RjjXy6dgAA1E1AAARQOXA=
To: <vidya@motorola.com>, <Francis.Dupont@enst-bretagne.fr>
X-OriginalArrivalTime: 25 Oct 2005 21:57:06.0198 (UTC)
	FILETIME=[0A1B1B60:01C5D9AF]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Content-Transfer-Encoding: quoted-printable
Cc: mip6@ietf.org, Kilian.Weniger@eu.panasonic.com,
	alexandru.petrescu@motorola.com, 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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

>>   =20
>>    1. Are we working on failover mechanisms in the WG?=20
>>   =20
>> =3D> yes, "Improving home agent reliability" is in the charter=20
>> and clearly something needed for deployment.
>>=20
>
>Yes, it seems to be in the charter. But, I recall that the chairs were
>questioning this in Paris - there seemed to be some feeling that this
>can be vendor specific for the moment and it was agreed that we would
>discuss on the ML to decide if it is critical enough to be looked at in
>the WG right now. I might have missed the discussion - was there a
>consensus on this?=20
>
>Anyway, I would agree that this is important.=20
>

Home agent reliability is indeed a part of the charter. We have had
discussion on this topic for a couple of IETFs now. If I remember right,
I think we agreed to poll the broader WG via the ML for consensus on=20
taking up work on this. Maybe it is time to get that consensus call=20
going so that we can have a better view of this topic at IETF64.

-BPa

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



From mip6-bounces@ietf.org Tue Oct 25 19:01:26 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUXnK-0001go-QE; Tue, 25 Oct 2005 19:01:26 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUXnI-0001gQ-8x
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 19:01:24 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA23630
	for <mip6@ietf.org>; Tue, 25 Oct 2005 19:01:08 -0400 (EDT)
Received: from motgate.mot.com ([129.188.136.100])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUY0F-0006LO-4w
	for mip6@ietf.org; Tue, 25 Oct 2005 19:14:53 -0400
Received: from az33exr03.mot.com (az33exr03.mot.com [10.64.251.233])
	by motgate.mot.com (Motorola/Motgate) with ESMTP id j9PN1APX021211;
	Tue, 25 Oct 2005 16:01:10 -0700 (MST)
Received: from [144.189.74.61] (mvp-144-189-74-61.corp.mot.com [144.189.74.61])
	by az33exr03.mot.com (8.13.1/8.13.0) with ESMTP id j9PNANMM004464;
	Tue, 25 Oct 2005 18:10:24 -0500 (CDT)
Message-ID: <435EB932.6020805@motorola.com>
Date: Wed, 26 Oct 2005 01:01:06 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: "Soliman, Hesham" <H.Soliman@flarion.com>
Subject: Re: [Mip6] I-D ACTION:draft-ietf-mip6-nemo-v4traversal-00.txt
References: <A11736FE943F1A408F8BBB1B9F5FE8AD17DE49@ftmailserver.flariontech.com>
In-Reply-To: <A11736FE943F1A408F8BBB1B9F5FE8AD17DE49@ftmailserver.flariontech.com>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be
Content-Transfer-Encoding: 7bit
Cc: mip6@ietf.org, Keiichi SHIMA <keiichi@iijlab.net>,
	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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Soliman, Hesham wrote:
> 
> 
>> Hesham, right, let's synchronize.  I was not saying vast majority 
>> of Internet is v4, I was saying vast majority of wireless access 
>> systems are v4.  In this case, the second scenario you've described
>>  in the Problem Statement draft (v6 MN, v6 app, v4-only access 
>> network) is the most valid and urgent.  Would you agree?
> 
> => No. v4 access, v4 app. There is no dependency between the access 
> and the app that uses the HoA.

Right, the version MH uses is independent of the version of the access.
 And this is a stringent problem when the app is v6 and the access v4.

>>> Why would you want to allow a MN to obtain a v4 CoA, while 
>>> communicating with everyone in the IPv4 Internet using an IPv6 
>>> home address?? Makes no sense to me.
>> 
>> Makes no sense to me on paper either, but let's address that later
>>  in 3-4 years when v6-only wireless access networks are more 
>> prevalent, so implementation feedback could help.   Would you 
>> agree?
> 
> => What is the relationship to this discussion? Implementation of 
> what?

The relationship to this discussion is that the case where access is
v6-only will happen later.  And then some implementor could implement
DSMIPv6 and provide feedback such as to improve the DSMIPv6 spec.  Until
then it can't, so the spec is incurring risks of not having
implementation feedback.

>>> You can't use that argument for the CoA and not for the HoA.
>> 
>> Oh, I see.  No I can't.  Fact is though that I can logically say 
>> that a marketed wireless device has more chances to acquire an IPv4
>>  CoA than an IPv6 CoA.
> 
> => Yet you seem to assume that it's ok to communicate with other IPv4
>  hosts using that IPv6 HoA.

Right, misunderstanding.  I was thinking the DSMIPv6 solution
suggests MN to use its IPv6 Home Address as an address that contains an
IPv4 address, thus talking to an IPv4 CN.

>> I can't compare number of available CoAs to available HoAs
> 
> => That's irrelevant, the relevant number is the number of CNs using
>  IPv4.

Right.

>> To stop turning in circles, and knowing it's not us deciding, let's
>>  deal.  I already said I believe IPv6 MN connecting to v4-only 
>> network and v6 app is a problem and needs a solution.  I do.  Would
>>  you agree with anything I've asked about?  Most notably about 
>> using MIP4 for managing an IPv4 Home Address?  Or about MIP4 doing 
>> v4 prefixes instead of MIP6 doing v4 prefixes?
> 
> => No I don't agree with that as stated earlier.

So you stated earlier you don't agree with MIP4 managing IPv4 prefixes?
 Or about MIP4 managing IPv4 Home Addresses?

Do you agree with _anything_ I'm suggesting for that matter?

>> Ok, how about this: a v6 MN with MIPv6 using MIP4's UDP traversal 
>> and running v6 app.  This would not break mobility between v4 and 
>> v6 access networks for that v6 app.
> 
> => What if some radical app decided to use IPv4?? How can you exclude
>  the v4 apps?

Right, good questions.  Several solutions here.  A mobile phone may have
an IPv4 jvm and IPv4 midlets.  To have that IPv4 midlets transformed
into IPv6 midlets it's sufficient to specify the IPv6 http url format
and port the jvm to IPv6 (not the app midlet).

Another possibility for another v4 radical app to run over IPv6 would be
to port it to IPv6.

Another possibility for the v4 radical app to use its IPv4 Home Address
over a v4-only access is to use MIP4.

Three possibilities, none needing new DSMIPv6.

Alex

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



From mip6-bounces@ietf.org Tue Oct 25 19:03:35 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUXpP-0002sm-2A; Tue, 25 Oct 2005 19:03:35 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUXpI-0002g4-4M
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 19:03:33 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA24270
	for <mip6@ietf.org>; Tue, 25 Oct 2005 19:03:12 -0400 (EDT)
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUY21-0006V0-Tj
	for mip6@ietf.org; Tue, 25 Oct 2005 19:16:49 -0400
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id j9PMTno05159;
	Tue, 25 Oct 2005 15:29:49 -0700
X-mProtect: <200510252229> Nokia Silicon Valley Messaging Protection
Received: from mvdhcp14184.americas.nokia.com (172.18.141.84,
	claiming to be "[127.0.0.1]")
	by darkstar.iprg.nokia.com smtpdEGoKbs; Tue, 25 Oct 2005 15:29:47 PDT
Message-ID: <435EB98D.3010401@iprg.nokia.com>
Date: Tue, 25 Oct 2005 16:02:37 -0700
From: Vijay Devarapalli <vijayd@iprg.nokia.com>
User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Gerardo Giaretta <Gerardo.Giaretta@TILAB.COM>
Subject: Re: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
References: <DA62A6E0CDD1B34A84557FF1AC850C57016E9CDC@EXC01B.cselt.it>
In-Reply-To: <DA62A6E0CDD1B34A84557FF1AC850C57016E9CDC@EXC01B.cselt.it>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Content-Transfer-Encoding: 7bit
Cc: mip6@ietf.org, Kilian Weniger <Kilian.Weniger@eu.panasonic.com>,
	James Kempf <Kempf@docomolabs-usa.com>,
	Francis Dupont <Francis.Dupont@enst-bretagne.fr>,
	Petrescu Alexandru-AAP021 <alexandru.petrescu@motorola.com>,
	COMBES Jean-Michel RD-MAPS-ISS <jeanmichel.combes@francetelecom.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Gerardo Giaretta wrote:

>>What does prevent the MN to contact the HA he wants? Nothing 
>>as far as I
>>can see.
>>
> 
> 
> I agree. This is true also for DHAAD. 
> Besides the motivation why a MN will prevent another HA that is
> theoretically more loaded, the operator may let the HA refuse the IPsec
> SA setup during IKEv2 through its AAA infrastructure. But I agree this
> is not a clean approach.
> 
> 
>>> Otherwise, in integrated scenario, 
>>>DHCP can be used. As mentioned before, if you need a very 
>>>strict control on the HA assignment by the operator, IMHO the 
>>>best way is to perform it during network access 
>>>authentication, but unfortunately this is not a general solution.
>>
>>Agree. But I think a operator must have the possibility to 
>>assign the HA
>>in any cases.
>>
> 
> 
> DHCP-based solution seems to achieve this. Do you see any issue on that?

yes. DHCP based solution would require the Operator to
first update the access network too. what many operators
would like to do (initially atleast) is to just plug in
a HA and introduce new mobile devices that can use the
new features. no upgrades anywhere else.

Vijay


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



From mip6-bounces@ietf.org Tue Oct 25 19:13:14 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUXyk-0001YR-6m; Tue, 25 Oct 2005 19:13:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUXyi-0001YA-M8
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 19:13:12 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA28930
	for <mip6@ietf.org>; Tue, 25 Oct 2005 19:12:58 -0400 (EDT)
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUYBk-0008LM-20
	for mip6@ietf.org; Tue, 25 Oct 2005 19:26:42 -0400
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id j9PMdhA17484;
	Tue, 25 Oct 2005 15:39:43 -0700
X-mProtect: <200510252239> Nokia Silicon Valley Messaging Protection
Received: from mvdhcp14184.americas.nokia.com (172.18.141.84,
	claiming to be "[127.0.0.1]")
	by darkstar.iprg.nokia.com smtpdQHXiP9; Tue, 25 Oct 2005 15:39:39 PDT
Message-ID: <435EBBDE.8020203@iprg.nokia.com>
Date: Tue, 25 Oct 2005 16:12:30 -0700
From: Vijay Devarapalli <vijayd@iprg.nokia.com>
User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Alexandru Petrescu <alexandru.petrescu@motorola.com>
Subject: Re: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
References: <200510251632.j9PGW4MC007527@givry.rennes.enst-bretagne.fr>
	<435E5FEB.3070700@motorola.com>
In-Reply-To: <435E5FEB.3070700@motorola.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Content-Transfer-Encoding: 7bit
Cc: Gerardo Giaretta <Gerardo.Giaretta@tilab.com>, mip6@ietf.org,
	Kilian Weniger <Kilian.Weniger@eu.panasonic.com>,
	Francis Dupont <Francis.Dupont@enst-bretagne.fr>,
	James Kempf <Kempf@docomolabs-usa.com>,
	COMBES Jean-Michel RD-MAPS-ISS <jeanmichel.combes@francetelecom.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Alexandru Petrescu wrote:
> Francis Dupont wrote:
> 
> 
>> In your previous mail you wrote:
>>
>>   Real simplification would be for the HA Switch message to be simplified
>>   and just be used as a trigger that would make MN re-start the DHAAD
>>   procedure to acquire the new HA.
>>
>>=> it doesn't need to be simplified, I quote here the I-D:
>>
>>   # of Addresses
>> 
>>     A 16-bit unsigned integer indicating the number of IPv6 home agent
>>     addresses in the message.  If set to zero, the mobile node MUST
>>     perform home agent discovery.
>>
>>So it can already do what you want... (another reason to like it? :-)
> 
> 
> That's good, thanks for pointing it.  Is that "home agent discovery" DHAAD?

nope. it is whatever the mobile node is configured to
use for HA discovery. possible options include

1. DHAAD
2. DNS
3. https to some server
4. over the air provisiong
5. other proprietary mechanisms specific to each operator.

notice, I left out DHCPv6 because it is tied to access
authentication and can't be used whenever you want.

in general, there are way too many device management
mechanisms that enterprises and Operators use today.
any of them are candidates for HA assignment.

Vijay


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



From mip6-bounces@ietf.org Tue Oct 25 19:19:07 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUY4R-0006yO-7E; Tue, 25 Oct 2005 19:19:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUY4P-0006yC-Ck
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 19:19:05 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01901
	for <mip6@ietf.org>; Tue, 25 Oct 2005 19:18:51 -0400 (EDT)
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUYHS-0000zw-2U
	for mip6@ietf.org; Tue, 25 Oct 2005 19:32:34 -0400
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id j9PMjnb25753;
	Tue, 25 Oct 2005 15:45:49 -0700
X-mProtect: <200510252245> Nokia Silicon Valley Messaging Protection
Received: from mvdhcp14184.americas.nokia.com (172.18.141.84,
	claiming to be "[127.0.0.1]")
	by darkstar.iprg.nokia.com smtpdTWTsYq; Tue, 25 Oct 2005 15:45:48 PDT
Message-ID: <435EBD4E.30603@iprg.nokia.com>
Date: Tue, 25 Oct 2005 16:18:38 -0700
From: Vijay Devarapalli <vijayd@iprg.nokia.com>
User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
Subject: Re: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
References: <200510251924.j9PJOtHE008854@givry.rennes.enst-bretagne.fr>
In-Reply-To: <200510251924.j9PJOtHE008854@givry.rennes.enst-bretagne.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Content-Transfer-Encoding: 7bit
Cc: mip6@ietf.org, Petrescu Alexandru-AAP021 <alexandru.petrescu@motorola.com>,
	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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Francis Dupont wrote:

> PS: the right way is to get feedback from operators: the goal of the IETF
> is not to produce X pages of junk specs per day, but to provide good
> (i.e., fulfilling real requirements) specs to operators and customers.
> At least it should be the goal...

well, the feedback I have gotten so far....

Dont worry about HA assignment. We know how to assign servers
to terminals that attach to our networks.

so maybe we need to sit back and relax a bit. wait
and see how MIPv6 is deployed and then develop
solutions that might actually be used. :)

Vijay


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



From mip6-bounces@ietf.org Tue Oct 25 19:23:24 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUY8a-0002ej-1Q; Tue, 25 Oct 2005 19:23:24 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUY8Y-0002eJ-A0
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 19:23:22 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA03863
	for <mip6@ietf.org>; Tue, 25 Oct 2005 19:23:07 -0400 (EDT)
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUYLZ-0001jE-8W
	for mip6@ietf.org; Tue, 25 Oct 2005 19:36:51 -0400
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id j9PMnIW30225;
	Tue, 25 Oct 2005 15:49:18 -0700
X-mProtect: <200510252249> Nokia Silicon Valley Messaging Protection
Received: from mvdhcp14184.americas.nokia.com (172.18.141.84,
	claiming to be "[127.0.0.1]")
	by darkstar.iprg.nokia.com smtpdiFMM57; Tue, 25 Oct 2005 15:49:16 PDT
Message-ID: <435EBE1E.50600@iprg.nokia.com>
Date: Tue, 25 Oct 2005 16:22:06 -0700
From: Vijay Devarapalli <vijayd@iprg.nokia.com>
User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Basavaraj.Patil@nokia.com
Subject: Re: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
References: <456943D540CFC14A8D7138E64843F85301E8A7B6@daebe101.NOE.Nokia.com>
In-Reply-To: <456943D540CFC14A8D7138E64843F85301E8A7B6@daebe101.NOE.Nokia.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Content-Transfer-Encoding: 7bit
Cc: mip6@ietf.org, Kilian.Weniger@eu.panasonic.com, Kempf@docomolabs-usa.com,
	Francis.Dupont@enst-bretagne.fr, 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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Basavaraj.Patil@nokia.com wrote:
>>>   
>>>   1. Are we working on failover mechanisms in the WG? 
>>>   
>>>=> yes, "Improving home agent reliability" is in the charter 
>>>and clearly something needed for deployment.
>>>
>>
>>Yes, it seems to be in the charter. But, I recall that the chairs were
>>questioning this in Paris - there seemed to be some feeling that this
>>can be vendor specific for the moment and it was agreed that we would
>>discuss on the ML to decide if it is critical enough to be looked at in
>>the WG right now. I might have missed the discussion - was there a
>>consensus on this? 
>>
>>Anyway, I would agree that this is important. 
>>
> 
> 
> Home agent reliability is indeed a part of the charter. We have had
> discussion on this topic for a couple of IETFs now. If I remember right,
> I think we agreed to poll the broader WG via the ML for consensus on 
> taking up work on this. Maybe it is time to get that consensus call 
> going so that we can have a better view of this topic at IETF64.

at the last IETF, there was a disagreement on whether IETF
needs to provide *a* solution for HA reliability or just
leave it to vendor specific solutions.

we never concluded that discussion.

there are a bunch of individual drafts available on this.

Vijay


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



From mip6-bounces@ietf.org Tue Oct 25 19:33:23 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUYIF-0006EF-0Z; Tue, 25 Oct 2005 19:33:23 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUYI9-0006Ag-CK
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 19:33:21 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05328
	for <mip6@ietf.org>; Tue, 25 Oct 2005 19:33:03 -0400 (EDT)
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUYVB-0002LY-Qz
	for mip6@ietf.org; Tue, 25 Oct 2005 19:46:46 -0400
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id j9PMxuY07729;
	Tue, 25 Oct 2005 15:59:56 -0700
X-mProtect: <200510252259> Nokia Silicon Valley Messaging Protection
Received: from mvdhcp14184.americas.nokia.com (172.18.141.84,
	claiming to be "[127.0.0.1]")
	by darkstar.iprg.nokia.com smtpdT2Joh4; Tue, 25 Oct 2005 15:59:55 PDT
Message-ID: <435EC09D.7010300@iprg.nokia.com>
Date: Tue, 25 Oct 2005 16:32:45 -0700
From: Vijay Devarapalli <vijayd@iprg.nokia.com>
User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Alexandru Petrescu <alexandru.petrescu@motorola.com>
Subject: Re: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
References: <4D2F935F08D41A4C8866693F4F0D7C4F58DBC3@lan-ex-01.panasonic.de>	<155a01c5ceb1$6748e190$196115ac@dcml.docomolabsusa.com>
	<435CCCD9.4070605@motorola.com>
In-Reply-To: <435CCCD9.4070605@motorola.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Content-Transfer-Encoding: 7bit
Cc: mip6@ietf.org, Kilian Weniger <Kilian.Weniger@eu.panasonic.com>,
	James Kempf <Kempf@docomolabs-usa.com>,
	Francis Dupont <Francis.Dupont@enst-bretagne.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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Alexandru Petrescu wrote:
> Hello to dhaad-harmful contributors and supporters.
> 
> James Kempf wrote:
> 
> 
>>>From a deployment standpoint, there are two issues with DHAAD:
>>
>>
>>- it uses ICMP across the Internet. The trend has been to turn off ICMP
>>except for local link communications, to avoid convenient vehicles for
>>DoS. I know that one can theoretically configure the firewall to filter
>>on the ICMP message type field, but it is easier just to drop it at the
>>firewall than to try to figure out what ICMP is good and what is bad.
> 
> 
> I think the argument 'some protocol may be blocked by some firewalls'
> for considering some protocol harmful and support other protocols
> instead, is probably a little bit flawed.

I agree with Alex.

I think it is easy opening your firewall to allow some
specific ICMPv6 messages.

Vijay


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



From mip6-bounces@ietf.org Tue Oct 25 20:01:44 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUYjg-0001PX-65; Tue, 25 Oct 2005 20:01:44 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUYje-0001PS-AL
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 20:01:42 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA08154
	for <mip6@ietf.org>; Tue, 25 Oct 2005 20:01:28 -0400 (EDT)
Received: from mail.flarion.com ([63.103.94.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUYwg-0003Z4-RZ
	for mip6@ietf.org; Tue, 25 Oct 2005 20:15:12 -0400
Received: from ftmailserver.flariontech.com ([10.10.1.140]) by
	mail.flarion.com with Microsoft SMTPSVC(5.0.2195.6713);
	Tue, 25 Oct 2005 20:01:28 -0400
Content-Class: urn:content-classes:message
Subject: RE: [Mip6] I-D ACTION:draft-ietf-mip6-nemo-v4traversal-00.txt
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
Date: Tue, 25 Oct 2005 20:01:27 -0400
Message-ID: <A11736FE943F1A408F8BBB1B9F5FE8AD17DE4A@ftmailserver.flariontech.com>
Thread-Topic: [Mip6] I-D ACTION:draft-ietf-mip6-nemo-v4traversal-00.txt
Thread-Index: AcXZt/4ce4XSFvjAR8a22akB7QPbIAABoXtw
From: "Soliman, Hesham" <H.Soliman@flarion.com>
To: "Alexandru Petrescu" <alexandru.petrescu@motorola.com>
X-OriginalArrivalTime: 26 Oct 2005 00:01:28.0956 (UTC)
	FILETIME=[6A419BC0:01C5D9C0]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d
Content-Transfer-Encoding: quoted-printable
Cc: mip6@ietf.org, Keiichi SHIMA <keiichi@iijlab.net>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org


 > >=20
 > > =3D> What is the relationship to this discussion? Implementation of =

 > > what?
 >=20
 > The relationship to this discussion is that the case where access is
 > v6-only will happen later.  And then some implementor could implement
 > DSMIPv6 and provide feedback such as to improve the DSMIPv6=20
 > spec.  Until
 > then it can't, so the spec is incurring risks of not having
 > implementation feedback.

=3D> You're assuming (wrongly) that this draft is written to only
be used in a v6 access when the MN wants to use a v6 app. This=20
is wrong. The draft is written to allow implementers and operators
to use MIPv6 only no matter where they are on the Internet and=20
for v6 and v4 apps.

 > > =3D> No I don't agree with that as stated earlier.
 >=20
 > So you stated earlier you don't agree with MIP4 managing=20
 > IPv4 prefixes?
 >  Or about MIP4 managing IPv4 Home Addresses?

=3D> Sigh. Alex, I disagreed with not supporting IPv4 home=20
addresses in MIPv6. How can I disagree with MIPv4 supporting
IPv4 home addresses. This a fact documented in RFCs.=20

 > Do you agree with _anything_ I'm suggesting for that matter?

=3D> I already agreed with a couple of your suggestions to improve the=20
draft.=20

 > > =3D> What if some radical app decided to use IPv4?? How can=20
 > you exclude
 > >  the v4 apps?
 >=20
 > Right, good questions.  Several solutions here.  A mobile=20
 > phone may have
 > an IPv4 jvm and IPv4 midlets.  To have that IPv4 midlets transformed
 > into IPv6 midlets it's sufficient to specify the IPv6 http url format
 > and port the jvm to IPv6 (not the app midlet).
 >=20
 > Another possibility for another v4 radical app to run over=20
 > IPv6 would be
 > to port it to IPv6.

=3D> Hmm. If you can guarantee this will be done by all CNs on the=20
Internet then we can start considering it seriously. Until then,
this is a dream that isn't remotely related to reality.

 >=20
 > Another possibility for the v4 radical app to use its IPv4=20
 > Home Address
 > over a v4-only access is to use MIP4.

=3D> I've already addressed this several times.

Hesham

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D
This email may contain confidential and privileged material for the sole =
use
 of the intended recipient.  Any review or distribution by others is =
strictly
 prohibited.  If you are not the intended recipient please contact the =
sender
 and delete all copies.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D


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



From mip6-bounces@ietf.org Tue Oct 25 22:12:32 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUamG-0001z8-88; Tue, 25 Oct 2005 22:12:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUamF-0001z3-J9
	for mip6@megatron.ietf.org; Tue, 25 Oct 2005 22:12:31 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14186
	for <mip6@ietf.org>; Tue, 25 Oct 2005 22:12:16 -0400 (EDT)
Received: from mail.sfc.wide.ad.jp ([203.178.142.146])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUazK-0006kI-1f
	for mip6@ietf.org; Tue, 25 Oct 2005 22:26:02 -0400
Received: from iseran.local (jules.nautilus6.org [203.178.138.2])
	by mail.sfc.wide.ad.jp (Postfix) with ESMTP id 383C94CC33
	for <mip6@ietf.org>; Wed, 26 Oct 2005 11:12:02 +0900 (JST)
Date: Wed, 26 Oct 2005 11:12:07 +0900
From: Thierry Ernst <ernst@sfc.wide.ad.jp>
To: mip6@ietf.org
Message-Id: <20051026111207.4259e2a9.ernst@sfc.wide.ad.jp>
In-Reply-To: <200510251551.j9PFpQXE007256@givry.rennes.enst-bretagne.fr>
References: <435E2D29.8070509@motorola.com>
	<200510251551.j9PFpQXE007256@givry.rennes.enst-bretagne.fr>
Organization: Keio University
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-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Content-Transfer-Encoding: 7bit
Subject: [Mip6] load balancing and HA (re-)assignment : which WG is the
 right venue ?
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org


BTW, I would like to discuss a concern I have: whatever the solution
for HA re-assignment, I think everyone agree that it should work for
both MIP6 and NEMO Basic Support. Right ? 

So, I'm wondering if the mip6 group is the right venue for a working
group item. 

A possible good venue could be, I think, the Monami6 WG, because it is
chartered to work on both MIP6 and NEMO Basic Support multihoming
extensions. Here, we fall into one of the multihoming configuration (of
course Monami6 is not presently chartered for HA re-assignement, but I
think it falls into its area of expertise).

I would like to get a sense of the WG regarding this point.

I think we will have sufficient time at Vancounver to add such a
discussion on the Monami6 agenda if someone want to lead it.

Thierry (speaking for himself).




 On Tue, 25 Oct 2005 17:51:26 +0200
Francis Dupont <Francis.Dupont@enst-bretagne.fr> wrote:

>  In your previous mail you wrote:
> 
>    Before making it a WG item I'd look at whether bootstrapping with
>    DHCPv6 doesn't involve use of some pre-defined DHCPv6 message
>    ("re-acquire"?)
> 
> => the "reconfigure" message
> 
>    that is sent by server to client and that could be reused or
>    extended to do the semantics of HA Switch message.
>    
> => I believe it is the right answer when DHCPv6 is used (but I have
> to read the last general bootstrapping I-D).
> 
>    Otherwise, the HA switch draft looks simple and rational and is
>    something good to work on and advance probably quickly, IMHO.
>    
> => we agree and the HA switch draft is already in the agenda of
> the next meeting.
> 
> Thanks
> 

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



From mip6-bounces@ietf.org Wed Oct 26 04:17:00 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUgSx-0008OG-T7; Wed, 26 Oct 2005 04:16:59 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUgSp-0008Ia-O5
	for mip6@megatron.ietf.org; Wed, 26 Oct 2005 04:16:58 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02874
	for <mip6@ietf.org>; Wed, 26 Oct 2005 04:16:35 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUgfv-0000X0-0t
	for mip6@ietf.org; Wed, 26 Oct 2005 04:30:24 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id j9Q8FsA09246; Wed, 26 Oct 2005 10:15:54 +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
	j9Q8FrkE011748; Wed, 26 Oct 2005 10:15:53 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200510260815.j9Q8FrkE011748@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Vijay Devarapalli <vijayd@iprg.nokia.com>
Subject: Re: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt 
In-reply-to: Your message of Tue, 25 Oct 2005 16:18:38 PDT.
	<435EBD4E.30603@iprg.nokia.com> 
Date: Wed, 26 Oct 2005 10:15:53 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Cc: mip6@ietf.org, Petrescu Alexandru-AAP021 <alexandru.petrescu@motorola.com>,
	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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   Dont worry about HA assignment. We know how to assign servers
   to terminals that attach to our networks.
   
=> but this is only the integrated scenario.

   so maybe we need to sit back and relax a bit. wait
   and see how MIPv6 is deployed and then develop
   solutions that might actually be used. :)
   
=> there is at least an operator asking for HA assignment and
I believe we can get a consensus about the fact that HA assignment
is better than HA discovery.

Regards

Francis.Dupont@enst-bretagne.fr
   

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



From mip6-bounces@ietf.org Wed Oct 26 04:35:48 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUglA-00046j-9M; Wed, 26 Oct 2005 04:35:48 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUgl9-00045O-6k
	for mip6@megatron.ietf.org; Wed, 26 Oct 2005 04:35:47 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA03833
	for <mip6@ietf.org>; Wed, 26 Oct 2005 04:35:31 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUgyF-00017x-TQ
	for mip6@ietf.org; Wed, 26 Oct 2005 04:49:21 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id j9Q8ZQA11107; Wed, 26 Oct 2005 10:35:26 +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
	j9Q8ZQsV012058; Wed, 26 Oct 2005 10:35:26 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200510260835.j9Q8ZQsV012058@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Thierry Ernst <ernst@sfc.wide.ad.jp>
Subject: Re: [Mip6] load balancing and HA (re-)assignment : which WG is the
	right venue ? 
In-reply-to: Your message of Wed, 26 Oct 2005 11:12:07 +0900.
	<20051026111207.4259e2a9.ernst@sfc.wide.ad.jp> 
Date: Wed, 26 Oct 2005 10:35:26 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:
   
   BTW, I would like to discuss a concern I have: whatever the solution
   for HA re-assignment, I think everyone agree that it should work for
   both MIP6 and NEMO Basic Support. Right ? 
   
=> yes!

   So, I'm wondering if the mip6 group is the right venue for a working
   group item. 
   
=> bootstrapping is already considered as the right venue and
HA assignment and discovery are clearly parts of it. I agree
HA re-assignment is not but it seems to be enough close.

   A possible good venue could be, I think, the Monami6 WG, because it is
   chartered to work on both MIP6 and NEMO Basic Support multihoming
   extensions. Here, we fall into one of the multihoming configuration (of
   course Monami6 is not presently chartered for HA re-assignement, but I
   think it falls into its area of expertise).
   
=> until there is something specific for Monami6 I believe the WG has
enough work...

   I would like to get a sense of the WG regarding this point.
   
   I think we will have sufficient time at Vancounver to add such a
   discussion on the Monami6 agenda if someone want to lead it.
   
=> agenda sharing is enough issue. One can believe it is fine (it gives
more time) but past experiences are not good (duplicate items,
more likely schedule conflicts, etc).

Regards

Francis.Dupont@enst-bretagne.fr

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



From mip6-bounces@ietf.org Wed Oct 26 04:49:28 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUgyN-000238-Pp; Wed, 26 Oct 2005 04:49:27 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUgyL-00020y-7w
	for mip6@megatron.ietf.org; Wed, 26 Oct 2005 04:49:25 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA04719
	for <mip6@ietf.org>; Wed, 26 Oct 2005 04:49:09 -0400 (EDT)
Received: from mout.perfora.net ([217.160.230.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUhBS-0001XF-Ab
	for mip6@ietf.org; Wed, 26 Oct 2005 05:02:59 -0400
Received: from [85.101.251.215] (helo=Alperyegin)
	by mrelay.perfora.net with ESMTP (Nemesis),
	id 0MKoyl-1EUgy81WT6-0006Gb; Wed, 26 Oct 2005 04:49:12 -0400
From: "Alper Yegin" <alper.yegin@yegin.org>
To: "'Francis Dupont'" <Francis.Dupont@enst-bretagne.fr>,
	"'COMBES Jean-Michel RD-MAPS-ISS'" <jeanmichel.combes@francetelecom.com>
Subject: RE: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt 
Date: Wed, 26 Oct 2005 11:49:06 +0300
Message-ID: <000001c5da0a$263a99f0$0302a8c0@Alperyegin>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
Importance: Normal
In-Reply-To: <200510251716.j9PHGe8o007841@givry.rennes.enst-bretagne.fr>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Provags-ID: perfora.net abuse@perfora.net
	login:abf7a4bb310ea4dfc9b6841113e2970f
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Content-Transfer-Encoding: 7bit
Cc: 'Gerardo Giaretta' <Gerardo.Giaretta@tilab.com>, mip6@ietf.org,
	'Kilian Weniger' <Kilian.Weniger@eu.panasonic.com>,
	'James Kempf' <Kempf@docomolabs-usa.com>,
	'Petrescu Alexandru-AAP021' <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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

>  In your previous mail you wrote:
> 
>    Drawback with a DHCP based solution (in the split case): you have
to
>    deploy a DHCP-Relay in all the potential Access Network because
even if
>    the MN knows the DHCP server's unicast address, this one will
refuse to
>    communicate directly with the MN (cf. RFC3315, section 22.12).
> 
> => I confirm: there must be a DHCP relay on each link (a real IPv6
> link with link-local addresses and multicast). After relays can talk
> with the server through multicast routers, routers or a relay chain.
> 
> This should be in the applicability statement for the DHCP-based
solution.

Well, this is what a regular DHCP deployment requires, in other words,
it is not specific to this particular usage of DHCP.

Alper



> 
> Regards
> 
> Francis.Dupont@enst-bretagne.fr
> 
> _______________________________________________
> 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 Oct 26 04:53:48 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUh2a-0005Ry-BV; Wed, 26 Oct 2005 04:53:48 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUh2Y-0005Rt-UR
	for mip6@megatron.ietf.org; Wed, 26 Oct 2005 04:53:47 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA04930
	for <mip6@ietf.org>; Wed, 26 Oct 2005 04:53:31 -0400 (EDT)
Received: from mail.sfc.wide.ad.jp ([203.178.142.146])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUhFe-0001en-AQ
	for mip6@ietf.org; Wed, 26 Oct 2005 05:07:21 -0400
Received: from iseran.local (jules.nautilus6.org [203.178.138.2])
	by mail.sfc.wide.ad.jp (Postfix) with ESMTP id D4D454CC33
	for <mip6@ietf.org>; Wed, 26 Oct 2005 17:53:28 +0900 (JST)
Date: Wed, 26 Oct 2005 17:53:34 +0900
From: Thierry Ernst <ernst@sfc.wide.ad.jp>
To: mip6@ietf.org
Subject: Re: [Mip6] load balancing and HA (re-)assignment : which WG is the
	right venue ?
Message-Id: <20051026175334.35856e7d.ernst@sfc.wide.ad.jp>
In-Reply-To: <200510260835.j9Q8ZQsV012058@givry.rennes.enst-bretagne.fr>
References: <20051026111207.4259e2a9.ernst@sfc.wide.ad.jp>
	<200510260835.j9Q8ZQsV012058@givry.rennes.enst-bretagne.fr>
Organization: Keio University
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-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Content-Transfer-Encoding: 7bit
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org


Hi,

>  In your previous mail you wrote:
>    
>    BTW, I would like to discuss a concern I have: whatever the
>    solution for HA re-assignment, I think everyone agree that it
>    should work for both MIP6 and NEMO Basic Support. Right ? 
>    
> => yes!
Good.
 
>    So, I'm wondering if the mip6 group is the right venue for a
>    working group item. 
>    
> => bootstrapping is already considered as the right venue and
> HA assignment and discovery are clearly parts of it. I agree
> HA re-assignment is not but it seems to be enough close.

Probably yes, but how the MIP6 group will consider the NEMO
specificities ? Isn't this also confusing for the group ?

>    A possible good venue could be, I think, the Monami6 WG, because it
>    is chartered to work on both MIP6 and NEMO Basic Support
>    multihoming extensions. Here, we fall into one of the multihoming
>    configuration (of course Monami6 is not presently chartered for HA
>    re-assignement, but I think it falls into its area of expertise).
>    
> => until there is something specific for Monami6 I believe the WG has
> enough work...

Monami6 has 4 items. How many for MIP6 ?

>    I would like to get a sense of the WG regarding this point.
>    
>    I think we will have sufficient time at Vancounver to add such a
>    discussion on the Monami6 agenda if someone want to lead it.
>    
> => agenda sharing is enough issue. One can believe it is fine (it
> gives more time) but past experiences are not good (duplicate items,
> more likely schedule conflicts, etc).

This is exactly why everything related to multihoming in MIP6/NEMO
should be moved to Monami6, particularly when it concerns both MIP6 and
NEMO.


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



From mip6-bounces@ietf.org Wed Oct 26 05:12:42 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUhKs-0007Qp-RL; Wed, 26 Oct 2005 05:12:42 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUhKq-0007Qh-Dy
	for mip6@megatron.ietf.org; Wed, 26 Oct 2005 05:12:40 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA05817
	for <mip6@ietf.org>; Wed, 26 Oct 2005 05:12:24 -0400 (EDT)
Received: from smtp2.int-evry.fr ([157.159.10.45])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUhXy-00029I-I6
	for mip6@ietf.org; Wed, 26 Oct 2005 05:26:15 -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 54F4A811F;
	Wed, 26 Oct 2005 11:12:21 +0200 (CEST)
Received: from jb by ipv6-3.int-evry.fr with local (Exim 4.52)
	id 1EUhIQ-0004e0-Id; Wed, 26 Oct 2005 11:10:10 +0200
Date: Wed, 26 Oct 2005 11:10:10 +0200
From: Julien Bournelle <julien.bournelle@int-evry.fr>
To: mip6@ietf.org, aaa-wg@merit.edu
Message-ID: <20051026091010.GD16237@ipv6-3.int-evry.fr>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="opJtzjQTFsWo+cga"
Content-Disposition: inline
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-MailScanner-From: jb@int-evry.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 14582b0692e7f70ce7111d04db3781c8
Cc: gerardo.giaretta@tilab.com, tseno.tsenov@mytum.de,
	hannes.tschofenig@siemens.com
Subject: [Mip6] [I-D ACTION:draft-tschofenig-mip6-aaa-ha-diameter-01.txt]
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org


--opJtzjQTFsWo+cga
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Hi all,

 we've submitted an i-d describing use of Diameter to handle the AAA
 part of both bootstrapping solutions for Mobile IPv6 (split and
 integrated scenario).

 The i-d can be found at:

 http://www.ietf.org/internet-drafts/draft-tschofenig-mip6-aaa-ha-diameter-01.txt

 Any comments welcome,
-- 
julien.bournelle at int-evry.fr

--opJtzjQTFsWo+cga
Content-Type: text/plain
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id FAA05817

ATTENTION !!!
Au moins une pi=C3=A8ce jointe =C3=A0 ce message ne vous a pas =C3=A9t=C3=
=A9 transmise
(sans nom).
SVP lire la pi=C3=A8ce jointe =C2=ABAlerteVirus.txt=C2=BB pour plus d'inf=
ormations.
---
Warning: This message has had one or more attachments removed
Warning: (sans nom).
Warning: Please read the "INT-Attachment-Warning.txt" attachment(s) for m=
ore information.

A New Internet-Draft is available from the on-line Internet-Drafts direct=
ories.


	Title		: Mobile IPv6 Bootstrapping using Diameter
	Author(s)	: H. Tschofenig, et al.
	Filename	: draft-tschofenig-mip6-aaa-ha-diameter-01.txt
	Pages		: 21
	Date		: 2005-10-25
=09
Both Mobile IPv6 bootstrapping solutions require use of a AAA
   interface.  In the split scenario, this interface is between the Home
   Agent and the AAA infrastructure of the Mobile Service Provider (MSP)
   and the Mobility Service Authorizer (MSA).  The first interface
   should meet a list of requirements.  This document provides an
   overview of the capabilities and design of the Diameter protocol that
   could meet the specified goals.  In the integrated scenario, in
   addition to this interface, the impact of the MIPv6 bootstrapping on
   the AAA interface for network access authentication must be
   considered.  Basically, this interface is also used to carry Home
   Agent information.  This document defines the necessary AVP and how
   Diameter can be used in the integrated scenario.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-tschofenig-mip6-aaa-ha-diameter=
-01.txt

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


Internet-Drafts are also available by anonymous FTP. Login with the usern=
ame
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-tschofenig-mip6-aaa-ha-diameter-01.txt".

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


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

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-tschofenig-mip6-aaa-ha-diameter-01.txt".
=09
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
	=09
	=09
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--opJtzjQTFsWo+cga
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

--opJtzjQTFsWo+cga--




From mip6-bounces@ietf.org Wed Oct 26 06:05:54 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUiAM-0000WI-Oa; Wed, 26 Oct 2005 06:05:54 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUiAK-0000WD-Tg
	for mip6@megatron.ietf.org; Wed, 26 Oct 2005 06:05:53 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA08746
	for <mip6@ietf.org>; Wed, 26 Oct 2005 06:05:37 -0400 (EDT)
Received: from motgate2.mot.com ([144.189.100.101])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUiNT-0003qA-IG
	for mip6@ietf.org; Wed, 26 Oct 2005 06:19:27 -0400
Received: from az33exr01.mot.com (az33exr01.mot.com [10.64.251.231])
	by motgate2.mot.com (8.12.11/Motgate2) with ESMTP id j9QAL2Zl003372;
	Wed, 26 Oct 2005 03:21:02 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by az33exr01.mot.com (8.13.1/8.13.0) with ESMTP id j9QAID5I011504;
	Wed, 26 Oct 2005 05:18:14 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id 3A9A3865980; Wed, 26 Oct 2005 12:05:48 +0200 (CEST)
Message-ID: <435F54FC.1020103@motorola.com>
Date: Wed, 26 Oct 2005 12:05:48 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: Thierry Ernst <ernst@sfc.wide.ad.jp>
Subject: Re: [Mip6] load balancing and HA (re-)assignment : which WG is the
	right venue ?
References: <20051026111207.4259e2a9.ernst@sfc.wide.ad.jp>	<200510260835.j9Q8ZQsV012058@givry.rennes.enst-bretagne.fr>
	<20051026175334.35856e7d.ernst@sfc.wide.ad.jp>
In-Reply-To: <20051026175334.35856e7d.ernst@sfc.wide.ad.jp>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135
Content-Transfer-Encoding: 7bit
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Thierry Ernst wrote:
> Hi,
> 
> 
>> In your previous mail you wrote:
>> 
>> BTW, I would like to discuss a concern I have: whatever the 
>> solution for HA re-assignment, I think everyone agree that it 
>> should work for both MIP6 and NEMO Basic Support. Right ?
>> 
>> => yes!
> 
> Good.
> 
> 
>> So, I'm wondering if the mip6 group is the right venue for a 
>> working group item.
>> 
>> => bootstrapping is already considered as the right venue and HA
>> assignment and discovery are clearly parts of it. I agree HA
>> re-assignment is not but it seems to be enough close.
> 
> Probably yes, but how the MIP6 group will consider the NEMO 
> specificities ? Isn't this also confusing for the group ?

Me deviating... I agree that the MIP6 WG should somehow consult the NEMO
WG with respect to NEMO specificities.

>> A possible good venue could be, I think, the Monami6 WG, because it
>>  is chartered to work on both MIP6 and NEMO Basic Support 
>> multihoming extensions. Here, we fall into one of the multihoming 
>> configuration (of course Monami6 is not presently chartered for HA 
>> re-assignement, but I think it falls into its area of expertise).
>> 
>> => until there is something specific for Monami6 I believe the WG
>> has enough work...
> 
> 
> Monami6 has 4 items. How many for MIP6 ?

Well, current charter mentions 8 milestones, 17 I-Ds, 2 RFCs (subject to
update at the meeting).

Monami6 has 4 milestones.  I personally believe that is focused and
motivating.

>> I would like to get a sense of the WG regarding this point.
>> 
>> I think we will have sufficient time at Vancounver to add such a 
>> discussion on the Monami6 agenda if someone want to lead it.
>> 
>> => agenda sharing is enough issue. One can believe it is fine (it 
>> gives more time) but past experiences are not good (duplicate
>> items, more likely schedule conflicts, etc).
> 
> This is exactly why everything related to multihoming in MIP6/NEMO 
> should be moved to Monami6, particularly when it concerns both MIP6
> and NEMO.

But which monami6 WG Deliverable?  The closest I could find is
"Flow/binding policies exchange" but this terminology has not been
discussed at all here.

During Monami6 BoF it was discussed thoroughly what exactly should the
WG work on so a Charter was issued.  Is the Monami6 trying to modify its
Charter with new items so quickly after creation?

Alex

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



From mip6-bounces@ietf.org Wed Oct 26 06:15:49 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUiJx-0005Py-Jv; Wed, 26 Oct 2005 06:15:49 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUiJv-0005PD-FZ
	for mip6@megatron.ietf.org; Wed, 26 Oct 2005 06:15:47 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA09152
	for <mip6@ietf.org>; Wed, 26 Oct 2005 06:15:31 -0400 (EDT)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUiX3-00048X-4c
	for mip6@ietf.org; Wed, 26 Oct 2005 06:29:22 -0400
Received: from il06exr03.mot.com (il06exr03.mot.com [129.188.137.133])
	by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id j9QARZBk008522;
	Wed, 26 Oct 2005 03:27:40 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by il06exr03.mot.com (8.13.1/8.13.0) with ESMTP id j9QAPhQ0025186;
	Wed, 26 Oct 2005 05:25:43 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id 2FBAC865980; Wed, 26 Oct 2005 12:15:38 +0200 (CEST)
Message-ID: <435F5749.3010502@motorola.com>
Date: Wed, 26 Oct 2005 12:15:37 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: "Soliman, Hesham" <H.Soliman@flarion.com>
Subject: Re: [Mip6] I-D ACTION:draft-ietf-mip6-nemo-v4traversal-00.txt
References: <A11736FE943F1A408F8BBB1B9F5FE8AD17DE4A@ftmailserver.flariontech.com>
In-Reply-To: <A11736FE943F1A408F8BBB1B9F5FE8AD17DE4A@ftmailserver.flariontech.com>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
Content-Transfer-Encoding: 7bit
Cc: mip6@ietf.org, Keiichi SHIMA <keiichi@iijlab.net>,
	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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Soliman, Hesham wrote:
>>> => What is the relationship to this discussion? Implementation of
>>>  what?
>> 
>> The relationship to this discussion is that the case where access 
>> is v6-only will happen later.  And then some implementor could 
>> implement DSMIPv6 and provide feedback such as to improve the 
>> DSMIPv6 spec.  Until then it can't, so the spec is incurring risks 
>> of not having implementation feedback.
> 
> => You're assuming (wrongly) that this draft is written to only be 
> used in a v6 access when the MN wants to use a v6 app. This is wrong.
> 
I think my assumption that this draft is written to only be used in a v6
access when the MN wants to use a v6 app was wrong.

> The draft is written to allow implementers and operators to use MIPv6
> only no matter where they are on the Internet and for v6 and v4 apps.

Hesham, that is a hefty goal.  I'd reach lower, do some small modular
parts that would fit in the current landscape, instead of building
entirely new architectures, solutions to everything a customer might
ever need.

In the past, "universal" mobility solutions have had lesser reach than
expected.  For example, real complete local and global mobility
solutions haven't seen widepsread use despite years of discussion
meeting after meeting, mail after mail.

>>> => No I don't agree with that as stated earlier.
>> 
>> So you stated earlier you don't agree with MIP4 managing IPv4 
>> prefixes? Or about MIP4 managing IPv4 Home Addresses?
> 
> => Sigh. Alex, I disagreed with not supporting IPv4 home addresses in
>  MIPv6. How can I disagree with MIPv4 supporting IPv4 home addresses.
>  This a fact documented in RFCs.

So you agree that DSMIPv6 would compete with MIPv4 to offer reachability
at a permanent MIP4 Home Address, when connected to a v4-only network
and v4 app.

>> Do you agree with _anything_ I'm suggesting for that matter?
> 
> => I already agreed with a couple of your suggestions to improve the 
> draft.
> 
>>> => What if some radical app decided to use IPv4?? How can
>> you exclude
>>> the v4 apps?
>> 
>> Right, good questions.  Several solutions here.  A mobile phone may
>>  have an IPv4 jvm and IPv4 midlets.  To have that IPv4 midlets 
>> transformed into IPv6 midlets it's sufficient to specify the IPv6 
>> http url format and port the jvm to IPv6 (not the app midlet).
>> 
>> Another possibility for another v4 radical app to run over IPv6 
>> would be to port it to IPv6.
> 
> => Hmm. If you can guarantee this will be done by all CNs on the 
> Internet then we can start considering it seriously. Until then, this
>  is a dream that isn't remotely related to reality.

I think I see your point.

>> Another possibility for the v4 radical app to use its IPv4 Home 
>> Address over a v4-only access is to use MIP4.
> 
> => I've already addressed this several times.

You're right.

Alex


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



From mip6-bounces@ietf.org Wed Oct 26 06:18:34 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUiMc-0006kg-6w; Wed, 26 Oct 2005 06:18:34 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUiMa-0006ji-6D
	for mip6@megatron.ietf.org; Wed, 26 Oct 2005 06:18:32 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA09335
	for <mip6@ietf.org>; Wed, 26 Oct 2005 06:18:16 -0400 (EDT)
Received: from mail.sfc.wide.ad.jp ([203.178.142.146])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUiZi-0004E0-AD
	for mip6@ietf.org; Wed, 26 Oct 2005 06:32:06 -0400
Received: from iseran.local (jules.nautilus6.org [203.178.138.2])
	by mail.sfc.wide.ad.jp (Postfix) with ESMTP id 21C1A4CC33
	for <mip6@ietf.org>; Wed, 26 Oct 2005 19:18:19 +0900 (JST)
Date: Wed, 26 Oct 2005 19:18:24 +0900
From: Thierry Ernst <ernst@sfc.wide.ad.jp>
To: mip6@ietf.org
Subject: Re: [Mip6] load balancing and HA (re-)assignment : which WG is the
	right venue ?
Message-Id: <20051026191824.75378624.ernst@sfc.wide.ad.jp>
In-Reply-To: <435F54FC.1020103@motorola.com>
References: <20051026111207.4259e2a9.ernst@sfc.wide.ad.jp>
	<200510260835.j9Q8ZQsV012058@givry.rennes.enst-bretagne.fr>
	<20051026175334.35856e7d.ernst@sfc.wide.ad.jp>
	<435F54FC.1020103@motorola.com>
Organization: Keio University
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-Spam-Score: 0.0 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Content-Transfer-Encoding: 7bit
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org



> > Probably yes, but how the MIP6 group will consider the NEMO 
> > specificities ? Isn't this also confusing for the group ?
> 
> Me deviating... I agree that the MIP6 WG should somehow consult the
> NEMO WG with respect to NEMO specificities.

> > Monami6 has 4 items. How many for MIP6 ?
> 
> Well, current charter mentions 8 milestones, 17 I-Ds, 2 RFCs (subject
> to update at the meeting).
> 
> Monami6 has 4 milestones.  I personally believe that is focused and
> motivating.
> 
> >> I would like to get a sense of the WG regarding this point.
> >> 
> >> I think we will have sufficient time at Vancounver to add such a 
> >> discussion on the Monami6 agenda if someone want to lead it.
> >> 
> >> => agenda sharing is enough issue. One can believe it is fine (it 
> >> gives more time) but past experiences are not good (duplicate
> >> items, more likely schedule conflicts, etc).
> > 
> > This is exactly why everything related to multihoming in MIP6/NEMO 
> > should be moved to Monami6, particularly when it concerns both MIP6
> > and NEMO.
> 
> But which monami6 WG Deliverable?  The closest I could find is
> "Flow/binding policies exchange" but this terminology has not been
> discussed at all here.

Actually, why not ? I was thinking about a new deliverable (because
it's clearer), but debating the exact features may well lead us to
consider HA-reassigment in any of the solutions. 

What I mean is that even if HA-reassignment is done in MIP6, both
HA-reasssigment, multiple CoA registration, and policies exchanges have
to be compatible. 

By the way, I would like to point to issue "HA synchronization" of
draft-ietf-nemo-multihoming-issues. 

> During Monami6 BoF it was discussed thoroughly what exactly should the
> WG work on so a Charter was issued.  Is the Monami6 trying to modify
> its Charter with new items so quickly after creation?

Why not ?

Well, adding a new item would require Monami6 to be rechartered if that
given work doesn't correspond to the charter. But there is no rules at
the IETF that a WG just approved cannot be rechartered, so this is not a
dead end, and I wouldn't mind to negociate that if this is the sense of
the MIP6/NEMO/MONAMI6 WG that this is the right thing to do.

But, I don't think this wouldn't be a dramatic change to the charter..

My personal view on all of this is that working on this topic in Monami6
would make it easier for everyone, the IETFers, and the people
interested in the standards defined by the IETF.

Thierry








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



From mip6-bounces@ietf.org Wed Oct 26 06:22:54 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUiQo-0000pz-Ij; Wed, 26 Oct 2005 06:22:54 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUiQm-0000pb-Kj
	for mip6@megatron.ietf.org; Wed, 26 Oct 2005 06:22:53 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA09710
	for <mip6@ietf.org>; Wed, 26 Oct 2005 06:22:34 -0400 (EDT)
Received: from motgate5.mot.com ([144.189.100.105])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUids-0004PK-BZ
	for mip6@ietf.org; Wed, 26 Oct 2005 06:36:25 -0400
Received: from az33exr04.mot.com (az33exr04.mot.com [10.64.251.234])
	by motgate5.mot.com (8.12.11/Motgate5) with ESMTP id j9QAUv0b012825
	for <mip6@ietf.org>; Wed, 26 Oct 2005 03:30:57 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by az33exr04.mot.com (8.13.1/8.13.0) with ESMTP id j9QATTWq022766
	for <mip6@ietf.org>; Wed, 26 Oct 2005 05:29:30 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP id 8C96E865980
	for <mip6@ietf.org>; Wed, 26 Oct 2005 12:22:41 +0200 (CEST)
Message-ID: <435F58F1.4080902@motorola.com>
Date: Wed, 26 Oct 2005 12:22:41 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: Mobile IPv6 Mailing List <mip6@ietf.org>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de
Content-Transfer-Encoding: 7bit
Subject: [Mip6] Authorship of draft-ietf-mip6-nemo-v4traversal-00.txt
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Hello to authors of draft-ietf-mip6-nemo-v4traversal-00.txt.

The author list on the first page contains a relatively long list of
authors (7).  Wouldn't it be better to have a Contributors section
listing all names in arbitrary order, state that this was a DT work, and
keep only an Editor on the front page?  I mean that's what I saw with
other drafts and RFCs.

Alex


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



From mip6-bounces@ietf.org Wed Oct 26 08:14:19 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUkAd-0006WK-3M; Wed, 26 Oct 2005 08:14:19 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUkAb-0006VJ-Fc
	for mip6@megatron.ietf.org; Wed, 26 Oct 2005 08:14:17 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA14922
	for <mip6@ietf.org>; Wed, 26 Oct 2005 08:14:03 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUkNk-0007cE-9p
	for mip6@ietf.org; Wed, 26 Oct 2005 08:27:53 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id j9QCDrA30681; Wed, 26 Oct 2005 14:13:53 +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
	j9QCDrOr013107; Wed, 26 Oct 2005 14:13:53 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200510261213.j9QCDrOr013107@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: "COMBES Jean-Michel RD-MAPS-ISS" <jeanmichel.combes@francetelecom.com>
Subject: Re: [Mip6] General comments/questions on MIPv6 bootstrapping 
In-reply-to: Your message of Mon, 24 Oct 2005 19:41:23 +0200.
	<D2AA6DF1AEE4404F8D983B68BAC97CD2022B914F@ftrdmel3.rd.francetelecom.fr>
Date: Wed, 26 Oct 2005 14:13:53 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   I have 2 main comments/questions.
   
   The first one is regarding the fact that we have two (very) different
   mechanisms for only one functionality (on one side DNS+IKEv2, on the
   other side PANA+AAA+DCHP). So, personally, I am a little afraid how all

=> PANA is not in the I-D, i.e., the protocol between the MN and
the NAS is not specified (but it can be PANA).

   this will be managed in the user's terminal and in the MSP's network.
   E.g., what will be the trigger in the terminal to know which is the
   bootstrapping mechanism the terminal has to use?
   
=> I don't believe it is a real issue, or to use another argument,
you have already the issue for the network access control itself.

   My second comment is regarding the interoperability with NEMO. I believe
   that if MIPv6 is deployed soon, NEMO will be deployed at the same time
   because the protocol is as mature as MIPv6. So I would like to know if
   the bootstrapping mechanisms working for MIPv6, will work with NEMO too.
   I would like to avoid to add new mechanisms again and so increase the
   complexity in a deployement architecture.
   
=> we can classify mechanisms into mechanisms with a NEMO flag (ICMP-based
DHAAD for instance) or NEMO knowledge (HA-switch for instance), and
zero-knowledge mechanisms where the NEMO knowledge has to be out of band.
I believe it is the case today for DHCP (but it can be easily fixed)
and IKEv2 HA-assignment (where IMHO it is harder without another anycast
address). I can't see a reason to get really different mechanisms for
MIPv6 and NEMO.

Regards

Francis.Dupont@enst-bretagne.fr

PS: I'll do a second answer with my comments about the draft (i.e.,
I'll keep the subject and the subject header).

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



From mip6-bounces@ietf.org Wed Oct 26 08:47:20 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUkga-0003SB-J2; Wed, 26 Oct 2005 08:47:20 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUkgZ-0003S6-EI
	for mip6@megatron.ietf.org; Wed, 26 Oct 2005 08:47:19 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17017
	for <mip6@ietf.org>; Wed, 26 Oct 2005 08:47:04 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUktj-0000HD-Gw
	for mip6@ietf.org; Wed, 26 Oct 2005 09:00:55 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id j9QCkwA01509; Wed, 26 Oct 2005 14:46:58 +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
	j9QCkxXL013329; Wed, 26 Oct 2005 14:46:59 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200510261246.j9QCkxXL013329@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: "COMBES Jean-Michel RD-MAPS-ISS" <jeanmichel.combes@francetelecom.com>
Subject: Re: [Mip6] General comments/questions on MIPv6 bootstrapping 
In-reply-to: Your message of Mon, 24 Oct 2005 19:41:23 +0200.
	<D2AA6DF1AEE4404F8D983B68BAC97CD2022B914F@ftrdmel3.rd.francetelecom.fr>
Date: Wed, 26 Oct 2005 14:46:59 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

This is a review of draft-ietf-mip6-bootstrapping-integrated-dhc-00.txt:

 - in fact the document can (should?) be split into 2 parts:
   the AAA stuff and the DHCP stuff. IMHO the important part
   is the AAA one because it comes directly from the "integrated"
   scenario, DHCP is used only to transmit the AAA results to
   the MN. One can use in some cases the access control protocol,
   for instance if it is 802.1X.

 - DHCPv6 has some constraints which are not explained in
   the document (cf my previous messages)

 - I don't know if the OPTION_MIP6-RELAY-Option is necessary, i.e.,
   why not use the RADIUS-RELAY-Option (aka RRAO) ?
   (cf. draft-ietf-dhc-v6-relay-radius-01.txt)

 - Security Considerations reference RFC which are not for DHCPv6,
   i.e., the right reference is RFC 3315.

 - DHCPv6 security doesn't work well in multi-domain environments
   so in the mobility context. Quoting RFC 3118:

   The "delayed authentication" protocol does not attempt to address
   situations where a client may roam from one administrative domain to
   another, i.e., interdomain roaming.  This protocol is focused on
   solving the intradomain problem where the out-of-band exchange of a
   shared secret is feasible.

   and:

      Delayed authentication requires a shared secret key for each
      client on each DHCP server with which that client may wish to use
      the DHCP protocol.  Each secret key has a unique identifier that
      can be used by a receiver to determine which secret was used to
      generate the MAC in the DHCP message.  Therefore, delayed
      authentication may not scale well in an architecture in which a
      DHCP client connects to multiple administrative domains.

 - IMHO this paragraph is not sound:

   The communication between the DHCP client and the DHCP server for the
   exchange of home agent information is security sensitive and requires
   authentication, integrity and replay protection.  Either lower-layer
   security (such as link layer security established as part of the
   network access authentication protocol run) or DHCP security
   [RFC3118] can be used.  The latter approach is only applicable in
   non-roaming environments due to the limited applicability of the DHCP
   security mechanisms.  An adversary that is able to modify home agent
   information can force the mobile node to use a different home agent
   than intended by the MSA.  However, this type of attack can be
   detected by the security mechanism between the mobile node and the
   home agent.


 - to finish the document presents the less aggressive scheme to use
   AAA in MIPv6 bootstrapping, i.e., it only assigns the HA. I have
   a concern about this because AAA is the only practical way to
   attach security properties (i.e., a proof it is not fake) to
   the care-of address so to improve the MIPv6 security.
   Unfortunately the document does nothing for this...

Regards

Francis.Dupont@enst-bretagne.fr

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



From mip6-bounces@ietf.org Wed Oct 26 09:28:57 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUlKr-0001SI-Po; Wed, 26 Oct 2005 09:28:57 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUlKp-0001Pq-FS
	for mip6@megatron.ietf.org; Wed, 26 Oct 2005 09:28:55 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19459
	for <mip6@ietf.org>; Wed, 26 Oct 2005 09:28:40 -0400 (EDT)
Received: from smtp2.int-evry.fr ([157.159.10.45])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUlXw-0001bK-W5
	for mip6@ietf.org; Wed, 26 Oct 2005 09:42:32 -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 D3DDB8106;
	Wed, 26 Oct 2005 15:28:31 +0200 (CEST)
Received: from jb by ipv6-3.int-evry.fr with local (Exim 4.52)
	id 1EUlIL-0004y9-As; Wed, 26 Oct 2005 15:26:21 +0200
Date: Wed, 26 Oct 2005 15:26:21 +0200
From: Julien Bournelle <julien.bournelle@int-evry.fr>
To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
Subject: Re: [Mip6] General comments/questions on MIPv6 bootstrapping
Message-ID: <20051026132621.GS16237@ipv6-3.int-evry.fr>
References: <D2AA6DF1AEE4404F8D983B68BAC97CD2022B914F@ftrdmel3.rd.francetelecom.fr>
	<200510261246.j9QCkxXL013329@givry.rennes.enst-bretagne.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200510261246.j9QCkxXL013329@givry.rennes.enst-bretagne.fr>
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-MailScanner-From: jb@int-evry.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Cc: mip6@ietf.org,
	COMBES Jean-Michel RD-MAPS-ISS <jeanmichel.combes@francetelecom.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Hi francis,

 just a comment concerning AAA inline,

On Wed, Oct 26, 2005 at 02:46:59PM +0200, Francis Dupont wrote:

<snip>

>  - to finish the document presents the less aggressive scheme to use
>    AAA in MIPv6 bootstrapping, i.e., it only assigns the HA. I have
>    a concern about this because AAA is the only practical way to
>    attach security properties (i.e., a proof it is not fake) to
>    the care-of address so to improve the MIPv6 security.
>    Unfortunately the document does nothing for this...

 the problem with doing what you proposed is the following:

 - or you have to modified all the MN-NAS protocol (e.g. 802.1X/PANA) to
 support bootstrapping Mobile IPv6

 - or you may use EAP and in this case we have an Applicability problem:
   EAP is not for configuration and EAP may not be in use in the access
   network.


 Julien  


> 
> Regards
> 
> Francis.Dupont@enst-bretagne.fr
> 
> _______________________________________________
> 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 Wed Oct 26 09:57:04 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUlm4-0004jG-7e; Wed, 26 Oct 2005 09:57:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUlm2-0004j8-Pz
	for mip6@megatron.ietf.org; Wed, 26 Oct 2005 09:57:02 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20702
	for <mip6@ietf.org>; Wed, 26 Oct 2005 09:56:47 -0400 (EDT)
Received: from dns2.tilab.com ([163.162.42.5])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUlzD-0002MF-3L
	for mip6@ietf.org; Wed, 26 Oct 2005 10:10:39 -0400
Received: from iowa2k01b.cselt.it ([163.162.242.202])
	by dns2.cselt.it (PMDF V6.1 #38895)
	with ESMTP id <0IOZ00L1Q02S3T@dns2.cselt.it> for mip6@ietf.org; Wed,
	26 Oct 2005 15:56:52 +0200 (MEST)
Received: from EXC01B.cselt.it ([163.162.4.199]) by iowa2k01b.cselt.it with
	Microsoft SMTPSVC(6.0.3790.211); Wed, 26 Oct 2005 15:54:30 +0200
Date: Wed, 26 Oct 2005 15:56:51 +0200
From: Gerardo Giaretta <Gerardo.Giaretta@TILAB.COM>
Subject: RE: [Mip6] General comments/questions on MIPv6 bootstrapping
To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
Message-id: <DA62A6E0CDD1B34A84557FF1AC850C57016E9CE7@EXC01B.cselt.it>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.3790.326
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: quoted-printable
Importance: normal
Priority: normal
Thread-Topic: [Mip6] General comments/questions on MIPv6 bootstrapping
thread-index: AcXaLZ2NOXyExU8VQrSFDhXOy3q3RQABuVxQ
Content-Class: urn:content-classes:message
X-OriginalArrivalTime: 26 Oct 2005 13:54:30.0156 (UTC)
	FILETIME=[C95F7CC0:01C5DA34]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2857c5c041d6c02d7181d602c22822c8
Content-Transfer-Encoding: quoted-printable
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Hi Francis,

just one comment below. I'll let the editor of the draft to answer more
detailed comments.=20

> This is a review of=20
> draft-ietf-mip6-bootstrapping-integrated-dhc-00.txt:
>=20
>  - in fact the document can (should?) be split into 2 parts:
>    the AAA stuff and the DHCP stuff. IMHO the important part
>    is the AAA one because it comes directly from the "integrated"
>    scenario, DHCP is used only to transmit the AAA results to
>    the MN. One can use in some cases the access control protocol,
>    for instance if it is 802.1X.
>

I believe that AAA is also the most pratcial way to perform HA
assignment.

I think modifying 802.1X is tricky. An extension to PANA may be easier.
Another approach is the usage of EAP between MN and AAA for HA
assignment. This has also the advantage that it does not imply
extensions to network access and this is good for deployment. The issue
with this approach is the applicability statement of EAP.

--Gerardo

=20
>  - DHCPv6 has some constraints which are not explained in
>    the document (cf my previous messages)
>=20
>  - I don't know if the OPTION_MIP6-RELAY-Option is necessary, i.e.,
>    why not use the RADIUS-RELAY-Option (aka RRAO) ?
>    (cf. draft-ietf-dhc-v6-relay-radius-01.txt)
>=20
>  - Security Considerations reference RFC which are not for DHCPv6,
>    i.e., the right reference is RFC 3315.
>=20
>  - DHCPv6 security doesn't work well in multi-domain environments
>    so in the mobility context. Quoting RFC 3118:
>=20
>    The "delayed authentication" protocol does not attempt to address
>    situations where a client may roam from one administrative=20
> domain to
>    another, i.e., interdomain roaming.  This protocol is focused on
>    solving the intradomain problem where the out-of-band exchange of a
>    shared secret is feasible.
>=20
>    and:
>=20
>       Delayed authentication requires a shared secret key for each
>       client on each DHCP server with which that client may=20
> wish to use
>       the DHCP protocol.  Each secret key has a unique identifier that
>       can be used by a receiver to determine which secret was used to
>       generate the MAC in the DHCP message.  Therefore, delayed
>       authentication may not scale well in an architecture in which a
>       DHCP client connects to multiple administrative domains.
>=20
>  - IMHO this paragraph is not sound:
>=20
>    The communication between the DHCP client and the DHCP=20
> server for the
>    exchange of home agent information is security sensitive=20
> and requires
>    authentication, integrity and replay protection.  Either=20
> lower-layer
>    security (such as link layer security established as part of the
>    network access authentication protocol run) or DHCP security
>    [RFC3118] can be used.  The latter approach is only applicable in
>    non-roaming environments due to the limited applicability=20
> of the DHCP
>    security mechanisms.  An adversary that is able to modify=20
> home agent
>    information can force the mobile node to use a different home agent
>    than intended by the MSA.  However, this type of attack can be
>    detected by the security mechanism between the mobile node and the
>    home agent.
>=20
>=20
>  - to finish the document presents the less aggressive scheme to use
>    AAA in MIPv6 bootstrapping, i.e., it only assigns the HA. I have
>    a concern about this because AAA is the only practical way to
>    attach security properties (i.e., a proof it is not fake) to
>    the care-of address so to improve the MIPv6 security.
>    Unfortunately the document does nothing for this...
>=20
> Regards
>=20
> Francis.Dupont@enst-bretagne.fr
>=20
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
>=20


Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia =
S.p.A.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
CONFIDENTIALITY NOTICE
This message and its attachments are addressed solely to the persons
above and may contain confidential information. If you have received
the message in error, be informed that any use of the content hereof
is prohibited. Please return it immediately to the sender and delete
the message. Should you have any questions, please send an e_mail to
MailAdmin@tilab.com. Thank you
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

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



From mip6-bounces@ietf.org Wed Oct 26 10:06:17 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUluz-0000ES-6Q; Wed, 26 Oct 2005 10:06:17 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUlux-0000CU-N5
	for mip6@megatron.ietf.org; Wed, 26 Oct 2005 10:06:15 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21703
	for <mip6@ietf.org>; Wed, 26 Oct 2005 10:06:00 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUm86-0002oi-Fu
	for mip6@ietf.org; Wed, 26 Oct 2005 10:19:52 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id j9QE5QA08504; Wed, 26 Oct 2005 16:05:26 +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
	j9QE5QqH013977; Wed, 26 Oct 2005 16:05:26 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200510261405.j9QE5QqH013977@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Julien Bournelle <julien.bournelle@int-evry.fr>
Subject: Re: [Mip6] General comments/questions on MIPv6 bootstrapping 
In-reply-to: Your message of Wed, 26 Oct 2005 15:26:21 +0200.
	<20051026132621.GS16237@ipv6-3.int-evry.fr> 
Date: Wed, 26 Oct 2005 16:05:26 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc: mip6@ietf.org,
	COMBES Jean-Michel RD-MAPS-ISS <jeanmichel.combes@francetelecom.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

    just a comment concerning AAA inline,
   
   On Wed, Oct 26, 2005 at 02:46:59PM +0200, Francis Dupont wrote:
   
   <snip>
   
   >  - to finish the document presents the less aggressive scheme to use
   >    AAA in MIPv6 bootstrapping, i.e., it only assigns the HA. I have
   >    a concern about this because AAA is the only practical way to
   >    attach security properties (i.e., a proof it is not fake) to
   >    the care-of address so to improve the MIPv6 security.
   >    Unfortunately the document does nothing for this...
   
    the problem with doing what you proposed is the following:
   
    - or you have to modified all the MN-NAS protocol (e.g. 802.1X/PANA) to
    support bootstrapping Mobile IPv6
   
    - or you may use EAP and in this case we have an Applicability problem:
      EAP is not for configuration and EAP may not be in use in the access
      network.
   
=> a la JFK: we choose to do this and the other things, not because
they are easy... (BTW I prefer faster than in this decade :-).
   
Regards

Francis.Dupont@enst-bretagne.fr

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



From mip6-bounces@ietf.org Wed Oct 26 10:14:21 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUm2n-0008LC-TB; Wed, 26 Oct 2005 10:14:21 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUm2n-0008KF-7B
	for mip6@megatron.ietf.org; Wed, 26 Oct 2005 10:14:21 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22327
	for <mip6@ietf.org>; Wed, 26 Oct 2005 10:14:06 -0400 (EDT)
Received: from dns2.tilab.com ([163.162.42.5])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUmFx-00038g-4j
	for mip6@ietf.org; Wed, 26 Oct 2005 10:27:58 -0400
Received: from iowa2k01b.cselt.it ([163.162.242.202])
	by dns2.cselt.it (PMDF V6.1 #38895)
	with ESMTP id <0IOZ00L3W0VMZA@dns2.cselt.it> for mip6@ietf.org; Wed,
	26 Oct 2005 16:14:10 +0200 (MEST)
Received: from EXC01B.cselt.it ([163.162.4.199]) by iowa2k01b.cselt.it with
	Microsoft SMTPSVC(6.0.3790.211); Wed, 26 Oct 2005 16:11:48 +0200
Date: Wed, 26 Oct 2005 16:14:06 +0200
From: Gerardo Giaretta <Gerardo.Giaretta@TILAB.COM>
Subject: RE: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
To: Kilian Weniger <Kilian.Weniger@eu.panasonic.com>
Message-id: <DA62A6E0CDD1B34A84557FF1AC850C57016E9CE8@EXC01B.cselt.it>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.3790.326
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: quoted-printable
Importance: normal
Priority: normal
Thread-Topic: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
thread-index: AcXYqXbXIA/i8BXYScS1SYiWXuH9KAAAVacgAAMu7pAAH2NZIAALuRIgAAHKS9AAMwznEA==
Content-Class: urn:content-classes:message
X-OriginalArrivalTime: 26 Oct 2005 14:11:48.0562 (UTC)
	FILETIME=[344FAB20:01C5DA37]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Content-Transfer-Encoding: quoted-printable
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Hi Kilian,=20

> > > 2. The MN starts anycast-based HA discovery (not necessarily=20
> > > as defined
> > > in RFC3775) using the discovered HA prefix to get the HA=20
> > address. This
> > > can support fine-grained load balancing between HAs on the=20
> > > same link and
> > > thus results in fast and efficient HA discovery (since=20
> subsequent HA
> > > re-assignment for load balancing is not necessarily required). A
> > > possible secure and efficient method could be the IKE=20
> > Security Gateway
> > > discovery/assignment mechanism mentioned by Francis.
> > >=20
> >=20
> > A similar approach was discussed in the DT: the MN could get=20
> > a HA prefix
> > via DNS and then perform DHAAD. However, we agreed that a=20
> > pure DNS-based
> > mechanism is better and does not have security concerns as DHAAD.=20
>=20
> O.k., I see. Can you recall the reasons, why a pure DNS-based=20
> mechanism
> was considered better?=20
> Any reasons apart from the ICMP and security issue?

Those were the main reasons. Moreover we agreed that in split scenario
the DNS-based solution with unicast address is good enough.

Regards,
--Gerardo

>=20
> Note that it would be possible to use an anycast-based discovery
> mechanism=20
> different from RFC3775 DHAAD, which is secure (e.g., the=20
> IKE Security Gateway discovery/assignment mechanism mentioned by
> Francis) and which doesn't=20
> have the deployment (ICMP) issue.
>=20
> >=20
> >=20
> > > 3. When load conditions change dramatically or the HA=20
> crashs, the MN
> > > changes its HA using an HA-switch mechanism (this mechanism=20
> > could also
> > > provide an optional fine-grained load balancing between HAs=20
> > > of different
> > > subnets).
> > >
> >=20
> > I would simplify the procedure a bit: get rid of DHAAD and=20
> > use HA switch
> > when a HA re-assignment is needed for any reason (e.g. load=20
> > balancing).
>=20
> O.k., I think it's just a matter of efficiency.=20
> Without RFC3775 DHAAD, an additional HA-switch might be needed after
> every bootstrapping.
> I agree with Francis that the "real world" requirements for load
> balancing must be known=20
> to be able to make a good decision.
>=20
> Regards,
>=20
> Kilian
>=20
>=20


Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia =
S.p.A.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
CONFIDENTIALITY NOTICE
This message and its attachments are addressed solely to the persons
above and may contain confidential information. If you have received
the message in error, be informed that any use of the content hereof
is prohibited. Please return it immediately to the sender and delete
the message. Should you have any questions, please send an e_mail to
MailAdmin@tilab.com. Thank you
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

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



From mip6-bounces@ietf.org Wed Oct 26 10:15:41 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUm44-0000Fe-U6; Wed, 26 Oct 2005 10:15:40 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUm43-0000Ef-Gv
	for mip6@megatron.ietf.org; Wed, 26 Oct 2005 10:15:39 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22425
	for <mip6@ietf.org>; Wed, 26 Oct 2005 10:15:24 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUmH9-0003B5-AA
	for mip6@ietf.org; Wed, 26 Oct 2005 10:29:16 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id j9QEEgA09494; Wed, 26 Oct 2005 16:14: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
	j9QEEgJK014047; Wed, 26 Oct 2005 16:14:42 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200510261414.j9QEEgJK014047@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Gerardo Giaretta <Gerardo.Giaretta@tilab.com>
Subject: Re: [Mip6] General comments/questions on MIPv6 bootstrapping 
In-reply-to: Your message of Wed, 26 Oct 2005 15:56:51 +0200.
	<DA62A6E0CDD1B34A84557FF1AC850C57016E9CE7@EXC01B.cselt.it> 
Date: Wed, 26 Oct 2005 16:14:42 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   > This is a review of 
   > draft-ietf-mip6-bootstrapping-integrated-dhc-00.txt:
   > 
   >  - in fact the document can (should?) be split into 2 parts:
   >    the AAA stuff and the DHCP stuff. IMHO the important part
   >    is the AAA one because it comes directly from the "integrated"
   >    scenario, DHCP is used only to transmit the AAA results to
   >    the MN. One can use in some cases the access control protocol,
   >    for instance if it is 802.1X.
   >
   
   I believe that AAA is also the most pratcial way to perform HA
   assignment.
   
=> yes, AAA is very fine:
 - more capability (it can assign all addresses)
 - more efficient (if it is used for piggybacking other things in it)
 - more secure (cf my concern).

   I think modifying 802.1X is tricky. An extension to PANA may be easier.
   Another approach is the usage of EAP between MN and AAA for HA
   assignment. This has also the advantage that it does not imply
   extensions to network access and this is good for deployment. The issue
   with this approach is the applicability statement of EAP.
   
=> Julien has just done the same comment. IMHO the security improvment
is the key, i.e., operators won't be happy if we can solve a security
issue (protect against fake CoA) but don't.
BTW I'd like to know the real world probability to be in the
integrated scenario for MIPv6 and for NEMO...
   
Regards

Francis.Dupont@enst-bretagne.fr

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



From mip6-bounces@ietf.org Wed Oct 26 10:19:45 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUm81-0001K6-NM; Wed, 26 Oct 2005 10:19:45 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUm80-0001Jb-H0
	for mip6@megatron.ietf.org; Wed, 26 Oct 2005 10:19:44 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22680
	for <mip6@ietf.org>; Wed, 26 Oct 2005 10:19:29 -0400 (EDT)
Received: from dns1.tilab.com ([163.162.42.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUmLA-0003KN-7x
	for mip6@ietf.org; Wed, 26 Oct 2005 10:33:21 -0400
Received: from iowa2k01a.cselt.it ([163.162.242.201])
	by dns1.cselt.it (PMDF V6.0-025 #38895)
	with ESMTP id <0IOZ0067S14HXC@dns1.cselt.it> for mip6@ietf.org; Wed,
	26 Oct 2005 16:19:29 +0200 (MEST)
Received: from EXC01B.cselt.it ([163.162.4.199]) by iowa2k01a.cselt.it with
	Microsoft SMTPSVC(6.0.3790.211); Wed, 26 Oct 2005 16:19:28 +0200
Date: Wed, 26 Oct 2005 16:19:28 +0200
From: Gerardo Giaretta <Gerardo.Giaretta@TILAB.COM>
Subject: RE: [Mip6] General comments/questions on MIPv6 bootstrapping
To: Francis.Dupont@enst-bretagne.fr
Message-id: <DA62A6E0CDD1B34A84557FF1AC850C57016E9CE9@EXC01B.cselt.it>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.3790.326
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: quoted-printable
Importance: normal
Priority: normal
Thread-Topic: [Mip6] General comments/questions on MIPv6 bootstrapping
thread-index: AcXaN8Kqv6bpog0nRQ6pmjjBxVZyNgAABCKw
Content-Class: urn:content-classes:message
X-OriginalArrivalTime: 26 Oct 2005 14:19:28.0975 (UTC)
	FILETIME=[46BD1DF0:01C5DA38]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
Content-Transfer-Encoding: quoted-printable
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

>  In your previous mail you wrote:
>=20
>    > This is a review of=20
>    > draft-ietf-mip6-bootstrapping-integrated-dhc-00.txt:
>    >=20
>    >  - in fact the document can (should?) be split into 2 parts:
>    >    the AAA stuff and the DHCP stuff. IMHO the important part
>    >    is the AAA one because it comes directly from the "integrated"
>    >    scenario, DHCP is used only to transmit the AAA results to
>    >    the MN. One can use in some cases the access control protocol,
>    >    for instance if it is 802.1X.
>    >
>   =20
>    I believe that AAA is also the most pratcial way to perform HA
>    assignment.
>   =20
> =3D> yes, AAA is very fine:
>  - more capability (it can assign all addresses)
>  - more efficient (if it is used for piggybacking other things in it)
>  - more secure (cf my concern).
>

Agree. This is why I have been proposing EAP approach in the past.
=20
>    I think modifying 802.1X is tricky. An extension to PANA=20
> may be easier.
>    Another approach is the usage of EAP between MN and AAA for HA
>    assignment. This has also the advantage that it does not imply
>    extensions to network access and this is good for=20
> deployment. The issue
>    with this approach is the applicability statement of EAP.
>   =20
> =3D> Julien has just done the same comment. IMHO the security =
improvment
> is the key, i.e., operators won't be happy if we can solve a security
> issue (protect against fake CoA) but don't.
> BTW I'd like to know the real world probability to be in the
> integrated scenario for MIPv6 and for NEMO...
>

Integrated scenario: MSA=3D=3DASA and this is the most common case for =
any
mobile operator.=20

--Gerardo

   =20
> Regards
>=20
> Francis.Dupont@enst-bretagne.fr
>=20


Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia =
S.p.A.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
CONFIDENTIALITY NOTICE
This message and its attachments are addressed solely to the persons
above and may contain confidential information. If you have received
the message in error, be informed that any use of the content hereof
is prohibited. Please return it immediately to the sender and delete
the message. Should you have any questions, please send an e_mail to=20
MailAdmin@tilab.com. Thank you
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

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



From mip6-bounces@ietf.org Wed Oct 26 10:38:40 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUmQK-0004Mu-0r; Wed, 26 Oct 2005 10:38:40 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUmQD-0004Mf-V4
	for mip6@megatron.ietf.org; Wed, 26 Oct 2005 10:38:38 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23933
	for <mip6@ietf.org>; Wed, 26 Oct 2005 10:38:18 -0400 (EDT)
Received: from dns2.tilab.com ([163.162.42.5])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUmdP-0003xH-4X
	for mip6@ietf.org; Wed, 26 Oct 2005 10:52:11 -0400
Received: from iowa2k01b.cselt.it ([163.162.242.202])
	by dns2.cselt.it (PMDF V6.1 #38895)
	with ESMTP id <0IOZ00N682002T@dns2.cselt.it> for mip6@ietf.org; Wed,
	26 Oct 2005 16:38:24 +0200 (MEST)
Received: from EXC01B.cselt.it ([163.162.4.199]) by iowa2k01b.cselt.it with
	Microsoft SMTPSVC(6.0.3790.211); Wed, 26 Oct 2005 16:36:01 +0200
Date: Wed, 26 Oct 2005 16:37:18 +0200
From: Gerardo Giaretta <Gerardo.Giaretta@TILAB.COM>
Subject: RE: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
To: Vijay Devarapalli <vijayd@iprg.nokia.com>
Message-id: <DA62A6E0CDD1B34A84557FF1AC850C57016E9CEA@EXC01B.cselt.it>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.3790.326
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: quoted-printable
Importance: normal
Priority: normal
Thread-Topic: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
thread-index: AcXZuEJAAKF7330MS2uAddiTR4NGuAAgdXWA
Content-Class: urn:content-classes:message
X-OriginalArrivalTime: 26 Oct 2005 14:36:01.0984 (UTC)
	FILETIME=[969E4400:01C5DA3A]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Content-Transfer-Encoding: quoted-printable
Cc: mip6@ietf.org, Kilian Weniger <Kilian.Weniger@eu.panasonic.com>,
	James Kempf <Kempf@docomolabs-usa.com>,
	Francis Dupont <Francis.Dupont@enst-bretagne.fr>,
	Petrescu Alexandru-AAP021 <alexandru.petrescu@motorola.com>,
	COMBES Jean-Michel RD-MAPS-ISS <jeanmichel.combes@francetelecom.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org


> >>Agree. But I think a operator must have the possibility to=20
> >>assign the HA
> >>in any cases.
> >>
> >=20
> >=20
> > DHCP-based solution seems to achieve this. Do you see any=20
> issue on that?
>=20
> yes. DHCP based solution would require the Operator to
> first update the access network too. what many operators
> would like to do (initially atleast) is to just plug in
> a HA and introduce new mobile devices that can use the
> new features. no upgrades anywhere else.
>=20

Fully agree.

--Gerardo

> Vijay
>=20
>=20


Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia =
S.p.A.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
CONFIDENTIALITY NOTICE
This message and its attachments are addressed solely to the persons
above and may contain confidential information. If you have received
the message in error, be informed that any use of the content hereof
is prohibited. Please return it immediately to the sender and delete
the message. Should you have any questions, please send an e_mail to
MailAdmin@tilab.com. Thank you
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

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



From mip6-bounces@ietf.org Wed Oct 26 10:38:45 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUmQP-0004NZ-78; Wed, 26 Oct 2005 10:38:45 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUmQN-0004NU-QV
	for mip6@megatron.ietf.org; Wed, 26 Oct 2005 10:38:43 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23941
	for <mip6@ietf.org>; Wed, 26 Oct 2005 10:38:28 -0400 (EDT)
Received: from atlrel6.hp.com ([156.153.255.205])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUmdV-0003xg-J6
	for mip6@ietf.org; Wed, 26 Oct 2005 10:52:21 -0400
Received: from taynzmail03.nz-tay.cpqcorp.net (compaqtay.compaq.com
	[16.47.4.103]) by atlrel6.hp.com (Postfix) with ESMTP id 52D4411EC0;
	Wed, 26 Oct 2005 10:38:36 -0400 (EDT)
Received: from kitche.zk3.dec.com (kitche1.zk3.dec.com [16.140.160.161])
	by taynzmail03.nz-tay.cpqcorp.net (Postfix) with ESMTP id 0909F11DF;
	Wed, 26 Oct 2005 10:38:36 -0400 (EDT)
Received: from [16.116.104.135] by kitche.zk3.dec.com
	(8.11.1/1.1.27.5/27Oct00-1235PM)
	id j9QEcYc0000683711; Wed, 26 Oct 2005 10:38:35 -0400 (EDT)
Message-ID: <435F94EA.8000103@hp.com>
Date: Wed, 26 Oct 2005 10:38:34 -0400
From: Brian Haley <brian.haley@hp.com>
Organization: Open Source and Linux Organization
User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051010)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
Subject: Re: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
References: <200510260815.j9Q8FrkE011748@givry.rennes.enst-bretagne.fr>
In-Reply-To: <200510260815.j9Q8FrkE011748@givry.rennes.enst-bretagne.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Content-Transfer-Encoding: 7bit
Cc: mip6@ietf.org, Kilian Weniger <Kilian.Weniger@eu.panasonic.com>,
	Vijay Devarapalli <vijayd@iprg.nokia.com>,
	James Kempf <Kempf@docomolabs-usa.com>,
	Petrescu Alexandru-AAP021 <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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

I finally caught-up on this thread :)

Francis Dupont wrote:
>    so maybe we need to sit back and relax a bit. wait
>    and see how MIPv6 is deployed and then develop
>    solutions that might actually be used. :)
>    
> => there is at least an operator asking for HA assignment and
> I believe we can get a consensus about the fact that HA assignment
> is better than HA discovery.

I believe there is also at least one operator asking for HA 
re-assignment, which was one reason for the ha-switch draft.

I do agree we need more input from our "customers", I surely don't want 
to invest any time in a draft that never gets used, but we've got to put 
a few basic tools in the MIPv6 toolbag.

-Brian

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



From mip6-bounces@ietf.org Wed Oct 26 10:45:56 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUmXM-0007V4-Px; Wed, 26 Oct 2005 10:45:56 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUmXK-0007QH-7z
	for mip6@megatron.ietf.org; Wed, 26 Oct 2005 10:45:54 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA24294
	for <mip6@ietf.org>; Wed, 26 Oct 2005 10:45:38 -0400 (EDT)
Received: from motgate3.mot.com ([144.189.100.103])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUmkO-00049E-Pc
	for mip6@ietf.org; Wed, 26 Oct 2005 10:59:31 -0400
Received: from az33exr03.mot.com (az33exr03.mot.com [10.64.251.233])
	by motgate3.mot.com (8.12.11/Motgate3) with ESMTP id j9QF1RO8006793
	for <mip6@ietf.org>; Wed, 26 Oct 2005 08:01:27 -0700 (MST)
Received: from de01exm69.ds.mot.com (de01exm69.am.mot.com [10.176.8.25])
	by az33exr03.mot.com (8.13.1/8.13.0) with ESMTP id j9QEstx8016744
	for <mip6@ietf.org>; Wed, 26 Oct 2005 09:54:55 -0500 (CDT)
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] load balancing and HA (re-)assignment : which WG is
	theright venue ?
Date: Wed, 26 Oct 2005 10:45:35 -0400
Message-ID: <0B40B6F9CB990B428819561A2A55613A144DEE@de01exm69.ds.mot.com>
Thread-Topic: [Mip6] load balancing and HA (re-)assignment : which WG is
	theright venue ?
Thread-Index: AcXaGCQ4puFU8ORRT/CmQBm9l0M4EAAI7Mng
From: "Narayanan Vidya-CVN065" <vidya@motorola.com>
To: "Thierry Ernst" <ernst@sfc.wide.ad.jp>, <mip6@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 14582b0692e7f70ce7111d04db3781c8
Content-Transfer-Encoding: quoted-printable
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Maybe I am missing something fundamental - what does HA assignment/load
balancing/re-assignment have to do with multi-homing?=20

Vidya=20

> -----Original Message-----
> From: mip6-bounces@ietf.org [mailto:mip6-bounces@ietf.org] On=20
> Behalf Of Thierry Ernst
> Sent: Wednesday, October 26, 2005 5:18 AM
> To: mip6@ietf.org
> Subject: Re: [Mip6] load balancing and HA (re-)assignment :=20
> which WG is theright venue ?
>=20
>=20
>=20
> > > Probably yes, but how the MIP6 group will consider the NEMO=20
> > > specificities ? Isn't this also confusing for the group ?
> >=20
> > Me deviating... I agree that the MIP6 WG should somehow consult the=20
> > NEMO WG with respect to NEMO specificities.
>=20
> > > Monami6 has 4 items. How many for MIP6 ?
> >=20
> > Well, current charter mentions 8 milestones, 17 I-Ds, 2=20
> RFCs (subject=20
> > to update at the meeting).
> >=20
> > Monami6 has 4 milestones.  I personally believe that is focused and=20
> > motivating.
> >=20
> > >> I would like to get a sense of the WG regarding this point.
> > >>=20
> > >> I think we will have sufficient time at Vancounver to add such a=20
> > >> discussion on the Monami6 agenda if someone want to lead it.
> > >>=20
> > >> =3D> agenda sharing is enough issue. One can believe it is=20
> fine (it=20
> > >> gives more time) but past experiences are not good (duplicate=20
> > >> items, more likely schedule conflicts, etc).
> > >=20
> > > This is exactly why everything related to multihoming in=20
> MIP6/NEMO=20
> > > should be moved to Monami6, particularly when it concerns=20
> both MIP6=20
> > > and NEMO.
> >=20
> > But which monami6 WG Deliverable?  The closest I could find is=20
> > "Flow/binding policies exchange" but this terminology has not been=20
> > discussed at all here.
>=20
> Actually, why not ? I was thinking about a new deliverable=20
> (because it's clearer), but debating the exact features may=20
> well lead us to consider HA-reassigment in any of the solutions.=20
>=20
> What I mean is that even if HA-reassignment is done in MIP6,=20
> both HA-reasssigment, multiple CoA registration, and policies=20
> exchanges have to be compatible.=20
>=20
> By the way, I would like to point to issue "HA=20
> synchronization" of draft-ietf-nemo-multihoming-issues.=20
>=20
> > During Monami6 BoF it was discussed thoroughly what exactly=20
> should the=20
> > WG work on so a Charter was issued.  Is the Monami6 trying=20
> to modify=20
> > its Charter with new items so quickly after creation?
>=20
> Why not ?
>=20
> Well, adding a new item would require Monami6 to be=20
> rechartered if that given work doesn't correspond to the=20
> charter. But there is no rules at the IETF that a WG just=20
> approved cannot be rechartered, so this is not a dead end,=20
> and I wouldn't mind to negociate that if this is the sense of=20
> the MIP6/NEMO/MONAMI6 WG that this is the right thing to do.
>=20
> But, I don't think this wouldn't be a dramatic change to the charter..
>=20
> My personal view on all of this is that working on this topic=20
> in Monami6 would make it easier for everyone, the IETFers,=20
> and the people interested in the standards defined by the IETF.
>=20
> Thierry
>=20
>=20
>=20
>=20
>=20
>=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 Wed Oct 26 10:51:14 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUmcU-0002eX-5A; Wed, 26 Oct 2005 10:51:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUmcS-0002e5-3p
	for mip6@megatron.ietf.org; Wed, 26 Oct 2005 10:51:12 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA24666
	for <mip6@ietf.org>; Wed, 26 Oct 2005 10:50:56 -0400 (EDT)
Received: from mout.perfora.net ([217.160.230.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUmpb-0004LL-4K
	for mip6@ietf.org; Wed, 26 Oct 2005 11:04:49 -0400
Received: from [85.101.251.215] (helo=Alperyegin)
	by mrelay.perfora.net with ESMTP (Nemesis),
	id 0MKoyl-1EUmcH1ma9-000161; Wed, 26 Oct 2005 10:51:01 -0400
From: "Alper Yegin" <alper.yegin@yegin.org>
To: "'Francis Dupont'" <Francis.Dupont@enst-bretagne.fr>,
	"'COMBES Jean-Michel RD-MAPS-ISS'" <jeanmichel.combes@francetelecom.com>
Subject: RE: [Mip6] General comments/questions on MIPv6 bootstrapping 
Date: Wed, 26 Oct 2005 17:50:54 +0300
Message-ID: <001201c5da3c$af1b1dd0$0302a8c0@Alperyegin>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
In-reply-to: <200510261246.j9QCkxXL013329@givry.rennes.enst-bretagne.fr>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
Importance: Normal
X-Provags-ID: perfora.net abuse@perfora.net
	login:abf7a4bb310ea4dfc9b6841113e2970f
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
Content-Transfer-Encoding: 7bit
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

>  - DHCPv6 security doesn't work well in multi-domain environments
>    so in the mobility context. Quoting RFC 3118:
> 
>    The "delayed authentication" protocol does not attempt to address
>    situations where a client may roam from one administrative domain
to
>    another, i.e., interdomain roaming.  This protocol is focused on
>    solving the intradomain problem where the out-of-band exchange of a
>    shared secret is feasible.
> 
>    and:
> 
>       Delayed authentication requires a shared secret key for each
>       client on each DHCP server with which that client may wish to
use
>       the DHCP protocol.  Each secret key has a unique identifier that
>       can be used by a receiver to determine which secret was used to
>       generate the MAC in the DHCP message.  Therefore, delayed
>       authentication may not scale well in an architecture in which a
>       DHCP client connects to multiple administrative domains.


Yes, these are right. But, is there any specifics of the DHCP usage
outlined in this document that relates to the above discussion? Whatever
DHCP security or insecurity exists apply to this usage as well.


>  - IMHO this paragraph is not sound:
> 
>    The communication between the DHCP client and the DHCP server for
the
>    exchange of home agent information is security sensitive and
requires
>    authentication, integrity and replay protection.  Either
lower-layer
>    security (such as link layer security established as part of the
>    network access authentication protocol run) or DHCP security
>    [RFC3118] can be used.  The latter approach is only applicable in
>    non-roaming environments due to the limited applicability of the
DHCP
>    security mechanisms.  An adversary that is able to modify home
agent
>    information can force the mobile node to use a different home agent
>    than intended by the MSA.  However, this type of attack can be
>    detected by the security mechanism between the mobile node and the
>    home agent.

If you can point out the specific issue, that'd be better.

>  - to finish the document presents the less aggressive scheme to use
>    AAA in MIPv6 bootstrapping, i.e., it only assigns the HA. I have
>    a concern about this because AAA is the only practical way to
>    attach security properties (i.e., a proof it is not fake) to
>    the care-of address so to improve the MIPv6 security.
>    Unfortunately the document does nothing for this...

CoA ownership issue is outside the scope of "MIP6 bootstrapping"
problem.

Alper




> 
> Regards
> 
> Francis.Dupont@enst-bretagne.fr
> 
> _______________________________________________
> 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 Oct 26 11:42:47 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUnQN-000588-7j; Wed, 26 Oct 2005 11:42:47 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUnQL-00057h-SQ
	for mip6@megatron.ietf.org; Wed, 26 Oct 2005 11:42:46 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02050
	for <mip6@ietf.org>; Wed, 26 Oct 2005 11:42:30 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUndW-0007Xh-GM
	for mip6@ietf.org; Wed, 26 Oct 2005 11:56:23 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id j9QFgJr18605; Wed, 26 Oct 2005 17:42:19 +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
	j9QFgJbc014569; Wed, 26 Oct 2005 17:42:19 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200510261542.j9QFgJbc014569@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: "Alper Yegin" <alper.yegin@yegin.org>
Subject: Re: [Mip6] General comments/questions on MIPv6 bootstrapping 
In-reply-to: Your message of Wed, 26 Oct 2005 17:50:54 +0300.
	<001201c5da3c$af1b1dd0$0302a8c0@Alperyegin> 
Date: Wed, 26 Oct 2005 17:42:19 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Cc: mip6@ietf.org,
	'COMBES Jean-Michel RD-MAPS-ISS' <jeanmichel.combes@francetelecom.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   >  - DHCPv6 security doesn't work well in multi-domain environments
   >    so in the mobility context. Quoting RFC 3118:...
   
   Yes, these are right. But, is there any specifics of the DHCP usage
   outlined in this document that relates to the above discussion? Whatever
   DHCP security or insecurity exists apply to this usage as well.
   
=> the document recommends DHCPv6 in a context where its security
can't be insured. IMHO this is a major issue.

   >  - IMHO this paragraph is not sound:

=> s/sound/consistent/?

   >    The communication between the DHCP client and the DHCP server for
   ...
   
=> the paragraph begins by "security sensitive" and "requires".
The proposed solutions are lower-layer security, something which can't
be assumed to be always available, and DHCPv6 security, which doesn't
work well in the context (this is my previous comment). It finishes
by explaining the security in fact doesn't matter: this is both
arguable (security matters soon or late, and HA assignment is more
vulnerable then HA discovery) and not consistent with the
beginning.

   >    I have
   >    a concern about this because AAA is the only practical way to
   >    attach security properties (i.e., a proof it is not fake) to
   >    the care-of address so to improve the MIPv6 security.
   >    Unfortunately the document does nothing for this...
   
   CoA ownership issue is outside the scope of "MIP6 bootstrapping"
   problem.
   
=> so we have to find a way to put it inside! Note we have CoA
authentication by a trusted third party, a bit more than ownership.   
   
Regards

Francis.Dupont@enst-bretagne.fr

PS: this is a bit strange: everybody seem to agree that AAA can provide
many good things and at the result it gives only the very minimum...
Perhaps what is wanted is a HA assignment in IKEv2 (making bootstrapping
current work useless) ? cf my checking message in the IPsec list:
http://msgs.securepoint.com/cgi-bin/get/ipsec-0510/26.html

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



From mip6-bounces@ietf.org Wed Oct 26 14:22:21 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUpum-0004gv-Sn; Wed, 26 Oct 2005 14:22:20 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUpul-0004gn-TT
	for mip6@megatron.ietf.org; Wed, 26 Oct 2005 14:22:19 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11757
	for <mip6@ietf.org>; Wed, 26 Oct 2005 14:22:05 -0400 (EDT)
Received: from mout.perfora.net ([217.160.230.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUq7x-0004H3-Un
	for mip6@ietf.org; Wed, 26 Oct 2005 14:35:59 -0400
Received: from [85.101.251.215] (helo=Alperyegin)
	by mrelay.perfora.net with ESMTP (Nemesis),
	id 0MKoyl-1EUpuc2wJ6-00009m; Wed, 26 Oct 2005 14:22:10 -0400
From: "Alper Yegin" <alper.yegin@yegin.org>
To: <Francis.Dupont@enst-bretagne.fr>
Subject: RE: [Mip6] General comments/questions on MIPv6 bootstrapping 
Date: Wed, 26 Oct 2005 21:22:03 +0300
Message-ID: <000001c5da5a$2dbbee90$0302a8c0@Alperyegin>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
Importance: Normal
In-Reply-To: <200510261542.j9QFgJbc014569@givry.rennes.enst-bretagne.fr>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Provags-ID: perfora.net abuse@perfora.net
	login:abf7a4bb310ea4dfc9b6841113e2970f
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f66b12316365a3fe519e75911daf28a8
Content-Transfer-Encoding: 7bit
Cc: mip6@ietf.org,
	'COMBES Jean-Michel RD-MAPS-ISS' <jeanmichel.combes@francetelecom.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

>  In your previous mail you wrote:
> 
>    >  - DHCPv6 security doesn't work well in multi-domain environments
>    >    so in the mobility context. Quoting RFC 3118:...
> 
>    Yes, these are right. But, is there any specifics of the DHCP usage
>    outlined in this document that relates to the above discussion?
> Whatever
>    DHCP security or insecurity exists apply to this usage as well.
> 
> => the document recommends DHCPv6 in a context where its security
> can't be insured. IMHO this is a major issue.

Actually, what we tried to say was "secure your DHCP in whatever way you
are securing it." Just because you are carrying an HA information does
not require that the DHCP signaling be more or less secured than what
the operator does normally. 

If you agree to that, and have a better way to capture in the document,
please propose some text.

[For DHCP security, the operator may rely on lower-layer security, or
some other mechanism, e.g., draft-yegin-eap-boot-rfc3118-00.txt, etc.]


> 
>    >  - IMHO this paragraph is not sound:
> 
> => s/sound/consistent/?
> 
>    >    The communication between the DHCP client and the DHCP server
for
>    ...
> 
> => the paragraph begins by "security sensitive" and "requires".
> The proposed solutions are lower-layer security, something which can't
> be assumed to be always available, 

Many, if not all, deployments rely on lower-layer security. This is
mostly an architectural issue. DSL operators know that the DHCP is run
over physically-secured lines, hence the current deployments don't
involved DHCP-level security....

> and DHCPv6 security, which doesn't
> work well in the context (this is my previous comment). It finishes
> by explaining the security in fact doesn't matter: this is both
> arguable (security matters soon or late, and HA assignment is more
> vulnerable then HA discovery) and not consistent with the
> beginning.

I see your point. The text is inconsistent.

> 
>    >    I have
>    >    a concern about this because AAA is the only practical way to
>    >    attach security properties (i.e., a proof it is not fake) to
>    >    the care-of address so to improve the MIPv6 security.
>    >    Unfortunately the document does nothing for this...
> 
>    CoA ownership issue is outside the scope of "MIP6 bootstrapping"
>    problem.
> 
> => so we have to find a way to put it inside! Note we have CoA
> authentication by a trusted third party, a bit more than ownership.

Sorry I don't understand. Why do you see this issue as part of the "MIP6
bootstrapping problem", which deals with HA, HoA, MN-HA SA
configuration?


> 
> Regards
> 
> Francis.Dupont@enst-bretagne.fr
> 
> PS: this is a bit strange: everybody seem to agree that AAA can
provide
> many good things and at the result it gives only the very minimum...
> Perhaps what is wanted is a HA assignment in IKEv2 (making
bootstrapping
> current work useless) ? cf my checking message in the IPsec list:
> http://msgs.securepoint.com/cgi-bin/get/ipsec-0510/26.html

Do you mind briefly stating why you think this is better than the DNS
and DHCP-based HA discovery/assignment?

Alper




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



From mip6-bounces@ietf.org Wed Oct 26 14:42:40 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUqES-0000jL-Mn; Wed, 26 Oct 2005 14:42:40 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUqEQ-0000j7-Ry
	for mip6@megatron.ietf.org; Wed, 26 Oct 2005 14:42:39 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13438
	for <mip6@ietf.org>; Wed, 26 Oct 2005 14:42:24 -0400 (EDT)
Received: from mx0.starentnetworks.com ([12.38.223.203])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUqRd-00055m-S7
	for mip6@ietf.org; Wed, 26 Oct 2005 14:56:18 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mx0.starentnetworks.com (Postfix) with ESMTP id 164E39000B;
	Wed, 26 Oct 2005 14:42:28 -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 21737-09; Wed, 26 Oct 2005 14:42:26 -0400 (EDT)
Received: from ames.starentnetworks.com (ames.starentnetworks.com
	[12.33.235.15]) by mx0.starentnetworks.com (Postfix) with ESMTP;
	Wed, 26 Oct 2005 14:42:26 -0400 (EDT)
X-MessageTextProcessor: DisclaimIt (2.50.252) [Starent Networks Corp.]
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
Importance: normal
Priority: normal
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] General comments/questions on MIPv6 bootstrapping 
Date: Wed, 26 Oct 2005 14:42:26 -0400
Message-ID: <8A16DAD84432534FBFC19FD92B50512F035D92CE@ames.starentnetworks.com>
Thread-Topic: [Mip6] General comments/questions on MIPv6 bootstrapping 
thread-index: AcXaLZaFRtKoWuHOQU+kryErNoXubAAK4Ung
From: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
To: "Francis Dupont" <Francis.Dupont@enst-bretagne.fr>,
	"COMBES Jean-Michel RD-MAPS-ISS" <jeanmichel.combes@francetelecom.com>
X-Virus-Scanned: amavisd-new 2.2.1 (20041222) at mx0.starentnetworks.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ff9c467ad7f19c2a6d058acd7faaec8
Content-Transfer-Encoding: quoted-printable
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Francis,

I am just trying to catch up with this thread. Please see my comments
inline...

-Kuntal


> -----Original Message-----
> From: mip6-bounces@ietf.org [mailto:mip6-bounces@ietf.org] On Behalf
Of
> Francis Dupont
> Sent: Wednesday, October 26, 2005 7:47 AM
> To: COMBES Jean-Michel RD-MAPS-ISS
> Cc: mip6@ietf.org
> Subject: Re: [Mip6] General comments/questions on MIPv6 bootstrapping
>=20
> This is a review of
draft-ietf-mip6-bootstrapping-integrated-dhc-00.txt:
>=20
>  - in fact the document can (should?) be split into 2 parts:
>    the AAA stuff and the DHCP stuff. IMHO the important part
>    is the AAA one because it comes directly from the "integrated"
>    scenario, DHCP is used only to transmit the AAA results to
>    the MN. One can use in some cases the access control protocol,
>    for instance if it is 802.1X.

[KC>] Not sure why the solution should be split into separate
components. For the split scenario draft we talk about all the
components in one place. Why should we do it differently for this one?
Moreover, no one in the DT favored producing many drafts for a solution.

>=20
>  - DHCPv6 has some constraints which are not explained in
>    the document (cf my previous messages)
>=20

[KC>] Not entirely true. We have statements in the draft on this line
e.g. "Also, the mechanism defined in this document requires the NAS to
support Mobile IPv6 specific AAA attributes and a collocated DHCP relay
agent."

>  - I don't know if the OPTION_MIP6-RELAY-Option is necessary, i.e.,
>    why not use the RADIUS-RELAY-Option (aka RRAO) ?
>    (cf. draft-ietf-dhc-v6-relay-radius-01.txt)
>=20

[KC>] It is required because the RRAO draft does not contain an option
to carry home agent address. Moreover, as stated earlier, reducing
dependencies on other drafts was an object in the DT.

>  - Security Considerations reference RFC which are not for DHCPv6,
>    i.e., the right reference is RFC 3315.

[KC>] I see your point. I would let the other DT members (who
contributed to the security considerations section) comment for this
one.
>=20
>  - DHCPv6 security doesn't work well in multi-domain environments
>    so in the mobility context. Quoting RFC 3118:
>=20
>    The "delayed authentication" protocol does not attempt to address
>    situations where a client may roam from one administrative domain
to
>    another, i.e., interdomain roaming.  This protocol is focused on
>    solving the intradomain problem where the out-of-band exchange of a
>    shared secret is feasible.
>=20
>    and:
>=20
>       Delayed authentication requires a shared secret key for each
>       client on each DHCP server with which that client may wish to
use
>       the DHCP protocol.  Each secret key has a unique identifier that
>       can be used by a receiver to determine which secret was used to
>       generate the MAC in the DHCP message.  Therefore, delayed
>       authentication may not scale well in an architecture in which a
>       DHCP client connects to multiple administrative domains.
>=20

[KC>] In some deployments, lower layer security can be relied on for
DHCP interaction. This is mentioned in the draft. Moreover, SDOs are
working on general bootstrapping applications that might take care of
the inter domain roaming issue.=20

>  - IMHO this paragraph is not sound:
>=20
>    The communication between the DHCP client and the DHCP server for
the
>    exchange of home agent information is security sensitive and
requires
>    authentication, integrity and replay protection.  Either
lower-layer
>    security (such as link layer security established as part of the
>    network access authentication protocol run) or DHCP security
>    [RFC3118] can be used.  The latter approach is only applicable in
>    non-roaming environments due to the limited applicability of the
DHCP
>    security mechanisms.  An adversary that is able to modify home
agent
>    information can force the mobile node to use a different home agent
>    than intended by the MSA.  However, this type of attack can be
>    detected by the security mechanism between the mobile node and the
>    home agent.
>=20
>=20
>  - to finish the document presents the less aggressive scheme to use
>    AAA in MIPv6 bootstrapping, i.e., it only assigns the HA. I have
>    a concern about this because AAA is the only practical way to
>    attach security properties (i.e., a proof it is not fake) to
>    the care-of address so to improve the MIPv6 security.
>    Unfortunately the document does nothing for this...
>=20

[KC>] The AAA can be used to bootstrap other parameters such as HoA,
however the DT decided to restrict the use of AAA for HA bootstrapping
only. The idea was to have as much common procedures between the split
and the integrated solutions as possible. I don't understand why IKEv2
based HoA bootstrapping will be weaker than the same with AAA.


> Regards
>=20
> Francis.Dupont@enst-bretagne.fr
>=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 Wed Oct 26 15:07:32 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUqcW-0004DY-9K; Wed, 26 Oct 2005 15:07:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUqcS-00042N-A9
	for mip6@megatron.ietf.org; Wed, 26 Oct 2005 15:07:29 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15062
	for <mip6@ietf.org>; Wed, 26 Oct 2005 15:07:12 -0400 (EDT)
Received: from mx0.starentnetworks.com ([12.38.223.203])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUqpe-0005to-Vu
	for mip6@ietf.org; Wed, 26 Oct 2005 15:21:07 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mx0.starentnetworks.com (Postfix) with ESMTP id 87C649001F;
	Wed, 26 Oct 2005 15:06:53 -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 21916-03; Wed, 26 Oct 2005 15:06:51 -0400 (EDT)
Received: from ames.starentnetworks.com (ames.starentnetworks.com
	[12.33.235.15]) by mx0.starentnetworks.com (Postfix) with ESMTP;
	Wed, 26 Oct 2005 15:06:51 -0400 (EDT)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
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] General comments/questions on MIPv6 bootstrapping
Date: Wed, 26 Oct 2005 15:03:48 -0400
Message-ID: <8A16DAD84432534FBFC19FD92B50512F035D92CF@ames.starentnetworks.com>
Thread-Topic: [Mip6] General comments/questions on MIPv6 bootstrapping
thread-index: AcXY2gvNGL3/4nIlRnOIjBMy/NvwzAAgqC8AAEBKKxA=
From: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
To: "COMBES Jean-Michel RD-MAPS-ISS" <jeanmichel.combes@francetelecom.com>
X-Virus-Scanned: amavisd-new 2.2.1 (20041222) at mx0.starentnetworks.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 42e3ed3f10a1d8bef690f09da16f507a
Content-Transfer-Encoding: quoted-printable
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

> Maybe, some text is needed to explain how and when the MN knows that
it
> cannot get the HA address with the DHCP-based mechanism and decides to
> use finally DNS-based mechanism.

This was discussed in DT. If the MN supports the DHCP based HA
bootstrapping scheme, it should send a DHCP Information Request for HA
info as soon as it connects in the access network. To reduce setup
delay, the MN can also send a DNS query to discover HA info
simultaneously. If it receives HA info from both DHCP and DNS servers,
then the HA info from DHCP takes precedence. If not, the HA info from
either one is used by the MN.

The operators can decide whether the MN needs to send DHCP and DNS
queries simultaneously or it does DHCP first and then falls back on DNS
if DHCP does not provide HA info. This is a MN configuration issue,
IMHO.

-Kuntal
 =20

> -----Original Message-----
> From: mip6-bounces@ietf.org [mailto:mip6-bounces@ietf.org] On Behalf
Of
> COMBES Jean-Michel RD-MAPS-ISS
> Sent: Tuesday, October 25, 2005 10:20 AM
> To: Vijay Devarapalli
> Cc: mip6@ietf.org
> Subject: RE: [Mip6] General comments/questions on MIPv6 bootstrapping
>=20
>=20
>=20
>=20
>=20
> > -----Original Message-----
> > From: Vijay Devarapalli [mailto:vijayd@iprg.nokia.com]
> > Sent: Monday, October 24, 2005 10:32 PM
> > To: COMBES Jean-Michel RD-MAPS-ISS
> > Cc: mip6@ietf.org
> > Subject: Re: [Mip6] General comments/questions on MIPv6
bootstrapping
> >
> > COMBES Jean-Michel RD-MAPS-ISS wrote:
> > > Hi again,
> > >
> > > I was waiting for the proposal for the integrated scenario
> > before to
> > > do this email.
> > >
> > > I have 2 main comments/questions.
> > >
> > > The first one is regarding the fact that we have two (very)
> > different
> > > mechanisms for only one functionality (on one side
> > DNS+IKEv2, on the
> > > other side PANA+AAA+DCHP).
> >
> > there are 4 mains problems in MIP6 bootstrapping
> >
> > 1. home agent discovery
> > 2. home address configuration
> > 3. security association setup
> > 4. DNS update for the MN
> >
> > draft-ietf-mip6-bootstrapping-split and
> > draft-ietf-mip6-bootstrapping-integrated-dhc differ only on
> > 1). the solutions for 2), 3) and 4) are the same in both drafts.
>=20
> OK.
>=20
> >
> >  > So, personally, I am a little afraid how all
> > > this will be managed in the user's terminal and in the
> > MSP's network.
> > > E.g., what will be the trigger in the terminal to know which is
the
> > > bootstrapping mechanism the terminal has to use?
> >
> > we have some text on this in the integrated draft. the mobile
> > node could be configured to use either DHCPv6 or DNS for HA
> > discovery. based on the configuration the MN uses a
> > particular mechanism for HA discovery. in case both are
> > available and the MN gets a response through a DHCP reply and
> > DNS reply, the DHCP response has precedence. do you see a
> > need for more text on this? let us know if there are any
> > issues we havent considered.
>=20
> Maybe, some text is needed to explain how and when the MN knows that
it
> cannot get the HA address with the DHCP-based mechanism and decides to
> use finally DNS-based mechanism.
>=20
> >
> > > My second comment is regarding the interoperability with NEMO. I
> > > believe that if MIPv6 is deployed soon, NEMO will be
> > deployed at the
> > > same time because the protocol is as mature as MIPv6. So I
> > would like
> > > to know if the bootstrapping mechanisms working for MIPv6,
> > will work with NEMO too.
> > > I would like to avoid to add new mechanisms again and so
> > increase the
> > > complexity in a deployement architecture.
> >
> > for NEMO, in addition to the 4 problems listed above, a
> > mobile network prefix needs to be configured. for that there
> > are two drafts being progressed in the NEMO WG.
> >
> > http://www.ietf.org/internet-drafts/draft-ietf-nemo-dhcpv6-pd-00.txt
> > http://www.ietf.org/internet-drafts/draft-ietf-nemo-prefix-del
> > egation-00.txt
> >
> > these drafts were written up even before the boostrapping
> > work started in the MIP6 WG. is there anything else that
> > needs to be addressed for NEMO bootstrapping?
>=20
> IMO, the other one is to be able to do the difference between a MIPv6
HA
> discovery and a NEMO HA discovery. But it seems that the DHCP-based
and
> the DNS-based mechanisms are easily adaptable to allow this.
>=20
> >
> > Vijay
> >
> >
> >
>=20
> Regards.
>=20
> JMC.
>=20
> France Telecom - R&D Division - MAPS/NSS
> Jean-Michel COMBES, Internet/Intranet Security
> E-Mail: jeanmichel.combes@francetelecom.com
> Phone: +33 (0)1 45 29 45 94
> Fax: +33 (0)1 45 29 65 19
> Mobile: +33 (0)6 07 29 30 16
>=20
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6



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



From mip6-bounces@ietf.org Wed Oct 26 15:08:47 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUqdi-00065Q-Ub; Wed, 26 Oct 2005 15:08:46 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUqdh-000649-Le
	for mip6@megatron.ietf.org; Wed, 26 Oct 2005 15:08:45 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15130
	for <mip6@ietf.org>; Wed, 26 Oct 2005 15:08:30 -0400 (EDT)
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUqqr-0005wg-Vy
	for mip6@ietf.org; Wed, 26 Oct 2005 15:22:25 -0400
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id j9QIZRF13219;
	Wed, 26 Oct 2005 11:35:27 -0700
X-mProtect: <200510261835> Nokia Silicon Valley Messaging Protection
Received: from mvdhcp14184.americas.nokia.com (172.18.141.84,
	claiming to be "[127.0.0.1]")
	by darkstar.iprg.nokia.com smtpdxmZTSw; Wed, 26 Oct 2005 11:35:26 PDT
Message-ID: <435FD422.1070601@iprg.nokia.com>
Date: Wed, 26 Oct 2005 12:08:18 -0700
From: Vijay Devarapalli <vijayd@iprg.nokia.com>
User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
Subject: CoA and AAA (was Re: [Mip6] General comments/questions on MIPv6
	bootstrapping)
References: <200510261246.j9QCkxXL013329@givry.rennes.enst-bretagne.fr>
In-Reply-To: <200510261246.j9QCkxXL013329@givry.rennes.enst-bretagne.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Content-Transfer-Encoding: 7bit
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Francis,

Francis Dupont wrote:

>  - to finish the document presents the less aggressive scheme to use
>    AAA in MIPv6 bootstrapping, i.e., it only assigns the HA. I have
>    a concern about this because AAA is the only practical way to
>    attach security properties (i.e., a proof it is not fake) to
>    the care-of address so to improve the MIPv6 security.
>    Unfortunately the document does nothing for this...

can you elaborate on this? the AAAH might never know the
CoA of the mobile node. what needs to be proven regarding
the CoA and to whom?

or do you want a solution where the AAAH stores the CoA
of the mobile node, knowing that the CoA was configured
after the MN was authenticated to the AAAH. and later
you want the HA to check with the AAAH to see if the CoA
is valid?

anyway I think it is outside the scope of the bootstrapping
solutions.

Vijay


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



From mip6-bounces@ietf.org Wed Oct 26 15:21:40 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUqqC-0004tP-Qp; Wed, 26 Oct 2005 15:21:40 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUqq6-0004nv-Ue
	for mip6@megatron.ietf.org; Wed, 26 Oct 2005 15:21:34 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16140
	for <mip6@ietf.org>; Wed, 26 Oct 2005 15:21:19 -0400 (EDT)
Received: from carrierpigeon.cs.umd.edu ([128.8.129.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUr3K-0006Tb-Bf
	for mip6@ietf.org; Wed, 26 Oct 2005 15:35:14 -0400
Received: from MINDLAP2 (pool-70-108-8-29.res.east.verizon.net [70.108.8.29])
	(authenticated bits=0)
	by carrierpigeon.cs.umd.edu (8.12.10/8.12.5) with ESMTP id
	j9QJLDfN013578
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <mip6@ietf.org>; Wed, 26 Oct 2005 15:21:25 -0400 (EDT)
Message-Id: <200510261921.j9QJLDfN013578@carrierpigeon.cs.umd.edu>
From: "Moustafa Youssef" <moustafa@cs.umd.edu>
To: <mip6@ietf.org>
Date: Wed, 26 Oct 2005 15:20:54 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ff9c467ad7f19c2a6d058acd7faaec8
Content-Transfer-Encoding: quoted-printable
Subject: [Mip6] CFP: IEEE Workshop on Dependability and Security in Sensor
	Networks and Systems
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

(Our apologies if you receive multiple copies of this CFP)

-------------------------------------------------------------
                   Call for Papers
       Second IEEE Workshop on Dependability and Security in
                    Sensor Networks and Systems
                            (DSSNS'2006)
                        http://www.dssns.org
                        In conjunction with
              2nd NASA/IEEE Systems and Software Week
        30th NASA/IEEE Software Engineering Workshop (SEW'2006)
            Columbia, Maryland, USA ~ April 24-28, 2006

Recently, there has been a growing interest in the potential use
of networked sensors in applications such as smart environments,=20
disaster management, combat field reconnaissance, and security=20
surveillance. While the initial view of the community was that=20
networked sensors will play a complementary role that enhances=20
the quality of these applications, recent research results have=20
encouraged practitioners to envision an increased reliance on sensor=20
networks and systems (SN&S) in such critical and sensitive=20
applications. Therefore to realize their potential, necessary=20
dependability and security (D&S) measures have to be=20
incorporated in the design and during the operation of SN&S.=20
Dependability is usually specified using attributes like reliability,=20
survivability, safety, maintainability, and availability in presence=20
of failure, while security is specified by attributes like integrity,=20
authenticity, confidentiality, and availability in presence of=20
attacks. D&S services accomplish tasks for attack and
failure prevention, detection and response. The scope of D&S=20
services may span the deployed sensors to command nodes=20
and likely beyond. It also involves D&S support at, and=20
cross-cutting, the protocol stack layers from physical to=20
application.

Achieving dependability and security in SN&S will require=20
non-conventional mechanisms due to many factors including:=20
(1) sensors are significantly constrained in the amount of=20
available resources such as energy, storage and computation;=20
(2) sensors are expected to be deployed in very large numbers=20
in normal as well as harsh/hostile environments; (3) sensor=20
networks suffer from structural weakness and limited physical
protection, and (4) localization of impact is complicated due=20
to the un-tethered nature of SN&S and of the potential=20
attackers. In addition, D&S requirements may vary according
to mission defined over a multi-dimensional context, such=20
as field of deployment (e.g., hostile versus friendly), type of=20
application (e.g., monitoring, tracking, data collection), mode=20
of operation (e.g., normal, exception, post-event recovery),=20
and time.

This workshop will foster a forum for discussing and presenting=20
recent research results on dependability and security in SN&S.=20
Topics of interest include, although not limited to, the following:

- Fault and intrusion-tolerant architectures, middleware and operational
models=20
- Robust routing, storage, and processing of sensed data
- D&S architectures, protocols and tools
- Vulnerabilities, attacks and countermeasures
- Monitoring and evaluation techniques
- Robust clustering techniques
- Self-awareness and context-awareness=20
- Resilient virtual infrastructures
- Autonomic and adaptive D&S support.
- Formal representation and verification of D&S properties
- Network inference support for D&S
- Quality of service provisioning
- Models, metrics, and measurements for D&S
- Privacy-aware D&S services
- Testbeds, simulation and visualization=20
- Agent-based D&S management=20
- SN&S support for D&S in larger information grids
- SN&S application development environments


Submission Guidelines
---------------------
For guidelines regarding paper submission, please refer to the
workshop=92s=20
website (http://www.dssns.org). Papers should contain original material=20
and not be previously published, or currently submitted for
consideration=20
elsewhere. The manuscript should not exceed 20 single-column
double-space=20
pages in PDF format, font size 11 or larger. The first page should
include=20
title, authors' contact information, abstract and five keywords.=20

Important Dates
----------------
Submission deadline:	November 7, 2005
Decision notification:	December 20, 2005
Final manuscript due:	January 20, 2006


The accepted papers will appear in a proceedings published by IEEE.
The best paper will be recognized and selected papers will be invited to

a Special Issue of the Journal of Ad Hoc and Sensor Wireless Networks.=20

Workshop Co-Chairs
-------------------
Mohamed Eltoweissy
Virginia Tech, USA
E-mail: toweissy@vt.edu=20

Mohamed Younis
University of Maryland Baltimore County, USA
E-mail: younis@csee.umbc.edu=20

Publicity Co-Chairs
--------------------
Denis Gracanin
Virginia Tech, USA
E-mail: gracanin@vt.edu

Moustafa Youssef
University of Maryland at College Park, USA
E-mail: moustafa@cs.umd.edu=20

Program Committee
------------------
Farooq Anjum, Telcordia & U. of Penn, USA
David Carman, Johns Hopkins U.=96 Applied Physics Lab, USA
Ing-Ray Chen, Virginia Tech, USA
M. Nazih Elderini, Alexandria U., Egypt
Deborah Frincke, Pacific Northwest National Lab and U. of Idaho, USA
Ahmed Helmy, University of Southern California, USA
Sushil Jajodia, George Mason U., USA
Shivakant Mishra, U. of Colorado, USA
Peng Ning, North Carolina State U., USA
Cristina Nita-Rotaru, Purdue U., USA
Stephan Olariu, Old Dominion U., USA
David Simplot-Ryl, U. Lille, INRIA Futurs, France
Mani B. Srivastava, U. of California =96 Los Angeles, USA
John A. Stankovic, U. of Virginia, USA
Ivan Stojmenovic, U. of Ottawa, Canada
Gene Tsudik, U. of California-Irvine, USA
Cliff Wang, Army Research Office, USA
Stephen D. Wolthusen, Fraunhofer-IGD, Germany
Albert Zomaya, U. of Sydney, Australia


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



From mip6-bounces@ietf.org Wed Oct 26 16:31:35 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUrvr-0007Uf-KR; Wed, 26 Oct 2005 16:31:35 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUrvp-0007Ti-SN
	for mip6@megatron.ietf.org; Wed, 26 Oct 2005 16:31:33 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05824
	for <mip6@ietf.org>; Wed, 26 Oct 2005 16:31:16 -0400 (EDT)
Received: from coliposte.enst-bretagne.fr ([192.108.115.12])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUs8y-0005ju-CD
	for mip6@ietf.org; Wed, 26 Oct 2005 16:45:12 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by coliposte.enst-bretagne.fr (8.12.10/8.12.10/2004.10.03) with ESMTP
	id j9QKUvhR023703; Wed, 26 Oct 2005 22:30:57 +0200
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by coliposte.enst-bretagne.fr (8.12.10/8.12.10/2004.09.01) with ESMTP
	id j9QKUUls023677; Wed, 26 Oct 2005 22:30: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
	j9QKUW5P016051; Wed, 26 Oct 2005 22:30:32 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200510262030.j9QKUW5P016051@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: "Alper Yegin" <alper.yegin@yegin.org>
Subject: Re: [Mip6] General comments/questions on MIPv6 bootstrapping 
In-reply-to: Your message of Wed, 26 Oct 2005 21:22:03 +0300.
	<000001c5da5a$2dbbee90$0302a8c0@Alperyegin> 
Date: Wed, 26 Oct 2005 22:30:32 +0200
X-Virus-Scanned: amavisd-new at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 386e0819b1192672467565a524848168
Cc: mip6@ietf.org,
	'COMBES Jean-Michel RD-MAPS-ISS' <jeanmichel.combes@francetelecom.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   > => the document recommends DHCPv6 in a context where its security
   > can't be insured. IMHO this is a major issue.
   
   Actually, what we tried to say was "secure your DHCP in whatever way you
   are securing it." Just because you are carrying an HA information does
   not require that the DHCP signaling be more or less secured than what
   the operator does normally. 
   
=> but it seems the operator does normally not use DHCP...

   If you agree to that, and have a better way to capture in the document,
   please propose some text.
   
=> as I've said my first concern is the document should be split between
AAA and DHCP...

   [For DHCP security, the operator may rely on lower-layer security, or
   some other mechanism, e.g., draft-yegin-eap-boot-rfc3118-00.txt, etc.]
   
=> argh, this draft is already expired... (I've it but we should not
rely on it). IMHO the idea to establish the DHCP shared secret in the
AAA phase is good (and similar to draft-dupont-mipv6-aaa-01.txt...).
You are saying too much or not enough (:-).
   
   > => the paragraph begins by "security sensitive" and "requires".
   > The proposed solutions are lower-layer security, something which can't
   > be assumed to be always available, 
   
   Many, if not all, deployments rely on lower-layer security. This is
   mostly an architectural issue. DSL operators know that the DHCP is run
   over physically-secured lines, hence the current deployments don't
   involved DHCP-level security....
   
=> hum, the 802.11 final link is not so secure...
IMHO in the scenario the only local secure mechanism is the network
access control, so it should be used to piggyback things in it or
to derive a shared secret for protection, shouldn't it?

   > and DHCPv6 security, which doesn't
   > work well in the context (this is my previous comment). It finishes
   > by explaining the security in fact doesn't matter: this is both
   > arguable (security matters soon or late, and HA assignment is more
   > vulnerable then HA discovery) and not consistent with the
   > beginning.
   
   I see your point. The text is inconsistent.
   
=> yes, and I believe the real issue is there is no good and general
way to provide the required level of security.

   >    CoA ownership issue is outside the scope of "MIP6 bootstrapping"
   >    problem.
   > 
   > => so we have to find a way to put it inside!
   
   Sorry I don't understand. Why do you see this issue as part of the "MIP6
   bootstrapping problem", which deals with HA, HoA, MN-HA SA
   configuration?
   
=> because AAA is the only mechanism which can provide a solution.
In the document the only feature provided by AAA+DHCP is HA assignment.
For any person who has worked on MIPv6/AAA stuff this is incredibly
limited.
   
Regards

Francis.Dupont@enst-bretagne.fr

PS: cf my checking message in the IPsec list:
http://msgs.securepoint.com/cgi-bin/get/ipsec-0510/26.html
   
Do you mind briefly stating why you think this is better than the DNS
and DHCP-based HA discovery/assignment?
   
=> it is far more general, there is only two constraints:
 - IKEv2 has to be used (but it seems it is already in all bootstrapping
   proposals)
 - the anycast address has to be known (exactly as the current DHAAD).
   Note this is compatible with DNS or DHCP-based discovery: in place
   of giving unicast addresses of servers one can answer with anycast
   addresses of server groups.
I've found only advantages at the exception of the compatibity with
NEMO: a second anycast IID should be assigned for NEMO HAs as there is
no way to distinguish between MIPv6 and NEMO HAs.

Regards

Francis.Dupont@enst-bretagne.fr

   

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



From mip6-bounces@ietf.org Wed Oct 26 17:09:07 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUsWB-0002pJ-Ns; Wed, 26 Oct 2005 17:09:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUsW9-0002oH-MC
	for mip6@megatron.ietf.org; Wed, 26 Oct 2005 17:09:05 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA24882
	for <mip6@ietf.org>; Wed, 26 Oct 2005 17:08:47 -0400 (EDT)
Received: from mx0.starentnetworks.com ([12.38.223.203])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUsjL-0004ba-E5
	for mip6@ietf.org; Wed, 26 Oct 2005 17:22:44 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mx0.starentnetworks.com (Postfix) with ESMTP id 4027390002;
	Wed, 26 Oct 2005 17:08:49 -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 22794-09; Wed, 26 Oct 2005 17:08:44 -0400 (EDT)
Received: from ames.starentnetworks.com (ames.starentnetworks.com
	[12.33.235.15]) by mx0.starentnetworks.com (Postfix) with ESMTP;
	Wed, 26 Oct 2005 17:08:39 -0400 (EDT)
X-MessageTextProcessor: DisclaimIt (2.50.252) [Starent Networks Corp.]
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
Importance: normal
Priority: normal
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] General comments/questions on MIPv6 bootstrapping 
Date: Wed, 26 Oct 2005 17:08:38 -0400
Message-ID: <8A16DAD84432534FBFC19FD92B50512F035D92D0@ames.starentnetworks.com>
Thread-Topic: [Mip6] General comments/questions on MIPv6 bootstrapping 
thread-index: AcXabx4k6Bqxg5fSRvO0lFRj/uxZ9gAAOJEA
From: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
To: "Francis Dupont" <Francis.Dupont@enst-bretagne.fr>,
	"Alper Yegin" <alper.yegin@yegin.org>
X-Virus-Scanned: amavisd-new 2.2.1 (20041222) at mx0.starentnetworks.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Content-Transfer-Encoding: quoted-printable
Cc: mip6@ietf.org,
	COMBES Jean-Michel RD-MAPS-ISS <jeanmichel.combes@francetelecom.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

> =3D> because AAA is the only mechanism which can provide a solution.
> In the document the only feature provided by AAA+DHCP is HA
assignment.
> For any person who has worked on MIPv6/AAA stuff this is incredibly
> limited.
>=20

[KC>] When I see this comment I think of the "MIP6 Parameter
Authenticity Attribute" for RADIUS (AAA) and "Authenticity sub-option"
for DHCPv6 in the following drafts which have expired but can be found
at:=20

http://ftp.tpnet.pl/vol/d1/ftp.rs.internic.net/internet-drafts/draft-cho
wdhury-mip6-bootstrap-radius-01.txt


http://ftp.tpnet.pl/vol/d1/ftp.rs.internic.net/internet-drafts/draft-cho
wdhury-dhc-mip6-agentop-00.txt


Note that we have dropped this attribute in the updated mip6-RADIUS
draft:

http://www.ietf.org/internet-drafts/draft-chowdhury-mip6-radius-00.txt

We can revive it back if there are some interests.

-Kuntal



"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 Wed Oct 26 17:34:36 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUsuq-0002WD-Ix; Wed, 26 Oct 2005 17:34:36 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUsuo-0002Ve-95
	for mip6@megatron.ietf.org; Wed, 26 Oct 2005 17:34:34 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA28130
	for <mip6@ietf.org>; Wed, 26 Oct 2005 17:34:18 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUt81-00067R-S4
	for mip6@ietf.org; Wed, 26 Oct 2005 17:48:15 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id j9QLY6i14402; Wed, 26 Oct 2005 23:34:06 +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
	j9QLY7P2016356; Wed, 26 Oct 2005 23:34:07 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200510262134.j9QLY7P2016356@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
Subject: Re: [Mip6] General comments/questions on MIPv6 bootstrapping 
In-reply-to: Your message of Wed, 26 Oct 2005 14:42:26 EDT.
	<8A16DAD84432534FBFC19FD92B50512F035D92CE@ames.starentnetworks.com> 
Date: Wed, 26 Oct 2005 23:34:07 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 31247fb3be228bb596db9127becad0bc
Cc: mip6@ietf.org,
	COMBES Jean-Michel RD-MAPS-ISS <jeanmichel.combes@francetelecom.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   >  - in fact the document can (should?) be split into 2 parts:
   >    the AAA stuff and the DHCP stuff. IMHO the important part
   >    is the AAA one because it comes directly from the "integrated"
   >    scenario, DHCP is used only to transmit the AAA results to
   >    the MN. One can use in some cases the access control protocol,
   >    for instance if it is 802.1X.
   
   [KC>] Not sure why the solution should be split into separate
   components. For the split scenario draft we talk about all the
   components in one place. Why should we do it differently for this one?
   Moreover, no one in the DT favored producing many drafts for a solution.
   
=> but if the document shall be the only one for the integrated
scenario (and it seems it is the case), the weakness of the DHCP
part will impact the whole solution.

   >  - DHCPv6 has some constraints which are not explained in
   >    the document (cf my previous messages)
   
   [KC>] Not entirely true. We have statements in the draft on this line
   e.g. "Also, the mechanism defined in this document requires the NAS to
   support Mobile IPv6 specific AAA attributes and a collocated DHCP relay
   agent."
   
=> my concern is this is not enough and it seems it is shared...

   >  - I don't know if the OPTION_MIP6-RELAY-Option is necessary, i.e.,
   >    why not use the RADIUS-RELAY-Option (aka RRAO) ?
   >    (cf. draft-ietf-dhc-v6-relay-radius-01.txt)
   > 
   
   [KC>] It is required because the RRAO draft does not contain an option
   to carry home agent address.

=> as the RRAO carries RADIUS attributes do you mean there is no
RADIUS attribute for home agent address (obviously not :-).

   Moreover, as stated earlier, reducing
   dependencies on other drafts was an object in the DT.
   
=> reducing the amount of similar drafts (and code I have to
write to support them) seems a good goal too.
The idea of the RRAO is to insert some AAA attribute from the NAS part
to messages to the DHCPv6 server using a colocated DHCPv6 relay.
I use it to connect the authentication (User-Name) on the NAS to
the DHCPv6 config (keyed by DUIDs) and to assign prefixes from
RADIUS (Delegated-IPv6-Prefix). This is very similar to what
the document proposes.

   [KC>] In some deployments, lower layer security can be relied on for
   DHCP interaction. This is mentioned in the draft. Moreover, SDOs are
   working on general bootstrapping applications that might take care of
   the inter domain roaming issue. 
   
=> but today the document doesn't propose a secure solution in the
general case...

   [KC>] The AAA can be used to bootstrap other parameters such as HoA,
   however the DT decided to restrict the use of AAA for HA bootstrapping
   only.

=> I have to confess I don't like at all this shyness.

   The idea was to have as much common procedures between the split
   and the integrated solutions as possible.

=> nice goal but it seems the result is at the opposite (procedures
are enough different to get concerns about this point, cf Jean-Michel's
original message, and the provided functionalities are minimal, i.e.,
some potentials of the different procedures have not been exploited).
A DT effect (:-)?

   I don't understand why IKEv2
   based HoA bootstrapping will be weaker than the same with AAA.
   
=> AAA bootstrapping has the potential to be stronger because it can
provide authentication of the CoA using a trusted third party.
   
Regards

Francis.Dupont@enst-bretagne.fr

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



From mip6-bounces@ietf.org Wed Oct 26 17:40:09 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUt0D-0005rm-LS; Wed, 26 Oct 2005 17:40:09 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUt0B-0005re-LB
	for mip6@megatron.ietf.org; Wed, 26 Oct 2005 17:40:07 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA28348
	for <mip6@ietf.org>; Wed, 26 Oct 2005 17:39:51 -0400 (EDT)
Received: from brmea-mail-3.sun.com ([192.18.98.34])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUtDN-0006GK-7k
	for mip6@ietf.org; Wed, 26 Oct 2005 17:53:48 -0400
Received: from jurassic.eng.sun.com ([129.146.58.37])
	by brmea-mail-3.sun.com (8.12.10/8.12.9) with ESMTP id j9QLe23F013807; 
	Wed, 26 Oct 2005 15:40:02 -0600 (MDT)
Received: from shubho (shubho.SFBay.Sun.COM [129.146.74.85])
	by jurassic.eng.sun.com (8.13.5+Sun/8.13.5) with SMTP id j9QLe2Rc879805;
	Wed, 26 Oct 2005 14:40:02 -0700 (PDT)
Message-Id: <200510262140.j9QLe2Rc879805@jurassic.eng.sun.com>
Date: Wed, 26 Oct 2005 14:37:37 -0700 (PDT)
From: Samita Chakrabarti <Samita.Chakrabarti@eng.sun.com>
To: mip6@ietf.org, basavaraj.patil@nokia.com, gdommety@cisco.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: FCv+oEx5Rtt7muqRVyN60Q==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.6 SunOS 5.10 sun4u sparc 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Cc: erik.nordmark@sun.com, samita.chakrabarti@sun.com
Subject: [Mip6] Status draft-ietf-mip6-advapi
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Samita Chakrabarti <Samita.Chakrabarti@eng.sun.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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org


FYI,


An updated version ( 05) of the MIP6API draft has been
published on the 24th. Based on IESG comments and other's comments, the notable
changes are:

      - Added an applicability section to clarify the scope
        of usage of the API described in this draft
        
      - Introduced new Socket Options (IPV6_MIPDSTOPTS, IPV6_RECVMIPDSTOPTS)
         for Home address destination option in order to avoid
         complexity of extension header ordering at the kernel
         on the outbound path.
         
      - Added a section on the order of extension headers when a home address
         destination option is present 
         
      - Removed inet6_rth_gettype() function. Routing header type is
         now directly obtained from the routing header; an example code
         is included. 
         
      - Clarified network-byte ordering for constants and data structures
       
 
 If there are no more comments from IESG, the draft should be ready to
 proceed after one or two minor typo fixes right after IETF.
 
 Erik Nordmark
 Samita Chakrabarti


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



From mip6-bounces@ietf.org Wed Oct 26 17:43:03 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUt31-0007HR-3Z; Wed, 26 Oct 2005 17:43:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUt30-0007GW-45
	for mip6@megatron.ietf.org; Wed, 26 Oct 2005 17:43:02 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA28479
	for <mip6@ietf.org>; Wed, 26 Oct 2005 17:42:46 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUtGD-0006Kh-Uy
	for mip6@ietf.org; Wed, 26 Oct 2005 17:56:43 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id j9QLghi14950; Wed, 26 Oct 2005 23:42:43 +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
	j9QLgiiK016389; Wed, 26 Oct 2005 23:42:44 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200510262142.j9QLgiiK016389@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
Subject: Re: [Mip6] General comments/questions on MIPv6 bootstrapping 
In-reply-to: Your message of Wed, 26 Oct 2005 15:03:48 EDT.
	<8A16DAD84432534FBFC19FD92B50512F035D92CF@ames.starentnetworks.com> 
Date: Wed, 26 Oct 2005 23:42:44 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Cc: mip6@ietf.org,
	COMBES Jean-Michel RD-MAPS-ISS <jeanmichel.combes@francetelecom.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   > Maybe, some text is needed to explain how and when the MN knows that
   it
   > cannot get the HA address with the DHCP-based mechanism and decides to
   > use finally DNS-based mechanism.
   
   This was discussed in DT. If the MN supports the DHCP based HA
   bootstrapping scheme, it should send a DHCP Information Request for HA
   info as soon as it connects in the access network. To reduce setup
   delay, the MN can also send a DNS query to discover HA info
   simultaneously. If it receives HA info from both DHCP and DNS servers,
   then the HA info from DHCP takes precedence. If not, the HA info from
   either one is used by the MN.
   
   The operators can decide whether the MN needs to send DHCP and DNS
   queries simultaneously or it does DHCP first and then falls back on DNS
   if DHCP does not provide HA info. This is a MN configuration issue,
   IMHO.
   
=> hum, I can guess what shall happen in the real world: the MN tries
DHCP first just because DHCP will give the local DNS server address.
If it doesn't get a DHCP reply it is in deep trouble, if it doesn't
get the HA info it retries using the DNS (through the local DNS
servers)...

Regards

Francis.Dupont@enst-bretagne.fr

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



From mip6-bounces@ietf.org Wed Oct 26 17:48:50 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUt8c-0001Nd-Ow; Wed, 26 Oct 2005 17:48:50 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUsGP-0007U1-CQ
	for mip6@megatron.ietf.org; Wed, 26 Oct 2005 16:52:49 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA17312
	for <mip6@ietf.org>; Wed, 26 Oct 2005 16:52:31 -0400 (EDT)
From: Mohan.Parthasarathy@nokia.com
Received: from mgw-ext01.nokia.com ([131.228.20.93])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUsTa-0001jN-GU
	for mip6@ietf.org; Wed, 26 Oct 2005 17:06:28 -0400
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211])
	by mgw-ext01.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id
	j9QKqdAu032265; Wed, 26 Oct 2005 23:52:43 +0300
Received: from daebh101.NOE.Nokia.com ([10.241.35.111]) by
	esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 26 Oct 2005 23:52:37 +0300
Received: from mvebe101.NOE.Nokia.com ([172.19.64.23]) by
	daebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 26 Oct 2005 15:52:34 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5.7233.31
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 26 Oct 2005 13:52:30 -0700
Message-ID: <8A76136424391244A5CF016533708537C8F791@mvebe101.NOE.Nokia.com>
Thread-Topic: concerns about draft-devarapalli-mip6-ikev1-bootstrap-00.txt
Thread-Index: AcXXIxeAevLLG8A4QF2+oRax9k1W7gDRC9tA
To: <Francis.Dupont@enst-bretagne.fr>, <vijayd@iprg.nokia.com>
X-OriginalArrivalTime: 26 Oct 2005 20:52:34.0257 (UTC)
	FILETIME=[30A98C10:01C5DA6F]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Wed, 26 Oct 2005 17:48:49 -0400
Cc: mip6@ietf.org, Mohan.Parthasarathy@nokia.com
Subject: [Mip6] RE: concerns about
	draft-devarapalli-mip6-ikev1-bootstrap-00.txt
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

=20
Francis,

>
>I maintain my previous concerns about MODECFG and XAUTH. Now=20
>I've read the whole document and I have some other concerns:
> - there are some normative references to documents which timed out
>   many years ago
> - there should be security considerations about the well known
>   essential insecurity of XAUTH (*)

It uses Hybrid authentication which essentially supports
asymmetric authentication for the entities. Hybrid
uses XAUTH but differently. See draft-kelly-ipsra-userauth-00.txt
on why Hybrid does not have the same secrity issues as XAUTH.
The reason we put this there is to support cases like where
the MN just has a MN-AAA shared secret.
=20
> - I am not convinced DHCPv6 can be used over IKE as described:
>   DHCPv6 is designed to run between the client and the first=20
>relay/server
>   over a link using multicast and link-local addresses. So it=20
>runs without
>   problem over L2TP/PPP between a client and a NAS. Here we=20
>have a tunnel
>   mode IPsec which is pretty different than a real tunnel interface.

RFC 3775 assumes that IPsec is modeled as an interface.
This one shows=20
http://www.research.earthlink.net/ipv6/ipv6-ipsec-tunnels.pdf
how DHCPv6 can be secured using IPsec. So, i don't understand
your concern.

-mohan


>So sections 3.1, 3.2 (HoA config) and 4 (SA setup) are at=20
>least questionable.
>The remaining spec is the section 5 (DNS update) which is=20
>already in a bootstrapping document... So I am sorry but IMHO=20
>there is nothing really useful today in the document

>Regards
>
>Francis.Dupont@enst-bretagne.fr
>
>(*): If someone knows Jose Puthenkulam, ask him to refresh its I-D.
>

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



From mip6-bounces@ietf.org Wed Oct 26 17:53:53 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUtDV-0006rJ-Ot; Wed, 26 Oct 2005 17:53:53 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUtDU-0006q3-5s
	for mip6@megatron.ietf.org; Wed, 26 Oct 2005 17:53:52 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA28959
	for <mip6@ietf.org>; Wed, 26 Oct 2005 17:53:36 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUtQh-0006cd-Uw
	for mip6@ietf.org; Wed, 26 Oct 2005 18:07:33 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id j9QLrTi15535; Wed, 26 Oct 2005 23:53:29 +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
	j9QLrUVC016451; Wed, 26 Oct 2005 23:53:30 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200510262153.j9QLrUVC016451@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Vijay Devarapalli <vijayd@iprg.nokia.com>
Subject: Re: CoA and AAA (was Re: [Mip6] General comments/questions on MIPv6
	bootstrapping) 
In-reply-to: Your message of Wed, 26 Oct 2005 12:08:18 PDT.
	<435FD422.1070601@iprg.nokia.com> 
Date: Wed, 26 Oct 2005 23:53:30 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   >  - to finish the document presents the less aggressive scheme to use
   >    AAA in MIPv6 bootstrapping, i.e., it only assigns the HA. I have
   >    a concern about this because AAA is the only practical way to
   >    attach security properties (i.e., a proof it is not fake) to
   >    the care-of address so to improve the MIPv6 security.
   >    Unfortunately the document does nothing for this...
   
   can you elaborate on this? the AAAH might never know the
   CoA of the mobile node. what needs to be proven regarding
   the CoA and to whom?
   
=> the CoA is an important parameter of the network access control
which is done by the AAAL so the AAAH can check with the AAAL
the CoA (this is what I mean by the AAA procedure can provide
an authentication of the CoA using a trusted third party (which
is the AAAL)).

   or do you want a solution where the AAAH stores the CoA
   of the mobile node, knowing that the CoA was configured
   after the MN was authenticated to the AAAH. and later
   you want the HA to check with the AAAH to see if the CoA
   is valid?
   
=> this is one way to provide it but my point of view is more
theorical, i.e., there can be all the needed infos, trusts and
communications.

   anyway I think it is outside the scope of the bootstrapping
   solutions.
   
=> it is not in the goals of the bootstrapping solutions you mean?
I agree but some operators could consider it should be added
(it is a shame to ignore a good property, in particular when it
is a security property).

Regards

Francis.Dupont@enst-bretagne.fr

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



From mip6-bounces@ietf.org Wed Oct 26 17:54:16 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUtDs-0007HN-K2; Wed, 26 Oct 2005 17:54:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUtDq-0007C7-CX
	for mip6@megatron.ietf.org; Wed, 26 Oct 2005 17:54:14 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA28985
	for <mip6@ietf.org>; Wed, 26 Oct 2005 17:53:58 -0400 (EDT)
Received: from mail.flarion.com ([63.103.94.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUtR4-0006cz-Dy
	for mip6@ietf.org; Wed, 26 Oct 2005 18:07:55 -0400
Received: from ftmailserver.flariontech.com ([10.10.1.140]) by
	mail.flarion.com with Microsoft SMTPSVC(5.0.2195.6713);
	Wed, 26 Oct 2005 17:53:56 -0400
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] I-D ACTION:draft-ietf-mip6-nemo-v4traversal-00.txt
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
Date: Wed, 26 Oct 2005 17:53:53 -0400
Message-ID: <A11736FE943F1A408F8BBB1B9F5FE8AD17DE4B@ftmailserver.flariontech.com>
Thread-Topic: [Mip6] I-D ACTION:draft-ietf-mip6-nemo-v4traversal-00.txt
Thread-Index: AcXaFjmOPteK+s4sR4aJunRsnGk3TAAYKmbg
From: "Soliman, Hesham" <H.Soliman@flarion.com>
To: "Alexandru Petrescu" <alexandru.petrescu@motorola.com>
X-OriginalArrivalTime: 26 Oct 2005 21:53:56.0009 (UTC)
	FILETIME=[C3285190:01C5DA77]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Content-Transfer-Encoding: quoted-printable
Cc: mip6@ietf.org, Keiichi SHIMA <keiichi@iijlab.net>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org


 > > The draft is written to allow implementers and operators=20
 > to use MIPv6
 > > only no matter where they are on the Internet and for v6=20
 > and v4 apps.
 >=20
 > Hesham, that is a hefty goal.  I'd reach lower, do some small modular
 > parts that would fit in the current landscape, instead of building
 > entirely new architectures, solutions to everything a customer might
 > ever need.

=3D> You might have had a point if there was no proof that this could
be done. The draft is already out there, it's been implemented
(except for the NAT traversal part). So there is proof that this is=20
doable with trivial extensions to MIPv6.

 > In the past, "universal" mobility solutions have had lesser=20
 > reach than
 > expected.  For example, real complete local and global mobility
 > solutions haven't seen widepsread use despite years of discussion
 > meeting after meeting, mail after mail.

=3D> Apples and oranges. One has nothing to do with the other. =
Furthermore,
you're attributing what you see as a failure to a specific=20
reason, for which you have no proof. BTW, we have commercial deployments
of some of those mechanisms that you claim no one has adopted.

 > So you agree that DSMIPv6 would compete with MIPv4 to offer=20
 > reachability
 > at a permanent MIP4 Home Address, when connected to a v4-only network
 > and v4 app.

=3D> Yes; for a green field operator/vendor that has no
products to build on.


Hesham

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D
This email may contain confidential and privileged material for the sole =
use
 of the intended recipient.  Any review or distribution by others is =
strictly
 prohibited.  If you are not the intended recipient please contact the =
sender
 and delete all copies.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D


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



From mip6-bounces@ietf.org Wed Oct 26 17:55:23 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUtEx-0007jR-36; Wed, 26 Oct 2005 17:55:23 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUtEt-0007in-OA
	for mip6@megatron.ietf.org; Wed, 26 Oct 2005 17:55:19 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29049
	for <mip6@ietf.org>; Wed, 26 Oct 2005 17:55:03 -0400 (EDT)
Received: from mx0.starentnetworks.com ([12.38.223.203])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUtS7-0006fU-Fj
	for mip6@ietf.org; Wed, 26 Oct 2005 18:09:00 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mx0.starentnetworks.com (Postfix) with ESMTP id 8B49E90016;
	Wed, 26 Oct 2005 17:55:07 -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 23099-06; Wed, 26 Oct 2005 17:55:05 -0400 (EDT)
Received: from ames.starentnetworks.com (ames.starentnetworks.com
	[12.33.235.15]) by mx0.starentnetworks.com (Postfix) with ESMTP;
	Wed, 26 Oct 2005 17:55:05 -0400 (EDT)
X-MessageTextProcessor: DisclaimIt (2.50.252) [Starent Networks Corp.]
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
Importance: normal
Priority: normal
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] General comments/questions on MIPv6 bootstrapping 
Date: Wed, 26 Oct 2005 17:55:05 -0400
Message-ID: <8A16DAD84432534FBFC19FD92B50512F035D92D2@ames.starentnetworks.com>
Thread-Topic: [Mip6] General comments/questions on MIPv6 bootstrapping 
thread-index: AcXadj9T+PdHdAo3Tbe2kaPCaG8LDwAAR8SA
From: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
To: <Francis.Dupont@enst-bretagne.fr>
X-Virus-Scanned: amavisd-new 2.2.1 (20041222) at mx0.starentnetworks.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d
Content-Transfer-Encoding: quoted-printable
Cc: mip6@ietf.org,
	COMBES Jean-Michel RD-MAPS-ISS <jeanmichel.combes@francetelecom.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

> =3D> hum, I can guess what shall happen in the real world: the MN =
tries
> DHCP first just because DHCP will give the local DNS server address.
> If it doesn't get a DHCP reply it is in deep trouble, if it doesn't
> get the HA info it retries using the DNS (through the local DNS
> servers)...
>

In real world the MN may have other ways to get the local DNS server
info e.g. PPP (this was also discussed in DT) or pre-configuration. The
MN won't be in "deep trouble" if it has other ways to acquire local DNS
address, after all.

-Kuntal


> -----Original Message-----
> From: Francis.Dupont@enst-bretagne.fr [mailto:Francis.Dupont@enst-
> bretagne.fr]
> Sent: Wednesday, October 26, 2005 4:43 PM
> To: Chowdhury, Kuntal
> Cc: COMBES Jean-Michel RD-MAPS-ISS; mip6@ietf.org
> Subject: Re: [Mip6] General comments/questions on MIPv6 bootstrapping
>=20
>  In your previous mail you wrote:
>=20
>    > Maybe, some text is needed to explain how and when the MN knows
that
>    it
>    > cannot get the HA address with the DHCP-based mechanism and
decides
> to
>    > use finally DNS-based mechanism.
>=20
>    This was discussed in DT. If the MN supports the DHCP based HA
>    bootstrapping scheme, it should send a DHCP Information Request for
HA
>    info as soon as it connects in the access network. To reduce setup
>    delay, the MN can also send a DNS query to discover HA info
>    simultaneously. If it receives HA info from both DHCP and DNS
servers,
>    then the HA info from DHCP takes precedence. If not, the HA info
from
>    either one is used by the MN.
>=20
>    The operators can decide whether the MN needs to send DHCP and DNS
>    queries simultaneously or it does DHCP first and then falls back on
DNS
>    if DHCP does not provide HA info. This is a MN configuration issue,
>    IMHO.
>=20
> =3D> hum, I can guess what shall happen in the real world: the MN =
tries
> DHCP first just because DHCP will give the local DNS server address.
> If it doesn't get a DHCP reply it is in deep trouble, if it doesn't
> get the HA info it retries using the DNS (through the local DNS
> servers)...
>=20
> Regards
>=20
> Francis.Dupont@enst-bretagne.fr



"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 Wed Oct 26 18:19:25 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUtcD-0000cr-NG; Wed, 26 Oct 2005 18:19:25 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUtcC-0000bU-N0
	for mip6@megatron.ietf.org; Wed, 26 Oct 2005 18:19:24 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA00252
	for <mip6@ietf.org>; Wed, 26 Oct 2005 18:19:08 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUtpP-0007Lk-4L
	for mip6@ietf.org; Wed, 26 Oct 2005 18:33:06 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id j9QMIxi17133; Thu, 27 Oct 2005 00:18:59 +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
	j9QMJ0qR016786; Thu, 27 Oct 2005 00:19:00 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200510262219.j9QMJ0qR016786@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Mohan.Parthasarathy@nokia.com
In-reply-to: Your message of Wed, 26 Oct 2005 13:52:30 PDT.
	<8A76136424391244A5CF016533708537C8F791@mvebe101.NOE.Nokia.com> 
Date: Thu, 27 Oct 2005 00:19:00 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Cc: mip6@ietf.org, vijayd@iprg.nokia.com
Subject: [Mip6] Re: concerns about
	draft-devarapalli-mip6-ikev1-bootstrap-00.txt 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   It uses Hybrid authentication which essentially supports
   asymmetric authentication for the entities. Hybrid
   uses XAUTH but differently. See draft-kelly-ipsra-userauth-00.txt

=> expired I-D again (and last century).

   > - I am not convinced DHCPv6 can be used over IKE as described:
   >   DHCPv6 is designed to run between the client and the first 
   >relay/server
   >   over a link using multicast and link-local addresses. So it 
   >runs without
   >   problem over L2TP/PPP between a client and a NAS. Here we 
   >have a tunnel
   >   mode IPsec which is pretty different than a real tunnel interface.
   
   RFC 3775 assumes that IPsec is modeled as an interface.

=> IPsec tunnel mode SAs are not real interfaces, they have no
link-local addresses for instance, when DHCPv6 requires a *link*.

   This one shows 
   http://www.research.earthlink.net/ipv6/ipv6-ipsec-tunnels.pdf
   how DHCPv6 can be secured using IPsec.

=> using real interfaces, *not* IPsec tunnel mode. BTW it talks
about AH on FreeBSD which is well known to not support AH tunnel mode.

   So, i don't understand your concern.
   
=> you try to run DHCPv6 over an IPsec tunnel mode something which
is not a link at all and doesn't provide what DHCPv6 needs
(link-local addresses, multicast, etc) for the client-relay/server.

BTW there is a solution to your problem, it is to colocate a
relay on the MN and to use the IPsec tunnel mode between the relay
and the DHCPv6 entity (relay or server) on the HA.
(the idea comes from a remark of KAME team: to colocate DHCPv6 entities
on the same box is a mess because of port conflicts, I needed the
relay/server case but the client/relay case only was supported).
   
Regards

Francis.Dupont@enst-bretagne.fr

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



From mip6-bounces@ietf.org Wed Oct 26 18:25:08 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUthk-00030A-CB; Wed, 26 Oct 2005 18:25:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUthi-0002zz-Ng
	for mip6@megatron.ietf.org; Wed, 26 Oct 2005 18:25:07 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA00618
	for <mip6@ietf.org>; Wed, 26 Oct 2005 18:24:50 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUtux-0007Vn-PL
	for mip6@ietf.org; Wed, 26 Oct 2005 18:38:48 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id j9QMOni17435; Thu, 27 Oct 2005 00:24: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
	j9QMOoQV016861; Thu, 27 Oct 2005 00:24:50 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200510262224.j9QMOoQV016861@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
Subject: Re: [Mip6] General comments/questions on MIPv6 bootstrapping 
In-reply-to: Your message of Wed, 26 Oct 2005 17:08:38 EDT.
	<8A16DAD84432534FBFC19FD92B50512F035D92D0@ames.starentnetworks.com> 
Date: Thu, 27 Oct 2005 00:24:50 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Cc: mip6@ietf.org,
	COMBES Jean-Michel RD-MAPS-ISS <jeanmichel.combes@francetelecom.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   [KC>] When I see this comment I think of the "MIP6 Parameter
   Authenticity Attribute" for RADIUS (AAA) and "Authenticity sub-option"
   for DHCPv6 in the following drafts which have expired but can be found
   at: 
   
=> so you are the forth member of the DT who seems to share my
frustration!

Thanks

Francis.Dupont@enst-bretagne.fr

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



From mip6-bounces@ietf.org Wed Oct 26 18:37:26 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUtte-0002Rq-Bn; Wed, 26 Oct 2005 18:37:26 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUttb-0002Re-3f
	for mip6@megatron.ietf.org; Wed, 26 Oct 2005 18:37:24 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01501
	for <mip6@ietf.org>; Wed, 26 Oct 2005 18:37:06 -0400 (EDT)
Received: from mx0.starentnetworks.com ([12.38.223.203])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUu6q-0007t8-2L
	for mip6@ietf.org; Wed, 26 Oct 2005 18:51:04 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mx0.starentnetworks.com (Postfix) with ESMTP id ADD479001E;
	Wed, 26 Oct 2005 18:37:12 -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 23321-08; Wed, 26 Oct 2005 18:37:11 -0400 (EDT)
Received: from ames.starentnetworks.com (ames.starentnetworks.com
	[12.33.235.15]) by mx0.starentnetworks.com (Postfix) with ESMTP;
	Wed, 26 Oct 2005 18:37:11 -0400 (EDT)
X-MessageTextProcessor: DisclaimIt (2.50.252) [Starent Networks Corp.]
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
Importance: normal
Priority: normal
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] General comments/questions on MIPv6 bootstrapping 
Date: Wed, 26 Oct 2005 18:37:11 -0400
Message-ID: <8A16DAD84432534FBFC19FD92B50512F035D92D3@ames.starentnetworks.com>
Thread-Topic: [Mip6] General comments/questions on MIPv6 bootstrapping 
thread-index: AcXadRJovTsvSQ6KRaq7sy4mN5fZtwAAuDSw
From: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
To: <Francis.Dupont@enst-bretagne.fr>
X-Virus-Scanned: amavisd-new 2.2.1 (20041222) at mx0.starentnetworks.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ee80a2074afbfe28d15369f4e74e579d
Content-Transfer-Encoding: quoted-printable
Cc: mip6@ietf.org,
	COMBES Jean-Michel RD-MAPS-ISS <jeanmichel.combes@francetelecom.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Please see inline...

> -----Original Message-----
> From: Francis.Dupont@enst-bretagne.fr [mailto:Francis.Dupont@enst-
> bretagne.fr]
> Sent: Wednesday, October 26, 2005 4:34 PM
> To: Chowdhury, Kuntal
> Cc: COMBES Jean-Michel RD-MAPS-ISS; mip6@ietf.org
> Subject: Re: [Mip6] General comments/questions on MIPv6 bootstrapping
>=20
>  In your previous mail you wrote:
>=20
>    >  - in fact the document can (should?) be split into 2 parts:
>    >    the AAA stuff and the DHCP stuff. IMHO the important part
>    >    is the AAA one because it comes directly from the "integrated"
>    >    scenario, DHCP is used only to transmit the AAA results to
>    >    the MN. One can use in some cases the access control protocol,
>    >    for instance if it is 802.1X.
>=20
>    [KC>] Not sure why the solution should be split into separate
>    components. For the split scenario draft we talk about all the
>    components in one place. Why should we do it differently for this
one?
>    Moreover, no one in the DT favored producing many drafts for a
> solution.
>=20
> =3D> but if the document shall be the only one for the integrated
> scenario (and it seems it is the case), the weakness of the DHCP
> part will impact the whole solution.

[KC>] No, this document is not the "only" one for the integrated
scenario. The draft is _a_ solution for the intergraded scenario using
DHCPv6. We are just trying to use an IETF defined protocol for
configuration management. The weaknesses with DHCPv6 should be discussed
in DHC WG.

>=20
>    >  - DHCPv6 has some constraints which are not explained in
>    >    the document (cf my previous messages)
>=20
>    [KC>] Not entirely true. We have statements in the draft on this
line
>    e.g. "Also, the mechanism defined in this document requires the NAS
to
>    support Mobile IPv6 specific AAA attributes and a collocated DHCP
relay
>    agent."
>=20
> =3D> my concern is this is not enough and it seems it is shared...

[KC>] I have not seen any other comments besides yours. May be I missed
the postings from others.=20

>=20
>    >  - I don't know if the OPTION_MIP6-RELAY-Option is necessary,
i.e.,
>    >    why not use the RADIUS-RELAY-Option (aka RRAO) ?
>    >    (cf. draft-ietf-dhc-v6-relay-radius-01.txt)
>    >
>=20
>    [KC>] It is required because the RRAO draft does not contain an
option
>    to carry home agent address.
>=20
> =3D> as the RRAO carries RADIUS attributes do you mean there is no
> RADIUS attribute for home agent address (obviously not :-).

[KC>] Unlike RRAO, OPTION_MIP6-RELAY-Option does not carry RADIUS
attributes. It carries home agent IPv6 address or the home agent FQDN.
This one works for both RADIUS and Diameter. Hence, it is more generic
than RRAO. Also, it does not require the DHCPv6 server to parse RADIUS
attributes which is a disadvantage of RRAO, IMHO.=20

>=20
>    Moreover, as stated earlier, reducing
>    dependencies on other drafts was an object in the DT.
>=20
> =3D> reducing the amount of similar drafts (and code I have to
> write to support them) seems a good goal too.
> The idea of the RRAO is to insert some AAA attribute from the NAS part
> to messages to the DHCPv6 server using a colocated DHCPv6 relay.
> I use it to connect the authentication (User-Name) on the NAS to
> the DHCPv6 config (keyed by DUIDs) and to assign prefixes from
> RADIUS (Delegated-IPv6-Prefix). This is very similar to what
> the document proposes.
>=20

[KC>] Well, I think you are contradicting yourself here. You like the
idea of reducing dependencies on other drafts...but you want to add
another (actually two, because we need an RRAO equivalent for Diameter)
dependency!

You may find a use of the RRAO, but that does not mean that everyone has
to find similar use of it as well. The defined attributes in RRAO are
simply not of any use for the integrated scenario solution. Besides, it
adds unnecessary dependencies.

>    [KC>] In some deployments, lower layer security can be relied on
for
>    DHCP interaction. This is mentioned in the draft. Moreover, SDOs
are
>    working on general bootstrapping applications that might take care
of
>    the inter domain roaming issue.
>=20
> =3D> but today the document doesn't propose a secure solution in the
> general case...
>=20

[KC>] I think it does provide adequate guidance to secure the MN-DHCP
communication via L2 or DHCPv6 security.

>    [KC>] The AAA can be used to bootstrap other parameters such as
HoA,
>    however the DT decided to restrict the use of AAA for HA
bootstrapping
>    only.
>=20
> =3D> I have to confess I don't like at all this shyness.
>

[KC>] We are discussing a draft which is an output of the DT. Regardless
of what you like to hear, as a member of the DT, I am going to state
exactly what the DT has decided.
=20
>    The idea was to have as much common procedures between the split
>    and the integrated solutions as possible.
>=20
> =3D> nice goal but it seems the result is at the opposite (procedures
> are enough different to get concerns about this point, cf
Jean-Michel's
> original message, and the provided functionalities are minimal, i.e.,
> some potentials of the different procedures have not been exploited).
> A DT effect (:-)?
>
=20
[KC>] In the integrated scenario, bootstrapping of MIP6 info can happen
at the time of access auth since ASA =3D=3D MSA. The DT has chosen =
DHCPv6
for conveying the home agent info to the MN and use AAA in the backend.
We had the option of defining a completely new set of procedures for HoA
and IPsec SA parts of the bootstrapping problem space, but we chose to
reuse procedures between split and integrated solutions. Not sure, why
you think it was a not-so-good decision?
=20

>    I don't understand why IKEv2
>    based HoA bootstrapping will be weaker than the same with AAA.
>=20
> =3D> AAA bootstrapping has the potential to be stronger because it can
> provide authentication of the CoA using a trusted third party.
>=20

[KC>] no comments.
=20
> Regards
>=20
> Francis.Dupont@enst-bretagne.fr



"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 Wed Oct 26 18:47:50 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUu3i-0007tz-IV; Wed, 26 Oct 2005 18:47:50 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUu3g-0007tr-6G
	for mip6@megatron.ietf.org; Wed, 26 Oct 2005 18:47:48 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA02192
	for <mip6@ietf.org>; Wed, 26 Oct 2005 18:47:31 -0400 (EDT)
Received: from mx0.starentnetworks.com ([12.38.223.203])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUuGv-0008Cj-G9
	for mip6@ietf.org; Wed, 26 Oct 2005 19:01:29 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mx0.starentnetworks.com (Postfix) with ESMTP id 782DD9001E;
	Wed, 26 Oct 2005 18:47:37 -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 23372-07; Wed, 26 Oct 2005 18:47:36 -0400 (EDT)
Received: from ames.starentnetworks.com (ames.starentnetworks.com
	[12.33.235.15]) by mx0.starentnetworks.com (Postfix) with ESMTP;
	Wed, 26 Oct 2005 18:47:36 -0400 (EDT)
X-MessageTextProcessor: DisclaimIt (2.50.252) [Starent Networks Corp.]
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
Importance: normal
Priority: normal
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] General comments/questions on MIPv6 bootstrapping 
Date: Wed, 26 Oct 2005 18:47:36 -0400
Message-ID: <8A16DAD84432534FBFC19FD92B50512F035D92D4@ames.starentnetworks.com>
Thread-Topic: [Mip6] General comments/questions on MIPv6 bootstrapping 
thread-index: AcXafCCaDA1Wy/roTluI25wqb9PX4gAAizDA
From: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
To: <Francis.Dupont@enst-bretagne.fr>
X-Virus-Scanned: amavisd-new 2.2.1 (20041222) at mx0.starentnetworks.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Content-Transfer-Encoding: quoted-printable
Cc: mip6@ietf.org,
	COMBES Jean-Michel RD-MAPS-ISS <jeanmichel.combes@francetelecom.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org



> -----Original Message-----
> From: Francis.Dupont@enst-bretagne.fr [mailto:Francis.Dupont@enst-
> bretagne.fr]
> Sent: Wednesday, October 26, 2005 5:25 PM
> To: Chowdhury, Kuntal
> Cc: Alper Yegin; mip6@ietf.org; COMBES Jean-Michel RD-MAPS-ISS
> Subject: Re: [Mip6] General comments/questions on MIPv6 bootstrapping
>=20
>  In your previous mail you wrote:
>=20
>    [KC>] When I see this comment I think of the "MIP6 Parameter
>    Authenticity Attribute" for RADIUS (AAA) and "Authenticity
sub-option"
>    for DHCPv6 in the following drafts which have expired but can be
found
>    at:
>=20
> =3D> so you are the forth member of the DT who seems to share my
> frustration!
>=20

[KC>] This draft out of the DT is -00 version. So, some changes are
expected when it is discussed in a broader audience. I am not
necessarily agreeing with you that we MUST do something to fix the
DHCPv6 security mechanism in this specific draft. I am merely pointing
to some similar thoughts/ideas in some old drafts I wrote, that's all.

BTW, I think you should post your concern(s) about DHCPv6 security in
DHC WG list. That is the appropriate forum for a solution (if needed),
IMHO.
 =20
> Thanks
>=20
> Francis.Dupont@enst-bretagne.fr



"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 Wed Oct 26 18:50:20 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUu68-0000bA-BD; Wed, 26 Oct 2005 18:50:20 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUu5r-0000S5-T3; Wed, 26 Oct 2005 18:50:03 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA02290;
	Wed, 26 Oct 2005 18:49:47 -0400 (EDT)
Received: from [132.151.6.50] (helo=newodin.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1EUuJ5-0008GV-M3; Wed, 26 Oct 2005 19:03:44 -0400
Received: from mlee by newodin.ietf.org with local (Exim 4.43)
	id 1EUu5p-0005Z1-EL; Wed, 26 Oct 2005 18:50:01 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1EUu5p-0005Z1-EL@newodin.ietf.org>
Date: Wed, 26 Oct 2005 18:50:01 -0400
X-Spam-Score: 0.4 (/)
X-Scan-Signature: f66b12316365a3fe519e75911daf28a8
Cc: mip6@ietf.org
Subject: [Mip6] I-D ACTION:draft-ietf-mip6-dsmip-problem-01.txt 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

--NextPart

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

	Title		: Mobility management for Dual stack mobile nodes A Problem Statement
	Author(s)	: H. Soliman, G. Tsirtsis
	Filename	: draft-ietf-mip6-dsmip-problem-01.txt
	Pages		: 7
	Date		: 2005-10-26
	
This draft discusses the issues associated with mobility management
   for dual stack mobile nodes. Currently, two mobility management
   protocols are defined for IPv4 and IPv6. Deploying both in a dual
   stack mobile node introduces a number of inefficiencies. Deployment
   and operational issues motivate the use of a single mobility
   management protocol. This draft discusses such motivations. The draft
   also hints on how the current [MIPv4] and [MIPv6] protocols could be
   extended so that they can support mobility management for a dual
   stack node.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mip6-dsmip-problem-01.txt

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


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

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


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

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-mip6-dsmip-problem-01.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

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

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

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

ENCODING mime
FILE /internet-drafts/draft-ietf-mip6-dsmip-problem-01.txt

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

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


--OtherAccess--

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

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

--NextPart--





From mip6-bounces@ietf.org Wed Oct 26 18:51:13 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUu6z-0000s1-69; Wed, 26 Oct 2005 18:51:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUu5v-0000UO-Cb; Wed, 26 Oct 2005 18:50:07 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA02319;
	Wed, 26 Oct 2005 18:49:50 -0400 (EDT)
Received: from [132.151.6.50] (helo=newodin.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1EUuJ6-0008Gq-1u; Wed, 26 Oct 2005 19:03:46 -0400
Received: from mlee by newodin.ietf.org with local (Exim 4.43)
	id 1EUu5p-0005a5-QF; Wed, 26 Oct 2005 18:50:01 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1EUu5p-0005a5-QF@newodin.ietf.org>
Date: Wed, 26 Oct 2005 18:50:01 -0400
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 31247fb3be228bb596db9127becad0bc
Cc: mip6@ietf.org
Subject: [Mip6] I-D ACTION:draft-ietf-mip6-ikev2-ipsec-04.txt 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

--NextPart

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

	Title		: Mobile IPv6 Operation with IKEv2 and the revised IPsec
	Author(s)	: F. Dupont, V. Devarapalli
	Filename	: draft-ietf-mip6-ikev2-ipsec-04.txt
	Pages		: 25
	Date		: 2005-10-26
	
This document describes Mobile IPv6 operation with the revised IPsec
   architecture and IKEv2.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mip6-ikev2-ipsec-04.txt

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


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

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


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

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-mip6-ikev2-ipsec-04.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

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

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

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

ENCODING mime
FILE /internet-drafts/draft-ietf-mip6-ikev2-ipsec-04.txt

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

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


--OtherAccess--

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

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

--NextPart--





From mip6-bounces@ietf.org Wed Oct 26 18:53:45 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUu9R-0001qJ-6l; Wed, 26 Oct 2005 18:53:45 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUu79-0000uh-MZ
	for mip6@megatron.ietf.org; Wed, 26 Oct 2005 18:51:23 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA02509
	for <mip6@ietf.org>; Wed, 26 Oct 2005 18:51:07 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUuKN-0008Lz-IJ
	for mip6@ietf.org; Wed, 26 Oct 2005 19:05:05 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id j9QModi19251; Thu, 27 Oct 2005 00:50:39 +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
	j9QMod6F017027; Thu, 27 Oct 2005 00:50:39 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200510262250.j9QMod6F017027@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
Subject: Re: [Mip6] General comments/questions on MIPv6 bootstrapping 
In-reply-to: Your message of Wed, 26 Oct 2005 17:55:05 EDT.
	<8A16DAD84432534FBFC19FD92B50512F035D92D2@ames.starentnetworks.com> 
Date: Thu, 27 Oct 2005 00:50:39 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: mip6@ietf.org,
	COMBES Jean-Michel RD-MAPS-ISS <jeanmichel.combes@francetelecom.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   In real world the MN may have other ways to get the local DNS server
   info e.g. PPP (this was also discussed in DT)

=> where is the DNS stuff in IPv6CP?

   or pre-configuration.

=> pre-configuration in a roaming environment?

   The MN won't be in "deep trouble" if it has other ways to acquire local DNS
   address, after all.

=> LLMNR? I believe more in manual configuration (written on the blackboard:
the WEP key is XXX, the DNS server is YY::YY, :-).
   
Believe me or not, the lightweight DHCPv6 service *is* the service which
will distribute local DNS server(s) address(es).

Regards

Francis.Dupont@enst-bretagne.fr

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



From mip6-bounces@ietf.org Wed Oct 26 19:12:55 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUuRz-00063x-Om; Wed, 26 Oct 2005 19:12:55 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUuRx-00062u-JJ
	for mip6@megatron.ietf.org; Wed, 26 Oct 2005 19:12:53 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA11657
	for <mip6@ietf.org>; Wed, 26 Oct 2005 19:12:36 -0400 (EDT)
Received: from mx0.starentnetworks.com ([12.38.223.203])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUuf1-0003LG-GX
	for mip6@ietf.org; Wed, 26 Oct 2005 19:26:24 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mx0.starentnetworks.com (Postfix) with ESMTP id 41AE29001E;
	Wed, 26 Oct 2005 19:12:32 -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 23480-08; Wed, 26 Oct 2005 19:12:31 -0400 (EDT)
Received: from ames.starentnetworks.com (ames.starentnetworks.com
	[12.33.235.15]) by mx0.starentnetworks.com (Postfix) with ESMTP;
	Wed, 26 Oct 2005 19:12:31 -0400 (EDT)
X-MessageTextProcessor: DisclaimIt (2.50.252) [Starent Networks Corp.]
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
Importance: normal
Priority: normal
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] General comments/questions on MIPv6 bootstrapping 
Date: Wed, 26 Oct 2005 19:12:30 -0400
Message-ID: <8A16DAD84432534FBFC19FD92B50512F035D92D5@ames.starentnetworks.com>
Thread-Topic: [Mip6] General comments/questions on MIPv6 bootstrapping 
thread-index: AcXaf8wq2L2b/uBLS4m2W+2Wpm0xZgAAfoLg
From: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
To: <Francis.Dupont@enst-bretagne.fr>
X-Virus-Scanned: amavisd-new 2.2.1 (20041222) at mx0.starentnetworks.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Content-Transfer-Encoding: quoted-printable
Cc: mip6@ietf.org,
	COMBES Jean-Michel RD-MAPS-ISS <jeanmichel.combes@francetelecom.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

If DHCPv6 is the most used way to discover DNS server address, it is
very unlikely that the DHCPv6 server won't return DNS server address
option.

In the worst case, the AR/NAS can relay DNS requests from the MN to the
local DNS server and vice-versa. We have already implemented this in our
product since there is no IPv6CP option for DNS.

-Kuntal

> -----Original Message-----
> From: Francis.Dupont@enst-bretagne.fr [mailto:Francis.Dupont@enst-
> bretagne.fr]
> Sent: Wednesday, October 26, 2005 5:51 PM
> To: Chowdhury, Kuntal
> Cc: COMBES Jean-Michel RD-MAPS-ISS; mip6@ietf.org
> Subject: Re: [Mip6] General comments/questions on MIPv6 bootstrapping
>=20
>  In your previous mail you wrote:
>=20
>    In real world the MN may have other ways to get the local DNS
server
>    info e.g. PPP (this was also discussed in DT)
>=20
> =3D> where is the DNS stuff in IPv6CP?
>=20
>    or pre-configuration.
>=20
> =3D> pre-configuration in a roaming environment?
>=20
>    The MN won't be in "deep trouble" if it has other ways to acquire
local
> DNS
>    address, after all.
>=20
> =3D> LLMNR? I believe more in manual configuration (written on the
> blackboard:
> the WEP key is XXX, the DNS server is YY::YY, :-).
>=20
> Believe me or not, the lightweight DHCPv6 service *is* the service
which
> will distribute local DNS server(s) address(es).
>=20
> Regards
>=20
> Francis.Dupont@enst-bretagne.fr



"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 Wed Oct 26 19:22:33 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUubI-0005KQ-Sc; Wed, 26 Oct 2005 19:22:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUubH-0005KA-Rv
	for mip6@megatron.ietf.org; Wed, 26 Oct 2005 19:22:31 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16774
	for <mip6@ietf.org>; Wed, 26 Oct 2005 19:22:14 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUuoU-0005HH-LU
	for mip6@ietf.org; Wed, 26 Oct 2005 19:36:12 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id j9QNMBb21670; Thu, 27 Oct 2005 01:22:11 +0200
Received: from givry.rennes.enst-bretagne.fr
	(localhost.rennes.enst-bretagne.fr [127.0.0.1])
	by givry.rennes.enst-bretagne.fr (8.13.1/8.13.1) with ESMTP id
	j9QNMC3d017315; Thu, 27 Oct 2005 01:22:12 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200510262322.j9QNMC3d017315@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
Subject: Re: [Mip6] General comments/questions on MIPv6 bootstrapping 
In-reply-to: Your message of Wed, 26 Oct 2005 18:37:11 EDT.
	<8A16DAD84432534FBFC19FD92B50512F035D92D3@ames.starentnetworks.com> 
Date: Thu, 27 Oct 2005 01:22:12 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8fbbaa16f9fd29df280814cb95ae2290
Cc: mip6@ietf.org,
	COMBES Jean-Michel RD-MAPS-ISS <jeanmichel.combes@francetelecom.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   > => but if the document shall be the only one for the integrated
   > scenario (and it seems it is the case), the weakness of the DHCP
   > part will impact the whole solution.
   
   [KC>] No, this document is not the "only" one for the integrated
   scenario.

=> what/where is the other one? I can see only the "probleme statement",
the "split" and the "integrated with DHCP" documents.

   The draft is _a_ solution for the intergraded scenario using
   DHCPv6. We are just trying to use an IETF defined protocol for
   configuration management.

=> yes, I saw the comment "EAP is not about configuration".
BTW I repeat from time to time to one of my colleagues that
RADIUS has no configuration application...

   The weaknesses with DHCPv6 should be discussed in DHC WG.
   
=> this is not the way real things are done...

   > => my concern is this is not enough and it seems it is shared...
   
   [KC>] I have not seen any other comments besides yours. May be I missed
   the postings from others. 
   
=> I remember some comments about the operational constraints implied
by the choice of DHCPv6.

   > => as the RRAO carries RADIUS attributes do you mean there is no
   > RADIUS attribute for home agent address (obviously not :-).
   
   [KC>] Unlike RRAO, OPTION_MIP6-RELAY-Option does not carry RADIUS
   attributes. It carries home agent IPv6 address or the home agent FQDN.
   This one works for both RADIUS and Diameter.

=> so your argument is with RRAO we have to translate Diameter AVPs to
RADIUS attributes. With OPTION_MIP6-RELAY-Option we have to translate
Diameter AVPs or RADIUS attributes to DHCPv6 options. Where is the win?

   Hence, it is more generic than RRAO.

=> it is fully a matter of taste. For me it is less generic.

   Also, it does not require the DHCPv6 server to parse RADIUS
   attributes which is a disadvantage of RRAO, IMHO. 

=> it is 10 lines of code (RADIUS attributes are in a very simple
TLV format). I am afraid the code to translate AAA stuff in the relay
is both longer and at a worse place.
   
   >    Moreover, as stated earlier, reducing
   >    dependencies on other drafts was an object in the DT.
   > 
   > => reducing the amount of similar drafts (and code I have to
   > write to support them) seems a good goal too.
   > The idea of the RRAO is to insert some AAA attribute from the NAS part
   > to messages to the DHCPv6 server using a colocated DHCPv6 relay.
   > I use it to connect the authentication (User-Name) on the NAS to
   > the DHCPv6 config (keyed by DUIDs) and to assign prefixes from
   > RADIUS (Delegated-IPv6-Prefix). This is very similar to what
   > the document proposes.
   > 
   
   [KC>] Well, I think you are contradicting yourself here.

=> no, I simply don't consider inclusion as a fair way to reduce
dependencies.

   You like the
   idea of reducing dependencies on other drafts...but you want to add
   another (actually two, because we need an RRAO equivalent for Diameter)
   dependency!
   
=> Diameter is deployed nowhere so we don't need an RDAO (it is a shame
Diameter is not used but it is a fact). My suggession is more to
translate Diameter AVPs into RADIUS attributes than to specify an RDAO.

   You may find a use of the RRAO,

=> this use is more than suggested in the RRAO draft.

   but that does not mean that everyone has
   to find similar use of it as well. The defined attributes in RRAO are
   simply not of any use for the integrated scenario solution.

=> the RRAO draft lists only attributes which are already defined
(i.e., in the IANA table). Note I use the Delegated-IPv6-Prefix
which is in a more recent draft and not in the list.

   Besides, it adds unnecessary dependencies.

=> because you believe to define stuff which is in the scope
of another WG is a good idea? We'll see.
   
   > => but today the document doesn't propose a secure solution in the
   > general case...
   
   [KC>] I think it does provide adequate guidance to secure the MN-DHCP
   communication via L2 or DHCPv6 security.
   
=> when the current DHCPv6 security is known to not work in the
context (according to the document itself ! :-).

   > => I have to confess I don't like at all this shyness.
   
   [KC>] We are discussing a draft which is an output of the DT.

=> yes, there are traces of a DT process (:-).

   Regardless of what you like to hear, as a member of the DT, I am
   going to state exactly what the DT has decided.
    
=> so we should dissolve the DT ASAP and give back your liberty?

   [KC>] In the integrated scenario, bootstrapping of MIP6 info can happen
   at the time of access auth since ASA == MSA. The DT has chosen DHCPv6
   for conveying the home agent info to the MN and use AAA in the backend.
   We had the option of defining a completely new set of procedures for HoA
   and IPsec SA parts of the bootstrapping problem space, but we chose to
   reuse procedures between split and integrated solutions. Not sure, why
   you think it was a not-so-good decision?
    
=> because I can see the result...
   
Regards

Francis.Dupont@enst-bretagne.fr

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



From mip6-bounces@ietf.org Wed Oct 26 19:39:11 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUurO-0002Rn-Ux; Wed, 26 Oct 2005 19:39:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUurM-0002Qs-6N
	for mip6@megatron.ietf.org; Wed, 26 Oct 2005 19:39:09 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA26070
	for <mip6@ietf.org>; Wed, 26 Oct 2005 19:38:51 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUv4Z-0000Kn-N1
	for mip6@ietf.org; Wed, 26 Oct 2005 19:52:49 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id j9QNchb22681; Thu, 27 Oct 2005 01:38:43 +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
	j9QNcio1017427; Thu, 27 Oct 2005 01:38:44 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200510262338.j9QNcio1017427@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
Subject: Re: [Mip6] General comments/questions on MIPv6 bootstrapping 
In-reply-to: Your message of Wed, 26 Oct 2005 18:47:36 EDT.
	<8A16DAD84432534FBFC19FD92B50512F035D92D4@ames.starentnetworks.com> 
Date: Thu, 27 Oct 2005 01:38:44 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Cc: mip6@ietf.org,
	COMBES Jean-Michel RD-MAPS-ISS <jeanmichel.combes@francetelecom.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   > => so you are the forth member of the DT who seems to share my
   > frustration!
   
   [KC>] This draft out of the DT is -00 version. So, some changes are
   expected when it is discussed in a broader audience. I am not
   necessarily agreeing with you that we MUST do something to fix the
   DHCPv6 security mechanism in this specific draft.

=> but IMHO we MUST fix the security of the solution before going
to the IESG.

   BTW, I think you should post your concern(s) about DHCPv6 security in
   DHC WG list.

=> as the issue comes from the use of DHCPv6, the first question is
whether to use DHCPv6 is a right idea. At least to rely on the work
of another WG (work which is not in its charter, a charter you should
read BTW) is a pretty bad idea.
     
Thanks

Francis.Dupont@enst-bretagne.fr

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



From mip6-bounces@ietf.org Wed Oct 26 20:03:15 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUvEh-0004Rf-5F; Wed, 26 Oct 2005 20:03:15 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUvEe-0004QH-F9
	for mip6@megatron.ietf.org; Wed, 26 Oct 2005 20:03:13 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA02379
	for <mip6@ietf.org>; Wed, 26 Oct 2005 20:02:52 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUvO4-0007gM-R7
	for mip6@ietf.org; Wed, 26 Oct 2005 20:12:59 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id j9QNwgb23923; Thu, 27 Oct 2005 01:58: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
	j9QNwgsc017663; Thu, 27 Oct 2005 01:58:42 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200510262358.j9QNwgsc017663@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Mohan.Parthasarathy@nokia.com
In-reply-to: Your message of Wed, 26 Oct 2005 16:06:27 PDT.
	<8A76136424391244A5CF016533708537C8F890@mvebe101.NOE.Nokia.com> 
Date: Thu, 27 Oct 2005 01:58:42 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Cc: mip6@ietf.org, vijayd@iprg.nokia.com
Subject: [Mip6] Re: concerns about
	draft-devarapalli-mip6-ikev1-bootstrap-00.txt 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   >=> IPsec tunnel mode SAs are not real interfaces, they have no 
   >link-local addresses for instance, when DHCPv6 requires a *link*.

   You just need to configure a IPv6-in-IPv6 tunnel interface (so
   that you get a link-local address) and use transport mode SA
   to protect the DHCPv6 traffic. Once you get the home address,
   you setup ipsec tunnel mode SAs using RFC 3775.
   
=> this is not what is the document ("IPsec tunnel") and the drawback
is the IKE has to be reestablished...

Regards

Francis.Dupont@enst-bretagne.fr


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



From mip6-bounces@ietf.org Wed Oct 26 21:27:21 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUwY5-0003O0-1H; Wed, 26 Oct 2005 21:27:21 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUwY4-0003MT-08; Wed, 26 Oct 2005 21:27:20 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA13695;
	Wed, 26 Oct 2005 21:27:04 -0400 (EDT)
Received: from neon.tcs.hut.fi ([130.233.215.20])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1EUwlK-0001yo-Ni; Wed, 26 Oct 2005 21:41:03 -0400
Received: from rhea.tcs.hut.fi (rhea.tcs.hut.fi [130.233.215.147])
	by neon.tcs.hut.fi (Postfix) with ESMTP id 6E6DD80008D;
	Thu, 27 Oct 2005 04:27:10 +0300 (EEST)
Date: Thu, 27 Oct 2005 04:27:10 +0300 (EEST)
From: Wassim Haddad <whaddad@tcs.hut.fi>
To: momipriv@lacnic.net
Message-ID: <Pine.LNX.4.58.0510270422270.393@rhea.tcs.hut.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 2.4 (++)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Cc: mip6@ietf.org, mipshop@ietf.org, mobopts@irtf.org
Subject: [Mip6] Privacy Problem Statement
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Hi all,

We have updated the momipriv problem statement. The new version expands
the privacy problem to include IPsec and SEND protocols. It is available at:

http://www.ietf.org/internet-drafts/draft-haddad-momipriv-problem-statement-02.txt

Comments appreciated.


Regards,

Wassim H.

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



From mip6-bounces@ietf.org Wed Oct 26 21:32:42 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUwdG-0005rD-7L; Wed, 26 Oct 2005 21:32:42 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUwdE-0005qC-28; Wed, 26 Oct 2005 21:32:40 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA13968;
	Wed, 26 Oct 2005 21:32:24 -0400 (EDT)
Received: from neon.tcs.hut.fi ([130.233.215.20])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1EUwqU-00028E-KD; Wed, 26 Oct 2005 21:46:22 -0400
Received: from rhea.tcs.hut.fi (rhea.tcs.hut.fi [130.233.215.147])
	by neon.tcs.hut.fi (Postfix) with ESMTP id 47879800098;
	Thu, 27 Oct 2005 04:32:30 +0300 (EEST)
Date: Thu, 27 Oct 2005 04:32:30 +0300 (EEST)
From: Wassim Haddad <whaddad@tcs.hut.fi>
To: momipriv@lacnic.net
Message-ID: <Pine.LNX.4.58.0510270427210.393@rhea.tcs.hut.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 2.4 (++)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Cc: mip6@ietf.org, mipshop@ietf.org, mobopts@irtf.org
Subject: [Mip6] Privacy Terminology
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Hi all,

We have separated and expanded the terminology related to privacy from the
MoMiPriv problem statement draft. The new draft is now available at:

http://www.ietf.org/internet-drafts/draft-haddad-alien-privacy-terminology-00.txt

Comments appreciated.


Regards,

Wassim H.



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



From mip6-bounces@ietf.org Wed Oct 26 23:33:59 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUyWd-0002ms-O0; Wed, 26 Oct 2005 23:33:59 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUyWb-0002jg-Fh
	for mip6@megatron.ietf.org; Wed, 26 Oct 2005 23:33:57 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA19289
	for <mip6@ietf.org>; Wed, 26 Oct 2005 23:33:41 -0400 (EDT)
Received: from mail.sfc.wide.ad.jp ([203.178.142.146])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUyjm-0005Gj-Uu
	for mip6@ietf.org; Wed, 26 Oct 2005 23:47:41 -0400
Received: from [203.178.138.10] (unknown [203.178.138.10])
	by mail.sfc.wide.ad.jp (Postfix) with ESMTP id CCDC34CBA5
	for <mip6@ietf.org>; Thu, 27 Oct 2005 12:33:15 +0900 (JST)
Message-ID: <43604AE6.7090309@sfc.wide.ad.jp>
Date: Thu, 27 Oct 2005 12:35:02 +0900
From: Romain KUNTZ <kuntz@sfc.wide.ad.jp>
Organization: Keio University
User-Agent: Mozilla Thunderbird 1.0.6 (Macintosh/20050716)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: mip6@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Content-Transfer-Encoding: 7bit
Subject: [Mip6] comment on draft-ietf-mip6-nemo-v4traversal-00
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Dear authors of draft-ietf-mip6-nemo-v4traversal-00,

First of all thank you for providing this draft. We were eager to see it 
as the v4 traversal feature is one of the most important missing feature 
for IPv6-mobility deployement.

About the draft, I have a concern regarding how the DSMIPv6 MN can get a 
new IPv4 CoA when roaming in an IPv4 network. Sorry if I have misread 
the draft, but no hints are provided in the draft, and the solutions 
proposed by RFC 3344 (MIPv4) cannot apply here, as it is based on the 
Agent Advertisement. Or does a Foreign Agent must be present in each 
IPv4 network we roam into?

Regards,

-- 
Romain KUNTZ
kuntz@sfc.wide.ad.jp

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



From mip6-bounces@ietf.org Wed Oct 26 23:36:47 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUyZL-00057e-KX; Wed, 26 Oct 2005 23:36:47 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUuM4-0000xF-OZ
	for mip6@megatron.ietf.org; Wed, 26 Oct 2005 19:06:48 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08115
	for <mip6@ietf.org>; Wed, 26 Oct 2005 19:06:32 -0400 (EDT)
From: Mohan.Parthasarathy@nokia.com
Received: from mgw-ext01.nokia.com ([131.228.20.93])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUuZI-000247-QS
	for mip6@ietf.org; Wed, 26 Oct 2005 19:20:30 -0400
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143])
	by mgw-ext01.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id
	j9QN6YZD024286; Thu, 27 Oct 2005 02:06:41 +0300
Received: from daebh101.NOE.Nokia.com ([10.241.35.111]) by
	esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 27 Oct 2005 02:06:29 +0300
Received: from mvebe101.NOE.Nokia.com ([172.19.64.23]) by
	daebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 26 Oct 2005 18:06:26 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5.7233.31
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 26 Oct 2005 16:06:27 -0700
Message-ID: <8A76136424391244A5CF016533708537C8F890@mvebe101.NOE.Nokia.com>
Thread-Topic: concerns about draft-devarapalli-mip6-ikev1-bootstrap-00.txt 
Thread-Index: AcXae1ygmczN6nfWQviTPhlZZoZk1QABYpNA
To: <Francis.Dupont@enst-bretagne.fr>
X-OriginalArrivalTime: 26 Oct 2005 23:06:26.0406 (UTC)
	FILETIME=[E4323860:01C5DA81]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Wed, 26 Oct 2005 23:36:44 -0400
Cc: mip6@ietf.org, vijayd@iprg.nokia.com
Subject: [Mip6] RE: concerns about
	draft-devarapalli-mip6-ikev1-bootstrap-00.txt 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 =20
>
>   > - I am not convinced DHCPv6 can be used over IKE as described:
>   >   DHCPv6 is designed to run between the client and the first=20
>   >relay/server
>   >   over a link using multicast and link-local addresses. So it=20
>   >runs without
>   >   problem over L2TP/PPP between a client and a NAS. Here we=20
>   >have a tunnel
>   >   mode IPsec which is pretty different than a real tunnel=20
>interface.
>  =20
>   RFC 3775 assumes that IPsec is modeled as an interface.
>
>=3D> IPsec tunnel mode SAs are not real interfaces, they have no=20
>link-local addresses for instance, when DHCPv6 requires a *link*.
>
You just need to configure a IPv6-in-IPv6 tunnel interface (so
that you get a link-local address) and use transport mode SA
to protect the DHCPv6 traffic. Once you get the home address,
you setup ipsec tunnel mode SAs using RFC 3775.

-mohan

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



From mip6-bounces@ietf.org Wed Oct 26 23:57:57 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUytp-0004mL-AL; Wed, 26 Oct 2005 23:57:57 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUytm-0004mC-Lj
	for mip6@megatron.ietf.org; Wed, 26 Oct 2005 23:57:54 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA20612
	for <mip6@ietf.org>; Wed, 26 Oct 2005 23:57:38 -0400 (EDT)
Received: from mail.flarion.com ([63.103.94.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUz71-000688-MP
	for mip6@ietf.org; Thu, 27 Oct 2005 00:11:38 -0400
Received: from ftmailserver.flariontech.com ([10.10.1.140]) by
	mail.flarion.com with Microsoft SMTPSVC(5.0.2195.6713);
	Wed, 26 Oct 2005 23:57:40 -0400
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] comment on draft-ietf-mip6-nemo-v4traversal-00
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
Date: Wed, 26 Oct 2005 23:57:37 -0400
Message-ID: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCDC8@ftmailserver.flariontech.com>
Thread-Topic: [Mip6] comment on draft-ietf-mip6-nemo-v4traversal-00
Thread-Index: AcXaqOGUZbwcsa+YTqSZf4yK8uLIrgAAVhiA
From: "Soliman, Hesham" <H.Soliman@flarion.com>
To: "Romain KUNTZ" <kuntz@sfc.wide.ad.jp>, <mip6@ietf.org>
X-OriginalArrivalTime: 27 Oct 2005 03:57:40.0227 (UTC)
	FILETIME=[9367B530:01C5DAAA]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Content-Transfer-Encoding: quoted-printable
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Hello Romain,


 > Dear authors of draft-ietf-mip6-nemo-v4traversal-00,
 >=20
 > First of all thank you for providing this draft. We were=20
 > eager to see it=20
 > as the v4 traversal feature is one of the most important=20
 > missing feature=20
 > for IPv6-mobility deployement.
 >=20
 > About the draft, I have a concern regarding how the DSMIPv6=20
 > MN can get a=20
 > new IPv4 CoA when roaming in an IPv4 network. Sorry if I=20
 > have misread=20
 > the draft, but no hints are provided in the draft, and the solutions=20
 > proposed by RFC 3344 (MIPv4) cannot apply here, as it is=20
 > based on the=20
 > Agent Advertisement.=20

=3D> The Agent advertisement does not allocate addresses. In MIPv4
the MN can either use its home address on the foreign link or=20
obtain a colocated CoA through DHCP or other mechanisms like
PPP. In the case of DSMIPv6 you can assume the same, i.e. DHCP, PPP
or any other mechanism at the visited network. MIPv4 is not used
in this solution.

Hesham

   Or does a Foreign Agent must be present in each=20
 > IPv4 network we roam into?
 >=20
 > Regards,
 >=20
 > --=20
 > Romain KUNTZ
 > kuntz@sfc.wide.ad.jp
 >=20
 > _______________________________________________
 > Mip6 mailing list
 > Mip6@ietf.org
 > https://www1.ietf.org/mailman/listinfo/mip6
 >=20

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D
This email may contain confidential and privileged material for the sole =
use
 of the intended recipient.  Any review or distribution by others is =
strictly
 prohibited.  If you are not the intended recipient please contact the =
sender
 and delete all copies.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D


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



From mip6-bounces@ietf.org Thu Oct 27 00:55:55 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EUznv-0001Cj-KW; Thu, 27 Oct 2005 00:55:55 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EUznq-0001C1-Co
	for mip6@megatron.ietf.org; Thu, 27 Oct 2005 00:55:51 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA23255
	for <mip6@ietf.org>; Thu, 27 Oct 2005 00:55:33 -0400 (EDT)
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EV016-0007fm-ME
	for mip6@ietf.org; Thu, 27 Oct 2005 01:09:35 -0400
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id 0FEE989848;
	Thu, 27 Oct 2005 07:55:37 +0300 (EEST)
Message-ID: <43605DD5.9000901@kolumbus.fi>
Date: Thu, 27 Oct 2005 07:55:49 +0300
From: Jari Arkko <jari.arkko@kolumbus.fi>
User-Agent: Mozilla Thunderbird 1.0 (X11/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
Subject: Re: CoA and AAA (was Re: [Mip6] General comments/questions on MIPv6
	bootstrapping)
References: <200510262153.j9QLrUVC016451@givry.rennes.enst-bretagne.fr>
In-Reply-To: <200510262153.j9QLrUVC016451@givry.rennes.enst-bretagne.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
Content-Transfer-Encoding: 7bit
Cc: mip6@ietf.org, Vijay Devarapalli <vijayd@iprg.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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Francis Dupont wrote:

>=> the CoA is an important parameter of the network access control
>which is done by the AAAL so the AAAH can check with the AAAL
>the CoA (this is what I mean by the AAA procedure can provide
>an authentication of the CoA using a trusted third party (which
>is the AAAL)).
>  
>
I do not think it makes sense to extend the bootstrapping
schemes to provide AAA-based care-of address verification.
(There might be some interest to look at using access network's
help in such checks, in research mode, but this appears
to be possible without AAA.)

One reason for this is separation of functions. It would
be unfortunate if route optimization depended on
specific form of bootstrapping we performed. What's
more, bootstrapping would have to be performed for
every move to a new care-of address, which would
put bootstrapping on critical path, decrease performance,
and in general do something that the bootstrapping work,
in my opinion, was not intended to do.

Secondly, AAA has significant limitations in the
sense that we can't necessarily assume a world
wide AAA where everything can roam everywhere,
and that all links have AAA. Particularly, correspondent
nodes most likely do no thave AAA. My private home network,
for instance, does not, and my company network
does not roam with anything else. And CNN.COM
has no AAA.

Finally, there does not appear to be any reason for
adding this functionality. We already have RFC 3775
route optimization, which, in my opinion, is sufficient
as far as the security requirements go. Where you
are worried about performance, we already have
improved methods that take the care-of address
check out of the critical path. See draft-arkko-mipshop-cba-cga,
for instance.  No AAA was needed to achieve this
speedup. If you are worried about security, there
are again multiple things that we can do without
AAA. For instance, CGA adds a small amount of
security even for the CGA case, though can not
eliminate the need for the test. The test could,
however, be completely eliminated if we did have
some assistance from the access network and
trust between the access network and the
correspondent nodes. This latter is a much
tougher assumption than we have had so far,
perhaps too tough. But people have looked
at schemes where SEND-like certificates
of address prefixes are used in a global manner.
If you assume this, then you can ask the local
router to give an address assignment certificate,
which can be later used to prove your topological
address is correct - without AAA.

--Jari


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



From mip6-bounces@ietf.org Thu Oct 27 01:53:01 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EV0hA-0002GD-Qa; Thu, 27 Oct 2005 01:53:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EV0h7-0002G6-NS
	for mip6@megatron.ietf.org; Thu, 27 Oct 2005 01:52:58 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA25835
	for <mip6@ietf.org>; Thu, 27 Oct 2005 01:52:40 -0400 (EDT)
Received: from mail.sfc.wide.ad.jp ([203.178.142.146])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EV0uP-0001E0-Kd
	for mip6@ietf.org; Thu, 27 Oct 2005 02:06:43 -0400
Received: from [203.178.138.10] (unknown [203.178.138.10])
	by mail.sfc.wide.ad.jp (Postfix) with ESMTP id 0934F4C0FE
	for <mip6@ietf.org>; Thu, 27 Oct 2005 14:52:47 +0900 (JST)
Message-ID: <43606B99.5030905@sfc.wide.ad.jp>
Date: Thu, 27 Oct 2005 14:54:33 +0900
From: Romain KUNTZ <kuntz@sfc.wide.ad.jp>
Organization: Keio University
User-Agent: Mozilla Thunderbird 1.0.6 (Macintosh/20050716)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: mip6@ietf.org
Subject: Re: [Mip6] comment on draft-ietf-mip6-nemo-v4traversal-00
References: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCDC8@ftmailserver.flariontech.com>
In-Reply-To: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCDC8@ftmailserver.flariontech.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Content-Transfer-Encoding: 7bit
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Hello,

Soliman, Hesham wrote:
> => The Agent advertisement does not allocate addresses. In MIPv4
> the MN can either use its home address on the foreign link or 
> obtain a colocated CoA through DHCP or other mechanisms like
> PPP. In the case of DSMIPv6 you can assume the same, i.e. DHCP, PPP
> or any other mechanism at the visited network. MIPv4 is not used
> in this solution.

I see. Sorry for the confusion and thanks for the clarification.

-- 
Romain KUNTZ
kuntz@sfc.wide.ad.jp


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



From mip6-bounces@ietf.org Thu Oct 27 05:15:18 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EV3qw-0003Ww-B1; Thu, 27 Oct 2005 05:15:18 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EV3qs-0003VF-9v
	for mip6@megatron.ietf.org; Thu, 27 Oct 2005 05:15:15 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA17247
	for <mip6@ietf.org>; Thu, 27 Oct 2005 05:14:58 -0400 (EDT)
Received: from mail.sfc.wide.ad.jp ([203.178.142.146])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EV44A-0003nQ-Hy
	for mip6@ietf.org; Thu, 27 Oct 2005 05:29:01 -0400
Received: from iseran.local (jules.nautilus6.org [203.178.138.2])
	by mail.sfc.wide.ad.jp (Postfix) with ESMTP id CE8534C63D
	for <mip6@ietf.org>; Thu, 27 Oct 2005 18:14:35 +0900 (JST)
Date: Thu, 27 Oct 2005 18:14:41 +0900
From: Thierry Ernst <ernst@sfc.wide.ad.jp>
To: mip6@ietf.org
Subject: Re: [Mip6] load balancing and HA (re-)assignment : which WG is
	theright venue ?
Message-Id: <20051027181441.78ea0665.ernst@sfc.wide.ad.jp>
In-Reply-To: <0B40B6F9CB990B428819561A2A55613A144DEE@de01exm69.ds.mot.com>
References: <0B40B6F9CB990B428819561A2A55613A144DEE@de01exm69.ds.mot.com>
Organization: Keio University
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-Spam-Score: 0.0 (/)
X-Scan-Signature: 5ebbf074524e58e662bc8209a6235027
Content-Transfer-Encoding: 7bit
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org


Hi Vidya,

I'm considering the case where there are multiple HAs on different
links. There are multiple paths, so this is a multihomed configuration.
Regarding load balancing, this is one of the goals (or benefit, if you
like) of multihoming [2]

[1]
http://www.nautilus6.org/doc/drafts/draft-ietf-nemo-multihoming-issues-04.txt
http://www.nautilus6.org/doc/drafts/draft-ietf-nemo-multihoming-issues-04.html
See section 4.3 "HA Synchronization"

[2]
http://www.nautilus6.org/doc/drafts/draft-ernst-monami6-multihoming-goals-and-benefits-02.txt
http://www.nautilus6.org/doc/drafts/draft-ernst-monami6-multihoming-goals-and-benefits-02.html

Thierry.



 On Wed, 26 Oct 2005 10:45:35 -0400
"Narayanan Vidya-CVN065" <vidya@motorola.com> wrote:

> Maybe I am missing something fundamental - what does HA
> assignment/load balancing/re-assignment have to do with multi-homing? 
> 
> Vidya 
> 
> > -----Original Message-----
> > From: mip6-bounces@ietf.org [mailto:mip6-bounces@ietf.org] On 
> > Behalf Of Thierry Ernst
> > Sent: Wednesday, October 26, 2005 5:18 AM
> > To: mip6@ietf.org
> > Subject: Re: [Mip6] load balancing and HA (re-)assignment : 
> > which WG is theright venue ?
> > 
> > 
> > 
> > > > Probably yes, but how the MIP6 group will consider the NEMO 
> > > > specificities ? Isn't this also confusing for the group ?
> > > 
> > > Me deviating... I agree that the MIP6 WG should somehow consult
> > > the NEMO WG with respect to NEMO specificities.
> > 
> > > > Monami6 has 4 items. How many for MIP6 ?
> > > 
> > > Well, current charter mentions 8 milestones, 17 I-Ds, 2 
> > RFCs (subject 
> > > to update at the meeting).
> > > 
> > > Monami6 has 4 milestones.  I personally believe that is focused
> > > and motivating.
> > > 
> > > >> I would like to get a sense of the WG regarding this point.
> > > >> 
> > > >> I think we will have sufficient time at Vancounver to add such
> > > >a > discussion on the Monami6 agenda if someone want to lead it.
> > > >> 
> > > >> => agenda sharing is enough issue. One can believe it is 
> > fine (it 
> > > >> gives more time) but past experiences are not good (duplicate 
> > > >> items, more likely schedule conflicts, etc).
> > > > 
> > > > This is exactly why everything related to multihoming in 
> > MIP6/NEMO 
> > > > should be moved to Monami6, particularly when it concerns 
> > both MIP6 
> > > > and NEMO.
> > > 
> > > But which monami6 WG Deliverable?  The closest I could find is 
> > > "Flow/binding policies exchange" but this terminology has not been
> > > discussed at all here.
> > 
> > Actually, why not ? I was thinking about a new deliverable 
> > (because it's clearer), but debating the exact features may 
> > well lead us to consider HA-reassigment in any of the solutions. 
> > 
> > What I mean is that even if HA-reassignment is done in MIP6, 
> > both HA-reasssigment, multiple CoA registration, and policies 
> > exchanges have to be compatible. 
> > 
> > By the way, I would like to point to issue "HA 
> > synchronization" of draft-ietf-nemo-multihoming-issues. 
> > 
> > > During Monami6 BoF it was discussed thoroughly what exactly 
> > should the 
> > > WG work on so a Charter was issued.  Is the Monami6 trying 
> > to modify 
> > > its Charter with new items so quickly after creation?
> > 
> > Why not ?
> > 
> > Well, adding a new item would require Monami6 to be 
> > rechartered if that given work doesn't correspond to the 
> > charter. But there is no rules at the IETF that a WG just 
> > approved cannot be rechartered, so this is not a dead end, 
> > and I wouldn't mind to negociate that if this is the sense of 
> > the MIP6/NEMO/MONAMI6 WG that this is the right thing to do.
> > 
> > But, I don't think this wouldn't be a dramatic change to the
> > charter..
> > 
> > My personal view on all of this is that working on this topic 
> > in Monami6 would make it easier for everyone, the IETFers, 
> > and the people interested in the standards defined by the IETF.
> > 
> > Thierry
> > 
> > 
> > 
> > 
> > 

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



From mip6-bounces@ietf.org Thu Oct 27 05:40:17 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EV4F7-0001oz-Qz; Thu, 27 Oct 2005 05:40:17 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EV4F5-0001oa-Ap
	for mip6@megatron.ietf.org; Thu, 27 Oct 2005 05:40:15 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA18446
	for <mip6@ietf.org>; Thu, 27 Oct 2005 05:39:59 -0400 (EDT)
Received: from mout.perfora.net ([217.160.230.41])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EV4SP-0004TY-8L
	for mip6@ietf.org; Thu, 27 Oct 2005 05:54:02 -0400
Received: from [85.101.251.215] (helo=Alperyegin)
	by mrelay.perfora.net with ESMTP (Nemesis),
	id 0MKp2t-1EV4Er0Mke-0004ih; Thu, 27 Oct 2005 05:40:01 -0400
From: "Alper Yegin" <alper.yegin@yegin.org>
To: <Francis.Dupont@enst-bretagne.fr>
Subject: RE: [Mip6] General comments/questions on MIPv6 bootstrapping 
Date: Thu, 27 Oct 2005 12:39:53 +0300
Message-ID: <001001c5dada$663d8280$0302a8c0@Alperyegin>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
Importance: Normal
In-Reply-To: <200510262030.j9QKUW5P016051@givry.rennes.enst-bretagne.fr>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Provags-ID: perfora.net abuse@perfora.net
	login:abf7a4bb310ea4dfc9b6841113e2970f
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 200d029292fbb60d25b263122ced50fc
Content-Transfer-Encoding: 7bit
Cc: mip6@ietf.org,
	'COMBES Jean-Michel RD-MAPS-ISS' <jeanmichel.combes@francetelecom.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Francis,

>    > => the document recommends DHCPv6 in a context where its security
>    > can't be insured. IMHO this is a major issue.
> 
>    Actually, what we tried to say was "secure your DHCP in whatever
way
> you
>    are securing it." Just because you are carrying an HA information
does
>    not require that the DHCP signaling be more or less secured than
what
>    the operator does normally.
> 
> => but it seems the operator does normally not use DHCP...

OK, you are making another point now....

On that point, I'm guessing you are only considering 3GPP operators,
right? Please also consider 3GPP2 and WiMAX operators. Both are using
DHCP in their architectures.

>    If you agree to that, and have a better way to capture in the
document,
>    please propose some text.
> 
> => as I've said my first concern is the document should be split
between
> AAA and DHCP...
> 
>    [For DHCP security, the operator may rely on lower-layer security,
or
>    some other mechanism, e.g., draft-yegin-eap-boot-rfc3118-00.txt,
etc.]
> 
> => argh, this draft is already expired... (I've it but we should not
> rely on it). IMHO the idea to establish the DHCP shared secret in the
> AAA phase is good (and similar to draft-dupont-mipv6-aaa-01.txt...).
> You are saying too much or not enough (:-).

You may be right. We shall not get too much into DHCP security. 

> 
>    > => the paragraph begins by "security sensitive" and "requires".
>    > The proposed solutions are lower-layer security, something which
> can't
>    > be assumed to be always available,
> 
>    Many, if not all, deployments rely on lower-layer security. This is
>    mostly an architectural issue. DSL operators know that the DHCP is
run
>    over physically-secured lines, hence the current deployments don't
>    involved DHCP-level security....
> 
> => hum, the 802.11 final link is not so secure...

In most, it is not secure. In some, it is. Security is improving with
11i deployments (at what rate, I don't know). 

Well, anyways. These are again architectural and deployment issues. We
are just carrying yet another configuration parameter with DHCP, that's
it.

> IMHO in the scenario the only local secure mechanism is the network
> access control, so it should be used to piggyback things in it or
> to derive a shared secret for protection, shouldn't it?

If you can elaborate, that'd help me understand what you are suggesting.


> 
>    > and DHCPv6 security, which doesn't
>    > work well in the context (this is my previous comment). It
finishes
>    > by explaining the security in fact doesn't matter: this is both
>    > arguable (security matters soon or late, and HA assignment is
more
>    > vulnerable then HA discovery) and not consistent with the
>    > beginning.
> 
>    I see your point. The text is inconsistent.
> 
> => yes, and I believe the real issue is there is no good and general
> way to provide the required level of security.

There is at least one practical way: relying on the lower-layer
security. That's how the DSL and 3GPP2 operator networks use DHCP. That
seems sufficient. [this is a good discussion for DHC WG]


> 
>    >    CoA ownership issue is outside the scope of "MIP6
bootstrapping"
>    >    problem.
>    >
>    > => so we have to find a way to put it inside!
> 
>    Sorry I don't understand. Why do you see this issue as part of the
> "MIP6
>    bootstrapping problem", which deals with HA, HoA, MN-HA SA
>    configuration?
> 
> => because AAA is the only mechanism which can provide a solution.
> In the document the only feature provided by AAA+DHCP is HA
assignment.
> For any person who has worked on MIPv6/AAA stuff this is incredibly
> limited.

MN-HA SA is also generated with the help of AAA. This is not discussed
in this document, but part of the overall solution. For anything else,
like CoA "authorization", I'd say interesting but definitely outside the
scope of the bootstrapping problem space. Let's create another thread
and discuss it.

Alper



> 
> Regards
> 
> Francis.Dupont@enst-bretagne.fr
> 
> PS: cf my checking message in the IPsec list:
> http://msgs.securepoint.com/cgi-bin/get/ipsec-0510/26.html
> 
> Do you mind briefly stating why you think this is better than the DNS
> and DHCP-based HA discovery/assignment?
> 
> => it is far more general, there is only two constraints:
>  - IKEv2 has to be used (but it seems it is already in all
bootstrapping
>    proposals)
>  - the anycast address has to be known (exactly as the current DHAAD).
>    Note this is compatible with DNS or DHCP-based discovery: in place
>    of giving unicast addresses of servers one can answer with anycast
>    addresses of server groups.
> I've found only advantages at the exception of the compatibity with
> NEMO: a second anycast IID should be assigned for NEMO HAs as there is
> no way to distinguish between MIPv6 and NEMO HAs.
> 
> Regards
> 
> Francis.Dupont@enst-bretagne.fr
> 
> 


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



From mip6-bounces@ietf.org Thu Oct 27 05:48:11 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EV4Ml-00063i-M5; Thu, 27 Oct 2005 05:48:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EV4Mj-00063a-EA
	for mip6@megatron.ietf.org; Thu, 27 Oct 2005 05:48:09 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA18751
	for <mip6@ietf.org>; Thu, 27 Oct 2005 05:47:53 -0400 (EDT)
Received: from mout.perfora.net ([217.160.230.41])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EV4a4-0004fN-Io
	for mip6@ietf.org; Thu, 27 Oct 2005 06:01:57 -0400
Received: from [85.101.251.215] (helo=Alperyegin)
	by mrelay.perfora.net with ESMTP (Nemesis),
	id 0MKoyl-1EV4Mc1hFp-0003y7; Thu, 27 Oct 2005 05:48:02 -0400
From: "Alper Yegin" <alper.yegin@yegin.org>
To: <Francis.Dupont@enst-bretagne.fr>,
	"'Chowdhury, Kuntal'" <kchowdhury@starentnetworks.com>
Subject: RE: [Mip6] General comments/questions on MIPv6 bootstrapping 
Date: Thu, 27 Oct 2005 12:47:55 +0300
Message-ID: <001101c5dadb$8525ff00$0302a8c0@Alperyegin>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
Importance: Normal
In-Reply-To: <200510262338.j9QNcio1017427@givry.rennes.enst-bretagne.fr>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Provags-ID: perfora.net abuse@perfora.net
	login:abf7a4bb310ea4dfc9b6841113e2970f
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Content-Transfer-Encoding: 7bit
Cc: mip6@ietf.org,
	'COMBES Jean-Michel RD-MAPS-ISS' <jeanmichel.combes@francetelecom.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org



Francis,

This is n+1st configuration parameter carried by DHCPv6. So, I don't see
why we suddenly hit a DHCP security problem that must be fixed now. Is
there an IAB recommendation that states "until the DHCPv6 security is
fixed, defining new options are on hold!"?

Unless you identify an interaction between this particular option and
the DHCP security, I don't see fixing the DHCP security a MUST or a show
stopper for this work.

I acknowledge the security issues of DHCPv6. There is ongoing (stalled?)
work in the DHC WG. We shall definitely discuss this issue there.

Btw, this issue is not specific to DHCPv6, but also applicable to
DHCPv4. Also, note that you may never get the result you are looking for
(DHCP-level crypto-security) due to the reliance on the L1/L2 security.
But again, we can discuss these on the DHC mailing list.

Alper

 

>  In your previous mail you wrote:
> 
>    > => so you are the forth member of the DT who seems to share my
>    > frustration!
> 
>    [KC>] This draft out of the DT is -00 version. So, some changes are
>    expected when it is discussed in a broader audience. I am not
>    necessarily agreeing with you that we MUST do something to fix the
>    DHCPv6 security mechanism in this specific draft.
> 
> => but IMHO we MUST fix the security of the solution before going
> to the IESG.
> 
>    BTW, I think you should post your concern(s) about DHCPv6 security
in
>    DHC WG list.
> 
> => as the issue comes from the use of DHCPv6, the first question is
> whether to use DHCPv6 is a right idea. At least to rely on the work
> of another WG (work which is not in its charter, a charter you should
> read BTW) is a pretty bad idea.
> 
> Thanks
> 
> Francis.Dupont@enst-bretagne.fr


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



From mip6-bounces@ietf.org Thu Oct 27 08:17:23 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EV6cr-0004W6-Ot; Thu, 27 Oct 2005 08:12:57 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EV6cq-0004W0-Lh
	for mip6@megatron.ietf.org; Thu, 27 Oct 2005 08:12:56 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA25129
	for <mip6@ietf.org>; Thu, 27 Oct 2005 08:12:39 -0400 (EDT)
Received: from motgate.mot.com ([129.188.136.100])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EV6qB-0008RM-Nk
	for mip6@ietf.org; Thu, 27 Oct 2005 08:26:45 -0400
Received: from az33exr02.mot.com (az33exr02.mot.com [10.64.251.232])
	by motgate.mot.com (Motorola/Motgate) with ESMTP id j9RCCqCX012529;
	Thu, 27 Oct 2005 05:12:53 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by az33exr02.mot.com (8.13.1/8.13.0) with ESMTP id j9RCKLVh005499;
	Thu, 27 Oct 2005 07:20:22 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id 590B4865980; Thu, 27 Oct 2005 14:12:50 +0200 (CEST)
Message-ID: <4360C442.8050907@motorola.com>
Date: Thu, 27 Oct 2005 14:12:50 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: "Soliman, Hesham" <H.Soliman@flarion.com>
Subject: Re: [Mip6] comment on draft-ietf-mip6-nemo-v4traversal-00
References: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCDC8@ftmailserver.flariontech.com>
In-Reply-To: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCDC8@ftmailserver.flariontech.com>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Content-Transfer-Encoding: 7bit
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Soliman, Hesham wrote:

> Hello Romain,
> 
> 
>> Dear authors of draft-ietf-mip6-nemo-v4traversal-00,
>> 
>> First of all thank you for providing this draft. We were eager to 
>> see it as the v4 traversal feature is one of the most important 
>> missing feature for IPv6-mobility deployement.
>> 
>> About the draft, I have a concern regarding how the DSMIPv6 MN can
>>  get a new IPv4 CoA when roaming in an IPv4 network. Sorry if I
>> have misread the draft, but no hints are provided in the draft, and
>> the solutions proposed by RFC 3344 (MIPv4) cannot apply here, as it
>> is based on the Agent Advertisement.
> 
> => The Agent advertisement does not allocate addresses.

But it does movement detection.  A DSMIPv6 that detects movement based
only on IPv6 RA can't detect movement when on a v4-only access network.

> In MIPv4 the MN can either use its home address on the foreign link 
> or obtain a colocated CoA through DHCP or other mechanisms like PPP.

Right, and when MIP4 is used with NAI (RFC specifies that) and ppp then
a stable IPv4 address is provided.  DSMIPv6 doesn't currently have that.

> In the case of DSMIPv6 you can assume the same, i.e. DHCP, PPP or any
>  other mechanism at the visited network.

I agree.

> MIPv4 is not used in this solution.

And because of the reasons above, a DSMIPv6 MN that needs to detect its
movement on a v4-only access network will still need a MIP4 stack.  In
addition to the reasons above, the MIP4 stack is also needed on the HA
to perform proxy ARP for the IPv4 Home Address (a thing that DSMIPv6
doesn't).

Alex


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



From mip6-bounces@ietf.org Thu Oct 27 08:35:24 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EV6ya-0000gO-PF; Thu, 27 Oct 2005 08:35:24 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EV6yZ-0000dd-0X
	for mip6@megatron.ietf.org; Thu, 27 Oct 2005 08:35:23 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA26209
	for <mip6@ietf.org>; Thu, 27 Oct 2005 08:35:05 -0400 (EDT)
Received: from coliposte.enst-bretagne.fr ([192.108.115.12])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EV7Bv-0000YL-L2
	for mip6@ietf.org; Thu, 27 Oct 2005 08:49:12 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by coliposte.enst-bretagne.fr (8.12.10/8.12.10/2004.10.03) with ESMTP
	id j9RCZChR021405; Thu, 27 Oct 2005 14:35:12 +0200
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by coliposte.enst-bretagne.fr (8.12.10/8.12.10/2004.09.01) with ESMTP
	id j9RCXwls021247; Thu, 27 Oct 2005 14:33:58 +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
	j9RCXxaQ020330; Thu, 27 Oct 2005 14:33:59 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200510271233.j9RCXxaQ020330@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Jari Arkko <jari.arkko@kolumbus.fi>
Subject: Re: CoA and AAA (was Re: [Mip6] General comments/questions on MIPv6
	bootstrapping) 
In-reply-to: Your message of Thu, 27 Oct 2005 07:55:49 +0300.
	<43605DD5.9000901@kolumbus.fi> 
Date: Thu, 27 Oct 2005 14:33:59 +0200
X-Virus-Scanned: amavisd-new at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Cc: mip6@ietf.org, Vijay Devarapalli <vijayd@iprg.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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   >=> the CoA is an important parameter of the network access control
   >which is done by the AAAL so the AAAH can check with the AAAL
   >the CoA (this is what I mean by the AAA procedure can provide
   >an authentication of the CoA using a trusted third party (which
   >is the AAAL)).

   I do not think it makes sense to extend the bootstrapping
   schemes to provide AAA-based care-of address verification.

=> I disagree: there is no such verification today and even
it is not needed it is always fine to be more secure.

   (There might be some interest to look at using access network's
   help in such checks, in research mode, but this appears
   to be possible without AAA.)
   
=> how you provide this without AAA?

   One reason for this is separation of functions. It would
   be unfortunate if route optimization depended on

=> Route Optimization??? We speak about initial MN-HA!

   specific form of bootstrapping we performed. What's
   more, bootstrapping would have to be performed for
   every move to a new care-of address,

=> this is not true. The only limit is the MN must stay in
the same AAA domain (i.e., the integrated scenario applies)
if we want to keep the CoA verification.

   Secondly, AAA has significant limitations in the
   sense that we can't necessarily assume a world
   wide AAA where everything can roam everywhere,

=> this discussion is not without a context: we are in
the integrated scenario.

   and that all links have AAA.

=> and DHCPv6 (:-)...

   Particularly, correspondent nodes most likely do no thave AAA.

=> we DON'T discuss about RO!

(I don't answer to other comments which are 100% out of the scope).

Regards

Francis.Dupont@enst-bretagne.fr

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



From mip6-bounces@ietf.org Thu Oct 27 09:14:07 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EV7a2-0004lq-Vk; Thu, 27 Oct 2005 09:14:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EV7a1-0004kn-0O
	for mip6@megatron.ietf.org; Thu, 27 Oct 2005 09:14:05 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA27955
	for <mip6@ietf.org>; Thu, 27 Oct 2005 09:13:49 -0400 (EDT)
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EV7nM-0001Sv-Rl
	for mip6@ietf.org; Thu, 27 Oct 2005 09:27:54 -0400
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id 9254F89871;
	Thu, 27 Oct 2005 16:13:49 +0300 (EEST)
Message-ID: <4360D299.4040908@kolumbus.fi>
Date: Thu, 27 Oct 2005 16:14:01 +0300
From: Jari Arkko <jari.arkko@kolumbus.fi>
User-Agent: Mozilla Thunderbird 1.0 (X11/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
Subject: Re: CoA and AAA (was Re: [Mip6] General comments/questions on MIPv6
	bootstrapping)
References: <200510271233.j9RCXxaQ020330@givry.rennes.enst-bretagne.fr>
In-Reply-To: <200510271233.j9RCXxaQ020330@givry.rennes.enst-bretagne.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Content-Transfer-Encoding: 7bit
Cc: mip6@ietf.org, Vijay Devarapalli <vijayd@iprg.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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Francis Dupont wrote:

> 
>=> Route Optimization??? We speak about initial MN-HA!
>  
>
Sorry. Maybe I need to read the original thread. Why would
you care about care-of address verification for the initial
MN-HA? Or more to the point, why would you need anything
more for the verification than what we would get from
running a protocol such as IKEv2 between the MN and the
HA? Or is this about the pseudonat attack in IKEv2?

--Jari


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



From mip6-bounces@ietf.org Thu Oct 27 09:35:37 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EV7ur-000896-3U; Thu, 27 Oct 2005 09:35:37 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EV7uq-00087s-37
	for mip6@megatron.ietf.org; Thu, 27 Oct 2005 09:35:36 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29645
	for <mip6@ietf.org>; Thu, 27 Oct 2005 09:35:20 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EV88A-0002Dq-91
	for mip6@ietf.org; Thu, 27 Oct 2005 09:49:25 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id j9RDYC820372; Thu, 27 Oct 2005 15:34:12 +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
	j9RDYBjA020857; Thu, 27 Oct 2005 15:34:12 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200510271334.j9RDYBjA020857@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: "Alper Yegin" <alper.yegin@yegin.org>
Subject: Re: [Mip6] General comments/questions on MIPv6 bootstrapping 
In-reply-to: Your message of Thu, 27 Oct 2005 12:39:53 +0300.
	<001001c5dada$663d8280$0302a8c0@Alperyegin> 
Date: Thu, 27 Oct 2005 15:34:11 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Cc: mip6@ietf.org,
	'COMBES Jean-Michel RD-MAPS-ISS' <jeanmichel.combes@francetelecom.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   On that point, I'm guessing you are only considering 3GPP operators,
   right?

=> no, I live in Europe and I know 3GPP operators won't support
IPv6 soon.

   > => argh, this draft is already expired... (I've it but we should not
   > rely on it). IMHO the idea to establish the DHCP shared secret in the
   > AAA phase is good (and similar to draft-dupont-mipv6-aaa-01.txt...).
   > You are saying too much or not enough (:-).
   
   You may be right. We shall not get too much into DHCP security. 
   
=> after reading the DHC WG charter I believe we shall simply
*not* rely on DHCP security!

   > IMHO in the scenario the only local secure mechanism is the network
   > access control, so it should be used to piggyback things in it or
   > to derive a shared secret for protection, shouldn't it?
   
   If you can elaborate, that'd help me understand what you are suggesting.
   
=> I can explain (in fact there is even a message in the list with
a reference to an expired draft proposing this) but I believe now
it is not the proper way. Please forget DHCP security and use
only the lower-link security.
   
   There is at least one practical way: relying on the lower-layer
   security.

=> IMHO it is the only practical way!

   That's how the DSL and 3GPP2 operator networks use DHCP. That
   seems sufficient. [this is a good discussion for DHC WG]
   
=> I agree: the scenario is not too limited when we add this constraint.

   MN-HA SA is also generated with the help of AAA. This is not discussed
   in this document, but part of the overall solution. For anything else,
   like CoA "authorization", I'd say interesting but definitely outside the
   scope of the bootstrapping problem space. Let's create another thread
   and discuss it.
   
=> fifth (the next one I'll get half of the DT :-)!
It seems the "CoA and AAA" thread is the right one, but in part is
on a closed DT list...

Regards

Francis.Dupont@enst-bretagne.fr

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



From mip6-bounces@ietf.org Thu Oct 27 09:41:26 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EV80T-0003NY-HC; Thu, 27 Oct 2005 09:41:25 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EV80S-0003NT-4K
	for mip6@megatron.ietf.org; Thu, 27 Oct 2005 09:41:24 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA00017
	for <mip6@ietf.org>; Thu, 27 Oct 2005 09:41:07 -0400 (EDT)
Received: from coliposte.enst-bretagne.fr ([192.108.115.12])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EV8Dm-0002P8-Vp
	for mip6@ietf.org; Thu, 27 Oct 2005 09:55:12 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by coliposte.enst-bretagne.fr (8.12.10/8.12.10/2004.10.03) with ESMTP
	id j9RDf9hR030985; Thu, 27 Oct 2005 15:41:09 +0200
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by coliposte.enst-bretagne.fr (8.12.10/8.12.10/2004.09.01) with ESMTP
	id j9RDeals030786; Thu, 27 Oct 2005 15:40:36 +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
	j9RDebLC020920; Thu, 27 Oct 2005 15:40:37 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200510271340.j9RDebLC020920@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: "Alper Yegin" <alper.yegin@yegin.org>
Subject: Re: [Mip6] General comments/questions on MIPv6 bootstrapping 
In-reply-to: Your message of Thu, 27 Oct 2005 12:47:55 +0300.
	<001101c5dadb$8525ff00$0302a8c0@Alperyegin> 
Date: Thu, 27 Oct 2005 15:40:37 +0200
X-Virus-Scanned: amavisd-new at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Cc: mip6@ietf.org,
	'COMBES Jean-Michel RD-MAPS-ISS' <jeanmichel.combes@francetelecom.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

=> after many messages about this in the list you still have to read
I now believe the best solution is simply to *not* rely on the
DHCPv6 security, i.e., to rely on lower-link security.
   
   This is n+1st configuration parameter carried by DHCPv6. So, I don't see
   why we suddenly hit a DHCP security problem that must be fixed now. Is
   there an IAB recommendation that states "until the DHCPv6 security is
   fixed, defining new options are on hold!"?
   
=> if they are security critical we should (:-).

   Unless you identify an interaction between this particular option and
   the DHCP security, I don't see fixing the DHCP security a MUST or a show
   stopper for this work.
   
   I acknowledge the security issues of DHCPv6. There is ongoing (stalled?)
   work in the DHC WG. We shall definitely discuss this issue there.

=> stalled!
   
   Btw, this issue is not specific to DHCPv6, but also applicable to
   DHCPv4.

=> yes, I believe the problem is worse in DHCPv6 but both share
the main issues.

It seems we agree the DHCPv6 security issue is not in the scope
of this WG so I shan't propose even to try to fix it (here or
in the DHC WG).

Thanks

Francis.Dupont@enst-bretagne.fr

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



From mip6-bounces@ietf.org Thu Oct 27 09:50:32 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EV89I-00070O-12; Thu, 27 Oct 2005 09:50:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EV89G-0006wS-H8
	for mip6@megatron.ietf.org; Thu, 27 Oct 2005 09:50:30 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA00566
	for <mip6@ietf.org>; Thu, 27 Oct 2005 09:50:14 -0400 (EDT)
Received: from motgate5.mot.com ([144.189.100.105])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EV8Mb-0002gS-0m
	for mip6@ietf.org; Thu, 27 Oct 2005 10:04:19 -0400
Received: from az33exr03.mot.com (az33exr03.mot.com [10.64.251.233])
	by motgate5.mot.com (8.12.11/Motgate5) with ESMTP id j9RDwUqS012801;
	Thu, 27 Oct 2005 06:58:35 -0700 (MST)
Received: from zfr01srv02.crm.mot.com (zfr01srv02.crm.mot.com [10.161.201.8])
	by az33exr03.mot.com (8.13.1/8.13.0) with ESMTP id j9RDxZsO012979;
	Thu, 27 Oct 2005 08:59:36 -0500 (CDT)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by zfr01srv02.crm.mot.com (Postfix) with ESMTP
	id 62C5D865980; Thu, 27 Oct 2005 15:50:13 +0200 (CEST)
Message-ID: <4360DB15.4090304@motorola.com>
Date: Thu, 27 Oct 2005 15:50:13 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: "Soliman, Hesham" <H.Soliman@flarion.com>
Subject: Re: [Mip6] I-D ACTION:draft-ietf-mip6-nemo-v4traversal-00.txt
References: <A11736FE943F1A408F8BBB1B9F5FE8AD17DE4B@ftmailserver.flariontech.com>
In-Reply-To: <A11736FE943F1A408F8BBB1B9F5FE8AD17DE4B@ftmailserver.flariontech.com>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Content-Transfer-Encoding: 7bit
Cc: mip6@ietf.org, Keiichi SHIMA <keiichi@iijlab.net>,
	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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Soliman, Hesham wrote:

>>> The draft is written to allow implementers and operators
>> to use MIPv6
>>> only no matter where they are on the Internet and for v6
>> and v4 apps.
>> 
>> Hesham, that is a hefty goal.  I'd reach lower, do some small 
>> modular parts that would fit in the current landscape, instead of 
>> building entirely new architectures, solutions to everything a 
>> customer might ever need.
> 
> => You might have had a point if there was no proof that this could 
> be done. The draft is already out there, it's been implemented 
> (except for the NAT traversal part). So there is proof that this is 
> doable with trivial extensions to MIPv6.

It is good to know there is an implementation of DSMIPv6 (w/o the NAT
traversal part).  It is good to know that it's doable.

>> In the past, "universal" mobility solutions have had lesser reach 
>> than expected.  For example, real complete local and global 
>> mobility solutions haven't seen widepsread use despite years of 
>> discussion meeting after meeting, mail after mail.
> 
> => Apples and oranges. One has nothing to do with the other. 
> Furthermore, you're attributing what you see as a failure to a 
> specific reason, for which you have no proof.

I don't, I attribute that to intuition.

> BTW, we have commercial deployments of some of those mechanisms that
> you claim no one has adopted.

Any proof of that?

I'd be happy to learn a certain experimental RFC got deployed on a
larger scale than lab.  It could be used as a strong argument for
changing status quickly.

>> So you agree that DSMIPv6 would compete with MIPv4 to offer 
>> reachability at a permanent MIP4 Home Address, when connected to a 
>> v4-only network and v4 app.
> 
> => Yes; for a green field operator/vendor that has no products to 
> build on.

I don't quite get that, please explain.

In what case would an operator/vendor have to choose between MIP4 and
DSMIPv6?  What's "green field operator"?

Alex


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



From mip6-bounces@ietf.org Thu Oct 27 10:25:28 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EV8h6-0000Le-JO; Thu, 27 Oct 2005 10:25:28 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EV8h5-0000LZ-TK
	for mip6@megatron.ietf.org; Thu, 27 Oct 2005 10:25:28 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02869
	for <mip6@ietf.org>; Thu, 27 Oct 2005 10:25:12 -0400 (EDT)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EV8uR-0003sV-Ko
	for mip6@ietf.org; Thu, 27 Oct 2005 10:39:17 -0400
Received: from az33exr03.mot.com ([10.64.251.233])
	by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id j9REbEIQ009002
	for <mip6@ietf.org>; Thu, 27 Oct 2005 07:37:14 -0700 (MST)
Received: from de01exm69.ds.mot.com (de01exm69.am.mot.com [10.176.8.25])
	by az33exr03.mot.com (8.13.1/8.13.0) with ESMTP id j9REYauo008815
	for <mip6@ietf.org>; Thu, 27 Oct 2005 09:34:37 -0500 (CDT)
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: CoA and AAA (was Re: [Mip6] General comments/questions on
	MIPv6bootstrapping)
Date: Thu, 27 Oct 2005 10:25:13 -0400
Message-ID: <0B40B6F9CB990B428819561A2A55613A14515E@de01exm69.ds.mot.com>
Thread-Topic: CoA and AAA (was Re: [Mip6] General comments/questions on
	MIPv6bootstrapping)
Thread-Index: AcXa+eXr+JFZRvYUQzuV7JqJK8iYVgAA5sQg
From: "Narayanan Vidya-CVN065" <vidya@motorola.com>
To: "Jari Arkko" <jari.arkko@kolumbus.fi>,
	"Francis Dupont" <Francis.Dupont@enst-bretagne.fr>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Content-Transfer-Encoding: quoted-printable
Cc: mip6@ietf.org, Vijay Devarapalli <vijayd@iprg.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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

> >=3D> Route Optimization??? We speak about initial MN-HA!
> > =20
> >
> Sorry. Maybe I need to read the original thread. Why would=20
> you care about care-of address verification for the initial=20
> MN-HA? Or more to the point, why would you need anything more=20
> for the verification than what we would get from running a=20
> protocol such as IKEv2 between the MN and the HA? Or is this=20
> about the pseudonat attack in IKEv2?
>=20

Actually, I have been following the thread and am still confused as to
why CoA verification is needed for bootstrapping.=20

There seems to be confusion on this front among some others as well -
Francis, it will help if you can elaborate a little here.=20

Regards,
Vidya

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



From mip6-bounces@ietf.org Thu Oct 27 10:34:05 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EV8pR-0000np-SP; Thu, 27 Oct 2005 10:34:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EV8pR-0000mi-0g
	for mip6@megatron.ietf.org; Thu, 27 Oct 2005 10:34:05 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03221
	for <mip6@ietf.org>; Thu, 27 Oct 2005 10:33:49 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EV92n-00046G-Lf
	for mip6@ietf.org; Thu, 27 Oct 2005 10:47:55 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id j9REXj825490; Thu, 27 Oct 2005 16:33:45 +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
	j9REXk23021592; Thu, 27 Oct 2005 16:33:46 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200510271433.j9REXk23021592@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: "Narayanan Vidya-CVN065" <vidya@motorola.com>
Subject: Re: CoA and AAA (was Re: [Mip6] General comments/questions on
	MIPv6bootstrapping) 
In-reply-to: Your message of Thu, 27 Oct 2005 10:25:13 EDT.
	<0B40B6F9CB990B428819561A2A55613A14515E@de01exm69.ds.mot.com> 
Date: Thu, 27 Oct 2005 16:33:46 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Cc: Jari Arkko <jari.arkko@kolumbus.fi>,
	Vijay Devarapalli <vijayd@iprg.nokia.com>, mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   Actually, I have been following the thread and am still confused as to
   why CoA verification is needed for bootstrapping. 
   
=> it is not needed (at the exception of a special case I don't
want to support officially). It is just a nice property.

Regards

Francis.Dupont@enst-bretagne.fr

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



From mip6-bounces@ietf.org Thu Oct 27 10:41:51 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EV8wx-0004Li-8N; Thu, 27 Oct 2005 10:41:51 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EV8wv-0004Lc-Hk
	for mip6@megatron.ietf.org; Thu, 27 Oct 2005 10:41:49 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03559
	for <mip6@ietf.org>; Thu, 27 Oct 2005 10:41:33 -0400 (EDT)
Received: from motgate3.mot.com ([144.189.100.103])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EV9AJ-0004Is-2E
	for mip6@ietf.org; Thu, 27 Oct 2005 10:55:39 -0400
Received: from az33exr02.mot.com (az33exr02.mot.com [10.64.251.232])
	by motgate3.mot.com (8.12.11/Motgate3) with ESMTP id j9REvceB008432
	for <mip6@ietf.org>; Thu, 27 Oct 2005 07:57:38 -0700 (MST)
Received: from de01exm69.ds.mot.com (de01exm69.am.mot.com [10.176.8.25])
	by az33exr02.mot.com (8.13.1/8.13.0) with ESMTP id j9REnGfp004059
	for <mip6@ietf.org>; Thu, 27 Oct 2005 09:49:17 -0500 (CDT)
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: CoA and AAA (was Re: [Mip6] General comments/questions on
	MIPv6bootstrapping) 
Date: Thu, 27 Oct 2005 10:41:45 -0400
Message-ID: <0B40B6F9CB990B428819561A2A55613A14517F@de01exm69.ds.mot.com>
Thread-Topic: CoA and AAA (was Re: [Mip6] General comments/questions on
	MIPv6bootstrapping) 
Thread-Index: AcXbA3/ayTbxFs4ESVOrqH6kzeEv4QAADf0g
From: "Narayanan Vidya-CVN065" <vidya@motorola.com>
To: <Francis.Dupont@enst-bretagne.fr>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Content-Transfer-Encoding: quoted-printable
Cc: Jari Arkko <jari.arkko@kolumbus.fi>,
	Vijay Devarapalli <vijayd@iprg.nokia.com>, mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

>  In your previous mail you wrote:
>=20
>    Actually, I have been following the thread and am still=20
> confused as to
>    why CoA verification is needed for bootstrapping.=20
>   =20
> =3D> it is not needed (at the exception of a special case I=20
> don't want to support officially). It is just a nice property.
>=20

What are you gaining from this for bootstrapping? In other words, what
is it that you lose by assigning a HA or HoA or creating an MN-HA SA
without doing CoA verification?=20

I think the main confusion here is that given that CoA is a transient
parameter that keeps changing, while the bootstrapped parameters are
expected not to change often (may be fair to say, as long as the MN
remains powered up, but that may be debatable), what can be the possible
gain of verifying the very first CoA of the MN alone?=20

Or, maybe I completely misunderstood your point :)=20

Regards,
Vidya

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



From mip6-bounces@ietf.org Thu Oct 27 10:50:58 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EV95m-0003lU-IJ; Thu, 27 Oct 2005 10:50:58 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EV94y-0003SO-Ha; Thu, 27 Oct 2005 10:50:08 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03957;
	Thu, 27 Oct 2005 10:49:52 -0400 (EDT)
Received: from [132.151.6.50] (helo=newodin.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1EV9IH-0004Wr-AC; Thu, 27 Oct 2005 11:03:56 -0400
Received: from mlee by newodin.ietf.org with local (Exim 4.43)
	id 1EV94s-0000Ir-K0; Thu, 27 Oct 2005 10:50:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1EV94s-0000Ir-K0@newodin.ietf.org>
Date: Thu, 27 Oct 2005 10:50:02 -0400
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 386e0819b1192672467565a524848168
Cc: mip6@ietf.org
Subject: [Mip6] I-D ACTION:draft-ietf-mip6-mipext-advapi-05.txt 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

--NextPart

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

	Title		: Extension to Sockets API for Mobile IPv6
	Author(s)	: S. Chakrabarti, E. Nordmark
	Filename	: draft-ietf-mip6-mipext-advapi-05.txt
	Pages		: 33
	Date		: 2005-10-27
	
This document describes data structures and API support for Mobile
   IPv6 as an extension to the Advanced Socket API for IPv6.

   Just the 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.

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

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


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

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


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

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-mip6-mipext-advapi-05.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

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

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

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

ENCODING mime
FILE /internet-drafts/draft-ietf-mip6-mipext-advapi-05.txt

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

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


--OtherAccess--

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

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

--NextPart--





From mip6-bounces@ietf.org Thu Oct 27 12:04:47 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EVAFD-0005J3-M7; Thu, 27 Oct 2005 12:04:47 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EVAFC-0005Iq-D4
	for mip6@megatron.ietf.org; Thu, 27 Oct 2005 12:04:46 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03641
	for <mip6@ietf.org>; Thu, 27 Oct 2005 12:04:30 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EVASX-0007Py-Jr
	for mip6@ietf.org; Thu, 27 Oct 2005 12:18:37 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id j9RG4I900897; Thu, 27 Oct 2005 18:04: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
	j9RG4IVa022039; Thu, 27 Oct 2005 18:04:18 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200510271604.j9RG4IVa022039@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: "Narayanan Vidya-CVN065" <vidya@motorola.com>
Subject: Re: CoA and AAA (was Re: [Mip6] General comments/questions on
	MIPv6bootstrapping) 
In-reply-to: Your message of Thu, 27 Oct 2005 10:41:45 EDT.
	<0B40B6F9CB990B428819561A2A55613A14517F@de01exm69.ds.mot.com> 
Date: Thu, 27 Oct 2005 18:04:18 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Cc: Jari Arkko <jari.arkko@kolumbus.fi>,
	Vijay Devarapalli <vijayd@iprg.nokia.com>, mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   > => it is not needed (at the exception of a special case I 
   > don't want to support officially). It is just a nice property.
   
   What are you gaining from this for bootstrapping?

=> better security (a fake CoA doesn't work).

   In other words, what is it that you lose by assigning a HA or HoA
   or creating an MN-HA SA without doing CoA verification?
   
=> nothing.

   I think the main confusion here is that given that CoA is a transient
   parameter that keeps changing, while the bootstrapped parameters are
   expected not to change often (may be fair to say, as long as the MN
   remains powered up, but that may be debatable), what can be the possible
   gain of verifying the very first CoA of the MN alone? 
   
=> I've already answered about the "alone".

   Or, maybe I completely misunderstood your point :) 
   
=> or you've missed some messages.

Regards

Francis.Dupont@enst-bretagne.fr

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



From mip6-bounces@ietf.org Fri Oct 28 01:08:50 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EVMTy-0005yw-9c; Fri, 28 Oct 2005 01:08:50 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EVMTs-0005yc-UW
	for mip6@megatron.ietf.org; Fri, 28 Oct 2005 01:08:45 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA20345
	for <mip6@ietf.org>; Fri, 28 Oct 2005 01:08:28 -0400 (EDT)
Received: from email.seas.smu.edu ([129.119.113.35])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EVMhM-0008OM-6W
	for mip6@ietf.org; Fri, 28 Oct 2005 01:22:42 -0400
Received: from sic300dpc1 (sic-300d-pc1.seas.smu.edu [129.119.101.37])
	by email.engr.smu.edu (Postfix) with ESMTP id C53E826BBE
	for <mip6@ietf.org>; Fri, 28 Oct 2005 00:08:39 -0500 (CDT)
From: "Jahanzeb Faizan" <jfaizan@smu.edu>
To: <mip6@ietf.org>
Subject: [Mip6] Reliability and Load Balancing in Mobile IPv6---work published
	in IEEE conferences
Date: Fri, 28 Oct 2005 00:08:39 -0500
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Thread-Index: AcXbfaiH41kD9Ia5RV6XFwH3h3PATg==
Message-Id: <20051028050839.C53E826BBE@email.engr.smu.edu>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: a8041eca2a724d631b098c15e9048ce9
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-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="===============1637084929=="
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1637084929==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0036_01C5DB53.BFD80120"

This is a multi-part message in MIME format.

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

 

For those of you working on MIP6 reliability and load balancing issues, our
recently published IEEE papers would be useful. These papers are the
extensions of our preliminary IETF drafts on reliability and load balancing
in MIP6. 

1.      J. Faizan, H. El-Rewini, and M. Khalil, "VHARP: Virtual Home Agent
Reliability Protocol for Mobile IPv6 based Networks," in Proc. IEEE Int.
Conf. Wireless Networks, Communications, and Mobile Computing, Hawaii, June
13-16, 2005. 

2.      J. Faizan, H. El-Rewini, and M. Khalil, "Efficient Dynamic Load
Balancing for Multiple Home Agents in Mobile IPv6 based Networks," in Proc.
IEEE Int. Conf. on Pervasive Services 2005, Santorini, Greece, July 11-14,
2005

You can download these papers from our PDA Mobile Lab's web site at
http://engr.smu.edu/~rewini/lab.html
<https://webmail.smu.edu/exchweb/bin/redir.asp?URL=http://engr.smu.edu/~rewi
ni/lab.html> 

 

Thanks

 

Jahanzeb Faizan

 


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

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

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"State"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"place"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:1563371236;
	mso-list-template-ids:1138380558;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

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

<div class=3DSection1>

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

<p class=3DMsoNormal><font size=3D2 face=3D"Times New Roman"><span =
style=3D'font-size:
10.0pt'>For those of you working on&nbsp;MIP6 reliability and load =
balancing
issues,&nbsp;our recently&nbsp;published IEEE papers would be useful. =
These
papers are the extensions of our preliminary IETF drafts on reliability =
and
load balancing in MIP6.</span></font>&nbsp;<o:p></o:p></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
margin-left:35.7pt;text-indent:-17.85pt;mso-list:l0 level1 lfo1'><![if =
!supportLists]><font
size=3D3 face=3D"Times New Roman"><span style=3D'font-size:12.0pt'><span
style=3D'mso-list:Ignore'>1.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></font></span></span></font><![endif]><font
size=3D2><span style=3D'font-size:10.0pt'>J. Faizan, H. El-Rewini, and =
M. Khalil, <strong><b><font
face=3D"Times New Roman">&quot;VHARP: Virtual Home Agent Reliability =
Protocol for
Mobile IPv6 based Networks,&quot;</font></b></strong> in Proc. IEEE Int. =
Conf.
Wireless Networks, Communications, and Mobile Computing, <st1:place =
w:st=3D"on"><st1:State
 w:st=3D"on">Hawaii</st1:State></st1:place>, June 13-16, =
2005.&nbsp;</span></font><o:p></o:p></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
margin-left:35.7pt;text-indent:-17.85pt;mso-list:l0 level1 lfo1'><![if =
!supportLists]><font
size=3D3 face=3D"Times New Roman"><span style=3D'font-size:12.0pt'><span
style=3D'mso-list:Ignore'>2.<font size=3D1 face=3D"Times New =
Roman"><span
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></font></span></span></font><![endif]><font
size=3D2><span style=3D'font-size:10.0pt'>J. Faizan, H. El-Rewini, and =
M. Khalil, <strong><b><font
face=3D"Times New Roman">&quot;Efficient Dynamic Load Balancing for =
Multiple Home
Agents in Mobile IPv6 based Networks,&quot;</font></b></strong> in Proc. =
IEEE
Int. Conf. on Pervasive Services 2005, Santorini, Greece, July 11-14, =
2005</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 face=3D"Times New Roman"><span =
style=3D'font-size:
10.0pt'>You can download these papers from our PDA Mobile Lab's web site =
at <a
href=3D"https://webmail.smu.edu/exchweb/bin/redir.asp?URL=3Dhttp://engr.s=
mu.edu/~rewini/lab.html"
target=3D"_blank">http://engr.smu.edu/~rewini/lab.html</a></span></font><=
o:p></o:p></p>

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

<p class=3DMsoNormal><font size=3D2 face=3D"Times New Roman"><span =
style=3D'font-size:
10.0pt'>Thanks</span></font><o:p></o:p></p>

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

<p class=3DMsoNormal><font size=3D2 face=3D"Times New Roman"><span =
style=3D'font-size:
10.0pt'>Jahanzeb Faizan</span></font><o:p></o:p></p>

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

</div>

</body>

</html>

------=_NextPart_000_0036_01C5DB53.BFD80120--



--===============1637084929==
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

--===============1637084929==--





From mip6-bounces@ietf.org Fri Oct 28 07:38:35 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EVSZ9-0006yN-Hj; Fri, 28 Oct 2005 07:38:35 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EVSZ8-0006xj-0I
	for mip6@megatron.ietf.org; Fri, 28 Oct 2005 07:38:34 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA09106
	for <mip6@ietf.org>; Fri, 28 Oct 2005 07:38:16 -0400 (EDT)
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EVSme-0002WT-TX
	for mip6@ietf.org; Fri, 28 Oct 2005 07:52:35 -0400
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id 7F41E89884;
	Fri, 28 Oct 2005 14:38:13 +0300 (EEST)
Message-ID: <43620DAE.1080905@kolumbus.fi>
Date: Fri, 28 Oct 2005 14:38:22 +0300
From: Jari Arkko <jari.arkko@kolumbus.fi>
User-Agent: Mozilla Thunderbird 1.0 (X11/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
Subject: Re: CoA and AAA (was Re: [Mip6] General comments/questions on
	MIPv6bootstrapping)
References: <200510271604.j9RG4IVa022039@givry.rennes.enst-bretagne.fr>
In-Reply-To: <200510271604.j9RG4IVa022039@givry.rennes.enst-bretagne.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Content-Transfer-Encoding: 7bit
Cc: mip6@ietf.org, Vijay Devarapalli <vijayd@iprg.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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

I have now read some more messages - not sure
if I read all of them.

But I still don't understand why this would be
useful. It seems clear that we could only do it
for the first care-of address, because it makes
no sense to put bootstrapping in the critical
path.

Perhaps we just attempt to provide additional
security (and I agree that in the integrated
scenario we know we have AAA between home
agent and access network). The question, though,
is why. It seems that if we need additional
security, then on subsequent movements we'd
have to do something different.

Or perhaps we attempt to design something
that works with IKEv1 main mode and shared
secrets. Not sure if I have seen all the details,
because recognition of a peer is not about
coa-verification as much as it is about having
an index from addresses to shared secrets.
Also, if vendors have not implemented
IKEv2, what makes us think that if we specify
a new solution that they will implement that
new solution either?

--Jari


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



From mip6-bounces@ietf.org Fri Oct 28 08:52:08 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EVTiK-0004mx-Mr; Fri, 28 Oct 2005 08:52:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EVTiF-0004lS-UB
	for mip6@megatron.ietf.org; Fri, 28 Oct 2005 08:52:03 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA12285
	for <mip6@ietf.org>; Fri, 28 Oct 2005 08:51:45 -0400 (EDT)
Received: from smtp10.clb.oleane.net ([213.56.31.32])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EVTvl-0004QG-MH
	for mip6@ietf.org; Fri, 28 Oct 2005 09:06:04 -0400
Received: from Pavillonquatre ([194.3.133.88]) (authenticated)
	by smtp10.clb.oleane.net with ESMTP id j9SCpXOv014656
	for <mip6@ietf.org>; Fri, 28 Oct 2005 14:51:37 +0200
Message-Id: <200510281251.j9SCpXOv014656@smtp10.clb.oleane.net>
From: "Chantal Ladouce" <chantal.ladouce@upperside.fr>
To: <mip6@ietf.org>
Date: Fri, 28 Oct 2005 14:51:26 +0200
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
Thread-Index: AcXbvk64vFErEpqdQBKWFfC7ksUVYA==
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Spam-Score: 0.1 (/)
X-Scan-Signature: f49c97ce49302a02285a2d36a99eef8c
Subject: [Mip6] WiMAX Summit 2006 - Paris - France
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1827072795=="
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1827072795==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0169_01C5DBCF.12E15E40"

This is a multi-part message in MIME format.

------=_NextPart_000_0169_01C5DBCF.12E15E40
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit

The third edition of the WiMAX Summit 2006, the most important European
event, will be held on February 21 to 24 at the Sofitel Bercy Hotel in
Paris. 

The conference will largely be devoted to case studies presented by both
incumbent and new entrant operators who have set up WiMAX infrastructures.

 

All details at:

 <http://www.upperside.fr/wimax2006/wimax2006intro.htm>
http://www.upperside.fr/wimax2006/wimax2006intro.htm

 


------=_NextPart_000_0169_01C5DBCF.12E15E40
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

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

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

</head>

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

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
10.0pt;font-family:Arial'>The third edition of the&nbsp;<strong><b><font
face=3DArial><span style=3D'font-family:Arial'>WiMAX Summit =
2006</span></font></b></strong>,
the most important European event,&nbsp;will be held on <strong><b><font
face=3DArial><span style=3D'font-family:Arial'>February 21 to =
24</span></font></b></strong>
at the Sofitel Bercy Hotel in <st1:place w:st=3D"on"><st1:City =
w:st=3D"on">Paris</st1:City></st1:place>.
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
10.0pt;font-family:Arial'>The conference will largely be devoted to case
studies presented by both incumbent and new entrant operators who have =
set up
WiMAX infrastructures.<o:p></o:p></span></font></p>

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

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

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

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

</div>

</body>

</html>

------=_NextPart_000_0169_01C5DBCF.12E15E40--



--===============1827072795==
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

--===============1827072795==--





From mip6-bounces@ietf.org Fri Oct 28 12:20:19 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EVWsI-00010y-9P; Fri, 28 Oct 2005 12:14:38 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EVWsG-00010f-MG
	for mip6@megatron.ietf.org; Fri, 28 Oct 2005 12:14:36 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26860
	for <mip6@ietf.org>; Fri, 28 Oct 2005 12:14:19 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EVX5p-0002Es-Ip
	for mip6@ietf.org; Fri, 28 Oct 2005 12:28:40 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr
	[193.52.74.194])
	by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with
	ESMTP id j9SGDUt14651; Fri, 28 Oct 2005 18:13: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
	j9SGDQ2m027292; Fri, 28 Oct 2005 18:13:26 +0200 (CEST)
	(envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200510281613.j9SGDQ2m027292@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Jari Arkko <jari.arkko@kolumbus.fi>
Subject: Re: CoA and AAA (was Re: [Mip6] General comments/questions on
	MIPv6bootstrapping) 
In-reply-to: Your message of Fri, 28 Oct 2005 14:38:22 +0300.
	<43620DAE.1080905@kolumbus.fi> 
Date: Fri, 28 Oct 2005 18:13:26 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
Cc: mip6@ietf.org, Vijay Devarapalli <vijayd@iprg.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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   But I still don't understand why this would be
   useful.

=> at least nobody argues it is necessary.

   It seems clear that we could only do it
   for the first care-of address, because it makes
   no sense to put bootstrapping in the critical
   path.
   
=> this is not fully true: if the mobile stays in the same
AAA domain, i.e., if the integrated scenario still applies,
new CoAs can be authenticated.

   Perhaps we just attempt to provide additional
   security

=> this is the main reason.

   (and I agree that in the integrated
   scenario we know we have AAA between home
   agent and access network).

=> the integrated scenario == applicable context.

   The question, though,
   is why. It seems that if we need additional
   security, then on subsequent movements we'd
   have to do something different.
   
=> as I've just explained, when the integrated scenario
still applies we still have the additional security
on subsequent movements.

   Or perhaps we attempt to design something
   that works with IKEv1 main mode and shared
   secrets.

=> this is a second reason. IMHO it is a good one
but IKEv1 is not considered in bootstrapping scenarios
because IKEv2 is far better. So I explicitely don't
want to use publicly this argument.

   Not sure if I have seen all the details,
   because recognition of a peer is not about
   coa-verification as much as it is about having
   an index from addresses to shared secrets.

=> pre-shared key authentication is based on the fact
the right index is used to get the key.

   Also, if vendors have not implemented
   IKEv2, what makes us think that if we specify
   a new solution that they will implement that
   new solution either?
   
=> if you argue we should simply implement and use IKEv2
I can't say something else (:-)!

Regards

Francis.Dupont@enst-bretagne.fr

PS: if we speak in terms of requiments, clearly it is not a MUST,
it can be a MAY and for a SHOULD this is in the hands of operators,
i.e., do they care or not. Operators I know seem to have no clear
opinion about this.

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



From mip6-bounces@ietf.org Fri Oct 28 13:36:51 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EVY9r-0000qq-1B; Fri, 28 Oct 2005 13:36:51 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EVY9m-0000qi-8S
	for mip6@megatron.ietf.org; Fri, 28 Oct 2005 13:36:46 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00041
	for <mip6@ietf.org>; Fri, 28 Oct 2005 13:36:29 -0400 (EDT)
Received: from mail.flarion.com ([63.103.94.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EVYNO-0004Xw-EA
	for mip6@ietf.org; Fri, 28 Oct 2005 13:50:50 -0400
Received: from ftmailserver.flariontech.com ([10.10.1.140]) by
	mail.flarion.com with Microsoft SMTPSVC(5.0.2195.6713);
	Fri, 28 Oct 2005 13:36:36 -0400
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] comment on draft-ietf-mip6-nemo-v4traversal-00
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
Date: Fri, 28 Oct 2005 13:36:34 -0400
Message-ID: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCDD0@ftmailserver.flariontech.com>
Thread-Topic: [Mip6] comment on draft-ietf-mip6-nemo-v4traversal-00
Thread-Index: AcXa78DttNb/w4SSTxChf/8odQP2qwA9eWUA
From: "Soliman, Hesham" <H.Soliman@flarion.com>
To: "Alexandru Petrescu" <alexandru.petrescu@motorola.com>
X-OriginalArrivalTime: 28 Oct 2005 17:36:37.0009 (UTC)
	FILETIME=[259F6010:01C5DBE6]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Content-Transfer-Encoding: quoted-printable
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org



 >=20
 > Right, and when MIP4 is used with NAI (RFC specifies that)=20
 > and ppp then
 > a stable IPv4 address is provided.  DSMIPv6 doesn't=20
 > currently have that.

=3D> No that's wrong. DSMIPv6 provides static or dynamic IPv4
home addresses based on the request in the BU. Instead of=20
the NAI, the IPv6 home address is used. A NAI could also
be used if we had a standard NAI extension in MIPv6.

 > > MIPv4 is not used in this solution.
 >=20
 > And because of the reasons above, a DSMIPv6 MN that needs to=20
 > detect its
 > movement on a v4-only access network will still need a MIP4=20
 > stack. =20

=3D> No. Movement detection is done based on Router Discovery. That's
what MIPv4 assumes...It only extends RFC 1256. You don't need that
extension if you're not using MIPv4, you detect movement based
on RFC 1256. That's something we can detail in the draft.

   In
 > addition to the reasons above, the MIP4 stack is also needed=20
 > on the HA
 > to perform proxy ARP for the IPv4 Home Address (a thing that DSMIPv6
 > doesn't).

=3D> This has zero relationship with MIPv4. ARP is not a function
of MIPv4.

Hesham


 >=20
 > Alex
 >=20
 >=20

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D
This email may contain confidential and privileged material for the sole =
use
 of the intended recipient.  Any review or distribution by others is =
strictly
 prohibited.  If you are not the intended recipient please contact the =
sender
 and delete all copies.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D


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



From mip6-bounces@ietf.org Fri Oct 28 14:02:59 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EVYZ9-0003f3-2b; Fri, 28 Oct 2005 14:02:59 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EVYZ7-0003ed-IP
	for mip6@megatron.ietf.org; Fri, 28 Oct 2005 14:02:57 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01178
	for <mip6@ietf.org>; Fri, 28 Oct 2005 14:02:39 -0400 (EDT)
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EVYmi-0005BO-Dh
	for mip6@ietf.org; Fri, 28 Oct 2005 14:17:01 -0400
Received: from il06exr02.mot.com (il06exr02.mot.com [129.188.137.132])
	by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id j9SIEeec000087;
	Fri, 28 Oct 2005 11:14:40 -0700 (MST)
Received: from [144.189.72.33] (mvp-144-189-72-33.corp.mot.com [144.189.72.33])
	by il06exr02.mot.com (8.13.1/8.13.0) with ESMTP id j9SIBK6D016341;
	Fri, 28 Oct 2005 13:11:21 -0500 (CDT)
Message-ID: <436267BB.2080305@motorola.com>
Date: Fri, 28 Oct 2005 20:02:35 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040803
X-Accept-Language: rs1_22c0391591b, rs2_349b8913e3d, rs3_148101cb63
MIME-Version: 1.0
To: "Soliman, Hesham" <H.Soliman@flarion.com>
Subject: Re: [Mip6] comment on draft-ietf-mip6-nemo-v4traversal-00
References: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCDD0@ftmailserver.flariontech.com>
In-Reply-To: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCDD0@ftmailserver.flariontech.com>
X-Enigmail-Version: 0.91.0.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Content-Transfer-Encoding: 7bit
Cc: 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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Soliman, Hesham wrote:
>> Right, and when MIP4 is used with NAI (RFC specifies that) and ppp
>>  then a stable IPv4 address is provided.  DSMIPv6 doesn't currently
>>  have that.
> 
> => No that's wrong. DSMIPv6 provides static or dynamic IPv4 home 
> addresses based on the request in the BU. Instead of the NAI, the 
> IPv6 home address is used. A NAI could also be used if we had a 
> standard NAI extension in MIPv6.

Ok.

NAI is implemented and deployed in some v4-only access networks, and
MIP4 uses it.  If MIP4 is not on the terminal then that would not be
used, right?

>>> MIPv4 is not used in this solution.
>> 
>> And because of the reasons above, a DSMIPv6 MN that needs to detect
>>  its movement on a v4-only access network will still need a MIP4 
>> stack.
> 
> => No. Movement detection is done based on Router Discovery. That's 
> what MIPv4 assumes...It only extends RFC 1256. You don't need that 
> extension if you're not using MIPv4, you detect movement based on RFC
>  1256. That's something we can detail in the draft.

Ok, so DSMIPv6 would be extended with Router Discovery.

>> In addition to the reasons above, the MIP4 stack is also needed on 
>> the HA to perform proxy ARP for the IPv4 Home Address (a thing that
>>  DSMIPv6 doesn't).
> 
> => This has zero relationship with MIPv4. ARP is not a function of 
> MIPv4.

Ok, so proxy ARP for the IPv4 Home Address would be something that
should be included in DSMIPv6.

Because if any of these features for permanent IPv4 Home Addresses are
not included, a user may be found in the situation to run both MIP4 and
DSMIPv6 in order to have permanent IPv4 Home Addresses, no?

This is something that DSMIPv6 stated in the Problem Statement: running
both MIP4 and MIP6 is inefficient.  Is running both DSMIP6 and MIP4 more
efficient?

Alternatively, if the goals of DSMIPv6 were not to address a problem
that does not quite exist, it would easily co-exist with MIP4.

Alex

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



From mip6-bounces@ietf.org Fri Oct 28 14:17:10 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EVYms-0001LW-2t; Fri, 28 Oct 2005 14:17:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EVYmr-0001LR-5k
	for mip6@megatron.ietf.org; Fri, 28 Oct 2005 14:17:09 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01672
	for <mip6@ietf.org>; Fri, 28 Oct 2005 14:16:51 -0400 (EDT)
Received: from mail.flarion.com ([63.103.94.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EVZ0S-0005VH-BB
	for mip6@ietf.org; Fri, 28 Oct 2005 14:31:13 -0400
Received: from ftmailserver.flariontech.com ([10.10.1.140]) by
	mail.flarion.com with Microsoft SMTPSVC(5.0.2195.6713);
	Fri, 28 Oct 2005 14:16:57 -0400
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] comment on draft-ietf-mip6-nemo-v4traversal-00
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
Date: Fri, 28 Oct 2005 14:16:54 -0400
Message-ID: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCDD3@ftmailserver.flariontech.com>
Thread-Topic: [Mip6] comment on draft-ietf-mip6-nemo-v4traversal-00
Thread-Index: AcXb6cvk3jA/AokAT0aJagbc0IQsRQAAWtfQ
From: "Soliman, Hesham" <H.Soliman@flarion.com>
To: "Alexandru Petrescu" <alexandru.petrescu@motorola.com>
X-OriginalArrivalTime: 28 Oct 2005 18:16:57.0571 (UTC)
	FILETIME=[C863D330:01C5DBEB]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Content-Transfer-Encoding: quoted-printable
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org


 > > =3D> No that's wrong. DSMIPv6 provides static or dynamic IPv4 home=20
 > > addresses based on the request in the BU. Instead of the NAI, the=20
 > > IPv6 home address is used. A NAI could also be used if we had a=20
 > > standard NAI extension in MIPv6.
 >=20
 > Ok.
 >=20
 > NAI is implemented and deployed in some v4-only access networks, and
 > MIP4 uses it.  If MIP4 is not on the terminal then that would not be
 > used, right?

=3D> ?? i don't understand how this is relevant to DSMIPv6.=20
I said "A NAI could also be used if we had a=20
standard NAI extension in MIPv6."

 > > =3D> No. Movement detection is done based on Router=20
 > Discovery. That's=20
 > > what MIPv4 assumes...It only extends RFC 1256. You don't need that=20
 > > extension if you're not using MIPv4, you detect movement=20
 > based on RFC
 > >  1256. That's something we can detail in the draft.
 >=20
 > Ok, so DSMIPv6 would be extended with Router Discovery.

=3D> No, router discovery is an IPv4 feature. DSMIPv6 could monitor
changes in RAs to detect movement.

 > Ok, so proxy ARP for the IPv4 Home Address would be something that
 > should be included in DSMIPv6.

=3D> Yes.

 >=20
 > Because if any of these features for permanent IPv4 Home=20
 > Addresses are
 > not included, a user may be found in the situation to run=20
 > both MIP4 and
 > DSMIPv6 in order to have permanent IPv4 Home Addresses, no?

=3D> No. I don't understand how you came to that conclusion.

Hesham

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D
This email may contain confidential and privileged material for the sole =
use
 of the intended recipient.  Any review or distribution by others is =
strictly
 prohibited.  If you are not the intended recipient please contact the =
sender
 and delete all copies.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D


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



From mip6-bounces@ietf.org Fri Oct 28 15:24:16 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EVZpo-0004hE-Kw; Fri, 28 Oct 2005 15:24:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EVZpm-0004h8-Ot
	for mip6@megatron.ietf.org; Fri, 28 Oct 2005 15:24:14 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04141
	for <mip6@ietf.org>; Fri, 28 Oct 2005 15:23:56 -0400 (EDT)
Received: from av9-2-sn2.hy.skanova.net ([81.228.8.180])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EVa3N-00070T-IX
	for mip6@ietf.org; Fri, 28 Oct 2005 15:38:19 -0400
Received: by av9-2-sn2.hy.skanova.net (Postfix, from userid 502)
	id 2D8B9381A0; Fri, 28 Oct 2005 21:23:58 +0200 (CEST)
Received: from smtp4-1-sn2.hy.skanova.net (smtp4-1-sn2.hy.skanova.net
	[81.228.8.92]) by av9-2-sn2.hy.skanova.net (Postfix) with ESMTP
	id 558593817C; Fri, 28 Oct 2005 21:23:57 +0200 (CEST)
Received: from shiraz.levkowetz.com (81-224-201-50-no45.tbcn.telia.com
	[81.224.201.50])
	by smtp4-1-sn2.hy.skanova.net (Postfix) with ESMTP id F36E537E43;
	Fri, 28 Oct 2005 21:23:56 +0200 (CEST)
Received: from localhost ([127.0.0.1])
	by shiraz.levkowetz.com with esmtp (Exim 4.54)
	id 1EVZpT-0007HD-NK; Fri, 28 Oct 2005 21:23:55 +0200
Message-ID: <43627ACB.9050806@levkowetz.com>
Date: Fri, 28 Oct 2005 21:23:55 +0200
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Mozilla Thunderbird 1.0.7 (Macintosh/20050923)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Soliman, Hesham" <H.Soliman@flarion.com>
Subject: Re: [Mip6] comment on draft-ietf-mip6-nemo-v4traversal-00
References: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCDD3@ftmailserver.flariontech.com>
In-Reply-To: <A11736FE943F1A408F8BBB1B9F5FE8AD01CBCDD3@ftmailserver.flariontech.com>
X-Enigmail-Version: 0.93.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: 7655788c23eb79e336f5f8ba8bce7906
Content-Transfer-Encoding: 7bit
Cc: 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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org



on 2005-10-28 20:16 Soliman, Hesham said the following:

>> > => No. Movement detection is done based on Router 
>> Discovery. That's 
>> > what MIPv4 assumes...It only extends RFC 1256. You don't need that 
>> > extension if you're not using MIPv4, you detect movement 
>> based on RFC
>> >  1256. That's something we can detail in the draft.
>> 
>> Ok, so DSMIPv6 would be extended with Router Discovery.
> 
> => No, router discovery is an IPv4 feature. DSMIPv6 could monitor
> changes in RAs to detect movement.

Right.

The most appropriate current reference for detecting changes in
attachment to IPv4 only networks would probably be the IPv4 DNA
document, currently draft-ietf-dhc-dna-ipv4-17.txt.

	Henrik

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



From mip6-bounces@ietf.org Mon Oct 31 11:05:06 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EWc9h-0007k8-VD; Mon, 31 Oct 2005 11:05:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EWc9f-0007j3-Gc
	for mip6@megatron.ietf.org; Mon, 31 Oct 2005 11:05:03 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17055
	for <mip6@ietf.org>; Mon, 31 Oct 2005 11:04:41 -0500 (EST)
Received: from mx0.starentnetworks.com ([12.38.223.203])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EWcNo-00033Y-Uz
	for mip6@ietf.org; Mon, 31 Oct 2005 11:19:42 -0500
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mx0.starentnetworks.com (Postfix) with ESMTP id 776F390011;
	Mon, 31 Oct 2005 11:04:44 -0500 (EST)
Received: from mx0.starentnetworks.com ([127.0.0.1])
	by localhost (mx0.starentnetworks.com [127.0.0.1]) (amavisd-new,
	port 10024)
	with ESMTP id 02535-06; Mon, 31 Oct 2005 11:04:42 -0500 (EST)
Received: from ames.starentnetworks.com (ames.starentnetworks.com
	[12.33.235.15]) by mx0.starentnetworks.com (Postfix) with ESMTP;
	Mon, 31 Oct 2005 11:04:42 -0500 (EST)
X-MessageTextProcessor: DisclaimIt (2.50.252) [Starent Networks Corp.]
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Importance: normal
Priority: normal
Content-Transfer-Encoding: quoted-printable
Date: Mon, 31 Oct 2005 11:04:42 -0500
Message-ID: <8A16DAD84432534FBFC19FD92B50512F035D92DA@ames.starentnetworks.com>
Thread-Topic: draft-chowdhury-mip6-radius-00.txt
thread-index: AcXeNMzLoxeCmAeoQnG0kx+3vmu/yw==
From: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
To: <mip6@ietf.org>
X-Virus-Scanned: amavisd-new 2.2.1 (20041222) at mx0.starentnetworks.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Content-Transfer-Encoding: quoted-printable
Cc: "Tschofenig, Hannes" <hannes.tschofenig@siemens.com>,
	avi@bridgewatersystems.com
Subject: [Mip6] draft-chowdhury-mip6-radius-00.txt
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Hi all,

We have submitted a draft on RADIUS-MIP6 interactions. A similar I-D was
submitted sometime ago, but it expired. Here is the abstract:

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

   A Mobile IPv6 node requires a home agent address, a home address, and
   IPsec security association with its home agent before it can start
   utilizing Mobile IPv6 service.  RFC 3775 requires that some or all of
   these parameters are statically configured.  Ongoing work aims to
   make this information dynamically available to the mobile node.  An
   important aspect of the Mobile IPv6 bootstrapping solution is to
   support interworking with existing authentication, authorization and
   accounting infrastructure.  This document defines the new attributes
   to facilitate Mobile IPv6 bootstrapping via a RADIUS infrastructure.
   This information exchange may take place as part of the initial
   network access authentication procedure or as part of a separate
   protocol exchange between the mobile node, the home agent and the AAA
   infrastructure.

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

http://www.ietf.org/internet-drafts/draft-chowdhury-mip6-radius-00.txt


Your comments are welcome.

-Kuntal



"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 Mon Oct 31 14:33:23 2005
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EWfPH-0003eO-5V; Mon, 31 Oct 2005 14:33:23 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EWfPF-0003df-Hh
	for mip6@megatron.ietf.org; Mon, 31 Oct 2005 14:33:21 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02267
	for <mip6@ietf.org>; Mon, 31 Oct 2005 14:32:57 -0500 (EST)
Received: from key1.docomolabs-usa.com
	([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EWfdP-0001Ls-1a
	for mip6@ietf.org; Mon, 31 Oct 2005 14:48:00 -0500
Message-ID: <0fd101c5de51$e501e0f0$226115ac@dcml.docomolabsusa.com>
From: "James Kempf" <Kempf@docomolabs-usa.com>
To: "Francis Dupont" <Francis.Dupont@enst-bretagne.fr>, <mip6@ietf.org>
References: <200510251215.j9PCFTFu096498@givry.rennes.enst-bretagne.fr>
Subject: Re: [Mip6] load balancing and HA (re-)assignment
Date: Mon, 31 Oct 2005 11:32:56 -0800
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="Windows-1252";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Content-Transfer-Encoding: 7bit
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>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

Francis,

There's an item on the Vancouver meeting agenda to talk about HA switch. At 
the end of the discussion, we can do a straw poll to see whether there's 
interest in making it a WG document.

          jak

----- Original Message ----- 
From: "Francis Dupont" <Francis.Dupont@enst-bretagne.fr>
To: <mip6@ietf.org>
Sent: Tuesday, October 25, 2005 4:15 AM
Subject: [Mip6] load balancing and HA (re-)assignment


> If HA assignment can help load balancing by selecting a less loaded HA,
> it works only in the bootstrapping phase and as the load is not
> proportional to the number of served MN (i.e., the load doesn't come only
> from background traffic) IMHO it is more important to be able to
> move some MNs from an overloaded HA, i.e., load balancing is a good
> reason to ask for HA re-assignement but not for HA assignment.
>
> So I believe we should work on HA-HA and HA-switch documents and
> as the HA-switch is more mature make it a WG item and submit it
> to IESG review ASAP?
>
> Regards
>
> Francis.Dupont@enst-bretagne.fr
>
> _______________________________________________
> 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



