From mip6-bounces@ietf.org Tue Aug 01 11:07:40 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G7vqC-0005yF-Mv; Tue, 01 Aug 2006 11:07:28 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G7vqB-0005yA-Vo
	for mip6@ietf.org; Tue, 01 Aug 2006 11:07:27 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G7vqA-0000PR-Hd
	for mip6@ietf.org; Tue, 01 Aug 2006 11:07:27 -0400
Received: from ams-core-1.cisco.com ([144.254.224.150])
	by ams-iport-1.cisco.com with ESMTP; 01 Aug 2006 17:07:27 +0200
Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com
	[144.254.231.71])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k71F7PUO002719; 
	Tue, 1 Aug 2006 17:07:25 +0200 (MEST)
Received: from xmb-ams-337.cisco.com ([144.254.231.82]) by
	xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.0); 
	Tue, 1 Aug 2006 17:07:25 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] Re: topology about v4-v6 migration
Date: Tue, 1 Aug 2006 17:07:21 +0200
Message-ID: <7892795E1A87F04CADFCCF41FADD00FC0280AFD3@xmb-ams-337.emea.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] Re: topology about v4-v6 migration
Thread-Index: AcanbT+JverwJBorSUaQf/SSJAnGigOC/D+w
From: "Pascal Thubert \(pthubert\)" <pthubert@cisco.com>
To: "Henrik Levkowetz" <henrik@levkowetz.com>,
	"Alexandru Petrescu" <alexandru.petrescu@motorola.com>
X-OriginalArrivalTime: 01 Aug 2006 15:07:25.0459 (UTC)
	FILETIME=[3281FE30:01C6B57C]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1676547e4f33b5e63227e9c02bd359e3
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi Alex:

This was a subject of disagreement within the MIPTRANS ML; as far as I
know, the outcome was to EXCLUDE SUPPORT for your scenario. I remember
Jim Bound complained about that, saying it was a very important scenario
for IPv6 dominant world. Note that the GW might be placed at the egress
of a legacy IPv4 only network as opposed to the ingress of a home
network.

There are basically 2 ways of supporting it:

1) native: MIP6-like over IPv4 between MN and GW. GW decapsulates and HA
receives MIP6 native.

2) tunnel: MIPTRANS over IPv4 between MN and GW. GW encapsulates over
IPv6 to HA.=20


With MIPTRANS as of today, the latter, tunnel, is really the only
option. This forces the HA to keep an IPv4 address long after is placed
in an IPv6 only domain, and the GW-HA tunnel is set up manually.

OTOH, the Doors proposal includes a native solution, with the concept of
a gateway and an automatic tunneling mechanism, an hybrid between ISATAP
and 6to4: The GW decapsulates IPv4/UDP from the MN packet, and forwards
the inner IPv6 packet to the HA; the packet looks exactly like a
traditional MIP6/NEMO packet. The source address (CoA) contains the pair
of IPv4 addresses and ports necessary for the GW to encaps on the way
back. The GW is stateless, and owns the 6to4 based /48 from which are
derived all CoA of MN using that GW.=20

Pascal


>-----Original Message-----
>From: Henrik Levkowetz [mailto:henrik@levkowetz.com]
>Sent: Friday, July 14, 2006 7:27 PM
>To: Alexandru Petrescu
>Cc: Mobile IPv6 Mailing List
>Subject: [Mip6] Re: topology about v4-v6 migration
>
>Hi Alex,
>
>  Snipping some stuff, and responding inline:
>
>on 2006-07-14 12:29 Alexandru Petrescu said the following:
>...
>>> on 2006-07-13 18:01 Alexandru Petrescu said the following:
>>>> Hi Henrik, per your request on the scenario of IPv6-IPv4 deployment
>>>>  I mentioned today in the MIP6 WG meeting.  Below is the topology
>>>> I've had in mind:
>>>>
>>
>>    +--+
>>    |CN|
>>    +--+
>>     |
>>   ------------------
>> / IPv6-only        \____
>> \ "island" network /    |
>>   ------------------     |
>>                          |
>>                          |
>>                          |
>>   ----------------       |    +---+     -------------    +----------+
>> / IPv4-only      \__IPv4_____|GW |____/ IPv6-only   \___| HA       |
>> \ access network /  Internet +---+    \ home network/   | IPv6-only|
>>   ----------------                      -------------    +----------+
>>        .
>>        |
>>      +--+
>>      |MN|
>>      +--+
>>
>>
>>>> The MN is "owned" by an IPv6 HA deep in an IPv6-only network,
>>>> presumably some operator's network.  MN connects to another
>>>> operator's IPv4-only wireless access.  It needs to communicate with
>>>>  an IPv6-only CN, present on an IPv6-only "island" network.
>>>>
>>>> The IPv4-only access network, the IPv6-only home network and the
>>>> IPv6-only "island" network are connected together on the IPv4
>>>> Internet
>
>...
>
>> I am not sure though how DS-MIPv6 current solution solves it.  The
doubt
>> I have is about the DS-MIPv6 tunnel MN-HA ending in HA's IPv4
address.
>> Is this so?
>
>More precise is to say that the HA has to be reachable through an
>IPv4 address somehow.  This could be an address on the GW which
>is forwarded to the HA through a tunnel, exactly as you mention
>next:
>
>> Also, maybe DS-MIPv6 assumes a form of IPv4-in-IPv6 encapsulation
>> between the GW (pictured) and the HA?
>>
>> We have both mentioned existing v4-v6 transitioning methods, no need
to
>> enhance them, just re-use them - ok.  But not sure between what and
>> what.  When I think re-using transitioning schemes is IPv6-in-IPv4
>> between GW and border on IPv6 Internet.  This is _not_ IPv4-in-IPv6
>> between GW and HA.  Do you assume this latter?
>
>Some kind of tunnelled forwarding between HA and the IPv4 address on
>the GW would be necessary, yes.  Exactly what is used is not
>important, as long as the HA is reachable through that IPv4 address
>and is aware that it has that IPv4 address.
>
>Regards,
>
>	Henrik
>
>_______________________________________________
>Mip6 mailing list
>Mip6@ietf.org
>https://www1.ietf.org/mailman/listinfo/mip6

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



From mip6-bounces@ietf.org Tue Aug 01 15:35:28 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G801U-0000Nc-I7; Tue, 01 Aug 2006 15:35:24 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G801U-0000NV-20
	for mip6@ietf.org; Tue, 01 Aug 2006 15:35:24 -0400
Received: from mgw-ext11.nokia.com ([131.228.20.170])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G801S-0007Lm-Ju
	for mip6@ietf.org; Tue, 01 Aug 2006 15:35:24 -0400
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143])
	by mgw-ext11.nokia.com (Switch-3.1.8/Switch-3.1.7) with ESMTP id
	k71IZLux013312 for <mip6@ietf.org>; Tue, 1 Aug 2006 21:35:22 +0300
Received: from daebh101.NOE.Nokia.com ([10.241.35.111]) by
	esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 1 Aug 2006 22:35:17 +0300
Received: from daebe101.NOE.Nokia.com ([10.241.35.113]) by
	daebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 1 Aug 2006 14:35:16 -0500
Received: from 172.19.244.182 ([172.19.244.182]) by daebe101.NOE.Nokia.com
	([10.241.35.113]) with Microsoft Exchange Server HTTP-DAV ; 
	Tue,  1 Aug 2006 19:35:18 +0000
User-Agent: Microsoft-Entourage/11.2.5.060620
Date: Tue, 01 Aug 2006 14:35:24 -0500
From: Basavaraj Patil <basavaraj.patil@nokia.com>
To: <mip6@ietf.org>
Message-ID: <C0F5172C.20530%basavaraj.patil@nokia.com>
Thread-Topic: Recommendation for bootstrapping using DHCPv6
Thread-Index: Aca1oaIQ4K1FzyGUEduPhAARJNUNiA==
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 01 Aug 2006 19:35:16.0388 (UTC)
	FILETIME=[9D872640:01C6B5A1]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Subject: [Mip6] Recommendation for bootstrapping using DHCPv6
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org


Alper/Kuntal et al,

I have reviewed the drafts:
1. Problem Statement for bootstrapping Mobile IPv6
   (draft-ietf-mip6-bootstrap-ps-05)
2. MIP6-bootstrapping via DHCPv6 for the Integrated Scenario
   (draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt)

and
3. DHCP Option for Home Information Discovery in MIPv6
   (draft-jang-mip6-hiopt-00.txt)

My conclusion from the review is that the integrated scenario
bootstrapping via DHCPv6 is covering the cases when DHCP is the
preferred method by MNs.

The WG I-D draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt in
sections 3.5 and 3.8 explain how DHCP would work. Having the options
specified in a stand-along document will not add much value. I am also
concerned about the fact in draft-jang which states that:
"
   The availability of the requested information depends on the DHCP
   server having prior knowledge or dynamically discovering it.  While
   the specific details are outside the scope of this document, use of
   static tables and AAA-assisted discovery are possible options
"

Another concern that I have w.r.t bootstrapping with DHCPv6 is that
instead of having DHCP provide the HoA or the HL prefix to the MS, it
is better to only provide the address of an HA (or list of HAs) and
let the MS send a BU with unspecified address and obtain an address
from the HA. This will simplify bootstrapping and also reduce the
interaction between DHCP and the HA from an address management
perspective. Hence you may want to reconsider the DHCP option which
carry the HL Prefix or the HoA for the MS.

I recommend that the DHCP option specified in draft-jang be
incorporated into the WG I-D and progressed on standards track. As a
result the WG will have a mechanism for bootstrapping MIP6 with DHCP
that also includes the DHCP options in a single I-D.

-Raj


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



From mip6-bounces@ietf.org Tue Aug 01 16:14:19 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G80d7-0000eL-8F; Tue, 01 Aug 2006 16:14:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G80d5-0000e7-HZ
	for mip6@ietf.org; Tue, 01 Aug 2006 16:14:15 -0400
Received: from mail.av.it.pt ([193.136.92.53] helo=av.it.pt)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G80d3-0002eA-6A
	for mip6@ietf.org; Tue, 01 Aug 2006 16:14:15 -0400
Received: from [192.168.0.251] (HELO mars.innerghost.net)
	by av.it.pt (CommuniGate Pro SMTP 5.0.9)
	with ESMTP id 5451717; Tue, 01 Aug 2006 21:14:12 +0100
Received: by mars.innerghost.net (Postfix, from userid 1000)
	id 7BC5B411C; Tue,  1 Aug 2006 21:14:11 +0100 (WEST)
Date: Tue, 1 Aug 2006 21:14:11 +0100
From: Hugo Santos <hsantos@av.it.pt>
To: Basavaraj Patil <basavaraj.patil@nokia.com>
Subject: Re: [Mip6] Recommendation for bootstrapping using DHCPv6
Message-ID: <20060801201411.GF8334@innerghost.net>
References: <C0F5172C.20530%basavaraj.patil@nokia.com>
Mime-Version: 1.0
In-Reply-To: <C0F5172C.20530%basavaraj.patil@nokia.com>
User-Agent: Mutt/1.5.6+20040907i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1320182532=="
Errors-To: mip6-bounces@ietf.org


--===============1320182532==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="/Q7FmPuhIbtiu4EM"
Content-Disposition: inline


--/Q7FmPuhIbtiu4EM
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Hi,

   I have one question regarding the following:

On Tue, Aug 01, 2006 at 02:35:24PM -0500, Basavaraj Patil wrote:
> Another concern that I have w.r.t bootstrapping with DHCPv6 is that
> instead of having DHCP provide the HoA or the HL prefix to the MS, it
> is better to only provide the address of an HA (or list of HAs) and
> let the MS send a BU with unspecified address and obtain an address
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

   RFC 3775 states that the home address specified in Binding Updates
 must be unicast routable, would this work with current Home Agents? By
 splitting assignment (DHCP) from mobility management (HA) we would
 allow for better upgrade paths. I do understand how your suggestion
 would reduce comunication between a DHCP server and the HA, but it
 seems that it reduces to something in the line of DHCP but using MH
 messages, which involves modifying the Home Agent vs. installing
 policies. Would a full IKE exchange be made with the HA before sending
 these address-obtaining BUs?

   Best regards,

      Hugo Santos

--/Q7FmPuhIbtiu4EM
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

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

iD8DBQFEz7YT7asb/itUNKwRAtR6AKCdEIoqJ21KHLhFSn9jqiod7J9VSgCfcLaj
gry4CgT3eQjpEkX1V1V+Yjc=
=j86T
-----END PGP SIGNATURE-----

--/Q7FmPuhIbtiu4EM--


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

--===============1320182532==--




From mip6-bounces@ietf.org Tue Aug 01 17:22:59 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G81hU-00046k-7v; Tue, 01 Aug 2006 17:22:52 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G81hS-0003zt-PX
	for mip6@ietf.org; Tue, 01 Aug 2006 17:22:50 -0400
Received: from mail1.azairenet.com ([66.92.223.4] helo=bart.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G81hQ-0001Tj-7X
	for mip6@ietf.org; Tue, 01 Aug 2006 17:22:50 -0400
Received: from [10.1.201.0] ([10.1.201.0]) by bart.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Tue, 1 Aug 2006 14:22:43 -0700
Message-ID: <44CFC5AE.3020504@azairenet.com>
Date: Tue, 01 Aug 2006 14:20:46 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.2 (X11/20060516)
MIME-Version: 1.0
To: Hugo Santos <hsantos@av.it.pt>
Subject: Re: [Mip6] Recommendation for bootstrapping using DHCPv6
References: <C0F5172C.20530%basavaraj.patil@nokia.com>
	<20060801201411.GF8334@innerghost.net>
In-Reply-To: <20060801201411.GF8334@innerghost.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 01 Aug 2006 21:22:43.0886 (UTC)
	FILETIME=[A08944E0:01C6B5B0]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Cc: mip6@ietf.org, Basavaraj Patil <basavaraj.patil@nokia.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hugo Santos wrote:
> Hi,
> 
>    I have one question regarding the following:
> 
> On Tue, Aug 01, 2006 at 02:35:24PM -0500, Basavaraj Patil wrote:
>> Another concern that I have w.r.t bootstrapping with DHCPv6 is that
>> instead of having DHCP provide the HoA or the HL prefix to the MS, it
>> is better to only provide the address of an HA (or list of HAs) and
>> let the MS send a BU with unspecified address and obtain an address
>              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> 
>    RFC 3775 states that the home address specified in Binding Updates
>  must be unicast routable, would this work with current Home Agents? 

bootstrapping specifications can "update" RFC 3775. RFC 3775
assumes the mobile node has a long lived home address that
does not change. RFC 3775 needs to be updated anyway.

> By
>  splitting assignment (DHCP) from mobility management (HA) we would
>  allow for better upgrade paths. I do understand how your suggestion
>  would reduce comunication between a DHCP server and the HA, but it
>  seems that it reduces to something in the line of DHCP but using MH
>  messages, which involves modifying the Home Agent vs. installing
>  policies. Would a full IKE exchange be made with the HA before sending
>  these address-obtaining BUs?

if IKEv2 is being used to setup security associations between
the MN and the HA, then the mechanism described in section 5.3
of 
http://www.ietf.org/internet-drafts/draft-ietf-mip6-bootstrapping-split-02.txt
would apply. a BU with unspecified home address will not be
sent.

if RFC 4285 is used instead of IKEv2 and IPsec, then a BU with
a 0::0 home address and the MN-ID option (RFC 4283) can be
sent to obtain a home address from the home agent.

Vijay

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



From mip6-bounces@ietf.org Tue Aug 01 17:53:55 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G82BW-0007MJ-IR; Tue, 01 Aug 2006 17:53:54 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G82BV-0007M0-Q5
	for mip6@ietf.org; Tue, 01 Aug 2006 17:53:53 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G80zV-0004Hi-Ep
	for mip6@ietf.org; Tue, 01 Aug 2006 16:37:25 -0400
Received: from atlrel6.hp.com ([156.153.255.205])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1G80km-0006gH-3v
	for mip6@ietf.org; Tue, 01 Aug 2006 16:22:14 -0400
Received: from smtp1.fc.hp.com (smtp1.fc.hp.com [15.15.136.127])
	by atlrel6.hp.com (Postfix) with ESMTP id 6964A36178;
	Tue,  1 Aug 2006 16:22:09 -0400 (EDT)
Received: from [16.116.114.13] (spaceshipone.zko.hp.com [16.116.114.13])
	by smtp1.fc.hp.com (Postfix) with ESMTP id 44DA76A1F3;
	Tue,  1 Aug 2006 20:22:07 +0000 (UTC)
Message-ID: <44CFB7EE.6080909@hp.com>
Date: Tue, 01 Aug 2006 16:22:06 -0400
From: Brian Haley <brian.haley@hp.com>
Organization: Open Source and Linux Organization
User-Agent: Thunderbird 1.5.0.4 (X11/20060615)
MIME-Version: 1.0
To: Alexandru Petrescu <alexandru.petrescu@motorola.com>
References: <200607262153.k6QLrEkt072488@givry.rennes.enst-bretagne.fr>	<03cd01c6b194$87a34c20$5a6015ac@dcml.docomolabsusa.com>	<44C8E293.9030205@motorola.com>	<03f101c6b196$e5f29950$5a6015ac@dcml.docomolabsusa.com>
	<44CAA8B6.4040807@motorola.com>
In-Reply-To: <44CAA8B6.4040807@motorola.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: -2.6 (--)
X-Scan-Signature: b132cb3ed2d4be2017585bf6859e1ede
Cc: mip6@ietf.org, James Kempf <kempf@docomolabs-usa.com>
Subject: [Mip6] Re: Comments on draft-ietf-mip6-ha-switch-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>
Errors-To: mip6-bounces@ietf.org

Hi Alex,

Alexandru Petrescu wrote:
> James Kempf wrote:
>> Actually, no. I was thinking of draft-ietf-mip6-ha-switch-00.txt.
> 
> The draft looks good.
> 
> It describes a message exchange between HA and MN.  A HA
> Switch message (a Mobility Header) is sent by HA to MN, optionally
> providing a list of alternate Home Agents.  The MN replies back with a
> BU requesting deletion of the current BCE.  Subsequently the MN performs
> IKE with a randomly chosen HA in the provided list or HA discovery
> otherwise.  The HA Switch message uses IPsec.
> 
> Could you please clarify whether HA Switch considers only HAs on a same
> home link, or can accomodate on different links too.  Because if the
> latter then it's clear that a Home Address should be acquired too, in
> which case ongoing sessions will be interrupted, a thing which should
> absolutely be mentioned.

It would be assumed that the new HA would have to be able to offer 
services for the home prefix this MN is using, the actual text just 
refers to the home link:

  Home Agent Addresses

      A list of alternate home agent addresses on the home link for the
      mobile node.  The number of addresses present in the list is
      indicated by the "# of Addresses" field in the Home Agent Switch
      message.

Guess we could update the "home link" text with something better.

>> There are various reasons why a mobility service provider might want
>>  to do this; an example is if the service provider revokes the
>> account of a user it has reason to believe might use the old home
>> agent address to disrupt service for other users.  With a signaling 
>> message, the service provider could inform mobile nodes to look for a
>>  new home agent.
> 
> Makes no sense.
> 
> It's sufficient for HA to revoke the key of a disruptive MN and it's
> recommended to do that instead of renumbering its HAs and inform all
> other MNs to switch, too much work.
> 
> It might have made sense if a majority of MNs were disruptive.

Would you prefer we removed the text?

>> The home agent addresses field should be constructed as described in 
>> Section 10.5.1 of [3775].
> 
> That cited section is 2-pages long and starts with a description on how
> to build a home agent list and ends with what should be put in the Home
> Agent Addresses field.
> 
> What that means is basically (1) how to collect information from HA RAs
> and (2) how to sort the HA addresses in the Home Agent Addresses field.
> 
> But this spec mentions scenarios "overloaded", "load balancing",
> "maintenance", "functional load balancing", "HA renumbering" without
> providing means to convert these words into actual Preference and
> Lifetime values in the RA.  I'd have preferred that.

When I wrote that it was under the assumption that the HA list built 
from received RAs already had what we needed - a sorted list of HAs on 
the link, so I didn't want to reinvent text.

We also purposely left any load-balancing requirements out of this draft 
just to focus on the signaling aspect - that could be a whole draft in 
itself.

> Also, this spec says that MN chooses randomly the HA in the HA list, so
> no reason to order the list before sending it.

This was a small attempt to load-balance as you don't want every MN to 
choose the first HA in the list, and you don't want the HA to randomize 
it for every MN.  Again, we assumed we already had a sorted list to work 
with.

>> 4.2 Retransmissions
> 
> It's good to have re-transmissions.
> 
> However, since their very goal is to provide reliability against packet
> loss or re-ordering it would be interesting to have an id in the
> message, and echoed back.

The BU/0 is the ACK essentially, but I think you knew that...

> Doing so would avoid a situation where the HA sends a switch to MN
> suggesting another HA1, then HA1 goes down, and HA sends another switch
> with HA2 inside.  If the first switch message is lost and HA receives
> BU/0 then MN has no more connectivity (because HA1 is down and HA
> believes MN responded to the right switch message).

If the MN loses all of its HAs it should fall-back to some bootstrapping 
mechanism, which is outside the scope of the draft :)

Some of this might be covered better in the ha-reliability draft?

>> Upon receipt of a Home Agent Switch message, the mobile node MUST stop 
>> using its current home agent for services and MUST delete its home 
>> binding by sending a Binding Update message as described in [2].
>>
> I'm not sure about the MUST above, I'd rather make it a SHOULD.  Because
> otherwise someone may come up with the idea that even if the HA is
> loaded and needs to switch MN to another HA then MN is probably in a
> situation where it absolutely wants to continue using this HA, so send
> it back a new message "I don't want to switch".  When can this happen?
> If MN is in the middle of a HoTI/HoT it surely doesn't want to switch HAs.

We used MUST because you have to assume the HA is going down.  If the MN 
ignores it then it's going to lose connectivity and/or have to bootstrap 
again.

Thanks for the feedback.

-Brian

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



From mip6-bounces@ietf.org Tue Aug 01 18:05:39 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G82Ms-0002Xe-G0; Tue, 01 Aug 2006 18:05:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G82Ms-0002XZ-5C
	for mip6@ietf.org; Tue, 01 Aug 2006 18:05:38 -0400
Received: from mail1.azairenet.com ([66.92.223.4] helo=bart.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G82Mq-0002oN-Dj
	for mip6@ietf.org; Tue, 01 Aug 2006 18:05:38 -0400
Received: from [10.1.201.0] ([10.1.201.0]) by bart.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Tue, 1 Aug 2006 15:05:34 -0700
Message-ID: <44CFCFB8.2050801@azairenet.com>
Date: Tue, 01 Aug 2006 15:03:36 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.2 (X11/20060516)
MIME-Version: 1.0
To: Hugo Santos <hsantos@av.it.pt>
Subject: Re: [Mip6] Recommendation for bootstrapping using DHCPv6
References: <C0F5172C.20530%basavaraj.patil@nokia.com>	<20060801201411.GF8334@innerghost.net>
	<44CFC5AE.3020504@azairenet.com>
In-Reply-To: <44CFC5AE.3020504@azairenet.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 01 Aug 2006 22:05:34.0075 (UTC)
	FILETIME=[9C7CFCB0:01C6B5B6]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Cc: mip6@ietf.org, Basavaraj Patil <basavaraj.patil@nokia.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

I guess I was hasty in my reply. :(

you are right. most of the bootstrapping mechanisms being
standardized currently in the MIP6 WG will not work with
home agents that implement only RFC 3775. but that was
never the goal anyway.

Vijay

> Hugo Santos wrote:
>> Hi,
>>
>>    I have one question regarding the following:
>>
>> On Tue, Aug 01, 2006 at 02:35:24PM -0500, Basavaraj Patil wrote:
>>> Another concern that I have w.r.t bootstrapping with DHCPv6 is that
>>> instead of having DHCP provide the HoA or the HL prefix to the MS, it
>>> is better to only provide the address of an HA (or list of HAs) and
>>> let the MS send a BU with unspecified address and obtain an address
>>              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>>
>>    RFC 3775 states that the home address specified in Binding Updates
>>  must be unicast routable, would this work with current Home Agents? 
> 
> bootstrapping specifications can "update" RFC 3775. RFC 3775
> assumes the mobile node has a long lived home address that
> does not change. RFC 3775 needs to be updated anyway.
> 
>> By
>>  splitting assignment (DHCP) from mobility management (HA) we would
>>  allow for better upgrade paths. I do understand how your suggestion
>>  would reduce comunication between a DHCP server and the HA, but it
>>  seems that it reduces to something in the line of DHCP but using MH
>>  messages, which involves modifying the Home Agent vs. installing
>>  policies. Would a full IKE exchange be made with the HA before sending
>>  these address-obtaining BUs?
> 
> if IKEv2 is being used to setup security associations between
> the MN and the HA, then the mechanism described in section 5.3
> of 
> http://www.ietf.org/internet-drafts/draft-ietf-mip6-bootstrapping-split-02.txt 
> 
> would apply. a BU with unspecified home address will not be
> sent.
> 
> if RFC 4285 is used instead of IKEv2 and IPsec, then a BU with
> a 0::0 home address and the MN-ID option (RFC 4283) can be
> sent to obtain a home address from the home agent.
> 
> Vijay
> 
> _______________________________________________
> 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 Aug 01 18:32:11 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G82mY-00005a-KP; Tue, 01 Aug 2006 18:32:10 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G82k2-00073b-MH
	for mip6@ietf.org; Tue, 01 Aug 2006 18:29:34 -0400
Received: from mail.av.it.pt ([193.136.92.53] helo=av.it.pt)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G82Vf-0004sv-D1
	for mip6@ietf.org; Tue, 01 Aug 2006 18:14:44 -0400
Received: from [192.168.0.251] (HELO mars.innerghost.net)
	by av.it.pt (CommuniGate Pro SMTP 5.0.9)
	with ESMTP id 5452780; Tue, 01 Aug 2006 23:14:42 +0100
Received: by mars.innerghost.net (Postfix, from userid 1000)
	id BCD93411C; Tue,  1 Aug 2006 23:14:41 +0100 (WEST)
Date: Tue, 1 Aug 2006 23:14:41 +0100
From: Hugo Santos <hsantos@av.it.pt>
To: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
Subject: Re: [Mip6] Recommendation for bootstrapping using DHCPv6
Message-ID: <20060801221441.GH8334@innerghost.net>
References: <C0F5172C.20530%basavaraj.patil@nokia.com>
	<20060801201411.GF8334@innerghost.net>
	<44CFC5AE.3020504@azairenet.com> <44CFCFB8.2050801@azairenet.com>
Mime-Version: 1.0
In-Reply-To: <44CFCFB8.2050801@azairenet.com>
User-Agent: Mutt/1.5.6+20040907i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Cc: mip6@ietf.org, Basavaraj Patil <basavaraj.patil@nokia.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0634340455=="
Errors-To: mip6-bounces@ietf.org


--===============0634340455==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="C4ZO9l7mQWyMv5+Y"
Content-Disposition: inline


--C4ZO9l7mQWyMv5+Y
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Hi Vijay,

On Tue, Aug 01, 2006 at 03:03:36PM -0700, Vijay Devarapalli wrote:
> you are right. most of the bootstrapping mechanisms being
> standardized currently in the MIP6 WG will not work with
> home agents that implement only RFC 3775. but that was
> never the goal anyway.

   Although i understand this position, i believe some solutions could
 in fact be able to use RFC 3775-esque Home agents (well, adding IKEv2
 would probably also be nice). My initial comments was exactly in this
 direction, if the Home agent already offloads the authorization to AAA,
 it might not require anything else. So, modifications should be well
 justified. But i may be missing pieces from the bigger picture.

   Hugo

--C4ZO9l7mQWyMv5+Y
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

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

iD8DBQFEz9JR7asb/itUNKwRAlgJAJ9cQ0J+SqInVyDj/XSj7GDbB5CW4ACfUx4a
e56B7wSmq9Tn/CgPtqx+KMw=
=HROz
-----END PGP SIGNATURE-----

--C4ZO9l7mQWyMv5+Y--


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

--===============0634340455==--




From mip6-bounces@ietf.org Wed Aug 02 06:25:35 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G8Dul-0007pX-CM; Wed, 02 Aug 2006 06:25:23 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G8Duk-0007m2-72
	for mip6@ietf.org; Wed, 02 Aug 2006 06:25:22 -0400
Received: from motgate4.mot.com ([144.189.100.102])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G8Duj-0004Kp-LE
	for mip6@ietf.org; Wed, 02 Aug 2006 06:25:22 -0400
Received: from az33exr01.mot.com (az33exr01.mot.com [10.64.251.231])
	by motgate4.mot.com (8.12.11/Motorola) with ESMTP id k72APD0F023810;
	Wed, 2 Aug 2006 03:25:14 -0700 (MST)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by az33exr01.mot.com (8.13.1/8.13.0) with ESMTP id k72APBaR019721;
	Wed, 2 Aug 2006 05:25:12 -0500 (CDT)
Message-ID: <44D07D86.5010004@motorola.com>
Date: Wed, 02 Aug 2006 12:25:10 +0200
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: Brian Haley <brian.haley@hp.com>
Subject: Re: [Mip6] Re: Comments on draft-ietf-mip6-ha-switch-00.txt
References: <200607262153.k6QLrEkt072488@givry.rennes.enst-bretagne.fr>	<03cd01c6b194$87a34c20$5a6015ac@dcml.docomolabsusa.com>	<44C8E293.9030205@motorola.com>	<03f101c6b196$e5f29950$5a6015ac@dcml.docomolabsusa.com>	<44CAA8B6.4040807@motorola.com>
	<44CFB7EE.6080909@hp.com>
In-Reply-To: <44CFB7EE.6080909@hp.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: AAAAAQAAAAQ=
X-White-List-Member: TRUE
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 827a2a57ca7ab0837847220f447e8d56
Cc: mip6@ietf.org, James Kempf <kempf@docomolabs-usa.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Brian Haley wrote:
> Hi Alex,
> 
> Alexandru Petrescu wrote:
>> James Kempf wrote:
>>> Actually, no. I was thinking of draft-ietf-mip6-ha-switch-00.txt.
>>> 
>>> 
>>> 
>> 
>> The draft looks good.
>> 
>> It describes a message exchange between HA and MN.  A HA Switch 
>> message (a Mobility Header) is sent by HA to MN, optionally 
>> providing a list of alternate Home Agents.  The MN replies back 
>> with a BU requesting deletion of the current BCE.  Subsequently the
>>  MN performs IKE with a randomly chosen HA in the provided list or
>>  HA discovery otherwise.  The HA Switch message uses IPsec.
>> 
>> Could you please clarify whether HA Switch considers only HAs on a
>>  same home link, or can accomodate on different links too.  Because
>>  if the latter then it's clear that a Home Address should be 
>> acquired too, in which case ongoing sessions will be interrupted, a
>>  thing which should absolutely be mentioned.
> 
> It would be assumed that the new HA would have to be able to offer 
> services for the home prefix this MN is using, the actual text just 
> refers to the home link:
> 
> Home Agent Addresses
> 
> A list of alternate home agent addresses on the home link for the 
> mobile node.  The number of addresses present in the list is 
> indicated by the "# of Addresses" field in the Home Agent Switch 
> message.
> 
> Guess we could update the "home link" text with something better.

No, it's fine to me.  I've missed that home link text, sorry.

>>> There are various reasons why a mobility service provider might 
>>> want to do this; an example is if the service provider revokes 
>>> the account of a user it has reason to believe might use the old
>>>  home agent address to disrupt service for other users.  With a 
>>> signaling message, the service provider could inform mobile nodes
>>>  to look for a new home agent.
>> 
>> Makes no sense.
>> 
>> It's sufficient for HA to revoke the key of a disruptive MN and 
>> it's recommended to do that instead of renumbering its HAs and 
>> inform all other MNs to switch, too much work.
>> 
>> It might have made sense if a majority of MNs were disruptive.
> 
> Would you prefer we removed the text?

I suggest so.  It can actually be interpreted as a DoS attack: I steal
somebody's MN, the owner signals this to operator and operator renumbers
all other MNs.  Where I live there are about 200.000 stolen mobile
phones a year and about 80% of them are discarded by operator based on
IMEI, just heard on radio.

>>> The home agent addresses field should be constructed as described
>>>  in Section 10.5.1 of [3775].
>> 
>> That cited section is 2-pages long and starts with a description on
>>  how to build a home agent list and ends with what should be put in
>>  the Home Agent Addresses field.
>> 
>> What that means is basically (1) how to collect information from HA
>>  RAs and (2) how to sort the HA addresses in the Home Agent 
>> Addresses field.
>> 
>> But this spec mentions scenarios "overloaded", "load balancing", 
>> "maintenance", "functional load balancing", "HA renumbering" 
>> without providing means to convert these words into actual 
>> Preference and Lifetime values in the RA.  I'd have preferred that.
>> 
>> 
>> 
> 
> When I wrote that it was under the assumption that the HA list built
>  from received RAs already had what we needed - a sorted list of HAs
>  on the link, so I didn't want to reinvent text.
> 
> We also purposely left any load-balancing requirements out of this 
> draft just to focus on the signaling aspect - that could be a whole 
> draft in itself.
> 
>> Also, this spec says that MN chooses randomly the HA in the HA 
>> list, so no reason to order the list before sending it.
> 
> This was a small attempt to load-balance as you don't want every MN 
> to choose the first HA in the list, and you don't want the HA to 
> randomize it for every MN.  Again, we assumed we already had a sorted
>  list to work with.

Brian, I understand now why you need MN to randomize its choice.  Please
allow me to continue if you don't mind.

What exactly will HAs put in the RA Preference and Lifetime?

For example, if all HAs put same Preference value then they must (by
3775) randomize the list, so again MN wouldn't need to choose randomly,
just pick the first.

>>> 4.2 Retransmissions
>> 
>> It's good to have re-transmissions.
>> 
>> However, since their very goal is to provide reliability against 
>> packet loss or re-ordering it would be interesting to have an id in
>>  the message, and echoed back.
> 
> The BU/0 is the ACK essentially, but I think you knew that...

No, I though it's a BU with lifetime 0 so the HA removes the BCE(?).

>> Doing so would avoid a situation where the HA sends a switch to MN 
>> suggesting another HA1, then HA1 goes down, and HA sends another 
>> switch with HA2 inside.  If the first switch message is lost and HA
>>  receives BU/0 then MN has no more connectivity (because HA1 is 
>> down and HA believes MN responded to the right switch message).
> 
> If the MN loses all of its HAs it should fall-back to some 
> bootstrapping mechanism, which is outside the scope of the draft :)
> 
> Some of this might be covered better in the ha-reliability draft?

Extending the ha-sync with an id wouldn't make sense there.

BTW, I've tried a little bit to comment on the ha-reliability draft but
I'm not sure about its current scoping.  For example it shows in Figure
2 that the HA that becomes active sends the ha-switch message to MN,
instructing it to use itself.  Or the semantics in this (ha-switch)
draft is that the HA that is about to die instructs the MN to choose
another HA in the provided list.  This is different, which one is the
right one ha-switch or ha-reliability?

>>> Upon receipt of a Home Agent Switch message, the mobile node MUST
>>>  stop using its current home agent for services and MUST delete 
>>> its home binding by sending a Binding Update message as described
>>>  in [2].
>>> 
>> I'm not sure about the MUST above, I'd rather make it a SHOULD. 
>> Because otherwise someone may come up with the idea that even if 
>> the HA is loaded and needs to switch MN to another HA then MN is 
>> probably in a situation where it absolutely wants to continue using
>>  this HA, so send it back a new message "I don't want to switch". 
>> When can this happen? If MN is in the middle of a HoTI/HoT it 
>> surely doesn't want to switch HAs.
> 
> We used MUST because you have to assume the HA is going down.  If the
>  MN ignores it then it's going to lose connectivity and/or have to 
> bootstrap again.

Ok then, more explicitely: what will MN do if receiving ha-switch during
a HoTI/HoT exchange.  Ignore the ha-switch?  Reply to HA something?
Just bootstrap?  Change HA and then instruct MN to re-HoTI/HoT?

Alex


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



From mip6-bounces@ietf.org Wed Aug 02 17:45:41 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G8OX1-0000oX-5G; Wed, 02 Aug 2006 17:45:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G8OX0-0000oS-0W
	for mip6@ietf.org; Wed, 02 Aug 2006 17:45:34 -0400
Received: from mout.perfora.net ([217.160.230.41])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G8OWy-00006M-OU
	for mip6@ietf.org; Wed, 02 Aug 2006 17:45:33 -0400
Received: from [85.97.7.241] (helo=IBM52A5038A94F)
	by mrelay.perfora.net (node=mrelayus0) with ESMTP (Nemesis),
	id 0MKoyl-1G8OWs1hGU-0005aB; Wed, 02 Aug 2006 17:45:29 -0400
From: "Alper Yegin" <alper.yegin@yegin.org>
To: "'Basavaraj Patil'" <basavaraj.patil@nokia.com>,
	<mip6@ietf.org>
Subject: RE: [Mip6] Recommendation for bootstrapping using DHCPv6
Date: Thu, 3 Aug 2006 00:45:23 +0300
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
In-Reply-To: <C0F5172C.20530%basavaraj.patil@nokia.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
Thread-Index: Aca1oaIQ4K1FzyGUEduPhAARJNUNiAA2bJdQ
Message-ID: <0MKoyl-1G8OWs1hGU-0005aB@mrelay.perfora.net>
X-Provags-ID: perfora.net abuse@perfora.net
	login:abf7a4bb310ea4dfc9b6841113e2970f
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6cca30437e2d04f45110f2ff8dc1b1d5
Cc: 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi Raj,

"Having the options specified in a stand-along document will not add much
value."

As we have been stating, draft-jang-mip6-hiopt-00.txt also has a use that
does not tie into the RADIUS-driven details -- the use where DHCP server can
be manually configured and has nothing to do with the AAA. 

Your above statement misses this point. 

Besides, while there is a standalone use for draft-jang-mip6-hiopt-00.txt,
there is none for the RADIUS and Diameter specs we expect to document
individually. Should we also merge those AAA documents with the others?

Also, I'm not sure what specific concern you are raising with respect to the
quoted text below.

Alper



> -----Original Message-----
> From: Basavaraj Patil [mailto:basavaraj.patil@nokia.com]
> Sent: Tuesday, August 01, 2006 12:35 PM
> To: mip6@ietf.org
> Subject: [Mip6] Recommendation for bootstrapping using DHCPv6
> 
> 
> Alper/Kuntal et al,
> 
> I have reviewed the drafts:
> 1. Problem Statement for bootstrapping Mobile IPv6
>    (draft-ietf-mip6-bootstrap-ps-05)
> 2. MIP6-bootstrapping via DHCPv6 for the Integrated Scenario
>    (draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt)
> 
> and
> 3. DHCP Option for Home Information Discovery in MIPv6
>    (draft-jang-mip6-hiopt-00.txt)
> 
> My conclusion from the review is that the integrated scenario
> bootstrapping via DHCPv6 is covering the cases when DHCP is the
> preferred method by MNs.
> 
> The WG I-D draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt in
> sections 3.5 and 3.8 explain how DHCP would work. Having the options
> specified in a stand-along document will not add much value. I am also
> concerned about the fact in draft-jang which states that:
> "
>    The availability of the requested information depends on the DHCP
>    server having prior knowledge or dynamically discovering it.  While
>    the specific details are outside the scope of this document, use of
>    static tables and AAA-assisted discovery are possible options
> "
> 
> Another concern that I have w.r.t bootstrapping with DHCPv6 is that
> instead of having DHCP provide the HoA or the HL prefix to the MS, it
> is better to only provide the address of an HA (or list of HAs) and
> let the MS send a BU with unspecified address and obtain an address
> from the HA. This will simplify bootstrapping and also reduce the
> interaction between DHCP and the HA from an address management
> perspective. Hence you may want to reconsider the DHCP option which
> carry the HL Prefix or the HoA for the MS.
> 
> I recommend that the DHCP option specified in draft-jang be
> incorporated into the WG I-D and progressed on standards track. As a
> result the WG will have a mechanism for bootstrapping MIP6 with DHCP
> that also includes the DHCP options in a single I-D.
> 
> -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 Wed Aug 02 19:01:03 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G8Phz-0008Je-9c; Wed, 02 Aug 2006 19:00:59 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G8Phy-0008JZ-Qo
	for mip6@ietf.org; Wed, 02 Aug 2006 19:00:58 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G8KCT-0001hp-Ps
	for mip6@ietf.org; Wed, 02 Aug 2006 13:08:05 -0400
Received: from atlrel7.hp.com ([156.153.255.213])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1G8K04-0005Ni-V8
	for mip6@ietf.org; Wed, 02 Aug 2006 12:55:17 -0400
Received: from smtp2.fc.hp.com (smtp2.fc.hp.com [15.11.136.114])
	by atlrel7.hp.com (Postfix) with ESMTP id ADF7A3881F;
	Wed,  2 Aug 2006 12:55:12 -0400 (EDT)
Received: from [16.116.114.13] (spaceshipone.zko.hp.com [16.116.114.13])
	by smtp2.fc.hp.com (Postfix) with ESMTP id 0994367292;
	Wed,  2 Aug 2006 16:55:11 +0000 (UTC)
Message-ID: <44D0D8EE.4030302@hp.com>
Date: Wed, 02 Aug 2006 12:55:10 -0400
From: Brian Haley <brian.haley@hp.com>
Organization: Open Source and Linux Organization
User-Agent: Thunderbird 1.5.0.4 (X11/20060615)
MIME-Version: 1.0
To: Alexandru Petrescu <alexandru.petrescu@motorola.com>
Subject: Re: [Mip6] Re: Comments on draft-ietf-mip6-ha-switch-00.txt
References: <200607262153.k6QLrEkt072488@givry.rennes.enst-bretagne.fr>	<03cd01c6b194$87a34c20$5a6015ac@dcml.docomolabsusa.com>	<44C8E293.9030205@motorola.com>	<03f101c6b196$e5f29950$5a6015ac@dcml.docomolabsusa.com>	<44CAA8B6.4040807@motorola.com>	<44CFB7EE.6080909@hp.com>
	<44D07D86.5010004@motorola.com>
In-Reply-To: <44D07D86.5010004@motorola.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: -2.6 (--)
X-Scan-Signature: 34d35111647d654d033d58d318c0d21a
Cc: mip6@ietf.org, James Kempf <kempf@docomolabs-usa.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Alexandru Petrescu wrote:

>>> Also, this spec says that MN chooses randomly the HA in the HA list, 
>>> so no reason to order the list before sending it.
>>
>> This was a small attempt to load-balance as you don't want every MN to 
>> choose the first HA in the list, and you don't want the HA to 
>> randomize it for every MN.  Again, we assumed we already had a sorted
>>  list to work with.
> 
> Brian, I understand now why you need MN to randomize its choice.  Please
> allow me to continue if you don't mind.
> 
> What exactly will HAs put in the RA Preference and Lifetime?
> 
> For example, if all HAs put same Preference value then they must (by
> 3775) randomize the list, so again MN wouldn't need to choose randomly,
> just pick the first.

Ok, I understand now, don't know how I missed this bullet in 10.5.1:

    o  The IP addresses in the Home Agent Addresses field SHOULD be
       listed in order of decreasing preference values, based either on
       the respective advertised preference from a Home Agent Information
       option or on the default preference of 0 if no preference is
       advertised (or on the configured home agent preference for this
       home agent itself).

So I'll change the ha-switch draft to not have the MN randomly select a 
HA from the message, just use the first, second, etc.

>>>> 4.2 Retransmissions
>>>
>>> It's good to have re-transmissions.
>>>
>>> However, since their very goal is to provide reliability against 
>>> packet loss or re-ordering it would be interesting to have an id in
>>>  the message, and echoed back.
>>
>> The BU/0 is the ACK essentially, but I think you knew that...
> 
> No, I though it's a BU with lifetime 0 so the HA removes the BCE(?).

That's what I meant with BU/0, my bad shorthand.

>>> Doing so would avoid a situation where the HA sends a switch to MN 
>>> suggesting another HA1, then HA1 goes down, and HA sends another 
>>> switch with HA2 inside.  If the first switch message is lost and HA
>>>  receives BU/0 then MN has no more connectivity (because HA1 is down 
>>> and HA believes MN responded to the right switch message).
>>
>> If the MN loses all of its HAs it should fall-back to some 
>> bootstrapping mechanism, which is outside the scope of the draft :)
>>
>> Some of this might be covered better in the ha-reliability draft?
> 
> Extending the ha-sync with an id wouldn't make sense there.
> 
> BTW, I've tried a little bit to comment on the ha-reliability draft but
> I'm not sure about its current scoping.  For example it shows in Figure
> 2 that the HA that becomes active sends the ha-switch message to MN,
> instructing it to use itself.  Or the semantics in this (ha-switch)
> draft is that the HA that is about to die instructs the MN to choose
> another HA in the provided list.  This is different, which one is the
> right one ha-switch or ha-reliability?

HA-switch needs to be updated to support ha-reliability in allowing 
another HA to send the message, didn't have time before the cutoff.

>>>> Upon receipt of a Home Agent Switch message, the mobile node MUST
>>>>  stop using its current home agent for services and MUST delete its 
>>>> home binding by sending a Binding Update message as described
>>>>  in [2].
>>>>
>>> I'm not sure about the MUST above, I'd rather make it a SHOULD. 
>>> Because otherwise someone may come up with the idea that even if the 
>>> HA is loaded and needs to switch MN to another HA then MN is probably 
>>> in a situation where it absolutely wants to continue using
>>>  this HA, so send it back a new message "I don't want to switch". 
>>> When can this happen? If MN is in the middle of a HoTI/HoT it surely 
>>> doesn't want to switch HAs.
>>
>> We used MUST because you have to assume the HA is going down.  If the
>>  MN ignores it then it's going to lose connectivity and/or have to 
>> bootstrap again.
> 
> Ok then, more explicitely: what will MN do if receiving ha-switch during
> a HoTI/HoT exchange.  Ignore the ha-switch?  Reply to HA something?
> Just bootstrap?  Change HA and then instruct MN to re-HoTI/HoT?

I don't understand why HoTI/HoT is a special case since it's between the 
MN and a CN, as long as the MN can send via a HA and that HA can 
intercept packets for it, mobility should work.

-Brian

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



From mip6-bounces@ietf.org Wed Aug 02 20:07:49 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G8Qkb-0005zw-0T; Wed, 02 Aug 2006 20:07:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G8QkZ-0005zn-5F
	for mip6@ietf.org; Wed, 02 Aug 2006 20:07:43 -0400
Received: from usaga01-in.huawei.com ([12.129.211.51])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G8QkT-0005he-OH
	for mip6@ietf.org; Wed, 02 Aug 2006 20:07:43 -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 <0J3E006W6AVGO3@usaga01-in.huawei.com> for
	mip6@ietf.org; Wed, 02 Aug 2006 17:04:28 -0700 (PDT)
Received: from Nakhjiri73701
	(pool-71-112-23-187.sttlwa.dsl-w.verizon.net [71.112.23.187])
	by usaga01-in.huawei.com
	(iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar  3 2004))
	with ESMTPA id <0J3E00F81AV891@usaga01-in.huawei.com> for mip6@ietf.org;
	Wed, 02 Aug 2006 17:04:27 -0700 (PDT)
Date: Wed, 02 Aug 2006 17:07:27 -0700
From: Madjid Nakhjiri <mnakhjiri@huawei.com>
In-reply-to: <003b01c6b5bc$faf001b0$6401a8c0@china.huawei.com>
To: mip6@ietf.org
Message-id: <002101c6b690$ce892c80$6401a8c0@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
X-Mailer: Microsoft Office Outlook 11
Thread-index: Aca1vPhZcNfDvQ2jTcWBw+1V22IdBwA06FBQ
X-Spam-Score: 0.1 (/)
X-Scan-Signature: ea36de7a5e28e9b4461c8d685f4e97f1
Cc: 
Subject: [Mip6] comments on AAA-HA-goals-02
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-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="===============0056038545=="
Errors-To: mip6-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0056038545==
Content-type: multipart/alternative;
	boundary="Boundary_(ID_QMa29lY4veV6E3vtfhRAJg)"

This is a multi-part message in MIME format.

--Boundary_(ID_QMa29lY4veV6E3vtfhRAJg)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT

Resending this message on the list, since it was sitting for moderator
approval!

 

Madjid

 

  _____  

From: Madjid Nakhjiri [mailto:mnakhjiri@huawei.com] 
Sent: Tuesday, August 01, 2006 3:51 PM
To: gerardo.giaretta@telecomitalia.it; julien.bournelle@int-evry.fr; 'Rafa
Marin Lopez'
Cc: 'Madjid Nakhjiri'; mip6@ietf.org; basavaraj.patil@nokia.com;
gdommety@cisco.com
Subject: comments on AAA-HA-goals-02

 

Hi, 

I have been trying to subscribe to this list since a few hours ago (not a
member yet), so I am ccing the chairs and authors I know for approval of
this message.

 I am new to the MIP6 bootstrapping terminology, but not new to
bootstrapping or AAA-MIP interactions. I just looked through the HA-AAA
goals drafts. Thank you for a very well written draft that also provides a
good summary of the split and integrated scenarios as well. I do however
find some the terminology confusing. I apologize if my questions have been
discussed extensively on the mailing list. I would appreciate if the authors
or other people can shed some light on some of the terminology or point me
to the proper document to read, I have started going through the
bootstrapping draft a bit as well, and am planning to see how MIP6-AAA
interaction works. 

*        The way the terminology of Mobility service provider and Access
service provider in the context of MIP6, which is layer 3 mobility, would be
defined in my mind is that the MSP only provides MIP6 services, while the
ASP provides access services, such as L2 access, QoS and other services
(guessing IP connectivity/ DHCP and so on). The network MSA to me symbolizes
the MSP-AAA server, while ASA symbolizes ASP-AAA server. 

*        I see a hot spot provider or a 802.16d network without mobility
support as an ASP, while a IP enabled cellular or a WiMAX network as a
combination of ASP and MSP. To me assignment of HA falls into the MSP
service category, not ASP service category (I just confirmed this in
bootstrapping-ps section 7.1), so there are some statements in the draft as
far as an  ASP assigning an HA and I don't think those are appropriate based
on the terminology provided. 

*        Then there is the concept of home versus visited domain. I am
guessing "domain" to administrative domain (AAA domain). Traditionally AAA
community is denoted as home and visited AAA servers, i.e. AAAH and AAAV,
respectively. I just checked the bootstrapping-ps draft and that draft calls
uses the term "serving" instead of "visited", but still provides a
distinction between home versus serving MSP (MSPH and MSPS) and between home
versus serving ASP (ASPH and ASPS). Having said this, I think if the group
is going to great length to separate ASP/ MSP and ASA/MSA, it also needs to
distinguish between the home versus visited domain for each of the
authorizers. So that MSAH refers to AAA server within home MSP (MSP-H) and
MSAV or MSAS (pick one) to AAA server within visited or serving MSP (MSP-V
or MSP-S). The same goes for ASAH and ASAV. This means Serving MSA is not
the same as serving ASA. It is not proper to equate the access service
provider (ASP) with MSP-V the visited domain as it is implied in section
4.2: "Mobile Node requests a home agent to the Access Service Provider
(ASP)". According to my understanding of the terminology of ASP, ASP has
nothing to anything to do with HA assignment. I think this can be easily
remedied by introducing MSAH and MSAS. Visited domain HA allocation can be
formulated as "MN can request MSAH for an HA assignment within MSPS after
authentication to MSAH and authorization of mobility service by the
MSAH/MSAS to MN".

*        The same goes for another sentence in the same section saying "..
Mobile Node can specify if it wants a home agent provided by the visited
domain (ASP) or by the home domain (ASA)", which seems to be mixing
(mobility and access service), (home and visited), (provider and authorizer)
all in the same sentence!!

*        The other comment along the same line is about section 4.1, where
it is stated a pool of HA s can rely on the home EAP server (I am guessing
EAP server belonging to MSA-H, since this is split scenario) for
authentication. Here it is stated "It allows the roaming mobility case in
which the MN obtains the mobility service in a different administrative
domain (MSP !=MSA). Here it seems that it is implied HA is part of MSP
function (appropriately), however, I am not sure if MSP and MSA can imply
two administrative domains, to me administrative domain implies AAA domain,
so one would be MSA-H and another MSA-V, so an HA could be authorized within
MSA-V based on authentication to MSA-H and authorization by MSA-H.

*        I also have an issue with the usage of term NAS in next to last
paragraph of section 3. NAS is really an access service agent (as the name
implies) not a mobility service agent. NAS performs many functions beyond
the AAA client function, which brings up two issues. 1) the sentence ".HA,
that can be seen as Network Access Server for MIP6", is only providing
confusion in this context, you may say that HA can be seen as Network
mobility server if you want but in a draft that has ASP and MSP everywhere.
2) in the goals sections (5.1/ 5.2) , it is not mentioned anywhere that the
HA MUST act as a AAA client, is this a non-requirement, or is it implicitly
understood?  Especially G2.2 seems to imply this.

*        In 5.4 why is it a "MUST" for HA to be an EAP pass-through
authenticator? As long as HA receives its information from the AAA server in
a secure fashion and both HA and AAA can identify the MN and its EAP session
uniquely, there is no reason for allocating HA and EAP pass-through EAP
authenticator in the same box.

*        For section 4.2, Integrated scenario, I see that NAS gets MIP6 conf
parameters from the AAAH, how does the HA receives the information it needs?

Thank you for your attention,

 

Madjid Nakhjiri

 


--Boundary_(ID_QMa29lY4veV6E3vtfhRAJg)
Content-type: text/html; charset=us-ascii
Content-transfer-encoding: 7BIT

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

<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Times;
	panose-1:2 2 6 3 5 4 5 2 3 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Times New Roman";}
p.MsoListBullet, li.MsoListBullet, div.MsoListBullet
	{margin-top:0in;
	margin-right:.5in;
	margin-bottom:10.0pt;
	margin-left:.25in;
	text-align:justify;
	text-justify:inter-ideograph;
	text-indent:-.25in;
	line-height:10.0pt;
	mso-list:l1 level1 lfo3;
	font-size:10.0pt;
	font-family:Times;}
p.MsoBodyText, li.MsoBodyText, div.MsoBodyText
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:6.0pt;
	margin-left:0in;
	font-size:10.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.EmailStyle19
	{mso-style-type:personal;
	font-family:Arial;
	color:windowtext;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:-119;
	mso-list-type:simple;
	mso-list-template-ids:-1660903884;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-style-link:"List Bullet";
	mso-level-text:\F0B7;
	mso-level-tab-stop:.25in;
	mso-level-number-position:left;
	margin-left:.25in;
	text-indent:-.25in;
	font-family:Symbol;}
@list l1
	{mso-list-id:1393693341;
	mso-list-type:simple;
	mso-list-template-ids:-1674154234;}
@list l1:level1
	{mso-level-number-format:bullet;
	mso-level-style-link:"List Bullet";
	mso-level-text:\F0A7;
	mso-level-tab-stop:.25in;
	mso-level-number-position:left;
	margin-left:.25in;
	text-indent:-.25in;
	mso-ansi-font-size:8.0pt;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>

</head>

<body lang=EN-US link=blue vlink=purple>

<div class=Section1>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Resending this message on the list, since
it was sitting for moderator approval!<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Madjid<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div>

<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>

<hr size=3 width="100%" align=center tabindex=-1>

</span></font></div>

<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font face=Tahoma><span
style='font-family:Tahoma'> Madjid Nakhjiri [mailto:mnakhjiri@huawei.com] <br>
<b><span style='font-weight:bold'>Sent:</span></b> Tuesday, August 01, 2006
3:51 PM<br>
<b><span style='font-weight:bold'>To:</span></b> gerardo.giaretta@telecomitalia.it;
julien.bournelle@int-evry.fr; 'Rafa Marin Lopez'<br>
<b><span style='font-weight:bold'>Cc:</span></b> 'Madjid Nakhjiri';
mip6@ietf.org; basavaraj.patil@nokia.com; gdommety@cisco.com<br>
<b><span style='font-weight:bold'>Subject:</span></b> comments on
AAA-HA-goals-02</span></font><font size=3><span style='font-size:12.0pt'><o:p></o:p></span></font></p>

</div>

<p class=MsoNormal><font size=2 face="Times New Roman"><span style='font-size:
10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoListBullet style='margin-left:0in;text-indent:0in;mso-list:none'><font
size=2 face=Times><span style='font-size:10.0pt'>Hi, <o:p></o:p></span></font></p>

<p class=MsoListBullet style='margin-left:0in;text-indent:0in;mso-list:none'><font
size=2 face=Times><span style='font-size:10.0pt'>I have been trying to
subscribe to this list since a few hours ago (not a member yet), so I am ccing
the chairs and authors I know for approval of this message.<o:p></o:p></span></font></p>

<p class=MsoListBullet style='margin-left:0in;text-indent:0in;mso-list:none'><font
size=2 face=Times><span style='font-size:10.0pt'>&nbsp;I am new to the MIP6 bootstrapping
terminology, but not new to bootstrapping or AAA-MIP interactions. I just
looked through the HA-AAA goals drafts. Thank you for a very well written draft
that also provides a good summary of the split and integrated scenarios as
well. I do however find some the terminology confusing. I apologize if my
questions have been discussed extensively on the mailing list. I would
appreciate if the authors or other people can shed some light on some of the
terminology or point me to the proper document to read, I have started going
through the bootstrapping draft a bit as well, and am planning to see how
MIP6-AAA interaction works. <o:p></o:p></span></font></p>

<p class=MsoListBullet><![if !supportLists]><font size=1 face=Wingdings><span
style='font-size:8.0pt;font-family:Wingdings'><span style='mso-list:Ignore'>&sect;<font
size=1 face="Times New Roman"><span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]>The way the terminology of
Mobility service provider and Access service provider in the context of MIP6,
which is layer 3 mobility, would be defined in my mind is that the MSP only
provides MIP6 services, while the ASP provides access services, such as L2
access, QoS and other services (guessing IP connectivity/ DHCP and so on). The
network MSA to me symbolizes the MSP-AAA server, while ASA symbolizes ASP-AAA
server. <o:p></o:p></p>

<p class=MsoListBullet><![if !supportLists]><font size=1 face=Wingdings><span
style='font-size:8.0pt;font-family:Wingdings'><span style='mso-list:Ignore'>&sect;<font
size=1 face="Times New Roman"><span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]>I see a hot spot provider or a
802.16d network without mobility support as an ASP, while a IP enabled cellular
or a WiMAX network as a combination of ASP and MSP. To me assignment of HA
falls into the MSP service category, not ASP service category (I just confirmed
this in bootstrapping-ps section 7.1), so there are some statements in the
draft as far as an&nbsp; ASP assigning an HA and I don&#8217;t think those are
appropriate based on the terminology provided. <o:p></o:p></p>

<p class=MsoListBullet><![if !supportLists]><font size=1 face=Wingdings><span
style='font-size:8.0pt;font-family:Wingdings'><span style='mso-list:Ignore'>&sect;<font
size=1 face="Times New Roman"><span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]>Then there is the concept of home
versus visited domain. I am guessing &#8220;domain&#8221; to administrative
domain (AAA domain). Traditionally AAA community is denoted as home and visited
AAA servers, i.e. AAAH and AAAV, respectively. I just checked the bootstrapping-ps
draft and that draft calls uses the term &#8220;serving&#8221; instead of
&#8220;visited&#8221;, but still provides a distinction between home versus
serving MSP (MSPH and MSPS) and between home versus serving ASP (ASPH and
ASPS). Having said this, I think if the group is going to great length to
separate ASP/ MSP and ASA/MSA, it also needs to distinguish between the home
versus visited domain for each of the authorizers. So that MSAH refers to AAA
server within home MSP (MSP-H) and MSAV or MSAS (pick one) to AAA server within
visited or serving MSP (MSP-V or MSP-S). The same goes for ASAH and ASAV. This
means Serving MSA is not the same as serving ASA. It is not proper to equate
the access service provider (ASP) with MSP-V the visited domain as it is
implied in section 4.2: &#8220;Mobile Node requests a home agent to the Access
Service Provider (ASP)&#8221;. According to my understanding of the terminology
of ASP, ASP has nothing to anything to do with HA assignment. I think this can
be easily remedied by introducing MSAH and MSAS. Visited domain HA allocation
can be formulated as &#8220;MN can request MSAH for an HA assignment within
MSPS after authentication to MSAH and authorization of mobility service by the
MSAH/MSAS to MN&#8221;.<o:p></o:p></p>

<p class=MsoListBullet><![if !supportLists]><font size=1 face=Wingdings><span
style='font-size:8.0pt;font-family:Wingdings'><span style='mso-list:Ignore'>&sect;<font
size=1 face="Times New Roman"><span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]>The same goes for another sentence
in the same section saying &#8220;.. Mobile Node can specify if it wants a home
agent provided by the visited domain (ASP) or by the home domain (ASA)&#8221;,
which seems to be mixing (mobility and access service), (home and visited),
(provider and authorizer) all in the same sentence!!<o:p></o:p></p>

<p class=MsoListBullet><![if !supportLists]><font size=1 face=Wingdings><span
style='font-size:8.0pt;font-family:Wingdings'><span style='mso-list:Ignore'>&sect;<font
size=1 face="Times New Roman"><span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]>The other comment along the same
line is about section 4.1, where it is stated a pool of HA s can rely on the
home EAP server (I am guessing EAP server belonging to MSA-H, since this is
split scenario) for authentication. Here it is stated &#8220;It allows the
roaming mobility case in which the MN obtains the mobility service in a
different administrative domain (MSP !=MSA). Here it seems that it is implied
HA is part of MSP function (appropriately), however, I am not sure if MSP and
MSA can imply two administrative domains, to me administrative domain implies
AAA domain, so one would be MSA-H and another MSA-V, so an HA could be
authorized within MSA-V based on authentication to MSA-H and authorization by
MSA-H.<o:p></o:p></p>

<p class=MsoListBullet><![if !supportLists]><font size=1 face=Wingdings><span
style='font-size:8.0pt;font-family:Wingdings'><span style='mso-list:Ignore'>&sect;<font
size=1 face="Times New Roman"><span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]>I also have an issue with the
usage of term NAS in next to last paragraph of section 3. NAS is really an
access service agent (as the name implies) not a mobility service agent. NAS
performs many functions beyond the AAA client function, which brings up two
issues. 1) the sentence &#8220;&#8230;HA, that can be seen as Network Access
Server for MIP6&#8221;, is only providing confusion in this context, you may
say that HA can be seen as Network mobility server if you want but in a draft
that has ASP and MSP everywhere&#8230; 2) in the goals sections (5.1/ 5.2) , it
is not mentioned anywhere that the HA MUST act as a AAA client, is this a
non-requirement, or is it implicitly understood? &nbsp;Especially G2.2 seems to
imply this.<o:p></o:p></p>

<p class=MsoListBullet><![if !supportLists]><font size=1 face=Wingdings><span
style='font-size:8.0pt;font-family:Wingdings'><span style='mso-list:Ignore'>&sect;<font
size=1 face="Times New Roman"><span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]>In 5.4 why is it a
&#8220;MUST&#8221; for HA to be an EAP pass-through authenticator? As long as
HA receives its information from the AAA server in a secure fashion and both HA
and AAA can identify the MN and its EAP session uniquely, there is no reason
for allocating HA and EAP pass-through EAP authenticator in the same box.<o:p></o:p></p>

<p class=MsoListBullet><![if !supportLists]><font size=1 face=Wingdings><span
style='font-size:8.0pt;font-family:Wingdings'><span style='mso-list:Ignore'>&sect;<font
size=1 face="Times New Roman"><span style='font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></font></span></span></font><![endif]>For section 4.2, Integrated
scenario, I see that NAS gets MIP6 conf parameters from the AAAH, how does the
HA receives the information it needs?<o:p></o:p></p>

<p class=MsoNormal><font size=2 face="Times New Roman"><span style='font-size:
10.0pt'>Thank you for your attention,<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=2 face="Times New Roman"><span style='font-size:
10.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=MsoNormal><font size=2 face="Times New Roman"><span style='font-size:
10.0pt'>Madjid Nakhjiri<o:p></o:p></span></font></p>

<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

--Boundary_(ID_QMa29lY4veV6E3vtfhRAJg)--


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

--===============0056038545==--




From mip6-bounces@ietf.org Thu Aug 03 10:20:02 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G8e3G-0003t5-7q; Thu, 03 Aug 2006 10:19:54 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G8e3F-0003t0-84
	for mip6@ietf.org; Thu, 03 Aug 2006 10:19:53 -0400
Received: from smtp2.int-evry.fr ([157.159.10.45])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G8e3C-0000wj-KO
	for mip6@ietf.org; Thu, 03 Aug 2006 10:19:53 -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 9CFE92FD7A;
	Thu,  3 Aug 2006 16:19:48 +0200 (CEST)
Received: from jb by ipv6-3.int-evry.fr with local (Exim 4.52)
	id 1G8e5R-0001TT-HE; Thu, 03 Aug 2006 16:22:09 +0200
Date: Thu, 3 Aug 2006 16:22:09 +0200
From: Julien Bournelle <julien.bournelle@int-evry.fr>
To: Madjid Nakhjiri <mnakhjiri@huawei.com>
Subject: Re: [Mip6] comments on AAA-HA-goals-02
Message-ID: <20060803142209.GA5650@ipv6-3.int-evry.fr>
References: <003b01c6b5bc$faf001b0$6401a8c0@china.huawei.com>
	<002101c6b690$ce892c80$6401a8c0@china.huawei.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <002101c6b690$ce892c80$6401a8c0@china.huawei.com>
User-Agent: Mutt/1.5.9i
X-INT-MailScanner-Information: Please contact the ISP for more information
X-INT-MailScanner: Found to be clean
X-INT-MailScanner-MCPCheck: 
X-INT-MailScanner-SpamCheck: 
X-MailScanner-From: jb@int-evry.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 20f22c03b5c66958bff5ef54fcda6e48
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi madjid,

 let me try to respond to your mail though some terminology issues are more related to the
 draft-ietf-mip6-bootstrapping-ps draft.

 First of all, thanks for reading the document.

On Wed, Aug 02, 2006 at 05:07:27PM -0700, Madjid Nakhjiri wrote:

<snip>
> 
>  I am new to the MIP6 bootstrapping terminology, but not new to
> bootstrapping or AAA-MIP interactions. I just looked through the HA-AAA
> goals drafts. Thank you for a very well written draft that also provides a
> good summary of the split and integrated scenarios as well. 

 thanks,
 
> I do however
> find some the terminology confusing. I apologize if my questions have been
> discussed extensively on the mailing list. I would appreciate if the authors
> or other people can shed some light on some of the terminology or point me
> to the proper document to read, I have started going through the
> bootstrapping draft a bit as well, and am planning to see how MIP6-AAA
> interaction works. 
> 
> *        The way the terminology of Mobility service provider and Access
> service provider in the context of MIP6, which is layer 3 mobility, would be
> defined in my mind is that the MSP only provides MIP6 services, while the
> ASP provides access services, such as L2 access, QoS and other services
> (guessing IP connectivity/ DHCP and so on). 

 right

> The network MSA to me symbolizes
> the MSP-AAA server, while ASA symbolizes ASP-AAA server. 

 no, the MSA is administrative entity with whom the user has a contract
 and thus credentials. The MSP effectively provides the MIP6 service to
 the user. Thus the MSP may have to contact the MSA before providing the
 service. 

> 
> *        I see a hot spot provider or a 802.16d network without mobility
> support as an ASP, while a IP enabled cellular or a WiMAX network as a
> combination of ASP and MSP. To me assignment of HA falls into the MSP
> service category, not ASP service category (I just confirmed this in
> bootstrapping-ps section 7.1), so there are some statements in the draft as
> far as an  ASP assigning an HA and I don't think those are appropriate based
> on the terminology provided. 

 it depends if we are in the split or integrated scenario.
 In the split scenario, we don't have ASP/ASA, only MSP/MSA. So the user
 has an HA from the MSP.
 In the integrated scenario, if MSP=ASP, the user obtains an HA from the
 MSP/ASP. 


> 
> *        Then there is the concept of home versus visited domain. I am
> guessing "domain" to administrative domain (AAA domain). Traditionally AAA
> community is denoted as home and visited AAA servers, i.e. AAAH and AAAV,
> respectively. I just checked the bootstrapping-ps draft and that draft calls
> uses the term "serving" instead of "visited", but still provides a
> distinction between home versus serving MSP (MSPH and MSPS) and between home
> versus serving ASP (ASPH and ASPS). Having said this, I think if the group
> is going to great length to separate ASP/ MSP and ASA/MSA, it also needs to
> distinguish between the home versus visited domain for each of the
> authorizers. So that MSAH refers to AAA server within home MSP (MSP-H) and
> MSAV or MSAS (pick one) to AAA server within visited or serving MSP (MSP-V
> or MSP-S). The same goes for ASAH and ASAV. This means Serving MSA is not
> the same as serving ASA. It is not proper to equate the access service
> provider (ASP) with MSP-V the visited domain as it is implied in section
> 4.2: "Mobile Node requests a home agent to the Access Service Provider
> (ASP)". According to my understanding of the terminology of ASP, ASP has
> nothing to anything to do with HA assignment. I think this can be easily
> remedied by introducing MSAH and MSAS. Visited domain HA allocation can be
> formulated as "MN can request MSAH for an HA assignment within MSPS after
> authentication to MSAH and authorization of mobility service by the
> MSAH/MSAS to MN".

 maybe my explanation below will answer to this paragraph ?

> *        The same goes for another sentence in the same section saying "..
> Mobile Node can specify if it wants a home agent provided by the visited
> domain (ASP) or by the home domain (ASA)", which seems to be mixing
> (mobility and access service), (home and visited), (provider and authorizer)
> all in the same sentence!!

 yes, that can be confusing. 

> 
> *        The other comment along the same line is about section 4.1, where
> it is stated a pool of HA s can rely on the home EAP server (I am guessing
> EAP server belonging to MSA-H, since this is split scenario) for
> authentication. Here it is stated "It allows the roaming mobility case in
> which the MN obtains the mobility service in a different administrative
> domain (MSP !=MSA). Here it seems that it is implied HA is part of MSP
> function (appropriately), however, I am not sure if MSP and MSA can imply
> two administrative domains, to me administrative domain implies AAA domain,
> so one would be MSA-H and another MSA-V, so an HA could be authorized within
> MSA-V based on authentication to MSA-H and authorization by MSA-H.

 MSP has its own AAA server. MSA is the AAA server of the MN. 
 Does it respond to your comment ?


> 
> *        I also have an issue with the usage of term NAS in next to last
> paragraph of section 3. NAS is really an access service agent (as the name
> implies) not a mobility service agent. NAS performs many functions beyond
> the AAA client function, which brings up two issues. 1) the sentence ".HA,
> that can be seen as Network Access Server for MIP6", is only providing
> confusion in this context, you may say that HA can be seen as Network
> mobility server if you want but in a draft that has ASP and MSP everywhere.

 ok.

> 2) in the goals sections (5.1/ 5.2) , it is not mentioned anywhere that the
> HA MUST act as a AAA client, is this a non-requirement, or is it implicitly
> understood?  Especially G2.2 seems to imply this.

 I think it is implicitly understood. Do you think we should add a
 statement on this ?

> 
> *        In 5.4 why is it a "MUST" for HA to be an EAP pass-through
> authenticator? As long as HA receives its information from the AAA server in
> a secure fashion and both HA and AAA can identify the MN and its EAP session
> uniquely, there is no reason for allocating HA and EAP pass-through EAP
> authenticator in the same box.

 hmmm, the HA acts as a AAA client and MN uses IKEv2 with EAP to be
 authenticated. So the HA MUST act as an EAP pass-through authenticator.

 Am I missing something ? do you think we should rephrase this ?

> 
> *        For section 4.2, Integrated scenario, I see that NAS gets MIP6 conf
> parameters from the AAAH, how does the HA receives the information it needs?

 In the integrated scenario based on DHCPv6, the MN gets HA info through
 DHCP. Then we fall in the split scenario and the MN uses IKEv2 with the
 HA. 


 Julien Bournelle

> Thank you for your attention,
> 
>  
> 
> Madjid Nakhjiri
> 
>  
> 

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


-- 
julien.bournelle at int-evry.fr

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



From mip6-bounces@ietf.org Thu Aug 03 11:56:03 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G8fYF-0004i3-4L; Thu, 03 Aug 2006 11:55:59 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G8fYE-0004hy-0p
	for mip6@ietf.org; Thu, 03 Aug 2006 11:55:58 -0400
Received: from web60317.mail.yahoo.com ([209.73.178.125])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1G8fYD-0006Cm-AN
	for mip6@ietf.org; Thu, 03 Aug 2006 11:55:58 -0400
Received: (qmail 92595 invoked by uid 60001); 3 Aug 2006 15:55:57 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=Message-ID:Received:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type;
	b=OjBaQgPmRqsqtdaMskY7kc8JLYqX4sCe7j5O+RVqZ4G5jWFNkROdhjtrFsupEoDLS0YPbOYVfxisArFUE78LN3D18ZuyvT3iLLTKPAIqgfL8ixIHjbnDw0SQe4gY+JWdJQewPJ4WSV1BC218snQwDRrKeJMdrIgoz4t+HuHx8PM=
	; 
Message-ID: <20060803155557.92593.qmail@web60317.mail.yahoo.com>
Received: from [12.129.211.52] by web60317.mail.yahoo.com via HTTP;
	Thu, 03 Aug 2006 08:55:57 PDT
Date: Thu, 3 Aug 2006 08:55:57 -0700 (PDT)
From: Behcet Sarikaya <behcetsarikaya@yahoo.com>
Subject: Re: [Mip6] comments on AAA-HA-goals-02
To: Julien Bournelle <julien.bournelle@int-evry.fr>
In-Reply-To: <20060803142209.GA5650@ipv6-3.int-evry.fr>
MIME-Version: 1.0
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 140baa79ca42e6b0e2b4504291346186
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Behcet Sarikaya <sarikaya@ieee.org>
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1442386435=="
Errors-To: mip6-bounces@ietf.org

--===============1442386435==
Content-Type: multipart/alternative; boundary="0-954521769-1154620557=:92559"

--0-954521769-1154620557=:92559
Content-Type: text/plain; charset=us-ascii

Hi Julien,
  Can you please point to where we can find the details on the use of IKEv2 EAP authentication of the MN where HA is Pass-Through Authenticator?

Thanks,

--behcet

----- Original Message ----
From: Julien Bournelle <julien.bournelle@int-evry.fr>
To: Madjid Nakhjiri <mnakhjiri@huawei.com>
Cc: mip6@ietf.org
Sent: Thursday, August 3, 2006 9:22:09 AM
Subject: Re: [Mip6] comments on AAA-HA-goals-02

Hi madjid,

 let me try to respond to your mail though some terminology issues are more related to the
 draft-ietf-mip6-bootstrapping-ps draft.

 First of all, thanks for reading the document.

On Wed, Aug 02, 2006 at 05:07:27PM -0700, Madjid Nakhjiri wrote:

<snip>
> 
>  I am new to the MIP6 bootstrapping terminology, but not new to
> bootstrapping or AAA-MIP interactions. I just looked through the HA-AAA
> goals drafts. Thank you for a very well written draft that also provides a
> good summary of the split and integrated scenarios as well. 

 thanks,
 
> I do however
> find some the terminology confusing. I apologize if my questions have been
> discussed extensively on the mailing list. I would appreciate if the authors
> or other people can shed some light on some of the terminology or point me
> to the proper document to read, I have started going through the
> bootstrapping draft a bit as well, and am planning to see how MIP6-AAA
> interaction works. 
> 
> *        The way the terminology of Mobility service provider and Access
> service provider in the context of MIP6, which is layer 3 mobility, would be
> defined in my mind is that the MSP only provides MIP6 services, while the
> ASP provides access services, such as L2 access, QoS and other services
> (guessing IP connectivity/ DHCP and so on). 

 right

> The network MSA to me symbolizes
> the MSP-AAA server, while ASA symbolizes ASP-AAA server. 

 no, the MSA is administrative entity with whom the user has a contract
 and thus credentials. The MSP effectively provides the MIP6 service to
 the user. Thus the MSP may have to contact the MSA before providing the
 service. 

> 
> *        I see a hot spot provider or a 802.16d network without mobility
> support as an ASP, while a IP enabled cellular or a WiMAX network as a
> combination of ASP and MSP. To me assignment of HA falls into the MSP
> service category, not ASP service category (I just confirmed this in
> bootstrapping-ps section 7.1), so there are some statements in the draft as
> far as an  ASP assigning an HA and I don't think those are appropriate based
> on the terminology provided. 

 it depends if we are in the split or integrated scenario.
 In the split scenario, we don't have ASP/ASA, only MSP/MSA. So the user
 has an HA from the MSP.
 In the integrated scenario, if MSP=ASP, the user obtains an HA from the
 MSP/ASP. 


> 
> *        Then there is the concept of home versus visited domain. I am
> guessing "domain" to administrative domain (AAA domain). Traditionally AAA
> community is denoted as home and visited AAA servers, i.e. AAAH and AAAV,
> respectively. I just checked the bootstrapping-ps draft and that draft calls
> uses the term "serving" instead of "visited", but still provides a
> distinction between home versus serving MSP (MSPH and MSPS) and between home
> versus serving ASP (ASPH and ASPS). Having said this, I think if the group
> is going to great length to separate ASP/ MSP and ASA/MSA, it also needs to
> distinguish between the home versus visited domain for each of the
> authorizers. So that MSAH refers to AAA server within home MSP (MSP-H) and
> MSAV or MSAS (pick one) to AAA server within visited or serving MSP (MSP-V
> or MSP-S). The same goes for ASAH and ASAV. This means Serving MSA is not
> the same as serving ASA. It is not proper to equate the access service
> provider (ASP) with MSP-V the visited domain as it is implied in section
> 4.2: "Mobile Node requests a home agent to the Access Service Provider
> (ASP)". According to my understanding of the terminology of ASP, ASP has
> nothing to anything to do with HA assignment. I think this can be easily
> remedied by introducing MSAH and MSAS. Visited domain HA allocation can be
> formulated as "MN can request MSAH for an HA assignment within MSPS after
> authentication to MSAH and authorization of mobility service by the
> MSAH/MSAS to MN".

 maybe my explanation below will answer to this paragraph ?

> *        The same goes for another sentence in the same section saying "..
> Mobile Node can specify if it wants a home agent provided by the visited
> domain (ASP) or by the home domain (ASA)", which seems to be mixing
> (mobility and access service), (home and visited), (provider and authorizer)
> all in the same sentence!!

 yes, that can be confusing. 

> 
> *        The other comment along the same line is about section 4.1, where
> it is stated a pool of HA s can rely on the home EAP server (I am guessing
> EAP server belonging to MSA-H, since this is split scenario) for
> authentication. Here it is stated "It allows the roaming mobility case in
> which the MN obtains the mobility service in a different administrative
> domain (MSP !=MSA). Here it seems that it is implied HA is part of MSP
> function (appropriately), however, I am not sure if MSP and MSA can imply
> two administrative domains, to me administrative domain implies AAA domain,
> so one would be MSA-H and another MSA-V, so an HA could be authorized within
> MSA-V based on authentication to MSA-H and authorization by MSA-H.

 MSP has its own AAA server. MSA is the AAA server of the MN. 
 Does it respond to your comment ?


> 
> *        I also have an issue with the usage of term NAS in next to last
> paragraph of section 3. NAS is really an access service agent (as the name
> implies) not a mobility service agent. NAS performs many functions beyond
> the AAA client function, which brings up two issues. 1) the sentence ".HA,
> that can be seen as Network Access Server for MIP6", is only providing
> confusion in this context, you may say that HA can be seen as Network
> mobility server if you want but in a draft that has ASP and MSP everywhere.

 ok.

> 2) in the goals sections (5.1/ 5.2) , it is not mentioned anywhere that the
> HA MUST act as a AAA client, is this a non-requirement, or is it implicitly
> understood?  Especially G2.2 seems to imply this.

 I think it is implicitly understood. Do you think we should add a
 statement on this ?

> 
> *        In 5.4 why is it a "MUST" for HA to be an EAP pass-through
> authenticator? As long as HA receives its information from the AAA server in
> a secure fashion and both HA and AAA can identify the MN and its EAP session
> uniquely, there is no reason for allocating HA and EAP pass-through EAP
> authenticator in the same box.

 hmmm, the HA acts as a AAA client and MN uses IKEv2 with EAP to be
 authenticated. So the HA MUST act as an EAP pass-through authenticator.

 Am I missing something ? do you think we should rephrase this ?

> 
> *        For section 4.2, Integrated scenario, I see that NAS gets MIP6 conf
> parameters from the AAAH, how does the HA receives the information it needs?

 In the integrated scenario based on DHCPv6, the MN gets HA info through
 DHCP. Then we fall in the split scenario and the MN uses IKEv2 with the
 HA. 


 Julien Bournelle

> Thank you for your attention,
> 
>  
> 
> Madjid Nakhjiri
> 
>  
> 

> _______________________________________________
> 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





--0-954521769-1154620557=:92559
Content-Type: text/html; charset=us-ascii

<html><head><style type="text/css"><!-- DIV {margin:0px} --></style></head><body><div style="font-family:courier, monaco, monospace, sans-serif;font-size:12pt"><div style="font-family: courier,monaco,monospace,sans-serif; font-size: 12pt;">Hi Julien,<br>&nbsp; Can you please point to where we can find the details on the use of IKEv2 EAP authentication of the MN where HA is Pass-Through Authenticator?<br><br>Thanks,<br><br>--behcet<br><br><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;">----- Original Message ----<br>From: Julien Bournelle &lt;julien.bournelle@int-evry.fr&gt;<br>To: Madjid Nakhjiri &lt;mnakhjiri@huawei.com&gt;<br>Cc: mip6@ietf.org<br>Sent: Thursday, August 3, 2006 9:22:09 AM<br>Subject: Re: [Mip6] comments on AAA-HA-goals-02<br><br><div>Hi madjid,<br><br> let me try to respond to your mail though some terminology issues are more related to the<br> draft-ietf-mip6-bootstrapping-ps draft.<br><br> First of all, thanks for reading
 the document.<br><br>On Wed, Aug 02, 2006 at 05:07:27PM -0700, Madjid Nakhjiri wrote:<br><br>&lt;snip&gt;<br>&gt; <br>&gt;&nbsp;&nbsp;I am new to the MIP6 bootstrapping terminology, but not new to<br>&gt; bootstrapping or AAA-MIP interactions. I just looked through the HA-AAA<br>&gt; goals drafts. Thank you for a very well written draft that also provides a<br>&gt; good summary of the split and integrated scenarios as well. <br><br> thanks,<br> <br>&gt; I do however<br>&gt; find some the terminology confusing. I apologize if my questions have been<br>&gt; discussed extensively on the mailing list. I would appreciate if the authors<br>&gt; or other people can shed some light on some of the terminology or point me<br>&gt; to the proper document to read, I have started going through the<br>&gt; bootstrapping draft a bit as well, and am planning to see how MIP6-AAA<br>&gt; interaction works. <br>&gt; <br>&gt; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;The way the
 terminology of Mobility service provider and Access<br>&gt; service provider in the context of MIP6, which is layer 3 mobility, would be<br>&gt; defined in my mind is that the MSP only provides MIP6 services, while the<br>&gt; ASP provides access services, such as L2 access, QoS and other services<br>&gt; (guessing IP connectivity/ DHCP and so on). <br><br> right<br><br>&gt; The network MSA to me symbolizes<br>&gt; the MSP-AAA server, while ASA symbolizes ASP-AAA server. <br><br> no, the MSA is administrative entity with whom the user has a contract<br> and thus credentials. The MSP effectively provides the MIP6 service to<br> the user. Thus the MSP may have to contact the MSA before providing the<br> service. <br><br>&gt; <br>&gt; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;I see a hot spot provider or a 802.16d network without mobility<br>&gt; support as an ASP, while a IP enabled cellular or a WiMAX network as a<br>&gt; combination of ASP and MSP. To me assignment
 of HA falls into the MSP<br>&gt; service category, not ASP service category (I just confirmed this in<br>&gt; bootstrapping-ps section 7.1), so there are some statements in the draft as<br>&gt; far as an&nbsp;&nbsp;ASP assigning an HA and I don't think those are appropriate based<br>&gt; on the terminology provided. <br><br> it depends if we are in the split or integrated scenario.<br> In the split scenario, we don't have ASP/ASA, only MSP/MSA. So the user<br> has an HA from the MSP.<br> In the integrated scenario, if MSP=ASP, the user obtains an HA from the<br> MSP/ASP. <br><br><br>&gt; <br>&gt; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Then there is the concept of home versus visited domain. I am<br>&gt; guessing "domain" to administrative domain (AAA domain). Traditionally AAA<br>&gt; community is denoted as home and visited AAA servers, i.e. AAAH and AAAV,<br>&gt; respectively. I just checked the bootstrapping-ps draft and that draft calls<br>&gt; uses the term
 "serving" instead of "visited", but still provides a<br>&gt; distinction between home versus serving MSP (MSPH and MSPS) and between home<br>&gt; versus serving ASP (ASPH and ASPS). Having said this, I think if the group<br>&gt; is going to great length to separate ASP/ MSP and ASA/MSA, it also needs to<br>&gt; distinguish between the home versus visited domain for each of the<br>&gt; authorizers. So that MSAH refers to AAA server within home MSP (MSP-H) and<br>&gt; MSAV or MSAS (pick one) to AAA server within visited or serving MSP (MSP-V<br>&gt; or MSP-S). The same goes for ASAH and ASAV. This means Serving MSA is not<br>&gt; the same as serving ASA. It is not proper to equate the access service<br>&gt; provider (ASP) with MSP-V the visited domain as it is implied in section<br>&gt; 4.2: "Mobile Node requests a home agent to the Access Service Provider<br>&gt; (ASP)". According to my understanding of the terminology of ASP, ASP has<br>&gt; nothing to anything to do with
 HA assignment. I think this can be easily<br>&gt; remedied by introducing MSAH and MSAS. Visited domain HA allocation can be<br>&gt; formulated as "MN can request MSAH for an HA assignment within MSPS after<br>&gt; authentication to MSAH and authorization of mobility service by the<br>&gt; MSAH/MSAS to MN".<br><br> maybe my explanation below will answer to this paragraph ?<br><br>&gt; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;The same goes for another sentence in the same section saying "..<br>&gt; Mobile Node can specify if it wants a home agent provided by the visited<br>&gt; domain (ASP) or by the home domain (ASA)", which seems to be mixing<br>&gt; (mobility and access service), (home and visited), (provider and authorizer)<br>&gt; all in the same sentence!!<br><br> yes, that can be confusing. <br><br>&gt; <br>&gt; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;The other comment along the same line is about section 4.1, where<br>&gt; it is stated a pool of HA
 s can rely on the home EAP server (I am guessing<br>&gt; EAP server belonging to MSA-H, since this is split scenario) for<br>&gt; authentication. Here it is stated "It allows the roaming mobility case in<br>&gt; which the MN obtains the mobility service in a different administrative<br>&gt; domain (MSP !=MSA). Here it seems that it is implied HA is part of MSP<br>&gt; function (appropriately), however, I am not sure if MSP and MSA can imply<br>&gt; two administrative domains, to me administrative domain implies AAA domain,<br>&gt; so one would be MSA-H and another MSA-V, so an HA could be authorized within<br>&gt; MSA-V based on authentication to MSA-H and authorization by MSA-H.<br><br> MSP has its own AAA server. MSA is the AAA server of the MN. <br> Does it respond to your comment ?<br><br><br>&gt; <br>&gt; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;I also have an issue with the usage of term NAS in next to last<br>&gt; paragraph of section 3. NAS is really an
 access service agent (as the name<br>&gt; implies) not a mobility service agent. NAS performs many functions beyond<br>&gt; the AAA client function, which brings up two issues. 1) the sentence ".HA,<br>&gt; that can be seen as Network Access Server for MIP6", is only providing<br>&gt; confusion in this context, you may say that HA can be seen as Network<br>&gt; mobility server if you want but in a draft that has ASP and MSP everywhere.<br><br> ok.<br><br>&gt; 2) in the goals sections (5.1/ 5.2) , it is not mentioned anywhere that the<br>&gt; HA MUST act as a AAA client, is this a non-requirement, or is it implicitly<br>&gt; understood?&nbsp;&nbsp;Especially G2.2 seems to imply this.<br><br> I think it is implicitly understood. Do you think we should add a<br> statement on this ?<br><br>&gt; <br>&gt; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;In 5.4 why is it a "MUST" for HA to be an EAP pass-through<br>&gt; authenticator? As long as HA receives its information from
 the AAA server in<br>&gt; a secure fashion and both HA and AAA can identify the MN and its EAP session<br>&gt; uniquely, there is no reason for allocating HA and EAP pass-through EAP<br>&gt; authenticator in the same box.<br><br> hmmm, the HA acts as a AAA client and MN uses IKEv2 with EAP to be<br> authenticated. So the HA MUST act as an EAP pass-through authenticator.<br><br> Am I missing something ? do you think we should rephrase this ?<br><br>&gt; <br>&gt; *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;For section 4.2, Integrated scenario, I see that NAS gets MIP6 conf<br>&gt; parameters from the AAAH, how does the HA receives the information it needs?<br><br> In the integrated scenario based on DHCPv6, the MN gets HA info through<br> DHCP. Then we fall in the split scenario and the MN uses IKEv2 with the<br> HA. <br><br><br> Julien Bournelle<br><br>&gt; Thank you for your attention,<br>&gt; <br>&gt;&nbsp;&nbsp;<br>&gt; <br>&gt; Madjid Nakhjiri<br>&gt;
 <br>&gt;&nbsp;&nbsp;<br>&gt; <br><br>&gt; _______________________________________________<br>&gt; Mip6 mailing list<br>&gt; Mip6@ietf.org<br>&gt; <a target="_blank" href="https://www1.ietf.org/mailman/listinfo/mip6">https://www1.ietf.org/mailman/listinfo/mip6</a><br><br><br>-- <br>julien.bournelle at int-evry.fr<br><br>_______________________________________________<br>Mip6 mailing list<br>Mip6@ietf.org<br><a target="_blank" href="https://www1.ietf.org/mailman/listinfo/mip6">https://www1.ietf.org/mailman/listinfo/mip6</a><br></div></div><br></div></div></body></html>
--0-954521769-1154620557=:92559--


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

--===============1442386435==--




From mip6-bounces@ietf.org Thu Aug 03 12:04:47 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G8fgi-0005OT-Ar; Thu, 03 Aug 2006 12:04:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G8fgg-0005OO-VE
	for mip6@ietf.org; Thu, 03 Aug 2006 12:04:42 -0400
Received: from smtp2.int-evry.fr ([157.159.10.45])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G8fgg-00076Y-AE
	for mip6@ietf.org; Thu, 03 Aug 2006 12:04:42 -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 15DFE2FEA9;
	Thu,  3 Aug 2006 18:04:40 +0200 (CEST)
Received: from jb by ipv6-3.int-evry.fr with local (Exim 4.52)
	id 1G8fiu-0001Zn-Sx; Thu, 03 Aug 2006 18:07:00 +0200
Date: Thu, 3 Aug 2006 18:07:00 +0200
From: Julien Bournelle <julien.bournelle@int-evry.fr>
To: Behcet Sarikaya <sarikaya@ieee.org>
Subject: Re: [Mip6] comments on AAA-HA-goals-02
Message-ID: <20060803160700.GA6054@ipv6-3.int-evry.fr>
References: <20060803142209.GA5650@ipv6-3.int-evry.fr>
	<20060803155557.92593.qmail@web60317.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20060803155557.92593.qmail@web60317.mail.yahoo.com>
User-Agent: Mutt/1.5.9i
X-INT-MailScanner-Information: Please contact the ISP for more information
X-INT-MailScanner: Found to be clean
X-INT-MailScanner-MCPCheck: 
X-INT-MailScanner-SpamCheck: 
X-MailScanner-From: jb@int-evry.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 311e798ce51dbeacf5cdfcc8e9fda21b
Cc: Julien Bournelle <julien.bournelle@int-evry.fr>, mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi Behcet,

On Thu, Aug 03, 2006 at 08:55:57AM -0700, Behcet Sarikaya wrote:
> Hi Julien,
>   Can you please point to where we can find the details on the use of IKEv2 EAP authentication of the MN where HA is Pass-Through Authenticator?

 you can take a look at draft-ietf-dime-mip6-split-00.txt.

 regards,

 Julien

> 
> Thanks,
> 
> --behcet
> 
> ----- Original Message ----
> From: Julien Bournelle <julien.bournelle@int-evry.fr>
> To: Madjid Nakhjiri <mnakhjiri@huawei.com>
> Cc: mip6@ietf.org
> Sent: Thursday, August 3, 2006 9:22:09 AM
> Subject: Re: [Mip6] comments on AAA-HA-goals-02
> 
> Hi madjid,
> 
>  let me try to respond to your mail though some terminology issues are more related to the
>  draft-ietf-mip6-bootstrapping-ps draft.
> 
>  First of all, thanks for reading the document.
> 
> On Wed, Aug 02, 2006 at 05:07:27PM -0700, Madjid Nakhjiri wrote:
> 
> <snip>
> > 
> >  I am new to the MIP6 bootstrapping terminology, but not new to
> > bootstrapping or AAA-MIP interactions. I just looked through the HA-AAA
> > goals drafts. Thank you for a very well written draft that also provides a
> > good summary of the split and integrated scenarios as well. 
> 
>  thanks,
>  
> > I do however
> > find some the terminology confusing. I apologize if my questions have been
> > discussed extensively on the mailing list. I would appreciate if the authors
> > or other people can shed some light on some of the terminology or point me
> > to the proper document to read, I have started going through the
> > bootstrapping draft a bit as well, and am planning to see how MIP6-AAA
> > interaction works. 
> > 
> > *        The way the terminology of Mobility service provider and Access
> > service provider in the context of MIP6, which is layer 3 mobility, would be
> > defined in my mind is that the MSP only provides MIP6 services, while the
> > ASP provides access services, such as L2 access, QoS and other services
> > (guessing IP connectivity/ DHCP and so on). 
> 
>  right
> 
> > The network MSA to me symbolizes
> > the MSP-AAA server, while ASA symbolizes ASP-AAA server. 
> 
>  no, the MSA is administrative entity with whom the user has a contract
>  and thus credentials. The MSP effectively provides the MIP6 service to
>  the user. Thus the MSP may have to contact the MSA before providing the
>  service. 
> 
> > 
> > *        I see a hot spot provider or a 802.16d network without mobility
> > support as an ASP, while a IP enabled cellular or a WiMAX network as a
> > combination of ASP and MSP. To me assignment of HA falls into the MSP
> > service category, not ASP service category (I just confirmed this in
> > bootstrapping-ps section 7.1), so there are some statements in the draft as
> > far as an  ASP assigning an HA and I don't think those are appropriate based
> > on the terminology provided. 
> 
>  it depends if we are in the split or integrated scenario.
>  In the split scenario, we don't have ASP/ASA, only MSP/MSA. So the user
>  has an HA from the MSP.
>  In the integrated scenario, if MSP=ASP, the user obtains an HA from the
>  MSP/ASP. 
> 
> 
> > 
> > *        Then there is the concept of home versus visited domain. I am
> > guessing "domain" to administrative domain (AAA domain). Traditionally AAA
> > community is denoted as home and visited AAA servers, i.e. AAAH and AAAV,
> > respectively. I just checked the bootstrapping-ps draft and that draft calls
> > uses the term "serving" instead of "visited", but still provides a
> > distinction between home versus serving MSP (MSPH and MSPS) and between home
> > versus serving ASP (ASPH and ASPS). Having said this, I think if the group
> > is going to great length to separate ASP/ MSP and ASA/MSA, it also needs to
> > distinguish between the home versus visited domain for each of the
> > authorizers. So that MSAH refers to AAA server within home MSP (MSP-H) and
> > MSAV or MSAS (pick one) to AAA server within visited or serving MSP (MSP-V
> > or MSP-S). The same goes for ASAH and ASAV. This means Serving MSA is not
> > the same as serving ASA. It is not proper to equate the access service
> > provider (ASP) with MSP-V the visited domain as it is implied in section
> > 4.2: "Mobile Node requests a home agent to the Access Service Provider
> > (ASP)". According to my understanding of the terminology of ASP, ASP has
> > nothing to anything to do with HA assignment. I think this can be easily
> > remedied by introducing MSAH and MSAS. Visited domain HA allocation can be
> > formulated as "MN can request MSAH for an HA assignment within MSPS after
> > authentication to MSAH and authorization of mobility service by the
> > MSAH/MSAS to MN".
> 
>  maybe my explanation below will answer to this paragraph ?
> 
> > *        The same goes for another sentence in the same section saying "..
> > Mobile Node can specify if it wants a home agent provided by the visited
> > domain (ASP) or by the home domain (ASA)", which seems to be mixing
> > (mobility and access service), (home and visited), (provider and authorizer)
> > all in the same sentence!!
> 
>  yes, that can be confusing. 
> 
> > 
> > *        The other comment along the same line is about section 4.1, where
> > it is stated a pool of HA s can rely on the home EAP server (I am guessing
> > EAP server belonging to MSA-H, since this is split scenario) for
> > authentication. Here it is stated "It allows the roaming mobility case in
> > which the MN obtains the mobility service in a different administrative
> > domain (MSP !=MSA). Here it seems that it is implied HA is part of MSP
> > function (appropriately), however, I am not sure if MSP and MSA can imply
> > two administrative domains, to me administrative domain implies AAA domain,
> > so one would be MSA-H and another MSA-V, so an HA could be authorized within
> > MSA-V based on authentication to MSA-H and authorization by MSA-H.
> 
>  MSP has its own AAA server. MSA is the AAA server of the MN. 
>  Does it respond to your comment ?
> 
> 
> > 
> > *        I also have an issue with the usage of term NAS in next to last
> > paragraph of section 3. NAS is really an access service agent (as the name
> > implies) not a mobility service agent. NAS performs many functions beyond
> > the AAA client function, which brings up two issues. 1) the sentence ".HA,
> > that can be seen as Network Access Server for MIP6", is only providing
> > confusion in this context, you may say that HA can be seen as Network
> > mobility server if you want but in a draft that has ASP and MSP everywhere.
> 
>  ok.
> 
> > 2) in the goals sections (5.1/ 5.2) , it is not mentioned anywhere that the
> > HA MUST act as a AAA client, is this a non-requirement, or is it implicitly
> > understood?  Especially G2.2 seems to imply this.
> 
>  I think it is implicitly understood. Do you think we should add a
>  statement on this ?
> 
> > 
> > *        In 5.4 why is it a "MUST" for HA to be an EAP pass-through
> > authenticator? As long as HA receives its information from the AAA server in
> > a secure fashion and both HA and AAA can identify the MN and its EAP session
> > uniquely, there is no reason for allocating HA and EAP pass-through EAP
> > authenticator in the same box.
> 
>  hmmm, the HA acts as a AAA client and MN uses IKEv2 with EAP to be
>  authenticated. So the HA MUST act as an EAP pass-through authenticator.
> 
>  Am I missing something ? do you think we should rephrase this ?
> 
> > 
> > *        For section 4.2, Integrated scenario, I see that NAS gets MIP6 conf
> > parameters from the AAAH, how does the HA receives the information it needs?
> 
>  In the integrated scenario based on DHCPv6, the MN gets HA info through
>  DHCP. Then we fall in the split scenario and the MN uses IKEv2 with the
>  HA. 
> 
> 
>  Julien Bournelle
> 
> > Thank you for your attention,
> > 
> >  
> > 
> > Madjid Nakhjiri
> > 
> >  
> > 
> 
> > _______________________________________________
> > 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
> 
> 
> 
> 

-- 
julien.bournelle at int-evry.fr

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



From mip6-bounces@ietf.org Thu Aug 03 15:28:49 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G8is6-0003Mg-6s; Thu, 03 Aug 2006 15:28:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G8is4-0003Ma-Mq
	for mip6@ietf.org; Thu, 03 Aug 2006 15:28:40 -0400
Received: from mgw-ext14.nokia.com ([131.228.20.173])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G8is2-0004Gi-4E
	for mip6@ietf.org; Thu, 03 Aug 2006 15:28:40 -0400
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
	by mgw-ext14.nokia.com (Switch-3.1.8/Switch-3.1.7) with ESMTP id
	k73JSa06025526; Thu, 3 Aug 2006 22:28:36 +0300
Received: from daebh101.NOE.Nokia.com ([10.241.35.111]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 3 Aug 2006 22:28:36 +0300
Received: from daebe101.NOE.Nokia.com ([10.241.35.113]) by
	daebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 3 Aug 2006 14:28:33 -0500
Received: from 172.19.244.182 ([172.19.244.182]) by daebe101.NOE.Nokia.com
	([10.241.35.113]) with Microsoft Exchange Server HTTP-DAV ; 
	Thu,  3 Aug 2006 19:28:34 +0000
User-Agent: Microsoft-Entourage/11.2.5.060620
Date: Thu, 03 Aug 2006 14:28:45 -0500
Subject: Re: [Mip6] Recommendation for bootstrapping using DHCPv6
From: Basavaraj Patil <basavaraj.patil@nokia.com>
To: ext Alper Yegin <alper.yegin@yegin.org>, <mip6@ietf.org>
Message-ID: <C0F7B89D.20864%basavaraj.patil@nokia.com>
Thread-Topic: [Mip6] Recommendation for bootstrapping using DHCPv6
Thread-Index: Aca1oaIQ4K1FzyGUEduPhAARJNUNiAA2bJdQAC3tKR8=
In-Reply-To: <0MKoyl-1G8OWs1hGU-0005aB@mrelay.perfora.net>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 03 Aug 2006 19:28:33.0874 (UTC)
	FILETIME=[026FE320:01C6B733]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ff03b0075c3fc728d7d60a15b4ee1ad2
Cc: 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org


Alper,

Inline:

On 8/2/06 4:45 PM, "ext Alper Yegin" <alper.yegin@yegin.org> wrote:

> Hi Raj,
> 
> "Having the options specified in a stand-along document will not add much
> value."
> 
> As we have been stating, draft-jang-mip6-hiopt-00.txt also has a use that
> does not tie into the RADIUS-driven details -- the use where DHCP server can
> be manually configured and has nothing to do with the AAA.

But why do you believe that the WG I-D which is using DHCP is RADIUS driven
only and nothing else? I mean it could just as well be used for the case
where the bootstrapping information is manually configured in the DHCP
server. What is needed are the DHCP options and the fact that the bootstrap
parameters are available in the DHCP server either as a result of some AAA
messages or manual configuration does not matter.

> 
> Your above statement misses this point.
> 
> Besides, while there is a standalone use for draft-jang-mip6-hiopt-00.txt,

What is the standalone use of draft-jang? The WG I-D needs to specify the
DHCP options anyway. Why would that not be sufficient for any deployment
scenario that you have in mind?

> there is none for the RADIUS and Diameter specs we expect to document
> individually. Should we also merge those AAA documents with the others?

Are you refering to the Radius/Diameter mechanisms for obtaining the
bootstrap parameters and storing them in the DHCP server? You could specify
those mechanisms independently of the fact that there is a specification
which explains how DHCP is used for bootstrapping and the DHCP options to
carry the bootstrap parameters between the MS and the DHCP server. So I
don't expect that those drafts also be merged with the current spec.

> 
> Also, I'm not sure what specific concern you are raising with respect to the
> quoted text below.

The concern that I have is the fact that the I-D specifies the DHCP options
for boostrapping. The bootstrap parameters are somehow stored in the DHCP
server. The I-D is basically saying that how the parameters get into the
DHCP server are not in scope here except giving an example that manual
configuration or AAA can be used. So it is incomplete and unusable. What you
say above is that there will be additional I-Ds coming to specify how that
is done. The current WG integrated scenario with DHCPv6 I-D has more details
and explains at least how AAA is used. I guess manual configuration is
pretty straightforward and does not need secification. But in the case when
the MS is roaming and attached to some visited network, how does it
bootstrap with DHCP? My concern is the fact that the I-D is incomplete and
it simply sweeps the issue under the mat by saying it is out of scope.

-Raj

> 
> Alper
> 
> 
> 
>> -----Original Message-----
>> From: Basavaraj Patil [mailto:basavaraj.patil@nokia.com]
>> Sent: Tuesday, August 01, 2006 12:35 PM
>> To: mip6@ietf.org
>> Subject: [Mip6] Recommendation for bootstrapping using DHCPv6
>> 
>> 
>> Alper/Kuntal et al,
>> 
>> I have reviewed the drafts:
>> 1. Problem Statement for bootstrapping Mobile IPv6
>>    (draft-ietf-mip6-bootstrap-ps-05)
>> 2. MIP6-bootstrapping via DHCPv6 for the Integrated Scenario
>>    (draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt)
>> 
>> and
>> 3. DHCP Option for Home Information Discovery in MIPv6
>>    (draft-jang-mip6-hiopt-00.txt)
>> 
>> My conclusion from the review is that the integrated scenario
>> bootstrapping via DHCPv6 is covering the cases when DHCP is the
>> preferred method by MNs.
>> 
>> The WG I-D draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt in
>> sections 3.5 and 3.8 explain how DHCP would work. Having the options
>> specified in a stand-along document will not add much value. I am also
>> concerned about the fact in draft-jang which states that:
>> "
>>    The availability of the requested information depends on the DHCP
>>    server having prior knowledge or dynamically discovering it.  While
>>    the specific details are outside the scope of this document, use of
>>    static tables and AAA-assisted discovery are possible options
>> "
>> 
>> Another concern that I have w.r.t bootstrapping with DHCPv6 is that
>> instead of having DHCP provide the HoA or the HL prefix to the MS, it
>> is better to only provide the address of an HA (or list of HAs) and
>> let the MS send a BU with unspecified address and obtain an address
>> from the HA. This will simplify bootstrapping and also reduce the
>> interaction between DHCP and the HA from an address management
>> perspective. Hence you may want to reconsider the DHCP option which
>> carry the HL Prefix or the HoA for the MS.
>> 
>> I recommend that the DHCP option specified in draft-jang be
>> incorporated into the WG I-D and progressed on standards track. As a
>> result the WG will have a mechanism for bootstrapping MIP6 with DHCP
>> that also includes the DHCP options in a single I-D.
>> 
>> -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 Thu Aug 03 19:27:26 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G8mb0-0004ZU-Cr; Thu, 03 Aug 2006 19:27:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G8may-0004ZO-VK
	for mip6@ietf.org; Thu, 03 Aug 2006 19:27:16 -0400
Received: from mout.perfora.net ([217.160.230.41])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G8may-0004ZI-KE
	for mip6@ietf.org; Thu, 03 Aug 2006 19:27:16 -0400
Received: from [85.97.7.241] (helo=IBM52A5038A94F)
	by mrelay.perfora.net (node=mrelayus1) with ESMTP (Nemesis),
	id 0MKp2t-1G8mau14ih-0004IW; Thu, 03 Aug 2006 19:27:15 -0400
From: "Alper Yegin" <alper.yegin@yegin.org>
To: "'Basavaraj Patil'" <basavaraj.patil@nokia.com>,
	<mip6@ietf.org>
Subject: RE: [Mip6] Recommendation for bootstrapping using DHCPv6
Date: Fri, 4 Aug 2006 02:27:07 +0300
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
In-Reply-To: <C0F7B89D.20864%basavaraj.patil@nokia.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
Thread-Index: Aca1oaIQ4K1FzyGUEduPhAARJNUNiAA2bJdQAC3tKR8AB7hywA==
Message-ID: <0MKp2t-1G8mau14ih-0004IW@mrelay.perfora.net>
X-Provags-ID: perfora.net abuse@perfora.net
	login:abf7a4bb310ea4dfc9b6841113e2970f
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 202a3ece0492a8c7e7c8672d5214398f
Cc: 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi Raj,

> > "Having the options specified in a stand-along document will not add
> much
> > value."
> >
> > As we have been stating, draft-jang-mip6-hiopt-00.txt also has a use
> that
> > does not tie into the RADIUS-driven details -- the use where DHCP server
> can
> > be manually configured and has nothing to do with the AAA.
> 
> But why do you believe that the WG I-D which is using DHCP is RADIUS
> driven
> only and nothing else? 

AAA is integral to the current solutions designed by the MIP6 WG for MIP6
bootstrapping. 

> I mean it could just as well be used for the case
> where the bootstrapping information is manually configured in the DHCP
> server. What is needed are the DHCP options and the fact that the
> bootstrap
> parameters are available in the DHCP server either as a result of some AAA
> messages or manual configuration does not matter.

Yes, this is exactly what the draft-jang is saying.


> > Your above statement misses this point.
> >
> > Besides, while there is a standalone use for draft-jang-mip6-hiopt-
> 00.txt,
> 
> What is the standalone use of draft-jang? 

Standalone use is the one that does not require all that AAA plumbing. For
example, when you manually configure the DHCP servers with the MIP6
information. 


> The WG I-D needs to specify the
> DHCP options anyway. Why would that not be sufficient for any deployment
> scenario that you have in mind?

I think there is a misunderstanding. I was not saying that.


> > there is none for the RADIUS and Diameter specs we expect to document
> > individually. Should we also merge those AAA documents with the others?
> 
> Are you refering to the Radius/Diameter mechanisms for obtaining the
> bootstrap parameters and storing them in the DHCP server? You could
> specify
> those mechanisms independently of the fact that there is a specification
> which explains how DHCP is used for bootstrapping and the DHCP options to
> carry the bootstrap parameters between the MS and the DHCP server. So I
> don't expect that those drafts also be merged with the current spec.


You misunderstood me. Let me re-iterate what I had described on the list
earlier:

- The integrated bootstrapping solution depends on a number of protocol
design work (1. DHCP options for HA discovery, 2. RADIUS attributes for HA
discovery, 3. Diameter AVPs for HA discovery, 4. IKEv2 for HoA
configuration, 5. RADIUS attributes for MIP6 authentication, 6. Diameter
AVPs for MIP6 authentication) and description (7) of how all such protocols
plumb together to yield so-called "MIP6 bootstrapping." 

Now, item 7 is described in
draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt. All the others are
currently described in separate documents, and that makes sense. Asking for
1 and 7 be merged does not make sense. If it did, my questions was, why not
merge the others as well. Do you see my point?

> >
> > Also, I'm not sure what specific concern you are raising with respect to
> the
> > quoted text below.
> 
> The concern that I have is the fact that the I-D specifies the DHCP
> options
> for boostrapping. The bootstrap parameters are somehow stored in the DHCP
> server. The I-D is basically saying that how the parameters get into the
> DHCP server are not in scope here except giving an example that manual
> configuration or AAA can be used. So it is incomplete and unusable. 


With the same token, documents 2..6 are also incomplete. Even 7 is
incomplete. It is the modular combination of these various protocol work
that makes a complete picture, no single one can make.


> What
> you
> say above is that there will be additional I-Ds coming to specify how that
> is done. The current WG integrated scenario with DHCPv6 I-D has more
> details
> and explains at least how AAA is used. I guess manual configuration is
> pretty straightforward and does not need secification. But in the case
> when
> the MS is roaming and attached to some visited network, how does it
> bootstrap with DHCP? My concern is the fact that the I-D is incomplete and
> it simply sweeps the issue under the mat by saying it is out of scope.

Alper





> 
> -Raj
> 
> >
> > Alper
> >
> >
> >
> >> -----Original Message-----
> >> From: Basavaraj Patil [mailto:basavaraj.patil@nokia.com]
> >> Sent: Tuesday, August 01, 2006 12:35 PM
> >> To: mip6@ietf.org
> >> Subject: [Mip6] Recommendation for bootstrapping using DHCPv6
> >>
> >>
> >> Alper/Kuntal et al,
> >>
> >> I have reviewed the drafts:
> >> 1. Problem Statement for bootstrapping Mobile IPv6
> >>    (draft-ietf-mip6-bootstrap-ps-05)
> >> 2. MIP6-bootstrapping via DHCPv6 for the Integrated Scenario
> >>    (draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt)
> >>
> >> and
> >> 3. DHCP Option for Home Information Discovery in MIPv6
> >>    (draft-jang-mip6-hiopt-00.txt)
> >>
> >> My conclusion from the review is that the integrated scenario
> >> bootstrapping via DHCPv6 is covering the cases when DHCP is the
> >> preferred method by MNs.
> >>
> >> The WG I-D draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt in
> >> sections 3.5 and 3.8 explain how DHCP would work. Having the options
> >> specified in a stand-along document will not add much value. I am also
> >> concerned about the fact in draft-jang which states that:
> >> "
> >>    The availability of the requested information depends on the DHCP
> >>    server having prior knowledge or dynamically discovering it.  While
> >>    the specific details are outside the scope of this document, use of
> >>    static tables and AAA-assisted discovery are possible options
> >> "
> >>
> >> Another concern that I have w.r.t bootstrapping with DHCPv6 is that
> >> instead of having DHCP provide the HoA or the HL prefix to the MS, it
> >> is better to only provide the address of an HA (or list of HAs) and
> >> let the MS send a BU with unspecified address and obtain an address
> >> from the HA. This will simplify bootstrapping and also reduce the
> >> interaction between DHCP and the HA from an address management
> >> perspective. Hence you may want to reconsider the DHCP option which
> >> carry the HL Prefix or the HoA for the MS.
> >>
> >> I recommend that the DHCP option specified in draft-jang be
> >> incorporated into the WG I-D and progressed on standards track. As a
> >> result the WG will have a mechanism for bootstrapping MIP6 with DHCP
> >> that also includes the DHCP options in a single I-D.
> >>
> >> -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 Thu Aug 03 19:37:57 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G8mlI-0007kl-UE; Thu, 03 Aug 2006 19:37:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G8mlH-0007kg-6m
	for mip6@ietf.org; Thu, 03 Aug 2006 19:37:55 -0400
Received: from usaga01-in.huawei.com ([12.129.211.51])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G8mlE-0005Gc-JD
	for mip6@ietf.org; Thu, 03 Aug 2006 19:37:55 -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 <0J3G00FLY45UQS@usaga01-in.huawei.com> for
	mip6@ietf.org; Thu, 03 Aug 2006 16:34:43 -0700 (PDT)
Received: from Nakhjiri73701
	(c-24-17-254-79.hsd1.mn.comcast.net [24.17.254.79]) by
	usaga01-in.huawei.com
	(iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar  3 2004))
	with ESMTPA id <0J3G0009H45QXE@usaga01-in.huawei.com> for mip6@ietf.org;
	Thu, 03 Aug 2006 16:34:42 -0700 (PDT)
Date: Thu, 03 Aug 2006 16:37:44 -0700
From: Madjid Nakhjiri <mnakhjiri@huawei.com>
Subject: RE: [Mip6] comments on AAA-HA-goals-02
In-reply-to: <20060803142209.GA5650@ipv6-3.int-evry.fr>
To: 'Julien Bournelle' <julien.bournelle@int-evry.fr>
Message-id: <003101c6b755$d1b6a930$03fda8c0@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Thread-index: Aca3CGd11m02bP4oRNGNwxKPbXmqTAASL88Q
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 16c9da4896bf5539ae3547c6c25f06a0
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi Julien, 

Thanks for the quick reply. 


-----Original Message-----
From: Julien Bournelle [mailto:julien.bournelle@int-evry.fr] 
Sent: Thursday, August 03, 2006 7:22 AM
To: Madjid Nakhjiri
Cc: mip6@ietf.org
Subject: Re: [Mip6] comments on AAA-HA-goals-02

Hi madjid,

 let me try to respond to your mail though some terminology issues are more
related to the
 draft-ietf-mip6-bootstrapping-ps draft.

Madjid>>I actually find the terminology in the bootstrapping draft more
consistent. 

> The network MSA to me symbolizes
> the MSP-AAA server, while ASA symbolizes ASP-AAA server. 

 no, the MSA is administrative entity with whom the user has a contract
 and thus credentials. The MSP effectively provides the MIP6 service to
 the user. Thus the MSP may have to contact the MSA before providing the
 service. 

Madjid>>Well, you are saying MSA has a contract with the user and has her
credentials. To me it translates to a home AAA server or authentication
server for the MSP. I think we need to make the distinction between home MSA
and visited MSA.
Also, MSP is a service provider, but you are implying it does not have a AAA
server? At the bottom of your email you said MSP has a AAA server. I am
confused now.
The ASP is defined in the bootstrapping draft as an _operator_, but it is
not clear whether MSP is an operator or just an entity like an HA. What is
the real life correspondence of the MSP??
I like to think MSP include both a HA and a AAA server (MSA).

> 
> *        I see a hot spot provider or a 802.16d network without mobility
> support as an ASP, while a IP enabled cellular or a WiMAX network as a
> combination of ASP and MSP. To me assignment of HA falls into the MSP
> service category, not ASP service category (I just confirmed this in
> bootstrapping-ps section 7.1), so there are some statements in the draft
as
> far as an  ASP assigning an HA and I don't think those are appropriate
based
> on the terminology provided. 

 it depends if we are in the split or integrated scenario.
 In the split scenario, we don't have ASP/ASA, only MSP/MSA. So the user
 has an HA from the MSP.

Madjid>> Well, you do have ASP/ASA, it just that it is beyond MSP control.

 In the integrated scenario, if MSP=ASP, the user obtains an HA from the
 MSP/ASP. 


> 
> *        Then there is the concept of home versus visited domain. I am
> guessing "domain" to administrative domain (AAA domain). Traditionally AAA
> community is denoted as home and visited AAA servers, i.e. AAAH and AAAV,
> respectively. I just checked the bootstrapping-ps draft and that draft
calls
> uses the term "serving" instead of "visited", but still provides a
> distinction between home versus serving MSP (MSPH and MSPS) and between
home
> versus serving ASP (ASPH and ASPS). Having said this, I think if the group
> is going to great length to separate ASP/ MSP and ASA/MSA, it also needs
to
> distinguish between the home versus visited domain for each of the
> authorizers. So that MSAH refers to AAA server within home MSP (MSP-H) and
> MSAV or MSAS (pick one) to AAA server within visited or serving MSP (MSP-V
> or MSP-S). The same goes for ASAH and ASAV. This means Serving MSA is not
> the same as serving ASA. It is not proper to equate the access service
> provider (ASP) with MSP-V the visited domain as it is implied in section
> 4.2: "Mobile Node requests a home agent to the Access Service Provider
> (ASP)". According to my understanding of the terminology of ASP, ASP has
> nothing to anything to do with HA assignment. I think this can be easily
> remedied by introducing MSAH and MSAS. Visited domain HA allocation can be
> formulated as "MN can request MSAH for an HA assignment within MSPS after
> authentication to MSAH and authorization of mobility service by the
> MSAH/MSAS to MN".

 maybe my explanation below will answer to this paragraph ?

Madjid>>Well one point is ASP is an access provider, not a mobility
provider, so ASP cannot grant an HA request nor can it assign one. So that
sentence needs to be revised. The other issue is the lack of distinction
between home and visited providers, ASP does not mean visited MSP!

> *        The same goes for another sentence in the same section saying "..
> Mobile Node can specify if it wants a home agent provided by the visited
> domain (ASP) or by the home domain (ASA)", which seems to be mixing
> (mobility and access service), (home and visited), (provider and
authorizer)
> all in the same sentence!!

 yes, that can be confusing. 

Madjid>>Well, if we stick to the terminology in the bootstrapping draft and
use "serving" and "visited" and clarify whether MSP is an operator or just
an HA, things should fall into a place better. If you agree with my
statements, I could help out with that.

> 
> *        The other comment along the same line is about section 4.1, where
> it is stated a pool of HA s can rely on the home EAP server (I am guessing
> EAP server belonging to MSA-H, since this is split scenario) for
> authentication. Here it is stated "It allows the roaming mobility case in
> which the MN obtains the mobility service in a different administrative
> domain (MSP !=MSA). Here it seems that it is implied HA is part of MSP
> function (appropriately), however, I am not sure if MSP and MSA can imply
> two administrative domains, to me administrative domain implies AAA
domain,
> so one would be MSA-H and another MSA-V, so an HA could be authorized
within
> MSA-V based on authentication to MSA-H and authorization by MSA-H.

 MSP has its own AAA server. MSA is the AAA server of the MN. 
 Does it respond to your comment ?

Madjid>>the definition of MSA is "an authorizer that authorizes MIP6
service". To me that is the AAA server of the MSP: a AAA server that
authorizes MIP6 service within an MSP. Then you have the concept of home
versus serving MSP or ASP and home versus serving MSA and ASA.
The home-MSA can authorize MIP6 service within home MSP and has MN's
credentials. The "MSA" alone is just like a "AAA server" alone, it does not
say home or visited AAA server.

> 
> *        I also have an issue with the usage of term NAS in next to last
> paragraph of section 3. NAS is really an access service agent (as the name
> implies) not a mobility service agent. NAS performs many functions beyond
> the AAA client function, which brings up two issues. 1) the sentence ".HA,
> that can be seen as Network Access Server for MIP6", is only providing
> confusion in this context, you may say that HA can be seen as Network
> mobility server if you want but in a draft that has ASP and MSP
everywhere.

 ok.

> 2) in the goals sections (5.1/ 5.2) , it is not mentioned anywhere that
the
> HA MUST act as a AAA client, is this a non-requirement, or is it
implicitly
> understood?  Especially G2.2 seems to imply this.

 I think it is implicitly understood. Do you think we should add a
 statement on this ?

Madjid>>I think this is the first requirement for the HA within an HA-AAA
goals draft. It tells the world what code to expect to have in the compliant
HA. Having it implicit is not a good thing.

> 
> *        In 5.4 why is it a "MUST" for HA to be an EAP pass-through
> authenticator? As long as HA receives its information from the AAA server
in
> a secure fashion and both HA and AAA can identify the MN and its EAP
session
> uniquely, there is no reason for allocating HA and EAP pass-through EAP
> authenticator in the same box.

 hmmm, the HA acts as a AAA client and MN uses IKEv2 with EAP to be
 authenticated. So the HA MUST act as an EAP pass-through authenticator.

 Am I missing something ? do you think we should rephrase this ?

Madjid>> I don't think this is hard requirement. You may another AAA client
on the path EAP signaling with EAP server. Aren't you separating ASA and
MSA?? HA is AAA client for MSP authorization but not necessarily the AAA
client for every EAP authentication, may be I am missing something.
The way to rephrase it is

"HA Should be able to act as EAP pass-through authenticator in the EAP
process for IKEv2." Or something like that. I have to look at the split
scenario doc explaining this.

> 
> *        For section 4.2, Integrated scenario, I see that NAS gets MIP6
conf
> parameters from the AAAH, how does the HA receives the information it
needs?

 In the integrated scenario based on DHCPv6, the MN gets HA info through
 DHCP. Then we fall in the split scenario and the MN uses IKEv2 with the
 HA. 

Madjid>> Let me do some more reading:)

Thanks,

Madjid

 Julien Bournelle





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



From mip6-bounces@ietf.org Thu Aug 03 20:14:29 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G8nKe-0000KC-2O; Thu, 03 Aug 2006 20:14:28 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G8nKa-0000Jj-Lo; Thu, 03 Aug 2006 20:14:24 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1G8m6e-0002Yt-L7; Thu, 03 Aug 2006 18:55:56 -0400
Received: from ns3.neustar.com ([156.154.24.138])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1G8m1Q-00082Q-PP; Thu, 03 Aug 2006 18:50:34 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id 901421765E;
	Thu,  3 Aug 2006 22:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1G8m0w-0002b8-7a; Thu, 03 Aug 2006 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: <E1G8m0w-0002b8-7a@stiedprstage1.ietf.org>
Date: Thu, 03 Aug 2006 18:50:02 -0400
X-Spam-Score: -5.9 (-----)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Cc: mip6@ietf.org
Subject: [Mip6] I-D ACTION:draft-ietf-mip6-cn-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>
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		: Using IPsec between Mobile and Correspondent IPv6 Nodes
	Author(s)	: F. Dupont, J. Combes
	Filename	: draft-ietf-mip6-cn-ipsec-03.txt
	Pages		: 8
	Date		: 2006-8-3
	
Mobile IPv6 uses IPsec to protect signaling between the mobile node
   and the home agent.  This document defines how IPsec can be used
   between the mobile node and correspondent nodes for home address
   option validation (aka. triangular routing) and protection of
   mobility signaling for route optimizations.  The configuration
   details for IPsec and IKE are also provided.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mip6-cn-ipsec-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-cn-ipsec-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-cn-ipsec-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: <2006-8-3165801.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-mip6-cn-ipsec-03.txt

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

Content-Type: text/plain
Content-ID: <2006-8-3165801.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 Aug 03 20:59:01 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G8o1f-0001sb-0b; Thu, 03 Aug 2006 20:58:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G8o1d-0001qh-Tt
	for mip6@ietf.org; Thu, 03 Aug 2006 20:58:53 -0400
Received: from mail1.azairenet.com ([66.92.223.4] helo=bart.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G8o1c-0001Pi-Kh
	for mip6@ietf.org; Thu, 03 Aug 2006 20:58:53 -0400
Received: from [10.1.201.0] ([10.1.201.0]) by bart.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Thu, 3 Aug 2006 17:58:51 -0700
Message-ID: <44D29B51.8000701@azairenet.com>
Date: Thu, 03 Aug 2006 17:56:49 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.2 (X11/20060516)
MIME-Version: 1.0
To: Alper Yegin <alper.yegin@yegin.org>
Subject: Re: [Mip6] Recommendation for bootstrapping using DHCPv6
References: <0MKp2t-1G8mau14ih-0004IW@mrelay.perfora.net>
In-Reply-To: <0MKp2t-1G8mau14ih-0004IW@mrelay.perfora.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 04 Aug 2006 00:58:51.0421 (UTC)
	FILETIME=[269D94D0:01C6B761]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Cc: mip6@ietf.org, 'Basavaraj Patil' <basavaraj.patil@nokia.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Alper,

Alper Yegin wrote:

> You misunderstood me. Let me re-iterate what I had described on the list
> earlier:
> 
> - The integrated bootstrapping solution depends on a number of protocol
> design work (1. DHCP options for HA discovery, 2. RADIUS attributes for HA
> discovery, 3. Diameter AVPs for HA discovery, 4. IKEv2 for HoA
> configuration, 5. RADIUS attributes for MIP6 authentication, 6. Diameter
> AVPs for MIP6 authentication) and description (7) of how all such protocols
> plumb together to yield so-called "MIP6 bootstrapping." 
> 
> Now, item 7 is described in
> draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt. All the others are
> currently described in separate documents, and that makes sense. Asking for
> 1 and 7 be merged does not make sense. If it did, my questions was, why not
> merge the others as well. Do you see my point?

2), 3), 4), 5) and 6) have nothing to do with DHCP. if
tomorrow somebody comes with a bootstrapping solution
based on PANA for the integrated scenario, 2), 3), 4),
5) and 6) can be re-used.

there were in fact two other proposals, one based on
PANA and another based on EAP for integrated scenario
bootstrapping.

draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt
describes a solution for the integrated scenario
*using* DHCP. it is not a "plumbing" document for the
integrated scenario.

Vijay

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



From mip6-bounces@ietf.org Thu Aug 03 21:04:58 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G8o7V-0008Ff-U9; Thu, 03 Aug 2006 21:04:57 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G8o7U-0008Eb-2k
	for mip6@ietf.org; Thu, 03 Aug 2006 21:04:56 -0400
Received: from email1.etri.re.kr ([129.254.16.131] helo=email1.etri.info)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G8o7Q-0002uk-UB
	for mip6@ietf.org; Thu, 03 Aug 2006 21:04:56 -0400
Received: from cool ([129.254.112.107]) by email1.etri.info with Microsoft
	SMTPSVC(6.0.3790.1830); Fri, 4 Aug 2006 10:08:09 +0900
From: "Junghoon Jee" <jhjee@etri.re.kr>
To: "'Alper Yegin'" <alper.yegin@yegin.org>,
	"'Basavaraj Patil'" <basavaraj.patil@nokia.com>, <mip6@ietf.org>
Subject: RE: [Mip6] Recommendation for bootstrapping using DHCPv6
Date: Fri, 4 Aug 2006 10:04:31 +0900
Message-ID: <00ab01c6b761$f12da910$6b70fe81@cool>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
In-Reply-To: <0MKp2t-1G8mau14ih-0004IW@mrelay.perfora.net>
Thread-Index: Aca1oaIQ4K1FzyGUEduPhAARJNUNiAA2bJdQAC3tKR8AB7hywAACSm+A
X-OriginalArrivalTime: 04 Aug 2006 01:08:09.0829 (UTC)
	FILETIME=[7373E150:01C6B762]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
Cc: 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Feeling hard to intervene...
However having looked at this issue over very long time again and
again,
eventually I spent sometime looking at this issue again and decided to
share my thought at this time.

Disclaimer: I don't have so strong opinion on this issue, just to
share my thought to try to resolve still unsolved issue.

> - The integrated bootstrapping solution depends on a number 
> of protocol design work (1. DHCP options for HA discovery, 2. 
> RADIUS attributes for HA discovery, 3. Diameter AVPs for HA 
> discovery, 4. IKEv2 for HoA configuration, 5. RADIUS 
> attributes for MIP6 authentication, 6. Diameter AVPs for MIP6 
> authentication) and description (7) of how all such protocols 
> plumb together to yield so-called "MIP6 bootstrapping." 
> 
> Now, item 7 is described in
> draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt. All the 
> others are currently described in separate documents, and 
> that makes sense. Asking for
> 1 and 7 be merged does not make sense. If it did, my 
> questions was, why not merge the others as well. Do you see my
point?

I also think above statements are reasonable. 
BTW, it is true that some concerns arise from the behaviors in the
draft-jang maybe throught the section 4.2.

Here is the section 4.2 for draft-jang.
--------------------------------------------------
4.2.  Mobile Node Considerations

   When a Mobile IPv6 Mobile Node finds itself with neither a home
   subnet prefix nor a home agent address, it may request the needed
   information with Option Request option.  For instance, a mobile
node
   connecting to a network for the first time may acquire a DHCP
address
   and solicit for home network information at the same time.

   A mobile node MUST identify the desired information with Home
Network
   Identifier option.  For example, a DHCP server may have information
   about home agents from several domains (and subnets).  It relies on
   the mobile node to select the domain for determining which ones it
   should provide in response to the client's request.

   When the mobile node gets more than one home agent address, it MUST
   have a selection mechanism to determine which one to use for
   establishing a Mobile IPv6 session.  In case it retrieves only home
   subnet prefix(es), it needs to perform dynamic home agent discovery
   to learn the IP addresses of the home agents.  Similarly, if FQDN
of
   a home agent is retrieved, the mobile node can use DNS to resolve
it
   to IPv6 address(es).
----------------------------------------------------------------

Vijay, could you pin-point out what specific texts are not comfortable
based on the protocol behavior from the
draft-ietf-mip6-bootstrapping-integrated-dhc-01?

Junghoon 


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



From mip6-bounces@ietf.org Fri Aug 04 00:19:39 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G8r9s-0002L7-5u; Fri, 04 Aug 2006 00:19:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G8r9r-0002Ij-0X
	for mip6@ietf.org; Fri, 04 Aug 2006 00:19:35 -0400
Received: from mail1.azairenet.com ([66.92.223.4] helo=bart.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G8r9o-000616-KU
	for mip6@ietf.org; Fri, 04 Aug 2006 00:19:34 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] Recommendation for bootstrapping using DHCPv6
Date: Thu, 3 Aug 2006 21:19:30 -0700
Message-ID: <C8E1D942CB394746BE5CFEB7D97610E701CA407B@bart.corp.azairenet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] Recommendation for bootstrapping using DHCPv6
Thread-Index: Aca1oaIQ4K1FzyGUEduPhAARJNUNiAA2bJdQAC3tKR8AB7hywAACSm+AAAiC2rA=
From: "Vijay Devarapalli" <Vijay.Devarapalli@AzaireNet.com>
To: "Junghoon Jee" <jhjee@etri.re.kr>, "Alper Yegin" <alper.yegin@yegin.org>,
	"Basavaraj Patil" <basavaraj.patil@nokia.com>, <mip6@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 31247fb3be228bb596db9127becad0bc
Cc: 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Junghoon,

been through that endless loop. I will pass. :)

Vijay=20

> -----Original Message-----
> From: Junghoon Jee [mailto:jhjee@etri.re.kr]=20
> Sent: Thursday, August 03, 2006 6:05 PM
> To: 'Alper Yegin'; 'Basavaraj Patil'; mip6@ietf.org
> Subject: RE: [Mip6] Recommendation for bootstrapping using DHCPv6
>=20
> Feeling hard to intervene...
> However having looked at this issue over very long time again and
> again,
> eventually I spent sometime looking at this issue again and decided to
> share my thought at this time.
>=20
> Disclaimer: I don't have so strong opinion on this issue, just to
> share my thought to try to resolve still unsolved issue.
>=20
> > - The integrated bootstrapping solution depends on a number=20
> > of protocol design work (1. DHCP options for HA discovery, 2.=20
> > RADIUS attributes for HA discovery, 3. Diameter AVPs for HA=20
> > discovery, 4. IKEv2 for HoA configuration, 5. RADIUS=20
> > attributes for MIP6 authentication, 6. Diameter AVPs for MIP6=20
> > authentication) and description (7) of how all such protocols=20
> > plumb together to yield so-called "MIP6 bootstrapping."=20
> >=20
> > Now, item 7 is described in
> > draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt. All the=20
> > others are currently described in separate documents, and=20
> > that makes sense. Asking for
> > 1 and 7 be merged does not make sense. If it did, my=20
> > questions was, why not merge the others as well. Do you see my
> point?
>=20
> I also think above statements are reasonable.=20
> BTW, it is true that some concerns arise from the behaviors in the
> draft-jang maybe throught the section 4.2.
>=20
> Here is the section 4.2 for draft-jang.
> --------------------------------------------------
> 4.2.  Mobile Node Considerations
>=20
>    When a Mobile IPv6 Mobile Node finds itself with neither a home
>    subnet prefix nor a home agent address, it may request the needed
>    information with Option Request option.  For instance, a mobile
> node
>    connecting to a network for the first time may acquire a DHCP
> address
>    and solicit for home network information at the same time.
>=20
>    A mobile node MUST identify the desired information with Home
> Network
>    Identifier option.  For example, a DHCP server may have information
>    about home agents from several domains (and subnets).  It relies on
>    the mobile node to select the domain for determining which ones it
>    should provide in response to the client's request.
>=20
>    When the mobile node gets more than one home agent address, it MUST
>    have a selection mechanism to determine which one to use for
>    establishing a Mobile IPv6 session.  In case it retrieves only home
>    subnet prefix(es), it needs to perform dynamic home agent discovery
>    to learn the IP addresses of the home agents.  Similarly, if FQDN
> of
>    a home agent is retrieved, the mobile node can use DNS to resolve
> it
>    to IPv6 address(es).
> ----------------------------------------------------------------
>=20
> Vijay, could you pin-point out what specific texts are not comfortable
> based on the protocol behavior from the
> draft-ietf-mip6-bootstrapping-integrated-dhc-01?
>=20
> Junghoon=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 Fri Aug 04 07:10:36 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G8xZT-0002v0-Td; Fri, 04 Aug 2006 07:10:27 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G8xZT-0002uv-9Y
	for mip6@ietf.org; Fri, 04 Aug 2006 07:10:27 -0400
Received: from smtp2.int-evry.fr ([157.159.10.45])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G8xZR-0006Kh-Sn
	for mip6@ietf.org; Fri, 04 Aug 2006 07:10:27 -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 3953E2FD7F;
	Fri,  4 Aug 2006 13:10:21 +0200 (CEST)
Received: from jb by ipv6-3.int-evry.fr with local (Exim 4.52)
	id 1G8xbd-0001jD-0w; Fri, 04 Aug 2006 13:12:41 +0200
Date: Fri, 4 Aug 2006 13:12:41 +0200
From: Julien Bournelle <julien.bournelle@int-evry.fr>
To: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
Subject: Re: [Mip6] Recommendation for bootstrapping using DHCPv6
Message-ID: <20060804111241.GB6628@ipv6-3.int-evry.fr>
References: <0MKp2t-1G8mau14ih-0004IW@mrelay.perfora.net>
	<44D29B51.8000701@azairenet.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <44D29B51.8000701@azairenet.com>
User-Agent: Mutt/1.5.9i
X-INT-MailScanner-Information: Please contact the ISP for more information
X-INT-MailScanner: Found to be clean
X-INT-MailScanner-MCPCheck: 
X-INT-MailScanner-SpamCheck: 
X-MailScanner-From: jb@int-evry.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Cc: mip6@ietf.org, 'Basavaraj Patil' <basavaraj.patil@nokia.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi all,

On Thu, Aug 03, 2006 at 05:56:49PM -0700, Vijay Devarapalli wrote:
> Alper,
> 
> Alper Yegin wrote:
> 
> >You misunderstood me. Let me re-iterate what I had described on the list
> >earlier:
> >
> >- The integrated bootstrapping solution depends on a number of protocol
> >design work (1. DHCP options for HA discovery, 2. RADIUS attributes for HA
> >discovery, 3. Diameter AVPs for HA discovery, 4. IKEv2 for HoA
> >configuration, 5. RADIUS attributes for MIP6 authentication, 6. Diameter
> >AVPs for MIP6 authentication) and description (7) of how all such protocols
> >plumb together to yield so-called "MIP6 bootstrapping." 
> >
> >Now, item 7 is described in
> >draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt. All the others are
> >currently described in separate documents, and that makes sense. Asking for
> >1 and 7 be merged does not make sense. If it did, my questions was, why not
> >merge the others as well. Do you see my point?
> 
> 2), 3), 4), 5) and 6) have nothing to do with DHCP. if
> tomorrow somebody comes with a bootstrapping solution
> based on PANA for the integrated scenario, 2), 3), 4),
> 5) and 6) can be re-used.
> 
> there were in fact two other proposals, one based on
> PANA and another based on EAP for integrated scenario
> bootstrapping.

 FYI, we have in fact a proposal based on PANA who can fit for 1/.
 http://www.ietf.org/internet-drafts/draft-bournelle-pana-mip6-01.txt
 and for which 2/ 3/ 4/ 5/ and 5/ can be re-used.

 regards,

 Julien

> 
> draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt
> describes a solution for the integrated scenario
> *using* DHCP. it is not a "plumbing" document for the
> integrated scenario.
> 
> Vijay
> 
> _______________________________________________
> 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 Fri Aug 04 09:28:49 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G8zj2-00057v-Qu; Fri, 04 Aug 2006 09:28:28 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G8zj1-00057o-KS
	for mip6@ietf.org; Fri, 04 Aug 2006 09:28:27 -0400
Received: from motgate5.mot.com ([144.189.100.105])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G8ziz-0007ym-3p
	for mip6@ietf.org; Fri, 04 Aug 2006 09:28:27 -0400
Received: from az33exr02.mot.com (az33exr02.mot.com [10.64.251.232])
	by motgate5.mot.com (8.12.11/Motorola) with ESMTP id k74DSOin023671
	for <mip6@ietf.org>; Fri, 4 Aug 2006 06:28:24 -0700 (MST)
Received: from ZMY16EXM67.ds.mot.com (zmy16exm67.ap.mot.com [10.179.4.27])
	by az33exr02.mot.com (8.13.1/8.13.0) with ESMTP id k74DSMxl026263
	for <mip6@ietf.org>; Fri, 4 Aug 2006 08:28:23 -0500 (CDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [Mip6] Recommendation for bootstrapping using DHCPv6
Date: Fri, 4 Aug 2006 21:28:21 +0800
Message-ID: <AE007C20C0A3D44D8EE9DD46764559AD010B6CB7@ZMY16EXM67.ds.mot.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Re: [Mip6] Recommendation for bootstrapping using DHCPv6
Thread-Index: Aca1oaIQ4K1FzyGUEduPhAARJNUNiAA2bJdQACND7dAAAnSisAAsarggAADlowA=
From: "Upadhyaya Saumya-a20369" <saumya@motorola.com>
To: <mip6@ietf.org>
X-Brightmail-Tracker: AAAAAQAAAAQ=
X-White-List-Member: TRUE
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 287c806b254c6353fcb09ee0e53bbc5e
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

=20
Hi Alper,

With regard to the Diameter interface to obtain MIP6 bootstrapping
parameters, we have an individual draft=20
(http://www.ietf.org/internet-drafts/draft-ram-dhc-dhcpv6-diam-app-00.tx
t)=20
for the proposed interface between DHCP Server and AAA. This interface
could be used to get the mip6  =20
bootstrapping params from the AAA, although the primary purpose of this
draft=20
is to authenticate the DHCPv6 service.=20

Comments are solicited.

Regards,
Saumya



-----Original Message-----
From: Alper Yegin [mailto:alper.yegin@yegin.org]=20
Sent: Thursday, August 03, 2006 3:15 AM
To: 'Basavaraj Patil'; mip6@ietf.org
Subject: RE: [Mip6] Recommendation for bootstrapping using DHCPv6


Hi Raj,

"Having the options specified in a stand-along document will not add
much value."

As we have been stating, draft-jang-mip6-hiopt-00.txt also has a use
that does not tie into the RADIUS-driven details -- the use where DHCP
server can be manually configured and has nothing to do with the AAA.=20

Your above statement misses this point.=20

Besides, while there is a standalone use for
draft-jang-mip6-hiopt-00.txt, there is none for the RADIUS and Diameter
specs we expect to document individually. Should we also merge those AAA
documents with the others?

Also, I'm not sure what specific concern you are raising with respect to
the quoted text below.

Alper



> -----Original Message-----
> From: Basavaraj Patil [mailto:basavaraj.patil@nokia.com]
> Sent: Tuesday, August 01, 2006 12:35 PM
> To: mip6@ietf.org
> Subject: [Mip6] Recommendation for bootstrapping using DHCPv6
>=20
>=20
> Alper/Kuntal et al,
>=20
> I have reviewed the drafts:
> 1. Problem Statement for bootstrapping Mobile IPv6
>    (draft-ietf-mip6-bootstrap-ps-05)
> 2. MIP6-bootstrapping via DHCPv6 for the Integrated Scenario
>    (draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt)
>=20
> and
> 3. DHCP Option for Home Information Discovery in MIPv6
>    (draft-jang-mip6-hiopt-00.txt)
>=20
> My conclusion from the review is that the integrated scenario=20
> bootstrapping via DHCPv6 is covering the cases when DHCP is the=20
> preferred method by MNs.
>=20
> The WG I-D draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt in=20
> sections 3.5 and 3.8 explain how DHCP would work. Having the options=20
> specified in a stand-along document will not add much value. I am also

> concerned about the fact in draft-jang which states that: "
>    The availability of the requested information depends on the DHCP
>    server having prior knowledge or dynamically discovering it.  While
>    the specific details are outside the scope of this document, use of
>    static tables and AAA-assisted discovery are possible options "
>=20
> Another concern that I have w.r.t bootstrapping with DHCPv6 is that=20
> instead of having DHCP provide the HoA or the HL prefix to the MS, it=20
> is better to only provide the address of an HA (or list of HAs) and=20
> let the MS send a BU with unspecified address and obtain an address=20
> from the HA. This will simplify bootstrapping and also reduce the=20
> interaction between DHCP and the HA from an address management=20
> perspective. Hence you may want to reconsider the DHCP option which=20
> carry the HL Prefix or the HoA for the MS.
>=20
> I recommend that the DHCP option specified in draft-jang be=20
> incorporated into the WG I-D and progressed on standards track. As a=20
> result the WG will have a mechanism for bootstrapping MIP6 with DHCP=20
> that also includes the DHCP options in a single I-D.
>=20
> -Raj
>=20
>=20
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6


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

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



From mip6-bounces@ietf.org Fri Aug 04 11:08:53 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G91I6-0001p2-Np; Fri, 04 Aug 2006 11:08:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G91I5-0001oV-5F
	for mip6@ietf.org; Fri, 04 Aug 2006 11:08:45 -0400
Received: from mail1.azairenet.com ([66.92.223.4] helo=bart.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G91I4-0004kC-NU
	for mip6@ietf.org; Fri, 04 Aug 2006 11:08:45 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] Recommendation for bootstrapping using DHCPv6
Date: Fri, 4 Aug 2006 08:08:42 -0700
Message-ID: <C8E1D942CB394746BE5CFEB7D97610E701D993AF@bart.corp.azairenet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] Recommendation for bootstrapping using DHCPv6
Thread-Index: Aca1oaIQ4K1FzyGUEduPhAARJNUNiAA2bJdQACND7dAAAnSisAAsarggAADlowAABBDVsA==
From: "Vijay Devarapalli" <Vijay.Devarapalli@AzaireNet.com>
To: "Upadhyaya Saumya-a20369" <saumya@motorola.com>,
	<mip6@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ff9c467ad7f19c2a6d058acd7faaec8
Cc: 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi Saumya,

the work on this is being done in the DIME WG. take a look at=20
http://www.ietf.org/internet-drafts/draft-ietf-dime-mip6-integrated-00.tx=
t=20
http://www.ietf.org/internet-drafts/draft-ietf-dime-mip6-split-00.txt

Vijay

> -----Original Message-----
> From: Upadhyaya Saumya-a20369 [mailto:saumya@motorola.com]=20
> Sent: Friday, August 04, 2006 6:28 AM
> To: mip6@ietf.org
> Subject: Re: [Mip6] Recommendation for bootstrapping using DHCPv6
>=20
> =20
> Hi Alper,
>=20
> With regard to the Diameter interface to obtain MIP6 bootstrapping
> parameters, we have an individual draft=20
> (http://www.ietf.org/internet-drafts/draft-ram-dhc-dhcpv6-diam
-app-00.tx
> t)=20
> for the proposed interface between DHCP Server and AAA. This interface
> could be used to get the mip6  =20
> bootstrapping params from the AAA, although the primary=20
> purpose of this
> draft=20
> is to authenticate the DHCPv6 service.=20
>=20
> Comments are solicited.
>=20
> Regards,
> Saumya
>=20
>=20
>=20
> -----Original Message-----
> From: Alper Yegin [mailto:alper.yegin@yegin.org]=20
> Sent: Thursday, August 03, 2006 3:15 AM
> To: 'Basavaraj Patil'; mip6@ietf.org
> Subject: RE: [Mip6] Recommendation for bootstrapping using DHCPv6
>=20
>=20
> Hi Raj,
>=20
> "Having the options specified in a stand-along document will not add
> much value."
>=20
> As we have been stating, draft-jang-mip6-hiopt-00.txt also has a use
> that does not tie into the RADIUS-driven details -- the use where DHCP
> server can be manually configured and has nothing to do with the AAA.=20
>=20
> Your above statement misses this point.=20
>=20
> Besides, while there is a standalone use for
> draft-jang-mip6-hiopt-00.txt, there is none for the RADIUS=20
> and Diameter
> specs we expect to document individually. Should we also=20
> merge those AAA
> documents with the others?
>=20
> Also, I'm not sure what specific concern you are raising with=20
> respect to
> the quoted text below.
>=20
> Alper
>=20
>=20
>=20
> > -----Original Message-----
> > From: Basavaraj Patil [mailto:basavaraj.patil@nokia.com]
> > Sent: Tuesday, August 01, 2006 12:35 PM
> > To: mip6@ietf.org
> > Subject: [Mip6] Recommendation for bootstrapping using DHCPv6
> >=20
> >=20
> > Alper/Kuntal et al,
> >=20
> > I have reviewed the drafts:
> > 1. Problem Statement for bootstrapping Mobile IPv6
> >    (draft-ietf-mip6-bootstrap-ps-05)
> > 2. MIP6-bootstrapping via DHCPv6 for the Integrated Scenario
> >    (draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt)
> >=20
> > and
> > 3. DHCP Option for Home Information Discovery in MIPv6
> >    (draft-jang-mip6-hiopt-00.txt)
> >=20
> > My conclusion from the review is that the integrated scenario=20
> > bootstrapping via DHCPv6 is covering the cases when DHCP is the=20
> > preferred method by MNs.
> >=20
> > The WG I-D draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt in=20
> > sections 3.5 and 3.8 explain how DHCP would work. Having=20
> the options=20
> > specified in a stand-along document will not add much=20
> value. I am also
>=20
> > concerned about the fact in draft-jang which states that: "
> >    The availability of the requested information depends on the DHCP
> >    server having prior knowledge or dynamically discovering=20
> it.  While
> >    the specific details are outside the scope of this=20
> document, use of
> >    static tables and AAA-assisted discovery are possible options "
> >=20
> > Another concern that I have w.r.t bootstrapping with DHCPv6 is that=20
> > instead of having DHCP provide the HoA or the HL prefix to=20
> the MS, it=20
> > is better to only provide the address of an HA (or list of HAs) and=20
> > let the MS send a BU with unspecified address and obtain an address=20
> > from the HA. This will simplify bootstrapping and also reduce the=20
> > interaction between DHCP and the HA from an address management=20
> > perspective. Hence you may want to reconsider the DHCP option which=20
> > carry the HL Prefix or the HoA for the MS.
> >=20
> > I recommend that the DHCP option specified in draft-jang be=20
> > incorporated into the WG I-D and progressed on standards=20
> track. As a=20
> > result the WG will have a mechanism for bootstrapping MIP6=20
> with DHCP=20
> > that also includes the DHCP options in a single I-D.
> >=20
> > -Raj
> >=20
> >=20
> > _______________________________________________
> > Mip6 mailing list
> > Mip6@ietf.org
> > https://www1.ietf.org/mailman/listinfo/mip6
>=20
>=20
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
>=20
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
>=20

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



From mip6-bounces@ietf.org Fri Aug 04 12:26:50 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G92VZ-00056x-Ph; Fri, 04 Aug 2006 12:26:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G92VY-00056a-HH
	for mip6@ietf.org; Fri, 04 Aug 2006 12:26:44 -0400
Received: from smtp2.int-evry.fr ([157.159.10.45])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G92RC-0001JZ-Kv
	for mip6@ietf.org; Fri, 04 Aug 2006 12:22: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 6F8A02FF0B;
	Fri,  4 Aug 2006 18:22:12 +0200 (CEST)
Received: from jb by ipv6-3.int-evry.fr with local (Exim 4.52)
	id 1G92TP-0001mq-Ub; Fri, 04 Aug 2006 18:24:31 +0200
Date: Fri, 4 Aug 2006 18:24:31 +0200
From: Julien Bournelle <julien.bournelle@int-evry.fr>
To: Madjid Nakhjiri <mnakhjiri@huawei.com>
Subject: Re: [Mip6] comments on AAA-HA-goals-02
Message-ID: <20060804162431.GA6864@ipv6-3.int-evry.fr>
References: <20060803142209.GA5650@ipv6-3.int-evry.fr>
	<003101c6b755$d1b6a930$03fda8c0@china.huawei.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <003101c6b755$d1b6a930$03fda8c0@china.huawei.com>
User-Agent: Mutt/1.5.9i
X-INT-MailScanner-Information: Please contact the ISP for more information
X-INT-MailScanner: Found to be clean
X-INT-MailScanner-MCPCheck: 
X-INT-MailScanner-SpamCheck: 
X-MailScanner-From: jb@int-evry.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bacfc6c7290e34d410f9bc22b825ce96
Cc: 'Julien Bournelle' <julien.bournelle@int-evry.fr>, mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi madjid,

 I think that this discussion is more about our understanding of the
 bootstrapping-ps terminology. Maybe we should start a new thread about
 this.

 Julien


On Thu, Aug 03, 2006 at 04:37:44PM -0700, Madjid Nakhjiri wrote:
> Hi Julien, 
> 
> Thanks for the quick reply. 
> 
> 
> -----Original Message-----
> From: Julien Bournelle [mailto:julien.bournelle@int-evry.fr] 
> Sent: Thursday, August 03, 2006 7:22 AM
> To: Madjid Nakhjiri
> Cc: mip6@ietf.org
> Subject: Re: [Mip6] comments on AAA-HA-goals-02
> 
> Hi madjid,
> 
>  let me try to respond to your mail though some terminology issues are more
> related to the
>  draft-ietf-mip6-bootstrapping-ps draft.
> 
> Madjid>>I actually find the terminology in the bootstrapping draft more
> consistent. 
> 
> > The network MSA to me symbolizes
> > the MSP-AAA server, while ASA symbolizes ASP-AAA server. 
> 
>  no, the MSA is administrative entity with whom the user has a contract
>  and thus credentials. The MSP effectively provides the MIP6 service to
>  the user. Thus the MSP may have to contact the MSA before providing the
>  service. 
> 
> Madjid>>Well, you are saying MSA has a contract with the user and has her
> credentials. To me it translates to a home AAA server or authentication
> server for the MSP. I think we need to make the distinction between home MSA
> and visited MSA.
> Also, MSP is a service provider, but you are implying it does not have a AAA
> server? At the bottom of your email you said MSP has a AAA server. I am
> confused now.
> The ASP is defined in the bootstrapping draft as an _operator_, but it is
> not clear whether MSP is an operator or just an entity like an HA. What is
> the real life correspondence of the MSP??
> I like to think MSP include both a HA and a AAA server (MSA).
> 
> > 
> > *        I see a hot spot provider or a 802.16d network without mobility
> > support as an ASP, while a IP enabled cellular or a WiMAX network as a
> > combination of ASP and MSP. To me assignment of HA falls into the MSP
> > service category, not ASP service category (I just confirmed this in
> > bootstrapping-ps section 7.1), so there are some statements in the draft
> as
> > far as an  ASP assigning an HA and I don't think those are appropriate
> based
> > on the terminology provided. 
> 
>  it depends if we are in the split or integrated scenario.
>  In the split scenario, we don't have ASP/ASA, only MSP/MSA. So the user
>  has an HA from the MSP.
> 
> Madjid>> Well, you do have ASP/ASA, it just that it is beyond MSP control.
> 
>  In the integrated scenario, if MSP=ASP, the user obtains an HA from the
>  MSP/ASP. 
> 
> 
> > 
> > *        Then there is the concept of home versus visited domain. I am
> > guessing "domain" to administrative domain (AAA domain). Traditionally AAA
> > community is denoted as home and visited AAA servers, i.e. AAAH and AAAV,
> > respectively. I just checked the bootstrapping-ps draft and that draft
> calls
> > uses the term "serving" instead of "visited", but still provides a
> > distinction between home versus serving MSP (MSPH and MSPS) and between
> home
> > versus serving ASP (ASPH and ASPS). Having said this, I think if the group
> > is going to great length to separate ASP/ MSP and ASA/MSA, it also needs
> to
> > distinguish between the home versus visited domain for each of the
> > authorizers. So that MSAH refers to AAA server within home MSP (MSP-H) and
> > MSAV or MSAS (pick one) to AAA server within visited or serving MSP (MSP-V
> > or MSP-S). The same goes for ASAH and ASAV. This means Serving MSA is not
> > the same as serving ASA. It is not proper to equate the access service
> > provider (ASP) with MSP-V the visited domain as it is implied in section
> > 4.2: "Mobile Node requests a home agent to the Access Service Provider
> > (ASP)". According to my understanding of the terminology of ASP, ASP has
> > nothing to anything to do with HA assignment. I think this can be easily
> > remedied by introducing MSAH and MSAS. Visited domain HA allocation can be
> > formulated as "MN can request MSAH for an HA assignment within MSPS after
> > authentication to MSAH and authorization of mobility service by the
> > MSAH/MSAS to MN".
> 
>  maybe my explanation below will answer to this paragraph ?
> 
> Madjid>>Well one point is ASP is an access provider, not a mobility
> provider, so ASP cannot grant an HA request nor can it assign one. So that
> sentence needs to be revised. The other issue is the lack of distinction
> between home and visited providers, ASP does not mean visited MSP!
> 
> > *        The same goes for another sentence in the same section saying "..
> > Mobile Node can specify if it wants a home agent provided by the visited
> > domain (ASP) or by the home domain (ASA)", which seems to be mixing
> > (mobility and access service), (home and visited), (provider and
> authorizer)
> > all in the same sentence!!
> 
>  yes, that can be confusing. 
> 
> Madjid>>Well, if we stick to the terminology in the bootstrapping draft and
> use "serving" and "visited" and clarify whether MSP is an operator or just
> an HA, things should fall into a place better. If you agree with my
> statements, I could help out with that.
> 
> > 
> > *        The other comment along the same line is about section 4.1, where
> > it is stated a pool of HA s can rely on the home EAP server (I am guessing
> > EAP server belonging to MSA-H, since this is split scenario) for
> > authentication. Here it is stated "It allows the roaming mobility case in
> > which the MN obtains the mobility service in a different administrative
> > domain (MSP !=MSA). Here it seems that it is implied HA is part of MSP
> > function (appropriately), however, I am not sure if MSP and MSA can imply
> > two administrative domains, to me administrative domain implies AAA
> domain,
> > so one would be MSA-H and another MSA-V, so an HA could be authorized
> within
> > MSA-V based on authentication to MSA-H and authorization by MSA-H.
> 
>  MSP has its own AAA server. MSA is the AAA server of the MN. 
>  Does it respond to your comment ?
> 
> Madjid>>the definition of MSA is "an authorizer that authorizes MIP6
> service". To me that is the AAA server of the MSP: a AAA server that
> authorizes MIP6 service within an MSP. Then you have the concept of home
> versus serving MSP or ASP and home versus serving MSA and ASA.
> The home-MSA can authorize MIP6 service within home MSP and has MN's
> credentials. The "MSA" alone is just like a "AAA server" alone, it does not
> say home or visited AAA server.
> 
> > 
> > *        I also have an issue with the usage of term NAS in next to last
> > paragraph of section 3. NAS is really an access service agent (as the name
> > implies) not a mobility service agent. NAS performs many functions beyond
> > the AAA client function, which brings up two issues. 1) the sentence ".HA,
> > that can be seen as Network Access Server for MIP6", is only providing
> > confusion in this context, you may say that HA can be seen as Network
> > mobility server if you want but in a draft that has ASP and MSP
> everywhere.
> 
>  ok.
> 
> > 2) in the goals sections (5.1/ 5.2) , it is not mentioned anywhere that
> the
> > HA MUST act as a AAA client, is this a non-requirement, or is it
> implicitly
> > understood?  Especially G2.2 seems to imply this.
> 
>  I think it is implicitly understood. Do you think we should add a
>  statement on this ?
> 
> Madjid>>I think this is the first requirement for the HA within an HA-AAA
> goals draft. It tells the world what code to expect to have in the compliant
> HA. Having it implicit is not a good thing.
> 
> > 
> > *        In 5.4 why is it a "MUST" for HA to be an EAP pass-through
> > authenticator? As long as HA receives its information from the AAA server
> in
> > a secure fashion and both HA and AAA can identify the MN and its EAP
> session
> > uniquely, there is no reason for allocating HA and EAP pass-through EAP
> > authenticator in the same box.
> 
>  hmmm, the HA acts as a AAA client and MN uses IKEv2 with EAP to be
>  authenticated. So the HA MUST act as an EAP pass-through authenticator.
> 
>  Am I missing something ? do you think we should rephrase this ?
> 
> Madjid>> I don't think this is hard requirement. You may another AAA client
> on the path EAP signaling with EAP server. Aren't you separating ASA and
> MSA?? HA is AAA client for MSP authorization but not necessarily the AAA
> client for every EAP authentication, may be I am missing something.
> The way to rephrase it is
> 
> "HA Should be able to act as EAP pass-through authenticator in the EAP
> process for IKEv2." Or something like that. I have to look at the split
> scenario doc explaining this.
> 
> > 
> > *        For section 4.2, Integrated scenario, I see that NAS gets MIP6
> conf
> > parameters from the AAAH, how does the HA receives the information it
> needs?
> 
>  In the integrated scenario based on DHCPv6, the MN gets HA info through
>  DHCP. Then we fall in the split scenario and the MN uses IKEv2 with the
>  HA. 
> 
> Madjid>> Let me do some more reading:)
> 
> Thanks,
> 
> Madjid
> 
>  Julien Bournelle
> 
> 
> 
> 

-- 
julien.bournelle at int-evry.fr

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



From mip6-bounces@ietf.org Fri Aug 04 12:31:04 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G92Zj-0004Nn-UZ; Fri, 04 Aug 2006 12:31:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G92Zj-0004Ni-IB
	for mip6@ietf.org; Fri, 04 Aug 2006 12:31:03 -0400
Received: from mgw-ext14.nokia.com ([131.228.20.173])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G92Zi-0002FS-RA
	for mip6@ietf.org; Fri, 04 Aug 2006 12:31:03 -0400
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
	by mgw-ext14.nokia.com (Switch-3.1.8/Switch-3.1.7) with ESMTP id
	k74GV1u0024621; Fri, 4 Aug 2006 19:31:01 +0300
Received: from daebh101.NOE.Nokia.com ([10.241.35.111]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 4 Aug 2006 19:31:02 +0300
Received: from daebe101.NOE.Nokia.com ([10.241.35.113]) by
	daebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 4 Aug 2006 11:30:52 -0500
Received: from 172.19.244.182 ([172.19.244.182]) by daebe101.NOE.Nokia.com
	([10.241.35.113]) with Microsoft Exchange Server HTTP-DAV ; 
	Fri,  4 Aug 2006 16:30:51 +0000
User-Agent: Microsoft-Entourage/11.2.5.060620
Date: Fri, 04 Aug 2006 11:31:05 -0500
Subject: Re: [Mip6] Recommendation for bootstrapping using DHCPv6
From: Basavaraj Patil <basavaraj.patil@nokia.com>
To: ext Alper Yegin <alper.yegin@yegin.org>, <mip6@ietf.org>
Message-ID: <C0F8E079.20984%basavaraj.patil@nokia.com>
Thread-Topic: [Mip6] Recommendation for bootstrapping using DHCPv6
Thread-Index: Aca1oaIQ4K1FzyGUEduPhAARJNUNiAA2bJdQAC3tKR8AB7hywAAkXbI5
In-Reply-To: <0MKp2t-1G8mau14ih-0004IW@mrelay.perfora.net>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 04 Aug 2006 16:30:52.0146 (UTC)
	FILETIME=[59F70D20:01C6B7E3]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bf422c85703d3d847fb014987125ac48
Cc: 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org


Alper,

On 8/3/06 6:27 PM, "ext Alper Yegin" <alper.yegin@yegin.org> wrote:


>
>Hi Raj,
>
>> > "Having the options specified in a stand-along document will not add much
>> > value."
>> >
>> > As we have been stating, draft-jang-mip6-hiopt-00.txt also has a use that
>> > does not tie into the RADIUS-driven details -- the use where DHCP server
>> can
>> > be manually configured and has nothing to do with the AAA.
>> 
>> But why do you believe that the WG I-D which is using DHCP is RADIUS driven
>> only and nothing else?
>
>AAA is integral to the current solutions designed by the MIP6 WG for MIP6
>bootstrapping. 

BP: Yes. I think we agreed when this work began that the MN shared a
BP: security association with an entity such as the AAA in the home
BP: network and not the HA (which is what RFC3775 is based on). But
BP: I dont see how the fact that AAA is an integral part of the
BP: bootstrapping solution has anything to do with DHCP options other
BP: than the fact that AAA messages are used to obtain information
BP: such as the address of the HA and insert them in a DHCP
BP: server. But that should be dealt with in the Dime WG (I-D:
BP: draft-ietf-dime-mip6-integrated-00.txt) and the same with Radius
BP: as specified in I-D: draft-chowdhury-mip6-radius-02.

>
>> I mean it could just as well be used for the case
>> where the bootstrapping information is manually configured in the DHCP
>> server. What is needed are the DHCP options and the fact that the
>> bootstrap
>> parameters are available in the DHCP server either as a result of some AAA
>> messages or manual configuration does not matter.
>
>Yes, this is exactly what the draft-jang is saying.

BP: I know. And my point is that the WG I-D:
BP: draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt is also doing
BP: the similar thing in section 3.5. What I am recommending is that
BP: the options that the I-D: draft-jang-mip6-hiopt-00.txt specifies
BP: in section 3 be included in section 3.5 of the WG I-D and be done.
BP: If you look at the title of the WG I-D, it says
BP: "MIP6-bootstrapping via DHCPv6..." which to me implies that it
BP: should specify how bootstrapping is done with DHCPv6 and the
BP: options that would be needed in DHCP to make this work. I know
BP: you would argue that if that were to be the case then the AAA
BP: aspects should also incorporated into the same. If it was a matter
BP: of only specifiying a couple of new AAA AVPs that could be a
BP: solution. However at the moment it appears that a more
BP: comprehensive AAA spec for Radius and Diameter are needed as seen
BP: from the AAA I-Ds mentioned above.

>
>
>> > Your above statement misses this point.
>> >
>> > Besides, while there is a standalone use for draft-jang-mip6-hiopt-
>> 00.txt,
>> 
>> What is the standalone use of draft-jang?
>
>Standalone use is the one that does not require all that AAA plumbing. For
>example, when you manually configure the DHCP servers with the MIP6
>information. 

BP: If you were to manually configure the DHCP server with the
BP: bootstrapping information, you could only bootstrap an MS when it
BP: is in its home network. But the manual configuration of the DHCP
BP: server scenario is not ruled out by incorporating these options in
BP: the WG I-D either. So I disagree that you need to specify the DHCP
BP: options separetely from the document that specifies the mechanism
BP: of  how bootstrapping is done with DHCP.

>
>
>> The WG I-D needs to specify the
>> DHCP options anyway. Why would that not be sufficient for any deployment
>> scenario that you have in mind?
>
>I think there is a misunderstanding. I was not saying that.

BP: Okay... 

>
>
>> > there is none for the RADIUS and Diameter specs we expect to document
>> > individually. Should we also merge those AAA documents with the others?
>> 
>> Are you refering to the Radius/Diameter mechanisms for obtaining the
>> bootstrap parameters and storing them in the DHCP server? You could
>> specify
>> those mechanisms independently of the fact that there is a specification
>> which explains how DHCP is used for bootstrapping and the DHCP options to
>> carry the bootstrap parameters between the MS and the DHCP server. So I
>> don't expect that those drafts also be merged with the current spec.
>
>
>You misunderstood me. Let me re-iterate what I had described on the list
>earlier:
>
>- The integrated bootstrapping solution depends on a number of protocol
>design work (1. DHCP options for HA discovery, 2. RADIUS attributes for HA
>discovery, 3. Diameter AVPs for HA discovery, 4. IKEv2 for HoA
>configuration, 5. RADIUS attributes for MIP6 authentication, 6. Diameter
>AVPs for MIP6 authentication) and description (7) of how all such protocols
>plumb together to yield so-called "MIP6 bootstrapping."
>
>Now, item 7 is described in
>draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt. All the others are
>currently described in separate documents, and that makes sense. Asking for
>1 and 7 be merged does not make sense. If it did, my questions was, why not
>merge the others as well. Do you see my point?

BP: I see your point... And I gave you my thoughts on the integration
BP: of AAA options as well in this document above. Elaborating:
BP: 2 & 3 are more than just specifying RADIUS attributes and Diameter
BP: AVPs. 
BP: 4 does not really apply. How IKEv2 is iused once you have the
BP: bootstrap parameters at the MN is specified in the split-scenario
BP: and can be reused.
BP: 5 & 6 are part of the interaction between HA and AAA and the
BP: requirements for this captured in the WG I-D
BP: draft-ietf-mip6-aaa-ha-goals-02, the intention of the WG being to
BP: develop AAA specifications separately.
BP: With the case of DHCP options, this is already covered in the
BP: existing WG I-D.

>
>> >
>> > Also, I'm not sure what specific concern you are raising with respect to
>> the
>> > quoted text below.
>> 
>> The concern that I have is the fact that the I-D specifies the DHCP
>> options
>> for boostrapping. The bootstrap parameters are somehow stored in the DHCP
>> server. The I-D is basically saying that how the parameters get into the
>> DHCP server are not in scope here except giving an example that manual
>> configuration or AAA can be used. So it is incomplete and unusable.
>
>
>With the same token, documents 2..6 are also incomplete. Even 7 is
>incomplete. It is the modular combination of these various protocol work
>that makes a complete picture, no single one can make.
>

BP: To implement a complete bootstrapping solution, yes you would need
BP: to refer to multiple documents. But it does not mean that for
BP: every option you have a separate spec. In this case, my argument
BP: yet again :) is that the WG I-D has a section for the DHCP options
BP: that are needed and the additional ones that are in draft-jang
BP: simply need to be incorporated into the WG doc.

BP: There are no hard-and-fast rules or guidelines
BP: which say that this is the way it should be done. If the DHCP
BP: options were to be specified separately, that would work as
BP: well. I am just recommending an approach that I believe in this
BP: case is optimal.


-Raj

>
>> What
>> you
>> say above is that there will be additional I-Ds coming to specify how that
>> is done. The current WG integrated scenario with DHCPv6 I-D has more
>> details
>> and explains at least how AAA is used. I guess manual configuration is
>> pretty straightforward and does not need secification. But in the case
>> when
>> the MS is roaming and attached to some visited network, how does it
>> bootstrap with DHCP? My concern is the fact that the I-D is incomplete and
>> it simply sweeps the issue under the mat by saying it is out of scope.
>
>Alper
>
>
>
>
>


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



From mip6-bounces@ietf.org Fri Aug 04 16:06:13 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G95vq-0004B1-FP; Fri, 04 Aug 2006 16:06:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G95vp-0004Aw-71
	for mip6@ietf.org; Fri, 04 Aug 2006 16:06:05 -0400
Received: from mout.perfora.net ([217.160.230.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G95vo-0006UL-PC
	for mip6@ietf.org; Fri, 04 Aug 2006 16:06:05 -0400
Received: from [85.97.7.241] (helo=IBM52A5038A94F)
	by mrelay.perfora.net (node=mrelayus1) with ESMTP (Nemesis),
	id 0MKp2t-1G95vg1ebo-0004Hl; Fri, 04 Aug 2006 16:06:04 -0400
From: "Alper Yegin" <alper.yegin@yegin.org>
To: "'Basavaraj Patil'" <basavaraj.patil@nokia.com>,
	<mip6@ietf.org>
Subject: RE: [Mip6] Recommendation for bootstrapping using DHCPv6
Date: Fri, 4 Aug 2006 23:05:50 +0300
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
In-Reply-To: <C0F8E079.20984%basavaraj.patil@nokia.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
Thread-Index: Aca1oaIQ4K1FzyGUEduPhAARJNUNiAA2bJdQAC3tKR8AB7hywAAkXbI5AAQcUPA=
Message-ID: <0MKp2t-1G95vg1ebo-0004Hl@mrelay.perfora.net>
X-Provags-ID: perfora.net abuse@perfora.net
	login:abf7a4bb310ea4dfc9b6841113e2970f
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 681e62a2ce9b0804b459fe780d892beb
Cc: 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Raj,

Your message simply tells me how we can combine the documents. It does not
say why this is a better idea than keeping them separate. More inlined
below.

> >> > "Having the options specified in a stand-along document will not add
> much
> >> > value."
> >> >
> >> > As we have been stating, draft-jang-mip6-hiopt-00.txt also has a use
> that
> >> > does not tie into the RADIUS-driven details -- the use where DHCP
> server
> >> can
> >> > be manually configured and has nothing to do with the AAA.
> >>
> >> But why do you believe that the WG I-D which is using DHCP is RADIUS
> driven
> >> only and nothing else?
> >
> >AAA is integral to the current solutions designed by the MIP6 WG for MIP6
> >bootstrapping.
> 
> BP: Yes. I think we agreed when this work began that the MN shared a
> BP: security association with an entity such as the AAA in the home
> BP: network and not the HA (which is what RFC3775 is based on). But
> BP: I dont see how the fact that AAA is an integral part of the
> BP: bootstrapping solution has anything to do with DHCP options 

Well, I was merely responding to your statement. Maybe I misunderstood what
you meant.


> other
> BP: than the fact that AAA messages are used to obtain information
> BP: such as the address of the HA and insert them in a DHCP
> BP: server. But that should be dealt with in the Dime WG (I-D:
> BP: draft-ietf-dime-mip6-integrated-00.txt) and the same with Radius
> BP: as specified in I-D: draft-chowdhury-mip6-radius-02.
> 
> >
> >> I mean it could just as well be used for the case
> >> where the bootstrapping information is manually configured in the DHCP
> >> server. What is needed are the DHCP options and the fact that the
> >> bootstrap
> >> parameters are available in the DHCP server either as a result of some
> AAA
> >> messages or manual configuration does not matter.
> >
> >Yes, this is exactly what the draft-jang is saying.
> 
> BP: I know. And my point is that the WG I-D:
> BP: draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt is also doing
> BP: the similar thing in section 3.5. 

No, it is not. WG I-D is describing the DHCP relay options, not the DHCP
options. I think we should move those to the other document as well.

> What I am recommending is that
> BP: the options that the I-D: draft-jang-mip6-hiopt-00.txt specifies
> BP: in section 3 be included in section 3.5 of the WG I-D and be done.
> BP: If you look at the title of the WG I-D, it says
> BP: "MIP6-bootstrapping via DHCPv6..." which to me implies that it

It was our mistake to name the document like that. You know, the integrated
solution involves EAP, RADIUS, Diameter, DHCP, IKEv2, etc. It is not fair to
name it after only one of the protocols involved. We shall fix the name, not
try to fit the content of the I-D to the mistaken name.

> BP: should specify how bootstrapping is done with DHCPv6 and the
> BP: options that would be needed in DHCP to make this work. I know
> BP: you would argue that if that were to be the case then the AAA
> BP: aspects should also incorporated into the same. If it was a matter
> BP: of only specifiying a couple of new AAA AVPs that could be a
> BP: solution. However at the moment it appears that a more
> BP: comprehensive AAA spec for Radius and Diameter are needed as seen
> BP: from the AAA I-Ds mentioned above.

This just tells me the amount of text for DHCP options is less than the
amount of text for AAA, hence the former should be merged and not the
latter. I think we should be more concerned about the modularity of our
specifications.

> >> > Your above statement misses this point.
> >> >
> >> > Besides, while there is a standalone use for draft-jang-mip6-hiopt-
> >> 00.txt,
> >>
> >> What is the standalone use of draft-jang?
> >
> >Standalone use is the one that does not require all that AAA plumbing.
> For
> >example, when you manually configure the DHCP servers with the MIP6
> >information.
> 
> BP: If you were to manually configure the DHCP server with the
> BP: bootstrapping information, you could only bootstrap an MS when it
> BP: is in its home network. 

Simply not true. You know DHCP runs across multiple IP hops, with the help
of DHCP relays. A MN may very well be connected to a foreign subnet and get
its configuration from a DHCP server in its home subnet.

> But the manual configuration of the DHCP
> BP: server scenario is not ruled out by incorporating these options in
> BP: the WG I-D either. So I disagree that you need to specify the DHCP
> BP: options separetely from the document that specifies the mechanism
> BP: of  how bootstrapping is done with DHCP.

Again, this is not "how bootstrapping is done with DHCP". This is "how
bootstrapping is done with EAP, RADIUS, Diameter, IKEv2, DHCP". The
integrated solution does not revolve around DHCP. DHCP is only used for HA
discovery component. MIP SA, and HoA are still handled by the other
protocols.

> >> The WG I-D needs to specify the
> >> DHCP options anyway. Why would that not be sufficient for any
> deployment
> >> scenario that you have in mind?
> >
> >I think there is a misunderstanding. I was not saying that.
> 
> BP: Okay...
> 
> >
> >
> >> > there is none for the RADIUS and Diameter specs we expect to document
> >> > individually. Should we also merge those AAA documents with the
> others?
> >>
> >> Are you refering to the Radius/Diameter mechanisms for obtaining the
> >> bootstrap parameters and storing them in the DHCP server? You could
> >> specify
> >> those mechanisms independently of the fact that there is a
> specification
> >> which explains how DHCP is used for bootstrapping and the DHCP options
> to
> >> carry the bootstrap parameters between the MS and the DHCP server. So I
> >> don't expect that those drafts also be merged with the current spec.
> >
> >
> >You misunderstood me. Let me re-iterate what I had described on the list
> >earlier:
> >
> >- The integrated bootstrapping solution depends on a number of protocol
> >design work (1. DHCP options for HA discovery, 2. RADIUS attributes for
> HA
> >discovery, 3. Diameter AVPs for HA discovery, 4. IKEv2 for HoA
> >configuration, 5. RADIUS attributes for MIP6 authentication, 6. Diameter
> >AVPs for MIP6 authentication) and description (7) of how all such
> protocols
> >plumb together to yield so-called "MIP6 bootstrapping."
> >
> >Now, item 7 is described in
> >draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt. All the others are
> >currently described in separate documents, and that makes sense. Asking
> for
> >1 and 7 be merged does not make sense. If it did, my questions was, why
> not
> >merge the others as well. Do you see my point?
> 
> BP: I see your point... And I gave you my thoughts on the integration
> BP: of AAA options as well in this document above. Elaborating:
> BP: 2 & 3 are more than just specifying RADIUS attributes and Diameter
> BP: AVPs.
> BP: 4 does not really apply. How IKEv2 is iused once you have the
> BP: bootstrap parameters at the MN is specified in the split-scenario
> BP: and can be reused.

That is not true. It is defined in draft-ietf-mip6-ikev2-ipsec-04 and simply
referred by the split-scenario document (right thing to do!).


> BP: 5 & 6 are part of the interaction between HA and AAA and the
> BP: requirements for this captured in the WG I-D
> BP: draft-ietf-mip6-aaa-ha-goals-02, the intention of the WG being to
> BP: develop AAA specifications separately.

Yes, that's the right thing to do.

> BP: With the case of DHCP options, this is already covered in the
> BP: existing WG I-D.
> 
> >
> >> >
> >> > Also, I'm not sure what specific concern you are raising with respect
> to
> >> the
> >> > quoted text below.
> >>
> >> The concern that I have is the fact that the I-D specifies the DHCP
> >> options
> >> for boostrapping. The bootstrap parameters are somehow stored in the
> DHCP
> >> server. The I-D is basically saying that how the parameters get into
> the
> >> DHCP server are not in scope here except giving an example that manual
> >> configuration or AAA can be used. So it is incomplete and unusable.
> >
> >
> >With the same token, documents 2..6 are also incomplete. Even 7 is
> >incomplete. It is the modular combination of these various protocol work
> >that makes a complete picture, no single one can make.
> >
> 
> BP: To implement a complete bootstrapping solution, yes you would need
> BP: to refer to multiple documents. But it does not mean that for
> BP: every option you have a separate spec.  In this case, my argument
> BP: yet again :) is that the WG I-D has a section for the DHCP options
> BP: that are needed and the additional ones that are in draft-jang
> BP: simply need to be incorporated into the WG doc.
> 
> BP: There are no hard-and-fast rules or guidelines
> BP: which say that this is the way it should be done. If the DHCP
> BP: options were to be specified separately, that would work as
> BP: well. 

I have yet to understand the fundamental problem with this approach. Do you
have any?

And I have a fundamental problem with arbitrarily merging one of the
protocol components with the document that aims plumbing those components.
My fundamental problem is, this component (more than the others) have uses
beyond this very specific plumbing. Given that we like designing protocols
that get used modularly (like the Lego pieces), it does not make sense to
clump an otherwise-independent protocol piece with a very specific
framework. There would be no gains but simply difficulty in referencing that
specific protocol component out of a specific framework when people need to
use it (but not the rest of the framework). 

> I am just recommending an approach that I believe in this
> BP: case is optimal.


Alper



> 
> 
> -Raj
> 
> >
> >> What
> >> you
> >> say above is that there will be additional I-Ds coming to specify how
> that
> >> is done. The current WG integrated scenario with DHCPv6 I-D has more
> >> details
> >> and explains at least how AAA is used. I guess manual configuration is
> >> pretty straightforward and does not need secification. But in the case
> >> when
> >> the MS is roaming and attached to some visited network, how does it
> >> bootstrap with DHCP? My concern is the fact that the I-D is incomplete
> and
> >> it simply sweeps the issue under the mat by saying it is out of scope.
> >
> >Alper
> >
> >
> >
> >
> >



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



From mip6-bounces@ietf.org Fri Aug 04 17:18:05 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G973Q-0001Su-IB; Fri, 04 Aug 2006 17:18:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G973P-0001Sp-U2
	for mip6@ietf.org; Fri, 04 Aug 2006 17:17:59 -0400
Received: from mgw-ext12.nokia.com ([131.228.20.171])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G973O-0006LT-Vy
	for mip6@ietf.org; Fri, 04 Aug 2006 17:17:59 -0400
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145])
	by mgw-ext12.nokia.com (Switch-3.1.8/Switch-3.1.7) with ESMTP id
	k74LHskx013536; Sat, 5 Aug 2006 00:17:57 +0300
Received: from daebh102.NOE.Nokia.com ([10.241.35.112]) by
	esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 5 Aug 2006 00:17:07 +0300
Received: from daebe101.NOE.Nokia.com ([10.241.35.113]) by
	daebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 4 Aug 2006 16:16:59 -0500
Received: from 172.19.244.182 ([172.19.244.182]) by daebe101.NOE.Nokia.com
	([10.241.35.113]) with Microsoft Exchange Server HTTP-DAV ; 
	Fri,  4 Aug 2006 21:16:58 +0000
User-Agent: Microsoft-Entourage/11.2.5.060620
Date: Fri, 04 Aug 2006 16:17:12 -0500
Subject: Re: [Mip6] Recommendation for bootstrapping using DHCPv6
From: Basavaraj Patil <basavaraj.patil@nokia.com>
To: ext Alper Yegin <alper.yegin@yegin.org>, <mip6@ietf.org>
Message-ID: <C0F92388.209E5%basavaraj.patil@nokia.com>
Thread-Topic: [Mip6] Recommendation for bootstrapping using DHCPv6
Thread-Index: Aca1oaIQ4K1FzyGUEduPhAARJNUNiAA2bJdQAC3tKR8AB7hywAAkXbI5AAQcUPAABeHFpw==
In-Reply-To: <0MKp2t-1G95vg1ebo-0004Hl@mrelay.perfora.net>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 04 Aug 2006 21:16:59.0126 (UTC)
	FILETIME=[52485160:01C6B80B]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c0aa019322dfce838bd8604f5a841b57
Cc: 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org


Alper,

The simple reason I recommended that the DHCP options specified in
draft-jang be combined with the WG I-D which is the solution for
Bootstrapping using DHCPv6 (I-D:
draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt) is because there is
already a section in the document which is intended for the DHCP options.
Doing two separate I-Ds IMO has no added value here. I am not convinced that
there are deployment scenarios that are enabled by specifying the DHCP
options separately (as I have stated in the earlier email as well).

And reiterating what I said earlier:
"
BP: There are no hard-and-fast rules or guidelines
BP: which say that this is the way it should be done. If the DHCP
BP: options were to be specified separately, that would work as
BP: well. I am just recommending an approach that I believe in this
BP: case is optimal.
"

That's it. Now, we may agree to disagree with this approach and that's fine.
I can issue a WG consensus call and resolve it based on what the view in the
WG is. Let me know.

-Raj

On 8/4/06 3:05 PM, "ext Alper Yegin" <alper.yegin@yegin.org> wrote:

> Raj,
> 
> Your message simply tells me how we can combine the documents. It does not
> say why this is a better idea than keeping them separate. More inlined
> below.
> 
>>>>> "Having the options specified in a stand-along document will not add
>> much
>>>>> value."
>>>>> 
>>>>> As we have been stating, draft-jang-mip6-hiopt-00.txt also has a use
>> that
>>>>> does not tie into the RADIUS-driven details -- the use where DHCP
>> server
>>>> can
>>>>> be manually configured and has nothing to do with the AAA.
>>>> 
>>>> But why do you believe that the WG I-D which is using DHCP is RADIUS
>> driven
>>>> only and nothing else?
>>> 
>>> AAA is integral to the current solutions designed by the MIP6 WG for MIP6
>>> bootstrapping.
>> 
>> BP: Yes. I think we agreed when this work began that the MN shared a
>> BP: security association with an entity such as the AAA in the home
>> BP: network and not the HA (which is what RFC3775 is based on). But
>> BP: I dont see how the fact that AAA is an integral part of the
>> BP: bootstrapping solution has anything to do with DHCP options
> 
> Well, I was merely responding to your statement. Maybe I misunderstood what
> you meant.
> 
> 
>> other
>> BP: than the fact that AAA messages are used to obtain information
>> BP: such as the address of the HA and insert them in a DHCP
>> BP: server. But that should be dealt with in the Dime WG (I-D:
>> BP: draft-ietf-dime-mip6-integrated-00.txt) and the same with Radius
>> BP: as specified in I-D: draft-chowdhury-mip6-radius-02.
>> 
>>> 
>>>> I mean it could just as well be used for the case
>>>> where the bootstrapping information is manually configured in the DHCP
>>>> server. What is needed are the DHCP options and the fact that the
>>>> bootstrap
>>>> parameters are available in the DHCP server either as a result of some
>> AAA
>>>> messages or manual configuration does not matter.
>>> 
>>> Yes, this is exactly what the draft-jang is saying.
>> 
>> BP: I know. And my point is that the WG I-D:
>> BP: draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt is also doing
>> BP: the similar thing in section 3.5.
> 
> No, it is not. WG I-D is describing the DHCP relay options, not the DHCP
> options. I think we should move those to the other document as well.
> 
>> What I am recommending is that
>> BP: the options that the I-D: draft-jang-mip6-hiopt-00.txt specifies
>> BP: in section 3 be included in section 3.5 of the WG I-D and be done.
>> BP: If you look at the title of the WG I-D, it says
>> BP: "MIP6-bootstrapping via DHCPv6..." which to me implies that it
> 
> It was our mistake to name the document like that. You know, the integrated
> solution involves EAP, RADIUS, Diameter, DHCP, IKEv2, etc. It is not fair to
> name it after only one of the protocols involved. We shall fix the name, not
> try to fit the content of the I-D to the mistaken name.
> 
>> BP: should specify how bootstrapping is done with DHCPv6 and the
>> BP: options that would be needed in DHCP to make this work. I know
>> BP: you would argue that if that were to be the case then the AAA
>> BP: aspects should also incorporated into the same. If it was a matter
>> BP: of only specifiying a couple of new AAA AVPs that could be a
>> BP: solution. However at the moment it appears that a more
>> BP: comprehensive AAA spec for Radius and Diameter are needed as seen
>> BP: from the AAA I-Ds mentioned above.
> 
> This just tells me the amount of text for DHCP options is less than the
> amount of text for AAA, hence the former should be merged and not the
> latter. I think we should be more concerned about the modularity of our
> specifications.
> 
>>>>> Your above statement misses this point.
>>>>> 
>>>>> Besides, while there is a standalone use for draft-jang-mip6-hiopt-
>>>> 00.txt,
>>>> 
>>>> What is the standalone use of draft-jang?
>>> 
>>> Standalone use is the one that does not require all that AAA plumbing.
>> For
>>> example, when you manually configure the DHCP servers with the MIP6
>>> information.
>> 
>> BP: If you were to manually configure the DHCP server with the
>> BP: bootstrapping information, you could only bootstrap an MS when it
>> BP: is in its home network.
> 
> Simply not true. You know DHCP runs across multiple IP hops, with the help
> of DHCP relays. A MN may very well be connected to a foreign subnet and get
> its configuration from a DHCP server in its home subnet.
> 
>> But the manual configuration of the DHCP
>> BP: server scenario is not ruled out by incorporating these options in
>> BP: the WG I-D either. So I disagree that you need to specify the DHCP
>> BP: options separetely from the document that specifies the mechanism
>> BP: of  how bootstrapping is done with DHCP.
> 
> Again, this is not "how bootstrapping is done with DHCP". This is "how
> bootstrapping is done with EAP, RADIUS, Diameter, IKEv2, DHCP". The
> integrated solution does not revolve around DHCP. DHCP is only used for HA
> discovery component. MIP SA, and HoA are still handled by the other
> protocols.
> 
>>>> The WG I-D needs to specify the
>>>> DHCP options anyway. Why would that not be sufficient for any
>> deployment
>>>> scenario that you have in mind?
>>> 
>>> I think there is a misunderstanding. I was not saying that.
>> 
>> BP: Okay...
>> 
>>> 
>>> 
>>>>> there is none for the RADIUS and Diameter specs we expect to document
>>>>> individually. Should we also merge those AAA documents with the
>> others?
>>>> 
>>>> Are you refering to the Radius/Diameter mechanisms for obtaining the
>>>> bootstrap parameters and storing them in the DHCP server? You could
>>>> specify
>>>> those mechanisms independently of the fact that there is a
>> specification
>>>> which explains how DHCP is used for bootstrapping and the DHCP options
>> to
>>>> carry the bootstrap parameters between the MS and the DHCP server. So I
>>>> don't expect that those drafts also be merged with the current spec.
>>> 
>>> 
>>> You misunderstood me. Let me re-iterate what I had described on the list
>>> earlier:
>>> 
>>> - The integrated bootstrapping solution depends on a number of protocol
>>> design work (1. DHCP options for HA discovery, 2. RADIUS attributes for
>> HA
>>> discovery, 3. Diameter AVPs for HA discovery, 4. IKEv2 for HoA
>>> configuration, 5. RADIUS attributes for MIP6 authentication, 6. Diameter
>>> AVPs for MIP6 authentication) and description (7) of how all such
>> protocols
>>> plumb together to yield so-called "MIP6 bootstrapping."
>>> 
>>> Now, item 7 is described in
>>> draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt. All the others are
>>> currently described in separate documents, and that makes sense. Asking
>> for
>>> 1 and 7 be merged does not make sense. If it did, my questions was, why
>> not
>>> merge the others as well. Do you see my point?
>> 
>> BP: I see your point... And I gave you my thoughts on the integration
>> BP: of AAA options as well in this document above. Elaborating:
>> BP: 2 & 3 are more than just specifying RADIUS attributes and Diameter
>> BP: AVPs.
>> BP: 4 does not really apply. How IKEv2 is iused once you have the
>> BP: bootstrap parameters at the MN is specified in the split-scenario
>> BP: and can be reused.
> 
> That is not true. It is defined in draft-ietf-mip6-ikev2-ipsec-04 and simply
> referred by the split-scenario document (right thing to do!).
> 
> 
>> BP: 5 & 6 are part of the interaction between HA and AAA and the
>> BP: requirements for this captured in the WG I-D
>> BP: draft-ietf-mip6-aaa-ha-goals-02, the intention of the WG being to
>> BP: develop AAA specifications separately.
> 
> Yes, that's the right thing to do.
> 
>> BP: With the case of DHCP options, this is already covered in the
>> BP: existing WG I-D.
>> 
>>> 
>>>>> 
>>>>> Also, I'm not sure what specific concern you are raising with respect
>> to
>>>> the
>>>>> quoted text below.
>>>> 
>>>> The concern that I have is the fact that the I-D specifies the DHCP
>>>> options
>>>> for boostrapping. The bootstrap parameters are somehow stored in the
>> DHCP
>>>> server. The I-D is basically saying that how the parameters get into
>> the
>>>> DHCP server are not in scope here except giving an example that manual
>>>> configuration or AAA can be used. So it is incomplete and unusable.
>>> 
>>> 
>>> With the same token, documents 2..6 are also incomplete. Even 7 is
>>> incomplete. It is the modular combination of these various protocol work
>>> that makes a complete picture, no single one can make.
>>> 
>> 
>> BP: To implement a complete bootstrapping solution, yes you would need
>> BP: to refer to multiple documents. But it does not mean that for
>> BP: every option you have a separate spec.  In this case, my argument
>> BP: yet again :) is that the WG I-D has a section for the DHCP options
>> BP: that are needed and the additional ones that are in draft-jang
>> BP: simply need to be incorporated into the WG doc.
>> 
>> BP: There are no hard-and-fast rules or guidelines
>> BP: which say that this is the way it should be done. If the DHCP
>> BP: options were to be specified separately, that would work as
>> BP: well. 
> 
> I have yet to understand the fundamental problem with this approach. Do you
> have any?
> 
> And I have a fundamental problem with arbitrarily merging one of the
> protocol components with the document that aims plumbing those components.
> My fundamental problem is, this component (more than the others) have uses
> beyond this very specific plumbing. Given that we like designing protocols
> that get used modularly (like the Lego pieces), it does not make sense to
> clump an otherwise-independent protocol piece with a very specific
> framework. There would be no gains but simply difficulty in referencing that
> specific protocol component out of a specific framework when people need to
> use it (but not the rest of the framework).
> 
>> I am just recommending an approach that I believe in this
>> BP: case is optimal.
> 
> 
> Alper
> 
> 
> 
>> 
>> 
>> -Raj
>> 
>>> 
>>>> What
>>>> you
>>>> say above is that there will be additional I-Ds coming to specify how
>> that
>>>> is done. The current WG integrated scenario with DHCPv6 I-D has more
>>>> details
>>>> and explains at least how AAA is used. I guess manual configuration is
>>>> pretty straightforward and does not need secification. But in the case
>>>> when
>>>> the MS is roaming and attached to some visited network, how does it
>>>> bootstrap with DHCP? My concern is the fact that the I-D is incomplete
>> and
>>>> it simply sweeps the issue under the mat by saying it is out of scope.
>>> 
>>> Alper
>>> 
>>> 
>>> 
>>> 
>>> 
> 
> 


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



From mip6-bounces@ietf.org Fri Aug 04 17:43:24 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G97S0-0003em-1x; Fri, 04 Aug 2006 17:43:24 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G97Rz-0003ee-3y
	for mip6@ietf.org; Fri, 04 Aug 2006 17:43:23 -0400
Received: from key1.docomolabs-usa.com ([216.98.102.225]
	helo=fridge.docomolabs-usa.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G97Rw-0003Wq-C9
	for mip6@ietf.org; Fri, 04 Aug 2006 17:43:23 -0400
Message-ID: <03c401c6b80c$c44dcff0$556015ac@dcml.docomolabsusa.com>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Alper Yegin" <alper.yegin@yegin.org>,
	"'Basavaraj Patil'" <basavaraj.patil@nokia.com>, <mip6@ietf.org>
References: <0MKp2t-1G95vg1ebo-0004Hl@mrelay.perfora.net>
Subject: Re: [Mip6] Recommendation for bootstrapping using DHCPv6
Date: Fri, 4 Aug 2006 14:27: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: 3.1 (+++)
X-Scan-Signature: 3be09dac38eaa50f02d21c7fcee1128c
Cc: 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Um, you know, we've been discussing this topic now for over a month. How 
about we do a consensus call and see what the WG wants to do with it? The 
document is, after all, a WG document and therefore the content is subject 
to WG consensus.

            jak

----- Original Message ----- 
From: "Alper Yegin" <alper.yegin@yegin.org>
To: "'Basavaraj Patil'" <basavaraj.patil@nokia.com>; <mip6@ietf.org>
Sent: Friday, August 04, 2006 1:05 PM
Subject: RE: [Mip6] Recommendation for bootstrapping using DHCPv6


> Raj,
>
> Your message simply tells me how we can combine the documents. It does not
> say why this is a better idea than keeping them separate. More inlined
> below.
>
>> >> > "Having the options specified in a stand-along document will not add
>> much
>> >> > value."
>> >> >
>> >> > As we have been stating, draft-jang-mip6-hiopt-00.txt also has a use
>> that
>> >> > does not tie into the RADIUS-driven details -- the use where DHCP
>> server
>> >> can
>> >> > be manually configured and has nothing to do with the AAA.
>> >>
>> >> But why do you believe that the WG I-D which is using DHCP is RADIUS
>> driven
>> >> only and nothing else?
>> >
>> >AAA is integral to the current solutions designed by the MIP6 WG for 
>> >MIP6
>> >bootstrapping.
>>
>> BP: Yes. I think we agreed when this work began that the MN shared a
>> BP: security association with an entity such as the AAA in the home
>> BP: network and not the HA (which is what RFC3775 is based on). But
>> BP: I dont see how the fact that AAA is an integral part of the
>> BP: bootstrapping solution has anything to do with DHCP options
>
> Well, I was merely responding to your statement. Maybe I misunderstood 
> what
> you meant.
>
>
>> other
>> BP: than the fact that AAA messages are used to obtain information
>> BP: such as the address of the HA and insert them in a DHCP
>> BP: server. But that should be dealt with in the Dime WG (I-D:
>> BP: draft-ietf-dime-mip6-integrated-00.txt) and the same with Radius
>> BP: as specified in I-D: draft-chowdhury-mip6-radius-02.
>>
>> >
>> >> I mean it could just as well be used for the case
>> >> where the bootstrapping information is manually configured in the DHCP
>> >> server. What is needed are the DHCP options and the fact that the
>> >> bootstrap
>> >> parameters are available in the DHCP server either as a result of some
>> AAA
>> >> messages or manual configuration does not matter.
>> >
>> >Yes, this is exactly what the draft-jang is saying.
>>
>> BP: I know. And my point is that the WG I-D:
>> BP: draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt is also doing
>> BP: the similar thing in section 3.5.
>
> No, it is not. WG I-D is describing the DHCP relay options, not the DHCP
> options. I think we should move those to the other document as well.
>
>> What I am recommending is that
>> BP: the options that the I-D: draft-jang-mip6-hiopt-00.txt specifies
>> BP: in section 3 be included in section 3.5 of the WG I-D and be done.
>> BP: If you look at the title of the WG I-D, it says
>> BP: "MIP6-bootstrapping via DHCPv6..." which to me implies that it
>
> It was our mistake to name the document like that. You know, the 
> integrated
> solution involves EAP, RADIUS, Diameter, DHCP, IKEv2, etc. It is not fair 
> to
> name it after only one of the protocols involved. We shall fix the name, 
> not
> try to fit the content of the I-D to the mistaken name.
>
>> BP: should specify how bootstrapping is done with DHCPv6 and the
>> BP: options that would be needed in DHCP to make this work. I know
>> BP: you would argue that if that were to be the case then the AAA
>> BP: aspects should also incorporated into the same. If it was a matter
>> BP: of only specifiying a couple of new AAA AVPs that could be a
>> BP: solution. However at the moment it appears that a more
>> BP: comprehensive AAA spec for Radius and Diameter are needed as seen
>> BP: from the AAA I-Ds mentioned above.
>
> This just tells me the amount of text for DHCP options is less than the
> amount of text for AAA, hence the former should be merged and not the
> latter. I think we should be more concerned about the modularity of our
> specifications.
>
>> >> > Your above statement misses this point.
>> >> >
>> >> > Besides, while there is a standalone use for draft-jang-mip6-hiopt-
>> >> 00.txt,
>> >>
>> >> What is the standalone use of draft-jang?
>> >
>> >Standalone use is the one that does not require all that AAA plumbing.
>> For
>> >example, when you manually configure the DHCP servers with the MIP6
>> >information.
>>
>> BP: If you were to manually configure the DHCP server with the
>> BP: bootstrapping information, you could only bootstrap an MS when it
>> BP: is in its home network.
>
> Simply not true. You know DHCP runs across multiple IP hops, with the help
> of DHCP relays. A MN may very well be connected to a foreign subnet and 
> get
> its configuration from a DHCP server in its home subnet.
>
>> But the manual configuration of the DHCP
>> BP: server scenario is not ruled out by incorporating these options in
>> BP: the WG I-D either. So I disagree that you need to specify the DHCP
>> BP: options separetely from the document that specifies the mechanism
>> BP: of  how bootstrapping is done with DHCP.
>
> Again, this is not "how bootstrapping is done with DHCP". This is "how
> bootstrapping is done with EAP, RADIUS, Diameter, IKEv2, DHCP". The
> integrated solution does not revolve around DHCP. DHCP is only used for HA
> discovery component. MIP SA, and HoA are still handled by the other
> protocols.
>
>> >> The WG I-D needs to specify the
>> >> DHCP options anyway. Why would that not be sufficient for any
>> deployment
>> >> scenario that you have in mind?
>> >
>> >I think there is a misunderstanding. I was not saying that.
>>
>> BP: Okay...
>>
>> >
>> >
>> >> > there is none for the RADIUS and Diameter specs we expect to 
>> >> > document
>> >> > individually. Should we also merge those AAA documents with the
>> others?
>> >>
>> >> Are you refering to the Radius/Diameter mechanisms for obtaining the
>> >> bootstrap parameters and storing them in the DHCP server? You could
>> >> specify
>> >> those mechanisms independently of the fact that there is a
>> specification
>> >> which explains how DHCP is used for bootstrapping and the DHCP options
>> to
>> >> carry the bootstrap parameters between the MS and the DHCP server. So 
>> >> I
>> >> don't expect that those drafts also be merged with the current spec.
>> >
>> >
>> >You misunderstood me. Let me re-iterate what I had described on the list
>> >earlier:
>> >
>> >- The integrated bootstrapping solution depends on a number of protocol
>> >design work (1. DHCP options for HA discovery, 2. RADIUS attributes for
>> HA
>> >discovery, 3. Diameter AVPs for HA discovery, 4. IKEv2 for HoA
>> >configuration, 5. RADIUS attributes for MIP6 authentication, 6. Diameter
>> >AVPs for MIP6 authentication) and description (7) of how all such
>> protocols
>> >plumb together to yield so-called "MIP6 bootstrapping."
>> >
>> >Now, item 7 is described in
>> >draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt. All the others are
>> >currently described in separate documents, and that makes sense. Asking
>> for
>> >1 and 7 be merged does not make sense. If it did, my questions was, why
>> not
>> >merge the others as well. Do you see my point?
>>
>> BP: I see your point... And I gave you my thoughts on the integration
>> BP: of AAA options as well in this document above. Elaborating:
>> BP: 2 & 3 are more than just specifying RADIUS attributes and Diameter
>> BP: AVPs.
>> BP: 4 does not really apply. How IKEv2 is iused once you have the
>> BP: bootstrap parameters at the MN is specified in the split-scenario
>> BP: and can be reused.
>
> That is not true. It is defined in draft-ietf-mip6-ikev2-ipsec-04 and 
> simply
> referred by the split-scenario document (right thing to do!).
>
>
>> BP: 5 & 6 are part of the interaction between HA and AAA and the
>> BP: requirements for this captured in the WG I-D
>> BP: draft-ietf-mip6-aaa-ha-goals-02, the intention of the WG being to
>> BP: develop AAA specifications separately.
>
> Yes, that's the right thing to do.
>
>> BP: With the case of DHCP options, this is already covered in the
>> BP: existing WG I-D.
>>
>> >
>> >> >
>> >> > Also, I'm not sure what specific concern you are raising with 
>> >> > respect
>> to
>> >> the
>> >> > quoted text below.
>> >>
>> >> The concern that I have is the fact that the I-D specifies the DHCP
>> >> options
>> >> for boostrapping. The bootstrap parameters are somehow stored in the
>> DHCP
>> >> server. The I-D is basically saying that how the parameters get into
>> the
>> >> DHCP server are not in scope here except giving an example that manual
>> >> configuration or AAA can be used. So it is incomplete and unusable.
>> >
>> >
>> >With the same token, documents 2..6 are also incomplete. Even 7 is
>> >incomplete. It is the modular combination of these various protocol work
>> >that makes a complete picture, no single one can make.
>> >
>>
>> BP: To implement a complete bootstrapping solution, yes you would need
>> BP: to refer to multiple documents. But it does not mean that for
>> BP: every option you have a separate spec.  In this case, my argument
>> BP: yet again :) is that the WG I-D has a section for the DHCP options
>> BP: that are needed and the additional ones that are in draft-jang
>> BP: simply need to be incorporated into the WG doc.
>>
>> BP: There are no hard-and-fast rules or guidelines
>> BP: which say that this is the way it should be done. If the DHCP
>> BP: options were to be specified separately, that would work as
>> BP: well.
>
> I have yet to understand the fundamental problem with this approach. Do 
> you
> have any?
>
> And I have a fundamental problem with arbitrarily merging one of the
> protocol components with the document that aims plumbing those components.
> My fundamental problem is, this component (more than the others) have uses
> beyond this very specific plumbing. Given that we like designing protocols
> that get used modularly (like the Lego pieces), it does not make sense to
> clump an otherwise-independent protocol piece with a very specific
> framework. There would be no gains but simply difficulty in referencing 
> that
> specific protocol component out of a specific framework when people need 
> to
> use it (but not the rest of the framework).
>
>> I am just recommending an approach that I believe in this
>> BP: case is optimal.
>
>
> Alper
>
>
>
>>
>>
>> -Raj
>>
>> >
>> >> What
>> >> you
>> >> say above is that there will be additional I-Ds coming to specify how
>> that
>> >> is done. The current WG integrated scenario with DHCPv6 I-D has more
>> >> details
>> >> and explains at least how AAA is used. I guess manual configuration is
>> >> pretty straightforward and does not need secification. But in the case
>> >> when
>> >> the MS is roaming and attached to some visited network, how does it
>> >> bootstrap with DHCP? My concern is the fact that the I-D is incomplete
>> and
>> >> it simply sweeps the issue under the mat by saying it is out of scope.
>> >
>> >Alper
>> >
>> >
>> >
>> >
>> >
>
>
>
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
> 



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



From mip6-bounces@ietf.org Fri Aug 04 18:56:00 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G98aD-0008EJ-6G; Fri, 04 Aug 2006 18:55:57 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G98aB-0008Cd-VR
	for mip6@ietf.org; Fri, 04 Aug 2006 18:55:55 -0400
Received: from mout.perfora.net ([217.160.230.41])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G98a9-00033w-DX
	for mip6@ietf.org; Fri, 04 Aug 2006 18:55:55 -0400
Received: from [85.97.7.241] (helo=IBM52A5038A94F)
	by mrelay.perfora.net (node=mrelayus0) with ESMTP (Nemesis),
	id 0MKoyl-1G98a310vg-0005XR; Fri, 04 Aug 2006 18:55:51 -0400
From: "Alper Yegin" <alper.yegin@yegin.org>
To: "'Basavaraj Patil'" <basavaraj.patil@nokia.com>,
	<mip6@ietf.org>
Subject: RE: [Mip6] Recommendation for bootstrapping using DHCPv6
Date: Sat, 5 Aug 2006 01:55:41 +0300
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
In-Reply-To: <C0F92388.209E5%basavaraj.patil@nokia.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
Thread-Index: Aca1oaIQ4K1FzyGUEduPhAARJNUNiAA2bJdQAC3tKR8AB7hywAAkXbI5AAQcUPAABeHFpwAC+CwQ
Message-ID: <0MKoyl-1G98a310vg-0005XR@mrelay.perfora.net>
X-Provags-ID: perfora.net abuse@perfora.net
	login:abf7a4bb310ea4dfc9b6841113e2970f
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1df8e4abc9851cb4adb45bd64d8514ae
Cc: 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Raj,

> I can issue a WG consensus call and resolve it based on what the view in
> the
> WG is. Let me know.

I think this is the best. 

Just to be clear, here are the two options on the table:

A: 
- move the "DHCP relay option" details from
draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt to
draft-jang-mip6-hiopt-00.txt
- rename "draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt" to
"draft-ietf-mip6-bootstrapping-integrated-01.txt" similar to its
counter-part (split).
- make the draft-jang-mip6-hiopt-00.txt as WG I-D as it is (already)
normatively referenced by the other document.

B:
- move the "DHCP option" details from draft-jang-mip6-hiopt-00.txt to
draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt.
- remove the normative reference to draft-jang-mip6-hiopt-00.txt and kill
that document.
- (I'd still recommend we drop the "-dhc" from the file and document name.
Apparently that was Vijay's idea :o )

Alper




> -----Original Message-----
> From: Basavaraj Patil [mailto:basavaraj.patil@nokia.com]
> Sent: Saturday, August 05, 2006 12:17 AM
> To: ext Alper Yegin; mip6@ietf.org
> Subject: Re: [Mip6] Recommendation for bootstrapping using DHCPv6
> 
> 
> Alper,
> 
> The simple reason I recommended that the DHCP options specified in
> draft-jang be combined with the WG I-D which is the solution for
> Bootstrapping using DHCPv6 (I-D:
> draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt) is because there is
> already a section in the document which is intended for the DHCP options.
> Doing two separate I-Ds IMO has no added value here. I am not convinced
> that
> there are deployment scenarios that are enabled by specifying the DHCP
> options separately (as I have stated in the earlier email as well).
> 
> And reiterating what I said earlier:
> "
> BP: There are no hard-and-fast rules or guidelines
> BP: which say that this is the way it should be done. If the DHCP
> BP: options were to be specified separately, that would work as
> BP: well. I am just recommending an approach that I believe in this
> BP: case is optimal.
> "
> 
> That's it. Now, we may agree to disagree with this approach and that's
> fine.
> I can issue a WG consensus call and resolve it based on what the view in
> the
> WG is. Let me know.
> 
> -Raj
> 
> On 8/4/06 3:05 PM, "ext Alper Yegin" <alper.yegin@yegin.org> wrote:
> 
> > Raj,
> >
> > Your message simply tells me how we can combine the documents. It does
> not
> > say why this is a better idea than keeping them separate. More inlined
> > below.
> >
> >>>>> "Having the options specified in a stand-along document will not add
> >> much
> >>>>> value."
> >>>>>
> >>>>> As we have been stating, draft-jang-mip6-hiopt-00.txt also has a use
> >> that
> >>>>> does not tie into the RADIUS-driven details -- the use where DHCP
> >> server
> >>>> can
> >>>>> be manually configured and has nothing to do with the AAA.
> >>>>
> >>>> But why do you believe that the WG I-D which is using DHCP is RADIUS
> >> driven
> >>>> only and nothing else?
> >>>
> >>> AAA is integral to the current solutions designed by the MIP6 WG for
> MIP6
> >>> bootstrapping.
> >>
> >> BP: Yes. I think we agreed when this work began that the MN shared a
> >> BP: security association with an entity such as the AAA in the home
> >> BP: network and not the HA (which is what RFC3775 is based on). But
> >> BP: I dont see how the fact that AAA is an integral part of the
> >> BP: bootstrapping solution has anything to do with DHCP options
> >
> > Well, I was merely responding to your statement. Maybe I misunderstood
> what
> > you meant.
> >
> >
> >> other
> >> BP: than the fact that AAA messages are used to obtain information
> >> BP: such as the address of the HA and insert them in a DHCP
> >> BP: server. But that should be dealt with in the Dime WG (I-D:
> >> BP: draft-ietf-dime-mip6-integrated-00.txt) and the same with Radius
> >> BP: as specified in I-D: draft-chowdhury-mip6-radius-02.
> >>
> >>>
> >>>> I mean it could just as well be used for the case
> >>>> where the bootstrapping information is manually configured in the
> DHCP
> >>>> server. What is needed are the DHCP options and the fact that the
> >>>> bootstrap
> >>>> parameters are available in the DHCP server either as a result of
> some
> >> AAA
> >>>> messages or manual configuration does not matter.
> >>>
> >>> Yes, this is exactly what the draft-jang is saying.
> >>
> >> BP: I know. And my point is that the WG I-D:
> >> BP: draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt is also doing
> >> BP: the similar thing in section 3.5.
> >
> > No, it is not. WG I-D is describing the DHCP relay options, not the DHCP
> > options. I think we should move those to the other document as well.
> >
> >> What I am recommending is that
> >> BP: the options that the I-D: draft-jang-mip6-hiopt-00.txt specifies
> >> BP: in section 3 be included in section 3.5 of the WG I-D and be done.
> >> BP: If you look at the title of the WG I-D, it says
> >> BP: "MIP6-bootstrapping via DHCPv6..." which to me implies that it
> >
> > It was our mistake to name the document like that. You know, the
> integrated
> > solution involves EAP, RADIUS, Diameter, DHCP, IKEv2, etc. It is not
> fair to
> > name it after only one of the protocols involved. We shall fix the name,
> not
> > try to fit the content of the I-D to the mistaken name.
> >
> >> BP: should specify how bootstrapping is done with DHCPv6 and the
> >> BP: options that would be needed in DHCP to make this work. I know
> >> BP: you would argue that if that were to be the case then the AAA
> >> BP: aspects should also incorporated into the same. If it was a matter
> >> BP: of only specifiying a couple of new AAA AVPs that could be a
> >> BP: solution. However at the moment it appears that a more
> >> BP: comprehensive AAA spec for Radius and Diameter are needed as seen
> >> BP: from the AAA I-Ds mentioned above.
> >
> > This just tells me the amount of text for DHCP options is less than the
> > amount of text for AAA, hence the former should be merged and not the
> > latter. I think we should be more concerned about the modularity of our
> > specifications.
> >
> >>>>> Your above statement misses this point.
> >>>>>
> >>>>> Besides, while there is a standalone use for draft-jang-mip6-hiopt-
> >>>> 00.txt,
> >>>>
> >>>> What is the standalone use of draft-jang?
> >>>
> >>> Standalone use is the one that does not require all that AAA plumbing.
> >> For
> >>> example, when you manually configure the DHCP servers with the MIP6
> >>> information.
> >>
> >> BP: If you were to manually configure the DHCP server with the
> >> BP: bootstrapping information, you could only bootstrap an MS when it
> >> BP: is in its home network.
> >
> > Simply not true. You know DHCP runs across multiple IP hops, with the
> help
> > of DHCP relays. A MN may very well be connected to a foreign subnet and
> get
> > its configuration from a DHCP server in its home subnet.
> >
> >> But the manual configuration of the DHCP
> >> BP: server scenario is not ruled out by incorporating these options in
> >> BP: the WG I-D either. So I disagree that you need to specify the DHCP
> >> BP: options separetely from the document that specifies the mechanism
> >> BP: of  how bootstrapping is done with DHCP.
> >
> > Again, this is not "how bootstrapping is done with DHCP". This is "how
> > bootstrapping is done with EAP, RADIUS, Diameter, IKEv2, DHCP". The
> > integrated solution does not revolve around DHCP. DHCP is only used for
> HA
> > discovery component. MIP SA, and HoA are still handled by the other
> > protocols.
> >
> >>>> The WG I-D needs to specify the
> >>>> DHCP options anyway. Why would that not be sufficient for any
> >> deployment
> >>>> scenario that you have in mind?
> >>>
> >>> I think there is a misunderstanding. I was not saying that.
> >>
> >> BP: Okay...
> >>
> >>>
> >>>
> >>>>> there is none for the RADIUS and Diameter specs we expect to
> document
> >>>>> individually. Should we also merge those AAA documents with the
> >> others?
> >>>>
> >>>> Are you refering to the Radius/Diameter mechanisms for obtaining the
> >>>> bootstrap parameters and storing them in the DHCP server? You could
> >>>> specify
> >>>> those mechanisms independently of the fact that there is a
> >> specification
> >>>> which explains how DHCP is used for bootstrapping and the DHCP
> options
> >> to
> >>>> carry the bootstrap parameters between the MS and the DHCP server. So
> I
> >>>> don't expect that those drafts also be merged with the current spec.
> >>>
> >>>
> >>> You misunderstood me. Let me re-iterate what I had described on the
> list
> >>> earlier:
> >>>
> >>> - The integrated bootstrapping solution depends on a number of
> protocol
> >>> design work (1. DHCP options for HA discovery, 2. RADIUS attributes
> for
> >> HA
> >>> discovery, 3. Diameter AVPs for HA discovery, 4. IKEv2 for HoA
> >>> configuration, 5. RADIUS attributes for MIP6 authentication, 6.
> Diameter
> >>> AVPs for MIP6 authentication) and description (7) of how all such
> >> protocols
> >>> plumb together to yield so-called "MIP6 bootstrapping."
> >>>
> >>> Now, item 7 is described in
> >>> draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt. All the others
> are
> >>> currently described in separate documents, and that makes sense.
> Asking
> >> for
> >>> 1 and 7 be merged does not make sense. If it did, my questions was,
> why
> >> not
> >>> merge the others as well. Do you see my point?
> >>
> >> BP: I see your point... And I gave you my thoughts on the integration
> >> BP: of AAA options as well in this document above. Elaborating:
> >> BP: 2 & 3 are more than just specifying RADIUS attributes and Diameter
> >> BP: AVPs.
> >> BP: 4 does not really apply. How IKEv2 is iused once you have the
> >> BP: bootstrap parameters at the MN is specified in the split-scenario
> >> BP: and can be reused.
> >
> > That is not true. It is defined in draft-ietf-mip6-ikev2-ipsec-04 and
> simply
> > referred by the split-scenario document (right thing to do!).
> >
> >
> >> BP: 5 & 6 are part of the interaction between HA and AAA and the
> >> BP: requirements for this captured in the WG I-D
> >> BP: draft-ietf-mip6-aaa-ha-goals-02, the intention of the WG being to
> >> BP: develop AAA specifications separately.
> >
> > Yes, that's the right thing to do.
> >
> >> BP: With the case of DHCP options, this is already covered in the
> >> BP: existing WG I-D.
> >>
> >>>
> >>>>>
> >>>>> Also, I'm not sure what specific concern you are raising with
> respect
> >> to
> >>>> the
> >>>>> quoted text below.
> >>>>
> >>>> The concern that I have is the fact that the I-D specifies the DHCP
> >>>> options
> >>>> for boostrapping. The bootstrap parameters are somehow stored in the
> >> DHCP
> >>>> server. The I-D is basically saying that how the parameters get into
> >> the
> >>>> DHCP server are not in scope here except giving an example that
> manual
> >>>> configuration or AAA can be used. So it is incomplete and unusable.
> >>>
> >>>
> >>> With the same token, documents 2..6 are also incomplete. Even 7 is
> >>> incomplete. It is the modular combination of these various protocol
> work
> >>> that makes a complete picture, no single one can make.
> >>>
> >>
> >> BP: To implement a complete bootstrapping solution, yes you would need
> >> BP: to refer to multiple documents. But it does not mean that for
> >> BP: every option you have a separate spec.  In this case, my argument
> >> BP: yet again :) is that the WG I-D has a section for the DHCP options
> >> BP: that are needed and the additional ones that are in draft-jang
> >> BP: simply need to be incorporated into the WG doc.
> >>
> >> BP: There are no hard-and-fast rules or guidelines
> >> BP: which say that this is the way it should be done. If the DHCP
> >> BP: options were to be specified separately, that would work as
> >> BP: well.
> >
> > I have yet to understand the fundamental problem with this approach. Do
> you
> > have any?
> >
> > And I have a fundamental problem with arbitrarily merging one of the
> > protocol components with the document that aims plumbing those
> components.
> > My fundamental problem is, this component (more than the others) have
> uses
> > beyond this very specific plumbing. Given that we like designing
> protocols
> > that get used modularly (like the Lego pieces), it does not make sense
> to
> > clump an otherwise-independent protocol piece with a very specific
> > framework. There would be no gains but simply difficulty in referencing
> that
> > specific protocol component out of a specific framework when people need
> to
> > use it (but not the rest of the framework).
> >
> >> I am just recommending an approach that I believe in this
> >> BP: case is optimal.
> >
> >
> > Alper
> >
> >
> >
> >>
> >>
> >> -Raj
> >>
> >>>
> >>>> What
> >>>> you
> >>>> say above is that there will be additional I-Ds coming to specify how
> >> that
> >>>> is done. The current WG integrated scenario with DHCPv6 I-D has more
> >>>> details
> >>>> and explains at least how AAA is used. I guess manual configuration
> is
> >>>> pretty straightforward and does not need secification. But in the
> case
> >>>> when
> >>>> the MS is roaming and attached to some visited network, how does it
> >>>> bootstrap with DHCP? My concern is the fact that the I-D is
> incomplete
> >> and
> >>>> it simply sweeps the issue under the mat by saying it is out of
scope.
> >>>
> >>> Alper
> >>>
> >>>
> >>>
> >>>
> >>>
> >
> >



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



From mip6-bounces@ietf.org Fri Aug 04 19:46:22 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G99Mw-0001mt-R6; Fri, 04 Aug 2006 19:46:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G99Mw-0001mo-1g
	for mip6@ietf.org; Fri, 04 Aug 2006 19:46:18 -0400
Received: from usaga01-in.huawei.com ([12.129.211.51])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G99Mt-0001Iq-Ew
	for mip6@ietf.org; Fri, 04 Aug 2006 19:46:18 -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 <0J3H0017DZ7QOP@usaga01-in.huawei.com> for
	mip6@ietf.org; Fri, 04 Aug 2006 16:43:03 -0700 (PDT)
Received: from Nakhjiri73701
	(c-24-17-254-79.hsd1.mn.comcast.net [24.17.254.79]) by
	usaga01-in.huawei.com
	(iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar  3 2004))
	with ESMTPA id <0J3H00JHWZ7MM0@usaga01-in.huawei.com> for mip6@ietf.org;
	Fri, 04 Aug 2006 16:43:02 -0700 (PDT)
Date: Fri, 04 Aug 2006 16:46:04 -0700
From: Madjid Nakhjiri <mnakhjiri@huawei.com>
Subject: RE: [Mip6] comments on AAA-HA-goals-02 or bootstrapping PS??
In-reply-to: <20060804162431.GA6864@ipv6-3.int-evry.fr>
To: 'Julien Bournelle' <julien.bournelle@int-evry.fr>
Message-id: <002101c6b820$2698cc10$02fda8c0@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-index: Aca34qs8xsqZYofPRTygQ4Xie8Oj5QAOxLRA
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 83867a50fd8f547996ccdaf89af24437
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi Julien,

There is some inconsistency in the AAA-HA-goals draft that could be
clarified if the concepts of home versus serving providers/authorizers
defined in the terminology section of the bootstrapping PS have been used
more persistently. Again, I am happy to provide the editorial changes once
we settle this:)

Looking at the bootstrapping paper a few things are clear:

1) ASPs do not deal with provisioning of mobility service, MSPs do. This
means an HA would be assigned by the MSP not by an ASP.

2) There is a concept of home versus serving provider versus authorizer.
This means a local HA in a serving/ foreign/ visited (pick one) would be
assigned by the "serving MSP" not by an ASP.

There is one error in my opinion in the bootstrapping ps section 5.1.2
(dynamic HA assignment):

"Local home agents

      The mobile node's MSP may want to allow the serving ASP to assign
      a local home agent for the mobile node."

It should say "...to allow serving MSP" not "ASP", since ASP is not in
charge of providing mobility service and that is where probably the
inconsistency starts??

What do you think?

R,

Madjid





-----Original Message-----
From: Julien Bournelle [mailto:julien.bournelle@int-evry.fr] 
Sent: Friday, August 04, 2006 9:25 AM
To: Madjid Nakhjiri
Cc: 'Julien Bournelle'; mip6@ietf.org
Subject: Re: [Mip6] comments on AAA-HA-goals-02

Hi madjid,

 I think that this discussion is more about our understanding of the
 bootstrapping-ps terminology. Maybe we should start a new thread about
 this.

 Julien


On Thu, Aug 03, 2006 at 04:37:44PM -0700, Madjid Nakhjiri wrote:
> Hi Julien, 
> 
> Thanks for the quick reply. 
> 
> 
> -----Original Message-----
> From: Julien Bournelle [mailto:julien.bournelle@int-evry.fr] 
> Sent: Thursday, August 03, 2006 7:22 AM
> To: Madjid Nakhjiri
> Cc: mip6@ietf.org
> Subject: Re: [Mip6] comments on AAA-HA-goals-02
> 
> Hi madjid,
> 
>  let me try to respond to your mail though some terminology issues are
more
> related to the
>  draft-ietf-mip6-bootstrapping-ps draft.
> 
> Madjid>>I actually find the terminology in the bootstrapping draft more
> consistent. 
> 
> > The network MSA to me symbolizes
> > the MSP-AAA server, while ASA symbolizes ASP-AAA server. 
> 
>  no, the MSA is administrative entity with whom the user has a contract
>  and thus credentials. The MSP effectively provides the MIP6 service to
>  the user. Thus the MSP may have to contact the MSA before providing the
>  service. 
> 
> Madjid>>Well, you are saying MSA has a contract with the user and has her
> credentials. To me it translates to a home AAA server or authentication
> server for the MSP. I think we need to make the distinction between home
MSA
> and visited MSA.
> Also, MSP is a service provider, but you are implying it does not have a
AAA
> server? At the bottom of your email you said MSP has a AAA server. I am
> confused now.
> The ASP is defined in the bootstrapping draft as an _operator_, but it is
> not clear whether MSP is an operator or just an entity like an HA. What is
> the real life correspondence of the MSP??
> I like to think MSP include both a HA and a AAA server (MSA).
> 
> > 
> > *        I see a hot spot provider or a 802.16d network without mobility
> > support as an ASP, while a IP enabled cellular or a WiMAX network as a
> > combination of ASP and MSP. To me assignment of HA falls into the MSP
> > service category, not ASP service category (I just confirmed this in
> > bootstrapping-ps section 7.1), so there are some statements in the draft
> as
> > far as an  ASP assigning an HA and I don't think those are appropriate
> based
> > on the terminology provided. 
> 
>  it depends if we are in the split or integrated scenario.
>  In the split scenario, we don't have ASP/ASA, only MSP/MSA. So the user
>  has an HA from the MSP.
> 
> Madjid>> Well, you do have ASP/ASA, it just that it is beyond MSP control.
> 
>  In the integrated scenario, if MSP=ASP, the user obtains an HA from the
>  MSP/ASP. 
> 
> 
> > 
> > *        Then there is the concept of home versus visited domain. I am
> > guessing "domain" to administrative domain (AAA domain). Traditionally
AAA
> > community is denoted as home and visited AAA servers, i.e. AAAH and
AAAV,
> > respectively. I just checked the bootstrapping-ps draft and that draft
> calls
> > uses the term "serving" instead of "visited", but still provides a
> > distinction between home versus serving MSP (MSPH and MSPS) and between
> home
> > versus serving ASP (ASPH and ASPS). Having said this, I think if the
group
> > is going to great length to separate ASP/ MSP and ASA/MSA, it also needs
> to
> > distinguish between the home versus visited domain for each of the
> > authorizers. So that MSAH refers to AAA server within home MSP (MSP-H)
and
> > MSAV or MSAS (pick one) to AAA server within visited or serving MSP
(MSP-V
> > or MSP-S). The same goes for ASAH and ASAV. This means Serving MSA is
not
> > the same as serving ASA. It is not proper to equate the access service
> > provider (ASP) with MSP-V the visited domain as it is implied in section
> > 4.2: "Mobile Node requests a home agent to the Access Service Provider
> > (ASP)". According to my understanding of the terminology of ASP, ASP has
> > nothing to anything to do with HA assignment. I think this can be easily
> > remedied by introducing MSAH and MSAS. Visited domain HA allocation can
be
> > formulated as "MN can request MSAH for an HA assignment within MSPS
after
> > authentication to MSAH and authorization of mobility service by the
> > MSAH/MSAS to MN".
> 
>  maybe my explanation below will answer to this paragraph ?
> 
> Madjid>>Well one point is ASP is an access provider, not a mobility
> provider, so ASP cannot grant an HA request nor can it assign one. So that
> sentence needs to be revised. The other issue is the lack of distinction
> between home and visited providers, ASP does not mean visited MSP!
> 
> > *        The same goes for another sentence in the same section saying
"..
> > Mobile Node can specify if it wants a home agent provided by the visited
> > domain (ASP) or by the home domain (ASA)", which seems to be mixing
> > (mobility and access service), (home and visited), (provider and
> authorizer)
> > all in the same sentence!!
> 
>  yes, that can be confusing. 
> 
> Madjid>>Well, if we stick to the terminology in the bootstrapping draft
and
> use "serving" and "visited" and clarify whether MSP is an operator or just
> an HA, things should fall into a place better. If you agree with my
> statements, I could help out with that.
> 
> > 
> > *        The other comment along the same line is about section 4.1,
where
> > it is stated a pool of HA s can rely on the home EAP server (I am
guessing
> > EAP server belonging to MSA-H, since this is split scenario) for
> > authentication. Here it is stated "It allows the roaming mobility case
in
> > which the MN obtains the mobility service in a different administrative
> > domain (MSP !=MSA). Here it seems that it is implied HA is part of MSP
> > function (appropriately), however, I am not sure if MSP and MSA can
imply
> > two administrative domains, to me administrative domain implies AAA
> domain,
> > so one would be MSA-H and another MSA-V, so an HA could be authorized
> within
> > MSA-V based on authentication to MSA-H and authorization by MSA-H.
> 
>  MSP has its own AAA server. MSA is the AAA server of the MN. 
>  Does it respond to your comment ?
> 
> Madjid>>the definition of MSA is "an authorizer that authorizes MIP6
> service". To me that is the AAA server of the MSP: a AAA server that
> authorizes MIP6 service within an MSP. Then you have the concept of home
> versus serving MSP or ASP and home versus serving MSA and ASA.
> The home-MSA can authorize MIP6 service within home MSP and has MN's
> credentials. The "MSA" alone is just like a "AAA server" alone, it does
not
> say home or visited AAA server.
> 
> > 
> > *        I also have an issue with the usage of term NAS in next to last
> > paragraph of section 3. NAS is really an access service agent (as the
name
> > implies) not a mobility service agent. NAS performs many functions
beyond
> > the AAA client function, which brings up two issues. 1) the sentence
".HA,
> > that can be seen as Network Access Server for MIP6", is only providing
> > confusion in this context, you may say that HA can be seen as Network
> > mobility server if you want but in a draft that has ASP and MSP
> everywhere.
> 
>  ok.
> 
> > 2) in the goals sections (5.1/ 5.2) , it is not mentioned anywhere that
> the
> > HA MUST act as a AAA client, is this a non-requirement, or is it
> implicitly
> > understood?  Especially G2.2 seems to imply this.
> 
>  I think it is implicitly understood. Do you think we should add a
>  statement on this ?
> 
> Madjid>>I think this is the first requirement for the HA within an HA-AAA
> goals draft. It tells the world what code to expect to have in the
compliant
> HA. Having it implicit is not a good thing.
> 
> > 
> > *        In 5.4 why is it a "MUST" for HA to be an EAP pass-through
> > authenticator? As long as HA receives its information from the AAA
server
> in
> > a secure fashion and both HA and AAA can identify the MN and its EAP
> session
> > uniquely, there is no reason for allocating HA and EAP pass-through EAP
> > authenticator in the same box.
> 
>  hmmm, the HA acts as a AAA client and MN uses IKEv2 with EAP to be
>  authenticated. So the HA MUST act as an EAP pass-through authenticator.
> 
>  Am I missing something ? do you think we should rephrase this ?
> 
> Madjid>> I don't think this is hard requirement. You may another AAA
client
> on the path EAP signaling with EAP server. Aren't you separating ASA and
> MSA?? HA is AAA client for MSP authorization but not necessarily the AAA
> client for every EAP authentication, may be I am missing something.
> The way to rephrase it is
> 
> "HA Should be able to act as EAP pass-through authenticator in the EAP
> process for IKEv2." Or something like that. I have to look at the split
> scenario doc explaining this.
> 
> > 
> > *        For section 4.2, Integrated scenario, I see that NAS gets MIP6
> conf
> > parameters from the AAAH, how does the HA receives the information it
> needs?
> 
>  In the integrated scenario based on DHCPv6, the MN gets HA info through
>  DHCP. Then we fall in the split scenario and the MN uses IKEv2 with the
>  HA. 
> 
> Madjid>> Let me do some more reading:)
> 
> Thanks,
> 
> Madjid
> 
>  Julien Bournelle
> 
> 
> 
> 

-- 
julien.bournelle at int-evry.fr



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



From mip6-bounces@ietf.org Fri Aug 04 22:26:54 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G9Bs4-0004Ex-9e; Fri, 04 Aug 2006 22:26:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G9Bs3-0004Es-Fe
	for mip6@ietf.org; Fri, 04 Aug 2006 22:26:35 -0400
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G9Bs2-0005wB-Nm
	for mip6@ietf.org; Fri, 04 Aug 2006 22:26:35 -0400
Received: from neophyte.qualcomm.com (neophyte.qualcomm.com [129.46.61.149])
	by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k752QVYg026329
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Fri, 4 Aug 2006 19:26:31 -0700
Received: from NAEXBR03.na.qualcomm.com (naexbr03.qualcomm.com
	[129.46.134.172])
	by neophyte.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	k752QTiq012628; Fri, 4 Aug 2006 19:26:29 -0700 (PDT)
Received: from NAEX14.na.qualcomm.com ([10.47.5.242]) by
	NAEXBR03.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 4 Aug 2006 19:26:28 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] Recommendation for bootstrapping using DHCPv6
Date: Fri, 4 Aug 2006 19:26:54 -0700
Message-ID: <7EB20EA0938B4D42A2D82689365C9B7A11D12D@NAEX14.na.qualcomm.com>
In-Reply-To: <03c401c6b80c$c44dcff0$556015ac@dcml.docomolabsusa.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] Recommendation for bootstrapping using DHCPv6
Thread-Index: Aca4EZkn7h56hQ63TcytBG2c6ya6DAAJMwCQ
From: "Soliman, Hesham" <hsoliman@qualcomm.com>
To: "James Kempf" <kempf@docomolabs-usa.com>,
	"Alper Yegin" <alper.yegin@yegin.org>,
	"Basavaraj Patil" <basavaraj.patil@nokia.com>, <mip6@ietf.org>
X-OriginalArrivalTime: 05 Aug 2006 02:26:28.0902 (UTC)
	FILETIME=[8EBB4460:01C6B836]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6fc5b1c74c5bed09a3a9da2884900dec
Cc: 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

I agree with James that this should be done through concensus. However,
the other issue that I find puzzling is the inconsistency of adding the
DHCP option formats in this document, while expecting the
Diameter/RADIUS AVPs/VSA to be done "somewhere else". Why is it ok for
AAA stuff to be done somewhere else and not DHCP?

Hesham=20

 > -----Original Message-----
 > From: James Kempf [mailto:kempf@docomolabs-usa.com]=20
 > Sent: Saturday, August 05, 2006 7:27 AM
 > To: Alper Yegin; 'Basavaraj Patil'; mip6@ietf.org
 > Subject: Re: [Mip6] Recommendation for bootstrapping using DHCPv6
 >=20
 > Um, you know, we've been discussing this topic now for over=20
 > a month. How=20
 > about we do a consensus call and see what the WG wants to do=20
 > with it? The=20
 > document is, after all, a WG document and therefore the=20
 > content is subject=20
 > to WG consensus.
 >=20
 >             jak
 >=20
 > ----- Original Message -----=20
 > From: "Alper Yegin" <alper.yegin@yegin.org>
 > To: "'Basavaraj Patil'" <basavaraj.patil@nokia.com>; <mip6@ietf.org>
 > Sent: Friday, August 04, 2006 1:05 PM
 > Subject: RE: [Mip6] Recommendation for bootstrapping using DHCPv6
 >=20
 >=20
 > > Raj,
 > >
 > > Your message simply tells me how we can combine the=20
 > documents. It does not
 > > say why this is a better idea than keeping them separate.=20
 > More inlined
 > > below.
 > >
 > >> >> > "Having the options specified in a stand-along=20
 > document will not add
 > >> much
 > >> >> > value."
 > >> >> >
 > >> >> > As we have been stating,=20
 > draft-jang-mip6-hiopt-00.txt also has a use
 > >> that
 > >> >> > does not tie into the RADIUS-driven details -- the=20
 > use where DHCP
 > >> server
 > >> >> can
 > >> >> > be manually configured and has nothing to do with the AAA.
 > >> >>
 > >> >> But why do you believe that the WG I-D which is using=20
 > DHCP is RADIUS
 > >> driven
 > >> >> only and nothing else?
 > >> >
 > >> >AAA is integral to the current solutions designed by the=20
 > MIP6 WG for=20
 > >> >MIP6
 > >> >bootstrapping.
 > >>
 > >> BP: Yes. I think we agreed when this work began that the=20
 > MN shared a
 > >> BP: security association with an entity such as the AAA=20
 > in the home
 > >> BP: network and not the HA (which is what RFC3775 is=20
 > based on). But
 > >> BP: I dont see how the fact that AAA is an integral part of the
 > >> BP: bootstrapping solution has anything to do with DHCP options
 > >
 > > Well, I was merely responding to your statement. Maybe I=20
 > misunderstood=20
 > > what
 > > you meant.
 > >
 > >
 > >> other
 > >> BP: than the fact that AAA messages are used to obtain information
 > >> BP: such as the address of the HA and insert them in a DHCP
 > >> BP: server. But that should be dealt with in the Dime WG (I-D:
 > >> BP: draft-ietf-dime-mip6-integrated-00.txt) and the same=20
 > with Radius
 > >> BP: as specified in I-D: draft-chowdhury-mip6-radius-02.
 > >>
 > >> >
 > >> >> I mean it could just as well be used for the case
 > >> >> where the bootstrapping information is manually=20
 > configured in the DHCP
 > >> >> server. What is needed are the DHCP options and the=20
 > fact that the
 > >> >> bootstrap
 > >> >> parameters are available in the DHCP server either as=20
 > a result of some
 > >> AAA
 > >> >> messages or manual configuration does not matter.
 > >> >
 > >> >Yes, this is exactly what the draft-jang is saying.
 > >>
 > >> BP: I know. And my point is that the WG I-D:
 > >> BP: draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt=20
 > is also doing
 > >> BP: the similar thing in section 3.5.
 > >
 > > No, it is not. WG I-D is describing the DHCP relay=20
 > options, not the DHCP
 > > options. I think we should move those to the other=20
 > document as well.
 > >
 > >> What I am recommending is that
 > >> BP: the options that the I-D:=20
 > draft-jang-mip6-hiopt-00.txt specifies
 > >> BP: in section 3 be included in section 3.5 of the WG I-D=20
 > and be done.
 > >> BP: If you look at the title of the WG I-D, it says
 > >> BP: "MIP6-bootstrapping via DHCPv6..." which to me implies that it
 > >
 > > It was our mistake to name the document like that. You know, the=20
 > > integrated
 > > solution involves EAP, RADIUS, Diameter, DHCP, IKEv2, etc.=20
 > It is not fair=20
 > > to
 > > name it after only one of the protocols involved. We shall=20
 > fix the name,=20
 > > not
 > > try to fit the content of the I-D to the mistaken name.
 > >
 > >> BP: should specify how bootstrapping is done with DHCPv6 and the
 > >> BP: options that would be needed in DHCP to make this work. I know
 > >> BP: you would argue that if that were to be the case then the AAA
 > >> BP: aspects should also incorporated into the same. If it=20
 > was a matter
 > >> BP: of only specifiying a couple of new AAA AVPs that could be a
 > >> BP: solution. However at the moment it appears that a more
 > >> BP: comprehensive AAA spec for Radius and Diameter are=20
 > needed as seen
 > >> BP: from the AAA I-Ds mentioned above.
 > >
 > > This just tells me the amount of text for DHCP options is=20
 > less than the
 > > amount of text for AAA, hence the former should be merged=20
 > and not the
 > > latter. I think we should be more concerned about the=20
 > modularity of our
 > > specifications.
 > >
 > >> >> > Your above statement misses this point.
 > >> >> >
 > >> >> > Besides, while there is a standalone use for=20
 > draft-jang-mip6-hiopt-
 > >> >> 00.txt,
 > >> >>
 > >> >> What is the standalone use of draft-jang?
 > >> >
 > >> >Standalone use is the one that does not require all that=20
 > AAA plumbing.
 > >> For
 > >> >example, when you manually configure the DHCP servers=20
 > with the MIP6
 > >> >information.
 > >>
 > >> BP: If you were to manually configure the DHCP server with the
 > >> BP: bootstrapping information, you could only bootstrap=20
 > an MS when it
 > >> BP: is in its home network.
 > >
 > > Simply not true. You know DHCP runs across multiple IP=20
 > hops, with the help
 > > of DHCP relays. A MN may very well be connected to a=20
 > foreign subnet and=20
 > > get
 > > its configuration from a DHCP server in its home subnet.
 > >
 > >> But the manual configuration of the DHCP
 > >> BP: server scenario is not ruled out by incorporating=20
 > these options in
 > >> BP: the WG I-D either. So I disagree that you need to=20
 > specify the DHCP
 > >> BP: options separetely from the document that specifies=20
 > the mechanism
 > >> BP: of  how bootstrapping is done with DHCP.
 > >
 > > Again, this is not "how bootstrapping is done with DHCP".=20
 > This is "how
 > > bootstrapping is done with EAP, RADIUS, Diameter, IKEv2, DHCP". The
 > > integrated solution does not revolve around DHCP. DHCP is=20
 > only used for HA
 > > discovery component. MIP SA, and HoA are still handled by the other
 > > protocols.
 > >
 > >> >> The WG I-D needs to specify the
 > >> >> DHCP options anyway. Why would that not be sufficient for any
 > >> deployment
 > >> >> scenario that you have in mind?
 > >> >
 > >> >I think there is a misunderstanding. I was not saying that.
 > >>
 > >> BP: Okay...
 > >>
 > >> >
 > >> >
 > >> >> > there is none for the RADIUS and Diameter specs we expect to=20
 > >> >> > document
 > >> >> > individually. Should we also merge those AAA=20
 > documents with the
 > >> others?
 > >> >>
 > >> >> Are you refering to the Radius/Diameter mechanisms for=20
 > obtaining the
 > >> >> bootstrap parameters and storing them in the DHCP=20
 > server? You could
 > >> >> specify
 > >> >> those mechanisms independently of the fact that there is a
 > >> specification
 > >> >> which explains how DHCP is used for bootstrapping and=20
 > the DHCP options
 > >> to
 > >> >> carry the bootstrap parameters between the MS and the=20
 > DHCP server. So=20
 > >> >> I
 > >> >> don't expect that those drafts also be merged with the=20
 > current spec.
 > >> >
 > >> >
 > >> >You misunderstood me. Let me re-iterate what I had=20
 > described on the list
 > >> >earlier:
 > >> >
 > >> >- The integrated bootstrapping solution depends on a=20
 > number of protocol
 > >> >design work (1. DHCP options for HA discovery, 2. RADIUS=20
 > attributes for
 > >> HA
 > >> >discovery, 3. Diameter AVPs for HA discovery, 4. IKEv2 for HoA
 > >> >configuration, 5. RADIUS attributes for MIP6=20
 > authentication, 6. Diameter
 > >> >AVPs for MIP6 authentication) and description (7) of how all such
 > >> protocols
 > >> >plumb together to yield so-called "MIP6 bootstrapping."
 > >> >
 > >> >Now, item 7 is described in
 > >> >draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt. All=20
 > the others are
 > >> >currently described in separate documents, and that=20
 > makes sense. Asking
 > >> for
 > >> >1 and 7 be merged does not make sense. If it did, my=20
 > questions was, why
 > >> not
 > >> >merge the others as well. Do you see my point?
 > >>
 > >> BP: I see your point... And I gave you my thoughts on the=20
 > integration
 > >> BP: of AAA options as well in this document above. Elaborating:
 > >> BP: 2 & 3 are more than just specifying RADIUS attributes=20
 > and Diameter
 > >> BP: AVPs.
 > >> BP: 4 does not really apply. How IKEv2 is iused once you have the
 > >> BP: bootstrap parameters at the MN is specified in the=20
 > split-scenario
 > >> BP: and can be reused.
 > >
 > > That is not true. It is defined in=20
 > draft-ietf-mip6-ikev2-ipsec-04 and=20
 > > simply
 > > referred by the split-scenario document (right thing to do!).
 > >
 > >
 > >> BP: 5 & 6 are part of the interaction between HA and AAA and the
 > >> BP: requirements for this captured in the WG I-D
 > >> BP: draft-ietf-mip6-aaa-ha-goals-02, the intention of the=20
 > WG being to
 > >> BP: develop AAA specifications separately.
 > >
 > > Yes, that's the right thing to do.
 > >
 > >> BP: With the case of DHCP options, this is already covered in the
 > >> BP: existing WG I-D.
 > >>
 > >> >
 > >> >> >
 > >> >> > Also, I'm not sure what specific concern you are=20
 > raising with=20
 > >> >> > respect
 > >> to
 > >> >> the
 > >> >> > quoted text below.
 > >> >>
 > >> >> The concern that I have is the fact that the I-D=20
 > specifies the DHCP
 > >> >> options
 > >> >> for boostrapping. The bootstrap parameters are somehow=20
 > stored in the
 > >> DHCP
 > >> >> server. The I-D is basically saying that how the=20
 > parameters get into
 > >> the
 > >> >> DHCP server are not in scope here except giving an=20
 > example that manual
 > >> >> configuration or AAA can be used. So it is incomplete=20
 > and unusable.
 > >> >
 > >> >
 > >> >With the same token, documents 2..6 are also incomplete.=20
 > Even 7 is
 > >> >incomplete. It is the modular combination of these=20
 > various protocol work
 > >> >that makes a complete picture, no single one can make.
 > >> >
 > >>
 > >> BP: To implement a complete bootstrapping solution, yes=20
 > you would need
 > >> BP: to refer to multiple documents. But it does not mean that for
 > >> BP: every option you have a separate spec.  In this case,=20
 > my argument
 > >> BP: yet again :) is that the WG I-D has a section for the=20
 > DHCP options
 > >> BP: that are needed and the additional ones that are in draft-jang
 > >> BP: simply need to be incorporated into the WG doc.
 > >>
 > >> BP: There are no hard-and-fast rules or guidelines
 > >> BP: which say that this is the way it should be done. If the DHCP
 > >> BP: options were to be specified separately, that would work as
 > >> BP: well.
 > >
 > > I have yet to understand the fundamental problem with this=20
 > approach. Do=20
 > > you
 > > have any?
 > >
 > > And I have a fundamental problem with arbitrarily merging=20
 > one of the
 > > protocol components with the document that aims plumbing=20
 > those components.
 > > My fundamental problem is, this component (more than the=20
 > others) have uses
 > > beyond this very specific plumbing. Given that we like=20
 > designing protocols
 > > that get used modularly (like the Lego pieces), it does=20
 > not make sense to
 > > clump an otherwise-independent protocol piece with a very specific
 > > framework. There would be no gains but simply difficulty=20
 > in referencing=20
 > > that
 > > specific protocol component out of a specific framework=20
 > when people need=20
 > > to
 > > use it (but not the rest of the framework).
 > >
 > >> I am just recommending an approach that I believe in this
 > >> BP: case is optimal.
 > >
 > >
 > > Alper
 > >
 > >
 > >
 > >>
 > >>
 > >> -Raj
 > >>
 > >> >
 > >> >> What
 > >> >> you
 > >> >> say above is that there will be additional I-Ds coming=20
 > to specify how
 > >> that
 > >> >> is done. The current WG integrated scenario with=20
 > DHCPv6 I-D has more
 > >> >> details
 > >> >> and explains at least how AAA is used. I guess manual=20
 > configuration is
 > >> >> pretty straightforward and does not need secification.=20
 > But in the case
 > >> >> when
 > >> >> the MS is roaming and attached to some visited=20
 > network, how does it
 > >> >> bootstrap with DHCP? My concern is the fact that the=20
 > I-D is incomplete
 > >> and
 > >> >> it simply sweeps the issue under the mat by saying it=20
 > is out of scope.
 > >> >
 > >> >Alper
 > >> >
 > >> >
 > >> >
 > >> >
 > >> >
 > >
 > >
 > >
 > > _______________________________________________
 > > Mip6 mailing list
 > > Mip6@ietf.org
 > > https://www1.ietf.org/mailman/listinfo/mip6
 > >=20
 >=20
 >=20
 >=20
 > _______________________________________________
 > Mip6 mailing list
 > Mip6@ietf.org
 > https://www1.ietf.org/mailman/listinfo/mip6
 >=20

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



From mip6-bounces@ietf.org Sat Aug 05 02:12:32 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G9FOS-0000Rm-3H; Sat, 05 Aug 2006 02:12:16 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G9FOQ-0000Pw-Op
	for mip6@ietf.org; Sat, 05 Aug 2006 02:12:14 -0400
Received: from mail1.azairenet.com ([66.92.223.4] helo=bart.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G9FOP-000667-TM
	for mip6@ietf.org; Sat, 05 Aug 2006 02:12:14 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] Recommendation for bootstrapping using DHCPv6
Date: Fri, 4 Aug 2006 23:12:12 -0700
Message-ID: <C8E1D942CB394746BE5CFEB7D97610E701D99485@bart.corp.azairenet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] Recommendation for bootstrapping using DHCPv6
Thread-Index: Aca4EZkn7h56hQ63TcytBG2c6ya6DAAJMwCQAAekdyA=
From: "Vijay Devarapalli" <Vijay.Devarapalli@AzaireNet.com>
To: "Soliman, Hesham" <hsoliman@qualcomm.com>,
	"James Kempf" <kempf@docomolabs-usa.com>,
	"Alper Yegin" <alper.yegin@yegin.org>,
	"Basavaraj Patil" <basavaraj.patil@nokia.com>, <mip6@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 22e211536bda974b2dcf811522dc525d
Cc: 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi Hesham,

AAA extensions were needed for the split scenario and
integrated scenario. some are common. There are some=20
common AVPs/attributes for NAS-AAA and HA-AAAH=20
interfaces. also the AAA extensions can be used with=20
RFC 4285, not just IKEv2/IPsec. from the beginning it=20
was recognized that the expertise for the AAA=20
extensions existed in the respective RADIUS and=20
Diameter WGs.=20

OTOH, defining new DHCP options can be done in any WG.=20
we checked with Ralph. all was needed was just a review
from the DHC WG before the document was last called.

Vijay

> -----Original Message-----
> From: Soliman, Hesham [mailto:hsoliman@qualcomm.com]=20
> Sent: Friday, August 04, 2006 7:27 PM
> To: James Kempf; Alper Yegin; Basavaraj Patil; mip6@ietf.org
> Subject: RE: [Mip6] Recommendation for bootstrapping using DHCPv6
>=20
> I agree with James that this should be done through=20
> concensus. However,
> the other issue that I find puzzling is the inconsistency of=20
> adding the
> DHCP option formats in this document, while expecting the
> Diameter/RADIUS AVPs/VSA to be done "somewhere else". Why is it ok for
> AAA stuff to be done somewhere else and not DHCP?
>=20
> Hesham=20
>=20
>  > -----Original Message-----
>  > From: James Kempf [mailto:kempf@docomolabs-usa.com]=20
>  > Sent: Saturday, August 05, 2006 7:27 AM
>  > To: Alper Yegin; 'Basavaraj Patil'; mip6@ietf.org
>  > Subject: Re: [Mip6] Recommendation for bootstrapping using DHCPv6
>  >=20
>  > Um, you know, we've been discussing this topic now for over=20
>  > a month. How=20
>  > about we do a consensus call and see what the WG wants to do=20
>  > with it? The=20
>  > document is, after all, a WG document and therefore the=20
>  > content is subject=20
>  > to WG consensus.
>  >=20
>  >             jak
>  >=20
>  > ----- Original Message -----=20
>  > From: "Alper Yegin" <alper.yegin@yegin.org>
>  > To: "'Basavaraj Patil'" <basavaraj.patil@nokia.com>;=20
> <mip6@ietf.org>
>  > Sent: Friday, August 04, 2006 1:05 PM
>  > Subject: RE: [Mip6] Recommendation for bootstrapping using DHCPv6
>  >=20
>  >=20
>  > > Raj,
>  > >
>  > > Your message simply tells me how we can combine the=20
>  > documents. It does not
>  > > say why this is a better idea than keeping them separate.=20
>  > More inlined
>  > > below.
>  > >
>  > >> >> > "Having the options specified in a stand-along=20
>  > document will not add
>  > >> much
>  > >> >> > value."
>  > >> >> >
>  > >> >> > As we have been stating,=20
>  > draft-jang-mip6-hiopt-00.txt also has a use
>  > >> that
>  > >> >> > does not tie into the RADIUS-driven details -- the=20
>  > use where DHCP
>  > >> server
>  > >> >> can
>  > >> >> > be manually configured and has nothing to do with the AAA.
>  > >> >>
>  > >> >> But why do you believe that the WG I-D which is using=20
>  > DHCP is RADIUS
>  > >> driven
>  > >> >> only and nothing else?
>  > >> >
>  > >> >AAA is integral to the current solutions designed by the=20
>  > MIP6 WG for=20
>  > >> >MIP6
>  > >> >bootstrapping.
>  > >>
>  > >> BP: Yes. I think we agreed when this work began that the=20
>  > MN shared a
>  > >> BP: security association with an entity such as the AAA=20
>  > in the home
>  > >> BP: network and not the HA (which is what RFC3775 is=20
>  > based on). But
>  > >> BP: I dont see how the fact that AAA is an integral part of the
>  > >> BP: bootstrapping solution has anything to do with DHCP options
>  > >
>  > > Well, I was merely responding to your statement. Maybe I=20
>  > misunderstood=20
>  > > what
>  > > you meant.
>  > >
>  > >
>  > >> other
>  > >> BP: than the fact that AAA messages are used to obtain=20
> information
>  > >> BP: such as the address of the HA and insert them in a DHCP
>  > >> BP: server. But that should be dealt with in the Dime WG (I-D:
>  > >> BP: draft-ietf-dime-mip6-integrated-00.txt) and the same=20
>  > with Radius
>  > >> BP: as specified in I-D: draft-chowdhury-mip6-radius-02.
>  > >>
>  > >> >
>  > >> >> I mean it could just as well be used for the case
>  > >> >> where the bootstrapping information is manually=20
>  > configured in the DHCP
>  > >> >> server. What is needed are the DHCP options and the=20
>  > fact that the
>  > >> >> bootstrap
>  > >> >> parameters are available in the DHCP server either as=20
>  > a result of some
>  > >> AAA
>  > >> >> messages or manual configuration does not matter.
>  > >> >
>  > >> >Yes, this is exactly what the draft-jang is saying.
>  > >>
>  > >> BP: I know. And my point is that the WG I-D:
>  > >> BP: draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt=20
>  > is also doing
>  > >> BP: the similar thing in section 3.5.
>  > >
>  > > No, it is not. WG I-D is describing the DHCP relay=20
>  > options, not the DHCP
>  > > options. I think we should move those to the other=20
>  > document as well.
>  > >
>  > >> What I am recommending is that
>  > >> BP: the options that the I-D:=20
>  > draft-jang-mip6-hiopt-00.txt specifies
>  > >> BP: in section 3 be included in section 3.5 of the WG I-D=20
>  > and be done.
>  > >> BP: If you look at the title of the WG I-D, it says
>  > >> BP: "MIP6-bootstrapping via DHCPv6..." which to me=20
> implies that it
>  > >
>  > > It was our mistake to name the document like that. You know, the=20
>  > > integrated
>  > > solution involves EAP, RADIUS, Diameter, DHCP, IKEv2, etc.=20
>  > It is not fair=20
>  > > to
>  > > name it after only one of the protocols involved. We shall=20
>  > fix the name,=20
>  > > not
>  > > try to fit the content of the I-D to the mistaken name.
>  > >
>  > >> BP: should specify how bootstrapping is done with DHCPv6 and the
>  > >> BP: options that would be needed in DHCP to make this=20
> work. I know
>  > >> BP: you would argue that if that were to be the case=20
> then the AAA
>  > >> BP: aspects should also incorporated into the same. If it=20
>  > was a matter
>  > >> BP: of only specifiying a couple of new AAA AVPs that could be a
>  > >> BP: solution. However at the moment it appears that a more
>  > >> BP: comprehensive AAA spec for Radius and Diameter are=20
>  > needed as seen
>  > >> BP: from the AAA I-Ds mentioned above.
>  > >
>  > > This just tells me the amount of text for DHCP options is=20
>  > less than the
>  > > amount of text for AAA, hence the former should be merged=20
>  > and not the
>  > > latter. I think we should be more concerned about the=20
>  > modularity of our
>  > > specifications.
>  > >
>  > >> >> > Your above statement misses this point.
>  > >> >> >
>  > >> >> > Besides, while there is a standalone use for=20
>  > draft-jang-mip6-hiopt-
>  > >> >> 00.txt,
>  > >> >>
>  > >> >> What is the standalone use of draft-jang?
>  > >> >
>  > >> >Standalone use is the one that does not require all that=20
>  > AAA plumbing.
>  > >> For
>  > >> >example, when you manually configure the DHCP servers=20
>  > with the MIP6
>  > >> >information.
>  > >>
>  > >> BP: If you were to manually configure the DHCP server with the
>  > >> BP: bootstrapping information, you could only bootstrap=20
>  > an MS when it
>  > >> BP: is in its home network.
>  > >
>  > > Simply not true. You know DHCP runs across multiple IP=20
>  > hops, with the help
>  > > of DHCP relays. A MN may very well be connected to a=20
>  > foreign subnet and=20
>  > > get
>  > > its configuration from a DHCP server in its home subnet.
>  > >
>  > >> But the manual configuration of the DHCP
>  > >> BP: server scenario is not ruled out by incorporating=20
>  > these options in
>  > >> BP: the WG I-D either. So I disagree that you need to=20
>  > specify the DHCP
>  > >> BP: options separetely from the document that specifies=20
>  > the mechanism
>  > >> BP: of  how bootstrapping is done with DHCP.
>  > >
>  > > Again, this is not "how bootstrapping is done with DHCP".=20
>  > This is "how
>  > > bootstrapping is done with EAP, RADIUS, Diameter, IKEv2,=20
> DHCP". The
>  > > integrated solution does not revolve around DHCP. DHCP is=20
>  > only used for HA
>  > > discovery component. MIP SA, and HoA are still handled=20
> by the other
>  > > protocols.
>  > >
>  > >> >> The WG I-D needs to specify the
>  > >> >> DHCP options anyway. Why would that not be sufficient for any
>  > >> deployment
>  > >> >> scenario that you have in mind?
>  > >> >
>  > >> >I think there is a misunderstanding. I was not saying that.
>  > >>
>  > >> BP: Okay...
>  > >>
>  > >> >
>  > >> >
>  > >> >> > there is none for the RADIUS and Diameter specs we=20
> expect to=20
>  > >> >> > document
>  > >> >> > individually. Should we also merge those AAA=20
>  > documents with the
>  > >> others?
>  > >> >>
>  > >> >> Are you refering to the Radius/Diameter mechanisms for=20
>  > obtaining the
>  > >> >> bootstrap parameters and storing them in the DHCP=20
>  > server? You could
>  > >> >> specify
>  > >> >> those mechanisms independently of the fact that there is a
>  > >> specification
>  > >> >> which explains how DHCP is used for bootstrapping and=20
>  > the DHCP options
>  > >> to
>  > >> >> carry the bootstrap parameters between the MS and the=20
>  > DHCP server. So=20
>  > >> >> I
>  > >> >> don't expect that those drafts also be merged with the=20
>  > current spec.
>  > >> >
>  > >> >
>  > >> >You misunderstood me. Let me re-iterate what I had=20
>  > described on the list
>  > >> >earlier:
>  > >> >
>  > >> >- The integrated bootstrapping solution depends on a=20
>  > number of protocol
>  > >> >design work (1. DHCP options for HA discovery, 2. RADIUS=20
>  > attributes for
>  > >> HA
>  > >> >discovery, 3. Diameter AVPs for HA discovery, 4. IKEv2 for HoA
>  > >> >configuration, 5. RADIUS attributes for MIP6=20
>  > authentication, 6. Diameter
>  > >> >AVPs for MIP6 authentication) and description (7) of=20
> how all such
>  > >> protocols
>  > >> >plumb together to yield so-called "MIP6 bootstrapping."
>  > >> >
>  > >> >Now, item 7 is described in
>  > >> >draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt. All=20
>  > the others are
>  > >> >currently described in separate documents, and that=20
>  > makes sense. Asking
>  > >> for
>  > >> >1 and 7 be merged does not make sense. If it did, my=20
>  > questions was, why
>  > >> not
>  > >> >merge the others as well. Do you see my point?
>  > >>
>  > >> BP: I see your point... And I gave you my thoughts on the=20
>  > integration
>  > >> BP: of AAA options as well in this document above. Elaborating:
>  > >> BP: 2 & 3 are more than just specifying RADIUS attributes=20
>  > and Diameter
>  > >> BP: AVPs.
>  > >> BP: 4 does not really apply. How IKEv2 is iused once=20
> you have the
>  > >> BP: bootstrap parameters at the MN is specified in the=20
>  > split-scenario
>  > >> BP: and can be reused.
>  > >
>  > > That is not true. It is defined in=20
>  > draft-ietf-mip6-ikev2-ipsec-04 and=20
>  > > simply
>  > > referred by the split-scenario document (right thing to do!).
>  > >
>  > >
>  > >> BP: 5 & 6 are part of the interaction between HA and AAA and the
>  > >> BP: requirements for this captured in the WG I-D
>  > >> BP: draft-ietf-mip6-aaa-ha-goals-02, the intention of the=20
>  > WG being to
>  > >> BP: develop AAA specifications separately.
>  > >
>  > > Yes, that's the right thing to do.
>  > >
>  > >> BP: With the case of DHCP options, this is already=20
> covered in the
>  > >> BP: existing WG I-D.
>  > >>
>  > >> >
>  > >> >> >
>  > >> >> > Also, I'm not sure what specific concern you are=20
>  > raising with=20
>  > >> >> > respect
>  > >> to
>  > >> >> the
>  > >> >> > quoted text below.
>  > >> >>
>  > >> >> The concern that I have is the fact that the I-D=20
>  > specifies the DHCP
>  > >> >> options
>  > >> >> for boostrapping. The bootstrap parameters are somehow=20
>  > stored in the
>  > >> DHCP
>  > >> >> server. The I-D is basically saying that how the=20
>  > parameters get into
>  > >> the
>  > >> >> DHCP server are not in scope here except giving an=20
>  > example that manual
>  > >> >> configuration or AAA can be used. So it is incomplete=20
>  > and unusable.
>  > >> >
>  > >> >
>  > >> >With the same token, documents 2..6 are also incomplete.=20
>  > Even 7 is
>  > >> >incomplete. It is the modular combination of these=20
>  > various protocol work
>  > >> >that makes a complete picture, no single one can make.
>  > >> >
>  > >>
>  > >> BP: To implement a complete bootstrapping solution, yes=20
>  > you would need
>  > >> BP: to refer to multiple documents. But it does not=20
> mean that for
>  > >> BP: every option you have a separate spec.  In this case,=20
>  > my argument
>  > >> BP: yet again :) is that the WG I-D has a section for the=20
>  > DHCP options
>  > >> BP: that are needed and the additional ones that are in=20
> draft-jang
>  > >> BP: simply need to be incorporated into the WG doc.
>  > >>
>  > >> BP: There are no hard-and-fast rules or guidelines
>  > >> BP: which say that this is the way it should be done.=20
> If the DHCP
>  > >> BP: options were to be specified separately, that would work as
>  > >> BP: well.
>  > >
>  > > I have yet to understand the fundamental problem with this=20
>  > approach. Do=20
>  > > you
>  > > have any?
>  > >
>  > > And I have a fundamental problem with arbitrarily merging=20
>  > one of the
>  > > protocol components with the document that aims plumbing=20
>  > those components.
>  > > My fundamental problem is, this component (more than the=20
>  > others) have uses
>  > > beyond this very specific plumbing. Given that we like=20
>  > designing protocols
>  > > that get used modularly (like the Lego pieces), it does=20
>  > not make sense to
>  > > clump an otherwise-independent protocol piece with a=20
> very specific
>  > > framework. There would be no gains but simply difficulty=20
>  > in referencing=20
>  > > that
>  > > specific protocol component out of a specific framework=20
>  > when people need=20
>  > > to
>  > > use it (but not the rest of the framework).
>  > >
>  > >> I am just recommending an approach that I believe in this
>  > >> BP: case is optimal.
>  > >
>  > >
>  > > Alper
>  > >
>  > >
>  > >
>  > >>
>  > >>
>  > >> -Raj
>  > >>
>  > >> >
>  > >> >> What
>  > >> >> you
>  > >> >> say above is that there will be additional I-Ds coming=20
>  > to specify how
>  > >> that
>  > >> >> is done. The current WG integrated scenario with=20
>  > DHCPv6 I-D has more
>  > >> >> details
>  > >> >> and explains at least how AAA is used. I guess manual=20
>  > configuration is
>  > >> >> pretty straightforward and does not need secification.=20
>  > But in the case
>  > >> >> when
>  > >> >> the MS is roaming and attached to some visited=20
>  > network, how does it
>  > >> >> bootstrap with DHCP? My concern is the fact that the=20
>  > I-D is incomplete
>  > >> and
>  > >> >> it simply sweeps the issue under the mat by saying it=20
>  > is out of scope.
>  > >> >
>  > >> >Alper
>  > >> >
>  > >> >
>  > >> >
>  > >> >
>  > >> >
>  > >
>  > >
>  > >
>  > > _______________________________________________
>  > > Mip6 mailing list
>  > > Mip6@ietf.org
>  > > https://www1.ietf.org/mailman/listinfo/mip6
>  > >=20
>  >=20
>  >=20
>  >=20
>  > _______________________________________________
>  > Mip6 mailing list
>  > Mip6@ietf.org
>  > https://www1.ietf.org/mailman/listinfo/mip6
>  >=20
>=20
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
>=20

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



From mip6-bounces@ietf.org Sat Aug 05 07:44:45 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1G9Ka5-0001QB-Mg; Sat, 05 Aug 2006 07:44:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1G9Ka4-0001Q6-1Y
	for mip6@ietf.org; Sat, 05 Aug 2006 07:44:36 -0400
Received: from smtp2.int-evry.fr ([157.159.10.45])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G9Ka1-0006C5-AS
	for mip6@ietf.org; Sat, 05 Aug 2006 07:44:36 -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 1B4472FE52;
	Sat,  5 Aug 2006 13:44:31 +0200 (CEST)
Received: from jb by ipv6-3.int-evry.fr with local (Exim 4.52)
	id 1G9KcD-0001vR-Ep; Sat, 05 Aug 2006 13:46:49 +0200
Date: Sat, 5 Aug 2006 13:46:49 +0200
From: Julien Bournelle <julien.bournelle@int-evry.fr>
To: Madjid Nakhjiri <mnakhjiri@huawei.com>
Subject: Re: [Mip6] comments on AAA-HA-goals-02 or bootstrapping PS??
Message-ID: <20060805114649.GA7397@ipv6-3.int-evry.fr>
References: <20060804162431.GA6864@ipv6-3.int-evry.fr>
	<002101c6b820$2698cc10$02fda8c0@china.huawei.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <002101c6b820$2698cc10$02fda8c0@china.huawei.com>
User-Agent: Mutt/1.5.9i
X-INT-MailScanner-Information: Please contact the ISP for more information
X-INT-MailScanner: Found to be clean
X-INT-MailScanner-MCPCheck: 
X-INT-MailScanner-SpamCheck: 
X-MailScanner-From: jb@int-evry.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: abda3837e791065a13ac6f11cf8e625a
Cc: 'Julien Bournelle' <julien.bournelle@int-evry.fr>, mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi madjid,

On Fri, Aug 04, 2006 at 04:46:04PM -0700, Madjid Nakhjiri wrote:
> Hi Julien,
> 
> There is some inconsistency in the AAA-HA-goals draft that could be
> clarified if the concepts of home versus serving providers/authorizers
> defined in the terminology section of the bootstrapping PS have been used
> more persistently. Again, I am happy to provide the editorial changes once
> we settle this:)
> 
> Looking at the bootstrapping paper a few things are clear:
> 
> 1) ASPs do not deal with provisioning of mobility service, MSPs do. This
> means an HA would be assigned by the MSP not by an ASP.

 I agree with that.

> 
> 2) There is a concept of home versus serving provider versus authorizer.
> This means a local HA in a serving/ foreign/ visited (pick one) would be
> assigned by the "serving MSP" not by an ASP.

 I also agree with that.

> 
> There is one error in my opinion in the bootstrapping ps section 5.1.2
> (dynamic HA assignment):
> 
> "Local home agents
> 
>       The mobile node's MSP may want to allow the serving ASP to assign
>       a local home agent for the mobile node."
> 
> It should say "...to allow serving MSP" not "ASP", since ASP is not in
> charge of providing mobility service and that is where probably the
> inconsistency starts??
> 
> What do you think?

 I agree on this point. 
 
 We'll incorporate this in the next revision (-03). 

 Thanks,

 Julien

> 
> R,
> 
> Madjid
> 
> 
> 
> 
> 
> -----Original Message-----
> From: Julien Bournelle [mailto:julien.bournelle@int-evry.fr] 
> Sent: Friday, August 04, 2006 9:25 AM
> To: Madjid Nakhjiri
> Cc: 'Julien Bournelle'; mip6@ietf.org
> Subject: Re: [Mip6] comments on AAA-HA-goals-02
> 
> Hi madjid,
> 
>  I think that this discussion is more about our understanding of the
>  bootstrapping-ps terminology. Maybe we should start a new thread about
>  this.
> 
>  Julien
> 
> 
> On Thu, Aug 03, 2006 at 04:37:44PM -0700, Madjid Nakhjiri wrote:
> > Hi Julien, 
> > 
> > Thanks for the quick reply. 
> > 
> > 
> > -----Original Message-----
> > From: Julien Bournelle [mailto:julien.bournelle@int-evry.fr] 
> > Sent: Thursday, August 03, 2006 7:22 AM
> > To: Madjid Nakhjiri
> > Cc: mip6@ietf.org
> > Subject: Re: [Mip6] comments on AAA-HA-goals-02
> > 
> > Hi madjid,
> > 
> >  let me try to respond to your mail though some terminology issues are
> more
> > related to the
> >  draft-ietf-mip6-bootstrapping-ps draft.
> > 
> > Madjid>>I actually find the terminology in the bootstrapping draft more
> > consistent. 
> > 
> > > The network MSA to me symbolizes
> > > the MSP-AAA server, while ASA symbolizes ASP-AAA server. 
> > 
> >  no, the MSA is administrative entity with whom the user has a contract
> >  and thus credentials. The MSP effectively provides the MIP6 service to
> >  the user. Thus the MSP may have to contact the MSA before providing the
> >  service. 
> > 
> > Madjid>>Well, you are saying MSA has a contract with the user and has her
> > credentials. To me it translates to a home AAA server or authentication
> > server for the MSP. I think we need to make the distinction between home
> MSA
> > and visited MSA.
> > Also, MSP is a service provider, but you are implying it does not have a
> AAA
> > server? At the bottom of your email you said MSP has a AAA server. I am
> > confused now.
> > The ASP is defined in the bootstrapping draft as an _operator_, but it is
> > not clear whether MSP is an operator or just an entity like an HA. What is
> > the real life correspondence of the MSP??
> > I like to think MSP include both a HA and a AAA server (MSA).
> > 
> > > 
> > > *        I see a hot spot provider or a 802.16d network without mobility
> > > support as an ASP, while a IP enabled cellular or a WiMAX network as a
> > > combination of ASP and MSP. To me assignment of HA falls into the MSP
> > > service category, not ASP service category (I just confirmed this in
> > > bootstrapping-ps section 7.1), so there are some statements in the draft
> > as
> > > far as an  ASP assigning an HA and I don't think those are appropriate
> > based
> > > on the terminology provided. 
> > 
> >  it depends if we are in the split or integrated scenario.
> >  In the split scenario, we don't have ASP/ASA, only MSP/MSA. So the user
> >  has an HA from the MSP.
> > 
> > Madjid>> Well, you do have ASP/ASA, it just that it is beyond MSP control.
> > 
> >  In the integrated scenario, if MSP=ASP, the user obtains an HA from the
> >  MSP/ASP. 
> > 
> > 
> > > 
> > > *        Then there is the concept of home versus visited domain. I am
> > > guessing "domain" to administrative domain (AAA domain). Traditionally
> AAA
> > > community is denoted as home and visited AAA servers, i.e. AAAH and
> AAAV,
> > > respectively. I just checked the bootstrapping-ps draft and that draft
> > calls
> > > uses the term "serving" instead of "visited", but still provides a
> > > distinction between home versus serving MSP (MSPH and MSPS) and between
> > home
> > > versus serving ASP (ASPH and ASPS). Having said this, I think if the
> group
> > > is going to great length to separate ASP/ MSP and ASA/MSA, it also needs
> > to
> > > distinguish between the home versus visited domain for each of the
> > > authorizers. So that MSAH refers to AAA server within home MSP (MSP-H)
> and
> > > MSAV or MSAS (pick one) to AAA server within visited or serving MSP
> (MSP-V
> > > or MSP-S). The same goes for ASAH and ASAV. This means Serving MSA is
> not
> > > the same as serving ASA. It is not proper to equate the access service
> > > provider (ASP) with MSP-V the visited domain as it is implied in section
> > > 4.2: "Mobile Node requests a home agent to the Access Service Provider
> > > (ASP)". According to my understanding of the terminology of ASP, ASP has
> > > nothing to anything to do with HA assignment. I think this can be easily
> > > remedied by introducing MSAH and MSAS. Visited domain HA allocation can
> be
> > > formulated as "MN can request MSAH for an HA assignment within MSPS
> after
> > > authentication to MSAH and authorization of mobility service by the
> > > MSAH/MSAS to MN".
> > 
> >  maybe my explanation below will answer to this paragraph ?
> > 
> > Madjid>>Well one point is ASP is an access provider, not a mobility
> > provider, so ASP cannot grant an HA request nor can it assign one. So that
> > sentence needs to be revised. The other issue is the lack of distinction
> > between home and visited providers, ASP does not mean visited MSP!
> > 
> > > *        The same goes for another sentence in the same section saying
> "..
> > > Mobile Node can specify if it wants a home agent provided by the visited
> > > domain (ASP) or by the home domain (ASA)", which seems to be mixing
> > > (mobility and access service), (home and visited), (provider and
> > authorizer)
> > > all in the same sentence!!
> > 
> >  yes, that can be confusing. 
> > 
> > Madjid>>Well, if we stick to the terminology in the bootstrapping draft
> and
> > use "serving" and "visited" and clarify whether MSP is an operator or just
> > an HA, things should fall into a place better. If you agree with my
> > statements, I could help out with that.
> > 
> > > 
> > > *        The other comment along the same line is about section 4.1,
> where
> > > it is stated a pool of HA s can rely on the home EAP server (I am
> guessing
> > > EAP server belonging to MSA-H, since this is split scenario) for
> > > authentication. Here it is stated "It allows the roaming mobility case
> in
> > > which the MN obtains the mobility service in a different administrative
> > > domain (MSP !=MSA). Here it seems that it is implied HA is part of MSP
> > > function (appropriately), however, I am not sure if MSP and MSA can
> imply
> > > two administrative domains, to me administrative domain implies AAA
> > domain,
> > > so one would be MSA-H and another MSA-V, so an HA could be authorized
> > within
> > > MSA-V based on authentication to MSA-H and authorization by MSA-H.
> > 
> >  MSP has its own AAA server. MSA is the AAA server of the MN. 
> >  Does it respond to your comment ?
> > 
> > Madjid>>the definition of MSA is "an authorizer that authorizes MIP6
> > service". To me that is the AAA server of the MSP: a AAA server that
> > authorizes MIP6 service within an MSP. Then you have the concept of home
> > versus serving MSP or ASP and home versus serving MSA and ASA.
> > The home-MSA can authorize MIP6 service within home MSP and has MN's
> > credentials. The "MSA" alone is just like a "AAA server" alone, it does
> not
> > say home or visited AAA server.
> > 
> > > 
> > > *        I also have an issue with the usage of term NAS in next to last
> > > paragraph of section 3. NAS is really an access service agent (as the
> name
> > > implies) not a mobility service agent. NAS performs many functions
> beyond
> > > the AAA client function, which brings up two issues. 1) the sentence
> ".HA,
> > > that can be seen as Network Access Server for MIP6", is only providing
> > > confusion in this context, you may say that HA can be seen as Network
> > > mobility server if you want but in a draft that has ASP and MSP
> > everywhere.
> > 
> >  ok.
> > 
> > > 2) in the goals sections (5.1/ 5.2) , it is not mentioned anywhere that
> > the
> > > HA MUST act as a AAA client, is this a non-requirement, or is it
> > implicitly
> > > understood?  Especially G2.2 seems to imply this.
> > 
> >  I think it is implicitly understood. Do you think we should add a
> >  statement on this ?
> > 
> > Madjid>>I think this is the first requirement for the HA within an HA-AAA
> > goals draft. It tells the world what code to expect to have in the
> compliant
> > HA. Having it implicit is not a good thing.
> > 
> > > 
> > > *        In 5.4 why is it a "MUST" for HA to be an EAP pass-through
> > > authenticator? As long as HA receives its information from the AAA
> server
> > in
> > > a secure fashion and both HA and AAA can identify the MN and its EAP
> > session
> > > uniquely, there is no reason for allocating HA and EAP pass-through EAP
> > > authenticator in the same box.
> > 
> >  hmmm, the HA acts as a AAA client and MN uses IKEv2 with EAP to be
> >  authenticated. So the HA MUST act as an EAP pass-through authenticator.
> > 
> >  Am I missing something ? do you think we should rephrase this ?
> > 
> > Madjid>> I don't think this is hard requirement. You may another AAA
> client
> > on the path EAP signaling with EAP server. Aren't you separating ASA and
> > MSA?? HA is AAA client for MSP authorization but not necessarily the AAA
> > client for every EAP authentication, may be I am missing something.
> > The way to rephrase it is
> > 
> > "HA Should be able to act as EAP pass-through authenticator in the EAP
> > process for IKEv2." Or something like that. I have to look at the split
> > scenario doc explaining this.
> > 
> > > 
> > > *        For section 4.2, Integrated scenario, I see that NAS gets MIP6
> > conf
> > > parameters from the AAAH, how does the HA receives the information it
> > needs?
> > 
> >  In the integrated scenario based on DHCPv6, the MN gets HA info through
> >  DHCP. Then we fall in the split scenario and the MN uses IKEv2 with the
> >  HA. 
> > 
> > Madjid>> Let me do some more reading:)
> > 
> > Thanks,
> > 
> > Madjid
> > 
> >  Julien Bournelle
> > 
> > 
> > 
> > 
> 
> -- 
> julien.bournelle at int-evry.fr
> 
> 

-- 
julien.bournelle at int-evry.fr

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



From mip6-bounces@ietf.org Mon Aug 07 09:34:47 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GA5Fb-0003Pf-83; Mon, 07 Aug 2006 09:34:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GA5FZ-0003M4-CX
	for mip6@ietf.org; Mon, 07 Aug 2006 09:34:33 -0400
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GA54c-00030o-57
	for mip6@ietf.org; Mon, 07 Aug 2006 09:23:15 -0400
Received: from il06exr03.mot.com (il06exr03.mot.com [129.188.137.133])
	by motgate8.mot.com (8.12.11/Motorola) with ESMTP id k77DNDSk005283
	for <mip6@ietf.org>; Mon, 7 Aug 2006 06:23:13 -0700 (MST)
Received: from ZMY16EXM67.ds.mot.com (zmy16exm67.ap.mot.com [10.179.4.27])
	by il06exr03.mot.com (8.13.1/8.13.0) with ESMTP id k77DNCGx022521
	for <mip6@ietf.org>; Mon, 7 Aug 2006 08:23:13 -0500 (CDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 7 Aug 2006 21:23:06 +0800
Message-ID: <AE007C20C0A3D44D8EE9DD46764559AD010B7144@ZMY16EXM67.ds.mot.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: DHCP-Diameter application for MIPv6 bootstrapping
Thread-Index: Aca32DC+yc2EexJUSginXFSsLjQq9gCCh0TgABBhRlA=
From: "Upadhyaya Saumya-a20369" <saumya@motorola.com>
To: <mip6@ietf.org>
X-Brightmail-Tracker: AAAAAQAAAAQ=
X-White-List-Member: TRUE
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Subject: [Mip6] DHCP-Diameter application for 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>
Errors-To: mip6-bounces@ietf.org

Hi Vijay,

We have gone over the listed drafts.

In our approach, we propose that the DHCP server contains a AAA client
which can thereby obtain the messages from either a local entity (say,
the AAAF/Local Diameter Proxy/NAS) or a home entity (say, the AAAH/Home
Diameter Server). This is in contrast to
draft-ietf-dime-mip6-integrated-00 which proposes to obtain the
bootstrapping parameters till the NAS using Diameter-EAP and proposes
that the NAS behave as a DHCP Relay. In our approach, the NAS can remain
independent of DHCP and need not perform any operations on the DHCP
packets that it relays.

In our approach, we propose that the MN makes use of DHCP to obtain the
bootstrapping parameters irrespective of the network architecture
(split/integrated).

In the draft [draft-ram-dhc-dhcpv6-diam-app-00], we define a Diameter
DHCP Application which could be used to obtain the MIPv6 bootstrapping
parameters from the MSA.

Regards,
Saumya

Date: Fri, 4 Aug 2006 08:08:42 -0700
From: "Vijay Devarapalli" <Vijay.Devarapalli@AzaireNet.com>
Subject: RE: [Mip6] Recommendation for bootstrapping using DHCPv6
To: "Upadhyaya Saumya-a20369" <saumya@motorola.com>,	<mip6@ietf.org>
Message-ID:
=09
<C8E1D942CB394746BE5CFEB7D97610E701D993AF@bart.corp.azairenet.com>
Content-Type: text/plain;	charset=3D"iso-8859-1"

Hi Saumya,

the work on this is being done in the DIME WG. take a look at=20
http://www.ietf.org/internet-drafts/draft-ietf-dime-mip6-integrated-00.t
xt=20
http://www.ietf.org/internet-drafts/draft-ietf-dime-mip6-split-00.txt

Vijay


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



From mip6-bounces@ietf.org Mon Aug 07 11:17:41 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GA6r7-0005vu-5o; Mon, 07 Aug 2006 11:17:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GA6r5-0005vl-Dv
	for mip6@ietf.org; Mon, 07 Aug 2006 11:17:23 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GA6r5-0000i8-CM
	for mip6@ietf.org; Mon, 07 Aug 2006 11:17:23 -0400
Received: from mx0.starentnetworks.com ([12.38.223.203])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1GA6hT-0004S5-4T
	for mip6@ietf.org; Mon, 07 Aug 2006 11:07:30 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mx0.starentnetworks.com (Postfix) with ESMTP id 3948B9001C;
	Mon,  7 Aug 2006 11:07:19 -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 15382-10; Mon, 7 Aug 2006 11:07:18 -0400 (EDT)
Received: from exchtewks1.starentnetworks.com (exchtewks1.starentnetworks.com
	[12.33.233.52]) by mx0.starentnetworks.com (Postfix) with ESMTP;
	Mon,  7 Aug 2006 11:07:18 -0400 (EDT)
X-MessageTextProcessor: DisclaimIt (2.70.271) [Starent Networks Corp.]
Received: from exchtewks2.starentnetworks.com ([12.33.232.12]) by
	exchtewks1.starentnetworks.com with Microsoft
	SMTPSVC(6.0.3790.1830); Mon, 7 Aug 2006 11:03:21 -0400
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] DHCP-Diameter application for MIPv6 bootstrapping
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
Date: Mon, 7 Aug 2006 11:03:21 -0400
Message-ID: <7CCD07160348804497EF29E9EA5560D783710C@exchtewks2.starentnetworks.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] DHCP-Diameter application for MIPv6 bootstrapping
thread-index: Aca32DC+yc2EexJUSginXFSsLjQq9gCCh0TgABBhRlAAA1yy8A==
From: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
Importance: normal
Priority: normal
To: "Upadhyaya Saumya-a20369" <saumya@motorola.com>, <mip6@ietf.org>
X-OriginalArrivalTime: 07 Aug 2006 15:03:21.0795 (UTC)
	FILETIME=[9FC05130:01C6BA32]
X-Virus-Scanned: amavisd-new 2.2.1 (20041222) at mx0.starentnetworks.com
X-Spam-Score: -2.6 (--)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
Cc: 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Saumya,

In your proposal, do you envision any kind of authentication at the DHCP
server for the MN prior to assigning the MN HA, HoA info? What is the
likelihood that operators will authenticate the MN at the DHCP server
instead of or in addition to the NAS (EAP-authenticator)?

There was a proposal a while back to use DHCP delayed authentication
scheme to perform MIP6 bootstrapping. Here is the link of the expired
I-D:

http://www.join.uni-muenster.de/Dokumente/drafts/draft-ohba-mip6-boot-ar
ch-dhcp-00.txt

Have you looked at this one?=20

-Kuntal

> -----Original Message-----
> From: Upadhyaya Saumya-a20369 [mailto:saumya@motorola.com]
> Sent: Monday, August 07, 2006 8:23 AM
> To: mip6@ietf.org
> Subject: [Mip6] DHCP-Diameter application for MIPv6 bootstrapping
>=20
> Hi Vijay,
>=20
> We have gone over the listed drafts.
>=20
> In our approach, we propose that the DHCP server contains a AAA client
> which can thereby obtain the messages from either a local entity (say,
> the AAAF/Local Diameter Proxy/NAS) or a home entity (say, the
AAAH/Home
> Diameter Server). This is in contrast to
> draft-ietf-dime-mip6-integrated-00 which proposes to obtain the
> bootstrapping parameters till the NAS using Diameter-EAP and proposes
> that the NAS behave as a DHCP Relay. In our approach, the NAS can
remain
> independent of DHCP and need not perform any operations on the DHCP
> packets that it relays.
>=20
> In our approach, we propose that the MN makes use of DHCP to obtain
the
> bootstrapping parameters irrespective of the network architecture
> (split/integrated).
>=20
> In the draft [draft-ram-dhc-dhcpv6-diam-app-00], we define a Diameter
> DHCP Application which could be used to obtain the MIPv6 bootstrapping
> parameters from the MSA.
>=20
> Regards,
> Saumya
>=20
> Date: Fri, 4 Aug 2006 08:08:42 -0700
> From: "Vijay Devarapalli" <Vijay.Devarapalli@AzaireNet.com>
> Subject: RE: [Mip6] Recommendation for bootstrapping using DHCPv6
> To: "Upadhyaya Saumya-a20369" <saumya@motorola.com>,	<mip6@ietf.org>
> Message-ID:
>=20
> <C8E1D942CB394746BE5CFEB7D97610E701D993AF@bart.corp.azairenet.com>
> Content-Type: text/plain;	charset=3D"iso-8859-1"
>=20
> Hi Saumya,
>=20
> the work on this is being done in the DIME WG. take a look at
>
http://www.ietf.org/internet-drafts/draft-ietf-dime-mip6-integrated-00.t
> xt
> http://www.ietf.org/internet-drafts/draft-ietf-dime-mip6-split-00.txt
>=20
> Vijay
>=20
>=20
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6


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

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



From mip6-bounces@ietf.org Mon Aug 07 12:52:53 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GA8LR-0001n6-8e; Mon, 07 Aug 2006 12:52:49 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GA8LQ-0001mw-9M
	for mip6@ietf.org; Mon, 07 Aug 2006 12:52:48 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GA76x-0002hQ-AC
	for mip6@ietf.org; Mon, 07 Aug 2006 11:33:47 -0400
Received: from mx0.starentnetworks.com ([12.38.223.203])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1GA72t-0004nN-El
	for mip6@ietf.org; Mon, 07 Aug 2006 11:29:40 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mx0.starentnetworks.com (Postfix) with ESMTP id 0D8839001D;
	Mon,  7 Aug 2006 11:29: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 16106-07; Mon, 7 Aug 2006 11:29:30 -0400 (EDT)
Received: from exchtewks1.starentnetworks.com (exchtewks1.starentnetworks.com
	[12.33.233.52]) by mx0.starentnetworks.com (Postfix) with ESMTP;
	Mon,  7 Aug 2006 11:29:27 -0400 (EDT)
X-MessageTextProcessor: DisclaimIt (2.70.271) [Starent Networks Corp.]
Received: from exchtewks2.starentnetworks.com ([12.33.232.12]) by
	exchtewks1.starentnetworks.com with Microsoft
	SMTPSVC(6.0.3790.1830); Mon, 7 Aug 2006 11:25:31 -0400
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] Recommendation for bootstrapping using DHCPv6
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
Date: Mon, 7 Aug 2006 11:25:31 -0400
Message-ID: <7CCD07160348804497EF29E9EA5560D783710D@exchtewks2.starentnetworks.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] Recommendation for bootstrapping using DHCPv6
thread-index: Aca1oaIQ4K1FzyGUEduPhAARJNUNiAA2bJdQAC3tKR8AwA9h0A==
From: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
Importance: normal
Priority: normal
To: "Basavaraj Patil" <basavaraj.patil@nokia.com>,
	"ext Alper Yegin" <alper.yegin@yegin.org>, <mip6@ietf.org>
X-OriginalArrivalTime: 07 Aug 2006 15:25:31.0233 (UTC)
	FILETIME=[B8287510:01C6BA35]
X-Virus-Scanned: amavisd-new 2.2.1 (20041222) at mx0.starentnetworks.com
X-Spam-Score: -2.6 (--)
X-Scan-Signature: 926f893f9bbbfa169f045f85f0cdb955
Cc: 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hello Raj,

IMHO, the working group I-Ds are defining the necessary mechanism for
mip6 bootstrapping by using various components such as IKEv2, DHCP, AAA,
DNS etc. Some of the components are defined in already published RFCs
and some are in the process of being defined e.g. the AAA and the DHCP
components. I do not think it makes sense to proceed with separate
documents for the AAA components whereas merge the DHCP component. I
don't find a valid reason to justify this exception. Note that all the
components that these bootstrapping solutions are trying to use are work
of other WGs in IETF.=20

There are simple use cases where a back-end AAA infrastructure is not
deployed but still DHCP options can be used to convey HA, HoA info from
a DHCP server to the MN (e.g. an enterprise network).=20

If your reasoning is purely related to the documentation of the DHCP
options in IETF, I would suggest that we follow what other SDOs are
doing. Most of the ones I know of adopted the approach of short and
manageable documents that are easy to use, read, and update. It also
allows focused discussion on specific areas.

Regards,
Kuntal



> -----Original Message-----
> From: Basavaraj Patil [mailto:basavaraj.patil@nokia.com]
> Sent: Thursday, August 03, 2006 2:29 PM
> To: ext Alper Yegin; mip6@ietf.org
> Subject: Re: [Mip6] Recommendation for bootstrapping using DHCPv6
>=20
>=20
> Alper,
>=20
> Inline:
>=20
> On 8/2/06 4:45 PM, "ext Alper Yegin" <alper.yegin@yegin.org> wrote:
>=20
> > Hi Raj,
> >
> > "Having the options specified in a stand-along document will not add
> much
> > value."
> >
> > As we have been stating, draft-jang-mip6-hiopt-00.txt also has a use
> that
> > does not tie into the RADIUS-driven details -- the use where DHCP
server
> can
> > be manually configured and has nothing to do with the AAA.
>=20
> But why do you believe that the WG I-D which is using DHCP is RADIUS
> driven
> only and nothing else? I mean it could just as well be used for the
case
> where the bootstrapping information is manually configured in the DHCP
> server. What is needed are the DHCP options and the fact that the
> bootstrap
> parameters are available in the DHCP server either as a result of some
AAA
> messages or manual configuration does not matter.
>=20
> >
> > Your above statement misses this point.
> >
> > Besides, while there is a standalone use for draft-jang-mip6-hiopt-
> 00.txt,
>=20
> What is the standalone use of draft-jang? The WG I-D needs to specify
the
> DHCP options anyway. Why would that not be sufficient for any
deployment
> scenario that you have in mind?
>=20
> > there is none for the RADIUS and Diameter specs we expect to
document
> > individually. Should we also merge those AAA documents with the
others?
>=20
> Are you refering to the Radius/Diameter mechanisms for obtaining the
> bootstrap parameters and storing them in the DHCP server? You could
> specify
> those mechanisms independently of the fact that there is a
specification
> which explains how DHCP is used for bootstrapping and the DHCP options
to
> carry the bootstrap parameters between the MS and the DHCP server. So
I
> don't expect that those drafts also be merged with the current spec.
>=20
> >
> > Also, I'm not sure what specific concern you are raising with
respect to
> the
> > quoted text below.
>=20
> The concern that I have is the fact that the I-D specifies the DHCP
> options
> for boostrapping. The bootstrap parameters are somehow stored in the
DHCP
> server. The I-D is basically saying that how the parameters get into
the
> DHCP server are not in scope here except giving an example that manual
> configuration or AAA can be used. So it is incomplete and unusable.
What
> you
> say above is that there will be additional I-Ds coming to specify how
that
> is done. The current WG integrated scenario with DHCPv6 I-D has more
> details
> and explains at least how AAA is used. I guess manual configuration is
> pretty straightforward and does not need secification. But in the case
> when
> the MS is roaming and attached to some visited network, how does it
> bootstrap with DHCP? My concern is the fact that the I-D is incomplete
and
> it simply sweeps the issue under the mat by saying it is out of scope.
>=20
> -Raj
>=20
> >
> > Alper
> >
> >
> >
> >> -----Original Message-----
> >> From: Basavaraj Patil [mailto:basavaraj.patil@nokia.com]
> >> Sent: Tuesday, August 01, 2006 12:35 PM
> >> To: mip6@ietf.org
> >> Subject: [Mip6] Recommendation for bootstrapping using DHCPv6
> >>
> >>
> >> Alper/Kuntal et al,
> >>
> >> I have reviewed the drafts:
> >> 1. Problem Statement for bootstrapping Mobile IPv6
> >>    (draft-ietf-mip6-bootstrap-ps-05)
> >> 2. MIP6-bootstrapping via DHCPv6 for the Integrated Scenario
> >>    (draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt)
> >>
> >> and
> >> 3. DHCP Option for Home Information Discovery in MIPv6
> >>    (draft-jang-mip6-hiopt-00.txt)
> >>
> >> My conclusion from the review is that the integrated scenario
> >> bootstrapping via DHCPv6 is covering the cases when DHCP is the
> >> preferred method by MNs.
> >>
> >> The WG I-D draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt in
> >> sections 3.5 and 3.8 explain how DHCP would work. Having the
options
> >> specified in a stand-along document will not add much value. I am
also
> >> concerned about the fact in draft-jang which states that:
> >> "
> >>    The availability of the requested information depends on the
DHCP
> >>    server having prior knowledge or dynamically discovering it.
While
> >>    the specific details are outside the scope of this document, use
of
> >>    static tables and AAA-assisted discovery are possible options
> >> "
> >>
> >> Another concern that I have w.r.t bootstrapping with DHCPv6 is that
> >> instead of having DHCP provide the HoA or the HL prefix to the MS,
it
> >> is better to only provide the address of an HA (or list of HAs) and
> >> let the MS send a BU with unspecified address and obtain an address
> >> from the HA. This will simplify bootstrapping and also reduce the
> >> interaction between DHCP and the HA from an address management
> >> perspective. Hence you may want to reconsider the DHCP option which
> >> carry the HL Prefix or the HoA for the MS.
> >>
> >> I recommend that the DHCP option specified in draft-jang be
> >> incorporated into the WG I-D and progressed on standards track. As
a
> >> result the WG will have a mechanism for bootstrapping MIP6 with
DHCP
> >> that also includes the DHCP options in a single I-D.
> >>
> >> -Raj
> >>
> >>
> >> _______________________________________________
> >> 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


"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 Aug 07 14:27:25 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GA9ot-0004lF-61; Mon, 07 Aug 2006 14:27:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GA9or-0004l9-MI
	for mip6@ietf.org; Mon, 07 Aug 2006 14:27:17 -0400
Received: from mgw-ext11.nokia.com ([131.228.20.170])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GA9op-0007T6-2J
	for mip6@ietf.org; Mon, 07 Aug 2006 14:27:17 -0400
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211])
	by mgw-ext11.nokia.com (Switch-3.1.8/Switch-3.1.7) with ESMTP id
	k77HRCBZ028123 for <mip6@ietf.org>; Mon, 7 Aug 2006 20:27:14 +0300
Received: from daebh102.NOE.Nokia.com ([10.241.35.112]) by
	esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 7 Aug 2006 21:27:09 +0300
Received: from daebe101.NOE.Nokia.com ([10.241.35.113]) by
	daebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 7 Aug 2006 13:27:03 -0500
Received: from 172.19.244.182 ([172.19.244.182]) by daebe101.NOE.Nokia.com
	([10.241.35.113]) with Microsoft Exchange Server HTTP-DAV ; 
	Mon,  7 Aug 2006 18:27:03 +0000
User-Agent: Microsoft-Entourage/11.2.5.060620
Date: Mon, 07 Aug 2006 13:27:21 -0500
From: Basavaraj Patil <basavaraj.patil@nokia.com>
To: <mip6@ietf.org>
Message-ID: <C0FCF039.20FB7%basavaraj.patil@nokia.com>
Thread-Topic: MIP6 WG meeting minutes from IETF66
Thread-Index: Aca6Tx7iXbz+OiZCEduYJQARJNUNiA==
Mime-version: 1.0
Content-type: text/plain;
	charset="Big5"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 07 Aug 2006 18:27:03.0597 (UTC)
	FILETIME=[14834DD0:01C6BA4F]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b045c2b078f76b9f842d469de8a32de3
Subject: [Mip6] MIP6 WG meeting minutes from IETF66
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org



Minutes of: Mobility for IPv6 (mip6) WG
At: IETF66
July 13, 2006 (Montreal)

Chairs: Hesham Soliman (hsoliman@qualcomm.com)
    Vijay Devarapalli (vijay.devarapalli@azairenet.com)

Credit for these minutes:
       1. Gabor Bajko (gabor.bajko@nokia.com)
       2. Brian Haley (brian.haley@hp.com)


Vijay Devarapalli and Hesham Soliman chairing the meeting on behalf of
Basavaraj Patil and Gopal Dommety

1. WG document status
----------------------
 - 3 RFCs published RFC 4487, 4449, 4295
 - 2 in RFC Ed queue (bootstrapping and mip6 api extensions)
 - 2 in Last Call
 - 2 in AD evaluation

2. Charter Discussion
---------------------
Jari - Proposed content for the rechartering. Scope: to align the charter
description with the work the wg is already doing. Taking on board new
work not necessarily the intention.

Gerardo - Should bootstrapping cover auth option also?

Jari - work on bootstrapping with IPsec for the time being, consider
4285 only if 3gpp wants that.

Petrescu - For dual stack, separate problem statement preferred for
mipv6 wg.

George - Have a common problem statement doc.

Hesham - Good to have a problem statement document, but not necessary
for the solution development.

Vijay - The problem description in the DS-MIPv6 solution document is
sufficient for DS-MIPv6. A separate problem statement is not needed.

Jari: Some adjustment to the charter needed. Will change charter
monthly if that's what we want


3. DHCP Option for Home Information Discovery in MIPv6
-------------------------------------------------------
I-D: I-D:  draft-jang-mip6-hiopt-00.txt

Hesham - has been discussed on the list, does it needs to be
standardised at all?

Petrescu - networks are identified by other means, not the proposed
HNid

Hesham - usage of HNid is common practice

Alper - This doc is next step after the framework doc.

Gerardo - Objects to a standalone document

Alper - this doc should be standalone. It can support static
configuration. Similar to how RFC 2132 defines a DHCP option for
MIPv4 home agent.

Vijay - There was never an intention to define a framework document,
just one solution document for the integrated scenario based on DHCP.

Hesham - lets take it to the mailing list.

Gerardo - has been discussed for more than 6 months. we need to
decide.

Vijay & Gerardo - Scrap the current working document if thats not
needed at all. draft-jang can define how to use DHCP for MIP6
bootstrapping.

Hesham - solution is agreeable, but no agreement on document
organization. Work offline and send something to the MIP6 mailing
list

4. Problem statement for Dual Stack MIP
---------------------------------------
I-D: draft-ietf-mip6-dsmip-problem-02.txt
No discussion

5. Dual Stack MIPv6
-------------------

I-D: draft-ietf-mip6-nemo-v4traversal-01.txt

Petrescu - why do we need keep-alive?

Hesham - to keep the NAT bindings alive

Petrescu - there are NATs which do not keep mappings even in
presence of keep alives

Henrik - questions the statement. does not believe there are NATs
like that.

Alex - have seen them

Henrik - we need product name and model number sent to the list
to verify Alex's statement

Hesham - scenario: dynamic detection of NAT in the HA's domain:
there might be IPRs

Vijay - nice to have, not necessary feature. Could be in a separate doc.

Hesham - should the feature be added or not?

Alex - The problem statement does not talk about this scenario.

George - not necessary in the DS-MIPv6 solution document

Henrik - IPR bothers him. if this will limit open source development
of this draft, then we can't have it

Leung - optional feature, it does not hurt having it

Vijay - It would be hard to distinguish which part of the spec has
IPR claims and which does not. IPR disclosure statements don't specify
that.

Sri: it does not make sense to not standardise it because of IPR. NEMO
standardised IPRed solutions.

Vijay - Each IPR decision needs to be taken separately. Precendent is
not useful.

Ruiji: relax 3775 for the NAT case (req to use altCoA when ESP is used).

Vijay: look at it as updating 3775 for NAT case

6. HA Reliability
------------------
I-D: draft-ietf-mip6-hareliability-00.txt

? - Don't think we can pre-establish multiple security associations as
specified

Ryuji - this is done at bootstrapping time

Petrescu - Why didn't we extend BRR instead of creating HA switch?

Brian - We could have, but didn't

Hesham - Why do we have switchover message?

Vijay - It's sent from the standby HA to become active

Bob Hinden - Should be very careful with deteting HA failures and
switching home agents. it is a hard problem. see VRRP for more details.

? - There are 2 things ? fault detection and state transfer ? fault
detection is not specific to this WG, they are IETF-wide so it would
be good to define them separately for that reason

Kent - routers already have hello beacons for a lot of things, we're
adding one more thing here. should we make this more generic and maybe
separate it out?

7. Experimental and Vendor-specific options and messages
---------------------------------------------------------

I-D: draft-devarapalli-mip6-vsm-00.txt
     draft-devarapalli-mip6-experimental-messages-00.txt

Alex - Why do we need both?

Vijay - Vendor-specific could be deployed, experimental shouldn't.
They are for separate purposes.

Henrik and Kent against vendor-specific message, ok with vendor
specific mobility option

8. Bootstrapping for RFC 4285
------------------------------
I-D: draft-devarapalli-mip6-authprotocol-bootstrap-00.txt

Hesham - Will this be informational like 4285?

Vijay - Yes

Vijay - What should the WG do?

? - Not currently in charter, if we do it it's informational, will
add it to the charter discussion

9. AAA goals status
-------------------
I-D: draft-ietf-mip6-aaa-ha-goals-02.txt

Gerardi - should we consider requirements for 4285 bootstrapping?
no comments

10. Scenario analysis and problem statement of the dual-stack mobile entity
roaming in the ipv4 and ipv6 network
--------------------------------------------------------------------------
I-D: draft-wan-mip6-nemo-dsanalysis-00.txt

George - need to explain the problems better

Henrik - doesn't see what the problem is either; believes dsmip will
solve this

Henrik- if the home network doesn't support ipv4, but you need to use
it, what do you do? Why can't you just deploy ipv4 there to solve it?
That is the simplest solution.  Same with ipv6.

Hesham - what are you going to do with this ipv4 address if the link
doesn't support it? Tunnel it somewhere?  DSMIPv6 solves this today.

Hesham - it's not clear all the scenarios are problems

George - need to better define the protocol and the scenario it will be
used in

11. MIPv6 Firewall issues
-------------------------
I-D: draft-bajko-mip6-rrtfw-00.txt

- Some work done in NSIS WG based on NSLP
- Gabor presented some slides on modifying return routability messages
to make Mobile IPv6 friendly to firewalls.

12. Next steps
---------------
 - revised charter
 - consider new wg docs based on charter


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



From mip6-bounces@ietf.org Mon Aug 07 16:57:56 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GACAb-0002jp-4H; Mon, 07 Aug 2006 16:57:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GACAa-0002jk-FL
	for mip6@ietf.org; Mon, 07 Aug 2006 16:57:52 -0400
Received: from mgw-ext11.nokia.com ([131.228.20.170])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GACAZ-0001Jt-0w
	for mip6@ietf.org; Mon, 07 Aug 2006 16:57:52 -0400
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211])
	by mgw-ext11.nokia.com (Switch-3.1.8/Switch-3.1.7) with ESMTP id
	k77Jvknn015034 for <mip6@ietf.org>; Mon, 7 Aug 2006 22:57:50 +0300
Received: from daebh102.NOE.Nokia.com ([10.241.35.112]) by
	esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 7 Aug 2006 23:57:38 +0300
Received: from daebe101.NOE.Nokia.com ([10.241.35.113]) by
	daebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 7 Aug 2006 15:57:26 -0500
Received: from 172.19.244.182 ([172.19.244.182]) by daebe101.NOE.Nokia.com
	([10.241.35.113]) with Microsoft Exchange Server HTTP-DAV ; 
	Mon,  7 Aug 2006 20:57:25 +0000
User-Agent: Microsoft-Entourage/11.2.5.060620
Date: Mon, 07 Aug 2006 15:57:44 -0500
From: Basavaraj Patil <basavaraj.patil@nokia.com>
To: <mip6@ietf.org>
Message-ID: <C0FD1378.20FF4%basavaraj.patil@nokia.com>
Thread-Topic: Consensus call: DHCPv6 options for bootstrapping
Thread-Index: Aca6ZCEDX9NMYiZXEduYJQARJNUNiA==
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 07 Aug 2006 20:57:26.0252 (UTC)
	FILETIME=[166F32C0:01C6BA64]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Subject: [Mip6] Consensus call: DHCPv6 options for 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>
Errors-To: mip6-bounces@ietf.org


Hello,

We have been debating the issue of how to specify the DHCP options
needed for bootstrapping for a while now and have not been able to
reach any conclusions. This issue was discussed at the WG meeting at
IETF66 and has been debated on the mailing list as well.


I-Ds of interest here:
a. MIP6-bootstrapping via DHCPv6 for the Integrated Scenario
   draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt

b. DHCP Option for Home Information Discovery in MIPv6
   draft-jang-mip6-hiopt-00.txt

Issue: MIP6 bootstrapping can be done using DHCPv6. The WG document
(draft-ietf-mip6-bootstrapping-integrated-dhc-01) describes the use of
DHCP in the integrated scenario. In order to use DHCP for
bootstrapping several DHCP options need to be specified. The WG I-D in
section 3.5 has specified a couple of DHCPv6 options. I-D
draft-jang-mip6-hiopt-00 specifies several other DHCP options which
are essential for bootstrapping.

The issue is if the DHCP options need to be specified
    (i) as part of the solution I-D describing bootstraping using DHCP
    or 
    (ii) in a separate document which would then be referenced by the
    bootstrapping with DHCP solution doc.

We are seeking WG consensus in order to resolve the issue. Please
express your opinion w.r.t the approaches mentioned below:

Options:

1. Have a single document which specifies the solution describing
   bootstrapping with DHCPv6 which includes the DHCPv6 options that
   are needed.

2. Specify the DHCP options needed for bootstrapping with DHCPv6 in a
   separate document and have this referenced in the solution I-D.


Please submit your preference to the list by Aug 14th, 06.

-Raj


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



From mip6-bounces@ietf.org Mon Aug 07 20:12:59 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GAFDN-0007J7-58; Mon, 07 Aug 2006 20:12:57 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GAFDL-0007IV-UT
	for mip6@ietf.org; Mon, 07 Aug 2006 20:12:55 -0400
Received: from mail1.azairenet.com ([66.92.223.4] helo=bart.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GAFDJ-0007HA-IY
	for mip6@ietf.org; Mon, 07 Aug 2006 20:12:55 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] Consensus call: DHCPv6 options for bootstrapping
Date: Mon, 7 Aug 2006 17:12:27 -0700
Message-ID: <C8E1D942CB394746BE5CFEB7D97610E701D995EA@bart.corp.azairenet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] Consensus call: DHCPv6 options for bootstrapping
Thread-Index: Aca6ZCEDX9NMYiZXEduYJQARJNUNiAAGxTYg
From: "Vijay Devarapalli" <Vijay.Devarapalli@AzaireNet.com>
To: "Basavaraj Patil" <basavaraj.patil@nokia.com>,
	<mip6@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
Cc: 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

I prefer option 1) since I don't really see the need for
a separate document specifying the DHCP options.

Vijay=20

> -----Original Message-----
> From: Basavaraj Patil [mailto:basavaraj.patil@nokia.com]=20
> Sent: Monday, August 07, 2006 1:58 PM
> To: mip6@ietf.org
> Subject: [Mip6] Consensus call: DHCPv6 options for bootstrapping
>=20
>=20
> Hello,
>=20
> We have been debating the issue of how to specify the DHCP options
> needed for bootstrapping for a while now and have not been able to
> reach any conclusions. This issue was discussed at the WG meeting at
> IETF66 and has been debated on the mailing list as well.
>=20
>=20
> I-Ds of interest here:
> a. MIP6-bootstrapping via DHCPv6 for the Integrated Scenario
>    draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt
>=20
> b. DHCP Option for Home Information Discovery in MIPv6
>    draft-jang-mip6-hiopt-00.txt
>=20
> Issue: MIP6 bootstrapping can be done using DHCPv6. The WG document
> (draft-ietf-mip6-bootstrapping-integrated-dhc-01) describes the use of
> DHCP in the integrated scenario. In order to use DHCP for
> bootstrapping several DHCP options need to be specified. The WG I-D in
> section 3.5 has specified a couple of DHCPv6 options. I-D
> draft-jang-mip6-hiopt-00 specifies several other DHCP options which
> are essential for bootstrapping.
>=20
> The issue is if the DHCP options need to be specified
>     (i) as part of the solution I-D describing bootstraping using DHCP
>     or=20
>     (ii) in a separate document which would then be referenced by the
>     bootstrapping with DHCP solution doc.
>=20
> We are seeking WG consensus in order to resolve the issue. Please
> express your opinion w.r.t the approaches mentioned below:
>=20
> Options:
>=20
> 1. Have a single document which specifies the solution describing
>    bootstrapping with DHCPv6 which includes the DHCPv6 options that
>    are needed.
>=20
> 2. Specify the DHCP options needed for bootstrapping with DHCPv6 in a
>    separate document and have this referenced in the solution I-D.
>=20
>=20
> Please submit your preference to the list by Aug 14th, 06.
>=20
> -Raj
>=20
>=20
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
>=20

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



From mip6-bounces@ietf.org Mon Aug 07 23:15:37 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GAI3y-0007nA-Li; Mon, 07 Aug 2006 23:15:26 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GAI3x-0007n5-Ju
	for mip6@ietf.org; Mon, 07 Aug 2006 23:15:25 -0400
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GAI3v-0004n2-64
	for mip6@ietf.org; Mon, 07 Aug 2006 23:15:25 -0400
Received: from magus.qualcomm.com (magus.qualcomm.com [129.46.61.148])
	by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k783FKcd008489
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Mon, 7 Aug 2006 20:15:21 -0700
Received: from NAEXBR03.na.qualcomm.com (naexbr03.qualcomm.com
	[129.46.134.172])
	by magus.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id k783FIem023751; 
	Mon, 7 Aug 2006 20:15:19 -0700 (PDT)
Received: from NAEX13.na.qualcomm.com ([129.46.51.248]) by
	NAEXBR03.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 7 Aug 2006 20:15:18 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] Consensus call: DHCPv6 options for bootstrapping
Date: Mon, 7 Aug 2006 20:15:19 -0700
Message-ID: <C24CB51D5AA800449982D9BCB90325130A1FEA@NAEX13.na.qualcomm.com>
In-Reply-To: <C8E1D942CB394746BE5CFEB7D97610E701D995EA@bart.corp.azairenet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] Consensus call: DHCPv6 options for bootstrapping
Thread-Index: Aca6ZCEDX9NMYiZXEduYJQARJNUNiAAGxTYgAAZm5LA=
From: "Narayanan, Vidya" <vidyan@qualcomm.com>
To: "Vijay Devarapalli" <Vijay.Devarapalli@azairenet.com>,
	"Basavaraj Patil" <basavaraj.patil@nokia.com>, <mip6@ietf.org>
X-OriginalArrivalTime: 08 Aug 2006 03:15:18.0684 (UTC)
	FILETIME=[E041C5C0:01C6BA98]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1
Cc: 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

I've been following the discussion and option 1 makes sense to me too.=20

Vidya=20

> -----Original Message-----
> From: Vijay Devarapalli [mailto:Vijay.Devarapalli@azairenet.com]=20
> Sent: Monday, August 07, 2006 5:12 PM
> To: Basavaraj Patil; mip6@ietf.org
> Subject: RE: [Mip6] Consensus call: DHCPv6 options for bootstrapping
>=20
> I prefer option 1) since I don't really see the need for a=20
> separate document specifying the DHCP options.
>=20
> Vijay=20
>=20
> > -----Original Message-----
> > From: Basavaraj Patil [mailto:basavaraj.patil@nokia.com]
> > Sent: Monday, August 07, 2006 1:58 PM
> > To: mip6@ietf.org
> > Subject: [Mip6] Consensus call: DHCPv6 options for bootstrapping
> >=20
> >=20
> > Hello,
> >=20
> > We have been debating the issue of how to specify the DHCP options=20
> > needed for bootstrapping for a while now and have not been able to=20
> > reach any conclusions. This issue was discussed at the WG meeting at
> > IETF66 and has been debated on the mailing list as well.
> >=20
> >=20
> > I-Ds of interest here:
> > a. MIP6-bootstrapping via DHCPv6 for the Integrated Scenario
> >    draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt
> >=20
> > b. DHCP Option for Home Information Discovery in MIPv6
> >    draft-jang-mip6-hiopt-00.txt
> >=20
> > Issue: MIP6 bootstrapping can be done using DHCPv6. The WG document
> > (draft-ietf-mip6-bootstrapping-integrated-dhc-01) describes=20
> the use of=20
> > DHCP in the integrated scenario. In order to use DHCP for=20
> > bootstrapping several DHCP options need to be specified.=20
> The WG I-D in=20
> > section 3.5 has specified a couple of DHCPv6 options. I-D=20
> > draft-jang-mip6-hiopt-00 specifies several other DHCP options which=20
> > are essential for bootstrapping.
> >=20
> > The issue is if the DHCP options need to be specified
> >     (i) as part of the solution I-D describing bootstraping=20
> using DHCP
> >     or=20
> >     (ii) in a separate document which would then be=20
> referenced by the
> >     bootstrapping with DHCP solution doc.
> >=20
> > We are seeking WG consensus in order to resolve the issue. Please=20
> > express your opinion w.r.t the approaches mentioned below:
> >=20
> > Options:
> >=20
> > 1. Have a single document which specifies the solution describing
> >    bootstrapping with DHCPv6 which includes the DHCPv6 options that
> >    are needed.
> >=20
> > 2. Specify the DHCP options needed for bootstrapping with=20
> DHCPv6 in a
> >    separate document and have this referenced in the solution I-D.
> >=20
> >=20
> > Please submit your preference to the list by Aug 14th, 06.
> >=20
> > -Raj
> >=20
> >=20
> > _______________________________________________
> > Mip6 mailing list
> > Mip6@ietf.org
> > https://www1.ietf.org/mailman/listinfo/mip6
> >=20
>=20
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
>=20

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



From mip6-bounces@ietf.org Tue Aug 08 04:10:42 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GAMfb-0005I3-3N; Tue, 08 Aug 2006 04:10:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GAMfa-0005Hy-9c
	for mip6@ietf.org; Tue, 08 Aug 2006 04:10:34 -0400
Received: from smtp2.int-evry.fr ([157.159.10.45])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GAMfY-0001O2-Rv
	for mip6@ietf.org; Tue, 08 Aug 2006 04:10:34 -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 8CB0A2FD61;
	Tue,  8 Aug 2006 10:10:30 +0200 (CEST)
Received: from jb by ipv6-3.int-evry.fr with local (Exim 4.52)
	id 1GAMhh-0002a9-1I; Tue, 08 Aug 2006 10:12:45 +0200
Date: Tue, 8 Aug 2006 10:12:44 +0200
From: Julien Bournelle <julien.bournelle@int-evry.fr>
To: Basavaraj Patil <basavaraj.patil@nokia.com>
Subject: Re: [Mip6] Consensus call: DHCPv6 options for bootstrapping
Message-ID: <20060808081244.GA9909@ipv6-3.int-evry.fr>
References: <C0FD1378.20FF4%basavaraj.patil@nokia.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <C0FD1378.20FF4%basavaraj.patil@nokia.com>
User-Agent: Mutt/1.5.9i
X-INT-MailScanner-Information: Please contact the ISP for more information
X-INT-MailScanner: Found to be clean
X-INT-MailScanner-MCPCheck: 
X-INT-MailScanner-SpamCheck: 
X-MailScanner-From: jb@int-evry.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 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>
Errors-To: mip6-bounces@ietf.org

Hi all,

 I would prefer option (ii).

 regards,

 Julien Bournelle

On Mon, Aug 07, 2006 at 03:57:44PM -0500, Basavaraj Patil wrote:
> 
> Hello,
> 
> We have been debating the issue of how to specify the DHCP options
> needed for bootstrapping for a while now and have not been able to
> reach any conclusions. This issue was discussed at the WG meeting at
> IETF66 and has been debated on the mailing list as well.
> 
> 
> I-Ds of interest here:
> a. MIP6-bootstrapping via DHCPv6 for the Integrated Scenario
>    draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt
> 
> b. DHCP Option for Home Information Discovery in MIPv6
>    draft-jang-mip6-hiopt-00.txt
> 
> Issue: MIP6 bootstrapping can be done using DHCPv6. The WG document
> (draft-ietf-mip6-bootstrapping-integrated-dhc-01) describes the use of
> DHCP in the integrated scenario. In order to use DHCP for
> bootstrapping several DHCP options need to be specified. The WG I-D in
> section 3.5 has specified a couple of DHCPv6 options. I-D
> draft-jang-mip6-hiopt-00 specifies several other DHCP options which
> are essential for bootstrapping.
> 
> The issue is if the DHCP options need to be specified
>     (i) as part of the solution I-D describing bootstraping using DHCP
>     or 
>     (ii) in a separate document which would then be referenced by the
>     bootstrapping with DHCP solution doc.
> 
> We are seeking WG consensus in order to resolve the issue. Please
> express your opinion w.r.t the approaches mentioned below:
> 
> Options:
> 
> 1. Have a single document which specifies the solution describing
>    bootstrapping with DHCPv6 which includes the DHCPv6 options that
>    are needed.
> 
> 2. Specify the DHCP options needed for bootstrapping with DHCPv6 in a
>    separate document and have this referenced in the solution I-D.
> 
> 
> Please submit your preference to the list by Aug 14th, 06.
> 
> -Raj
> 
> 
> _______________________________________________
> 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 Tue Aug 08 06:43:33 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GAP3X-0007a0-V6; Tue, 08 Aug 2006 06:43:27 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GAP3W-0007Zu-Bt
	for mip6@ietf.org; Tue, 08 Aug 2006 06:43:26 -0400
Received: from mout.perfora.net ([217.160.230.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GAP3T-0001Os-5G
	for mip6@ietf.org; Tue, 08 Aug 2006 06:43:26 -0400
Received: from [85.101.17.2] (helo=IBM52A5038A94F)
	by mrelay.perfora.net (node=mrelayus0) with ESMTP (Nemesis),
	id 0MKoyl-1GAP3M2EPl-0003de; Tue, 08 Aug 2006 06:43:19 -0400
From: "Alper Yegin" <alper.yegin@yegin.org>
To: "'Basavaraj Patil'" <basavaraj.patil@nokia.com>,
	<mip6@ietf.org>
Subject: RE: [Mip6] Consensus call: DHCPv6 options for bootstrapping
Date: Tue, 8 Aug 2006 13:43:05 +0300
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
Thread-index: Aca6ZCEDX9NMYiZXEduYJQARJNUNiAAckCyg
In-Reply-To: <C0FD1378.20FF4%basavaraj.patil@nokia.com>
Message-ID: <0MKoyl-1GAP3M2EPl-0003de@mrelay.perfora.net>
X-Provags-ID: perfora.net abuse@perfora.net
	login:abf7a4bb310ea4dfc9b6841113e2970f
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Cc: 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

 
> 1. Have a single document which specifies the solution describing
>    bootstrapping with DHCPv6 which includes the DHCPv6 options that
>    are needed.

I have been trying very hard explaining that the integrated bootstrapping
solution is not "solution describing bootstrapping with DHCPv6."

If anyone wants to name the solutions that way, it'd be "solution describing
bootstrapping with DHCPv6, RADIUS, Diameter, EAP, IKEv2". 

Sigh.....

Whether this is fixed or not, my vote is for 2 (considering what is really
meant for it).



> 
> 2. Specify the DHCP options needed for bootstrapping with DHCPv6 in a
>    separate document and have this referenced in the solution I-D.
> 

Alper




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



From mip6-bounces@ietf.org Tue Aug 08 08:06:30 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GAQLq-0006SZ-B3; Tue, 08 Aug 2006 08:06:26 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GAQLo-0006R7-GK
	for mip6@ietf.org; Tue, 08 Aug 2006 08:06:24 -0400
Received: from eunet-gw.ipv6.netcore.fi ([2001:670:86:3001::1] helo=netcore.fi)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GAQLo-0006aG-1D
	for mip6@ietf.org; Tue, 08 Aug 2006 08:06:24 -0400
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.12.11.20060614/8.12.11) with ESMTP id k78C6E5k031118; 
	Tue, 8 Aug 2006 15:06:15 +0300
Date: Tue, 8 Aug 2006 15:06:14 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: Basavaraj Patil <basavaraj.patil@nokia.com>
Subject: Re: [Mip6] Consensus call: DHCPv6 options for bootstrapping
In-Reply-To: <C0FD1378.20FF4%basavaraj.patil@nokia.com>
Message-ID: <Pine.LNX.4.64.0608081504260.30578@netcore.fi>
References: <C0FD1378.20FF4%basavaraj.patil@nokia.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Virus-Scanned: ClamAV 0.88.2/1639/Mon Aug 7 16:34:09 2006 on otso.netcore.fi
X-Virus-Status: Clean
X-Spam-Status: No, score=-2.4 required=5.0 tests=AWL,BAYES_00,NO_RELAYS 
	autolearn=ham version=3.1.2
X-Spam-Checker-Version: SpamAssassin 3.1.2 (2006-05-25) on otso.netcore.fi
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

On Mon, 7 Aug 2006, Basavaraj Patil wrote:
> We are seeking WG consensus in order to resolve the issue. Please
> express your opinion w.r.t the approaches mentioned below:
>
> Options:
>
> 1. Have a single document which specifies the solution describing
>   bootstrapping with DHCPv6 which includes the DHCPv6 options that
>   are needed.
>
> 2. Specify the DHCP options needed for bootstrapping with DHCPv6 in a
>   separate document and have this referenced in the solution I-D.

Does DHC WG (which has to do significant review for the document) have 
an opinion on this ?

If I were a member of DHC WG and knew nothing (and didn't want to know 
for that matter) about MIPv6, I'd argue for 2...

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings

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



From mip6-bounces@ietf.org Tue Aug 08 09:55:49 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GAS3T-0002kB-NQ; Tue, 08 Aug 2006 09:55:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GAS3S-0002k3-P9
	for mip6@ietf.org; Tue, 08 Aug 2006 09:55:34 -0400
Received: from motgate5.mot.com ([144.189.100.105])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GAS3R-0002Nw-9g
	for mip6@ietf.org; Tue, 08 Aug 2006 09:55:34 -0400
Received: from az33exr01.mot.com (az33exr01.mot.com [10.64.251.231])
	by motgate5.mot.com (8.12.11/Motorola) with ESMTP id k78DtSaG010899
	for <mip6@ietf.org>; Tue, 8 Aug 2006 06:55:32 -0700 (MST)
Received: from ZMY16EXM66.ds.mot.com (zmy16exm66.ap.mot.com [10.179.4.26])
	by az33exr01.mot.com (8.13.1/8.13.0) with ESMTP id k78DtQHK017939
	for <mip6@ietf.org>; Tue, 8 Aug 2006 08:55:27 -0500 (CDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] Consensus call: DHCPv6 options for bootstrapping
Date: Tue, 8 Aug 2006 21:55:25 +0800
Message-ID: <C82A9B11BE247C4E952DC733EA98DAA1016F8E85@ZMY16EXM66.ds.mot.com>
In-Reply-To: <Pine.LNX.4.64.0608081504260.30578@netcore.fi>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] Consensus call: DHCPv6 options for bootstrapping
Thread-Index: Aca65ZKDewWhaSJXQiK7cngl8EcCogADHxYg
From: "Ram O V Vishnu-A14676" <vishnu@motorola.com>
To: "Pekka Savola" <pekkas@netcore.fi>,
	"Basavaraj Patil" <basavaraj.patil@nokia.com>
X-Brightmail-Tracker: AAAAAQAAAAQ=
X-White-List-Member: TRUE
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org



I have been following the discussions & I am for option-2.

Regards,
Vishnu.

Motorola=20
+91 9844178052

-----Original Message-----
From: Pekka Savola [mailto:pekkas@netcore.fi]=20
Sent: Tuesday, August 08, 2006 5:36 PM
To: Basavaraj Patil
Cc: mip6@ietf.org
Subject: Re: [Mip6] Consensus call: DHCPv6 options for bootstrapping


On Mon, 7 Aug 2006, Basavaraj Patil wrote:
> We are seeking WG consensus in order to resolve the issue. Please=20
> express your opinion w.r.t the approaches mentioned below:
>
> Options:
>
> 1. Have a single document which specifies the solution describing
>   bootstrapping with DHCPv6 which includes the DHCPv6 options that
>   are needed.
>
> 2. Specify the DHCP options needed for bootstrapping with DHCPv6 in a
>   separate document and have this referenced in the solution I-D.

Does DHC WG (which has to do significant review for the document) have=20
an opinion on this ?

If I were a member of DHC WG and knew nothing (and didn't want to know=20
for that matter) about MIPv6, I'd argue for 2...

--=20
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings

_______________________________________________
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 Aug 08 10:50:59 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GASv0-0007Pi-QG; Tue, 08 Aug 2006 10:50:54 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GASuz-0007Pd-3R
	for mip6@ietf.org; Tue, 08 Aug 2006 10:50:53 -0400
Received: from mail1.azairenet.com ([66.92.223.4] helo=bart.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GASux-0001r4-Oy
	for mip6@ietf.org; Tue, 08 Aug 2006 10:50:53 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] Consensus call: DHCPv6 options for bootstrapping
Date: Tue, 8 Aug 2006 07:50:50 -0700
Message-ID: <C8E1D942CB394746BE5CFEB7D97610E701D99656@bart.corp.azairenet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] Consensus call: DHCPv6 options for bootstrapping
Thread-Index: Aca65YNOjKHarw0OSW2+fnbSeO1MvwAFCzEg
From: "Vijay Devarapalli" <Vijay.Devarapalli@AzaireNet.com>
To: "Pekka Savola" <pekkas@netcore.fi>,
	"Basavaraj Patil" <basavaraj.patil@nokia.com>
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>
Errors-To: mip6-bounces@ietf.org

Hi Pekka,

when we check with Ralph, he said a review by the=20
DHC WG is needed when the document is last called.
other WGs like SIP, for e.g., have defined DHCP
options outside the DHCP WG.

in the other bootstrapping documents we do defined
new IKEv2 configuration payload attributes, new
DNS SRVs, etc.. doing separate documents for
everything would create a mess.

Vijay=20

> -----Original Message-----
> From: Pekka Savola [mailto:pekkas@netcore.fi]=20
> Sent: Tuesday, August 08, 2006 5:06 AM
> To: Basavaraj Patil
> Cc: mip6@ietf.org
> Subject: Re: [Mip6] Consensus call: DHCPv6 options for bootstrapping
>=20
> On Mon, 7 Aug 2006, Basavaraj Patil wrote:
> > We are seeking WG consensus in order to resolve the issue. Please
> > express your opinion w.r.t the approaches mentioned below:
> >
> > Options:
> >
> > 1. Have a single document which specifies the solution describing
> >   bootstrapping with DHCPv6 which includes the DHCPv6 options that
> >   are needed.
> >
> > 2. Specify the DHCP options needed for bootstrapping with=20
> DHCPv6 in a
> >   separate document and have this referenced in the solution I-D.
>=20
> Does DHC WG (which has to do significant review for the=20
> document) have=20
> an opinion on this ?
>=20
> If I were a member of DHC WG and knew nothing (and didn't=20
> want to know=20
> for that matter) about MIPv6, I'd argue for 2...
>=20
> --=20
> Pekka Savola                 "You each name yourselves king, yet the
> Netcore Oy                    kingdom bleeds."
> Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
>=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 Tue Aug 08 11:18:43 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GATLq-0004E4-Or; Tue, 08 Aug 2006 11:18:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GATLp-0004Dz-Gu
	for mip6@ietf.org; Tue, 08 Aug 2006 11:18:37 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GARA6-0000dA-J5
	for mip6@ietf.org; Tue, 08 Aug 2006 08:58:22 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1GAQwn-0005FA-Cc
	for mip6@ietf.org; Tue, 08 Aug 2006 08:44:40 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 08 Aug 2006 08:44:31 -0400
X-IronPort-AV: i="4.07,221,1151899200"; 
	d="scan'208"; a="95647101:sNHT26091964"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-2.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id
	k78CiURj003979; Tue, 8 Aug 2006 08:44:30 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k78CiQdt011377; 
	Tue, 8 Aug 2006 08:44:30 -0400 (EDT)
Received: from xmb-rtp-20a.amer.cisco.com ([64.102.31.15]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 8 Aug 2006 08:44:29 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] Consensus call: DHCPv6 options for bootstrapping
Date: Tue, 8 Aug 2006 08:44:27 -0400
Message-ID: <9C192798F2F9454381E4811C41A44134021FFAC5@xmb-rtp-20a.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] Consensus call: DHCPv6 options for bootstrapping
Thread-Index: Aca65YVq/FOtoSVkTw+Aj8dwMMu4KwAAqowg
From: "Shengyou Zeng \(szeng\)" <szeng@cisco.com>
To: "Pekka Savola" <pekkas@netcore.fi>,
	"Basavaraj Patil" <basavaraj.patil@nokia.com>
X-OriginalArrivalTime: 08 Aug 2006 12:44:29.0814 (UTC)
	FILETIME=[63EAA960:01C6BAE8]
DKIM-Signature: a=rsa-sha1; q=dns; l=1504; t=1155041070; x=1155905070;
	c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=szeng@cisco.com;
	z=From:=22Shengyou=20Zeng=20\(szeng\)=22=20<szeng@cisco.com>
	|Subject:RE=3A=20[Mip6]=20Consensus=20call=3A=20DHCPv6=20options=20for=20bootstra
	pping |To:=22Pekka=20Savola=22=20<pekkas@netcore.fi>,
	=0A=20=20=20=20=20=20=20=20=2
	2Basavaraj=20Patil=22=20<basavaraj.patil@nokia.com>;
	X=v=3Dcisco.com=3B=20h=3Di1IYaOgM3PqgLZhA/cXOKNl3994=3D;
	b=EFPKyJ8+oAqDQeKUxHHEnTIJSb94NCZdXPLesGqp/t3tzEYjKE+Jo8Cn0iYnWILkhKJzPWW6
	FQGvNH6petihgIeydzks0z73ZUO0TRe7a15F98AikG1pwy4UCnKEw+cf;
Authentication-Results: rtp-dkim-2.cisco.com; header.From=szeng@cisco.com;
	dkim=pass ( sig from cisco.com verified; ); 
X-Spam-Score: -2.6 (--)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

I participate in DHC WG and know a little about MIPv6, and my=20
opinion is 2 is the right way to do it.  -Shengyou=20

> -----Original Message-----
> From: Pekka Savola [mailto:pekkas@netcore.fi]=20
> Sent: Tuesday, August 08, 2006 8:06 AM
> To: Basavaraj Patil
> Cc: mip6@ietf.org
> Subject: Re: [Mip6] Consensus call: DHCPv6 options for bootstrapping
>=20
> On Mon, 7 Aug 2006, Basavaraj Patil wrote:
> > We are seeking WG consensus in order to resolve the issue. Please
> > express your opinion w.r.t the approaches mentioned below:
> >
> > Options:
> >
> > 1. Have a single document which specifies the solution describing
> >   bootstrapping with DHCPv6 which includes the DHCPv6 options that
> >   are needed.
> >
> > 2. Specify the DHCP options needed for bootstrapping with=20
> DHCPv6 in a
> >   separate document and have this referenced in the solution I-D.
>=20
> Does DHC WG (which has to do significant review for the=20
> document) have=20
> an opinion on this ?
>=20
> If I were a member of DHC WG and knew nothing (and didn't=20
> want to know=20
> for that matter) about MIPv6, I'd argue for 2...
>=20
> --=20
> Pekka Savola                 "You each name yourselves king, yet the
> Netcore Oy                    kingdom bleeds."
> Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
>=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 Tue Aug 08 11:27:09 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GATU5-0000sB-8i; Tue, 08 Aug 2006 11:27:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GATU3-0000s3-Rw
	for mip6@ietf.org; Tue, 08 Aug 2006 11:27:07 -0400
Received: from py-out-1112.google.com ([64.233.166.177])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GATU2-0008Dd-JB
	for mip6@ietf.org; Tue, 08 Aug 2006 11:27:07 -0400
Received: by py-out-1112.google.com with SMTP id b29so606736pya
	for <mip6@ietf.org>; Tue, 08 Aug 2006 08:27:06 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=OpIeu+o1jSdna0cmQ9oUUTZu/l2KkgsqIwBUMCJpVAF8OwqYBsiVg2StfP0cChgt44rE4hup5rxtbEJgQJjAv2R2a2HP4AwwzT6mKNBI1zcE/d5frgGNr4aDocFgm/lt+f0ShwwOwgeOyPz2/cmrWpUyO/1wT2MbjrZ4+3/MMWI=
Received: by 10.35.111.14 with SMTP id o14mr14808535pym;
	Tue, 08 Aug 2006 08:27:05 -0700 (PDT)
Received: by 10.35.111.9 with HTTP; Tue, 8 Aug 2006 08:27:05 -0700 (PDT)
Message-ID: <729b68be0608080827s13ce90feu15963287cc5ad40f@mail.gmail.com>
Date: Tue, 8 Aug 2006 17:27:05 +0200
From: "Jean-Michel Combes" <jeanmichel.combes@gmail.com>
To: "Vijay Devarapalli" <Vijay.Devarapalli@azairenet.com>
Subject: Re: [Mip6] Consensus call: DHCPv6 options for bootstrapping
In-Reply-To: <C8E1D942CB394746BE5CFEB7D97610E701D99656@bart.corp.azairenet.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <C8E1D942CB394746BE5CFEB7D97610E701D99656@bart.corp.azairenet.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135
Cc: mip6@ietf.org, Pekka Savola <pekkas@netcore.fi>,
	Basavaraj Patil <basavaraj.patil@nokia.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi,

I vote for option (ii).

Best regards.

JMC.

2006/8/8, Vijay Devarapalli <Vijay.Devarapalli@azairenet.com>:
> Hi Pekka,
>
> when we check with Ralph, he said a review by the
> DHC WG is needed when the document is last called.
> other WGs like SIP, for e.g., have defined DHCP
> options outside the DHCP WG.
>
> in the other bootstrapping documents we do defined
> new IKEv2 configuration payload attributes, new
> DNS SRVs, etc.. doing separate documents for
> everything would create a mess.
>
> Vijay
>
> > -----Original Message-----
> > From: Pekka Savola [mailto:pekkas@netcore.fi]
> > Sent: Tuesday, August 08, 2006 5:06 AM
> > To: Basavaraj Patil
> > Cc: mip6@ietf.org
> > Subject: Re: [Mip6] Consensus call: DHCPv6 options for bootstrapping
> >
> > On Mon, 7 Aug 2006, Basavaraj Patil wrote:
> > > We are seeking WG consensus in order to resolve the issue. Please
> > > express your opinion w.r.t the approaches mentioned below:
> > >
> > > Options:
> > >
> > > 1. Have a single document which specifies the solution describing
> > >   bootstrapping with DHCPv6 which includes the DHCPv6 options that
> > >   are needed.
> > >
> > > 2. Specify the DHCP options needed for bootstrapping with
> > DHCPv6 in a
> > >   separate document and have this referenced in the solution I-D.
> >
> > Does DHC WG (which has to do significant review for the
> > document) have
> > an opinion on this ?
> >
> > If I were a member of DHC WG and knew nothing (and didn't
> > want to know
> > for that matter) about MIPv6, I'd argue for 2...
> >
> > --
> > Pekka Savola                 "You each name yourselves king, yet the
> > Netcore Oy                    kingdom bleeds."
> > Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
> >
> > _______________________________________________
> > Mip6 mailing list
> > Mip6@ietf.org
> > https://www1.ietf.org/mailman/listinfo/mip6
> >
>
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
>

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



From mip6-bounces@ietf.org Tue Aug 08 12:17:42 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GAUGn-0003i7-2L; Tue, 08 Aug 2006 12:17:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GAUGl-0003hx-R7
	for mip6@ietf.org; Tue, 08 Aug 2006 12:17:27 -0400
Received: from mx0.starentnetworks.com ([12.38.223.203])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GAUGj-0006O5-E3
	for mip6@ietf.org; Tue, 08 Aug 2006 12:17:27 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mx0.starentnetworks.com (Postfix) with ESMTP id BE2A79002B;
	Tue,  8 Aug 2006 12:17:21 -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 12271-10; Tue, 8 Aug 2006 12:17:20 -0400 (EDT)
Received: from exchtewks1.starentnetworks.com (exchtewks1.starentnetworks.com
	[12.33.233.52]) by mx0.starentnetworks.com (Postfix) with ESMTP;
	Tue,  8 Aug 2006 12:17:20 -0400 (EDT)
X-MessageTextProcessor: DisclaimIt (2.70.271) [Starent Networks Corp.]
Received: from exchtewks2.starentnetworks.com ([12.33.232.12]) by
	exchtewks1.starentnetworks.com with Microsoft
	SMTPSVC(6.0.3790.1830); Tue, 8 Aug 2006 12:13:22 -0400
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] Consensus call: DHCPv6 options for bootstrapping
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
Date: Tue, 8 Aug 2006 12:13:22 -0400
Message-ID: <7CCD07160348804497EF29E9EA5560D7837123@exchtewks2.starentnetworks.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] Consensus call: DHCPv6 options for bootstrapping
thread-index: Aca7BZIB7KgvC2jtSdG24adXmPauPg==
From: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
Importance: normal
Priority: normal
To: "Basavaraj Patil" <basavaraj.patil@nokia.com>, <mip6@ietf.org>
X-OriginalArrivalTime: 08 Aug 2006 16:13:22.0795 (UTC)
	FILETIME=[9227CBB0:01C6BB05]
X-Virus-Scanned: amavisd-new 2.2.1 (20041222) at mx0.starentnetworks.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d
Cc: 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

I vote for option 2.

-Kuntal

> -----Original Message-----
> From: Basavaraj Patil [mailto:basavaraj.patil@nokia.com]
> Sent: Monday, August 07, 2006 3:58 PM
> To: mip6@ietf.org
> Subject: [Mip6] Consensus call: DHCPv6 options for bootstrapping
>=20
>=20
> Hello,
>=20
> We have been debating the issue of how to specify the DHCP options
> needed for bootstrapping for a while now and have not been able to
> reach any conclusions. This issue was discussed at the WG meeting at
> IETF66 and has been debated on the mailing list as well.
>=20
>=20
> I-Ds of interest here:
> a. MIP6-bootstrapping via DHCPv6 for the Integrated Scenario
>    draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt
>=20
> b. DHCP Option for Home Information Discovery in MIPv6
>    draft-jang-mip6-hiopt-00.txt
>=20
> Issue: MIP6 bootstrapping can be done using DHCPv6. The WG document
> (draft-ietf-mip6-bootstrapping-integrated-dhc-01) describes the use of
> DHCP in the integrated scenario. In order to use DHCP for
> bootstrapping several DHCP options need to be specified. The WG I-D in
> section 3.5 has specified a couple of DHCPv6 options. I-D
> draft-jang-mip6-hiopt-00 specifies several other DHCP options which
> are essential for bootstrapping.
>=20
> The issue is if the DHCP options need to be specified
>     (i) as part of the solution I-D describing bootstraping using DHCP
>     or
>     (ii) in a separate document which would then be referenced by the
>     bootstrapping with DHCP solution doc.
>=20
> We are seeking WG consensus in order to resolve the issue. Please
> express your opinion w.r.t the approaches mentioned below:
>=20
> Options:
>=20
> 1. Have a single document which specifies the solution describing
>    bootstrapping with DHCPv6 which includes the DHCPv6 options that
>    are needed.
>=20
> 2. Specify the DHCP options needed for bootstrapping with DHCPv6 in a
>    separate document and have this referenced in the solution I-D.
>=20
>=20
> Please submit your preference to the list by Aug 14th, 06.
>=20
> -Raj
>=20
>=20
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6


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

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



From mip6-bounces@ietf.org Tue Aug 08 13:11:59 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GAV7Q-0007hg-G6; Tue, 08 Aug 2006 13:11:52 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GAV7P-0007hb-9X
	for mip6@ietf.org; Tue, 08 Aug 2006 13:11:51 -0400
Received: from key1.docomolabs-usa.com ([216.98.102.225]
	helo=fridge.docomolabs-usa.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GAV7N-0000Rw-Ry
	for mip6@ietf.org; Tue, 08 Aug 2006 13:11:51 -0400
Message-ID: <004601c6bb0d$ae759bf0$266115ac@dcml.docomolabsusa.com>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Basavaraj Patil" <basavaraj.patil@nokia.com>, <mip6@ietf.org>
References: <C0FD1378.20FF4%basavaraj.patil@nokia.com>
Subject: Re: [Mip6] Consensus call: DHCPv6 options for bootstrapping
Date: Tue, 8 Aug 2006 10:11:26 -0700
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
Cc: 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Number 1.

            jak

----- Original Message ----- 
From: "Basavaraj Patil" <basavaraj.patil@nokia.com>
To: <mip6@ietf.org>
Sent: Monday, August 07, 2006 1:57 PM
Subject: [Mip6] Consensus call: DHCPv6 options for bootstrapping


> 
> Hello,
> 
> We have been debating the issue of how to specify the DHCP options
> needed for bootstrapping for a while now and have not been able to
> reach any conclusions. This issue was discussed at the WG meeting at
> IETF66 and has been debated on the mailing list as well.
> 
> 
> I-Ds of interest here:
> a. MIP6-bootstrapping via DHCPv6 for the Integrated Scenario
>   draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt
> 
> b. DHCP Option for Home Information Discovery in MIPv6
>   draft-jang-mip6-hiopt-00.txt
> 
> Issue: MIP6 bootstrapping can be done using DHCPv6. The WG document
> (draft-ietf-mip6-bootstrapping-integrated-dhc-01) describes the use of
> DHCP in the integrated scenario. In order to use DHCP for
> bootstrapping several DHCP options need to be specified. The WG I-D in
> section 3.5 has specified a couple of DHCPv6 options. I-D
> draft-jang-mip6-hiopt-00 specifies several other DHCP options which
> are essential for bootstrapping.
> 
> The issue is if the DHCP options need to be specified
>    (i) as part of the solution I-D describing bootstraping using DHCP
>    or 
>    (ii) in a separate document which would then be referenced by the
>    bootstrapping with DHCP solution doc.
> 
> We are seeking WG consensus in order to resolve the issue. Please
> express your opinion w.r.t the approaches mentioned below:
> 
> Options:
> 
> 1. Have a single document which specifies the solution describing
>   bootstrapping with DHCPv6 which includes the DHCPv6 options that
>   are needed.
> 
> 2. Specify the DHCP options needed for bootstrapping with DHCPv6 in a
>   separate document and have this referenced in the solution I-D.
> 
> 
> Please submit your preference to the list by Aug 14th, 06.
> 
> -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 Tue Aug 08 13:17:05 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GAVCT-0002Mx-CT; Tue, 08 Aug 2006 13:17:05 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GAVCS-0002Ms-Lb
	for mip6@ietf.org; Tue, 08 Aug 2006 13:17:04 -0400
Received: from web60324.mail.yahoo.com ([209.73.178.132])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1GAVCQ-0001M4-8I
	for mip6@ietf.org; Tue, 08 Aug 2006 13:17:04 -0400
Received: (qmail 23443 invoked by uid 60001); 8 Aug 2006 17:17:01 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=Message-ID:Received:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type;
	b=GZQgGdFjDNiz/rMhPFuA6yJEHEeR3+LjxTrd2lpoMZxss2UjzIJquxewrTjdn9U79wB5VE2FPEaMyJQjB8hZzqzgc1Fm+zu0A/5a8HDpocVXaNHeamvE836A99KQ/j3BC2Lhi6DEzHCfiJUFcNfCymlBHbnMb8gdAwuOSFS1Fhw=
	; 
Message-ID: <20060808171701.23430.qmail@web60324.mail.yahoo.com>
Received: from [12.129.211.52] by web60324.mail.yahoo.com via HTTP;
	Tue, 08 Aug 2006 10:17:00 PDT
Date: Tue, 8 Aug 2006 10:17:00 -0700 (PDT)
From: Behcet Sarikaya <behcetsarikaya@yahoo.com>
Subject: Re: [Mip6] Consensus call: DHCPv6 options for bootstrapping
To: mip6@ietf.org
In-Reply-To: <7CCD07160348804497EF29E9EA5560D7837123@exchtewks2.starentnetworks.com>
MIME-Version: 1.0
X-Spam-Score: 0.5 (/)
X-Scan-Signature: cf3becbbd6d1a45acbe2ffd4ab88bdc2
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Behcet Sarikaya <sarikaya@ieee.org>
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0867983536=="
Errors-To: mip6-bounces@ietf.org

--===============0867983536==
Content-Type: multipart/alternative; boundary="0-616588685-1155057420=:8947"

--0-616588685-1155057420=:8947
Content-Type: text/plain; charset=us-ascii

I also vote for option 2.
You know there is a saying, you want it, you get it.

--behcet

----- Original Message ----
From: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
To: Basavaraj Patil <basavaraj.patil@nokia.com>; mip6@ietf.org
Sent: Tuesday, August 8, 2006 11:13:22 AM
Subject: RE: [Mip6] Consensus call: DHCPv6 options for bootstrapping

I vote for option 2.

-Kuntal

> -----Original Message-----
> From: Basavaraj Patil [mailto:basavaraj.patil@nokia.com]
> Sent: Monday, August 07, 2006 3:58 PM
> To: mip6@ietf.org
> Subject: [Mip6] Consensus call: DHCPv6 options for bootstrapping
> 
> 
> Hello,
> 
> We have been debating the issue of how to specify the DHCP options
> needed for bootstrapping for a while now and have not been able to
> reach any conclusions. This issue was discussed at the WG meeting at
> IETF66 and has been debated on the mailing list as well.
> 
> 
> I-Ds of interest here:
> a. MIP6-bootstrapping via DHCPv6 for the Integrated Scenario
>    draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt
> 
> b. DHCP Option for Home Information Discovery in MIPv6
>    draft-jang-mip6-hiopt-00.txt
> 
> Issue: MIP6 bootstrapping can be done using DHCPv6. The WG document
> (draft-ietf-mip6-bootstrapping-integrated-dhc-01) describes the use of
> DHCP in the integrated scenario. In order to use DHCP for
> bootstrapping several DHCP options need to be specified. The WG I-D in
> section 3.5 has specified a couple of DHCPv6 options. I-D
> draft-jang-mip6-hiopt-00 specifies several other DHCP options which
> are essential for bootstrapping.
> 
> The issue is if the DHCP options need to be specified
>     (i) as part of the solution I-D describing bootstraping using DHCP
>     or
>     (ii) in a separate document which would then be referenced by the
>     bootstrapping with DHCP solution doc.
> 
> We are seeking WG consensus in order to resolve the issue. Please
> express your opinion w.r.t the approaches mentioned below:
> 
> Options:
> 
> 1. Have a single document which specifies the solution describing
>    bootstrapping with DHCPv6 which includes the DHCPv6 options that
>    are needed.
> 
> 2. Specify the DHCP options needed for bootstrapping with DHCPv6 in a
>    separate document and have this referenced in the solution I-D.
> 
> 
> Please submit your preference to the list by Aug 14th, 06.
> 
> -Raj
> 
> 
> _______________________________________________
> 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





--0-616588685-1155057420=:8947
Content-Type: text/html; charset=us-ascii

<html><head><style type="text/css"><!-- DIV {margin:0px} --></style></head><body><div style="font-family:courier, monaco, monospace, sans-serif;font-size:12pt"><div style="font-family: courier,monaco,monospace,sans-serif; font-size: 12pt;">I also vote for option 2.<br>You know there is a saying, you want it, you get it.<br><br>--behcet<br><br><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;">----- Original Message ----<br>From: "Chowdhury, Kuntal" &lt;kchowdhury@starentnetworks.com&gt;<br>To: Basavaraj Patil &lt;basavaraj.patil@nokia.com&gt;; mip6@ietf.org<br>Sent: Tuesday, August 8, 2006 11:13:22 AM<br>Subject: RE: [Mip6] Consensus call: DHCPv6 options for bootstrapping<br><br><div>I vote for option 2.<br><br>-Kuntal<br><br>&gt; -----Original Message-----<br>&gt; From: Basavaraj Patil [mailto:basavaraj.patil@nokia.com]<br>&gt; Sent: Monday, August 07, 2006 3:58 PM<br>&gt; To: mip6@ietf.org<br>&gt; Subject: [Mip6] Consensus call: DHCPv6
 options for bootstrapping<br>&gt; <br>&gt; <br>&gt; Hello,<br>&gt; <br>&gt; We have been debating the issue of how to specify the DHCP options<br>&gt; needed for bootstrapping for a while now and have not been able to<br>&gt; reach any conclusions. This issue was discussed at the WG meeting at<br>&gt; IETF66 and has been debated on the mailing list as well.<br>&gt; <br>&gt; <br>&gt; I-Ds of interest here:<br>&gt; a. MIP6-bootstrapping via DHCPv6 for the Integrated Scenario<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt<br>&gt; <br>&gt; b. DHCP Option for Home Information Discovery in MIPv6<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;draft-jang-mip6-hiopt-00.txt<br>&gt; <br>&gt; Issue: MIP6 bootstrapping can be done using DHCPv6. The WG document<br>&gt; (draft-ietf-mip6-bootstrapping-integrated-dhc-01) describes the use of<br>&gt; DHCP in the integrated scenario. In order to use DHCP for<br>&gt; bootstrapping several DHCP options need to be specified.
 The WG I-D in<br>&gt; section 3.5 has specified a couple of DHCPv6 options. I-D<br>&gt; draft-jang-mip6-hiopt-00 specifies several other DHCP options which<br>&gt; are essential for bootstrapping.<br>&gt; <br>&gt; The issue is if the DHCP options need to be specified<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; (i) as part of the solution I-D describing bootstraping using DHCP<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; or<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; (ii) in a separate document which would then be referenced by the<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; bootstrapping with DHCP solution doc.<br>&gt; <br>&gt; We are seeking WG consensus in order to resolve the issue. Please<br>&gt; express your opinion w.r.t the approaches mentioned below:<br>&gt; <br>&gt; Options:<br>&gt; <br>&gt; 1. Have a single document which specifies the solution describing<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;bootstrapping with DHCPv6 which includes the DHCPv6 options that<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;are needed.<br>&gt; <br>&gt; 2.
 Specify the DHCP options needed for bootstrapping with DHCPv6 in a<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;separate document and have this referenced in the solution I-D.<br>&gt; <br>&gt; <br>&gt; Please submit your preference to the list by Aug 14th, 06.<br>&gt; <br>&gt; -Raj<br>&gt; <br>&gt; <br>&gt; _______________________________________________<br>&gt; Mip6 mailing list<br>&gt; Mip6@ietf.org<br>&gt; <a target="_blank" href="https://www1.ietf.org/mailman/listinfo/mip6">https://www1.ietf.org/mailman/listinfo/mip6</a><br><br><br>"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.&nbsp;&nbsp;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."<br><br>_______________________________________________<br>Mip6 mailing list<br>Mip6@ietf.org<br><a target="_blank" href="https://www1.ietf.org/mailman/listinfo/mip6">https://www1.ietf.org/mailman/listinfo/mip6</a><br></div></div><br></div></div></body></html>
--0-616588685-1155057420=:8947--


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

--===============0867983536==--




From mip6-bounces@ietf.org Tue Aug 08 15:04:26 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GAWsL-0001GQ-9A; Tue, 08 Aug 2006 15:04:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GAWsJ-0001GK-AV
	for mip6@ietf.org; Tue, 08 Aug 2006 15:04:23 -0400
Received: from outbound-kan.frontbridge.com ([63.161.60.23]
	helo=outbound2-kan-R.bigfish.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GAWsF-0006N2-UU
	for mip6@ietf.org; Tue, 08 Aug 2006 15:04:23 -0400
Received: from outbound2-kan.bigfish.com (localhost.localdomain [127.0.0.1])
	by outbound2-kan-R.bigfish.com (Postfix) with ESMTP id B382D97DAB0;
	Tue,  8 Aug 2006 19:04:19 +0000 (UTC)
Received: from mail56-kan-R.bigfish.com (unknown [172.18.7.1])
	by outbound2-kan.bigfish.com (Postfix) with ESMTP id AB7A397DAAC;
	Tue,  8 Aug 2006 19:04:19 +0000 (UTC)
Received: from mail56-kan.bigfish.com (localhost.localdomain [127.0.0.1])
	by mail56-kan-R.bigfish.com (Postfix) with ESMTP id A0D711D42B5;
	Tue,  8 Aug 2006 19:04:19 +0000 (UTC)
X-BigFish: V
Received: by mail56-kan (MessageSwitch) id 1155063859578123_10035;
	Tue,  8 Aug 2006 19:04:19 +0000 (UCT)
Received: from smtpgw5.sprintspectrum.com (smtpgw5.sprintspectrum.com
	[207.40.188.13])
	by mail56-kan.bigfish.com (Postfix) with ESMTP id 8888F1D405C;
	Tue,  8 Aug 2006 19:04:19 +0000 (UTC)
Received: from mailhost.sprintspectrum.com (smtpgw7.it.sprintspectrum.com
	[207.40.65.55])
	by smtpgw5.sprintspectrum.com (8.12.10/8.12.8) with ESMTP id
	k78J4Iqd015420; Tue, 8 Aug 2006 14:04:18 -0500 (CDT)
Received: from plswg01a.ad.sprint.com (PLSWG01A.corp.sprint.com [10.214.11.47])
	by mailhost.sprintspectrum.com (Switch-2.2.8/Switch-2.2.8) with ESMTP
	id k78J4G323237; Tue, 8 Aug 2006 14:04:16 -0500 (CDT)
Received: from PLSWB09C.ad.sprint.com ([208.10.70.239]) by
	plswg01a.ad.sprint.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 8 Aug 2006 14:04:16 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] Consensus call: DHCPv6 options for bootstrapping
Date: Tue, 8 Aug 2006 14:04:16 -0500
Message-ID: <38586DE67CB335498A0E9BA99201311B057B1DDE@PLSWB09C.ad.sprint.com>
In-Reply-To: <C0FD1378.20FF4%basavaraj.patil@nokia.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] Consensus call: DHCPv6 options for bootstrapping
Thread-Index: Aca6ZCEDX9NMYiZXEduYJQARJNUNiAAuUAJw
From: "Hirschman, Brent B [CTO]" <Brent.Hirschman@sprint.com>
To: "Basavaraj Patil" <basavaraj.patil@nokia.com>, <mip6@ietf.org>
X-OriginalArrivalTime: 08 Aug 2006 19:04:16.0275 (UTC)
	FILETIME=[71B4AE30:01C6BB1D]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 6cca30437e2d04f45110f2ff8dc1b1d5
Cc: 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

I support option 2.

Brent Hirschman
Technology Development Strategist III
Global Technology Standards
KSOPHD0504-5D178
6220 Sprint Parkway, Overland Park, KS 66251
Voice 913-794-4271  FAX 913-794-0420
PCS 913-593-6221
Brent.Hirschman@sprint.com
IMPORTANT: This message (including any attachments) may contain
material, non-public information or proprietary information and is for
the intended recipients only. If you are not the intended recipient, you
should notify the sender and delete this message. Any disclosure,
copying, or use of this information is strictly prohibited and may
subject you to legal liability.=20


-----Original Message-----
From: Basavaraj Patil [mailto:basavaraj.patil@nokia.com]=20
Sent: Monday, August 07, 2006 3:58 PM
To: mip6@ietf.org
Subject: [Mip6] Consensus call: DHCPv6 options for bootstrapping


Hello,

We have been debating the issue of how to specify the DHCP options
needed for bootstrapping for a while now and have not been able to
reach any conclusions. This issue was discussed at the WG meeting at
IETF66 and has been debated on the mailing list as well.


I-Ds of interest here:
a. MIP6-bootstrapping via DHCPv6 for the Integrated Scenario
   draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt

b. DHCP Option for Home Information Discovery in MIPv6
   draft-jang-mip6-hiopt-00.txt

Issue: MIP6 bootstrapping can be done using DHCPv6. The WG document
(draft-ietf-mip6-bootstrapping-integrated-dhc-01) describes the use of
DHCP in the integrated scenario. In order to use DHCP for
bootstrapping several DHCP options need to be specified. The WG I-D in
section 3.5 has specified a couple of DHCPv6 options. I-D
draft-jang-mip6-hiopt-00 specifies several other DHCP options which
are essential for bootstrapping.

The issue is if the DHCP options need to be specified
    (i) as part of the solution I-D describing bootstraping using DHCP
    or=20
    (ii) in a separate document which would then be referenced by the
    bootstrapping with DHCP solution doc.

We are seeking WG consensus in order to resolve the issue. Please
express your opinion w.r.t the approaches mentioned below:

Options:

1. Have a single document which specifies the solution describing
   bootstrapping with DHCPv6 which includes the DHCPv6 options that
   are needed.

2. Specify the DHCP options needed for bootstrapping with DHCPv6 in a
   separate document and have this referenced in the solution I-D.


Please submit your preference to the list by Aug 14th, 06.

-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 Tue Aug 08 19:29:32 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GAb0s-00064k-Ld; Tue, 08 Aug 2006 19:29:30 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GAb0r-00064f-E4
	for mip6@ietf.org; Tue, 08 Aug 2006 19:29:29 -0400
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GAb0p-0005Ir-1z
	for mip6@ietf.org; Tue, 08 Aug 2006 19:29:29 -0400
Received: from neophyte.qualcomm.com (neophyte.qualcomm.com [129.46.61.149])
	by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k78NTMN6009926
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Tue, 8 Aug 2006 16:29:23 -0700
Received: from NAEXBR02.na.qualcomm.com (naexbr02.qualcomm.com [10.46.92.109])
	by neophyte.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	k78NTJDG000437; Tue, 8 Aug 2006 16:29:21 -0700 (PDT)
Received: from NAEX14.na.qualcomm.com ([10.47.5.242]) by
	NAEXBR02.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 8 Aug 2006 16:29:20 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] Consensus call: DHCPv6 options for bootstrapping
Date: Tue, 8 Aug 2006 16:29:17 -0700
Message-ID: <7EB20EA0938B4D42A2D82689365C9B7A11D2EE@NAEX14.na.qualcomm.com>
In-Reply-To: <C8E1D942CB394746BE5CFEB7D97610E701D99656@bart.corp.azairenet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] Consensus call: DHCPv6 options for bootstrapping
Thread-Index: Aca65YNOjKHarw0OSW2+fnbSeO1MvwAFCzEgABIpH5A=
From: "Soliman, Hesham" <hsoliman@qualcomm.com>
To: "Vijay Devarapalli" <Vijay.Devarapalli@azairenet.com>,
	"Pekka Savola" <pekkas@netcore.fi>,
	"Basavaraj Patil" <basavaraj.patil@nokia.com>
X-OriginalArrivalTime: 08 Aug 2006 23:29:20.0289 (UTC)
	FILETIME=[793CA110:01C6BB42]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org



 > when we check with Ralph, he said a review by the=20
 > DHC WG is needed when the document is last called.
 > other WGs like SIP, for e.g., have defined DHCP
 > options outside the DHCP WG.

=3D> A data point here. When SIP defined a new DHCP option they defined =
it
in a separate document, which was not part of any SIP spec.=20

Hesham

 >=20
 > > -----Original Message-----
 > > From: Pekka Savola [mailto:pekkas@netcore.fi]=20
 > > Sent: Tuesday, August 08, 2006 5:06 AM
 > > To: Basavaraj Patil
 > > Cc: mip6@ietf.org
 > > Subject: Re: [Mip6] Consensus call: DHCPv6 options for=20
 > bootstrapping
 > >=20
 > > On Mon, 7 Aug 2006, Basavaraj Patil wrote:
 > > > We are seeking WG consensus in order to resolve the issue. Please
 > > > express your opinion w.r.t the approaches mentioned below:
 > > >
 > > > Options:
 > > >
 > > > 1. Have a single document which specifies the solution describing
 > > >   bootstrapping with DHCPv6 which includes the DHCPv6=20
 > options that
 > > >   are needed.
 > > >
 > > > 2. Specify the DHCP options needed for bootstrapping with=20
 > > DHCPv6 in a
 > > >   separate document and have this referenced in the solution I-D.
 > >=20
 > > Does DHC WG (which has to do significant review for the=20
 > > document) have=20
 > > an opinion on this ?
 > >=20
 > > If I were a member of DHC WG and knew nothing (and didn't=20
 > > want to know=20
 > > for that matter) about MIPv6, I'd argue for 2...
 > >=20
 > > --=20
 > > Pekka Savola                 "You each name yourselves=20
 > king, yet the
 > > Netcore Oy                    kingdom bleeds."
 > > Systems. Networks. Security. -- George R.R. Martin: A=20
 > Clash of Kings
 > >=20
 > > _______________________________________________
 > > Mip6 mailing list
 > > Mip6@ietf.org
 > > https://www1.ietf.org/mailman/listinfo/mip6
 > >=20
 >=20
 > _______________________________________________
 > Mip6 mailing list
 > Mip6@ietf.org
 > https://www1.ietf.org/mailman/listinfo/mip6
 >=20

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



From mip6-bounces@ietf.org Tue Aug 08 20:29:23 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GAbwk-0007lJ-Jp; Tue, 08 Aug 2006 20:29:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GAbwj-0007lE-KI
	for mip6@ietf.org; Tue, 08 Aug 2006 20:29:17 -0400
Received: from mailout3.samsung.com ([203.254.224.33])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GAbwi-00027d-8V
	for mip6@ietf.org; Tue, 08 Aug 2006 20:29:17 -0400
Received: from ep_mmp2 (mailout3.samsung.com [203.254.224.33])
	by mailout3.samsung.com
	(iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004))
	with ESMTP id <0J3P00EL9G0PV8@mailout3.samsung.com> for mip6@ietf.org;
	Wed, 09 Aug 2006 09:29:13 +0900 (KST)
Received: from LocalHost
	(adsl-75-2-41-177.dsl.ipltin.sbcglobal.net [75.2.41.177])
	by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0J3P00897G0PZY@mmp2.samsung.com> for
	mip6@ietf.org; Wed, 09 Aug 2006 09:29:13 +0900 (KST)
Date: Wed, 09 Aug 2006 09:29:11 +0900
From: Heejin Jang <heejin.jang@samsung.com>
Subject: RE: [Mip6] Consensus call: DHCPv6 options for bootstrapping
In-reply-to: <7EB20EA0938B4D42A2D82689365C9B7A11D2EE@NAEX14.na.qualcomm.com>
To: 'Basavaraj Patil' <basavaraj.patil@nokia.com>
Message-id: <00cc01c6bb4a$d5e7a560$b129024b@LocalHost>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-index: Aca65YNOjKHarw0OSW2+fnbSeO1MvwAFCzEgABIpH5AAAhWWUA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8ac499381112328dd60aea5b1ff596ea
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

 
I support option 2. 

-Regards
Heejin


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



From mip6-bounces@ietf.org Tue Aug 08 21:53:13 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GAdFs-0003kR-Ef; Tue, 08 Aug 2006 21:53:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GAdFr-0003kM-1q
	for mip6@ietf.org; Tue, 08 Aug 2006 21:53:07 -0400
Received: from mailout3.samsung.com ([203.254.224.33])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GAdFo-0005zN-SX
	for mip6@ietf.org; Tue, 08 Aug 2006 21:53:07 -0400
Received: from ep_mmp1 (mailout3.samsung.com [203.254.224.33])
	by mailout3.samsung.com
	(iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004))
	with ESMTP id <0J3P00K6GJVA46@mailout3.samsung.com> for mip6@ietf.org;
	Wed, 09 Aug 2006 10:52:22 +0900 (KST)
Received: from your655e9d6f61 ([168.219.198.109])
	by mmp1.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14
	2004))
	with ESMTPA id <0J3P000HNJV96E@mmp1.samsung.com> for mip6@ietf.org; Wed,
	09 Aug 2006 10:52:22 +0900 (KST)
Date: Wed, 09 Aug 2006 10:52:11 +0900
From: Soohong Daniel Park <soohong.park@samsung.com>
Subject: Re: [Mip6] Consensus call: DHCPv6 options for bootstrapping
To: Basavaraj Patil <basavaraj.patil@nokia.com>, mip6@ietf.org
Message-id: <022b01c6bb56$6e899610$6dc6dba8@your655e9d6f61>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
X-Mailer: Microsoft Outlook Express 6.00.2900.2869
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
References: <C0FD1378.20FF4%basavaraj.patil@nokia.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Cc: 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Option (2)

If MIP6 makes a clear consensus now, then DHC WG 
will take this option accordingly. A separated document
is a good choice for further details...

Daniel (Soohong Daniel Park)
Mobile Convergence Laboratory, SAMSUNG Electronics.

----- Original Message ----- 
From: "Basavaraj Patil" <basavaraj.patil@nokia.com>
To: <mip6@ietf.org>
Sent: Tuesday, August 08, 2006 5:57 AM
Subject: [Mip6] Consensus call: DHCPv6 options for bootstrapping


> 
> Hello,
> 
> We have been debating the issue of how to specify the DHCP options
> needed for bootstrapping for a while now and have not been able to
> reach any conclusions. This issue was discussed at the WG meeting at
> IETF66 and has been debated on the mailing list as well.
> 
> 
> I-Ds of interest here:
> a. MIP6-bootstrapping via DHCPv6 for the Integrated Scenario
>   draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt
> 
> b. DHCP Option for Home Information Discovery in MIPv6
>   draft-jang-mip6-hiopt-00.txt
> 
> Issue: MIP6 bootstrapping can be done using DHCPv6. The WG document
> (draft-ietf-mip6-bootstrapping-integrated-dhc-01) describes the use of
> DHCP in the integrated scenario. In order to use DHCP for
> bootstrapping several DHCP options need to be specified. The WG I-D in
> section 3.5 has specified a couple of DHCPv6 options. I-D
> draft-jang-mip6-hiopt-00 specifies several other DHCP options which
> are essential for bootstrapping.
> 
> The issue is if the DHCP options need to be specified
>    (i) as part of the solution I-D describing bootstraping using DHCP
>    or 
>    (ii) in a separate document which would then be referenced by the
>    bootstrapping with DHCP solution doc.
> 
> We are seeking WG consensus in order to resolve the issue. Please
> express your opinion w.r.t the approaches mentioned below:
> 
> Options:
> 
> 1. Have a single document which specifies the solution describing
>   bootstrapping with DHCPv6 which includes the DHCPv6 options that
>   are needed.
> 
> 2. Specify the DHCP options needed for bootstrapping with DHCPv6 in a
>   separate document and have this referenced in the solution I-D.
> 
> 
> Please submit your preference to the list by Aug 14th, 06.
> 
> -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 Wed Aug 09 08:04:34 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GAmnP-0003hk-OS; Wed, 09 Aug 2006 08:04:23 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GAmnO-0003hf-05
	for mip6@ietf.org; Wed, 09 Aug 2006 08:04:22 -0400
Received: from motgate3.mot.com ([144.189.100.103])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GAmnK-0005u6-E1
	for mip6@ietf.org; Wed, 09 Aug 2006 08:04:21 -0400
Received: from az33exr03.mot.com (az33exr03.mot.com [10.64.251.233])
	by motgate3.mot.com (8.12.11/Motorola) with ESMTP id k79C4HZG010717
	for <mip6@ietf.org>; Wed, 9 Aug 2006 05:04:17 -0700 (MST)
Received: from ZMY16EXM67.ds.mot.com (zmy16exm67.ap.mot.com [10.179.4.27])
	by az33exr03.mot.com (8.13.1/8.13.0) with ESMTP id k79C4FKL007393
	for <mip6@ietf.org>; Wed, 9 Aug 2006 07:04:16 -0500 (CDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] DHCP-Diameter application for MIPv6 bootstrapping
Date: Wed, 9 Aug 2006 20:04:14 +0800
Message-ID: <AE007C20C0A3D44D8EE9DD46764559AD010B7891@ZMY16EXM67.ds.mot.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: RE: [Mip6] DHCP-Diameter application for MIPv6 bootstrapping
Thread-Index: Aca32DC+yc2EexJUSginXFSsLjQq9gCCh0TgABBhRlAAA1yy8ABdt/4w
From: "Upadhyaya Saumya-a20369" <saumya@motorola.com>
To: <mip6@ietf.org>
X-Brightmail-Tracker: AAAAAQAAAAQ=
X-White-List-Member: TRUE
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5ebbf074524e58e662bc8209a6235027
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Kuntal,

In our approach, the MN is authenticated in the home domain.=20
We mainly discuss DHCP authentication. This can be done in addition=20
to the authentication done at the NAS.

In addition, we discuss the establishment of a security association=20
Dynamically between the DHCP Server and Client.=20
The DHCP options required for establishing this=20
security association are discussed in=20
http://www.ietf.org/internet-drafts/draft-ram-dhc-dhcpv6-aakey-00.txt

- Saumya

=20

=20

-----Original Message-----
From: Chowdhury, Kuntal [mailto:kchowdhury@starentnetworks.com]=20
Sent: Monday, August 07, 2006 8:33 PM
To: Upadhyaya Saumya-a20369; mip6@ietf.org
Subject: RE: [Mip6] DHCP-Diameter application for MIPv6 bootstrapping

Saumya,

In your proposal, do you envision any kind of authentication at the DHCP
server for the MN prior to assigning the MN HA, HoA info? What is the
likelihood that operators will authenticate the MN at the DHCP server
instead of or in addition to the NAS (EAP-authenticator)?

There was a proposal a while back to use DHCP delayed authentication
scheme to perform MIP6 bootstrapping. Here is the link of the expired
I-D:

http://www.join.uni-muenster.de/Dokumente/drafts/draft-ohba-mip6-boot-ar
ch-dhcp-00.txt

Have you looked at this one?=20

-Kuntal

> -----Original Message-----
> From: Upadhyaya Saumya-a20369 [mailto:saumya@motorola.com]
> Sent: Monday, August 07, 2006 8:23 AM
> To: mip6@ietf.org
> Subject: [Mip6] DHCP-Diameter application for MIPv6 bootstrapping
>=20
> Hi Vijay,
>=20
> We have gone over the listed drafts.
>=20
> In our approach, we propose that the DHCP server contains a AAA client
> which can thereby obtain the messages from either a local entity (say,
> the AAAF/Local Diameter Proxy/NAS) or a home entity (say, the
AAAH/Home
> Diameter Server). This is in contrast to
> draft-ietf-dime-mip6-integrated-00 which proposes to obtain the
> bootstrapping parameters till the NAS using Diameter-EAP and proposes
> that the NAS behave as a DHCP Relay. In our approach, the NAS can
remain
> independent of DHCP and need not perform any operations on the DHCP
> packets that it relays.
>=20
> In our approach, we propose that the MN makes use of DHCP to obtain
the
> bootstrapping parameters irrespective of the network architecture
> (split/integrated).
>=20
> In the draft [draft-ram-dhc-dhcpv6-diam-app-00], we define a Diameter
> DHCP Application which could be used to obtain the MIPv6 bootstrapping
> parameters from the MSA.
>=20
> Regards,
> Saumya
>=20
> Date: Fri, 4 Aug 2006 08:08:42 -0700
> From: "Vijay Devarapalli" <Vijay.Devarapalli@AzaireNet.com>
> Subject: RE: [Mip6] Recommendation for bootstrapping using DHCPv6
> To: "Upadhyaya Saumya-a20369" <saumya@motorola.com>,	<mip6@ietf.org>
> Message-ID:
>=20
> <C8E1D942CB394746BE5CFEB7D97610E701D993AF@bart.corp.azairenet.com>
> Content-Type: text/plain;	charset=3D"iso-8859-1"
>=20
> Hi Saumya,
>=20
> the work on this is being done in the DIME WG. take a look at
>
http://www.ietf.org/internet-drafts/draft-ietf-dime-mip6-integrated-00.t
> xt
> http://www.ietf.org/internet-drafts/draft-ietf-dime-mip6-split-00.txt
>=20
> Vijay
>=20
>=20
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6


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

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



From mip6-bounces@ietf.org Wed Aug 09 14:09:15 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GAsUI-0002uF-QF; Wed, 09 Aug 2006 14:09:02 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GAsUG-0002th-O6
	for mip6@ietf.org; Wed, 09 Aug 2006 14:09:00 -0400
Received: from mx0.starentnetworks.com ([12.38.223.203])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GAsUD-00012f-9e
	for mip6@ietf.org; Wed, 09 Aug 2006 14:09:00 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mx0.starentnetworks.com (Postfix) with ESMTP id 91BE69000A;
	Wed,  9 Aug 2006 14:08: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 09130-06; Wed, 9 Aug 2006 14:08:52 -0400 (EDT)
Received: from exchtewks1.starentnetworks.com (exchtewks1.starentnetworks.com
	[12.33.233.52]) by mx0.starentnetworks.com (Postfix) with ESMTP;
	Wed,  9 Aug 2006 14:08:52 -0400 (EDT)
X-MessageTextProcessor: DisclaimIt (2.70.271) [Starent Networks Corp.]
Received: from exchtewks2.starentnetworks.com ([12.33.232.12]) by
	exchtewks1.starentnetworks.com with Microsoft
	SMTPSVC(6.0.3790.1830); Wed, 9 Aug 2006 14:08:47 -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.3790.1830
Subject: RE: [Mip6] DHCP-Diameter application for MIPv6 bootstrapping
Date: Wed, 9 Aug 2006 14:08:46 -0400
Message-ID: <7CCD07160348804497EF29E9EA5560D7837138@exchtewks2.starentnetworks.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] DHCP-Diameter application for MIPv6 bootstrapping
thread-index: Aca32DC+yc2EexJUSginXFSsLjQq9gCCh0TgABBhRlAAA1yy8ABdt/4wAA0zVGA=
From: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
Importance: normal
Priority: normal
To: "Upadhyaya Saumya-a20369" <saumya@motorola.com>, <mip6@ietf.org>
X-OriginalArrivalTime: 09 Aug 2006 18:08:47.0494 (UTC)
	FILETIME=[DC02C260:01C6BBDE]
X-Virus-Scanned: amavisd-new 2.2.1 (20041222) at mx0.starentnetworks.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2e8fc473f5174be667965460bd5288ba
Cc: 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Saumya,

Please see inline...=20

> -----Original Message-----
> From: Upadhyaya Saumya-a20369 [mailto:saumya@motorola.com]=20
> Sent: Wednesday, August 09, 2006 7:04 AM
> To: mip6@ietf.org
> Subject: RE: [Mip6] DHCP-Diameter application for MIPv6 bootstrapping
>=20
> Kuntal,
>=20
> In our approach, the MN is authenticated in the home domain.=20

Isn't that always the case? The HAAA is in the home domain of the MN,
right?

> We mainly discuss DHCP authentication. This can be done in=20
> addition to the authentication done at the NAS.
>=20

I am not sure about the use case where the MN will be required to
authenticate twice to get access and obtain DHCP info.=20
Someone may find such use case, but I have not seen one yet. If the
authentication function at the NAS does not exist and the DHCP
server is exposed to the public internet, may be such scheme is
desirable.

> In addition, we discuss the establishment of a security=20
> association Dynamically between the DHCP Server and Client.=20
> The DHCP options required for establishing this security=20
> association are discussed in=20
> http://www.ietf.org/internet-drafts/draft-ram-dhc-dhcpv6-aakey-00.txt
>=20

This means yet another SA setup requirement for the MN. Normally the MN
gets authenticated at the NAS (PDSN, GGSN, ASN-GW) in most of the
wireless data networks today.

> - Saumya
>=20
> =20
>=20
> =20
>=20
> -----Original Message-----
> From: Chowdhury, Kuntal [mailto:kchowdhury@starentnetworks.com]
> Sent: Monday, August 07, 2006 8:33 PM
> To: Upadhyaya Saumya-a20369; mip6@ietf.org
> Subject: RE: [Mip6] DHCP-Diameter application for MIPv6 bootstrapping
>=20
> Saumya,
>=20
> In your proposal, do you envision any kind of authentication=20
> at the DHCP server for the MN prior to assigning the MN HA,=20
> HoA info? What is the likelihood that operators will=20
> authenticate the MN at the DHCP server instead of or in=20
> addition to the NAS (EAP-authenticator)?
>=20
> There was a proposal a while back to use DHCP delayed=20
> authentication scheme to perform MIP6 bootstrapping. Here is=20
> the link of the expired
> I-D:
>=20
> http://www.join.uni-muenster.de/Dokumente/drafts/draft-ohba-mi
> p6-boot-ar
> ch-dhcp-00.txt
>=20
> Have you looked at this one?=20
>=20
> -Kuntal
>=20
> > -----Original Message-----
> > From: Upadhyaya Saumya-a20369 [mailto:saumya@motorola.com]
> > Sent: Monday, August 07, 2006 8:23 AM
> > To: mip6@ietf.org
> > Subject: [Mip6] DHCP-Diameter application for MIPv6 bootstrapping
> >=20
> > Hi Vijay,
> >=20
> > We have gone over the listed drafts.
> >=20
> > In our approach, we propose that the DHCP server contains a=20
> AAA client=20
> > which can thereby obtain the messages from either a local=20
> entity (say,=20
> > the AAAF/Local Diameter Proxy/NAS) or a home entity (say, the
> AAAH/Home
> > Diameter Server). This is in contrast to=20
> > draft-ietf-dime-mip6-integrated-00 which proposes to obtain the=20
> > bootstrapping parameters till the NAS using Diameter-EAP=20
> and proposes=20
> > that the NAS behave as a DHCP Relay. In our approach, the NAS can
> remain
> > independent of DHCP and need not perform any operations on the DHCP=20
> > packets that it relays.
> >=20
> > In our approach, we propose that the MN makes use of DHCP to obtain
> the
> > bootstrapping parameters irrespective of the network architecture=20
> > (split/integrated).
> >=20
> > In the draft [draft-ram-dhc-dhcpv6-diam-app-00], we define=20
> a Diameter=20
> > DHCP Application which could be used to obtain the MIPv6=20
> bootstrapping=20
> > parameters from the MSA.
> >=20
> > Regards,
> > Saumya
> >=20
> > Date: Fri, 4 Aug 2006 08:08:42 -0700
> > From: "Vijay Devarapalli" <Vijay.Devarapalli@AzaireNet.com>
> > Subject: RE: [Mip6] Recommendation for bootstrapping using DHCPv6
> > To: "Upadhyaya Saumya-a20369" <saumya@motorola.com>,=09
> <mip6@ietf.org>
> > Message-ID:
> >=20
> > <C8E1D942CB394746BE5CFEB7D97610E701D993AF@bart.corp.azairenet.com>
> > Content-Type: text/plain;	charset=3D"iso-8859-1"
> >=20
> > Hi Saumya,
> >=20
> > the work on this is being done in the DIME WG. take a look at
> >
> http://www.ietf.org/internet-drafts/draft-ietf-dime-mip6-integ
> rated-00.t
> > xt
> >=20
> http://www.ietf.org/internet-drafts/draft-ietf-dime-mip6-split-00.txt
> >=20
> > Vijay
> >=20
> >=20
> > _______________________________________________
> > Mip6 mailing list
> > Mip6@ietf.org
> > https://www1.ietf.org/mailman/listinfo/mip6
>=20
>=20
> "This email message and any attachments are confidential=20
> information of Starent Networks, Corp. The information=20
> transmitted may not be used to create or change any=20
> contractual obligations of Starent Networks, Corp.
> Any review, retransmission, dissemination or other use of, or=20
> taking of any action in reliance upon this e-mail and its=20
> attachments by persons or entities other than the intended=20
> recipient is prohibited. If you are not the intended=20
> recipient, please notify the sender immediately -- by=20
> replying to this message or by sending an email to=20
> postmaster@starentnetworks.com -- and destroy all copies of=20
> this message and any attachments without reading or=20
> disclosing their contents. Thank you."
>=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 Aug 09 16:47:02 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GAuxA-0002Of-GU; Wed, 09 Aug 2006 16:47:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GAux9-0002Ne-7t
	for mip6@ietf.org; Wed, 09 Aug 2006 16:46:59 -0400
Received: from atlrel7.hp.com ([156.153.255.213])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GAux7-0000rg-QI
	for mip6@ietf.org; Wed, 09 Aug 2006 16:46:59 -0400
Received: from smtp1.fc.hp.com (smtp.fc.hp.com [15.15.136.127])
	by atlrel7.hp.com (Postfix) with ESMTP id 1629B36C32;
	Wed,  9 Aug 2006 16:46:55 -0400 (EDT)
Received: from [16.116.114.13] (spaceshipone.zko.hp.com [16.116.114.13])
	by smtp1.fc.hp.com (Postfix) with ESMTP id 9AFD374BEB;
	Wed,  9 Aug 2006 20:46:54 +0000 (UTC)
Message-ID: <44DA49BD.8060109@hp.com>
Date: Wed, 09 Aug 2006 16:46:53 -0400
From: Brian Haley <brian.haley@hp.com>
Organization: Open Source and Linux Organization
User-Agent: Thunderbird 1.5.0.5 (X11/20060728)
MIME-Version: 1.0
To: Fritsche Wolfgang <Fritsche@iabg.de>
References: <69A5E767EC979846826F566C7932A3F2041F98AA@exchange03.iabg.de>
In-Reply-To: <69A5E767EC979846826F566C7932A3F2041F98AA@exchange03.iabg.de>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024
Cc: Mobile IPv6 Mailing List <mip6@ietf.org>
Subject: [Mip6] Re: Mip6: Comments on draft-ietf-mip6-hareliability-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>
Errors-To: mip6-bounces@ietf.org

Fritsche Wolfgang wrote:
> Dear members of the HA reliability DT,
> 
> after the presentation of the version 0 of the
> draft-ietf-mip6-hareliability-00.txt doc during the last IETF Mip6 WG
> meeting, I had a more detailed review on the draft and would like
> provide some comments on it. As I'm not sure if you want at this stage a
> discussion on the Mip6 mailing list, I first send them to you as draft
> contributors, however, feel free to reply on the Mip6 list if found
> appropriate.

I think the Mip6 list is the right place for this discussion as it is a 
working group document.  Changed cc to the list.

I'll just answer #4 for now since I'd need to think to answer them :)

> 1) As I understood the draft, it assumes a redundant HA set comprising a
> single Active HA and one or multiple Standby HAs. However, from an
> operational point of view it could be interesting for economic reasons,
> to have n>1 Active HAs deployed (possibly with some load balancing
> between them) and m Standby HAs, with the flexibility, that each of the
> Standby HAs could replace each of the Active HAs in case of failure.
> This flexibility would reduce the amount of Standby HAs required to m<n.
> With the current draft version I think it won't be possible. 
> One approach could be to allow the Standby HAs to join more redundant HA
> sets simultaneously, using the respective Group-ID to identify for which
> redundant HA set a certain message is destined for. If then e.g. a
> Standby HA becomes Active HA for one redundant HA set / Group-ID, it
> could decrease its preference field for all other redundant HA sets /
> Group-IDs in order to be a less preferred Standby HA there (one may even
> disregard an Active HA for one redundant HA set / Group-ID as possible
> Standby HA in another redundant HA set / Group-ID).
> 
> 2) In the draft it is not clear how a new HA learns about the HAs of a
> certain redundant HA set. Chapter 7.2.3 says here it SHOULD wait a
> particular time to listen for home agent Hello messages of all
> configured Home Agents, and alternative would be to solicit Hello
> message by sending a Hello Request message. However, based on chapter
> 7.2.1 Hello Request messages are unicasted, that is, for this purpose
> the new HA already has to know the IP address of the HA it intends to
> solicit a Hello message for. 
> Based on this I think you assume each HA from the redundant HA set is
> preconfigured with the list of all HAs being member of its redundant HA
> set. If this is correct, it would help to clearly state this somewhere
> at the beginning of the draft, e.g. at the place where the term of
> redundant HA set is introduced.
> 
> 3) In 7.5.3 the draft says "If an Active Home Agent sends the state
> synchronization message whenever the local state information such as
> binding cache changed, the size of the state synchronization message are
> large." I assume rather than "the size of the state synchronization
> message are large" you mean "the number of state synchronization
> messages are high". A single local state information change may not
> require a large state synchronization message, but if for each local
> state information change a separate state synchronization message will
> be sent, their number could easily become high.
> 
> 4)draft-ietf-mip6-hareliability-00.txt and
> draft-ietf-mip6-ha-switch-00.txt are not in the same direction
> concerning which HA will send the HA switch message to the MN.
> draft-ietf-mip6-ha-switch-00.txt assumes this will be the Active HA
> indicating to the MN that it doesn't consider itself any longer suitable
> to serve the MN (e.g. for reasons of overload, upcoming maintenance,
> ...). The HA switch message MUST here be acknowledged by the MN by
> sending a BU for deleting its current registration. 
> draft-ietf-mip6-hareliability-00.txt assumes that mainly the Standby HA
> sends the HA switch message to the MN after it detected a failure of the
> Active HA. Acknowledgement based on sending a BU for deleting its
> current registration makes no sense here, as probably the Active HA
> already failed anyway (which was also discussed on the mailing list).
> Note, based on draft-ietf-mip6-hareliability-00.txt one could send HA
> switch messages also for other reasons than Active HA failure, e.g.
> after an administratively initiated HA SwitchOver or SwitchBack event. 
> Wouldn't it be most flexible to generally allow sending a HA switch
> message from both, the Active and the Standby HA?

I didn't have time before the I-D cutoff to make this change, but it 
will be in the -01 version.

-Brian

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



From mip6-bounces@ietf.org Wed Aug 09 17:30:47 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GAvdW-0008Vj-3D; Wed, 09 Aug 2006 17:30:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GAvdU-0008Vd-Om
	for mip6@ietf.org; Wed, 09 Aug 2006 17:30:44 -0400
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GAvdT-00055z-FL
	for mip6@ietf.org; Wed, 09 Aug 2006 17:30:44 -0400
Received: from p130.piuha.net (localhost [127.0.0.1])
	by p130.piuha.net (Postfix) with ESMTP id CE43389858
	for <mip6@ietf.org>; Thu, 10 Aug 2006 00:30:41 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id 901B88984E
	for <mip6@ietf.org>; Thu, 10 Aug 2006 00:30:41 +0300 (EEST)
Message-ID: <44DA53F4.9060705@piuha.net>
Date: Thu, 10 Aug 2006 00:30:28 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Mozilla Thunderbird 1.0.8 (X11/20060725)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: mip6@ietf.org
Subject: Re: [Mip6] Consensus call: DHCPv6 options for bootstrapping
References: <C0FD1378.20FF4%basavaraj.patil@nokia.com>
	<022b01c6bb56$6e899610$6dc6dba8@your655e9d6f61>
In-Reply-To: <022b01c6bb56$6e899610$6dc6dba8@your655e9d6f61>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

For what its worth, I do not really have a preference. It seems that
we can achieve what we need either way. If the option is in the
main document it does not prevent independent use (and I would
personally be happy to see that the option can be used without
AAA). If the option is in its own document it does not relieve
the WG from the requirement of being able to explain what
the bigger picture is. Reviewers from, say, the DHC WG need
to understand at least some of the system view. Similarly,
the data carried by the option(s) needs to be fully specified
in both cases. Content is dictated by the working group,
chairs have the power to pick editors etc.

But I would like the working group to make this decision
and move on. You are spending a lot of energy on a
documentation issue as opposed to the technical work.

--Jari


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



From mip6-bounces@ietf.org Wed Aug 09 18:13:28 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GAwIm-0001b9-ER; Wed, 09 Aug 2006 18:13:24 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GAwIl-0001Zl-0n
	for mip6@ietf.org; Wed, 09 Aug 2006 18:13:23 -0400
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GAwIk-0002LW-9A
	for mip6@ietf.org; Wed, 09 Aug 2006 18:13:22 -0400
Received: from p130.piuha.net (localhost [127.0.0.1])
	by p130.piuha.net (Postfix) with ESMTP id 5811F8985E;
	Thu, 10 Aug 2006 01:13:21 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id C60A98984E;
	Thu, 10 Aug 2006 01:13:20 +0300 (EEST)
Message-ID: <44DA5DF3.2050901@piuha.net>
Date: Thu, 10 Aug 2006 01:13:07 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Mozilla Thunderbird 1.0.8 (X11/20060725)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Francis Dupont <Francis.Dupont@point6.net>
Subject: Re: [Mip6] New Charter Item:Support for Dormant Mode Alert to HA?
References: <200607251357.k6PDv1xT065992@givry.rennes.enst-bretagne.fr>
In-Reply-To: <200607251357.k6PDv1xT065992@givry.rennes.enst-bretagne.fr>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac
Cc: mip6@ietf.org, James Kempf <kempf@docomolabs-usa.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi Francis, and thanks for this note. Inline:

>I've not so arbitrary pick up one of the messages to answer...
>
>IMHO there are three issues to address: DPD, SA lifetimes, BCE.
>
>About Dead Peer Detection, RFC 4306 is very flexible. I believe there is
>no reason in this case to have each peer polling the other, i.e., one sends
>polls and says its peer is dead when it doesn't receive a small number of
>acks in a row, the other says its peer is dead when it doesn't receive a
>small (perhaps a bit larger) number of polls in a row.
>We have already in practice the HA in a passive mode, i.e., it is *never*
>the IKE initiator. To make the MN the active polling side and the HA the
>passive one seems the right way to go (but I'll come back about DPD).
>
>Security Association lifetimes: IKEv1 can negociate them but this is a
>major operational issue to get this right. IKEv2 relies on the config
>so the idea should be to have a good config. BTW at least the IKE SA
>lifetime should be in the PAD so there is no issue to put a large value
>(i.e., almost infinite) on a HA for MNs but not for other HAs.
>Again we need only rekeys initiated by one side, of course this side
>should be the MN, i.e., HAs should use almost infinite lifetimes.
>
>What is the real limit? The only thing which really requires a rekey
>is the sequence number exhaution but smaller sequence numbers are on
>32 bits: I can't see an issue for low traffic SAs, i.e., the IKE SA,
>the BU/BA transport SA, the HOTI/HOT SA, etc. The only problem can
>be with a payload SA when the MN should actively rekey in time, so
>IMHO the only case we can be in trouble (but in fact independtly of IPsec)
>is a dormant node receiving a lot of protected traffic...
>  
>
I agree with all of the above.

>BCE: even very unreasonable BCE lifetimes are a bit small (a few days,
>16 bit value in 4 second unit). If we add something IMHO this is the first
>place as the MIPv6 code can really take benefit to know the node is dormant.
>
>Come back to DPD: a passive DPD should have a good way to distinguish
>between a dormant and a dead node so I propose to add a new "private
>status" notification in DPD poll with in the data the delay to the next
>poll in second. So the passive DPD code becomes very easy to implement,
>and a MN going to the dormant node has only to send a poll with a large
>delay and wait for the ack. BTW this needs only a document, and an
>experimental RFC if we prefer a "IANA status" type.
>  
>
The key question is why we are doing the periodic traffic to
begin with. In some cases, like the NAT keepalive, we have
to do it. New protocol mechanisms wouldn't change that,
nor does the dormant status of the node.

Detecting a dead node is another reason. But in this application
it will not change the fact that packets will be dropped on the
floor. The packets are dropped both when the home agent knows
the mobile node is no longer there, and when it doesn't know.
The home agent may be able to send better ICMPs to the other side
or generate more accurate accounting records, however, but
I wonder if this is worth the extra effort.

In any case, it seems to me that most of this issue relates
to finding the right configuration parameters to suit this
particular application. If someone wants to write a document
explaining how to best configure the different protocol layers
so that battery usage and network traffic is minimized, this
would be welcome. But lets not jump into designing new protocol
mechanisms until we have documented how the current
ones should be used to avoid (most/all) of the problems.

And the dormant mode problem is not specific to Mobile IPv6
or even mobility; wireless nodes that do not move can have
exactly the same issue. This suggests a general solution
rather than a Mobile IPv6 specific one. (And I think you
were implying a general solution, for all IPsec use.)

--Jari


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



From mip6-bounces@ietf.org Thu Aug 10 09:21:20 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GBATK-0005g6-OG; Thu, 10 Aug 2006 09:21:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GBATJ-0005g1-4U
	for mip6@ietf.org; Thu, 10 Aug 2006 09:21:13 -0400
Received: from mailout3.samsung.com ([203.254.224.33])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GBATG-0003I6-LK
	for mip6@ietf.org; Thu, 10 Aug 2006 09:21:13 -0400
Received: from ep_mmp1 (mailout3.samsung.com [203.254.224.33])
	by mailout3.samsung.com
	(iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004))
	with ESMTP id <0J3S00B0VAF8SG@mailout3.samsung.com> for mip6@ietf.org;
	Thu, 10 Aug 2006 22:21:08 +0900 (KST)
Received: from NC (adsl-75-2-41-236.dsl.ipltin.sbcglobal.net [75.2.41.236])
	by mmp1.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14
	2004))
	with ESMTPA id <0J3S00AO4AF8A3@mmp1.samsung.com> for mip6@ietf.org; Thu,
	10 Aug 2006 22:21:08 +0900 (KST)
Date: Thu, 10 Aug 2006 22:21:07 +0900
From: JinHyeock Choi <jinchoe@samsung.com>
Subject: Re: [Mip6] Consensus call: DHCPv6 options for bootstrapping
To: Basavaraj Patil <basavaraj.patil@nokia.com>, mip6@ietf.org
Message-id: <004601c6bc7f$d6f44900$ec29024b@NC>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
X-Mailer: Microsoft Outlook Express 6.00.2900.2869
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
References: <C0FD1378.20FF4%basavaraj.patil@nokia.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Cc: 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

I am for option 2. 

Best Regards

JinHyeock 

----- Original Message ----- 
From: "Basavaraj Patil" <basavaraj.patil@nokia.com>
To: <mip6@ietf.org>
Sent: Tuesday, August 08, 2006 5:57 AM
Subject: [Mip6] Consensus call: DHCPv6 options for bootstrapping


> 
> Hello,
> 
> We have been debating the issue of how to specify the DHCP options
> needed for bootstrapping for a while now and have not been able to
> reach any conclusions. This issue was discussed at the WG meeting at
> IETF66 and has been debated on the mailing list as well.
> 
> 
> I-Ds of interest here:
> a. MIP6-bootstrapping via DHCPv6 for the Integrated Scenario
>   draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt
> 
> b. DHCP Option for Home Information Discovery in MIPv6
>   draft-jang-mip6-hiopt-00.txt
> 
> Issue: MIP6 bootstrapping can be done using DHCPv6. The WG document
> (draft-ietf-mip6-bootstrapping-integrated-dhc-01) describes the use of
> DHCP in the integrated scenario. In order to use DHCP for
> bootstrapping several DHCP options need to be specified. The WG I-D in
> section 3.5 has specified a couple of DHCPv6 options. I-D
> draft-jang-mip6-hiopt-00 specifies several other DHCP options which
> are essential for bootstrapping.
> 
> The issue is if the DHCP options need to be specified
>    (i) as part of the solution I-D describing bootstraping using DHCP
>    or 
>    (ii) in a separate document which would then be referenced by the
>    bootstrapping with DHCP solution doc.
> 
> We are seeking WG consensus in order to resolve the issue. Please
> express your opinion w.r.t the approaches mentioned below:
> 
> Options:
> 
> 1. Have a single document which specifies the solution describing
>   bootstrapping with DHCPv6 which includes the DHCPv6 options that
>   are needed.
> 
> 2. Specify the DHCP options needed for bootstrapping with DHCPv6 in a
>   separate document and have this referenced in the solution I-D.
> 
> 
> Please submit your preference to the list by Aug 14th, 06.
> 
> -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 Thu Aug 10 23:56:59 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GBO8h-0000IO-9D; Thu, 10 Aug 2006 23:56:51 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GBO8f-0000FJ-OS
	for mip6@ietf.org; Thu, 10 Aug 2006 23:56:49 -0400
Received: from motgate2.mot.com ([144.189.100.101])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GBO8c-0001iB-P0
	for mip6@ietf.org; Thu, 10 Aug 2006 23:56:49 -0400
Received: from az33exr02.mot.com (az33exr02.mot.com [10.64.251.232])
	by motgate2.mot.com (8.12.11/Motorola) with ESMTP id k7B3ujQf019782
	for <mip6@ietf.org>; Thu, 10 Aug 2006 20:56:45 -0700 (MST)
Received: from ZMY16EXM67.ds.mot.com (zmy16exm67.ap.mot.com [10.179.4.27])
	by az33exr02.mot.com (8.13.1/8.13.0) with ESMTP id k7B3uh2L006829
	for <mip6@ietf.org>; Thu, 10 Aug 2006 22:56:44 -0500 (CDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 11 Aug 2006 11:56:42 +0800
Message-ID: <AE007C20C0A3D44D8EE9DD46764559AD0110814A@ZMY16EXM67.ds.mot.com>
In-Reply-To: <C82A9B11BE247C4E952DC733EA98DAA1016F8E98@ZMY16EXM66.ds.mot.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [internal] DHCP-Diameter application for MIPv6 bootstrapping
Thread-Index: Aca32DC+yc2EexJUSginXFSsLjQq9gCCh0TgABBhRlAAA1yy8ABdt/4wAA0zVGAAGjlKgAAAu0cQACwz1bA=
From: "Upadhyaya Saumya-a20369" <saumya@motorola.com>
To: <kchowdhury@starentnetworks.com>, <mip6@ietf.org>
X-Brightmail-Tracker: AAAAAQAAAAQ=
X-White-List-Member: TRUE
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ded6070f7eed56e10c4f4d0d5043d9c7
Cc: 
Subject: [Mip6] RE: [internal] DHCP-Diameter application for 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>
Errors-To: mip6-bounces@ietf.org

Kuntal,

I'm highlighting the salient points of our approach:

- The DHCP Client is authenticated at the home network using a security
association between the=20
home AAA and DHCP client.
- In the process, the DHCP Client obtains authorized configuration
parameters (say, the bootstrapping info)
and security associations (for message authentication) for the DHCP
service from the home network.=20
- The bootstrapping information transferred to the DHCP client is secure
from modification as a result of
  this message authentication using the dynamically established SA.

Saumya

-----Original Message-----
From: Chowdhury, Kuntal [mailto:kchowdhury@starentnetworks.com]=20
Sent: Wednesday, August 09, 2006 11:39 PM
To: Upadhyaya Saumya-a20369; mip6@ietf.org
Subject: RE: [Mip6] DHCP-Diameter application for MIPv6 bootstrapping

Saumya,

Please see inline...=20

> -----Original Message-----
> From: Upadhyaya Saumya-a20369 [mailto:saumya@motorola.com]
> Sent: Wednesday, August 09, 2006 7:04 AM
> To: mip6@ietf.org
> Subject: RE: [Mip6] DHCP-Diameter application for MIPv6 bootstrapping
>=20
> Kuntal,
>=20
> In our approach, the MN is authenticated in the home domain.

Isn't that always the case? The HAAA is in the home domain of the MN,
right?

> We mainly discuss DHCP authentication. This can be done in
> addition to the authentication done at the NAS.
>=20

I am not sure about the use case where the MN will be required to
authenticate twice to get access and obtain DHCP info.=20
Someone may find such use case, but I have not seen one yet. If the
authentication function at the NAS does not exist and the DHCP
server is exposed to the public internet, may be such scheme is
desirable.

> In addition, we discuss the establishment of a security=20
> association Dynamically between the DHCP Server and Client.=20
> The DHCP options required for establishing this security=20
> association are discussed in=20
> http://www.ietf.org/internet-drafts/draft-ram-dhc-dhcpv6-aakey-00.txt
>=20

This means yet another SA setup requirement for the MN. Normally the MN
gets authenticated at the NAS (PDSN, GGSN, ASN-GW) in most of the
wireless data networks today.

> - Saumya
>=20
> =20
>=20
> =20
>=20
> -----Original Message-----
> From: Chowdhury, Kuntal [mailto:kchowdhury@starentnetworks.com]
> Sent: Monday, August 07, 2006 8:33 PM
> To: Upadhyaya Saumya-a20369; mip6@ietf.org
> Subject: RE: [Mip6] DHCP-Diameter application for MIPv6 bootstrapping
>=20
> Saumya,
>=20
> In your proposal, do you envision any kind of authentication=20
> at the DHCP server for the MN prior to assigning the MN HA,=20
> HoA info? What is the likelihood that operators will=20
> authenticate the MN at the DHCP server instead of or in=20
> addition to the NAS (EAP-authenticator)?
>=20
> There was a proposal a while back to use DHCP delayed=20
> authentication scheme to perform MIP6 bootstrapping. Here is=20
> the link of the expired
> I-D:
>=20
> http://www.join.uni-muenster.de/Dokumente/drafts/draft-ohba-mi
> p6-boot-ar
> ch-dhcp-00.txt
>=20
> Have you looked at this one?=20
>=20
> -Kuntal
>=20
> > -----Original Message-----
> > From: Upadhyaya Saumya-a20369 [mailto:saumya@motorola.com]
> > Sent: Monday, August 07, 2006 8:23 AM
> > To: mip6@ietf.org
> > Subject: [Mip6] DHCP-Diameter application for MIPv6 bootstrapping
> >=20
> > Hi Vijay,
> >=20
> > We have gone over the listed drafts.
> >=20
> > In our approach, we propose that the DHCP server contains a=20
> AAA client=20
> > which can thereby obtain the messages from either a local=20
> entity (say,=20
> > the AAAF/Local Diameter Proxy/NAS) or a home entity (say, the
> AAAH/Home
> > Diameter Server). This is in contrast to=20
> > draft-ietf-dime-mip6-integrated-00 which proposes to obtain the=20
> > bootstrapping parameters till the NAS using Diameter-EAP=20
> and proposes=20
> > that the NAS behave as a DHCP Relay. In our approach, the NAS can
> remain
> > independent of DHCP and need not perform any operations on the DHCP=20
> > packets that it relays.
> >=20
> > In our approach, we propose that the MN makes use of DHCP to obtain
> the
> > bootstrapping parameters irrespective of the network architecture=20
> > (split/integrated).
> >=20
> > In the draft [draft-ram-dhc-dhcpv6-diam-app-00], we define=20
> a Diameter=20
> > DHCP Application which could be used to obtain the MIPv6=20
> bootstrapping=20
> > parameters from the MSA.
> >=20
> > Regards,
> > Saumya
> >=20
> > Date: Fri, 4 Aug 2006 08:08:42 -0700
> > From: "Vijay Devarapalli" <Vijay.Devarapalli@AzaireNet.com>
> > Subject: RE: [Mip6] Recommendation for bootstrapping using DHCPv6
> > To: "Upadhyaya Saumya-a20369" <saumya@motorola.com>,=09
> <mip6@ietf.org>
> > Message-ID:
> >=20
> > <C8E1D942CB394746BE5CFEB7D97610E701D993AF@bart.corp.azairenet.com>
> > Content-Type: text/plain;	charset=3D"iso-8859-1"
> >=20
> > Hi Saumya,
> >=20
> > the work on this is being done in the DIME WG. take a look at
> >
> http://www.ietf.org/internet-drafts/draft-ietf-dime-mip6-integ
> rated-00.t
> > xt
> >=20
> http://www.ietf.org/internet-drafts/draft-ietf-dime-mip6-split-00.txt
> >=20
> > Vijay
> >=20
> >=20
> > _______________________________________________
> > Mip6 mailing list
> > Mip6@ietf.org
> > https://www1.ietf.org/mailman/listinfo/mip6
>=20
>=20
> "This email message and any attachments are confidential=20
> information of Starent Networks, Corp. The information=20
> transmitted may not be used to create or change any=20
> contractual obligations of Starent Networks, Corp.
> Any review, retransmission, dissemination or other use of, or=20
> taking of any action in reliance upon this e-mail and its=20
> attachments by persons or entities other than the intended=20
> recipient is prohibited. If you are not the intended=20
> recipient, please notify the sender immediately -- by=20
> replying to this message or by sending an email to=20
> postmaster@starentnetworks.com -- and destroy all copies of=20
> this message and any attachments without reading or=20
> disclosing their contents. Thank you."
>=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 Fri Aug 11 00:21:29 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GBOWL-0001pj-42; Fri, 11 Aug 2006 00:21:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GBOWJ-0001kF-JV
	for mip6@ietf.org; Fri, 11 Aug 2006 00:21:15 -0400
Received: from mx0.starentnetworks.com ([12.38.223.203])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GBOWJ-0003xD-2O
	for mip6@ietf.org; Fri, 11 Aug 2006 00:21:15 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mx0.starentnetworks.com (Postfix) with ESMTP id BA34490086;
	Fri, 11 Aug 2006 00:21:11 -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 16889-08; Fri, 11 Aug 2006 00:21:10 -0400 (EDT)
Received: from exchtewks1.starentnetworks.com (exchtewks1.starentnetworks.com
	[12.33.233.52]) by mx0.starentnetworks.com (Postfix) with ESMTP;
	Fri, 11 Aug 2006 00:20:56 -0400 (EDT)
X-MessageTextProcessor: DisclaimIt (2.70.271) [Starent Networks Corp.]
Received: from exchtewks2.starentnetworks.com ([12.33.232.12]) by
	exchtewks1.starentnetworks.com with Microsoft
	SMTPSVC(6.0.3790.1830); Fri, 11 Aug 2006 00:20:56 -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.3790.1830
Date: Fri, 11 Aug 2006 00:20:56 -0400
Message-ID: <7CCD07160348804497EF29E9EA5560D7837160@exchtewks2.starentnetworks.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [internal] DHCP-Diameter application for MIPv6 bootstrapping
thread-index: Aca32DC+yc2EexJUSginXFSsLjQq9gCCh0TgABBhRlAAA1yy8ABdt/4wAA0zVGAAGjlKgAAAu0cQACwz1bAAAKj3IA==
From: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
Importance: normal
To: "Upadhyaya Saumya-a20369" <saumya@motorola.com>, <mip6@ietf.org>
Priority: normal
X-OriginalArrivalTime: 11 Aug 2006 04:20:56.0283 (UTC)
	FILETIME=[8A7CF2B0:01C6BCFD]
X-Virus-Scanned: amavisd-new 2.2.1 (20041222) at mx0.starentnetworks.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7268a2980febc47a9fa732aba2b737ba
Cc: 
Subject: [Mip6] RE: [internal] DHCP-Diameter application for 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>
Errors-To: mip6-bounces@ietf.org

Saumya,

The solution for integrated scenario does not require another round of
authentication at the DHCP server. The authentication at the NAS
suffices. It also does not require second round of AAA transaction
(first between NAS-AAA, second between DHCP Server-AAA).

BTW, as I mentioned earlier, your proposed way is similar to Model 1 in
the following I-D which was submitted and discussed in IETF:

http://www.join.uni-muenster.de/Dokumente/drafts/draft-ohba-mip6-boot-ar
ch-dhcp-00.txt

FYI, there was no interest to define a scheme based on Model 1.=20

-Kuntal


> -----Original Message-----
> From: Upadhyaya Saumya-a20369 [mailto:saumya@motorola.com]
> Sent: Thursday, August 10, 2006 10:57 PM
> To: Chowdhury, Kuntal; mip6@ietf.org
> Subject: RE: [internal] DHCP-Diameter application for MIPv6
bootstrapping
>=20
> Kuntal,
>=20
> I'm highlighting the salient points of our approach:
>=20
> - The DHCP Client is authenticated at the home network using a
security
> association between the
> home AAA and DHCP client.
> - In the process, the DHCP Client obtains authorized configuration
> parameters (say, the bootstrapping info)
> and security associations (for message authentication) for the DHCP
> service from the home network.
> - The bootstrapping information transferred to the DHCP client is
secure
> from modification as a result of
>   this message authentication using the dynamically established SA.
>=20
> Saumya
>=20
> -----Original Message-----
> From: Chowdhury, Kuntal [mailto:kchowdhury@starentnetworks.com]
> Sent: Wednesday, August 09, 2006 11:39 PM
> To: Upadhyaya Saumya-a20369; mip6@ietf.org
> Subject: RE: [Mip6] DHCP-Diameter application for MIPv6 bootstrapping
>=20
> Saumya,
>=20
> Please see inline...
>=20
> > -----Original Message-----
> > From: Upadhyaya Saumya-a20369 [mailto:saumya@motorola.com]
> > Sent: Wednesday, August 09, 2006 7:04 AM
> > To: mip6@ietf.org
> > Subject: RE: [Mip6] DHCP-Diameter application for MIPv6
bootstrapping
> >
> > Kuntal,
> >
> > In our approach, the MN is authenticated in the home domain.
>=20
> Isn't that always the case? The HAAA is in the home domain of the MN,
> right?
>=20
> > We mainly discuss DHCP authentication. This can be done in
> > addition to the authentication done at the NAS.
> >
>=20
> I am not sure about the use case where the MN will be required to
> authenticate twice to get access and obtain DHCP info.
> Someone may find such use case, but I have not seen one yet. If the
> authentication function at the NAS does not exist and the DHCP
> server is exposed to the public internet, may be such scheme is
> desirable.
>=20
> > In addition, we discuss the establishment of a security
> > association Dynamically between the DHCP Server and Client.
> > The DHCP options required for establishing this security
> > association are discussed in
> >
http://www.ietf.org/internet-drafts/draft-ram-dhc-dhcpv6-aakey-00.txt
> >
>=20
> This means yet another SA setup requirement for the MN. Normally the
MN
> gets authenticated at the NAS (PDSN, GGSN, ASN-GW) in most of the
> wireless data networks today.
>=20
> > - Saumya
> >
> >
> >
> >
> >
> > -----Original Message-----
> > From: Chowdhury, Kuntal [mailto:kchowdhury@starentnetworks.com]
> > Sent: Monday, August 07, 2006 8:33 PM
> > To: Upadhyaya Saumya-a20369; mip6@ietf.org
> > Subject: RE: [Mip6] DHCP-Diameter application for MIPv6
bootstrapping
> >
> > Saumya,
> >
> > In your proposal, do you envision any kind of authentication
> > at the DHCP server for the MN prior to assigning the MN HA,
> > HoA info? What is the likelihood that operators will
> > authenticate the MN at the DHCP server instead of or in
> > addition to the NAS (EAP-authenticator)?
> >
> > There was a proposal a while back to use DHCP delayed
> > authentication scheme to perform MIP6 bootstrapping. Here is
> > the link of the expired
> > I-D:
> >
> > http://www.join.uni-muenster.de/Dokumente/drafts/draft-ohba-mi
> > p6-boot-ar
> > ch-dhcp-00.txt
> >
> > Have you looked at this one?
> >
> > -Kuntal
> >
> > > -----Original Message-----
> > > From: Upadhyaya Saumya-a20369 [mailto:saumya@motorola.com]
> > > Sent: Monday, August 07, 2006 8:23 AM
> > > To: mip6@ietf.org
> > > Subject: [Mip6] DHCP-Diameter application for MIPv6 bootstrapping
> > >
> > > Hi Vijay,
> > >
> > > We have gone over the listed drafts.
> > >
> > > In our approach, we propose that the DHCP server contains a
> > AAA client
> > > which can thereby obtain the messages from either a local
> > entity (say,
> > > the AAAF/Local Diameter Proxy/NAS) or a home entity (say, the
> > AAAH/Home
> > > Diameter Server). This is in contrast to
> > > draft-ietf-dime-mip6-integrated-00 which proposes to obtain the
> > > bootstrapping parameters till the NAS using Diameter-EAP
> > and proposes
> > > that the NAS behave as a DHCP Relay. In our approach, the NAS can
> > remain
> > > independent of DHCP and need not perform any operations on the
DHCP
> > > packets that it relays.
> > >
> > > In our approach, we propose that the MN makes use of DHCP to
obtain
> > the
> > > bootstrapping parameters irrespective of the network architecture
> > > (split/integrated).
> > >
> > > In the draft [draft-ram-dhc-dhcpv6-diam-app-00], we define
> > a Diameter
> > > DHCP Application which could be used to obtain the MIPv6
> > bootstrapping
> > > parameters from the MSA.
> > >
> > > Regards,
> > > Saumya
> > >
> > > Date: Fri, 4 Aug 2006 08:08:42 -0700
> > > From: "Vijay Devarapalli" <Vijay.Devarapalli@AzaireNet.com>
> > > Subject: RE: [Mip6] Recommendation for bootstrapping using DHCPv6
> > > To: "Upadhyaya Saumya-a20369" <saumya@motorola.com>,
> > <mip6@ietf.org>
> > > Message-ID:
> > >
> > > <C8E1D942CB394746BE5CFEB7D97610E701D993AF@bart.corp.azairenet.com>
> > > Content-Type: text/plain;	charset=3D"iso-8859-1"
> > >
> > > Hi Saumya,
> > >
> > > the work on this is being done in the DIME WG. take a look at
> > >
> > http://www.ietf.org/internet-drafts/draft-ietf-dime-mip6-integ
> > rated-00.t
> > > xt
> > >
> >
http://www.ietf.org/internet-drafts/draft-ietf-dime-mip6-split-00.txt
> > >
> > > Vijay
> > >
> > >
> > > _______________________________________________
> > > Mip6 mailing list
> > > Mip6@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/mip6
> >
> >
> > "This email message and any attachments are confidential
> > information of Starent Networks, Corp. The information
> > transmitted may not be used to create or change any
> > contractual obligations of Starent Networks, Corp.
> > Any review, retransmission, dissemination or other use of, or
> > taking of any action in reliance upon this e-mail and its
> > attachments by persons or entities other than the intended
> > recipient is prohibited. If you are not the intended
> > recipient, please notify the sender immediately -- by
> > replying to this message or by sending an email to
> > postmaster@starentnetworks.com -- and destroy all copies of
> > this message and any attachments without reading or
> > disclosing their contents. Thank you."
> >
> > _______________________________________________
> > Mip6 mailing list
> > Mip6@ietf.org
> > https://www1.ietf.org/mailman/listinfo/mip6
> >

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



From mip6-bounces@ietf.org Fri Aug 11 00:28:13 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GBOcz-0007vG-87; Fri, 11 Aug 2006 00:28:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GBOcx-0007v8-IC
	for mip6@ietf.org; Fri, 11 Aug 2006 00:28:07 -0400
Received: from py-out-1112.google.com ([64.233.166.181])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GBOcv-0004YG-2d
	for mip6@ietf.org; Fri, 11 Aug 2006 00:28:07 -0400
Received: by py-out-1112.google.com with SMTP id m51so1023307pye
	for <mip6@ietf.org>; Thu, 10 Aug 2006 21:28:04 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:reply-to:organization:user-agent:x-accept-language:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=jUal8dMg5PBoypetpZM2Taz/vfTay5XlBbKenyIhqgwoddozJqBb8IYWl9JR3OuCiygOXI0KpvMS5lrNUSyJJCN94tWWPlbfeWYQdYKqnMFWXRCtMWwHYOYTgYUHWmAxBpjNQDO8iC+Wl+RmdFG/vzBkFIdOfMaGLwXH/+f/imU=
Received: by 10.35.63.2 with SMTP id q2mr5208705pyk;
	Thu, 10 Aug 2006 21:28:04 -0700 (PDT)
Received: from ?129.254.112.125? ( [129.254.112.125])
	by mx.gmail.com with ESMTP id 37sm1251852nzf.2006.08.10.21.28.03;
	Thu, 10 Aug 2006 21:28:04 -0700 (PDT)
Message-ID: <44DC074C.60305@gmail.com>
Date: Fri, 11 Aug 2006 13:27:56 +0900
From: Myung-Ki Shin <myungki.shin@gmail.com>
Organization: ETRI
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Basavaraj Patil <basavaraj.patil@nokia.com>
Subject: Re: [Mip6] Consensus call: DHCPv6 options for bootstrapping
References: <C0FD1378.20FF4%basavaraj.patil@nokia.com>
In-Reply-To: <C0FD1378.20FF4%basavaraj.patil@nokia.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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
Reply-To: myungki.shin@gmail.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>
Errors-To: mip6-bounces@ietf.org

I favor option 2.

Thanks,
Myung-Ki,
ETRI

Basavaraj Patil wrote:
> Hello,
> 
> We have been debating the issue of how to specify the DHCP options
> needed for bootstrapping for a while now and have not been able to
> reach any conclusions. This issue was discussed at the WG meeting at
> IETF66 and has been debated on the mailing list as well.
> 
> 
> I-Ds of interest here:
> a. MIP6-bootstrapping via DHCPv6 for the Integrated Scenario
>    draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt
> 
> b. DHCP Option for Home Information Discovery in MIPv6
>    draft-jang-mip6-hiopt-00.txt
> 
> Issue: MIP6 bootstrapping can be done using DHCPv6. The WG document
> (draft-ietf-mip6-bootstrapping-integrated-dhc-01) describes the use of
> DHCP in the integrated scenario. In order to use DHCP for
> bootstrapping several DHCP options need to be specified. The WG I-D in
> section 3.5 has specified a couple of DHCPv6 options. I-D
> draft-jang-mip6-hiopt-00 specifies several other DHCP options which
> are essential for bootstrapping.
> 
> The issue is if the DHCP options need to be specified
>     (i) as part of the solution I-D describing bootstraping using DHCP
>     or 
>     (ii) in a separate document which would then be referenced by the
>     bootstrapping with DHCP solution doc.
> 
> We are seeking WG consensus in order to resolve the issue. Please
> express your opinion w.r.t the approaches mentioned below:
> 
> Options:
> 
> 1. Have a single document which specifies the solution describing
>    bootstrapping with DHCPv6 which includes the DHCPv6 options that
>    are needed.
> 
> 2. Specify the DHCP options needed for bootstrapping with DHCPv6 in a
>    separate document and have this referenced in the solution I-D.
> 
> 
> Please submit your preference to the list by Aug 14th, 06.
> 
> -Raj
>

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



From mip6-bounces@ietf.org Fri Aug 11 08:03:05 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GBVj7-0002l4-Ta; Fri, 11 Aug 2006 08:02:57 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GBVj6-0002kv-QO
	for mip6@ietf.org; Fri, 11 Aug 2006 08:02:56 -0400
Received: from yskfw1.ysknet.co.jp ([210.169.255.3] helo=ksns.ks.ysknet.co.jp)
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1GBVj5-0007N8-58
	for mip6@ietf.org; Fri, 11 Aug 2006 08:02:56 -0400
Received: (qmail 3882 invoked from network); 11 Aug 2006 21:02:50 +0900
Received: from  (HELO MIP6-236) (@) by  with SMTP; 11 Aug 2006 21:02:50 +0900
To: mip6@ietf.org
From: "K.Kawaguchi" <kawaguti@ysknet.co.jp>
Message-Id: <200608112102.EBF60915.XHBVULJB@ysknet.co.jp>
X-Mailer: Winbiff [Version 2.43 PL1]
X-Accept-Language: ja,en
Date: Fri, 11 Aug 2006 21:02:48 +0900
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Subject: [Mip6] Question about RFC3776 9.3.1 sentences
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi,

Please teach sentences of RFC3775.

Must CN send the Binding Error in situation of paragraph-1 ?
(Is paragraph-1 included in "The above tests" of paragraph-3 ?)


RFC3775
------------------------------
9.3.1.  Receiving Packets with Home Address Option

  <paragraph-1>
   Packets containing a Home Address option MUST be dropped if the given
   home address is not a unicast routable address.

  <paragraph-2>
   Mobile nodes can include a Home Address destination option in a
   packet if they believe the correspondent node has a Binding Cache
   entry for the home address of a mobile node.  Packets containing a
   Home Address option MUST be dropped if there is no corresponding
   Binding Cache entry.  A corresponding Binding Cache entry MUST have
   the same home address as appears in the Home Address destination
   option, and the currently registered care-of address MUST be equal to
   the source address of the packet.  These tests MUST NOT be done for
   packets that contain a Home Address option and a Binding Update.

  <paragraph-3>
   If the packet is dropped due the above tests, the correspondent node
                                ^^^^^^^^^^^^^^^
   MUST send the Binding Error message as described in Section 9.3.3.
   ^^^^^^^^^^^^^^^^^^^^^^^^^^^
   The Status field in this message should be set to 1 (unknown binding
   for Home Address destination option).
------------------------------


# I'm sorry. I can't reply to your answers during short japanese summer vacation. :-)


Best regards
---
Kiyoaki KAWAGUCHI


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



From mip6-bounces@ietf.org Fri Aug 11 09:03:46 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GBWfp-0006cE-NI; Fri, 11 Aug 2006 09:03:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GBWfo-0006c9-R8
	for mip6@ietf.org; Fri, 11 Aug 2006 09:03:36 -0400
Received: from motgate8.mot.com ([129.188.136.8])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GBWfm-0003yr-BR
	for mip6@ietf.org; Fri, 11 Aug 2006 09:03:36 -0400
Received: from il06exr02.mot.com (il06exr02.mot.com [129.188.137.132])
	by motgate8.mot.com (8.12.11/Motorola) with ESMTP id k7BD3YeG013763
	for <mip6@ietf.org>; Fri, 11 Aug 2006 06:03:34 -0700 (MST)
Received: from ZMY16EXM67.ds.mot.com (zmy16exm67.ap.mot.com [10.179.4.27])
	by il06exr02.mot.com (8.13.1/8.13.0) with ESMTP id k7BD3Wwq026838
	for <mip6@ietf.org>; Fri, 11 Aug 2006 08:03:33 -0500 (CDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 11 Aug 2006 21:03:31 +0800
Message-ID: <AE007C20C0A3D44D8EE9DD46764559AD011083F5@ZMY16EXM67.ds.mot.com>
In-Reply-To: <C82A9B11BE247C4E952DC733EA98DAA1016F8EB5@ZMY16EXM66.ds.mot.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: RE:DHCP-Diameter application for MIPv6bootstrapping
Thread-Index: Aca32DC+yc2EexJUSginXFSsLjQq9gCCh0TgABBhRlAAA1yy8ABdt/4wAA0zVGAAGjlKgAAAu0cQACwz1bAAAKj3IAABz6DQAAJ9YrAABQjaMAAHvrDQAAF1GSA=
From: "Upadhyaya Saumya-a20369" <saumya@motorola.com>
To: <mip6@ietf.org>
X-Brightmail-Tracker: AAAAAQAAAAQ=
X-White-List-Member: TRUE
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f8ee348dcc4be4a59bc395f7cd6343ad
Subject: [Mip6] RE:DHCP-Diameter application for MIPv6bootstrapping
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

=20
Hi Kuntal,

Thanks for your pointers.
I understand your point about Model-1 being discussed already. But I
guess what I am suggesting is:

1. In draft-ohba-mip6-boot-arch-dhcp-00.txt, section 4, there is a
statement which says -=20
"There are several protocols that can be used for carrying Mobile IPv6
   bootstrap information and a DHCP delayed authentication key from the
   NAS to the DHCP server.  SNMP is one such protocol."
I am proposing a Diameter based application messaging for that (instead
of a SNMP based one).=20
I understand that the draft-ram-dhc-dhcpv6-diam-app-00 as it is, with
its focus on authentication of DHCP client sounds/looks closer to
Model-1. May be it will need a few changes to fit into the role quoted
above. May be I will make another attempt.

Before you say "the solution" is
draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt, please read the
next 2 points too.

2. This discussion thread started after I suggested that
draft-ram-dhc-dhcpv6-diam-app-00 could be used as the north side for
draft-jang-mip6-hiopt-00.txt. In draft-jang-mip6-hiopt-00.txt, there is
statement which says " It is assumed that the DHCP server has access to
home network information for its clients for this option to be useful.".
I am proposing a Diameter application messaging for that. Now, I
understand (again) your point about double auth (once in NAS and another
in DHCP Server). But please note that the Diameter message which we are
proposing could be routed to NAS! In which case there would be
effectively only one authentication & the Bootstrapping params could be
transferred using draft-ram-dhc-dhcpv6-diam-app-00 to DHCP Server from
NAS.

3. This approach (as opposed to colocating a DHCP relay with NAS,
followed by pushing the params to DHCP Server), has some advantages: As
you see from the above paras, the DHCP Server & its implementation need
minimal changes (in the form of a AAA client). The AAA Client will
figure out to go to NAS (incase draft-ietf-dime-mip6-integrated-00.txt
is in effect), AAAF or AAAH (incase draft-jang-mip6-hiopt-00.txt) is in
effect.

Please comment.=20

- Saumya

-----Original Message-----
From: Chowdhury, Kuntal [mailto:kchowdhury@starentnetworks.com]=20
Sent: Friday, August 11, 2006 9:51 AM
To: Upadhyaya Saumya-a20369; mip6@ietf.org
Subject: [Mip6] RE: [internal] DHCP-Diameter application for
MIPv6bootstrapping


Saumya,

The solution for integrated scenario does not require another round of
authentication at the DHCP server. The authentication at the NAS
suffices. It also does not require second round of AAA transaction
(first between NAS-AAA, second between DHCP Server-AAA).

BTW, as I mentioned earlier, your proposed way is similar to Model 1 in
the following I-D which was submitted and discussed in IETF:

http://www.join.uni-muenster.de/Dokumente/drafts/draft-ohba-mip6-boot-ar
ch-dhcp-00.txt

FYI, there was no interest to define a scheme based on Model 1.=20

-Kuntal


> -----Original Message-----
> From: Upadhyaya Saumya-a20369 [mailto:saumya@motorola.com]
> Sent: Thursday, August 10, 2006 10:57 PM
> To: Chowdhury, Kuntal; mip6@ietf.org
> Subject: RE: [internal] DHCP-Diameter application for MIPv6
bootstrapping
>=20
> Kuntal,
>=20
> I'm highlighting the salient points of our approach:
>=20
> - The DHCP Client is authenticated at the home network using a
security
> association between the
> home AAA and DHCP client.
> - In the process, the DHCP Client obtains authorized configuration=20
> parameters (say, the bootstrapping info) and security associations=20
> (for message authentication) for the DHCP service from the home=20
> network.
> - The bootstrapping information transferred to the DHCP client is
secure
> from modification as a result of
>   this message authentication using the dynamically established SA.
>=20
> Saumya
>=20
> -----Original Message-----
> From: Chowdhury, Kuntal [mailto:kchowdhury@starentnetworks.com]
> Sent: Wednesday, August 09, 2006 11:39 PM
> To: Upadhyaya Saumya-a20369; mip6@ietf.org
> Subject: RE: [Mip6] DHCP-Diameter application for MIPv6 bootstrapping
>=20
> Saumya,
>=20
> Please see inline...
>=20
> > -----Original Message-----
> > From: Upadhyaya Saumya-a20369 [mailto:saumya@motorola.com]
> > Sent: Wednesday, August 09, 2006 7:04 AM
> > To: mip6@ietf.org
> > Subject: RE: [Mip6] DHCP-Diameter application for MIPv6
bootstrapping
> >
> > Kuntal,
> >
> > In our approach, the MN is authenticated in the home domain.
>=20
> Isn't that always the case? The HAAA is in the home domain of the MN,=20
> right?
>=20
> > We mainly discuss DHCP authentication. This can be done in addition=20
> > to the authentication done at the NAS.
> >
>=20
> I am not sure about the use case where the MN will be required to=20
> authenticate twice to get access and obtain DHCP info. Someone may=20
> find such use case, but I have not seen one yet. If the authentication

> function at the NAS does not exist and the DHCP server is exposed to=20
> the public internet, may be such scheme is desirable.
>=20
> > In addition, we discuss the establishment of a security association=20
> > Dynamically between the DHCP Server and Client. The DHCP options=20
> > required for establishing this security association are discussed in
> >
http://www.ietf.org/internet-drafts/draft-ram-dhc-dhcpv6-aakey-00.txt
> >
>=20
> This means yet another SA setup requirement for the MN. Normally the
MN
> gets authenticated at the NAS (PDSN, GGSN, ASN-GW) in most of the=20
> wireless data networks today.
>=20
> > - Saumya
> >
> >
> >
> >
> >
> > -----Original Message-----
> > From: Chowdhury, Kuntal [mailto:kchowdhury@starentnetworks.com]
> > Sent: Monday, August 07, 2006 8:33 PM
> > To: Upadhyaya Saumya-a20369; mip6@ietf.org
> > Subject: RE: [Mip6] DHCP-Diameter application for MIPv6
bootstrapping
> >
> > Saumya,
> >
> > In your proposal, do you envision any kind of authentication at the=20
> > DHCP server for the MN prior to assigning the MN HA, HoA info? What=20
> > is the likelihood that operators will authenticate the MN at the=20
> > DHCP server instead of or in addition to the NAS=20
> > (EAP-authenticator)?
> >
> > There was a proposal a while back to use DHCP delayed authentication

> > scheme to perform MIP6 bootstrapping. Here is the link of the=20
> > expired
> > I-D:
> >
> > http://www.join.uni-muenster.de/Dokumente/drafts/draft-ohba-mi
> > p6-boot-ar
> > ch-dhcp-00.txt
> >
> > Have you looked at this one?
> >
> > -Kuntal
> >
> > > -----Original Message-----
> > > From: Upadhyaya Saumya-a20369 [mailto:saumya@motorola.com]
> > > Sent: Monday, August 07, 2006 8:23 AM
> > > To: mip6@ietf.org
> > > Subject: [Mip6] DHCP-Diameter application for MIPv6 bootstrapping
> > >
> > > Hi Vijay,
> > >
> > > We have gone over the listed drafts.
> > >
> > > In our approach, we propose that the DHCP server contains a
> > AAA client
> > > which can thereby obtain the messages from either a local
> > entity (say,
> > > the AAAF/Local Diameter Proxy/NAS) or a home entity (say, the
> > AAAH/Home
> > > Diameter Server). This is in contrast to=20
> > > draft-ietf-dime-mip6-integrated-00 which proposes to obtain the=20
> > > bootstrapping parameters till the NAS using Diameter-EAP
> > and proposes
> > > that the NAS behave as a DHCP Relay. In our approach, the NAS can
> > remain
> > > independent of DHCP and need not perform any operations on the
DHCP
> > > packets that it relays.
> > >
> > > In our approach, we propose that the MN makes use of DHCP to
obtain
> > the
> > > bootstrapping parameters irrespective of the network architecture=20
> > > (split/integrated).
> > >
> > > In the draft [draft-ram-dhc-dhcpv6-diam-app-00], we define
> > a Diameter
> > > DHCP Application which could be used to obtain the MIPv6
> > bootstrapping
> > > parameters from the MSA.
> > >
> > > Regards,
> > > Saumya
> > >
> > > Date: Fri, 4 Aug 2006 08:08:42 -0700
> > > From: "Vijay Devarapalli" <Vijay.Devarapalli@AzaireNet.com>
> > > Subject: RE: [Mip6] Recommendation for bootstrapping using DHCPv6
> > > To: "Upadhyaya Saumya-a20369" <saumya@motorola.com>,
> > <mip6@ietf.org>
> > > Message-ID:
> > >
> > > <C8E1D942CB394746BE5CFEB7D97610E701D993AF@bart.corp.azairenet.com>
> > > Content-Type: text/plain;	charset=3D"iso-8859-1"
> > >
> > > Hi Saumya,
> > >
> > > the work on this is being done in the DIME WG. take a look at
> > >
> > http://www.ietf.org/internet-drafts/draft-ietf-dime-mip6-integ
> > rated-00.t
> > > xt
> > >
> >
http://www.ietf.org/internet-drafts/draft-ietf-dime-mip6-split-00.txt
> > >
> > > Vijay
> > >
> > >
> > > _______________________________________________
> > > 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=20
> > used to create or change any contractual obligations of Starent=20
> > Networks, Corp. Any review, retransmission, dissemination or other=20
> > 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=20
> > the sender immediately -- by replying to this message or by sending=20
> > an email to postmaster@starentnetworks.com -- and destroy all copies

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

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

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



From mip6-bounces@ietf.org Fri Aug 11 18:43:50 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GBfj4-0005M3-MG; Fri, 11 Aug 2006 18:43:34 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GBfj3-0005Ly-Ph
	for mip6@ietf.org; Fri, 11 Aug 2006 18:43:33 -0400
Received: from mail1.azairenet.com ([66.92.223.4] helo=bart.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GBfj1-0007Bz-EN
	for mip6@ietf.org; Fri, 11 Aug 2006 18:43:33 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] Question about RFC3776 9.3.1 sentences
Date: Fri, 11 Aug 2006 15:43:29 -0700
Message-ID: <C8E1D942CB394746BE5CFEB7D97610E701D99AE5@bart.corp.azairenet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] Question about RFC3776 9.3.1 sentences
Thread-Index: Aca9QIjmTiy8Ik/YSD6OjSZC/r/mEQAVn80g
From: "Vijay Devarapalli" <Vijay.Devarapalli@AzaireNet.com>
To: "K.Kawaguchi" <kawaguti@ysknet.co.jp>,
	<mip6@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Cc: 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

there is no need for a binding error in the first case
where the packet was dropped because the home address
was not a unicast routable address.

I guess the confusion is caused by the phrase "the=20
above  tests". the "above" only refers to the preceding=20
paragraph (paragraph-2 in your email).

Vijay

> -----Original Message-----
> From: K.Kawaguchi [mailto:kawaguti@ysknet.co.jp]=20
> Sent: Friday, August 11, 2006 5:03 AM
> To: mip6@ietf.org
> Subject: [Mip6] Question about RFC3776 9.3.1 sentences
>=20
> Hi,
>=20
> Please teach sentences of RFC3775.
>=20
> Must CN send the Binding Error in situation of paragraph-1 ?
> (Is paragraph-1 included in "The above tests" of paragraph-3 ?)
>=20
>=20
> RFC3775
> ------------------------------
> 9.3.1.  Receiving Packets with Home Address Option
>=20
>   <paragraph-1>
>    Packets containing a Home Address option MUST be dropped=20
> if the given
>    home address is not a unicast routable address.
>=20
>   <paragraph-2>
>    Mobile nodes can include a Home Address destination option in a
>    packet if they believe the correspondent node has a Binding Cache
>    entry for the home address of a mobile node.  Packets containing a
>    Home Address option MUST be dropped if there is no corresponding
>    Binding Cache entry.  A corresponding Binding Cache entry MUST have
>    the same home address as appears in the Home Address destination
>    option, and the currently registered care-of address MUST=20
> be equal to
>    the source address of the packet.  These tests MUST NOT be done for
>    packets that contain a Home Address option and a Binding Update.
>=20
>   <paragraph-3>
>    If the packet is dropped due the above tests, the=20
> correspondent node
>                                 ^^^^^^^^^^^^^^^
>    MUST send the Binding Error message as described in Section 9.3.3.
>    ^^^^^^^^^^^^^^^^^^^^^^^^^^^
>    The Status field in this message should be set to 1=20
> (unknown binding
>    for Home Address destination option).
> ------------------------------
>=20
>=20
> # I'm sorry. I can't reply to your answers during short=20
> japanese summer vacation. :-)
>=20
>=20
> Best regards
> ---
> Kiyoaki KAWAGUCHI
>=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 Fri Aug 11 19:02:49 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GBg1W-00064U-Rv; Fri, 11 Aug 2006 19:02:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GBfys-000522-8d
	for mip6@ietf.org; Fri, 11 Aug 2006 18:59:54 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GBfoW-00082A-5w
	for mip6@ietf.org; Fri, 11 Aug 2006 18:49:12 -0400
Received: from fruitcake.icsi.berkeley.edu ([192.150.186.11])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1GBfoV-00061Z-5g
	for mip6@ietf.org; Fri, 11 Aug 2006 18:49:12 -0400
Received: from shrimp (shrimp [192.150.186.31])
	by fruitcake.ICSI.Berkeley.EDU (8.12.11.20060614/8.12.9) with ESMTP id
	k7BMn8SY007908
	for <mip6@ietf.org>; Fri, 11 Aug 2006 15:49:08 -0700 (PDT)
From: Zhen Chen <zhenchen@ICSI.Berkeley.EDU>
To: mip6@ietf.org
Content-Type: text/plain
Organization: International Computer Science Institute
Message-Id: <1155336548.19749.316.camel@shrimp>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.5 (1.4.5-17) 
Date: Fri, 11 Aug 2006 15:49:08 -0700
Content-Transfer-Encoding: 7bit
X-Spam-Score: -2.6 (--)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976
Subject: [Mip6] A bug in RFC3775.
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: zhenchen@ICSI.Berkeley.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>
Errors-To: mip6-bounces@ietf.org

Hi everyone, 
  I am working in mobile IPv6. I find a bug in RFC3775. It is
self-contradiction. :)
  I infer that The section 6.4 is correct and the 9.3.2 is wrong.  and
the section 10.4.2 is also wrong, because it uses section 9.3.2. 

Has this bug been corrected? 

See:

6.4.  Type 2 Routing Header

   Mobile IPv6 defines a new routing header variant, the type 2 routing
   header, to allow the packet to be routed directly from a
   correspondent to the mobile node's care-of address.  
The mobile
   node's care-of address is inserted into the IPv6 Destination Address
   field.  Once the packet arrives at the care-of address, the mobile
   node retrieves its home address from the routing header, and this is
   used as the final destination address for the packet.

   


9.3.2.  Sending Packets to a Mobile Node

   Before sending any packet, the sending node SHOULD examine its
   Binding Cache for an entry for the destination address to which the
   packet is being sent. 
----->>>> If the sending node has a Binding Cache entry
   for this address, the sending node SHOULD use a type 2 routing header
   to route the packet to this mobile node (the destination node) by way
   of its care-of address. 

   For instance, assuming there are no additional routing headers in
   this packet beyond those needed by Mobile IPv6, the correspondent
   node could set the fields in the packet's IPv6 header and routing
   header as follows:

   o  The ~~~Destination Address~~~~ in the packet's IPv6 header is set
to the
      mobile node's ~~~~~home address~~~~~~~~~~ (the original
destination address to
      which the packet was being sent).
   o  The routing header is initialized to contain a single route
      segment, containing the mobile node's ~~~care-of address~~~~~
copied from
      the Binding Cache entry.  The Segments Left field is, however,
      temporarily set to zero.

   The IP layer will insert the routing header before performing any
   necessary IPsec processing.  Once all IPsec processing has been
   performed, the node swaps the IPv6 destination field with the Home
   Address field in the routing header, sets the Segments Left field to
   one, and sends the packet.  This ensures the AH calculation is done
   on the packet in the form it will have on the receiver after
   advancing the routing header.

   Following the definition of a type 2 routing header in Section 6.4,
   this packet will be routed to the mobile node's care-of address,
   where it will be delivered to the mobile node (the mobile node has
   associated the care-of address with its network interface).



  ---------- If, instead, the sending node has no Binding Cache entry
for the
   destination address to which the packet is being sent, the sending
   node simply sends the packet normally, with no routing header. 

If
   the destination node is not a mobile node (or is a mobile node that
   is currently at home), the packet will be delivered directly to this
   node and processed normally by it.  If, however, the destination node
   is a mobile node that is currently away from home, the packet will be
   intercepted by the mobile node's home agent and tunneled to the
   mobile node's current primary care-of address.





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



From mip6-bounces@ietf.org Fri Aug 11 19:25:57 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GBgNt-0000qK-RB; Fri, 11 Aug 2006 19:25:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GBgNs-0000qF-AX
	for mip6@ietf.org; Fri, 11 Aug 2006 19:25:44 -0400
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GBgNq-0003sF-VC
	for mip6@ietf.org; Fri, 11 Aug 2006 19:25:44 -0400
Received: from sj-dkim-6.cisco.com ([171.68.10.81])
	by sj-iport-4.cisco.com with ESMTP; 11 Aug 2006 16:25:42 -0700
X-IronPort-AV: i="4.08,116,1154934000"; 
	d="scan'208"; a="1846388353:sNHT32064200"
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138])
	by sj-dkim-6.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id
	k7BNPgVw004886; Fri, 11 Aug 2006 16:25:42 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id k7BNPfIZ026454;
	Fri, 11 Aug 2006 16:25:41 -0700 (PDT)
Received: from xmb-sjc-235.amer.cisco.com ([128.107.191.85]) by
	xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 11 Aug 2006 16:25:41 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] Consensus call: DHCPv6 options for bootstrapping
Date: Fri, 11 Aug 2006 16:25:40 -0700
Message-ID: <2979E38DD6FC6544B789C8DAD7BAFC52024F427B@xmb-sjc-235.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] Consensus call: DHCPv6 options for bootstrapping
Thread-Index: Aca6ZCEDX9NMYiZXEduYJQARJNUNiABqjYiA
From: "Kent Leung \(kleung\)" <kleung@cisco.com>
To: "Basavaraj Patil" <basavaraj.patil@nokia.com>, <mip6@ietf.org>
X-OriginalArrivalTime: 11 Aug 2006 23:25:41.0888 (UTC)
	FILETIME=[764C8800:01C6BD9D]
DKIM-Signature: a=rsa-sha1; q=dns; l=2443; t=1155338742; x=1156202742;
	c=relaxed/simple; s=sjdkim6002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=kleung@cisco.com;
	z=From:=22Kent=20Leung=20\(kleung\)=22=20<kleung@cisco.com>
	|Subject:RE=3A=20[Mip6]=20Consensus=20call=3A=20DHCPv6=20options=20for=20bootstra
	pping; X=v=3Dcisco.com=3B=20h=3DfnzvapiS0RxO/qo8zPxOgis5MDU=3D;
	b=MBLxxdnRLpohzthdb8Fr/2C+c8y4wmxZa8TH1vlbDMS7NTVj/aV+wCZSD+nz/LEUuElJbwwu
	2VUWc1lEi0mig83Sj/xBzjHWnQIsibv/NuKnWF2oiRw71S87MGf22a+e;
Authentication-Results: sj-dkim-6.cisco.com; header.From=kleung@cisco.com;
	dkim=pass ( sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Cc: 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

I'm assuming that Option #1 would not include the Home Address Option.
This is needed in 3GPP2's TIA-835 Rev D.

I vote for #2 so various schemes could make use of the DHCP Options.

Kent=20

> -----Original Message-----
> From: Basavaraj Patil [mailto:basavaraj.patil@nokia.com]=20
> Sent: Monday, August 07, 2006 1:58 PM
> To: mip6@ietf.org
> Subject: [Mip6] Consensus call: DHCPv6 options for bootstrapping
>=20
>=20
> Hello,
>=20
> We have been debating the issue of how to specify the DHCP=20
> options needed for bootstrapping for a while now and have not=20
> been able to reach any conclusions. This issue was discussed=20
> at the WG meeting at
> IETF66 and has been debated on the mailing list as well.
>=20
>=20
> I-Ds of interest here:
> a. MIP6-bootstrapping via DHCPv6 for the Integrated Scenario
>    draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt
>=20
> b. DHCP Option for Home Information Discovery in MIPv6
>    draft-jang-mip6-hiopt-00.txt
>=20
> Issue: MIP6 bootstrapping can be done using DHCPv6. The WG document
> (draft-ietf-mip6-bootstrapping-integrated-dhc-01) describes=20
> the use of DHCP in the integrated scenario. In order to use=20
> DHCP for bootstrapping several DHCP options need to be=20
> specified. The WG I-D in section 3.5 has specified a couple=20
> of DHCPv6 options. I-D draft-jang-mip6-hiopt-00 specifies=20
> several other DHCP options which are essential for bootstrapping.
>=20
> The issue is if the DHCP options need to be specified
>     (i) as part of the solution I-D describing bootstraping using DHCP
>     or=20
>     (ii) in a separate document which would then be referenced by the
>     bootstrapping with DHCP solution doc.
>=20
> We are seeking WG consensus in order to resolve the issue.=20
> Please express your opinion w.r.t the approaches mentioned below:
>=20
> Options:
>=20
> 1. Have a single document which specifies the solution describing
>    bootstrapping with DHCPv6 which includes the DHCPv6 options that
>    are needed.
>=20
> 2. Specify the DHCP options needed for bootstrapping with DHCPv6 in a
>    separate document and have this referenced in the solution I-D.
>=20
>=20
> Please submit your preference to the list by Aug 14th, 06.
>=20
> -Raj
>=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 Fri Aug 11 23:37:48 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GBkJY-0002Va-63; Fri, 11 Aug 2006 23:37:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GBkJW-0002VR-NW
	for mip6@ietf.org; Fri, 11 Aug 2006 23:37:30 -0400
Received: from ccerelrim02.cce.hp.com ([161.114.21.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GBkJV-00048o-Fb
	for mip6@ietf.org; Fri, 11 Aug 2006 23:37:30 -0400
Received: from ccerelrim02.cce.hp.com (localhost [127.0.0.1])
	by receive-from-antispam-filter (Postfix) with SMTP id 564DC330B8;
	Fri, 11 Aug 2006 22:43:05 -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 06D0832EBD;
	Fri, 11 Aug 2006 22:43:04 -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 D1C48CD92; Fri, 11 Aug 2006 22:37:26 -0500 (CDT)
Message-ID: <44DD4D24.8010101@hp.com>
Date: Fri, 11 Aug 2006 23:38:12 -0400
From: Brian Haley <Brian.Haley@hp.com>
Organization: Linux and Open Source Lab
User-Agent: Thunderbird 1.5.0.5 (Windows/20060719)
MIME-Version: 1.0
To: zhenchen@ICSI.Berkeley.EDU
Subject: Re: [Mip6] A bug in RFC3775.
References: <1155336548.19749.316.camel@shrimp>
In-Reply-To: <1155336548.19749.316.camel@shrimp>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-PMX-Version: 5.1.2.240295, Antispam-Engine: 2.3.0.1,
	Antispam-Data: 2006.8.11.201933
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Zhen Chen wrote:
> Hi everyone, 
>   I am working in mobile IPv6. I find a bug in RFC3775. It is
> self-contradiction. :)
>   I infer that The section 6.4 is correct and the 9.3.2 is wrong.  and
> the section 10.4.2 is also wrong, because it uses section 9.3.2.

So I'll assume your saying the text on how to build a Type 2 routing 
header is inconsistent?  It looks correct to me, and we've had many 
inter-operable implementations tested against each other successfully 
(including mine :).  Maybe you can describe in a paragraph what you 
think the problem is, maybe I'm missing something?  Your snippets of 
text are confusing since you're leaving out intermediate paragraphs that 
are pretty useful, like:

    When calculating authentication data in a packet that contains a type
    2 routing header, the correspondent node MUST calculate the AH
    authentication data as if the following were true: The routing header
    contains the care-of address, the destination IPv6 address field of
    the IPv6 header contains the home address, and the Segments Left
    field is zero.  The IPsec Security Policy Database lookup MUST based
    on the mobile node's home address.

Maybe this is the crux of the confusion?  For security calculations the 
IPv6 source address is always the home address.

-Brian

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



From mip6-bounces@ietf.org Sat Aug 12 00:22:07 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GBl0d-0006KW-HH; Sat, 12 Aug 2006 00:22:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GBl0c-0006Gk-DW
	for mip6@ietf.org; Sat, 12 Aug 2006 00:22:02 -0400
Received: from fruitcake.icsi.berkeley.edu ([192.150.186.11])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GBl0Z-0007Li-VS
	for mip6@ietf.org; Sat, 12 Aug 2006 00:22:02 -0400
Received: from shrimp (shrimp [192.150.186.31])
	by fruitcake.ICSI.Berkeley.EDU (8.12.11.20060614/8.12.9) with ESMTP id
	k7C4LtBR013543; Fri, 11 Aug 2006 21:21:55 -0700 (PDT)
Subject: Re: [Mip6] A bug in RFC3775.
From: Zhen Chen <zhenchen@ICSI.Berkeley.EDU>
To: Brian Haley <Brian.Haley@hp.com>
In-Reply-To: <44DD4D24.8010101@hp.com>
References: <1155336548.19749.316.camel@shrimp>  <44DD4D24.8010101@hp.com>
Content-Type: text/plain
Organization: International Computer Science Institute
Message-Id: <1155356515.19749.338.camel@shrimp>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.5 (1.4.5-17) 
Date: Fri, 11 Aug 2006 21:21:55 -0700
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: zhenchen@ICSI.Berkeley.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>
Errors-To: mip6-bounces@ietf.org

thanks your comments.
In my understanding, message send from CN--->>>MN
in Section 6.4 
home address inserted into T2 routing header, while
Care-of Address inserted into Destination address of Packet

while in Section 9.3.2 still the case CN--->>>MN
Home Address is inserted into Destination address of packet, while
Care-of Address inserted into T2 Routing header of Packet

Could you help me to check it again? thanks!

Best,

Zhen

On Fri, 2006-08-11 at 20:38, Brian Haley wrote:
> Zhen Chen wrote:
> > Hi everyone, 
> >   I am working in mobile IPv6. I find a bug in RFC3775. It is
> > self-contradiction. :)
> >   I infer that The section 6.4 is correct and the 9.3.2 is wrong.  and
> > the section 10.4.2 is also wrong, because it uses section 9.3.2.
> 
> So I'll assume your saying the text on how to build a Type 2 routing 
> header is inconsistent?  It looks correct to me, and we've had many 
> inter-operable implementations tested against each other successfully 
> (including mine :).  Maybe you can describe in a paragraph what you 
> think the problem is, maybe I'm missing something?  Your snippets of 
> text are confusing since you're leaving out intermediate paragraphs that 
> are pretty useful, like:
> 
>     When calculating authentication data in a packet that contains a type
>     2 routing header, the correspondent node MUST calculate the AH
>     authentication data as if the following were true: The routing header
>     contains the care-of address, the destination IPv6 address field of
>     the IPv6 header contains the home address, and the Segments Left
>     field is zero.  The IPsec Security Policy Database lookup MUST based
>     on the mobile node's home address.
> 
> Maybe this is the crux of the confusion?  For security calculations the 
> IPv6 source address is always the home address.
> 
> -Brian
> 
> _______________________________________________
> 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 Aug 13 23:04:04 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GCSk7-0002rs-Aj; Sun, 13 Aug 2006 23:03:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GCSk6-0002rn-7b
	for mip6@ietf.org; Sun, 13 Aug 2006 23:03:54 -0400
Received: from otm-mgo01.iij.ad.jp ([210.138.20.175])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GCSk3-00040W-Mo
	for mip6@ietf.org; Sun, 13 Aug 2006 23:03:54 -0400
Received: OTM-MO(otm-mgo01) id k7E33iB2010974;
	Mon, 14 Aug 2006 12:03:44 +0900 (JST)
Received: OTM-MIX(otm-mix00) id k7E33i8J082789;
	Mon, 14 Aug 2006 12:03:44 +0900 (JST)
Received: from [192.168.64.81] (n064-h081-dhcp.osaka.iij.ad.jp [192.168.64.81])
	by rsmtp.iij.ad.jp (OTM-MR/rsmtp) id k7E33h7a024787
	(version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT);
	Mon, 14 Aug 2006 12:03:43 +0900 (JST)
In-Reply-To: <1155356515.19749.338.camel@shrimp>
References: <1155336548.19749.316.camel@shrimp> <44DD4D24.8010101@hp.com>
	<1155356515.19749.338.camel@shrimp>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <D85DDD80-0259-4328-A446-FB37B6B93145@iijlab.net>
Content-Transfer-Encoding: 7bit
From: Keiichi SHIMA <keiichi@iijlab.net>
Subject: Re: [Mip6] A bug in RFC3775.
Date: Mon, 14 Aug 2006 12:03:49 +0900
To: zhenchen@ICSI.Berkeley.EDU
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: mip6@ietf.org, Brian Haley <Brian.Haley@hp.com>,
	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>
Errors-To: mip6-bounces@ietf.org

Hello,

On 2006/08/12, at 13:21, Zhen Chen wrote:

> thanks your comments.
> In my understanding, message send from CN--->>>MN
> in Section 6.4
> home address inserted into T2 routing header, while
> Care-of Address inserted into Destination address of Packet

Section 6.4 talks about the on-the-wire format of sent packets from  
CN to MN.

> while in Section 9.3.2 still the case CN--->>>MN
> Home Address is inserted into Destination address of packet, while
> Care-of Address inserted into T2 Routing header of Packet

This section discusses how to construct a packet that has a Type-2  
Routing Header on CN.


> Could you help me to check it again? thanks!

Does this solve your question?

---
Keiichi SHIMA
IIJ Research Laboratory <keiichi@iijlab.net>
WIDE Project <shima@wide.ad.jp>



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



From mip6-bounces@ietf.org Mon Aug 14 07:13:27 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GCaNg-0002ZB-V6; Mon, 14 Aug 2006 07:13:16 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GCaMJ-00029B-Te
	for mip6@ietf.org; Mon, 14 Aug 2006 07:11:51 -0400
Received: from mailout2.samsung.com ([203.254.224.25])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GCaLB-0001iD-Gg
	for mip6@ietf.org; Mon, 14 Aug 2006 07:10:42 -0400
Received: from ep_mmp2 (mailout2.samsung.com [203.254.224.25])
	by mailout2.samsung.com
	(iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004))
	with ESMTP id <0J3Z007ASJ1RNU@mailout2.samsung.com> for mip6@ietf.org;
	Mon, 14 Aug 2006 20:10:39 +0900 (KST)
Received: from wable ([107.108.72.147])
	by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0J3Z0004TJ1PNR@mmp2.samsung.com> for
	mip6@ietf.org; Mon, 14 Aug 2006 20:10:39 +0900 (KST)
Date: Mon, 14 Aug 2006 16:42:23 +0530
From: Ranjitsinh Wable <wable@samsung.com>
Subject: Re: [Mip6] A bug in RFC3775.
To: zhenchen@ICSI.Berkeley.EDU
Message-id: <0b7b01c6bf92$8548f7c0$93486c6b@sisodomain.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
X-Mailer: Microsoft Outlook Express 6.00.2900.2869
Content-type: text/plain; reply-type=original; charset=iso-8859-1;
	format=flowed
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
References: <1155336548.19749.316.camel@shrimp> <44DD4D24.8010101@hp.com>
	<1155356515.19749.338.camel@shrimp>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 14582b0692e7f70ce7111d04db3781c8
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi Zhen Chen,

I think you missed the next part in the RFC.

====>

    The IP layer will insert the routing header before performing any
   necessary IPsec processing.  Once all IPsec processing has been
   performed, the node swaps the IPv6 destination field with the Home
   Address field in the routing header, sets the Segments Left field to
   one, and sends the packet.  This ensures the AH calculation is done
   on the packet in the form it will have on the receiver after
   advancing the routing header.

As Brian said,

>> Maybe this is the crux of the confusion?  For security calculations the
>> IPv6 source address is always the home address.

I think now it may be clear to you.

Regards,

Wable





----- Original Message ----- 
From: "Zhen Chen" <zhenchen@ICSI.Berkeley.EDU>
To: "Brian Haley" <Brian.Haley@hp.com>
Cc: <mip6@ietf.org>
Sent: Saturday, August 12, 2006 9:51 AM
Subject: Re: [Mip6] A bug in RFC3775.


> thanks your comments.
> In my understanding, message send from CN--->>>MN
> in Section 6.4
> home address inserted into T2 routing header, while
> Care-of Address inserted into Destination address of Packet
>
> while in Section 9.3.2 still the case CN--->>>MN
> Home Address is inserted into Destination address of packet, while
> Care-of Address inserted into T2 Routing header of Packet
>
> Could you help me to check it again? thanks!
>
> Best,
>
> Zhen
>
> On Fri, 2006-08-11 at 20:38, Brian Haley wrote:
>> Zhen Chen wrote:
>> > Hi everyone,
>> >   I am working in mobile IPv6. I find a bug in RFC3775. It is
>> > self-contradiction. :)
>> >   I infer that The section 6.4 is correct and the 9.3.2 is wrong.  and
>> > the section 10.4.2 is also wrong, because it uses section 9.3.2.
>>
>> So I'll assume your saying the text on how to build a Type 2 routing
>> header is inconsistent?  It looks correct to me, and we've had many
>> inter-operable implementations tested against each other successfully
>> (including mine :).  Maybe you can describe in a paragraph what you
>> think the problem is, maybe I'm missing something?  Your snippets of
>> text are confusing since you're leaving out intermediate paragraphs that
>> are pretty useful, like:
>>
>>     When calculating authentication data in a packet that contains a type
>>     2 routing header, the correspondent node MUST calculate the AH
>>     authentication data as if the following were true: The routing header
>>     contains the care-of address, the destination IPv6 address field of
>>     the IPv6 header contains the home address, and the Segments Left
>>     field is zero.  The IPsec Security Policy Database lookup MUST based
>>     on the mobile node's home address.
>>
>> Maybe this is the crux of the confusion?  For security calculations the
>> IPv6 source address is always the home address.
>>
>> -Brian
>>
>> _______________________________________________
>> Mip6 mailing list
>> Mip6@ietf.org
>> https://www1.ietf.org/mailman/listinfo/mip6
>>
>
>
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
>
> 


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



From mip6-bounces@ietf.org Mon Aug 14 08:56:18 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GCbzK-0004KV-4a; Mon, 14 Aug 2006 08:56:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GCbzJ-0004KE-5i; Mon, 14 Aug 2006 08:56:13 -0400
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GCbzG-0007Vs-MY; Mon, 14 Aug 2006 08:56:13 -0400
Received: from p130.piuha.net (localhost [127.0.0.1])
	by p130.piuha.net (Postfix) with ESMTP id 2927589884;
	Mon, 14 Aug 2006 15:56:09 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id E2E2E8984E;
	Mon, 14 Aug 2006 15:56:08 +0300 (EEST)
Message-ID: <44E072D9.5040307@piuha.net>
Date: Mon, 14 Aug 2006 15:55:53 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Mozilla Thunderbird 1.0.8 (X11/20060725)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Mipshop <mipshop@ietf.org>, Mobile IPv6 Mailing List <mip6@ietf.org>
References: <E1GBYY7-0001q9-DY@stiedprstage1.ietf.org>
In-Reply-To: <E1GBYY7-0001q9-DY@stiedprstage1.ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: netlmm@ietf.org
Subject: [Mip6] FW: Last Call: 'Goals for Network-based Localized Mobility
 Management
 (NETLMM)' to Informational RFC (draft-ietf-netlmm-nohost-req)
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi all,

NETLMM WG has produced a document that outlines the
goals for a local mobility management solution. It also
analyzes the fullfillment of those goals wrt existing global
mobility management protocols (Mobile IPv6) and local
mobility management solutions (e.g., HMIPv6).

It would be valuable to get additional review from the
MIPSHOP and MIP6 WGs regarding the latter part.
The gap analysis in Section 8 of the document.

The best place for follow-ups is probably the NETLMM list,
though as always you can also send last call comments to
the IETF main list or the IESG directly.

>The IESG has received a request from the Network-based Localized Mobility 
>Management WG to consider the following document:
>
>- 'Goals for Network-based Localized Mobility Management (NETLMM) '
>   <draft-ietf-netlmm-nohost-req-04.txt> as an Informational RFC
>
>The IESG plans to make a decision in the next few weeks, and solicits
>final comments on this action.  Please send any comments to the
>iesg@ietf.org or ietf@ietf.org mailing lists by 2006-08-25.
>
>The file can be obtained via
>http://www.ietf.org/internet-drafts/draft-ietf-netlmm-nohost-req-04.txt
>  
>


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



From mip6-bounces@ietf.org Wed Aug 16 11:50:09 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GDNdh-0007Cn-Fz; Wed, 16 Aug 2006 11:49:05 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GDNdg-0007Bv-8L
	for mip6@ietf.org; Wed, 16 Aug 2006 11:49:04 -0400
Received: from maild.telecomitalia.it ([156.54.233.30])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GDNda-000842-80
	for mip6@ietf.org; Wed, 16 Aug 2006 11:49:04 -0400
Received: from ptpxch010ba020.idc.cww.telecomitalia.it ([156.54.240.53]) by
	maild.telecomitalia.it with Microsoft SMTPSVC(6.0.3790.1830);
	Wed, 16 Aug 2006 17:48:55 +0200
Received: from PTPEVS108BA020.idc.cww.telecomitalia.it ([156.54.241.228]) by
	ptpxch010ba020.idc.cww.telecomitalia.it with Microsoft
	SMTPSVC(6.0.3790.1830); Wed, 16 Aug 2006 17:48:54 +0200
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2757
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Importance: normal
Priority: normal
Subject: RE: [Mip6] comments on AAA-HA-goals-02 or bootstrapping PS??
Date: Wed, 16 Aug 2006 17:46:05 +0200
Message-ID: <F5F8BEB3F2C54240999C08F4D455D28801205C15@PTPEVS108BA020.idc.cww.telecomitalia.it>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] comments on AAA-HA-goals-02 or bootstrapping PS??
thread-index: Aca4hOKHFZd/of5cQcWoBTmcITQQ9AIwXZEQ
From: "Giaretta Gerardo" <gerardo.giaretta@telecomitalia.it>
To: "Julien Bournelle" <julien.bournelle@int-evry.fr>,
	"Madjid Nakhjiri" <mnakhjiri@huawei.com>
X-OriginalArrivalTime: 16 Aug 2006 15:48:54.0690 (UTC)
	FILETIME=[7A66C020:01C6C14B]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2ce306e4307a2c0b518ae453b13efdd0
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

The error is in the PS document. It is in RFC editor queue. I'll correct
that in AUTH48.

--Gerardo=20

> -----Original Message-----
> From: Julien Bournelle [mailto:julien.bournelle@int-evry.fr]=20
> Sent: sabato 5 agosto 2006 13.47
> To: Madjid Nakhjiri
> Cc: 'Julien Bournelle'; mip6@ietf.org
> Subject: Re: [Mip6] comments on AAA-HA-goals-02 or bootstrapping PS??
>=20
> Hi madjid,
>=20
> On Fri, Aug 04, 2006 at 04:46:04PM -0700, Madjid Nakhjiri wrote:
> > Hi Julien,
> >=20
> > There is some inconsistency in the AAA-HA-goals draft that could be
> > clarified if the concepts of home versus serving=20
> providers/authorizers
> > defined in the terminology section of the bootstrapping PS=20
> have been used
> > more persistently. Again, I am happy to provide the=20
> editorial changes once
> > we settle this:)
> >=20
> > Looking at the bootstrapping paper a few things are clear:
> >=20
> > 1) ASPs do not deal with provisioning of mobility service,=20
> MSPs do. This
> > means an HA would be assigned by the MSP not by an ASP.
>=20
>  I agree with that.
>=20
> >=20
> > 2) There is a concept of home versus serving provider=20
> versus authorizer.
> > This means a local HA in a serving/ foreign/ visited (pick=20
> one) would be
> > assigned by the "serving MSP" not by an ASP.
>=20
>  I also agree with that.
>=20
> >=20
> > There is one error in my opinion in the bootstrapping ps=20
> section 5.1.2
> > (dynamic HA assignment):
> >=20
> > "Local home agents
> >=20
> >       The mobile node's MSP may want to allow the serving=20
> ASP to assign
> >       a local home agent for the mobile node."
> >=20
> > It should say "...to allow serving MSP" not "ASP", since=20
> ASP is not in
> > charge of providing mobility service and that is where probably the
> > inconsistency starts??
> >=20
> > What do you think?
>=20
>  I agree on this point.=20
> =20
>  We'll incorporate this in the next revision (-03).=20
>=20
>  Thanks,
>=20
>  Julien
>=20
> >=20
> > R,
> >=20
> > Madjid
> >=20
> >=20
> >=20
> >=20
> >=20
> > -----Original Message-----
> > From: Julien Bournelle [mailto:julien.bournelle@int-evry.fr]=20
> > Sent: Friday, August 04, 2006 9:25 AM
> > To: Madjid Nakhjiri
> > Cc: 'Julien Bournelle'; mip6@ietf.org
> > Subject: Re: [Mip6] comments on AAA-HA-goals-02
> >=20
> > Hi madjid,
> >=20
> >  I think that this discussion is more about our understanding of the
> >  bootstrapping-ps terminology. Maybe we should start a new=20
> thread about
> >  this.
> >=20
> >  Julien
> >=20
> >=20
> > On Thu, Aug 03, 2006 at 04:37:44PM -0700, Madjid Nakhjiri wrote:
> > > Hi Julien,=20
> > >=20
> > > Thanks for the quick reply.=20
> > >=20
> > >=20
> > > -----Original Message-----
> > > From: Julien Bournelle [mailto:julien.bournelle@int-evry.fr]=20
> > > Sent: Thursday, August 03, 2006 7:22 AM
> > > To: Madjid Nakhjiri
> > > Cc: mip6@ietf.org
> > > Subject: Re: [Mip6] comments on AAA-HA-goals-02
> > >=20
> > > Hi madjid,
> > >=20
> > >  let me try to respond to your mail though some=20
> terminology issues are
> > more
> > > related to the
> > >  draft-ietf-mip6-bootstrapping-ps draft.
> > >=20
> > > Madjid>>I actually find the terminology in the=20
> bootstrapping draft more
> > > consistent.=20
> > >=20
> > > > The network MSA to me symbolizes
> > > > the MSP-AAA server, while ASA symbolizes ASP-AAA server.=20
> > >=20
> > >  no, the MSA is administrative entity with whom the user=20
> has a contract
> > >  and thus credentials. The MSP effectively provides the=20
> MIP6 service to
> > >  the user. Thus the MSP may have to contact the MSA=20
> before providing the
> > >  service.=20
> > >=20
> > > Madjid>>Well, you are saying MSA has a contract with the=20
> user and has her
> > > credentials. To me it translates to a home AAA server or=20
> authentication
> > > server for the MSP. I think we need to make the=20
> distinction between home
> > MSA
> > > and visited MSA.
> > > Also, MSP is a service provider, but you are implying it=20
> does not have a
> > AAA
> > > server? At the bottom of your email you said MSP has a=20
> AAA server. I am
> > > confused now.
> > > The ASP is defined in the bootstrapping draft as an=20
> _operator_, but it is
> > > not clear whether MSP is an operator or just an entity=20
> like an HA. What is
> > > the real life correspondence of the MSP??
> > > I like to think MSP include both a HA and a AAA server (MSA).
> > >=20
> > > >=20
> > > > *        I see a hot spot provider or a 802.16d network=20
> without mobility
> > > > support as an ASP, while a IP enabled cellular or a=20
> WiMAX network as a
> > > > combination of ASP and MSP. To me assignment of HA=20
> falls into the MSP
> > > > service category, not ASP service category (I just=20
> confirmed this in
> > > > bootstrapping-ps section 7.1), so there are some=20
> statements in the draft
> > > as
> > > > far as an  ASP assigning an HA and I don't think those=20
> are appropriate
> > > based
> > > > on the terminology provided.=20
> > >=20
> > >  it depends if we are in the split or integrated scenario.
> > >  In the split scenario, we don't have ASP/ASA, only=20
> MSP/MSA. So the user
> > >  has an HA from the MSP.
> > >=20
> > > Madjid>> Well, you do have ASP/ASA, it just that it is=20
> beyond MSP control.
> > >=20
> > >  In the integrated scenario, if MSP=3DASP, the user obtains=20
> an HA from the
> > >  MSP/ASP.=20
> > >=20
> > >=20
> > > >=20
> > > > *        Then there is the concept of home versus=20
> visited domain. I am
> > > > guessing "domain" to administrative domain (AAA=20
> domain). Traditionally
> > AAA
> > > > community is denoted as home and visited AAA servers,=20
> i.e. AAAH and
> > AAAV,
> > > > respectively. I just checked the bootstrapping-ps draft=20
> and that draft
> > > calls
> > > > uses the term "serving" instead of "visited", but still=20
> provides a
> > > > distinction between home versus serving MSP (MSPH and=20
> MSPS) and between
> > > home
> > > > versus serving ASP (ASPH and ASPS). Having said this, I=20
> think if the
> > group
> > > > is going to great length to separate ASP/ MSP and=20
> ASA/MSA, it also needs
> > > to
> > > > distinguish between the home versus visited domain for=20
> each of the
> > > > authorizers. So that MSAH refers to AAA server within=20
> home MSP (MSP-H)
> > and
> > > > MSAV or MSAS (pick one) to AAA server within visited or=20
> serving MSP
> > (MSP-V
> > > > or MSP-S). The same goes for ASAH and ASAV. This means=20
> Serving MSA is
> > not
> > > > the same as serving ASA. It is not proper to equate the=20
> access service
> > > > provider (ASP) with MSP-V the visited domain as it is=20
> implied in section
> > > > 4.2: "Mobile Node requests a home agent to the Access=20
> Service Provider
> > > > (ASP)". According to my understanding of the=20
> terminology of ASP, ASP has
> > > > nothing to anything to do with HA assignment. I think=20
> this can be easily
> > > > remedied by introducing MSAH and MSAS. Visited domain=20
> HA allocation can
> > be
> > > > formulated as "MN can request MSAH for an HA assignment=20
> within MSPS
> > after
> > > > authentication to MSAH and authorization of mobility=20
> service by the
> > > > MSAH/MSAS to MN".
> > >=20
> > >  maybe my explanation below will answer to this paragraph ?
> > >=20
> > > Madjid>>Well one point is ASP is an access provider, not=20
> a mobility
> > > provider, so ASP cannot grant an HA request nor can it=20
> assign one. So that
> > > sentence needs to be revised. The other issue is the lack=20
> of distinction
> > > between home and visited providers, ASP does not mean visited MSP!
> > >=20
> > > > *        The same goes for another sentence in the same=20
> section saying
> > "..
> > > > Mobile Node can specify if it wants a home agent=20
> provided by the visited
> > > > domain (ASP) or by the home domain (ASA)", which seems=20
> to be mixing
> > > > (mobility and access service), (home and visited), (provider and
> > > authorizer)
> > > > all in the same sentence!!
> > >=20
> > >  yes, that can be confusing.=20
> > >=20
> > > Madjid>>Well, if we stick to the terminology in the=20
> bootstrapping draft
> > and
> > > use "serving" and "visited" and clarify whether MSP is an=20
> operator or just
> > > an HA, things should fall into a place better. If you=20
> agree with my
> > > statements, I could help out with that.
> > >=20
> > > >=20
> > > > *        The other comment along the same line is about=20
> section 4.1,
> > where
> > > > it is stated a pool of HA s can rely on the home EAP=20
> server (I am
> > guessing
> > > > EAP server belonging to MSA-H, since this is split scenario) for
> > > > authentication. Here it is stated "It allows the=20
> roaming mobility case
> > in
> > > > which the MN obtains the mobility service in a=20
> different administrative
> > > > domain (MSP !=3DMSA). Here it seems that it is implied HA=20
> is part of MSP
> > > > function (appropriately), however, I am not sure if MSP=20
> and MSA can
> > imply
> > > > two administrative domains, to me administrative domain=20
> implies AAA
> > > domain,
> > > > so one would be MSA-H and another MSA-V, so an HA could=20
> be authorized
> > > within
> > > > MSA-V based on authentication to MSA-H and=20
> authorization by MSA-H.
> > >=20
> > >  MSP has its own AAA server. MSA is the AAA server of the MN.=20
> > >  Does it respond to your comment ?
> > >=20
> > > Madjid>>the definition of MSA is "an authorizer that=20
> authorizes MIP6
> > > service". To me that is the AAA server of the MSP: a AAA=20
> server that
> > > authorizes MIP6 service within an MSP. Then you have the=20
> concept of home
> > > versus serving MSP or ASP and home versus serving MSA and ASA.
> > > The home-MSA can authorize MIP6 service within home MSP=20
> and has MN's
> > > credentials. The "MSA" alone is just like a "AAA server"=20
> alone, it does
> > not
> > > say home or visited AAA server.
> > >=20
> > > >=20
> > > > *        I also have an issue with the usage of term=20
> NAS in next to last
> > > > paragraph of section 3. NAS is really an access service=20
> agent (as the
> > name
> > > > implies) not a mobility service agent. NAS performs=20
> many functions
> > beyond
> > > > the AAA client function, which brings up two issues. 1)=20
> the sentence
> > ".HA,
> > > > that can be seen as Network Access Server for MIP6", is=20
> only providing
> > > > confusion in this context, you may say that HA can be=20
> seen as Network
> > > > mobility server if you want but in a draft that has ASP and MSP
> > > everywhere.
> > >=20
> > >  ok.
> > >=20
> > > > 2) in the goals sections (5.1/ 5.2) , it is not=20
> mentioned anywhere that
> > > the
> > > > HA MUST act as a AAA client, is this a non-requirement, or is it
> > > implicitly
> > > > understood?  Especially G2.2 seems to imply this.
> > >=20
> > >  I think it is implicitly understood. Do you think we should add a
> > >  statement on this ?
> > >=20
> > > Madjid>>I think this is the first requirement for the HA=20
> within an HA-AAA
> > > goals draft. It tells the world what code to expect to have in the
> > compliant
> > > HA. Having it implicit is not a good thing.
> > >=20
> > > >=20
> > > > *        In 5.4 why is it a "MUST" for HA to be an EAP=20
> pass-through
> > > > authenticator? As long as HA receives its information=20
> from the AAA
> > server
> > > in
> > > > a secure fashion and both HA and AAA can identify the=20
> MN and its EAP
> > > session
> > > > uniquely, there is no reason for allocating HA and EAP=20
> pass-through EAP
> > > > authenticator in the same box.
> > >=20
> > >  hmmm, the HA acts as a AAA client and MN uses IKEv2 with=20
> EAP to be
> > >  authenticated. So the HA MUST act as an EAP pass-through=20
> authenticator.
> > >=20
> > >  Am I missing something ? do you think we should rephrase this ?
> > >=20
> > > Madjid>> I don't think this is hard requirement. You may=20
> another AAA
> > client
> > > on the path EAP signaling with EAP server. Aren't you=20
> separating ASA and
> > > MSA?? HA is AAA client for MSP authorization but not=20
> necessarily the AAA
> > > client for every EAP authentication, may be I am missing=20
> something.
> > > The way to rephrase it is
> > >=20
> > > "HA Should be able to act as EAP pass-through=20
> authenticator in the EAP
> > > process for IKEv2." Or something like that. I have to=20
> look at the split
> > > scenario doc explaining this.
> > >=20
> > > >=20
> > > > *        For section 4.2, Integrated scenario, I see=20
> that NAS gets MIP6
> > > conf
> > > > parameters from the AAAH, how does the HA receives the=20
> information it
> > > needs?
> > >=20
> > >  In the integrated scenario based on DHCPv6, the MN gets=20
> HA info through
> > >  DHCP. Then we fall in the split scenario and the MN uses=20
> IKEv2 with the
> > >  HA.=20
> > >=20
> > > Madjid>> Let me do some more reading:)
> > >=20
> > > Thanks,
> > >=20
> > > Madjid
> > >=20
> > >  Julien Bournelle
> > >=20
> > >=20
> > >=20
> > >=20
> >=20
> > --=20
> > julien.bournelle at int-evry.fr
> >=20
> >=20
>=20
> --=20
> julien.bournelle at int-evry.fr
>=20
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
>=20
--------------------------------------------------------------------

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 contact us by replying to =
webmaster@telecomitalia.it.

        Thank you

                                        www.telecomitalia.it

--------------------------------------------------------------------
                       =20

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



From mip6-bounces@ietf.org Wed Aug 16 11:50:31 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GDNf5-0007fo-7X; Wed, 16 Aug 2006 11:50:31 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GDNf3-0007f3-MV
	for mip6@ietf.org; Wed, 16 Aug 2006 11:50:29 -0400
Received: from maild.telecomitalia.it ([156.54.233.30])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GDNez-0000Qf-TO
	for mip6@ietf.org; Wed, 16 Aug 2006 11:50:29 -0400
Received: from ptpxch008ba020.idc.cww.telecomitalia.it ([156.54.240.51]) by
	maild.telecomitalia.it with Microsoft SMTPSVC(6.0.3790.1830);
	Wed, 16 Aug 2006 17:50:25 +0200
Received: from PTPEVS108BA020.idc.cww.telecomitalia.it ([156.54.241.228]) by
	ptpxch008ba020.idc.cww.telecomitalia.it with Microsoft
	SMTPSVC(6.0.3790.1830); Wed, 16 Aug 2006 17:50:24 +0200
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2757
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Importance: normal
Priority: normal
Subject: RE: [Mip6] Consensus call: DHCPv6 options for bootstrapping
Date: Wed, 16 Aug 2006 17:46:14 +0200
Message-ID: <F5F8BEB3F2C54240999C08F4D455D28801205C19@PTPEVS108BA020.idc.cww.telecomitalia.it>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] Consensus call: DHCPv6 options for bootstrapping
thread-index: Aca6ZCEDX9NMYiZXEduYJQARJNUNiAG5Gh/Q
From: "Giaretta Gerardo" <gerardo.giaretta@telecomitalia.it>
To: "Basavaraj Patil" <basavaraj.patil@nokia.com>,
	<mip6@ietf.org>
X-OriginalArrivalTime: 16 Aug 2006 15:50:24.0892 (UTC)
	FILETIME=[B02A7BC0:01C6C14B]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: df9edf1223802dd4cf213867a3af6121
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>
Content-Type: multipart/mixed; boundary="===============1241415214=="
Errors-To: mip6-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1241415214==
Content-Transfer-Encoding: 7bit
Content-Class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C6C14B.AFADE35F"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C6C14B.AFADE35F
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I'm in favor of option 1. If option 2 is chosen, I'm wondering if we =
really need the integrated scenario document (since it is named =
"DHCP-based" and does not add too much to the split document).

--Gerardo

> -----Original Message-----
> From: Basavaraj Patil [mailto:basavaraj.patil@nokia.com =
<mailto:basavaraj.patil@nokia.com> ]
> Sent: luned=EC 7 agosto 2006 22.58
> To: mip6@ietf.org
> Subject: [Mip6] Consensus call: DHCPv6 options for bootstrapping
>
>
> Hello,
>
> We have been debating the issue of how to specify the DHCP options
> needed for bootstrapping for a while now and have not been able to
> reach any conclusions. This issue was discussed at the WG meeting at
> IETF66 and has been debated on the mailing list as well.
>
>
> I-Ds of interest here:
> a. MIP6-bootstrapping via DHCPv6 for the Integrated Scenario
>    draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt
>
> b. DHCP Option for Home Information Discovery in MIPv6
>    draft-jang-mip6-hiopt-00.txt
>
> Issue: MIP6 bootstrapping can be done using DHCPv6. The WG document
> (draft-ietf-mip6-bootstrapping-integrated-dhc-01) describes the use of
> DHCP in the integrated scenario. In order to use DHCP for
> bootstrapping several DHCP options need to be specified. The WG I-D in
> section 3.5 has specified a couple of DHCPv6 options. I-D
> draft-jang-mip6-hiopt-00 specifies several other DHCP options which
> are essential for bootstrapping.
>
> The issue is if the DHCP options need to be specified
>     (i) as part of the solution I-D describing bootstraping using DHCP
>     or
>     (ii) in a separate document which would then be referenced by the
>     bootstrapping with DHCP solution doc.
>
> We are seeking WG consensus in order to resolve the issue. Please
> express your opinion w.r.t the approaches mentioned below:
>
> Options:
>
> 1. Have a single document which specifies the solution describing
>    bootstrapping with DHCPv6 which includes the DHCPv6 options that
>    are needed.
>
> 2. Specify the DHCP options needed for bootstrapping with DHCPv6 in a
>    separate document and have this referenced in the solution I-D.
>
>
> Please submit your preference to the list by Aug 14th, 06.
>
> -Raj
>
>
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6 =
<https://www1.ietf.org/mailman/listinfo/mip6>=20
>=20

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

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 contact us by replying to =
webmaster@telecomitalia.it.

        Thank you

                                        www.telecomitalia.it

--------------------------------------------------------------------
                       =20

------_=_NextPart_001_01C6C14B.AFADE35F
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><TITLE></TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.2802" name=3DGENERATOR></HEAD>
<BODY><!-- Converted from text/plain format -->
<P><FONT size=3D2><FONT face=3D"Courier New">I'm in favor of option 1. =
If option 2=20
is&nbsp;chosen, I'm wondering if we really need the integrated scenario =
document=20
(since it is named "DHCP-based" and does not add too much to the split=20
document).</FONT></FONT></P>
<P><FONT size=3D2><FONT face=3D"Courier New">--Gerardo<BR><BR>&gt; =
-----Original=20
Message-----<BR>&gt; From: Basavaraj Patil [</FONT><A=20
href=3D"mailto:basavaraj.patil@nokia.com"><FONT=20
face=3D"Courier New">mailto:basavaraj.patil@nokia.com</FONT></A><FONT=20
face=3D"Courier New">]<BR>&gt; Sent: luned=EC 7 agosto 2006 =
22.58<BR>&gt; To:=20
mip6@ietf.org<BR>&gt; Subject: [Mip6] Consensus call: DHCPv6 options for =

bootstrapping<BR>&gt;<BR>&gt;<BR>&gt; Hello,<BR>&gt;<BR>&gt; We have =
been=20
debating the issue of how to specify the DHCP options<BR>&gt; needed for =

bootstrapping for a while now and have not been able to<BR>&gt; reach =
any=20
conclusions. This issue was discussed at the WG meeting at<BR>&gt; =
IETF66 and=20
has been debated on the mailing list as well.<BR>&gt;<BR>&gt;<BR>&gt; =
I-Ds of=20
interest here:<BR>&gt; a. MIP6-bootstrapping via DHCPv6 for the =
Integrated=20
Scenario<BR>&gt;&nbsp;&nbsp;&nbsp;=20
draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt<BR>&gt;<BR>&gt; b. =
DHCP=20
Option for Home Information Discovery in MIPv6<BR>&gt;&nbsp;&nbsp;&nbsp; =

draft-jang-mip6-hiopt-00.txt<BR>&gt;<BR>&gt; Issue: MIP6 bootstrapping =
can be=20
done using DHCPv6. The WG document<BR>&gt;=20
(draft-ietf-mip6-bootstrapping-integrated-dhc-01) describes the use =
of<BR>&gt;=20
DHCP in the integrated scenario. In order to use DHCP for<BR>&gt; =
bootstrapping=20
several DHCP options need to be specified. The WG I-D in<BR>&gt; section =
3.5 has=20
specified a couple of DHCPv6 options. I-D<BR>&gt; =
draft-jang-mip6-hiopt-00=20
specifies several other DHCP options which<BR>&gt; are essential for=20
bootstrapping.<BR>&gt;<BR>&gt; The issue is if the DHCP options need to =
be=20
specified<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp; (i) as part of the solution =
I-D=20
describing bootstraping using DHCP<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;=20
or<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp; (ii) in a separate document which =
would then=20
be referenced by the<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp; bootstrapping with =
DHCP=20
solution doc.<BR>&gt;<BR>&gt; We are seeking WG consensus in order to =
resolve=20
the issue. Please<BR>&gt; express your opinion w.r.t the approaches =
mentioned=20
below:<BR>&gt;<BR>&gt; Options:<BR>&gt;<BR>&gt; 1. Have a single =
document which=20
specifies the solution describing<BR>&gt;&nbsp;&nbsp;&nbsp; =
bootstrapping with=20
DHCPv6 which includes the DHCPv6 options that<BR>&gt;&nbsp;&nbsp;&nbsp; =
are=20
needed.<BR>&gt;<BR>&gt; 2. Specify the DHCP options needed for =
bootstrapping=20
with DHCPv6 in a<BR>&gt;&nbsp;&nbsp;&nbsp; separate document and have =
this=20
referenced in the solution I-D.<BR>&gt;<BR>&gt;<BR>&gt; Please submit =
your=20
preference to the list by Aug 14th, 06.<BR>&gt;<BR>&gt;=20
-Raj<BR>&gt;<BR>&gt;<BR>&gt;=20
_______________________________________________<BR>&gt; Mip6 mailing=20
list<BR>&gt; Mip6@ietf.org<BR>&gt; </FONT><A=20
href=3D"https://www1.ietf.org/mailman/listinfo/mip6"><FONT=20
face=3D"Courier =
New">https://www1.ietf.org/mailman/listinfo/mip6</FONT></A><BR><FONT=20
face=3D"Courier New">&gt; </FONT></FONT></P><DIV><FONT size=3D2><FONT=20
face=3D"Courier =
New">--------------------------------------------------------------------=
<BR>CONFIDENTIALITY=20
NOTICE<BR>This message and its attachments are addressed solely to the=20
persons<BR>above and may contain confidential information. If you have=20
received<BR>the message in error, be informed that any use of the =
content=20
hereof<BR>is prohibited. Please return it immediately to the sender and=20
delete<BR>the message. Should you have any questions, please contact us=20
by<BR>replying to </FONT><A =
href=3D"mailto:webmaster@telecomitalia.it"><FONT=20
face=3D"Courier New">webmaster@telecomitalia.it</FONT></A><FONT=20
face=3D"Courier New">.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Thank=20
you<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;=20
</FONT><A href=3D"http://www.telecomitalia.it"><FONT=20
face=3D"Courier New">www.telecomitalia.it</FONT></A><BR><FONT=20
face=3D"Courier =
New">--------------------------------------------------------------------=
</FONT></FONT></DIV>
</BODY></HTML>

------_=_NextPart_001_01C6C14B.AFADE35F--


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

--===============1241415214==--




From mip6-bounces@ietf.org Thu Aug 17 15:35:02 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GDncH-0000UB-So; Thu, 17 Aug 2006 15:33:21 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GDncH-0000U5-2o
	for mip6@ietf.org; Thu, 17 Aug 2006 15:33:21 -0400
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GDncF-0003Jo-Kq
	for mip6@ietf.org; Thu, 17 Aug 2006 15:33:21 -0400
Received: from wei.isi.edu (wei.isi.edu [128.9.160.23])
	by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id k7HJWVY13008
	for <mip6@ietf.org>; Thu, 17 Aug 2006 12:32:31 -0700 (PDT)
From: Wei Ye <weiye@ISI.EDU>
To: mip6@ietf.org
Content-Type: text/plain
Date: Thu, 17 Aug 2006 12:32:25 -0700
Message-Id: <1155843146.4064.29.camel@wei.isi.edu>
Mime-Version: 1.0
X-Mailer: Evolution 2.6.2 (2.6.2-1.fc5.5) 
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: weiye@isi.edu
X-Spam-Score: 0.0 (/)
X-Scan-Signature: df9edf1223802dd4cf213867a3af6121
Subject: [Mip6] Call for Participation: ACM WUWNet'06
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Our Apologies if you have received multiple copies.

Volkan Rodoplu and Wei Ye
WUWNet 2006 Publicity Co-Chairs


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

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

         In conjunction with ACM MobiCom 2006
                 September 25, 2006
            Los Angeles, California, USA

             Sponsored by ACM SIGMOBILE

              Technical Co-Sponsorship:
        IEEE Oceanographic Engineering Society

             Financial Support From:
            Boeing, DARPA, MIT SeaGrant, NSF

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

CALL FOR PARTICIPATION


WUWNet 2006 is the first international workshop on 
underwater networks in the networking and communications 
community. The final program comprises 3 invited talks, 
10 full technical paper presentations, a poster/demo 
session including short papers, work-in-progress posters 
and demos (from both industries and academia), and a 
fascinating panel entitled "Underwater Networks: Methods, 
Systems, and Applications".


Early registration deadline is Sun, Sep. 3rd, 2006. To 
register for the workshop, please visit:

http://www.sigmobile.org/mobicom/2006/registration.html 



TENTATIVE PROGRAM


07:00-08:30 Registration/Breakfast



08:30-08:40 Welcome Address



08:40-09:40 Tutorials
(Session Chair: Milica Stojanovic, MIT/WHOI)

* Acoustic Propagation Considerations for Underwater Acoustic 
Communications Network Development
James Preisig (WHOI)

* Modulation and Demodulation Techniques for Underwater 
Acoustic Communications
John Proakis (UCSD)

* State-of-the-Art in Protocol Research for Underwater 
Sensor Networks 
Ian Akyildiz (Georgia Institute of Technology)



09:40-10:40 Session 1:  Systems 
(Session Chair: Jun-Hong Cui, UCONN)

* A Survey of Practical Issues in Underwater Networks

Jim Partan (UMASS, Amherst), Lee Freitag (WHOI), Jim Kurose 
(UMASS, Amherst)

* Wide Area Ocean Networks: Architecture and System Design 
Considerations

Sumit Roy, Payman Arabshahi, Dan Rouseff, Warren Fox 
(University of Washington)

* Localization in Underwater Sensor Networks -- Survey 
and Challenges

Vijay Chandrasekhar, Winston KG Seah (Institute for Infocomm 
Research, Singapore), Yoo Sang Choo, How Voon Ee (National 
University of Singapore) 



10:40-11:00 Coffee break



11:00-12:00 Session 2:  Analysis and Algorithms 
(Session Chair: Urbashi Mitra, USC)

* On the relationship between capacity and distance in an 
underwater acoustic communication channel

Milica Stojanovic (MIT/WHOI)

* Deployment Analysis in Underwater Acoustic Wireless Sensor 
Networks

Dario Pompili, Tommaso Melodia, Ian F. Akyildiz (Georgia 
Institute of Technology)

* An Optimization Framework for Joint Sensor Deployment, 
Link Scheduling and Routing in Underwater Sensor Networks

Leonardo Badia (IMT Lucca Institute for Advanced Studies, 
Italy), Michele Mastrogiovanni, Chiara Petrioli, Stamatis 
Stefanakos (University of Rome, Italy), Michele Zorzi 
(University of Padova, Italy)



12:00-14:20 Poster/Demo Session (including short papers, 
work-in-progress posters, and demos) and Lunch

Poster Presenations
* Sensor Networks of Freely Drifting Autonomous Underwater 
Explorers

Jules S. Jaffe (Scripps Institution of Oceanography/UCSD), 
Curt Schurgers (UCSD)

* Cooperative Multihop Communication for Underwater 
Acoustic Networks

Cecilia Carbonelli (Qualcomm), Urbashi Mitra (USC)

* Reconfigurable Acoustic Modem for Underwater Sensor Networks 

Ethem M. Sozer, Milica Stojanovic (MIT)

* Why Underwater Acoustic Nodes Should Sleep With One Eye Open: 
Idle-time Power Management In Underwater Sensor Networks

Albert F. Harris III (University of Padova, Italy), Milica 
Stojanovic (MIT, USA), Michele Zorzi (University of Padova, Italy)

* On Applying Network Coding to Underwater Sensor Networks

Zheng Guo, Peng Xie, Jun-Hong Cui, Bing Wang (University of Connecticut)

* A MAC Protocol for Ad-Hoc Underwater Acoustic Sensor Networks 

Borja Peleato, Milica Stojanovic (MIT)


14:20-15:50 Panel Discussion: 
"Underwater Networks: Methods, Systems, and Applications"

Confirmed Panelists:
* Chris Clark (Cornell) 
* Scott Galagher (WHOI) 
* John Heidemann (USC)
* Richard Nielsen (Boeing)
* Jason Redi (BBN)
* Thomas Torgersen (UCONN)



15:50-16:10 Coffee break



16:10-17:30 Session 3:  System Design 
(Session Chair: Kevin Fall, Intel Research)

* Electromagnetic Communications within Swarms of Autonomous 
Underwater Vehicles

Michael R. Frater, Michael J. Ryan, Robin M. Dunbar (The University 
of New South Wales, Australia)

* Design of a Low-cost Acoustic Modem for Moored Oceanographic
Applications

Bridget Benson, Grace Chang, Derek Manov, Brian Graham, Ryan Kastner
(UCSB)

* Low-Power Acoustic Modem for Dense Underwater Sensor Networks

Jack Wills, Wei Ye, John Heidemann (USC/ISI) 

* Status Packet Deprecation and Store-Forward Routing in AUSNet

Matthew Haag, Emmanuel Agu (Worcester Polytechnic Institute), Rick 
Komerska, Steven G. Chappell (Autonomous Undersea Systems Institute), 
Radim Bartos (University of New Hampshire)



17:30-17:40 Wrap-up and end of workshop




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



From mip6-bounces@ietf.org Thu Aug 17 18:10:24 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GDq3V-00038d-2c; Thu, 17 Aug 2006 18:09:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GDq3U-00038Y-BB
	for mip6@ietf.org; Thu, 17 Aug 2006 18:09:36 -0400
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GDq3R-0000aP-UF
	for mip6@ietf.org; Thu, 17 Aug 2006 18:09:36 -0400
Received: from wei.isi.edu (wei.isi.edu [128.9.160.23])
	by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id k7HM91Y07041
	for <mip6@ietf.org>; Thu, 17 Aug 2006 15:09:01 -0700 (PDT)
From: Wei Ye <weiye@ISI.EDU>
To: mip6@ietf.org
Content-Type: text/plain
Date: Thu, 17 Aug 2006 15:08:55 -0700
Message-Id: <1155852536.4064.63.camel@wei.isi.edu>
Mime-Version: 1.0
X-Mailer: Evolution 2.6.2 (2.6.2-1.fc5.5) 
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: weiye@isi.edu
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
Subject: [Mip6] ACM WUWNet'06 call for work-in-progress posters
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Our Apologies if you have received multiple copies.

Volkan Rodoplu and Wei Ye
WUWNet 2006 Publicity Co-Chairs

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

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

         In conjunction with ACM MobiCom 2006
                 September 25, 2006
            Los Angeles, California, USA

             Sponsored by ACM SIGMOBILE

              Technical Co-Sponsorship:
        IEEE Oceanographic Engineering Society

             Financial Support From:
            Boeing, DARPA, MIT SeaGrant, NSF

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

CALL FOR WORK-IN-PROGRESS POSTERS

The work-in-progress poster session will provide a forum for 
researchers to showcase their work and obtain feedback on 
ongoing research from conference attendees. Topics of interest 
include, but are not limited to:

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

POSTER SUBMISSION INSTRUCTIONS

Please submit an extended abstract (no more than 2 pages)
of your poster as a PDF e-mail attachment to

wuwnet06.poster.chairs@gmail.com

with the subject line reading "WUWNet Poster Submission" 
before the deadline. Please be as specific as possible in 
describing what you will show. Accepted abstracts will be 
posted and maintained on the workshop website.

IMPORTANT DATES

Extended abstract due date: 11:59pm (EST), August 27, 2006
Notification of acceptance: August 31, 2006
Web abstract due date: September 8, 2006
Workshop date: September 25, 2006

Work-In-Progress Poster Committee

Jun-Hong Cui, UCONN
We Ye, USC/ISI
Shengli Zhou, UCONN



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



From mip6-bounces@ietf.org Fri Aug 18 18:55:48 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GEDES-0002KR-KE; Fri, 18 Aug 2006 18:54:28 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GEDER-0002K7-Fk
	for mip6@ietf.org; Fri, 18 Aug 2006 18:54:27 -0400
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GEDEQ-000695-4T
	for mip6@ietf.org; Fri, 18 Aug 2006 18:54:27 -0400
Received: from wee.isi.edu (wee.isi.edu [128.9.168.112])
	by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id k7IMs4Y21047
	for <mip6@ietf.org>; Fri, 18 Aug 2006 15:54:04 -0700 (PDT)
From: Wei Ye <weiye@ISI.EDU>
To: mip6@ietf.org
Content-Type: text/plain
Date: Fri, 18 Aug 2006 15:53:59 -0700
Message-Id: <1155941639.13560.31.camel@wee.isi.edu>
Mime-Version: 1.0
X-Mailer: Evolution 2.6.2 (2.6.2-1.fc5.5) 
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: weiye@isi.edu
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Subject: [Mip6] ACM WUWNet'06 call for demos
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Our Apologies if you have received multiple copies.

Volkan Rodoplu and Wei Ye
WUWNet 2006 Publicity Co-Chairs

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

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

         In conjunction with ACM MobiCom 2006
                 September 25, 2006
            Los Angeles, California, USA

             Sponsored by ACM SIGMOBILE

              Technical Co-Sponsorship:
        IEEE Oceanographic Engineering Society

             Financial Support From:
            Boeing, DARPA, MIT SeaGrant, NSF

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


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

Demonstrations of innovative research, applications,
and products are solicited. Demonstrations of technology,
platforms, application and products for all aspects of 
underwater networks are of strong interest. Submission 
from both industry and universities are encouraged.

DEMO SUBMISSION INSTRUCTIONS

Please submit an extended abstract (no more than 2 pages)
of your demo as a PDF e-mail attachment to:

james.w.nash@boeing.com and william.f.whitson@boeing.com

with the subject line reading "WUWNet Demo Submission"
before the deadline. Please be as specific as possible 
in describing what you will demonstrate or exhibit. The 
extended abstract should include a short description of 
space and equipment requirements. Accepted abstracts will 
be posted and maintained on the workshop website.

IMPORTANT DATES

Extended abstract due date: 11:59pm (EST), August 27, 2006
Notification of acceptance: August 31, 2006
Web abstract due date: September 8, 2006
Workshop date: September 25, 2006


WUWNet 2006 Demo Committee

James W Nash, Boeing
Dana M Graham, Boeing
David J Hinkes, Boeing
William F Whitson, Boeing




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



From mip6-bounces@ietf.org Sun Aug 20 15:10:38 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GEsgF-0005TV-Q0; Sun, 20 Aug 2006 15:09:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GEsgE-0005PV-MX
	for mip6@ietf.org; Sun, 20 Aug 2006 15:09:54 -0400
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GEsgB-0004Hf-VP
	for mip6@ietf.org; Sun, 20 Aug 2006 15:09:54 -0400
Received: from p130.piuha.net (localhost [127.0.0.1])
	by p130.piuha.net (Postfix) with ESMTP id F002B89837;
	Sun, 20 Aug 2006 22:09:39 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id 86EFB8980A;
	Sun, 20 Aug 2006 22:09:39 +0300 (EEST)
Message-ID: <44E8B357.9010705@piuha.net>
Date: Sun, 20 Aug 2006 22:09:11 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Mozilla Thunderbird 1.0.8 (X11/20060725)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Vijay Devarapalli <Vijay.Devarapalli@AzaireNet.com>, 
	Mobile IPv6 Mailing List <mip6@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ec7c6dab5a62df223002ae71b5179d41
Cc: 
Subject: [Mip6] AD review of 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>
Errors-To: mip6-bounces@ietf.org


I have finally performed my AD review of this document.
Sorry for taking so long time.

Overall, the document is in relatively good shape. I
do have some issues, however. Addressing these
issues requires a new revision of the spec, and
probably some help from RFC 4301 experts.

Technical:

>    In case the mobile node reverse tunnels all traffic including Mobile
>    IPv6 signaling messages exchanged between the mobile node and the
>    home agent, then the Home Address Option is not required to be
>    present in the messages sent to the home agent.  The packet format
>    for the binding update when sent in the tunnel mode looks as follows.

...

>    o  ESP encapsulation for Binding Updates and Binding Acknowledgements
>       MUST be supported and used.

>    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.

The latter requirements are copied from RFC 3776 but they do not seem
to say anything about the new, alternate, tunnel mode BU encapsulation.
Please specify whether the new encapsulation is a MUST/MAY implement
or not.

There are probably other occurrences of this problem elsewhere
in the document.

>       With dynamic keying, it
>       should be possible for the home agent to verify that the identity
>       presented in the IKE_AUTH exchange is allowed to create security
>       associations for a particular home address.

This is weaker than I would like it to be. This check is not optional.
Say "... the home agent MUST ..." or something to that effect.

>    o  The home agent and mobile node SHOULD support Mobility Header
>       message type as an IPsec selector.
>
>    o  The home agent and mobile node SHOULD support ICMPv6 message type
>       as an IPsec selector.

> 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 this spec it would seem that a MUST requirement for the
finer granularity would be better. This would also reduce
the number of variant configuration styles that implementations
must support, reduce configuration related problems, and
enhance interoperability.

I am quite concerned about interoperability in the mobility
space. We have multiple protocols, they have multiple
ways to set up security, multiple operation modes, different
configuration options, etc. One of the main reasons we
work in organizations like the IETF is that we agree on
a standard way to do things (see also RFC 1958).

I can see situations where we have to have options and
alternate ways. But for that we need a very good reason.
Is there such a reason for this? For instance, do we have
implementors who have stated they have a problem with
the granularity?

Note also that folks who do not support full RFC 4301 granularity
could keep on using RFC 3776.

(Note: I was similarly concerned about the continued support
for manual keying and the introduction of the tunnel mode
packet formats. And the consensus for tunnel mode was decided
based on a tiny number of opinions. But maybe these two
features can be justified by the need to ease the manual
configuration process for some current implementions.)

>    In the examples shown above, the home address of the mobile node
>    might not be available all the time.  For instance, the mobile node
>    might have not configured a home address yet.  When the mobile node
>    acquires a new home address, it must either add the address to the
>    corresponding SPD entries or create the SPD entries for the home
>    address.

Has this procedure been reviewed by IKEv2 experts?

>    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.

Assuming a likely deployment arrangement is authentication
through EAP and AAA, this seems hard to achieve. Overall, the text
in this section follows the RFC 3776 model which may not be all
that great for a dynamic operation.

>    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.

This text fragment has several issues:

1) I am not sure why we are making recommendations about the
    mechanism used.
2) Using the identity to identify a shared secret: if this is the usual
    IKEv2 procedure, then maybe it is not worth repeating here. If
    it is something else, please clarify.
3) Why are we explaining some (but not all) details of the
    public key authentication process in IKEv2? The same
    issue continues further down in the next paragraph.

>    The mobile node should always include its identity in the IDi payload
>    in the IKE_AUTH exchange.  The mobile node could use the following
>    different types of identities to identity itself to the home agent.
>
>    o  Home Address - The mobile node could use its statically configured
>       home address as its identity.  In this case the ID Type field is
>       set to ID_IPV6_ADDR.
>    o  FQDN - The mobile node can use a Fully Qualified Domain Name as
>       the identifier and set the ID Type field to ID_FQDN.
>    o  RFC 822 identifier - If the mobile node uses a RFC 822 identifier
>       [9], it sets the ID Type field to ID_RFC822_ADDR.

It is good that you list the specific identities that devices
conformant to this spec need to employ. However, it
seems that you are missing one case. When EAP is used
within IKEv2, it is possible that the identity provided in the
IDi payload is not the final, true identity. See Sections 3.4
and 3.5 in draft-eronen-ipsec-ikev2-clarifications-09.txt.
I wouldn't bring this up otherwise but I think EAP usage
in this application is likely.

>    If the mobile node or the home agent does
>    not support this capability, then an IKEv2 exchange MUST be initiated
>    to re-establish a new IKE SA.

This seems too strict. If the K bit functionality is not there,
it is still possible that the peers happen to support MOBIKE.
The MUST prevents using it. I would phrase this as "If the
mobile node or the home agent does not support this capability
and has no other means to update the addresses (such as
MOBIKE [ref]), then a new IKEv2 exchange MUST be initiated
to re-establish another IKE SA."

> 9.  Dynamic Home Address Configuration

This section does not say anything about the use of multiple
home addresses for the same mobile node. I believe this
should be allowed. Perhaps you could explicitly mention
that it is allowed.

> 7.1.  Security Policy Database Entries

The style of presentation in this section is taken from
RFC 3776. With the new IPsec architecture, it seems that
it would be more appropriate to state the configuration
in terms of the PAD and the SPD, rather than in SPD only.
I would also like you to go through the examples in both
the dynamic and manual keying sections with an RFC 4301
expert, to ensure that they are generally written in the
way that is in alignment with the current specs.

Editorial:

>    The mobile node should always include its identity in the IDi payload
>    in the IKE_AUTH exchange.

I think this should be "always includes" instead of "should always
include". The payload is mandatory.

>    implementations are required to match the source address in the outer
>    most IP header with the IP address in the IDi field [8].  This

s/outer most/outermost/

> The author would like to thank

authors

--Jari


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



From mip6-bounces@ietf.org Sun Aug 20 23:08:05 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GF07y-00051Z-BG; Sun, 20 Aug 2006 23:07:02 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GF07w-0004zb-Ib
	for mip6@ietf.org; Sun, 20 Aug 2006 23:07:00 -0400
Received: from yskfw1.ysknet.co.jp ([210.169.255.3] helo=ksns.ks.ysknet.co.jp)
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1GF07u-0008Bc-SH
	for mip6@ietf.org; Sun, 20 Aug 2006 23:07:00 -0400
Received: (qmail 3319 invoked from network); 21 Aug 2006 12:06:45 +0900
Received: from  (HELO MIP6-236) (@) by  with SMTP; 21 Aug 2006 12:06:45 +0900
To: mip6@ietf.org
Subject: Re: [Mip6] Question about RFC3776 9.3.1 sentences
From: "K.Kawaguchi" <kawaguti@ysknet.co.jp>
References: <C8E1D942CB394746BE5CFEB7D97610E701D99AE5@bart.corp.azairenet.com>
In-Reply-To: <C8E1D942CB394746BE5CFEB7D97610E701D99AE5@bart.corp.azairenet.com>
Message-Id: <200608211206.AAC69767.VXULBHJB@ysknet.co.jp>
X-Mailer: Winbiff [Version 2.43 PL1]
X-Accept-Language: ja,en
Date: Mon, 21 Aug 2006 12:06:45 +0900
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a8a20a483a84f747e56475e290ee868e
Cc: Vijay.Devarapalli@AzaireNet.com
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org


Thank you for the answer.
I consented to your answer.

> there is no need for a binding error in the first case
> where the packet was dropped because the home address
> was not a unicast routable address.

Certainly, RFC3775 said in other similar parts,
when some address fields are not unicast routable address,
the packet is silently discard.


> I guess the confusion is caused by the phrase "the 
> above  tests". the "above" only refers to the preceding 
> paragraph (paragraph-2 in your email).

Yes. we hesitated in the paragraph that "above" indicated.


Best regards
---
Kiyoaki KAWAGUCHI



"RE: [Mip6] Question about RFC3776 9.3.1 sentences"
""Vijay Devarapalli" <Vijay.Devarapalli@AzaireNet.com>" wrote:

> there is no need for a binding error in the first case
> where the packet was dropped because the home address
> was not a unicast routable address.
> 
> I guess the confusion is caused by the phrase "the 
> above  tests". the "above" only refers to the preceding 
> paragraph (paragraph-2 in your email).
> 
> Vijay
> 
> > -----Original Message-----
> > From: K.Kawaguchi [mailto:kawaguti@ysknet.co.jp] 
> > Sent: Friday, August 11, 2006 5:03 AM
> > To: mip6@ietf.org
> > Subject: [Mip6] Question about RFC3776 9.3.1 sentences
> > 
> > Hi,
> > 
> > Please teach sentences of RFC3775.
> > 
> > Must CN send the Binding Error in situation of paragraph-1 ?
> > (Is paragraph-1 included in "The above tests" of paragraph-3 ?)
> > 
> > 
> > RFC3775
> > ------------------------------
> > 9.3.1.  Receiving Packets with Home Address Option
> > 
> >   <paragraph-1>
> >    Packets containing a Home Address option MUST be dropped 
> > if the given
> >    home address is not a unicast routable address.
> > 
> >   <paragraph-2>
> >    Mobile nodes can include a Home Address destination option in a
> >    packet if they believe the correspondent node has a Binding Cache
> >    entry for the home address of a mobile node.  Packets containing a
> >    Home Address option MUST be dropped if there is no corresponding
> >    Binding Cache entry.  A corresponding Binding Cache entry MUST have
> >    the same home address as appears in the Home Address destination
> >    option, and the currently registered care-of address MUST 
> > be equal to
> >    the source address of the packet.  These tests MUST NOT be done for
> >    packets that contain a Home Address option and a Binding Update.
> > 
> >   <paragraph-3>
> >    If the packet is dropped due the above tests, the 
> > correspondent node
> >                                 ^^^^^^^^^^^^^^^
> >    MUST send the Binding Error message as described in Section 9.3.3.
> >    ^^^^^^^^^^^^^^^^^^^^^^^^^^^
> >    The Status field in this message should be set to 1 
> > (unknown binding
> >    for Home Address destination option).
> > ------------------------------
> > 
> > 
> > # I'm sorry. I can't reply to your answers during short 
> > japanese summer vacation. :-)
> > 
> > 
> > Best regards
> > ---
> > Kiyoaki KAWAGUCHI
> > 
> > 
> > _______________________________________________
> > 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 Aug 21 18:17:14 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GFI4N-0003xY-BO; Mon, 21 Aug 2006 18:16:31 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GFI4L-0003xP-Hi
	for mip6@ietf.org; Mon, 21 Aug 2006 18:16:29 -0400
Received: from mgw-ext11.nokia.com ([131.228.20.170])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GFI4K-0005FE-1z
	for mip6@ietf.org; Mon, 21 Aug 2006 18:16:29 -0400
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143])
	by mgw-ext11.nokia.com (Switch-3.1.10/Switch-3.1.7) with ESMTP id
	k7LLGRfw027088 for <mip6@ietf.org>; Tue, 22 Aug 2006 00:16:28 +0300
Received: from daebh101.NOE.Nokia.com ([10.241.35.111]) by
	esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 22 Aug 2006 01:16:09 +0300
Received: from daebe101.NOE.Nokia.com ([10.241.35.113]) by
	daebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 21 Aug 2006 17:16:07 -0500
Received: from 172.19.244.121 ([172.19.244.121]) by daebe101.NOE.Nokia.com
	([10.241.35.113]) with Microsoft Exchange Server HTTP-DAV ; 
	Mon, 21 Aug 2006 22:16:07 +0000
User-Agent: Microsoft-Entourage/11.2.5.060620
Date: Mon, 21 Aug 2006 17:16:47 -0500
From: Basavaraj Patil <basavaraj.patil@nokia.com>
To: <mip6@ietf.org>
Message-ID: <C10F9AFF.2293D%basavaraj.patil@nokia.com>
Thread-Topic: Conclusion of the consensus call related to the
	bootstrapping I-Ds
Thread-Index: AcbFb33YvCP4MzFiEduFKQARJNUNiA==
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 21 Aug 2006 22:16:07.0927 (UTC)
	FILETIME=[668E2070:01C6C56F]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Subject: [Mip6] Conclusion of the consensus call related to the
	bootstrapping I-Ds
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org



Hello,

The consensus call for determining how to specify the DHCP options has
concluded. The details of the consensus call are at:
http://www1.ietf.org/mail-archive/web/mip6/current/msg05033.html

Conclusion:
WG consensus is to specify the DHCP options in a separate document
(independent of the I-D:
draft-ietf-mip6-bootstrapping-integrated-dhc-01). Hence we will adopt
draft-jang-mip6-hiopt-00.txt as a WG I-D and specify the DHCP options
required for bootstrapping. It is also possible that a couple of the
DHCP options that are currently included in the I-D:
draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt may be included in
the new WG I-D. 


Is the integrated scenario bootstrap document still useful or needed?
I think there have been some opinions that it may not be essential and
hence we will determine if there is a need to continue working on it
or to deprecate it by the end of this month.

-Raj


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



From mip6-bounces@ietf.org Mon Aug 21 23:11:03 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GFMei-0001Ai-QU; Mon, 21 Aug 2006 23:10:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GFMei-0001Ab-2F
	for mip6@ietf.org; Mon, 21 Aug 2006 23:10:20 -0400
Received: from mx0.starentnetworks.com ([12.38.223.203])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GFMec-0003kh-Tm
	for mip6@ietf.org; Mon, 21 Aug 2006 23:10:19 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mx0.starentnetworks.com (Postfix) with ESMTP id 4511490007;
	Mon, 21 Aug 2006 23:10:11 -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 22755-06; Mon, 21 Aug 2006 23:10:10 -0400 (EDT)
Received: from exchtewks1.starentnetworks.com (exchtewks1.starentnetworks.com
	[12.33.233.52]) by mx0.starentnetworks.com (Postfix) with ESMTP;
	Mon, 21 Aug 2006 23:10:10 -0400 (EDT)
X-MessageTextProcessor: DisclaimIt (2.70.271) [Starent Networks Corp.]
Received: from exchtewks2.starentnetworks.com ([12.33.232.12]) by
	exchtewks1.starentnetworks.com with Microsoft
	SMTPSVC(6.0.3790.1830); Mon, 21 Aug 2006 23:10:10 -0400
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] Conclusion of the consensus call related to
	thebootstrapping I-Ds
Date: Mon, 21 Aug 2006 23:10:10 -0400
Message-ID: <7CCD07160348804497EF29E9EA5560D783722A@exchtewks2.starentnetworks.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] Conclusion of the consensus call related to
	thebootstrapping I-Ds
thread-index: AcbFb33YvCP4MzFiEduFKQARJNUNiAAKLoqQ
From: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
To: "Basavaraj Patil" <basavaraj.patil@nokia.com>, <mip6@ietf.org>
Importance: normal
Priority: normal
X-OriginalArrivalTime: 22 Aug 2006 03:10:10.0567 (UTC)
	FILETIME=[7A635970:01C6C598]
X-Virus-Scanned: amavisd-new 2.2.1 (20041222) at mx0.starentnetworks.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Cc: 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org



> -----Original Message-----
> From: Basavaraj Patil [mailto:basavaraj.patil@nokia.com]
> Sent: Monday, August 21, 2006 5:17 PM
> To: mip6@ietf.org
> Subject: [Mip6] Conclusion of the consensus call related to
> thebootstrapping I-Ds
>=20
>=20
>=20
> Hello,
>=20
> The consensus call for determining how to specify the DHCP options has
> concluded. The details of the consensus call are at:
> http://www1.ietf.org/mail-archive/web/mip6/current/msg05033.html
>=20
> Conclusion:
> WG consensus is to specify the DHCP options in a separate document
> (independent of the I-D:
> draft-ietf-mip6-bootstrapping-integrated-dhc-01). Hence we will adopt
> draft-jang-mip6-hiopt-00.txt as a WG I-D and specify the DHCP options
> required for bootstrapping. It is also possible that a couple of the
> DHCP options that are currently included in the I-D:
> draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt may be included in
> the new WG I-D.
>=20
>=20
> Is the integrated scenario bootstrap document still useful or needed?
> I think there have been some opinions that it may not be essential and
> hence we will determine if there is a need to continue working on it
> or to deprecate it by the end of this month.
>=20
[KC>] I don't know how you concluded that! There was just one opinion in
my recollection.=20

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


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

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



From mip6-bounces@ietf.org Mon Aug 21 23:20:43 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GFMoc-0004g0-Ke; Mon, 21 Aug 2006 23:20:34 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GFMoa-0004ft-UW
	for mip6@ietf.org; Mon, 21 Aug 2006 23:20:32 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GFLTz-0004NI-07
	for mip6@ietf.org; Mon, 21 Aug 2006 21:55:11 -0400
Received: from mailout2.samsung.com ([203.254.224.25])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1GFLP7-00012P-7B
	for mip6@ietf.org; Mon, 21 Aug 2006 21:50:12 -0400
Received: from ep_mmp2 (mailout2.samsung.com [203.254.224.25])
	by mailout2.samsung.com
	(iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004))
	with ESMTP id <0J4D002QLMFIWL@mailout2.samsung.com> for mip6@ietf.org;
	Tue, 22 Aug 2006 10:50:06 +0900 (KST)
Received: from LocalHost
	(adsl-75-2-41-177.dsl.ipltin.sbcglobal.net [75.2.41.177])
	by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built
	Jun 23 2003)) with ESMTPA id <0J4D00ER2MFI1V@mmp2.samsung.com> for
	mip6@ietf.org; Tue, 22 Aug 2006 10:50:06 +0900 (KST)
Date: Tue, 22 Aug 2006 10:50:06 +0900
From: Heejin Jang <heejin.jang@samsung.com>
Subject: RE: [Mip6] Conclusion of the consensus call related to the
	bootstrapping I-Ds
In-reply-to: <C10F9AFF.2293D%basavaraj.patil@nokia.com>
To: 'Basavaraj Patil' <basavaraj.patil@nokia.com>, mip6@ietf.org
Message-id: <000501c6c58d$4b1250f0$b129024b@LocalHost>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-index: AcbFb33YvCP4MzFiEduFKQARJNUNiAAGtctg
X-Spam-Score: -2.6 (--)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Cc: 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org


Hi, Raj.
Thanks for arranging consensus call. 

Regarding the direction of bootstrap document, I've understood 
"seperate document" in option (2) in the cc meant that 
"to proceed both of documents" and that's what folks preferring option 2
wanted. 

Technically, draft-jang-mip6-hiopt-00.tx introduces only one of DHCP options

and bootstrap document includes the overal bootstrap procedure by using the
proposed option. 

If bootstrap document is deprecated and integrated to draft-hiopt, 
it does not make difference from option (1).
If bootstrap document is deprecated and not integrated to draft-hiopt,
there is no standard document for integrated-bootstrapping scenarios.

-- Regards, 
Heejin.


-----Original Message-----
From: Basavaraj Patil [mailto:basavaraj.patil@nokia.com] 
Sent: Tuesday, August 22, 2006 7:17 AM
To: mip6@ietf.org
Subject: [Mip6] Conclusion of the consensus call related to the
bootstrapping I-Ds



Hello,

The consensus call for determining how to specify the DHCP options has
concluded. The details of the consensus call are at:
http://www1.ietf.org/mail-archive/web/mip6/current/msg05033.html

Conclusion:
WG consensus is to specify the DHCP options in a separate document
(independent of the I-D:
draft-ietf-mip6-bootstrapping-integrated-dhc-01). Hence we will adopt
draft-jang-mip6-hiopt-00.txt as a WG I-D and specify the DHCP options
required for bootstrapping. It is also possible that a couple of the DHCP
options that are currently included in the I-D:
draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt may be included in the
new WG I-D. 


Is the integrated scenario bootstrap document still useful or needed?
I think there have been some opinions that it may not be essential and hence
we will determine if there is a need to continue working on it or to
deprecate it by the end of this month.

-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 Tue Aug 22 00:02:22 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GFNSP-0001hs-Fu; Tue, 22 Aug 2006 00:01:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GFNSO-0001hj-E3
	for mip6@ietf.org; Tue, 22 Aug 2006 00:01:40 -0400
Received: from mgw-ext14.nokia.com ([131.228.20.173])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GFNSM-0006Ze-VD
	for mip6@ietf.org; Tue, 22 Aug 2006 00:01:40 -0400
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145])
	by mgw-ext14.nokia.com (Switch-3.1.10/Switch-3.1.7) with ESMTP id
	k7M41b6a009016; Tue, 22 Aug 2006 07:01:37 +0300
Received: from daebh101.NOE.Nokia.com ([10.241.35.111]) by
	esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 22 Aug 2006 07:01:33 +0300
Received: from daebe101.NOE.Nokia.com ([10.241.35.113]) by
	daebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 21 Aug 2006 23:01:31 -0500
Received: from 10.241.58.131 ([10.241.58.131]) by daebe101.NOE.Nokia.com
	([10.241.35.113]) with Microsoft Exchange Server HTTP-DAV ; 
	Tue, 22 Aug 2006 04:01:31 +0000
User-Agent: Microsoft-Entourage/11.2.5.060620
Date: Mon, 21 Aug 2006 23:02:11 -0500
Subject: Re: [Mip6] Conclusion of the consensus call related to
	thebootstrapping I-Ds
From: Basavaraj Patil <basavaraj.patil@nokia.com>
To: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>, <mip6@ietf.org>
Message-ID: <C10FEBF3.22998%basavaraj.patil@nokia.com>
Thread-Topic: [Mip6] Conclusion of the consensus call related to
	thebootstrapping I-Ds
Thread-Index: AcbFb33YvCP4MzFiEduFKQARJNUNiAAKLoqQAAHhk4k=
In-Reply-To: <7CCD07160348804497EF29E9EA5560D783722A@exchtewks2.starentnetworks.com>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 22 Aug 2006 04:01:31.0616 (UTC)
	FILETIME=[A6D61E00:01C6C59F]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Cc: 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org


Kuntal,

On 8/21/06 10:10 PM, "ext Chowdhury, Kuntal"
<kchowdhury@starentnetworks.com> wrote:

> 
> 
>> 
>> Is the integrated scenario bootstrap document still useful or needed?
>> I think there have been some opinions that it may not be essential and
>> hence we will determine if there is a need to continue working on it
>> or to deprecate it by the end of this month.
>> 
> [KC>] I don't know how you concluded that! There was just one opinion in
> my recollection. 

The above paragraph was not part of the conclusion of the consensus call but
rather some musing on my part about what to do with the integrated scenarios
I-D. I have no problems in having the WG work on both the documents.

-Raj


> 
>> -Raj
>> 
>> 


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



From mip6-bounces@ietf.org Tue Aug 22 01:24:34 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GFOjt-0003Kn-23; Tue, 22 Aug 2006 01:23:49 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GFOjr-0003JR-P7
	for mip6@ietf.org; Tue, 22 Aug 2006 01:23:47 -0400
Received: from ag.ntt-at.co.jp ([221.186.82.162])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1GFOdC-00024Q-EQ
	for mip6@ietf.org; Tue, 22 Aug 2006 01:16:56 -0400
Received: (qmail 10180 invoked by alias); 22 Aug 2006 14:16:49 +0900
Received: from suez.bb.ntt-at.co.jp (192.168.2.9)
	by atgate.bb.ntt-at.co.jp with SMTP; 22 Aug 2006 05:16:49 -0000
Received: from pacific.bb.ntt-at.co.jp (suez [127.0.0.1])
	by suez.bb.ntt-at.co.jp (8.12.10/8.12.10) with ESMTP id k7M5GlZj010789
	for <mip6@ietf.org>; Tue, 22 Aug 2006 14:16:48 +0900
Received: from karuta.cnh.ntt-at.co.jp (karutagw.cnh.ntt-at.co.jp
	[192.168.24.65])
	by pacific.bb.ntt-at.co.jp (8.13.1/cf/pacific) with ESMTP id
	k7M5GlO5076751
	for <mip6@ietf.org>; Tue, 22 Aug 2006 14:16:48 +0900 (JST)
	(envelope-from takaaki.matsuura@ntt-at.co.jp)
Received: from [192.168.23.230] (center5230.mitaka.ntt-at.co.jp
	[192.168.23.230]) by karuta.cnh.ntt-at.co.jp (Postfix) with ESMTP
	id DA09B6EE87; Tue, 22 Aug 2006 14:16:47 +0900 (JST)
Date: Tue, 22 Aug 2006 14:16:47 +0900
From: =?ISO-2022-JP?B?IlRha2Fha2kgTUFUU1VVUkEvGyRCPj4xOhsoQiA=?=
	=?ISO-2022-JP?B?GyRCOWJMQBsoQiI=?= <takaaki.matsuura@ntt-at.co.jp>
To: mip6@ietf.org
Subject: Re: [Mip6] Question about RFC3776 9.3.1 sentences 
References: <C8E1D942CB394746BE5CFEB7D97610E701D99AE5@bart.corp.azairenet.com>
Message-Id: <20060822141610.E094.TAKAAKI.MATSUURA@ntt-at.co.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-2022-JP"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.24.01 [ja]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi, all

I'm takaaki matsuura from Japan.

> there is no need for a binding error in the first case
> where the packet was dropped because the home address
> was not a unicast routable address.

I consented to your answer, too.

So Now, should I read "CN must NOT send binding error
in the first case" or "two kinds of actions are aceptable
for CN those are sending binding error and dropping packets
silently"?

----
Very truly yours,
Takaakki Matsuura <takaaki.matsuura@ntt-at.co.jp>
NTT Advanced Technology

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



From mip6-bounces@ietf.org Tue Aug 22 05:28:00 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GFSX2-0000cA-0x; Tue, 22 Aug 2006 05:26:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GFSX1-0000bc-9W
	for mip6@ietf.org; Tue, 22 Aug 2006 05:26:47 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GFSX1-0005k5-80
	for mip6@ietf.org; Tue, 22 Aug 2006 05:26:47 -0400
Received: from mail1.azairenet.com ([66.92.223.4] helo=bart.corp.azairenet.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1GFSVm-00021f-9t
	for mip6@ietf.org; Tue, 22 Aug 2006 05:25:32 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] Conclusion of the consensus call related
	tothebootstrapping I-Ds
Date: Tue, 22 Aug 2006 02:25:27 -0700
Message-ID: <C8E1D942CB394746BE5CFEB7D97610E701D9A2AD@bart.corp.azairenet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] Conclusion of the consensus call related
	tothebootstrapping I-Ds
thread-index: AcbFb33YvCP4MzFiEduFKQARJNUNiAAKLoqQAAHhk4kACzqSIA==
From: "Vijay Devarapalli" <Vijay.Devarapalli@AzaireNet.com>
To: "Basavaraj Patil" <basavaraj.patil@nokia.com>,
	"Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>, <mip6@ietf.org>
X-Spam-Score: -2.2 (--)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Cc: 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

deprecating the current WG document was brought up many
times (including during the IETF meeting). didn't realize
people would conveniently forget it.=20

Vijay

> -----Original Message-----
> From: Basavaraj Patil [mailto:basavaraj.patil@nokia.com]=20
> Sent: Monday, August 21, 2006 9:02 PM
> To: Chowdhury, Kuntal; mip6@ietf.org
> Subject: Re: [Mip6] Conclusion of the consensus call related=20
> tothebootstrapping I-Ds
>=20
>=20
> Kuntal,
>=20
> On 8/21/06 10:10 PM, "ext Chowdhury, Kuntal"
> <kchowdhury@starentnetworks.com> wrote:
>=20
> >=20
> >=20
> >>=20
> >> Is the integrated scenario bootstrap document still useful=20
> or needed?
> >> I think there have been some opinions that it may not be=20
> essential and
> >> hence we will determine if there is a need to continue=20
> working on it
> >> or to deprecate it by the end of this month.
> >>=20
> > [KC>] I don't know how you concluded that! There was just=20
> one opinion in
> > my recollection.=20
>=20
> The above paragraph was not part of the conclusion of the=20
> consensus call but
> rather some musing on my part about what to do with the=20
> integrated scenarios
> I-D. I have no problems in having the WG work on both the documents.
>=20
> -Raj
>=20
>=20
> >=20
> >> -Raj
> >>=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 Tue Aug 22 05:37:44 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GFShR-0004OI-9l; Tue, 22 Aug 2006 05:37:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GFShP-0004O8-Tu
	for mip6@ietf.org; Tue, 22 Aug 2006 05:37:31 -0400
Received: from mail1.azairenet.com ([66.92.223.4] helo=bart.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GFShO-0007fr-IS
	for mip6@ietf.org; Tue, 22 Aug 2006 05:37:31 -0400
Received: from [10.1.210.1] ([10.1.210.1]) by bart.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Tue, 22 Aug 2006 02:37:29 -0700
Message-ID: <44EAD04E.7020400@azairenet.com>
Date: Tue, 22 Aug 2006 02:37:18 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.5 (Windows/20060719)
MIME-Version: 1.0
To: Heejin Jang <heejin.jang@samsung.com>
Subject: Re: [Mip6] Conclusion of the consensus call related to
	the	bootstrapping I-Ds
References: <000501c6c58d$4b1250f0$b129024b@LocalHost>
In-Reply-To: <000501c6c58d$4b1250f0$b129024b@LocalHost>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 22 Aug 2006 09:37:29.0525 (UTC)
	FILETIME=[95E2EE50:01C6C5CE]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36
Cc: mip6@ietf.org, 'Basavaraj Patil' <basavaraj.patil@nokia.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Heejin Jang wrote:
> If bootstrap document is deprecated and integrated to draft-hiopt, 
> it does not make difference from option (1).
> If bootstrap document is deprecated and not integrated to draft-hiopt,
> there is no standard document for integrated-bootstrapping scenarios.

lets discuss this further. there is no standard document for
integrated bootstrapping scenarios currently. we have *one*
solution for the integrated scenario using DHCP. perhaps it
is best left that way. initially in the bootstrapping design
team, folks managed to convince me and others in the design
team that DHCP was the way to go for the integrated scenario.
but now it turns out that using DHCP needs many hacks,
especially when the NAS and the DHCP server are separate
boxes (which is true most of the time). I am not any more
convinced that DHCP based bootstrapping should be a proposed
standard (note that this my personal opinion).

what I would like to see is a informational document written
that shows how exactly DHCP is being planned for use for MIP6
bootstrapping in various SDOs and have that reviewed by the
DHC WG.

Vijay

> 
> -- Regards, 
> Heejin.
> 
> 
> -----Original Message-----
> From: Basavaraj Patil [mailto:basavaraj.patil@nokia.com] 
> Sent: Tuesday, August 22, 2006 7:17 AM
> To: mip6@ietf.org
> Subject: [Mip6] Conclusion of the consensus call related to the
> bootstrapping I-Ds
> 
> 
> 
> Hello,
> 
> The consensus call for determining how to specify the DHCP options has
> concluded. The details of the consensus call are at:
> http://www1.ietf.org/mail-archive/web/mip6/current/msg05033.html
> 
> Conclusion:
> WG consensus is to specify the DHCP options in a separate document
> (independent of the I-D:
> draft-ietf-mip6-bootstrapping-integrated-dhc-01). Hence we will adopt
> draft-jang-mip6-hiopt-00.txt as a WG I-D and specify the DHCP options
> required for bootstrapping. It is also possible that a couple of the DHCP
> options that are currently included in the I-D:
> draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt may be included in the
> new WG I-D. 
> 
> 
> Is the integrated scenario bootstrap document still useful or needed?
> I think there have been some opinions that it may not be essential and hence
> we will determine if there is a need to continue working on it or to
> deprecate it by the end of this month.
> 
> -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


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



From mip6-bounces@ietf.org Tue Aug 22 05:38:21 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GFSi8-0004e8-OA; Tue, 22 Aug 2006 05:38:16 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GFSi7-0004e3-AI
	for mip6@ietf.org; Tue, 22 Aug 2006 05:38:15 -0400
Received: from mail1.azairenet.com ([66.92.223.4] helo=bart.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GFSi6-0007ra-10
	for mip6@ietf.org; Tue, 22 Aug 2006 05:38:15 -0400
Received: from [10.1.210.1] ([10.1.210.1]) by bart.corp.azairenet.com with
	Microsoft SMTPSVC(6.0.3790.1830); Tue, 22 Aug 2006 02:38:09 -0700
Message-ID: <44EAD07F.6040504@azairenet.com>
Date: Tue, 22 Aug 2006 02:38:07 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.5 (Windows/20060719)
MIME-Version: 1.0
To: =?ISO-2022-JP?B?VGFrYWFraSBNQVRTVVVSQS8bJEI+PjE6GyhCIBskQjliTEAbKEI=?=
	<takaaki.matsuura@ntt-at.co.jp>
Subject: Re: [Mip6] Question about RFC3776 9.3.1 sentences
References: <C8E1D942CB394746BE5CFEB7D97610E701D99AE5@bart.corp.azairenet.com>
	<20060822141610.E094.TAKAAKI.MATSUURA@ntt-at.co.jp>
In-Reply-To: <20060822141610.E094.TAKAAKI.MATSUURA@ntt-at.co.jp>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 22 Aug 2006 09:38:10.0479 (UTC)
	FILETIME=[AE4C03F0:01C6C5CE]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Takaaki MATSUURA/$B>>1:(B $B9bL@(B wrote:
> Hi, all
> 
> I'm takaaki matsuura from Japan.
> 
>> there is no need for a binding error in the first case
>> where the packet was dropped because the home address
>> was not a unicast routable address.
> 
> I consented to your answer, too.
> 
> So Now, should I read "CN must NOT send binding error
> in the first case" or "two kinds of actions are aceptable
> for CN those are sending binding error and dropping packets
> silently"?

CN MUST NOT send a binding error in the first case.

Vijay

> 
> ----
> Very truly yours,
> Takaakki Matsuura <takaaki.matsuura@ntt-at.co.jp>
> NTT Advanced Technology
> 
> _______________________________________________
> 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 Aug 22 08:01:51 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GFUwE-0004r8-FJ; Tue, 22 Aug 2006 08:00:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GFUwC-0004od-75
	for mip6@ietf.org; Tue, 22 Aug 2006 08:00:56 -0400
Received: from mout.perfora.net ([217.160.230.40])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GFUwA-0003KE-UV
	for mip6@ietf.org; Tue, 22 Aug 2006 08:00:56 -0400
Received: from [85.96.35.242] (helo=IBM52A5038A94F)
	by mrelay.perfora.net (node=mrelayus1) with ESMTP (Nemesis),
	id 0MKp2t-1GFUw32Tqo-0002lv; Tue, 22 Aug 2006 08:00:50 -0400
From: "Alper Yegin" <alper.yegin@yegin.org>
To: "'Basavaraj Patil'" <basavaraj.patil@nokia.com>,
	<mip6@ietf.org>
Subject: RE: [Mip6] Conclusion of the consensus call related to
	thebootstrapping I-Ds
Date: Tue, 22 Aug 2006 15:00:32 +0300
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
In-Reply-To: <C10F9AFF.2293D%basavaraj.patil@nokia.com>
Thread-Index: AcbFb33YvCP4MzFiEduFKQARJNUNiAAchFhA
Message-ID: <0MKp2t-1GFUw32Tqo-0002lv@mrelay.perfora.net>
X-Provags-ID: perfora.net abuse@perfora.net
	login:abf7a4bb310ea4dfc9b6841113e2970f
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org


Hi Raj,

Given that the options were:

1. Have a single document which specifies the solution describing
   bootstrapping with DHCPv6 which includes the DHCPv6 options that
   are needed.

2. Specify the DHCP options needed for bootstrapping with DHCPv6 in a
   separate document and have this referenced in the solution I-D.


And the WG consensus was for option 2, we cannot be still asking:

> Is the integrated scenario bootstrap document still useful or needed?

This question is already answered. That was the whole idea behind this
consensus call (one vs. two documents).

Alper



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



From mip6-bounces@ietf.org Tue Aug 22 12:43:42 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GFZLG-0005UN-JV; Tue, 22 Aug 2006 12:43:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GFZLF-0005UI-J7
	for mip6@ietf.org; Tue, 22 Aug 2006 12:43:05 -0400
Received: from key1.docomolabs-usa.com ([216.98.102.225]
	helo=fridge.docomolabs-usa.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GFZLE-0000Gd-67
	for mip6@ietf.org; Tue, 22 Aug 2006 12:43:05 -0400
Message-ID: <049a01c6c60a$04f00810$636015ac@dcml.docomolabsusa.com>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Alper Yegin" <alper.yegin@yegin.org>,
	"'Basavaraj Patil'" <basavaraj.patil@nokia.com>, <mip6@ietf.org>
References: <0MKp2t-1GFUw32Tqo-0002lv@mrelay.perfora.net>
Subject: Re: [Mip6] Conclusion of the consensus call related
	tothebootstrapping I-Ds
Date: Tue, 22 Aug 2006 09:42:55 -0700
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Cc: 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Alper,

>From an interoperation standpoint, if draft-jang is Proposed Standard, is 
there really any need for the integrated scenerio document to be Proposed 
Standard as well? As I recall, there are a number of assumptions about 
system architecture in the document that may be specific to certain SDO 
architectures. Would it make more sense to expand the document's scope into 
a survey of how DHCP is used for bootstrapping in various SDO architectures 
and make it Informational?

                       jak

----- Original Message ----- 
From: "Alper Yegin" <alper.yegin@yegin.org>
To: "'Basavaraj Patil'" <basavaraj.patil@nokia.com>; <mip6@ietf.org>
Sent: Tuesday, August 22, 2006 5:00 AM
Subject: RE: [Mip6] Conclusion of the consensus call related 
tothebootstrapping I-Ds


>
> Hi Raj,
>
> Given that the options were:
>
> 1. Have a single document which specifies the solution describing
>   bootstrapping with DHCPv6 which includes the DHCPv6 options that
>   are needed.
>
> 2. Specify the DHCP options needed for bootstrapping with DHCPv6 in a
>   separate document and have this referenced in the solution I-D.
>
>
> And the WG consensus was for option 2, we cannot be still asking:
>
>> Is the integrated scenario bootstrap document still useful or needed?
>
> This question is already answered. That was the whole idea behind this
> consensus call (one vs. two documents).
>
> Alper
>
>
>
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
> 



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



From mip6-bounces@ietf.org Tue Aug 22 13:42:01 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GFaFt-0000h1-7l; Tue, 22 Aug 2006 13:41:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GFaFr-0000gr-H8
	for mip6@ietf.org; Tue, 22 Aug 2006 13:41:35 -0400
Received: from mx0.starentnetworks.com ([12.38.223.203])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GFaFp-0001YP-2m
	for mip6@ietf.org; Tue, 22 Aug 2006 13:41:35 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mx0.starentnetworks.com (Postfix) with ESMTP id 5981C9006A;
	Tue, 22 Aug 2006 13:41: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 07111-07; Tue, 22 Aug 2006 13:41:27 -0400 (EDT)
Received: from exchtewks1.starentnetworks.com (exchtewks1.starentnetworks.com
	[12.33.233.52]) by mx0.starentnetworks.com (Postfix) with ESMTP;
	Tue, 22 Aug 2006 13:41:27 -0400 (EDT)
X-MessageTextProcessor: DisclaimIt (2.70.271) [Starent Networks Corp.]
Received: from exchtewks2.starentnetworks.com ([12.33.232.12]) by
	exchtewks1.starentnetworks.com with Microsoft
	SMTPSVC(6.0.3790.1830); Tue, 22 Aug 2006 13:41:27 -0400
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] Conclusion of the consensus call relatedtothebootstrapping
	I-Ds
Date: Tue, 22 Aug 2006 13:41:27 -0400
Message-ID: <7CCD07160348804497EF29E9EA5560D7837242@exchtewks2.starentnetworks.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] Conclusion of the consensus call
	relatedtothebootstrapping I-Ds
thread-index: AcbGDKUk4/eB2o22SoCUKu74vuLjaQABC1RA
From: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
Importance: normal
To: "James Kempf" <kempf@docomolabs-usa.com>,
	"Alper Yegin" <alper.yegin@yegin.org>,
	"Basavaraj Patil" <basavaraj.patil@nokia.com>, <mip6@ietf.org>
Priority: normal
X-OriginalArrivalTime: 22 Aug 2006 17:41:27.0415 (UTC)
	FILETIME=[31D15070:01C6C612]
X-Virus-Scanned: amavisd-new 2.2.1 (20041222) at mx0.starentnetworks.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87
Cc: 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org



> -----Original Message-----
> From: James Kempf [mailto:kempf@docomolabs-usa.com]
> Sent: Tuesday, August 22, 2006 11:43 AM
> To: Alper Yegin; 'Basavaraj Patil'; mip6@ietf.org
> Subject: Re: [Mip6] Conclusion of the consensus call
> relatedtothebootstrapping I-Ds
>=20
> Alper,
>=20
> >From an interoperation standpoint, if draft-jang is Proposed
Standard, is
> there really any need for the integrated scenerio document to be
Proposed
> Standard as well? As I recall, there are a number of assumptions about
> system architecture in the document that may be specific to certain
SDO
> architectures. Would it make more sense to expand the document's scope
> into
> a survey of how DHCP is used for bootstrapping in various SDO
> architectures
> and make it Informational?
>=20
[KC>] The problem statements for mip6 bootstrapping talks about two
scenarios split and integrated. We have two I-Ds for each scenario. Now,
you are questioning the need for a solution document for the integrated
scenario to be standards track document or not. What about split
scenario document? The split scenario document is nothing but a
framework with a handful of (rather useless) things like DNS update and
HL prefix etc. Integrated scenario is likely to be widely deployed,
where as the split scenario doesn't even have any buyer.=20

So, if you want to go down this path, we will end up making both the
documents informational. If not both of them should remain standards
track.

>                        jak
>=20
> ----- Original Message -----
> From: "Alper Yegin" <alper.yegin@yegin.org>
> To: "'Basavaraj Patil'" <basavaraj.patil@nokia.com>; <mip6@ietf.org>
> Sent: Tuesday, August 22, 2006 5:00 AM
> Subject: RE: [Mip6] Conclusion of the consensus call related
> tothebootstrapping I-Ds
>=20
>=20
> >
> > Hi Raj,
> >
> > Given that the options were:
> >
> > 1. Have a single document which specifies the solution describing
> >   bootstrapping with DHCPv6 which includes the DHCPv6 options that
> >   are needed.
> >
> > 2. Specify the DHCP options needed for bootstrapping with DHCPv6 in
a
> >   separate document and have this referenced in the solution I-D.
> >
> >
> > And the WG consensus was for option 2, we cannot be still asking:
> >
> >> Is the integrated scenario bootstrap document still useful or
needed?
> >
> > This question is already answered. That was the whole idea behind
this
> > consensus call (one vs. two documents).
> >
> > Alper
> >
> >
> >
> > _______________________________________________
> > Mip6 mailing list
> > Mip6@ietf.org
> > https://www1.ietf.org/mailman/listinfo/mip6
> >
>=20
>=20
>=20
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6


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

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



From mip6-bounces@ietf.org Tue Aug 22 13:46:31 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GFaKR-0001u6-9N; Tue, 22 Aug 2006 13:46:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GFaKP-0001tr-Nw
	for mip6@ietf.org; Tue, 22 Aug 2006 13:46:17 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GFWUM-0006CD-JQ
	for mip6@ietf.org; Tue, 22 Aug 2006 09:40:18 -0400
Received: from mx0.starentnetworks.com ([12.38.223.203])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1GFW8L-00071k-NH
	for mip6@ietf.org; Tue, 22 Aug 2006 09:17:37 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mx0.starentnetworks.com (Postfix) with ESMTP id 6B77B9002A;
	Tue, 22 Aug 2006 09:17:29 -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 01349-08; Tue, 22 Aug 2006 09:17:27 -0400 (EDT)
Received: from exchtewks1.starentnetworks.com (exchtewks1.starentnetworks.com
	[12.33.233.52]) by mx0.starentnetworks.com (Postfix) with ESMTP;
	Tue, 22 Aug 2006 09:17:27 -0400 (EDT)
X-MessageTextProcessor: DisclaimIt (2.70.271) [Starent Networks Corp.]
Received: from exchtewks2.starentnetworks.com ([12.33.232.12]) by
	exchtewks1.starentnetworks.com with Microsoft
	SMTPSVC(6.0.3790.1830); Tue, 22 Aug 2006 09:17:27 -0400
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] Conclusion of the consensus call related
	tothe	bootstrapping I-Ds
Date: Tue, 22 Aug 2006 09:17:27 -0400
Message-ID: <7CCD07160348804497EF29E9EA5560D7837237@exchtewks2.starentnetworks.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] Conclusion of the consensus call related
	tothe	bootstrapping I-Ds
thread-index: AcbF0S6mLHNyJ3ZeSWudEUPxqTzzggAGx6jA
From: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
To: "Vijay Devarapalli" <vijay.devarapalli@azairenet.com>
Importance: normal
Priority: normal
X-OriginalArrivalTime: 22 Aug 2006 13:17:27.0637 (UTC)
	FILETIME=[50930050:01C6C5ED]
X-Virus-Scanned: amavisd-new 2.2.1 (20041222) at mx0.starentnetworks.com
X-Spam-Score: -2.6 (--)
X-Scan-Signature: 6ffdee8af20de249c24731d8414917d3
Cc: mip6@ietf.org, Heejin Jang <heejin.jang@samsung.com>,
	Basavaraj Patil <basavaraj.patil@nokia.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org



> -----Original Message-----
> From: Vijay Devarapalli [mailto:vijay.devarapalli@azairenet.com]
> Sent: Tuesday, August 22, 2006 4:37 AM
> To: Heejin Jang
> Cc: mip6@ietf.org; 'Basavaraj Patil'
> Subject: Re: [Mip6] Conclusion of the consensus call related tothe
> bootstrapping I-Ds
>=20
> Heejin Jang wrote:
> > If bootstrap document is deprecated and integrated to draft-hiopt,
> > it does not make difference from option (1).
> > If bootstrap document is deprecated and not integrated to
draft-hiopt,
> > there is no standard document for integrated-bootstrapping
scenarios.
>=20
> lets discuss this further. there is no standard document for
> integrated bootstrapping scenarios currently. we have *one*
> solution for the integrated scenario using DHCP. perhaps it
> is best left that way. initially in the bootstrapping design
> team, folks managed to convince me and others in the design
> team that DHCP was the way to go for the integrated scenario.
> but now it turns out that using DHCP needs many hacks,
> especially when the NAS and the DHCP server are separate
> boxes (which is true most of the time). I am not any more
> convinced that DHCP based bootstrapping should be a proposed
> standard (note that this my personal opinion).
>=20
[KC>] In the integrated solution there is no assumption that the NAS and
the DHCP server are in the same box. It is an optimization that some SDO
implementations can leverage, but it is NOT what we have defined in
IETF. To help refresh your memory, please look at steps 3 and 4 in Fig 2
and 3.
=20

> what I would like to see is a informational document written
> that shows how exactly DHCP is being planned for use for MIP6
> bootstrapping in various SDOs and have that reviewed by the
> DHC WG.
>=20
[KC>] We have just finished wasting our times haggling over a pure
documentation issue. Thanks to you and few others! It will be incredibly
bad, if we start another round of wasteful debate...

> Vijay
>=20
> >
> > -- Regards,
> > Heejin.
> >
> >
> > -----Original Message-----
> > From: Basavaraj Patil [mailto:basavaraj.patil@nokia.com]
> > Sent: Tuesday, August 22, 2006 7:17 AM
> > To: mip6@ietf.org
> > Subject: [Mip6] Conclusion of the consensus call related to the
> > bootstrapping I-Ds
> >
> >
> >
> > Hello,
> >
> > The consensus call for determining how to specify the DHCP options
has
> > concluded. The details of the consensus call are at:
> > http://www1.ietf.org/mail-archive/web/mip6/current/msg05033.html
> >
> > Conclusion:
> > WG consensus is to specify the DHCP options in a separate document
> > (independent of the I-D:
> > draft-ietf-mip6-bootstrapping-integrated-dhc-01). Hence we will
adopt
> > draft-jang-mip6-hiopt-00.txt as a WG I-D and specify the DHCP
options
> > required for bootstrapping. It is also possible that a couple of the
> DHCP
> > options that are currently included in the I-D:
> > draft-ietf-mip6-bootstrapping-integrated-dhc-01.txt may be included
in
> the
> > new WG I-D.
> >
> >
> > Is the integrated scenario bootstrap document still useful or
needed?
> > I think there have been some opinions that it may not be essential
and
> hence
> > we will determine if there is a need to continue working on it or to
> > deprecate it by the end of this month.
> >
> > -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
>=20
>=20
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6


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

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



From mip6-bounces@ietf.org Tue Aug 22 14:29:06 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GFazf-0007dt-OK; Tue, 22 Aug 2006 14:28:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GFaze-0007dZ-Jv
	for mip6@ietf.org; Tue, 22 Aug 2006 14:28:54 -0400
Received: from key1.docomolabs-usa.com ([216.98.102.225]
	helo=fridge.docomolabs-usa.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GFazd-0004Ej-7c
	for mip6@ietf.org; Tue, 22 Aug 2006 14:28:54 -0400
Message-ID: <051401c6c618$ce47bb00$636015ac@dcml.docomolabsusa.com>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>,
	"Alper Yegin" <alper.yegin@yegin.org>,
	"Basavaraj Patil" <basavaraj.patil@nokia.com>, <mip6@ietf.org>
References: <7CCD07160348804497EF29E9EA5560D7837242@exchtewks2.starentnetworks.com>
Subject: Re: [Mip6] Conclusion of the consensus call relatedtothebootstrapping
	I-Ds
Date: Tue, 22 Aug 2006 11:28:46 -0700
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Cc: 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Kuntal,


[KC>] The problem statements for mip6 bootstrapping talks about two
scenarios split and integrated. We have two I-Ds for each scenario. Now,
you are questioning the need for a solution document for the integrated
scenario to be standards track document or not. What about split
scenario document? The split scenario document is nothing but a
framework with a handful of (rather useless) things like DNS update and

jak>> Let's try to avoid emotional language, shall we? We're trying to 
determine what would be the best role for this document, in terms of its 
potential customers.

HL prefix etc. Integrated scenario is likely to be widely deployed,
where as the split scenario doesn't even have any buyer.

jak>> I think you mean draft-jang will be widely deployed. As I recall 
someone posted email a while back saying that there was no plan by any other 
SDO to adopt the integrated draft as is, just the two draft-jang DHCP 
enhancements.

So, if you want to go down this path, we will end up making both the
documents informational. If not both of them should remain standards
track.

jak>> We're not discussing the split draft here. If you want to propose 
changing it, then start a separate thread.

jak>> The integrated draft has some protocol enhancements, in Sections 3.5.1 
and 3.5.2. These could be separated out into a separate, PS draft, just as 
the WG has decided to do with draft-jang, and the system description in the 
rest of the draft could be published as Informational, with perhaps some 
additional work to complete the survey of what other SDOs are doing. That 
way, the other SDOs could pick and choose what part of the DHCP solution 
they want to standardize and how to combine them, and the integrated draft 
could serve as a documentation of how other SDOs are using DHCP 
bootstrapping in their system architecture. This seems to be more consistent 
with the way most WG members seem to want the DHCP solution to be 
standardized.

            jak 



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



From mip6-bounces@ietf.org Tue Aug 22 15:07:00 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GFbZc-0003VX-1E; Tue, 22 Aug 2006 15:06:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GFbZa-0003VS-Hv
	for mip6@ietf.org; Tue, 22 Aug 2006 15:06:02 -0400
Received: from mail1.azairenet.com ([66.92.223.4] helo=bart.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GFbZZ-0004zp-50
	for mip6@ietf.org; Tue, 22 Aug 2006 15:06:02 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] Conclusion of the consensus call
	relatedtothebootstrappingI-Ds
Date: Tue, 22 Aug 2006 12:02:34 -0700
Message-ID: <C8E1D942CB394746BE5CFEB7D97610E70169AA6D@bart.corp.azairenet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] Conclusion of the consensus callrelatedtothebootstrapping
	I-Ds
thread-index: AcbGDKUk4/eB2o22SoCUKu74vuLjaQABC1RAAAMtCYU=
From: "Vijay Devarapalli" <Vijay.Devarapalli@AzaireNet.com>
To: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>,
	"James Kempf" <kempf@docomolabs-usa.com>,
	"Alper Yegin" <alper.yegin@yegin.org>,
	"Basavaraj Patil" <basavaraj.patil@nokia.com>, <mip6@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b2809b6f39decc6de467dcf252f42af1
Cc: 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Kuntal,
=20
we are currently discussing bootstrapping based on DHCP. the=20
solution for split scenario is based on DNS based HA discovery
and the use of IKEv2 for home address configuration. it is a=20
solution that works in all scenarios. thats why it is on standards=20
track.=20
=20
so lets stick to discussiong DHCP based MIP6 bootstrapping.
=20
Vijay

________________________________

From: Chowdhury, Kuntal [mailto:kchowdhury@starentnetworks.com]
Sent: Tue 8/22/2006 10:41 AM
To: James Kempf; Alper Yegin; Basavaraj Patil; mip6@ietf.org
Subject: RE: [Mip6] Conclusion of the consensus call =
relatedtothebootstrappingI-Ds





> -----Original Message-----
> From: James Kempf [mailto:kempf@docomolabs-usa.com]
> Sent: Tuesday, August 22, 2006 11:43 AM
> To: Alper Yegin; 'Basavaraj Patil'; mip6@ietf.org
> Subject: Re: [Mip6] Conclusion of the consensus call
> relatedtothebootstrapping I-Ds
>
> Alper,
>
> >From an interoperation standpoint, if draft-jang is Proposed
Standard, is
> there really any need for the integrated scenerio document to be
Proposed
> Standard as well? As I recall, there are a number of assumptions about
> system architecture in the document that may be specific to certain
SDO
> architectures. Would it make more sense to expand the document's scope
> into
> a survey of how DHCP is used for bootstrapping in various SDO
> architectures
> and make it Informational?
>
[KC>] The problem statements for mip6 bootstrapping talks about two
scenarios split and integrated. We have two I-Ds for each scenario. Now,
you are questioning the need for a solution document for the integrated
scenario to be standards track document or not. What about split
scenario document? The split scenario document is nothing but a
framework with a handful of (rather useless) things like DNS update and
HL prefix etc. Integrated scenario is likely to be widely deployed,
where as the split scenario doesn't even have any buyer.

So, if you want to go down this path, we will end up making both the
documents informational. If not both of them should remain standards
track.

>                        jak
>
> ----- Original Message -----
> From: "Alper Yegin" <alper.yegin@yegin.org>
> To: "'Basavaraj Patil'" <basavaraj.patil@nokia.com>; <mip6@ietf.org>
> Sent: Tuesday, August 22, 2006 5:00 AM
> Subject: RE: [Mip6] Conclusion of the consensus call related
> tothebootstrapping I-Ds
>
>
> >
> > Hi Raj,
> >
> > Given that the options were:
> >
> > 1. Have a single document which specifies the solution describing
> >   bootstrapping with DHCPv6 which includes the DHCPv6 options that
> >   are needed.
> >
> > 2. Specify the DHCP options needed for bootstrapping with DHCPv6 in
a
> >   separate document and have this referenced in the solution I-D.
> >
> >
> > And the WG consensus was for option 2, we cannot be still asking:
> >
> >> Is the integrated scenario bootstrap document still useful or
needed?
> >
> > This question is already answered. That was the whole idea behind
this
> > consensus call (one vs. two documents).
> >
> > Alper
> >
> >
> >
> > _______________________________________________
> > Mip6 mailing list
> > Mip6@ietf.org
> > https://www1.ietf.org/mailman/listinfo/mip6
> >
>
>
>
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6


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

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



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



From mip6-bounces@ietf.org Tue Aug 22 15:14:14 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GFbhN-000601-79; Tue, 22 Aug 2006 15:14:05 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GFbhL-0005yU-LR
	for mip6@ietf.org; Tue, 22 Aug 2006 15:14:03 -0400
Received: from mgw-ext13.nokia.com ([131.228.20.172])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GFbhK-00072f-7u
	for mip6@ietf.org; Tue, 22 Aug 2006 15:14:03 -0400
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
	by mgw-ext13.nokia.com (Switch-3.1.10/Switch-3.1.7) with ESMTP id
	k7MJDuMd017836; Tue, 22 Aug 2006 22:13:57 +0300
Received: from daebh102.NOE.Nokia.com ([10.241.35.112]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 22 Aug 2006 22:13:28 +0300
Received: from daebe101.NOE.Nokia.com ([10.241.35.113]) by
	daebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 22 Aug 2006 14:13:08 -0500
Received: from 172.19.244.121 ([172.19.244.121]) by daebe101.NOE.Nokia.com
	([10.241.35.113]) with Microsoft Exchange Server HTTP-DAV ; 
	Tue, 22 Aug 2006 19:13:07 +0000
User-Agent: Microsoft-Entourage/11.2.5.060620
Date: Tue, 22 Aug 2006 14:13:48 -0500
Subject: Re: [Mip6] Conclusion of the consensus call related to the
	bootstrapping I-Ds
From: Basavaraj Patil <basavaraj.patil@nokia.com>
To: ext James Kempf <kempf@docomolabs-usa.com>,
	"Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>,
	Alper Yegin <alper.yegin@yegin.org>, <mip6@ietf.org>
Message-ID: <C110C19C.22AAB%basavaraj.patil@nokia.com>
Thread-Topic: [Mip6] Conclusion of the consensus call related to the
	bootstrapping I-Ds
Thread-Index: AcbGHxhDVv4XVDISEduldAARJNUNiA==
In-Reply-To: <051401c6c618$ce47bb00$636015ac@dcml.docomolabsusa.com>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 22 Aug 2006 19:13:08.0413 (UTC)
	FILETIME=[00AAFED0:01C6C61F]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Cc: 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org


Having spent a few months on deliberating how DHCP options required for
bootstrapping be specified, lets not go back in time and start discussing if
the intergrated scenarios I-D is necessary or not.

When the design team was formed, the conclusion after the completion of the
split scenarios I-D was that a solution for the integrated scenario is
needed as well and hence the creation of the WG I-D.

I have also been told by 3GPP2 (liaison) that they have a dependency on the
integrated scenarios I-D.

Hence I would recommend that we stop this discussion and lets work on
completing the bootstrap solutions work.

-Raj


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



From mip6-bounces@ietf.org Tue Aug 22 15:41:43 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GFc7y-0008Ce-84; Tue, 22 Aug 2006 15:41:34 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GFc7x-0008Bg-6X
	for mip6@ietf.org; Tue, 22 Aug 2006 15:41:33 -0400
Received: from key1.docomolabs-usa.com ([216.98.102.225]
	helo=fridge.docomolabs-usa.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GFc7v-0004qy-Qj
	for mip6@ietf.org; Tue, 22 Aug 2006 15:41:33 -0400
Message-ID: <056001c6c622$ebb25b00$636015ac@dcml.docomolabsusa.com>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Basavaraj Patil" <basavaraj.patil@nokia.com>,
	"Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>,
	"Alper Yegin" <alper.yegin@yegin.org>, <mip6@ietf.org>
References: <C110C19C.22AAB%basavaraj.patil@nokia.com>
Subject: Re: [Mip6] Conclusion of the consensus call related to the
	bootstrapping I-Ds
Date: Tue, 22 Aug 2006 12:41:11 -0700
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Cc: 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Raj,

I'm not questioning the need for the document. What I'm asking is whether 
the document, as it stands, is consistent with the direction the WG wants to 
go in, given the consensus decision not to include the DHCP options into it. 
It seems to me that the direction is for the various pieces of the 
intergrated solution as separate documents.

Regarding the 3GPP dependency, do they really want the system description 
part or are they really interested in the relay to server options?

            jak


----- Original Message ----- 
From: "Basavaraj Patil" <basavaraj.patil@nokia.com>
To: "ext James Kempf" <kempf@docomolabs-usa.com>; "Chowdhury, Kuntal" 
<kchowdhury@starentnetworks.com>; "Alper Yegin" <alper.yegin@yegin.org>; 
<mip6@ietf.org>
Sent: Tuesday, August 22, 2006 12:13 PM
Subject: Re: [Mip6] Conclusion of the consensus call related to the 
bootstrapping I-Ds


>
> Having spent a few months on deliberating how DHCP options required for
> bootstrapping be specified, lets not go back in time and start discussing 
> if
> the intergrated scenarios I-D is necessary or not.
>
> When the design team was formed, the conclusion after the completion of 
> the
> split scenarios I-D was that a solution for the integrated scenario is
> needed as well and hence the creation of the WG I-D.
>
> I have also been told by 3GPP2 (liaison) that they have a dependency on 
> the
> integrated scenarios I-D.
>
> Hence I would recommend that we stop this discussion and lets work on
> completing the bootstrap solutions work.
>
> -Raj
>
> 



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



From mip6-bounces@ietf.org Tue Aug 22 16:37:12 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GFczc-0000vq-54; Tue, 22 Aug 2006 16:37:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GFcza-0000vb-Pv
	for mip6@ietf.org; Tue, 22 Aug 2006 16:36:58 -0400
Received: from key1.docomolabs-usa.com ([216.98.102.225]
	helo=fridge.docomolabs-usa.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GFcza-0005uC-Aa
	for mip6@ietf.org; Tue, 22 Aug 2006 16:36:58 -0400
Message-ID: <058701c6c62a$bd3d11e0$636015ac@dcml.docomolabsusa.com>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>,
	"Alper Yegin" <alper.yegin@yegin.org>,
	"Basavaraj Patil" <basavaraj.patil@nokia.com>, <mip6@ietf.org>
References: <7CCD07160348804497EF29E9EA5560D7837244@exchtewks2.starentnetworks.com>
Subject: Kuntal's comments on the split document (was: Re: [Mip6] Conclusion
	of the consensus call relatedtothebootstrapping I-Ds)
Date: Tue, 22 Aug 2006 13:37:08 -0700
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: 31247fb3be228bb596db9127becad0bc
Cc: 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Alright. If you want to discuss the split document then let's do it (note 
change in thread header).

[KC>] Which part of my statement you found to be "emotional"? Is it the
"rather useless" part? In my opinion, the split scenario solution
document has some things that are totally out of scope of mip6
bootstrapping (e.g. the dynamic DNS update). Moreover, the HA
bootstrapping is based on DNS query which has security issues. Anybody
in the public internet can discover operator's HAs. This is a security
hole that the split solution introduces. These are NOT emotional
statements :-). I am just expressing how I feel about the split solution
document, that's all.

jak>> These are your opinions, and I would say they are rather emotionally 
expressed (my opinion, of course).

jak>> The goals of the split document are different from the intergrated 
document. The split document is primarily for enterprises and for businesses 
that have as their primary business providing mobility service only (hence 
the name). Since such businesses are new, they are likely to be 
entrepreneurial. They're not going to have the time or resources to run 
around to various different SDOs and try to force their solutions to get 
locked into the standards. The split solution is designed to provide them 
with interoperability. It is possible for integrated wireless service 
providers to use the split solution, of course, possibly as an additional 
revenue generator for providing mobility service to customers that use a 
different access network provider.

jak>> Regarding the security issues of DNS, we've been through this issue a 
number of times, the draft was reviewed by SAAG (we have yet to respond) and 
there was nothing said about it, so I am puzzled why you are raising this 
canard again. We recently had a good (and I might add nonemotional) 
discussion on this list about using anycast, initiated by Jean-Marie, and 
I've drafted some text up that will allow anycast addresses to be used in 
DNS SRV RRs instead of the unicast addresses of the HAs, based on Francis's 
draft, and sent the text to Gerardo (he's on vacation at the moment). This 
should provide some moderate protection from DoS, but it will not protect 
completely, just as the DHCP solution won't. As I've pointed out in the 
past, as soon as you release the address of a server to an end host, 
regardless of how it is done, all bets are off. What the end host does with 
that address is completely out of your control, and if the end host is 
infected with malware, you can be sure somebody's botnet will get the 
address. Or are you proposing some enhancement to the DHCP based solution 
that will make it impossible for malware to grab a home agent's address?

> HL prefix etc. Integrated scenario is likely to be widely deployed,
> where as the split scenario doesn't even have any buyer.
>
> jak>> I think you mean draft-jang will be widely deployed. As I recall
> someone posted email a while back saying that there was no plan by any
> other
> SDO to adopt the integrated draft as is, just the two draft-jang DHCP
> enhancements.
>
[KC>] Unfortunately, here you are making your argument based on some
rumor that you heard about real SDO requirements. Please use official
liaison channels to confirm SDO requirements before posting comments on
the mailing list.

jak>> OK. Would any of our liasons like to comment on this? Is the system 
architecture described in the integrated draft what your SDO is planning on 
standardizing?

> So, if you want to go down this path, we will end up making both the
> documents informational. If not both of them should remain standards
> track.
>
> jak>> We're not discussing the split draft here. If you want to
propose
> changing it, then start a separate thread.
>
[KC>] We need to discuss how useful the split scenario draft is. Also to
be fair, we need to make a decision about informational vs. standards
track suitability for _both_ the documents if that's what the WG ends up
deciding. That's what I meant to say here.

jak>> Then why didn't you start a separate thread on it? This is basic IETF 
courtesy. Kuntal, you've been around IETF long enough to know these kinds of 
things.

            jak 



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



From mip6-bounces@ietf.org Tue Aug 22 17:14:28 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GFdZB-00074m-KV; Tue, 22 Aug 2006 17:13:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GFdZB-00074P-2c
	for mip6@ietf.org; Tue, 22 Aug 2006 17:13:45 -0400
Received: from mgw-ext13.nokia.com ([131.228.20.172])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GFdZ9-00043W-Fz
	for mip6@ietf.org; Tue, 22 Aug 2006 17:13:45 -0400
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211])
	by mgw-ext13.nokia.com (Switch-3.1.10/Switch-3.1.7) with ESMTP id
	k7MLDY9m029005; Wed, 23 Aug 2006 00:13:39 +0300
Received: from daebh101.NOE.Nokia.com ([10.241.35.111]) by
	esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 23 Aug 2006 00:12:34 +0300
Received: from daebe101.NOE.Nokia.com ([10.241.35.113]) by
	daebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 22 Aug 2006 16:12:31 -0500
Received: from 172.19.244.121 ([172.19.244.121]) by daebe101.NOE.Nokia.com
	([10.241.35.113]) with Microsoft Exchange Server HTTP-DAV ; 
	Tue, 22 Aug 2006 21:12:30 +0000
User-Agent: Microsoft-Entourage/11.2.5.060620
Date: Tue, 22 Aug 2006 16:13:11 -0500
Subject: Re: [Mip6] Conclusion of the consensus call related to the
	bootstrapping I-Ds
From: Basavaraj Patil <basavaraj.patil@nokia.com>
To: ext James Kempf <kempf@docomolabs-usa.com>,
	"Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>,
	Alper Yegin <alper.yegin@yegin.org>, <mip6@ietf.org>
Message-ID: <C110DD97.22AF5%basavaraj.patil@nokia.com>
Thread-Topic: [Mip6] Conclusion of the consensus call related to the
	bootstrapping I-Ds
Thread-Index: AcbGL8W+BGGOlzIjEduldAARJNUNiA==
In-Reply-To: <056001c6c622$ebb25b00$636015ac@dcml.docomolabsusa.com>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 22 Aug 2006 21:12:31.0426 (UTC)
	FILETIME=[AE280A20:01C6C62F]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976
Cc: 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org


Hi James,

Stepping back from the specifics of the documents that we have today in the
WG w.r.t bootstrapping, I believe what the WG is chartered (which needs to
be updated BTW), is to develop a solution or solutions for bootstrapping
MIP6. I think we disccovered fairly early on that one bootstrapping solution
does not fit all environments. We are now even considering adopting Vijay's
draft which specifies bootstrapping in the case of the use of the
authenication protocol. But that's not the point here.

The WG direction is to develop a set of bootstrapping solutions that can be
used in various deployment scenarios. The scenarios that we have specified
in the WG today are based on the use of IKE for bootstrapping for the cases
that we call split and integrated. The issue about whether the DHCP options
should be specified within the integrated scenarios document or separately
is simply a matter of how we split the documents.
Consensus was that keeping the DHCP options is preferred because of various
reasons (as has been discussed at length).

My recommendation is that we move forward with the set of existing I-Ds
which include the problem statement, Split scenario, Integrated scenario,
and DHCPv6 options.

W.r.t what 3GPP2 really wants from the integrated scenarios I-D, I believe
they require the IKE based bootstrapping solution for MIP6 and not just the
DHCP options.

-Raj


On 8/22/06 2:41 PM, "ext James Kempf" <kempf@docomolabs-usa.com> wrote:

> Raj,
> 
> I'm not questioning the need for the document. What I'm asking is whether
> the document, as it stands, is consistent with the direction the WG wants to
> go in, given the consensus decision not to include the DHCP options into it.
> It seems to me that the direction is for the various pieces of the
> intergrated solution as separate documents.
> 
> Regarding the 3GPP dependency, do they really want the system description
> part or are they really interested in the relay to server options?
> 
>             jak
> 
> 
> ----- Original Message -----
> From: "Basavaraj Patil" <basavaraj.patil@nokia.com>
> To: "ext James Kempf" <kempf@docomolabs-usa.com>; "Chowdhury, Kuntal"
> <kchowdhury@starentnetworks.com>; "Alper Yegin" <alper.yegin@yegin.org>;
> <mip6@ietf.org>
> Sent: Tuesday, August 22, 2006 12:13 PM
> Subject: Re: [Mip6] Conclusion of the consensus call related to the
> bootstrapping I-Ds
> 
> 
>> 
>> Having spent a few months on deliberating how DHCP options required for
>> bootstrapping be specified, lets not go back in time and start discussing
>> if
>> the intergrated scenarios I-D is necessary or not.
>> 
>> When the design team was formed, the conclusion after the completion of
>> the
>> split scenarios I-D was that a solution for the integrated scenario is
>> needed as well and hence the creation of the WG I-D.
>> 
>> I have also been told by 3GPP2 (liaison) that they have a dependency on
>> the
>> integrated scenarios I-D.
>> 
>> Hence I would recommend that we stop this discussion and lets work on
>> completing the bootstrap solutions work.
>> 
>> -Raj
>> 
>> 
> 
> 


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



From mip6-bounces@ietf.org Tue Aug 22 17:26:13 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GFdkx-000180-Ta; Tue, 22 Aug 2006 17:25:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GFdkx-00017q-0X
	for mip6@ietf.org; Tue, 22 Aug 2006 17:25:55 -0400
Received: from key1.docomolabs-usa.com ([216.98.102.225]
	helo=fridge.docomolabs-usa.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GFdkv-0006Qb-Jj
	for mip6@ietf.org; Tue, 22 Aug 2006 17:25:54 -0400
Message-ID: <0cc401c6c631$8ed3cc20$636015ac@dcml.docomolabsusa.com>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Basavaraj Patil" <basavaraj.patil@nokia.com>,
	"Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>,
	"Alper Yegin" <alper.yegin@yegin.org>, <mip6@ietf.org>
References: <C110DD97.22AF5%basavaraj.patil@nokia.com>
Subject: Re: [Mip6] Conclusion of the consensus call related to the
	bootstrapping I-Ds
Date: Tue, 22 Aug 2006 14:25:57 -0700
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Cc: 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Raj,

> Stepping back from the specifics of the documents that we have today in 
> the
> WG w.r.t bootstrapping, I believe what the WG is chartered (which needs to
> be updated BTW), is to develop a solution or solutions for bootstrapping
> MIP6. I think we disccovered fairly early on that one bootstrapping 
> solution
> does not fit all environments. We are now even considering adopting 
> Vijay's
> draft which specifies bootstrapping in the case of the use of the
> authenication protocol. But that's not the point here.
>
> The WG direction is to develop a set of bootstrapping solutions that can 
> be
> used in various deployment scenarios. The scenarios that we have specified
> in the WG today are based on the use of IKE for bootstrapping for the 
> cases
> that we call split and integrated. The issue about whether the DHCP 
> options
> should be specified within the integrated scenarios document or separately
> is simply a matter of how we split the documents.
> Consensus was that keeping the DHCP options is preferred because of 
> various
> reasons (as has been discussed at length).
>
> My recommendation is that we move forward with the set of existing I-Ds
> which include the problem statement, Split scenario, Integrated scenario,
> and DHCPv6 options.
>

As you know, I was not in favor of splitting off the DHCPv6 options into 
separate documents. However, since it seems like that is what the WG wants, 
I was just trying to get an idea of whether that should apply to the relay 
to server options too. As I mentioned to Kuntal, I think this would make a 
certain amount of sense from an organizational standpoint (protocol mods in 
separate, small PS documents, system architecture in larger Informational 
document) which is what I thought Alper was trying to achieve. I frankly 
don't care much either way.

Does anybody else in the WG have an opinion on this?


> W.r.t what 3GPP2 really wants from the integrated scenarios I-D, I believe
> they require the IKE based bootstrapping solution for MIP6 and not just 
> the
> DHCP options.
>

Then they will need to refer to something more than the integrated document. 
The IKEv2 bootstrapping is specified in the split document, not the 
integrated document.

Maybe we need the 3GPP2 liason to step forward and say what 3GPP2 wants, or 
is the liason you?

            jak




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



From mip6-bounces@ietf.org Tue Aug 22 17:56:41 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GFeES-0006Va-Oj; Tue, 22 Aug 2006 17:56:24 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GFeER-0006VR-CV
	for mip6@ietf.org; Tue, 22 Aug 2006 17:56:23 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GFcjp-0003BK-2B
	for mip6@ietf.org; Tue, 22 Aug 2006 16:20:41 -0400
Received: from mx0.starentnetworks.com ([12.38.223.203])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1GFccr-0001bR-L2
	for mip6@ietf.org; Tue, 22 Aug 2006 16:13:35 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mx0.starentnetworks.com (Postfix) with ESMTP id EF85A90036;
	Tue, 22 Aug 2006 16:13:23 -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 10338-03; Tue, 22 Aug 2006 16:13:22 -0400 (EDT)
Received: from exchtewks1.starentnetworks.com (exchtewks1.starentnetworks.com
	[12.33.233.52]) by mx0.starentnetworks.com (Postfix) with ESMTP;
	Tue, 22 Aug 2006 16:13:11 -0400 (EDT)
X-MessageTextProcessor: DisclaimIt (2.70.271) [Starent Networks Corp.]
Received: from exchtewks2.starentnetworks.com ([12.33.232.12]) by
	exchtewks1.starentnetworks.com with Microsoft
	SMTPSVC(6.0.3790.1830); Tue, 22 Aug 2006 16:13:11 -0400
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] Conclusion of the consensus call relatedtothebootstrapping
	I-Ds
Date: Tue, 22 Aug 2006 16:13:11 -0400
Message-ID: <7CCD07160348804497EF29E9EA5560D7837244@exchtewks2.starentnetworks.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] Conclusion of the consensus call
	relatedtothebootstrapping I-Ds
thread-index: AcbGGNX2u9FMnqJfRl+uCv4KBoivDAABlE4Q
From: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
Importance: normal
Priority: normal
To: "James Kempf" <kempf@docomolabs-usa.com>,
	"Alper Yegin" <alper.yegin@yegin.org>,
	"Basavaraj Patil" <basavaraj.patil@nokia.com>, <mip6@ietf.org>
X-OriginalArrivalTime: 22 Aug 2006 20:13:11.0361 (UTC)
	FILETIME=[64313B10:01C6C627]
X-Virus-Scanned: amavisd-new 2.2.1 (20041222) at mx0.starentnetworks.com
X-Spam-Score: -2.6 (--)
X-Scan-Signature: 1a1bf7677bfe77d8af1ebe0e91045c5b
Cc: 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org



> -----Original Message-----
> From: James Kempf [mailto:kempf@docomolabs-usa.com]
> Sent: Tuesday, August 22, 2006 1:29 PM
> To: Chowdhury, Kuntal; Alper Yegin; Basavaraj Patil; mip6@ietf.org
> Subject: Re: [Mip6] Conclusion of the consensus call
> relatedtothebootstrapping I-Ds
>=20
> Kuntal,
>=20
>=20
> [KC>] The problem statements for mip6 bootstrapping talks about two
> scenarios split and integrated. We have two I-Ds for each scenario.
Now,
> you are questioning the need for a solution document for the
integrated
> scenario to be standards track document or not. What about split
> scenario document? The split scenario document is nothing but a
> framework with a handful of (rather useless) things like DNS update
and
>=20
> jak>> Let's try to avoid emotional language, shall we? We're trying to
> determine what would be the best role for this document, in terms of
its
> potential customers.
>=20
[KC>] Which part of my statement you found to be "emotional"? Is it the
"rather useless" part? In my opinion, the split scenario solution
document has some things that are totally out of scope of mip6
bootstrapping (e.g. the dynamic DNS update). Moreover, the HA
bootstrapping is based on DNS query which has security issues. Anybody
in the public internet can discover operator's HAs. This is a security
hole that the split solution introduces. These are NOT emotional
statements :-). I am just expressing how I feel about the split solution
document, that's all.

> HL prefix etc. Integrated scenario is likely to be widely deployed,
> where as the split scenario doesn't even have any buyer.
>=20
> jak>> I think you mean draft-jang will be widely deployed. As I recall
> someone posted email a while back saying that there was no plan by any
> other
> SDO to adopt the integrated draft as is, just the two draft-jang DHCP
> enhancements.
>=20
[KC>] Unfortunately, here you are making your argument based on some
rumor that you heard about real SDO requirements. Please use official
liaison channels to confirm SDO requirements before posting comments on
the mailing list.


> So, if you want to go down this path, we will end up making both the
> documents informational. If not both of them should remain standards
> track.
>=20
> jak>> We're not discussing the split draft here. If you want to
propose
> changing it, then start a separate thread.
>=20
[KC>] We need to discuss how useful the split scenario draft is. Also to
be fair, we need to make a decision about informational vs. standards
track suitability for _both_ the documents if that's what the WG ends up
deciding. That's what I meant to say here.


> jak>> The integrated draft has some protocol enhancements, in Sections
> 3.5.1
> and 3.5.2. These could be separated out into a separate, PS draft,
just as
> the WG has decided to do with draft-jang, and the system description
in
> the
> rest of the draft could be published as Informational, with perhaps
some
> additional work to complete the survey of what other SDOs are doing.
That
> way, the other SDOs could pick and choose what part of the DHCP
solution
> they want to standardize and how to combine them, and the integrated
draft
> could serve as a documentation of how other SDOs are using DHCP
> bootstrapping in their system architecture. This seems to be more
> consistent
> with the way most WG members seem to want the DHCP solution to be
> standardized.
>=20
>             jak
>=20


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

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



From mip6-bounces@ietf.org Tue Aug 22 18:27:21 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GFehp-0001DP-91; Tue, 22 Aug 2006 18:26:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GFeho-0001DD-D1
	for mip6@ietf.org; Tue, 22 Aug 2006 18:26:44 -0400
Received: from mx0.starentnetworks.com ([12.38.223.203])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GFehi-0008Cq-SI
	for mip6@ietf.org; Tue, 22 Aug 2006 18:26:44 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mx0.starentnetworks.com (Postfix) with ESMTP id 86F0890066;
	Tue, 22 Aug 2006 18:26:35 -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 12965-07; Tue, 22 Aug 2006 18:26:34 -0400 (EDT)
Received: from exchtewks1.starentnetworks.com (exchtewks1.starentnetworks.com
	[12.33.233.52]) by mx0.starentnetworks.com (Postfix) with ESMTP;
	Tue, 22 Aug 2006 18:26:34 -0400 (EDT)
X-MessageTextProcessor: DisclaimIt (2.70.271) [Starent Networks Corp.]
Received: from exchtewks2.starentnetworks.com ([12.33.232.12]) by
	exchtewks1.starentnetworks.com with Microsoft
	SMTPSVC(6.0.3790.1830); Tue, 22 Aug 2006 18:26:34 -0400
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Kuntal's comments on the split document (was: Re: [Mip6]
	Conclusion of the consensus call relatedtothebootstrapping I-Ds)
Date: Tue, 22 Aug 2006 18:26:34 -0400
Message-ID: <7CCD07160348804497EF29E9EA5560D7837248@exchtewks2.starentnetworks.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Kuntal's comments on the split document (was: Re: [Mip6]
	Conclusion of the consensus call relatedtothebootstrapping I-Ds)
thread-index: AcbGKsWswIBJQvnATwWWa3sXWWdnegAAqf/w
From: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
Importance: normal
Priority: normal
To: "James Kempf" <kempf@docomolabs-usa.com>,
	"Alper Yegin" <alper.yegin@yegin.org>,
	"Basavaraj Patil" <basavaraj.patil@nokia.com>, <mip6@ietf.org>
X-OriginalArrivalTime: 22 Aug 2006 22:26:34.0539 (UTC)
	FILETIME=[067547B0:01C6C63A]
X-Virus-Scanned: amavisd-new 2.2.1 (20041222) at mx0.starentnetworks.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d890c9ddd0b0a61e8c597ad30c1c2176
Cc: 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org



> -----Original Message-----
> From: James Kempf [mailto:kempf@docomolabs-usa.com]
> Sent: Tuesday, August 22, 2006 3:37 PM
> To: Chowdhury, Kuntal; Alper Yegin; Basavaraj Patil; mip6@ietf.org
> Subject: Kuntal's comments on the split document (was: Re: [Mip6]
> Conclusion of the consensus call relatedtothebootstrapping I-Ds)
>=20
> Alright. If you want to discuss the split document then let's do it
(note
> change in thread header).
>=20
> [KC>] Which part of my statement you found to be "emotional"? Is it
the
> "rather useless" part? In my opinion, the split scenario solution
> document has some things that are totally out of scope of mip6
> bootstrapping (e.g. the dynamic DNS update). Moreover, the HA
> bootstrapping is based on DNS query which has security issues. Anybody
> in the public internet can discover operator's HAs. This is a security
> hole that the split solution introduces. These are NOT emotional
> statements :-). I am just expressing how I feel about the split
solution
> document, that's all.
>=20
> jak>> These are your opinions, and I would say they are rather
emotionally
> expressed (my opinion, of course).
>=20
> jak>> The goals of the split document are different from the
intergrated
> document. The split document is primarily for enterprises and for
> businesses
> that have as their primary business providing mobility service only
(hence
> the name). Since such businesses are new, they are likely to be
> entrepreneurial. They're not going to have the time or resources to
run
> around to various different SDOs and try to force their solutions to
get
> locked into the standards. The split solution is designed to provide
them
> with interoperability. It is possible for integrated wireless service
> providers to use the split solution, of course, possibly as an
additional
> revenue generator for providing mobility service to customers that use
a
> different access network provider.
>=20
[KC>] What you describe above is the scope of the split document. The
scope is unique, understood. But that does not automatically justify a
standards track RFC for the solution document. What we have is a split
scenario solution framework document _using_ IKEv2, DNS etc. So, are you
OK to make the split solution I-D an informational RFC?

> jak>> Regarding the security issues of DNS, we've been through this
issue
> a
> number of times, the draft was reviewed by SAAG (we have yet to
respond)
> and
> there was nothing said about it, so I am puzzled why you are raising
this
> canard again. We recently had a good (and I might add nonemotional)
> discussion on this list about using anycast, initiated by Jean-Marie,
and
> I've drafted some text up that will allow anycast addresses to be used
in
> DNS SRV RRs instead of the unicast addresses of the HAs, based on
> Francis's
> draft, and sent the text to Gerardo (he's on vacation at the moment).
This
> should provide some moderate protection from DoS, but it will not
protect
> completely, just as the DHCP solution won't. As I've pointed out in
the
> past, as soon as you release the address of a server to an end host,
> regardless of how it is done, all bets are off. What the end host does
> with
> that address is completely out of your control, and if the end host is
> infected with malware, you can be sure somebody's botnet will get the
> address. Or are you proposing some enhancement to the DHCP based
solution
> that will make it impossible for malware to grab a home agent's
address?
>=20
[KC>] There is a clear difference between the way HA address is
discovered in the split solution and in the integrated solution. The HA
address is _assigned_ to the MN in the integrated solution by the Home
AAA server. This ONLY happens once the MN passes authentication. So, the
chances of giving away the HA address to totally unknown entities in
this case is next to none. In case of split scenario, the HAs are
totally exposed to anyone with good or bad intention. Anyone with an IP
connection can send DNS queries to get any MSP's HA addresses and then
launch DoS attacks from his/her basement.=20

It is true that once the HA address is given to an entity, if that
entity is compromised, the HA address can get out to some bad guys. But
it is not likely to happen too often. This type of security threat is
generic and not specific to mip6 bootstrapping, IMHO. If the
entity/device is compromised, other things like root-key, username, any
other cached data will also be revealed. So, it is a generic issue.

In case of split scenario, the risk of giving away the HA address to bad
guys is always there. So, the solution doesn't seem to be deployable in
public wireless networks.=20

> > HL prefix etc. Integrated scenario is likely to be widely deployed,
> > where as the split scenario doesn't even have any buyer.
> >
> > jak>> I think you mean draft-jang will be widely deployed. As I
recall
> > someone posted email a while back saying that there was no plan by
any
> > other
> > SDO to adopt the integrated draft as is, just the two draft-jang
DHCP
> > enhancements.
> >
> [KC>] Unfortunately, here you are making your argument based on some
> rumor that you heard about real SDO requirements. Please use official
> liaison channels to confirm SDO requirements before posting comments
on
> the mailing list.
>=20
> jak>> OK. Would any of our liasons like to comment on this? Is the
system
> architecture described in the integrated draft what your SDO is
planning
> on
> standardizing?
>=20
> > So, if you want to go down this path, we will end up making both the
> > documents informational. If not both of them should remain standards
> > track.
> >
> > jak>> We're not discussing the split draft here. If you want to
> propose
> > changing it, then start a separate thread.
> >
> [KC>] We need to discuss how useful the split scenario draft is. Also
to
> be fair, we need to make a decision about informational vs. standards
> track suitability for _both_ the documents if that's what the WG ends
up
> deciding. That's what I meant to say here.
>=20
> jak>> Then why didn't you start a separate thread on it? This is basic
> IETF
> courtesy. Kuntal, you've been around IETF long enough to know these
kinds
> of
> things.
>=20
[KC>] OK, I apologize for raising the issues with the split solutions
I-D late in the game. James, you did not raise all the issues that you
had with the integrated I-D until now. You have been around in IETF more
than I have been....


>             jak
>=20


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

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



From mip6-bounces@ietf.org Tue Aug 22 19:17:14 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GFfU1-0005Rr-4o; Tue, 22 Aug 2006 19:16:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GFfTz-0005Qq-U1
	for mip6@ietf.org; Tue, 22 Aug 2006 19:16:31 -0400
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GFfTz-00058t-AY
	for mip6@ietf.org; Tue, 22 Aug 2006 19:16:31 -0400
Received: from magus.qualcomm.com (magus.qualcomm.com [129.46.61.148])
	by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k7MNGSuW020976
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Tue, 22 Aug 2006 16:16:28 -0700
Received: from NAEXBR03.na.qualcomm.com (naexbr03.qualcomm.com
	[129.46.134.172])
	by magus.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id k7MNGQKX022085; 
	Tue, 22 Aug 2006 16:16:27 -0700 (PDT)
Received: from NAEX14.na.qualcomm.com ([10.47.5.242]) by
	NAEXBR03.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 22 Aug 2006 16:16:25 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Kuntal's comments on the split document (was: Re:
	[Mip6]Conclusion of the consensus call relatedtothebootstrapping I-Ds)
Date: Tue, 22 Aug 2006 16:16:24 -0700
Message-ID: <7EB20EA0938B4D42A2D82689365C9B7A11DBD6@NAEX14.na.qualcomm.com>
In-Reply-To: <7CCD07160348804497EF29E9EA5560D7837248@exchtewks2.starentnetworks.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Kuntal's comments on the split document (was: Re:
	[Mip6]Conclusion of the consensus call
	relatedtothebootstrapping I-Ds)
Thread-Index: AcbGKsWswIBJQvnATwWWa3sXWWdnegAAqf/wAARS70A=
From: "Tsirtsis, George" <tsirtsis@qualcomm.com>
To: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>,
	"James Kempf" <kempf@docomolabs-usa.com>,
	"Alper Yegin" <alper.yegin@yegin.org>,
	"Basavaraj Patil" <basavaraj.patil@nokia.com>, <mip6@ietf.org>
X-OriginalArrivalTime: 22 Aug 2006 23:16:25.0982 (UTC)
	FILETIME=[FD7F41E0:01C6C640]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 850245b51c39701e2700a112f3032caa
Cc: 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

I have not followed this discussion from the beginning so my apologies
if this has been discussed before.=20

IMHO, the problem with both the split and integrated documents is that
they are more system design documents than protocol specifications.=20

I think the WG correctly decided to standardize the DHCP-option of the
integrated document separately since this is the protocol part.=20
The rest of the document defines a way to use the DHCP-option together
with other IETF "tools" to build a system. The split document does the
same thing so, if there is a protocol extension to be standardized
(e.g., DNS Update mobility option) it needs to be taken out and be
standardized.

Let me remind everyone that the IETF does not build
systems/architectures unless absolutely necessary and in this case it is
not necessary since one can come up with many different ways of using
several IETF protocols to bootstrap MIP, all of which are valid.

The "system description" parts of the split/integrated documents can
then become whatever; it does not really matter since the notion of
"standards track" in the IETF does not apply to systems. As far as I am
concerned, if they need to be standardized at all, they need to be
standardized in an SDO otherwise informational or BCP can work too.

Regards
George

> -----Original Message-----
> From: Chowdhury, Kuntal [mailto:kchowdhury@starentnetworks.com]
> Sent: Tuesday, August 22, 2006 6:27 PM
> To: James Kempf; Alper Yegin; Basavaraj Patil; mip6@ietf.org
> Subject: RE: Kuntal's comments on the split document (was: Re:
> [Mip6]Conclusion of the consensus call relatedtothebootstrapping I-Ds)
>=20
>=20
>=20
> > -----Original Message-----
> > From: James Kempf [mailto:kempf@docomolabs-usa.com]
> > Sent: Tuesday, August 22, 2006 3:37 PM
> > To: Chowdhury, Kuntal; Alper Yegin; Basavaraj Patil; mip6@ietf.org
> > Subject: Kuntal's comments on the split document (was: Re: [Mip6]
> > Conclusion of the consensus call relatedtothebootstrapping I-Ds)
> >
> > Alright. If you want to discuss the split document then let's do it
> (note
> > change in thread header).
> >
> > [KC>] Which part of my statement you found to be "emotional"? Is it
> the
> > "rather useless" part? In my opinion, the split scenario solution
> > document has some things that are totally out of scope of mip6
> > bootstrapping (e.g. the dynamic DNS update). Moreover, the HA
> > bootstrapping is based on DNS query which has security issues.
Anybody
> > in the public internet can discover operator's HAs. This is a
security
> > hole that the split solution introduces. These are NOT emotional
> > statements :-). I am just expressing how I feel about the split
> solution
> > document, that's all.
> >
> > jak>> These are your opinions, and I would say they are rather
> emotionally
> > expressed (my opinion, of course).
> >
> > jak>> The goals of the split document are different from the
> intergrated
> > document. The split document is primarily for enterprises and for
> > businesses
> > that have as their primary business providing mobility service only
> (hence
> > the name). Since such businesses are new, they are likely to be
> > entrepreneurial. They're not going to have the time or resources to
> run
> > around to various different SDOs and try to force their solutions to
> get
> > locked into the standards. The split solution is designed to provide
> them
> > with interoperability. It is possible for integrated wireless
service
> > providers to use the split solution, of course, possibly as an
> additional
> > revenue generator for providing mobility service to customers that
use
> a
> > different access network provider.
> >
> [KC>] What you describe above is the scope of the split document. The
> scope is unique, understood. But that does not automatically justify a
> standards track RFC for the solution document. What we have is a split
> scenario solution framework document _using_ IKEv2, DNS etc. So, are
you
> OK to make the split solution I-D an informational RFC?
>=20
> > jak>> Regarding the security issues of DNS, we've been through this
> issue
> > a
> > number of times, the draft was reviewed by SAAG (we have yet to
> respond)
> > and
> > there was nothing said about it, so I am puzzled why you are raising
> this
> > canard again. We recently had a good (and I might add nonemotional)
> > discussion on this list about using anycast, initiated by
Jean-Marie,
> and
> > I've drafted some text up that will allow anycast addresses to be
used
> in
> > DNS SRV RRs instead of the unicast addresses of the HAs, based on
> > Francis's
> > draft, and sent the text to Gerardo (he's on vacation at the
moment).
> This
> > should provide some moderate protection from DoS, but it will not
> protect
> > completely, just as the DHCP solution won't. As I've pointed out in
> the
> > past, as soon as you release the address of a server to an end host,
> > regardless of how it is done, all bets are off. What the end host
does
> > with
> > that address is completely out of your control, and if the end host
is
> > infected with malware, you can be sure somebody's botnet will get
the
> > address. Or are you proposing some enhancement to the DHCP based
> solution
> > that will make it impossible for malware to grab a home agent's
> address?
> >
> [KC>] There is a clear difference between the way HA address is
> discovered in the split solution and in the integrated solution. The
HA
> address is _assigned_ to the MN in the integrated solution by the Home
> AAA server. This ONLY happens once the MN passes authentication. So,
the
> chances of giving away the HA address to totally unknown entities in
> this case is next to none. In case of split scenario, the HAs are
> totally exposed to anyone with good or bad intention. Anyone with an
IP
> connection can send DNS queries to get any MSP's HA addresses and then
> launch DoS attacks from his/her basement.
>=20
> It is true that once the HA address is given to an entity, if that
> entity is compromised, the HA address can get out to some bad guys.
But
> it is not likely to happen too often. This type of security threat is
> generic and not specific to mip6 bootstrapping, IMHO. If the
> entity/device is compromised, other things like root-key, username,
any
> other cached data will also be revealed. So, it is a generic issue.
>=20
> In case of split scenario, the risk of giving away the HA address to
bad
> guys is always there. So, the solution doesn't seem to be deployable
in
> public wireless networks.
>=20
> > > HL prefix etc. Integrated scenario is likely to be widely
deployed,
> > > where as the split scenario doesn't even have any buyer.
> > >
> > > jak>> I think you mean draft-jang will be widely deployed. As I
> recall
> > > someone posted email a while back saying that there was no plan by
> any
> > > other
> > > SDO to adopt the integrated draft as is, just the two draft-jang
> DHCP
> > > enhancements.
> > >
> > [KC>] Unfortunately, here you are making your argument based on some
> > rumor that you heard about real SDO requirements. Please use
official
> > liaison channels to confirm SDO requirements before posting comments
> on
> > the mailing list.
> >
> > jak>> OK. Would any of our liasons like to comment on this? Is the
> system
> > architecture described in the integrated draft what your SDO is
> planning
> > on
> > standardizing?
> >
> > > So, if you want to go down this path, we will end up making both
the
> > > documents informational. If not both of them should remain
standards
> > > track.
> > >
> > > jak>> We're not discussing the split draft here. If you want to
> > propose
> > > changing it, then start a separate thread.
> > >
> > [KC>] We need to discuss how useful the split scenario draft is.
Also
> to
> > be fair, we need to make a decision about informational vs.
standards
> > track suitability for _both_ the documents if that's what the WG
ends
> up
> > deciding. That's what I meant to say here.
> >
> > jak>> Then why didn't you start a separate thread on it? This is
basic
> > IETF
> > courtesy. Kuntal, you've been around IETF long enough to know these
> kinds
> > of
> > things.
> >
> [KC>] OK, I apologize for raising the issues with the split solutions
> I-D late in the game. James, you did not raise all the issues that you
> had with the integrated I-D until now. You have been around in IETF
more
> than I have been....
>=20
>=20
> >             jak
> >
>=20
>=20
> "This email message and any attachments are confidential information
of
> Starent Networks, Corp. The information transmitted may not be used to
> create or change any contractual obligations of Starent Networks,
Corp.
> Any review, retransmission, dissemination or other use of, or taking
of
> any action in reliance upon this e-mail and its attachments by persons
or
> entities other than the intended recipient is prohibited. If you are
not
> the intended recipient, please notify the sender immediately -- by
> replying to this message or by sending an email to
> postmaster@starentnetworks.com -- and destroy all copies of this
message
> and any attachments without reading or disclosing their contents.
Thank
> you."
>=20
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6

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



From mip6-bounces@ietf.org Tue Aug 22 20:20:15 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GFgTL-0000d0-Vi; Tue, 22 Aug 2006 20:19:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GFgTK-0000Xh-Em
	for mip6@ietf.org; Tue, 22 Aug 2006 20:19:54 -0400
Received: from mx0.starentnetworks.com ([12.38.223.203])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GFgTH-0003Sx-L1
	for mip6@ietf.org; Tue, 22 Aug 2006 20:19:54 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mx0.starentnetworks.com (Postfix) with ESMTP id B8CFA9001C;
	Tue, 22 Aug 2006 20:19:47 -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 14762-04; Tue, 22 Aug 2006 20:19:46 -0400 (EDT)
Received: from exchtewks1.starentnetworks.com (exchtewks1.starentnetworks.com
	[12.33.233.52]) by mx0.starentnetworks.com (Postfix) with ESMTP;
	Tue, 22 Aug 2006 20:19:46 -0400 (EDT)
X-MessageTextProcessor: DisclaimIt (2.70.271) [Starent Networks Corp.]
Received: from exchtewks2.starentnetworks.com ([12.33.232.12]) by
	exchtewks1.starentnetworks.com with Microsoft
	SMTPSVC(6.0.3790.1830); Tue, 22 Aug 2006 20:19:46 -0400
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Kuntal's comments on the split document (was: Re:
	[Mip6]Conclusion of the consensus call relatedtothebootstrapping I-Ds)
Date: Tue, 22 Aug 2006 20:19:45 -0400
Message-ID: <7CCD07160348804497EF29E9EA5560D7837249@exchtewks2.starentnetworks.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Kuntal's comments on the split document (was: Re:
	[Mip6]Conclusion of the consensus call
	relatedtothebootstrapping I-Ds)
thread-index: AcbGKsWswIBJQvnATwWWa3sXWWdnegAAqf/wAARS70AAAh+ZQA==
From: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
To: "Tsirtsis, George" <tsirtsis@qualcomm.com>,
	"James Kempf" <kempf@docomolabs-usa.com>,
	"Alper Yegin" <alper.yegin@yegin.org>,
	"Basavaraj Patil" <basavaraj.patil@nokia.com>, <mip6@ietf.org>
Importance: normal
Priority: normal
X-OriginalArrivalTime: 23 Aug 2006 00:19:46.0263 (UTC)
	FILETIME=[D6A41E70:01C6C649]
X-Virus-Scanned: amavisd-new 2.2.1 (20041222) at mx0.starentnetworks.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 918f4bd8440e8de4700bcf6d658bc801
Cc: 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

I think there needs to be ways described in IETF documents for each
scenario. Otherwise, the SDOs will have,

1. No clue what to do, or
2. Will have clue, but each one will invent new ways

We should at least try to avoid that situation.

-Kuntal


> -----Original Message-----
> From: Tsirtsis, George [mailto:tsirtsis@qualcomm.com]
> Sent: Tuesday, August 22, 2006 6:16 PM
> To: Chowdhury, Kuntal; James Kempf; Alper Yegin; Basavaraj Patil;
> mip6@ietf.org
> Subject: RE: Kuntal's comments on the split document (was: Re:
> [Mip6]Conclusion of the consensus call relatedtothebootstrapping I-Ds)
>=20
> I have not followed this discussion from the beginning so my apologies
> if this has been discussed before.
>=20
> IMHO, the problem with both the split and integrated documents is that
> they are more system design documents than protocol specifications.
>=20
> I think the WG correctly decided to standardize the DHCP-option of the
> integrated document separately since this is the protocol part.
> The rest of the document defines a way to use the DHCP-option together
> with other IETF "tools" to build a system. The split document does the
> same thing so, if there is a protocol extension to be standardized
> (e.g., DNS Update mobility option) it needs to be taken out and be
> standardized.
>=20
[KC>] Agree, only if _both_ the documents are made informational.

> Let me remind everyone that the IETF does not build
> systems/architectures unless absolutely necessary and in this case it
is
> not necessary since one can come up with many different ways of using
> several IETF protocols to bootstrap MIP, all of which are valid.
>=20
[KC>] We should avoid this if possible. No one benefits from a
fragmented solution space. So, a solution description in an IETF
document is the correct way to go.

> The "system description" parts of the split/integrated documents can
> then become whatever; it does not really matter since the notion of
> "standards track" in the IETF does not apply to systems. As far as I
am
> concerned, if they need to be standardized at all, they need to be
> standardized in an SDO otherwise informational or BCP can work too.
>=20
[KC>] There are some exceptions where a framework document in IETF is
also standards track. I don't agree that how to knit the pieces of the
puzzle together should be left entirely to the SDOs.=20

> Regards
> George
>=20
> > -----Original Message-----
> > From: Chowdhury, Kuntal [mailto:kchowdhury@starentnetworks.com]
> > Sent: Tuesday, August 22, 2006 6:27 PM
> > To: James Kempf; Alper Yegin; Basavaraj Patil; mip6@ietf.org
> > Subject: RE: Kuntal's comments on the split document (was: Re:
> > [Mip6]Conclusion of the consensus call relatedtothebootstrapping
I-Ds)
> >
> >
> >
> > > -----Original Message-----
> > > From: James Kempf [mailto:kempf@docomolabs-usa.com]
> > > Sent: Tuesday, August 22, 2006 3:37 PM
> > > To: Chowdhury, Kuntal; Alper Yegin; Basavaraj Patil; mip6@ietf.org
> > > Subject: Kuntal's comments on the split document (was: Re: [Mip6]
> > > Conclusion of the consensus call relatedtothebootstrapping I-Ds)
> > >
> > > Alright. If you want to discuss the split document then let's do
it
> > (note
> > > change in thread header).
> > >
> > > [KC>] Which part of my statement you found to be "emotional"? Is
it
> > the
> > > "rather useless" part? In my opinion, the split scenario solution
> > > document has some things that are totally out of scope of mip6
> > > bootstrapping (e.g. the dynamic DNS update). Moreover, the HA
> > > bootstrapping is based on DNS query which has security issues.
> Anybody
> > > in the public internet can discover operator's HAs. This is a
> security
> > > hole that the split solution introduces. These are NOT emotional
> > > statements :-). I am just expressing how I feel about the split
> > solution
> > > document, that's all.
> > >
> > > jak>> These are your opinions, and I would say they are rather
> > emotionally
> > > expressed (my opinion, of course).
> > >
> > > jak>> The goals of the split document are different from the
> > intergrated
> > > document. The split document is primarily for enterprises and for
> > > businesses
> > > that have as their primary business providing mobility service
only
> > (hence
> > > the name). Since such businesses are new, they are likely to be
> > > entrepreneurial. They're not going to have the time or resources
to
> > run
> > > around to various different SDOs and try to force their solutions
to
> > get
> > > locked into the standards. The split solution is designed to
provide
> > them
> > > with interoperability. It is possible for integrated wireless
> service
> > > providers to use the split solution, of course, possibly as an
> > additional
> > > revenue generator for providing mobility service to customers that
> use
> > a
> > > different access network provider.
> > >
> > [KC>] What you describe above is the scope of the split document.
The
> > scope is unique, understood. But that does not automatically justify
a
> > standards track RFC for the solution document. What we have is a
split
> > scenario solution framework document _using_ IKEv2, DNS etc. So, are
> you
> > OK to make the split solution I-D an informational RFC?
> >
> > > jak>> Regarding the security issues of DNS, we've been through
this
> > issue
> > > a
> > > number of times, the draft was reviewed by SAAG (we have yet to
> > respond)
> > > and
> > > there was nothing said about it, so I am puzzled why you are
raising
> > this
> > > canard again. We recently had a good (and I might add
nonemotional)
> > > discussion on this list about using anycast, initiated by
> Jean-Marie,
> > and
> > > I've drafted some text up that will allow anycast addresses to be
> used
> > in
> > > DNS SRV RRs instead of the unicast addresses of the HAs, based on
> > > Francis's
> > > draft, and sent the text to Gerardo (he's on vacation at the
> moment).
> > This
> > > should provide some moderate protection from DoS, but it will not
> > protect
> > > completely, just as the DHCP solution won't. As I've pointed out
in
> > the
> > > past, as soon as you release the address of a server to an end
host,
> > > regardless of how it is done, all bets are off. What the end host
> does
> > > with
> > > that address is completely out of your control, and if the end
host
> is
> > > infected with malware, you can be sure somebody's botnet will get
> the
> > > address. Or are you proposing some enhancement to the DHCP based
> > solution
> > > that will make it impossible for malware to grab a home agent's
> > address?
> > >
> > [KC>] There is a clear difference between the way HA address is
> > discovered in the split solution and in the integrated solution. The
> HA
> > address is _assigned_ to the MN in the integrated solution by the
Home
> > AAA server. This ONLY happens once the MN passes authentication. So,
> the
> > chances of giving away the HA address to totally unknown entities in
> > this case is next to none. In case of split scenario, the HAs are
> > totally exposed to anyone with good or bad intention. Anyone with an
> IP
> > connection can send DNS queries to get any MSP's HA addresses and
then
> > launch DoS attacks from his/her basement.
> >
> > It is true that once the HA address is given to an entity, if that
> > entity is compromised, the HA address can get out to some bad guys.
> But
> > it is not likely to happen too often. This type of security threat
is
> > generic and not specific to mip6 bootstrapping, IMHO. If the
> > entity/device is compromised, other things like root-key, username,
> any
> > other cached data will also be revealed. So, it is a generic issue.
> >
> > In case of split scenario, the risk of giving away the HA address to
> bad
> > guys is always there. So, the solution doesn't seem to be deployable
> in
> > public wireless networks.
> >
> > > > HL prefix etc. Integrated scenario is likely to be widely
> deployed,
> > > > where as the split scenario doesn't even have any buyer.
> > > >
> > > > jak>> I think you mean draft-jang will be widely deployed. As I
> > recall
> > > > someone posted email a while back saying that there was no plan
by
> > any
> > > > other
> > > > SDO to adopt the integrated draft as is, just the two draft-jang
> > DHCP
> > > > enhancements.
> > > >
> > > [KC>] Unfortunately, here you are making your argument based on
some
> > > rumor that you heard about real SDO requirements. Please use
> official
> > > liaison channels to confirm SDO requirements before posting
comments
> > on
> > > the mailing list.
> > >
> > > jak>> OK. Would any of our liasons like to comment on this? Is the
> > system
> > > architecture described in the integrated draft what your SDO is
> > planning
> > > on
> > > standardizing?
> > >
> > > > So, if you want to go down this path, we will end up making both
> the
> > > > documents informational. If not both of them should remain
> standards
> > > > track.
> > > >
> > > > jak>> We're not discussing the split draft here. If you want to
> > > propose
> > > > changing it, then start a separate thread.
> > > >
> > > [KC>] We need to discuss how useful the split scenario draft is.
> Also
> > to
> > > be fair, we need to make a decision about informational vs.
> standards
> > > track suitability for _both_ the documents if that's what the WG
> ends
> > up
> > > deciding. That's what I meant to say here.
> > >
> > > jak>> Then why didn't you start a separate thread on it? This is
> basic
> > > IETF
> > > courtesy. Kuntal, you've been around IETF long enough to know
these
> > kinds
> > > of
> > > things.
> > >
> > [KC>] OK, I apologize for raising the issues with the split
solutions
> > I-D late in the game. James, you did not raise all the issues that
you
> > had with the integrated I-D until now. You have been around in IETF
> more
> > than I have been....
> >
> >
> > >             jak
> > >
> >
> >
> > "This email message and any attachments are confidential information
> of
> > Starent Networks, Corp. The information transmitted may not be used
to
> > create or change any contractual obligations of Starent Networks,
> Corp.
> > Any review, retransmission, dissemination or other use of, or taking
> of
> > any action in reliance upon this e-mail and its attachments by
persons
> or
> > entities other than the intended recipient is prohibited. If you are
> not
> > the intended recipient, please notify the sender immediately -- by
> > replying to this message or by sending an email to
> > postmaster@starentnetworks.com -- and destroy all copies of this
> message
> > and any attachments without reading or disclosing their contents.
> Thank
> > you."
> >
> > _______________________________________________
> > Mip6 mailing list
> > Mip6@ietf.org
> > https://www1.ietf.org/mailman/listinfo/mip6

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



From mip6-bounces@ietf.org Wed Aug 23 04:24:49 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GFo1n-0005mr-17; Wed, 23 Aug 2006 04:23:59 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GFo1m-0005mi-9z
	for mip6@ietf.org; Wed, 23 Aug 2006 04:23:58 -0400
Received: from mail1.azairenet.com ([66.92.223.4] helo=bart.corp.azairenet.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GFo1l-00064G-02
	for mip6@ietf.org; Wed, 23 Aug 2006 04:23:58 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] Conclusion of the consensus call related to
	thebootstrapping I-Ds
Date: Wed, 23 Aug 2006 01:23:54 -0700
Message-ID: <C8E1D942CB394746BE5CFEB7D97610E70169AA79@bart.corp.azairenet.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] Conclusion of the consensus call related to
	thebootstrapping I-Ds
thread-index: AcbGHxhDVv4XVDISEduldAARJNUNiAAbW6uu
From: "Vijay Devarapalli" <Vijay.Devarapalli@AzaireNet.com>
To: "Basavaraj Patil" <basavaraj.patil@nokia.com>,
	"ext James Kempf" <kempf@docomolabs-usa.com>,
	"Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>,
	"Alper Yegin" <alper.yegin@yegin.org>, <mip6@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Cc: 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org


hi Raj,

I was under the impression that some SDOs only
have a dependency on the DHCP options in draft-jang.
not the current WG document based on DHCP for=20
the integrated scenario. perhaps it would be good
to figure out what exactly the SDOs want for DHCP
based MIP6 bootstrapping.

Vijay

-----Original Message-----
From: Basavaraj Patil [mailto:basavaraj.patil@nokia.com]
Sent: Tue 8/22/2006 12:13 PM
To: ext James Kempf; Chowdhury, Kuntal; Alper Yegin; mip6@ietf.org
Subject: Re: [Mip6] Conclusion of the consensus call related to =
thebootstrapping I-Ds
=20

Having spent a few months on deliberating how DHCP options required for
bootstrapping be specified, lets not go back in time and start =
discussing if
the intergrated scenarios I-D is necessary or not.

When the design team was formed, the conclusion after the completion of =
the
split scenarios I-D was that a solution for the integrated scenario is
needed as well and hence the creation of the WG I-D.

I have also been told by 3GPP2 (liaison) that they have a dependency on =
the
integrated scenarios I-D.

Hence I would recommend that we stop this discussion and lets work on
completing the bootstrap solutions work.

-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 Wed Aug 23 05:51:16 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GFpNg-0001mR-2W; Wed, 23 Aug 2006 05:50:40 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GFpNd-0001mJ-Vh
	for mip6@ietf.org; Wed, 23 Aug 2006 05:50:37 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GFnyc-000563-VO
	for mip6@ietf.org; Wed, 23 Aug 2006 04:20:43 -0400
Received: from ithilien.qualcomm.com ([129.46.51.59])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1GFnr5-00011Y-Ho
	for mip6@ietf.org; Wed, 23 Aug 2006 04:12:58 -0400
Received: from neophyte.qualcomm.com (neophyte.qualcomm.com [129.46.61.149])
	by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k7N8Chfs011542
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Wed, 23 Aug 2006 01:12:44 -0700
Received: from NAEXBR03.na.qualcomm.com (naexbr03.qualcomm.com
	[129.46.134.172])
	by neophyte.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	k7N8CepE016427; Wed, 23 Aug 2006 01:12:43 -0700 (PDT)
Received: from NAEX13.na.qualcomm.com ([129.46.51.248]) by
	NAEXBR03.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 23 Aug 2006 01:12:40 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] Conclusion of the consensus call related to
	thebootstrapping I-Ds
Date: Wed, 23 Aug 2006 01:12:39 -0700
Message-ID: <C24CB51D5AA800449982D9BCB903251311ABCD@NAEX13.na.qualcomm.com>
In-Reply-To: <0cc401c6c631$8ed3cc20$636015ac@dcml.docomolabsusa.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] Conclusion of the consensus call related to
	thebootstrapping I-Ds
Thread-Index: AcbGNCWWF9rh49uETxelkBvn/lB2igAVWgTQ
From: "Narayanan, Vidya" <vidyan@qualcomm.com>
To: "James Kempf" <kempf@docomolabs-usa.com>,
	"Basavaraj Patil" <basavaraj.patil@nokia.com>,
	"Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>,
	"Alper Yegin" <alper.yegin@yegin.org>, <mip6@ietf.org>
X-OriginalArrivalTime: 23 Aug 2006 08:12:40.0226 (UTC)
	FILETIME=[E6D74820:01C6C68B]
X-Spam-Score: -2.5 (--)
X-Scan-Signature: 5ebbf074524e58e662bc8209a6235027
Cc: 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org


I have asked the 3gpp2 liaison to respond. In the meantime, here is my
take on this whole thread of emails:

Pending confirmation from the liaison, I believe that 3gpp2 plans to use
DHCP as the means of discovering the HA. Further, the plan is to use
IKEv2 to obtain a HoA.=20

I don't really have an opinion on what track each of these documents get
published under or whether they are separate or not. I stated a
preference during the consensus call and that's that.=20

In my personal opinion, DHCP, as envisioned as being used to discover
HAs, is rather specific to certain scenarios and is not generically
applicable. The DNS-based solution is the more generic model that is
universally applicable. And, FWIW, I don't quite buy the security
problem with the DNS approach. If a provider is hosting a service such
as Mobile IP, the servers (i.e., home agents) must be globally reachable
or there is no service at that point. Even with the DHCP-based
mechanism, any attacker will happily learn the HA IP address in BUs and
BAs that are exchanged even if the argument is that the HA IP address is
given out in DHCP only to authenticated clients. Paranoid network
deployments better use DNSSEC to hand out addresses, preprovision IPsec
keys between the MN and HA, encrypt the BU/BAs using the preprovisioned
keys and subsequently use tunnel mode IPsec with a gateway to which they
are comfortable providing global reachability for data packets!=20

It's at the end of a long day, but I think if you did all of the above,
it may be difficult for an attacker to learn the HA IP address :)=20

My 2 cents,
Vidya

> -----Original Message-----
> From: James Kempf [mailto:kempf@docomolabs-usa.com]=20
> Sent: Tuesday, August 22, 2006 2:26 PM
> To: Basavaraj Patil; Chowdhury, Kuntal; Alper Yegin; mip6@ietf.org
> Subject: Re: [Mip6] Conclusion of the consensus call related=20
> to thebootstrapping I-Ds
>=20
> Raj,
>=20
> > Stepping back from the specifics of the documents that we=20
> have today=20
> > in the WG w.r.t bootstrapping, I believe what the WG is chartered=20
> > (which needs to be updated BTW), is to develop a solution=20
> or solutions=20
> > for bootstrapping MIP6. I think we disccovered fairly early on that=20
> > one bootstrapping solution does not fit all environments.=20
> We are now=20
> > even considering adopting Vijay's draft which specifies=20
> bootstrapping=20
> > in the case of the use of the authenication protocol. But=20
> that's not=20
> > the point here.
> >
> > The WG direction is to develop a set of bootstrapping=20
> solutions that=20
> > can be used in various deployment scenarios. The scenarios that we=20
> > have specified in the WG today are based on the use of IKE for=20
> > bootstrapping for the cases that we call split and integrated. The=20
> > issue about whether the DHCP options should be specified within the=20
> > integrated scenarios document or separately is simply a=20
> matter of how=20
> > we split the documents.
> > Consensus was that keeping the DHCP options is preferred because of=20
> > various reasons (as has been discussed at length).
> >
> > My recommendation is that we move forward with the set of existing=20
> > I-Ds which include the problem statement, Split scenario,=20
> Integrated=20
> > scenario, and DHCPv6 options.
> >
>=20
> As you know, I was not in favor of splitting off the DHCPv6=20
> options into separate documents. However, since it seems like=20
> that is what the WG wants, I was just trying to get an idea=20
> of whether that should apply to the relay to server options=20
> too. As I mentioned to Kuntal, I think this would make a=20
> certain amount of sense from an organizational standpoint=20
> (protocol mods in separate, small PS documents, system=20
> architecture in larger Informational
> document) which is what I thought Alper was trying to=20
> achieve. I frankly don't care much either way.
>=20
> Does anybody else in the WG have an opinion on this?
>=20
>=20
> > W.r.t what 3GPP2 really wants from the integrated scenarios I-D, I=20
> > believe they require the IKE based bootstrapping solution=20
> for MIP6 and=20
> > not just the DHCP options.
> >
>=20
> Then they will need to refer to something more than the=20
> integrated document.=20
> The IKEv2 bootstrapping is specified in the split document, not the=20
> integrated document.
>=20
> Maybe we need the 3GPP2 liason to step forward and say what=20
> 3GPP2 wants, or=20
> is the liason you?
>=20
>             jak
>=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 Aug 23 07:24:00 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GFqpt-0007qt-I0; Wed, 23 Aug 2006 07:23:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GFqps-0007qo-FL
	for mip6@ietf.org; Wed, 23 Aug 2006 07:23:52 -0400
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GFqpr-0002oE-VR
	for mip6@ietf.org; Wed, 23 Aug 2006 07:23:52 -0400
Received: from crowley.qualcomm.com (crowley.qualcomm.com [129.46.61.151])
	by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k7NBN2Eg012410
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Wed, 23 Aug 2006 04:23:03 -0700
Received: from NAEXBR03.na.qualcomm.com (naexbr03.qualcomm.com
	[129.46.134.172])
	by crowley.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	k7NBN1xX002021; Wed, 23 Aug 2006 04:23:01 -0700 (PDT)
Received: from NAEX14.na.qualcomm.com ([10.47.5.242]) by
	NAEXBR03.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 23 Aug 2006 04:23:00 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] Conclusion of the consensus call related
	tothebootstrapping I-Ds
Date: Wed, 23 Aug 2006 04:23:01 -0700
Message-ID: <7EB20EA0938B4D42A2D82689365C9B7A11DC04@NAEX14.na.qualcomm.com>
In-Reply-To: <C24CB51D5AA800449982D9BCB903251311ABCD@NAEX13.na.qualcomm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] Conclusion of the consensus call related
	tothebootstrapping I-Ds
Thread-Index: AcbGNCWWF9rh49uETxelkBvn/lB2igAVWgTQAAbIu+A=
From: "Tsirtsis, George" <tsirtsis@qualcomm.com>
To: "Narayanan, Vidya" <vidyan@qualcomm.com>,
	"James Kempf" <kempf@docomolabs-usa.com>,
	"Basavaraj Patil" <basavaraj.patil@nokia.com>,
	"Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>,
	"Alper Yegin" <alper.yegin@yegin.org>, <mip6@ietf.org>
X-OriginalArrivalTime: 23 Aug 2006 11:23:00.0875 (UTC)
	FILETIME=[7E1405B0:01C6C6A6]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3971661e40967acfc35f708dd5f33760
Cc: 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

I agree that the security problems with DNS are not relevant but for
slightly different reasons. HAs are globally reachable entities. The
DHCP approach provides some obscurity by the fact that the system can be
made to work so that the DHCP server only talks to authenticated (i.e.,
known) entities. Obscurity, however, is not security. If attacking HAs
is a good attack the IP addresses of such HAs will be on the "hacker's
weekly" web site in no time.

In the Internet, major infrastructure equipment are always going to be
somewhat vulnerable, which is why we do generally avoid them and instead
we distribute functions. Until routing can deal with mobility, however,
we will have to have HAs, oh well :-)

George


> -----Original Message-----
> From: Narayanan, Vidya [mailto:vidyan@qualcomm.com]
> Sent: Wednesday, August 23, 2006 4:13 AM
> To: James Kempf; Basavaraj Patil; Chowdhury, Kuntal; Alper Yegin;
> mip6@ietf.org
> Subject: RE: [Mip6] Conclusion of the consensus call related
> tothebootstrapping I-Ds
>=20
>=20
> I have asked the 3gpp2 liaison to respond. In the meantime, here is my
> take on this whole thread of emails:
>=20
> Pending confirmation from the liaison, I believe that 3gpp2 plans to
use
> DHCP as the means of discovering the HA. Further, the plan is to use
> IKEv2 to obtain a HoA.
>=20
> I don't really have an opinion on what track each of these documents
get
> published under or whether they are separate or not. I stated a
> preference during the consensus call and that's that.
>=20
> In my personal opinion, DHCP, as envisioned as being used to discover
> HAs, is rather specific to certain scenarios and is not generically
> applicable. The DNS-based solution is the more generic model that is
> universally applicable. And, FWIW, I don't quite buy the security
> problem with the DNS approach. If a provider is hosting a service such
> as Mobile IP, the servers (i.e., home agents) must be globally
reachable
> or there is no service at that point. Even with the DHCP-based
> mechanism, any attacker will happily learn the HA IP address in BUs
and
> BAs that are exchanged even if the argument is that the HA IP address
is
> given out in DHCP only to authenticated clients. Paranoid network
> deployments better use DNSSEC to hand out addresses, preprovision
IPsec
> keys between the MN and HA, encrypt the BU/BAs using the
preprovisioned
> keys and subsequently use tunnel mode IPsec with a gateway to which
they
> are comfortable providing global reachability for data packets!
>=20
> It's at the end of a long day, but I think if you did all of the
above,
> it may be difficult for an attacker to learn the HA IP address :)
>=20
> My 2 cents,
> Vidya
>=20
> > -----Original Message-----
> > From: James Kempf [mailto:kempf@docomolabs-usa.com]
> > Sent: Tuesday, August 22, 2006 2:26 PM
> > To: Basavaraj Patil; Chowdhury, Kuntal; Alper Yegin; mip6@ietf.org
> > Subject: Re: [Mip6] Conclusion of the consensus call related
> > to thebootstrapping I-Ds
> >
> > Raj,
> >
> > > Stepping back from the specifics of the documents that we
> > have today
> > > in the WG w.r.t bootstrapping, I believe what the WG is chartered
> > > (which needs to be updated BTW), is to develop a solution
> > or solutions
> > > for bootstrapping MIP6. I think we disccovered fairly early on
that
> > > one bootstrapping solution does not fit all environments.
> > We are now
> > > even considering adopting Vijay's draft which specifies
> > bootstrapping
> > > in the case of the use of the authenication protocol. But
> > that's not
> > > the point here.
> > >
> > > The WG direction is to develop a set of bootstrapping
> > solutions that
> > > can be used in various deployment scenarios. The scenarios that we
> > > have specified in the WG today are based on the use of IKE for
> > > bootstrapping for the cases that we call split and integrated. The
> > > issue about whether the DHCP options should be specified within
the
> > > integrated scenarios document or separately is simply a
> > matter of how
> > > we split the documents.
> > > Consensus was that keeping the DHCP options is preferred because
of
> > > various reasons (as has been discussed at length).
> > >
> > > My recommendation is that we move forward with the set of existing
> > > I-Ds which include the problem statement, Split scenario,
> > Integrated
> > > scenario, and DHCPv6 options.
> > >
> >
> > As you know, I was not in favor of splitting off the DHCPv6
> > options into separate documents. However, since it seems like
> > that is what the WG wants, I was just trying to get an idea
> > of whether that should apply to the relay to server options
> > too. As I mentioned to Kuntal, I think this would make a
> > certain amount of sense from an organizational standpoint
> > (protocol mods in separate, small PS documents, system
> > architecture in larger Informational
> > document) which is what I thought Alper was trying to
> > achieve. I frankly don't care much either way.
> >
> > Does anybody else in the WG have an opinion on this?
> >
> >
> > > W.r.t what 3GPP2 really wants from the integrated scenarios I-D, I
> > > believe they require the IKE based bootstrapping solution
> > for MIP6 and
> > > not just the DHCP options.
> > >
> >
> > Then they will need to refer to something more than the
> > integrated document.
> > The IKEv2 bootstrapping is specified in the split document, not the
> > integrated document.
> >
> > Maybe we need the 3GPP2 liason to step forward and say what
> > 3GPP2 wants, or
> > is the liason you?
> >
> >             jak
> >
> >
> >
> >
> > _______________________________________________
> > 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

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



From mip6-bounces@ietf.org Wed Aug 23 09:31:28 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GFsoy-0006N2-Q5; Wed, 23 Aug 2006 09:31:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GFsow-0006IX-PT
	for mip6@ietf.org; Wed, 23 Aug 2006 09:31:02 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GFsow-00043X-MV
	for mip6@ietf.org; Wed, 23 Aug 2006 09:31:02 -0400
Received: from py-out-1112.google.com ([64.233.166.179])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1GFsm9-0001t9-Jl
	for mip6@ietf.org; Wed, 23 Aug 2006 09:28:12 -0400
Received: by py-out-1112.google.com with SMTP id z59so157215pyg
	for <mip6@ietf.org>; Wed, 23 Aug 2006 06:28:08 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=MG9EEx0DssD0Rt7wDOLk6BRScRUNj71BT4cnyiJWd2QdMU9AuwaWhfn+KZtmFisEUEGDjcKfOhJNVvJVkc2nEDEzxT+EkNknmkmaQ5v5MVXcrSu8aMhrxVeQOmb750OOT5WgwWxyEwoIT5HsTIVVL3fd2ywOdNCnQsYsnEKMd84=
Received: by 10.35.66.12 with SMTP id t12mr612186pyk;
	Wed, 23 Aug 2006 06:28:08 -0700 (PDT)
Received: by 10.35.83.13 with HTTP; Wed, 23 Aug 2006 06:28:08 -0700 (PDT)
Message-ID: <729b68be0608230628o1f5d4e72o874404fd120845eb@mail.gmail.com>
Date: Wed, 23 Aug 2006 15:28:08 +0200
From: "Jean-Michel Combes" <jeanmichel.combes@gmail.com>
To: "Tsirtsis, George" <tsirtsis@qualcomm.com>
Subject: Re: [Mip6] Conclusion of the consensus call related
	tothebootstrapping I-Ds
In-Reply-To: <7EB20EA0938B4D42A2D82689365C9B7A11DC04@NAEX14.na.qualcomm.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <C24CB51D5AA800449982D9BCB903251311ABCD@NAEX13.na.qualcomm.com>
	<7EB20EA0938B4D42A2D82689365C9B7A11DC04@NAEX14.na.qualcomm.com>
X-Spam-Score: -2.5 (--)
X-Scan-Signature: 8b6657e60309a1317174c9db2ae5f227
Cc: Basavaraj Patil <basavaraj.patil@nokia.com>, mip6@ietf.org,
	James Kempf <kempf@docomolabs-usa.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi,

At first, I have the strange feeling that this thread is going out of
scope from the initial subject :s
There is an old thread where security regarding HA
discovery/assignment was debated: "New charter item: HA assignment"
(http://www1.ietf.org/mail-archive/web/mip6/current/msg04859.html).

2006/8/23, Tsirtsis, George <tsirtsis@qualcomm.com>:
> I agree that the security problems with DNS are not relevant but for
> slightly different reasons. HAs are globally reachable entities.

Don't agree. Depends who wants to reach it.

> The
> DHCP approach provides some obscurity by the fact that the system can be
> made to work so that the DHCP server only talks to authenticated (i.e.,
> known) entities. Obscurity, however, is not security.

Agree :)

> If attacking HAs
> is a good attack the IP addresses of such HAs will be on the "hacker's
> weekly" web site in no time.

HA are the point of fealure for IPv6 mobility protocols (MIPv6 and
furthermore NEMO). Trying to give the minimum of information can limit
the attacks.

>
> In the Internet, major infrastructure equipment are always going to be
> somewhat vulnerable, which is why we do generally avoid them and instead
> we distribute functions. Until routing can deal with mobility, however,
> we will have to have HAs, oh well :-)
>
> George
>
>
> > -----Original Message-----
> > From: Narayanan, Vidya [mailto:vidyan@qualcomm.com]
> > Sent: Wednesday, August 23, 2006 4:13 AM
> > To: James Kempf; Basavaraj Patil; Chowdhury, Kuntal; Alper Yegin;
> > mip6@ietf.org
> > Subject: RE: [Mip6] Conclusion of the consensus call related
> > tothebootstrapping I-Ds
> >
> >
> > I have asked the 3gpp2 liaison to respond. In the meantime, here is my
> > take on this whole thread of emails:
> >
> > Pending confirmation from the liaison, I believe that 3gpp2 plans to
> use
> > DHCP as the means of discovering the HA. Further, the plan is to use
> > IKEv2 to obtain a HoA.
> >
> > I don't really have an opinion on what track each of these documents
> get
> > published under or whether they are separate or not. I stated a
> > preference during the consensus call and that's that.
> >
> > In my personal opinion, DHCP, as envisioned as being used to discover
> > HAs, is rather specific to certain scenarios and is not generically
> > applicable. The DNS-based solution is the more generic model that is
> > universally applicable. And, FWIW, I don't quite buy the security
> > problem with the DNS approach. If a provider is hosting a service such
> > as Mobile IP, the servers (i.e., home agents) must be globally
> reachable

Don't agree: cf. the thread I mentionned before.

> > or there is no service at that point. Even with the DHCP-based
> > mechanism, any attacker will happily learn the HA IP address in BUs
> and
> > BAs that are exchanged even if the argument is that the HA IP address
> is
> > given out in DHCP only to authenticated clients. Paranoid network
> > deployments better use DNSSEC to hand out addresses

In theory, DNSSEC may be used. Not in practical.

>> , preprovision
> IPsec
> > keys between the MN and HA, encrypt the BU/BAs using the
> preprovisioned
> > keys
>> and subsequently use tunnel mode IPsec with a gateway to which
> they
> > are comfortable providing global reachability for data packets!
> >
> > It's at the end of a long day, but I think if you did all of the
> above,
> > it may be difficult for an attacker to learn the HA IP address :)

The goal is not that an attacker may be able to learn one HA IP
address but that an attacker learns _all_ the HAs IP addresses from
one MSP.

Best regards.

JMC.

> >
> > My 2 cents,
> > Vidya
> >
> > > -----Original Message-----
> > > From: James Kempf [mailto:kempf@docomolabs-usa.com]
> > > Sent: Tuesday, August 22, 2006 2:26 PM
> > > To: Basavaraj Patil; Chowdhury, Kuntal; Alper Yegin; mip6@ietf.org
> > > Subject: Re: [Mip6] Conclusion of the consensus call related
> > > to thebootstrapping I-Ds
> > >
> > > Raj,
> > >
> > > > Stepping back from the specifics of the documents that we
> > > have today
> > > > in the WG w.r.t bootstrapping, I believe what the WG is chartered
> > > > (which needs to be updated BTW), is to develop a solution
> > > or solutions
> > > > for bootstrapping MIP6. I think we disccovered fairly early on
> that
> > > > one bootstrapping solution does not fit all environments.
> > > We are now
> > > > even considering adopting Vijay's draft which specifies
> > > bootstrapping
> > > > in the case of the use of the authenication protocol. But
> > > that's not
> > > > the point here.
> > > >
> > > > The WG direction is to develop a set of bootstrapping
> > > solutions that
> > > > can be used in various deployment scenarios. The scenarios that we
> > > > have specified in the WG today are based on the use of IKE for
> > > > bootstrapping for the cases that we call split and integrated. The
> > > > issue about whether the DHCP options should be specified within
> the
> > > > integrated scenarios document or separately is simply a
> > > matter of how
> > > > we split the documents.
> > > > Consensus was that keeping the DHCP options is preferred because
> of
> > > > various reasons (as has been discussed at length).
> > > >
> > > > My recommendation is that we move forward with the set of existing
> > > > I-Ds which include the problem statement, Split scenario,
> > > Integrated
> > > > scenario, and DHCPv6 options.
> > > >
> > >
> > > As you know, I was not in favor of splitting off the DHCPv6
> > > options into separate documents. However, since it seems like
> > > that is what the WG wants, I was just trying to get an idea
> > > of whether that should apply to the relay to server options
> > > too. As I mentioned to Kuntal, I think this would make a
> > > certain amount of sense from an organizational standpoint
> > > (protocol mods in separate, small PS documents, system
> > > architecture in larger Informational
> > > document) which is what I thought Alper was trying to
> > > achieve. I frankly don't care much either way.
> > >
> > > Does anybody else in the WG have an opinion on this?
> > >
> > >
> > > > W.r.t what 3GPP2 really wants from the integrated scenarios I-D, I
> > > > believe they require the IKE based bootstrapping solution
> > > for MIP6 and
> > > > not just the DHCP options.
> > > >
> > >
> > > Then they will need to refer to something more than the
> > > integrated document.
> > > The IKEv2 bootstrapping is specified in the split document, not the
> > > integrated document.
> > >
> > > Maybe we need the 3GPP2 liason to step forward and say what
> > > 3GPP2 wants, or
> > > is the liason you?
> > >
> > >             jak
> > >
> > >
> > >
> > >
> > > _______________________________________________
> > > Mip6 mailing list
> > > Mip6@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/mip6
> > >
> >
> > _______________________________________________
> > Mip6 mailing list
> > Mip6@ietf.org
> > https://www1.ietf.org/mailman/listinfo/mip6
>
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
>

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



From mip6-bounces@ietf.org Wed Aug 23 13:12:16 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GFwGf-0008Ef-CX; Wed, 23 Aug 2006 13:11:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GFwGe-00084e-CN
	for mip6@ietf.org; Wed, 23 Aug 2006 13:11:52 -0400
Received: from key1.docomolabs-usa.com ([216.98.102.225]
	helo=fridge.docomolabs-usa.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GFw8L-0003Cv-0l
	for mip6@ietf.org; Wed, 23 Aug 2006 13:03:17 -0400
Message-ID: <030a01c6c6d6$05025de0$546015ac@dcml.docomolabsusa.com>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>,
	"Alper Yegin" <alper.yegin@yegin.org>,
	"Basavaraj Patil" <basavaraj.patil@nokia.com>, <mip6@ietf.org>
References: <7CCD07160348804497EF29E9EA5560D7837248@exchtewks2.starentnetworks.com>
Subject: Re: Kuntal's comments on the split document (was: Re: [Mip6]
	Conclusion of the consensus call relatedtothebootstrapping I-Ds)
Date: Wed, 23 Aug 2006 10:03:13 -0700
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: b132cb3ed2d4be2017585bf6859e1ede
Cc: 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

[KC>] What you describe above is the scope of the split document. The
scope is unique, understood. But that does not automatically justify a
standards track RFC for the solution document. What we have is a split
scenario solution framework document _using_ IKEv2, DNS etc. So, are you
OK to make the split solution I-D an informational RFC?

jak>> I think there is a difference in the documentation approach that the 
split document and the intergrated document have taken. From the beginning, 
the design team and authors have agreed that the split document should 
remain one unit, for ease of reference and implementation. The protocol 
enhancements described in Section 8 must be Standards Track, the rest of the 
material on system architecture is unique IETF architecture, and needs to be 
described in a Standard Track document for interoperability reasons. 
Documents are supposed to be Standards Track if their content is critical 
for interoperability.

jak>> On the other hand, the authors of the integrated document have argued 
from the beginning that it should be split up into in separate pieces, each 
an individual Standards Track document, with the various DHCP protocol 
enhancements in the pieces. If that is the case, why aren't the DHCP 
enhancements in Section 3.5 in a separate Standards Track document? It 
doesn't make any sense to me. Looking at it as a customer of the integrated 
solution, does it make sense to you?

jak>> Regarding the system architecture in the rest of the document,  I do 
question the wisdom of including system architecture from other SDO's 
standards in IETF Standards Track document, unless they conform closely to 
what is IETF architecture. Whose system architecture will be in the 
document, 3GPP, 3GPP2 or Wimax Forum? Are they all the same? Is IETF going 
to come up with something that is completely different from all three, and 
therefore is never really deployed in the form it is in the document? The 
other SDOs are going to use the DHCP options in their own system 
architectures, and these may or may not interoperate with each other, but 
the other SDOs don't need to care because their systems are only for their 
members. So I don't see such a pressing interoperability need for a 
Standards Track document for the integrated case.

 jak>> In the end, don't really care whether the integrated document is 
Standards Track or not, but I think a document philosophy should be applied 
consistently when a particular body of work is being documented in the IETF.

[KC>] There is a clear difference between the way HA address is
discovered in the split solution and in the integrated solution. The HA
address is _assigned_ to the MN in the integrated solution by the Home
AAA server. This ONLY happens once the MN passes authentication. So, the
chances of giving away the HA address to totally unknown entities in
this case is next to none. In case of split scenario, the HAs are
totally exposed to anyone with good or bad intention. Anyone with an IP
connection can send DNS queries to get any MSP's HA addresses and then
launch DoS attacks from his/her basement.

jak>> Kuntal, you've completely ignored what I said, and the basic design of 
the split protocol. What I said and what the protocol does is:

jak>> 1) In response to Jean-Marie's request, we're incorporating a means 
whereby the HA address can be assigned via an anycast intermediary. This 
reduces the ease by which an adversary can obtain the HA addresses, but it 
does not remove the threat of DoS attack due to malware, just as for the 
integrated case.
jak>> 2) In the split scenerio, authentication for MSP service is performed 
during the IKE transaction. It is like any other Web service, and is not 
integrated with network access authentication. This is a basic aspect of how 
the split scenerio works: the ASP and MSP are different service providers 
(or different services provided by the same company) and so they must be 
authenticated separately.

jak>> Please go back and read the protocol design document and problem 
statement before posting these kinds of baseless comments.

It is true that once the HA address is given to an entity, if that
entity is compromised, the HA address can get out to some bad guys. But
it is not likely to happen too often. This type of security threat is
generic and not specific to mip6 bootstrapping, IMHO. If the
entity/device is compromised, other things like root-key, username, any
other cached data will also be revealed. So, it is a generic issue.

In case of split scenario, the risk of giving away the HA address to bad
guys is always there. So, the solution doesn't seem to be deployable in
public wireless networks.

jak>> If you think this is "unlikely to happen often", let me send you the 
contents of my spam folder. Today I got email from the following people:

jak>> Cleo Lindsey, Suzanne Thibault, Jeff Orr, John Bourne, 
trader@kenora.net, ... and maybe another 100 or so additional offers from 
people I don't know and have no interest in having heard from.

jak>> Now, how did those people get my email address? Presumably all of 
these people were fully authenticated with their service providers, just as 
you claim would be the case in the integrated bootstrapping solution. Why 
are they sending me this email?

jak>> If you think that the various criminal groups who are sending spam 
aren't going to start harvesting home agent addresses and mounting DoS 
attacks on wireless service providers for blackmail I have a bridge I'd like 
to sell you.

jak>> You are right that it is a generic problem, but service providers have 
to deal with it regardless of the type of bootstrapping that is used. 
Asserting that DHCP provides any more or less protection is misleading. The 
threat must be mentioned in the Security Considerations section, and it is 
mentioned in the split scenerio Section 9.

>
[KC>] OK, I apologize for raising the issues with the split solutions
I-D late in the game. James, you did not raise all the issues that you
had with the integrated I-D until now. You have been around in IETF more
than I have been....

jak>> The only issue I have is, like I said above, that a documentation 
philosophy should be applied consistently to a body of work. If the 
philosophy is "protocol enhancements in separate Standards Track documents" 
then I think that should apply to all protocol enhancements.

            jak

PS: Isn't it a bit ironic that the authors of the split document want to 
have the document be integrated and the authors of the integrated document 
want it to be split? :-) 



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



From mip6-bounces@ietf.org Wed Aug 23 13:38:12 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GFwg3-0004PS-P3; Wed, 23 Aug 2006 13:38:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GFwg2-0004NZ-Nf
	for mip6@ietf.org; Wed, 23 Aug 2006 13:38:06 -0400
Received: from key1.docomolabs-usa.com ([216.98.102.225]
	helo=fridge.docomolabs-usa.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GFwg2-0004cv-0E
	for mip6@ietf.org; Wed, 23 Aug 2006 13:38:06 -0400
Message-ID: <020101c6c6da$f062ba10$546015ac@dcml.docomolabsusa.com>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Tsirtsis, George" <tsirtsis@qualcomm.com>,
	"Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>,
	"Alper Yegin" <alper.yegin@yegin.org>,
	"Basavaraj Patil" <basavaraj.patil@nokia.com>, <mip6@ietf.org>
References: <7EB20EA0938B4D42A2D82689365C9B7A11DBD6@NAEX14.na.qualcomm.com>
Subject: Re: Kuntal's comments on the split document (was: Re:
	[Mip6]Conclusion of the consensus call relatedtothebootstrapping I-Ds)
Date: Wed, 23 Aug 2006 10:38:26 -0700
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: f8184d7d4d1b986353eb58ea3e887935
Cc: 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

George,

The problem is that interoperability requires standardizing more than bits 
on the wire. If one MSP deploys, for example IKEv2 home address assignment 
and another doesn't then a client that is expecting to get its home address 
via IKEv2 won't know that it can for all MSPs. Unlike the integrated 
solution, no other SDO is going to take and standardize a system 
architecture based on the protocol enhancements in the split solution.

            jak

----- Original Message ----- 
From: "Tsirtsis, George" <tsirtsis@qualcomm.com>
To: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>; "James Kempf" 
<kempf@docomolabs-usa.com>; "Alper Yegin" <alper.yegin@yegin.org>; 
"Basavaraj Patil" <basavaraj.patil@nokia.com>; <mip6@ietf.org>
Sent: Tuesday, August 22, 2006 4:16 PM
Subject: RE: Kuntal's comments on the split document (was: Re: 
[Mip6]Conclusion of the consensus call relatedtothebootstrapping I-Ds)


I have not followed this discussion from the beginning so my apologies
if this has been discussed before.

IMHO, the problem with both the split and integrated documents is that
they are more system design documents than protocol specifications.

I think the WG correctly decided to standardize the DHCP-option of the
integrated document separately since this is the protocol part.
The rest of the document defines a way to use the DHCP-option together
with other IETF "tools" to build a system. The split document does the
same thing so, if there is a protocol extension to be standardized
(e.g., DNS Update mobility option) it needs to be taken out and be
standardized.

Let me remind everyone that the IETF does not build
systems/architectures unless absolutely necessary and in this case it is
not necessary since one can come up with many different ways of using
several IETF protocols to bootstrap MIP, all of which are valid.

The "system description" parts of the split/integrated documents can
then become whatever; it does not really matter since the notion of
"standards track" in the IETF does not apply to systems. As far as I am
concerned, if they need to be standardized at all, they need to be
standardized in an SDO otherwise informational or BCP can work too.

Regards
George

> -----Original Message-----
> From: Chowdhury, Kuntal [mailto:kchowdhury@starentnetworks.com]
> Sent: Tuesday, August 22, 2006 6:27 PM
> To: James Kempf; Alper Yegin; Basavaraj Patil; mip6@ietf.org
> Subject: RE: Kuntal's comments on the split document (was: Re:
> [Mip6]Conclusion of the consensus call relatedtothebootstrapping I-Ds)
>
>
>
> > -----Original Message-----
> > From: James Kempf [mailto:kempf@docomolabs-usa.com]
> > Sent: Tuesday, August 22, 2006 3:37 PM
> > To: Chowdhury, Kuntal; Alper Yegin; Basavaraj Patil; mip6@ietf.org
> > Subject: Kuntal's comments on the split document (was: Re: [Mip6]
> > Conclusion of the consensus call relatedtothebootstrapping I-Ds)
> >
> > Alright. If you want to discuss the split document then let's do it
> (note
> > change in thread header).
> >
> > [KC>] Which part of my statement you found to be "emotional"? Is it
> the
> > "rather useless" part? In my opinion, the split scenario solution
> > document has some things that are totally out of scope of mip6
> > bootstrapping (e.g. the dynamic DNS update). Moreover, the HA
> > bootstrapping is based on DNS query which has security issues.
Anybody
> > in the public internet can discover operator's HAs. This is a
security
> > hole that the split solution introduces. These are NOT emotional
> > statements :-). I am just expressing how I feel about the split
> solution
> > document, that's all.
> >
> > jak>> These are your opinions, and I would say they are rather
> emotionally
> > expressed (my opinion, of course).
> >
> > jak>> The goals of the split document are different from the
> intergrated
> > document. The split document is primarily for enterprises and for
> > businesses
> > that have as their primary business providing mobility service only
> (hence
> > the name). Since such businesses are new, they are likely to be
> > entrepreneurial. They're not going to have the time or resources to
> run
> > around to various different SDOs and try to force their solutions to
> get
> > locked into the standards. The split solution is designed to provide
> them
> > with interoperability. It is possible for integrated wireless
service
> > providers to use the split solution, of course, possibly as an
> additional
> > revenue generator for providing mobility service to customers that
use
> a
> > different access network provider.
> >
> [KC>] What you describe above is the scope of the split document. The
> scope is unique, understood. But that does not automatically justify a
> standards track RFC for the solution document. What we have is a split
> scenario solution framework document _using_ IKEv2, DNS etc. So, are
you
> OK to make the split solution I-D an informational RFC?
>
> > jak>> Regarding the security issues of DNS, we've been through this
> issue
> > a
> > number of times, the draft was reviewed by SAAG (we have yet to
> respond)
> > and
> > there was nothing said about it, so I am puzzled why you are raising
> this
> > canard again. We recently had a good (and I might add nonemotional)
> > discussion on this list about using anycast, initiated by
Jean-Marie,
> and
> > I've drafted some text up that will allow anycast addresses to be
used
> in
> > DNS SRV RRs instead of the unicast addresses of the HAs, based on
> > Francis's
> > draft, and sent the text to Gerardo (he's on vacation at the
moment).
> This
> > should provide some moderate protection from DoS, but it will not
> protect
> > completely, just as the DHCP solution won't. As I've pointed out in
> the
> > past, as soon as you release the address of a server to an end host,
> > regardless of how it is done, all bets are off. What the end host
does
> > with
> > that address is completely out of your control, and if the end host
is
> > infected with malware, you can be sure somebody's botnet will get
the
> > address. Or are you proposing some enhancement to the DHCP based
> solution
> > that will make it impossible for malware to grab a home agent's
> address?
> >
> [KC>] There is a clear difference between the way HA address is
> discovered in the split solution and in the integrated solution. The
HA
> address is _assigned_ to the MN in the integrated solution by the Home
> AAA server. This ONLY happens once the MN passes authentication. So,
the
> chances of giving away the HA address to totally unknown entities in
> this case is next to none. In case of split scenario, the HAs are
> totally exposed to anyone with good or bad intention. Anyone with an
IP
> connection can send DNS queries to get any MSP's HA addresses and then
> launch DoS attacks from his/her basement.
>
> It is true that once the HA address is given to an entity, if that
> entity is compromised, the HA address can get out to some bad guys.
But
> it is not likely to happen too often. This type of security threat is
> generic and not specific to mip6 bootstrapping, IMHO. If the
> entity/device is compromised, other things like root-key, username,
any
> other cached data will also be revealed. So, it is a generic issue.
>
> In case of split scenario, the risk of giving away the HA address to
bad
> guys is always there. So, the solution doesn't seem to be deployable
in
> public wireless networks.
>
> > > HL prefix etc. Integrated scenario is likely to be widely
deployed,
> > > where as the split scenario doesn't even have any buyer.
> > >
> > > jak>> I think you mean draft-jang will be widely deployed. As I
> recall
> > > someone posted email a while back saying that there was no plan by
> any
> > > other
> > > SDO to adopt the integrated draft as is, just the two draft-jang
> DHCP
> > > enhancements.
> > >
> > [KC>] Unfortunately, here you are making your argument based on some
> > rumor that you heard about real SDO requirements. Please use
official
> > liaison channels to confirm SDO requirements before posting comments
> on
> > the mailing list.
> >
> > jak>> OK. Would any of our liasons like to comment on this? Is the
> system
> > architecture described in the integrated draft what your SDO is
> planning
> > on
> > standardizing?
> >
> > > So, if you want to go down this path, we will end up making both
the
> > > documents informational. If not both of them should remain
standards
> > > track.
> > >
> > > jak>> We're not discussing the split draft here. If you want to
> > propose
> > > changing it, then start a separate thread.
> > >
> > [KC>] We need to discuss how useful the split scenario draft is.
Also
> to
> > be fair, we need to make a decision about informational vs.
standards
> > track suitability for _both_ the documents if that's what the WG
ends
> up
> > deciding. That's what I meant to say here.
> >
> > jak>> Then why didn't you start a separate thread on it? This is
basic
> > IETF
> > courtesy. Kuntal, you've been around IETF long enough to know these
> kinds
> > of
> > things.
> >
> [KC>] OK, I apologize for raising the issues with the split solutions
> I-D late in the game. James, you did not raise all the issues that you
> had with the integrated I-D until now. You have been around in IETF
more
> than I have been....
>
>
> >             jak
> >
>
>
> "This email message and any attachments are confidential information
of
> Starent Networks, Corp. The information transmitted may not be used to
> create or change any contractual obligations of Starent Networks,
Corp.
> Any review, retransmission, dissemination or other use of, or taking
of
> any action in reliance upon this e-mail and its attachments by persons
or
> entities other than the intended recipient is prohibited. If you are
not
> the intended recipient, please notify the sender immediately -- by
> replying to this message or by sending an email to
> postmaster@starentnetworks.com -- and destroy all copies of this
message
> and any attachments without reading or disclosing their contents.
Thank
> you."
>
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6



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



From mip6-bounces@ietf.org Wed Aug 23 13:55:17 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GFwwL-00054s-TY; Wed, 23 Aug 2006 13:54:57 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GFwwL-00054m-5w
	for mip6@ietf.org; Wed, 23 Aug 2006 13:54:57 -0400
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GFwwJ-0007kH-E2
	for mip6@ietf.org; Wed, 23 Aug 2006 13:54:57 -0400
Received: from sabrina.qualcomm.com (sabrina.qualcomm.com [129.46.61.150])
	by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k7NHsotn002646
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Wed, 23 Aug 2006 10:54:51 -0700
Received: from NAEXBR02.na.qualcomm.com (naexbr02.qualcomm.com [10.46.92.109])
	by sabrina.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id
	k7NHruUP003706; Wed, 23 Aug 2006 10:54:49 -0700 (PDT)
Received: from NAEX14.na.qualcomm.com ([10.47.5.242]) by
	NAEXBR02.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 23 Aug 2006 10:54:48 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Kuntal's comments on the split document (was: Re:
	[Mip6]Conclusion of the consensus call relatedtothebootstrapping I-Ds)
Date: Wed, 23 Aug 2006 10:54:42 -0700
Message-ID: <7EB20EA0938B4D42A2D82689365C9B7A11DC63@NAEX14.na.qualcomm.com>
In-Reply-To: <020101c6c6da$f062ba10$546015ac@dcml.docomolabsusa.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Kuntal's comments on the split document (was: Re:
	[Mip6]Conclusion of the consensus call
	relatedtothebootstrapping I-Ds)
Thread-Index: AcbG2uyrxK+QbJxcR6C3a5oAE/bo5QAAC73g
From: "Tsirtsis, George" <tsirtsis@qualcomm.com>
To: "James Kempf" <kempf@docomolabs-usa.com>,
	"Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>,
	"Alper Yegin" <alper.yegin@yegin.org>,
	"Basavaraj Patil" <basavaraj.patil@nokia.com>, <mip6@ietf.org>
X-OriginalArrivalTime: 23 Aug 2006 17:54:48.0458 (UTC)
	FILETIME=[39B086A0:01C6C6DD]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1c0c3d540ad9f95212b1c2a9a2cc2595
Cc: 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

SDOs are by definition defining architectures relevant only to that
specific SDO. Traditionally SDOs have strived to be incompatible. More
recently there are uncertain steps towards commonality but we will see
how far this can go.

We should also not confuse what one or more SDOs may decide to do with
what is good for the Internet as a whole. MIP is not only used by
systems defined in SDOs, but also by systems used in corporate and other
systems that Net Admins put together as they see fit based on tools
available to them by the IETF and the market.

Let me also repeat that I have no problem with BCP/Info type documents
defining how these tools can be put together in certain cases.

George

> -----Original Message-----
> From: James Kempf [mailto:kempf@docomolabs-usa.com]
> Sent: Wednesday, August 23, 2006 1:38 PM
> To: Tsirtsis, George; Chowdhury, Kuntal; Alper Yegin; Basavaraj Patil;
> mip6@ietf.org
> Subject: Re: Kuntal's comments on the split document (was: Re:
> [Mip6]Conclusion of the consensus call relatedtothebootstrapping I-Ds)
>=20
> George,
>=20
> The problem is that interoperability requires standardizing more than
bits
> on the wire. If one MSP deploys, for example IKEv2 home address
assignment
> and another doesn't then a client that is expecting to get its home
> address
> via IKEv2 won't know that it can for all MSPs. Unlike the integrated
> solution, no other SDO is going to take and standardize a system
> architecture based on the protocol enhancements in the split solution.
>=20
>             jak
>=20
> ----- Original Message -----
> From: "Tsirtsis, George" <tsirtsis@qualcomm.com>
> To: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>; "James
Kempf"
> <kempf@docomolabs-usa.com>; "Alper Yegin" <alper.yegin@yegin.org>;
> "Basavaraj Patil" <basavaraj.patil@nokia.com>; <mip6@ietf.org>
> Sent: Tuesday, August 22, 2006 4:16 PM
> Subject: RE: Kuntal's comments on the split document (was: Re:
> [Mip6]Conclusion of the consensus call relatedtothebootstrapping I-Ds)
>=20
>=20
> I have not followed this discussion from the beginning so my apologies
> if this has been discussed before.
>=20
> IMHO, the problem with both the split and integrated documents is that
> they are more system design documents than protocol specifications.
>=20
> I think the WG correctly decided to standardize the DHCP-option of the
> integrated document separately since this is the protocol part.
> The rest of the document defines a way to use the DHCP-option together
> with other IETF "tools" to build a system. The split document does the
> same thing so, if there is a protocol extension to be standardized
> (e.g., DNS Update mobility option) it needs to be taken out and be
> standardized.
>=20
> Let me remind everyone that the IETF does not build
> systems/architectures unless absolutely necessary and in this case it
is
> not necessary since one can come up with many different ways of using
> several IETF protocols to bootstrap MIP, all of which are valid.
>=20
> The "system description" parts of the split/integrated documents can
> then become whatever; it does not really matter since the notion of
> "standards track" in the IETF does not apply to systems. As far as I
am
> concerned, if they need to be standardized at all, they need to be
> standardized in an SDO otherwise informational or BCP can work too.
>=20
> Regards
> George
>=20
> > -----Original Message-----
> > From: Chowdhury, Kuntal [mailto:kchowdhury@starentnetworks.com]
> > Sent: Tuesday, August 22, 2006 6:27 PM
> > To: James Kempf; Alper Yegin; Basavaraj Patil; mip6@ietf.org
> > Subject: RE: Kuntal's comments on the split document (was: Re:
> > [Mip6]Conclusion of the consensus call relatedtothebootstrapping
I-Ds)
> >
> >
> >
> > > -----Original Message-----
> > > From: James Kempf [mailto:kempf@docomolabs-usa.com]
> > > Sent: Tuesday, August 22, 2006 3:37 PM
> > > To: Chowdhury, Kuntal; Alper Yegin; Basavaraj Patil; mip6@ietf.org
> > > Subject: Kuntal's comments on the split document (was: Re: [Mip6]
> > > Conclusion of the consensus call relatedtothebootstrapping I-Ds)
> > >
> > > Alright. If you want to discuss the split document then let's do
it
> > (note
> > > change in thread header).
> > >
> > > [KC>] Which part of my statement you found to be "emotional"? Is
it
> > the
> > > "rather useless" part? In my opinion, the split scenario solution
> > > document has some things that are totally out of scope of mip6
> > > bootstrapping (e.g. the dynamic DNS update). Moreover, the HA
> > > bootstrapping is based on DNS query which has security issues.
> Anybody
> > > in the public internet can discover operator's HAs. This is a
> security
> > > hole that the split solution introduces. These are NOT emotional
> > > statements :-). I am just expressing how I feel about the split
> > solution
> > > document, that's all.
> > >
> > > jak>> These are your opinions, and I would say they are rather
> > emotionally
> > > expressed (my opinion, of course).
> > >
> > > jak>> The goals of the split document are different from the
> > intergrated
> > > document. The split document is primarily for enterprises and for
> > > businesses
> > > that have as their primary business providing mobility service
only
> > (hence
> > > the name). Since such businesses are new, they are likely to be
> > > entrepreneurial. They're not going to have the time or resources
to
> > run
> > > around to various different SDOs and try to force their solutions
to
> > get
> > > locked into the standards. The split solution is designed to
provide
> > them
> > > with interoperability. It is possible for integrated wireless
> service
> > > providers to use the split solution, of course, possibly as an
> > additional
> > > revenue generator for providing mobility service to customers that
> use
> > a
> > > different access network provider.
> > >
> > [KC>] What you describe above is the scope of the split document.
The
> > scope is unique, understood. But that does not automatically justify
a
> > standards track RFC for the solution document. What we have is a
split
> > scenario solution framework document _using_ IKEv2, DNS etc. So, are
> you
> > OK to make the split solution I-D an informational RFC?
> >
> > > jak>> Regarding the security issues of DNS, we've been through
this
> > issue
> > > a
> > > number of times, the draft was reviewed by SAAG (we have yet to
> > respond)
> > > and
> > > there was nothing said about it, so I am puzzled why you are
raising
> > this
> > > canard again. We recently had a good (and I might add
nonemotional)
> > > discussion on this list about using anycast, initiated by
> Jean-Marie,
> > and
> > > I've drafted some text up that will allow anycast addresses to be
> used
> > in
> > > DNS SRV RRs instead of the unicast addresses of the HAs, based on
> > > Francis's
> > > draft, and sent the text to Gerardo (he's on vacation at the
> moment).
> > This
> > > should provide some moderate protection from DoS, but it will not
> > protect
> > > completely, just as the DHCP solution won't. As I've pointed out
in
> > the
> > > past, as soon as you release the address of a server to an end
host,
> > > regardless of how it is done, all bets are off. What the end host
> does
> > > with
> > > that address is completely out of your control, and if the end
host
> is
> > > infected with malware, you can be sure somebody's botnet will get
> the
> > > address. Or are you proposing some enhancement to the DHCP based
> > solution
> > > that will make it impossible for malware to grab a home agent's
> > address?
> > >
> > [KC>] There is a clear difference between the way HA address is
> > discovered in the split solution and in the integrated solution. The
> HA
> > address is _assigned_ to the MN in the integrated solution by the
Home
> > AAA server. This ONLY happens once the MN passes authentication. So,
> the
> > chances of giving away the HA address to totally unknown entities in
> > this case is next to none. In case of split scenario, the HAs are
> > totally exposed to anyone with good or bad intention. Anyone with an
> IP
> > connection can send DNS queries to get any MSP's HA addresses and
then
> > launch DoS attacks from his/her basement.
> >
> > It is true that once the HA address is given to an entity, if that
> > entity is compromised, the HA address can get out to some bad guys.
> But
> > it is not likely to happen too often. This type of security threat
is
> > generic and not specific to mip6 bootstrapping, IMHO. If the
> > entity/device is compromised, other things like root-key, username,
> any
> > other cached data will also be revealed. So, it is a generic issue.
> >
> > In case of split scenario, the risk of giving away the HA address to
> bad
> > guys is always there. So, the solution doesn't seem to be deployable
> in
> > public wireless networks.
> >
> > > > HL prefix etc. Integrated scenario is likely to be widely
> deployed,
> > > > where as the split scenario doesn't even have any buyer.
> > > >
> > > > jak>> I think you mean draft-jang will be widely deployed. As I
> > recall
> > > > someone posted email a while back saying that there was no plan
by
> > any
> > > > other
> > > > SDO to adopt the integrated draft as is, just the two draft-jang
> > DHCP
> > > > enhancements.
> > > >
> > > [KC>] Unfortunately, here you are making your argument based on
some
> > > rumor that you heard about real SDO requirements. Please use
> official
> > > liaison channels to confirm SDO requirements before posting
comments
> > on
> > > the mailing list.
> > >
> > > jak>> OK. Would any of our liasons like to comment on this? Is the
> > system
> > > architecture described in the integrated draft what your SDO is
> > planning
> > > on
> > > standardizing?
> > >
> > > > So, if you want to go down this path, we will end up making both
> the
> > > > documents informational. If not both of them should remain
> standards
> > > > track.
> > > >
> > > > jak>> We're not discussing the split draft here. If you want to
> > > propose
> > > > changing it, then start a separate thread.
> > > >
> > > [KC>] We need to discuss how useful the split scenario draft is.
> Also
> > to
> > > be fair, we need to make a decision about informational vs.
> standards
> > > track suitability for _both_ the documents if that's what the WG
> ends
> > up
> > > deciding. That's what I meant to say here.
> > >
> > > jak>> Then why didn't you start a separate thread on it? This is
> basic
> > > IETF
> > > courtesy. Kuntal, you've been around IETF long enough to know
these
> > kinds
> > > of
> > > things.
> > >
> > [KC>] OK, I apologize for raising the issues with the split
solutions
> > I-D late in the game. James, you did not raise all the issues that
you
> > had with the integrated I-D until now. You have been around in IETF
> more
> > than I have been....
> >
> >
> > >             jak
> > >
> >
> >
> > "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
>=20


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



From mip6-bounces@ietf.org Wed Aug 23 14:27:50 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GFxRo-0004AF-Ug; Wed, 23 Aug 2006 14:27:28 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GFxRo-00048i-7H
	for mip6@ietf.org; Wed, 23 Aug 2006 14:27:28 -0400
Received: from key1.docomolabs-usa.com ([216.98.102.225]
	helo=fridge.docomolabs-usa.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GFxRk-0004Rm-DC
	for mip6@ietf.org; Wed, 23 Aug 2006 14:27:28 -0400
Message-ID: <026301c6c6e1$d7f00350$546015ac@dcml.docomolabsusa.com>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>,
	"Tsirtsis, George" <tsirtsis@qualcomm.com>,
	"Alper Yegin" <alper.yegin@yegin.org>,
	"Basavaraj Patil" <basavaraj.patil@nokia.com>, <mip6@ietf.org>
References: <7CCD07160348804497EF29E9EA5560D783725F@exchtewks2.starentnetworks.com>
Subject: Re: Kuntal's comments on the split document (was: Re:
	[Mip6]Conclusion of the consensus call relatedtothebootstrapping I-Ds)
Date: Wed, 23 Aug 2006 11:27:51 -0700
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: db284e046c8702920c1c6125bc4d0b7a
Cc: 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Kuntal,

I don't have much time to argue either. And, yes, I do have an idea of how 
Mobile IP might be deployed differently. For an idea of how it might look, 
check http://www.hotspotvpn.com/. This is not to say that the current 
deployment model is wrong, just that I think more choices in the future 
might be beneficial, even for integrated service providers.

                  jak

----- Original Message ----- 
From: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
To: "James Kempf" <kempf@docomolabs-usa.com>; "Tsirtsis, George" 
<tsirtsis@qualcomm.com>; "Alper Yegin" <alper.yegin@yegin.org>; "Basavaraj 
Patil" <basavaraj.patil@nokia.com>; <mip6@ietf.org>
Sent: Wednesday, August 23, 2006 11:14 AM
Subject: RE: Kuntal's comments on the split document (was: Re: 
[Mip6]Conclusion of the consensus call relatedtothebootstrapping I-Ds)


James,

I don't have infinite amount of time in hand to argue with you here. The
split solutions document is nothing more than a description of how
people can do mip6 bootstrapping when ASA != MSA, that's all. Section 8
has only two new options/attributes i.e. DNS update MO which is totally
orthogonal to the solution, so it should be taken out. HL prefix via
IKEv2 is unnecessary since the HA can give out a HoA to the MN w/o doing
this roundabout way to do HoA assignment. So, this attribute should be
taken out as well. Since there is nothing else to standardize in the
split solutions doc, we should make it informational.

Your idea of how mobile IP works seems to be very different than what is
largely deployed today. Mobile IP is primarily used by large (CDMA)
wireless operators. These wireless IP networks are not public internet,
so someone snooping into these wireless links to figure out HA addresses
can be practically ruled out. Even if someone tries to snoop into these
wireless links, the degree of difficulty is substantially higher than
sending a simple DNS query.

Regards,
Kuntal


> -----Original Message-----
> From: James Kempf [mailto:kempf@docomolabs-usa.com]
> Sent: Wednesday, August 23, 2006 12:38 PM
> To: Tsirtsis, George; Chowdhury, Kuntal; Alper Yegin; Basavaraj Patil;
> mip6@ietf.org
> Subject: Re: Kuntal's comments on the split document (was: Re:
> [Mip6]Conclusion of the consensus call relatedtothebootstrapping I-Ds)
>
> George,
>
> The problem is that interoperability requires standardizing more than
bits
> on the wire. If one MSP deploys, for example IKEv2 home address
assignment
> and another doesn't then a client that is expecting to get its home
> address
> via IKEv2 won't know that it can for all MSPs. Unlike the integrated
> solution, no other SDO is going to take and standardize a system
> architecture based on the protocol enhancements in the split solution.
>
>             jak
>
> ----- Original Message -----
> From: "Tsirtsis, George" <tsirtsis@qualcomm.com>
> To: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>; "James
Kempf"
> <kempf@docomolabs-usa.com>; "Alper Yegin" <alper.yegin@yegin.org>;
> "Basavaraj Patil" <basavaraj.patil@nokia.com>; <mip6@ietf.org>
> Sent: Tuesday, August 22, 2006 4:16 PM
> Subject: RE: Kuntal's comments on the split document (was: Re:
> [Mip6]Conclusion of the consensus call relatedtothebootstrapping I-Ds)
>
>
> I have not followed this discussion from the beginning so my apologies
> if this has been discussed before.
>
> IMHO, the problem with both the split and integrated documents is that
> they are more system design documents than protocol specifications.
>
> I think the WG correctly decided to standardize the DHCP-option of the
> integrated document separately since this is the protocol part.
> The rest of the document defines a way to use the DHCP-option together
> with other IETF "tools" to build a system. The split document does the
> same thing so, if there is a protocol extension to be standardized
> (e.g., DNS Update mobility option) it needs to be taken out and be
> standardized.
>
> Let me remind everyone that the IETF does not build
> systems/architectures unless absolutely necessary and in this case it
is
> not necessary since one can come up with many different ways of using
> several IETF protocols to bootstrap MIP, all of which are valid.
>
> The "system description" parts of the split/integrated documents can
> then become whatever; it does not really matter since the notion of
> "standards track" in the IETF does not apply to systems. As far as I
am
> concerned, if they need to be standardized at all, they need to be
> standardized in an SDO otherwise informational or BCP can work too.
>
> Regards
> George
>
> > -----Original Message-----
> > From: Chowdhury, Kuntal [mailto:kchowdhury@starentnetworks.com]
> > Sent: Tuesday, August 22, 2006 6:27 PM
> > To: James Kempf; Alper Yegin; Basavaraj Patil; mip6@ietf.org
> > Subject: RE: Kuntal's comments on the split document (was: Re:
> > [Mip6]Conclusion of the consensus call relatedtothebootstrapping
I-Ds)
> >
> >
> >
> > > -----Original Message-----
> > > From: James Kempf [mailto:kempf@docomolabs-usa.com]
> > > Sent: Tuesday, August 22, 2006 3:37 PM
> > > To: Chowdhury, Kuntal; Alper Yegin; Basavaraj Patil; mip6@ietf.org
> > > Subject: Kuntal's comments on the split document (was: Re: [Mip6]
> > > Conclusion of the consensus call relatedtothebootstrapping I-Ds)
> > >
> > > Alright. If you want to discuss the split document then let's do
it
> > (note
> > > change in thread header).
> > >
> > > [KC>] Which part of my statement you found to be "emotional"? Is
it
> > the
> > > "rather useless" part? In my opinion, the split scenario solution
> > > document has some things that are totally out of scope of mip6
> > > bootstrapping (e.g. the dynamic DNS update). Moreover, the HA
> > > bootstrapping is based on DNS query which has security issues.
> Anybody
> > > in the public internet can discover operator's HAs. This is a
> security
> > > hole that the split solution introduces. These are NOT emotional
> > > statements :-). I am just expressing how I feel about the split
> > solution
> > > document, that's all.
> > >
> > > jak>> These are your opinions, and I would say they are rather
> > emotionally
> > > expressed (my opinion, of course).
> > >
> > > jak>> The goals of the split document are different from the
> > intergrated
> > > document. The split document is primarily for enterprises and for
> > > businesses
> > > that have as their primary business providing mobility service
only
> > (hence
> > > the name). Since such businesses are new, they are likely to be
> > > entrepreneurial. They're not going to have the time or resources
to
> > run
> > > around to various different SDOs and try to force their solutions
to
> > get
> > > locked into the standards. The split solution is designed to
provide
> > them
> > > with interoperability. It is possible for integrated wireless
> service
> > > providers to use the split solution, of course, possibly as an
> > additional
> > > revenue generator for providing mobility service to customers that
> use
> > a
> > > different access network provider.
> > >
> > [KC>] What you describe above is the scope of the split document.
The
> > scope is unique, understood. But that does not automatically justify
a
> > standards track RFC for the solution document. What we have is a
split
> > scenario solution framework document _using_ IKEv2, DNS etc. So, are
> you
> > OK to make the split solution I-D an informational RFC?
> >
> > > jak>> Regarding the security issues of DNS, we've been through
this
> > issue
> > > a
> > > number of times, the draft was reviewed by SAAG (we have yet to
> > respond)
> > > and
> > > there was nothing said about it, so I am puzzled why you are
raising
> > this
> > > canard again. We recently had a good (and I might add
nonemotional)
> > > discussion on this list about using anycast, initiated by
> Jean-Marie,
> > and
> > > I've drafted some text up that will allow anycast addresses to be
> used
> > in
> > > DNS SRV RRs instead of the unicast addresses of the HAs, based on
> > > Francis's
> > > draft, and sent the text to Gerardo (he's on vacation at the
> moment).
> > This
> > > should provide some moderate protection from DoS, but it will not
> > protect
> > > completely, just as the DHCP solution won't. As I've pointed out
in
> > the
> > > past, as soon as you release the address of a server to an end
host,
> > > regardless of how it is done, all bets are off. What the end host
> does
> > > with
> > > that address is completely out of your control, and if the end
host
> is
> > > infected with malware, you can be sure somebody's botnet will get
> the
> > > address. Or are you proposing some enhancement to the DHCP based
> > solution
> > > that will make it impossible for malware to grab a home agent's
> > address?
> > >
> > [KC>] There is a clear difference between the way HA address is
> > discovered in the split solution and in the integrated solution. The
> HA
> > address is _assigned_ to the MN in the integrated solution by the
Home
> > AAA server. This ONLY happens once the MN passes authentication. So,
> the
> > chances of giving away the HA address to totally unknown entities in
> > this case is next to none. In case of split scenario, the HAs are
> > totally exposed to anyone with good or bad intention. Anyone with an
> IP
> > connection can send DNS queries to get any MSP's HA addresses and
then
> > launch DoS attacks from his/her basement.
> >
> > It is true that once the HA address is given to an entity, if that
> > entity is compromised, the HA address can get out to some bad guys.
> But
> > it is not likely to happen too often. This type of security threat
is
> > generic and not specific to mip6 bootstrapping, IMHO. If the
> > entity/device is compromised, other things like root-key, username,
> any
> > other cached data will also be revealed. So, it is a generic issue.
> >
> > In case of split scenario, the risk of giving away the HA address to
> bad
> > guys is always there. So, the solution doesn't seem to be deployable
> in
> > public wireless networks.
> >
> > > > HL prefix etc. Integrated scenario is likely to be widely
> deployed,
> > > > where as the split scenario doesn't even have any buyer.
> > > >
> > > > jak>> I think you mean draft-jang will be widely deployed. As I
> > recall
> > > > someone posted email a while back saying that there was no plan
by
> > any
> > > > other
> > > > SDO to adopt the integrated draft as is, just the two draft-jang
> > DHCP
> > > > enhancements.
> > > >
> > > [KC>] Unfortunately, here you are making your argument based on
some
> > > rumor that you heard about real SDO requirements. Please use
> official
> > > liaison channels to confirm SDO requirements before posting
comments
> > on
> > > the mailing list.
> > >
> > > jak>> OK. Would any of our liasons like to comment on this? Is the
> > system
> > > architecture described in the integrated draft what your SDO is
> > planning
> > > on
> > > standardizing?
> > >
> > > > So, if you want to go down this path, we will end up making both
> the
> > > > documents informational. If not both of them should remain
> standards
> > > > track.
> > > >
> > > > jak>> We're not discussing the split draft here. If you want to
> > > propose
> > > > changing it, then start a separate thread.
> > > >
> > > [KC>] We need to discuss how useful the split scenario draft is.
> Also
> > to
> > > be fair, we need to make a decision about informational vs.
> standards
> > > track suitability for _both_ the documents if that's what the WG
> ends
> > up
> > > deciding. That's what I meant to say here.
> > >
> > > jak>> Then why didn't you start a separate thread on it? This is
> basic
> > > IETF
> > > courtesy. Kuntal, you've been around IETF long enough to know
these
> > kinds
> > > of
> > > things.
> > >
> > [KC>] OK, I apologize for raising the issues with the split
solutions
> > I-D late in the game. James, you did not raise all the issues that
you
> > had with the integrated I-D until now. You have been around in IETF
> more
> > than I have been....
> >
> >
> > >             jak
> > >
> >
> >
> > "This email message and any attachments are confidential information
> of
> > Starent Networks, Corp. The information transmitted may not be used
to
> > create or change any contractual obligations of Starent Networks,
> Corp.
> > Any review, retransmission, dissemination or other use of, or taking
> of
> > any action in reliance upon this e-mail and its attachments by
persons
> or
> > entities other than the intended recipient is prohibited. If you are
> not
> > the intended recipient, please notify the sender immediately -- by
> > replying to this message or by sending an email to
> > postmaster@starentnetworks.com -- and destroy all copies of this
> message
> > and any attachments without reading or disclosing their contents.
> Thank
> > you."
> >
> > _______________________________________________
> > Mip6 mailing list
> > Mip6@ietf.org
> > https://www1.ietf.org/mailman/listinfo/mip6
>




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



From mip6-bounces@ietf.org Wed Aug 23 15:36:03 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GFyV8-0005Lf-GL; Wed, 23 Aug 2006 15:34:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GFyV6-0005La-IF
	for mip6@ietf.org; Wed, 23 Aug 2006 15:34:56 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GFxRv-0004OR-3u
	for mip6@ietf.org; Wed, 23 Aug 2006 14:27:35 -0400
Received: from mx0.starentnetworks.com ([12.38.223.203])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1GFxFi-0007f2-L7
	for mip6@ietf.org; Wed, 23 Aug 2006 14:15:02 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mx0.starentnetworks.com (Postfix) with ESMTP id 723D49001B;
	Wed, 23 Aug 2006 14:14:54 -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 01818-09; Wed, 23 Aug 2006 14:14:53 -0400 (EDT)
Received: from exchtewks1.starentnetworks.com (exchtewks1.starentnetworks.com
	[12.33.233.52]) by mx0.starentnetworks.com (Postfix) with ESMTP;
	Wed, 23 Aug 2006 14:14:53 -0400 (EDT)
X-MessageTextProcessor: DisclaimIt (2.70.271) [Starent Networks Corp.]
Received: from exchtewks2.starentnetworks.com ([12.33.232.12]) by
	exchtewks1.starentnetworks.com with Microsoft
	SMTPSVC(6.0.3790.1830); Wed, 23 Aug 2006 14:14:53 -0400
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Kuntal's comments on the split document (was: Re:
	[Mip6]Conclusion of the consensus call relatedtothebootstrapping I-Ds)
Date: Wed, 23 Aug 2006 14:14:52 -0400
Message-ID: <7CCD07160348804497EF29E9EA5560D783725F@exchtewks2.starentnetworks.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Kuntal's comments on the split document (was: Re:
	[Mip6]Conclusion of the consensus call
	relatedtothebootstrapping I-Ds)
thread-index: AcbG2uLKMCKtmCu/RUWH59lpootjHgAAg5NQ
From: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
Importance: normal
Priority: normal
To: "James Kempf" <kempf@docomolabs-usa.com>,
	"Tsirtsis, George" <tsirtsis@qualcomm.com>,
	"Alper Yegin" <alper.yegin@yegin.org>,
	"Basavaraj Patil" <basavaraj.patil@nokia.com>, <mip6@ietf.org>
X-OriginalArrivalTime: 23 Aug 2006 18:14:53.0144 (UTC)
	FILETIME=[07BD0580:01C6C6E0]
X-Virus-Scanned: amavisd-new 2.2.1 (20041222) at mx0.starentnetworks.com
X-Spam-Score: -2.6 (--)
X-Scan-Signature: 32a65c0bf5eb4ec26489239c7cdd0636
Cc: 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

James,

I don't have infinite amount of time in hand to argue with you here. The
split solutions document is nothing more than a description of how
people can do mip6 bootstrapping when ASA !=3D MSA, that's all. Section =
8
has only two new options/attributes i.e. DNS update MO which is totally
orthogonal to the solution, so it should be taken out. HL prefix via
IKEv2 is unnecessary since the HA can give out a HoA to the MN w/o doing
this roundabout way to do HoA assignment. So, this attribute should be
taken out as well. Since there is nothing else to standardize in the
split solutions doc, we should make it informational.

Your idea of how mobile IP works seems to be very different than what is
largely deployed today. Mobile IP is primarily used by large (CDMA)
wireless operators. These wireless IP networks are not public internet,
so someone snooping into these wireless links to figure out HA addresses
can be practically ruled out. Even if someone tries to snoop into these
wireless links, the degree of difficulty is substantially higher than
sending a simple DNS query.

Regards,
Kuntal


> -----Original Message-----
> From: James Kempf [mailto:kempf@docomolabs-usa.com]
> Sent: Wednesday, August 23, 2006 12:38 PM
> To: Tsirtsis, George; Chowdhury, Kuntal; Alper Yegin; Basavaraj Patil;
> mip6@ietf.org
> Subject: Re: Kuntal's comments on the split document (was: Re:
> [Mip6]Conclusion of the consensus call relatedtothebootstrapping I-Ds)
>=20
> George,
>=20
> The problem is that interoperability requires standardizing more than
bits
> on the wire. If one MSP deploys, for example IKEv2 home address
assignment
> and another doesn't then a client that is expecting to get its home
> address
> via IKEv2 won't know that it can for all MSPs. Unlike the integrated
> solution, no other SDO is going to take and standardize a system
> architecture based on the protocol enhancements in the split solution.
>=20
>             jak
>=20
> ----- Original Message -----
> From: "Tsirtsis, George" <tsirtsis@qualcomm.com>
> To: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>; "James
Kempf"
> <kempf@docomolabs-usa.com>; "Alper Yegin" <alper.yegin@yegin.org>;
> "Basavaraj Patil" <basavaraj.patil@nokia.com>; <mip6@ietf.org>
> Sent: Tuesday, August 22, 2006 4:16 PM
> Subject: RE: Kuntal's comments on the split document (was: Re:
> [Mip6]Conclusion of the consensus call relatedtothebootstrapping I-Ds)
>=20
>=20
> I have not followed this discussion from the beginning so my apologies
> if this has been discussed before.
>=20
> IMHO, the problem with both the split and integrated documents is that
> they are more system design documents than protocol specifications.
>=20
> I think the WG correctly decided to standardize the DHCP-option of the
> integrated document separately since this is the protocol part.
> The rest of the document defines a way to use the DHCP-option together
> with other IETF "tools" to build a system. The split document does the
> same thing so, if there is a protocol extension to be standardized
> (e.g., DNS Update mobility option) it needs to be taken out and be
> standardized.
>=20
> Let me remind everyone that the IETF does not build
> systems/architectures unless absolutely necessary and in this case it
is
> not necessary since one can come up with many different ways of using
> several IETF protocols to bootstrap MIP, all of which are valid.
>=20
> The "system description" parts of the split/integrated documents can
> then become whatever; it does not really matter since the notion of
> "standards track" in the IETF does not apply to systems. As far as I
am
> concerned, if they need to be standardized at all, they need to be
> standardized in an SDO otherwise informational or BCP can work too.
>=20
> Regards
> George
>=20
> > -----Original Message-----
> > From: Chowdhury, Kuntal [mailto:kchowdhury@starentnetworks.com]
> > Sent: Tuesday, August 22, 2006 6:27 PM
> > To: James Kempf; Alper Yegin; Basavaraj Patil; mip6@ietf.org
> > Subject: RE: Kuntal's comments on the split document (was: Re:
> > [Mip6]Conclusion of the consensus call relatedtothebootstrapping
I-Ds)
> >
> >
> >
> > > -----Original Message-----
> > > From: James Kempf [mailto:kempf@docomolabs-usa.com]
> > > Sent: Tuesday, August 22, 2006 3:37 PM
> > > To: Chowdhury, Kuntal; Alper Yegin; Basavaraj Patil; mip6@ietf.org
> > > Subject: Kuntal's comments on the split document (was: Re: [Mip6]
> > > Conclusion of the consensus call relatedtothebootstrapping I-Ds)
> > >
> > > Alright. If you want to discuss the split document then let's do
it
> > (note
> > > change in thread header).
> > >
> > > [KC>] Which part of my statement you found to be "emotional"? Is
it
> > the
> > > "rather useless" part? In my opinion, the split scenario solution
> > > document has some things that are totally out of scope of mip6
> > > bootstrapping (e.g. the dynamic DNS update). Moreover, the HA
> > > bootstrapping is based on DNS query which has security issues.
> Anybody
> > > in the public internet can discover operator's HAs. This is a
> security
> > > hole that the split solution introduces. These are NOT emotional
> > > statements :-). I am just expressing how I feel about the split
> > solution
> > > document, that's all.
> > >
> > > jak>> These are your opinions, and I would say they are rather
> > emotionally
> > > expressed (my opinion, of course).
> > >
> > > jak>> The goals of the split document are different from the
> > intergrated
> > > document. The split document is primarily for enterprises and for
> > > businesses
> > > that have as their primary business providing mobility service
only
> > (hence
> > > the name). Since such businesses are new, they are likely to be
> > > entrepreneurial. They're not going to have the time or resources
to
> > run
> > > around to various different SDOs and try to force their solutions
to
> > get
> > > locked into the standards. The split solution is designed to
provide
> > them
> > > with interoperability. It is possible for integrated wireless
> service
> > > providers to use the split solution, of course, possibly as an
> > additional
> > > revenue generator for providing mobility service to customers that
> use
> > a
> > > different access network provider.
> > >
> > [KC>] What you describe above is the scope of the split document.
The
> > scope is unique, understood. But that does not automatically justify
a
> > standards track RFC for the solution document. What we have is a
split
> > scenario solution framework document _using_ IKEv2, DNS etc. So, are
> you
> > OK to make the split solution I-D an informational RFC?
> >
> > > jak>> Regarding the security issues of DNS, we've been through
this
> > issue
> > > a
> > > number of times, the draft was reviewed by SAAG (we have yet to
> > respond)
> > > and
> > > there was nothing said about it, so I am puzzled why you are
raising
> > this
> > > canard again. We recently had a good (and I might add
nonemotional)
> > > discussion on this list about using anycast, initiated by
> Jean-Marie,
> > and
> > > I've drafted some text up that will allow anycast addresses to be
> used
> > in
> > > DNS SRV RRs instead of the unicast addresses of the HAs, based on
> > > Francis's
> > > draft, and sent the text to Gerardo (he's on vacation at the
> moment).
> > This
> > > should provide some moderate protection from DoS, but it will not
> > protect
> > > completely, just as the DHCP solution won't. As I've pointed out
in
> > the
> > > past, as soon as you release the address of a server to an end
host,
> > > regardless of how it is done, all bets are off. What the end host
> does
> > > with
> > > that address is completely out of your control, and if the end
host
> is
> > > infected with malware, you can be sure somebody's botnet will get
> the
> > > address. Or are you proposing some enhancement to the DHCP based
> > solution
> > > that will make it impossible for malware to grab a home agent's
> > address?
> > >
> > [KC>] There is a clear difference between the way HA address is
> > discovered in the split solution and in the integrated solution. The
> HA
> > address is _assigned_ to the MN in the integrated solution by the
Home
> > AAA server. This ONLY happens once the MN passes authentication. So,
> the
> > chances of giving away the HA address to totally unknown entities in
> > this case is next to none. In case of split scenario, the HAs are
> > totally exposed to anyone with good or bad intention. Anyone with an
> IP
> > connection can send DNS queries to get any MSP's HA addresses and
then
> > launch DoS attacks from his/her basement.
> >
> > It is true that once the HA address is given to an entity, if that
> > entity is compromised, the HA address can get out to some bad guys.
> But
> > it is not likely to happen too often. This type of security threat
is
> > generic and not specific to mip6 bootstrapping, IMHO. If the
> > entity/device is compromised, other things like root-key, username,
> any
> > other cached data will also be revealed. So, it is a generic issue.
> >
> > In case of split scenario, the risk of giving away the HA address to
> bad
> > guys is always there. So, the solution doesn't seem to be deployable
> in
> > public wireless networks.
> >
> > > > HL prefix etc. Integrated scenario is likely to be widely
> deployed,
> > > > where as the split scenario doesn't even have any buyer.
> > > >
> > > > jak>> I think you mean draft-jang will be widely deployed. As I
> > recall
> > > > someone posted email a while back saying that there was no plan
by
> > any
> > > > other
> > > > SDO to adopt the integrated draft as is, just the two draft-jang
> > DHCP
> > > > enhancements.
> > > >
> > > [KC>] Unfortunately, here you are making your argument based on
some
> > > rumor that you heard about real SDO requirements. Please use
> official
> > > liaison channels to confirm SDO requirements before posting
comments
> > on
> > > the mailing list.
> > >
> > > jak>> OK. Would any of our liasons like to comment on this? Is the
> > system
> > > architecture described in the integrated draft what your SDO is
> > planning
> > > on
> > > standardizing?
> > >
> > > > So, if you want to go down this path, we will end up making both
> the
> > > > documents informational. If not both of them should remain
> standards
> > > > track.
> > > >
> > > > jak>> We're not discussing the split draft here. If you want to
> > > propose
> > > > changing it, then start a separate thread.
> > > >
> > > [KC>] We need to discuss how useful the split scenario draft is.
> Also
> > to
> > > be fair, we need to make a decision about informational vs.
> standards
> > > track suitability for _both_ the documents if that's what the WG
> ends
> > up
> > > deciding. That's what I meant to say here.
> > >
> > > jak>> Then why didn't you start a separate thread on it? This is
> basic
> > > IETF
> > > courtesy. Kuntal, you've been around IETF long enough to know
these
> > kinds
> > > of
> > > things.
> > >
> > [KC>] OK, I apologize for raising the issues with the split
solutions
> > I-D late in the game. James, you did not raise all the issues that
you
> > had with the integrated I-D until now. You have been around in IETF
> more
> > than I have been....
> >
> >
> > >             jak
> > >
> >
> >
> > "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
>=20


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



From mip6-bounces@ietf.org Thu Aug 24 01:10:24 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GG7TV-0001TN-8c; Thu, 24 Aug 2006 01:09:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GG7TT-0001T7-PN
	for mip6@ietf.org; Thu, 24 Aug 2006 01:09:51 -0400
Received: from f.csce.kyushu-u.ac.jp ([133.5.33.1])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1GG7TQ-0000lt-2Y
	for mip6@ietf.org; Thu, 24 Aug 2006 01:09:51 -0400
Received: (qmail 23795 invoked from network); 24 Aug 2006 05:09:45 -0000
Received: from unknown (HELO ?127.0.0.1?) (127.0.0.1)
	by localhost with SMTP; 24 Aug 2006 05:09:45 -0000
Date: Thu, 24 Aug 2006 14:09:50 +0900
From: kitasuka@f.csce.kyushu-u.ac.jp
To: manet@ietf.org, mip4@ietf.org, mip6@ietf.org, mipshop@ietf.org,
	monami6@ietf.org, nemo@ietf.org
Message-Id: <20060824140453.A1FB.KITASUKA@f.csce.kyushu-u.ac.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.25.02 [ja]
X-Spam-Score: 0.2 (/)
X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d
Cc: 
Subject: [Mip6] call for participation: ICMU2006, 11-13 October,
	London - Int. Conf. on Mobile Computing and Ubiquitous Networking
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

(apologies if you receive multiple copies of this message)



		Call for Participation
		------------------------

The 3rd International Conference on Mobile Computing and Ubiquitous Networking (ICMU2006)

October 11-13, 2006   BCS London Office, London, UK

Sponsored by Information Processing Society of Japan
Technically Co-Sponsored by
        British Computer Society, 
        Institution of Engineering and Technology, and
        IEEE ITS Society, Technical Committee on Mobile Communications & Applications
Supported by
        International Communications Foundation and
        SCAT (Support Center for Advanced Telecommunications Technology Research, Foundation) 


For detailed information about travel and hotel, please refer to the conference webpage: 

http://www.icmu.org/icmu2006/

ICMU2006 is the 3rd of a successful series of conferences that aim to serve as a specialized conference on a broad range of research topics centred on mobile computing and ubiquitous networking. ICMU strives to provide a place for researchers and practitioners from the globe to meet together to exchange latest research ideas and outcomes on ubiquitous networks and mobile computing. ICMU2006 is to be held in London, UK, one of the most accessible and attractive cities in the world.	


Keynote Talks
-------------

Wednesday, Oct. 11 2006: "RFID: Towards an IP-based Application ? by Ms. Monique Jeanne Morrow, Cisco Systems, Inc., USA 
Thursday, Oct. 12, 2006: "Reconciling Communication Networks, Sensor Networks, and Human Networks: a Social Perspective on Ubiquitous Computing ? by Dr. Ken Wood of Microsoft Research Cambridge, UK 
Friday, Oct. 13, 2006: "Toward Ubiquitous Wireless Networking: the Evolution of Keitai (Cell Phone) Communication?by Dr. Atsushi Murase of NTT DoCoMo, Japan


Program in Brief
----------------
8 Oral Sessions:
(1) Location, (2) QoS, Scheduling, Performance; (3) Ad hoc & sensor networks -1, (4) Ad hoc & sensor networks -2; (5) Security, Privacy; (6) Architecture; (7) Application-1; (8) Application-2

Panel Session, Poster Session



Organizers
-----------
General Chair
  C K Toh: Univ. of Hong Kong
Technical Program Co-Chairs
  Susumu Ishihara: Shizuoka Univ., Japan
  Eiji Kamioka: National Institute of Informatics, Japan 
Publications Co-chairs
  Gen Kitagata: Tohoku Univ., Japan
  Yang Yang: University College London, UK
Publicity Co-chairs
  Teruaki Kitasuka: Kyusyu Univ., Japan
  Kun Yang: Univ. of Essex, UK 
Local Arrangement Chair
  David Martland: Kingston University, UK
  Hiroshi Mineno: Shizuoka University, Japan
Treasurers
  Tomohiko Yagyu:  NEC, Japan
  David Martland: Kingston University, UK
Registration Co-Chairs
  Jindong Hou: France Telecom, UK
  Homare Murakami: NICT, Japan
Steering Committee 
  Osamu Takahashi: Future Univ.Hakodate, Japan
  Tadanori Mizuno: Shizuoka Univ., Japan
  Takashi Watanabe: Shizuoka Univ., Japan
  Miki Yamamoto: Kansai Univ., Japan




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



From mip6-bounces@ietf.org Fri Aug 25 06:56:38 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GGZLu-0003CF-96; Fri, 25 Aug 2006 06:55:54 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GGZLs-0003AA-OP
	for mip6@ietf.org; Fri, 25 Aug 2006 06:55:52 -0400
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GGZLq-00075B-6p
	for mip6@ietf.org; Fri, 25 Aug 2006 06:55:52 -0400
Received: from p130.piuha.net (localhost [127.0.0.1])
	by p130.piuha.net (Postfix) with ESMTP id 3A24B89851;
	Fri, 25 Aug 2006 13:55:38 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id B0B9689837;
	Fri, 25 Aug 2006 13:55:37 +0300 (EEST)
Message-ID: <44EED728.6010300@piuha.net>
Date: Fri, 25 Aug 2006 13:55:36 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Mozilla Thunderbird 1.0.8 (X11/20060725)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Basavaraj Patil <basavaraj.patil@nokia.com>
Subject: Re: [Mip6] Conclusion of the consensus call related to
	the	bootstrapping I-Ds
References: <C110DD97.22AF5%basavaraj.patil@nokia.com>
In-Reply-To: <C110DD97.22AF5%basavaraj.patil@nokia.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 67c1ea29f88502ef6a32ccec927970f0
Cc: mip6@ietf.org, ext James Kempf <kempf@docomolabs-usa.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

For what its worth, I would like to see a document that explains
how the different protocol pieces are used together. Without
such a document, its hard to understand how the protocol
parts make sense and if they indeed work, are secure, etc.

The contents of that document is up to the group to decide
of course -- but it would be useful if matched with reality in
some currently planned deployments, likely 3GPP2. Make
sure there is sufficient joint participation, reviews, etc. with
them.

I can see that some further decisions may be needed on
e.g. what if any protocol parts remain in the integrated
document. I would suggest that to avoid wasting additional
time for purely editorial discussions, the WG focuses on
the technical content (what do we want?) and we let
the chairs decide how the content is packaged into
the documents, under the guidance of the consensus call
that we just concluded.

--Jari

Basavaraj Patil wrote:

>Hi James,
>
>Stepping back from the specifics of the documents that we have today in the
>WG w.r.t bootstrapping, I believe what the WG is chartered (which needs to
>be updated BTW), is to develop a solution or solutions for bootstrapping
>MIP6. I think we disccovered fairly early on that one bootstrapping solution
>does not fit all environments. We are now even considering adopting Vijay's
>draft which specifies bootstrapping in the case of the use of the
>authenication protocol. But that's not the point here.
>
>The WG direction is to develop a set of bootstrapping solutions that can be
>used in various deployment scenarios. The scenarios that we have specified
>in the WG today are based on the use of IKE for bootstrapping for the cases
>that we call split and integrated. The issue about whether the DHCP options
>should be specified within the integrated scenarios document or separately
>is simply a matter of how we split the documents.
>Consensus was that keeping the DHCP options is preferred because of various
>reasons (as has been discussed at length).
>
>My recommendation is that we move forward with the set of existing I-Ds
>which include the problem statement, Split scenario, Integrated scenario,
>and DHCPv6 options.
>
>W.r.t what 3GPP2 really wants from the integrated scenarios I-D, I believe
>they require the IKE based bootstrapping solution for MIP6 and not just the
>DHCP options.
>
>-Raj
>
>
>On 8/22/06 2:41 PM, "ext James Kempf" <kempf@docomolabs-usa.com> wrote:
>
>  
>
>>Raj,
>>
>>I'm not questioning the need for the document. What I'm asking is whether
>>the document, as it stands, is consistent with the direction the WG wants to
>>go in, given the consensus decision not to include the DHCP options into it.
>>It seems to me that the direction is for the various pieces of the
>>intergrated solution as separate documents.
>>
>>Regarding the 3GPP dependency, do they really want the system description
>>part or are they really interested in the relay to server options?
>>
>>            jak
>>
>>
>>----- Original Message -----
>>From: "Basavaraj Patil" <basavaraj.patil@nokia.com>
>>To: "ext James Kempf" <kempf@docomolabs-usa.com>; "Chowdhury, Kuntal"
>><kchowdhury@starentnetworks.com>; "Alper Yegin" <alper.yegin@yegin.org>;
>><mip6@ietf.org>
>>Sent: Tuesday, August 22, 2006 12:13 PM
>>Subject: Re: [Mip6] Conclusion of the consensus call related to the
>>bootstrapping I-Ds
>>
>>
>>    
>>
>>>Having spent a few months on deliberating how DHCP options required for
>>>bootstrapping be specified, lets not go back in time and start discussing
>>>if
>>>the intergrated scenarios I-D is necessary or not.
>>>
>>>When the design team was formed, the conclusion after the completion of
>>>the
>>>split scenarios I-D was that a solution for the integrated scenario is
>>>needed as well and hence the creation of the WG I-D.
>>>
>>>I have also been told by 3GPP2 (liaison) that they have a dependency on
>>>the
>>>integrated scenarios I-D.
>>>
>>>Hence I would recommend that we stop this discussion and lets work on
>>>completing the bootstrap solutions work.
>>>
>>>-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 Aug 25 09:56:41 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GGcAI-0001Ht-EQ; Fri, 25 Aug 2006 09:56:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GGcAH-0001Hi-Bi; Fri, 25 Aug 2006 09:56:05 -0400
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GGcAE-0008Jf-Sf; Fri, 25 Aug 2006 09:56:05 -0400
Received: from p130.piuha.net (localhost [127.0.0.1])
	by p130.piuha.net (Postfix) with ESMTP id 7A9E989851;
	Fri, 25 Aug 2006 16:55:59 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id 43B6989837;
	Fri, 25 Aug 2006 16:55:59 +0300 (EEST)
Message-ID: <44EF016E.5010206@piuha.net>
Date: Fri, 25 Aug 2006 16:55:58 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Mozilla Thunderbird 1.0.8 (X11/20060725)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Mipshop <mipshop@ietf.org>, Mobile IPv6 Mailing List <mip6@ietf.org>
References: <E1GBYY7-0001q9-DY@stiedprstage1.ietf.org>
	<44E072D9.5040307@piuha.net>
In-Reply-To: <44E072D9.5040307@piuha.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Cc: netlmm@ietf.org
Subject: [Mip6] Re: FW: Last Call: 'Goals for Network-based Localized
 Mobility Management
 (NETLMM)' to Informational RFC (draft-ietf-netlmm-nohost-req)
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Reminder: Last day of the Last Call period.

Jari Arkko wrote:

>Hi all,
>
>NETLMM WG has produced a document that outlines the
>goals for a local mobility management solution. It also
>analyzes the fullfillment of those goals wrt existing global
>mobility management protocols (Mobile IPv6) and local
>mobility management solutions (e.g., HMIPv6).
>
>It would be valuable to get additional review from the
>MIPSHOP and MIP6 WGs regarding the latter part.
>The gap analysis in Section 8 of the document.
>
>The best place for follow-ups is probably the NETLMM list,
>though as always you can also send last call comments to
>the IETF main list or the IESG directly.
>
>  
>
>>The IESG has received a request from the Network-based Localized Mobility 
>>Management WG to consider the following document:
>>
>>- 'Goals for Network-based Localized Mobility Management (NETLMM) '
>>  <draft-ietf-netlmm-nohost-req-04.txt> as an Informational RFC
>>
>>The IESG plans to make a decision in the next few weeks, and solicits
>>final comments on this action.  Please send any comments to the
>>iesg@ietf.org or ietf@ietf.org mailing lists by 2006-08-25.
>>
>>The file can be obtained via
>>http://www.ietf.org/internet-drafts/draft-ietf-netlmm-nohost-req-04.txt
>> 
>>    
>>
>
>  
>


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



From mip6-bounces@ietf.org Fri Aug 25 15:50:45 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GGhgx-00016h-58; Fri, 25 Aug 2006 15:50:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GGhgp-00015T-3y; Fri, 25 Aug 2006 15:50:03 -0400
Received: from ns0.neustar.com ([156.154.16.158])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GGhgo-0004wV-T3; Fri, 25 Aug 2006 15:50:03 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id 9BC42328D7;
	Fri, 25 Aug 2006 19:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1GGhgo-0004yJ-FN; Fri, 25 Aug 2006 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: <E1GGhgo-0004yJ-FN@stiedprstage1.ietf.org>
Date: Fri, 25 Aug 2006 15:50:02 -0400
X-Spam-Score: -2.5 (--)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Cc: mip6@ietf.org
Subject: [Mip6] I-D ACTION:draft-ietf-mip6-hiopt-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>
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		: DHCP Option for Home Information Discovery in MIPv6
	Author(s)	: H. Jang, et al.
	Filename	: draft-ietf-mip6-hiopt-00.txt
	Pages		: 15
	Date		: 2006-8-25
	
This draft defines a DHCP-based scheme to enable dynamic discovery of
Mobile IPv6 home agent address, home address, and home subnet.  New
DHCP options are defined to carry the information from a DHCP server
to the DHCP client running on the mobile node.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mip6-hiopt-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-hiopt-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-hiopt-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: <2006-8-25122520.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-mip6-hiopt-00.txt

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

Content-Type: text/plain
Content-ID: <2006-8-25122520.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 Mon Aug 28 21:40:21 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GHsZj-0006nw-IE; Mon, 28 Aug 2006 21:39:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GHsZj-0006nr-01
	for mip6@ietf.org; Mon, 28 Aug 2006 21:39:35 -0400
Received: from mgw-ext13.nokia.com ([131.228.20.172])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GHsZh-0003B5-JG
	for mip6@ietf.org; Mon, 28 Aug 2006 21:39:34 -0400
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
	by mgw-ext13.nokia.com (Switch-3.1.10/Switch-3.1.7) with ESMTP id
	k7T1dWEu025594 for <mip6@ietf.org>; Tue, 29 Aug 2006 04:39:32 +0300
Received: from daebh102.NOE.Nokia.com ([10.241.35.112]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 29 Aug 2006 04:39:32 +0300
Received: from daebe101.NOE.Nokia.com ([10.241.35.113]) by
	daebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 28 Aug 2006 20:39:30 -0500
Received: from 10.241.59.94 ([10.241.59.94]) by daebe101.NOE.Nokia.com
	([10.241.35.113]) with Microsoft Exchange Server HTTP-DAV ; 
	Tue, 29 Aug 2006 01:39:30 +0000
User-Agent: Microsoft-Entourage/11.2.5.060620
Date: Mon, 28 Aug 2006 20:40:20 -0500
From: Basavaraj Patil <basavaraj.patil@nokia.com>
To: <mip6@ietf.org>
Message-ID: <C1190534.23255%basavaraj.patil@nokia.com>
Thread-Topic: WG LC: draft-ietf-mip6-whyauthdataoption-01
Thread-Index: AcbLDBZAVLEuIjb/EdujTwARJNUNiA==
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 29 Aug 2006 01:39:30.0472 (UTC)
	FILETIME=[F8BAFA80:01C6CB0B]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Subject: [Mip6] WG LC: draft-ietf-mip6-whyauthdataoption-01
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org


Hello,

The I-D 'Why Authentication Data suboption is needed for MIP6'
(draft-ietf-mip6-whyauthdataoption-01) was generated as a justification for
specifying the 'Authentication Protocol' (RFC 4285) in the MIP6 WG.

Similar to RFC4225 (MIP6 Route Optimization Security Design Background), we
would like this I-D to be published as informational to capture the thinking
in the WG that went into the specification of the Auth. Protocol.

Please consider this as the Working group last call for I-D:
draft-ietf-mip6-whyauthdataoption-01.

The WG LC will expire on September 12th, 2006.
Please submit your comments to the WG ML or to the authors.

-Raj


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



From mip6-bounces@ietf.org Wed Aug 30 07:33:28 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GIOId-0004Ub-GQ; Wed, 30 Aug 2006 07:32:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GIOIa-0004Pi-Rj
	for mip6@ietf.org; Wed, 30 Aug 2006 07:32:00 -0400
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GIO9C-0007v5-6z
	for mip6@ietf.org; Wed, 30 Aug 2006 07:22:19 -0400
Received: from magus.qualcomm.com (magus.qualcomm.com [129.46.61.148])
	by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id
	k7UBMCfE017675
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL)
	for <mip6@ietf.org>; Wed, 30 Aug 2006 04:22:13 -0700
Received: from NAEXBR03.na.qualcomm.com (naexbr03.qualcomm.com
	[129.46.134.172])
	by magus.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id k7UBMBQZ011445
	for <mip6@ietf.org>; Wed, 30 Aug 2006 04:22:12 -0700 (PDT)
Received: from NAEX14.na.qualcomm.com ([10.47.5.242]) by
	NAEXBR03.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 30 Aug 2006 04:22:11 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 30 Aug 2006 04:22:08 -0700
Message-ID: <7EB20EA0938B4D42A2D82689365C9B7A1922E7@NAEX14.na.qualcomm.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: WG LC for draft-ietf-mip6-dsmip-problem-02?
Thread-Index: AcbMJoeIKFG3xPcyQYO2CPlIMOUyVw==
From: "Soliman, Hesham" <hsoliman@qualcomm.com>
To: <mip6@ietf.org>
X-OriginalArrivalTime: 30 Aug 2006 11:22:11.0955 (UTC)
	FILETIME=[89CFAC30:01C6CC26]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aefe408d50e9c7c47615841cb314bed
Subject: [Mip6] WG LC for draft-ietf-mip6-dsmip-problem-02?
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hi chairs,=20

Can we call for LC for this draft? The draft has been ready for a long
time now and in the last meeting we agreed to indlude it in the
charter/WG.=20

Hesham

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



From mip6-bounces@ietf.org Wed Aug 30 20:43:22 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GIadt-00011x-On; Wed, 30 Aug 2006 20:42:49 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GIads-00011s-MM
	for mip6@ietf.org; Wed, 30 Aug 2006 20:42:48 -0400
Received: from mgw-ext11.nokia.com ([131.228.20.170])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GIads-0002OJ-2U
	for mip6@ietf.org; Wed, 30 Aug 2006 20:42:48 -0400
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211])
	by mgw-ext11.nokia.com (Switch-3.1.10/Switch-3.1.7) with ESMTP id
	k7V0gjOV017731 for <mip6@ietf.org>; Thu, 31 Aug 2006 03:42:47 +0300
Received: from daebh102.NOE.Nokia.com ([10.241.35.112]) by
	esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 31 Aug 2006 03:42:45 +0300
Received: from daebe101.NOE.Nokia.com ([10.241.35.113]) by
	daebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 30 Aug 2006 19:42:44 -0500
Received: from 10.162.253.30 ([10.162.253.30]) by daebe101.NOE.Nokia.com
	([10.241.35.113]) with Microsoft Exchange Server HTTP-DAV ; 
	Thu, 31 Aug 2006 00:42:44 +0000
User-Agent: Microsoft-Entourage/11.2.5.060620
Date: Wed, 30 Aug 2006 19:43:35 -0500
From: Basavaraj Patil <basavaraj.patil@nokia.com>
To: <mip6@ietf.org>
Message-ID: <C11B9AE7.233DF%basavaraj.patil@nokia.com>
Thread-Topic: Revised WG charter 
Thread-Index: AcbMln2KvAZUGDiJEduIYQARJNUNiA==
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 31 Aug 2006 00:42:44.0486 (UTC)
	FILETIME=[5F6E4260:01C6CC96]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e472ca43d56132790a46d9eefd95f0a5
Subject: [Mip6] Revised WG charter 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org


Hello,

Below is the revised WG charter (based on discussion at IETF66 and WG ML
following the meeting). The intent is to send this for IESG review/approval
by Sept 8th. If you have comments, please post them to the list.

-Raj

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


Mobility for IPv6 (mip6)

Last Modified: 2006-08-26

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

Internet Area Director(s):
Jari Arkko <jari.arkko@piuha.net>
Mark Townsley <townsley@cisco.com>

Internet Area Advisor:
Jari Arkko <jari.arkko@piuha.net>

Mailing Lists:
General Discussion: mip6@ietf.org
To Subscribe: https://www.ietf.org/mailman/listinfo/mip6
Archive: http://www.ietf.org/mail-archive/web/mip6/index.html

Description of Working Group:

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

     o RFC 3775
     o RFC 3776

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

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

Work items related to base specification maintenance include:

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

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

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

Work items related to large scale deployment include:

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

   Work on the problem statement and the solutions needed for various
   deployment scenarios. Work with other WGs such as DHC for defining
   the options needed for bootstrapping.

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

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

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

 - A mechanism to force an MN to switch the HA that is currently
   serving it. This is required in deployments where the HA may need
   to be taken offline for maintenance.

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

Work items related to informational documentation include:

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

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

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

Milestones:

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

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

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

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

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

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

Nov 2006 Submit I-D 'DHCP Options for Home Information Discovery in
        MIPv6' for publication as a proposed standard.

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

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

Dec 2006 Submit I-D 'Mobility Header Home Agent Switch Message' to
         IESG for publication as a Proposed Standard.

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

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

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




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



From mip6-bounces@ietf.org Wed Aug 30 21:15:10 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GIb8u-00083v-Bm; Wed, 30 Aug 2006 21:14:52 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GIb8s-00083h-E2
	for mip6@ietf.org; Wed, 30 Aug 2006 21:14:50 -0400
Received: from mgw-ext11.nokia.com ([131.228.20.170])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GIb8r-0005rB-0X
	for mip6@ietf.org; Wed, 30 Aug 2006 21:14:50 -0400
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145])
	by mgw-ext11.nokia.com (Switch-3.1.10/Switch-3.1.7) with ESMTP id
	k7V1Ei1G001653 for <mip6@ietf.org>; Thu, 31 Aug 2006 04:14:48 +0300
Received: from daebh101.NOE.Nokia.com ([10.241.35.111]) by
	esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 31 Aug 2006 04:14:03 +0300
Received: from daebe101.NOE.Nokia.com ([10.241.35.113]) by
	daebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 30 Aug 2006 20:14:01 -0500
Received: from 10.162.253.30 ([10.162.253.30]) by daebe101.NOE.Nokia.com
	([10.241.35.113]) with Microsoft Exchange Server HTTP-DAV ; 
	Thu, 31 Aug 2006 01:14:01 +0000
User-Agent: Microsoft-Entourage/11.2.5.060620
Date: Wed, 30 Aug 2006 20:14:53 -0500
From: Basavaraj Patil <basavaraj.patil@nokia.com>
To: <mip6@ietf.org>
Message-ID: <C11BA23D.233EB%basavaraj.patil@nokia.com>
Thread-Topic: WG LC: draft-ietf-mip6-dsmip-problem-02.txt
Thread-Index: AcbMmtzqG4QbijiOEduIYQARJNUNiA==
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 31 Aug 2006 01:14:01.0397 (UTC)
	FILETIME=[BE282650:01C6CC9A]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Subject: [Mip6] WG LC: draft-ietf-mip6-dsmip-problem-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>
Errors-To: mip6-bounces@ietf.org


Hello,

Please consider this as the WG last call for I-D: Mobility management
for Dual stack mobile nodes :  A Problem Statement
(draft-ietf-mip6-dsmip-problem-02.txt)

The status intended for I-D draft-ietf-mip6-dsmip-problem-02.txt is
Informational. 

The last call will expire on Sept 14th. Please send your comments to
the WG list or to the authors.

-Raj


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



From mip6-bounces@ietf.org Wed Aug 30 21:48:24 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GIbf3-0008Eo-1N; Wed, 30 Aug 2006 21:48:05 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GIbf1-0008AS-CC
	for mip6@ietf.org; Wed, 30 Aug 2006 21:48:03 -0400
Received: from mx0.starentnetworks.com ([12.38.223.203])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GIbez-0001EI-3T
	for mip6@ietf.org; Wed, 30 Aug 2006 21:48:03 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mx0.starentnetworks.com (Postfix) with ESMTP id 11E4490005;
	Wed, 30 Aug 2006 21:47:57 -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 14439-04; Wed, 30 Aug 2006 21:47:56 -0400 (EDT)
Received: from exchtewks1.starentnetworks.com (exchtewks1.starentnetworks.com
	[12.33.233.52]) by mx0.starentnetworks.com (Postfix) with ESMTP;
	Wed, 30 Aug 2006 21:47:55 -0400 (EDT)
X-MessageTextProcessor: DisclaimIt (2.70.271) [Starent Networks Corp.]
Received: from exchtewks2.starentnetworks.com ([12.33.232.12]) by
	exchtewks1.starentnetworks.com with Microsoft
	SMTPSVC(6.0.3790.1830); Wed, 30 Aug 2006 21:47:55 -0400
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] Revised WG charter 
Date: Wed, 30 Aug 2006 21:47:55 -0400
Message-ID: <7CCD07160348804497EF29E9EA5560D78372E1@exchtewks2.starentnetworks.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] Revised WG charter 
thread-index: AcbMln2KvAZUGDiJEduIYQARJNUNiAACFb/Q
From: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
Importance: normal
To: "Basavaraj Patil" <basavaraj.patil@nokia.com>, <mip6@ietf.org>
Priority: normal
X-OriginalArrivalTime: 31 Aug 2006 01:47:55.0777 (UTC)
	FILETIME=[7ABDE710:01C6CC9F]
X-Virus-Scanned: amavisd-new 2.2.1 (20041222) at mx0.starentnetworks.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: df9edf1223802dd4cf213867a3af6121
Cc: "Tschofenig, Hannes" <hannes.tschofenig@siemens.com>,
	Avi Lior <avi@bridgewatersystems.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Hello Raj,

MIP6-RADIUS is another work item that should be on the mip6 WG charter.
Could you please update the charter accordingly?

-Kuntal


> -----Original Message-----
> From: Basavaraj Patil [mailto:basavaraj.patil@nokia.com]
> Sent: Wednesday, August 30, 2006 7:44 PM
> To: mip6@ietf.org
> Subject: [Mip6] Revised WG charter
>=20
>=20
> Hello,
>=20
> Below is the revised WG charter (based on discussion at IETF66 and WG
ML
> following the meeting). The intent is to send this for IESG
> review/approval
> by Sept 8th. If you have comments, please post them to the list.
>=20
> -Raj
>=20
> ------------------------------------------------------------
>=20
>=20
> Mobility for IPv6 (mip6)
>=20
> Last Modified: 2006-08-26
>=20
> Chair(s):
> Basavaraj Patil <basavaraj.patil@nokia.com>
> Gopal Dommety <gdommety@cisco.com>
>=20
> Internet Area Director(s):
> Jari Arkko <jari.arkko@piuha.net>
> Mark Townsley <townsley@cisco.com>
>=20
> Internet Area Advisor:
> Jari Arkko <jari.arkko@piuha.net>
>=20
> Mailing Lists:
> General Discussion: mip6@ietf.org
> To Subscribe: https://www.ietf.org/mailman/listinfo/mip6
> Archive: http://www.ietf.org/mail-archive/web/mip6/index.html
>=20
> Description of Working Group:
>=20
> Mobile IPv6 (MIP6) specifies routing support which permits an IPv6
> host to continue using its home address as it moves around the
> Internet, enabling continuity of sessions. Mobile IPv6 supports
> transparency above the IP layer, including maintenance of active TCP
> connections and UDP port bindings. The base specifications for Mobile
> IPv6 consist of:
>=20
>      o RFC 3775
>      o RFC 3776
>=20
> The primary goal of the MIP6 working group will be to enhance base
> IPv6 mobility by continuing work on developments that are required for
> wide-scale deployments. Additionally the working group will ensure
> that any issues identified by implementation and interoperability
> experience are addressed, and that the base specifications are
> maintained. The group will also produce informational documentation,
> such as design rationale documents or description of specific issues
> within the protocol.
>=20
> Deployment considerations call for work to reduce per-mobile node
> configuration and enrollment effort, solutions to enable dual-stack
> operation, mechanisms to support high-availabity home agents, and ways
> to employ Mobile IPv6 in the presence of firewalls.
>=20
> Work items related to base specification maintenance include:
>=20
>  - Create and maintain an issue list that is generated on the basis of
>    implementation and interoperability experience. Address specific
>    issues with specific updates or revisions of the base
>    specification.  This work relates only to corrections and
>    clarifications. The working group shall not revisit design
>    decisions or change the protocol.
>=20
>  - Update RFC 3776 to specify the usage of IKEv2 for the establishment
>    of the IPsec SA between the MN and HA. This work also provides a
>    way for a mobile node to change its home address or employ multiple
>    home addresses as needed.
>=20
>  - Update the IANA considerations of RFC 3775 to allow extensions for
>    experimental purposes as well passing of optional vendor-specific
>    information.
>=20
> Work items related to large scale deployment include:
>=20
>  - Bootstrapping Mobile IPv6: A bootstrapping mechanism is intended to
>    be used when the device is turned on the very first time and
>    activates Mobile IPv6, or periodically such as when powering
>    on. The WG should investigate and define the scope before solving
>    the problem.
>=20
>    Work on the problem statement and the solutions needed for various
>    deployment scenarios. Work with other WGs such as DHC for defining
>    the options needed for bootstrapping.
>=20
>  - Capture the AAA requirements needed for bootstrapping and
>    deployment, and work with the Radext and DiME WGs on the solutions.
>=20
>  - A Solution for MIP6 session continuity for dual stack hosts which
>    attach to IPv4 access networks. Additionally provide a mechanism
>    for carrying IPv4 packets via the Home agent for MIP6 capable
>    dual-stack hosts. This work will be done in collaboration with the
>    NEMO WG.
>=20
>  - A protocol based solution for enhancing the reliability of home
>    agents and a method to force a host to switch home agents.
>=20
>  - A mechanism to force an MN to switch the HA that is currently
>    serving it. This is required in deployments where the HA may need
>    to be taken offline for maintenance.
>=20
>  - Work on solutions to deal with firewalls and the problems that
>    firewalls cause as identified in RFC 4487.
>=20
> Work items related to informational documentation include:
>=20
>  - Produce a problem statement relating to location privacy and the
>    use of Mobile IPv6. Work with the IRTF MOBOPTS RG on developing the
>    solution.
>=20
>  - Produce a design rationale that documents the historical
>    thinking behind the introduction of an alternative security
>    mechanism, the Authentication Protocol (RFC 4285).
>=20
> It should be noted that some of the features that are directly related
> to Mobile IPv6 are being worked on in the MONAMI6, MIPSHOP, and NEMO
> working groups. The specific extensions from these groups are out of
> scope for the MIP6 working group. In particular, all optimizations are
> out of scope. However, MIP6 may assist these groups when they use
> features listed above and have requirements on them.
>=20
> Milestones:
>=20
> Done          Submit I-D 'MIPv6 operation with IKEV2 and the revised
>         IPsec Architecture' to IESG for publication as a
>         Proposed Standard.
>=20
> Sep 2006    Submit I-D 'Motivation for Authentication I-D' to IESG
>         for publication as Informational.
>=20
> Sep 2006    Submit I-D 'Bootstrapping solution for Integrated
Scenario'
>         to IESG for publication as a Proposed Standard.
>=20
> Oct 2006    Submit I-D 'Goals for AAA HA Interface' to IESG for
>         publication as Informational.
>=20
> Oct 2006    Submit I-D 'Address Location Privacy and Mobile IPv6
Problem
>         Statement' to IESG for publication as Informational.
>=20
> Nov 2006    Submit I-D 'Bootstrapping solution for split Scenario' to
IESG
>         for publication as a Proposed Standard.
>=20
> Nov 2006 Submit I-D 'DHCP Options for Home Information Discovery in
>         MIPv6' for publication as a proposed standard.
>=20
> Dec 2006    Submit I-D 'Home agent reliability' to IESG for
publication
>         as a Proposed Standard.
>=20
> Dec 2006    Submit I-D 'Mobile IPv6 Dual-Stack Operation' to IESG for
>         publication as a Proposed Standard.
>=20
> Dec 2006 Submit I-D 'Mobility Header Home Agent Switch Message' to
>          IESG for publication as a Proposed Standard.
>=20
> Jan 2007    Submit I-D 'Mobile IPv6 Experimental Allocations' to IESG
for
>         publication as a Proposed Standard.
>=20
> Apr 2007    Submit I-D 'Mobile IPv6 Operation with Firewalls' to IESG
>         for publication as Informational.
>=20
> May 2007    Submit I-D(s) related to specific updates and corrections
>         of RFC 3775 to IESG for publication as Proposed Standard.
>=20
>=20
>=20
>=20
> _______________________________________________
> Mip6 mailing list
> Mip6@ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6


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

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



From mip6-bounces@ietf.org Thu Aug 31 14:04:46 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GIqta-0005ac-ES; Thu, 31 Aug 2006 14:04:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GIqtY-0005aW-Kg
	for mip6@ietf.org; Thu, 31 Aug 2006 14:04:04 -0400
Received: from key1.docomolabs-usa.com ([216.98.102.225]
	helo=fridge.docomolabs-usa.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GIqtY-0008Dn-0R
	for mip6@ietf.org; Thu, 31 Aug 2006 14:04:04 -0400
Message-ID: <012001c6cd27$e67e3fd0$626015ac@dcml.docomolabsusa.com>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Basavaraj Patil" <basavaraj.patil@nokia.com>, <mip6@ietf.org>
References: <C11B9AE7.233DF%basavaraj.patil@nokia.com>
Subject: Re: [Mip6] Revised WG charter 
Date: Thu, 31 Aug 2006 11:04:28 -0700
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Spam-Score: 3.1 (+++)
X-Scan-Signature: 963faf56c3a5b6715f0b71b66181e01a
Cc: 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

Raj,

Some specific comments, mostly editorial.


>
>
> Mobility for IPv6 (mip6)
>
> Last Modified: 2006-08-26
>
> Chair(s):
> Basavaraj Patil <basavaraj.patil@nokia.com>
> Gopal Dommety <gdommety@cisco.com>
>
> Internet Area Director(s):
> Jari Arkko <jari.arkko@piuha.net>
> Mark Townsley <townsley@cisco.com>
>
> Internet Area Advisor:
> Jari Arkko <jari.arkko@piuha.net>
>
> Mailing Lists:
> General Discussion: mip6@ietf.org
> To Subscribe: https://www.ietf.org/mailman/listinfo/mip6
> Archive: http://www.ietf.org/mail-archive/web/mip6/index.html
>
> Description of Working Group:
>
> Mobile IPv6 (MIP6) specifies routing support which permits an IPv6
> host to continue using its home address as it moves around the
> Internet, enabling continuity of sessions. Mobile IPv6 supports
> transparency above the IP layer, including maintenance of active TCP
> connections and UDP port bindings. The base specifications for Mobile

So does this mean the Mobile IP doesn't support SCTP or DCCP?

I'd suggest the following:

    including maintenance of active transport level sessions.

> IPv6 consist of:
>
>     o RFC 3775
>     o RFC 3776
>
> The primary goal of the MIP6 working group will be to enhance base
> IPv6 mobility by continuing work on developments that are required for
> wide-scale deployments. Additionally the working group will ensure
> that any issues identified by implementation and interoperability
> experience are addressed, and that the base specifications are
> maintained. The group will also produce informational documentation,
> such as design rationale documents or description of specific issues
> within the protocol.
>
> Deployment considerations call for work to reduce per-mobile node
> configuration and enrollment effort, solutions to enable dual-stack
> operation, mechanisms to support high-availabity home agents, and ways
> to employ Mobile IPv6 in the presence of firewalls.
>
> Work items related to base specification maintenance include:
>
> - Create and maintain an issue list that is generated on the basis of
>   implementation and interoperability experience. Address specific
>   issues with specific updates or revisions of the base
>   specification.  This work relates only to corrections and
>   clarifications. The working group shall not revisit design
>   decisions or change the protocol.
>
> - Update RFC 3776 to specify the usage of IKEv2 for the establishment
>   of the IPsec SA between the MN and HA. This work also provides a
>   way for a mobile node to change its home address or employ multiple
>   home addresses as needed.
>
> - Update the IANA considerations of RFC 3775 to allow extensions for
>   experimental purposes as well passing of optional vendor-specific
>   information.
>
> Work items related to large scale deployment include:
>
> - Bootstrapping Mobile IPv6: A bootstrapping mechanism is intended to
>   be used when the device is turned on the very first time and
>   activates Mobile IPv6, or periodically such as when powering
>   on. The WG should investigate and define the scope before solving
>   the problem.
>
>   Work on the problem statement and the solutions needed for various
>   deployment scenarios. Work with other WGs such as DHC for defining
>   the options needed for bootstrapping.
>
> - Capture the AAA requirements needed for bootstrapping and
>   deployment, and work with the Radext and DiME WGs on the solutions.
>

I think this addresses Kuntal's comment.

> - A Solution for MIP6 session continuity for dual stack hosts which
>   attach to IPv4 access networks. Additionally provide a mechanism
>   for carrying IPv4 packets via the Home agent for MIP6 capable
>   dual-stack hosts. This work will be done in collaboration with the
>   NEMO WG.
>
> - A protocol based solution for enhancing the reliability of home
>   agents and a method to force a host to switch home agents.
>
> - A mechanism to force an MN to switch the HA that is currently
>   serving it. This is required in deployments where the HA may need
>   to be taken offline for maintenance.
>
> - Work on solutions to deal with firewalls and the problems that
>   firewalls cause as identified in RFC 4487.
>
> Work items related to informational documentation include:
>
> - Produce a problem statement relating to location privacy and the
>   use of Mobile IPv6. Work with the IRTF MOBOPTS RG on developing the
>   solution.
>
> - Produce a design rationale that documents the historical
>   thinking behind the introduction of an alternative security
>   mechanism, the Authentication Protocol (RFC 4285).
>

Actually, there are some technical problems with RFC 4285. There is no 
algorithm agility, for example, so if cryptanalysis continues to chip away 
at SHA1, the security will deteriorate. I think it might be worthwhile to 
revisit RFC 4285 if the WG really believes there is value in it.

> It should be noted that some of the features that are directly related
> to Mobile IPv6 are being worked on in the MONAMI6, MIPSHOP, and NEMO
> working groups. The specific extensions from these groups are out of
> scope for the MIP6 working group. In particular, all optimizations are
> out of scope. However, MIP6 may assist these groups when they use
> features listed above and have requirements on them.
>
> Milestones:
>
> Done          Submit I-D 'MIPv6 operation with IKEV2 and the revised
>        IPsec Architecture' to IESG for publication as a
>        Proposed Standard.
>

If this is complete, then why is it in the milestones?

> Sep 2006    Submit I-D 'Motivation for Authentication I-D' to IESG
>        for publication as Informational.
>
> Sep 2006    Submit I-D 'Bootstrapping solution for Integrated Scenario'
>        to IESG for publication as a Proposed Standard.
>
> Oct 2006    Submit I-D 'Goals for AAA HA Interface' to IESG for
>        publication as Informational.
>
> Oct 2006    Submit I-D 'Address Location Privacy and Mobile IPv6 Problem
>        Statement' to IESG for publication as Informational.
>
> Nov 2006    Submit I-D 'Bootstrapping solution for split Scenario' to IESG
>        for publication as a Proposed Standard.
>
> Nov 2006 Submit I-D 'DHCP Options for Home Information Discovery in
>        MIPv6' for publication as a proposed standard.
>
> Dec 2006    Submit I-D 'Home agent reliability' to IESG for publication
>        as a Proposed Standard.
>
> Dec 2006    Submit I-D 'Mobile IPv6 Dual-Stack Operation' to IESG for
>        publication as a Proposed Standard.
>
> Dec 2006 Submit I-D 'Mobility Header Home Agent Switch Message' to
>         IESG for publication as a Proposed Standard.
>
> Jan 2007    Submit I-D 'Mobile IPv6 Experimental Allocations' to IESG for
>        publication as a Proposed Standard.
>
> Apr 2007    Submit I-D 'Mobile IPv6 Operation with Firewalls' to IESG
>        for publication as Informational.
>
> May 2007    Submit I-D(s) related to specific updates and corrections
>        of RFC 3775 to IESG for publication as Proposed Standard.
>

Some of these are very short term, like the Sept. ones. If the charter is 
approved by the end of Sept, they will be complete before the charter is. Is 
it really necessary to list those?

        jak 


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



From mip6-bounces@ietf.org Thu Aug 31 15:26:11 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GIsAl-0000iP-7V; Thu, 31 Aug 2006 15:25:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GIsAj-0000iF-RX
	for mip6@ietf.org; Thu, 31 Aug 2006 15:25:53 -0400
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GIsAi-0000cc-6O
	for mip6@ietf.org; Thu, 31 Aug 2006 15:25:53 -0400
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-3.cisco.com with ESMTP; 31 Aug 2006 12:25:51 -0700
X-IronPort-AV: i="4.08,195,1154934000"; 
	d="scan'208"; a="442171736:sNHT46435624"
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-1.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id
	k7VJPphM027224; Thu, 31 Aug 2006 12:25:51 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com
	[128.107.191.100])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id k7VJPpYp024846;
	Thu, 31 Aug 2006 12:25:51 -0700 (PDT)
Received: from xmb-sjc-224.amer.cisco.com ([128.107.191.98]) by
	xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211);
	Thu, 31 Aug 2006 12:25:51 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] Revised WG charter 
Date: Thu, 31 Aug 2006 12:25:50 -0700
Message-ID: <28CEA477BE98ED48AF08A0B637A74BF4023242F6@xmb-sjc-224.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip6] Revised WG charter 
Thread-Index: AcbNKgVjbcnNolgBRiugnY1yidY0uAACOt+A
From: "Gopal Dommety \(gdommety\)" <gdommety@cisco.com>
To: "James Kempf" <kempf@docomolabs-usa.com>,
	"Basavaraj Patil" <basavaraj.patil@nokia.com>, <mip6@ietf.org>
X-OriginalArrivalTime: 31 Aug 2006 19:25:51.0503 (UTC)
	FILETIME=[453909F0:01C6CD33]
DKIM-Signature: a=rsa-sha1; q=dns; l=7966; t=1157052351; x=1157916351;
	c=relaxed/simple; s=sjdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=gdommety@cisco.com;
	z=From:=22Gopal=20Dommety=20\(gdommety\)=22=20<gdommety@cisco.com>
	|Subject:RE=3A=20[Mip6]=20Revised=20WG=20charter=20;
	X=v=3Dcisco.com=3B=20h=3DwBW1f35lq9P3v6ckLe0P4eD8uYw=3D;
	b=fT72+hWGggs3hxDoSkNubHk4qhQv7/WX+ECyYR2wiF6Oyzbd878KiL/TS7hvwI90ziLCeD+q
	1wKyfRutjh9oT9WzN9OphEEhu2wp4qTsVrMMHJzGHnnl/bv6b0bHTUOK;
Authentication-Results: sj-dkim-1.cisco.com; header.From=gdommety@cisco.com;
	dkim=pass ( sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ff0adf256e4dd459cc25215cfa732ac1
Cc: 
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>,
	<mailto:mip6-request@ietf.org?subject=subscribe>
Errors-To: mip6-bounces@ietf.org

James,

	It will be useful to list the milestones even if they are short
term. This will provide accurate tracking without much of overhear.


Regards,
-Gopal


-----Original Message-----
From: James Kempf [mailto:kempf@docomolabs-usa.com]=20
Sent: Thursday, August 31, 2006 11:04 AM
To: Basavaraj Patil; mip6@ietf.org
Subject: Re: [Mip6] Revised WG charter=20

Raj,

Some specific comments, mostly editorial.


>
>
> Mobility for IPv6 (mip6)
>
> Last Modified: 2006-08-26
>
> Chair(s):
> Basavaraj Patil <basavaraj.patil@nokia.com> Gopal Dommety=20
> <gdommety@cisco.com>
>
> Internet Area Director(s):
> Jari Arkko <jari.arkko@piuha.net>
> Mark Townsley <townsley@cisco.com>
>
> Internet Area Advisor:
> Jari Arkko <jari.arkko@piuha.net>
>
> Mailing Lists:
> General Discussion: mip6@ietf.org
> To Subscribe: https://www.ietf.org/mailman/listinfo/mip6
> Archive: http://www.ietf.org/mail-archive/web/mip6/index.html
>
> Description of Working Group:
>
> Mobile IPv6 (MIP6) specifies routing support which permits an IPv6=20
> host to continue using its home address as it moves around the=20
> Internet, enabling continuity of sessions. Mobile IPv6 supports=20
> transparency above the IP layer, including maintenance of active TCP=20
> connections and UDP port bindings. The base specifications for Mobile

So does this mean the Mobile IP doesn't support SCTP or DCCP?

I'd suggest the following:

    including maintenance of active transport level sessions.

> IPv6 consist of:
>
>     o RFC 3775
>     o RFC 3776
>
> The primary goal of the MIP6 working group will be to enhance base
> IPv6 mobility by continuing work on developments that are required for

> wide-scale deployments. Additionally the working group will ensure=20
> that any issues identified by implementation and interoperability=20
> experience are addressed, and that the base specifications are=20
> maintained. The group will also produce informational documentation,=20
> such as design rationale documents or description of specific issues=20
> within the protocol.
>
> Deployment considerations call for work to reduce per-mobile node=20
> configuration and enrollment effort, solutions to enable dual-stack=20
> operation, mechanisms to support high-availabity home agents, and ways

> to employ Mobile IPv6 in the presence of firewalls.
>
> Work items related to base specification maintenance include:
>
> - Create and maintain an issue list that is generated on the basis of
>   implementation and interoperability experience. Address specific
>   issues with specific updates or revisions of the base
>   specification.  This work relates only to corrections and
>   clarifications. The working group shall not revisit design
>   decisions or change the protocol.
>
> - Update RFC 3776 to specify the usage of IKEv2 for the establishment
>   of the IPsec SA between the MN and HA. This work also provides a
>   way for a mobile node to change its home address or employ multiple
>   home addresses as needed.
>
> - Update the IANA considerations of RFC 3775 to allow extensions for
>   experimental purposes as well passing of optional vendor-specific
>   information.
>
> Work items related to large scale deployment include:
>
> - Bootstrapping Mobile IPv6: A bootstrapping mechanism is intended to
>   be used when the device is turned on the very first time and
>   activates Mobile IPv6, or periodically such as when powering
>   on. The WG should investigate and define the scope before solving
>   the problem.
>
>   Work on the problem statement and the solutions needed for various
>   deployment scenarios. Work with other WGs such as DHC for defining
>   the options needed for bootstrapping.
>
> - Capture the AAA requirements needed for bootstrapping and
>   deployment, and work with the Radext and DiME WGs on the solutions.
>

I think this addresses Kuntal's comment.

> - A Solution for MIP6 session continuity for dual stack hosts which
>   attach to IPv4 access networks. Additionally provide a mechanism
>   for carrying IPv4 packets via the Home agent for MIP6 capable
>   dual-stack hosts. This work will be done in collaboration with the
>   NEMO WG.
>
> - A protocol based solution for enhancing the reliability of home
>   agents and a method to force a host to switch home agents.
>
> - A mechanism to force an MN to switch the HA that is currently
>   serving it. This is required in deployments where the HA may need
>   to be taken offline for maintenance.
>
> - Work on solutions to deal with firewalls and the problems that
>   firewalls cause as identified in RFC 4487.
>
> Work items related to informational documentation include:
>
> - Produce a problem statement relating to location privacy and the
>   use of Mobile IPv6. Work with the IRTF MOBOPTS RG on developing the
>   solution.
>
> - Produce a design rationale that documents the historical
>   thinking behind the introduction of an alternative security
>   mechanism, the Authentication Protocol (RFC 4285).
>

Actually, there are some technical problems with RFC 4285. There is no
algorithm agility, for example, so if cryptanalysis continues to chip
away at SHA1, the security will deteriorate. I think it might be
worthwhile to revisit RFC 4285 if the WG really believes there is value
in it.

> It should be noted that some of the features that are directly related

> to Mobile IPv6 are being worked on in the MONAMI6, MIPSHOP, and NEMO=20
> working groups. The specific extensions from these groups are out of=20
> scope for the MIP6 working group. In particular, all optimizations are

> out of scope. However, MIP6 may assist these groups when they use=20
> features listed above and have requirements on them.
>
> Milestones:
>
> Done          Submit I-D 'MIPv6 operation with IKEV2 and the revised
>        IPsec Architecture' to IESG for publication as a
>        Proposed Standard.
>

If this is complete, then why is it in the milestones?

> Sep 2006    Submit I-D 'Motivation for Authentication I-D' to IESG
>        for publication as Informational.
>
> Sep 2006    Submit I-D 'Bootstrapping solution for Integrated
Scenario'
>        to IESG for publication as a Proposed Standard.
>
> Oct 2006    Submit I-D 'Goals for AAA HA Interface' to IESG for
>        publication as Informational.
>
> Oct 2006    Submit I-D 'Address Location Privacy and Mobile IPv6
Problem
>        Statement' to IESG for publication as Informational.
>
> Nov 2006    Submit I-D 'Bootstrapping solution for split Scenario' to
IESG
>        for publication as a Proposed Standard.
>
> Nov 2006 Submit I-D 'DHCP Options for Home Information Discovery in
>        MIPv6' for publication as a proposed standard.
>
> Dec 2006    Submit I-D 'Home agent reliability' to IESG for
publication
>        as a Proposed Standard.
>
> Dec 2006    Submit I-D 'Mobile IPv6 Dual-Stack Operation' to IESG for
>        publication as a Proposed Standard.
>
> Dec 2006 Submit I-D 'Mobility Header Home Agent Switch Message' to
>         IESG for publication as a Proposed Standard.
>
> Jan 2007    Submit I-D 'Mobile IPv6 Experimental Allocations' to IESG
for
>        publication as a Proposed Standard.
>
> Apr 2007    Submit I-D 'Mobile IPv6 Operation with Firewalls' to IESG
>        for publication as Informational.
>
> May 2007    Submit I-D(s) related to specific updates and corrections
>        of RFC 3775 to IESG for publication as Proposed Standard.
>

Some of these are very short term, like the Sept. ones. If the charter
is approved by the end of Sept, they will be complete before the charter
is. Is it really necessary to list those?

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



